From xen-users-bounces@lists.xen.org Sat Sep 01 09:44:08 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Sat, 01 Sep 2012 09:44:08 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1T7kDy-00086h-Vm; Sat, 01 Sep 2012 09:42:42 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1T7kDx-00086c-FD for xen-users@lists.xen.org; Sat, 01 Sep 2012 09:42:41 +0000 Received: from [85.158.143.35:59082] by server-2.bemta-4.messagelabs.com id 20/76-21239-098D1405; Sat, 01 Sep 2012 09:42:40 +0000 X-Env-Sender: tesla.coil@live.com X-Msg-Ref: server-15.tower-21.messagelabs.com!1346492557!14381786!1 X-Originating-IP: [65.55.111.87] X-SpamReason: No, hits=0.2 required=7.0 tests=FORGED_HOTMAIL_RCVD, HTML_30_40,HTML_MESSAGE,ML_RADAR_SPEW_LINKS_12,UPPERCASE_25_50, spamassassin: X-StarScan-Received: X-StarScan-Version: 6.6.1.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 27450 invoked from network); 1 Sep 2012 09:42:37 -0000 Received: from blu0-omc2-s12.blu0.hotmail.com (HELO blu0-omc2-s12.blu0.hotmail.com) (65.55.111.87) by server-15.tower-21.messagelabs.com with SMTP; 1 Sep 2012 09:42:37 -0000 Received: from BLU171-W49 ([65.55.111.72]) by blu0-omc2-s12.blu0.hotmail.com with Microsoft SMTPSVC(6.0.3790.4675); Sat, 1 Sep 2012 02:42:37 -0700 Message-ID: X-Originating-IP: [49.207.233.129] From: Riyan S To: Date: Sat, 1 Sep 2012 15:12:37 +0530 Importance: Normal MIME-Version: 1.0 X-OriginalArrivalTime: 01 Sep 2012 09:42:37.0615 (UTC) FILETIME=[1F233BF0:01CD8826] Subject: [Xen-users] X taking 100 % cpu on Xen dom0 X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============6878644681257645647==" Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org --===============6878644681257645647== Content-Type: multipart/alternative; boundary="_9459b54c-c833-41b4-b596-0fac1a5b4119_" --_9459b54c-c833-41b4-b596-0fac1a5b4119_ Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Hi=2C I am trying to get X to work on Xen Dom0 running a custom 3.4.10 kernel. wi= th a Nvidia Gt220 card + 295.59 drivers.Although=2Cthe drivers get loaded a= nd X starts=2Cbut after some time its seems to get stuck in some kind of in= finite loop and starts taking up 100 % cpu. This is observed only when i b= oot up the machine with the Xen hypervisor=2Cotherwise X works well with ou= t the hypervisor being involved.=20 Is the Xen hypervisor which is acting up or is it the Nvidia drivers ? I do= nt see anything suspicious in dmesg or Xorg.0.log=2Cthe only error i see is= from kdm in var log messages. Os: Centos6.3 Xen hypervisor - 4.1.3 # Xorg -version X.Org X Server 1.10.6Release Date: 2012-02-10X Protocol Version 11=2C Revis= ion 0 # Grub title CentOS (3.4.10-custom2-Xen) root (hd0=2C0) kerne= l /xen.gz dom0_mem=3D4096M iommu=3Don iommu=3Dverbose module /vmlinu= z-3.4.10-custom2 ro root=3D/dev/mapper/vg_livecd-lv_root rd_NO_LUKS LANG=3D= en_US.UTF-8 rd_LVM_LV=3Dvg_livecd/lv_swap rd_NO_MD rd_LVM_LV=3Dvg_livecd/lv= _root SYSFONT=3Dlatarcyrheb-sun16 crashkernel=3Dauto KEYBOARDTYPE=3Dpc KEY= TABLE=3Dus rd_NO_DM rhgb quiet module /initramfs-3.4.10-custom2.img # /var/log/messages ep 1 10:43:36 localhost acpid: client 24735[0:0] has disconnectedSep 1 10= :43:36 localhost acpid: client connected from 25254[0:0]Sep 1 10:43:36 loc= alhost acpid: 1 client rule loadedSep 1 10:43:53 localhost kdm[25248]: X s= erver startup timeout=2C terminatingSep 1 10:44:23 localhost kdm[25248]: X= server termination timeout=2C killingSep 1 10:44:33 localhost kdm[25248]:= X server is stuck in D state=3B leaving it aloneSep 1 10:44:33 localhost = kdm[25248]: X server for display :0 cannot be started=2C session disabled # xm dmesg (XEN) domain.c:655:d0 Attempt to change CR4 flags 00002660 -> 000026e0(XEN)= domain.c:655:d0 Attempt to change CR4 flags 00002660 -> 000026e0(XEN) doma= in.c:655:d0 Attempt to change CR4 flags 00002660 -> 000026e0(XEN) domain.c:= 655:d0 Attempt to change CR4 flags 00002660 -> 000026e0(XEN) domain.c:655:d= 0 Attempt to change CR4 flags 00002660 -> 000026e0 # Dom0 Kernel config # zgrep -i xen /proc/config.gzCONFIG_XEN=3DyCONFIG_XEN_DOM0=3DyCONFIG_XEN_P= RIVILEGED_GUEST=3DyCONFIG_XEN_PVHVM=3DyCONFIG_XEN_MAX_DOMAIN_MEMORY=3D500CO= NFIG_XEN_SAVE_RESTORE=3Dy# CONFIG_XEN_DEBUG_FS is not setCONFIG_PCI_XEN=3Dy= CONFIG_XEN_PCIDEV_FRONTEND=3DyCONFIG_XEN_BLKDEV_FRONTEND=3DyCONFIG_XEN_BLKD= EV_BACKEND=3DyCONFIG_NETXEN_NIC=3DmCONFIG_XEN_NETDEV_FRONTEND=3DyCONFIG_XEN= _NETDEV_BACKEND=3DmCONFIG_INPUT_XEN_KBDDEV_FRONTEND=3DyCONFIG_HVC_XEN=3DyCO= NFIG_HVC_XEN_FRONTEND=3Dy# CONFIG_XEN_WDT is not setCONFIG_XEN_FBDEV_FRONTE= ND=3Dy# Xen driver supportCONFIG_XEN_BALLOON=3Dy# CONFIG_XEN_BALLOON_MEMORY= _HOTPLUG is not setCONFIG_XEN_SCRUB_PAGES=3DyCONFIG_XEN_DEV_EVTCHN=3DyCONFI= G_XEN_BACKEND=3DyCONFIG_XENFS=3DyCONFIG_XEN_COMPAT_XENFS=3DyCONFIG_XEN_SYS_= HYPERVISOR=3DyCONFIG_XEN_XENBUS_FRONTEND=3DyCONFIG_XEN_GNTDEV=3DyCONFIG_XEN= _GRANT_DEV_ALLOC=3DmCONFIG_SWIOTLB_XEN=3DyCONFIG_XEN_PCIDEV_BACKEND=3DmCONF= IG_XEN_PRIVCMD=3Dy# CONFIG_XEN_ACPI_PROCESSOR is not set = --_9459b54c-c833-41b4-b596-0fac1a5b4119_ Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable
Hi=2C

I am trying to get X to work on Xen Dom0 running a= custom 3.4.10 kernel. with a Nvidia Gt220 card + 295.59 drivers.Although= =2Cthe drivers get loaded and X starts=2Cbut after some time its seems to g= et stuck in some kind of infinite  =3Bloop and starts taking up 100 % c= pu. This is observed only when i boot up the machine with the Xen hyperviso= r=2Cotherwise X works well with out the hypervisor being involved. =3B<= /div>

Is the Xen hypervisor which is acting up or is it = the Nvidia drivers ? I dont see anything suspicious in dmesg or Xorg.0.log= =2Cthe only error i see is from kdm in var log messages.


Os: Centos6.3

= Xen hypervisor - 4.1.3

# Xorg -version

X.Org X Server 1.10.6
Release Da= te: 2012-02-10
X Protocol Version 11=2C Revision 0

# Grub =3B
title CentOS (3.4.10-= custom2-Xen)
 =3B  =3B  =3B  =3B root (hd0=2C0)
 =3B  =3B  =3B  =3B kernel /xen.gz dom0_mem=3D4096= M iommu=3Don iommu=3Dverbose
 =3B  =3B  =3B  =3B = module /vmlinuz-3.4.10-custom2 ro root=3D/dev/mapper/vg_livecd-lv_root rd_N= O_LUKS LANG=3Den_US.UTF-8 rd_LVM_LV=3Dvg_livecd/lv_swap rd_NO_MD rd_LVM_LV= =3Dvg_livecd/lv_root SYSFONT=3Dlatarcyrheb-sun16 crashkernel=3Dauto  = =3BKEYBOARDTYPE=3Dpc KEYTABLE=3Dus rd_NO_DM rhgb quiet
 =3B &= nbsp=3B  =3B  =3B module /initramfs-3.4.10-custom2.img
<= div>
# /var/log/messages

ep  =3B1 10:43:36 localhost acpid: client 24735[0:0] has disconnected<= /div>
Sep  =3B1 10:43:36 localhost acpid: client connected from 252= 54[0:0]
Sep  =3B1 10:43:36 localhost acpid: 1 client rule loa= ded
Sep  =3B1 10:43:53 localhost kdm[25248]: X server startup= timeout=2C terminating
Sep  =3B1 10:44:23 localhost kdm[2524= 8]: X server termination timeout=2C killing
Sep  =3B1 10:44:3= 3 localhost kdm[25248]: X server is stuck in D state=3B leaving it alone
Sep  =3B1 10:44:33 localhost kdm[25248]: X server for display := 0 cannot be started=2C session disabled

#= xm dmesg

(XEN) domain.c:655:d0 Attempt t= o change CR4 flags 00002660 ->=3B 000026e0
(XEN) domain.c:655:d= 0 Attempt to change CR4 flags 00002660 ->=3B 000026e0
(XEN) dom= ain.c:655:d0 Attempt to change CR4 flags 00002660 ->=3B 000026e0
(XEN) domain.c:655:d0 Attempt to change CR4 flags 00002660 ->=3B 000026= e0
(XEN) domain.c:655:d0 Attempt to change CR4 flags 00002660 -&g= t=3B 000026e0

# Dom0 Kernel config=

# zgrep -i xen /proc/config.gz
CONFIG_XEN=3Dy
CONFIG_XEN_DOM0=3Dy
CONFIG_XEN_P= RIVILEGED_GUEST=3Dy
CONFIG_XEN_PVHVM=3Dy
CONFIG_XEN_MAX= _DOMAIN_MEMORY=3D500
CONFIG_XEN_SAVE_RESTORE=3Dy
# CONF= IG_XEN_DEBUG_FS is not set
CONFIG_PCI_XEN=3Dy
CONFIG_XE= N_PCIDEV_FRONTEND=3Dy
CONFIG_XEN_BLKDEV_FRONTEND=3Dy
CO= NFIG_XEN_BLKDEV_BACKEND=3Dy
CONFIG_NETXEN_NIC=3Dm
CONFI= G_XEN_NETDEV_FRONTEND=3Dy
CONFIG_XEN_NETDEV_BACKEND=3Dm
CONFIG_INPUT_XEN_KBDDEV_FRONTEND=3Dy
CONFIG_HVC_XEN=3Dy
CONFIG_HVC_XEN_FRONTEND=3Dy
# CONFIG_XEN_WDT is not set
CONFIG_XEN_FBDEV_FRONTEND=3Dy
# Xen driver support
C= ONFIG_XEN_BALLOON=3Dy
# CONFIG_XEN_BALLOON_MEMORY_HOTPLUG is not = set
CONFIG_XEN_SCRUB_PAGES=3Dy
CONFIG_XEN_DEV_EVTCHN=3D= y
CONFIG_XEN_BACKEND=3Dy
CONFIG_XENFS=3Dy
CON= FIG_XEN_COMPAT_XENFS=3Dy
CONFIG_XEN_SYS_HYPERVISOR=3Dy
= CONFIG_XEN_XENBUS_FRONTEND=3Dy
CONFIG_XEN_GNTDEV=3Dy
CO= NFIG_XEN_GRANT_DEV_ALLOC=3Dm
CONFIG_SWIOTLB_XEN=3Dy
CON= FIG_XEN_PCIDEV_BACKEND=3Dm
CONFIG_XEN_PRIVCMD=3Dy
# CON= FIG_XEN_ACPI_PROCESSOR is not set
= --_9459b54c-c833-41b4-b596-0fac1a5b4119_-- --===============6878644681257645647== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users --===============6878644681257645647==-- From xen-users-bounces@lists.xen.org Sat Sep 01 09:44:08 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Sat, 01 Sep 2012 09:44:08 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1T7kDy-00086h-Vm; Sat, 01 Sep 2012 09:42:42 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1T7kDx-00086c-FD for xen-users@lists.xen.org; Sat, 01 Sep 2012 09:42:41 +0000 Received: from [85.158.143.35:59082] by server-2.bemta-4.messagelabs.com id 20/76-21239-098D1405; Sat, 01 Sep 2012 09:42:40 +0000 X-Env-Sender: tesla.coil@live.com X-Msg-Ref: server-15.tower-21.messagelabs.com!1346492557!14381786!1 X-Originating-IP: [65.55.111.87] X-SpamReason: No, hits=0.2 required=7.0 tests=FORGED_HOTMAIL_RCVD, HTML_30_40,HTML_MESSAGE,ML_RADAR_SPEW_LINKS_12,UPPERCASE_25_50, spamassassin: X-StarScan-Received: X-StarScan-Version: 6.6.1.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 27450 invoked from network); 1 Sep 2012 09:42:37 -0000 Received: from blu0-omc2-s12.blu0.hotmail.com (HELO blu0-omc2-s12.blu0.hotmail.com) (65.55.111.87) by server-15.tower-21.messagelabs.com with SMTP; 1 Sep 2012 09:42:37 -0000 Received: from BLU171-W49 ([65.55.111.72]) by blu0-omc2-s12.blu0.hotmail.com with Microsoft SMTPSVC(6.0.3790.4675); Sat, 1 Sep 2012 02:42:37 -0700 Message-ID: X-Originating-IP: [49.207.233.129] From: Riyan S To: Date: Sat, 1 Sep 2012 15:12:37 +0530 Importance: Normal MIME-Version: 1.0 X-OriginalArrivalTime: 01 Sep 2012 09:42:37.0615 (UTC) FILETIME=[1F233BF0:01CD8826] Subject: [Xen-users] X taking 100 % cpu on Xen dom0 X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============6878644681257645647==" Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org --===============6878644681257645647== Content-Type: multipart/alternative; boundary="_9459b54c-c833-41b4-b596-0fac1a5b4119_" --_9459b54c-c833-41b4-b596-0fac1a5b4119_ Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Hi=2C I am trying to get X to work on Xen Dom0 running a custom 3.4.10 kernel. wi= th a Nvidia Gt220 card + 295.59 drivers.Although=2Cthe drivers get loaded a= nd X starts=2Cbut after some time its seems to get stuck in some kind of in= finite loop and starts taking up 100 % cpu. This is observed only when i b= oot up the machine with the Xen hypervisor=2Cotherwise X works well with ou= t the hypervisor being involved.=20 Is the Xen hypervisor which is acting up or is it the Nvidia drivers ? I do= nt see anything suspicious in dmesg or Xorg.0.log=2Cthe only error i see is= from kdm in var log messages. Os: Centos6.3 Xen hypervisor - 4.1.3 # Xorg -version X.Org X Server 1.10.6Release Date: 2012-02-10X Protocol Version 11=2C Revis= ion 0 # Grub title CentOS (3.4.10-custom2-Xen) root (hd0=2C0) kerne= l /xen.gz dom0_mem=3D4096M iommu=3Don iommu=3Dverbose module /vmlinu= z-3.4.10-custom2 ro root=3D/dev/mapper/vg_livecd-lv_root rd_NO_LUKS LANG=3D= en_US.UTF-8 rd_LVM_LV=3Dvg_livecd/lv_swap rd_NO_MD rd_LVM_LV=3Dvg_livecd/lv= _root SYSFONT=3Dlatarcyrheb-sun16 crashkernel=3Dauto KEYBOARDTYPE=3Dpc KEY= TABLE=3Dus rd_NO_DM rhgb quiet module /initramfs-3.4.10-custom2.img # /var/log/messages ep 1 10:43:36 localhost acpid: client 24735[0:0] has disconnectedSep 1 10= :43:36 localhost acpid: client connected from 25254[0:0]Sep 1 10:43:36 loc= alhost acpid: 1 client rule loadedSep 1 10:43:53 localhost kdm[25248]: X s= erver startup timeout=2C terminatingSep 1 10:44:23 localhost kdm[25248]: X= server termination timeout=2C killingSep 1 10:44:33 localhost kdm[25248]:= X server is stuck in D state=3B leaving it aloneSep 1 10:44:33 localhost = kdm[25248]: X server for display :0 cannot be started=2C session disabled # xm dmesg (XEN) domain.c:655:d0 Attempt to change CR4 flags 00002660 -> 000026e0(XEN)= domain.c:655:d0 Attempt to change CR4 flags 00002660 -> 000026e0(XEN) doma= in.c:655:d0 Attempt to change CR4 flags 00002660 -> 000026e0(XEN) domain.c:= 655:d0 Attempt to change CR4 flags 00002660 -> 000026e0(XEN) domain.c:655:d= 0 Attempt to change CR4 flags 00002660 -> 000026e0 # Dom0 Kernel config # zgrep -i xen /proc/config.gzCONFIG_XEN=3DyCONFIG_XEN_DOM0=3DyCONFIG_XEN_P= RIVILEGED_GUEST=3DyCONFIG_XEN_PVHVM=3DyCONFIG_XEN_MAX_DOMAIN_MEMORY=3D500CO= NFIG_XEN_SAVE_RESTORE=3Dy# CONFIG_XEN_DEBUG_FS is not setCONFIG_PCI_XEN=3Dy= CONFIG_XEN_PCIDEV_FRONTEND=3DyCONFIG_XEN_BLKDEV_FRONTEND=3DyCONFIG_XEN_BLKD= EV_BACKEND=3DyCONFIG_NETXEN_NIC=3DmCONFIG_XEN_NETDEV_FRONTEND=3DyCONFIG_XEN= _NETDEV_BACKEND=3DmCONFIG_INPUT_XEN_KBDDEV_FRONTEND=3DyCONFIG_HVC_XEN=3DyCO= NFIG_HVC_XEN_FRONTEND=3Dy# CONFIG_XEN_WDT is not setCONFIG_XEN_FBDEV_FRONTE= ND=3Dy# Xen driver supportCONFIG_XEN_BALLOON=3Dy# CONFIG_XEN_BALLOON_MEMORY= _HOTPLUG is not setCONFIG_XEN_SCRUB_PAGES=3DyCONFIG_XEN_DEV_EVTCHN=3DyCONFI= G_XEN_BACKEND=3DyCONFIG_XENFS=3DyCONFIG_XEN_COMPAT_XENFS=3DyCONFIG_XEN_SYS_= HYPERVISOR=3DyCONFIG_XEN_XENBUS_FRONTEND=3DyCONFIG_XEN_GNTDEV=3DyCONFIG_XEN= _GRANT_DEV_ALLOC=3DmCONFIG_SWIOTLB_XEN=3DyCONFIG_XEN_PCIDEV_BACKEND=3DmCONF= IG_XEN_PRIVCMD=3Dy# CONFIG_XEN_ACPI_PROCESSOR is not set = --_9459b54c-c833-41b4-b596-0fac1a5b4119_ Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable
Hi=2C

I am trying to get X to work on Xen Dom0 running a= custom 3.4.10 kernel. with a Nvidia Gt220 card + 295.59 drivers.Although= =2Cthe drivers get loaded and X starts=2Cbut after some time its seems to g= et stuck in some kind of infinite  =3Bloop and starts taking up 100 % c= pu. This is observed only when i boot up the machine with the Xen hyperviso= r=2Cotherwise X works well with out the hypervisor being involved. =3B<= /div>

Is the Xen hypervisor which is acting up or is it = the Nvidia drivers ? I dont see anything suspicious in dmesg or Xorg.0.log= =2Cthe only error i see is from kdm in var log messages.


Os: Centos6.3

= Xen hypervisor - 4.1.3

# Xorg -version

X.Org X Server 1.10.6
Release Da= te: 2012-02-10
X Protocol Version 11=2C Revision 0

# Grub =3B
title CentOS (3.4.10-= custom2-Xen)
 =3B  =3B  =3B  =3B root (hd0=2C0)
 =3B  =3B  =3B  =3B kernel /xen.gz dom0_mem=3D4096= M iommu=3Don iommu=3Dverbose
 =3B  =3B  =3B  =3B = module /vmlinuz-3.4.10-custom2 ro root=3D/dev/mapper/vg_livecd-lv_root rd_N= O_LUKS LANG=3Den_US.UTF-8 rd_LVM_LV=3Dvg_livecd/lv_swap rd_NO_MD rd_LVM_LV= =3Dvg_livecd/lv_root SYSFONT=3Dlatarcyrheb-sun16 crashkernel=3Dauto  = =3BKEYBOARDTYPE=3Dpc KEYTABLE=3Dus rd_NO_DM rhgb quiet
 =3B &= nbsp=3B  =3B  =3B module /initramfs-3.4.10-custom2.img
<= div>
# /var/log/messages

ep  =3B1 10:43:36 localhost acpid: client 24735[0:0] has disconnected<= /div>
Sep  =3B1 10:43:36 localhost acpid: client connected from 252= 54[0:0]
Sep  =3B1 10:43:36 localhost acpid: 1 client rule loa= ded
Sep  =3B1 10:43:53 localhost kdm[25248]: X server startup= timeout=2C terminating
Sep  =3B1 10:44:23 localhost kdm[2524= 8]: X server termination timeout=2C killing
Sep  =3B1 10:44:3= 3 localhost kdm[25248]: X server is stuck in D state=3B leaving it alone
Sep  =3B1 10:44:33 localhost kdm[25248]: X server for display := 0 cannot be started=2C session disabled

#= xm dmesg

(XEN) domain.c:655:d0 Attempt t= o change CR4 flags 00002660 ->=3B 000026e0
(XEN) domain.c:655:d= 0 Attempt to change CR4 flags 00002660 ->=3B 000026e0
(XEN) dom= ain.c:655:d0 Attempt to change CR4 flags 00002660 ->=3B 000026e0
(XEN) domain.c:655:d0 Attempt to change CR4 flags 00002660 ->=3B 000026= e0
(XEN) domain.c:655:d0 Attempt to change CR4 flags 00002660 -&g= t=3B 000026e0

# Dom0 Kernel config=

# zgrep -i xen /proc/config.gz
CONFIG_XEN=3Dy
CONFIG_XEN_DOM0=3Dy
CONFIG_XEN_P= RIVILEGED_GUEST=3Dy
CONFIG_XEN_PVHVM=3Dy
CONFIG_XEN_MAX= _DOMAIN_MEMORY=3D500
CONFIG_XEN_SAVE_RESTORE=3Dy
# CONF= IG_XEN_DEBUG_FS is not set
CONFIG_PCI_XEN=3Dy
CONFIG_XE= N_PCIDEV_FRONTEND=3Dy
CONFIG_XEN_BLKDEV_FRONTEND=3Dy
CO= NFIG_XEN_BLKDEV_BACKEND=3Dy
CONFIG_NETXEN_NIC=3Dm
CONFI= G_XEN_NETDEV_FRONTEND=3Dy
CONFIG_XEN_NETDEV_BACKEND=3Dm
CONFIG_INPUT_XEN_KBDDEV_FRONTEND=3Dy
CONFIG_HVC_XEN=3Dy
CONFIG_HVC_XEN_FRONTEND=3Dy
# CONFIG_XEN_WDT is not set
CONFIG_XEN_FBDEV_FRONTEND=3Dy
# Xen driver support
C= ONFIG_XEN_BALLOON=3Dy
# CONFIG_XEN_BALLOON_MEMORY_HOTPLUG is not = set
CONFIG_XEN_SCRUB_PAGES=3Dy
CONFIG_XEN_DEV_EVTCHN=3D= y
CONFIG_XEN_BACKEND=3Dy
CONFIG_XENFS=3Dy
CON= FIG_XEN_COMPAT_XENFS=3Dy
CONFIG_XEN_SYS_HYPERVISOR=3Dy
= CONFIG_XEN_XENBUS_FRONTEND=3Dy
CONFIG_XEN_GNTDEV=3Dy
CO= NFIG_XEN_GRANT_DEV_ALLOC=3Dm
CONFIG_SWIOTLB_XEN=3Dy
CON= FIG_XEN_PCIDEV_BACKEND=3Dm
CONFIG_XEN_PRIVCMD=3Dy
# CON= FIG_XEN_ACPI_PROCESSOR is not set
= --_9459b54c-c833-41b4-b596-0fac1a5b4119_-- --===============6878644681257645647== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users --===============6878644681257645647==-- From xen-users-bounces@lists.xen.org Sun Sep 02 01:13:09 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Sun, 02 Sep 2012 01:13:09 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1T7yio-0002UA-4a; Sun, 02 Sep 2012 01:11:30 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1T7xVu-0004LV-Vt for xen-users@lists.xen.org; Sat, 01 Sep 2012 23:54:07 +0000 Received: from [85.158.143.99:29763] by server-1.bemta-4.messagelabs.com id 50/AB-12504-E10A2405; Sat, 01 Sep 2012 23:54:06 +0000 X-Env-Sender: jasonkobrien@gmail.com X-Msg-Ref: server-11.tower-216.messagelabs.com!1346543644!20493594!1 X-Originating-IP: [209.85.214.45] X-SpamReason: No, hits=0.3 required=7.0 tests=RCVD_BY_IP X-StarScan-Received: X-StarScan-Version: 6.6.1.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 25932 invoked from network); 1 Sep 2012 23:54:04 -0000 Received: from mail-bk0-f45.google.com (HELO mail-bk0-f45.google.com) (209.85.214.45) by server-11.tower-216.messagelabs.com with RC4-SHA encrypted SMTP; 1 Sep 2012 23:54:04 -0000 Received: by bkcji1 with SMTP id ji1so1762151bkc.32 for ; Sat, 01 Sep 2012 16:54:03 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:date:x-google-sender-auth:message-id:subject :from:to:content-type; bh=0fZha30nbJ1kV1MuhTz6bmlupWpeRn/d04nhFGOkzFE=; b=0mraWo8GP7BI8lVilHfcb6bQveeHTIsvt2OZYvVqxTWzy95ScL5xR421s4KP5HY5UD vx6A0SP8N6hQk7CIqvMTuTa5XnLpQt/CcaFNmOTh/abTE/X/eqDaJ0JWXfkJMmuyhoC+ VvJHfpRduTpYAf/oN8hvNRZRS9DA+HJZaDrWYpC2rx1ts9REUfJjlVpx6vZj9OUDB8DL ZIq3BcWvpCiMgZ4BhRIeLN0mX9L/5oIW1TlG3n/fkT126UQCTwCuDu0UaCPOJmk231uX XJJ11amPRqgdZXHEDR5IxIBUXobudU8uhuYYWP1ktaxt66vNAJDJ/rvMGlyK76R3UYz8 Ek4w== MIME-Version: 1.0 Received: by 10.204.136.205 with SMTP id s13mr5517107bkt.22.1346543643742; Sat, 01 Sep 2012 16:54:03 -0700 (PDT) Received: by 10.205.33.10 with HTTP; Sat, 1 Sep 2012 16:54:03 -0700 (PDT) Date: Sat, 1 Sep 2012 19:54:03 -0400 X-Google-Sender-Auth: DFTlumKvd7Y3VjaUfpeHy0CIZI8 Message-ID: From: "Jason O'Brien" To: xen-users@lists.xen.org X-Mailman-Approved-At: Sun, 02 Sep 2012 01:11:28 +0000 Subject: [Xen-users] Can't pass through onboard Intel HDA, works in KVM X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org With the kernel option 'xen-pciback.hide=(00:14.2) xen-pciback.permissive', Xen-4.2.0-rc3 is unable to pass through my onboard Intel HDA audio adapter to a Windows7 guest. I tried doing the same in KVM and it worked immediately without issue. On the guest, I get a "High Definition Audio Controller" with the correct vendor/device ID, and an error of "This device cannot start. (Code 10)". I've tried a bunch of combinations, including late binding to pciback, with no luck. Has anyone seen this before? It seems to be the only thing that won't work.. secondary passthrough of my AMD HD6850 in Xen works great (but not in KVM unfortunately), as does passing through the USB controllers. There's another google hit for a guy with a similar problem, but it turned out he was using pci-stub instead of pciback (which, as the below info shows, I am not). Thanks for your time, Jason Relevant info: [jason@virt-host ~]$ dmesg | grep '14\.2' ... [ 3.863511] pciback 0000:00:14.2: seizing device [ 5.081737] xen-pciback: backend is vpci [ 239.702436] xen-pciback: vpci: 0000:00:14.2: assign to virtual slot 0 [jason@virt-host ~]$ cat /var/log/xen/qemu-dm-Windows7.log ... dm-command: hot insert pass-through pci dev register_real_device: Assigning real physical device 00:14.2 ... register_real_device: Disable MSI translation via per device option register_real_device: Disable power management pt_iomul_init: Error: pt_iomul_init can't open file /dev/xen/pci_iomul: No such file or directory: 0x0:0x14.0x2 pt_register_regions: IO region registered (size=0x00004000 base_addr=0xfeb00004) pci_intx: intx=1 register_real_device: Real physical device 00:14.2 registered successfuly! IRQ type = INTx ... [jason@virt-host ~]$ lspci -tv -[0000:00]-+-00.0 ATI Technologies Inc RD890 PCI to PCI bridge (external gfx0 port B) +-00.2 ATI Technologies Inc Device 5a23 +-02.0-[01]--+-00.0 ATI Technologies Inc Barts XT [ATI Radeon HD 6800 Series] | \-00.1 ATI Technologies Inc Barts HDMI Audio [Radeon HD 6800 Series] +-04.0-[02]----00.0 Realtek Semiconductor Co., Ltd. RTL8111/8168B PCI Express Gigabit Ethernet controller +-07.0-[03]----00.0 ASMedia Technology Inc. ASM1042 SuperSpeed USB Host Controller +-11.0 ATI Technologies Inc SB7x0/SB8x0/SB9x0 SATA Controller [AHCI mode] +-12.0 ATI Technologies Inc SB7x0/SB8x0/SB9x0 USB OHCI0 Controller +-12.2 ATI Technologies Inc SB7x0/SB8x0/SB9x0 USB EHCI Controller +-13.0 ATI Technologies Inc SB7x0/SB8x0/SB9x0 USB OHCI0 Controller +-13.2 ATI Technologies Inc SB7x0/SB8x0/SB9x0 USB EHCI Controller +-14.0 ATI Technologies Inc SBx00 SMBus Controller +-14.2 ATI Technologies Inc SBx00 Azalia (Intel HDA) +-14.3 ATI Technologies Inc SB7x0/SB8x0/SB9x0 LPC host controller +-14.4-[04]-- +-14.5 ATI Technologies Inc SB7x0/SB8x0/SB9x0 USB OHCI2 Controller +-16.0 ATI Technologies Inc SB7x0/SB8x0/SB9x0 USB OHCI0 Controller +-16.2 ATI Technologies Inc SB7x0/SB8x0/SB9x0 USB EHCI Controller +-18.0 Advanced Micro Devices [AMD] Family 10h Processor HyperTransport Configuration +-18.1 Advanced Micro Devices [AMD] Family 10h Processor Address Map +-18.2 Advanced Micro Devices [AMD] Family 10h Processor DRAM Controller +-18.3 Advanced Micro Devices [AMD] Family 10h Processor Miscellaneous Control \-18.4 Advanced Micro Devices [AMD] Family 10h Processor Link Control [jason@virt-host ~]$ lspci -kn | grep -A2 '14\.2' 00:14.2 0403: 1002:4383 (rev 40) Subsystem: 1043:8444 Kernel driver in use: pciback _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Sun Sep 02 01:13:09 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Sun, 02 Sep 2012 01:13:09 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1T7yio-0002UA-4a; Sun, 02 Sep 2012 01:11:30 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1T7xVu-0004LV-Vt for xen-users@lists.xen.org; Sat, 01 Sep 2012 23:54:07 +0000 Received: from [85.158.143.99:29763] by server-1.bemta-4.messagelabs.com id 50/AB-12504-E10A2405; Sat, 01 Sep 2012 23:54:06 +0000 X-Env-Sender: jasonkobrien@gmail.com X-Msg-Ref: server-11.tower-216.messagelabs.com!1346543644!20493594!1 X-Originating-IP: [209.85.214.45] X-SpamReason: No, hits=0.3 required=7.0 tests=RCVD_BY_IP X-StarScan-Received: X-StarScan-Version: 6.6.1.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 25932 invoked from network); 1 Sep 2012 23:54:04 -0000 Received: from mail-bk0-f45.google.com (HELO mail-bk0-f45.google.com) (209.85.214.45) by server-11.tower-216.messagelabs.com with RC4-SHA encrypted SMTP; 1 Sep 2012 23:54:04 -0000 Received: by bkcji1 with SMTP id ji1so1762151bkc.32 for ; Sat, 01 Sep 2012 16:54:03 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:date:x-google-sender-auth:message-id:subject :from:to:content-type; bh=0fZha30nbJ1kV1MuhTz6bmlupWpeRn/d04nhFGOkzFE=; b=0mraWo8GP7BI8lVilHfcb6bQveeHTIsvt2OZYvVqxTWzy95ScL5xR421s4KP5HY5UD vx6A0SP8N6hQk7CIqvMTuTa5XnLpQt/CcaFNmOTh/abTE/X/eqDaJ0JWXfkJMmuyhoC+ VvJHfpRduTpYAf/oN8hvNRZRS9DA+HJZaDrWYpC2rx1ts9REUfJjlVpx6vZj9OUDB8DL ZIq3BcWvpCiMgZ4BhRIeLN0mX9L/5oIW1TlG3n/fkT126UQCTwCuDu0UaCPOJmk231uX XJJ11amPRqgdZXHEDR5IxIBUXobudU8uhuYYWP1ktaxt66vNAJDJ/rvMGlyK76R3UYz8 Ek4w== MIME-Version: 1.0 Received: by 10.204.136.205 with SMTP id s13mr5517107bkt.22.1346543643742; Sat, 01 Sep 2012 16:54:03 -0700 (PDT) Received: by 10.205.33.10 with HTTP; Sat, 1 Sep 2012 16:54:03 -0700 (PDT) Date: Sat, 1 Sep 2012 19:54:03 -0400 X-Google-Sender-Auth: DFTlumKvd7Y3VjaUfpeHy0CIZI8 Message-ID: From: "Jason O'Brien" To: xen-users@lists.xen.org X-Mailman-Approved-At: Sun, 02 Sep 2012 01:11:28 +0000 Subject: [Xen-users] Can't pass through onboard Intel HDA, works in KVM X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org With the kernel option 'xen-pciback.hide=(00:14.2) xen-pciback.permissive', Xen-4.2.0-rc3 is unable to pass through my onboard Intel HDA audio adapter to a Windows7 guest. I tried doing the same in KVM and it worked immediately without issue. On the guest, I get a "High Definition Audio Controller" with the correct vendor/device ID, and an error of "This device cannot start. (Code 10)". I've tried a bunch of combinations, including late binding to pciback, with no luck. Has anyone seen this before? It seems to be the only thing that won't work.. secondary passthrough of my AMD HD6850 in Xen works great (but not in KVM unfortunately), as does passing through the USB controllers. There's another google hit for a guy with a similar problem, but it turned out he was using pci-stub instead of pciback (which, as the below info shows, I am not). Thanks for your time, Jason Relevant info: [jason@virt-host ~]$ dmesg | grep '14\.2' ... [ 3.863511] pciback 0000:00:14.2: seizing device [ 5.081737] xen-pciback: backend is vpci [ 239.702436] xen-pciback: vpci: 0000:00:14.2: assign to virtual slot 0 [jason@virt-host ~]$ cat /var/log/xen/qemu-dm-Windows7.log ... dm-command: hot insert pass-through pci dev register_real_device: Assigning real physical device 00:14.2 ... register_real_device: Disable MSI translation via per device option register_real_device: Disable power management pt_iomul_init: Error: pt_iomul_init can't open file /dev/xen/pci_iomul: No such file or directory: 0x0:0x14.0x2 pt_register_regions: IO region registered (size=0x00004000 base_addr=0xfeb00004) pci_intx: intx=1 register_real_device: Real physical device 00:14.2 registered successfuly! IRQ type = INTx ... [jason@virt-host ~]$ lspci -tv -[0000:00]-+-00.0 ATI Technologies Inc RD890 PCI to PCI bridge (external gfx0 port B) +-00.2 ATI Technologies Inc Device 5a23 +-02.0-[01]--+-00.0 ATI Technologies Inc Barts XT [ATI Radeon HD 6800 Series] | \-00.1 ATI Technologies Inc Barts HDMI Audio [Radeon HD 6800 Series] +-04.0-[02]----00.0 Realtek Semiconductor Co., Ltd. RTL8111/8168B PCI Express Gigabit Ethernet controller +-07.0-[03]----00.0 ASMedia Technology Inc. ASM1042 SuperSpeed USB Host Controller +-11.0 ATI Technologies Inc SB7x0/SB8x0/SB9x0 SATA Controller [AHCI mode] +-12.0 ATI Technologies Inc SB7x0/SB8x0/SB9x0 USB OHCI0 Controller +-12.2 ATI Technologies Inc SB7x0/SB8x0/SB9x0 USB EHCI Controller +-13.0 ATI Technologies Inc SB7x0/SB8x0/SB9x0 USB OHCI0 Controller +-13.2 ATI Technologies Inc SB7x0/SB8x0/SB9x0 USB EHCI Controller +-14.0 ATI Technologies Inc SBx00 SMBus Controller +-14.2 ATI Technologies Inc SBx00 Azalia (Intel HDA) +-14.3 ATI Technologies Inc SB7x0/SB8x0/SB9x0 LPC host controller +-14.4-[04]-- +-14.5 ATI Technologies Inc SB7x0/SB8x0/SB9x0 USB OHCI2 Controller +-16.0 ATI Technologies Inc SB7x0/SB8x0/SB9x0 USB OHCI0 Controller +-16.2 ATI Technologies Inc SB7x0/SB8x0/SB9x0 USB EHCI Controller +-18.0 Advanced Micro Devices [AMD] Family 10h Processor HyperTransport Configuration +-18.1 Advanced Micro Devices [AMD] Family 10h Processor Address Map +-18.2 Advanced Micro Devices [AMD] Family 10h Processor DRAM Controller +-18.3 Advanced Micro Devices [AMD] Family 10h Processor Miscellaneous Control \-18.4 Advanced Micro Devices [AMD] Family 10h Processor Link Control [jason@virt-host ~]$ lspci -kn | grep -A2 '14\.2' 00:14.2 0403: 1002:4383 (rev 40) Subsystem: 1043:8444 Kernel driver in use: pciback _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Sun Sep 02 04:48:05 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Sun, 02 Sep 2012 04:48:05 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1T824v-0004Ci-0U; Sun, 02 Sep 2012 04:46:33 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1T824u-0004CR-0d for xen-users@lists.xen.org; Sun, 02 Sep 2012 04:46:32 +0000 Received: from [85.158.138.51:64365] by server-7.bemta-3.messagelabs.com id 57/32-32000-6A4E2405; Sun, 02 Sep 2012 04:46:30 +0000 X-Env-Sender: pasik@iki.fi X-Msg-Ref: server-8.tower-174.messagelabs.com!1346561188!28070450!1 X-Originating-IP: [192.89.123.25] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogMTkyLjg5LjEyMy4yNSA9PiA0OTc5Mjk=\n X-StarScan-Received: X-StarScan-Version: 6.6.1.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 2181 invoked from network); 2 Sep 2012 04:46:28 -0000 Received: from smtp.tele.fi (HELO smtp.tele.fi) (192.89.123.25) by server-8.tower-174.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 2 Sep 2012 04:46:28 -0000 X-Originating-Ip: [194.89.68.22] Received: from ydin.reaktio.net (reaktio.net [194.89.68.22]) by smtp.tele.fi (Postfix) with ESMTP id 396F227E6; Sun, 2 Sep 2012 07:46:27 +0300 (EEST) Received: by ydin.reaktio.net (Postfix, from userid 1001) id DD7FD2005D; Sun, 2 Sep 2012 07:46:26 +0300 (EEST) Date: Sun, 2 Sep 2012 07:46:26 +0300 From: Pasi =?iso-8859-1?Q?K=E4rkk=E4inen?= To: Ian Campbell Message-ID: <20120902044626.GE8912@reaktio.net> References: <1346148361.9975.3.camel@zakaz.uk.xensource.com> MIME-Version: 1.0 Content-Disposition: inline In-Reply-To: <1346148361.9975.3.camel@zakaz.uk.xensource.com> User-Agent: Mutt/1.5.20 (2009-06-14) Cc: xen-users , xen-devel Subject: Re: [Xen-users] [Xen-devel] Xen 4.2 TODO / Release Plan X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org On Tue, Aug 28, 2012 at 11:06:01AM +0100, Ian Campbell wrote: > = > * xl.cfg(5) documentation patch for qemu-upstream > videoram/videomem support: > http://lists.xen.org/archives/html/xen-devel/2012-05/msg00250.html > qemu-upstream doesn't support specifying videomem size for the > HVM guest cirrus/stdvga. (but this works with > qemu-xen-traditional). (Pasi K=E4rkk=E4inen) > = Patch sent to the list. -- Pasi _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Sun Sep 02 04:48:05 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Sun, 02 Sep 2012 04:48:05 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1T824v-0004Ci-0U; Sun, 02 Sep 2012 04:46:33 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1T824u-0004CR-0d for xen-users@lists.xen.org; Sun, 02 Sep 2012 04:46:32 +0000 Received: from [85.158.138.51:64365] by server-7.bemta-3.messagelabs.com id 57/32-32000-6A4E2405; Sun, 02 Sep 2012 04:46:30 +0000 X-Env-Sender: pasik@iki.fi X-Msg-Ref: server-8.tower-174.messagelabs.com!1346561188!28070450!1 X-Originating-IP: [192.89.123.25] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogMTkyLjg5LjEyMy4yNSA9PiA0OTc5Mjk=\n X-StarScan-Received: X-StarScan-Version: 6.6.1.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 2181 invoked from network); 2 Sep 2012 04:46:28 -0000 Received: from smtp.tele.fi (HELO smtp.tele.fi) (192.89.123.25) by server-8.tower-174.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 2 Sep 2012 04:46:28 -0000 X-Originating-Ip: [194.89.68.22] Received: from ydin.reaktio.net (reaktio.net [194.89.68.22]) by smtp.tele.fi (Postfix) with ESMTP id 396F227E6; Sun, 2 Sep 2012 07:46:27 +0300 (EEST) Received: by ydin.reaktio.net (Postfix, from userid 1001) id DD7FD2005D; Sun, 2 Sep 2012 07:46:26 +0300 (EEST) Date: Sun, 2 Sep 2012 07:46:26 +0300 From: Pasi =?iso-8859-1?Q?K=E4rkk=E4inen?= To: Ian Campbell Message-ID: <20120902044626.GE8912@reaktio.net> References: <1346148361.9975.3.camel@zakaz.uk.xensource.com> MIME-Version: 1.0 Content-Disposition: inline In-Reply-To: <1346148361.9975.3.camel@zakaz.uk.xensource.com> User-Agent: Mutt/1.5.20 (2009-06-14) Cc: xen-users , xen-devel Subject: Re: [Xen-users] [Xen-devel] Xen 4.2 TODO / Release Plan X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org On Tue, Aug 28, 2012 at 11:06:01AM +0100, Ian Campbell wrote: > = > * xl.cfg(5) documentation patch for qemu-upstream > videoram/videomem support: > http://lists.xen.org/archives/html/xen-devel/2012-05/msg00250.html > qemu-upstream doesn't support specifying videomem size for the > HVM guest cirrus/stdvga. (but this works with > qemu-xen-traditional). (Pasi K=E4rkk=E4inen) > = Patch sent to the list. -- Pasi _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Mon Sep 03 07:55:55 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Mon, 03 Sep 2012 07:55:55 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1T8RUJ-000274-BJ; Mon, 03 Sep 2012 07:54:27 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1T8RUH-00026u-Gv for xen-users@lists.xen.org; Mon, 03 Sep 2012 07:54:25 +0000 Received: from [85.158.143.35:24968] by server-1.bemta-4.messagelabs.com id 18/D5-12504-03264405; Mon, 03 Sep 2012 07:54:24 +0000 X-Env-Sender: thecarrionkind@gmail.com X-Msg-Ref: server-15.tower-21.messagelabs.com!1346658863!14555164!1 X-Originating-IP: [209.85.212.45] X-SpamReason: No, hits=0.3 required=7.0 tests=ML_RADAR_SPEW_LINKS_14, RCVD_BY_IP,spamassassin: X-StarScan-Received: X-StarScan-Version: 6.6.1.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 26359 invoked from network); 3 Sep 2012 07:54:24 -0000 Received: from mail-vb0-f45.google.com (HELO mail-vb0-f45.google.com) (209.85.212.45) by server-15.tower-21.messagelabs.com with RC4-SHA encrypted SMTP; 3 Sep 2012 07:54:24 -0000 Received: by vbip1 with SMTP id p1so6382547vbi.32 for ; Mon, 03 Sep 2012 00:54:22 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:date:message-id:subject:from:to:content-type; bh=VmE6DtFeXranDpon2MvywVrkXjn6lZpOTrR7J/3lRdc=; b=rrAFWOxBBEY3JXlc2cqFAZpvPC5aMhhxKqvCd+K37Dlpb8/Su7HJIBh6CoYNe2nWAQ ko58g1JemNOd7m3V8AzKYEOHM6/+owfUYkgNOyDDFq3T3+dwWzGs1WsglrkfUJg5YqPC j1vbZc7WNDgFcSgbvHTwuBzeyDk4KUR7tRAU9lNM+43+KwfeIgkVVKt0loup+rYksAS2 K408y7Yt46zISw2Pe2BUDq/TA/D68L1k11DSVbxbGDRE4/lJq6PJKpS9ssakGipaKR7S VcMjyFlSvD9HiL8fryvWI5+u/8T2RzRtbMghLRDDSN3a1c7ZOt3PyLbCmgzt9bjb1SlB 8BmQ== MIME-Version: 1.0 Received: by 10.52.67.143 with SMTP id n15mr9183721vdt.34.1346658862851; Mon, 03 Sep 2012 00:54:22 -0700 (PDT) Received: by 10.58.77.144 with HTTP; Mon, 3 Sep 2012 00:54:22 -0700 (PDT) Date: Mon, 3 Sep 2012 09:54:22 +0200 Message-ID: From: Lloyd Dizon To: xen-users@lists.xen.org Subject: [Xen-users] Accessing SSD disks on VM X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org Hi, Do you have suggestions on how to properly access SSD disks? Currently I have a RAID0 on two SSD disks, accessible as /dev/md0. md0 is used as a PV with LVM, on which I have a VG and a LV. The LV is seen as xvda by the VM. I am using the whole LV as a root device for the VM (no partitions). I am seeing up to 25% less performance on the VM when doing IO tests (not sure if I am doing the correct way to test IO). Do you have any suggestions if I can do this configuration better. Thanks. Lloyd IO tests with hdparm: Avg. cached reads xvda: 2586.68 MB/s Avg. cached reads md0: 2654.68 MB/s Difference (cached reads) entre xvda et md0: 97% -> 3% moins rapide sur VM --- Avg. buffered reads xvda: 357.67 MB/s Avg. buffered reads md0: 419.67 MB/s Difference (buffered read) entre xvda et md0: 85% -> 15% moins rapide sur VM IO tests with dd: vm:~ # time dd if=/dev/zero of=/var/tmp/zero.txt bs=1k count=10485760 10485760+0 records in 10485760+0 records out 10737418240 bytes (11 GB) copied, 118.399 s, 90.7 MB/s xen:/mnt/ioaccel_vm/var/tmp # time dd if=/dev/zero of=./zero-phy.txt bs=1k count=10485760 10485760+0 records in 10485760+0 records out 10737418240 bytes (11 GB) copied, 90.4089 s, 119 MB/s _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Mon Sep 03 07:55:55 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Mon, 03 Sep 2012 07:55:55 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1T8RUJ-000274-BJ; Mon, 03 Sep 2012 07:54:27 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1T8RUH-00026u-Gv for xen-users@lists.xen.org; Mon, 03 Sep 2012 07:54:25 +0000 Received: from [85.158.143.35:24968] by server-1.bemta-4.messagelabs.com id 18/D5-12504-03264405; Mon, 03 Sep 2012 07:54:24 +0000 X-Env-Sender: thecarrionkind@gmail.com X-Msg-Ref: server-15.tower-21.messagelabs.com!1346658863!14555164!1 X-Originating-IP: [209.85.212.45] X-SpamReason: No, hits=0.3 required=7.0 tests=ML_RADAR_SPEW_LINKS_14, RCVD_BY_IP,spamassassin: X-StarScan-Received: X-StarScan-Version: 6.6.1.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 26359 invoked from network); 3 Sep 2012 07:54:24 -0000 Received: from mail-vb0-f45.google.com (HELO mail-vb0-f45.google.com) (209.85.212.45) by server-15.tower-21.messagelabs.com with RC4-SHA encrypted SMTP; 3 Sep 2012 07:54:24 -0000 Received: by vbip1 with SMTP id p1so6382547vbi.32 for ; Mon, 03 Sep 2012 00:54:22 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:date:message-id:subject:from:to:content-type; bh=VmE6DtFeXranDpon2MvywVrkXjn6lZpOTrR7J/3lRdc=; b=rrAFWOxBBEY3JXlc2cqFAZpvPC5aMhhxKqvCd+K37Dlpb8/Su7HJIBh6CoYNe2nWAQ ko58g1JemNOd7m3V8AzKYEOHM6/+owfUYkgNOyDDFq3T3+dwWzGs1WsglrkfUJg5YqPC j1vbZc7WNDgFcSgbvHTwuBzeyDk4KUR7tRAU9lNM+43+KwfeIgkVVKt0loup+rYksAS2 K408y7Yt46zISw2Pe2BUDq/TA/D68L1k11DSVbxbGDRE4/lJq6PJKpS9ssakGipaKR7S VcMjyFlSvD9HiL8fryvWI5+u/8T2RzRtbMghLRDDSN3a1c7ZOt3PyLbCmgzt9bjb1SlB 8BmQ== MIME-Version: 1.0 Received: by 10.52.67.143 with SMTP id n15mr9183721vdt.34.1346658862851; Mon, 03 Sep 2012 00:54:22 -0700 (PDT) Received: by 10.58.77.144 with HTTP; Mon, 3 Sep 2012 00:54:22 -0700 (PDT) Date: Mon, 3 Sep 2012 09:54:22 +0200 Message-ID: From: Lloyd Dizon To: xen-users@lists.xen.org Subject: [Xen-users] Accessing SSD disks on VM X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org Hi, Do you have suggestions on how to properly access SSD disks? Currently I have a RAID0 on two SSD disks, accessible as /dev/md0. md0 is used as a PV with LVM, on which I have a VG and a LV. The LV is seen as xvda by the VM. I am using the whole LV as a root device for the VM (no partitions). I am seeing up to 25% less performance on the VM when doing IO tests (not sure if I am doing the correct way to test IO). Do you have any suggestions if I can do this configuration better. Thanks. Lloyd IO tests with hdparm: Avg. cached reads xvda: 2586.68 MB/s Avg. cached reads md0: 2654.68 MB/s Difference (cached reads) entre xvda et md0: 97% -> 3% moins rapide sur VM --- Avg. buffered reads xvda: 357.67 MB/s Avg. buffered reads md0: 419.67 MB/s Difference (buffered read) entre xvda et md0: 85% -> 15% moins rapide sur VM IO tests with dd: vm:~ # time dd if=/dev/zero of=/var/tmp/zero.txt bs=1k count=10485760 10485760+0 records in 10485760+0 records out 10737418240 bytes (11 GB) copied, 118.399 s, 90.7 MB/s xen:/mnt/ioaccel_vm/var/tmp # time dd if=/dev/zero of=./zero-phy.txt bs=1k count=10485760 10485760+0 records in 10485760+0 records out 10737418240 bytes (11 GB) copied, 90.4089 s, 119 MB/s _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Mon Sep 03 08:53:33 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Mon, 03 Sep 2012 08:53:33 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1T8SOE-0003sJ-1V; Mon, 03 Sep 2012 08:52:14 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1T8SOB-0003sA-Vy for xen-users@lists.xen.org; Mon, 03 Sep 2012 08:52:12 +0000 Received: from [85.158.139.83:35341] by server-11.bemta-5.messagelabs.com id 8C/4E-24658-BBF64405; Mon, 03 Sep 2012 08:52:11 +0000 X-Env-Sender: fajar@fajar.net X-Msg-Ref: server-2.tower-182.messagelabs.com!1346662329!28221916!1 X-Originating-IP: [209.85.220.173] X-SpamReason: No, hits=0.3 required=7.0 tests=RCVD_BY_IP X-StarScan-Received: X-StarScan-Version: 6.6.1.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 25350 invoked from network); 3 Sep 2012 08:52:10 -0000 Received: from mail-vc0-f173.google.com (HELO mail-vc0-f173.google.com) (209.85.220.173) by server-2.tower-182.messagelabs.com with RC4-SHA encrypted SMTP; 3 Sep 2012 08:52:10 -0000 Received: by vcbgb23 with SMTP id gb23so6592221vcb.32 for ; Mon, 03 Sep 2012 01:52:09 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:x-gm-message-state; bh=fHioEgm/ThERdJbsAY4XMJa2f0wbXSn1POCkcynUVAU=; b=FNxbkMvVt/bkc7u328VlrbF0njUHSJQMdnJKx7Vd99H6TSopXVUA4LCdttyHVOdTlu fPw7lkU0xrHtmvO6YBiDZ0OKiF+TsQr/JmZ3xRSrb/F14CJz7LzNbezBr4jxp/WoX9Mj ww8II2eYViT5KOZIQDVxVYdmB36O0ZXGF+kK2Wyj55ixWKRwUz2d3VWam9BgEFlnOHCA o8oKLvGrJn2HLcA/dWYja+DXOHvMYXYeh41i8fKsIdBwHs0T9Sm2qw6gs1vfnVivcvXi znxCm9Z983fKiYkMzX5+yKWHiknei+2LFMWSt1YSxygkQSDefRxARmRyvYPQ/fIMOe4H nS3w== MIME-Version: 1.0 Received: by 10.52.24.103 with SMTP id t7mr9375942vdf.84.1346662329172; Mon, 03 Sep 2012 01:52:09 -0700 (PDT) Received: by 10.52.165.165 with HTTP; Mon, 3 Sep 2012 01:52:09 -0700 (PDT) In-Reply-To: References: Date: Mon, 3 Sep 2012 15:52:09 +0700 Message-ID: From: "Fajar A. Nugraha" To: Lloyd Dizon X-Gm-Message-State: ALoCoQmOv3UMviulLcFfkFeJ4Ym7IUtWrFog2UYMCTGKyPsyPbpgRWxnSxDUGQ4/plsbr3O6ZEPV Cc: xen-users@lists.xen.org Subject: Re: [Xen-users] Accessing SSD disks on VM X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org On Mon, Sep 3, 2012 at 2:54 PM, Lloyd Dizon wrote: > Hi, > Do you have suggestions on how to properly access SSD disks? > Currently I have a RAID0 on two SSD disks, accessible as /dev/md0. > md0 is used as a PV with LVM, on which I have a VG and a LV. > The LV is seen as xvda by the VM. I am using the whole LV as a root > device for the VM (no partitions). That works. Although if it's raid0 I'd just use LVM directly without md. Or, since you seem to only use the SSD for the domU anyway, you can pass the SSDs (/dev/sd*) to domU, and do LVM there. > > I am seeing up to 25% less performance on the VM when doing IO tests > (not sure if I am doing the correct way to test IO). Nope :) Your test is basically influenced by cache. IMHO something like bonnie++ or fio (configured with random r/w) is better. And make sure your test size is at least twice the RAM. And there ARE some performance penalty in domU, though I don't know what the "normal" number is nowadays. -- Fajar _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Mon Sep 03 08:53:33 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Mon, 03 Sep 2012 08:53:33 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1T8SOE-0003sJ-1V; Mon, 03 Sep 2012 08:52:14 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1T8SOB-0003sA-Vy for xen-users@lists.xen.org; Mon, 03 Sep 2012 08:52:12 +0000 Received: from [85.158.139.83:35341] by server-11.bemta-5.messagelabs.com id 8C/4E-24658-BBF64405; Mon, 03 Sep 2012 08:52:11 +0000 X-Env-Sender: fajar@fajar.net X-Msg-Ref: server-2.tower-182.messagelabs.com!1346662329!28221916!1 X-Originating-IP: [209.85.220.173] X-SpamReason: No, hits=0.3 required=7.0 tests=RCVD_BY_IP X-StarScan-Received: X-StarScan-Version: 6.6.1.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 25350 invoked from network); 3 Sep 2012 08:52:10 -0000 Received: from mail-vc0-f173.google.com (HELO mail-vc0-f173.google.com) (209.85.220.173) by server-2.tower-182.messagelabs.com with RC4-SHA encrypted SMTP; 3 Sep 2012 08:52:10 -0000 Received: by vcbgb23 with SMTP id gb23so6592221vcb.32 for ; Mon, 03 Sep 2012 01:52:09 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:x-gm-message-state; bh=fHioEgm/ThERdJbsAY4XMJa2f0wbXSn1POCkcynUVAU=; b=FNxbkMvVt/bkc7u328VlrbF0njUHSJQMdnJKx7Vd99H6TSopXVUA4LCdttyHVOdTlu fPw7lkU0xrHtmvO6YBiDZ0OKiF+TsQr/JmZ3xRSrb/F14CJz7LzNbezBr4jxp/WoX9Mj ww8II2eYViT5KOZIQDVxVYdmB36O0ZXGF+kK2Wyj55ixWKRwUz2d3VWam9BgEFlnOHCA o8oKLvGrJn2HLcA/dWYja+DXOHvMYXYeh41i8fKsIdBwHs0T9Sm2qw6gs1vfnVivcvXi znxCm9Z983fKiYkMzX5+yKWHiknei+2LFMWSt1YSxygkQSDefRxARmRyvYPQ/fIMOe4H nS3w== MIME-Version: 1.0 Received: by 10.52.24.103 with SMTP id t7mr9375942vdf.84.1346662329172; Mon, 03 Sep 2012 01:52:09 -0700 (PDT) Received: by 10.52.165.165 with HTTP; Mon, 3 Sep 2012 01:52:09 -0700 (PDT) In-Reply-To: References: Date: Mon, 3 Sep 2012 15:52:09 +0700 Message-ID: From: "Fajar A. Nugraha" To: Lloyd Dizon X-Gm-Message-State: ALoCoQmOv3UMviulLcFfkFeJ4Ym7IUtWrFog2UYMCTGKyPsyPbpgRWxnSxDUGQ4/plsbr3O6ZEPV Cc: xen-users@lists.xen.org Subject: Re: [Xen-users] Accessing SSD disks on VM X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org On Mon, Sep 3, 2012 at 2:54 PM, Lloyd Dizon wrote: > Hi, > Do you have suggestions on how to properly access SSD disks? > Currently I have a RAID0 on two SSD disks, accessible as /dev/md0. > md0 is used as a PV with LVM, on which I have a VG and a LV. > The LV is seen as xvda by the VM. I am using the whole LV as a root > device for the VM (no partitions). That works. Although if it's raid0 I'd just use LVM directly without md. Or, since you seem to only use the SSD for the domU anyway, you can pass the SSDs (/dev/sd*) to domU, and do LVM there. > > I am seeing up to 25% less performance on the VM when doing IO tests > (not sure if I am doing the correct way to test IO). Nope :) Your test is basically influenced by cache. IMHO something like bonnie++ or fio (configured with random r/w) is better. And make sure your test size is at least twice the RAM. And there ARE some performance penalty in domU, though I don't know what the "normal" number is nowadays. -- Fajar _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Mon Sep 03 09:10:31 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Mon, 03 Sep 2012 09:10:31 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1T8Sel-0004th-D3; Mon, 03 Sep 2012 09:09:19 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1T8Sej-0004tE-Er for xen-users@lists.xen.org; Mon, 03 Sep 2012 09:09:17 +0000 Received: from [85.158.143.35:54592] by server-3.bemta-4.messagelabs.com id 29/95-08232-CB374405; Mon, 03 Sep 2012 09:09:16 +0000 X-Env-Sender: Ian.Campbell@citrix.com X-Msg-Ref: server-11.tower-21.messagelabs.com!1346663349!11963754!1 X-Originating-IP: [62.200.22.115] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogNjIuMjAwLjIyLjExNSA9PiAxMTE0ODk=\n X-StarScan-Received: X-StarScan-Version: 6.6.1.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 24455 invoked from network); 3 Sep 2012 09:09:09 -0000 Received: from smtp.eu.citrix.com (HELO SMTP.EU.CITRIX.COM) (62.200.22.115) by server-11.tower-21.messagelabs.com with RC4-SHA encrypted SMTP; 3 Sep 2012 09:09:09 -0000 X-IronPort-AV: E=Sophos;i="4.80,359,1344211200"; d="scan'208";a="14311907" Received: from lonpmailmx01.citrite.net ([10.30.203.162]) by LONPIPO01.EU.CITRIX.COM with ESMTP/TLS/RC4-MD5; 03 Sep 2012 09:09:09 +0000 Received: from [10.80.2.42] (10.80.2.42) by LONPMAILMX01.citrite.net (10.30.203.162) with Microsoft SMTP Server id 8.3.279.1; Mon, 3 Sep 2012 10:09:09 +0100 Message-ID: <1346663347.27277.253.camel@zakaz.uk.xensource.com> From: Ian Campbell To: Pasi =?ISO-8859-1?Q?K=E4rkk=E4inen?= Date: Mon, 3 Sep 2012 10:09:07 +0100 In-Reply-To: <20120902044626.GE8912@reaktio.net> References: <1346148361.9975.3.camel@zakaz.uk.xensource.com> <20120902044626.GE8912@reaktio.net> Organization: Citrix Systems, Inc. X-Mailer: Evolution 3.4.3-1 MIME-Version: 1.0 Cc: xen-users , xen-devel Subject: Re: [Xen-users] [Xen-devel] Xen 4.2 TODO / Release Plan X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: base64 Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org T24gU3VuLCAyMDEyLTA5LTAyIGF0IDA1OjQ2ICswMTAwLCBQYXNpIEvDpHJra8OkaW5lbiB3cm90 ZToKPiBPbiBUdWUsIEF1ZyAyOCwgMjAxMiBhdCAxMTowNjowMUFNICswMTAwLCBJYW4gQ2FtcGJl bGwgd3JvdGU6Cj4gPiAKPiA+ICAgICAqIHhsLmNmZyg1KSBkb2N1bWVudGF0aW9uIHBhdGNoIGZv ciBxZW11LXVwc3RyZWFtCj4gPiAgICAgICB2aWRlb3JhbS92aWRlb21lbSBzdXBwb3J0Ogo+ID4g ICAgICAgaHR0cDovL2xpc3RzLnhlbi5vcmcvYXJjaGl2ZXMvaHRtbC94ZW4tZGV2ZWwvMjAxMi0w NS9tc2cwMDI1MC5odG1sCj4gPiAgICAgICBxZW11LXVwc3RyZWFtIGRvZXNuJ3Qgc3VwcG9ydCBz cGVjaWZ5aW5nIHZpZGVvbWVtIHNpemUgZm9yIHRoZQo+ID4gICAgICAgSFZNIGd1ZXN0IGNpcnJ1 cy9zdGR2Z2EuICAoYnV0IHRoaXMgd29ya3Mgd2l0aAo+ID4gICAgICAgcWVtdS14ZW4tdHJhZGl0 aW9uYWwpLiAoUGFzaSBLw6Rya2vDpGluZW4pCj4gPiAKPiAKPiBQYXRjaCBzZW50IHRvIHRoZSBs aXN0LgoKVGhhbmtzIQoKCgpfX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19f X19fX19fXwpYZW4tdXNlcnMgbWFpbGluZyBsaXN0Clhlbi11c2Vyc0BsaXN0cy54ZW4ub3JnCmh0 dHA6Ly9saXN0cy54ZW4ub3JnL3hlbi11c2Vycw== From xen-users-bounces@lists.xen.org Mon Sep 03 09:10:31 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Mon, 03 Sep 2012 09:10:31 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1T8Sel-0004th-D3; Mon, 03 Sep 2012 09:09:19 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1T8Sej-0004tE-Er for xen-users@lists.xen.org; Mon, 03 Sep 2012 09:09:17 +0000 Received: from [85.158.143.35:54592] by server-3.bemta-4.messagelabs.com id 29/95-08232-CB374405; Mon, 03 Sep 2012 09:09:16 +0000 X-Env-Sender: Ian.Campbell@citrix.com X-Msg-Ref: server-11.tower-21.messagelabs.com!1346663349!11963754!1 X-Originating-IP: [62.200.22.115] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogNjIuMjAwLjIyLjExNSA9PiAxMTE0ODk=\n X-StarScan-Received: X-StarScan-Version: 6.6.1.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 24455 invoked from network); 3 Sep 2012 09:09:09 -0000 Received: from smtp.eu.citrix.com (HELO SMTP.EU.CITRIX.COM) (62.200.22.115) by server-11.tower-21.messagelabs.com with RC4-SHA encrypted SMTP; 3 Sep 2012 09:09:09 -0000 X-IronPort-AV: E=Sophos;i="4.80,359,1344211200"; d="scan'208";a="14311907" Received: from lonpmailmx01.citrite.net ([10.30.203.162]) by LONPIPO01.EU.CITRIX.COM with ESMTP/TLS/RC4-MD5; 03 Sep 2012 09:09:09 +0000 Received: from [10.80.2.42] (10.80.2.42) by LONPMAILMX01.citrite.net (10.30.203.162) with Microsoft SMTP Server id 8.3.279.1; Mon, 3 Sep 2012 10:09:09 +0100 Message-ID: <1346663347.27277.253.camel@zakaz.uk.xensource.com> From: Ian Campbell To: Pasi =?ISO-8859-1?Q?K=E4rkk=E4inen?= Date: Mon, 3 Sep 2012 10:09:07 +0100 In-Reply-To: <20120902044626.GE8912@reaktio.net> References: <1346148361.9975.3.camel@zakaz.uk.xensource.com> <20120902044626.GE8912@reaktio.net> Organization: Citrix Systems, Inc. X-Mailer: Evolution 3.4.3-1 MIME-Version: 1.0 Cc: xen-users , xen-devel Subject: Re: [Xen-users] [Xen-devel] Xen 4.2 TODO / Release Plan X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: base64 Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org T24gU3VuLCAyMDEyLTA5LTAyIGF0IDA1OjQ2ICswMTAwLCBQYXNpIEvDpHJra8OkaW5lbiB3cm90 ZToKPiBPbiBUdWUsIEF1ZyAyOCwgMjAxMiBhdCAxMTowNjowMUFNICswMTAwLCBJYW4gQ2FtcGJl bGwgd3JvdGU6Cj4gPiAKPiA+ICAgICAqIHhsLmNmZyg1KSBkb2N1bWVudGF0aW9uIHBhdGNoIGZv ciBxZW11LXVwc3RyZWFtCj4gPiAgICAgICB2aWRlb3JhbS92aWRlb21lbSBzdXBwb3J0Ogo+ID4g ICAgICAgaHR0cDovL2xpc3RzLnhlbi5vcmcvYXJjaGl2ZXMvaHRtbC94ZW4tZGV2ZWwvMjAxMi0w NS9tc2cwMDI1MC5odG1sCj4gPiAgICAgICBxZW11LXVwc3RyZWFtIGRvZXNuJ3Qgc3VwcG9ydCBz cGVjaWZ5aW5nIHZpZGVvbWVtIHNpemUgZm9yIHRoZQo+ID4gICAgICAgSFZNIGd1ZXN0IGNpcnJ1 cy9zdGR2Z2EuICAoYnV0IHRoaXMgd29ya3Mgd2l0aAo+ID4gICAgICAgcWVtdS14ZW4tdHJhZGl0 aW9uYWwpLiAoUGFzaSBLw6Rya2vDpGluZW4pCj4gPiAKPiAKPiBQYXRjaCBzZW50IHRvIHRoZSBs aXN0LgoKVGhhbmtzIQoKCgpfX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19f X19fX19fXwpYZW4tdXNlcnMgbWFpbGluZyBsaXN0Clhlbi11c2Vyc0BsaXN0cy54ZW4ub3JnCmh0 dHA6Ly9saXN0cy54ZW4ub3JnL3hlbi11c2Vycw== From xen-users-bounces@lists.xen.org Mon Sep 03 09:12:00 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Mon, 03 Sep 2012 09:12:00 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1T8SgY-0005Bm-0E; Mon, 03 Sep 2012 09:11:10 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1T8SgW-0005Au-C3 for xen-users@lists.xen.org; Mon, 03 Sep 2012 09:11:08 +0000 Received: from [85.158.138.51:7537] by server-3.bemta-3.messagelabs.com id 71/D5-21322-A2474405; Mon, 03 Sep 2012 09:11:06 +0000 X-Env-Sender: Ian.Campbell@citrix.com X-Msg-Ref: server-6.tower-174.messagelabs.com!1346663449!20234038!1 X-Originating-IP: [62.200.22.115] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogNjIuMjAwLjIyLjExNSA9PiAxMTEzODI=\n X-StarScan-Received: X-StarScan-Version: 6.6.1.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 9258 invoked from network); 3 Sep 2012 09:10:49 -0000 Received: from smtp.ctxuk.citrix.com (HELO SMTP.EU.CITRIX.COM) (62.200.22.115) by server-6.tower-174.messagelabs.com with RC4-SHA encrypted SMTP; 3 Sep 2012 09:10:49 -0000 X-IronPort-AV: E=Sophos;i="4.80,359,1344211200"; d="scan'208";a="14312062" Received: from lonpmailmx01.citrite.net ([10.30.203.162]) by LONPIPO01.EU.CITRIX.COM with ESMTP/TLS/RC4-MD5; 03 Sep 2012 09:10:48 +0000 Received: from [10.80.2.42] (10.80.2.42) by LONPMAILMX01.citrite.net (10.30.203.162) with Microsoft SMTP Server id 8.3.279.1; Mon, 3 Sep 2012 10:10:48 +0100 Message-ID: <1346663447.27277.254.camel@zakaz.uk.xensource.com> From: Ian Campbell To: George Dunlap Date: Mon, 3 Sep 2012 10:10:47 +0100 In-Reply-To: References: <1346148361.9975.3.camel@zakaz.uk.xensource.com> Organization: Citrix Systems, Inc. X-Mailer: Evolution 3.4.3-1 MIME-Version: 1.0 Cc: xen-users , xen-devel Subject: Re: [Xen-users] [Xen-devel] Xen 4.2 TODO / Release Plan X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org On Fri, 2012-08-31 at 18:26 +0100, George Dunlap wrote: > On Tue, Aug 28, 2012 at 3:06 AM, Ian Campbell wrote: > > hypervisor, nice to have: > > > > * [BUG(?)] Under certain conditions, the p2m_pod_sweep code will > > stop halfway through searching, causing a guest to crash even if > > there was zeroed memory available. This is NOT a regression > > from 4.1, and is a very rare case, so probably shouldn't be a > > blocker. (In fact, I'd be open to the idea that it should wait > > until after the release to get more testing.) > > (George Dunlap) > > I probably won't get a chance to work on this until I get back > mid-september, so this shouldn't be a blocker. No problem. Since we hope to do the final RC this week that effectively means its pushed out to 4.3 so I'll mark it as such. Ian. _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Mon Sep 03 09:12:00 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Mon, 03 Sep 2012 09:12:00 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1T8SgY-0005Bm-0E; Mon, 03 Sep 2012 09:11:10 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1T8SgW-0005Au-C3 for xen-users@lists.xen.org; Mon, 03 Sep 2012 09:11:08 +0000 Received: from [85.158.138.51:7537] by server-3.bemta-3.messagelabs.com id 71/D5-21322-A2474405; Mon, 03 Sep 2012 09:11:06 +0000 X-Env-Sender: Ian.Campbell@citrix.com X-Msg-Ref: server-6.tower-174.messagelabs.com!1346663449!20234038!1 X-Originating-IP: [62.200.22.115] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogNjIuMjAwLjIyLjExNSA9PiAxMTEzODI=\n X-StarScan-Received: X-StarScan-Version: 6.6.1.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 9258 invoked from network); 3 Sep 2012 09:10:49 -0000 Received: from smtp.ctxuk.citrix.com (HELO SMTP.EU.CITRIX.COM) (62.200.22.115) by server-6.tower-174.messagelabs.com with RC4-SHA encrypted SMTP; 3 Sep 2012 09:10:49 -0000 X-IronPort-AV: E=Sophos;i="4.80,359,1344211200"; d="scan'208";a="14312062" Received: from lonpmailmx01.citrite.net ([10.30.203.162]) by LONPIPO01.EU.CITRIX.COM with ESMTP/TLS/RC4-MD5; 03 Sep 2012 09:10:48 +0000 Received: from [10.80.2.42] (10.80.2.42) by LONPMAILMX01.citrite.net (10.30.203.162) with Microsoft SMTP Server id 8.3.279.1; Mon, 3 Sep 2012 10:10:48 +0100 Message-ID: <1346663447.27277.254.camel@zakaz.uk.xensource.com> From: Ian Campbell To: George Dunlap Date: Mon, 3 Sep 2012 10:10:47 +0100 In-Reply-To: References: <1346148361.9975.3.camel@zakaz.uk.xensource.com> Organization: Citrix Systems, Inc. X-Mailer: Evolution 3.4.3-1 MIME-Version: 1.0 Cc: xen-users , xen-devel Subject: Re: [Xen-users] [Xen-devel] Xen 4.2 TODO / Release Plan X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org On Fri, 2012-08-31 at 18:26 +0100, George Dunlap wrote: > On Tue, Aug 28, 2012 at 3:06 AM, Ian Campbell wrote: > > hypervisor, nice to have: > > > > * [BUG(?)] Under certain conditions, the p2m_pod_sweep code will > > stop halfway through searching, causing a guest to crash even if > > there was zeroed memory available. This is NOT a regression > > from 4.1, and is a very rare case, so probably shouldn't be a > > blocker. (In fact, I'd be open to the idea that it should wait > > until after the release to get more testing.) > > (George Dunlap) > > I probably won't get a chance to work on this until I get back > mid-september, so this shouldn't be a blocker. No problem. Since we hope to do the final RC this week that effectively means its pushed out to 4.3 so I'll mark it as such. Ian. _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Mon Sep 03 09:24:55 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Mon, 03 Sep 2012 09:24:55 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1T8St1-0006PH-VC; Mon, 03 Sep 2012 09:24:03 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1T8St0-0006PC-V3 for xen-users@lists.xen.org; Mon, 03 Sep 2012 09:24:03 +0000 Received: from [85.158.143.99:20022] by server-1.bemta-4.messagelabs.com id EA/A9-12504-23774405; Mon, 03 Sep 2012 09:24:02 +0000 X-Env-Sender: s.munaut@whatever-company.com X-Msg-Ref: server-5.tower-216.messagelabs.com!1346664240!27861120!1 X-Originating-IP: [209.85.220.173] X-SpamReason: No, hits=0.3 required=7.0 tests=RCVD_BY_IP X-StarScan-Received: X-StarScan-Version: 6.6.1.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 28617 invoked from network); 3 Sep 2012 09:24:01 -0000 Received: from mail-vc0-f173.google.com (HELO mail-vc0-f173.google.com) (209.85.220.173) by server-5.tower-216.messagelabs.com with RC4-SHA encrypted SMTP; 3 Sep 2012 09:24:01 -0000 Received: by vcbgb23 with SMTP id gb23so6628356vcb.32 for ; Mon, 03 Sep 2012 02:24:00 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:x-gm-message-state; bh=8bmLThCbDqs6G3kuwySqHn2NJfywbd9JYJ5i0PGDR+I=; b=b99bDyQ68oS4GOBzop/K68HtBBDMBIS/ePLQ0hqdl80Gg6N3yjgG+6+Op93qiEtwjO 4XoeNcsPgDbQrzjB+tzPzaodaY0wqNGFyNouyjnDJbXF96VCxJf5slaRUC8/tRHLH/uG 6lx1Lgdavc4vgi7lJA9T6ZBEvJEcMIEi9Rwu3U/ltce5Ke406racqQD4krLbZxZQ3pf7 HA/NM+oHwsSA4rYux/Q/SRzwqwZNXdMJDpP9rgCGSMloHOkIcNTq6jDM4jxD6jCwas01 WycFdUd+TlSnaoejWHc/RV1Tc41c/1yr4V/AIyw0j6lkMvbuT/1VZJVFtTZpLV/ykZDa 8SkQ== MIME-Version: 1.0 Received: by 10.220.228.131 with SMTP id je3mr11733483vcb.73.1346664240417; Mon, 03 Sep 2012 02:24:00 -0700 (PDT) Received: by 10.58.70.172 with HTTP; Mon, 3 Sep 2012 02:24:00 -0700 (PDT) In-Reply-To: References: <503F7C25.2000303@inktank.com> Date: Mon, 3 Sep 2012 11:24:00 +0200 Message-ID: From: Sylvain Munaut To: "Fajar A. Nugraha" X-Gm-Message-State: ALoCoQk4E81x1x9pk605Y9D7BLt9v2K1ZdFAVUJrq5xrHDCdER49P1smQ/Glgrqba293QohWYveA Cc: Alex Elder , xen-users@lists.xen.org, ceph-devel@vger.kernel.org Subject: Re: [Xen-users] Ceph + RBD + Xen: Complete collapse -> Network issue in domU / Bad data for OSD / OOM Kill X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org On Thu, Aug 30, 2012 at 5:04 PM, Fajar A. Nugraha wrote: > On Thu, Aug 30, 2012 at 9:43 PM, Alex Elder wrote: >> On 08/30/2012 09:06 AM, Sylvain Munaut wrote: >>> Hi, >> >> I posted the following comments on IRC but am putting it here >> just so it's visible along with the original post. All of the >> following is deduced from about 10 minutes of scanning through >> unfamiliar code, so I may be way off. (I've edited my the >> comments I posted for readability.) >> >> The code is in drivers/net/xen-netfront.c, in the function >> xennet_get_responses(). > > IIRC that's the xen PV driver. I've been digging a bit and it seems issuing a ethtool -K vif1.0 tx off in the dom0 prevents the issue. Note that it needs to be in the dom0 on the VIF and not in the domU on the eth0 interface like I originally tried. It's also not enough to disable gso and/or tso, you need to turn off all tx accel. I will start another subject in xen-devel seems it appears to be a bug in the PV driver. Cheers, Sylvain _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Mon Sep 03 09:24:55 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Mon, 03 Sep 2012 09:24:55 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1T8St1-0006PH-VC; Mon, 03 Sep 2012 09:24:03 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1T8St0-0006PC-V3 for xen-users@lists.xen.org; Mon, 03 Sep 2012 09:24:03 +0000 Received: from [85.158.143.99:20022] by server-1.bemta-4.messagelabs.com id EA/A9-12504-23774405; Mon, 03 Sep 2012 09:24:02 +0000 X-Env-Sender: s.munaut@whatever-company.com X-Msg-Ref: server-5.tower-216.messagelabs.com!1346664240!27861120!1 X-Originating-IP: [209.85.220.173] X-SpamReason: No, hits=0.3 required=7.0 tests=RCVD_BY_IP X-StarScan-Received: X-StarScan-Version: 6.6.1.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 28617 invoked from network); 3 Sep 2012 09:24:01 -0000 Received: from mail-vc0-f173.google.com (HELO mail-vc0-f173.google.com) (209.85.220.173) by server-5.tower-216.messagelabs.com with RC4-SHA encrypted SMTP; 3 Sep 2012 09:24:01 -0000 Received: by vcbgb23 with SMTP id gb23so6628356vcb.32 for ; Mon, 03 Sep 2012 02:24:00 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:x-gm-message-state; bh=8bmLThCbDqs6G3kuwySqHn2NJfywbd9JYJ5i0PGDR+I=; b=b99bDyQ68oS4GOBzop/K68HtBBDMBIS/ePLQ0hqdl80Gg6N3yjgG+6+Op93qiEtwjO 4XoeNcsPgDbQrzjB+tzPzaodaY0wqNGFyNouyjnDJbXF96VCxJf5slaRUC8/tRHLH/uG 6lx1Lgdavc4vgi7lJA9T6ZBEvJEcMIEi9Rwu3U/ltce5Ke406racqQD4krLbZxZQ3pf7 HA/NM+oHwsSA4rYux/Q/SRzwqwZNXdMJDpP9rgCGSMloHOkIcNTq6jDM4jxD6jCwas01 WycFdUd+TlSnaoejWHc/RV1Tc41c/1yr4V/AIyw0j6lkMvbuT/1VZJVFtTZpLV/ykZDa 8SkQ== MIME-Version: 1.0 Received: by 10.220.228.131 with SMTP id je3mr11733483vcb.73.1346664240417; Mon, 03 Sep 2012 02:24:00 -0700 (PDT) Received: by 10.58.70.172 with HTTP; Mon, 3 Sep 2012 02:24:00 -0700 (PDT) In-Reply-To: References: <503F7C25.2000303@inktank.com> Date: Mon, 3 Sep 2012 11:24:00 +0200 Message-ID: From: Sylvain Munaut To: "Fajar A. Nugraha" X-Gm-Message-State: ALoCoQk4E81x1x9pk605Y9D7BLt9v2K1ZdFAVUJrq5xrHDCdER49P1smQ/Glgrqba293QohWYveA Cc: Alex Elder , xen-users@lists.xen.org, ceph-devel@vger.kernel.org Subject: Re: [Xen-users] Ceph + RBD + Xen: Complete collapse -> Network issue in domU / Bad data for OSD / OOM Kill X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org On Thu, Aug 30, 2012 at 5:04 PM, Fajar A. Nugraha wrote: > On Thu, Aug 30, 2012 at 9:43 PM, Alex Elder wrote: >> On 08/30/2012 09:06 AM, Sylvain Munaut wrote: >>> Hi, >> >> I posted the following comments on IRC but am putting it here >> just so it's visible along with the original post. All of the >> following is deduced from about 10 minutes of scanning through >> unfamiliar code, so I may be way off. (I've edited my the >> comments I posted for readability.) >> >> The code is in drivers/net/xen-netfront.c, in the function >> xennet_get_responses(). > > IIRC that's the xen PV driver. I've been digging a bit and it seems issuing a ethtool -K vif1.0 tx off in the dom0 prevents the issue. Note that it needs to be in the dom0 on the VIF and not in the domU on the eth0 interface like I originally tried. It's also not enough to disable gso and/or tso, you need to turn off all tx accel. I will start another subject in xen-devel seems it appears to be a bug in the PV driver. Cheers, Sylvain _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Mon Sep 03 09:44:04 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Mon, 03 Sep 2012 09:44:04 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1T8TBj-00070b-58; Mon, 03 Sep 2012 09:43:23 +0000 Received: from mail27.messagelabs.com ([193.109.254.147]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1T8TBh-00070M-Hj; Mon, 03 Sep 2012 09:43:21 +0000 X-Env-Sender: Ian.Campbell@citrix.com X-Msg-Ref: server-10.tower-27.messagelabs.com!1346665394!4128925!1 X-Originating-IP: [62.200.22.115] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogNjIuMjAwLjIyLjExNSA9PiAxMTEzODI=\n X-StarScan-Received: X-StarScan-Version: 6.6.1.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 718 invoked from network); 3 Sep 2012 09:43:15 -0000 Received: from smtp.eu.citrix.com (HELO SMTP.EU.CITRIX.COM) (62.200.22.115) by server-10.tower-27.messagelabs.com with RC4-SHA encrypted SMTP; 3 Sep 2012 09:43:15 -0000 X-IronPort-AV: E=Sophos;i="4.80,359,1344211200"; d="scan'208";a="14312871" Received: from lonpmailmx01.citrite.net ([10.30.203.162]) by LONPIPO01.EU.CITRIX.COM with ESMTP/TLS/RC4-MD5; 03 Sep 2012 09:42:42 +0000 Received: from [10.80.2.42] (10.80.2.42) by LONPMAILMX01.citrite.net (10.30.203.162) with Microsoft SMTP Server id 8.3.279.1; Mon, 3 Sep 2012 10:42:42 +0100 Message-ID: <1346665360.25864.2.camel@zakaz.uk.xensource.com> From: Ian Campbell To: xen-devel , xen-users Date: Mon, 3 Sep 2012 10:42:40 +0100 Organization: Citrix Systems, Inc. X-Mailer: Evolution 3.4.3-1 MIME-Version: 1.0 Subject: [Xen-users] Xen 4.2.0 Release Plan / TODO X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: base64 Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org MTkgTWFyY2ggICAgICAgIC0tIFRPRE8gbGlzdCBsb2NrZWQgZG93bgoyIEFwcmlsICAgICAgICAg LS0gRmVhdHVyZSBGcmVlemUKMzAgSnVseQkJLS0gWGVuIDQuMi4wLXJjMQo4IEF1Z3VzdAktLSBY ZW4gNC4yLjAtcmMyCjIzIEF1Z3VzdAktLSBYZW4gNC4yLjAtcmMzCldlZWtseSAgICAgICAgICAt LSBSQ04rMSB1bnRpbCByZWxlYXNlICAgICAgICAgIDw8IFdFIEFSRSBIRVJFCgpXZSBpbnRlbmQg dG8gcmVsZWFzZSBSQzQgdG93YXJkcyB0aGUgZW5kIG9mIHRoaXMgd2Vlay4gQWxsIGJlaW5nIHdl bGwKd2UgaW50ZW5kIGZvciB0aGlzIHRvIGJlIHRoZSBmaW5hbCByZWxlYXNlIGNhbmRpZGF0ZS4g UGxlYXNlIHRlc3QhCgpUaGUgdXBkYXRlZCBUT0RPIGxpc3QgZm9sbG93cy4KCmh5cGVydmlzb3Is IGJsb2NrZXJzOgoKICAgICogTm9uZQoKdG9vbHMsIGJsb2NrZXJzOgoKICAgICogbGlieGwgc3Rh YmxlIEFQSSAtLSB3ZSB3b3VsZCBsaWtlIDQuMiB0byBkZWZpbmUgYSBzdGFibGUgQVBJCiAgICAg IHdoaWNoIGRvd25zdHJlYW0ncyBjYW4gc3RhcnQgdG8gcmVseSBvbiBub3QgY2hhbmdpbmcuIEFz cGVjdHMgb2YKICAgICAgdGhpcyBhcmU6CgogICAgICAgICogTm9uZSBrbm93bgoKICAgICogeGwg Y29tcGF0aWJpbGl0eSB3aXRoIHhtOgoKICAgICAgICAqIE5vIGtub3duIGlzc3VlcwoKICAgICog W0NIRUNLXSBNb3JlIGZvcm1hbGx5IGRlcHJlY2F0ZSB4bS94ZW5kLiBNYW5wYWdlIHBhdGNoZXMg YWxyZWFkeQogICAgICBpbiB0cmVlLiBOZWVkcyByZWxlYXNlIG5vdGluZyBhbmQgY29tbXVuaWNh dGlvbiBhcm91bmQgLXJjMSB0bwogICAgICByZW1pbmQgcGVvcGxlIHRvIHRlc3QgeGwuIChET05F KQoKICAgICogW0NIRUNLXSBDb25maXJtIHRoYXQgbWlncmF0aW9uIGZyb20gWGVuIDQuMSAtPiA0 LjIgd29ya3MuIChET05FCiAgICAgIGZvciBQViwgSFZNIHN0aWxsIFRPRE8pCgogICAgKiBCdW1w IGxpYnJhcnkgU09OQU1FUyBhcyBuZWNlc3NhcnkuCiAgICAgIDwyMDUwMi4zOTQ0MC45Njk2MTku ODI0OTc2QG1hcmluZXIudWsueGVuc291cmNlLmNvbT4KCiAgICAqIFtCVUddIHFlbXUtdHJhZGl0 aW9uYWwgaGFzIDUwJSBjcHUgdXRpbGl6YXRpb24gb24gYW4gaWRsZQogICAgICBXaW5kb3dzIHN5 c3RlbSBpZiBVU0IgaXMgZW5hYmxlZC4gTm90IDEwMCUgY2xlYXIgd2hldGhlciB0aGlzIGlzCiAg ICAgIFhlbiBvciBxZW11LiAgR2VvcmdlIER1bmxhcCB0aGlua3MgdGhpcyBpcyBtb3N0bHkgZG93 biB0byA2NC1iaXQKICAgICAgc3lzY2FsbCBvdmVyaGVhZCBhbmQgaXMgbm90IGEgYmxvY2tlciwg d2lsbCBkcm9wIGZyb20gdGhlIGxpc3QuCgogICAgKiBEaXNhYmxlIGdlbmVyYXRpb24gaWQgZnJv bSB4bC4gTWljcm9zb2Z0IGNoYW5nZWQgdGhlCiAgICAgIHNwZWNpZmljYXRpb24gb2YgdGhpcyB2 YWx1ZSBiZXR3ZWVuIFc4IGJldGEgYW5kIFJDIGFuZCB3ZSBub3cKICAgICAgaW1wbGVtZW50IHRo ZSBvbGQgc3BlYy4gRGlzYWJsZSBmb3IgNC4yIGFuZCByZXZpc3QgaW1wbGVtZW50aW5nCiAgICAg IHRoZSBuZXcgc3BlYyBmb3IgNC4zLiAoUGF1bCBEdXJyYW50LCBET05FKQoKaHlwZXJ2aXNvciwg bmljZSB0byBoYXZlOgoKICAgICogW0JVRyg/KV0gVW5kZXIgY2VydGFpbiBjb25kaXRpb25zLCB0 aGUgcDJtX3BvZF9zd2VlcCBjb2RlIHdpbGwKICAgICAgc3RvcCBoYWxmd2F5IHRocm91Z2ggc2Vh cmNoaW5nLCBjYXVzaW5nIGEgZ3Vlc3QgdG8gY3Jhc2ggZXZlbiBpZgogICAgICB0aGVyZSB3YXMg emVyb2VkIG1lbW9yeSBhdmFpbGFibGUuICBUaGlzIGlzIE5PVCBhIHJlZ3Jlc3Npb24KICAgICAg ZnJvbSA0LjEsIGFuZCBpcyBhIHZlcnkgcmFyZSBjYXNlLCBzbyBwcm9iYWJseSBzaG91bGRuJ3Qg YmUgYQogICAgICBibG9ja2VyLiAgKEluIGZhY3QsIEknZCBiZSBvcGVuIHRvIHRoZSBpZGVhIHRo YXQgaXQgc2hvdWxkIHdhaXQKICAgICAgdW50aWwgYWZ0ZXIgdGhlIHJlbGVhc2UgdG8gZ2V0IG1v cmUgdGVzdGluZy4pCiAgICAgIAkgICAgKEdlb3JnZSBEdW5sYXAsIGRlZmVyIHVudGlsIDQuMykK CiAgICAqIFMzIHJlZ3Jlc3Npb24ocz8pIHJlcG9ydGVkIGJ5IEJlbiBHdXRocm8gKEJlbiAmIEph biBCZXVsaWNoKQoKICAgICogZml4IGhpZ2ggY2hhbmdlIHJhdGUgdG8gQ01PUyBSVEMgcGVyaW9k aWMgaW50ZXJydXB0IGNhdXNpbmcKICAgICAgZ3Vlc3Qgd2FsbCBjbG9jayB0aW1lIHRvIGxhZyAo SmFuIEJldWxpY2gsIGNvcmUgZml4IERPTkUgZm9yCiAgICAgIDQuMiwgcmVzdCBwdXNoZWQgb3V0 IHRvIHBvc3QgNC4yKQoKdG9vbHMsIG5pY2UgdG8gaGF2ZToKCiAgICAqIHhsIGNvbXBhdGliaWxp dHkgd2l0aCB4bToKCiAgICAgICAgKiB0aGUgcGFyYW1ldGVyIGlvIGFuZCBpcnEgaW4gZG9tVSBj b25maWcgZmlsZXMgYXJlIG5vdAogICAgICAgICAgZXZhbHVhdGVkIGJ5IHhsLiAgU28gaXQgaXMg bm90IHBvc3NpYmxlIHRvIHBhc3N0aHJvdWdoIGEKICAgICAgICAgIHBhcmFsbGVsIHBvcnQgZm9y IG15IHByaW50ZXIgdG8gZG9tVSB3aGVuIEkgc3RhcnQgdGhlIGRvbVUKICAgICAgICAgIHdpdGgg eGwgY29tbWFuZC4gKHJlcG9ydGVkIGJ5IERpZXRlciBCbG9tcywKICAgICAgICAgIDwyMDEyMDgx NDEwMDcwNC5HQTE5NzA0QGJsb21zLmRlPi4gSWFuIENhbXBiZWxsLCBwYXRjaCBwb3N0ZWQpCgog ICAgICAgICogeGwgZG9lc24ndCBzdXBwb3J0IHRoZSAnLWEnIG9wdGlvbiBmb3Igc2h1dGRvd24s IHRvIHNodXRkb3duCiAgICAgICAgICBhbGwgZG9tYWlucy4gKFJlcG9ydGVkIGJ5IFNhbmRlciBF aWtlbGVuYm9vbSAKCSAgPDg4NTgyMTU0OC4yMDEyMDgzMTEyNDkwMkBlaWtlbGVuYm9vbS5pdD4p IAoKICAgICogeGwuY2ZnKDUpIGRvY3VtZW50YXRpb24gcGF0Y2ggZm9yIHFlbXUtdXBzdHJlYW0K ICAgICAgdmlkZW9yYW0vdmlkZW9tZW0gc3VwcG9ydDoKICAgICAgaHR0cDovL2xpc3RzLnhlbi5v cmcvYXJjaGl2ZXMvaHRtbC94ZW4tZGV2ZWwvMjAxMi0wNS9tc2cwMDI1MC5odG1sCiAgICAgIHFl bXUtdXBzdHJlYW0gZG9lc24ndCBzdXBwb3J0IHNwZWNpZnlpbmcgdmlkZW9tZW0gc2l6ZSBmb3Ig dGhlCiAgICAgIEhWTSBndWVzdCBjaXJydXMvc3RkdmdhLiAgKGJ1dCB0aGlzIHdvcmtzIHdpdGgK ICAgICAgcWVtdS14ZW4tdHJhZGl0aW9uYWwpLiAoUGFzaSBLw6Rya2vDpGluZW4sIHBhdGNoZXMg c2VudCkKCiAgICAqIFtCVUddICd4bCB2Y3B1LXNldCcgY2FuJ3QgZGVjcmVhc2UgdGhlIHZDUFUg bnVtYmVyIG9mIGEgSFZNIGd1ZXN0CiAgICAgIGh0dHA6Ly9idWd6aWxsYS54ZW4ub3JnL2J1Z3pp bGxhL3Nob3dfYnVnLmNnaT9pZD0xODIyCgogICAgKiBMb2FkIGJsa3RhcCBkcml2ZXIgZnJvbSB4 ZW5jb21tb25zIGluaXRzY3JpcHQgaWYgYXZhaWxhYmxlLCB0aHJlYWQgYXQ6CiAgICAgIDxkYjYx NGU5MmZhZjc0M2UyMGIzZi4xMzM3MDk2OTc3QGtvZG8yPi4gVG8gYmUgZml4ZWQgbW9yZQogICAg ICBwcm9wZXJseSBpbiA0LjMuIChET05FKQoKICAgICogW0JVR10geGwgYWxsb3dzIHNhbWUgUENJ IGRldmljZSB0byBiZSBhc3NpZ25lZCB0byBtdWx0aXBsZQogICAgICBndWVzdHMuIGh0dHA6Ly9i dWd6aWxsYS54ZW4ub3JnL2J1Z3ppbGxhL3Nob3dfYnVnLmNnaT9pZD0xODI2CiAgICAgICg8RTQ1 NThDMEM5NjY4ODc0ODgzN0VCMUIwNUJFRUQ3NUEwRkQ1NTc0QUBTSFNNU1gxMDIuY2NyLmNvcnAu aW50ZWwuY29tPikKCiAgICAqICJ4bCBjcHVwb29sLWNyZWF0ZSIgc2VnZmF1bHQgb24gaW5jb3Jy ZWN0IGlucHV0LiBSZXBvcnRlZCBieQogICAgICBHZW9yZ2UgRHVubGFwLAogICAgICA8Q0FGTEJ4 WmFFY2kwbU9jRENnRlg5ems9d2gzejROZjFMRDVFNUZjeTdZMz1pb0RBTT1nQG1haWwuZ21haWwu Y29tPgogICAgICAoSWFuIEphY2tzb24sIERPTkUpCgogICAgKiBbQlVHXSB4bCBmYWlscyBvbiBj b25maWcgZmlsZXMgd2hpY2ggYXJlIG1pc3NpbmcgdGhlIGZpbmFsCiAgICAgIG5ld2xpbmUgKElh biBKYWNrc29uKSAKCgoKX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19f X19fX18KWGVuLXVzZXJzIG1haWxpbmcgbGlzdApYZW4tdXNlcnNAbGlzdHMueGVuLm9yZwpodHRw Oi8vbGlzdHMueGVuLm9yZy94ZW4tdXNlcnM= From xen-users-bounces@lists.xen.org Mon Sep 03 09:44:04 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Mon, 03 Sep 2012 09:44:04 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1T8TBj-00070b-58; Mon, 03 Sep 2012 09:43:23 +0000 Received: from mail27.messagelabs.com ([193.109.254.147]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1T8TBh-00070M-Hj; Mon, 03 Sep 2012 09:43:21 +0000 X-Env-Sender: Ian.Campbell@citrix.com X-Msg-Ref: server-10.tower-27.messagelabs.com!1346665394!4128925!1 X-Originating-IP: [62.200.22.115] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogNjIuMjAwLjIyLjExNSA9PiAxMTEzODI=\n X-StarScan-Received: X-StarScan-Version: 6.6.1.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 718 invoked from network); 3 Sep 2012 09:43:15 -0000 Received: from smtp.eu.citrix.com (HELO SMTP.EU.CITRIX.COM) (62.200.22.115) by server-10.tower-27.messagelabs.com with RC4-SHA encrypted SMTP; 3 Sep 2012 09:43:15 -0000 X-IronPort-AV: E=Sophos;i="4.80,359,1344211200"; d="scan'208";a="14312871" Received: from lonpmailmx01.citrite.net ([10.30.203.162]) by LONPIPO01.EU.CITRIX.COM with ESMTP/TLS/RC4-MD5; 03 Sep 2012 09:42:42 +0000 Received: from [10.80.2.42] (10.80.2.42) by LONPMAILMX01.citrite.net (10.30.203.162) with Microsoft SMTP Server id 8.3.279.1; Mon, 3 Sep 2012 10:42:42 +0100 Message-ID: <1346665360.25864.2.camel@zakaz.uk.xensource.com> From: Ian Campbell To: xen-devel , xen-users Date: Mon, 3 Sep 2012 10:42:40 +0100 Organization: Citrix Systems, Inc. X-Mailer: Evolution 3.4.3-1 MIME-Version: 1.0 Subject: [Xen-users] Xen 4.2.0 Release Plan / TODO X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: base64 Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org MTkgTWFyY2ggICAgICAgIC0tIFRPRE8gbGlzdCBsb2NrZWQgZG93bgoyIEFwcmlsICAgICAgICAg LS0gRmVhdHVyZSBGcmVlemUKMzAgSnVseQkJLS0gWGVuIDQuMi4wLXJjMQo4IEF1Z3VzdAktLSBY ZW4gNC4yLjAtcmMyCjIzIEF1Z3VzdAktLSBYZW4gNC4yLjAtcmMzCldlZWtseSAgICAgICAgICAt LSBSQ04rMSB1bnRpbCByZWxlYXNlICAgICAgICAgIDw8IFdFIEFSRSBIRVJFCgpXZSBpbnRlbmQg dG8gcmVsZWFzZSBSQzQgdG93YXJkcyB0aGUgZW5kIG9mIHRoaXMgd2Vlay4gQWxsIGJlaW5nIHdl bGwKd2UgaW50ZW5kIGZvciB0aGlzIHRvIGJlIHRoZSBmaW5hbCByZWxlYXNlIGNhbmRpZGF0ZS4g UGxlYXNlIHRlc3QhCgpUaGUgdXBkYXRlZCBUT0RPIGxpc3QgZm9sbG93cy4KCmh5cGVydmlzb3Is IGJsb2NrZXJzOgoKICAgICogTm9uZQoKdG9vbHMsIGJsb2NrZXJzOgoKICAgICogbGlieGwgc3Rh YmxlIEFQSSAtLSB3ZSB3b3VsZCBsaWtlIDQuMiB0byBkZWZpbmUgYSBzdGFibGUgQVBJCiAgICAg IHdoaWNoIGRvd25zdHJlYW0ncyBjYW4gc3RhcnQgdG8gcmVseSBvbiBub3QgY2hhbmdpbmcuIEFz cGVjdHMgb2YKICAgICAgdGhpcyBhcmU6CgogICAgICAgICogTm9uZSBrbm93bgoKICAgICogeGwg Y29tcGF0aWJpbGl0eSB3aXRoIHhtOgoKICAgICAgICAqIE5vIGtub3duIGlzc3VlcwoKICAgICog W0NIRUNLXSBNb3JlIGZvcm1hbGx5IGRlcHJlY2F0ZSB4bS94ZW5kLiBNYW5wYWdlIHBhdGNoZXMg YWxyZWFkeQogICAgICBpbiB0cmVlLiBOZWVkcyByZWxlYXNlIG5vdGluZyBhbmQgY29tbXVuaWNh dGlvbiBhcm91bmQgLXJjMSB0bwogICAgICByZW1pbmQgcGVvcGxlIHRvIHRlc3QgeGwuIChET05F KQoKICAgICogW0NIRUNLXSBDb25maXJtIHRoYXQgbWlncmF0aW9uIGZyb20gWGVuIDQuMSAtPiA0 LjIgd29ya3MuIChET05FCiAgICAgIGZvciBQViwgSFZNIHN0aWxsIFRPRE8pCgogICAgKiBCdW1w IGxpYnJhcnkgU09OQU1FUyBhcyBuZWNlc3NhcnkuCiAgICAgIDwyMDUwMi4zOTQ0MC45Njk2MTku ODI0OTc2QG1hcmluZXIudWsueGVuc291cmNlLmNvbT4KCiAgICAqIFtCVUddIHFlbXUtdHJhZGl0 aW9uYWwgaGFzIDUwJSBjcHUgdXRpbGl6YXRpb24gb24gYW4gaWRsZQogICAgICBXaW5kb3dzIHN5 c3RlbSBpZiBVU0IgaXMgZW5hYmxlZC4gTm90IDEwMCUgY2xlYXIgd2hldGhlciB0aGlzIGlzCiAg ICAgIFhlbiBvciBxZW11LiAgR2VvcmdlIER1bmxhcCB0aGlua3MgdGhpcyBpcyBtb3N0bHkgZG93 biB0byA2NC1iaXQKICAgICAgc3lzY2FsbCBvdmVyaGVhZCBhbmQgaXMgbm90IGEgYmxvY2tlciwg d2lsbCBkcm9wIGZyb20gdGhlIGxpc3QuCgogICAgKiBEaXNhYmxlIGdlbmVyYXRpb24gaWQgZnJv bSB4bC4gTWljcm9zb2Z0IGNoYW5nZWQgdGhlCiAgICAgIHNwZWNpZmljYXRpb24gb2YgdGhpcyB2 YWx1ZSBiZXR3ZWVuIFc4IGJldGEgYW5kIFJDIGFuZCB3ZSBub3cKICAgICAgaW1wbGVtZW50IHRo ZSBvbGQgc3BlYy4gRGlzYWJsZSBmb3IgNC4yIGFuZCByZXZpc3QgaW1wbGVtZW50aW5nCiAgICAg IHRoZSBuZXcgc3BlYyBmb3IgNC4zLiAoUGF1bCBEdXJyYW50LCBET05FKQoKaHlwZXJ2aXNvciwg bmljZSB0byBoYXZlOgoKICAgICogW0JVRyg/KV0gVW5kZXIgY2VydGFpbiBjb25kaXRpb25zLCB0 aGUgcDJtX3BvZF9zd2VlcCBjb2RlIHdpbGwKICAgICAgc3RvcCBoYWxmd2F5IHRocm91Z2ggc2Vh cmNoaW5nLCBjYXVzaW5nIGEgZ3Vlc3QgdG8gY3Jhc2ggZXZlbiBpZgogICAgICB0aGVyZSB3YXMg emVyb2VkIG1lbW9yeSBhdmFpbGFibGUuICBUaGlzIGlzIE5PVCBhIHJlZ3Jlc3Npb24KICAgICAg ZnJvbSA0LjEsIGFuZCBpcyBhIHZlcnkgcmFyZSBjYXNlLCBzbyBwcm9iYWJseSBzaG91bGRuJ3Qg YmUgYQogICAgICBibG9ja2VyLiAgKEluIGZhY3QsIEknZCBiZSBvcGVuIHRvIHRoZSBpZGVhIHRo YXQgaXQgc2hvdWxkIHdhaXQKICAgICAgdW50aWwgYWZ0ZXIgdGhlIHJlbGVhc2UgdG8gZ2V0IG1v cmUgdGVzdGluZy4pCiAgICAgIAkgICAgKEdlb3JnZSBEdW5sYXAsIGRlZmVyIHVudGlsIDQuMykK CiAgICAqIFMzIHJlZ3Jlc3Npb24ocz8pIHJlcG9ydGVkIGJ5IEJlbiBHdXRocm8gKEJlbiAmIEph biBCZXVsaWNoKQoKICAgICogZml4IGhpZ2ggY2hhbmdlIHJhdGUgdG8gQ01PUyBSVEMgcGVyaW9k aWMgaW50ZXJydXB0IGNhdXNpbmcKICAgICAgZ3Vlc3Qgd2FsbCBjbG9jayB0aW1lIHRvIGxhZyAo SmFuIEJldWxpY2gsIGNvcmUgZml4IERPTkUgZm9yCiAgICAgIDQuMiwgcmVzdCBwdXNoZWQgb3V0 IHRvIHBvc3QgNC4yKQoKdG9vbHMsIG5pY2UgdG8gaGF2ZToKCiAgICAqIHhsIGNvbXBhdGliaWxp dHkgd2l0aCB4bToKCiAgICAgICAgKiB0aGUgcGFyYW1ldGVyIGlvIGFuZCBpcnEgaW4gZG9tVSBj b25maWcgZmlsZXMgYXJlIG5vdAogICAgICAgICAgZXZhbHVhdGVkIGJ5IHhsLiAgU28gaXQgaXMg bm90IHBvc3NpYmxlIHRvIHBhc3N0aHJvdWdoIGEKICAgICAgICAgIHBhcmFsbGVsIHBvcnQgZm9y IG15IHByaW50ZXIgdG8gZG9tVSB3aGVuIEkgc3RhcnQgdGhlIGRvbVUKICAgICAgICAgIHdpdGgg eGwgY29tbWFuZC4gKHJlcG9ydGVkIGJ5IERpZXRlciBCbG9tcywKICAgICAgICAgIDwyMDEyMDgx NDEwMDcwNC5HQTE5NzA0QGJsb21zLmRlPi4gSWFuIENhbXBiZWxsLCBwYXRjaCBwb3N0ZWQpCgog ICAgICAgICogeGwgZG9lc24ndCBzdXBwb3J0IHRoZSAnLWEnIG9wdGlvbiBmb3Igc2h1dGRvd24s IHRvIHNodXRkb3duCiAgICAgICAgICBhbGwgZG9tYWlucy4gKFJlcG9ydGVkIGJ5IFNhbmRlciBF aWtlbGVuYm9vbSAKCSAgPDg4NTgyMTU0OC4yMDEyMDgzMTEyNDkwMkBlaWtlbGVuYm9vbS5pdD4p IAoKICAgICogeGwuY2ZnKDUpIGRvY3VtZW50YXRpb24gcGF0Y2ggZm9yIHFlbXUtdXBzdHJlYW0K ICAgICAgdmlkZW9yYW0vdmlkZW9tZW0gc3VwcG9ydDoKICAgICAgaHR0cDovL2xpc3RzLnhlbi5v cmcvYXJjaGl2ZXMvaHRtbC94ZW4tZGV2ZWwvMjAxMi0wNS9tc2cwMDI1MC5odG1sCiAgICAgIHFl bXUtdXBzdHJlYW0gZG9lc24ndCBzdXBwb3J0IHNwZWNpZnlpbmcgdmlkZW9tZW0gc2l6ZSBmb3Ig dGhlCiAgICAgIEhWTSBndWVzdCBjaXJydXMvc3RkdmdhLiAgKGJ1dCB0aGlzIHdvcmtzIHdpdGgK ICAgICAgcWVtdS14ZW4tdHJhZGl0aW9uYWwpLiAoUGFzaSBLw6Rya2vDpGluZW4sIHBhdGNoZXMg c2VudCkKCiAgICAqIFtCVUddICd4bCB2Y3B1LXNldCcgY2FuJ3QgZGVjcmVhc2UgdGhlIHZDUFUg bnVtYmVyIG9mIGEgSFZNIGd1ZXN0CiAgICAgIGh0dHA6Ly9idWd6aWxsYS54ZW4ub3JnL2J1Z3pp bGxhL3Nob3dfYnVnLmNnaT9pZD0xODIyCgogICAgKiBMb2FkIGJsa3RhcCBkcml2ZXIgZnJvbSB4 ZW5jb21tb25zIGluaXRzY3JpcHQgaWYgYXZhaWxhYmxlLCB0aHJlYWQgYXQ6CiAgICAgIDxkYjYx NGU5MmZhZjc0M2UyMGIzZi4xMzM3MDk2OTc3QGtvZG8yPi4gVG8gYmUgZml4ZWQgbW9yZQogICAg ICBwcm9wZXJseSBpbiA0LjMuIChET05FKQoKICAgICogW0JVR10geGwgYWxsb3dzIHNhbWUgUENJ IGRldmljZSB0byBiZSBhc3NpZ25lZCB0byBtdWx0aXBsZQogICAgICBndWVzdHMuIGh0dHA6Ly9i dWd6aWxsYS54ZW4ub3JnL2J1Z3ppbGxhL3Nob3dfYnVnLmNnaT9pZD0xODI2CiAgICAgICg8RTQ1 NThDMEM5NjY4ODc0ODgzN0VCMUIwNUJFRUQ3NUEwRkQ1NTc0QUBTSFNNU1gxMDIuY2NyLmNvcnAu aW50ZWwuY29tPikKCiAgICAqICJ4bCBjcHVwb29sLWNyZWF0ZSIgc2VnZmF1bHQgb24gaW5jb3Jy ZWN0IGlucHV0LiBSZXBvcnRlZCBieQogICAgICBHZW9yZ2UgRHVubGFwLAogICAgICA8Q0FGTEJ4 WmFFY2kwbU9jRENnRlg5ems9d2gzejROZjFMRDVFNUZjeTdZMz1pb0RBTT1nQG1haWwuZ21haWwu Y29tPgogICAgICAoSWFuIEphY2tzb24sIERPTkUpCgogICAgKiBbQlVHXSB4bCBmYWlscyBvbiBj b25maWcgZmlsZXMgd2hpY2ggYXJlIG1pc3NpbmcgdGhlIGZpbmFsCiAgICAgIG5ld2xpbmUgKElh biBKYWNrc29uKSAKCgoKX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19f X19fX18KWGVuLXVzZXJzIG1haWxpbmcgbGlzdApYZW4tdXNlcnNAbGlzdHMueGVuLm9yZwpodHRw Oi8vbGlzdHMueGVuLm9yZy94ZW4tdXNlcnM= From xen-users-bounces@lists.xen.org Mon Sep 03 11:51:14 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Mon, 03 Sep 2012 11:51:14 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1T8VAJ-0000yE-MQ; Mon, 03 Sep 2012 11:50:03 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1T8VAI-0000y8-OB for xen-users@lists.xen.org; Mon, 03 Sep 2012 11:50:02 +0000 Received: from [85.158.139.83:32342] by server-11.bemta-5.messagelabs.com id B2/A4-24658-96994405; Mon, 03 Sep 2012 11:50:01 +0000 X-Env-Sender: maik.brauer@mbs-systems.net X-Msg-Ref: server-5.tower-182.messagelabs.com!1346672999!28057475!1 X-Originating-IP: [188.40.240.248] X-SpamReason: No, hits=0.0 required=7.0 tests= X-StarScan-Received: X-StarScan-Version: 6.6.1.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 23903 invoked from network); 3 Sep 2012 11:49:59 -0000 Received: from mx1.mbs-systems.net (HELO mx1.mbs-systems.net) (188.40.240.248) by server-5.tower-182.messagelabs.com with SMTP; 3 Sep 2012 11:49:59 -0000 Received: from localhost (localhost [127.0.0.1]) by mx1.mbs-systems.net (Postfix) with ESMTP id 2B4D45C30B for ; Mon, 3 Sep 2012 13:50:53 +0200 (CEST) Received: from mx1.mbs-systems.net ([127.0.0.1]) by localhost (mta.mbs-systems.net [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id u3kCS7hMli+x for ; Mon, 3 Sep 2012 13:50:52 +0200 (CEST) Received: from [62.213.144.234] (unknown [62.213.144.234]) by mx1.mbs-systems.net (Postfix) with ESMTPSA id 1C6B65C221 for ; Mon, 3 Sep 2012 13:50:52 +0200 (CEST) From: Maik Brauer Date: Mon, 3 Sep 2012 13:49:55 +0200 Message-Id: To: xen-users@lists.xen.org Mime-Version: 1.0 (Apple Message framework v1278) X-Mailer: Apple Mail (2.1278) Subject: [Xen-users] Dom0 crashed when rebooting whilst DomU are running X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org Hello, when for example the Dom0 needs to be rebooted manually and several DomU's are running, the Dom0 will crash during shutdown, that just a Manual Hardware Reset will help to reboot. Current HVM is: Xen 4.1.3 Current Kernel: 2.6.32-5-xen-amd64 Is there a know issue, or what might could case this issue. When rebooting the Dom0 without having at least one DomU running, then the reboot is successful. Can someone help me? Thanks. Cheers, Maik _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Mon Sep 03 11:51:14 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Mon, 03 Sep 2012 11:51:14 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1T8VAJ-0000yE-MQ; Mon, 03 Sep 2012 11:50:03 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1T8VAI-0000y8-OB for xen-users@lists.xen.org; Mon, 03 Sep 2012 11:50:02 +0000 Received: from [85.158.139.83:32342] by server-11.bemta-5.messagelabs.com id B2/A4-24658-96994405; Mon, 03 Sep 2012 11:50:01 +0000 X-Env-Sender: maik.brauer@mbs-systems.net X-Msg-Ref: server-5.tower-182.messagelabs.com!1346672999!28057475!1 X-Originating-IP: [188.40.240.248] X-SpamReason: No, hits=0.0 required=7.0 tests= X-StarScan-Received: X-StarScan-Version: 6.6.1.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 23903 invoked from network); 3 Sep 2012 11:49:59 -0000 Received: from mx1.mbs-systems.net (HELO mx1.mbs-systems.net) (188.40.240.248) by server-5.tower-182.messagelabs.com with SMTP; 3 Sep 2012 11:49:59 -0000 Received: from localhost (localhost [127.0.0.1]) by mx1.mbs-systems.net (Postfix) with ESMTP id 2B4D45C30B for ; Mon, 3 Sep 2012 13:50:53 +0200 (CEST) Received: from mx1.mbs-systems.net ([127.0.0.1]) by localhost (mta.mbs-systems.net [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id u3kCS7hMli+x for ; Mon, 3 Sep 2012 13:50:52 +0200 (CEST) Received: from [62.213.144.234] (unknown [62.213.144.234]) by mx1.mbs-systems.net (Postfix) with ESMTPSA id 1C6B65C221 for ; Mon, 3 Sep 2012 13:50:52 +0200 (CEST) From: Maik Brauer Date: Mon, 3 Sep 2012 13:49:55 +0200 Message-Id: To: xen-users@lists.xen.org Mime-Version: 1.0 (Apple Message framework v1278) X-Mailer: Apple Mail (2.1278) Subject: [Xen-users] Dom0 crashed when rebooting whilst DomU are running X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org Hello, when for example the Dom0 needs to be rebooted manually and several DomU's are running, the Dom0 will crash during shutdown, that just a Manual Hardware Reset will help to reboot. Current HVM is: Xen 4.1.3 Current Kernel: 2.6.32-5-xen-amd64 Is there a know issue, or what might could case this issue. When rebooting the Dom0 without having at least one DomU running, then the reboot is successful. Can someone help me? Thanks. Cheers, Maik _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Mon Sep 03 16:21:09 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Mon, 03 Sep 2012 16:21:09 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1T8ZNW-0006It-42; Mon, 03 Sep 2012 16:19:58 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1T8ZNU-0006Il-Cx for Xen-users@lists.xen.org; Mon, 03 Sep 2012 16:19:56 +0000 Received: from [85.158.143.35:33217] by server-3.bemta-4.messagelabs.com id AF/3E-08232-BA8D4405; Mon, 03 Sep 2012 16:19:55 +0000 X-Env-Sender: lists@dadigi.com X-Msg-Ref: server-7.tower-21.messagelabs.com!1346689194!12004190!1 X-Originating-IP: [212.227.17.10] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogMjEyLjIyNy4xNy4xMCA9PiA3MjU0NA==\n X-StarScan-Received: X-StarScan-Version: 6.6.1.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 16062 invoked from network); 3 Sep 2012 16:19:54 -0000 Received: from moutng.kundenserver.de (HELO moutng.kundenserver.de) (212.227.17.10) by server-7.tower-21.messagelabs.com with SMTP; 3 Sep 2012 16:19:54 -0000 Received: from [10.10.10.5] (e180140056.adsl.alicedsl.de [85.180.140.56]) by mrelayeu.kundenserver.de (node=mreu4) with ESMTP (Nemesis) id 0LZpVp-1TrpoN03m1-00llfo; Mon, 03 Sep 2012 18:19:54 +0200 Message-ID: <5044D8A9.6090604@dadigi.com> Date: Mon, 03 Sep 2012 18:19:53 +0200 From: Daniel Di Giacomo User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:15.0) Gecko/20120827 Thunderbird/15.0 MIME-Version: 1.0 To: Xen-users@lists.xen.org X-Enigmail-Version: 1.4.4 X-Provags-ID: V02:K0:4vByo8xpZvVhm9f75qZ0oiFrTiWMUVHSjStSjSxqo1G Qi3gurlS9hd/IxGgb6nxXw/peBRRn4ONLxAADdpezyVeG6eWJ5 N3z+DUiDNGXbe/7h5LRuUc0PwfMwlXZTxDiBosxNrAoy/J9las dB+Eq0ob69xczvrtKyC5Vzv5fYys28KTxgDuq2L10guJH3zI63 IrLjjVAeaQZayWq29MFaFGkwW0G9xLap7dcZQuJO7drhPNY1kg zeRy6alCSzgJh1nTI/POtX/w1e2ix/FNhgUO8XuwM/stAg2Wa1 ThpdktSTvjEC74u9wM7Tj/mJ2s/p9yOb4PTLEZpGT0dfQi7pBk r1HJlNooIEa7Ap5zkyUA= Subject: Re: [Xen-users] [Xen-devel] PCI passthrough for domU allocated with more than 4G memory X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Same problem here. I'm using gentoo with kernel 3.5.3 (gentoo-sources) and XEN 4.1.2 as dom0. DomU is also gentoo with the same kernel version. When I assign more than 4G memory to this domU, the memory for the passed-through Intel-gigabit-nic cannot be allocated and the initialization of the device fails. With 3968M memory assigned everything works fine. Assigning 8GB RAM to domU works without any problems, when I use the old kernel-version 2.6.34 (xen-sources) in domU. Regards Daniel -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.11 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://www.enigmail.net/ iQIcBAEBAgAGBQJQRNihAAoJEO8IGUBgh06fLYIP/jfEaf/edX2y9zsNOH1V21pD g7B1zXSTyDEbgelvmo6mVmAIM4UYLIeiPQVtjzBnJ1XPmTzwyPj9rUaq2HspyRE5 9Nq6Iy/57ZnleApPUpr2I972EDHdBWnW4z8Z8G+OuN7ONWAitbG6EabYAyLXPnq+ M/owPRGvw5U6rJNlO5/KBN3LYWOE0YYd1Chq+AX0KpJJ2pXbCB6JukAuLi22XE74 gJWRnUsOTXbiHLJfImLBb0A8piDDxcal2i5SjebEGjNMC7HX5uN0xo2LbX4Xr/vo oHDn7vHmE3GpMSImJD0v0ZHc8wrSYTCO6Wc4h5WYEM4rB1EcWgv+2zyg0cBlGHG/ fjRGEYdCr4g1yYrRg4gPO72WlIncvPh9TxoUloV4vSG/NuNfW/LGyewVQ9Y4Ykb2 oOm2vH0xSZxFLjfxCS+Nnzu9yH5OJi+5R0felDGsg/wd7O+QAbUNYzTkHKufoXvM q1bGwRFs6abFYTg8/wtMNU7j53uvkVaCZJN6o04m75WgVcjOgFPtFD5IwowVI0Iu jbWtcN1WPoSPExXnZXXoBSUpmGYzK7FDFUu9ckEJoYsfR7L4u1QQ469nkaLlypF0 v3SPl/vS/sDhIlvwKgwOYSA2KEe2QouJ6hJa27Gswo42lVj57L/BaRnBDIGJ9T8Y PY5B44ZtQkpCCwVVJeZD =STDs -----END PGP SIGNATURE----- _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Mon Sep 03 16:21:09 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Mon, 03 Sep 2012 16:21:09 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1T8ZNW-0006It-42; Mon, 03 Sep 2012 16:19:58 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1T8ZNU-0006Il-Cx for Xen-users@lists.xen.org; Mon, 03 Sep 2012 16:19:56 +0000 Received: from [85.158.143.35:33217] by server-3.bemta-4.messagelabs.com id AF/3E-08232-BA8D4405; Mon, 03 Sep 2012 16:19:55 +0000 X-Env-Sender: lists@dadigi.com X-Msg-Ref: server-7.tower-21.messagelabs.com!1346689194!12004190!1 X-Originating-IP: [212.227.17.10] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogMjEyLjIyNy4xNy4xMCA9PiA3MjU0NA==\n X-StarScan-Received: X-StarScan-Version: 6.6.1.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 16062 invoked from network); 3 Sep 2012 16:19:54 -0000 Received: from moutng.kundenserver.de (HELO moutng.kundenserver.de) (212.227.17.10) by server-7.tower-21.messagelabs.com with SMTP; 3 Sep 2012 16:19:54 -0000 Received: from [10.10.10.5] (e180140056.adsl.alicedsl.de [85.180.140.56]) by mrelayeu.kundenserver.de (node=mreu4) with ESMTP (Nemesis) id 0LZpVp-1TrpoN03m1-00llfo; Mon, 03 Sep 2012 18:19:54 +0200 Message-ID: <5044D8A9.6090604@dadigi.com> Date: Mon, 03 Sep 2012 18:19:53 +0200 From: Daniel Di Giacomo User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:15.0) Gecko/20120827 Thunderbird/15.0 MIME-Version: 1.0 To: Xen-users@lists.xen.org X-Enigmail-Version: 1.4.4 X-Provags-ID: V02:K0:4vByo8xpZvVhm9f75qZ0oiFrTiWMUVHSjStSjSxqo1G Qi3gurlS9hd/IxGgb6nxXw/peBRRn4ONLxAADdpezyVeG6eWJ5 N3z+DUiDNGXbe/7h5LRuUc0PwfMwlXZTxDiBosxNrAoy/J9las dB+Eq0ob69xczvrtKyC5Vzv5fYys28KTxgDuq2L10guJH3zI63 IrLjjVAeaQZayWq29MFaFGkwW0G9xLap7dcZQuJO7drhPNY1kg zeRy6alCSzgJh1nTI/POtX/w1e2ix/FNhgUO8XuwM/stAg2Wa1 ThpdktSTvjEC74u9wM7Tj/mJ2s/p9yOb4PTLEZpGT0dfQi7pBk r1HJlNooIEa7Ap5zkyUA= Subject: Re: [Xen-users] [Xen-devel] PCI passthrough for domU allocated with more than 4G memory X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Same problem here. I'm using gentoo with kernel 3.5.3 (gentoo-sources) and XEN 4.1.2 as dom0. DomU is also gentoo with the same kernel version. When I assign more than 4G memory to this domU, the memory for the passed-through Intel-gigabit-nic cannot be allocated and the initialization of the device fails. With 3968M memory assigned everything works fine. Assigning 8GB RAM to domU works without any problems, when I use the old kernel-version 2.6.34 (xen-sources) in domU. Regards Daniel -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.11 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://www.enigmail.net/ iQIcBAEBAgAGBQJQRNihAAoJEO8IGUBgh06fLYIP/jfEaf/edX2y9zsNOH1V21pD g7B1zXSTyDEbgelvmo6mVmAIM4UYLIeiPQVtjzBnJ1XPmTzwyPj9rUaq2HspyRE5 9Nq6Iy/57ZnleApPUpr2I972EDHdBWnW4z8Z8G+OuN7ONWAitbG6EabYAyLXPnq+ M/owPRGvw5U6rJNlO5/KBN3LYWOE0YYd1Chq+AX0KpJJ2pXbCB6JukAuLi22XE74 gJWRnUsOTXbiHLJfImLBb0A8piDDxcal2i5SjebEGjNMC7HX5uN0xo2LbX4Xr/vo oHDn7vHmE3GpMSImJD0v0ZHc8wrSYTCO6Wc4h5WYEM4rB1EcWgv+2zyg0cBlGHG/ fjRGEYdCr4g1yYrRg4gPO72WlIncvPh9TxoUloV4vSG/NuNfW/LGyewVQ9Y4Ykb2 oOm2vH0xSZxFLjfxCS+Nnzu9yH5OJi+5R0felDGsg/wd7O+QAbUNYzTkHKufoXvM q1bGwRFs6abFYTg8/wtMNU7j53uvkVaCZJN6o04m75WgVcjOgFPtFD5IwowVI0Iu jbWtcN1WPoSPExXnZXXoBSUpmGYzK7FDFUu9ckEJoYsfR7L4u1QQ469nkaLlypF0 v3SPl/vS/sDhIlvwKgwOYSA2KEe2QouJ6hJa27Gswo42lVj57L/BaRnBDIGJ9T8Y PY5B44ZtQkpCCwVVJeZD =STDs -----END PGP SIGNATURE----- _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Mon Sep 03 16:28:15 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Mon, 03 Sep 2012 16:28:15 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1T8ZUY-0006le-Tk; Mon, 03 Sep 2012 16:27:14 +0000 Received: from mail27.messagelabs.com ([193.109.254.147]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1T8ZUX-0006l4-2q for xen-users@lists.xen.org; Mon, 03 Sep 2012 16:27:13 +0000 X-Env-Sender: cdelorme@gmail.com X-Msg-Ref: server-12.tower-27.messagelabs.com!1346689624!9382732!1 X-Originating-IP: [209.85.214.173] X-SpamReason: No, hits=0.4 required=7.0 tests=HTML_30_40,HTML_MESSAGE, ML_RADAR_SPEW_LINKS_14,RCVD_BY_IP,spamassassin: X-StarScan-Received: X-StarScan-Version: 6.6.1.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 14829 invoked from network); 3 Sep 2012 16:27:05 -0000 Received: from mail-ob0-f173.google.com (HELO mail-ob0-f173.google.com) (209.85.214.173) by server-12.tower-27.messagelabs.com with RC4-SHA encrypted SMTP; 3 Sep 2012 16:27:05 -0000 Received: by obbta14 with SMTP id ta14so12415435obb.32 for ; Mon, 03 Sep 2012 09:27:04 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=xfRuFVy88slgeqkNBExJnELFCQIT9OHmwpgGW4Yyn/I=; b=cnlcbcf8kh1RtNMnRTOTSPhKwTTeX8iDAceaFohpee8iFYnZ4ubZ6/lTKERddgw9EU HNYK8XnK+OTy05Pmr4A/qaiQORVWvW6fY5mdRxX3QKP1ZQ3A3j3i0xTTBl14XAdCiVnj UiW6IyZcZYm7c8Give+otoIroZpm2jLLIdblASgs11k/y7b8oKoNbwu30cgGPrBLevvL zfFkJOlqo0blr2qcXeotLDW4Gh6Jx1jkstnhA3kNtQPOMcK1dzO8WimirnjJ7vjRpXO/ PURr9I0xmXQunRbGYoB//QmyNDy8Ows8+53l93UbX5Ga8T3oDNpPcBqPtnZC1HtkhSID K++Q== MIME-Version: 1.0 Received: by 10.182.131.98 with SMTP id ol2mr14200937obb.69.1346689624165; Mon, 03 Sep 2012 09:27:04 -0700 (PDT) Received: by 10.76.115.197 with HTTP; Mon, 3 Sep 2012 09:27:04 -0700 (PDT) In-Reply-To: References: Date: Mon, 3 Sep 2012 12:27:04 -0400 Message-ID: From: Casey DeLorme To: Maik Brauer Cc: xen-users@lists.xen.org Subject: Re: [Xen-users] Dom0 crashed when rebooting whilst DomU are running X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============2264709884011642812==" Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org --===============2264709884011642812== Content-Type: multipart/alternative; boundary=e89a8f5028beabce5a04c8ce9c37 --e89a8f5028beabce5a04c8ce9c37 Content-Type: text/plain; charset=ISO-8859-1 This could have changed, but I am fairly certain rebooting Dom0 reboots Xen, hence any running DomU's will have to be shutdown. A 2010 reference: http://old-list-archives.xen.org/archives/html/xen-users/2010-04/msg00710.html You could always try running aliasing the shutdown command to shutdown all running domU's by name, but otherwise forcing them to shutdown as Dom0 does could damage your data. On Mon, Sep 3, 2012 at 7:49 AM, Maik Brauer wrote: > Hello, > > when for example the Dom0 needs to be rebooted manually and several DomU's > are running, > the Dom0 will crash during shutdown, that just a Manual Hardware Reset > will help to reboot. > > Current HVM is: Xen 4.1.3 > Current Kernel: 2.6.32-5-xen-amd64 > > Is there a know issue, or what might could case this issue. > When rebooting the Dom0 without having at least one DomU running, then the > reboot is successful. > Can someone help me? > Thanks. > > Cheers, > Maik > > > _______________________________________________ > Xen-users mailing list > Xen-users@lists.xen.org > http://lists.xen.org/xen-users > --e89a8f5028beabce5a04c8ce9c37 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable
This could have changed, but I am fairly certain rebooting Dom0 reboot= s Xen, hence any running DomU's will have to be shutdown.
A 2010 reference:

You could always try running aliasing the shutdown comm= and to shutdown all running domU's by name, but otherwise forcing them = to shutdown as Dom0 does could damage your data.

On Mon, Sep 3, 2012 at 7:49 AM, Maik Brauer <maik.brauer@mbs-s= ystems.net> wrote:
Hello,

when for example the Dom0 needs to be rebooted manually and several DomU= 9;s are running,
the Dom0 will crash during shutdown, that just a Manual Hardware Reset will= help to reboot.

Current HVM is: Xen 4.1.3
Current Kernel: 2.6.32-5-xen-amd64

Is there a know issue, or what might could case this issue.
When rebooting the Dom0 without having at least one DomU running, then the = reboot is successful.
Can someone help me?
Thanks.

Cheers,
Maik


_______________________________________________
Xen-users mailing list
Xen-users@lists.xen.org
http://lists.x= en.org/xen-users

--e89a8f5028beabce5a04c8ce9c37-- --===============2264709884011642812== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users --===============2264709884011642812==-- From xen-users-bounces@lists.xen.org Mon Sep 03 16:28:15 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Mon, 03 Sep 2012 16:28:15 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1T8ZUY-0006le-Tk; Mon, 03 Sep 2012 16:27:14 +0000 Received: from mail27.messagelabs.com ([193.109.254.147]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1T8ZUX-0006l4-2q for xen-users@lists.xen.org; Mon, 03 Sep 2012 16:27:13 +0000 X-Env-Sender: cdelorme@gmail.com X-Msg-Ref: server-12.tower-27.messagelabs.com!1346689624!9382732!1 X-Originating-IP: [209.85.214.173] X-SpamReason: No, hits=0.4 required=7.0 tests=HTML_30_40,HTML_MESSAGE, ML_RADAR_SPEW_LINKS_14,RCVD_BY_IP,spamassassin: X-StarScan-Received: X-StarScan-Version: 6.6.1.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 14829 invoked from network); 3 Sep 2012 16:27:05 -0000 Received: from mail-ob0-f173.google.com (HELO mail-ob0-f173.google.com) (209.85.214.173) by server-12.tower-27.messagelabs.com with RC4-SHA encrypted SMTP; 3 Sep 2012 16:27:05 -0000 Received: by obbta14 with SMTP id ta14so12415435obb.32 for ; Mon, 03 Sep 2012 09:27:04 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=xfRuFVy88slgeqkNBExJnELFCQIT9OHmwpgGW4Yyn/I=; b=cnlcbcf8kh1RtNMnRTOTSPhKwTTeX8iDAceaFohpee8iFYnZ4ubZ6/lTKERddgw9EU HNYK8XnK+OTy05Pmr4A/qaiQORVWvW6fY5mdRxX3QKP1ZQ3A3j3i0xTTBl14XAdCiVnj UiW6IyZcZYm7c8Give+otoIroZpm2jLLIdblASgs11k/y7b8oKoNbwu30cgGPrBLevvL zfFkJOlqo0blr2qcXeotLDW4Gh6Jx1jkstnhA3kNtQPOMcK1dzO8WimirnjJ7vjRpXO/ PURr9I0xmXQunRbGYoB//QmyNDy8Ows8+53l93UbX5Ga8T3oDNpPcBqPtnZC1HtkhSID K++Q== MIME-Version: 1.0 Received: by 10.182.131.98 with SMTP id ol2mr14200937obb.69.1346689624165; Mon, 03 Sep 2012 09:27:04 -0700 (PDT) Received: by 10.76.115.197 with HTTP; Mon, 3 Sep 2012 09:27:04 -0700 (PDT) In-Reply-To: References: Date: Mon, 3 Sep 2012 12:27:04 -0400 Message-ID: From: Casey DeLorme To: Maik Brauer Cc: xen-users@lists.xen.org Subject: Re: [Xen-users] Dom0 crashed when rebooting whilst DomU are running X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============2264709884011642812==" Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org --===============2264709884011642812== Content-Type: multipart/alternative; boundary=e89a8f5028beabce5a04c8ce9c37 --e89a8f5028beabce5a04c8ce9c37 Content-Type: text/plain; charset=ISO-8859-1 This could have changed, but I am fairly certain rebooting Dom0 reboots Xen, hence any running DomU's will have to be shutdown. A 2010 reference: http://old-list-archives.xen.org/archives/html/xen-users/2010-04/msg00710.html You could always try running aliasing the shutdown command to shutdown all running domU's by name, but otherwise forcing them to shutdown as Dom0 does could damage your data. On Mon, Sep 3, 2012 at 7:49 AM, Maik Brauer wrote: > Hello, > > when for example the Dom0 needs to be rebooted manually and several DomU's > are running, > the Dom0 will crash during shutdown, that just a Manual Hardware Reset > will help to reboot. > > Current HVM is: Xen 4.1.3 > Current Kernel: 2.6.32-5-xen-amd64 > > Is there a know issue, or what might could case this issue. > When rebooting the Dom0 without having at least one DomU running, then the > reboot is successful. > Can someone help me? > Thanks. > > Cheers, > Maik > > > _______________________________________________ > Xen-users mailing list > Xen-users@lists.xen.org > http://lists.xen.org/xen-users > --e89a8f5028beabce5a04c8ce9c37 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable
This could have changed, but I am fairly certain rebooting Dom0 reboot= s Xen, hence any running DomU's will have to be shutdown.
A 2010 reference:

You could always try running aliasing the shutdown comm= and to shutdown all running domU's by name, but otherwise forcing them = to shutdown as Dom0 does could damage your data.

On Mon, Sep 3, 2012 at 7:49 AM, Maik Brauer <maik.brauer@mbs-s= ystems.net> wrote:
Hello,

when for example the Dom0 needs to be rebooted manually and several DomU= 9;s are running,
the Dom0 will crash during shutdown, that just a Manual Hardware Reset will= help to reboot.

Current HVM is: Xen 4.1.3
Current Kernel: 2.6.32-5-xen-amd64

Is there a know issue, or what might could case this issue.
When rebooting the Dom0 without having at least one DomU running, then the = reboot is successful.
Can someone help me?
Thanks.

Cheers,
Maik


_______________________________________________
Xen-users mailing list
Xen-users@lists.xen.org
http://lists.x= en.org/xen-users

--e89a8f5028beabce5a04c8ce9c37-- --===============2264709884011642812== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users --===============2264709884011642812==-- From xen-users-bounces@lists.xen.org Mon Sep 03 16:42:18 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Mon, 03 Sep 2012 16:42:18 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1T8ZiK-0007H5-J6; Mon, 03 Sep 2012 16:41:28 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1T8ZiJ-0007H0-Gy for xen-users@lists.xen.org; Mon, 03 Sep 2012 16:41:27 +0000 Received: from [85.158.143.35:43360] by server-3.bemta-4.messagelabs.com id 33/64-08232-6BDD4405; Mon, 03 Sep 2012 16:41:26 +0000 X-Env-Sender: maik.brauer@mbs-systems.net X-Msg-Ref: server-9.tower-21.messagelabs.com!1346690484!5412597!1 X-Originating-IP: [188.40.240.248] X-SpamReason: No, hits=0.1 required=7.0 tests=HTML_30_40,HTML_MESSAGE X-StarScan-Received: X-StarScan-Version: 6.6.1.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 19492 invoked from network); 3 Sep 2012 16:41:25 -0000 Received: from mx1.mbs-systems.net (HELO mx1.mbs-systems.net) (188.40.240.248) by server-9.tower-21.messagelabs.com with SMTP; 3 Sep 2012 16:41:25 -0000 Received: from localhost (localhost [127.0.0.1]) by mx1.mbs-systems.net (Postfix) with ESMTP id C69CE5C30B; Mon, 3 Sep 2012 18:42:18 +0200 (CEST) Received: from mx1.mbs-systems.net ([127.0.0.1]) by localhost (mta.mbs-systems.net [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id koT-AAL6BFnd; Mon, 3 Sep 2012 18:42:17 +0200 (CEST) Received: from [172.16.11.41] (dslb-178-009-089-188.pools.arcor-ip.net [178.9.89.188]) by mx1.mbs-systems.net (Postfix) with ESMTPSA id BD2DC5C221; Mon, 3 Sep 2012 18:42:17 +0200 (CEST) Mime-Version: 1.0 (Apple Message framework v1278) From: Maik Brauer In-Reply-To: Date: Mon, 3 Sep 2012 18:41:21 +0200 Message-Id: <9F8FD2B0-450A-4A6E-A929-BA240ED1D997@mbs-systems.net> References: To: Casey DeLorme X-Mailer: Apple Mail (2.1278) Cc: xen-users@lists.xen.org Subject: Re: [Xen-users] Dom0 crashed when rebooting whilst DomU are running X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============1466454171463226915==" Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org --===============1466454171463226915== Content-Type: multipart/alternative; boundary="Apple-Mail=_EA7E26E1-87FE-43B8-9AFF-69F5A6040825" --Apple-Mail=_EA7E26E1-87FE-43B8-9AFF-69F5A6040825 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=iso-8859-1 Hi, that is true, I understand that, but at least if the Dom0 is rebooting = and will destroy the DomU's, the Dom0 itself should not crash and hang that a Hard-reset is needed to = reboot. Is there not any shutdown control, which can shutdown the DomU's from = the Dom0 automatically in case of reboot or shutdown? When I manually shutdown all DomU's before rebooting Dom0, then the Dom0 = will reboot and come up again. On Sep 3, 2012, at 6:27 PM, Casey DeLorme wrote: > This could have changed, but I am fairly certain rebooting Dom0 = reboots Xen, hence any running DomU's will have to be shutdown. >=20 > A 2010 reference: > = http://old-list-archives.xen.org/archives/html/xen-users/2010-04/msg00710.= html >=20 > You could always try running aliasing the shutdown command to shutdown = all running domU's by name, but otherwise forcing them to shutdown as = Dom0 does could damage your data. >=20 > On Mon, Sep 3, 2012 at 7:49 AM, Maik Brauer = wrote: > Hello, >=20 > when for example the Dom0 needs to be rebooted manually and several = DomU's are running, > the Dom0 will crash during shutdown, that just a Manual Hardware Reset = will help to reboot. >=20 > Current HVM is: Xen 4.1.3 > Current Kernel: 2.6.32-5-xen-amd64 >=20 > Is there a know issue, or what might could case this issue. > When rebooting the Dom0 without having at least one DomU running, then = the reboot is successful. > Can someone help me? > Thanks. >=20 > Cheers, > Maik >=20 >=20 > _______________________________________________ > Xen-users mailing list > Xen-users@lists.xen.org > http://lists.xen.org/xen-users >=20 > _______________________________________________ > Xen-users mailing list > Xen-users@lists.xen.org > http://lists.xen.org/xen-users --Apple-Mail=_EA7E26E1-87FE-43B8-9AFF-69F5A6040825 Content-Transfer-Encoding: quoted-printable Content-Type: text/html; charset=iso-8859-1
This = could have changed, but I am fairly certain rebooting Dom0 reboots Xen, = hence any running DomU's will have to be = shutdown.

A 2010 reference:

You could always try running aliasing the shutdown = command to shutdown all running domU's by name, but otherwise forcing = them to shutdown as Dom0 does could damage your data.

On Mon, Sep 3, 2012 at 7:49 AM, Maik Brauer <maik.brauer@mbs-systems.net> = wrote:
Hello,

when for example the Dom0 needs to be rebooted manually and several = DomU's are running,
the Dom0 will crash during shutdown, that just a Manual Hardware Reset = will help to reboot.

Current HVM is: Xen 4.1.3
Current Kernel: 2.6.32-5-xen-amd64

Is there a know issue, or what might could case this issue.
When rebooting the Dom0 without having at least one DomU running, then = the reboot is successful.
Can someone help me?
Thanks.

Cheers,
Maik


_______________________________________________
Xen-users mailing list
Xen-users@lists.xen.org
= http://lists.xen.org/xen-users

_______________________________________________
Xen-users mailing = list
Xen-users@lists.xen.org
htt= p://lists.xen.org/xen-users


= --Apple-Mail=_EA7E26E1-87FE-43B8-9AFF-69F5A6040825-- --===============1466454171463226915== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users --===============1466454171463226915==-- From xen-users-bounces@lists.xen.org Mon Sep 03 16:42:18 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Mon, 03 Sep 2012 16:42:18 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1T8ZiK-0007H5-J6; Mon, 03 Sep 2012 16:41:28 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1T8ZiJ-0007H0-Gy for xen-users@lists.xen.org; Mon, 03 Sep 2012 16:41:27 +0000 Received: from [85.158.143.35:43360] by server-3.bemta-4.messagelabs.com id 33/64-08232-6BDD4405; Mon, 03 Sep 2012 16:41:26 +0000 X-Env-Sender: maik.brauer@mbs-systems.net X-Msg-Ref: server-9.tower-21.messagelabs.com!1346690484!5412597!1 X-Originating-IP: [188.40.240.248] X-SpamReason: No, hits=0.1 required=7.0 tests=HTML_30_40,HTML_MESSAGE X-StarScan-Received: X-StarScan-Version: 6.6.1.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 19492 invoked from network); 3 Sep 2012 16:41:25 -0000 Received: from mx1.mbs-systems.net (HELO mx1.mbs-systems.net) (188.40.240.248) by server-9.tower-21.messagelabs.com with SMTP; 3 Sep 2012 16:41:25 -0000 Received: from localhost (localhost [127.0.0.1]) by mx1.mbs-systems.net (Postfix) with ESMTP id C69CE5C30B; Mon, 3 Sep 2012 18:42:18 +0200 (CEST) Received: from mx1.mbs-systems.net ([127.0.0.1]) by localhost (mta.mbs-systems.net [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id koT-AAL6BFnd; Mon, 3 Sep 2012 18:42:17 +0200 (CEST) Received: from [172.16.11.41] (dslb-178-009-089-188.pools.arcor-ip.net [178.9.89.188]) by mx1.mbs-systems.net (Postfix) with ESMTPSA id BD2DC5C221; Mon, 3 Sep 2012 18:42:17 +0200 (CEST) Mime-Version: 1.0 (Apple Message framework v1278) From: Maik Brauer In-Reply-To: Date: Mon, 3 Sep 2012 18:41:21 +0200 Message-Id: <9F8FD2B0-450A-4A6E-A929-BA240ED1D997@mbs-systems.net> References: To: Casey DeLorme X-Mailer: Apple Mail (2.1278) Cc: xen-users@lists.xen.org Subject: Re: [Xen-users] Dom0 crashed when rebooting whilst DomU are running X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============1466454171463226915==" Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org --===============1466454171463226915== Content-Type: multipart/alternative; boundary="Apple-Mail=_EA7E26E1-87FE-43B8-9AFF-69F5A6040825" --Apple-Mail=_EA7E26E1-87FE-43B8-9AFF-69F5A6040825 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=iso-8859-1 Hi, that is true, I understand that, but at least if the Dom0 is rebooting = and will destroy the DomU's, the Dom0 itself should not crash and hang that a Hard-reset is needed to = reboot. Is there not any shutdown control, which can shutdown the DomU's from = the Dom0 automatically in case of reboot or shutdown? When I manually shutdown all DomU's before rebooting Dom0, then the Dom0 = will reboot and come up again. On Sep 3, 2012, at 6:27 PM, Casey DeLorme wrote: > This could have changed, but I am fairly certain rebooting Dom0 = reboots Xen, hence any running DomU's will have to be shutdown. >=20 > A 2010 reference: > = http://old-list-archives.xen.org/archives/html/xen-users/2010-04/msg00710.= html >=20 > You could always try running aliasing the shutdown command to shutdown = all running domU's by name, but otherwise forcing them to shutdown as = Dom0 does could damage your data. >=20 > On Mon, Sep 3, 2012 at 7:49 AM, Maik Brauer = wrote: > Hello, >=20 > when for example the Dom0 needs to be rebooted manually and several = DomU's are running, > the Dom0 will crash during shutdown, that just a Manual Hardware Reset = will help to reboot. >=20 > Current HVM is: Xen 4.1.3 > Current Kernel: 2.6.32-5-xen-amd64 >=20 > Is there a know issue, or what might could case this issue. > When rebooting the Dom0 without having at least one DomU running, then = the reboot is successful. > Can someone help me? > Thanks. >=20 > Cheers, > Maik >=20 >=20 > _______________________________________________ > Xen-users mailing list > Xen-users@lists.xen.org > http://lists.xen.org/xen-users >=20 > _______________________________________________ > Xen-users mailing list > Xen-users@lists.xen.org > http://lists.xen.org/xen-users --Apple-Mail=_EA7E26E1-87FE-43B8-9AFF-69F5A6040825 Content-Transfer-Encoding: quoted-printable Content-Type: text/html; charset=iso-8859-1
This = could have changed, but I am fairly certain rebooting Dom0 reboots Xen, = hence any running DomU's will have to be = shutdown.

A 2010 reference:

You could always try running aliasing the shutdown = command to shutdown all running domU's by name, but otherwise forcing = them to shutdown as Dom0 does could damage your data.

On Mon, Sep 3, 2012 at 7:49 AM, Maik Brauer <maik.brauer@mbs-systems.net> = wrote:
Hello,

when for example the Dom0 needs to be rebooted manually and several = DomU's are running,
the Dom0 will crash during shutdown, that just a Manual Hardware Reset = will help to reboot.

Current HVM is: Xen 4.1.3
Current Kernel: 2.6.32-5-xen-amd64

Is there a know issue, or what might could case this issue.
When rebooting the Dom0 without having at least one DomU running, then = the reboot is successful.
Can someone help me?
Thanks.

Cheers,
Maik


_______________________________________________
Xen-users mailing list
Xen-users@lists.xen.org
= http://lists.xen.org/xen-users

_______________________________________________
Xen-users mailing = list
Xen-users@lists.xen.org
htt= p://lists.xen.org/xen-users


= --Apple-Mail=_EA7E26E1-87FE-43B8-9AFF-69F5A6040825-- --===============1466454171463226915== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users --===============1466454171463226915==-- From xen-users-bounces@lists.xen.org Mon Sep 03 17:11:00 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Mon, 03 Sep 2012 17:11:00 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1T8aA2-0007ic-Ab; Mon, 03 Sep 2012 17:10:06 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1T8aA0-0007iX-FG for xen-users@lists.xen.org; Mon, 03 Sep 2012 17:10:04 +0000 Received: from [85.158.143.35:38486] by server-1.bemta-4.messagelabs.com id DE/6A-12504-B64E4405; Mon, 03 Sep 2012 17:10:03 +0000 X-Env-Sender: cdelorme@gmail.com X-Msg-Ref: server-14.tower-21.messagelabs.com!1346692200!16522674!1 X-Originating-IP: [209.85.214.173] X-SpamReason: No, hits=0.4 required=7.0 tests=HTML_30_40,HTML_MESSAGE, ML_RADAR_SPEW_LINKS_14,RCVD_BY_IP,spamassassin: X-StarScan-Received: X-StarScan-Version: 6.6.1.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 14443 invoked from network); 3 Sep 2012 17:10:01 -0000 Received: from mail-ob0-f173.google.com (HELO mail-ob0-f173.google.com) (209.85.214.173) by server-14.tower-21.messagelabs.com with RC4-SHA encrypted SMTP; 3 Sep 2012 17:10:01 -0000 Received: by obbta14 with SMTP id ta14so12499742obb.32 for ; Mon, 03 Sep 2012 10:10:00 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=VWTyETKvoZfdm0n53mMQ5JgMkVRnUL6uElevISWMLh4=; b=X4fQh4AnhKE/RfohHOrgo0GO/2FoVGj1wXs0tXbndkVWsgEv/g/q29F8CKVSIgrJAo X+sQcQJpzwosAufLVpFyCJtguGLilBsDmen2XknPkdom8+tXh0GhszIbPfUsvpH6LIRP bEM8nRslZaOepSDazNMu9GPGiJj86XCI3VAtzmw2IGM5zsoXyNxCEKX1t7LuCowDfouW OV8zscqjtDcu006KRE+PS7KrEsTYqlF4SE1lw/JM+LqB7wsLPHw2jA+90m36eT7fC/AB E2UhTEZOvcE4OnlTWvEqmn4a1utnCM96q1386XwA6o1BL7agf+sAFAKVIbv7bRFlhMX9 NjCA== MIME-Version: 1.0 Received: by 10.60.154.232 with SMTP id vr8mr14181410oeb.30.1346692200269; Mon, 03 Sep 2012 10:10:00 -0700 (PDT) Received: by 10.76.115.197 with HTTP; Mon, 3 Sep 2012 10:10:00 -0700 (PDT) In-Reply-To: <9F8FD2B0-450A-4A6E-A929-BA240ED1D997@mbs-systems.net> References: <9F8FD2B0-450A-4A6E-A929-BA240ED1D997@mbs-systems.net> Date: Mon, 3 Sep 2012 13:10:00 -0400 Message-ID: From: Casey DeLorme To: Maik Brauer Cc: xen-users@lists.xen.org Subject: Re: [Xen-users] Dom0 crashed when rebooting whilst DomU are running X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============5563159482806327500==" Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org --===============5563159482806327500== Content-Type: multipart/alternative; boundary=bcaec55245ec3808c104c8cf36cc --bcaec55245ec3808c104c8cf36cc Content-Type: text/plain; charset=ISO-8859-1 As stated, you can alias shutdown to do exactly what you need, it can be as simple as a series of hard-coded operations to a complex custom shell script that parses your domains and closes each with feedback. I don't know of a specific xl toolstack solution, but if you are using the xm toolstack you can try this: http://www.novell.com/support/kb/doc.php?id=3029956 Keep in mind that without PV on HVM drivers or paravirtualized DomU's you'll have to use the `destroy` command from Dom0, which is not a graceful shutdown. On Mon, Sep 3, 2012 at 12:41 PM, Maik Brauer wrote: > Hi, > > that is true, I understand that, but at least if the Dom0 is rebooting and > will destroy the DomU's, the > Dom0 itself should not crash and hang that a Hard-reset is needed to > reboot. > > Is there not any shutdown control, which can shutdown the DomU's from the > Dom0 automatically in case of reboot or shutdown? > When I manually shutdown all DomU's before rebooting Dom0, then the Dom0 > will reboot and come up again. > > > On Sep 3, 2012, at 6:27 PM, Casey DeLorme wrote: > > This could have changed, but I am fairly certain rebooting Dom0 reboots > Xen, hence any running DomU's will have to be shutdown. > > A 2010 reference: > > http://old-list-archives.xen.org/archives/html/xen-users/2010-04/msg00710.html > > You could always try running aliasing the shutdown command to shutdown all > running domU's by name, but otherwise forcing them to shutdown as Dom0 does > could damage your data. > > On Mon, Sep 3, 2012 at 7:49 AM, Maik Brauer wrote: > >> Hello, >> >> when for example the Dom0 needs to be rebooted manually and several >> DomU's are running, >> the Dom0 will crash during shutdown, that just a Manual Hardware Reset >> will help to reboot. >> >> Current HVM is: Xen 4.1.3 >> Current Kernel: 2.6.32-5-xen-amd64 >> >> Is there a know issue, or what might could case this issue. >> When rebooting the Dom0 without having at least one DomU running, then >> the reboot is successful. >> Can someone help me? >> Thanks. >> >> Cheers, >> Maik >> >> >> _______________________________________________ >> Xen-users mailing list >> Xen-users@lists.xen.org >> http://lists.xen.org/xen-users >> > > _______________________________________________ > Xen-users mailing list > Xen-users@lists.xen.org > http://lists.xen.org/xen-users > > > > --bcaec55245ec3808c104c8cf36cc Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable
As stated, you can alias shutdown to do exactly what you need, it= can be as simple as a series of hard-coded operations to a complex custom = shell script that parses your domains and closes each with feedback.

I don't know of a specific xl toolstack solut= ion, but if you are using the xm toolstack you can try this:

Keep in mind that without PV on HVM drivers or paravirt= ualized DomU's you'll have to use the `destroy` command from Dom0, = which is not a graceful shutdown.

On Mon, Sep 3, 2012 at 12:41 PM, Maik Brauer <maik.brauer@mbs-s= ystems.net> wrote:
Hi,

that = is true, I understand that, but at least if the Dom0 is rebooting and will = destroy the DomU's, the
Dom0 itself should not crash and hang= that a Hard-reset is needed to reboot.

Is there not any shutdown control, which can shutdown t= he DomU's from the Dom0 automatically in case of reboot or shutdown?
When I manually shutdown all DomU's before rebooting Dom0, then= the Dom0 will reboot and come up again.


On Sep 3, 2012, at 6:27= PM, Casey DeLorme wrote:

This coul= d have changed, but I am fairly certain rebooting Dom0 reboots Xen, hence a= ny running DomU's will have to be shutdown.

A 2010 reference:

You could always try running aliasing the shutdown comm= and to shutdown all running domU's by name, but otherwise forcing them = to shutdown as Dom0 does could damage your data.

On Mon, Sep 3, 2012 at 7:49 AM, Maik Brauer <maik.brauer@mbs-s= ystems.net> wrote:
Hello,

when for example the Dom0 needs to be rebooted manually and several DomU= 9;s are running,
the Dom0 will crash during shutdown, that just a Manual Hardware Reset will= help to reboot.

Current HVM is: Xen 4.1.3
Current Kernel: 2.6.32-5-xen-amd64

Is there a know issue, or what might could case this issue.
When rebooting the Dom0 without having at least one DomU running, then the = reboot is successful.
Can someone help me?
Thanks.

Cheers,
Maik


_______________________________________________
Xen-users mailing list
Xen-users@list= s.xen.org
http://lists.x= en.org/xen-users

_______________________________________________
Xen-users mailing listXen-users@li= sts.xen.org
http://lists.xen.org/xen-users



--bcaec55245ec3808c104c8cf36cc-- --===============5563159482806327500== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users --===============5563159482806327500==-- From xen-users-bounces@lists.xen.org Mon Sep 03 17:11:00 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Mon, 03 Sep 2012 17:11:00 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1T8aA2-0007ic-Ab; Mon, 03 Sep 2012 17:10:06 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1T8aA0-0007iX-FG for xen-users@lists.xen.org; Mon, 03 Sep 2012 17:10:04 +0000 Received: from [85.158.143.35:38486] by server-1.bemta-4.messagelabs.com id DE/6A-12504-B64E4405; Mon, 03 Sep 2012 17:10:03 +0000 X-Env-Sender: cdelorme@gmail.com X-Msg-Ref: server-14.tower-21.messagelabs.com!1346692200!16522674!1 X-Originating-IP: [209.85.214.173] X-SpamReason: No, hits=0.4 required=7.0 tests=HTML_30_40,HTML_MESSAGE, ML_RADAR_SPEW_LINKS_14,RCVD_BY_IP,spamassassin: X-StarScan-Received: X-StarScan-Version: 6.6.1.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 14443 invoked from network); 3 Sep 2012 17:10:01 -0000 Received: from mail-ob0-f173.google.com (HELO mail-ob0-f173.google.com) (209.85.214.173) by server-14.tower-21.messagelabs.com with RC4-SHA encrypted SMTP; 3 Sep 2012 17:10:01 -0000 Received: by obbta14 with SMTP id ta14so12499742obb.32 for ; Mon, 03 Sep 2012 10:10:00 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=VWTyETKvoZfdm0n53mMQ5JgMkVRnUL6uElevISWMLh4=; b=X4fQh4AnhKE/RfohHOrgo0GO/2FoVGj1wXs0tXbndkVWsgEv/g/q29F8CKVSIgrJAo X+sQcQJpzwosAufLVpFyCJtguGLilBsDmen2XknPkdom8+tXh0GhszIbPfUsvpH6LIRP bEM8nRslZaOepSDazNMu9GPGiJj86XCI3VAtzmw2IGM5zsoXyNxCEKX1t7LuCowDfouW OV8zscqjtDcu006KRE+PS7KrEsTYqlF4SE1lw/JM+LqB7wsLPHw2jA+90m36eT7fC/AB E2UhTEZOvcE4OnlTWvEqmn4a1utnCM96q1386XwA6o1BL7agf+sAFAKVIbv7bRFlhMX9 NjCA== MIME-Version: 1.0 Received: by 10.60.154.232 with SMTP id vr8mr14181410oeb.30.1346692200269; Mon, 03 Sep 2012 10:10:00 -0700 (PDT) Received: by 10.76.115.197 with HTTP; Mon, 3 Sep 2012 10:10:00 -0700 (PDT) In-Reply-To: <9F8FD2B0-450A-4A6E-A929-BA240ED1D997@mbs-systems.net> References: <9F8FD2B0-450A-4A6E-A929-BA240ED1D997@mbs-systems.net> Date: Mon, 3 Sep 2012 13:10:00 -0400 Message-ID: From: Casey DeLorme To: Maik Brauer Cc: xen-users@lists.xen.org Subject: Re: [Xen-users] Dom0 crashed when rebooting whilst DomU are running X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============5563159482806327500==" Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org --===============5563159482806327500== Content-Type: multipart/alternative; boundary=bcaec55245ec3808c104c8cf36cc --bcaec55245ec3808c104c8cf36cc Content-Type: text/plain; charset=ISO-8859-1 As stated, you can alias shutdown to do exactly what you need, it can be as simple as a series of hard-coded operations to a complex custom shell script that parses your domains and closes each with feedback. I don't know of a specific xl toolstack solution, but if you are using the xm toolstack you can try this: http://www.novell.com/support/kb/doc.php?id=3029956 Keep in mind that without PV on HVM drivers or paravirtualized DomU's you'll have to use the `destroy` command from Dom0, which is not a graceful shutdown. On Mon, Sep 3, 2012 at 12:41 PM, Maik Brauer wrote: > Hi, > > that is true, I understand that, but at least if the Dom0 is rebooting and > will destroy the DomU's, the > Dom0 itself should not crash and hang that a Hard-reset is needed to > reboot. > > Is there not any shutdown control, which can shutdown the DomU's from the > Dom0 automatically in case of reboot or shutdown? > When I manually shutdown all DomU's before rebooting Dom0, then the Dom0 > will reboot and come up again. > > > On Sep 3, 2012, at 6:27 PM, Casey DeLorme wrote: > > This could have changed, but I am fairly certain rebooting Dom0 reboots > Xen, hence any running DomU's will have to be shutdown. > > A 2010 reference: > > http://old-list-archives.xen.org/archives/html/xen-users/2010-04/msg00710.html > > You could always try running aliasing the shutdown command to shutdown all > running domU's by name, but otherwise forcing them to shutdown as Dom0 does > could damage your data. > > On Mon, Sep 3, 2012 at 7:49 AM, Maik Brauer wrote: > >> Hello, >> >> when for example the Dom0 needs to be rebooted manually and several >> DomU's are running, >> the Dom0 will crash during shutdown, that just a Manual Hardware Reset >> will help to reboot. >> >> Current HVM is: Xen 4.1.3 >> Current Kernel: 2.6.32-5-xen-amd64 >> >> Is there a know issue, or what might could case this issue. >> When rebooting the Dom0 without having at least one DomU running, then >> the reboot is successful. >> Can someone help me? >> Thanks. >> >> Cheers, >> Maik >> >> >> _______________________________________________ >> Xen-users mailing list >> Xen-users@lists.xen.org >> http://lists.xen.org/xen-users >> > > _______________________________________________ > Xen-users mailing list > Xen-users@lists.xen.org > http://lists.xen.org/xen-users > > > > --bcaec55245ec3808c104c8cf36cc Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable
As stated, you can alias shutdown to do exactly what you need, it= can be as simple as a series of hard-coded operations to a complex custom = shell script that parses your domains and closes each with feedback.

I don't know of a specific xl toolstack solut= ion, but if you are using the xm toolstack you can try this:

Keep in mind that without PV on HVM drivers or paravirt= ualized DomU's you'll have to use the `destroy` command from Dom0, = which is not a graceful shutdown.

On Mon, Sep 3, 2012 at 12:41 PM, Maik Brauer <maik.brauer@mbs-s= ystems.net> wrote:
Hi,

that = is true, I understand that, but at least if the Dom0 is rebooting and will = destroy the DomU's, the
Dom0 itself should not crash and hang= that a Hard-reset is needed to reboot.

Is there not any shutdown control, which can shutdown t= he DomU's from the Dom0 automatically in case of reboot or shutdown?
When I manually shutdown all DomU's before rebooting Dom0, then= the Dom0 will reboot and come up again.


On Sep 3, 2012, at 6:27= PM, Casey DeLorme wrote:

This coul= d have changed, but I am fairly certain rebooting Dom0 reboots Xen, hence a= ny running DomU's will have to be shutdown.

A 2010 reference:

You could always try running aliasing the shutdown comm= and to shutdown all running domU's by name, but otherwise forcing them = to shutdown as Dom0 does could damage your data.

On Mon, Sep 3, 2012 at 7:49 AM, Maik Brauer <maik.brauer@mbs-s= ystems.net> wrote:
Hello,

when for example the Dom0 needs to be rebooted manually and several DomU= 9;s are running,
the Dom0 will crash during shutdown, that just a Manual Hardware Reset will= help to reboot.

Current HVM is: Xen 4.1.3
Current Kernel: 2.6.32-5-xen-amd64

Is there a know issue, or what might could case this issue.
When rebooting the Dom0 without having at least one DomU running, then the = reboot is successful.
Can someone help me?
Thanks.

Cheers,
Maik


_______________________________________________
Xen-users mailing list
Xen-users@list= s.xen.org
http://lists.x= en.org/xen-users

_______________________________________________
Xen-users mailing listXen-users@li= sts.xen.org
http://lists.xen.org/xen-users



--bcaec55245ec3808c104c8cf36cc-- --===============5563159482806327500== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users --===============5563159482806327500==-- From xen-users-bounces@lists.xen.org Tue Sep 04 00:39:45 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Tue, 04 Sep 2012 00:39:45 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1T8h9q-0001Fu-AD; Tue, 04 Sep 2012 00:38:22 +0000 Received: from mail27.messagelabs.com ([193.109.254.147]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1T8h9p-0001Fp-59 for xen-users@lists.xen.org; Tue, 04 Sep 2012 00:38:21 +0000 X-Env-Sender: buck.alex@gmail.com X-Msg-Ref: server-12.tower-27.messagelabs.com!1346719089!9425869!1 X-Originating-IP: [209.85.160.45] X-SpamReason: No, hits=0.8 required=7.0 tests=BODY_RANDOM_LONG, ML_RADAR_SPEW_LINKS_14,RCVD_BY_IP,spamassassin: X-StarScan-Received: X-StarScan-Version: 6.6.1.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 11608 invoked from network); 4 Sep 2012 00:38:11 -0000 Received: from mail-pb0-f45.google.com (HELO mail-pb0-f45.google.com) (209.85.160.45) by server-12.tower-27.messagelabs.com with RC4-SHA encrypted SMTP; 4 Sep 2012 00:38:11 -0000 Received: by pbbjt11 with SMTP id jt11so8455149pbb.32 for ; Mon, 03 Sep 2012 17:38:08 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:user-agent:mime-version:to:subject :content-type; bh=GEW72uBfjb6wcYo1EKX4bHfbfjW0RYmUJg084rtLFfM=; b=EEZxdu/KFcZtiKHxPqQX2Cdw+PdxrIXgL3ieZUJfuvUZ9GvFLnsl4XDJfYpG2BHVN+ pN6c1zFfErrZH8KoNoH1eWlszqVfVyimU3romSI+wdJYkE/JdBw0Bqao5f1vbMm5M0at ZR4lwWgulqCxnMMiIkJ5m+P4HRhLnehltGahQis0m2Ho2GWDowM632OqmBL7RsIEplSk aK6w/FzADY2XO9xJD0qRtPzW6yqVqZRUNMNiGmdi2eym618lJGZcmJ5iYpOY+x7mydng mxt+qBDzQAvX6mjaFE0Rq9PwRO1iVOs8+Ukm7e3GDSmF1so2E8jlgucwgpGV1k7q89wu K1Mw== Received: by 10.68.235.68 with SMTP id uk4mr41631512pbc.52.1346719088831; Mon, 03 Sep 2012 17:38:08 -0700 (PDT) Received: from [192.168.1.60] (99-108-141-230.lightspeed.sntcca.sbcglobal.net. [99.108.141.230]) by mx.google.com with ESMTPS id uj3sm10917447pbc.39.2012.09.03.17.38.07 (version=SSLv3 cipher=OTHER); Mon, 03 Sep 2012 17:38:08 -0700 (PDT) Message-ID: <50454D6B.5090800@gmail.com> Date: Mon, 03 Sep 2012 17:38:03 -0700 From: Keith Buck User-Agent: Postbox 3.0.5 (Windows/20120826) MIME-Version: 1.0 To: xen-users@lists.xen.org Content-Type: multipart/mixed; boundary="------------000002040006090604060406" Subject: [Xen-users] Severe dom0 performance issues after installing Xen X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org This is a multi-part message in MIME format. --------------000002040006090604060406 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Hello, I'm experiencing some severe performance issues running Xen 4.0.1 with a cleanly-installed Debian 6 dom0. Prior to installation, the machine's performance was fine, but after installation booting takes anywhere from 5 to 20 times longer, processes take a long time to start, and SSH lags. No domUs are running (or have been created yet). I can switch back to running without Xen (but still using the Xen-compatible kernel) and the performance problems disappear. I attempted to dig into the issue further, but haven't been able to find any reason why the machine is so slow. Some cursory CPU integer performance and memory bandwidth benchmarks I ran showed that there is almost no difference in performance, and disk only loses about 10% of its performance. I also haven't found anything particularly alarming in dmesg or xm dmesg (although this is my first time installing Xen, so I am not sure I would know what to look for). top and xm top don't show anything constantly consuming all of the system's resources, and the only additional service I've installed so far is ntpd. As an additional debugging step, I've attempted limiting the dom0 memory to 1536MB (the machine has 4GB of physical memory). I haven't managed to turn up anything about this on Google yet. Has anyone seen a similar issue before or have ideas on how to fix/debug it? I have no physical access to the machine, unfortunately, so I am unable to play with BIOS settings. I've attached the contents of dmesg and xm dmesg, should these be useful. Thanks, Keith --------------000002040006090604060406 Content-Type: text/plain; name="dmesg" Content-Transfer-Encoding: 7bit Content-Disposition: attachment; filename="dmesg" [ 0.000000] Initializing cgroup subsys cpuset [ 0.000000] Initializing cgroup subsys cpu [ 0.000000] Linux version 2.6.32-5-xen-amd64 (Debian 2.6.32-45) (dannf@debian.org) (gcc version 4.3.5 (Debian 4.3.5-4) ) #1 SMP Sun May 6 08:57:29 UTC 2012 [ 0.000000] Command line: placeholder root=UUID=9ae68388-d77c-4f93-97cd-661e3c787190 ro quiet [ 0.000000] KERNEL supported cpus: [ 0.000000] Intel GenuineIntel [ 0.000000] AMD AuthenticAMD [ 0.000000] Centaur CentaurHauls [ 0.000000] released 0 pages of unused memory [ 0.000000] BIOS-provided physical RAM map: [ 0.000000] Xen: 0000000000000000 - 000000000009dc00 (usable) [ 0.000000] Xen: 000000000009dc00 - 0000000000100000 (reserved) [ 0.000000] Xen: 0000000000100000 - 0000000060000000 (usable) [ 0.000000] Xen: 00000000bf790000 - 00000000bf79e000 (ACPI data) [ 0.000000] Xen: 00000000bf79e000 - 00000000bf7d0000 (ACPI NVS) [ 0.000000] Xen: 00000000bf7d0000 - 00000000bf7e0000 (reserved) [ 0.000000] Xen: 00000000bf7ec000 - 00000000c0000000 (reserved) [ 0.000000] Xen: 00000000e0000000 - 00000000f0000000 (reserved) [ 0.000000] Xen: 00000000fec00000 - 00000000fec01000 (reserved) [ 0.000000] Xen: 00000000fec8a000 - 00000000fec8b000 (reserved) [ 0.000000] Xen: 00000000fee00000 - 00000000fee01000 (reserved) [ 0.000000] Xen: 00000000ffc00000 - 0000000100000000 (reserved) [ 0.000000] DMI present. [ 0.000000] AMI BIOS detected: BIOS may corrupt low RAM, working around it. [ 0.000000] e820 update range: 0000000000000000 - 0000000000010000 (usable) ==> (reserved) [ 0.000000] last_pfn = 0x60000 max_arch_pfn = 0x400000000 [ 0.000000] x86 PAT enabled: cpu 0, old 0x50100070406, new 0x7010600070106 [ 0.000000] initial memory mapped : 0 - 20000000 [ 0.000000] init_memory_mapping: 0000000000000000-0000000060000000 [ 0.000000] 0000000000 - 0060000000 page 4k [ 0.000000] kernel direct mapping tables up to 60000000 @ 100000-403000 [ 0.000000] RAMDISK: 01708000 - 0332a000 [ 0.000000] ACPI: RSDP 00000000000fac10 00024 (v02 ACPIAM) [ 0.000000] ACPI: XSDT 00000000bf790100 0005C (v01 SMCI 20100528 MSFT 00000097) [ 0.000000] ACPI: FACP 00000000bf790290 000F4 (v03 052810 FACP1443 20100528 MSFT 00000097) [ 0.000000] ACPI: DSDT 00000000bf7906a0 0650A (v01 10006 10006000 00000000 INTL 20051117) [ 0.000000] ACPI: FACS 00000000bf79e000 00040 [ 0.000000] ACPI: APIC 00000000bf790390 0011E (v01 052810 APIC1443 20100528 MSFT 00000097) [ 0.000000] ACPI: MCFG 00000000bf7904b0 0003C (v01 052810 OEMMCFG 20100528 MSFT 00000097) [ 0.000000] ACPI: SLIT 00000000bf7904f0 00030 (v01 052810 OEMSLIT 20100528 MSFT 00000097) [ 0.000000] ACPI: OEMB 00000000bf79e040 0007D (v01 052810 OEMB1443 20100528 MSFT 00000097) [ 0.000000] ACPI: HPET 00000000bf79a6a0 00038 (v01 052810 OEMHPET 20100528 MSFT 00000097) [ 0.000000] ACPI: SSDT 00000000bf79ee90 00363 (v01 DpgPmm CpuPm 00000012 INTL 20051117) [ 0.000000] ACPI: Local APIC address 0xfee00000 [ 0.000000] No NUMA configuration found [ 0.000000] Faking a node at 0000000000000000-0000000060000000 [ 0.000000] Bootmem setup node 0 0000000000000000-0000000060000000 [ 0.000000] NODE_DATA [0000000000010040 - 000000000001803f] [ 0.000000] bootmap [0000000000019000 - 0000000000024fff] pages c [ 0.000000] (9 early reservations) ==> bootmem [0000000000 - 0060000000] [ 0.000000] #0 [0000000000 - 0000001000] BIOS data page ==> [0000000000 - 0000001000] [ 0.000000] #1 [000362b000 - 000364a000] XEN PAGETABLES ==> [000362b000 - 000364a000] [ 0.000000] #2 [0000006000 - 0000008000] TRAMPOLINE ==> [0000006000 - 0000008000] [ 0.000000] #3 [0001000000 - 00016e7b44] TEXT DATA BSS ==> [0001000000 - 00016e7b44] [ 0.000000] #4 [0001708000 - 000332a000] RAMDISK ==> [0001708000 - 000332a000] [ 0.000000] #5 [000332a000 - 000362b000] XEN START INFO ==> [000332a000 - 000362b000] [ 0.000000] #6 [00016e8000 - 00016e821d] BRK ==> [00016e8000 - 00016e821d] [ 0.000000] #7 [0000100000 - 00003e1000] PGTABLE ==> [0000100000 - 00003e1000] [ 0.000000] #8 [0000010000 - 0000010030] ACPI SLIT ==> [0000010000 - 0000010030] [ 0.000000] found SMP MP-table at [ffff8800000ff780] ff780 [ 0.000000] Zone PFN ranges: [ 0.000000] DMA 0x00000010 -> 0x00001000 [ 0.000000] DMA32 0x00001000 -> 0x00100000 [ 0.000000] Normal 0x00100000 -> 0x00100000 [ 0.000000] Movable zone start PFN for each node [ 0.000000] early_node_map[2] active PFN ranges [ 0.000000] 0: 0x00000010 -> 0x0000009d [ 0.000000] 0: 0x00000100 -> 0x00060000 [ 0.000000] On node 0 totalpages: 393101 [ 0.000000] DMA zone: 56 pages used for memmap [ 0.000000] DMA zone: 740 pages reserved [ 0.000000] DMA zone: 3185 pages, LIFO batch:0 [ 0.000000] DMA32 zone: 5320 pages used for memmap [ 0.000000] DMA32 zone: 383800 pages, LIFO batch:31 [ 0.000000] ACPI: PM-Timer IO Port: 0x808 [ 0.000000] ACPI: Local APIC address 0xfee00000 [ 0.000000] ACPI: LAPIC (acpi_id[0x01] lapic_id[0x00] enabled) [ 0.000000] ACPI: LAPIC (acpi_id[0x02] lapic_id[0x02] enabled) [ 0.000000] ACPI: LAPIC (acpi_id[0x03] lapic_id[0x04] enabled) [ 0.000000] ACPI: LAPIC (acpi_id[0x04] lapic_id[0x06] enabled) [ 0.000000] ACPI: LAPIC (acpi_id[0x05] lapic_id[0x84] disabled) [ 0.000000] ACPI: LAPIC (acpi_id[0x06] lapic_id[0x85] disabled) [ 0.000000] ACPI: LAPIC (acpi_id[0x07] lapic_id[0x86] disabled) [ 0.000000] ACPI: LAPIC (acpi_id[0x08] lapic_id[0x87] disabled) [ 0.000000] ACPI: LAPIC (acpi_id[0x09] lapic_id[0x88] disabled) [ 0.000000] ACPI: LAPIC (acpi_id[0x0a] lapic_id[0x89] disabled) [ 0.000000] ACPI: LAPIC (acpi_id[0x0b] lapic_id[0x8a] disabled) [ 0.000000] ACPI: LAPIC (acpi_id[0x0c] lapic_id[0x8b] disabled) [ 0.000000] ACPI: LAPIC (acpi_id[0x0d] lapic_id[0x8c] disabled) [ 0.000000] ACPI: LAPIC (acpi_id[0x0e] lapic_id[0x8d] disabled) [ 0.000000] ACPI: LAPIC (acpi_id[0x0f] lapic_id[0x8e] disabled) [ 0.000000] ACPI: LAPIC (acpi_id[0x10] lapic_id[0x8f] disabled) [ 0.000000] ACPI: LAPIC (acpi_id[0x11] lapic_id[0x90] disabled) [ 0.000000] ACPI: LAPIC (acpi_id[0x12] lapic_id[0x91] disabled) [ 0.000000] ACPI: LAPIC (acpi_id[0x13] lapic_id[0x92] disabled) [ 0.000000] ACPI: LAPIC (acpi_id[0x14] lapic_id[0x93] disabled) [ 0.000000] ACPI: LAPIC (acpi_id[0x15] lapic_id[0x94] disabled) [ 0.000000] ACPI: LAPIC (acpi_id[0x16] lapic_id[0x95] disabled) [ 0.000000] ACPI: LAPIC (acpi_id[0x17] lapic_id[0x96] disabled) [ 0.000000] ACPI: LAPIC (acpi_id[0x18] lapic_id[0x97] disabled) [ 0.000000] ACPI: LAPIC_NMI (acpi_id[0xff] dfl dfl lint[0x1]) [ 0.000000] ACPI: IOAPIC (id[0x01] address[0xfec00000] gsi_base[0]) [ 0.000000] IOAPIC[0]: apic_id 1, version 0, address 0xfec00000, GSI 0-0 [ 0.000000] ACPI: IOAPIC (id[0x03] address[0xfec8a000] gsi_base[24]) [ 0.000000] IOAPIC[1]: apic_id 3, version 0, address 0xfec8a000, GSI 24-24 [ 0.000000] ACPI: INT_SRC_OVR (bus 0 bus_irq 0 global_irq 2 dfl dfl) [ 0.000000] ERROR: Unable to locate IOAPIC for GSI 2 [ 0.000000] ACPI: INT_SRC_OVR (bus 0 bus_irq 9 global_irq 9 high level) [ 0.000000] ERROR: Unable to locate IOAPIC for GSI 9 [ 0.000000] Using ACPI (MADT) for SMP configuration information [ 0.000000] ACPI: HPET id: 0x8086a301 base: 0xfed00000 [ 0.000000] SMP: Allowing 4 CPUs, 0 hotplug CPUs [ 0.000000] nr_irqs_gsi: 280 [ 0.000000] PM: Registered nosave memory: 000000000009d000 - 000000000009e000 [ 0.000000] PM: Registered nosave memory: 000000000009e000 - 0000000000100000 [ 0.000000] Allocating PCI resources starting at 60000000 (gap: 60000000:5f790000) [ 0.000000] Booting paravirtualized kernel on Xen [ 0.000000] Xen version: 4.0.1 (preserve-AD) (dom0) [ 0.000000] NR_CPUS:512 nr_cpumask_bits:512 nr_cpu_ids:4 nr_node_ids:1 [ 0.000000] PERCPU: Embedded 30 pages/cpu @ffff880003680000 s90328 r8192 d24360 u122880 [ 0.000000] pcpu-alloc: s90328 r8192 d24360 u122880 alloc=30*4096 [ 0.000000] pcpu-alloc: [0] 0 [0] 1 [0] 2 [0] 3 [ 1.145664] trying to map vcpu_info 0 at ffff88000368b020, mfn 13b68b, offset 32 [ 1.145668] cpu 0 using vcpu_info at ffff88000368b020 [ 1.145671] trying to map vcpu_info 1 at ffff8800036a9020, mfn 13b6a9, offset 32 [ 1.145674] cpu 1 using vcpu_info at ffff8800036a9020 [ 1.145676] trying to map vcpu_info 2 at ffff8800036c7020, mfn 13b6c7, offset 32 [ 1.145679] cpu 2 using vcpu_info at ffff8800036c7020 [ 1.145681] trying to map vcpu_info 3 at ffff8800036e5020, mfn 13b6e5, offset 32 [ 1.145684] cpu 3 using vcpu_info at ffff8800036e5020 [ 1.145685] Xen: using vcpu_info placement [ 1.145691] Built 1 zonelists in Node order, mobility grouping on. Total pages: 386985 [ 1.145693] Policy zone: DMA32 [ 1.145696] Kernel command line: placeholder root=UUID=9ae68388-d77c-4f93-97cd-661e3c787190 ro quiet [ 1.145726] PID hash table entries: 4096 (order: 3, 32768 bytes) [ 1.146059] Initializing CPU#0 [ 1.154734] DMA: Placing 64MB software IO TLB between ffff880004f58000 - ffff880008f58000 [ 1.154738] DMA: software IO TLB at phys 0x4f58000 - 0x8f58000 [ 1.154741] xen_swiotlb_fixup: buf=ffff880004f58000 size=67108864 [ 1.175539] xen_swiotlb_fixup: buf=ffff880008fb8000 size=32768 [ 1.183119] Memory: 1442072k/1572864k available (3152k kernel code, 460k absent, 130332k reserved, 2064k data, 604k init) [ 1.183159] SLUB: Genslabs=14, HWalign=64, Order=0-3, MinObjects=0, CPUs=4, Nodes=1 [ 1.183183] Hierarchical RCU implementation. [ 1.183190] NR_IRQS:4352 nr_irqs:1280 [ 1.183271] xen: --> irq=0 [ 1.183278] xen: --> irq=1 [ 1.183282] xen: --> irq=2 [ 1.183287] xen: --> irq=3 [ 1.183291] xen: --> irq=4 [ 1.183295] xen: --> irq=5 [ 1.183300] xen: --> irq=6 [ 1.183304] xen: --> irq=7 [ 1.183308] xen: --> irq=8 [ 1.183312] xen: --> irq=9 [ 1.183317] xen: --> irq=10 [ 1.183328] xen: --> irq=11 [ 1.183333] xen: --> irq=12 [ 1.183337] xen: --> irq=13 [ 1.183342] xen: --> irq=14 [ 1.183346] xen: --> irq=15 [ 1.183362] ACPI: INT_SRC_OVR (bus 0 bus_irq 0 global_irq 2 dfl dfl) [ 1.183366] ACPI: INT_SRC_OVR (bus 0 bus_irq 9 global_irq 9 high level) [ 1.183368] xen: sci override: source_irq=9 global_irq=9 trigger=c polarity=1 [ 1.183371] xen: registering gsi 9 triggering 0 polarity 0 [ 1.183373] xen_allocate_pirq: returning irq 9 for gsi 9 [ 1.183375] xen: --> irq=9 [ 1.183382] xen: acpi sci 9 [ 1.189510] Console: colour VGA+ 80x25 [ 1.189622] console [tty0] enabled [ 1.189650] Xen: using vcpuop timer interface [ 1.189654] installing Xen timer for CPU 0 [ 1.189661] alloc irq_desc for 1279 on node -1 [ 1.189664] alloc kstat_irqs on node -1 [ 1.189683] Detected 2133.454 MHz processor. [ 1.189690] Calibrating delay loop (skipped), value calculated using timer frequency.. 4266.90 BogoMIPS (lpj=8533816) [ 1.189707] Security Framework initialized [ 1.189713] SELinux: Disabled at boot. [ 1.190094] Dentry cache hash table entries: 262144 (order: 9, 2097152 bytes) [ 1.190727] Inode-cache hash table entries: 131072 (order: 8, 1048576 bytes) [ 1.190972] Mount-cache hash table entries: 256 [ 1.191101] Initializing cgroup subsys ns [ 1.191105] Initializing cgroup subsys cpuacct [ 1.191110] Initializing cgroup subsys devices [ 1.191113] Initializing cgroup subsys freezer [ 1.191115] Initializing cgroup subsys net_cls [ 1.191152] CPU: L1 I cache: 32K, L1 D cache: 32K [ 1.191155] CPU: L2 cache: 256K [ 1.191157] CPU: L3 cache: 4096K [ 1.191162] CPU 0/0x0 -> Node 0 [ 1.191164] CPU: Unsupported number of siblings 16 [ 1.191169] mce: CPU supports 9 MCE banks [ 1.191195] Performance Events: unsupported p6 CPU model 26 no PMU driver, software events only. [ 1.191210] SMP alternatives: switching to UP code [ 1.218048] ACPI: Core revision 20090903 [ 1.248472] alloc irq_desc for 1278 on node -1 [ 1.248474] alloc kstat_irqs on node -1 [ 1.248484] alloc irq_desc for 1277 on node -1 [ 1.248486] alloc kstat_irqs on node -1 [ 1.248490] alloc irq_desc for 1276 on node -1 [ 1.248493] alloc kstat_irqs on node -1 [ 1.248497] alloc irq_desc for 1275 on node -1 [ 1.248499] alloc kstat_irqs on node -1 [ 1.248666] installing Xen timer for CPU 1 [ 1.248669] alloc irq_desc for 1274 on node -1 [ 1.248671] alloc kstat_irqs on node -1 [ 1.248700] SMP alternatives: switching to SMP code [ 1.274563] alloc irq_desc for 1273 on node -1 [ 1.274566] alloc kstat_irqs on node -1 [ 1.274578] alloc irq_desc for 1272 on node -1 [ 1.274581] alloc kstat_irqs on node -1 [ 1.274585] alloc irq_desc for 1271 on node -1 [ 1.274588] alloc kstat_irqs on node -1 [ 1.274592] alloc irq_desc for 1270 on node -1 [ 1.274595] alloc kstat_irqs on node -1 [ 1.274608] Initializing CPU#1 [ 1.274648] CPU: L1 I cache: 32K, L1 D cache: 32K [ 1.274651] CPU: L2 cache: 256K [ 1.274652] CPU: L3 cache: 4096K [ 1.274656] CPU 1/0x0 -> Node 0 [ 1.274658] CPU: Unsupported number of siblings 16 [ 1.274760] installing Xen timer for CPU 2 [ 1.274764] alloc irq_desc for 1269 on node -1 [ 1.274767] alloc kstat_irqs on node -1 [ 1.274792] alloc irq_desc for 1268 on node -1 [ 1.274794] alloc kstat_irqs on node -1 [ 1.274800] alloc irq_desc for 1267 on node -1 [ 1.274802] alloc kstat_irqs on node -1 [ 1.274807] alloc irq_desc for 1266 on node -1 [ 1.274809] alloc kstat_irqs on node -1 [ 1.274816] alloc irq_desc for 1265 on node -1 [ 1.274818] alloc kstat_irqs on node -1 [ 1.274829] Initializing CPU#2 [ 1.274867] CPU: L1 I cache: 32K, L1 D cache: 32K [ 1.274870] CPU: L2 cache: 256K [ 1.274871] CPU: L3 cache: 4096K [ 1.274875] CPU 2/0x0 -> Node 0 [ 1.274877] CPU: Unsupported number of siblings 16 [ 1.274973] installing Xen timer for CPU 3 [ 1.274977] alloc irq_desc for 1264 on node -1 [ 1.274980] alloc kstat_irqs on node -1 [ 1.275001] alloc irq_desc for 1263 on node -1 [ 1.275003] alloc kstat_irqs on node -1 [ 1.275008] alloc irq_desc for 1262 on node -1 [ 1.275011] alloc kstat_irqs on node -1 [ 1.275015] alloc irq_desc for 1261 on node -1 [ 1.275017] alloc kstat_irqs on node -1 [ 1.275022] alloc irq_desc for 1260 on node -1 [ 1.275024] alloc kstat_irqs on node -1 [ 1.275035] Initializing CPU#3 [ 1.275073] CPU: L1 I cache: 32K, L1 D cache: 32K [ 1.275075] CPU: L2 cache: 256K [ 1.275077] CPU: L3 cache: 4096K [ 1.275081] CPU 3/0x0 -> Node 0 [ 1.275083] CPU: Unsupported number of siblings 16 [ 1.275120] Brought up 4 CPUs [ 1.275146] CPU0 attaching sched-domain: [ 1.275149] domain 0: span 0-3 level CPU [ 1.275152] groups: group ffff88000368fd00 cpus 0 group ffff8800036add00 cpus 1 group ffff8800036cbd00 cpus 2 group ffff8800036e9d00 cpus 3 [ 1.275164] CPU1 attaching sched-domain: [ 1.275166] domain 0: span 0-3 level CPU [ 1.275169] groups: group ffff8800036add00 cpus 1 group ffff8800036cbd00 cpus 2 group ffff8800036e9d00 cpus 3 group ffff88000368fd00 cpus 0 [ 1.275179] CPU2 attaching sched-domain: [ 1.275181] domain 0: span 0-3 level CPU [ 1.275183] groups: group ffff8800036cbd00 cpus 2 group ffff8800036e9d00 cpus 3 group ffff88000368fd00 cpus 0 group ffff8800036add00 cpus 1 [ 1.275193] CPU3 attaching sched-domain: [ 1.275195] domain 0: span 0-3 level CPU [ 1.275198] groups: group ffff8800036e9d00 cpus 3 group ffff88000368fd00 cpus 0 group ffff8800036add00 cpus 1 group ffff8800036cbd00 cpus 2 [ 1.275466] devtmpfs: initialized [ 1.278443] Grant table initialized [ 1.278446] regulator: core version 0.5 [ 1.278499] NET: Registered protocol family 16 [ 1.278551] alloc irq_desc for 1259 on node -1 [ 1.278553] alloc kstat_irqs on node -1 [ 1.278687] ACPI: bus type pci registered [ 1.278703] sync cpu 0 get result 1 max_id 3 [ 1.278715] sync cpu 1 get result 1 max_id 3 [ 1.278724] sync cpu 2 get result 1 max_id 3 [ 1.278732] sync cpu 3 get result 1 max_id 3 [ 1.278737] alloc irq_desc for 1258 on node -1 [ 1.278739] alloc kstat_irqs on node -1 [ 1.278826] PCI: MCFG configuration 0: base e0000000 segment 0 buses 0 - 255 [ 1.278829] PCI: MCFG area at e0000000 reserved in E820 [ 1.325249] PCI: Using MMCONFIG at e0000000 - efffffff [ 1.325251] PCI: Using configuration type 1 for base access [ 1.325856] bio: create slab at 0 [ 1.327251] ERROR: Unable to locate IOAPIC for GSI 9 [ 1.327321] ACPI: EC: Look up EC in DSDT [ 1.330013] ACPI Warning for \_SB_._OSC: Return type mismatch - found Integer, expected Buffer (20090903/nspredef-1006) [ 1.330023] \_SB_:_OSC evaluation returned wrong type [ 1.330025] _OSC request data:1 7 [ 1.331152] ACPI: Executed 1 blocks of module-level executable AML code [ 1.342955] ACPI: Interpreter enabled [ 1.342958] ACPI: (supports S0 S1 S4 S5) [ 1.342989] ACPI: Using IOAPIC for interrupt routing [ 1.356571] ACPI Warning: Incorrect checksum in table [OEMB] - 64, should be 61 (20090903/tbutils-314) [ 1.356768] ACPI: No dock devices found. [ 1.357003] ACPI: PCI Root Bridge [PCI0] (0000:00) [ 1.357183] pci 0000:00:00.0: PME# supported from D0 D3hot D3cold [ 1.357190] pci 0000:00:00.0: PME# disabled [ 1.357374] pci 0000:00:01.0: PME# supported from D0 D3hot D3cold [ 1.357381] pci 0000:00:01.0: PME# disabled [ 1.357565] pci 0000:00:03.0: PME# supported from D0 D3hot D3cold [ 1.357571] pci 0000:00:03.0: PME# disabled [ 1.357759] pci 0000:00:07.0: PME# supported from D0 D3hot D3cold [ 1.357765] pci 0000:00:07.0: PME# disabled [ 1.357950] pci 0000:00:09.0: PME# supported from D0 D3hot D3cold [ 1.357956] pci 0000:00:09.0: PME# disabled [ 1.358034] pci 0000:00:13.0: reg 10 32bit mmio: [0xfec8a000-0xfec8afff] [ 1.358122] pci 0000:00:13.0: PME# supported from D0 D3hot D3cold [ 1.358128] pci 0000:00:13.0: PME# disabled [ 1.358662] pci 0000:00:16.0: reg 10 64bit mmio: [0xfbef8000-0xfbefbfff] [ 1.358832] pci 0000:00:16.1: reg 10 64bit mmio: [0xfbef4000-0xfbef7fff] [ 1.359002] pci 0000:00:16.2: reg 10 64bit mmio: [0xfbef0000-0xfbef3fff] [ 1.359172] pci 0000:00:16.3: reg 10 64bit mmio: [0xfbeec000-0xfbeeffff] [ 1.359341] pci 0000:00:16.4: reg 10 64bit mmio: [0xfbee8000-0xfbeebfff] [ 1.359511] pci 0000:00:16.5: reg 10 64bit mmio: [0xfbee4000-0xfbee7fff] [ 1.359682] pci 0000:00:16.6: reg 10 64bit mmio: [0xfbee0000-0xfbee3fff] [ 1.359853] pci 0000:00:16.7: reg 10 64bit mmio: [0xfbedc000-0xfbedffff] [ 1.360062] pci 0000:00:1a.0: reg 20 io port: [0xcc00-0xcc1f] [ 1.360215] pci 0000:00:1a.1: reg 20 io port: [0xc880-0xc89f] [ 1.360368] pci 0000:00:1a.2: reg 20 io port: [0xc800-0xc81f] [ 1.360522] pci 0000:00:1a.7: reg 10 32bit mmio: [0xfbeda000-0xfbeda3ff] [ 1.360655] pci 0000:00:1a.7: PME# supported from D0 D3hot D3cold [ 1.360661] pci 0000:00:1a.7: PME# disabled [ 1.360738] pci 0000:00:1b.0: reg 10 64bit mmio: [0xfbed4000-0xfbed7fff] [ 1.360849] pci 0000:00:1b.0: PME# supported from D0 D3hot D3cold [ 1.360855] pci 0000:00:1b.0: PME# disabled [ 1.361009] pci 0000:00:1c.0: PME# supported from D0 D3hot D3cold [ 1.361015] pci 0000:00:1c.0: PME# disabled [ 1.361192] pci 0000:00:1c.4: PME# supported from D0 D3hot D3cold [ 1.361199] pci 0000:00:1c.4: PME# disabled [ 1.361367] pci 0000:00:1c.5: PME# supported from D0 D3hot D3cold [ 1.361373] pci 0000:00:1c.5: PME# disabled [ 1.361481] pci 0000:00:1d.0: reg 20 io port: [0xc480-0xc49f] [ 1.361634] pci 0000:00:1d.1: reg 20 io port: [0xc400-0xc41f] [ 1.361788] pci 0000:00:1d.2: reg 20 io port: [0xc080-0xc09f] [ 1.361946] pci 0000:00:1d.7: reg 10 32bit mmio: [0xfbed8000-0xfbed83ff] [ 1.362084] pci 0000:00:1d.7: PME# supported from D0 D3hot D3cold [ 1.362091] pci 0000:00:1d.7: PME# disabled [ 1.362350] pci 0000:00:1f.0: ICH7 LPC Generic IO decode 1 PIO at 0a00 (mask 00ff) [ 1.362355] pci 0000:00:1f.0: ICH7 LPC Generic IO decode 2 PIO at 4700 (mask 00ff) [ 1.362478] pci 0000:00:1f.2: reg 10 io port: [0xc000-0xc007] [ 1.362489] pci 0000:00:1f.2: reg 14 io port: [0xbc00-0xbc03] [ 1.362499] pci 0000:00:1f.2: reg 18 io port: [0xb880-0xb887] [ 1.362509] pci 0000:00:1f.2: reg 1c io port: [0xb800-0xb803] [ 1.362519] pci 0000:00:1f.2: reg 20 io port: [0xb480-0xb48f] [ 1.362530] pci 0000:00:1f.2: reg 24 io port: [0xb400-0xb40f] [ 1.362651] pci 0000:00:1f.3: reg 10 64bit mmio: [0xfbed2000-0xfbed20ff] [ 1.362677] pci 0000:00:1f.3: reg 20 io port: [0x400-0x41f] [ 1.362770] pci 0000:00:1f.5: reg 10 io port: [0xb000-0xb007] [ 1.362781] pci 0000:00:1f.5: reg 14 io port: [0xac00-0xac03] [ 1.362791] pci 0000:00:1f.5: reg 18 io port: [0xa880-0xa887] [ 1.362801] pci 0000:00:1f.5: reg 1c io port: [0xa800-0xa803] [ 1.362811] pci 0000:00:1f.5: reg 20 io port: [0xa480-0xa48f] [ 1.362822] pci 0000:00:1f.5: reg 24 io port: [0xa400-0xa40f] [ 1.363388] pci 0000:06:00.0: reg 10 32bit mmio: [0xfbce0000-0xfbcfffff] [ 1.363417] pci 0000:06:00.0: reg 18 io port: [0xdc00-0xdc1f] [ 1.363433] pci 0000:06:00.0: reg 1c 32bit mmio: [0xfbcdc000-0xfbcdffff] [ 1.363612] pci 0000:06:00.0: PME# supported from D0 D3hot D3cold [ 1.363621] pci 0000:06:00.0: PME# disabled [ 1.369340] pci 0000:00:1c.4: bridge io port: [0xd000-0xdfff] [ 1.369346] pci 0000:00:1c.4: bridge 32bit mmio: [0xfbc00000-0xfbcfffff] [ 1.369451] pci 0000:07:00.0: reg 10 32bit mmio: [0xfbde0000-0xfbdfffff] [ 1.369480] pci 0000:07:00.0: reg 18 io port: [0xec00-0xec1f] [ 1.369496] pci 0000:07:00.0: reg 1c 32bit mmio: [0xfbddc000-0xfbddffff] [ 1.369674] pci 0000:07:00.0: PME# supported from D0 D3hot D3cold [ 1.369683] pci 0000:07:00.0: PME# disabled [ 1.377351] pci 0000:00:1c.5: bridge io port: [0xe000-0xefff] [ 1.377358] pci 0000:00:1c.5: bridge 32bit mmio: [0xfbd00000-0xfbdfffff] [ 1.377430] pci 0000:08:01.0: reg 10 32bit mmio pref: [0xf9000000-0xf9ffffff] [ 1.377441] pci 0000:08:01.0: reg 14 32bit mmio: [0xfaffc000-0xfaffffff] [ 1.377453] pci 0000:08:01.0: reg 18 32bit mmio: [0xfb000000-0xfb7fffff] [ 1.377625] pci 0000:00:1e.0: transparent bridge [ 1.377636] pci 0000:00:1e.0: bridge 32bit mmio: [0xfaf00000-0xfb7fffff] [ 1.377646] pci 0000:00:1e.0: bridge 64bit mmio pref: [0xf9000000-0xf9ffffff] [ 1.377717] ACPI: PCI Interrupt Routing Table [\_SB_.PCI0._PRT] [ 1.378281] ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.NPE1._PRT] [ 1.378371] ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.NPE3._PRT] [ 1.378471] ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.NPE7._PRT] [ 1.378559] ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.NPE9._PRT] [ 1.378647] ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.P0P1._PRT] [ 1.378837] ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.P0P4._PRT] [ 1.378935] ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.P0P8._PRT] [ 1.379017] ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.P0P9._PRT] [ 1.432947] ACPI: PCI Interrupt Link [LNKA] (IRQs 3 4 6 7 10 *11 12 14 15) [ 1.433098] ACPI: PCI Interrupt Link [LNKB] (IRQs 3 4 6 7 *10 11 12 14 15) [ 1.433246] ACPI: PCI Interrupt Link [LNKC] (IRQs 3 4 6 7 10 11 12 14 *15) [ 1.433395] ACPI: PCI Interrupt Link [LNKD] (IRQs 3 4 6 7 10 11 12 *14 15) [ 1.433543] ACPI: PCI Interrupt Link [LNKE] (IRQs 3 4 6 7 10 11 12 14 15) *0, disabled. [ 1.433696] ACPI: PCI Interrupt Link [LNKF] (IRQs 3 4 6 *7 10 11 12 14 15) [ 1.433845] ACPI: PCI Interrupt Link [LNKG] (IRQs 3 4 *6 7 10 11 12 14 15) [ 1.434005] ACPI: PCI Interrupt Link [LNKH] (IRQs 3 4 6 7 *10 11 12 14 15) [ 1.434101] xen_balloon: Initialising balloon driver with page order 0. [ 1.434177] vgaarb: device added: PCI:0000:08:01.0,decodes=io+mem,owns=io+mem,locks=none [ 1.434180] vgaarb: loaded [ 1.434267] PCI: Using ACPI for IRQ routing [ 1.434588] Switching to clocksource xen [ 1.436132] pnp: PnP ACPI init [ 1.436148] ACPI: bus type pnp registered [ 1.436785] xen: registering gsi 8 triggering 1 polarity 0 [ 1.436788] xen_allocate_pirq: returning irq 8 for gsi 8 [ 1.436790] xen: --> irq=8 [ 1.437025] xen: registering gsi 13 triggering 1 polarity 0 [ 1.437028] xen_allocate_pirq: returning irq 13 for gsi 13 [ 1.437030] xen: --> irq=13 [ 1.437819] xen: registering gsi 4 triggering 1 polarity 0 [ 1.437822] xen_allocate_pirq: returning irq 4 for gsi 4 [ 1.437824] xen: --> irq=4 [ 1.438459] xen: registering gsi 3 triggering 1 polarity 0 [ 1.438461] xen_allocate_pirq: returning irq 3 for gsi 3 [ 1.438463] xen: --> irq=3 [ 1.440449] pnp: PnP ACPI: found 14 devices [ 1.440451] ACPI: ACPI bus type pnp unregistered [ 1.440463] system 00:01: iomem range 0xfed1c000-0xfed1ffff has been reserved [ 1.440471] system 00:06: ioport range 0xa10-0xa1f has been reserved [ 1.440478] system 00:09: ioport range 0xca2-0xca3 has been reserved [ 1.440481] system 00:09: ioport range 0xcf8-0xcff could not be reserved [ 1.440484] system 00:09: ioport range 0x4d0-0x4d1 has been reserved [ 1.440488] system 00:09: ioport range 0x800-0x87f has been reserved [ 1.440491] system 00:09: ioport range 0x500-0x57f has been reserved [ 1.440494] system 00:09: iomem range 0x400-0x4ff could not be reserved [ 1.440498] system 00:09: iomem range 0xfed1c000-0xfed1ffff has been reserved [ 1.440501] system 00:09: iomem range 0xfed20000-0xfed3ffff has been reserved [ 1.440505] system 00:09: iomem range 0xfed40000-0xfed8ffff has been reserved [ 1.440511] system 00:0b: iomem range 0xfec00000-0xfec00fff could not be reserved [ 1.440515] system 00:0b: iomem range 0xfee00000-0xfee00fff has been reserved [ 1.440521] system 00:0c: iomem range 0xe0000000-0xefffffff has been reserved [ 1.440527] system 00:0d: iomem range 0xc0000-0xcffff could not be reserved [ 1.440530] system 00:0d: iomem range 0xe0000-0xfffff could not be reserved [ 1.440534] system 00:0d: iomem range 0xfed90000-0xffffffff could not be reserved [ 1.445620] PM-Timer failed consistency check (0x0xffffff) - aborting. [ 1.445759] pci 0000:00:01.0: PCI bridge, secondary bus 0000:01 [ 1.445762] pci 0000:00:01.0: IO window: disabled [ 1.445770] pci 0000:00:01.0: MEM window: disabled [ 1.445775] pci 0000:00:01.0: PREFETCH window: disabled [ 1.445785] pci 0000:00:03.0: PCI bridge, secondary bus 0000:02 [ 1.445787] pci 0000:00:03.0: IO window: disabled [ 1.445795] pci 0000:00:03.0: MEM window: disabled [ 1.445801] pci 0000:00:03.0: PREFETCH window: disabled [ 1.445810] pci 0000:00:07.0: PCI bridge, secondary bus 0000:03 [ 1.445812] pci 0000:00:07.0: IO window: disabled [ 1.445820] pci 0000:00:07.0: MEM window: disabled [ 1.445825] pci 0000:00:07.0: PREFETCH window: disabled [ 1.445835] pci 0000:00:09.0: PCI bridge, secondary bus 0000:04 [ 1.445837] pci 0000:00:09.0: IO window: disabled [ 1.445845] pci 0000:00:09.0: MEM window: disabled [ 1.445851] pci 0000:00:09.0: PREFETCH window: disabled [ 1.445860] pci 0000:00:1c.0: PCI bridge, secondary bus 0000:05 [ 1.445865] pci 0000:00:1c.0: IO window: 0x1000-0x1fff [ 1.445873] pci 0000:00:1c.0: MEM window: 0x60000000-0x601fffff [ 1.445880] pci 0000:00:1c.0: PREFETCH window: 0x00000060200000-0x000000603fffff [ 1.445890] pci 0000:00:1c.4: PCI bridge, secondary bus 0000:06 [ 1.445895] pci 0000:00:1c.4: IO window: 0xd000-0xdfff [ 1.445903] pci 0000:00:1c.4: MEM window: 0xfbc00000-0xfbcfffff [ 1.445909] pci 0000:00:1c.4: PREFETCH window: 0x00000060400000-0x000000605fffff [ 1.445920] pci 0000:00:1c.5: PCI bridge, secondary bus 0000:07 [ 1.445924] pci 0000:00:1c.5: IO window: 0xe000-0xefff [ 1.445932] pci 0000:00:1c.5: MEM window: 0xfbd00000-0xfbdfffff [ 1.445939] pci 0000:00:1c.5: PREFETCH window: 0x00000060600000-0x000000607fffff [ 1.445949] pci 0000:00:1e.0: PCI bridge, secondary bus 0000:08 [ 1.445952] pci 0000:00:1e.0: IO window: disabled [ 1.445960] pci 0000:00:1e.0: MEM window: 0xfaf00000-0xfb7fffff [ 1.445966] pci 0000:00:1e.0: PREFETCH window: 0x000000f9000000-0x000000f9ffffff [ 1.445991] pci 0000:00:01.0: setting latency timer to 64 [ 1.446008] pci 0000:00:03.0: setting latency timer to 64 [ 1.446024] pci 0000:00:07.0: setting latency timer to 64 [ 1.446040] pci 0000:00:09.0: setting latency timer to 64 [ 1.446053] pci 0000:00:1c.0: enabling device (0104 -> 0107) [ 1.446059] xen: registering gsi 17 triggering 0 polarity 1 [ 1.446067] alloc irq_desc for 17 on node -1 [ 1.446069] alloc kstat_irqs on node -1 [ 1.446074] xen: --> irq=17 [ 1.446080] pci 0000:00:1c.0: PCI INT A -> GSI 17 (level, low) -> IRQ 17 [ 1.446086] pci 0000:00:1c.0: setting latency timer to 64 [ 1.446100] xen: registering gsi 17 triggering 0 polarity 1 [ 1.446103] xen_allocate_pirq: returning irq 17 for gsi 17 [ 1.446104] xen: --> irq=17 [ 1.446107] Already setup the GSI :17 [ 1.446109] pci 0000:00:1c.4: PCI INT A -> GSI 17 (level, low) -> IRQ 17 [ 1.446116] pci 0000:00:1c.4: setting latency timer to 64 [ 1.446129] xen: registering gsi 16 triggering 0 polarity 1 [ 1.446134] alloc irq_desc for 16 on node -1 [ 1.446136] alloc kstat_irqs on node -1 [ 1.446139] xen: --> irq=16 [ 1.446143] pci 0000:00:1c.5: PCI INT B -> GSI 16 (level, low) -> IRQ 16 [ 1.446149] pci 0000:00:1c.5: setting latency timer to 64 [ 1.446161] pci 0000:00:1e.0: setting latency timer to 64 [ 1.446166] pci_bus 0000:00: resource 0 io: [0x00-0xffff] [ 1.446169] pci_bus 0000:00: resource 1 mem: [0x000000-0xffffffffffffffff] [ 1.446172] pci_bus 0000:05: resource 0 io: [0x1000-0x1fff] [ 1.446175] pci_bus 0000:05: resource 1 mem: [0x60000000-0x601fffff] [ 1.446177] pci_bus 0000:05: resource 2 pref mem [0x60200000-0x603fffff] [ 1.446180] pci_bus 0000:06: resource 0 io: [0xd000-0xdfff] [ 1.446183] pci_bus 0000:06: resource 1 mem: [0xfbc00000-0xfbcfffff] [ 1.446185] pci_bus 0000:06: resource 2 pref mem [0x60400000-0x605fffff] [ 1.446188] pci_bus 0000:07: resource 0 io: [0xe000-0xefff] [ 1.446191] pci_bus 0000:07: resource 1 mem: [0xfbd00000-0xfbdfffff] [ 1.446193] pci_bus 0000:07: resource 2 pref mem [0x60600000-0x607fffff] [ 1.446196] pci_bus 0000:08: resource 1 mem: [0xfaf00000-0xfb7fffff] [ 1.446199] pci_bus 0000:08: resource 2 pref mem [0xf9000000-0xf9ffffff] [ 1.446202] pci_bus 0000:08: resource 3 io: [0x00-0xffff] [ 1.446204] pci_bus 0000:08: resource 4 mem: [0x000000-0xffffffffffffffff] [ 1.446230] NET: Registered protocol family 2 [ 1.446411] IP route cache hash table entries: 65536 (order: 7, 524288 bytes) [ 1.447389] TCP established hash table entries: 262144 (order: 10, 4194304 bytes) [ 1.448480] TCP bind hash table entries: 65536 (order: 8, 1048576 bytes) [ 1.448709] TCP: Hash tables configured (established 262144 bind 65536) [ 1.448712] TCP reno registered [ 1.448811] NET: Registered protocol family 1 [ 1.448863] xen: registering gsi 16 triggering 0 polarity 1 [ 1.448867] xen_allocate_pirq: returning irq 16 for gsi 16 [ 1.448869] xen: --> irq=16 [ 1.448873] Already setup the GSI :16 [ 1.448876] pci 0000:00:1a.0: PCI INT A -> GSI 16 (level, low) -> IRQ 16 [ 1.448903] pci 0000:00:1a.0: PCI INT A disabled [ 1.448910] xen: registering gsi 21 triggering 0 polarity 1 [ 1.448919] alloc irq_desc for 21 on node -1 [ 1.448922] alloc kstat_irqs on node -1 [ 1.448927] xen: --> irq=21 [ 1.448933] pci 0000:00:1a.1: PCI INT B -> GSI 21 (level, low) -> IRQ 21 [ 1.448957] pci 0000:00:1a.1: PCI INT B disabled [ 1.448965] xen: registering gsi 19 triggering 0 polarity 1 [ 1.448969] alloc irq_desc for 19 on node -1 [ 1.448971] alloc kstat_irqs on node -1 [ 1.448974] xen: --> irq=19 [ 1.448978] pci 0000:00:1a.2: PCI INT D -> GSI 19 (level, low) -> IRQ 19 [ 1.449003] pci 0000:00:1a.2: PCI INT D disabled [ 1.449018] xen: registering gsi 18 triggering 0 polarity 1 [ 1.449022] alloc irq_desc for 18 on node -1 [ 1.449024] alloc kstat_irqs on node -1 [ 1.449027] xen: --> irq=18 [ 1.449031] pci 0000:00:1a.7: PCI INT C -> GSI 18 (level, low) -> IRQ 18 [ 1.449075] pci 0000:00:1a.7: PCI INT C disabled [ 1.449088] xen: registering gsi 23 triggering 0 polarity 1 [ 1.449092] alloc irq_desc for 23 on node -1 [ 1.449095] alloc kstat_irqs on node -1 [ 1.449098] xen: --> irq=23 [ 1.449102] pci 0000:00:1d.0: PCI INT A -> GSI 23 (level, low) -> IRQ 23 [ 1.449127] pci 0000:00:1d.0: PCI INT A disabled [ 1.449134] xen: registering gsi 19 triggering 0 polarity 1 [ 1.449136] xen_allocate_pirq: returning irq 19 for gsi 19 [ 1.449138] xen: --> irq=19 [ 1.449140] Already setup the GSI :19 [ 1.449143] pci 0000:00:1d.1: PCI INT B -> GSI 19 (level, low) -> IRQ 19 [ 1.449167] pci 0000:00:1d.1: PCI INT B disabled [ 1.449174] xen: registering gsi 18 triggering 0 polarity 1 [ 1.449177] xen_allocate_pirq: returning irq 18 for gsi 18 [ 1.449179] xen: --> irq=18 [ 1.449181] Already setup the GSI :18 [ 1.449183] pci 0000:00:1d.2: PCI INT C -> GSI 18 (level, low) -> IRQ 18 [ 1.449208] pci 0000:00:1d.2: PCI INT C disabled [ 1.449222] xen: registering gsi 23 triggering 0 polarity 1 [ 1.449224] xen_allocate_pirq: returning irq 23 for gsi 23 [ 1.449226] xen: --> irq=23 [ 1.449228] Already setup the GSI :23 [ 1.449231] pci 0000:00:1d.7: PCI INT A -> GSI 23 (level, low) -> IRQ 23 [ 1.449255] pci 0000:00:1d.7: PCI INT A disabled [ 1.449273] pci 0000:08:01.0: Boot video device [ 1.449323] Unpacking initramfs... [ 1.473770] Freeing initrd memory: 28808k freed [ 1.479791] PCI-DMA: Using software bounce buffering for IO (SWIOTLB) [ 1.479797] DMA: Placing 64MB software IO TLB between ffff880004f58000 - ffff880008f58000 [ 1.479800] DMA: software IO TLB at phys 0x4f58000 - 0x8f58000 [ 1.480367] audit: initializing netlink socket (disabled) [ 1.480380] type=2000 audit(1346634674.413:1): initialized [ 1.483775] HugeTLB registered 2 MB page size, pre-allocated 0 pages [ 1.485416] VFS: Disk quotas dquot_6.5.2 [ 1.485466] Dquot-cache hash table entries: 512 (order 0, 4096 bytes) [ 1.485549] msgmni has been set to 2872 [ 1.485859] alg: No test for stdrng (krng) [ 1.485915] Block layer SCSI generic (bsg) driver version 0.4 loaded (major 253) [ 1.485919] io scheduler noop registered [ 1.485921] io scheduler anticipatory registered [ 1.485923] io scheduler deadline registered [ 1.485979] io scheduler cfq registered (default) [ 1.486213] alloc irq_desc for 1257 on node -1 [ 1.486215] alloc kstat_irqs on node -1 [ 1.486257] pcieport 0000:00:01.0: setting latency timer to 64 [ 1.486473] alloc irq_desc for 1256 on node -1 [ 1.486476] alloc kstat_irqs on node -1 [ 1.486505] pcieport 0000:00:03.0: setting latency timer to 64 [ 1.486729] alloc irq_desc for 1255 on node -1 [ 1.486732] alloc kstat_irqs on node -1 [ 1.486761] pcieport 0000:00:07.0: setting latency timer to 64 [ 1.486973] alloc irq_desc for 1254 on node -1 [ 1.486976] alloc kstat_irqs on node -1 [ 1.487005] pcieport 0000:00:09.0: setting latency timer to 64 [ 1.487198] alloc irq_desc for 1253 on node -1 [ 1.487200] alloc kstat_irqs on node -1 [ 1.487233] pcieport 0000:00:1c.0: setting latency timer to 64 [ 1.487430] alloc irq_desc for 1252 on node -1 [ 1.487433] alloc kstat_irqs on node -1 [ 1.487463] pcieport 0000:00:1c.4: setting latency timer to 64 [ 1.487658] alloc irq_desc for 1251 on node -1 [ 1.487660] alloc kstat_irqs on node -1 [ 1.487690] pcieport 0000:00:1c.5: setting latency timer to 64 [ 1.487817] aer 0000:00:01.0:pcie02: AER service couldn't init device: no _OSC support [ 1.487827] aer 0000:00:03.0:pcie02: AER service couldn't init device: no _OSC support [ 1.487833] aer 0000:00:07.0:pcie02: AER service couldn't init device: no _OSC support [ 1.487840] aer 0000:00:09.0:pcie02: AER service couldn't init device: no _OSC support [ 1.491913] registering netback [ 1.492020] alloc irq_desc for 1250 on node -1 [ 1.492023] alloc kstat_irqs on node -1 [ 1.493450] alloc irq_desc for 1249 on node -1 [ 1.493453] alloc kstat_irqs on node -1 [ 1.493826] hpet_acpi_add: no address or irqs in _CRS [ 1.493842] Linux agpgart interface v0.103 [ 1.493893] Serial: 8250/16550 driver, 4 ports, IRQ sharing enabled [ 1.494024] serial8250: ttyS0 at I/O 0x3f8 (irq = 4) is a 16550A [ 1.494155] serial8250: ttyS1 at I/O 0x2f8 (irq = 3) is a 16550A [ 1.494446] 00:07: ttyS0 at I/O 0x3f8 (irq = 4) is a 16550A [ 1.494605] 00:08: ttyS1 at I/O 0x2f8 (irq = 3) is a 16550A [ 1.494772] input: Macintosh mouse button emulation as /devices/virtual/input/input0 [ 1.494831] PNP: No PS/2 controller found. Probing ports directly. [ 1.497494] serio: i8042 KBD port at 0x60,0x64 irq 1 [ 1.497502] serio: i8042 AUX port at 0x60,0x64 irq 12 [ 1.497587] mice: PS/2 mouse device common for all mice [ 1.497630] rtc_cmos 00:03: RTC can wake from S4 [ 1.497670] rtc_cmos 00:03: rtc core: registered rtc_cmos as rtc0 [ 1.497703] rtc0: alarms up to one month, y3k, 114 bytes nvram [ 1.497718] cpuidle: using governor ladder [ 1.497721] cpuidle: using governor menu [ 1.497726] No iBFT detected. [ 1.498004] TCP cubic registered [ 1.498117] NET: Registered protocol family 10 [ 1.498806] Mobile IPv6 [ 1.498809] NET: Registered protocol family 17 [ 1.498889] PM: Resume from disk failed. [ 1.498900] registered taskstats version 1 [ 1.500106] rtc_cmos 00:03: setting system clock to 2012-09-03 01:11:14 UTC (1346634674) [ 1.500157] Initalizing network drop monitor service [ 1.500238] Freeing unused kernel memory: 604k freed [ 1.500361] Write protecting the kernel read-only data: 4336k [ 1.531801] udev[83]: starting version 164 [ 1.615512] e1000e: Intel(R) PRO/1000 Network Driver - 1.2.20-k2 [ 1.615516] e1000e: Copyright(c) 1999 - 2011 Intel Corporation. [ 1.615572] xen: registering gsi 16 triggering 0 polarity 1 [ 1.615576] xen_allocate_pirq: returning irq 16 for gsi 16 [ 1.615578] xen: --> irq=16 [ 1.615583] Already setup the GSI :16 [ 1.615586] e1000e 0000:06:00.0: PCI INT A -> GSI 16 (level, low) -> IRQ 16 [ 1.615637] e1000e 0000:06:00.0: setting latency timer to 64 [ 1.615997] alloc irq_desc for 1248 on node -1 [ 1.615999] alloc kstat_irqs on node -1 [ 1.616123] alloc irq_desc for 1247 on node -1 [ 1.616125] alloc kstat_irqs on node -1 [ 1.616245] alloc irq_desc for 1246 on node -1 [ 1.616248] alloc kstat_irqs on node -1 [ 1.616513] e1000e 0000:06:00.0: Disabling ASPM L0s [ 1.648958] usbcore: registered new interface driver usbfs [ 1.648986] usbcore: registered new interface driver hub [ 1.649046] usbcore: registered new device driver usb [ 1.650510] SCSI subsystem initialized [ 1.650847] ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver [ 1.650880] xen: registering gsi 18 triggering 0 polarity 1 [ 1.650884] xen_allocate_pirq: returning irq 18 for gsi 18 [ 1.650886] xen: --> irq=18 [ 1.650891] Already setup the GSI :18 [ 1.650894] ehci_hcd 0000:00:1a.7: PCI INT C -> GSI 18 (level, low) -> IRQ 18 [ 1.650921] ehci_hcd 0000:00:1a.7: setting latency timer to 64 [ 1.650926] ehci_hcd 0000:00:1a.7: EHCI Host Controller [ 1.650954] ehci_hcd 0000:00:1a.7: new USB bus registered, assigned bus number 1 [ 1.651019] ehci_hcd 0000:00:1a.7: debug port 1 [ 1.654896] ehci_hcd 0000:00:1a.7: cache line size of 32 is not supported [ 1.654923] ehci_hcd 0000:00:1a.7: irq 18, io mem 0xfbeda000 [ 1.664014] libata version 3.00 loaded. [ 1.670835] ehci_hcd 0000:00:1a.7: USB 2.0 started, EHCI 1.00 [ 1.670862] usb usb1: New USB device found, idVendor=1d6b, idProduct=0002 [ 1.670865] usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1 [ 1.670868] usb usb1: Product: EHCI Host Controller [ 1.670870] usb usb1: Manufacturer: Linux 2.6.32-5-xen-amd64 ehci_hcd [ 1.670873] usb usb1: SerialNumber: 0000:00:1a.7 [ 1.670950] usb usb1: configuration #1 chosen from 1 choice [ 1.670984] hub 1-0:1.0: USB hub found [ 1.671004] hub 1-0:1.0: 6 ports detected [ 1.671071] ata_piix 0000:00:1f.2: version 2.13 [ 1.671091] xen: registering gsi 19 triggering 0 polarity 1 [ 1.671094] xen_allocate_pirq: returning irq 19 for gsi 19 [ 1.671096] xen: --> irq=19 [ 1.671100] Already setup the GSI :19 [ 1.671103] ata_piix 0000:00:1f.2: PCI INT B -> GSI 19 (level, low) -> IRQ 19 [ 1.671110] ata_piix 0000:00:1f.2: MAP [ P0 P2 P1 P3 ] [ 1.671163] ata_piix 0000:00:1f.2: setting latency timer to 64 [ 1.671256] scsi0 : ata_piix [ 1.671441] scsi1 : ata_piix [ 1.674044] ata1: SATA max UDMA/133 cmd 0xc000 ctl 0xbc00 bmdma 0xb480 irq 19 [ 1.674053] ata2: SATA max UDMA/133 cmd 0xb880 ctl 0xb800 bmdma 0xb488 irq 19 [ 1.674087] xen: registering gsi 23 triggering 0 polarity 1 [ 1.674090] xen_allocate_pirq: returning irq 23 for gsi 23 [ 1.674092] xen: --> irq=23 [ 1.674095] Already setup the GSI :23 [ 1.674098] ehci_hcd 0000:00:1d.7: PCI INT A -> GSI 23 (level, low) -> IRQ 23 [ 1.674123] ehci_hcd 0000:00:1d.7: setting latency timer to 64 [ 1.674128] ehci_hcd 0000:00:1d.7: EHCI Host Controller [ 1.674137] ehci_hcd 0000:00:1d.7: new USB bus registered, assigned bus number 2 [ 1.674192] ehci_hcd 0000:00:1d.7: debug port 1 [ 1.678087] ehci_hcd 0000:00:1d.7: cache line size of 32 is not supported [ 1.678107] ehci_hcd 0000:00:1d.7: irq 23, io mem 0xfbed8000 [ 1.694740] ehci_hcd 0000:00:1d.7: USB 2.0 started, EHCI 1.00 [ 1.694780] usb usb2: New USB device found, idVendor=1d6b, idProduct=0002 [ 1.694784] usb usb2: New USB device strings: Mfr=3, Product=2, SerialNumber=1 [ 1.694787] usb usb2: Product: EHCI Host Controller [ 1.694790] usb usb2: Manufacturer: Linux 2.6.32-5-xen-amd64 ehci_hcd [ 1.694793] usb usb2: SerialNumber: 0000:00:1d.7 [ 1.694862] usb usb2: configuration #1 chosen from 1 choice [ 1.694897] hub 2-0:1.0: USB hub found [ 1.694913] hub 2-0:1.0: 6 ports detected [ 1.695056] xen: registering gsi 19 triggering 0 polarity 1 [ 1.695059] xen_allocate_pirq: returning irq 19 for gsi 19 [ 1.695061] xen: --> irq=19 [ 1.695064] Already setup the GSI :19 [ 1.695067] ata_piix 0000:00:1f.5: PCI INT B -> GSI 19 (level, low) -> IRQ 19 [ 1.695075] ata_piix 0000:00:1f.5: MAP [ P0 -- P1 -- ] [ 1.695122] ata_piix 0000:00:1f.5: setting latency timer to 64 [ 1.695198] scsi2 : ata_piix [ 1.695268] scsi3 : ata_piix [ 1.697425] ata3: SATA max UDMA/133 cmd 0xb000 ctl 0xac00 bmdma 0xa480 irq 19 [ 1.697431] ata4: SATA max UDMA/133 cmd 0xa880 ctl 0xa800 bmdma 0xa488 irq 19 [ 1.734264] e1000e 0000:06:00.0: eth0: (PCI Express:2.5GB/s:Width x1) 00:25:90:08:f8:f4 [ 1.734267] e1000e 0000:06:00.0: eth0: Intel(R) PRO/1000 Network Connection [ 1.734354] e1000e 0000:06:00.0: eth0: MAC: 3, PHY: 8, PBA No: 0101FF-0FF [ 1.734391] xen: registering gsi 17 triggering 0 polarity 1 [ 1.734394] xen_allocate_pirq: returning irq 17 for gsi 17 [ 1.734396] xen: --> irq=17 [ 1.734398] Already setup the GSI :17 [ 1.734401] e1000e 0000:07:00.0: PCI INT A -> GSI 17 (level, low) -> IRQ 17 [ 1.734446] e1000e 0000:07:00.0: setting latency timer to 64 [ 1.734753] alloc irq_desc for 1245 on node -1 [ 1.734756] alloc kstat_irqs on node -1 [ 1.734873] alloc irq_desc for 1244 on node -1 [ 1.734875] alloc kstat_irqs on node -1 [ 1.734985] alloc irq_desc for 1243 on node -1 [ 1.734988] alloc kstat_irqs on node -1 [ 1.735554] e1000e 0000:07:00.0: Disabling ASPM L0s [ 1.752363] uhci_hcd: USB Universal Host Controller Interface driver [ 1.752393] xen: registering gsi 16 triggering 0 polarity 1 [ 1.752396] xen_allocate_pirq: returning irq 16 for gsi 16 [ 1.752398] xen: --> irq=16 [ 1.752401] Already setup the GSI :16 [ 1.752404] uhci_hcd 0000:00:1a.0: PCI INT A -> GSI 16 (level, low) -> IRQ 16 [ 1.752416] uhci_hcd 0000:00:1a.0: setting latency timer to 64 [ 1.752421] uhci_hcd 0000:00:1a.0: UHCI Host Controller [ 1.752431] uhci_hcd 0000:00:1a.0: new USB bus registered, assigned bus number 3 [ 1.752478] uhci_hcd 0000:00:1a.0: irq 16, io base 0x0000cc00 [ 1.752537] usb usb3: New USB device found, idVendor=1d6b, idProduct=0001 [ 1.752540] usb usb3: New USB device strings: Mfr=3, Product=2, SerialNumber=1 [ 1.752543] usb usb3: Product: UHCI Host Controller [ 1.752545] usb usb3: Manufacturer: Linux 2.6.32-5-xen-amd64 uhci_hcd [ 1.752547] usb usb3: SerialNumber: 0000:00:1a.0 [ 1.752608] usb usb3: configuration #1 chosen from 1 choice [ 1.752636] hub 3-0:1.0: USB hub found [ 1.752648] hub 3-0:1.0: 2 ports detected [ 1.752702] xen: registering gsi 21 triggering 0 polarity 1 [ 1.752705] xen_allocate_pirq: returning irq 21 for gsi 21 [ 1.752707] xen: --> irq=21 [ 1.752710] Already setup the GSI :21 [ 1.752712] uhci_hcd 0000:00:1a.1: PCI INT B -> GSI 21 (level, low) -> IRQ 21 [ 1.752724] uhci_hcd 0000:00:1a.1: setting latency timer to 64 [ 1.752729] uhci_hcd 0000:00:1a.1: UHCI Host Controller [ 1.752736] uhci_hcd 0000:00:1a.1: new USB bus registered, assigned bus number 4 [ 1.752780] uhci_hcd 0000:00:1a.1: irq 21, io base 0x0000c880 [ 1.752831] usb usb4: New USB device found, idVendor=1d6b, idProduct=0001 [ 1.752834] usb usb4: New USB device strings: Mfr=3, Product=2, SerialNumber=1 [ 1.752837] usb usb4: Product: UHCI Host Controller [ 1.752839] usb usb4: Manufacturer: Linux 2.6.32-5-xen-amd64 uhci_hcd [ 1.752841] usb usb4: SerialNumber: 0000:00:1a.1 [ 1.752902] usb usb4: configuration #1 chosen from 1 choice [ 1.752929] hub 4-0:1.0: USB hub found [ 1.752941] hub 4-0:1.0: 2 ports detected [ 1.752997] xen: registering gsi 19 triggering 0 polarity 1 [ 1.752999] xen_allocate_pirq: returning irq 19 for gsi 19 [ 1.753001] xen: --> irq=19 [ 1.753004] Already setup the GSI :19 [ 1.753007] uhci_hcd 0000:00:1a.2: PCI INT D -> GSI 19 (level, low) -> IRQ 19 [ 1.753019] uhci_hcd 0000:00:1a.2: setting latency timer to 64 [ 1.753023] uhci_hcd 0000:00:1a.2: UHCI Host Controller [ 1.753031] uhci_hcd 0000:00:1a.2: new USB bus registered, assigned bus number 5 [ 1.753064] uhci_hcd 0000:00:1a.2: irq 19, io base 0x0000c800 [ 1.753114] usb usb5: New USB device found, idVendor=1d6b, idProduct=0001 [ 1.753117] usb usb5: New USB device strings: Mfr=3, Product=2, SerialNumber=1 [ 1.753119] usb usb5: Product: UHCI Host Controller [ 1.753122] usb usb5: Manufacturer: Linux 2.6.32-5-xen-amd64 uhci_hcd [ 1.753124] usb usb5: SerialNumber: 0000:00:1a.2 [ 1.753179] usb usb5: configuration #1 chosen from 1 choice [ 1.753205] hub 5-0:1.0: USB hub found [ 1.753216] hub 5-0:1.0: 2 ports detected [ 1.753271] xen: registering gsi 23 triggering 0 polarity 1 [ 1.753274] xen_allocate_pirq: returning irq 23 for gsi 23 [ 1.753276] xen: --> irq=23 [ 1.753279] Already setup the GSI :23 [ 1.753282] uhci_hcd 0000:00:1d.0: PCI INT A -> GSI 23 (level, low) -> IRQ 23 [ 1.753293] uhci_hcd 0000:00:1d.0: setting latency timer to 64 [ 1.753298] uhci_hcd 0000:00:1d.0: UHCI Host Controller [ 1.753307] uhci_hcd 0000:00:1d.0: new USB bus registered, assigned bus number 6 [ 1.753340] uhci_hcd 0000:00:1d.0: irq 23, io base 0x0000c480 [ 1.753389] usb usb6: New USB device found, idVendor=1d6b, idProduct=0001 [ 1.753392] usb usb6: New USB device strings: Mfr=3, Product=2, SerialNumber=1 [ 1.753395] usb usb6: Product: UHCI Host Controller [ 1.753397] usb usb6: Manufacturer: Linux 2.6.32-5-xen-amd64 uhci_hcd [ 1.753399] usb usb6: SerialNumber: 0000:00:1d.0 [ 1.753452] usb usb6: configuration #1 chosen from 1 choice [ 1.753480] hub 6-0:1.0: USB hub found [ 1.753492] hub 6-0:1.0: 2 ports detected [ 1.753547] xen: registering gsi 19 triggering 0 polarity 1 [ 1.753550] xen_allocate_pirq: returning irq 19 for gsi 19 [ 1.753552] xen: --> irq=19 [ 1.753554] Already setup the GSI :19 [ 1.753557] uhci_hcd 0000:00:1d.1: PCI INT B -> GSI 19 (level, low) -> IRQ 19 [ 1.753568] uhci_hcd 0000:00:1d.1: setting latency timer to 64 [ 1.753573] uhci_hcd 0000:00:1d.1: UHCI Host Controller [ 1.753580] uhci_hcd 0000:00:1d.1: new USB bus registered, assigned bus number 7 [ 1.753613] uhci_hcd 0000:00:1d.1: irq 19, io base 0x0000c400 [ 1.753665] usb usb7: New USB device found, idVendor=1d6b, idProduct=0001 [ 1.753668] usb usb7: New USB device strings: Mfr=3, Product=2, SerialNumber=1 [ 1.753671] usb usb7: Product: UHCI Host Controller [ 1.753673] usb usb7: Manufacturer: Linux 2.6.32-5-xen-amd64 uhci_hcd [ 1.753675] usb usb7: SerialNumber: 0000:00:1d.1 [ 1.753730] usb usb7: configuration #1 chosen from 1 choice [ 1.753756] hub 7-0:1.0: USB hub found [ 1.753768] hub 7-0:1.0: 2 ports detected [ 1.753823] xen: registering gsi 18 triggering 0 polarity 1 [ 1.753825] xen_allocate_pirq: returning irq 18 for gsi 18 [ 1.753827] xen: --> irq=18 [ 1.753830] Already setup the GSI :18 [ 1.753833] uhci_hcd 0000:00:1d.2: PCI INT C -> GSI 18 (level, low) -> IRQ 18 [ 1.753844] uhci_hcd 0000:00:1d.2: setting latency timer to 64 [ 1.753849] uhci_hcd 0000:00:1d.2: UHCI Host Controller [ 1.753856] uhci_hcd 0000:00:1d.2: new USB bus registered, assigned bus number 8 [ 1.753889] uhci_hcd 0000:00:1d.2: irq 18, io base 0x0000c080 [ 1.753938] usb usb8: New USB device found, idVendor=1d6b, idProduct=0001 [ 1.753941] usb usb8: New USB device strings: Mfr=3, Product=2, SerialNumber=1 [ 1.753944] usb usb8: Product: UHCI Host Controller [ 1.753946] usb usb8: Manufacturer: Linux 2.6.32-5-xen-amd64 uhci_hcd [ 1.753948] usb usb8: SerialNumber: 0000:00:1d.2 [ 1.754003] usb usb8: configuration #1 chosen from 1 choice [ 1.754030] hub 8-0:1.0: USB hub found [ 1.754041] hub 8-0:1.0: 2 ports detected [ 1.856060] e1000e 0000:07:00.0: eth1: (PCI Express:2.5GB/s:Width x1) 00:25:90:08:f8:f5 [ 1.856063] e1000e 0000:07:00.0: eth1: Intel(R) PRO/1000 Network Connection [ 1.856149] e1000e 0000:07:00.0: eth1: MAC: 3, PHY: 8, PBA No: 0101FF-0FF [ 2.026118] ata3: SATA link down (SStatus 0 SControl 300) [ 2.037464] ata4: SATA link down (SStatus 0 SControl 300) [ 2.194749] usb 6-2: new low speed USB device using uhci_hcd and address 2 [ 2.322246] ata2.00: SATA link down (SStatus 0 SControl 300) [ 2.322278] ata2.01: SATA link down (SStatus 0 SControl 300) [ 2.383407] usb 6-2: New USB device found, idVendor=0624, idProduct=0294 [ 2.383411] usb 6-2: New USB device strings: Mfr=1, Product=2, SerialNumber=0 [ 2.383414] usb 6-2: Product: Dell 03R874 [ 2.383417] usb 6-2: Manufacturer: Avocent [ 2.383502] usb 6-2: configuration #1 chosen from 1 choice [ 2.466851] ata1.00: SATA link up 3.0 Gbps (SStatus 123 SControl 300) [ 2.466872] ata1.01: SATA link down (SStatus 0 SControl 300) [ 2.475316] ata1.00: ATA-8: ST31000524NS, SN11, max UDMA/133 [ 2.475320] ata1.00: 1953525168 sectors, multi 16: LBA48 NCQ (depth 0/32) [ 2.491336] ata1.00: configured for UDMA/133 [ 2.491456] scsi 0:0:0:0: Direct-Access ATA ST31000524NS SN11 PQ: 0 ANSI: 5 [ 2.494928] usbcore: registered new interface driver hiddev [ 2.498808] sd 0:0:0:0: [sda] 1953525168 512-byte logical blocks: (1.00 TB/931 GiB) [ 2.498883] sd 0:0:0:0: [sda] Write Protect is off [ 2.498886] sd 0:0:0:0: [sda] Mode Sense: 00 3a 00 00 [ 2.498917] sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA [ 2.499181] sda: [ 2.508634] input: Avocent Dell 03R874 as /devices/pci0000:00/0000:00:1d.0/usb6/6-2/6-2:1.0/input/input1 [ 2.508681] generic-usb 0003:0624:0294.0001: input,hidraw0: USB HID v1.10 Keyboard [Avocent Dell 03R874] on usb-0000:00:1d.0-2/input0 [ 2.516368] sda1 sda2 < sda5 [ 2.531678] input: Avocent Dell 03R874 as /devices/pci0000:00/0000:00:1d.0/usb6/6-2/6-2:1.1/input/input2 [ 2.531739] generic-usb 0003:0624:0294.0002: input,hidraw1: USB HID v1.10 Mouse [Avocent Dell 03R874] on usb-0000:00:1d.0-2/input1 [ 2.531759] usbcore: registered new interface driver usbhid [ 2.531762] usbhid: v2.6:USB HID core driver [ 2.534295] sda6 sda7 sda8 > [ 2.555825] sd 0:0:0:0: [sda] Attached SCSI disk [ 2.899763] device-mapper: uevent: version 1.0.3 [ 2.899895] device-mapper: ioctl: 4.15.0-ioctl (2009-04-01) initialised: dm-devel@redhat.com [ 2.909503] PM: Starting manual resume from disk [ 2.909506] PM: Resume from partition 8:5 [ 2.909508] PM: Checking hibernation image. [ 2.909833] PM: Error -22 checking image file [ 2.909836] PM: Resume from disk failed. [ 2.924059] EXT3-fs: INFO: recovery required on readonly filesystem. [ 2.924062] EXT3-fs: write access will be enabled during recovery. [ 2.946363] kjournald starting. Commit interval 5 seconds [ 2.946373] EXT3-fs: recovery complete. [ 2.946668] EXT3-fs: mounted filesystem with ordered data mode. [ 3.754433] udev[499]: starting version 164 [ 3.945625] dca service started, version 1.12.1 [ 4.001259] ioatdma: Intel(R) QuickData Technology Driver 4.00 [ 4.001323] xen: registering gsi 43 triggering 0 polarity 1 [ 4.001332] alloc irq_desc for 43 on node -1 [ 4.001334] alloc kstat_irqs on node -1 [ 4.001340] xen: --> irq=43 [ 4.001349] ioatdma 0000:00:16.0: PCI INT A -> GSI 43 (level, low) -> IRQ 43 [ 4.001381] ioatdma 0000:00:16.0: setting latency timer to 64 [ 4.001471] alloc irq_desc for 1242 on node -1 [ 4.001473] alloc kstat_irqs on node -1 [ 4.001854] xen: registering gsi 44 triggering 0 polarity 1 [ 4.001860] alloc irq_desc for 44 on node -1 [ 4.001862] alloc kstat_irqs on node -1 [ 4.001866] xen: --> irq=44 [ 4.001873] ioatdma 0000:00:16.1: PCI INT B -> GSI 44 (level, low) -> IRQ 44 [ 4.001895] ioatdma 0000:00:16.1: setting latency timer to 64 [ 4.001973] alloc irq_desc for 1241 on node -1 [ 4.001975] alloc kstat_irqs on node -1 [ 4.002654] xen: registering gsi 45 triggering 0 polarity 1 [ 4.002660] alloc irq_desc for 45 on node -1 [ 4.002663] alloc kstat_irqs on node -1 [ 4.002666] xen: --> irq=45 [ 4.002673] ioatdma 0000:00:16.2: PCI INT C -> GSI 45 (level, low) -> IRQ 45 [ 4.002697] ioatdma 0000:00:16.2: setting latency timer to 64 [ 4.002780] alloc irq_desc for 1240 on node -1 [ 4.002783] alloc kstat_irqs on node -1 [ 4.003358] xen: registering gsi 46 triggering 0 polarity 1 [ 4.003366] alloc irq_desc for 46 on node -1 [ 4.003369] alloc kstat_irqs on node -1 [ 4.003374] xen: --> irq=46 [ 4.003382] ioatdma 0000:00:16.3: PCI INT D -> GSI 46 (level, low) -> IRQ 46 [ 4.003411] ioatdma 0000:00:16.3: setting latency timer to 64 [ 4.003503] alloc irq_desc for 1239 on node -1 [ 4.003505] alloc kstat_irqs on node -1 [ 4.007654] input: Power Button as /devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0C:00/input/input3 [ 4.007660] ACPI: Power Button [PWRB] [ 4.007712] input: Power Button as /devices/LNXSYSTM:00/LNXPWRBN:00/input/input4 [ 4.007716] ACPI: Power Button [PWRF] [ 4.008167] xen: registering gsi 43 triggering 0 polarity 1 [ 4.008170] xen_allocate_pirq: returning irq 43 for gsi 43 [ 4.008173] xen: --> irq=43 [ 4.008177] Already setup the GSI :43 [ 4.008180] ioatdma 0000:00:16.4: PCI INT A -> GSI 43 (level, low) -> IRQ 43 [ 4.008213] ioatdma 0000:00:16.4: setting latency timer to 64 [ 4.008304] alloc irq_desc for 1238 on node -1 [ 4.008306] alloc kstat_irqs on node -1 [ 4.008678] xen: registering gsi 44 triggering 0 polarity 1 [ 4.008682] xen_allocate_pirq: returning irq 44 for gsi 44 [ 4.008684] xen: --> irq=44 [ 4.008687] Already setup the GSI :44 [ 4.008690] ioatdma 0000:00:16.5: PCI INT B -> GSI 44 (level, low) -> IRQ 44 [ 4.008717] ioatdma 0000:00:16.5: setting latency timer to 64 [ 4.008797] alloc irq_desc for 1237 on node -1 [ 4.008800] alloc kstat_irqs on node -1 [ 4.009157] xen: registering gsi 45 triggering 0 polarity 1 [ 4.009162] xen_allocate_pirq: returning irq 45 for gsi 45 [ 4.009164] xen: --> irq=45 [ 4.009167] Already setup the GSI :45 [ 4.009170] ioatdma 0000:00:16.6: PCI INT C -> GSI 45 (level, low) -> IRQ 45 [ 4.009198] ioatdma 0000:00:16.6: setting latency timer to 64 [ 4.009289] alloc irq_desc for 1236 on node -1 [ 4.009293] alloc kstat_irqs on node -1 [ 4.009669] xen: registering gsi 46 triggering 0 polarity 1 [ 4.009672] xen_allocate_pirq: returning irq 46 for gsi 46 [ 4.009674] xen: --> irq=46 [ 4.009677] Already setup the GSI :46 [ 4.009680] ioatdma 0000:00:16.7: PCI INT D -> GSI 46 (level, low) -> IRQ 46 [ 4.009706] ioatdma 0000:00:16.7: setting latency timer to 64 [ 4.009789] alloc irq_desc for 1235 on node -1 [ 4.009791] alloc kstat_irqs on node -1 [ 4.122331] ACPI: SSDT 00000000bf79e0c0 008F0 (v01 DpgPmm P001Ist 00000011 INTL 20051117) [ 4.123073] ACPI: SSDT 00000000bf79e9b0 004D5 (v01 PmRef P001Cst 00003001 INTL 20051117) [ 4.126163] ACPI: CPU-1 (power states: C1[C1] C2[C3] C3[C3]) [ 4.127906] ACPI: CPU-1 (power states: C1[C1] C2[C3] C3[C3]) [ 4.128785] ACPI: CPU-1 (power states: C1[C1] C2[C3] C3[C3]) [ 4.130779] ACPI: CPU-1 (power states: C1[C1] C2[C3] C3[C3]) [ 4.137541] input: PC Speaker as /devices/platform/pcspkr/input/input5 [ 7.296701] xen: registering gsi 18 triggering 0 polarity 1 [ 7.296706] xen_allocate_pirq: returning irq 18 for gsi 18 [ 7.296709] xen: --> irq=18 [ 7.296714] Already setup the GSI :18 [ 7.296718] i801_smbus 0000:00:1f.3: PCI INT C -> GSI 18 (level, low) -> IRQ 18 [ 31.570836] Error: Driver 'pcspkr' is already registered, aborting... [ 31.635627] xen: registering gsi 22 triggering 0 polarity 1 [ 31.635637] alloc irq_desc for 22 on node -1 [ 31.635641] alloc kstat_irqs on node -1 [ 31.635647] xen: --> irq=22 [ 31.635657] HDA Intel 0000:00:1b.0: PCI INT A -> GSI 22 (level, low) -> IRQ 22 [ 31.635725] HDA Intel 0000:00:1b.0: setting latency timer to 64 [ 31.926667] hda-intel: no codecs found! [ 31.926920] HDA Intel 0000:00:1b.0: PCI INT A disabled [ 186.671977] Adding 7811064k swap on /dev/sda5. Priority:-1 extents:1 across:7811064k [ 187.701870] EXT3 FS on sda7, internal journal [ 190.439342] loop: module loaded [ 202.731165] kjournald starting. Commit interval 5 seconds [ 202.731449] EXT3 FS on sda1, internal journal [ 202.731457] EXT3-fs: mounted filesystem with ordered data mode. [ 202.739591] kjournald starting. Commit interval 5 seconds [ 202.739903] EXT3 FS on sda6, internal journal [ 202.739910] EXT3-fs: mounted filesystem with ordered data mode. [ 285.391611] ADDRCONF(NETDEV_UP): eth0: link is not ready [ 285.395769] e1000e: eth0 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: Rx/Tx [ 285.396222] ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready [ 296.174595] Event-channel device installed. [ 297.320190] alloc irq_desc for 1234 on node -1 [ 297.320194] alloc kstat_irqs on node -1 [ 297.320355] alloc irq_desc for 1233 on node -1 [ 297.320358] alloc kstat_irqs on node -1 [ 297.322088] XENBUS: Unable to read cpu state [ 297.322298] XENBUS: Unable to read cpu state [ 297.322490] XENBUS: Unable to read cpu state [ 297.323213] XENBUS: Unable to read cpu state [ 300.308073] Bridge firewalling registered [ 301.180816] eth0: no IPv6 routers present [ 442.059305] ADDRCONF(NETDEV_UP): peth0: link is not ready [ 445.180920] e1000e: peth0 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: Rx/Tx [ 445.181356] ADDRCONF(NETDEV_CHANGE): peth0: link becomes ready [ 445.185609] device peth0 entered promiscuous mode [ 445.200468] eth0: port 1(peth0) entering forwarding state [ 451.395728] ip_tables: (C) 2000-2006 Netfilter Core Team [ 458.353997] peth0: no IPv6 routers present [ 458.354001] eth0: no IPv6 routers present --------------000002040006090604060406 Content-Type: text/plain; name="xm-dmesg" Content-Transfer-Encoding: 7bit Content-Disposition: attachment; filename="xm-dmesg" (XEN) Xen version 4.0.1 (Debian 4.0.1-5.3) (ultrotter@debian.org) (gcc version 4.4.5 (Debian 4.4.5-8) ) Tue Aug 14 14:54:17 UTC 2012 (XEN) Bootloader: GRUB 1.98+20100804-14+squeeze1 (XEN) Command line: placeholder dom0_mem=1536M (XEN) Video information: (XEN) VGA is text mode 80x25, font 8x16 (XEN) VBE/DDC methods: V2; EDID transfer time: 1 seconds (XEN) Disc information: (XEN) Found 1 MBR signatures (XEN) Found 1 EDD information structures (XEN) Xen-e820 RAM map: (XEN) 0000000000000000 - 000000000009dc00 (usable) (XEN) 000000000009dc00 - 00000000000a0000 (reserved) (XEN) 00000000000e4000 - 0000000000100000 (reserved) (XEN) 0000000000100000 - 00000000bf790000 (usable) (XEN) 00000000bf790000 - 00000000bf79e000 (ACPI data) (XEN) 00000000bf79e000 - 00000000bf7d0000 (ACPI NVS) (XEN) 00000000bf7d0000 - 00000000bf7e0000 (reserved) (XEN) 00000000bf7ec000 - 00000000c0000000 (reserved) (XEN) 00000000e0000000 - 00000000f0000000 (reserved) (XEN) 00000000fee00000 - 00000000fee01000 (reserved) (XEN) 00000000ffc00000 - 0000000100000000 (reserved) (XEN) 0000000100000000 - 0000000140000000 (usable) (XEN) ACPI: RSDP 000FAC10, 0024 (r2 ACPIAM) (XEN) ACPI: XSDT BF790100, 005C (r1 SMCI 20100528 MSFT 97) (XEN) ACPI: FACP BF790290, 00F4 (r3 052810 FACP1443 20100528 MSFT 97) (XEN) ACPI: DSDT BF7906A0, 650A (r1 10006 10006000 0 INTL 20051117) (XEN) ACPI: FACS BF79E000, 0040 (XEN) ACPI: APIC BF790390, 011E (r1 052810 APIC1443 20100528 MSFT 97) (XEN) ACPI: MCFG BF7904B0, 003C (r1 052810 OEMMCFG 20100528 MSFT 97) (XEN) ACPI: SLIT BF7904F0, 0030 (r1 052810 OEMSLIT 20100528 MSFT 97) (XEN) ACPI: OEMB BF79E040, 007D (r1 052810 OEMB1443 20100528 MSFT 97) (XEN) ACPI: HPET BF79A6A0, 0038 (r1 052810 OEMHPET 20100528 MSFT 97) (XEN) ACPI: SSDT BF79EE90, 0363 (r1 DpgPmm CpuPm 12 INTL 20051117) (XEN) System RAM: 4087MB (4185268kB) (XEN) Domain heap initialised (XEN) Processor #0 7:10 APIC version 21 (XEN) Processor #2 7:10 APIC version 21 (XEN) Processor #4 7:10 APIC version 21 (XEN) Processor #6 7:10 APIC version 21 (XEN) IOAPIC[0]: apic_id 1, version 32, address 0xfec00000, GSI 0-23 (XEN) IOAPIC[1]: apic_id 3, version 32, address 0xfec8a000, GSI 24-47 (XEN) Enabling APIC mode: Flat. Using 2 I/O APICs (XEN) Using scheduler: SMP Credit Scheduler (credit) (XEN) Detected 2133.454 MHz processor. (XEN) Initing memory sharing. (XEN) VMX: Supported advanced features: (XEN) - APIC MMIO access virtualisation (XEN) - APIC TPR shadow (XEN) - Extended Page Tables (EPT) (XEN) - Virtual-Processor Identifiers (VPID) (XEN) - Virtual NMI (XEN) - MSR direct-access bitmap (XEN) EPT supports 2MB super page. (XEN) HVM: ASIDs enabled. (XEN) HVM: VMX enabled (XEN) HVM: Hardware Assisted Paging detected. (XEN) I/O virtualisation disabled (XEN) Total of 4 processors activated. (XEN) ENABLING IO-APIC IRQs (XEN) -> Using new ACK method (XEN) TSC is reliable, synchronization unnecessary (XEN) Platform timer appears to have unexpectedly wrapped 10 or more times. (XEN) Platform timer is 14.318MHz HPET (XEN) Allocated console ring of 16 KiB. (XEN) Brought up 4 CPUs (XEN) *** LOADING DOMAIN 0 *** (XEN) Xen kernel: 64-bit, lsb, compat32 (XEN) Dom0 kernel: 64-bit, PAE, lsb, paddr 0x1000000 -> 0x1708000 (XEN) PHYSICAL MEMORY ARRANGEMENT: (XEN) Dom0 alloc.: 0000000138000000->000000013c000000 (376832 pages to be allocated) (XEN) VIRTUAL MEMORY ARRANGEMENT: (XEN) Loaded kernel: ffffffff81000000->ffffffff81708000 (XEN) Init. ramdisk: ffffffff81708000->ffffffff8332a000 (XEN) Phys-Mach map: ffffffff8332a000->ffffffff8362a000 (XEN) Start info: ffffffff8362a000->ffffffff8362a4b4 (XEN) Page tables: ffffffff8362b000->ffffffff8364a000 (XEN) Boot stack: ffffffff8364a000->ffffffff8364b000 (XEN) TOTAL: ffffffff80000000->ffffffff83800000 (XEN) ENTRY ADDRESS: ffffffff81531200 (XEN) Dom0 has maximum 4 VCPUs (XEN) Scrubbing Free RAM: .........................done. (XEN) Xen trace buffers: disabled (XEN) Std. Loglevel: Errors and warnings (XEN) Guest Loglevel: Nothing (Rate-limited: Errors and warnings) (XEN) Xen is relinquishing VGA console. (XEN) *** Serial input -> DOM0 (type 'CTRL-a' three times to switch input to Xen) (XEN) Freed 176kB init memory. --------------000002040006090604060406 Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users --------------000002040006090604060406-- From xen-users-bounces@lists.xen.org Tue Sep 04 00:39:45 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Tue, 04 Sep 2012 00:39:45 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1T8h9q-0001Fu-AD; Tue, 04 Sep 2012 00:38:22 +0000 Received: from mail27.messagelabs.com ([193.109.254.147]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1T8h9p-0001Fp-59 for xen-users@lists.xen.org; Tue, 04 Sep 2012 00:38:21 +0000 X-Env-Sender: buck.alex@gmail.com X-Msg-Ref: server-12.tower-27.messagelabs.com!1346719089!9425869!1 X-Originating-IP: [209.85.160.45] X-SpamReason: No, hits=0.8 required=7.0 tests=BODY_RANDOM_LONG, ML_RADAR_SPEW_LINKS_14,RCVD_BY_IP,spamassassin: X-StarScan-Received: X-StarScan-Version: 6.6.1.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 11608 invoked from network); 4 Sep 2012 00:38:11 -0000 Received: from mail-pb0-f45.google.com (HELO mail-pb0-f45.google.com) (209.85.160.45) by server-12.tower-27.messagelabs.com with RC4-SHA encrypted SMTP; 4 Sep 2012 00:38:11 -0000 Received: by pbbjt11 with SMTP id jt11so8455149pbb.32 for ; Mon, 03 Sep 2012 17:38:08 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:user-agent:mime-version:to:subject :content-type; bh=GEW72uBfjb6wcYo1EKX4bHfbfjW0RYmUJg084rtLFfM=; b=EEZxdu/KFcZtiKHxPqQX2Cdw+PdxrIXgL3ieZUJfuvUZ9GvFLnsl4XDJfYpG2BHVN+ pN6c1zFfErrZH8KoNoH1eWlszqVfVyimU3romSI+wdJYkE/JdBw0Bqao5f1vbMm5M0at ZR4lwWgulqCxnMMiIkJ5m+P4HRhLnehltGahQis0m2Ho2GWDowM632OqmBL7RsIEplSk aK6w/FzADY2XO9xJD0qRtPzW6yqVqZRUNMNiGmdi2eym618lJGZcmJ5iYpOY+x7mydng mxt+qBDzQAvX6mjaFE0Rq9PwRO1iVOs8+Ukm7e3GDSmF1so2E8jlgucwgpGV1k7q89wu K1Mw== Received: by 10.68.235.68 with SMTP id uk4mr41631512pbc.52.1346719088831; Mon, 03 Sep 2012 17:38:08 -0700 (PDT) Received: from [192.168.1.60] (99-108-141-230.lightspeed.sntcca.sbcglobal.net. [99.108.141.230]) by mx.google.com with ESMTPS id uj3sm10917447pbc.39.2012.09.03.17.38.07 (version=SSLv3 cipher=OTHER); Mon, 03 Sep 2012 17:38:08 -0700 (PDT) Message-ID: <50454D6B.5090800@gmail.com> Date: Mon, 03 Sep 2012 17:38:03 -0700 From: Keith Buck User-Agent: Postbox 3.0.5 (Windows/20120826) MIME-Version: 1.0 To: xen-users@lists.xen.org Content-Type: multipart/mixed; boundary="------------000002040006090604060406" Subject: [Xen-users] Severe dom0 performance issues after installing Xen X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org This is a multi-part message in MIME format. --------------000002040006090604060406 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Hello, I'm experiencing some severe performance issues running Xen 4.0.1 with a cleanly-installed Debian 6 dom0. Prior to installation, the machine's performance was fine, but after installation booting takes anywhere from 5 to 20 times longer, processes take a long time to start, and SSH lags. No domUs are running (or have been created yet). I can switch back to running without Xen (but still using the Xen-compatible kernel) and the performance problems disappear. I attempted to dig into the issue further, but haven't been able to find any reason why the machine is so slow. Some cursory CPU integer performance and memory bandwidth benchmarks I ran showed that there is almost no difference in performance, and disk only loses about 10% of its performance. I also haven't found anything particularly alarming in dmesg or xm dmesg (although this is my first time installing Xen, so I am not sure I would know what to look for). top and xm top don't show anything constantly consuming all of the system's resources, and the only additional service I've installed so far is ntpd. As an additional debugging step, I've attempted limiting the dom0 memory to 1536MB (the machine has 4GB of physical memory). I haven't managed to turn up anything about this on Google yet. Has anyone seen a similar issue before or have ideas on how to fix/debug it? I have no physical access to the machine, unfortunately, so I am unable to play with BIOS settings. I've attached the contents of dmesg and xm dmesg, should these be useful. Thanks, Keith --------------000002040006090604060406 Content-Type: text/plain; name="dmesg" Content-Transfer-Encoding: 7bit Content-Disposition: attachment; filename="dmesg" [ 0.000000] Initializing cgroup subsys cpuset [ 0.000000] Initializing cgroup subsys cpu [ 0.000000] Linux version 2.6.32-5-xen-amd64 (Debian 2.6.32-45) (dannf@debian.org) (gcc version 4.3.5 (Debian 4.3.5-4) ) #1 SMP Sun May 6 08:57:29 UTC 2012 [ 0.000000] Command line: placeholder root=UUID=9ae68388-d77c-4f93-97cd-661e3c787190 ro quiet [ 0.000000] KERNEL supported cpus: [ 0.000000] Intel GenuineIntel [ 0.000000] AMD AuthenticAMD [ 0.000000] Centaur CentaurHauls [ 0.000000] released 0 pages of unused memory [ 0.000000] BIOS-provided physical RAM map: [ 0.000000] Xen: 0000000000000000 - 000000000009dc00 (usable) [ 0.000000] Xen: 000000000009dc00 - 0000000000100000 (reserved) [ 0.000000] Xen: 0000000000100000 - 0000000060000000 (usable) [ 0.000000] Xen: 00000000bf790000 - 00000000bf79e000 (ACPI data) [ 0.000000] Xen: 00000000bf79e000 - 00000000bf7d0000 (ACPI NVS) [ 0.000000] Xen: 00000000bf7d0000 - 00000000bf7e0000 (reserved) [ 0.000000] Xen: 00000000bf7ec000 - 00000000c0000000 (reserved) [ 0.000000] Xen: 00000000e0000000 - 00000000f0000000 (reserved) [ 0.000000] Xen: 00000000fec00000 - 00000000fec01000 (reserved) [ 0.000000] Xen: 00000000fec8a000 - 00000000fec8b000 (reserved) [ 0.000000] Xen: 00000000fee00000 - 00000000fee01000 (reserved) [ 0.000000] Xen: 00000000ffc00000 - 0000000100000000 (reserved) [ 0.000000] DMI present. [ 0.000000] AMI BIOS detected: BIOS may corrupt low RAM, working around it. [ 0.000000] e820 update range: 0000000000000000 - 0000000000010000 (usable) ==> (reserved) [ 0.000000] last_pfn = 0x60000 max_arch_pfn = 0x400000000 [ 0.000000] x86 PAT enabled: cpu 0, old 0x50100070406, new 0x7010600070106 [ 0.000000] initial memory mapped : 0 - 20000000 [ 0.000000] init_memory_mapping: 0000000000000000-0000000060000000 [ 0.000000] 0000000000 - 0060000000 page 4k [ 0.000000] kernel direct mapping tables up to 60000000 @ 100000-403000 [ 0.000000] RAMDISK: 01708000 - 0332a000 [ 0.000000] ACPI: RSDP 00000000000fac10 00024 (v02 ACPIAM) [ 0.000000] ACPI: XSDT 00000000bf790100 0005C (v01 SMCI 20100528 MSFT 00000097) [ 0.000000] ACPI: FACP 00000000bf790290 000F4 (v03 052810 FACP1443 20100528 MSFT 00000097) [ 0.000000] ACPI: DSDT 00000000bf7906a0 0650A (v01 10006 10006000 00000000 INTL 20051117) [ 0.000000] ACPI: FACS 00000000bf79e000 00040 [ 0.000000] ACPI: APIC 00000000bf790390 0011E (v01 052810 APIC1443 20100528 MSFT 00000097) [ 0.000000] ACPI: MCFG 00000000bf7904b0 0003C (v01 052810 OEMMCFG 20100528 MSFT 00000097) [ 0.000000] ACPI: SLIT 00000000bf7904f0 00030 (v01 052810 OEMSLIT 20100528 MSFT 00000097) [ 0.000000] ACPI: OEMB 00000000bf79e040 0007D (v01 052810 OEMB1443 20100528 MSFT 00000097) [ 0.000000] ACPI: HPET 00000000bf79a6a0 00038 (v01 052810 OEMHPET 20100528 MSFT 00000097) [ 0.000000] ACPI: SSDT 00000000bf79ee90 00363 (v01 DpgPmm CpuPm 00000012 INTL 20051117) [ 0.000000] ACPI: Local APIC address 0xfee00000 [ 0.000000] No NUMA configuration found [ 0.000000] Faking a node at 0000000000000000-0000000060000000 [ 0.000000] Bootmem setup node 0 0000000000000000-0000000060000000 [ 0.000000] NODE_DATA [0000000000010040 - 000000000001803f] [ 0.000000] bootmap [0000000000019000 - 0000000000024fff] pages c [ 0.000000] (9 early reservations) ==> bootmem [0000000000 - 0060000000] [ 0.000000] #0 [0000000000 - 0000001000] BIOS data page ==> [0000000000 - 0000001000] [ 0.000000] #1 [000362b000 - 000364a000] XEN PAGETABLES ==> [000362b000 - 000364a000] [ 0.000000] #2 [0000006000 - 0000008000] TRAMPOLINE ==> [0000006000 - 0000008000] [ 0.000000] #3 [0001000000 - 00016e7b44] TEXT DATA BSS ==> [0001000000 - 00016e7b44] [ 0.000000] #4 [0001708000 - 000332a000] RAMDISK ==> [0001708000 - 000332a000] [ 0.000000] #5 [000332a000 - 000362b000] XEN START INFO ==> [000332a000 - 000362b000] [ 0.000000] #6 [00016e8000 - 00016e821d] BRK ==> [00016e8000 - 00016e821d] [ 0.000000] #7 [0000100000 - 00003e1000] PGTABLE ==> [0000100000 - 00003e1000] [ 0.000000] #8 [0000010000 - 0000010030] ACPI SLIT ==> [0000010000 - 0000010030] [ 0.000000] found SMP MP-table at [ffff8800000ff780] ff780 [ 0.000000] Zone PFN ranges: [ 0.000000] DMA 0x00000010 -> 0x00001000 [ 0.000000] DMA32 0x00001000 -> 0x00100000 [ 0.000000] Normal 0x00100000 -> 0x00100000 [ 0.000000] Movable zone start PFN for each node [ 0.000000] early_node_map[2] active PFN ranges [ 0.000000] 0: 0x00000010 -> 0x0000009d [ 0.000000] 0: 0x00000100 -> 0x00060000 [ 0.000000] On node 0 totalpages: 393101 [ 0.000000] DMA zone: 56 pages used for memmap [ 0.000000] DMA zone: 740 pages reserved [ 0.000000] DMA zone: 3185 pages, LIFO batch:0 [ 0.000000] DMA32 zone: 5320 pages used for memmap [ 0.000000] DMA32 zone: 383800 pages, LIFO batch:31 [ 0.000000] ACPI: PM-Timer IO Port: 0x808 [ 0.000000] ACPI: Local APIC address 0xfee00000 [ 0.000000] ACPI: LAPIC (acpi_id[0x01] lapic_id[0x00] enabled) [ 0.000000] ACPI: LAPIC (acpi_id[0x02] lapic_id[0x02] enabled) [ 0.000000] ACPI: LAPIC (acpi_id[0x03] lapic_id[0x04] enabled) [ 0.000000] ACPI: LAPIC (acpi_id[0x04] lapic_id[0x06] enabled) [ 0.000000] ACPI: LAPIC (acpi_id[0x05] lapic_id[0x84] disabled) [ 0.000000] ACPI: LAPIC (acpi_id[0x06] lapic_id[0x85] disabled) [ 0.000000] ACPI: LAPIC (acpi_id[0x07] lapic_id[0x86] disabled) [ 0.000000] ACPI: LAPIC (acpi_id[0x08] lapic_id[0x87] disabled) [ 0.000000] ACPI: LAPIC (acpi_id[0x09] lapic_id[0x88] disabled) [ 0.000000] ACPI: LAPIC (acpi_id[0x0a] lapic_id[0x89] disabled) [ 0.000000] ACPI: LAPIC (acpi_id[0x0b] lapic_id[0x8a] disabled) [ 0.000000] ACPI: LAPIC (acpi_id[0x0c] lapic_id[0x8b] disabled) [ 0.000000] ACPI: LAPIC (acpi_id[0x0d] lapic_id[0x8c] disabled) [ 0.000000] ACPI: LAPIC (acpi_id[0x0e] lapic_id[0x8d] disabled) [ 0.000000] ACPI: LAPIC (acpi_id[0x0f] lapic_id[0x8e] disabled) [ 0.000000] ACPI: LAPIC (acpi_id[0x10] lapic_id[0x8f] disabled) [ 0.000000] ACPI: LAPIC (acpi_id[0x11] lapic_id[0x90] disabled) [ 0.000000] ACPI: LAPIC (acpi_id[0x12] lapic_id[0x91] disabled) [ 0.000000] ACPI: LAPIC (acpi_id[0x13] lapic_id[0x92] disabled) [ 0.000000] ACPI: LAPIC (acpi_id[0x14] lapic_id[0x93] disabled) [ 0.000000] ACPI: LAPIC (acpi_id[0x15] lapic_id[0x94] disabled) [ 0.000000] ACPI: LAPIC (acpi_id[0x16] lapic_id[0x95] disabled) [ 0.000000] ACPI: LAPIC (acpi_id[0x17] lapic_id[0x96] disabled) [ 0.000000] ACPI: LAPIC (acpi_id[0x18] lapic_id[0x97] disabled) [ 0.000000] ACPI: LAPIC_NMI (acpi_id[0xff] dfl dfl lint[0x1]) [ 0.000000] ACPI: IOAPIC (id[0x01] address[0xfec00000] gsi_base[0]) [ 0.000000] IOAPIC[0]: apic_id 1, version 0, address 0xfec00000, GSI 0-0 [ 0.000000] ACPI: IOAPIC (id[0x03] address[0xfec8a000] gsi_base[24]) [ 0.000000] IOAPIC[1]: apic_id 3, version 0, address 0xfec8a000, GSI 24-24 [ 0.000000] ACPI: INT_SRC_OVR (bus 0 bus_irq 0 global_irq 2 dfl dfl) [ 0.000000] ERROR: Unable to locate IOAPIC for GSI 2 [ 0.000000] ACPI: INT_SRC_OVR (bus 0 bus_irq 9 global_irq 9 high level) [ 0.000000] ERROR: Unable to locate IOAPIC for GSI 9 [ 0.000000] Using ACPI (MADT) for SMP configuration information [ 0.000000] ACPI: HPET id: 0x8086a301 base: 0xfed00000 [ 0.000000] SMP: Allowing 4 CPUs, 0 hotplug CPUs [ 0.000000] nr_irqs_gsi: 280 [ 0.000000] PM: Registered nosave memory: 000000000009d000 - 000000000009e000 [ 0.000000] PM: Registered nosave memory: 000000000009e000 - 0000000000100000 [ 0.000000] Allocating PCI resources starting at 60000000 (gap: 60000000:5f790000) [ 0.000000] Booting paravirtualized kernel on Xen [ 0.000000] Xen version: 4.0.1 (preserve-AD) (dom0) [ 0.000000] NR_CPUS:512 nr_cpumask_bits:512 nr_cpu_ids:4 nr_node_ids:1 [ 0.000000] PERCPU: Embedded 30 pages/cpu @ffff880003680000 s90328 r8192 d24360 u122880 [ 0.000000] pcpu-alloc: s90328 r8192 d24360 u122880 alloc=30*4096 [ 0.000000] pcpu-alloc: [0] 0 [0] 1 [0] 2 [0] 3 [ 1.145664] trying to map vcpu_info 0 at ffff88000368b020, mfn 13b68b, offset 32 [ 1.145668] cpu 0 using vcpu_info at ffff88000368b020 [ 1.145671] trying to map vcpu_info 1 at ffff8800036a9020, mfn 13b6a9, offset 32 [ 1.145674] cpu 1 using vcpu_info at ffff8800036a9020 [ 1.145676] trying to map vcpu_info 2 at ffff8800036c7020, mfn 13b6c7, offset 32 [ 1.145679] cpu 2 using vcpu_info at ffff8800036c7020 [ 1.145681] trying to map vcpu_info 3 at ffff8800036e5020, mfn 13b6e5, offset 32 [ 1.145684] cpu 3 using vcpu_info at ffff8800036e5020 [ 1.145685] Xen: using vcpu_info placement [ 1.145691] Built 1 zonelists in Node order, mobility grouping on. Total pages: 386985 [ 1.145693] Policy zone: DMA32 [ 1.145696] Kernel command line: placeholder root=UUID=9ae68388-d77c-4f93-97cd-661e3c787190 ro quiet [ 1.145726] PID hash table entries: 4096 (order: 3, 32768 bytes) [ 1.146059] Initializing CPU#0 [ 1.154734] DMA: Placing 64MB software IO TLB between ffff880004f58000 - ffff880008f58000 [ 1.154738] DMA: software IO TLB at phys 0x4f58000 - 0x8f58000 [ 1.154741] xen_swiotlb_fixup: buf=ffff880004f58000 size=67108864 [ 1.175539] xen_swiotlb_fixup: buf=ffff880008fb8000 size=32768 [ 1.183119] Memory: 1442072k/1572864k available (3152k kernel code, 460k absent, 130332k reserved, 2064k data, 604k init) [ 1.183159] SLUB: Genslabs=14, HWalign=64, Order=0-3, MinObjects=0, CPUs=4, Nodes=1 [ 1.183183] Hierarchical RCU implementation. [ 1.183190] NR_IRQS:4352 nr_irqs:1280 [ 1.183271] xen: --> irq=0 [ 1.183278] xen: --> irq=1 [ 1.183282] xen: --> irq=2 [ 1.183287] xen: --> irq=3 [ 1.183291] xen: --> irq=4 [ 1.183295] xen: --> irq=5 [ 1.183300] xen: --> irq=6 [ 1.183304] xen: --> irq=7 [ 1.183308] xen: --> irq=8 [ 1.183312] xen: --> irq=9 [ 1.183317] xen: --> irq=10 [ 1.183328] xen: --> irq=11 [ 1.183333] xen: --> irq=12 [ 1.183337] xen: --> irq=13 [ 1.183342] xen: --> irq=14 [ 1.183346] xen: --> irq=15 [ 1.183362] ACPI: INT_SRC_OVR (bus 0 bus_irq 0 global_irq 2 dfl dfl) [ 1.183366] ACPI: INT_SRC_OVR (bus 0 bus_irq 9 global_irq 9 high level) [ 1.183368] xen: sci override: source_irq=9 global_irq=9 trigger=c polarity=1 [ 1.183371] xen: registering gsi 9 triggering 0 polarity 0 [ 1.183373] xen_allocate_pirq: returning irq 9 for gsi 9 [ 1.183375] xen: --> irq=9 [ 1.183382] xen: acpi sci 9 [ 1.189510] Console: colour VGA+ 80x25 [ 1.189622] console [tty0] enabled [ 1.189650] Xen: using vcpuop timer interface [ 1.189654] installing Xen timer for CPU 0 [ 1.189661] alloc irq_desc for 1279 on node -1 [ 1.189664] alloc kstat_irqs on node -1 [ 1.189683] Detected 2133.454 MHz processor. [ 1.189690] Calibrating delay loop (skipped), value calculated using timer frequency.. 4266.90 BogoMIPS (lpj=8533816) [ 1.189707] Security Framework initialized [ 1.189713] SELinux: Disabled at boot. [ 1.190094] Dentry cache hash table entries: 262144 (order: 9, 2097152 bytes) [ 1.190727] Inode-cache hash table entries: 131072 (order: 8, 1048576 bytes) [ 1.190972] Mount-cache hash table entries: 256 [ 1.191101] Initializing cgroup subsys ns [ 1.191105] Initializing cgroup subsys cpuacct [ 1.191110] Initializing cgroup subsys devices [ 1.191113] Initializing cgroup subsys freezer [ 1.191115] Initializing cgroup subsys net_cls [ 1.191152] CPU: L1 I cache: 32K, L1 D cache: 32K [ 1.191155] CPU: L2 cache: 256K [ 1.191157] CPU: L3 cache: 4096K [ 1.191162] CPU 0/0x0 -> Node 0 [ 1.191164] CPU: Unsupported number of siblings 16 [ 1.191169] mce: CPU supports 9 MCE banks [ 1.191195] Performance Events: unsupported p6 CPU model 26 no PMU driver, software events only. [ 1.191210] SMP alternatives: switching to UP code [ 1.218048] ACPI: Core revision 20090903 [ 1.248472] alloc irq_desc for 1278 on node -1 [ 1.248474] alloc kstat_irqs on node -1 [ 1.248484] alloc irq_desc for 1277 on node -1 [ 1.248486] alloc kstat_irqs on node -1 [ 1.248490] alloc irq_desc for 1276 on node -1 [ 1.248493] alloc kstat_irqs on node -1 [ 1.248497] alloc irq_desc for 1275 on node -1 [ 1.248499] alloc kstat_irqs on node -1 [ 1.248666] installing Xen timer for CPU 1 [ 1.248669] alloc irq_desc for 1274 on node -1 [ 1.248671] alloc kstat_irqs on node -1 [ 1.248700] SMP alternatives: switching to SMP code [ 1.274563] alloc irq_desc for 1273 on node -1 [ 1.274566] alloc kstat_irqs on node -1 [ 1.274578] alloc irq_desc for 1272 on node -1 [ 1.274581] alloc kstat_irqs on node -1 [ 1.274585] alloc irq_desc for 1271 on node -1 [ 1.274588] alloc kstat_irqs on node -1 [ 1.274592] alloc irq_desc for 1270 on node -1 [ 1.274595] alloc kstat_irqs on node -1 [ 1.274608] Initializing CPU#1 [ 1.274648] CPU: L1 I cache: 32K, L1 D cache: 32K [ 1.274651] CPU: L2 cache: 256K [ 1.274652] CPU: L3 cache: 4096K [ 1.274656] CPU 1/0x0 -> Node 0 [ 1.274658] CPU: Unsupported number of siblings 16 [ 1.274760] installing Xen timer for CPU 2 [ 1.274764] alloc irq_desc for 1269 on node -1 [ 1.274767] alloc kstat_irqs on node -1 [ 1.274792] alloc irq_desc for 1268 on node -1 [ 1.274794] alloc kstat_irqs on node -1 [ 1.274800] alloc irq_desc for 1267 on node -1 [ 1.274802] alloc kstat_irqs on node -1 [ 1.274807] alloc irq_desc for 1266 on node -1 [ 1.274809] alloc kstat_irqs on node -1 [ 1.274816] alloc irq_desc for 1265 on node -1 [ 1.274818] alloc kstat_irqs on node -1 [ 1.274829] Initializing CPU#2 [ 1.274867] CPU: L1 I cache: 32K, L1 D cache: 32K [ 1.274870] CPU: L2 cache: 256K [ 1.274871] CPU: L3 cache: 4096K [ 1.274875] CPU 2/0x0 -> Node 0 [ 1.274877] CPU: Unsupported number of siblings 16 [ 1.274973] installing Xen timer for CPU 3 [ 1.274977] alloc irq_desc for 1264 on node -1 [ 1.274980] alloc kstat_irqs on node -1 [ 1.275001] alloc irq_desc for 1263 on node -1 [ 1.275003] alloc kstat_irqs on node -1 [ 1.275008] alloc irq_desc for 1262 on node -1 [ 1.275011] alloc kstat_irqs on node -1 [ 1.275015] alloc irq_desc for 1261 on node -1 [ 1.275017] alloc kstat_irqs on node -1 [ 1.275022] alloc irq_desc for 1260 on node -1 [ 1.275024] alloc kstat_irqs on node -1 [ 1.275035] Initializing CPU#3 [ 1.275073] CPU: L1 I cache: 32K, L1 D cache: 32K [ 1.275075] CPU: L2 cache: 256K [ 1.275077] CPU: L3 cache: 4096K [ 1.275081] CPU 3/0x0 -> Node 0 [ 1.275083] CPU: Unsupported number of siblings 16 [ 1.275120] Brought up 4 CPUs [ 1.275146] CPU0 attaching sched-domain: [ 1.275149] domain 0: span 0-3 level CPU [ 1.275152] groups: group ffff88000368fd00 cpus 0 group ffff8800036add00 cpus 1 group ffff8800036cbd00 cpus 2 group ffff8800036e9d00 cpus 3 [ 1.275164] CPU1 attaching sched-domain: [ 1.275166] domain 0: span 0-3 level CPU [ 1.275169] groups: group ffff8800036add00 cpus 1 group ffff8800036cbd00 cpus 2 group ffff8800036e9d00 cpus 3 group ffff88000368fd00 cpus 0 [ 1.275179] CPU2 attaching sched-domain: [ 1.275181] domain 0: span 0-3 level CPU [ 1.275183] groups: group ffff8800036cbd00 cpus 2 group ffff8800036e9d00 cpus 3 group ffff88000368fd00 cpus 0 group ffff8800036add00 cpus 1 [ 1.275193] CPU3 attaching sched-domain: [ 1.275195] domain 0: span 0-3 level CPU [ 1.275198] groups: group ffff8800036e9d00 cpus 3 group ffff88000368fd00 cpus 0 group ffff8800036add00 cpus 1 group ffff8800036cbd00 cpus 2 [ 1.275466] devtmpfs: initialized [ 1.278443] Grant table initialized [ 1.278446] regulator: core version 0.5 [ 1.278499] NET: Registered protocol family 16 [ 1.278551] alloc irq_desc for 1259 on node -1 [ 1.278553] alloc kstat_irqs on node -1 [ 1.278687] ACPI: bus type pci registered [ 1.278703] sync cpu 0 get result 1 max_id 3 [ 1.278715] sync cpu 1 get result 1 max_id 3 [ 1.278724] sync cpu 2 get result 1 max_id 3 [ 1.278732] sync cpu 3 get result 1 max_id 3 [ 1.278737] alloc irq_desc for 1258 on node -1 [ 1.278739] alloc kstat_irqs on node -1 [ 1.278826] PCI: MCFG configuration 0: base e0000000 segment 0 buses 0 - 255 [ 1.278829] PCI: MCFG area at e0000000 reserved in E820 [ 1.325249] PCI: Using MMCONFIG at e0000000 - efffffff [ 1.325251] PCI: Using configuration type 1 for base access [ 1.325856] bio: create slab at 0 [ 1.327251] ERROR: Unable to locate IOAPIC for GSI 9 [ 1.327321] ACPI: EC: Look up EC in DSDT [ 1.330013] ACPI Warning for \_SB_._OSC: Return type mismatch - found Integer, expected Buffer (20090903/nspredef-1006) [ 1.330023] \_SB_:_OSC evaluation returned wrong type [ 1.330025] _OSC request data:1 7 [ 1.331152] ACPI: Executed 1 blocks of module-level executable AML code [ 1.342955] ACPI: Interpreter enabled [ 1.342958] ACPI: (supports S0 S1 S4 S5) [ 1.342989] ACPI: Using IOAPIC for interrupt routing [ 1.356571] ACPI Warning: Incorrect checksum in table [OEMB] - 64, should be 61 (20090903/tbutils-314) [ 1.356768] ACPI: No dock devices found. [ 1.357003] ACPI: PCI Root Bridge [PCI0] (0000:00) [ 1.357183] pci 0000:00:00.0: PME# supported from D0 D3hot D3cold [ 1.357190] pci 0000:00:00.0: PME# disabled [ 1.357374] pci 0000:00:01.0: PME# supported from D0 D3hot D3cold [ 1.357381] pci 0000:00:01.0: PME# disabled [ 1.357565] pci 0000:00:03.0: PME# supported from D0 D3hot D3cold [ 1.357571] pci 0000:00:03.0: PME# disabled [ 1.357759] pci 0000:00:07.0: PME# supported from D0 D3hot D3cold [ 1.357765] pci 0000:00:07.0: PME# disabled [ 1.357950] pci 0000:00:09.0: PME# supported from D0 D3hot D3cold [ 1.357956] pci 0000:00:09.0: PME# disabled [ 1.358034] pci 0000:00:13.0: reg 10 32bit mmio: [0xfec8a000-0xfec8afff] [ 1.358122] pci 0000:00:13.0: PME# supported from D0 D3hot D3cold [ 1.358128] pci 0000:00:13.0: PME# disabled [ 1.358662] pci 0000:00:16.0: reg 10 64bit mmio: [0xfbef8000-0xfbefbfff] [ 1.358832] pci 0000:00:16.1: reg 10 64bit mmio: [0xfbef4000-0xfbef7fff] [ 1.359002] pci 0000:00:16.2: reg 10 64bit mmio: [0xfbef0000-0xfbef3fff] [ 1.359172] pci 0000:00:16.3: reg 10 64bit mmio: [0xfbeec000-0xfbeeffff] [ 1.359341] pci 0000:00:16.4: reg 10 64bit mmio: [0xfbee8000-0xfbeebfff] [ 1.359511] pci 0000:00:16.5: reg 10 64bit mmio: [0xfbee4000-0xfbee7fff] [ 1.359682] pci 0000:00:16.6: reg 10 64bit mmio: [0xfbee0000-0xfbee3fff] [ 1.359853] pci 0000:00:16.7: reg 10 64bit mmio: [0xfbedc000-0xfbedffff] [ 1.360062] pci 0000:00:1a.0: reg 20 io port: [0xcc00-0xcc1f] [ 1.360215] pci 0000:00:1a.1: reg 20 io port: [0xc880-0xc89f] [ 1.360368] pci 0000:00:1a.2: reg 20 io port: [0xc800-0xc81f] [ 1.360522] pci 0000:00:1a.7: reg 10 32bit mmio: [0xfbeda000-0xfbeda3ff] [ 1.360655] pci 0000:00:1a.7: PME# supported from D0 D3hot D3cold [ 1.360661] pci 0000:00:1a.7: PME# disabled [ 1.360738] pci 0000:00:1b.0: reg 10 64bit mmio: [0xfbed4000-0xfbed7fff] [ 1.360849] pci 0000:00:1b.0: PME# supported from D0 D3hot D3cold [ 1.360855] pci 0000:00:1b.0: PME# disabled [ 1.361009] pci 0000:00:1c.0: PME# supported from D0 D3hot D3cold [ 1.361015] pci 0000:00:1c.0: PME# disabled [ 1.361192] pci 0000:00:1c.4: PME# supported from D0 D3hot D3cold [ 1.361199] pci 0000:00:1c.4: PME# disabled [ 1.361367] pci 0000:00:1c.5: PME# supported from D0 D3hot D3cold [ 1.361373] pci 0000:00:1c.5: PME# disabled [ 1.361481] pci 0000:00:1d.0: reg 20 io port: [0xc480-0xc49f] [ 1.361634] pci 0000:00:1d.1: reg 20 io port: [0xc400-0xc41f] [ 1.361788] pci 0000:00:1d.2: reg 20 io port: [0xc080-0xc09f] [ 1.361946] pci 0000:00:1d.7: reg 10 32bit mmio: [0xfbed8000-0xfbed83ff] [ 1.362084] pci 0000:00:1d.7: PME# supported from D0 D3hot D3cold [ 1.362091] pci 0000:00:1d.7: PME# disabled [ 1.362350] pci 0000:00:1f.0: ICH7 LPC Generic IO decode 1 PIO at 0a00 (mask 00ff) [ 1.362355] pci 0000:00:1f.0: ICH7 LPC Generic IO decode 2 PIO at 4700 (mask 00ff) [ 1.362478] pci 0000:00:1f.2: reg 10 io port: [0xc000-0xc007] [ 1.362489] pci 0000:00:1f.2: reg 14 io port: [0xbc00-0xbc03] [ 1.362499] pci 0000:00:1f.2: reg 18 io port: [0xb880-0xb887] [ 1.362509] pci 0000:00:1f.2: reg 1c io port: [0xb800-0xb803] [ 1.362519] pci 0000:00:1f.2: reg 20 io port: [0xb480-0xb48f] [ 1.362530] pci 0000:00:1f.2: reg 24 io port: [0xb400-0xb40f] [ 1.362651] pci 0000:00:1f.3: reg 10 64bit mmio: [0xfbed2000-0xfbed20ff] [ 1.362677] pci 0000:00:1f.3: reg 20 io port: [0x400-0x41f] [ 1.362770] pci 0000:00:1f.5: reg 10 io port: [0xb000-0xb007] [ 1.362781] pci 0000:00:1f.5: reg 14 io port: [0xac00-0xac03] [ 1.362791] pci 0000:00:1f.5: reg 18 io port: [0xa880-0xa887] [ 1.362801] pci 0000:00:1f.5: reg 1c io port: [0xa800-0xa803] [ 1.362811] pci 0000:00:1f.5: reg 20 io port: [0xa480-0xa48f] [ 1.362822] pci 0000:00:1f.5: reg 24 io port: [0xa400-0xa40f] [ 1.363388] pci 0000:06:00.0: reg 10 32bit mmio: [0xfbce0000-0xfbcfffff] [ 1.363417] pci 0000:06:00.0: reg 18 io port: [0xdc00-0xdc1f] [ 1.363433] pci 0000:06:00.0: reg 1c 32bit mmio: [0xfbcdc000-0xfbcdffff] [ 1.363612] pci 0000:06:00.0: PME# supported from D0 D3hot D3cold [ 1.363621] pci 0000:06:00.0: PME# disabled [ 1.369340] pci 0000:00:1c.4: bridge io port: [0xd000-0xdfff] [ 1.369346] pci 0000:00:1c.4: bridge 32bit mmio: [0xfbc00000-0xfbcfffff] [ 1.369451] pci 0000:07:00.0: reg 10 32bit mmio: [0xfbde0000-0xfbdfffff] [ 1.369480] pci 0000:07:00.0: reg 18 io port: [0xec00-0xec1f] [ 1.369496] pci 0000:07:00.0: reg 1c 32bit mmio: [0xfbddc000-0xfbddffff] [ 1.369674] pci 0000:07:00.0: PME# supported from D0 D3hot D3cold [ 1.369683] pci 0000:07:00.0: PME# disabled [ 1.377351] pci 0000:00:1c.5: bridge io port: [0xe000-0xefff] [ 1.377358] pci 0000:00:1c.5: bridge 32bit mmio: [0xfbd00000-0xfbdfffff] [ 1.377430] pci 0000:08:01.0: reg 10 32bit mmio pref: [0xf9000000-0xf9ffffff] [ 1.377441] pci 0000:08:01.0: reg 14 32bit mmio: [0xfaffc000-0xfaffffff] [ 1.377453] pci 0000:08:01.0: reg 18 32bit mmio: [0xfb000000-0xfb7fffff] [ 1.377625] pci 0000:00:1e.0: transparent bridge [ 1.377636] pci 0000:00:1e.0: bridge 32bit mmio: [0xfaf00000-0xfb7fffff] [ 1.377646] pci 0000:00:1e.0: bridge 64bit mmio pref: [0xf9000000-0xf9ffffff] [ 1.377717] ACPI: PCI Interrupt Routing Table [\_SB_.PCI0._PRT] [ 1.378281] ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.NPE1._PRT] [ 1.378371] ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.NPE3._PRT] [ 1.378471] ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.NPE7._PRT] [ 1.378559] ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.NPE9._PRT] [ 1.378647] ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.P0P1._PRT] [ 1.378837] ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.P0P4._PRT] [ 1.378935] ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.P0P8._PRT] [ 1.379017] ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.P0P9._PRT] [ 1.432947] ACPI: PCI Interrupt Link [LNKA] (IRQs 3 4 6 7 10 *11 12 14 15) [ 1.433098] ACPI: PCI Interrupt Link [LNKB] (IRQs 3 4 6 7 *10 11 12 14 15) [ 1.433246] ACPI: PCI Interrupt Link [LNKC] (IRQs 3 4 6 7 10 11 12 14 *15) [ 1.433395] ACPI: PCI Interrupt Link [LNKD] (IRQs 3 4 6 7 10 11 12 *14 15) [ 1.433543] ACPI: PCI Interrupt Link [LNKE] (IRQs 3 4 6 7 10 11 12 14 15) *0, disabled. [ 1.433696] ACPI: PCI Interrupt Link [LNKF] (IRQs 3 4 6 *7 10 11 12 14 15) [ 1.433845] ACPI: PCI Interrupt Link [LNKG] (IRQs 3 4 *6 7 10 11 12 14 15) [ 1.434005] ACPI: PCI Interrupt Link [LNKH] (IRQs 3 4 6 7 *10 11 12 14 15) [ 1.434101] xen_balloon: Initialising balloon driver with page order 0. [ 1.434177] vgaarb: device added: PCI:0000:08:01.0,decodes=io+mem,owns=io+mem,locks=none [ 1.434180] vgaarb: loaded [ 1.434267] PCI: Using ACPI for IRQ routing [ 1.434588] Switching to clocksource xen [ 1.436132] pnp: PnP ACPI init [ 1.436148] ACPI: bus type pnp registered [ 1.436785] xen: registering gsi 8 triggering 1 polarity 0 [ 1.436788] xen_allocate_pirq: returning irq 8 for gsi 8 [ 1.436790] xen: --> irq=8 [ 1.437025] xen: registering gsi 13 triggering 1 polarity 0 [ 1.437028] xen_allocate_pirq: returning irq 13 for gsi 13 [ 1.437030] xen: --> irq=13 [ 1.437819] xen: registering gsi 4 triggering 1 polarity 0 [ 1.437822] xen_allocate_pirq: returning irq 4 for gsi 4 [ 1.437824] xen: --> irq=4 [ 1.438459] xen: registering gsi 3 triggering 1 polarity 0 [ 1.438461] xen_allocate_pirq: returning irq 3 for gsi 3 [ 1.438463] xen: --> irq=3 [ 1.440449] pnp: PnP ACPI: found 14 devices [ 1.440451] ACPI: ACPI bus type pnp unregistered [ 1.440463] system 00:01: iomem range 0xfed1c000-0xfed1ffff has been reserved [ 1.440471] system 00:06: ioport range 0xa10-0xa1f has been reserved [ 1.440478] system 00:09: ioport range 0xca2-0xca3 has been reserved [ 1.440481] system 00:09: ioport range 0xcf8-0xcff could not be reserved [ 1.440484] system 00:09: ioport range 0x4d0-0x4d1 has been reserved [ 1.440488] system 00:09: ioport range 0x800-0x87f has been reserved [ 1.440491] system 00:09: ioport range 0x500-0x57f has been reserved [ 1.440494] system 00:09: iomem range 0x400-0x4ff could not be reserved [ 1.440498] system 00:09: iomem range 0xfed1c000-0xfed1ffff has been reserved [ 1.440501] system 00:09: iomem range 0xfed20000-0xfed3ffff has been reserved [ 1.440505] system 00:09: iomem range 0xfed40000-0xfed8ffff has been reserved [ 1.440511] system 00:0b: iomem range 0xfec00000-0xfec00fff could not be reserved [ 1.440515] system 00:0b: iomem range 0xfee00000-0xfee00fff has been reserved [ 1.440521] system 00:0c: iomem range 0xe0000000-0xefffffff has been reserved [ 1.440527] system 00:0d: iomem range 0xc0000-0xcffff could not be reserved [ 1.440530] system 00:0d: iomem range 0xe0000-0xfffff could not be reserved [ 1.440534] system 00:0d: iomem range 0xfed90000-0xffffffff could not be reserved [ 1.445620] PM-Timer failed consistency check (0x0xffffff) - aborting. [ 1.445759] pci 0000:00:01.0: PCI bridge, secondary bus 0000:01 [ 1.445762] pci 0000:00:01.0: IO window: disabled [ 1.445770] pci 0000:00:01.0: MEM window: disabled [ 1.445775] pci 0000:00:01.0: PREFETCH window: disabled [ 1.445785] pci 0000:00:03.0: PCI bridge, secondary bus 0000:02 [ 1.445787] pci 0000:00:03.0: IO window: disabled [ 1.445795] pci 0000:00:03.0: MEM window: disabled [ 1.445801] pci 0000:00:03.0: PREFETCH window: disabled [ 1.445810] pci 0000:00:07.0: PCI bridge, secondary bus 0000:03 [ 1.445812] pci 0000:00:07.0: IO window: disabled [ 1.445820] pci 0000:00:07.0: MEM window: disabled [ 1.445825] pci 0000:00:07.0: PREFETCH window: disabled [ 1.445835] pci 0000:00:09.0: PCI bridge, secondary bus 0000:04 [ 1.445837] pci 0000:00:09.0: IO window: disabled [ 1.445845] pci 0000:00:09.0: MEM window: disabled [ 1.445851] pci 0000:00:09.0: PREFETCH window: disabled [ 1.445860] pci 0000:00:1c.0: PCI bridge, secondary bus 0000:05 [ 1.445865] pci 0000:00:1c.0: IO window: 0x1000-0x1fff [ 1.445873] pci 0000:00:1c.0: MEM window: 0x60000000-0x601fffff [ 1.445880] pci 0000:00:1c.0: PREFETCH window: 0x00000060200000-0x000000603fffff [ 1.445890] pci 0000:00:1c.4: PCI bridge, secondary bus 0000:06 [ 1.445895] pci 0000:00:1c.4: IO window: 0xd000-0xdfff [ 1.445903] pci 0000:00:1c.4: MEM window: 0xfbc00000-0xfbcfffff [ 1.445909] pci 0000:00:1c.4: PREFETCH window: 0x00000060400000-0x000000605fffff [ 1.445920] pci 0000:00:1c.5: PCI bridge, secondary bus 0000:07 [ 1.445924] pci 0000:00:1c.5: IO window: 0xe000-0xefff [ 1.445932] pci 0000:00:1c.5: MEM window: 0xfbd00000-0xfbdfffff [ 1.445939] pci 0000:00:1c.5: PREFETCH window: 0x00000060600000-0x000000607fffff [ 1.445949] pci 0000:00:1e.0: PCI bridge, secondary bus 0000:08 [ 1.445952] pci 0000:00:1e.0: IO window: disabled [ 1.445960] pci 0000:00:1e.0: MEM window: 0xfaf00000-0xfb7fffff [ 1.445966] pci 0000:00:1e.0: PREFETCH window: 0x000000f9000000-0x000000f9ffffff [ 1.445991] pci 0000:00:01.0: setting latency timer to 64 [ 1.446008] pci 0000:00:03.0: setting latency timer to 64 [ 1.446024] pci 0000:00:07.0: setting latency timer to 64 [ 1.446040] pci 0000:00:09.0: setting latency timer to 64 [ 1.446053] pci 0000:00:1c.0: enabling device (0104 -> 0107) [ 1.446059] xen: registering gsi 17 triggering 0 polarity 1 [ 1.446067] alloc irq_desc for 17 on node -1 [ 1.446069] alloc kstat_irqs on node -1 [ 1.446074] xen: --> irq=17 [ 1.446080] pci 0000:00:1c.0: PCI INT A -> GSI 17 (level, low) -> IRQ 17 [ 1.446086] pci 0000:00:1c.0: setting latency timer to 64 [ 1.446100] xen: registering gsi 17 triggering 0 polarity 1 [ 1.446103] xen_allocate_pirq: returning irq 17 for gsi 17 [ 1.446104] xen: --> irq=17 [ 1.446107] Already setup the GSI :17 [ 1.446109] pci 0000:00:1c.4: PCI INT A -> GSI 17 (level, low) -> IRQ 17 [ 1.446116] pci 0000:00:1c.4: setting latency timer to 64 [ 1.446129] xen: registering gsi 16 triggering 0 polarity 1 [ 1.446134] alloc irq_desc for 16 on node -1 [ 1.446136] alloc kstat_irqs on node -1 [ 1.446139] xen: --> irq=16 [ 1.446143] pci 0000:00:1c.5: PCI INT B -> GSI 16 (level, low) -> IRQ 16 [ 1.446149] pci 0000:00:1c.5: setting latency timer to 64 [ 1.446161] pci 0000:00:1e.0: setting latency timer to 64 [ 1.446166] pci_bus 0000:00: resource 0 io: [0x00-0xffff] [ 1.446169] pci_bus 0000:00: resource 1 mem: [0x000000-0xffffffffffffffff] [ 1.446172] pci_bus 0000:05: resource 0 io: [0x1000-0x1fff] [ 1.446175] pci_bus 0000:05: resource 1 mem: [0x60000000-0x601fffff] [ 1.446177] pci_bus 0000:05: resource 2 pref mem [0x60200000-0x603fffff] [ 1.446180] pci_bus 0000:06: resource 0 io: [0xd000-0xdfff] [ 1.446183] pci_bus 0000:06: resource 1 mem: [0xfbc00000-0xfbcfffff] [ 1.446185] pci_bus 0000:06: resource 2 pref mem [0x60400000-0x605fffff] [ 1.446188] pci_bus 0000:07: resource 0 io: [0xe000-0xefff] [ 1.446191] pci_bus 0000:07: resource 1 mem: [0xfbd00000-0xfbdfffff] [ 1.446193] pci_bus 0000:07: resource 2 pref mem [0x60600000-0x607fffff] [ 1.446196] pci_bus 0000:08: resource 1 mem: [0xfaf00000-0xfb7fffff] [ 1.446199] pci_bus 0000:08: resource 2 pref mem [0xf9000000-0xf9ffffff] [ 1.446202] pci_bus 0000:08: resource 3 io: [0x00-0xffff] [ 1.446204] pci_bus 0000:08: resource 4 mem: [0x000000-0xffffffffffffffff] [ 1.446230] NET: Registered protocol family 2 [ 1.446411] IP route cache hash table entries: 65536 (order: 7, 524288 bytes) [ 1.447389] TCP established hash table entries: 262144 (order: 10, 4194304 bytes) [ 1.448480] TCP bind hash table entries: 65536 (order: 8, 1048576 bytes) [ 1.448709] TCP: Hash tables configured (established 262144 bind 65536) [ 1.448712] TCP reno registered [ 1.448811] NET: Registered protocol family 1 [ 1.448863] xen: registering gsi 16 triggering 0 polarity 1 [ 1.448867] xen_allocate_pirq: returning irq 16 for gsi 16 [ 1.448869] xen: --> irq=16 [ 1.448873] Already setup the GSI :16 [ 1.448876] pci 0000:00:1a.0: PCI INT A -> GSI 16 (level, low) -> IRQ 16 [ 1.448903] pci 0000:00:1a.0: PCI INT A disabled [ 1.448910] xen: registering gsi 21 triggering 0 polarity 1 [ 1.448919] alloc irq_desc for 21 on node -1 [ 1.448922] alloc kstat_irqs on node -1 [ 1.448927] xen: --> irq=21 [ 1.448933] pci 0000:00:1a.1: PCI INT B -> GSI 21 (level, low) -> IRQ 21 [ 1.448957] pci 0000:00:1a.1: PCI INT B disabled [ 1.448965] xen: registering gsi 19 triggering 0 polarity 1 [ 1.448969] alloc irq_desc for 19 on node -1 [ 1.448971] alloc kstat_irqs on node -1 [ 1.448974] xen: --> irq=19 [ 1.448978] pci 0000:00:1a.2: PCI INT D -> GSI 19 (level, low) -> IRQ 19 [ 1.449003] pci 0000:00:1a.2: PCI INT D disabled [ 1.449018] xen: registering gsi 18 triggering 0 polarity 1 [ 1.449022] alloc irq_desc for 18 on node -1 [ 1.449024] alloc kstat_irqs on node -1 [ 1.449027] xen: --> irq=18 [ 1.449031] pci 0000:00:1a.7: PCI INT C -> GSI 18 (level, low) -> IRQ 18 [ 1.449075] pci 0000:00:1a.7: PCI INT C disabled [ 1.449088] xen: registering gsi 23 triggering 0 polarity 1 [ 1.449092] alloc irq_desc for 23 on node -1 [ 1.449095] alloc kstat_irqs on node -1 [ 1.449098] xen: --> irq=23 [ 1.449102] pci 0000:00:1d.0: PCI INT A -> GSI 23 (level, low) -> IRQ 23 [ 1.449127] pci 0000:00:1d.0: PCI INT A disabled [ 1.449134] xen: registering gsi 19 triggering 0 polarity 1 [ 1.449136] xen_allocate_pirq: returning irq 19 for gsi 19 [ 1.449138] xen: --> irq=19 [ 1.449140] Already setup the GSI :19 [ 1.449143] pci 0000:00:1d.1: PCI INT B -> GSI 19 (level, low) -> IRQ 19 [ 1.449167] pci 0000:00:1d.1: PCI INT B disabled [ 1.449174] xen: registering gsi 18 triggering 0 polarity 1 [ 1.449177] xen_allocate_pirq: returning irq 18 for gsi 18 [ 1.449179] xen: --> irq=18 [ 1.449181] Already setup the GSI :18 [ 1.449183] pci 0000:00:1d.2: PCI INT C -> GSI 18 (level, low) -> IRQ 18 [ 1.449208] pci 0000:00:1d.2: PCI INT C disabled [ 1.449222] xen: registering gsi 23 triggering 0 polarity 1 [ 1.449224] xen_allocate_pirq: returning irq 23 for gsi 23 [ 1.449226] xen: --> irq=23 [ 1.449228] Already setup the GSI :23 [ 1.449231] pci 0000:00:1d.7: PCI INT A -> GSI 23 (level, low) -> IRQ 23 [ 1.449255] pci 0000:00:1d.7: PCI INT A disabled [ 1.449273] pci 0000:08:01.0: Boot video device [ 1.449323] Unpacking initramfs... [ 1.473770] Freeing initrd memory: 28808k freed [ 1.479791] PCI-DMA: Using software bounce buffering for IO (SWIOTLB) [ 1.479797] DMA: Placing 64MB software IO TLB between ffff880004f58000 - ffff880008f58000 [ 1.479800] DMA: software IO TLB at phys 0x4f58000 - 0x8f58000 [ 1.480367] audit: initializing netlink socket (disabled) [ 1.480380] type=2000 audit(1346634674.413:1): initialized [ 1.483775] HugeTLB registered 2 MB page size, pre-allocated 0 pages [ 1.485416] VFS: Disk quotas dquot_6.5.2 [ 1.485466] Dquot-cache hash table entries: 512 (order 0, 4096 bytes) [ 1.485549] msgmni has been set to 2872 [ 1.485859] alg: No test for stdrng (krng) [ 1.485915] Block layer SCSI generic (bsg) driver version 0.4 loaded (major 253) [ 1.485919] io scheduler noop registered [ 1.485921] io scheduler anticipatory registered [ 1.485923] io scheduler deadline registered [ 1.485979] io scheduler cfq registered (default) [ 1.486213] alloc irq_desc for 1257 on node -1 [ 1.486215] alloc kstat_irqs on node -1 [ 1.486257] pcieport 0000:00:01.0: setting latency timer to 64 [ 1.486473] alloc irq_desc for 1256 on node -1 [ 1.486476] alloc kstat_irqs on node -1 [ 1.486505] pcieport 0000:00:03.0: setting latency timer to 64 [ 1.486729] alloc irq_desc for 1255 on node -1 [ 1.486732] alloc kstat_irqs on node -1 [ 1.486761] pcieport 0000:00:07.0: setting latency timer to 64 [ 1.486973] alloc irq_desc for 1254 on node -1 [ 1.486976] alloc kstat_irqs on node -1 [ 1.487005] pcieport 0000:00:09.0: setting latency timer to 64 [ 1.487198] alloc irq_desc for 1253 on node -1 [ 1.487200] alloc kstat_irqs on node -1 [ 1.487233] pcieport 0000:00:1c.0: setting latency timer to 64 [ 1.487430] alloc irq_desc for 1252 on node -1 [ 1.487433] alloc kstat_irqs on node -1 [ 1.487463] pcieport 0000:00:1c.4: setting latency timer to 64 [ 1.487658] alloc irq_desc for 1251 on node -1 [ 1.487660] alloc kstat_irqs on node -1 [ 1.487690] pcieport 0000:00:1c.5: setting latency timer to 64 [ 1.487817] aer 0000:00:01.0:pcie02: AER service couldn't init device: no _OSC support [ 1.487827] aer 0000:00:03.0:pcie02: AER service couldn't init device: no _OSC support [ 1.487833] aer 0000:00:07.0:pcie02: AER service couldn't init device: no _OSC support [ 1.487840] aer 0000:00:09.0:pcie02: AER service couldn't init device: no _OSC support [ 1.491913] registering netback [ 1.492020] alloc irq_desc for 1250 on node -1 [ 1.492023] alloc kstat_irqs on node -1 [ 1.493450] alloc irq_desc for 1249 on node -1 [ 1.493453] alloc kstat_irqs on node -1 [ 1.493826] hpet_acpi_add: no address or irqs in _CRS [ 1.493842] Linux agpgart interface v0.103 [ 1.493893] Serial: 8250/16550 driver, 4 ports, IRQ sharing enabled [ 1.494024] serial8250: ttyS0 at I/O 0x3f8 (irq = 4) is a 16550A [ 1.494155] serial8250: ttyS1 at I/O 0x2f8 (irq = 3) is a 16550A [ 1.494446] 00:07: ttyS0 at I/O 0x3f8 (irq = 4) is a 16550A [ 1.494605] 00:08: ttyS1 at I/O 0x2f8 (irq = 3) is a 16550A [ 1.494772] input: Macintosh mouse button emulation as /devices/virtual/input/input0 [ 1.494831] PNP: No PS/2 controller found. Probing ports directly. [ 1.497494] serio: i8042 KBD port at 0x60,0x64 irq 1 [ 1.497502] serio: i8042 AUX port at 0x60,0x64 irq 12 [ 1.497587] mice: PS/2 mouse device common for all mice [ 1.497630] rtc_cmos 00:03: RTC can wake from S4 [ 1.497670] rtc_cmos 00:03: rtc core: registered rtc_cmos as rtc0 [ 1.497703] rtc0: alarms up to one month, y3k, 114 bytes nvram [ 1.497718] cpuidle: using governor ladder [ 1.497721] cpuidle: using governor menu [ 1.497726] No iBFT detected. [ 1.498004] TCP cubic registered [ 1.498117] NET: Registered protocol family 10 [ 1.498806] Mobile IPv6 [ 1.498809] NET: Registered protocol family 17 [ 1.498889] PM: Resume from disk failed. [ 1.498900] registered taskstats version 1 [ 1.500106] rtc_cmos 00:03: setting system clock to 2012-09-03 01:11:14 UTC (1346634674) [ 1.500157] Initalizing network drop monitor service [ 1.500238] Freeing unused kernel memory: 604k freed [ 1.500361] Write protecting the kernel read-only data: 4336k [ 1.531801] udev[83]: starting version 164 [ 1.615512] e1000e: Intel(R) PRO/1000 Network Driver - 1.2.20-k2 [ 1.615516] e1000e: Copyright(c) 1999 - 2011 Intel Corporation. [ 1.615572] xen: registering gsi 16 triggering 0 polarity 1 [ 1.615576] xen_allocate_pirq: returning irq 16 for gsi 16 [ 1.615578] xen: --> irq=16 [ 1.615583] Already setup the GSI :16 [ 1.615586] e1000e 0000:06:00.0: PCI INT A -> GSI 16 (level, low) -> IRQ 16 [ 1.615637] e1000e 0000:06:00.0: setting latency timer to 64 [ 1.615997] alloc irq_desc for 1248 on node -1 [ 1.615999] alloc kstat_irqs on node -1 [ 1.616123] alloc irq_desc for 1247 on node -1 [ 1.616125] alloc kstat_irqs on node -1 [ 1.616245] alloc irq_desc for 1246 on node -1 [ 1.616248] alloc kstat_irqs on node -1 [ 1.616513] e1000e 0000:06:00.0: Disabling ASPM L0s [ 1.648958] usbcore: registered new interface driver usbfs [ 1.648986] usbcore: registered new interface driver hub [ 1.649046] usbcore: registered new device driver usb [ 1.650510] SCSI subsystem initialized [ 1.650847] ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver [ 1.650880] xen: registering gsi 18 triggering 0 polarity 1 [ 1.650884] xen_allocate_pirq: returning irq 18 for gsi 18 [ 1.650886] xen: --> irq=18 [ 1.650891] Already setup the GSI :18 [ 1.650894] ehci_hcd 0000:00:1a.7: PCI INT C -> GSI 18 (level, low) -> IRQ 18 [ 1.650921] ehci_hcd 0000:00:1a.7: setting latency timer to 64 [ 1.650926] ehci_hcd 0000:00:1a.7: EHCI Host Controller [ 1.650954] ehci_hcd 0000:00:1a.7: new USB bus registered, assigned bus number 1 [ 1.651019] ehci_hcd 0000:00:1a.7: debug port 1 [ 1.654896] ehci_hcd 0000:00:1a.7: cache line size of 32 is not supported [ 1.654923] ehci_hcd 0000:00:1a.7: irq 18, io mem 0xfbeda000 [ 1.664014] libata version 3.00 loaded. [ 1.670835] ehci_hcd 0000:00:1a.7: USB 2.0 started, EHCI 1.00 [ 1.670862] usb usb1: New USB device found, idVendor=1d6b, idProduct=0002 [ 1.670865] usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1 [ 1.670868] usb usb1: Product: EHCI Host Controller [ 1.670870] usb usb1: Manufacturer: Linux 2.6.32-5-xen-amd64 ehci_hcd [ 1.670873] usb usb1: SerialNumber: 0000:00:1a.7 [ 1.670950] usb usb1: configuration #1 chosen from 1 choice [ 1.670984] hub 1-0:1.0: USB hub found [ 1.671004] hub 1-0:1.0: 6 ports detected [ 1.671071] ata_piix 0000:00:1f.2: version 2.13 [ 1.671091] xen: registering gsi 19 triggering 0 polarity 1 [ 1.671094] xen_allocate_pirq: returning irq 19 for gsi 19 [ 1.671096] xen: --> irq=19 [ 1.671100] Already setup the GSI :19 [ 1.671103] ata_piix 0000:00:1f.2: PCI INT B -> GSI 19 (level, low) -> IRQ 19 [ 1.671110] ata_piix 0000:00:1f.2: MAP [ P0 P2 P1 P3 ] [ 1.671163] ata_piix 0000:00:1f.2: setting latency timer to 64 [ 1.671256] scsi0 : ata_piix [ 1.671441] scsi1 : ata_piix [ 1.674044] ata1: SATA max UDMA/133 cmd 0xc000 ctl 0xbc00 bmdma 0xb480 irq 19 [ 1.674053] ata2: SATA max UDMA/133 cmd 0xb880 ctl 0xb800 bmdma 0xb488 irq 19 [ 1.674087] xen: registering gsi 23 triggering 0 polarity 1 [ 1.674090] xen_allocate_pirq: returning irq 23 for gsi 23 [ 1.674092] xen: --> irq=23 [ 1.674095] Already setup the GSI :23 [ 1.674098] ehci_hcd 0000:00:1d.7: PCI INT A -> GSI 23 (level, low) -> IRQ 23 [ 1.674123] ehci_hcd 0000:00:1d.7: setting latency timer to 64 [ 1.674128] ehci_hcd 0000:00:1d.7: EHCI Host Controller [ 1.674137] ehci_hcd 0000:00:1d.7: new USB bus registered, assigned bus number 2 [ 1.674192] ehci_hcd 0000:00:1d.7: debug port 1 [ 1.678087] ehci_hcd 0000:00:1d.7: cache line size of 32 is not supported [ 1.678107] ehci_hcd 0000:00:1d.7: irq 23, io mem 0xfbed8000 [ 1.694740] ehci_hcd 0000:00:1d.7: USB 2.0 started, EHCI 1.00 [ 1.694780] usb usb2: New USB device found, idVendor=1d6b, idProduct=0002 [ 1.694784] usb usb2: New USB device strings: Mfr=3, Product=2, SerialNumber=1 [ 1.694787] usb usb2: Product: EHCI Host Controller [ 1.694790] usb usb2: Manufacturer: Linux 2.6.32-5-xen-amd64 ehci_hcd [ 1.694793] usb usb2: SerialNumber: 0000:00:1d.7 [ 1.694862] usb usb2: configuration #1 chosen from 1 choice [ 1.694897] hub 2-0:1.0: USB hub found [ 1.694913] hub 2-0:1.0: 6 ports detected [ 1.695056] xen: registering gsi 19 triggering 0 polarity 1 [ 1.695059] xen_allocate_pirq: returning irq 19 for gsi 19 [ 1.695061] xen: --> irq=19 [ 1.695064] Already setup the GSI :19 [ 1.695067] ata_piix 0000:00:1f.5: PCI INT B -> GSI 19 (level, low) -> IRQ 19 [ 1.695075] ata_piix 0000:00:1f.5: MAP [ P0 -- P1 -- ] [ 1.695122] ata_piix 0000:00:1f.5: setting latency timer to 64 [ 1.695198] scsi2 : ata_piix [ 1.695268] scsi3 : ata_piix [ 1.697425] ata3: SATA max UDMA/133 cmd 0xb000 ctl 0xac00 bmdma 0xa480 irq 19 [ 1.697431] ata4: SATA max UDMA/133 cmd 0xa880 ctl 0xa800 bmdma 0xa488 irq 19 [ 1.734264] e1000e 0000:06:00.0: eth0: (PCI Express:2.5GB/s:Width x1) 00:25:90:08:f8:f4 [ 1.734267] e1000e 0000:06:00.0: eth0: Intel(R) PRO/1000 Network Connection [ 1.734354] e1000e 0000:06:00.0: eth0: MAC: 3, PHY: 8, PBA No: 0101FF-0FF [ 1.734391] xen: registering gsi 17 triggering 0 polarity 1 [ 1.734394] xen_allocate_pirq: returning irq 17 for gsi 17 [ 1.734396] xen: --> irq=17 [ 1.734398] Already setup the GSI :17 [ 1.734401] e1000e 0000:07:00.0: PCI INT A -> GSI 17 (level, low) -> IRQ 17 [ 1.734446] e1000e 0000:07:00.0: setting latency timer to 64 [ 1.734753] alloc irq_desc for 1245 on node -1 [ 1.734756] alloc kstat_irqs on node -1 [ 1.734873] alloc irq_desc for 1244 on node -1 [ 1.734875] alloc kstat_irqs on node -1 [ 1.734985] alloc irq_desc for 1243 on node -1 [ 1.734988] alloc kstat_irqs on node -1 [ 1.735554] e1000e 0000:07:00.0: Disabling ASPM L0s [ 1.752363] uhci_hcd: USB Universal Host Controller Interface driver [ 1.752393] xen: registering gsi 16 triggering 0 polarity 1 [ 1.752396] xen_allocate_pirq: returning irq 16 for gsi 16 [ 1.752398] xen: --> irq=16 [ 1.752401] Already setup the GSI :16 [ 1.752404] uhci_hcd 0000:00:1a.0: PCI INT A -> GSI 16 (level, low) -> IRQ 16 [ 1.752416] uhci_hcd 0000:00:1a.0: setting latency timer to 64 [ 1.752421] uhci_hcd 0000:00:1a.0: UHCI Host Controller [ 1.752431] uhci_hcd 0000:00:1a.0: new USB bus registered, assigned bus number 3 [ 1.752478] uhci_hcd 0000:00:1a.0: irq 16, io base 0x0000cc00 [ 1.752537] usb usb3: New USB device found, idVendor=1d6b, idProduct=0001 [ 1.752540] usb usb3: New USB device strings: Mfr=3, Product=2, SerialNumber=1 [ 1.752543] usb usb3: Product: UHCI Host Controller [ 1.752545] usb usb3: Manufacturer: Linux 2.6.32-5-xen-amd64 uhci_hcd [ 1.752547] usb usb3: SerialNumber: 0000:00:1a.0 [ 1.752608] usb usb3: configuration #1 chosen from 1 choice [ 1.752636] hub 3-0:1.0: USB hub found [ 1.752648] hub 3-0:1.0: 2 ports detected [ 1.752702] xen: registering gsi 21 triggering 0 polarity 1 [ 1.752705] xen_allocate_pirq: returning irq 21 for gsi 21 [ 1.752707] xen: --> irq=21 [ 1.752710] Already setup the GSI :21 [ 1.752712] uhci_hcd 0000:00:1a.1: PCI INT B -> GSI 21 (level, low) -> IRQ 21 [ 1.752724] uhci_hcd 0000:00:1a.1: setting latency timer to 64 [ 1.752729] uhci_hcd 0000:00:1a.1: UHCI Host Controller [ 1.752736] uhci_hcd 0000:00:1a.1: new USB bus registered, assigned bus number 4 [ 1.752780] uhci_hcd 0000:00:1a.1: irq 21, io base 0x0000c880 [ 1.752831] usb usb4: New USB device found, idVendor=1d6b, idProduct=0001 [ 1.752834] usb usb4: New USB device strings: Mfr=3, Product=2, SerialNumber=1 [ 1.752837] usb usb4: Product: UHCI Host Controller [ 1.752839] usb usb4: Manufacturer: Linux 2.6.32-5-xen-amd64 uhci_hcd [ 1.752841] usb usb4: SerialNumber: 0000:00:1a.1 [ 1.752902] usb usb4: configuration #1 chosen from 1 choice [ 1.752929] hub 4-0:1.0: USB hub found [ 1.752941] hub 4-0:1.0: 2 ports detected [ 1.752997] xen: registering gsi 19 triggering 0 polarity 1 [ 1.752999] xen_allocate_pirq: returning irq 19 for gsi 19 [ 1.753001] xen: --> irq=19 [ 1.753004] Already setup the GSI :19 [ 1.753007] uhci_hcd 0000:00:1a.2: PCI INT D -> GSI 19 (level, low) -> IRQ 19 [ 1.753019] uhci_hcd 0000:00:1a.2: setting latency timer to 64 [ 1.753023] uhci_hcd 0000:00:1a.2: UHCI Host Controller [ 1.753031] uhci_hcd 0000:00:1a.2: new USB bus registered, assigned bus number 5 [ 1.753064] uhci_hcd 0000:00:1a.2: irq 19, io base 0x0000c800 [ 1.753114] usb usb5: New USB device found, idVendor=1d6b, idProduct=0001 [ 1.753117] usb usb5: New USB device strings: Mfr=3, Product=2, SerialNumber=1 [ 1.753119] usb usb5: Product: UHCI Host Controller [ 1.753122] usb usb5: Manufacturer: Linux 2.6.32-5-xen-amd64 uhci_hcd [ 1.753124] usb usb5: SerialNumber: 0000:00:1a.2 [ 1.753179] usb usb5: configuration #1 chosen from 1 choice [ 1.753205] hub 5-0:1.0: USB hub found [ 1.753216] hub 5-0:1.0: 2 ports detected [ 1.753271] xen: registering gsi 23 triggering 0 polarity 1 [ 1.753274] xen_allocate_pirq: returning irq 23 for gsi 23 [ 1.753276] xen: --> irq=23 [ 1.753279] Already setup the GSI :23 [ 1.753282] uhci_hcd 0000:00:1d.0: PCI INT A -> GSI 23 (level, low) -> IRQ 23 [ 1.753293] uhci_hcd 0000:00:1d.0: setting latency timer to 64 [ 1.753298] uhci_hcd 0000:00:1d.0: UHCI Host Controller [ 1.753307] uhci_hcd 0000:00:1d.0: new USB bus registered, assigned bus number 6 [ 1.753340] uhci_hcd 0000:00:1d.0: irq 23, io base 0x0000c480 [ 1.753389] usb usb6: New USB device found, idVendor=1d6b, idProduct=0001 [ 1.753392] usb usb6: New USB device strings: Mfr=3, Product=2, SerialNumber=1 [ 1.753395] usb usb6: Product: UHCI Host Controller [ 1.753397] usb usb6: Manufacturer: Linux 2.6.32-5-xen-amd64 uhci_hcd [ 1.753399] usb usb6: SerialNumber: 0000:00:1d.0 [ 1.753452] usb usb6: configuration #1 chosen from 1 choice [ 1.753480] hub 6-0:1.0: USB hub found [ 1.753492] hub 6-0:1.0: 2 ports detected [ 1.753547] xen: registering gsi 19 triggering 0 polarity 1 [ 1.753550] xen_allocate_pirq: returning irq 19 for gsi 19 [ 1.753552] xen: --> irq=19 [ 1.753554] Already setup the GSI :19 [ 1.753557] uhci_hcd 0000:00:1d.1: PCI INT B -> GSI 19 (level, low) -> IRQ 19 [ 1.753568] uhci_hcd 0000:00:1d.1: setting latency timer to 64 [ 1.753573] uhci_hcd 0000:00:1d.1: UHCI Host Controller [ 1.753580] uhci_hcd 0000:00:1d.1: new USB bus registered, assigned bus number 7 [ 1.753613] uhci_hcd 0000:00:1d.1: irq 19, io base 0x0000c400 [ 1.753665] usb usb7: New USB device found, idVendor=1d6b, idProduct=0001 [ 1.753668] usb usb7: New USB device strings: Mfr=3, Product=2, SerialNumber=1 [ 1.753671] usb usb7: Product: UHCI Host Controller [ 1.753673] usb usb7: Manufacturer: Linux 2.6.32-5-xen-amd64 uhci_hcd [ 1.753675] usb usb7: SerialNumber: 0000:00:1d.1 [ 1.753730] usb usb7: configuration #1 chosen from 1 choice [ 1.753756] hub 7-0:1.0: USB hub found [ 1.753768] hub 7-0:1.0: 2 ports detected [ 1.753823] xen: registering gsi 18 triggering 0 polarity 1 [ 1.753825] xen_allocate_pirq: returning irq 18 for gsi 18 [ 1.753827] xen: --> irq=18 [ 1.753830] Already setup the GSI :18 [ 1.753833] uhci_hcd 0000:00:1d.2: PCI INT C -> GSI 18 (level, low) -> IRQ 18 [ 1.753844] uhci_hcd 0000:00:1d.2: setting latency timer to 64 [ 1.753849] uhci_hcd 0000:00:1d.2: UHCI Host Controller [ 1.753856] uhci_hcd 0000:00:1d.2: new USB bus registered, assigned bus number 8 [ 1.753889] uhci_hcd 0000:00:1d.2: irq 18, io base 0x0000c080 [ 1.753938] usb usb8: New USB device found, idVendor=1d6b, idProduct=0001 [ 1.753941] usb usb8: New USB device strings: Mfr=3, Product=2, SerialNumber=1 [ 1.753944] usb usb8: Product: UHCI Host Controller [ 1.753946] usb usb8: Manufacturer: Linux 2.6.32-5-xen-amd64 uhci_hcd [ 1.753948] usb usb8: SerialNumber: 0000:00:1d.2 [ 1.754003] usb usb8: configuration #1 chosen from 1 choice [ 1.754030] hub 8-0:1.0: USB hub found [ 1.754041] hub 8-0:1.0: 2 ports detected [ 1.856060] e1000e 0000:07:00.0: eth1: (PCI Express:2.5GB/s:Width x1) 00:25:90:08:f8:f5 [ 1.856063] e1000e 0000:07:00.0: eth1: Intel(R) PRO/1000 Network Connection [ 1.856149] e1000e 0000:07:00.0: eth1: MAC: 3, PHY: 8, PBA No: 0101FF-0FF [ 2.026118] ata3: SATA link down (SStatus 0 SControl 300) [ 2.037464] ata4: SATA link down (SStatus 0 SControl 300) [ 2.194749] usb 6-2: new low speed USB device using uhci_hcd and address 2 [ 2.322246] ata2.00: SATA link down (SStatus 0 SControl 300) [ 2.322278] ata2.01: SATA link down (SStatus 0 SControl 300) [ 2.383407] usb 6-2: New USB device found, idVendor=0624, idProduct=0294 [ 2.383411] usb 6-2: New USB device strings: Mfr=1, Product=2, SerialNumber=0 [ 2.383414] usb 6-2: Product: Dell 03R874 [ 2.383417] usb 6-2: Manufacturer: Avocent [ 2.383502] usb 6-2: configuration #1 chosen from 1 choice [ 2.466851] ata1.00: SATA link up 3.0 Gbps (SStatus 123 SControl 300) [ 2.466872] ata1.01: SATA link down (SStatus 0 SControl 300) [ 2.475316] ata1.00: ATA-8: ST31000524NS, SN11, max UDMA/133 [ 2.475320] ata1.00: 1953525168 sectors, multi 16: LBA48 NCQ (depth 0/32) [ 2.491336] ata1.00: configured for UDMA/133 [ 2.491456] scsi 0:0:0:0: Direct-Access ATA ST31000524NS SN11 PQ: 0 ANSI: 5 [ 2.494928] usbcore: registered new interface driver hiddev [ 2.498808] sd 0:0:0:0: [sda] 1953525168 512-byte logical blocks: (1.00 TB/931 GiB) [ 2.498883] sd 0:0:0:0: [sda] Write Protect is off [ 2.498886] sd 0:0:0:0: [sda] Mode Sense: 00 3a 00 00 [ 2.498917] sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA [ 2.499181] sda: [ 2.508634] input: Avocent Dell 03R874 as /devices/pci0000:00/0000:00:1d.0/usb6/6-2/6-2:1.0/input/input1 [ 2.508681] generic-usb 0003:0624:0294.0001: input,hidraw0: USB HID v1.10 Keyboard [Avocent Dell 03R874] on usb-0000:00:1d.0-2/input0 [ 2.516368] sda1 sda2 < sda5 [ 2.531678] input: Avocent Dell 03R874 as /devices/pci0000:00/0000:00:1d.0/usb6/6-2/6-2:1.1/input/input2 [ 2.531739] generic-usb 0003:0624:0294.0002: input,hidraw1: USB HID v1.10 Mouse [Avocent Dell 03R874] on usb-0000:00:1d.0-2/input1 [ 2.531759] usbcore: registered new interface driver usbhid [ 2.531762] usbhid: v2.6:USB HID core driver [ 2.534295] sda6 sda7 sda8 > [ 2.555825] sd 0:0:0:0: [sda] Attached SCSI disk [ 2.899763] device-mapper: uevent: version 1.0.3 [ 2.899895] device-mapper: ioctl: 4.15.0-ioctl (2009-04-01) initialised: dm-devel@redhat.com [ 2.909503] PM: Starting manual resume from disk [ 2.909506] PM: Resume from partition 8:5 [ 2.909508] PM: Checking hibernation image. [ 2.909833] PM: Error -22 checking image file [ 2.909836] PM: Resume from disk failed. [ 2.924059] EXT3-fs: INFO: recovery required on readonly filesystem. [ 2.924062] EXT3-fs: write access will be enabled during recovery. [ 2.946363] kjournald starting. Commit interval 5 seconds [ 2.946373] EXT3-fs: recovery complete. [ 2.946668] EXT3-fs: mounted filesystem with ordered data mode. [ 3.754433] udev[499]: starting version 164 [ 3.945625] dca service started, version 1.12.1 [ 4.001259] ioatdma: Intel(R) QuickData Technology Driver 4.00 [ 4.001323] xen: registering gsi 43 triggering 0 polarity 1 [ 4.001332] alloc irq_desc for 43 on node -1 [ 4.001334] alloc kstat_irqs on node -1 [ 4.001340] xen: --> irq=43 [ 4.001349] ioatdma 0000:00:16.0: PCI INT A -> GSI 43 (level, low) -> IRQ 43 [ 4.001381] ioatdma 0000:00:16.0: setting latency timer to 64 [ 4.001471] alloc irq_desc for 1242 on node -1 [ 4.001473] alloc kstat_irqs on node -1 [ 4.001854] xen: registering gsi 44 triggering 0 polarity 1 [ 4.001860] alloc irq_desc for 44 on node -1 [ 4.001862] alloc kstat_irqs on node -1 [ 4.001866] xen: --> irq=44 [ 4.001873] ioatdma 0000:00:16.1: PCI INT B -> GSI 44 (level, low) -> IRQ 44 [ 4.001895] ioatdma 0000:00:16.1: setting latency timer to 64 [ 4.001973] alloc irq_desc for 1241 on node -1 [ 4.001975] alloc kstat_irqs on node -1 [ 4.002654] xen: registering gsi 45 triggering 0 polarity 1 [ 4.002660] alloc irq_desc for 45 on node -1 [ 4.002663] alloc kstat_irqs on node -1 [ 4.002666] xen: --> irq=45 [ 4.002673] ioatdma 0000:00:16.2: PCI INT C -> GSI 45 (level, low) -> IRQ 45 [ 4.002697] ioatdma 0000:00:16.2: setting latency timer to 64 [ 4.002780] alloc irq_desc for 1240 on node -1 [ 4.002783] alloc kstat_irqs on node -1 [ 4.003358] xen: registering gsi 46 triggering 0 polarity 1 [ 4.003366] alloc irq_desc for 46 on node -1 [ 4.003369] alloc kstat_irqs on node -1 [ 4.003374] xen: --> irq=46 [ 4.003382] ioatdma 0000:00:16.3: PCI INT D -> GSI 46 (level, low) -> IRQ 46 [ 4.003411] ioatdma 0000:00:16.3: setting latency timer to 64 [ 4.003503] alloc irq_desc for 1239 on node -1 [ 4.003505] alloc kstat_irqs on node -1 [ 4.007654] input: Power Button as /devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0C:00/input/input3 [ 4.007660] ACPI: Power Button [PWRB] [ 4.007712] input: Power Button as /devices/LNXSYSTM:00/LNXPWRBN:00/input/input4 [ 4.007716] ACPI: Power Button [PWRF] [ 4.008167] xen: registering gsi 43 triggering 0 polarity 1 [ 4.008170] xen_allocate_pirq: returning irq 43 for gsi 43 [ 4.008173] xen: --> irq=43 [ 4.008177] Already setup the GSI :43 [ 4.008180] ioatdma 0000:00:16.4: PCI INT A -> GSI 43 (level, low) -> IRQ 43 [ 4.008213] ioatdma 0000:00:16.4: setting latency timer to 64 [ 4.008304] alloc irq_desc for 1238 on node -1 [ 4.008306] alloc kstat_irqs on node -1 [ 4.008678] xen: registering gsi 44 triggering 0 polarity 1 [ 4.008682] xen_allocate_pirq: returning irq 44 for gsi 44 [ 4.008684] xen: --> irq=44 [ 4.008687] Already setup the GSI :44 [ 4.008690] ioatdma 0000:00:16.5: PCI INT B -> GSI 44 (level, low) -> IRQ 44 [ 4.008717] ioatdma 0000:00:16.5: setting latency timer to 64 [ 4.008797] alloc irq_desc for 1237 on node -1 [ 4.008800] alloc kstat_irqs on node -1 [ 4.009157] xen: registering gsi 45 triggering 0 polarity 1 [ 4.009162] xen_allocate_pirq: returning irq 45 for gsi 45 [ 4.009164] xen: --> irq=45 [ 4.009167] Already setup the GSI :45 [ 4.009170] ioatdma 0000:00:16.6: PCI INT C -> GSI 45 (level, low) -> IRQ 45 [ 4.009198] ioatdma 0000:00:16.6: setting latency timer to 64 [ 4.009289] alloc irq_desc for 1236 on node -1 [ 4.009293] alloc kstat_irqs on node -1 [ 4.009669] xen: registering gsi 46 triggering 0 polarity 1 [ 4.009672] xen_allocate_pirq: returning irq 46 for gsi 46 [ 4.009674] xen: --> irq=46 [ 4.009677] Already setup the GSI :46 [ 4.009680] ioatdma 0000:00:16.7: PCI INT D -> GSI 46 (level, low) -> IRQ 46 [ 4.009706] ioatdma 0000:00:16.7: setting latency timer to 64 [ 4.009789] alloc irq_desc for 1235 on node -1 [ 4.009791] alloc kstat_irqs on node -1 [ 4.122331] ACPI: SSDT 00000000bf79e0c0 008F0 (v01 DpgPmm P001Ist 00000011 INTL 20051117) [ 4.123073] ACPI: SSDT 00000000bf79e9b0 004D5 (v01 PmRef P001Cst 00003001 INTL 20051117) [ 4.126163] ACPI: CPU-1 (power states: C1[C1] C2[C3] C3[C3]) [ 4.127906] ACPI: CPU-1 (power states: C1[C1] C2[C3] C3[C3]) [ 4.128785] ACPI: CPU-1 (power states: C1[C1] C2[C3] C3[C3]) [ 4.130779] ACPI: CPU-1 (power states: C1[C1] C2[C3] C3[C3]) [ 4.137541] input: PC Speaker as /devices/platform/pcspkr/input/input5 [ 7.296701] xen: registering gsi 18 triggering 0 polarity 1 [ 7.296706] xen_allocate_pirq: returning irq 18 for gsi 18 [ 7.296709] xen: --> irq=18 [ 7.296714] Already setup the GSI :18 [ 7.296718] i801_smbus 0000:00:1f.3: PCI INT C -> GSI 18 (level, low) -> IRQ 18 [ 31.570836] Error: Driver 'pcspkr' is already registered, aborting... [ 31.635627] xen: registering gsi 22 triggering 0 polarity 1 [ 31.635637] alloc irq_desc for 22 on node -1 [ 31.635641] alloc kstat_irqs on node -1 [ 31.635647] xen: --> irq=22 [ 31.635657] HDA Intel 0000:00:1b.0: PCI INT A -> GSI 22 (level, low) -> IRQ 22 [ 31.635725] HDA Intel 0000:00:1b.0: setting latency timer to 64 [ 31.926667] hda-intel: no codecs found! [ 31.926920] HDA Intel 0000:00:1b.0: PCI INT A disabled [ 186.671977] Adding 7811064k swap on /dev/sda5. Priority:-1 extents:1 across:7811064k [ 187.701870] EXT3 FS on sda7, internal journal [ 190.439342] loop: module loaded [ 202.731165] kjournald starting. Commit interval 5 seconds [ 202.731449] EXT3 FS on sda1, internal journal [ 202.731457] EXT3-fs: mounted filesystem with ordered data mode. [ 202.739591] kjournald starting. Commit interval 5 seconds [ 202.739903] EXT3 FS on sda6, internal journal [ 202.739910] EXT3-fs: mounted filesystem with ordered data mode. [ 285.391611] ADDRCONF(NETDEV_UP): eth0: link is not ready [ 285.395769] e1000e: eth0 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: Rx/Tx [ 285.396222] ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready [ 296.174595] Event-channel device installed. [ 297.320190] alloc irq_desc for 1234 on node -1 [ 297.320194] alloc kstat_irqs on node -1 [ 297.320355] alloc irq_desc for 1233 on node -1 [ 297.320358] alloc kstat_irqs on node -1 [ 297.322088] XENBUS: Unable to read cpu state [ 297.322298] XENBUS: Unable to read cpu state [ 297.322490] XENBUS: Unable to read cpu state [ 297.323213] XENBUS: Unable to read cpu state [ 300.308073] Bridge firewalling registered [ 301.180816] eth0: no IPv6 routers present [ 442.059305] ADDRCONF(NETDEV_UP): peth0: link is not ready [ 445.180920] e1000e: peth0 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: Rx/Tx [ 445.181356] ADDRCONF(NETDEV_CHANGE): peth0: link becomes ready [ 445.185609] device peth0 entered promiscuous mode [ 445.200468] eth0: port 1(peth0) entering forwarding state [ 451.395728] ip_tables: (C) 2000-2006 Netfilter Core Team [ 458.353997] peth0: no IPv6 routers present [ 458.354001] eth0: no IPv6 routers present --------------000002040006090604060406 Content-Type: text/plain; name="xm-dmesg" Content-Transfer-Encoding: 7bit Content-Disposition: attachment; filename="xm-dmesg" (XEN) Xen version 4.0.1 (Debian 4.0.1-5.3) (ultrotter@debian.org) (gcc version 4.4.5 (Debian 4.4.5-8) ) Tue Aug 14 14:54:17 UTC 2012 (XEN) Bootloader: GRUB 1.98+20100804-14+squeeze1 (XEN) Command line: placeholder dom0_mem=1536M (XEN) Video information: (XEN) VGA is text mode 80x25, font 8x16 (XEN) VBE/DDC methods: V2; EDID transfer time: 1 seconds (XEN) Disc information: (XEN) Found 1 MBR signatures (XEN) Found 1 EDD information structures (XEN) Xen-e820 RAM map: (XEN) 0000000000000000 - 000000000009dc00 (usable) (XEN) 000000000009dc00 - 00000000000a0000 (reserved) (XEN) 00000000000e4000 - 0000000000100000 (reserved) (XEN) 0000000000100000 - 00000000bf790000 (usable) (XEN) 00000000bf790000 - 00000000bf79e000 (ACPI data) (XEN) 00000000bf79e000 - 00000000bf7d0000 (ACPI NVS) (XEN) 00000000bf7d0000 - 00000000bf7e0000 (reserved) (XEN) 00000000bf7ec000 - 00000000c0000000 (reserved) (XEN) 00000000e0000000 - 00000000f0000000 (reserved) (XEN) 00000000fee00000 - 00000000fee01000 (reserved) (XEN) 00000000ffc00000 - 0000000100000000 (reserved) (XEN) 0000000100000000 - 0000000140000000 (usable) (XEN) ACPI: RSDP 000FAC10, 0024 (r2 ACPIAM) (XEN) ACPI: XSDT BF790100, 005C (r1 SMCI 20100528 MSFT 97) (XEN) ACPI: FACP BF790290, 00F4 (r3 052810 FACP1443 20100528 MSFT 97) (XEN) ACPI: DSDT BF7906A0, 650A (r1 10006 10006000 0 INTL 20051117) (XEN) ACPI: FACS BF79E000, 0040 (XEN) ACPI: APIC BF790390, 011E (r1 052810 APIC1443 20100528 MSFT 97) (XEN) ACPI: MCFG BF7904B0, 003C (r1 052810 OEMMCFG 20100528 MSFT 97) (XEN) ACPI: SLIT BF7904F0, 0030 (r1 052810 OEMSLIT 20100528 MSFT 97) (XEN) ACPI: OEMB BF79E040, 007D (r1 052810 OEMB1443 20100528 MSFT 97) (XEN) ACPI: HPET BF79A6A0, 0038 (r1 052810 OEMHPET 20100528 MSFT 97) (XEN) ACPI: SSDT BF79EE90, 0363 (r1 DpgPmm CpuPm 12 INTL 20051117) (XEN) System RAM: 4087MB (4185268kB) (XEN) Domain heap initialised (XEN) Processor #0 7:10 APIC version 21 (XEN) Processor #2 7:10 APIC version 21 (XEN) Processor #4 7:10 APIC version 21 (XEN) Processor #6 7:10 APIC version 21 (XEN) IOAPIC[0]: apic_id 1, version 32, address 0xfec00000, GSI 0-23 (XEN) IOAPIC[1]: apic_id 3, version 32, address 0xfec8a000, GSI 24-47 (XEN) Enabling APIC mode: Flat. Using 2 I/O APICs (XEN) Using scheduler: SMP Credit Scheduler (credit) (XEN) Detected 2133.454 MHz processor. (XEN) Initing memory sharing. (XEN) VMX: Supported advanced features: (XEN) - APIC MMIO access virtualisation (XEN) - APIC TPR shadow (XEN) - Extended Page Tables (EPT) (XEN) - Virtual-Processor Identifiers (VPID) (XEN) - Virtual NMI (XEN) - MSR direct-access bitmap (XEN) EPT supports 2MB super page. (XEN) HVM: ASIDs enabled. (XEN) HVM: VMX enabled (XEN) HVM: Hardware Assisted Paging detected. (XEN) I/O virtualisation disabled (XEN) Total of 4 processors activated. (XEN) ENABLING IO-APIC IRQs (XEN) -> Using new ACK method (XEN) TSC is reliable, synchronization unnecessary (XEN) Platform timer appears to have unexpectedly wrapped 10 or more times. (XEN) Platform timer is 14.318MHz HPET (XEN) Allocated console ring of 16 KiB. (XEN) Brought up 4 CPUs (XEN) *** LOADING DOMAIN 0 *** (XEN) Xen kernel: 64-bit, lsb, compat32 (XEN) Dom0 kernel: 64-bit, PAE, lsb, paddr 0x1000000 -> 0x1708000 (XEN) PHYSICAL MEMORY ARRANGEMENT: (XEN) Dom0 alloc.: 0000000138000000->000000013c000000 (376832 pages to be allocated) (XEN) VIRTUAL MEMORY ARRANGEMENT: (XEN) Loaded kernel: ffffffff81000000->ffffffff81708000 (XEN) Init. ramdisk: ffffffff81708000->ffffffff8332a000 (XEN) Phys-Mach map: ffffffff8332a000->ffffffff8362a000 (XEN) Start info: ffffffff8362a000->ffffffff8362a4b4 (XEN) Page tables: ffffffff8362b000->ffffffff8364a000 (XEN) Boot stack: ffffffff8364a000->ffffffff8364b000 (XEN) TOTAL: ffffffff80000000->ffffffff83800000 (XEN) ENTRY ADDRESS: ffffffff81531200 (XEN) Dom0 has maximum 4 VCPUs (XEN) Scrubbing Free RAM: .........................done. (XEN) Xen trace buffers: disabled (XEN) Std. Loglevel: Errors and warnings (XEN) Guest Loglevel: Nothing (Rate-limited: Errors and warnings) (XEN) Xen is relinquishing VGA console. (XEN) *** Serial input -> DOM0 (type 'CTRL-a' three times to switch input to Xen) (XEN) Freed 176kB init memory. --------------000002040006090604060406 Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users --------------000002040006090604060406-- From xen-users-bounces@lists.xen.org Tue Sep 04 02:03:35 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Tue, 04 Sep 2012 02:03:35 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1T8iT0-0005rr-1j; Tue, 04 Sep 2012 02:02:14 +0000 Received: from mail27.messagelabs.com ([193.109.254.147]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1T8iSx-0005rj-Hq for xen-users@lists.xen.org; Tue, 04 Sep 2012 02:02:11 +0000 X-Env-Sender: raju@linux-delhi.org X-Msg-Ref: server-13.tower-27.messagelabs.com!1346724109!9311501!1 X-Originating-IP: [83.143.86.98] X-SpamReason: No, hits=0.0 required=7.0 tests=ML_RADAR_SPEW_LINKS_8, spamassassin: , async_handler: YXN5bmNfZGVsYXk6IDcwNTg2NTIgKHRpbWVvdXQp\n X-StarScan-Received: X-StarScan-Version: 6.6.1.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 5005 invoked from network); 4 Sep 2012 02:01:49 -0000 Received: from etc.kandalaya.org (HELO images.kandalaya.org) (83.143.86.98) by server-13.tower-27.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 4 Sep 2012 02:01:49 -0000 Received: from mail.linux-delhi.org ([115.241.240.117]) by images.kandalaya.org (8.14.3/8.14.3/Debian-9) with ESMTP id q84214hQ003955 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK) for ; Tue, 4 Sep 2012 07:31:16 +0530 Received: from mail.linux-delhi.org (raju@localhost [127.0.0.1]) by mail.linux-delhi.org (8.14.4/8.14.4/Debian-2.1) with ESMTP id q8420i2H013575 for ; Tue, 4 Sep 2012 07:30:48 +0530 From: "Raj Mathur (=?utf-8?b?4KSw4KS+4KSc?= =?utf-8?b?IOCkruCkvuCkpeClgeCksA==?=)" Organization: Kandalaya To: xen-users@lists.xen.org Date: Tue, 4 Sep 2012 07:30:43 +0530 User-Agent: KMail/1.13.7 (Linux/3.2.233-rt37; KDE/4.8.4; i686; ; ) References: <50454D6B.5090800@gmail.com> In-Reply-To: <50454D6B.5090800@gmail.com> MIME-Version: 1.0 Message-Id: <201209040730.43878.raju@linux-delhi.org> X-Spam-Status: No, score=-10.8 required=5.0 tests=AWL,BAYES_00, DNS_FROM_RFC_BOGUSMX, LOCAL_FROM_RAJU, RCVD_IN_PBL, RDNS_NONE autolearn=ham version=3.2.5 X-Spam-Checker-Version: SpamAssassin 3.2.5 (2008-06-10) on images.kandalaya.org X-Virus-Scanned: clamav-milter 0.95.2 at images.kandalaya.org X-Virus-Status: Clean Subject: Re: [Xen-users] Severe dom0 performance issues after installing Xen X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list Reply-To: raju@linux-delhi.org List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org On Tuesday 04 Sep 2012, Keith Buck wrote: > I'm experiencing some severe performance issues running Xen 4.0.1 > with a cleanly-installed Debian 6 dom0. Prior to installation, the > machine's performance was fine, but after installation booting takes > anywhere from 5 to 20 times longer, processes take a long time to > start, and SSH lags. No domUs are running (or have been created > yet). I can switch back to running without Xen (but still using the > Xen-compatible kernel) and the performance problems disappear. Probably a stupid question, but sometime we miss the obvious: did you make any networking changes? Specifically, could this problem be due to not being able to reverse resolve IP addresses on your machine? Regards, -- Raj -- Raj Mathur || raju@kandalaya.org || GPG: http://otheronepercent.blogspot.com || http://kandalaya.org || CC68 It is the mind that moves || http://schizoid.in || D17F _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Tue Sep 04 02:03:35 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Tue, 04 Sep 2012 02:03:35 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1T8iT0-0005rr-1j; Tue, 04 Sep 2012 02:02:14 +0000 Received: from mail27.messagelabs.com ([193.109.254.147]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1T8iSx-0005rj-Hq for xen-users@lists.xen.org; Tue, 04 Sep 2012 02:02:11 +0000 X-Env-Sender: raju@linux-delhi.org X-Msg-Ref: server-13.tower-27.messagelabs.com!1346724109!9311501!1 X-Originating-IP: [83.143.86.98] X-SpamReason: No, hits=0.0 required=7.0 tests=ML_RADAR_SPEW_LINKS_8, spamassassin: , async_handler: YXN5bmNfZGVsYXk6IDcwNTg2NTIgKHRpbWVvdXQp\n X-StarScan-Received: X-StarScan-Version: 6.6.1.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 5005 invoked from network); 4 Sep 2012 02:01:49 -0000 Received: from etc.kandalaya.org (HELO images.kandalaya.org) (83.143.86.98) by server-13.tower-27.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 4 Sep 2012 02:01:49 -0000 Received: from mail.linux-delhi.org ([115.241.240.117]) by images.kandalaya.org (8.14.3/8.14.3/Debian-9) with ESMTP id q84214hQ003955 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK) for ; Tue, 4 Sep 2012 07:31:16 +0530 Received: from mail.linux-delhi.org (raju@localhost [127.0.0.1]) by mail.linux-delhi.org (8.14.4/8.14.4/Debian-2.1) with ESMTP id q8420i2H013575 for ; Tue, 4 Sep 2012 07:30:48 +0530 From: "Raj Mathur (=?utf-8?b?4KSw4KS+4KSc?= =?utf-8?b?IOCkruCkvuCkpeClgeCksA==?=)" Organization: Kandalaya To: xen-users@lists.xen.org Date: Tue, 4 Sep 2012 07:30:43 +0530 User-Agent: KMail/1.13.7 (Linux/3.2.233-rt37; KDE/4.8.4; i686; ; ) References: <50454D6B.5090800@gmail.com> In-Reply-To: <50454D6B.5090800@gmail.com> MIME-Version: 1.0 Message-Id: <201209040730.43878.raju@linux-delhi.org> X-Spam-Status: No, score=-10.8 required=5.0 tests=AWL,BAYES_00, DNS_FROM_RFC_BOGUSMX, LOCAL_FROM_RAJU, RCVD_IN_PBL, RDNS_NONE autolearn=ham version=3.2.5 X-Spam-Checker-Version: SpamAssassin 3.2.5 (2008-06-10) on images.kandalaya.org X-Virus-Scanned: clamav-milter 0.95.2 at images.kandalaya.org X-Virus-Status: Clean Subject: Re: [Xen-users] Severe dom0 performance issues after installing Xen X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list Reply-To: raju@linux-delhi.org List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org On Tuesday 04 Sep 2012, Keith Buck wrote: > I'm experiencing some severe performance issues running Xen 4.0.1 > with a cleanly-installed Debian 6 dom0. Prior to installation, the > machine's performance was fine, but after installation booting takes > anywhere from 5 to 20 times longer, processes take a long time to > start, and SSH lags. No domUs are running (or have been created > yet). I can switch back to running without Xen (but still using the > Xen-compatible kernel) and the performance problems disappear. Probably a stupid question, but sometime we miss the obvious: did you make any networking changes? Specifically, could this problem be due to not being able to reverse resolve IP addresses on your machine? Regards, -- Raj -- Raj Mathur || raju@kandalaya.org || GPG: http://otheronepercent.blogspot.com || http://kandalaya.org || CC68 It is the mind that moves || http://schizoid.in || D17F _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Tue Sep 04 02:17:33 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Tue, 04 Sep 2012 02:17:33 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1T8igd-0006Pv-Nv; Tue, 04 Sep 2012 02:16:19 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1T8igb-0006Ph-Tg for xen-users@lists.xen.org; Tue, 04 Sep 2012 02:16:18 +0000 Received: from [85.158.143.99:23658] by server-2.bemta-4.messagelabs.com id 02/52-21239-17465405; Tue, 04 Sep 2012 02:16:17 +0000 X-Env-Sender: buck.alex@gmail.com X-Msg-Ref: server-9.tower-216.messagelabs.com!1346724975!28355829!1 X-Originating-IP: [209.85.212.45] X-SpamReason: No, hits=1.2 required=7.0 tests=HTML_20_30,HTML_MESSAGE, ML_RADAR_SPEW_LINKS_14,RCVD_BY_IP,spamassassin: X-StarScan-Received: X-StarScan-Version: 6.6.1.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 26971 invoked from network); 4 Sep 2012 02:16:16 -0000 Received: from mail-vb0-f45.google.com (HELO mail-vb0-f45.google.com) (209.85.212.45) by server-9.tower-216.messagelabs.com with RC4-SHA encrypted SMTP; 4 Sep 2012 02:16:16 -0000 Received: by vbip1 with SMTP id p1so7518876vbi.32 for ; Mon, 03 Sep 2012 19:16:15 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=dOs5A0Ffr6KIZ9XMSwiI9kI2kGwLWocLmvO8YPFXWNQ=; b=PUaGtCXqXWLJlqBue6wDj1Oh2jtMUNiZu2NOboY6HnjwJo0c1ugOhhT99Big0gOBdX ERnu9+YoYbyWEOQdJDu76besi/Y3g5vnXSSWd5w0VeNIgtRkjcBr5HhE+qgizbQD0Dzi 9sMcawTtK4uxXqp34XWcLiUmN51m8nXeABH1VNLwfKXTscObTtrQVbHHtgiJNZ7lbO/E ftge6IsXlhTcdoQ5M79HDxbAQkqZR7OtWF6eUYMWyULM+SXDF9C93/aggr7mcRxvFjUd TizCTuzWUkn8HkIa1UhrrpIeTUjmmTh8KRZvW0C5YKfBvcZOlARfleRWmJcvM6oZta0/ 0YTA== MIME-Version: 1.0 Received: by 10.220.221.18 with SMTP id ia18mr13692989vcb.62.1346724974973; Mon, 03 Sep 2012 19:16:14 -0700 (PDT) Received: by 10.58.91.7 with HTTP; Mon, 3 Sep 2012 19:16:14 -0700 (PDT) In-Reply-To: <201209040730.43878.raju@linux-delhi.org> References: <50454D6B.5090800@gmail.com> <201209040730.43878.raju@linux-delhi.org> Date: Mon, 3 Sep 2012 19:16:14 -0700 Message-ID: From: Keith Buck To: raju@linux-delhi.org Cc: xen-users@lists.xen.org Subject: Re: [Xen-users] Severe dom0 performance issues after installing Xen X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============2329545676643952155==" Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org --===============2329545676643952155== Content-Type: multipart/alternative; boundary=14dae9cfc700be539704c8d6d71b --14dae9cfc700be539704c8d6d71b Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable On Mon, Sep 3, 2012 at 7:00 PM, Raj Mathur (=E0=A4=B0=E0=A4=BE=E0=A4=9C =E0= =A4=AE=E0=A4=BE=E0=A4=A5=E0=A5=81=E0=A4=B0) wrote: > On Tuesday 04 Sep 2012, Keith Buck wrote: > > I'm experiencing some severe performance issues running Xen 4.0.1 > > with a cleanly-installed Debian 6 dom0. Prior to installation, the > > machine's performance was fine, but after installation booting takes > > anywhere from 5 to 20 times longer, processes take a long time to > > start, and SSH lags. No domUs are running (or have been created > > yet). I can switch back to running without Xen (but still using the > > Xen-compatible kernel) and the performance problems disappear. > > Probably a stupid question, but sometime we miss the obvious: did you > make any networking changes? Specifically, could this problem be due to > not being able to reverse resolve IP addresses on your machine? > > I haven't made any networking changes. The SSH latency isn't just loggin= g in, there's also latency echoing back what I type at the prompt and displaying the output of programs. --14dae9cfc700be539704c8d6d71b Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
On Mon, Sep 3, 2012 at 7:00 PM, Raj Mathur (=E0= =A4=B0=E0=A4=BE=E0=A4=9C =E0=A4=AE=E0=A4=BE=E0=A4=A5=E0=A5=81=E0=A4=B0) <raju@linux-delhi.org> wrote:
On Tuesday 04 Sep 2012, Keith Buck wrote:
> I'm experiencing some severe performance issues running Xen 4.0.1<= br> > with a cleanly-installed Debian 6 dom0. =C2=A0Prior to installation, t= he
> machine's performance was fine, but after installation booting tak= es
> anywhere from 5 to 20 times longer, processes take a long time to
> start, and SSH lags. =C2=A0No domUs are running (or have been created<= br> > yet). =C2=A0I can switch back to running without Xen (but still using = the
> Xen-compatible kernel) and the performance problems disappear.

Probably a stupid question, but sometime we miss the obvious: did you=
make any networking changes? =C2=A0Specifically, could this problem be due = to
not being able to reverse resolve IP addresses on your machine?

I haven't made any networking changes.=C2=A0 The = SSH latency isn't just=20 logging in, there's also latency echoing back what I type at the prompt= =20 and displaying the output of programs.
--14dae9cfc700be539704c8d6d71b-- --===============2329545676643952155== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users --===============2329545676643952155==-- From xen-users-bounces@lists.xen.org Tue Sep 04 02:17:33 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Tue, 04 Sep 2012 02:17:33 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1T8igd-0006Pv-Nv; Tue, 04 Sep 2012 02:16:19 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1T8igb-0006Ph-Tg for xen-users@lists.xen.org; Tue, 04 Sep 2012 02:16:18 +0000 Received: from [85.158.143.99:23658] by server-2.bemta-4.messagelabs.com id 02/52-21239-17465405; Tue, 04 Sep 2012 02:16:17 +0000 X-Env-Sender: buck.alex@gmail.com X-Msg-Ref: server-9.tower-216.messagelabs.com!1346724975!28355829!1 X-Originating-IP: [209.85.212.45] X-SpamReason: No, hits=1.2 required=7.0 tests=HTML_20_30,HTML_MESSAGE, ML_RADAR_SPEW_LINKS_14,RCVD_BY_IP,spamassassin: X-StarScan-Received: X-StarScan-Version: 6.6.1.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 26971 invoked from network); 4 Sep 2012 02:16:16 -0000 Received: from mail-vb0-f45.google.com (HELO mail-vb0-f45.google.com) (209.85.212.45) by server-9.tower-216.messagelabs.com with RC4-SHA encrypted SMTP; 4 Sep 2012 02:16:16 -0000 Received: by vbip1 with SMTP id p1so7518876vbi.32 for ; Mon, 03 Sep 2012 19:16:15 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=dOs5A0Ffr6KIZ9XMSwiI9kI2kGwLWocLmvO8YPFXWNQ=; b=PUaGtCXqXWLJlqBue6wDj1Oh2jtMUNiZu2NOboY6HnjwJo0c1ugOhhT99Big0gOBdX ERnu9+YoYbyWEOQdJDu76besi/Y3g5vnXSSWd5w0VeNIgtRkjcBr5HhE+qgizbQD0Dzi 9sMcawTtK4uxXqp34XWcLiUmN51m8nXeABH1VNLwfKXTscObTtrQVbHHtgiJNZ7lbO/E ftge6IsXlhTcdoQ5M79HDxbAQkqZR7OtWF6eUYMWyULM+SXDF9C93/aggr7mcRxvFjUd TizCTuzWUkn8HkIa1UhrrpIeTUjmmTh8KRZvW0C5YKfBvcZOlARfleRWmJcvM6oZta0/ 0YTA== MIME-Version: 1.0 Received: by 10.220.221.18 with SMTP id ia18mr13692989vcb.62.1346724974973; Mon, 03 Sep 2012 19:16:14 -0700 (PDT) Received: by 10.58.91.7 with HTTP; Mon, 3 Sep 2012 19:16:14 -0700 (PDT) In-Reply-To: <201209040730.43878.raju@linux-delhi.org> References: <50454D6B.5090800@gmail.com> <201209040730.43878.raju@linux-delhi.org> Date: Mon, 3 Sep 2012 19:16:14 -0700 Message-ID: From: Keith Buck To: raju@linux-delhi.org Cc: xen-users@lists.xen.org Subject: Re: [Xen-users] Severe dom0 performance issues after installing Xen X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============2329545676643952155==" Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org --===============2329545676643952155== Content-Type: multipart/alternative; boundary=14dae9cfc700be539704c8d6d71b --14dae9cfc700be539704c8d6d71b Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable On Mon, Sep 3, 2012 at 7:00 PM, Raj Mathur (=E0=A4=B0=E0=A4=BE=E0=A4=9C =E0= =A4=AE=E0=A4=BE=E0=A4=A5=E0=A5=81=E0=A4=B0) wrote: > On Tuesday 04 Sep 2012, Keith Buck wrote: > > I'm experiencing some severe performance issues running Xen 4.0.1 > > with a cleanly-installed Debian 6 dom0. Prior to installation, the > > machine's performance was fine, but after installation booting takes > > anywhere from 5 to 20 times longer, processes take a long time to > > start, and SSH lags. No domUs are running (or have been created > > yet). I can switch back to running without Xen (but still using the > > Xen-compatible kernel) and the performance problems disappear. > > Probably a stupid question, but sometime we miss the obvious: did you > make any networking changes? Specifically, could this problem be due to > not being able to reverse resolve IP addresses on your machine? > > I haven't made any networking changes. The SSH latency isn't just loggin= g in, there's also latency echoing back what I type at the prompt and displaying the output of programs. --14dae9cfc700be539704c8d6d71b Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
On Mon, Sep 3, 2012 at 7:00 PM, Raj Mathur (=E0= =A4=B0=E0=A4=BE=E0=A4=9C =E0=A4=AE=E0=A4=BE=E0=A4=A5=E0=A5=81=E0=A4=B0) <raju@linux-delhi.org> wrote:
On Tuesday 04 Sep 2012, Keith Buck wrote:
> I'm experiencing some severe performance issues running Xen 4.0.1<= br> > with a cleanly-installed Debian 6 dom0. =C2=A0Prior to installation, t= he
> machine's performance was fine, but after installation booting tak= es
> anywhere from 5 to 20 times longer, processes take a long time to
> start, and SSH lags. =C2=A0No domUs are running (or have been created<= br> > yet). =C2=A0I can switch back to running without Xen (but still using = the
> Xen-compatible kernel) and the performance problems disappear.

Probably a stupid question, but sometime we miss the obvious: did you=
make any networking changes? =C2=A0Specifically, could this problem be due = to
not being able to reverse resolve IP addresses on your machine?

I haven't made any networking changes.=C2=A0 The = SSH latency isn't just=20 logging in, there's also latency echoing back what I type at the prompt= =20 and displaying the output of programs.
--14dae9cfc700be539704c8d6d71b-- --===============2329545676643952155== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users --===============2329545676643952155==-- From xen-users-bounces@lists.xen.org Tue Sep 04 04:40:00 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Tue, 04 Sep 2012 04:40:00 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1T8kuV-0007JT-IH; Tue, 04 Sep 2012 04:38:47 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1T8kuU-0007JO-2Y for xen-users@lists.xen.org; Tue, 04 Sep 2012 04:38:46 +0000 Received: from [85.158.143.99:42915] by server-1.bemta-4.messagelabs.com id 53/E1-12504-5D585405; Tue, 04 Sep 2012 04:38:45 +0000 X-Env-Sender: maheen_butt26@yahoo.com X-Msg-Ref: server-10.tower-216.messagelabs.com!1346733524!21960463!1 X-Originating-IP: [98.138.91.22] X-SpamReason: No, hits=0.7 required=7.0 tests=FROM_HAS_ULINE_NUMS, ML_RADAR_SPEW_LINKS_12,ML_RADAR_SPEW_LINKS_14,ML_RADAR_SPEW_LINKS_6, spamassassin: X-StarScan-Received: X-StarScan-Version: 6.6.1.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 14771 invoked from network); 4 Sep 2012 04:38:44 -0000 Received: from nm28-vm0.bullet.mail.ne1.yahoo.com (HELO nm28-vm0.bullet.mail.ne1.yahoo.com) (98.138.91.22) by server-10.tower-216.messagelabs.com with SMTP; 4 Sep 2012 04:38:44 -0000 Received: from [98.138.90.57] by nm28.bullet.mail.ne1.yahoo.com with NNFMP; 04 Sep 2012 04:38:43 -0000 Received: from [98.138.89.245] by tm10.bullet.mail.ne1.yahoo.com with NNFMP; 04 Sep 2012 04:38:43 -0000 Received: from [127.0.0.1] by omp1059.mail.ne1.yahoo.com with NNFMP; 04 Sep 2012 04:38:43 -0000 X-Yahoo-Newman-Property: ymail-3 X-Yahoo-Newman-Id: 506758.9932.bm@omp1059.mail.ne1.yahoo.com Received: (qmail 71459 invoked by uid 60001); 4 Sep 2012 04:38:43 -0000 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.com; s=s1024; t=1346733523; bh=qlQkNYy7e3/QVN9wY/a2J/rfAEbvWm0k5j2CaAk2J1w=; h=X-YMail-OSG:Received:X-Mailer:Message-ID:Date:From:Reply-To:Subject:To:MIME-Version:Content-Type:Content-Transfer-Encoding; b=DxZiQInOPKgtHufA0tqA/bbBPPmxEeGvHCbnkJyQF+ra7IdMY5Ux27fOuOgXsUTmVd4L6jORDAufvc4HB6bJXJjr+JpMsR8i8FBPF3iN5iw6VfFXngCTuUDeyUQJf4pLcWHQEy1fWBdgm8CwVlwUZ4DGVDtWHQ0yC6MVLvEbXf0= DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com; h=X-YMail-OSG:Received:X-Mailer:Message-ID:Date:From:Reply-To:Subject:To:MIME-Version:Content-Type:Content-Transfer-Encoding; b=2XxsZCTiRQTai7LovE1lIoMQOU6sXn7H4PJ+AV2I8H6x/ljsy23aQBSYJRtBd2FasKSott0uHISC/NFl/bAnU+dVdMMzo0Am5SZpRrmV7YrQ3BPNaE0SNVJgeLJwaCQLmm2AT85aQ+hPRJpi/Pe3KRhp+VZyT5VBMFrKx2Yi2ew=; X-YMail-OSG: JjoZu0YVM1k6rD8ErVTlMo7B2UZnWk8WUCA2JibPF2V8Upu 8iPF_yp2hz6V_qXyWPQGZXSDv1TA4kKiad7XWK6ttJoJyp5fKSDxcAa5N7_o QyVf_YsrL2WqYokbOOibtOKh20sHe8TPhuA3ZhGrCIfT6r3Nu57FD3aLxnY4 6w_IogDmtmW8l1E7DJ5_F.LQSoNxYzoLufjFfx1aKRmE3TFlaL41uVzcY1zR b_D1F.L5p5VUytpaCekVhpKi.gHhEaTJm7g96gZ7LdYEPCVvpSXJwRGEdx9W F6E4zXdoQkOZrrupZkpv7ir4PPOiE4jLRfCj5H97CsqlIgUu9l7tGb1Jq2kx U3fYwXKEHb9TIlIwZHRPvy8Ethy9yfPSUIPAJtn6_X.uhkjDGiZ7TtQ49SCZ WXvM..Ljh7s.ORsiSEuEdYIeMIT_N4L1UYYioJm1iriOS0fa.XDaJPUtfob8 c.OAdXsvvZObdSWptflySFRCJwNuleZXLlscQss4H7Ean2vgqqcYDBOrRw6p I0r3Jwe2655hDV2E- Received: from [111.68.102.23] by web126003.mail.ne1.yahoo.com via HTTP; Mon, 03 Sep 2012 21:38:43 PDT X-Mailer: YahooMailWebService/0.8.121.416 Message-ID: <1346733523.60759.YahooMailNeo@web126003.mail.ne1.yahoo.com> Date: Mon, 3 Sep 2012 21:38:43 -0700 (PDT) From: maheen butt To: "xen-users@lists.xen.org" MIME-Version: 1.0 Subject: [Xen-users] Xen summit Videos X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list Reply-To: maheen butt List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org Hi, When will Xen Summit 2012's Videos and presentation be=A0available on xen.o= rg? Thanks=A0 _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Tue Sep 04 04:40:00 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Tue, 04 Sep 2012 04:40:00 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1T8kuV-0007JT-IH; Tue, 04 Sep 2012 04:38:47 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1T8kuU-0007JO-2Y for xen-users@lists.xen.org; Tue, 04 Sep 2012 04:38:46 +0000 Received: from [85.158.143.99:42915] by server-1.bemta-4.messagelabs.com id 53/E1-12504-5D585405; Tue, 04 Sep 2012 04:38:45 +0000 X-Env-Sender: maheen_butt26@yahoo.com X-Msg-Ref: server-10.tower-216.messagelabs.com!1346733524!21960463!1 X-Originating-IP: [98.138.91.22] X-SpamReason: No, hits=0.7 required=7.0 tests=FROM_HAS_ULINE_NUMS, ML_RADAR_SPEW_LINKS_12,ML_RADAR_SPEW_LINKS_14,ML_RADAR_SPEW_LINKS_6, spamassassin: X-StarScan-Received: X-StarScan-Version: 6.6.1.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 14771 invoked from network); 4 Sep 2012 04:38:44 -0000 Received: from nm28-vm0.bullet.mail.ne1.yahoo.com (HELO nm28-vm0.bullet.mail.ne1.yahoo.com) (98.138.91.22) by server-10.tower-216.messagelabs.com with SMTP; 4 Sep 2012 04:38:44 -0000 Received: from [98.138.90.57] by nm28.bullet.mail.ne1.yahoo.com with NNFMP; 04 Sep 2012 04:38:43 -0000 Received: from [98.138.89.245] by tm10.bullet.mail.ne1.yahoo.com with NNFMP; 04 Sep 2012 04:38:43 -0000 Received: from [127.0.0.1] by omp1059.mail.ne1.yahoo.com with NNFMP; 04 Sep 2012 04:38:43 -0000 X-Yahoo-Newman-Property: ymail-3 X-Yahoo-Newman-Id: 506758.9932.bm@omp1059.mail.ne1.yahoo.com Received: (qmail 71459 invoked by uid 60001); 4 Sep 2012 04:38:43 -0000 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.com; s=s1024; t=1346733523; bh=qlQkNYy7e3/QVN9wY/a2J/rfAEbvWm0k5j2CaAk2J1w=; h=X-YMail-OSG:Received:X-Mailer:Message-ID:Date:From:Reply-To:Subject:To:MIME-Version:Content-Type:Content-Transfer-Encoding; b=DxZiQInOPKgtHufA0tqA/bbBPPmxEeGvHCbnkJyQF+ra7IdMY5Ux27fOuOgXsUTmVd4L6jORDAufvc4HB6bJXJjr+JpMsR8i8FBPF3iN5iw6VfFXngCTuUDeyUQJf4pLcWHQEy1fWBdgm8CwVlwUZ4DGVDtWHQ0yC6MVLvEbXf0= DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com; h=X-YMail-OSG:Received:X-Mailer:Message-ID:Date:From:Reply-To:Subject:To:MIME-Version:Content-Type:Content-Transfer-Encoding; b=2XxsZCTiRQTai7LovE1lIoMQOU6sXn7H4PJ+AV2I8H6x/ljsy23aQBSYJRtBd2FasKSott0uHISC/NFl/bAnU+dVdMMzo0Am5SZpRrmV7YrQ3BPNaE0SNVJgeLJwaCQLmm2AT85aQ+hPRJpi/Pe3KRhp+VZyT5VBMFrKx2Yi2ew=; X-YMail-OSG: JjoZu0YVM1k6rD8ErVTlMo7B2UZnWk8WUCA2JibPF2V8Upu 8iPF_yp2hz6V_qXyWPQGZXSDv1TA4kKiad7XWK6ttJoJyp5fKSDxcAa5N7_o QyVf_YsrL2WqYokbOOibtOKh20sHe8TPhuA3ZhGrCIfT6r3Nu57FD3aLxnY4 6w_IogDmtmW8l1E7DJ5_F.LQSoNxYzoLufjFfx1aKRmE3TFlaL41uVzcY1zR b_D1F.L5p5VUytpaCekVhpKi.gHhEaTJm7g96gZ7LdYEPCVvpSXJwRGEdx9W F6E4zXdoQkOZrrupZkpv7ir4PPOiE4jLRfCj5H97CsqlIgUu9l7tGb1Jq2kx U3fYwXKEHb9TIlIwZHRPvy8Ethy9yfPSUIPAJtn6_X.uhkjDGiZ7TtQ49SCZ WXvM..Ljh7s.ORsiSEuEdYIeMIT_N4L1UYYioJm1iriOS0fa.XDaJPUtfob8 c.OAdXsvvZObdSWptflySFRCJwNuleZXLlscQss4H7Ean2vgqqcYDBOrRw6p I0r3Jwe2655hDV2E- Received: from [111.68.102.23] by web126003.mail.ne1.yahoo.com via HTTP; Mon, 03 Sep 2012 21:38:43 PDT X-Mailer: YahooMailWebService/0.8.121.416 Message-ID: <1346733523.60759.YahooMailNeo@web126003.mail.ne1.yahoo.com> Date: Mon, 3 Sep 2012 21:38:43 -0700 (PDT) From: maheen butt To: "xen-users@lists.xen.org" MIME-Version: 1.0 Subject: [Xen-users] Xen summit Videos X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list Reply-To: maheen butt List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org Hi, When will Xen Summit 2012's Videos and presentation be=A0available on xen.o= rg? Thanks=A0 _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Tue Sep 04 04:56:58 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Tue, 04 Sep 2012 04:56:58 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1T8lB1-0007e8-9C; Tue, 04 Sep 2012 04:55:51 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1T8lB0-0007e2-Da for xen-users@lists.xen.org; Tue, 04 Sep 2012 04:55:50 +0000 Received: from [85.158.139.83:41234] by server-12.bemta-5.messagelabs.com id 22/67-18300-5D985405; Tue, 04 Sep 2012 04:55:49 +0000 X-Env-Sender: maheen_butt26@yahoo.com X-Msg-Ref: server-2.tower-182.messagelabs.com!1346734548!28378802!1 X-Originating-IP: [98.138.91.73] X-SpamReason: No, hits=0.7 required=7.0 tests=FROM_HAS_ULINE_NUMS, ML_RADAR_SPEW_LINKS_12,ML_RADAR_SPEW_LINKS_14,spamassassin: X-StarScan-Received: X-StarScan-Version: 6.6.1.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 1908 invoked from network); 4 Sep 2012 04:55:48 -0000 Received: from nm25-vm0.bullet.mail.ne1.yahoo.com (HELO nm25-vm0.bullet.mail.ne1.yahoo.com) (98.138.91.73) by server-2.tower-182.messagelabs.com with SMTP; 4 Sep 2012 04:55:48 -0000 Received: from [98.138.90.55] by nm25.bullet.mail.ne1.yahoo.com with NNFMP; 04 Sep 2012 04:55:47 -0000 Received: from [98.138.89.194] by tm8.bullet.mail.ne1.yahoo.com with NNFMP; 04 Sep 2012 04:55:47 -0000 Received: from [127.0.0.1] by omp1052.mail.ne1.yahoo.com with NNFMP; 04 Sep 2012 04:55:47 -0000 X-Yahoo-Newman-Property: ymail-3 X-Yahoo-Newman-Id: 460545.23364.bm@omp1052.mail.ne1.yahoo.com Received: (qmail 966 invoked by uid 60001); 4 Sep 2012 04:55:47 -0000 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.com; s=s1024; t=1346734547; bh=F8fQKsKnSee1sKW0N5sN+hLRCuqgp4Clya2BAoF7mlQ=; h=X-YMail-OSG:Received:X-Mailer:References:Message-ID:Date:From:Reply-To:Subject:To:Cc:In-Reply-To:MIME-Version:Content-Type:Content-Transfer-Encoding; b=oYV2XX67FrdU2yhVHR9Pf937YhfuVy6yYzfmPBFYnn/rEyf0nEAi9lR785zQVqPML0btH8gcu/XdFkGKrDJE9BalrNZXRLhi3+l56lky9VQxEnmCsj+jolxue9flyC15Q2Iwsg64pWayaK2XzzOjS5omNjb6KT1GQnYjuaIJtxI= DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com; h=X-YMail-OSG:Received:X-Mailer:References:Message-ID:Date:From:Reply-To:Subject:To:Cc:In-Reply-To:MIME-Version:Content-Type:Content-Transfer-Encoding; b=l55+CpJpkga20DsnlLNfaxNK0J5DHImuXULmq5oMMWxDwpz/k58jKoOFYQ9Q2rljsKpT2FhtTuewPRAzJsy/u+I1Ep7a5B3vYtIcEdY+A172lupYexJB2VxfKKnacnvB+wtD+dKEZOjF+7pwfug/kI1D395yuNJTA4Q3gnSG+rk=; X-YMail-OSG: GDPaWA0VM1kX7.QXSWIb4VWpdjLZ_OS3zGZgbR42gLCHmh8 Po1DeBJ.OMVto4h.o_kRJ3r22.HipGuFNy6TPcYR3VuxnJpKL6WEbWY2K5AY VvqzXstkLnCdYeqX9JlHN1iqfjPRNiZNo9Aq7Yik5q2QyNX4JlwqZhyYVwjW yTD.g4j23Cm4n7JRgeKM7Qj25rIWT4p63j8xv.jg_LNf.0eoBqNgSuLV_Fsq yz43XSCSMiRGhys9QrAWkYW9h1ElGVdyQYlYG__bOjxNV4OFOalh.uORkfcG 1m.a1epmBFbcS9QOLRILlPe9AoWFTply9EpxRtMODJuy5SO09k0mcoDQdTkh 2OTbsDttJ0aWvnxcABOL0MmPaI3XvQCDZtzQcc6hDHVqfTAVjjmzgf29gF9D IV7ieonswSlcojtUJDW12yn7g1XpOTEn7jGpZ.19dtIr5DYTH.0ywaOkq9pQ 28cvvlo32i_Az9t8sIJN7aGqnHOb_TRnSLzqE.n89TWEbp7wD Received: from [111.68.102.23] by web126002.mail.ne1.yahoo.com via HTTP; Mon, 03 Sep 2012 21:55:47 PDT X-Mailer: YahooMailWebService/0.8.121.416 References: <1092892085@mx1.poinfor.net> Message-ID: <1346734547.93695.YahooMailNeo@web126002.mail.ne1.yahoo.com> Date: Mon, 3 Sep 2012 21:55:47 -0700 (PDT) From: maheen butt To: "florian.piroux@piroux.com" In-Reply-To: <1092892085@mx1.poinfor.net> MIME-Version: 1.0 Cc: "xen-users@lists.xen.org" Subject: Re: [Xen-users] Xen summit Videos X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list Reply-To: maheen butt List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org can't understand Please use English=A0 ----- Original Message ----- From: "florian.piroux@piroux.com" To: maheen_butt26@yahoo.com Cc: = Sent: Tuesday, September 4, 2012 9:45 AM Subject: Re: [Xen-users] Xen summit Videos Mr Florian PIROUX ne fait plus partie du Groupe Piroux. Vous pouvez d=E9sormais contacter le service informatique : 04 74 42 10 45 ou Brice PACCOUD au 04 74 42 98 28 ou =E0 l'adresse brice.paccoud@piroux.com ou Patrice CARRON au 04 74 42 98 29=A0 ou =E0 l'adresse patrice.carron@piroux.= com Cordialement _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Tue Sep 04 04:56:58 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Tue, 04 Sep 2012 04:56:58 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1T8lB1-0007e8-9C; Tue, 04 Sep 2012 04:55:51 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1T8lB0-0007e2-Da for xen-users@lists.xen.org; Tue, 04 Sep 2012 04:55:50 +0000 Received: from [85.158.139.83:41234] by server-12.bemta-5.messagelabs.com id 22/67-18300-5D985405; Tue, 04 Sep 2012 04:55:49 +0000 X-Env-Sender: maheen_butt26@yahoo.com X-Msg-Ref: server-2.tower-182.messagelabs.com!1346734548!28378802!1 X-Originating-IP: [98.138.91.73] X-SpamReason: No, hits=0.7 required=7.0 tests=FROM_HAS_ULINE_NUMS, ML_RADAR_SPEW_LINKS_12,ML_RADAR_SPEW_LINKS_14,spamassassin: X-StarScan-Received: X-StarScan-Version: 6.6.1.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 1908 invoked from network); 4 Sep 2012 04:55:48 -0000 Received: from nm25-vm0.bullet.mail.ne1.yahoo.com (HELO nm25-vm0.bullet.mail.ne1.yahoo.com) (98.138.91.73) by server-2.tower-182.messagelabs.com with SMTP; 4 Sep 2012 04:55:48 -0000 Received: from [98.138.90.55] by nm25.bullet.mail.ne1.yahoo.com with NNFMP; 04 Sep 2012 04:55:47 -0000 Received: from [98.138.89.194] by tm8.bullet.mail.ne1.yahoo.com with NNFMP; 04 Sep 2012 04:55:47 -0000 Received: from [127.0.0.1] by omp1052.mail.ne1.yahoo.com with NNFMP; 04 Sep 2012 04:55:47 -0000 X-Yahoo-Newman-Property: ymail-3 X-Yahoo-Newman-Id: 460545.23364.bm@omp1052.mail.ne1.yahoo.com Received: (qmail 966 invoked by uid 60001); 4 Sep 2012 04:55:47 -0000 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.com; s=s1024; t=1346734547; bh=F8fQKsKnSee1sKW0N5sN+hLRCuqgp4Clya2BAoF7mlQ=; h=X-YMail-OSG:Received:X-Mailer:References:Message-ID:Date:From:Reply-To:Subject:To:Cc:In-Reply-To:MIME-Version:Content-Type:Content-Transfer-Encoding; b=oYV2XX67FrdU2yhVHR9Pf937YhfuVy6yYzfmPBFYnn/rEyf0nEAi9lR785zQVqPML0btH8gcu/XdFkGKrDJE9BalrNZXRLhi3+l56lky9VQxEnmCsj+jolxue9flyC15Q2Iwsg64pWayaK2XzzOjS5omNjb6KT1GQnYjuaIJtxI= DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com; h=X-YMail-OSG:Received:X-Mailer:References:Message-ID:Date:From:Reply-To:Subject:To:Cc:In-Reply-To:MIME-Version:Content-Type:Content-Transfer-Encoding; b=l55+CpJpkga20DsnlLNfaxNK0J5DHImuXULmq5oMMWxDwpz/k58jKoOFYQ9Q2rljsKpT2FhtTuewPRAzJsy/u+I1Ep7a5B3vYtIcEdY+A172lupYexJB2VxfKKnacnvB+wtD+dKEZOjF+7pwfug/kI1D395yuNJTA4Q3gnSG+rk=; X-YMail-OSG: GDPaWA0VM1kX7.QXSWIb4VWpdjLZ_OS3zGZgbR42gLCHmh8 Po1DeBJ.OMVto4h.o_kRJ3r22.HipGuFNy6TPcYR3VuxnJpKL6WEbWY2K5AY VvqzXstkLnCdYeqX9JlHN1iqfjPRNiZNo9Aq7Yik5q2QyNX4JlwqZhyYVwjW yTD.g4j23Cm4n7JRgeKM7Qj25rIWT4p63j8xv.jg_LNf.0eoBqNgSuLV_Fsq yz43XSCSMiRGhys9QrAWkYW9h1ElGVdyQYlYG__bOjxNV4OFOalh.uORkfcG 1m.a1epmBFbcS9QOLRILlPe9AoWFTply9EpxRtMODJuy5SO09k0mcoDQdTkh 2OTbsDttJ0aWvnxcABOL0MmPaI3XvQCDZtzQcc6hDHVqfTAVjjmzgf29gF9D IV7ieonswSlcojtUJDW12yn7g1XpOTEn7jGpZ.19dtIr5DYTH.0ywaOkq9pQ 28cvvlo32i_Az9t8sIJN7aGqnHOb_TRnSLzqE.n89TWEbp7wD Received: from [111.68.102.23] by web126002.mail.ne1.yahoo.com via HTTP; Mon, 03 Sep 2012 21:55:47 PDT X-Mailer: YahooMailWebService/0.8.121.416 References: <1092892085@mx1.poinfor.net> Message-ID: <1346734547.93695.YahooMailNeo@web126002.mail.ne1.yahoo.com> Date: Mon, 3 Sep 2012 21:55:47 -0700 (PDT) From: maheen butt To: "florian.piroux@piroux.com" In-Reply-To: <1092892085@mx1.poinfor.net> MIME-Version: 1.0 Cc: "xen-users@lists.xen.org" Subject: Re: [Xen-users] Xen summit Videos X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list Reply-To: maheen butt List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org can't understand Please use English=A0 ----- Original Message ----- From: "florian.piroux@piroux.com" To: maheen_butt26@yahoo.com Cc: = Sent: Tuesday, September 4, 2012 9:45 AM Subject: Re: [Xen-users] Xen summit Videos Mr Florian PIROUX ne fait plus partie du Groupe Piroux. Vous pouvez d=E9sormais contacter le service informatique : 04 74 42 10 45 ou Brice PACCOUD au 04 74 42 98 28 ou =E0 l'adresse brice.paccoud@piroux.com ou Patrice CARRON au 04 74 42 98 29=A0 ou =E0 l'adresse patrice.carron@piroux.= com Cordialement _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Tue Sep 04 05:30:02 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Tue, 04 Sep 2012 05:30:02 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1T8lgz-0008Ed-9W; Tue, 04 Sep 2012 05:28:53 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1T8lgx-0008EY-M2 for xen-users@lists.xen.org; Tue, 04 Sep 2012 05:28:51 +0000 Received: from [85.158.138.51:60977] by server-4.bemta-3.messagelabs.com id DF/EA-24831-19195405; Tue, 04 Sep 2012 05:28:49 +0000 X-Env-Sender: raju@linux-delhi.org X-Msg-Ref: server-6.tower-174.messagelabs.com!1346736519!20408953!1 X-Originating-IP: [83.143.86.98] X-SpamReason: No, hits=0.0 required=7.0 tests=ML_RADAR_SPEW_LINKS_8, spamassassin: , async_handler: YXN5bmNfZGVsYXk6IDcwNDU1ODkgKHRpbWVvdXQp\n X-StarScan-Received: X-StarScan-Version: 6.6.1.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 6538 invoked from network); 4 Sep 2012 05:28:39 -0000 Received: from etc.kandalaya.org (HELO images.kandalaya.org) (83.143.86.98) by server-6.tower-174.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 4 Sep 2012 05:28:39 -0000 Received: from mail.linux-delhi.org ([115.241.240.117]) by images.kandalaya.org (8.14.3/8.14.3/Debian-9) with ESMTP id q845SWIu017783 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK) for ; Tue, 4 Sep 2012 10:58:36 +0530 Received: from mail.linux-delhi.org (raju@localhost [127.0.0.1]) by mail.linux-delhi.org (8.14.4/8.14.4/Debian-2.1) with ESMTP id q845SHhL012474 for ; Tue, 4 Sep 2012 10:58:18 +0530 From: "Raj Mathur (=?utf-8?b?4KSw4KS+4KSc?= =?utf-8?b?IOCkruCkvuCkpeClgeCksA==?=)" Organization: Kandalaya To: xen-users@lists.xen.org Date: Tue, 4 Sep 2012 10:58:17 +0530 User-Agent: KMail/1.13.7 (Linux/3.2.233-rt37; KDE/4.8.4; i686; ; ) References: <1092892085@mx1.poinfor.net> <1346734547.93695.YahooMailNeo@web126002.mail.ne1.yahoo.com> In-Reply-To: <1346734547.93695.YahooMailNeo@web126002.mail.ne1.yahoo.com> MIME-Version: 1.0 Message-Id: <201209041058.17442.raju@linux-delhi.org> X-Spam-Status: No, score=-10.7 required=5.0 tests=AWL,BAYES_00, DNS_FROM_RFC_BOGUSMX, LOCAL_FROM_RAJU, RCVD_IN_PBL, RDNS_NONE autolearn=ham version=3.2.5 X-Spam-Checker-Version: SpamAssassin 3.2.5 (2008-06-10) on images.kandalaya.org X-Virus-Scanned: clamav-milter 0.95.2 at images.kandalaya.org X-Virus-Status: Clean Subject: Re: [Xen-users] Xen summit Videos X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list Reply-To: raju@linux-delhi.org List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org On Tuesday 04 Sep 2012, maheen butt wrote: > can't understand Please use English = Looks like an automated Out-of-Office message in French. I also got one = of these. Do these need to be reported to the list admin? -- Raj > ----- Original Message ----- > From: "florian.piroux@piroux.com" > To: maheen_butt26@yahoo.com > Cc: > Sent: Tuesday, September 4, 2012 9:45 AM > Subject: Re: [Xen-users] Xen summit Videos > = > Mr Florian PIROUX ne fait plus partie du Groupe Piroux. > = > Vous pouvez d=E9sormais contacter le service informatique : > 04 74 42 10 45 > ou > Brice PACCOUD au 04 74 42 98 28 ou =E0 l'adresse > brice.paccoud@piroux.com ou > Patrice CARRON au 04 74 42 98 29 ou =E0 l'adresse > patrice.carron@piroux.com > = > Cordialement -- = Raj Mathur || raju@kandalaya.org || GPG: http://otheronepercent.blogspot.com || http://kandalaya.org || CC68 It is the mind that moves || http://schizoid.in || D17F _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Tue Sep 04 05:30:02 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Tue, 04 Sep 2012 05:30:02 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1T8lgz-0008Ed-9W; Tue, 04 Sep 2012 05:28:53 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1T8lgx-0008EY-M2 for xen-users@lists.xen.org; Tue, 04 Sep 2012 05:28:51 +0000 Received: from [85.158.138.51:60977] by server-4.bemta-3.messagelabs.com id DF/EA-24831-19195405; Tue, 04 Sep 2012 05:28:49 +0000 X-Env-Sender: raju@linux-delhi.org X-Msg-Ref: server-6.tower-174.messagelabs.com!1346736519!20408953!1 X-Originating-IP: [83.143.86.98] X-SpamReason: No, hits=0.0 required=7.0 tests=ML_RADAR_SPEW_LINKS_8, spamassassin: , async_handler: YXN5bmNfZGVsYXk6IDcwNDU1ODkgKHRpbWVvdXQp\n X-StarScan-Received: X-StarScan-Version: 6.6.1.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 6538 invoked from network); 4 Sep 2012 05:28:39 -0000 Received: from etc.kandalaya.org (HELO images.kandalaya.org) (83.143.86.98) by server-6.tower-174.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 4 Sep 2012 05:28:39 -0000 Received: from mail.linux-delhi.org ([115.241.240.117]) by images.kandalaya.org (8.14.3/8.14.3/Debian-9) with ESMTP id q845SWIu017783 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK) for ; Tue, 4 Sep 2012 10:58:36 +0530 Received: from mail.linux-delhi.org (raju@localhost [127.0.0.1]) by mail.linux-delhi.org (8.14.4/8.14.4/Debian-2.1) with ESMTP id q845SHhL012474 for ; Tue, 4 Sep 2012 10:58:18 +0530 From: "Raj Mathur (=?utf-8?b?4KSw4KS+4KSc?= =?utf-8?b?IOCkruCkvuCkpeClgeCksA==?=)" Organization: Kandalaya To: xen-users@lists.xen.org Date: Tue, 4 Sep 2012 10:58:17 +0530 User-Agent: KMail/1.13.7 (Linux/3.2.233-rt37; KDE/4.8.4; i686; ; ) References: <1092892085@mx1.poinfor.net> <1346734547.93695.YahooMailNeo@web126002.mail.ne1.yahoo.com> In-Reply-To: <1346734547.93695.YahooMailNeo@web126002.mail.ne1.yahoo.com> MIME-Version: 1.0 Message-Id: <201209041058.17442.raju@linux-delhi.org> X-Spam-Status: No, score=-10.7 required=5.0 tests=AWL,BAYES_00, DNS_FROM_RFC_BOGUSMX, LOCAL_FROM_RAJU, RCVD_IN_PBL, RDNS_NONE autolearn=ham version=3.2.5 X-Spam-Checker-Version: SpamAssassin 3.2.5 (2008-06-10) on images.kandalaya.org X-Virus-Scanned: clamav-milter 0.95.2 at images.kandalaya.org X-Virus-Status: Clean Subject: Re: [Xen-users] Xen summit Videos X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list Reply-To: raju@linux-delhi.org List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org On Tuesday 04 Sep 2012, maheen butt wrote: > can't understand Please use English = Looks like an automated Out-of-Office message in French. I also got one = of these. Do these need to be reported to the list admin? -- Raj > ----- Original Message ----- > From: "florian.piroux@piroux.com" > To: maheen_butt26@yahoo.com > Cc: > Sent: Tuesday, September 4, 2012 9:45 AM > Subject: Re: [Xen-users] Xen summit Videos > = > Mr Florian PIROUX ne fait plus partie du Groupe Piroux. > = > Vous pouvez d=E9sormais contacter le service informatique : > 04 74 42 10 45 > ou > Brice PACCOUD au 04 74 42 98 28 ou =E0 l'adresse > brice.paccoud@piroux.com ou > Patrice CARRON au 04 74 42 98 29 ou =E0 l'adresse > patrice.carron@piroux.com > = > Cordialement -- = Raj Mathur || raju@kandalaya.org || GPG: http://otheronepercent.blogspot.com || http://kandalaya.org || CC68 It is the mind that moves || http://schizoid.in || D17F _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Tue Sep 04 05:44:36 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Tue, 04 Sep 2012 05:44:36 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1T8lvH-00008T-Vl; Tue, 04 Sep 2012 05:43:39 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1T8lvG-00008M-FS for xen-users@lists.xen.org; Tue, 04 Sep 2012 05:43:38 +0000 Received: from [85.158.139.83:31841] by server-12.bemta-5.messagelabs.com id 86/D4-18300-70595405; Tue, 04 Sep 2012 05:43:35 +0000 X-Env-Sender: nd@syndicat.com X-Msg-Ref: server-2.tower-182.messagelabs.com!1346737414!28383547!1 X-Originating-IP: [62.146.89.62] X-SpamReason: No, hits=0.0 required=7.0 tests=ML_RADAR_SPEW_LINKS_8, spamassassin: , surbl: (ASYNC_NO) c3VyYmxfcmVjaGVja19kZWxheTogMCAoYWJhbmRv bmVkOiBvdGhlcm9uZXBlcmNlbnQuYmxvZ3Nw\nb3QuY29tKQ==\n X-StarScan-Received: X-StarScan-Version: 6.6.1.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 3123 invoked from network); 4 Sep 2012 05:43:34 -0000 Received: from ffm-dr1.syndicat.com (HELO ffm-dr1.syndicat.com) (62.146.89.62) by server-2.tower-182.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 4 Sep 2012 05:43:34 -0000 Received: from localhost.syndicat.com ([127.0.0.1] helo=localhost) by ffm-dr1.syndicat.com with esmtp (Syndicat.com PostHamster 8.1.4.76) (envelope-from ) id 1T8lvC-00000x-JF; Tue, 04 Sep 2012 07:43:34 +0200 X-Virus-Scanned: amavisd-new at syndicat.com Received: from ffm-dr1.syndicat.com ([127.0.0.1]) by localhost (ffm-dr1.syndicat.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id K7s4O7C69q-1; Tue, 4 Sep 2012 07:43:34 +0200 (CEST) Received: from p5dc3fa31.dip.t-dialin.net ([93.195.250.49] helo=htc.syndicat) by ffm-dr1.syndicat.com with esmtpsa (TLSv1:RC4-MD5:128) (Syndicat.com PostHamster 8.1.4.76) (envelope-from ) id 1T8lv7-0006y6-0A; Tue, 04 Sep 2012 07:43:34 +0200 User-Agent: K-9 Mail for Android References: <2b6855a8-e110-45b5-9a26-c575823060f3@email.android.com> In-Reply-To: <2b6855a8-e110-45b5-9a26-c575823060f3@email.android.com> MIME-Version: 1.0 From: "Niels Dettenbach (Syndicat IT&Internet)" Date: Tue, 04 Sep 2012 07:43:06 +0200 To: raju@linux-delhi.org,xen-users@lists.xen.org Message-ID: <32e7240f-0a6e-42af-8ecf-1569f7e4ff4e@email.android.com> Subject: Re: [Xen-users] Severe dom0 performance issues after installing Xen X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: base64 Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org Li4ubm90IHNodXJlIHdoYXQncyBnb2luZyBvbiB0aGVyZSwgYnV0IHdvdWxkIHRyeSBmb2xsb3dp bmcgdGhpbmdzOgoKLSB0cnkgdG8gYm9vdCB3aXRoIGtlcm5lbCBvcHRpb25zIG5vYXBpYwotIHRy eSB0byBwaW4gb25lIENQVSBkaXJlY3RseSB0byBEb20wIGFuZCBzZXQgbWF4IGNwdSB0byAxIG9u IERvbTAgKHhlbiBhbmQga2VybmVsIG9wdGlvbnMpCi0gdHJ5IHRvIGJvb3Qgd2l0aCBkaXNhYmxl ZCBhY3BpIGV0Yy4KLSB0cnkgdG8gZmluZCBvdXQgIndoYXQiIGlzIHNsb3csIGkuZS4gSS9PLCBD UFUsIG5ldCBldGMgYW5kIHdoYXQgbm90CgpJcyB0aGVyZSBhbnkgInBvaW50IiB0byByZWNvZ25p emUgZHVyaW5nIGJvb3Qgd2hlbiB0aGUgc3lzdGVtICJnb3Qgc2xvdyI/CgoKQmVzdCByZWdhcmRz LAoKCk5pZWxzLgoKCgoiUmFqIE1hdGh1ciAo4KSw4KS+4KScIOCkruCkvuCkpeClgeCksCkiIDxy YWp1QGxpbnV4LWRlbGhpLm9yZz4gc2NocmllYjoKCj5PbiBUdWVzZGF5IDA0IFNlcCAyMDEyLCBL ZWl0aCBCdWNrIHdyb3RlOgo+PiBJJ20gZXhwZXJpZW5jaW5nIHNvbWUgc2V2ZXJlIHBlcmZvcm1h bmNlIGlzc3VlcyBydW5uaW5nIFhlbiA0LjAuMQo+PiB3aXRoIGEgY2xlYW5seS1pbnN0YWxsZWQg RGViaWFuIDYgZG9tMC4gIFByaW9yIHRvIGluc3RhbGxhdGlvbiwgdGhlCj4+IG1hY2hpbmUncyBw ZXJmb3JtYW5jZSB3YXMgZmluZSwgYnV0IGFmdGVyIGluc3RhbGxhdGlvbiBib290aW5nIHRha2Vz Cj4+IGFueXdoZXJlIGZyb20gNSB0byAyMCB0aW1lcyBsb25nZXIsIHByb2Nlc3NlcyB0YWtlIGEg bG9uZyB0aW1lIHRvCj4+IHN0YXJ0LCBhbmQgU1NIIGxhZ3MuICBObyBkb21VcyBhcmUgcnVubmlu ZyAob3IgaGF2ZSBiZWVuIGNyZWF0ZWQKPj4geWV0KS4gIEkgY2FuIHN3aXRjaCBiYWNrIHRvIHJ1 bm5pbmcgd2l0aG91dCBYZW4gKGJ1dCBzdGlsbCB1c2luZyB0aGUKPj4gWGVuLWNvbXBhdGlibGUg a2VybmVsKSBhbmQgdGhlIHBlcmZvcm1hbmNlIHByb2JsZW1zIGRpc2FwcGVhci4KPgo+UHJvYmFi bHkgYSBzdHVwaWQgcXVlc3Rpb24sIGJ1dCBzb21ldGltZSB3ZSBtaXNzIHRoZSBvYnZpb3VzOiBk aWQgeW91IAo+bWFrZSBhbnkgbmV0d29ya2luZyBjaGFuZ2VzPyAgU3BlY2lmaWNhbGx5LCBjb3Vs ZCB0aGlzIHByb2JsZW0gYmUgZHVlCj50byAKPm5vdCBiZWluZyBhYmxlIHRvIHJldmVyc2UgcmVz b2x2ZSBJUCBhZGRyZXNzZXMgb24geW91ciBtYWNoaW5lPwo+Cj5SZWdhcmRzLAo+Cj4tLSBSYWoK Pi0tIAo+UmFqIE1hdGh1ciAgICAgICAgICAgICAgICAgICAgICAgICAgfHwgcmFqdUBrYW5kYWxh eWEub3JnICAgfHwgR1BHOgo+aHR0cDovL290aGVyb25lcGVyY2VudC5ibG9nc3BvdC5jb20gfHwg aHR0cDovL2thbmRhbGF5YS5vcmcgfHwgQ0M2OAo+SXQgaXMgdGhlIG1pbmQgdGhhdCBtb3ZlcyAg ICAgICAgICAgfHwgaHR0cDovL3NjaGl6b2lkLmluICAgfHwgRDE3Rgo+Cj5fX19fX19fX19fX19f X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fXwoKLS0gCk5pZWxzIERldHRlbmJhY2gKU3lu ZGljYXQgSVQmSW50ZXJuZXQKaHR0cDovL3d3dy5zeW5kaWNhdC5jb20KCgpfX19fX19fX19fX19f X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fXwpYZW4tdXNlcnMgbWFpbGluZyBsaXN0 Clhlbi11c2Vyc0BsaXN0cy54ZW4ub3JnCmh0dHA6Ly9saXN0cy54ZW4ub3JnL3hlbi11c2Vycw== From xen-users-bounces@lists.xen.org Tue Sep 04 05:44:36 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Tue, 04 Sep 2012 05:44:36 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1T8lvH-00008T-Vl; Tue, 04 Sep 2012 05:43:39 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1T8lvG-00008M-FS for xen-users@lists.xen.org; Tue, 04 Sep 2012 05:43:38 +0000 Received: from [85.158.139.83:31841] by server-12.bemta-5.messagelabs.com id 86/D4-18300-70595405; Tue, 04 Sep 2012 05:43:35 +0000 X-Env-Sender: nd@syndicat.com X-Msg-Ref: server-2.tower-182.messagelabs.com!1346737414!28383547!1 X-Originating-IP: [62.146.89.62] X-SpamReason: No, hits=0.0 required=7.0 tests=ML_RADAR_SPEW_LINKS_8, spamassassin: , surbl: (ASYNC_NO) c3VyYmxfcmVjaGVja19kZWxheTogMCAoYWJhbmRv bmVkOiBvdGhlcm9uZXBlcmNlbnQuYmxvZ3Nw\nb3QuY29tKQ==\n X-StarScan-Received: X-StarScan-Version: 6.6.1.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 3123 invoked from network); 4 Sep 2012 05:43:34 -0000 Received: from ffm-dr1.syndicat.com (HELO ffm-dr1.syndicat.com) (62.146.89.62) by server-2.tower-182.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 4 Sep 2012 05:43:34 -0000 Received: from localhost.syndicat.com ([127.0.0.1] helo=localhost) by ffm-dr1.syndicat.com with esmtp (Syndicat.com PostHamster 8.1.4.76) (envelope-from ) id 1T8lvC-00000x-JF; Tue, 04 Sep 2012 07:43:34 +0200 X-Virus-Scanned: amavisd-new at syndicat.com Received: from ffm-dr1.syndicat.com ([127.0.0.1]) by localhost (ffm-dr1.syndicat.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id K7s4O7C69q-1; Tue, 4 Sep 2012 07:43:34 +0200 (CEST) Received: from p5dc3fa31.dip.t-dialin.net ([93.195.250.49] helo=htc.syndicat) by ffm-dr1.syndicat.com with esmtpsa (TLSv1:RC4-MD5:128) (Syndicat.com PostHamster 8.1.4.76) (envelope-from ) id 1T8lv7-0006y6-0A; Tue, 04 Sep 2012 07:43:34 +0200 User-Agent: K-9 Mail for Android References: <2b6855a8-e110-45b5-9a26-c575823060f3@email.android.com> In-Reply-To: <2b6855a8-e110-45b5-9a26-c575823060f3@email.android.com> MIME-Version: 1.0 From: "Niels Dettenbach (Syndicat IT&Internet)" Date: Tue, 04 Sep 2012 07:43:06 +0200 To: raju@linux-delhi.org,xen-users@lists.xen.org Message-ID: <32e7240f-0a6e-42af-8ecf-1569f7e4ff4e@email.android.com> Subject: Re: [Xen-users] Severe dom0 performance issues after installing Xen X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: base64 Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org Li4ubm90IHNodXJlIHdoYXQncyBnb2luZyBvbiB0aGVyZSwgYnV0IHdvdWxkIHRyeSBmb2xsb3dp bmcgdGhpbmdzOgoKLSB0cnkgdG8gYm9vdCB3aXRoIGtlcm5lbCBvcHRpb25zIG5vYXBpYwotIHRy eSB0byBwaW4gb25lIENQVSBkaXJlY3RseSB0byBEb20wIGFuZCBzZXQgbWF4IGNwdSB0byAxIG9u IERvbTAgKHhlbiBhbmQga2VybmVsIG9wdGlvbnMpCi0gdHJ5IHRvIGJvb3Qgd2l0aCBkaXNhYmxl ZCBhY3BpIGV0Yy4KLSB0cnkgdG8gZmluZCBvdXQgIndoYXQiIGlzIHNsb3csIGkuZS4gSS9PLCBD UFUsIG5ldCBldGMgYW5kIHdoYXQgbm90CgpJcyB0aGVyZSBhbnkgInBvaW50IiB0byByZWNvZ25p emUgZHVyaW5nIGJvb3Qgd2hlbiB0aGUgc3lzdGVtICJnb3Qgc2xvdyI/CgoKQmVzdCByZWdhcmRz LAoKCk5pZWxzLgoKCgoiUmFqIE1hdGh1ciAo4KSw4KS+4KScIOCkruCkvuCkpeClgeCksCkiIDxy YWp1QGxpbnV4LWRlbGhpLm9yZz4gc2NocmllYjoKCj5PbiBUdWVzZGF5IDA0IFNlcCAyMDEyLCBL ZWl0aCBCdWNrIHdyb3RlOgo+PiBJJ20gZXhwZXJpZW5jaW5nIHNvbWUgc2V2ZXJlIHBlcmZvcm1h bmNlIGlzc3VlcyBydW5uaW5nIFhlbiA0LjAuMQo+PiB3aXRoIGEgY2xlYW5seS1pbnN0YWxsZWQg RGViaWFuIDYgZG9tMC4gIFByaW9yIHRvIGluc3RhbGxhdGlvbiwgdGhlCj4+IG1hY2hpbmUncyBw ZXJmb3JtYW5jZSB3YXMgZmluZSwgYnV0IGFmdGVyIGluc3RhbGxhdGlvbiBib290aW5nIHRha2Vz Cj4+IGFueXdoZXJlIGZyb20gNSB0byAyMCB0aW1lcyBsb25nZXIsIHByb2Nlc3NlcyB0YWtlIGEg bG9uZyB0aW1lIHRvCj4+IHN0YXJ0LCBhbmQgU1NIIGxhZ3MuICBObyBkb21VcyBhcmUgcnVubmlu ZyAob3IgaGF2ZSBiZWVuIGNyZWF0ZWQKPj4geWV0KS4gIEkgY2FuIHN3aXRjaCBiYWNrIHRvIHJ1 bm5pbmcgd2l0aG91dCBYZW4gKGJ1dCBzdGlsbCB1c2luZyB0aGUKPj4gWGVuLWNvbXBhdGlibGUg a2VybmVsKSBhbmQgdGhlIHBlcmZvcm1hbmNlIHByb2JsZW1zIGRpc2FwcGVhci4KPgo+UHJvYmFi bHkgYSBzdHVwaWQgcXVlc3Rpb24sIGJ1dCBzb21ldGltZSB3ZSBtaXNzIHRoZSBvYnZpb3VzOiBk aWQgeW91IAo+bWFrZSBhbnkgbmV0d29ya2luZyBjaGFuZ2VzPyAgU3BlY2lmaWNhbGx5LCBjb3Vs ZCB0aGlzIHByb2JsZW0gYmUgZHVlCj50byAKPm5vdCBiZWluZyBhYmxlIHRvIHJldmVyc2UgcmVz b2x2ZSBJUCBhZGRyZXNzZXMgb24geW91ciBtYWNoaW5lPwo+Cj5SZWdhcmRzLAo+Cj4tLSBSYWoK Pi0tIAo+UmFqIE1hdGh1ciAgICAgICAgICAgICAgICAgICAgICAgICAgfHwgcmFqdUBrYW5kYWxh eWEub3JnICAgfHwgR1BHOgo+aHR0cDovL290aGVyb25lcGVyY2VudC5ibG9nc3BvdC5jb20gfHwg aHR0cDovL2thbmRhbGF5YS5vcmcgfHwgQ0M2OAo+SXQgaXMgdGhlIG1pbmQgdGhhdCBtb3ZlcyAg ICAgICAgICAgfHwgaHR0cDovL3NjaGl6b2lkLmluICAgfHwgRDE3Rgo+Cj5fX19fX19fX19fX19f X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fXwoKLS0gCk5pZWxzIERldHRlbmJhY2gKU3lu ZGljYXQgSVQmSW50ZXJuZXQKaHR0cDovL3d3dy5zeW5kaWNhdC5jb20KCgpfX19fX19fX19fX19f X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fXwpYZW4tdXNlcnMgbWFpbGluZyBsaXN0 Clhlbi11c2Vyc0BsaXN0cy54ZW4ub3JnCmh0dHA6Ly9saXN0cy54ZW4ub3JnL3hlbi11c2Vycw== From xen-users-bounces@lists.xen.org Tue Sep 04 07:07:03 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Tue, 04 Sep 2012 07:07:03 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1T8nD8-0001U0-07; Tue, 04 Sep 2012 07:06:10 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1T8nD6-0001Tk-I3 for xen-users@lists.xen.org; Tue, 04 Sep 2012 07:06:08 +0000 Received: from [85.158.143.35:47313] by server-2.bemta-4.messagelabs.com id 7D/CB-21239-F58A5405; Tue, 04 Sep 2012 07:06:07 +0000 X-Env-Sender: lists+xen@internecto.net X-Msg-Ref: server-2.tower-21.messagelabs.com!1346742364!5591237!1 X-Originating-IP: [176.9.245.29] X-SpamReason: No, hits=0.0 required=7.0 tests= X-StarScan-Received: X-StarScan-Version: 6.6.1.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 31505 invoked from network); 4 Sep 2012 07:06:04 -0000 Received: from polaris.internecto.net (HELO mx1.internecto.net) (176.9.245.29) by server-2.tower-21.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 4 Sep 2012 07:06:04 -0000 Received: from localhost (localhost [127.0.0.1]) by mx1.internecto.net (Postfix) with ESMTP id DA344A02EF; Tue, 4 Sep 2012 07:06:03 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at mail.internecto.net Received: from mx1.internecto.net ([127.0.0.1]) by localhost (mail.polaris.internecto.net [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 8HVgjEBzbH5J; Tue, 4 Sep 2012 07:06:03 +0000 (UTC) Received: from internecto.net (5ED4FDEB.cm-7-5d.dynamic.ziggo.nl [94.212.253.235]) (using TLSv1 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (Client did not present a certificate) (Authenticated sender: lists@internecto.net) by mx1.internecto.net (Postfix) with ESMTPSA id 50549A0089; Tue, 4 Sep 2012 07:06:03 +0000 (UTC) Date: Tue, 4 Sep 2012 09:06:01 +0200 From: Mark van Dijk To: Ian Campbell Message-ID: <20120904090601.77377684@internecto.net> In-Reply-To: <1346665360.25864.2.camel@zakaz.uk.xensource.com> References: <1346665360.25864.2.camel@zakaz.uk.xensource.com> Organization: Internecto SIS X-Mailer: Claws Mail 3.8.0 (GTK+ 2.24.10; x86_64-pc-linux-gnu) Mime-Version: 1.0 Cc: xen-users@lists.xen.org, xen-devel Subject: Re: [Xen-users] Xen 4.2.0 Release Plan / TODO X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org Good morning, I realise I'm probably too late, but if it's trivial then maybe it is possible to implement an 'xl reset vmname' function before the final release. Or is this not as trivial as I think it is? -- Stay in touch, Mark van Dijk. ,--------------------------------- ----------------------------' Tue Sep 04 07:04 UTC 2012 Today is Boomtime, the 28th day of Bureaucracy in the YOLD 3178 _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Tue Sep 04 07:07:03 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Tue, 04 Sep 2012 07:07:03 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1T8nD8-0001U0-07; Tue, 04 Sep 2012 07:06:10 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1T8nD6-0001Tk-I3 for xen-users@lists.xen.org; Tue, 04 Sep 2012 07:06:08 +0000 Received: from [85.158.143.35:47313] by server-2.bemta-4.messagelabs.com id 7D/CB-21239-F58A5405; Tue, 04 Sep 2012 07:06:07 +0000 X-Env-Sender: lists+xen@internecto.net X-Msg-Ref: server-2.tower-21.messagelabs.com!1346742364!5591237!1 X-Originating-IP: [176.9.245.29] X-SpamReason: No, hits=0.0 required=7.0 tests= X-StarScan-Received: X-StarScan-Version: 6.6.1.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 31505 invoked from network); 4 Sep 2012 07:06:04 -0000 Received: from polaris.internecto.net (HELO mx1.internecto.net) (176.9.245.29) by server-2.tower-21.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 4 Sep 2012 07:06:04 -0000 Received: from localhost (localhost [127.0.0.1]) by mx1.internecto.net (Postfix) with ESMTP id DA344A02EF; Tue, 4 Sep 2012 07:06:03 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at mail.internecto.net Received: from mx1.internecto.net ([127.0.0.1]) by localhost (mail.polaris.internecto.net [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 8HVgjEBzbH5J; Tue, 4 Sep 2012 07:06:03 +0000 (UTC) Received: from internecto.net (5ED4FDEB.cm-7-5d.dynamic.ziggo.nl [94.212.253.235]) (using TLSv1 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (Client did not present a certificate) (Authenticated sender: lists@internecto.net) by mx1.internecto.net (Postfix) with ESMTPSA id 50549A0089; Tue, 4 Sep 2012 07:06:03 +0000 (UTC) Date: Tue, 4 Sep 2012 09:06:01 +0200 From: Mark van Dijk To: Ian Campbell Message-ID: <20120904090601.77377684@internecto.net> In-Reply-To: <1346665360.25864.2.camel@zakaz.uk.xensource.com> References: <1346665360.25864.2.camel@zakaz.uk.xensource.com> Organization: Internecto SIS X-Mailer: Claws Mail 3.8.0 (GTK+ 2.24.10; x86_64-pc-linux-gnu) Mime-Version: 1.0 Cc: xen-users@lists.xen.org, xen-devel Subject: Re: [Xen-users] Xen 4.2.0 Release Plan / TODO X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org Good morning, I realise I'm probably too late, but if it's trivial then maybe it is possible to implement an 'xl reset vmname' function before the final release. Or is this not as trivial as I think it is? -- Stay in touch, Mark van Dijk. ,--------------------------------- ----------------------------' Tue Sep 04 07:04 UTC 2012 Today is Boomtime, the 28th day of Bureaucracy in the YOLD 3178 _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Tue Sep 04 07:32:04 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Tue, 04 Sep 2012 07:32:04 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1T8nbN-0002A5-G6; Tue, 04 Sep 2012 07:31:13 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1T8nbL-00029m-BO for xen-users@lists.xen.org; Tue, 04 Sep 2012 07:31:11 +0000 Received: from [85.158.139.83:54624] by server-7.bemta-5.messagelabs.com id 03/EF-19703-E3EA5405; Tue, 04 Sep 2012 07:31:10 +0000 X-Env-Sender: Ian.Campbell@citrix.com X-Msg-Ref: server-3.tower-182.messagelabs.com!1346743869!28394376!1 X-Originating-IP: [62.200.22.115] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogNjIuMjAwLjIyLjExNSA9PiAxMTE2MDc=\n X-StarScan-Received: X-StarScan-Version: 6.6.1.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 32220 invoked from network); 4 Sep 2012 07:31:09 -0000 Received: from smtp.ctxuk.citrix.com (HELO SMTP.EU.CITRIX.COM) (62.200.22.115) by server-3.tower-182.messagelabs.com with RC4-SHA encrypted SMTP; 4 Sep 2012 07:31:09 -0000 X-IronPort-AV: E=Sophos;i="4.80,365,1344211200"; d="scan'208";a="14327530" Received: from lonpmailmx01.citrite.net ([10.30.203.162]) by LONPIPO01.EU.CITRIX.COM with ESMTP/TLS/RC4-MD5; 04 Sep 2012 07:31:08 +0000 Received: from [127.0.0.1] (10.80.16.67) by smtprelay.citrix.com (10.30.203.162) with Microsoft SMTP Server id 8.3.279.1; Tue, 4 Sep 2012 08:31:08 +0100 Message-ID: <1346743867.10570.2.camel@dagon.hellion.org.uk> From: Ian Campbell To: Mark van Dijk Date: Tue, 4 Sep 2012 08:31:07 +0100 In-Reply-To: <20120904090601.77377684@internecto.net> References: <1346665360.25864.2.camel@zakaz.uk.xensource.com> <20120904090601.77377684@internecto.net> Organization: Citrix Systems, Inc. X-Mailer: Evolution 3.4.3-1 MIME-Version: 1.0 Cc: "xen-users@lists.xen.org" , xen-devel Subject: Re: [Xen-users] Xen 4.2.0 Release Plan / TODO X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org On Tue, 2012-09-04 at 08:06 +0100, Mark van Dijk wrote: > Good morning, > > I realise I'm probably too late, but if it's trivial then maybe it is > possible to implement an 'xl reset vmname' function before the final > release. > > Or is this not as trivial as I think it is? What is it supposed to do? Ian. _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Tue Sep 04 07:32:04 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Tue, 04 Sep 2012 07:32:04 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1T8nbN-0002A5-G6; Tue, 04 Sep 2012 07:31:13 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1T8nbL-00029m-BO for xen-users@lists.xen.org; Tue, 04 Sep 2012 07:31:11 +0000 Received: from [85.158.139.83:54624] by server-7.bemta-5.messagelabs.com id 03/EF-19703-E3EA5405; Tue, 04 Sep 2012 07:31:10 +0000 X-Env-Sender: Ian.Campbell@citrix.com X-Msg-Ref: server-3.tower-182.messagelabs.com!1346743869!28394376!1 X-Originating-IP: [62.200.22.115] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogNjIuMjAwLjIyLjExNSA9PiAxMTE2MDc=\n X-StarScan-Received: X-StarScan-Version: 6.6.1.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 32220 invoked from network); 4 Sep 2012 07:31:09 -0000 Received: from smtp.ctxuk.citrix.com (HELO SMTP.EU.CITRIX.COM) (62.200.22.115) by server-3.tower-182.messagelabs.com with RC4-SHA encrypted SMTP; 4 Sep 2012 07:31:09 -0000 X-IronPort-AV: E=Sophos;i="4.80,365,1344211200"; d="scan'208";a="14327530" Received: from lonpmailmx01.citrite.net ([10.30.203.162]) by LONPIPO01.EU.CITRIX.COM with ESMTP/TLS/RC4-MD5; 04 Sep 2012 07:31:08 +0000 Received: from [127.0.0.1] (10.80.16.67) by smtprelay.citrix.com (10.30.203.162) with Microsoft SMTP Server id 8.3.279.1; Tue, 4 Sep 2012 08:31:08 +0100 Message-ID: <1346743867.10570.2.camel@dagon.hellion.org.uk> From: Ian Campbell To: Mark van Dijk Date: Tue, 4 Sep 2012 08:31:07 +0100 In-Reply-To: <20120904090601.77377684@internecto.net> References: <1346665360.25864.2.camel@zakaz.uk.xensource.com> <20120904090601.77377684@internecto.net> Organization: Citrix Systems, Inc. X-Mailer: Evolution 3.4.3-1 MIME-Version: 1.0 Cc: "xen-users@lists.xen.org" , xen-devel Subject: Re: [Xen-users] Xen 4.2.0 Release Plan / TODO X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org On Tue, 2012-09-04 at 08:06 +0100, Mark van Dijk wrote: > Good morning, > > I realise I'm probably too late, but if it's trivial then maybe it is > possible to implement an 'xl reset vmname' function before the final > release. > > Or is this not as trivial as I think it is? What is it supposed to do? Ian. _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Tue Sep 04 07:35:15 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Tue, 04 Sep 2012 07:35:15 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1T8nee-0002TB-PK; Tue, 04 Sep 2012 07:34:36 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1T8nec-0002Sb-Ny for xen-users@lists.xen.org; Tue, 04 Sep 2012 07:34:34 +0000 Received: from [85.158.139.83:29107] by server-9.bemta-5.messagelabs.com id 5B/6A-20529-90FA5405; Tue, 04 Sep 2012 07:34:33 +0000 X-Env-Sender: cdelorme@gmail.com X-Msg-Ref: server-8.tower-182.messagelabs.com!1346744071!17138312!1 X-Originating-IP: [209.85.214.173] X-SpamReason: No, hits=0.9 required=7.0 tests=HTML_40_50,HTML_MESSAGE, ML_RADAR_SPEW_LINKS_14,RCVD_BY_IP,spamassassin: X-StarScan-Received: X-StarScan-Version: 6.6.1.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 2237 invoked from network); 4 Sep 2012 07:34:32 -0000 Received: from mail-ob0-f173.google.com (HELO mail-ob0-f173.google.com) (209.85.214.173) by server-8.tower-182.messagelabs.com with RC4-SHA encrypted SMTP; 4 Sep 2012 07:34:32 -0000 Received: by obbta14 with SMTP id ta14so13683510obb.32 for ; Tue, 04 Sep 2012 00:34:30 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=Yl2VNIJXO2hBbzyzxaXPafnu/SdZmw/XtyMjFL9Bw0s=; b=YiSyuvlKRvFaubW6Dk2dDzOXrWFqzNfEUJwkWhxUqHMMU5xR/V8cijFBPEsXGXfrya AM3JFV673c2KTbzxMXozOjzdSMY3Ndro5KpTkUrXvNFoXbTo3OCynIDj3CLVf487dYOZ 0sRjDh5Qs6JisnS3VvLpWMJiykAKZWvp69gz47Wab0JvZOLe33y3LDima5X0EHBfRmL5 IXLjbHnZlHGe0RcnYNK+E6bLNaLnHuWtCMH21f5HgBNf8ck377tD9RATEorLnEz5sPvC FLvd0HIRzf0gdb7kIZgqQdrlQB0qmeszjS/fB6O9nYrJ1nlveU+ZuCSgyPkkvX6jetg2 BWYA== MIME-Version: 1.0 Received: by 10.60.170.229 with SMTP id ap5mr15430194oec.101.1346744070818; Tue, 04 Sep 2012 00:34:30 -0700 (PDT) Received: by 10.76.115.197 with HTTP; Tue, 4 Sep 2012 00:34:30 -0700 (PDT) In-Reply-To: <20120904090601.77377684@internecto.net> References: <1346665360.25864.2.camel@zakaz.uk.xensource.com> <20120904090601.77377684@internecto.net> Date: Tue, 4 Sep 2012 03:34:30 -0400 Message-ID: From: Casey DeLorme To: Mark van Dijk Cc: xen-users@lists.xen.org, Ian Campbell , xen-devel Subject: Re: [Xen-users] Xen 4.2.0 Release Plan / TODO X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============8211418857772106819==" Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org --===============8211418857772106819== Content-Type: multipart/alternative; boundary=bcaec54b4ac0f1cb1704c8db490b --bcaec54b4ac0f1cb1704c8db490b Content-Type: text/plain; charset=ISO-8859-1 Would reset be different than reboot? http://xenbits.xen.org/docs/unstable/man/xl.1.html On Tue, Sep 4, 2012 at 3:06 AM, Mark van Dijk wrote: > Good morning, > > I realise I'm probably too late, but if it's trivial then maybe it is > possible to implement an 'xl reset vmname' function before the final > release. > > Or is this not as trivial as I think it is? > > -- > Stay in touch, > Mark van Dijk. ,--------------------------------- > ----------------------------' Tue Sep 04 07:04 UTC 2012 > Today is Boomtime, the 28th day of Bureaucracy in the YOLD 3178 > > _______________________________________________ > Xen-users mailing list > Xen-users@lists.xen.org > http://lists.xen.org/xen-users > --bcaec54b4ac0f1cb1704c8db490b Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Would reset be different than reboot?
http://xenbits.xen.org/docs/unstable/man/xl.1= .html

On Tue, Sep 4, 2012 at 3:06 AM,= Mark van Dijk <lists+xen@internecto.net> wrote:
Good morning,

I realise I'm probably too late, but if it's trivial then maybe it = is
possible to implement an 'xl reset vmname' function before the fina= l
release.

Or is this not as trivial as I think it is?

--
Stay in touch,
Mark van Dijk. =A0 =A0 =A0 =A0 =A0 =A0 =A0 ,-------------------------------= --
----------------------------' =A0 =A0 =A0 =A0 Tue Sep 04 07:04 UTC 2012=
Today is Boomtime, the 28th day of Bureaucracy in the YOLD 3178

_______________________________________________
Xen-users mailing list
Xen-users@lists.xen.org
http://lists.x= en.org/xen-users

--bcaec54b4ac0f1cb1704c8db490b-- --===============8211418857772106819== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users --===============8211418857772106819==-- From xen-users-bounces@lists.xen.org Tue Sep 04 07:35:15 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Tue, 04 Sep 2012 07:35:15 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1T8nee-0002TB-PK; Tue, 04 Sep 2012 07:34:36 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1T8nec-0002Sb-Ny for xen-users@lists.xen.org; Tue, 04 Sep 2012 07:34:34 +0000 Received: from [85.158.139.83:29107] by server-9.bemta-5.messagelabs.com id 5B/6A-20529-90FA5405; Tue, 04 Sep 2012 07:34:33 +0000 X-Env-Sender: cdelorme@gmail.com X-Msg-Ref: server-8.tower-182.messagelabs.com!1346744071!17138312!1 X-Originating-IP: [209.85.214.173] X-SpamReason: No, hits=0.9 required=7.0 tests=HTML_40_50,HTML_MESSAGE, ML_RADAR_SPEW_LINKS_14,RCVD_BY_IP,spamassassin: X-StarScan-Received: X-StarScan-Version: 6.6.1.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 2237 invoked from network); 4 Sep 2012 07:34:32 -0000 Received: from mail-ob0-f173.google.com (HELO mail-ob0-f173.google.com) (209.85.214.173) by server-8.tower-182.messagelabs.com with RC4-SHA encrypted SMTP; 4 Sep 2012 07:34:32 -0000 Received: by obbta14 with SMTP id ta14so13683510obb.32 for ; Tue, 04 Sep 2012 00:34:30 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=Yl2VNIJXO2hBbzyzxaXPafnu/SdZmw/XtyMjFL9Bw0s=; b=YiSyuvlKRvFaubW6Dk2dDzOXrWFqzNfEUJwkWhxUqHMMU5xR/V8cijFBPEsXGXfrya AM3JFV673c2KTbzxMXozOjzdSMY3Ndro5KpTkUrXvNFoXbTo3OCynIDj3CLVf487dYOZ 0sRjDh5Qs6JisnS3VvLpWMJiykAKZWvp69gz47Wab0JvZOLe33y3LDima5X0EHBfRmL5 IXLjbHnZlHGe0RcnYNK+E6bLNaLnHuWtCMH21f5HgBNf8ck377tD9RATEorLnEz5sPvC FLvd0HIRzf0gdb7kIZgqQdrlQB0qmeszjS/fB6O9nYrJ1nlveU+ZuCSgyPkkvX6jetg2 BWYA== MIME-Version: 1.0 Received: by 10.60.170.229 with SMTP id ap5mr15430194oec.101.1346744070818; Tue, 04 Sep 2012 00:34:30 -0700 (PDT) Received: by 10.76.115.197 with HTTP; Tue, 4 Sep 2012 00:34:30 -0700 (PDT) In-Reply-To: <20120904090601.77377684@internecto.net> References: <1346665360.25864.2.camel@zakaz.uk.xensource.com> <20120904090601.77377684@internecto.net> Date: Tue, 4 Sep 2012 03:34:30 -0400 Message-ID: From: Casey DeLorme To: Mark van Dijk Cc: xen-users@lists.xen.org, Ian Campbell , xen-devel Subject: Re: [Xen-users] Xen 4.2.0 Release Plan / TODO X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============8211418857772106819==" Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org --===============8211418857772106819== Content-Type: multipart/alternative; boundary=bcaec54b4ac0f1cb1704c8db490b --bcaec54b4ac0f1cb1704c8db490b Content-Type: text/plain; charset=ISO-8859-1 Would reset be different than reboot? http://xenbits.xen.org/docs/unstable/man/xl.1.html On Tue, Sep 4, 2012 at 3:06 AM, Mark van Dijk wrote: > Good morning, > > I realise I'm probably too late, but if it's trivial then maybe it is > possible to implement an 'xl reset vmname' function before the final > release. > > Or is this not as trivial as I think it is? > > -- > Stay in touch, > Mark van Dijk. ,--------------------------------- > ----------------------------' Tue Sep 04 07:04 UTC 2012 > Today is Boomtime, the 28th day of Bureaucracy in the YOLD 3178 > > _______________________________________________ > Xen-users mailing list > Xen-users@lists.xen.org > http://lists.xen.org/xen-users > --bcaec54b4ac0f1cb1704c8db490b Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Would reset be different than reboot?
http://xenbits.xen.org/docs/unstable/man/xl.1= .html

On Tue, Sep 4, 2012 at 3:06 AM,= Mark van Dijk <lists+xen@internecto.net> wrote:
Good morning,

I realise I'm probably too late, but if it's trivial then maybe it = is
possible to implement an 'xl reset vmname' function before the fina= l
release.

Or is this not as trivial as I think it is?

--
Stay in touch,
Mark van Dijk. =A0 =A0 =A0 =A0 =A0 =A0 =A0 ,-------------------------------= --
----------------------------' =A0 =A0 =A0 =A0 Tue Sep 04 07:04 UTC 2012=
Today is Boomtime, the 28th day of Bureaucracy in the YOLD 3178

_______________________________________________
Xen-users mailing list
Xen-users@lists.xen.org
http://lists.x= en.org/xen-users

--bcaec54b4ac0f1cb1704c8db490b-- --===============8211418857772106819== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users --===============8211418857772106819==-- From xen-users-bounces@lists.xen.org Tue Sep 04 08:12:43 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Tue, 04 Sep 2012 08:12:43 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1T8oEn-0004Hb-ND; Tue, 04 Sep 2012 08:11:57 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1T8oEn-0004HR-0V for xen-users@lists.xen.org; Tue, 04 Sep 2012 08:11:57 +0000 Received: from [85.158.143.35:60815] by server-2.bemta-4.messagelabs.com id D7/2C-21239-CC7B5405; Tue, 04 Sep 2012 08:11:56 +0000 X-Env-Sender: Ian.Campbell@citrix.com X-Msg-Ref: server-16.tower-21.messagelabs.com!1346746315!14013965!1 X-Originating-IP: [62.200.22.115] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogNjIuMjAwLjIyLjExNSA9PiAxMTE2MDc=\n X-StarScan-Received: X-StarScan-Version: 6.6.1.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 10213 invoked from network); 4 Sep 2012 08:11:55 -0000 Received: from smtp.eu.citrix.com (HELO SMTP.EU.CITRIX.COM) (62.200.22.115) by server-16.tower-21.messagelabs.com with RC4-SHA encrypted SMTP; 4 Sep 2012 08:11:55 -0000 X-IronPort-AV: E=Sophos;i="4.80,365,1344211200"; d="scan'208";a="14328372" Received: from lonpmailmx01.citrite.net ([10.30.203.162]) by LONPIPO01.EU.CITRIX.COM with ESMTP/TLS/RC4-MD5; 04 Sep 2012 08:11:38 +0000 Received: from [10.80.2.42] (10.80.2.42) by LONPMAILMX01.citrite.net (10.30.203.162) with Microsoft SMTP Server id 8.3.279.1; Tue, 4 Sep 2012 09:11:38 +0100 Message-ID: <1346746297.32462.37.camel@zakaz.uk.xensource.com> From: Ian Campbell To: Casey DeLorme Date: Tue, 4 Sep 2012 09:11:37 +0100 In-Reply-To: References: <9F8FD2B0-450A-4A6E-A929-BA240ED1D997@mbs-systems.net> Organization: Citrix Systems, Inc. X-Mailer: Evolution 3.4.3-1 MIME-Version: 1.0 Cc: "xen-users@lists.xen.org" , Maik Brauer Subject: Re: [Xen-users] Dom0 crashed when rebooting whilst DomU are running X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org Could you not top post please, it makes it rather hard to follow the flow of the conversation. On Mon, 2012-09-03 at 18:10 +0100, Casey DeLorme wrote: > As stated, you can alias shutdown to do exactly what you need, it can > be as simple as a series of hard-coded operations to a complex custom > shell script that parses your domains and closes each with feedback. Xen ships the "xendomains" initscript which can halt guest on shutdown as well as automatically start specific guests on boot. It can also be configured to suspend/resume them or (I think) migrate them away. For diagnosing the crash itself more details will be required than were provided in the original post. Please see http://wiki.xen.org/wiki/Reporting_Bugs_against_Xen for some guidance. At a minimum we would need a capture (serial console or photo) of the crash backtrace. Ian. _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Tue Sep 04 08:12:43 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Tue, 04 Sep 2012 08:12:43 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1T8oEn-0004Hb-ND; Tue, 04 Sep 2012 08:11:57 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1T8oEn-0004HR-0V for xen-users@lists.xen.org; Tue, 04 Sep 2012 08:11:57 +0000 Received: from [85.158.143.35:60815] by server-2.bemta-4.messagelabs.com id D7/2C-21239-CC7B5405; Tue, 04 Sep 2012 08:11:56 +0000 X-Env-Sender: Ian.Campbell@citrix.com X-Msg-Ref: server-16.tower-21.messagelabs.com!1346746315!14013965!1 X-Originating-IP: [62.200.22.115] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogNjIuMjAwLjIyLjExNSA9PiAxMTE2MDc=\n X-StarScan-Received: X-StarScan-Version: 6.6.1.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 10213 invoked from network); 4 Sep 2012 08:11:55 -0000 Received: from smtp.eu.citrix.com (HELO SMTP.EU.CITRIX.COM) (62.200.22.115) by server-16.tower-21.messagelabs.com with RC4-SHA encrypted SMTP; 4 Sep 2012 08:11:55 -0000 X-IronPort-AV: E=Sophos;i="4.80,365,1344211200"; d="scan'208";a="14328372" Received: from lonpmailmx01.citrite.net ([10.30.203.162]) by LONPIPO01.EU.CITRIX.COM with ESMTP/TLS/RC4-MD5; 04 Sep 2012 08:11:38 +0000 Received: from [10.80.2.42] (10.80.2.42) by LONPMAILMX01.citrite.net (10.30.203.162) with Microsoft SMTP Server id 8.3.279.1; Tue, 4 Sep 2012 09:11:38 +0100 Message-ID: <1346746297.32462.37.camel@zakaz.uk.xensource.com> From: Ian Campbell To: Casey DeLorme Date: Tue, 4 Sep 2012 09:11:37 +0100 In-Reply-To: References: <9F8FD2B0-450A-4A6E-A929-BA240ED1D997@mbs-systems.net> Organization: Citrix Systems, Inc. X-Mailer: Evolution 3.4.3-1 MIME-Version: 1.0 Cc: "xen-users@lists.xen.org" , Maik Brauer Subject: Re: [Xen-users] Dom0 crashed when rebooting whilst DomU are running X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org Could you not top post please, it makes it rather hard to follow the flow of the conversation. On Mon, 2012-09-03 at 18:10 +0100, Casey DeLorme wrote: > As stated, you can alias shutdown to do exactly what you need, it can > be as simple as a series of hard-coded operations to a complex custom > shell script that parses your domains and closes each with feedback. Xen ships the "xendomains" initscript which can halt guest on shutdown as well as automatically start specific guests on boot. It can also be configured to suspend/resume them or (I think) migrate them away. For diagnosing the crash itself more details will be required than were provided in the original post. Please see http://wiki.xen.org/wiki/Reporting_Bugs_against_Xen for some guidance. At a minimum we would need a capture (serial console or photo) of the crash backtrace. Ian. _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Tue Sep 04 08:18:32 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Tue, 04 Sep 2012 08:18:32 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1T8oKO-0004qI-4y; Tue, 04 Sep 2012 08:17:44 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1T8oKL-0004qB-SU for xen-users@lists.xen.org; Tue, 04 Sep 2012 08:17:41 +0000 Received: from [85.158.143.99:6932] by server-3.bemta-4.messagelabs.com id A2/3A-08232-529B5405; Tue, 04 Sep 2012 08:17:41 +0000 X-Env-Sender: Ian.Campbell@citrix.com X-Msg-Ref: server-16.tower-216.messagelabs.com!1346746647!17175470!1 X-Originating-IP: [62.200.22.115] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogNjIuMjAwLjIyLjExNSA9PiAxMTE2MDc=\n X-StarScan-Received: X-StarScan-Version: 6.6.1.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 9993 invoked from network); 4 Sep 2012 08:17:28 -0000 Received: from smtp.ctxuk.citrix.com (HELO SMTP.EU.CITRIX.COM) (62.200.22.115) by server-16.tower-216.messagelabs.com with RC4-SHA encrypted SMTP; 4 Sep 2012 08:17:28 -0000 X-IronPort-AV: E=Sophos;i="4.80,366,1344211200"; d="scan'208";a="14328522" Received: from lonpmailmx01.citrite.net ([10.30.203.162]) by LONPIPO01.EU.CITRIX.COM with ESMTP/TLS/RC4-MD5; 04 Sep 2012 08:16:18 +0000 Received: from [10.80.2.42] (10.80.2.42) by LONPMAILMX01.citrite.net (10.30.203.162) with Microsoft SMTP Server id 8.3.279.1; Tue, 4 Sep 2012 09:16:18 +0100 Message-ID: <1346746577.6712.0.camel@zakaz.uk.xensource.com> From: Ian Campbell To: maheen butt Date: Tue, 4 Sep 2012 09:16:17 +0100 In-Reply-To: <1346733523.60759.YahooMailNeo@web126003.mail.ne1.yahoo.com> References: <1346733523.60759.YahooMailNeo@web126003.mail.ne1.yahoo.com> Organization: Citrix Systems, Inc. X-Mailer: Evolution 3.4.3-1 MIME-Version: 1.0 Cc: "xen-users@lists.xen.org" Subject: Re: [Xen-users] Xen summit Videos X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org On Tue, 2012-09-04 at 05:38 +0100, maheen butt wrote: > Hi, > > When will Xen Summit 2012's Videos and presentation be available on xen.org? It usually takes some time to process and upload them, plus there were more conferences immediately after XenSummit (LPC and LinuxCon, at least) so everyone has likely been busy with those and the subsequent travel. Expect an announcement when they are ready. Ian. _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Tue Sep 04 08:18:32 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Tue, 04 Sep 2012 08:18:32 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1T8oKO-0004qI-4y; Tue, 04 Sep 2012 08:17:44 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1T8oKL-0004qB-SU for xen-users@lists.xen.org; Tue, 04 Sep 2012 08:17:41 +0000 Received: from [85.158.143.99:6932] by server-3.bemta-4.messagelabs.com id A2/3A-08232-529B5405; Tue, 04 Sep 2012 08:17:41 +0000 X-Env-Sender: Ian.Campbell@citrix.com X-Msg-Ref: server-16.tower-216.messagelabs.com!1346746647!17175470!1 X-Originating-IP: [62.200.22.115] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogNjIuMjAwLjIyLjExNSA9PiAxMTE2MDc=\n X-StarScan-Received: X-StarScan-Version: 6.6.1.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 9993 invoked from network); 4 Sep 2012 08:17:28 -0000 Received: from smtp.ctxuk.citrix.com (HELO SMTP.EU.CITRIX.COM) (62.200.22.115) by server-16.tower-216.messagelabs.com with RC4-SHA encrypted SMTP; 4 Sep 2012 08:17:28 -0000 X-IronPort-AV: E=Sophos;i="4.80,366,1344211200"; d="scan'208";a="14328522" Received: from lonpmailmx01.citrite.net ([10.30.203.162]) by LONPIPO01.EU.CITRIX.COM with ESMTP/TLS/RC4-MD5; 04 Sep 2012 08:16:18 +0000 Received: from [10.80.2.42] (10.80.2.42) by LONPMAILMX01.citrite.net (10.30.203.162) with Microsoft SMTP Server id 8.3.279.1; Tue, 4 Sep 2012 09:16:18 +0100 Message-ID: <1346746577.6712.0.camel@zakaz.uk.xensource.com> From: Ian Campbell To: maheen butt Date: Tue, 4 Sep 2012 09:16:17 +0100 In-Reply-To: <1346733523.60759.YahooMailNeo@web126003.mail.ne1.yahoo.com> References: <1346733523.60759.YahooMailNeo@web126003.mail.ne1.yahoo.com> Organization: Citrix Systems, Inc. X-Mailer: Evolution 3.4.3-1 MIME-Version: 1.0 Cc: "xen-users@lists.xen.org" Subject: Re: [Xen-users] Xen summit Videos X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org On Tue, 2012-09-04 at 05:38 +0100, maheen butt wrote: > Hi, > > When will Xen Summit 2012's Videos and presentation be available on xen.org? It usually takes some time to process and upload them, plus there were more conferences immediately after XenSummit (LPC and LinuxCon, at least) so everyone has likely been busy with those and the subsequent travel. Expect an announcement when they are ready. Ian. _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Tue Sep 04 08:38:34 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Tue, 04 Sep 2012 08:38:34 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1T8odw-0005mx-Ok; Tue, 04 Sep 2012 08:37:56 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1T8odv-0005mc-Fg for xen-users@lists.xen.org; Tue, 04 Sep 2012 08:37:55 +0000 Received: from [85.158.139.83:30807] by server-10.bemta-5.messagelabs.com id 26/F0-10969-2EDB5405; Tue, 04 Sep 2012 08:37:54 +0000 X-Env-Sender: lists+xen@internecto.net X-Msg-Ref: server-14.tower-182.messagelabs.com!1346747873!24161474!1 X-Originating-IP: [176.9.245.29] X-SpamReason: No, hits=0.0 required=7.0 tests= X-StarScan-Received: X-StarScan-Version: 6.6.1.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 7458 invoked from network); 4 Sep 2012 08:37:53 -0000 Received: from polaris.internecto.net (HELO mx1.internecto.net) (176.9.245.29) by server-14.tower-182.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 4 Sep 2012 08:37:53 -0000 Received: from localhost (localhost [127.0.0.1]) by mx1.internecto.net (Postfix) with ESMTP id B5FA9A02EF; Tue, 4 Sep 2012 08:37:52 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at mail.internecto.net Received: from mx1.internecto.net ([127.0.0.1]) by localhost (mail.polaris.internecto.net [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id vw8Xola+U6dl; Tue, 4 Sep 2012 08:37:52 +0000 (UTC) Received: from internecto.net (5ED4FDEB.cm-7-5d.dynamic.ziggo.nl [94.212.253.235]) (using TLSv1 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (Client did not present a certificate) (Authenticated sender: lists@internecto.net) by mx1.internecto.net (Postfix) with ESMTPSA id CFAF0A0089; Tue, 4 Sep 2012 08:37:51 +0000 (UTC) Date: Tue, 4 Sep 2012 10:37:50 +0200 From: Mark van Dijk To: Ian Campbell Message-ID: <20120904103750.112fb44d@internecto.net> In-Reply-To: <1346743867.10570.2.camel@dagon.hellion.org.uk> References: <1346665360.25864.2.camel@zakaz.uk.xensource.com> <20120904090601.77377684@internecto.net> <1346743867.10570.2.camel@dagon.hellion.org.uk> Organization: Internecto SIS X-Mailer: Claws Mail 3.8.0 (GTK+ 2.24.10; x86_64-pc-linux-gnu) Mime-Version: 1.0 Cc: xen-users@lists.xen.org, xen-devel Subject: Re: [Xen-users] Xen 4.2.0 Release Plan / TODO X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org >> I realise I'm probably too late, but if it's trivial then maybe it is >> possible to implement an 'xl reset vmname' function before the final >> release. >> >> Or is this not as trivial as I think it is? Ian Campbell wrote: > What is it supposed to do? Casey DeLorme wrote: > Would reset be different than reboot? > http://xenbits.xen.org/docs/unstable/man/xl.1.html The already implemented 'xl reboot' sends an instruction to the running VM. If that VM doesn't understand this type of call then xl tells you to try issuing 'xl reboot -F', which sends an ACPI reboot instruction. These are convenient commands to be issued to a running domain so they can properly shutdown. But today I found that these both do nothing when a domain is frozen, e.g. a windows bsod or a hard Linux crash. It looks to me like there is just one way to take care of that: (manually) destroy and recreate. Back when I used xm I remember using the 'xm reset' command that just simply emulates a manual press of the reset button. By coincidence, today I found xl lacks this command. In effect I think all it does is 'xl destroy', wait until the domain is properly released and then 'xl create' it again. This is a bit more convenient than manually issuing both commands because the time it takes to destroy a VM varies. So my request is just for convenience and this is why I called it trivial. Also because one could still issue something like 'xl destroy domain; sleep 30s; xl create domain'. (In fact, in my zsh shell env I wrote an xl function that is a wrapper to the xl binary. Another thing is that it allows me to do 'xl edit VMname' which issues e.g. 'vim /etc/xen/hosts/VMname'. And when I issue 'xl create VMname' it actually executes '/usr/sbin/xl create /etc/xen/hosts/VMname'. I like convenience; who doesn't? ) -- Stay in touch, Mark van Dijk. ,--------------------------------- ----------------------------' Tue Sep 04 08:23 UTC 2012 Today is Boomtime, the 28th day of Bureaucracy in the YOLD 3178 _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Tue Sep 04 08:38:34 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Tue, 04 Sep 2012 08:38:34 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1T8odw-0005mx-Ok; Tue, 04 Sep 2012 08:37:56 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1T8odv-0005mc-Fg for xen-users@lists.xen.org; Tue, 04 Sep 2012 08:37:55 +0000 Received: from [85.158.139.83:30807] by server-10.bemta-5.messagelabs.com id 26/F0-10969-2EDB5405; Tue, 04 Sep 2012 08:37:54 +0000 X-Env-Sender: lists+xen@internecto.net X-Msg-Ref: server-14.tower-182.messagelabs.com!1346747873!24161474!1 X-Originating-IP: [176.9.245.29] X-SpamReason: No, hits=0.0 required=7.0 tests= X-StarScan-Received: X-StarScan-Version: 6.6.1.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 7458 invoked from network); 4 Sep 2012 08:37:53 -0000 Received: from polaris.internecto.net (HELO mx1.internecto.net) (176.9.245.29) by server-14.tower-182.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 4 Sep 2012 08:37:53 -0000 Received: from localhost (localhost [127.0.0.1]) by mx1.internecto.net (Postfix) with ESMTP id B5FA9A02EF; Tue, 4 Sep 2012 08:37:52 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at mail.internecto.net Received: from mx1.internecto.net ([127.0.0.1]) by localhost (mail.polaris.internecto.net [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id vw8Xola+U6dl; Tue, 4 Sep 2012 08:37:52 +0000 (UTC) Received: from internecto.net (5ED4FDEB.cm-7-5d.dynamic.ziggo.nl [94.212.253.235]) (using TLSv1 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (Client did not present a certificate) (Authenticated sender: lists@internecto.net) by mx1.internecto.net (Postfix) with ESMTPSA id CFAF0A0089; Tue, 4 Sep 2012 08:37:51 +0000 (UTC) Date: Tue, 4 Sep 2012 10:37:50 +0200 From: Mark van Dijk To: Ian Campbell Message-ID: <20120904103750.112fb44d@internecto.net> In-Reply-To: <1346743867.10570.2.camel@dagon.hellion.org.uk> References: <1346665360.25864.2.camel@zakaz.uk.xensource.com> <20120904090601.77377684@internecto.net> <1346743867.10570.2.camel@dagon.hellion.org.uk> Organization: Internecto SIS X-Mailer: Claws Mail 3.8.0 (GTK+ 2.24.10; x86_64-pc-linux-gnu) Mime-Version: 1.0 Cc: xen-users@lists.xen.org, xen-devel Subject: Re: [Xen-users] Xen 4.2.0 Release Plan / TODO X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org >> I realise I'm probably too late, but if it's trivial then maybe it is >> possible to implement an 'xl reset vmname' function before the final >> release. >> >> Or is this not as trivial as I think it is? Ian Campbell wrote: > What is it supposed to do? Casey DeLorme wrote: > Would reset be different than reboot? > http://xenbits.xen.org/docs/unstable/man/xl.1.html The already implemented 'xl reboot' sends an instruction to the running VM. If that VM doesn't understand this type of call then xl tells you to try issuing 'xl reboot -F', which sends an ACPI reboot instruction. These are convenient commands to be issued to a running domain so they can properly shutdown. But today I found that these both do nothing when a domain is frozen, e.g. a windows bsod or a hard Linux crash. It looks to me like there is just one way to take care of that: (manually) destroy and recreate. Back when I used xm I remember using the 'xm reset' command that just simply emulates a manual press of the reset button. By coincidence, today I found xl lacks this command. In effect I think all it does is 'xl destroy', wait until the domain is properly released and then 'xl create' it again. This is a bit more convenient than manually issuing both commands because the time it takes to destroy a VM varies. So my request is just for convenience and this is why I called it trivial. Also because one could still issue something like 'xl destroy domain; sleep 30s; xl create domain'. (In fact, in my zsh shell env I wrote an xl function that is a wrapper to the xl binary. Another thing is that it allows me to do 'xl edit VMname' which issues e.g. 'vim /etc/xen/hosts/VMname'. And when I issue 'xl create VMname' it actually executes '/usr/sbin/xl create /etc/xen/hosts/VMname'. I like convenience; who doesn't? ) -- Stay in touch, Mark van Dijk. ,--------------------------------- ----------------------------' Tue Sep 04 08:23 UTC 2012 Today is Boomtime, the 28th day of Bureaucracy in the YOLD 3178 _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Tue Sep 04 08:52:47 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Tue, 04 Sep 2012 08:52:47 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1T8orb-0006QO-EJ; Tue, 04 Sep 2012 08:52:03 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1T8orZ-0006Q8-JC for xen-users@lists.xen.org; Tue, 04 Sep 2012 08:52:01 +0000 Received: from [85.158.138.51:24869] by server-3.bemta-3.messagelabs.com id 61/2E-21322-031C5405; Tue, 04 Sep 2012 08:52:00 +0000 X-Env-Sender: Ian.Campbell@citrix.com X-Msg-Ref: server-7.tower-174.messagelabs.com!1346748719!19586733!1 X-Originating-IP: [62.200.22.115] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogNjIuMjAwLjIyLjExNSA9PiAxMTE3MTg=\n X-StarScan-Received: X-StarScan-Version: 6.6.1.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 673 invoked from network); 4 Sep 2012 08:51:59 -0000 Received: from smtp.eu.citrix.com (HELO SMTP.EU.CITRIX.COM) (62.200.22.115) by server-7.tower-174.messagelabs.com with RC4-SHA encrypted SMTP; 4 Sep 2012 08:51:59 -0000 X-IronPort-AV: E=Sophos;i="4.80,366,1344211200"; d="scan'208";a="14329442" Received: from lonpmailmx01.citrite.net ([10.30.203.162]) by LONPIPO01.EU.CITRIX.COM with ESMTP/TLS/RC4-MD5; 04 Sep 2012 08:51:59 +0000 Received: from [10.80.2.42] (10.80.2.42) by LONPMAILMX01.citrite.net (10.30.203.162) with Microsoft SMTP Server id 8.3.279.1; Tue, 4 Sep 2012 09:51:59 +0100 Message-ID: <1346748717.6712.12.camel@zakaz.uk.xensource.com> From: Ian Campbell To: Mark van Dijk Date: Tue, 4 Sep 2012 09:51:57 +0100 In-Reply-To: <20120904103750.112fb44d@internecto.net> References: <1346665360.25864.2.camel@zakaz.uk.xensource.com> <20120904090601.77377684@internecto.net> <1346743867.10570.2.camel@dagon.hellion.org.uk> <20120904103750.112fb44d@internecto.net> Organization: Citrix Systems, Inc. X-Mailer: Evolution 3.4.3-1 MIME-Version: 1.0 Cc: "xen-users@lists.xen.org" , xen-devel Subject: Re: [Xen-users] Xen 4.2.0 Release Plan / TODO X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org On Tue, 2012-09-04 at 09:37 +0100, Mark van Dijk wrote: > Back when I used xm I remember using the 'xm reset' command that just > simply emulates a manual press of the reset button. By coincidence, > today I found xl lacks this command. In effect I think all it does is > 'xl destroy', wait until the domain is properly released and then 'xl > create' it again. This is a bit more convenient than manually issuing > both commands because the time it takes to destroy a VM varies. I can see how that would be useful. I think it is now too late for 4.2.0 (although it might depend on the patch) but if someone were to produce a patch for 4.3 we could consider a backport for 4.2.1. I think you would just need to expose a libxl function which ended up doing "xc_domain_shutdown(CTX->xch, domid, SHUTDOWN_reboot)". This would kill the domain and set its shutdown reason to SHUTDOWN_reboot which would signal the xl daemon monitoring the domain to restart it. Wire that libxl function up to xl reset (add it to xl_cmdtable.c, xl_cmdimpl.c and docs/man/xl.cfg.pod.1) and you are good to go, I think. Let me know if you want to give it a go and require more guidance. Ian. _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Tue Sep 04 08:52:47 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Tue, 04 Sep 2012 08:52:47 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1T8orb-0006QO-EJ; Tue, 04 Sep 2012 08:52:03 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1T8orZ-0006Q8-JC for xen-users@lists.xen.org; Tue, 04 Sep 2012 08:52:01 +0000 Received: from [85.158.138.51:24869] by server-3.bemta-3.messagelabs.com id 61/2E-21322-031C5405; Tue, 04 Sep 2012 08:52:00 +0000 X-Env-Sender: Ian.Campbell@citrix.com X-Msg-Ref: server-7.tower-174.messagelabs.com!1346748719!19586733!1 X-Originating-IP: [62.200.22.115] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogNjIuMjAwLjIyLjExNSA9PiAxMTE3MTg=\n X-StarScan-Received: X-StarScan-Version: 6.6.1.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 673 invoked from network); 4 Sep 2012 08:51:59 -0000 Received: from smtp.eu.citrix.com (HELO SMTP.EU.CITRIX.COM) (62.200.22.115) by server-7.tower-174.messagelabs.com with RC4-SHA encrypted SMTP; 4 Sep 2012 08:51:59 -0000 X-IronPort-AV: E=Sophos;i="4.80,366,1344211200"; d="scan'208";a="14329442" Received: from lonpmailmx01.citrite.net ([10.30.203.162]) by LONPIPO01.EU.CITRIX.COM with ESMTP/TLS/RC4-MD5; 04 Sep 2012 08:51:59 +0000 Received: from [10.80.2.42] (10.80.2.42) by LONPMAILMX01.citrite.net (10.30.203.162) with Microsoft SMTP Server id 8.3.279.1; Tue, 4 Sep 2012 09:51:59 +0100 Message-ID: <1346748717.6712.12.camel@zakaz.uk.xensource.com> From: Ian Campbell To: Mark van Dijk Date: Tue, 4 Sep 2012 09:51:57 +0100 In-Reply-To: <20120904103750.112fb44d@internecto.net> References: <1346665360.25864.2.camel@zakaz.uk.xensource.com> <20120904090601.77377684@internecto.net> <1346743867.10570.2.camel@dagon.hellion.org.uk> <20120904103750.112fb44d@internecto.net> Organization: Citrix Systems, Inc. X-Mailer: Evolution 3.4.3-1 MIME-Version: 1.0 Cc: "xen-users@lists.xen.org" , xen-devel Subject: Re: [Xen-users] Xen 4.2.0 Release Plan / TODO X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org On Tue, 2012-09-04 at 09:37 +0100, Mark van Dijk wrote: > Back when I used xm I remember using the 'xm reset' command that just > simply emulates a manual press of the reset button. By coincidence, > today I found xl lacks this command. In effect I think all it does is > 'xl destroy', wait until the domain is properly released and then 'xl > create' it again. This is a bit more convenient than manually issuing > both commands because the time it takes to destroy a VM varies. I can see how that would be useful. I think it is now too late for 4.2.0 (although it might depend on the patch) but if someone were to produce a patch for 4.3 we could consider a backport for 4.2.1. I think you would just need to expose a libxl function which ended up doing "xc_domain_shutdown(CTX->xch, domid, SHUTDOWN_reboot)". This would kill the domain and set its shutdown reason to SHUTDOWN_reboot which would signal the xl daemon monitoring the domain to restart it. Wire that libxl function up to xl reset (add it to xl_cmdtable.c, xl_cmdimpl.c and docs/man/xl.cfg.pod.1) and you are good to go, I think. Let me know if you want to give it a go and require more guidance. Ian. _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Tue Sep 04 09:01:08 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Tue, 04 Sep 2012 09:01:08 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1T8ozk-00072P-5m; Tue, 04 Sep 2012 09:00:28 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1T8ozh-00072I-MN for xen-users@lists.xen.org; Tue, 04 Sep 2012 09:00:26 +0000 Received: from [85.158.143.99:64451] by server-1.bemta-4.messagelabs.com id CA/41-12504-923C5405; Tue, 04 Sep 2012 09:00:25 +0000 X-Env-Sender: nd@syndicat.com X-Msg-Ref: server-5.tower-216.messagelabs.com!1346749223!28058241!1 X-Originating-IP: [62.146.89.62] X-SpamReason: No, hits=0.0 required=7.0 tests= X-StarScan-Received: X-StarScan-Version: 6.6.1.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 16160 invoked from network); 4 Sep 2012 09:00:23 -0000 Received: from ffm-dr1.syndicat.com (HELO ffm-dr1.syndicat.com) (62.146.89.62) by server-5.tower-216.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 4 Sep 2012 09:00:23 -0000 Received: from localhost.syndicat.com ([127.0.0.1] helo=localhost) by ffm-dr1.syndicat.com with esmtp (Syndicat.com PostHamster 8.1.4.76) (envelope-from ) id 1T8oze-0005O2-VI for xen-users@lists.xen.org; Tue, 04 Sep 2012 11:00:22 +0200 X-Virus-Scanned: amavisd-new at syndicat.com Received: from ffm-dr1.syndicat.com ([127.0.0.1]) by localhost (ffm-dr1.syndicat.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id jf3LwWlEfGpu for ; Tue, 4 Sep 2012 11:00:22 +0200 (CEST) Received: from p5dc3fa31.dip.t-dialin.net ([93.195.250.49] helo=gongo.localnet) by ffm-dr1.syndicat.com with esmtpsa (TLSv1:AES256-SHA:256) (Syndicat.com PostHamster 8.1.4.76) (envelope-from ) id 1T8oze-0001f0-Kf for xen-users@lists.xen.org; Tue, 04 Sep 2012 11:00:22 +0200 From: Niels Dettenbach To: xen-users@lists.xen.org Date: Tue, 04 Sep 2012 11:00:05 +0200 Message-ID: <1909678.1rKzGqToy9@gongo> Organization: Syndicat IT&Internet User-Agent: KMail/4.9 (Linux/3.5.0-niels; KDE/4.9.0; x86_64; ; ) In-Reply-To: <20120904103750.112fb44d@internecto.net> References: <1346665360.25864.2.camel@zakaz.uk.xensource.com> <1346743867.10570.2.camel@dagon.hellion.org.uk> <20120904103750.112fb44d@internecto.net> MIME-Version: 1.0 Subject: Re: [Xen-users] Xen 4.2.0 Release Plan / TODO X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============3457607378199742993==" Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org --===============3457607378199742993== Content-Type: multipart/signed; boundary="nextPart3365284.on2W9BADfc"; micalg="pgp-sha256"; protocol="application/pgp-signature" Content-Transfer-Encoding: 7Bit --nextPart3365284.on2W9BADfc Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="us-ascii" Am Dienstag, 4. September 2012, 10:37:50 schrieb Mark van Dijk: > (In fact, in my zsh shell env I wrote an xl function that is a wrapper > to the xl binary. Another thing is that it allows me to do 'xl edit > VMname' which issues e.g. 'vim /etc/xen/hosts/VMname'. And when I issue > 'xl create VMname' it actually executes '/usr/sbin/xl > create /etc/xen/hosts/VMname'. I like convenience; who doesn't? ) hmm, from my experience in many environments did not are "fixed" pathes or places for config files as i.e. in your /etc/xen/hosts/ (i.e. many people hold config files with other stuff in per domain directories etc.) - makes it hardly or even impossible to provide a generic "edit" or "create" natively without any other limitations - so it would be more or less "usual" that users create their own scripts or wrappers for their own environment or provide external / third party toolsets for such "typical applications". best regards, Niels. -- --- Niels Dettenbach Syndicat IT & Internet http://www.syndicat.com PGP: https://syndicat.com/pub_key.asc --- --nextPart3365284.on2W9BADfc Content-Type: application/pgp-signature; name="signature.asc" Content-Description: This is a digitally signed message part. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.19 (GNU/Linux) iQIcBAABCAAGBQJQRcMZAAoJEM78prARigUnC6AQAI3LWHepLxdjHvGeSk7zLY9p 5amFpYl41bGbZvPpjap1QWw2EPsp6vzfAEPtL4e5USqihLpP/tRHMUZVIgFI3WKn G+WA00qixsB/CdldR5CluEIPMgblDdIA5hqYiI4LGVxlNj9qnyuzC/MjhNR8HQjC Mf5PTC8CY3cGdaSxtcIIp7nMP/GDvIx2EFrydnvoStGihAv3Zzqjn0TG34ld+29r 4M3NB8ua0jIew/11tu/JH/z3EyrbeokNhBMov80l0ZTgcW1eVDs8yHhYhFS/YIaF 78SvNDgdY+bVBcuzpqmI58UCA0xY14AgxhPgqYs4yvDzSyvht5BEBaI7ljkCBy8t NO9bX535OlSpJl0ZpGeVAJcb+nw30bkZ3tYLWRXeQ81qGuwYqW23ledHvtPBnYyp H+a7JiPjYfcb17jQyhJe9bIk/Af/89maENRV/CaGHWACaJm0VSnbHOW0r9xfHgpP JpShpeaVJXMGlMY2juuRobAPzkRbnWC0GAImWVNi98rLTIrI07dcofrhSuAfj0Kf ayQu2+MQwpmGL/H5ozn3KWFppxYzoWxGE0r8rKUHWAzc0OQQfp3AjizCc3D09WD7 VW/m8qNaoYNA43HWVkIk2hwI0Gs7rPFBBQVlNrgJjCvp0NxUY8dBFq/dxSRfNDUF dVcuFZuyqUlLnbrk/TTl =iyL6 -----END PGP SIGNATURE----- --nextPart3365284.on2W9BADfc-- --===============3457607378199742993== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users --===============3457607378199742993==-- From xen-users-bounces@lists.xen.org Tue Sep 04 09:01:08 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Tue, 04 Sep 2012 09:01:08 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1T8ozk-00072P-5m; Tue, 04 Sep 2012 09:00:28 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1T8ozh-00072I-MN for xen-users@lists.xen.org; Tue, 04 Sep 2012 09:00:26 +0000 Received: from [85.158.143.99:64451] by server-1.bemta-4.messagelabs.com id CA/41-12504-923C5405; Tue, 04 Sep 2012 09:00:25 +0000 X-Env-Sender: nd@syndicat.com X-Msg-Ref: server-5.tower-216.messagelabs.com!1346749223!28058241!1 X-Originating-IP: [62.146.89.62] X-SpamReason: No, hits=0.0 required=7.0 tests= X-StarScan-Received: X-StarScan-Version: 6.6.1.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 16160 invoked from network); 4 Sep 2012 09:00:23 -0000 Received: from ffm-dr1.syndicat.com (HELO ffm-dr1.syndicat.com) (62.146.89.62) by server-5.tower-216.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 4 Sep 2012 09:00:23 -0000 Received: from localhost.syndicat.com ([127.0.0.1] helo=localhost) by ffm-dr1.syndicat.com with esmtp (Syndicat.com PostHamster 8.1.4.76) (envelope-from ) id 1T8oze-0005O2-VI for xen-users@lists.xen.org; Tue, 04 Sep 2012 11:00:22 +0200 X-Virus-Scanned: amavisd-new at syndicat.com Received: from ffm-dr1.syndicat.com ([127.0.0.1]) by localhost (ffm-dr1.syndicat.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id jf3LwWlEfGpu for ; Tue, 4 Sep 2012 11:00:22 +0200 (CEST) Received: from p5dc3fa31.dip.t-dialin.net ([93.195.250.49] helo=gongo.localnet) by ffm-dr1.syndicat.com with esmtpsa (TLSv1:AES256-SHA:256) (Syndicat.com PostHamster 8.1.4.76) (envelope-from ) id 1T8oze-0001f0-Kf for xen-users@lists.xen.org; Tue, 04 Sep 2012 11:00:22 +0200 From: Niels Dettenbach To: xen-users@lists.xen.org Date: Tue, 04 Sep 2012 11:00:05 +0200 Message-ID: <1909678.1rKzGqToy9@gongo> Organization: Syndicat IT&Internet User-Agent: KMail/4.9 (Linux/3.5.0-niels; KDE/4.9.0; x86_64; ; ) In-Reply-To: <20120904103750.112fb44d@internecto.net> References: <1346665360.25864.2.camel@zakaz.uk.xensource.com> <1346743867.10570.2.camel@dagon.hellion.org.uk> <20120904103750.112fb44d@internecto.net> MIME-Version: 1.0 Subject: Re: [Xen-users] Xen 4.2.0 Release Plan / TODO X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============3457607378199742993==" Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org --===============3457607378199742993== Content-Type: multipart/signed; boundary="nextPart3365284.on2W9BADfc"; micalg="pgp-sha256"; protocol="application/pgp-signature" Content-Transfer-Encoding: 7Bit --nextPart3365284.on2W9BADfc Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="us-ascii" Am Dienstag, 4. September 2012, 10:37:50 schrieb Mark van Dijk: > (In fact, in my zsh shell env I wrote an xl function that is a wrapper > to the xl binary. Another thing is that it allows me to do 'xl edit > VMname' which issues e.g. 'vim /etc/xen/hosts/VMname'. And when I issue > 'xl create VMname' it actually executes '/usr/sbin/xl > create /etc/xen/hosts/VMname'. I like convenience; who doesn't? ) hmm, from my experience in many environments did not are "fixed" pathes or places for config files as i.e. in your /etc/xen/hosts/ (i.e. many people hold config files with other stuff in per domain directories etc.) - makes it hardly or even impossible to provide a generic "edit" or "create" natively without any other limitations - so it would be more or less "usual" that users create their own scripts or wrappers for their own environment or provide external / third party toolsets for such "typical applications". best regards, Niels. -- --- Niels Dettenbach Syndicat IT & Internet http://www.syndicat.com PGP: https://syndicat.com/pub_key.asc --- --nextPart3365284.on2W9BADfc Content-Type: application/pgp-signature; name="signature.asc" Content-Description: This is a digitally signed message part. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.19 (GNU/Linux) iQIcBAABCAAGBQJQRcMZAAoJEM78prARigUnC6AQAI3LWHepLxdjHvGeSk7zLY9p 5amFpYl41bGbZvPpjap1QWw2EPsp6vzfAEPtL4e5USqihLpP/tRHMUZVIgFI3WKn G+WA00qixsB/CdldR5CluEIPMgblDdIA5hqYiI4LGVxlNj9qnyuzC/MjhNR8HQjC Mf5PTC8CY3cGdaSxtcIIp7nMP/GDvIx2EFrydnvoStGihAv3Zzqjn0TG34ld+29r 4M3NB8ua0jIew/11tu/JH/z3EyrbeokNhBMov80l0ZTgcW1eVDs8yHhYhFS/YIaF 78SvNDgdY+bVBcuzpqmI58UCA0xY14AgxhPgqYs4yvDzSyvht5BEBaI7ljkCBy8t NO9bX535OlSpJl0ZpGeVAJcb+nw30bkZ3tYLWRXeQ81qGuwYqW23ledHvtPBnYyp H+a7JiPjYfcb17jQyhJe9bIk/Af/89maENRV/CaGHWACaJm0VSnbHOW0r9xfHgpP JpShpeaVJXMGlMY2juuRobAPzkRbnWC0GAImWVNi98rLTIrI07dcofrhSuAfj0Kf ayQu2+MQwpmGL/H5ozn3KWFppxYzoWxGE0r8rKUHWAzc0OQQfp3AjizCc3D09WD7 VW/m8qNaoYNA43HWVkIk2hwI0Gs7rPFBBQVlNrgJjCvp0NxUY8dBFq/dxSRfNDUF dVcuFZuyqUlLnbrk/TTl =iyL6 -----END PGP SIGNATURE----- --nextPart3365284.on2W9BADfc-- --===============3457607378199742993== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users --===============3457607378199742993==-- From xen-users-bounces@lists.xen.org Tue Sep 04 14:25:22 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Tue, 04 Sep 2012 14:25:22 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1T8u2t-0001OT-9l; Tue, 04 Sep 2012 14:24:03 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1T8u2r-0001OO-Cy for xen-users@lists.xensource.com; Tue, 04 Sep 2012 14:24:01 +0000 Received: from [85.158.138.51:13085] by server-7.bemta-3.messagelabs.com id 97/62-32000-00F06405; Tue, 04 Sep 2012 14:24:00 +0000 X-Env-Sender: k@itoc.dk X-Msg-Ref: server-7.tower-174.messagelabs.com!1346768638!19674557!1 X-Originating-IP: [216.139.236.26] X-SpamReason: No, hits=0.0 required=7.0 tests= X-StarScan-Received: X-StarScan-Version: 6.6.1.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 24329 invoked from network); 4 Sep 2012 14:23:59 -0000 Received: from sam.nabble.com (HELO sam.nabble.com) (216.139.236.26) by server-7.tower-174.messagelabs.com with AES256-SHA encrypted SMTP; 4 Sep 2012 14:23:59 -0000 Received: from [192.168.236.26] (helo=sam.nabble.com) by sam.nabble.com with esmtp (Exim 4.72) (envelope-from ) id 1T8u2n-0005sb-AF for xen-users@lists.xensource.com; Tue, 04 Sep 2012 07:23:57 -0700 Date: Tue, 4 Sep 2012 07:23:57 -0700 (PDT) From: Kristoffer Harthing Egefelt To: xen-users@lists.xensource.com Message-ID: <1346768637276-5710961.post@n5.nabble.com> MIME-Version: 1.0 Subject: [Xen-users] blktap vs qemu backend X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org Hi, I'm trying to figure out if blktap or qemu is the best backend for raw images? Using xen4.2 and kernel 3.2 and 3.5 theres a lot of problems with blktap, hacking blktap, hanging devices, unbootable domUs (block device errors). Performance in the qemu backend actually seems to be quite ok, 5-20% slower than LVM though - but not that much slower than blktap. It seems that a userspace blktap3 is not coming soon (http://lists.xen.org/archives/html/xen-devel/2012-04/msg00583.html) so maybe one should just settle with qemu for now. - Anybody know where the source code for blktap3 is? - xl top does not show VBD stats for qemu devices - is this expected? Thanks. Regards Kristoffer -- View this message in context: http://xen.1045712.n5.nabble.com/blktap-vs-qemu-backend-tp5710961.html Sent from the Xen - User mailing list archive at Nabble.com. _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Tue Sep 04 14:25:22 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Tue, 04 Sep 2012 14:25:22 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1T8u2t-0001OT-9l; Tue, 04 Sep 2012 14:24:03 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1T8u2r-0001OO-Cy for xen-users@lists.xensource.com; Tue, 04 Sep 2012 14:24:01 +0000 Received: from [85.158.138.51:13085] by server-7.bemta-3.messagelabs.com id 97/62-32000-00F06405; Tue, 04 Sep 2012 14:24:00 +0000 X-Env-Sender: k@itoc.dk X-Msg-Ref: server-7.tower-174.messagelabs.com!1346768638!19674557!1 X-Originating-IP: [216.139.236.26] X-SpamReason: No, hits=0.0 required=7.0 tests= X-StarScan-Received: X-StarScan-Version: 6.6.1.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 24329 invoked from network); 4 Sep 2012 14:23:59 -0000 Received: from sam.nabble.com (HELO sam.nabble.com) (216.139.236.26) by server-7.tower-174.messagelabs.com with AES256-SHA encrypted SMTP; 4 Sep 2012 14:23:59 -0000 Received: from [192.168.236.26] (helo=sam.nabble.com) by sam.nabble.com with esmtp (Exim 4.72) (envelope-from ) id 1T8u2n-0005sb-AF for xen-users@lists.xensource.com; Tue, 04 Sep 2012 07:23:57 -0700 Date: Tue, 4 Sep 2012 07:23:57 -0700 (PDT) From: Kristoffer Harthing Egefelt To: xen-users@lists.xensource.com Message-ID: <1346768637276-5710961.post@n5.nabble.com> MIME-Version: 1.0 Subject: [Xen-users] blktap vs qemu backend X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org Hi, I'm trying to figure out if blktap or qemu is the best backend for raw images? Using xen4.2 and kernel 3.2 and 3.5 theres a lot of problems with blktap, hacking blktap, hanging devices, unbootable domUs (block device errors). Performance in the qemu backend actually seems to be quite ok, 5-20% slower than LVM though - but not that much slower than blktap. It seems that a userspace blktap3 is not coming soon (http://lists.xen.org/archives/html/xen-devel/2012-04/msg00583.html) so maybe one should just settle with qemu for now. - Anybody know where the source code for blktap3 is? - xl top does not show VBD stats for qemu devices - is this expected? Thanks. Regards Kristoffer -- View this message in context: http://xen.1045712.n5.nabble.com/blktap-vs-qemu-backend-tp5710961.html Sent from the Xen - User mailing list archive at Nabble.com. _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Wed Sep 05 02:52:55 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Wed, 05 Sep 2012 02:52:55 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1T95iM-0000FS-5w; Wed, 05 Sep 2012 02:51:38 +0000 Received: from mail27.messagelabs.com ([193.109.254.147]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1T95iJ-0000FC-GQ; Wed, 05 Sep 2012 02:51:35 +0000 X-Env-Sender: pasik@iki.fi X-Msg-Ref: server-11.tower-27.messagelabs.com!1346813488!2787250!1 X-Originating-IP: [192.89.123.25] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogMTkyLjg5LjEyMy4yNSA9PiA1MDIwMTE=\n X-StarScan-Received: X-StarScan-Version: 6.6.1.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 18652 invoked from network); 5 Sep 2012 02:51:29 -0000 Received: from smtp.tele.fi (HELO smtp.tele.fi) (192.89.123.25) by server-11.tower-27.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 5 Sep 2012 02:51:29 -0000 X-Originating-Ip: [194.89.68.22] Received: from ydin.reaktio.net (reaktio.net [194.89.68.22]) by smtp.tele.fi (Postfix) with ESMTP id 2836B11CE; Wed, 5 Sep 2012 05:51:28 +0300 (EEST) Received: by ydin.reaktio.net (Postfix, from userid 1001) id 0241E2005D; Wed, 5 Sep 2012 05:51:28 +0300 (EEST) Date: Wed, 5 Sep 2012 05:51:27 +0300 From: Pasi =?iso-8859-1?Q?K=E4rkk=E4inen?= To: Ian Campbell Message-ID: <20120905025127.GI8912@reaktio.net> References: <1346665360.25864.2.camel@zakaz.uk.xensource.com> MIME-Version: 1.0 Content-Disposition: inline In-Reply-To: <1346665360.25864.2.camel@zakaz.uk.xensource.com> User-Agent: Mutt/1.5.20 (2009-06-14) Cc: xen-users , xen-devel Subject: Re: [Xen-users] [Xen-devel] Xen 4.2.0 Release Plan / TODO X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org On Mon, Sep 03, 2012 at 10:42:40AM +0100, Ian Campbell wrote: > > tools, nice to have: > > * xl compatibility with xm: > * xl support for "monitor" command. I don't see it mentioned in xl.cfg docs. (the command to enable/disable access to the per-vm Qemu monitor/console from VNC, which is usually accessed with ctrl-alt-2). -- Pasi _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Wed Sep 05 02:52:55 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Wed, 05 Sep 2012 02:52:55 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1T95iM-0000FS-5w; Wed, 05 Sep 2012 02:51:38 +0000 Received: from mail27.messagelabs.com ([193.109.254.147]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1T95iJ-0000FC-GQ; Wed, 05 Sep 2012 02:51:35 +0000 X-Env-Sender: pasik@iki.fi X-Msg-Ref: server-11.tower-27.messagelabs.com!1346813488!2787250!1 X-Originating-IP: [192.89.123.25] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogMTkyLjg5LjEyMy4yNSA9PiA1MDIwMTE=\n X-StarScan-Received: X-StarScan-Version: 6.6.1.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 18652 invoked from network); 5 Sep 2012 02:51:29 -0000 Received: from smtp.tele.fi (HELO smtp.tele.fi) (192.89.123.25) by server-11.tower-27.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 5 Sep 2012 02:51:29 -0000 X-Originating-Ip: [194.89.68.22] Received: from ydin.reaktio.net (reaktio.net [194.89.68.22]) by smtp.tele.fi (Postfix) with ESMTP id 2836B11CE; Wed, 5 Sep 2012 05:51:28 +0300 (EEST) Received: by ydin.reaktio.net (Postfix, from userid 1001) id 0241E2005D; Wed, 5 Sep 2012 05:51:28 +0300 (EEST) Date: Wed, 5 Sep 2012 05:51:27 +0300 From: Pasi =?iso-8859-1?Q?K=E4rkk=E4inen?= To: Ian Campbell Message-ID: <20120905025127.GI8912@reaktio.net> References: <1346665360.25864.2.camel@zakaz.uk.xensource.com> MIME-Version: 1.0 Content-Disposition: inline In-Reply-To: <1346665360.25864.2.camel@zakaz.uk.xensource.com> User-Agent: Mutt/1.5.20 (2009-06-14) Cc: xen-users , xen-devel Subject: Re: [Xen-users] [Xen-devel] Xen 4.2.0 Release Plan / TODO X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org On Mon, Sep 03, 2012 at 10:42:40AM +0100, Ian Campbell wrote: > > tools, nice to have: > > * xl compatibility with xm: > * xl support for "monitor" command. I don't see it mentioned in xl.cfg docs. (the command to enable/disable access to the per-vm Qemu monitor/console from VNC, which is usually accessed with ctrl-alt-2). -- Pasi _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Wed Sep 05 03:58:42 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Wed, 05 Sep 2012 03:58:42 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1T96k4-00019O-Dw; Wed, 05 Sep 2012 03:57:28 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1T96k3-00019J-OG for xen-users@lists.xen.org; Wed, 05 Sep 2012 03:57:27 +0000 Received: from [85.158.143.35:28540] by server-3.bemta-4.messagelabs.com id 74/71-08232-6ADC6405; Wed, 05 Sep 2012 03:57:26 +0000 X-Env-Sender: umarzuki@gmail.com X-Msg-Ref: server-13.tower-21.messagelabs.com!1346817445!15326199!1 X-Originating-IP: [74.125.82.51] X-SpamReason: No, hits=0.3 required=7.0 tests=ML_RADAR_SPEW_LINKS_14, RCVD_BY_IP,spamassassin: X-StarScan-Received: X-StarScan-Version: 6.6.1.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 25827 invoked from network); 5 Sep 2012 03:57:26 -0000 Received: from mail-wg0-f51.google.com (HELO mail-wg0-f51.google.com) (74.125.82.51) by server-13.tower-21.messagelabs.com with RC4-SHA encrypted SMTP; 5 Sep 2012 03:57:26 -0000 Received: by wgbed3 with SMTP id ed3so49693wgb.32 for ; Tue, 04 Sep 2012 20:57:25 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:date:message-id:subject:from:to:content-type; bh=STsOOkCfDl0pXRyDh6OfLWOwzyQXTzcYyj1sGj9GkKo=; b=rvoj3dGSclFymPAL84G1FGvRexJz0JjNm+my5Djlh/J8njWkG3BdjLILEI2k7ttbmO gVheU8cjpX2wuYRe0SrQ++uYDX4KDVdcGZDe4U6pQomowQcT9GHvXjzbOHyTTdlYCI+P K8cEGha8KBDsI2kSk4/JXZT2jXDCxTmIzVCSF39Y6H4ru0pudT/A4VwdbYrAlbpHRVUP IS2MbSb8NOywwvTHtHPsCfpiCFU2ykPbgrTfggt44zaBT8ESQWHgZrPT6I5jK2SvgPRF XLxOb2RqtpOPsEZtGf3Zsav96c/p96qN9+IIjnl9zGM5AtnxURSTpKThjYpYDw+mUsLe rH+g== MIME-Version: 1.0 Received: by 10.216.208.69 with SMTP id p47mr11582256weo.150.1346817445373; Tue, 04 Sep 2012 20:57:25 -0700 (PDT) Received: by 10.194.60.40 with HTTP; Tue, 4 Sep 2012 20:57:25 -0700 (PDT) Date: Wed, 5 Sep 2012 11:57:25 +0800 Message-ID: From: Umarzuki Mochlis To: xen-users@lists.xen.org Subject: [Xen-users] guest OS High Availability with local storage X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org hi, if I were to use Debian Squeeze as dom0 (3 servers) and install Xen hypervisor 4.0 on all of them, how would I achieve HA with only using local storage? has it ever been done before? -- Regards, Umarzuki Mochlis http://debmal.my _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Wed Sep 05 03:58:42 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Wed, 05 Sep 2012 03:58:42 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1T96k4-00019O-Dw; Wed, 05 Sep 2012 03:57:28 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1T96k3-00019J-OG for xen-users@lists.xen.org; Wed, 05 Sep 2012 03:57:27 +0000 Received: from [85.158.143.35:28540] by server-3.bemta-4.messagelabs.com id 74/71-08232-6ADC6405; Wed, 05 Sep 2012 03:57:26 +0000 X-Env-Sender: umarzuki@gmail.com X-Msg-Ref: server-13.tower-21.messagelabs.com!1346817445!15326199!1 X-Originating-IP: [74.125.82.51] X-SpamReason: No, hits=0.3 required=7.0 tests=ML_RADAR_SPEW_LINKS_14, RCVD_BY_IP,spamassassin: X-StarScan-Received: X-StarScan-Version: 6.6.1.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 25827 invoked from network); 5 Sep 2012 03:57:26 -0000 Received: from mail-wg0-f51.google.com (HELO mail-wg0-f51.google.com) (74.125.82.51) by server-13.tower-21.messagelabs.com with RC4-SHA encrypted SMTP; 5 Sep 2012 03:57:26 -0000 Received: by wgbed3 with SMTP id ed3so49693wgb.32 for ; Tue, 04 Sep 2012 20:57:25 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:date:message-id:subject:from:to:content-type; bh=STsOOkCfDl0pXRyDh6OfLWOwzyQXTzcYyj1sGj9GkKo=; b=rvoj3dGSclFymPAL84G1FGvRexJz0JjNm+my5Djlh/J8njWkG3BdjLILEI2k7ttbmO gVheU8cjpX2wuYRe0SrQ++uYDX4KDVdcGZDe4U6pQomowQcT9GHvXjzbOHyTTdlYCI+P K8cEGha8KBDsI2kSk4/JXZT2jXDCxTmIzVCSF39Y6H4ru0pudT/A4VwdbYrAlbpHRVUP IS2MbSb8NOywwvTHtHPsCfpiCFU2ykPbgrTfggt44zaBT8ESQWHgZrPT6I5jK2SvgPRF XLxOb2RqtpOPsEZtGf3Zsav96c/p96qN9+IIjnl9zGM5AtnxURSTpKThjYpYDw+mUsLe rH+g== MIME-Version: 1.0 Received: by 10.216.208.69 with SMTP id p47mr11582256weo.150.1346817445373; Tue, 04 Sep 2012 20:57:25 -0700 (PDT) Received: by 10.194.60.40 with HTTP; Tue, 4 Sep 2012 20:57:25 -0700 (PDT) Date: Wed, 5 Sep 2012 11:57:25 +0800 Message-ID: From: Umarzuki Mochlis To: xen-users@lists.xen.org Subject: [Xen-users] guest OS High Availability with local storage X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org hi, if I were to use Debian Squeeze as dom0 (3 servers) and install Xen hypervisor 4.0 on all of them, how would I achieve HA with only using local storage? has it ever been done before? -- Regards, Umarzuki Mochlis http://debmal.my _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Wed Sep 05 04:46:11 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Wed, 05 Sep 2012 04:46:11 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1T97U4-0001i5-Pn; Wed, 05 Sep 2012 04:45:00 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1T97U2-0001hw-PV for xen-users@lists.xen.org; Wed, 05 Sep 2012 04:44:58 +0000 Received: from [85.158.139.83:28650] by server-12.bemta-5.messagelabs.com id 7F/3B-18300-9C8D6405; Wed, 05 Sep 2012 04:44:57 +0000 X-Env-Sender: fajar@fajar.net X-Msg-Ref: server-11.tower-182.messagelabs.com!1346820296!21383833!1 X-Originating-IP: [209.85.223.173] X-SpamReason: No, hits=0.3 required=7.0 tests=RCVD_BY_IP X-StarScan-Received: X-StarScan-Version: 6.6.1.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 18102 invoked from network); 5 Sep 2012 04:44:57 -0000 Received: from mail-ie0-f173.google.com (HELO mail-ie0-f173.google.com) (209.85.223.173) by server-11.tower-182.messagelabs.com with RC4-SHA encrypted SMTP; 5 Sep 2012 04:44:57 -0000 Received: by iebc10 with SMTP id c10so272736ieb.32 for ; Tue, 04 Sep 2012 21:44:56 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:x-gm-message-state; bh=nvZcnqowHiLFsOCoGgwPR1teGWM5qlN+9+JxWHdj+U4=; b=MPrK2sgfhnumcMMxJO5WopYXBuZLBqJ/VPH6oDxyKbrm/Be748kfM8AZ2XLy05pQsd OlGPEFgS4+CkJyh9nvQ9+RIHsEB5oeap4yfSG82f64u1Ea2i0Moco+P/rfjl7rA6zzi3 pvkxoOcEvQvmEKKkPlHx+LkWCgnrjdua5PUFWV9KHdU5QABdUVPP1lLcjtfrfTo3An63 HBbYqv5O++v7i7u8RKoLTX1xD15atg5Eeha2e/hZzlrNi2vNPPZY71WxgkBntLhTl7tL OT1RwexAx+iD5sX/kwyHXnC/iWI3K5obx5vatUPGDLYsQd3QqUgbV7v4Mljof3KUQ9l3 1mbg== MIME-Version: 1.0 Received: by 10.60.30.132 with SMTP id s4mr16467218oeh.6.1346820295655; Tue, 04 Sep 2012 21:44:55 -0700 (PDT) Received: by 10.60.6.230 with HTTP; Tue, 4 Sep 2012 21:44:55 -0700 (PDT) In-Reply-To: References: Date: Wed, 5 Sep 2012 11:44:55 +0700 Message-ID: From: "Fajar A. Nugraha" To: Umarzuki Mochlis X-Gm-Message-State: ALoCoQkdhI6CUR6xBhb0uY3t0iQeKXM95EJprogD9hIHzC9q34dfVepvVh1fkyXPuLhMHQSx8rsl Cc: xen-users@lists.xen.org Subject: Re: [Xen-users] guest OS High Availability with local storage X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org On Wed, Sep 5, 2012 at 10:57 AM, Umarzuki Mochlis wrote: > hi, > > if I were to use Debian Squeeze as dom0 (3 servers) and install Xen > hypervisor 4.0 on all of them, how would I achieve HA with only using > local storage? You can't > has it ever been done before? The easiest way would be to use shared storage and some sort of cluster manager. So if it were me I'd use one node as SAN (e.g. with openindiana + nappit, or whatever iscsi-capable storage appliance of your choice) and the other two as compute nodes. The SAN becomes a single point of failure though (unless you can afford two storage nodes, but that's another story). If you don't have SAN, then to have a "shared" common storage you can use DRBD. AFAIK you can only have two nodes for primary-primary setup though. See https://alteeve.ca/w/Red_Hat_Cluster_Service_3_Tutorial for example (it uses KVM, but the concept should be similar). -- Fajar _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Wed Sep 05 04:46:11 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Wed, 05 Sep 2012 04:46:11 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1T97U4-0001i5-Pn; Wed, 05 Sep 2012 04:45:00 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1T97U2-0001hw-PV for xen-users@lists.xen.org; Wed, 05 Sep 2012 04:44:58 +0000 Received: from [85.158.139.83:28650] by server-12.bemta-5.messagelabs.com id 7F/3B-18300-9C8D6405; Wed, 05 Sep 2012 04:44:57 +0000 X-Env-Sender: fajar@fajar.net X-Msg-Ref: server-11.tower-182.messagelabs.com!1346820296!21383833!1 X-Originating-IP: [209.85.223.173] X-SpamReason: No, hits=0.3 required=7.0 tests=RCVD_BY_IP X-StarScan-Received: X-StarScan-Version: 6.6.1.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 18102 invoked from network); 5 Sep 2012 04:44:57 -0000 Received: from mail-ie0-f173.google.com (HELO mail-ie0-f173.google.com) (209.85.223.173) by server-11.tower-182.messagelabs.com with RC4-SHA encrypted SMTP; 5 Sep 2012 04:44:57 -0000 Received: by iebc10 with SMTP id c10so272736ieb.32 for ; Tue, 04 Sep 2012 21:44:56 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:x-gm-message-state; bh=nvZcnqowHiLFsOCoGgwPR1teGWM5qlN+9+JxWHdj+U4=; b=MPrK2sgfhnumcMMxJO5WopYXBuZLBqJ/VPH6oDxyKbrm/Be748kfM8AZ2XLy05pQsd OlGPEFgS4+CkJyh9nvQ9+RIHsEB5oeap4yfSG82f64u1Ea2i0Moco+P/rfjl7rA6zzi3 pvkxoOcEvQvmEKKkPlHx+LkWCgnrjdua5PUFWV9KHdU5QABdUVPP1lLcjtfrfTo3An63 HBbYqv5O++v7i7u8RKoLTX1xD15atg5Eeha2e/hZzlrNi2vNPPZY71WxgkBntLhTl7tL OT1RwexAx+iD5sX/kwyHXnC/iWI3K5obx5vatUPGDLYsQd3QqUgbV7v4Mljof3KUQ9l3 1mbg== MIME-Version: 1.0 Received: by 10.60.30.132 with SMTP id s4mr16467218oeh.6.1346820295655; Tue, 04 Sep 2012 21:44:55 -0700 (PDT) Received: by 10.60.6.230 with HTTP; Tue, 4 Sep 2012 21:44:55 -0700 (PDT) In-Reply-To: References: Date: Wed, 5 Sep 2012 11:44:55 +0700 Message-ID: From: "Fajar A. Nugraha" To: Umarzuki Mochlis X-Gm-Message-State: ALoCoQkdhI6CUR6xBhb0uY3t0iQeKXM95EJprogD9hIHzC9q34dfVepvVh1fkyXPuLhMHQSx8rsl Cc: xen-users@lists.xen.org Subject: Re: [Xen-users] guest OS High Availability with local storage X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org On Wed, Sep 5, 2012 at 10:57 AM, Umarzuki Mochlis wrote: > hi, > > if I were to use Debian Squeeze as dom0 (3 servers) and install Xen > hypervisor 4.0 on all of them, how would I achieve HA with only using > local storage? You can't > has it ever been done before? The easiest way would be to use shared storage and some sort of cluster manager. So if it were me I'd use one node as SAN (e.g. with openindiana + nappit, or whatever iscsi-capable storage appliance of your choice) and the other two as compute nodes. The SAN becomes a single point of failure though (unless you can afford two storage nodes, but that's another story). If you don't have SAN, then to have a "shared" common storage you can use DRBD. AFAIK you can only have two nodes for primary-primary setup though. See https://alteeve.ca/w/Red_Hat_Cluster_Service_3_Tutorial for example (it uses KVM, but the concept should be similar). -- Fajar _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Wed Sep 05 04:49:15 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Wed, 05 Sep 2012 04:49:15 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1T97XK-0001uy-0U; Wed, 05 Sep 2012 04:48:22 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1T94Gp-00087p-Qh for xen-users@lists.xen.org; Wed, 05 Sep 2012 01:19:07 +0000 Received: from [85.158.138.51:50006] by server-7.bemta-3.messagelabs.com id 71/D4-32000-A88A6405; Wed, 05 Sep 2012 01:19:06 +0000 X-Env-Sender: xtrusia@gmail.com X-Msg-Ref: server-5.tower-174.messagelabs.com!1346807944!28738483!1 X-Originating-IP: [209.85.160.45] X-SpamReason: No, hits=0.3 required=7.0 tests=ML_RADAR_SPEW_LINKS_14, RCVD_BY_IP,spamassassin: X-StarScan-Received: X-StarScan-Version: 6.6.1.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 19173 invoked from network); 5 Sep 2012 01:19:06 -0000 Received: from mail-pb0-f45.google.com (HELO mail-pb0-f45.google.com) (209.85.160.45) by server-5.tower-174.messagelabs.com with RC4-SHA encrypted SMTP; 5 Sep 2012 01:19:06 -0000 Received: by pbbjt11 with SMTP id jt11so74361pbb.32 for ; Tue, 04 Sep 2012 18:19:04 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=from:content-type:content-transfer-encoding:subject:message-id:date :to:mime-version:x-mailer; bh=YhtN7iOENzc52jK8pDIIJe4IOr4NtKAYW3SEkKs8yKs=; b=0hNCY79tE56WE7BVRLk2WFAtLBlH5Vh1ZhL+V+4gr56cyue27YRM7QpFQ3Kd8tM9Qy bO6PEyGqHSNAfrFzE5f97r/UCGvfeB3kRi2v7LC8TIIx1OWgN8jR0v6nEyl5zhxCH75D FXvEUW0AQ223zDnKeci5uMfgVSxNILsGRPOQVoskAAFEKKsoP5FZV8wT97SL4SO/J0ZU K12WCognPhq4sp0oOS9yjYirlUEjz6uRXhTaAcm+fCqdPl0d9tXqMZyq4ph2wI1zZcAS Se5nNfU2rPKhtylpj3amNe+nfR5j152P8hrRJ3ABa5MYqObHns2uLaAHlH3n26Etsh4v 6WVQ== Received: by 10.68.201.198 with SMTP id kc6mr49619152pbc.122.1346807944022; Tue, 04 Sep 2012 18:19:04 -0700 (PDT) Received: from [192.168.0.2] ([183.98.30.10]) by mx.google.com with ESMTPS id it6sm226750pbc.14.2012.09.04.18.19.01 (version=TLSv1/SSLv3 cipher=OTHER); Tue, 04 Sep 2012 18:19:02 -0700 (PDT) From: =?euc-kr?B?us6357Chtvc=?= Message-Id: <83719580-EC61-4E48-9A62-B0CC5CDDACC4@gmail.com> Date: Wed, 5 Sep 2012 10:18:59 +0900 To: xen-users@lists.xen.org Mime-Version: 1.0 (Mac OS X Mail 6.0 \(1486\)) X-Mailer: Apple Mail (2.1486) X-Mailman-Approved-At: Wed, 05 Sep 2012 04:48:18 +0000 Subject: [Xen-users] hang when umount right after write big data X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org it hangs when umount right after wite big data in dom0 i tried step like below mkdir mnt truncate --size 2G image.img mount -o loop image.img mnt cd mnt cp rootfs.tar.gz . tar -xvzf rootfs.tar.gz (this file size is around 1G ) cd .. umount mnt and it hangs if I try umount after i wait 30 seconds or more. it could be done. any opinion about this? it doesn't happened when i tried on linux machine not dom0 thanks _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Wed Sep 05 04:49:15 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Wed, 05 Sep 2012 04:49:15 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1T97XK-0001uy-0U; Wed, 05 Sep 2012 04:48:22 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1T94Gp-00087p-Qh for xen-users@lists.xen.org; Wed, 05 Sep 2012 01:19:07 +0000 Received: from [85.158.138.51:50006] by server-7.bemta-3.messagelabs.com id 71/D4-32000-A88A6405; Wed, 05 Sep 2012 01:19:06 +0000 X-Env-Sender: xtrusia@gmail.com X-Msg-Ref: server-5.tower-174.messagelabs.com!1346807944!28738483!1 X-Originating-IP: [209.85.160.45] X-SpamReason: No, hits=0.3 required=7.0 tests=ML_RADAR_SPEW_LINKS_14, RCVD_BY_IP,spamassassin: X-StarScan-Received: X-StarScan-Version: 6.6.1.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 19173 invoked from network); 5 Sep 2012 01:19:06 -0000 Received: from mail-pb0-f45.google.com (HELO mail-pb0-f45.google.com) (209.85.160.45) by server-5.tower-174.messagelabs.com with RC4-SHA encrypted SMTP; 5 Sep 2012 01:19:06 -0000 Received: by pbbjt11 with SMTP id jt11so74361pbb.32 for ; Tue, 04 Sep 2012 18:19:04 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=from:content-type:content-transfer-encoding:subject:message-id:date :to:mime-version:x-mailer; bh=YhtN7iOENzc52jK8pDIIJe4IOr4NtKAYW3SEkKs8yKs=; b=0hNCY79tE56WE7BVRLk2WFAtLBlH5Vh1ZhL+V+4gr56cyue27YRM7QpFQ3Kd8tM9Qy bO6PEyGqHSNAfrFzE5f97r/UCGvfeB3kRi2v7LC8TIIx1OWgN8jR0v6nEyl5zhxCH75D FXvEUW0AQ223zDnKeci5uMfgVSxNILsGRPOQVoskAAFEKKsoP5FZV8wT97SL4SO/J0ZU K12WCognPhq4sp0oOS9yjYirlUEjz6uRXhTaAcm+fCqdPl0d9tXqMZyq4ph2wI1zZcAS Se5nNfU2rPKhtylpj3amNe+nfR5j152P8hrRJ3ABa5MYqObHns2uLaAHlH3n26Etsh4v 6WVQ== Received: by 10.68.201.198 with SMTP id kc6mr49619152pbc.122.1346807944022; Tue, 04 Sep 2012 18:19:04 -0700 (PDT) Received: from [192.168.0.2] ([183.98.30.10]) by mx.google.com with ESMTPS id it6sm226750pbc.14.2012.09.04.18.19.01 (version=TLSv1/SSLv3 cipher=OTHER); Tue, 04 Sep 2012 18:19:02 -0700 (PDT) From: =?euc-kr?B?us6357Chtvc=?= Message-Id: <83719580-EC61-4E48-9A62-B0CC5CDDACC4@gmail.com> Date: Wed, 5 Sep 2012 10:18:59 +0900 To: xen-users@lists.xen.org Mime-Version: 1.0 (Mac OS X Mail 6.0 \(1486\)) X-Mailer: Apple Mail (2.1486) X-Mailman-Approved-At: Wed, 05 Sep 2012 04:48:18 +0000 Subject: [Xen-users] hang when umount right after write big data X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org it hangs when umount right after wite big data in dom0 i tried step like below mkdir mnt truncate --size 2G image.img mount -o loop image.img mnt cd mnt cp rootfs.tar.gz . tar -xvzf rootfs.tar.gz (this file size is around 1G ) cd .. umount mnt and it hangs if I try umount after i wait 30 seconds or more. it could be done. any opinion about this? it doesn't happened when i tried on linux machine not dom0 thanks _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Wed Sep 05 05:02:26 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Wed, 05 Sep 2012 05:02:26 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1T97kB-0002cj-JP; Wed, 05 Sep 2012 05:01:39 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1T97k9-0002ce-DJ for xen-users@lists.xen.org; Wed, 05 Sep 2012 05:01:37 +0000 Received: from [85.158.139.83:8920] by server-7.bemta-5.messagelabs.com id 11/F0-19703-0BCD6405; Wed, 05 Sep 2012 05:01:36 +0000 X-Env-Sender: theubaz@gmail.com X-Msg-Ref: server-2.tower-182.messagelabs.com!1346821294!28592306!1 X-Originating-IP: [209.85.216.52] X-SpamReason: No, hits=0.4 required=7.0 tests=HTML_30_40,HTML_MESSAGE, RCVD_BY_IP X-StarScan-Received: X-StarScan-Version: 6.6.1.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 1702 invoked from network); 5 Sep 2012 05:01:35 -0000 Received: from mail-qa0-f52.google.com (HELO mail-qa0-f52.google.com) (209.85.216.52) by server-2.tower-182.messagelabs.com with RC4-SHA encrypted SMTP; 5 Sep 2012 05:01:35 -0000 Received: by qabg14 with SMTP id g14so270058qab.11 for ; Tue, 04 Sep 2012 22:01:34 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:content-type; bh=gA7sdjFceHluYnUJghHuOAoAohLYGfrqQmhGp1rn7+U=; b=IsL0yJh4TfzTEjalnF/KdBTGQBLqFOVIRiCcy012W2HjI+47XITO9S6q2RCYyBA7bK H9ktJLaffOmxFPleN52DJWmoqZ3VH8/zFY5H0jJdPPAh+Cn8CK/atDx2jZ69Z84dtt0q xyC322Ot1Yw6AjwfBFKO2xu+tO58XxvK/7eBhJurhp9mfl/oEecqQ+pr/MXDhxetmFYI UvhErxZ2HjVLjdVRX8XXlkeYVGPUZCbzqRzoB7cTnwPO9C5VeeFbH978AJ+Z7I6uyVyc wdocN7YL8EvtxeCl3uWmBKvbSAusQDJfuxLnufteGDns44hDIcAJbEeMkMrES0IaJTxW NQ6w== MIME-Version: 1.0 Received: by 10.224.173.82 with SMTP id o18mr43133939qaz.96.1346821293717; Tue, 04 Sep 2012 22:01:33 -0700 (PDT) Received: by 10.229.16.134 with HTTP; Tue, 4 Sep 2012 22:01:33 -0700 (PDT) In-Reply-To: References: Date: Tue, 4 Sep 2012 22:01:33 -0700 X-Google-Sender-Auth: OsU8oVsdCmmjHLF6pwgaBTaaheA Message-ID: From: John Sherwood To: xen-users@lists.xen.org Subject: Re: [Xen-users] guest OS High Availability with local storage X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============5894389904919978074==" Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org --===============5894389904919978074== Content-Type: multipart/alternative; boundary=20cf30363ffdc9b8dd04c8ed44c9 --20cf30363ffdc9b8dd04c8ed44c9 Content-Type: text/plain; charset=ISO-8859-1 On Tue, Sep 4, 2012 at 9:44 PM, Fajar A. Nugraha wrote: > On Wed, Sep 5, 2012 at 10:57 AM, Umarzuki Mochlis > wrote: > > hi, > > > > if I were to use Debian Squeeze as dom0 (3 servers) and install Xen > > hypervisor 4.0 on all of them, how would I achieve HA with only using > > local storage? > > You can't > > > has it ever been done before? > > The easiest way would be to use shared storage and some sort of > cluster manager. So if it were me I'd use one node as SAN (e.g. with > openindiana + nappit, or whatever iscsi-capable storage appliance of > your choice) and the other two as compute nodes. The SAN becomes a > single point of failure though (unless you can afford two storage > nodes, but that's another story). > > If you don't have SAN, then to have a "shared" common storage you can > use DRBD. AFAIK you can only have two nodes for primary-primary setup > though. See https://alteeve.ca/w/Red_Hat_Cluster_Service_3_Tutorial > for example (it uses KVM, but the concept should be similar). > > -- > Fajar > > You can, technically do this with only local storage and stuff like DRBD; boot your HA host off the network and store everything in RAM, bypassing local storage entirely. The drawback there is obvious, but it is a (VERY application dependent) option. Also, with respect to doing it using Xen, Xen HA = Remus, and DRBD is going to be your best option for storage if you've ruled out an actual HA storage solution (e.g., a SAN). It's discussed in the original Remus whitepaper as well (http://nss.cs.ubc.ca/remus/papers/remus-nsdi08.pdf). That being said, while you can technically make DRBD work across three hosts (mirror A to B, then B to C), I'm not sure if you could make Remus do that, and on the subject of Remus, I wouldn't trust it in prod until 4.2 is released. _______________________________________________ > Xen-users mailing list > Xen-users@lists.xen.org > http://lists.xen.org/xen-users > --20cf30363ffdc9b8dd04c8ed44c9 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable

On Tue, Sep 4, 2012 at 9:44 PM, Fajar A.= Nugraha <list@fajar.net> wrote:
On Wed, Sep 5, 2012 at 10:57 AM, Umarzuki Mochlis <umarzuki@gmail.com> wrote:
> hi,
>
> if I were to use Debian Squeeze as dom0 (3 servers) and install Xen > hypervisor 4.0 on all of them, how would I achieve HA with only using<= br> > local storage?

You can't

> has it ever been done before?

The easiest way would be to use shared storage and some sort of
cluster manager. So if it were me I'd use one node as SAN (e.g. with openindiana + nappit, or whatever iscsi-capable storage appliance of
your choice) and the other two as compute nodes. The SAN becomes a
single point of failure though (unless you can afford two storage
nodes, but that's another story).

If you don't have SAN, then to have a "shared" common storage= you can
use DRBD. AFAIK you can only have two nodes for primary-primary setup
though. See https://alteeve.ca/w/Red_Hat_Cluster_Service_3_Tutor= ial
for example (it uses KVM, but the concept should be similar).

--
Fajar

You can, technically do this with only = local storage and stuff like DRBD; boot your HA host off the network and st= ore everything in RAM, bypassing local storage entirely. The drawback there= is obvious, but it is a (VERY application dependent) option.

Also, with respect to doing it using Xen, Xen HA =3D Re= mus, and DRBD is going to be your best option for storage if you've rul= ed out an actual HA storage solution (e.g., a SAN). It's discussed in t= he original Remus whitepaper as well (http://nss.cs.ubc.ca/remus/papers/remus-nsdi08.pd= f). That being said, while you can technically make DRBD work across th= ree hosts (mirror A to B, then B to C), I'm not sure if you could make = Remus do that, and on the subject of Remus, I wouldn't trust it in prod= until 4.2 is released.

_______________________________________________
Xen-users mailing list
Xen-users@list= s.xen.org
http://lists.x= en.org/xen-users

--20cf30363ffdc9b8dd04c8ed44c9-- --===============5894389904919978074== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users --===============5894389904919978074==-- From xen-users-bounces@lists.xen.org Wed Sep 05 05:02:26 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Wed, 05 Sep 2012 05:02:26 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1T97kB-0002cj-JP; Wed, 05 Sep 2012 05:01:39 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1T97k9-0002ce-DJ for xen-users@lists.xen.org; Wed, 05 Sep 2012 05:01:37 +0000 Received: from [85.158.139.83:8920] by server-7.bemta-5.messagelabs.com id 11/F0-19703-0BCD6405; Wed, 05 Sep 2012 05:01:36 +0000 X-Env-Sender: theubaz@gmail.com X-Msg-Ref: server-2.tower-182.messagelabs.com!1346821294!28592306!1 X-Originating-IP: [209.85.216.52] X-SpamReason: No, hits=0.4 required=7.0 tests=HTML_30_40,HTML_MESSAGE, RCVD_BY_IP X-StarScan-Received: X-StarScan-Version: 6.6.1.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 1702 invoked from network); 5 Sep 2012 05:01:35 -0000 Received: from mail-qa0-f52.google.com (HELO mail-qa0-f52.google.com) (209.85.216.52) by server-2.tower-182.messagelabs.com with RC4-SHA encrypted SMTP; 5 Sep 2012 05:01:35 -0000 Received: by qabg14 with SMTP id g14so270058qab.11 for ; Tue, 04 Sep 2012 22:01:34 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:content-type; bh=gA7sdjFceHluYnUJghHuOAoAohLYGfrqQmhGp1rn7+U=; b=IsL0yJh4TfzTEjalnF/KdBTGQBLqFOVIRiCcy012W2HjI+47XITO9S6q2RCYyBA7bK H9ktJLaffOmxFPleN52DJWmoqZ3VH8/zFY5H0jJdPPAh+Cn8CK/atDx2jZ69Z84dtt0q xyC322Ot1Yw6AjwfBFKO2xu+tO58XxvK/7eBhJurhp9mfl/oEecqQ+pr/MXDhxetmFYI UvhErxZ2HjVLjdVRX8XXlkeYVGPUZCbzqRzoB7cTnwPO9C5VeeFbH978AJ+Z7I6uyVyc wdocN7YL8EvtxeCl3uWmBKvbSAusQDJfuxLnufteGDns44hDIcAJbEeMkMrES0IaJTxW NQ6w== MIME-Version: 1.0 Received: by 10.224.173.82 with SMTP id o18mr43133939qaz.96.1346821293717; Tue, 04 Sep 2012 22:01:33 -0700 (PDT) Received: by 10.229.16.134 with HTTP; Tue, 4 Sep 2012 22:01:33 -0700 (PDT) In-Reply-To: References: Date: Tue, 4 Sep 2012 22:01:33 -0700 X-Google-Sender-Auth: OsU8oVsdCmmjHLF6pwgaBTaaheA Message-ID: From: John Sherwood To: xen-users@lists.xen.org Subject: Re: [Xen-users] guest OS High Availability with local storage X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============5894389904919978074==" Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org --===============5894389904919978074== Content-Type: multipart/alternative; boundary=20cf30363ffdc9b8dd04c8ed44c9 --20cf30363ffdc9b8dd04c8ed44c9 Content-Type: text/plain; charset=ISO-8859-1 On Tue, Sep 4, 2012 at 9:44 PM, Fajar A. Nugraha wrote: > On Wed, Sep 5, 2012 at 10:57 AM, Umarzuki Mochlis > wrote: > > hi, > > > > if I were to use Debian Squeeze as dom0 (3 servers) and install Xen > > hypervisor 4.0 on all of them, how would I achieve HA with only using > > local storage? > > You can't > > > has it ever been done before? > > The easiest way would be to use shared storage and some sort of > cluster manager. So if it were me I'd use one node as SAN (e.g. with > openindiana + nappit, or whatever iscsi-capable storage appliance of > your choice) and the other two as compute nodes. The SAN becomes a > single point of failure though (unless you can afford two storage > nodes, but that's another story). > > If you don't have SAN, then to have a "shared" common storage you can > use DRBD. AFAIK you can only have two nodes for primary-primary setup > though. See https://alteeve.ca/w/Red_Hat_Cluster_Service_3_Tutorial > for example (it uses KVM, but the concept should be similar). > > -- > Fajar > > You can, technically do this with only local storage and stuff like DRBD; boot your HA host off the network and store everything in RAM, bypassing local storage entirely. The drawback there is obvious, but it is a (VERY application dependent) option. Also, with respect to doing it using Xen, Xen HA = Remus, and DRBD is going to be your best option for storage if you've ruled out an actual HA storage solution (e.g., a SAN). It's discussed in the original Remus whitepaper as well (http://nss.cs.ubc.ca/remus/papers/remus-nsdi08.pdf). That being said, while you can technically make DRBD work across three hosts (mirror A to B, then B to C), I'm not sure if you could make Remus do that, and on the subject of Remus, I wouldn't trust it in prod until 4.2 is released. _______________________________________________ > Xen-users mailing list > Xen-users@lists.xen.org > http://lists.xen.org/xen-users > --20cf30363ffdc9b8dd04c8ed44c9 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable

On Tue, Sep 4, 2012 at 9:44 PM, Fajar A.= Nugraha <list@fajar.net> wrote:
On Wed, Sep 5, 2012 at 10:57 AM, Umarzuki Mochlis <umarzuki@gmail.com> wrote:
> hi,
>
> if I were to use Debian Squeeze as dom0 (3 servers) and install Xen > hypervisor 4.0 on all of them, how would I achieve HA with only using<= br> > local storage?

You can't

> has it ever been done before?

The easiest way would be to use shared storage and some sort of
cluster manager. So if it were me I'd use one node as SAN (e.g. with openindiana + nappit, or whatever iscsi-capable storage appliance of
your choice) and the other two as compute nodes. The SAN becomes a
single point of failure though (unless you can afford two storage
nodes, but that's another story).

If you don't have SAN, then to have a "shared" common storage= you can
use DRBD. AFAIK you can only have two nodes for primary-primary setup
though. See https://alteeve.ca/w/Red_Hat_Cluster_Service_3_Tutor= ial
for example (it uses KVM, but the concept should be similar).

--
Fajar

You can, technically do this with only = local storage and stuff like DRBD; boot your HA host off the network and st= ore everything in RAM, bypassing local storage entirely. The drawback there= is obvious, but it is a (VERY application dependent) option.

Also, with respect to doing it using Xen, Xen HA =3D Re= mus, and DRBD is going to be your best option for storage if you've rul= ed out an actual HA storage solution (e.g., a SAN). It's discussed in t= he original Remus whitepaper as well (http://nss.cs.ubc.ca/remus/papers/remus-nsdi08.pd= f). That being said, while you can technically make DRBD work across th= ree hosts (mirror A to B, then B to C), I'm not sure if you could make = Remus do that, and on the subject of Remus, I wouldn't trust it in prod= until 4.2 is released.

_______________________________________________
Xen-users mailing list
Xen-users@list= s.xen.org
http://lists.x= en.org/xen-users

--20cf30363ffdc9b8dd04c8ed44c9-- --===============5894389904919978074== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users --===============5894389904919978074==-- From xen-users-bounces@lists.xen.org Wed Sep 05 05:03:19 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Wed, 05 Sep 2012 05:03:19 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1T97kq-0002eB-9Q; Wed, 05 Sep 2012 05:02:20 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1T97ko-0002dx-Mi for xen-users@lists.xen.org; Wed, 05 Sep 2012 05:02:19 +0000 Received: from [85.158.138.51:63636] by server-11.bemta-3.messagelabs.com id BA/25-30250-9DCD6405; Wed, 05 Sep 2012 05:02:17 +0000 X-Env-Sender: theubaz@gmail.com X-Msg-Ref: server-14.tower-174.messagelabs.com!1346821335!22328367!1 X-Originating-IP: [209.85.216.45] X-SpamReason: No, hits=0.9 required=7.0 tests=HTML_40_50,HTML_MESSAGE, RCVD_BY_IP X-StarScan-Received: X-StarScan-Version: 6.6.1.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 31160 invoked from network); 5 Sep 2012 05:02:16 -0000 Received: from mail-qa0-f45.google.com (HELO mail-qa0-f45.google.com) (209.85.216.45) by server-14.tower-174.messagelabs.com with RC4-SHA encrypted SMTP; 5 Sep 2012 05:02:16 -0000 Received: by qadc10 with SMTP id c10so4479687qad.11 for ; Tue, 04 Sep 2012 22:02:15 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:content-type; bh=t4x6F4eQPN+Wbk2l1FO68V9zEy83TMwPmXE1IFR8L4k=; b=hFGF9kXUiYc5HhLjt7mx+N2ItbpthubsBz5zMcJ6pjCq3O6epshUr1bM/C++YOP1zH x0tvpG09O3Tmz1YpSjf+IMIY0oEaC7a/YgLqYdofR1Dy3FKfEVx9hsRpHHZwWkP85HoE rUZ4JPE5Ww91QKeAEUoOuFDORWQbxLcMD+0aBVklvBOb82nAG5iO367B51tRGl71fzC8 Q1P7JJULppdblrO4E0vvQzE7vMZ4qkt2EQ39YtpDBJkOAxrUc+/SSwPTpU/1da0PJED4 XZuHSRn53JoZ8phSxBnvprv+K7pGj+LjO1K9gjZw1IFnvlpYslHujCvKKwqayhbMj2sn az8A== MIME-Version: 1.0 Received: by 10.224.40.11 with SMTP id i11mr22546148qae.45.1346821335182; Tue, 04 Sep 2012 22:02:15 -0700 (PDT) Received: by 10.229.16.134 with HTTP; Tue, 4 Sep 2012 22:02:15 -0700 (PDT) In-Reply-To: References: Date: Tue, 4 Sep 2012 22:02:15 -0700 X-Google-Sender-Auth: 6J7qQsuG7qlS-9jyZIQfmUYMnQc Message-ID: From: John Sherwood To: xen-users@lists.xen.org Subject: Re: [Xen-users] guest OS High Availability with local storage X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============4852897626795590833==" Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org --===============4852897626795590833== Content-Type: multipart/alternative; boundary=20cf306f76c8426e3a04c8ed4737 --20cf306f76c8426e3a04c8ed4737 Content-Type: text/plain; charset=ISO-8859-1 On Tue, Sep 4, 2012 at 10:01 PM, John Sherwood wrote: > > > On Tue, Sep 4, 2012 at 9:44 PM, Fajar A. Nugraha wrote: > >> On Wed, Sep 5, 2012 at 10:57 AM, Umarzuki Mochlis >> wrote: >> > hi, >> > >> > if I were to use Debian Squeeze as dom0 (3 servers) and install Xen >> > hypervisor 4.0 on all of them, how would I achieve HA with only using >> > local storage? >> >> You can't >> >> > has it ever been done before? >> >> The easiest way would be to use shared storage and some sort of >> cluster manager. So if it were me I'd use one node as SAN (e.g. with >> openindiana + nappit, or whatever iscsi-capable storage appliance of >> your choice) and the other two as compute nodes. The SAN becomes a >> single point of failure though (unless you can afford two storage >> nodes, but that's another story). >> >> If you don't have SAN, then to have a "shared" common storage you can >> use DRBD. AFAIK you can only have two nodes for primary-primary setup >> though. See https://alteeve.ca/w/Red_Hat_Cluster_Service_3_Tutorial >> for example (it uses KVM, but the concept should be similar). >> >> -- >> Fajar >> >> You can, technically do this with only local storage and stuff like DRBD; > oops, meant to say "without" stuff like DRBD (kind of an important word to leave out, sorry) > boot your HA host off the network and store everything in RAM, bypassing > local storage entirely. The drawback there is obvious, but it is a (VERY > application dependent) option. > > Also, with respect to doing it using Xen, Xen HA = Remus, and DRBD is > going to be your best option for storage if you've ruled out an actual HA > storage solution (e.g., a SAN). It's discussed in the original Remus > whitepaper as well (http://nss.cs.ubc.ca/remus/papers/remus-nsdi08.pdf). > That being said, while you can technically make DRBD work across three > hosts (mirror A to B, then B to C), I'm not sure if you could make Remus do > that, and on the subject of Remus, I wouldn't trust it in prod until 4.2 is > released. > > _______________________________________________ >> Xen-users mailing list >> Xen-users@lists.xen.org >> http://lists.xen.org/xen-users >> > > --20cf306f76c8426e3a04c8ed4737 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable

On Tue, Sep 4, 2012 at 10:01 PM, John Sh= erwood <jrs@vt.edu> wrote:


On Tue, Sep 4, 2012 at= 9:44 PM, Fajar A. Nugraha <list@fajar.net> wrote:
On Wed, Sep 5, 2012 at 10:57 AM, Umarzuki Mochlis <umarzuki@gmail.com> wrote:
> hi,
>
> if I were to use Debian Squeeze as dom0 (3 servers) and install Xen > hypervisor 4.0 on all of them, how would I achieve HA with only using<= br> > local storage?

You can't

> has it ever been done before?

The easiest way would be to use shared storage and some sort of
cluster manager. So if it were me I'd use one node as SAN (e.g. with openindiana + nappit, or whatever iscsi-capable storage appliance of
your choice) and the other two as compute nodes. The SAN becomes a
single point of failure though (unless you can afford two storage
nodes, but that's another story).

If you don't have SAN, then to have a "shared" common storage= you can
use DRBD. AFAIK you can only have two nodes for primary-primary setup
though. See https://alteeve.ca/w/Red_Hat_Cluster_Service_3_Tutor= ial
for example (it uses KVM, but the concept should be similar).

--
Fajar

You can, technically do this with= only local storage and stuff like DRBD;

<= /div>
oops, meant to say "without" stuff like DRBD (kind of a= n important word to leave out, sorry)
=A0
boot your HA host off the network and store everything in RAM, bypassing = local storage entirely. The drawback there is obvious, but it is a (VERY ap= plication dependent) option.

Also, with respect to doing it using Xen, Xen HA =3D Re= mus, and DRBD is going to be your best option for storage if you've rul= ed out an actual HA storage solution (e.g., a SAN). It's discussed in t= he original Remus whitepaper as well (http://nss.cs.ubc.ca/remus/pape= rs/remus-nsdi08.pdf). That being said, while you can technically make D= RBD work across three hosts (mirror A to B, then B to C), I'm not sure = if you could make Remus do that, and on the subject of Remus, I wouldn'= t trust it in prod until 4.2 is released.

_______________________________________________
Xen-users mailing list
Xen-users@list= s.xen.org
http://lists.x= en.org/xen-users


--20cf306f76c8426e3a04c8ed4737-- --===============4852897626795590833== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users --===============4852897626795590833==-- From xen-users-bounces@lists.xen.org Wed Sep 05 05:03:19 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Wed, 05 Sep 2012 05:03:19 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1T97kq-0002eB-9Q; Wed, 05 Sep 2012 05:02:20 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1T97ko-0002dx-Mi for xen-users@lists.xen.org; Wed, 05 Sep 2012 05:02:19 +0000 Received: from [85.158.138.51:63636] by server-11.bemta-3.messagelabs.com id BA/25-30250-9DCD6405; Wed, 05 Sep 2012 05:02:17 +0000 X-Env-Sender: theubaz@gmail.com X-Msg-Ref: server-14.tower-174.messagelabs.com!1346821335!22328367!1 X-Originating-IP: [209.85.216.45] X-SpamReason: No, hits=0.9 required=7.0 tests=HTML_40_50,HTML_MESSAGE, RCVD_BY_IP X-StarScan-Received: X-StarScan-Version: 6.6.1.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 31160 invoked from network); 5 Sep 2012 05:02:16 -0000 Received: from mail-qa0-f45.google.com (HELO mail-qa0-f45.google.com) (209.85.216.45) by server-14.tower-174.messagelabs.com with RC4-SHA encrypted SMTP; 5 Sep 2012 05:02:16 -0000 Received: by qadc10 with SMTP id c10so4479687qad.11 for ; Tue, 04 Sep 2012 22:02:15 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:content-type; bh=t4x6F4eQPN+Wbk2l1FO68V9zEy83TMwPmXE1IFR8L4k=; b=hFGF9kXUiYc5HhLjt7mx+N2ItbpthubsBz5zMcJ6pjCq3O6epshUr1bM/C++YOP1zH x0tvpG09O3Tmz1YpSjf+IMIY0oEaC7a/YgLqYdofR1Dy3FKfEVx9hsRpHHZwWkP85HoE rUZ4JPE5Ww91QKeAEUoOuFDORWQbxLcMD+0aBVklvBOb82nAG5iO367B51tRGl71fzC8 Q1P7JJULppdblrO4E0vvQzE7vMZ4qkt2EQ39YtpDBJkOAxrUc+/SSwPTpU/1da0PJED4 XZuHSRn53JoZ8phSxBnvprv+K7pGj+LjO1K9gjZw1IFnvlpYslHujCvKKwqayhbMj2sn az8A== MIME-Version: 1.0 Received: by 10.224.40.11 with SMTP id i11mr22546148qae.45.1346821335182; Tue, 04 Sep 2012 22:02:15 -0700 (PDT) Received: by 10.229.16.134 with HTTP; Tue, 4 Sep 2012 22:02:15 -0700 (PDT) In-Reply-To: References: Date: Tue, 4 Sep 2012 22:02:15 -0700 X-Google-Sender-Auth: 6J7qQsuG7qlS-9jyZIQfmUYMnQc Message-ID: From: John Sherwood To: xen-users@lists.xen.org Subject: Re: [Xen-users] guest OS High Availability with local storage X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============4852897626795590833==" Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org --===============4852897626795590833== Content-Type: multipart/alternative; boundary=20cf306f76c8426e3a04c8ed4737 --20cf306f76c8426e3a04c8ed4737 Content-Type: text/plain; charset=ISO-8859-1 On Tue, Sep 4, 2012 at 10:01 PM, John Sherwood wrote: > > > On Tue, Sep 4, 2012 at 9:44 PM, Fajar A. Nugraha wrote: > >> On Wed, Sep 5, 2012 at 10:57 AM, Umarzuki Mochlis >> wrote: >> > hi, >> > >> > if I were to use Debian Squeeze as dom0 (3 servers) and install Xen >> > hypervisor 4.0 on all of them, how would I achieve HA with only using >> > local storage? >> >> You can't >> >> > has it ever been done before? >> >> The easiest way would be to use shared storage and some sort of >> cluster manager. So if it were me I'd use one node as SAN (e.g. with >> openindiana + nappit, or whatever iscsi-capable storage appliance of >> your choice) and the other two as compute nodes. The SAN becomes a >> single point of failure though (unless you can afford two storage >> nodes, but that's another story). >> >> If you don't have SAN, then to have a "shared" common storage you can >> use DRBD. AFAIK you can only have two nodes for primary-primary setup >> though. See https://alteeve.ca/w/Red_Hat_Cluster_Service_3_Tutorial >> for example (it uses KVM, but the concept should be similar). >> >> -- >> Fajar >> >> You can, technically do this with only local storage and stuff like DRBD; > oops, meant to say "without" stuff like DRBD (kind of an important word to leave out, sorry) > boot your HA host off the network and store everything in RAM, bypassing > local storage entirely. The drawback there is obvious, but it is a (VERY > application dependent) option. > > Also, with respect to doing it using Xen, Xen HA = Remus, and DRBD is > going to be your best option for storage if you've ruled out an actual HA > storage solution (e.g., a SAN). It's discussed in the original Remus > whitepaper as well (http://nss.cs.ubc.ca/remus/papers/remus-nsdi08.pdf). > That being said, while you can technically make DRBD work across three > hosts (mirror A to B, then B to C), I'm not sure if you could make Remus do > that, and on the subject of Remus, I wouldn't trust it in prod until 4.2 is > released. > > _______________________________________________ >> Xen-users mailing list >> Xen-users@lists.xen.org >> http://lists.xen.org/xen-users >> > > --20cf306f76c8426e3a04c8ed4737 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable

On Tue, Sep 4, 2012 at 10:01 PM, John Sh= erwood <jrs@vt.edu> wrote:


On Tue, Sep 4, 2012 at= 9:44 PM, Fajar A. Nugraha <list@fajar.net> wrote:
On Wed, Sep 5, 2012 at 10:57 AM, Umarzuki Mochlis <umarzuki@gmail.com> wrote:
> hi,
>
> if I were to use Debian Squeeze as dom0 (3 servers) and install Xen > hypervisor 4.0 on all of them, how would I achieve HA with only using<= br> > local storage?

You can't

> has it ever been done before?

The easiest way would be to use shared storage and some sort of
cluster manager. So if it were me I'd use one node as SAN (e.g. with openindiana + nappit, or whatever iscsi-capable storage appliance of
your choice) and the other two as compute nodes. The SAN becomes a
single point of failure though (unless you can afford two storage
nodes, but that's another story).

If you don't have SAN, then to have a "shared" common storage= you can
use DRBD. AFAIK you can only have two nodes for primary-primary setup
though. See https://alteeve.ca/w/Red_Hat_Cluster_Service_3_Tutor= ial
for example (it uses KVM, but the concept should be similar).

--
Fajar

You can, technically do this with= only local storage and stuff like DRBD;

<= /div>
oops, meant to say "without" stuff like DRBD (kind of a= n important word to leave out, sorry)
=A0
boot your HA host off the network and store everything in RAM, bypassing = local storage entirely. The drawback there is obvious, but it is a (VERY ap= plication dependent) option.

Also, with respect to doing it using Xen, Xen HA =3D Re= mus, and DRBD is going to be your best option for storage if you've rul= ed out an actual HA storage solution (e.g., a SAN). It's discussed in t= he original Remus whitepaper as well (http://nss.cs.ubc.ca/remus/pape= rs/remus-nsdi08.pdf). That being said, while you can technically make D= RBD work across three hosts (mirror A to B, then B to C), I'm not sure = if you could make Remus do that, and on the subject of Remus, I wouldn'= t trust it in prod until 4.2 is released.

_______________________________________________
Xen-users mailing list
Xen-users@list= s.xen.org
http://lists.x= en.org/xen-users


--20cf306f76c8426e3a04c8ed4737-- --===============4852897626795590833== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users --===============4852897626795590833==-- From xen-users-bounces@lists.xen.org Wed Sep 05 07:44:39 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Wed, 05 Sep 2012 07:44:39 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1T9AGk-0003of-Ez; Wed, 05 Sep 2012 07:43:26 +0000 Received: from mail27.messagelabs.com ([193.109.254.147]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1T9AGi-0003oa-Rl for xen-users@lists.xensource.com; Wed, 05 Sep 2012 07:43:25 +0000 X-Env-Sender: venkateshpnv@gmail.com X-Msg-Ref: server-14.tower-27.messagelabs.com!1346830996!2722413!1 X-Originating-IP: [209.85.210.43] X-SpamReason: No, hits=1.2 required=7.0 tests=HTML_10_20,HTML_MESSAGE, ML_RADAR_SPEW_LINKS_14,RCVD_BY_IP,spamassassin: X-StarScan-Received: X-StarScan-Version: 6.6.1.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 13607 invoked from network); 5 Sep 2012 07:43:18 -0000 Received: from mail-pz0-f43.google.com (HELO mail-pz0-f43.google.com) (209.85.210.43) by server-14.tower-27.messagelabs.com with RC4-SHA encrypted SMTP; 5 Sep 2012 07:43:18 -0000 Received: by daku36 with SMTP id u36so213478dak.30 for ; Wed, 05 Sep 2012 00:43:16 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:date:message-id:subject:from:to:content-type; bh=DOu4BvETYuxzbYS0doCj7Wfsc6Y27KnwPzhg8dup9+0=; b=bOX5tkht6ou6dnrFzg03IZyi3UCFHe+4iszPIZd4PMMoT+8DYD6fSOGP3YASjk33md EAc5Hbkn8F4filNeQNAOGZUfz9xUsp8Mt1V8XhA/2kKy1tSZ0OSZTi8W7yEVuTBpJ2h4 Oq1bBDXw0TiDmmPzsPxYOYsKJ2Zc38RZDI2WxgWSjXrSgZAIZ6+wTklK+AlQFjH3yHur 7ceTqR2MweUmrnahFvL3gHx9BNNMmEYfxfnmqy4C1k/YgMcR6iR52U7vHGGICJ3MH2ep Pc8uOiHJVQN5CUuxl6plWncTOye4ED/toiJnAyfvuiRX9K63pSbr09+GFCkVKmk7x7mO F89A== MIME-Version: 1.0 Received: by 10.66.85.167 with SMTP id i7mr47122975paz.8.1346830996396; Wed, 05 Sep 2012 00:43:16 -0700 (PDT) Received: by 10.68.73.99 with HTTP; Wed, 5 Sep 2012 00:43:16 -0700 (PDT) Date: Wed, 5 Sep 2012 13:13:16 +0530 Message-ID: From: Venkatesh P N To: xen-users@lists.xensource.com Subject: [Xen-users] How to assign a SR-IOV Virtual Function to Host X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============3341939119610035830==" Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org --===============3341939119610035830== Content-Type: multipart/alternative; boundary=f46d042de6891cda1204c8ef8772 --f46d042de6891cda1204c8ef8772 Content-Type: text/plain; charset=ISO-8859-1 Hi, I am using Ubuntu Xen 4.1 with kernel 3.1.0. When SR-IOV is enabled for a PCI device (*pci_enable_sriov(device, no_vf)*), it creates multiple VFs on the machine. I am able to assign it to a guest VM by PCI passthrough (*xm pci-attach*)* *and use the device as a regular device on guest VM. I have a use-case like, I need to use one of the VFs on the host machine itself. So, is there any way to assign VF to host itself and use it as a regular device there. Or, how can we can access a VF created by SR-OV on host machine directly. Thanks Venkatesh --f46d042de6891cda1204c8ef8772 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Hi,

I am using Ubuntu Xen 4.1 with kernel 3.1.0.

When SR-IOV = is enabled for a PCI device (pci_enable_sriov(device, no_vf)), it cr= eates multiple VFs on the machine.

I am able to assign it to a guest= VM by PCI passthrough (xm pci-attach) and use the device as = a regular device on guest VM.

I have a use-case like, I need to use one of the VFs on the host machin= e itself.
So, is there any way to assign VF to host itself and use it as= a regular device there.

Or, how can we can access a VF created by S= R-OV on host machine directly.

Thanks
Venkatesh

--f46d042de6891cda1204c8ef8772-- --===============3341939119610035830== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users --===============3341939119610035830==-- From xen-users-bounces@lists.xen.org Wed Sep 05 07:44:39 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Wed, 05 Sep 2012 07:44:39 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1T9AGk-0003of-Ez; Wed, 05 Sep 2012 07:43:26 +0000 Received: from mail27.messagelabs.com ([193.109.254.147]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1T9AGi-0003oa-Rl for xen-users@lists.xensource.com; Wed, 05 Sep 2012 07:43:25 +0000 X-Env-Sender: venkateshpnv@gmail.com X-Msg-Ref: server-14.tower-27.messagelabs.com!1346830996!2722413!1 X-Originating-IP: [209.85.210.43] X-SpamReason: No, hits=1.2 required=7.0 tests=HTML_10_20,HTML_MESSAGE, ML_RADAR_SPEW_LINKS_14,RCVD_BY_IP,spamassassin: X-StarScan-Received: X-StarScan-Version: 6.6.1.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 13607 invoked from network); 5 Sep 2012 07:43:18 -0000 Received: from mail-pz0-f43.google.com (HELO mail-pz0-f43.google.com) (209.85.210.43) by server-14.tower-27.messagelabs.com with RC4-SHA encrypted SMTP; 5 Sep 2012 07:43:18 -0000 Received: by daku36 with SMTP id u36so213478dak.30 for ; Wed, 05 Sep 2012 00:43:16 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:date:message-id:subject:from:to:content-type; bh=DOu4BvETYuxzbYS0doCj7Wfsc6Y27KnwPzhg8dup9+0=; b=bOX5tkht6ou6dnrFzg03IZyi3UCFHe+4iszPIZd4PMMoT+8DYD6fSOGP3YASjk33md EAc5Hbkn8F4filNeQNAOGZUfz9xUsp8Mt1V8XhA/2kKy1tSZ0OSZTi8W7yEVuTBpJ2h4 Oq1bBDXw0TiDmmPzsPxYOYsKJ2Zc38RZDI2WxgWSjXrSgZAIZ6+wTklK+AlQFjH3yHur 7ceTqR2MweUmrnahFvL3gHx9BNNMmEYfxfnmqy4C1k/YgMcR6iR52U7vHGGICJ3MH2ep Pc8uOiHJVQN5CUuxl6plWncTOye4ED/toiJnAyfvuiRX9K63pSbr09+GFCkVKmk7x7mO F89A== MIME-Version: 1.0 Received: by 10.66.85.167 with SMTP id i7mr47122975paz.8.1346830996396; Wed, 05 Sep 2012 00:43:16 -0700 (PDT) Received: by 10.68.73.99 with HTTP; Wed, 5 Sep 2012 00:43:16 -0700 (PDT) Date: Wed, 5 Sep 2012 13:13:16 +0530 Message-ID: From: Venkatesh P N To: xen-users@lists.xensource.com Subject: [Xen-users] How to assign a SR-IOV Virtual Function to Host X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============3341939119610035830==" Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org --===============3341939119610035830== Content-Type: multipart/alternative; boundary=f46d042de6891cda1204c8ef8772 --f46d042de6891cda1204c8ef8772 Content-Type: text/plain; charset=ISO-8859-1 Hi, I am using Ubuntu Xen 4.1 with kernel 3.1.0. When SR-IOV is enabled for a PCI device (*pci_enable_sriov(device, no_vf)*), it creates multiple VFs on the machine. I am able to assign it to a guest VM by PCI passthrough (*xm pci-attach*)* *and use the device as a regular device on guest VM. I have a use-case like, I need to use one of the VFs on the host machine itself. So, is there any way to assign VF to host itself and use it as a regular device there. Or, how can we can access a VF created by SR-OV on host machine directly. Thanks Venkatesh --f46d042de6891cda1204c8ef8772 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Hi,

I am using Ubuntu Xen 4.1 with kernel 3.1.0.

When SR-IOV = is enabled for a PCI device (pci_enable_sriov(device, no_vf)), it cr= eates multiple VFs on the machine.

I am able to assign it to a guest= VM by PCI passthrough (xm pci-attach) and use the device as = a regular device on guest VM.

I have a use-case like, I need to use one of the VFs on the host machin= e itself.
So, is there any way to assign VF to host itself and use it as= a regular device there.

Or, how can we can access a VF created by S= R-OV on host machine directly.

Thanks
Venkatesh

--f46d042de6891cda1204c8ef8772-- --===============3341939119610035830== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users --===============3341939119610035830==-- From xen-users-bounces@lists.xen.org Wed Sep 05 08:35:56 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Wed, 05 Sep 2012 08:35:56 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1T9B4T-0004io-JL; Wed, 05 Sep 2012 08:34:49 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1T9B4S-0004iO-73 for xen-users@lists.xen.org; Wed, 05 Sep 2012 08:34:48 +0000 Received: from [85.158.143.35:52425] by server-1.bemta-4.messagelabs.com id 4B/B6-12504-7AE07405; Wed, 05 Sep 2012 08:34:47 +0000 X-Env-Sender: Ian.Campbell@citrix.com X-Msg-Ref: server-14.tower-21.messagelabs.com!1346834086!16794240!1 X-Originating-IP: [62.200.22.115] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogNjIuMjAwLjIyLjExNSA9PiAxMTE4NjM=\n X-StarScan-Received: X-StarScan-Version: 6.6.1.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 28914 invoked from network); 5 Sep 2012 08:34:46 -0000 Received: from smtp.eu.citrix.com (HELO SMTP.EU.CITRIX.COM) (62.200.22.115) by server-14.tower-21.messagelabs.com with RC4-SHA encrypted SMTP; 5 Sep 2012 08:34:46 -0000 X-IronPort-AV: E=Sophos;i="4.80,372,1344211200"; d="scan'208";a="14350974" Received: from lonpmailmx01.citrite.net ([10.30.203.162]) by LONPIPO01.EU.CITRIX.COM with ESMTP/TLS/RC4-MD5; 05 Sep 2012 08:34:29 +0000 Received: from [10.80.2.42] (10.80.2.42) by LONPMAILMX01.citrite.net (10.30.203.162) with Microsoft SMTP Server id 8.3.279.1; Wed, 5 Sep 2012 09:34:29 +0100 Message-ID: <1346834067.17325.5.camel@zakaz.uk.xensource.com> From: Ian Campbell To: Pasi =?ISO-8859-1?Q?K=E4rkk=E4inen?= Date: Wed, 5 Sep 2012 09:34:27 +0100 In-Reply-To: <20120905025127.GI8912@reaktio.net> References: <1346665360.25864.2.camel@zakaz.uk.xensource.com> <20120905025127.GI8912@reaktio.net> Organization: Citrix Systems, Inc. X-Mailer: Evolution 3.4.3-1 MIME-Version: 1.0 Cc: xen-users , xen-devel Subject: Re: [Xen-users] [Xen-devel] Xen 4.2.0 Release Plan / TODO X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: base64 Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org T24gV2VkLCAyMDEyLTA5LTA1IGF0IDAzOjUxICswMTAwLCBQYXNpIEvDpHJra8OkaW5lbiB3cm90 ZToKPiBPbiBNb24sIFNlcCAwMywgMjAxMiBhdCAxMDo0Mjo0MEFNICswMTAwLCBJYW4gQ2FtcGJl bGwgd3JvdGU6Cj4gPiAKPiA+IHRvb2xzLCBuaWNlIHRvIGhhdmU6Cj4gPiAKPiA+ICAgICAqIHhs IGNvbXBhdGliaWxpdHkgd2l0aCB4bToKPiA+IAo+ICAgICAgICAgICAqIHhsIHN1cHBvcnQgZm9y ICJtb25pdG9yIiBjb21tYW5kLiBJIGRvbid0IHNlZSBpdCBtZW50aW9uZWQgaW4geGwuY2ZnIGRv Y3MuCj4gICAgICAgICAgICAgKHRoZSBjb21tYW5kIHRvIGVuYWJsZS9kaXNhYmxlIGFjY2VzcyB0 byB0aGUgcGVyLXZtIFFlbXUgbW9uaXRvci9jb25zb2xlIAo+ICAgICAgICAgICAgICBmcm9tIFZO Qywgd2hpY2ggaXMgdXN1YWxseSBhY2Nlc3NlZCB3aXRoIGN0cmwtYWx0LTIpLgoKSSBjYW4ndCBz ZWUgdGhhdCBoYXBwZW5pbmcgZm9yIDQuMi4wIG5vdyBJJ20gYWZyYWlkLiBQcm9iYWJseSBiZXN0 IHRvCmJyaW5nIGl0IHVwIHdpdGggR2VvcmdlIGluIHRoZSA0LjMgdGhyZWFkLiBJdCBtaWdodCBi ZSBhIGNhbmRpZGF0ZSBmb3IKNC4yLjEgZGVwZW5kaW5nIG9uIHRoZSBzaXplIG9mIHRoZSBwYXRj aC4KCklhbi4KCgpfX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19f XwpYZW4tdXNlcnMgbWFpbGluZyBsaXN0Clhlbi11c2Vyc0BsaXN0cy54ZW4ub3JnCmh0dHA6Ly9s aXN0cy54ZW4ub3JnL3hlbi11c2Vycw== From xen-users-bounces@lists.xen.org Wed Sep 05 08:35:56 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Wed, 05 Sep 2012 08:35:56 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1T9B4T-0004io-JL; Wed, 05 Sep 2012 08:34:49 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1T9B4S-0004iO-73 for xen-users@lists.xen.org; Wed, 05 Sep 2012 08:34:48 +0000 Received: from [85.158.143.35:52425] by server-1.bemta-4.messagelabs.com id 4B/B6-12504-7AE07405; Wed, 05 Sep 2012 08:34:47 +0000 X-Env-Sender: Ian.Campbell@citrix.com X-Msg-Ref: server-14.tower-21.messagelabs.com!1346834086!16794240!1 X-Originating-IP: [62.200.22.115] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogNjIuMjAwLjIyLjExNSA9PiAxMTE4NjM=\n X-StarScan-Received: X-StarScan-Version: 6.6.1.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 28914 invoked from network); 5 Sep 2012 08:34:46 -0000 Received: from smtp.eu.citrix.com (HELO SMTP.EU.CITRIX.COM) (62.200.22.115) by server-14.tower-21.messagelabs.com with RC4-SHA encrypted SMTP; 5 Sep 2012 08:34:46 -0000 X-IronPort-AV: E=Sophos;i="4.80,372,1344211200"; d="scan'208";a="14350974" Received: from lonpmailmx01.citrite.net ([10.30.203.162]) by LONPIPO01.EU.CITRIX.COM with ESMTP/TLS/RC4-MD5; 05 Sep 2012 08:34:29 +0000 Received: from [10.80.2.42] (10.80.2.42) by LONPMAILMX01.citrite.net (10.30.203.162) with Microsoft SMTP Server id 8.3.279.1; Wed, 5 Sep 2012 09:34:29 +0100 Message-ID: <1346834067.17325.5.camel@zakaz.uk.xensource.com> From: Ian Campbell To: Pasi =?ISO-8859-1?Q?K=E4rkk=E4inen?= Date: Wed, 5 Sep 2012 09:34:27 +0100 In-Reply-To: <20120905025127.GI8912@reaktio.net> References: <1346665360.25864.2.camel@zakaz.uk.xensource.com> <20120905025127.GI8912@reaktio.net> Organization: Citrix Systems, Inc. X-Mailer: Evolution 3.4.3-1 MIME-Version: 1.0 Cc: xen-users , xen-devel Subject: Re: [Xen-users] [Xen-devel] Xen 4.2.0 Release Plan / TODO X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: base64 Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org T24gV2VkLCAyMDEyLTA5LTA1IGF0IDAzOjUxICswMTAwLCBQYXNpIEvDpHJra8OkaW5lbiB3cm90 ZToKPiBPbiBNb24sIFNlcCAwMywgMjAxMiBhdCAxMDo0Mjo0MEFNICswMTAwLCBJYW4gQ2FtcGJl bGwgd3JvdGU6Cj4gPiAKPiA+IHRvb2xzLCBuaWNlIHRvIGhhdmU6Cj4gPiAKPiA+ICAgICAqIHhs IGNvbXBhdGliaWxpdHkgd2l0aCB4bToKPiA+IAo+ICAgICAgICAgICAqIHhsIHN1cHBvcnQgZm9y ICJtb25pdG9yIiBjb21tYW5kLiBJIGRvbid0IHNlZSBpdCBtZW50aW9uZWQgaW4geGwuY2ZnIGRv Y3MuCj4gICAgICAgICAgICAgKHRoZSBjb21tYW5kIHRvIGVuYWJsZS9kaXNhYmxlIGFjY2VzcyB0 byB0aGUgcGVyLXZtIFFlbXUgbW9uaXRvci9jb25zb2xlIAo+ICAgICAgICAgICAgICBmcm9tIFZO Qywgd2hpY2ggaXMgdXN1YWxseSBhY2Nlc3NlZCB3aXRoIGN0cmwtYWx0LTIpLgoKSSBjYW4ndCBz ZWUgdGhhdCBoYXBwZW5pbmcgZm9yIDQuMi4wIG5vdyBJJ20gYWZyYWlkLiBQcm9iYWJseSBiZXN0 IHRvCmJyaW5nIGl0IHVwIHdpdGggR2VvcmdlIGluIHRoZSA0LjMgdGhyZWFkLiBJdCBtaWdodCBi ZSBhIGNhbmRpZGF0ZSBmb3IKNC4yLjEgZGVwZW5kaW5nIG9uIHRoZSBzaXplIG9mIHRoZSBwYXRj aC4KCklhbi4KCgpfX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19f XwpYZW4tdXNlcnMgbWFpbGluZyBsaXN0Clhlbi11c2Vyc0BsaXN0cy54ZW4ub3JnCmh0dHA6Ly9s aXN0cy54ZW4ub3JnL3hlbi11c2Vycw== From xen-users-bounces@lists.xen.org Wed Sep 05 08:40:23 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Wed, 05 Sep 2012 08:40:23 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1T9B8v-00058d-UC; Wed, 05 Sep 2012 08:39:25 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1T9B8u-00058F-78 for xen-users@lists.xen.org; Wed, 05 Sep 2012 08:39:24 +0000 Received: from [85.158.143.99:37878] by server-1.bemta-4.messagelabs.com id A5/60-12504-BBF07405; Wed, 05 Sep 2012 08:39:23 +0000 X-Env-Sender: pasik@iki.fi X-Msg-Ref: server-16.tower-216.messagelabs.com!1346834362!17405276!1 X-Originating-IP: [192.89.123.25] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogMTkyLjg5LjEyMy4yNSA9PiA1MDIwMTE=\n X-StarScan-Received: X-StarScan-Version: 6.6.1.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 3503 invoked from network); 5 Sep 2012 08:39:22 -0000 Received: from smtp.tele.fi (HELO smtp.tele.fi) (192.89.123.25) by server-16.tower-216.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 5 Sep 2012 08:39:22 -0000 X-Originating-Ip: [194.89.68.22] Received: from ydin.reaktio.net (reaktio.net [194.89.68.22]) by smtp.tele.fi (Postfix) with ESMTP id B535D1179; Wed, 5 Sep 2012 11:39:21 +0300 (EEST) Received: by ydin.reaktio.net (Postfix, from userid 1001) id 6FE0B2005D; Wed, 5 Sep 2012 11:39:21 +0300 (EEST) Date: Wed, 5 Sep 2012 11:39:21 +0300 From: Pasi =?iso-8859-1?Q?K=E4rkk=E4inen?= To: Ian Campbell Message-ID: <20120905083921.GL8912@reaktio.net> References: <1346665360.25864.2.camel@zakaz.uk.xensource.com> <20120905025127.GI8912@reaktio.net> <1346834067.17325.5.camel@zakaz.uk.xensource.com> MIME-Version: 1.0 Content-Disposition: inline In-Reply-To: <1346834067.17325.5.camel@zakaz.uk.xensource.com> User-Agent: Mutt/1.5.20 (2009-06-14) Cc: xen-users , xen-devel Subject: Re: [Xen-users] [Xen-devel] Xen 4.2.0 Release Plan / TODO X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org On Wed, Sep 05, 2012 at 09:34:27AM +0100, Ian Campbell wrote: > On Wed, 2012-09-05 at 03:51 +0100, Pasi K=E4rkk=E4inen wrote: > > On Mon, Sep 03, 2012 at 10:42:40AM +0100, Ian Campbell wrote: > > > = > > > tools, nice to have: > > > = > > > * xl compatibility with xm: > > > = > > * xl support for "monitor" command. I don't see it mentioned = in xl.cfg docs. > > (the command to enable/disable access to the per-vm Qemu mo= nitor/console = > > from VNC, which is usually accessed with ctrl-alt-2). > = > I can't see that happening for 4.2.0 now I'm afraid. Probably best to > bring it up with George in the 4.3 thread. It might be a candidate for > 4.2.1 depending on the size of the patch. > = Yep. If "monitor2 is enabled as a default (I'm not sure about that), then i= t's a security issue.. = User having a VNC session to the console of the VM can run Qemu commands, s= o for example map .iso files from dom0 etc.. -- Pasi _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Wed Sep 05 08:40:23 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Wed, 05 Sep 2012 08:40:23 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1T9B8v-00058d-UC; Wed, 05 Sep 2012 08:39:25 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1T9B8u-00058F-78 for xen-users@lists.xen.org; Wed, 05 Sep 2012 08:39:24 +0000 Received: from [85.158.143.99:37878] by server-1.bemta-4.messagelabs.com id A5/60-12504-BBF07405; Wed, 05 Sep 2012 08:39:23 +0000 X-Env-Sender: pasik@iki.fi X-Msg-Ref: server-16.tower-216.messagelabs.com!1346834362!17405276!1 X-Originating-IP: [192.89.123.25] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogMTkyLjg5LjEyMy4yNSA9PiA1MDIwMTE=\n X-StarScan-Received: X-StarScan-Version: 6.6.1.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 3503 invoked from network); 5 Sep 2012 08:39:22 -0000 Received: from smtp.tele.fi (HELO smtp.tele.fi) (192.89.123.25) by server-16.tower-216.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 5 Sep 2012 08:39:22 -0000 X-Originating-Ip: [194.89.68.22] Received: from ydin.reaktio.net (reaktio.net [194.89.68.22]) by smtp.tele.fi (Postfix) with ESMTP id B535D1179; Wed, 5 Sep 2012 11:39:21 +0300 (EEST) Received: by ydin.reaktio.net (Postfix, from userid 1001) id 6FE0B2005D; Wed, 5 Sep 2012 11:39:21 +0300 (EEST) Date: Wed, 5 Sep 2012 11:39:21 +0300 From: Pasi =?iso-8859-1?Q?K=E4rkk=E4inen?= To: Ian Campbell Message-ID: <20120905083921.GL8912@reaktio.net> References: <1346665360.25864.2.camel@zakaz.uk.xensource.com> <20120905025127.GI8912@reaktio.net> <1346834067.17325.5.camel@zakaz.uk.xensource.com> MIME-Version: 1.0 Content-Disposition: inline In-Reply-To: <1346834067.17325.5.camel@zakaz.uk.xensource.com> User-Agent: Mutt/1.5.20 (2009-06-14) Cc: xen-users , xen-devel Subject: Re: [Xen-users] [Xen-devel] Xen 4.2.0 Release Plan / TODO X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org On Wed, Sep 05, 2012 at 09:34:27AM +0100, Ian Campbell wrote: > On Wed, 2012-09-05 at 03:51 +0100, Pasi K=E4rkk=E4inen wrote: > > On Mon, Sep 03, 2012 at 10:42:40AM +0100, Ian Campbell wrote: > > > = > > > tools, nice to have: > > > = > > > * xl compatibility with xm: > > > = > > * xl support for "monitor" command. I don't see it mentioned = in xl.cfg docs. > > (the command to enable/disable access to the per-vm Qemu mo= nitor/console = > > from VNC, which is usually accessed with ctrl-alt-2). > = > I can't see that happening for 4.2.0 now I'm afraid. Probably best to > bring it up with George in the 4.3 thread. It might be a candidate for > 4.2.1 depending on the size of the patch. > = Yep. If "monitor2 is enabled as a default (I'm not sure about that), then i= t's a security issue.. = User having a VNC session to the console of the VM can run Qemu commands, s= o for example map .iso files from dom0 etc.. -- Pasi _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Wed Sep 05 08:53:20 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Wed, 05 Sep 2012 08:53:20 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1T9BLR-0005mA-SR; Wed, 05 Sep 2012 08:52:21 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1T9BLQ-0005lr-FI for xen-users@lists.xen.org; Wed, 05 Sep 2012 08:52:20 +0000 Received: from [85.158.138.51:40444] by server-3.bemta-3.messagelabs.com id 8D/68-21322-3C217405; Wed, 05 Sep 2012 08:52:19 +0000 X-Env-Sender: linux@eikelenboom.it X-Msg-Ref: server-11.tower-174.messagelabs.com!1346835132!28715162!1 X-Originating-IP: [188.40.164.121] X-SpamReason: No, hits=0.0 required=7.0 tests= X-StarScan-Received: X-StarScan-Version: 6.6.1.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 8004 invoked from network); 5 Sep 2012 08:52:12 -0000 Received: from static.121.164.40.188.clients.your-server.de (HELO smtp.eikelenboom.it) (188.40.164.121) by server-11.tower-174.messagelabs.com with AES256-SHA encrypted SMTP; 5 Sep 2012 08:52:12 -0000 Received: from 128-64-ftth.onsneteindhoven.nl ([88.159.64.128]:51391 helo=[172.16.1.20]) by smtp.eikelenboom.it with esmtpsa (TLS1.0:RSA_AES_256_CBC_SHA1:32) (Exim 4.72) (envelope-from ) id 1T9BHu-0007LZ-8N; Wed, 05 Sep 2012 10:48:42 +0200 Date: Wed, 5 Sep 2012 10:51:46 +0200 From: Sander Eikelenboom Organization: Eikelenboom IT services X-Priority: 3 (Normal) Message-ID: <102157590.20120905105146@eikelenboom.it> To: Ian Campbell In-Reply-To: <1346834067.17325.5.camel@zakaz.uk.xensource.com> References: <1346665360.25864.2.camel@zakaz.uk.xensource.com> <20120905025127.GI8912@reaktio.net> <1346834067.17325.5.camel@zakaz.uk.xensource.com> MIME-Version: 1.0 Cc: xen-users , =?utf-8?Q?Pasi_K=C3=A4rkk=C3=A4inen?= , xen-devel Subject: Re: [Xen-users] [Xen-devel] Xen 4.2.0 Release Plan / TODO X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: base64 Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org DQpXZWRuZXNkYXksIFNlcHRlbWJlciA1LCAyMDEyLCAxMDozNDoyNyBBTSwgeW91IHdyb3RlOgoK PiBPbiBXZWQsIDIwMTItMDktMDUgYXQgMDM6NTEgKzAxMDAsIFBhc2kgS8Okcmtrw6RpbmVuIHdy b3RlOgo+PiBPbiBNb24sIFNlcCAwMywgMjAxMiBhdCAxMDo0Mjo0MEFNICswMTAwLCBJYW4gQ2Ft cGJlbGwgd3JvdGU6Cj4+ID4gCj4+ID4gdG9vbHMsIG5pY2UgdG8gaGF2ZToKPj4gPiAKPj4gPiAg ICAgKiB4bCBjb21wYXRpYmlsaXR5IHdpdGggeG06Cj4+ID4gCj4+ICAgICAgICAgICAqIHhsIHN1 cHBvcnQgZm9yICJtb25pdG9yIiBjb21tYW5kLiBJIGRvbid0IHNlZSBpdCBtZW50aW9uZWQgaW4g eGwuY2ZnIGRvY3MuCj4+ICAgICAgICAgICAgICh0aGUgY29tbWFuZCB0byBlbmFibGUvZGlzYWJs ZSBhY2Nlc3MgdG8gdGhlIHBlci12bSBRZW11IG1vbml0b3IvY29uc29sZSAKPj4gICAgICAgICAg ICAgIGZyb20gVk5DLCB3aGljaCBpcyB1c3VhbGx5IGFjY2Vzc2VkIHdpdGggY3RybC1hbHQtMiku Cgo+IEkgY2FuJ3Qgc2VlIHRoYXQgaGFwcGVuaW5nIGZvciA0LjIuMCBub3cgSSdtIGFmcmFpZC4g UHJvYmFibHkgYmVzdCB0bwo+IGJyaW5nIGl0IHVwIHdpdGggR2VvcmdlIGluIHRoZSA0LjMgdGhy ZWFkLiBJdCBtaWdodCBiZSBhIGNhbmRpZGF0ZSBmb3IKPiA0LjIuMSBkZXBlbmRpbmcgb24gdGhl IHNpemUgb2YgdGhlIHBhdGNoLgoKSSBoYXZlIHRoZSBmZWVsaW5nIHRoZXJlIGFyZSBzdGlsbCBx dWl0ZSBzb21lIG9wdGlvbnMgbWlzc2luZyBmcm9tIHhsID8KQW5kIHNpbmNlIHhtIHdpbGwgYmUg Zm9ybWFsbHkgZGVwcmVjYXRlZCBwZXJoYXBzIHRoaXMgdXJnZXMgZm9yIGEgbGliZXJhbCB2aWV3 IG9uIGJhY2twb3J0aW5nIGNhbmRpZGF0ZXMuCgpIYXZpbmcgdG8gd2FpdCBhIGZ1bGwgcmVsZWFz ZSBjeWNsZSBmb3IgY29tcGF0aWJpbGl0eSBzdHVmZiBkb2Vzbid0IHNlZW0gdmVyeSBhdHRyYWN0 aXZlIGFuZCBtaWdodCBtYWtlIHBlb3BsZSBza2lwIDQuMi54IGFsdG9nZXRoZXIuCgpJIGhhdmUg anVzdCBzdGFydGVkIG9uIHRoZSBzaHV0ZG93biBvcHRpb24sIHNvIGhvcGVmdWxseSB0aGF0IGNh biBiZSBvZmYgdGhlIGxpc3QgdG9kYXkgOi0pCkFuZCBkbyBpdCBmb3IgeGwgcmVib290IHRvbywg aXQgYWxzbyBsYWNrcyB0aGUgIi1hIiBvcHRpb24uCgpBZnRlciB0aGF0IHBlcmhhcHMgdHJ5IHRv IG1ha2UgYSBjb21wYXJpc29uIGJldHdlZW4geG0gYW5kIHhsIHRvIHNlZSB3aGF0J3Mgc3RpbGwg bGFja2luZyBpbiB0ZXJtcyBvZiBjb21wYXRpYmlsaXR5IGFuZCBzZWUgd2hhdCB3b3VsZCBiZSBu aWNlIHRvIGhhdmUgaW1wbGVtZW50ZWQsIGFuZCB3aGF0IGNhbiBwZXJoYXBzIGJlIGxlZnQgb3V0 LgoKLS0KU2FuZGVyCgo+IElhbi4KCgoKCgpfX19fX19fX19fX19fX19fX19fX19fX19fX19fX19f X19fX19fX19fX19fX19fXwpYZW4tdXNlcnMgbWFpbGluZyBsaXN0Clhlbi11c2Vyc0BsaXN0cy54 ZW4ub3JnCmh0dHA6Ly9saXN0cy54ZW4ub3JnL3hlbi11c2Vycw== From xen-users-bounces@lists.xen.org Wed Sep 05 08:53:20 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Wed, 05 Sep 2012 08:53:20 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1T9BLR-0005mA-SR; Wed, 05 Sep 2012 08:52:21 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1T9BLQ-0005lr-FI for xen-users@lists.xen.org; Wed, 05 Sep 2012 08:52:20 +0000 Received: from [85.158.138.51:40444] by server-3.bemta-3.messagelabs.com id 8D/68-21322-3C217405; Wed, 05 Sep 2012 08:52:19 +0000 X-Env-Sender: linux@eikelenboom.it X-Msg-Ref: server-11.tower-174.messagelabs.com!1346835132!28715162!1 X-Originating-IP: [188.40.164.121] X-SpamReason: No, hits=0.0 required=7.0 tests= X-StarScan-Received: X-StarScan-Version: 6.6.1.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 8004 invoked from network); 5 Sep 2012 08:52:12 -0000 Received: from static.121.164.40.188.clients.your-server.de (HELO smtp.eikelenboom.it) (188.40.164.121) by server-11.tower-174.messagelabs.com with AES256-SHA encrypted SMTP; 5 Sep 2012 08:52:12 -0000 Received: from 128-64-ftth.onsneteindhoven.nl ([88.159.64.128]:51391 helo=[172.16.1.20]) by smtp.eikelenboom.it with esmtpsa (TLS1.0:RSA_AES_256_CBC_SHA1:32) (Exim 4.72) (envelope-from ) id 1T9BHu-0007LZ-8N; Wed, 05 Sep 2012 10:48:42 +0200 Date: Wed, 5 Sep 2012 10:51:46 +0200 From: Sander Eikelenboom Organization: Eikelenboom IT services X-Priority: 3 (Normal) Message-ID: <102157590.20120905105146@eikelenboom.it> To: Ian Campbell In-Reply-To: <1346834067.17325.5.camel@zakaz.uk.xensource.com> References: <1346665360.25864.2.camel@zakaz.uk.xensource.com> <20120905025127.GI8912@reaktio.net> <1346834067.17325.5.camel@zakaz.uk.xensource.com> MIME-Version: 1.0 Cc: xen-users , =?utf-8?Q?Pasi_K=C3=A4rkk=C3=A4inen?= , xen-devel Subject: Re: [Xen-users] [Xen-devel] Xen 4.2.0 Release Plan / TODO X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: base64 Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org DQpXZWRuZXNkYXksIFNlcHRlbWJlciA1LCAyMDEyLCAxMDozNDoyNyBBTSwgeW91IHdyb3RlOgoK PiBPbiBXZWQsIDIwMTItMDktMDUgYXQgMDM6NTEgKzAxMDAsIFBhc2kgS8Okcmtrw6RpbmVuIHdy b3RlOgo+PiBPbiBNb24sIFNlcCAwMywgMjAxMiBhdCAxMDo0Mjo0MEFNICswMTAwLCBJYW4gQ2Ft cGJlbGwgd3JvdGU6Cj4+ID4gCj4+ID4gdG9vbHMsIG5pY2UgdG8gaGF2ZToKPj4gPiAKPj4gPiAg ICAgKiB4bCBjb21wYXRpYmlsaXR5IHdpdGggeG06Cj4+ID4gCj4+ICAgICAgICAgICAqIHhsIHN1 cHBvcnQgZm9yICJtb25pdG9yIiBjb21tYW5kLiBJIGRvbid0IHNlZSBpdCBtZW50aW9uZWQgaW4g eGwuY2ZnIGRvY3MuCj4+ICAgICAgICAgICAgICh0aGUgY29tbWFuZCB0byBlbmFibGUvZGlzYWJs ZSBhY2Nlc3MgdG8gdGhlIHBlci12bSBRZW11IG1vbml0b3IvY29uc29sZSAKPj4gICAgICAgICAg ICAgIGZyb20gVk5DLCB3aGljaCBpcyB1c3VhbGx5IGFjY2Vzc2VkIHdpdGggY3RybC1hbHQtMiku Cgo+IEkgY2FuJ3Qgc2VlIHRoYXQgaGFwcGVuaW5nIGZvciA0LjIuMCBub3cgSSdtIGFmcmFpZC4g UHJvYmFibHkgYmVzdCB0bwo+IGJyaW5nIGl0IHVwIHdpdGggR2VvcmdlIGluIHRoZSA0LjMgdGhy ZWFkLiBJdCBtaWdodCBiZSBhIGNhbmRpZGF0ZSBmb3IKPiA0LjIuMSBkZXBlbmRpbmcgb24gdGhl IHNpemUgb2YgdGhlIHBhdGNoLgoKSSBoYXZlIHRoZSBmZWVsaW5nIHRoZXJlIGFyZSBzdGlsbCBx dWl0ZSBzb21lIG9wdGlvbnMgbWlzc2luZyBmcm9tIHhsID8KQW5kIHNpbmNlIHhtIHdpbGwgYmUg Zm9ybWFsbHkgZGVwcmVjYXRlZCBwZXJoYXBzIHRoaXMgdXJnZXMgZm9yIGEgbGliZXJhbCB2aWV3 IG9uIGJhY2twb3J0aW5nIGNhbmRpZGF0ZXMuCgpIYXZpbmcgdG8gd2FpdCBhIGZ1bGwgcmVsZWFz ZSBjeWNsZSBmb3IgY29tcGF0aWJpbGl0eSBzdHVmZiBkb2Vzbid0IHNlZW0gdmVyeSBhdHRyYWN0 aXZlIGFuZCBtaWdodCBtYWtlIHBlb3BsZSBza2lwIDQuMi54IGFsdG9nZXRoZXIuCgpJIGhhdmUg anVzdCBzdGFydGVkIG9uIHRoZSBzaHV0ZG93biBvcHRpb24sIHNvIGhvcGVmdWxseSB0aGF0IGNh biBiZSBvZmYgdGhlIGxpc3QgdG9kYXkgOi0pCkFuZCBkbyBpdCBmb3IgeGwgcmVib290IHRvbywg aXQgYWxzbyBsYWNrcyB0aGUgIi1hIiBvcHRpb24uCgpBZnRlciB0aGF0IHBlcmhhcHMgdHJ5IHRv IG1ha2UgYSBjb21wYXJpc29uIGJldHdlZW4geG0gYW5kIHhsIHRvIHNlZSB3aGF0J3Mgc3RpbGwg bGFja2luZyBpbiB0ZXJtcyBvZiBjb21wYXRpYmlsaXR5IGFuZCBzZWUgd2hhdCB3b3VsZCBiZSBu aWNlIHRvIGhhdmUgaW1wbGVtZW50ZWQsIGFuZCB3aGF0IGNhbiBwZXJoYXBzIGJlIGxlZnQgb3V0 LgoKLS0KU2FuZGVyCgo+IElhbi4KCgoKCgpfX19fX19fX19fX19fX19fX19fX19fX19fX19fX19f X19fX19fX19fX19fX19fXwpYZW4tdXNlcnMgbWFpbGluZyBsaXN0Clhlbi11c2Vyc0BsaXN0cy54 ZW4ub3JnCmh0dHA6Ly9saXN0cy54ZW4ub3JnL3hlbi11c2Vycw== From xen-users-bounces@lists.xen.org Wed Sep 05 09:21:47 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Wed, 05 Sep 2012 09:21:47 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1T9BnE-0006TO-EP; Wed, 05 Sep 2012 09:21:04 +0000 Received: from mail27.messagelabs.com ([193.109.254.147]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1T9BnC-0006T9-Qf; Wed, 05 Sep 2012 09:21:03 +0000 X-Env-Sender: Ian.Campbell@citrix.com X-Msg-Ref: server-5.tower-27.messagelabs.com!1346836561!6228563!1 X-Originating-IP: [62.200.22.115] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogNjIuMjAwLjIyLjExNSA9PiAxMTE5ODY=\n X-StarScan-Received: X-StarScan-Version: 6.6.1.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 28716 invoked from network); 5 Sep 2012 09:16:02 -0000 Received: from smtp.ctxuk.citrix.com (HELO SMTP.EU.CITRIX.COM) (62.200.22.115) by server-5.tower-27.messagelabs.com with RC4-SHA encrypted SMTP; 5 Sep 2012 09:16:02 -0000 X-IronPort-AV: E=Sophos;i="4.80,372,1344211200"; d="scan'208";a="14352240" Received: from lonpmailmx01.citrite.net ([10.30.203.162]) by LONPIPO01.EU.CITRIX.COM with ESMTP/TLS/RC4-MD5; 05 Sep 2012 09:15:39 +0000 Received: from [10.80.2.42] (10.80.2.42) by LONPMAILMX01.citrite.net (10.30.203.162) with Microsoft SMTP Server id 8.3.279.1; Wed, 5 Sep 2012 10:15:39 +0100 Message-ID: <1346836538.17325.32.camel@zakaz.uk.xensource.com> From: Ian Campbell To: Sander Eikelenboom Date: Wed, 5 Sep 2012 10:15:38 +0100 In-Reply-To: <102157590.20120905105146@eikelenboom.it> References: <1346665360.25864.2.camel@zakaz.uk.xensource.com> <20120905025127.GI8912@reaktio.net> <1346834067.17325.5.camel@zakaz.uk.xensource.com> <102157590.20120905105146@eikelenboom.it> Organization: Citrix Systems, Inc. X-Mailer: Evolution 3.4.3-1 MIME-Version: 1.0 Cc: xen-users , Pasi =?ISO-8859-1?Q?K=E4rkk=E4inen?= , xen-devel Subject: Re: [Xen-users] [Xen-devel] Xen 4.2.0 Release Plan / TODO X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: base64 Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org T24gV2VkLCAyMDEyLTA5LTA1IGF0IDA5OjUxICswMTAwLCBTYW5kZXIgRWlrZWxlbmJvb20gd3Jv dGU6Cj4gV2VkbmVzZGF5LCBTZXB0ZW1iZXIgNSwgMjAxMiwgMTA6MzQ6MjcgQU0sIHlvdSB3cm90 ZToKPiAKPiA+IE9uIFdlZCwgMjAxMi0wOS0wNSBhdCAwMzo1MSArMDEwMCwgUGFzaSBLw6Rya2vD pGluZW4gd3JvdGU6Cj4gPj4gT24gTW9uLCBTZXAgMDMsIDIwMTIgYXQgMTA6NDI6NDBBTSArMDEw MCwgSWFuIENhbXBiZWxsIHdyb3RlOgo+ID4+ID4gCj4gPj4gPiB0b29scywgbmljZSB0byBoYXZl Ogo+ID4+ID4gCj4gPj4gPiAgICAgKiB4bCBjb21wYXRpYmlsaXR5IHdpdGggeG06Cj4gPj4gPiAK PiA+PiAgICAgICAgICAgKiB4bCBzdXBwb3J0IGZvciAibW9uaXRvciIgY29tbWFuZC4gSSBkb24n dCBzZWUgaXQgbWVudGlvbmVkIGluIHhsLmNmZyBkb2NzLgo+ID4+ICAgICAgICAgICAgICh0aGUg Y29tbWFuZCB0byBlbmFibGUvZGlzYWJsZSBhY2Nlc3MgdG8gdGhlIHBlci12bSBRZW11IG1vbml0 b3IvY29uc29sZSAKPiA+PiAgICAgICAgICAgICAgZnJvbSBWTkMsIHdoaWNoIGlzIHVzdWFsbHkg YWNjZXNzZWQgd2l0aCBjdHJsLWFsdC0yKS4KPiAKPiA+IEkgY2FuJ3Qgc2VlIHRoYXQgaGFwcGVu aW5nIGZvciA0LjIuMCBub3cgSSdtIGFmcmFpZC4gUHJvYmFibHkgYmVzdCB0bwo+ID4gYnJpbmcg aXQgdXAgd2l0aCBHZW9yZ2UgaW4gdGhlIDQuMyB0aHJlYWQuIEl0IG1pZ2h0IGJlIGEgY2FuZGlk YXRlIGZvcgo+ID4gNC4yLjEgZGVwZW5kaW5nIG9uIHRoZSBzaXplIG9mIHRoZSBwYXRjaC4KPiAK PiBJIGhhdmUgdGhlIGZlZWxpbmcgdGhlcmUgYXJlIHN0aWxsIHF1aXRlIHNvbWUgb3B0aW9ucyBt aXNzaW5nIGZyb20geGwgPwo+IEFuZCBzaW5jZSB4bSB3aWxsIGJlIGZvcm1hbGx5IGRlcHJlY2F0 ZWQgcGVyaGFwcyB0aGlzIHVyZ2VzIGZvciBhIGxpYmVyYWwgdmlldyBvbiBiYWNrcG9ydGluZyBj YW5kaWRhdGVzLgo+IAo+IEhhdmluZyB0byB3YWl0IGEgZnVsbCByZWxlYXNlIGN5Y2xlIGZvciBj b21wYXRpYmlsaXR5IHN0dWZmIGRvZXNuJ3QKPiBzZWVtIHZlcnkgYXR0cmFjdGl2ZSBhbmQgbWln aHQgbWFrZSBwZW9wbGUgc2tpcCA0LjIueCBhbHRvZ2V0aGVyLgoKV2UgaGF2ZSBwcmV0dHkgbXVj aCBhZ3JlZWQgdGhhdCBmb3IgYXQgbGVhc3QgNC4yLjEgKGFuZCBwZXJoYXBzIGxhdGVyCjQuMi54 IHRvbykgd2Ugd2lsbCB0YWtlIGEgc2xpZ2h0bHkgbW9yZSBsaWJlcmFsIHRoYW4gdXN1YWwgYXBw cm9hY2ggdG8KYmFja3BvcnRzIHdoaWNoIGltcHJvdmUgeGwncyBmZWF0dXJlIHBhcml0eSB3aXRo IHhlbmQuCgo+IEkgaGF2ZSBqdXN0IHN0YXJ0ZWQgb24gdGhlIHNodXRkb3duIG9wdGlvbiwgc28g aG9wZWZ1bGx5IHRoYXQgY2FuIGJlIG9mZiB0aGUgbGlzdCB0b2RheSA6LSkKPiBBbmQgZG8gaXQg Zm9yIHhsIHJlYm9vdCB0b28sIGl0IGFsc28gbGFja3MgdGhlICItYSIgb3B0aW9uLgoKR3JlYXQg dGhhbmtzLgoKPiBBZnRlciB0aGF0IHBlcmhhcHMgdHJ5IHRvIG1ha2UgYSBjb21wYXJpc29uIGJl dHdlZW4geG0gYW5kIHhsIHRvIHNlZQo+IHdoYXQncyBzdGlsbCBsYWNraW5nIGluIHRlcm1zIG9m IGNvbXBhdGliaWxpdHkgYW5kIHNlZSB3aGF0IHdvdWxkIGJlCj4gbmljZSB0byBoYXZlIGltcGxl bWVudGVkLCBhbmQgd2hhdCBjYW4gcGVyaGFwcyBiZSBsZWZ0IG91dC4KClRoYXQgd291bGQgYmUg Z3JlYXQuIE91ciBwcmlvcml0eSB3b3VsZCBiZSB0byBpbXBsZW1lbnQgZmVhdHVyZXMgd2hpY2gK cGVvcGxlIGFjdHVhbGx5IHVzZSBpbiBwcmFjdGljZS4KCgoKX19fX19fX19fX19fX19fX19fX19f X19fX19fX19fX19fX19fX19fX19fX19fX18KWGVuLXVzZXJzIG1haWxpbmcgbGlzdApYZW4tdXNl cnNAbGlzdHMueGVuLm9yZwpodHRwOi8vbGlzdHMueGVuLm9yZy94ZW4tdXNlcnM= From xen-users-bounces@lists.xen.org Wed Sep 05 09:21:47 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Wed, 05 Sep 2012 09:21:47 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1T9BnE-0006TO-EP; Wed, 05 Sep 2012 09:21:04 +0000 Received: from mail27.messagelabs.com ([193.109.254.147]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1T9BnC-0006T9-Qf; Wed, 05 Sep 2012 09:21:03 +0000 X-Env-Sender: Ian.Campbell@citrix.com X-Msg-Ref: server-5.tower-27.messagelabs.com!1346836561!6228563!1 X-Originating-IP: [62.200.22.115] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogNjIuMjAwLjIyLjExNSA9PiAxMTE5ODY=\n X-StarScan-Received: X-StarScan-Version: 6.6.1.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 28716 invoked from network); 5 Sep 2012 09:16:02 -0000 Received: from smtp.ctxuk.citrix.com (HELO SMTP.EU.CITRIX.COM) (62.200.22.115) by server-5.tower-27.messagelabs.com with RC4-SHA encrypted SMTP; 5 Sep 2012 09:16:02 -0000 X-IronPort-AV: E=Sophos;i="4.80,372,1344211200"; d="scan'208";a="14352240" Received: from lonpmailmx01.citrite.net ([10.30.203.162]) by LONPIPO01.EU.CITRIX.COM with ESMTP/TLS/RC4-MD5; 05 Sep 2012 09:15:39 +0000 Received: from [10.80.2.42] (10.80.2.42) by LONPMAILMX01.citrite.net (10.30.203.162) with Microsoft SMTP Server id 8.3.279.1; Wed, 5 Sep 2012 10:15:39 +0100 Message-ID: <1346836538.17325.32.camel@zakaz.uk.xensource.com> From: Ian Campbell To: Sander Eikelenboom Date: Wed, 5 Sep 2012 10:15:38 +0100 In-Reply-To: <102157590.20120905105146@eikelenboom.it> References: <1346665360.25864.2.camel@zakaz.uk.xensource.com> <20120905025127.GI8912@reaktio.net> <1346834067.17325.5.camel@zakaz.uk.xensource.com> <102157590.20120905105146@eikelenboom.it> Organization: Citrix Systems, Inc. X-Mailer: Evolution 3.4.3-1 MIME-Version: 1.0 Cc: xen-users , Pasi =?ISO-8859-1?Q?K=E4rkk=E4inen?= , xen-devel Subject: Re: [Xen-users] [Xen-devel] Xen 4.2.0 Release Plan / TODO X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: base64 Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org T24gV2VkLCAyMDEyLTA5LTA1IGF0IDA5OjUxICswMTAwLCBTYW5kZXIgRWlrZWxlbmJvb20gd3Jv dGU6Cj4gV2VkbmVzZGF5LCBTZXB0ZW1iZXIgNSwgMjAxMiwgMTA6MzQ6MjcgQU0sIHlvdSB3cm90 ZToKPiAKPiA+IE9uIFdlZCwgMjAxMi0wOS0wNSBhdCAwMzo1MSArMDEwMCwgUGFzaSBLw6Rya2vD pGluZW4gd3JvdGU6Cj4gPj4gT24gTW9uLCBTZXAgMDMsIDIwMTIgYXQgMTA6NDI6NDBBTSArMDEw MCwgSWFuIENhbXBiZWxsIHdyb3RlOgo+ID4+ID4gCj4gPj4gPiB0b29scywgbmljZSB0byBoYXZl Ogo+ID4+ID4gCj4gPj4gPiAgICAgKiB4bCBjb21wYXRpYmlsaXR5IHdpdGggeG06Cj4gPj4gPiAK PiA+PiAgICAgICAgICAgKiB4bCBzdXBwb3J0IGZvciAibW9uaXRvciIgY29tbWFuZC4gSSBkb24n dCBzZWUgaXQgbWVudGlvbmVkIGluIHhsLmNmZyBkb2NzLgo+ID4+ICAgICAgICAgICAgICh0aGUg Y29tbWFuZCB0byBlbmFibGUvZGlzYWJsZSBhY2Nlc3MgdG8gdGhlIHBlci12bSBRZW11IG1vbml0 b3IvY29uc29sZSAKPiA+PiAgICAgICAgICAgICAgZnJvbSBWTkMsIHdoaWNoIGlzIHVzdWFsbHkg YWNjZXNzZWQgd2l0aCBjdHJsLWFsdC0yKS4KPiAKPiA+IEkgY2FuJ3Qgc2VlIHRoYXQgaGFwcGVu aW5nIGZvciA0LjIuMCBub3cgSSdtIGFmcmFpZC4gUHJvYmFibHkgYmVzdCB0bwo+ID4gYnJpbmcg aXQgdXAgd2l0aCBHZW9yZ2UgaW4gdGhlIDQuMyB0aHJlYWQuIEl0IG1pZ2h0IGJlIGEgY2FuZGlk YXRlIGZvcgo+ID4gNC4yLjEgZGVwZW5kaW5nIG9uIHRoZSBzaXplIG9mIHRoZSBwYXRjaC4KPiAK PiBJIGhhdmUgdGhlIGZlZWxpbmcgdGhlcmUgYXJlIHN0aWxsIHF1aXRlIHNvbWUgb3B0aW9ucyBt aXNzaW5nIGZyb20geGwgPwo+IEFuZCBzaW5jZSB4bSB3aWxsIGJlIGZvcm1hbGx5IGRlcHJlY2F0 ZWQgcGVyaGFwcyB0aGlzIHVyZ2VzIGZvciBhIGxpYmVyYWwgdmlldyBvbiBiYWNrcG9ydGluZyBj YW5kaWRhdGVzLgo+IAo+IEhhdmluZyB0byB3YWl0IGEgZnVsbCByZWxlYXNlIGN5Y2xlIGZvciBj b21wYXRpYmlsaXR5IHN0dWZmIGRvZXNuJ3QKPiBzZWVtIHZlcnkgYXR0cmFjdGl2ZSBhbmQgbWln aHQgbWFrZSBwZW9wbGUgc2tpcCA0LjIueCBhbHRvZ2V0aGVyLgoKV2UgaGF2ZSBwcmV0dHkgbXVj aCBhZ3JlZWQgdGhhdCBmb3IgYXQgbGVhc3QgNC4yLjEgKGFuZCBwZXJoYXBzIGxhdGVyCjQuMi54 IHRvbykgd2Ugd2lsbCB0YWtlIGEgc2xpZ2h0bHkgbW9yZSBsaWJlcmFsIHRoYW4gdXN1YWwgYXBw cm9hY2ggdG8KYmFja3BvcnRzIHdoaWNoIGltcHJvdmUgeGwncyBmZWF0dXJlIHBhcml0eSB3aXRo IHhlbmQuCgo+IEkgaGF2ZSBqdXN0IHN0YXJ0ZWQgb24gdGhlIHNodXRkb3duIG9wdGlvbiwgc28g aG9wZWZ1bGx5IHRoYXQgY2FuIGJlIG9mZiB0aGUgbGlzdCB0b2RheSA6LSkKPiBBbmQgZG8gaXQg Zm9yIHhsIHJlYm9vdCB0b28sIGl0IGFsc28gbGFja3MgdGhlICItYSIgb3B0aW9uLgoKR3JlYXQg dGhhbmtzLgoKPiBBZnRlciB0aGF0IHBlcmhhcHMgdHJ5IHRvIG1ha2UgYSBjb21wYXJpc29uIGJl dHdlZW4geG0gYW5kIHhsIHRvIHNlZQo+IHdoYXQncyBzdGlsbCBsYWNraW5nIGluIHRlcm1zIG9m IGNvbXBhdGliaWxpdHkgYW5kIHNlZSB3aGF0IHdvdWxkIGJlCj4gbmljZSB0byBoYXZlIGltcGxl bWVudGVkLCBhbmQgd2hhdCBjYW4gcGVyaGFwcyBiZSBsZWZ0IG91dC4KClRoYXQgd291bGQgYmUg Z3JlYXQuIE91ciBwcmlvcml0eSB3b3VsZCBiZSB0byBpbXBsZW1lbnQgZmVhdHVyZXMgd2hpY2gK cGVvcGxlIGFjdHVhbGx5IHVzZSBpbiBwcmFjdGljZS4KCgoKX19fX19fX19fX19fX19fX19fX19f X19fX19fX19fX19fX19fX19fX19fX19fX18KWGVuLXVzZXJzIG1haWxpbmcgbGlzdApYZW4tdXNl cnNAbGlzdHMueGVuLm9yZwpodHRwOi8vbGlzdHMueGVuLm9yZy94ZW4tdXNlcnM= From xen-users-bounces@lists.xen.org Wed Sep 05 09:25:38 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Wed, 05 Sep 2012 09:25:38 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1T9Br2-0006n4-OI; Wed, 05 Sep 2012 09:25:00 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1T9Br1-0006me-74 for xen-users@lists.xen.org; Wed, 05 Sep 2012 09:24:59 +0000 Received: from [85.158.138.51:42449] by server-8.bemta-3.messagelabs.com id 8B/22-24700-76A17405; Wed, 05 Sep 2012 09:24:55 +0000 X-Env-Sender: Ian.Campbell@citrix.com X-Msg-Ref: server-13.tower-174.messagelabs.com!1346837094!10051547!1 X-Originating-IP: [62.200.22.115] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogNjIuMjAwLjIyLjExNSA9PiAxMTE5ODY=\n X-StarScan-Received: X-StarScan-Version: 6.6.1.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 11259 invoked from network); 5 Sep 2012 09:24:55 -0000 Received: from smtp.ctxuk.citrix.com (HELO SMTP.EU.CITRIX.COM) (62.200.22.115) by server-13.tower-174.messagelabs.com with RC4-SHA encrypted SMTP; 5 Sep 2012 09:24:55 -0000 X-IronPort-AV: E=Sophos;i="4.80,372,1344211200"; d="scan'208";a="14352546" Received: from lonpmailmx01.citrite.net ([10.30.203.162]) by LONPIPO01.EU.CITRIX.COM with ESMTP/TLS/RC4-MD5; 05 Sep 2012 09:24:54 +0000 Received: from [10.80.2.42] (10.80.2.42) by LONPMAILMX01.citrite.net (10.30.203.162) with Microsoft SMTP Server id 8.3.279.1; Wed, 5 Sep 2012 10:24:54 +0100 Message-ID: <1346837093.17325.38.camel@zakaz.uk.xensource.com> From: Ian Campbell To: Pasi =?ISO-8859-1?Q?K=E4rkk=E4inen?= Date: Wed, 5 Sep 2012 10:24:53 +0100 In-Reply-To: <20120905083921.GL8912@reaktio.net> References: <1346665360.25864.2.camel@zakaz.uk.xensource.com> <20120905025127.GI8912@reaktio.net> <1346834067.17325.5.camel@zakaz.uk.xensource.com> <20120905083921.GL8912@reaktio.net> Organization: Citrix Systems, Inc. X-Mailer: Evolution 3.4.3-1 MIME-Version: 1.0 Cc: xen-users , xen-devel Subject: Re: [Xen-users] [Xen-devel] Xen 4.2.0 Release Plan / TODO X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: base64 Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org T24gV2VkLCAyMDEyLTA5LTA1IGF0IDA5OjM5ICswMTAwLCBQYXNpIEvDpHJra8OkaW5lbiB3cm90 ZToKPiBPbiBXZWQsIFNlcCAwNSwgMjAxMiBhdCAwOTozNDoyN0FNICswMTAwLCBJYW4gQ2FtcGJl bGwgd3JvdGU6Cj4gPiBPbiBXZWQsIDIwMTItMDktMDUgYXQgMDM6NTEgKzAxMDAsIFBhc2kgS8Ok cmtrw6RpbmVuIHdyb3RlOgo+ID4gPiBPbiBNb24sIFNlcCAwMywgMjAxMiBhdCAxMDo0Mjo0MEFN ICswMTAwLCBJYW4gQ2FtcGJlbGwgd3JvdGU6Cj4gPiA+ID4gCj4gPiA+ID4gdG9vbHMsIG5pY2Ug dG8gaGF2ZToKPiA+ID4gPiAKPiA+ID4gPiAgICAgKiB4bCBjb21wYXRpYmlsaXR5IHdpdGggeG06 Cj4gPiA+ID4gCj4gPiA+ICAgICAgICAgICAqIHhsIHN1cHBvcnQgZm9yICJtb25pdG9yIiBjb21t YW5kLiBJIGRvbid0IHNlZSBpdCBtZW50aW9uZWQgaW4geGwuY2ZnIGRvY3MuCj4gPiA+ICAgICAg ICAgICAgICh0aGUgY29tbWFuZCB0byBlbmFibGUvZGlzYWJsZSBhY2Nlc3MgdG8gdGhlIHBlci12 bSBRZW11IG1vbml0b3IvY29uc29sZSAKPiA+ID4gICAgICAgICAgICAgIGZyb20gVk5DLCB3aGlj aCBpcyB1c3VhbGx5IGFjY2Vzc2VkIHdpdGggY3RybC1hbHQtMikuCj4gPiAKPiA+IEkgY2FuJ3Qg c2VlIHRoYXQgaGFwcGVuaW5nIGZvciA0LjIuMCBub3cgSSdtIGFmcmFpZC4gUHJvYmFibHkgYmVz dCB0bwo+ID4gYnJpbmcgaXQgdXAgd2l0aCBHZW9yZ2UgaW4gdGhlIDQuMyB0aHJlYWQuIEl0IG1p Z2h0IGJlIGEgY2FuZGlkYXRlIGZvcgo+ID4gNC4yLjEgZGVwZW5kaW5nIG9uIHRoZSBzaXplIG9m IHRoZSBwYXRjaC4KPiA+IAo+IAo+IFllcC4gSWYgIm1vbml0b3IyIGlzIGVuYWJsZWQgYXMgYSBk ZWZhdWx0IChJJ20gbm90IHN1cmUgYWJvdXQgdGhhdCksIHRoZW4gaXQncyBhIHNlY3VyaXR5IGlz c3VlLi4gCgpSaWdodCwgd2UgKmRlZmluaXRlbHkqIG5lZWQgdG8gbWFrZSBzdXJlIHRoaXMgaXMg bm90IHRoZSBjYXNlIGJlZm9yZQo0LjIuMC4gSSBjb25zaWRlciB0aGlzIGFzcGVjdCBvZiBtb25p dG9yIHN1cHBvcnQgYSBibG9ja2VyLgoKPiBVc2VyIGhhdmluZyBhIFZOQyBzZXNzaW9uIHRvIHRo ZSBjb25zb2xlIG9mIHRoZSBWTSBjYW4gcnVuIFFlbXUKPiBjb21tYW5kcywgc28gZm9yIGV4YW1w bGUgbWFwIC5pc28gZmlsZXMgZnJvbSBkb20wIGV0Yy4uCgpJYW4uCgoKX19fX19fX19fX19fX19f X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18KWGVuLXVzZXJzIG1haWxpbmcgbGlzdApY ZW4tdXNlcnNAbGlzdHMueGVuLm9yZwpodHRwOi8vbGlzdHMueGVuLm9yZy94ZW4tdXNlcnM= From xen-users-bounces@lists.xen.org Wed Sep 05 09:25:38 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Wed, 05 Sep 2012 09:25:38 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1T9Br2-0006n4-OI; Wed, 05 Sep 2012 09:25:00 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1T9Br1-0006me-74 for xen-users@lists.xen.org; Wed, 05 Sep 2012 09:24:59 +0000 Received: from [85.158.138.51:42449] by server-8.bemta-3.messagelabs.com id 8B/22-24700-76A17405; Wed, 05 Sep 2012 09:24:55 +0000 X-Env-Sender: Ian.Campbell@citrix.com X-Msg-Ref: server-13.tower-174.messagelabs.com!1346837094!10051547!1 X-Originating-IP: [62.200.22.115] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogNjIuMjAwLjIyLjExNSA9PiAxMTE5ODY=\n X-StarScan-Received: X-StarScan-Version: 6.6.1.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 11259 invoked from network); 5 Sep 2012 09:24:55 -0000 Received: from smtp.ctxuk.citrix.com (HELO SMTP.EU.CITRIX.COM) (62.200.22.115) by server-13.tower-174.messagelabs.com with RC4-SHA encrypted SMTP; 5 Sep 2012 09:24:55 -0000 X-IronPort-AV: E=Sophos;i="4.80,372,1344211200"; d="scan'208";a="14352546" Received: from lonpmailmx01.citrite.net ([10.30.203.162]) by LONPIPO01.EU.CITRIX.COM with ESMTP/TLS/RC4-MD5; 05 Sep 2012 09:24:54 +0000 Received: from [10.80.2.42] (10.80.2.42) by LONPMAILMX01.citrite.net (10.30.203.162) with Microsoft SMTP Server id 8.3.279.1; Wed, 5 Sep 2012 10:24:54 +0100 Message-ID: <1346837093.17325.38.camel@zakaz.uk.xensource.com> From: Ian Campbell To: Pasi =?ISO-8859-1?Q?K=E4rkk=E4inen?= Date: Wed, 5 Sep 2012 10:24:53 +0100 In-Reply-To: <20120905083921.GL8912@reaktio.net> References: <1346665360.25864.2.camel@zakaz.uk.xensource.com> <20120905025127.GI8912@reaktio.net> <1346834067.17325.5.camel@zakaz.uk.xensource.com> <20120905083921.GL8912@reaktio.net> Organization: Citrix Systems, Inc. X-Mailer: Evolution 3.4.3-1 MIME-Version: 1.0 Cc: xen-users , xen-devel Subject: Re: [Xen-users] [Xen-devel] Xen 4.2.0 Release Plan / TODO X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: base64 Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org T24gV2VkLCAyMDEyLTA5LTA1IGF0IDA5OjM5ICswMTAwLCBQYXNpIEvDpHJra8OkaW5lbiB3cm90 ZToKPiBPbiBXZWQsIFNlcCAwNSwgMjAxMiBhdCAwOTozNDoyN0FNICswMTAwLCBJYW4gQ2FtcGJl bGwgd3JvdGU6Cj4gPiBPbiBXZWQsIDIwMTItMDktMDUgYXQgMDM6NTEgKzAxMDAsIFBhc2kgS8Ok cmtrw6RpbmVuIHdyb3RlOgo+ID4gPiBPbiBNb24sIFNlcCAwMywgMjAxMiBhdCAxMDo0Mjo0MEFN ICswMTAwLCBJYW4gQ2FtcGJlbGwgd3JvdGU6Cj4gPiA+ID4gCj4gPiA+ID4gdG9vbHMsIG5pY2Ug dG8gaGF2ZToKPiA+ID4gPiAKPiA+ID4gPiAgICAgKiB4bCBjb21wYXRpYmlsaXR5IHdpdGggeG06 Cj4gPiA+ID4gCj4gPiA+ICAgICAgICAgICAqIHhsIHN1cHBvcnQgZm9yICJtb25pdG9yIiBjb21t YW5kLiBJIGRvbid0IHNlZSBpdCBtZW50aW9uZWQgaW4geGwuY2ZnIGRvY3MuCj4gPiA+ICAgICAg ICAgICAgICh0aGUgY29tbWFuZCB0byBlbmFibGUvZGlzYWJsZSBhY2Nlc3MgdG8gdGhlIHBlci12 bSBRZW11IG1vbml0b3IvY29uc29sZSAKPiA+ID4gICAgICAgICAgICAgIGZyb20gVk5DLCB3aGlj aCBpcyB1c3VhbGx5IGFjY2Vzc2VkIHdpdGggY3RybC1hbHQtMikuCj4gPiAKPiA+IEkgY2FuJ3Qg c2VlIHRoYXQgaGFwcGVuaW5nIGZvciA0LjIuMCBub3cgSSdtIGFmcmFpZC4gUHJvYmFibHkgYmVz dCB0bwo+ID4gYnJpbmcgaXQgdXAgd2l0aCBHZW9yZ2UgaW4gdGhlIDQuMyB0aHJlYWQuIEl0IG1p Z2h0IGJlIGEgY2FuZGlkYXRlIGZvcgo+ID4gNC4yLjEgZGVwZW5kaW5nIG9uIHRoZSBzaXplIG9m IHRoZSBwYXRjaC4KPiA+IAo+IAo+IFllcC4gSWYgIm1vbml0b3IyIGlzIGVuYWJsZWQgYXMgYSBk ZWZhdWx0IChJJ20gbm90IHN1cmUgYWJvdXQgdGhhdCksIHRoZW4gaXQncyBhIHNlY3VyaXR5IGlz c3VlLi4gCgpSaWdodCwgd2UgKmRlZmluaXRlbHkqIG5lZWQgdG8gbWFrZSBzdXJlIHRoaXMgaXMg bm90IHRoZSBjYXNlIGJlZm9yZQo0LjIuMC4gSSBjb25zaWRlciB0aGlzIGFzcGVjdCBvZiBtb25p dG9yIHN1cHBvcnQgYSBibG9ja2VyLgoKPiBVc2VyIGhhdmluZyBhIFZOQyBzZXNzaW9uIHRvIHRo ZSBjb25zb2xlIG9mIHRoZSBWTSBjYW4gcnVuIFFlbXUKPiBjb21tYW5kcywgc28gZm9yIGV4YW1w bGUgbWFwIC5pc28gZmlsZXMgZnJvbSBkb20wIGV0Yy4uCgpJYW4uCgoKX19fX19fX19fX19fX19f X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18KWGVuLXVzZXJzIG1haWxpbmcgbGlzdApY ZW4tdXNlcnNAbGlzdHMueGVuLm9yZwpodHRwOi8vbGlzdHMueGVuLm9yZy94ZW4tdXNlcnM= From xen-users-bounces@lists.xen.org Wed Sep 05 09:41:29 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Wed, 05 Sep 2012 09:41:29 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1T9C6C-0007RD-Ua; Wed, 05 Sep 2012 09:40:40 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1T9C6B-0007Qt-Dw for xen-users@lists.xen.org; Wed, 05 Sep 2012 09:40:39 +0000 Received: from [85.158.139.83:61115] by server-11.bemta-5.messagelabs.com id 1F/C8-24658-51E17405; Wed, 05 Sep 2012 09:40:37 +0000 X-Env-Sender: Ian.Jackson@eu.citrix.com X-Msg-Ref: server-13.tower-182.messagelabs.com!1346837936!28122186!1 X-Originating-IP: [62.200.22.115] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogNjIuMjAwLjIyLjExNSA9PiAxMTE5ODY=\n X-StarScan-Received: X-StarScan-Version: 6.6.1.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 19268 invoked from network); 5 Sep 2012 09:38:57 -0000 Received: from smtp.ctxuk.citrix.com (HELO SMTP.EU.CITRIX.COM) (62.200.22.115) by server-13.tower-182.messagelabs.com with RC4-SHA encrypted SMTP; 5 Sep 2012 09:38:57 -0000 X-IronPort-AV: E=Sophos;i="4.80,372,1344211200"; d="scan'208";a="14353051" Received: from lonpmailmx01.citrite.net ([10.30.203.162]) by LONPIPO01.EU.CITRIX.COM with ESMTP/TLS/RC4-MD5; 05 Sep 2012 09:38:44 +0000 Received: from norwich.cam.xci-test.com (10.80.248.129) by smtprelay.citrix.com (10.30.203.162) with Microsoft SMTP Server id 8.3.279.1; Wed, 5 Sep 2012 10:38:44 +0100 Received: from mariner.cam.xci-test.com ([10.80.2.22] helo=mariner.uk.xensource.com ident=Debian-exim) by norwich.cam.xci-test.com with esmtp (Exim 4.72) (envelope-from ) id 1T9C4K-0001aP-6p; Wed, 05 Sep 2012 09:38:44 +0000 Received: from iwj by mariner.uk.xensource.com with local (Exim 4.72) (envelope-from ) id 1T9C4K-0003Su-2p; Wed, 05 Sep 2012 10:38:44 +0100 Date: Wed, 5 Sep 2012 10:38:44 +0100 Message-ID: Content-Type: multipart/mixed; boundary="=separator"; charset="utf-8" MIME-Version: 1.0 X-Mailer: MIME-tools 5.428 (Entity 5.428) To: xen-announce@lists.xen.org, xen-devel@lists.xen.org, xen-users@lists.xen.org, oss-security@lists.openwall.com From: Xen.org security team Cc: "Xen.org security team" Subject: [Xen-users] Xen Security Advisory 12 (CVE-2012-3494) - hypercall set_debugreg vulnerability X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org --=separator Content-Type: text/plain; charset="utf-8" Content-Disposition: inline Content-Transfer-Encoding: 7bit -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Xen Security Advisory CVE-2012-3494 / XSA-12 version 3 hypercall set_debugreg vulnerability UPDATES IN VERSION 3 ==================== Public release. ISSUE DESCRIPTION ================= set_debugreg allows writes to reserved bits of the DR7 debug control register on x86-64. IMPACT ====== A malicious guest can cause the host to crash, leading to a DoS. If the vulnerable hypervisor is run on future hardware, the impact of the vulnerability might be widened depending on the future assignment of the currently-reserved debug register bits. VULNERABLE SYSTEMS ================== All systems running 64-bit paravirtualised guests. The vulnerability dates back to at least Xen 4.0. 4.0, 4.1, the 4.2 RCs, and xen-unstable.hg are all vulnerable. MITIGATION ========== This issue can be mitigated by ensuring (inside the guest) that the kernel is trustworthy, or by running only 32-bit or HVM guests. RESOLUTION ========== Applying the appropriate attached patch will resolve the issue. PATCH INFORMATION ================= The attached patch resolves this issue: Xen unstable, 4.1 and 4.0 xsa12-all.patch $ sha256sum xsa12-all.patch 2415ee133e28b1c848c5ae3ce766cc2a67009bad8d026879030a6511b85dbc13 xsa12-all.patch -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.10 (GNU/Linux) iQEcBAEBAgAGBQJQRx0+AAoJEIP+FMlX6CvZnMAH/0fcm9nfiChokydCyqXgdKtJ U2NqeqKzEP6emwLE+cvc+2EBP40fiBXsNATVdXc6Vx15eyzSMfJD3ndYF9OaKMVH MVP6KU/tyK1G/9WgQK9PHBj/Kzp8hwrY0Qw45od7z+R7XMGieLH9l1O1xwkNCYDw R8Xy2GI9IqsXLNpwy3BFYSyGYIX9o8/aBx4ZxHCV8H0OYUWv5hDGZZVXPDqGm11c N+qmUaPV2QlW8Aoww1SiwW5E+/CpyJT5+awEMgZ4IOHPbCBXJfyXbw4aMM2q5Soe mStqvPKL4H10SahaygdjxO+e4NqCHao0rYUXXpUr+aikIXvEearukp3FezR5IUE= =/LmZ -----END PGP SIGNATURE----- --=separator Content-Type: application/octet-stream; name="xsa12-all.patch" Content-Disposition: attachment; filename="xsa12-all.patch" Content-Transfer-Encoding: base64 eGVuOiBwcmV2ZW50IGEgNjQgYml0IGd1ZXN0IHNldHRpbmcgcmVzZXJ2ZWQg Yml0cyBpbiBEUjcKClRoZSB1cHBlciAzMiBiaXRzIG9mIHRoaXMgcmVnaXN0 ZXIgYXJlIHJlc2VydmVkIGFuZCBzaG91bGQgYmUgd3JpdHRlbiBhcwp6ZXJv LgoKVGhpcyBpcyBYU0EtMTIgLyBDVkUtMjAxMi0zNDk0CgpTaWduZWQtb2Zm LWJ5OiBKYW4gQmV1bGljaCA8amJldWxpY2hAc3VzZS5jb20+ClJldmlld2Vk LWJ5OiBJYW4gQ2FtcGJlbGwgPGlhbi5jYW1wYmVsbEBjaXRyaXguY29tPgoK ZGlmZiAtciAzNTNiYzA4MDFiMTEgeGVuL2luY2x1ZGUvYXNtLXg4Ni9kZWJ1 Z3JlZy5oCi0tLSBhL3hlbi9pbmNsdWRlL2FzbS14ODYvZGVidWdyZWcuaAlN b24gQXVnIDA2IDEyOjI4OjAzIDIwMTIgKzAxMDAKKysrIGIveGVuL2luY2x1 ZGUvYXNtLXg4Ni9kZWJ1Z3JlZy5oCVdlZCBBdWcgMTUgMTI6MDA6MjEgMjAx MiArMDEwMApAQCAtNTgsNyArNTgsNyBAQAogICAgV2UgY2FuIHNsb3cgdGhl IGluc3RydWN0aW9uIHBpcGVsaW5lIGZvciBpbnN0cnVjdGlvbnMgY29taW5n IHZpYSB0aGUKICAgIGdkdCBvciB0aGUgbGR0IGlmIHdlIHdhbnQgdG8uICBJ IGFtIG5vdCBzdXJlIHdoeSB0aGlzIGlzIGFuIGFkdmFudGFnZSAqLwogCi0j ZGVmaW5lIERSX0NPTlRST0xfUkVTRVJWRURfWkVSTyAoMHgwMDAwZDgwMHVs KSAvKiBSZXNlcnZlZCwgcmVhZCBhcyB6ZXJvICovCisjZGVmaW5lIERSX0NP TlRST0xfUkVTRVJWRURfWkVSTyAofjB4ZmZmZjI3ZmZ1bCkgLyogUmVzZXJ2 ZWQsIHJlYWQgYXMgemVybyAqLwogI2RlZmluZSBEUl9DT05UUk9MX1JFU0VS VkVEX09ORSAgKDB4MDAwMDA0MDB1bCkgLyogUmVzZXJ2ZWQsIHJlYWQgYXMg b25lICovCiAjZGVmaW5lIERSX0xPQ0FMX0VYQUNUX0VOQUJMRSAgICAoMHgw MDAwMDEwMHVsKSAvKiBMb2NhbCBleGFjdCBlbmFibGUgKi8KICNkZWZpbmUg RFJfR0xPQkFMX0VYQUNUX0VOQUJMRSAgICgweDAwMDAwMjAwdWwpIC8qIEds b2JhbCBleGFjdCBlbmFibGUgKi8K --=separator Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users --=separator-- From xen-users-bounces@lists.xen.org Wed Sep 05 09:41:29 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Wed, 05 Sep 2012 09:41:29 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1T9C6C-0007RD-Ua; Wed, 05 Sep 2012 09:40:40 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1T9C6B-0007Qt-Dw for xen-users@lists.xen.org; Wed, 05 Sep 2012 09:40:39 +0000 Received: from [85.158.139.83:61115] by server-11.bemta-5.messagelabs.com id 1F/C8-24658-51E17405; Wed, 05 Sep 2012 09:40:37 +0000 X-Env-Sender: Ian.Jackson@eu.citrix.com X-Msg-Ref: server-13.tower-182.messagelabs.com!1346837936!28122186!1 X-Originating-IP: [62.200.22.115] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogNjIuMjAwLjIyLjExNSA9PiAxMTE5ODY=\n X-StarScan-Received: X-StarScan-Version: 6.6.1.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 19268 invoked from network); 5 Sep 2012 09:38:57 -0000 Received: from smtp.ctxuk.citrix.com (HELO SMTP.EU.CITRIX.COM) (62.200.22.115) by server-13.tower-182.messagelabs.com with RC4-SHA encrypted SMTP; 5 Sep 2012 09:38:57 -0000 X-IronPort-AV: E=Sophos;i="4.80,372,1344211200"; d="scan'208";a="14353051" Received: from lonpmailmx01.citrite.net ([10.30.203.162]) by LONPIPO01.EU.CITRIX.COM with ESMTP/TLS/RC4-MD5; 05 Sep 2012 09:38:44 +0000 Received: from norwich.cam.xci-test.com (10.80.248.129) by smtprelay.citrix.com (10.30.203.162) with Microsoft SMTP Server id 8.3.279.1; Wed, 5 Sep 2012 10:38:44 +0100 Received: from mariner.cam.xci-test.com ([10.80.2.22] helo=mariner.uk.xensource.com ident=Debian-exim) by norwich.cam.xci-test.com with esmtp (Exim 4.72) (envelope-from ) id 1T9C4K-0001aP-6p; Wed, 05 Sep 2012 09:38:44 +0000 Received: from iwj by mariner.uk.xensource.com with local (Exim 4.72) (envelope-from ) id 1T9C4K-0003Su-2p; Wed, 05 Sep 2012 10:38:44 +0100 Date: Wed, 5 Sep 2012 10:38:44 +0100 Message-ID: Content-Type: multipart/mixed; boundary="=separator"; charset="utf-8" MIME-Version: 1.0 X-Mailer: MIME-tools 5.428 (Entity 5.428) To: xen-announce@lists.xen.org, xen-devel@lists.xen.org, xen-users@lists.xen.org, oss-security@lists.openwall.com From: Xen.org security team Cc: "Xen.org security team" Subject: [Xen-users] Xen Security Advisory 12 (CVE-2012-3494) - hypercall set_debugreg vulnerability X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org --=separator Content-Type: text/plain; charset="utf-8" Content-Disposition: inline Content-Transfer-Encoding: 7bit -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Xen Security Advisory CVE-2012-3494 / XSA-12 version 3 hypercall set_debugreg vulnerability UPDATES IN VERSION 3 ==================== Public release. ISSUE DESCRIPTION ================= set_debugreg allows writes to reserved bits of the DR7 debug control register on x86-64. IMPACT ====== A malicious guest can cause the host to crash, leading to a DoS. If the vulnerable hypervisor is run on future hardware, the impact of the vulnerability might be widened depending on the future assignment of the currently-reserved debug register bits. VULNERABLE SYSTEMS ================== All systems running 64-bit paravirtualised guests. The vulnerability dates back to at least Xen 4.0. 4.0, 4.1, the 4.2 RCs, and xen-unstable.hg are all vulnerable. MITIGATION ========== This issue can be mitigated by ensuring (inside the guest) that the kernel is trustworthy, or by running only 32-bit or HVM guests. RESOLUTION ========== Applying the appropriate attached patch will resolve the issue. PATCH INFORMATION ================= The attached patch resolves this issue: Xen unstable, 4.1 and 4.0 xsa12-all.patch $ sha256sum xsa12-all.patch 2415ee133e28b1c848c5ae3ce766cc2a67009bad8d026879030a6511b85dbc13 xsa12-all.patch -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.10 (GNU/Linux) iQEcBAEBAgAGBQJQRx0+AAoJEIP+FMlX6CvZnMAH/0fcm9nfiChokydCyqXgdKtJ U2NqeqKzEP6emwLE+cvc+2EBP40fiBXsNATVdXc6Vx15eyzSMfJD3ndYF9OaKMVH MVP6KU/tyK1G/9WgQK9PHBj/Kzp8hwrY0Qw45od7z+R7XMGieLH9l1O1xwkNCYDw R8Xy2GI9IqsXLNpwy3BFYSyGYIX9o8/aBx4ZxHCV8H0OYUWv5hDGZZVXPDqGm11c N+qmUaPV2QlW8Aoww1SiwW5E+/CpyJT5+awEMgZ4IOHPbCBXJfyXbw4aMM2q5Soe mStqvPKL4H10SahaygdjxO+e4NqCHao0rYUXXpUr+aikIXvEearukp3FezR5IUE= =/LmZ -----END PGP SIGNATURE----- --=separator Content-Type: application/octet-stream; name="xsa12-all.patch" Content-Disposition: attachment; filename="xsa12-all.patch" Content-Transfer-Encoding: base64 eGVuOiBwcmV2ZW50IGEgNjQgYml0IGd1ZXN0IHNldHRpbmcgcmVzZXJ2ZWQg Yml0cyBpbiBEUjcKClRoZSB1cHBlciAzMiBiaXRzIG9mIHRoaXMgcmVnaXN0 ZXIgYXJlIHJlc2VydmVkIGFuZCBzaG91bGQgYmUgd3JpdHRlbiBhcwp6ZXJv LgoKVGhpcyBpcyBYU0EtMTIgLyBDVkUtMjAxMi0zNDk0CgpTaWduZWQtb2Zm LWJ5OiBKYW4gQmV1bGljaCA8amJldWxpY2hAc3VzZS5jb20+ClJldmlld2Vk LWJ5OiBJYW4gQ2FtcGJlbGwgPGlhbi5jYW1wYmVsbEBjaXRyaXguY29tPgoK ZGlmZiAtciAzNTNiYzA4MDFiMTEgeGVuL2luY2x1ZGUvYXNtLXg4Ni9kZWJ1 Z3JlZy5oCi0tLSBhL3hlbi9pbmNsdWRlL2FzbS14ODYvZGVidWdyZWcuaAlN b24gQXVnIDA2IDEyOjI4OjAzIDIwMTIgKzAxMDAKKysrIGIveGVuL2luY2x1 ZGUvYXNtLXg4Ni9kZWJ1Z3JlZy5oCVdlZCBBdWcgMTUgMTI6MDA6MjEgMjAx MiArMDEwMApAQCAtNTgsNyArNTgsNyBAQAogICAgV2UgY2FuIHNsb3cgdGhl IGluc3RydWN0aW9uIHBpcGVsaW5lIGZvciBpbnN0cnVjdGlvbnMgY29taW5n IHZpYSB0aGUKICAgIGdkdCBvciB0aGUgbGR0IGlmIHdlIHdhbnQgdG8uICBJ IGFtIG5vdCBzdXJlIHdoeSB0aGlzIGlzIGFuIGFkdmFudGFnZSAqLwogCi0j ZGVmaW5lIERSX0NPTlRST0xfUkVTRVJWRURfWkVSTyAoMHgwMDAwZDgwMHVs KSAvKiBSZXNlcnZlZCwgcmVhZCBhcyB6ZXJvICovCisjZGVmaW5lIERSX0NP TlRST0xfUkVTRVJWRURfWkVSTyAofjB4ZmZmZjI3ZmZ1bCkgLyogUmVzZXJ2 ZWQsIHJlYWQgYXMgemVybyAqLwogI2RlZmluZSBEUl9DT05UUk9MX1JFU0VS VkVEX09ORSAgKDB4MDAwMDA0MDB1bCkgLyogUmVzZXJ2ZWQsIHJlYWQgYXMg b25lICovCiAjZGVmaW5lIERSX0xPQ0FMX0VYQUNUX0VOQUJMRSAgICAoMHgw MDAwMDEwMHVsKSAvKiBMb2NhbCBleGFjdCBlbmFibGUgKi8KICNkZWZpbmUg RFJfR0xPQkFMX0VYQUNUX0VOQUJMRSAgICgweDAwMDAwMjAwdWwpIC8qIEds b2JhbCBleGFjdCBlbmFibGUgKi8K --=separator Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users --=separator-- From xen-users-bounces@lists.xen.org Wed Sep 05 10:14:58 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Wed, 05 Sep 2012 10:14:58 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1T9Cce-0000dI-9r; Wed, 05 Sep 2012 10:14:12 +0000 Received: from mail27.messagelabs.com ([193.109.254.147]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1T9Ccb-0000c6-IO; Wed, 05 Sep 2012 10:14:09 +0000 X-Env-Sender: Ian.Jackson@eu.citrix.com X-Msg-Ref: server-3.tower-27.messagelabs.com!1346840028!8841583!1 X-Originating-IP: [62.200.22.115] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogNjIuMjAwLjIyLjExNSA9PiAxMTE5ODY=\n X-StarScan-Received: X-StarScan-Version: 6.6.1.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 32669 invoked from network); 5 Sep 2012 10:13:50 -0000 Received: from smtp.eu.citrix.com (HELO SMTP.EU.CITRIX.COM) (62.200.22.115) by server-3.tower-27.messagelabs.com with RC4-SHA encrypted SMTP; 5 Sep 2012 10:13:50 -0000 X-IronPort-AV: E=Sophos;i="4.80,372,1344211200"; d="scan'208";a="14354132" Received: from lonpmailmx01.citrite.net ([10.30.203.162]) by LONPIPO01.EU.CITRIX.COM with ESMTP/TLS/RC4-MD5; 05 Sep 2012 10:13:31 +0000 Received: from norwich.cam.xci-test.com (10.80.248.129) by smtprelay.citrix.com (10.30.203.162) with Microsoft SMTP Server id 8.3.279.1; Wed, 5 Sep 2012 11:13:31 +0100 Received: from mariner.cam.xci-test.com ([10.80.2.22] helo=mariner.uk.xensource.com ident=Debian-exim) by norwich.cam.xci-test.com with esmtp (Exim 4.72) (envelope-from ) id 1T9Cbz-0001sP-5Y; Wed, 05 Sep 2012 10:13:31 +0000 Received: from iwj by mariner.uk.xensource.com with local (Exim 4.72) (envelope-from ) id 1T9Cbz-0003ZK-24; Wed, 05 Sep 2012 11:13:31 +0100 Date: Wed, 5 Sep 2012 11:13:31 +0100 Message-ID: Content-Type: multipart/mixed; boundary="=separator"; charset="utf-8" MIME-Version: 1.0 X-Mailer: MIME-tools 5.428 (Entity 5.428) To: xen-announce@lists.xen.org, xen-devel@lists.xen.org, xen-users@lists.xen.org, oss-security@lists.openwall.com From: Xen.org security team Cc: "Xen.org security team" Subject: [Xen-users] Xen Security Advisory 13 (CVE-2012-3495) - hypercall physdev_get_free_pirq vulnerability X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org --=separator Content-Type: text/plain; charset="utf-8" Content-Disposition: inline Content-Transfer-Encoding: 7bit -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Xen Security Advisory CVE-2012-3495 / XSA-13 version 3 hypercall physdev_get_free_pirq vulnerability UPDATES IN VERSION 3 ==================== Public release. Credit Matthew Daley. ISSUE DESCRIPTION ================= PHYSDEVOP_get_free_pirq does not check that its call to get_free_pirq succeeded, and if it fails will use the error code as an array index. IMPACT ====== A malicious guest might be able to cause the host to crash, leading to a DoS, depending on the exact memory layout. Privilege escalation is a theoretical possibility which cannot be ruled out, but is considered unlikely. VULNERABLE SYSTEMS ================== All Xen systems. Xen 4.1 is vulnerable. Other versions of Xen are not vulnerable. MITIGATION ========== This issue can be mitigated by ensuring (inside the guest) that the kernel is trustworthy and avoiding situations where something might repeatedly cause the attempted allocation of a physical irq. RESOLUTION ========== Applying the appropriate attached patch will resolve the issue. CREDIT ====== Thanks to Matthew Daley for finding this vulnerability (and that in XSA-12) and notifying the Xen.org security team. PATCH INFORMATION ================= The attached patches resolve this issue Xen 4.1, 4.1.x xsa13-xen-4.1.patch $ sha256sum xsa13-*.patch ad6e3e40ff56c7c25a94d8d9763d4b49f07802b90b4362ddbe4c86bf285c1239 xsa13-xen-4.1.patch -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.10 (GNU/Linux) iQEcBAEBAgAGBQJQRyVqAAoJEIP+FMlX6CvZjrcH/A0xq4dTMtJpUc1WHyUi2aXd 5ap+AA8w0XHLdosXnbxnsTCSsAdkUeBlPkqZAoGxrCGYrzP83T0cPrz8qjzN64KE Jaei9prTk7VFHa9aAz3OqFYjYd/d21CxI4goGJ4Z0tygys4lmkDeex2kEAj5dq7b 0FLj6aIAVFYI3mWMztx4poOrz/BSCMk1YtrV5hZaY8i7Y6nhaOsPISveS0Dv4FPm YDGc93ykhOwEWCNqWFQGVndRihgUWQIUcb7f2SUfOC/FvbcJHGlP4Aojl4LUePqM bi/CR9cPESr7x1+1vcGUZybXALsRMBCJPrx1td3OCgqx8bwAbsQIszuFaWTtajY= =s7wG -----END PGP SIGNATURE----- --=separator Content-Type: application/octet-stream; name="xsa13-xen-4.1.patch" Content-Disposition: attachment; filename="xsa13-xen-4.1.patch" Content-Transfer-Encoding: base64 eGVuOiBoYW5kbGUgb3V0LW9mLXBpcnEgY29uZGl0aW9uIGNvcnJlY3RseSBp biBQSFlTREVWT1BfZ2V0X2ZyZWVfcGlycQoKVGhpcyBpcyBYU0EtMTMgLyBD VkUtMjAxMi0zNDk1CgpTaWduZWQtb2ZmLWJ5OiBJYW4gQ2FtcGJlbGwgPGlh bi5jYW1wYmVsbEBjaXRyaXguY29tPgpTaWduZWQtb2ZmLWJ5OiBKYW4gQmV1 bGljaCA8SkJldWxpY2hAc3VzZS5jb20+CgpkaWZmIC1yIDEyMjVhZmYwNWRk MiB4ZW4vYXJjaC94ODYvcGh5c2Rldi5jCi0tLSBhL3hlbi9hcmNoL3g4Ni9w aHlzZGV2LmMJVGh1IEF1ZyAwOSAxNjo0ODowNyAyMDEyICswMTAwCisrKyBi L3hlbi9hcmNoL3g4Ni9waHlzZGV2LmMJVGh1IEF1ZyAxNiAxMTowNzozNiAy MDEyICswMTAwCkBAIC01ODcsMTEgKzU4NywxNiBAQCByZXRfdCBkb19waHlz ZGV2X29wKGludCBjbWQsIFhFTl9HVUVTVF9ICiAgICAgICAgICAgICBicmVh azsKIAogICAgICAgICBzcGluX2xvY2soJmQtPmV2ZW50X2xvY2spOwotICAg ICAgICBvdXQucGlycSA9IGdldF9mcmVlX3BpcnEoZCwgb3V0LnR5cGUsIDAp OwotICAgICAgICBkLT5hcmNoLnBpcnFfaXJxW291dC5waXJxXSA9IFBJUlFf QUxMT0NBVEVEOworICAgICAgICByZXQgPSBnZXRfZnJlZV9waXJxKGQsIG91 dC50eXBlLCAwKTsKKyAgICAgICAgaWYgKCByZXQgPj0gMCApCisgICAgICAg ICAgICBkLT5hcmNoLnBpcnFfaXJxW3JldF0gPSBQSVJRX0FMTE9DQVRFRDsK ICAgICAgICAgc3Bpbl91bmxvY2soJmQtPmV2ZW50X2xvY2spOwogCi0gICAg ICAgIHJldCA9IGNvcHlfdG9fZ3Vlc3QoYXJnLCAmb3V0LCAxKSA/IC1FRkFV TFQgOiAwOworICAgICAgICBpZiAoIHJldCA+PSAwICkKKyAgICAgICAgewor ICAgICAgICAgICAgb3V0LnBpcnEgPSByZXQ7CisgICAgICAgICAgICByZXQg PSBjb3B5X3RvX2d1ZXN0KGFyZywgJm91dCwgMSkgPyAtRUZBVUxUIDogMDsK KyAgICAgICAgfQogCiAgICAgICAgIHJjdV91bmxvY2tfZG9tYWluKGQpOwog ICAgICAgICBicmVhazsK --=separator Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users --=separator-- From xen-users-bounces@lists.xen.org Wed Sep 05 10:14:58 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Wed, 05 Sep 2012 10:14:58 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1T9Cce-0000dI-9r; Wed, 05 Sep 2012 10:14:12 +0000 Received: from mail27.messagelabs.com ([193.109.254.147]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1T9Ccb-0000c6-IO; Wed, 05 Sep 2012 10:14:09 +0000 X-Env-Sender: Ian.Jackson@eu.citrix.com X-Msg-Ref: server-3.tower-27.messagelabs.com!1346840028!8841583!1 X-Originating-IP: [62.200.22.115] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogNjIuMjAwLjIyLjExNSA9PiAxMTE5ODY=\n X-StarScan-Received: X-StarScan-Version: 6.6.1.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 32669 invoked from network); 5 Sep 2012 10:13:50 -0000 Received: from smtp.eu.citrix.com (HELO SMTP.EU.CITRIX.COM) (62.200.22.115) by server-3.tower-27.messagelabs.com with RC4-SHA encrypted SMTP; 5 Sep 2012 10:13:50 -0000 X-IronPort-AV: E=Sophos;i="4.80,372,1344211200"; d="scan'208";a="14354132" Received: from lonpmailmx01.citrite.net ([10.30.203.162]) by LONPIPO01.EU.CITRIX.COM with ESMTP/TLS/RC4-MD5; 05 Sep 2012 10:13:31 +0000 Received: from norwich.cam.xci-test.com (10.80.248.129) by smtprelay.citrix.com (10.30.203.162) with Microsoft SMTP Server id 8.3.279.1; Wed, 5 Sep 2012 11:13:31 +0100 Received: from mariner.cam.xci-test.com ([10.80.2.22] helo=mariner.uk.xensource.com ident=Debian-exim) by norwich.cam.xci-test.com with esmtp (Exim 4.72) (envelope-from ) id 1T9Cbz-0001sP-5Y; Wed, 05 Sep 2012 10:13:31 +0000 Received: from iwj by mariner.uk.xensource.com with local (Exim 4.72) (envelope-from ) id 1T9Cbz-0003ZK-24; Wed, 05 Sep 2012 11:13:31 +0100 Date: Wed, 5 Sep 2012 11:13:31 +0100 Message-ID: Content-Type: multipart/mixed; boundary="=separator"; charset="utf-8" MIME-Version: 1.0 X-Mailer: MIME-tools 5.428 (Entity 5.428) To: xen-announce@lists.xen.org, xen-devel@lists.xen.org, xen-users@lists.xen.org, oss-security@lists.openwall.com From: Xen.org security team Cc: "Xen.org security team" Subject: [Xen-users] Xen Security Advisory 13 (CVE-2012-3495) - hypercall physdev_get_free_pirq vulnerability X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org --=separator Content-Type: text/plain; charset="utf-8" Content-Disposition: inline Content-Transfer-Encoding: 7bit -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Xen Security Advisory CVE-2012-3495 / XSA-13 version 3 hypercall physdev_get_free_pirq vulnerability UPDATES IN VERSION 3 ==================== Public release. Credit Matthew Daley. ISSUE DESCRIPTION ================= PHYSDEVOP_get_free_pirq does not check that its call to get_free_pirq succeeded, and if it fails will use the error code as an array index. IMPACT ====== A malicious guest might be able to cause the host to crash, leading to a DoS, depending on the exact memory layout. Privilege escalation is a theoretical possibility which cannot be ruled out, but is considered unlikely. VULNERABLE SYSTEMS ================== All Xen systems. Xen 4.1 is vulnerable. Other versions of Xen are not vulnerable. MITIGATION ========== This issue can be mitigated by ensuring (inside the guest) that the kernel is trustworthy and avoiding situations where something might repeatedly cause the attempted allocation of a physical irq. RESOLUTION ========== Applying the appropriate attached patch will resolve the issue. CREDIT ====== Thanks to Matthew Daley for finding this vulnerability (and that in XSA-12) and notifying the Xen.org security team. PATCH INFORMATION ================= The attached patches resolve this issue Xen 4.1, 4.1.x xsa13-xen-4.1.patch $ sha256sum xsa13-*.patch ad6e3e40ff56c7c25a94d8d9763d4b49f07802b90b4362ddbe4c86bf285c1239 xsa13-xen-4.1.patch -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.10 (GNU/Linux) iQEcBAEBAgAGBQJQRyVqAAoJEIP+FMlX6CvZjrcH/A0xq4dTMtJpUc1WHyUi2aXd 5ap+AA8w0XHLdosXnbxnsTCSsAdkUeBlPkqZAoGxrCGYrzP83T0cPrz8qjzN64KE Jaei9prTk7VFHa9aAz3OqFYjYd/d21CxI4goGJ4Z0tygys4lmkDeex2kEAj5dq7b 0FLj6aIAVFYI3mWMztx4poOrz/BSCMk1YtrV5hZaY8i7Y6nhaOsPISveS0Dv4FPm YDGc93ykhOwEWCNqWFQGVndRihgUWQIUcb7f2SUfOC/FvbcJHGlP4Aojl4LUePqM bi/CR9cPESr7x1+1vcGUZybXALsRMBCJPrx1td3OCgqx8bwAbsQIszuFaWTtajY= =s7wG -----END PGP SIGNATURE----- --=separator Content-Type: application/octet-stream; name="xsa13-xen-4.1.patch" Content-Disposition: attachment; filename="xsa13-xen-4.1.patch" Content-Transfer-Encoding: base64 eGVuOiBoYW5kbGUgb3V0LW9mLXBpcnEgY29uZGl0aW9uIGNvcnJlY3RseSBp biBQSFlTREVWT1BfZ2V0X2ZyZWVfcGlycQoKVGhpcyBpcyBYU0EtMTMgLyBD VkUtMjAxMi0zNDk1CgpTaWduZWQtb2ZmLWJ5OiBJYW4gQ2FtcGJlbGwgPGlh bi5jYW1wYmVsbEBjaXRyaXguY29tPgpTaWduZWQtb2ZmLWJ5OiBKYW4gQmV1 bGljaCA8SkJldWxpY2hAc3VzZS5jb20+CgpkaWZmIC1yIDEyMjVhZmYwNWRk MiB4ZW4vYXJjaC94ODYvcGh5c2Rldi5jCi0tLSBhL3hlbi9hcmNoL3g4Ni9w aHlzZGV2LmMJVGh1IEF1ZyAwOSAxNjo0ODowNyAyMDEyICswMTAwCisrKyBi L3hlbi9hcmNoL3g4Ni9waHlzZGV2LmMJVGh1IEF1ZyAxNiAxMTowNzozNiAy MDEyICswMTAwCkBAIC01ODcsMTEgKzU4NywxNiBAQCByZXRfdCBkb19waHlz ZGV2X29wKGludCBjbWQsIFhFTl9HVUVTVF9ICiAgICAgICAgICAgICBicmVh azsKIAogICAgICAgICBzcGluX2xvY2soJmQtPmV2ZW50X2xvY2spOwotICAg ICAgICBvdXQucGlycSA9IGdldF9mcmVlX3BpcnEoZCwgb3V0LnR5cGUsIDAp OwotICAgICAgICBkLT5hcmNoLnBpcnFfaXJxW291dC5waXJxXSA9IFBJUlFf QUxMT0NBVEVEOworICAgICAgICByZXQgPSBnZXRfZnJlZV9waXJxKGQsIG91 dC50eXBlLCAwKTsKKyAgICAgICAgaWYgKCByZXQgPj0gMCApCisgICAgICAg ICAgICBkLT5hcmNoLnBpcnFfaXJxW3JldF0gPSBQSVJRX0FMTE9DQVRFRDsK ICAgICAgICAgc3Bpbl91bmxvY2soJmQtPmV2ZW50X2xvY2spOwogCi0gICAg ICAgIHJldCA9IGNvcHlfdG9fZ3Vlc3QoYXJnLCAmb3V0LCAxKSA/IC1FRkFV TFQgOiAwOworICAgICAgICBpZiAoIHJldCA+PSAwICkKKyAgICAgICAgewor ICAgICAgICAgICAgb3V0LnBpcnEgPSByZXQ7CisgICAgICAgICAgICByZXQg PSBjb3B5X3RvX2d1ZXN0KGFyZywgJm91dCwgMSkgPyAtRUZBVUxUIDogMDsK KyAgICAgICAgfQogCiAgICAgICAgIHJjdV91bmxvY2tfZG9tYWluKGQpOwog ICAgICAgICBicmVhazsK --=separator Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users --=separator-- From xen-users-bounces@lists.xen.org Wed Sep 05 10:45:26 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Wed, 05 Sep 2012 10:45:26 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1T9D5q-0002Ns-PJ; Wed, 05 Sep 2012 10:44:22 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1T9D5p-0002Nh-JC for xen-users@lists.xen.org; Wed, 05 Sep 2012 10:44:21 +0000 Received: from [85.158.143.99:29354] by server-3.bemta-4.messagelabs.com id 87/A6-08232-40D27405; Wed, 05 Sep 2012 10:44:20 +0000 X-Env-Sender: lists+xen@internecto.net X-Msg-Ref: server-12.tower-216.messagelabs.com!1346841859!23400161!1 X-Originating-IP: [176.9.245.29] X-SpamReason: No, hits=0.0 required=7.0 tests= X-StarScan-Received: X-StarScan-Version: 6.6.1.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 23732 invoked from network); 5 Sep 2012 10:44:19 -0000 Received: from polaris.internecto.net (HELO mx1.internecto.net) (176.9.245.29) by server-12.tower-216.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 5 Sep 2012 10:44:19 -0000 Received: from localhost (localhost [127.0.0.1]) by mx1.internecto.net (Postfix) with ESMTP id 6C9C4A0086; Wed, 5 Sep 2012 10:44:19 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at mail.internecto.net Received: from mx1.internecto.net ([127.0.0.1]) by localhost (mail.polaris.internecto.net [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id r3o1ySzSN+8G; Wed, 5 Sep 2012 10:44:19 +0000 (UTC) Received: from internecto.net (5ED4FDEB.cm-7-5d.dynamic.ziggo.nl [94.212.253.235]) (using TLSv1 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (Client did not present a certificate) (Authenticated sender: lists@internecto.net) by mx1.internecto.net (Postfix) with ESMTPSA id E933CA0058; Wed, 5 Sep 2012 10:44:18 +0000 (UTC) Date: Wed, 5 Sep 2012 12:44:12 +0200 From: Mark van Dijk To: Venkatesh P N Message-ID: <20120905124412.561cd132@internecto.net> In-Reply-To: References: Organization: Internecto SIS X-Mailer: Claws Mail 3.8.0 (GTK+ 2.24.10; x86_64-pc-linux-gnu) Mime-Version: 1.0 Cc: xen-users@lists.xen.org Subject: Re: [Xen-users] How to assign a SR-IOV Virtual Function to Host X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org >I have a use-case like, I need to use one of the VFs on the host >machine itself. >So, is there any way to assign VF to host itself and use it as a >regular device there. > >Or, how can we can access a VF created by SR-OV on host machine >directly. Hi Venkatesh, I tested SR-IOV a couple of months ago and this is how I got it to work at one point. So, normally you have an ethernet device with address e.g. 02:00.0. With SR-IOV the addresses are extended. From memory I recall this extends addresses to something like either 02:00.1, 02:00.2 OR 02:01.0, 02:02.0. It's one or the other. Then I got SR-IOV to work by issuing, in the dom0 kernel boot cmdline, xen.pciback=(02:00.1)(02:00.2). If you don't hide the base address (02:00.0) in that line then it should still be usable by the dom0. And then in your VM config you pass the address to the VM with e.g. pci=['02:00.1']. I also found that SR-IOV degraded the performance of the NIC somewhat. Note that SR-IOV is only supported by some devices, e.g. the Intel 10Gbit ixgbe device. I used Intel's external driver (the one they share on their website, it is different from the in-kernel driver). Read the README thoroughly and make sure that you disable LRO, this is crucial for both SR-IOV and for the ip_forward=1 sysctl, even without SR-IOV. LRO can be disabled in a couple of ways -- when you compile the module; when you load the kernel module with LRO=0 in modules.conf or by using ethtool. I strongly recommend you use the first option here: disable it by passing some argument to the 'make' command -- this should be in the README, at least for Intel drivers. Let me know if this works for you. If not I will test this stuff out on my SR-IOV capable server and get back to you. -- Adios, Mark van Dijk. ,--------------------------------- -----------------------------' Wed Sep 05 10:43 UTC 2012 Today is Pungenday, the 29th day of Bureaucracy in the YOLD 3178 _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Wed Sep 05 10:45:26 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Wed, 05 Sep 2012 10:45:26 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1T9D5q-0002Ns-PJ; Wed, 05 Sep 2012 10:44:22 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1T9D5p-0002Nh-JC for xen-users@lists.xen.org; Wed, 05 Sep 2012 10:44:21 +0000 Received: from [85.158.143.99:29354] by server-3.bemta-4.messagelabs.com id 87/A6-08232-40D27405; Wed, 05 Sep 2012 10:44:20 +0000 X-Env-Sender: lists+xen@internecto.net X-Msg-Ref: server-12.tower-216.messagelabs.com!1346841859!23400161!1 X-Originating-IP: [176.9.245.29] X-SpamReason: No, hits=0.0 required=7.0 tests= X-StarScan-Received: X-StarScan-Version: 6.6.1.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 23732 invoked from network); 5 Sep 2012 10:44:19 -0000 Received: from polaris.internecto.net (HELO mx1.internecto.net) (176.9.245.29) by server-12.tower-216.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 5 Sep 2012 10:44:19 -0000 Received: from localhost (localhost [127.0.0.1]) by mx1.internecto.net (Postfix) with ESMTP id 6C9C4A0086; Wed, 5 Sep 2012 10:44:19 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at mail.internecto.net Received: from mx1.internecto.net ([127.0.0.1]) by localhost (mail.polaris.internecto.net [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id r3o1ySzSN+8G; Wed, 5 Sep 2012 10:44:19 +0000 (UTC) Received: from internecto.net (5ED4FDEB.cm-7-5d.dynamic.ziggo.nl [94.212.253.235]) (using TLSv1 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (Client did not present a certificate) (Authenticated sender: lists@internecto.net) by mx1.internecto.net (Postfix) with ESMTPSA id E933CA0058; Wed, 5 Sep 2012 10:44:18 +0000 (UTC) Date: Wed, 5 Sep 2012 12:44:12 +0200 From: Mark van Dijk To: Venkatesh P N Message-ID: <20120905124412.561cd132@internecto.net> In-Reply-To: References: Organization: Internecto SIS X-Mailer: Claws Mail 3.8.0 (GTK+ 2.24.10; x86_64-pc-linux-gnu) Mime-Version: 1.0 Cc: xen-users@lists.xen.org Subject: Re: [Xen-users] How to assign a SR-IOV Virtual Function to Host X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org >I have a use-case like, I need to use one of the VFs on the host >machine itself. >So, is there any way to assign VF to host itself and use it as a >regular device there. > >Or, how can we can access a VF created by SR-OV on host machine >directly. Hi Venkatesh, I tested SR-IOV a couple of months ago and this is how I got it to work at one point. So, normally you have an ethernet device with address e.g. 02:00.0. With SR-IOV the addresses are extended. From memory I recall this extends addresses to something like either 02:00.1, 02:00.2 OR 02:01.0, 02:02.0. It's one or the other. Then I got SR-IOV to work by issuing, in the dom0 kernel boot cmdline, xen.pciback=(02:00.1)(02:00.2). If you don't hide the base address (02:00.0) in that line then it should still be usable by the dom0. And then in your VM config you pass the address to the VM with e.g. pci=['02:00.1']. I also found that SR-IOV degraded the performance of the NIC somewhat. Note that SR-IOV is only supported by some devices, e.g. the Intel 10Gbit ixgbe device. I used Intel's external driver (the one they share on their website, it is different from the in-kernel driver). Read the README thoroughly and make sure that you disable LRO, this is crucial for both SR-IOV and for the ip_forward=1 sysctl, even without SR-IOV. LRO can be disabled in a couple of ways -- when you compile the module; when you load the kernel module with LRO=0 in modules.conf or by using ethtool. I strongly recommend you use the first option here: disable it by passing some argument to the 'make' command -- this should be in the README, at least for Intel drivers. Let me know if this works for you. If not I will test this stuff out on my SR-IOV capable server and get back to you. -- Adios, Mark van Dijk. ,--------------------------------- -----------------------------' Wed Sep 05 10:43 UTC 2012 Today is Pungenday, the 29th day of Bureaucracy in the YOLD 3178 _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Wed Sep 05 10:55:16 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Wed, 05 Sep 2012 10:55:16 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1T9DFm-0003DB-Q8; Wed, 05 Sep 2012 10:54:38 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1T9DFl-0003Cn-Bk for xen-users@lists.xen.org; Wed, 05 Sep 2012 10:54:37 +0000 Received: from [85.158.139.83:57080] by server-4.bemta-5.messagelabs.com id E5/4C-23042-C6F27405; Wed, 05 Sep 2012 10:54:36 +0000 X-Env-Sender: lists+xen@internecto.net X-Msg-Ref: server-8.tower-182.messagelabs.com!1346842391!17402643!1 X-Originating-IP: [176.9.245.29] X-SpamReason: No, hits=0.0 required=7.0 tests= X-StarScan-Received: X-StarScan-Version: 6.6.1.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 6506 invoked from network); 5 Sep 2012 10:53:12 -0000 Received: from polaris.internecto.net (HELO mx1.internecto.net) (176.9.245.29) by server-8.tower-182.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 5 Sep 2012 10:53:12 -0000 Received: from localhost (localhost [127.0.0.1]) by mx1.internecto.net (Postfix) with ESMTP id 5598EA0086 for ; Wed, 5 Sep 2012 10:53:11 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at mail.internecto.net Received: from mx1.internecto.net ([127.0.0.1]) by localhost (mail.polaris.internecto.net [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Llrtq4F6CEuy for ; Wed, 5 Sep 2012 10:53:10 +0000 (UTC) Received: from internecto.net (5ED4FDEB.cm-7-5d.dynamic.ziggo.nl [94.212.253.235]) (using TLSv1 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (Client did not present a certificate) (Authenticated sender: lists@internecto.net) by mx1.internecto.net (Postfix) with ESMTPSA id 8D308A0058 for ; Wed, 5 Sep 2012 10:53:10 +0000 (UTC) Date: Wed, 5 Sep 2012 12:53:08 +0200 From: Mark van Dijk To: xen-users@lists.xen.org Message-ID: <20120905125308.24ba4f58@internecto.net> Organization: Internecto SIS X-Mailer: Claws Mail 3.8.0 (GTK+ 2.24.10; x86_64-pc-linux-gnu) Mime-Version: 1.0 Subject: [Xen-users] Sharing entropy across VMs X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org Short question: is it possible to share entropy across all VMs and how can this be done? I found http://vanheusden.com/entropybroker/ which seems to offer a way, but I cannot get it to work, syslog tells me "stack smashing detected". So if there are ways people are currently using I'd be interested to hear them. Currently I find that even generating a gpg key on a PV VM takes ages and I don't want to compromise the security by using workarounds. -- Thank you, Mark van Dijk. ,--------------------------------- -----------------------------' Wed Sep 05 10:48 UTC 2012 Today is Pungenday, the 29th day of Bureaucracy in the YOLD 3178 _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Wed Sep 05 10:55:16 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Wed, 05 Sep 2012 10:55:16 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1T9DFm-0003DB-Q8; Wed, 05 Sep 2012 10:54:38 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1T9DFl-0003Cn-Bk for xen-users@lists.xen.org; Wed, 05 Sep 2012 10:54:37 +0000 Received: from [85.158.139.83:57080] by server-4.bemta-5.messagelabs.com id E5/4C-23042-C6F27405; Wed, 05 Sep 2012 10:54:36 +0000 X-Env-Sender: lists+xen@internecto.net X-Msg-Ref: server-8.tower-182.messagelabs.com!1346842391!17402643!1 X-Originating-IP: [176.9.245.29] X-SpamReason: No, hits=0.0 required=7.0 tests= X-StarScan-Received: X-StarScan-Version: 6.6.1.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 6506 invoked from network); 5 Sep 2012 10:53:12 -0000 Received: from polaris.internecto.net (HELO mx1.internecto.net) (176.9.245.29) by server-8.tower-182.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 5 Sep 2012 10:53:12 -0000 Received: from localhost (localhost [127.0.0.1]) by mx1.internecto.net (Postfix) with ESMTP id 5598EA0086 for ; Wed, 5 Sep 2012 10:53:11 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at mail.internecto.net Received: from mx1.internecto.net ([127.0.0.1]) by localhost (mail.polaris.internecto.net [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Llrtq4F6CEuy for ; Wed, 5 Sep 2012 10:53:10 +0000 (UTC) Received: from internecto.net (5ED4FDEB.cm-7-5d.dynamic.ziggo.nl [94.212.253.235]) (using TLSv1 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (Client did not present a certificate) (Authenticated sender: lists@internecto.net) by mx1.internecto.net (Postfix) with ESMTPSA id 8D308A0058 for ; Wed, 5 Sep 2012 10:53:10 +0000 (UTC) Date: Wed, 5 Sep 2012 12:53:08 +0200 From: Mark van Dijk To: xen-users@lists.xen.org Message-ID: <20120905125308.24ba4f58@internecto.net> Organization: Internecto SIS X-Mailer: Claws Mail 3.8.0 (GTK+ 2.24.10; x86_64-pc-linux-gnu) Mime-Version: 1.0 Subject: [Xen-users] Sharing entropy across VMs X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org Short question: is it possible to share entropy across all VMs and how can this be done? I found http://vanheusden.com/entropybroker/ which seems to offer a way, but I cannot get it to work, syslog tells me "stack smashing detected". So if there are ways people are currently using I'd be interested to hear them. Currently I find that even generating a gpg key on a PV VM takes ages and I don't want to compromise the security by using workarounds. -- Thank you, Mark van Dijk. ,--------------------------------- -----------------------------' Wed Sep 05 10:48 UTC 2012 Today is Pungenday, the 29th day of Bureaucracy in the YOLD 3178 _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Wed Sep 05 11:10:42 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Wed, 05 Sep 2012 11:10:42 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1T9DUh-0004dV-1x; Wed, 05 Sep 2012 11:10:03 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1T9D0n-0002DK-G6 for xen-users@lists.xen.org; Wed, 05 Sep 2012 10:39:09 +0000 Received: from [85.158.143.35:39618] by server-3.bemta-4.messagelabs.com id 68/1C-08232-BCB27405; Wed, 05 Sep 2012 10:39:07 +0000 X-Env-Sender: iwj@xenbits.xen.org X-Msg-Ref: server-4.tower-21.messagelabs.com!1346841534!6292152!1 X-Originating-IP: [50.57.168.107] X-SpamReason: No, hits=0.0 required=7.0 tests= X-StarScan-Received: X-StarScan-Version: 6.6.1.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 28614 invoked from network); 5 Sep 2012 10:38:59 -0000 Received: from mail.xen.org (HELO mail.xen.org) (50.57.168.107) by server-4.tower-21.messagelabs.com with AES256-SHA encrypted SMTP; 5 Sep 2012 10:38:59 -0000 Received: from xenbits.xen.org ([50.57.170.242]) by mail.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1T9D0R-0000nI-AY; Wed, 05 Sep 2012 10:38:47 +0000 Received: from iwj by xenbits.xen.org with local (Exim 4.72) (envelope-from ) id 1T9D0R-0004Zb-5d; Wed, 05 Sep 2012 10:38:47 +0000 Date: Wed, 05 Sep 2012 10:38:47 +0000 Message-Id: Content-Type: multipart/mixed; boundary="=separator"; charset="utf-8" Content-Transfer-Encoding: binary MIME-Version: 1.0 X-Mailer: MIME-tools 5.428 (Entity 5.428) To: xen-announce@lists.xen.org, xen-devel@lists.xen.org, xen-users@lists.xen.org, oss-security@lists.openwall.com From: Xen.org security team X-Mailman-Approved-At: Wed, 05 Sep 2012 11:10:02 +0000 Cc: "Xen.org security team" Subject: [Xen-users] Xen Security Advisory 14 (CVE-2012-3496) - XENMEM_populate_physmap DoS vulnerability X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org --=separator Content-Type: text/plain; charset="utf-8" Content-Disposition: inline Content-Transfer-Encoding: 7bit -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Xen Security Advisory CVE-2012-3496 / XSA-14 version 3 XENMEM_populate_physmap DoS vulnerability UPDATES IN VERSION 3 ==================== Public release. Credit Matthew Daley. ISSUE DESCRIPTION ================= XENMEM_populate_physmap can be called with invalid flags. By calling it with MEMF_populate_on_demand flag set, a BUG can be triggered if a translating paging mode is not being used. IMPACT ====== A malicious guest kernel can crash the host. VULNERABLE SYSTEMS ================== All Xen systems running PV guests. Systems running only HVM guests are not vulnerable. The vulnerability dates back to at least Xen 4.0. 4.0, 4.1, the 4.2 RCs, and xen-unstable.hg are all vulnerable. MITIGATION ========== This issue can be mitigated by ensuring that the guest kernel is trustworthy or by running only HVM guests. RESOLUTION ========== Applying the appropriate attached patch will resolve the issue. CREDIT ====== Thanks to Matthew Daley for finding this vulnerability (and that in XSA-12) and notifying the Xen.org security team. PATCH INFORMATION ================= The attached patches resolve this issue xen-unstable xsa14-unstable.patch Xen 4.1, 4.1.x, 4.0, 4.0.x, 3.4 and 3.4.x xsa14-xen-3.4-and-4.x.patch $ sha256sum xsa14-*.patch 7a2e119b114708420c3484ecc338c7a198097f40e0d38854756dfa69c4c859a8 xsa14-unstable.patch 41a1ee1da7e990dc93b75fad0d46b66a2bda472e9aa288c91d1dc5d15d2c2012 xsa14-xen-3.4-and-4.x.patch -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.10 (GNU/Linux) iQEcBAEBAgAGBQJQRyVAAAoJEIP+FMlX6CvZF0IH/RV88Xqc9SdwrDZ7w6uwsRt+ 2keNPNyDBYxoYeqEqP9q/zICmxEqHMk/1zvSksimuIoiblliYQPHcJjhYhiBA8aX tarL2byKK+AE/1xvgh1BZiizCR6UV33Zi2PNdB3aaLizh82+70Lbx4ZtDg3zCpEo cvXGyMrNwzxMS+7ORuBAC9gtMke3sBeLua4KvGMhuByDIbW+9/7124YSGo30vFa3 VHmZ8995ishkSQyzgvZVLMQ+y2G1GofUqa4gPRcNoMCULKGGkqJCyHPZfuAOY+w+ 0Cy/WDIE1HZd6DIn+09IoHe+StkyPgqYkai+QYwxS+JW/vpns82fpsAtmOF64tg= =EONA -----END PGP SIGNATURE----- --=separator Content-Type: application/octet-stream; name="xsa14-unstable.patch" Content-Disposition: attachment; filename="xsa14-unstable.patch" Content-Transfer-Encoding: base64 eGVuOiBEb24ndCBCVUdfT04oKSBQb0Qgb3BlcmF0aW9ucyBvbiBhIG5vbi10 cmFuc2xhdGVkIGd1ZXN0LgoKVGhpcyBpcyBYU0EtMTQgLyBDVkUtMjAxMi0z NDk2CgpTaWduZWQtb2ZmLWJ5OiBUaW0gRGVlZ2FuIDx0aW1AeGVuLm9yZz4K UmV2aWV3ZWQtYnk6IElhbiBDYW1wYmVsbCA8aWFuLmNhbXBiZWxsQGNpdHJp eC5jb20+ClRlc3RlZC1ieTogSWFuIENhbXBiZWxsIDxpYW4uY2FtcGJlbGxA Y2l0cml4LmNvbT4KCmRpZmYgLXIgMzUzYmMwODAxYjExIHhlbi9hcmNoL3g4 Ni9tbS9wMm0tcG9kLmMKLS0tIGEveGVuL2FyY2gveDg2L21tL3AybS1wb2Qu YwlNb24gQXVnIDA2IDEyOjI4OjAzIDIwMTIgKzAxMDAKKysrIGIveGVuL2Fy Y2gveDg2L21tL3AybS1wb2QuYwlXZWQgQXVnIDE1IDEyOjA2OjQzIDIwMTIg KzAxMDAKQEAgLTExMTcsNyArMTExNyw4IEBAIGd1ZXN0X3BoeXNtYXBfbWFy a19wb3B1bGF0ZV9vbl9kZW1hbmQoc3QKICAgICBtZm5fdCBvbWZuOwogICAg IGludCByYyA9IDA7CiAKLSAgICBCVUdfT04oIXBhZ2luZ19tb2RlX3RyYW5z bGF0ZShkKSk7CisgICAgaWYgKCAhcGFnaW5nX21vZGVfdHJhbnNsYXRlKGQp ICkKKyAgICAgICAgcmV0dXJuIC1FSU5WQUw7CiAKICAgICByYyA9IHAybV9n Zm5fY2hlY2tfbGltaXQoZCwgZ2ZuLCBvcmRlcik7CiAgICAgaWYgKCByYyAh PSAwICkK --=separator Content-Type: application/octet-stream; name="xsa14-xen-3.4-and-4.x.patch" Content-Disposition: attachment; filename="xsa14-xen-3.4-and-4.x.patch" Content-Transfer-Encoding: base64 eGVuOiBEb24ndCBCVUdfT04oKSBQb0Qgb3BlcmF0aW9ucyBvbiBhIG5vbi10 cmFuc2xhdGVkIGd1ZXN0LgoKVGhpcyBpcyBYU0EtMTQgLyBDVkUtMjAxMi0z NDk2CgpTaWduZWQtb2ZmLWJ5OiBUaW0gRGVlZ2FuIDx0aW1AeGVuLm9yZz4K UmV2aWV3ZWQtYnk6IElhbiBDYW1wYmVsbCA8aWFuLmNhbXBiZWxsQGNpdHJp eC5jb20+ClRlc3RlZC1ieTogSWFuIENhbXBiZWxsIDxpYW4uY2FtcGJlbGxA Y2l0cml4LmNvbT4KCmRpZmYgLXIgMTIyNWFmZjA1ZGQyIHhlbi9hcmNoL3g4 Ni9tbS9wMm0uYwotLS0gYS94ZW4vYXJjaC94ODYvbW0vcDJtLmMJVGh1IEF1 ZyAwOSAxNjo0ODowNyAyMDEyICswMTAwCisrKyBiL3hlbi9hcmNoL3g4Ni9t bS9wMm0uYwlXZWQgQXVnIDE1IDEyOjEwOjMzIDIwMTIgKzAxMDAKQEAgLTI0 MTQsNyArMjQxNCw4IEBAIGd1ZXN0X3BoeXNtYXBfbWFya19wb3B1bGF0ZV9v bl9kZW1hbmQoc3QKICAgICBpbnQgcG9kX2NvdW50ID0gMDsKICAgICBpbnQg cmMgPSAwOwogCi0gICAgQlVHX09OKCFwYWdpbmdfbW9kZV90cmFuc2xhdGUo ZCkpOworICAgIGlmICggIXBhZ2luZ19tb2RlX3RyYW5zbGF0ZShkKSApCisg ICAgICAgIHJldHVybiAtRUlOVkFMOwogCiAgICAgcmMgPSBnZm5fY2hlY2tf bGltaXQoZCwgZ2ZuLCBvcmRlcik7CiAgICAgaWYgKCByYyAhPSAwICkK --=separator Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users --=separator-- From xen-users-bounces@lists.xen.org Wed Sep 05 11:10:42 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Wed, 05 Sep 2012 11:10:42 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1T9DUh-0004dV-1x; Wed, 05 Sep 2012 11:10:03 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1T9D0n-0002DK-G6 for xen-users@lists.xen.org; Wed, 05 Sep 2012 10:39:09 +0000 Received: from [85.158.143.35:39618] by server-3.bemta-4.messagelabs.com id 68/1C-08232-BCB27405; Wed, 05 Sep 2012 10:39:07 +0000 X-Env-Sender: iwj@xenbits.xen.org X-Msg-Ref: server-4.tower-21.messagelabs.com!1346841534!6292152!1 X-Originating-IP: [50.57.168.107] X-SpamReason: No, hits=0.0 required=7.0 tests= X-StarScan-Received: X-StarScan-Version: 6.6.1.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 28614 invoked from network); 5 Sep 2012 10:38:59 -0000 Received: from mail.xen.org (HELO mail.xen.org) (50.57.168.107) by server-4.tower-21.messagelabs.com with AES256-SHA encrypted SMTP; 5 Sep 2012 10:38:59 -0000 Received: from xenbits.xen.org ([50.57.170.242]) by mail.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1T9D0R-0000nI-AY; Wed, 05 Sep 2012 10:38:47 +0000 Received: from iwj by xenbits.xen.org with local (Exim 4.72) (envelope-from ) id 1T9D0R-0004Zb-5d; Wed, 05 Sep 2012 10:38:47 +0000 Date: Wed, 05 Sep 2012 10:38:47 +0000 Message-Id: Content-Type: multipart/mixed; boundary="=separator"; charset="utf-8" Content-Transfer-Encoding: binary MIME-Version: 1.0 X-Mailer: MIME-tools 5.428 (Entity 5.428) To: xen-announce@lists.xen.org, xen-devel@lists.xen.org, xen-users@lists.xen.org, oss-security@lists.openwall.com From: Xen.org security team X-Mailman-Approved-At: Wed, 05 Sep 2012 11:10:02 +0000 Cc: "Xen.org security team" Subject: [Xen-users] Xen Security Advisory 14 (CVE-2012-3496) - XENMEM_populate_physmap DoS vulnerability X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org --=separator Content-Type: text/plain; charset="utf-8" Content-Disposition: inline Content-Transfer-Encoding: 7bit -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Xen Security Advisory CVE-2012-3496 / XSA-14 version 3 XENMEM_populate_physmap DoS vulnerability UPDATES IN VERSION 3 ==================== Public release. Credit Matthew Daley. ISSUE DESCRIPTION ================= XENMEM_populate_physmap can be called with invalid flags. By calling it with MEMF_populate_on_demand flag set, a BUG can be triggered if a translating paging mode is not being used. IMPACT ====== A malicious guest kernel can crash the host. VULNERABLE SYSTEMS ================== All Xen systems running PV guests. Systems running only HVM guests are not vulnerable. The vulnerability dates back to at least Xen 4.0. 4.0, 4.1, the 4.2 RCs, and xen-unstable.hg are all vulnerable. MITIGATION ========== This issue can be mitigated by ensuring that the guest kernel is trustworthy or by running only HVM guests. RESOLUTION ========== Applying the appropriate attached patch will resolve the issue. CREDIT ====== Thanks to Matthew Daley for finding this vulnerability (and that in XSA-12) and notifying the Xen.org security team. PATCH INFORMATION ================= The attached patches resolve this issue xen-unstable xsa14-unstable.patch Xen 4.1, 4.1.x, 4.0, 4.0.x, 3.4 and 3.4.x xsa14-xen-3.4-and-4.x.patch $ sha256sum xsa14-*.patch 7a2e119b114708420c3484ecc338c7a198097f40e0d38854756dfa69c4c859a8 xsa14-unstable.patch 41a1ee1da7e990dc93b75fad0d46b66a2bda472e9aa288c91d1dc5d15d2c2012 xsa14-xen-3.4-and-4.x.patch -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.10 (GNU/Linux) iQEcBAEBAgAGBQJQRyVAAAoJEIP+FMlX6CvZF0IH/RV88Xqc9SdwrDZ7w6uwsRt+ 2keNPNyDBYxoYeqEqP9q/zICmxEqHMk/1zvSksimuIoiblliYQPHcJjhYhiBA8aX tarL2byKK+AE/1xvgh1BZiizCR6UV33Zi2PNdB3aaLizh82+70Lbx4ZtDg3zCpEo cvXGyMrNwzxMS+7ORuBAC9gtMke3sBeLua4KvGMhuByDIbW+9/7124YSGo30vFa3 VHmZ8995ishkSQyzgvZVLMQ+y2G1GofUqa4gPRcNoMCULKGGkqJCyHPZfuAOY+w+ 0Cy/WDIE1HZd6DIn+09IoHe+StkyPgqYkai+QYwxS+JW/vpns82fpsAtmOF64tg= =EONA -----END PGP SIGNATURE----- --=separator Content-Type: application/octet-stream; name="xsa14-unstable.patch" Content-Disposition: attachment; filename="xsa14-unstable.patch" Content-Transfer-Encoding: base64 eGVuOiBEb24ndCBCVUdfT04oKSBQb0Qgb3BlcmF0aW9ucyBvbiBhIG5vbi10 cmFuc2xhdGVkIGd1ZXN0LgoKVGhpcyBpcyBYU0EtMTQgLyBDVkUtMjAxMi0z NDk2CgpTaWduZWQtb2ZmLWJ5OiBUaW0gRGVlZ2FuIDx0aW1AeGVuLm9yZz4K UmV2aWV3ZWQtYnk6IElhbiBDYW1wYmVsbCA8aWFuLmNhbXBiZWxsQGNpdHJp eC5jb20+ClRlc3RlZC1ieTogSWFuIENhbXBiZWxsIDxpYW4uY2FtcGJlbGxA Y2l0cml4LmNvbT4KCmRpZmYgLXIgMzUzYmMwODAxYjExIHhlbi9hcmNoL3g4 Ni9tbS9wMm0tcG9kLmMKLS0tIGEveGVuL2FyY2gveDg2L21tL3AybS1wb2Qu YwlNb24gQXVnIDA2IDEyOjI4OjAzIDIwMTIgKzAxMDAKKysrIGIveGVuL2Fy Y2gveDg2L21tL3AybS1wb2QuYwlXZWQgQXVnIDE1IDEyOjA2OjQzIDIwMTIg KzAxMDAKQEAgLTExMTcsNyArMTExNyw4IEBAIGd1ZXN0X3BoeXNtYXBfbWFy a19wb3B1bGF0ZV9vbl9kZW1hbmQoc3QKICAgICBtZm5fdCBvbWZuOwogICAg IGludCByYyA9IDA7CiAKLSAgICBCVUdfT04oIXBhZ2luZ19tb2RlX3RyYW5z bGF0ZShkKSk7CisgICAgaWYgKCAhcGFnaW5nX21vZGVfdHJhbnNsYXRlKGQp ICkKKyAgICAgICAgcmV0dXJuIC1FSU5WQUw7CiAKICAgICByYyA9IHAybV9n Zm5fY2hlY2tfbGltaXQoZCwgZ2ZuLCBvcmRlcik7CiAgICAgaWYgKCByYyAh PSAwICkK --=separator Content-Type: application/octet-stream; name="xsa14-xen-3.4-and-4.x.patch" Content-Disposition: attachment; filename="xsa14-xen-3.4-and-4.x.patch" Content-Transfer-Encoding: base64 eGVuOiBEb24ndCBCVUdfT04oKSBQb0Qgb3BlcmF0aW9ucyBvbiBhIG5vbi10 cmFuc2xhdGVkIGd1ZXN0LgoKVGhpcyBpcyBYU0EtMTQgLyBDVkUtMjAxMi0z NDk2CgpTaWduZWQtb2ZmLWJ5OiBUaW0gRGVlZ2FuIDx0aW1AeGVuLm9yZz4K UmV2aWV3ZWQtYnk6IElhbiBDYW1wYmVsbCA8aWFuLmNhbXBiZWxsQGNpdHJp eC5jb20+ClRlc3RlZC1ieTogSWFuIENhbXBiZWxsIDxpYW4uY2FtcGJlbGxA Y2l0cml4LmNvbT4KCmRpZmYgLXIgMTIyNWFmZjA1ZGQyIHhlbi9hcmNoL3g4 Ni9tbS9wMm0uYwotLS0gYS94ZW4vYXJjaC94ODYvbW0vcDJtLmMJVGh1IEF1 ZyAwOSAxNjo0ODowNyAyMDEyICswMTAwCisrKyBiL3hlbi9hcmNoL3g4Ni9t bS9wMm0uYwlXZWQgQXVnIDE1IDEyOjEwOjMzIDIwMTIgKzAxMDAKQEAgLTI0 MTQsNyArMjQxNCw4IEBAIGd1ZXN0X3BoeXNtYXBfbWFya19wb3B1bGF0ZV9v bl9kZW1hbmQoc3QKICAgICBpbnQgcG9kX2NvdW50ID0gMDsKICAgICBpbnQg cmMgPSAwOwogCi0gICAgQlVHX09OKCFwYWdpbmdfbW9kZV90cmFuc2xhdGUo ZCkpOworICAgIGlmICggIXBhZ2luZ19tb2RlX3RyYW5zbGF0ZShkKSApCisg ICAgICAgIHJldHVybiAtRUlOVkFMOwogCiAgICAgcmMgPSBnZm5fY2hlY2tf bGltaXQoZCwgZ2ZuLCBvcmRlcik7CiAgICAgaWYgKCByYyAhPSAwICkK --=separator Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users --=separator-- From xen-users-bounces@lists.xen.org Wed Sep 05 11:16:53 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Wed, 05 Sep 2012 11:16:53 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1T9Dat-0005CM-GP; Wed, 05 Sep 2012 11:16:27 +0000 Received: from mail27.messagelabs.com ([193.109.254.147]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1T9DYi-00053C-Vt; Wed, 05 Sep 2012 11:14:13 +0000 X-Env-Sender: iwj@xenbits.xen.org X-Msg-Ref: server-5.tower-27.messagelabs.com!1346843573!6253309!1 X-Originating-IP: [50.57.168.107] X-SpamReason: No, hits=0.5 required=7.0 tests=BODY_RANDOM_LONG X-StarScan-Received: X-StarScan-Version: 6.6.1.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 16021 invoked from network); 5 Sep 2012 11:12:55 -0000 Received: from mail.xen.org (HELO mail.xen.org) (50.57.168.107) by server-5.tower-27.messagelabs.com with AES256-SHA encrypted SMTP; 5 Sep 2012 11:12:55 -0000 Received: from xenbits.xen.org ([50.57.170.242]) by mail.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1T9DXL-0001Cr-Dg; Wed, 05 Sep 2012 11:12:47 +0000 Received: from iwj by xenbits.xen.org with local (Exim 4.72) (envelope-from ) id 1T9DXL-0005Qu-97; Wed, 05 Sep 2012 11:12:47 +0000 Date: Wed, 05 Sep 2012 11:12:47 +0000 Message-Id: Content-Type: multipart/mixed; boundary="=separator"; charset="utf-8" Content-Transfer-Encoding: binary MIME-Version: 1.0 X-Mailer: MIME-tools 5.428 (Entity 5.428) To: xen-announce@lists.xen.org, xen-devel@lists.xen.org, xen-users@lists.xen.org, oss-security@lists.openwall.com From: Xen.org security team X-Mailman-Approved-At: Wed, 05 Sep 2012 11:16:25 +0000 Cc: "Xen.org security team" Subject: [Xen-users] Xen Security Advisory 17 (CVE-2012-3515) - Qemu VT100 emulation vulnerability X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org --=separator Content-Type: text/plain; charset="utf-8" Content-Disposition: inline Content-Transfer-Encoding: 7bit -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Xen Security Advisory CVE-2012-3515 / XSA-17 version 2 Qemu VT100 emulation vulnerability UPDATES IN VERSION 2 ==================== Public release. ISSUE DESCRIPTION ================= The device model used by fully virtualised (HVM) domains, qemu, does not properly handle escape VT100 sequences when emulating certain devices with a virtual console backend. IMPACT ====== An attacker who has sufficient privilege to access a vulnerable device within a guest can overwrite portions of the device model's address space. This can allow them to escalate their privileges to that of the device model process. VULNERABLE SYSTEMS ================== All Xen systems running HVM guests are potentially vulnerable to this depending on the specific guest configuration. The default configuration is vulnerable. Guests using either the traditional "qemu-xen" or upstream qemu device models are vulnerable. MITIGATION ========== This issue can be avoided by only running PV guests or by configuring HVM guests to not use the virtual console('vc') backend for any device. For serial devices specify in your guest configuration: serial = 'none' in your guest configuration. For parallel port devices the syntax is toolstack specific. For xend specify in your guest configuration: parallel = 'none' For xl specify in your guest configuration: xl: device_model_args = ['-parallel', 'none'] In both cases the default is to use the vulnerable 'vc' mode. You can confirm whether or not you are vulnerable by pressing Ctrl-Alt- (for digit N) while connected to either the VNC or SDL console. If you are able to switch to a window displaying "serial" or "parallel" then you are vulnerable. The issue can also be mitigated by enabling the stub domain device model. In this case the attacked can only potentially gain control of the stub domain and not of the entire system. To enable stub domains specify in your guest configuration: device_model = "stubdom-dm" RESOLUTION ========== Applying the appropriate attached patch(es) will resolve the issue. PATCH INFORMATION ================= The attached patches resolve this issue Traditional qemu tree Xen 4.0, 4.1 and unstable xsa17-qemu-xen-traditional-all.patch Upstream qemu tree (present in unstable only) Xen unstable xsa17-qemu-xen-unstable.patch $ sha256sum xsa17-*.patch 60215322d3fbbc2054dfc160a20d9e0811af88487c4edc2f6ea81dcd5cedf039 xsa17-qemu-xen-traditional-all.patch 7b4bb59e7757080e7806a8b8eeb6b78fa0ffdfbfb28a7a379f7edff285bffd88 xsa17-qemu-xen-unstable.patch -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.10 (GNU/Linux) iQEcBAEBAgAGBQJQRx1PAAoJEIP+FMlX6CvZUqUH/jeAAvQnoBp6YKzm78XSnnmk GI2C/LhH0xqR3wFoEmWeMsiO4lrGrASX6T31NTvHa8sOtFqlNpTfRhwQybwYR3aa cz9/4y2a54hD95P1nVmPF0PddmSP47QSpRdCj0projq1UGxIdwEhkNeSoM8h7dXO MegqZClsvJMKd8XEcjBF5Qg7u9vLrXilCx5+It7XNE31Jxpkr/fozBb7FnNtDGJj s4RN/UDU4Pu68XyZ7Dc5xEFdJW48tz4BIlxxXavILBRFSE1VEf7Gc8H9CsUtBPWB C/LCUjpHkAOmqdgFhiLnZ2u+2s79U0dtPDJMNmqaGgWH+AqGkU9Nq8XXODTyY9k= =gnuE -----END PGP SIGNATURE----- --=separator Content-Type: application/octet-stream; name="xsa17-qemu-xen-traditional-all.patch" Content-Disposition: attachment; filename="xsa17-qemu-xen-traditional-all.patch" Content-Transfer-Encoding: base64 Y29uc29sZTogYm91bmRzIGNoZWNrIHdoZW5ldmVyIGNoYW5naW5nIHRoZSBj dXJzb3IgZHVlIHRvIGFuIGVzY2FwZSBjb2RlCgpUaGlzIGlzIFhTQS0xNyAv IENWRS0yMDEyLTM1MTUKClNpZ25lZC1vZmYtYnk6IElhbiBDYW1wYmVsbCA8 aWFuLmNhbXBiZWxsQGNpdHJpeC5jb20+CgpkaWZmIC0tZ2l0IGEvY29uc29s ZS5jIGIvY29uc29sZS5jCmluZGV4IDVlNmUzZDAuLjk5ODRkNmYgMTAwNjQ0 Ci0tLSBhL2NvbnNvbGUuYworKysgYi9jb25zb2xlLmMKQEAgLTc5NCw2ICs3 OTQsMjYgQEAgc3RhdGljIHZvaWQgY29uc29sZV9jbGVhcl94eShUZXh0Q29u c29sZSAqcywgaW50IHgsIGludCB5KQogICAgIHVwZGF0ZV94eShzLCB4LCB5 KTsKIH0KIAorLyogc2V0IGN1cnNvciwgY2hlY2tpbmcgYm91bmRzICovCitz dGF0aWMgdm9pZCBzZXRfY3Vyc29yKFRleHRDb25zb2xlICpzLCBpbnQgeCwg aW50IHkpCit7CisgICAgaWYgKHggPCAwKSB7CisgICAgICAgIHggPSAwOwor ICAgIH0KKyAgICBpZiAoeSA8IDApIHsKKyAgICAgICAgeSA9IDA7CisgICAg fQorICAgIGlmICh5ID49IHMtPmhlaWdodCkgeworICAgICAgICB5ID0gcy0+ aGVpZ2h0IC0gMTsKKyAgICB9CisgICAgaWYgKHggPj0gcy0+d2lkdGgpIHsK KyAgICAgICAgeCA9IHMtPndpZHRoIC0gMTsKKyAgICB9CisKKyAgICBzLT54 ID0geDsKKyAgICBzLT55ID0geTsKK30KKwogc3RhdGljIHZvaWQgY29uc29s ZV9wdXRjaGFyKFRleHRDb25zb2xlICpzLCBpbnQgY2gpCiB7CiAgICAgVGV4 dENlbGwgKmM7CkBAIC04NjksNyArODg5LDggQEAgc3RhdGljIHZvaWQgY29u c29sZV9wdXRjaGFyKFRleHRDb25zb2xlICpzLCBpbnQgY2gpCiAgICAgICAg ICAgICAgICAgICAgIHMtPmVzY19wYXJhbXNbcy0+bmJfZXNjX3BhcmFtc10g KiAxMCArIGNoIC0gJzAnOwogICAgICAgICAgICAgfQogICAgICAgICB9IGVs c2UgewotICAgICAgICAgICAgcy0+bmJfZXNjX3BhcmFtcysrOworICAgICAg ICAgICAgaWYgKHMtPm5iX2VzY19wYXJhbXMgPCBNQVhfRVNDX1BBUkFNUykK KyAgICAgICAgICAgICAgICBzLT5uYl9lc2NfcGFyYW1zKys7CiAgICAgICAg ICAgICBpZiAoY2ggPT0gJzsnKQogICAgICAgICAgICAgICAgIGJyZWFrOwog I2lmZGVmIERFQlVHX0NPTlNPTEUKQEAgLTg4Myw1OSArOTA0LDM3IEBAIHN0 YXRpYyB2b2lkIGNvbnNvbGVfcHV0Y2hhcihUZXh0Q29uc29sZSAqcywgaW50 IGNoKQogICAgICAgICAgICAgICAgIGlmIChzLT5lc2NfcGFyYW1zWzBdID09 IDApIHsKICAgICAgICAgICAgICAgICAgICAgcy0+ZXNjX3BhcmFtc1swXSA9 IDE7CiAgICAgICAgICAgICAgICAgfQotICAgICAgICAgICAgICAgIHMtPnkg LT0gcy0+ZXNjX3BhcmFtc1swXTsKLSAgICAgICAgICAgICAgICBpZiAocy0+ eSA8IDApIHsKLSAgICAgICAgICAgICAgICAgICAgcy0+eSA9IDA7Ci0gICAg ICAgICAgICAgICAgfQorICAgICAgICAgICAgICAgIHNldF9jdXJzb3Iocywg cy0+eCwgcy0+eSAtIHMtPmVzY19wYXJhbXNbMF0pOwogICAgICAgICAgICAg ICAgIGJyZWFrOwogICAgICAgICAgICAgY2FzZSAnQic6CiAgICAgICAgICAg ICAgICAgLyogbW92ZSBjdXJzb3IgZG93biAqLwogICAgICAgICAgICAgICAg IGlmIChzLT5lc2NfcGFyYW1zWzBdID09IDApIHsKICAgICAgICAgICAgICAg ICAgICAgcy0+ZXNjX3BhcmFtc1swXSA9IDE7CiAgICAgICAgICAgICAgICAg fQotICAgICAgICAgICAgICAgIHMtPnkgKz0gcy0+ZXNjX3BhcmFtc1swXTsK LSAgICAgICAgICAgICAgICBpZiAocy0+eSA+PSBzLT5oZWlnaHQpIHsKLSAg ICAgICAgICAgICAgICAgICAgcy0+eSA9IHMtPmhlaWdodCAtIDE7Ci0gICAg ICAgICAgICAgICAgfQorICAgICAgICAgICAgICAgIHNldF9jdXJzb3Iocywg cy0+eCwgcy0+eSArIHMtPmVzY19wYXJhbXNbMF0pOwogICAgICAgICAgICAg ICAgIGJyZWFrOwogICAgICAgICAgICAgY2FzZSAnQyc6CiAgICAgICAgICAg ICAgICAgLyogbW92ZSBjdXJzb3IgcmlnaHQgKi8KICAgICAgICAgICAgICAg ICBpZiAocy0+ZXNjX3BhcmFtc1swXSA9PSAwKSB7CiAgICAgICAgICAgICAg ICAgICAgIHMtPmVzY19wYXJhbXNbMF0gPSAxOwogICAgICAgICAgICAgICAg IH0KLSAgICAgICAgICAgICAgICBzLT54ICs9IHMtPmVzY19wYXJhbXNbMF07 Ci0gICAgICAgICAgICAgICAgaWYgKHMtPnggPj0gcy0+d2lkdGgpIHsKLSAg ICAgICAgICAgICAgICAgICAgcy0+eCA9IHMtPndpZHRoIC0gMTsKLSAgICAg ICAgICAgICAgICB9CisgICAgICAgICAgICAgICAgc2V0X2N1cnNvcihzLCBz LT54ICsgcy0+ZXNjX3BhcmFtc1swXSwgcy0+eSk7CiAgICAgICAgICAgICAg ICAgYnJlYWs7CiAgICAgICAgICAgICBjYXNlICdEJzoKICAgICAgICAgICAg ICAgICAvKiBtb3ZlIGN1cnNvciBsZWZ0ICovCiAgICAgICAgICAgICAgICAg aWYgKHMtPmVzY19wYXJhbXNbMF0gPT0gMCkgewogICAgICAgICAgICAgICAg ICAgICBzLT5lc2NfcGFyYW1zWzBdID0gMTsKICAgICAgICAgICAgICAgICB9 Ci0gICAgICAgICAgICAgICAgcy0+eCAtPSBzLT5lc2NfcGFyYW1zWzBdOwot ICAgICAgICAgICAgICAgIGlmIChzLT54IDwgMCkgewotICAgICAgICAgICAg ICAgICAgICBzLT54ID0gMDsKLSAgICAgICAgICAgICAgICB9CisgICAgICAg ICAgICAgICAgc2V0X2N1cnNvcihzLCBzLT54IC0gcy0+ZXNjX3BhcmFtc1sw XSwgcy0+eSk7CiAgICAgICAgICAgICAgICAgYnJlYWs7CiAgICAgICAgICAg ICBjYXNlICdHJzoKICAgICAgICAgICAgICAgICAvKiBtb3ZlIGN1cnNvciB0 byBjb2x1bW4gKi8KLSAgICAgICAgICAgICAgICBzLT54ID0gcy0+ZXNjX3Bh cmFtc1swXSAtIDE7Ci0gICAgICAgICAgICAgICAgaWYgKHMtPnggPCAwKSB7 Ci0gICAgICAgICAgICAgICAgICAgIHMtPnggPSAwOwotICAgICAgICAgICAg ICAgIH0KKyAgICAgICAgICAgICAgICBzZXRfY3Vyc29yKHMsIHMtPmVzY19w YXJhbXNbMF0gLSAxLCBzLT55KTsKICAgICAgICAgICAgICAgICBicmVhazsK ICAgICAgICAgICAgIGNhc2UgJ2YnOgogICAgICAgICAgICAgY2FzZSAnSCc6 CiAgICAgICAgICAgICAgICAgLyogbW92ZSBjdXJzb3IgdG8gcm93LCBjb2x1 bW4gKi8KLSAgICAgICAgICAgICAgICBzLT54ID0gcy0+ZXNjX3BhcmFtc1sx XSAtIDE7Ci0gICAgICAgICAgICAgICAgaWYgKHMtPnggPCAwKSB7Ci0gICAg ICAgICAgICAgICAgICAgIHMtPnggPSAwOwotICAgICAgICAgICAgICAgIH0K LSAgICAgICAgICAgICAgICBzLT55ID0gcy0+ZXNjX3BhcmFtc1swXSAtIDE7 Ci0gICAgICAgICAgICAgICAgaWYgKHMtPnkgPCAwKSB7Ci0gICAgICAgICAg ICAgICAgICAgIHMtPnkgPSAwOwotICAgICAgICAgICAgICAgIH0KKyAgICAg ICAgICAgICAgICBzZXRfY3Vyc29yKHMsIHMtPmVzY19wYXJhbXNbMV0gLSAx LCBzLT5lc2NfcGFyYW1zWzBdIC0gMSk7CiAgICAgICAgICAgICAgICAgYnJl YWs7CiAgICAgICAgICAgICBjYXNlICdKJzoKICAgICAgICAgICAgICAgICBz d2l0Y2ggKHMtPmVzY19wYXJhbXNbMF0pIHsK --=separator Content-Type: application/octet-stream; name="xsa17-qemu-xen-unstable.patch" Content-Disposition: attachment; filename="xsa17-qemu-xen-unstable.patch" Content-Transfer-Encoding: base64 Y29uc29sZTogYm91bmRzIGNoZWNrIHdoZW5ldmVyIGNoYW5naW5nIHRoZSBj dXJzb3IgZHVlIHRvIGFuIGVzY2FwZSBjb2RlCgpUaGlzIGlzIFhTQS0xNyAv IENWRS0yMDEyLTM1MTUKClNpZ25lZC1vZmYtYnk6IElhbiBDYW1wYmVsbCA8 aWFuLmNhbXBiZWxsQGNpdHJpeC5jb20+CgpkaWZmIC0tZ2l0IGEvY29uc29s ZS5jIGIvY29uc29sZS5jCmluZGV4IGVkNmE2NTMuLmJmYWQzNjAgMTAwNjQ0 Ci0tLSBhL2NvbnNvbGUuYworKysgYi9jb25zb2xlLmMKQEAgLTg0MSw2ICs4 NDEsMjYgQEAgc3RhdGljIHZvaWQgY29uc29sZV9jbGVhcl94eShUZXh0Q29u c29sZSAqcywgaW50IHgsIGludCB5KQogICAgIHVwZGF0ZV94eShzLCB4LCB5 KTsKIH0KIAorLyogc2V0IGN1cnNvciwgY2hlY2tpbmcgYm91bmRzICovCitz dGF0aWMgdm9pZCBzZXRfY3Vyc29yKFRleHRDb25zb2xlICpzLCBpbnQgeCwg aW50IHkpCit7CisgICAgaWYgKHggPCAwKSB7CisgICAgICAgIHggPSAwOwor ICAgIH0KKyAgICBpZiAoeSA8IDApIHsKKyAgICAgICAgeSA9IDA7CisgICAg fQorICAgIGlmICh5ID49IHMtPmhlaWdodCkgeworICAgICAgICB5ID0gcy0+ aGVpZ2h0IC0gMTsKKyAgICB9CisgICAgaWYgKHggPj0gcy0+d2lkdGgpIHsK KyAgICAgICAgeCA9IHMtPndpZHRoIC0gMTsKKyAgICB9CisKKyAgICBzLT54 ID0geDsKKyAgICBzLT55ID0geTsKK30KKwogc3RhdGljIHZvaWQgY29uc29s ZV9wdXRjaGFyKFRleHRDb25zb2xlICpzLCBpbnQgY2gpCiB7CiAgICAgVGV4 dENlbGwgKmM7CkBAIC05MTIsNyArOTMyLDggQEAgc3RhdGljIHZvaWQgY29u c29sZV9wdXRjaGFyKFRleHRDb25zb2xlICpzLCBpbnQgY2gpCiAgICAgICAg ICAgICAgICAgICAgIHMtPmVzY19wYXJhbXNbcy0+bmJfZXNjX3BhcmFtc10g KiAxMCArIGNoIC0gJzAnOwogICAgICAgICAgICAgfQogICAgICAgICB9IGVs c2UgewotICAgICAgICAgICAgcy0+bmJfZXNjX3BhcmFtcysrOworICAgICAg ICAgICAgaWYgKHMtPm5iX2VzY19wYXJhbXMgPCBNQVhfRVNDX1BBUkFNUykK KyAgICAgICAgICAgICAgICBzLT5uYl9lc2NfcGFyYW1zKys7CiAgICAgICAg ICAgICBpZiAoY2ggPT0gJzsnKQogICAgICAgICAgICAgICAgIGJyZWFrOwog I2lmZGVmIERFQlVHX0NPTlNPTEUKQEAgLTkyNiw1OSArOTQ3LDM3IEBAIHN0 YXRpYyB2b2lkIGNvbnNvbGVfcHV0Y2hhcihUZXh0Q29uc29sZSAqcywgaW50 IGNoKQogICAgICAgICAgICAgICAgIGlmIChzLT5lc2NfcGFyYW1zWzBdID09 IDApIHsKICAgICAgICAgICAgICAgICAgICAgcy0+ZXNjX3BhcmFtc1swXSA9 IDE7CiAgICAgICAgICAgICAgICAgfQotICAgICAgICAgICAgICAgIHMtPnkg LT0gcy0+ZXNjX3BhcmFtc1swXTsKLSAgICAgICAgICAgICAgICBpZiAocy0+ eSA8IDApIHsKLSAgICAgICAgICAgICAgICAgICAgcy0+eSA9IDA7Ci0gICAg ICAgICAgICAgICAgfQorICAgICAgICAgICAgICAgIHNldF9jdXJzb3Iocywg cy0+eCwgcy0+eSAtIHMtPmVzY19wYXJhbXNbMF0pOwogICAgICAgICAgICAg ICAgIGJyZWFrOwogICAgICAgICAgICAgY2FzZSAnQic6CiAgICAgICAgICAg ICAgICAgLyogbW92ZSBjdXJzb3IgZG93biAqLwogICAgICAgICAgICAgICAg IGlmIChzLT5lc2NfcGFyYW1zWzBdID09IDApIHsKICAgICAgICAgICAgICAg ICAgICAgcy0+ZXNjX3BhcmFtc1swXSA9IDE7CiAgICAgICAgICAgICAgICAg fQotICAgICAgICAgICAgICAgIHMtPnkgKz0gcy0+ZXNjX3BhcmFtc1swXTsK LSAgICAgICAgICAgICAgICBpZiAocy0+eSA+PSBzLT5oZWlnaHQpIHsKLSAg ICAgICAgICAgICAgICAgICAgcy0+eSA9IHMtPmhlaWdodCAtIDE7Ci0gICAg ICAgICAgICAgICAgfQorICAgICAgICAgICAgICAgIHNldF9jdXJzb3Iocywg cy0+eCwgcy0+eSArIHMtPmVzY19wYXJhbXNbMF0pOwogICAgICAgICAgICAg ICAgIGJyZWFrOwogICAgICAgICAgICAgY2FzZSAnQyc6CiAgICAgICAgICAg ICAgICAgLyogbW92ZSBjdXJzb3IgcmlnaHQgKi8KICAgICAgICAgICAgICAg ICBpZiAocy0+ZXNjX3BhcmFtc1swXSA9PSAwKSB7CiAgICAgICAgICAgICAg ICAgICAgIHMtPmVzY19wYXJhbXNbMF0gPSAxOwogICAgICAgICAgICAgICAg IH0KLSAgICAgICAgICAgICAgICBzLT54ICs9IHMtPmVzY19wYXJhbXNbMF07 Ci0gICAgICAgICAgICAgICAgaWYgKHMtPnggPj0gcy0+d2lkdGgpIHsKLSAg ICAgICAgICAgICAgICAgICAgcy0+eCA9IHMtPndpZHRoIC0gMTsKLSAgICAg ICAgICAgICAgICB9CisgICAgICAgICAgICAgICAgc2V0X2N1cnNvcihzLCBz LT54ICsgcy0+ZXNjX3BhcmFtc1swXSwgcy0+eSk7CiAgICAgICAgICAgICAg ICAgYnJlYWs7CiAgICAgICAgICAgICBjYXNlICdEJzoKICAgICAgICAgICAg ICAgICAvKiBtb3ZlIGN1cnNvciBsZWZ0ICovCiAgICAgICAgICAgICAgICAg aWYgKHMtPmVzY19wYXJhbXNbMF0gPT0gMCkgewogICAgICAgICAgICAgICAg ICAgICBzLT5lc2NfcGFyYW1zWzBdID0gMTsKICAgICAgICAgICAgICAgICB9 Ci0gICAgICAgICAgICAgICAgcy0+eCAtPSBzLT5lc2NfcGFyYW1zWzBdOwot ICAgICAgICAgICAgICAgIGlmIChzLT54IDwgMCkgewotICAgICAgICAgICAg ICAgICAgICBzLT54ID0gMDsKLSAgICAgICAgICAgICAgICB9CisgICAgICAg ICAgICAgICAgc2V0X2N1cnNvcihzLCBzLT54IC0gcy0+ZXNjX3BhcmFtc1sw XSwgcy0+eSk7CiAgICAgICAgICAgICAgICAgYnJlYWs7CiAgICAgICAgICAg ICBjYXNlICdHJzoKICAgICAgICAgICAgICAgICAvKiBtb3ZlIGN1cnNvciB0 byBjb2x1bW4gKi8KLSAgICAgICAgICAgICAgICBzLT54ID0gcy0+ZXNjX3Bh cmFtc1swXSAtIDE7Ci0gICAgICAgICAgICAgICAgaWYgKHMtPnggPCAwKSB7 Ci0gICAgICAgICAgICAgICAgICAgIHMtPnggPSAwOwotICAgICAgICAgICAg ICAgIH0KKyAgICAgICAgICAgICAgICBzZXRfY3Vyc29yKHMsIHMtPmVzY19w YXJhbXNbMF0gLSAxLCBzLT55KTsKICAgICAgICAgICAgICAgICBicmVhazsK ICAgICAgICAgICAgIGNhc2UgJ2YnOgogICAgICAgICAgICAgY2FzZSAnSCc6 CiAgICAgICAgICAgICAgICAgLyogbW92ZSBjdXJzb3IgdG8gcm93LCBjb2x1 bW4gKi8KLSAgICAgICAgICAgICAgICBzLT54ID0gcy0+ZXNjX3BhcmFtc1sx XSAtIDE7Ci0gICAgICAgICAgICAgICAgaWYgKHMtPnggPCAwKSB7Ci0gICAg ICAgICAgICAgICAgICAgIHMtPnggPSAwOwotICAgICAgICAgICAgICAgIH0K LSAgICAgICAgICAgICAgICBzLT55ID0gcy0+ZXNjX3BhcmFtc1swXSAtIDE7 Ci0gICAgICAgICAgICAgICAgaWYgKHMtPnkgPCAwKSB7Ci0gICAgICAgICAg ICAgICAgICAgIHMtPnkgPSAwOwotICAgICAgICAgICAgICAgIH0KKyAgICAg ICAgICAgICAgICBzZXRfY3Vyc29yKHMsIHMtPmVzY19wYXJhbXNbMV0gLSAx LCBzLT5lc2NfcGFyYW1zWzBdIC0gMSk7CiAgICAgICAgICAgICAgICAgYnJl YWs7CiAgICAgICAgICAgICBjYXNlICdKJzoKICAgICAgICAgICAgICAgICBz d2l0Y2ggKHMtPmVzY19wYXJhbXNbMF0pIHsK --=separator Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users --=separator-- From xen-users-bounces@lists.xen.org Wed Sep 05 11:16:53 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Wed, 05 Sep 2012 11:16:53 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1T9Das-0005C0-47; Wed, 05 Sep 2012 11:16:26 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1T9DVc-0004hj-Je for xen-users@lists.xen.org; Wed, 05 Sep 2012 11:11:00 +0000 Received: from [85.158.143.99:60864] by server-1.bemta-4.messagelabs.com id 10/C3-12504-24337405; Wed, 05 Sep 2012 11:10:58 +0000 X-Env-Sender: iwj@xenbits.xen.org X-Msg-Ref: server-11.tower-216.messagelabs.com!1346843448!21117190!1 X-Originating-IP: [50.57.168.107] X-SpamReason: No, hits=0.5 required=7.0 tests=BODY_RANDOM_LONG X-StarScan-Received: X-StarScan-Version: 6.6.1.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 19330 invoked from network); 5 Sep 2012 11:10:50 -0000 Received: from mail.xen.org (HELO mail.xen.org) (50.57.168.107) by server-11.tower-216.messagelabs.com with AES256-SHA encrypted SMTP; 5 Sep 2012 11:10:50 -0000 Received: from xenbits.xen.org ([50.57.170.242]) by mail.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1T9DVJ-0001Az-MN; Wed, 05 Sep 2012 11:10:41 +0000 Received: from iwj by xenbits.xen.org with local (Exim 4.72) (envelope-from ) id 1T9DVJ-0005Jh-0F; Wed, 05 Sep 2012 11:10:41 +0000 Date: Wed, 05 Sep 2012 11:10:41 +0000 Message-Id: Content-Type: multipart/mixed; boundary="=separator"; charset="utf-8" Content-Transfer-Encoding: binary MIME-Version: 1.0 X-Mailer: MIME-tools 5.428 (Entity 5.428) To: xen-announce@lists.xen.org, xen-devel@lists.xen.org, xen-users@lists.xen.org, oss-security@lists.openwall.com From: Xen.org security team X-Mailman-Approved-At: Wed, 05 Sep 2012 11:16:25 +0000 Cc: "Xen.org security team" Subject: [Xen-users] Xen Security Advisory 15 (CVE-2012-3497) - multiple TMEM hypercall vulnerabilities X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org --=separator Content-Type: text/plain; charset="utf-8" Content-Disposition: inline Content-Transfer-Encoding: 7bit -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Xen Security Advisory CVE-2012-3497 / XSA-15 version 2 multiple TMEM hypercall vulnerabilities UPDATES IN VERSION 2 ==================== Public release. Credit Matthew Daley. ISSUE DESCRIPTION ================= Several sub-operations of the Transcendent Memory (TMEM) hypercall either do not correctly validate their inputs, do not correctly validate the privilege of the calling guest, or have other security-relevant bugs. A full list of the vulnerabilities in the TMEM system is not available at present. IMPACT ====== An unprivileged guest can overwrite hypervisor owned memory with the content of their choosing allowing them to escalate their privilege to that of the host. In addition an unprivileged guest can also crash the hypervisor, leading to a Denial of Service attack. VULNERABLE SYSTEMS ================== ONLY installations where "tmem" is specified on the hypervisor command line are vulnerable. Most Xen installations do not do so. All versions of Xen from 4.0 onward which have TMEM enabled and are running guests with untrusted administrators are vulnerable. Although we consider it unlikely, we have not been able to rule out the possibility that an malicious unprivileged user could exploit these issues via a trusted TMEM-aware kernel. Therefore all administrators are advised to disable TMEM even if all guest kernels are controlled and trusted. MITIGATION ========== Only systems which have TMEM enabled at boot time are affected by this issue. By default TMEM is disabled unless it is explicitly enabled via the hypervisor command line option "tmem". TMEM has been described by its maintainers as a technology preview, and is therefore not supported by them for use in production systems. Pending a full security audit of the code, the Xen.org security team recommends that Xen users do not enable TMEM. RESOLUTION ========== Work is ongoing, by the community maintainers for TMEM, to patch the specific bugs as they are found. This includes both the multiple vulnerabilities initially reported to the Xen.org security team, and multiple further vulnerabilities which have been discovered since then during our ad-hoc code inspection. At the time of writing, a complete set of fixes even for known issues is not available. PROCESS FOR TMEM VULNERABILITIES ================================ Until TMEM has gained production maturity, the Xen.org security team intends (subject of course to the permission of anyone disclosing to us) to handle these and future TMEM vulnerabilities in public, as if they were normal non-security-related bugs. We therefore intend that currently-known vulnerabilities will be publicly disclosed on the xen-devel mailing list, as normal bug reports, at the expiry of the XSA-15 embargo. In the meantime the list below may be helpful. Xen.org security team will ensure, on expiry of the embargo, that the documentation reflects TMEM's technology preview status. CREDIT ====== Thanks to Matthew Daley for finding these vulnerabilities (and that in XSA-12) and notifying the Xen.org security team. LIST OF KNOWN VULNERABILITIES ============================= **NOTE** that this is unlikely to be a complete list of problems. **NOTE** that after publication of this advisory, after the embargo ends, the advisory will no longer be updated to extend this list of vulnerabilities. See `Process for TMEM vulnerabilities', above. Multiple tmem save-related control ops do not check for NULL clients: TMEMC_SAVE_GET_CLIENT_WEIGHT, TMEMC_SAVE_GET_CLIENT_CAP, TMEMC_SAVE_GET_CLIENT_FLAGS and TMEMC_SAVE_END do not check that the cli_id used to find the client is valid, and can hence dereference a NULL client. This allows a malicious guest to crash the host (DoS), or, in the case of TMEMC_SAVE_END, memory corruption (DoS or worse). Multiple tmem save-related control ops do not check guest output buffer pointers: The functions tmemc_save_get_next_page, tmemc_save_get_next_inv and the TMEMC_SAVE_GET_POOL_UUID subop do not check incoming guest output buffer pointers, and do not use ie. copy_to_guest. A malicious guest can crash the host or cause memory corruption (DoS / code execution). Multiple tmem ops do not check for negative pool IDs: The functions tmemc_save_get_next_page, tmemc_restore_put_page and tmemc_restore_flush_page do not check for negative pool IDs, allowing (at least) memory corruption. do_tmem_destroy_pool does not check for invalid pool IDs: The function do_tmem_destroy_pool does not check for invalid pool IDs, allowing a malicious guest to crash the host or corrupt host memory (DoS / code execution). do_tmem_control's privilege check is commented out: This allows any guest access to control stack operations (many of which themselves do not have adequate argument checking). tmh_copy_from_client and tmh_copy_to_client have an integer overflow vulnerability: This can corrupt host memory. do_tmem_get()'s bad_copy error path leaves a spinlock held: The next operation on the same object will hang the CPU. This is a host DoS. do_tmem_op has at least one error path with broken locking checks: This is a host DoS or worse. -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.10 (GNU/Linux) iQEcBAEBAgAGBQJQRyVDAAoJEIP+FMlX6CvZZSEH/11RvLycH5Qm0rkmWb16iuRU s9xmGDxGr6LDGLLYenp7RDc6FU7xjFxNeMhziIWckic2f0V1UtEqxiTHViEeOsOu AQfiwrUaaSf+fwcDqt07bb6gTynxyqS+faLKpk4bq89tKK1318JlxWN2gRtEW5g9 KEo7Bt/O0hYuIJBlBWnH48OHPzGSrwVaw51NLt0oPqiWp4w3ObLRhVttKB7VWJlw OQR9hSStVWhKR68VUBd/LpTZTkX/Hn5qwhX6ltgQ10RW1n4cF2pvebiKu6CtePCl JVBJgn/4ZmaT1joJ8SpX/BONnLt0KHNrublB6vO++1m+7+lBA5qXL38gg4jl48E= =yP/R -----END PGP SIGNATURE----- --=separator Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users --=separator-- From xen-users-bounces@lists.xen.org Wed Sep 05 11:16:53 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Wed, 05 Sep 2012 11:16:53 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1T9Dat-0005CM-GP; Wed, 05 Sep 2012 11:16:27 +0000 Received: from mail27.messagelabs.com ([193.109.254.147]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1T9DYi-00053C-Vt; Wed, 05 Sep 2012 11:14:13 +0000 X-Env-Sender: iwj@xenbits.xen.org X-Msg-Ref: server-5.tower-27.messagelabs.com!1346843573!6253309!1 X-Originating-IP: [50.57.168.107] X-SpamReason: No, hits=0.5 required=7.0 tests=BODY_RANDOM_LONG X-StarScan-Received: X-StarScan-Version: 6.6.1.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 16021 invoked from network); 5 Sep 2012 11:12:55 -0000 Received: from mail.xen.org (HELO mail.xen.org) (50.57.168.107) by server-5.tower-27.messagelabs.com with AES256-SHA encrypted SMTP; 5 Sep 2012 11:12:55 -0000 Received: from xenbits.xen.org ([50.57.170.242]) by mail.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1T9DXL-0001Cr-Dg; Wed, 05 Sep 2012 11:12:47 +0000 Received: from iwj by xenbits.xen.org with local (Exim 4.72) (envelope-from ) id 1T9DXL-0005Qu-97; Wed, 05 Sep 2012 11:12:47 +0000 Date: Wed, 05 Sep 2012 11:12:47 +0000 Message-Id: Content-Type: multipart/mixed; boundary="=separator"; charset="utf-8" Content-Transfer-Encoding: binary MIME-Version: 1.0 X-Mailer: MIME-tools 5.428 (Entity 5.428) To: xen-announce@lists.xen.org, xen-devel@lists.xen.org, xen-users@lists.xen.org, oss-security@lists.openwall.com From: Xen.org security team X-Mailman-Approved-At: Wed, 05 Sep 2012 11:16:25 +0000 Cc: "Xen.org security team" Subject: [Xen-users] Xen Security Advisory 17 (CVE-2012-3515) - Qemu VT100 emulation vulnerability X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org --=separator Content-Type: text/plain; charset="utf-8" Content-Disposition: inline Content-Transfer-Encoding: 7bit -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Xen Security Advisory CVE-2012-3515 / XSA-17 version 2 Qemu VT100 emulation vulnerability UPDATES IN VERSION 2 ==================== Public release. ISSUE DESCRIPTION ================= The device model used by fully virtualised (HVM) domains, qemu, does not properly handle escape VT100 sequences when emulating certain devices with a virtual console backend. IMPACT ====== An attacker who has sufficient privilege to access a vulnerable device within a guest can overwrite portions of the device model's address space. This can allow them to escalate their privileges to that of the device model process. VULNERABLE SYSTEMS ================== All Xen systems running HVM guests are potentially vulnerable to this depending on the specific guest configuration. The default configuration is vulnerable. Guests using either the traditional "qemu-xen" or upstream qemu device models are vulnerable. MITIGATION ========== This issue can be avoided by only running PV guests or by configuring HVM guests to not use the virtual console('vc') backend for any device. For serial devices specify in your guest configuration: serial = 'none' in your guest configuration. For parallel port devices the syntax is toolstack specific. For xend specify in your guest configuration: parallel = 'none' For xl specify in your guest configuration: xl: device_model_args = ['-parallel', 'none'] In both cases the default is to use the vulnerable 'vc' mode. You can confirm whether or not you are vulnerable by pressing Ctrl-Alt- (for digit N) while connected to either the VNC or SDL console. If you are able to switch to a window displaying "serial" or "parallel" then you are vulnerable. The issue can also be mitigated by enabling the stub domain device model. In this case the attacked can only potentially gain control of the stub domain and not of the entire system. To enable stub domains specify in your guest configuration: device_model = "stubdom-dm" RESOLUTION ========== Applying the appropriate attached patch(es) will resolve the issue. PATCH INFORMATION ================= The attached patches resolve this issue Traditional qemu tree Xen 4.0, 4.1 and unstable xsa17-qemu-xen-traditional-all.patch Upstream qemu tree (present in unstable only) Xen unstable xsa17-qemu-xen-unstable.patch $ sha256sum xsa17-*.patch 60215322d3fbbc2054dfc160a20d9e0811af88487c4edc2f6ea81dcd5cedf039 xsa17-qemu-xen-traditional-all.patch 7b4bb59e7757080e7806a8b8eeb6b78fa0ffdfbfb28a7a379f7edff285bffd88 xsa17-qemu-xen-unstable.patch -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.10 (GNU/Linux) iQEcBAEBAgAGBQJQRx1PAAoJEIP+FMlX6CvZUqUH/jeAAvQnoBp6YKzm78XSnnmk GI2C/LhH0xqR3wFoEmWeMsiO4lrGrASX6T31NTvHa8sOtFqlNpTfRhwQybwYR3aa cz9/4y2a54hD95P1nVmPF0PddmSP47QSpRdCj0projq1UGxIdwEhkNeSoM8h7dXO MegqZClsvJMKd8XEcjBF5Qg7u9vLrXilCx5+It7XNE31Jxpkr/fozBb7FnNtDGJj s4RN/UDU4Pu68XyZ7Dc5xEFdJW48tz4BIlxxXavILBRFSE1VEf7Gc8H9CsUtBPWB C/LCUjpHkAOmqdgFhiLnZ2u+2s79U0dtPDJMNmqaGgWH+AqGkU9Nq8XXODTyY9k= =gnuE -----END PGP SIGNATURE----- --=separator Content-Type: application/octet-stream; name="xsa17-qemu-xen-traditional-all.patch" Content-Disposition: attachment; filename="xsa17-qemu-xen-traditional-all.patch" Content-Transfer-Encoding: base64 Y29uc29sZTogYm91bmRzIGNoZWNrIHdoZW5ldmVyIGNoYW5naW5nIHRoZSBj dXJzb3IgZHVlIHRvIGFuIGVzY2FwZSBjb2RlCgpUaGlzIGlzIFhTQS0xNyAv IENWRS0yMDEyLTM1MTUKClNpZ25lZC1vZmYtYnk6IElhbiBDYW1wYmVsbCA8 aWFuLmNhbXBiZWxsQGNpdHJpeC5jb20+CgpkaWZmIC0tZ2l0IGEvY29uc29s ZS5jIGIvY29uc29sZS5jCmluZGV4IDVlNmUzZDAuLjk5ODRkNmYgMTAwNjQ0 Ci0tLSBhL2NvbnNvbGUuYworKysgYi9jb25zb2xlLmMKQEAgLTc5NCw2ICs3 OTQsMjYgQEAgc3RhdGljIHZvaWQgY29uc29sZV9jbGVhcl94eShUZXh0Q29u c29sZSAqcywgaW50IHgsIGludCB5KQogICAgIHVwZGF0ZV94eShzLCB4LCB5 KTsKIH0KIAorLyogc2V0IGN1cnNvciwgY2hlY2tpbmcgYm91bmRzICovCitz dGF0aWMgdm9pZCBzZXRfY3Vyc29yKFRleHRDb25zb2xlICpzLCBpbnQgeCwg aW50IHkpCit7CisgICAgaWYgKHggPCAwKSB7CisgICAgICAgIHggPSAwOwor ICAgIH0KKyAgICBpZiAoeSA8IDApIHsKKyAgICAgICAgeSA9IDA7CisgICAg fQorICAgIGlmICh5ID49IHMtPmhlaWdodCkgeworICAgICAgICB5ID0gcy0+ aGVpZ2h0IC0gMTsKKyAgICB9CisgICAgaWYgKHggPj0gcy0+d2lkdGgpIHsK KyAgICAgICAgeCA9IHMtPndpZHRoIC0gMTsKKyAgICB9CisKKyAgICBzLT54 ID0geDsKKyAgICBzLT55ID0geTsKK30KKwogc3RhdGljIHZvaWQgY29uc29s ZV9wdXRjaGFyKFRleHRDb25zb2xlICpzLCBpbnQgY2gpCiB7CiAgICAgVGV4 dENlbGwgKmM7CkBAIC04NjksNyArODg5LDggQEAgc3RhdGljIHZvaWQgY29u c29sZV9wdXRjaGFyKFRleHRDb25zb2xlICpzLCBpbnQgY2gpCiAgICAgICAg ICAgICAgICAgICAgIHMtPmVzY19wYXJhbXNbcy0+bmJfZXNjX3BhcmFtc10g KiAxMCArIGNoIC0gJzAnOwogICAgICAgICAgICAgfQogICAgICAgICB9IGVs c2UgewotICAgICAgICAgICAgcy0+bmJfZXNjX3BhcmFtcysrOworICAgICAg ICAgICAgaWYgKHMtPm5iX2VzY19wYXJhbXMgPCBNQVhfRVNDX1BBUkFNUykK KyAgICAgICAgICAgICAgICBzLT5uYl9lc2NfcGFyYW1zKys7CiAgICAgICAg ICAgICBpZiAoY2ggPT0gJzsnKQogICAgICAgICAgICAgICAgIGJyZWFrOwog I2lmZGVmIERFQlVHX0NPTlNPTEUKQEAgLTg4Myw1OSArOTA0LDM3IEBAIHN0 YXRpYyB2b2lkIGNvbnNvbGVfcHV0Y2hhcihUZXh0Q29uc29sZSAqcywgaW50 IGNoKQogICAgICAgICAgICAgICAgIGlmIChzLT5lc2NfcGFyYW1zWzBdID09 IDApIHsKICAgICAgICAgICAgICAgICAgICAgcy0+ZXNjX3BhcmFtc1swXSA9 IDE7CiAgICAgICAgICAgICAgICAgfQotICAgICAgICAgICAgICAgIHMtPnkg LT0gcy0+ZXNjX3BhcmFtc1swXTsKLSAgICAgICAgICAgICAgICBpZiAocy0+ eSA8IDApIHsKLSAgICAgICAgICAgICAgICAgICAgcy0+eSA9IDA7Ci0gICAg ICAgICAgICAgICAgfQorICAgICAgICAgICAgICAgIHNldF9jdXJzb3Iocywg cy0+eCwgcy0+eSAtIHMtPmVzY19wYXJhbXNbMF0pOwogICAgICAgICAgICAg ICAgIGJyZWFrOwogICAgICAgICAgICAgY2FzZSAnQic6CiAgICAgICAgICAg ICAgICAgLyogbW92ZSBjdXJzb3IgZG93biAqLwogICAgICAgICAgICAgICAg IGlmIChzLT5lc2NfcGFyYW1zWzBdID09IDApIHsKICAgICAgICAgICAgICAg ICAgICAgcy0+ZXNjX3BhcmFtc1swXSA9IDE7CiAgICAgICAgICAgICAgICAg fQotICAgICAgICAgICAgICAgIHMtPnkgKz0gcy0+ZXNjX3BhcmFtc1swXTsK LSAgICAgICAgICAgICAgICBpZiAocy0+eSA+PSBzLT5oZWlnaHQpIHsKLSAg ICAgICAgICAgICAgICAgICAgcy0+eSA9IHMtPmhlaWdodCAtIDE7Ci0gICAg ICAgICAgICAgICAgfQorICAgICAgICAgICAgICAgIHNldF9jdXJzb3Iocywg cy0+eCwgcy0+eSArIHMtPmVzY19wYXJhbXNbMF0pOwogICAgICAgICAgICAg ICAgIGJyZWFrOwogICAgICAgICAgICAgY2FzZSAnQyc6CiAgICAgICAgICAg ICAgICAgLyogbW92ZSBjdXJzb3IgcmlnaHQgKi8KICAgICAgICAgICAgICAg ICBpZiAocy0+ZXNjX3BhcmFtc1swXSA9PSAwKSB7CiAgICAgICAgICAgICAg ICAgICAgIHMtPmVzY19wYXJhbXNbMF0gPSAxOwogICAgICAgICAgICAgICAg IH0KLSAgICAgICAgICAgICAgICBzLT54ICs9IHMtPmVzY19wYXJhbXNbMF07 Ci0gICAgICAgICAgICAgICAgaWYgKHMtPnggPj0gcy0+d2lkdGgpIHsKLSAg ICAgICAgICAgICAgICAgICAgcy0+eCA9IHMtPndpZHRoIC0gMTsKLSAgICAg ICAgICAgICAgICB9CisgICAgICAgICAgICAgICAgc2V0X2N1cnNvcihzLCBz LT54ICsgcy0+ZXNjX3BhcmFtc1swXSwgcy0+eSk7CiAgICAgICAgICAgICAg ICAgYnJlYWs7CiAgICAgICAgICAgICBjYXNlICdEJzoKICAgICAgICAgICAg ICAgICAvKiBtb3ZlIGN1cnNvciBsZWZ0ICovCiAgICAgICAgICAgICAgICAg aWYgKHMtPmVzY19wYXJhbXNbMF0gPT0gMCkgewogICAgICAgICAgICAgICAg ICAgICBzLT5lc2NfcGFyYW1zWzBdID0gMTsKICAgICAgICAgICAgICAgICB9 Ci0gICAgICAgICAgICAgICAgcy0+eCAtPSBzLT5lc2NfcGFyYW1zWzBdOwot ICAgICAgICAgICAgICAgIGlmIChzLT54IDwgMCkgewotICAgICAgICAgICAg ICAgICAgICBzLT54ID0gMDsKLSAgICAgICAgICAgICAgICB9CisgICAgICAg ICAgICAgICAgc2V0X2N1cnNvcihzLCBzLT54IC0gcy0+ZXNjX3BhcmFtc1sw XSwgcy0+eSk7CiAgICAgICAgICAgICAgICAgYnJlYWs7CiAgICAgICAgICAg ICBjYXNlICdHJzoKICAgICAgICAgICAgICAgICAvKiBtb3ZlIGN1cnNvciB0 byBjb2x1bW4gKi8KLSAgICAgICAgICAgICAgICBzLT54ID0gcy0+ZXNjX3Bh cmFtc1swXSAtIDE7Ci0gICAgICAgICAgICAgICAgaWYgKHMtPnggPCAwKSB7 Ci0gICAgICAgICAgICAgICAgICAgIHMtPnggPSAwOwotICAgICAgICAgICAg ICAgIH0KKyAgICAgICAgICAgICAgICBzZXRfY3Vyc29yKHMsIHMtPmVzY19w YXJhbXNbMF0gLSAxLCBzLT55KTsKICAgICAgICAgICAgICAgICBicmVhazsK ICAgICAgICAgICAgIGNhc2UgJ2YnOgogICAgICAgICAgICAgY2FzZSAnSCc6 CiAgICAgICAgICAgICAgICAgLyogbW92ZSBjdXJzb3IgdG8gcm93LCBjb2x1 bW4gKi8KLSAgICAgICAgICAgICAgICBzLT54ID0gcy0+ZXNjX3BhcmFtc1sx XSAtIDE7Ci0gICAgICAgICAgICAgICAgaWYgKHMtPnggPCAwKSB7Ci0gICAg ICAgICAgICAgICAgICAgIHMtPnggPSAwOwotICAgICAgICAgICAgICAgIH0K LSAgICAgICAgICAgICAgICBzLT55ID0gcy0+ZXNjX3BhcmFtc1swXSAtIDE7 Ci0gICAgICAgICAgICAgICAgaWYgKHMtPnkgPCAwKSB7Ci0gICAgICAgICAg ICAgICAgICAgIHMtPnkgPSAwOwotICAgICAgICAgICAgICAgIH0KKyAgICAg ICAgICAgICAgICBzZXRfY3Vyc29yKHMsIHMtPmVzY19wYXJhbXNbMV0gLSAx LCBzLT5lc2NfcGFyYW1zWzBdIC0gMSk7CiAgICAgICAgICAgICAgICAgYnJl YWs7CiAgICAgICAgICAgICBjYXNlICdKJzoKICAgICAgICAgICAgICAgICBz d2l0Y2ggKHMtPmVzY19wYXJhbXNbMF0pIHsK --=separator Content-Type: application/octet-stream; name="xsa17-qemu-xen-unstable.patch" Content-Disposition: attachment; filename="xsa17-qemu-xen-unstable.patch" Content-Transfer-Encoding: base64 Y29uc29sZTogYm91bmRzIGNoZWNrIHdoZW5ldmVyIGNoYW5naW5nIHRoZSBj dXJzb3IgZHVlIHRvIGFuIGVzY2FwZSBjb2RlCgpUaGlzIGlzIFhTQS0xNyAv IENWRS0yMDEyLTM1MTUKClNpZ25lZC1vZmYtYnk6IElhbiBDYW1wYmVsbCA8 aWFuLmNhbXBiZWxsQGNpdHJpeC5jb20+CgpkaWZmIC0tZ2l0IGEvY29uc29s ZS5jIGIvY29uc29sZS5jCmluZGV4IGVkNmE2NTMuLmJmYWQzNjAgMTAwNjQ0 Ci0tLSBhL2NvbnNvbGUuYworKysgYi9jb25zb2xlLmMKQEAgLTg0MSw2ICs4 NDEsMjYgQEAgc3RhdGljIHZvaWQgY29uc29sZV9jbGVhcl94eShUZXh0Q29u c29sZSAqcywgaW50IHgsIGludCB5KQogICAgIHVwZGF0ZV94eShzLCB4LCB5 KTsKIH0KIAorLyogc2V0IGN1cnNvciwgY2hlY2tpbmcgYm91bmRzICovCitz dGF0aWMgdm9pZCBzZXRfY3Vyc29yKFRleHRDb25zb2xlICpzLCBpbnQgeCwg aW50IHkpCit7CisgICAgaWYgKHggPCAwKSB7CisgICAgICAgIHggPSAwOwor ICAgIH0KKyAgICBpZiAoeSA8IDApIHsKKyAgICAgICAgeSA9IDA7CisgICAg fQorICAgIGlmICh5ID49IHMtPmhlaWdodCkgeworICAgICAgICB5ID0gcy0+ aGVpZ2h0IC0gMTsKKyAgICB9CisgICAgaWYgKHggPj0gcy0+d2lkdGgpIHsK KyAgICAgICAgeCA9IHMtPndpZHRoIC0gMTsKKyAgICB9CisKKyAgICBzLT54 ID0geDsKKyAgICBzLT55ID0geTsKK30KKwogc3RhdGljIHZvaWQgY29uc29s ZV9wdXRjaGFyKFRleHRDb25zb2xlICpzLCBpbnQgY2gpCiB7CiAgICAgVGV4 dENlbGwgKmM7CkBAIC05MTIsNyArOTMyLDggQEAgc3RhdGljIHZvaWQgY29u c29sZV9wdXRjaGFyKFRleHRDb25zb2xlICpzLCBpbnQgY2gpCiAgICAgICAg ICAgICAgICAgICAgIHMtPmVzY19wYXJhbXNbcy0+bmJfZXNjX3BhcmFtc10g KiAxMCArIGNoIC0gJzAnOwogICAgICAgICAgICAgfQogICAgICAgICB9IGVs c2UgewotICAgICAgICAgICAgcy0+bmJfZXNjX3BhcmFtcysrOworICAgICAg ICAgICAgaWYgKHMtPm5iX2VzY19wYXJhbXMgPCBNQVhfRVNDX1BBUkFNUykK KyAgICAgICAgICAgICAgICBzLT5uYl9lc2NfcGFyYW1zKys7CiAgICAgICAg ICAgICBpZiAoY2ggPT0gJzsnKQogICAgICAgICAgICAgICAgIGJyZWFrOwog I2lmZGVmIERFQlVHX0NPTlNPTEUKQEAgLTkyNiw1OSArOTQ3LDM3IEBAIHN0 YXRpYyB2b2lkIGNvbnNvbGVfcHV0Y2hhcihUZXh0Q29uc29sZSAqcywgaW50 IGNoKQogICAgICAgICAgICAgICAgIGlmIChzLT5lc2NfcGFyYW1zWzBdID09 IDApIHsKICAgICAgICAgICAgICAgICAgICAgcy0+ZXNjX3BhcmFtc1swXSA9 IDE7CiAgICAgICAgICAgICAgICAgfQotICAgICAgICAgICAgICAgIHMtPnkg LT0gcy0+ZXNjX3BhcmFtc1swXTsKLSAgICAgICAgICAgICAgICBpZiAocy0+ eSA8IDApIHsKLSAgICAgICAgICAgICAgICAgICAgcy0+eSA9IDA7Ci0gICAg ICAgICAgICAgICAgfQorICAgICAgICAgICAgICAgIHNldF9jdXJzb3Iocywg cy0+eCwgcy0+eSAtIHMtPmVzY19wYXJhbXNbMF0pOwogICAgICAgICAgICAg ICAgIGJyZWFrOwogICAgICAgICAgICAgY2FzZSAnQic6CiAgICAgICAgICAg ICAgICAgLyogbW92ZSBjdXJzb3IgZG93biAqLwogICAgICAgICAgICAgICAg IGlmIChzLT5lc2NfcGFyYW1zWzBdID09IDApIHsKICAgICAgICAgICAgICAg ICAgICAgcy0+ZXNjX3BhcmFtc1swXSA9IDE7CiAgICAgICAgICAgICAgICAg fQotICAgICAgICAgICAgICAgIHMtPnkgKz0gcy0+ZXNjX3BhcmFtc1swXTsK LSAgICAgICAgICAgICAgICBpZiAocy0+eSA+PSBzLT5oZWlnaHQpIHsKLSAg ICAgICAgICAgICAgICAgICAgcy0+eSA9IHMtPmhlaWdodCAtIDE7Ci0gICAg ICAgICAgICAgICAgfQorICAgICAgICAgICAgICAgIHNldF9jdXJzb3Iocywg cy0+eCwgcy0+eSArIHMtPmVzY19wYXJhbXNbMF0pOwogICAgICAgICAgICAg ICAgIGJyZWFrOwogICAgICAgICAgICAgY2FzZSAnQyc6CiAgICAgICAgICAg ICAgICAgLyogbW92ZSBjdXJzb3IgcmlnaHQgKi8KICAgICAgICAgICAgICAg ICBpZiAocy0+ZXNjX3BhcmFtc1swXSA9PSAwKSB7CiAgICAgICAgICAgICAg ICAgICAgIHMtPmVzY19wYXJhbXNbMF0gPSAxOwogICAgICAgICAgICAgICAg IH0KLSAgICAgICAgICAgICAgICBzLT54ICs9IHMtPmVzY19wYXJhbXNbMF07 Ci0gICAgICAgICAgICAgICAgaWYgKHMtPnggPj0gcy0+d2lkdGgpIHsKLSAg ICAgICAgICAgICAgICAgICAgcy0+eCA9IHMtPndpZHRoIC0gMTsKLSAgICAg ICAgICAgICAgICB9CisgICAgICAgICAgICAgICAgc2V0X2N1cnNvcihzLCBz LT54ICsgcy0+ZXNjX3BhcmFtc1swXSwgcy0+eSk7CiAgICAgICAgICAgICAg ICAgYnJlYWs7CiAgICAgICAgICAgICBjYXNlICdEJzoKICAgICAgICAgICAg ICAgICAvKiBtb3ZlIGN1cnNvciBsZWZ0ICovCiAgICAgICAgICAgICAgICAg aWYgKHMtPmVzY19wYXJhbXNbMF0gPT0gMCkgewogICAgICAgICAgICAgICAg ICAgICBzLT5lc2NfcGFyYW1zWzBdID0gMTsKICAgICAgICAgICAgICAgICB9 Ci0gICAgICAgICAgICAgICAgcy0+eCAtPSBzLT5lc2NfcGFyYW1zWzBdOwot ICAgICAgICAgICAgICAgIGlmIChzLT54IDwgMCkgewotICAgICAgICAgICAg ICAgICAgICBzLT54ID0gMDsKLSAgICAgICAgICAgICAgICB9CisgICAgICAg ICAgICAgICAgc2V0X2N1cnNvcihzLCBzLT54IC0gcy0+ZXNjX3BhcmFtc1sw XSwgcy0+eSk7CiAgICAgICAgICAgICAgICAgYnJlYWs7CiAgICAgICAgICAg ICBjYXNlICdHJzoKICAgICAgICAgICAgICAgICAvKiBtb3ZlIGN1cnNvciB0 byBjb2x1bW4gKi8KLSAgICAgICAgICAgICAgICBzLT54ID0gcy0+ZXNjX3Bh cmFtc1swXSAtIDE7Ci0gICAgICAgICAgICAgICAgaWYgKHMtPnggPCAwKSB7 Ci0gICAgICAgICAgICAgICAgICAgIHMtPnggPSAwOwotICAgICAgICAgICAg ICAgIH0KKyAgICAgICAgICAgICAgICBzZXRfY3Vyc29yKHMsIHMtPmVzY19w YXJhbXNbMF0gLSAxLCBzLT55KTsKICAgICAgICAgICAgICAgICBicmVhazsK ICAgICAgICAgICAgIGNhc2UgJ2YnOgogICAgICAgICAgICAgY2FzZSAnSCc6 CiAgICAgICAgICAgICAgICAgLyogbW92ZSBjdXJzb3IgdG8gcm93LCBjb2x1 bW4gKi8KLSAgICAgICAgICAgICAgICBzLT54ID0gcy0+ZXNjX3BhcmFtc1sx XSAtIDE7Ci0gICAgICAgICAgICAgICAgaWYgKHMtPnggPCAwKSB7Ci0gICAg ICAgICAgICAgICAgICAgIHMtPnggPSAwOwotICAgICAgICAgICAgICAgIH0K LSAgICAgICAgICAgICAgICBzLT55ID0gcy0+ZXNjX3BhcmFtc1swXSAtIDE7 Ci0gICAgICAgICAgICAgICAgaWYgKHMtPnkgPCAwKSB7Ci0gICAgICAgICAg ICAgICAgICAgIHMtPnkgPSAwOwotICAgICAgICAgICAgICAgIH0KKyAgICAg ICAgICAgICAgICBzZXRfY3Vyc29yKHMsIHMtPmVzY19wYXJhbXNbMV0gLSAx LCBzLT5lc2NfcGFyYW1zWzBdIC0gMSk7CiAgICAgICAgICAgICAgICAgYnJl YWs7CiAgICAgICAgICAgICBjYXNlICdKJzoKICAgICAgICAgICAgICAgICBz d2l0Y2ggKHMtPmVzY19wYXJhbXNbMF0pIHsK --=separator Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users --=separator-- From xen-users-bounces@lists.xen.org Wed Sep 05 11:16:53 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Wed, 05 Sep 2012 11:16:53 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1T9Das-0005C0-47; Wed, 05 Sep 2012 11:16:26 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1T9DVc-0004hj-Je for xen-users@lists.xen.org; Wed, 05 Sep 2012 11:11:00 +0000 Received: from [85.158.143.99:60864] by server-1.bemta-4.messagelabs.com id 10/C3-12504-24337405; Wed, 05 Sep 2012 11:10:58 +0000 X-Env-Sender: iwj@xenbits.xen.org X-Msg-Ref: server-11.tower-216.messagelabs.com!1346843448!21117190!1 X-Originating-IP: [50.57.168.107] X-SpamReason: No, hits=0.5 required=7.0 tests=BODY_RANDOM_LONG X-StarScan-Received: X-StarScan-Version: 6.6.1.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 19330 invoked from network); 5 Sep 2012 11:10:50 -0000 Received: from mail.xen.org (HELO mail.xen.org) (50.57.168.107) by server-11.tower-216.messagelabs.com with AES256-SHA encrypted SMTP; 5 Sep 2012 11:10:50 -0000 Received: from xenbits.xen.org ([50.57.170.242]) by mail.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1T9DVJ-0001Az-MN; Wed, 05 Sep 2012 11:10:41 +0000 Received: from iwj by xenbits.xen.org with local (Exim 4.72) (envelope-from ) id 1T9DVJ-0005Jh-0F; Wed, 05 Sep 2012 11:10:41 +0000 Date: Wed, 05 Sep 2012 11:10:41 +0000 Message-Id: Content-Type: multipart/mixed; boundary="=separator"; charset="utf-8" Content-Transfer-Encoding: binary MIME-Version: 1.0 X-Mailer: MIME-tools 5.428 (Entity 5.428) To: xen-announce@lists.xen.org, xen-devel@lists.xen.org, xen-users@lists.xen.org, oss-security@lists.openwall.com From: Xen.org security team X-Mailman-Approved-At: Wed, 05 Sep 2012 11:16:25 +0000 Cc: "Xen.org security team" Subject: [Xen-users] Xen Security Advisory 15 (CVE-2012-3497) - multiple TMEM hypercall vulnerabilities X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org --=separator Content-Type: text/plain; charset="utf-8" Content-Disposition: inline Content-Transfer-Encoding: 7bit -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Xen Security Advisory CVE-2012-3497 / XSA-15 version 2 multiple TMEM hypercall vulnerabilities UPDATES IN VERSION 2 ==================== Public release. Credit Matthew Daley. ISSUE DESCRIPTION ================= Several sub-operations of the Transcendent Memory (TMEM) hypercall either do not correctly validate their inputs, do not correctly validate the privilege of the calling guest, or have other security-relevant bugs. A full list of the vulnerabilities in the TMEM system is not available at present. IMPACT ====== An unprivileged guest can overwrite hypervisor owned memory with the content of their choosing allowing them to escalate their privilege to that of the host. In addition an unprivileged guest can also crash the hypervisor, leading to a Denial of Service attack. VULNERABLE SYSTEMS ================== ONLY installations where "tmem" is specified on the hypervisor command line are vulnerable. Most Xen installations do not do so. All versions of Xen from 4.0 onward which have TMEM enabled and are running guests with untrusted administrators are vulnerable. Although we consider it unlikely, we have not been able to rule out the possibility that an malicious unprivileged user could exploit these issues via a trusted TMEM-aware kernel. Therefore all administrators are advised to disable TMEM even if all guest kernels are controlled and trusted. MITIGATION ========== Only systems which have TMEM enabled at boot time are affected by this issue. By default TMEM is disabled unless it is explicitly enabled via the hypervisor command line option "tmem". TMEM has been described by its maintainers as a technology preview, and is therefore not supported by them for use in production systems. Pending a full security audit of the code, the Xen.org security team recommends that Xen users do not enable TMEM. RESOLUTION ========== Work is ongoing, by the community maintainers for TMEM, to patch the specific bugs as they are found. This includes both the multiple vulnerabilities initially reported to the Xen.org security team, and multiple further vulnerabilities which have been discovered since then during our ad-hoc code inspection. At the time of writing, a complete set of fixes even for known issues is not available. PROCESS FOR TMEM VULNERABILITIES ================================ Until TMEM has gained production maturity, the Xen.org security team intends (subject of course to the permission of anyone disclosing to us) to handle these and future TMEM vulnerabilities in public, as if they were normal non-security-related bugs. We therefore intend that currently-known vulnerabilities will be publicly disclosed on the xen-devel mailing list, as normal bug reports, at the expiry of the XSA-15 embargo. In the meantime the list below may be helpful. Xen.org security team will ensure, on expiry of the embargo, that the documentation reflects TMEM's technology preview status. CREDIT ====== Thanks to Matthew Daley for finding these vulnerabilities (and that in XSA-12) and notifying the Xen.org security team. LIST OF KNOWN VULNERABILITIES ============================= **NOTE** that this is unlikely to be a complete list of problems. **NOTE** that after publication of this advisory, after the embargo ends, the advisory will no longer be updated to extend this list of vulnerabilities. See `Process for TMEM vulnerabilities', above. Multiple tmem save-related control ops do not check for NULL clients: TMEMC_SAVE_GET_CLIENT_WEIGHT, TMEMC_SAVE_GET_CLIENT_CAP, TMEMC_SAVE_GET_CLIENT_FLAGS and TMEMC_SAVE_END do not check that the cli_id used to find the client is valid, and can hence dereference a NULL client. This allows a malicious guest to crash the host (DoS), or, in the case of TMEMC_SAVE_END, memory corruption (DoS or worse). Multiple tmem save-related control ops do not check guest output buffer pointers: The functions tmemc_save_get_next_page, tmemc_save_get_next_inv and the TMEMC_SAVE_GET_POOL_UUID subop do not check incoming guest output buffer pointers, and do not use ie. copy_to_guest. A malicious guest can crash the host or cause memory corruption (DoS / code execution). Multiple tmem ops do not check for negative pool IDs: The functions tmemc_save_get_next_page, tmemc_restore_put_page and tmemc_restore_flush_page do not check for negative pool IDs, allowing (at least) memory corruption. do_tmem_destroy_pool does not check for invalid pool IDs: The function do_tmem_destroy_pool does not check for invalid pool IDs, allowing a malicious guest to crash the host or corrupt host memory (DoS / code execution). do_tmem_control's privilege check is commented out: This allows any guest access to control stack operations (many of which themselves do not have adequate argument checking). tmh_copy_from_client and tmh_copy_to_client have an integer overflow vulnerability: This can corrupt host memory. do_tmem_get()'s bad_copy error path leaves a spinlock held: The next operation on the same object will hang the CPU. This is a host DoS. do_tmem_op has at least one error path with broken locking checks: This is a host DoS or worse. -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.10 (GNU/Linux) iQEcBAEBAgAGBQJQRyVDAAoJEIP+FMlX6CvZZSEH/11RvLycH5Qm0rkmWb16iuRU s9xmGDxGr6LDGLLYenp7RDc6FU7xjFxNeMhziIWckic2f0V1UtEqxiTHViEeOsOu AQfiwrUaaSf+fwcDqt07bb6gTynxyqS+faLKpk4bq89tKK1318JlxWN2gRtEW5g9 KEo7Bt/O0hYuIJBlBWnH48OHPzGSrwVaw51NLt0oPqiWp4w3ObLRhVttKB7VWJlw OQR9hSStVWhKR68VUBd/LpTZTkX/Hn5qwhX6ltgQ10RW1n4cF2pvebiKu6CtePCl JVBJgn/4ZmaT1joJ8SpX/BONnLt0KHNrublB6vO++1m+7+lBA5qXL38gg4jl48E= =yP/R -----END PGP SIGNATURE----- --=separator Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users --=separator-- From xen-users-bounces@lists.xen.org Wed Sep 05 11:16:54 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Wed, 05 Sep 2012 11:16:54 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1T9Das-0005CB-Qi; Wed, 05 Sep 2012 11:16:26 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1T9DXQ-0004qz-AR for xen-users@lists.xen.org; Wed, 05 Sep 2012 11:12:52 +0000 Received: from [85.158.139.83:19732] by server-6.bemta-5.messagelabs.com id B1/42-21336-2B337405; Wed, 05 Sep 2012 11:12:50 +0000 X-Env-Sender: iwj@xenbits.xen.org X-Msg-Ref: server-11.tower-182.messagelabs.com!1346843568!21461727!1 X-Originating-IP: [50.57.168.107] X-SpamReason: No, hits=0.0 required=7.0 tests= X-StarScan-Received: X-StarScan-Version: 6.6.1.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 22577 invoked from network); 5 Sep 2012 11:12:49 -0000 Received: from mail.xen.org (HELO mail.xen.org) (50.57.168.107) by server-11.tower-182.messagelabs.com with AES256-SHA encrypted SMTP; 5 Sep 2012 11:12:49 -0000 Received: from xenbits.xen.org ([50.57.170.242]) by mail.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1T9DXH-0001Cf-UU; Wed, 05 Sep 2012 11:12:43 +0000 Received: from iwj by xenbits.xen.org with local (Exim 4.72) (envelope-from ) id 1T9DXH-0005Qg-SS; Wed, 05 Sep 2012 11:12:43 +0000 Date: Wed, 05 Sep 2012 11:12:43 +0000 Message-Id: Content-Type: multipart/mixed; boundary="=separator"; charset="utf-8" Content-Transfer-Encoding: binary MIME-Version: 1.0 X-Mailer: MIME-tools 5.428 (Entity 5.428) To: xen-announce@lists.xen.org, xen-devel@lists.xen.org, xen-users@lists.xen.org, oss-security@lists.openwall.com From: Xen.org security team X-Mailman-Approved-At: Wed, 05 Sep 2012 11:16:25 +0000 Cc: "Xen.org security team" Subject: [Xen-users] Xen Security Advisory 16 (CVE-2012-3498) - PHYSDEVOP_map_pirq index vulnerability X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org --=separator Content-Type: text/plain; charset="utf-8" Content-Disposition: inline Content-Transfer-Encoding: 7bit -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Xen Security Advisory CVE-2012-3498 / XSA-16 version 3 PHYSDEVOP_map_pirq index vulnerability UPDATES IN VERSION 3 ==================== Public release. Credit Matthew Daley. ISSUE DESCRIPTION ================= PHYSDEVOP_map_pirq with MAP_PIRQ_TYPE_GSI does not range check map->index. IMPACT ====== A malicious HVM guest kernel can crash the host. It might also be able to read hypervisor or guest memory. VULNERABLE SYSTEMS ================== All Xen systems running HVM guests. PV guests are not vulnerable. The vulnerability dates back to Xen 4.1. Xen 4.0 is not vulnerable. 4.1, the 4.2 RCs, and xen-unstable.hg are vulnerable. MITIGATION ========== This issue can be mitigated by ensuring that the guest kernel is trustworthy, or by running only PV guests. RESOLUTION ========== Applying the appropriate attached patch will resolve the issue. CREDIT ====== Thanks to Matthew Daley for finding this vulnerability (and that in XSA-12) and notifying the Xen.org security team. PATCH INFORMATION ================= The attached patches resolve this issue Xen unstable xsa16-unstable.patch Xen 4.1, 4.1.x xsa16-xen-4.1.patch $ sha256sum xsa16-*.patch f8db42898620112c8e77bf116645d650b3671d4ccc49adcad09c7b4591d55cab xsa16-unstable.patch 4b76d554b23977443209e45d3a2404d63695eb3020ff87a8e16e5e25cbddff31 xsa16-xen-4.1.patch -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.10 (GNU/Linux) iQEcBAEBAgAGBQJQRyVFAAoJEIP+FMlX6CvZkqkH/2k5sdGWVThawtjkpTfx8L3T d0QnlJYstbvGxNkRvaafj32jApGkHWwr/Rd4w1MPxXXJOU6bmXjKKXAugVj0wl5Z PZeVtek46S3sSNCavLH7kL1SVZoCikEH2+kv9edGhKOXxO3C+8FkM+HvoZU7tQco ppUhEfINP9WidXlWSEmK2nhZdvrLW7KeqHTQmwx6AC1mUE0YdaF2oTZRPyOgRwIx quYJ3hLiQiQD3eUV56iqNO19/D4jpPibBG33yurdzahRivuLTb7XD+QfKfEDZ1WC SVqIRJha84QBjHLTtPIgmjyF8ysUXnPLol1NTxpIBFX98OCw9Ery0Zic/poFjcc= =7hrh -----END PGP SIGNATURE----- --=separator Content-Type: application/octet-stream; name="xsa16-unstable.patch" Content-Disposition: attachment; filename="xsa16-unstable.patch" Content-Transfer-Encoding: base64 eDg2L3B2aHZtOiBwcm9wZXJseSByYW5nZS1jaGVjayBQSFlTREVWT1BfbWFw X3BpcnEvTUFQX1BJUlFfVFlQRV9HU0kKClRoaXMgaXMgYmVpbmcgdXNlZCBh cyBhIGFycmF5IGluZGV4LCBhbmQgaGVuY2UgbXVzdCBiZSB2YWxpZGF0ZWQg YmVmb3JlCnVzZS4KClRoaXMgaXMgWFNBLTE2IC8gQ1ZFLTIwMTItMzQ5OC4K ClNpZ25lZC1vZmYtYnk6IEphbiBCZXVsaWNoIDxqYmV1bGljaEBzdXNlLmNv bT4KCi0tLSBhL3hlbi9hcmNoL3g4Ni9waHlzZGV2LmMKKysrIGIveGVuL2Fy Y2gveDg2L3BoeXNkZXYuYwpAQCAtNDMsMTEgKzQzLDE4IEBAIHN0YXRpYyBp bnQgcGh5c2Rldl9odm1fbWFwX3BpcnEoCiAgICAgICAgIHN0cnVjdCBodm1f Z2lycV9kcGNpX21hcHBpbmcgKmdpcnE7CiAgICAgICAgIHVpbnQzMl90IG1h Y2hpbmVfZ3NpID0gMDsKIAorICAgICAgICBpZiAoICppbmRleCA8IDAgfHwg KmluZGV4ID49IE5SX0hWTV9JUlFTICkKKyAgICAgICAgeworICAgICAgICAg ICAgcmV0ID0gLUVJTlZBTDsKKyAgICAgICAgICAgIGJyZWFrOworICAgICAg ICB9CisKICAgICAgICAgLyogZmluZCB0aGUgbWFjaGluZSBnc2kgY29ycmVz cG9uZGluZyB0byB0aGUKICAgICAgICAgICogZW11bGF0ZWQgZ3NpICovCiAg ICAgICAgIGh2bV9pcnFfZHBjaSA9IGRvbWFpbl9nZXRfaXJxX2RwY2koZCk7 CiAgICAgICAgIGlmICggaHZtX2lycV9kcGNpICkKICAgICAgICAgeworICAg ICAgICAgICAgQlVJTERfQlVHX09OKEFSUkFZX1NJWkUoaHZtX2lycV9kcGNp LT5naXJxKSA8IE5SX0hWTV9JUlFTKTsKICAgICAgICAgICAgIGxpc3RfZm9y X2VhY2hfZW50cnkgKCBnaXJxLAogICAgICAgICAgICAgICAgICAgICAgICAg ICAgICAgICAgICZodm1faXJxX2RwY2ktPmdpcnFbKmluZGV4XSwKICAgICAg ICAgICAgICAgICAgICAgICAgICAgICAgICAgICBsaXN0ICkK --=separator Content-Type: application/octet-stream; name="xsa16-xen-4.1.patch" Content-Disposition: attachment; filename="xsa16-xen-4.1.patch" Content-Transfer-Encoding: base64 eDg2L3B2aHZtOiBwcm9wZXJseSByYW5nZS1jaGVjayBQSFlTREVWT1BfbWFw X3BpcnEvTUFQX1BJUlFfVFlQRV9HU0kKClRoaXMgaXMgYmVpbmcgdXNlZCBh cyBhIGFycmF5IGluZGV4LCBhbmQgaGVuY2UgbXVzdCBiZSB2YWxpZGF0ZWQg YmVmb3JlCnVzZS4KClRoaXMgaXMgWFNBLTE2IC8gQ1ZFLTIwMTItMzQ5OC4K ClNpZ25lZC1vZmYtYnk6IEphbiBCZXVsaWNoIDxqYmV1bGljaEBzdXNlLmNv bT4KCmRpZmYgLXIgMTIyNWFmZjA1ZGQyIHhlbi9hcmNoL3g4Ni9waHlzZGV2 LmMKLS0tIGEveGVuL2FyY2gveDg2L3BoeXNkZXYuYwlUaHUgQXVnIDA5IDE2 OjQ4OjA3IDIwMTIgKzAxMDAKKysrIGIveGVuL2FyY2gveDg2L3BoeXNkZXYu YwlUaHUgQXVnIDE2IDEzOjAzOjM2IDIwMTIgKzAxMDAKQEAgLTQwLDExICs0 MCwxOCBAQCBzdGF0aWMgaW50IHBoeXNkZXZfaHZtX21hcF9waXJxKAogICAg ICAgICBzdHJ1Y3QgaHZtX2dpcnFfZHBjaV9tYXBwaW5nICpnaXJxOwogICAg ICAgICB1aW50MzJfdCBtYWNoaW5lX2dzaSA9IDA7CiAKKyAgICAgICAgaWYg KCBtYXAtPmluZGV4IDwgMCB8fCBtYXAtPmluZGV4ID49IE5SX0hWTV9JUlFT ICkKKyAgICAgICAgeworICAgICAgICAgICAgcmV0ID0gLUVJTlZBTDsKKyAg ICAgICAgICAgIGJyZWFrOworICAgICAgICB9CisKICAgICAgICAgLyogZmlu ZCB0aGUgbWFjaGluZSBnc2kgY29ycmVzcG9uZGluZyB0byB0aGUKICAgICAg ICAgICogZW11bGF0ZWQgZ3NpICovCiAgICAgICAgIGh2bV9pcnFfZHBjaSA9 IGRvbWFpbl9nZXRfaXJxX2RwY2koZCk7CiAgICAgICAgIGlmICggaHZtX2ly cV9kcGNpICkKICAgICAgICAgeworICAgICAgICAgICAgQlVJTERfQlVHX09O KEFSUkFZX1NJWkUoaHZtX2lycV9kcGNpLT5naXJxKSA8IE5SX0hWTV9JUlFT KTsKICAgICAgICAgICAgIGxpc3RfZm9yX2VhY2hfZW50cnkgKCBnaXJxLAog ICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICZodm1faXJxX2Rw Y2ktPmdpcnFbbWFwLT5pbmRleF0sCiAgICAgICAgICAgICAgICAgICAgICAg ICAgICAgICAgICAgbGlzdCApCg== --=separator Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users --=separator-- From xen-users-bounces@lists.xen.org Wed Sep 05 11:16:54 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Wed, 05 Sep 2012 11:16:54 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1T9Das-0005CB-Qi; Wed, 05 Sep 2012 11:16:26 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1T9DXQ-0004qz-AR for xen-users@lists.xen.org; Wed, 05 Sep 2012 11:12:52 +0000 Received: from [85.158.139.83:19732] by server-6.bemta-5.messagelabs.com id B1/42-21336-2B337405; Wed, 05 Sep 2012 11:12:50 +0000 X-Env-Sender: iwj@xenbits.xen.org X-Msg-Ref: server-11.tower-182.messagelabs.com!1346843568!21461727!1 X-Originating-IP: [50.57.168.107] X-SpamReason: No, hits=0.0 required=7.0 tests= X-StarScan-Received: X-StarScan-Version: 6.6.1.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 22577 invoked from network); 5 Sep 2012 11:12:49 -0000 Received: from mail.xen.org (HELO mail.xen.org) (50.57.168.107) by server-11.tower-182.messagelabs.com with AES256-SHA encrypted SMTP; 5 Sep 2012 11:12:49 -0000 Received: from xenbits.xen.org ([50.57.170.242]) by mail.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1T9DXH-0001Cf-UU; Wed, 05 Sep 2012 11:12:43 +0000 Received: from iwj by xenbits.xen.org with local (Exim 4.72) (envelope-from ) id 1T9DXH-0005Qg-SS; Wed, 05 Sep 2012 11:12:43 +0000 Date: Wed, 05 Sep 2012 11:12:43 +0000 Message-Id: Content-Type: multipart/mixed; boundary="=separator"; charset="utf-8" Content-Transfer-Encoding: binary MIME-Version: 1.0 X-Mailer: MIME-tools 5.428 (Entity 5.428) To: xen-announce@lists.xen.org, xen-devel@lists.xen.org, xen-users@lists.xen.org, oss-security@lists.openwall.com From: Xen.org security team X-Mailman-Approved-At: Wed, 05 Sep 2012 11:16:25 +0000 Cc: "Xen.org security team" Subject: [Xen-users] Xen Security Advisory 16 (CVE-2012-3498) - PHYSDEVOP_map_pirq index vulnerability X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org --=separator Content-Type: text/plain; charset="utf-8" Content-Disposition: inline Content-Transfer-Encoding: 7bit -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Xen Security Advisory CVE-2012-3498 / XSA-16 version 3 PHYSDEVOP_map_pirq index vulnerability UPDATES IN VERSION 3 ==================== Public release. Credit Matthew Daley. ISSUE DESCRIPTION ================= PHYSDEVOP_map_pirq with MAP_PIRQ_TYPE_GSI does not range check map->index. IMPACT ====== A malicious HVM guest kernel can crash the host. It might also be able to read hypervisor or guest memory. VULNERABLE SYSTEMS ================== All Xen systems running HVM guests. PV guests are not vulnerable. The vulnerability dates back to Xen 4.1. Xen 4.0 is not vulnerable. 4.1, the 4.2 RCs, and xen-unstable.hg are vulnerable. MITIGATION ========== This issue can be mitigated by ensuring that the guest kernel is trustworthy, or by running only PV guests. RESOLUTION ========== Applying the appropriate attached patch will resolve the issue. CREDIT ====== Thanks to Matthew Daley for finding this vulnerability (and that in XSA-12) and notifying the Xen.org security team. PATCH INFORMATION ================= The attached patches resolve this issue Xen unstable xsa16-unstable.patch Xen 4.1, 4.1.x xsa16-xen-4.1.patch $ sha256sum xsa16-*.patch f8db42898620112c8e77bf116645d650b3671d4ccc49adcad09c7b4591d55cab xsa16-unstable.patch 4b76d554b23977443209e45d3a2404d63695eb3020ff87a8e16e5e25cbddff31 xsa16-xen-4.1.patch -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.10 (GNU/Linux) iQEcBAEBAgAGBQJQRyVFAAoJEIP+FMlX6CvZkqkH/2k5sdGWVThawtjkpTfx8L3T d0QnlJYstbvGxNkRvaafj32jApGkHWwr/Rd4w1MPxXXJOU6bmXjKKXAugVj0wl5Z PZeVtek46S3sSNCavLH7kL1SVZoCikEH2+kv9edGhKOXxO3C+8FkM+HvoZU7tQco ppUhEfINP9WidXlWSEmK2nhZdvrLW7KeqHTQmwx6AC1mUE0YdaF2oTZRPyOgRwIx quYJ3hLiQiQD3eUV56iqNO19/D4jpPibBG33yurdzahRivuLTb7XD+QfKfEDZ1WC SVqIRJha84QBjHLTtPIgmjyF8ysUXnPLol1NTxpIBFX98OCw9Ery0Zic/poFjcc= =7hrh -----END PGP SIGNATURE----- --=separator Content-Type: application/octet-stream; name="xsa16-unstable.patch" Content-Disposition: attachment; filename="xsa16-unstable.patch" Content-Transfer-Encoding: base64 eDg2L3B2aHZtOiBwcm9wZXJseSByYW5nZS1jaGVjayBQSFlTREVWT1BfbWFw X3BpcnEvTUFQX1BJUlFfVFlQRV9HU0kKClRoaXMgaXMgYmVpbmcgdXNlZCBh cyBhIGFycmF5IGluZGV4LCBhbmQgaGVuY2UgbXVzdCBiZSB2YWxpZGF0ZWQg YmVmb3JlCnVzZS4KClRoaXMgaXMgWFNBLTE2IC8gQ1ZFLTIwMTItMzQ5OC4K ClNpZ25lZC1vZmYtYnk6IEphbiBCZXVsaWNoIDxqYmV1bGljaEBzdXNlLmNv bT4KCi0tLSBhL3hlbi9hcmNoL3g4Ni9waHlzZGV2LmMKKysrIGIveGVuL2Fy Y2gveDg2L3BoeXNkZXYuYwpAQCAtNDMsMTEgKzQzLDE4IEBAIHN0YXRpYyBp bnQgcGh5c2Rldl9odm1fbWFwX3BpcnEoCiAgICAgICAgIHN0cnVjdCBodm1f Z2lycV9kcGNpX21hcHBpbmcgKmdpcnE7CiAgICAgICAgIHVpbnQzMl90IG1h Y2hpbmVfZ3NpID0gMDsKIAorICAgICAgICBpZiAoICppbmRleCA8IDAgfHwg KmluZGV4ID49IE5SX0hWTV9JUlFTICkKKyAgICAgICAgeworICAgICAgICAg ICAgcmV0ID0gLUVJTlZBTDsKKyAgICAgICAgICAgIGJyZWFrOworICAgICAg ICB9CisKICAgICAgICAgLyogZmluZCB0aGUgbWFjaGluZSBnc2kgY29ycmVz cG9uZGluZyB0byB0aGUKICAgICAgICAgICogZW11bGF0ZWQgZ3NpICovCiAg ICAgICAgIGh2bV9pcnFfZHBjaSA9IGRvbWFpbl9nZXRfaXJxX2RwY2koZCk7 CiAgICAgICAgIGlmICggaHZtX2lycV9kcGNpICkKICAgICAgICAgeworICAg ICAgICAgICAgQlVJTERfQlVHX09OKEFSUkFZX1NJWkUoaHZtX2lycV9kcGNp LT5naXJxKSA8IE5SX0hWTV9JUlFTKTsKICAgICAgICAgICAgIGxpc3RfZm9y X2VhY2hfZW50cnkgKCBnaXJxLAogICAgICAgICAgICAgICAgICAgICAgICAg ICAgICAgICAgICZodm1faXJxX2RwY2ktPmdpcnFbKmluZGV4XSwKICAgICAg ICAgICAgICAgICAgICAgICAgICAgICAgICAgICBsaXN0ICkK --=separator Content-Type: application/octet-stream; name="xsa16-xen-4.1.patch" Content-Disposition: attachment; filename="xsa16-xen-4.1.patch" Content-Transfer-Encoding: base64 eDg2L3B2aHZtOiBwcm9wZXJseSByYW5nZS1jaGVjayBQSFlTREVWT1BfbWFw X3BpcnEvTUFQX1BJUlFfVFlQRV9HU0kKClRoaXMgaXMgYmVpbmcgdXNlZCBh cyBhIGFycmF5IGluZGV4LCBhbmQgaGVuY2UgbXVzdCBiZSB2YWxpZGF0ZWQg YmVmb3JlCnVzZS4KClRoaXMgaXMgWFNBLTE2IC8gQ1ZFLTIwMTItMzQ5OC4K ClNpZ25lZC1vZmYtYnk6IEphbiBCZXVsaWNoIDxqYmV1bGljaEBzdXNlLmNv bT4KCmRpZmYgLXIgMTIyNWFmZjA1ZGQyIHhlbi9hcmNoL3g4Ni9waHlzZGV2 LmMKLS0tIGEveGVuL2FyY2gveDg2L3BoeXNkZXYuYwlUaHUgQXVnIDA5IDE2 OjQ4OjA3IDIwMTIgKzAxMDAKKysrIGIveGVuL2FyY2gveDg2L3BoeXNkZXYu YwlUaHUgQXVnIDE2IDEzOjAzOjM2IDIwMTIgKzAxMDAKQEAgLTQwLDExICs0 MCwxOCBAQCBzdGF0aWMgaW50IHBoeXNkZXZfaHZtX21hcF9waXJxKAogICAg ICAgICBzdHJ1Y3QgaHZtX2dpcnFfZHBjaV9tYXBwaW5nICpnaXJxOwogICAg ICAgICB1aW50MzJfdCBtYWNoaW5lX2dzaSA9IDA7CiAKKyAgICAgICAgaWYg KCBtYXAtPmluZGV4IDwgMCB8fCBtYXAtPmluZGV4ID49IE5SX0hWTV9JUlFT ICkKKyAgICAgICAgeworICAgICAgICAgICAgcmV0ID0gLUVJTlZBTDsKKyAg ICAgICAgICAgIGJyZWFrOworICAgICAgICB9CisKICAgICAgICAgLyogZmlu ZCB0aGUgbWFjaGluZSBnc2kgY29ycmVzcG9uZGluZyB0byB0aGUKICAgICAg ICAgICogZW11bGF0ZWQgZ3NpICovCiAgICAgICAgIGh2bV9pcnFfZHBjaSA9 IGRvbWFpbl9nZXRfaXJxX2RwY2koZCk7CiAgICAgICAgIGlmICggaHZtX2ly cV9kcGNpICkKICAgICAgICAgeworICAgICAgICAgICAgQlVJTERfQlVHX09O KEFSUkFZX1NJWkUoaHZtX2lycV9kcGNpLT5naXJxKSA8IE5SX0hWTV9JUlFT KTsKICAgICAgICAgICAgIGxpc3RfZm9yX2VhY2hfZW50cnkgKCBnaXJxLAog ICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICZodm1faXJxX2Rw Y2ktPmdpcnFbbWFwLT5pbmRleF0sCiAgICAgICAgICAgICAgICAgICAgICAg ICAgICAgICAgICAgbGlzdCApCg== --=separator Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users --=separator-- From xen-users-bounces@lists.xen.org Wed Sep 05 11:16:54 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Wed, 05 Sep 2012 11:16:54 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1T9Dau-0005CZ-7N; Wed, 05 Sep 2012 11:16:28 +0000 Received: from mail27.messagelabs.com ([193.109.254.147]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1T9DYt-000551-Ug; Wed, 05 Sep 2012 11:14:24 +0000 X-Env-Sender: iwj@xenbits.xen.org X-Msg-Ref: server-15.tower-27.messagelabs.com!1346843656!2698197!1 X-Originating-IP: [50.57.168.107] X-SpamReason: No, hits=0.0 required=7.0 tests= X-StarScan-Received: X-StarScan-Version: 6.6.1.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 31598 invoked from network); 5 Sep 2012 11:14:17 -0000 Received: from mail.xen.org (HELO mail.xen.org) (50.57.168.107) by server-15.tower-27.messagelabs.com with AES256-SHA encrypted SMTP; 5 Sep 2012 11:14:17 -0000 Received: from xenbits.xen.org ([50.57.170.242]) by mail.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1T9DYh-0001EZ-BG; Wed, 05 Sep 2012 11:14:11 +0000 Received: from iwj by xenbits.xen.org with local (Exim 4.72) (envelope-from ) id 1T9DYh-0005Tm-0t; Wed, 05 Sep 2012 11:14:11 +0000 Date: Wed, 05 Sep 2012 11:14:11 +0000 Message-Id: Content-Type: multipart/mixed; boundary="=separator"; charset="utf-8" Content-Transfer-Encoding: binary MIME-Version: 1.0 X-Mailer: MIME-tools 5.428 (Entity 5.428) To: xen-announce@lists.xen.org, xen-devel@lists.xen.org, xen-users@lists.xen.org, oss-security@lists.openwall.com From: Xen.org security team X-Mailman-Approved-At: Wed, 05 Sep 2012 11:16:25 +0000 Cc: "Xen.org security team" Subject: [Xen-users] Xen Security Advisory 18 (CVE-2012-3516) - grant table entry swaps have inadequate bounds checking X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org --=separator Content-Type: text/plain; charset="utf-8" Content-Disposition: inline Content-Transfer-Encoding: 7bit -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Xen Security Advisory CVE-2012-3516 / XSA-18 version 2 grant table entry swaps have inadequate bounds checking UPDATES IN VERSION 2 ==================== Public release. ISSUE DESCRIPTION ================= The grant table hypercall's GNTTABOP_swap_grant_ref sub-operation does not perform adequate checks on the input grant references. IMPACT ====== A malicious guest kernel or administrator can crash the host. It may be possible for an attacker to swap a valid grant reference, which they control, with an invalid one allowing them to write abitrary values to hypervisor memory. This could potentially lead to a privilege escalation. VULNERABLE SYSTEMS ================== Xen-unstable, including Xen 4.2 release candidates are vulnerable to this issue. Xen 4.1 and earlier do not include this hypercall and are therefore not vulnerable. MITIGATION ========== The only mitigation is not to run guests which have untrusted administrators. RESOLUTION ========== Applying the attached patch will resolve the issue. PATCH INFORMATION ================= The attached patch resolves this issue Xen unstable xsa18-unstable.patch $ sha256sum xsa18-unstable.patch ad354a1964fc52b0e48d405514156935cc8dfcb5bdaee307e3e74afcc0ca8914 xsa18-unstable.patch -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.10 (GNU/Linux) iQEcBAEBAgAGBQJQRzP3AAoJEIP+FMlX6CvZ350H/jfmrx6a1pNYF3KYtVVIXu1y ZERi/qxji162XGvB+7gdq+IdhLYAeWXRFF309U1FwcRxaQJPRAT024q6Hs+ITr9i L7OnSP9s+UHT4251X3UlOnEfQyKF6NKJIYbamQbfVIvVPdUtNLj4SKYqxlvjyyc3 DpqiARD5f9+i7OkcojvhXszlbMgbpSQ8TYCW5De0dTkZgKQYq2hRuYf/1hmZ1lJt vFEkTCFxO7uxoH6gulyuEjszDYFAUmE3xdxKbT11mIkwnS1wfgp4Ob5H0ioSDNJo oOxqt4KsuNXHDW/B8QlxnQejKBL0INtmOjh7GMox4bvxg4gP57ZlDweC2lkR37c= =dD8C -----END PGP SIGNATURE----- --=separator Content-Type: application/octet-stream; name="xsa18-unstable.patch" Content-Disposition: attachment; filename="xsa18-unstable.patch" Content-Transfer-Encoding: base64 eGVuL2dudHRhYjogVmFsaWRhdGUgaW5wdXQgdG8gR05UVEFCT1Bfc3dhcF9n cmFudF9yZWYKCnhlbi11bnN0YWJsZSBjL3MgMjQ1NDg6ZDExNTg0NGViZmJi IGludHJvZHVjZXMgYSBuZXcgR05UVEFCT1AgdG8gc3dhcApncmFudCByZWZz LiAgSG93ZXZlciwgaXQgZmFpbHMgdG8gdmFsaWRhdGUgdGhlIHR3byByZWZz IHBhc3NlZCBmcm9tCnRoZSBndWVzdC4KClRoZSByZXN1bHQgaXMgdGhhdCBw YXNzaW5nIG91dC1vZi1yYW5nZSByZWZzIGNhbiBjYXVzZSBYZW4gdG8gcmVh ZApwYXN0IHRoZSBlbmQgb2YgdGhlIGdyYW50X3RhYmxlLT5hY3RpdmVbXSBh cnJheSwgYW5kIGRlZmVyZW5jZQp3aGF0ZXZlciBpdCBmaW5kcy4gIFR5cGlj YWxseSwgdGhpcyByZXN1bHRzIGluIFhlbiB0cnlpbmcgdG8gZGVmZXJlbmNl CmEgbG93IHBvaW50ZXIgYW5kIGZhaWwgd2l0aCBhIHBhZ2UtZmF1bHQuCgpB cyB0aGlzIGh5cGVyY2FsbCBjYW4gYmUgaXNzdWVkIGJ5IGFuIHVucHJpdmls ZWdlZCBndWVzdCwgdGhpcyBpcyBhCkRlbmlhbCBvZiBTZXJ2aWNlIGFnYWlu c3QgWGVuLgoKU2lnbmVkLW9mZi1ieTogQW5kcmV3IENvb3BlciA8YW5kcmV3 LmNvb3BlcjNAY2l0cml4LmNvbT4KQWNrZWQtYnk6IFBhdWwgRHVycmFudCA8 cGF1bC5kdXJyYW50QGNpdHJpeC5jb20+CgpkaWZmIC0tZ2l0IGEveGVuL2Nv bW1vbi9ncmFudF90YWJsZS5jIGIveGVuL2NvbW1vbi9ncmFudF90YWJsZS5j CmluZGV4IDk5NjFlODMuLjMyZGUyOTUgMTAwNjQ0Ci0tLSBhL3hlbi9jb21t b24vZ3JhbnRfdGFibGUuYworKysgYi94ZW4vY29tbW9uL2dyYW50X3RhYmxl LmMKQEAgLTIzMjgsNiArMjMyOCwxMiBAQCBfX2dudHRhYl9zd2FwX2dyYW50 X3JlZihncmFudF9yZWZfdCByZWZfYSwgZ3JhbnRfcmVmX3QgcmVmX2IpCiAK ICAgICBzcGluX2xvY2soJmd0LT5sb2NrKTsKIAorICAgIC8qIEJvdW5kcyBj aGVjayBvbiB0aGUgZ3JhbnQgcmVmcyAqLworICAgIGlmICggdW5saWtlbHko cmVmX2EgPj0gbnJfZ3JhbnRfZW50cmllcyhkLT5ncmFudF90YWJsZSkpKQor ICAgICAgICBQSU5fRkFJTChvdXQsIEdOVFNUX2JhZF9nbnRyZWYsICJCYWQg cmVmLWEgKCVkKS5cbiIsIHJlZl9hKTsKKyAgICBpZiAoIHVubGlrZWx5KHJl Zl9iID49IG5yX2dyYW50X2VudHJpZXMoZC0+Z3JhbnRfdGFibGUpKSkKKyAg ICAgICAgUElOX0ZBSUwob3V0LCBHTlRTVF9iYWRfZ250cmVmLCAiQmFkIHJl Zi1iICglZCkuXG4iLCByZWZfYik7CisKICAgICBhY3QgPSAmYWN0aXZlX2Vu dHJ5KGd0LCByZWZfYSk7CiAgICAgaWYgKCBhY3QtPnBpbiApCiAgICAgICAg IFBJTl9GQUlMKG91dCwgR05UU1RfZWFnYWluLCAicmVmIGEgJWxkIGJ1c3lc biIsIChsb25nKXJlZl9hKTsK --=separator Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users --=separator-- From xen-users-bounces@lists.xen.org Wed Sep 05 11:16:54 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Wed, 05 Sep 2012 11:16:54 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1T9Dau-0005CZ-7N; Wed, 05 Sep 2012 11:16:28 +0000 Received: from mail27.messagelabs.com ([193.109.254.147]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1T9DYt-000551-Ug; Wed, 05 Sep 2012 11:14:24 +0000 X-Env-Sender: iwj@xenbits.xen.org X-Msg-Ref: server-15.tower-27.messagelabs.com!1346843656!2698197!1 X-Originating-IP: [50.57.168.107] X-SpamReason: No, hits=0.0 required=7.0 tests= X-StarScan-Received: X-StarScan-Version: 6.6.1.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 31598 invoked from network); 5 Sep 2012 11:14:17 -0000 Received: from mail.xen.org (HELO mail.xen.org) (50.57.168.107) by server-15.tower-27.messagelabs.com with AES256-SHA encrypted SMTP; 5 Sep 2012 11:14:17 -0000 Received: from xenbits.xen.org ([50.57.170.242]) by mail.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1T9DYh-0001EZ-BG; Wed, 05 Sep 2012 11:14:11 +0000 Received: from iwj by xenbits.xen.org with local (Exim 4.72) (envelope-from ) id 1T9DYh-0005Tm-0t; Wed, 05 Sep 2012 11:14:11 +0000 Date: Wed, 05 Sep 2012 11:14:11 +0000 Message-Id: Content-Type: multipart/mixed; boundary="=separator"; charset="utf-8" Content-Transfer-Encoding: binary MIME-Version: 1.0 X-Mailer: MIME-tools 5.428 (Entity 5.428) To: xen-announce@lists.xen.org, xen-devel@lists.xen.org, xen-users@lists.xen.org, oss-security@lists.openwall.com From: Xen.org security team X-Mailman-Approved-At: Wed, 05 Sep 2012 11:16:25 +0000 Cc: "Xen.org security team" Subject: [Xen-users] Xen Security Advisory 18 (CVE-2012-3516) - grant table entry swaps have inadequate bounds checking X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org --=separator Content-Type: text/plain; charset="utf-8" Content-Disposition: inline Content-Transfer-Encoding: 7bit -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Xen Security Advisory CVE-2012-3516 / XSA-18 version 2 grant table entry swaps have inadequate bounds checking UPDATES IN VERSION 2 ==================== Public release. ISSUE DESCRIPTION ================= The grant table hypercall's GNTTABOP_swap_grant_ref sub-operation does not perform adequate checks on the input grant references. IMPACT ====== A malicious guest kernel or administrator can crash the host. It may be possible for an attacker to swap a valid grant reference, which they control, with an invalid one allowing them to write abitrary values to hypervisor memory. This could potentially lead to a privilege escalation. VULNERABLE SYSTEMS ================== Xen-unstable, including Xen 4.2 release candidates are vulnerable to this issue. Xen 4.1 and earlier do not include this hypercall and are therefore not vulnerable. MITIGATION ========== The only mitigation is not to run guests which have untrusted administrators. RESOLUTION ========== Applying the attached patch will resolve the issue. PATCH INFORMATION ================= The attached patch resolves this issue Xen unstable xsa18-unstable.patch $ sha256sum xsa18-unstable.patch ad354a1964fc52b0e48d405514156935cc8dfcb5bdaee307e3e74afcc0ca8914 xsa18-unstable.patch -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.10 (GNU/Linux) iQEcBAEBAgAGBQJQRzP3AAoJEIP+FMlX6CvZ350H/jfmrx6a1pNYF3KYtVVIXu1y ZERi/qxji162XGvB+7gdq+IdhLYAeWXRFF309U1FwcRxaQJPRAT024q6Hs+ITr9i L7OnSP9s+UHT4251X3UlOnEfQyKF6NKJIYbamQbfVIvVPdUtNLj4SKYqxlvjyyc3 DpqiARD5f9+i7OkcojvhXszlbMgbpSQ8TYCW5De0dTkZgKQYq2hRuYf/1hmZ1lJt vFEkTCFxO7uxoH6gulyuEjszDYFAUmE3xdxKbT11mIkwnS1wfgp4Ob5H0ioSDNJo oOxqt4KsuNXHDW/B8QlxnQejKBL0INtmOjh7GMox4bvxg4gP57ZlDweC2lkR37c= =dD8C -----END PGP SIGNATURE----- --=separator Content-Type: application/octet-stream; name="xsa18-unstable.patch" Content-Disposition: attachment; filename="xsa18-unstable.patch" Content-Transfer-Encoding: base64 eGVuL2dudHRhYjogVmFsaWRhdGUgaW5wdXQgdG8gR05UVEFCT1Bfc3dhcF9n cmFudF9yZWYKCnhlbi11bnN0YWJsZSBjL3MgMjQ1NDg6ZDExNTg0NGViZmJi IGludHJvZHVjZXMgYSBuZXcgR05UVEFCT1AgdG8gc3dhcApncmFudCByZWZz LiAgSG93ZXZlciwgaXQgZmFpbHMgdG8gdmFsaWRhdGUgdGhlIHR3byByZWZz IHBhc3NlZCBmcm9tCnRoZSBndWVzdC4KClRoZSByZXN1bHQgaXMgdGhhdCBw YXNzaW5nIG91dC1vZi1yYW5nZSByZWZzIGNhbiBjYXVzZSBYZW4gdG8gcmVh ZApwYXN0IHRoZSBlbmQgb2YgdGhlIGdyYW50X3RhYmxlLT5hY3RpdmVbXSBh cnJheSwgYW5kIGRlZmVyZW5jZQp3aGF0ZXZlciBpdCBmaW5kcy4gIFR5cGlj YWxseSwgdGhpcyByZXN1bHRzIGluIFhlbiB0cnlpbmcgdG8gZGVmZXJlbmNl CmEgbG93IHBvaW50ZXIgYW5kIGZhaWwgd2l0aCBhIHBhZ2UtZmF1bHQuCgpB cyB0aGlzIGh5cGVyY2FsbCBjYW4gYmUgaXNzdWVkIGJ5IGFuIHVucHJpdmls ZWdlZCBndWVzdCwgdGhpcyBpcyBhCkRlbmlhbCBvZiBTZXJ2aWNlIGFnYWlu c3QgWGVuLgoKU2lnbmVkLW9mZi1ieTogQW5kcmV3IENvb3BlciA8YW5kcmV3 LmNvb3BlcjNAY2l0cml4LmNvbT4KQWNrZWQtYnk6IFBhdWwgRHVycmFudCA8 cGF1bC5kdXJyYW50QGNpdHJpeC5jb20+CgpkaWZmIC0tZ2l0IGEveGVuL2Nv bW1vbi9ncmFudF90YWJsZS5jIGIveGVuL2NvbW1vbi9ncmFudF90YWJsZS5j CmluZGV4IDk5NjFlODMuLjMyZGUyOTUgMTAwNjQ0Ci0tLSBhL3hlbi9jb21t b24vZ3JhbnRfdGFibGUuYworKysgYi94ZW4vY29tbW9uL2dyYW50X3RhYmxl LmMKQEAgLTIzMjgsNiArMjMyOCwxMiBAQCBfX2dudHRhYl9zd2FwX2dyYW50 X3JlZihncmFudF9yZWZfdCByZWZfYSwgZ3JhbnRfcmVmX3QgcmVmX2IpCiAK ICAgICBzcGluX2xvY2soJmd0LT5sb2NrKTsKIAorICAgIC8qIEJvdW5kcyBj aGVjayBvbiB0aGUgZ3JhbnQgcmVmcyAqLworICAgIGlmICggdW5saWtlbHko cmVmX2EgPj0gbnJfZ3JhbnRfZW50cmllcyhkLT5ncmFudF90YWJsZSkpKQor ICAgICAgICBQSU5fRkFJTChvdXQsIEdOVFNUX2JhZF9nbnRyZWYsICJCYWQg cmVmLWEgKCVkKS5cbiIsIHJlZl9hKTsKKyAgICBpZiAoIHVubGlrZWx5KHJl Zl9iID49IG5yX2dyYW50X2VudHJpZXMoZC0+Z3JhbnRfdGFibGUpKSkKKyAg ICAgICAgUElOX0ZBSUwob3V0LCBHTlRTVF9iYWRfZ250cmVmLCAiQmFkIHJl Zi1iICglZCkuXG4iLCByZWZfYik7CisKICAgICBhY3QgPSAmYWN0aXZlX2Vu dHJ5KGd0LCByZWZfYSk7CiAgICAgaWYgKCBhY3QtPnBpbiApCiAgICAgICAg IFBJTl9GQUlMKG91dCwgR05UU1RfZWFnYWluLCAicmVmIGEgJWxkIGJ1c3lc biIsIChsb25nKXJlZl9hKTsK --=separator Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users --=separator-- From xen-users-bounces@lists.xen.org Wed Sep 05 12:01:09 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Wed, 05 Sep 2012 12:01:09 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1T9EHS-0001oc-KF; Wed, 05 Sep 2012 12:00:26 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1T9EHR-0001oQ-9f for xen-users@lists.xen.org; Wed, 05 Sep 2012 12:00:25 +0000 Received: from [85.158.143.99:59400] by server-2.bemta-4.messagelabs.com id F0/A2-21239-8DE37405; Wed, 05 Sep 2012 12:00:24 +0000 X-Env-Sender: lists+xen@internecto.net X-Msg-Ref: server-14.tower-216.messagelabs.com!1346846422!19038114!1 X-Originating-IP: [176.9.245.29] X-SpamReason: No, hits=0.0 required=7.0 tests= X-StarScan-Received: X-StarScan-Version: 6.6.1.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 6924 invoked from network); 5 Sep 2012 12:00:23 -0000 Received: from polaris.internecto.net (HELO mx1.internecto.net) (176.9.245.29) by server-14.tower-216.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 5 Sep 2012 12:00:23 -0000 Received: from localhost (localhost [127.0.0.1]) by mx1.internecto.net (Postfix) with ESMTP id C3458A0086; Wed, 5 Sep 2012 12:00:22 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at mail.internecto.net Received: from mx1.internecto.net ([127.0.0.1]) by localhost (mail.polaris.internecto.net [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id CE9Ih5+pgS6Z; Wed, 5 Sep 2012 12:00:22 +0000 (UTC) Received: from internecto.net (5ED4FDEB.cm-7-5d.dynamic.ziggo.nl [94.212.253.235]) (using TLSv1 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (Client did not present a certificate) (Authenticated sender: lists@internecto.net) by mx1.internecto.net (Postfix) with ESMTPSA id 44C66A0058; Wed, 5 Sep 2012 12:00:22 +0000 (UTC) Date: Wed, 5 Sep 2012 14:00:20 +0200 From: Mark van Dijk To: Niels Dettenbach Message-ID: <20120905140020.1e3b2b60@internecto.net> In-Reply-To: <1909678.1rKzGqToy9@gongo> References: <1346665360.25864.2.camel@zakaz.uk.xensource.com> <1346743867.10570.2.camel@dagon.hellion.org.uk> <20120904103750.112fb44d@internecto.net> <1909678.1rKzGqToy9@gongo> Organization: Internecto SIS X-Mailer: Claws Mail 3.8.0 (GTK+ 2.24.10; x86_64-pc-linux-gnu) Mime-Version: 1.0 Cc: xen-users@lists.xen.org Subject: Re: [Xen-users] Xen 4.2.0 Release Plan / TODO X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org Quoting Niels Dettenbach's message from 04 sep 2012: >Am Dienstag, 4. September 2012, 10:37:50 schrieb Mark van Dijk: >> (In fact, in my zsh shell env I wrote an xl function that is a >> wrapper to the xl binary. Another thing is that it allows me to do >> 'xl edit VMname' which issues e.g. 'vim /etc/xen/hosts/VMname'. And >> when I issue 'xl create VMname' it actually executes '/usr/sbin/xl >> create /etc/xen/hosts/VMname'. I like convenience; who doesn't? >> ) >hmm, >from my experience in many environments did not are "fixed" pathes or >places for config files as i.e. in your /etc/xen/hosts/ (i.e. many >people hold config files with other stuff in per domain directories >etc.) - makes it hardly or even impossible to provide a generic "edit" >or "create" natively without any other limitations - so it would be >more or less "usual" that users create their own scripts or wrappers >for their own environment or provide external / third party toolsets >for such "typical applications". Yes. The request I made was for 'xl reset', the rest served only as an example. -- Anyway, time for lunch! -Mark van Dijk. ,--------------------------------- -----------------------------' Wed Sep 05 11:56 UTC 2012 Today is Pungenday, the 29th day of Bureaucracy in the YOLD 3178 _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Wed Sep 05 12:01:09 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Wed, 05 Sep 2012 12:01:09 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1T9EHS-0001oc-KF; Wed, 05 Sep 2012 12:00:26 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1T9EHR-0001oQ-9f for xen-users@lists.xen.org; Wed, 05 Sep 2012 12:00:25 +0000 Received: from [85.158.143.99:59400] by server-2.bemta-4.messagelabs.com id F0/A2-21239-8DE37405; Wed, 05 Sep 2012 12:00:24 +0000 X-Env-Sender: lists+xen@internecto.net X-Msg-Ref: server-14.tower-216.messagelabs.com!1346846422!19038114!1 X-Originating-IP: [176.9.245.29] X-SpamReason: No, hits=0.0 required=7.0 tests= X-StarScan-Received: X-StarScan-Version: 6.6.1.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 6924 invoked from network); 5 Sep 2012 12:00:23 -0000 Received: from polaris.internecto.net (HELO mx1.internecto.net) (176.9.245.29) by server-14.tower-216.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 5 Sep 2012 12:00:23 -0000 Received: from localhost (localhost [127.0.0.1]) by mx1.internecto.net (Postfix) with ESMTP id C3458A0086; Wed, 5 Sep 2012 12:00:22 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at mail.internecto.net Received: from mx1.internecto.net ([127.0.0.1]) by localhost (mail.polaris.internecto.net [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id CE9Ih5+pgS6Z; Wed, 5 Sep 2012 12:00:22 +0000 (UTC) Received: from internecto.net (5ED4FDEB.cm-7-5d.dynamic.ziggo.nl [94.212.253.235]) (using TLSv1 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (Client did not present a certificate) (Authenticated sender: lists@internecto.net) by mx1.internecto.net (Postfix) with ESMTPSA id 44C66A0058; Wed, 5 Sep 2012 12:00:22 +0000 (UTC) Date: Wed, 5 Sep 2012 14:00:20 +0200 From: Mark van Dijk To: Niels Dettenbach Message-ID: <20120905140020.1e3b2b60@internecto.net> In-Reply-To: <1909678.1rKzGqToy9@gongo> References: <1346665360.25864.2.camel@zakaz.uk.xensource.com> <1346743867.10570.2.camel@dagon.hellion.org.uk> <20120904103750.112fb44d@internecto.net> <1909678.1rKzGqToy9@gongo> Organization: Internecto SIS X-Mailer: Claws Mail 3.8.0 (GTK+ 2.24.10; x86_64-pc-linux-gnu) Mime-Version: 1.0 Cc: xen-users@lists.xen.org Subject: Re: [Xen-users] Xen 4.2.0 Release Plan / TODO X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org Quoting Niels Dettenbach's message from 04 sep 2012: >Am Dienstag, 4. September 2012, 10:37:50 schrieb Mark van Dijk: >> (In fact, in my zsh shell env I wrote an xl function that is a >> wrapper to the xl binary. Another thing is that it allows me to do >> 'xl edit VMname' which issues e.g. 'vim /etc/xen/hosts/VMname'. And >> when I issue 'xl create VMname' it actually executes '/usr/sbin/xl >> create /etc/xen/hosts/VMname'. I like convenience; who doesn't? >> ) >hmm, >from my experience in many environments did not are "fixed" pathes or >places for config files as i.e. in your /etc/xen/hosts/ (i.e. many >people hold config files with other stuff in per domain directories >etc.) - makes it hardly or even impossible to provide a generic "edit" >or "create" natively without any other limitations - so it would be >more or less "usual" that users create their own scripts or wrappers >for their own environment or provide external / third party toolsets >for such "typical applications". Yes. The request I made was for 'xl reset', the rest served only as an example. -- Anyway, time for lunch! -Mark van Dijk. ,--------------------------------- -----------------------------' Wed Sep 05 11:56 UTC 2012 Today is Pungenday, the 29th day of Bureaucracy in the YOLD 3178 _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Wed Sep 05 12:28:54 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Wed, 05 Sep 2012 12:28:54 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1T9EiC-0003OX-Op; Wed, 05 Sep 2012 12:28:04 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1T9EiA-0003ON-Sh for xen-users@lists.xen.org; Wed, 05 Sep 2012 12:28:03 +0000 Received: from [85.158.143.99:23661] by server-2.bemta-4.messagelabs.com id 25/B5-21239-25547405; Wed, 05 Sep 2012 12:28:02 +0000 X-Env-Sender: agwells0714@gmail.com X-Msg-Ref: server-10.tower-216.messagelabs.com!1346848080!22274881!1 X-Originating-IP: [74.125.83.45] X-SpamReason: No, hits=0.9 required=7.0 tests=HTML_40_50,HTML_MESSAGE, ML_RADAR_SPEW_LINKS_14,RCVD_BY_IP,spamassassin: X-StarScan-Received: X-StarScan-Version: 6.6.1.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 3445 invoked from network); 5 Sep 2012 12:28:01 -0000 Received: from mail-ee0-f45.google.com (HELO mail-ee0-f45.google.com) (74.125.83.45) by server-10.tower-216.messagelabs.com with RC4-SHA encrypted SMTP; 5 Sep 2012 12:28:01 -0000 Received: by eeke53 with SMTP id e53so228478eek.32 for ; Wed, 05 Sep 2012 05:28:00 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=QFrEnPMhCDngC3qN8v1uBEEyZ/NOGKXnDmSoyutWYIQ=; b=lebuLCvdn+NwuJbvHMFCiImvnmSeyrvYB10+kr0mpCqIg/W29NAYQGtExyXwC+2MhL YTbrmW9TqLGJYfxF3amnw4KxfRsh3WsSYfKxxT6SqKqf3hD0d8/mcRiPiYANa/p0h6wi 1cWkx8KGEJcOcF/1n1k+p93joUCKBEBCNC/vkWFUayDYjdz/ERn+qSnkjirWmGvd2Rqz CIpTRjrNs2b8lr+ExVkx1u9wwiYPf36nFSwwFi7uCoTXCq0mnfMGrlaKcc8UMV/7R52G PImQGk9IZqUgSX7M9Hw9TO0M/zABHrKxwGslq/upjWRTkeRwtOki9PYzX+mUkW0wDuNG XYKA== MIME-Version: 1.0 Received: by 10.14.173.9 with SMTP id u9mr30430778eel.8.1346848080589; Wed, 05 Sep 2012 05:28:00 -0700 (PDT) Received: by 10.14.224.65 with HTTP; Wed, 5 Sep 2012 05:28:00 -0700 (PDT) Received: by 10.14.224.65 with HTTP; Wed, 5 Sep 2012 05:28:00 -0700 (PDT) In-Reply-To: References: Date: Wed, 5 Sep 2012 08:28:00 -0400 Message-ID: From: Andrew Wells To: John Sherwood Cc: xen-users@lists.xen.org Subject: Re: [Xen-users] guest OS High Availability with local storage X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============1851152307990791512==" Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org --===============1851152307990791512== Content-Type: multipart/alternative; boundary=047d7b603d7268f27304c8f38165 --047d7b603d7268f27304c8f38165 Content-Type: text/plain; charset=ISO-8859-1 Actually look into gluster for turning your local storage into shared storage. Works with more than one node and replicates data. On Sep 5, 2012 1:05 AM, "John Sherwood" wrote: > > > On Tue, Sep 4, 2012 at 10:01 PM, John Sherwood wrote: > >> >> >> On Tue, Sep 4, 2012 at 9:44 PM, Fajar A. Nugraha wrote: >> >>> On Wed, Sep 5, 2012 at 10:57 AM, Umarzuki Mochlis >>> wrote: >>> > hi, >>> > >>> > if I were to use Debian Squeeze as dom0 (3 servers) and install Xen >>> > hypervisor 4.0 on all of them, how would I achieve HA with only using >>> > local storage? >>> >>> You can't >>> >>> > has it ever been done before? >>> >>> The easiest way would be to use shared storage and some sort of >>> cluster manager. So if it were me I'd use one node as SAN (e.g. with >>> openindiana + nappit, or whatever iscsi-capable storage appliance of >>> your choice) and the other two as compute nodes. The SAN becomes a >>> single point of failure though (unless you can afford two storage >>> nodes, but that's another story). >>> >>> If you don't have SAN, then to have a "shared" common storage you can >>> use DRBD. AFAIK you can only have two nodes for primary-primary setup >>> though. See https://alteeve.ca/w/Red_Hat_Cluster_Service_3_Tutorial >>> for example (it uses KVM, but the concept should be similar). >>> >>> -- >>> Fajar >>> >>> You can, technically do this with only local storage and stuff like DRBD; >> > > oops, meant to say "without" stuff like DRBD (kind of an important word to > leave out, sorry) > > >> boot your HA host off the network and store everything in RAM, bypassing >> local storage entirely. The drawback there is obvious, but it is a (VERY >> application dependent) option. >> >> Also, with respect to doing it using Xen, Xen HA = Remus, and DRBD is >> going to be your best option for storage if you've ruled out an actual HA >> storage solution (e.g., a SAN). It's discussed in the original Remus >> whitepaper as well (http://nss.cs.ubc.ca/remus/papers/remus-nsdi08.pdf). >> That being said, while you can technically make DRBD work across three >> hosts (mirror A to B, then B to C), I'm not sure if you could make Remus do >> that, and on the subject of Remus, I wouldn't trust it in prod until 4.2 is >> released. >> >> _______________________________________________ >>> Xen-users mailing list >>> Xen-users@lists.xen.org >>> http://lists.xen.org/xen-users >>> >> >> > > _______________________________________________ > Xen-users mailing list > Xen-users@lists.xen.org > http://lists.xen.org/xen-users > --047d7b603d7268f27304c8f38165 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable

Actually look into gluster for turning your local storage into shared st= orage. Works with more than one node and replicates data.

On Sep 5, 2012 1:05 AM, "John Sherwood"= ; <jrs@vt.edu> wrote:


On Tue, Sep 4, 2012 at 10:01 PM, John Sh= erwood <jrs@vt.edu> wrote:


On Tue, Sep 4, 2012 at 9:44 PM, Faj= ar A. Nugraha <list@fajar.net> wrote:
On Wed, Sep 5, 2012 at 10:57 AM, Umarzuki Mochlis <umarzuki@gmail.com> wrote:
> hi,
>
> if I were to use Debian Squeeze as dom0 (3 servers) and install Xen > hypervisor 4.0 on all of them, how would I achieve HA with only using<= br> > local storage?

You can't

> has it ever been done before?

The easiest way would be to use shared storage and some sort of
cluster manager. So if it were me I'd use one node as SAN (e.g. with openindiana + nappit, or whatever iscsi-capable storage appliance of
your choice) and the other two as compute nodes. The SAN becomes a
single point of failure though (unless you can afford two storage
nodes, but that's another story).

If you don't have SAN, then to have a "shared" common storage= you can
use DRBD. AFAIK you can only have two nodes for primary-primary setup
though. See https://alteeve.ca/w/Red_Hat_Cluster_Service_3_Tutor= ial
for example (it uses KVM, but the concept should be similar).

--
Fajar

You can, technically do this with= only local storage and stuff like DRBD;

<= /div>
oops, meant to say "without" stuff like DRBD (kind of a= n important word to leave out, sorry)
=A0
boot your HA host off the network and store everything in RAM, bypassing = local storage entirely. The drawback there is obvious, but it is a (VERY ap= plication dependent) option.

Also, with respect to doing it using Xen, Xen HA =3D Re= mus, and DRBD is going to be your best option for storage if you've rul= ed out an actual HA storage solution (e.g., a SAN). It's discussed in t= he original Remus whitepaper as well (http://nss.cs.ubc.ca/remus/pape= rs/remus-nsdi08.pdf). That being said, while you can technically make D= RBD work across three hosts (mirror A to B, then B to C), I'm not sure = if you could make Remus do that, and on the subject of Remus, I wouldn'= t trust it in prod until 4.2 is released.

_______________________________________________
Xen-users mailing list
Xen-users@list= s.xen.org
http://lists.x= en.org/xen-users



_______________________________________________
Xen-users mailing list
Xen-users@lists.xen.org
http://lists.x= en.org/xen-users
--047d7b603d7268f27304c8f38165-- --===============1851152307990791512== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users --===============1851152307990791512==-- From xen-users-bounces@lists.xen.org Wed Sep 05 12:28:54 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Wed, 05 Sep 2012 12:28:54 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1T9EiC-0003OX-Op; Wed, 05 Sep 2012 12:28:04 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1T9EiA-0003ON-Sh for xen-users@lists.xen.org; Wed, 05 Sep 2012 12:28:03 +0000 Received: from [85.158.143.99:23661] by server-2.bemta-4.messagelabs.com id 25/B5-21239-25547405; Wed, 05 Sep 2012 12:28:02 +0000 X-Env-Sender: agwells0714@gmail.com X-Msg-Ref: server-10.tower-216.messagelabs.com!1346848080!22274881!1 X-Originating-IP: [74.125.83.45] X-SpamReason: No, hits=0.9 required=7.0 tests=HTML_40_50,HTML_MESSAGE, ML_RADAR_SPEW_LINKS_14,RCVD_BY_IP,spamassassin: X-StarScan-Received: X-StarScan-Version: 6.6.1.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 3445 invoked from network); 5 Sep 2012 12:28:01 -0000 Received: from mail-ee0-f45.google.com (HELO mail-ee0-f45.google.com) (74.125.83.45) by server-10.tower-216.messagelabs.com with RC4-SHA encrypted SMTP; 5 Sep 2012 12:28:01 -0000 Received: by eeke53 with SMTP id e53so228478eek.32 for ; Wed, 05 Sep 2012 05:28:00 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=QFrEnPMhCDngC3qN8v1uBEEyZ/NOGKXnDmSoyutWYIQ=; b=lebuLCvdn+NwuJbvHMFCiImvnmSeyrvYB10+kr0mpCqIg/W29NAYQGtExyXwC+2MhL YTbrmW9TqLGJYfxF3amnw4KxfRsh3WsSYfKxxT6SqKqf3hD0d8/mcRiPiYANa/p0h6wi 1cWkx8KGEJcOcF/1n1k+p93joUCKBEBCNC/vkWFUayDYjdz/ERn+qSnkjirWmGvd2Rqz CIpTRjrNs2b8lr+ExVkx1u9wwiYPf36nFSwwFi7uCoTXCq0mnfMGrlaKcc8UMV/7R52G PImQGk9IZqUgSX7M9Hw9TO0M/zABHrKxwGslq/upjWRTkeRwtOki9PYzX+mUkW0wDuNG XYKA== MIME-Version: 1.0 Received: by 10.14.173.9 with SMTP id u9mr30430778eel.8.1346848080589; Wed, 05 Sep 2012 05:28:00 -0700 (PDT) Received: by 10.14.224.65 with HTTP; Wed, 5 Sep 2012 05:28:00 -0700 (PDT) Received: by 10.14.224.65 with HTTP; Wed, 5 Sep 2012 05:28:00 -0700 (PDT) In-Reply-To: References: Date: Wed, 5 Sep 2012 08:28:00 -0400 Message-ID: From: Andrew Wells To: John Sherwood Cc: xen-users@lists.xen.org Subject: Re: [Xen-users] guest OS High Availability with local storage X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============1851152307990791512==" Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org --===============1851152307990791512== Content-Type: multipart/alternative; boundary=047d7b603d7268f27304c8f38165 --047d7b603d7268f27304c8f38165 Content-Type: text/plain; charset=ISO-8859-1 Actually look into gluster for turning your local storage into shared storage. Works with more than one node and replicates data. On Sep 5, 2012 1:05 AM, "John Sherwood" wrote: > > > On Tue, Sep 4, 2012 at 10:01 PM, John Sherwood wrote: > >> >> >> On Tue, Sep 4, 2012 at 9:44 PM, Fajar A. Nugraha wrote: >> >>> On Wed, Sep 5, 2012 at 10:57 AM, Umarzuki Mochlis >>> wrote: >>> > hi, >>> > >>> > if I were to use Debian Squeeze as dom0 (3 servers) and install Xen >>> > hypervisor 4.0 on all of them, how would I achieve HA with only using >>> > local storage? >>> >>> You can't >>> >>> > has it ever been done before? >>> >>> The easiest way would be to use shared storage and some sort of >>> cluster manager. So if it were me I'd use one node as SAN (e.g. with >>> openindiana + nappit, or whatever iscsi-capable storage appliance of >>> your choice) and the other two as compute nodes. The SAN becomes a >>> single point of failure though (unless you can afford two storage >>> nodes, but that's another story). >>> >>> If you don't have SAN, then to have a "shared" common storage you can >>> use DRBD. AFAIK you can only have two nodes for primary-primary setup >>> though. See https://alteeve.ca/w/Red_Hat_Cluster_Service_3_Tutorial >>> for example (it uses KVM, but the concept should be similar). >>> >>> -- >>> Fajar >>> >>> You can, technically do this with only local storage and stuff like DRBD; >> > > oops, meant to say "without" stuff like DRBD (kind of an important word to > leave out, sorry) > > >> boot your HA host off the network and store everything in RAM, bypassing >> local storage entirely. The drawback there is obvious, but it is a (VERY >> application dependent) option. >> >> Also, with respect to doing it using Xen, Xen HA = Remus, and DRBD is >> going to be your best option for storage if you've ruled out an actual HA >> storage solution (e.g., a SAN). It's discussed in the original Remus >> whitepaper as well (http://nss.cs.ubc.ca/remus/papers/remus-nsdi08.pdf). >> That being said, while you can technically make DRBD work across three >> hosts (mirror A to B, then B to C), I'm not sure if you could make Remus do >> that, and on the subject of Remus, I wouldn't trust it in prod until 4.2 is >> released. >> >> _______________________________________________ >>> Xen-users mailing list >>> Xen-users@lists.xen.org >>> http://lists.xen.org/xen-users >>> >> >> > > _______________________________________________ > Xen-users mailing list > Xen-users@lists.xen.org > http://lists.xen.org/xen-users > --047d7b603d7268f27304c8f38165 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable

Actually look into gluster for turning your local storage into shared st= orage. Works with more than one node and replicates data.

On Sep 5, 2012 1:05 AM, "John Sherwood"= ; <jrs@vt.edu> wrote:


On Tue, Sep 4, 2012 at 10:01 PM, John Sh= erwood <jrs@vt.edu> wrote:


On Tue, Sep 4, 2012 at 9:44 PM, Faj= ar A. Nugraha <list@fajar.net> wrote:
On Wed, Sep 5, 2012 at 10:57 AM, Umarzuki Mochlis <umarzuki@gmail.com> wrote:
> hi,
>
> if I were to use Debian Squeeze as dom0 (3 servers) and install Xen > hypervisor 4.0 on all of them, how would I achieve HA with only using<= br> > local storage?

You can't

> has it ever been done before?

The easiest way would be to use shared storage and some sort of
cluster manager. So if it were me I'd use one node as SAN (e.g. with openindiana + nappit, or whatever iscsi-capable storage appliance of
your choice) and the other two as compute nodes. The SAN becomes a
single point of failure though (unless you can afford two storage
nodes, but that's another story).

If you don't have SAN, then to have a "shared" common storage= you can
use DRBD. AFAIK you can only have two nodes for primary-primary setup
though. See https://alteeve.ca/w/Red_Hat_Cluster_Service_3_Tutor= ial
for example (it uses KVM, but the concept should be similar).

--
Fajar

You can, technically do this with= only local storage and stuff like DRBD;

<= /div>
oops, meant to say "without" stuff like DRBD (kind of a= n important word to leave out, sorry)
=A0
boot your HA host off the network and store everything in RAM, bypassing = local storage entirely. The drawback there is obvious, but it is a (VERY ap= plication dependent) option.

Also, with respect to doing it using Xen, Xen HA =3D Re= mus, and DRBD is going to be your best option for storage if you've rul= ed out an actual HA storage solution (e.g., a SAN). It's discussed in t= he original Remus whitepaper as well (http://nss.cs.ubc.ca/remus/pape= rs/remus-nsdi08.pdf). That being said, while you can technically make D= RBD work across three hosts (mirror A to B, then B to C), I'm not sure = if you could make Remus do that, and on the subject of Remus, I wouldn'= t trust it in prod until 4.2 is released.

_______________________________________________
Xen-users mailing list
Xen-users@list= s.xen.org
http://lists.x= en.org/xen-users



_______________________________________________
Xen-users mailing list
Xen-users@lists.xen.org
http://lists.x= en.org/xen-users
--047d7b603d7268f27304c8f38165-- --===============1851152307990791512== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users --===============1851152307990791512==-- From xen-users-bounces@lists.xen.org Wed Sep 05 12:30:14 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Wed, 05 Sep 2012 12:30:14 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1T9Ejg-0003XE-W8; Wed, 05 Sep 2012 12:29:36 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1T9Ejf-0003Wq-Ff for xen-users@lists.xen.org; Wed, 05 Sep 2012 12:29:35 +0000 Received: from [85.158.139.83:46048] by server-12.bemta-5.messagelabs.com id 6D/C8-18300-EA547405; Wed, 05 Sep 2012 12:29:34 +0000 X-Env-Sender: lists+xen@internecto.net X-Msg-Ref: server-14.tower-182.messagelabs.com!1346848173!24434037!1 X-Originating-IP: [176.9.245.29] X-SpamReason: No, hits=0.0 required=7.0 tests= X-StarScan-Received: X-StarScan-Version: 6.6.1.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 5676 invoked from network); 5 Sep 2012 12:29:33 -0000 Received: from polaris.internecto.net (HELO mx1.internecto.net) (176.9.245.29) by server-14.tower-182.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 5 Sep 2012 12:29:33 -0000 Received: from localhost (localhost [127.0.0.1]) by mx1.internecto.net (Postfix) with ESMTP id 1BF8CA0086; Wed, 5 Sep 2012 12:29:33 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at mail.internecto.net Received: from mx1.internecto.net ([127.0.0.1]) by localhost (mail.polaris.internecto.net [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id zUzAdXIgRS3m; Wed, 5 Sep 2012 12:29:32 +0000 (UTC) Received: from internecto.net (5ED4FDEB.cm-7-5d.dynamic.ziggo.nl [94.212.253.235]) (using TLSv1 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (Client did not present a certificate) (Authenticated sender: lists@internecto.net) by mx1.internecto.net (Postfix) with ESMTPSA id 7DD66A0058; Wed, 5 Sep 2012 12:29:32 +0000 (UTC) Date: Wed, 5 Sep 2012 14:29:31 +0200 From: Mark van Dijk To: Ian Campbell Message-ID: <20120905142931.4d8a5109@internecto.net> In-Reply-To: <1346665360.25864.2.camel@zakaz.uk.xensource.com> References: <1346665360.25864.2.camel@zakaz.uk.xensource.com> Organization: Internecto SIS X-Mailer: Claws Mail 3.8.0 (GTK+ 2.24.10; x86_64-pc-linux-gnu) Mime-Version: 1.0 Cc: xen-users@lists.xen.org, xen-devel Subject: Re: [Xen-users] Xen 4.2.0 Release Plan / TODO X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org Quoting Ian Campbell's message from 03 sep 2012: > * [CHECK] More formally deprecate xm/xend. Manpage patches already > in tree. Needs release noting and communication around -rc1 to > remind people to test xl. (DONE) I'm just wondering if it's properly stated somewhere that the 'vfb' line in a VM's config has been replaced with things like: vnc=1 vnclisten="0.0.0.0" vncdisplay="10" This reminds me of a few things I found with regards to VNC just now, while testing the upstream qemu with Xen (both master and version 1.1-stable). 1) While the above syntax, it is also possible to have 'vnclisten="0.0.0.0:10"'. They do the same i.e. open a listening VNC port on port 5910. But imho the term vncdisplay is a bit vague. I realise 'display' refers to a display port. However, I suspect that not everyone understands it just means the tcp listening port. Perhaps it would be better to just use the latter and deprecate/remove the vncdisplay line? 'vnclisten="0.0.0.0:10"' is more common anyway, right? 2) With upstream qemu it seems that the highest possible number for both syntaxes is 99. In other words, it looks like upstream qemu 'suddenly' enforces the VNC ports to be between 5900 and 5999. It's just a matter of taste probably but I really dislike this new restriction. I also dislike using iptables -t nat -j REDIRECT to redirect another port number to the actual (59xx) VNC port. How do you guys feel about this? Oh, just a small disclaimer -- i'm not saying this should all be settled before 4.2 though it's probably wise to at least state somewhere that 'the vfb line is deprecated with xl'. And it's all up to Ian c.s. anyway ;) -- Stay in touch, Mark van Dijk. ,--------------------------------- -----------------------------' Wed Sep 05 12:27 UTC 2012 Today is Pungenday, the 29th day of Bureaucracy in the YOLD 3178 _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Wed Sep 05 12:30:14 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Wed, 05 Sep 2012 12:30:14 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1T9Ejg-0003XE-W8; Wed, 05 Sep 2012 12:29:36 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1T9Ejf-0003Wq-Ff for xen-users@lists.xen.org; Wed, 05 Sep 2012 12:29:35 +0000 Received: from [85.158.139.83:46048] by server-12.bemta-5.messagelabs.com id 6D/C8-18300-EA547405; Wed, 05 Sep 2012 12:29:34 +0000 X-Env-Sender: lists+xen@internecto.net X-Msg-Ref: server-14.tower-182.messagelabs.com!1346848173!24434037!1 X-Originating-IP: [176.9.245.29] X-SpamReason: No, hits=0.0 required=7.0 tests= X-StarScan-Received: X-StarScan-Version: 6.6.1.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 5676 invoked from network); 5 Sep 2012 12:29:33 -0000 Received: from polaris.internecto.net (HELO mx1.internecto.net) (176.9.245.29) by server-14.tower-182.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 5 Sep 2012 12:29:33 -0000 Received: from localhost (localhost [127.0.0.1]) by mx1.internecto.net (Postfix) with ESMTP id 1BF8CA0086; Wed, 5 Sep 2012 12:29:33 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at mail.internecto.net Received: from mx1.internecto.net ([127.0.0.1]) by localhost (mail.polaris.internecto.net [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id zUzAdXIgRS3m; Wed, 5 Sep 2012 12:29:32 +0000 (UTC) Received: from internecto.net (5ED4FDEB.cm-7-5d.dynamic.ziggo.nl [94.212.253.235]) (using TLSv1 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (Client did not present a certificate) (Authenticated sender: lists@internecto.net) by mx1.internecto.net (Postfix) with ESMTPSA id 7DD66A0058; Wed, 5 Sep 2012 12:29:32 +0000 (UTC) Date: Wed, 5 Sep 2012 14:29:31 +0200 From: Mark van Dijk To: Ian Campbell Message-ID: <20120905142931.4d8a5109@internecto.net> In-Reply-To: <1346665360.25864.2.camel@zakaz.uk.xensource.com> References: <1346665360.25864.2.camel@zakaz.uk.xensource.com> Organization: Internecto SIS X-Mailer: Claws Mail 3.8.0 (GTK+ 2.24.10; x86_64-pc-linux-gnu) Mime-Version: 1.0 Cc: xen-users@lists.xen.org, xen-devel Subject: Re: [Xen-users] Xen 4.2.0 Release Plan / TODO X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org Quoting Ian Campbell's message from 03 sep 2012: > * [CHECK] More formally deprecate xm/xend. Manpage patches already > in tree. Needs release noting and communication around -rc1 to > remind people to test xl. (DONE) I'm just wondering if it's properly stated somewhere that the 'vfb' line in a VM's config has been replaced with things like: vnc=1 vnclisten="0.0.0.0" vncdisplay="10" This reminds me of a few things I found with regards to VNC just now, while testing the upstream qemu with Xen (both master and version 1.1-stable). 1) While the above syntax, it is also possible to have 'vnclisten="0.0.0.0:10"'. They do the same i.e. open a listening VNC port on port 5910. But imho the term vncdisplay is a bit vague. I realise 'display' refers to a display port. However, I suspect that not everyone understands it just means the tcp listening port. Perhaps it would be better to just use the latter and deprecate/remove the vncdisplay line? 'vnclisten="0.0.0.0:10"' is more common anyway, right? 2) With upstream qemu it seems that the highest possible number for both syntaxes is 99. In other words, it looks like upstream qemu 'suddenly' enforces the VNC ports to be between 5900 and 5999. It's just a matter of taste probably but I really dislike this new restriction. I also dislike using iptables -t nat -j REDIRECT to redirect another port number to the actual (59xx) VNC port. How do you guys feel about this? Oh, just a small disclaimer -- i'm not saying this should all be settled before 4.2 though it's probably wise to at least state somewhere that 'the vfb line is deprecated with xl'. And it's all up to Ian c.s. anyway ;) -- Stay in touch, Mark van Dijk. ,--------------------------------- -----------------------------' Wed Sep 05 12:27 UTC 2012 Today is Pungenday, the 29th day of Bureaucracy in the YOLD 3178 _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Wed Sep 05 12:47:32 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Wed, 05 Sep 2012 12:47:32 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1T9F0W-00070G-Hl; Wed, 05 Sep 2012 12:47:00 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1T9F0V-000705-Dv for xen-users@lists.xen.org; Wed, 05 Sep 2012 12:46:59 +0000 Received: from [85.158.139.83:54191] by server-1.bemta-5.messagelabs.com id A1/8B-32692-2C947405; Wed, 05 Sep 2012 12:46:58 +0000 X-Env-Sender: umarzuki@gmail.com X-Msg-Ref: server-15.tower-182.messagelabs.com!1346849217!28622026!1 X-Originating-IP: [74.125.82.51] X-SpamReason: No, hits=0.6 required=7.0 tests=MAILTO_TO_SPAM_ADDR, ML_RADAR_SPEW_LINKS_14,RCVD_BY_IP,spamassassin: X-StarScan-Received: X-StarScan-Version: 6.6.1.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 3738 invoked from network); 5 Sep 2012 12:46:58 -0000 Received: from mail-wg0-f51.google.com (HELO mail-wg0-f51.google.com) (74.125.82.51) by server-15.tower-182.messagelabs.com with RC4-SHA encrypted SMTP; 5 Sep 2012 12:46:58 -0000 Received: by wgbed3 with SMTP id ed3so406295wgb.32 for ; Wed, 05 Sep 2012 05:46:57 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=Hzl19iln+gOjaHuphIUduta+mYPLKy/L/xe8nfRQULk=; b=ncA+inWJbj5GPNongno4wyKTSBBmNZRM424FWybWXuNIFeVx7MEfw+YTXvCQYE2O3Y BcytjLGsPjhu09nn1E7jINWdfHlKT4jRNNbmi43oCA+LdKh49o2f8oLehL5FX+wHFUUl MKiiRru8Uxrz0MZHou4yKCackd+OFgU44XdhpdomllZvjZI/vmCBgXGoDm84GRPd99la fE547iJjeKnzlr+v+wV3g5RphBP1IsHx4BIC/wSwPFms9agY5tN2P8beCeJUFNb7GybJ MqX5IZjNOd5ZuwH99OckqIP2x9/v+HVLGPB1jlCuJ3pSvzf+Af7dNE6+8NtfFcTKHXF4 D1Xw== MIME-Version: 1.0 Received: by 10.180.86.3 with SMTP id l3mr38025724wiz.16.1346849217634; Wed, 05 Sep 2012 05:46:57 -0700 (PDT) Received: by 10.194.60.40 with HTTP; Wed, 5 Sep 2012 05:46:57 -0700 (PDT) In-Reply-To: References: Date: Wed, 5 Sep 2012 20:46:57 +0800 Message-ID: From: Umarzuki Mochlis To: Andrew Wells Cc: xen-users@lists.xen.org, John Sherwood Subject: Re: [Xen-users] guest OS High Availability with local storage X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org 2012/9/5 Andrew Wells : > Actually look into gluster for turning your local storage into shared > storage. Works with more than one node and replicates data. thanks for for this useful info, also to everyone who shared their opinion -- Regards, Umarzuki Mochlis http://debmal.my _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Wed Sep 05 12:47:32 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Wed, 05 Sep 2012 12:47:32 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1T9F0W-00070G-Hl; Wed, 05 Sep 2012 12:47:00 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1T9F0V-000705-Dv for xen-users@lists.xen.org; Wed, 05 Sep 2012 12:46:59 +0000 Received: from [85.158.139.83:54191] by server-1.bemta-5.messagelabs.com id A1/8B-32692-2C947405; Wed, 05 Sep 2012 12:46:58 +0000 X-Env-Sender: umarzuki@gmail.com X-Msg-Ref: server-15.tower-182.messagelabs.com!1346849217!28622026!1 X-Originating-IP: [74.125.82.51] X-SpamReason: No, hits=0.6 required=7.0 tests=MAILTO_TO_SPAM_ADDR, ML_RADAR_SPEW_LINKS_14,RCVD_BY_IP,spamassassin: X-StarScan-Received: X-StarScan-Version: 6.6.1.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 3738 invoked from network); 5 Sep 2012 12:46:58 -0000 Received: from mail-wg0-f51.google.com (HELO mail-wg0-f51.google.com) (74.125.82.51) by server-15.tower-182.messagelabs.com with RC4-SHA encrypted SMTP; 5 Sep 2012 12:46:58 -0000 Received: by wgbed3 with SMTP id ed3so406295wgb.32 for ; Wed, 05 Sep 2012 05:46:57 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=Hzl19iln+gOjaHuphIUduta+mYPLKy/L/xe8nfRQULk=; b=ncA+inWJbj5GPNongno4wyKTSBBmNZRM424FWybWXuNIFeVx7MEfw+YTXvCQYE2O3Y BcytjLGsPjhu09nn1E7jINWdfHlKT4jRNNbmi43oCA+LdKh49o2f8oLehL5FX+wHFUUl MKiiRru8Uxrz0MZHou4yKCackd+OFgU44XdhpdomllZvjZI/vmCBgXGoDm84GRPd99la fE547iJjeKnzlr+v+wV3g5RphBP1IsHx4BIC/wSwPFms9agY5tN2P8beCeJUFNb7GybJ MqX5IZjNOd5ZuwH99OckqIP2x9/v+HVLGPB1jlCuJ3pSvzf+Af7dNE6+8NtfFcTKHXF4 D1Xw== MIME-Version: 1.0 Received: by 10.180.86.3 with SMTP id l3mr38025724wiz.16.1346849217634; Wed, 05 Sep 2012 05:46:57 -0700 (PDT) Received: by 10.194.60.40 with HTTP; Wed, 5 Sep 2012 05:46:57 -0700 (PDT) In-Reply-To: References: Date: Wed, 5 Sep 2012 20:46:57 +0800 Message-ID: From: Umarzuki Mochlis To: Andrew Wells Cc: xen-users@lists.xen.org, John Sherwood Subject: Re: [Xen-users] guest OS High Availability with local storage X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org 2012/9/5 Andrew Wells : > Actually look into gluster for turning your local storage into shared > storage. Works with more than one node and replicates data. thanks for for this useful info, also to everyone who shared their opinion -- Regards, Umarzuki Mochlis http://debmal.my _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Wed Sep 05 13:25:09 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Wed, 05 Sep 2012 13:25:09 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1T9Fal-0008Jw-Bs; Wed, 05 Sep 2012 13:24:27 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1T9Faj-0008Jo-P2 for xen-users@lists.xensource.com; Wed, 05 Sep 2012 13:24:25 +0000 Received: from [85.158.143.99:54598] by server-2.bemta-4.messagelabs.com id 90/D2-21239-88257405; Wed, 05 Sep 2012 13:24:24 +0000 X-Env-Sender: mfidelman@meetinghouse.net X-Msg-Ref: server-5.tower-216.messagelabs.com!1346851464!28343615!1 X-Originating-IP: [207.154.13.48] X-SpamReason: No, hits=0.0 required=7.0 tests= X-StarScan-Received: X-StarScan-Version: 6.6.1.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 23709 invoked from network); 5 Sep 2012 13:24:24 -0000 Received: from server1.neighborhoods.net (HELO server1.neighborhoods.net) (207.154.13.48) by server-5.tower-216.messagelabs.com with SMTP; 5 Sep 2012 13:24:24 -0000 Received: from localhost (localhost.localdomain [127.0.0.1]) by server1.neighborhoods.net (Postfix) with ESMTP id 713F2CC0BE for ; Wed, 5 Sep 2012 09:24:23 -0400 (EDT) X-Virus-Scanned: by amavisd-new-2.6.2 (20081215) (Debian) at neighborhoods.net Received: from server1.neighborhoods.net ([127.0.0.1]) by localhost (server1.neighborhoods.net [127.0.0.1]) (amavisd-new, port 10024) with LMTP id Eo0d7dMvqB7S for ; Wed, 5 Sep 2012 09:24:22 -0400 (EDT) Received: from new-host-2.home (pool-71-184-234-147.bstnma.fios.verizon.net [71.184.234.147]) by server1.neighborhoods.net (Postfix) with ESMTPSA id 2DCBCCC0B3 for ; Wed, 5 Sep 2012 09:24:22 -0400 (EDT) Message-ID: <50475285.5090300@meetinghouse.net> Date: Wed, 05 Sep 2012 09:24:21 -0400 From: Miles Fidelman User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.6; rv:15.0) Gecko/20120828 Firefox/15.0 SeaMonkey/2.12 MIME-Version: 1.0 To: "xen-users@lists.xensource.com" Subject: [Xen-users] xen + gluster: recent experiences? X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset="us-ascii"; Format="flowed" Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org Hi Folks, Anybody have any recent experiences building a small cluster with Xen and Gluster? I've been getting ready to move from a 2-node HA cluster (using DRBD) to a 4-node cluster. Sort of been tracking the maturity of Gluster as a replacement for DRBD. Any comments? Thanks, Miles Fidelman -- In theory, there is no difference between theory and practice. In practice, there is. .... Yogi Berra _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Wed Sep 05 13:25:09 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Wed, 05 Sep 2012 13:25:09 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1T9Fal-0008Jw-Bs; Wed, 05 Sep 2012 13:24:27 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1T9Faj-0008Jo-P2 for xen-users@lists.xensource.com; Wed, 05 Sep 2012 13:24:25 +0000 Received: from [85.158.143.99:54598] by server-2.bemta-4.messagelabs.com id 90/D2-21239-88257405; Wed, 05 Sep 2012 13:24:24 +0000 X-Env-Sender: mfidelman@meetinghouse.net X-Msg-Ref: server-5.tower-216.messagelabs.com!1346851464!28343615!1 X-Originating-IP: [207.154.13.48] X-SpamReason: No, hits=0.0 required=7.0 tests= X-StarScan-Received: X-StarScan-Version: 6.6.1.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 23709 invoked from network); 5 Sep 2012 13:24:24 -0000 Received: from server1.neighborhoods.net (HELO server1.neighborhoods.net) (207.154.13.48) by server-5.tower-216.messagelabs.com with SMTP; 5 Sep 2012 13:24:24 -0000 Received: from localhost (localhost.localdomain [127.0.0.1]) by server1.neighborhoods.net (Postfix) with ESMTP id 713F2CC0BE for ; Wed, 5 Sep 2012 09:24:23 -0400 (EDT) X-Virus-Scanned: by amavisd-new-2.6.2 (20081215) (Debian) at neighborhoods.net Received: from server1.neighborhoods.net ([127.0.0.1]) by localhost (server1.neighborhoods.net [127.0.0.1]) (amavisd-new, port 10024) with LMTP id Eo0d7dMvqB7S for ; Wed, 5 Sep 2012 09:24:22 -0400 (EDT) Received: from new-host-2.home (pool-71-184-234-147.bstnma.fios.verizon.net [71.184.234.147]) by server1.neighborhoods.net (Postfix) with ESMTPSA id 2DCBCCC0B3 for ; Wed, 5 Sep 2012 09:24:22 -0400 (EDT) Message-ID: <50475285.5090300@meetinghouse.net> Date: Wed, 05 Sep 2012 09:24:21 -0400 From: Miles Fidelman User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.6; rv:15.0) Gecko/20120828 Firefox/15.0 SeaMonkey/2.12 MIME-Version: 1.0 To: "xen-users@lists.xensource.com" Subject: [Xen-users] xen + gluster: recent experiences? X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset="us-ascii"; Format="flowed" Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org Hi Folks, Anybody have any recent experiences building a small cluster with Xen and Gluster? I've been getting ready to move from a 2-node HA cluster (using DRBD) to a 4-node cluster. Sort of been tracking the maturity of Gluster as a replacement for DRBD. Any comments? Thanks, Miles Fidelman -- In theory, there is no difference between theory and practice. In practice, there is. .... Yogi Berra _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Wed Sep 05 15:05:45 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Wed, 05 Sep 2012 15:05:45 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1T9H9G-0002pX-Kq; Wed, 05 Sep 2012 15:04:10 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1T9H9E-0002pO-Ut for xen-users@lists.xen.org; Wed, 05 Sep 2012 15:04:09 +0000 Received: from [85.158.143.99:36989] by server-2.bemta-4.messagelabs.com id 41/A4-21239-7E967405; Wed, 05 Sep 2012 15:04:07 +0000 X-Env-Sender: dan@soleks.com X-Msg-Ref: server-4.tower-216.messagelabs.com!1346857444!23425975!1 X-Originating-IP: [199.175.126.195] X-SpamReason: No, hits=1.2 required=7.0 tests=HTML_20_30,HTML_MESSAGE, MAILTO_TO_SPAM_ADDR X-StarScan-Received: X-StarScan-Version: 6.6.1.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 19983 invoked from network); 5 Sep 2012 15:04:06 -0000 Received: from smtp.soleks.com (HELO mail-smtp00.soleks.net) (199.175.126.195) by server-4.tower-216.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 5 Sep 2012 15:04:06 -0000 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=soleks.com; s=x; h=Content-Transfer-Encoding:Content-Type:MIME-Version:In-Reply-To:References:Subject:To:From:Date:Message-ID; bh=oA2FJxaM2YzGUojn8mFUDqj5boNFe/koSs37yMM5aRQ=; b=OIcftc93xyXJwwc9gBPv0g5uGXy+tFyiaJc/oXcSw6W3NyzIj+ROnh7YcMc8c1AN5uyR03kjoco1PhZL/vMfRXo8Ylnij1hoixXvGCVJzlMneQeJ0KfXckTGHuzJaqj6; Received: from localhost ([127.0.0.1]) by mail-smtp00.soleks.net with smtp (Exim 4.74) (envelope-from ) id 1T9I7z-0003Kd-LV for xen-users@lists.xen.org; Wed, 05 Sep 2012 09:06:55 -0700 Received: from mail-webmail00.soleks.net ([192.168.230.224] helo=webmail.soleks.net) by mail-smtp00.soleks.net with esmtpa (Exim 4.74) (envelope-from ) id 1T9I7t-0003KW-3A for xen-users@lists.xen.org; Wed, 05 Sep 2012 09:06:53 -0700 Received: from S010678cd8e7ac150.vf.shawcable.net (S010678cd8e7ac150.vf.shawcable.net [174.1.142.40]) by webmail.soleks.com (Horde Framework) with HTTP; Wed, 05 Sep 2012 08:56:53 -0700 Message-ID: <20120905085653.19451hqjife56728@webmail.soleks.com> Date: Wed, 05 Sep 2012 08:56:53 -0700 From: dan@soleks.com To: xen-users@lists.xen.org References: In-Reply-To: MIME-Version: 1.0 User-Agent: Internet Messaging Program (IMP) H3 (4.3.9) X-GMS-IP-Reputation: 0 X-GMS-DCC-Result: A X-GMS-SpamScanned: 41ffe12a11cd4df5c438ff669f697540 X-DSPAM-Result: Innocent X-DSPAM-Processed: Wed Sep 5 09:06:55 2012 X-DSPAM-Confidence: 1.0000 X-DSPAM-Probability: 0.0023 X-DSPAM-Signature: 438,5047789f18351300313448 X-DSPAM-Factors: 27, will+#+#+time, 0.40000, will+#+#+time, 0.40000, was+#+saturation+appr+90, 0.40000, was+#+saturation+appr+90, 0.40000, Logical+Volumes+on+#+of, 0.40000, Logical+Volumes+on+#+of, 0.40000, i+think+#+best+solution, 0.40000, i+think+#+best+solution, 0.40000, best+#+for+#+man, 0.40000, best+#+for+#+man, 0.40000, for+#+#+local+storage, 0.40000, for+#+#+local+storage, 0.40000, XEN+#+#+So+i, 0.40000, XEN+#+#+So+i, 0.40000, 512G+I+don't+#+any, 0.40000, 512G+I+don't+#+any, 0.40000, see+#+performance+loss+Also, 0.40000, see+#+performance+loss+Also, 0.40000, performance+loss, 0.40000, performance+loss, 0.40000, but, 0.40000, but, 0.40000, message+is+#+MIME, 0.40000, 2+#+#+is+very, 0.40000, 2+#+#+is+very, 0.40000, HA+for+#+i'd, 0.40000, HA+for+#+i'd, 0.40000 X-GMS-SpamScore: 0 Subject: Re: [Xen-users] guest OS High Availability with local storage X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============1156303789257595448==" Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org This message is in MIME format. --===============1156303789257595448== Content-Type: multipart/alternative; boundary="=_862a6leqtyosg" Content-Transfer-Encoding: 7bit This message is in MIME format. --=_862a6leqtyosg Content-Type: text/plain; charset=ISO-8859-1 Content-Description: Plaintext Version of Message Content-Disposition: inline Content-Transfer-Encoding: 7bit From my experience gluster write performance (2 mirrored nodes) is very low, approx 40-45Mb/sec. read is pretty high and it was network saturation - appr 90-95Mb/sec (i have gigi network). For HA for VMs i'd highly recommend DRDB+Pacemaker+Corosync. Solution is much more advanced, and requires much more efforts, but output will cover all time expenses. I have cluster of 2 nodes with DRBD, some VM images (block devices, using Logical Volumes on top of DRDB) are up to 512G. I don't see any performance loss. Also Pacemaker is well integrated with XEN live migration. So i think it's best solution for "cheap man". > 2012/9/5 Andrew Wells : >> Actually look into gluster for turning your local storage into shared >> storage. Works with more than one node and replicates data. > > thanks for for this useful info, also to everyone who shared their opinion > > > > -- > Regards, > > Umarzuki Mochlis > http://debmal.my > > _______________________________________________ > Xen-users mailing list > Xen-users@lists.xen.org > http://lists.xen.org/xen-users > ---------------------------------------------------------------- This message was sent using IMP, the Internet Messaging Program. --=_862a6leqtyosg Content-Type: text/html; charset=ISO-8859-1 Content-Description: HTML Version of Message Content-Disposition: inline Content-Transfer-Encoding: 7bit

 From my experience gluster write performance (2 mirrored nodes) is very low, approx 40-45Mb/sec. read is pretty high and it was network saturation  - appr 90-95Mb/sec (i have gigi network). For HA for VMs i'd highly recommend DRDB+Pacemaker+Corosync. Solution is much more advanced, and requires much more efforts, but output will cover all time expenses. I have cluster of 2 nodes with DRBD, some VM images (block devices, using Logical Volumes on top of DRDB) are up to 512G. I don't see any performance loss. Also Pacemaker is well integrated with XEN live migration. So i think it's best solution for "cheap man".


> 2012/9/5 Andrew Wells <agwells0714@gmail.com>:
>> Actually look into gluster for turning your local storage into shared
>> storage. Works with more than one node and replicates data.
>
> thanks for for this useful info, also to everyone who shared their opinion
>
>
>
> --
> Regards,
>
> Umarzuki Mochlis
> http://debmal.my
>
> _______________________________________________
> Xen-users mailing list
> Xen-users@lists.xen.org
> http://lists.xen.org/xen-users
>


----------------------------------------------------------------
This message was sent using IMP, the Internet Messaging Program.
--=_862a6leqtyosg-- --===============1156303789257595448== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users --===============1156303789257595448==-- From xen-users-bounces@lists.xen.org Wed Sep 05 15:05:45 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Wed, 05 Sep 2012 15:05:45 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1T9H9G-0002pX-Kq; Wed, 05 Sep 2012 15:04:10 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1T9H9E-0002pO-Ut for xen-users@lists.xen.org; Wed, 05 Sep 2012 15:04:09 +0000 Received: from [85.158.143.99:36989] by server-2.bemta-4.messagelabs.com id 41/A4-21239-7E967405; Wed, 05 Sep 2012 15:04:07 +0000 X-Env-Sender: dan@soleks.com X-Msg-Ref: server-4.tower-216.messagelabs.com!1346857444!23425975!1 X-Originating-IP: [199.175.126.195] X-SpamReason: No, hits=1.2 required=7.0 tests=HTML_20_30,HTML_MESSAGE, MAILTO_TO_SPAM_ADDR X-StarScan-Received: X-StarScan-Version: 6.6.1.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 19983 invoked from network); 5 Sep 2012 15:04:06 -0000 Received: from smtp.soleks.com (HELO mail-smtp00.soleks.net) (199.175.126.195) by server-4.tower-216.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 5 Sep 2012 15:04:06 -0000 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=soleks.com; s=x; h=Content-Transfer-Encoding:Content-Type:MIME-Version:In-Reply-To:References:Subject:To:From:Date:Message-ID; bh=oA2FJxaM2YzGUojn8mFUDqj5boNFe/koSs37yMM5aRQ=; b=OIcftc93xyXJwwc9gBPv0g5uGXy+tFyiaJc/oXcSw6W3NyzIj+ROnh7YcMc8c1AN5uyR03kjoco1PhZL/vMfRXo8Ylnij1hoixXvGCVJzlMneQeJ0KfXckTGHuzJaqj6; Received: from localhost ([127.0.0.1]) by mail-smtp00.soleks.net with smtp (Exim 4.74) (envelope-from ) id 1T9I7z-0003Kd-LV for xen-users@lists.xen.org; Wed, 05 Sep 2012 09:06:55 -0700 Received: from mail-webmail00.soleks.net ([192.168.230.224] helo=webmail.soleks.net) by mail-smtp00.soleks.net with esmtpa (Exim 4.74) (envelope-from ) id 1T9I7t-0003KW-3A for xen-users@lists.xen.org; Wed, 05 Sep 2012 09:06:53 -0700 Received: from S010678cd8e7ac150.vf.shawcable.net (S010678cd8e7ac150.vf.shawcable.net [174.1.142.40]) by webmail.soleks.com (Horde Framework) with HTTP; Wed, 05 Sep 2012 08:56:53 -0700 Message-ID: <20120905085653.19451hqjife56728@webmail.soleks.com> Date: Wed, 05 Sep 2012 08:56:53 -0700 From: dan@soleks.com To: xen-users@lists.xen.org References: In-Reply-To: MIME-Version: 1.0 User-Agent: Internet Messaging Program (IMP) H3 (4.3.9) X-GMS-IP-Reputation: 0 X-GMS-DCC-Result: A X-GMS-SpamScanned: 41ffe12a11cd4df5c438ff669f697540 X-DSPAM-Result: Innocent X-DSPAM-Processed: Wed Sep 5 09:06:55 2012 X-DSPAM-Confidence: 1.0000 X-DSPAM-Probability: 0.0023 X-DSPAM-Signature: 438,5047789f18351300313448 X-DSPAM-Factors: 27, will+#+#+time, 0.40000, will+#+#+time, 0.40000, was+#+saturation+appr+90, 0.40000, was+#+saturation+appr+90, 0.40000, Logical+Volumes+on+#+of, 0.40000, Logical+Volumes+on+#+of, 0.40000, i+think+#+best+solution, 0.40000, i+think+#+best+solution, 0.40000, best+#+for+#+man, 0.40000, best+#+for+#+man, 0.40000, for+#+#+local+storage, 0.40000, for+#+#+local+storage, 0.40000, XEN+#+#+So+i, 0.40000, XEN+#+#+So+i, 0.40000, 512G+I+don't+#+any, 0.40000, 512G+I+don't+#+any, 0.40000, see+#+performance+loss+Also, 0.40000, see+#+performance+loss+Also, 0.40000, performance+loss, 0.40000, performance+loss, 0.40000, but, 0.40000, but, 0.40000, message+is+#+MIME, 0.40000, 2+#+#+is+very, 0.40000, 2+#+#+is+very, 0.40000, HA+for+#+i'd, 0.40000, HA+for+#+i'd, 0.40000 X-GMS-SpamScore: 0 Subject: Re: [Xen-users] guest OS High Availability with local storage X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============1156303789257595448==" Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org This message is in MIME format. --===============1156303789257595448== Content-Type: multipart/alternative; boundary="=_862a6leqtyosg" Content-Transfer-Encoding: 7bit This message is in MIME format. --=_862a6leqtyosg Content-Type: text/plain; charset=ISO-8859-1 Content-Description: Plaintext Version of Message Content-Disposition: inline Content-Transfer-Encoding: 7bit From my experience gluster write performance (2 mirrored nodes) is very low, approx 40-45Mb/sec. read is pretty high and it was network saturation - appr 90-95Mb/sec (i have gigi network). For HA for VMs i'd highly recommend DRDB+Pacemaker+Corosync. Solution is much more advanced, and requires much more efforts, but output will cover all time expenses. I have cluster of 2 nodes with DRBD, some VM images (block devices, using Logical Volumes on top of DRDB) are up to 512G. I don't see any performance loss. Also Pacemaker is well integrated with XEN live migration. So i think it's best solution for "cheap man". > 2012/9/5 Andrew Wells : >> Actually look into gluster for turning your local storage into shared >> storage. Works with more than one node and replicates data. > > thanks for for this useful info, also to everyone who shared their opinion > > > > -- > Regards, > > Umarzuki Mochlis > http://debmal.my > > _______________________________________________ > Xen-users mailing list > Xen-users@lists.xen.org > http://lists.xen.org/xen-users > ---------------------------------------------------------------- This message was sent using IMP, the Internet Messaging Program. --=_862a6leqtyosg Content-Type: text/html; charset=ISO-8859-1 Content-Description: HTML Version of Message Content-Disposition: inline Content-Transfer-Encoding: 7bit

 From my experience gluster write performance (2 mirrored nodes) is very low, approx 40-45Mb/sec. read is pretty high and it was network saturation  - appr 90-95Mb/sec (i have gigi network). For HA for VMs i'd highly recommend DRDB+Pacemaker+Corosync. Solution is much more advanced, and requires much more efforts, but output will cover all time expenses. I have cluster of 2 nodes with DRBD, some VM images (block devices, using Logical Volumes on top of DRDB) are up to 512G. I don't see any performance loss. Also Pacemaker is well integrated with XEN live migration. So i think it's best solution for "cheap man".


> 2012/9/5 Andrew Wells <agwells0714@gmail.com>:
>> Actually look into gluster for turning your local storage into shared
>> storage. Works with more than one node and replicates data.
>
> thanks for for this useful info, also to everyone who shared their opinion
>
>
>
> --
> Regards,
>
> Umarzuki Mochlis
> http://debmal.my
>
> _______________________________________________
> Xen-users mailing list
> Xen-users@lists.xen.org
> http://lists.xen.org/xen-users
>


----------------------------------------------------------------
This message was sent using IMP, the Internet Messaging Program.
--=_862a6leqtyosg-- --===============1156303789257595448== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users --===============1156303789257595448==-- From xen-users-bounces@lists.xen.org Wed Sep 05 15:30:50 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Wed, 05 Sep 2012 15:30:50 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1T9HXs-0003gC-AC; Wed, 05 Sep 2012 15:29:36 +0000 Received: from mail27.messagelabs.com ([193.109.254.147]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1T9HXq-0003fx-7w; Wed, 05 Sep 2012 15:29:34 +0000 X-Env-Sender: pasik@iki.fi X-Msg-Ref: server-7.tower-27.messagelabs.com!1346858967!2038421!1 X-Originating-IP: [192.89.123.25] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogMTkyLjg5LjEyMy4yNSA9PiA1MDI2OTU=\n X-StarScan-Received: X-StarScan-Version: 6.6.1.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 1212 invoked from network); 5 Sep 2012 15:29:28 -0000 Received: from smtp.tele.fi (HELO smtp.tele.fi) (192.89.123.25) by server-7.tower-27.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 5 Sep 2012 15:29:28 -0000 X-Originating-Ip: [194.89.68.22] Received: from ydin.reaktio.net (reaktio.net [194.89.68.22]) by smtp.tele.fi (Postfix) with ESMTP id 3A2941265; Wed, 5 Sep 2012 18:29:26 +0300 (EEST) Received: by ydin.reaktio.net (Postfix, from userid 1001) id 690E62005D; Wed, 5 Sep 2012 18:29:26 +0300 (EEST) Date: Wed, 5 Sep 2012 18:29:26 +0300 From: Pasi =?iso-8859-1?Q?K=E4rkk=E4inen?= To: Ian Campbell Message-ID: <20120905152926.GM8912@reaktio.net> References: <1346665360.25864.2.camel@zakaz.uk.xensource.com> MIME-Version: 1.0 Content-Disposition: inline In-Reply-To: <1346665360.25864.2.camel@zakaz.uk.xensource.com> User-Agent: Mutt/1.5.20 (2009-06-14) Cc: xen-users , xen-devel Subject: Re: [Xen-users] [Xen-devel] Xen 4.2.0 Release Plan / TODO X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org On Mon, Sep 03, 2012 at 10:42:40AM +0100, Ian Campbell wrote: > > tools, nice to have: > * pygrub support for ext4 on rhel5/centos5. Roger already sent a patch for this. -- Pasi _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Wed Sep 05 15:30:50 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Wed, 05 Sep 2012 15:30:50 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1T9HXs-0003gC-AC; Wed, 05 Sep 2012 15:29:36 +0000 Received: from mail27.messagelabs.com ([193.109.254.147]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1T9HXq-0003fx-7w; Wed, 05 Sep 2012 15:29:34 +0000 X-Env-Sender: pasik@iki.fi X-Msg-Ref: server-7.tower-27.messagelabs.com!1346858967!2038421!1 X-Originating-IP: [192.89.123.25] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogMTkyLjg5LjEyMy4yNSA9PiA1MDI2OTU=\n X-StarScan-Received: X-StarScan-Version: 6.6.1.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 1212 invoked from network); 5 Sep 2012 15:29:28 -0000 Received: from smtp.tele.fi (HELO smtp.tele.fi) (192.89.123.25) by server-7.tower-27.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 5 Sep 2012 15:29:28 -0000 X-Originating-Ip: [194.89.68.22] Received: from ydin.reaktio.net (reaktio.net [194.89.68.22]) by smtp.tele.fi (Postfix) with ESMTP id 3A2941265; Wed, 5 Sep 2012 18:29:26 +0300 (EEST) Received: by ydin.reaktio.net (Postfix, from userid 1001) id 690E62005D; Wed, 5 Sep 2012 18:29:26 +0300 (EEST) Date: Wed, 5 Sep 2012 18:29:26 +0300 From: Pasi =?iso-8859-1?Q?K=E4rkk=E4inen?= To: Ian Campbell Message-ID: <20120905152926.GM8912@reaktio.net> References: <1346665360.25864.2.camel@zakaz.uk.xensource.com> MIME-Version: 1.0 Content-Disposition: inline In-Reply-To: <1346665360.25864.2.camel@zakaz.uk.xensource.com> User-Agent: Mutt/1.5.20 (2009-06-14) Cc: xen-users , xen-devel Subject: Re: [Xen-users] [Xen-devel] Xen 4.2.0 Release Plan / TODO X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org On Mon, Sep 03, 2012 at 10:42:40AM +0100, Ian Campbell wrote: > > tools, nice to have: > * pygrub support for ext4 on rhel5/centos5. Roger already sent a patch for this. -- Pasi _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Wed Sep 05 16:38:15 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Wed, 05 Sep 2012 16:38:15 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1T9IbE-0005bj-05; Wed, 05 Sep 2012 16:37:08 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1T9IbD-0005bS-26 for xen-users@lists.xen.org; Wed, 05 Sep 2012 16:37:07 +0000 Received: from [85.158.143.99:14434] by server-1.bemta-4.messagelabs.com id AA/A0-12504-2BF77405; Wed, 05 Sep 2012 16:37:06 +0000 X-Env-Sender: mex@di.unipmn.it X-Msg-Ref: server-2.tower-216.messagelabs.com!1346863025!23395917!1 X-Originating-IP: [193.206.52.44] X-SpamReason: No, hits=0.0 required=7.0 tests=received_headers: No Received headers X-StarScan-Received: X-StarScan-Version: 6.6.1.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 18834 invoked from network); 5 Sep 2012 16:37:06 -0000 Received: from mail.di.unipmn.it (HELO mail.di.unipmn.it) (193.206.52.44) by server-2.tower-216.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 5 Sep 2012 16:37:06 -0000 X-Received: from shrek.mfn.unipmn.it (unknown [172.22.255.10]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) (Authenticated sender: mex@di.unipmn.it) by mail.di.unipmn.it (vPostMaster) with ESMTP id 2A1CA138002 for ; Wed, 5 Sep 2012 18:37:05 +0200 (CEST) Message-ID: <50477EF6.4070802@di.unipmn.it> Date: Wed, 05 Sep 2012 18:33:58 +0200 From: Massimo Canonico User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:13.0) Gecko/20120605 Thunderbird/13.0 MIME-Version: 1.0 To: xen-users@lists.xen.org Subject: [Xen-users] "xentop -b -i1" always returns 0 for cpuload X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset="us-ascii"; Format="flowed" Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org Hi, I need to save into a file the "cpu load" value for a specific domain provided by "xentop" command. So I decided to write a very simple bash script: while : do sudo xentop -b -i1 | grep | awk '{print $4}' sleep 10 done The problem is that with "-i1" I always get 0.0 as output values, even if when xentop (without "-b -i1") provides me the right cpu load values. How can I fix this problem? Thanks, M _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Wed Sep 05 16:38:15 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Wed, 05 Sep 2012 16:38:15 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1T9IbE-0005bj-05; Wed, 05 Sep 2012 16:37:08 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1T9IbD-0005bS-26 for xen-users@lists.xen.org; Wed, 05 Sep 2012 16:37:07 +0000 Received: from [85.158.143.99:14434] by server-1.bemta-4.messagelabs.com id AA/A0-12504-2BF77405; Wed, 05 Sep 2012 16:37:06 +0000 X-Env-Sender: mex@di.unipmn.it X-Msg-Ref: server-2.tower-216.messagelabs.com!1346863025!23395917!1 X-Originating-IP: [193.206.52.44] X-SpamReason: No, hits=0.0 required=7.0 tests=received_headers: No Received headers X-StarScan-Received: X-StarScan-Version: 6.6.1.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 18834 invoked from network); 5 Sep 2012 16:37:06 -0000 Received: from mail.di.unipmn.it (HELO mail.di.unipmn.it) (193.206.52.44) by server-2.tower-216.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 5 Sep 2012 16:37:06 -0000 X-Received: from shrek.mfn.unipmn.it (unknown [172.22.255.10]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) (Authenticated sender: mex@di.unipmn.it) by mail.di.unipmn.it (vPostMaster) with ESMTP id 2A1CA138002 for ; Wed, 5 Sep 2012 18:37:05 +0200 (CEST) Message-ID: <50477EF6.4070802@di.unipmn.it> Date: Wed, 05 Sep 2012 18:33:58 +0200 From: Massimo Canonico User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:13.0) Gecko/20120605 Thunderbird/13.0 MIME-Version: 1.0 To: xen-users@lists.xen.org Subject: [Xen-users] "xentop -b -i1" always returns 0 for cpuload X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset="us-ascii"; Format="flowed" Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org Hi, I need to save into a file the "cpu load" value for a specific domain provided by "xentop" command. So I decided to write a very simple bash script: while : do sudo xentop -b -i1 | grep | awk '{print $4}' sleep 10 done The problem is that with "-i1" I always get 0.0 as output values, even if when xentop (without "-b -i1") provides me the right cpu load values. How can I fix this problem? Thanks, M _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Wed Sep 05 17:54:22 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Wed, 05 Sep 2012 17:54:22 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1T9Jmy-00007o-Fh; Wed, 05 Sep 2012 17:53:20 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1T9Jmx-00007X-O4 for xen-users@lists.xen.org; Wed, 05 Sep 2012 17:53:19 +0000 Received: from [85.158.143.99:59539] by server-3.bemta-4.messagelabs.com id D3/32-08232-E8197405; Wed, 05 Sep 2012 17:53:18 +0000 X-Env-Sender: lists+xen@internecto.net X-Msg-Ref: server-3.tower-216.messagelabs.com!1346867595!28155512!1 X-Originating-IP: [176.9.245.29] X-SpamReason: No, hits=0.0 required=7.0 tests= X-StarScan-Received: X-StarScan-Version: 6.6.1.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 23433 invoked from network); 5 Sep 2012 17:53:18 -0000 Received: from polaris.internecto.net (HELO mx1.internecto.net) (176.9.245.29) by server-3.tower-216.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 5 Sep 2012 17:53:18 -0000 Received: from localhost (localhost [127.0.0.1]) by mx1.internecto.net (Postfix) with ESMTP id 48273A0086; Wed, 5 Sep 2012 17:53:11 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at mail.internecto.net Received: from mx1.internecto.net ([127.0.0.1]) by localhost (mail.polaris.internecto.net [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Ecj6FGasp5gl; Wed, 5 Sep 2012 17:53:10 +0000 (UTC) Received: from internecto.net (5ED4FDEB.cm-7-5d.dynamic.ziggo.nl [94.212.253.235]) (using TLSv1 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (Client did not present a certificate) (Authenticated sender: lists@internecto.net) by mx1.internecto.net (Postfix) with ESMTPSA id BE728A0058; Wed, 5 Sep 2012 17:53:10 +0000 (UTC) Date: Wed, 5 Sep 2012 19:53:07 +0200 From: Mark van Dijk To: xen-users@lists.xen.org Message-ID: <20120905195307.101d0cbc@internecto.net> In-Reply-To: <20120905152926.GM8912@reaktio.net> References: <1346665360.25864.2.camel@zakaz.uk.xensource.com> <20120905152926.GM8912@reaktio.net> Organization: Internecto SIS X-Mailer: Claws Mail 3.8.0 (GTK+ 2.24.10; x86_64-pc-linux-gnu) Mime-Version: 1.0 Cc: xen-devel Subject: Re: [Xen-users] [Xen-devel] Xen 4.2.0 Release Plan / TODO X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org >> tools, nice to have: > > * pygrub support for ext4 on rhel5/centos5. > Roger already sent a patch for this. I'd love to see some kind of extlinux (or grub2) that can replace the current pv-grub. Both support ext4 and, more importantly imho, btrfs, now that is one really cool filesystem. Grub0.97 is/will be being deprecated on an increasing number of distributions. And pv-grub is safer than pygrub because pygrub executes in the dom0 and pv-grub in the domU, if I understand correctly. Anyone willing to share thoughts on the possibility of 'pv-extlinux?' -- Stay in touch, Mark van Dijk. ,--------------------------------- -----------------------------' Wed Sep 05 17:44 UTC 2012 Today is Pungenday, the 29th day of Bureaucracy in the YOLD 3178 _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Wed Sep 05 17:54:22 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Wed, 05 Sep 2012 17:54:22 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1T9Jmy-00007o-Fh; Wed, 05 Sep 2012 17:53:20 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1T9Jmx-00007X-O4 for xen-users@lists.xen.org; Wed, 05 Sep 2012 17:53:19 +0000 Received: from [85.158.143.99:59539] by server-3.bemta-4.messagelabs.com id D3/32-08232-E8197405; Wed, 05 Sep 2012 17:53:18 +0000 X-Env-Sender: lists+xen@internecto.net X-Msg-Ref: server-3.tower-216.messagelabs.com!1346867595!28155512!1 X-Originating-IP: [176.9.245.29] X-SpamReason: No, hits=0.0 required=7.0 tests= X-StarScan-Received: X-StarScan-Version: 6.6.1.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 23433 invoked from network); 5 Sep 2012 17:53:18 -0000 Received: from polaris.internecto.net (HELO mx1.internecto.net) (176.9.245.29) by server-3.tower-216.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 5 Sep 2012 17:53:18 -0000 Received: from localhost (localhost [127.0.0.1]) by mx1.internecto.net (Postfix) with ESMTP id 48273A0086; Wed, 5 Sep 2012 17:53:11 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at mail.internecto.net Received: from mx1.internecto.net ([127.0.0.1]) by localhost (mail.polaris.internecto.net [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Ecj6FGasp5gl; Wed, 5 Sep 2012 17:53:10 +0000 (UTC) Received: from internecto.net (5ED4FDEB.cm-7-5d.dynamic.ziggo.nl [94.212.253.235]) (using TLSv1 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (Client did not present a certificate) (Authenticated sender: lists@internecto.net) by mx1.internecto.net (Postfix) with ESMTPSA id BE728A0058; Wed, 5 Sep 2012 17:53:10 +0000 (UTC) Date: Wed, 5 Sep 2012 19:53:07 +0200 From: Mark van Dijk To: xen-users@lists.xen.org Message-ID: <20120905195307.101d0cbc@internecto.net> In-Reply-To: <20120905152926.GM8912@reaktio.net> References: <1346665360.25864.2.camel@zakaz.uk.xensource.com> <20120905152926.GM8912@reaktio.net> Organization: Internecto SIS X-Mailer: Claws Mail 3.8.0 (GTK+ 2.24.10; x86_64-pc-linux-gnu) Mime-Version: 1.0 Cc: xen-devel Subject: Re: [Xen-users] [Xen-devel] Xen 4.2.0 Release Plan / TODO X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org >> tools, nice to have: > > * pygrub support for ext4 on rhel5/centos5. > Roger already sent a patch for this. I'd love to see some kind of extlinux (or grub2) that can replace the current pv-grub. Both support ext4 and, more importantly imho, btrfs, now that is one really cool filesystem. Grub0.97 is/will be being deprecated on an increasing number of distributions. And pv-grub is safer than pygrub because pygrub executes in the dom0 and pv-grub in the domU, if I understand correctly. Anyone willing to share thoughts on the possibility of 'pv-extlinux?' -- Stay in touch, Mark van Dijk. ,--------------------------------- -----------------------------' Wed Sep 05 17:44 UTC 2012 Today is Pungenday, the 29th day of Bureaucracy in the YOLD 3178 _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Wed Sep 05 17:58:41 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Wed, 05 Sep 2012 17:58:41 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1T9JrK-0000Vy-RE; Wed, 05 Sep 2012 17:57:50 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1T9JrI-0000VW-SU for xen-users@lists.xen.org; Wed, 05 Sep 2012 17:57:48 +0000 Received: from [85.158.139.83:45969] by server-10.bemta-5.messagelabs.com id CD/42-10969-B9297405; Wed, 05 Sep 2012 17:57:47 +0000 X-Env-Sender: Ian.Campbell@citrix.com X-Msg-Ref: server-16.tower-182.messagelabs.com!1346867867!21426399!1 X-Originating-IP: [62.200.22.115] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogNjIuMjAwLjIyLjExNSA9PiAxMTE5ODY=\n X-StarScan-Received: X-StarScan-Version: 6.6.1.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 26408 invoked from network); 5 Sep 2012 17:57:47 -0000 Received: from smtp.eu.citrix.com (HELO SMTP.EU.CITRIX.COM) (62.200.22.115) by server-16.tower-182.messagelabs.com with RC4-SHA encrypted SMTP; 5 Sep 2012 17:57:47 -0000 X-IronPort-AV: E=Sophos;i="4.80,375,1344211200"; d="scan'208";a="14365823" Received: from lonpmailmx01.citrite.net ([10.30.203.162]) by LONPIPO01.EU.CITRIX.COM with ESMTP/TLS/RC4-MD5; 05 Sep 2012 17:57:47 +0000 Received: from [127.0.0.1] (10.80.16.67) by smtprelay.citrix.com (10.30.203.162) with Microsoft SMTP Server id 8.3.279.1; Wed, 5 Sep 2012 18:57:46 +0100 Message-ID: <1346867866.10570.4.camel@dagon.hellion.org.uk> From: Ian Campbell To: Pasi =?ISO-8859-1?Q?K=E4rkk=E4inen?= Date: Wed, 5 Sep 2012 18:57:46 +0100 In-Reply-To: <20120905152926.GM8912@reaktio.net> References: <1346665360.25864.2.camel@zakaz.uk.xensource.com> <20120905152926.GM8912@reaktio.net> Organization: Citrix Systems, Inc. X-Mailer: Evolution 3.4.3-1 MIME-Version: 1.0 Cc: xen-users , xen-devel Subject: Re: [Xen-users] [Xen-devel] Xen 4.2.0 Release Plan / TODO X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org On Wed, 2012-09-05 at 16:29 +0100, Pasi K=E4rkk=E4inen wrote: > On Mon, Sep 03, 2012 at 10:42:40AM +0100, Ian Campbell wrote: > > = > > tools, nice to have: > > = > = > * pygrub support for ext4 on rhel5/centos5. > Roger already sent a patch for this. As I said in the introduction we are intending to do the final RC on Friday (i.e. the day after tomorrow). So at this stage in the release I'm afraid you will have to do a *much* better job of justifying why any change should go on the list (and therefore be considered for inclusion in 4.2.0) than that. Ian. _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Wed Sep 05 17:58:41 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Wed, 05 Sep 2012 17:58:41 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1T9JrK-0000Vy-RE; Wed, 05 Sep 2012 17:57:50 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1T9JrI-0000VW-SU for xen-users@lists.xen.org; Wed, 05 Sep 2012 17:57:48 +0000 Received: from [85.158.139.83:45969] by server-10.bemta-5.messagelabs.com id CD/42-10969-B9297405; Wed, 05 Sep 2012 17:57:47 +0000 X-Env-Sender: Ian.Campbell@citrix.com X-Msg-Ref: server-16.tower-182.messagelabs.com!1346867867!21426399!1 X-Originating-IP: [62.200.22.115] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogNjIuMjAwLjIyLjExNSA9PiAxMTE5ODY=\n X-StarScan-Received: X-StarScan-Version: 6.6.1.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 26408 invoked from network); 5 Sep 2012 17:57:47 -0000 Received: from smtp.eu.citrix.com (HELO SMTP.EU.CITRIX.COM) (62.200.22.115) by server-16.tower-182.messagelabs.com with RC4-SHA encrypted SMTP; 5 Sep 2012 17:57:47 -0000 X-IronPort-AV: E=Sophos;i="4.80,375,1344211200"; d="scan'208";a="14365823" Received: from lonpmailmx01.citrite.net ([10.30.203.162]) by LONPIPO01.EU.CITRIX.COM with ESMTP/TLS/RC4-MD5; 05 Sep 2012 17:57:47 +0000 Received: from [127.0.0.1] (10.80.16.67) by smtprelay.citrix.com (10.30.203.162) with Microsoft SMTP Server id 8.3.279.1; Wed, 5 Sep 2012 18:57:46 +0100 Message-ID: <1346867866.10570.4.camel@dagon.hellion.org.uk> From: Ian Campbell To: Pasi =?ISO-8859-1?Q?K=E4rkk=E4inen?= Date: Wed, 5 Sep 2012 18:57:46 +0100 In-Reply-To: <20120905152926.GM8912@reaktio.net> References: <1346665360.25864.2.camel@zakaz.uk.xensource.com> <20120905152926.GM8912@reaktio.net> Organization: Citrix Systems, Inc. X-Mailer: Evolution 3.4.3-1 MIME-Version: 1.0 Cc: xen-users , xen-devel Subject: Re: [Xen-users] [Xen-devel] Xen 4.2.0 Release Plan / TODO X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org On Wed, 2012-09-05 at 16:29 +0100, Pasi K=E4rkk=E4inen wrote: > On Mon, Sep 03, 2012 at 10:42:40AM +0100, Ian Campbell wrote: > > = > > tools, nice to have: > > = > = > * pygrub support for ext4 on rhel5/centos5. > Roger already sent a patch for this. As I said in the introduction we are intending to do the final RC on Friday (i.e. the day after tomorrow). So at this stage in the release I'm afraid you will have to do a *much* better job of justifying why any change should go on the list (and therefore be considered for inclusion in 4.2.0) than that. Ian. _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Wed Sep 05 18:07:04 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Wed, 05 Sep 2012 18:07:04 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1T9JzT-0001Aq-FM; Wed, 05 Sep 2012 18:06:15 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1T9JzR-0001Ad-Gj for xen-users@lists.xen.org; Wed, 05 Sep 2012 18:06:13 +0000 Received: from [85.158.143.99:39642] by server-3.bemta-4.messagelabs.com id CA/AB-08232-49497405; Wed, 05 Sep 2012 18:06:12 +0000 X-Env-Sender: lists+xen@internecto.net X-Msg-Ref: server-9.tower-216.messagelabs.com!1346868371!28764799!1 X-Originating-IP: [176.9.245.29] X-SpamReason: No, hits=0.0 required=7.0 tests= X-StarScan-Received: X-StarScan-Version: 6.6.1.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 25741 invoked from network); 5 Sep 2012 18:06:12 -0000 Received: from polaris.internecto.net (HELO mx1.internecto.net) (176.9.245.29) by server-9.tower-216.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 5 Sep 2012 18:06:12 -0000 Received: from localhost (localhost [127.0.0.1]) by mx1.internecto.net (Postfix) with ESMTP id AA54AA0086; Wed, 5 Sep 2012 18:06:11 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at mail.internecto.net Received: from mx1.internecto.net ([127.0.0.1]) by localhost (mail.polaris.internecto.net [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id SbexAdHgREMH; Wed, 5 Sep 2012 18:06:11 +0000 (UTC) Received: from internecto.net (5ED4FDEB.cm-7-5d.dynamic.ziggo.nl [94.212.253.235]) (using TLSv1 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (Client did not present a certificate) (Authenticated sender: lists@internecto.net) by mx1.internecto.net (Postfix) with ESMTPSA id 3E1A5A0058; Wed, 5 Sep 2012 18:06:11 +0000 (UTC) Date: Wed, 5 Sep 2012 20:06:10 +0200 From: Mark van Dijk To: raju@linux-delhi.org Message-ID: <20120905200610.67ded1a9@internecto.net> In-Reply-To: <201209041058.17442.raju@linux-delhi.org> References: <1092892085@mx1.poinfor.net> <1346734547.93695.YahooMailNeo@web126002.mail.ne1.yahoo.com> <201209041058.17442.raju@linux-delhi.org> Organization: Internecto SIS X-Mailer: Claws Mail 3.8.0 (GTK+ 2.24.10; x86_64-pc-linux-gnu) Mime-Version: 1.0 Cc: xen-users@lists.xen.org Subject: Re: [Xen-users] Xen summit Videos X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: base64 Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org UXVvdGluZyBSYWogTWF0aHVyICjgpLDgpL7gpJwg4KSu4KS+4KSl4KWB4KSwKSdzIG1lc3NhZ2Ug ZnJvbSAwNCBzZXAgMjAxMjoKPk9uIFR1ZXNkYXkgMDQgU2VwIDIwMTIsIG1haGVlbiBidXR0IHdy b3RlOgo+PiBjYW4ndCB1bmRlcnN0YW5kIFBsZWFzZSB1c2UgRW5nbGlzaCAKPgo+TG9va3MgbGlr ZSBhbiBhdXRvbWF0ZWQgT3V0LW9mLU9mZmljZSBtZXNzYWdlIGluIEZyZW5jaC4gIEkgYWxzbyBn b3QKPm9uZSBvZiB0aGVzZS4KPgo+RG8gdGhlc2UgbmVlZCB0byBiZSByZXBvcnRlZCB0byB0aGUg bGlzdCBhZG1pbj8KCkkgdGhpbmsgdGhhdCB3b24ndCBoZWxwIG11Y2ggYmVjYXVzZSB0aG9zZSAn dmFjYXRpb24nIG1lc3NhZ2VzIHdpbGwKc3RpbGwgYmUgc2VudCB0byBpbmRpdmlkdWFscyBhZGRy ZXNzZXMgKHNhbWUgYXMgd2hlbiB5b3UgaGl0ICJyZXBseQphbGwiKS4gVXN1YWxseSBwZW9wbGUg YXJlIHRvbGQsIG9mZiBsaXN0LCB0byBkaXNhYmxlIHRoYXQgYXNhcCBhbmQgbW9zdApwZW9wbGUg ZG8gdGhhdCBhbnl3YXkgb25jZSB0aGV5IGdldCBiYWNrLiBCdXQgZWFjaCB5ZWFyLCBlc3BlY2lh bGx5CmFyb3VuZCBKdWx5L0F1Z3VzdCwgbmV3IHN1YnNjcmliZXJzIG1ha2UgdGhlIHNhbWUgbWlz dGFrZSBhcyB0aGVpcgpwcmVkZWNlc3NvcnMuCgpBaCB3ZWxsLiBTaW5jZSB0aGV5IGp1c3QgaW5m b3JtZWQgdGhlIHdob2xlIHdvcmxkLCB2aWEgcHVibGljIGxpc3RzLAphYm91dCB0aGVpciB2YWNh dGlvbiBpdCB3aWxsIG1ha2UgKnNvbWUqIHBlb3BsZSBoYXBweS4gTGlrZSBtYXJrZXRlZXJzLAph ZHZlcnRpc2VycyBhbmQgZXZlbiBidXJnbGFycyBJIHdhZ2VyLiA+OikKCl9fX19fX19fX19fX19f X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fClhlbi11c2VycyBtYWlsaW5nIGxpc3QK WGVuLXVzZXJzQGxpc3RzLnhlbi5vcmcKaHR0cDovL2xpc3RzLnhlbi5vcmcveGVuLXVzZXJz From xen-users-bounces@lists.xen.org Wed Sep 05 18:07:04 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Wed, 05 Sep 2012 18:07:04 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1T9JzT-0001Aq-FM; Wed, 05 Sep 2012 18:06:15 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1T9JzR-0001Ad-Gj for xen-users@lists.xen.org; Wed, 05 Sep 2012 18:06:13 +0000 Received: from [85.158.143.99:39642] by server-3.bemta-4.messagelabs.com id CA/AB-08232-49497405; Wed, 05 Sep 2012 18:06:12 +0000 X-Env-Sender: lists+xen@internecto.net X-Msg-Ref: server-9.tower-216.messagelabs.com!1346868371!28764799!1 X-Originating-IP: [176.9.245.29] X-SpamReason: No, hits=0.0 required=7.0 tests= X-StarScan-Received: X-StarScan-Version: 6.6.1.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 25741 invoked from network); 5 Sep 2012 18:06:12 -0000 Received: from polaris.internecto.net (HELO mx1.internecto.net) (176.9.245.29) by server-9.tower-216.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 5 Sep 2012 18:06:12 -0000 Received: from localhost (localhost [127.0.0.1]) by mx1.internecto.net (Postfix) with ESMTP id AA54AA0086; Wed, 5 Sep 2012 18:06:11 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at mail.internecto.net Received: from mx1.internecto.net ([127.0.0.1]) by localhost (mail.polaris.internecto.net [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id SbexAdHgREMH; Wed, 5 Sep 2012 18:06:11 +0000 (UTC) Received: from internecto.net (5ED4FDEB.cm-7-5d.dynamic.ziggo.nl [94.212.253.235]) (using TLSv1 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (Client did not present a certificate) (Authenticated sender: lists@internecto.net) by mx1.internecto.net (Postfix) with ESMTPSA id 3E1A5A0058; Wed, 5 Sep 2012 18:06:11 +0000 (UTC) Date: Wed, 5 Sep 2012 20:06:10 +0200 From: Mark van Dijk To: raju@linux-delhi.org Message-ID: <20120905200610.67ded1a9@internecto.net> In-Reply-To: <201209041058.17442.raju@linux-delhi.org> References: <1092892085@mx1.poinfor.net> <1346734547.93695.YahooMailNeo@web126002.mail.ne1.yahoo.com> <201209041058.17442.raju@linux-delhi.org> Organization: Internecto SIS X-Mailer: Claws Mail 3.8.0 (GTK+ 2.24.10; x86_64-pc-linux-gnu) Mime-Version: 1.0 Cc: xen-users@lists.xen.org Subject: Re: [Xen-users] Xen summit Videos X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: base64 Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org UXVvdGluZyBSYWogTWF0aHVyICjgpLDgpL7gpJwg4KSu4KS+4KSl4KWB4KSwKSdzIG1lc3NhZ2Ug ZnJvbSAwNCBzZXAgMjAxMjoKPk9uIFR1ZXNkYXkgMDQgU2VwIDIwMTIsIG1haGVlbiBidXR0IHdy b3RlOgo+PiBjYW4ndCB1bmRlcnN0YW5kIFBsZWFzZSB1c2UgRW5nbGlzaCAKPgo+TG9va3MgbGlr ZSBhbiBhdXRvbWF0ZWQgT3V0LW9mLU9mZmljZSBtZXNzYWdlIGluIEZyZW5jaC4gIEkgYWxzbyBn b3QKPm9uZSBvZiB0aGVzZS4KPgo+RG8gdGhlc2UgbmVlZCB0byBiZSByZXBvcnRlZCB0byB0aGUg bGlzdCBhZG1pbj8KCkkgdGhpbmsgdGhhdCB3b24ndCBoZWxwIG11Y2ggYmVjYXVzZSB0aG9zZSAn dmFjYXRpb24nIG1lc3NhZ2VzIHdpbGwKc3RpbGwgYmUgc2VudCB0byBpbmRpdmlkdWFscyBhZGRy ZXNzZXMgKHNhbWUgYXMgd2hlbiB5b3UgaGl0ICJyZXBseQphbGwiKS4gVXN1YWxseSBwZW9wbGUg YXJlIHRvbGQsIG9mZiBsaXN0LCB0byBkaXNhYmxlIHRoYXQgYXNhcCBhbmQgbW9zdApwZW9wbGUg ZG8gdGhhdCBhbnl3YXkgb25jZSB0aGV5IGdldCBiYWNrLiBCdXQgZWFjaCB5ZWFyLCBlc3BlY2lh bGx5CmFyb3VuZCBKdWx5L0F1Z3VzdCwgbmV3IHN1YnNjcmliZXJzIG1ha2UgdGhlIHNhbWUgbWlz dGFrZSBhcyB0aGVpcgpwcmVkZWNlc3NvcnMuCgpBaCB3ZWxsLiBTaW5jZSB0aGV5IGp1c3QgaW5m b3JtZWQgdGhlIHdob2xlIHdvcmxkLCB2aWEgcHVibGljIGxpc3RzLAphYm91dCB0aGVpciB2YWNh dGlvbiBpdCB3aWxsIG1ha2UgKnNvbWUqIHBlb3BsZSBoYXBweS4gTGlrZSBtYXJrZXRlZXJzLAph ZHZlcnRpc2VycyBhbmQgZXZlbiBidXJnbGFycyBJIHdhZ2VyLiA+OikKCl9fX19fX19fX19fX19f X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fClhlbi11c2VycyBtYWlsaW5nIGxpc3QK WGVuLXVzZXJzQGxpc3RzLnhlbi5vcmcKaHR0cDovL2xpc3RzLnhlbi5vcmcveGVuLXVzZXJz From xen-users-bounces@lists.xen.org Wed Sep 05 18:42:11 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Wed, 05 Sep 2012 18:42:11 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1T9KXI-0001xb-LJ; Wed, 05 Sep 2012 18:41:12 +0000 Received: from mail27.messagelabs.com ([193.109.254.147]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1T9KXG-0001xT-Nj for xen-users@lists.xen.org; Wed, 05 Sep 2012 18:41:10 +0000 X-Env-Sender: lists+xen@internecto.net X-Msg-Ref: server-13.tower-27.messagelabs.com!1346870463!8658617!1 X-Originating-IP: [176.9.245.29] X-SpamReason: No, hits=0.0 required=7.0 tests= X-StarScan-Received: X-StarScan-Version: 6.6.1.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 28058 invoked from network); 5 Sep 2012 18:41:03 -0000 Received: from polaris.internecto.net (HELO mx1.internecto.net) (176.9.245.29) by server-13.tower-27.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 5 Sep 2012 18:41:03 -0000 Received: from localhost (localhost [127.0.0.1]) by mx1.internecto.net (Postfix) with ESMTP id 59BC4A0086; Wed, 5 Sep 2012 18:41:03 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at mail.internecto.net Received: from mx1.internecto.net ([127.0.0.1]) by localhost (mail.polaris.internecto.net [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id G97dVGzG4FXO; Wed, 5 Sep 2012 18:41:01 +0000 (UTC) Received: from internecto.net (5ED4FDEB.cm-7-5d.dynamic.ziggo.nl [94.212.253.235]) (using TLSv1 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (Client did not present a certificate) (Authenticated sender: lists@internecto.net) by mx1.internecto.net (Postfix) with ESMTPSA id 0E682A0058; Wed, 5 Sep 2012 18:41:01 +0000 (UTC) Date: Wed, 5 Sep 2012 20:40:59 +0200 From: Mark van Dijk To: Massimo Canonico Message-ID: <20120905204059.2ef16c1b@internecto.net> In-Reply-To: <50477EF6.4070802@di.unipmn.it> References: <50477EF6.4070802@di.unipmn.it> Organization: Internecto SIS X-Mailer: Claws Mail 3.8.0 (GTK+ 2.24.10; x86_64-pc-linux-gnu) Mime-Version: 1.0 Cc: xen-users@lists.xen.org Subject: Re: [Xen-users] "xentop -b -i1" always returns 0 for cpuload X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org Quoting Massimo Canonico's message from 05 sep 2012: >Hi, >I need to save into a file the "cpu load" value for a specific domain >provided by "xentop" command. > >So I decided to write a very simple bash script: >while : >do > sudo xentop -b -i1 | grep | awk '{print $4}' > sleep 10 >done I remember back some years people talked about "cat abuse" when someone suggested to do "cat foo | grep bar". So I'll dub this "grep abuse" because awk can do what grep does, and much much more, especially in these instances. >The problem is that with "-i1" I always get 0.0 as output values, even >if when xentop (without "-b -i1") provides me the right cpu load >values. I can confirm this after having tested it myself. The first iteration of xentop has bogative values. >How can I fix this problem? Fixing this requires modifying xentop but you can work around it, awk to the rescue! What we want is the output from xentop's second iteration. Then, just let awk print that. while true; do xentop -b -i2 | awk '$1 == "VMname" && ++iter > 1 {print $4}' sleep 10s done The above awk says "if $1 exactly matches "VMname", and (iter+1) is more than one, print $4." If you want to match with a regular expression, replace the $1 == "VMname" with $1 ~ /regex/. You don't need the while loop at all by the way. xentop has a --delay=SECONDS (-d) parameter. So you could also opt to do: xentop -b -d 10 | awk '/VMname/ && ++iter > 1 {print $4}' I suppose the only downside of the second approach is that you have a 10 second delay at startup. HTH -Mark _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Wed Sep 05 18:42:11 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Wed, 05 Sep 2012 18:42:11 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1T9KXI-0001xb-LJ; Wed, 05 Sep 2012 18:41:12 +0000 Received: from mail27.messagelabs.com ([193.109.254.147]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1T9KXG-0001xT-Nj for xen-users@lists.xen.org; Wed, 05 Sep 2012 18:41:10 +0000 X-Env-Sender: lists+xen@internecto.net X-Msg-Ref: server-13.tower-27.messagelabs.com!1346870463!8658617!1 X-Originating-IP: [176.9.245.29] X-SpamReason: No, hits=0.0 required=7.0 tests= X-StarScan-Received: X-StarScan-Version: 6.6.1.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 28058 invoked from network); 5 Sep 2012 18:41:03 -0000 Received: from polaris.internecto.net (HELO mx1.internecto.net) (176.9.245.29) by server-13.tower-27.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 5 Sep 2012 18:41:03 -0000 Received: from localhost (localhost [127.0.0.1]) by mx1.internecto.net (Postfix) with ESMTP id 59BC4A0086; Wed, 5 Sep 2012 18:41:03 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at mail.internecto.net Received: from mx1.internecto.net ([127.0.0.1]) by localhost (mail.polaris.internecto.net [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id G97dVGzG4FXO; Wed, 5 Sep 2012 18:41:01 +0000 (UTC) Received: from internecto.net (5ED4FDEB.cm-7-5d.dynamic.ziggo.nl [94.212.253.235]) (using TLSv1 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (Client did not present a certificate) (Authenticated sender: lists@internecto.net) by mx1.internecto.net (Postfix) with ESMTPSA id 0E682A0058; Wed, 5 Sep 2012 18:41:01 +0000 (UTC) Date: Wed, 5 Sep 2012 20:40:59 +0200 From: Mark van Dijk To: Massimo Canonico Message-ID: <20120905204059.2ef16c1b@internecto.net> In-Reply-To: <50477EF6.4070802@di.unipmn.it> References: <50477EF6.4070802@di.unipmn.it> Organization: Internecto SIS X-Mailer: Claws Mail 3.8.0 (GTK+ 2.24.10; x86_64-pc-linux-gnu) Mime-Version: 1.0 Cc: xen-users@lists.xen.org Subject: Re: [Xen-users] "xentop -b -i1" always returns 0 for cpuload X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org Quoting Massimo Canonico's message from 05 sep 2012: >Hi, >I need to save into a file the "cpu load" value for a specific domain >provided by "xentop" command. > >So I decided to write a very simple bash script: >while : >do > sudo xentop -b -i1 | grep | awk '{print $4}' > sleep 10 >done I remember back some years people talked about "cat abuse" when someone suggested to do "cat foo | grep bar". So I'll dub this "grep abuse" because awk can do what grep does, and much much more, especially in these instances. >The problem is that with "-i1" I always get 0.0 as output values, even >if when xentop (without "-b -i1") provides me the right cpu load >values. I can confirm this after having tested it myself. The first iteration of xentop has bogative values. >How can I fix this problem? Fixing this requires modifying xentop but you can work around it, awk to the rescue! What we want is the output from xentop's second iteration. Then, just let awk print that. while true; do xentop -b -i2 | awk '$1 == "VMname" && ++iter > 1 {print $4}' sleep 10s done The above awk says "if $1 exactly matches "VMname", and (iter+1) is more than one, print $4." If you want to match with a regular expression, replace the $1 == "VMname" with $1 ~ /regex/. You don't need the while loop at all by the way. xentop has a --delay=SECONDS (-d) parameter. So you could also opt to do: xentop -b -d 10 | awk '/VMname/ && ++iter > 1 {print $4}' I suppose the only downside of the second approach is that you have a 10 second delay at startup. HTH -Mark _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Wed Sep 05 20:19:19 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Wed, 05 Sep 2012 20:19:19 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1T9M2v-00047r-Ct; Wed, 05 Sep 2012 20:17:57 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1T9M2t-00047l-V4 for xen-users@lists.xensource.com; Wed, 05 Sep 2012 20:17:56 +0000 Received: from [85.158.143.99:61458] by server-1.bemta-4.messagelabs.com id AF/45-12504-373B7405; Wed, 05 Sep 2012 20:17:55 +0000 X-Env-Sender: javier@guerrag.com X-Msg-Ref: server-11.tower-216.messagelabs.com!1346876273!21221373!1 X-Originating-IP: [209.85.160.43] X-SpamReason: No, hits=0.3 required=7.0 tests=RCVD_BY_IP X-StarScan-Received: X-StarScan-Version: 6.6.1.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 2277 invoked from network); 5 Sep 2012 20:17:54 -0000 Received: from mail-pb0-f43.google.com (HELO mail-pb0-f43.google.com) (209.85.160.43) by server-11.tower-216.messagelabs.com with RC4-SHA encrypted SMTP; 5 Sep 2012 20:17:54 -0000 Received: by pbbrq2 with SMTP id rq2so1810612pbb.30 for ; Wed, 05 Sep 2012 13:17:52 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:x-gm-message-state; bh=OtaAyfUEQky5X/fWXYgQITLolM2IHHd6cJg97Z4QWOo=; b=Rj/2NBNN3Ce/3zF89EJrAQnRNXo+kzOKv/P/CidOm5Xe15Z/+U2ZxS/frq8MoJy7Ji rCfUDvkvK7mX3cYw2/mk4tt2ou4SS2CoBLVv/FzyOb8EJwMTxS4zlYQf2/LqUgPTFaWn 8ZI6BxJZBAODusx0KSFpOasdByuM2XZ7/6098qiX8Zc3s6+xKcCOR6zbKOTtFIQaQxH7 PJSITbuhZsZI+YKYy3ZQwbyeEnn4mY0oZrCcwZK5BiHfC8dmj8gyI+tWJ4GjscPotZHn 3XzG0s6FXYe01rmLc1qqlSEpRLUa3gW0gwyI6eRHj90fUY2D626eq4y+SLxPx0Lfz8ZL nM7g== MIME-Version: 1.0 Received: by 10.68.217.100 with SMTP id ox4mr377047pbc.87.1346876272675; Wed, 05 Sep 2012 13:17:52 -0700 (PDT) Received: by 10.66.249.38 with HTTP; Wed, 5 Sep 2012 13:17:52 -0700 (PDT) In-Reply-To: <50475285.5090300@meetinghouse.net> References: <50475285.5090300@meetinghouse.net> Date: Wed, 5 Sep 2012 15:17:52 -0500 Message-ID: From: Javier Guerra Giraldez To: Miles Fidelman X-Gm-Message-State: ALoCoQl9tEHGFhn0xBTz9Lo8BiAgQtMHEYfc1iVdjL2qaeGhgFbokhIrG6ntZj+y3ZtG3PP9V0tB Cc: "xen-users@lists.xensource.com" Subject: Re: [Xen-users] xen + gluster: recent experiences? X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org On Wed, Sep 5, 2012 at 8:24 AM, Miles Fidelman wrote: > Anybody have any recent experiences building a small cluster with Xen and > Gluster? I've been getting ready to move from a 2-node HA cluster (using > DRBD) to a 4-node cluster. Sort of been tracking the maturity of Gluster as > a replacement for DRBD. Any comments? on a related theme, it would also be great if there's any recent experiences with VastSky[1]... at some point, it was included in XCP, but I can't find if there's been any further development. [1]: http://sourceforge.net/apps/mediawiki/vastsky -- Javier _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Wed Sep 05 20:19:19 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Wed, 05 Sep 2012 20:19:19 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1T9M2v-00047r-Ct; Wed, 05 Sep 2012 20:17:57 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1T9M2t-00047l-V4 for xen-users@lists.xensource.com; Wed, 05 Sep 2012 20:17:56 +0000 Received: from [85.158.143.99:61458] by server-1.bemta-4.messagelabs.com id AF/45-12504-373B7405; Wed, 05 Sep 2012 20:17:55 +0000 X-Env-Sender: javier@guerrag.com X-Msg-Ref: server-11.tower-216.messagelabs.com!1346876273!21221373!1 X-Originating-IP: [209.85.160.43] X-SpamReason: No, hits=0.3 required=7.0 tests=RCVD_BY_IP X-StarScan-Received: X-StarScan-Version: 6.6.1.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 2277 invoked from network); 5 Sep 2012 20:17:54 -0000 Received: from mail-pb0-f43.google.com (HELO mail-pb0-f43.google.com) (209.85.160.43) by server-11.tower-216.messagelabs.com with RC4-SHA encrypted SMTP; 5 Sep 2012 20:17:54 -0000 Received: by pbbrq2 with SMTP id rq2so1810612pbb.30 for ; Wed, 05 Sep 2012 13:17:52 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:x-gm-message-state; bh=OtaAyfUEQky5X/fWXYgQITLolM2IHHd6cJg97Z4QWOo=; b=Rj/2NBNN3Ce/3zF89EJrAQnRNXo+kzOKv/P/CidOm5Xe15Z/+U2ZxS/frq8MoJy7Ji rCfUDvkvK7mX3cYw2/mk4tt2ou4SS2CoBLVv/FzyOb8EJwMTxS4zlYQf2/LqUgPTFaWn 8ZI6BxJZBAODusx0KSFpOasdByuM2XZ7/6098qiX8Zc3s6+xKcCOR6zbKOTtFIQaQxH7 PJSITbuhZsZI+YKYy3ZQwbyeEnn4mY0oZrCcwZK5BiHfC8dmj8gyI+tWJ4GjscPotZHn 3XzG0s6FXYe01rmLc1qqlSEpRLUa3gW0gwyI6eRHj90fUY2D626eq4y+SLxPx0Lfz8ZL nM7g== MIME-Version: 1.0 Received: by 10.68.217.100 with SMTP id ox4mr377047pbc.87.1346876272675; Wed, 05 Sep 2012 13:17:52 -0700 (PDT) Received: by 10.66.249.38 with HTTP; Wed, 5 Sep 2012 13:17:52 -0700 (PDT) In-Reply-To: <50475285.5090300@meetinghouse.net> References: <50475285.5090300@meetinghouse.net> Date: Wed, 5 Sep 2012 15:17:52 -0500 Message-ID: From: Javier Guerra Giraldez To: Miles Fidelman X-Gm-Message-State: ALoCoQl9tEHGFhn0xBTz9Lo8BiAgQtMHEYfc1iVdjL2qaeGhgFbokhIrG6ntZj+y3ZtG3PP9V0tB Cc: "xen-users@lists.xensource.com" Subject: Re: [Xen-users] xen + gluster: recent experiences? X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org On Wed, Sep 5, 2012 at 8:24 AM, Miles Fidelman wrote: > Anybody have any recent experiences building a small cluster with Xen and > Gluster? I've been getting ready to move from a 2-node HA cluster (using > DRBD) to a 4-node cluster. Sort of been tracking the maturity of Gluster as > a replacement for DRBD. Any comments? on a related theme, it would also be great if there's any recent experiences with VastSky[1]... at some point, it was included in XCP, but I can't find if there's been any further development. [1]: http://sourceforge.net/apps/mediawiki/vastsky -- Javier _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Wed Sep 05 20:58:46 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Wed, 05 Sep 2012 20:58:46 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1T9MfD-0005GL-NB; Wed, 05 Sep 2012 20:57:31 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1T9MfC-0005GD-Ak for Xen-users@lists.xen.org; Wed, 05 Sep 2012 20:57:30 +0000 Received: from [85.158.138.51:31291] by server-5.bemta-3.messagelabs.com id ED/61-13133-9BCB7405; Wed, 05 Sep 2012 20:57:29 +0000 X-Env-Sender: andy@strugglers.net X-Msg-Ref: server-10.tower-174.messagelabs.com!1346878648!24837549!1 X-Originating-IP: [85.119.80.223] X-SpamReason: No, hits=0.0 required=7.0 tests= X-StarScan-Received: X-StarScan-Version: 6.6.1.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 4234 invoked from network); 5 Sep 2012 20:57:29 -0000 Received: from bitfolk.com (HELO mail.bitfolk.com) (85.119.80.223) by server-10.tower-174.messagelabs.com with AES256-SHA encrypted SMTP; 5 Sep 2012 20:57:29 -0000 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=bitfolk.com; s=alpha; h=Subject:In-Reply-To:Content-Transfer-Encoding:Content-Type:MIME-Version:References:Message-ID:To:From:Date; bh=57PH5L64oD12l5xK8brk9Z/2If975eiGAs42RnRrEC0=; b=0fnbHs4Tv5tEJYMBGWonO5BgEg3vuNnwy4qsHK91nfzy8NLZNNo3Bmj5ytALbWrXspAa0MAE0q9zOOyTP3cqb4GHdNgOouFCn0pDoBEl9YWMxsNpyJjC9V8thbFe04gb; Received: from andy by mail.bitfolk.com with local (Exim 4.72) (envelope-from ) id 1T9MfA-0001wv-Gs for Xen-users@lists.xen.org; Wed, 05 Sep 2012 20:57:28 +0000 Date: Wed, 5 Sep 2012 20:57:28 +0000 From: Andy Smith To: Xen-users Message-ID: <20120905205728.GE3867@bitfolk.com> References: <20120905125308.24ba4f58@internecto.net> MIME-Version: 1.0 Content-Disposition: inline In-Reply-To: <20120905125308.24ba4f58@internecto.net> OpenPGP: id=BF15490B; url=http://strugglers.net/~andy/pubkey.asc X-URL: http://strugglers.net/wiki/User:Andy User-Agent: Mutt/1.5.20 (2009-06-14) X-Virus-Scanner: Scanned by ClamAV on mail.bitfolk.com at Wed, 05 Sep 2012 20:57:28 +0000 X-SA-Exim-Connect-IP: X-SA-Exim-Mail-From: andy@strugglers.net X-Spam-Checker-Version: SpamAssassin 3.3.1 (2010-03-16) on spamd2.lon.bitfolk.com X-Spam-Level: X-Spam-ASN: X-Spam-Status: No, score=-0.0 required=5.0 tests=NO_RELAYS shortcircuit=no autolearn=disabled version=3.3.1 X-Spam-Report: * -0.0 NO_RELAYS Informational: message was not relayed via SMTP X-SA-Exim-Version: 4.2.1 (built Mon, 22 Mar 2010 06:51:10 +0000) X-SA-Exim-Scanned: Yes (on mail.bitfolk.com) Subject: Re: [Xen-users] Sharing entropy across VMs X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: base64 Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org SGkgTWFyaywKCk9uIFdlZCwgU2VwIDA1LCAyMDEyIGF0IDEyOjUzOjA4UE0gKzAyMDAsIE1hcmsg dmFuIERpamsgd3JvdGU6Cj4gU2hvcnQgcXVlc3Rpb246IGlzIGl0IHBvc3NpYmxlIHRvIHNoYXJl IGVudHJvcHkgYWNyb3NzIGFsbCBWTXMgYW5kIGhvdwo+IGNhbiB0aGlzIGJlIGRvbmU/CgpJIGhh dmUgYmVlbiBkb2luZyBpdCB3aXRoIGFuIEVudHJvcHkgS2V5OgoKaHR0cDovL3d3dy5lbnRyb3B5 a2V5LmNvLnVrLwoKVGhleSBoYXZlIHBhY2thZ2VkIHNvZnR3YXJlIGZvciBEZWJpYW4gYW5kIFVi dW50dSB3aGljaCBpbmNsdWRlcyBhCmRhZW1vbiBjYWxsZWQgZWtleWQuIGVrZXlkIHdvdWxkIHVz dWFsbHkgYmUgY29uZmlndXJlZCB0byBzdHVmZiB0aGUKZW50cm9weSBpdCBnZXRzIGZyb20gdGhl IGtleSBpbnRvIHRoZSBrZXJuZWwncyBlbnRyb3B5IHBvb2wsIGJ1dCB5b3UKY2FuIGNvbmZpZ3Vy ZSBpdCBpbnN0ZWFkIHRvIHNlcnZlIHRoZSBlbnRyb3B5IG91dCB1c2luZyB0aGUgRUdECnByb3Rv Y29sLgoKVGhleSBhbHNvIGhhdmUgYSBtb2RpZmllZCBFR0QgY2xpZW50IGNhbGxlZCBla2V5ZC1l Z2QtbGludXggd2hpY2gKdGFsa3MgdG8gZWtleWQgb3ZlciB0aGUgbmV0d29yayBhbmQgc3R1ZmZz IHRoYXQgZW50cm9weSBpbnRvIHRoZQpsb2NhbCBrZXJuZWwgZW50cm9weSBwb29sLgoKU28sIGVr ZXlkLWVnZC1saW51eCBvbiBlYWNoIGNsaWVudCBtYWNoaW5lLCB0YWxraW5nIHRvIGVrZXlkIG9u IG9uZQpvciBtb3JlIGhvc3RzIHdpdGggZW50cm9weSBrZXlzLgoKSXQncyBhIHBpdHkgdGhhdCB0 aGVyZSBzZWVtcyBubyB3YXkgd2l0aGluIFhlbiB0byBnZXQgdGhlIGVudHJvcHkKZnJvbSB0aGUg ZG9tMCBrZXJuZWwgaW50byBlYWNoIGRvbVUuIEtWTSBoYXMgdGhpcyBmZWF0dXJlIGRvZXNuJ3QK aXQ/IFRoYXQgd291bGQgc2F2ZSBtZSBoYXZpbmcgdG8gcnVuIGFuIGVrZXlkLWVnZC1saW51eCBv biBlYWNoCmRvbVUuCgpDaGVlcnMsCkFuZHkKCi0tIAo+IFRoZSBvcHRpbXVtIHByb2dyYW1taW5n IHRlYW0gc2l6ZSBpcyAxLgpIYXMgSnVyYXNzaWMgUGFyayB0YXVnaHQgdXMgbm90aGluZz8KIOKA lCBwZmlsYW5kcgoKX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19f X18KWGVuLXVzZXJzIG1haWxpbmcgbGlzdApYZW4tdXNlcnNAbGlzdHMueGVuLm9yZwpodHRwOi8v bGlzdHMueGVuLm9yZy94ZW4tdXNlcnM= From xen-users-bounces@lists.xen.org Wed Sep 05 20:58:46 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Wed, 05 Sep 2012 20:58:46 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1T9MfD-0005GL-NB; Wed, 05 Sep 2012 20:57:31 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1T9MfC-0005GD-Ak for Xen-users@lists.xen.org; Wed, 05 Sep 2012 20:57:30 +0000 Received: from [85.158.138.51:31291] by server-5.bemta-3.messagelabs.com id ED/61-13133-9BCB7405; Wed, 05 Sep 2012 20:57:29 +0000 X-Env-Sender: andy@strugglers.net X-Msg-Ref: server-10.tower-174.messagelabs.com!1346878648!24837549!1 X-Originating-IP: [85.119.80.223] X-SpamReason: No, hits=0.0 required=7.0 tests= X-StarScan-Received: X-StarScan-Version: 6.6.1.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 4234 invoked from network); 5 Sep 2012 20:57:29 -0000 Received: from bitfolk.com (HELO mail.bitfolk.com) (85.119.80.223) by server-10.tower-174.messagelabs.com with AES256-SHA encrypted SMTP; 5 Sep 2012 20:57:29 -0000 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=bitfolk.com; s=alpha; h=Subject:In-Reply-To:Content-Transfer-Encoding:Content-Type:MIME-Version:References:Message-ID:To:From:Date; bh=57PH5L64oD12l5xK8brk9Z/2If975eiGAs42RnRrEC0=; b=0fnbHs4Tv5tEJYMBGWonO5BgEg3vuNnwy4qsHK91nfzy8NLZNNo3Bmj5ytALbWrXspAa0MAE0q9zOOyTP3cqb4GHdNgOouFCn0pDoBEl9YWMxsNpyJjC9V8thbFe04gb; Received: from andy by mail.bitfolk.com with local (Exim 4.72) (envelope-from ) id 1T9MfA-0001wv-Gs for Xen-users@lists.xen.org; Wed, 05 Sep 2012 20:57:28 +0000 Date: Wed, 5 Sep 2012 20:57:28 +0000 From: Andy Smith To: Xen-users Message-ID: <20120905205728.GE3867@bitfolk.com> References: <20120905125308.24ba4f58@internecto.net> MIME-Version: 1.0 Content-Disposition: inline In-Reply-To: <20120905125308.24ba4f58@internecto.net> OpenPGP: id=BF15490B; url=http://strugglers.net/~andy/pubkey.asc X-URL: http://strugglers.net/wiki/User:Andy User-Agent: Mutt/1.5.20 (2009-06-14) X-Virus-Scanner: Scanned by ClamAV on mail.bitfolk.com at Wed, 05 Sep 2012 20:57:28 +0000 X-SA-Exim-Connect-IP: X-SA-Exim-Mail-From: andy@strugglers.net X-Spam-Checker-Version: SpamAssassin 3.3.1 (2010-03-16) on spamd2.lon.bitfolk.com X-Spam-Level: X-Spam-ASN: X-Spam-Status: No, score=-0.0 required=5.0 tests=NO_RELAYS shortcircuit=no autolearn=disabled version=3.3.1 X-Spam-Report: * -0.0 NO_RELAYS Informational: message was not relayed via SMTP X-SA-Exim-Version: 4.2.1 (built Mon, 22 Mar 2010 06:51:10 +0000) X-SA-Exim-Scanned: Yes (on mail.bitfolk.com) Subject: Re: [Xen-users] Sharing entropy across VMs X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: base64 Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org SGkgTWFyaywKCk9uIFdlZCwgU2VwIDA1LCAyMDEyIGF0IDEyOjUzOjA4UE0gKzAyMDAsIE1hcmsg dmFuIERpamsgd3JvdGU6Cj4gU2hvcnQgcXVlc3Rpb246IGlzIGl0IHBvc3NpYmxlIHRvIHNoYXJl IGVudHJvcHkgYWNyb3NzIGFsbCBWTXMgYW5kIGhvdwo+IGNhbiB0aGlzIGJlIGRvbmU/CgpJIGhh dmUgYmVlbiBkb2luZyBpdCB3aXRoIGFuIEVudHJvcHkgS2V5OgoKaHR0cDovL3d3dy5lbnRyb3B5 a2V5LmNvLnVrLwoKVGhleSBoYXZlIHBhY2thZ2VkIHNvZnR3YXJlIGZvciBEZWJpYW4gYW5kIFVi dW50dSB3aGljaCBpbmNsdWRlcyBhCmRhZW1vbiBjYWxsZWQgZWtleWQuIGVrZXlkIHdvdWxkIHVz dWFsbHkgYmUgY29uZmlndXJlZCB0byBzdHVmZiB0aGUKZW50cm9weSBpdCBnZXRzIGZyb20gdGhl IGtleSBpbnRvIHRoZSBrZXJuZWwncyBlbnRyb3B5IHBvb2wsIGJ1dCB5b3UKY2FuIGNvbmZpZ3Vy ZSBpdCBpbnN0ZWFkIHRvIHNlcnZlIHRoZSBlbnRyb3B5IG91dCB1c2luZyB0aGUgRUdECnByb3Rv Y29sLgoKVGhleSBhbHNvIGhhdmUgYSBtb2RpZmllZCBFR0QgY2xpZW50IGNhbGxlZCBla2V5ZC1l Z2QtbGludXggd2hpY2gKdGFsa3MgdG8gZWtleWQgb3ZlciB0aGUgbmV0d29yayBhbmQgc3R1ZmZz IHRoYXQgZW50cm9weSBpbnRvIHRoZQpsb2NhbCBrZXJuZWwgZW50cm9weSBwb29sLgoKU28sIGVr ZXlkLWVnZC1saW51eCBvbiBlYWNoIGNsaWVudCBtYWNoaW5lLCB0YWxraW5nIHRvIGVrZXlkIG9u IG9uZQpvciBtb3JlIGhvc3RzIHdpdGggZW50cm9weSBrZXlzLgoKSXQncyBhIHBpdHkgdGhhdCB0 aGVyZSBzZWVtcyBubyB3YXkgd2l0aGluIFhlbiB0byBnZXQgdGhlIGVudHJvcHkKZnJvbSB0aGUg ZG9tMCBrZXJuZWwgaW50byBlYWNoIGRvbVUuIEtWTSBoYXMgdGhpcyBmZWF0dXJlIGRvZXNuJ3QK aXQ/IFRoYXQgd291bGQgc2F2ZSBtZSBoYXZpbmcgdG8gcnVuIGFuIGVrZXlkLWVnZC1saW51eCBv biBlYWNoCmRvbVUuCgpDaGVlcnMsCkFuZHkKCi0tIAo+IFRoZSBvcHRpbXVtIHByb2dyYW1taW5n IHRlYW0gc2l6ZSBpcyAxLgpIYXMgSnVyYXNzaWMgUGFyayB0YXVnaHQgdXMgbm90aGluZz8KIOKA lCBwZmlsYW5kcgoKX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19f X18KWGVuLXVzZXJzIG1haWxpbmcgbGlzdApYZW4tdXNlcnNAbGlzdHMueGVuLm9yZwpodHRwOi8v bGlzdHMueGVuLm9yZy94ZW4tdXNlcnM= From xen-users-bounces@lists.xen.org Wed Sep 05 21:04:52 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Wed, 05 Sep 2012 21:04:52 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1T9MlO-0005ad-Q6; Wed, 05 Sep 2012 21:03:54 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1T9MGf-0004ar-0V for xen-users@lists.xen.org; Wed, 05 Sep 2012 20:32:09 +0000 Received: from [85.158.143.35:62520] by server-1.bemta-4.messagelabs.com id 79/7D-12504-7C6B7405; Wed, 05 Sep 2012 20:32:07 +0000 X-Env-Sender: msw@amazon.com X-Msg-Ref: server-7.tower-21.messagelabs.com!1346877120!12413963!1 X-Originating-IP: [207.171.178.25] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogMjA3LjE3MS4xNzguMjUgPT4gNjU1MTM=\n X-StarScan-Received: X-StarScan-Version: 6.6.1.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 7492 invoked from network); 5 Sep 2012 20:32:03 -0000 Received: from smtp-fw-31001.amazon.com (HELO smtp-fw-31001.amazon.com) (207.171.178.25) by server-7.tower-21.messagelabs.com with RC4-SHA encrypted SMTP; 5 Sep 2012 20:32:03 -0000 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=amazon.com; i=msw@amazon.com; q=dns/txt; s=rte02; t=1346877122; x=1378413122; h=date:from:to:cc:subject:message-id:references: mime-version:in-reply-to; bh=weYfTFCljrbFAUUawEUS2pPVdOSV9Qrhfomfs+TD0Lg=; b=luHWZOnqD+YpimcShgPtMLGHm/31aLwemXKqQhlOAz+nFGw9T5pRU8Zi Pl3zK+kTZiUntVOa3iQC8LVZrJsNcQ==; X-IronPort-AV: E=Sophos;i="4.80,376,1344211200"; d="scan'208";a="289914386" Received: from smtp-in-0102.sea3.amazon.com ([10.224.19.46]) by smtp-border-fw-out-31001.sea31.amazon.com with ESMTP/TLS/DHE-RSA-AES256-SHA; 05 Sep 2012 20:31:58 +0000 Received: from ex10-hub-9003.ant.amazon.com (ex10-hub-9003.ant.amazon.com [10.185.137.132]) by smtp-in-0102.sea3.amazon.com (8.13.8/8.13.8) with ESMTP id q85KVvJk006258 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Wed, 5 Sep 2012 20:31:58 GMT Received: from u002268147cd4502c336d.ant.amazon.com (10.224.80.34) by ex10-hub-9003.ant.amazon.com (10.185.137.132) with Microsoft SMTP Server id 14.2.247.3; Wed, 5 Sep 2012 13:31:52 -0700 Received: by u002268147cd4502c336d.ant.amazon.com (sSMTP sendmail emulation); Wed, 05 Sep 2012 13:31:55 -0700 Date: Wed, 5 Sep 2012 13:31:55 -0700 From: Matt Wilson To: Mark van Dijk Message-ID: <20120905203153.GA26680@u002268147cd4502c336d.ant.amazon.com> References: <1346665360.25864.2.camel@zakaz.uk.xensource.com> <20120905152926.GM8912@reaktio.net> <20120905195307.101d0cbc@internecto.net> MIME-Version: 1.0 Content-Disposition: inline In-Reply-To: <20120905195307.101d0cbc@internecto.net> User-Agent: Mutt/1.5.21 (2010-09-15) X-Mailman-Approved-At: Wed, 05 Sep 2012 21:03:53 +0000 Cc: xen-users@lists.xen.org, xen-devel Subject: Re: [Xen-users] [Xen-devel] Xen 4.2.0 Release Plan / TODO X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org On Wed, Sep 05, 2012 at 07:53:07PM +0200, Mark van Dijk wrote: > >> tools, nice to have: > > > > * pygrub support for ext4 on rhel5/centos5. > > Roger already sent a patch for this. > > I'd love to see some kind of extlinux (or grub2) that can replace the > current pv-grub. Both support ext4 and, more importantly imho, > btrfs, now that is one really cool filesystem. Personally I'd love to see pv-extlinux. I chatted last week with some folks at the Linux Plumbers Conference about this, and I think it should be possible with a lot of work. > Grub0.97 is/will be being deprecated on an increasing number of > distributions. And pv-grub is safer than pygrub because pygrub executes > in the dom0 and pv-grub in the domU, if I understand correctly. > > Anyone willing to share thoughts on the possibility of 'pv-extlinux?' I believe that syslinux only builds as 32-bit, and the elf output is only an intermediate build target. Booting a 64-bit kernel with a 32-bit pv-extlinux won't work. Also, I'm not sure that you could load the .elf output and do anything useful with it. I've heard a rumor that a pure-C syslinux version is in the works, which could help with this. syslinux has a really decent subset of the standard C library in com32/, and implementing the frontend drivers with it shouldn't not be too hard. Building libxc against it might be another matter entirely. GRUB2 is currently more popular than extlinux I think, and it might lend itself to a PV port more readily. There was some initial work that made grub-emu run on top of MiniOS [1], but I'm not sure that it got much farther than that. Matt [1] http://lists.xen.org/archives/html/xen-devel/2009-05/msg00666.html _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Wed Sep 05 21:04:52 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Wed, 05 Sep 2012 21:04:52 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1T9MlO-0005ad-Q6; Wed, 05 Sep 2012 21:03:54 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1T9MGf-0004ar-0V for xen-users@lists.xen.org; Wed, 05 Sep 2012 20:32:09 +0000 Received: from [85.158.143.35:62520] by server-1.bemta-4.messagelabs.com id 79/7D-12504-7C6B7405; Wed, 05 Sep 2012 20:32:07 +0000 X-Env-Sender: msw@amazon.com X-Msg-Ref: server-7.tower-21.messagelabs.com!1346877120!12413963!1 X-Originating-IP: [207.171.178.25] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogMjA3LjE3MS4xNzguMjUgPT4gNjU1MTM=\n X-StarScan-Received: X-StarScan-Version: 6.6.1.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 7492 invoked from network); 5 Sep 2012 20:32:03 -0000 Received: from smtp-fw-31001.amazon.com (HELO smtp-fw-31001.amazon.com) (207.171.178.25) by server-7.tower-21.messagelabs.com with RC4-SHA encrypted SMTP; 5 Sep 2012 20:32:03 -0000 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=amazon.com; i=msw@amazon.com; q=dns/txt; s=rte02; t=1346877122; x=1378413122; h=date:from:to:cc:subject:message-id:references: mime-version:in-reply-to; bh=weYfTFCljrbFAUUawEUS2pPVdOSV9Qrhfomfs+TD0Lg=; b=luHWZOnqD+YpimcShgPtMLGHm/31aLwemXKqQhlOAz+nFGw9T5pRU8Zi Pl3zK+kTZiUntVOa3iQC8LVZrJsNcQ==; X-IronPort-AV: E=Sophos;i="4.80,376,1344211200"; d="scan'208";a="289914386" Received: from smtp-in-0102.sea3.amazon.com ([10.224.19.46]) by smtp-border-fw-out-31001.sea31.amazon.com with ESMTP/TLS/DHE-RSA-AES256-SHA; 05 Sep 2012 20:31:58 +0000 Received: from ex10-hub-9003.ant.amazon.com (ex10-hub-9003.ant.amazon.com [10.185.137.132]) by smtp-in-0102.sea3.amazon.com (8.13.8/8.13.8) with ESMTP id q85KVvJk006258 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Wed, 5 Sep 2012 20:31:58 GMT Received: from u002268147cd4502c336d.ant.amazon.com (10.224.80.34) by ex10-hub-9003.ant.amazon.com (10.185.137.132) with Microsoft SMTP Server id 14.2.247.3; Wed, 5 Sep 2012 13:31:52 -0700 Received: by u002268147cd4502c336d.ant.amazon.com (sSMTP sendmail emulation); Wed, 05 Sep 2012 13:31:55 -0700 Date: Wed, 5 Sep 2012 13:31:55 -0700 From: Matt Wilson To: Mark van Dijk Message-ID: <20120905203153.GA26680@u002268147cd4502c336d.ant.amazon.com> References: <1346665360.25864.2.camel@zakaz.uk.xensource.com> <20120905152926.GM8912@reaktio.net> <20120905195307.101d0cbc@internecto.net> MIME-Version: 1.0 Content-Disposition: inline In-Reply-To: <20120905195307.101d0cbc@internecto.net> User-Agent: Mutt/1.5.21 (2010-09-15) X-Mailman-Approved-At: Wed, 05 Sep 2012 21:03:53 +0000 Cc: xen-users@lists.xen.org, xen-devel Subject: Re: [Xen-users] [Xen-devel] Xen 4.2.0 Release Plan / TODO X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org On Wed, Sep 05, 2012 at 07:53:07PM +0200, Mark van Dijk wrote: > >> tools, nice to have: > > > > * pygrub support for ext4 on rhel5/centos5. > > Roger already sent a patch for this. > > I'd love to see some kind of extlinux (or grub2) that can replace the > current pv-grub. Both support ext4 and, more importantly imho, > btrfs, now that is one really cool filesystem. Personally I'd love to see pv-extlinux. I chatted last week with some folks at the Linux Plumbers Conference about this, and I think it should be possible with a lot of work. > Grub0.97 is/will be being deprecated on an increasing number of > distributions. And pv-grub is safer than pygrub because pygrub executes > in the dom0 and pv-grub in the domU, if I understand correctly. > > Anyone willing to share thoughts on the possibility of 'pv-extlinux?' I believe that syslinux only builds as 32-bit, and the elf output is only an intermediate build target. Booting a 64-bit kernel with a 32-bit pv-extlinux won't work. Also, I'm not sure that you could load the .elf output and do anything useful with it. I've heard a rumor that a pure-C syslinux version is in the works, which could help with this. syslinux has a really decent subset of the standard C library in com32/, and implementing the frontend drivers with it shouldn't not be too hard. Building libxc against it might be another matter entirely. GRUB2 is currently more popular than extlinux I think, and it might lend itself to a PV port more readily. There was some initial work that made grub-emu run on top of MiniOS [1], but I'm not sure that it got much farther than that. Matt [1] http://lists.xen.org/archives/html/xen-devel/2009-05/msg00666.html _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Thu Sep 06 08:58:20 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Thu, 06 Sep 2012 08:58:20 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1T9XtJ-00028p-BX; Thu, 06 Sep 2012 08:56:49 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1T9XtH-00028N-Ck for xen-users@lists.xen.org; Thu, 06 Sep 2012 08:56:47 +0000 Received: from [85.158.143.35:60558] by server-1.bemta-4.messagelabs.com id 70/E2-12504-E4568405; Thu, 06 Sep 2012 08:56:46 +0000 X-Env-Sender: Ian.Campbell@citrix.com X-Msg-Ref: server-7.tower-21.messagelabs.com!1346921804!12497002!1 X-Originating-IP: [62.200.22.115] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogNjIuMjAwLjIyLjExNSA9PiAxMTE5NzY=\n X-StarScan-Received: X-StarScan-Version: 6.6.1.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 2094 invoked from network); 6 Sep 2012 08:56:44 -0000 Received: from smtp.eu.citrix.com (HELO SMTP.EU.CITRIX.COM) (62.200.22.115) by server-7.tower-21.messagelabs.com with RC4-SHA encrypted SMTP; 6 Sep 2012 08:56:44 -0000 X-IronPort-AV: E=Sophos;i="4.80,379,1344211200"; d="scan'208";a="14378549" Received: from lonpmailmx01.citrite.net ([10.30.203.162]) by LONPIPO01.EU.CITRIX.COM with ESMTP/TLS/RC4-MD5; 06 Sep 2012 08:56:44 +0000 Received: from [10.80.2.42] (10.80.2.42) by LONPMAILMX01.citrite.net (10.30.203.162) with Microsoft SMTP Server id 8.3.279.1; Thu, 6 Sep 2012 09:56:44 +0100 Message-ID: <1346921802.23055.26.camel@zakaz.uk.xensource.com> From: Ian Campbell To: kk s Date: Thu, 6 Sep 2012 09:56:42 +0100 In-Reply-To: References: Organization: Citrix Systems, Inc. X-Mailer: Evolution 3.4.3-1 MIME-Version: 1.0 Cc: "xen-users@lists.xen.org" , "xen-devel@lists.xen.org" Subject: Re: [Xen-users] [Xen-devel] Security patches X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org On Thu, 2012-09-06 at 09:31 +0100, kk s wrote: > Hi, > > Can anyone give the patch file download link for the below xen > security for xen version 3.4 and 4.1? Since I couldn't find the > downloadable patch file for some of the CVE's. > > CVE-2012-0029 - http://lists.xen.org/archives/html/xen-devel/2012-02/msg00212.html (There is no download link for both xen 3.4 and 4.1) > CVE-2012-2934 - http://lists.xen.org/archives/html/xen-announce/2012-06/msg00002.html (There is no patch file to download of xen 3.4) > CVE-2012-3432 - http://lists.xen.org/archives/html/xen-devel/2012-07/msg01649.html (There is no download link for both xen 3.4 and 4.1) > CVE-2012-3433 - http://lists.xen.org/archives/html/xen-devel/2012-08/msg00855.html (There is no download link for both xen 3.4 and 4.1) It looks to me like there are changeset references and/or patches for all of these in the advisories. You might find it easier to follow: http://wiki.xen.org/wiki/Security_Announcements You can also always look in the appropriate xen-X.Y-testing.hg tree for the fix. > CVE-2012-3497 - http://lists.xen.org/archives/html/xen-announce/2012-09/msg00006.html (There is no download link for patch) This is quite clearly explained in the advisory. > Also I have some doubts for the below CVE's. > > CVE-2012-3496 - Is this vulnerability affected for xen 4.x only or it > does include for xen 3.4 too? Since the patch name was > xsa14-xen-3.4-and-4.x.patch > http://lists.xen.org/archives/html/xen-announce/2012-09/msg00002.html Yes, it looks like this effects 3.4 too. > CVE-2012-3516 - Shall I apply this unstable for patch for xen4.2 too? > http://lists.xen.org/archives/html/xen-announce/2012-09/msg00004.html The advisory says "Xen-unstable, including Xen 4.2 release candidates are vulnerable to this issue.", so yes, obviously. In the future please carefully read the advisories before asking lots of questions, almost everything you have asked is addressed in the advisory texts AFAICT. Ian. _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Thu Sep 06 08:58:20 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Thu, 06 Sep 2012 08:58:20 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1T9XtJ-00028p-BX; Thu, 06 Sep 2012 08:56:49 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1T9XtH-00028N-Ck for xen-users@lists.xen.org; Thu, 06 Sep 2012 08:56:47 +0000 Received: from [85.158.143.35:60558] by server-1.bemta-4.messagelabs.com id 70/E2-12504-E4568405; Thu, 06 Sep 2012 08:56:46 +0000 X-Env-Sender: Ian.Campbell@citrix.com X-Msg-Ref: server-7.tower-21.messagelabs.com!1346921804!12497002!1 X-Originating-IP: [62.200.22.115] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogNjIuMjAwLjIyLjExNSA9PiAxMTE5NzY=\n X-StarScan-Received: X-StarScan-Version: 6.6.1.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 2094 invoked from network); 6 Sep 2012 08:56:44 -0000 Received: from smtp.eu.citrix.com (HELO SMTP.EU.CITRIX.COM) (62.200.22.115) by server-7.tower-21.messagelabs.com with RC4-SHA encrypted SMTP; 6 Sep 2012 08:56:44 -0000 X-IronPort-AV: E=Sophos;i="4.80,379,1344211200"; d="scan'208";a="14378549" Received: from lonpmailmx01.citrite.net ([10.30.203.162]) by LONPIPO01.EU.CITRIX.COM with ESMTP/TLS/RC4-MD5; 06 Sep 2012 08:56:44 +0000 Received: from [10.80.2.42] (10.80.2.42) by LONPMAILMX01.citrite.net (10.30.203.162) with Microsoft SMTP Server id 8.3.279.1; Thu, 6 Sep 2012 09:56:44 +0100 Message-ID: <1346921802.23055.26.camel@zakaz.uk.xensource.com> From: Ian Campbell To: kk s Date: Thu, 6 Sep 2012 09:56:42 +0100 In-Reply-To: References: Organization: Citrix Systems, Inc. X-Mailer: Evolution 3.4.3-1 MIME-Version: 1.0 Cc: "xen-users@lists.xen.org" , "xen-devel@lists.xen.org" Subject: Re: [Xen-users] [Xen-devel] Security patches X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org On Thu, 2012-09-06 at 09:31 +0100, kk s wrote: > Hi, > > Can anyone give the patch file download link for the below xen > security for xen version 3.4 and 4.1? Since I couldn't find the > downloadable patch file for some of the CVE's. > > CVE-2012-0029 - http://lists.xen.org/archives/html/xen-devel/2012-02/msg00212.html (There is no download link for both xen 3.4 and 4.1) > CVE-2012-2934 - http://lists.xen.org/archives/html/xen-announce/2012-06/msg00002.html (There is no patch file to download of xen 3.4) > CVE-2012-3432 - http://lists.xen.org/archives/html/xen-devel/2012-07/msg01649.html (There is no download link for both xen 3.4 and 4.1) > CVE-2012-3433 - http://lists.xen.org/archives/html/xen-devel/2012-08/msg00855.html (There is no download link for both xen 3.4 and 4.1) It looks to me like there are changeset references and/or patches for all of these in the advisories. You might find it easier to follow: http://wiki.xen.org/wiki/Security_Announcements You can also always look in the appropriate xen-X.Y-testing.hg tree for the fix. > CVE-2012-3497 - http://lists.xen.org/archives/html/xen-announce/2012-09/msg00006.html (There is no download link for patch) This is quite clearly explained in the advisory. > Also I have some doubts for the below CVE's. > > CVE-2012-3496 - Is this vulnerability affected for xen 4.x only or it > does include for xen 3.4 too? Since the patch name was > xsa14-xen-3.4-and-4.x.patch > http://lists.xen.org/archives/html/xen-announce/2012-09/msg00002.html Yes, it looks like this effects 3.4 too. > CVE-2012-3516 - Shall I apply this unstable for patch for xen4.2 too? > http://lists.xen.org/archives/html/xen-announce/2012-09/msg00004.html The advisory says "Xen-unstable, including Xen 4.2 release candidates are vulnerable to this issue.", so yes, obviously. In the future please carefully read the advisories before asking lots of questions, almost everything you have asked is addressed in the advisory texts AFAICT. Ian. _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Thu Sep 06 09:04:47 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Thu, 06 Sep 2012 09:04:47 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1T9Xzp-0002gG-AW; Thu, 06 Sep 2012 09:03:33 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1T9Xzn-0002fz-4s for xen-users@lists.xen.org; Thu, 06 Sep 2012 09:03:31 +0000 Received: from [85.158.138.51:49653] by server-3.bemta-3.messagelabs.com id 43/71-21322-1E668405; Thu, 06 Sep 2012 09:03:29 +0000 X-Env-Sender: Ian.Campbell@citrix.com X-Msg-Ref: server-3.tower-174.messagelabs.com!1346922209!20901213!1 X-Originating-IP: [62.200.22.115] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogNjIuMjAwLjIyLjExNSA9PiAxMTE5NjQ=\n X-StarScan-Received: X-StarScan-Version: 6.6.1.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 19165 invoked from network); 6 Sep 2012 09:03:29 -0000 Received: from smtp.ctxuk.citrix.com (HELO SMTP.EU.CITRIX.COM) (62.200.22.115) by server-3.tower-174.messagelabs.com with RC4-SHA encrypted SMTP; 6 Sep 2012 09:03:29 -0000 X-IronPort-AV: E=Sophos;i="4.80,379,1344211200"; d="scan'208";a="14378956" Received: from lonpmailmx01.citrite.net ([10.30.203.162]) by LONPIPO01.EU.CITRIX.COM with ESMTP/TLS/RC4-MD5; 06 Sep 2012 09:03:28 +0000 Received: from [10.80.2.42] (10.80.2.42) by LONPMAILMX01.citrite.net (10.30.203.162) with Microsoft SMTP Server id 8.3.279.1; Thu, 6 Sep 2012 10:03:29 +0100 Message-ID: <1346922207.23055.29.camel@zakaz.uk.xensource.com> From: Ian Campbell To: kk s Date: Thu, 6 Sep 2012 10:03:27 +0100 In-Reply-To: References: Organization: Citrix Systems, Inc. X-Mailer: Evolution 3.4.3-1 MIME-Version: 1.0 Cc: "xen-users@lists.xen.org" Subject: Re: [Xen-users] [Xen-devel] Xen 4.2 rpm build X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org Please don't cross post to both users and devel. Both http://wiki.xen.org/wiki/Asking_Xen_Devel_Questions and http://wiki.xen.org/wiki/Xen_Users_Netiquette caution against this. I have moved xen-devel to BCC. On Thu, 2012-09-06 at 09:56 +0100, kk s wrote: > Can anyone provide the steps to build rpm from source for Xen 4.1.2? Have you searched the wiki and tries using a search engine? There are plenty of tutorials around. Ian. _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Thu Sep 06 09:04:47 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Thu, 06 Sep 2012 09:04:47 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1T9Xzp-0002gG-AW; Thu, 06 Sep 2012 09:03:33 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1T9Xzn-0002fz-4s for xen-users@lists.xen.org; Thu, 06 Sep 2012 09:03:31 +0000 Received: from [85.158.138.51:49653] by server-3.bemta-3.messagelabs.com id 43/71-21322-1E668405; Thu, 06 Sep 2012 09:03:29 +0000 X-Env-Sender: Ian.Campbell@citrix.com X-Msg-Ref: server-3.tower-174.messagelabs.com!1346922209!20901213!1 X-Originating-IP: [62.200.22.115] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogNjIuMjAwLjIyLjExNSA9PiAxMTE5NjQ=\n X-StarScan-Received: X-StarScan-Version: 6.6.1.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 19165 invoked from network); 6 Sep 2012 09:03:29 -0000 Received: from smtp.ctxuk.citrix.com (HELO SMTP.EU.CITRIX.COM) (62.200.22.115) by server-3.tower-174.messagelabs.com with RC4-SHA encrypted SMTP; 6 Sep 2012 09:03:29 -0000 X-IronPort-AV: E=Sophos;i="4.80,379,1344211200"; d="scan'208";a="14378956" Received: from lonpmailmx01.citrite.net ([10.30.203.162]) by LONPIPO01.EU.CITRIX.COM with ESMTP/TLS/RC4-MD5; 06 Sep 2012 09:03:28 +0000 Received: from [10.80.2.42] (10.80.2.42) by LONPMAILMX01.citrite.net (10.30.203.162) with Microsoft SMTP Server id 8.3.279.1; Thu, 6 Sep 2012 10:03:29 +0100 Message-ID: <1346922207.23055.29.camel@zakaz.uk.xensource.com> From: Ian Campbell To: kk s Date: Thu, 6 Sep 2012 10:03:27 +0100 In-Reply-To: References: Organization: Citrix Systems, Inc. X-Mailer: Evolution 3.4.3-1 MIME-Version: 1.0 Cc: "xen-users@lists.xen.org" Subject: Re: [Xen-users] [Xen-devel] Xen 4.2 rpm build X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org Please don't cross post to both users and devel. Both http://wiki.xen.org/wiki/Asking_Xen_Devel_Questions and http://wiki.xen.org/wiki/Xen_Users_Netiquette caution against this. I have moved xen-devel to BCC. On Thu, 2012-09-06 at 09:56 +0100, kk s wrote: > Can anyone provide the steps to build rpm from source for Xen 4.1.2? Have you searched the wiki and tries using a search engine? There are plenty of tutorials around. Ian. _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Thu Sep 06 09:08:33 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Thu, 06 Sep 2012 09:08:33 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1T9Y3b-0002xE-Lp; Thu, 06 Sep 2012 09:07:27 +0000 Received: from mail27.messagelabs.com ([193.109.254.147]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1T9Y3a-0002wY-Ez for xen-users@lists.xen.org; Thu, 06 Sep 2012 09:07:26 +0000 X-Env-Sender: ricardo.meb.jesus@gmail.com X-Msg-Ref: server-8.tower-27.messagelabs.com!1346922404!9830164!1 X-Originating-IP: [209.85.160.45] X-SpamReason: No, hits=0.3 required=7.0 tests=ML_RADAR_SPEW_LINKS_14, ML_RADAR_SPEW_LINKS_8,RCVD_BY_IP,spamassassin: ,async_handler: YXN5bmNfZGVsYXk6IDcwNjY2MjAgKHRpbWVvdXQp\n X-StarScan-Received: X-StarScan-Version: 6.6.1.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 2027 invoked from network); 6 Sep 2012 09:06:46 -0000 Received: from mail-pb0-f45.google.com (HELO mail-pb0-f45.google.com) (209.85.160.45) by server-8.tower-27.messagelabs.com with RC4-SHA encrypted SMTP; 6 Sep 2012 09:06:46 -0000 Received: by pbbjt11 with SMTP id jt11so2295365pbb.32 for ; Thu, 06 Sep 2012 02:06:44 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=Q48XObubjsH3vMiEOVgevnYLmSKuKMs/V+TTR813mPk=; b=UkC8OFr3pnggE73s2gzhgp3sABmw+9dOtUBB7U1C/4W/suUUIez+CtvVMwohzMBW++ Rm4OY9PJk8FUPxHX2ynJCWpsag66KWlpgdh8wWXIc2alFpo/P+n7wrKdcKmz3lEk+sH6 T+CNyEHyWi7cy9cxwXOGmtCtvIS8yVwxbzo8ErOtXRwrSY69LHvt09QL9FPDuL36mxZp RX5cCgR9AJxFzQJHvWM0GHwJtnfezxJlw1ipxugQqNmaT8gd+CFIdlG9dMSwAAQdbPMY G6+8Fzobj1QUPfcx1D93HVwtQKstcGOwRrt9BEj/r2/AeF+7fNZ534r0dad4LaGGcPXf 6kgQ== MIME-Version: 1.0 Received: by 10.68.232.138 with SMTP id to10mr3936667pbc.77.1346922404159; Thu, 06 Sep 2012 02:06:44 -0700 (PDT) Received: by 10.66.72.34 with HTTP; Thu, 6 Sep 2012 02:06:44 -0700 (PDT) In-Reply-To: References: Date: Thu, 6 Sep 2012 10:06:44 +0100 Message-ID: From: Ricardo Jesus To: kk s Cc: xen-users@lists.xen.org Subject: Re: [Xen-users] [Xen-devel] Xen 4.2 rpm build X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org Hi, Did you check out https://www.crc.id.au/xen-on-rhel6-scientific-linux-6-centos-6-howto/ ? Their repository provides rpm for RHEL 6.x and as far as i recall the current available version is Xen 4.1.3. There's also Choon's repository for RHEL 6.x and others are listed in Xen's Wiki. As allways you can check out the source rpms from these repos and customize from there. Best regards, Ricardo Jesus. On Thu, Sep 6, 2012 at 9:56 AM, kk s wrote: > Hi, > > Can anyone provide the steps to build rpm from source for Xen 4.1.2? > > > > _______________________________________________ > Xen-devel mailing list > Xen-devel@lists.xen.org > http://lists.xen.org/xen-devel > _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Thu Sep 06 09:08:33 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Thu, 06 Sep 2012 09:08:33 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1T9Y3b-0002xE-Lp; Thu, 06 Sep 2012 09:07:27 +0000 Received: from mail27.messagelabs.com ([193.109.254.147]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1T9Y3a-0002wY-Ez for xen-users@lists.xen.org; Thu, 06 Sep 2012 09:07:26 +0000 X-Env-Sender: ricardo.meb.jesus@gmail.com X-Msg-Ref: server-8.tower-27.messagelabs.com!1346922404!9830164!1 X-Originating-IP: [209.85.160.45] X-SpamReason: No, hits=0.3 required=7.0 tests=ML_RADAR_SPEW_LINKS_14, ML_RADAR_SPEW_LINKS_8,RCVD_BY_IP,spamassassin: ,async_handler: YXN5bmNfZGVsYXk6IDcwNjY2MjAgKHRpbWVvdXQp\n X-StarScan-Received: X-StarScan-Version: 6.6.1.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 2027 invoked from network); 6 Sep 2012 09:06:46 -0000 Received: from mail-pb0-f45.google.com (HELO mail-pb0-f45.google.com) (209.85.160.45) by server-8.tower-27.messagelabs.com with RC4-SHA encrypted SMTP; 6 Sep 2012 09:06:46 -0000 Received: by pbbjt11 with SMTP id jt11so2295365pbb.32 for ; Thu, 06 Sep 2012 02:06:44 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=Q48XObubjsH3vMiEOVgevnYLmSKuKMs/V+TTR813mPk=; b=UkC8OFr3pnggE73s2gzhgp3sABmw+9dOtUBB7U1C/4W/suUUIez+CtvVMwohzMBW++ Rm4OY9PJk8FUPxHX2ynJCWpsag66KWlpgdh8wWXIc2alFpo/P+n7wrKdcKmz3lEk+sH6 T+CNyEHyWi7cy9cxwXOGmtCtvIS8yVwxbzo8ErOtXRwrSY69LHvt09QL9FPDuL36mxZp RX5cCgR9AJxFzQJHvWM0GHwJtnfezxJlw1ipxugQqNmaT8gd+CFIdlG9dMSwAAQdbPMY G6+8Fzobj1QUPfcx1D93HVwtQKstcGOwRrt9BEj/r2/AeF+7fNZ534r0dad4LaGGcPXf 6kgQ== MIME-Version: 1.0 Received: by 10.68.232.138 with SMTP id to10mr3936667pbc.77.1346922404159; Thu, 06 Sep 2012 02:06:44 -0700 (PDT) Received: by 10.66.72.34 with HTTP; Thu, 6 Sep 2012 02:06:44 -0700 (PDT) In-Reply-To: References: Date: Thu, 6 Sep 2012 10:06:44 +0100 Message-ID: From: Ricardo Jesus To: kk s Cc: xen-users@lists.xen.org Subject: Re: [Xen-users] [Xen-devel] Xen 4.2 rpm build X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org Hi, Did you check out https://www.crc.id.au/xen-on-rhel6-scientific-linux-6-centos-6-howto/ ? Their repository provides rpm for RHEL 6.x and as far as i recall the current available version is Xen 4.1.3. There's also Choon's repository for RHEL 6.x and others are listed in Xen's Wiki. As allways you can check out the source rpms from these repos and customize from there. Best regards, Ricardo Jesus. On Thu, Sep 6, 2012 at 9:56 AM, kk s wrote: > Hi, > > Can anyone provide the steps to build rpm from source for Xen 4.1.2? > > > > _______________________________________________ > Xen-devel mailing list > Xen-devel@lists.xen.org > http://lists.xen.org/xen-devel > _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Thu Sep 06 09:15:03 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Thu, 06 Sep 2012 09:15:03 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1T9Y9y-0003Rp-F5; Thu, 06 Sep 2012 09:14:02 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1T9Y9w-0003RT-Ia for xen-users@lists.xen.org; Thu, 06 Sep 2012 09:14:00 +0000 Received: from [85.158.143.35:57464] by server-3.bemta-4.messagelabs.com id F0/E7-08232-75968405; Thu, 06 Sep 2012 09:13:59 +0000 X-Env-Sender: Ian.Campbell@citrix.com X-Msg-Ref: server-4.tower-21.messagelabs.com!1346922838!5245294!1 X-Originating-IP: [62.200.22.115] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogNjIuMjAwLjIyLjExNSA9PiAxMTE5NzY=\n X-StarScan-Received: X-StarScan-Version: 6.6.1.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 7331 invoked from network); 6 Sep 2012 09:13:59 -0000 Received: from smtp.ctxuk.citrix.com (HELO SMTP.EU.CITRIX.COM) (62.200.22.115) by server-4.tower-21.messagelabs.com with RC4-SHA encrypted SMTP; 6 Sep 2012 09:13:59 -0000 X-IronPort-AV: E=Sophos;i="4.80,379,1344211200"; d="scan'208";a="14379307" Received: from lonpmailmx01.citrite.net ([10.30.203.162]) by LONPIPO01.EU.CITRIX.COM with ESMTP/TLS/RC4-MD5; 06 Sep 2012 09:13:58 +0000 Received: from [10.80.2.42] (10.80.2.42) by LONPMAILMX01.citrite.net (10.30.203.162) with Microsoft SMTP Server id 8.3.279.1; Thu, 6 Sep 2012 10:13:58 +0100 Message-ID: <1346922837.23055.33.camel@zakaz.uk.xensource.com> From: Ian Campbell To: kk s Date: Thu, 6 Sep 2012 10:13:57 +0100 In-Reply-To: References: <1346921802.23055.26.camel@zakaz.uk.xensource.com> Organization: Citrix Systems, Inc. X-Mailer: Evolution 3.4.3-1 MIME-Version: 1.0 Cc: "xen-users@lists.xen.org" , "xen-devel@lists.xen.org" Subject: Re: [Xen-users] [Xen-devel] Security patches X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org On Thu, 2012-09-06 at 10:08 +0100, kk s wrote: > Hi Ian, > > Thanks for your reply. Sorry to bother you with this. I am bit > confused and so I am asking to make clear myself. > > Reg CVE-2012-2934 - > http://lists.xen.org/archives/html/xen-announce/2012-06/msg00002.html > Is Xen 3.4 too affected with this vulnerable? If so I couldn't find > the patch for xen 3.4 and it does exit for xen 4.x only. I expect it does effect 3.4, but only if you are running on one of the listed processors. security@xen.org doesn't provide security support for 3.4 any more. If you aren't able to backport the 4.0 patch yourself, you would need to speak to Keith Coleman who is the 3.4 stable maintainer. > I don't how to apply the following patches since I have created rpm > with patches applied that included as downloadable file. But for these > patches I am not seeing any downloadable file. > > http://lists.xen.org/archives/html/xen-devel/2012-02/msg00212.html > http://lists.xen.org/archives/html/xen-devel/2012-07/msg01649.html > http://lists.xen.org/archives/html/xen-devel/2012-08/msg00855.html > > If you can clear this for me that would be great :) I already pointed you at http://wiki.xen.org/wiki/Security_Announcements which should have all the links you need. _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Thu Sep 06 09:15:03 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Thu, 06 Sep 2012 09:15:03 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1T9Y9y-0003Rp-F5; Thu, 06 Sep 2012 09:14:02 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1T9Y9w-0003RT-Ia for xen-users@lists.xen.org; Thu, 06 Sep 2012 09:14:00 +0000 Received: from [85.158.143.35:57464] by server-3.bemta-4.messagelabs.com id F0/E7-08232-75968405; Thu, 06 Sep 2012 09:13:59 +0000 X-Env-Sender: Ian.Campbell@citrix.com X-Msg-Ref: server-4.tower-21.messagelabs.com!1346922838!5245294!1 X-Originating-IP: [62.200.22.115] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogNjIuMjAwLjIyLjExNSA9PiAxMTE5NzY=\n X-StarScan-Received: X-StarScan-Version: 6.6.1.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 7331 invoked from network); 6 Sep 2012 09:13:59 -0000 Received: from smtp.ctxuk.citrix.com (HELO SMTP.EU.CITRIX.COM) (62.200.22.115) by server-4.tower-21.messagelabs.com with RC4-SHA encrypted SMTP; 6 Sep 2012 09:13:59 -0000 X-IronPort-AV: E=Sophos;i="4.80,379,1344211200"; d="scan'208";a="14379307" Received: from lonpmailmx01.citrite.net ([10.30.203.162]) by LONPIPO01.EU.CITRIX.COM with ESMTP/TLS/RC4-MD5; 06 Sep 2012 09:13:58 +0000 Received: from [10.80.2.42] (10.80.2.42) by LONPMAILMX01.citrite.net (10.30.203.162) with Microsoft SMTP Server id 8.3.279.1; Thu, 6 Sep 2012 10:13:58 +0100 Message-ID: <1346922837.23055.33.camel@zakaz.uk.xensource.com> From: Ian Campbell To: kk s Date: Thu, 6 Sep 2012 10:13:57 +0100 In-Reply-To: References: <1346921802.23055.26.camel@zakaz.uk.xensource.com> Organization: Citrix Systems, Inc. X-Mailer: Evolution 3.4.3-1 MIME-Version: 1.0 Cc: "xen-users@lists.xen.org" , "xen-devel@lists.xen.org" Subject: Re: [Xen-users] [Xen-devel] Security patches X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org On Thu, 2012-09-06 at 10:08 +0100, kk s wrote: > Hi Ian, > > Thanks for your reply. Sorry to bother you with this. I am bit > confused and so I am asking to make clear myself. > > Reg CVE-2012-2934 - > http://lists.xen.org/archives/html/xen-announce/2012-06/msg00002.html > Is Xen 3.4 too affected with this vulnerable? If so I couldn't find > the patch for xen 3.4 and it does exit for xen 4.x only. I expect it does effect 3.4, but only if you are running on one of the listed processors. security@xen.org doesn't provide security support for 3.4 any more. If you aren't able to backport the 4.0 patch yourself, you would need to speak to Keith Coleman who is the 3.4 stable maintainer. > I don't how to apply the following patches since I have created rpm > with patches applied that included as downloadable file. But for these > patches I am not seeing any downloadable file. > > http://lists.xen.org/archives/html/xen-devel/2012-02/msg00212.html > http://lists.xen.org/archives/html/xen-devel/2012-07/msg01649.html > http://lists.xen.org/archives/html/xen-devel/2012-08/msg00855.html > > If you can clear this for me that would be great :) I already pointed you at http://wiki.xen.org/wiki/Security_Announcements which should have all the links you need. _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Thu Sep 06 10:43:01 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Thu, 06 Sep 2012 10:43:01 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1T9ZWq-0006tX-8p; Thu, 06 Sep 2012 10:41:44 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1T9ZWp-0006tS-GL for xen-users@lists.xen.org; Thu, 06 Sep 2012 10:41:43 +0000 Received: from [85.158.143.99:44816] by server-2.bemta-4.messagelabs.com id 2A/E7-21239-6ED78405; Thu, 06 Sep 2012 10:41:42 +0000 X-Env-Sender: niuxinli1989@gmail.com X-Msg-Ref: server-10.tower-216.messagelabs.com!1346928101!22481927!1 X-Originating-IP: [209.85.215.173] X-SpamReason: No, hits=1.5 required=7.0 tests=HTML_00_10,HTML_MESSAGE, ML_RADAR_SPEW_LINKS_14,RCVD_BY_IP,spamassassin: X-StarScan-Received: X-StarScan-Version: 6.6.1.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 25241 invoked from network); 6 Sep 2012 10:41:41 -0000 Received: from mail-ey0-f173.google.com (HELO mail-ey0-f173.google.com) (209.85.215.173) by server-10.tower-216.messagelabs.com with RC4-SHA encrypted SMTP; 6 Sep 2012 10:41:41 -0000 Received: by eaac13 with SMTP id c13so547354eaa.32 for ; Thu, 06 Sep 2012 03:41:41 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:date:message-id:subject:from:to:content-type; bh=2psCNd1ZyGQoEzyXI555gZHhW+kEb8HiRND8L2tFVZo=; b=HsBzx+3rwp7Ty8WKX01/WgFSiRy2v3oAH7ydYMuxlgNXImBYWGUl3ETvIKEX7GAS+Z G3JqdpZHOT4CC0KIo/11calTasBh5N+r3t771zObaXM5Bx5yUf3YrCUV8UbVEm9+fYqd 0xZ3un88M/WZCt29JPjEzsaR3kC+nB/5tJbEOhm+W9+THPQJHGOAAy+zQDHhlZNTrQRB 14V8UYR/b4gUwpB9Gy8IJls5ONljvO77XhCrxfbEtcrVGy/wzvJV+ht7NUtSjA5sIP5I UKsJYCbH+If5Mcckay3UyGpK6C1d8rnoNJaNSw7gUor54FeKXLz7gvq6rUYsTZQnpHfH GGhA== MIME-Version: 1.0 Received: by 10.14.212.72 with SMTP id x48mr2134967eeo.40.1346928100876; Thu, 06 Sep 2012 03:41:40 -0700 (PDT) Received: by 10.14.132.79 with HTTP; Thu, 6 Sep 2012 03:41:40 -0700 (PDT) Date: Thu, 6 Sep 2012 18:41:40 +0800 Message-ID: From: Xinli Niu To: xen-users@lists.xen.org Subject: [Xen-users] XenServer Tools For Linux X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============3809641354860363150==" Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org --===============3809641354860363150== Content-Type: multipart/alternative; boundary=047d7b621e40fda2fe04c906229f --047d7b621e40fda2fe04c906229f Content-Type: text/plain; charset=ISO-8859-1 Hi, I installed two linux VMs in XenServer 6.0, one is CentOS 5.5 and the other is Ubuntu 10.04, both of which are HVMs. I install xenserver tools many times and the packages are installed, but XenCenter keeps telling me that "Xenserver tools is not installed". Are xenserver tools of linux intended only for PV vm? I am not familiar with xenserver and need help.Thanks! Best Regards, Xinli --047d7b621e40fda2fe04c906229f Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Hi,
=A0=A0=A0 I installed two linux VMs in XenServer 6.0, one is CentOS = 5.5 and the other is Ubuntu 10.04, both of which are HVMs. I install xenser= ver tools many times and the packages are installed, but XenCenter keeps te= lling me that "Xenserver tools is not installed". Are xenserver t= ools of linux intended only for PV vm? I am not familiar with xenserver and= need help.Thanks!

Best Regards,
Xinli

--047d7b621e40fda2fe04c906229f-- --===============3809641354860363150== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users --===============3809641354860363150==-- From xen-users-bounces@lists.xen.org Thu Sep 06 10:43:01 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Thu, 06 Sep 2012 10:43:01 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1T9ZWq-0006tX-8p; Thu, 06 Sep 2012 10:41:44 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1T9ZWp-0006tS-GL for xen-users@lists.xen.org; Thu, 06 Sep 2012 10:41:43 +0000 Received: from [85.158.143.99:44816] by server-2.bemta-4.messagelabs.com id 2A/E7-21239-6ED78405; Thu, 06 Sep 2012 10:41:42 +0000 X-Env-Sender: niuxinli1989@gmail.com X-Msg-Ref: server-10.tower-216.messagelabs.com!1346928101!22481927!1 X-Originating-IP: [209.85.215.173] X-SpamReason: No, hits=1.5 required=7.0 tests=HTML_00_10,HTML_MESSAGE, ML_RADAR_SPEW_LINKS_14,RCVD_BY_IP,spamassassin: X-StarScan-Received: X-StarScan-Version: 6.6.1.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 25241 invoked from network); 6 Sep 2012 10:41:41 -0000 Received: from mail-ey0-f173.google.com (HELO mail-ey0-f173.google.com) (209.85.215.173) by server-10.tower-216.messagelabs.com with RC4-SHA encrypted SMTP; 6 Sep 2012 10:41:41 -0000 Received: by eaac13 with SMTP id c13so547354eaa.32 for ; Thu, 06 Sep 2012 03:41:41 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:date:message-id:subject:from:to:content-type; bh=2psCNd1ZyGQoEzyXI555gZHhW+kEb8HiRND8L2tFVZo=; b=HsBzx+3rwp7Ty8WKX01/WgFSiRy2v3oAH7ydYMuxlgNXImBYWGUl3ETvIKEX7GAS+Z G3JqdpZHOT4CC0KIo/11calTasBh5N+r3t771zObaXM5Bx5yUf3YrCUV8UbVEm9+fYqd 0xZ3un88M/WZCt29JPjEzsaR3kC+nB/5tJbEOhm+W9+THPQJHGOAAy+zQDHhlZNTrQRB 14V8UYR/b4gUwpB9Gy8IJls5ONljvO77XhCrxfbEtcrVGy/wzvJV+ht7NUtSjA5sIP5I UKsJYCbH+If5Mcckay3UyGpK6C1d8rnoNJaNSw7gUor54FeKXLz7gvq6rUYsTZQnpHfH GGhA== MIME-Version: 1.0 Received: by 10.14.212.72 with SMTP id x48mr2134967eeo.40.1346928100876; Thu, 06 Sep 2012 03:41:40 -0700 (PDT) Received: by 10.14.132.79 with HTTP; Thu, 6 Sep 2012 03:41:40 -0700 (PDT) Date: Thu, 6 Sep 2012 18:41:40 +0800 Message-ID: From: Xinli Niu To: xen-users@lists.xen.org Subject: [Xen-users] XenServer Tools For Linux X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============3809641354860363150==" Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org --===============3809641354860363150== Content-Type: multipart/alternative; boundary=047d7b621e40fda2fe04c906229f --047d7b621e40fda2fe04c906229f Content-Type: text/plain; charset=ISO-8859-1 Hi, I installed two linux VMs in XenServer 6.0, one is CentOS 5.5 and the other is Ubuntu 10.04, both of which are HVMs. I install xenserver tools many times and the packages are installed, but XenCenter keeps telling me that "Xenserver tools is not installed". Are xenserver tools of linux intended only for PV vm? I am not familiar with xenserver and need help.Thanks! Best Regards, Xinli --047d7b621e40fda2fe04c906229f Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Hi,
=A0=A0=A0 I installed two linux VMs in XenServer 6.0, one is CentOS = 5.5 and the other is Ubuntu 10.04, both of which are HVMs. I install xenser= ver tools many times and the packages are installed, but XenCenter keeps te= lling me that "Xenserver tools is not installed". Are xenserver t= ools of linux intended only for PV vm? I am not familiar with xenserver and= need help.Thanks!

Best Regards,
Xinli

--047d7b621e40fda2fe04c906229f-- --===============3809641354860363150== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users --===============3809641354860363150==-- From xen-users-bounces@lists.xen.org Thu Sep 06 10:51:36 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Thu, 06 Sep 2012 10:51:36 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1T9ZfG-0007Lq-Td; Thu, 06 Sep 2012 10:50:26 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1T9ZfF-0007Lf-H2 for xen-users@lists.xen.org; Thu, 06 Sep 2012 10:50:25 +0000 Received: from [85.158.143.35:20760] by server-1.bemta-4.messagelabs.com id BB/68-12504-0FF78405; Thu, 06 Sep 2012 10:50:24 +0000 X-Env-Sender: Ian.Campbell@citrix.com X-Msg-Ref: server-4.tower-21.messagelabs.com!1346928600!5266058!1 X-Originating-IP: [62.200.22.115] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogNjIuMjAwLjIyLjExNSA9PiAxMTE5NzY=\n X-StarScan-Received: X-StarScan-Version: 6.6.1.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 15945 invoked from network); 6 Sep 2012 10:50:01 -0000 Received: from smtp.ctxuk.citrix.com (HELO SMTP.EU.CITRIX.COM) (62.200.22.115) by server-4.tower-21.messagelabs.com with RC4-SHA encrypted SMTP; 6 Sep 2012 10:50:01 -0000 X-IronPort-AV: E=Sophos;i="4.80,380,1344211200"; d="scan'208";a="14382238" Received: from lonpmailmx01.citrite.net ([10.30.203.162]) by LONPIPO01.EU.CITRIX.COM with ESMTP/TLS/RC4-MD5; 06 Sep 2012 10:49:23 +0000 Received: from [10.80.2.42] (10.80.2.42) by LONPMAILMX01.citrite.net (10.30.203.162) with Microsoft SMTP Server id 8.3.279.1; Thu, 6 Sep 2012 11:49:23 +0100 Message-ID: <1346928561.23055.39.camel@zakaz.uk.xensource.com> From: Ian Campbell To: Xinli Niu Date: Thu, 6 Sep 2012 11:49:21 +0100 In-Reply-To: References: Organization: Citrix Systems, Inc. X-Mailer: Evolution 3.4.3-1 MIME-Version: 1.0 Cc: "xen-users@lists.xen.org" Subject: Re: [Xen-users] XenServer Tools For Linux X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org Hi Xinli, On Thu, 2012-09-06 at 11:41 +0100, Xinli Niu wrote: > Hi, > I installed two linux VMs in XenServer 6.0, one is CentOS 5.5 and > the other is Ubuntu 10.04, both of which are HVMs. I install xenserver > tools many times and the packages are installed, but XenCenter keeps > telling me that "Xenserver tools is not installed". Are xenserver > tools of linux intended only for PV vm? I am not familiar with > xenserver and need help.Thanks! This list is for users of the Xen.org version of Xen. Questions about XenServer should be addressed to either your XS support rep or the xenserver forums: http://forums.citrix.com/category.jspa?categoryID=101 Thanks, Ian. _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Thu Sep 06 10:51:36 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Thu, 06 Sep 2012 10:51:36 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1T9ZfG-0007Lq-Td; Thu, 06 Sep 2012 10:50:26 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1T9ZfF-0007Lf-H2 for xen-users@lists.xen.org; Thu, 06 Sep 2012 10:50:25 +0000 Received: from [85.158.143.35:20760] by server-1.bemta-4.messagelabs.com id BB/68-12504-0FF78405; Thu, 06 Sep 2012 10:50:24 +0000 X-Env-Sender: Ian.Campbell@citrix.com X-Msg-Ref: server-4.tower-21.messagelabs.com!1346928600!5266058!1 X-Originating-IP: [62.200.22.115] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogNjIuMjAwLjIyLjExNSA9PiAxMTE5NzY=\n X-StarScan-Received: X-StarScan-Version: 6.6.1.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 15945 invoked from network); 6 Sep 2012 10:50:01 -0000 Received: from smtp.ctxuk.citrix.com (HELO SMTP.EU.CITRIX.COM) (62.200.22.115) by server-4.tower-21.messagelabs.com with RC4-SHA encrypted SMTP; 6 Sep 2012 10:50:01 -0000 X-IronPort-AV: E=Sophos;i="4.80,380,1344211200"; d="scan'208";a="14382238" Received: from lonpmailmx01.citrite.net ([10.30.203.162]) by LONPIPO01.EU.CITRIX.COM with ESMTP/TLS/RC4-MD5; 06 Sep 2012 10:49:23 +0000 Received: from [10.80.2.42] (10.80.2.42) by LONPMAILMX01.citrite.net (10.30.203.162) with Microsoft SMTP Server id 8.3.279.1; Thu, 6 Sep 2012 11:49:23 +0100 Message-ID: <1346928561.23055.39.camel@zakaz.uk.xensource.com> From: Ian Campbell To: Xinli Niu Date: Thu, 6 Sep 2012 11:49:21 +0100 In-Reply-To: References: Organization: Citrix Systems, Inc. X-Mailer: Evolution 3.4.3-1 MIME-Version: 1.0 Cc: "xen-users@lists.xen.org" Subject: Re: [Xen-users] XenServer Tools For Linux X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org Hi Xinli, On Thu, 2012-09-06 at 11:41 +0100, Xinli Niu wrote: > Hi, > I installed two linux VMs in XenServer 6.0, one is CentOS 5.5 and > the other is Ubuntu 10.04, both of which are HVMs. I install xenserver > tools many times and the packages are installed, but XenCenter keeps > telling me that "Xenserver tools is not installed". Are xenserver > tools of linux intended only for PV vm? I am not familiar with > xenserver and need help.Thanks! This list is for users of the Xen.org version of Xen. Questions about XenServer should be addressed to either your XS support rep or the xenserver forums: http://forums.citrix.com/category.jspa?categoryID=101 Thanks, Ian. _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Thu Sep 06 11:03:45 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Thu, 06 Sep 2012 11:03:45 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1T9ZrD-00089y-W1; Thu, 06 Sep 2012 11:02:47 +0000 Received: from mail27.messagelabs.com ([193.109.254.147]) by lists.xen.org with smtp (Exim 4.72) (envelope-from ) id 1T9ZrC-000898-C9 for xen-users@lists.xen.org; Thu, 06 Sep 2012 11:02:46 +0000 X-Env-Sender: matej.zary@cvtisr.sk X-Msg-Ref: server-16.tower-27.messagelabs.com!1346929358!8433053!1 X-Originating-IP: [193.87.7.3] X-SpamReason: No, hits=0.8 required=7.0 tests=BODY_RANDOM_LONG, MAILTO_TO_SPAM_ADDR X-StarScan-Received: X-StarScan-Version: 6.6.1.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 3815 invoked from network); 6 Sep 2012 11:02:38 -0000 Received: from virgo.cvtisr.sk (HELO mail.cvtisr.sk) (193.87.7.3) by server-16.tower-27.messagelabs.com with SMTP; 6 Sep 2012 11:02:38 -0000 Received: from localhost (unknown [127.0.0.1]) by mail.cvtisr.sk (Postfix) with ESMTP id 0F937920F6; Thu, 6 Sep 2012 13:43:09 +0200 (CEST) X-Virus-Scanned: amavisd-new at cvtisr.sk Received: from mail.cvtisr.sk ([127.0.0.1]) by localhost (mail.cvtisr.sk [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 8vG6+2qMLMw8; Thu, 6 Sep 2012 13:43:05 +0200 (CEST) Received: from aries.space.cvtisr.sk (unknown [192.168.1.51]) by mail.cvtisr.sk (Postfix) with ESMTP id 107DB920A1; Thu, 6 Sep 2012 13:43:05 +0200 (CEST) Received: from Aries.space.cvtisr.sk ([::1]) by aries.space.cvtisr.sk ([::1]) with mapi; Thu, 6 Sep 2012 13:02:34 +0200 From: Zary Matej To: Xinli Niu , "xen-users@lists.xen.org" Date: Thu, 6 Sep 2012 12:58:17 +0200 Thread-Topic: [Xen-users] XenServer Tools For Linux Thread-Index: Ac2MHaOUJJO9aaiwQgOW7bUxApE45AAAOGLo Message-ID: <5DB0519124BB3D4DBEEB14426D4AC7EA6A72C9D589@aries.space.cvtisr.sk> References: In-Reply-To: Accept-Language: en-US Content-Language: en-GB X-MS-Has-Attach: X-MS-TNEF-Correlator: acceptlanguage: en-US MIME-Version: 1.0 Subject: Re: [Xen-users] XenServer Tools For Linux X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org >________________________________________ >From: xen-users-bounces@lists.xen.org [xen-users-bounces@lists.xen.org] On Behalf Of Xinli Niu [niuxinli1989@gmail.com] >Sent: 06 September 2012 12:41 >To: xen-users@lists.xen.org >Subject: [Xen-users] XenServer Tools For Linux > >Hi, > I installed two linux VMs in XenServer 6.0, one is CentOS 5.5 and the other is Ubuntu 10.04, both of which are HVMs. I install xenserver tools many times and the packages are installed, but XenCenter keeps telling me that "Xenserver >tools is not installed". Are xenserver tools of linux intended only for PV vm? I am not familiar with xenserver and need help.Thanks! > >Best Regards, >Xinli > Hi there. First, to get help on Citrix XenServer issues, there are better places than this one - e.g. official Citrix XenServer support forums - http://forums.citrix.com/category.jspa?categoryID=101. And shot in the dark - have you restared the VMs after installing the XenTools? regards Matej _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Thu Sep 06 11:03:45 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Thu, 06 Sep 2012 11:03:45 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1T9ZrD-00089y-W1; Thu, 06 Sep 2012 11:02:47 +0000 Received: from mail27.messagelabs.com ([193.109.254.147]) by lists.xen.org with smtp (Exim 4.72) (envelope-from ) id 1T9ZrC-000898-C9 for xen-users@lists.xen.org; Thu, 06 Sep 2012 11:02:46 +0000 X-Env-Sender: matej.zary@cvtisr.sk X-Msg-Ref: server-16.tower-27.messagelabs.com!1346929358!8433053!1 X-Originating-IP: [193.87.7.3] X-SpamReason: No, hits=0.8 required=7.0 tests=BODY_RANDOM_LONG, MAILTO_TO_SPAM_ADDR X-StarScan-Received: X-StarScan-Version: 6.6.1.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 3815 invoked from network); 6 Sep 2012 11:02:38 -0000 Received: from virgo.cvtisr.sk (HELO mail.cvtisr.sk) (193.87.7.3) by server-16.tower-27.messagelabs.com with SMTP; 6 Sep 2012 11:02:38 -0000 Received: from localhost (unknown [127.0.0.1]) by mail.cvtisr.sk (Postfix) with ESMTP id 0F937920F6; Thu, 6 Sep 2012 13:43:09 +0200 (CEST) X-Virus-Scanned: amavisd-new at cvtisr.sk Received: from mail.cvtisr.sk ([127.0.0.1]) by localhost (mail.cvtisr.sk [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 8vG6+2qMLMw8; Thu, 6 Sep 2012 13:43:05 +0200 (CEST) Received: from aries.space.cvtisr.sk (unknown [192.168.1.51]) by mail.cvtisr.sk (Postfix) with ESMTP id 107DB920A1; Thu, 6 Sep 2012 13:43:05 +0200 (CEST) Received: from Aries.space.cvtisr.sk ([::1]) by aries.space.cvtisr.sk ([::1]) with mapi; Thu, 6 Sep 2012 13:02:34 +0200 From: Zary Matej To: Xinli Niu , "xen-users@lists.xen.org" Date: Thu, 6 Sep 2012 12:58:17 +0200 Thread-Topic: [Xen-users] XenServer Tools For Linux Thread-Index: Ac2MHaOUJJO9aaiwQgOW7bUxApE45AAAOGLo Message-ID: <5DB0519124BB3D4DBEEB14426D4AC7EA6A72C9D589@aries.space.cvtisr.sk> References: In-Reply-To: Accept-Language: en-US Content-Language: en-GB X-MS-Has-Attach: X-MS-TNEF-Correlator: acceptlanguage: en-US MIME-Version: 1.0 Subject: Re: [Xen-users] XenServer Tools For Linux X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org >________________________________________ >From: xen-users-bounces@lists.xen.org [xen-users-bounces@lists.xen.org] On Behalf Of Xinli Niu [niuxinli1989@gmail.com] >Sent: 06 September 2012 12:41 >To: xen-users@lists.xen.org >Subject: [Xen-users] XenServer Tools For Linux > >Hi, > I installed two linux VMs in XenServer 6.0, one is CentOS 5.5 and the other is Ubuntu 10.04, both of which are HVMs. I install xenserver tools many times and the packages are installed, but XenCenter keeps telling me that "Xenserver >tools is not installed". Are xenserver tools of linux intended only for PV vm? I am not familiar with xenserver and need help.Thanks! > >Best Regards, >Xinli > Hi there. First, to get help on Citrix XenServer issues, there are better places than this one - e.g. official Citrix XenServer support forums - http://forums.citrix.com/category.jspa?categoryID=101. And shot in the dark - have you restared the VMs after installing the XenTools? regards Matej _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Thu Sep 06 11:33:03 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Thu, 06 Sep 2012 11:33:03 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1T9aJW-0001W1-Bl; Thu, 06 Sep 2012 11:32:02 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1T9aJU-0001Vq-VF for xen-users@lists.xen.org; Thu, 06 Sep 2012 11:32:01 +0000 Received: from [85.158.143.99:7555] by server-1.bemta-4.messagelabs.com id 42/6D-12504-0B988405; Thu, 06 Sep 2012 11:32:00 +0000 X-Env-Sender: agwells0714@gmail.com X-Msg-Ref: server-15.tower-216.messagelabs.com!1346931118!28876354!1 X-Originating-IP: [209.85.215.173] X-SpamReason: No, hits=0.7 required=7.0 tests=HTML_30_40,HTML_MESSAGE, MAILTO_TO_SPAM_ADDR,ML_RADAR_SPEW_LINKS_14,RCVD_BY_IP,spamassassin: X-StarScan-Received: X-StarScan-Version: 6.6.1.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 12204 invoked from network); 6 Sep 2012 11:31:59 -0000 Received: from mail-ey0-f173.google.com (HELO mail-ey0-f173.google.com) (209.85.215.173) by server-15.tower-216.messagelabs.com with RC4-SHA encrypted SMTP; 6 Sep 2012 11:31:59 -0000 Received: by eaac13 with SMTP id c13so566378eaa.32 for ; Thu, 06 Sep 2012 04:31:58 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=71QWD1oXKgJs100dxGCuMjk4IIjW3GL8WbIt8tuut/A=; b=hs/9BNhP4tN+0LkmbGB3ySK+YwzfhIUU1At7KGsYW3SJR6KskwOyohpIspn/8LRI9M nAGDMf5tI4AFTHGr1prw84ilA20cdm1CvAmAUyqWaPIIbmWkSQlIGs+ZM2TLKgb6tZmC LOxXuzWEpDw7FOnXBi7Fp5NYOZ2ldv2ik9Q16wfx3YXRl5meZtLJ43BGDc8vZzV4y9ny Vl5hMmkU0DgCYQB4xAeRpMQSabJ2cGLAyHNpu54rTHTQzZsQlu8gXcyk/dOoduQi+ISM lOAfeK+fLRUJhxrGMEeirrPkc7vCtxLENquQHrpLZQqRHbCYJL3wWsqxg8w6RJDbnmoa wajg== MIME-Version: 1.0 Received: by 10.14.184.134 with SMTP id s6mr2362704eem.46.1346931118553; Thu, 06 Sep 2012 04:31:58 -0700 (PDT) Received: by 10.14.224.65 with HTTP; Thu, 6 Sep 2012 04:31:58 -0700 (PDT) Received: by 10.14.224.65 with HTTP; Thu, 6 Sep 2012 04:31:58 -0700 (PDT) In-Reply-To: <20120905085653.19451hqjife56728@webmail.soleks.com> References: <20120905085653.19451hqjife56728@webmail.soleks.com> Date: Thu, 6 Sep 2012 07:31:58 -0400 Message-ID: From: Andrew Wells To: dan@soleks.com Cc: xen-users@lists.xen.org Subject: Re: [Xen-users] guest OS High Availability with local storage X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============8322578955727798058==" Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org --===============8322578955727798058== Content-Type: multipart/alternative; boundary=047d7b3a7ff8dbbac904c906d686 --047d7b3a7ff8dbbac904c906d686 Content-Type: text/plain; charset=ISO-8859-1 True, but I have not heard it being that slow before, also if you do go with gluster use 3.3. if you are looking for ease of setup gluster is easy. And drdb stops at 2 nodes doesnt it. On Sep 5, 2012 11:08 AM, wrote: > From my experience gluster write performance (2 mirrored nodes) is very > low, approx 40-45Mb/sec. read is pretty high and it was network saturation > - appr 90-95Mb/sec (i have gigi network). For HA for VMs i'd highly > recommend DRDB+Pacemaker+Corosync. Solution is much more advanced, and > requires much more efforts, but output will cover all time expenses. I have > cluster of 2 nodes with DRBD, some VM images (block devices, using Logical > Volumes on top of DRDB) are up to 512G. I don't see any performance loss. > Also Pacemaker is well integrated with XEN live migration. So i think it's > best solution for "cheap man". > > > > 2012/9/5 Andrew Wells : > >> Actually look into gluster for turning your local storage into shared > >> storage. Works with more than one node and replicates data. > > > > thanks for for this useful info, also to everyone who shared their > opinion > > > > > > > > -- > > Regards, > > > > Umarzuki Mochlis > > http://debmal.my > > > > _______________________________________________ > > Xen-users mailing list > > Xen-users@lists.xen.org > > http://lists.xen.org/xen-users > > > > > ---------------------------------------------------------------- > This message was sent using IMP, the Internet Messaging Program. > > _______________________________________________ > Xen-users mailing list > Xen-users@lists.xen.org > http://lists.xen.org/xen-users > --047d7b3a7ff8dbbac904c906d686 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable

True, but I have not heard it being that slow before, also if you do go = with gluster use 3.3. if you are looking for ease of setup gluster is easy.= And drdb stops at 2 nodes doesnt it.

On Sep 5, 2012 11:08 AM, <dan@soleks.com> wrote:

=A0From my experience gluster write performance (2 mirrored nodes) is ve= ry low, approx 40-45Mb/sec. read is pretty high and it was network saturati= on =A0- appr 90-95Mb/sec (i have gigi network). For HA for VMs i'd high= ly recommend DRDB+Pacemaker+Corosync. Solution is much more advanced, and r= equires much more efforts, but output will cover all time expenses. I have = cluster of 2 nodes with DRBD, some VM images (block devices, using Logical = Volumes on top of DRDB) are up to 512G. I don't see any performance los= s. Also Pacemaker is well integrated with XEN live migration. So i think it= 's best solution for "cheap man".


> 2012/9/5 Andrew Wells <agwells0714@gmail.com>:
>> Actually look into gluster for turning your local storage into sha= red
>> storage. Works with more than one node and replicates data.
>
> thanks for for this useful info, also to everyone who shared their opi= nion
>
>
>
> --
> Regards,
>
> Umarzuki Mochlis
> http://debmal.my >
> _______________________________________________
> Xen-users mailing list
> Xen-users= @lists.xen.org
> http://li= sts.xen.org/xen-users
>


----------------------------------------------------------------
This message was sent using IMP, the Internet Messaging Program.

_______________________________________________
Xen-users mailing list
Xen-users@lists.xen.org
http://lists.x= en.org/xen-users
--047d7b3a7ff8dbbac904c906d686-- --===============8322578955727798058== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users --===============8322578955727798058==-- From xen-users-bounces@lists.xen.org Thu Sep 06 11:33:03 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Thu, 06 Sep 2012 11:33:03 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1T9aJW-0001W1-Bl; Thu, 06 Sep 2012 11:32:02 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1T9aJU-0001Vq-VF for xen-users@lists.xen.org; Thu, 06 Sep 2012 11:32:01 +0000 Received: from [85.158.143.99:7555] by server-1.bemta-4.messagelabs.com id 42/6D-12504-0B988405; Thu, 06 Sep 2012 11:32:00 +0000 X-Env-Sender: agwells0714@gmail.com X-Msg-Ref: server-15.tower-216.messagelabs.com!1346931118!28876354!1 X-Originating-IP: [209.85.215.173] X-SpamReason: No, hits=0.7 required=7.0 tests=HTML_30_40,HTML_MESSAGE, MAILTO_TO_SPAM_ADDR,ML_RADAR_SPEW_LINKS_14,RCVD_BY_IP,spamassassin: X-StarScan-Received: X-StarScan-Version: 6.6.1.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 12204 invoked from network); 6 Sep 2012 11:31:59 -0000 Received: from mail-ey0-f173.google.com (HELO mail-ey0-f173.google.com) (209.85.215.173) by server-15.tower-216.messagelabs.com with RC4-SHA encrypted SMTP; 6 Sep 2012 11:31:59 -0000 Received: by eaac13 with SMTP id c13so566378eaa.32 for ; Thu, 06 Sep 2012 04:31:58 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=71QWD1oXKgJs100dxGCuMjk4IIjW3GL8WbIt8tuut/A=; b=hs/9BNhP4tN+0LkmbGB3ySK+YwzfhIUU1At7KGsYW3SJR6KskwOyohpIspn/8LRI9M nAGDMf5tI4AFTHGr1prw84ilA20cdm1CvAmAUyqWaPIIbmWkSQlIGs+ZM2TLKgb6tZmC LOxXuzWEpDw7FOnXBi7Fp5NYOZ2ldv2ik9Q16wfx3YXRl5meZtLJ43BGDc8vZzV4y9ny Vl5hMmkU0DgCYQB4xAeRpMQSabJ2cGLAyHNpu54rTHTQzZsQlu8gXcyk/dOoduQi+ISM lOAfeK+fLRUJhxrGMEeirrPkc7vCtxLENquQHrpLZQqRHbCYJL3wWsqxg8w6RJDbnmoa wajg== MIME-Version: 1.0 Received: by 10.14.184.134 with SMTP id s6mr2362704eem.46.1346931118553; Thu, 06 Sep 2012 04:31:58 -0700 (PDT) Received: by 10.14.224.65 with HTTP; Thu, 6 Sep 2012 04:31:58 -0700 (PDT) Received: by 10.14.224.65 with HTTP; Thu, 6 Sep 2012 04:31:58 -0700 (PDT) In-Reply-To: <20120905085653.19451hqjife56728@webmail.soleks.com> References: <20120905085653.19451hqjife56728@webmail.soleks.com> Date: Thu, 6 Sep 2012 07:31:58 -0400 Message-ID: From: Andrew Wells To: dan@soleks.com Cc: xen-users@lists.xen.org Subject: Re: [Xen-users] guest OS High Availability with local storage X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============8322578955727798058==" Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org --===============8322578955727798058== Content-Type: multipart/alternative; boundary=047d7b3a7ff8dbbac904c906d686 --047d7b3a7ff8dbbac904c906d686 Content-Type: text/plain; charset=ISO-8859-1 True, but I have not heard it being that slow before, also if you do go with gluster use 3.3. if you are looking for ease of setup gluster is easy. And drdb stops at 2 nodes doesnt it. On Sep 5, 2012 11:08 AM, wrote: > From my experience gluster write performance (2 mirrored nodes) is very > low, approx 40-45Mb/sec. read is pretty high and it was network saturation > - appr 90-95Mb/sec (i have gigi network). For HA for VMs i'd highly > recommend DRDB+Pacemaker+Corosync. Solution is much more advanced, and > requires much more efforts, but output will cover all time expenses. I have > cluster of 2 nodes with DRBD, some VM images (block devices, using Logical > Volumes on top of DRDB) are up to 512G. I don't see any performance loss. > Also Pacemaker is well integrated with XEN live migration. So i think it's > best solution for "cheap man". > > > > 2012/9/5 Andrew Wells : > >> Actually look into gluster for turning your local storage into shared > >> storage. Works with more than one node and replicates data. > > > > thanks for for this useful info, also to everyone who shared their > opinion > > > > > > > > -- > > Regards, > > > > Umarzuki Mochlis > > http://debmal.my > > > > _______________________________________________ > > Xen-users mailing list > > Xen-users@lists.xen.org > > http://lists.xen.org/xen-users > > > > > ---------------------------------------------------------------- > This message was sent using IMP, the Internet Messaging Program. > > _______________________________________________ > Xen-users mailing list > Xen-users@lists.xen.org > http://lists.xen.org/xen-users > --047d7b3a7ff8dbbac904c906d686 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable

True, but I have not heard it being that slow before, also if you do go = with gluster use 3.3. if you are looking for ease of setup gluster is easy.= And drdb stops at 2 nodes doesnt it.

On Sep 5, 2012 11:08 AM, <dan@soleks.com> wrote:

=A0From my experience gluster write performance (2 mirrored nodes) is ve= ry low, approx 40-45Mb/sec. read is pretty high and it was network saturati= on =A0- appr 90-95Mb/sec (i have gigi network). For HA for VMs i'd high= ly recommend DRDB+Pacemaker+Corosync. Solution is much more advanced, and r= equires much more efforts, but output will cover all time expenses. I have = cluster of 2 nodes with DRBD, some VM images (block devices, using Logical = Volumes on top of DRDB) are up to 512G. I don't see any performance los= s. Also Pacemaker is well integrated with XEN live migration. So i think it= 's best solution for "cheap man".


> 2012/9/5 Andrew Wells <agwells0714@gmail.com>:
>> Actually look into gluster for turning your local storage into sha= red
>> storage. Works with more than one node and replicates data.
>
> thanks for for this useful info, also to everyone who shared their opi= nion
>
>
>
> --
> Regards,
>
> Umarzuki Mochlis
> http://debmal.my >
> _______________________________________________
> Xen-users mailing list
> Xen-users= @lists.xen.org
> http://li= sts.xen.org/xen-users
>


----------------------------------------------------------------
This message was sent using IMP, the Internet Messaging Program.

_______________________________________________
Xen-users mailing list
Xen-users@lists.xen.org
http://lists.x= en.org/xen-users
--047d7b3a7ff8dbbac904c906d686-- --===============8322578955727798058== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users --===============8322578955727798058==-- From xen-users-bounces@lists.xen.org Thu Sep 06 11:38:25 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Thu, 06 Sep 2012 11:38:25 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1T9aOx-00020y-JU; Thu, 06 Sep 2012 11:37:39 +0000 Received: from mail27.messagelabs.com ([193.109.254.147]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1T9Y4Z-00032z-HU for xen-users@lists.xen.org; Thu, 06 Sep 2012 09:08:27 +0000 X-Env-Sender: kks.kbase@gmail.com X-Msg-Ref: server-10.tower-27.messagelabs.com!1346922485!4658750!1 X-Originating-IP: [209.85.214.45] X-SpamReason: No, hits=0.9 required=7.0 tests=HTML_40_50,HTML_MESSAGE, ML_RADAR_SPEW_LINKS_14, ML_RADAR_SPEW_LINKS_8, RCVD_BY_IP, spamassassin: , async_handler: YXN5bmNfZGVsYXk6IDcwNTc5ODIgKHRpbWVvdXQp\n X-StarScan-Received: X-StarScan-Version: 6.6.1.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 2844 invoked from network); 6 Sep 2012 09:08:06 -0000 Received: from mail-bk0-f45.google.com (HELO mail-bk0-f45.google.com) (209.85.214.45) by server-10.tower-27.messagelabs.com with RC4-SHA encrypted SMTP; 6 Sep 2012 09:08:06 -0000 Received: by bkcji1 with SMTP id ji1so659037bkc.32 for ; Thu, 06 Sep 2012 02:08:05 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=/ZeFb2tqnREqCQnpLBePRaBhA7sP+s0yUiupkuqKYJQ=; b=IWBrQeH1WyQVe0RuMXJRPCF/dAjtGH4Kfo8qDnzSCEfozHJDsZul/LPPl9k6WA6Deq grvTuuWZAX8YrHDrt2995DuBaVXQ/og12SMKbpci7Qpqsbdg4OAIcwkzjvfEPJsoo4m5 VOPYZ4ifo/V/vCPvv3/L9A25WiGqSVlmW4SqWSwxFSB9MJ3yjyJWFfmBpaFHP6iIPJOx 09/sy90NRJm/w1b9qQcoDrie4cfwkUX7z3FQR/lVyyrolUo3vThA7Kd4uLPMEtescvqJ D46cwsIyt0W8GHvaDAg60biFB9dH3HULmZ7yhzso80qXYv2359uqwRR8EGdsLcCleO/I X8vw== MIME-Version: 1.0 Received: by 10.204.148.86 with SMTP id o22mr450399bkv.59.1346922484889; Thu, 06 Sep 2012 02:08:04 -0700 (PDT) Received: by 10.204.56.134 with HTTP; Thu, 6 Sep 2012 02:08:04 -0700 (PDT) In-Reply-To: References: Date: Thu, 6 Sep 2012 14:38:04 +0530 Message-ID: From: kk s To: Ricardo Jesus X-Mailman-Approved-At: Thu, 06 Sep 2012 11:37:37 +0000 Cc: xen-users@lists.xen.org Subject: Re: [Xen-users] [Xen-devel] Xen 4.2 rpm build X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============2814244922665145835==" Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org --===============2814244922665145835== Content-Type: multipart/alternative; boundary=0015175cd29a40788a04c904d4de --0015175cd29a40788a04c904d4de Content-Type: text/plain; charset=ISO-8859-1 Hi Richard, Thanks for pointing me. I will take look into this and update it. On Thu, Sep 6, 2012 at 2:36 PM, Ricardo Jesus wrote: > Hi, > > Did you check out > https://www.crc.id.au/xen-on-rhel6-scientific-linux-6-centos-6-howto/ > ? > Their repository provides rpm for RHEL 6.x and as far as i recall the > current available version is Xen 4.1.3. > > There's also Choon's repository for RHEL 6.x and others are listed in > Xen's Wiki. > > As allways you can check out the source rpms from these repos and > customize from there. > > Best regards, > Ricardo Jesus. > > On Thu, Sep 6, 2012 at 9:56 AM, kk s wrote: > > Hi, > > > > Can anyone provide the steps to build rpm from source for Xen 4.1.2? > > > > > > > > _______________________________________________ > > Xen-devel mailing list > > Xen-devel@lists.xen.org > > http://lists.xen.org/xen-devel > > > --0015175cd29a40788a04c904d4de Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Hi Richard,

Thanks for pointing me. I will take look into this and u= pdate it.


On Thu, Sep 6, 2012 at 2:36= PM, Ricardo Jesus <ricardo.meb.jesus@gmail.com> w= rote:
Hi,

Did you check out
https://www.crc.id.au/xen-on-rhel6-scientific-linu= x-6-centos-6-howto/
?
Their repository provides rpm for RHEL 6.x and as far as i recall the
current available version is Xen 4.1.3.

There's also Choon's repository for RHEL 6.x and others are listed = in
Xen's Wiki.

As allways you can check out the source rpms from these repos and
customize from there.

Best regards,
Ricardo Jesus.

On Thu, Sep 6, 2012 at 9:56 AM, kk s <kks.kbase@gmail.com> wrote:
> Hi,
>
> Can anyone provide the steps to build rpm from source for Xen 4.1.2? >
>
>
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xen.org=
> http://li= sts.xen.org/xen-devel
>

--0015175cd29a40788a04c904d4de-- --===============2814244922665145835== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users --===============2814244922665145835==-- From xen-users-bounces@lists.xen.org Thu Sep 06 11:38:25 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Thu, 06 Sep 2012 11:38:25 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1T9aOx-00020y-JU; Thu, 06 Sep 2012 11:37:39 +0000 Received: from mail27.messagelabs.com ([193.109.254.147]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1T9Y4Z-00032z-HU for xen-users@lists.xen.org; Thu, 06 Sep 2012 09:08:27 +0000 X-Env-Sender: kks.kbase@gmail.com X-Msg-Ref: server-10.tower-27.messagelabs.com!1346922485!4658750!1 X-Originating-IP: [209.85.214.45] X-SpamReason: No, hits=0.9 required=7.0 tests=HTML_40_50,HTML_MESSAGE, ML_RADAR_SPEW_LINKS_14, ML_RADAR_SPEW_LINKS_8, RCVD_BY_IP, spamassassin: , async_handler: YXN5bmNfZGVsYXk6IDcwNTc5ODIgKHRpbWVvdXQp\n X-StarScan-Received: X-StarScan-Version: 6.6.1.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 2844 invoked from network); 6 Sep 2012 09:08:06 -0000 Received: from mail-bk0-f45.google.com (HELO mail-bk0-f45.google.com) (209.85.214.45) by server-10.tower-27.messagelabs.com with RC4-SHA encrypted SMTP; 6 Sep 2012 09:08:06 -0000 Received: by bkcji1 with SMTP id ji1so659037bkc.32 for ; Thu, 06 Sep 2012 02:08:05 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=/ZeFb2tqnREqCQnpLBePRaBhA7sP+s0yUiupkuqKYJQ=; b=IWBrQeH1WyQVe0RuMXJRPCF/dAjtGH4Kfo8qDnzSCEfozHJDsZul/LPPl9k6WA6Deq grvTuuWZAX8YrHDrt2995DuBaVXQ/og12SMKbpci7Qpqsbdg4OAIcwkzjvfEPJsoo4m5 VOPYZ4ifo/V/vCPvv3/L9A25WiGqSVlmW4SqWSwxFSB9MJ3yjyJWFfmBpaFHP6iIPJOx 09/sy90NRJm/w1b9qQcoDrie4cfwkUX7z3FQR/lVyyrolUo3vThA7Kd4uLPMEtescvqJ D46cwsIyt0W8GHvaDAg60biFB9dH3HULmZ7yhzso80qXYv2359uqwRR8EGdsLcCleO/I X8vw== MIME-Version: 1.0 Received: by 10.204.148.86 with SMTP id o22mr450399bkv.59.1346922484889; Thu, 06 Sep 2012 02:08:04 -0700 (PDT) Received: by 10.204.56.134 with HTTP; Thu, 6 Sep 2012 02:08:04 -0700 (PDT) In-Reply-To: References: Date: Thu, 6 Sep 2012 14:38:04 +0530 Message-ID: From: kk s To: Ricardo Jesus X-Mailman-Approved-At: Thu, 06 Sep 2012 11:37:37 +0000 Cc: xen-users@lists.xen.org Subject: Re: [Xen-users] [Xen-devel] Xen 4.2 rpm build X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============2814244922665145835==" Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org --===============2814244922665145835== Content-Type: multipart/alternative; boundary=0015175cd29a40788a04c904d4de --0015175cd29a40788a04c904d4de Content-Type: text/plain; charset=ISO-8859-1 Hi Richard, Thanks for pointing me. I will take look into this and update it. On Thu, Sep 6, 2012 at 2:36 PM, Ricardo Jesus wrote: > Hi, > > Did you check out > https://www.crc.id.au/xen-on-rhel6-scientific-linux-6-centos-6-howto/ > ? > Their repository provides rpm for RHEL 6.x and as far as i recall the > current available version is Xen 4.1.3. > > There's also Choon's repository for RHEL 6.x and others are listed in > Xen's Wiki. > > As allways you can check out the source rpms from these repos and > customize from there. > > Best regards, > Ricardo Jesus. > > On Thu, Sep 6, 2012 at 9:56 AM, kk s wrote: > > Hi, > > > > Can anyone provide the steps to build rpm from source for Xen 4.1.2? > > > > > > > > _______________________________________________ > > Xen-devel mailing list > > Xen-devel@lists.xen.org > > http://lists.xen.org/xen-devel > > > --0015175cd29a40788a04c904d4de Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Hi Richard,

Thanks for pointing me. I will take look into this and u= pdate it.


On Thu, Sep 6, 2012 at 2:36= PM, Ricardo Jesus <ricardo.meb.jesus@gmail.com> w= rote:
Hi,

Did you check out
https://www.crc.id.au/xen-on-rhel6-scientific-linu= x-6-centos-6-howto/
?
Their repository provides rpm for RHEL 6.x and as far as i recall the
current available version is Xen 4.1.3.

There's also Choon's repository for RHEL 6.x and others are listed = in
Xen's Wiki.

As allways you can check out the source rpms from these repos and
customize from there.

Best regards,
Ricardo Jesus.

On Thu, Sep 6, 2012 at 9:56 AM, kk s <kks.kbase@gmail.com> wrote:
> Hi,
>
> Can anyone provide the steps to build rpm from source for Xen 4.1.2? >
>
>
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xen.org=
> http://li= sts.xen.org/xen-devel
>

--0015175cd29a40788a04c904d4de-- --===============2814244922665145835== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users --===============2814244922665145835==-- From xen-users-bounces@lists.xen.org Thu Sep 06 11:38:26 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Thu, 06 Sep 2012 11:38:26 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1T9aOy-00021C-9Y; Thu, 06 Sep 2012 11:37:40 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1T9Y55-00036x-Rb for xen-users@lists.xen.org; Thu, 06 Sep 2012 09:09:00 +0000 Received: from [85.158.138.51:43682] by server-12.bemta-3.messagelabs.com id C5/4A-10384-A2868405; Thu, 06 Sep 2012 09:08:58 +0000 X-Env-Sender: kks.kbase@gmail.com X-Msg-Ref: server-5.tower-174.messagelabs.com!1346922536!29062103!1 X-Originating-IP: [209.85.214.45] X-SpamReason: No, hits=0.9 required=7.0 tests=HTML_40_50,HTML_MESSAGE, ML_RADAR_SPEW_LINKS_14,RCVD_BY_IP,spamassassin: X-StarScan-Received: X-StarScan-Version: 6.6.1.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 21746 invoked from network); 6 Sep 2012 09:08:56 -0000 Received: from mail-bk0-f45.google.com (HELO mail-bk0-f45.google.com) (209.85.214.45) by server-5.tower-174.messagelabs.com with RC4-SHA encrypted SMTP; 6 Sep 2012 09:08:56 -0000 Received: by bkcji1 with SMTP id ji1so659471bkc.32 for ; Thu, 06 Sep 2012 02:08:56 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=SOOv7sUmIDAPjfyj2g9cQZ2zdyjmkSxCKdSjoKNaHGo=; b=fo+MT4ThDxyniKW0rTsFlx45nRLUYRCRWfv/jpdAvvPHSfS5Kw5fCsDTiZj/RjcPlG SVJBa6Qtq63sXnBKWxZxGlEfPlE30VPZ9o/Rm/QykVT6EWpqpKzttyOgl60D5tJTr6Zc dnp+RrAMKmIdyyTA8jYvebxAuxrdFtlctHe9E0097qkqvkPuZzyVzwMTM41uxqH6EFZl FRtzHWDW3CoZMNZr4gwZ0B1Gu6Tc0IpizweXdSdRytxG84XiJo5HWTHCmPWXneUUz7lh BmWFdNY8Yt+dJlGPUjPXr0SmiJA5zWndhoi+0Sswicx2+PjQUOh66kHeJwUV59g86R4q w/xw== MIME-Version: 1.0 Received: by 10.205.127.72 with SMTP id gz8mr422122bkc.121.1346922536405; Thu, 06 Sep 2012 02:08:56 -0700 (PDT) Received: by 10.204.56.134 with HTTP; Thu, 6 Sep 2012 02:08:56 -0700 (PDT) In-Reply-To: <1346921802.23055.26.camel@zakaz.uk.xensource.com> References: <1346921802.23055.26.camel@zakaz.uk.xensource.com> Date: Thu, 6 Sep 2012 14:38:56 +0530 Message-ID: From: kk s To: Ian Campbell X-Mailman-Approved-At: Thu, 06 Sep 2012 11:37:37 +0000 Cc: "xen-users@lists.xen.org" , "xen-devel@lists.xen.org" Subject: Re: [Xen-users] [Xen-devel] Security patches X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============5975442184366754390==" Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org --===============5975442184366754390== Content-Type: multipart/alternative; boundary=0015173fe992528c2804c904d71e --0015173fe992528c2804c904d71e Content-Type: text/plain; charset=ISO-8859-1 Hi Ian, Thanks for your reply. Sorry to bother you with this. I am bit confused and so I am asking to make clear myself. Reg CVE-2012-2934 - http://lists.xen.org/archives/html/xen-announce/2012-06/msg00002.html Is Xen 3.4 too affected with this vulnerable? If so I couldn't find the patch for xen 3.4 and it does exit for xen 4.x only. I don't how to apply the following patches since I have created rpm with patches applied that included as downloadable file. But for these patches I am not seeing any downloadable file. http://lists.xen.org/archives/html/xen-devel/2012-02/msg00212.html http://lists.xen.org/archives/html/xen-devel/2012-07/msg01649.html http://lists.xen.org/archives/html/xen-devel/2012-08/msg00855.html If you can clear this for me that would be great :) I hope that I am replying in correct way. On Thu, Sep 6, 2012 at 2:26 PM, Ian Campbell wrote: > On Thu, 2012-09-06 at 09:31 +0100, kk s wrote: > > Hi, > > > > Can anyone give the patch file download link for the below xen > > security for xen version 3.4 and 4.1? Since I couldn't find the > > downloadable patch file for some of the CVE's. > > > > CVE-2012-0029 - > http://lists.xen.org/archives/html/xen-devel/2012-02/msg00212.html (There is no download link for both xen 3.4 and 4.1) > > CVE-2012-2934 - > http://lists.xen.org/archives/html/xen-announce/2012-06/msg00002.html (There is no patch file to download of xen 3.4) > > CVE-2012-3432 - > http://lists.xen.org/archives/html/xen-devel/2012-07/msg01649.html (There is no download link for both xen 3.4 and 4.1) > > CVE-2012-3433 - > http://lists.xen.org/archives/html/xen-devel/2012-08/msg00855.html (There is no download link for both xen 3.4 and 4.1) > > It looks to me like there are changeset references and/or patches for > all of these in the advisories. You might find it easier to follow: > http://wiki.xen.org/wiki/Security_Announcements > > You can also always look in the appropriate xen-X.Y-testing.hg tree for > the fix. > > > CVE-2012-3497 - > http://lists.xen.org/archives/html/xen-announce/2012-09/msg00006.html (There is no download link for patch) > > This is quite clearly explained in the advisory. > > > Also I have some doubts for the below CVE's. > > > > CVE-2012-3496 - Is this vulnerability affected for xen 4.x only or it > > does include for xen 3.4 too? Since the patch name was > > xsa14-xen-3.4-and-4.x.patch > > http://lists.xen.org/archives/html/xen-announce/2012-09/msg00002.html > > Yes, it looks like this effects 3.4 too. > > > CVE-2012-3516 - Shall I apply this unstable for patch for xen4.2 too? > > http://lists.xen.org/archives/html/xen-announce/2012-09/msg00004.html > > The advisory says "Xen-unstable, including Xen 4.2 release candidates > are vulnerable to this issue.", so yes, obviously. > > In the future please carefully read the advisories before asking lots of > questions, almost everything you have asked is addressed in the advisory > texts AFAICT. > > Ian. > > > --0015173fe992528c2804c904d71e Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Hi Ian,

Thanks for your reply. Sorry to bother you with this. I am b= it confused and so I am asking to make clear myself.

Reg CVE-2012-2934 - http= ://lists.xen.org/archives/html/xen-announce/2012-06/msg00002.html Is Xen 3.4 too affected with this vulnerable? If so I couldn't= find the patch for xen 3.4 and it does exit for xen 4.x only.

I don't how to apply the following patches since I have created rpm= =20 with patches applied that included as downloadable file. But for these=20 patches I am not seeing any downloadable file.

http://lists.xen.org/archives/html/xen-devel/2012-02/msg00212.html
http://lists.xen.org/archives/html/xen-devel/2012-07/= msg01649.html
http://lists.xen.org/archives/ht= ml/xen-devel/2012-08/msg00855.html

If you can clear this for me that would be great :)

I hope that = I am replying in correct way.


On Thu,= Sep 6, 2012 at 2:26 PM, Ian Campbell <Ian.Campbell@citrix.com&g= t; wrote:
On Thu, 2012-09-06 at 09:3= 1 +0100, kk s wrote:
> Hi,
>
> Can anyone give the patch file download link for the below xen
> security for xen version 3.4 and 4.1? Since I couldn't find the > downloadable patch file for some of the CVE's.
>
> CVE-2012-0029 =A0 - http://lists.xen.org/archive= s/html/xen-devel/2012-02/msg00212.html =A0(There is no download link fo= r both xen 3.4 and 4.1)
> CVE-2012-2934 =A0 - http://lists.xen.org/arch= ives/html/xen-announce/2012-06/msg00002.html =A0(There is no patch file= to download of xen 3.4)
> CVE-2012-3432 =A0 - http://lists.xen.org/archive= s/html/xen-devel/2012-07/msg01649.html =A0(There is no download link fo= r both xen 3.4 and 4.1)
> CVE-2012-3433 =A0 - http://lists.xen.org/archive= s/html/xen-devel/2012-08/msg00855.html =A0(There is no download link fo= r both xen 3.4 and 4.1)

It looks to me like there are changeset references and/or patches for=
all of these in the advisories. You might find it easier to follow:
=A0 =A0 =A0 =A0 http://wiki.xen.org/wiki/Security_Announcements

You can also always look in the appropriate xen-X.Y-testing.hg tree for
the fix.

> CVE-2012-3497 =A0 - http://lists.xen.org/arch= ives/html/xen-announce/2012-09/msg00006.html =A0(There is no download l= ink for patch)

This is quite clearly explained in the advisory.

> Also I have some doubts for the below CVE's.
>
> CVE-2012-3496 =A0- Is this vulnerability affected for xen 4.x only or = it
> does include for xen 3.4 too? Since the patch name was
> xsa14-xen-3.4-and-4.x.patch
> http://lists.xen.org/archives/html/xen-announ= ce/2012-09/msg00002.html

Yes, it looks like this effects 3.4 too.

> CVE-2012-3516 =A0- Shall I apply this unstable for patch for xen4.2 to= o?
> http://lists.xen.org/archives/html/xen-announ= ce/2012-09/msg00004.html

The advisory says "Xen-unstable, including Xen 4.2 release candi= dates
are vulnerable to this issue.", so yes, obviously.

In the future please carefully read the advisories before asking lots of questions, almost everything you have asked is addressed in the advisory texts AFAICT.

Ian.



--0015173fe992528c2804c904d71e-- --===============5975442184366754390== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users --===============5975442184366754390==-- From xen-users-bounces@lists.xen.org Thu Sep 06 11:38:26 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Thu, 06 Sep 2012 11:38:26 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1T9aOy-00021C-9Y; Thu, 06 Sep 2012 11:37:40 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1T9Y55-00036x-Rb for xen-users@lists.xen.org; Thu, 06 Sep 2012 09:09:00 +0000 Received: from [85.158.138.51:43682] by server-12.bemta-3.messagelabs.com id C5/4A-10384-A2868405; Thu, 06 Sep 2012 09:08:58 +0000 X-Env-Sender: kks.kbase@gmail.com X-Msg-Ref: server-5.tower-174.messagelabs.com!1346922536!29062103!1 X-Originating-IP: [209.85.214.45] X-SpamReason: No, hits=0.9 required=7.0 tests=HTML_40_50,HTML_MESSAGE, ML_RADAR_SPEW_LINKS_14,RCVD_BY_IP,spamassassin: X-StarScan-Received: X-StarScan-Version: 6.6.1.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 21746 invoked from network); 6 Sep 2012 09:08:56 -0000 Received: from mail-bk0-f45.google.com (HELO mail-bk0-f45.google.com) (209.85.214.45) by server-5.tower-174.messagelabs.com with RC4-SHA encrypted SMTP; 6 Sep 2012 09:08:56 -0000 Received: by bkcji1 with SMTP id ji1so659471bkc.32 for ; Thu, 06 Sep 2012 02:08:56 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=SOOv7sUmIDAPjfyj2g9cQZ2zdyjmkSxCKdSjoKNaHGo=; b=fo+MT4ThDxyniKW0rTsFlx45nRLUYRCRWfv/jpdAvvPHSfS5Kw5fCsDTiZj/RjcPlG SVJBa6Qtq63sXnBKWxZxGlEfPlE30VPZ9o/Rm/QykVT6EWpqpKzttyOgl60D5tJTr6Zc dnp+RrAMKmIdyyTA8jYvebxAuxrdFtlctHe9E0097qkqvkPuZzyVzwMTM41uxqH6EFZl FRtzHWDW3CoZMNZr4gwZ0B1Gu6Tc0IpizweXdSdRytxG84XiJo5HWTHCmPWXneUUz7lh BmWFdNY8Yt+dJlGPUjPXr0SmiJA5zWndhoi+0Sswicx2+PjQUOh66kHeJwUV59g86R4q w/xw== MIME-Version: 1.0 Received: by 10.205.127.72 with SMTP id gz8mr422122bkc.121.1346922536405; Thu, 06 Sep 2012 02:08:56 -0700 (PDT) Received: by 10.204.56.134 with HTTP; Thu, 6 Sep 2012 02:08:56 -0700 (PDT) In-Reply-To: <1346921802.23055.26.camel@zakaz.uk.xensource.com> References: <1346921802.23055.26.camel@zakaz.uk.xensource.com> Date: Thu, 6 Sep 2012 14:38:56 +0530 Message-ID: From: kk s To: Ian Campbell X-Mailman-Approved-At: Thu, 06 Sep 2012 11:37:37 +0000 Cc: "xen-users@lists.xen.org" , "xen-devel@lists.xen.org" Subject: Re: [Xen-users] [Xen-devel] Security patches X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============5975442184366754390==" Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org --===============5975442184366754390== Content-Type: multipart/alternative; boundary=0015173fe992528c2804c904d71e --0015173fe992528c2804c904d71e Content-Type: text/plain; charset=ISO-8859-1 Hi Ian, Thanks for your reply. Sorry to bother you with this. I am bit confused and so I am asking to make clear myself. Reg CVE-2012-2934 - http://lists.xen.org/archives/html/xen-announce/2012-06/msg00002.html Is Xen 3.4 too affected with this vulnerable? If so I couldn't find the patch for xen 3.4 and it does exit for xen 4.x only. I don't how to apply the following patches since I have created rpm with patches applied that included as downloadable file. But for these patches I am not seeing any downloadable file. http://lists.xen.org/archives/html/xen-devel/2012-02/msg00212.html http://lists.xen.org/archives/html/xen-devel/2012-07/msg01649.html http://lists.xen.org/archives/html/xen-devel/2012-08/msg00855.html If you can clear this for me that would be great :) I hope that I am replying in correct way. On Thu, Sep 6, 2012 at 2:26 PM, Ian Campbell wrote: > On Thu, 2012-09-06 at 09:31 +0100, kk s wrote: > > Hi, > > > > Can anyone give the patch file download link for the below xen > > security for xen version 3.4 and 4.1? Since I couldn't find the > > downloadable patch file for some of the CVE's. > > > > CVE-2012-0029 - > http://lists.xen.org/archives/html/xen-devel/2012-02/msg00212.html (There is no download link for both xen 3.4 and 4.1) > > CVE-2012-2934 - > http://lists.xen.org/archives/html/xen-announce/2012-06/msg00002.html (There is no patch file to download of xen 3.4) > > CVE-2012-3432 - > http://lists.xen.org/archives/html/xen-devel/2012-07/msg01649.html (There is no download link for both xen 3.4 and 4.1) > > CVE-2012-3433 - > http://lists.xen.org/archives/html/xen-devel/2012-08/msg00855.html (There is no download link for both xen 3.4 and 4.1) > > It looks to me like there are changeset references and/or patches for > all of these in the advisories. You might find it easier to follow: > http://wiki.xen.org/wiki/Security_Announcements > > You can also always look in the appropriate xen-X.Y-testing.hg tree for > the fix. > > > CVE-2012-3497 - > http://lists.xen.org/archives/html/xen-announce/2012-09/msg00006.html (There is no download link for patch) > > This is quite clearly explained in the advisory. > > > Also I have some doubts for the below CVE's. > > > > CVE-2012-3496 - Is this vulnerability affected for xen 4.x only or it > > does include for xen 3.4 too? Since the patch name was > > xsa14-xen-3.4-and-4.x.patch > > http://lists.xen.org/archives/html/xen-announce/2012-09/msg00002.html > > Yes, it looks like this effects 3.4 too. > > > CVE-2012-3516 - Shall I apply this unstable for patch for xen4.2 too? > > http://lists.xen.org/archives/html/xen-announce/2012-09/msg00004.html > > The advisory says "Xen-unstable, including Xen 4.2 release candidates > are vulnerable to this issue.", so yes, obviously. > > In the future please carefully read the advisories before asking lots of > questions, almost everything you have asked is addressed in the advisory > texts AFAICT. > > Ian. > > > --0015173fe992528c2804c904d71e Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Hi Ian,

Thanks for your reply. Sorry to bother you with this. I am b= it confused and so I am asking to make clear myself.

Reg CVE-2012-2934 - http= ://lists.xen.org/archives/html/xen-announce/2012-06/msg00002.html Is Xen 3.4 too affected with this vulnerable? If so I couldn't= find the patch for xen 3.4 and it does exit for xen 4.x only.

I don't how to apply the following patches since I have created rpm= =20 with patches applied that included as downloadable file. But for these=20 patches I am not seeing any downloadable file.

http://lists.xen.org/archives/html/xen-devel/2012-02/msg00212.html
http://lists.xen.org/archives/html/xen-devel/2012-07/= msg01649.html
http://lists.xen.org/archives/ht= ml/xen-devel/2012-08/msg00855.html

If you can clear this for me that would be great :)

I hope that = I am replying in correct way.


On Thu,= Sep 6, 2012 at 2:26 PM, Ian Campbell <Ian.Campbell@citrix.com&g= t; wrote:
On Thu, 2012-09-06 at 09:3= 1 +0100, kk s wrote:
> Hi,
>
> Can anyone give the patch file download link for the below xen
> security for xen version 3.4 and 4.1? Since I couldn't find the > downloadable patch file for some of the CVE's.
>
> CVE-2012-0029 =A0 - http://lists.xen.org/archive= s/html/xen-devel/2012-02/msg00212.html =A0(There is no download link fo= r both xen 3.4 and 4.1)
> CVE-2012-2934 =A0 - http://lists.xen.org/arch= ives/html/xen-announce/2012-06/msg00002.html =A0(There is no patch file= to download of xen 3.4)
> CVE-2012-3432 =A0 - http://lists.xen.org/archive= s/html/xen-devel/2012-07/msg01649.html =A0(There is no download link fo= r both xen 3.4 and 4.1)
> CVE-2012-3433 =A0 - http://lists.xen.org/archive= s/html/xen-devel/2012-08/msg00855.html =A0(There is no download link fo= r both xen 3.4 and 4.1)

It looks to me like there are changeset references and/or patches for=
all of these in the advisories. You might find it easier to follow:
=A0 =A0 =A0 =A0 http://wiki.xen.org/wiki/Security_Announcements

You can also always look in the appropriate xen-X.Y-testing.hg tree for
the fix.

> CVE-2012-3497 =A0 - http://lists.xen.org/arch= ives/html/xen-announce/2012-09/msg00006.html =A0(There is no download l= ink for patch)

This is quite clearly explained in the advisory.

> Also I have some doubts for the below CVE's.
>
> CVE-2012-3496 =A0- Is this vulnerability affected for xen 4.x only or = it
> does include for xen 3.4 too? Since the patch name was
> xsa14-xen-3.4-and-4.x.patch
> http://lists.xen.org/archives/html/xen-announ= ce/2012-09/msg00002.html

Yes, it looks like this effects 3.4 too.

> CVE-2012-3516 =A0- Shall I apply this unstable for patch for xen4.2 to= o?
> http://lists.xen.org/archives/html/xen-announ= ce/2012-09/msg00004.html

The advisory says "Xen-unstable, including Xen 4.2 release candi= dates
are vulnerable to this issue.", so yes, obviously.

In the future please carefully read the advisories before asking lots of questions, almost everything you have asked is addressed in the advisory texts AFAICT.

Ian.



--0015173fe992528c2804c904d71e-- --===============5975442184366754390== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users --===============5975442184366754390==-- From xen-users-bounces@lists.xen.org Thu Sep 06 11:38:26 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Thu, 06 Sep 2012 11:38:26 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1T9aOz-00021j-L3; Thu, 06 Sep 2012 11:37:41 +0000 Received: from mail27.messagelabs.com ([193.109.254.147]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1T9Zfw-0007Oh-JV; Thu, 06 Sep 2012 10:51:08 +0000 X-Env-Sender: kks.kbase@gmail.com X-Msg-Ref: server-14.tower-27.messagelabs.com!1346928655!2849028!1 X-Originating-IP: [209.85.214.45] X-SpamReason: No, hits=0.4 required=7.0 tests=HTML_30_40,HTML_MESSAGE, ML_RADAR_SPEW_LINKS_14,RCVD_BY_IP,spamassassin: X-StarScan-Received: X-StarScan-Version: 6.6.1.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 31892 invoked from network); 6 Sep 2012 10:50:55 -0000 Received: from mail-bk0-f45.google.com (HELO mail-bk0-f45.google.com) (209.85.214.45) by server-14.tower-27.messagelabs.com with RC4-SHA encrypted SMTP; 6 Sep 2012 10:50:55 -0000 Received: by bkcji1 with SMTP id ji1so715084bkc.32 for ; Thu, 06 Sep 2012 03:50:55 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=V7/Vv9Jz8UEIn0Z+MytWrJHC7wUcL5sz5JRRZW0A82M=; b=0vCa3+dcFfyoqlIQpUTSM0TlVZVfZGIHyKajGdLGjrBe84e3WA1uOUw4c4i7d0kDkj /42fmUTTl/GrsF5tWt/FTrJzX2uz1ieQkzIkSD/eo+RH0AIqyfHa2+BVGIuzp+ABpCpx lbCEf8PYeCYOPceySCuS9qocp1X4KNT285wbVvtSjGYV3kmQVjL1PLTvfmob21ebbRfQ Zz2UZyngW6s/ZSuHHi3/7Ch5X4oQUAMCBxHKFsSHxiuy5TciKzJq9SBg0+NCbsljSd35 Sp+eC+Jt6caynZd094zOlvPPQG2vC8iC462EdgbYH4LzeKaDWb+pfz1FEN0Q3sCdjvV3 A3fA== MIME-Version: 1.0 Received: by 10.204.130.156 with SMTP id t28mr667416bks.33.1346928654792; Thu, 06 Sep 2012 03:50:54 -0700 (PDT) Received: by 10.204.56.134 with HTTP; Thu, 6 Sep 2012 03:50:54 -0700 (PDT) In-Reply-To: <1346922837.23055.33.camel@zakaz.uk.xensource.com> References: <1346921802.23055.26.camel@zakaz.uk.xensource.com> <1346922837.23055.33.camel@zakaz.uk.xensource.com> Date: Thu, 6 Sep 2012 16:20:54 +0530 Message-ID: From: kk s To: Ian Campbell X-Mailman-Approved-At: Thu, 06 Sep 2012 11:37:37 +0000 Cc: "xen-users@lists.xen.org" , "xen-devel@lists.xen.org" Subject: Re: [Xen-users] [Xen-devel] Security patches X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============7455325383689370311==" Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org --===============7455325383689370311== Content-Type: multipart/alternative; boundary=00151743f82e01b70504c9064409 --00151743f82e01b70504c9064409 Content-Type: text/plain; charset=ISO-8859-1 Hi, It looks like the patch that has been provided on Xen Security Advisory 11 (CVE-2012-3433) doesn't applied for Xen 3.4.4. When I try to apply this patch and I am getting the below error, 1 out of 1 hunk FAILED -- saving rejects to file xen/arch/x86/mm/p2m.c.rej 1 out of 1 hunk FAILED -- saving rejects to file xen/arch/x86/mm/p2m.c.rej Seems there is no for loop "for ( gfn=0; gfn < p2m->max_mapped_pfn; gfn++ )" on xen/arch/x86/mm/p2m.c.rej on xen3.4.4 source instead if loop only exists. p2m.c: && (gfn + (1UL << page_order) - 1 > d->arch.p2m->max_mapped_pfn) ) p2m.c: d->arch.p2m->max_mapped_pfn = gfn + (1UL << page_order) - 1; p2m.c: if ( gfn > d->arch.p2m->max_mapped_pfn ) p2m.c: if ( gfn <= current->domain->arch.p2m->max_mapped_pfn ) p2m.c: if ( test_linear && (gfn <= d->arch.p2m->max_mapped_pfn) ) p2m.c.orig: && (gfn + (1UL << page_order) - 1 > d->arch.p2m->max_mapped_pfn) ) p2m.c.orig: d->arch.p2m->max_mapped_pfn = gfn + (1UL << page_order) - 1; p2m.c.orig: if ( gfn > d->arch.p2m->max_mapped_pfn ) p2m.c.orig: if ( gfn <= current->domain->arch.p2m->max_mapped_pfn ) p2m.c.orig: if ( test_linear && (gfn <= d->arch.p2m->max_mapped_pfn) ) p2m.c.rej: for ( gfn=0; gfn < p2m->max_mapped_pfn; gfn++ ) p2m.c.rej: for ( gfn=0; gfn < p2m->max_mapped_pfn; gfn++ ) So I guess this patch applicable for Xen 4.x only. If you update the patch for Xen 3.4 that would be great. On Thu, Sep 6, 2012 at 2:43 PM, Ian Campbell wrote: > On Thu, 2012-09-06 at 10:08 +0100, kk s wrote: > > Hi Ian, > > > > Thanks for your reply. Sorry to bother you with this. I am bit > > confused and so I am asking to make clear myself. > > > > Reg CVE-2012-2934 - > > http://lists.xen.org/archives/html/xen-announce/2012-06/msg00002.html > > Is Xen 3.4 too affected with this vulnerable? If so I couldn't find > > the patch for xen 3.4 and it does exit for xen 4.x only. > > I expect it does effect 3.4, but only if you are running on one of the > listed processors. > > security@xen.org doesn't provide security support for 3.4 any more. If > you aren't able to backport the 4.0 patch yourself, you would need to > speak to Keith Coleman who is the 3.4 stable maintainer. > > > I don't how to apply the following patches since I have created rpm > > with patches applied that included as downloadable file. But for these > > patches I am not seeing any downloadable file. > > > > http://lists.xen.org/archives/html/xen-devel/2012-02/msg00212.html > > http://lists.xen.org/archives/html/xen-devel/2012-07/msg01649.html > > http://lists.xen.org/archives/html/xen-devel/2012-08/msg00855.html > > > > If you can clear this for me that would be great :) > > I already pointed you at http://wiki.xen.org/wiki/Security_Announcements > which should have all the links you need. > > > --00151743f82e01b70504c9064409 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable
Hi,

It looks like the patch that has been= provided on Xen Security Advisory 11 (CVE-2012-3433) doesn't applied f= or Xen 3.4.4.

When I try to apply this patch and I= am getting the below error,

1 out of 1 hunk FAILED -- saving rejects to file xen/ar= ch/x86/mm/p2m.c.rej
1 out of 1 hunk FAILED -- saving rejects to file xen= /arch/x86/mm/p2m.c.rej

Seems there is no for loop = "for ( gfn=3D0; gfn < p2m->max_mapped_pfn; gfn++ )" on xen/= arch/x86/mm/p2m.c.rej on xen3.4.4 source instead if loop only exists.

p2m.c: && (gfn + (1UL << page_ord= er) - 1 > d->arch.p2m->max_mapped_pfn) )
p2m.c: d->ar= ch.p2m->max_mapped_pfn =3D gfn + (1UL << page_order) - 1;
p2m.c= : if ( gfn > d->arch.p2m->max_mapped_pfn )
p2m.c: if ( gfn <=3D current->domain->arch.p2m->max_mapped_p= fn )
p2m.c: if ( test_linear && (gfn <=3D d->arch.p= 2m->max_mapped_pfn) )
p2m.c.orig: && (gfn + (1UL <= < page_order) - 1 > d->arch.p2m->max_mapped_pfn) )
p2m.c.orig: d->arch.p2m->max_mapped_pfn =3D gfn + (1UL <<= ; page_order) - 1;
p2m.c.orig: if ( gfn > d->arch.p2m->max_m= apped_pfn )
p2m.c.orig: if ( gfn <=3D current->domain->arch.= p2m->max_mapped_pfn )
p2m.c.orig: if ( test_linear && (gfn <=3D d->arch.p2m-= >max_mapped_pfn) )
p2m.c.rej: for ( gfn=3D0; gfn < p2m->ma= x_mapped_pfn; gfn++ )
p2m.c.rej: for ( gfn=3D0; gfn < p2m->ma= x_mapped_pfn; gfn++ )

So I guess this patch applicable for Xen 4.x only. If y= ou update the patch for Xen 3.4 that would be great.

On Thu, Sep 6, 2012 at 2:43 PM, Ian Campbell <= span dir=3D"ltr"><Ian.Campbell@citrix.com> wrote:
On Thu, 2012-09-06 at 10:0= 8 +0100, kk s wrote:
> Hi Ian,
>
> Thanks for your reply. Sorry to bother you with this. I am bit
> confused and so I am asking to make clear myself.
>
> Reg CVE-2012-2934 -
> http://lists.xen.org/archives/html/xen-announ= ce/2012-06/msg00002.html
> Is Xen 3.4 too affected with this vulnerable? If so I couldn't fin= d
> the patch for xen 3.4 and it does exit for xen 4.x only.

I expect it does effect 3.4, but only if you are running on one of th= e
listed processors.

security@xen.org doesn't provid= e security support for 3.4 any more. If
you aren't able to backport the 4.0 patch yourself, you would need to speak to Keith Coleman who is the 3.4 stable maintainer.

> I don't how to apply the following patches since I have created rp= m
> with patches applied that included as downloadable file. But for these=
> patches I am not seeing any downloadable file.
>
> http://lists.xen.org/archives/html/xen-devel/201= 2-02/msg00212.html
> http://lists.xen.org/archives/html/xen-devel/201= 2-07/msg01649.html
> http://lists.xen.org/archives/html/xen-devel/201= 2-08/msg00855.html
>
> If you can clear this for me that would be great :)

I already pointed you at http://wiki.xen.org/wiki/Security_Announc= ements
which should have all the links you need.



--00151743f82e01b70504c9064409-- --===============7455325383689370311== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users --===============7455325383689370311==-- From xen-users-bounces@lists.xen.org Thu Sep 06 11:38:26 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Thu, 06 Sep 2012 11:38:26 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1T9aOz-00021j-L3; Thu, 06 Sep 2012 11:37:41 +0000 Received: from mail27.messagelabs.com ([193.109.254.147]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1T9Zfw-0007Oh-JV; Thu, 06 Sep 2012 10:51:08 +0000 X-Env-Sender: kks.kbase@gmail.com X-Msg-Ref: server-14.tower-27.messagelabs.com!1346928655!2849028!1 X-Originating-IP: [209.85.214.45] X-SpamReason: No, hits=0.4 required=7.0 tests=HTML_30_40,HTML_MESSAGE, ML_RADAR_SPEW_LINKS_14,RCVD_BY_IP,spamassassin: X-StarScan-Received: X-StarScan-Version: 6.6.1.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 31892 invoked from network); 6 Sep 2012 10:50:55 -0000 Received: from mail-bk0-f45.google.com (HELO mail-bk0-f45.google.com) (209.85.214.45) by server-14.tower-27.messagelabs.com with RC4-SHA encrypted SMTP; 6 Sep 2012 10:50:55 -0000 Received: by bkcji1 with SMTP id ji1so715084bkc.32 for ; Thu, 06 Sep 2012 03:50:55 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=V7/Vv9Jz8UEIn0Z+MytWrJHC7wUcL5sz5JRRZW0A82M=; b=0vCa3+dcFfyoqlIQpUTSM0TlVZVfZGIHyKajGdLGjrBe84e3WA1uOUw4c4i7d0kDkj /42fmUTTl/GrsF5tWt/FTrJzX2uz1ieQkzIkSD/eo+RH0AIqyfHa2+BVGIuzp+ABpCpx lbCEf8PYeCYOPceySCuS9qocp1X4KNT285wbVvtSjGYV3kmQVjL1PLTvfmob21ebbRfQ Zz2UZyngW6s/ZSuHHi3/7Ch5X4oQUAMCBxHKFsSHxiuy5TciKzJq9SBg0+NCbsljSd35 Sp+eC+Jt6caynZd094zOlvPPQG2vC8iC462EdgbYH4LzeKaDWb+pfz1FEN0Q3sCdjvV3 A3fA== MIME-Version: 1.0 Received: by 10.204.130.156 with SMTP id t28mr667416bks.33.1346928654792; Thu, 06 Sep 2012 03:50:54 -0700 (PDT) Received: by 10.204.56.134 with HTTP; Thu, 6 Sep 2012 03:50:54 -0700 (PDT) In-Reply-To: <1346922837.23055.33.camel@zakaz.uk.xensource.com> References: <1346921802.23055.26.camel@zakaz.uk.xensource.com> <1346922837.23055.33.camel@zakaz.uk.xensource.com> Date: Thu, 6 Sep 2012 16:20:54 +0530 Message-ID: From: kk s To: Ian Campbell X-Mailman-Approved-At: Thu, 06 Sep 2012 11:37:37 +0000 Cc: "xen-users@lists.xen.org" , "xen-devel@lists.xen.org" Subject: Re: [Xen-users] [Xen-devel] Security patches X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============7455325383689370311==" Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org --===============7455325383689370311== Content-Type: multipart/alternative; boundary=00151743f82e01b70504c9064409 --00151743f82e01b70504c9064409 Content-Type: text/plain; charset=ISO-8859-1 Hi, It looks like the patch that has been provided on Xen Security Advisory 11 (CVE-2012-3433) doesn't applied for Xen 3.4.4. When I try to apply this patch and I am getting the below error, 1 out of 1 hunk FAILED -- saving rejects to file xen/arch/x86/mm/p2m.c.rej 1 out of 1 hunk FAILED -- saving rejects to file xen/arch/x86/mm/p2m.c.rej Seems there is no for loop "for ( gfn=0; gfn < p2m->max_mapped_pfn; gfn++ )" on xen/arch/x86/mm/p2m.c.rej on xen3.4.4 source instead if loop only exists. p2m.c: && (gfn + (1UL << page_order) - 1 > d->arch.p2m->max_mapped_pfn) ) p2m.c: d->arch.p2m->max_mapped_pfn = gfn + (1UL << page_order) - 1; p2m.c: if ( gfn > d->arch.p2m->max_mapped_pfn ) p2m.c: if ( gfn <= current->domain->arch.p2m->max_mapped_pfn ) p2m.c: if ( test_linear && (gfn <= d->arch.p2m->max_mapped_pfn) ) p2m.c.orig: && (gfn + (1UL << page_order) - 1 > d->arch.p2m->max_mapped_pfn) ) p2m.c.orig: d->arch.p2m->max_mapped_pfn = gfn + (1UL << page_order) - 1; p2m.c.orig: if ( gfn > d->arch.p2m->max_mapped_pfn ) p2m.c.orig: if ( gfn <= current->domain->arch.p2m->max_mapped_pfn ) p2m.c.orig: if ( test_linear && (gfn <= d->arch.p2m->max_mapped_pfn) ) p2m.c.rej: for ( gfn=0; gfn < p2m->max_mapped_pfn; gfn++ ) p2m.c.rej: for ( gfn=0; gfn < p2m->max_mapped_pfn; gfn++ ) So I guess this patch applicable for Xen 4.x only. If you update the patch for Xen 3.4 that would be great. On Thu, Sep 6, 2012 at 2:43 PM, Ian Campbell wrote: > On Thu, 2012-09-06 at 10:08 +0100, kk s wrote: > > Hi Ian, > > > > Thanks for your reply. Sorry to bother you with this. I am bit > > confused and so I am asking to make clear myself. > > > > Reg CVE-2012-2934 - > > http://lists.xen.org/archives/html/xen-announce/2012-06/msg00002.html > > Is Xen 3.4 too affected with this vulnerable? If so I couldn't find > > the patch for xen 3.4 and it does exit for xen 4.x only. > > I expect it does effect 3.4, but only if you are running on one of the > listed processors. > > security@xen.org doesn't provide security support for 3.4 any more. If > you aren't able to backport the 4.0 patch yourself, you would need to > speak to Keith Coleman who is the 3.4 stable maintainer. > > > I don't how to apply the following patches since I have created rpm > > with patches applied that included as downloadable file. But for these > > patches I am not seeing any downloadable file. > > > > http://lists.xen.org/archives/html/xen-devel/2012-02/msg00212.html > > http://lists.xen.org/archives/html/xen-devel/2012-07/msg01649.html > > http://lists.xen.org/archives/html/xen-devel/2012-08/msg00855.html > > > > If you can clear this for me that would be great :) > > I already pointed you at http://wiki.xen.org/wiki/Security_Announcements > which should have all the links you need. > > > --00151743f82e01b70504c9064409 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable
Hi,

It looks like the patch that has been= provided on Xen Security Advisory 11 (CVE-2012-3433) doesn't applied f= or Xen 3.4.4.

When I try to apply this patch and I= am getting the below error,

1 out of 1 hunk FAILED -- saving rejects to file xen/ar= ch/x86/mm/p2m.c.rej
1 out of 1 hunk FAILED -- saving rejects to file xen= /arch/x86/mm/p2m.c.rej

Seems there is no for loop = "for ( gfn=3D0; gfn < p2m->max_mapped_pfn; gfn++ )" on xen/= arch/x86/mm/p2m.c.rej on xen3.4.4 source instead if loop only exists.

p2m.c: && (gfn + (1UL << page_ord= er) - 1 > d->arch.p2m->max_mapped_pfn) )
p2m.c: d->ar= ch.p2m->max_mapped_pfn =3D gfn + (1UL << page_order) - 1;
p2m.c= : if ( gfn > d->arch.p2m->max_mapped_pfn )
p2m.c: if ( gfn <=3D current->domain->arch.p2m->max_mapped_p= fn )
p2m.c: if ( test_linear && (gfn <=3D d->arch.p= 2m->max_mapped_pfn) )
p2m.c.orig: && (gfn + (1UL <= < page_order) - 1 > d->arch.p2m->max_mapped_pfn) )
p2m.c.orig: d->arch.p2m->max_mapped_pfn =3D gfn + (1UL <<= ; page_order) - 1;
p2m.c.orig: if ( gfn > d->arch.p2m->max_m= apped_pfn )
p2m.c.orig: if ( gfn <=3D current->domain->arch.= p2m->max_mapped_pfn )
p2m.c.orig: if ( test_linear && (gfn <=3D d->arch.p2m-= >max_mapped_pfn) )
p2m.c.rej: for ( gfn=3D0; gfn < p2m->ma= x_mapped_pfn; gfn++ )
p2m.c.rej: for ( gfn=3D0; gfn < p2m->ma= x_mapped_pfn; gfn++ )

So I guess this patch applicable for Xen 4.x only. If y= ou update the patch for Xen 3.4 that would be great.

On Thu, Sep 6, 2012 at 2:43 PM, Ian Campbell <= span dir=3D"ltr"><Ian.Campbell@citrix.com> wrote:
On Thu, 2012-09-06 at 10:0= 8 +0100, kk s wrote:
> Hi Ian,
>
> Thanks for your reply. Sorry to bother you with this. I am bit
> confused and so I am asking to make clear myself.
>
> Reg CVE-2012-2934 -
> http://lists.xen.org/archives/html/xen-announ= ce/2012-06/msg00002.html
> Is Xen 3.4 too affected with this vulnerable? If so I couldn't fin= d
> the patch for xen 3.4 and it does exit for xen 4.x only.

I expect it does effect 3.4, but only if you are running on one of th= e
listed processors.

security@xen.org doesn't provid= e security support for 3.4 any more. If
you aren't able to backport the 4.0 patch yourself, you would need to speak to Keith Coleman who is the 3.4 stable maintainer.

> I don't how to apply the following patches since I have created rp= m
> with patches applied that included as downloadable file. But for these=
> patches I am not seeing any downloadable file.
>
> http://lists.xen.org/archives/html/xen-devel/201= 2-02/msg00212.html
> http://lists.xen.org/archives/html/xen-devel/201= 2-07/msg01649.html
> http://lists.xen.org/archives/html/xen-devel/201= 2-08/msg00855.html
>
> If you can clear this for me that would be great :)

I already pointed you at http://wiki.xen.org/wiki/Security_Announc= ements
which should have all the links you need.



--00151743f82e01b70504c9064409-- --===============7455325383689370311== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users --===============7455325383689370311==-- From xen-users-bounces@lists.xen.org Thu Sep 06 11:38:26 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Thu, 06 Sep 2012 11:38:26 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1T9aOy-00021T-W5; Thu, 06 Sep 2012 11:37:40 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1T9YAc-0003XJ-C1 for xen-users@lists.xen.org; Thu, 06 Sep 2012 09:14:42 +0000 Received: from [85.158.139.83:58995] by server-3.bemta-5.messagelabs.com id 95/BE-21836-08968405; Thu, 06 Sep 2012 09:14:40 +0000 X-Env-Sender: kks.kbase@gmail.com X-Msg-Ref: server-5.tower-182.messagelabs.com!1346922880!28658026!1 X-Originating-IP: [209.85.214.45] X-SpamReason: No, hits=1.2 required=7.0 tests=HTML_10_20,HTML_MESSAGE, ML_RADAR_SPEW_LINKS_14,RCVD_BY_IP,spamassassin: X-StarScan-Received: X-StarScan-Version: 6.6.1.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 31760 invoked from network); 6 Sep 2012 09:14:40 -0000 Received: from mail-bk0-f45.google.com (HELO mail-bk0-f45.google.com) (209.85.214.45) by server-5.tower-182.messagelabs.com with RC4-SHA encrypted SMTP; 6 Sep 2012 09:14:40 -0000 Received: by bkcji1 with SMTP id ji1so662618bkc.32 for ; Thu, 06 Sep 2012 02:14:40 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:date:message-id:subject:from:to:content-type; bh=m4gDY9EYLd5BSKK+88RD//Nfqk9RdX5fCTCKMVp5YEo=; b=yq9+lIgwMT2pnD9ZvCtCx9tGA20EPwzYb7xgy9wpXoBnU06HyopTULlNwV583qOCGE /+GBtcr5XxiYJrdq0f2O1n5ngfMmU13JlYKdhRlT/GR4ZzqaQ7iDfaJ7nteArTV/8oR5 xeZs7ttlLXXm24bEWQvFszMGDI6DqFRkBqWFCAHU5J86kRw+Hc3Vwp0uB6yiSE13gFrH gXdcsU4oq/9UOavLKmb1ICXa0dSFhpf01KA9g3+eU02fsIpoqGb867qY5s9eO8V4QvjF JWbdaNaUvRF+rXL06f9qudhovrxEGhxZYAzuMdyGaTWaW7n4t+7a4Q/90molTWOGULSr YVLQ== MIME-Version: 1.0 Received: by 10.204.154.131 with SMTP id o3mr438749bkw.87.1346922879846; Thu, 06 Sep 2012 02:14:39 -0700 (PDT) Received: by 10.204.56.134 with HTTP; Thu, 6 Sep 2012 02:14:39 -0700 (PDT) Date: Thu, 6 Sep 2012 14:44:39 +0530 Message-ID: From: kk s To: xen-users@lists.xen.org, xen-devel@lists.xen.org X-Mailman-Approved-At: Thu, 06 Sep 2012 11:37:37 +0000 Subject: [Xen-users] Issue with making rpm with patch applied X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============3225686416013838924==" Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org --===============3225686416013838924== Content-Type: multipart/alternative; boundary=0015175cae66cb089204c904eb73 --0015175cae66cb089204c904eb73 Content-Type: text/plain; charset=ISO-8859-1 Hi, I have downloaded src rpm from gitco and extracted into the /usr/src/redhat/SOURCES dir then downloaded the patches and renamed it as properly like xen-3.4.4-xsa17-qemu-xen-traditional-all.patch. Then edited the xen-x.spec file and added the patches. After that I have tried to make rpm using rpmbuild -bb xen-x.spec and I ended up with the below error, Patch #13 (xen-3.4.4-xsa17-qemu-xen-traditional-all.patch): + patch -p1 -s The text leading up to this was: -------------------------- |console: bounds check whenever changing the cursor due to an escape code | |This is XSA-17 / CVE-2012-3515 | |Signed-off-by: Ian Campbell | |diff --git a/console.c b/console.c |index 5e6e3d0..9984d6f 100644 |--- a/console.c |+++ b/console.c -------------------------- File to patch: Fyi : I have added the patches xsa12-all.patch, xsa14-xen-3.4-and-4.x.patch and xsa17-qemu-xen-traditional-all.patch. All the patches goes fine expect xsa17-qemu-xen-traditional-all.patch. May I know how can I apply this? --0015175cae66cb089204c904eb73 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Hi,

I have downloaded src rpm from gitco and extracted into the /usr= /src/redhat/SOURCES dir then downloaded the patches and renamed it as prope= rly like xen-3.4.4-xsa17-qemu-xen-traditional-all.patch. Then edited the xe= n-x.spec file and added the patches. After that I have tried to make rpm us= ing rpmbuild -bb xen-x.spec and I ended up with the below error,


Patch #13 (xen-3.4.4-xsa17-qemu-xen-traditional-all.patch):
+ pa= tch -p1 -s
The text leading up to this was:
-------------------------= -
|console: bounds check whenever changing the cursor due to an escape c= ode
|
|This is XSA-17 / CVE-2012-3515
|
|Signed-off-by: Ian Campbell &= lt;ian.campbell@citrix.com&g= t;
|
|diff --git a/console.c b/console.c
|index 5e6e3d0..9984d6f 1= 00644
|--- a/console.c
|+++ b/console.c
--------------------------
File = to patch:=A0=A0=A0=A0=A0


Fyi : I have added the patches xsa12-a= ll.patch, xsa14-xen-3.4-and-4.x.patch and xsa17-qemu-xen-traditional-all.pa= tch. All the patches goes fine expect xsa17-qemu-xen-traditional-all.patch.=

May I know how can I apply this?

--0015175cae66cb089204c904eb73-- --===============3225686416013838924== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users --===============3225686416013838924==-- From xen-users-bounces@lists.xen.org Thu Sep 06 11:38:26 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Thu, 06 Sep 2012 11:38:26 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1T9aOy-00021T-W5; Thu, 06 Sep 2012 11:37:40 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1T9YAc-0003XJ-C1 for xen-users@lists.xen.org; Thu, 06 Sep 2012 09:14:42 +0000 Received: from [85.158.139.83:58995] by server-3.bemta-5.messagelabs.com id 95/BE-21836-08968405; Thu, 06 Sep 2012 09:14:40 +0000 X-Env-Sender: kks.kbase@gmail.com X-Msg-Ref: server-5.tower-182.messagelabs.com!1346922880!28658026!1 X-Originating-IP: [209.85.214.45] X-SpamReason: No, hits=1.2 required=7.0 tests=HTML_10_20,HTML_MESSAGE, ML_RADAR_SPEW_LINKS_14,RCVD_BY_IP,spamassassin: X-StarScan-Received: X-StarScan-Version: 6.6.1.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 31760 invoked from network); 6 Sep 2012 09:14:40 -0000 Received: from mail-bk0-f45.google.com (HELO mail-bk0-f45.google.com) (209.85.214.45) by server-5.tower-182.messagelabs.com with RC4-SHA encrypted SMTP; 6 Sep 2012 09:14:40 -0000 Received: by bkcji1 with SMTP id ji1so662618bkc.32 for ; Thu, 06 Sep 2012 02:14:40 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:date:message-id:subject:from:to:content-type; bh=m4gDY9EYLd5BSKK+88RD//Nfqk9RdX5fCTCKMVp5YEo=; b=yq9+lIgwMT2pnD9ZvCtCx9tGA20EPwzYb7xgy9wpXoBnU06HyopTULlNwV583qOCGE /+GBtcr5XxiYJrdq0f2O1n5ngfMmU13JlYKdhRlT/GR4ZzqaQ7iDfaJ7nteArTV/8oR5 xeZs7ttlLXXm24bEWQvFszMGDI6DqFRkBqWFCAHU5J86kRw+Hc3Vwp0uB6yiSE13gFrH gXdcsU4oq/9UOavLKmb1ICXa0dSFhpf01KA9g3+eU02fsIpoqGb867qY5s9eO8V4QvjF JWbdaNaUvRF+rXL06f9qudhovrxEGhxZYAzuMdyGaTWaW7n4t+7a4Q/90molTWOGULSr YVLQ== MIME-Version: 1.0 Received: by 10.204.154.131 with SMTP id o3mr438749bkw.87.1346922879846; Thu, 06 Sep 2012 02:14:39 -0700 (PDT) Received: by 10.204.56.134 with HTTP; Thu, 6 Sep 2012 02:14:39 -0700 (PDT) Date: Thu, 6 Sep 2012 14:44:39 +0530 Message-ID: From: kk s To: xen-users@lists.xen.org, xen-devel@lists.xen.org X-Mailman-Approved-At: Thu, 06 Sep 2012 11:37:37 +0000 Subject: [Xen-users] Issue with making rpm with patch applied X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============3225686416013838924==" Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org --===============3225686416013838924== Content-Type: multipart/alternative; boundary=0015175cae66cb089204c904eb73 --0015175cae66cb089204c904eb73 Content-Type: text/plain; charset=ISO-8859-1 Hi, I have downloaded src rpm from gitco and extracted into the /usr/src/redhat/SOURCES dir then downloaded the patches and renamed it as properly like xen-3.4.4-xsa17-qemu-xen-traditional-all.patch. Then edited the xen-x.spec file and added the patches. After that I have tried to make rpm using rpmbuild -bb xen-x.spec and I ended up with the below error, Patch #13 (xen-3.4.4-xsa17-qemu-xen-traditional-all.patch): + patch -p1 -s The text leading up to this was: -------------------------- |console: bounds check whenever changing the cursor due to an escape code | |This is XSA-17 / CVE-2012-3515 | |Signed-off-by: Ian Campbell | |diff --git a/console.c b/console.c |index 5e6e3d0..9984d6f 100644 |--- a/console.c |+++ b/console.c -------------------------- File to patch: Fyi : I have added the patches xsa12-all.patch, xsa14-xen-3.4-and-4.x.patch and xsa17-qemu-xen-traditional-all.patch. All the patches goes fine expect xsa17-qemu-xen-traditional-all.patch. May I know how can I apply this? --0015175cae66cb089204c904eb73 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Hi,

I have downloaded src rpm from gitco and extracted into the /usr= /src/redhat/SOURCES dir then downloaded the patches and renamed it as prope= rly like xen-3.4.4-xsa17-qemu-xen-traditional-all.patch. Then edited the xe= n-x.spec file and added the patches. After that I have tried to make rpm us= ing rpmbuild -bb xen-x.spec and I ended up with the below error,


Patch #13 (xen-3.4.4-xsa17-qemu-xen-traditional-all.patch):
+ pa= tch -p1 -s
The text leading up to this was:
-------------------------= -
|console: bounds check whenever changing the cursor due to an escape c= ode
|
|This is XSA-17 / CVE-2012-3515
|
|Signed-off-by: Ian Campbell &= lt;ian.campbell@citrix.com&g= t;
|
|diff --git a/console.c b/console.c
|index 5e6e3d0..9984d6f 1= 00644
|--- a/console.c
|+++ b/console.c
--------------------------
File = to patch:=A0=A0=A0=A0=A0


Fyi : I have added the patches xsa12-a= ll.patch, xsa14-xen-3.4-and-4.x.patch and xsa17-qemu-xen-traditional-all.pa= tch. All the patches goes fine expect xsa17-qemu-xen-traditional-all.patch.=

May I know how can I apply this?

--0015175cae66cb089204c904eb73-- --===============3225686416013838924== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users --===============3225686416013838924==-- From xen-users-bounces@lists.xen.org Thu Sep 06 11:38:27 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Thu, 06 Sep 2012 11:38:27 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1T9aOw-00020e-Ai; Thu, 06 Sep 2012 11:37:38 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1T9XVG-0001Te-4I for xen-users@lists.xen.org; Thu, 06 Sep 2012 08:31:58 +0000 Received: from [85.158.139.83:30605] by server-4.bemta-5.messagelabs.com id A9/F7-23042-C7F58405; Thu, 06 Sep 2012 08:31:56 +0000 X-Env-Sender: kks.kbase@gmail.com X-Msg-Ref: server-7.tower-182.messagelabs.com!1346920315!24926816!1 X-Originating-IP: [209.85.214.45] X-SpamReason: No, hits=3.3 required=7.0 tests=HTML_60_70,HTML_MESSAGE, HTML_OBFUSCATE_20_30,ML_RADAR_SPEW_LINKS_14,RCVD_BY_IP,spamassassin: X-StarScan-Received: X-StarScan-Version: 6.6.1.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 21875 invoked from network); 6 Sep 2012 08:31:55 -0000 Received: from mail-bk0-f45.google.com (HELO mail-bk0-f45.google.com) (209.85.214.45) by server-7.tower-182.messagelabs.com with RC4-SHA encrypted SMTP; 6 Sep 2012 08:31:55 -0000 Received: by bkcji1 with SMTP id ji1so640256bkc.32 for ; Thu, 06 Sep 2012 01:31:54 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:date:message-id:subject:from:to:content-type; bh=lOuOuo1q2EMSOyeWBKK6mpZh9TtU/kWkbEKqNvQCppM=; b=IjoApTWOOmB9biHLR/aDnHgZfSQjmE6JKicV5m5NqEHI0olIuuFmf+WjA0RRObd9xO H6ialTy5vhX+DBDqmtJTiugQntvZ3Xp0eXtVM3wL5h755u0sue2VMDsdt3Vt2xXHjFh/ 9x+ExvtD81SES1qFojH5Jx5cDXZvThhzQP/eRKjAy3jxIxP+1+Y1T4OOE6nhClvWP7eq 1wqV+qOrm4Q9FRiqAAa3GUu0vzQhN7fGq6K/LXDyu8cBX8l1hy7rAmurtbPuR7+9LeQp 0IQ9h/Cyb6y3GJB+cn7H/spZR8pJkMT7oL2+eWc/8LPme/tCooth9ZSGa555mcToSr6U 9x2w== MIME-Version: 1.0 Received: by 10.204.152.136 with SMTP id g8mr363414bkw.44.1346920314713; Thu, 06 Sep 2012 01:31:54 -0700 (PDT) Received: by 10.204.56.134 with HTTP; Thu, 6 Sep 2012 01:31:54 -0700 (PDT) Date: Thu, 6 Sep 2012 14:01:54 +0530 Message-ID: From: kk s To: xen-users@lists.xen.org, xen-devel@lists.xen.org X-Mailman-Approved-At: Thu, 06 Sep 2012 11:37:37 +0000 Subject: [Xen-users] Security patches X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============0812910301755377235==" Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org --===============0812910301755377235== Content-Type: multipart/alternative; boundary=0015175d0998e637f704c90452ff --0015175d0998e637f704c90452ff Content-Type: text/plain; charset=ISO-8859-1 Hi, Can anyone give the patch file download link for the below xen security for xen version 3.4 and 4.1? Since I couldn't find the downloadable patch file for some of the CVE's. CVE-2012-0029 - http://lists.xen.org/archives/html/xen-devel/2012-02/msg00212.html (There is no download link for both xen 3.4 and 4.1) CVE-2012-2934 - http://lists.xen.org/archives/html/xen-announce/2012-06/msg00002.html (There is no patch file to download of xen 3.4) CVE-2012-3432 - http://lists.xen.org/archives/html/xen-devel/2012-07/msg01649.html (There is no download link for both xen 3.4 and 4.1) CVE-2012-3433 - http://lists.xen.org/archives/html/xen-devel/2012-08/msg00855.html (There is no download link for both xen 3.4 and 4.1) CVE-2012-3497 - http://lists.xen.org/archives/html/xen-announce/2012-09/msg00006.html (There is no download link for patch) Also I have some doubts for the below CVE's. CVE-2012-3496 - Is this vulnerability affected for xen 4.x only or it does include for xen 3.4 too? Since the patch name was *xsa14-xen-3.4-and-4.x.patch * http://lists.xen.org/archives/html/xen-announce/2012-09/msg00002.html CVE-2012-3516 - Shall I apply this unstable for patch for xen4.2 too? http://lists.xen.org/archives/html/xen-announce/2012-09/msg00004.html --0015175d0998e637f704c90452ff Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Hi,

Can anyone give the patch file download link for the below xen s= ecurity for xen version 3.4 and 4.1? Since I couldn't find the download= able patch file for some of the CVE's.

CVE-2012-0029=A0=A0 - http://lists.xen.org/archives/h= tml/xen-devel/2012-02/msg00212.html=A0 (There is no download link for b= oth xen 3.4 and 4.1)
CVE-2012-2934=A0=A0 - http:= //lists.xen.org/archives/html/xen-announce/2012-06/msg00002.html=A0 (Th= ere is no patch file to download of xen 3.4)
CVE-2012-3432=A0=A0 - http://l= ists.xen.org/archives/html/xen-devel/2012-07/msg01649.html=A0 (There is= no download link for both xen 3.4 and 4.1)
CVE-2012-3433=A0=A0 - http://l= ists.xen.org/archives/html/xen-devel/2012-08/msg00855.html=A0 (There is= no download link for both xen 3.4 and 4.1)
CVE-2012-3497=A0=A0 - http:= //lists.xen.org/archives/html/xen-announce/2012-09/msg00006.html=A0 (Th= ere is no download link for patch)

Also I have some doubts for the below CVE's.

CVE-2012-3496=A0 - Is this vulnerability affected= for xen 4.x only or it does include for xen 3.4 too? Since the patch name = was xsa14-xen-3.4-and-4.x.patch=A0= http://lists.xen.org/archives/html/xen-announce/2012-09/msg00002.ht= ml
CVE-2012-3516=A0 - Shall I apply t= his unstable for patch for xen4.2 too?=A0=A0 http://lists.xen.org/ar= chives/html/xen-announce/2012-09/msg00004.html


--0015175d0998e637f704c90452ff-- --===============0812910301755377235== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users --===============0812910301755377235==-- From xen-users-bounces@lists.xen.org Thu Sep 06 11:38:27 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Thu, 06 Sep 2012 11:38:27 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1T9aOw-00020e-Ai; Thu, 06 Sep 2012 11:37:38 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1T9XVG-0001Te-4I for xen-users@lists.xen.org; Thu, 06 Sep 2012 08:31:58 +0000 Received: from [85.158.139.83:30605] by server-4.bemta-5.messagelabs.com id A9/F7-23042-C7F58405; Thu, 06 Sep 2012 08:31:56 +0000 X-Env-Sender: kks.kbase@gmail.com X-Msg-Ref: server-7.tower-182.messagelabs.com!1346920315!24926816!1 X-Originating-IP: [209.85.214.45] X-SpamReason: No, hits=3.3 required=7.0 tests=HTML_60_70,HTML_MESSAGE, HTML_OBFUSCATE_20_30,ML_RADAR_SPEW_LINKS_14,RCVD_BY_IP,spamassassin: X-StarScan-Received: X-StarScan-Version: 6.6.1.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 21875 invoked from network); 6 Sep 2012 08:31:55 -0000 Received: from mail-bk0-f45.google.com (HELO mail-bk0-f45.google.com) (209.85.214.45) by server-7.tower-182.messagelabs.com with RC4-SHA encrypted SMTP; 6 Sep 2012 08:31:55 -0000 Received: by bkcji1 with SMTP id ji1so640256bkc.32 for ; Thu, 06 Sep 2012 01:31:54 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:date:message-id:subject:from:to:content-type; bh=lOuOuo1q2EMSOyeWBKK6mpZh9TtU/kWkbEKqNvQCppM=; b=IjoApTWOOmB9biHLR/aDnHgZfSQjmE6JKicV5m5NqEHI0olIuuFmf+WjA0RRObd9xO H6ialTy5vhX+DBDqmtJTiugQntvZ3Xp0eXtVM3wL5h755u0sue2VMDsdt3Vt2xXHjFh/ 9x+ExvtD81SES1qFojH5Jx5cDXZvThhzQP/eRKjAy3jxIxP+1+Y1T4OOE6nhClvWP7eq 1wqV+qOrm4Q9FRiqAAa3GUu0vzQhN7fGq6K/LXDyu8cBX8l1hy7rAmurtbPuR7+9LeQp 0IQ9h/Cyb6y3GJB+cn7H/spZR8pJkMT7oL2+eWc/8LPme/tCooth9ZSGa555mcToSr6U 9x2w== MIME-Version: 1.0 Received: by 10.204.152.136 with SMTP id g8mr363414bkw.44.1346920314713; Thu, 06 Sep 2012 01:31:54 -0700 (PDT) Received: by 10.204.56.134 with HTTP; Thu, 6 Sep 2012 01:31:54 -0700 (PDT) Date: Thu, 6 Sep 2012 14:01:54 +0530 Message-ID: From: kk s To: xen-users@lists.xen.org, xen-devel@lists.xen.org X-Mailman-Approved-At: Thu, 06 Sep 2012 11:37:37 +0000 Subject: [Xen-users] Security patches X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============0812910301755377235==" Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org --===============0812910301755377235== Content-Type: multipart/alternative; boundary=0015175d0998e637f704c90452ff --0015175d0998e637f704c90452ff Content-Type: text/plain; charset=ISO-8859-1 Hi, Can anyone give the patch file download link for the below xen security for xen version 3.4 and 4.1? Since I couldn't find the downloadable patch file for some of the CVE's. CVE-2012-0029 - http://lists.xen.org/archives/html/xen-devel/2012-02/msg00212.html (There is no download link for both xen 3.4 and 4.1) CVE-2012-2934 - http://lists.xen.org/archives/html/xen-announce/2012-06/msg00002.html (There is no patch file to download of xen 3.4) CVE-2012-3432 - http://lists.xen.org/archives/html/xen-devel/2012-07/msg01649.html (There is no download link for both xen 3.4 and 4.1) CVE-2012-3433 - http://lists.xen.org/archives/html/xen-devel/2012-08/msg00855.html (There is no download link for both xen 3.4 and 4.1) CVE-2012-3497 - http://lists.xen.org/archives/html/xen-announce/2012-09/msg00006.html (There is no download link for patch) Also I have some doubts for the below CVE's. CVE-2012-3496 - Is this vulnerability affected for xen 4.x only or it does include for xen 3.4 too? Since the patch name was *xsa14-xen-3.4-and-4.x.patch * http://lists.xen.org/archives/html/xen-announce/2012-09/msg00002.html CVE-2012-3516 - Shall I apply this unstable for patch for xen4.2 too? http://lists.xen.org/archives/html/xen-announce/2012-09/msg00004.html --0015175d0998e637f704c90452ff Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Hi,

Can anyone give the patch file download link for the below xen s= ecurity for xen version 3.4 and 4.1? Since I couldn't find the download= able patch file for some of the CVE's.

CVE-2012-0029=A0=A0 - http://lists.xen.org/archives/h= tml/xen-devel/2012-02/msg00212.html=A0 (There is no download link for b= oth xen 3.4 and 4.1)
CVE-2012-2934=A0=A0 - http:= //lists.xen.org/archives/html/xen-announce/2012-06/msg00002.html=A0 (Th= ere is no patch file to download of xen 3.4)
CVE-2012-3432=A0=A0 - http://l= ists.xen.org/archives/html/xen-devel/2012-07/msg01649.html=A0 (There is= no download link for both xen 3.4 and 4.1)
CVE-2012-3433=A0=A0 - http://l= ists.xen.org/archives/html/xen-devel/2012-08/msg00855.html=A0 (There is= no download link for both xen 3.4 and 4.1)
CVE-2012-3497=A0=A0 - http:= //lists.xen.org/archives/html/xen-announce/2012-09/msg00006.html=A0 (Th= ere is no download link for patch)

Also I have some doubts for the below CVE's.

CVE-2012-3496=A0 - Is this vulnerability affected= for xen 4.x only or it does include for xen 3.4 too? Since the patch name = was xsa14-xen-3.4-and-4.x.patch=A0= http://lists.xen.org/archives/html/xen-announce/2012-09/msg00002.ht= ml
CVE-2012-3516=A0 - Shall I apply t= his unstable for patch for xen4.2 too?=A0=A0 http://lists.xen.org/ar= chives/html/xen-announce/2012-09/msg00004.html


--0015175d0998e637f704c90452ff-- --===============0812910301755377235== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users --===============0812910301755377235==-- From xen-users-bounces@lists.xen.org Thu Sep 06 11:38:28 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Thu, 06 Sep 2012 11:38:28 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1T9aOw-00020p-VF; Thu, 06 Sep 2012 11:37:38 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1T9XtI-00028O-EI for xen-users@lists.xen.org; Thu, 06 Sep 2012 08:56:48 +0000 Received: from [85.158.138.51:26658] by server-4.bemta-3.messagelabs.com id 8E/6F-24831-E4568405; Thu, 06 Sep 2012 08:56:46 +0000 X-Env-Sender: kks.kbase@gmail.com X-Msg-Ref: server-9.tower-174.messagelabs.com!1346921805!29029970!1 X-Originating-IP: [209.85.214.45] X-SpamReason: No, hits=2.8 required=7.0 tests=HTML_10_20,HTML_MESSAGE, HTML_SHORT_LENGTH,ML_RADAR_SPEW_LINKS_14,RCVD_BY_IP,spamassassin: X-StarScan-Received: X-StarScan-Version: 6.6.1.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 862 invoked from network); 6 Sep 2012 08:56:46 -0000 Received: from mail-bk0-f45.google.com (HELO mail-bk0-f45.google.com) (209.85.214.45) by server-9.tower-174.messagelabs.com with RC4-SHA encrypted SMTP; 6 Sep 2012 08:56:46 -0000 Received: by bkcji1 with SMTP id ji1so653178bkc.32 for ; Thu, 06 Sep 2012 01:56:45 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:date:message-id:subject:from:to:content-type; bh=MS0jXLhw+w2Uqa0SCtUAzPS+SNN0Syugsvf8huDdFY4=; b=UEYD7X6a2cYTajEcZ1AXxLhtv0k5FdVSeICSjugK2IQjZH4c3XUwHwHB+Ng8Gu0sJ5 V7xwcISvXj3RSWclGFWdfgAkMcZCMtCDdoV/Zx0JcFNgOoiPUN65xEr7jRSTjFz7yO/7 +AYirGMPCl7j102NRIWOcZgsmfScFeD0BbFEug/p9w9vbFDU1db2MAwUqVCjs5zHPPCH 7WSXbbe1HR+J4yLHu5y9s0r+zytccpDaLSQLUdZLoXjxQ/I2Mx8QIdk8xZBaoRj0Z9Sv rFKAOOayTFtsQxAn4nsnOZ+/lXqLJUFPXtSdSww6CH8DIPwMbBQRQDfrE3ulXWBmpE0j CDKA== MIME-Version: 1.0 Received: by 10.205.126.13 with SMTP id gu13mr403746bkc.79.1346921805299; Thu, 06 Sep 2012 01:56:45 -0700 (PDT) Received: by 10.204.56.134 with HTTP; Thu, 6 Sep 2012 01:56:45 -0700 (PDT) Date: Thu, 6 Sep 2012 14:26:45 +0530 Message-ID: From: kk s To: xen-devel@lists.xen.org, xen-users@lists.xen.org X-Mailman-Approved-At: Thu, 06 Sep 2012 11:37:37 +0000 Subject: [Xen-users] Xen 4.2 rpm build X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============3395643118522349619==" Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org --===============3395643118522349619== Content-Type: multipart/alternative; boundary=00151747b744bec1ed04c904ab76 --00151747b744bec1ed04c904ab76 Content-Type: text/plain; charset=ISO-8859-1 Hi, Can anyone provide the steps to build rpm from source for Xen 4.1.2? --00151747b744bec1ed04c904ab76 Content-Type: text/html; charset=ISO-8859-1 Hi,

Can anyone provide the steps to build rpm from source for Xen 4.1.2?


--00151747b744bec1ed04c904ab76-- --===============3395643118522349619== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users --===============3395643118522349619==-- From xen-users-bounces@lists.xen.org Thu Sep 06 11:38:28 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Thu, 06 Sep 2012 11:38:28 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1T9aOw-00020p-VF; Thu, 06 Sep 2012 11:37:38 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1T9XtI-00028O-EI for xen-users@lists.xen.org; Thu, 06 Sep 2012 08:56:48 +0000 Received: from [85.158.138.51:26658] by server-4.bemta-3.messagelabs.com id 8E/6F-24831-E4568405; Thu, 06 Sep 2012 08:56:46 +0000 X-Env-Sender: kks.kbase@gmail.com X-Msg-Ref: server-9.tower-174.messagelabs.com!1346921805!29029970!1 X-Originating-IP: [209.85.214.45] X-SpamReason: No, hits=2.8 required=7.0 tests=HTML_10_20,HTML_MESSAGE, HTML_SHORT_LENGTH,ML_RADAR_SPEW_LINKS_14,RCVD_BY_IP,spamassassin: X-StarScan-Received: X-StarScan-Version: 6.6.1.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 862 invoked from network); 6 Sep 2012 08:56:46 -0000 Received: from mail-bk0-f45.google.com (HELO mail-bk0-f45.google.com) (209.85.214.45) by server-9.tower-174.messagelabs.com with RC4-SHA encrypted SMTP; 6 Sep 2012 08:56:46 -0000 Received: by bkcji1 with SMTP id ji1so653178bkc.32 for ; Thu, 06 Sep 2012 01:56:45 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:date:message-id:subject:from:to:content-type; bh=MS0jXLhw+w2Uqa0SCtUAzPS+SNN0Syugsvf8huDdFY4=; b=UEYD7X6a2cYTajEcZ1AXxLhtv0k5FdVSeICSjugK2IQjZH4c3XUwHwHB+Ng8Gu0sJ5 V7xwcISvXj3RSWclGFWdfgAkMcZCMtCDdoV/Zx0JcFNgOoiPUN65xEr7jRSTjFz7yO/7 +AYirGMPCl7j102NRIWOcZgsmfScFeD0BbFEug/p9w9vbFDU1db2MAwUqVCjs5zHPPCH 7WSXbbe1HR+J4yLHu5y9s0r+zytccpDaLSQLUdZLoXjxQ/I2Mx8QIdk8xZBaoRj0Z9Sv rFKAOOayTFtsQxAn4nsnOZ+/lXqLJUFPXtSdSww6CH8DIPwMbBQRQDfrE3ulXWBmpE0j CDKA== MIME-Version: 1.0 Received: by 10.205.126.13 with SMTP id gu13mr403746bkc.79.1346921805299; Thu, 06 Sep 2012 01:56:45 -0700 (PDT) Received: by 10.204.56.134 with HTTP; Thu, 6 Sep 2012 01:56:45 -0700 (PDT) Date: Thu, 6 Sep 2012 14:26:45 +0530 Message-ID: From: kk s To: xen-devel@lists.xen.org, xen-users@lists.xen.org X-Mailman-Approved-At: Thu, 06 Sep 2012 11:37:37 +0000 Subject: [Xen-users] Xen 4.2 rpm build X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============3395643118522349619==" Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org --===============3395643118522349619== Content-Type: multipart/alternative; boundary=00151747b744bec1ed04c904ab76 --00151747b744bec1ed04c904ab76 Content-Type: text/plain; charset=ISO-8859-1 Hi, Can anyone provide the steps to build rpm from source for Xen 4.1.2? --00151747b744bec1ed04c904ab76 Content-Type: text/html; charset=ISO-8859-1 Hi,

Can anyone provide the steps to build rpm from source for Xen 4.1.2?


--00151747b744bec1ed04c904ab76-- --===============3395643118522349619== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users --===============3395643118522349619==-- From xen-users-bounces@lists.xen.org Thu Sep 06 12:46:32 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Thu, 06 Sep 2012 12:46:32 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1T9bSZ-0008BH-4T; Thu, 06 Sep 2012 12:45:27 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1T9bSX-0008BC-P7 for xen-users@lists.xen.org; Thu, 06 Sep 2012 12:45:25 +0000 Received: from [85.158.139.83:15810] by server-12.bemta-5.messagelabs.com id 70/56-18300-4EA98405; Thu, 06 Sep 2012 12:45:24 +0000 X-Env-Sender: pasik@iki.fi X-Msg-Ref: server-10.tower-182.messagelabs.com!1346935523!29230751!1 X-Originating-IP: [192.89.123.25] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogMTkyLjg5LjEyMy4yNSA9PiA1MDQ1MDg=\n X-StarScan-Received: X-StarScan-Version: 6.6.1.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 17358 invoked from network); 6 Sep 2012 12:45:24 -0000 Received: from smtp.tele.fi (HELO smtp.tele.fi) (192.89.123.25) by server-10.tower-182.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 6 Sep 2012 12:45:24 -0000 X-Originating-Ip: [194.89.68.22] Received: from ydin.reaktio.net (reaktio.net [194.89.68.22]) by smtp.tele.fi (Postfix) with ESMTP id 547D811FE; Thu, 6 Sep 2012 15:45:23 +0300 (EEST) Received: by ydin.reaktio.net (Postfix, from userid 1001) id 26E9A2005D; Thu, 6 Sep 2012 15:45:23 +0300 (EEST) Date: Thu, 6 Sep 2012 15:45:23 +0300 From: Pasi =?iso-8859-1?Q?K=E4rkk=E4inen?= To: Ian Campbell Message-ID: <20120906124522.GS8912@reaktio.net> References: <1346922207.23055.29.camel@zakaz.uk.xensource.com> MIME-Version: 1.0 Content-Disposition: inline In-Reply-To: <1346922207.23055.29.camel@zakaz.uk.xensource.com> User-Agent: Mutt/1.5.20 (2009-06-14) Cc: "xen-users@lists.xen.org" , kk s Subject: Re: [Xen-users] [Xen-devel] Xen 4.2 rpm build X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org On Thu, Sep 06, 2012 at 10:03:27AM +0100, Ian Campbell wrote: > Please don't cross post to both users and devel. > > Both http://wiki.xen.org/wiki/Asking_Xen_Devel_Questions and > http://wiki.xen.org/wiki/Xen_Users_Netiquette caution against this. > > I have moved xen-devel to BCC. > > On Thu, 2012-09-06 at 09:56 +0100, kk s wrote: > > Can anyone provide the steps to build rpm from source for Xen 4.1.2? > > Have you searched the wiki and tries using a search engine? There are > plenty of tutorials around. > Grab Xen 4.1.2 or Xen 4.1.3 src.rpm from Fedora 16 or Fedora 17 and use/modify/rebuild that? -- Pasi _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Thu Sep 06 12:46:32 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Thu, 06 Sep 2012 12:46:32 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1T9bSZ-0008BH-4T; Thu, 06 Sep 2012 12:45:27 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1T9bSX-0008BC-P7 for xen-users@lists.xen.org; Thu, 06 Sep 2012 12:45:25 +0000 Received: from [85.158.139.83:15810] by server-12.bemta-5.messagelabs.com id 70/56-18300-4EA98405; Thu, 06 Sep 2012 12:45:24 +0000 X-Env-Sender: pasik@iki.fi X-Msg-Ref: server-10.tower-182.messagelabs.com!1346935523!29230751!1 X-Originating-IP: [192.89.123.25] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogMTkyLjg5LjEyMy4yNSA9PiA1MDQ1MDg=\n X-StarScan-Received: X-StarScan-Version: 6.6.1.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 17358 invoked from network); 6 Sep 2012 12:45:24 -0000 Received: from smtp.tele.fi (HELO smtp.tele.fi) (192.89.123.25) by server-10.tower-182.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 6 Sep 2012 12:45:24 -0000 X-Originating-Ip: [194.89.68.22] Received: from ydin.reaktio.net (reaktio.net [194.89.68.22]) by smtp.tele.fi (Postfix) with ESMTP id 547D811FE; Thu, 6 Sep 2012 15:45:23 +0300 (EEST) Received: by ydin.reaktio.net (Postfix, from userid 1001) id 26E9A2005D; Thu, 6 Sep 2012 15:45:23 +0300 (EEST) Date: Thu, 6 Sep 2012 15:45:23 +0300 From: Pasi =?iso-8859-1?Q?K=E4rkk=E4inen?= To: Ian Campbell Message-ID: <20120906124522.GS8912@reaktio.net> References: <1346922207.23055.29.camel@zakaz.uk.xensource.com> MIME-Version: 1.0 Content-Disposition: inline In-Reply-To: <1346922207.23055.29.camel@zakaz.uk.xensource.com> User-Agent: Mutt/1.5.20 (2009-06-14) Cc: "xen-users@lists.xen.org" , kk s Subject: Re: [Xen-users] [Xen-devel] Xen 4.2 rpm build X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org On Thu, Sep 06, 2012 at 10:03:27AM +0100, Ian Campbell wrote: > Please don't cross post to both users and devel. > > Both http://wiki.xen.org/wiki/Asking_Xen_Devel_Questions and > http://wiki.xen.org/wiki/Xen_Users_Netiquette caution against this. > > I have moved xen-devel to BCC. > > On Thu, 2012-09-06 at 09:56 +0100, kk s wrote: > > Can anyone provide the steps to build rpm from source for Xen 4.1.2? > > Have you searched the wiki and tries using a search engine? There are > plenty of tutorials around. > Grab Xen 4.1.2 or Xen 4.1.3 src.rpm from Fedora 16 or Fedora 17 and use/modify/rebuild that? -- Pasi _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Thu Sep 06 12:47:23 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Thu, 06 Sep 2012 12:47:23 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1T9bTQ-0008Du-Qz; Thu, 06 Sep 2012 12:46:20 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1T9bTP-0008Dl-C5 for xen-users@lists.xen.org; Thu, 06 Sep 2012 12:46:19 +0000 Received: from [85.158.139.83:38209] by server-10.bemta-5.messagelabs.com id C5/C9-10969-A1B98405; Thu, 06 Sep 2012 12:46:18 +0000 X-Env-Sender: pasik@iki.fi X-Msg-Ref: server-3.tower-182.messagelabs.com!1346935577!28929644!1 X-Originating-IP: [192.89.123.25] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogMTkyLjg5LjEyMy4yNSA9PiA1MDQ1MDg=\n X-StarScan-Received: X-StarScan-Version: 6.6.1.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 5695 invoked from network); 6 Sep 2012 12:46:18 -0000 Received: from smtp.tele.fi (HELO smtp.tele.fi) (192.89.123.25) by server-3.tower-182.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 6 Sep 2012 12:46:18 -0000 X-Originating-Ip: [194.89.68.22] Received: from ydin.reaktio.net (reaktio.net [194.89.68.22]) by smtp.tele.fi (Postfix) with ESMTP id 661F11286; Thu, 6 Sep 2012 15:46:17 +0300 (EEST) Received: by ydin.reaktio.net (Postfix, from userid 1001) id 4DC662005D; Thu, 6 Sep 2012 15:46:17 +0300 (EEST) Date: Thu, 6 Sep 2012 15:46:17 +0300 From: Pasi =?iso-8859-1?Q?K=E4rkk=E4inen?= To: kk s Message-ID: <20120906124617.GT8912@reaktio.net> References: MIME-Version: 1.0 Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.20 (2009-06-14) Cc: xen-users@lists.xen.org Subject: Re: [Xen-users] [Xen-devel] Issue with making rpm with patch applied X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org On Thu, Sep 06, 2012 at 02:44:39PM +0530, kk s wrote: > Hi, > > I have downloaded src rpm from gitco and extracted into the > /usr/src/redhat/SOURCES dir then downloaded the patches and renamed it as > properly like xen-3.4.4-xsa17-qemu-xen-traditional-all.patch. Then edited > the xen-x.spec file and added the patches. After that I have tried to make > rpm using rpmbuild -bb xen-x.spec and I ended up with the below error, > > Patch #13 (xen-3.4.4-xsa17-qemu-xen-traditional-all.patch): > + patch -p1 -s > The text leading up to this was: > -------------------------- > |console: bounds check whenever changing the cursor due to an escape code > | > |This is XSA-17 / CVE-2012-3515 > | > |Signed-off-by: Ian Campbell <[1]ian.campbell@citrix.com> > | > |diff --git a/console.c b/console.c > |index 5e6e3d0..9984d6f 100644 > |--- a/console.c > |+++ b/console.c > -------------------------- > File to patch: > > Fyi : I have added the patches xsa12-all.patch, > xsa14-xen-3.4-and-4.x.patch and xsa17-qemu-xen-traditional-all.patch. All > the patches goes fine expect xsa17-qemu-xen-traditional-all.patch. > > May I know how can I apply this? > With a quick look at your email it looks like wrong -p option for patch? -- Pasi _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Thu Sep 06 12:47:23 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Thu, 06 Sep 2012 12:47:23 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1T9bTQ-0008Du-Qz; Thu, 06 Sep 2012 12:46:20 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1T9bTP-0008Dl-C5 for xen-users@lists.xen.org; Thu, 06 Sep 2012 12:46:19 +0000 Received: from [85.158.139.83:38209] by server-10.bemta-5.messagelabs.com id C5/C9-10969-A1B98405; Thu, 06 Sep 2012 12:46:18 +0000 X-Env-Sender: pasik@iki.fi X-Msg-Ref: server-3.tower-182.messagelabs.com!1346935577!28929644!1 X-Originating-IP: [192.89.123.25] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogMTkyLjg5LjEyMy4yNSA9PiA1MDQ1MDg=\n X-StarScan-Received: X-StarScan-Version: 6.6.1.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 5695 invoked from network); 6 Sep 2012 12:46:18 -0000 Received: from smtp.tele.fi (HELO smtp.tele.fi) (192.89.123.25) by server-3.tower-182.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 6 Sep 2012 12:46:18 -0000 X-Originating-Ip: [194.89.68.22] Received: from ydin.reaktio.net (reaktio.net [194.89.68.22]) by smtp.tele.fi (Postfix) with ESMTP id 661F11286; Thu, 6 Sep 2012 15:46:17 +0300 (EEST) Received: by ydin.reaktio.net (Postfix, from userid 1001) id 4DC662005D; Thu, 6 Sep 2012 15:46:17 +0300 (EEST) Date: Thu, 6 Sep 2012 15:46:17 +0300 From: Pasi =?iso-8859-1?Q?K=E4rkk=E4inen?= To: kk s Message-ID: <20120906124617.GT8912@reaktio.net> References: MIME-Version: 1.0 Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.20 (2009-06-14) Cc: xen-users@lists.xen.org Subject: Re: [Xen-users] [Xen-devel] Issue with making rpm with patch applied X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org On Thu, Sep 06, 2012 at 02:44:39PM +0530, kk s wrote: > Hi, > > I have downloaded src rpm from gitco and extracted into the > /usr/src/redhat/SOURCES dir then downloaded the patches and renamed it as > properly like xen-3.4.4-xsa17-qemu-xen-traditional-all.patch. Then edited > the xen-x.spec file and added the patches. After that I have tried to make > rpm using rpmbuild -bb xen-x.spec and I ended up with the below error, > > Patch #13 (xen-3.4.4-xsa17-qemu-xen-traditional-all.patch): > + patch -p1 -s > The text leading up to this was: > -------------------------- > |console: bounds check whenever changing the cursor due to an escape code > | > |This is XSA-17 / CVE-2012-3515 > | > |Signed-off-by: Ian Campbell <[1]ian.campbell@citrix.com> > | > |diff --git a/console.c b/console.c > |index 5e6e3d0..9984d6f 100644 > |--- a/console.c > |+++ b/console.c > -------------------------- > File to patch: > > Fyi : I have added the patches xsa12-all.patch, > xsa14-xen-3.4-and-4.x.patch and xsa17-qemu-xen-traditional-all.patch. All > the patches goes fine expect xsa17-qemu-xen-traditional-all.patch. > > May I know how can I apply this? > With a quick look at your email it looks like wrong -p option for patch? -- Pasi _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Thu Sep 06 12:59:49 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Thu, 06 Sep 2012 12:59:49 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1T9bfY-0000aw-SU; Thu, 06 Sep 2012 12:58:52 +0000 Received: from mail27.messagelabs.com ([193.109.254.147]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1T9bfW-0000aG-Pw for xen-users@lists.xen.org; Thu, 06 Sep 2012 12:58:50 +0000 X-Env-Sender: pasik@iki.fi X-Msg-Ref: server-8.tower-27.messagelabs.com!1346936324!9873297!1 X-Originating-IP: [192.89.123.25] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogMTkyLjg5LjEyMy4yNSA9PiA1MDQ1MDg=\n X-StarScan-Received: X-StarScan-Version: 6.6.1.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 19996 invoked from network); 6 Sep 2012 12:58:44 -0000 Received: from smtp.tele.fi (HELO smtp.tele.fi) (192.89.123.25) by server-8.tower-27.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 6 Sep 2012 12:58:44 -0000 X-Originating-Ip: [194.89.68.22] Received: from ydin.reaktio.net (reaktio.net [194.89.68.22]) by smtp.tele.fi (Postfix) with ESMTP id 2D82A18DF; Thu, 6 Sep 2012 15:58:44 +0300 (EEST) Received: by ydin.reaktio.net (Postfix, from userid 1001) id 095D52005D; Thu, 6 Sep 2012 15:58:43 +0300 (EEST) Date: Thu, 6 Sep 2012 15:58:43 +0300 From: Pasi =?iso-8859-1?Q?K=E4rkk=E4inen?= To: kk s Message-ID: <20120906125843.GU8912@reaktio.net> References: <20120906124617.GT8912@reaktio.net> MIME-Version: 1.0 Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.20 (2009-06-14) Cc: xen-users@lists.xen.org Subject: Re: [Xen-users] [Xen-devel] Issue with making rpm with patch applied X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org On Thu, Sep 06, 2012 at 06:23:18PM +0530, kk s wrote: > Hi Pasi, > I have tried with the -p options p1 and p0 which doesn't help :( > Well did you verify the file paths? Where is console.c on the xen source tr= ee? = how many directories 'deep' in the tree? = The patch only mentions a/console.c, so you might need to add some more pat= h elements there.. -- Pasi > On Thu, Sep 6, 2012 at 6:16 PM, Pasi K=E4rkk=E4inen <[1]pasik@iki.fi> = wrote: > = > On Thu, Sep 06, 2012 at 02:44:39PM +0530, kk s wrote: > > Hi, > > > > I have downloaded src rpm from gitco and extracted into the > > /usr/src/redhat/SOURCES dir then downloaded the patches and ren= amed > it as > > properly like xen-3.4.4-xsa17-qemu-xen-traditional-all.patch. T= hen > edited > > the xen-x.spec file and added the patches. After that I have tr= ied > to make > > rpm using rpmbuild -bb xen-x.spec and I ended up with the below > error, > > > > Patch #13 (xen-3.4.4-xsa17-qemu-xen-traditional-all.patch): > > + patch -p1 -s > > The text leading up to this was: > > -------------------------- > > |console: bounds check whenever changing the cursor due to an > escape code > > | > > |This is XSA-17 / CVE-2012-3515 > > | > > |Signed-off-by: Ian Campbell <[1][2]ian.campbell@citrix.com> > > | > > |diff --git a/console.c b/console.c > > |index 5e6e3d0..9984d6f 100644 > > |--- a/console.c > > |+++ b/console.c > > -------------------------- > > File to patch: > > > > Fyi : I have added the patches xsa12-all.patch, > > xsa14-xen-3.4-and-4.x.patch and > xsa17-qemu-xen-traditional-all.patch. All > > the patches goes fine expect xsa17-qemu-xen-traditional-all.pat= ch. > > > > May I know how can I apply this? > > > = > With a quick look at your email it looks like wrong -p option for pa= tch? > -- Pasi > = > References > = > Visible links > 1. mailto:pasik@iki.fi > 2. mailto:ian.campbell@citrix.com _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Thu Sep 06 12:59:49 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Thu, 06 Sep 2012 12:59:49 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1T9bfY-0000aw-SU; Thu, 06 Sep 2012 12:58:52 +0000 Received: from mail27.messagelabs.com ([193.109.254.147]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1T9bfW-0000aG-Pw for xen-users@lists.xen.org; Thu, 06 Sep 2012 12:58:50 +0000 X-Env-Sender: pasik@iki.fi X-Msg-Ref: server-8.tower-27.messagelabs.com!1346936324!9873297!1 X-Originating-IP: [192.89.123.25] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogMTkyLjg5LjEyMy4yNSA9PiA1MDQ1MDg=\n X-StarScan-Received: X-StarScan-Version: 6.6.1.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 19996 invoked from network); 6 Sep 2012 12:58:44 -0000 Received: from smtp.tele.fi (HELO smtp.tele.fi) (192.89.123.25) by server-8.tower-27.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 6 Sep 2012 12:58:44 -0000 X-Originating-Ip: [194.89.68.22] Received: from ydin.reaktio.net (reaktio.net [194.89.68.22]) by smtp.tele.fi (Postfix) with ESMTP id 2D82A18DF; Thu, 6 Sep 2012 15:58:44 +0300 (EEST) Received: by ydin.reaktio.net (Postfix, from userid 1001) id 095D52005D; Thu, 6 Sep 2012 15:58:43 +0300 (EEST) Date: Thu, 6 Sep 2012 15:58:43 +0300 From: Pasi =?iso-8859-1?Q?K=E4rkk=E4inen?= To: kk s Message-ID: <20120906125843.GU8912@reaktio.net> References: <20120906124617.GT8912@reaktio.net> MIME-Version: 1.0 Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.20 (2009-06-14) Cc: xen-users@lists.xen.org Subject: Re: [Xen-users] [Xen-devel] Issue with making rpm with patch applied X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org On Thu, Sep 06, 2012 at 06:23:18PM +0530, kk s wrote: > Hi Pasi, > I have tried with the -p options p1 and p0 which doesn't help :( > Well did you verify the file paths? Where is console.c on the xen source tr= ee? = how many directories 'deep' in the tree? = The patch only mentions a/console.c, so you might need to add some more pat= h elements there.. -- Pasi > On Thu, Sep 6, 2012 at 6:16 PM, Pasi K=E4rkk=E4inen <[1]pasik@iki.fi> = wrote: > = > On Thu, Sep 06, 2012 at 02:44:39PM +0530, kk s wrote: > > Hi, > > > > I have downloaded src rpm from gitco and extracted into the > > /usr/src/redhat/SOURCES dir then downloaded the patches and ren= amed > it as > > properly like xen-3.4.4-xsa17-qemu-xen-traditional-all.patch. T= hen > edited > > the xen-x.spec file and added the patches. After that I have tr= ied > to make > > rpm using rpmbuild -bb xen-x.spec and I ended up with the below > error, > > > > Patch #13 (xen-3.4.4-xsa17-qemu-xen-traditional-all.patch): > > + patch -p1 -s > > The text leading up to this was: > > -------------------------- > > |console: bounds check whenever changing the cursor due to an > escape code > > | > > |This is XSA-17 / CVE-2012-3515 > > | > > |Signed-off-by: Ian Campbell <[1][2]ian.campbell@citrix.com> > > | > > |diff --git a/console.c b/console.c > > |index 5e6e3d0..9984d6f 100644 > > |--- a/console.c > > |+++ b/console.c > > -------------------------- > > File to patch: > > > > Fyi : I have added the patches xsa12-all.patch, > > xsa14-xen-3.4-and-4.x.patch and > xsa17-qemu-xen-traditional-all.patch. All > > the patches goes fine expect xsa17-qemu-xen-traditional-all.pat= ch. > > > > May I know how can I apply this? > > > = > With a quick look at your email it looks like wrong -p option for pa= tch? > -- Pasi > = > References > = > Visible links > 1. mailto:pasik@iki.fi > 2. mailto:ian.campbell@citrix.com _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Thu Sep 06 13:25:37 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Thu, 06 Sep 2012 13:25:37 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1T9c4Z-0001tl-9O; Thu, 06 Sep 2012 13:24:43 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1T9baC-0000Ka-Qz for xen-users@lists.xen.org; Thu, 06 Sep 2012 12:53:21 +0000 Received: from [85.158.139.83:38370] by server-7.bemta-5.messagelabs.com id B9/F5-19703-FBC98405; Thu, 06 Sep 2012 12:53:19 +0000 X-Env-Sender: kks.kbase@gmail.com X-Msg-Ref: server-13.tower-182.messagelabs.com!1346935998!28414314!1 X-Originating-IP: [209.85.214.45] X-SpamReason: No, hits=0.4 required=7.0 tests=HTML_30_40,HTML_MESSAGE, ML_RADAR_SPEW_LINKS_14,RCVD_BY_IP,spamassassin: X-StarScan-Received: X-StarScan-Version: 6.6.1.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 25535 invoked from network); 6 Sep 2012 12:53:19 -0000 Received: from mail-bk0-f45.google.com (HELO mail-bk0-f45.google.com) (209.85.214.45) by server-13.tower-182.messagelabs.com with RC4-SHA encrypted SMTP; 6 Sep 2012 12:53:19 -0000 Received: by bkcji1 with SMTP id ji1so780613bkc.32 for ; Thu, 06 Sep 2012 05:53:18 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=DvMR43rq+hV9OcRfrEJElKItekECwVGpbjdSZu0pBlE=; b=BCcD165UV3SvV30Yj5fJtdqHkL8onR0Koha2mxOd0PmaDYffYZ8JhhHxS2BFs7MIy9 1uwAMXSb3rX2f71Cj1pyYmXFu01E4paeiGFIklN1Bob3kaBkf5qnb9rKSy6dn4bPhteN 0EQzt7AYbJ1s8Eg5rf1D0gSl30swRXrOBgbO9JJNmnR3lNlqSBT5uuhq/6kCcFaGalbd 4l+pO1RYoQR8Tf7MELA39sYNbQP0ZbuYO32TGtTumDqqLw49OHBa8T7CX/RkZkarAvvl 7F0Tp1XCLZ5rdXmS5jQy/WmfS5dEeTnenKHdarP0TJSy5d4KzVWM+esDLHLpO+NP5xXV LlUA== MIME-Version: 1.0 Received: by 10.205.134.133 with SMTP id ic5mr900981bkc.15.1346935998370; Thu, 06 Sep 2012 05:53:18 -0700 (PDT) Received: by 10.204.56.134 with HTTP; Thu, 6 Sep 2012 05:53:18 -0700 (PDT) In-Reply-To: <20120906124617.GT8912@reaktio.net> References: <20120906124617.GT8912@reaktio.net> Date: Thu, 6 Sep 2012 18:23:18 +0530 Message-ID: From: kk s To: =?ISO-8859-1?Q?Pasi_K=E4rkk=E4inen?= X-Mailman-Approved-At: Thu, 06 Sep 2012 13:24:41 +0000 Cc: xen-users@lists.xen.org Subject: Re: [Xen-users] [Xen-devel] Issue with making rpm with patch applied X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============5726088642040927986==" Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org --===============5726088642040927986== Content-Type: multipart/alternative; boundary=00151747b77cb7d32b04c907f957 --00151747b77cb7d32b04c907f957 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Hi Pasi, I have tried with the -p options p1 and p0 which doesn't help :( On Thu, Sep 6, 2012 at 6:16 PM, Pasi K=E4rkk=E4inen wrote: > On Thu, Sep 06, 2012 at 02:44:39PM +0530, kk s wrote: > > Hi, > > > > I have downloaded src rpm from gitco and extracted into the > > /usr/src/redhat/SOURCES dir then downloaded the patches and renamed > it as > > properly like xen-3.4.4-xsa17-qemu-xen-traditional-all.patch. Then > edited > > the xen-x.spec file and added the patches. After that I have tried t= o > make > > rpm using rpmbuild -bb xen-x.spec and I ended up with the below erro= r, > > > > Patch #13 (xen-3.4.4-xsa17-qemu-xen-traditional-all.patch): > > + patch -p1 -s > > The text leading up to this was: > > -------------------------- > > |console: bounds check whenever changing the cursor due to an escape > code > > | > > |This is XSA-17 / CVE-2012-3515 > > | > > |Signed-off-by: Ian Campbell <[1]ian.campbell@citrix.com> > > | > > |diff --git a/console.c b/console.c > > |index 5e6e3d0..9984d6f 100644 > > |--- a/console.c > > |+++ b/console.c > > -------------------------- > > File to patch: > > > > Fyi : I have added the patches xsa12-all.patch, > > xsa14-xen-3.4-and-4.x.patch and xsa17-qemu-xen-traditional-all.patch= . > All > > the patches goes fine expect xsa17-qemu-xen-traditional-all.patch. > > > > May I know how can I apply this? > > > > With a quick look at your email it looks like wrong -p option for patch? > > -- Pasi > > --00151747b77cb7d32b04c907f957 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable
Hi Pasi,

I have tried with the -p options= p1 and p0 which doesn't help :(

On= Thu, Sep 6, 2012 at 6:16 PM, Pasi K=E4rkk=E4inen <pasik@iki.fi> = wrote:
On Thu, Sep 06, 2012 at 02= :44:39PM +0530, kk s wrote:
> =A0 =A0Hi,
>
> =A0 =A0I have downloaded src rpm from gitco and extracted into the
> =A0 =A0/usr/src/redhat/SOURCES dir then downloaded the patches and ren= amed it as
> =A0 =A0properly like xen-3.4.4-xsa17-qemu-xen-traditional-all.patch. T= hen edited
> =A0 =A0the xen-x.spec file and added the patches. After that I have tr= ied to make
> =A0 =A0rpm using rpmbuild -bb xen-x.spec and I ended up with the below= error,
>
> =A0 =A0Patch #13 (xen-3.4.4-xsa17-qemu-xen-traditional-all.patch):
> =A0 =A0+ patch -p1 -s
> =A0 =A0The text leading up to this was:
> =A0 =A0--------------------------
> =A0 =A0|console: bounds check whenever changing the cursor due to an e= scape code
> =A0 =A0|
> =A0 =A0|This is XSA-17 / CVE-2012-3515
> =A0 =A0|
> =A0 =A0|Signed-off-by: Ian Campbell <[1]ian.campbell@citrix.com>
> =A0 =A0|
> =A0 =A0|diff --git a/console.c b/console.c
> =A0 =A0|index 5e6e3d0..9984d6f 100644
> =A0 =A0|--- a/console.c
> =A0 =A0|+++ b/console.c
> =A0 =A0--------------------------
> =A0 =A0File to patch:
>
> =A0 =A0Fyi : I have added the patches xsa12-all.patch,
> =A0 =A0xsa14-xen-3.4-and-4.x.patch and xsa17-qemu-xen-traditional-all.= patch. All
> =A0 =A0the patches goes fine expect xsa17-qemu-xen-traditional-all.pat= ch.
>
> =A0 =A0May I know how can I apply this?
>

With a quick look at your email it looks like wrong -p option for pat= ch?

-- Pasi


--00151747b77cb7d32b04c907f957-- --===============5726088642040927986== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users --===============5726088642040927986==-- From xen-users-bounces@lists.xen.org Thu Sep 06 13:25:37 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Thu, 06 Sep 2012 13:25:37 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1T9c4Z-0001tl-9O; Thu, 06 Sep 2012 13:24:43 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1T9baC-0000Ka-Qz for xen-users@lists.xen.org; Thu, 06 Sep 2012 12:53:21 +0000 Received: from [85.158.139.83:38370] by server-7.bemta-5.messagelabs.com id B9/F5-19703-FBC98405; Thu, 06 Sep 2012 12:53:19 +0000 X-Env-Sender: kks.kbase@gmail.com X-Msg-Ref: server-13.tower-182.messagelabs.com!1346935998!28414314!1 X-Originating-IP: [209.85.214.45] X-SpamReason: No, hits=0.4 required=7.0 tests=HTML_30_40,HTML_MESSAGE, ML_RADAR_SPEW_LINKS_14,RCVD_BY_IP,spamassassin: X-StarScan-Received: X-StarScan-Version: 6.6.1.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 25535 invoked from network); 6 Sep 2012 12:53:19 -0000 Received: from mail-bk0-f45.google.com (HELO mail-bk0-f45.google.com) (209.85.214.45) by server-13.tower-182.messagelabs.com with RC4-SHA encrypted SMTP; 6 Sep 2012 12:53:19 -0000 Received: by bkcji1 with SMTP id ji1so780613bkc.32 for ; Thu, 06 Sep 2012 05:53:18 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=DvMR43rq+hV9OcRfrEJElKItekECwVGpbjdSZu0pBlE=; b=BCcD165UV3SvV30Yj5fJtdqHkL8onR0Koha2mxOd0PmaDYffYZ8JhhHxS2BFs7MIy9 1uwAMXSb3rX2f71Cj1pyYmXFu01E4paeiGFIklN1Bob3kaBkf5qnb9rKSy6dn4bPhteN 0EQzt7AYbJ1s8Eg5rf1D0gSl30swRXrOBgbO9JJNmnR3lNlqSBT5uuhq/6kCcFaGalbd 4l+pO1RYoQR8Tf7MELA39sYNbQP0ZbuYO32TGtTumDqqLw49OHBa8T7CX/RkZkarAvvl 7F0Tp1XCLZ5rdXmS5jQy/WmfS5dEeTnenKHdarP0TJSy5d4KzVWM+esDLHLpO+NP5xXV LlUA== MIME-Version: 1.0 Received: by 10.205.134.133 with SMTP id ic5mr900981bkc.15.1346935998370; Thu, 06 Sep 2012 05:53:18 -0700 (PDT) Received: by 10.204.56.134 with HTTP; Thu, 6 Sep 2012 05:53:18 -0700 (PDT) In-Reply-To: <20120906124617.GT8912@reaktio.net> References: <20120906124617.GT8912@reaktio.net> Date: Thu, 6 Sep 2012 18:23:18 +0530 Message-ID: From: kk s To: =?ISO-8859-1?Q?Pasi_K=E4rkk=E4inen?= X-Mailman-Approved-At: Thu, 06 Sep 2012 13:24:41 +0000 Cc: xen-users@lists.xen.org Subject: Re: [Xen-users] [Xen-devel] Issue with making rpm with patch applied X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============5726088642040927986==" Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org --===============5726088642040927986== Content-Type: multipart/alternative; boundary=00151747b77cb7d32b04c907f957 --00151747b77cb7d32b04c907f957 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Hi Pasi, I have tried with the -p options p1 and p0 which doesn't help :( On Thu, Sep 6, 2012 at 6:16 PM, Pasi K=E4rkk=E4inen wrote: > On Thu, Sep 06, 2012 at 02:44:39PM +0530, kk s wrote: > > Hi, > > > > I have downloaded src rpm from gitco and extracted into the > > /usr/src/redhat/SOURCES dir then downloaded the patches and renamed > it as > > properly like xen-3.4.4-xsa17-qemu-xen-traditional-all.patch. Then > edited > > the xen-x.spec file and added the patches. After that I have tried t= o > make > > rpm using rpmbuild -bb xen-x.spec and I ended up with the below erro= r, > > > > Patch #13 (xen-3.4.4-xsa17-qemu-xen-traditional-all.patch): > > + patch -p1 -s > > The text leading up to this was: > > -------------------------- > > |console: bounds check whenever changing the cursor due to an escape > code > > | > > |This is XSA-17 / CVE-2012-3515 > > | > > |Signed-off-by: Ian Campbell <[1]ian.campbell@citrix.com> > > | > > |diff --git a/console.c b/console.c > > |index 5e6e3d0..9984d6f 100644 > > |--- a/console.c > > |+++ b/console.c > > -------------------------- > > File to patch: > > > > Fyi : I have added the patches xsa12-all.patch, > > xsa14-xen-3.4-and-4.x.patch and xsa17-qemu-xen-traditional-all.patch= . > All > > the patches goes fine expect xsa17-qemu-xen-traditional-all.patch. > > > > May I know how can I apply this? > > > > With a quick look at your email it looks like wrong -p option for patch? > > -- Pasi > > --00151747b77cb7d32b04c907f957 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable
Hi Pasi,

I have tried with the -p options= p1 and p0 which doesn't help :(

On= Thu, Sep 6, 2012 at 6:16 PM, Pasi K=E4rkk=E4inen <pasik@iki.fi> = wrote:
On Thu, Sep 06, 2012 at 02= :44:39PM +0530, kk s wrote:
> =A0 =A0Hi,
>
> =A0 =A0I have downloaded src rpm from gitco and extracted into the
> =A0 =A0/usr/src/redhat/SOURCES dir then downloaded the patches and ren= amed it as
> =A0 =A0properly like xen-3.4.4-xsa17-qemu-xen-traditional-all.patch. T= hen edited
> =A0 =A0the xen-x.spec file and added the patches. After that I have tr= ied to make
> =A0 =A0rpm using rpmbuild -bb xen-x.spec and I ended up with the below= error,
>
> =A0 =A0Patch #13 (xen-3.4.4-xsa17-qemu-xen-traditional-all.patch):
> =A0 =A0+ patch -p1 -s
> =A0 =A0The text leading up to this was:
> =A0 =A0--------------------------
> =A0 =A0|console: bounds check whenever changing the cursor due to an e= scape code
> =A0 =A0|
> =A0 =A0|This is XSA-17 / CVE-2012-3515
> =A0 =A0|
> =A0 =A0|Signed-off-by: Ian Campbell <[1]ian.campbell@citrix.com>
> =A0 =A0|
> =A0 =A0|diff --git a/console.c b/console.c
> =A0 =A0|index 5e6e3d0..9984d6f 100644
> =A0 =A0|--- a/console.c
> =A0 =A0|+++ b/console.c
> =A0 =A0--------------------------
> =A0 =A0File to patch:
>
> =A0 =A0Fyi : I have added the patches xsa12-all.patch,
> =A0 =A0xsa14-xen-3.4-and-4.x.patch and xsa17-qemu-xen-traditional-all.= patch. All
> =A0 =A0the patches goes fine expect xsa17-qemu-xen-traditional-all.pat= ch.
>
> =A0 =A0May I know how can I apply this?
>

With a quick look at your email it looks like wrong -p option for pat= ch?

-- Pasi


--00151747b77cb7d32b04c907f957-- --===============5726088642040927986== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users --===============5726088642040927986==-- From xen-users-bounces@lists.xen.org Thu Sep 06 13:25:38 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Thu, 06 Sep 2012 13:25:38 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1T9c4Z-0001tu-Sm; Thu, 06 Sep 2012 13:24:43 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1T9c1P-0001pU-4u for xen-users@lists.xen.org; Thu, 06 Sep 2012 13:21:27 +0000 Received: from [85.158.138.51:55251] by server-11.bemta-3.messagelabs.com id F7/2A-30250-653A8405; Thu, 06 Sep 2012 13:21:26 +0000 X-Env-Sender: kks.kbase@gmail.com X-Msg-Ref: server-2.tower-174.messagelabs.com!1346937685!29072021!1 X-Originating-IP: [209.85.214.45] X-SpamReason: No, hits=0.4 required=7.0 tests=HTML_30_40,HTML_MESSAGE, ML_RADAR_SPEW_LINKS_14,RCVD_BY_IP,spamassassin: X-StarScan-Received: X-StarScan-Version: 6.6.1.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 4652 invoked from network); 6 Sep 2012 13:21:25 -0000 Received: from mail-bk0-f45.google.com (HELO mail-bk0-f45.google.com) (209.85.214.45) by server-2.tower-174.messagelabs.com with RC4-SHA encrypted SMTP; 6 Sep 2012 13:21:25 -0000 Received: by bkcji1 with SMTP id ji1so797708bkc.32 for ; Thu, 06 Sep 2012 06:21:25 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=5RUqCLRcHVpRVMI1PxR9341JXusLX4kes7cqSNLzdww=; b=FVYoKLRAypCI3PgH1WFk2Evm/AmfLON8fTByv3fiYUvPh0vP9HaZPSwSe0dlWt4/Us v+6U/kN4/rpaWAz3AB8/jaBHqmzC+p0fsFxcDA6/85Ql20/VqFsFq0xPV58YsPyPyUZd ijlvG4559sUnsBnujPMZbawEhgfONiWLzw+Ch7ZQUwMq17p7i4p6xr5a6y5E48KU82tj nk5S6qgVEkrPHUyCy5tFtXGZjlXXqgLwFJ79lG2zR05V579tdpj7phv03uLemtlRonAJ FuFKb4Dl+eWw8KhwDvnX+kvYOW/EiL4rerea2Zkubt5Hx10K3ZaOCg6vilvmzt7SHnih t/SA== MIME-Version: 1.0 Received: by 10.205.126.13 with SMTP id gu13mr915309bkc.79.1346937684875; Thu, 06 Sep 2012 06:21:24 -0700 (PDT) Received: by 10.204.56.134 with HTTP; Thu, 6 Sep 2012 06:21:24 -0700 (PDT) In-Reply-To: <20120906125843.GU8912@reaktio.net> References: <20120906124617.GT8912@reaktio.net> <20120906125843.GU8912@reaktio.net> Date: Thu, 6 Sep 2012 18:51:24 +0530 Message-ID: From: kk s To: =?ISO-8859-1?Q?Pasi_K=E4rkk=E4inen?= X-Mailman-Approved-At: Thu, 06 Sep 2012 13:24:41 +0000 Cc: xen-users@lists.xen.org Subject: Re: [Xen-users] [Xen-devel] Issue with making rpm with patch applied X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============7676034870965912750==" Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org --===============7676034870965912750== Content-Type: multipart/alternative; boundary=00151747b7443dd88c04c9085e2e --00151747b7443dd88c04c9085e2e Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Hi Pasi, You are right. It looks like the path is wrong and I have changed from a/console.c to a/tools/ioemu-qemu-xen/console.c and as well for b/ which going fine. May I confirm is this correct file that I am applying? On Thu, Sep 6, 2012 at 6:28 PM, Pasi K=E4rkk=E4inen wrote: > On Thu, Sep 06, 2012 at 06:23:18PM +0530, kk s wrote: > > Hi Pasi, > > I have tried with the -p options p1 and p0 which doesn't help :( > > > > Well did you verify the file paths? Where is console.c on the xen source > tree? > how many directories 'deep' in the tree? > > The patch only mentions a/console.c, so you might need to add some more > path elements there.. > > -- Pasi > > > On Thu, Sep 6, 2012 at 6:16 PM, Pasi K=E4rkk=E4inen <[1]pasik@iki.fi= > > wrote: > > > > On Thu, Sep 06, 2012 at 02:44:39PM +0530, kk s wrote: > > > Hi, > > > > > > I have downloaded src rpm from gitco and extracted into the > > > /usr/src/redhat/SOURCES dir then downloaded the patches and > renamed > > it as > > > properly like xen-3.4.4-xsa17-qemu-xen-traditional-all.patch. > Then > > edited > > > the xen-x.spec file and added the patches. After that I have > tried > > to make > > > rpm using rpmbuild -bb xen-x.spec and I ended up with the bel= ow > > error, > > > > > > Patch #13 (xen-3.4.4-xsa17-qemu-xen-traditional-all.patch): > > > + patch -p1 -s > > > The text leading up to this was: > > > -------------------------- > > > |console: bounds check whenever changing the cursor due to an > > escape code > > > | > > > |This is XSA-17 / CVE-2012-3515 > > > | > > > |Signed-off-by: Ian Campbell <[1][2]ian.campbell@citrix.com> > > > | > > > |diff --git a/console.c b/console.c > > > |index 5e6e3d0..9984d6f 100644 > > > |--- a/console.c > > > |+++ b/console.c > > > -------------------------- > > > File to patch: > > > > > > Fyi : I have added the patches xsa12-all.patch, > > > xsa14-xen-3.4-and-4.x.patch and > > xsa17-qemu-xen-traditional-all.patch. All > > > the patches goes fine expect > xsa17-qemu-xen-traditional-all.patch. > > > > > > May I know how can I apply this? > > > > > > > With a quick look at your email it looks like wrong -p option for > patch? > > -- Pasi > > > > References > > > > Visible links > > 1. mailto:pasik@iki.fi > > 2. mailto:ian.campbell@citrix.com > --00151747b7443dd88c04c9085e2e Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable
Hi Pasi,

You are right.

It looks like the path is wrong and I have changed from a/console.c= to a/tools/ioemu-qemu-xen/console.c and as well for b/ which going fine.

May I confirm is this correct file that I am applying?<= /div>
On Thu, Sep 6, 2012 at 6:28 PM, Pasi K= =E4rkk=E4inen <pasik@iki.fi> wrote:
On Thu, Sep 06, 2012 at 06= :23:18PM +0530, kk s wrote:
> =A0 =A0Hi Pasi,
> =A0 =A0I have tried with the -p options p1 and p0 which doesn't he= lp :(
>

Well did you verify the file paths? Where is console.c on the xen sou= rce tree?
how many directories 'deep' in the tree?

The patch only mentions a/console.c, so you might need to add some more pat= h elements there..

-- Pasi

> =A0 =A0On Thu, Sep 6, 2012 at 6:16 PM, Pasi K=E4rkk=E4inen <[1]pasik@iki.fi> wrote:
>
> =A0 =A0 =A0On Thu, Sep 06, 2012 at 02:44:39PM +0530, kk s wrote:
> =A0 =A0 =A0> =A0 =A0Hi,
> =A0 =A0 =A0>
> =A0 =A0 =A0> =A0 =A0I have downloaded src rpm from gitco and extrac= ted into the
> =A0 =A0 =A0> =A0 =A0/usr/src/redhat/SOURCES dir then downloaded the= patches and renamed
> =A0 =A0 =A0it as
> =A0 =A0 =A0> =A0 =A0properly like xen-3.4.4-xsa17-qemu-xen-traditio= nal-all.patch. Then
> =A0 =A0 =A0edited
> =A0 =A0 =A0> =A0 =A0the xen-x.spec file and added the patches. Afte= r that I have tried
> =A0 =A0 =A0to make
> =A0 =A0 =A0> =A0 =A0rpm using rpmbuild -bb xen-x.spec and I ended u= p with the below
> =A0 =A0 =A0error,
> =A0 =A0 =A0>
> =A0 =A0 =A0> =A0 =A0Patch #13 (xen-3.4.4-xsa17-qemu-xen-traditional= -all.patch):
> =A0 =A0 =A0> =A0 =A0+ patch -p1 -s
> =A0 =A0 =A0> =A0 =A0The text leading up to this was:
> =A0 =A0 =A0> =A0 =A0--------------------------
> =A0 =A0 =A0> =A0 =A0|console: bounds check whenever changing the cu= rsor due to an
> =A0 =A0 =A0escape code
> =A0 =A0 =A0> =A0 =A0|
> =A0 =A0 =A0> =A0 =A0|This is XSA-17 / CVE-2012-3515
> =A0 =A0 =A0> =A0 =A0|
> =A0 =A0 =A0> =A0 =A0|Signed-off-by: Ian Campbell <[1][2]ian.campbell@citrix.com>
> =A0 =A0 =A0> =A0 =A0|
> =A0 =A0 =A0> =A0 =A0|diff --git a/console.c b/console.c
> =A0 =A0 =A0> =A0 =A0|index 5e6e3d0..9984d6f 100644
> =A0 =A0 =A0> =A0 =A0|--- a/console.c
> =A0 =A0 =A0> =A0 =A0|+++ b/console.c
> =A0 =A0 =A0> =A0 =A0--------------------------
> =A0 =A0 =A0> =A0 =A0File to patch:
> =A0 =A0 =A0>
> =A0 =A0 =A0> =A0 =A0Fyi : I have added the patches xsa12-all.patch,=
> =A0 =A0 =A0> =A0 =A0xsa14-xen-3.4-and-4.x.patch and
> =A0 =A0 =A0xsa17-qemu-xen-traditional-all.patch. All
> =A0 =A0 =A0> =A0 =A0the patches goes fine expect xsa17-qemu-xen-tra= ditional-all.patch.
> =A0 =A0 =A0>
> =A0 =A0 =A0> =A0 =A0May I know how can I apply this?
> =A0 =A0 =A0>
>
> =A0 =A0 =A0With a quick look at your email it looks like wrong -p opti= on for patch?
> =A0 =A0 =A0-- Pasi
>
> References
>
> =A0 =A0Visible links
> =A0 =A01. mailto:pasik@iki.fi
> =A0 =A02. mailto:ian.campbe= ll@citrix.com

--00151747b7443dd88c04c9085e2e-- --===============7676034870965912750== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users --===============7676034870965912750==-- From xen-users-bounces@lists.xen.org Thu Sep 06 13:25:38 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Thu, 06 Sep 2012 13:25:38 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1T9c4Z-0001tu-Sm; Thu, 06 Sep 2012 13:24:43 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1T9c1P-0001pU-4u for xen-users@lists.xen.org; Thu, 06 Sep 2012 13:21:27 +0000 Received: from [85.158.138.51:55251] by server-11.bemta-3.messagelabs.com id F7/2A-30250-653A8405; Thu, 06 Sep 2012 13:21:26 +0000 X-Env-Sender: kks.kbase@gmail.com X-Msg-Ref: server-2.tower-174.messagelabs.com!1346937685!29072021!1 X-Originating-IP: [209.85.214.45] X-SpamReason: No, hits=0.4 required=7.0 tests=HTML_30_40,HTML_MESSAGE, ML_RADAR_SPEW_LINKS_14,RCVD_BY_IP,spamassassin: X-StarScan-Received: X-StarScan-Version: 6.6.1.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 4652 invoked from network); 6 Sep 2012 13:21:25 -0000 Received: from mail-bk0-f45.google.com (HELO mail-bk0-f45.google.com) (209.85.214.45) by server-2.tower-174.messagelabs.com with RC4-SHA encrypted SMTP; 6 Sep 2012 13:21:25 -0000 Received: by bkcji1 with SMTP id ji1so797708bkc.32 for ; Thu, 06 Sep 2012 06:21:25 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=5RUqCLRcHVpRVMI1PxR9341JXusLX4kes7cqSNLzdww=; b=FVYoKLRAypCI3PgH1WFk2Evm/AmfLON8fTByv3fiYUvPh0vP9HaZPSwSe0dlWt4/Us v+6U/kN4/rpaWAz3AB8/jaBHqmzC+p0fsFxcDA6/85Ql20/VqFsFq0xPV58YsPyPyUZd ijlvG4559sUnsBnujPMZbawEhgfONiWLzw+Ch7ZQUwMq17p7i4p6xr5a6y5E48KU82tj nk5S6qgVEkrPHUyCy5tFtXGZjlXXqgLwFJ79lG2zR05V579tdpj7phv03uLemtlRonAJ FuFKb4Dl+eWw8KhwDvnX+kvYOW/EiL4rerea2Zkubt5Hx10K3ZaOCg6vilvmzt7SHnih t/SA== MIME-Version: 1.0 Received: by 10.205.126.13 with SMTP id gu13mr915309bkc.79.1346937684875; Thu, 06 Sep 2012 06:21:24 -0700 (PDT) Received: by 10.204.56.134 with HTTP; Thu, 6 Sep 2012 06:21:24 -0700 (PDT) In-Reply-To: <20120906125843.GU8912@reaktio.net> References: <20120906124617.GT8912@reaktio.net> <20120906125843.GU8912@reaktio.net> Date: Thu, 6 Sep 2012 18:51:24 +0530 Message-ID: From: kk s To: =?ISO-8859-1?Q?Pasi_K=E4rkk=E4inen?= X-Mailman-Approved-At: Thu, 06 Sep 2012 13:24:41 +0000 Cc: xen-users@lists.xen.org Subject: Re: [Xen-users] [Xen-devel] Issue with making rpm with patch applied X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============7676034870965912750==" Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org --===============7676034870965912750== Content-Type: multipart/alternative; boundary=00151747b7443dd88c04c9085e2e --00151747b7443dd88c04c9085e2e Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Hi Pasi, You are right. It looks like the path is wrong and I have changed from a/console.c to a/tools/ioemu-qemu-xen/console.c and as well for b/ which going fine. May I confirm is this correct file that I am applying? On Thu, Sep 6, 2012 at 6:28 PM, Pasi K=E4rkk=E4inen wrote: > On Thu, Sep 06, 2012 at 06:23:18PM +0530, kk s wrote: > > Hi Pasi, > > I have tried with the -p options p1 and p0 which doesn't help :( > > > > Well did you verify the file paths? Where is console.c on the xen source > tree? > how many directories 'deep' in the tree? > > The patch only mentions a/console.c, so you might need to add some more > path elements there.. > > -- Pasi > > > On Thu, Sep 6, 2012 at 6:16 PM, Pasi K=E4rkk=E4inen <[1]pasik@iki.fi= > > wrote: > > > > On Thu, Sep 06, 2012 at 02:44:39PM +0530, kk s wrote: > > > Hi, > > > > > > I have downloaded src rpm from gitco and extracted into the > > > /usr/src/redhat/SOURCES dir then downloaded the patches and > renamed > > it as > > > properly like xen-3.4.4-xsa17-qemu-xen-traditional-all.patch. > Then > > edited > > > the xen-x.spec file and added the patches. After that I have > tried > > to make > > > rpm using rpmbuild -bb xen-x.spec and I ended up with the bel= ow > > error, > > > > > > Patch #13 (xen-3.4.4-xsa17-qemu-xen-traditional-all.patch): > > > + patch -p1 -s > > > The text leading up to this was: > > > -------------------------- > > > |console: bounds check whenever changing the cursor due to an > > escape code > > > | > > > |This is XSA-17 / CVE-2012-3515 > > > | > > > |Signed-off-by: Ian Campbell <[1][2]ian.campbell@citrix.com> > > > | > > > |diff --git a/console.c b/console.c > > > |index 5e6e3d0..9984d6f 100644 > > > |--- a/console.c > > > |+++ b/console.c > > > -------------------------- > > > File to patch: > > > > > > Fyi : I have added the patches xsa12-all.patch, > > > xsa14-xen-3.4-and-4.x.patch and > > xsa17-qemu-xen-traditional-all.patch. All > > > the patches goes fine expect > xsa17-qemu-xen-traditional-all.patch. > > > > > > May I know how can I apply this? > > > > > > > With a quick look at your email it looks like wrong -p option for > patch? > > -- Pasi > > > > References > > > > Visible links > > 1. mailto:pasik@iki.fi > > 2. mailto:ian.campbell@citrix.com > --00151747b7443dd88c04c9085e2e Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable
Hi Pasi,

You are right.

It looks like the path is wrong and I have changed from a/console.c= to a/tools/ioemu-qemu-xen/console.c and as well for b/ which going fine.

May I confirm is this correct file that I am applying?<= /div>
On Thu, Sep 6, 2012 at 6:28 PM, Pasi K= =E4rkk=E4inen <pasik@iki.fi> wrote:
On Thu, Sep 06, 2012 at 06= :23:18PM +0530, kk s wrote:
> =A0 =A0Hi Pasi,
> =A0 =A0I have tried with the -p options p1 and p0 which doesn't he= lp :(
>

Well did you verify the file paths? Where is console.c on the xen sou= rce tree?
how many directories 'deep' in the tree?

The patch only mentions a/console.c, so you might need to add some more pat= h elements there..

-- Pasi

> =A0 =A0On Thu, Sep 6, 2012 at 6:16 PM, Pasi K=E4rkk=E4inen <[1]pasik@iki.fi> wrote:
>
> =A0 =A0 =A0On Thu, Sep 06, 2012 at 02:44:39PM +0530, kk s wrote:
> =A0 =A0 =A0> =A0 =A0Hi,
> =A0 =A0 =A0>
> =A0 =A0 =A0> =A0 =A0I have downloaded src rpm from gitco and extrac= ted into the
> =A0 =A0 =A0> =A0 =A0/usr/src/redhat/SOURCES dir then downloaded the= patches and renamed
> =A0 =A0 =A0it as
> =A0 =A0 =A0> =A0 =A0properly like xen-3.4.4-xsa17-qemu-xen-traditio= nal-all.patch. Then
> =A0 =A0 =A0edited
> =A0 =A0 =A0> =A0 =A0the xen-x.spec file and added the patches. Afte= r that I have tried
> =A0 =A0 =A0to make
> =A0 =A0 =A0> =A0 =A0rpm using rpmbuild -bb xen-x.spec and I ended u= p with the below
> =A0 =A0 =A0error,
> =A0 =A0 =A0>
> =A0 =A0 =A0> =A0 =A0Patch #13 (xen-3.4.4-xsa17-qemu-xen-traditional= -all.patch):
> =A0 =A0 =A0> =A0 =A0+ patch -p1 -s
> =A0 =A0 =A0> =A0 =A0The text leading up to this was:
> =A0 =A0 =A0> =A0 =A0--------------------------
> =A0 =A0 =A0> =A0 =A0|console: bounds check whenever changing the cu= rsor due to an
> =A0 =A0 =A0escape code
> =A0 =A0 =A0> =A0 =A0|
> =A0 =A0 =A0> =A0 =A0|This is XSA-17 / CVE-2012-3515
> =A0 =A0 =A0> =A0 =A0|
> =A0 =A0 =A0> =A0 =A0|Signed-off-by: Ian Campbell <[1][2]ian.campbell@citrix.com>
> =A0 =A0 =A0> =A0 =A0|
> =A0 =A0 =A0> =A0 =A0|diff --git a/console.c b/console.c
> =A0 =A0 =A0> =A0 =A0|index 5e6e3d0..9984d6f 100644
> =A0 =A0 =A0> =A0 =A0|--- a/console.c
> =A0 =A0 =A0> =A0 =A0|+++ b/console.c
> =A0 =A0 =A0> =A0 =A0--------------------------
> =A0 =A0 =A0> =A0 =A0File to patch:
> =A0 =A0 =A0>
> =A0 =A0 =A0> =A0 =A0Fyi : I have added the patches xsa12-all.patch,=
> =A0 =A0 =A0> =A0 =A0xsa14-xen-3.4-and-4.x.patch and
> =A0 =A0 =A0xsa17-qemu-xen-traditional-all.patch. All
> =A0 =A0 =A0> =A0 =A0the patches goes fine expect xsa17-qemu-xen-tra= ditional-all.patch.
> =A0 =A0 =A0>
> =A0 =A0 =A0> =A0 =A0May I know how can I apply this?
> =A0 =A0 =A0>
>
> =A0 =A0 =A0With a quick look at your email it looks like wrong -p opti= on for patch?
> =A0 =A0 =A0-- Pasi
>
> References
>
> =A0 =A0Visible links
> =A0 =A01. mailto:pasik@iki.fi
> =A0 =A02. mailto:ian.campbe= ll@citrix.com

--00151747b7443dd88c04c9085e2e-- --===============7676034870965912750== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users --===============7676034870965912750==-- From xen-users-bounces@lists.xen.org Thu Sep 06 14:11:01 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Thu, 06 Sep 2012 14:11:01 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1T9cmC-0006bH-5C; Thu, 06 Sep 2012 14:09:48 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1T9cmA-0006b1-K4 for xen-users@lists.xen.org; Thu, 06 Sep 2012 14:09:46 +0000 Received: from [85.158.138.51:52264] by server-4.bemta-3.messagelabs.com id 24/00-24831-9AEA8405; Thu, 06 Sep 2012 14:09:45 +0000 X-Env-Sender: Ian.Campbell@citrix.com X-Msg-Ref: server-13.tower-174.messagelabs.com!1346940584!10386699!1 X-Originating-IP: [62.200.22.115] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogNjIuMjAwLjIyLjExNSA9PiAxMTE5NzY=\n X-StarScan-Received: X-StarScan-Version: 6.6.1.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 21306 invoked from network); 6 Sep 2012 14:09:45 -0000 Received: from smtp.eu.citrix.com (HELO SMTP.EU.CITRIX.COM) (62.200.22.115) by server-13.tower-174.messagelabs.com with RC4-SHA encrypted SMTP; 6 Sep 2012 14:09:45 -0000 X-IronPort-AV: E=Sophos;i="4.80,380,1344211200"; d="scan'208";a="14388127" Received: from lonpmailmx01.citrite.net ([10.30.203.162]) by LONPIPO01.EU.CITRIX.COM with ESMTP/TLS/RC4-MD5; 06 Sep 2012 14:09:27 +0000 Received: from [10.80.2.42] (10.80.2.42) by LONPMAILMX01.citrite.net (10.30.203.162) with Microsoft SMTP Server id 8.3.279.1; Thu, 6 Sep 2012 15:09:26 +0100 Message-ID: <1346940565.30018.24.camel@zakaz.uk.xensource.com> From: Ian Campbell To: kk s Date: Thu, 6 Sep 2012 15:09:25 +0100 In-Reply-To: References: Organization: Citrix Systems, Inc. X-Mailer: Evolution 3.4.3-1 MIME-Version: 1.0 Cc: "xen-users@lists.xen.org" , "xen-devel@lists.xen.org" Subject: Re: [Xen-users] [Xen-devel] XSA patch help X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org I've asked you already to stop cross posting (this means posting to multiple lists), and yet you continue to do so. Please stop. On Thu, 2012-09-06 at 14:57 +0100, kk s wrote: > Finally I got success to applied all the patches on my server except > "Xen Security Advisory 15 (CVE-2012-3497)" > http://lists.xen.org/archives/html/xen-announce/2012-09/msg00006.html . > I don't know if this includes any patch or its just the information. Please reread the advisory, it contains the answer to your question as well as plenty of background on the reasoning and information on what you must have done to be vulnerable to these issues in the first place. If you think the advisory is unclear then please quote the text which you don't understand. > If anyone clear this up then I am happy that my servers are secured. Ian. _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Thu Sep 06 14:11:01 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Thu, 06 Sep 2012 14:11:01 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1T9cmC-0006bH-5C; Thu, 06 Sep 2012 14:09:48 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1T9cmA-0006b1-K4 for xen-users@lists.xen.org; Thu, 06 Sep 2012 14:09:46 +0000 Received: from [85.158.138.51:52264] by server-4.bemta-3.messagelabs.com id 24/00-24831-9AEA8405; Thu, 06 Sep 2012 14:09:45 +0000 X-Env-Sender: Ian.Campbell@citrix.com X-Msg-Ref: server-13.tower-174.messagelabs.com!1346940584!10386699!1 X-Originating-IP: [62.200.22.115] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogNjIuMjAwLjIyLjExNSA9PiAxMTE5NzY=\n X-StarScan-Received: X-StarScan-Version: 6.6.1.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 21306 invoked from network); 6 Sep 2012 14:09:45 -0000 Received: from smtp.eu.citrix.com (HELO SMTP.EU.CITRIX.COM) (62.200.22.115) by server-13.tower-174.messagelabs.com with RC4-SHA encrypted SMTP; 6 Sep 2012 14:09:45 -0000 X-IronPort-AV: E=Sophos;i="4.80,380,1344211200"; d="scan'208";a="14388127" Received: from lonpmailmx01.citrite.net ([10.30.203.162]) by LONPIPO01.EU.CITRIX.COM with ESMTP/TLS/RC4-MD5; 06 Sep 2012 14:09:27 +0000 Received: from [10.80.2.42] (10.80.2.42) by LONPMAILMX01.citrite.net (10.30.203.162) with Microsoft SMTP Server id 8.3.279.1; Thu, 6 Sep 2012 15:09:26 +0100 Message-ID: <1346940565.30018.24.camel@zakaz.uk.xensource.com> From: Ian Campbell To: kk s Date: Thu, 6 Sep 2012 15:09:25 +0100 In-Reply-To: References: Organization: Citrix Systems, Inc. X-Mailer: Evolution 3.4.3-1 MIME-Version: 1.0 Cc: "xen-users@lists.xen.org" , "xen-devel@lists.xen.org" Subject: Re: [Xen-users] [Xen-devel] XSA patch help X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org I've asked you already to stop cross posting (this means posting to multiple lists), and yet you continue to do so. Please stop. On Thu, 2012-09-06 at 14:57 +0100, kk s wrote: > Finally I got success to applied all the patches on my server except > "Xen Security Advisory 15 (CVE-2012-3497)" > http://lists.xen.org/archives/html/xen-announce/2012-09/msg00006.html . > I don't know if this includes any patch or its just the information. Please reread the advisory, it contains the answer to your question as well as plenty of background on the reasoning and information on what you must have done to be vulnerable to these issues in the first place. If you think the advisory is unclear then please quote the text which you don't understand. > If anyone clear this up then I am happy that my servers are secured. Ian. _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Thu Sep 06 14:26:42 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Thu, 06 Sep 2012 14:26:42 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1T9d1T-0007bk-GR; Thu, 06 Sep 2012 14:25:35 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1T9d1R-0007be-Hk for xen-users@lists.xen.org; Thu, 06 Sep 2012 14:25:33 +0000 Received: from [85.158.143.35:39211] by server-2.bemta-4.messagelabs.com id 59/61-21239-C52B8405; Thu, 06 Sep 2012 14:25:32 +0000 X-Env-Sender: dan@soleks.com X-Msg-Ref: server-14.tower-21.messagelabs.com!1346941523!17074551!1 X-Originating-IP: [199.175.126.195] X-SpamReason: No, hits=1.3 required=7.0 tests=DATE_IN_PAST_06_12, HTML_50_60,HTML_MESSAGE,MAILTO_TO_SPAM_ADDR X-StarScan-Received: X-StarScan-Version: 6.6.1.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 31166 invoked from network); 6 Sep 2012 14:25:26 -0000 Received: from smtp.soleks.com (HELO mail-smtp00.soleks.net) (199.175.126.195) by server-14.tower-21.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 6 Sep 2012 14:25:26 -0000 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=soleks.com; s=x; h=Content-Type:In-Reply-To:References:Subject:To:MIME-Version:From:Date:Message-ID; bh=2Vmm5B2iOG2T+QGEkdVFkEUTgg5lajWLPFwHadLueig=; b=LtxGsKpbdHcvzNCoTGKKRbEUv4ezFjGEPNBjjHcKRSXjDTYg8nrTwLA27ecFaLbhGD4yd5I/oY8NUng2tZYFsV4Uk5YP0ZqTGAHYP2DLmm+kpe5wqN2Qj1Wbt9btII0y; Received: from localhost ([127.0.0.1]) by mail-smtp00.soleks.net with smtp (Exim 4.74) (envelope-from ) id 1T9e0B-0005DA-3n for xen-users@lists.xen.org; Thu, 06 Sep 2012 08:28:19 -0700 Received: from s010678cd8e7ac150.vf.shawcable.net ([174.1.142.40] helo=borei.soleks.net) by mail-smtp00.soleks.net with esmtpa (Exim 4.74) (envelope-from ) id 1T9e08-0005D5-JI for xen-users@lists.xen.org; Thu, 06 Sep 2012 08:28:16 -0700 Message-ID: <50484FDD.3040409@soleks.com> Date: Thu, 06 Sep 2012 00:25:17 -0700 From: Daniel Mezentsev User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:10.0.1) Gecko/20120208 Thunderbird/10.0.1 MIME-Version: 1.0 To: xen-users@lists.xen.org References: <20120905085653.19451hqjife56728@webmail.soleks.com> In-Reply-To: X-GMS-IP-Reputation: 0 X-GMS-DCC-Result: A X-GMS-SpamScanned: 13979cefbc74aa8d78f8c40bfc1f2348 X-DSPAM-Result: Innocent X-DSPAM-Processed: Thu Sep 6 08:28:18 2012 X-DSPAM-Confidence: 1.0000 X-DSPAM-Probability: 0.0023 X-DSPAM-Signature: 438,5048c11218351763315507 X-DSPAM-Factors: 27, for+ease+#+setup+gluster, 0.40000, for+ease+#+setup+gluster, 0.40000, one+#+#+#+support, 0.40000, one+#+#+#+support, 0.40000, will+#+#+time, 0.40000, will+#+#+time, 0.40000, go+with+gluster+use+3, 0.40000, go+with+gluster+use+3, 0.40000, was+#+saturation+appr+90, 0.40000, was+#+saturation+appr+90, 0.40000, Logical+Volumes+on+#+of, 0.40000, Logical+Volumes+on+#+of, 0.40000, use+3+#+#+you, 0.40000, use+3+#+#+you, 0.40000, lists+xen+#+#+Xen, 0.40000, lists+xen+#+#+Xen, 0.40000, i+think+#+best+solution, 0.40000, i+think+#+best+solution, 0.40000, best+#+for+#+man, 0.40000, best+#+for+#+man, 0.40000, next+one+9+x, 0.40000, next+one+9+x, 0.40000, for+#+#+local+storage, 0.40000, for+#+#+local+storage, 0.40000, XEN+#+#+So+i, 0.40000, XEN+#+#+So+i, 0.40000, 512G+I+don't+#+any, 0.40000 X-GMS-SpamScore: 0 Subject: Re: [Xen-users] guest OS High Availability with local storage X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============3872891014501495037==" Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org This is a multi-part message in MIME format. --===============3872891014501495037== Content-Type: multipart/alternative; boundary="------------050407080406060206010707" This is a multi-part message in MIME format. --------------050407080406060206010707 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Im on the latest gluster, was following recommendations about tune-up, improved results, but still have less then 50Mb/sec. Yes, current version of DRBD stops on 2 nodes, but next one 9.x will support up to 32 (need to be verified). > > True, but I have not heard it being that slow before, also if you do > go with gluster use 3.3. if you are looking for ease of setup gluster > is easy. And drdb stops at 2 nodes doesnt it. > > On Sep 5, 2012 11:08 AM, > wrote: > > From my experience gluster write performance (2 mirrored nodes) > is very low, approx 40-45Mb/sec. read is pretty high and it was > network saturation - appr 90-95Mb/sec (i have gigi network). For > HA for VMs i'd highly recommend DRDB+Pacemaker+Corosync. Solution > is much more advanced, and requires much more efforts, but output > will cover all time expenses. I have cluster of 2 nodes with DRBD, > some VM images (block devices, using Logical Volumes on top of > DRDB) are up to 512G. I don't see any performance loss. Also > Pacemaker is well integrated with XEN live migration. So i think > it's best solution for "cheap man". > > > > 2012/9/5 Andrew Wells >: > >> Actually look into gluster for turning your local storage into > shared > >> storage. Works with more than one node and replicates data. > > > > thanks for for this useful info, also to everyone who shared > their opinion > > > > > > > > -- > > Regards, > > > > Umarzuki Mochlis > > http://debmal.my > > > > _______________________________________________ > > Xen-users mailing list > > Xen-users@lists.xen.org > > http://lists.xen.org/xen-users > > > > > ---------------------------------------------------------------- > This message was sent using IMP, the Internet Messaging Program. > > _______________________________________________ > Xen-users mailing list > Xen-users@lists.xen.org > http://lists.xen.org/xen-users > > > > _______________________________________________ > Xen-users mailing list > Xen-users@lists.xen.org > http://lists.xen.org/xen-users --------------050407080406060206010707 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Im on the latest gluster, was following recommendations about tune-up, improved results, but still have less then 50Mb/sec. Yes, current version of DRBD stops on 2 nodes, but next one 9.x will support up to 32 (need to be verified).

True, but I have not heard it being that slow before, also if you do go with gluster use 3.3. if you are looking for ease of setup gluster is easy. And drdb stops at 2 nodes doesnt it.

On Sep 5, 2012 11:08 AM, <dan@soleks.com> wrote:

 From my experience gluster write performance (2 mirrored nodes) is very low, approx 40-45Mb/sec. read is pretty high and it was network saturation  - appr 90-95Mb/sec (i have gigi network). For HA for VMs i'd highly recommend DRDB+Pacemaker+Corosync. Solution is much more advanced, and requires much more efforts, but output will cover all time expenses. I have cluster of 2 nodes with DRBD, some VM images (block devices, using Logical Volumes on top of DRDB) are up to 512G. I don't see any performance loss. Also Pacemaker is well integrated with XEN live migration. So i think it's best solution for "cheap man".


> 2012/9/5 Andrew Wells <agwells0714@gmail.com>:
>> Actually look into gluster for turning your local storage into shared
>> storage. Works with more than one node and replicates data.
>
> thanks for for this useful info, also to everyone who shared their opinion
>
>
>
> --
> Regards,
>
> Umarzuki Mochlis
> http://debmal.my
>
> _______________________________________________
> Xen-users mailing list
> Xen-users@lists.xen.org
> http://lists.xen.org/xen-users
>


----------------------------------------------------------------
This message was sent using IMP, the Internet Messaging Program.

_______________________________________________
Xen-users mailing list
Xen-users@lists.xen.org
http://lists.xen.org/xen-users


_______________________________________________
Xen-users mailing list
Xen-users@lists.xen.org
http://lists.xen.org/xen-users

--------------050407080406060206010707-- --===============3872891014501495037== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users --===============3872891014501495037==-- From xen-users-bounces@lists.xen.org Thu Sep 06 14:26:42 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Thu, 06 Sep 2012 14:26:42 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1T9d1T-0007bk-GR; Thu, 06 Sep 2012 14:25:35 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1T9d1R-0007be-Hk for xen-users@lists.xen.org; Thu, 06 Sep 2012 14:25:33 +0000 Received: from [85.158.143.35:39211] by server-2.bemta-4.messagelabs.com id 59/61-21239-C52B8405; Thu, 06 Sep 2012 14:25:32 +0000 X-Env-Sender: dan@soleks.com X-Msg-Ref: server-14.tower-21.messagelabs.com!1346941523!17074551!1 X-Originating-IP: [199.175.126.195] X-SpamReason: No, hits=1.3 required=7.0 tests=DATE_IN_PAST_06_12, HTML_50_60,HTML_MESSAGE,MAILTO_TO_SPAM_ADDR X-StarScan-Received: X-StarScan-Version: 6.6.1.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 31166 invoked from network); 6 Sep 2012 14:25:26 -0000 Received: from smtp.soleks.com (HELO mail-smtp00.soleks.net) (199.175.126.195) by server-14.tower-21.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 6 Sep 2012 14:25:26 -0000 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=soleks.com; s=x; h=Content-Type:In-Reply-To:References:Subject:To:MIME-Version:From:Date:Message-ID; bh=2Vmm5B2iOG2T+QGEkdVFkEUTgg5lajWLPFwHadLueig=; b=LtxGsKpbdHcvzNCoTGKKRbEUv4ezFjGEPNBjjHcKRSXjDTYg8nrTwLA27ecFaLbhGD4yd5I/oY8NUng2tZYFsV4Uk5YP0ZqTGAHYP2DLmm+kpe5wqN2Qj1Wbt9btII0y; Received: from localhost ([127.0.0.1]) by mail-smtp00.soleks.net with smtp (Exim 4.74) (envelope-from ) id 1T9e0B-0005DA-3n for xen-users@lists.xen.org; Thu, 06 Sep 2012 08:28:19 -0700 Received: from s010678cd8e7ac150.vf.shawcable.net ([174.1.142.40] helo=borei.soleks.net) by mail-smtp00.soleks.net with esmtpa (Exim 4.74) (envelope-from ) id 1T9e08-0005D5-JI for xen-users@lists.xen.org; Thu, 06 Sep 2012 08:28:16 -0700 Message-ID: <50484FDD.3040409@soleks.com> Date: Thu, 06 Sep 2012 00:25:17 -0700 From: Daniel Mezentsev User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:10.0.1) Gecko/20120208 Thunderbird/10.0.1 MIME-Version: 1.0 To: xen-users@lists.xen.org References: <20120905085653.19451hqjife56728@webmail.soleks.com> In-Reply-To: X-GMS-IP-Reputation: 0 X-GMS-DCC-Result: A X-GMS-SpamScanned: 13979cefbc74aa8d78f8c40bfc1f2348 X-DSPAM-Result: Innocent X-DSPAM-Processed: Thu Sep 6 08:28:18 2012 X-DSPAM-Confidence: 1.0000 X-DSPAM-Probability: 0.0023 X-DSPAM-Signature: 438,5048c11218351763315507 X-DSPAM-Factors: 27, for+ease+#+setup+gluster, 0.40000, for+ease+#+setup+gluster, 0.40000, one+#+#+#+support, 0.40000, one+#+#+#+support, 0.40000, will+#+#+time, 0.40000, will+#+#+time, 0.40000, go+with+gluster+use+3, 0.40000, go+with+gluster+use+3, 0.40000, was+#+saturation+appr+90, 0.40000, was+#+saturation+appr+90, 0.40000, Logical+Volumes+on+#+of, 0.40000, Logical+Volumes+on+#+of, 0.40000, use+3+#+#+you, 0.40000, use+3+#+#+you, 0.40000, lists+xen+#+#+Xen, 0.40000, lists+xen+#+#+Xen, 0.40000, i+think+#+best+solution, 0.40000, i+think+#+best+solution, 0.40000, best+#+for+#+man, 0.40000, best+#+for+#+man, 0.40000, next+one+9+x, 0.40000, next+one+9+x, 0.40000, for+#+#+local+storage, 0.40000, for+#+#+local+storage, 0.40000, XEN+#+#+So+i, 0.40000, XEN+#+#+So+i, 0.40000, 512G+I+don't+#+any, 0.40000 X-GMS-SpamScore: 0 Subject: Re: [Xen-users] guest OS High Availability with local storage X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============3872891014501495037==" Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org This is a multi-part message in MIME format. --===============3872891014501495037== Content-Type: multipart/alternative; boundary="------------050407080406060206010707" This is a multi-part message in MIME format. --------------050407080406060206010707 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Im on the latest gluster, was following recommendations about tune-up, improved results, but still have less then 50Mb/sec. Yes, current version of DRBD stops on 2 nodes, but next one 9.x will support up to 32 (need to be verified). > > True, but I have not heard it being that slow before, also if you do > go with gluster use 3.3. if you are looking for ease of setup gluster > is easy. And drdb stops at 2 nodes doesnt it. > > On Sep 5, 2012 11:08 AM, > wrote: > > From my experience gluster write performance (2 mirrored nodes) > is very low, approx 40-45Mb/sec. read is pretty high and it was > network saturation - appr 90-95Mb/sec (i have gigi network). For > HA for VMs i'd highly recommend DRDB+Pacemaker+Corosync. Solution > is much more advanced, and requires much more efforts, but output > will cover all time expenses. I have cluster of 2 nodes with DRBD, > some VM images (block devices, using Logical Volumes on top of > DRDB) are up to 512G. I don't see any performance loss. Also > Pacemaker is well integrated with XEN live migration. So i think > it's best solution for "cheap man". > > > > 2012/9/5 Andrew Wells >: > >> Actually look into gluster for turning your local storage into > shared > >> storage. Works with more than one node and replicates data. > > > > thanks for for this useful info, also to everyone who shared > their opinion > > > > > > > > -- > > Regards, > > > > Umarzuki Mochlis > > http://debmal.my > > > > _______________________________________________ > > Xen-users mailing list > > Xen-users@lists.xen.org > > http://lists.xen.org/xen-users > > > > > ---------------------------------------------------------------- > This message was sent using IMP, the Internet Messaging Program. > > _______________________________________________ > Xen-users mailing list > Xen-users@lists.xen.org > http://lists.xen.org/xen-users > > > > _______________________________________________ > Xen-users mailing list > Xen-users@lists.xen.org > http://lists.xen.org/xen-users --------------050407080406060206010707 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Im on the latest gluster, was following recommendations about tune-up, improved results, but still have less then 50Mb/sec. Yes, current version of DRBD stops on 2 nodes, but next one 9.x will support up to 32 (need to be verified).

True, but I have not heard it being that slow before, also if you do go with gluster use 3.3. if you are looking for ease of setup gluster is easy. And drdb stops at 2 nodes doesnt it.

On Sep 5, 2012 11:08 AM, <dan@soleks.com> wrote:

 From my experience gluster write performance (2 mirrored nodes) is very low, approx 40-45Mb/sec. read is pretty high and it was network saturation  - appr 90-95Mb/sec (i have gigi network). For HA for VMs i'd highly recommend DRDB+Pacemaker+Corosync. Solution is much more advanced, and requires much more efforts, but output will cover all time expenses. I have cluster of 2 nodes with DRBD, some VM images (block devices, using Logical Volumes on top of DRDB) are up to 512G. I don't see any performance loss. Also Pacemaker is well integrated with XEN live migration. So i think it's best solution for "cheap man".


> 2012/9/5 Andrew Wells <agwells0714@gmail.com>:
>> Actually look into gluster for turning your local storage into shared
>> storage. Works with more than one node and replicates data.
>
> thanks for for this useful info, also to everyone who shared their opinion
>
>
>
> --
> Regards,
>
> Umarzuki Mochlis
> http://debmal.my
>
> _______________________________________________
> Xen-users mailing list
> Xen-users@lists.xen.org
> http://lists.xen.org/xen-users
>


----------------------------------------------------------------
This message was sent using IMP, the Internet Messaging Program.

_______________________________________________
Xen-users mailing list
Xen-users@lists.xen.org
http://lists.xen.org/xen-users


_______________________________________________
Xen-users mailing list
Xen-users@lists.xen.org
http://lists.xen.org/xen-users

--------------050407080406060206010707-- --===============3872891014501495037== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users --===============3872891014501495037==-- From xen-users-bounces@lists.xen.org Thu Sep 06 15:08:17 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Thu, 06 Sep 2012 15:08:17 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1T9dfW-0001SD-Ex; Thu, 06 Sep 2012 15:06:58 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1T9dfV-0001S6-AW for xen-users@lists.xensource.com; Thu, 06 Sep 2012 15:06:57 +0000 Received: from [85.158.138.51:54428] by server-12.bemta-3.messagelabs.com id 36/17-10384-01CB8405; Thu, 06 Sep 2012 15:06:56 +0000 X-Env-Sender: pasik@iki.fi X-Msg-Ref: server-9.tower-174.messagelabs.com!1346944015!27399097!1 X-Originating-IP: [192.89.123.25] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogMTkyLjg5LjEyMy4yNSA9PiA1MDQ1MDg=\n X-StarScan-Received: X-StarScan-Version: 6.6.1.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 6884 invoked from network); 6 Sep 2012 15:06:56 -0000 Received: from smtp.tele.fi (HELO smtp.tele.fi) (192.89.123.25) by server-9.tower-174.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 6 Sep 2012 15:06:56 -0000 X-Originating-Ip: [194.89.68.22] Received: from ydin.reaktio.net (reaktio.net [194.89.68.22]) by smtp.tele.fi (Postfix) with ESMTP id 09EE52A8D; Thu, 6 Sep 2012 18:06:53 +0300 (EEST) Received: by ydin.reaktio.net (Postfix, from userid 1001) id 37B4D2005D; Thu, 6 Sep 2012 18:06:53 +0300 (EEST) Date: Thu, 6 Sep 2012 18:06:53 +0300 From: Pasi =?iso-8859-1?Q?K=E4rkk=E4inen?= To: "Michael A. Collins" Message-ID: <20120906150653.GZ8912@reaktio.net> References: <6035A0D088A63A46850C3988ED045A4B289D3F42@BITCOM1.int.sbss.com.au> <013501cd870d$10617740$312465c0$@ark-net.org> MIME-Version: 1.0 Content-Disposition: inline In-Reply-To: <013501cd870d$10617740$312465c0$@ark-net.org> User-Agent: Mutt/1.5.20 (2009-06-14) Cc: 'James Harper' , xen-users@lists.xensource.com Subject: Re: [Xen-users] emulated rtl8139 driver, openvswitch, and offload X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org On Thu, Aug 30, 2012 at 08:10:39PM -0400, Michael A. Collins wrote: > James, > I have not been able to reliably disable Large Send Offload, Checksum > Offload and Scatter/Gather through the device manager GUI on Windows 2008 > 32bit/64bit with pv_drivers installed. The Xen Net Device Driver will fail > to start and them the dom0 will panic and reboot. I am very scared to > continue! This happened to me twice today while I was going through and > disabling GSO/TSO/GRO on my broadcom bnx2 interfaces to fix a serious issue > we have with inter-Host network traffic. Is there a way to do this that > doesn't involve crashing the dom0 and causing the whole box to reboot? > Also, is there a guide to updating the drivers? I would like to install the > latest 357 drivers, but the one time I tried uninstalling them I had a BSOD > and had to reimage. > What dom0 kernel version are you using? Also what Xen version? dom0 crashing when changing settings in the domU is a very serious bug! -- Pasi > > Mike > > > -----Original Message----- > > From: xen-users-bounces@lists.xen.org [mailto:xen-users- > > bounces@lists.xen.org] On Behalf Of James Harper > > Sent: Saturday, June 23, 2012 5:49 AM > > To: xen-users@lists.xensource.com > > Subject: [Xen-users] emulated rtl8139 driver, openvswitch, and offload > > > > I'm getting strange network problems when deploying WDS images, > > specifically: > > > > DHCP doesn't seem to renew properly > > > > Tcpdump shows a 5K packet transmitted to the DomU, then retransmitted as > > 3 x 1500 byte packets, so presumably large packets are being passed to > > DomU and the emulated adapter can't handle them and just drops them. > > > > This happens even when all the offload on the ovs bridge is off, so I > don't > > know what is happening. > > > > Any suggestions? > > > > James > > > > _______________________________________________ > > Xen-users mailing list > > Xen-users@lists.xen.org > > http://lists.xen.org/xen-users > > > > _______________________________________________ > Xen-users mailing list > Xen-users@lists.xen.org > http://lists.xen.org/xen-users _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Thu Sep 06 15:08:17 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Thu, 06 Sep 2012 15:08:17 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1T9dfW-0001SD-Ex; Thu, 06 Sep 2012 15:06:58 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1T9dfV-0001S6-AW for xen-users@lists.xensource.com; Thu, 06 Sep 2012 15:06:57 +0000 Received: from [85.158.138.51:54428] by server-12.bemta-3.messagelabs.com id 36/17-10384-01CB8405; Thu, 06 Sep 2012 15:06:56 +0000 X-Env-Sender: pasik@iki.fi X-Msg-Ref: server-9.tower-174.messagelabs.com!1346944015!27399097!1 X-Originating-IP: [192.89.123.25] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogMTkyLjg5LjEyMy4yNSA9PiA1MDQ1MDg=\n X-StarScan-Received: X-StarScan-Version: 6.6.1.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 6884 invoked from network); 6 Sep 2012 15:06:56 -0000 Received: from smtp.tele.fi (HELO smtp.tele.fi) (192.89.123.25) by server-9.tower-174.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 6 Sep 2012 15:06:56 -0000 X-Originating-Ip: [194.89.68.22] Received: from ydin.reaktio.net (reaktio.net [194.89.68.22]) by smtp.tele.fi (Postfix) with ESMTP id 09EE52A8D; Thu, 6 Sep 2012 18:06:53 +0300 (EEST) Received: by ydin.reaktio.net (Postfix, from userid 1001) id 37B4D2005D; Thu, 6 Sep 2012 18:06:53 +0300 (EEST) Date: Thu, 6 Sep 2012 18:06:53 +0300 From: Pasi =?iso-8859-1?Q?K=E4rkk=E4inen?= To: "Michael A. Collins" Message-ID: <20120906150653.GZ8912@reaktio.net> References: <6035A0D088A63A46850C3988ED045A4B289D3F42@BITCOM1.int.sbss.com.au> <013501cd870d$10617740$312465c0$@ark-net.org> MIME-Version: 1.0 Content-Disposition: inline In-Reply-To: <013501cd870d$10617740$312465c0$@ark-net.org> User-Agent: Mutt/1.5.20 (2009-06-14) Cc: 'James Harper' , xen-users@lists.xensource.com Subject: Re: [Xen-users] emulated rtl8139 driver, openvswitch, and offload X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org On Thu, Aug 30, 2012 at 08:10:39PM -0400, Michael A. Collins wrote: > James, > I have not been able to reliably disable Large Send Offload, Checksum > Offload and Scatter/Gather through the device manager GUI on Windows 2008 > 32bit/64bit with pv_drivers installed. The Xen Net Device Driver will fail > to start and them the dom0 will panic and reboot. I am very scared to > continue! This happened to me twice today while I was going through and > disabling GSO/TSO/GRO on my broadcom bnx2 interfaces to fix a serious issue > we have with inter-Host network traffic. Is there a way to do this that > doesn't involve crashing the dom0 and causing the whole box to reboot? > Also, is there a guide to updating the drivers? I would like to install the > latest 357 drivers, but the one time I tried uninstalling them I had a BSOD > and had to reimage. > What dom0 kernel version are you using? Also what Xen version? dom0 crashing when changing settings in the domU is a very serious bug! -- Pasi > > Mike > > > -----Original Message----- > > From: xen-users-bounces@lists.xen.org [mailto:xen-users- > > bounces@lists.xen.org] On Behalf Of James Harper > > Sent: Saturday, June 23, 2012 5:49 AM > > To: xen-users@lists.xensource.com > > Subject: [Xen-users] emulated rtl8139 driver, openvswitch, and offload > > > > I'm getting strange network problems when deploying WDS images, > > specifically: > > > > DHCP doesn't seem to renew properly > > > > Tcpdump shows a 5K packet transmitted to the DomU, then retransmitted as > > 3 x 1500 byte packets, so presumably large packets are being passed to > > DomU and the emulated adapter can't handle them and just drops them. > > > > This happens even when all the offload on the ovs bridge is off, so I > don't > > know what is happening. > > > > Any suggestions? > > > > James > > > > _______________________________________________ > > Xen-users mailing list > > Xen-users@lists.xen.org > > http://lists.xen.org/xen-users > > > > _______________________________________________ > Xen-users mailing list > Xen-users@lists.xen.org > http://lists.xen.org/xen-users _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Thu Sep 06 15:09:49 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Thu, 06 Sep 2012 15:09:49 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1T9dhF-0001bM-7L; Thu, 06 Sep 2012 15:08:45 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1T9dhD-0001bD-F3 for xen-users@lists.xen.org; Thu, 06 Sep 2012 15:08:43 +0000 Received: from [85.158.143.35:25650] by server-1.bemta-4.messagelabs.com id 61/C4-12504-A7CB8405; Thu, 06 Sep 2012 15:08:42 +0000 X-Env-Sender: pasik@iki.fi X-Msg-Ref: server-9.tower-21.messagelabs.com!1346944121!5973666!1 X-Originating-IP: [192.89.123.25] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogMTkyLjg5LjEyMy4yNSA9PiA1MDQ1MDg=\n X-StarScan-Received: X-StarScan-Version: 6.6.1.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 27800 invoked from network); 6 Sep 2012 15:08:42 -0000 Received: from smtp.tele.fi (HELO smtp.tele.fi) (192.89.123.25) by server-9.tower-21.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 6 Sep 2012 15:08:42 -0000 X-Originating-Ip: [194.89.68.22] Received: from ydin.reaktio.net (reaktio.net [194.89.68.22]) by smtp.tele.fi (Postfix) with ESMTP id 4CDA92ADD; Thu, 6 Sep 2012 18:08:40 +0300 (EEST) Received: by ydin.reaktio.net (Postfix, from userid 1001) id 339CE2005D; Thu, 6 Sep 2012 18:08:40 +0300 (EEST) Date: Thu, 6 Sep 2012 18:08:40 +0300 From: Pasi =?iso-8859-1?Q?K=E4rkk=E4inen?= To: Tobias Geiger Message-ID: <20120906150840.GA8912@reaktio.net> References: <119401aed3127cc6684bf6a78eaeaa4c@vido.info> <20120828182321.GP19851@reaktio.net> <395cb8324418afd2506d0fce5e7df422@vido.info> MIME-Version: 1.0 Content-Disposition: inline In-Reply-To: <395cb8324418afd2506d0fce5e7df422@vido.info> User-Agent: Mutt/1.5.20 (2009-06-14) Cc: xen-users@lists.xen.org, Casey DeLorme Subject: Re: [Xen-users] Passthrough USB Controllers X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org On Wed, Aug 29, 2012 at 11:44:56AM +0200, Tobias Geiger wrote: > Am 29.08.2012 00:45, schrieb Casey DeLorme: > >Yes I am using 3.4.9 now and passthrough is working as expected. > > > >On Tue, Aug 28, 2012 at 2:23 PM, Pasi K=E4rkk=E4inen > >wrote: > > > >>On Thu, Aug 23, 2012 at 11:27:57AM -0400, Casey DeLorme wrote: > >>> Hi Tobias, > >>> Yeah I spent last night compiling and testing, 3.5 and > >>3.5.2 both > >>have the > >>> same bug with USB Controllers, odd since video works fine. > >>> I did not encounter a crash when shutting down the virtual > >>machine, I > >>had > >>> two instances of Win7, one with PVHVM drivers, one without, > >>both > >>acted the > >>> same with the passed devices. > >>> However, I did not try running shutdown or destroy from xl. > >>> Thanks for verifying it wasn't just me. > >> > >>So using Linux 3.4.x as dom0 kernel works OK ? > >> > >>-- Pasi > >> > = > Hi, > = > yes i can confirm that - here does 3.4.0 the job... > = > Strange that its only me who gets the > dom0-crash-when-domu-shuttdown, but maybe these are 2 very different > things then... > = Yes, they are separate bugs. The dom0-crash-when-domu-shutdown bug is being discussed on xen-devel atm. -- Pasi > >>> ~Casey > >>> On Thu, Aug 23, 2012 at 8:22 AM, Tobias Geiger > >>> <[1]tobias.geiger@vido.info> wrote: > >>> > >>> typo... what i meant was: > >>> > >>> "do you also encounter the dom0 crash when shutting down > >>domU ?" > >>> > >>> Greetings > >>> Tobias > >>> > >>> Am 23.08.2012 13:39, schrieb Tobias Geiger: > >>> > >>> Hi Casey, > >>> > >>> encountered the same problem with 3.5 as Dom0 kernel, > >>see here > >>> [2] > >>http://lists.xen.org/archives/html/xen-devel/2012-08/msg00562.html > >>> > >>> Konrad could - partially - reproduce this and i guess > >>it will be > >>> fixed in 3.6 (guess!) > >>> > >>> do you also encounter the dom0 crash when shutting down > >>dom0? > >>> > >>> Greetings > >>> Tobias > >>> > >>> Am 23.08.2012 02:39, schrieb Casey DeLorme: > >>> > >>> Good Evening, > >>> > >>> I am testing our Xen 4.2 RC3 on Wheezy with the > >>latest Kernel > >>3.5.2, > >>> and > >>> encountered a bug. > >>> > >>> I am certain it is stemming from the latest kernel, > >>since the > >>bug is > >>> not > >>> present when using kernels 3.3.8 and 3.4.9. > >>> > >>> I am running a Windows 7 HVM and passing USB 2.0 and > >>USB 3.0 > >>> controllers, > >>> as well as my graphics card. > >>> > >>> The graphics card works, and to my surprise the USB > >>controllers > >>are > >>> the > >>> problem. > >>> > >>> Windows just gives me a Code 10 for all three, I > >>tried each PCI > >>> device solo > >>> with no changes, so it wasn't a conflict, and the > >>qemu log > >>appears > >>> no > >>> different than with the other kernels. > >>> > >>> Any ideas what logs I should check? Also, is anyone > >>aware of > >>any > >>> changes > >>> to the 3.5.2 kernel that could cause problems with USB > >>controllers? > >>> > >>> Thanks, > >>> > >>> ~Casey > >>> > >>> _______________________________________________ > >>> Xen-users mailing list > >>> [3]Xen-users@lists.xen.org > >>> [4]http://lists.xen.org/xen-users > >>> > >>> _______________________________________________ > >>> Xen-users mailing list > >>> [5]Xen-users@lists.xen.org > >>> [6]http://lists.xen.org/xen-users > >>> > >>> References > >>> > >>> Visible links > >>> 1. mailto:tobias.geiger@vido.info > >>> 2. > >>http://lists.xen.org/archives/html/xen-devel/2012-08/msg00562.html > >>> 3. mailto:Xen-users@lists.xen.org > >>> 4. http://lists.xen.org/xen-users > >>> 5. mailto:Xen-users@lists.xen.org > >>> 6. http://lists.xen.org/xen-users > >> > >>> _______________________________________________ > >>> Xen-users mailing list > >>> Xen-users@lists.xen.org > >>> http://lists.xen.org/xen-users > >> > >> > = > = > _______________________________________________ > Xen-users mailing list > Xen-users@lists.xen.org > http://lists.xen.org/xen-users _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Thu Sep 06 15:09:49 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Thu, 06 Sep 2012 15:09:49 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1T9dhF-0001bM-7L; Thu, 06 Sep 2012 15:08:45 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1T9dhD-0001bD-F3 for xen-users@lists.xen.org; Thu, 06 Sep 2012 15:08:43 +0000 Received: from [85.158.143.35:25650] by server-1.bemta-4.messagelabs.com id 61/C4-12504-A7CB8405; Thu, 06 Sep 2012 15:08:42 +0000 X-Env-Sender: pasik@iki.fi X-Msg-Ref: server-9.tower-21.messagelabs.com!1346944121!5973666!1 X-Originating-IP: [192.89.123.25] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogMTkyLjg5LjEyMy4yNSA9PiA1MDQ1MDg=\n X-StarScan-Received: X-StarScan-Version: 6.6.1.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 27800 invoked from network); 6 Sep 2012 15:08:42 -0000 Received: from smtp.tele.fi (HELO smtp.tele.fi) (192.89.123.25) by server-9.tower-21.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 6 Sep 2012 15:08:42 -0000 X-Originating-Ip: [194.89.68.22] Received: from ydin.reaktio.net (reaktio.net [194.89.68.22]) by smtp.tele.fi (Postfix) with ESMTP id 4CDA92ADD; Thu, 6 Sep 2012 18:08:40 +0300 (EEST) Received: by ydin.reaktio.net (Postfix, from userid 1001) id 339CE2005D; Thu, 6 Sep 2012 18:08:40 +0300 (EEST) Date: Thu, 6 Sep 2012 18:08:40 +0300 From: Pasi =?iso-8859-1?Q?K=E4rkk=E4inen?= To: Tobias Geiger Message-ID: <20120906150840.GA8912@reaktio.net> References: <119401aed3127cc6684bf6a78eaeaa4c@vido.info> <20120828182321.GP19851@reaktio.net> <395cb8324418afd2506d0fce5e7df422@vido.info> MIME-Version: 1.0 Content-Disposition: inline In-Reply-To: <395cb8324418afd2506d0fce5e7df422@vido.info> User-Agent: Mutt/1.5.20 (2009-06-14) Cc: xen-users@lists.xen.org, Casey DeLorme Subject: Re: [Xen-users] Passthrough USB Controllers X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org On Wed, Aug 29, 2012 at 11:44:56AM +0200, Tobias Geiger wrote: > Am 29.08.2012 00:45, schrieb Casey DeLorme: > >Yes I am using 3.4.9 now and passthrough is working as expected. > > > >On Tue, Aug 28, 2012 at 2:23 PM, Pasi K=E4rkk=E4inen > >wrote: > > > >>On Thu, Aug 23, 2012 at 11:27:57AM -0400, Casey DeLorme wrote: > >>> Hi Tobias, > >>> Yeah I spent last night compiling and testing, 3.5 and > >>3.5.2 both > >>have the > >>> same bug with USB Controllers, odd since video works fine. > >>> I did not encounter a crash when shutting down the virtual > >>machine, I > >>had > >>> two instances of Win7, one with PVHVM drivers, one without, > >>both > >>acted the > >>> same with the passed devices. > >>> However, I did not try running shutdown or destroy from xl. > >>> Thanks for verifying it wasn't just me. > >> > >>So using Linux 3.4.x as dom0 kernel works OK ? > >> > >>-- Pasi > >> > = > Hi, > = > yes i can confirm that - here does 3.4.0 the job... > = > Strange that its only me who gets the > dom0-crash-when-domu-shuttdown, but maybe these are 2 very different > things then... > = Yes, they are separate bugs. The dom0-crash-when-domu-shutdown bug is being discussed on xen-devel atm. -- Pasi > >>> ~Casey > >>> On Thu, Aug 23, 2012 at 8:22 AM, Tobias Geiger > >>> <[1]tobias.geiger@vido.info> wrote: > >>> > >>> typo... what i meant was: > >>> > >>> "do you also encounter the dom0 crash when shutting down > >>domU ?" > >>> > >>> Greetings > >>> Tobias > >>> > >>> Am 23.08.2012 13:39, schrieb Tobias Geiger: > >>> > >>> Hi Casey, > >>> > >>> encountered the same problem with 3.5 as Dom0 kernel, > >>see here > >>> [2] > >>http://lists.xen.org/archives/html/xen-devel/2012-08/msg00562.html > >>> > >>> Konrad could - partially - reproduce this and i guess > >>it will be > >>> fixed in 3.6 (guess!) > >>> > >>> do you also encounter the dom0 crash when shutting down > >>dom0? > >>> > >>> Greetings > >>> Tobias > >>> > >>> Am 23.08.2012 02:39, schrieb Casey DeLorme: > >>> > >>> Good Evening, > >>> > >>> I am testing our Xen 4.2 RC3 on Wheezy with the > >>latest Kernel > >>3.5.2, > >>> and > >>> encountered a bug. > >>> > >>> I am certain it is stemming from the latest kernel, > >>since the > >>bug is > >>> not > >>> present when using kernels 3.3.8 and 3.4.9. > >>> > >>> I am running a Windows 7 HVM and passing USB 2.0 and > >>USB 3.0 > >>> controllers, > >>> as well as my graphics card. > >>> > >>> The graphics card works, and to my surprise the USB > >>controllers > >>are > >>> the > >>> problem. > >>> > >>> Windows just gives me a Code 10 for all three, I > >>tried each PCI > >>> device solo > >>> with no changes, so it wasn't a conflict, and the > >>qemu log > >>appears > >>> no > >>> different than with the other kernels. > >>> > >>> Any ideas what logs I should check? Also, is anyone > >>aware of > >>any > >>> changes > >>> to the 3.5.2 kernel that could cause problems with USB > >>controllers? > >>> > >>> Thanks, > >>> > >>> ~Casey > >>> > >>> _______________________________________________ > >>> Xen-users mailing list > >>> [3]Xen-users@lists.xen.org > >>> [4]http://lists.xen.org/xen-users > >>> > >>> _______________________________________________ > >>> Xen-users mailing list > >>> [5]Xen-users@lists.xen.org > >>> [6]http://lists.xen.org/xen-users > >>> > >>> References > >>> > >>> Visible links > >>> 1. mailto:tobias.geiger@vido.info > >>> 2. > >>http://lists.xen.org/archives/html/xen-devel/2012-08/msg00562.html > >>> 3. mailto:Xen-users@lists.xen.org > >>> 4. http://lists.xen.org/xen-users > >>> 5. mailto:Xen-users@lists.xen.org > >>> 6. http://lists.xen.org/xen-users > >> > >>> _______________________________________________ > >>> Xen-users mailing list > >>> Xen-users@lists.xen.org > >>> http://lists.xen.org/xen-users > >> > >> > = > = > _______________________________________________ > Xen-users mailing list > Xen-users@lists.xen.org > http://lists.xen.org/xen-users _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Thu Sep 06 15:13:08 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Thu, 06 Sep 2012 15:13:08 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1T9dkR-00021B-NW; Thu, 06 Sep 2012 15:12:03 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1T9dkQ-00020p-1c for xen-users@lists.xen.org; Thu, 06 Sep 2012 15:12:02 +0000 Received: from [85.158.138.51:43016] by server-8.bemta-3.messagelabs.com id 1B/E6-24700-F3DB8405; Thu, 06 Sep 2012 15:11:59 +0000 X-Env-Sender: pasik@iki.fi X-Msg-Ref: server-9.tower-174.messagelabs.com!1346944318!27400331!1 X-Originating-IP: [192.89.123.25] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogMTkyLjg5LjEyMy4yNSA9PiA1MDQ1MDg=\n X-StarScan-Received: X-StarScan-Version: 6.6.1.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 7953 invoked from network); 6 Sep 2012 15:11:58 -0000 Received: from smtp.tele.fi (HELO smtp.tele.fi) (192.89.123.25) by server-9.tower-174.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 6 Sep 2012 15:11:58 -0000 X-Originating-Ip: [194.89.68.22] Received: from ydin.reaktio.net (reaktio.net [194.89.68.22]) by smtp.tele.fi (Postfix) with ESMTP id 06AF611C3; Thu, 6 Sep 2012 18:11:58 +0300 (EEST) Received: by ydin.reaktio.net (Postfix, from userid 1001) id E35CD2005D; Thu, 6 Sep 2012 18:11:57 +0300 (EEST) Date: Thu, 6 Sep 2012 18:11:57 +0300 From: Pasi =?iso-8859-1?Q?K=E4rkk=E4inen?= To: Brian Johnson Message-ID: <20120906151157.GB8912@reaktio.net> References: MIME-Version: 1.0 Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.20 (2009-06-14) Cc: xen-users@lists.xen.org, Konrad Rzeszutek Wilk Subject: Re: [Xen-users] Nvidia: card fails to work in EITHER dom0 or domU -- any advice? X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org On Thu, Aug 30, 2012 at 03:37:23PM -0700, Brian Johnson wrote: > Hi all, > I have a Nvidia GeForce GTX 680 that I'd like to use in a Xen > configuration. I don't care if it's used by dom0 or by a linux domU > guest, either would be OK for my purposes. Since getting this card, I've > experimented with Linux 3.4.6 and Xen 4.1.2 and determined the following: > 1. The card works correctly under a linux kernel without Xen running. > 2. The Nvidia proprietary drivers do not function in a dom0 setting, > because PAT is disabled in the dom0 kernel. The driver detects this and > refuses to run. > Hmmm.. maybe Konrad (cc) can tell more about the PAT stuff. > 3. Using PCI passthrough to a domU linux VM does not work either -- the > Nvidia proprietary driver does not recognize the card in the guest. Not > sure why, but I suspect some resource the card uses is not being passed > through correctly. (I can pass an AMD card to a domU without problems.) > I know that the Nvidia proprietary driver doesn't officially support Xen, > so getting it to work in dom0 might be futile, even if the PAT issue is > resolved. So my main hope is to get passthrough to a guest working > correctly. Any suggestions? Is Xen 4.2 more likely to work for my use > case? > You probably need the Nvidia vga passthru patches for Xen. Those patches are not yet merged to Xen, so they're out-of-tree. > (The nouveau driver is not an option for me because I require OpenGL 3.2+ > features, and last I checked, it doesn't support the GTX 680 anyway.) > Brian -- Pasi _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Thu Sep 06 15:13:08 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Thu, 06 Sep 2012 15:13:08 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1T9dkR-00021B-NW; Thu, 06 Sep 2012 15:12:03 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1T9dkQ-00020p-1c for xen-users@lists.xen.org; Thu, 06 Sep 2012 15:12:02 +0000 Received: from [85.158.138.51:43016] by server-8.bemta-3.messagelabs.com id 1B/E6-24700-F3DB8405; Thu, 06 Sep 2012 15:11:59 +0000 X-Env-Sender: pasik@iki.fi X-Msg-Ref: server-9.tower-174.messagelabs.com!1346944318!27400331!1 X-Originating-IP: [192.89.123.25] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogMTkyLjg5LjEyMy4yNSA9PiA1MDQ1MDg=\n X-StarScan-Received: X-StarScan-Version: 6.6.1.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 7953 invoked from network); 6 Sep 2012 15:11:58 -0000 Received: from smtp.tele.fi (HELO smtp.tele.fi) (192.89.123.25) by server-9.tower-174.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 6 Sep 2012 15:11:58 -0000 X-Originating-Ip: [194.89.68.22] Received: from ydin.reaktio.net (reaktio.net [194.89.68.22]) by smtp.tele.fi (Postfix) with ESMTP id 06AF611C3; Thu, 6 Sep 2012 18:11:58 +0300 (EEST) Received: by ydin.reaktio.net (Postfix, from userid 1001) id E35CD2005D; Thu, 6 Sep 2012 18:11:57 +0300 (EEST) Date: Thu, 6 Sep 2012 18:11:57 +0300 From: Pasi =?iso-8859-1?Q?K=E4rkk=E4inen?= To: Brian Johnson Message-ID: <20120906151157.GB8912@reaktio.net> References: MIME-Version: 1.0 Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.20 (2009-06-14) Cc: xen-users@lists.xen.org, Konrad Rzeszutek Wilk Subject: Re: [Xen-users] Nvidia: card fails to work in EITHER dom0 or domU -- any advice? X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org On Thu, Aug 30, 2012 at 03:37:23PM -0700, Brian Johnson wrote: > Hi all, > I have a Nvidia GeForce GTX 680 that I'd like to use in a Xen > configuration. I don't care if it's used by dom0 or by a linux domU > guest, either would be OK for my purposes. Since getting this card, I've > experimented with Linux 3.4.6 and Xen 4.1.2 and determined the following: > 1. The card works correctly under a linux kernel without Xen running. > 2. The Nvidia proprietary drivers do not function in a dom0 setting, > because PAT is disabled in the dom0 kernel. The driver detects this and > refuses to run. > Hmmm.. maybe Konrad (cc) can tell more about the PAT stuff. > 3. Using PCI passthrough to a domU linux VM does not work either -- the > Nvidia proprietary driver does not recognize the card in the guest. Not > sure why, but I suspect some resource the card uses is not being passed > through correctly. (I can pass an AMD card to a domU without problems.) > I know that the Nvidia proprietary driver doesn't officially support Xen, > so getting it to work in dom0 might be futile, even if the PAT issue is > resolved. So my main hope is to get passthrough to a guest working > correctly. Any suggestions? Is Xen 4.2 more likely to work for my use > case? > You probably need the Nvidia vga passthru patches for Xen. Those patches are not yet merged to Xen, so they're out-of-tree. > (The nouveau driver is not an option for me because I require OpenGL 3.2+ > features, and last I checked, it doesn't support the GTX 680 anyway.) > Brian -- Pasi _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Thu Sep 06 15:13:17 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Thu, 06 Sep 2012 15:13:17 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1T9dks-00024K-Cz; Thu, 06 Sep 2012 15:12:30 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1T9dkr-00023z-8S for xen-users@lists.xensource.com; Thu, 06 Sep 2012 15:12:29 +0000 Received: from [85.158.143.35:43409] by server-2.bemta-4.messagelabs.com id 17/C9-21239-C5DB8405; Thu, 06 Sep 2012 15:12:28 +0000 X-Env-Sender: pasik@iki.fi X-Msg-Ref: server-16.tower-21.messagelabs.com!1346944347!14510369!1 X-Originating-IP: [192.89.123.25] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogMTkyLjg5LjEyMy4yNSA9PiA1MDQ1MDg=\n X-StarScan-Received: X-StarScan-Version: 6.6.1.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 25282 invoked from network); 6 Sep 2012 15:12:28 -0000 Received: from smtp.tele.fi (HELO smtp.tele.fi) (192.89.123.25) by server-16.tower-21.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 6 Sep 2012 15:12:28 -0000 X-Originating-Ip: [194.89.68.22] Received: from ydin.reaktio.net (reaktio.net [194.89.68.22]) by smtp.tele.fi (Postfix) with ESMTP id 308822B69; Thu, 6 Sep 2012 18:12:24 +0300 (EEST) Received: by ydin.reaktio.net (Postfix, from userid 1001) id 762772005D; Thu, 6 Sep 2012 18:12:24 +0300 (EEST) Date: Thu, 6 Sep 2012 18:12:24 +0300 From: Pasi =?iso-8859-1?Q?K=E4rkk=E4inen?= To: Andy Howell Message-ID: <20120906151224.GC8912@reaktio.net> References: <50405CCB.7060802@gamubaru.com> MIME-Version: 1.0 Content-Disposition: inline In-Reply-To: <50405CCB.7060802@gamubaru.com> User-Agent: Mutt/1.5.20 (2009-06-14) Cc: xen-users@lists.xensource.com Subject: Re: [Xen-users] No dom0 video after startup on ubuntu 12.04 xen 4.1.2-2ubuntu2.2 X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org On Fri, Aug 31, 2012 at 01:42:19AM -0500, Andy Howell wrote: > I'm trying to get xen running on my laptop. It starts booting, > resets the video to a blank black screen, then nothing. It seems > like its still running. ctrl-alt-del reboots. > > Any ideas? > Did you try with giving dom0 Linux kernel (vmlinuz) "nomodeset" option? -- Pasi _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Thu Sep 06 15:13:17 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Thu, 06 Sep 2012 15:13:17 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1T9dks-00024K-Cz; Thu, 06 Sep 2012 15:12:30 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1T9dkr-00023z-8S for xen-users@lists.xensource.com; Thu, 06 Sep 2012 15:12:29 +0000 Received: from [85.158.143.35:43409] by server-2.bemta-4.messagelabs.com id 17/C9-21239-C5DB8405; Thu, 06 Sep 2012 15:12:28 +0000 X-Env-Sender: pasik@iki.fi X-Msg-Ref: server-16.tower-21.messagelabs.com!1346944347!14510369!1 X-Originating-IP: [192.89.123.25] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogMTkyLjg5LjEyMy4yNSA9PiA1MDQ1MDg=\n X-StarScan-Received: X-StarScan-Version: 6.6.1.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 25282 invoked from network); 6 Sep 2012 15:12:28 -0000 Received: from smtp.tele.fi (HELO smtp.tele.fi) (192.89.123.25) by server-16.tower-21.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 6 Sep 2012 15:12:28 -0000 X-Originating-Ip: [194.89.68.22] Received: from ydin.reaktio.net (reaktio.net [194.89.68.22]) by smtp.tele.fi (Postfix) with ESMTP id 308822B69; Thu, 6 Sep 2012 18:12:24 +0300 (EEST) Received: by ydin.reaktio.net (Postfix, from userid 1001) id 762772005D; Thu, 6 Sep 2012 18:12:24 +0300 (EEST) Date: Thu, 6 Sep 2012 18:12:24 +0300 From: Pasi =?iso-8859-1?Q?K=E4rkk=E4inen?= To: Andy Howell Message-ID: <20120906151224.GC8912@reaktio.net> References: <50405CCB.7060802@gamubaru.com> MIME-Version: 1.0 Content-Disposition: inline In-Reply-To: <50405CCB.7060802@gamubaru.com> User-Agent: Mutt/1.5.20 (2009-06-14) Cc: xen-users@lists.xensource.com Subject: Re: [Xen-users] No dom0 video after startup on ubuntu 12.04 xen 4.1.2-2ubuntu2.2 X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org On Fri, Aug 31, 2012 at 01:42:19AM -0500, Andy Howell wrote: > I'm trying to get xen running on my laptop. It starts booting, > resets the video to a blank black screen, then nothing. It seems > like its still running. ctrl-alt-del reboots. > > Any ideas? > Did you try with giving dom0 Linux kernel (vmlinuz) "nomodeset" option? -- Pasi _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Thu Sep 06 16:16:03 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Thu, 06 Sep 2012 16:16:03 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1T9ejJ-000510-18; Thu, 06 Sep 2012 16:14:57 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1T9ei1-0004vi-Iw for xen-users@lists.xen.org; Thu, 06 Sep 2012 16:13:37 +0000 Received: from [85.158.138.51:23579] by server-3.bemta-3.messagelabs.com id D8/7D-21322-FABC8405; Thu, 06 Sep 2012 16:13:35 +0000 X-Env-Sender: iwj@xenbits.xen.org X-Msg-Ref: server-2.tower-174.messagelabs.com!1346948013!29115213!1 X-Originating-IP: [50.57.168.107] X-SpamReason: No, hits=0.5 required=7.0 tests=BODY_RANDOM_LONG X-StarScan-Received: X-StarScan-Version: 6.6.1.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 443 invoked from network); 6 Sep 2012 16:13:34 -0000 Received: from mail.xen.org (HELO mail.xen.org) (50.57.168.107) by server-2.tower-174.messagelabs.com with AES256-SHA encrypted SMTP; 6 Sep 2012 16:13:34 -0000 Received: from xenbits.xen.org ([50.57.170.242]) by mail.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1T9ehq-0006FF-9D; Thu, 06 Sep 2012 16:13:26 +0000 Received: from iwj by xenbits.xen.org with local (Exim 4.72) (envelope-from ) id 1T9ehq-0006nu-7Q; Thu, 06 Sep 2012 16:13:26 +0000 Date: Thu, 06 Sep 2012 16:13:26 +0000 Message-Id: Content-Type: multipart/mixed; boundary="=separator"; charset="utf-8" Content-Transfer-Encoding: binary MIME-Version: 1.0 X-Mailer: MIME-tools 5.428 (Entity 5.428) To: xen-announce@lists.xen.org, xen-devel@lists.xen.org, xen-users@lists.xen.org, oss-security@lists.openwall.com From: Xen.org security team X-Mailman-Approved-At: Thu, 06 Sep 2012 16:14:55 +0000 Cc: "Xen.org security team" Subject: [Xen-users] Xen Security Advisory 19 - guest administrator can access qemu monitor console X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org --=separator Content-Type: text/plain; charset="utf-8" Content-Disposition: inline Content-Transfer-Encoding: 7bit -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Xen Security Advisory XSA-19 guest administrator can access qemu monitor console ISSUE DESCRIPTION ================= A guest administrator who is granted access to the graphical console of a Xen guest can access the qemu monitor. The monitor can be used to access host resources. IMPACT ====== A malicious guest administrator can access host resources (perhaps belonging to other guests or the underlying system) and may be able to escalate their privilege to that of the host. VULNERABLE SYSTEMS ================== Installations where guest administrators do not have access to a domain's graphical console, or containing only PV domains configured without a graphical console, are not vulnerable. Installations where all guest administrators are trustworthy are not vulnerable, even if the guest operating systems themselves are untrusted. Systems using xend/xm: At least all versions since Xen 4.0 are affected. Systems are vulnerable even if "monitor=no" is specified in the xm domain configuration file - this configuration option is not properly honoured in the vulnerable versions. Systems using libxl/xl: All versions are affected. The "monitor=" option is not understood, and is therefore ignored, by xl. However, systems using the experimental device model version based on upstream qemu are NOT vulnerable; that is, Xen 4.2 RC systems with device_model_version="qemu_xen" specified in the xl domain config file. Systems using libvirt are vulnerable. For "xen:" URIs, see xend/xm, above. For "libxl:" URIs, all versions are affected. Systems based on the Xen Cloud Platform are NOT vulnerable. CONFIRMING VULNERABILITY ======================== Connect to the guest's VNC (or SDL) graphical display and make sure your focus is in that window. Hold down CTRL and ALT and press 2. You will see a black screen showing one of "serial0", "parallel0" or "QEMU monitor". Repeat this exercise for other digits 3 to 6. CTRL+ALT+1 is the domain's normal graphical console. Not all numbers will have screens attached, but note that you must release and re-press CTRL and ALT each time. If one of the accessible screens shows "QEMU monitor" then you are vulnerable. Otherwise you are not. MITIGATION ========== With xl in Xen 4.1 and later, supplying the following config option in the VM configuration file will disable the monitor: device_model_args=["-monitor","null"] With xend the following config option will disable the monitor: monitor_path="null" Note that with a vulnerable version of the software specifying "monitor=0" will NOT disable the monitor. We are not currently aware of the availability of mitigation for systems using libvirt. NOTE REGARDING EMBARGO ====================== This issue was publicly discussed online by its discoverer. There is therefore no embargo. NOTE REGARDING CVE ================== This issue was previously reported in a different context, not to Xen upstream, and assigned CVE-2007-0998 and fixed in a different way. We have requested a new CVE for XSA-19 but it is not yet available. RESOLUTION ========== The attached patch against qemu-xen-traditional (qemu-xen-4.*-testing.git) resolves this issue. $ sha256sum xsa19-qemu-all.patch 19fc5ff9334e7e7ad429388850dc6e52e7062c21a677082e7a89c2f2c91365fa xsa19-qemu-all.patch -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.10 (GNU/Linux) iQEcBAEBAgAGBQJQSMr3AAoJEIP+FMlX6CvZ2O8H/2cZuOEMQd6ELDSmgj2fVaYl qpev3Ux50+wHsBf2JS4XMW+f6wwNWa8IBP1GL+SUvOLVr0PGYb8cbISy+zp6z+ku mAF1T19iaAMNc/feSYwgtLfYE9H25SbB4cuPg6YkyLf6dQn0KnEyf9GIJxHy0xir nU5XKEwhhJHw17cXZyagTBheXqrIRtIhgMNv3oQKg60NDc+2sMYwMmv7lgPVIvTZ 5+rkY7RX34hBCw08qt/CEyI9OXKHL1jDjPM8QtCKuwDzaWI10yQxtLjWJCYEhGkH QqMHU6D8Q3DptCSZj/9urs7+oWGwb3TKR7rUc5v7NbiHlliEX5njDKrhxZpxvJg= =21pO -----END PGP SIGNATURE----- --=separator Content-Type: application/octet-stream; name="xsa19-qemu-all.patch" Content-Disposition: attachment; filename="xsa19-qemu-all.patch" Content-Transfer-Encoding: base64 RnJvbTogSWFuIEphY2tzb24gPGlhbi5qYWNrc29uQGV1LmNpdHJpeC5jb20+ CgpEaXNhYmxlIHFlbXUgbW9uaXRvciBieSBkZWZhdWx0LiAgVGhlIHFlbXUg bW9uaXRvciBpcyBhbiBvdmVybHkKcG93ZXJmdWwgZmVhdHVyZSB3aGljaCBt dXN0IGJlIHByb3RlY3RlZCBmcm9tIHVudHJ1c3RlZCAoZ3Vlc3QpCmFkbWlu aXN0cmF0b3JzLgoKTmVpdGhlciB4bCBub3IgeGVuZCBleHBlY3QgcWVtdSB0 byBwcm9kdWNlIHRoaXMgbW9uaXRvciB1bmxlc3MgaXQgaXMKZXhwbGljaXRs eSByZXF1ZXN0ZWQuCgpUaGlzIGlzIGEgc2VjdXJpdHkgcHJvYmxlbSwgWFNB LTE5LiAgUHJldmlvdXNseSBpdCB3YXMgQ1ZFLTIwMDctMDk5OAppbiBSZWQg SGF0IGJ1dCB3ZSBoYXZlbid0IGRlYWx0IHdpdGggaXQgaW4gdXBzdHJlYW0u ICBXZSBob3BlIHRvIGhhdmUKYSBuZXcgQ1ZFIGZvciBpdCBoZXJlIGJ1dCB3 ZSBkb24ndCBoYXZlIG9uZSB5ZXQuCgpTaWduZWQtb2ZmLWJ5OiBJYW4gSmFj a3NvbiA8aWFuLmphY2tzb25AZXUuY2l0cml4LmNvbT4KCmRpZmYgLS1naXQg YS92bC5jIGIvdmwuYwppbmRleCBkMzBjYjJjLi5kMjFjM2FhIDEwMDY0NAot LS0gYS92bC5jCisrKyBiL3ZsLmMKQEAgLTQ5MjAsNyArNDkyMCw3IEBAIGlu dCBtYWluKGludCBhcmdjLCBjaGFyICoqYXJndiwgY2hhciAqKmVudnApCiAg ICAga2VybmVsX2NtZGxpbmUgPSAiIjsKICAgICBjeWxzID0gaGVhZHMgPSBz ZWNzID0gMDsKICAgICB0cmFuc2xhdGlvbiA9IEJJT1NfQVRBX1RSQU5TTEFU SU9OX0FVVE87Ci0gICAgbW9uaXRvcl9kZXZpY2UgPSAidmM6ODBDeDI0QyI7 CisgICAgbW9uaXRvcl9kZXZpY2UgPSAibnVsbCI7CiAKICAgICBzZXJpYWxf ZGV2aWNlc1swXSA9ICJ2Yzo4MEN4MjRDIjsKICAgICBmb3IoaSA9IDE7IGkg PCBNQVhfU0VSSUFMX1BPUlRTOyBpKyspCg== --=separator Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users --=separator-- From xen-users-bounces@lists.xen.org Thu Sep 06 16:16:03 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Thu, 06 Sep 2012 16:16:03 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1T9ejJ-000510-18; Thu, 06 Sep 2012 16:14:57 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1T9ei1-0004vi-Iw for xen-users@lists.xen.org; Thu, 06 Sep 2012 16:13:37 +0000 Received: from [85.158.138.51:23579] by server-3.bemta-3.messagelabs.com id D8/7D-21322-FABC8405; Thu, 06 Sep 2012 16:13:35 +0000 X-Env-Sender: iwj@xenbits.xen.org X-Msg-Ref: server-2.tower-174.messagelabs.com!1346948013!29115213!1 X-Originating-IP: [50.57.168.107] X-SpamReason: No, hits=0.5 required=7.0 tests=BODY_RANDOM_LONG X-StarScan-Received: X-StarScan-Version: 6.6.1.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 443 invoked from network); 6 Sep 2012 16:13:34 -0000 Received: from mail.xen.org (HELO mail.xen.org) (50.57.168.107) by server-2.tower-174.messagelabs.com with AES256-SHA encrypted SMTP; 6 Sep 2012 16:13:34 -0000 Received: from xenbits.xen.org ([50.57.170.242]) by mail.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1T9ehq-0006FF-9D; Thu, 06 Sep 2012 16:13:26 +0000 Received: from iwj by xenbits.xen.org with local (Exim 4.72) (envelope-from ) id 1T9ehq-0006nu-7Q; Thu, 06 Sep 2012 16:13:26 +0000 Date: Thu, 06 Sep 2012 16:13:26 +0000 Message-Id: Content-Type: multipart/mixed; boundary="=separator"; charset="utf-8" Content-Transfer-Encoding: binary MIME-Version: 1.0 X-Mailer: MIME-tools 5.428 (Entity 5.428) To: xen-announce@lists.xen.org, xen-devel@lists.xen.org, xen-users@lists.xen.org, oss-security@lists.openwall.com From: Xen.org security team X-Mailman-Approved-At: Thu, 06 Sep 2012 16:14:55 +0000 Cc: "Xen.org security team" Subject: [Xen-users] Xen Security Advisory 19 - guest administrator can access qemu monitor console X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org --=separator Content-Type: text/plain; charset="utf-8" Content-Disposition: inline Content-Transfer-Encoding: 7bit -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Xen Security Advisory XSA-19 guest administrator can access qemu monitor console ISSUE DESCRIPTION ================= A guest administrator who is granted access to the graphical console of a Xen guest can access the qemu monitor. The monitor can be used to access host resources. IMPACT ====== A malicious guest administrator can access host resources (perhaps belonging to other guests or the underlying system) and may be able to escalate their privilege to that of the host. VULNERABLE SYSTEMS ================== Installations where guest administrators do not have access to a domain's graphical console, or containing only PV domains configured without a graphical console, are not vulnerable. Installations where all guest administrators are trustworthy are not vulnerable, even if the guest operating systems themselves are untrusted. Systems using xend/xm: At least all versions since Xen 4.0 are affected. Systems are vulnerable even if "monitor=no" is specified in the xm domain configuration file - this configuration option is not properly honoured in the vulnerable versions. Systems using libxl/xl: All versions are affected. The "monitor=" option is not understood, and is therefore ignored, by xl. However, systems using the experimental device model version based on upstream qemu are NOT vulnerable; that is, Xen 4.2 RC systems with device_model_version="qemu_xen" specified in the xl domain config file. Systems using libvirt are vulnerable. For "xen:" URIs, see xend/xm, above. For "libxl:" URIs, all versions are affected. Systems based on the Xen Cloud Platform are NOT vulnerable. CONFIRMING VULNERABILITY ======================== Connect to the guest's VNC (or SDL) graphical display and make sure your focus is in that window. Hold down CTRL and ALT and press 2. You will see a black screen showing one of "serial0", "parallel0" or "QEMU monitor". Repeat this exercise for other digits 3 to 6. CTRL+ALT+1 is the domain's normal graphical console. Not all numbers will have screens attached, but note that you must release and re-press CTRL and ALT each time. If one of the accessible screens shows "QEMU monitor" then you are vulnerable. Otherwise you are not. MITIGATION ========== With xl in Xen 4.1 and later, supplying the following config option in the VM configuration file will disable the monitor: device_model_args=["-monitor","null"] With xend the following config option will disable the monitor: monitor_path="null" Note that with a vulnerable version of the software specifying "monitor=0" will NOT disable the monitor. We are not currently aware of the availability of mitigation for systems using libvirt. NOTE REGARDING EMBARGO ====================== This issue was publicly discussed online by its discoverer. There is therefore no embargo. NOTE REGARDING CVE ================== This issue was previously reported in a different context, not to Xen upstream, and assigned CVE-2007-0998 and fixed in a different way. We have requested a new CVE for XSA-19 but it is not yet available. RESOLUTION ========== The attached patch against qemu-xen-traditional (qemu-xen-4.*-testing.git) resolves this issue. $ sha256sum xsa19-qemu-all.patch 19fc5ff9334e7e7ad429388850dc6e52e7062c21a677082e7a89c2f2c91365fa xsa19-qemu-all.patch -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.10 (GNU/Linux) iQEcBAEBAgAGBQJQSMr3AAoJEIP+FMlX6CvZ2O8H/2cZuOEMQd6ELDSmgj2fVaYl qpev3Ux50+wHsBf2JS4XMW+f6wwNWa8IBP1GL+SUvOLVr0PGYb8cbISy+zp6z+ku mAF1T19iaAMNc/feSYwgtLfYE9H25SbB4cuPg6YkyLf6dQn0KnEyf9GIJxHy0xir nU5XKEwhhJHw17cXZyagTBheXqrIRtIhgMNv3oQKg60NDc+2sMYwMmv7lgPVIvTZ 5+rkY7RX34hBCw08qt/CEyI9OXKHL1jDjPM8QtCKuwDzaWI10yQxtLjWJCYEhGkH QqMHU6D8Q3DptCSZj/9urs7+oWGwb3TKR7rUc5v7NbiHlliEX5njDKrhxZpxvJg= =21pO -----END PGP SIGNATURE----- --=separator Content-Type: application/octet-stream; name="xsa19-qemu-all.patch" Content-Disposition: attachment; filename="xsa19-qemu-all.patch" Content-Transfer-Encoding: base64 RnJvbTogSWFuIEphY2tzb24gPGlhbi5qYWNrc29uQGV1LmNpdHJpeC5jb20+ CgpEaXNhYmxlIHFlbXUgbW9uaXRvciBieSBkZWZhdWx0LiAgVGhlIHFlbXUg bW9uaXRvciBpcyBhbiBvdmVybHkKcG93ZXJmdWwgZmVhdHVyZSB3aGljaCBt dXN0IGJlIHByb3RlY3RlZCBmcm9tIHVudHJ1c3RlZCAoZ3Vlc3QpCmFkbWlu aXN0cmF0b3JzLgoKTmVpdGhlciB4bCBub3IgeGVuZCBleHBlY3QgcWVtdSB0 byBwcm9kdWNlIHRoaXMgbW9uaXRvciB1bmxlc3MgaXQgaXMKZXhwbGljaXRs eSByZXF1ZXN0ZWQuCgpUaGlzIGlzIGEgc2VjdXJpdHkgcHJvYmxlbSwgWFNB LTE5LiAgUHJldmlvdXNseSBpdCB3YXMgQ1ZFLTIwMDctMDk5OAppbiBSZWQg SGF0IGJ1dCB3ZSBoYXZlbid0IGRlYWx0IHdpdGggaXQgaW4gdXBzdHJlYW0u ICBXZSBob3BlIHRvIGhhdmUKYSBuZXcgQ1ZFIGZvciBpdCBoZXJlIGJ1dCB3 ZSBkb24ndCBoYXZlIG9uZSB5ZXQuCgpTaWduZWQtb2ZmLWJ5OiBJYW4gSmFj a3NvbiA8aWFuLmphY2tzb25AZXUuY2l0cml4LmNvbT4KCmRpZmYgLS1naXQg YS92bC5jIGIvdmwuYwppbmRleCBkMzBjYjJjLi5kMjFjM2FhIDEwMDY0NAot LS0gYS92bC5jCisrKyBiL3ZsLmMKQEAgLTQ5MjAsNyArNDkyMCw3IEBAIGlu dCBtYWluKGludCBhcmdjLCBjaGFyICoqYXJndiwgY2hhciAqKmVudnApCiAg ICAga2VybmVsX2NtZGxpbmUgPSAiIjsKICAgICBjeWxzID0gaGVhZHMgPSBz ZWNzID0gMDsKICAgICB0cmFuc2xhdGlvbiA9IEJJT1NfQVRBX1RSQU5TTEFU SU9OX0FVVE87Ci0gICAgbW9uaXRvcl9kZXZpY2UgPSAidmM6ODBDeDI0QyI7 CisgICAgbW9uaXRvcl9kZXZpY2UgPSAibnVsbCI7CiAKICAgICBzZXJpYWxf ZGV2aWNlc1swXSA9ICJ2Yzo4MEN4MjRDIjsKICAgICBmb3IoaSA9IDE7IGkg PCBNQVhfU0VSSUFMX1BPUlRTOyBpKyspCg== --=separator Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users --=separator-- From xen-users-bounces@lists.xen.org Thu Sep 06 17:05:57 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Thu, 06 Sep 2012 17:05:57 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1T9fVt-00089M-54; Thu, 06 Sep 2012 17:05:09 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1T9dLl-0000FU-QH for xen-users@lists.xen.org; Thu, 06 Sep 2012 14:46:34 +0000 Received: from [85.158.139.83:13792] by server-12.bemta-5.messagelabs.com id 54/2A-18300-947B8405; Thu, 06 Sep 2012 14:46:33 +0000 X-Env-Sender: kks.kbase@gmail.com X-Msg-Ref: server-9.tower-182.messagelabs.com!1346942791!28303462!1 X-Originating-IP: [209.85.214.45] X-SpamReason: No, hits=0.9 required=7.0 tests=HTML_40_50,HTML_MESSAGE, ML_RADAR_SPEW_LINKS_14,RCVD_BY_IP,spamassassin: X-StarScan-Received: X-StarScan-Version: 6.6.1.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 27514 invoked from network); 6 Sep 2012 14:46:32 -0000 Received: from mail-bk0-f45.google.com (HELO mail-bk0-f45.google.com) (209.85.214.45) by server-9.tower-182.messagelabs.com with RC4-SHA encrypted SMTP; 6 Sep 2012 14:46:32 -0000 Received: by bkcji1 with SMTP id ji1so849044bkc.32 for ; Thu, 06 Sep 2012 07:46:31 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=gKBV3+WeeKVBb/ldKvMDckzAeE9ULAUvbHoA4vYUDm4=; b=V2eyL7/xkNCeznBAUu8edbADWvgb9rou2bjzBhp+1MsTZX8BrD6549K6WPk/iAPf4d Man/KwViS+Jh/8MTfN4tgp0wJAa5w40J3jpi2lpxhRznfagKsWCntNqbssTnVBkQTi+F aO9beHbJ9CDIEVl9ILxUAewnGzHo6WtE+Nh3WChqV47uRTUFLQmbtbfed88oo6xVESbw 7HmdsMlad7AVZZRQ7EbiSOHxBsAwYkI5vOJd75aBA8kGV3h+S8CZQY8UK8+5kJw3pbSN Xg8Xqm+yaaY8xprB1hToRRUIj2eVlyt3+l80cGi0IJadxn6lVP4Q5u+t9fRdgbKgdVPH eqQA== MIME-Version: 1.0 Received: by 10.204.148.86 with SMTP id o22mr1148371bkv.59.1346942791615; Thu, 06 Sep 2012 07:46:31 -0700 (PDT) Received: by 10.204.56.134 with HTTP; Thu, 6 Sep 2012 07:46:31 -0700 (PDT) In-Reply-To: References: <20120906124617.GT8912@reaktio.net> <20120906125843.GU8912@reaktio.net> Date: Thu, 6 Sep 2012 20:16:31 +0530 Message-ID: From: kk s To: =?ISO-8859-1?Q?Pasi_K=E4rkk=E4inen?= X-Mailman-Approved-At: Thu, 06 Sep 2012 17:05:06 +0000 Cc: xen-users@lists.xen.org Subject: Re: [Xen-users] [Xen-devel] Issue with making rpm with patch applied X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============8384181282722243385==" Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org --===============8384181282722243385== Content-Type: multipart/alternative; boundary=0015175cd29aa0868a04c9098e39 --0015175cd29aa0868a04c9098e39 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Hi, Everything has been done fine. I just want to make sure that I did correct for this patch issue? On Thu, Sep 6, 2012 at 6:51 PM, kk s wrote: > Hi Pasi, > > You are right. > > It looks like the path is wrong and I have changed from a/console.c to > a/tools/ioemu-qemu-xen/console.c and as well for b/ which going fine. > > May I confirm is this correct file that I am applying? > > On Thu, Sep 6, 2012 at 6:28 PM, Pasi K=E4rkk=E4inen wrote: > >> On Thu, Sep 06, 2012 at 06:23:18PM +0530, kk s wrote: >> > Hi Pasi, >> > I have tried with the -p options p1 and p0 which doesn't help :( >> > >> >> Well did you verify the file paths? Where is console.c on the xen source >> tree? >> how many directories 'deep' in the tree? >> >> The patch only mentions a/console.c, so you might need to add some more >> path elements there.. >> >> -- Pasi >> >> > On Thu, Sep 6, 2012 at 6:16 PM, Pasi K=E4rkk=E4inen <[1]pasik@iki.f= i> >> wrote: >> > >> > On Thu, Sep 06, 2012 at 02:44:39PM +0530, kk s wrote: >> > > Hi, >> > > >> > > I have downloaded src rpm from gitco and extracted into the >> > > /usr/src/redhat/SOURCES dir then downloaded the patches and >> renamed >> > it as >> > > properly like xen-3.4.4-xsa17-qemu-xen-traditional-all.patch= . >> Then >> > edited >> > > the xen-x.spec file and added the patches. After that I have >> tried >> > to make >> > > rpm using rpmbuild -bb xen-x.spec and I ended up with the >> below >> > error, >> > > >> > > Patch #13 (xen-3.4.4-xsa17-qemu-xen-traditional-all.patch): >> > > + patch -p1 -s >> > > The text leading up to this was: >> > > -------------------------- >> > > |console: bounds check whenever changing the cursor due to a= n >> > escape code >> > > | >> > > |This is XSA-17 / CVE-2012-3515 >> > > | >> > > |Signed-off-by: Ian Campbell <[1][2]ian.campbell@citrix.com> >> > > | >> > > |diff --git a/console.c b/console.c >> > > |index 5e6e3d0..9984d6f 100644 >> > > |--- a/console.c >> > > |+++ b/console.c >> > > -------------------------- >> > > File to patch: >> > > >> > > Fyi : I have added the patches xsa12-all.patch, >> > > xsa14-xen-3.4-and-4.x.patch and >> > xsa17-qemu-xen-traditional-all.patch. All >> > > the patches goes fine expect >> xsa17-qemu-xen-traditional-all.patch. >> > > >> > > May I know how can I apply this? >> > > >> > >> > With a quick look at your email it looks like wrong -p option for >> patch? >> > -- Pasi >> > >> > References >> > >> > Visible links >> > 1. mailto:pasik@iki.fi >> > 2. mailto:ian.campbell@citrix.com >> > > --0015175cd29aa0868a04c9098e39 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable
Hi,

Everything has been done fine.
<= div>
I just want to make sure that I did correct for this pat= ch issue?



On Thu, Sep 6, 2012 at 6:51 PM, kk s <kks.kbase@gmail.com>= wrote:
Hi Pasi,

You are right.

It looks like the path is wrong and I have changed from a/console.c= to a/tools/ioemu-qemu-xen/console.c and as well for b/ which going fine.

May I confirm is this correct file that I am applying?<= /div>

On Thu, Sep 6, 2012 at 6:28 PM, Pasi K=E4rkk=E4inen <= pasik@iki.fi> wrote:
On Thu, Sep 06, 2012 at 06:23:18PM +053= 0, kk s wrote:
> =A0 =A0Hi Pasi,
> =A0 =A0I have tried with the -p options p1 and p0 which doesn't he= lp :(
>

Well did you verify the file paths? Where is console.c on the xen sou= rce tree?
how many directories 'deep' in the tree?

The patch only mentions a/console.c, so you might need to add some more pat= h elements there..

-- Pasi

> =A0 =A0On Thu, Sep 6, 2012 at 6:16 PM, Pasi K=E4rkk=E4inen <[1]pasik@iki.fi> wrote: >
> =A0 =A0 =A0On Thu, Sep 06, 2012 at 02:44:39PM +0530, kk s wrote:
> =A0 =A0 =A0> =A0 =A0Hi,
> =A0 =A0 =A0>
> =A0 =A0 =A0> =A0 =A0I have downloaded src rpm from gitco and extrac= ted into the
> =A0 =A0 =A0> =A0 =A0/usr/src/redhat/SOURCES dir then downloaded the= patches and renamed
> =A0 =A0 =A0it as
> =A0 =A0 =A0> =A0 =A0properly like xen-3.4.4-xsa17-qemu-xen-traditio= nal-all.patch. Then
> =A0 =A0 =A0edited
> =A0 =A0 =A0> =A0 =A0the xen-x.spec file and added the patches. Afte= r that I have tried
> =A0 =A0 =A0to make
> =A0 =A0 =A0> =A0 =A0rpm using rpmbuild -bb xen-x.spec and I ended u= p with the below
> =A0 =A0 =A0error,
> =A0 =A0 =A0>
> =A0 =A0 =A0> =A0 =A0Patch #13 (xen-3.4.4-xsa17-qemu-xen-traditional= -all.patch):
> =A0 =A0 =A0> =A0 =A0+ patch -p1 -s
> =A0 =A0 =A0> =A0 =A0The text leading up to this was:
> =A0 =A0 =A0> =A0 =A0--------------------------
> =A0 =A0 =A0> =A0 =A0|console: bounds check whenever changing the cu= rsor due to an
> =A0 =A0 =A0escape code
> =A0 =A0 =A0> =A0 =A0|
> =A0 =A0 =A0> =A0 =A0|This is XSA-17 / CVE-2012-3515
> =A0 =A0 =A0> =A0 =A0|
> =A0 =A0 =A0> =A0 =A0|Signed-off-by: Ian Campbell <[1][2]ian.campbell@cit= rix.com>
> =A0 =A0 =A0> =A0 =A0|
> =A0 =A0 =A0> =A0 =A0|diff --git a/console.c b/console.c
> =A0 =A0 =A0> =A0 =A0|index 5e6e3d0..9984d6f 100644
> =A0 =A0 =A0> =A0 =A0|--- a/console.c
> =A0 =A0 =A0> =A0 =A0|+++ b/console.c
> =A0 =A0 =A0> =A0 =A0--------------------------
> =A0 =A0 =A0> =A0 =A0File to patch:
> =A0 =A0 =A0>
> =A0 =A0 =A0> =A0 =A0Fyi : I have added the patches xsa12-all.patch,=
> =A0 =A0 =A0> =A0 =A0xsa14-xen-3.4-and-4.x.patch and
> =A0 =A0 =A0xsa17-qemu-xen-traditional-all.patch. All
> =A0 =A0 =A0> =A0 =A0the patches goes fine expect xsa17-qemu-xen-tra= ditional-all.patch.
> =A0 =A0 =A0>
> =A0 =A0 =A0> =A0 =A0May I know how can I apply this?
> =A0 =A0 =A0>
>
> =A0 =A0 =A0With a quick look at your email it looks like wrong -p opti= on for patch?
> =A0 =A0 =A0-- Pasi
>
> References
>
> =A0 =A0Visible links
> =A0 =A01. mailto:pas= ik@iki.fi
> =A0 =A02. mailto:ian.campbell@citrix.com


--0015175cd29aa0868a04c9098e39-- --===============8384181282722243385== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users --===============8384181282722243385==-- From xen-users-bounces@lists.xen.org Thu Sep 06 17:05:57 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Thu, 06 Sep 2012 17:05:57 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1T9fVt-00089M-54; Thu, 06 Sep 2012 17:05:09 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1T9dLl-0000FU-QH for xen-users@lists.xen.org; Thu, 06 Sep 2012 14:46:34 +0000 Received: from [85.158.139.83:13792] by server-12.bemta-5.messagelabs.com id 54/2A-18300-947B8405; Thu, 06 Sep 2012 14:46:33 +0000 X-Env-Sender: kks.kbase@gmail.com X-Msg-Ref: server-9.tower-182.messagelabs.com!1346942791!28303462!1 X-Originating-IP: [209.85.214.45] X-SpamReason: No, hits=0.9 required=7.0 tests=HTML_40_50,HTML_MESSAGE, ML_RADAR_SPEW_LINKS_14,RCVD_BY_IP,spamassassin: X-StarScan-Received: X-StarScan-Version: 6.6.1.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 27514 invoked from network); 6 Sep 2012 14:46:32 -0000 Received: from mail-bk0-f45.google.com (HELO mail-bk0-f45.google.com) (209.85.214.45) by server-9.tower-182.messagelabs.com with RC4-SHA encrypted SMTP; 6 Sep 2012 14:46:32 -0000 Received: by bkcji1 with SMTP id ji1so849044bkc.32 for ; Thu, 06 Sep 2012 07:46:31 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=gKBV3+WeeKVBb/ldKvMDckzAeE9ULAUvbHoA4vYUDm4=; b=V2eyL7/xkNCeznBAUu8edbADWvgb9rou2bjzBhp+1MsTZX8BrD6549K6WPk/iAPf4d Man/KwViS+Jh/8MTfN4tgp0wJAa5w40J3jpi2lpxhRznfagKsWCntNqbssTnVBkQTi+F aO9beHbJ9CDIEVl9ILxUAewnGzHo6WtE+Nh3WChqV47uRTUFLQmbtbfed88oo6xVESbw 7HmdsMlad7AVZZRQ7EbiSOHxBsAwYkI5vOJd75aBA8kGV3h+S8CZQY8UK8+5kJw3pbSN Xg8Xqm+yaaY8xprB1hToRRUIj2eVlyt3+l80cGi0IJadxn6lVP4Q5u+t9fRdgbKgdVPH eqQA== MIME-Version: 1.0 Received: by 10.204.148.86 with SMTP id o22mr1148371bkv.59.1346942791615; Thu, 06 Sep 2012 07:46:31 -0700 (PDT) Received: by 10.204.56.134 with HTTP; Thu, 6 Sep 2012 07:46:31 -0700 (PDT) In-Reply-To: References: <20120906124617.GT8912@reaktio.net> <20120906125843.GU8912@reaktio.net> Date: Thu, 6 Sep 2012 20:16:31 +0530 Message-ID: From: kk s To: =?ISO-8859-1?Q?Pasi_K=E4rkk=E4inen?= X-Mailman-Approved-At: Thu, 06 Sep 2012 17:05:06 +0000 Cc: xen-users@lists.xen.org Subject: Re: [Xen-users] [Xen-devel] Issue with making rpm with patch applied X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============8384181282722243385==" Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org --===============8384181282722243385== Content-Type: multipart/alternative; boundary=0015175cd29aa0868a04c9098e39 --0015175cd29aa0868a04c9098e39 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Hi, Everything has been done fine. I just want to make sure that I did correct for this patch issue? On Thu, Sep 6, 2012 at 6:51 PM, kk s wrote: > Hi Pasi, > > You are right. > > It looks like the path is wrong and I have changed from a/console.c to > a/tools/ioemu-qemu-xen/console.c and as well for b/ which going fine. > > May I confirm is this correct file that I am applying? > > On Thu, Sep 6, 2012 at 6:28 PM, Pasi K=E4rkk=E4inen wrote: > >> On Thu, Sep 06, 2012 at 06:23:18PM +0530, kk s wrote: >> > Hi Pasi, >> > I have tried with the -p options p1 and p0 which doesn't help :( >> > >> >> Well did you verify the file paths? Where is console.c on the xen source >> tree? >> how many directories 'deep' in the tree? >> >> The patch only mentions a/console.c, so you might need to add some more >> path elements there.. >> >> -- Pasi >> >> > On Thu, Sep 6, 2012 at 6:16 PM, Pasi K=E4rkk=E4inen <[1]pasik@iki.f= i> >> wrote: >> > >> > On Thu, Sep 06, 2012 at 02:44:39PM +0530, kk s wrote: >> > > Hi, >> > > >> > > I have downloaded src rpm from gitco and extracted into the >> > > /usr/src/redhat/SOURCES dir then downloaded the patches and >> renamed >> > it as >> > > properly like xen-3.4.4-xsa17-qemu-xen-traditional-all.patch= . >> Then >> > edited >> > > the xen-x.spec file and added the patches. After that I have >> tried >> > to make >> > > rpm using rpmbuild -bb xen-x.spec and I ended up with the >> below >> > error, >> > > >> > > Patch #13 (xen-3.4.4-xsa17-qemu-xen-traditional-all.patch): >> > > + patch -p1 -s >> > > The text leading up to this was: >> > > -------------------------- >> > > |console: bounds check whenever changing the cursor due to a= n >> > escape code >> > > | >> > > |This is XSA-17 / CVE-2012-3515 >> > > | >> > > |Signed-off-by: Ian Campbell <[1][2]ian.campbell@citrix.com> >> > > | >> > > |diff --git a/console.c b/console.c >> > > |index 5e6e3d0..9984d6f 100644 >> > > |--- a/console.c >> > > |+++ b/console.c >> > > -------------------------- >> > > File to patch: >> > > >> > > Fyi : I have added the patches xsa12-all.patch, >> > > xsa14-xen-3.4-and-4.x.patch and >> > xsa17-qemu-xen-traditional-all.patch. All >> > > the patches goes fine expect >> xsa17-qemu-xen-traditional-all.patch. >> > > >> > > May I know how can I apply this? >> > > >> > >> > With a quick look at your email it looks like wrong -p option for >> patch? >> > -- Pasi >> > >> > References >> > >> > Visible links >> > 1. mailto:pasik@iki.fi >> > 2. mailto:ian.campbell@citrix.com >> > > --0015175cd29aa0868a04c9098e39 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable
Hi,

Everything has been done fine.
<= div>
I just want to make sure that I did correct for this pat= ch issue?



On Thu, Sep 6, 2012 at 6:51 PM, kk s <kks.kbase@gmail.com>= wrote:
Hi Pasi,

You are right.

It looks like the path is wrong and I have changed from a/console.c= to a/tools/ioemu-qemu-xen/console.c and as well for b/ which going fine.

May I confirm is this correct file that I am applying?<= /div>

On Thu, Sep 6, 2012 at 6:28 PM, Pasi K=E4rkk=E4inen <= pasik@iki.fi> wrote:
On Thu, Sep 06, 2012 at 06:23:18PM +053= 0, kk s wrote:
> =A0 =A0Hi Pasi,
> =A0 =A0I have tried with the -p options p1 and p0 which doesn't he= lp :(
>

Well did you verify the file paths? Where is console.c on the xen sou= rce tree?
how many directories 'deep' in the tree?

The patch only mentions a/console.c, so you might need to add some more pat= h elements there..

-- Pasi

> =A0 =A0On Thu, Sep 6, 2012 at 6:16 PM, Pasi K=E4rkk=E4inen <[1]pasik@iki.fi> wrote: >
> =A0 =A0 =A0On Thu, Sep 06, 2012 at 02:44:39PM +0530, kk s wrote:
> =A0 =A0 =A0> =A0 =A0Hi,
> =A0 =A0 =A0>
> =A0 =A0 =A0> =A0 =A0I have downloaded src rpm from gitco and extrac= ted into the
> =A0 =A0 =A0> =A0 =A0/usr/src/redhat/SOURCES dir then downloaded the= patches and renamed
> =A0 =A0 =A0it as
> =A0 =A0 =A0> =A0 =A0properly like xen-3.4.4-xsa17-qemu-xen-traditio= nal-all.patch. Then
> =A0 =A0 =A0edited
> =A0 =A0 =A0> =A0 =A0the xen-x.spec file and added the patches. Afte= r that I have tried
> =A0 =A0 =A0to make
> =A0 =A0 =A0> =A0 =A0rpm using rpmbuild -bb xen-x.spec and I ended u= p with the below
> =A0 =A0 =A0error,
> =A0 =A0 =A0>
> =A0 =A0 =A0> =A0 =A0Patch #13 (xen-3.4.4-xsa17-qemu-xen-traditional= -all.patch):
> =A0 =A0 =A0> =A0 =A0+ patch -p1 -s
> =A0 =A0 =A0> =A0 =A0The text leading up to this was:
> =A0 =A0 =A0> =A0 =A0--------------------------
> =A0 =A0 =A0> =A0 =A0|console: bounds check whenever changing the cu= rsor due to an
> =A0 =A0 =A0escape code
> =A0 =A0 =A0> =A0 =A0|
> =A0 =A0 =A0> =A0 =A0|This is XSA-17 / CVE-2012-3515
> =A0 =A0 =A0> =A0 =A0|
> =A0 =A0 =A0> =A0 =A0|Signed-off-by: Ian Campbell <[1][2]ian.campbell@cit= rix.com>
> =A0 =A0 =A0> =A0 =A0|
> =A0 =A0 =A0> =A0 =A0|diff --git a/console.c b/console.c
> =A0 =A0 =A0> =A0 =A0|index 5e6e3d0..9984d6f 100644
> =A0 =A0 =A0> =A0 =A0|--- a/console.c
> =A0 =A0 =A0> =A0 =A0|+++ b/console.c
> =A0 =A0 =A0> =A0 =A0--------------------------
> =A0 =A0 =A0> =A0 =A0File to patch:
> =A0 =A0 =A0>
> =A0 =A0 =A0> =A0 =A0Fyi : I have added the patches xsa12-all.patch,=
> =A0 =A0 =A0> =A0 =A0xsa14-xen-3.4-and-4.x.patch and
> =A0 =A0 =A0xsa17-qemu-xen-traditional-all.patch. All
> =A0 =A0 =A0> =A0 =A0the patches goes fine expect xsa17-qemu-xen-tra= ditional-all.patch.
> =A0 =A0 =A0>
> =A0 =A0 =A0> =A0 =A0May I know how can I apply this?
> =A0 =A0 =A0>
>
> =A0 =A0 =A0With a quick look at your email it looks like wrong -p opti= on for patch?
> =A0 =A0 =A0-- Pasi
>
> References
>
> =A0 =A0Visible links
> =A0 =A01. mailto:pas= ik@iki.fi
> =A0 =A02. mailto:ian.campbell@citrix.com


--0015175cd29aa0868a04c9098e39-- --===============8384181282722243385== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users --===============8384181282722243385==-- From xen-users-bounces@lists.xen.org Thu Sep 06 17:05:57 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Thu, 06 Sep 2012 17:05:57 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1T9fVs-00089C-H9; Thu, 06 Sep 2012 17:05:08 +0000 Received: from mail27.messagelabs.com ([193.109.254.147]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1T9caa-0005VA-AL; Thu, 06 Sep 2012 13:57:48 +0000 X-Env-Sender: kks.kbase@gmail.com X-Msg-Ref: server-8.tower-27.messagelabs.com!1346939861!9884890!1 X-Originating-IP: [209.85.214.45] X-SpamReason: No, hits=0.4 required=7.0 tests=HTML_30_40,HTML_MESSAGE, ML_RADAR_SPEW_LINKS_14,RCVD_BY_IP,spamassassin: X-StarScan-Received: X-StarScan-Version: 6.6.1.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 32646 invoked from network); 6 Sep 2012 13:57:42 -0000 Received: from mail-bk0-f45.google.com (HELO mail-bk0-f45.google.com) (209.85.214.45) by server-8.tower-27.messagelabs.com with RC4-SHA encrypted SMTP; 6 Sep 2012 13:57:42 -0000 Received: by bkcji1 with SMTP id ji1so819621bkc.32 for ; Thu, 06 Sep 2012 06:57:41 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:date:message-id:subject:from:to:content-type; bh=5Er4xAIOsn/W+pqGTTQlPIyQZr3e2raR7Fs4HjGSk8Y=; b=kIt3mF4wOZFdgtWhegWJxdQNEDo1ZXLZeLkJX7wQ1pELJbQlGSxgmWbyfuRbvd69DL PD8T0udArAeqMfyTh5m+zyYMM1y7Yt068EwwsqUsQfrc43A9yWqiI7sPBQfY46Ncx0nc HcNaTVTa9bWTo75vmSvY0UyNw/PCu0zNQeSicCQ+CE/5P9uPeWWnwbarsVcjl+XhL5q/ rlQr+d8r0LHMtkGQlAV93N50r8DyHC1HYFQi3eJu8rJWiwM7z41VAh/wDwUHTljDIK1W YqNN7XlHv191IU23nfiNXEpoo4817eOgZsK2SpZR9irj0F9gq9/RDxDTcrsjFelh/Lmg zBaA== MIME-Version: 1.0 Received: by 10.205.127.72 with SMTP id gz8mr982906bkc.121.1346939861514; Thu, 06 Sep 2012 06:57:41 -0700 (PDT) Received: by 10.204.56.134 with HTTP; Thu, 6 Sep 2012 06:57:41 -0700 (PDT) Date: Thu, 6 Sep 2012 19:27:41 +0530 Message-ID: From: kk s To: xen-users@lists.xen.org, xen-devel@lists.xen.org X-Mailman-Approved-At: Thu, 06 Sep 2012 17:05:06 +0000 Subject: [Xen-users] XSA patch help X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============8281503675012259436==" Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org --===============8281503675012259436== Content-Type: multipart/alternative; boundary=0015173fe992faba7504c908dfa8 --0015173fe992faba7504c908dfa8 Content-Type: text/plain; charset=ISO-8859-1 Hi, Finally I got success to applied all the patches on my server except "Xen Security Advisory 15 (CVE-2012-3497)" http://lists.xen.org/archives/html/xen-announce/2012-09/msg00006.html . I don't know if this includes any patch or its just the information. If anyone clear this up then I am happy that my servers are secured. --0015173fe992faba7504c908dfa8 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable
Hi,

Finally I got success to applied all = the patches on my server except "Xen Security Advisory 15 (CVE-2012-34= 97)" http://lists.xen.org/archives/html/xen-announce/2012-09/ms= g00006.html .

I don't know if this includes any patch or its just= the information. If anyone clear this up then I am happy that my servers a= re secured.

--0015173fe992faba7504c908dfa8-- --===============8281503675012259436== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users --===============8281503675012259436==-- From xen-users-bounces@lists.xen.org Thu Sep 06 17:05:57 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Thu, 06 Sep 2012 17:05:57 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1T9fVs-00089C-H9; Thu, 06 Sep 2012 17:05:08 +0000 Received: from mail27.messagelabs.com ([193.109.254.147]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1T9caa-0005VA-AL; Thu, 06 Sep 2012 13:57:48 +0000 X-Env-Sender: kks.kbase@gmail.com X-Msg-Ref: server-8.tower-27.messagelabs.com!1346939861!9884890!1 X-Originating-IP: [209.85.214.45] X-SpamReason: No, hits=0.4 required=7.0 tests=HTML_30_40,HTML_MESSAGE, ML_RADAR_SPEW_LINKS_14,RCVD_BY_IP,spamassassin: X-StarScan-Received: X-StarScan-Version: 6.6.1.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 32646 invoked from network); 6 Sep 2012 13:57:42 -0000 Received: from mail-bk0-f45.google.com (HELO mail-bk0-f45.google.com) (209.85.214.45) by server-8.tower-27.messagelabs.com with RC4-SHA encrypted SMTP; 6 Sep 2012 13:57:42 -0000 Received: by bkcji1 with SMTP id ji1so819621bkc.32 for ; Thu, 06 Sep 2012 06:57:41 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:date:message-id:subject:from:to:content-type; bh=5Er4xAIOsn/W+pqGTTQlPIyQZr3e2raR7Fs4HjGSk8Y=; b=kIt3mF4wOZFdgtWhegWJxdQNEDo1ZXLZeLkJX7wQ1pELJbQlGSxgmWbyfuRbvd69DL PD8T0udArAeqMfyTh5m+zyYMM1y7Yt068EwwsqUsQfrc43A9yWqiI7sPBQfY46Ncx0nc HcNaTVTa9bWTo75vmSvY0UyNw/PCu0zNQeSicCQ+CE/5P9uPeWWnwbarsVcjl+XhL5q/ rlQr+d8r0LHMtkGQlAV93N50r8DyHC1HYFQi3eJu8rJWiwM7z41VAh/wDwUHTljDIK1W YqNN7XlHv191IU23nfiNXEpoo4817eOgZsK2SpZR9irj0F9gq9/RDxDTcrsjFelh/Lmg zBaA== MIME-Version: 1.0 Received: by 10.205.127.72 with SMTP id gz8mr982906bkc.121.1346939861514; Thu, 06 Sep 2012 06:57:41 -0700 (PDT) Received: by 10.204.56.134 with HTTP; Thu, 6 Sep 2012 06:57:41 -0700 (PDT) Date: Thu, 6 Sep 2012 19:27:41 +0530 Message-ID: From: kk s To: xen-users@lists.xen.org, xen-devel@lists.xen.org X-Mailman-Approved-At: Thu, 06 Sep 2012 17:05:06 +0000 Subject: [Xen-users] XSA patch help X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============8281503675012259436==" Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org --===============8281503675012259436== Content-Type: multipart/alternative; boundary=0015173fe992faba7504c908dfa8 --0015173fe992faba7504c908dfa8 Content-Type: text/plain; charset=ISO-8859-1 Hi, Finally I got success to applied all the patches on my server except "Xen Security Advisory 15 (CVE-2012-3497)" http://lists.xen.org/archives/html/xen-announce/2012-09/msg00006.html . I don't know if this includes any patch or its just the information. If anyone clear this up then I am happy that my servers are secured. --0015173fe992faba7504c908dfa8 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable
Hi,

Finally I got success to applied all = the patches on my server except "Xen Security Advisory 15 (CVE-2012-34= 97)" http://lists.xen.org/archives/html/xen-announce/2012-09/ms= g00006.html .

I don't know if this includes any patch or its just= the information. If anyone clear this up then I am happy that my servers a= re secured.

--0015173fe992faba7504c908dfa8-- --===============8281503675012259436== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users --===============8281503675012259436==-- From xen-users-bounces@lists.xen.org Thu Sep 06 18:28:55 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Thu, 06 Sep 2012 18:28:55 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1T9gnx-0002Ae-98; Thu, 06 Sep 2012 18:27:53 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1T9gbm-0001mZ-61 for xen-users@lists.xen.org; Thu, 06 Sep 2012 18:15:18 +0000 Received: from [85.158.138.51:60224] by server-11.bemta-3.messagelabs.com id A1/F7-30250-438E8405; Thu, 06 Sep 2012 18:15:16 +0000 X-Env-Sender: kseifried@redhat.com X-Msg-Ref: server-14.tower-174.messagelabs.com!1346955314!22770708!1 X-Originating-IP: [209.132.183.28] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogMjA5LjEzMi4xODMuMjggPT4gNTU5NTQ=\n X-StarScan-Received: X-StarScan-Version: 6.6.1.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 733 invoked from network); 6 Sep 2012 18:15:15 -0000 Received: from mx1.redhat.com (HELO mx1.redhat.com) (209.132.183.28) by server-14.tower-174.messagelabs.com with SMTP; 6 Sep 2012 18:15:15 -0000 Received: from int-mx11.intmail.prod.int.phx2.redhat.com (int-mx11.intmail.prod.int.phx2.redhat.com [10.5.11.24]) by mx1.redhat.com (8.14.4/8.14.4) with ESMTP id q86IF02M022527 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Thu, 6 Sep 2012 14:15:00 -0400 Received: from seif-rht-f16.edm.seifried.org (ovpn-113-47.phx2.redhat.com [10.3.113.47]) by int-mx11.intmail.prod.int.phx2.redhat.com (8.14.4/8.14.4) with ESMTP id q86IEwmL020096; Thu, 6 Sep 2012 14:14:59 -0400 Message-ID: <5048E824.7030802@redhat.com> Date: Thu, 06 Sep 2012 12:15:00 -0600 From: Kurt Seifried User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:14.0) Gecko/20120717 Thunderbird/14.0 MIME-Version: 1.0 To: oss-security@lists.openwall.com References: In-Reply-To: X-Enigmail-Version: 1.4.4 OpenPGP: id=5E267993 X-Scanned-By: MIMEDefang 2.68 on 10.5.11.24 X-Mailman-Approved-At: Thu, 06 Sep 2012 18:27:51 +0000 Cc: xen-users@lists.xen.org, xen-devel@lists.xen.org, xen-announce@lists.xen.org, "Xen.org security team" Subject: Re: [Xen-users] [oss-security] Xen Security Advisory 19 - guest administrator can access qemu monitor console X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 09/06/2012 10:13 AM, Xen.org security team wrote: > Xen Security Advisory XSA-19 > > guest administrator can access qemu monitor console > > > ISSUE DESCRIPTION > ================= > > A guest administrator who is granted access to the graphical console > of a Xen guest can access the qemu monitor. The monitor can be used > to access host resources. > > IMPACT > ====== > > A malicious guest administrator can access host resources (perhaps > belonging to other guests or the underlying system) and may be able to > escalate their privilege to that of the host. > > VULNERABLE SYSTEMS > ================== > > Installations where guest administrators do not have access to a > domain's graphical console, or containing only PV domains configured > without a graphical console, are not vulnerable. > > Installations where all guest administrators are trustworthy are not > vulnerable, even if the guest operating systems themselves are > untrusted. > > Systems using xend/xm: At least all versions since Xen 4.0 are > affected. Systems are vulnerable even if "monitor=no" is specified in > the xm domain configuration file - this configuration option is not > properly honoured in the vulnerable versions. > > Systems using libxl/xl: All versions are affected. The "monitor=" > option is not understood, and is therefore ignored, by xl. However, > systems using the experimental device model version based on upstream > qemu are NOT vulnerable; that is, Xen 4.2 RC systems with > device_model_version="qemu_xen" specified in the xl domain config > file. > > Systems using libvirt are vulnerable. For "xen:" URIs, see xend/xm, > above. For "libxl:" URIs, all versions are affected. > > Systems based on the Xen Cloud Platform are NOT vulnerable. > > CONFIRMING VULNERABILITY > ======================== > > Connect to the guest's VNC (or SDL) graphical display and make sure > your focus is in that window. Hold down CTRL and ALT and press 2. > You will see a black screen showing one of "serial0", "parallel0" or > "QEMU monitor". Repeat this exercise for other digits 3 to > 6. CTRL+ALT+1 is the domain's normal graphical console. Not all > numbers will have screens attached, but note that you must release and > re-press CTRL and ALT each time. > > If one of the accessible screens shows "QEMU monitor" then > you are vulnerable. Otherwise you are not. > > MITIGATION > ========== > > With xl in Xen 4.1 and later, supplying the following config > option in the VM configuration file will disable the monitor: > device_model_args=["-monitor","null"] > > With xend the following config option will disable the monitor: > monitor_path="null" > Note that with a vulnerable version of the software specifying > "monitor=0" will NOT disable the monitor. > > We are not currently aware of the availability of mitigation for > systems using libvirt. > > NOTE REGARDING EMBARGO > ====================== > > This issue was publicly discussed online by its discoverer. > There is therefore no embargo. > > NOTE REGARDING CVE > ================== > > This issue was previously reported in a different context, not to Xen > upstream, and assigned CVE-2007-0998 and fixed in a different way. We > have requested a new CVE for XSA-19 but it is not yet available. Ahh I see the request now (it was in a different email folder). Please use CVE-2012-4411 for this issue. > RESOLUTION > ========== > > The attached patch against qemu-xen-traditional > (qemu-xen-4.*-testing.git) resolves this issue. > > $ sha256sum xsa19-qemu-all.patch > 19fc5ff9334e7e7ad429388850dc6e52e7062c21a677082e7a89c2f2c91365fa xsa19-qemu-all.patch > - -- Kurt Seifried Red Hat Security Response Team (SRT) PGP: 0x5E267993 A90B F995 7350 148F 66BF 7554 160D 4553 5E26 7993 -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.12 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://www.enigmail.net/ iQIcBAEBAgAGBQJQSOgkAAoJEBYNRVNeJnmTonAP/3BTawvHhQX3HOScXFSUiIuO Sp8+Swmfe4uvxGOR4z/q3f3FdrKN6GdBc9cmmZeSSuYelFYaIpG6PIgv4Tbf9Fwy F8qc/nxHSWhb19J/ifAHckd7kq99qrdei+59jZeiy8PTS+6//SeVhLDvKlV7B/1X QsS3qM6vgpGXx9xoCIxyjVODIm23Q/iWjyqtJl3uqiW5wymLOcZvLC37Do/2DJ8l NOEqDalueYypKhPZnoj05iUiuR4vpSl/DNMvi6NHu0fI3ZEATCkEPV16fCSnPIv6 oN2UG0X7qNmIBz7oUD7lnoM86TGjFuxT4Ka4gSACykaeGpIuoeFbcboEKqMmejXH 9knYcMl9+t0G3yNYPpA6G2ED0BVXu8Ov3JmO2FoT9OEgkDv7HGD50GltnqYFvM2b O97g3GJ9w0lJQ55cWzjU6lr763tM/lYYcl3KX/ic8frtX+7FK+rXHt0j+QHWRzbx YmewJphXkURBVva+FvYhTlagh2tWK1w2yUarrTFiFoxUss/out58L2QP5ie41urG JNajebW8gNPa/C3MxB+IWfGLci36+3/qW+czgvEOMwFsbE2YmbnSrZiA+9wrPNzJ Ngn88tHZftHwUwbikjYwMBCZnFG1hySyQUCu+Ym3itQqbA9IQRxaBbBOzI4gLxso LuaafXJ0lxi3HvevyfvA =ZGCU -----END PGP SIGNATURE----- _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Thu Sep 06 18:28:55 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Thu, 06 Sep 2012 18:28:55 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1T9gnx-0002Ae-98; Thu, 06 Sep 2012 18:27:53 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1T9gbm-0001mZ-61 for xen-users@lists.xen.org; Thu, 06 Sep 2012 18:15:18 +0000 Received: from [85.158.138.51:60224] by server-11.bemta-3.messagelabs.com id A1/F7-30250-438E8405; Thu, 06 Sep 2012 18:15:16 +0000 X-Env-Sender: kseifried@redhat.com X-Msg-Ref: server-14.tower-174.messagelabs.com!1346955314!22770708!1 X-Originating-IP: [209.132.183.28] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogMjA5LjEzMi4xODMuMjggPT4gNTU5NTQ=\n X-StarScan-Received: X-StarScan-Version: 6.6.1.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 733 invoked from network); 6 Sep 2012 18:15:15 -0000 Received: from mx1.redhat.com (HELO mx1.redhat.com) (209.132.183.28) by server-14.tower-174.messagelabs.com with SMTP; 6 Sep 2012 18:15:15 -0000 Received: from int-mx11.intmail.prod.int.phx2.redhat.com (int-mx11.intmail.prod.int.phx2.redhat.com [10.5.11.24]) by mx1.redhat.com (8.14.4/8.14.4) with ESMTP id q86IF02M022527 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Thu, 6 Sep 2012 14:15:00 -0400 Received: from seif-rht-f16.edm.seifried.org (ovpn-113-47.phx2.redhat.com [10.3.113.47]) by int-mx11.intmail.prod.int.phx2.redhat.com (8.14.4/8.14.4) with ESMTP id q86IEwmL020096; Thu, 6 Sep 2012 14:14:59 -0400 Message-ID: <5048E824.7030802@redhat.com> Date: Thu, 06 Sep 2012 12:15:00 -0600 From: Kurt Seifried User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:14.0) Gecko/20120717 Thunderbird/14.0 MIME-Version: 1.0 To: oss-security@lists.openwall.com References: In-Reply-To: X-Enigmail-Version: 1.4.4 OpenPGP: id=5E267993 X-Scanned-By: MIMEDefang 2.68 on 10.5.11.24 X-Mailman-Approved-At: Thu, 06 Sep 2012 18:27:51 +0000 Cc: xen-users@lists.xen.org, xen-devel@lists.xen.org, xen-announce@lists.xen.org, "Xen.org security team" Subject: Re: [Xen-users] [oss-security] Xen Security Advisory 19 - guest administrator can access qemu monitor console X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 09/06/2012 10:13 AM, Xen.org security team wrote: > Xen Security Advisory XSA-19 > > guest administrator can access qemu monitor console > > > ISSUE DESCRIPTION > ================= > > A guest administrator who is granted access to the graphical console > of a Xen guest can access the qemu monitor. The monitor can be used > to access host resources. > > IMPACT > ====== > > A malicious guest administrator can access host resources (perhaps > belonging to other guests or the underlying system) and may be able to > escalate their privilege to that of the host. > > VULNERABLE SYSTEMS > ================== > > Installations where guest administrators do not have access to a > domain's graphical console, or containing only PV domains configured > without a graphical console, are not vulnerable. > > Installations where all guest administrators are trustworthy are not > vulnerable, even if the guest operating systems themselves are > untrusted. > > Systems using xend/xm: At least all versions since Xen 4.0 are > affected. Systems are vulnerable even if "monitor=no" is specified in > the xm domain configuration file - this configuration option is not > properly honoured in the vulnerable versions. > > Systems using libxl/xl: All versions are affected. The "monitor=" > option is not understood, and is therefore ignored, by xl. However, > systems using the experimental device model version based on upstream > qemu are NOT vulnerable; that is, Xen 4.2 RC systems with > device_model_version="qemu_xen" specified in the xl domain config > file. > > Systems using libvirt are vulnerable. For "xen:" URIs, see xend/xm, > above. For "libxl:" URIs, all versions are affected. > > Systems based on the Xen Cloud Platform are NOT vulnerable. > > CONFIRMING VULNERABILITY > ======================== > > Connect to the guest's VNC (or SDL) graphical display and make sure > your focus is in that window. Hold down CTRL and ALT and press 2. > You will see a black screen showing one of "serial0", "parallel0" or > "QEMU monitor". Repeat this exercise for other digits 3 to > 6. CTRL+ALT+1 is the domain's normal graphical console. Not all > numbers will have screens attached, but note that you must release and > re-press CTRL and ALT each time. > > If one of the accessible screens shows "QEMU monitor" then > you are vulnerable. Otherwise you are not. > > MITIGATION > ========== > > With xl in Xen 4.1 and later, supplying the following config > option in the VM configuration file will disable the monitor: > device_model_args=["-monitor","null"] > > With xend the following config option will disable the monitor: > monitor_path="null" > Note that with a vulnerable version of the software specifying > "monitor=0" will NOT disable the monitor. > > We are not currently aware of the availability of mitigation for > systems using libvirt. > > NOTE REGARDING EMBARGO > ====================== > > This issue was publicly discussed online by its discoverer. > There is therefore no embargo. > > NOTE REGARDING CVE > ================== > > This issue was previously reported in a different context, not to Xen > upstream, and assigned CVE-2007-0998 and fixed in a different way. We > have requested a new CVE for XSA-19 but it is not yet available. Ahh I see the request now (it was in a different email folder). Please use CVE-2012-4411 for this issue. > RESOLUTION > ========== > > The attached patch against qemu-xen-traditional > (qemu-xen-4.*-testing.git) resolves this issue. > > $ sha256sum xsa19-qemu-all.patch > 19fc5ff9334e7e7ad429388850dc6e52e7062c21a677082e7a89c2f2c91365fa xsa19-qemu-all.patch > - -- Kurt Seifried Red Hat Security Response Team (SRT) PGP: 0x5E267993 A90B F995 7350 148F 66BF 7554 160D 4553 5E26 7993 -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.12 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://www.enigmail.net/ iQIcBAEBAgAGBQJQSOgkAAoJEBYNRVNeJnmTonAP/3BTawvHhQX3HOScXFSUiIuO Sp8+Swmfe4uvxGOR4z/q3f3FdrKN6GdBc9cmmZeSSuYelFYaIpG6PIgv4Tbf9Fwy F8qc/nxHSWhb19J/ifAHckd7kq99qrdei+59jZeiy8PTS+6//SeVhLDvKlV7B/1X QsS3qM6vgpGXx9xoCIxyjVODIm23Q/iWjyqtJl3uqiW5wymLOcZvLC37Do/2DJ8l NOEqDalueYypKhPZnoj05iUiuR4vpSl/DNMvi6NHu0fI3ZEATCkEPV16fCSnPIv6 oN2UG0X7qNmIBz7oUD7lnoM86TGjFuxT4Ka4gSACykaeGpIuoeFbcboEKqMmejXH 9knYcMl9+t0G3yNYPpA6G2ED0BVXu8Ov3JmO2FoT9OEgkDv7HGD50GltnqYFvM2b O97g3GJ9w0lJQ55cWzjU6lr763tM/lYYcl3KX/ic8frtX+7FK+rXHt0j+QHWRzbx YmewJphXkURBVva+FvYhTlagh2tWK1w2yUarrTFiFoxUss/out58L2QP5ie41urG JNajebW8gNPa/C3MxB+IWfGLci36+3/qW+czgvEOMwFsbE2YmbnSrZiA+9wrPNzJ Ngn88tHZftHwUwbikjYwMBCZnFG1hySyQUCu+Ym3itQqbA9IQRxaBbBOzI4gLxso LuaafXJ0lxi3HvevyfvA =ZGCU -----END PGP SIGNATURE----- _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Thu Sep 06 18:42:57 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Thu, 06 Sep 2012 18:42:57 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1T9h1d-0002kh-TK; Thu, 06 Sep 2012 18:42:01 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1T9h1d-0002kc-4P for xen-users@lists.xen.org; Thu, 06 Sep 2012 18:42:01 +0000 Received: from [85.158.143.35:53839] by server-1.bemta-4.messagelabs.com id E4/98-12504-87EE8405; Thu, 06 Sep 2012 18:42:00 +0000 X-Env-Sender: andy@gamubaru.com X-Msg-Ref: server-3.tower-21.messagelabs.com!1346956915!13683278!1 X-Originating-IP: [97.77.79.203] X-SpamReason: No, hits=0.0 required=7.0 tests= X-StarScan-Received: X-StarScan-Version: 6.6.1.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 12553 invoked from network); 6 Sep 2012 18:41:58 -0000 Received: from trillian.gamubaru.com (HELO trillian.gamubaru.com) (97.77.79.203) by server-3.tower-21.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 6 Sep 2012 18:41:58 -0000 Received: from localhost (localhost.localdomain [127.0.0.1]) by trillian.gamubaru.com (Postfix) with ESMTP id 873172B61C1 for ; Thu, 6 Sep 2012 12:56:29 -0500 (CDT) X-Virus-Scanned: amavisd-new at gamubaru.com Received: from trillian.gamubaru.com ([127.0.0.1]) by localhost (trillian.localdomain [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id cng6Ej5agXcP for ; Thu, 6 Sep 2012 12:56:25 -0500 (CDT) Received: from [192.168.20.7] (unknown [192.168.30.2]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (No client certificate requested) by trillian.gamubaru.com (Postfix) with ESMTPSA id CB90F2B61BF for ; Thu, 6 Sep 2012 12:56:24 -0500 (CDT) Message-ID: <5048EE6D.10606@gamubaru.com> Date: Thu, 06 Sep 2012 13:41:49 -0500 From: Andy Howell User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:15.0) Gecko/20120827 Thunderbird/15.0 MIME-Version: 1.0 To: xen-users@lists.xen.org References: <50405CCB.7060802@gamubaru.com> <20120906151224.GC8912@reaktio.net> In-Reply-To: <20120906151224.GC8912@reaktio.net> Subject: Re: [Xen-users] No dom0 video after startup on ubuntu 12.04 xen 4.1.2-2ubuntu2.2 X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset="iso-8859-1"; Format="flowed" Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org On 09/06/2012 10:12 AM, Pasi K=E4rkk=E4inen wrote: > On Fri, Aug 31, 2012 at 01:42:19AM -0500, Andy Howell wrote: >> I'm trying to get xen running on my laptop. It starts booting, >> resets the video to a blank black screen, then nothing. It seems >> like its still running. ctrl-alt-del reboots. >> >> Any ideas? >> > > Did you try with giving dom0 Linux kernel (vmlinuz) "nomodeset" option? > Pasi, Yes, in /etc/default/grub I set: GRUB_CMDLINE_LINUX_DEFAULT=3D"nomodeset vga=3Dnormal" and did and update-grub and rebooted. Same results. Thanks, Andy _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Thu Sep 06 18:42:57 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Thu, 06 Sep 2012 18:42:57 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1T9h1d-0002kh-TK; Thu, 06 Sep 2012 18:42:01 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1T9h1d-0002kc-4P for xen-users@lists.xen.org; Thu, 06 Sep 2012 18:42:01 +0000 Received: from [85.158.143.35:53839] by server-1.bemta-4.messagelabs.com id E4/98-12504-87EE8405; Thu, 06 Sep 2012 18:42:00 +0000 X-Env-Sender: andy@gamubaru.com X-Msg-Ref: server-3.tower-21.messagelabs.com!1346956915!13683278!1 X-Originating-IP: [97.77.79.203] X-SpamReason: No, hits=0.0 required=7.0 tests= X-StarScan-Received: X-StarScan-Version: 6.6.1.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 12553 invoked from network); 6 Sep 2012 18:41:58 -0000 Received: from trillian.gamubaru.com (HELO trillian.gamubaru.com) (97.77.79.203) by server-3.tower-21.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 6 Sep 2012 18:41:58 -0000 Received: from localhost (localhost.localdomain [127.0.0.1]) by trillian.gamubaru.com (Postfix) with ESMTP id 873172B61C1 for ; Thu, 6 Sep 2012 12:56:29 -0500 (CDT) X-Virus-Scanned: amavisd-new at gamubaru.com Received: from trillian.gamubaru.com ([127.0.0.1]) by localhost (trillian.localdomain [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id cng6Ej5agXcP for ; Thu, 6 Sep 2012 12:56:25 -0500 (CDT) Received: from [192.168.20.7] (unknown [192.168.30.2]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (No client certificate requested) by trillian.gamubaru.com (Postfix) with ESMTPSA id CB90F2B61BF for ; Thu, 6 Sep 2012 12:56:24 -0500 (CDT) Message-ID: <5048EE6D.10606@gamubaru.com> Date: Thu, 06 Sep 2012 13:41:49 -0500 From: Andy Howell User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:15.0) Gecko/20120827 Thunderbird/15.0 MIME-Version: 1.0 To: xen-users@lists.xen.org References: <50405CCB.7060802@gamubaru.com> <20120906151224.GC8912@reaktio.net> In-Reply-To: <20120906151224.GC8912@reaktio.net> Subject: Re: [Xen-users] No dom0 video after startup on ubuntu 12.04 xen 4.1.2-2ubuntu2.2 X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset="iso-8859-1"; Format="flowed" Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org On 09/06/2012 10:12 AM, Pasi K=E4rkk=E4inen wrote: > On Fri, Aug 31, 2012 at 01:42:19AM -0500, Andy Howell wrote: >> I'm trying to get xen running on my laptop. It starts booting, >> resets the video to a blank black screen, then nothing. It seems >> like its still running. ctrl-alt-del reboots. >> >> Any ideas? >> > > Did you try with giving dom0 Linux kernel (vmlinuz) "nomodeset" option? > Pasi, Yes, in /etc/default/grub I set: GRUB_CMDLINE_LINUX_DEFAULT=3D"nomodeset vga=3Dnormal" and did and update-grub and rebooted. Same results. Thanks, Andy _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Thu Sep 06 21:35:23 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Thu, 06 Sep 2012 21:35:23 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1T9jiH-0006AT-7u; Thu, 06 Sep 2012 21:34:13 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1T9jiG-0006AO-1H for xen-users@lists.xen.org; Thu, 06 Sep 2012 21:34:12 +0000 Received: from [85.158.139.83:33884] by server-5.bemta-5.messagelabs.com id C3/04-30514-3D619405; Thu, 06 Sep 2012 21:34:11 +0000 X-Env-Sender: konrad.wilk@oracle.com X-Msg-Ref: server-5.tower-182.messagelabs.com!1346967249!28799461!1 X-Originating-IP: [141.146.126.227] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogMTQxLjE0Ni4xMjYuMjI3ID0+IDc0MzEyOQ==\n X-StarScan-Received: X-StarScan-Version: 6.6.1.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 18021 invoked from network); 6 Sep 2012 21:34:10 -0000 Received: from acsinet15.oracle.com (HELO acsinet15.oracle.com) (141.146.126.227) by server-5.tower-182.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 6 Sep 2012 21:34:10 -0000 Received: from ucsinet21.oracle.com (ucsinet21.oracle.com [156.151.31.93]) by acsinet15.oracle.com (Sentrion-MTA-4.2.2/Sentrion-MTA-4.2.2) with ESMTP id q86LXspj019367 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Thu, 6 Sep 2012 21:33:55 GMT Received: from acsmt356.oracle.com (acsmt356.oracle.com [141.146.40.156]) by ucsinet21.oracle.com (8.14.4+Sun/8.14.4) with ESMTP id q86LXr0f013387 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 6 Sep 2012 21:33:54 GMT Received: from abhmt109.oracle.com (abhmt109.oracle.com [141.146.116.61]) by acsmt356.oracle.com (8.12.11.20060308/8.12.11) with ESMTP id q86LXraG032741; Thu, 6 Sep 2012 16:33:53 -0500 Received: from phenom.dumpdata.com (/209.6.85.33) by default (Oracle Beehive Gateway v4.0) with ESMTP ; Thu, 06 Sep 2012 14:33:53 -0700 Received: by phenom.dumpdata.com (Postfix, from userid 1000) id C9F5A402E4; Thu, 6 Sep 2012 17:23:21 -0400 (EDT) Date: Thu, 6 Sep 2012 17:23:21 -0400 From: Konrad Rzeszutek Wilk To: Pasi =?iso-8859-1?Q?K=E4rkk=E4inen?= Message-ID: <20120906212321.GA490@phenom.dumpdata.com> References: <20120906151157.GB8912@reaktio.net> MIME-Version: 1.0 Content-Disposition: inline In-Reply-To: <20120906151157.GB8912@reaktio.net> User-Agent: Mutt/1.5.21 (2010-09-15) X-Source-IP: ucsinet21.oracle.com [156.151.31.93] Cc: xen-users@lists.xen.org, Brian Johnson Subject: Re: [Xen-users] Nvidia: card fails to work in EITHER dom0 or domU -- any advice? X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org On Thu, Sep 06, 2012 at 06:11:57PM +0300, Pasi K=E4rkk=E4inen wrote: > On Thu, Aug 30, 2012 at 03:37:23PM -0700, Brian Johnson wrote: > > Hi all, > > I have a Nvidia GeForce GTX 680 that I'd like to use in a Xen > > configuration. I don't care if it's used by dom0 or by a linux domU > > guest, either would be OK for my purposes. Since getting this card,= I've > > experimented with Linux 3.4.6 and Xen 4.1.2 and determined the follo= wing: > > 1. The card works correctly under a linux kernel without Xen running. > > 2. The Nvidia proprietary drivers do not function in a dom0 setting, > > because PAT is disabled in the dom0 kernel. The driver detects this= and > > refuses to run. > > > = > Hmmm.. maybe Konrad (cc) can tell more about the PAT stuff. = You could revert one patch and insert two other ones that make PAT work. Look at http://lists.xen.org/archives/html/xen-devel/2012-05/msg02277.html ah, but the resolution never got copied. If you can revert 8eaffa67b43e99ae581622c5133e20b0f48bcef1 and merge git://git.kernel.org/pub/scm/linux/kernel/git/konrad/xen.git stab= le/for-x86 Or here: https://groups.google.com/forum/?fromgroups=3D#!topic/qubes-devel/MyVtKaKfq= IM > = > > 3. Using PCI passthrough to a domU linux VM does not work either -- = the > > Nvidia proprietary driver does not recognize the card in the guest. = Not > > sure why, but I suspect some resource the card uses is not being pas= sed > > through correctly. (I can pass an AMD card to a domU without proble= ms.) > > I know that the Nvidia proprietary driver doesn't officially support= Xen, > > so getting it to work in dom0 might be futile, even if the PAT issue= is > > resolved. So my main hope is to get passthrough to a guest working > > correctly. Any suggestions? Is Xen 4.2 more likely to work for my = use > > case? > > > = > You probably need the Nvidia vga passthru patches for Xen. = > Those patches are not yet merged to Xen, so they're out-of-tree. > = > = > > (The nouveau driver is not an option for me because I require OpenGL= 3.2+ > > features, and last I checked, it doesn't support the GTX 680 anyway.) > > Brian > = > -- Pasi _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Thu Sep 06 21:35:23 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Thu, 06 Sep 2012 21:35:23 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1T9jiH-0006AT-7u; Thu, 06 Sep 2012 21:34:13 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1T9jiG-0006AO-1H for xen-users@lists.xen.org; Thu, 06 Sep 2012 21:34:12 +0000 Received: from [85.158.139.83:33884] by server-5.bemta-5.messagelabs.com id C3/04-30514-3D619405; Thu, 06 Sep 2012 21:34:11 +0000 X-Env-Sender: konrad.wilk@oracle.com X-Msg-Ref: server-5.tower-182.messagelabs.com!1346967249!28799461!1 X-Originating-IP: [141.146.126.227] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogMTQxLjE0Ni4xMjYuMjI3ID0+IDc0MzEyOQ==\n X-StarScan-Received: X-StarScan-Version: 6.6.1.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 18021 invoked from network); 6 Sep 2012 21:34:10 -0000 Received: from acsinet15.oracle.com (HELO acsinet15.oracle.com) (141.146.126.227) by server-5.tower-182.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 6 Sep 2012 21:34:10 -0000 Received: from ucsinet21.oracle.com (ucsinet21.oracle.com [156.151.31.93]) by acsinet15.oracle.com (Sentrion-MTA-4.2.2/Sentrion-MTA-4.2.2) with ESMTP id q86LXspj019367 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Thu, 6 Sep 2012 21:33:55 GMT Received: from acsmt356.oracle.com (acsmt356.oracle.com [141.146.40.156]) by ucsinet21.oracle.com (8.14.4+Sun/8.14.4) with ESMTP id q86LXr0f013387 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 6 Sep 2012 21:33:54 GMT Received: from abhmt109.oracle.com (abhmt109.oracle.com [141.146.116.61]) by acsmt356.oracle.com (8.12.11.20060308/8.12.11) with ESMTP id q86LXraG032741; Thu, 6 Sep 2012 16:33:53 -0500 Received: from phenom.dumpdata.com (/209.6.85.33) by default (Oracle Beehive Gateway v4.0) with ESMTP ; Thu, 06 Sep 2012 14:33:53 -0700 Received: by phenom.dumpdata.com (Postfix, from userid 1000) id C9F5A402E4; Thu, 6 Sep 2012 17:23:21 -0400 (EDT) Date: Thu, 6 Sep 2012 17:23:21 -0400 From: Konrad Rzeszutek Wilk To: Pasi =?iso-8859-1?Q?K=E4rkk=E4inen?= Message-ID: <20120906212321.GA490@phenom.dumpdata.com> References: <20120906151157.GB8912@reaktio.net> MIME-Version: 1.0 Content-Disposition: inline In-Reply-To: <20120906151157.GB8912@reaktio.net> User-Agent: Mutt/1.5.21 (2010-09-15) X-Source-IP: ucsinet21.oracle.com [156.151.31.93] Cc: xen-users@lists.xen.org, Brian Johnson Subject: Re: [Xen-users] Nvidia: card fails to work in EITHER dom0 or domU -- any advice? X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org On Thu, Sep 06, 2012 at 06:11:57PM +0300, Pasi K=E4rkk=E4inen wrote: > On Thu, Aug 30, 2012 at 03:37:23PM -0700, Brian Johnson wrote: > > Hi all, > > I have a Nvidia GeForce GTX 680 that I'd like to use in a Xen > > configuration. I don't care if it's used by dom0 or by a linux domU > > guest, either would be OK for my purposes. Since getting this card,= I've > > experimented with Linux 3.4.6 and Xen 4.1.2 and determined the follo= wing: > > 1. The card works correctly under a linux kernel without Xen running. > > 2. The Nvidia proprietary drivers do not function in a dom0 setting, > > because PAT is disabled in the dom0 kernel. The driver detects this= and > > refuses to run. > > > = > Hmmm.. maybe Konrad (cc) can tell more about the PAT stuff. = You could revert one patch and insert two other ones that make PAT work. Look at http://lists.xen.org/archives/html/xen-devel/2012-05/msg02277.html ah, but the resolution never got copied. If you can revert 8eaffa67b43e99ae581622c5133e20b0f48bcef1 and merge git://git.kernel.org/pub/scm/linux/kernel/git/konrad/xen.git stab= le/for-x86 Or here: https://groups.google.com/forum/?fromgroups=3D#!topic/qubes-devel/MyVtKaKfq= IM > = > > 3. Using PCI passthrough to a domU linux VM does not work either -- = the > > Nvidia proprietary driver does not recognize the card in the guest. = Not > > sure why, but I suspect some resource the card uses is not being pas= sed > > through correctly. (I can pass an AMD card to a domU without proble= ms.) > > I know that the Nvidia proprietary driver doesn't officially support= Xen, > > so getting it to work in dom0 might be futile, even if the PAT issue= is > > resolved. So my main hope is to get passthrough to a guest working > > correctly. Any suggestions? Is Xen 4.2 more likely to work for my = use > > case? > > > = > You probably need the Nvidia vga passthru patches for Xen. = > Those patches are not yet merged to Xen, so they're out-of-tree. > = > = > > (The nouveau driver is not an option for me because I require OpenGL= 3.2+ > > features, and last I checked, it doesn't support the GTX 680 anyway.) > > Brian > = > -- Pasi _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Thu Sep 06 22:16:09 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Thu, 06 Sep 2012 22:16:09 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1T9kLh-0006zO-4S; Thu, 06 Sep 2012 22:14:57 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1T9kLf-0006zJ-Bt for xen-users@lists.xen.org; Thu, 06 Sep 2012 22:14:55 +0000 Received: from [85.158.143.99:23625] by server-3.bemta-4.messagelabs.com id EE/77-08232-E5029405; Thu, 06 Sep 2012 22:14:54 +0000 X-Env-Sender: nathan@gossamer-threads.com X-Msg-Ref: server-12.tower-216.messagelabs.com!1346969692!23750204!1 X-Originating-IP: [208.70.244.21] X-SpamReason: No, hits=0.0 required=7.0 tests=HTML_MESSAGE X-StarScan-Received: X-StarScan-Version: 6.6.1.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 6393 invoked from network); 6 Sep 2012 22:14:53 -0000 Received: from gossamer.nmsrv.com (HELO gossamer.nmsrv.com) (208.70.244.21) by server-12.tower-216.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 6 Sep 2012 22:14:53 -0000 DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=gossamer-threads.com; h= from:to:subject:date:content-type:message-id:mime-version :reply-to; s=mail; bh=VgNRGnsXhBB3L18PKF6DSRxRpIE=; b=qml/bfnn2u CUjV6mn+FlZaPD4Zp8nzn45QtfORG302jM4NPQFFUgFEoMkCXHgrkGVUw9qX6672 9h7eStw++trsMExr3pLXCaaJ0Rx5MLZ320BrRkk8pbomkEXsfNEV9fQdLITfIHRY vHeR/Erp6cmwc/KJHa/p90gjuHfxlbdOo= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gossamer-threads.com; h=from :to:subject:date:content-type:message-id:mime-version:reply-to; q=dns; s=mail; b=WJzgLGETlhkHqvihQ9AR9yDHau2hRodzWlhi5HFl9euaQy KhBFLaSGJOhANnDxiSQv/R+pgdgIs947CO0XGcs+mUkyIVAdwq+rMuGb6xJqVt3G lppfxO5DsazvRYo7DvF6TSP4+LDWxEo97dM/YO1+IgvsMaFCvYNUxm0R4arP0= Received: (qmail 9793 invoked from network); 6 Sep 2012 22:14:51 -0000 X-AntiVirus: Clean Received: from gateway.gossamer-threads.com (HELO ?192.168.1.152?) (nathan@gt.net@208.70.247.145) by gossamer.nmsrv.com with ESMTPSA (AES128-SHA encrypted); 6 Sep 2012 22:14:51 -0000 From: nathan@gossamer-threads.com To: xen-users@lists.xen.org Date: Thu, 06 Sep 2012 22:14:46 +0000 Message-Id: Mime-Version: 1.0 User-Agent: eM_Client/4.0.15145.0 Subject: [Xen-users] Xen 4.1.4 release imminent? X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list Reply-To: nathan@gossamer-threads.com List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============7612006202155766691==" Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org --===============7612006202155766691== Content-Type: multipart/alternative; boundary="------=_MB65B9355D-248C-4201-AB92-1FE62698B5B2" --------=_MB65B9355D-248C-4201-AB92-1FE62698B5B2 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; format=flowed; charset=utf-8 Hi, Just wondering if there's a release of xen 4.1.4 being planned for the=20 near future to bundle up the recent XSA's? - Nathan --------=_MB65B9355D-248C-4201-AB92-1FE62698B5B2 Content-Transfer-Encoding: quoted-printable Content-Type: text/html; charset=utf-8
Hi,

Just wondering if there's a release of xen 4.1.4 being plan= ned for the near future to bundle up the recent XSA's?

- Nathan --------=_MB65B9355D-248C-4201-AB92-1FE62698B5B2-- --===============7612006202155766691== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users --===============7612006202155766691==-- From xen-users-bounces@lists.xen.org Thu Sep 06 22:16:09 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Thu, 06 Sep 2012 22:16:09 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1T9kLh-0006zO-4S; Thu, 06 Sep 2012 22:14:57 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1T9kLf-0006zJ-Bt for xen-users@lists.xen.org; Thu, 06 Sep 2012 22:14:55 +0000 Received: from [85.158.143.99:23625] by server-3.bemta-4.messagelabs.com id EE/77-08232-E5029405; Thu, 06 Sep 2012 22:14:54 +0000 X-Env-Sender: nathan@gossamer-threads.com X-Msg-Ref: server-12.tower-216.messagelabs.com!1346969692!23750204!1 X-Originating-IP: [208.70.244.21] X-SpamReason: No, hits=0.0 required=7.0 tests=HTML_MESSAGE X-StarScan-Received: X-StarScan-Version: 6.6.1.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 6393 invoked from network); 6 Sep 2012 22:14:53 -0000 Received: from gossamer.nmsrv.com (HELO gossamer.nmsrv.com) (208.70.244.21) by server-12.tower-216.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 6 Sep 2012 22:14:53 -0000 DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=gossamer-threads.com; h= from:to:subject:date:content-type:message-id:mime-version :reply-to; s=mail; bh=VgNRGnsXhBB3L18PKF6DSRxRpIE=; b=qml/bfnn2u CUjV6mn+FlZaPD4Zp8nzn45QtfORG302jM4NPQFFUgFEoMkCXHgrkGVUw9qX6672 9h7eStw++trsMExr3pLXCaaJ0Rx5MLZ320BrRkk8pbomkEXsfNEV9fQdLITfIHRY vHeR/Erp6cmwc/KJHa/p90gjuHfxlbdOo= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gossamer-threads.com; h=from :to:subject:date:content-type:message-id:mime-version:reply-to; q=dns; s=mail; b=WJzgLGETlhkHqvihQ9AR9yDHau2hRodzWlhi5HFl9euaQy KhBFLaSGJOhANnDxiSQv/R+pgdgIs947CO0XGcs+mUkyIVAdwq+rMuGb6xJqVt3G lppfxO5DsazvRYo7DvF6TSP4+LDWxEo97dM/YO1+IgvsMaFCvYNUxm0R4arP0= Received: (qmail 9793 invoked from network); 6 Sep 2012 22:14:51 -0000 X-AntiVirus: Clean Received: from gateway.gossamer-threads.com (HELO ?192.168.1.152?) (nathan@gt.net@208.70.247.145) by gossamer.nmsrv.com with ESMTPSA (AES128-SHA encrypted); 6 Sep 2012 22:14:51 -0000 From: nathan@gossamer-threads.com To: xen-users@lists.xen.org Date: Thu, 06 Sep 2012 22:14:46 +0000 Message-Id: Mime-Version: 1.0 User-Agent: eM_Client/4.0.15145.0 Subject: [Xen-users] Xen 4.1.4 release imminent? X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list Reply-To: nathan@gossamer-threads.com List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============7612006202155766691==" Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org --===============7612006202155766691== Content-Type: multipart/alternative; boundary="------=_MB65B9355D-248C-4201-AB92-1FE62698B5B2" --------=_MB65B9355D-248C-4201-AB92-1FE62698B5B2 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; format=flowed; charset=utf-8 Hi, Just wondering if there's a release of xen 4.1.4 being planned for the=20 near future to bundle up the recent XSA's? - Nathan --------=_MB65B9355D-248C-4201-AB92-1FE62698B5B2 Content-Transfer-Encoding: quoted-printable Content-Type: text/html; charset=utf-8
Hi,

Just wondering if there's a release of xen 4.1.4 being plan= ned for the near future to bundle up the recent XSA's?

- Nathan --------=_MB65B9355D-248C-4201-AB92-1FE62698B5B2-- --===============7612006202155766691== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users --===============7612006202155766691==-- From xen-users-bounces@lists.xen.org Fri Sep 07 00:23:54 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Fri, 07 Sep 2012 00:23:54 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1T9mLG-0000dZ-6E; Fri, 07 Sep 2012 00:22:38 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1T9mLD-0000dU-VO for xen-users@lists.xensource.com; Fri, 07 Sep 2012 00:22:36 +0000 Received: from [85.158.143.99:42142] by server-2.bemta-4.messagelabs.com id 81/50-21239-B4E39405; Fri, 07 Sep 2012 00:22:35 +0000 X-Env-Sender: mike.a.collins@ark-net.org X-Msg-Ref: server-7.tower-216.messagelabs.com!1346977353!25637951!1 X-Originating-IP: [216.33.127.81] X-SpamReason: No, hits=0.0 required=7.0 tests= X-StarScan-Received: X-StarScan-Version: 6.6.1.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 31127 invoked from network); 7 Sep 2012 00:22:34 -0000 Received: from mta21.charter.net (HELO mta21.charter.net) (216.33.127.81) by server-7.tower-216.messagelabs.com with SMTP; 7 Sep 2012 00:22:34 -0000 Received: from imp11 ([10.20.200.11]) by mta21.charter.net (InterMail vM.8.01.05.02 201-2260-151-103-20110920) with ESMTP id <20120907002233.HCGO12025.mta21.charter.net@imp11>; Thu, 6 Sep 2012 20:22:33 -0400 Received: from mail.ark-net.org ([75.138.215.251]) by imp11 with smtp.charter.net id w0NY1j00a5S18aK050NZ7h; Thu, 06 Sep 2012 20:22:33 -0400 X-Authority-Analysis: v=1.1 cv=Mv9Cy8NsQItTEAHnXr6fCNbI23lcrkmyMeqLv9HU3yU= c=1 sm=1 a=yvU03qplA7IA:10 a=VCxxn1A5iYMA:10 a=wPDyFdB5xvgA:10 a=YBs1tj9y_9UA:10 a=8nJEP1OIZ-IA:10 a=4A50YBgeEUJTzIKlCdeDOQ==:17 a=SEF7xSSsAAAA:8 a=_d79F5ZRt9Uoh52VZ_IA:9 a=wPNLvfGTeEIA:10 a=4A50YBgeEUJTzIKlCdeDOQ==:117 Received: from localhost (unknown [127.0.0.1]) by mail.ark-net.org (Postfix) with ESMTP id ED5D820421; Fri, 7 Sep 2012 00:22:37 +0000 (UTC) X-Virus-Scanned: amavisd-new at ark-net.org Received: from mail.ark-net.org ([127.0.0.1]) by localhost (mail.ark-net.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id NSQ3LRMrsHxZ; Thu, 6 Sep 2012 20:22:12 -0400 (EDT) Received: from mikePC (unknown [192.168.1.35]) by mail.ark-net.org (Postfix) with ESMTP id 4DB5F20336; Thu, 6 Sep 2012 20:22:12 -0400 (EDT) From: "Michael A. Collins" To: =?iso-8859-1?Q?'Pasi_K=E4rkk=E4inen'?= References: <6035A0D088A63A46850C3988ED045A4B289D3F42@BITCOM1.int.sbss.com.au> <013501cd870d$10617740$312465c0$@ark-net.org> <20120906150653.GZ8912@reaktio.net> In-Reply-To: <20120906150653.GZ8912@reaktio.net> Date: Thu, 6 Sep 2012 20:22:57 -0400 Message-ID: <030d01cd8c8e$f13d8d40$d3b8a7c0$@ark-net.org> MIME-Version: 1.0 X-Mailer: Microsoft Outlook 14.0 Thread-Index: AQIRmcOIxnsUpbFnh+pVCjczJ/P8jwEwQnRKAWALQPSW4WD4AA== Content-Language: en-us Cc: 'James Harper' , xen-users@lists.xensource.com Subject: Re: [Xen-users] emulated rtl8139 driver, openvswitch, and offload X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org > -----Original Message----- > From: Pasi K=E4rkk=E4inen [mailto:pasik@iki.fi] > Sent: Thursday, September 06, 2012 11:07 AM > To: Michael A. Collins > Cc: 'James Harper'; xen-users@lists.xensource.com > Subject: Re: [Xen-users] emulated rtl8139 driver, openvswitch, and offload > = > On Thu, Aug 30, 2012 at 08:10:39PM -0400, Michael A. Collins wrote: > > James, > > I have not been able to reliably disable Large Send Offload, > > Checksum Offload and Scatter/Gather through the device manager GUI on > > Windows 2008 32bit/64bit with pv_drivers installed. The Xen Net > > Device Driver will fail to start and them the dom0 will panic and > > reboot. I am very scared to continue! This happened to me twice > > today while I was going through and disabling GSO/TSO/GRO on my > > broadcom bnx2 interfaces to fix a serious issue we have with > > inter-Host network traffic. Is there a way to do this that doesn't involve > crashing the dom0 and causing the whole box to reboot? > > Also, is there a guide to updating the drivers? I would like to > > install the latest 357 drivers, but the one time I tried uninstalling > > them I had a BSOD and had to reimage. > > > = > What dom0 kernel version are you using? Also what Xen version? > = > dom0 crashing when changing settings in the domU is a very serious bug! > = > = > -- Pasi > = Linux version: 3.5.0-rc2 Xen version: Xen 4.2 unstable changeset: 25467 I can test with a more recent version or Xen or the kernel this weekend. I can capture serial console logs and whatever else is needed. MIke _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Fri Sep 07 00:23:54 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Fri, 07 Sep 2012 00:23:54 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1T9mLG-0000dZ-6E; Fri, 07 Sep 2012 00:22:38 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1T9mLD-0000dU-VO for xen-users@lists.xensource.com; Fri, 07 Sep 2012 00:22:36 +0000 Received: from [85.158.143.99:42142] by server-2.bemta-4.messagelabs.com id 81/50-21239-B4E39405; Fri, 07 Sep 2012 00:22:35 +0000 X-Env-Sender: mike.a.collins@ark-net.org X-Msg-Ref: server-7.tower-216.messagelabs.com!1346977353!25637951!1 X-Originating-IP: [216.33.127.81] X-SpamReason: No, hits=0.0 required=7.0 tests= X-StarScan-Received: X-StarScan-Version: 6.6.1.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 31127 invoked from network); 7 Sep 2012 00:22:34 -0000 Received: from mta21.charter.net (HELO mta21.charter.net) (216.33.127.81) by server-7.tower-216.messagelabs.com with SMTP; 7 Sep 2012 00:22:34 -0000 Received: from imp11 ([10.20.200.11]) by mta21.charter.net (InterMail vM.8.01.05.02 201-2260-151-103-20110920) with ESMTP id <20120907002233.HCGO12025.mta21.charter.net@imp11>; Thu, 6 Sep 2012 20:22:33 -0400 Received: from mail.ark-net.org ([75.138.215.251]) by imp11 with smtp.charter.net id w0NY1j00a5S18aK050NZ7h; Thu, 06 Sep 2012 20:22:33 -0400 X-Authority-Analysis: v=1.1 cv=Mv9Cy8NsQItTEAHnXr6fCNbI23lcrkmyMeqLv9HU3yU= c=1 sm=1 a=yvU03qplA7IA:10 a=VCxxn1A5iYMA:10 a=wPDyFdB5xvgA:10 a=YBs1tj9y_9UA:10 a=8nJEP1OIZ-IA:10 a=4A50YBgeEUJTzIKlCdeDOQ==:17 a=SEF7xSSsAAAA:8 a=_d79F5ZRt9Uoh52VZ_IA:9 a=wPNLvfGTeEIA:10 a=4A50YBgeEUJTzIKlCdeDOQ==:117 Received: from localhost (unknown [127.0.0.1]) by mail.ark-net.org (Postfix) with ESMTP id ED5D820421; Fri, 7 Sep 2012 00:22:37 +0000 (UTC) X-Virus-Scanned: amavisd-new at ark-net.org Received: from mail.ark-net.org ([127.0.0.1]) by localhost (mail.ark-net.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id NSQ3LRMrsHxZ; Thu, 6 Sep 2012 20:22:12 -0400 (EDT) Received: from mikePC (unknown [192.168.1.35]) by mail.ark-net.org (Postfix) with ESMTP id 4DB5F20336; Thu, 6 Sep 2012 20:22:12 -0400 (EDT) From: "Michael A. Collins" To: =?iso-8859-1?Q?'Pasi_K=E4rkk=E4inen'?= References: <6035A0D088A63A46850C3988ED045A4B289D3F42@BITCOM1.int.sbss.com.au> <013501cd870d$10617740$312465c0$@ark-net.org> <20120906150653.GZ8912@reaktio.net> In-Reply-To: <20120906150653.GZ8912@reaktio.net> Date: Thu, 6 Sep 2012 20:22:57 -0400 Message-ID: <030d01cd8c8e$f13d8d40$d3b8a7c0$@ark-net.org> MIME-Version: 1.0 X-Mailer: Microsoft Outlook 14.0 Thread-Index: AQIRmcOIxnsUpbFnh+pVCjczJ/P8jwEwQnRKAWALQPSW4WD4AA== Content-Language: en-us Cc: 'James Harper' , xen-users@lists.xensource.com Subject: Re: [Xen-users] emulated rtl8139 driver, openvswitch, and offload X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org > -----Original Message----- > From: Pasi K=E4rkk=E4inen [mailto:pasik@iki.fi] > Sent: Thursday, September 06, 2012 11:07 AM > To: Michael A. Collins > Cc: 'James Harper'; xen-users@lists.xensource.com > Subject: Re: [Xen-users] emulated rtl8139 driver, openvswitch, and offload > = > On Thu, Aug 30, 2012 at 08:10:39PM -0400, Michael A. Collins wrote: > > James, > > I have not been able to reliably disable Large Send Offload, > > Checksum Offload and Scatter/Gather through the device manager GUI on > > Windows 2008 32bit/64bit with pv_drivers installed. The Xen Net > > Device Driver will fail to start and them the dom0 will panic and > > reboot. I am very scared to continue! This happened to me twice > > today while I was going through and disabling GSO/TSO/GRO on my > > broadcom bnx2 interfaces to fix a serious issue we have with > > inter-Host network traffic. Is there a way to do this that doesn't involve > crashing the dom0 and causing the whole box to reboot? > > Also, is there a guide to updating the drivers? I would like to > > install the latest 357 drivers, but the one time I tried uninstalling > > them I had a BSOD and had to reimage. > > > = > What dom0 kernel version are you using? Also what Xen version? > = > dom0 crashing when changing settings in the domU is a very serious bug! > = > = > -- Pasi > = Linux version: 3.5.0-rc2 Xen version: Xen 4.2 unstable changeset: 25467 I can test with a more recent version or Xen or the kernel this weekend. I can capture serial console logs and whatever else is needed. MIke _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Fri Sep 07 05:34:12 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Fri, 07 Sep 2012 05:34:12 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1T9rBY-00006S-Dx; Fri, 07 Sep 2012 05:32:56 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1T9rBX-000068-2f for xen-users@lists.xensource.com; Fri, 07 Sep 2012 05:32:55 +0000 Received: from [85.158.138.51:15157] by server-4.bemta-3.messagelabs.com id DE/BD-24831-60789405; Fri, 07 Sep 2012 05:32:54 +0000 X-Env-Sender: pasik@iki.fi X-Msg-Ref: server-5.tower-174.messagelabs.com!1346995973!29257939!1 X-Originating-IP: [192.89.123.25] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogMTkyLjg5LjEyMy4yNSA9PiA1MDU2NTM=\n X-StarScan-Received: X-StarScan-Version: 6.6.1.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 11379 invoked from network); 7 Sep 2012 05:32:53 -0000 Received: from smtp.tele.fi (HELO smtp.tele.fi) (192.89.123.25) by server-5.tower-174.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 7 Sep 2012 05:32:53 -0000 X-Originating-Ip: [194.89.68.22] Received: from ydin.reaktio.net (reaktio.net [194.89.68.22]) by smtp.tele.fi (Postfix) with ESMTP id 1D18319E8; Fri, 7 Sep 2012 08:32:51 +0300 (EEST) Received: by ydin.reaktio.net (Postfix, from userid 1001) id B081F2005D; Fri, 7 Sep 2012 08:32:51 +0300 (EEST) Date: Fri, 7 Sep 2012 08:32:51 +0300 From: Pasi =?iso-8859-1?Q?K=E4rkk=E4inen?= To: "Michael A. Collins" Message-ID: <20120907053251.GE8912@reaktio.net> References: <6035A0D088A63A46850C3988ED045A4B289D3F42@BITCOM1.int.sbss.com.au> <013501cd870d$10617740$312465c0$@ark-net.org> <20120906150653.GZ8912@reaktio.net> <030d01cd8c8e$f13d8d40$d3b8a7c0$@ark-net.org> MIME-Version: 1.0 Content-Disposition: inline In-Reply-To: <030d01cd8c8e$f13d8d40$d3b8a7c0$@ark-net.org> User-Agent: Mutt/1.5.20 (2009-06-14) Cc: 'James Harper' , xen-users@lists.xensource.com Subject: Re: [Xen-users] emulated rtl8139 driver, openvswitch, and offload X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org On Thu, Sep 06, 2012 at 08:22:57PM -0400, Michael A. Collins wrote: > > -----Original Message----- > > From: Pasi K=E4rkk=E4inen [mailto:pasik@iki.fi] > > Sent: Thursday, September 06, 2012 11:07 AM > > To: Michael A. Collins > > Cc: 'James Harper'; xen-users@lists.xensource.com > > Subject: Re: [Xen-users] emulated rtl8139 driver, openvswitch, and offl= oad > > = > > On Thu, Aug 30, 2012 at 08:10:39PM -0400, Michael A. Collins wrote: > > > James, > > > I have not been able to reliably disable Large Send Offload, > > > Checksum Offload and Scatter/Gather through the device manager GUI on > > > Windows 2008 32bit/64bit with pv_drivers installed. The Xen Net > > > Device Driver will fail to start and them the dom0 will panic and > > > reboot. I am very scared to continue! This happened to me twice > > > today while I was going through and disabling GSO/TSO/GRO on my > > > broadcom bnx2 interfaces to fix a serious issue we have with > > > inter-Host network traffic. Is there a way to do this that doesn't > involve > > crashing the dom0 and causing the whole box to reboot? > > > Also, is there a guide to updating the drivers? I would like to > > > install the latest 357 drivers, but the one time I tried uninstalling > > > them I had a BSOD and had to reimage. > > > > > = > > What dom0 kernel version are you using? Also what Xen version? > > = > > dom0 crashing when changing settings in the domU is a very serious bug! > > = > > = > > -- Pasi > > = > Linux version: 3.5.0-rc2 > Xen version: Xen 4.2 unstable changeset: 25467 > = > I can test with a more recent version or Xen or the kernel this weekend. = I > can capture serial console logs and whatever else is needed. > Make sure you update your Xen to latest version, and also your dom0 kernel to at least 3.5.3. -- Pasi _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Fri Sep 07 05:34:12 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Fri, 07 Sep 2012 05:34:12 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1T9rBY-00006S-Dx; Fri, 07 Sep 2012 05:32:56 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1T9rBX-000068-2f for xen-users@lists.xensource.com; Fri, 07 Sep 2012 05:32:55 +0000 Received: from [85.158.138.51:15157] by server-4.bemta-3.messagelabs.com id DE/BD-24831-60789405; Fri, 07 Sep 2012 05:32:54 +0000 X-Env-Sender: pasik@iki.fi X-Msg-Ref: server-5.tower-174.messagelabs.com!1346995973!29257939!1 X-Originating-IP: [192.89.123.25] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogMTkyLjg5LjEyMy4yNSA9PiA1MDU2NTM=\n X-StarScan-Received: X-StarScan-Version: 6.6.1.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 11379 invoked from network); 7 Sep 2012 05:32:53 -0000 Received: from smtp.tele.fi (HELO smtp.tele.fi) (192.89.123.25) by server-5.tower-174.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 7 Sep 2012 05:32:53 -0000 X-Originating-Ip: [194.89.68.22] Received: from ydin.reaktio.net (reaktio.net [194.89.68.22]) by smtp.tele.fi (Postfix) with ESMTP id 1D18319E8; Fri, 7 Sep 2012 08:32:51 +0300 (EEST) Received: by ydin.reaktio.net (Postfix, from userid 1001) id B081F2005D; Fri, 7 Sep 2012 08:32:51 +0300 (EEST) Date: Fri, 7 Sep 2012 08:32:51 +0300 From: Pasi =?iso-8859-1?Q?K=E4rkk=E4inen?= To: "Michael A. Collins" Message-ID: <20120907053251.GE8912@reaktio.net> References: <6035A0D088A63A46850C3988ED045A4B289D3F42@BITCOM1.int.sbss.com.au> <013501cd870d$10617740$312465c0$@ark-net.org> <20120906150653.GZ8912@reaktio.net> <030d01cd8c8e$f13d8d40$d3b8a7c0$@ark-net.org> MIME-Version: 1.0 Content-Disposition: inline In-Reply-To: <030d01cd8c8e$f13d8d40$d3b8a7c0$@ark-net.org> User-Agent: Mutt/1.5.20 (2009-06-14) Cc: 'James Harper' , xen-users@lists.xensource.com Subject: Re: [Xen-users] emulated rtl8139 driver, openvswitch, and offload X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org On Thu, Sep 06, 2012 at 08:22:57PM -0400, Michael A. Collins wrote: > > -----Original Message----- > > From: Pasi K=E4rkk=E4inen [mailto:pasik@iki.fi] > > Sent: Thursday, September 06, 2012 11:07 AM > > To: Michael A. Collins > > Cc: 'James Harper'; xen-users@lists.xensource.com > > Subject: Re: [Xen-users] emulated rtl8139 driver, openvswitch, and offl= oad > > = > > On Thu, Aug 30, 2012 at 08:10:39PM -0400, Michael A. Collins wrote: > > > James, > > > I have not been able to reliably disable Large Send Offload, > > > Checksum Offload and Scatter/Gather through the device manager GUI on > > > Windows 2008 32bit/64bit with pv_drivers installed. The Xen Net > > > Device Driver will fail to start and them the dom0 will panic and > > > reboot. I am very scared to continue! This happened to me twice > > > today while I was going through and disabling GSO/TSO/GRO on my > > > broadcom bnx2 interfaces to fix a serious issue we have with > > > inter-Host network traffic. Is there a way to do this that doesn't > involve > > crashing the dom0 and causing the whole box to reboot? > > > Also, is there a guide to updating the drivers? I would like to > > > install the latest 357 drivers, but the one time I tried uninstalling > > > them I had a BSOD and had to reimage. > > > > > = > > What dom0 kernel version are you using? Also what Xen version? > > = > > dom0 crashing when changing settings in the domU is a very serious bug! > > = > > = > > -- Pasi > > = > Linux version: 3.5.0-rc2 > Xen version: Xen 4.2 unstable changeset: 25467 > = > I can test with a more recent version or Xen or the kernel this weekend. = I > can capture serial console logs and whatever else is needed. > Make sure you update your Xen to latest version, and also your dom0 kernel to at least 3.5.3. -- Pasi _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Fri Sep 07 10:43:49 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Fri, 07 Sep 2012 10:43:49 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1T9w05-0007x3-RC; Fri, 07 Sep 2012 10:41:25 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1T9w04-0007wb-Fz for xen-users@lists.xen.org; Fri, 07 Sep 2012 10:41:24 +0000 Received: from [85.158.143.99:27931] by server-2.bemta-4.messagelabs.com id BF/E0-21239-15FC9405; Fri, 07 Sep 2012 10:41:21 +0000 X-Env-Sender: ianc@xenbits.xen.org X-Msg-Ref: server-7.tower-216.messagelabs.com!1347014470!25727106!1 X-Originating-IP: [50.57.168.107] X-SpamReason: No, hits=0.5 required=7.0 tests=BODY_RANDOM_LONG X-StarScan-Received: X-StarScan-Version: 6.6.1.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 15372 invoked from network); 7 Sep 2012 10:41:12 -0000 Received: from mail.xen.org (HELO mail.xen.org) (50.57.168.107) by server-7.tower-216.messagelabs.com with AES256-SHA encrypted SMTP; 7 Sep 2012 10:41:12 -0000 Received: from xenbits.xen.org ([50.57.170.242]) by mail.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1T9vzi-0003JO-5i; Fri, 07 Sep 2012 10:41:02 +0000 Received: from ianc by xenbits.xen.org with local (Exim 4.72) (envelope-from ) id 1T9vzh-0000k0-IX; Fri, 07 Sep 2012 10:41:01 +0000 Date: Fri, 07 Sep 2012 10:41:01 +0000 Message-Id: Content-Type: multipart/mixed; boundary="=separator"; charset="utf-8" Content-Transfer-Encoding: binary MIME-Version: 1.0 X-Mailer: MIME-tools 5.428 (Entity 5.428) To: xen-announce@lists.xen.org, xen-devel@lists.xen.org, xen-users@lists.xen.org, oss-security@lists.openwall.com From: Xen.org security team Cc: "Xen.org security team" Subject: [Xen-users] Xen Security Advisory 19 (CVE-2012-4411) - guest administrator can access qemu monitor console X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org --=separator Content-Type: text/plain; charset="utf-8" Content-Disposition: inline Content-Transfer-Encoding: 7bit -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Xen Security Advisory CVE-2012-4411 / XSA-19 version 2 guest administrator can access qemu monitor console UPDATES IN VERSION 2 ==================== We have now been issued with a CVE number. ISSUE DESCRIPTION ================= A guest administrator who is granted access to the graphical console of a Xen guest can access the qemu monitor. The monitor can be used to access host resources. IMPACT ====== A malicious guest administrator can access host resources (perhaps belonging to other guests or the underlying system) and may be able to escalate their privilege to that of the host. VULNERABLE SYSTEMS ================== Installations where guest administrators do not have access to a domain's graphical console, or containing only PV domains configured without a graphical console, are not vulnerable. Installations where all guest administrators are trustworthy are not vulnerable, even if the guest operating systems themselves are untrusted. Systems using xend/xm: At least all versions since Xen 4.0 are affected. Systems are vulnerable even if "monitor=no" is specified in the xm domain configuration file - this configuration option is not properly honoured in the vulnerable versions. Systems using libxl/xl: All versions are affected. The "monitor=" option is not understood, and is therefore ignored, by xl. However, systems using the experimental device model version based on upstream qemu are NOT vulnerable; that is, Xen 4.2 RC systems with device_model_version="qemu_xen" specified in the xl domain config file. Systems using libvirt are vulnerable. For "xen:" URIs, see xend/xm, above. For "libxl:" URIs, all versions are affected. Systems based on the Xen Cloud Platform are NOT vulnerable. CONFIRMING VULNERABILITY ======================== Connect to the guest's VNC (or SDL) graphical display and make sure your focus is in that window. Hold down CTRL and ALT and press 2. You will see a black screen showing one of "serial0", "parallel0" or "QEMU monitor". Repeat this exercise for other digits 3 to 6. CTRL+ALT+1 is the domain's normal graphical console. Not all numbers will have screens attached, but note that you must release and re-press CTRL and ALT each time. If one of the accessible screens shows "QEMU monitor" then you are vulnerable. Otherwise you are not. MITIGATION ========== With xl in Xen 4.1 and later, supplying the following config option in the VM configuration file will disable the monitor: device_model_args=["-monitor","null"] With xend the following config option will disable the monitor: monitor_path="null" Note that with a vulnerable version of the software specifying "monitor=0" will NOT disable the monitor. We are not currently aware of the availability of mitigation for systems using libvirt. NOTE REGARDING EMBARGO ====================== This issue was publicly discussed online by its discoverer. There is therefore no embargo. RESOLUTION ========== The attached patch against qemu-xen-traditional (qemu-xen-4.*-testing.git) resolves this issue. $ sha256sum xsa19-qemu-all.patch 19fc5ff9334e7e7ad429388850dc6e52e7062c21a677082e7a89c2f2c91365fa xsa19-qemu-all.patch -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.10 (GNU/Linux) iQEcBAEBAgAGBQJQSc6yAAoJEIP+FMlX6CvZ3MMIAJ3BfY4EXmye0ucZKU2zsrNx R9w3AXdZWywf9qWX9DvgnJ0r4v/1wukqYwqpShAYNRHnbc3M15/ipEyLZDS2L4I2 On2mcaQeFAx5xIesRAaggyr4mQLoafCZxQO1ADPEIoyX97BBCJB85AjY5ctuoRX7 vDIUCwcXENsSVoDu3jJxqwwvbLbR7CA//V6RmCCIV9JKqcAdnrCTbRnoC7auDBzq rbEqf9yyW2Md9Dul6S6j5RUim0CT7dJ7LlEbjRoyiDleHrK1T5UlfxHaCGhGa/ud YRkW34PogsB1/boOi6T03Eir7svNNfN46ZS8Y+Pf6Dkv765BabIKwhhl7idIDUM= =ayT8 -----END PGP SIGNATURE----- --=separator Content-Type: application/octet-stream; name="xsa19-qemu-all.patch" Content-Disposition: attachment; filename="xsa19-qemu-all.patch" Content-Transfer-Encoding: base64 RnJvbTogSWFuIEphY2tzb24gPGlhbi5qYWNrc29uQGV1LmNpdHJpeC5jb20+ CgpEaXNhYmxlIHFlbXUgbW9uaXRvciBieSBkZWZhdWx0LiAgVGhlIHFlbXUg bW9uaXRvciBpcyBhbiBvdmVybHkKcG93ZXJmdWwgZmVhdHVyZSB3aGljaCBt dXN0IGJlIHByb3RlY3RlZCBmcm9tIHVudHJ1c3RlZCAoZ3Vlc3QpCmFkbWlu aXN0cmF0b3JzLgoKTmVpdGhlciB4bCBub3IgeGVuZCBleHBlY3QgcWVtdSB0 byBwcm9kdWNlIHRoaXMgbW9uaXRvciB1bmxlc3MgaXQgaXMKZXhwbGljaXRs eSByZXF1ZXN0ZWQuCgpUaGlzIGlzIGEgc2VjdXJpdHkgcHJvYmxlbSwgWFNB LTE5LiAgUHJldmlvdXNseSBpdCB3YXMgQ1ZFLTIwMDctMDk5OAppbiBSZWQg SGF0IGJ1dCB3ZSBoYXZlbid0IGRlYWx0IHdpdGggaXQgaW4gdXBzdHJlYW0u ICBXZSBob3BlIHRvIGhhdmUKYSBuZXcgQ1ZFIGZvciBpdCBoZXJlIGJ1dCB3 ZSBkb24ndCBoYXZlIG9uZSB5ZXQuCgpTaWduZWQtb2ZmLWJ5OiBJYW4gSmFj a3NvbiA8aWFuLmphY2tzb25AZXUuY2l0cml4LmNvbT4KCmRpZmYgLS1naXQg YS92bC5jIGIvdmwuYwppbmRleCBkMzBjYjJjLi5kMjFjM2FhIDEwMDY0NAot LS0gYS92bC5jCisrKyBiL3ZsLmMKQEAgLTQ5MjAsNyArNDkyMCw3IEBAIGlu dCBtYWluKGludCBhcmdjLCBjaGFyICoqYXJndiwgY2hhciAqKmVudnApCiAg ICAga2VybmVsX2NtZGxpbmUgPSAiIjsKICAgICBjeWxzID0gaGVhZHMgPSBz ZWNzID0gMDsKICAgICB0cmFuc2xhdGlvbiA9IEJJT1NfQVRBX1RSQU5TTEFU SU9OX0FVVE87Ci0gICAgbW9uaXRvcl9kZXZpY2UgPSAidmM6ODBDeDI0QyI7 CisgICAgbW9uaXRvcl9kZXZpY2UgPSAibnVsbCI7CiAKICAgICBzZXJpYWxf ZGV2aWNlc1swXSA9ICJ2Yzo4MEN4MjRDIjsKICAgICBmb3IoaSA9IDE7IGkg PCBNQVhfU0VSSUFMX1BPUlRTOyBpKyspCg== --=separator Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users --=separator-- From xen-users-bounces@lists.xen.org Fri Sep 07 10:43:49 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Fri, 07 Sep 2012 10:43:49 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1T9w05-0007x3-RC; Fri, 07 Sep 2012 10:41:25 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1T9w04-0007wb-Fz for xen-users@lists.xen.org; Fri, 07 Sep 2012 10:41:24 +0000 Received: from [85.158.143.99:27931] by server-2.bemta-4.messagelabs.com id BF/E0-21239-15FC9405; Fri, 07 Sep 2012 10:41:21 +0000 X-Env-Sender: ianc@xenbits.xen.org X-Msg-Ref: server-7.tower-216.messagelabs.com!1347014470!25727106!1 X-Originating-IP: [50.57.168.107] X-SpamReason: No, hits=0.5 required=7.0 tests=BODY_RANDOM_LONG X-StarScan-Received: X-StarScan-Version: 6.6.1.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 15372 invoked from network); 7 Sep 2012 10:41:12 -0000 Received: from mail.xen.org (HELO mail.xen.org) (50.57.168.107) by server-7.tower-216.messagelabs.com with AES256-SHA encrypted SMTP; 7 Sep 2012 10:41:12 -0000 Received: from xenbits.xen.org ([50.57.170.242]) by mail.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1T9vzi-0003JO-5i; Fri, 07 Sep 2012 10:41:02 +0000 Received: from ianc by xenbits.xen.org with local (Exim 4.72) (envelope-from ) id 1T9vzh-0000k0-IX; Fri, 07 Sep 2012 10:41:01 +0000 Date: Fri, 07 Sep 2012 10:41:01 +0000 Message-Id: Content-Type: multipart/mixed; boundary="=separator"; charset="utf-8" Content-Transfer-Encoding: binary MIME-Version: 1.0 X-Mailer: MIME-tools 5.428 (Entity 5.428) To: xen-announce@lists.xen.org, xen-devel@lists.xen.org, xen-users@lists.xen.org, oss-security@lists.openwall.com From: Xen.org security team Cc: "Xen.org security team" Subject: [Xen-users] Xen Security Advisory 19 (CVE-2012-4411) - guest administrator can access qemu monitor console X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org --=separator Content-Type: text/plain; charset="utf-8" Content-Disposition: inline Content-Transfer-Encoding: 7bit -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Xen Security Advisory CVE-2012-4411 / XSA-19 version 2 guest administrator can access qemu monitor console UPDATES IN VERSION 2 ==================== We have now been issued with a CVE number. ISSUE DESCRIPTION ================= A guest administrator who is granted access to the graphical console of a Xen guest can access the qemu monitor. The monitor can be used to access host resources. IMPACT ====== A malicious guest administrator can access host resources (perhaps belonging to other guests or the underlying system) and may be able to escalate their privilege to that of the host. VULNERABLE SYSTEMS ================== Installations where guest administrators do not have access to a domain's graphical console, or containing only PV domains configured without a graphical console, are not vulnerable. Installations where all guest administrators are trustworthy are not vulnerable, even if the guest operating systems themselves are untrusted. Systems using xend/xm: At least all versions since Xen 4.0 are affected. Systems are vulnerable even if "monitor=no" is specified in the xm domain configuration file - this configuration option is not properly honoured in the vulnerable versions. Systems using libxl/xl: All versions are affected. The "monitor=" option is not understood, and is therefore ignored, by xl. However, systems using the experimental device model version based on upstream qemu are NOT vulnerable; that is, Xen 4.2 RC systems with device_model_version="qemu_xen" specified in the xl domain config file. Systems using libvirt are vulnerable. For "xen:" URIs, see xend/xm, above. For "libxl:" URIs, all versions are affected. Systems based on the Xen Cloud Platform are NOT vulnerable. CONFIRMING VULNERABILITY ======================== Connect to the guest's VNC (or SDL) graphical display and make sure your focus is in that window. Hold down CTRL and ALT and press 2. You will see a black screen showing one of "serial0", "parallel0" or "QEMU monitor". Repeat this exercise for other digits 3 to 6. CTRL+ALT+1 is the domain's normal graphical console. Not all numbers will have screens attached, but note that you must release and re-press CTRL and ALT each time. If one of the accessible screens shows "QEMU monitor" then you are vulnerable. Otherwise you are not. MITIGATION ========== With xl in Xen 4.1 and later, supplying the following config option in the VM configuration file will disable the monitor: device_model_args=["-monitor","null"] With xend the following config option will disable the monitor: monitor_path="null" Note that with a vulnerable version of the software specifying "monitor=0" will NOT disable the monitor. We are not currently aware of the availability of mitigation for systems using libvirt. NOTE REGARDING EMBARGO ====================== This issue was publicly discussed online by its discoverer. There is therefore no embargo. RESOLUTION ========== The attached patch against qemu-xen-traditional (qemu-xen-4.*-testing.git) resolves this issue. $ sha256sum xsa19-qemu-all.patch 19fc5ff9334e7e7ad429388850dc6e52e7062c21a677082e7a89c2f2c91365fa xsa19-qemu-all.patch -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.10 (GNU/Linux) iQEcBAEBAgAGBQJQSc6yAAoJEIP+FMlX6CvZ3MMIAJ3BfY4EXmye0ucZKU2zsrNx R9w3AXdZWywf9qWX9DvgnJ0r4v/1wukqYwqpShAYNRHnbc3M15/ipEyLZDS2L4I2 On2mcaQeFAx5xIesRAaggyr4mQLoafCZxQO1ADPEIoyX97BBCJB85AjY5ctuoRX7 vDIUCwcXENsSVoDu3jJxqwwvbLbR7CA//V6RmCCIV9JKqcAdnrCTbRnoC7auDBzq rbEqf9yyW2Md9Dul6S6j5RUim0CT7dJ7LlEbjRoyiDleHrK1T5UlfxHaCGhGa/ud YRkW34PogsB1/boOi6T03Eir7svNNfN46ZS8Y+Pf6Dkv765BabIKwhhl7idIDUM= =ayT8 -----END PGP SIGNATURE----- --=separator Content-Type: application/octet-stream; name="xsa19-qemu-all.patch" Content-Disposition: attachment; filename="xsa19-qemu-all.patch" Content-Transfer-Encoding: base64 RnJvbTogSWFuIEphY2tzb24gPGlhbi5qYWNrc29uQGV1LmNpdHJpeC5jb20+ CgpEaXNhYmxlIHFlbXUgbW9uaXRvciBieSBkZWZhdWx0LiAgVGhlIHFlbXUg bW9uaXRvciBpcyBhbiBvdmVybHkKcG93ZXJmdWwgZmVhdHVyZSB3aGljaCBt dXN0IGJlIHByb3RlY3RlZCBmcm9tIHVudHJ1c3RlZCAoZ3Vlc3QpCmFkbWlu aXN0cmF0b3JzLgoKTmVpdGhlciB4bCBub3IgeGVuZCBleHBlY3QgcWVtdSB0 byBwcm9kdWNlIHRoaXMgbW9uaXRvciB1bmxlc3MgaXQgaXMKZXhwbGljaXRs eSByZXF1ZXN0ZWQuCgpUaGlzIGlzIGEgc2VjdXJpdHkgcHJvYmxlbSwgWFNB LTE5LiAgUHJldmlvdXNseSBpdCB3YXMgQ1ZFLTIwMDctMDk5OAppbiBSZWQg SGF0IGJ1dCB3ZSBoYXZlbid0IGRlYWx0IHdpdGggaXQgaW4gdXBzdHJlYW0u ICBXZSBob3BlIHRvIGhhdmUKYSBuZXcgQ1ZFIGZvciBpdCBoZXJlIGJ1dCB3 ZSBkb24ndCBoYXZlIG9uZSB5ZXQuCgpTaWduZWQtb2ZmLWJ5OiBJYW4gSmFj a3NvbiA8aWFuLmphY2tzb25AZXUuY2l0cml4LmNvbT4KCmRpZmYgLS1naXQg YS92bC5jIGIvdmwuYwppbmRleCBkMzBjYjJjLi5kMjFjM2FhIDEwMDY0NAot LS0gYS92bC5jCisrKyBiL3ZsLmMKQEAgLTQ5MjAsNyArNDkyMCw3IEBAIGlu dCBtYWluKGludCBhcmdjLCBjaGFyICoqYXJndiwgY2hhciAqKmVudnApCiAg ICAga2VybmVsX2NtZGxpbmUgPSAiIjsKICAgICBjeWxzID0gaGVhZHMgPSBz ZWNzID0gMDsKICAgICB0cmFuc2xhdGlvbiA9IEJJT1NfQVRBX1RSQU5TTEFU SU9OX0FVVE87Ci0gICAgbW9uaXRvcl9kZXZpY2UgPSAidmM6ODBDeDI0QyI7 CisgICAgbW9uaXRvcl9kZXZpY2UgPSAibnVsbCI7CiAKICAgICBzZXJpYWxf ZGV2aWNlc1swXSA9ICJ2Yzo4MEN4MjRDIjsKICAgICBmb3IoaSA9IDE7IGkg PCBNQVhfU0VSSUFMX1BPUlRTOyBpKyspCg== --=separator Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users --=separator-- From xen-users-bounces@lists.xen.org Fri Sep 07 13:27:06 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Fri, 07 Sep 2012 13:27:06 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1T9yZN-00062a-15; Fri, 07 Sep 2012 13:26:01 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1T9yZK-00062T-TP for xen-users@lists.xen.org; Fri, 07 Sep 2012 13:25:59 +0000 Received: from [85.158.138.51:48899] by server-12.bemta-3.messagelabs.com id DC/71-10384-6E5F9405; Fri, 07 Sep 2012 13:25:58 +0000 X-Env-Sender: delentef@gmail.com X-Msg-Ref: server-3.tower-174.messagelabs.com!1347024356!21204993!1 X-Originating-IP: [209.85.214.173] X-SpamReason: No, hits=1.2 required=7.0 tests=HTML_10_20,HTML_MESSAGE, ML_RADAR_SPEW_LINKS_14,RCVD_BY_IP,spamassassin: X-StarScan-Received: X-StarScan-Version: 6.6.1.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 10168 invoked from network); 7 Sep 2012 13:25:57 -0000 Received: from mail-ob0-f173.google.com (HELO mail-ob0-f173.google.com) (209.85.214.173) by server-3.tower-174.messagelabs.com with RC4-SHA encrypted SMTP; 7 Sep 2012 13:25:57 -0000 Received: by obbta14 with SMTP id ta14so5692525obb.32 for ; Fri, 07 Sep 2012 06:25:55 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:date:message-id:subject:from:to:content-type; bh=A/OjaWv1YRBz8c0R8yLP69LQT4/8PGNuZwk/Djvs6jI=; b=gVQa+69z9Q5YFGYeOobbZ0TRdqDZ9PKg79FlkmRCyPvZTypETNq+buB5L8jZd4ZXMx qtj09dBEcCobPDe5IIcDYlDrdDoLfOj/UVAuLo73ytBRImUMJv79sDB49HIk0MiUScW5 0sCxCzfFajG0RNbXemwF4BthvVgutDlqgjFWN5i5c1Mze6W8vdlIMjq7dwoogZwR7hOi kB2PRgQ7GUwh43yMaCJLMWK7t1t49sn87u8UvS4wZFssV/9/SvuoB/Sk9Q4tDk5jZTYN R+bTtGKEiLrBWaCHfw171l9pYA5HCjPTxhUiSTp3O09y4LwIv8nT0OyO131OLjPy9VUp iWRQ== MIME-Version: 1.0 Received: by 10.60.7.104 with SMTP id i8mr5851589oea.31.1347024355818; Fri, 07 Sep 2012 06:25:55 -0700 (PDT) Received: by 10.60.65.74 with HTTP; Fri, 7 Sep 2012 06:25:55 -0700 (PDT) Date: Fri, 7 Sep 2012 15:25:55 +0200 Message-ID: From: Fabrice Delente To: xen-users@lists.xen.org Subject: [Xen-users] How to setup the keyboard map in the VNC server? X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============5142638479518911339==" Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org --===============5142638479518911339== Content-Type: multipart/alternative; boundary=e89a8fb1ef143b7c9a04c91c8cd2 --e89a8fb1ef143b7c9a04c91c8cd2 Content-Type: text/plain; charset=UTF-8 Hello. This is my first experience with Xen. I set up a machine to server as a Xen host, and am now in the process of installing a Windows XP guest. When I get to typing the Windows XP license key, my keyboard keys are all mangled (I have a french keyboard, but it seems to be in QWERTY in the VNC server, though some keys are not in the place they should be on a american keyboard). I haven't been able to find '4' or '6' but I need them to type the key... How can I change the keyboard layout for the VNC server? It is started in a guest.cfg file, with the line vfb = [ 'type=vnc,vnclisten=10.*.*.*,vncpasswd=********' ] Thanks! -- Fabrice DELENTE --e89a8fb1ef143b7c9a04c91c8cd2 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Hello.

This is my first experience with Xen.

I set up a machi= ne to server as a Xen host, and am now in the process of installing a Windo= ws XP guest.

When I get to typing the Windows XP license key, my key= board keys are all mangled (I have a french keyboard, but it seems to be in= QWERTY in the VNC server, though some keys are not in the place they shoul= d be on a american keyboard). I haven't been able to find '4' o= r '6' but I need them to type the key...

How can I change the keyboard layout for the VNC server? It is started = in a guest.cfg file, with the line

vfb =3D [ 'type=3Dvnc,vnclis= ten=3D10.*.*.*,vncpasswd=3D********' ]

Thanks!
=
--
Fabrice DELENTE
--e89a8fb1ef143b7c9a04c91c8cd2-- --===============5142638479518911339== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users --===============5142638479518911339==-- From xen-users-bounces@lists.xen.org Fri Sep 07 13:27:06 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Fri, 07 Sep 2012 13:27:06 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1T9yZN-00062a-15; Fri, 07 Sep 2012 13:26:01 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1T9yZK-00062T-TP for xen-users@lists.xen.org; Fri, 07 Sep 2012 13:25:59 +0000 Received: from [85.158.138.51:48899] by server-12.bemta-3.messagelabs.com id DC/71-10384-6E5F9405; Fri, 07 Sep 2012 13:25:58 +0000 X-Env-Sender: delentef@gmail.com X-Msg-Ref: server-3.tower-174.messagelabs.com!1347024356!21204993!1 X-Originating-IP: [209.85.214.173] X-SpamReason: No, hits=1.2 required=7.0 tests=HTML_10_20,HTML_MESSAGE, ML_RADAR_SPEW_LINKS_14,RCVD_BY_IP,spamassassin: X-StarScan-Received: X-StarScan-Version: 6.6.1.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 10168 invoked from network); 7 Sep 2012 13:25:57 -0000 Received: from mail-ob0-f173.google.com (HELO mail-ob0-f173.google.com) (209.85.214.173) by server-3.tower-174.messagelabs.com with RC4-SHA encrypted SMTP; 7 Sep 2012 13:25:57 -0000 Received: by obbta14 with SMTP id ta14so5692525obb.32 for ; Fri, 07 Sep 2012 06:25:55 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:date:message-id:subject:from:to:content-type; bh=A/OjaWv1YRBz8c0R8yLP69LQT4/8PGNuZwk/Djvs6jI=; b=gVQa+69z9Q5YFGYeOobbZ0TRdqDZ9PKg79FlkmRCyPvZTypETNq+buB5L8jZd4ZXMx qtj09dBEcCobPDe5IIcDYlDrdDoLfOj/UVAuLo73ytBRImUMJv79sDB49HIk0MiUScW5 0sCxCzfFajG0RNbXemwF4BthvVgutDlqgjFWN5i5c1Mze6W8vdlIMjq7dwoogZwR7hOi kB2PRgQ7GUwh43yMaCJLMWK7t1t49sn87u8UvS4wZFssV/9/SvuoB/Sk9Q4tDk5jZTYN R+bTtGKEiLrBWaCHfw171l9pYA5HCjPTxhUiSTp3O09y4LwIv8nT0OyO131OLjPy9VUp iWRQ== MIME-Version: 1.0 Received: by 10.60.7.104 with SMTP id i8mr5851589oea.31.1347024355818; Fri, 07 Sep 2012 06:25:55 -0700 (PDT) Received: by 10.60.65.74 with HTTP; Fri, 7 Sep 2012 06:25:55 -0700 (PDT) Date: Fri, 7 Sep 2012 15:25:55 +0200 Message-ID: From: Fabrice Delente To: xen-users@lists.xen.org Subject: [Xen-users] How to setup the keyboard map in the VNC server? X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============5142638479518911339==" Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org --===============5142638479518911339== Content-Type: multipart/alternative; boundary=e89a8fb1ef143b7c9a04c91c8cd2 --e89a8fb1ef143b7c9a04c91c8cd2 Content-Type: text/plain; charset=UTF-8 Hello. This is my first experience with Xen. I set up a machine to server as a Xen host, and am now in the process of installing a Windows XP guest. When I get to typing the Windows XP license key, my keyboard keys are all mangled (I have a french keyboard, but it seems to be in QWERTY in the VNC server, though some keys are not in the place they should be on a american keyboard). I haven't been able to find '4' or '6' but I need them to type the key... How can I change the keyboard layout for the VNC server? It is started in a guest.cfg file, with the line vfb = [ 'type=vnc,vnclisten=10.*.*.*,vncpasswd=********' ] Thanks! -- Fabrice DELENTE --e89a8fb1ef143b7c9a04c91c8cd2 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Hello.

This is my first experience with Xen.

I set up a machi= ne to server as a Xen host, and am now in the process of installing a Windo= ws XP guest.

When I get to typing the Windows XP license key, my key= board keys are all mangled (I have a french keyboard, but it seems to be in= QWERTY in the VNC server, though some keys are not in the place they shoul= d be on a american keyboard). I haven't been able to find '4' o= r '6' but I need them to type the key...

How can I change the keyboard layout for the VNC server? It is started = in a guest.cfg file, with the line

vfb =3D [ 'type=3Dvnc,vnclis= ten=3D10.*.*.*,vncpasswd=3D********' ]

Thanks!
=
--
Fabrice DELENTE
--e89a8fb1ef143b7c9a04c91c8cd2-- --===============5142638479518911339== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users --===============5142638479518911339==-- From xen-users-bounces@lists.xen.org Fri Sep 07 14:32:05 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Fri, 07 Sep 2012 14:32:05 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1T9za2-000097-Ao; Fri, 07 Sep 2012 14:30:46 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1T9zIu-0007oN-Od for xen-users@lists.xen.org; Fri, 07 Sep 2012 14:13:04 +0000 Received: from [85.158.143.35:23227] by server-1.bemta-4.messagelabs.com id F3/D4-12504-0F00A405; Fri, 07 Sep 2012 14:13:04 +0000 X-Env-Sender: Artem.Metra@gmx.de X-Msg-Ref: server-9.tower-21.messagelabs.com!1347027180!6143809!1 X-Originating-IP: [213.165.64.23] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogMjEzLjE2NS42NC4yMyA9PiAyMzAxNjQ=\n, ML_RADAR_SPEW_LINKS_14,spamassassin: X-StarScan-Received: X-StarScan-Version: 6.6.1.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 14789 invoked from network); 7 Sep 2012 14:13:01 -0000 Received: from mailout-de.gmx.net (HELO mailout-de.gmx.net) (213.165.64.23) by server-9.tower-21.messagelabs.com with SMTP; 7 Sep 2012 14:13:01 -0000 Received: (qmail 2031 invoked by uid 0); 7 Sep 2012 14:13:00 -0000 Received: from 129.217.43.51 by www027.gmx.net with HTTP; Fri, 07 Sep 2012 16:12:58 +0200 (CEST) Date: Fri, 07 Sep 2012 16:12:58 +0200 From: "Artem Metra" Message-ID: <20120907141258.237920@gmx.net> MIME-Version: 1.0 To: xen-users@lists.xen.org X-Authenticated: #142584949 X-Flags: 0001 X-Mailer: WWW-Mail 6100 (Global Message Exchange) X-Priority: 3 X-Provags-ID: V01U2FsdGVkX19EXlssUaVENjNARtlxaqi5637JlLD1cXXjxNXOxn kWg/b8HyLc+mlDTbd07k0VVkUdWDgcVP1HUQ== X-GMX-UID: vWU4cJQ9eSEqbRTPFHwhtdx+IGRvb8CM X-Mailman-Approved-At: Fri, 07 Sep 2012 14:30:44 +0000 Subject: [Xen-users] Fast Network Bridge X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org Hi, I'm working a lot with xen and migration. Now I switched to Xen 4.2 which is really nice. But there is one big problem. A performence issue. I used Xen 4.1 with a networkbridge by using the following line in the vm-config: vif = [ "bridge=eth0,script=vif-bridge" ] In Xen 4.2 this is not possible anymore so that i have entered the following in my /etc/network/interfaces: # This file describes the network interfaces available on your system # and how to activate them. For more information, see interfaces(5). # The loopback network interface auto lo iface lo inet loopback auto xenbr1 iface xenbr1 inet dhcp bridge_ports eth0 And used the bridge by entering this in the vm-config: vif = [ "bridge=xenbr1" ] Using the same system und software with xen 4.1 a live migration has 400 milliseconds network downtime. With Xen 4.2 the network downtime is 5 seconds!!! I tested it by sending udp pakages from the vm to another pc every ms. Big delays are the network downtime. Does anybody see my fault or is xen 4.2 slower in this kind of work. Best regards _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Fri Sep 07 14:32:05 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Fri, 07 Sep 2012 14:32:05 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1T9za2-000097-Ao; Fri, 07 Sep 2012 14:30:46 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1T9zIu-0007oN-Od for xen-users@lists.xen.org; Fri, 07 Sep 2012 14:13:04 +0000 Received: from [85.158.143.35:23227] by server-1.bemta-4.messagelabs.com id F3/D4-12504-0F00A405; Fri, 07 Sep 2012 14:13:04 +0000 X-Env-Sender: Artem.Metra@gmx.de X-Msg-Ref: server-9.tower-21.messagelabs.com!1347027180!6143809!1 X-Originating-IP: [213.165.64.23] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogMjEzLjE2NS42NC4yMyA9PiAyMzAxNjQ=\n, ML_RADAR_SPEW_LINKS_14,spamassassin: X-StarScan-Received: X-StarScan-Version: 6.6.1.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 14789 invoked from network); 7 Sep 2012 14:13:01 -0000 Received: from mailout-de.gmx.net (HELO mailout-de.gmx.net) (213.165.64.23) by server-9.tower-21.messagelabs.com with SMTP; 7 Sep 2012 14:13:01 -0000 Received: (qmail 2031 invoked by uid 0); 7 Sep 2012 14:13:00 -0000 Received: from 129.217.43.51 by www027.gmx.net with HTTP; Fri, 07 Sep 2012 16:12:58 +0200 (CEST) Date: Fri, 07 Sep 2012 16:12:58 +0200 From: "Artem Metra" Message-ID: <20120907141258.237920@gmx.net> MIME-Version: 1.0 To: xen-users@lists.xen.org X-Authenticated: #142584949 X-Flags: 0001 X-Mailer: WWW-Mail 6100 (Global Message Exchange) X-Priority: 3 X-Provags-ID: V01U2FsdGVkX19EXlssUaVENjNARtlxaqi5637JlLD1cXXjxNXOxn kWg/b8HyLc+mlDTbd07k0VVkUdWDgcVP1HUQ== X-GMX-UID: vWU4cJQ9eSEqbRTPFHwhtdx+IGRvb8CM X-Mailman-Approved-At: Fri, 07 Sep 2012 14:30:44 +0000 Subject: [Xen-users] Fast Network Bridge X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org Hi, I'm working a lot with xen and migration. Now I switched to Xen 4.2 which is really nice. But there is one big problem. A performence issue. I used Xen 4.1 with a networkbridge by using the following line in the vm-config: vif = [ "bridge=eth0,script=vif-bridge" ] In Xen 4.2 this is not possible anymore so that i have entered the following in my /etc/network/interfaces: # This file describes the network interfaces available on your system # and how to activate them. For more information, see interfaces(5). # The loopback network interface auto lo iface lo inet loopback auto xenbr1 iface xenbr1 inet dhcp bridge_ports eth0 And used the bridge by entering this in the vm-config: vif = [ "bridge=xenbr1" ] Using the same system und software with xen 4.1 a live migration has 400 milliseconds network downtime. With Xen 4.2 the network downtime is 5 seconds!!! I tested it by sending udp pakages from the vm to another pc every ms. Big delays are the network downtime. Does anybody see my fault or is xen 4.2 slower in this kind of work. Best regards _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Fri Sep 07 14:38:52 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Fri, 07 Sep 2012 14:38:52 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1T9zgf-0000gi-01; Fri, 07 Sep 2012 14:37:37 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1T9zgd-0000gc-H0 for xen-users@lists.xen.org; Fri, 07 Sep 2012 14:37:35 +0000 Received: from [85.158.143.35:26123] by server-3.bemta-4.messagelabs.com id A1/D2-08232-EA60A405; Fri, 07 Sep 2012 14:37:34 +0000 X-Env-Sender: Ian.Campbell@citrix.com X-Msg-Ref: server-9.tower-21.messagelabs.com!1347028654!6148153!1 X-Originating-IP: [62.200.22.115] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogNjIuMjAwLjIyLjExNSA9PiAxMTIyMTE=\n X-StarScan-Received: X-StarScan-Version: 6.6.1.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 16754 invoked from network); 7 Sep 2012 14:37:34 -0000 Received: from smtp.ctxuk.citrix.com (HELO SMTP.EU.CITRIX.COM) (62.200.22.115) by server-9.tower-21.messagelabs.com with RC4-SHA encrypted SMTP; 7 Sep 2012 14:37:34 -0000 X-IronPort-AV: E=Sophos;i="4.80,387,1344211200"; d="scan'208";a="14412484" Received: from lonpmailmx01.citrite.net ([10.30.203.162]) by LONPIPO01.EU.CITRIX.COM with ESMTP/TLS/RC4-MD5; 07 Sep 2012 14:37:33 +0000 Received: from [10.80.2.42] (10.80.2.42) by LONPMAILMX01.citrite.net (10.30.203.162) with Microsoft SMTP Server id 8.3.279.1; Fri, 7 Sep 2012 15:37:33 +0100 Message-ID: <1347028652.30018.112.camel@zakaz.uk.xensource.com> From: Ian Campbell To: Artem Metra Date: Fri, 7 Sep 2012 15:37:32 +0100 In-Reply-To: <20120907141258.237920@gmx.net> References: <20120907141258.237920@gmx.net> Organization: Citrix Systems, Inc. X-Mailer: Evolution 3.4.3-1 MIME-Version: 1.0 Cc: "xen-users@lists.xen.org" Subject: Re: [Xen-users] Fast Network Bridge X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org On Fri, 2012-09-07 at 15:12 +0100, Artem Metra wrote: > Using the same system und software with xen 4.1 a live migration has > 400 milliseconds network downtime. With Xen 4.2 the network downtime > is 5 seconds!!! 5 seconds sounds like an STP forwarding delay. http://wiki.xen.org/wiki/Network_Configuration_Examples_%28Xen_4.1%2B%29 lists a few useful options (under "Some other useful options to use in any stanza in a virtualised environment are:") in this regard. Ian. _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Fri Sep 07 14:38:52 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Fri, 07 Sep 2012 14:38:52 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1T9zgf-0000gi-01; Fri, 07 Sep 2012 14:37:37 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1T9zgd-0000gc-H0 for xen-users@lists.xen.org; Fri, 07 Sep 2012 14:37:35 +0000 Received: from [85.158.143.35:26123] by server-3.bemta-4.messagelabs.com id A1/D2-08232-EA60A405; Fri, 07 Sep 2012 14:37:34 +0000 X-Env-Sender: Ian.Campbell@citrix.com X-Msg-Ref: server-9.tower-21.messagelabs.com!1347028654!6148153!1 X-Originating-IP: [62.200.22.115] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogNjIuMjAwLjIyLjExNSA9PiAxMTIyMTE=\n X-StarScan-Received: X-StarScan-Version: 6.6.1.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 16754 invoked from network); 7 Sep 2012 14:37:34 -0000 Received: from smtp.ctxuk.citrix.com (HELO SMTP.EU.CITRIX.COM) (62.200.22.115) by server-9.tower-21.messagelabs.com with RC4-SHA encrypted SMTP; 7 Sep 2012 14:37:34 -0000 X-IronPort-AV: E=Sophos;i="4.80,387,1344211200"; d="scan'208";a="14412484" Received: from lonpmailmx01.citrite.net ([10.30.203.162]) by LONPIPO01.EU.CITRIX.COM with ESMTP/TLS/RC4-MD5; 07 Sep 2012 14:37:33 +0000 Received: from [10.80.2.42] (10.80.2.42) by LONPMAILMX01.citrite.net (10.30.203.162) with Microsoft SMTP Server id 8.3.279.1; Fri, 7 Sep 2012 15:37:33 +0100 Message-ID: <1347028652.30018.112.camel@zakaz.uk.xensource.com> From: Ian Campbell To: Artem Metra Date: Fri, 7 Sep 2012 15:37:32 +0100 In-Reply-To: <20120907141258.237920@gmx.net> References: <20120907141258.237920@gmx.net> Organization: Citrix Systems, Inc. X-Mailer: Evolution 3.4.3-1 MIME-Version: 1.0 Cc: "xen-users@lists.xen.org" Subject: Re: [Xen-users] Fast Network Bridge X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org On Fri, 2012-09-07 at 15:12 +0100, Artem Metra wrote: > Using the same system und software with xen 4.1 a live migration has > 400 milliseconds network downtime. With Xen 4.2 the network downtime > is 5 seconds!!! 5 seconds sounds like an STP forwarding delay. http://wiki.xen.org/wiki/Network_Configuration_Examples_%28Xen_4.1%2B%29 lists a few useful options (under "Some other useful options to use in any stanza in a virtualised environment are:") in this regard. Ian. _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Fri Sep 07 19:35:15 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Fri, 07 Sep 2012 19:35:15 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TA4JP-0002C9-QY; Fri, 07 Sep 2012 19:33:55 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TA4JN-0002Bx-QP for xen-users@lists.xen.org; Fri, 07 Sep 2012 19:33:54 +0000 Received: from [85.158.143.99:4257] by server-2.bemta-4.messagelabs.com id 6E/5E-21239-12C4A405; Fri, 07 Sep 2012 19:33:53 +0000 X-Env-Sender: nathan@gt.net X-Msg-Ref: server-6.tower-216.messagelabs.com!1347046429!22165346!1 X-Originating-IP: [208.70.244.21] X-SpamReason: No, hits=1.1 required=7.0 tests=BODY_RANDOM_LONG, HTML_40_50,HTML_MESSAGE X-StarScan-Received: X-StarScan-Version: 6.6.1.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 19594 invoked from network); 7 Sep 2012 19:33:51 -0000 Received: from gossamer.nmsrv.com (HELO gossamer.nmsrv.com) (208.70.244.21) by server-6.tower-216.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 7 Sep 2012 19:33:51 -0000 DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=gt.net; h=from:to:subject :cc:date:content-type:in-reply-to:message-id:mime-version :reply-to; s=mail; bh=b90i7uN2i9o2+wIG6MIdi8KrZns=; b=iBqchG4wFw pa4bU908XT0bizkXD2QxYbgzEa16lJCTkD6Dj74ddVqXxOgsaW7PnMFfikkc8lEv d2YZc21UwWrZtp26qxG9zqZL4I0AgDRp74qEoenytZ7EwREJu2LdXogWVXhiJlwB uybypho9cYOgtoEvtX5NIPFE+KVTI9q+4= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gt.net; h=from:to:subject:cc :date:content-type:in-reply-to:message-id:mime-version:reply-to; q=dns; s=mail; b=TCPqKQn7vG+NNnDgw1PoKboCnibOotDHx+lZo39bsMmv7X kfYWVGrnv7CoJKUV0xe3X0JeGFjGIYCaTqo5VQqYlpDC0MZ4cZjr9djYtb7ELQpR ZZae1Hrcntr/fSJZzT+AaSLBU37bIgq7QvoxzDBG4gJm82AvAq5e9YqpzEweU= Received: (qmail 24889 invoked from network); 7 Sep 2012 19:33:48 -0000 X-AntiVirus: Clean Received: from gateway.gossamer-threads.com (HELO ?192.168.1.152?) (nathan@gt.net@208.70.247.145) by gossamer.nmsrv.com with ESMTPSA (AES128-SHA encrypted); 7 Sep 2012 19:33:48 -0000 From: "Nathan March" To: "Xen.org security team" , xen-devel@lists.xen.org, xen-users@lists.xen.org, oss-security@lists.openwall.com Date: Fri, 07 Sep 2012 19:33:42 +0000 In-Reply-To: Message-Id: Mime-Version: 1.0 User-Agent: eM_Client/4.0.15145.0 Cc: "Xen.org security team" Subject: Re: [Xen-users] Xen Security Advisory 17 (CVE-2012-3515) - Qemu VT100 emulation vulnerability X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list Reply-To: Nathan March List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============3863741412607480835==" Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org --===============3863741412607480835== Content-Type: multipart/alternative; boundary="------=_MB49CA08F0-682A-4135-A2F6-956DD7751BF1" --------=_MB49CA08F0-682A-4135-A2F6-956DD7751BF1 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; format=flowed; charset=utf-8 =EF=BB=BFHi All, I'm guessing this wasn't intentional, but the patch for xsa17 does not=20 contain a complete path to the tools/ioemu-qemu-xen/ path: --- a/console.c +++ b/console.c Compared to all the other patches which provide a full path to the=20 patched file: --- a/xen/include/asm-x86/debugreg.h Mon Aug 06 12:28:03 2012 +0100 +++ b/xen/include/asm-x86/debugreg.h Wed Aug 15 12:00:21 2012 +0100 Little annoying since it means you have to track down which console.c=20 is being patched instead of just applying from the root xen build dir. - Nathan ------ Original Message ------ From: "Xen.org security team" To:=20 xen-announce@lists.xen.org;xen-devel@lists.xen.org;xen-users@lists.xen.org;= oss-security@lists.openwall.com Cc: "Xen.org security team" Sent: 9/5/2012 4:12:47 AM Subject: [Xen-users] Xen Security Advisory 17 (CVE-2012-3515) - Qemu=20 VT100 emulation vulnerability >-----BEGIN PGP SIGNED MESSAGE----- >Hash: SHA1 > > Xen Security Advisory CVE-2012-3515 / XSA-17 > version 2 > > Qemu VT100 emulation vulnerability > >UPDATES IN VERSION 2 >=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D > >Public release. > >ISSUE DESCRIPTION >=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D > >The device model used by fully virtualised (HVM) domains, qemu, does >not properly handle escape VT100 sequences when emulating certain >devices with a virtual console backend. > >IMPACT >=3D=3D=3D=3D=3D=3D > >An attacker who has sufficient privilege to access a vulnerable device >within a guest can overwrite portions of the device model's address >space. This can allow them to escalate their privileges to that of the >device model process. > >VULNERABLE SYSTEMS >=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D > >All Xen systems running HVM guests are potentially vulnerable to this >depending on the specific guest configuration. The default >configuration is vulnerable. > >Guests using either the traditional "qemu-xen" or upstream qemu device >models are vulnerable. > >MITIGATION >=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D > >This issue can be avoided by only running PV guests or by configuring >HVM guests to not use the virtual console('vc') backend for any device. > >For serial devices specify in your guest configuration: > serial =3D 'none' >in your guest configuration. > >For parallel port devices the syntax is toolstack specific. >For xend specify in your guest configuration: > parallel =3D 'none' >For xl specify in your guest configuration: > xl: device_model_args =3D ['-parallel', 'none'] > >In both cases the default is to use the vulnerable 'vc' mode. > >You can confirm whether or not you are vulnerable by pressing >Ctrl-Alt- (for digit N) while connected to either the VNC or SDL >console. If you are able to switch to a window displaying "serial" or >"parallel" then you are vulnerable. > >The issue can also be mitigated by enabling the stub domain device >model. In this case the attacked can only potentially gain control of >the stub domain and not of the entire system. > >To enable stub domains specify in your guest configuration: > device_model =3D "stubdom-dm" > >RESOLUTION >=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D > >Applying the appropriate attached patch(es) will resolve the issue. > >PATCH INFORMATION >=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D > >The attached patches resolve this issue > >Traditional qemu tree > Xen 4.0, 4.1 and unstable xsa17-qemu-xen-traditional-all.patch > >Upstream qemu tree (present in unstable only) > Xen unstable xsa17-qemu-xen-unstable.patch > >$ sha256sum xsa17-*.patch >60215322d3fbbc2054dfc160a20d9e0811af88487c4edc2f6ea81dcd5cedf039 xsa17-qe= mu-xen-traditional-all.patch >7b4bb59e7757080e7806a8b8eeb6b78fa0ffdfbfb28a7a379f7edff285bffd88 xsa17-qe= mu-xen-unstable.patch >-----BEGIN PGP SIGNATURE----- >Version: GnuPG v1.4.10 (GNU/Linux) > >iQEcBAEBAgAGBQJQRx1PAAoJEIP+FMlX6CvZUqUH/jeAAvQnoBp6YKzm78XSnnmk >GI2C/LhH0xqR3wFoEmWeMsiO4lrGrASX6T31NTvHa8sOtFqlNpTfRhwQybwYR3aa >cz9/4y2a54hD95P1nVmPF0PddmSP47QSpRdCj0projq1UGxIdwEhkNeSoM8h7dXO >MegqZClsvJMKd8XEcjBF5Qg7u9vLrXilCx5+It7XNE31Jxpkr/fozBb7FnNtDGJj >s4RN/UDU4Pu68XyZ7Dc5xEFdJW48tz4BIlxxXavILBRFSE1VEf7Gc8H9CsUtBPWB >C/LCUjpHkAOmqdgFhiLnZ2u+2s79U0dtPDJMNmqaGgWH+AqGkU9Nq8XXODTyY9k=3D >=3DgnuE >-----END PGP SIGNATURE----- > > --------=_MB49CA08F0-682A-4135-A2F6-956DD7751BF1 Content-Transfer-Encoding: quoted-printable Content-Type: text/html; charset=utf-8
Hi All,
 
I'm guessing this wasn't intentional, but the patch for xsa17 does = not contain a complete path to the tools/ioemu-qemu-xen/ path:
 
--- a/console.c
+++ b/console.c
 
Compared to all the other patches which provide a full path to the patched file:
 
--- a/xen/include/asm-x86/debugreg.h Mon Aug 06 12:28:03 2012 +0100+++ b/xen/include/asm-x86/debugreg.h Wed Aug 15 12:00:21 2012 +0100
 
Little annoying since it means you have to track down which console.c= is being patched instead of just applying from the root xen build dir.
 
- Nathan
 

------ Original Message ------
From: "Xen.org security team"= <security@xen.org>
To: xen-announce@lists.xen.org;xen-devel@lists= .xen.org;xen-users@lists.xen.org;oss-security@lists.openwall.com
Cc: = "Xen.org security team" <security@xen.org>
Sent: 9/5/2012 4:12:47= AM
Subject: [Xen-users] Xen Security Advisory 17 (CVE-2012-3515) - Qemu= VT100 emulation vulnerability
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

           Xen Secur=
ity Advisory CVE-2012-3515 / XSA-17
            &nb=
sp;            =
 version 2

            &nb=
sp; Qemu VT100 emulation vulnerability

UPDATES IN VERSION 2
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D

Public release.

ISSUE DESCRIPTION
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D

The device model used by fully virtualised (HVM) domains, qemu, does
not properly handle escape VT100 sequences when emulating certain
devices with a virtual console backend.

IMPACT
=3D=3D=3D=3D=3D=3D

An attacker who has sufficient privilege to access a vulnerable device
within a guest can overwrite portions of the device model's address
space. This can allow them to escalate their privileges to that of the
device model process.

VULNERABLE SYSTEMS
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D

All Xen systems running HVM guests are potentially vulnerable to this
depending on the specific guest configuration. The default
configuration is vulnerable.

Guests using either the traditional "qemu-xen" or upstream qemu device
models are vulnerable.

MITIGATION
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D

This issue can be avoided by only running PV guests or by configuring
HVM guests to not use the virtual console('vc') backend for any device.

For serial devices specify in your guest configuration:
    serial =3D 'none'
in your guest configuration.

For parallel port devices the syntax is toolstack specific.
For xend specify in your guest configuration:
    parallel =3D 'none'
For xl specify in your guest configuration:
    xl: device_model_args =3D ['-parallel', 'none']

In both cases the default is to use the vulnerable 'vc' mode.

You can confirm whether or not you are vulnerable by pressing
Ctrl-Alt-<N> (for digit N) while connected to either the VNC or SDL
console. If you are able to switch to a window displaying "serial" or
"parallel" then you are vulnerable.

The issue can also be mitigated by enabling the stub domain device
model. In this case the attacked can only potentially gain control of
the stub domain and not of the entire system.

To enable stub domains specify in your guest configuration:
   device_model =3D "stubdom-dm"

RESOLUTION
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D

Applying the appropriate attached patch(es) will resolve the issue.

PATCH INFORMATION
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D

The attached patches resolve this issue

Traditional qemu tree
  Xen 4.0, 4.1 and unstable         xsa17-qemu-xen-traditional-al=
l.patch

Upstream qemu tree (present in unstable only)
  Xen unstable                      xsa17-qemu-xen-unstable.patch

$ sha256sum xsa17-*.patch
60215322d3fbbc2054dfc160a20d9e0811af88487c4edc2f6ea81dcd5cedf039  xsa17-qem=
u-xen-traditional-all.patch
7b4bb59e7757080e7806a8b8eeb6b78fa0ffdfbfb28a7a379f7edff285bffd88  xsa17-qem=
u-xen-unstable.patch
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.10 (GNU/Linux)

iQEcBAEBAgAGBQJQRx1PAAoJEIP+FMlX6CvZUqUH/jeAAvQnoBp6YKzm78XSnnmk
GI2C/LhH0xqR3wFoEmWeMsiO4lrGrASX6T31NTvHa8sOtFqlNpTfRhwQybwYR3aa
cz9/4y2a54hD95P1nVmPF0PddmSP47QSpRdCj0projq1UGxIdwEhkNeSoM8h7dXO
MegqZClsvJMKd8XEcjBF5Qg7u9vLrXilCx5+It7XNE31Jxpkr/fozBb7FnNtDGJj
s4RN/UDU4Pu68XyZ7Dc5xEFdJW48tz4BIlxxXavILBRFSE1VEf7Gc8H9CsUtBPWB
C/LCUjpHkAOmqdgFhiLnZ2u+2s79U0dtPDJMNmqaGgWH+AqGkU9Nq8XXODTyY9k=3D
=3DgnuE
-----END PGP SIGNATURE-----
--------=_MB49CA08F0-682A-4135-A2F6-956DD7751BF1-- --===============3863741412607480835== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users --===============3863741412607480835==-- From xen-users-bounces@lists.xen.org Fri Sep 07 19:35:15 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Fri, 07 Sep 2012 19:35:15 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TA4JP-0002C9-QY; Fri, 07 Sep 2012 19:33:55 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TA4JN-0002Bx-QP for xen-users@lists.xen.org; Fri, 07 Sep 2012 19:33:54 +0000 Received: from [85.158.143.99:4257] by server-2.bemta-4.messagelabs.com id 6E/5E-21239-12C4A405; Fri, 07 Sep 2012 19:33:53 +0000 X-Env-Sender: nathan@gt.net X-Msg-Ref: server-6.tower-216.messagelabs.com!1347046429!22165346!1 X-Originating-IP: [208.70.244.21] X-SpamReason: No, hits=1.1 required=7.0 tests=BODY_RANDOM_LONG, HTML_40_50,HTML_MESSAGE X-StarScan-Received: X-StarScan-Version: 6.6.1.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 19594 invoked from network); 7 Sep 2012 19:33:51 -0000 Received: from gossamer.nmsrv.com (HELO gossamer.nmsrv.com) (208.70.244.21) by server-6.tower-216.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 7 Sep 2012 19:33:51 -0000 DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=gt.net; h=from:to:subject :cc:date:content-type:in-reply-to:message-id:mime-version :reply-to; s=mail; bh=b90i7uN2i9o2+wIG6MIdi8KrZns=; b=iBqchG4wFw pa4bU908XT0bizkXD2QxYbgzEa16lJCTkD6Dj74ddVqXxOgsaW7PnMFfikkc8lEv d2YZc21UwWrZtp26qxG9zqZL4I0AgDRp74qEoenytZ7EwREJu2LdXogWVXhiJlwB uybypho9cYOgtoEvtX5NIPFE+KVTI9q+4= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gt.net; h=from:to:subject:cc :date:content-type:in-reply-to:message-id:mime-version:reply-to; q=dns; s=mail; b=TCPqKQn7vG+NNnDgw1PoKboCnibOotDHx+lZo39bsMmv7X kfYWVGrnv7CoJKUV0xe3X0JeGFjGIYCaTqo5VQqYlpDC0MZ4cZjr9djYtb7ELQpR ZZae1Hrcntr/fSJZzT+AaSLBU37bIgq7QvoxzDBG4gJm82AvAq5e9YqpzEweU= Received: (qmail 24889 invoked from network); 7 Sep 2012 19:33:48 -0000 X-AntiVirus: Clean Received: from gateway.gossamer-threads.com (HELO ?192.168.1.152?) (nathan@gt.net@208.70.247.145) by gossamer.nmsrv.com with ESMTPSA (AES128-SHA encrypted); 7 Sep 2012 19:33:48 -0000 From: "Nathan March" To: "Xen.org security team" , xen-devel@lists.xen.org, xen-users@lists.xen.org, oss-security@lists.openwall.com Date: Fri, 07 Sep 2012 19:33:42 +0000 In-Reply-To: Message-Id: Mime-Version: 1.0 User-Agent: eM_Client/4.0.15145.0 Cc: "Xen.org security team" Subject: Re: [Xen-users] Xen Security Advisory 17 (CVE-2012-3515) - Qemu VT100 emulation vulnerability X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list Reply-To: Nathan March List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============3863741412607480835==" Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org --===============3863741412607480835== Content-Type: multipart/alternative; boundary="------=_MB49CA08F0-682A-4135-A2F6-956DD7751BF1" --------=_MB49CA08F0-682A-4135-A2F6-956DD7751BF1 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; format=flowed; charset=utf-8 =EF=BB=BFHi All, I'm guessing this wasn't intentional, but the patch for xsa17 does not=20 contain a complete path to the tools/ioemu-qemu-xen/ path: --- a/console.c +++ b/console.c Compared to all the other patches which provide a full path to the=20 patched file: --- a/xen/include/asm-x86/debugreg.h Mon Aug 06 12:28:03 2012 +0100 +++ b/xen/include/asm-x86/debugreg.h Wed Aug 15 12:00:21 2012 +0100 Little annoying since it means you have to track down which console.c=20 is being patched instead of just applying from the root xen build dir. - Nathan ------ Original Message ------ From: "Xen.org security team" To:=20 xen-announce@lists.xen.org;xen-devel@lists.xen.org;xen-users@lists.xen.org;= oss-security@lists.openwall.com Cc: "Xen.org security team" Sent: 9/5/2012 4:12:47 AM Subject: [Xen-users] Xen Security Advisory 17 (CVE-2012-3515) - Qemu=20 VT100 emulation vulnerability >-----BEGIN PGP SIGNED MESSAGE----- >Hash: SHA1 > > Xen Security Advisory CVE-2012-3515 / XSA-17 > version 2 > > Qemu VT100 emulation vulnerability > >UPDATES IN VERSION 2 >=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D > >Public release. > >ISSUE DESCRIPTION >=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D > >The device model used by fully virtualised (HVM) domains, qemu, does >not properly handle escape VT100 sequences when emulating certain >devices with a virtual console backend. > >IMPACT >=3D=3D=3D=3D=3D=3D > >An attacker who has sufficient privilege to access a vulnerable device >within a guest can overwrite portions of the device model's address >space. This can allow them to escalate their privileges to that of the >device model process. > >VULNERABLE SYSTEMS >=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D > >All Xen systems running HVM guests are potentially vulnerable to this >depending on the specific guest configuration. The default >configuration is vulnerable. > >Guests using either the traditional "qemu-xen" or upstream qemu device >models are vulnerable. > >MITIGATION >=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D > >This issue can be avoided by only running PV guests or by configuring >HVM guests to not use the virtual console('vc') backend for any device. > >For serial devices specify in your guest configuration: > serial =3D 'none' >in your guest configuration. > >For parallel port devices the syntax is toolstack specific. >For xend specify in your guest configuration: > parallel =3D 'none' >For xl specify in your guest configuration: > xl: device_model_args =3D ['-parallel', 'none'] > >In both cases the default is to use the vulnerable 'vc' mode. > >You can confirm whether or not you are vulnerable by pressing >Ctrl-Alt- (for digit N) while connected to either the VNC or SDL >console. If you are able to switch to a window displaying "serial" or >"parallel" then you are vulnerable. > >The issue can also be mitigated by enabling the stub domain device >model. In this case the attacked can only potentially gain control of >the stub domain and not of the entire system. > >To enable stub domains specify in your guest configuration: > device_model =3D "stubdom-dm" > >RESOLUTION >=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D > >Applying the appropriate attached patch(es) will resolve the issue. > >PATCH INFORMATION >=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D > >The attached patches resolve this issue > >Traditional qemu tree > Xen 4.0, 4.1 and unstable xsa17-qemu-xen-traditional-all.patch > >Upstream qemu tree (present in unstable only) > Xen unstable xsa17-qemu-xen-unstable.patch > >$ sha256sum xsa17-*.patch >60215322d3fbbc2054dfc160a20d9e0811af88487c4edc2f6ea81dcd5cedf039 xsa17-qe= mu-xen-traditional-all.patch >7b4bb59e7757080e7806a8b8eeb6b78fa0ffdfbfb28a7a379f7edff285bffd88 xsa17-qe= mu-xen-unstable.patch >-----BEGIN PGP SIGNATURE----- >Version: GnuPG v1.4.10 (GNU/Linux) > >iQEcBAEBAgAGBQJQRx1PAAoJEIP+FMlX6CvZUqUH/jeAAvQnoBp6YKzm78XSnnmk >GI2C/LhH0xqR3wFoEmWeMsiO4lrGrASX6T31NTvHa8sOtFqlNpTfRhwQybwYR3aa >cz9/4y2a54hD95P1nVmPF0PddmSP47QSpRdCj0projq1UGxIdwEhkNeSoM8h7dXO >MegqZClsvJMKd8XEcjBF5Qg7u9vLrXilCx5+It7XNE31Jxpkr/fozBb7FnNtDGJj >s4RN/UDU4Pu68XyZ7Dc5xEFdJW48tz4BIlxxXavILBRFSE1VEf7Gc8H9CsUtBPWB >C/LCUjpHkAOmqdgFhiLnZ2u+2s79U0dtPDJMNmqaGgWH+AqGkU9Nq8XXODTyY9k=3D >=3DgnuE >-----END PGP SIGNATURE----- > > --------=_MB49CA08F0-682A-4135-A2F6-956DD7751BF1 Content-Transfer-Encoding: quoted-printable Content-Type: text/html; charset=utf-8
Hi All,
 
I'm guessing this wasn't intentional, but the patch for xsa17 does = not contain a complete path to the tools/ioemu-qemu-xen/ path:
 
--- a/console.c
+++ b/console.c
 
Compared to all the other patches which provide a full path to the patched file:
 
--- a/xen/include/asm-x86/debugreg.h Mon Aug 06 12:28:03 2012 +0100+++ b/xen/include/asm-x86/debugreg.h Wed Aug 15 12:00:21 2012 +0100
 
Little annoying since it means you have to track down which console.c= is being patched instead of just applying from the root xen build dir.
 
- Nathan
 

------ Original Message ------
From: "Xen.org security team"= <security@xen.org>
To: xen-announce@lists.xen.org;xen-devel@lists= .xen.org;xen-users@lists.xen.org;oss-security@lists.openwall.com
Cc: = "Xen.org security team" <security@xen.org>
Sent: 9/5/2012 4:12:47= AM
Subject: [Xen-users] Xen Security Advisory 17 (CVE-2012-3515) - Qemu= VT100 emulation vulnerability
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

           Xen Secur=
ity Advisory CVE-2012-3515 / XSA-17
            &nb=
sp;            =
 version 2

            &nb=
sp; Qemu VT100 emulation vulnerability

UPDATES IN VERSION 2
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D

Public release.

ISSUE DESCRIPTION
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D

The device model used by fully virtualised (HVM) domains, qemu, does
not properly handle escape VT100 sequences when emulating certain
devices with a virtual console backend.

IMPACT
=3D=3D=3D=3D=3D=3D

An attacker who has sufficient privilege to access a vulnerable device
within a guest can overwrite portions of the device model's address
space. This can allow them to escalate their privileges to that of the
device model process.

VULNERABLE SYSTEMS
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D

All Xen systems running HVM guests are potentially vulnerable to this
depending on the specific guest configuration. The default
configuration is vulnerable.

Guests using either the traditional "qemu-xen" or upstream qemu device
models are vulnerable.

MITIGATION
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D

This issue can be avoided by only running PV guests or by configuring
HVM guests to not use the virtual console('vc') backend for any device.

For serial devices specify in your guest configuration:
    serial =3D 'none'
in your guest configuration.

For parallel port devices the syntax is toolstack specific.
For xend specify in your guest configuration:
    parallel =3D 'none'
For xl specify in your guest configuration:
    xl: device_model_args =3D ['-parallel', 'none']

In both cases the default is to use the vulnerable 'vc' mode.

You can confirm whether or not you are vulnerable by pressing
Ctrl-Alt-<N> (for digit N) while connected to either the VNC or SDL
console. If you are able to switch to a window displaying "serial" or
"parallel" then you are vulnerable.

The issue can also be mitigated by enabling the stub domain device
model. In this case the attacked can only potentially gain control of
the stub domain and not of the entire system.

To enable stub domains specify in your guest configuration:
   device_model =3D "stubdom-dm"

RESOLUTION
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D

Applying the appropriate attached patch(es) will resolve the issue.

PATCH INFORMATION
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D

The attached patches resolve this issue

Traditional qemu tree
  Xen 4.0, 4.1 and unstable         xsa17-qemu-xen-traditional-al=
l.patch

Upstream qemu tree (present in unstable only)
  Xen unstable                      xsa17-qemu-xen-unstable.patch

$ sha256sum xsa17-*.patch
60215322d3fbbc2054dfc160a20d9e0811af88487c4edc2f6ea81dcd5cedf039  xsa17-qem=
u-xen-traditional-all.patch
7b4bb59e7757080e7806a8b8eeb6b78fa0ffdfbfb28a7a379f7edff285bffd88  xsa17-qem=
u-xen-unstable.patch
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.10 (GNU/Linux)

iQEcBAEBAgAGBQJQRx1PAAoJEIP+FMlX6CvZUqUH/jeAAvQnoBp6YKzm78XSnnmk
GI2C/LhH0xqR3wFoEmWeMsiO4lrGrASX6T31NTvHa8sOtFqlNpTfRhwQybwYR3aa
cz9/4y2a54hD95P1nVmPF0PddmSP47QSpRdCj0projq1UGxIdwEhkNeSoM8h7dXO
MegqZClsvJMKd8XEcjBF5Qg7u9vLrXilCx5+It7XNE31Jxpkr/fozBb7FnNtDGJj
s4RN/UDU4Pu68XyZ7Dc5xEFdJW48tz4BIlxxXavILBRFSE1VEf7Gc8H9CsUtBPWB
C/LCUjpHkAOmqdgFhiLnZ2u+2s79U0dtPDJMNmqaGgWH+AqGkU9Nq8XXODTyY9k=3D
=3DgnuE
-----END PGP SIGNATURE-----
--------=_MB49CA08F0-682A-4135-A2F6-956DD7751BF1-- --===============3863741412607480835== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users --===============3863741412607480835==-- From xen-users-bounces@lists.xen.org Fri Sep 07 19:39:38 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Fri, 07 Sep 2012 19:39:38 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TA4Nl-0002cb-IW; Fri, 07 Sep 2012 19:38:25 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TA4Nj-0002cG-Am for xen-users@lists.xen.org; Fri, 07 Sep 2012 19:38:23 +0000 Received: from [85.158.143.35:5644] by server-3.bemta-4.messagelabs.com id 9C/2A-08232-E2D4A405; Fri, 07 Sep 2012 19:38:22 +0000 X-Env-Sender: nathan@gt.net X-Msg-Ref: server-14.tower-21.messagelabs.com!1347046698!17290202!1 X-Originating-IP: [208.70.244.21] X-SpamReason: No, hits=0.6 required=7.0 tests=BODY_RANDOM_LONG, HTML_50_60,HTML_MESSAGE X-StarScan-Received: X-StarScan-Version: 6.6.1.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 20594 invoked from network); 7 Sep 2012 19:38:19 -0000 Received: from gossamer.nmsrv.com (HELO gossamer.nmsrv.com) (208.70.244.21) by server-14.tower-21.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 7 Sep 2012 19:38:19 -0000 DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=gt.net; h=from:to:subject :date:content-type:in-reply-to:message-id:mime-version:reply-to; s=mail; bh=eccYW+NXSWljr1MDEIF1jjR1CLM=; b=K5lRpDAYj/iBP+Y0xUab vrjqkhoqU70k662PajUijouj/lLP0jMebtKJ7SHKHdLN0YX+soD+xCsaTzlWLwTO 8sO41hLmkGpB+RCBy0KErmECUOuMka3GKk3ADjL5YNhaA2poxIQd+zkaDKgfYw+i 8TXh36KhyMxMrAccB+X+0O4= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gt.net; h=from:to:subject :date:content-type:in-reply-to:message-id:mime-version:reply-to; q=dns; s=mail; b=fPcpUzhlk83c52TEpI4sE7dKEHVXJn76J2D4kulLjOvVV8 nWQCGF9M31bZmPNunhpfZE+3Ugsd29Gv1vkRGla+Bd+ADmhNtOuYwVpFaM3OwHxP BJcsn1uOCIRoZnnN1b2R8j1wrspO0is+HFVseVbxDf9fNKo722A0AuJlxphEY= Received: (qmail 26415 invoked from network); 7 Sep 2012 19:38:17 -0000 X-AntiVirus: Clean Received: from gateway.gossamer-threads.com (HELO ?192.168.1.152?) (nathan@gt.net@208.70.247.145) by gossamer.nmsrv.com with ESMTPSA (AES128-SHA encrypted); 7 Sep 2012 19:38:17 -0000 From: "Nathan March" To: "Xen.org security team" , xen-devel@lists.xen.org, xen-users@lists.xen.org Date: Fri, 07 Sep 2012 19:38:12 +0000 In-Reply-To: Message-Id: Mime-Version: 1.0 User-Agent: eM_Client/4.0.15145.0 Subject: Re: [Xen-users] [Xen-devel] Xen Security Advisory 17 (CVE-2012-3515) - Qemu VT100 emulation vulnerability X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list Reply-To: Nathan March List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============8258707292691800831==" Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org --===============8258707292691800831== Content-Type: multipart/alternative; boundary="------=_MB8E0CD934-91C9-4BEF-81FF-850F253CC118" --------=_MB8E0CD934-91C9-4BEF-81FF-850F253CC118 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; format=flowed; charset=utf-8 Same issue also applies to the xsa-19 patch. - Nathan ------ Original Message ------ From: "Nathan March" To: "Xen.org security team"=20 ;xen-devel@lists.xen.org;xen-users@lists.xen.org;oss-secu= rity@lists.openwall.com Cc: "Xen.org security team" Sent: 9/7/2012 12:33:42 PM Subject: Re: [Xen-devel] [Xen-users] Xen Security Advisory 17=20 (CVE-2012-3515) - Qemu VT100 emulation vulnerability >Hi All, >I'm guessing this wasn't intentional, but the patch for xsa17 does not=20 >contain a complete path to the tools/ioemu-qemu-xen/ path: >--- a/console.c >+++ b/console.c >Compared to all the other patches which provide a full path to the=20 >patched file: >--- a/xen/include/asm-x86/debugreg.h Mon Aug 06 12:28:03 2012 +0100 >+++ b/xen/include/asm-x86/debugreg.h Wed Aug 15 12:00:21 2012 +0100 >Little annoying since it means you have to track down which console.c=20 >is being patched instead of just applying from the root xen build dir. >- Nathan > >------ Original Message ------ >From: "Xen.org security team" >To: xen-announce@lists.xen.org;xen-devel@lists.xen.org;xen-users@lists.xen= .org;oss-security@lists.openwall.com >Cc: "Xen.org security team" >Sent: 9/5/2012 4:12:47 AM >Subject: [Xen-users] Xen Security Advisory 17 (CVE-2012-3515) - Qemu=20 >VT100 emulation vulnerability >>-----BEGIN PGP SIGNED MESSAGE----- >>Hash: SHA1 >> >> Xen Security Advisory CVE-2012-3515 / XSA-17 >> version 2 >> >> Qemu VT100 emulation vulnerability >> >>UPDATES IN VERSION 2 >>=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D >> >>Public release. >> >>ISSUE DESCRIPTION >>=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D >> >>The device model used by fully virtualised (HVM) domains, qemu, does >>not properly handle escape VT100 sequences when emulating certain >>devices with a virtual console backend. >> >>IMPACT >>=3D=3D=3D=3D=3D=3D >> >>An attacker who has sufficient privilege to access a vulnerable device >>within a guest can overwrite portions of the device model's address >>space. This can allow them to escalate their privileges to that of the >>device model process. >> >>VULNERABLE SYSTEMS >>=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D >> >>All Xen systems running HVM guests are potentially vulnerable to this >>depending on the specific guest configuration. The default >>configuration is vulnerable. >> >>Guests using either the traditional "qemu-xen" or upstream qemu device >>models are vulnerable. >> >>MITIGATION >>=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D >> >>This issue can be avoided by only running PV guests or by configuring >>HVM guests to not use the virtual console('vc') backend for any device. >> >>For serial devices specify in your guest configuration: >> serial =3D 'none' >>in your guest configuration. >> >>For parallel port devices the syntax is toolstack specific. >>For xend specify in your guest configuration: >> parallel =3D 'none' >>For xl specify in your guest configuration: >> xl: device_model_args =3D ['-parallel', 'none'] >> >>In both cases the default is to use the vulnerable 'vc' mode. >> >>You can confirm whether or not you are vulnerable by pressing >>Ctrl-Alt- (for digit N) while connected to either the VNC or SDL >>console. If you are able to switch to a window displaying "serial" or >>"parallel" then you are vulnerable. >> >>The issue can also be mitigated by enabling the stub domain device >>model. In this case the attacked can only potentially gain control of >>the stub domain and not of the entire system. >> >>To enable stub domains specify in your guest configuration: >> device_model =3D "stubdom-dm" >> >>RESOLUTION >>=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D >> >>Applying the appropriate attached patch(es) will resolve the issue. >> >>PATCH INFORMATION >>=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D >> >>The attached patches resolve this issue >> >>Traditional qemu tree >> Xen 4.0, 4.1 and unstable xsa17-qemu-xen-traditional-all.patch >> >>Upstream qemu tree (present in unstable only) >> Xen unstable xsa17-qemu-xen-unstable.patch >> >>$ sha256sum xsa17-*.patch >>60215322d3fbbc2054dfc160a20d9e0811af88487c4edc2f6ea81dcd5cedf039 xsa17-q= emu-xen-traditional-all.patch >>7b4bb59e7757080e7806a8b8eeb6b78fa0ffdfbfb28a7a379f7edff285bffd88 xsa17-q= emu-xen-unstable.patch >>-----BEGIN PGP SIGNATURE----- >>Version: GnuPG v1.4.10 (GNU/Linux) >> >>iQEcBAEBAgAGBQJQRx1PAAoJEIP+FMlX6CvZUqUH/jeAAvQnoBp6YKzm78XSnnmk >>GI2C/LhH0xqR3wFoEmWeMsiO4lrGrASX6T31NTvHa8sOtFqlNpTfRhwQybwYR3aa >>cz9/4y2a54hD95P1nVmPF0PddmSP47QSpRdCj0projq1UGxIdwEhkNeSoM8h7dXO >>MegqZClsvJMKd8XEcjBF5Qg7u9vLrXilCx5+It7XNE31Jxpkr/fozBb7FnNtDGJj >>s4RN/UDU4Pu68XyZ7Dc5xEFdJW48tz4BIlxxXavILBRFSE1VEf7Gc8H9CsUtBPWB >>C/LCUjpHkAOmqdgFhiLnZ2u+2s79U0dtPDJMNmqaGgWH+AqGkU9Nq8XXODTyY9k=3D >>=3DgnuE >>-----END PGP SIGNATURE----- >> >> --------=_MB8E0CD934-91C9-4BEF-81FF-850F253CC118 Content-Transfer-Encoding: quoted-printable Content-Type: text/html; charset=utf-8
Same issue also applies to the xsa-19 patch.
 
- Nathan

------ Original Message ------
From: "Nathan March" <nathan@= gt.net>
To: "Xen.org security team" <security@xen.org>;xen-deve= l@lists.xen.org;xen-users@lists.xen.org;oss-security@lists.openwall.com
= Cc: "Xen.org security team" <security@xen.org>
Sent: 9/7/2012 12:3= 3:42 PM
Subject: Re: [Xen-devel] [Xen-users] Xen Security Advisory 17= (CVE-2012-3515) - Qemu VT100 emulation vulnerability
Hi All,
 
I'm guessing this wasn't intentional, but the patch for xsa17 does = not contain a complete path to the tools/ioemu-qemu-xen/ path:
 
--- a/console.c
+++ b/console.c
 
Compared to all the other patches which provide a full path to the patched file:
 
--- a/xen/include/asm-x86/debugreg.h Mon Aug 06 12:28:03 2012 +0100+++ b/xen/include/asm-x86/debugreg.h Wed Aug 15 12:00:21 2012 +0100
 
Little annoying since it means you have to track down which console.c= is being patched instead of just applying from the root xen build dir.
 
- Nathan
 

------ Original Message ------
From: "Xen.org security team"= <security@xen.org>
To: xen-announce@lists.x= en.org;xen-devel@lists.xen.org;xen-us= ers@lists.xen.org;oss-security@lists.ope= nwall.com
Cc: "Xen.org security team" <security@xen.org&= gt;
Sent: 9/5/2012 4:12:47 AM
Subject: [Xen-users] Xen Security Advis= ory 17 (CVE-2012-3515) - Qemu VT100 emulation vulnerability
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

           Xen Secur=
ity Advisory CVE-2012-3515 / XSA-17
            &nb=
sp;            =
 version 2

            &nb=
sp; Qemu VT100 emulation vulnerability

UPDATES IN VERSION 2
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D

Public release.

ISSUE DESCRIPTION
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D

The device model used by fully virtualised (HVM) domains, qemu, does
not properly handle escape VT100 sequences when emulating certain
devices with a virtual console backend.

IMPACT
=3D=3D=3D=3D=3D=3D

An attacker who has sufficient privilege to access a vulnerable device
within a guest can overwrite portions of the device model's address
space. This can allow them to escalate their privileges to that of the
device model process.

VULNERABLE SYSTEMS
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D

All Xen systems running HVM guests are potentially vulnerable to this
depending on the specific guest configuration. The default
configuration is vulnerable.

Guests using either the traditional "qemu-xen" or upstream qemu device
models are vulnerable.

MITIGATION
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D

This issue can be avoided by only running PV guests or by configuring
HVM guests to not use the virtual console('vc') backend for any device.

For serial devices specify in your guest configuration:
    serial =3D 'none'
in your guest configuration.

For parallel port devices the syntax is toolstack specific.
For xend specify in your guest configuration:
    parallel =3D 'none'
For xl specify in your guest configuration:
    xl: device_model_args =3D ['-parallel', 'none']

In both cases the default is to use the vulnerable 'vc' mode.

You can confirm whether or not you are vulnerable by pressing
Ctrl-Alt-<N> (for digit N) while connected to either the VNC or SDL
console. If you are able to switch to a window displaying "serial" or
"parallel" then you are vulnerable.

The issue can also be mitigated by enabling the stub domain device
model. In this case the attacked can only potentially gain control of
the stub domain and not of the entire system.

To enable stub domains specify in your guest configuration:
   device_model =3D "stubdom-dm"

RESOLUTION
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D

Applying the appropriate attached patch(es) will resolve the issue.

PATCH INFORMATION
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D

The attached patches resolve this issue

Traditional qemu tree
  Xen 4.0, 4.1 and unstable         xsa17-qemu-xen-traditional-al=
l.patch

Upstream qemu tree (present in unstable only)
  Xen unstable                      xsa17-qemu-xen-unstable.patch

$ sha256sum xsa17-*.patch
60215322d3fbbc2054dfc160a20d9e0811af88487c4edc2f6ea81dcd5cedf039  xsa17-qem=
u-xen-traditional-all.patch
7b4bb59e7757080e7806a8b8eeb6b78fa0ffdfbfb28a7a379f7edff285bffd88  xsa17-qem=
u-xen-unstable.patch
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.10 (GNU/Linux)

iQEcBAEBAgAGBQJQRx1PAAoJEIP+FMlX6CvZUqUH/jeAAvQnoBp6YKzm78XSnnmk
GI2C/LhH0xqR3wFoEmWeMsiO4lrGrASX6T31NTvHa8sOtFqlNpTfRhwQybwYR3aa
cz9/4y2a54hD95P1nVmPF0PddmSP47QSpRdCj0projq1UGxIdwEhkNeSoM8h7dXO
MegqZClsvJMKd8XEcjBF5Qg7u9vLrXilCx5+It7XNE31Jxpkr/fozBb7FnNtDGJj
s4RN/UDU4Pu68XyZ7Dc5xEFdJW48tz4BIlxxXavILBRFSE1VEf7Gc8H9CsUtBPWB
C/LCUjpHkAOmqdgFhiLnZ2u+2s79U0dtPDJMNmqaGgWH+AqGkU9Nq8XXODTyY9k=3D
=3DgnuE
-----END PGP SIGNATURE-----
--------=_MB8E0CD934-91C9-4BEF-81FF-850F253CC118-- --===============8258707292691800831== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users --===============8258707292691800831==-- From xen-users-bounces@lists.xen.org Fri Sep 07 19:39:38 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Fri, 07 Sep 2012 19:39:38 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TA4Nl-0002cb-IW; Fri, 07 Sep 2012 19:38:25 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TA4Nj-0002cG-Am for xen-users@lists.xen.org; Fri, 07 Sep 2012 19:38:23 +0000 Received: from [85.158.143.35:5644] by server-3.bemta-4.messagelabs.com id 9C/2A-08232-E2D4A405; Fri, 07 Sep 2012 19:38:22 +0000 X-Env-Sender: nathan@gt.net X-Msg-Ref: server-14.tower-21.messagelabs.com!1347046698!17290202!1 X-Originating-IP: [208.70.244.21] X-SpamReason: No, hits=0.6 required=7.0 tests=BODY_RANDOM_LONG, HTML_50_60,HTML_MESSAGE X-StarScan-Received: X-StarScan-Version: 6.6.1.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 20594 invoked from network); 7 Sep 2012 19:38:19 -0000 Received: from gossamer.nmsrv.com (HELO gossamer.nmsrv.com) (208.70.244.21) by server-14.tower-21.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 7 Sep 2012 19:38:19 -0000 DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=gt.net; h=from:to:subject :date:content-type:in-reply-to:message-id:mime-version:reply-to; s=mail; bh=eccYW+NXSWljr1MDEIF1jjR1CLM=; b=K5lRpDAYj/iBP+Y0xUab vrjqkhoqU70k662PajUijouj/lLP0jMebtKJ7SHKHdLN0YX+soD+xCsaTzlWLwTO 8sO41hLmkGpB+RCBy0KErmECUOuMka3GKk3ADjL5YNhaA2poxIQd+zkaDKgfYw+i 8TXh36KhyMxMrAccB+X+0O4= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gt.net; h=from:to:subject :date:content-type:in-reply-to:message-id:mime-version:reply-to; q=dns; s=mail; b=fPcpUzhlk83c52TEpI4sE7dKEHVXJn76J2D4kulLjOvVV8 nWQCGF9M31bZmPNunhpfZE+3Ugsd29Gv1vkRGla+Bd+ADmhNtOuYwVpFaM3OwHxP BJcsn1uOCIRoZnnN1b2R8j1wrspO0is+HFVseVbxDf9fNKo722A0AuJlxphEY= Received: (qmail 26415 invoked from network); 7 Sep 2012 19:38:17 -0000 X-AntiVirus: Clean Received: from gateway.gossamer-threads.com (HELO ?192.168.1.152?) (nathan@gt.net@208.70.247.145) by gossamer.nmsrv.com with ESMTPSA (AES128-SHA encrypted); 7 Sep 2012 19:38:17 -0000 From: "Nathan March" To: "Xen.org security team" , xen-devel@lists.xen.org, xen-users@lists.xen.org Date: Fri, 07 Sep 2012 19:38:12 +0000 In-Reply-To: Message-Id: Mime-Version: 1.0 User-Agent: eM_Client/4.0.15145.0 Subject: Re: [Xen-users] [Xen-devel] Xen Security Advisory 17 (CVE-2012-3515) - Qemu VT100 emulation vulnerability X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list Reply-To: Nathan March List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============8258707292691800831==" Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org --===============8258707292691800831== Content-Type: multipart/alternative; boundary="------=_MB8E0CD934-91C9-4BEF-81FF-850F253CC118" --------=_MB8E0CD934-91C9-4BEF-81FF-850F253CC118 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; format=flowed; charset=utf-8 Same issue also applies to the xsa-19 patch. - Nathan ------ Original Message ------ From: "Nathan March" To: "Xen.org security team"=20 ;xen-devel@lists.xen.org;xen-users@lists.xen.org;oss-secu= rity@lists.openwall.com Cc: "Xen.org security team" Sent: 9/7/2012 12:33:42 PM Subject: Re: [Xen-devel] [Xen-users] Xen Security Advisory 17=20 (CVE-2012-3515) - Qemu VT100 emulation vulnerability >Hi All, >I'm guessing this wasn't intentional, but the patch for xsa17 does not=20 >contain a complete path to the tools/ioemu-qemu-xen/ path: >--- a/console.c >+++ b/console.c >Compared to all the other patches which provide a full path to the=20 >patched file: >--- a/xen/include/asm-x86/debugreg.h Mon Aug 06 12:28:03 2012 +0100 >+++ b/xen/include/asm-x86/debugreg.h Wed Aug 15 12:00:21 2012 +0100 >Little annoying since it means you have to track down which console.c=20 >is being patched instead of just applying from the root xen build dir. >- Nathan > >------ Original Message ------ >From: "Xen.org security team" >To: xen-announce@lists.xen.org;xen-devel@lists.xen.org;xen-users@lists.xen= .org;oss-security@lists.openwall.com >Cc: "Xen.org security team" >Sent: 9/5/2012 4:12:47 AM >Subject: [Xen-users] Xen Security Advisory 17 (CVE-2012-3515) - Qemu=20 >VT100 emulation vulnerability >>-----BEGIN PGP SIGNED MESSAGE----- >>Hash: SHA1 >> >> Xen Security Advisory CVE-2012-3515 / XSA-17 >> version 2 >> >> Qemu VT100 emulation vulnerability >> >>UPDATES IN VERSION 2 >>=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D >> >>Public release. >> >>ISSUE DESCRIPTION >>=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D >> >>The device model used by fully virtualised (HVM) domains, qemu, does >>not properly handle escape VT100 sequences when emulating certain >>devices with a virtual console backend. >> >>IMPACT >>=3D=3D=3D=3D=3D=3D >> >>An attacker who has sufficient privilege to access a vulnerable device >>within a guest can overwrite portions of the device model's address >>space. This can allow them to escalate their privileges to that of the >>device model process. >> >>VULNERABLE SYSTEMS >>=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D >> >>All Xen systems running HVM guests are potentially vulnerable to this >>depending on the specific guest configuration. The default >>configuration is vulnerable. >> >>Guests using either the traditional "qemu-xen" or upstream qemu device >>models are vulnerable. >> >>MITIGATION >>=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D >> >>This issue can be avoided by only running PV guests or by configuring >>HVM guests to not use the virtual console('vc') backend for any device. >> >>For serial devices specify in your guest configuration: >> serial =3D 'none' >>in your guest configuration. >> >>For parallel port devices the syntax is toolstack specific. >>For xend specify in your guest configuration: >> parallel =3D 'none' >>For xl specify in your guest configuration: >> xl: device_model_args =3D ['-parallel', 'none'] >> >>In both cases the default is to use the vulnerable 'vc' mode. >> >>You can confirm whether or not you are vulnerable by pressing >>Ctrl-Alt- (for digit N) while connected to either the VNC or SDL >>console. If you are able to switch to a window displaying "serial" or >>"parallel" then you are vulnerable. >> >>The issue can also be mitigated by enabling the stub domain device >>model. In this case the attacked can only potentially gain control of >>the stub domain and not of the entire system. >> >>To enable stub domains specify in your guest configuration: >> device_model =3D "stubdom-dm" >> >>RESOLUTION >>=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D >> >>Applying the appropriate attached patch(es) will resolve the issue. >> >>PATCH INFORMATION >>=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D >> >>The attached patches resolve this issue >> >>Traditional qemu tree >> Xen 4.0, 4.1 and unstable xsa17-qemu-xen-traditional-all.patch >> >>Upstream qemu tree (present in unstable only) >> Xen unstable xsa17-qemu-xen-unstable.patch >> >>$ sha256sum xsa17-*.patch >>60215322d3fbbc2054dfc160a20d9e0811af88487c4edc2f6ea81dcd5cedf039 xsa17-q= emu-xen-traditional-all.patch >>7b4bb59e7757080e7806a8b8eeb6b78fa0ffdfbfb28a7a379f7edff285bffd88 xsa17-q= emu-xen-unstable.patch >>-----BEGIN PGP SIGNATURE----- >>Version: GnuPG v1.4.10 (GNU/Linux) >> >>iQEcBAEBAgAGBQJQRx1PAAoJEIP+FMlX6CvZUqUH/jeAAvQnoBp6YKzm78XSnnmk >>GI2C/LhH0xqR3wFoEmWeMsiO4lrGrASX6T31NTvHa8sOtFqlNpTfRhwQybwYR3aa >>cz9/4y2a54hD95P1nVmPF0PddmSP47QSpRdCj0projq1UGxIdwEhkNeSoM8h7dXO >>MegqZClsvJMKd8XEcjBF5Qg7u9vLrXilCx5+It7XNE31Jxpkr/fozBb7FnNtDGJj >>s4RN/UDU4Pu68XyZ7Dc5xEFdJW48tz4BIlxxXavILBRFSE1VEf7Gc8H9CsUtBPWB >>C/LCUjpHkAOmqdgFhiLnZ2u+2s79U0dtPDJMNmqaGgWH+AqGkU9Nq8XXODTyY9k=3D >>=3DgnuE >>-----END PGP SIGNATURE----- >> >> --------=_MB8E0CD934-91C9-4BEF-81FF-850F253CC118 Content-Transfer-Encoding: quoted-printable Content-Type: text/html; charset=utf-8
Same issue also applies to the xsa-19 patch.
 
- Nathan

------ Original Message ------
From: "Nathan March" <nathan@= gt.net>
To: "Xen.org security team" <security@xen.org>;xen-deve= l@lists.xen.org;xen-users@lists.xen.org;oss-security@lists.openwall.com
= Cc: "Xen.org security team" <security@xen.org>
Sent: 9/7/2012 12:3= 3:42 PM
Subject: Re: [Xen-devel] [Xen-users] Xen Security Advisory 17= (CVE-2012-3515) - Qemu VT100 emulation vulnerability
Hi All,
 
I'm guessing this wasn't intentional, but the patch for xsa17 does = not contain a complete path to the tools/ioemu-qemu-xen/ path:
 
--- a/console.c
+++ b/console.c
 
Compared to all the other patches which provide a full path to the patched file:
 
--- a/xen/include/asm-x86/debugreg.h Mon Aug 06 12:28:03 2012 +0100+++ b/xen/include/asm-x86/debugreg.h Wed Aug 15 12:00:21 2012 +0100
 
Little annoying since it means you have to track down which console.c= is being patched instead of just applying from the root xen build dir.
 
- Nathan
 

------ Original Message ------
From: "Xen.org security team"= <security@xen.org>
To: xen-announce@lists.x= en.org;xen-devel@lists.xen.org;xen-us= ers@lists.xen.org;oss-security@lists.ope= nwall.com
Cc: "Xen.org security team" <security@xen.org&= gt;
Sent: 9/5/2012 4:12:47 AM
Subject: [Xen-users] Xen Security Advis= ory 17 (CVE-2012-3515) - Qemu VT100 emulation vulnerability
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

           Xen Secur=
ity Advisory CVE-2012-3515 / XSA-17
            &nb=
sp;            =
 version 2

            &nb=
sp; Qemu VT100 emulation vulnerability

UPDATES IN VERSION 2
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D

Public release.

ISSUE DESCRIPTION
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D

The device model used by fully virtualised (HVM) domains, qemu, does
not properly handle escape VT100 sequences when emulating certain
devices with a virtual console backend.

IMPACT
=3D=3D=3D=3D=3D=3D

An attacker who has sufficient privilege to access a vulnerable device
within a guest can overwrite portions of the device model's address
space. This can allow them to escalate their privileges to that of the
device model process.

VULNERABLE SYSTEMS
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D

All Xen systems running HVM guests are potentially vulnerable to this
depending on the specific guest configuration. The default
configuration is vulnerable.

Guests using either the traditional "qemu-xen" or upstream qemu device
models are vulnerable.

MITIGATION
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D

This issue can be avoided by only running PV guests or by configuring
HVM guests to not use the virtual console('vc') backend for any device.

For serial devices specify in your guest configuration:
    serial =3D 'none'
in your guest configuration.

For parallel port devices the syntax is toolstack specific.
For xend specify in your guest configuration:
    parallel =3D 'none'
For xl specify in your guest configuration:
    xl: device_model_args =3D ['-parallel', 'none']

In both cases the default is to use the vulnerable 'vc' mode.

You can confirm whether or not you are vulnerable by pressing
Ctrl-Alt-<N> (for digit N) while connected to either the VNC or SDL
console. If you are able to switch to a window displaying "serial" or
"parallel" then you are vulnerable.

The issue can also be mitigated by enabling the stub domain device
model. In this case the attacked can only potentially gain control of
the stub domain and not of the entire system.

To enable stub domains specify in your guest configuration:
   device_model =3D "stubdom-dm"

RESOLUTION
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D

Applying the appropriate attached patch(es) will resolve the issue.

PATCH INFORMATION
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D

The attached patches resolve this issue

Traditional qemu tree
  Xen 4.0, 4.1 and unstable         xsa17-qemu-xen-traditional-al=
l.patch

Upstream qemu tree (present in unstable only)
  Xen unstable                      xsa17-qemu-xen-unstable.patch

$ sha256sum xsa17-*.patch
60215322d3fbbc2054dfc160a20d9e0811af88487c4edc2f6ea81dcd5cedf039  xsa17-qem=
u-xen-traditional-all.patch
7b4bb59e7757080e7806a8b8eeb6b78fa0ffdfbfb28a7a379f7edff285bffd88  xsa17-qem=
u-xen-unstable.patch
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.10 (GNU/Linux)

iQEcBAEBAgAGBQJQRx1PAAoJEIP+FMlX6CvZUqUH/jeAAvQnoBp6YKzm78XSnnmk
GI2C/LhH0xqR3wFoEmWeMsiO4lrGrASX6T31NTvHa8sOtFqlNpTfRhwQybwYR3aa
cz9/4y2a54hD95P1nVmPF0PddmSP47QSpRdCj0projq1UGxIdwEhkNeSoM8h7dXO
MegqZClsvJMKd8XEcjBF5Qg7u9vLrXilCx5+It7XNE31Jxpkr/fozBb7FnNtDGJj
s4RN/UDU4Pu68XyZ7Dc5xEFdJW48tz4BIlxxXavILBRFSE1VEf7Gc8H9CsUtBPWB
C/LCUjpHkAOmqdgFhiLnZ2u+2s79U0dtPDJMNmqaGgWH+AqGkU9Nq8XXODTyY9k=3D
=3DgnuE
-----END PGP SIGNATURE-----
--------=_MB8E0CD934-91C9-4BEF-81FF-850F253CC118-- --===============8258707292691800831== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users --===============8258707292691800831==-- From xen-users-bounces@lists.xen.org Sat Sep 08 08:17:24 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Sat, 08 Sep 2012 08:17:24 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TAGCR-0006jW-Ez; Sat, 08 Sep 2012 08:15:31 +0000 Received: from mail27.messagelabs.com ([193.109.254.147]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TAGCQ-0006jR-AM for xen-users@lists.xen.org; Sat, 08 Sep 2012 08:15:30 +0000 X-Env-Sender: lists+xen@internecto.net X-Msg-Ref: server-9.tower-27.messagelabs.com!1347092123!8873637!1 X-Originating-IP: [176.9.245.29] X-SpamReason: No, hits=0.0 required=7.0 tests= X-StarScan-Received: X-StarScan-Version: 6.6.1.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 21278 invoked from network); 8 Sep 2012 08:15:24 -0000 Received: from polaris.internecto.net (HELO mx1.internecto.net) (176.9.245.29) by server-9.tower-27.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 8 Sep 2012 08:15:24 -0000 Received: from localhost (localhost [127.0.0.1]) by mx1.internecto.net (Postfix) with ESMTP id BB6B9A016E for ; Sat, 8 Sep 2012 08:15:23 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at mail.internecto.net Received: from mx1.internecto.net ([127.0.0.1]) by localhost (mail.polaris.internecto.net [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id C5eYSvB2cy3A for ; Sat, 8 Sep 2012 08:15:23 +0000 (UTC) Received: from internecto.net (5ED4FDEB.cm-7-5d.dynamic.ziggo.nl [94.212.253.235]) (using TLSv1 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (Client did not present a certificate) (Authenticated sender: lists@internecto.net) by mx1.internecto.net (Postfix) with ESMTPSA id 39530A0089 for ; Sat, 8 Sep 2012 08:15:23 +0000 (UTC) Date: Sat, 8 Sep 2012 10:15:21 +0200 From: Mark van Dijk To: xen-users@lists.xen.org Message-ID: <20120908101521.6f201570@internecto.net> Organization: Internecto SIS X-Mailer: Claws Mail 3.8.0 (GTK+ 2.24.10; x86_64-pc-linux-gnu) Mime-Version: 1.0 Subject: [Xen-users] Windows 2008 Server, GPLPV drivers, Qemu upstream and BSoD X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org Hi, I just tested booting Windows 2008 server 64 bit using GPLPV drivers. It seems to work with qemu traditional, but with Qemu upstream (1.1-stable) there is a BSOD when using the most recent signed GPLPV drivers (paging fault in non-paged area). -- Stay in touch, Mark van Dijk. ,--------------------------------- -----------------------------' Sat Sep 08 08:14 UTC 2012 Today is Sweetmorn, the 32nd day of Bureaucracy in the YOLD 3178 _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Sat Sep 08 08:17:24 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Sat, 08 Sep 2012 08:17:24 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TAGCR-0006jW-Ez; Sat, 08 Sep 2012 08:15:31 +0000 Received: from mail27.messagelabs.com ([193.109.254.147]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TAGCQ-0006jR-AM for xen-users@lists.xen.org; Sat, 08 Sep 2012 08:15:30 +0000 X-Env-Sender: lists+xen@internecto.net X-Msg-Ref: server-9.tower-27.messagelabs.com!1347092123!8873637!1 X-Originating-IP: [176.9.245.29] X-SpamReason: No, hits=0.0 required=7.0 tests= X-StarScan-Received: X-StarScan-Version: 6.6.1.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 21278 invoked from network); 8 Sep 2012 08:15:24 -0000 Received: from polaris.internecto.net (HELO mx1.internecto.net) (176.9.245.29) by server-9.tower-27.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 8 Sep 2012 08:15:24 -0000 Received: from localhost (localhost [127.0.0.1]) by mx1.internecto.net (Postfix) with ESMTP id BB6B9A016E for ; Sat, 8 Sep 2012 08:15:23 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at mail.internecto.net Received: from mx1.internecto.net ([127.0.0.1]) by localhost (mail.polaris.internecto.net [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id C5eYSvB2cy3A for ; Sat, 8 Sep 2012 08:15:23 +0000 (UTC) Received: from internecto.net (5ED4FDEB.cm-7-5d.dynamic.ziggo.nl [94.212.253.235]) (using TLSv1 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (Client did not present a certificate) (Authenticated sender: lists@internecto.net) by mx1.internecto.net (Postfix) with ESMTPSA id 39530A0089 for ; Sat, 8 Sep 2012 08:15:23 +0000 (UTC) Date: Sat, 8 Sep 2012 10:15:21 +0200 From: Mark van Dijk To: xen-users@lists.xen.org Message-ID: <20120908101521.6f201570@internecto.net> Organization: Internecto SIS X-Mailer: Claws Mail 3.8.0 (GTK+ 2.24.10; x86_64-pc-linux-gnu) Mime-Version: 1.0 Subject: [Xen-users] Windows 2008 Server, GPLPV drivers, Qemu upstream and BSoD X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org Hi, I just tested booting Windows 2008 server 64 bit using GPLPV drivers. It seems to work with qemu traditional, but with Qemu upstream (1.1-stable) there is a BSOD when using the most recent signed GPLPV drivers (paging fault in non-paged area). -- Stay in touch, Mark van Dijk. ,--------------------------------- -----------------------------' Sat Sep 08 08:14 UTC 2012 Today is Sweetmorn, the 32nd day of Bureaucracy in the YOLD 3178 _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Sat Sep 08 14:51:43 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Sat, 08 Sep 2012 14:51:43 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TAMMQ-0003At-3q; Sat, 08 Sep 2012 14:50:14 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TAMMP-0003Ao-F4 for xen-users@lists.xen.org; Sat, 08 Sep 2012 14:50:13 +0000 Received: from [85.158.139.83:4824] by server-8.bemta-5.messagelabs.com id 03/05-17085-42B5B405; Sat, 08 Sep 2012 14:50:12 +0000 X-Env-Sender: maik.brauer@mbs-systems.net X-Msg-Ref: server-13.tower-182.messagelabs.com!1347115810!28802568!1 X-Originating-IP: [188.40.240.248] X-SpamReason: No, hits=0.0 required=7.0 tests= X-StarScan-Received: X-StarScan-Version: 6.6.1.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 32407 invoked from network); 8 Sep 2012 14:50:11 -0000 Received: from mx1.mbs-systems.net (HELO mx1.mbs-systems.net) (188.40.240.248) by server-13.tower-182.messagelabs.com with SMTP; 8 Sep 2012 14:50:11 -0000 Received: from localhost (localhost [127.0.0.1]) by mx1.mbs-systems.net (Postfix) with ESMTP id 4CE245C30B; Sat, 8 Sep 2012 16:51:09 +0200 (CEST) Received: from mx1.mbs-systems.net ([127.0.0.1]) by localhost (mta.mbs-systems.net [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 7hfXRGSY5WRZ; Sat, 8 Sep 2012 16:51:08 +0200 (CEST) Received: from maiks-macbookpro.fritz.box (dslb-094-221-252-144.pools.arcor-ip.net [94.221.252.144]) by mx1.mbs-systems.net (Postfix) with ESMTPSA id 6D14C5C2A7; Sat, 8 Sep 2012 16:51:08 +0200 (CEST) Mime-Version: 1.0 (Apple Message framework v1278) From: Maik Brauer In-Reply-To: <1346746297.32462.37.camel@zakaz.uk.xensource.com> Date: Sat, 8 Sep 2012 16:50:06 +0200 Message-Id: References: <9F8FD2B0-450A-4A6E-A929-BA240ED1D997@mbs-systems.net> <1346746297.32462.37.camel@zakaz.uk.xensource.com> To: Ian Campbell X-Mailer: Apple Mail (2.1278) Cc: "xen-users@lists.xen.org" , Casey DeLorme Subject: Re: [Xen-users] Dom0 crashed when rebooting whilst DomU are running X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org On Sep 4, 2012, at 10:11 AM, Ian Campbell wrote: > Could you not top post please, it makes it rather hard to follow the > flow of the conversation. > On Mon, 2012-09-03 at 18:10 +0100, Casey DeLorme wrote: >> As stated, you can alias shutdown to do exactly what you need, it can >> be as simple as a series of hard-coded operations to a complex custom >> shell script that parses your domains and closes each with feedback. > > Xen ships the "xendomains" initscript which can halt guest on shutdown > as well as automatically start specific guests on boot. It can also be > configured to suspend/resume them or (I think) migrate them away. > > For diagnosing the crash itself more details will be required than were > provided in the original post. Please see > http://wiki.xen.org/wiki/Reporting_Bugs_against_Xen for some guidance. > At a minimum we would need a capture (serial console or photo) of the > crash backtrace. > > Ian. > > I found out that it hangs during re-boot of dom0 when having more Network interfaces involved, like: vif = [ 'mac=06:46:AB:CC:11:01, ip=', '', '', 'mac=06:04:AB:BB:11:03, bridge=VLAN20, script=vif-bridge', '', 'mac=06:04:AB:BB:11:05, bridge=VLAN40, script=vif-bridge' ] in case you use just one or having the basic line in place, it is working: vif = [ '' ] The system stops after initiating the reboot at the following line in the console: System will restart........... In the Logfile of /var/log/message you can find this as the last line: Sep 8 15:44:28 rootsrv01 shutdown[2445]: shutting down for system reboot Sep 8 15:44:31 rootsrv01 kernel: [ 73.716246] VLAN20: port 1(vif2.3) entering forwarding state Sep 8 15:44:31 rootsrv01 kernel: [ 74.500111] VLAN40: port 1(vif2.5) entering forwarding state Sep 8 15:44:34 rootsrv01 kernel: [ 77.317431] VLAN20: port 1(vif2.3) entering disabled state Sep 8 15:44:34 rootsrv01 kernel: [ 77.317490] VLAN20: port 1(vif2.3) entering disabled state Sep 8 15:44:36 rootsrv01 kernel: [ 79.368685] VLAN40: port 1(vif2.5) entering disabled state Sep 8 15:44:36 rootsrv01 kernel: [ 79.369156] VLAN40: port 1(vif2.5) entering disabled state Sep 8 15:44:37 rootsrv01 kernel: Kernel logging (proc) stopped. Sep 8 15:44:37 rootsrv01 rsyslogd: [origin software="rsyslogd" swVersion="4.6.4" x-pid="890" x-info="http://www.rsyslog.com"] exiting on signal 15. In the /var/log/daemong.log you can find this message: Sep 8 15:44:37 rootsrv01 acpid: exiting Sep 8 15:44:37 rootsrv01 rpc.statd[750]: Caught signal 15, un-registering and exiting Sep 8 15:44:37 rootsrv01 udevd-work[2276]: '/etc/xen/scripts/vif-setup offline type_if=vif' unexpected exit with status 0x000f Cheers, Maik > > > _______________________________________________ > Xen-users mailing list > Xen-users@lists.xen.org > http://lists.xen.org/xen-users _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Sat Sep 08 14:51:43 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Sat, 08 Sep 2012 14:51:43 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TAMMQ-0003At-3q; Sat, 08 Sep 2012 14:50:14 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TAMMP-0003Ao-F4 for xen-users@lists.xen.org; Sat, 08 Sep 2012 14:50:13 +0000 Received: from [85.158.139.83:4824] by server-8.bemta-5.messagelabs.com id 03/05-17085-42B5B405; Sat, 08 Sep 2012 14:50:12 +0000 X-Env-Sender: maik.brauer@mbs-systems.net X-Msg-Ref: server-13.tower-182.messagelabs.com!1347115810!28802568!1 X-Originating-IP: [188.40.240.248] X-SpamReason: No, hits=0.0 required=7.0 tests= X-StarScan-Received: X-StarScan-Version: 6.6.1.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 32407 invoked from network); 8 Sep 2012 14:50:11 -0000 Received: from mx1.mbs-systems.net (HELO mx1.mbs-systems.net) (188.40.240.248) by server-13.tower-182.messagelabs.com with SMTP; 8 Sep 2012 14:50:11 -0000 Received: from localhost (localhost [127.0.0.1]) by mx1.mbs-systems.net (Postfix) with ESMTP id 4CE245C30B; Sat, 8 Sep 2012 16:51:09 +0200 (CEST) Received: from mx1.mbs-systems.net ([127.0.0.1]) by localhost (mta.mbs-systems.net [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 7hfXRGSY5WRZ; Sat, 8 Sep 2012 16:51:08 +0200 (CEST) Received: from maiks-macbookpro.fritz.box (dslb-094-221-252-144.pools.arcor-ip.net [94.221.252.144]) by mx1.mbs-systems.net (Postfix) with ESMTPSA id 6D14C5C2A7; Sat, 8 Sep 2012 16:51:08 +0200 (CEST) Mime-Version: 1.0 (Apple Message framework v1278) From: Maik Brauer In-Reply-To: <1346746297.32462.37.camel@zakaz.uk.xensource.com> Date: Sat, 8 Sep 2012 16:50:06 +0200 Message-Id: References: <9F8FD2B0-450A-4A6E-A929-BA240ED1D997@mbs-systems.net> <1346746297.32462.37.camel@zakaz.uk.xensource.com> To: Ian Campbell X-Mailer: Apple Mail (2.1278) Cc: "xen-users@lists.xen.org" , Casey DeLorme Subject: Re: [Xen-users] Dom0 crashed when rebooting whilst DomU are running X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org On Sep 4, 2012, at 10:11 AM, Ian Campbell wrote: > Could you not top post please, it makes it rather hard to follow the > flow of the conversation. > On Mon, 2012-09-03 at 18:10 +0100, Casey DeLorme wrote: >> As stated, you can alias shutdown to do exactly what you need, it can >> be as simple as a series of hard-coded operations to a complex custom >> shell script that parses your domains and closes each with feedback. > > Xen ships the "xendomains" initscript which can halt guest on shutdown > as well as automatically start specific guests on boot. It can also be > configured to suspend/resume them or (I think) migrate them away. > > For diagnosing the crash itself more details will be required than were > provided in the original post. Please see > http://wiki.xen.org/wiki/Reporting_Bugs_against_Xen for some guidance. > At a minimum we would need a capture (serial console or photo) of the > crash backtrace. > > Ian. > > I found out that it hangs during re-boot of dom0 when having more Network interfaces involved, like: vif = [ 'mac=06:46:AB:CC:11:01, ip=', '', '', 'mac=06:04:AB:BB:11:03, bridge=VLAN20, script=vif-bridge', '', 'mac=06:04:AB:BB:11:05, bridge=VLAN40, script=vif-bridge' ] in case you use just one or having the basic line in place, it is working: vif = [ '' ] The system stops after initiating the reboot at the following line in the console: System will restart........... In the Logfile of /var/log/message you can find this as the last line: Sep 8 15:44:28 rootsrv01 shutdown[2445]: shutting down for system reboot Sep 8 15:44:31 rootsrv01 kernel: [ 73.716246] VLAN20: port 1(vif2.3) entering forwarding state Sep 8 15:44:31 rootsrv01 kernel: [ 74.500111] VLAN40: port 1(vif2.5) entering forwarding state Sep 8 15:44:34 rootsrv01 kernel: [ 77.317431] VLAN20: port 1(vif2.3) entering disabled state Sep 8 15:44:34 rootsrv01 kernel: [ 77.317490] VLAN20: port 1(vif2.3) entering disabled state Sep 8 15:44:36 rootsrv01 kernel: [ 79.368685] VLAN40: port 1(vif2.5) entering disabled state Sep 8 15:44:36 rootsrv01 kernel: [ 79.369156] VLAN40: port 1(vif2.5) entering disabled state Sep 8 15:44:37 rootsrv01 kernel: Kernel logging (proc) stopped. Sep 8 15:44:37 rootsrv01 rsyslogd: [origin software="rsyslogd" swVersion="4.6.4" x-pid="890" x-info="http://www.rsyslog.com"] exiting on signal 15. In the /var/log/daemong.log you can find this message: Sep 8 15:44:37 rootsrv01 acpid: exiting Sep 8 15:44:37 rootsrv01 rpc.statd[750]: Caught signal 15, un-registering and exiting Sep 8 15:44:37 rootsrv01 udevd-work[2276]: '/etc/xen/scripts/vif-setup offline type_if=vif' unexpected exit with status 0x000f Cheers, Maik > > > _______________________________________________ > Xen-users mailing list > Xen-users@lists.xen.org > http://lists.xen.org/xen-users _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Sun Sep 09 19:39:35 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Sun, 09 Sep 2012 19:39:35 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TAnKO-00046z-V2; Sun, 09 Sep 2012 19:37:56 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TAnKN-00046u-BS for xen-users@lists.xen.org; Sun, 09 Sep 2012 19:37:55 +0000 Received: from [85.158.139.83:59715] by server-3.bemta-5.messagelabs.com id 88/EA-21836-210FC405; Sun, 09 Sep 2012 19:37:54 +0000 X-Env-Sender: maik.brauer@mbs-systems.net X-Msg-Ref: server-4.tower-182.messagelabs.com!1347219473!24929094!1 X-Originating-IP: [188.40.240.248] X-SpamReason: No, hits=0.0 required=7.0 tests= X-StarScan-Received: X-StarScan-Version: 6.6.1.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 374 invoked from network); 9 Sep 2012 19:37:53 -0000 Received: from mx1.mbs-systems.net (HELO mx1.mbs-systems.net) (188.40.240.248) by server-4.tower-182.messagelabs.com with SMTP; 9 Sep 2012 19:37:53 -0000 Received: from localhost (localhost [127.0.0.1]) by mx1.mbs-systems.net (Postfix) with ESMTP id D87985C30B; Sun, 9 Sep 2012 21:38:52 +0200 (CEST) Received: from mx1.mbs-systems.net ([127.0.0.1]) by localhost (mta.mbs-systems.net [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id GR92Nvu22bm8; Sun, 9 Sep 2012 21:38:52 +0200 (CEST) Received: from maiks-macbookpro.fritz.box (dslb-092-072-030-114.pools.arcor-ip.net [92.72.30.114]) by mx1.mbs-systems.net (Postfix) with ESMTPSA id 59F235C215; Sun, 9 Sep 2012 21:38:52 +0200 (CEST) Mime-Version: 1.0 (Apple Message framework v1278) From: Maik Brauer In-Reply-To: Date: Sun, 9 Sep 2012 21:37:51 +0200 Message-Id: <35537B6A-D4DF-4F1B-B2A1-861CB2B0C0A3@mbs-systems.net> References: <9F8FD2B0-450A-4A6E-A929-BA240ED1D997@mbs-systems.net> <1346746297.32462.37.camel@zakaz.uk.xensource.com> To: Ian Campbell X-Mailer: Apple Mail (2.1278) Cc: "xen-users@lists.xen.org" , Casey DeLorme Subject: Re: [Xen-users] Dom0 crashed when rebooting whilst DomU are running X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org On Sep 8, 2012, at 4:50 PM, Maik Brauer wrote: > > On Sep 4, 2012, at 10:11 AM, Ian Campbell wrote: > >> Could you not top post please, it makes it rather hard to follow the >> flow of the conversation. >> On Mon, 2012-09-03 at 18:10 +0100, Casey DeLorme wrote: >>> As stated, you can alias shutdown to do exactly what you need, it can >>> be as simple as a series of hard-coded operations to a complex custom >>> shell script that parses your domains and closes each with feedback. >> >> Xen ships the "xendomains" initscript which can halt guest on shutdown >> as well as automatically start specific guests on boot. It can also be >> configured to suspend/resume them or (I think) migrate them away. >> >> For diagnosing the crash itself more details will be required than were >> provided in the original post. Please see >> http://wiki.xen.org/wiki/Reporting_Bugs_against_Xen for some guidance. >> At a minimum we would need a capture (serial console or photo) of the >> crash backtrace. >> >> Ian. >> >> > I found out that it hangs during re-boot of dom0 when having more Network interfaces involved, like: > vif = [ 'mac=06:46:AB:CC:11:01, ip=', '', '', 'mac=06:04:AB:BB:11:03, bridge=VLAN20, script=vif-bridge', '', 'mac=06:04:AB:BB:11:05, bridge=VLAN40, script=vif-bridge' ] > > in case you use just one or having the basic line in place, it is working: > vif = [ '' ] > > The system stops after initiating the reboot at the following line in the console: System will restart........... > > In the Logfile of /var/log/message you can find this as the last line: > Sep 8 15:44:28 rootsrv01 shutdown[2445]: shutting down for system reboot > Sep 8 15:44:31 rootsrv01 kernel: [ 73.716246] VLAN20: port 1(vif2.3) entering forwarding state > Sep 8 15:44:31 rootsrv01 kernel: [ 74.500111] VLAN40: port 1(vif2.5) entering forwarding state > Sep 8 15:44:34 rootsrv01 kernel: [ 77.317431] VLAN20: port 1(vif2.3) entering disabled state > Sep 8 15:44:34 rootsrv01 kernel: [ 77.317490] VLAN20: port 1(vif2.3) entering disabled state > Sep 8 15:44:36 rootsrv01 kernel: [ 79.368685] VLAN40: port 1(vif2.5) entering disabled state > Sep 8 15:44:36 rootsrv01 kernel: [ 79.369156] VLAN40: port 1(vif2.5) entering disabled state > Sep 8 15:44:37 rootsrv01 kernel: Kernel logging (proc) stopped. > Sep 8 15:44:37 rootsrv01 rsyslogd: [origin software="rsyslogd" swVersion="4.6.4" x-pid="890" x-info="http://www.rsyslog.com"] exiting on signal 15. > > In the /var/log/daemong.log you can find this message: > Sep 8 15:44:37 rootsrv01 acpid: exiting > Sep 8 15:44:37 rootsrv01 rpc.statd[750]: Caught signal 15, un-registering and exiting > Sep 8 15:44:37 rootsrv01 udevd-work[2276]: '/etc/xen/scripts/vif-setup offline type_if=vif' unexpected exit with status 0x000f > > Cheers, > Maik > Hi Ian, I found an interesting article in the internet, having exact the same issue: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=630984 Can you confirm. >> >> >> _______________________________________________ >> Xen-users mailing list >> Xen-users@lists.xen.org >> http://lists.xen.org/xen-users > > > > _______________________________________________ > Xen-users mailing list > Xen-users@lists.xen.org > http://lists.xen.org/xen-users _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Sun Sep 09 19:39:35 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Sun, 09 Sep 2012 19:39:35 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TAnKO-00046z-V2; Sun, 09 Sep 2012 19:37:56 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TAnKN-00046u-BS for xen-users@lists.xen.org; Sun, 09 Sep 2012 19:37:55 +0000 Received: from [85.158.139.83:59715] by server-3.bemta-5.messagelabs.com id 88/EA-21836-210FC405; Sun, 09 Sep 2012 19:37:54 +0000 X-Env-Sender: maik.brauer@mbs-systems.net X-Msg-Ref: server-4.tower-182.messagelabs.com!1347219473!24929094!1 X-Originating-IP: [188.40.240.248] X-SpamReason: No, hits=0.0 required=7.0 tests= X-StarScan-Received: X-StarScan-Version: 6.6.1.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 374 invoked from network); 9 Sep 2012 19:37:53 -0000 Received: from mx1.mbs-systems.net (HELO mx1.mbs-systems.net) (188.40.240.248) by server-4.tower-182.messagelabs.com with SMTP; 9 Sep 2012 19:37:53 -0000 Received: from localhost (localhost [127.0.0.1]) by mx1.mbs-systems.net (Postfix) with ESMTP id D87985C30B; Sun, 9 Sep 2012 21:38:52 +0200 (CEST) Received: from mx1.mbs-systems.net ([127.0.0.1]) by localhost (mta.mbs-systems.net [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id GR92Nvu22bm8; Sun, 9 Sep 2012 21:38:52 +0200 (CEST) Received: from maiks-macbookpro.fritz.box (dslb-092-072-030-114.pools.arcor-ip.net [92.72.30.114]) by mx1.mbs-systems.net (Postfix) with ESMTPSA id 59F235C215; Sun, 9 Sep 2012 21:38:52 +0200 (CEST) Mime-Version: 1.0 (Apple Message framework v1278) From: Maik Brauer In-Reply-To: Date: Sun, 9 Sep 2012 21:37:51 +0200 Message-Id: <35537B6A-D4DF-4F1B-B2A1-861CB2B0C0A3@mbs-systems.net> References: <9F8FD2B0-450A-4A6E-A929-BA240ED1D997@mbs-systems.net> <1346746297.32462.37.camel@zakaz.uk.xensource.com> To: Ian Campbell X-Mailer: Apple Mail (2.1278) Cc: "xen-users@lists.xen.org" , Casey DeLorme Subject: Re: [Xen-users] Dom0 crashed when rebooting whilst DomU are running X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org On Sep 8, 2012, at 4:50 PM, Maik Brauer wrote: > > On Sep 4, 2012, at 10:11 AM, Ian Campbell wrote: > >> Could you not top post please, it makes it rather hard to follow the >> flow of the conversation. >> On Mon, 2012-09-03 at 18:10 +0100, Casey DeLorme wrote: >>> As stated, you can alias shutdown to do exactly what you need, it can >>> be as simple as a series of hard-coded operations to a complex custom >>> shell script that parses your domains and closes each with feedback. >> >> Xen ships the "xendomains" initscript which can halt guest on shutdown >> as well as automatically start specific guests on boot. It can also be >> configured to suspend/resume them or (I think) migrate them away. >> >> For diagnosing the crash itself more details will be required than were >> provided in the original post. Please see >> http://wiki.xen.org/wiki/Reporting_Bugs_against_Xen for some guidance. >> At a minimum we would need a capture (serial console or photo) of the >> crash backtrace. >> >> Ian. >> >> > I found out that it hangs during re-boot of dom0 when having more Network interfaces involved, like: > vif = [ 'mac=06:46:AB:CC:11:01, ip=', '', '', 'mac=06:04:AB:BB:11:03, bridge=VLAN20, script=vif-bridge', '', 'mac=06:04:AB:BB:11:05, bridge=VLAN40, script=vif-bridge' ] > > in case you use just one or having the basic line in place, it is working: > vif = [ '' ] > > The system stops after initiating the reboot at the following line in the console: System will restart........... > > In the Logfile of /var/log/message you can find this as the last line: > Sep 8 15:44:28 rootsrv01 shutdown[2445]: shutting down for system reboot > Sep 8 15:44:31 rootsrv01 kernel: [ 73.716246] VLAN20: port 1(vif2.3) entering forwarding state > Sep 8 15:44:31 rootsrv01 kernel: [ 74.500111] VLAN40: port 1(vif2.5) entering forwarding state > Sep 8 15:44:34 rootsrv01 kernel: [ 77.317431] VLAN20: port 1(vif2.3) entering disabled state > Sep 8 15:44:34 rootsrv01 kernel: [ 77.317490] VLAN20: port 1(vif2.3) entering disabled state > Sep 8 15:44:36 rootsrv01 kernel: [ 79.368685] VLAN40: port 1(vif2.5) entering disabled state > Sep 8 15:44:36 rootsrv01 kernel: [ 79.369156] VLAN40: port 1(vif2.5) entering disabled state > Sep 8 15:44:37 rootsrv01 kernel: Kernel logging (proc) stopped. > Sep 8 15:44:37 rootsrv01 rsyslogd: [origin software="rsyslogd" swVersion="4.6.4" x-pid="890" x-info="http://www.rsyslog.com"] exiting on signal 15. > > In the /var/log/daemong.log you can find this message: > Sep 8 15:44:37 rootsrv01 acpid: exiting > Sep 8 15:44:37 rootsrv01 rpc.statd[750]: Caught signal 15, un-registering and exiting > Sep 8 15:44:37 rootsrv01 udevd-work[2276]: '/etc/xen/scripts/vif-setup offline type_if=vif' unexpected exit with status 0x000f > > Cheers, > Maik > Hi Ian, I found an interesting article in the internet, having exact the same issue: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=630984 Can you confirm. >> >> >> _______________________________________________ >> Xen-users mailing list >> Xen-users@lists.xen.org >> http://lists.xen.org/xen-users > > > > _______________________________________________ > Xen-users mailing list > Xen-users@lists.xen.org > http://lists.xen.org/xen-users _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Sun Sep 09 20:25:16 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Sun, 09 Sep 2012 20:25:16 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TAo2z-00052F-8X; Sun, 09 Sep 2012 20:24:01 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TAo2x-00052A-Vu for xen-users@lists.xensource.com; Sun, 09 Sep 2012 20:24:00 +0000 Received: from [85.158.143.35:28859] by server-1.bemta-4.messagelabs.com id 19/68-12504-FDAFC405; Sun, 09 Sep 2012 20:23:59 +0000 X-Env-Sender: tknchris@gmail.com X-Msg-Ref: server-7.tower-21.messagelabs.com!1347222233!11948744!1 X-Originating-IP: [209.85.210.171] X-SpamReason: No, hits=0.9 required=7.0 tests=BODY_RANDOM_LONG, HTML_30_40, HTML_MESSAGE, ML_RADAR_SPEW_LINKS_14, RCVD_BY_IP, spamassassin: X-StarScan-Received: X-StarScan-Version: 6.6.1.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 32246 invoked from network); 9 Sep 2012 20:23:54 -0000 Received: from mail-iy0-f171.google.com (HELO mail-iy0-f171.google.com) (209.85.210.171) by server-7.tower-21.messagelabs.com with RC4-SHA encrypted SMTP; 9 Sep 2012 20:23:54 -0000 Received: by iabz25 with SMTP id z25so1505799iab.30 for ; Sun, 09 Sep 2012 13:23:53 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=yqQyUarDv2n4Jy3qlWbnnuvv+PiWenX1rKqr1BTmsFo=; b=j+3trhjDyyXcgWmpBwvMzs0ibp7Yv0BBLDFE0mvoyIT2lALokyJB6hhPbFDZzhbiBz OQDsyeX8RWf9tdUD1iYZiX4KYoVa45OAmOVIT+z/lgTH0H+yEWS5ft/BAJdpJ5vNuDOi S3d9sZSRFzX0dE/pkAkww0RQaFrDF6lHoJwR0sLuCIaoaWD7H4oyqI0CpNsS6EtDxW4X LSyO23gb8ttVaunjwjP0GXlGEZ26rnNED/M9XgDI61ITM1VUaCbGqrjS2S3TY9KYdP57 iLwCxXIarZur32iQkAEd0wyvwPDhMJvmhPf/BlkVvR3La8DXfMvrDZnashuCQuZfrmvC 4zwg== MIME-Version: 1.0 Received: by 10.50.10.225 with SMTP id l1mr7487463igb.66.1347222233235; Sun, 09 Sep 2012 13:23:53 -0700 (PDT) Received: by 10.64.58.46 with HTTP; Sun, 9 Sep 2012 13:23:53 -0700 (PDT) In-Reply-To: <1346229699.9975.30.camel@zakaz.uk.xensource.com> References: <1346164781.9975.27.camel@zakaz.uk.xensource.com> <1346229699.9975.30.camel@zakaz.uk.xensource.com> Date: Sun, 9 Sep 2012 16:23:53 -0400 Message-ID: From: chris To: Ian Campbell Content-Type: multipart/mixed; boundary=14dae9340e73a540c204c94a9e50 Cc: Xen-Users List Subject: Re: [Xen-users] pvhvm on debian X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org --14dae9340e73a540c204c94a9e50 Content-Type: multipart/alternative; boundary=14dae9340e73a540b204c94a9e4e --14dae9340e73a540b204c94a9e4e Content-Type: text/plain; charset=ISO-8859-1 Hi Ian, Finally got a chance to play with this again. Working box (squeeze dom0, centos domU) --- dom0 (squeeze) --- root@cyrax:~# dpkg -l | grep xen ii libxenstore3.0 4.0.1-4 Xenstore communications library for Xen ii linux-image-2.6.32-5-xen-amd64 2.6.32-45 Linux 2.6.32 for 64-bit PCs, Xen dom0 support ii xen-hypervisor-4.0-amd64 4.0.1-4 The Xen Hypervisor on AMD64 ii xen-linux-system-2.6-xen-amd64 2.6.32+29 Xen system with Linux 2.6 for 64-bit PCs (meta-package) ii xen-linux-system-2.6.32-5-xen-amd64 2.6.32-45 Xen system with Linux 2.6.32 on 64-bit PCs (meta-package) ii xen-qemu-dm-4.0 4.0.1-2+squeeze1 Xen Qemu Device Model virtual machine hardware emulator ii xen-utils-4.0 4.0.1-4 XEN administrative tools ii xen-utils-common 4.0.0-1 XEN administrative tools - common files ii xenstore-utils 4.0.1-4 Xenstore utilities for Xen root@cyrax:~# uname -a Linux cyrax 2.6.32-5-xen-amd64 #1 SMP Sun May 6 08:57:29 UTC 2012 x86_64 GNU/Linux working domU (centos) [root@sektor ~]# cat /etc/redhat-release CentOS release 5.5 (Final) [root@sektor ~]# uname -a Linux sektor 2.6.18-194.3.1.el5 #1 SMP Thu May 13 13:08:30 EDT 2010 x86_64 x86_64 x86_64 GNU/Linux [root@sektor ~]# lspci | grep Xen 00:03.0 Class ff80: XenSource, Inc. Xen Platform Device (rev 01) [root@sektor ~]# lsmod | grep xen xen_vnif 58817 0 [permanent] xen_vbd 50345 0 xen_balloon 45641 1 xen_vnif,[permanent] xen_platform_pci 117741 3 xen_vnif,xen_vbd,xen_balloon,[permanent] As you can see above the platform pci device shows in lspci and you can see in lsmod that the pv interfaces are being detected and used New box (wheezy, nonworking) root@barium:~# dpkg -l | grep xen ii libxen-4.1 4.1.3-1 amd64 Public libs for Xen ii libxenstore3.0 4.1.3-1 amd64 Xenstore communications library for Xen ii xen-hypervisor-4.1-amd64 4.1.3-1 amd64 Xen Hypervisor on AMD64 ii xen-system-amd64 4.1.3-1 amd64 Xen System on AMD64 (meta-package) ii xen-utils-4.1 4.1.3-1 amd64 XEN administrative tools ii xen-utils-common 4.1.3-1 all Xen administrative tools - common files ii xenstore-utils 4.1.3-1 amd64 Xenstore utilities for Xen root@barium:~# uname -a Linux barium 3.2.0-3-amd64 #1 SMP Mon Jul 23 02:45:17 UTC 2012 x86_64 GNU/Linux domU (centos) [root@baraka ~]# cat /etc/redhat-release CentOS release 5.5 (Final) [root@baraka ~]# uname -a Linux baraka 2.6.18-194.3.1.el5 #1 SMP Thu May 13 13:08:30 EDT 2010 x86_64 x86_64 x86_64 GNU/Linux [root@baraka ~]# lspci | grep Xen 00:03.0 Class ff80: XenSource, Inc. Xen Platform Device (rev 01) [root@baraka ~]# lsmod | grep xen xen_platform_pci 117741 0 [permanent] So as you can see the domU is identical kernel in both cases however when the domU is running on the wheezy dom0 even despite that the platform pci device appears exactly the same in lspci I've attached the configs and logs that you asked for Any ideas how to debug further? The difference between the working scenario and nonworking is the dom0 distro (squeeze vs wheezy), dom0 kernel and dom0 hypervisor Testing with both scenario's was done with the exact same domU so I cant see how it could be a domU issue. thanks chris On Wed, Aug 29, 2012 at 4:41 AM, Ian Campbell wrote: > On Tue, 2012-08-28 at 18:52 +0100, chris wrote: > > the issue seems to be with wheezy not squeeze im just trying to figure > > out why with wheezy with newer versions of everything pvhvm is not > > working. > > I upgraded my test Squeeze VM to Wheezy and PVHVM continued working > (this is on a fresh Wheezy dom0). > > > and in domU's I compared the lspci of the xen platform pci device to > > the lspci output from a working pvhvm domU that resides on a squeeze > > dom0. > > And they were identical? > > > so my guess is that its related to hypervisor? > > I don't think we have enough evidence to decide one way or the other. > > Can you provide the logs and guest configurations which I asked for > please. > > Ian. > > > --14dae9340e73a540b204c94a9e4e Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Hi Ian,

Finally got a chance to play with this again.=A0
=
Working box (squeeze dom0, centos domU)

=
--- dom0 (squeeze) ---
root@cyrax:~# dpkg -l | grep xen
ii =A0libxenstore3.0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A04= .0.1-4 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0Xenstore communications l= ibrary for Xen
ii =A0linux-image-2.6.32-5-xen-amd64 =A0 =A0 =A02.= 6.32-45 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0Linux 2.6.32 for 64-bit PCs,= Xen dom0 support
ii =A0xen-hypervisor-4.0-amd64 =A0 =A0 =A0 =A0 =A0 =A04.0.1-4 =A0 =A0 = =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0The Xen Hypervisor on AMD64
ii= =A0xen-linux-system-2.6-xen-amd64 =A0 =A0 =A02.6.32+29 =A0 =A0 =A0 =A0 =A0= =A0 =A0 =A0 =A0 =A0Xen system with Linux 2.6 for 64-bit PCs (meta-package)=
ii =A0xen-linux-system-2.6.32-5-xen-amd64 2.6.32-45 =A0 =A0 =A0 =A0 = =A0 =A0 =A0 =A0 =A0 =A0Xen system with Linux 2.6.32 on 64-bit PCs (meta-pac= kage)
ii =A0xen-qemu-dm-4.0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 = =A0 4.0.1-2+squeeze1 =A0 =A0 =A0 =A0 =A0 =A0 Xen Qemu Device Model virtual = machine hardware emulator
ii =A0xen-utils-4.0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 4.0.1-= 4 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0XEN administrative tools
=
ii =A0xen-utils-common =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A04.0.0-1 = =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0XEN administrative tools - commo= n files
ii =A0xenstore-utils =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A04.0.1-= 4 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0Xenstore utilities for Xen
root@cyrax:~# uname -a
Linux cyrax 2.6.32-5-xen-amd64= #1 SMP Sun May 6 08:57:29 UTC 2012 x86_64 GNU/Linux

working domU (centos)
[root@sektor= ~]# cat /etc/redhat-release
CentOS release 5.5 (Final)
[root@sektor ~]# uname -a
Linux sektor 2.6.18-194.3.1.el5 #1 SMP= Thu May 13 13:08:30 EDT 2010 x86_64 x86_64 x86_64 GNU/Linux
[root@sektor ~]# lspci | grep Xen
00:03.0 Class f= f80: XenSource, Inc. Xen Platform Device (rev 01)
[root@sektor ~]= # lsmod | grep xen
xen_vnif =A0 =A0 =A0 =A0 =A0 =A0 =A0 58817 =A0= 0 [permanent]
xen_vbd =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A050345 =A00
xen_balloo= n =A0 =A0 =A0 =A0 =A0 =A045641 =A01 xen_vnif,[permanent]
xen_plat= form_pci =A0 =A0 =A0117741 =A03 xen_vnif,xen_vbd,xen_balloon,[permanent]

As you can see above the platform pci device s= hows in lspci and you can see in lsmod that the pv interfaces are being det= ected and used

New box (wheezy, nonworking)

<= div>root@barium:~# dpkg -l | grep xen
ii =A0libxen-4.1 =A0 =A0 = =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 4.1.3-1 =A0 =A0 =A0 =A0 =A0 =A0 =A0= =A0 =A0 =A0amd64 =A0 =A0 =A0 =A0Public libs for Xen
ii =A0libxenstore3.0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 4.1.3-1 = =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0amd64 =A0 =A0 =A0 =A0Xenstore commun= ications library for Xen
ii =A0xen-hypervisor-4.1-amd64 =A0 =A0 = =A0 =A0 =A0 4.1.3-1 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0amd64 =A0 =A0 = =A0 =A0Xen Hypervisor on AMD64
ii =A0xen-system-amd64 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 4.1.3-1 =A0= =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0amd64 =A0 =A0 =A0 =A0Xen System on AMD6= 4 (meta-package)
ii =A0xen-utils-4.1 =A0 =A0 =A0 =A0 =A0 =A0 =A0 = =A0 =A0 =A0 =A04.1.3-1 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0amd64 =A0 =A0= =A0 =A0XEN administrative tools
ii =A0xen-utils-common =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 4.1.3-1 =A0= =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0all =A0 =A0 =A0 =A0 =A0Xen administrati= ve tools - common files
ii =A0xenstore-utils =A0 =A0 =A0 =A0 =A0 = =A0 =A0 =A0 =A0 =A0 4.1.3-1 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0amd64 = =A0 =A0 =A0 =A0Xenstore utilities for Xen
root@barium:~# uname -a
Linux barium 3.2.0-3-amd6= 4 #1 SMP Mon Jul 23 02:45:17 UTC 2012 x86_64 GNU/Linux

=
domU (centos)
[root@baraka ~]# cat /etc/redhat-re= lease
CentOS release 5.5 (Final)
[root@baraka ~]# uname= -a
Linux baraka 2.6.18-194.3.1.el5 #1 SMP Thu May 13 13:08:30 ED= T 2010 x86_64 x86_64 x86_64 GNU/Linux
[root@baraka ~]#= lspci | grep Xen
00:03.0 Class ff80: XenSource, Inc. Xen Platform Device (rev 01)
=
[root@baraka ~]# lsmod | grep xen
xen_platform_pc= i =A0 =A0 =A0117741 =A00 [permanent]

So as y= ou can see the domU is identical kernel in both cases however when the domU= is running on the wheezy dom0 even despite that the platform pci device ap= pears exactly the same in lspci=A0

I've attached the configs and logs that you asked f= or

Any ideas how to debug further? The difference = between the working scenario and nonworking is the dom0 distro (squeeze vs = wheezy), dom0 kernel and dom0 hypervisor
Testing with both scenario's was done with the exact same domU so = I cant see how it could be a domU issue.

thanks
chris

On Wed, Aug 29, 2012 at 4= :41 AM, Ian Campbell <Ian.Campbell@citrix.com> wrote:<= br>
On Tue, 2012-08-28 at 18:5= 2 +0100, chris wrote:
> the issue seems to be with wheezy not squeeze im just trying to figure=
> out why with wheezy with newer versions of everything pvhvm is not
> working.

I upgraded my test Squeeze VM to Wheezy and PVHVM continued working (this is on a fresh Wheezy dom0).

> and in domU's I compared the lspci of the xen platform pci device = to
> the lspci output from a working pvhvm domU that resides on a squeeze > dom0.

And they were identical?

> so my guess is that its related to hypervisor?

I don't think we have enough evidence to decide one way or the ot= her.

Can you provide the logs and guest configurations which I asked for
please.

Ian.



--14dae9340e73a540b204c94a9e4e-- --14dae9340e73a540c204c94a9e50 Content-Type: text/plain; charset=US-ASCII; name="baraka-qemu.txt" Content-Disposition: attachment; filename="baraka-qemu.txt" Content-Transfer-Encoding: base64 X-Attachment-Id: f_h6wlbamh2 cm9vdEBiYXJpdW06L3Zhci9sb2cveGVuIyBjYXQgcWVtdS1kbS12bS1iYXJha2EubG9nDQpkb21p ZDogMTcNCi1jIGNvbmZpZyBxZW11IG5ldHdvcmsgd2l0aCB4ZW4gYnJpZGdlIGZvcg0KdmlmMTcu MC1lbXUgdm0tYmFyYWthLWxhbg0KVXNpbmcgZmlsZSAvZGV2L3N0b3JhZ2Uvdm0tYmFyYWthIGlu IHJlYWQtd3JpdGUgbW9kZQ0KV2F0Y2hpbmcgL2xvY2FsL2RvbWFpbi8wL2RldmljZS1tb2RlbC8x Ny9sb2dkaXJ0eS9jbWQNCldhdGNoaW5nIC9sb2NhbC9kb21haW4vMC9kZXZpY2UtbW9kZWwvMTcv Y29tbWFuZA0KV2F0Y2hpbmcgL2xvY2FsL2RvbWFpbi8xNy9jcHUNCnFlbXVfbWFwX2NhY2hlX2lu aXQgbnJfYnVja2V0cyA9IDEwMDAwIHNpemUgNDE5NDMwNA0Kc2hhcmVkIHBhZ2UgYXQgcGZuIGZl ZmZkDQpidWZmZXJlZCBpbyBwYWdlIGF0IHBmbiBmZWZmYg0KR3Vlc3QgdXVpZCA9IDZkNDdlZjc0 LTkwYjYtNzE1YS1iYTI2LWU4ZjlmMzA0YWEzNw0KVGltZSBvZmZzZXQgc2V0IDANCnBvcHVsYXRp bmcgdmlkZW8gUkFNIGF0IGZmMDAwMDAwDQptYXBwaW5nIHZpZGVvIFJBTSBmcm9tIGZmMDAwMDAw DQpSZWdpc3RlciB4ZW4gcGxhdGZvcm0uDQpEb25lIHJlZ2lzdGVyIHBsYXRmb3JtLg0KcGxhdGZv cm1fZml4ZWRfaW9wb3J0OiBjaGFuZ2VkIHJvL3J3IHN0YXRlIG9mIFJPTSBtZW1vcnkgYXJlYS4g bm93IGlzIHJ3IHN0YXRlLg0KeHNfcmVhZCgvbG9jYWwvZG9tYWluLzAvZGV2aWNlLW1vZGVsLzE3 L3hlbl9leHRlbmRlZF9wb3dlcl9tZ210KTogcmVhZCBlcnJvcg0KSS9PIHJlcXVlc3Qgbm90IHJl YWR5OiAwLCBwdHI6IDAsIHBvcnQ6IDAsIGRhdGE6IDAsIGNvdW50OiAwLCBzaXplOiAwDQpMb2ct ZGlydHk6IG5vIGNvbW1hbmQgeWV0Lg0KdmNwdS1zZXQ6IHdhdGNoIG5vZGUgZXJyb3IuDQp4c19y ZWFkKC9sb2NhbC9kb21haW4vMTcvbG9nLXRocm90dGxpbmcpOiByZWFkIGVycm9yDQpxZW11OiBp Z25vcmluZyBub3QtdW5kZXJzdG9vZCBkcml2ZSBgL2xvY2FsL2RvbWFpbi8xNy9sb2ctdGhyb3R0 bGluZycNCm1lZGl1bSBjaGFuZ2Ugd2F0Y2ggb24gYC9sb2NhbC9kb21haW4vMTcvbG9nLXRocm90 dGxpbmcnIC0gdW5rbm93biBkZXZpY2UsIGlnbm9yZWQNCmNoYXIgZGV2aWNlIHJlZGlyZWN0ZWQg dG8gL2Rldi9wdHMvMA0KeGVuIGJlOiBjb25zb2xlLTA6IHhlbiBiZTogY29uc29sZS0wOiBpbml0 aWFsaXNlKCkgZmFpbGVkDQppbml0aWFsaXNlKCkgZmFpbGVkDQp4ZW4gYmU6IGNvbnNvbGUtMDog eGVuIGJlOiBjb25zb2xlLTA6IGluaXRpYWxpc2UoKSBmYWlsZWQNCmluaXRpYWxpc2UoKSBmYWls ZWQNCnhlbiBiZTogY29uc29sZS0wOiB4ZW4gYmU6IGNvbnNvbGUtMDogaW5pdGlhbGlzZSgpIGZh aWxlZA0KaW5pdGlhbGlzZSgpIGZhaWxlZA0KeGVuIGJlOiBjb25zb2xlLTA6IHhlbiBiZTogY29u c29sZS0wOiBpbml0aWFsaXNlKCkgZmFpbGVkDQppbml0aWFsaXNlKCkgZmFpbGVkDQp4ZW4gYmU6 IGNvbnNvbGUtMDogeGVuIGJlOiBjb25zb2xlLTA6IGluaXRpYWxpc2UoKSBmYWlsZWQNCmluaXRp YWxpc2UoKSBmYWlsZWQNCnhlbiBiZTogY29uc29sZS0wOiB4ZW4gYmU6IGNvbnNvbGUtMDogaW5p dGlhbGlzZSgpIGZhaWxlZA0KaW5pdGlhbGlzZSgpIGZhaWxlZA0KeGVuIGJlOiBjb25zb2xlLTA6 IHhlbiBiZTogY29uc29sZS0wOiBpbml0aWFsaXNlKCkgZmFpbGVkDQppbml0aWFsaXNlKCkgZmFp bGVkDQp4ZW4gYmU6IGNvbnNvbGUtMDogeGVuIGJlOiBjb25zb2xlLTA6IGluaXRpYWxpc2UoKSBm YWlsZWQNCmluaXRpYWxpc2UoKSBmYWlsZWQNCnhlbiBiZTogY29uc29sZS0wOiB4ZW4gYmU6IGNv bnNvbGUtMDogaW5pdGlhbGlzZSgpIGZhaWxlZA0KaW5pdGlhbGlzZSgpIGZhaWxlZA0KeGVuIGJl OiBjb25zb2xlLTA6IHhlbiBiZTogY29uc29sZS0wOiBpbml0aWFsaXNlKCkgZmFpbGVkDQppbml0 aWFsaXNlKCkgZmFpbGVkDQp4ZW4gYmU6IGNvbnNvbGUtMDogeGVuIGJlOiBjb25zb2xlLTA6IGlu aXRpYWxpc2UoKSBmYWlsZWQNCmluaXRpYWxpc2UoKSBmYWlsZWQNCnhlbiBiZTogY29uc29sZS0w OiB4ZW4gYmU6IGNvbnNvbGUtMDogaW5pdGlhbGlzZSgpIGZhaWxlZA0KaW5pdGlhbGlzZSgpIGZh aWxlZA0KY2lycnVzIHZnYSBtYXAgY2hhbmdlIHdoaWxlIG9uIGxmYiBtb2RlDQptYXBwaW5nIHZy YW0gdG8gZjAwMDAwMDAgLSBmMDQwMDAwMA0KcGxhdGZvcm1fZml4ZWRfaW9wb3J0OiBjaGFuZ2Vk IHJvL3J3IHN0YXRlIG9mIFJPTSBtZW1vcnkgYXJlYS4gbm93IGlzIHJ3IHN0YXRlLg0KcGxhdGZv cm1fZml4ZWRfaW9wb3J0OiBjaGFuZ2VkIHJvL3J3IHN0YXRlIG9mIFJPTSBtZW1vcnkgYXJlYS4g bm93IGlzIHJvIHN0YXRlLg0K --14dae9340e73a540c204c94a9e50 Content-Type: application/octet-stream; name="vm-baraka.cfg" Content-Disposition: attachment; filename="vm-baraka.cfg" Content-Transfer-Encoding: base64 X-Attachment-Id: f_h6wlazpt0 a2VybmVsID0gJy91c3IvbGliL3hlbi9ib290L2h2bWxvYWRlcicNCmJ1aWxkZXIgPSAnaHZtJw0K bWVtb3J5ID0gJzc2OCcNCmRldmljZV9tb2RlbD0nL3Vzci9saWIveGVuL2Jpbi9xZW11LWRtJw0K IyBEaXNrcw0KZGlzayA9IFsgJ3BoeTovZGV2L3N0b3JhZ2Uvdm0tYmFyYWthLGlvZW11OmhkYSx3 JywNCl0NCg0KIyBIb3N0bmFtZQ0KbmFtZSA9ICd2bS1iYXJha2EnDQoNCiMgTmV0d29ya2luZw0K dmlmID0gWyd0eXBlPWlvZW11LCBicmlkZ2U9dm0tYmFyYWthLWxhbiwgbWFjPTAwOjE3OjcxOjM3 OjU4OkVFJ10NCg0KIyBCZWhhdmlvdXINCmJvb3Q9J2MnDQp2Y3B1cz0xDQphY3BpPTENCmFwaWM9 MQ0KYWhjaT0xDQp2bmM9MQ0Kdm5jdmlld2VyPTENCnNkbD0wDQp1c2I9MQ0KdXNiZGV2aWNlPSd0 YWJsZXQnDQp0aW1lcl9tb2RlPTENCnhlbl9wbGF0Zm9ybV9wY2k9MQ0K --14dae9340e73a540c204c94a9e50 Content-Type: application/octet-stream; name="vm-sektor.cfg" Content-Disposition: attachment; filename="vm-sektor.cfg" Content-Transfer-Encoding: base64 X-Attachment-Id: f_h6wlb41m1 a2VybmVsID0gJy91c3IvbGliL3hlbi9ib290L2h2bWxvYWRlcicNCmJ1aWxkZXIgPSAnaHZtJw0K bWVtb3J5ID0gJzc2OCcNCmRldmljZV9tb2RlbD0nL3Vzci9saWIveGVuL2Jpbi9xZW11LWRtJw0K IyBEaXNrcw0KZGlzayA9IFsgJ3BoeTovZGV2L3N0b3JhZ2Uvdm0tc2VrdG9yLGlvZW11OmhkYSx3 JywNCl0NCg0KIyBIb3N0bmFtZQ0KbmFtZSA9ICd2bS1zZWt0b3InDQoNCiMgTmV0d29ya2luZw0K dmlmID0gWyd0eXBlPWlvZW11LCBicmlkZ2U9dm0tc2VrdG9yLWxhbiwgdmlmbmFtZT12bS1zZWt0 b3IsIG1hYz0wMDoxNjozRDozNzpCMjpBQSddDQoNCiMgQmVoYXZpb3VyDQpib290PSdjJw0KdmNw dXM9MQ0KYWNwaT0xDQphaGNpPTENCnZuYz0xDQp2bmN2aWV3ZXI9MQ0Kc2RsPTANCnRpbWVyX21v ZGU9MQ0KdXNiPTENCnVzYmRldmljZT0ndGFibGV0Jw0KeGVuX3BsYXRmb3JtX3BjaT0xDQo= --14dae9340e73a540c204c94a9e50 Content-Type: text/plain; charset=US-ASCII; name="sektor-qemu.txt" Content-Disposition: attachment; filename="sektor-qemu.txt" Content-Transfer-Encoding: base64 X-Attachment-Id: f_h6wlbdch3 cm9vdEBiYXJpdW06L3Zhci9sb2cveGVuIyBjYXQgcWVtdS1kbS12bS1iYXJha2EubG9nDQpkb21p ZDogMTcNCi1jIGNvbmZpZyBxZW11IG5ldHdvcmsgd2l0aCB4ZW4gYnJpZGdlIGZvcg0KdmlmMTcu MC1lbXUgdm0tYmFyYWthLWxhbg0KVXNpbmcgZmlsZSAvZGV2L3N0b3JhZ2Uvdm0tYmFyYWthIGlu IHJlYWQtd3JpdGUgbW9kZQ0KV2F0Y2hpbmcgL2xvY2FsL2RvbWFpbi8wL2RldmljZS1tb2RlbC8x Ny9sb2dkaXJ0eS9jbWQNCldhdGNoaW5nIC9sb2NhbC9kb21haW4vMC9kZXZpY2UtbW9kZWwvMTcv Y29tbWFuZA0KV2F0Y2hpbmcgL2xvY2FsL2RvbWFpbi8xNy9jcHUNCnFlbXVfbWFwX2NhY2hlX2lu aXQgbnJfYnVja2V0cyA9IDEwMDAwIHNpemUgNDE5NDMwNA0Kc2hhcmVkIHBhZ2UgYXQgcGZuIGZl ZmZkDQpidWZmZXJlZCBpbyBwYWdlIGF0IHBmbiBmZWZmYg0KR3Vlc3QgdXVpZCA9IDZkNDdlZjc0 LTkwYjYtNzE1YS1iYTI2LWU4ZjlmMzA0YWEzNw0KVGltZSBvZmZzZXQgc2V0IDANCnBvcHVsYXRp bmcgdmlkZW8gUkFNIGF0IGZmMDAwMDAwDQptYXBwaW5nIHZpZGVvIFJBTSBmcm9tIGZmMDAwMDAw DQpSZWdpc3RlciB4ZW4gcGxhdGZvcm0uDQpEb25lIHJlZ2lzdGVyIHBsYXRmb3JtLg0KcGxhdGZv cm1fZml4ZWRfaW9wb3J0OiBjaGFuZ2VkIHJvL3J3IHN0YXRlIG9mIFJPTSBtZW1vcnkgYXJlYS4g bm93IGlzIHJ3IHN0YXRlLg0KeHNfcmVhZCgvbG9jYWwvZG9tYWluLzAvZGV2aWNlLW1vZGVsLzE3 L3hlbl9leHRlbmRlZF9wb3dlcl9tZ210KTogcmVhZCBlcnJvcg0KSS9PIHJlcXVlc3Qgbm90IHJl YWR5OiAwLCBwdHI6IDAsIHBvcnQ6IDAsIGRhdGE6IDAsIGNvdW50OiAwLCBzaXplOiAwDQpMb2ct ZGlydHk6IG5vIGNvbW1hbmQgeWV0Lg0KdmNwdS1zZXQ6IHdhdGNoIG5vZGUgZXJyb3IuDQp4c19y ZWFkKC9sb2NhbC9kb21haW4vMTcvbG9nLXRocm90dGxpbmcpOiByZWFkIGVycm9yDQpxZW11OiBp Z25vcmluZyBub3QtdW5kZXJzdG9vZCBkcml2ZSBgL2xvY2FsL2RvbWFpbi8xNy9sb2ctdGhyb3R0 bGluZycNCm1lZGl1bSBjaGFuZ2Ugd2F0Y2ggb24gYC9sb2NhbC9kb21haW4vMTcvbG9nLXRocm90 dGxpbmcnIC0gdW5rbm93biBkZXZpY2UsIGlnbm9yZWQNCmNoYXIgZGV2aWNlIHJlZGlyZWN0ZWQg dG8gL2Rldi9wdHMvMA0KeGVuIGJlOiBjb25zb2xlLTA6IHhlbiBiZTogY29uc29sZS0wOiBpbml0 aWFsaXNlKCkgZmFpbGVkDQppbml0aWFsaXNlKCkgZmFpbGVkDQp4ZW4gYmU6IGNvbnNvbGUtMDog eGVuIGJlOiBjb25zb2xlLTA6IGluaXRpYWxpc2UoKSBmYWlsZWQNCmluaXRpYWxpc2UoKSBmYWls ZWQNCnhlbiBiZTogY29uc29sZS0wOiB4ZW4gYmU6IGNvbnNvbGUtMDogaW5pdGlhbGlzZSgpIGZh aWxlZA0KaW5pdGlhbGlzZSgpIGZhaWxlZA0KeGVuIGJlOiBjb25zb2xlLTA6IHhlbiBiZTogY29u c29sZS0wOiBpbml0aWFsaXNlKCkgZmFpbGVkDQppbml0aWFsaXNlKCkgZmFpbGVkDQp4ZW4gYmU6 IGNvbnNvbGUtMDogeGVuIGJlOiBjb25zb2xlLTA6IGluaXRpYWxpc2UoKSBmYWlsZWQNCmluaXRp YWxpc2UoKSBmYWlsZWQNCnhlbiBiZTogY29uc29sZS0wOiB4ZW4gYmU6IGNvbnNvbGUtMDogaW5p dGlhbGlzZSgpIGZhaWxlZA0KaW5pdGlhbGlzZSgpIGZhaWxlZA0KeGVuIGJlOiBjb25zb2xlLTA6 IHhlbiBiZTogY29uc29sZS0wOiBpbml0aWFsaXNlKCkgZmFpbGVkDQppbml0aWFsaXNlKCkgZmFp bGVkDQp4ZW4gYmU6IGNvbnNvbGUtMDogeGVuIGJlOiBjb25zb2xlLTA6IGluaXRpYWxpc2UoKSBm YWlsZWQNCmluaXRpYWxpc2UoKSBmYWlsZWQNCnhlbiBiZTogY29uc29sZS0wOiB4ZW4gYmU6IGNv bnNvbGUtMDogaW5pdGlhbGlzZSgpIGZhaWxlZA0KaW5pdGlhbGlzZSgpIGZhaWxlZA0KeGVuIGJl OiBjb25zb2xlLTA6IHhlbiBiZTogY29uc29sZS0wOiBpbml0aWFsaXNlKCkgZmFpbGVkDQppbml0 aWFsaXNlKCkgZmFpbGVkDQp4ZW4gYmU6IGNvbnNvbGUtMDogeGVuIGJlOiBjb25zb2xlLTA6IGlu aXRpYWxpc2UoKSBmYWlsZWQNCmluaXRpYWxpc2UoKSBmYWlsZWQNCnhlbiBiZTogY29uc29sZS0w OiB4ZW4gYmU6IGNvbnNvbGUtMDogaW5pdGlhbGlzZSgpIGZhaWxlZA0KaW5pdGlhbGlzZSgpIGZh aWxlZA0KY2lycnVzIHZnYSBtYXAgY2hhbmdlIHdoaWxlIG9uIGxmYiBtb2RlDQptYXBwaW5nIHZy YW0gdG8gZjAwMDAwMDAgLSBmMDQwMDAwMA0KcGxhdGZvcm1fZml4ZWRfaW9wb3J0OiBjaGFuZ2Vk IHJvL3J3IHN0YXRlIG9mIFJPTSBtZW1vcnkgYXJlYS4gbm93IGlzIHJ3IHN0YXRlLg0KcGxhdGZv cm1fZml4ZWRfaW9wb3J0OiBjaGFuZ2VkIHJvL3J3IHN0YXRlIG9mIFJPTSBtZW1vcnkgYXJlYS4g bm93IGlzIHJvIHN0YXRlLg0K --14dae9340e73a540c204c94a9e50 Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users --14dae9340e73a540c204c94a9e50-- From xen-users-bounces@lists.xen.org Sun Sep 09 20:25:16 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Sun, 09 Sep 2012 20:25:16 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TAo2z-00052F-8X; Sun, 09 Sep 2012 20:24:01 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TAo2x-00052A-Vu for xen-users@lists.xensource.com; Sun, 09 Sep 2012 20:24:00 +0000 Received: from [85.158.143.35:28859] by server-1.bemta-4.messagelabs.com id 19/68-12504-FDAFC405; Sun, 09 Sep 2012 20:23:59 +0000 X-Env-Sender: tknchris@gmail.com X-Msg-Ref: server-7.tower-21.messagelabs.com!1347222233!11948744!1 X-Originating-IP: [209.85.210.171] X-SpamReason: No, hits=0.9 required=7.0 tests=BODY_RANDOM_LONG, HTML_30_40, HTML_MESSAGE, ML_RADAR_SPEW_LINKS_14, RCVD_BY_IP, spamassassin: X-StarScan-Received: X-StarScan-Version: 6.6.1.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 32246 invoked from network); 9 Sep 2012 20:23:54 -0000 Received: from mail-iy0-f171.google.com (HELO mail-iy0-f171.google.com) (209.85.210.171) by server-7.tower-21.messagelabs.com with RC4-SHA encrypted SMTP; 9 Sep 2012 20:23:54 -0000 Received: by iabz25 with SMTP id z25so1505799iab.30 for ; Sun, 09 Sep 2012 13:23:53 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=yqQyUarDv2n4Jy3qlWbnnuvv+PiWenX1rKqr1BTmsFo=; b=j+3trhjDyyXcgWmpBwvMzs0ibp7Yv0BBLDFE0mvoyIT2lALokyJB6hhPbFDZzhbiBz OQDsyeX8RWf9tdUD1iYZiX4KYoVa45OAmOVIT+z/lgTH0H+yEWS5ft/BAJdpJ5vNuDOi S3d9sZSRFzX0dE/pkAkww0RQaFrDF6lHoJwR0sLuCIaoaWD7H4oyqI0CpNsS6EtDxW4X LSyO23gb8ttVaunjwjP0GXlGEZ26rnNED/M9XgDI61ITM1VUaCbGqrjS2S3TY9KYdP57 iLwCxXIarZur32iQkAEd0wyvwPDhMJvmhPf/BlkVvR3La8DXfMvrDZnashuCQuZfrmvC 4zwg== MIME-Version: 1.0 Received: by 10.50.10.225 with SMTP id l1mr7487463igb.66.1347222233235; Sun, 09 Sep 2012 13:23:53 -0700 (PDT) Received: by 10.64.58.46 with HTTP; Sun, 9 Sep 2012 13:23:53 -0700 (PDT) In-Reply-To: <1346229699.9975.30.camel@zakaz.uk.xensource.com> References: <1346164781.9975.27.camel@zakaz.uk.xensource.com> <1346229699.9975.30.camel@zakaz.uk.xensource.com> Date: Sun, 9 Sep 2012 16:23:53 -0400 Message-ID: From: chris To: Ian Campbell Content-Type: multipart/mixed; boundary=14dae9340e73a540c204c94a9e50 Cc: Xen-Users List Subject: Re: [Xen-users] pvhvm on debian X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org --14dae9340e73a540c204c94a9e50 Content-Type: multipart/alternative; boundary=14dae9340e73a540b204c94a9e4e --14dae9340e73a540b204c94a9e4e Content-Type: text/plain; charset=ISO-8859-1 Hi Ian, Finally got a chance to play with this again. Working box (squeeze dom0, centos domU) --- dom0 (squeeze) --- root@cyrax:~# dpkg -l | grep xen ii libxenstore3.0 4.0.1-4 Xenstore communications library for Xen ii linux-image-2.6.32-5-xen-amd64 2.6.32-45 Linux 2.6.32 for 64-bit PCs, Xen dom0 support ii xen-hypervisor-4.0-amd64 4.0.1-4 The Xen Hypervisor on AMD64 ii xen-linux-system-2.6-xen-amd64 2.6.32+29 Xen system with Linux 2.6 for 64-bit PCs (meta-package) ii xen-linux-system-2.6.32-5-xen-amd64 2.6.32-45 Xen system with Linux 2.6.32 on 64-bit PCs (meta-package) ii xen-qemu-dm-4.0 4.0.1-2+squeeze1 Xen Qemu Device Model virtual machine hardware emulator ii xen-utils-4.0 4.0.1-4 XEN administrative tools ii xen-utils-common 4.0.0-1 XEN administrative tools - common files ii xenstore-utils 4.0.1-4 Xenstore utilities for Xen root@cyrax:~# uname -a Linux cyrax 2.6.32-5-xen-amd64 #1 SMP Sun May 6 08:57:29 UTC 2012 x86_64 GNU/Linux working domU (centos) [root@sektor ~]# cat /etc/redhat-release CentOS release 5.5 (Final) [root@sektor ~]# uname -a Linux sektor 2.6.18-194.3.1.el5 #1 SMP Thu May 13 13:08:30 EDT 2010 x86_64 x86_64 x86_64 GNU/Linux [root@sektor ~]# lspci | grep Xen 00:03.0 Class ff80: XenSource, Inc. Xen Platform Device (rev 01) [root@sektor ~]# lsmod | grep xen xen_vnif 58817 0 [permanent] xen_vbd 50345 0 xen_balloon 45641 1 xen_vnif,[permanent] xen_platform_pci 117741 3 xen_vnif,xen_vbd,xen_balloon,[permanent] As you can see above the platform pci device shows in lspci and you can see in lsmod that the pv interfaces are being detected and used New box (wheezy, nonworking) root@barium:~# dpkg -l | grep xen ii libxen-4.1 4.1.3-1 amd64 Public libs for Xen ii libxenstore3.0 4.1.3-1 amd64 Xenstore communications library for Xen ii xen-hypervisor-4.1-amd64 4.1.3-1 amd64 Xen Hypervisor on AMD64 ii xen-system-amd64 4.1.3-1 amd64 Xen System on AMD64 (meta-package) ii xen-utils-4.1 4.1.3-1 amd64 XEN administrative tools ii xen-utils-common 4.1.3-1 all Xen administrative tools - common files ii xenstore-utils 4.1.3-1 amd64 Xenstore utilities for Xen root@barium:~# uname -a Linux barium 3.2.0-3-amd64 #1 SMP Mon Jul 23 02:45:17 UTC 2012 x86_64 GNU/Linux domU (centos) [root@baraka ~]# cat /etc/redhat-release CentOS release 5.5 (Final) [root@baraka ~]# uname -a Linux baraka 2.6.18-194.3.1.el5 #1 SMP Thu May 13 13:08:30 EDT 2010 x86_64 x86_64 x86_64 GNU/Linux [root@baraka ~]# lspci | grep Xen 00:03.0 Class ff80: XenSource, Inc. Xen Platform Device (rev 01) [root@baraka ~]# lsmod | grep xen xen_platform_pci 117741 0 [permanent] So as you can see the domU is identical kernel in both cases however when the domU is running on the wheezy dom0 even despite that the platform pci device appears exactly the same in lspci I've attached the configs and logs that you asked for Any ideas how to debug further? The difference between the working scenario and nonworking is the dom0 distro (squeeze vs wheezy), dom0 kernel and dom0 hypervisor Testing with both scenario's was done with the exact same domU so I cant see how it could be a domU issue. thanks chris On Wed, Aug 29, 2012 at 4:41 AM, Ian Campbell wrote: > On Tue, 2012-08-28 at 18:52 +0100, chris wrote: > > the issue seems to be with wheezy not squeeze im just trying to figure > > out why with wheezy with newer versions of everything pvhvm is not > > working. > > I upgraded my test Squeeze VM to Wheezy and PVHVM continued working > (this is on a fresh Wheezy dom0). > > > and in domU's I compared the lspci of the xen platform pci device to > > the lspci output from a working pvhvm domU that resides on a squeeze > > dom0. > > And they were identical? > > > so my guess is that its related to hypervisor? > > I don't think we have enough evidence to decide one way or the other. > > Can you provide the logs and guest configurations which I asked for > please. > > Ian. > > > --14dae9340e73a540b204c94a9e4e Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Hi Ian,

Finally got a chance to play with this again.=A0
=
Working box (squeeze dom0, centos domU)

=
--- dom0 (squeeze) ---
root@cyrax:~# dpkg -l | grep xen
ii =A0libxenstore3.0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A04= .0.1-4 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0Xenstore communications l= ibrary for Xen
ii =A0linux-image-2.6.32-5-xen-amd64 =A0 =A0 =A02.= 6.32-45 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0Linux 2.6.32 for 64-bit PCs,= Xen dom0 support
ii =A0xen-hypervisor-4.0-amd64 =A0 =A0 =A0 =A0 =A0 =A04.0.1-4 =A0 =A0 = =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0The Xen Hypervisor on AMD64
ii= =A0xen-linux-system-2.6-xen-amd64 =A0 =A0 =A02.6.32+29 =A0 =A0 =A0 =A0 =A0= =A0 =A0 =A0 =A0 =A0Xen system with Linux 2.6 for 64-bit PCs (meta-package)=
ii =A0xen-linux-system-2.6.32-5-xen-amd64 2.6.32-45 =A0 =A0 =A0 =A0 = =A0 =A0 =A0 =A0 =A0 =A0Xen system with Linux 2.6.32 on 64-bit PCs (meta-pac= kage)
ii =A0xen-qemu-dm-4.0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 = =A0 4.0.1-2+squeeze1 =A0 =A0 =A0 =A0 =A0 =A0 Xen Qemu Device Model virtual = machine hardware emulator
ii =A0xen-utils-4.0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 4.0.1-= 4 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0XEN administrative tools
=
ii =A0xen-utils-common =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A04.0.0-1 = =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0XEN administrative tools - commo= n files
ii =A0xenstore-utils =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A04.0.1-= 4 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0Xenstore utilities for Xen
root@cyrax:~# uname -a
Linux cyrax 2.6.32-5-xen-amd64= #1 SMP Sun May 6 08:57:29 UTC 2012 x86_64 GNU/Linux

working domU (centos)
[root@sektor= ~]# cat /etc/redhat-release
CentOS release 5.5 (Final)
[root@sektor ~]# uname -a
Linux sektor 2.6.18-194.3.1.el5 #1 SMP= Thu May 13 13:08:30 EDT 2010 x86_64 x86_64 x86_64 GNU/Linux
[root@sektor ~]# lspci | grep Xen
00:03.0 Class f= f80: XenSource, Inc. Xen Platform Device (rev 01)
[root@sektor ~]= # lsmod | grep xen
xen_vnif =A0 =A0 =A0 =A0 =A0 =A0 =A0 58817 =A0= 0 [permanent]
xen_vbd =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A050345 =A00
xen_balloo= n =A0 =A0 =A0 =A0 =A0 =A045641 =A01 xen_vnif,[permanent]
xen_plat= form_pci =A0 =A0 =A0117741 =A03 xen_vnif,xen_vbd,xen_balloon,[permanent]

As you can see above the platform pci device s= hows in lspci and you can see in lsmod that the pv interfaces are being det= ected and used

New box (wheezy, nonworking)

<= div>root@barium:~# dpkg -l | grep xen
ii =A0libxen-4.1 =A0 =A0 = =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 4.1.3-1 =A0 =A0 =A0 =A0 =A0 =A0 =A0= =A0 =A0 =A0amd64 =A0 =A0 =A0 =A0Public libs for Xen
ii =A0libxenstore3.0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 4.1.3-1 = =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0amd64 =A0 =A0 =A0 =A0Xenstore commun= ications library for Xen
ii =A0xen-hypervisor-4.1-amd64 =A0 =A0 = =A0 =A0 =A0 4.1.3-1 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0amd64 =A0 =A0 = =A0 =A0Xen Hypervisor on AMD64
ii =A0xen-system-amd64 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 4.1.3-1 =A0= =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0amd64 =A0 =A0 =A0 =A0Xen System on AMD6= 4 (meta-package)
ii =A0xen-utils-4.1 =A0 =A0 =A0 =A0 =A0 =A0 =A0 = =A0 =A0 =A0 =A04.1.3-1 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0amd64 =A0 =A0= =A0 =A0XEN administrative tools
ii =A0xen-utils-common =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 4.1.3-1 =A0= =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0all =A0 =A0 =A0 =A0 =A0Xen administrati= ve tools - common files
ii =A0xenstore-utils =A0 =A0 =A0 =A0 =A0 = =A0 =A0 =A0 =A0 =A0 4.1.3-1 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0amd64 = =A0 =A0 =A0 =A0Xenstore utilities for Xen
root@barium:~# uname -a
Linux barium 3.2.0-3-amd6= 4 #1 SMP Mon Jul 23 02:45:17 UTC 2012 x86_64 GNU/Linux

=
domU (centos)
[root@baraka ~]# cat /etc/redhat-re= lease
CentOS release 5.5 (Final)
[root@baraka ~]# uname= -a
Linux baraka 2.6.18-194.3.1.el5 #1 SMP Thu May 13 13:08:30 ED= T 2010 x86_64 x86_64 x86_64 GNU/Linux
[root@baraka ~]#= lspci | grep Xen
00:03.0 Class ff80: XenSource, Inc. Xen Platform Device (rev 01)
=
[root@baraka ~]# lsmod | grep xen
xen_platform_pc= i =A0 =A0 =A0117741 =A00 [permanent]

So as y= ou can see the domU is identical kernel in both cases however when the domU= is running on the wheezy dom0 even despite that the platform pci device ap= pears exactly the same in lspci=A0

I've attached the configs and logs that you asked f= or

Any ideas how to debug further? The difference = between the working scenario and nonworking is the dom0 distro (squeeze vs = wheezy), dom0 kernel and dom0 hypervisor
Testing with both scenario's was done with the exact same domU so = I cant see how it could be a domU issue.

thanks
chris

On Wed, Aug 29, 2012 at 4= :41 AM, Ian Campbell <Ian.Campbell@citrix.com> wrote:<= br>
On Tue, 2012-08-28 at 18:5= 2 +0100, chris wrote:
> the issue seems to be with wheezy not squeeze im just trying to figure=
> out why with wheezy with newer versions of everything pvhvm is not
> working.

I upgraded my test Squeeze VM to Wheezy and PVHVM continued working (this is on a fresh Wheezy dom0).

> and in domU's I compared the lspci of the xen platform pci device = to
> the lspci output from a working pvhvm domU that resides on a squeeze > dom0.

And they were identical?

> so my guess is that its related to hypervisor?

I don't think we have enough evidence to decide one way or the ot= her.

Can you provide the logs and guest configurations which I asked for
please.

Ian.



--14dae9340e73a540b204c94a9e4e-- --14dae9340e73a540c204c94a9e50 Content-Type: text/plain; charset=US-ASCII; name="baraka-qemu.txt" Content-Disposition: attachment; filename="baraka-qemu.txt" Content-Transfer-Encoding: base64 X-Attachment-Id: f_h6wlbamh2 cm9vdEBiYXJpdW06L3Zhci9sb2cveGVuIyBjYXQgcWVtdS1kbS12bS1iYXJha2EubG9nDQpkb21p ZDogMTcNCi1jIGNvbmZpZyBxZW11IG5ldHdvcmsgd2l0aCB4ZW4gYnJpZGdlIGZvcg0KdmlmMTcu MC1lbXUgdm0tYmFyYWthLWxhbg0KVXNpbmcgZmlsZSAvZGV2L3N0b3JhZ2Uvdm0tYmFyYWthIGlu IHJlYWQtd3JpdGUgbW9kZQ0KV2F0Y2hpbmcgL2xvY2FsL2RvbWFpbi8wL2RldmljZS1tb2RlbC8x Ny9sb2dkaXJ0eS9jbWQNCldhdGNoaW5nIC9sb2NhbC9kb21haW4vMC9kZXZpY2UtbW9kZWwvMTcv Y29tbWFuZA0KV2F0Y2hpbmcgL2xvY2FsL2RvbWFpbi8xNy9jcHUNCnFlbXVfbWFwX2NhY2hlX2lu aXQgbnJfYnVja2V0cyA9IDEwMDAwIHNpemUgNDE5NDMwNA0Kc2hhcmVkIHBhZ2UgYXQgcGZuIGZl ZmZkDQpidWZmZXJlZCBpbyBwYWdlIGF0IHBmbiBmZWZmYg0KR3Vlc3QgdXVpZCA9IDZkNDdlZjc0 LTkwYjYtNzE1YS1iYTI2LWU4ZjlmMzA0YWEzNw0KVGltZSBvZmZzZXQgc2V0IDANCnBvcHVsYXRp bmcgdmlkZW8gUkFNIGF0IGZmMDAwMDAwDQptYXBwaW5nIHZpZGVvIFJBTSBmcm9tIGZmMDAwMDAw DQpSZWdpc3RlciB4ZW4gcGxhdGZvcm0uDQpEb25lIHJlZ2lzdGVyIHBsYXRmb3JtLg0KcGxhdGZv cm1fZml4ZWRfaW9wb3J0OiBjaGFuZ2VkIHJvL3J3IHN0YXRlIG9mIFJPTSBtZW1vcnkgYXJlYS4g bm93IGlzIHJ3IHN0YXRlLg0KeHNfcmVhZCgvbG9jYWwvZG9tYWluLzAvZGV2aWNlLW1vZGVsLzE3 L3hlbl9leHRlbmRlZF9wb3dlcl9tZ210KTogcmVhZCBlcnJvcg0KSS9PIHJlcXVlc3Qgbm90IHJl YWR5OiAwLCBwdHI6IDAsIHBvcnQ6IDAsIGRhdGE6IDAsIGNvdW50OiAwLCBzaXplOiAwDQpMb2ct ZGlydHk6IG5vIGNvbW1hbmQgeWV0Lg0KdmNwdS1zZXQ6IHdhdGNoIG5vZGUgZXJyb3IuDQp4c19y ZWFkKC9sb2NhbC9kb21haW4vMTcvbG9nLXRocm90dGxpbmcpOiByZWFkIGVycm9yDQpxZW11OiBp Z25vcmluZyBub3QtdW5kZXJzdG9vZCBkcml2ZSBgL2xvY2FsL2RvbWFpbi8xNy9sb2ctdGhyb3R0 bGluZycNCm1lZGl1bSBjaGFuZ2Ugd2F0Y2ggb24gYC9sb2NhbC9kb21haW4vMTcvbG9nLXRocm90 dGxpbmcnIC0gdW5rbm93biBkZXZpY2UsIGlnbm9yZWQNCmNoYXIgZGV2aWNlIHJlZGlyZWN0ZWQg dG8gL2Rldi9wdHMvMA0KeGVuIGJlOiBjb25zb2xlLTA6IHhlbiBiZTogY29uc29sZS0wOiBpbml0 aWFsaXNlKCkgZmFpbGVkDQppbml0aWFsaXNlKCkgZmFpbGVkDQp4ZW4gYmU6IGNvbnNvbGUtMDog eGVuIGJlOiBjb25zb2xlLTA6IGluaXRpYWxpc2UoKSBmYWlsZWQNCmluaXRpYWxpc2UoKSBmYWls ZWQNCnhlbiBiZTogY29uc29sZS0wOiB4ZW4gYmU6IGNvbnNvbGUtMDogaW5pdGlhbGlzZSgpIGZh aWxlZA0KaW5pdGlhbGlzZSgpIGZhaWxlZA0KeGVuIGJlOiBjb25zb2xlLTA6IHhlbiBiZTogY29u c29sZS0wOiBpbml0aWFsaXNlKCkgZmFpbGVkDQppbml0aWFsaXNlKCkgZmFpbGVkDQp4ZW4gYmU6 IGNvbnNvbGUtMDogeGVuIGJlOiBjb25zb2xlLTA6IGluaXRpYWxpc2UoKSBmYWlsZWQNCmluaXRp YWxpc2UoKSBmYWlsZWQNCnhlbiBiZTogY29uc29sZS0wOiB4ZW4gYmU6IGNvbnNvbGUtMDogaW5p dGlhbGlzZSgpIGZhaWxlZA0KaW5pdGlhbGlzZSgpIGZhaWxlZA0KeGVuIGJlOiBjb25zb2xlLTA6 IHhlbiBiZTogY29uc29sZS0wOiBpbml0aWFsaXNlKCkgZmFpbGVkDQppbml0aWFsaXNlKCkgZmFp bGVkDQp4ZW4gYmU6IGNvbnNvbGUtMDogeGVuIGJlOiBjb25zb2xlLTA6IGluaXRpYWxpc2UoKSBm YWlsZWQNCmluaXRpYWxpc2UoKSBmYWlsZWQNCnhlbiBiZTogY29uc29sZS0wOiB4ZW4gYmU6IGNv bnNvbGUtMDogaW5pdGlhbGlzZSgpIGZhaWxlZA0KaW5pdGlhbGlzZSgpIGZhaWxlZA0KeGVuIGJl OiBjb25zb2xlLTA6IHhlbiBiZTogY29uc29sZS0wOiBpbml0aWFsaXNlKCkgZmFpbGVkDQppbml0 aWFsaXNlKCkgZmFpbGVkDQp4ZW4gYmU6IGNvbnNvbGUtMDogeGVuIGJlOiBjb25zb2xlLTA6IGlu aXRpYWxpc2UoKSBmYWlsZWQNCmluaXRpYWxpc2UoKSBmYWlsZWQNCnhlbiBiZTogY29uc29sZS0w OiB4ZW4gYmU6IGNvbnNvbGUtMDogaW5pdGlhbGlzZSgpIGZhaWxlZA0KaW5pdGlhbGlzZSgpIGZh aWxlZA0KY2lycnVzIHZnYSBtYXAgY2hhbmdlIHdoaWxlIG9uIGxmYiBtb2RlDQptYXBwaW5nIHZy YW0gdG8gZjAwMDAwMDAgLSBmMDQwMDAwMA0KcGxhdGZvcm1fZml4ZWRfaW9wb3J0OiBjaGFuZ2Vk IHJvL3J3IHN0YXRlIG9mIFJPTSBtZW1vcnkgYXJlYS4gbm93IGlzIHJ3IHN0YXRlLg0KcGxhdGZv cm1fZml4ZWRfaW9wb3J0OiBjaGFuZ2VkIHJvL3J3IHN0YXRlIG9mIFJPTSBtZW1vcnkgYXJlYS4g bm93IGlzIHJvIHN0YXRlLg0K --14dae9340e73a540c204c94a9e50 Content-Type: application/octet-stream; name="vm-baraka.cfg" Content-Disposition: attachment; filename="vm-baraka.cfg" Content-Transfer-Encoding: base64 X-Attachment-Id: f_h6wlazpt0 a2VybmVsID0gJy91c3IvbGliL3hlbi9ib290L2h2bWxvYWRlcicNCmJ1aWxkZXIgPSAnaHZtJw0K bWVtb3J5ID0gJzc2OCcNCmRldmljZV9tb2RlbD0nL3Vzci9saWIveGVuL2Jpbi9xZW11LWRtJw0K IyBEaXNrcw0KZGlzayA9IFsgJ3BoeTovZGV2L3N0b3JhZ2Uvdm0tYmFyYWthLGlvZW11OmhkYSx3 JywNCl0NCg0KIyBIb3N0bmFtZQ0KbmFtZSA9ICd2bS1iYXJha2EnDQoNCiMgTmV0d29ya2luZw0K dmlmID0gWyd0eXBlPWlvZW11LCBicmlkZ2U9dm0tYmFyYWthLWxhbiwgbWFjPTAwOjE3OjcxOjM3 OjU4OkVFJ10NCg0KIyBCZWhhdmlvdXINCmJvb3Q9J2MnDQp2Y3B1cz0xDQphY3BpPTENCmFwaWM9 MQ0KYWhjaT0xDQp2bmM9MQ0Kdm5jdmlld2VyPTENCnNkbD0wDQp1c2I9MQ0KdXNiZGV2aWNlPSd0 YWJsZXQnDQp0aW1lcl9tb2RlPTENCnhlbl9wbGF0Zm9ybV9wY2k9MQ0K --14dae9340e73a540c204c94a9e50 Content-Type: application/octet-stream; name="vm-sektor.cfg" Content-Disposition: attachment; filename="vm-sektor.cfg" Content-Transfer-Encoding: base64 X-Attachment-Id: f_h6wlb41m1 a2VybmVsID0gJy91c3IvbGliL3hlbi9ib290L2h2bWxvYWRlcicNCmJ1aWxkZXIgPSAnaHZtJw0K bWVtb3J5ID0gJzc2OCcNCmRldmljZV9tb2RlbD0nL3Vzci9saWIveGVuL2Jpbi9xZW11LWRtJw0K IyBEaXNrcw0KZGlzayA9IFsgJ3BoeTovZGV2L3N0b3JhZ2Uvdm0tc2VrdG9yLGlvZW11OmhkYSx3 JywNCl0NCg0KIyBIb3N0bmFtZQ0KbmFtZSA9ICd2bS1zZWt0b3InDQoNCiMgTmV0d29ya2luZw0K dmlmID0gWyd0eXBlPWlvZW11LCBicmlkZ2U9dm0tc2VrdG9yLWxhbiwgdmlmbmFtZT12bS1zZWt0 b3IsIG1hYz0wMDoxNjozRDozNzpCMjpBQSddDQoNCiMgQmVoYXZpb3VyDQpib290PSdjJw0KdmNw dXM9MQ0KYWNwaT0xDQphaGNpPTENCnZuYz0xDQp2bmN2aWV3ZXI9MQ0Kc2RsPTANCnRpbWVyX21v ZGU9MQ0KdXNiPTENCnVzYmRldmljZT0ndGFibGV0Jw0KeGVuX3BsYXRmb3JtX3BjaT0xDQo= --14dae9340e73a540c204c94a9e50 Content-Type: text/plain; charset=US-ASCII; name="sektor-qemu.txt" Content-Disposition: attachment; filename="sektor-qemu.txt" Content-Transfer-Encoding: base64 X-Attachment-Id: f_h6wlbdch3 cm9vdEBiYXJpdW06L3Zhci9sb2cveGVuIyBjYXQgcWVtdS1kbS12bS1iYXJha2EubG9nDQpkb21p ZDogMTcNCi1jIGNvbmZpZyBxZW11IG5ldHdvcmsgd2l0aCB4ZW4gYnJpZGdlIGZvcg0KdmlmMTcu MC1lbXUgdm0tYmFyYWthLWxhbg0KVXNpbmcgZmlsZSAvZGV2L3N0b3JhZ2Uvdm0tYmFyYWthIGlu IHJlYWQtd3JpdGUgbW9kZQ0KV2F0Y2hpbmcgL2xvY2FsL2RvbWFpbi8wL2RldmljZS1tb2RlbC8x Ny9sb2dkaXJ0eS9jbWQNCldhdGNoaW5nIC9sb2NhbC9kb21haW4vMC9kZXZpY2UtbW9kZWwvMTcv Y29tbWFuZA0KV2F0Y2hpbmcgL2xvY2FsL2RvbWFpbi8xNy9jcHUNCnFlbXVfbWFwX2NhY2hlX2lu aXQgbnJfYnVja2V0cyA9IDEwMDAwIHNpemUgNDE5NDMwNA0Kc2hhcmVkIHBhZ2UgYXQgcGZuIGZl ZmZkDQpidWZmZXJlZCBpbyBwYWdlIGF0IHBmbiBmZWZmYg0KR3Vlc3QgdXVpZCA9IDZkNDdlZjc0 LTkwYjYtNzE1YS1iYTI2LWU4ZjlmMzA0YWEzNw0KVGltZSBvZmZzZXQgc2V0IDANCnBvcHVsYXRp bmcgdmlkZW8gUkFNIGF0IGZmMDAwMDAwDQptYXBwaW5nIHZpZGVvIFJBTSBmcm9tIGZmMDAwMDAw DQpSZWdpc3RlciB4ZW4gcGxhdGZvcm0uDQpEb25lIHJlZ2lzdGVyIHBsYXRmb3JtLg0KcGxhdGZv cm1fZml4ZWRfaW9wb3J0OiBjaGFuZ2VkIHJvL3J3IHN0YXRlIG9mIFJPTSBtZW1vcnkgYXJlYS4g bm93IGlzIHJ3IHN0YXRlLg0KeHNfcmVhZCgvbG9jYWwvZG9tYWluLzAvZGV2aWNlLW1vZGVsLzE3 L3hlbl9leHRlbmRlZF9wb3dlcl9tZ210KTogcmVhZCBlcnJvcg0KSS9PIHJlcXVlc3Qgbm90IHJl YWR5OiAwLCBwdHI6IDAsIHBvcnQ6IDAsIGRhdGE6IDAsIGNvdW50OiAwLCBzaXplOiAwDQpMb2ct ZGlydHk6IG5vIGNvbW1hbmQgeWV0Lg0KdmNwdS1zZXQ6IHdhdGNoIG5vZGUgZXJyb3IuDQp4c19y ZWFkKC9sb2NhbC9kb21haW4vMTcvbG9nLXRocm90dGxpbmcpOiByZWFkIGVycm9yDQpxZW11OiBp Z25vcmluZyBub3QtdW5kZXJzdG9vZCBkcml2ZSBgL2xvY2FsL2RvbWFpbi8xNy9sb2ctdGhyb3R0 bGluZycNCm1lZGl1bSBjaGFuZ2Ugd2F0Y2ggb24gYC9sb2NhbC9kb21haW4vMTcvbG9nLXRocm90 dGxpbmcnIC0gdW5rbm93biBkZXZpY2UsIGlnbm9yZWQNCmNoYXIgZGV2aWNlIHJlZGlyZWN0ZWQg dG8gL2Rldi9wdHMvMA0KeGVuIGJlOiBjb25zb2xlLTA6IHhlbiBiZTogY29uc29sZS0wOiBpbml0 aWFsaXNlKCkgZmFpbGVkDQppbml0aWFsaXNlKCkgZmFpbGVkDQp4ZW4gYmU6IGNvbnNvbGUtMDog eGVuIGJlOiBjb25zb2xlLTA6IGluaXRpYWxpc2UoKSBmYWlsZWQNCmluaXRpYWxpc2UoKSBmYWls ZWQNCnhlbiBiZTogY29uc29sZS0wOiB4ZW4gYmU6IGNvbnNvbGUtMDogaW5pdGlhbGlzZSgpIGZh aWxlZA0KaW5pdGlhbGlzZSgpIGZhaWxlZA0KeGVuIGJlOiBjb25zb2xlLTA6IHhlbiBiZTogY29u c29sZS0wOiBpbml0aWFsaXNlKCkgZmFpbGVkDQppbml0aWFsaXNlKCkgZmFpbGVkDQp4ZW4gYmU6 IGNvbnNvbGUtMDogeGVuIGJlOiBjb25zb2xlLTA6IGluaXRpYWxpc2UoKSBmYWlsZWQNCmluaXRp YWxpc2UoKSBmYWlsZWQNCnhlbiBiZTogY29uc29sZS0wOiB4ZW4gYmU6IGNvbnNvbGUtMDogaW5p dGlhbGlzZSgpIGZhaWxlZA0KaW5pdGlhbGlzZSgpIGZhaWxlZA0KeGVuIGJlOiBjb25zb2xlLTA6 IHhlbiBiZTogY29uc29sZS0wOiBpbml0aWFsaXNlKCkgZmFpbGVkDQppbml0aWFsaXNlKCkgZmFp bGVkDQp4ZW4gYmU6IGNvbnNvbGUtMDogeGVuIGJlOiBjb25zb2xlLTA6IGluaXRpYWxpc2UoKSBm YWlsZWQNCmluaXRpYWxpc2UoKSBmYWlsZWQNCnhlbiBiZTogY29uc29sZS0wOiB4ZW4gYmU6IGNv bnNvbGUtMDogaW5pdGlhbGlzZSgpIGZhaWxlZA0KaW5pdGlhbGlzZSgpIGZhaWxlZA0KeGVuIGJl OiBjb25zb2xlLTA6IHhlbiBiZTogY29uc29sZS0wOiBpbml0aWFsaXNlKCkgZmFpbGVkDQppbml0 aWFsaXNlKCkgZmFpbGVkDQp4ZW4gYmU6IGNvbnNvbGUtMDogeGVuIGJlOiBjb25zb2xlLTA6IGlu aXRpYWxpc2UoKSBmYWlsZWQNCmluaXRpYWxpc2UoKSBmYWlsZWQNCnhlbiBiZTogY29uc29sZS0w OiB4ZW4gYmU6IGNvbnNvbGUtMDogaW5pdGlhbGlzZSgpIGZhaWxlZA0KaW5pdGlhbGlzZSgpIGZh aWxlZA0KY2lycnVzIHZnYSBtYXAgY2hhbmdlIHdoaWxlIG9uIGxmYiBtb2RlDQptYXBwaW5nIHZy YW0gdG8gZjAwMDAwMDAgLSBmMDQwMDAwMA0KcGxhdGZvcm1fZml4ZWRfaW9wb3J0OiBjaGFuZ2Vk IHJvL3J3IHN0YXRlIG9mIFJPTSBtZW1vcnkgYXJlYS4gbm93IGlzIHJ3IHN0YXRlLg0KcGxhdGZv cm1fZml4ZWRfaW9wb3J0OiBjaGFuZ2VkIHJvL3J3IHN0YXRlIG9mIFJPTSBtZW1vcnkgYXJlYS4g bm93IGlzIHJvIHN0YXRlLg0K --14dae9340e73a540c204c94a9e50 Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users --14dae9340e73a540c204c94a9e50-- From xen-users-bounces@lists.xen.org Sun Sep 09 22:29:36 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Sun, 09 Sep 2012 22:29:36 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TApz1-0005jg-6H; Sun, 09 Sep 2012 22:28:03 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TApyy-0005jb-Tr for xen-users@lists.xen.org; Sun, 09 Sep 2012 22:28:01 +0000 Received: from [85.158.139.83:57511] by server-4.bemta-5.messagelabs.com id 45/6B-23042-0F71D405; Sun, 09 Sep 2012 22:28:00 +0000 X-Env-Sender: murrayie@yahoo.co.uk X-Msg-Ref: server-7.tower-182.messagelabs.com!1347229679!25517939!1 X-Originating-IP: [217.146.183.194] X-SpamReason: No, hits=0.0 required=7.0 tests=ML_RADAR_SPEW_LINKS_14, spamassassin: X-StarScan-Received: X-StarScan-Version: 6.6.1.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 783 invoked from network); 9 Sep 2012 22:27:59 -0000 Received: from nm20.bullet.mail.ukl.yahoo.com (HELO nm20.bullet.mail.ukl.yahoo.com) (217.146.183.194) by server-7.tower-182.messagelabs.com with SMTP; 9 Sep 2012 22:27:59 -0000 Received: from [217.146.183.215] by nm20.bullet.mail.ukl.yahoo.com with NNFMP; 09 Sep 2012 22:27:58 -0000 Received: from [217.146.183.129] by tm8.bullet.mail.ukl.yahoo.com with NNFMP; 09 Sep 2012 22:27:58 -0000 Received: from [127.0.0.1] by smtp114.mail.ukl.yahoo.com with NNFMP; 09 Sep 2012 22:27:58 -0000 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.co.uk; s=s1024; t=1347229678; bh=ljpCXUCJyQo1TMtDRzcc1/QUSf78zZ7V0tt00gpESTU=; h=X-Yahoo-Newman-Id:X-Yahoo-Newman-Property:X-YMail-OSG:X-Yahoo-SMTP:Received:Message-ID:Date:From:User-Agent:MIME-Version:To:Subject:Content-Type:Content-Transfer-Encoding; b=BQ2JQBHIsEdL6Mr0Q0eDfcaq9vD49xrTrLTopU/aqlq/5WGz7sIbSrAuvQBrBxH8Cj95nDqacMnTcZOTfzd32U/Rhpp1Jnp4FGet8dV6kAWdM4XYLmO57MhhFVptY4ZNzBdUad+On2Rv10lA51/LJThrl45b/Q/xP/csTMw++qY= X-Yahoo-Newman-Id: 730328.64156.bm@smtp114.mail.ukl.yahoo.com X-Yahoo-Newman-Property: ymail-3 X-YMail-OSG: fr4e_74VM1lztDPW7sU1leqnCAtIl4amDNs_l7eqSkhHkBv nc7kwJYxmkUX3LVQpkosTkWphL6EX5QGpoNKjULjtR0N5Bd5zPTiZB2zjvbp KdbIYfupdY2m1VC.Ga4XpI3qcKzefVdxjye2pIYDr9etyMVOe2SLT7l1.r40 A45ZScXvSRlW1DDHmwEEkevOAQl33OSqRqaaFLbERq3_0pgZuTDxAzYwlEkV Sv2CosFAorgLHQdDApibkYosjuJn_uPGVDqRCdylNB.rEtHMK6SyaGyWVHWP Z.mPJfAENXm4A594PqIbjCzFL3dXsl4KMAuyk83UZlWDa_bZhAjX1WWcr7P9 zy9eSyVFxvRM_M.RWeZqUBg84pXSvFbqnesoDV5Bnv0xLcw4Kdv3zCB9BZc5 KF1WE0iI.d8KBFgabNcYBEeCvyJ0zWF_XABClXZk0zmZ_dQ-- X-Yahoo-SMTP: P.LfrmaswBDlKN6tCvtOaEZlSVsY Received: from [192.168.1.3] (murrayie@82.13.25.53 with plain) by smtp114.mail.ukl.yahoo.com with SMTP; 09 Sep 2012 15:27:58 -0700 PDT Message-ID: <504D17ED.9030105@yahoo.co.uk> Date: Sun, 09 Sep 2012 23:27:57 +0100 From: Ian User-Agent: Mozilla/5.0 (X11; Linux i686; rv:15.0) Gecko/20120827 Thunderbird/15.0 MIME-Version: 1.0 To: "xen-users@lists.xen.org" Subject: [Xen-users] Stall on CPU X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset="us-ascii"; Format="flowed" Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org Hi, I have been receiving messages on a new DomU's kern.log. I've done a lot of googling, but haven't came up with anything very useful, at least not in a Xen context. I was wondering if anyone had any suggestions about what could be wrong. >From everything I have read, there should be a stack trace included, but I am not seeing one. Thanks in advance, Ian. on Xen 4.1.2... Sep 6 13:04:07 davical kernel: [12008.080091] INFO: rcu_sched detected stall on CPU 1 (t=50460 jiffies) Sep 6 13:04:07 davical kernel: [12008.084081] sending NMI to all CPUs: Sep 6 13:04:07 davical kernel: [11806.576064] INFO: rcu_sched detected stalls on CPUs/tasks: { 1} (detected by 0, t=566314 jiffies) Sep 6 13:04:07 davical kernel: [75644.150936] INFO: rcu_sched detected stall on CPU 0 (t=15393163 jiffies) Sep 6 13:04:07 davical kernel: [75644.304186] sched: RT throttling activated on Xen 4.1.3... Sep 8 11:39:40 davical kernel: [62220.039363] INFO: rcu_sched detected stall on CPU 1 (t=355732 jiffies) Sep 8 11:39:40 davical kernel: [62220.039363] sending NMI to all CPUs: Sep 8 11:39:40 davical kernel: [124714.197152] INFO: rcu_sched detected stalls on CPUs/tasks: { 1} (detected by 0, t=355732 jiffies) Sep 8 11:39:48 davical kernel: [124721.756263] INFO: rcu_sched detected stall on CPU 1 (t=15751455 jiffies) Sep 8 11:39:48 davical kernel: [124721.756328] sending NMI to all CPUs: Sep 8 11:39:48 davical kernel: [124721.760199] INFO: rcu_sched detected stalls on CPUs/tasks: { 1} (detected by 0, t=15751455 jiffies) Sep 8 11:39:52 davical kernel: [124725.855952] ipv6_create_tempaddr(): retry temporary address regeneration. Sep 8 11:40:08 davical kernel: [124721.760226] INFO: rcu_bh detected stall on CPU 1 (t=15395723 jiffies) Sep 8 11:40:08 davical kernel: [124721.760226] sending NMI to all CPUs: Sep 8 11:40:08 davical kernel: [124742.485888] sched: RT throttling activated I have tried it on two Xen Dom0 installations, one of 4.1.2 and the other on 4.1.3. The 4.1.2 Dom0 machine is a scientific linux installation using a custom compiled kernel, 3.4.0+. The 4.1.3 Dom0 machine is using a standard Ubuntu server kernel 3.2.0-29-generic-pae The domU is an Ubuntu 12.04.1 server based using a standard Ubuntu 12.04.1 kernel, also 3.2.0-29-generic-pae. xl info of the 4.1.2 machine: host : xen3 release : 3.4.0+ version : #1 SMP Mon Jun 4 12:41:14 BST 2012 machine : x86_64 nr_cpus : 4 nr_nodes : 1 cores_per_socket : 4 threads_per_core : 1 cpu_mhz : 2300 hw_caps : 178bf3ff:efd3fbff:00000000:00001310:00802001:00000000:000007ff:00000000 virt_caps : hvm total_memory : 8159 free_memory : 3866 free_cpus : 0 xen_major : 4 xen_minor : 1 xen_extra : .2 xen_caps : xen-3.0-x86_64 xen-3.0-x86_32p hvm-3.0-x86_32 hvm-3.0-x86_32p hvm-3.0-x86_64 xen_scheduler : credit xen_pagesize : 4096 platform_params : virt_start=0xffff800000000000 xen_changeset : unavailable xen_commandline : loglvl=all guesloglvl=all cc_compiler : gcc version 4.4.5 20110214 (Red Hat 4.4.5-6) (GCC) cc_compile_by : root cc_compile_domain : (none) cc_compile_date : Sun Jan 22 01:18:42 GMT 2012 xend_config_format : 4 xl info of the 4.1.3 machine: host : xen5 release : 3.2.0-29-generic-pae version : #46-Ubuntu SMP Fri Jul 27 17:25:43 UTC 2012 machine : i686 nr_cpus : 2 nr_nodes : 1 cores_per_socket : 2 threads_per_core : 1 cpu_mhz : 1995 hw_caps : bfe9fbff:00100000:00000000:00000940:0000c1a9:00000000:00000000:00000000 virt_caps : total_memory : 3062 free_memory : 173 free_cpus : 0 xen_major : 4 xen_minor : 1 xen_extra : .3 xen_caps : xen-3.0-x86_32p xen_scheduler : credit xen_pagesize : 4096 platform_params : virt_start=0xf5800000 xen_changeset : unavailable xen_commandline : placeholder cc_compiler : gcc version 4.6.3 (Ubuntu/Linaro 4.6.3-1ubuntu5) cc_compile_by : root cc_compile_domain : local cc_compile_date : Thu Sep 6 01:53:48 BST 2012 xend_config_format : 4 DomU config file: cat ubuntu-calendar name = "ubuntu-calendar" memory = 1024 disk = ['phy:/dev/xen5/ubuntu-calendar,xvda,w'] vif = [ 'mac=00:16:31:50:01:03' ] bootloader="/usr/bin/pygrub" vfb = [ "type=vnc,vncunused=1,vnclisten=0.0.0.0" ] vcpus = 2 on_reboot = 'restart' on_crash = 'restart' DomU's grub.lst.... menuentry 'Ubuntu, with Linux 3.2.0-29-generic' --class ubuntu --class gnu-linux --class gnu --class os { recordfail insmod ext2 set root='(hd0,1)' search --no-floppy --fs-uuid --set=root 70149f72-3c4f-4608-bebd-06825b91 ce29 linux /boot/vmlinuz-3.2.0-29-generic-pae root=UUID=70149f72-3c4f-4608- bebd-06825b91ce29 ro quiet splash set default="0" set timeout=5 menuentry 'Ubuntu GNU/Linux, with Xen 4.1-amd64 and Linux 3.2.0-23-generic' --class ubuntu --class gnu-linux --class gnu --class os --class xen { insmod part_msdos insmod ext2 set root='(hd0,msdos1)' search --no-floppy --fs-uuid --set=root 1b478986-8c02-4a79-ad61-cf8f418e35ad echo 'Loading Xen 4.1-amd64 ...' multiboot /xen.gz placeholder echo 'Loading Linux 3.2.0-29-generic-pae ...' module /vmlinuz-3.2.0-29-generic-pae placeholder root=/dev/mapper/xen5-root ro echo 'Loading initial ramdisk ...' module /initrd.img-3.2.0-29-generic-pae } xen-fbfront.video=16,1024,768 $vt_handoff initrd /boot/initrd.img-3.2.0-29-generic-pae Dom0's grub.lst (4.1.3)... set default="0" set timeout=5 menuentry 'Ubuntu GNU/Linux, with Xen 4.1-amd64 and Linux 3.2.0-23-generic' --class ubuntu --class gnu-linux --class gnu --class os --class xen { insmod part_msdos insmod ext2 set root='(hd0,msdos1)' search --no-floppy --fs-uuid --set=root 1b478986-8c02-4a79-ad61-cf8f418e35ad echo 'Loading Xen 4.1-amd64 ...' multiboot /xen.gz placeholder echo 'Loading Linux 3.2.0-29-generic-pae ...' module /vmlinuz-3.2.0-29-generic-pae placeholder root=/dev/mapper/xen5-root ro echo 'Loading initial ramdisk ...' module /initrd.img-3.2.0-29-generic-pae } _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Sun Sep 09 22:29:36 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Sun, 09 Sep 2012 22:29:36 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TApz1-0005jg-6H; Sun, 09 Sep 2012 22:28:03 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TApyy-0005jb-Tr for xen-users@lists.xen.org; Sun, 09 Sep 2012 22:28:01 +0000 Received: from [85.158.139.83:57511] by server-4.bemta-5.messagelabs.com id 45/6B-23042-0F71D405; Sun, 09 Sep 2012 22:28:00 +0000 X-Env-Sender: murrayie@yahoo.co.uk X-Msg-Ref: server-7.tower-182.messagelabs.com!1347229679!25517939!1 X-Originating-IP: [217.146.183.194] X-SpamReason: No, hits=0.0 required=7.0 tests=ML_RADAR_SPEW_LINKS_14, spamassassin: X-StarScan-Received: X-StarScan-Version: 6.6.1.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 783 invoked from network); 9 Sep 2012 22:27:59 -0000 Received: from nm20.bullet.mail.ukl.yahoo.com (HELO nm20.bullet.mail.ukl.yahoo.com) (217.146.183.194) by server-7.tower-182.messagelabs.com with SMTP; 9 Sep 2012 22:27:59 -0000 Received: from [217.146.183.215] by nm20.bullet.mail.ukl.yahoo.com with NNFMP; 09 Sep 2012 22:27:58 -0000 Received: from [217.146.183.129] by tm8.bullet.mail.ukl.yahoo.com with NNFMP; 09 Sep 2012 22:27:58 -0000 Received: from [127.0.0.1] by smtp114.mail.ukl.yahoo.com with NNFMP; 09 Sep 2012 22:27:58 -0000 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.co.uk; s=s1024; t=1347229678; bh=ljpCXUCJyQo1TMtDRzcc1/QUSf78zZ7V0tt00gpESTU=; h=X-Yahoo-Newman-Id:X-Yahoo-Newman-Property:X-YMail-OSG:X-Yahoo-SMTP:Received:Message-ID:Date:From:User-Agent:MIME-Version:To:Subject:Content-Type:Content-Transfer-Encoding; b=BQ2JQBHIsEdL6Mr0Q0eDfcaq9vD49xrTrLTopU/aqlq/5WGz7sIbSrAuvQBrBxH8Cj95nDqacMnTcZOTfzd32U/Rhpp1Jnp4FGet8dV6kAWdM4XYLmO57MhhFVptY4ZNzBdUad+On2Rv10lA51/LJThrl45b/Q/xP/csTMw++qY= X-Yahoo-Newman-Id: 730328.64156.bm@smtp114.mail.ukl.yahoo.com X-Yahoo-Newman-Property: ymail-3 X-YMail-OSG: fr4e_74VM1lztDPW7sU1leqnCAtIl4amDNs_l7eqSkhHkBv nc7kwJYxmkUX3LVQpkosTkWphL6EX5QGpoNKjULjtR0N5Bd5zPTiZB2zjvbp KdbIYfupdY2m1VC.Ga4XpI3qcKzefVdxjye2pIYDr9etyMVOe2SLT7l1.r40 A45ZScXvSRlW1DDHmwEEkevOAQl33OSqRqaaFLbERq3_0pgZuTDxAzYwlEkV Sv2CosFAorgLHQdDApibkYosjuJn_uPGVDqRCdylNB.rEtHMK6SyaGyWVHWP Z.mPJfAENXm4A594PqIbjCzFL3dXsl4KMAuyk83UZlWDa_bZhAjX1WWcr7P9 zy9eSyVFxvRM_M.RWeZqUBg84pXSvFbqnesoDV5Bnv0xLcw4Kdv3zCB9BZc5 KF1WE0iI.d8KBFgabNcYBEeCvyJ0zWF_XABClXZk0zmZ_dQ-- X-Yahoo-SMTP: P.LfrmaswBDlKN6tCvtOaEZlSVsY Received: from [192.168.1.3] (murrayie@82.13.25.53 with plain) by smtp114.mail.ukl.yahoo.com with SMTP; 09 Sep 2012 15:27:58 -0700 PDT Message-ID: <504D17ED.9030105@yahoo.co.uk> Date: Sun, 09 Sep 2012 23:27:57 +0100 From: Ian User-Agent: Mozilla/5.0 (X11; Linux i686; rv:15.0) Gecko/20120827 Thunderbird/15.0 MIME-Version: 1.0 To: "xen-users@lists.xen.org" Subject: [Xen-users] Stall on CPU X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset="us-ascii"; Format="flowed" Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org Hi, I have been receiving messages on a new DomU's kern.log. I've done a lot of googling, but haven't came up with anything very useful, at least not in a Xen context. I was wondering if anyone had any suggestions about what could be wrong. >From everything I have read, there should be a stack trace included, but I am not seeing one. Thanks in advance, Ian. on Xen 4.1.2... Sep 6 13:04:07 davical kernel: [12008.080091] INFO: rcu_sched detected stall on CPU 1 (t=50460 jiffies) Sep 6 13:04:07 davical kernel: [12008.084081] sending NMI to all CPUs: Sep 6 13:04:07 davical kernel: [11806.576064] INFO: rcu_sched detected stalls on CPUs/tasks: { 1} (detected by 0, t=566314 jiffies) Sep 6 13:04:07 davical kernel: [75644.150936] INFO: rcu_sched detected stall on CPU 0 (t=15393163 jiffies) Sep 6 13:04:07 davical kernel: [75644.304186] sched: RT throttling activated on Xen 4.1.3... Sep 8 11:39:40 davical kernel: [62220.039363] INFO: rcu_sched detected stall on CPU 1 (t=355732 jiffies) Sep 8 11:39:40 davical kernel: [62220.039363] sending NMI to all CPUs: Sep 8 11:39:40 davical kernel: [124714.197152] INFO: rcu_sched detected stalls on CPUs/tasks: { 1} (detected by 0, t=355732 jiffies) Sep 8 11:39:48 davical kernel: [124721.756263] INFO: rcu_sched detected stall on CPU 1 (t=15751455 jiffies) Sep 8 11:39:48 davical kernel: [124721.756328] sending NMI to all CPUs: Sep 8 11:39:48 davical kernel: [124721.760199] INFO: rcu_sched detected stalls on CPUs/tasks: { 1} (detected by 0, t=15751455 jiffies) Sep 8 11:39:52 davical kernel: [124725.855952] ipv6_create_tempaddr(): retry temporary address regeneration. Sep 8 11:40:08 davical kernel: [124721.760226] INFO: rcu_bh detected stall on CPU 1 (t=15395723 jiffies) Sep 8 11:40:08 davical kernel: [124721.760226] sending NMI to all CPUs: Sep 8 11:40:08 davical kernel: [124742.485888] sched: RT throttling activated I have tried it on two Xen Dom0 installations, one of 4.1.2 and the other on 4.1.3. The 4.1.2 Dom0 machine is a scientific linux installation using a custom compiled kernel, 3.4.0+. The 4.1.3 Dom0 machine is using a standard Ubuntu server kernel 3.2.0-29-generic-pae The domU is an Ubuntu 12.04.1 server based using a standard Ubuntu 12.04.1 kernel, also 3.2.0-29-generic-pae. xl info of the 4.1.2 machine: host : xen3 release : 3.4.0+ version : #1 SMP Mon Jun 4 12:41:14 BST 2012 machine : x86_64 nr_cpus : 4 nr_nodes : 1 cores_per_socket : 4 threads_per_core : 1 cpu_mhz : 2300 hw_caps : 178bf3ff:efd3fbff:00000000:00001310:00802001:00000000:000007ff:00000000 virt_caps : hvm total_memory : 8159 free_memory : 3866 free_cpus : 0 xen_major : 4 xen_minor : 1 xen_extra : .2 xen_caps : xen-3.0-x86_64 xen-3.0-x86_32p hvm-3.0-x86_32 hvm-3.0-x86_32p hvm-3.0-x86_64 xen_scheduler : credit xen_pagesize : 4096 platform_params : virt_start=0xffff800000000000 xen_changeset : unavailable xen_commandline : loglvl=all guesloglvl=all cc_compiler : gcc version 4.4.5 20110214 (Red Hat 4.4.5-6) (GCC) cc_compile_by : root cc_compile_domain : (none) cc_compile_date : Sun Jan 22 01:18:42 GMT 2012 xend_config_format : 4 xl info of the 4.1.3 machine: host : xen5 release : 3.2.0-29-generic-pae version : #46-Ubuntu SMP Fri Jul 27 17:25:43 UTC 2012 machine : i686 nr_cpus : 2 nr_nodes : 1 cores_per_socket : 2 threads_per_core : 1 cpu_mhz : 1995 hw_caps : bfe9fbff:00100000:00000000:00000940:0000c1a9:00000000:00000000:00000000 virt_caps : total_memory : 3062 free_memory : 173 free_cpus : 0 xen_major : 4 xen_minor : 1 xen_extra : .3 xen_caps : xen-3.0-x86_32p xen_scheduler : credit xen_pagesize : 4096 platform_params : virt_start=0xf5800000 xen_changeset : unavailable xen_commandline : placeholder cc_compiler : gcc version 4.6.3 (Ubuntu/Linaro 4.6.3-1ubuntu5) cc_compile_by : root cc_compile_domain : local cc_compile_date : Thu Sep 6 01:53:48 BST 2012 xend_config_format : 4 DomU config file: cat ubuntu-calendar name = "ubuntu-calendar" memory = 1024 disk = ['phy:/dev/xen5/ubuntu-calendar,xvda,w'] vif = [ 'mac=00:16:31:50:01:03' ] bootloader="/usr/bin/pygrub" vfb = [ "type=vnc,vncunused=1,vnclisten=0.0.0.0" ] vcpus = 2 on_reboot = 'restart' on_crash = 'restart' DomU's grub.lst.... menuentry 'Ubuntu, with Linux 3.2.0-29-generic' --class ubuntu --class gnu-linux --class gnu --class os { recordfail insmod ext2 set root='(hd0,1)' search --no-floppy --fs-uuid --set=root 70149f72-3c4f-4608-bebd-06825b91 ce29 linux /boot/vmlinuz-3.2.0-29-generic-pae root=UUID=70149f72-3c4f-4608- bebd-06825b91ce29 ro quiet splash set default="0" set timeout=5 menuentry 'Ubuntu GNU/Linux, with Xen 4.1-amd64 and Linux 3.2.0-23-generic' --class ubuntu --class gnu-linux --class gnu --class os --class xen { insmod part_msdos insmod ext2 set root='(hd0,msdos1)' search --no-floppy --fs-uuid --set=root 1b478986-8c02-4a79-ad61-cf8f418e35ad echo 'Loading Xen 4.1-amd64 ...' multiboot /xen.gz placeholder echo 'Loading Linux 3.2.0-29-generic-pae ...' module /vmlinuz-3.2.0-29-generic-pae placeholder root=/dev/mapper/xen5-root ro echo 'Loading initial ramdisk ...' module /initrd.img-3.2.0-29-generic-pae } xen-fbfront.video=16,1024,768 $vt_handoff initrd /boot/initrd.img-3.2.0-29-generic-pae Dom0's grub.lst (4.1.3)... set default="0" set timeout=5 menuentry 'Ubuntu GNU/Linux, with Xen 4.1-amd64 and Linux 3.2.0-23-generic' --class ubuntu --class gnu-linux --class gnu --class os --class xen { insmod part_msdos insmod ext2 set root='(hd0,msdos1)' search --no-floppy --fs-uuid --set=root 1b478986-8c02-4a79-ad61-cf8f418e35ad echo 'Loading Xen 4.1-amd64 ...' multiboot /xen.gz placeholder echo 'Loading Linux 3.2.0-29-generic-pae ...' module /vmlinuz-3.2.0-29-generic-pae placeholder root=/dev/mapper/xen5-root ro echo 'Loading initial ramdisk ...' module /initrd.img-3.2.0-29-generic-pae } _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Mon Sep 10 01:17:19 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Mon, 10 Sep 2012 01:17:19 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TAsb9-0002Fj-R8; Mon, 10 Sep 2012 01:15:35 +0000 Received: from mail27.messagelabs.com ([193.109.254.147]) by lists.xen.org with smtp (Exim 4.72) (envelope-from ) id 1TAsb7-0002Fe-It for xen-users@lists.xen.org; Mon, 10 Sep 2012 01:15:33 +0000 X-Env-Sender: mike.a.collins@ark-net.org X-Msg-Ref: server-9.tower-27.messagelabs.com!1347239726!9011676!1 X-Originating-IP: [216.33.127.81] X-SpamReason: No, hits=0.5 required=7.0 tests=BODY_RANDOM_LONG X-StarScan-Received: X-StarScan-Version: 6.6.1.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 18851 invoked from network); 10 Sep 2012 01:15:27 -0000 Received: from mta21.charter.net (HELO mta21.charter.net) (216.33.127.81) by server-9.tower-27.messagelabs.com with SMTP; 10 Sep 2012 01:15:27 -0000 Received: from imp10 ([10.20.200.15]) by mta21.charter.net (InterMail vM.8.01.05.02 201-2260-151-103-20110920) with ESMTP id <20120910011526.CNHM12025.mta21.charter.net@imp10>; Sun, 9 Sep 2012 21:15:26 -0400 Received: from mail.ark-net.org ([75.138.215.251]) by imp10 with smtp.charter.net id xDFR1j00Z5S18aK05DFSsw; Sun, 09 Sep 2012 21:15:26 -0400 X-Authority-Analysis: v=1.1 cv=qU9vTENroOq2s6i9/sTxZt9WOCoWX/XGfIT3Tj8F8dQ= c=1 sm=1 a=_-NSfvUG02YA:10 a=VCxxn1A5iYMA:10 a=wPDyFdB5xvgA:10 a=YBs1tj9y_9UA:10 a=kj9zAlcOel0A:10 a=4A50YBgeEUJTzIKlCdeDOQ==:17 a=ecfIRNFSBeCB0Za1qSgA:9 a=CjuIK1q_8ugA:10 a=4A50YBgeEUJTzIKlCdeDOQ==:117 Received: from localhost (unknown [127.0.0.1]) by mail.ark-net.org (Postfix) with ESMTP id 87A8B203B4; Mon, 10 Sep 2012 01:15:38 +0000 (UTC) X-Virus-Scanned: amavisd-new at ark-net.org Received: from mail.ark-net.org ([127.0.0.1]) by localhost (mail.ark-net.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id qLqy4hANSxWt; Sun, 9 Sep 2012 21:15:12 -0400 (EDT) Received: from mikePC (unknown [192.168.1.35]) by mail.ark-net.org (Postfix) with ESMTP id EE401203AC; Sun, 9 Sep 2012 21:15:12 -0400 (EDT) From: "Michael A. Collins" To: Date: Sun, 9 Sep 2012 21:15:45 -0400 Message-ID: <043f01cd8ef1$d0b30c70$72192550$@ark-net.org> MIME-Version: 1.0 X-Mailer: Microsoft Outlook 14.0 Thread-Index: Ac2O8HMz6xaM8sRLQDCi9nZjGnWsOQ== Content-Language: en-us Cc: jsoriano617@gmail.com Subject: [Xen-users] Intel 4 Series Chipset Integrated Graphics Controller X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org I am trying to get the onboard graphics passthrough on a Dell Optiplex 780, but everytime I try as soon as Windows loads the driver during startup, it bluescreens with a STOP error referring to PAGING on a NON-PAGED area or something like that. I was under the impression that it was plug and play, but maybe not. Anyone done this successfully? Details below: VM: Windows 7 32bit HVM Host: Fedora 14, with vanilla 3.4.10 kernel. Xen: Changeset 25746 IOMMU=1 MSI=1 XEN-PCIBACK (Built-in) passthrough=1 gfx-passthru=1 I have passed in both PCI devices for the graphics card, one ended in 0 and the other in 1. I have passed in Sound and USB, which work great. The graphics card works as well, I can start the VM and see ROMBIOS display on the monitor and go through setup, select the partition and then during the install once it loads the driver it bluescreens and then I have to start over again. I can finish the install if I don't pass the graphics through, then if I try to start it with gfx-passthru, it'll bluescreen. If I start it without, then attach the pci devices it'll prompt me to restart, and then bluescreen after it starts... Any help would be greatly appreciated. Mike _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Mon Sep 10 01:17:19 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Mon, 10 Sep 2012 01:17:19 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TAsb9-0002Fj-R8; Mon, 10 Sep 2012 01:15:35 +0000 Received: from mail27.messagelabs.com ([193.109.254.147]) by lists.xen.org with smtp (Exim 4.72) (envelope-from ) id 1TAsb7-0002Fe-It for xen-users@lists.xen.org; Mon, 10 Sep 2012 01:15:33 +0000 X-Env-Sender: mike.a.collins@ark-net.org X-Msg-Ref: server-9.tower-27.messagelabs.com!1347239726!9011676!1 X-Originating-IP: [216.33.127.81] X-SpamReason: No, hits=0.5 required=7.0 tests=BODY_RANDOM_LONG X-StarScan-Received: X-StarScan-Version: 6.6.1.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 18851 invoked from network); 10 Sep 2012 01:15:27 -0000 Received: from mta21.charter.net (HELO mta21.charter.net) (216.33.127.81) by server-9.tower-27.messagelabs.com with SMTP; 10 Sep 2012 01:15:27 -0000 Received: from imp10 ([10.20.200.15]) by mta21.charter.net (InterMail vM.8.01.05.02 201-2260-151-103-20110920) with ESMTP id <20120910011526.CNHM12025.mta21.charter.net@imp10>; Sun, 9 Sep 2012 21:15:26 -0400 Received: from mail.ark-net.org ([75.138.215.251]) by imp10 with smtp.charter.net id xDFR1j00Z5S18aK05DFSsw; Sun, 09 Sep 2012 21:15:26 -0400 X-Authority-Analysis: v=1.1 cv=qU9vTENroOq2s6i9/sTxZt9WOCoWX/XGfIT3Tj8F8dQ= c=1 sm=1 a=_-NSfvUG02YA:10 a=VCxxn1A5iYMA:10 a=wPDyFdB5xvgA:10 a=YBs1tj9y_9UA:10 a=kj9zAlcOel0A:10 a=4A50YBgeEUJTzIKlCdeDOQ==:17 a=ecfIRNFSBeCB0Za1qSgA:9 a=CjuIK1q_8ugA:10 a=4A50YBgeEUJTzIKlCdeDOQ==:117 Received: from localhost (unknown [127.0.0.1]) by mail.ark-net.org (Postfix) with ESMTP id 87A8B203B4; Mon, 10 Sep 2012 01:15:38 +0000 (UTC) X-Virus-Scanned: amavisd-new at ark-net.org Received: from mail.ark-net.org ([127.0.0.1]) by localhost (mail.ark-net.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id qLqy4hANSxWt; Sun, 9 Sep 2012 21:15:12 -0400 (EDT) Received: from mikePC (unknown [192.168.1.35]) by mail.ark-net.org (Postfix) with ESMTP id EE401203AC; Sun, 9 Sep 2012 21:15:12 -0400 (EDT) From: "Michael A. Collins" To: Date: Sun, 9 Sep 2012 21:15:45 -0400 Message-ID: <043f01cd8ef1$d0b30c70$72192550$@ark-net.org> MIME-Version: 1.0 X-Mailer: Microsoft Outlook 14.0 Thread-Index: Ac2O8HMz6xaM8sRLQDCi9nZjGnWsOQ== Content-Language: en-us Cc: jsoriano617@gmail.com Subject: [Xen-users] Intel 4 Series Chipset Integrated Graphics Controller X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org I am trying to get the onboard graphics passthrough on a Dell Optiplex 780, but everytime I try as soon as Windows loads the driver during startup, it bluescreens with a STOP error referring to PAGING on a NON-PAGED area or something like that. I was under the impression that it was plug and play, but maybe not. Anyone done this successfully? Details below: VM: Windows 7 32bit HVM Host: Fedora 14, with vanilla 3.4.10 kernel. Xen: Changeset 25746 IOMMU=1 MSI=1 XEN-PCIBACK (Built-in) passthrough=1 gfx-passthru=1 I have passed in both PCI devices for the graphics card, one ended in 0 and the other in 1. I have passed in Sound and USB, which work great. The graphics card works as well, I can start the VM and see ROMBIOS display on the monitor and go through setup, select the partition and then during the install once it loads the driver it bluescreens and then I have to start over again. I can finish the install if I don't pass the graphics through, then if I try to start it with gfx-passthru, it'll bluescreen. If I start it without, then attach the pci devices it'll prompt me to restart, and then bluescreen after it starts... Any help would be greatly appreciated. Mike _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Mon Sep 10 08:41:05 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Mon, 10 Sep 2012 08:41:05 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TAzX5-0005Xn-8q; Mon, 10 Sep 2012 08:39:51 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TAzX3-0005XX-TW for xen-users@lists.xen.org; Mon, 10 Sep 2012 08:39:50 +0000 Received: from [85.158.138.51:54826] by server-3.bemta-3.messagelabs.com id EF/E4-21322-557AD405; Mon, 10 Sep 2012 08:39:49 +0000 X-Env-Sender: Ian.Campbell@citrix.com X-Msg-Ref: server-13.tower-174.messagelabs.com!1347266387!10952228!1 X-Originating-IP: [62.200.22.115] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogNjIuMjAwLjIyLjExNSA9PiAxMTIzMzg=\n X-StarScan-Received: X-StarScan-Version: 6.6.1.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 23628 invoked from network); 10 Sep 2012 08:39:48 -0000 Received: from smtp.ctxuk.citrix.com (HELO SMTP.EU.CITRIX.COM) (62.200.22.115) by server-13.tower-174.messagelabs.com with RC4-SHA encrypted SMTP; 10 Sep 2012 08:39:48 -0000 X-IronPort-AV: E=Sophos;i="4.80,396,1344211200"; d="scan'208";a="14435224" Received: from lonpmailmx01.citrite.net ([10.30.203.162]) by LONPIPO01.EU.CITRIX.COM with ESMTP/TLS/RC4-MD5; 10 Sep 2012 08:39:47 +0000 Received: from [10.80.2.42] (10.80.2.42) by LONPMAILMX01.citrite.net (10.30.203.162) with Microsoft SMTP Server id 8.3.279.1; Mon, 10 Sep 2012 09:39:47 +0100 Message-ID: <1347266386.5305.17.camel@zakaz.uk.xensource.com> From: Ian Campbell To: Maik Brauer Date: Mon, 10 Sep 2012 09:39:46 +0100 In-Reply-To: References: <9F8FD2B0-450A-4A6E-A929-BA240ED1D997@mbs-systems.net> <1346746297.32462.37.camel@zakaz.uk.xensource.com> Organization: Citrix Systems, Inc. X-Mailer: Evolution 3.4.3-1 MIME-Version: 1.0 Cc: "xen-users@lists.xen.org" , Casey DeLorme Subject: Re: [Xen-users] Dom0 crashed when rebooting whilst DomU are running X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org On Sat, 2012-09-08 at 15:50 +0100, Maik Brauer wrote: > On Sep 4, 2012, at 10:11 AM, Ian Campbell wrote: > > > Could you not top post please, it makes it rather hard to follow the > > flow of the conversation. > > On Mon, 2012-09-03 at 18:10 +0100, Casey DeLorme wrote: > >> As stated, you can alias shutdown to do exactly what you need, it can > >> be as simple as a series of hard-coded operations to a complex custom > >> shell script that parses your domains and closes each with feedback. > > > > Xen ships the "xendomains" initscript which can halt guest on shutdown > > as well as automatically start specific guests on boot. It can also be > > configured to suspend/resume them or (I think) migrate them away. > > > > For diagnosing the crash itself more details will be required than were > > provided in the original post. Please see > > http://wiki.xen.org/wiki/Reporting_Bugs_against_Xen for some guidance. > > At a minimum we would need a capture (serial console or photo) of the > > crash backtrace. > > > > Ian. > > > > > I found out that it hangs during re-boot of dom0 when having more > Network interfaces involved, like: > vif = [ 'mac=06:46:AB:CC:11:01, ip=', '', '', > 'mac=06:04:AB:BB:11:03, bridge=VLAN20, script=vif-bridge', '', > 'mac=06:04:AB:BB:11:05, bridge=VLAN40, script=vif-bridge' ] 6 interfaces total, 3 of which have a random mac on each reboot and all get put on the default bridge? Is your default script vif-bridge or something else? Have you modified any of these scripts? > in case you use just one or having the basic line in place, it is > working: > vif = [ '' ] > > The system stops after initiating the reboot at the following line in the console: System will restart........... So this is a hang, not a crash as suggested originally? If it is a hang then you might have some luck using hte magic sysrq keys to print lists of blocked tasks. I'm not sure in Squeeze but you might need to enable this as described in Documentation/sysrq.txt in the Linux source. Blocked tasks are listed with SysRQ-'w'. If you have serial console then 't' will list all task, but that list can be quite long so it is useless without a serial console. > In the Logfile of /var/log/message you can find this as the last line: > Sep 8 15:44:28 rootsrv01 shutdown[2445]: shutting down for system reboot > Sep 8 15:44:31 rootsrv01 kernel: [ 73.716246] VLAN20: port 1(vif2.3) entering forwarding state > Sep 8 15:44:31 rootsrv01 kernel: [ 74.500111] VLAN40: port 1(vif2.5) entering forwarding state > Sep 8 15:44:34 rootsrv01 kernel: [ 77.317431] VLAN20: port 1(vif2.3) entering disabled state > Sep 8 15:44:34 rootsrv01 kernel: [ 77.317490] VLAN20: port 1(vif2.3) entering disabled state > Sep 8 15:44:36 rootsrv01 kernel: [ 79.368685] VLAN40: port 1(vif2.5) entering disabled state > Sep 8 15:44:36 rootsrv01 kernel: [ 79.369156] VLAN40: port 1(vif2.5) entering disabled state > Sep 8 15:44:37 rootsrv01 kernel: Kernel logging (proc) stopped. > Sep 8 15:44:37 rootsrv01 rsyslogd: [origin software="rsyslogd" swVersion="4.6.4" x-pid="890" x-info="http://www.rsyslog.com"] exiting on signal 15. > > In the /var/log/daemong.log you can find this message: > Sep 8 15:44:37 rootsrv01 acpid: exiting > Sep 8 15:44:37 rootsrv01 rpc.statd[750]: Caught signal 15, un-registering and exiting All the above (both message and daemon.log) look like normal parts of shutting down to me. > Sep 8 15:44:37 rootsrv01 udevd-work[2276]: '/etc/xen/scripts/vif-setup offline type_if=vif' unexpected exit with status 0x000f This might be worth following up on. I would do this by adding near the top of vif-setup and/or vif-bridge (or whichever script you use): exec 1>>/var/log/vif-setup.log exec 2>&1 I would then also annotate all through vif-bridge in the offline path with echo statements showing how far it got and what command was to be run next. Ian. _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Mon Sep 10 08:41:05 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Mon, 10 Sep 2012 08:41:05 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TAzX5-0005Xn-8q; Mon, 10 Sep 2012 08:39:51 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TAzX3-0005XX-TW for xen-users@lists.xen.org; Mon, 10 Sep 2012 08:39:50 +0000 Received: from [85.158.138.51:54826] by server-3.bemta-3.messagelabs.com id EF/E4-21322-557AD405; Mon, 10 Sep 2012 08:39:49 +0000 X-Env-Sender: Ian.Campbell@citrix.com X-Msg-Ref: server-13.tower-174.messagelabs.com!1347266387!10952228!1 X-Originating-IP: [62.200.22.115] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogNjIuMjAwLjIyLjExNSA9PiAxMTIzMzg=\n X-StarScan-Received: X-StarScan-Version: 6.6.1.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 23628 invoked from network); 10 Sep 2012 08:39:48 -0000 Received: from smtp.ctxuk.citrix.com (HELO SMTP.EU.CITRIX.COM) (62.200.22.115) by server-13.tower-174.messagelabs.com with RC4-SHA encrypted SMTP; 10 Sep 2012 08:39:48 -0000 X-IronPort-AV: E=Sophos;i="4.80,396,1344211200"; d="scan'208";a="14435224" Received: from lonpmailmx01.citrite.net ([10.30.203.162]) by LONPIPO01.EU.CITRIX.COM with ESMTP/TLS/RC4-MD5; 10 Sep 2012 08:39:47 +0000 Received: from [10.80.2.42] (10.80.2.42) by LONPMAILMX01.citrite.net (10.30.203.162) with Microsoft SMTP Server id 8.3.279.1; Mon, 10 Sep 2012 09:39:47 +0100 Message-ID: <1347266386.5305.17.camel@zakaz.uk.xensource.com> From: Ian Campbell To: Maik Brauer Date: Mon, 10 Sep 2012 09:39:46 +0100 In-Reply-To: References: <9F8FD2B0-450A-4A6E-A929-BA240ED1D997@mbs-systems.net> <1346746297.32462.37.camel@zakaz.uk.xensource.com> Organization: Citrix Systems, Inc. X-Mailer: Evolution 3.4.3-1 MIME-Version: 1.0 Cc: "xen-users@lists.xen.org" , Casey DeLorme Subject: Re: [Xen-users] Dom0 crashed when rebooting whilst DomU are running X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org On Sat, 2012-09-08 at 15:50 +0100, Maik Brauer wrote: > On Sep 4, 2012, at 10:11 AM, Ian Campbell wrote: > > > Could you not top post please, it makes it rather hard to follow the > > flow of the conversation. > > On Mon, 2012-09-03 at 18:10 +0100, Casey DeLorme wrote: > >> As stated, you can alias shutdown to do exactly what you need, it can > >> be as simple as a series of hard-coded operations to a complex custom > >> shell script that parses your domains and closes each with feedback. > > > > Xen ships the "xendomains" initscript which can halt guest on shutdown > > as well as automatically start specific guests on boot. It can also be > > configured to suspend/resume them or (I think) migrate them away. > > > > For diagnosing the crash itself more details will be required than were > > provided in the original post. Please see > > http://wiki.xen.org/wiki/Reporting_Bugs_against_Xen for some guidance. > > At a minimum we would need a capture (serial console or photo) of the > > crash backtrace. > > > > Ian. > > > > > I found out that it hangs during re-boot of dom0 when having more > Network interfaces involved, like: > vif = [ 'mac=06:46:AB:CC:11:01, ip=', '', '', > 'mac=06:04:AB:BB:11:03, bridge=VLAN20, script=vif-bridge', '', > 'mac=06:04:AB:BB:11:05, bridge=VLAN40, script=vif-bridge' ] 6 interfaces total, 3 of which have a random mac on each reboot and all get put on the default bridge? Is your default script vif-bridge or something else? Have you modified any of these scripts? > in case you use just one or having the basic line in place, it is > working: > vif = [ '' ] > > The system stops after initiating the reboot at the following line in the console: System will restart........... So this is a hang, not a crash as suggested originally? If it is a hang then you might have some luck using hte magic sysrq keys to print lists of blocked tasks. I'm not sure in Squeeze but you might need to enable this as described in Documentation/sysrq.txt in the Linux source. Blocked tasks are listed with SysRQ-'w'. If you have serial console then 't' will list all task, but that list can be quite long so it is useless without a serial console. > In the Logfile of /var/log/message you can find this as the last line: > Sep 8 15:44:28 rootsrv01 shutdown[2445]: shutting down for system reboot > Sep 8 15:44:31 rootsrv01 kernel: [ 73.716246] VLAN20: port 1(vif2.3) entering forwarding state > Sep 8 15:44:31 rootsrv01 kernel: [ 74.500111] VLAN40: port 1(vif2.5) entering forwarding state > Sep 8 15:44:34 rootsrv01 kernel: [ 77.317431] VLAN20: port 1(vif2.3) entering disabled state > Sep 8 15:44:34 rootsrv01 kernel: [ 77.317490] VLAN20: port 1(vif2.3) entering disabled state > Sep 8 15:44:36 rootsrv01 kernel: [ 79.368685] VLAN40: port 1(vif2.5) entering disabled state > Sep 8 15:44:36 rootsrv01 kernel: [ 79.369156] VLAN40: port 1(vif2.5) entering disabled state > Sep 8 15:44:37 rootsrv01 kernel: Kernel logging (proc) stopped. > Sep 8 15:44:37 rootsrv01 rsyslogd: [origin software="rsyslogd" swVersion="4.6.4" x-pid="890" x-info="http://www.rsyslog.com"] exiting on signal 15. > > In the /var/log/daemong.log you can find this message: > Sep 8 15:44:37 rootsrv01 acpid: exiting > Sep 8 15:44:37 rootsrv01 rpc.statd[750]: Caught signal 15, un-registering and exiting All the above (both message and daemon.log) look like normal parts of shutting down to me. > Sep 8 15:44:37 rootsrv01 udevd-work[2276]: '/etc/xen/scripts/vif-setup offline type_if=vif' unexpected exit with status 0x000f This might be worth following up on. I would do this by adding near the top of vif-setup and/or vif-bridge (or whichever script you use): exec 1>>/var/log/vif-setup.log exec 2>&1 I would then also annotate all through vif-bridge in the offline path with echo statements showing how far it got and what command was to be run next. Ian. _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Mon Sep 10 09:04:24 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Mon, 10 Sep 2012 09:04:24 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TAztn-0006UR-VD; Mon, 10 Sep 2012 09:03:19 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TAztm-0006UM-9v for xen-users@lists.xensource.com; Mon, 10 Sep 2012 09:03:18 +0000 Received: from [85.158.143.99:38913] by server-3.bemta-4.messagelabs.com id 14/A4-08232-5DCAD405; Mon, 10 Sep 2012 09:03:17 +0000 X-Env-Sender: Ian.Campbell@citrix.com X-Msg-Ref: server-5.tower-216.messagelabs.com!1347267796!29129044!1 X-Originating-IP: [62.200.22.115] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogNjIuMjAwLjIyLjExNSA9PiAxMTIyODk=\n X-StarScan-Received: X-StarScan-Version: 6.6.1.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 6983 invoked from network); 10 Sep 2012 09:03:17 -0000 Received: from smtp.eu.citrix.com (HELO SMTP.EU.CITRIX.COM) (62.200.22.115) by server-5.tower-216.messagelabs.com with RC4-SHA encrypted SMTP; 10 Sep 2012 09:03:17 -0000 X-IronPort-AV: E=Sophos;i="4.80,396,1344211200"; d="scan'208";a="14436089" Received: from lonpmailmx01.citrite.net ([10.30.203.162]) by LONPIPO01.EU.CITRIX.COM with ESMTP/TLS/RC4-MD5; 10 Sep 2012 09:02:49 +0000 Received: from [10.80.2.42] (10.80.2.42) by LONPMAILMX01.citrite.net (10.30.203.162) with Microsoft SMTP Server id 8.3.279.1; Mon, 10 Sep 2012 10:02:49 +0100 Message-ID: <1347267768.5305.32.camel@zakaz.uk.xensource.com> From: Ian Campbell To: chris Date: Mon, 10 Sep 2012 10:02:48 +0100 In-Reply-To: References: <1346164781.9975.27.camel@zakaz.uk.xensource.com> <1346229699.9975.30.camel@zakaz.uk.xensource.com> Organization: Citrix Systems, Inc. X-Mailer: Evolution 3.4.3-1 MIME-Version: 1.0 Cc: Xen-Users List Subject: Re: [Xen-users] pvhvm on debian X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org On Sun, 2012-09-09 at 21:23 +0100, chris wrote: > So as you can see the domU is identical kernel in both cases however > when the domU is running on the wheezy dom0 even despite that the > platform pci device appears exactly the same in lspci Is the contents of the initrd identical in both cases? Specifically do they both contain the same set of kernel modules? Note that CentOS does not strictly speaking contain "PVHVM", which is a more recent upstream development. What you have here is the PV drivers add on driver from the unmodified_drivers. Did these drivers ship with CentOS or did you get them from elsewhere? Do you have the source for them? The difference is that PVHVM is part of the kernel itself and are tightly integrated, while the unmodified_drivers are a set of drivers used as an "add-on" pack for various existing OSes (similar in principal to how e.g. the Windows drivers are supplied for Windows). The main differences in practice will be at setup and initialisation time, which of course is where things appear to be going wrong for you. I think this highlights why it is important to always give all the precise details in a bug report, this is the first time CentOS has been mentioned at all so I think I can be forgiven for assuming you were running Debian PVHVM in the guest too (which is what I spent time reproducing). > I've attached the configs and logs that you asked for I asked for guest console logs. The guest console logs are where the guest decisions about PVHVM drivers will be logged, if anywhere. sektor-qemu.txt and baraka-qemu.txt are identical, but they both contain references to "baraka" which should surely be "sektor" in the at least one place (e.g. the disk path) for that VM. Your vm configs show the name has changed in the disk path so I don't see why it isn't different in the logs too. re you sure these are the actual logs from real runs of the guest? > Any ideas how to debug further? The difference between the working > scenario and nonworking is the dom0 distro (squeeze vs wheezy), dom0 > kernel and dom0 hypervisor > Testing with both scenario's was done with the exact same domU so I > cant see how it could be a domU issue. Comparing your guest configs shows that they aren't actual quite identical though, for reasons other than the different names. One has apic=1 then other doesn't, I'm not sure what the default is, and also one names its vif with vifname and the other doesn't. Perhaps these don't matter but it suggests that you need to double check your assumption that these VMs are "identical". Ian. _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Mon Sep 10 09:04:24 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Mon, 10 Sep 2012 09:04:24 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TAztn-0006UR-VD; Mon, 10 Sep 2012 09:03:19 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TAztm-0006UM-9v for xen-users@lists.xensource.com; Mon, 10 Sep 2012 09:03:18 +0000 Received: from [85.158.143.99:38913] by server-3.bemta-4.messagelabs.com id 14/A4-08232-5DCAD405; Mon, 10 Sep 2012 09:03:17 +0000 X-Env-Sender: Ian.Campbell@citrix.com X-Msg-Ref: server-5.tower-216.messagelabs.com!1347267796!29129044!1 X-Originating-IP: [62.200.22.115] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogNjIuMjAwLjIyLjExNSA9PiAxMTIyODk=\n X-StarScan-Received: X-StarScan-Version: 6.6.1.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 6983 invoked from network); 10 Sep 2012 09:03:17 -0000 Received: from smtp.eu.citrix.com (HELO SMTP.EU.CITRIX.COM) (62.200.22.115) by server-5.tower-216.messagelabs.com with RC4-SHA encrypted SMTP; 10 Sep 2012 09:03:17 -0000 X-IronPort-AV: E=Sophos;i="4.80,396,1344211200"; d="scan'208";a="14436089" Received: from lonpmailmx01.citrite.net ([10.30.203.162]) by LONPIPO01.EU.CITRIX.COM with ESMTP/TLS/RC4-MD5; 10 Sep 2012 09:02:49 +0000 Received: from [10.80.2.42] (10.80.2.42) by LONPMAILMX01.citrite.net (10.30.203.162) with Microsoft SMTP Server id 8.3.279.1; Mon, 10 Sep 2012 10:02:49 +0100 Message-ID: <1347267768.5305.32.camel@zakaz.uk.xensource.com> From: Ian Campbell To: chris Date: Mon, 10 Sep 2012 10:02:48 +0100 In-Reply-To: References: <1346164781.9975.27.camel@zakaz.uk.xensource.com> <1346229699.9975.30.camel@zakaz.uk.xensource.com> Organization: Citrix Systems, Inc. X-Mailer: Evolution 3.4.3-1 MIME-Version: 1.0 Cc: Xen-Users List Subject: Re: [Xen-users] pvhvm on debian X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org On Sun, 2012-09-09 at 21:23 +0100, chris wrote: > So as you can see the domU is identical kernel in both cases however > when the domU is running on the wheezy dom0 even despite that the > platform pci device appears exactly the same in lspci Is the contents of the initrd identical in both cases? Specifically do they both contain the same set of kernel modules? Note that CentOS does not strictly speaking contain "PVHVM", which is a more recent upstream development. What you have here is the PV drivers add on driver from the unmodified_drivers. Did these drivers ship with CentOS or did you get them from elsewhere? Do you have the source for them? The difference is that PVHVM is part of the kernel itself and are tightly integrated, while the unmodified_drivers are a set of drivers used as an "add-on" pack for various existing OSes (similar in principal to how e.g. the Windows drivers are supplied for Windows). The main differences in practice will be at setup and initialisation time, which of course is where things appear to be going wrong for you. I think this highlights why it is important to always give all the precise details in a bug report, this is the first time CentOS has been mentioned at all so I think I can be forgiven for assuming you were running Debian PVHVM in the guest too (which is what I spent time reproducing). > I've attached the configs and logs that you asked for I asked for guest console logs. The guest console logs are where the guest decisions about PVHVM drivers will be logged, if anywhere. sektor-qemu.txt and baraka-qemu.txt are identical, but they both contain references to "baraka" which should surely be "sektor" in the at least one place (e.g. the disk path) for that VM. Your vm configs show the name has changed in the disk path so I don't see why it isn't different in the logs too. re you sure these are the actual logs from real runs of the guest? > Any ideas how to debug further? The difference between the working > scenario and nonworking is the dom0 distro (squeeze vs wheezy), dom0 > kernel and dom0 hypervisor > Testing with both scenario's was done with the exact same domU so I > cant see how it could be a domU issue. Comparing your guest configs shows that they aren't actual quite identical though, for reasons other than the different names. One has apic=1 then other doesn't, I'm not sure what the default is, and also one names its vif with vifname and the other doesn't. Perhaps these don't matter but it suggests that you need to double check your assumption that these VMs are "identical". Ian. _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Mon Sep 10 10:18:53 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Mon, 10 Sep 2012 10:18:53 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TB13x-0008RD-Qi; Mon, 10 Sep 2012 10:17:53 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TB13w-0008Qx-IR for xen-users@lists.xen.org; Mon, 10 Sep 2012 10:17:52 +0000 Received: from [85.158.138.51:15231] by server-2.bemta-3.messagelabs.com id 24/87-04862-F4EBD405; Mon, 10 Sep 2012 10:17:51 +0000 X-Env-Sender: ashok.anand@gmail.com X-Msg-Ref: server-8.tower-174.messagelabs.com!1347272269!29613421!1 X-Originating-IP: [209.85.214.173] X-SpamReason: No, hits=0.4 required=7.0 tests=HTML_30_40,HTML_MESSAGE, ML_RADAR_SPEW_LINKS_14,RCVD_BY_IP,spamassassin: X-StarScan-Received: X-StarScan-Version: 6.6.1.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 3011 invoked from network); 10 Sep 2012 10:17:50 -0000 Received: from mail-ob0-f173.google.com (HELO mail-ob0-f173.google.com) (209.85.214.173) by server-8.tower-174.messagelabs.com with RC4-SHA encrypted SMTP; 10 Sep 2012 10:17:50 -0000 Received: by obbta14 with SMTP id ta14so3520204obb.32 for ; Mon, 10 Sep 2012 03:17:49 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:date:message-id:subject:from:to:content-type; bh=WzyomSgdM8jP7v0SWSj08rlkzgRsalX8LTA0cQTta7I=; b=U8DVa32588vyxM/jGEWaDNftLpu/FKABBNMp1NKXz5PrVl+0QztjeBHaLzNjsZxMph VK5BZ50IqjTEXclY0gnanXB1hphlxF2LIlYtIA7AQ+6jLDhJLZgbsy79iysJT1k3c36p DgtUVF1iuz/5A5CrQRfKUrJRGp63DzPX62HEo9sFE5i0lcygDtmENm/7e68zJGfOFh+P 78/p0pxi7UNVB4x/LGXxuYohU5qVEGNohZHrhm3NkOTFaGoYVMn+yCpa+oPl8Ay3NQqx ULhy9WyxdXF29sRQRyRwSDjzyD688wPUH06L9CHjDduttDCejc2N8Ufv/YdYxqcym6z+ V1Vw== MIME-Version: 1.0 Received: by 10.182.193.7 with SMTP id hk7mr13407418obc.30.1347272269156; Mon, 10 Sep 2012 03:17:49 -0700 (PDT) Received: by 10.182.32.102 with HTTP; Mon, 10 Sep 2012 03:17:49 -0700 (PDT) Date: Mon, 10 Sep 2012 15:47:49 +0530 Message-ID: From: Ashok Anand To: xen-users@lists.xen.org Subject: [Xen-users] issue using SRIOV "Unable to start - perhaps the PF driver is not up yet", while PF driver is actually up X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============0085661898658311209==" Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org --===============0085661898658311209== Content-Type: multipart/alternative; boundary=f46d0447868f04d21d04c956451b --f46d0447868f04d21d04c956451b Content-Type: text/plain; charset=ISO-8859-1 Hi, I am trying to use SRIOV, usnig xen 4.0 on debian. On my dom0, xm pci-list-assignable-devices show that 0000:0f:10.0 0000:0f:10.2 0000:0f:10.4 0000:0f:10.6 0000:0f:11.2 0000:0f:11.4 0000:0f:11.6 these virtual interfaces correspond to eth2, i attach 0f:10.0 to a domU ubuntu machine, xm pci-attach ubuntu 0f:10.0 on my dom0 machine, i can ping other machine using eth2, (implying PF on eth2 is active) on my domU machine, when i attach the virtual function, i get the following messages [ 2282.688356] ixgbevf 0000:00:00.0: Xen PCI mapped GSI0 to IRQ28 [ 2282.688470] ixgbevf 0000:00:00.0: setting latency timer to 64 [ 2282.690187] ixgbevf 0000:00:00.0: PF still in reset state, assigning new address while PF on eth2 is there and active, since i can ping other machine. Now, when I try to bring up the VF interface on domU, i get the following error 2476.295582] Unable to start - perhaps the PF Driver isn't up yet SIOCSIFFLAGS: Network is down [ 2476.296917] Unable to start - perhaps the PF Driver isn't up yet SIOCSIFFLAGS: Network is down and on dmesg on domU, [ 2476.295582] Unable to start - perhaps the PF Driver isn't up yet [ 2476.296917] Unable to start - perhaps the PF Driver isn't up yet Any thoughts on what could be wrong? I have been struggling with this for quite some time and would really appreciate your thoughts on it. Thanks, Ashok --f46d0447868f04d21d04c956451b Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Hi,=A0

I am trying to use SRIOV, usnig xen 4.0 on debian= .=A0

On my dom0, xm pci-list-assignable-devices sh= ow that
0000:0f:10.0
0000:0f:10.2
0000:0= f:10.4
0000:0f:10.6
0000:0f:11.2
0000:0f:11.4
0= 000:0f:11.6

these virtual interfaces corresp= ond to eth2,=A0

i attach 0f:10.0 to a domU ubuntu = machine,=A0xm pci-attach ubuntu 0f:10.0

on my dom0 machine, i can ping other machine using eth2= , (implying PF on eth2 is active)

on my domU machi= ne, when i attach the virtual function, i get the following messages

[ 2282.688356] ixgbevf 0000:00:00.0: Xen PCI mappe= d GSI0 to IRQ28
[ 2282.688470] ixgbevf 0000:00:00.0: setting late= ncy timer to 64
[ 2282.690187] ixgbevf 0000:00:00.0: PF still in = reset state, assigning new address

while PF on eth2 is =A0there and active, since i = can ping other machine.

Now, when I try to bring u= p the VF interface on domU,=A0
=A0i get the following error
=

=A02476.295582] Unable to start - perhaps the PF Driver= isn't up yet
SIOCSIFFLAGS: Network is down
[ 2476.= 296917] Unable to start - perhaps the PF Driver isn't up yet
SIOCSIFFLAGS: Network is down

and on dmesg o= n domU,=A0
[ 2476.295582] Unable to start - perhaps the PF D= river isn't up yet
[ 2476.296917] Unable to start - perhaps t= he PF Driver isn't up yet


Any thoughts on what could be wron= g? I have been struggling with this for quite some time
and would= really appreciate your thoughts on it.

Thanks,=A0=
Ashok





--f46d0447868f04d21d04c956451b-- --===============0085661898658311209== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users --===============0085661898658311209==-- From xen-users-bounces@lists.xen.org Mon Sep 10 10:18:53 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Mon, 10 Sep 2012 10:18:53 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TB13x-0008RD-Qi; Mon, 10 Sep 2012 10:17:53 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TB13w-0008Qx-IR for xen-users@lists.xen.org; Mon, 10 Sep 2012 10:17:52 +0000 Received: from [85.158.138.51:15231] by server-2.bemta-3.messagelabs.com id 24/87-04862-F4EBD405; Mon, 10 Sep 2012 10:17:51 +0000 X-Env-Sender: ashok.anand@gmail.com X-Msg-Ref: server-8.tower-174.messagelabs.com!1347272269!29613421!1 X-Originating-IP: [209.85.214.173] X-SpamReason: No, hits=0.4 required=7.0 tests=HTML_30_40,HTML_MESSAGE, ML_RADAR_SPEW_LINKS_14,RCVD_BY_IP,spamassassin: X-StarScan-Received: X-StarScan-Version: 6.6.1.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 3011 invoked from network); 10 Sep 2012 10:17:50 -0000 Received: from mail-ob0-f173.google.com (HELO mail-ob0-f173.google.com) (209.85.214.173) by server-8.tower-174.messagelabs.com with RC4-SHA encrypted SMTP; 10 Sep 2012 10:17:50 -0000 Received: by obbta14 with SMTP id ta14so3520204obb.32 for ; Mon, 10 Sep 2012 03:17:49 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:date:message-id:subject:from:to:content-type; bh=WzyomSgdM8jP7v0SWSj08rlkzgRsalX8LTA0cQTta7I=; b=U8DVa32588vyxM/jGEWaDNftLpu/FKABBNMp1NKXz5PrVl+0QztjeBHaLzNjsZxMph VK5BZ50IqjTEXclY0gnanXB1hphlxF2LIlYtIA7AQ+6jLDhJLZgbsy79iysJT1k3c36p DgtUVF1iuz/5A5CrQRfKUrJRGp63DzPX62HEo9sFE5i0lcygDtmENm/7e68zJGfOFh+P 78/p0pxi7UNVB4x/LGXxuYohU5qVEGNohZHrhm3NkOTFaGoYVMn+yCpa+oPl8Ay3NQqx ULhy9WyxdXF29sRQRyRwSDjzyD688wPUH06L9CHjDduttDCejc2N8Ufv/YdYxqcym6z+ V1Vw== MIME-Version: 1.0 Received: by 10.182.193.7 with SMTP id hk7mr13407418obc.30.1347272269156; Mon, 10 Sep 2012 03:17:49 -0700 (PDT) Received: by 10.182.32.102 with HTTP; Mon, 10 Sep 2012 03:17:49 -0700 (PDT) Date: Mon, 10 Sep 2012 15:47:49 +0530 Message-ID: From: Ashok Anand To: xen-users@lists.xen.org Subject: [Xen-users] issue using SRIOV "Unable to start - perhaps the PF driver is not up yet", while PF driver is actually up X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============0085661898658311209==" Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org --===============0085661898658311209== Content-Type: multipart/alternative; boundary=f46d0447868f04d21d04c956451b --f46d0447868f04d21d04c956451b Content-Type: text/plain; charset=ISO-8859-1 Hi, I am trying to use SRIOV, usnig xen 4.0 on debian. On my dom0, xm pci-list-assignable-devices show that 0000:0f:10.0 0000:0f:10.2 0000:0f:10.4 0000:0f:10.6 0000:0f:11.2 0000:0f:11.4 0000:0f:11.6 these virtual interfaces correspond to eth2, i attach 0f:10.0 to a domU ubuntu machine, xm pci-attach ubuntu 0f:10.0 on my dom0 machine, i can ping other machine using eth2, (implying PF on eth2 is active) on my domU machine, when i attach the virtual function, i get the following messages [ 2282.688356] ixgbevf 0000:00:00.0: Xen PCI mapped GSI0 to IRQ28 [ 2282.688470] ixgbevf 0000:00:00.0: setting latency timer to 64 [ 2282.690187] ixgbevf 0000:00:00.0: PF still in reset state, assigning new address while PF on eth2 is there and active, since i can ping other machine. Now, when I try to bring up the VF interface on domU, i get the following error 2476.295582] Unable to start - perhaps the PF Driver isn't up yet SIOCSIFFLAGS: Network is down [ 2476.296917] Unable to start - perhaps the PF Driver isn't up yet SIOCSIFFLAGS: Network is down and on dmesg on domU, [ 2476.295582] Unable to start - perhaps the PF Driver isn't up yet [ 2476.296917] Unable to start - perhaps the PF Driver isn't up yet Any thoughts on what could be wrong? I have been struggling with this for quite some time and would really appreciate your thoughts on it. Thanks, Ashok --f46d0447868f04d21d04c956451b Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Hi,=A0

I am trying to use SRIOV, usnig xen 4.0 on debian= .=A0

On my dom0, xm pci-list-assignable-devices sh= ow that
0000:0f:10.0
0000:0f:10.2
0000:0= f:10.4
0000:0f:10.6
0000:0f:11.2
0000:0f:11.4
0= 000:0f:11.6

these virtual interfaces corresp= ond to eth2,=A0

i attach 0f:10.0 to a domU ubuntu = machine,=A0xm pci-attach ubuntu 0f:10.0

on my dom0 machine, i can ping other machine using eth2= , (implying PF on eth2 is active)

on my domU machi= ne, when i attach the virtual function, i get the following messages

[ 2282.688356] ixgbevf 0000:00:00.0: Xen PCI mappe= d GSI0 to IRQ28
[ 2282.688470] ixgbevf 0000:00:00.0: setting late= ncy timer to 64
[ 2282.690187] ixgbevf 0000:00:00.0: PF still in = reset state, assigning new address

while PF on eth2 is =A0there and active, since i = can ping other machine.

Now, when I try to bring u= p the VF interface on domU,=A0
=A0i get the following error
=

=A02476.295582] Unable to start - perhaps the PF Driver= isn't up yet
SIOCSIFFLAGS: Network is down
[ 2476.= 296917] Unable to start - perhaps the PF Driver isn't up yet
SIOCSIFFLAGS: Network is down

and on dmesg o= n domU,=A0
[ 2476.295582] Unable to start - perhaps the PF D= river isn't up yet
[ 2476.296917] Unable to start - perhaps t= he PF Driver isn't up yet


Any thoughts on what could be wron= g? I have been struggling with this for quite some time
and would= really appreciate your thoughts on it.

Thanks,=A0=
Ashok





--f46d0447868f04d21d04c956451b-- --===============0085661898658311209== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users --===============0085661898658311209==-- From xen-users-bounces@lists.xen.org Mon Sep 10 10:45:31 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Mon, 10 Sep 2012 10:45:31 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TB1Tp-000208-Uh; Mon, 10 Sep 2012 10:44:37 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TB1Tp-000200-Ar for xen-users@lists.xen.org; Mon, 10 Sep 2012 10:44:37 +0000 Received: from [85.158.143.99:48068] by server-2.bemta-4.messagelabs.com id EA/DA-21239-494CD405; Mon, 10 Sep 2012 10:44:36 +0000 X-Env-Sender: delentef@gmail.com X-Msg-Ref: server-15.tower-216.messagelabs.com!1347273874!29486420!1 X-Originating-IP: [209.85.210.45] X-SpamReason: No, hits=1.2 required=7.0 tests=HTML_10_20,HTML_MESSAGE, ML_RADAR_SPEW_LINKS_14,RCVD_BY_IP,spamassassin: X-StarScan-Received: X-StarScan-Version: 6.6.1.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 28575 invoked from network); 10 Sep 2012 10:44:35 -0000 Received: from mail-pz0-f45.google.com (HELO mail-pz0-f45.google.com) (209.85.210.45) by server-15.tower-216.messagelabs.com with RC4-SHA encrypted SMTP; 10 Sep 2012 10:44:35 -0000 Received: by dadn15 with SMTP id n15so1248961dad.32 for ; Mon, 10 Sep 2012 03:44:14 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:date:message-id:subject:from:to:content-type; bh=smkU2tlEMEW185tWG9uSXLeBfuWPkFSkWr+k0iFNrM0=; b=mDPuFNlEQ0E74nZ7BOBZw08djFRafTYIhPPEGjb3s3RelBc0HFD/3pzjI8GgpPV3Fl ygy3IRsJn/cjIoUMFXS5qDqIKmKavWNNxYiQm4IImWYDEaDwmef6qHLIW/CHKhaD0pbh fJ2YgKkUaX5Nh9i0gIfr9tkwZDriqyLxMzgxu8t8FgNa3MdB+XRSeTgBZXueMF4FQ7SH rz2Cx+GeeGAzihT8r/icw3CRA0IiorbOqCh5LtTDzFXbIdyvmhtxfTg0sWnYpBU6EvnF aTZvZ3fhKq9L6YqqzkAdswchA8LfanUBuyf7dJsps1vsrCCwEPeyHVQPTNZuSPsP5uKo bcJw== MIME-Version: 1.0 Received: by 10.66.72.197 with SMTP id f5mr21450886pav.20.1347273854286; Mon, 10 Sep 2012 03:44:14 -0700 (PDT) Received: by 10.68.203.33 with HTTP; Mon, 10 Sep 2012 03:44:14 -0700 (PDT) Date: Mon, 10 Sep 2012 12:44:14 +0200 Message-ID: From: Fabrice Delente To: xen-users@lists.xen.org Subject: [Xen-users] Bugs in VNC viewer ? Mouse offset and keyboard map incorrect X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============0902464321421352117==" Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org --===============0902464321421352117== Content-Type: multipart/alternative; boundary=f46d042fddb07ff97b04c956a35b --f46d042fddb07ff97b04c956a35b Content-Type: text/plain; charset=UTF-8 Hello. Am I the only one to have problem with the VNC server that is included in Xen? Ihave tried with several VNC client, and every time * the mouse cursor is offset from the host system cursor; * the keys on the keyboard give characters that don't match (for example, typing ';' on my keyboard gives an 'm' on the guest's screen...) Thanks. -- Fabrice DELENTE --f46d042fddb07ff97b04c956a35b Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Hello.

Am I the only one to have problem with the VNC server that is= included in Xen? Ihave tried with several VNC client, and every time
* the mouse cursor is offset from the host system cursor;

* the ke= ys on the keyboard give characters that don't match (for example, typin= g ';' on my keyboard gives an 'm' on the guest's screen= ...)

Thanks.

--
Fabrice DELENTE
--f46d042fddb07ff97b04c956a35b-- --===============0902464321421352117== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users --===============0902464321421352117==-- From xen-users-bounces@lists.xen.org Mon Sep 10 10:45:31 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Mon, 10 Sep 2012 10:45:31 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TB1Tp-000208-Uh; Mon, 10 Sep 2012 10:44:37 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TB1Tp-000200-Ar for xen-users@lists.xen.org; Mon, 10 Sep 2012 10:44:37 +0000 Received: from [85.158.143.99:48068] by server-2.bemta-4.messagelabs.com id EA/DA-21239-494CD405; Mon, 10 Sep 2012 10:44:36 +0000 X-Env-Sender: delentef@gmail.com X-Msg-Ref: server-15.tower-216.messagelabs.com!1347273874!29486420!1 X-Originating-IP: [209.85.210.45] X-SpamReason: No, hits=1.2 required=7.0 tests=HTML_10_20,HTML_MESSAGE, ML_RADAR_SPEW_LINKS_14,RCVD_BY_IP,spamassassin: X-StarScan-Received: X-StarScan-Version: 6.6.1.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 28575 invoked from network); 10 Sep 2012 10:44:35 -0000 Received: from mail-pz0-f45.google.com (HELO mail-pz0-f45.google.com) (209.85.210.45) by server-15.tower-216.messagelabs.com with RC4-SHA encrypted SMTP; 10 Sep 2012 10:44:35 -0000 Received: by dadn15 with SMTP id n15so1248961dad.32 for ; Mon, 10 Sep 2012 03:44:14 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:date:message-id:subject:from:to:content-type; bh=smkU2tlEMEW185tWG9uSXLeBfuWPkFSkWr+k0iFNrM0=; b=mDPuFNlEQ0E74nZ7BOBZw08djFRafTYIhPPEGjb3s3RelBc0HFD/3pzjI8GgpPV3Fl ygy3IRsJn/cjIoUMFXS5qDqIKmKavWNNxYiQm4IImWYDEaDwmef6qHLIW/CHKhaD0pbh fJ2YgKkUaX5Nh9i0gIfr9tkwZDriqyLxMzgxu8t8FgNa3MdB+XRSeTgBZXueMF4FQ7SH rz2Cx+GeeGAzihT8r/icw3CRA0IiorbOqCh5LtTDzFXbIdyvmhtxfTg0sWnYpBU6EvnF aTZvZ3fhKq9L6YqqzkAdswchA8LfanUBuyf7dJsps1vsrCCwEPeyHVQPTNZuSPsP5uKo bcJw== MIME-Version: 1.0 Received: by 10.66.72.197 with SMTP id f5mr21450886pav.20.1347273854286; Mon, 10 Sep 2012 03:44:14 -0700 (PDT) Received: by 10.68.203.33 with HTTP; Mon, 10 Sep 2012 03:44:14 -0700 (PDT) Date: Mon, 10 Sep 2012 12:44:14 +0200 Message-ID: From: Fabrice Delente To: xen-users@lists.xen.org Subject: [Xen-users] Bugs in VNC viewer ? Mouse offset and keyboard map incorrect X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============0902464321421352117==" Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org --===============0902464321421352117== Content-Type: multipart/alternative; boundary=f46d042fddb07ff97b04c956a35b --f46d042fddb07ff97b04c956a35b Content-Type: text/plain; charset=UTF-8 Hello. Am I the only one to have problem with the VNC server that is included in Xen? Ihave tried with several VNC client, and every time * the mouse cursor is offset from the host system cursor; * the keys on the keyboard give characters that don't match (for example, typing ';' on my keyboard gives an 'm' on the guest's screen...) Thanks. -- Fabrice DELENTE --f46d042fddb07ff97b04c956a35b Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Hello.

Am I the only one to have problem with the VNC server that is= included in Xen? Ihave tried with several VNC client, and every time
* the mouse cursor is offset from the host system cursor;

* the ke= ys on the keyboard give characters that don't match (for example, typin= g ';' on my keyboard gives an 'm' on the guest's screen= ...)

Thanks.

--
Fabrice DELENTE
--f46d042fddb07ff97b04c956a35b-- --===============0902464321421352117== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users --===============0902464321421352117==-- From xen-users-bounces@lists.xen.org Mon Sep 10 12:01:50 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Mon, 10 Sep 2012 12:01:50 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TB2fo-0003zG-8x; Mon, 10 Sep 2012 12:01:04 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TB2fm-0003yY-20 for xen-users@lists.xensource.com; Mon, 10 Sep 2012 12:01:02 +0000 Received: from [85.158.139.83:27869] by server-10.bemta-5.messagelabs.com id CE/0F-10969-D76DD405; Mon, 10 Sep 2012 12:01:01 +0000 X-Env-Sender: tknchris@gmail.com X-Msg-Ref: server-10.tower-182.messagelabs.com!1347278456!29878746!1 X-Originating-IP: [209.85.223.171] X-SpamReason: No, hits=1.7 required=7.0 tests=BODY_RANDOM_LONG, HTML_10_20, HTML_MESSAGE, ML_RADAR_SPEW_LINKS_14, RCVD_BY_IP, spamassassin: X-StarScan-Received: X-StarScan-Version: 6.6.1.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 8869 invoked from network); 10 Sep 2012 12:00:57 -0000 Received: from mail-ie0-f171.google.com (HELO mail-ie0-f171.google.com) (209.85.223.171) by server-10.tower-182.messagelabs.com with RC4-SHA encrypted SMTP; 10 Sep 2012 12:00:57 -0000 Received: by ieje14 with SMTP id e14so3688493iej.30 for ; Mon, 10 Sep 2012 05:00:55 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=HrDdc1HC/sHowvTWhHW7d9jg3LKxRwv16Jbv9XgpFzM=; b=jaY1JMxTkdZvrnk89XVb2F/9XHnaFLsZ23Pow3PGNVQduh0ZRRFgWmNgDlLzU33sWT zKY642BOQl8yw/mH6E/x3vQWkgJNjjOTAJni+XjcIhc+W9VV0eiMIoEJJVMXlCKUroED tREskmVd/Em4g8O0UcuWN4rogjVFESGtGtTBLAbxBQmc1G5y47UCDUz+/hDXLXisdgR9 F8/d/ERxoboN0qglgA23f9Uq4axfonL+yQZNMz+GPCU9is1qImzFqDZvmuNBRFSvJlDn Af3OfaR7ltITbP/BL6H2wBFxXI9MgeM3DgEPGoOse/PHcUUHFmkNgB6um/kM/L2WaWt3 QMpg== MIME-Version: 1.0 Received: by 10.43.103.193 with SMTP id dj1mr17112903icc.2.1347278455561; Mon, 10 Sep 2012 05:00:55 -0700 (PDT) Received: by 10.64.58.46 with HTTP; Mon, 10 Sep 2012 05:00:55 -0700 (PDT) In-Reply-To: <1347267768.5305.32.camel@zakaz.uk.xensource.com> References: <1346164781.9975.27.camel@zakaz.uk.xensource.com> <1346229699.9975.30.camel@zakaz.uk.xensource.com> <1347267768.5305.32.camel@zakaz.uk.xensource.com> Date: Mon, 10 Sep 2012 08:00:55 -0400 Message-ID: From: chris To: Ian Campbell Cc: Xen-Users List Subject: Re: [Xen-users] pvhvm on debian X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============8634735010837734042==" Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org --===============8634735010837734042== Content-Type: multipart/alternative; boundary=bcaec51719c5c1dc6d04c957b556 --bcaec51719c5c1dc6d04c957b556 Content-Type: text/plain; charset=ISO-8859-1 Ian, You are awesome! I figured it out by looking at console logs. The nonworking domU had this in its console: Detected Xen platform device but not Xen VMM? (sig Microsoft Hv, eax 40000006) xen-platform-pci: probe of 0000:00:03.0 failed with error -22 The mention of hyperv reminded me back when I had to add viridian=1 in order to avoid bluescreens in certain newer versions of windows, and sure enough the nonworking centos domU had viridian=1 After removing/disabling this option the Xen pv drivers come up properly. Just for clarification on the centos side though, in regard to your guest about if I installed any additional standalone PV drivers, the answer is no. The only reason I referred to it as PVHVM was I assumed that maybe pvhvm had become mainline and the kernel centos was using had these features now. Anyway its all working now and its good to know it works in wheezy and I can continue to move towards that in production. Thanks for all your time and help chris On Mon, Sep 10, 2012 at 5:02 AM, Ian Campbell wrote: > On Sun, 2012-09-09 at 21:23 +0100, chris wrote: > > So as you can see the domU is identical kernel in both cases however > > when the domU is running on the wheezy dom0 even despite that the > > platform pci device appears exactly the same in lspci > > Is the contents of the initrd identical in both cases? Specifically do > they both contain the same set of kernel modules? > > Note that CentOS does not strictly speaking contain "PVHVM", which is a > more recent upstream development. What you have here is the PV drivers > add on driver from the unmodified_drivers. Did these drivers ship with > CentOS or did you get them from elsewhere? Do you have the source for > them? > > The difference is that PVHVM is part of the kernel itself and are > tightly integrated, while the unmodified_drivers are a set of drivers > used as an "add-on" pack for various existing OSes (similar in principal > to how e.g. the Windows drivers are supplied for Windows). The main > differences in practice will be at setup and initialisation time, which > of course is where things appear to be going wrong for you. > > I think this highlights why it is important to always give all the > precise details in a bug report, this is the first time CentOS has been > mentioned at all so I think I can be forgiven for assuming you were > running Debian PVHVM in the guest too (which is what I spent time > reproducing). > > > I've attached the configs and logs that you asked for > > I asked for guest console logs. The guest console logs are where the > guest decisions about PVHVM drivers will be logged, if anywhere. > > sektor-qemu.txt and baraka-qemu.txt are identical, but they both contain > references to "baraka" which should surely be "sektor" in the at least > one place (e.g. the disk path) for that VM. > > Your vm configs show the name has changed in the disk path so I don't > see why it isn't different in the logs too. re you sure these are the > actual logs from real runs of the guest? > > > Any ideas how to debug further? The difference between the working > > scenario and nonworking is the dom0 distro (squeeze vs wheezy), dom0 > > kernel and dom0 hypervisor > > Testing with both scenario's was done with the exact same domU so I > > cant see how it could be a domU issue. > > Comparing your guest configs shows that they aren't actual quite > identical though, for reasons other than the different names. > > One has apic=1 then other doesn't, I'm not sure what the default is, and > also one names its vif with vifname and the other doesn't. > > Perhaps these don't matter but it suggests that you need to double check > your assumption that these VMs are "identical". > > Ian. > > > > --bcaec51719c5c1dc6d04c957b556 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Ian,=A0

You are awesome! I figured it out by looking at = console logs. The nonworking domU had this in its console:

Detected Xen platform device but not Xen VMM? (sig Microsoft = Hv, eax 40000006)
xen-platform-pci: probe of 0000:00:03.0 failed with error -22

The mention of hyperv reminded me back when I had to= add viridian=3D1 in order to avoid bluescreens in certain newer versions o= f windows, and sure enough the nonworking centos domU had viridian=3D1
After removing/disabling this option the Xen pv drivers come up proper= ly.

Just for clarification on the centos side thou= gh, in regard to your guest about if I installed any additional standalone = PV drivers, the answer is no. The only reason I referred to it as PVHVM was= I assumed that maybe pvhvm had become mainline and the kernel centos was u= sing had these features now.=A0

Anyway its all working now and its good to know it work= s in wheezy and I can continue to move towards that in production.

Thanks for all your time and help
chris

On Mon, Sep 10, 2012 at 5:02 AM, Ian Ca= mpbell <Ian.Campbell@citrix.com> wrote:
On Sun, 2012-09-09 at 21:23 +0100, chris wrote:
> So as you can see the domU is identical kernel in both cases however > when the domU is running on the wheezy dom0 even despite that the
> platform pci device appears exactly the same in lspci

Is the contents of the initrd identical in both cases? Specifically d= o
they both contain the same set of kernel modules?

Note that CentOS does not strictly speaking contain "PVHVM", whic= h is a
more recent upstream development. What you have here is the PV drivers
add on driver from the unmodified_drivers. Did these drivers ship with
CentOS or did you get them from elsewhere? Do you have the source for
them?

The difference is that PVHVM is part of the kernel itself and are
tightly integrated, while the unmodified_drivers are a set of drivers
used as an "add-on" pack for various existing OSes (similar in pr= incipal
to how e.g. the Windows drivers are supplied for Windows). The main
differences in practice will be at setup and initialisation time, which
of course is where things appear to be going wrong for you.

I think this highlights why it is important to always give all the
precise details in a bug report, this is the first time CentOS has been
mentioned at all so I think I can be forgiven for assuming you were
running Debian PVHVM in the guest too (which is what I spent time
reproducing).

> I've attached the configs and logs that you asked for

I asked for guest console logs. The guest console logs are where the<= br> guest decisions about PVHVM drivers will be logged, if anywhere.

sektor-qemu.txt and baraka-qemu.txt are identical, but they both contain references to "baraka" which should surely be "sektor" = in the at least
one place (e.g. the disk path) for that VM.

Your vm configs show the name has changed in the disk path so I don't see why it isn't different in the logs too. re you sure these are the actual logs from real runs of the guest?

> Any ideas how to debug further? The difference between the working
> scenario and nonworking is the dom0 distro (squeeze vs wheezy), dom0 > kernel and dom0 hypervisor
> Testing with both scenario's was done with the exact same domU so = I
> cant see how it could be a domU issue.

Comparing your guest configs shows that they aren't actual quite<= br> identical though, for reasons other than the different names.

One has apic=3D1 then other doesn't, I'm not sure what the default = is, and
also one names its vif with vifname and the other doesn't.

Perhaps these don't matter but it suggests that you need to double chec= k
your assumption that these VMs are "identical".

Ian.




--bcaec51719c5c1dc6d04c957b556-- --===============8634735010837734042== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users --===============8634735010837734042==-- From xen-users-bounces@lists.xen.org Mon Sep 10 12:01:50 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Mon, 10 Sep 2012 12:01:50 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TB2fo-0003zG-8x; Mon, 10 Sep 2012 12:01:04 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TB2fm-0003yY-20 for xen-users@lists.xensource.com; Mon, 10 Sep 2012 12:01:02 +0000 Received: from [85.158.139.83:27869] by server-10.bemta-5.messagelabs.com id CE/0F-10969-D76DD405; Mon, 10 Sep 2012 12:01:01 +0000 X-Env-Sender: tknchris@gmail.com X-Msg-Ref: server-10.tower-182.messagelabs.com!1347278456!29878746!1 X-Originating-IP: [209.85.223.171] X-SpamReason: No, hits=1.7 required=7.0 tests=BODY_RANDOM_LONG, HTML_10_20, HTML_MESSAGE, ML_RADAR_SPEW_LINKS_14, RCVD_BY_IP, spamassassin: X-StarScan-Received: X-StarScan-Version: 6.6.1.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 8869 invoked from network); 10 Sep 2012 12:00:57 -0000 Received: from mail-ie0-f171.google.com (HELO mail-ie0-f171.google.com) (209.85.223.171) by server-10.tower-182.messagelabs.com with RC4-SHA encrypted SMTP; 10 Sep 2012 12:00:57 -0000 Received: by ieje14 with SMTP id e14so3688493iej.30 for ; Mon, 10 Sep 2012 05:00:55 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=HrDdc1HC/sHowvTWhHW7d9jg3LKxRwv16Jbv9XgpFzM=; b=jaY1JMxTkdZvrnk89XVb2F/9XHnaFLsZ23Pow3PGNVQduh0ZRRFgWmNgDlLzU33sWT zKY642BOQl8yw/mH6E/x3vQWkgJNjjOTAJni+XjcIhc+W9VV0eiMIoEJJVMXlCKUroED tREskmVd/Em4g8O0UcuWN4rogjVFESGtGtTBLAbxBQmc1G5y47UCDUz+/hDXLXisdgR9 F8/d/ERxoboN0qglgA23f9Uq4axfonL+yQZNMz+GPCU9is1qImzFqDZvmuNBRFSvJlDn Af3OfaR7ltITbP/BL6H2wBFxXI9MgeM3DgEPGoOse/PHcUUHFmkNgB6um/kM/L2WaWt3 QMpg== MIME-Version: 1.0 Received: by 10.43.103.193 with SMTP id dj1mr17112903icc.2.1347278455561; Mon, 10 Sep 2012 05:00:55 -0700 (PDT) Received: by 10.64.58.46 with HTTP; Mon, 10 Sep 2012 05:00:55 -0700 (PDT) In-Reply-To: <1347267768.5305.32.camel@zakaz.uk.xensource.com> References: <1346164781.9975.27.camel@zakaz.uk.xensource.com> <1346229699.9975.30.camel@zakaz.uk.xensource.com> <1347267768.5305.32.camel@zakaz.uk.xensource.com> Date: Mon, 10 Sep 2012 08:00:55 -0400 Message-ID: From: chris To: Ian Campbell Cc: Xen-Users List Subject: Re: [Xen-users] pvhvm on debian X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============8634735010837734042==" Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org --===============8634735010837734042== Content-Type: multipart/alternative; boundary=bcaec51719c5c1dc6d04c957b556 --bcaec51719c5c1dc6d04c957b556 Content-Type: text/plain; charset=ISO-8859-1 Ian, You are awesome! I figured it out by looking at console logs. The nonworking domU had this in its console: Detected Xen platform device but not Xen VMM? (sig Microsoft Hv, eax 40000006) xen-platform-pci: probe of 0000:00:03.0 failed with error -22 The mention of hyperv reminded me back when I had to add viridian=1 in order to avoid bluescreens in certain newer versions of windows, and sure enough the nonworking centos domU had viridian=1 After removing/disabling this option the Xen pv drivers come up properly. Just for clarification on the centos side though, in regard to your guest about if I installed any additional standalone PV drivers, the answer is no. The only reason I referred to it as PVHVM was I assumed that maybe pvhvm had become mainline and the kernel centos was using had these features now. Anyway its all working now and its good to know it works in wheezy and I can continue to move towards that in production. Thanks for all your time and help chris On Mon, Sep 10, 2012 at 5:02 AM, Ian Campbell wrote: > On Sun, 2012-09-09 at 21:23 +0100, chris wrote: > > So as you can see the domU is identical kernel in both cases however > > when the domU is running on the wheezy dom0 even despite that the > > platform pci device appears exactly the same in lspci > > Is the contents of the initrd identical in both cases? Specifically do > they both contain the same set of kernel modules? > > Note that CentOS does not strictly speaking contain "PVHVM", which is a > more recent upstream development. What you have here is the PV drivers > add on driver from the unmodified_drivers. Did these drivers ship with > CentOS or did you get them from elsewhere? Do you have the source for > them? > > The difference is that PVHVM is part of the kernel itself and are > tightly integrated, while the unmodified_drivers are a set of drivers > used as an "add-on" pack for various existing OSes (similar in principal > to how e.g. the Windows drivers are supplied for Windows). The main > differences in practice will be at setup and initialisation time, which > of course is where things appear to be going wrong for you. > > I think this highlights why it is important to always give all the > precise details in a bug report, this is the first time CentOS has been > mentioned at all so I think I can be forgiven for assuming you were > running Debian PVHVM in the guest too (which is what I spent time > reproducing). > > > I've attached the configs and logs that you asked for > > I asked for guest console logs. The guest console logs are where the > guest decisions about PVHVM drivers will be logged, if anywhere. > > sektor-qemu.txt and baraka-qemu.txt are identical, but they both contain > references to "baraka" which should surely be "sektor" in the at least > one place (e.g. the disk path) for that VM. > > Your vm configs show the name has changed in the disk path so I don't > see why it isn't different in the logs too. re you sure these are the > actual logs from real runs of the guest? > > > Any ideas how to debug further? The difference between the working > > scenario and nonworking is the dom0 distro (squeeze vs wheezy), dom0 > > kernel and dom0 hypervisor > > Testing with both scenario's was done with the exact same domU so I > > cant see how it could be a domU issue. > > Comparing your guest configs shows that they aren't actual quite > identical though, for reasons other than the different names. > > One has apic=1 then other doesn't, I'm not sure what the default is, and > also one names its vif with vifname and the other doesn't. > > Perhaps these don't matter but it suggests that you need to double check > your assumption that these VMs are "identical". > > Ian. > > > > --bcaec51719c5c1dc6d04c957b556 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Ian,=A0

You are awesome! I figured it out by looking at = console logs. The nonworking domU had this in its console:

Detected Xen platform device but not Xen VMM? (sig Microsoft = Hv, eax 40000006)
xen-platform-pci: probe of 0000:00:03.0 failed with error -22

The mention of hyperv reminded me back when I had to= add viridian=3D1 in order to avoid bluescreens in certain newer versions o= f windows, and sure enough the nonworking centos domU had viridian=3D1
After removing/disabling this option the Xen pv drivers come up proper= ly.

Just for clarification on the centos side thou= gh, in regard to your guest about if I installed any additional standalone = PV drivers, the answer is no. The only reason I referred to it as PVHVM was= I assumed that maybe pvhvm had become mainline and the kernel centos was u= sing had these features now.=A0

Anyway its all working now and its good to know it work= s in wheezy and I can continue to move towards that in production.

Thanks for all your time and help
chris

On Mon, Sep 10, 2012 at 5:02 AM, Ian Ca= mpbell <Ian.Campbell@citrix.com> wrote:
On Sun, 2012-09-09 at 21:23 +0100, chris wrote:
> So as you can see the domU is identical kernel in both cases however > when the domU is running on the wheezy dom0 even despite that the
> platform pci device appears exactly the same in lspci

Is the contents of the initrd identical in both cases? Specifically d= o
they both contain the same set of kernel modules?

Note that CentOS does not strictly speaking contain "PVHVM", whic= h is a
more recent upstream development. What you have here is the PV drivers
add on driver from the unmodified_drivers. Did these drivers ship with
CentOS or did you get them from elsewhere? Do you have the source for
them?

The difference is that PVHVM is part of the kernel itself and are
tightly integrated, while the unmodified_drivers are a set of drivers
used as an "add-on" pack for various existing OSes (similar in pr= incipal
to how e.g. the Windows drivers are supplied for Windows). The main
differences in practice will be at setup and initialisation time, which
of course is where things appear to be going wrong for you.

I think this highlights why it is important to always give all the
precise details in a bug report, this is the first time CentOS has been
mentioned at all so I think I can be forgiven for assuming you were
running Debian PVHVM in the guest too (which is what I spent time
reproducing).

> I've attached the configs and logs that you asked for

I asked for guest console logs. The guest console logs are where the<= br> guest decisions about PVHVM drivers will be logged, if anywhere.

sektor-qemu.txt and baraka-qemu.txt are identical, but they both contain references to "baraka" which should surely be "sektor" = in the at least
one place (e.g. the disk path) for that VM.

Your vm configs show the name has changed in the disk path so I don't see why it isn't different in the logs too. re you sure these are the actual logs from real runs of the guest?

> Any ideas how to debug further? The difference between the working
> scenario and nonworking is the dom0 distro (squeeze vs wheezy), dom0 > kernel and dom0 hypervisor
> Testing with both scenario's was done with the exact same domU so = I
> cant see how it could be a domU issue.

Comparing your guest configs shows that they aren't actual quite<= br> identical though, for reasons other than the different names.

One has apic=3D1 then other doesn't, I'm not sure what the default = is, and
also one names its vif with vifname and the other doesn't.

Perhaps these don't matter but it suggests that you need to double chec= k
your assumption that these VMs are "identical".

Ian.




--bcaec51719c5c1dc6d04c957b556-- --===============8634735010837734042== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users --===============8634735010837734042==-- From xen-users-bounces@lists.xen.org Mon Sep 10 12:08:18 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Mon, 10 Sep 2012 12:08:18 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TB2ly-0004lJ-Pz; Mon, 10 Sep 2012 12:07:26 +0000 Received: from mail27.messagelabs.com ([193.109.254.147]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TB2lx-0004ks-P9 for xen-users@lists.xen.org; Mon, 10 Sep 2012 12:07:25 +0000 X-Env-Sender: shoban.preeth@gmail.com X-Msg-Ref: server-11.tower-27.messagelabs.com!1347278764!3414461!1 X-Originating-IP: [209.85.215.45] X-SpamReason: No, hits=0.3 required=7.0 tests=ML_RADAR_SPEW_LINKS_14, RCVD_BY_IP,spamassassin: X-StarScan-Received: X-StarScan-Version: 6.6.1.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 26427 invoked from network); 10 Sep 2012 12:06:05 -0000 Received: from mail-lpp01m010-f45.google.com (HELO mail-lpp01m010-f45.google.com) (209.85.215.45) by server-11.tower-27.messagelabs.com with RC4-SHA encrypted SMTP; 10 Sep 2012 12:06:05 -0000 Received: by lagz14 with SMTP id z14so1318637lag.32 for ; Mon, 10 Sep 2012 05:06:04 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:date:message-id:subject:from:to:content-type; bh=GsqjyWTkglkNAgWalN+vcNOGIrjFZXRm6FhpW2HQgF8=; b=HfLJ+e8dn35JYYskek9//RLBY7C8oWyzzOkW9oSd4y2RVz9mKIcAEMDh58mwmtejrb T6CVj4hcNyng5gZhQwIgA72kRFI8XwYeiFptLfSzV+/+AzLb6ix4JArdZ48p85Mv4ReV Ml42S8Vn1wQ990a4GGcKQaCc8IkZUBmS0+ljnUCcO9mRAz1xOJ8GD4lks2kpnEtS/4s8 mE0V+piLYS+3haqWSFFmpJgBxx2nmCuFR7W/Zult2RQULSKEGaQwnEoBI6dT7z8r8sNt NSOqaKhDBTF4o98onCY5CxBKGUqjZK7oTWGEzRhaoIvCMRzcv2R/hfiTat4CBxDuIHPM I0Jw== MIME-Version: 1.0 Received: by 10.152.124.18 with SMTP id me18mr4874871lab.6.1347278764106; Mon, 10 Sep 2012 05:06:04 -0700 (PDT) Received: by 10.152.8.15 with HTTP; Mon, 10 Sep 2012 05:06:04 -0700 (PDT) Date: Mon, 10 Sep 2012 17:36:04 +0530 Message-ID: From: Shoban To: xen-users@lists.xen.org Subject: [Xen-users] Issue with domU RX throughput X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org Hi, I am encountering a weird issue, where domU RX throughput (of traffic from another machine) is very low. But domU RX throughput from dom0 is fine, and dom0 RX from another machine is fine. iperf reported the following throughputs: dom0 <- outside -- 942Mbps domU <- dom0 -- 3467Mbps domU <- outside -- 87Mbps The NIC on the machine is 1GE. What puzzles me is, some instances of domU (with same config) is able to achieve almost 1Gbps RX throughput. And this seem to be very random. I am running Debian stable (Squeeze) with standard Xen packages, and standard network setup with linux bridging module. NIC is Broadcomm BCM5764M GE. Please let me know, if more information on configuration/tests is required. Thanks, Shoban _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Mon Sep 10 12:08:18 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Mon, 10 Sep 2012 12:08:18 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TB2ly-0004lJ-Pz; Mon, 10 Sep 2012 12:07:26 +0000 Received: from mail27.messagelabs.com ([193.109.254.147]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TB2lx-0004ks-P9 for xen-users@lists.xen.org; Mon, 10 Sep 2012 12:07:25 +0000 X-Env-Sender: shoban.preeth@gmail.com X-Msg-Ref: server-11.tower-27.messagelabs.com!1347278764!3414461!1 X-Originating-IP: [209.85.215.45] X-SpamReason: No, hits=0.3 required=7.0 tests=ML_RADAR_SPEW_LINKS_14, RCVD_BY_IP,spamassassin: X-StarScan-Received: X-StarScan-Version: 6.6.1.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 26427 invoked from network); 10 Sep 2012 12:06:05 -0000 Received: from mail-lpp01m010-f45.google.com (HELO mail-lpp01m010-f45.google.com) (209.85.215.45) by server-11.tower-27.messagelabs.com with RC4-SHA encrypted SMTP; 10 Sep 2012 12:06:05 -0000 Received: by lagz14 with SMTP id z14so1318637lag.32 for ; Mon, 10 Sep 2012 05:06:04 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:date:message-id:subject:from:to:content-type; bh=GsqjyWTkglkNAgWalN+vcNOGIrjFZXRm6FhpW2HQgF8=; b=HfLJ+e8dn35JYYskek9//RLBY7C8oWyzzOkW9oSd4y2RVz9mKIcAEMDh58mwmtejrb T6CVj4hcNyng5gZhQwIgA72kRFI8XwYeiFptLfSzV+/+AzLb6ix4JArdZ48p85Mv4ReV Ml42S8Vn1wQ990a4GGcKQaCc8IkZUBmS0+ljnUCcO9mRAz1xOJ8GD4lks2kpnEtS/4s8 mE0V+piLYS+3haqWSFFmpJgBxx2nmCuFR7W/Zult2RQULSKEGaQwnEoBI6dT7z8r8sNt NSOqaKhDBTF4o98onCY5CxBKGUqjZK7oTWGEzRhaoIvCMRzcv2R/hfiTat4CBxDuIHPM I0Jw== MIME-Version: 1.0 Received: by 10.152.124.18 with SMTP id me18mr4874871lab.6.1347278764106; Mon, 10 Sep 2012 05:06:04 -0700 (PDT) Received: by 10.152.8.15 with HTTP; Mon, 10 Sep 2012 05:06:04 -0700 (PDT) Date: Mon, 10 Sep 2012 17:36:04 +0530 Message-ID: From: Shoban To: xen-users@lists.xen.org Subject: [Xen-users] Issue with domU RX throughput X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org Hi, I am encountering a weird issue, where domU RX throughput (of traffic from another machine) is very low. But domU RX throughput from dom0 is fine, and dom0 RX from another machine is fine. iperf reported the following throughputs: dom0 <- outside -- 942Mbps domU <- dom0 -- 3467Mbps domU <- outside -- 87Mbps The NIC on the machine is 1GE. What puzzles me is, some instances of domU (with same config) is able to achieve almost 1Gbps RX throughput. And this seem to be very random. I am running Debian stable (Squeeze) with standard Xen packages, and standard network setup with linux bridging module. NIC is Broadcomm BCM5764M GE. Please let me know, if more information on configuration/tests is required. Thanks, Shoban _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Mon Sep 10 12:14:37 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Mon, 10 Sep 2012 12:14:37 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TB2s9-0005BR-Sp; Mon, 10 Sep 2012 12:13:49 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TB2s8-0005BM-6g for xen-users@lists.xensource.com; Mon, 10 Sep 2012 12:13:48 +0000 Received: from [85.158.143.99:29332] by server-2.bemta-4.messagelabs.com id 7B/56-21239-B79DD405; Mon, 10 Sep 2012 12:13:47 +0000 X-Env-Sender: tknchris@gmail.com X-Msg-Ref: server-13.tower-216.messagelabs.com!1347279224!28615844!1 X-Originating-IP: [209.85.210.171] X-SpamReason: No, hits=1.7 required=7.0 tests=BODY_RANDOM_LONG, HTML_20_30, HTML_MESSAGE, ML_RADAR_SPEW_LINKS_14, RCVD_BY_IP, spamassassin: X-StarScan-Received: X-StarScan-Version: 6.6.1.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 25709 invoked from network); 10 Sep 2012 12:13:45 -0000 Received: from mail-iy0-f171.google.com (HELO mail-iy0-f171.google.com) (209.85.210.171) by server-13.tower-216.messagelabs.com with RC4-SHA encrypted SMTP; 10 Sep 2012 12:13:45 -0000 Received: by iabz25 with SMTP id z25so2146577iab.30 for ; Mon, 10 Sep 2012 05:13:44 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=qw8T4LSSghWZLeu5wY15I6g4/pGcrkGU3zbuPGs7EL4=; b=kkvPNYvaWiqu8uiV+ouaa23eOEnWBBH8zbMLKOBJjf31OrF0n1TWVl2rAiAkQyUryx w6echoeA9HweIbuaRyda0+m7FPRbDawDfU9dKEnPG2NDnupzayCPQqx/wK88mf2Vfk4g vbN8JCTPh2o74jHXuxYlb0ruYWP+Q1pV/AO8YOnQ4v4dAEclatmDJJ5yF+GsA40r3/YU fU7wjL/0sbtvKHNbFgaSZNgfPlNEPGazctE750ecYNw4Q5oWcWNURXNYJPxDRpejwd3E b5hylCRTIJ2BfzifCfV9n9h1BEr0eAHLgFHIS15TmVAyvjsJibb5KcyARvjuhvpVBaPn Qwmw== MIME-Version: 1.0 Received: by 10.50.53.199 with SMTP id d7mr10743528igp.55.1347279224117; Mon, 10 Sep 2012 05:13:44 -0700 (PDT) Received: by 10.64.58.46 with HTTP; Mon, 10 Sep 2012 05:13:44 -0700 (PDT) In-Reply-To: References: <1346164781.9975.27.camel@zakaz.uk.xensource.com> <1346229699.9975.30.camel@zakaz.uk.xensource.com> <1347267768.5305.32.camel@zakaz.uk.xensource.com> Date: Mon, 10 Sep 2012 08:13:44 -0400 Message-ID: From: chris To: Ian Campbell Cc: Xen-Users List Subject: Re: [Xen-users] pvhvm on debian X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============7875597278416629350==" Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org --===============7875597278416629350== Content-Type: multipart/alternative; boundary=f46d04339c4c91191f04c957e3bf --f46d04339c4c91191f04c957e3bf Content-Type: text/plain; charset=ISO-8859-1 So I found the drivers, are you saying these are not pvhvm drivers? # find /lib/modules/2.6.18-194.3.1.el5/ | grep xen /lib/modules/2.6.18-194.3.1.el5/kernel/drivers/net/netxen /lib/modules/2.6.18-194.3.1.el5/kernel/drivers/net/netxen/netxen_nic.ko /lib/modules/2.6.18-194.3.1.el5/kernel/drivers/xenpv_hvm /lib/modules/2.6.18-194.3.1.el5/kernel/drivers/xenpv_hvm/platform-pci /lib/modules/2.6.18-194.3.1.el5/kernel/drivers/xenpv_hvm/platform-pci/xen-platform-pci.ko /lib/modules/2.6.18-194.3.1.el5/kernel/drivers/xenpv_hvm/netfront /lib/modules/2.6.18-194.3.1.el5/kernel/drivers/xenpv_hvm/netfront/xen-vnif.ko /lib/modules/2.6.18-194.3.1.el5/kernel/drivers/xenpv_hvm/blkfront /lib/modules/2.6.18-194.3.1.el5/kernel/drivers/xenpv_hvm/blkfront/xen-vbd.ko /lib/modules/2.6.18-194.3.1.el5/kernel/drivers/xenpv_hvm/balloon /lib/modules/2.6.18-194.3.1.el5/kernel/drivers/xenpv_hvm/balloon/xen-balloon.ko I can't find any packages that look like a seperate package for the drivers only, I have a feeling its integrated with the kernel package [root@baraka ~]# rpm -qa | grep -i xen [root@baraka ~]# rpm -qa | grep -i pv iptables-ipv6-1.3.5-5.3.el5_4.1 [root@baraka ~]# rpm -qa | grep -i hvm Any idea how can I track down which drivers it is being used? chris On Mon, Sep 10, 2012 at 8:00 AM, chris wrote: > Ian, > > You are awesome! I figured it out by looking at console logs. The > nonworking domU had this in its console: > > Detected Xen platform device but not Xen VMM? (sig Microsoft Hv, eax > 40000006) > xen-platform-pci: probe of 0000:00:03.0 failed with error -22 > > The mention of hyperv reminded me back when I had to add viridian=1 in > order to avoid bluescreens in certain newer versions of windows, and sure > enough the nonworking centos domU had viridian=1 > After removing/disabling this option the Xen pv drivers come up properly. > > Just for clarification on the centos side though, in regard to your guest > about if I installed any additional standalone PV drivers, the answer is > no. The only reason I referred to it as PVHVM was I assumed that maybe > pvhvm had become mainline and the kernel centos was using had these > features now. > > Anyway its all working now and its good to know it works in wheezy and I > can continue to move towards that in production. > > Thanks for all your time and help > chris > > On Mon, Sep 10, 2012 at 5:02 AM, Ian Campbell wrote: > >> On Sun, 2012-09-09 at 21:23 +0100, chris wrote: >> > So as you can see the domU is identical kernel in both cases however >> > when the domU is running on the wheezy dom0 even despite that the >> > platform pci device appears exactly the same in lspci >> >> Is the contents of the initrd identical in both cases? Specifically do >> they both contain the same set of kernel modules? >> >> Note that CentOS does not strictly speaking contain "PVHVM", which is a >> more recent upstream development. What you have here is the PV drivers >> add on driver from the unmodified_drivers. Did these drivers ship with >> CentOS or did you get them from elsewhere? Do you have the source for >> them? >> >> The difference is that PVHVM is part of the kernel itself and are >> tightly integrated, while the unmodified_drivers are a set of drivers >> used as an "add-on" pack for various existing OSes (similar in principal >> to how e.g. the Windows drivers are supplied for Windows). The main >> differences in practice will be at setup and initialisation time, which >> of course is where things appear to be going wrong for you. >> >> I think this highlights why it is important to always give all the >> precise details in a bug report, this is the first time CentOS has been >> mentioned at all so I think I can be forgiven for assuming you were >> running Debian PVHVM in the guest too (which is what I spent time >> reproducing). >> >> > I've attached the configs and logs that you asked for >> >> I asked for guest console logs. The guest console logs are where the >> guest decisions about PVHVM drivers will be logged, if anywhere. >> >> sektor-qemu.txt and baraka-qemu.txt are identical, but they both contain >> references to "baraka" which should surely be "sektor" in the at least >> one place (e.g. the disk path) for that VM. >> >> Your vm configs show the name has changed in the disk path so I don't >> see why it isn't different in the logs too. re you sure these are the >> actual logs from real runs of the guest? >> >> > Any ideas how to debug further? The difference between the working >> > scenario and nonworking is the dom0 distro (squeeze vs wheezy), dom0 >> > kernel and dom0 hypervisor >> > Testing with both scenario's was done with the exact same domU so I >> > cant see how it could be a domU issue. >> >> Comparing your guest configs shows that they aren't actual quite >> identical though, for reasons other than the different names. >> >> One has apic=1 then other doesn't, I'm not sure what the default is, and >> also one names its vif with vifname and the other doesn't. >> >> Perhaps these don't matter but it suggests that you need to double check >> your assumption that these VMs are "identical". >> >> Ian. >> >> >> >> > --f46d04339c4c91191f04c957e3bf Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable
So I found the drivers, are you saying these are not pvhvm drivers?

# find /lib/modules/2.6.18-194.3.1.el5/ | grep xen
/lib/modules/2.6.18-194.3.1.el5/kernel/drivers/net/netxen
/lib/modules/2.6.18-194.3.1.el5/kernel/drivers/net/netxen/netxen_nic.k= o
/lib/modules/2.6.18-194.3.1.el5/kernel/drivers/xenpv_hvm
<= div>/lib/modules/2.6.18-194.3.1.el5/kernel/drivers/xenpv_hvm/platform-pci
/lib/modules/2.6.18-194.3.1.el5/kernel/drivers/xenpv_hvm/platform-pci/= xen-platform-pci.ko
/lib/modules/2.6.18-194.3.1.el5/kernel/driver= s/xenpv_hvm/netfront
/lib/modules/2.6.18-194.3.1.el5/kernel/drive= rs/xenpv_hvm/netfront/xen-vnif.ko
/lib/modules/2.6.18-194.3.1.el5/kernel/drivers/xenpv_hvm/blkfront
/lib/modules/2.6.18-194.3.1.el5/kernel/drivers/xenpv_hvm/blkfront/xen= -vbd.ko
/lib/modules/2.6.18-194.3.1.el5/kernel/drivers/xenpv_hvm/= balloon
/lib/modules/2.6.18-194.3.1.el5/kernel/drivers/xenpv_hvm/balloon/xen-b= alloon.ko

I can't find any packages that look = like a seperate package for the drivers only, I have a feeling its integrat= ed with the kernel package
[root@baraka ~]# rpm -qa | grep -i xen
[root@baraka ~]#= rpm -qa | grep -i pv
iptables-ipv6-1.3.5-5.3.el5_4.1
[= root@baraka ~]# rpm -qa | grep -i hvm

Any id= ea how can I track down which drivers it is being used?

chris

On Mon, Sep 1= 0, 2012 at 8:00 AM, chris <tknchris@gmail.com> wrote:
Ian,=A0

You are awesome! I figured it out by looking at = console logs. The nonworking domU had this in its console:

Detected Xen platform device but not Xen VMM? (sig Microsoft = Hv, eax 40000006)
xen-platform-pci: probe of 0000:00:03.0 failed with error -22

The mention of hyperv reminded me back when I had to= add viridian=3D1 in order to avoid bluescreens in certain newer versions o= f windows, and sure enough the nonworking centos domU had viridian=3D1
After removing/disabling this option the Xen pv drivers come up proper= ly.

Just for clarification on the centos side thou= gh, in regard to your guest about if I installed any additional standalone = PV drivers, the answer is no. The only reason I referred to it as PVHVM was= I assumed that maybe pvhvm had become mainline and the kernel centos was u= sing had these features now.=A0

Anyway its all working now and its good to know it work= s in wheezy and I can continue to move towards that in production.

Thanks for all your time and help
chris

On Mon, Sep 10, 2012 at 5:02 AM, Ian Ca= mpbell <Ian.Campbell@citrix.com> wrote:
On Sun, 2012-09-09 at 21:23 +0100, chris wrote:
> So as you can see the domU is identical kernel in both cases however > when the domU is running on the wheezy dom0 even despite that the
> platform pci device appears exactly the same in lspci

Is the contents of the initrd identical in both cases? Specifically d= o
they both contain the same set of kernel modules?

Note that CentOS does not strictly speaking contain "PVHVM", whic= h is a
more recent upstream development. What you have here is the PV drivers
add on driver from the unmodified_drivers. Did these drivers ship with
CentOS or did you get them from elsewhere? Do you have the source for
them?

The difference is that PVHVM is part of the kernel itself and are
tightly integrated, while the unmodified_drivers are a set of drivers
used as an "add-on" pack for various existing OSes (similar in pr= incipal
to how e.g. the Windows drivers are supplied for Windows). The main
differences in practice will be at setup and initialisation time, which
of course is where things appear to be going wrong for you.

I think this highlights why it is important to always give all the
precise details in a bug report, this is the first time CentOS has been
mentioned at all so I think I can be forgiven for assuming you were
running Debian PVHVM in the guest too (which is what I spent time
reproducing).

> I've attached the configs and logs that you asked for

I asked for guest console logs. The guest console logs are where the<= br> guest decisions about PVHVM drivers will be logged, if anywhere.

sektor-qemu.txt and baraka-qemu.txt are identical, but they both contain references to "baraka" which should surely be "sektor" = in the at least
one place (e.g. the disk path) for that VM.

Your vm configs show the name has changed in the disk path so I don't see why it isn't different in the logs too. re you sure these are the actual logs from real runs of the guest?

> Any ideas how to debug further? The difference between the working
> scenario and nonworking is the dom0 distro (squeeze vs wheezy), dom0 > kernel and dom0 hypervisor
> Testing with both scenario's was done with the exact same domU so = I
> cant see how it could be a domU issue.

Comparing your guest configs shows that they aren't actual quite<= br> identical though, for reasons other than the different names.

One has apic=3D1 then other doesn't, I'm not sure what the default = is, and
also one names its vif with vifname and the other doesn't.

Perhaps these don't matter but it suggests that you need to double chec= k
your assumption that these VMs are "identical".

Ian.





--f46d04339c4c91191f04c957e3bf-- --===============7875597278416629350== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users --===============7875597278416629350==-- From xen-users-bounces@lists.xen.org Mon Sep 10 12:14:37 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Mon, 10 Sep 2012 12:14:37 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TB2s9-0005BR-Sp; Mon, 10 Sep 2012 12:13:49 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TB2s8-0005BM-6g for xen-users@lists.xensource.com; Mon, 10 Sep 2012 12:13:48 +0000 Received: from [85.158.143.99:29332] by server-2.bemta-4.messagelabs.com id 7B/56-21239-B79DD405; Mon, 10 Sep 2012 12:13:47 +0000 X-Env-Sender: tknchris@gmail.com X-Msg-Ref: server-13.tower-216.messagelabs.com!1347279224!28615844!1 X-Originating-IP: [209.85.210.171] X-SpamReason: No, hits=1.7 required=7.0 tests=BODY_RANDOM_LONG, HTML_20_30, HTML_MESSAGE, ML_RADAR_SPEW_LINKS_14, RCVD_BY_IP, spamassassin: X-StarScan-Received: X-StarScan-Version: 6.6.1.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 25709 invoked from network); 10 Sep 2012 12:13:45 -0000 Received: from mail-iy0-f171.google.com (HELO mail-iy0-f171.google.com) (209.85.210.171) by server-13.tower-216.messagelabs.com with RC4-SHA encrypted SMTP; 10 Sep 2012 12:13:45 -0000 Received: by iabz25 with SMTP id z25so2146577iab.30 for ; Mon, 10 Sep 2012 05:13:44 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=qw8T4LSSghWZLeu5wY15I6g4/pGcrkGU3zbuPGs7EL4=; b=kkvPNYvaWiqu8uiV+ouaa23eOEnWBBH8zbMLKOBJjf31OrF0n1TWVl2rAiAkQyUryx w6echoeA9HweIbuaRyda0+m7FPRbDawDfU9dKEnPG2NDnupzayCPQqx/wK88mf2Vfk4g vbN8JCTPh2o74jHXuxYlb0ruYWP+Q1pV/AO8YOnQ4v4dAEclatmDJJ5yF+GsA40r3/YU fU7wjL/0sbtvKHNbFgaSZNgfPlNEPGazctE750ecYNw4Q5oWcWNURXNYJPxDRpejwd3E b5hylCRTIJ2BfzifCfV9n9h1BEr0eAHLgFHIS15TmVAyvjsJibb5KcyARvjuhvpVBaPn Qwmw== MIME-Version: 1.0 Received: by 10.50.53.199 with SMTP id d7mr10743528igp.55.1347279224117; Mon, 10 Sep 2012 05:13:44 -0700 (PDT) Received: by 10.64.58.46 with HTTP; Mon, 10 Sep 2012 05:13:44 -0700 (PDT) In-Reply-To: References: <1346164781.9975.27.camel@zakaz.uk.xensource.com> <1346229699.9975.30.camel@zakaz.uk.xensource.com> <1347267768.5305.32.camel@zakaz.uk.xensource.com> Date: Mon, 10 Sep 2012 08:13:44 -0400 Message-ID: From: chris To: Ian Campbell Cc: Xen-Users List Subject: Re: [Xen-users] pvhvm on debian X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============7875597278416629350==" Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org --===============7875597278416629350== Content-Type: multipart/alternative; boundary=f46d04339c4c91191f04c957e3bf --f46d04339c4c91191f04c957e3bf Content-Type: text/plain; charset=ISO-8859-1 So I found the drivers, are you saying these are not pvhvm drivers? # find /lib/modules/2.6.18-194.3.1.el5/ | grep xen /lib/modules/2.6.18-194.3.1.el5/kernel/drivers/net/netxen /lib/modules/2.6.18-194.3.1.el5/kernel/drivers/net/netxen/netxen_nic.ko /lib/modules/2.6.18-194.3.1.el5/kernel/drivers/xenpv_hvm /lib/modules/2.6.18-194.3.1.el5/kernel/drivers/xenpv_hvm/platform-pci /lib/modules/2.6.18-194.3.1.el5/kernel/drivers/xenpv_hvm/platform-pci/xen-platform-pci.ko /lib/modules/2.6.18-194.3.1.el5/kernel/drivers/xenpv_hvm/netfront /lib/modules/2.6.18-194.3.1.el5/kernel/drivers/xenpv_hvm/netfront/xen-vnif.ko /lib/modules/2.6.18-194.3.1.el5/kernel/drivers/xenpv_hvm/blkfront /lib/modules/2.6.18-194.3.1.el5/kernel/drivers/xenpv_hvm/blkfront/xen-vbd.ko /lib/modules/2.6.18-194.3.1.el5/kernel/drivers/xenpv_hvm/balloon /lib/modules/2.6.18-194.3.1.el5/kernel/drivers/xenpv_hvm/balloon/xen-balloon.ko I can't find any packages that look like a seperate package for the drivers only, I have a feeling its integrated with the kernel package [root@baraka ~]# rpm -qa | grep -i xen [root@baraka ~]# rpm -qa | grep -i pv iptables-ipv6-1.3.5-5.3.el5_4.1 [root@baraka ~]# rpm -qa | grep -i hvm Any idea how can I track down which drivers it is being used? chris On Mon, Sep 10, 2012 at 8:00 AM, chris wrote: > Ian, > > You are awesome! I figured it out by looking at console logs. The > nonworking domU had this in its console: > > Detected Xen platform device but not Xen VMM? (sig Microsoft Hv, eax > 40000006) > xen-platform-pci: probe of 0000:00:03.0 failed with error -22 > > The mention of hyperv reminded me back when I had to add viridian=1 in > order to avoid bluescreens in certain newer versions of windows, and sure > enough the nonworking centos domU had viridian=1 > After removing/disabling this option the Xen pv drivers come up properly. > > Just for clarification on the centos side though, in regard to your guest > about if I installed any additional standalone PV drivers, the answer is > no. The only reason I referred to it as PVHVM was I assumed that maybe > pvhvm had become mainline and the kernel centos was using had these > features now. > > Anyway its all working now and its good to know it works in wheezy and I > can continue to move towards that in production. > > Thanks for all your time and help > chris > > On Mon, Sep 10, 2012 at 5:02 AM, Ian Campbell wrote: > >> On Sun, 2012-09-09 at 21:23 +0100, chris wrote: >> > So as you can see the domU is identical kernel in both cases however >> > when the domU is running on the wheezy dom0 even despite that the >> > platform pci device appears exactly the same in lspci >> >> Is the contents of the initrd identical in both cases? Specifically do >> they both contain the same set of kernel modules? >> >> Note that CentOS does not strictly speaking contain "PVHVM", which is a >> more recent upstream development. What you have here is the PV drivers >> add on driver from the unmodified_drivers. Did these drivers ship with >> CentOS or did you get them from elsewhere? Do you have the source for >> them? >> >> The difference is that PVHVM is part of the kernel itself and are >> tightly integrated, while the unmodified_drivers are a set of drivers >> used as an "add-on" pack for various existing OSes (similar in principal >> to how e.g. the Windows drivers are supplied for Windows). The main >> differences in practice will be at setup and initialisation time, which >> of course is where things appear to be going wrong for you. >> >> I think this highlights why it is important to always give all the >> precise details in a bug report, this is the first time CentOS has been >> mentioned at all so I think I can be forgiven for assuming you were >> running Debian PVHVM in the guest too (which is what I spent time >> reproducing). >> >> > I've attached the configs and logs that you asked for >> >> I asked for guest console logs. The guest console logs are where the >> guest decisions about PVHVM drivers will be logged, if anywhere. >> >> sektor-qemu.txt and baraka-qemu.txt are identical, but they both contain >> references to "baraka" which should surely be "sektor" in the at least >> one place (e.g. the disk path) for that VM. >> >> Your vm configs show the name has changed in the disk path so I don't >> see why it isn't different in the logs too. re you sure these are the >> actual logs from real runs of the guest? >> >> > Any ideas how to debug further? The difference between the working >> > scenario and nonworking is the dom0 distro (squeeze vs wheezy), dom0 >> > kernel and dom0 hypervisor >> > Testing with both scenario's was done with the exact same domU so I >> > cant see how it could be a domU issue. >> >> Comparing your guest configs shows that they aren't actual quite >> identical though, for reasons other than the different names. >> >> One has apic=1 then other doesn't, I'm not sure what the default is, and >> also one names its vif with vifname and the other doesn't. >> >> Perhaps these don't matter but it suggests that you need to double check >> your assumption that these VMs are "identical". >> >> Ian. >> >> >> >> > --f46d04339c4c91191f04c957e3bf Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable
So I found the drivers, are you saying these are not pvhvm drivers?

# find /lib/modules/2.6.18-194.3.1.el5/ | grep xen
/lib/modules/2.6.18-194.3.1.el5/kernel/drivers/net/netxen
/lib/modules/2.6.18-194.3.1.el5/kernel/drivers/net/netxen/netxen_nic.k= o
/lib/modules/2.6.18-194.3.1.el5/kernel/drivers/xenpv_hvm
<= div>/lib/modules/2.6.18-194.3.1.el5/kernel/drivers/xenpv_hvm/platform-pci
/lib/modules/2.6.18-194.3.1.el5/kernel/drivers/xenpv_hvm/platform-pci/= xen-platform-pci.ko
/lib/modules/2.6.18-194.3.1.el5/kernel/driver= s/xenpv_hvm/netfront
/lib/modules/2.6.18-194.3.1.el5/kernel/drive= rs/xenpv_hvm/netfront/xen-vnif.ko
/lib/modules/2.6.18-194.3.1.el5/kernel/drivers/xenpv_hvm/blkfront
/lib/modules/2.6.18-194.3.1.el5/kernel/drivers/xenpv_hvm/blkfront/xen= -vbd.ko
/lib/modules/2.6.18-194.3.1.el5/kernel/drivers/xenpv_hvm/= balloon
/lib/modules/2.6.18-194.3.1.el5/kernel/drivers/xenpv_hvm/balloon/xen-b= alloon.ko

I can't find any packages that look = like a seperate package for the drivers only, I have a feeling its integrat= ed with the kernel package
[root@baraka ~]# rpm -qa | grep -i xen
[root@baraka ~]#= rpm -qa | grep -i pv
iptables-ipv6-1.3.5-5.3.el5_4.1
[= root@baraka ~]# rpm -qa | grep -i hvm

Any id= ea how can I track down which drivers it is being used?

chris

On Mon, Sep 1= 0, 2012 at 8:00 AM, chris <tknchris@gmail.com> wrote:
Ian,=A0

You are awesome! I figured it out by looking at = console logs. The nonworking domU had this in its console:

Detected Xen platform device but not Xen VMM? (sig Microsoft = Hv, eax 40000006)
xen-platform-pci: probe of 0000:00:03.0 failed with error -22

The mention of hyperv reminded me back when I had to= add viridian=3D1 in order to avoid bluescreens in certain newer versions o= f windows, and sure enough the nonworking centos domU had viridian=3D1
After removing/disabling this option the Xen pv drivers come up proper= ly.

Just for clarification on the centos side thou= gh, in regard to your guest about if I installed any additional standalone = PV drivers, the answer is no. The only reason I referred to it as PVHVM was= I assumed that maybe pvhvm had become mainline and the kernel centos was u= sing had these features now.=A0

Anyway its all working now and its good to know it work= s in wheezy and I can continue to move towards that in production.

Thanks for all your time and help
chris

On Mon, Sep 10, 2012 at 5:02 AM, Ian Ca= mpbell <Ian.Campbell@citrix.com> wrote:
On Sun, 2012-09-09 at 21:23 +0100, chris wrote:
> So as you can see the domU is identical kernel in both cases however > when the domU is running on the wheezy dom0 even despite that the
> platform pci device appears exactly the same in lspci

Is the contents of the initrd identical in both cases? Specifically d= o
they both contain the same set of kernel modules?

Note that CentOS does not strictly speaking contain "PVHVM", whic= h is a
more recent upstream development. What you have here is the PV drivers
add on driver from the unmodified_drivers. Did these drivers ship with
CentOS or did you get them from elsewhere? Do you have the source for
them?

The difference is that PVHVM is part of the kernel itself and are
tightly integrated, while the unmodified_drivers are a set of drivers
used as an "add-on" pack for various existing OSes (similar in pr= incipal
to how e.g. the Windows drivers are supplied for Windows). The main
differences in practice will be at setup and initialisation time, which
of course is where things appear to be going wrong for you.

I think this highlights why it is important to always give all the
precise details in a bug report, this is the first time CentOS has been
mentioned at all so I think I can be forgiven for assuming you were
running Debian PVHVM in the guest too (which is what I spent time
reproducing).

> I've attached the configs and logs that you asked for

I asked for guest console logs. The guest console logs are where the<= br> guest decisions about PVHVM drivers will be logged, if anywhere.

sektor-qemu.txt and baraka-qemu.txt are identical, but they both contain references to "baraka" which should surely be "sektor" = in the at least
one place (e.g. the disk path) for that VM.

Your vm configs show the name has changed in the disk path so I don't see why it isn't different in the logs too. re you sure these are the actual logs from real runs of the guest?

> Any ideas how to debug further? The difference between the working
> scenario and nonworking is the dom0 distro (squeeze vs wheezy), dom0 > kernel and dom0 hypervisor
> Testing with both scenario's was done with the exact same domU so = I
> cant see how it could be a domU issue.

Comparing your guest configs shows that they aren't actual quite<= br> identical though, for reasons other than the different names.

One has apic=3D1 then other doesn't, I'm not sure what the default = is, and
also one names its vif with vifname and the other doesn't.

Perhaps these don't matter but it suggests that you need to double chec= k
your assumption that these VMs are "identical".

Ian.





--f46d04339c4c91191f04c957e3bf-- --===============7875597278416629350== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users --===============7875597278416629350==-- From xen-users-bounces@lists.xen.org Mon Sep 10 12:19:11 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Mon, 10 Sep 2012 12:19:11 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TB2wg-0005Ts-Gb; Mon, 10 Sep 2012 12:18:30 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TB2we-0005Ti-U3 for xen-users@lists.xensource.com; Mon, 10 Sep 2012 12:18:29 +0000 Received: from [85.158.138.51:17617] by server-5.bemta-3.messagelabs.com id 6E/02-13133-49ADD405; Mon, 10 Sep 2012 12:18:28 +0000 X-Env-Sender: Ian.Campbell@citrix.com X-Msg-Ref: server-5.tower-174.messagelabs.com!1347279500!29763520!1 X-Originating-IP: [62.200.22.115] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogNjIuMjAwLjIyLjExNSA9PiAxMTIyODk=\n X-StarScan-Received: X-StarScan-Version: 6.6.1.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 10232 invoked from network); 10 Sep 2012 12:18:20 -0000 Received: from smtp.ctxuk.citrix.com (HELO SMTP.EU.CITRIX.COM) (62.200.22.115) by server-5.tower-174.messagelabs.com with RC4-SHA encrypted SMTP; 10 Sep 2012 12:18:20 -0000 X-IronPort-AV: E=Sophos;i="4.80,398,1344211200"; d="scan'208";a="14441907" Received: from lonpmailmx01.citrite.net ([10.30.203.162]) by LONPIPO01.EU.CITRIX.COM with ESMTP/TLS/RC4-MD5; 10 Sep 2012 12:18:20 +0000 Received: from [10.80.2.42] (10.80.2.42) by LONPMAILMX01.citrite.net (10.30.203.162) with Microsoft SMTP Server id 8.3.279.1; Mon, 10 Sep 2012 13:18:20 +0100 Message-ID: <1347279498.5305.78.camel@zakaz.uk.xensource.com> From: Ian Campbell To: chris Date: Mon, 10 Sep 2012 13:18:18 +0100 In-Reply-To: References: <1346164781.9975.27.camel@zakaz.uk.xensource.com> <1346229699.9975.30.camel@zakaz.uk.xensource.com> <1347267768.5305.32.camel@zakaz.uk.xensource.com> Organization: Citrix Systems, Inc. X-Mailer: Evolution 3.4.3-1 MIME-Version: 1.0 Cc: Xen-Users List Subject: Re: [Xen-users] pvhvm on debian X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org On Mon, 2012-09-10 at 13:13 +0100, chris wrote: > So I found the drivers, are you saying these are not pvhvm drivers? Strictly speaking no, these are the 3rd party modules irefered to earlier. > > > # find /lib/modules/2.6.18-194.3.1.el5/ | grep xen > /lib/modules/2.6.18-194.3.1.el5/kernel/drivers/net/netxen > /lib/modules/2.6.18-194.3.1.el5/kernel/drivers/net/netxen/netxen_nic.ko > /lib/modules/2.6.18-194.3.1.el5/kernel/drivers/xenpv_hvm > /lib/modules/2.6.18-194.3.1.el5/kernel/drivers/xenpv_hvm/platform-pci > /lib/modules/2.6.18-194.3.1.el5/kernel/drivers/xenpv_hvm/platform-pci/xen-platform-pci.ko > /lib/modules/2.6.18-194.3.1.el5/kernel/drivers/xenpv_hvm/netfront > /lib/modules/2.6.18-194.3.1.el5/kernel/drivers/xenpv_hvm/netfront/xen-vnif.ko > /lib/modules/2.6.18-194.3.1.el5/kernel/drivers/xenpv_hvm/blkfront > /lib/modules/2.6.18-194.3.1.el5/kernel/drivers/xenpv_hvm/blkfront/xen-vbd.ko > /lib/modules/2.6.18-194.3.1.el5/kernel/drivers/xenpv_hvm/balloon > /lib/modules/2.6.18-194.3.1.el5/kernel/drivers/xenpv_hvm/balloon/xen-balloon.ko > > > I can't find any packages that look like a seperate package for the > drivers only, I have a feeling its integrated with the kernel package I suspect RH have simply incorporated them into their kernel build directly for convenience (they also incorporate the hypervisor into the kenrel package) > [root@baraka ~]# rpm -qa | grep -i xen > [root@baraka ~]# rpm -qa | grep -i pv > iptables-ipv6-1.3.5-5.3.el5_4.1 > [root@baraka ~]# rpm -qa | grep -i hvm > > > Any idea how can I track down which drivers it is being used? > > > chris > > On Mon, Sep 10, 2012 at 8:00 AM, chris wrote: > Ian, > > > You are awesome! I figured it out by looking at console logs. > The nonworking domU had this in its console: > > > Detected Xen platform device but not Xen VMM? (sig Microsoft > Hv, eax 40000006) > xen-platform-pci: probe of 0000:00:03.0 failed with error -22 > > > The mention of hyperv reminded me back when I had to add > viridian=1 in order to avoid bluescreens in certain newer > versions of windows, and sure enough the nonworking centos > domU had viridian=1 > After removing/disabling this option the Xen pv drivers come > up properly. > > > Just for clarification on the centos side though, in regard to > your guest about if I installed any additional standalone PV > drivers, the answer is no. The only reason I referred to it as > PVHVM was I assumed that maybe pvhvm had become mainline and > the kernel centos was using had these features now. > > > Anyway its all working now and its good to know it works in > wheezy and I can continue to move towards that in production. > > > Thanks for all your time and help > chris > > On Mon, Sep 10, 2012 at 5:02 AM, Ian Campbell > wrote: > On Sun, 2012-09-09 at 21:23 +0100, chris wrote: > > So as you can see the domU is identical kernel in > both cases however > > when the domU is running on the wheezy dom0 even > despite that the > > platform pci device appears exactly the same in > lspci > > > Is the contents of the initrd identical in both cases? > Specifically do > they both contain the same set of kernel modules? > > Note that CentOS does not strictly speaking contain > "PVHVM", which is a > more recent upstream development. What you have here > is the PV drivers > add on driver from the unmodified_drivers. Did these > drivers ship with > CentOS or did you get them from elsewhere? Do you have > the source for > them? > > The difference is that PVHVM is part of the kernel > itself and are > tightly integrated, while the unmodified_drivers are a > set of drivers > used as an "add-on" pack for various existing OSes > (similar in principal > to how e.g. the Windows drivers are supplied for > Windows). The main > differences in practice will be at setup and > initialisation time, which > of course is where things appear to be going wrong for > you. > > I think this highlights why it is important to always > give all the > precise details in a bug report, this is the first > time CentOS has been > mentioned at all so I think I can be forgiven for > assuming you were > running Debian PVHVM in the guest too (which is what I > spent time > reproducing). > > > I've attached the configs and logs that you asked > for > > > I asked for guest console logs. The guest console logs > are where the > guest decisions about PVHVM drivers will be logged, if > anywhere. > > sektor-qemu.txt and baraka-qemu.txt are identical, but > they both contain > references to "baraka" which should surely be "sektor" > in the at least > one place (e.g. the disk path) for that VM. > > Your vm configs show the name has changed in the disk > path so I don't > see why it isn't different in the logs too. re you > sure these are the > actual logs from real runs of the guest? > > > Any ideas how to debug further? The difference > between the working > > scenario and nonworking is the dom0 distro (squeeze > vs wheezy), dom0 > > kernel and dom0 hypervisor > > Testing with both scenario's was done with the exact > same domU so I > > cant see how it could be a domU issue. > > > Comparing your guest configs shows that they aren't > actual quite > identical though, for reasons other than the different > names. > > One has apic=1 then other doesn't, I'm not sure what > the default is, and > also one names its vif with vifname and the other > doesn't. > > Perhaps these don't matter but it suggests that you > need to double check > your assumption that these VMs are "identical". > > Ian. > > > > > > _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Mon Sep 10 12:19:11 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Mon, 10 Sep 2012 12:19:11 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TB2wg-0005Ts-Gb; Mon, 10 Sep 2012 12:18:30 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TB2we-0005Ti-U3 for xen-users@lists.xensource.com; Mon, 10 Sep 2012 12:18:29 +0000 Received: from [85.158.138.51:17617] by server-5.bemta-3.messagelabs.com id 6E/02-13133-49ADD405; Mon, 10 Sep 2012 12:18:28 +0000 X-Env-Sender: Ian.Campbell@citrix.com X-Msg-Ref: server-5.tower-174.messagelabs.com!1347279500!29763520!1 X-Originating-IP: [62.200.22.115] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogNjIuMjAwLjIyLjExNSA9PiAxMTIyODk=\n X-StarScan-Received: X-StarScan-Version: 6.6.1.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 10232 invoked from network); 10 Sep 2012 12:18:20 -0000 Received: from smtp.ctxuk.citrix.com (HELO SMTP.EU.CITRIX.COM) (62.200.22.115) by server-5.tower-174.messagelabs.com with RC4-SHA encrypted SMTP; 10 Sep 2012 12:18:20 -0000 X-IronPort-AV: E=Sophos;i="4.80,398,1344211200"; d="scan'208";a="14441907" Received: from lonpmailmx01.citrite.net ([10.30.203.162]) by LONPIPO01.EU.CITRIX.COM with ESMTP/TLS/RC4-MD5; 10 Sep 2012 12:18:20 +0000 Received: from [10.80.2.42] (10.80.2.42) by LONPMAILMX01.citrite.net (10.30.203.162) with Microsoft SMTP Server id 8.3.279.1; Mon, 10 Sep 2012 13:18:20 +0100 Message-ID: <1347279498.5305.78.camel@zakaz.uk.xensource.com> From: Ian Campbell To: chris Date: Mon, 10 Sep 2012 13:18:18 +0100 In-Reply-To: References: <1346164781.9975.27.camel@zakaz.uk.xensource.com> <1346229699.9975.30.camel@zakaz.uk.xensource.com> <1347267768.5305.32.camel@zakaz.uk.xensource.com> Organization: Citrix Systems, Inc. X-Mailer: Evolution 3.4.3-1 MIME-Version: 1.0 Cc: Xen-Users List Subject: Re: [Xen-users] pvhvm on debian X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org On Mon, 2012-09-10 at 13:13 +0100, chris wrote: > So I found the drivers, are you saying these are not pvhvm drivers? Strictly speaking no, these are the 3rd party modules irefered to earlier. > > > # find /lib/modules/2.6.18-194.3.1.el5/ | grep xen > /lib/modules/2.6.18-194.3.1.el5/kernel/drivers/net/netxen > /lib/modules/2.6.18-194.3.1.el5/kernel/drivers/net/netxen/netxen_nic.ko > /lib/modules/2.6.18-194.3.1.el5/kernel/drivers/xenpv_hvm > /lib/modules/2.6.18-194.3.1.el5/kernel/drivers/xenpv_hvm/platform-pci > /lib/modules/2.6.18-194.3.1.el5/kernel/drivers/xenpv_hvm/platform-pci/xen-platform-pci.ko > /lib/modules/2.6.18-194.3.1.el5/kernel/drivers/xenpv_hvm/netfront > /lib/modules/2.6.18-194.3.1.el5/kernel/drivers/xenpv_hvm/netfront/xen-vnif.ko > /lib/modules/2.6.18-194.3.1.el5/kernel/drivers/xenpv_hvm/blkfront > /lib/modules/2.6.18-194.3.1.el5/kernel/drivers/xenpv_hvm/blkfront/xen-vbd.ko > /lib/modules/2.6.18-194.3.1.el5/kernel/drivers/xenpv_hvm/balloon > /lib/modules/2.6.18-194.3.1.el5/kernel/drivers/xenpv_hvm/balloon/xen-balloon.ko > > > I can't find any packages that look like a seperate package for the > drivers only, I have a feeling its integrated with the kernel package I suspect RH have simply incorporated them into their kernel build directly for convenience (they also incorporate the hypervisor into the kenrel package) > [root@baraka ~]# rpm -qa | grep -i xen > [root@baraka ~]# rpm -qa | grep -i pv > iptables-ipv6-1.3.5-5.3.el5_4.1 > [root@baraka ~]# rpm -qa | grep -i hvm > > > Any idea how can I track down which drivers it is being used? > > > chris > > On Mon, Sep 10, 2012 at 8:00 AM, chris wrote: > Ian, > > > You are awesome! I figured it out by looking at console logs. > The nonworking domU had this in its console: > > > Detected Xen platform device but not Xen VMM? (sig Microsoft > Hv, eax 40000006) > xen-platform-pci: probe of 0000:00:03.0 failed with error -22 > > > The mention of hyperv reminded me back when I had to add > viridian=1 in order to avoid bluescreens in certain newer > versions of windows, and sure enough the nonworking centos > domU had viridian=1 > After removing/disabling this option the Xen pv drivers come > up properly. > > > Just for clarification on the centos side though, in regard to > your guest about if I installed any additional standalone PV > drivers, the answer is no. The only reason I referred to it as > PVHVM was I assumed that maybe pvhvm had become mainline and > the kernel centos was using had these features now. > > > Anyway its all working now and its good to know it works in > wheezy and I can continue to move towards that in production. > > > Thanks for all your time and help > chris > > On Mon, Sep 10, 2012 at 5:02 AM, Ian Campbell > wrote: > On Sun, 2012-09-09 at 21:23 +0100, chris wrote: > > So as you can see the domU is identical kernel in > both cases however > > when the domU is running on the wheezy dom0 even > despite that the > > platform pci device appears exactly the same in > lspci > > > Is the contents of the initrd identical in both cases? > Specifically do > they both contain the same set of kernel modules? > > Note that CentOS does not strictly speaking contain > "PVHVM", which is a > more recent upstream development. What you have here > is the PV drivers > add on driver from the unmodified_drivers. Did these > drivers ship with > CentOS or did you get them from elsewhere? Do you have > the source for > them? > > The difference is that PVHVM is part of the kernel > itself and are > tightly integrated, while the unmodified_drivers are a > set of drivers > used as an "add-on" pack for various existing OSes > (similar in principal > to how e.g. the Windows drivers are supplied for > Windows). The main > differences in practice will be at setup and > initialisation time, which > of course is where things appear to be going wrong for > you. > > I think this highlights why it is important to always > give all the > precise details in a bug report, this is the first > time CentOS has been > mentioned at all so I think I can be forgiven for > assuming you were > running Debian PVHVM in the guest too (which is what I > spent time > reproducing). > > > I've attached the configs and logs that you asked > for > > > I asked for guest console logs. The guest console logs > are where the > guest decisions about PVHVM drivers will be logged, if > anywhere. > > sektor-qemu.txt and baraka-qemu.txt are identical, but > they both contain > references to "baraka" which should surely be "sektor" > in the at least > one place (e.g. the disk path) for that VM. > > Your vm configs show the name has changed in the disk > path so I don't > see why it isn't different in the logs too. re you > sure these are the > actual logs from real runs of the guest? > > > Any ideas how to debug further? The difference > between the working > > scenario and nonworking is the dom0 distro (squeeze > vs wheezy), dom0 > > kernel and dom0 hypervisor > > Testing with both scenario's was done with the exact > same domU so I > > cant see how it could be a domU issue. > > > Comparing your guest configs shows that they aren't > actual quite > identical though, for reasons other than the different > names. > > One has apic=1 then other doesn't, I'm not sure what > the default is, and > also one names its vif with vifname and the other > doesn't. > > Perhaps these don't matter but it suggests that you > need to double check > your assumption that these VMs are "identical". > > Ian. > > > > > > _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Mon Sep 10 12:19:11 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Mon, 10 Sep 2012 12:19:11 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TB2wX-0005TG-S5; Mon, 10 Sep 2012 12:18:21 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TB2wV-0005T8-Ux for xen-users@lists.xensource.com; Mon, 10 Sep 2012 12:18:20 +0000 Received: from [85.158.143.99:57948] by server-1.bemta-4.messagelabs.com id FC/8B-12504-B8ADD405; Mon, 10 Sep 2012 12:18:19 +0000 X-Env-Sender: Ian.Campbell@citrix.com X-Msg-Ref: server-12.tower-216.messagelabs.com!1347279470!24270876!1 X-Originating-IP: [62.200.22.115] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogNjIuMjAwLjIyLjExNSA9PiAxMTIyODk=\n X-StarScan-Received: X-StarScan-Version: 6.6.1.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 977 invoked from network); 10 Sep 2012 12:17:50 -0000 Received: from smtp.ctxuk.citrix.com (HELO SMTP.EU.CITRIX.COM) (62.200.22.115) by server-12.tower-216.messagelabs.com with RC4-SHA encrypted SMTP; 10 Sep 2012 12:17:50 -0000 X-IronPort-AV: E=Sophos;i="4.80,398,1344211200"; d="scan'208";a="14441871" Received: from lonpmailmx01.citrite.net ([10.30.203.162]) by LONPIPO01.EU.CITRIX.COM with ESMTP/TLS/RC4-MD5; 10 Sep 2012 12:17:20 +0000 Received: from [10.80.2.42] (10.80.2.42) by LONPMAILMX01.citrite.net (10.30.203.162) with Microsoft SMTP Server id 8.3.279.1; Mon, 10 Sep 2012 13:17:20 +0100 Message-ID: <1347279439.5305.77.camel@zakaz.uk.xensource.com> From: Ian Campbell To: chris Date: Mon, 10 Sep 2012 13:17:19 +0100 In-Reply-To: References: <1346164781.9975.27.camel@zakaz.uk.xensource.com> <1346229699.9975.30.camel@zakaz.uk.xensource.com> <1347267768.5305.32.camel@zakaz.uk.xensource.com> Organization: Citrix Systems, Inc. X-Mailer: Evolution 3.4.3-1 MIME-Version: 1.0 Cc: Xen-Users List Subject: Re: [Xen-users] pvhvm on debian X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org On Mon, 2012-09-10 at 13:00 +0100, chris wrote: > The mention of hyperv reminded me back when I had to add viridian=1 in > order to avoid bluescreens in certain newer versions of windows, and > sure enough the nonworking centos domU had viridian=1 I'm a little bit annoyed by this since neither of the two VM configurations you previously sent, one of which you claimed represented the broken VM, had this in it. If it had I would have immediately mentioned it since it was one of the things I considered. Please, when you ask for help on a list and expect people to spend their valuable time helping you always try and provide correct, consistent and above all *truthful* information. By providing such incorrect information you have caused me to waste my time trying to provide help based on a false understanding of your configuration. Ian. _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Mon Sep 10 12:19:11 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Mon, 10 Sep 2012 12:19:11 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TB2wX-0005TG-S5; Mon, 10 Sep 2012 12:18:21 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TB2wV-0005T8-Ux for xen-users@lists.xensource.com; Mon, 10 Sep 2012 12:18:20 +0000 Received: from [85.158.143.99:57948] by server-1.bemta-4.messagelabs.com id FC/8B-12504-B8ADD405; Mon, 10 Sep 2012 12:18:19 +0000 X-Env-Sender: Ian.Campbell@citrix.com X-Msg-Ref: server-12.tower-216.messagelabs.com!1347279470!24270876!1 X-Originating-IP: [62.200.22.115] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogNjIuMjAwLjIyLjExNSA9PiAxMTIyODk=\n X-StarScan-Received: X-StarScan-Version: 6.6.1.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 977 invoked from network); 10 Sep 2012 12:17:50 -0000 Received: from smtp.ctxuk.citrix.com (HELO SMTP.EU.CITRIX.COM) (62.200.22.115) by server-12.tower-216.messagelabs.com with RC4-SHA encrypted SMTP; 10 Sep 2012 12:17:50 -0000 X-IronPort-AV: E=Sophos;i="4.80,398,1344211200"; d="scan'208";a="14441871" Received: from lonpmailmx01.citrite.net ([10.30.203.162]) by LONPIPO01.EU.CITRIX.COM with ESMTP/TLS/RC4-MD5; 10 Sep 2012 12:17:20 +0000 Received: from [10.80.2.42] (10.80.2.42) by LONPMAILMX01.citrite.net (10.30.203.162) with Microsoft SMTP Server id 8.3.279.1; Mon, 10 Sep 2012 13:17:20 +0100 Message-ID: <1347279439.5305.77.camel@zakaz.uk.xensource.com> From: Ian Campbell To: chris Date: Mon, 10 Sep 2012 13:17:19 +0100 In-Reply-To: References: <1346164781.9975.27.camel@zakaz.uk.xensource.com> <1346229699.9975.30.camel@zakaz.uk.xensource.com> <1347267768.5305.32.camel@zakaz.uk.xensource.com> Organization: Citrix Systems, Inc. X-Mailer: Evolution 3.4.3-1 MIME-Version: 1.0 Cc: Xen-Users List Subject: Re: [Xen-users] pvhvm on debian X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org On Mon, 2012-09-10 at 13:00 +0100, chris wrote: > The mention of hyperv reminded me back when I had to add viridian=1 in > order to avoid bluescreens in certain newer versions of windows, and > sure enough the nonworking centos domU had viridian=1 I'm a little bit annoyed by this since neither of the two VM configurations you previously sent, one of which you claimed represented the broken VM, had this in it. If it had I would have immediately mentioned it since it was one of the things I considered. Please, when you ask for help on a list and expect people to spend their valuable time helping you always try and provide correct, consistent and above all *truthful* information. By providing such incorrect information you have caused me to waste my time trying to provide help based on a false understanding of your configuration. Ian. _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Mon Sep 10 12:21:39 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Mon, 10 Sep 2012 12:21:39 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TB2zI-0005sl-OC; Mon, 10 Sep 2012 12:21:12 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TB2zH-0005sJ-AW for xen-users@lists.xen.org; Mon, 10 Sep 2012 12:21:11 +0000 Received: from [85.158.139.83:9784] by server-7.bemta-5.messagelabs.com id 59/15-19703-53BDD405; Mon, 10 Sep 2012 12:21:09 +0000 X-Env-Sender: ashok.anand@gmail.com X-Msg-Ref: server-8.tower-182.messagelabs.com!1347279632!18312833!1 X-Originating-IP: [209.85.219.45] X-SpamReason: No, hits=1.2 required=7.0 tests=HTML_20_30,HTML_MESSAGE, ML_RADAR_SPEW_LINKS_14,RCVD_BY_IP,spamassassin: X-StarScan-Received: X-StarScan-Version: 6.6.1.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 31854 invoked from network); 10 Sep 2012 12:20:34 -0000 Received: from mail-oa0-f45.google.com (HELO mail-oa0-f45.google.com) (209.85.219.45) by server-8.tower-182.messagelabs.com with RC4-SHA encrypted SMTP; 10 Sep 2012 12:20:34 -0000 Received: by oagn12 with SMTP id n12so637235oag.32 for ; Mon, 10 Sep 2012 05:20:32 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:date:message-id:subject:from:to:content-type; bh=QYHCLmCYjBVljXrIHSZnh3NFMgo8HtYTtIf1KMcCu1M=; b=kxY4GVF/d7yafPh3nEwgRS9Ygn1RlXjTsoxgV9XZF5EDh1mNTiimIvVA35kbM/UOk0 8T3CO3tGDpfEeFIlPE0uLhBgSZS4OI12Y/abZMcDpPr7tG9/hxmnsfx2QN8yXvijOzIP sLVfdDK3rDf8pTPFTChpvMjcIYn5PK5TcmMRGIreHkzV6w1AfOkEIWjQ+lM3+7Jq7NYt L4DVKsoXZ3X9KU2TqgRP/4A+1uA/+tl98dTviLJ+aCZqF1PQdUIGzgfhRgH1nfGnb1Km CpxKC+EFqNr18KhCdpD96i9U1DIDrj6/V3tJ5ubYepMxeyPbvfDmV9UmndVoww4reW4l 82fQ== MIME-Version: 1.0 Received: by 10.60.0.161 with SMTP id 1mr14193735oef.83.1347279632193; Mon, 10 Sep 2012 05:20:32 -0700 (PDT) Received: by 10.182.32.102 with HTTP; Mon, 10 Sep 2012 05:20:32 -0700 (PDT) Date: Mon, 10 Sep 2012 17:50:32 +0530 Message-ID: From: Ashok Anand To: xen-devel@lists.xen.org, xen-users@lists.xen.org Subject: [Xen-users] memory snapshot X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============5169109666135203718==" Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org --===============5169109666135203718== Content-Type: multipart/alternative; boundary=e89a8fb1ffc2e3d9d604c957fbd9 --e89a8fb1ffc2e3d9d604c957fbd9 Content-Type: text/plain; charset=ISO-8859-1 Hi, I want to take the snapshot of only physical memory of a VM. I know that we can take memory dump of a VM, using xm dump-core, or using xm save. However, with these tools, the dumped (or saved) file would have some headers/metadata along with the memory contents. So, I am wondering if there is a tool, that can help me to give only memory contents (headers removed), or alternatively, if there is a tool that can remove these headers/metadata, and give the memory content back. Any thoughts? Regards., Ashok --e89a8fb1ffc2e3d9d604c957fbd9 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Hi,=A0

I want to take the snapshot of only physical memo= ry of a VM.=A0
I know that we can take memory dump of a VM, using= xm dump-core, or using xm save.
However, with these tools, the d= umped (or saved) file would have some headers/metadata along with
the memory contents.
So, I am wondering if there is a tool, = that can help me to give only memory contents (headers removed),
= or alternatively, if there is a tool that can remove these headers/metadata= , and give the memory content back.

Any thoughts?

Regards.,
<= div>Ashok
--e89a8fb1ffc2e3d9d604c957fbd9-- --===============5169109666135203718== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users --===============5169109666135203718==-- From xen-users-bounces@lists.xen.org Mon Sep 10 12:21:39 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Mon, 10 Sep 2012 12:21:39 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TB2zI-0005sl-OC; Mon, 10 Sep 2012 12:21:12 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TB2zH-0005sJ-AW for xen-users@lists.xen.org; Mon, 10 Sep 2012 12:21:11 +0000 Received: from [85.158.139.83:9784] by server-7.bemta-5.messagelabs.com id 59/15-19703-53BDD405; Mon, 10 Sep 2012 12:21:09 +0000 X-Env-Sender: ashok.anand@gmail.com X-Msg-Ref: server-8.tower-182.messagelabs.com!1347279632!18312833!1 X-Originating-IP: [209.85.219.45] X-SpamReason: No, hits=1.2 required=7.0 tests=HTML_20_30,HTML_MESSAGE, ML_RADAR_SPEW_LINKS_14,RCVD_BY_IP,spamassassin: X-StarScan-Received: X-StarScan-Version: 6.6.1.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 31854 invoked from network); 10 Sep 2012 12:20:34 -0000 Received: from mail-oa0-f45.google.com (HELO mail-oa0-f45.google.com) (209.85.219.45) by server-8.tower-182.messagelabs.com with RC4-SHA encrypted SMTP; 10 Sep 2012 12:20:34 -0000 Received: by oagn12 with SMTP id n12so637235oag.32 for ; Mon, 10 Sep 2012 05:20:32 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:date:message-id:subject:from:to:content-type; bh=QYHCLmCYjBVljXrIHSZnh3NFMgo8HtYTtIf1KMcCu1M=; b=kxY4GVF/d7yafPh3nEwgRS9Ygn1RlXjTsoxgV9XZF5EDh1mNTiimIvVA35kbM/UOk0 8T3CO3tGDpfEeFIlPE0uLhBgSZS4OI12Y/abZMcDpPr7tG9/hxmnsfx2QN8yXvijOzIP sLVfdDK3rDf8pTPFTChpvMjcIYn5PK5TcmMRGIreHkzV6w1AfOkEIWjQ+lM3+7Jq7NYt L4DVKsoXZ3X9KU2TqgRP/4A+1uA/+tl98dTviLJ+aCZqF1PQdUIGzgfhRgH1nfGnb1Km CpxKC+EFqNr18KhCdpD96i9U1DIDrj6/V3tJ5ubYepMxeyPbvfDmV9UmndVoww4reW4l 82fQ== MIME-Version: 1.0 Received: by 10.60.0.161 with SMTP id 1mr14193735oef.83.1347279632193; Mon, 10 Sep 2012 05:20:32 -0700 (PDT) Received: by 10.182.32.102 with HTTP; Mon, 10 Sep 2012 05:20:32 -0700 (PDT) Date: Mon, 10 Sep 2012 17:50:32 +0530 Message-ID: From: Ashok Anand To: xen-devel@lists.xen.org, xen-users@lists.xen.org Subject: [Xen-users] memory snapshot X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============5169109666135203718==" Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org --===============5169109666135203718== Content-Type: multipart/alternative; boundary=e89a8fb1ffc2e3d9d604c957fbd9 --e89a8fb1ffc2e3d9d604c957fbd9 Content-Type: text/plain; charset=ISO-8859-1 Hi, I want to take the snapshot of only physical memory of a VM. I know that we can take memory dump of a VM, using xm dump-core, or using xm save. However, with these tools, the dumped (or saved) file would have some headers/metadata along with the memory contents. So, I am wondering if there is a tool, that can help me to give only memory contents (headers removed), or alternatively, if there is a tool that can remove these headers/metadata, and give the memory content back. Any thoughts? Regards., Ashok --e89a8fb1ffc2e3d9d604c957fbd9 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Hi,=A0

I want to take the snapshot of only physical memo= ry of a VM.=A0
I know that we can take memory dump of a VM, using= xm dump-core, or using xm save.
However, with these tools, the d= umped (or saved) file would have some headers/metadata along with
the memory contents.
So, I am wondering if there is a tool, = that can help me to give only memory contents (headers removed),
= or alternatively, if there is a tool that can remove these headers/metadata= , and give the memory content back.

Any thoughts?

Regards.,
<= div>Ashok
--e89a8fb1ffc2e3d9d604c957fbd9-- --===============5169109666135203718== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users --===============5169109666135203718==-- From xen-users-bounces@lists.xen.org Mon Sep 10 15:01:22 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Mon, 10 Sep 2012 15:01:22 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TB5TO-0002fi-KK; Mon, 10 Sep 2012 15:00:26 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TB5TM-0002fd-N4 for xen-users@lists.xen.org; Mon, 10 Sep 2012 15:00:25 +0000 Received: from [85.158.139.83:15157] by server-4.bemta-5.messagelabs.com id 86/CB-23042-7800E405; Mon, 10 Sep 2012 15:00:23 +0000 X-Env-Sender: maik.brauer@mbs-systems.net X-Msg-Ref: server-8.tower-182.messagelabs.com!1347289223!18352055!1 X-Originating-IP: [188.40.240.248] X-SpamReason: No, hits=0.0 required=7.0 tests= X-StarScan-Received: X-StarScan-Version: 6.6.1.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 6184 invoked from network); 10 Sep 2012 15:00:23 -0000 Received: from mx1.mbs-systems.net (HELO mx1.mbs-systems.net) (188.40.240.248) by server-8.tower-182.messagelabs.com with SMTP; 10 Sep 2012 15:00:23 -0000 Received: from localhost (localhost [127.0.0.1]) by mx1.mbs-systems.net (Postfix) with ESMTP id 98DC45C30B; Mon, 10 Sep 2012 17:01:23 +0200 (CEST) Received: from mx1.mbs-systems.net ([127.0.0.1]) by localhost (mta.mbs-systems.net [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 1vjdyJKuqmVP; Mon, 10 Sep 2012 17:01:23 +0200 (CEST) Received: from [62.213.147.241] (unknown [62.213.147.241]) by mx1.mbs-systems.net (Postfix) with ESMTPSA id 20BB55C221; Mon, 10 Sep 2012 17:01:23 +0200 (CEST) Mime-Version: 1.0 (Apple Message framework v1278) From: Maik Brauer In-Reply-To: <1347266386.5305.17.camel@zakaz.uk.xensource.com> Date: Mon, 10 Sep 2012 17:00:21 +0200 Message-Id: <4957C391-6070-47C1-A2AC-991ED1C1766A@mbs-systems.net> References: <9F8FD2B0-450A-4A6E-A929-BA240ED1D997@mbs-systems.net> <1346746297.32462.37.camel@zakaz.uk.xensource.com> <1347266386.5305.17.camel@zakaz.uk.xensource.com> To: Ian Campbell X-Mailer: Apple Mail (2.1278) Cc: xen-users@lists.xen.org Subject: Re: [Xen-users] Dom0 crashed when rebooting whilst DomU are running X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org On Sep 10, 2012, at 10:39 AM, Ian Campbell wrote: > On Sat, 2012-09-08 at 15:50 +0100, Maik Brauer wrote: >> On Sep 4, 2012, at 10:11 AM, Ian Campbell wrote: >> >>> Could you not top post please, it makes it rather hard to follow the >>> flow of the conversation. >>> On Mon, 2012-09-03 at 18:10 +0100, Casey DeLorme wrote: >>>> As stated, you can alias shutdown to do exactly what you need, it can >>>> be as simple as a series of hard-coded operations to a complex custom >>>> shell script that parses your domains and closes each with feedback. >>> >>> Xen ships the "xendomains" initscript which can halt guest on shutdown >>> as well as automatically start specific guests on boot. It can also be >>> configured to suspend/resume them or (I think) migrate them away. >>> >>> For diagnosing the crash itself more details will be required than were >>> provided in the original post. Please see >>> http://wiki.xen.org/wiki/Reporting_Bugs_against_Xen for some guidance. >>> At a minimum we would need a capture (serial console or photo) of the >>> crash backtrace. >>> >>> Ian. >>> >>> >> I found out that it hangs during re-boot of dom0 when having more >> Network interfaces involved, like: >> vif = [ 'mac=06:46:AB:CC:11:01, ip=', '', '', >> 'mac=06:04:AB:BB:11:03, bridge=VLAN20, script=vif-bridge', '', >> 'mac=06:04:AB:BB:11:05, bridge=VLAN40, script=vif-bridge' ] > > 6 interfaces total, 3 of which have a random mac on each reboot and all > get put on the default bridge? No, not really. The bridge is different for each interface. We have VLAN20, VLAN40, etc as bridges. These one will be created as well at the beginning when the system starts up (create_bridges.sh): /usr/sbin/brctl addbr VLAN11 /usr/sbin/brctl addbr VLAN12 /usr/sbin/brctl addbr VLAN20 /usr/sbin/brctl addbr VLAN30 /usr/sbin/brctl addbr VLAN40 /sbin/ifconfig VLAN11 down -arp up /sbin/ifconfig VLAN12 down -arp up /sbin/ifconfig VLAN20 down -arp up /sbin/ifconfig VLAN30 down -arp up /sbin/ifconfig VLAN40 down -arp up > > Is your default script vif-bridge or something else? Have you modified > any of these scripts? No I didn't modify anything. Still the original script. > >> in case you use just one or having the basic line in place, it is >> working: >> vif = [ '' ] >> >> The system stops after initiating the reboot at the following line in the console: System will restart........... > > So this is a hang, not a crash as suggested originally? Yes, you are right. It is just a hang. > > If it is a hang then you might have some luck using hte magic sysrq keys > to print lists of blocked tasks. I'm not sure in Squeeze but you might > need to enable this as described in Documentation/sysrq.txt in the Linux > source. > > Blocked tasks are listed with SysRQ-'w'. If you have serial console then > 't' will list all task, but that list can be quite long so it is useless > without a serial console. List is empty. SysRQ -w and SysRQ-t shows nothing at all. There is nothing running anymore. It shows periodically: INFO: task xenwatch:12 blocked for more than 120 seconds Seems that the xenwatch is blocking the reboot here, is that assumption correct? But strange enough that I can't see any process anymore with the SysRQ -t or SysRQ -w >> In the Logfile of /var/log/message you can find this as the last line: >> Sep 8 15:44:28 rootsrv01 shutdown[2445]: shutting down for system reboot >> Sep 8 15:44:31 rootsrv01 kernel: [ 73.716246] VLAN20: port 1(vif2.3) entering forwarding state >> Sep 8 15:44:31 rootsrv01 kernel: [ 74.500111] VLAN40: port 1(vif2.5) entering forwarding state >> Sep 8 15:44:34 rootsrv01 kernel: [ 77.317431] VLAN20: port 1(vif2.3) entering disabled state >> Sep 8 15:44:34 rootsrv01 kernel: [ 77.317490] VLAN20: port 1(vif2.3) entering disabled state >> Sep 8 15:44:36 rootsrv01 kernel: [ 79.368685] VLAN40: port 1(vif2.5) entering disabled state >> Sep 8 15:44:36 rootsrv01 kernel: [ 79.369156] VLAN40: port 1(vif2.5) entering disabled state >> Sep 8 15:44:37 rootsrv01 kernel: Kernel logging (proc) stopped. >> Sep 8 15:44:37 rootsrv01 rsyslogd: [origin software="rsyslogd" swVersion="4.6.4" x-pid="890" x-info="http://www.rsyslog.com"] exiting on signal 15. >> >> In the /var/log/daemong.log you can find this message: >> Sep 8 15:44:37 rootsrv01 acpid: exiting >> Sep 8 15:44:37 rootsrv01 rpc.statd[750]: Caught signal 15, un-registering and exiting > > All the above (both message and daemon.log) look like normal parts of > shutting down to me. > >> Sep 8 15:44:37 rootsrv01 udevd-work[2276]: '/etc/xen/scripts/vif-setup offline type_if=vif' unexpected exit with status 0x000f > > This might be worth following up on. When putting a "sleep 5" in stop section of the /etc/init.d/xendomains: case "$1" in start) start rc_status if test -f $LOCKFILE; then rc_status -v; fi ;; stop) stop rc_status -v sleep 5 ;; then the system shuts down as expected and is rebooting properly. In the daemon.log file I couldn't find the error: Sep 8 15:44:37 rootsrv01 udevd-work[2276]: '/etc/xen/scripts/vif-setup offline type_if=vif' unexpected exit with status 0x000f anymore. It seems that it disappeared after putting a delay inside. Could it be a race condition here during shutdown, with the udev-daemon?? > > I would do this by adding near the top of vif-setup and/or vif-bridge > (or whichever script you use): > exec 1>>/var/log/vif-setup.log > exec 2>&1 > > I would then also annotate all through vif-bridge in the offline path > with echo statements showing how far it got and what command was to be > run next. > > Ian. > > > _______________________________________________ > Xen-users mailing list > Xen-users@lists.xen.org > http://lists.xen.org/xen-users _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Mon Sep 10 15:01:22 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Mon, 10 Sep 2012 15:01:22 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TB5TO-0002fi-KK; Mon, 10 Sep 2012 15:00:26 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TB5TM-0002fd-N4 for xen-users@lists.xen.org; Mon, 10 Sep 2012 15:00:25 +0000 Received: from [85.158.139.83:15157] by server-4.bemta-5.messagelabs.com id 86/CB-23042-7800E405; Mon, 10 Sep 2012 15:00:23 +0000 X-Env-Sender: maik.brauer@mbs-systems.net X-Msg-Ref: server-8.tower-182.messagelabs.com!1347289223!18352055!1 X-Originating-IP: [188.40.240.248] X-SpamReason: No, hits=0.0 required=7.0 tests= X-StarScan-Received: X-StarScan-Version: 6.6.1.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 6184 invoked from network); 10 Sep 2012 15:00:23 -0000 Received: from mx1.mbs-systems.net (HELO mx1.mbs-systems.net) (188.40.240.248) by server-8.tower-182.messagelabs.com with SMTP; 10 Sep 2012 15:00:23 -0000 Received: from localhost (localhost [127.0.0.1]) by mx1.mbs-systems.net (Postfix) with ESMTP id 98DC45C30B; Mon, 10 Sep 2012 17:01:23 +0200 (CEST) Received: from mx1.mbs-systems.net ([127.0.0.1]) by localhost (mta.mbs-systems.net [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 1vjdyJKuqmVP; Mon, 10 Sep 2012 17:01:23 +0200 (CEST) Received: from [62.213.147.241] (unknown [62.213.147.241]) by mx1.mbs-systems.net (Postfix) with ESMTPSA id 20BB55C221; Mon, 10 Sep 2012 17:01:23 +0200 (CEST) Mime-Version: 1.0 (Apple Message framework v1278) From: Maik Brauer In-Reply-To: <1347266386.5305.17.camel@zakaz.uk.xensource.com> Date: Mon, 10 Sep 2012 17:00:21 +0200 Message-Id: <4957C391-6070-47C1-A2AC-991ED1C1766A@mbs-systems.net> References: <9F8FD2B0-450A-4A6E-A929-BA240ED1D997@mbs-systems.net> <1346746297.32462.37.camel@zakaz.uk.xensource.com> <1347266386.5305.17.camel@zakaz.uk.xensource.com> To: Ian Campbell X-Mailer: Apple Mail (2.1278) Cc: xen-users@lists.xen.org Subject: Re: [Xen-users] Dom0 crashed when rebooting whilst DomU are running X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org On Sep 10, 2012, at 10:39 AM, Ian Campbell wrote: > On Sat, 2012-09-08 at 15:50 +0100, Maik Brauer wrote: >> On Sep 4, 2012, at 10:11 AM, Ian Campbell wrote: >> >>> Could you not top post please, it makes it rather hard to follow the >>> flow of the conversation. >>> On Mon, 2012-09-03 at 18:10 +0100, Casey DeLorme wrote: >>>> As stated, you can alias shutdown to do exactly what you need, it can >>>> be as simple as a series of hard-coded operations to a complex custom >>>> shell script that parses your domains and closes each with feedback. >>> >>> Xen ships the "xendomains" initscript which can halt guest on shutdown >>> as well as automatically start specific guests on boot. It can also be >>> configured to suspend/resume them or (I think) migrate them away. >>> >>> For diagnosing the crash itself more details will be required than were >>> provided in the original post. Please see >>> http://wiki.xen.org/wiki/Reporting_Bugs_against_Xen for some guidance. >>> At a minimum we would need a capture (serial console or photo) of the >>> crash backtrace. >>> >>> Ian. >>> >>> >> I found out that it hangs during re-boot of dom0 when having more >> Network interfaces involved, like: >> vif = [ 'mac=06:46:AB:CC:11:01, ip=', '', '', >> 'mac=06:04:AB:BB:11:03, bridge=VLAN20, script=vif-bridge', '', >> 'mac=06:04:AB:BB:11:05, bridge=VLAN40, script=vif-bridge' ] > > 6 interfaces total, 3 of which have a random mac on each reboot and all > get put on the default bridge? No, not really. The bridge is different for each interface. We have VLAN20, VLAN40, etc as bridges. These one will be created as well at the beginning when the system starts up (create_bridges.sh): /usr/sbin/brctl addbr VLAN11 /usr/sbin/brctl addbr VLAN12 /usr/sbin/brctl addbr VLAN20 /usr/sbin/brctl addbr VLAN30 /usr/sbin/brctl addbr VLAN40 /sbin/ifconfig VLAN11 down -arp up /sbin/ifconfig VLAN12 down -arp up /sbin/ifconfig VLAN20 down -arp up /sbin/ifconfig VLAN30 down -arp up /sbin/ifconfig VLAN40 down -arp up > > Is your default script vif-bridge or something else? Have you modified > any of these scripts? No I didn't modify anything. Still the original script. > >> in case you use just one or having the basic line in place, it is >> working: >> vif = [ '' ] >> >> The system stops after initiating the reboot at the following line in the console: System will restart........... > > So this is a hang, not a crash as suggested originally? Yes, you are right. It is just a hang. > > If it is a hang then you might have some luck using hte magic sysrq keys > to print lists of blocked tasks. I'm not sure in Squeeze but you might > need to enable this as described in Documentation/sysrq.txt in the Linux > source. > > Blocked tasks are listed with SysRQ-'w'. If you have serial console then > 't' will list all task, but that list can be quite long so it is useless > without a serial console. List is empty. SysRQ -w and SysRQ-t shows nothing at all. There is nothing running anymore. It shows periodically: INFO: task xenwatch:12 blocked for more than 120 seconds Seems that the xenwatch is blocking the reboot here, is that assumption correct? But strange enough that I can't see any process anymore with the SysRQ -t or SysRQ -w >> In the Logfile of /var/log/message you can find this as the last line: >> Sep 8 15:44:28 rootsrv01 shutdown[2445]: shutting down for system reboot >> Sep 8 15:44:31 rootsrv01 kernel: [ 73.716246] VLAN20: port 1(vif2.3) entering forwarding state >> Sep 8 15:44:31 rootsrv01 kernel: [ 74.500111] VLAN40: port 1(vif2.5) entering forwarding state >> Sep 8 15:44:34 rootsrv01 kernel: [ 77.317431] VLAN20: port 1(vif2.3) entering disabled state >> Sep 8 15:44:34 rootsrv01 kernel: [ 77.317490] VLAN20: port 1(vif2.3) entering disabled state >> Sep 8 15:44:36 rootsrv01 kernel: [ 79.368685] VLAN40: port 1(vif2.5) entering disabled state >> Sep 8 15:44:36 rootsrv01 kernel: [ 79.369156] VLAN40: port 1(vif2.5) entering disabled state >> Sep 8 15:44:37 rootsrv01 kernel: Kernel logging (proc) stopped. >> Sep 8 15:44:37 rootsrv01 rsyslogd: [origin software="rsyslogd" swVersion="4.6.4" x-pid="890" x-info="http://www.rsyslog.com"] exiting on signal 15. >> >> In the /var/log/daemong.log you can find this message: >> Sep 8 15:44:37 rootsrv01 acpid: exiting >> Sep 8 15:44:37 rootsrv01 rpc.statd[750]: Caught signal 15, un-registering and exiting > > All the above (both message and daemon.log) look like normal parts of > shutting down to me. > >> Sep 8 15:44:37 rootsrv01 udevd-work[2276]: '/etc/xen/scripts/vif-setup offline type_if=vif' unexpected exit with status 0x000f > > This might be worth following up on. When putting a "sleep 5" in stop section of the /etc/init.d/xendomains: case "$1" in start) start rc_status if test -f $LOCKFILE; then rc_status -v; fi ;; stop) stop rc_status -v sleep 5 ;; then the system shuts down as expected and is rebooting properly. In the daemon.log file I couldn't find the error: Sep 8 15:44:37 rootsrv01 udevd-work[2276]: '/etc/xen/scripts/vif-setup offline type_if=vif' unexpected exit with status 0x000f anymore. It seems that it disappeared after putting a delay inside. Could it be a race condition here during shutdown, with the udev-daemon?? > > I would do this by adding near the top of vif-setup and/or vif-bridge > (or whichever script you use): > exec 1>>/var/log/vif-setup.log > exec 2>&1 > > I would then also annotate all through vif-bridge in the offline path > with echo statements showing how far it got and what command was to be > run next. > > Ian. > > > _______________________________________________ > Xen-users mailing list > Xen-users@lists.xen.org > http://lists.xen.org/xen-users _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Mon Sep 10 15:11:54 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Mon, 10 Sep 2012 15:11:54 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TB5di-00035f-CX; Mon, 10 Sep 2012 15:11:06 +0000 Received: from mail27.messagelabs.com ([193.109.254.147]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TB5dg-00035L-J8 for xen-users@lists.xen.org; Mon, 10 Sep 2012 15:11:04 +0000 X-Env-Sender: Ian.Campbell@citrix.com X-Msg-Ref: server-9.tower-27.messagelabs.com!1347289858!9128176!1 X-Originating-IP: [62.200.22.115] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogNjIuMjAwLjIyLjExNSA9PiAxMTIyODk=\n X-StarScan-Received: X-StarScan-Version: 6.6.1.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 30231 invoked from network); 10 Sep 2012 15:10:58 -0000 Received: from smtp.ctxuk.citrix.com (HELO SMTP.EU.CITRIX.COM) (62.200.22.115) by server-9.tower-27.messagelabs.com with RC4-SHA encrypted SMTP; 10 Sep 2012 15:10:58 -0000 X-IronPort-AV: E=Sophos;i="4.80,398,1344211200"; d="scan'208";a="14447637" Received: from lonpmailmx01.citrite.net ([10.30.203.162]) by LONPIPO01.EU.CITRIX.COM with ESMTP/TLS/RC4-MD5; 10 Sep 2012 15:10:54 +0000 Received: from [10.80.2.42] (10.80.2.42) by LONPMAILMX01.citrite.net (10.30.203.162) with Microsoft SMTP Server id 8.3.279.1; Mon, 10 Sep 2012 16:10:54 +0100 Message-ID: <1347289853.5305.105.camel@zakaz.uk.xensource.com> From: Ian Campbell To: Maik Brauer Date: Mon, 10 Sep 2012 16:10:53 +0100 In-Reply-To: <4957C391-6070-47C1-A2AC-991ED1C1766A@mbs-systems.net> References: <9F8FD2B0-450A-4A6E-A929-BA240ED1D997@mbs-systems.net> <1346746297.32462.37.camel@zakaz.uk.xensource.com> <1347266386.5305.17.camel@zakaz.uk.xensource.com> <4957C391-6070-47C1-A2AC-991ED1C1766A@mbs-systems.net> Organization: Citrix Systems, Inc. X-Mailer: Evolution 3.4.3-1 MIME-Version: 1.0 Cc: "xen-users@lists.xen.org" Subject: Re: [Xen-users] Dom0 crashed when rebooting whilst DomU are running X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org On Mon, 2012-09-10 at 16:00 +0100, Maik Brauer wrote: > On Sep 10, 2012, at 10:39 AM, Ian Campbell wrote: > > > On Sat, 2012-09-08 at 15:50 +0100, Maik Brauer wrote: > >> On Sep 4, 2012, at 10:11 AM, Ian Campbell wrote: > >> > >>> Could you not top post please, it makes it rather hard to follow the > >>> flow of the conversation. > >>> On Mon, 2012-09-03 at 18:10 +0100, Casey DeLorme wrote: > >>>> As stated, you can alias shutdown to do exactly what you need, it can > >>>> be as simple as a series of hard-coded operations to a complex custom > >>>> shell script that parses your domains and closes each with feedback. > >>> > >>> Xen ships the "xendomains" initscript which can halt guest on shutdown > >>> as well as automatically start specific guests on boot. It can also be > >>> configured to suspend/resume them or (I think) migrate them away. > >>> > >>> For diagnosing the crash itself more details will be required than were > >>> provided in the original post. Please see > >>> http://wiki.xen.org/wiki/Reporting_Bugs_against_Xen for some guidance. > >>> At a minimum we would need a capture (serial console or photo) of the > >>> crash backtrace. > >>> > >>> Ian. > >>> > >>> > >> I found out that it hangs during re-boot of dom0 when having more > >> Network interfaces involved, like: > >> vif = [ 'mac=06:46:AB:CC:11:01, ip=', '', '', > >> 'mac=06:04:AB:BB:11:03, bridge=VLAN20, script=vif-bridge', '', > >> 'mac=06:04:AB:BB:11:05, bridge=VLAN40, script=vif-bridge' ] > > > > 6 interfaces total, 3 of which have a random mac on each reboot and all > > get put on the default bridge? > > No, not really. The bridge is different for each interface. You have three lots of '' which will all go onto the same bridge AFAICT (whichever one is determined to be the default) > > If it is a hang then you might have some luck using hte magic sysrq keys > > to print lists of blocked tasks. I'm not sure in Squeeze but you might > > need to enable this as described in Documentation/sysrq.txt in the Linux > > source. > > > > Blocked tasks are listed with SysRQ-'w'. If you have serial console then > > 't' will list all task, but that list can be quite long so it is useless > > without a serial console. > > List is empty. SysRQ -w and SysRQ-t shows nothing at all. You might need to increase the log verbosity with SysRQ-9 first? > There is nothing running anymore. > It shows periodically: INFO: task xenwatch:12 blocked for more than 120 seconds What is the very last thing printed before this? > Seems that the xenwatch is blocking the reboot here, is that assumption correct? But strange enough that I can't > see any process anymore with the SysRQ -t or SysRQ -w The xenwatch thread ought to count as a process for at least the purposes of SysRQ-t if not -w. > > >> In the Logfile of /var/log/message you can find this as the last line: > >> Sep 8 15:44:28 rootsrv01 shutdown[2445]: shutting down for system reboot > >> Sep 8 15:44:31 rootsrv01 kernel: [ 73.716246] VLAN20: port 1(vif2.3) entering forwarding state > >> Sep 8 15:44:31 rootsrv01 kernel: [ 74.500111] VLAN40: port 1(vif2.5) entering forwarding state > >> Sep 8 15:44:34 rootsrv01 kernel: [ 77.317431] VLAN20: port 1(vif2.3) entering disabled state > >> Sep 8 15:44:34 rootsrv01 kernel: [ 77.317490] VLAN20: port 1(vif2.3) entering disabled state > >> Sep 8 15:44:36 rootsrv01 kernel: [ 79.368685] VLAN40: port 1(vif2.5) entering disabled state > >> Sep 8 15:44:36 rootsrv01 kernel: [ 79.369156] VLAN40: port 1(vif2.5) entering disabled state > >> Sep 8 15:44:37 rootsrv01 kernel: Kernel logging (proc) stopped. > >> Sep 8 15:44:37 rootsrv01 rsyslogd: [origin software="rsyslogd" swVersion="4.6.4" x-pid="890" x-info="http://www.rsyslog.com"] exiting on signal 15. > >> > >> In the /var/log/daemong.log you can find this message: > >> Sep 8 15:44:37 rootsrv01 acpid: exiting > >> Sep 8 15:44:37 rootsrv01 rpc.statd[750]: Caught signal 15, un-registering and exiting > > > > All the above (both message and daemon.log) look like normal parts of > > shutting down to me. > > > >> Sep 8 15:44:37 rootsrv01 udevd-work[2276]: '/etc/xen/scripts/vif-setup offline type_if=vif' unexpected exit with status 0x000f > > > > This might be worth following up on. > > When putting a "sleep 5" in stop section of the /etc/init.d/xendomains: > case "$1" in > start) > start > rc_status > if test -f $LOCKFILE; then rc_status -v; fi > ;; > > stop) > stop > rc_status -v > sleep 5 > ;; > > then the system shuts down as expected and is rebooting properly. > In the daemon.log file I couldn't find the error: Sep 8 15:44:37 rootsrv01 udevd-work[2276]: '/etc/xen/scripts/vif-setup offline type_if=vif' unexpected exit with status 0x000f > anymore. It seems that it disappeared after putting a delay inside. Could it be a race condition here during shutdown, with the udev-daemon?? It could be a race with the guests actually shuting down vs the rest of the initscripts running. Really the initscript ought to wait, the default at least with the script shipped with xen is to do so, by using shutdown --wait. can you confirm whether or not this is happening for you? Possibly someone is trying to talk to xenstore after xenstored has exited -- I expect that would cause the sorts of blocked for 120 messages you are seeing. _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Mon Sep 10 15:11:54 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Mon, 10 Sep 2012 15:11:54 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TB5di-00035f-CX; Mon, 10 Sep 2012 15:11:06 +0000 Received: from mail27.messagelabs.com ([193.109.254.147]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TB5dg-00035L-J8 for xen-users@lists.xen.org; Mon, 10 Sep 2012 15:11:04 +0000 X-Env-Sender: Ian.Campbell@citrix.com X-Msg-Ref: server-9.tower-27.messagelabs.com!1347289858!9128176!1 X-Originating-IP: [62.200.22.115] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogNjIuMjAwLjIyLjExNSA9PiAxMTIyODk=\n X-StarScan-Received: X-StarScan-Version: 6.6.1.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 30231 invoked from network); 10 Sep 2012 15:10:58 -0000 Received: from smtp.ctxuk.citrix.com (HELO SMTP.EU.CITRIX.COM) (62.200.22.115) by server-9.tower-27.messagelabs.com with RC4-SHA encrypted SMTP; 10 Sep 2012 15:10:58 -0000 X-IronPort-AV: E=Sophos;i="4.80,398,1344211200"; d="scan'208";a="14447637" Received: from lonpmailmx01.citrite.net ([10.30.203.162]) by LONPIPO01.EU.CITRIX.COM with ESMTP/TLS/RC4-MD5; 10 Sep 2012 15:10:54 +0000 Received: from [10.80.2.42] (10.80.2.42) by LONPMAILMX01.citrite.net (10.30.203.162) with Microsoft SMTP Server id 8.3.279.1; Mon, 10 Sep 2012 16:10:54 +0100 Message-ID: <1347289853.5305.105.camel@zakaz.uk.xensource.com> From: Ian Campbell To: Maik Brauer Date: Mon, 10 Sep 2012 16:10:53 +0100 In-Reply-To: <4957C391-6070-47C1-A2AC-991ED1C1766A@mbs-systems.net> References: <9F8FD2B0-450A-4A6E-A929-BA240ED1D997@mbs-systems.net> <1346746297.32462.37.camel@zakaz.uk.xensource.com> <1347266386.5305.17.camel@zakaz.uk.xensource.com> <4957C391-6070-47C1-A2AC-991ED1C1766A@mbs-systems.net> Organization: Citrix Systems, Inc. X-Mailer: Evolution 3.4.3-1 MIME-Version: 1.0 Cc: "xen-users@lists.xen.org" Subject: Re: [Xen-users] Dom0 crashed when rebooting whilst DomU are running X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org On Mon, 2012-09-10 at 16:00 +0100, Maik Brauer wrote: > On Sep 10, 2012, at 10:39 AM, Ian Campbell wrote: > > > On Sat, 2012-09-08 at 15:50 +0100, Maik Brauer wrote: > >> On Sep 4, 2012, at 10:11 AM, Ian Campbell wrote: > >> > >>> Could you not top post please, it makes it rather hard to follow the > >>> flow of the conversation. > >>> On Mon, 2012-09-03 at 18:10 +0100, Casey DeLorme wrote: > >>>> As stated, you can alias shutdown to do exactly what you need, it can > >>>> be as simple as a series of hard-coded operations to a complex custom > >>>> shell script that parses your domains and closes each with feedback. > >>> > >>> Xen ships the "xendomains" initscript which can halt guest on shutdown > >>> as well as automatically start specific guests on boot. It can also be > >>> configured to suspend/resume them or (I think) migrate them away. > >>> > >>> For diagnosing the crash itself more details will be required than were > >>> provided in the original post. Please see > >>> http://wiki.xen.org/wiki/Reporting_Bugs_against_Xen for some guidance. > >>> At a minimum we would need a capture (serial console or photo) of the > >>> crash backtrace. > >>> > >>> Ian. > >>> > >>> > >> I found out that it hangs during re-boot of dom0 when having more > >> Network interfaces involved, like: > >> vif = [ 'mac=06:46:AB:CC:11:01, ip=', '', '', > >> 'mac=06:04:AB:BB:11:03, bridge=VLAN20, script=vif-bridge', '', > >> 'mac=06:04:AB:BB:11:05, bridge=VLAN40, script=vif-bridge' ] > > > > 6 interfaces total, 3 of which have a random mac on each reboot and all > > get put on the default bridge? > > No, not really. The bridge is different for each interface. You have three lots of '' which will all go onto the same bridge AFAICT (whichever one is determined to be the default) > > If it is a hang then you might have some luck using hte magic sysrq keys > > to print lists of blocked tasks. I'm not sure in Squeeze but you might > > need to enable this as described in Documentation/sysrq.txt in the Linux > > source. > > > > Blocked tasks are listed with SysRQ-'w'. If you have serial console then > > 't' will list all task, but that list can be quite long so it is useless > > without a serial console. > > List is empty. SysRQ -w and SysRQ-t shows nothing at all. You might need to increase the log verbosity with SysRQ-9 first? > There is nothing running anymore. > It shows periodically: INFO: task xenwatch:12 blocked for more than 120 seconds What is the very last thing printed before this? > Seems that the xenwatch is blocking the reboot here, is that assumption correct? But strange enough that I can't > see any process anymore with the SysRQ -t or SysRQ -w The xenwatch thread ought to count as a process for at least the purposes of SysRQ-t if not -w. > > >> In the Logfile of /var/log/message you can find this as the last line: > >> Sep 8 15:44:28 rootsrv01 shutdown[2445]: shutting down for system reboot > >> Sep 8 15:44:31 rootsrv01 kernel: [ 73.716246] VLAN20: port 1(vif2.3) entering forwarding state > >> Sep 8 15:44:31 rootsrv01 kernel: [ 74.500111] VLAN40: port 1(vif2.5) entering forwarding state > >> Sep 8 15:44:34 rootsrv01 kernel: [ 77.317431] VLAN20: port 1(vif2.3) entering disabled state > >> Sep 8 15:44:34 rootsrv01 kernel: [ 77.317490] VLAN20: port 1(vif2.3) entering disabled state > >> Sep 8 15:44:36 rootsrv01 kernel: [ 79.368685] VLAN40: port 1(vif2.5) entering disabled state > >> Sep 8 15:44:36 rootsrv01 kernel: [ 79.369156] VLAN40: port 1(vif2.5) entering disabled state > >> Sep 8 15:44:37 rootsrv01 kernel: Kernel logging (proc) stopped. > >> Sep 8 15:44:37 rootsrv01 rsyslogd: [origin software="rsyslogd" swVersion="4.6.4" x-pid="890" x-info="http://www.rsyslog.com"] exiting on signal 15. > >> > >> In the /var/log/daemong.log you can find this message: > >> Sep 8 15:44:37 rootsrv01 acpid: exiting > >> Sep 8 15:44:37 rootsrv01 rpc.statd[750]: Caught signal 15, un-registering and exiting > > > > All the above (both message and daemon.log) look like normal parts of > > shutting down to me. > > > >> Sep 8 15:44:37 rootsrv01 udevd-work[2276]: '/etc/xen/scripts/vif-setup offline type_if=vif' unexpected exit with status 0x000f > > > > This might be worth following up on. > > When putting a "sleep 5" in stop section of the /etc/init.d/xendomains: > case "$1" in > start) > start > rc_status > if test -f $LOCKFILE; then rc_status -v; fi > ;; > > stop) > stop > rc_status -v > sleep 5 > ;; > > then the system shuts down as expected and is rebooting properly. > In the daemon.log file I couldn't find the error: Sep 8 15:44:37 rootsrv01 udevd-work[2276]: '/etc/xen/scripts/vif-setup offline type_if=vif' unexpected exit with status 0x000f > anymore. It seems that it disappeared after putting a delay inside. Could it be a race condition here during shutdown, with the udev-daemon?? It could be a race with the guests actually shuting down vs the rest of the initscripts running. Really the initscript ought to wait, the default at least with the script shipped with xen is to do so, by using shutdown --wait. can you confirm whether or not this is happening for you? Possibly someone is trying to talk to xenstore after xenstored has exited -- I expect that would cause the sorts of blocked for 120 messages you are seeing. _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Mon Sep 10 17:04:43 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Mon, 10 Sep 2012 17:04:43 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TB7Oi-0006JM-19; Mon, 10 Sep 2012 17:03:44 +0000 Received: from mail27.messagelabs.com ([193.109.254.147]) by lists.xen.org with smtp (Exim 4.72) (envelope-from ) id 1TB7Og-0006JH-Q0 for xen-users@lists.xen.org; Mon, 10 Sep 2012 17:03:43 +0000 X-Env-Sender: phenix@web.de X-Msg-Ref: server-4.tower-27.messagelabs.com!1347296616!9854572!1 X-Originating-IP: [212.227.17.11] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogMjEyLjIyNy4xNy4xMSA9PiAxNzMzMQ==\n X-StarScan-Received: X-StarScan-Version: 6.6.1.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 1785 invoked from network); 10 Sep 2012 17:03:36 -0000 Received: from mout.web.de (HELO mout.web.de) (212.227.17.11) by server-4.tower-27.messagelabs.com with SMTP; 10 Sep 2012 17:03:36 -0000 Received: from [10.10.10.2] ([86.103.239.138]) by smtp.web.de (mrweb002) with ESMTPSA (Nemesis) id 0MVcvn-1T3DYF1wdj-00YnkM for ; Mon, 10 Sep 2012 19:03:36 +0200 Message-ID: <504E1D66.6030502@web.de> Date: Mon, 10 Sep 2012 19:03:34 +0200 From: Tilo Peter User-Agent: Mozilla/5.0 (X11; Linux i686; rv:15.0) Gecko/20120827 Thunderbird/15.0 MIME-Version: 1.0 To: "xen-users@lists.xen.org" References: In-Reply-To: X-Enigmail-Version: 1.4.4 X-Provags-ID: V02:K0:Panq7j9Z2tQ5molpGbNNwgK7PfsHh6XjByKZ5qwb83p HvtKSlOFjxjBxg2vLAaRSEo7ucQfJvv5sFw5BO4SYz/K1WjNSk NtngyDRfVnQDnginY+BEXhRt3S7qes/9zOlZF+8bORwhChqsRc 7TmDhwm36ipir8u4puoKBNeI/23NlUDTpFDsC3Jz+qHogKf7e0 u0/XRhzx6oWtuNT0SfpvA== Subject: [Xen-users] xen-pciback always gives error: Unknown parameter `1)' X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org Hi, I tried running debian wheezy amd64 with the debian stock kernel 3.2 and xen 4.2 rc3. Compiling ran through without any errors and xen boots up without problems. But xen-pciback always produces the same error message: # lsmod | grep pci pci_stub 12429 0 # modprobe xen-pciback ERROR: could not insert 'xen_pciback': Unknown symbol in module, or unknown parameter (see dmesg) # dmesg | tail -n 1 [ 3687.470124] xen_pciback: Unknown parameter `1)' This message always appears when I try to load xen-pciback, whenever I give a "hide=(0000:01.00.0)" parameter or not, or in general whatever I do. Since I couldn't find any help on this topic so far, I hope for some idea for a solution here! Best Regards, Tilo _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Mon Sep 10 17:04:43 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Mon, 10 Sep 2012 17:04:43 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TB7Oi-0006JM-19; Mon, 10 Sep 2012 17:03:44 +0000 Received: from mail27.messagelabs.com ([193.109.254.147]) by lists.xen.org with smtp (Exim 4.72) (envelope-from ) id 1TB7Og-0006JH-Q0 for xen-users@lists.xen.org; Mon, 10 Sep 2012 17:03:43 +0000 X-Env-Sender: phenix@web.de X-Msg-Ref: server-4.tower-27.messagelabs.com!1347296616!9854572!1 X-Originating-IP: [212.227.17.11] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogMjEyLjIyNy4xNy4xMSA9PiAxNzMzMQ==\n X-StarScan-Received: X-StarScan-Version: 6.6.1.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 1785 invoked from network); 10 Sep 2012 17:03:36 -0000 Received: from mout.web.de (HELO mout.web.de) (212.227.17.11) by server-4.tower-27.messagelabs.com with SMTP; 10 Sep 2012 17:03:36 -0000 Received: from [10.10.10.2] ([86.103.239.138]) by smtp.web.de (mrweb002) with ESMTPSA (Nemesis) id 0MVcvn-1T3DYF1wdj-00YnkM for ; Mon, 10 Sep 2012 19:03:36 +0200 Message-ID: <504E1D66.6030502@web.de> Date: Mon, 10 Sep 2012 19:03:34 +0200 From: Tilo Peter User-Agent: Mozilla/5.0 (X11; Linux i686; rv:15.0) Gecko/20120827 Thunderbird/15.0 MIME-Version: 1.0 To: "xen-users@lists.xen.org" References: In-Reply-To: X-Enigmail-Version: 1.4.4 X-Provags-ID: V02:K0:Panq7j9Z2tQ5molpGbNNwgK7PfsHh6XjByKZ5qwb83p HvtKSlOFjxjBxg2vLAaRSEo7ucQfJvv5sFw5BO4SYz/K1WjNSk NtngyDRfVnQDnginY+BEXhRt3S7qes/9zOlZF+8bORwhChqsRc 7TmDhwm36ipir8u4puoKBNeI/23NlUDTpFDsC3Jz+qHogKf7e0 u0/XRhzx6oWtuNT0SfpvA== Subject: [Xen-users] xen-pciback always gives error: Unknown parameter `1)' X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org Hi, I tried running debian wheezy amd64 with the debian stock kernel 3.2 and xen 4.2 rc3. Compiling ran through without any errors and xen boots up without problems. But xen-pciback always produces the same error message: # lsmod | grep pci pci_stub 12429 0 # modprobe xen-pciback ERROR: could not insert 'xen_pciback': Unknown symbol in module, or unknown parameter (see dmesg) # dmesg | tail -n 1 [ 3687.470124] xen_pciback: Unknown parameter `1)' This message always appears when I try to load xen-pciback, whenever I give a "hide=(0000:01.00.0)" parameter or not, or in general whatever I do. Since I couldn't find any help on this topic so far, I hope for some idea for a solution here! Best Regards, Tilo _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Mon Sep 10 18:33:47 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Mon, 10 Sep 2012 18:33:47 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TB8mv-00082Y-IH; Mon, 10 Sep 2012 18:32:49 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TB8mu-00082N-2b for xen-users@lists.xen.org; Mon, 10 Sep 2012 18:32:48 +0000 Received: from [85.158.139.83:38562] by server-12.bemta-5.messagelabs.com id 11/A3-18300-F423E405; Mon, 10 Sep 2012 18:32:47 +0000 X-Env-Sender: bunkertor@tiscali.it X-Msg-Ref: server-5.tower-182.messagelabs.com!1347301966!29415128!1 X-Originating-IP: [213.205.33.245] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogMjEzLjIwNS4zMy4yNDUgPT4gMjAzMjU=\n, ML_RADAR_SPEW_LINKS_14,spamassassin: X-StarScan-Received: X-StarScan-Version: 6.6.1.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 12229 invoked from network); 10 Sep 2012 18:32:46 -0000 Received: from santino.mail.tiscali.it (HELO santino.mail.tiscali.it) (213.205.33.245) by server-5.tower-182.messagelabs.com with SMTP; 10 Sep 2012 18:32:46 -0000 Received: from [172.16.1.180] ([78.13.188.52]) by santino.mail.tiscali.it with id xWYm1j00118G0wm01WYmN4; Mon, 10 Sep 2012 20:32:46 +0200 Message-ID: <504E324D.80005@tiscali.it> Date: Mon, 10 Sep 2012 20:32:45 +0200 From: bunkertor User-Agent: Mozilla/5.0 (Windows NT 5.1; rv:11.0) Gecko/20120327 Thunderbird/11.0.1 MIME-Version: 1.0 To: xen-users@lists.xen.org References: <504E10DA.6040603@tiscali.it> In-Reply-To: <504E10DA.6040603@tiscali.it> X-Forwarded-Message-Id: <504E10DA.6040603@tiscali.it> Subject: [Xen-users] Fwd: [Xen-devel] grub error 28 X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset="us-ascii"; Format="flowed" Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org hi all i compiled by myself xen-unstable from hg repo (changeset: 25835:c70d70d85306) but i'm facing a problem when i try to boot with xen kernel: Error 28 Selected item can not fit into memory. i'm newbie and i cannot understand where i fail... here's the error (bad...) ================================================================ [root@xen-02 xen-unstable]# grub Probing devices to guess BIOS drives. This may take a long time. GNU GRUB version 0.97 (640K lower / 3072K upper memory) [ Minimal BASH-like line editing is supported. For the first word, TAB lists possible command completions. Anywhere else TAB lists the possible completions of a device/filename.] grub> root (hd0,0) root (hd0,0) Filesystem type is ext2fs, partition type 0x83 grub> kernel /xen.gz kernel /xen.gz [Multiboot-elf,<0x964000:0x1a6db8:0x54248>(bad) Error 28: Selected item cannot fit into memory ================================================================ and here are my specs: ================================================================ [root@xen-02 xen-unstable]# uname -r 2.6.32-279.5.2.el6.x86_64 [root@xen-02 xen-unstable]# cat /etc/redhat-release CentOS release 6.3 (Final) [root@xen-02 xen-unstable]# [root@xen-02 xen-unstable]# cat /proc/meminfo MemTotal: 16029352 kB MemFree: 15720112 kB Buffers: 11488 kB Cached: 47264 kB SwapCached: 0 kB Active: 23736 kB Inactive: 40804 kB Active(anon): 5924 kB Inactive(anon): 5628 kB Active(file): 17812 kB Inactive(file): 35176 kB Unevictable: 0 kB Mlocked: 0 kB SwapTotal: 32767992 kB SwapFree: 32767992 kB Dirty: 0 kB Writeback: 0 kB AnonPages: 5776 kB Mapped: 5768 kB Shmem: 5764 kB Slab: 36836 kB SReclaimable: 10224 kB SUnreclaim: 26612 kB KernelStack: 1224 kB PageTables: 1128 kB NFS_Unstable: 0 kB Bounce: 0 kB WritebackTmp: 0 kB CommitLimit: 40782668 kB Committed_AS: 59656 kB VmallocTotal: 34359738367 kB VmallocUsed: 392120 kB VmallocChunk: 34359341780 kB HardwareCorrupted: 0 kB AnonHugePages: 0 kB HugePages_Total: 0 HugePages_Free: 0 HugePages_Rsvd: 0 HugePages_Surp: 0 Hugepagesize: 2048 kB DirectMap4k: 8192 kB DirectMap2M: 16480256 kB [root@xen-02 xen-unstable]# cat /proc/cpuinfo processor : 0 vendor_id : GenuineIntel cpu family : 6 model : 42 model name : Intel(R) Core(TM) i5-2400 CPU @ 3.10GHz stepping : 7 cpu MHz : 3092.749 cache size : 6144 KB physical id : 0 siblings : 4 core id : 0 cpu cores : 4 apicid : 0 initial apicid : 0 fpu : yes fpu_exception : yes cpuid level : 13 wp : yes flags : fpu vme de pse tsc msr pae mce cx8 apic mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx rdtscp lm constant_tsc arch_perfmon pebs bts rep_good xtopology nonstop_tsc aperfmperf pni pclmulqdq dtes64 monitor ds_cpl vmx smx est tm2 ssse3 cx16 xtpr pdcm sse4_1 sse4_2 x2apic popcnt aes xsave avx lahf_lm ida arat epb xsaveopt pln pts dts tpr_shadow vnmi flexpriority ept vpid bogomips : 6185.49 clflush size : 64 cache_alignment : 64 address sizes : 36 bits physical, 48 bits virtual power management: ..... ..... ================================================================= [root@xen-02 xen-unstable]# ls -lh /boot/ totale 247M -rw-r--r--. 1 root root 100K 24 ago 03:31 config-2.6.32-279.5.2.el6.x86_64 -rw-r--r--. 1 root root 100K 22 giu 14:44 config-2.6.32-279.el6.x86_64 -rw-r--r--. 1 root root 114K 9 set 02:09 config-3.1.0-rc9 drwxr-xr-x. 3 root root 4,0K 9 set 00:16 efi drwxr-xr-x. 2 root root 4,0K 9 set 12:11 grub -rw-r--r--. 1 root root 23M 9 set 01:16 initramfs-2.6.32-279.5.2.el6.x86_64.img -rw-r--r--. 1 root root 23M 9 set 00:17 initramfs-2.6.32-279.el6.x86_64.img -rw-r--r--. 1 root root 154M 9 set 02:31 initramfs-3.1.0-rc9.img drwx------. 2 root root 16K 9 set 00:13 lost+found -rw-r--r--. 1 root root 176K 24 ago 03:32 symvers-2.6.32-279.5.2.el6.x86_64.gz -rw-r--r--. 1 root root 175K 22 giu 14:45 symvers-2.6.32-279.el6.x86_64.gz -rw-r--r--. 1 root root 2,3M 24 ago 03:31 System.map-2.6.32-279.5.2.el6.x86_64 -rw-r--r--. 1 root root 2,3M 22 giu 14:44 System.map-2.6.32-279.el6.x86_64 -rw-r--r--. 1 root root 2,4M 9 set 02:12 System.map-3.1.0-rc9 -rwxr-xr-x. 1 root root 3,9M 24 ago 03:31 vmlinuz-2.6.32-279.5.2.el6.x86_64 -rwxr-xr-x. 1 root root 3,9M 22 giu 14:44 vmlinuz-2.6.32-279.el6.x86_64 -rwxr-xr-x. 1 root root 3,9M 9 set 02:12 vmlinuz-3.1.0-rc9 -rw-r--r--. 1 root root 776K 9 set 11:42 xen-4.2.0-rc2.gz -rw-r--r--. 1 root root 779K 9 set 01:01 xen-4.2.0-rc4-pre.gz lrwxrwxrwx. 1 root root 16 9 set 11:42 xen-4.2.gz -> xen-4.2.0-rc2.gz lrwxrwxrwx. 1 root root 16 9 set 11:42 xen-4.gz -> xen-4.2.0-rc2.gz lrwxrwxrwx. 1 root root 16 9 set 11:42 xen.gz -> xen-4.2.0-rc2.gz -rw-r--r--. 1 root root 13M 9 set 11:42 xen-syms-4.2.0-rc2 -rw-r--r--. 1 root root 14M 9 set 01:01 xen-syms-4.2.0-rc4-pre ================================================================= title Xen 4.2.0-rc4-pre with linux 3.1.0-rc9 pvops root (hd0,0) kernel /xen.gz dom0_mem=2048M loglvl=all guest_loglvl=all module /vmlinuz-3.1.0-rc9 ro root=/dev/mapper/vg_xen02-LogVol00 LANG=it_IT.UTF-8 rd_NO_LUKS KEYBOARDTYPE=pc KEYTABLE=it rd_NO_MD rd_LVM_LV=vg_xen02/LogVol00 SYSFONT=latarcyrheb-sun16 crashkernel=auto rd_LVM_LV=vg_xen02/LogVol01 rd_NO_DM rhgb quiet nomodeset module /initramfs-3.1.0-rc9.img ================================================================= [root@xen-02 xen-unstable]# dmesg | grep BIOS BIOS-provided physical RAM map: BIOS-e820: 0000000000000000 - 000000000009ec00 (usable) BIOS-e820: 000000000009ec00 - 00000000000a0000 (reserved) BIOS-e820: 00000000000e0000 - 0000000000100000 (reserved) BIOS-e820: 0000000000100000 - 0000000020000000 (usable) BIOS-e820: 0000000020000000 - 0000000020200000 (reserved) BIOS-e820: 0000000020200000 - 0000000040000000 (usable) BIOS-e820: 0000000040000000 - 0000000040200000 (reserved) BIOS-e820: 0000000040200000 - 00000000cd86f000 (usable) BIOS-e820: 00000000cd86f000 - 00000000ce01a000 (reserved) BIOS-e820: 00000000ce01a000 - 00000000ce29a000 (ACPI NVS) BIOS-e820: 00000000ce29a000 - 00000000ce29f000 (ACPI data) BIOS-e820: 00000000ce29f000 - 00000000ce2e2000 (ACPI NVS) BIOS-e820: 00000000ce2e2000 - 00000000cec3f000 (usable) BIOS-e820: 00000000cec3f000 - 00000000ceff2000 (reserved) BIOS-e820: 00000000ceff2000 - 00000000cf000000 (usable) BIOS-e820: 00000000cf800000 - 00000000dfa00000 (reserved) BIOS-e820: 00000000f8000000 - 00000000fc000000 (reserved) BIOS-e820: 00000000fec00000 - 00000000fec01000 (reserved) BIOS-e820: 00000000fed00000 - 00000000fed04000 (reserved) BIOS-e820: 00000000fed1c000 - 00000000fed20000 (reserved) BIOS-e820: 00000000fee00000 - 00000000fee01000 (reserved) BIOS-e820: 00000000ff000000 - 0000000100000000 (reserved) BIOS-e820: 0000000100000000 - 000000041f600000 (usable) SMBIOS version 2.7 @ 0xF0480 DMI: To Be Filled By O.E.M. To Be Filled By O.E.M./Z68 Extreme4, BIOS P2.20 06/29/2012 AMI BIOS detected: BIOS may corrupt low RAM, working around it. #0 [0000000000 - 0000001000] BIOS data page ==> [0000000000 - 0000001000] #4 [000009ec00 - 0000100000] BIOS reserved ==> [000009ec00 - 0000100000] ================================================================= any help will be appreciated. thanks in advance. _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Mon Sep 10 18:33:47 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Mon, 10 Sep 2012 18:33:47 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TB8mv-00082Y-IH; Mon, 10 Sep 2012 18:32:49 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TB8mu-00082N-2b for xen-users@lists.xen.org; Mon, 10 Sep 2012 18:32:48 +0000 Received: from [85.158.139.83:38562] by server-12.bemta-5.messagelabs.com id 11/A3-18300-F423E405; Mon, 10 Sep 2012 18:32:47 +0000 X-Env-Sender: bunkertor@tiscali.it X-Msg-Ref: server-5.tower-182.messagelabs.com!1347301966!29415128!1 X-Originating-IP: [213.205.33.245] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogMjEzLjIwNS4zMy4yNDUgPT4gMjAzMjU=\n, ML_RADAR_SPEW_LINKS_14,spamassassin: X-StarScan-Received: X-StarScan-Version: 6.6.1.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 12229 invoked from network); 10 Sep 2012 18:32:46 -0000 Received: from santino.mail.tiscali.it (HELO santino.mail.tiscali.it) (213.205.33.245) by server-5.tower-182.messagelabs.com with SMTP; 10 Sep 2012 18:32:46 -0000 Received: from [172.16.1.180] ([78.13.188.52]) by santino.mail.tiscali.it with id xWYm1j00118G0wm01WYmN4; Mon, 10 Sep 2012 20:32:46 +0200 Message-ID: <504E324D.80005@tiscali.it> Date: Mon, 10 Sep 2012 20:32:45 +0200 From: bunkertor User-Agent: Mozilla/5.0 (Windows NT 5.1; rv:11.0) Gecko/20120327 Thunderbird/11.0.1 MIME-Version: 1.0 To: xen-users@lists.xen.org References: <504E10DA.6040603@tiscali.it> In-Reply-To: <504E10DA.6040603@tiscali.it> X-Forwarded-Message-Id: <504E10DA.6040603@tiscali.it> Subject: [Xen-users] Fwd: [Xen-devel] grub error 28 X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset="us-ascii"; Format="flowed" Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org hi all i compiled by myself xen-unstable from hg repo (changeset: 25835:c70d70d85306) but i'm facing a problem when i try to boot with xen kernel: Error 28 Selected item can not fit into memory. i'm newbie and i cannot understand where i fail... here's the error (bad...) ================================================================ [root@xen-02 xen-unstable]# grub Probing devices to guess BIOS drives. This may take a long time. GNU GRUB version 0.97 (640K lower / 3072K upper memory) [ Minimal BASH-like line editing is supported. For the first word, TAB lists possible command completions. Anywhere else TAB lists the possible completions of a device/filename.] grub> root (hd0,0) root (hd0,0) Filesystem type is ext2fs, partition type 0x83 grub> kernel /xen.gz kernel /xen.gz [Multiboot-elf,<0x964000:0x1a6db8:0x54248>(bad) Error 28: Selected item cannot fit into memory ================================================================ and here are my specs: ================================================================ [root@xen-02 xen-unstable]# uname -r 2.6.32-279.5.2.el6.x86_64 [root@xen-02 xen-unstable]# cat /etc/redhat-release CentOS release 6.3 (Final) [root@xen-02 xen-unstable]# [root@xen-02 xen-unstable]# cat /proc/meminfo MemTotal: 16029352 kB MemFree: 15720112 kB Buffers: 11488 kB Cached: 47264 kB SwapCached: 0 kB Active: 23736 kB Inactive: 40804 kB Active(anon): 5924 kB Inactive(anon): 5628 kB Active(file): 17812 kB Inactive(file): 35176 kB Unevictable: 0 kB Mlocked: 0 kB SwapTotal: 32767992 kB SwapFree: 32767992 kB Dirty: 0 kB Writeback: 0 kB AnonPages: 5776 kB Mapped: 5768 kB Shmem: 5764 kB Slab: 36836 kB SReclaimable: 10224 kB SUnreclaim: 26612 kB KernelStack: 1224 kB PageTables: 1128 kB NFS_Unstable: 0 kB Bounce: 0 kB WritebackTmp: 0 kB CommitLimit: 40782668 kB Committed_AS: 59656 kB VmallocTotal: 34359738367 kB VmallocUsed: 392120 kB VmallocChunk: 34359341780 kB HardwareCorrupted: 0 kB AnonHugePages: 0 kB HugePages_Total: 0 HugePages_Free: 0 HugePages_Rsvd: 0 HugePages_Surp: 0 Hugepagesize: 2048 kB DirectMap4k: 8192 kB DirectMap2M: 16480256 kB [root@xen-02 xen-unstable]# cat /proc/cpuinfo processor : 0 vendor_id : GenuineIntel cpu family : 6 model : 42 model name : Intel(R) Core(TM) i5-2400 CPU @ 3.10GHz stepping : 7 cpu MHz : 3092.749 cache size : 6144 KB physical id : 0 siblings : 4 core id : 0 cpu cores : 4 apicid : 0 initial apicid : 0 fpu : yes fpu_exception : yes cpuid level : 13 wp : yes flags : fpu vme de pse tsc msr pae mce cx8 apic mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx rdtscp lm constant_tsc arch_perfmon pebs bts rep_good xtopology nonstop_tsc aperfmperf pni pclmulqdq dtes64 monitor ds_cpl vmx smx est tm2 ssse3 cx16 xtpr pdcm sse4_1 sse4_2 x2apic popcnt aes xsave avx lahf_lm ida arat epb xsaveopt pln pts dts tpr_shadow vnmi flexpriority ept vpid bogomips : 6185.49 clflush size : 64 cache_alignment : 64 address sizes : 36 bits physical, 48 bits virtual power management: ..... ..... ================================================================= [root@xen-02 xen-unstable]# ls -lh /boot/ totale 247M -rw-r--r--. 1 root root 100K 24 ago 03:31 config-2.6.32-279.5.2.el6.x86_64 -rw-r--r--. 1 root root 100K 22 giu 14:44 config-2.6.32-279.el6.x86_64 -rw-r--r--. 1 root root 114K 9 set 02:09 config-3.1.0-rc9 drwxr-xr-x. 3 root root 4,0K 9 set 00:16 efi drwxr-xr-x. 2 root root 4,0K 9 set 12:11 grub -rw-r--r--. 1 root root 23M 9 set 01:16 initramfs-2.6.32-279.5.2.el6.x86_64.img -rw-r--r--. 1 root root 23M 9 set 00:17 initramfs-2.6.32-279.el6.x86_64.img -rw-r--r--. 1 root root 154M 9 set 02:31 initramfs-3.1.0-rc9.img drwx------. 2 root root 16K 9 set 00:13 lost+found -rw-r--r--. 1 root root 176K 24 ago 03:32 symvers-2.6.32-279.5.2.el6.x86_64.gz -rw-r--r--. 1 root root 175K 22 giu 14:45 symvers-2.6.32-279.el6.x86_64.gz -rw-r--r--. 1 root root 2,3M 24 ago 03:31 System.map-2.6.32-279.5.2.el6.x86_64 -rw-r--r--. 1 root root 2,3M 22 giu 14:44 System.map-2.6.32-279.el6.x86_64 -rw-r--r--. 1 root root 2,4M 9 set 02:12 System.map-3.1.0-rc9 -rwxr-xr-x. 1 root root 3,9M 24 ago 03:31 vmlinuz-2.6.32-279.5.2.el6.x86_64 -rwxr-xr-x. 1 root root 3,9M 22 giu 14:44 vmlinuz-2.6.32-279.el6.x86_64 -rwxr-xr-x. 1 root root 3,9M 9 set 02:12 vmlinuz-3.1.0-rc9 -rw-r--r--. 1 root root 776K 9 set 11:42 xen-4.2.0-rc2.gz -rw-r--r--. 1 root root 779K 9 set 01:01 xen-4.2.0-rc4-pre.gz lrwxrwxrwx. 1 root root 16 9 set 11:42 xen-4.2.gz -> xen-4.2.0-rc2.gz lrwxrwxrwx. 1 root root 16 9 set 11:42 xen-4.gz -> xen-4.2.0-rc2.gz lrwxrwxrwx. 1 root root 16 9 set 11:42 xen.gz -> xen-4.2.0-rc2.gz -rw-r--r--. 1 root root 13M 9 set 11:42 xen-syms-4.2.0-rc2 -rw-r--r--. 1 root root 14M 9 set 01:01 xen-syms-4.2.0-rc4-pre ================================================================= title Xen 4.2.0-rc4-pre with linux 3.1.0-rc9 pvops root (hd0,0) kernel /xen.gz dom0_mem=2048M loglvl=all guest_loglvl=all module /vmlinuz-3.1.0-rc9 ro root=/dev/mapper/vg_xen02-LogVol00 LANG=it_IT.UTF-8 rd_NO_LUKS KEYBOARDTYPE=pc KEYTABLE=it rd_NO_MD rd_LVM_LV=vg_xen02/LogVol00 SYSFONT=latarcyrheb-sun16 crashkernel=auto rd_LVM_LV=vg_xen02/LogVol01 rd_NO_DM rhgb quiet nomodeset module /initramfs-3.1.0-rc9.img ================================================================= [root@xen-02 xen-unstable]# dmesg | grep BIOS BIOS-provided physical RAM map: BIOS-e820: 0000000000000000 - 000000000009ec00 (usable) BIOS-e820: 000000000009ec00 - 00000000000a0000 (reserved) BIOS-e820: 00000000000e0000 - 0000000000100000 (reserved) BIOS-e820: 0000000000100000 - 0000000020000000 (usable) BIOS-e820: 0000000020000000 - 0000000020200000 (reserved) BIOS-e820: 0000000020200000 - 0000000040000000 (usable) BIOS-e820: 0000000040000000 - 0000000040200000 (reserved) BIOS-e820: 0000000040200000 - 00000000cd86f000 (usable) BIOS-e820: 00000000cd86f000 - 00000000ce01a000 (reserved) BIOS-e820: 00000000ce01a000 - 00000000ce29a000 (ACPI NVS) BIOS-e820: 00000000ce29a000 - 00000000ce29f000 (ACPI data) BIOS-e820: 00000000ce29f000 - 00000000ce2e2000 (ACPI NVS) BIOS-e820: 00000000ce2e2000 - 00000000cec3f000 (usable) BIOS-e820: 00000000cec3f000 - 00000000ceff2000 (reserved) BIOS-e820: 00000000ceff2000 - 00000000cf000000 (usable) BIOS-e820: 00000000cf800000 - 00000000dfa00000 (reserved) BIOS-e820: 00000000f8000000 - 00000000fc000000 (reserved) BIOS-e820: 00000000fec00000 - 00000000fec01000 (reserved) BIOS-e820: 00000000fed00000 - 00000000fed04000 (reserved) BIOS-e820: 00000000fed1c000 - 00000000fed20000 (reserved) BIOS-e820: 00000000fee00000 - 00000000fee01000 (reserved) BIOS-e820: 00000000ff000000 - 0000000100000000 (reserved) BIOS-e820: 0000000100000000 - 000000041f600000 (usable) SMBIOS version 2.7 @ 0xF0480 DMI: To Be Filled By O.E.M. To Be Filled By O.E.M./Z68 Extreme4, BIOS P2.20 06/29/2012 AMI BIOS detected: BIOS may corrupt low RAM, working around it. #0 [0000000000 - 0000001000] BIOS data page ==> [0000000000 - 0000001000] #4 [000009ec00 - 0000100000] BIOS reserved ==> [000009ec00 - 0000100000] ================================================================= any help will be appreciated. thanks in advance. _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Mon Sep 10 19:14:55 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Mon, 10 Sep 2012 19:14:55 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TB9Qn-0000Hl-1z; Mon, 10 Sep 2012 19:14:01 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TB9Qk-0000Hg-MN for xen-users@lists.xen.org; Mon, 10 Sep 2012 19:13:59 +0000 Received: from [85.158.139.83:25393] by server-3.bemta-5.messagelabs.com id 06/4E-21836-5FB3E405; Mon, 10 Sep 2012 19:13:57 +0000 X-Env-Sender: cdelorme@gmail.com X-Msg-Ref: server-15.tower-182.messagelabs.com!1347304434!27494616!1 X-Originating-IP: [209.85.214.173] X-SpamReason: No, hits=0.9 required=7.0 tests=BODY_RANDOM_LONG, HTML_30_40, HTML_MESSAGE, ML_RADAR_SPEW_LINKS_14, RCVD_BY_IP, spamassassin: X-StarScan-Received: X-StarScan-Version: 6.6.1.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 21611 invoked from network); 10 Sep 2012 19:13:55 -0000 Received: from mail-ob0-f173.google.com (HELO mail-ob0-f173.google.com) (209.85.214.173) by server-15.tower-182.messagelabs.com with RC4-SHA encrypted SMTP; 10 Sep 2012 19:13:55 -0000 Received: by obbta14 with SMTP id ta14so4611905obb.32 for ; Mon, 10 Sep 2012 12:13:53 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=DxTfd5rPj5FeB/oC111Y4FIcubZ6PQiVu4da7H3928I=; b=J3txwlqrUXeTtXxqDgCS8wpuIiWwdT5QpAsHPsp5QJbmYBAp7CQ2NRIgFC6Ojs0yka GujgC3HEBhsf5ciE4kegypinuTVKkboll0E6R3SwOLGBT7hgXuv3/Vawk/dt2a1g6Gq4 5JZCK46pPypPuPoPkdjBLvsublPhlYPgoozNVkzNEmhiCThJsv4Zxk6QubKyB7fp0+g/ UDOEubB7lnfalaLg5RDtgqnqW2LEGrK8XPvJm8ihnexDEWGK2mb9D5ZDsXkBLWg0aWI4 ogRPwy8ookv5AIoUKCaJ8jVkwVjyjsmbGFas0hDKSxwGqXDxKZQsgkRYHpuQ3tsTkd5n YDJw== MIME-Version: 1.0 Received: by 10.60.169.8 with SMTP id aa8mr15250661oec.109.1347304433797; Mon, 10 Sep 2012 12:13:53 -0700 (PDT) Received: by 10.76.115.197 with HTTP; Mon, 10 Sep 2012 12:13:53 -0700 (PDT) In-Reply-To: <504E1D66.6030502@web.de> References: <504E1D66.6030502@web.de> Date: Mon, 10 Sep 2012 15:13:53 -0400 Message-ID: From: Casey DeLorme To: Tilo Peter Cc: "xen-users@lists.xen.org" Subject: Re: [Xen-users] xen-pciback always gives error: Unknown parameter `1)' X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============8772633522200577697==" Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org --===============8772633522200577697== Content-Type: multipart/alternative; boundary=bcaec54a35ca2e4b5904c95dc2bd --bcaec54a35ca2e4b5904c95dc2bd Content-Type: text/plain; charset=ISO-8859-1 If you are using the stock kernel and pciback as a module, then you have to use live binding, not grub. Alternatively, rebuild the kernel with pciback built-in (not as a module) and that will allow you to use grub. Supposedly you can rebuild the initrd image without recompiling the whole kernel, if live binding isn't appealing then I would investigate that. On Mon, Sep 10, 2012 at 1:03 PM, Tilo Peter wrote: > Hi, > I tried running debian wheezy amd64 with the debian stock kernel 3.2 and > xen 4.2 rc3. Compiling ran through without any errors and xen boots up > without problems. > > But xen-pciback always produces the same error message: > > # lsmod | grep pci > pci_stub 12429 0 > # modprobe xen-pciback > ERROR: could not insert 'xen_pciback': Unknown symbol in module, or > unknown parameter (see dmesg) > # dmesg | tail -n 1 > [ 3687.470124] xen_pciback: Unknown parameter `1)' > > > This message always appears when I try to load xen-pciback, whenever I > give a "hide=(0000:01.00.0)" parameter or not, or in general whatever I do. > > Since I couldn't find any help on this topic so far, I hope for some > idea for a solution here! > > > Best Regards, > Tilo > > > _______________________________________________ > Xen-users mailing list > Xen-users@lists.xen.org > http://lists.xen.org/xen-users > --bcaec54a35ca2e4b5904c95dc2bd Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable
If you are using the stock kernel and pciback as a module, then you ha= ve to use live binding, not grub.

Alternatively, r= ebuild the kernel with pciback built-in (not as a module) and that will all= ow you to use grub.

Supposedly you can rebuild the initrd image without rec= ompiling the whole kernel, if live binding isn't appealing then I would= investigate that.

On M= on, Sep 10, 2012 at 1:03 PM, Tilo Peter <phenix@web.de> wrote:
Hi,
I tried running debian wheezy amd64 with the debian stock kernel 3.2 and xen 4.2 rc3. Compiling ran through without any errors and xen boots up
without problems.

But xen-pciback always produces the same error message:

# lsmod | grep pci
pci_stub =A0 =A0 =A0 =A0 =A0 =A0 =A0 12429 =A00
# modprobe xen-pciback
ERROR: could not insert 'xen_pciback': Unknown symbol in module, or=
unknown parameter (see dmesg)
# dmesg | tail -n 1
[ 3687.470124] xen_pciback: Unknown parameter `1)'


This message always appears when I try to load xen-pciback, whenever I
give a "hide=3D(0000:01.00.0)" parameter or not, or in general wh= atever I do.

Since I couldn't find any help on this topic so far, I hope for some idea for a solution here!


Best Regards,
Tilo


_______________________________________________
Xen-users mailing list
Xen-users@lists.xen.org
http://lists.x= en.org/xen-users

--bcaec54a35ca2e4b5904c95dc2bd-- --===============8772633522200577697== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users --===============8772633522200577697==-- From xen-users-bounces@lists.xen.org Mon Sep 10 19:14:55 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Mon, 10 Sep 2012 19:14:55 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TB9Qn-0000Hl-1z; Mon, 10 Sep 2012 19:14:01 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TB9Qk-0000Hg-MN for xen-users@lists.xen.org; Mon, 10 Sep 2012 19:13:59 +0000 Received: from [85.158.139.83:25393] by server-3.bemta-5.messagelabs.com id 06/4E-21836-5FB3E405; Mon, 10 Sep 2012 19:13:57 +0000 X-Env-Sender: cdelorme@gmail.com X-Msg-Ref: server-15.tower-182.messagelabs.com!1347304434!27494616!1 X-Originating-IP: [209.85.214.173] X-SpamReason: No, hits=0.9 required=7.0 tests=BODY_RANDOM_LONG, HTML_30_40, HTML_MESSAGE, ML_RADAR_SPEW_LINKS_14, RCVD_BY_IP, spamassassin: X-StarScan-Received: X-StarScan-Version: 6.6.1.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 21611 invoked from network); 10 Sep 2012 19:13:55 -0000 Received: from mail-ob0-f173.google.com (HELO mail-ob0-f173.google.com) (209.85.214.173) by server-15.tower-182.messagelabs.com with RC4-SHA encrypted SMTP; 10 Sep 2012 19:13:55 -0000 Received: by obbta14 with SMTP id ta14so4611905obb.32 for ; Mon, 10 Sep 2012 12:13:53 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=DxTfd5rPj5FeB/oC111Y4FIcubZ6PQiVu4da7H3928I=; b=J3txwlqrUXeTtXxqDgCS8wpuIiWwdT5QpAsHPsp5QJbmYBAp7CQ2NRIgFC6Ojs0yka GujgC3HEBhsf5ciE4kegypinuTVKkboll0E6R3SwOLGBT7hgXuv3/Vawk/dt2a1g6Gq4 5JZCK46pPypPuPoPkdjBLvsublPhlYPgoozNVkzNEmhiCThJsv4Zxk6QubKyB7fp0+g/ UDOEubB7lnfalaLg5RDtgqnqW2LEGrK8XPvJm8ihnexDEWGK2mb9D5ZDsXkBLWg0aWI4 ogRPwy8ookv5AIoUKCaJ8jVkwVjyjsmbGFas0hDKSxwGqXDxKZQsgkRYHpuQ3tsTkd5n YDJw== MIME-Version: 1.0 Received: by 10.60.169.8 with SMTP id aa8mr15250661oec.109.1347304433797; Mon, 10 Sep 2012 12:13:53 -0700 (PDT) Received: by 10.76.115.197 with HTTP; Mon, 10 Sep 2012 12:13:53 -0700 (PDT) In-Reply-To: <504E1D66.6030502@web.de> References: <504E1D66.6030502@web.de> Date: Mon, 10 Sep 2012 15:13:53 -0400 Message-ID: From: Casey DeLorme To: Tilo Peter Cc: "xen-users@lists.xen.org" Subject: Re: [Xen-users] xen-pciback always gives error: Unknown parameter `1)' X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============8772633522200577697==" Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org --===============8772633522200577697== Content-Type: multipart/alternative; boundary=bcaec54a35ca2e4b5904c95dc2bd --bcaec54a35ca2e4b5904c95dc2bd Content-Type: text/plain; charset=ISO-8859-1 If you are using the stock kernel and pciback as a module, then you have to use live binding, not grub. Alternatively, rebuild the kernel with pciback built-in (not as a module) and that will allow you to use grub. Supposedly you can rebuild the initrd image without recompiling the whole kernel, if live binding isn't appealing then I would investigate that. On Mon, Sep 10, 2012 at 1:03 PM, Tilo Peter wrote: > Hi, > I tried running debian wheezy amd64 with the debian stock kernel 3.2 and > xen 4.2 rc3. Compiling ran through without any errors and xen boots up > without problems. > > But xen-pciback always produces the same error message: > > # lsmod | grep pci > pci_stub 12429 0 > # modprobe xen-pciback > ERROR: could not insert 'xen_pciback': Unknown symbol in module, or > unknown parameter (see dmesg) > # dmesg | tail -n 1 > [ 3687.470124] xen_pciback: Unknown parameter `1)' > > > This message always appears when I try to load xen-pciback, whenever I > give a "hide=(0000:01.00.0)" parameter or not, or in general whatever I do. > > Since I couldn't find any help on this topic so far, I hope for some > idea for a solution here! > > > Best Regards, > Tilo > > > _______________________________________________ > Xen-users mailing list > Xen-users@lists.xen.org > http://lists.xen.org/xen-users > --bcaec54a35ca2e4b5904c95dc2bd Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable
If you are using the stock kernel and pciback as a module, then you ha= ve to use live binding, not grub.

Alternatively, r= ebuild the kernel with pciback built-in (not as a module) and that will all= ow you to use grub.

Supposedly you can rebuild the initrd image without rec= ompiling the whole kernel, if live binding isn't appealing then I would= investigate that.

On M= on, Sep 10, 2012 at 1:03 PM, Tilo Peter <phenix@web.de> wrote:
Hi,
I tried running debian wheezy amd64 with the debian stock kernel 3.2 and xen 4.2 rc3. Compiling ran through without any errors and xen boots up
without problems.

But xen-pciback always produces the same error message:

# lsmod | grep pci
pci_stub =A0 =A0 =A0 =A0 =A0 =A0 =A0 12429 =A00
# modprobe xen-pciback
ERROR: could not insert 'xen_pciback': Unknown symbol in module, or=
unknown parameter (see dmesg)
# dmesg | tail -n 1
[ 3687.470124] xen_pciback: Unknown parameter `1)'


This message always appears when I try to load xen-pciback, whenever I
give a "hide=3D(0000:01.00.0)" parameter or not, or in general wh= atever I do.

Since I couldn't find any help on this topic so far, I hope for some idea for a solution here!


Best Regards,
Tilo


_______________________________________________
Xen-users mailing list
Xen-users@lists.xen.org
http://lists.x= en.org/xen-users

--bcaec54a35ca2e4b5904c95dc2bd-- --===============8772633522200577697== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users --===============8772633522200577697==-- From xen-users-bounces@lists.xen.org Mon Sep 10 19:55:47 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Mon, 10 Sep 2012 19:55:47 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TBA4S-0004HR-0R; Mon, 10 Sep 2012 19:55:00 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TBA4Q-0004GT-39 for xen-users@lists.xen.org; Mon, 10 Sep 2012 19:54:58 +0000 Received: from [85.158.139.83:43004] by server-11.bemta-5.messagelabs.com id F8/AF-24658-F854E405; Mon, 10 Sep 2012 19:54:55 +0000 X-Env-Sender: phenix@web.de X-Msg-Ref: server-12.tower-182.messagelabs.com!1347306894!29512177!1 X-Originating-IP: [212.227.15.4] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogMjEyLjIyNy4xNS40ID0+IDE3NTMy\n X-StarScan-Received: X-StarScan-Version: 6.6.1.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 17741 invoked from network); 10 Sep 2012 19:54:54 -0000 Received: from mout.web.de (HELO mout.web.de) (212.227.15.4) by server-12.tower-182.messagelabs.com with SMTP; 10 Sep 2012 19:54:54 -0000 Received: from [10.10.10.24] ([86.103.239.138]) by smtp.web.de (mrweb002) with ESMTPSA (Nemesis) id 0M6UmJ-1TUmSE2z3z-00y0AC; Mon, 10 Sep 2012 21:54:53 +0200 Message-ID: <504E462F.8000505@web.de> Date: Mon, 10 Sep 2012 21:57:35 +0200 From: Tilo Peter User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:13.0) Gecko/20120614 Thunderbird/13.0.1 MIME-Version: 1.0 To: Casey DeLorme References: <504E1D66.6030502@web.de> In-Reply-To: X-Provags-ID: V02:K0:D9IWVrIGJRBXfCe4M7yGssyLVXKm8B5MP6TGaBvrFmu zR9tFB9AFkafceDLfMc52NxwYC4w0Fb0FvWh2WStEijZIk9ZUV 9oIh/OeF3nGartkZ6Z8eHDzyg506kj7wFSch4atjKgk1idCXWy RHUXT6oVmLfyY1GfOCuMtEMmH5MqrXA7WYfkoyZNpzCqIu5xrP rf8SHwRVl3GvW0zkcDcSg== Cc: "xen-users@lists.xen.org" Subject: Re: [Xen-users] xen-pciback always gives error: Unknown parameter `1)' X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset="us-ascii"; Format="flowed" Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org Thanks for your reply, what exactly do you mean by "live binding"? As I showed in the code example, I tried to do this in the running system using modprobe. I will look into recompiling the kernel, but I still wonder if there is a bug that prevents xen-pciback to run probably in this configuration. On 10.9.12 21:13, Casey DeLorme wrote: > If you are using the stock kernel and pciback as a module, then you have > to use live binding, not grub. > > Alternatively, rebuild the kernel with pciback built-in (not as a > module) and that will allow you to use grub. > > Supposedly you can rebuild the initrd image without recompiling the > whole kernel, if live binding isn't appealing then I would investigate that. > > On Mon, Sep 10, 2012 at 1:03 PM, Tilo Peter > wrote: > > Hi, > I tried running debian wheezy amd64 with the debian stock kernel 3.2 and > xen 4.2 rc3. Compiling ran through without any errors and xen boots up > without problems. > > But xen-pciback always produces the same error message: > > # lsmod | grep pci > pci_stub 12429 0 > # modprobe xen-pciback > ERROR: could not insert 'xen_pciback': Unknown symbol in module, or > unknown parameter (see dmesg) > # dmesg | tail -n 1 > [ 3687.470124] xen_pciback: Unknown parameter `1)' > > > This message always appears when I try to load xen-pciback, whenever I > give a "hide=(0000:01.00.0)" parameter or not, or in general > whatever I do. > > Since I couldn't find any help on this topic so far, I hope for some > idea for a solution here! > > > Best Regards, > Tilo > _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Mon Sep 10 19:55:47 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Mon, 10 Sep 2012 19:55:47 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TBA4S-0004HR-0R; Mon, 10 Sep 2012 19:55:00 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TBA4Q-0004GT-39 for xen-users@lists.xen.org; Mon, 10 Sep 2012 19:54:58 +0000 Received: from [85.158.139.83:43004] by server-11.bemta-5.messagelabs.com id F8/AF-24658-F854E405; Mon, 10 Sep 2012 19:54:55 +0000 X-Env-Sender: phenix@web.de X-Msg-Ref: server-12.tower-182.messagelabs.com!1347306894!29512177!1 X-Originating-IP: [212.227.15.4] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogMjEyLjIyNy4xNS40ID0+IDE3NTMy\n X-StarScan-Received: X-StarScan-Version: 6.6.1.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 17741 invoked from network); 10 Sep 2012 19:54:54 -0000 Received: from mout.web.de (HELO mout.web.de) (212.227.15.4) by server-12.tower-182.messagelabs.com with SMTP; 10 Sep 2012 19:54:54 -0000 Received: from [10.10.10.24] ([86.103.239.138]) by smtp.web.de (mrweb002) with ESMTPSA (Nemesis) id 0M6UmJ-1TUmSE2z3z-00y0AC; Mon, 10 Sep 2012 21:54:53 +0200 Message-ID: <504E462F.8000505@web.de> Date: Mon, 10 Sep 2012 21:57:35 +0200 From: Tilo Peter User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:13.0) Gecko/20120614 Thunderbird/13.0.1 MIME-Version: 1.0 To: Casey DeLorme References: <504E1D66.6030502@web.de> In-Reply-To: X-Provags-ID: V02:K0:D9IWVrIGJRBXfCe4M7yGssyLVXKm8B5MP6TGaBvrFmu zR9tFB9AFkafceDLfMc52NxwYC4w0Fb0FvWh2WStEijZIk9ZUV 9oIh/OeF3nGartkZ6Z8eHDzyg506kj7wFSch4atjKgk1idCXWy RHUXT6oVmLfyY1GfOCuMtEMmH5MqrXA7WYfkoyZNpzCqIu5xrP rf8SHwRVl3GvW0zkcDcSg== Cc: "xen-users@lists.xen.org" Subject: Re: [Xen-users] xen-pciback always gives error: Unknown parameter `1)' X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset="us-ascii"; Format="flowed" Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org Thanks for your reply, what exactly do you mean by "live binding"? As I showed in the code example, I tried to do this in the running system using modprobe. I will look into recompiling the kernel, but I still wonder if there is a bug that prevents xen-pciback to run probably in this configuration. On 10.9.12 21:13, Casey DeLorme wrote: > If you are using the stock kernel and pciback as a module, then you have > to use live binding, not grub. > > Alternatively, rebuild the kernel with pciback built-in (not as a > module) and that will allow you to use grub. > > Supposedly you can rebuild the initrd image without recompiling the > whole kernel, if live binding isn't appealing then I would investigate that. > > On Mon, Sep 10, 2012 at 1:03 PM, Tilo Peter > wrote: > > Hi, > I tried running debian wheezy amd64 with the debian stock kernel 3.2 and > xen 4.2 rc3. Compiling ran through without any errors and xen boots up > without problems. > > But xen-pciback always produces the same error message: > > # lsmod | grep pci > pci_stub 12429 0 > # modprobe xen-pciback > ERROR: could not insert 'xen_pciback': Unknown symbol in module, or > unknown parameter (see dmesg) > # dmesg | tail -n 1 > [ 3687.470124] xen_pciback: Unknown parameter `1)' > > > This message always appears when I try to load xen-pciback, whenever I > give a "hide=(0000:01.00.0)" parameter or not, or in general > whatever I do. > > Since I couldn't find any help on this topic so far, I hope for some > idea for a solution here! > > > Best Regards, > Tilo > _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Mon Sep 10 20:23:08 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Mon, 10 Sep 2012 20:23:08 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TBAUz-0006jt-MV; Mon, 10 Sep 2012 20:22:25 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TBAUx-0006iw-K4 for xen-users@lists.xen.org; Mon, 10 Sep 2012 20:22:23 +0000 Received: from [85.158.139.83:49229] by server-4.bemta-5.messagelabs.com id 40/FF-23042-EFB4E405; Mon, 10 Sep 2012 20:22:22 +0000 X-Env-Sender: lists+xen@internecto.net X-Msg-Ref: server-10.tower-182.messagelabs.com!1347308541!29969984!1 X-Originating-IP: [176.9.245.29] X-SpamReason: No, hits=0.0 required=7.0 tests= X-StarScan-Received: X-StarScan-Version: 6.6.1.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 18153 invoked from network); 10 Sep 2012 20:22:22 -0000 Received: from polaris.internecto.net (HELO mx1.internecto.net) (176.9.245.29) by server-10.tower-182.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 10 Sep 2012 20:22:22 -0000 Received: from localhost (localhost [127.0.0.1]) by mx1.internecto.net (Postfix) with ESMTP id B312FA02ED; Mon, 10 Sep 2012 20:22:21 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at mail.internecto.net Received: from mx1.internecto.net ([127.0.0.1]) by localhost (mail.polaris.internecto.net [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 4JoLdhGOrTqN; Mon, 10 Sep 2012 20:22:16 +0000 (UTC) Received: from internecto.net (5ED4FDEB.cm-7-5d.dynamic.ziggo.nl [94.212.253.235]) (using TLSv1 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (Client did not present a certificate) (Authenticated sender: lists@internecto.net) by mx1.internecto.net (Postfix) with ESMTPSA id 25A5EA0089; Mon, 10 Sep 2012 20:22:16 +0000 (UTC) Date: Mon, 10 Sep 2012 22:22:14 +0200 From: Mark van Dijk To: Fabrice Delente Message-ID: <20120910222214.444b9b72@internecto.net> In-Reply-To: References: Organization: Internecto SIS X-Mailer: Claws Mail 3.8.0 (GTK+ 2.24.10; x86_64-pc-linux-gnu) Mime-Version: 1.0 Cc: xen-users@lists.xen.org Subject: Re: [Xen-users] Bugs in VNC viewer ? Mouse offset and keyboard map incorrect X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org Quoting Fabrice Delente's message from 10 sep 2012: >Hello. > >Am I the only one to have problem with the VNC server that is included >in Xen? Ihave tried with several VNC client, and every time > >* the mouse cursor is offset from the host system cursor; Yeah, that's pretty common in my experience. It's because the client uses its own cursor acceleration. > >* the keys on the keyboard give characters that don't match (for >example, typing ';' on my keyboard gives an 'm' on the guest's >screen...) Probably an issue between different keymaps on the VNC client and server. Maybe you can set a keymap on your vnc client? I use remmina as a vnc client (wrapper), and am able to choose different clients. I use the dvorak layout, so I have set my VNC client to dvorak as well. But on the guest VM I still have to set it to the US layout. Probably because the client sends key codes, not characters, to the VNC server. -- HTH, Mark van Dijk. ,--------------------------------- -----------------------------' Mon Sep 10 20:22 UTC 2012 Today is Pungenday, the 34th day of Bureaucracy in the YOLD 3178 _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Mon Sep 10 20:23:08 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Mon, 10 Sep 2012 20:23:08 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TBAUz-0006jt-MV; Mon, 10 Sep 2012 20:22:25 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TBAUx-0006iw-K4 for xen-users@lists.xen.org; Mon, 10 Sep 2012 20:22:23 +0000 Received: from [85.158.139.83:49229] by server-4.bemta-5.messagelabs.com id 40/FF-23042-EFB4E405; Mon, 10 Sep 2012 20:22:22 +0000 X-Env-Sender: lists+xen@internecto.net X-Msg-Ref: server-10.tower-182.messagelabs.com!1347308541!29969984!1 X-Originating-IP: [176.9.245.29] X-SpamReason: No, hits=0.0 required=7.0 tests= X-StarScan-Received: X-StarScan-Version: 6.6.1.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 18153 invoked from network); 10 Sep 2012 20:22:22 -0000 Received: from polaris.internecto.net (HELO mx1.internecto.net) (176.9.245.29) by server-10.tower-182.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 10 Sep 2012 20:22:22 -0000 Received: from localhost (localhost [127.0.0.1]) by mx1.internecto.net (Postfix) with ESMTP id B312FA02ED; Mon, 10 Sep 2012 20:22:21 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at mail.internecto.net Received: from mx1.internecto.net ([127.0.0.1]) by localhost (mail.polaris.internecto.net [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 4JoLdhGOrTqN; Mon, 10 Sep 2012 20:22:16 +0000 (UTC) Received: from internecto.net (5ED4FDEB.cm-7-5d.dynamic.ziggo.nl [94.212.253.235]) (using TLSv1 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (Client did not present a certificate) (Authenticated sender: lists@internecto.net) by mx1.internecto.net (Postfix) with ESMTPSA id 25A5EA0089; Mon, 10 Sep 2012 20:22:16 +0000 (UTC) Date: Mon, 10 Sep 2012 22:22:14 +0200 From: Mark van Dijk To: Fabrice Delente Message-ID: <20120910222214.444b9b72@internecto.net> In-Reply-To: References: Organization: Internecto SIS X-Mailer: Claws Mail 3.8.0 (GTK+ 2.24.10; x86_64-pc-linux-gnu) Mime-Version: 1.0 Cc: xen-users@lists.xen.org Subject: Re: [Xen-users] Bugs in VNC viewer ? Mouse offset and keyboard map incorrect X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org Quoting Fabrice Delente's message from 10 sep 2012: >Hello. > >Am I the only one to have problem with the VNC server that is included >in Xen? Ihave tried with several VNC client, and every time > >* the mouse cursor is offset from the host system cursor; Yeah, that's pretty common in my experience. It's because the client uses its own cursor acceleration. > >* the keys on the keyboard give characters that don't match (for >example, typing ';' on my keyboard gives an 'm' on the guest's >screen...) Probably an issue between different keymaps on the VNC client and server. Maybe you can set a keymap on your vnc client? I use remmina as a vnc client (wrapper), and am able to choose different clients. I use the dvorak layout, so I have set my VNC client to dvorak as well. But on the guest VM I still have to set it to the US layout. Probably because the client sends key codes, not characters, to the VNC server. -- HTH, Mark van Dijk. ,--------------------------------- -----------------------------' Mon Sep 10 20:22 UTC 2012 Today is Pungenday, the 34th day of Bureaucracy in the YOLD 3178 _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Mon Sep 10 20:35:18 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Mon, 10 Sep 2012 20:35:18 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TBAgn-0007Ir-Ag; Mon, 10 Sep 2012 20:34:37 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TBAgl-0007Ii-My for xen-users@lists.xen.org; Mon, 10 Sep 2012 20:34:35 +0000 Received: from [85.158.143.99:47181] by server-2.bemta-4.messagelabs.com id C4/DF-21239-BDE4E405; Mon, 10 Sep 2012 20:34:35 +0000 X-Env-Sender: lists+xen@internecto.net X-Msg-Ref: server-16.tower-216.messagelabs.com!1347309274!18377241!1 X-Originating-IP: [176.9.245.29] X-SpamReason: No, hits=0.5 required=7.0 tests=BODY_RANDOM_LONG X-StarScan-Received: X-StarScan-Version: 6.6.1.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 24002 invoked from network); 10 Sep 2012 20:34:34 -0000 Received: from polaris.internecto.net (HELO mx1.internecto.net) (176.9.245.29) by server-16.tower-216.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 10 Sep 2012 20:34:34 -0000 Received: from localhost (localhost [127.0.0.1]) by mx1.internecto.net (Postfix) with ESMTP id D66FFA02ED; Mon, 10 Sep 2012 20:34:33 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at mail.internecto.net Received: from mx1.internecto.net ([127.0.0.1]) by localhost (mail.polaris.internecto.net [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id jhwK+CVPV2sh; Mon, 10 Sep 2012 20:34:33 +0000 (UTC) Received: from internecto.net (5ED4FDEB.cm-7-5d.dynamic.ziggo.nl [94.212.253.235]) (using TLSv1 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (Client did not present a certificate) (Authenticated sender: lists@internecto.net) by mx1.internecto.net (Postfix) with ESMTPSA id D3544A0089; Mon, 10 Sep 2012 20:34:32 +0000 (UTC) Date: Mon, 10 Sep 2012 22:34:31 +0200 From: Mark van Dijk To: Tilo Peter Message-ID: <20120910223431.60c22bcd@internecto.net> In-Reply-To: <504E1D66.6030502@web.de> References: <504E1D66.6030502@web.de> Organization: Internecto SIS X-Mailer: Claws Mail 3.8.0 (GTK+ 2.24.10; x86_64-pc-linux-gnu) Mime-Version: 1.0 Cc: xen-users@lists.xen.org Subject: Re: [Xen-users] xen-pciback always gives error: Unknown parameter `1)' X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org Quoting Tilo Peter's message from 10 sep 2012: >Hi, >I tried running debian wheezy amd64 with the debian stock kernel 3.2 >and xen 4.2 rc3. Compiling ran through without any errors and xen >boots up without problems. > >But xen-pciback always produces the same error message: > ># lsmod | grep pci >pci_stub 12429 0 ># modprobe xen-pciback >ERROR: could not insert 'xen_pciback': Unknown symbol in module, or >unknown parameter (see dmesg) ># dmesg | tail -n 1 >[ 3687.470124] xen_pciback: Unknown parameter `1)' > > >This message always appears when I try to load xen-pciback, whenever I >give a "hide=(0000:01.00.0)" parameter or not, or in general whatever >I do. > >Since I couldn't find any help on this topic so far, I hope for some >idea for a solution here! If you load the module on the kernel command line, try to put the whole string inside quotes. For example, in my extlinux.conf I have: "xen-pciback.hide=(01:00.0)" and I can imagine that you could also try this with grub. I noticed you have 0000:01.00.0. I see two periods. Are you sure that this is right? Usually it should be similar to 01:00.0, 02:00.0, 06:04.0 et cetera. Be sure to double check that. If you would rather not have the xen-pciback line in grub but instead have the module be loaded during boot or via a manual modprobe, then be sure to have something in /etc/modules.conf or /etc/module.d/custom.conf (or another name of your own preference) like the following: options xen-pciback hide=(01:00.0)(02:00.0)(06:04.0) After that, run update-initramfs. Usually I just do either "update-initramfs -k all -c" or instead of -c (create new initramfs) I use -u (update existing initramfs). If that does not work, try to put the full string of the last element in quotes and retry again. -- HTH, Mark van Dijk. ,--------------------------------- -----------------------------' Mon Sep 10 20:34 UTC 2012 Today is Pungenday, the 34th day of Bureaucracy in the YOLD 3178 _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Mon Sep 10 20:35:18 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Mon, 10 Sep 2012 20:35:18 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TBAgn-0007Ir-Ag; Mon, 10 Sep 2012 20:34:37 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TBAgl-0007Ii-My for xen-users@lists.xen.org; Mon, 10 Sep 2012 20:34:35 +0000 Received: from [85.158.143.99:47181] by server-2.bemta-4.messagelabs.com id C4/DF-21239-BDE4E405; Mon, 10 Sep 2012 20:34:35 +0000 X-Env-Sender: lists+xen@internecto.net X-Msg-Ref: server-16.tower-216.messagelabs.com!1347309274!18377241!1 X-Originating-IP: [176.9.245.29] X-SpamReason: No, hits=0.5 required=7.0 tests=BODY_RANDOM_LONG X-StarScan-Received: X-StarScan-Version: 6.6.1.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 24002 invoked from network); 10 Sep 2012 20:34:34 -0000 Received: from polaris.internecto.net (HELO mx1.internecto.net) (176.9.245.29) by server-16.tower-216.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 10 Sep 2012 20:34:34 -0000 Received: from localhost (localhost [127.0.0.1]) by mx1.internecto.net (Postfix) with ESMTP id D66FFA02ED; Mon, 10 Sep 2012 20:34:33 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at mail.internecto.net Received: from mx1.internecto.net ([127.0.0.1]) by localhost (mail.polaris.internecto.net [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id jhwK+CVPV2sh; Mon, 10 Sep 2012 20:34:33 +0000 (UTC) Received: from internecto.net (5ED4FDEB.cm-7-5d.dynamic.ziggo.nl [94.212.253.235]) (using TLSv1 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (Client did not present a certificate) (Authenticated sender: lists@internecto.net) by mx1.internecto.net (Postfix) with ESMTPSA id D3544A0089; Mon, 10 Sep 2012 20:34:32 +0000 (UTC) Date: Mon, 10 Sep 2012 22:34:31 +0200 From: Mark van Dijk To: Tilo Peter Message-ID: <20120910223431.60c22bcd@internecto.net> In-Reply-To: <504E1D66.6030502@web.de> References: <504E1D66.6030502@web.de> Organization: Internecto SIS X-Mailer: Claws Mail 3.8.0 (GTK+ 2.24.10; x86_64-pc-linux-gnu) Mime-Version: 1.0 Cc: xen-users@lists.xen.org Subject: Re: [Xen-users] xen-pciback always gives error: Unknown parameter `1)' X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org Quoting Tilo Peter's message from 10 sep 2012: >Hi, >I tried running debian wheezy amd64 with the debian stock kernel 3.2 >and xen 4.2 rc3. Compiling ran through without any errors and xen >boots up without problems. > >But xen-pciback always produces the same error message: > ># lsmod | grep pci >pci_stub 12429 0 ># modprobe xen-pciback >ERROR: could not insert 'xen_pciback': Unknown symbol in module, or >unknown parameter (see dmesg) ># dmesg | tail -n 1 >[ 3687.470124] xen_pciback: Unknown parameter `1)' > > >This message always appears when I try to load xen-pciback, whenever I >give a "hide=(0000:01.00.0)" parameter or not, or in general whatever >I do. > >Since I couldn't find any help on this topic so far, I hope for some >idea for a solution here! If you load the module on the kernel command line, try to put the whole string inside quotes. For example, in my extlinux.conf I have: "xen-pciback.hide=(01:00.0)" and I can imagine that you could also try this with grub. I noticed you have 0000:01.00.0. I see two periods. Are you sure that this is right? Usually it should be similar to 01:00.0, 02:00.0, 06:04.0 et cetera. Be sure to double check that. If you would rather not have the xen-pciback line in grub but instead have the module be loaded during boot or via a manual modprobe, then be sure to have something in /etc/modules.conf or /etc/module.d/custom.conf (or another name of your own preference) like the following: options xen-pciback hide=(01:00.0)(02:00.0)(06:04.0) After that, run update-initramfs. Usually I just do either "update-initramfs -k all -c" or instead of -c (create new initramfs) I use -u (update existing initramfs). If that does not work, try to put the full string of the last element in quotes and retry again. -- HTH, Mark van Dijk. ,--------------------------------- -----------------------------' Mon Sep 10 20:34 UTC 2012 Today is Pungenday, the 34th day of Bureaucracy in the YOLD 3178 _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Mon Sep 10 20:46:27 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Mon, 10 Sep 2012 20:46:27 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TBArM-0007jw-Ou; Mon, 10 Sep 2012 20:45:32 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TBArK-0007jq-JE for xen-users@lists.xen.org; Mon, 10 Sep 2012 20:45:30 +0000 Received: from [85.158.143.35:22701] by server-3.bemta-4.messagelabs.com id A0/59-08232-9615E405; Mon, 10 Sep 2012 20:45:29 +0000 X-Env-Sender: bunkertor@tiscali.it X-Msg-Ref: server-10.tower-21.messagelabs.com!1347309928!10243240!1 X-Originating-IP: [213.205.33.245] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogMjEzLjIwNS4zMy4yNDUgPT4gMjAzMjU=\n, ML_RADAR_SPEW_LINKS_14,spamassassin: X-StarScan-Received: X-StarScan-Version: 6.6.1.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 20607 invoked from network); 10 Sep 2012 20:45:28 -0000 Received: from santino.mail.tiscali.it (HELO santino.mail.tiscali.it) (213.205.33.245) by server-10.tower-21.messagelabs.com with SMTP; 10 Sep 2012 20:45:28 -0000 Received: from [172.16.1.180] ([78.13.188.52]) by santino.mail.tiscali.it with id xYlT1j00518G0wm01YlToL; Mon, 10 Sep 2012 22:45:28 +0200 Message-ID: <504E5167.20901@tiscali.it> Date: Mon, 10 Sep 2012 22:45:27 +0200 From: bunkertor User-Agent: Mozilla/5.0 (Windows NT 5.1; rv:11.0) Gecko/20120327 Thunderbird/11.0.1 MIME-Version: 1.0 To: xen-users@lists.xen.org References: <504E4DD5.8010705@tiscali.it> In-Reply-To: <504E4DD5.8010705@tiscali.it> X-Forwarded-Message-Id: <504E4DD5.8010705@tiscali.it> Subject: [Xen-users] Fwd: Re: [Xen-devel] grub error 28 X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============1697991516237496429==" Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org This is a multi-part message in MIME format. --===============1697991516237496429== Content-Type: multipart/alternative; boundary="------------030702000700000607060300" This is a multi-part message in MIME format. --------------030702000700000607060300 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit -------- Messaggio originale -------- Oggetto: Re: [Xen-devel] grub error 28 Data: Mon, 10 Sep 2012 22:30:13 +0200 Mittente: bunkertor A: Konrad Rzeszutek Wilk Il 10/09/2012 21.27, Konrad Rzeszutek Wilk ha scritto: >> GNU GRUB version 0.97 (640K lower / 3072K upper memory) >> >> [ Minimal BASH-like line editing is supported. For the first word, TAB >> lists possible command completions. Anywhere else TAB lists the >> possible >> completions of a device/filename.] >> grub> root (hd0,0) >> root (hd0,0) >> Filesystem type is ext2fs, partition type 0x83 >> grub> kernel /xen.gz >> kernel /xen.gz >> [Multiboot-elf,<0x964000:0x1a6db8:0x54248>(bad) >> >> Error 28: Selected item cannot fit into memory >> > Wish it said which one.. > >> [root@xen-02 xen-unstable]# ls -lh /boot/ >> totale 247M >> -rw-r--r--. 1 root root 100K 24 ago 03:31 config-2.6.32-279.5.2.el6.x86_64 >> -rw-r--r--. 1 root root 100K 22 giu 14:44 config-2.6.32-279.el6.x86_64 >> -rw-r--r--. 1 root root 114K 9 set 02:09 config-3.1.0-rc9 >> drwxr-xr-x. 3 root root 4,0K 9 set 00:16 efi >> drwxr-xr-x. 2 root root 4,0K 9 set 12:11 grub >> -rw-r--r--. 1 root root 23M 9 set 01:16 >> initramfs-2.6.32-279.5.2.el6.x86_64.img >> -rw-r--r--. 1 root root 23M 9 set 00:17 >> initramfs-2.6.32-279.el6.x86_64.img >> -rw-r--r--. 1 root root 154M 9 set 02:31 initramfs-3.1.0-rc9.img > This is pretty large? Any reason its so huge compared to the other ones? > > And why not use v3.4 instead of v3.1? > > > _______________________________________________ > Xen-devel mailing list > Xen-devel@lists.xen.org > http://lists.xen.org/xen-devel > hi i tried 2 different kernel version 3.1.0-rc9+ (jeremy/xen.git) and 3.5.0+ (konrad/xen.git): same error in both versions (http://wiki.xensource.com/xenwiki/XenParavirtOps) i've noticed initramfs is huge, i dont know why, i've just followed the xen wiki to compile xenified kernel, no special options: fresh install clone git kernel-xen cp config-runningversion .config make oldconfig enabling all raccomanded xen options in .config (static should be ok) make bzImage make modules make install_modules cp bzImage, system.map, .config in /boot dir dracut initramfs... standard procedure end no error compiling kernels. same for xen-unstable or xen-4.2.0-rc2 tarball (http://wiki.xen.org/wiki/Xen_4.2_Build_From_Source_On_RHEL_CentOS_Fedora) git clone xe-unstable (or untar) .configure (no error, no warning) make xen&& make tools&& make stubdom make install-xen&& make install-tools&& make install-stubdom with different standard linux distributions (fedora 16-grub2, ubuntu 12.04-grub2, centos 6.3-grub itself) i can boot and run system. thanks for quick answer and for help! regards. --------------030702000700000607060300 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit

-------- Messaggio originale --------
Oggetto: Re: [Xen-devel] grub error 28
Data: Mon, 10 Sep 2012 22:30:13 +0200
Mittente: bunkertor <bunkertor@tiscali.it>
A: Konrad Rzeszutek Wilk <konrad@kernel.org> 


Il 10/09/2012 21.27, Konrad Rzeszutek Wilk ha scritto:
>>      GNU GRUB  version 0.97  (640K lower / 3072K upper memory)
>>
>>   [ Minimal BASH-like line editing is supported.  For the first word, TAB
>>     lists possible command completions.  Anywhere else TAB lists the
>> possible
>>     completions of a device/filename.]
>> grub>  root (hd0,0)
>> root (hd0,0)
>>   Filesystem type is ext2fs, partition type 0x83
>> grub>  kernel /xen.gz
>> kernel /xen.gz
>>     [Multiboot-elf,<0x964000:0x1a6db8:0x54248>(bad)
>>
>> Error 28: Selected item cannot fit into memory
>>
> Wish it said which one..
>
>> [root@xen-02 xen-unstable]# ls -lh /boot/
>> totale 247M
>> -rw-r--r--. 1 root root 100K 24 ago 03:31 config-2.6.32-279.5.2.el6.x86_64
>> -rw-r--r--. 1 root root 100K 22 giu 14:44 config-2.6.32-279.el6.x86_64
>> -rw-r--r--. 1 root root 114K  9 set 02:09 config-3.1.0-rc9
>> drwxr-xr-x. 3 root root 4,0K  9 set 00:16 efi
>> drwxr-xr-x. 2 root root 4,0K  9 set 12:11 grub
>> -rw-r--r--. 1 root root  23M  9 set 01:16
>> initramfs-2.6.32-279.5.2.el6.x86_64.img
>> -rw-r--r--. 1 root root  23M  9 set 00:17
>> initramfs-2.6.32-279.el6.x86_64.img
>> -rw-r--r--. 1 root root 154M  9 set 02:31 initramfs-3.1.0-rc9.img
> This is pretty large? Any reason its so huge compared to the other ones?
>
> And why not use v3.4 instead of v3.1?
>
>
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xen.org
> http://lists.xen.org/xen-devel
>
hi

i tried 2 different kernel version 3.1.0-rc9+ (jeremy/xen.git) and 
3.5.0+ (konrad/xen.git): same error in both versions 
(http://wiki.xensource.com/xenwiki/XenParavirtOps)
i've noticed initramfs is huge, i dont know why, i've just followed the 
xen wiki to compile xenified kernel, no special options:

fresh install
clone git kernel-xen
cp config-runningversion .config
make oldconfig
enabling all raccomanded xen options in .config (static should be ok)
make bzImage
make modules
make install_modules
cp bzImage, system.map, .config in /boot dir
dracut initramfs...

standard procedure end no error compiling kernels.
same for xen-unstable or xen-4.2.0-rc2 tarball 
(http://wiki.xen.org/wiki/Xen_4.2_Build_From_Source_On_RHEL_CentOS_Fedora)

git clone xe-unstable (or untar)
.configure (no error, no warning)
make xen && make tools && make stubdom
make install-xen && make install-tools && make install-stubdom

with different standard linux distributions (fedora 16-grub2, ubuntu 
12.04-grub2, centos 6.3-grub itself) i can boot and run system.

thanks for quick answer and for help!

regards.
--------------030702000700000607060300-- --===============1697991516237496429== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users --===============1697991516237496429==-- From xen-users-bounces@lists.xen.org Mon Sep 10 20:46:27 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Mon, 10 Sep 2012 20:46:27 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TBArM-0007jw-Ou; Mon, 10 Sep 2012 20:45:32 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TBArK-0007jq-JE for xen-users@lists.xen.org; Mon, 10 Sep 2012 20:45:30 +0000 Received: from [85.158.143.35:22701] by server-3.bemta-4.messagelabs.com id A0/59-08232-9615E405; Mon, 10 Sep 2012 20:45:29 +0000 X-Env-Sender: bunkertor@tiscali.it X-Msg-Ref: server-10.tower-21.messagelabs.com!1347309928!10243240!1 X-Originating-IP: [213.205.33.245] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogMjEzLjIwNS4zMy4yNDUgPT4gMjAzMjU=\n, ML_RADAR_SPEW_LINKS_14,spamassassin: X-StarScan-Received: X-StarScan-Version: 6.6.1.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 20607 invoked from network); 10 Sep 2012 20:45:28 -0000 Received: from santino.mail.tiscali.it (HELO santino.mail.tiscali.it) (213.205.33.245) by server-10.tower-21.messagelabs.com with SMTP; 10 Sep 2012 20:45:28 -0000 Received: from [172.16.1.180] ([78.13.188.52]) by santino.mail.tiscali.it with id xYlT1j00518G0wm01YlToL; Mon, 10 Sep 2012 22:45:28 +0200 Message-ID: <504E5167.20901@tiscali.it> Date: Mon, 10 Sep 2012 22:45:27 +0200 From: bunkertor User-Agent: Mozilla/5.0 (Windows NT 5.1; rv:11.0) Gecko/20120327 Thunderbird/11.0.1 MIME-Version: 1.0 To: xen-users@lists.xen.org References: <504E4DD5.8010705@tiscali.it> In-Reply-To: <504E4DD5.8010705@tiscali.it> X-Forwarded-Message-Id: <504E4DD5.8010705@tiscali.it> Subject: [Xen-users] Fwd: Re: [Xen-devel] grub error 28 X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============1697991516237496429==" Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org This is a multi-part message in MIME format. --===============1697991516237496429== Content-Type: multipart/alternative; boundary="------------030702000700000607060300" This is a multi-part message in MIME format. --------------030702000700000607060300 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit -------- Messaggio originale -------- Oggetto: Re: [Xen-devel] grub error 28 Data: Mon, 10 Sep 2012 22:30:13 +0200 Mittente: bunkertor A: Konrad Rzeszutek Wilk Il 10/09/2012 21.27, Konrad Rzeszutek Wilk ha scritto: >> GNU GRUB version 0.97 (640K lower / 3072K upper memory) >> >> [ Minimal BASH-like line editing is supported. For the first word, TAB >> lists possible command completions. Anywhere else TAB lists the >> possible >> completions of a device/filename.] >> grub> root (hd0,0) >> root (hd0,0) >> Filesystem type is ext2fs, partition type 0x83 >> grub> kernel /xen.gz >> kernel /xen.gz >> [Multiboot-elf,<0x964000:0x1a6db8:0x54248>(bad) >> >> Error 28: Selected item cannot fit into memory >> > Wish it said which one.. > >> [root@xen-02 xen-unstable]# ls -lh /boot/ >> totale 247M >> -rw-r--r--. 1 root root 100K 24 ago 03:31 config-2.6.32-279.5.2.el6.x86_64 >> -rw-r--r--. 1 root root 100K 22 giu 14:44 config-2.6.32-279.el6.x86_64 >> -rw-r--r--. 1 root root 114K 9 set 02:09 config-3.1.0-rc9 >> drwxr-xr-x. 3 root root 4,0K 9 set 00:16 efi >> drwxr-xr-x. 2 root root 4,0K 9 set 12:11 grub >> -rw-r--r--. 1 root root 23M 9 set 01:16 >> initramfs-2.6.32-279.5.2.el6.x86_64.img >> -rw-r--r--. 1 root root 23M 9 set 00:17 >> initramfs-2.6.32-279.el6.x86_64.img >> -rw-r--r--. 1 root root 154M 9 set 02:31 initramfs-3.1.0-rc9.img > This is pretty large? Any reason its so huge compared to the other ones? > > And why not use v3.4 instead of v3.1? > > > _______________________________________________ > Xen-devel mailing list > Xen-devel@lists.xen.org > http://lists.xen.org/xen-devel > hi i tried 2 different kernel version 3.1.0-rc9+ (jeremy/xen.git) and 3.5.0+ (konrad/xen.git): same error in both versions (http://wiki.xensource.com/xenwiki/XenParavirtOps) i've noticed initramfs is huge, i dont know why, i've just followed the xen wiki to compile xenified kernel, no special options: fresh install clone git kernel-xen cp config-runningversion .config make oldconfig enabling all raccomanded xen options in .config (static should be ok) make bzImage make modules make install_modules cp bzImage, system.map, .config in /boot dir dracut initramfs... standard procedure end no error compiling kernels. same for xen-unstable or xen-4.2.0-rc2 tarball (http://wiki.xen.org/wiki/Xen_4.2_Build_From_Source_On_RHEL_CentOS_Fedora) git clone xe-unstable (or untar) .configure (no error, no warning) make xen&& make tools&& make stubdom make install-xen&& make install-tools&& make install-stubdom with different standard linux distributions (fedora 16-grub2, ubuntu 12.04-grub2, centos 6.3-grub itself) i can boot and run system. thanks for quick answer and for help! regards. --------------030702000700000607060300 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit

-------- Messaggio originale --------
Oggetto: Re: [Xen-devel] grub error 28
Data: Mon, 10 Sep 2012 22:30:13 +0200
Mittente: bunkertor <bunkertor@tiscali.it>
A: Konrad Rzeszutek Wilk <konrad@kernel.org> 


Il 10/09/2012 21.27, Konrad Rzeszutek Wilk ha scritto:
>>      GNU GRUB  version 0.97  (640K lower / 3072K upper memory)
>>
>>   [ Minimal BASH-like line editing is supported.  For the first word, TAB
>>     lists possible command completions.  Anywhere else TAB lists the
>> possible
>>     completions of a device/filename.]
>> grub>  root (hd0,0)
>> root (hd0,0)
>>   Filesystem type is ext2fs, partition type 0x83
>> grub>  kernel /xen.gz
>> kernel /xen.gz
>>     [Multiboot-elf,<0x964000:0x1a6db8:0x54248>(bad)
>>
>> Error 28: Selected item cannot fit into memory
>>
> Wish it said which one..
>
>> [root@xen-02 xen-unstable]# ls -lh /boot/
>> totale 247M
>> -rw-r--r--. 1 root root 100K 24 ago 03:31 config-2.6.32-279.5.2.el6.x86_64
>> -rw-r--r--. 1 root root 100K 22 giu 14:44 config-2.6.32-279.el6.x86_64
>> -rw-r--r--. 1 root root 114K  9 set 02:09 config-3.1.0-rc9
>> drwxr-xr-x. 3 root root 4,0K  9 set 00:16 efi
>> drwxr-xr-x. 2 root root 4,0K  9 set 12:11 grub
>> -rw-r--r--. 1 root root  23M  9 set 01:16
>> initramfs-2.6.32-279.5.2.el6.x86_64.img
>> -rw-r--r--. 1 root root  23M  9 set 00:17
>> initramfs-2.6.32-279.el6.x86_64.img
>> -rw-r--r--. 1 root root 154M  9 set 02:31 initramfs-3.1.0-rc9.img
> This is pretty large? Any reason its so huge compared to the other ones?
>
> And why not use v3.4 instead of v3.1?
>
>
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xen.org
> http://lists.xen.org/xen-devel
>
hi

i tried 2 different kernel version 3.1.0-rc9+ (jeremy/xen.git) and 
3.5.0+ (konrad/xen.git): same error in both versions 
(http://wiki.xensource.com/xenwiki/XenParavirtOps)
i've noticed initramfs is huge, i dont know why, i've just followed the 
xen wiki to compile xenified kernel, no special options:

fresh install
clone git kernel-xen
cp config-runningversion .config
make oldconfig
enabling all raccomanded xen options in .config (static should be ok)
make bzImage
make modules
make install_modules
cp bzImage, system.map, .config in /boot dir
dracut initramfs...

standard procedure end no error compiling kernels.
same for xen-unstable or xen-4.2.0-rc2 tarball 
(http://wiki.xen.org/wiki/Xen_4.2_Build_From_Source_On_RHEL_CentOS_Fedora)

git clone xe-unstable (or untar)
.configure (no error, no warning)
make xen && make tools && make stubdom
make install-xen && make install-tools && make install-stubdom

with different standard linux distributions (fedora 16-grub2, ubuntu 
12.04-grub2, centos 6.3-grub itself) i can boot and run system.

thanks for quick answer and for help!

regards.
--------------030702000700000607060300-- --===============1697991516237496429== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users --===============1697991516237496429==-- From xen-users-bounces@lists.xen.org Mon Sep 10 21:35:33 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Mon, 10 Sep 2012 21:35:33 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TBBcy-0001pO-9g; Mon, 10 Sep 2012 21:34:44 +0000 Received: from mail27.messagelabs.com ([193.109.254.147]) by lists.xen.org with smtp (Exim 4.72) (envelope-from ) id 1TBBcx-0001pH-CN for xen-users@lists.xen.org; Mon, 10 Sep 2012 21:34:43 +0000 X-Env-Sender: phenix@web.de X-Msg-Ref: server-7.tower-27.messagelabs.com!1347312875!2757912!1 X-Originating-IP: [212.227.17.11] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogMjEyLjIyNy4xNy4xMSA9PiAxODk2MA==\n X-StarScan-Received: X-StarScan-Version: 6.6.1.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 11713 invoked from network); 10 Sep 2012 21:34:35 -0000 Received: from mout.web.de (HELO mout.web.de) (212.227.17.11) by server-7.tower-27.messagelabs.com with SMTP; 10 Sep 2012 21:34:35 -0000 Received: from [10.10.10.2] ([86.103.239.138]) by smtp.web.de (mrweb103) with ESMTPSA (Nemesis) id 0MJCWU-1T8QjZ1F7a-002xSn; Mon, 10 Sep 2012 23:34:35 +0200 Message-ID: <504E5CE8.6040805@web.de> Date: Mon, 10 Sep 2012 23:34:32 +0200 From: Tilo Peter User-Agent: Mozilla/5.0 (X11; Linux i686; rv:15.0) Gecko/20120827 Thunderbird/15.0 MIME-Version: 1.0 To: Mark van Dijk References: <504E1D66.6030502@web.de> <20120910223431.60c22bcd@internecto.net> In-Reply-To: <20120910223431.60c22bcd@internecto.net> X-Enigmail-Version: 1.4.4 X-Provags-ID: V02:K0:8jkihLOORgHDsCTynXRSWrZPjiVo3mCiiFRMN5fkNCM 8IMgZt5VOh705IikkrZmjdvoiTzg9BLGiLSq5Tbnbmcap7W94c iUK1R3XMHDDst2BEim5gdEDkhPM0uB2lDozhxBNsQqv8dEgtAo ooa/kl82eeoX9bFVjXsXLedKJ7nzLJnkEMzYG/m6JRhmjL78K4 F5mQIRox0V+C+3UmfCIUw== Cc: xen-users@lists.xen.org Subject: Re: [Xen-users] xen-pciback always gives error: Unknown parameter `1)' X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org On 10/09/12 22:34, Mark van Dijk wrote: > Quoting Tilo Peter's message from 10 sep 2012: >> Hi, >> I tried running debian wheezy amd64 with the debian stock kernel 3.2 >> and xen 4.2 rc3. Compiling ran through without any errors and xen >> boots up without problems. >> >> But xen-pciback always produces the same error message: >> >> # lsmod | grep pci >> pci_stub 12429 0 >> # modprobe xen-pciback >> ERROR: could not insert 'xen_pciback': Unknown symbol in module, or >> unknown parameter (see dmesg) >> # dmesg | tail -n 1 >> [ 3687.470124] xen_pciback: Unknown parameter `1)' >> >> >> This message always appears when I try to load xen-pciback, whenever I >> give a "hide=(0000:01.00.0)" parameter or not, or in general whatever >> I do. >> >> Since I couldn't find any help on this topic so far, I hope for some >> idea for a solution here! > > If you load the module on the kernel command line, try to put the whole > string inside quotes. For example, in my extlinux.conf I have: > "xen-pciback.hide=(01:00.0)" and I can imagine that you could also try > this with grub. I tried this, but it didn't work, just didn't give any effect I could see. I only checked with "xm pci-list-assignable-devices", or is there any other way? > I noticed you have 0000:01.00.0. I see two periods. Are you sure that > this is right? Usually it should be similar to 01:00.0, 02:00.0, > 06:04.0 et cetera. Be sure to double check that. Just a typo, because in the shell it doesnt matter if try "modprobe xen-pciback", "modprobe xen-pciback 'hide=(01.00.0)'" or "modprobe xen-pciback foobar" the error message will always be the same. > If you would rather not have the xen-pciback line in grub but instead > have the module be loaded during boot or via a manual modprobe, then be > sure to have something in /etc/modules.conf or /etc/module.d/custom.conf > (or another name of your own preference) like the following: > > options xen-pciback hide=(01:00.0)(02:00.0)(06:04.0) OK, this actually worked. Thanks! > After that, run update-initramfs. Usually I just do either > "update-initramfs -k all -c" or instead of -c (create new initramfs) > I use -u (update existing initramfs). > > If that does not work, try to put the full string of the last element > in quotes and retry again. _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Mon Sep 10 21:35:33 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Mon, 10 Sep 2012 21:35:33 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TBBcy-0001pO-9g; Mon, 10 Sep 2012 21:34:44 +0000 Received: from mail27.messagelabs.com ([193.109.254.147]) by lists.xen.org with smtp (Exim 4.72) (envelope-from ) id 1TBBcx-0001pH-CN for xen-users@lists.xen.org; Mon, 10 Sep 2012 21:34:43 +0000 X-Env-Sender: phenix@web.de X-Msg-Ref: server-7.tower-27.messagelabs.com!1347312875!2757912!1 X-Originating-IP: [212.227.17.11] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogMjEyLjIyNy4xNy4xMSA9PiAxODk2MA==\n X-StarScan-Received: X-StarScan-Version: 6.6.1.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 11713 invoked from network); 10 Sep 2012 21:34:35 -0000 Received: from mout.web.de (HELO mout.web.de) (212.227.17.11) by server-7.tower-27.messagelabs.com with SMTP; 10 Sep 2012 21:34:35 -0000 Received: from [10.10.10.2] ([86.103.239.138]) by smtp.web.de (mrweb103) with ESMTPSA (Nemesis) id 0MJCWU-1T8QjZ1F7a-002xSn; Mon, 10 Sep 2012 23:34:35 +0200 Message-ID: <504E5CE8.6040805@web.de> Date: Mon, 10 Sep 2012 23:34:32 +0200 From: Tilo Peter User-Agent: Mozilla/5.0 (X11; Linux i686; rv:15.0) Gecko/20120827 Thunderbird/15.0 MIME-Version: 1.0 To: Mark van Dijk References: <504E1D66.6030502@web.de> <20120910223431.60c22bcd@internecto.net> In-Reply-To: <20120910223431.60c22bcd@internecto.net> X-Enigmail-Version: 1.4.4 X-Provags-ID: V02:K0:8jkihLOORgHDsCTynXRSWrZPjiVo3mCiiFRMN5fkNCM 8IMgZt5VOh705IikkrZmjdvoiTzg9BLGiLSq5Tbnbmcap7W94c iUK1R3XMHDDst2BEim5gdEDkhPM0uB2lDozhxBNsQqv8dEgtAo ooa/kl82eeoX9bFVjXsXLedKJ7nzLJnkEMzYG/m6JRhmjL78K4 F5mQIRox0V+C+3UmfCIUw== Cc: xen-users@lists.xen.org Subject: Re: [Xen-users] xen-pciback always gives error: Unknown parameter `1)' X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org On 10/09/12 22:34, Mark van Dijk wrote: > Quoting Tilo Peter's message from 10 sep 2012: >> Hi, >> I tried running debian wheezy amd64 with the debian stock kernel 3.2 >> and xen 4.2 rc3. Compiling ran through without any errors and xen >> boots up without problems. >> >> But xen-pciback always produces the same error message: >> >> # lsmod | grep pci >> pci_stub 12429 0 >> # modprobe xen-pciback >> ERROR: could not insert 'xen_pciback': Unknown symbol in module, or >> unknown parameter (see dmesg) >> # dmesg | tail -n 1 >> [ 3687.470124] xen_pciback: Unknown parameter `1)' >> >> >> This message always appears when I try to load xen-pciback, whenever I >> give a "hide=(0000:01.00.0)" parameter or not, or in general whatever >> I do. >> >> Since I couldn't find any help on this topic so far, I hope for some >> idea for a solution here! > > If you load the module on the kernel command line, try to put the whole > string inside quotes. For example, in my extlinux.conf I have: > "xen-pciback.hide=(01:00.0)" and I can imagine that you could also try > this with grub. I tried this, but it didn't work, just didn't give any effect I could see. I only checked with "xm pci-list-assignable-devices", or is there any other way? > I noticed you have 0000:01.00.0. I see two periods. Are you sure that > this is right? Usually it should be similar to 01:00.0, 02:00.0, > 06:04.0 et cetera. Be sure to double check that. Just a typo, because in the shell it doesnt matter if try "modprobe xen-pciback", "modprobe xen-pciback 'hide=(01.00.0)'" or "modprobe xen-pciback foobar" the error message will always be the same. > If you would rather not have the xen-pciback line in grub but instead > have the module be loaded during boot or via a manual modprobe, then be > sure to have something in /etc/modules.conf or /etc/module.d/custom.conf > (or another name of your own preference) like the following: > > options xen-pciback hide=(01:00.0)(02:00.0)(06:04.0) OK, this actually worked. Thanks! > After that, run update-initramfs. Usually I just do either > "update-initramfs -k all -c" or instead of -c (create new initramfs) > I use -u (update existing initramfs). > > If that does not work, try to put the full string of the last element > in quotes and retry again. _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Tue Sep 11 07:26:29 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Tue, 11 Sep 2012 07:26:29 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TBKqE-0004BN-7F; Tue, 11 Sep 2012 07:25:02 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TBKqB-0004BF-UA for xen-users@lists.xen.org; Tue, 11 Sep 2012 07:25:00 +0000 Received: from [85.158.138.51:16817] by server-4.bemta-3.messagelabs.com id B1/6B-24831-B47EE405; Tue, 11 Sep 2012 07:24:59 +0000 X-Env-Sender: Ian.Campbell@citrix.com X-Msg-Ref: server-7.tower-174.messagelabs.com!1347348298!20941046!1 X-Originating-IP: [62.200.22.115] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogNjIuMjAwLjIyLjExNSA9PiAxMDg1MTY=\n X-StarScan-Received: X-StarScan-Version: 6.6.1.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 27369 invoked from network); 11 Sep 2012 07:24:58 -0000 Received: from smtp.ctxuk.citrix.com (HELO SMTP.EU.CITRIX.COM) (62.200.22.115) by server-7.tower-174.messagelabs.com with RC4-SHA encrypted SMTP; 11 Sep 2012 07:24:58 -0000 X-IronPort-AV: E=Sophos;i="4.80,402,1344211200"; d="scan'208";a="14460097" Received: from lonpmailmx01.citrite.net ([10.30.203.162]) by LONPIPO01.EU.CITRIX.COM with ESMTP/TLS/RC4-MD5; 11 Sep 2012 07:24:36 +0000 Received: from [127.0.0.1] (10.80.16.67) by smtprelay.citrix.com (10.30.203.162) with Microsoft SMTP Server id 8.3.279.1; Tue, 11 Sep 2012 08:24:36 +0100 Message-ID: <1347348275.10570.80.camel@dagon.hellion.org.uk> From: Ian Campbell To: Mark van Dijk Date: Tue, 11 Sep 2012 08:24:35 +0100 In-Reply-To: <20120910222214.444b9b72@internecto.net> References: <20120910222214.444b9b72@internecto.net> Organization: Citrix Systems, Inc. X-Mailer: Evolution 3.4.3-1 MIME-Version: 1.0 Cc: "xen-users@lists.xen.org" , Fabrice Delente Subject: Re: [Xen-users] Bugs in VNC viewer ? Mouse offset and keyboard map incorrect X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org On Mon, 2012-09-10 at 21:22 +0100, Mark van Dijk wrote: > Quoting Fabrice Delente's message from 10 sep 2012: > >Hello. > > > >Am I the only one to have problem with the VNC server that is included > >in Xen? Ihave tried with several VNC client, and every time > > > >* the mouse cursor is offset from the host system cursor; > > Yeah, that's pretty common in my experience. It's because the client > uses its own cursor acceleration. Using usbdevice="tablet" in your guest config fixes this by using an absolute device type. > >* the keys on the keyboard give characters that don't match (for > >example, typing ';' on my keyboard gives an 'm' on the guest's > >screen...) > > Probably an issue between different keymaps on the VNC client and > server. Maybe you can set a keymap on your vnc client? I use remmina > as a vnc client (wrapper), and am able to choose different clients. I > use the dvorak layout, so I have set my VNC client to dvorak as well. > But on the guest VM I still have to set it to the US layout. > Probably because the client sends key codes, not characters, to the > VNC server. You can also use keymap='XX' in your guest config to configure the VNC server. I use keymap='en-gb' and that serves me well enough without client side configuration, but I don't have much experience with keymaps which differ more substantially from the default us one than the UK one does. Ian. _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Tue Sep 11 07:26:29 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Tue, 11 Sep 2012 07:26:29 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TBKqE-0004BN-7F; Tue, 11 Sep 2012 07:25:02 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TBKqB-0004BF-UA for xen-users@lists.xen.org; Tue, 11 Sep 2012 07:25:00 +0000 Received: from [85.158.138.51:16817] by server-4.bemta-3.messagelabs.com id B1/6B-24831-B47EE405; Tue, 11 Sep 2012 07:24:59 +0000 X-Env-Sender: Ian.Campbell@citrix.com X-Msg-Ref: server-7.tower-174.messagelabs.com!1347348298!20941046!1 X-Originating-IP: [62.200.22.115] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogNjIuMjAwLjIyLjExNSA9PiAxMDg1MTY=\n X-StarScan-Received: X-StarScan-Version: 6.6.1.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 27369 invoked from network); 11 Sep 2012 07:24:58 -0000 Received: from smtp.ctxuk.citrix.com (HELO SMTP.EU.CITRIX.COM) (62.200.22.115) by server-7.tower-174.messagelabs.com with RC4-SHA encrypted SMTP; 11 Sep 2012 07:24:58 -0000 X-IronPort-AV: E=Sophos;i="4.80,402,1344211200"; d="scan'208";a="14460097" Received: from lonpmailmx01.citrite.net ([10.30.203.162]) by LONPIPO01.EU.CITRIX.COM with ESMTP/TLS/RC4-MD5; 11 Sep 2012 07:24:36 +0000 Received: from [127.0.0.1] (10.80.16.67) by smtprelay.citrix.com (10.30.203.162) with Microsoft SMTP Server id 8.3.279.1; Tue, 11 Sep 2012 08:24:36 +0100 Message-ID: <1347348275.10570.80.camel@dagon.hellion.org.uk> From: Ian Campbell To: Mark van Dijk Date: Tue, 11 Sep 2012 08:24:35 +0100 In-Reply-To: <20120910222214.444b9b72@internecto.net> References: <20120910222214.444b9b72@internecto.net> Organization: Citrix Systems, Inc. X-Mailer: Evolution 3.4.3-1 MIME-Version: 1.0 Cc: "xen-users@lists.xen.org" , Fabrice Delente Subject: Re: [Xen-users] Bugs in VNC viewer ? Mouse offset and keyboard map incorrect X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org On Mon, 2012-09-10 at 21:22 +0100, Mark van Dijk wrote: > Quoting Fabrice Delente's message from 10 sep 2012: > >Hello. > > > >Am I the only one to have problem with the VNC server that is included > >in Xen? Ihave tried with several VNC client, and every time > > > >* the mouse cursor is offset from the host system cursor; > > Yeah, that's pretty common in my experience. It's because the client > uses its own cursor acceleration. Using usbdevice="tablet" in your guest config fixes this by using an absolute device type. > >* the keys on the keyboard give characters that don't match (for > >example, typing ';' on my keyboard gives an 'm' on the guest's > >screen...) > > Probably an issue between different keymaps on the VNC client and > server. Maybe you can set a keymap on your vnc client? I use remmina > as a vnc client (wrapper), and am able to choose different clients. I > use the dvorak layout, so I have set my VNC client to dvorak as well. > But on the guest VM I still have to set it to the US layout. > Probably because the client sends key codes, not characters, to the > VNC server. You can also use keymap='XX' in your guest config to configure the VNC server. I use keymap='en-gb' and that serves me well enough without client side configuration, but I don't have much experience with keymaps which differ more substantially from the default us one than the UK one does. Ian. _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Tue Sep 11 07:30:32 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Tue, 11 Sep 2012 07:30:32 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TBKuY-0004RU-JD; Tue, 11 Sep 2012 07:29:30 +0000 Received: from mail27.messagelabs.com ([193.109.254.147]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TBKuX-0004Qe-An for xen-users@lists.xen.org; Tue, 11 Sep 2012 07:29:29 +0000 X-Env-Sender: delentef@gmail.com X-Msg-Ref: server-6.tower-27.messagelabs.com!1347348561!4901792!1 X-Originating-IP: [209.85.210.45] X-SpamReason: No, hits=2.8 required=7.0 tests=HTML_10_20,HTML_MESSAGE, HTML_SHORT_LENGTH,ML_RADAR_SPEW_LINKS_14,RCVD_BY_IP,spamassassin: X-StarScan-Received: X-StarScan-Version: 6.6.1.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 25312 invoked from network); 11 Sep 2012 07:29:23 -0000 Received: from mail-pz0-f45.google.com (HELO mail-pz0-f45.google.com) (209.85.210.45) by server-6.tower-27.messagelabs.com with RC4-SHA encrypted SMTP; 11 Sep 2012 07:29:23 -0000 Received: by dadn15 with SMTP id n15so140125dad.32 for ; Tue, 11 Sep 2012 00:29:21 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; bh=0HBj9MHy9L9ZCBgU1OL1XDPbn58QJPuFQympK4/K8L8=; b=BGraLTNJszUEXgrqvwywq9PcSKMhUq0uMbGnDz5lBGiXeJScmhPC6hQa2K0cLY5UOm f8J5PcUObeoBxLecQAg+2sudQAgS2rCQghZ8ouqIKjNq8n08YWehZFqqE+9WxwemKCUB LpUPAPCAIr+L344xg5rNEQHPGFTG3brLmluWOCm2YSyYPFGHRCWCaAaGgVBYKKBWb94n X7lnOLSszOFPE0ZrlRViJyw+elMFn0yEC1CU+cr03Y7KUtzWdYzfyT42BFrxGdboIuIS dK771vumYvtbrBBcxkAxWWL8YQfBH2cza3LN2Aof8w5Krm+2N6U1UxDWrKvdjW5J1Rgs sCMA== MIME-Version: 1.0 Received: by 10.68.221.168 with SMTP id qf8mr10079227pbc.37.1347348561199; Tue, 11 Sep 2012 00:29:21 -0700 (PDT) Received: by 10.68.203.33 with HTTP; Tue, 11 Sep 2012 00:29:21 -0700 (PDT) In-Reply-To: <1347348275.10570.80.camel@dagon.hellion.org.uk> References: <20120910222214.444b9b72@internecto.net> <1347348275.10570.80.camel@dagon.hellion.org.uk> Date: Tue, 11 Sep 2012 09:29:21 +0200 Message-ID: From: Fabrice Delente To: "xen-users@lists.xen.org" Subject: Re: [Xen-users] Bugs in VNC viewer ? Mouse offset and keyboard map incorrect X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============5155289841793879076==" Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org --===============5155289841793879076== Content-Type: multipart/alternative; boundary=e89a8f838d0361010504c968082b --e89a8f838d0361010504c968082b Content-Type: text/plain; charset=UTF-8 I didn't know about all that, thank you very much, it solved everything! -- Fabrice DELENTE --e89a8f838d0361010504c968082b Content-Type: text/html; charset=UTF-8 I didn't know about all that, thank you very much, it solved everything!

--
Fabrice DELENTE
--e89a8f838d0361010504c968082b-- --===============5155289841793879076== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users --===============5155289841793879076==-- From xen-users-bounces@lists.xen.org Tue Sep 11 07:30:32 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Tue, 11 Sep 2012 07:30:32 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TBKuY-0004RU-JD; Tue, 11 Sep 2012 07:29:30 +0000 Received: from mail27.messagelabs.com ([193.109.254.147]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TBKuX-0004Qe-An for xen-users@lists.xen.org; Tue, 11 Sep 2012 07:29:29 +0000 X-Env-Sender: delentef@gmail.com X-Msg-Ref: server-6.tower-27.messagelabs.com!1347348561!4901792!1 X-Originating-IP: [209.85.210.45] X-SpamReason: No, hits=2.8 required=7.0 tests=HTML_10_20,HTML_MESSAGE, HTML_SHORT_LENGTH,ML_RADAR_SPEW_LINKS_14,RCVD_BY_IP,spamassassin: X-StarScan-Received: X-StarScan-Version: 6.6.1.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 25312 invoked from network); 11 Sep 2012 07:29:23 -0000 Received: from mail-pz0-f45.google.com (HELO mail-pz0-f45.google.com) (209.85.210.45) by server-6.tower-27.messagelabs.com with RC4-SHA encrypted SMTP; 11 Sep 2012 07:29:23 -0000 Received: by dadn15 with SMTP id n15so140125dad.32 for ; Tue, 11 Sep 2012 00:29:21 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; bh=0HBj9MHy9L9ZCBgU1OL1XDPbn58QJPuFQympK4/K8L8=; b=BGraLTNJszUEXgrqvwywq9PcSKMhUq0uMbGnDz5lBGiXeJScmhPC6hQa2K0cLY5UOm f8J5PcUObeoBxLecQAg+2sudQAgS2rCQghZ8ouqIKjNq8n08YWehZFqqE+9WxwemKCUB LpUPAPCAIr+L344xg5rNEQHPGFTG3brLmluWOCm2YSyYPFGHRCWCaAaGgVBYKKBWb94n X7lnOLSszOFPE0ZrlRViJyw+elMFn0yEC1CU+cr03Y7KUtzWdYzfyT42BFrxGdboIuIS dK771vumYvtbrBBcxkAxWWL8YQfBH2cza3LN2Aof8w5Krm+2N6U1UxDWrKvdjW5J1Rgs sCMA== MIME-Version: 1.0 Received: by 10.68.221.168 with SMTP id qf8mr10079227pbc.37.1347348561199; Tue, 11 Sep 2012 00:29:21 -0700 (PDT) Received: by 10.68.203.33 with HTTP; Tue, 11 Sep 2012 00:29:21 -0700 (PDT) In-Reply-To: <1347348275.10570.80.camel@dagon.hellion.org.uk> References: <20120910222214.444b9b72@internecto.net> <1347348275.10570.80.camel@dagon.hellion.org.uk> Date: Tue, 11 Sep 2012 09:29:21 +0200 Message-ID: From: Fabrice Delente To: "xen-users@lists.xen.org" Subject: Re: [Xen-users] Bugs in VNC viewer ? Mouse offset and keyboard map incorrect X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============5155289841793879076==" Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org --===============5155289841793879076== Content-Type: multipart/alternative; boundary=e89a8f838d0361010504c968082b --e89a8f838d0361010504c968082b Content-Type: text/plain; charset=UTF-8 I didn't know about all that, thank you very much, it solved everything! -- Fabrice DELENTE --e89a8f838d0361010504c968082b Content-Type: text/html; charset=UTF-8 I didn't know about all that, thank you very much, it solved everything!

--
Fabrice DELENTE
--e89a8f838d0361010504c968082b-- --===============5155289841793879076== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users --===============5155289841793879076==-- From xen-users-bounces@lists.xen.org Tue Sep 11 07:54:02 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Tue, 11 Sep 2012 07:54:02 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TBLHY-0006BB-DS; Tue, 11 Sep 2012 07:53:16 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TBLHX-0006Aw-9Y for xen-users@lists.xensource.com; Tue, 11 Sep 2012 07:53:15 +0000 Received: from [85.158.143.99:33497] by server-1.bemta-4.messagelabs.com id D4/63-12504-AEDEE405; Tue, 11 Sep 2012 07:53:14 +0000 X-Env-Sender: hahn@univention.de X-Msg-Ref: server-14.tower-216.messagelabs.com!1347349993!20039503!1 X-Originating-IP: [82.198.197.8] X-SpamReason: No, hits=0.0 required=7.0 tests= X-StarScan-Received: X-StarScan-Version: 6.6.1.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 20417 invoked from network); 11 Sep 2012 07:53:13 -0000 Received: from mail.univention.de (HELO mail.univention.de) (82.198.197.8) by server-14.tower-216.messagelabs.com with SMTP; 11 Sep 2012 07:53:13 -0000 Received: from localhost (localhost [127.0.0.1]) by slugis.knut.univention.de (Postfix) with ESMTP id C167E164B105 for ; Tue, 11 Sep 2012 09:53:13 +0200 (CEST) Received: from localhost (localhost [127.0.0.1]) by slugis.knut.univention.de (Postfix) with ESMTP id B6CFB7DF5D1 for ; Tue, 11 Sep 2012 09:53:13 +0200 (CEST) X-Virus-Scanned: by amavisd-new-2.6.1 (20080629) (Debian) at knut.univention.de Received: from mail.univention.de ([127.0.0.1]) by localhost (slugis.knut.univention.de [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ZO+ewo+lF2-l for ; Tue, 11 Sep 2012 09:53:13 +0200 (CEST) Received: from stave.knut.univention.de (mail.univention.de [82.198.197.8]) by slugis.knut.univention.de (Postfix) with ESMTPSA id 587E5164B105 for ; Tue, 11 Sep 2012 09:53:13 +0200 (CEST) From: Philipp Hahn Organization: Univention.de To: xen-users@lists.xensource.com Date: Tue, 11 Sep 2012 09:53:07 +0200 User-Agent: KMail/1.9.10 (enterprise35 20100903.1171286) References: <1347348275.10570.80.camel@dagon.hellion.org.uk> In-Reply-To: X-KMail-QuotePrefix: > MIME-Version: 1.0 Message-Id: <201209110953.11773.hahn@univention.de> Subject: Re: [Xen-users] Bugs in VNC viewer ? Mouse offset and keyboard map incorrect X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============9024083046758876720==" Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org --===============9024083046758876720== Content-Type: multipart/signed; boundary="nextPart2342135.RenJzb0iO4"; protocol="application/pgp-signature"; micalg=pgp-sha1 Content-Transfer-Encoding: 7bit --nextPart2342135.RenJzb0iO4 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline Hello, On Tuesday 11 September 2012 09:29:21 Fabrice Delente wrote: > I didn't know about all that, thank you very much, it solved everything! Daniel P. Berrang=C3=A9 of libvirt fame has written some excellent posts wi= th the=20 gory technical details, why VNC often has keyboard problems: It helped me a lot to understand on how to configure the keyboard layouts t= o=20 make it somehow work. Sincerely Philipp =2D-=20 Philipp Hahn Open Source Software Engineer hahn@univention.de Univention GmbH be open. fon: +49 421 22 232- 0 Mary-Somerville-Str.1 D-28359 Bremen fax: +49 421 22 232-99 http://www.univention.de/ --nextPart2342135.RenJzb0iO4 Content-Type: application/pgp-signature; name=signature.asc Content-Description: This is a digitally signed message part. -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (GNU/Linux) iEYEABECAAYFAlBO7eMACgkQYPlgoZpUDjnbUACguolhsjpajIBZz8o/bLl33trH kV0An3lK7OT5YOafplyWIySbuyVjuFJF =tTID -----END PGP SIGNATURE----- --nextPart2342135.RenJzb0iO4-- --===============9024083046758876720== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users --===============9024083046758876720==-- From xen-users-bounces@lists.xen.org Tue Sep 11 07:54:02 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Tue, 11 Sep 2012 07:54:02 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TBLHY-0006BB-DS; Tue, 11 Sep 2012 07:53:16 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TBLHX-0006Aw-9Y for xen-users@lists.xensource.com; Tue, 11 Sep 2012 07:53:15 +0000 Received: from [85.158.143.99:33497] by server-1.bemta-4.messagelabs.com id D4/63-12504-AEDEE405; Tue, 11 Sep 2012 07:53:14 +0000 X-Env-Sender: hahn@univention.de X-Msg-Ref: server-14.tower-216.messagelabs.com!1347349993!20039503!1 X-Originating-IP: [82.198.197.8] X-SpamReason: No, hits=0.0 required=7.0 tests= X-StarScan-Received: X-StarScan-Version: 6.6.1.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 20417 invoked from network); 11 Sep 2012 07:53:13 -0000 Received: from mail.univention.de (HELO mail.univention.de) (82.198.197.8) by server-14.tower-216.messagelabs.com with SMTP; 11 Sep 2012 07:53:13 -0000 Received: from localhost (localhost [127.0.0.1]) by slugis.knut.univention.de (Postfix) with ESMTP id C167E164B105 for ; Tue, 11 Sep 2012 09:53:13 +0200 (CEST) Received: from localhost (localhost [127.0.0.1]) by slugis.knut.univention.de (Postfix) with ESMTP id B6CFB7DF5D1 for ; Tue, 11 Sep 2012 09:53:13 +0200 (CEST) X-Virus-Scanned: by amavisd-new-2.6.1 (20080629) (Debian) at knut.univention.de Received: from mail.univention.de ([127.0.0.1]) by localhost (slugis.knut.univention.de [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ZO+ewo+lF2-l for ; Tue, 11 Sep 2012 09:53:13 +0200 (CEST) Received: from stave.knut.univention.de (mail.univention.de [82.198.197.8]) by slugis.knut.univention.de (Postfix) with ESMTPSA id 587E5164B105 for ; Tue, 11 Sep 2012 09:53:13 +0200 (CEST) From: Philipp Hahn Organization: Univention.de To: xen-users@lists.xensource.com Date: Tue, 11 Sep 2012 09:53:07 +0200 User-Agent: KMail/1.9.10 (enterprise35 20100903.1171286) References: <1347348275.10570.80.camel@dagon.hellion.org.uk> In-Reply-To: X-KMail-QuotePrefix: > MIME-Version: 1.0 Message-Id: <201209110953.11773.hahn@univention.de> Subject: Re: [Xen-users] Bugs in VNC viewer ? Mouse offset and keyboard map incorrect X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============9024083046758876720==" Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org --===============9024083046758876720== Content-Type: multipart/signed; boundary="nextPart2342135.RenJzb0iO4"; protocol="application/pgp-signature"; micalg=pgp-sha1 Content-Transfer-Encoding: 7bit --nextPart2342135.RenJzb0iO4 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline Hello, On Tuesday 11 September 2012 09:29:21 Fabrice Delente wrote: > I didn't know about all that, thank you very much, it solved everything! Daniel P. Berrang=C3=A9 of libvirt fame has written some excellent posts wi= th the=20 gory technical details, why VNC often has keyboard problems: It helped me a lot to understand on how to configure the keyboard layouts t= o=20 make it somehow work. Sincerely Philipp =2D-=20 Philipp Hahn Open Source Software Engineer hahn@univention.de Univention GmbH be open. fon: +49 421 22 232- 0 Mary-Somerville-Str.1 D-28359 Bremen fax: +49 421 22 232-99 http://www.univention.de/ --nextPart2342135.RenJzb0iO4 Content-Type: application/pgp-signature; name=signature.asc Content-Description: This is a digitally signed message part. -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (GNU/Linux) iEYEABECAAYFAlBO7eMACgkQYPlgoZpUDjnbUACguolhsjpajIBZz8o/bLl33trH kV0An3lK7OT5YOafplyWIySbuyVjuFJF =tTID -----END PGP SIGNATURE----- --nextPart2342135.RenJzb0iO4-- --===============9024083046758876720== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users --===============9024083046758876720==-- From xen-users-bounces@lists.xen.org Tue Sep 11 08:25:34 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Tue, 11 Sep 2012 08:25:34 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TBLm4-0008CM-RE; Tue, 11 Sep 2012 08:24:48 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TBLm3-0008CG-Ut for xen-users@lists.xen.org; Tue, 11 Sep 2012 08:24:48 +0000 Received: from [85.158.143.99:6309] by server-2.bemta-4.messagelabs.com id 7E/83-21239-F45FE405; Tue, 11 Sep 2012 08:24:47 +0000 X-Env-Sender: shoban.preeth@gmail.com X-Msg-Ref: server-10.tower-216.messagelabs.com!1347351870!23270732!1 X-Originating-IP: [209.85.217.173] X-SpamReason: No, hits=0.3 required=7.0 tests=ML_RADAR_SPEW_LINKS_14, RCVD_BY_IP,spamassassin: X-StarScan-Received: X-StarScan-Version: 6.6.1.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 8446 invoked from network); 11 Sep 2012 08:24:30 -0000 Received: from mail-lb0-f173.google.com (HELO mail-lb0-f173.google.com) (209.85.217.173) by server-10.tower-216.messagelabs.com with RC4-SHA encrypted SMTP; 11 Sep 2012 08:24:30 -0000 Received: by lbbgm13 with SMTP id gm13so241013lbb.32 for ; Tue, 11 Sep 2012 01:24:29 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; bh=ZwmCjFL33RgY0JMDeBmlh2ziDXNLnI3zeMxVolNLuy0=; b=0Lnzz/wLjJZkmm6ZQwnh47Kge2EhbW22opK2u7/WNRRpFbcioi+qJJtPwaU+4omMvL euwPxddkdnrjdnk85oUdNU7OTFDS4FM0P8LYRE1XuDdAl9+XJ9laQmqgFIbT36DnE4jV IYejBGrkEf9VhFZe/poT4c54eB49WhanNc9XNWXd6Rl6u4aup+3zZ+GQDrYX/U7OmXVM aSQPUUhCr/cujea+4l1n1SyHn1dd87snTV5Jwtsc4VU4/HbA5pOsGmZKcbI0tDsrgLB7 VvgqqDmK6BnNVFgOicY0FB4hA5L9ijHPtTLUFAylNFd0/QPr05zvugHVbX89hnlXLMc2 IlFg== MIME-Version: 1.0 Received: by 10.112.101.104 with SMTP id ff8mr5660067lbb.45.1347351869718; Tue, 11 Sep 2012 01:24:29 -0700 (PDT) Received: by 10.152.8.15 with HTTP; Tue, 11 Sep 2012 01:24:29 -0700 (PDT) In-Reply-To: References: Date: Tue, 11 Sep 2012 13:54:29 +0530 Message-ID: From: Shoban To: xen-users@lists.xen.org Subject: Re: [Xen-users] Issue with domU RX throughput X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org Nevermind. The issue seemed to be with the switch, and its flow-control mechanism. Thanks, Shoban On Mon, Sep 10, 2012 at 5:36 PM, Shoban wrote: > Hi, > > I am encountering a weird issue, where domU RX throughput (of traffic from > another machine) is very low. But domU RX throughput from dom0 is fine, > and dom0 RX from another machine is fine. iperf reported the following > throughputs: > > dom0 <- outside -- 942Mbps > domU <- dom0 -- 3467Mbps > domU <- outside -- 87Mbps > > The NIC on the machine is 1GE. > > What puzzles me is, some instances of domU (with same config) is able to > achieve almost 1Gbps RX throughput. And this seem to be very random. > > I am running Debian stable (Squeeze) with standard Xen packages, > and standard network setup with linux bridging module. NIC is Broadcomm > BCM5764M GE. > > Please let me know, if more information on configuration/tests is required. > > Thanks, > Shoban _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Tue Sep 11 08:25:34 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Tue, 11 Sep 2012 08:25:34 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TBLm4-0008CM-RE; Tue, 11 Sep 2012 08:24:48 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TBLm3-0008CG-Ut for xen-users@lists.xen.org; Tue, 11 Sep 2012 08:24:48 +0000 Received: from [85.158.143.99:6309] by server-2.bemta-4.messagelabs.com id 7E/83-21239-F45FE405; Tue, 11 Sep 2012 08:24:47 +0000 X-Env-Sender: shoban.preeth@gmail.com X-Msg-Ref: server-10.tower-216.messagelabs.com!1347351870!23270732!1 X-Originating-IP: [209.85.217.173] X-SpamReason: No, hits=0.3 required=7.0 tests=ML_RADAR_SPEW_LINKS_14, RCVD_BY_IP,spamassassin: X-StarScan-Received: X-StarScan-Version: 6.6.1.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 8446 invoked from network); 11 Sep 2012 08:24:30 -0000 Received: from mail-lb0-f173.google.com (HELO mail-lb0-f173.google.com) (209.85.217.173) by server-10.tower-216.messagelabs.com with RC4-SHA encrypted SMTP; 11 Sep 2012 08:24:30 -0000 Received: by lbbgm13 with SMTP id gm13so241013lbb.32 for ; Tue, 11 Sep 2012 01:24:29 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; bh=ZwmCjFL33RgY0JMDeBmlh2ziDXNLnI3zeMxVolNLuy0=; b=0Lnzz/wLjJZkmm6ZQwnh47Kge2EhbW22opK2u7/WNRRpFbcioi+qJJtPwaU+4omMvL euwPxddkdnrjdnk85oUdNU7OTFDS4FM0P8LYRE1XuDdAl9+XJ9laQmqgFIbT36DnE4jV IYejBGrkEf9VhFZe/poT4c54eB49WhanNc9XNWXd6Rl6u4aup+3zZ+GQDrYX/U7OmXVM aSQPUUhCr/cujea+4l1n1SyHn1dd87snTV5Jwtsc4VU4/HbA5pOsGmZKcbI0tDsrgLB7 VvgqqDmK6BnNVFgOicY0FB4hA5L9ijHPtTLUFAylNFd0/QPr05zvugHVbX89hnlXLMc2 IlFg== MIME-Version: 1.0 Received: by 10.112.101.104 with SMTP id ff8mr5660067lbb.45.1347351869718; Tue, 11 Sep 2012 01:24:29 -0700 (PDT) Received: by 10.152.8.15 with HTTP; Tue, 11 Sep 2012 01:24:29 -0700 (PDT) In-Reply-To: References: Date: Tue, 11 Sep 2012 13:54:29 +0530 Message-ID: From: Shoban To: xen-users@lists.xen.org Subject: Re: [Xen-users] Issue with domU RX throughput X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org Nevermind. The issue seemed to be with the switch, and its flow-control mechanism. Thanks, Shoban On Mon, Sep 10, 2012 at 5:36 PM, Shoban wrote: > Hi, > > I am encountering a weird issue, where domU RX throughput (of traffic from > another machine) is very low. But domU RX throughput from dom0 is fine, > and dom0 RX from another machine is fine. iperf reported the following > throughputs: > > dom0 <- outside -- 942Mbps > domU <- dom0 -- 3467Mbps > domU <- outside -- 87Mbps > > The NIC on the machine is 1GE. > > What puzzles me is, some instances of domU (with same config) is able to > achieve almost 1Gbps RX throughput. And this seem to be very random. > > I am running Debian stable (Squeeze) with standard Xen packages, > and standard network setup with linux bridging module. NIC is Broadcomm > BCM5764M GE. > > Please let me know, if more information on configuration/tests is required. > > Thanks, > Shoban _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Tue Sep 11 14:44:08 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Tue, 11 Sep 2012 14:44:08 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TBRfz-0008HZ-0Q; Tue, 11 Sep 2012 14:42:55 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TBRfx-0008HQ-Eo for xen-users@lists.xen.org; Tue, 11 Sep 2012 14:42:53 +0000 Received: from [85.158.143.99:42523] by server-1.bemta-4.messagelabs.com id 46/7F-12504-CED4F405; Tue, 11 Sep 2012 14:42:52 +0000 X-Env-Sender: s.seitz@netzhaut.de X-Msg-Ref: server-6.tower-216.messagelabs.com!1347374570!22745772!1 X-Originating-IP: [212.114.142.59] X-SpamReason: No, hits=0.9 required=7.0 tests=HTML_10_20,HTML_MESSAGE X-StarScan-Received: X-StarScan-Version: 6.6.1.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 23576 invoked from network); 11 Sep 2012 14:42:51 -0000 Received: from remote.netzhaut.de (HELO remote.netzhaut.de) (212.114.142.59) by server-6.tower-216.messagelabs.com with AES128-SHA encrypted SMTP; 11 Sep 2012 14:42:51 -0000 Received: from EXCHANGE.nh.local ([fe80::c860:b1b4:4316:c81e]) by EXCHANGE.nh.local ([fe80::c860:b1b4:4316:c81e%13]) with mapi id 14.01.0355.002; Tue, 11 Sep 2012 16:42:50 +0200 From: Stephan Seitz To: Ian Thread-Topic: [Xen-users] Stall on CPU Thread-Index: AQHNjty3clWGkU/v8kmlIY/DMst3rJeFGCwA Date: Tue, 11 Sep 2012 14:42:49 +0000 Message-ID: <1347374568.7226.12.camel@wotan2> References: <504D17ED.9030105@yahoo.co.uk> In-Reply-To: <504D17ED.9030105@yahoo.co.uk> Accept-Language: de-DE, en-US Content-Language: de-DE X-MS-Has-Attach: yes X-MS-TNEF-Correlator: x-originating-ip: [212.114.142.50] MIME-Version: 1.0 Cc: "xen-users@lists.xen.org" Subject: Re: [Xen-users] Stall on CPU X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============3466945957166837128==" Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org --===============3466945957166837128== Content-Language: de-DE Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="=-W4QsZT7UiRWsGlRPgsBP" --=-W4QsZT7UiRWsGlRPgsBP Content-Type: multipart/alternative; boundary="=-shbzO0Wi0DlnQ9xe0gCH" --=-shbzO0Wi0DlnQ9xe0gCH Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Hi, I've also seen that "rcu sched detected stalls on CPU x", but on dom0, not domU. The dom0 which had this error (leading to a complete system stop) is running xen 4.1.3 and vanilla 3.5.2 as dom0 kernel. I know, I should go with the xenified kernels, but I'm currently evaluating tmem features on recent kernels. Another machine which hit that "rcu sched" was a baremetal 3.1.1 acting as scst target. I've got the feeling the error can be triggered by heavy I/O, but to be honest, I don't have any glue what to do against it. Cheers, - Stephan Am Sonntag, den 09.09.2012, 23:27 +0100 schrieb Ian: > Hi, >=20 > I have been receiving messages on a new DomU's kern.log. I've done a lot= =20 > of googling, but haven't came up with anything very useful, at least not= =20 > in a Xen context. >=20 > I was wondering if anyone had any suggestions about what could be wrong.= =20 > From everything I have read, there should be a stack trace included, but= =20 > I am not seeing one. >=20 > Thanks in advance, >=20 > Ian. >=20 > on Xen 4.1.2... > Sep 6 13:04:07 davical kernel: [12008.080091] INFO: rcu_sched detected= =20 > stall on CPU 1 (t=3D50460 jiffies) > Sep 6 13:04:07 davical kernel: [12008.084081] sending NMI to all CPUs: > Sep 6 13:04:07 davical kernel: [11806.576064] INFO: rcu_sched detected= =20 > stalls on CPUs/tasks: { 1} (detected by 0, t=3D566314 jiffies) > Sep 6 13:04:07 davical kernel: [75644.150936] INFO: rcu_sched detected= =20 > stall on CPU 0 (t=3D15393163 jiffies) > Sep 6 13:04:07 davical kernel: [75644.304186] sched: RT throttling=20 > activated >=20 > on Xen 4.1.3... > Sep 8 11:39:40 davical kernel: [62220.039363] INFO: rcu_sched detected= =20 > stall on CPU 1 (t=3D355732 jiffies) > Sep 8 11:39:40 davical kernel: [62220.039363] sending NMI to all CPUs: > Sep 8 11:39:40 davical kernel: [124714.197152] INFO: rcu_sched detected= =20 > stalls on CPUs/tasks: { 1} (detected by 0, t=3D355732 jiffies) > Sep 8 11:39:48 davical kernel: [124721.756263] INFO: rcu_sched detected= =20 > stall on CPU 1 (t=3D15751455 jiffies) > Sep 8 11:39:48 davical kernel: [124721.756328] sending NMI to all CPUs: > Sep 8 11:39:48 davical kernel: [124721.760199] INFO: rcu_sched detected= =20 > stalls on CPUs/tasks: { 1} (detected by 0, t=3D15751455 jiffies) > Sep 8 11:39:52 davical kernel: [124725.855952] ipv6_create_tempaddr():= =20 > retry temporary address regeneration. > Sep 8 11:40:08 davical kernel: [124721.760226] INFO: rcu_bh detected=20 > stall on CPU 1 (t=3D15395723 jiffies) > Sep 8 11:40:08 davical kernel: [124721.760226] sending NMI to all CPUs: > Sep 8 11:40:08 davical kernel: [124742.485888] sched: RT throttling=20 > activated >=20 >=20 >=20 > I have tried it on two Xen Dom0 installations, one of 4.1.2 and the=20 > other on 4.1.3. >=20 > The 4.1.2 Dom0 machine is a scientific linux installation using a custom= =20 > compiled kernel, 3.4.0+. >=20 > The 4.1.3 Dom0 machine is using a standard Ubuntu server kernel=20 > 3.2.0-29-generic-pae >=20 > The domU is an Ubuntu 12.04.1 server based using a standard Ubuntu=20 > 12.04.1 kernel, also 3.2.0-29-generic-pae. >=20 > xl info of the 4.1.2 machine: >=20 > host : xen3 > release : 3.4.0+ > version : #1 SMP Mon Jun 4 12:41:14 BST 2012 > machine : x86_64 > nr_cpus : 4 > nr_nodes : 1 > cores_per_socket : 4 > threads_per_core : 1 > cpu_mhz : 2300 > hw_caps :=20 > 178bf3ff:efd3fbff:00000000:00001310:00802001:00000000:000007ff:00000000 > virt_caps : hvm > total_memory : 8159 > free_memory : 3866 > free_cpus : 0 > xen_major : 4 > xen_minor : 1 > xen_extra : .2 > xen_caps : xen-3.0-x86_64 xen-3.0-x86_32p hvm-3.0-x86_32= =20 > hvm-3.0-x86_32p hvm-3.0-x86_64 > xen_scheduler : credit > xen_pagesize : 4096 > platform_params : virt_start=3D0xffff800000000000 > xen_changeset : unavailable > xen_commandline : loglvl=3Dall guesloglvl=3Dall > cc_compiler : gcc version 4.4.5 20110214 (Red Hat 4.4.5-6) (GC= C) > cc_compile_by : root > cc_compile_domain : (none) > cc_compile_date : Sun Jan 22 01:18:42 GMT 2012 > xend_config_format : 4 >=20 >=20 > xl info of the 4.1.3 machine: >=20 > host : xen5 > release : 3.2.0-29-generic-pae > version : #46-Ubuntu SMP Fri Jul 27 17:25:43 UTC 2012 > machine : i686 > nr_cpus : 2 > nr_nodes : 1 > cores_per_socket : 2 > threads_per_core : 1 > cpu_mhz : 1995 > hw_caps :=20 > bfe9fbff:00100000:00000000:00000940:0000c1a9:00000000:00000000:00000000 > virt_caps : > total_memory : 3062 > free_memory : 173 > free_cpus : 0 > xen_major : 4 > xen_minor : 1 > xen_extra : .3 > xen_caps : xen-3.0-x86_32p > xen_scheduler : credit > xen_pagesize : 4096 > platform_params : virt_start=3D0xf5800000 > xen_changeset : unavailable > xen_commandline : placeholder > cc_compiler : gcc version 4.6.3 (Ubuntu/Linaro 4.6.3-1ubuntu5) > cc_compile_by : root > cc_compile_domain : local > cc_compile_date : Thu Sep 6 01:53:48 BST 2012 > xend_config_format : 4 >=20 > DomU config file: >=20 > cat ubuntu-calendar > name =3D "ubuntu-calendar" > memory =3D 1024 > disk =3D ['phy:/dev/xen5/ubuntu-calendar,xvda,w'] > vif =3D [ 'mac=3D00:16:31:50:01:03' ] > bootloader=3D"/usr/bin/pygrub" > vfb =3D [ "type=3Dvnc,vncunused=3D1,vnclisten=3D0.0.0.0" ] > vcpus =3D 2 > on_reboot =3D 'restart' > on_crash =3D 'restart' >=20 > DomU's grub.lst.... >=20 > menuentry 'Ubuntu, with Linux 3.2.0-29-generic' --class ubuntu --class= =20 > gnu-linux > --class gnu --class os { > recordfail > insmod ext2 > set root=3D'(hd0,1)' > search --no-floppy --fs-uuid --set=3Droot=20 > 70149f72-3c4f-4608-bebd-06825b91 > ce29 > linux /boot/vmlinuz-3.2.0-29-generic-pae=20 > root=3DUUID=3D70149f72-3c4f-4608- > bebd-06825b91ce29 ro quiet splash set default=3D"0" > set timeout=3D5 > menuentry 'Ubuntu GNU/Linux, with Xen 4.1-amd64 and Linux=20 > 3.2.0-23-generic' --class ubuntu --class gnu-linux --class gnu --class= =20 > os --class xen { > insmod part_msdos > insmod ext2 > set root=3D'(hd0,msdos1)' > search --no-floppy --fs-uuid --set=3Droot=20 > 1b478986-8c02-4a79-ad61-cf8f418e35ad > echo 'Loading Xen 4.1-amd64 ...' > multiboot /xen.gz placeholder > echo 'Loading Linux 3.2.0-29-generic-pae ...' > module /vmlinuz-3.2.0-29-generic-pae placeholder=20 > root=3D/dev/mapper/xen5-root ro > echo 'Loading initial ramdisk ...' > module /initrd.img-3.2.0-29-generic-pae > } > xen-fbfront.video=3D16,1024,768 $vt_handoff > initrd /boot/initrd.img-3.2.0-29-generic-pae >=20 >=20 > Dom0's grub.lst (4.1.3)... >=20 > set default=3D"0" > set timeout=3D5 > menuentry 'Ubuntu GNU/Linux, with Xen 4.1-amd64 and Linux=20 > 3.2.0-23-generic' --class ubuntu --class gnu-linux --class gnu --class= =20 > os --class xen { > insmod part_msdos > insmod ext2 > set root=3D'(hd0,msdos1)' > search --no-floppy --fs-uuid --set=3Droot=20 > 1b478986-8c02-4a79-ad61-cf8f418e35ad > echo 'Loading Xen 4.1-amd64 ...' > multiboot /xen.gz placeholder > echo 'Loading Linux 3.2.0-29-generic-pae ...' > module /vmlinuz-3.2.0-29-generic-pae placeholder=20 > root=3D/dev/mapper/xen5-root ro > echo 'Loading initial ramdisk ...' > module /initrd.img-3.2.0-29-generic-pae > } >=20 >=20 >=20 >=20 >=20 >=20 >=20 >=20 >=20 > _______________________________________________ > Xen-users mailing list > Xen-users@lists.xen.org > http://lists.xen.org/xen-users --=-shbzO0Wi0DlnQ9xe0gCH Content-Type: text/html; charset="utf-8" Content-Transfer-Encoding: quoted-printable Hi,

I've also seen that "rcu sched detected stalls on CPU x", but on = dom0, not domU.
The dom0 which had this error (leading to a complete system stop) is runnin= g xen 4.1.3
and vanilla 3.5.2 as dom0 kernel.
I know, I should go with the xenified kernels, but I'm currently evaluating= tmem features on recent
kernels.

Another machine which hit that "rcu sched" was a baremetal 3.1.1 = acting as scst target.

I've got the feeling the error can be triggered by heavy I/O, but to be hon= est, I don't have
any glue what to do against it.


Cheers,

- Stephan
Am Sonntag, den 09.09.2012, 23:27 +0100 schrieb Ian: 
Hi,

I have been receiving messages on a new DomU's kern.log. I've done a lot=
=20
of googling, but haven't came up with anything very useful, at least not=
=20
in a Xen context.

I was wondering if anyone had any suggestions about what could be wrong.=
=20
=46rom everything I have read, there should be a stack trace included, but=
=20
I am not seeing one.

Thanks in advance,

Ian.

on Xen 4.1.2...
Sep  6 13:04:07 davical kernel: [12008.080091] INFO: rcu_sched detected=20
stall on CPU 1 (t=3D50460 jiffies)
Sep  6 13:04:07 davical kernel: [12008.084081] sending NMI to all CPUs:
Sep  6 13:04:07 davical kernel: [11806.576064] INFO: rcu_sched detected=20
stalls on CPUs/tasks: { 1} (detected by 0, t=3D566314 jiffies)
Sep  6 13:04:07 davical kernel: [75644.150936] INFO: rcu_sched detected=20
stall on  CPU 0 (t=3D15393163 jiffies)
Sep  6 13:04:07 davical kernel: [75644.304186] sched: RT throttling=20
activated

on Xen 4.1.3...
Sep  8 11:39:40 davical kernel: [62220.039363] INFO: rcu_sched detected=20
stall on CPU 1 (t=3D355732 jiffies)
Sep  8 11:39:40 davical kernel: [62220.039363] sending NMI to all CPUs:
Sep  8 11:39:40 davical kernel: [124714.197152] INFO: rcu_sched detected=
=20
stalls on CPUs/tasks: { 1} (detected by 0, t=3D355732 jiffies)
Sep  8 11:39:48 davical kernel: [124721.756263] INFO: rcu_sched detected=
=20
stall on CPU 1 (t=3D15751455 jiffies)
Sep  8 11:39:48 davical kernel: [124721.756328] sending NMI to all CPUs:
Sep  8 11:39:48 davical kernel: [124721.760199] INFO: rcu_sched detected=
=20
stalls on CPUs/tasks: { 1} (detected by 0, t=3D15751455 jiffies)
Sep  8 11:39:52 davical kernel: [124725.855952] ipv6_create_tempaddr():=20
retry temporary address regeneration.
Sep  8 11:40:08 davical kernel: [124721.760226] INFO: rcu_bh detected=20
stall on CPU 1 (t=3D15395723 jiffies)
Sep  8 11:40:08 davical kernel: [124721.760226] sending NMI to all CPUs:
Sep  8 11:40:08 davical kernel: [124742.485888] sched: RT throttling=20
activated



I have tried it on two Xen Dom0 installations, one of 4.1.2 and the=20
other on 4.1.3.

The 4.1.2 Dom0 machine is a scientific linux installation using a custom=
=20
compiled kernel, 3.4.0+.

The 4.1.3 Dom0 machine is using a standard Ubuntu server kernel=20
3.2.0-29-generic-pae

The domU is an Ubuntu 12.04.1 server based using a standard Ubuntu=20
12.04.1 kernel, also 3.2.0-29-generic-pae.

xl info of the 4.1.2 machine:

host                   : xen3
release                : 3.4.0+
version                : #1 SMP Mon Jun 4 12:41:14 BST 2012
machine                : x86_64
nr_cpus                : 4
nr_nodes               : 1
cores_per_socket       : 4
threads_per_core       : 1
cpu_mhz                : 2300
hw_caps                :=20
178bf3ff:efd3fbff:00000000:00001310:00802001:00000000:000007ff:00000000
virt_caps              : hvm
total_memory           : 8159
free_memory            : 3866
free_cpus              : 0
xen_major              : 4
xen_minor              : 1
xen_extra              : .2
xen_caps               : xen-3.0-x86_64 xen-3.0-x86_32p hvm-3.0-x86_32=20
hvm-3.0-x86_32p hvm-3.0-x86_64
xen_scheduler          : credit
xen_pagesize           : 4096
platform_params        : virt_start=3D0xffff800000000000
xen_changeset          : unavailable
xen_commandline        : loglvl=3Dall guesloglvl=3Dall
cc_compiler            : gcc version 4.4.5 20110214 (Red Hat 4.4.5-6) (GCC)
cc_compile_by          : root
cc_compile_domain      : (none)
cc_compile_date        : Sun Jan 22 01:18:42 GMT 2012
xend_config_format     : 4


xl info of the 4.1.3 machine:

host                   : xen5
release                : 3.2.0-29-generic-pae
version                : #46-Ubuntu SMP Fri Jul 27 17:25:43 UTC 2012
machine                : i686
nr_cpus                : 2
nr_nodes               : 1
cores_per_socket       : 2
threads_per_core       : 1
cpu_mhz                : 1995
hw_caps                :=20
bfe9fbff:00100000:00000000:00000940:0000c1a9:00000000:00000000:00000000
virt_caps              :
total_memory           : 3062
free_memory            : 173
free_cpus              : 0
xen_major              : 4
xen_minor              : 1
xen_extra              : .3
xen_caps               : xen-3.0-x86_32p
xen_scheduler          : credit
xen_pagesize           : 4096
platform_params        : virt_start=3D0xf5800000
xen_changeset          : unavailable
xen_commandline        : placeholder
cc_compiler            : gcc version 4.6.3 (Ubuntu/Linaro 4.6.3-1ubuntu5)
cc_compile_by          : root
cc_compile_domain      : local
cc_compile_date        : Thu Sep  6 01:53:48 BST 2012
xend_config_format     : 4

DomU config file:

cat ubuntu-calendar
name      =3D "ubuntu-calendar"
memory    =3D 1024
disk      =3D ['phy:/dev/xen5/ubuntu-calendar,xvda,w']
vif =3D [ 'mac=3D00:16:31:50:01:03' ]
bootloader=3D"/usr/bin/pygrub"
vfb =3D [ "type=3Dvnc,vncunused=3D1,vnclisten=3D0.0.0.0" ]
vcpus     =3D 2
on_reboot =3D 'restart'
on_crash  =3D 'restart'

DomU's grub.lst....

menuentry 'Ubuntu, with Linux 3.2.0-29-generic' --class ubuntu --class=20
gnu-linux
  --class gnu --class os {
         recordfail
         insmod ext2
         set root=3D'(hd0,1)'
         search --no-floppy --fs-uuid --set=3Droot=20
70149f72-3c4f-4608-bebd-06825b91
ce29
         linux   /boot/vmlinuz-3.2.0-29-generic-pae=20
root=3DUUID=3D70149f72-3c4f-4608-
bebd-06825b91ce29 ro   quiet splash set default=3D"0"
set timeout=3D5
menuentry 'Ubuntu GNU/Linux, with Xen 4.1-amd64 and Linux=20
3.2.0-23-generic' --class ubuntu --class gnu-linux --class gnu --class=20
os --class xen {
     insmod part_msdos
     insmod ext2
     set root=3D'(hd0,msdos1)'
     search --no-floppy --fs-uuid --set=3Droot=20
1b478986-8c02-4a79-ad61-cf8f418e35ad
     echo    'Loading Xen 4.1-amd64 ...'
     multiboot    /xen.gz placeholder
     echo    'Loading Linux 3.2.0-29-generic-pae ...'
     module    /vmlinuz-3.2.0-29-generic-pae placeholder=20
root=3D/dev/mapper/xen5-root ro
     echo    'Loading initial ramdisk ...'
     module    /initrd.img-3.2.0-29-generic-pae
}
xen-fbfront.video=3D16,1024,768 $vt_handoff
         initrd  /boot/initrd.img-3.2.0-29-generic-pae


Dom0's grub.lst (4.1.3)...

set default=3D"0"
set timeout=3D5
menuentry 'Ubuntu GNU/Linux, with Xen 4.1-amd64 and Linux=20
3.2.0-23-generic' --class ubuntu --class gnu-linux --class gnu --class=20
os --class xen {
     insmod part_msdos
     insmod ext2
     set root=3D'(hd0,msdos1)'
     search --no-floppy --fs-uuid --set=3Droot=20
1b478986-8c02-4a79-ad61-cf8f418e35ad
     echo    'Loading Xen 4.1-amd64 ...'
     multiboot    /xen.gz placeholder
     echo    'Loading Linux 3.2.0-29-generic-pae ...'
     module    /vmlinuz-3.2.0-29-generic-pae placeholder=20
root=3D/dev/mapper/xen5-root ro
     echo    'Loading initial ramdisk ...'
     module    /initrd.img-3.2.0-29-generic-pae
}









_______________________________________________
Xen-users mailing list
Xen-users@lists.xen.org
http://lists.xen.org/xen-users
--=-shbzO0Wi0DlnQ9xe0gCH-- --=-W4QsZT7UiRWsGlRPgsBP Content-Type: application/pgp-signature; name="signature.asc" Content-Description: This is a digitally signed message part Content-Transfer-Encoding: 7bit -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.11 (GNU/Linux) iQEcBAABAgAGBQJQT03oAAoJEHzu36SveClljEoIAIR6nMFNSmDJoBlVTdsB49PD 2qwGlBNp04RFaAxkLIedfaL0pXmAYR4yPGuiZvN0hnAL1PrR+4462cBAe+bHBPwB oXwOJ/BjDar2i3bOxikND77EK6yob0Gld5SWfgKX/K5S/Trp4viHNnUI9GVNV+aJ Z3yH4pbBwANe85Wkauzdo1DbHIBdOhbxX8Enj4um1H5QvNrkGchMZZkl4oGDv+Kc KFV9jUTj5X5GzpEMzD7HyS7pENoLbrQsesLBvsHYM7qdrBYbOOczGg2QH7sU6yp/ NY6zUMOZM/IFVI6dqaMHgtkpfUkXWNygkTwVj7RYjOjCTLr6CYNu7IkTmd7zayo= =b9bW -----END PGP SIGNATURE----- --=-W4QsZT7UiRWsGlRPgsBP-- --===============3466945957166837128== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users --===============3466945957166837128==-- From xen-users-bounces@lists.xen.org Tue Sep 11 14:44:08 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Tue, 11 Sep 2012 14:44:08 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TBRfz-0008HZ-0Q; Tue, 11 Sep 2012 14:42:55 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TBRfx-0008HQ-Eo for xen-users@lists.xen.org; Tue, 11 Sep 2012 14:42:53 +0000 Received: from [85.158.143.99:42523] by server-1.bemta-4.messagelabs.com id 46/7F-12504-CED4F405; Tue, 11 Sep 2012 14:42:52 +0000 X-Env-Sender: s.seitz@netzhaut.de X-Msg-Ref: server-6.tower-216.messagelabs.com!1347374570!22745772!1 X-Originating-IP: [212.114.142.59] X-SpamReason: No, hits=0.9 required=7.0 tests=HTML_10_20,HTML_MESSAGE X-StarScan-Received: X-StarScan-Version: 6.6.1.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 23576 invoked from network); 11 Sep 2012 14:42:51 -0000 Received: from remote.netzhaut.de (HELO remote.netzhaut.de) (212.114.142.59) by server-6.tower-216.messagelabs.com with AES128-SHA encrypted SMTP; 11 Sep 2012 14:42:51 -0000 Received: from EXCHANGE.nh.local ([fe80::c860:b1b4:4316:c81e]) by EXCHANGE.nh.local ([fe80::c860:b1b4:4316:c81e%13]) with mapi id 14.01.0355.002; Tue, 11 Sep 2012 16:42:50 +0200 From: Stephan Seitz To: Ian Thread-Topic: [Xen-users] Stall on CPU Thread-Index: AQHNjty3clWGkU/v8kmlIY/DMst3rJeFGCwA Date: Tue, 11 Sep 2012 14:42:49 +0000 Message-ID: <1347374568.7226.12.camel@wotan2> References: <504D17ED.9030105@yahoo.co.uk> In-Reply-To: <504D17ED.9030105@yahoo.co.uk> Accept-Language: de-DE, en-US Content-Language: de-DE X-MS-Has-Attach: yes X-MS-TNEF-Correlator: x-originating-ip: [212.114.142.50] MIME-Version: 1.0 Cc: "xen-users@lists.xen.org" Subject: Re: [Xen-users] Stall on CPU X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============3466945957166837128==" Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org --===============3466945957166837128== Content-Language: de-DE Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="=-W4QsZT7UiRWsGlRPgsBP" --=-W4QsZT7UiRWsGlRPgsBP Content-Type: multipart/alternative; boundary="=-shbzO0Wi0DlnQ9xe0gCH" --=-shbzO0Wi0DlnQ9xe0gCH Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Hi, I've also seen that "rcu sched detected stalls on CPU x", but on dom0, not domU. The dom0 which had this error (leading to a complete system stop) is running xen 4.1.3 and vanilla 3.5.2 as dom0 kernel. I know, I should go with the xenified kernels, but I'm currently evaluating tmem features on recent kernels. Another machine which hit that "rcu sched" was a baremetal 3.1.1 acting as scst target. I've got the feeling the error can be triggered by heavy I/O, but to be honest, I don't have any glue what to do against it. Cheers, - Stephan Am Sonntag, den 09.09.2012, 23:27 +0100 schrieb Ian: > Hi, >=20 > I have been receiving messages on a new DomU's kern.log. I've done a lot= =20 > of googling, but haven't came up with anything very useful, at least not= =20 > in a Xen context. >=20 > I was wondering if anyone had any suggestions about what could be wrong.= =20 > From everything I have read, there should be a stack trace included, but= =20 > I am not seeing one. >=20 > Thanks in advance, >=20 > Ian. >=20 > on Xen 4.1.2... > Sep 6 13:04:07 davical kernel: [12008.080091] INFO: rcu_sched detected= =20 > stall on CPU 1 (t=3D50460 jiffies) > Sep 6 13:04:07 davical kernel: [12008.084081] sending NMI to all CPUs: > Sep 6 13:04:07 davical kernel: [11806.576064] INFO: rcu_sched detected= =20 > stalls on CPUs/tasks: { 1} (detected by 0, t=3D566314 jiffies) > Sep 6 13:04:07 davical kernel: [75644.150936] INFO: rcu_sched detected= =20 > stall on CPU 0 (t=3D15393163 jiffies) > Sep 6 13:04:07 davical kernel: [75644.304186] sched: RT throttling=20 > activated >=20 > on Xen 4.1.3... > Sep 8 11:39:40 davical kernel: [62220.039363] INFO: rcu_sched detected= =20 > stall on CPU 1 (t=3D355732 jiffies) > Sep 8 11:39:40 davical kernel: [62220.039363] sending NMI to all CPUs: > Sep 8 11:39:40 davical kernel: [124714.197152] INFO: rcu_sched detected= =20 > stalls on CPUs/tasks: { 1} (detected by 0, t=3D355732 jiffies) > Sep 8 11:39:48 davical kernel: [124721.756263] INFO: rcu_sched detected= =20 > stall on CPU 1 (t=3D15751455 jiffies) > Sep 8 11:39:48 davical kernel: [124721.756328] sending NMI to all CPUs: > Sep 8 11:39:48 davical kernel: [124721.760199] INFO: rcu_sched detected= =20 > stalls on CPUs/tasks: { 1} (detected by 0, t=3D15751455 jiffies) > Sep 8 11:39:52 davical kernel: [124725.855952] ipv6_create_tempaddr():= =20 > retry temporary address regeneration. > Sep 8 11:40:08 davical kernel: [124721.760226] INFO: rcu_bh detected=20 > stall on CPU 1 (t=3D15395723 jiffies) > Sep 8 11:40:08 davical kernel: [124721.760226] sending NMI to all CPUs: > Sep 8 11:40:08 davical kernel: [124742.485888] sched: RT throttling=20 > activated >=20 >=20 >=20 > I have tried it on two Xen Dom0 installations, one of 4.1.2 and the=20 > other on 4.1.3. >=20 > The 4.1.2 Dom0 machine is a scientific linux installation using a custom= =20 > compiled kernel, 3.4.0+. >=20 > The 4.1.3 Dom0 machine is using a standard Ubuntu server kernel=20 > 3.2.0-29-generic-pae >=20 > The domU is an Ubuntu 12.04.1 server based using a standard Ubuntu=20 > 12.04.1 kernel, also 3.2.0-29-generic-pae. >=20 > xl info of the 4.1.2 machine: >=20 > host : xen3 > release : 3.4.0+ > version : #1 SMP Mon Jun 4 12:41:14 BST 2012 > machine : x86_64 > nr_cpus : 4 > nr_nodes : 1 > cores_per_socket : 4 > threads_per_core : 1 > cpu_mhz : 2300 > hw_caps :=20 > 178bf3ff:efd3fbff:00000000:00001310:00802001:00000000:000007ff:00000000 > virt_caps : hvm > total_memory : 8159 > free_memory : 3866 > free_cpus : 0 > xen_major : 4 > xen_minor : 1 > xen_extra : .2 > xen_caps : xen-3.0-x86_64 xen-3.0-x86_32p hvm-3.0-x86_32= =20 > hvm-3.0-x86_32p hvm-3.0-x86_64 > xen_scheduler : credit > xen_pagesize : 4096 > platform_params : virt_start=3D0xffff800000000000 > xen_changeset : unavailable > xen_commandline : loglvl=3Dall guesloglvl=3Dall > cc_compiler : gcc version 4.4.5 20110214 (Red Hat 4.4.5-6) (GC= C) > cc_compile_by : root > cc_compile_domain : (none) > cc_compile_date : Sun Jan 22 01:18:42 GMT 2012 > xend_config_format : 4 >=20 >=20 > xl info of the 4.1.3 machine: >=20 > host : xen5 > release : 3.2.0-29-generic-pae > version : #46-Ubuntu SMP Fri Jul 27 17:25:43 UTC 2012 > machine : i686 > nr_cpus : 2 > nr_nodes : 1 > cores_per_socket : 2 > threads_per_core : 1 > cpu_mhz : 1995 > hw_caps :=20 > bfe9fbff:00100000:00000000:00000940:0000c1a9:00000000:00000000:00000000 > virt_caps : > total_memory : 3062 > free_memory : 173 > free_cpus : 0 > xen_major : 4 > xen_minor : 1 > xen_extra : .3 > xen_caps : xen-3.0-x86_32p > xen_scheduler : credit > xen_pagesize : 4096 > platform_params : virt_start=3D0xf5800000 > xen_changeset : unavailable > xen_commandline : placeholder > cc_compiler : gcc version 4.6.3 (Ubuntu/Linaro 4.6.3-1ubuntu5) > cc_compile_by : root > cc_compile_domain : local > cc_compile_date : Thu Sep 6 01:53:48 BST 2012 > xend_config_format : 4 >=20 > DomU config file: >=20 > cat ubuntu-calendar > name =3D "ubuntu-calendar" > memory =3D 1024 > disk =3D ['phy:/dev/xen5/ubuntu-calendar,xvda,w'] > vif =3D [ 'mac=3D00:16:31:50:01:03' ] > bootloader=3D"/usr/bin/pygrub" > vfb =3D [ "type=3Dvnc,vncunused=3D1,vnclisten=3D0.0.0.0" ] > vcpus =3D 2 > on_reboot =3D 'restart' > on_crash =3D 'restart' >=20 > DomU's grub.lst.... >=20 > menuentry 'Ubuntu, with Linux 3.2.0-29-generic' --class ubuntu --class= =20 > gnu-linux > --class gnu --class os { > recordfail > insmod ext2 > set root=3D'(hd0,1)' > search --no-floppy --fs-uuid --set=3Droot=20 > 70149f72-3c4f-4608-bebd-06825b91 > ce29 > linux /boot/vmlinuz-3.2.0-29-generic-pae=20 > root=3DUUID=3D70149f72-3c4f-4608- > bebd-06825b91ce29 ro quiet splash set default=3D"0" > set timeout=3D5 > menuentry 'Ubuntu GNU/Linux, with Xen 4.1-amd64 and Linux=20 > 3.2.0-23-generic' --class ubuntu --class gnu-linux --class gnu --class= =20 > os --class xen { > insmod part_msdos > insmod ext2 > set root=3D'(hd0,msdos1)' > search --no-floppy --fs-uuid --set=3Droot=20 > 1b478986-8c02-4a79-ad61-cf8f418e35ad > echo 'Loading Xen 4.1-amd64 ...' > multiboot /xen.gz placeholder > echo 'Loading Linux 3.2.0-29-generic-pae ...' > module /vmlinuz-3.2.0-29-generic-pae placeholder=20 > root=3D/dev/mapper/xen5-root ro > echo 'Loading initial ramdisk ...' > module /initrd.img-3.2.0-29-generic-pae > } > xen-fbfront.video=3D16,1024,768 $vt_handoff > initrd /boot/initrd.img-3.2.0-29-generic-pae >=20 >=20 > Dom0's grub.lst (4.1.3)... >=20 > set default=3D"0" > set timeout=3D5 > menuentry 'Ubuntu GNU/Linux, with Xen 4.1-amd64 and Linux=20 > 3.2.0-23-generic' --class ubuntu --class gnu-linux --class gnu --class= =20 > os --class xen { > insmod part_msdos > insmod ext2 > set root=3D'(hd0,msdos1)' > search --no-floppy --fs-uuid --set=3Droot=20 > 1b478986-8c02-4a79-ad61-cf8f418e35ad > echo 'Loading Xen 4.1-amd64 ...' > multiboot /xen.gz placeholder > echo 'Loading Linux 3.2.0-29-generic-pae ...' > module /vmlinuz-3.2.0-29-generic-pae placeholder=20 > root=3D/dev/mapper/xen5-root ro > echo 'Loading initial ramdisk ...' > module /initrd.img-3.2.0-29-generic-pae > } >=20 >=20 >=20 >=20 >=20 >=20 >=20 >=20 >=20 > _______________________________________________ > Xen-users mailing list > Xen-users@lists.xen.org > http://lists.xen.org/xen-users --=-shbzO0Wi0DlnQ9xe0gCH Content-Type: text/html; charset="utf-8" Content-Transfer-Encoding: quoted-printable Hi,

I've also seen that "rcu sched detected stalls on CPU x", but on = dom0, not domU.
The dom0 which had this error (leading to a complete system stop) is runnin= g xen 4.1.3
and vanilla 3.5.2 as dom0 kernel.
I know, I should go with the xenified kernels, but I'm currently evaluating= tmem features on recent
kernels.

Another machine which hit that "rcu sched" was a baremetal 3.1.1 = acting as scst target.

I've got the feeling the error can be triggered by heavy I/O, but to be hon= est, I don't have
any glue what to do against it.


Cheers,

- Stephan
Am Sonntag, den 09.09.2012, 23:27 +0100 schrieb Ian: 
Hi,

I have been receiving messages on a new DomU's kern.log. I've done a lot=
=20
of googling, but haven't came up with anything very useful, at least not=
=20
in a Xen context.

I was wondering if anyone had any suggestions about what could be wrong.=
=20
=46rom everything I have read, there should be a stack trace included, but=
=20
I am not seeing one.

Thanks in advance,

Ian.

on Xen 4.1.2...
Sep  6 13:04:07 davical kernel: [12008.080091] INFO: rcu_sched detected=20
stall on CPU 1 (t=3D50460 jiffies)
Sep  6 13:04:07 davical kernel: [12008.084081] sending NMI to all CPUs:
Sep  6 13:04:07 davical kernel: [11806.576064] INFO: rcu_sched detected=20
stalls on CPUs/tasks: { 1} (detected by 0, t=3D566314 jiffies)
Sep  6 13:04:07 davical kernel: [75644.150936] INFO: rcu_sched detected=20
stall on  CPU 0 (t=3D15393163 jiffies)
Sep  6 13:04:07 davical kernel: [75644.304186] sched: RT throttling=20
activated

on Xen 4.1.3...
Sep  8 11:39:40 davical kernel: [62220.039363] INFO: rcu_sched detected=20
stall on CPU 1 (t=3D355732 jiffies)
Sep  8 11:39:40 davical kernel: [62220.039363] sending NMI to all CPUs:
Sep  8 11:39:40 davical kernel: [124714.197152] INFO: rcu_sched detected=
=20
stalls on CPUs/tasks: { 1} (detected by 0, t=3D355732 jiffies)
Sep  8 11:39:48 davical kernel: [124721.756263] INFO: rcu_sched detected=
=20
stall on CPU 1 (t=3D15751455 jiffies)
Sep  8 11:39:48 davical kernel: [124721.756328] sending NMI to all CPUs:
Sep  8 11:39:48 davical kernel: [124721.760199] INFO: rcu_sched detected=
=20
stalls on CPUs/tasks: { 1} (detected by 0, t=3D15751455 jiffies)
Sep  8 11:39:52 davical kernel: [124725.855952] ipv6_create_tempaddr():=20
retry temporary address regeneration.
Sep  8 11:40:08 davical kernel: [124721.760226] INFO: rcu_bh detected=20
stall on CPU 1 (t=3D15395723 jiffies)
Sep  8 11:40:08 davical kernel: [124721.760226] sending NMI to all CPUs:
Sep  8 11:40:08 davical kernel: [124742.485888] sched: RT throttling=20
activated



I have tried it on two Xen Dom0 installations, one of 4.1.2 and the=20
other on 4.1.3.

The 4.1.2 Dom0 machine is a scientific linux installation using a custom=
=20
compiled kernel, 3.4.0+.

The 4.1.3 Dom0 machine is using a standard Ubuntu server kernel=20
3.2.0-29-generic-pae

The domU is an Ubuntu 12.04.1 server based using a standard Ubuntu=20
12.04.1 kernel, also 3.2.0-29-generic-pae.

xl info of the 4.1.2 machine:

host                   : xen3
release                : 3.4.0+
version                : #1 SMP Mon Jun 4 12:41:14 BST 2012
machine                : x86_64
nr_cpus                : 4
nr_nodes               : 1
cores_per_socket       : 4
threads_per_core       : 1
cpu_mhz                : 2300
hw_caps                :=20
178bf3ff:efd3fbff:00000000:00001310:00802001:00000000:000007ff:00000000
virt_caps              : hvm
total_memory           : 8159
free_memory            : 3866
free_cpus              : 0
xen_major              : 4
xen_minor              : 1
xen_extra              : .2
xen_caps               : xen-3.0-x86_64 xen-3.0-x86_32p hvm-3.0-x86_32=20
hvm-3.0-x86_32p hvm-3.0-x86_64
xen_scheduler          : credit
xen_pagesize           : 4096
platform_params        : virt_start=3D0xffff800000000000
xen_changeset          : unavailable
xen_commandline        : loglvl=3Dall guesloglvl=3Dall
cc_compiler            : gcc version 4.4.5 20110214 (Red Hat 4.4.5-6) (GCC)
cc_compile_by          : root
cc_compile_domain      : (none)
cc_compile_date        : Sun Jan 22 01:18:42 GMT 2012
xend_config_format     : 4


xl info of the 4.1.3 machine:

host                   : xen5
release                : 3.2.0-29-generic-pae
version                : #46-Ubuntu SMP Fri Jul 27 17:25:43 UTC 2012
machine                : i686
nr_cpus                : 2
nr_nodes               : 1
cores_per_socket       : 2
threads_per_core       : 1
cpu_mhz                : 1995
hw_caps                :=20
bfe9fbff:00100000:00000000:00000940:0000c1a9:00000000:00000000:00000000
virt_caps              :
total_memory           : 3062
free_memory            : 173
free_cpus              : 0
xen_major              : 4
xen_minor              : 1
xen_extra              : .3
xen_caps               : xen-3.0-x86_32p
xen_scheduler          : credit
xen_pagesize           : 4096
platform_params        : virt_start=3D0xf5800000
xen_changeset          : unavailable
xen_commandline        : placeholder
cc_compiler            : gcc version 4.6.3 (Ubuntu/Linaro 4.6.3-1ubuntu5)
cc_compile_by          : root
cc_compile_domain      : local
cc_compile_date        : Thu Sep  6 01:53:48 BST 2012
xend_config_format     : 4

DomU config file:

cat ubuntu-calendar
name      =3D "ubuntu-calendar"
memory    =3D 1024
disk      =3D ['phy:/dev/xen5/ubuntu-calendar,xvda,w']
vif =3D [ 'mac=3D00:16:31:50:01:03' ]
bootloader=3D"/usr/bin/pygrub"
vfb =3D [ "type=3Dvnc,vncunused=3D1,vnclisten=3D0.0.0.0" ]
vcpus     =3D 2
on_reboot =3D 'restart'
on_crash  =3D 'restart'

DomU's grub.lst....

menuentry 'Ubuntu, with Linux 3.2.0-29-generic' --class ubuntu --class=20
gnu-linux
  --class gnu --class os {
         recordfail
         insmod ext2
         set root=3D'(hd0,1)'
         search --no-floppy --fs-uuid --set=3Droot=20
70149f72-3c4f-4608-bebd-06825b91
ce29
         linux   /boot/vmlinuz-3.2.0-29-generic-pae=20
root=3DUUID=3D70149f72-3c4f-4608-
bebd-06825b91ce29 ro   quiet splash set default=3D"0"
set timeout=3D5
menuentry 'Ubuntu GNU/Linux, with Xen 4.1-amd64 and Linux=20
3.2.0-23-generic' --class ubuntu --class gnu-linux --class gnu --class=20
os --class xen {
     insmod part_msdos
     insmod ext2
     set root=3D'(hd0,msdos1)'
     search --no-floppy --fs-uuid --set=3Droot=20
1b478986-8c02-4a79-ad61-cf8f418e35ad
     echo    'Loading Xen 4.1-amd64 ...'
     multiboot    /xen.gz placeholder
     echo    'Loading Linux 3.2.0-29-generic-pae ...'
     module    /vmlinuz-3.2.0-29-generic-pae placeholder=20
root=3D/dev/mapper/xen5-root ro
     echo    'Loading initial ramdisk ...'
     module    /initrd.img-3.2.0-29-generic-pae
}
xen-fbfront.video=3D16,1024,768 $vt_handoff
         initrd  /boot/initrd.img-3.2.0-29-generic-pae


Dom0's grub.lst (4.1.3)...

set default=3D"0"
set timeout=3D5
menuentry 'Ubuntu GNU/Linux, with Xen 4.1-amd64 and Linux=20
3.2.0-23-generic' --class ubuntu --class gnu-linux --class gnu --class=20
os --class xen {
     insmod part_msdos
     insmod ext2
     set root=3D'(hd0,msdos1)'
     search --no-floppy --fs-uuid --set=3Droot=20
1b478986-8c02-4a79-ad61-cf8f418e35ad
     echo    'Loading Xen 4.1-amd64 ...'
     multiboot    /xen.gz placeholder
     echo    'Loading Linux 3.2.0-29-generic-pae ...'
     module    /vmlinuz-3.2.0-29-generic-pae placeholder=20
root=3D/dev/mapper/xen5-root ro
     echo    'Loading initial ramdisk ...'
     module    /initrd.img-3.2.0-29-generic-pae
}









_______________________________________________
Xen-users mailing list
Xen-users@lists.xen.org
http://lists.xen.org/xen-users
--=-shbzO0Wi0DlnQ9xe0gCH-- --=-W4QsZT7UiRWsGlRPgsBP Content-Type: application/pgp-signature; name="signature.asc" Content-Description: This is a digitally signed message part Content-Transfer-Encoding: 7bit -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.11 (GNU/Linux) iQEcBAABAgAGBQJQT03oAAoJEHzu36SveClljEoIAIR6nMFNSmDJoBlVTdsB49PD 2qwGlBNp04RFaAxkLIedfaL0pXmAYR4yPGuiZvN0hnAL1PrR+4462cBAe+bHBPwB oXwOJ/BjDar2i3bOxikND77EK6yob0Gld5SWfgKX/K5S/Trp4viHNnUI9GVNV+aJ Z3yH4pbBwANe85Wkauzdo1DbHIBdOhbxX8Enj4um1H5QvNrkGchMZZkl4oGDv+Kc KFV9jUTj5X5GzpEMzD7HyS7pENoLbrQsesLBvsHYM7qdrBYbOOczGg2QH7sU6yp/ NY6zUMOZM/IFVI6dqaMHgtkpfUkXWNygkTwVj7RYjOjCTLr6CYNu7IkTmd7zayo= =b9bW -----END PGP SIGNATURE----- --=-W4QsZT7UiRWsGlRPgsBP-- --===============3466945957166837128== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users --===============3466945957166837128==-- From xen-users-bounces@lists.xen.org Tue Sep 11 22:47:44 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Tue, 11 Sep 2012 22:47:44 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TBZDk-0005e5-Kd; Tue, 11 Sep 2012 22:46:16 +0000 Received: from mail27.messagelabs.com ([193.109.254.147]) by lists.xen.org with smtp (Exim 4.72) (envelope-from ) id 1TBZDi-0005dx-A3 for xen-users@lists.xen.org; Tue, 11 Sep 2012 22:46:14 +0000 X-Env-Sender: maik.brauer@mbs-systems.net X-Msg-Ref: server-11.tower-27.messagelabs.com!1347403567!3682351!1 X-Originating-IP: [188.40.240.248] X-SpamReason: No, hits=0.0 required=7.0 tests= X-StarScan-Received: X-StarScan-Version: 6.6.1.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 13125 invoked from network); 11 Sep 2012 22:46:07 -0000 Received: from mx1.mbs-systems.net (HELO mx1.mbs-systems.net) (188.40.240.248) by server-11.tower-27.messagelabs.com with SMTP; 11 Sep 2012 22:46:07 -0000 Received: from localhost (localhost [127.0.0.1]) by mx1.mbs-systems.net (Postfix) with ESMTP id 90A535C30B; Wed, 12 Sep 2012 00:47:08 +0200 (CEST) Received: from mx1.mbs-systems.net ([127.0.0.1]) by localhost (mta.mbs-systems.net [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id fBjkVQanvM5v; Wed, 12 Sep 2012 00:47:07 +0200 (CEST) Received: from maiks-macbookpro.fritz.box (dslb-092-072-023-197.pools.arcor-ip.net [92.72.23.197]) by mx1.mbs-systems.net (Postfix) with ESMTPSA id 736E85C281; Wed, 12 Sep 2012 00:47:07 +0200 (CEST) Mime-Version: 1.0 (Apple Message framework v1278) From: Maik Brauer In-Reply-To: <1347289853.5305.105.camel@zakaz.uk.xensource.com> Date: Wed, 12 Sep 2012 00:46:04 +0200 Message-Id: <4BCC413D-1697-4681-AF28-118D1623AF1C@mbs-systems.net> References: <9F8FD2B0-450A-4A6E-A929-BA240ED1D997@mbs-systems.net> <1346746297.32462.37.camel@zakaz.uk.xensource.com> <1347266386.5305.17.camel@zakaz.uk.xensource.com> <4957C391-6070-47C1-A2AC-991ED1C1766A@mbs-systems.net> <1347289853.5305.105.camel@zakaz.uk.xensource.com> To: Ian Campbell X-Mailer: Apple Mail (2.1278) Cc: "xen-users@lists.xen.org" Subject: Re: [Xen-users] Dom0 crashed when rebooting whilst DomU are running X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org On Sep 10, 2012, at 5:10 PM, Ian Campbell wrote: > On Mon, 2012-09-10 at 16:00 +0100, Maik Brauer wrote: >> On Sep 10, 2012, at 10:39 AM, Ian Campbell wrote: >> >>> On Sat, 2012-09-08 at 15:50 +0100, Maik Brauer wrote: >>>> On Sep 4, 2012, at 10:11 AM, Ian Campbell wrote: >>>> >>>>> Could you not top post please, it makes it rather hard to follow the >>>>> flow of the conversation. >>>>> On Mon, 2012-09-03 at 18:10 +0100, Casey DeLorme wrote: >>>>>> As stated, you can alias shutdown to do exactly what you need, it can >>>>>> be as simple as a series of hard-coded operations to a complex custom >>>>>> shell script that parses your domains and closes each with feedback. >>>>> >>>>> Xen ships the "xendomains" initscript which can halt guest on shutdown >>>>> as well as automatically start specific guests on boot. It can also be >>>>> configured to suspend/resume them or (I think) migrate them away. >>>>> >>>>> For diagnosing the crash itself more details will be required than were >>>>> provided in the original post. Please see >>>>> http://wiki.xen.org/wiki/Reporting_Bugs_against_Xen for some guidance. >>>>> At a minimum we would need a capture (serial console or photo) of the >>>>> crash backtrace. >>>>> >>>>> Ian. >>>>> >>>>> >>>> I found out that it hangs during re-boot of dom0 when having more >>>> Network interfaces involved, like: >>>> vif = [ 'mac=06:46:AB:CC:11:01, ip=', '', '', >>>> 'mac=06:04:AB:BB:11:03, bridge=VLAN20, script=vif-bridge', '', >>>> 'mac=06:04:AB:BB:11:05, bridge=VLAN40, script=vif-bridge' ] >>> >>> 6 interfaces total, 3 of which have a random mac on each reboot and all >>> get put on the default bridge? >> >> No, not really. The bridge is different for each interface. > > You have three lots of '' which will all go onto the same bridge AFAICT > (whichever one is determined to be the default) That is right. As long as I put nothing inside that it should be a different script to execute, it will use default for '' > >>> If it is a hang then you might have some luck using hte magic sysrq keys >>> to print lists of blocked tasks. I'm not sure in Squeeze but you might >>> need to enable this as described in Documentation/sysrq.txt in the Linux >>> source. >>> >>> Blocked tasks are listed with SysRQ-'w'. If you have serial console then >>> 't' will list all task, but that list can be quite long so it is useless >>> without a serial console. >> >> List is empty. SysRQ -w and SysRQ-t shows nothing at all. > > You might need to increase the log verbosity with SysRQ-9 first? I did and now I got more Information. But due to the amount of data which slips over the console screen I am not able to record properly. Can you advice what to do here? > >> There is nothing running anymore. >> It shows periodically: INFO: task xenwatch:12 blocked for more than 120 seconds > > What is the very last thing printed before this? There is nothing before. Just that message pops up periodically. > >> Seems that the xenwatch is blocking the reboot here, is that assumption correct? But strange enough that I can't >> see any process anymore with the SysRQ -t or SysRQ -w > > The xenwatch thread ought to count as a process for at least the > purposes of SysRQ-t if not -w. Could be, but due to the amount it slips over the screen, that I am not able to read it line by line. Please advice a procedure to record. > >> >>>> In the Logfile of /var/log/message you can find this as the last line: >>>> Sep 8 15:44:28 rootsrv01 shutdown[2445]: shutting down for system reboot >>>> Sep 8 15:44:31 rootsrv01 kernel: [ 73.716246] VLAN20: port 1(vif2.3) entering forwarding state >>>> Sep 8 15:44:31 rootsrv01 kernel: [ 74.500111] VLAN40: port 1(vif2.5) entering forwarding state >>>> Sep 8 15:44:34 rootsrv01 kernel: [ 77.317431] VLAN20: port 1(vif2.3) entering disabled state >>>> Sep 8 15:44:34 rootsrv01 kernel: [ 77.317490] VLAN20: port 1(vif2.3) entering disabled state >>>> Sep 8 15:44:36 rootsrv01 kernel: [ 79.368685] VLAN40: port 1(vif2.5) entering disabled state >>>> Sep 8 15:44:36 rootsrv01 kernel: [ 79.369156] VLAN40: port 1(vif2.5) entering disabled state >>>> Sep 8 15:44:37 rootsrv01 kernel: Kernel logging (proc) stopped. >>>> Sep 8 15:44:37 rootsrv01 rsyslogd: [origin software="rsyslogd" swVersion="4.6.4" x-pid="890" x-info="http://www.rsyslog.com"] exiting on signal 15. >>>> >>>> In the /var/log/daemong.log you can find this message: >>>> Sep 8 15:44:37 rootsrv01 acpid: exiting >>>> Sep 8 15:44:37 rootsrv01 rpc.statd[750]: Caught signal 15, un-registering and exiting >>> >>> All the above (both message and daemon.log) look like normal parts of >>> shutting down to me. >>> >>>> Sep 8 15:44:37 rootsrv01 udevd-work[2276]: '/etc/xen/scripts/vif-setup offline type_if=vif' unexpected exit with status 0x000f >>> >>> This might be worth following up on. >> >> When putting a "sleep 5" in stop section of the /etc/init.d/xendomains: >> case "$1" in >> start) >> start >> rc_status >> if test -f $LOCKFILE; then rc_status -v; fi >> ;; >> >> stop) >> stop >> rc_status -v >> sleep 5 >> ;; >> >> then the system shuts down as expected and is rebooting properly. >> In the daemon.log file I couldn't find the error: Sep 8 15:44:37 rootsrv01 udevd-work[2276]: '/etc/xen/scripts/vif-setup offline type_if=vif' unexpected exit with status 0x000f >> anymore. It seems that it disappeared after putting a delay inside. Could it be a race condition here during shutdown, with the udev-daemon?? > > It could be a race with the guests actually shuting down vs the rest of > the initscripts running. > > Really the initscript ought to wait, the default at least with the > script shipped with xen is to do so, by using shutdown --wait. can you > confirm whether or not this is happening for you? At least I can see that the shutdown --wait is in the scripts. So it seems that the init script is waiting. But independent from that, something must be still in use. Which block the reboot process. > > Possibly someone is trying to talk to xenstore after xenstored has > exited -- I expect that would cause the sorts of blocked for 120 > messages you are seeing. > Could be, but we need to find out what is blocking the shutdown. I do not know what else I can do in order to measure and collect data for investigation. Let me know what else I can do? You can easiliy reproduce this issue, when using more that 3 Network devices. I installed that now on several machines at home and I have on all the same issue when using more than 2-3 network Interfaces. > > > _______________________________________________ > Xen-users mailing list > Xen-users@lists.xen.org > http://lists.xen.org/xen-users _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Tue Sep 11 22:47:44 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Tue, 11 Sep 2012 22:47:44 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TBZDk-0005e5-Kd; Tue, 11 Sep 2012 22:46:16 +0000 Received: from mail27.messagelabs.com ([193.109.254.147]) by lists.xen.org with smtp (Exim 4.72) (envelope-from ) id 1TBZDi-0005dx-A3 for xen-users@lists.xen.org; Tue, 11 Sep 2012 22:46:14 +0000 X-Env-Sender: maik.brauer@mbs-systems.net X-Msg-Ref: server-11.tower-27.messagelabs.com!1347403567!3682351!1 X-Originating-IP: [188.40.240.248] X-SpamReason: No, hits=0.0 required=7.0 tests= X-StarScan-Received: X-StarScan-Version: 6.6.1.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 13125 invoked from network); 11 Sep 2012 22:46:07 -0000 Received: from mx1.mbs-systems.net (HELO mx1.mbs-systems.net) (188.40.240.248) by server-11.tower-27.messagelabs.com with SMTP; 11 Sep 2012 22:46:07 -0000 Received: from localhost (localhost [127.0.0.1]) by mx1.mbs-systems.net (Postfix) with ESMTP id 90A535C30B; Wed, 12 Sep 2012 00:47:08 +0200 (CEST) Received: from mx1.mbs-systems.net ([127.0.0.1]) by localhost (mta.mbs-systems.net [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id fBjkVQanvM5v; Wed, 12 Sep 2012 00:47:07 +0200 (CEST) Received: from maiks-macbookpro.fritz.box (dslb-092-072-023-197.pools.arcor-ip.net [92.72.23.197]) by mx1.mbs-systems.net (Postfix) with ESMTPSA id 736E85C281; Wed, 12 Sep 2012 00:47:07 +0200 (CEST) Mime-Version: 1.0 (Apple Message framework v1278) From: Maik Brauer In-Reply-To: <1347289853.5305.105.camel@zakaz.uk.xensource.com> Date: Wed, 12 Sep 2012 00:46:04 +0200 Message-Id: <4BCC413D-1697-4681-AF28-118D1623AF1C@mbs-systems.net> References: <9F8FD2B0-450A-4A6E-A929-BA240ED1D997@mbs-systems.net> <1346746297.32462.37.camel@zakaz.uk.xensource.com> <1347266386.5305.17.camel@zakaz.uk.xensource.com> <4957C391-6070-47C1-A2AC-991ED1C1766A@mbs-systems.net> <1347289853.5305.105.camel@zakaz.uk.xensource.com> To: Ian Campbell X-Mailer: Apple Mail (2.1278) Cc: "xen-users@lists.xen.org" Subject: Re: [Xen-users] Dom0 crashed when rebooting whilst DomU are running X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org On Sep 10, 2012, at 5:10 PM, Ian Campbell wrote: > On Mon, 2012-09-10 at 16:00 +0100, Maik Brauer wrote: >> On Sep 10, 2012, at 10:39 AM, Ian Campbell wrote: >> >>> On Sat, 2012-09-08 at 15:50 +0100, Maik Brauer wrote: >>>> On Sep 4, 2012, at 10:11 AM, Ian Campbell wrote: >>>> >>>>> Could you not top post please, it makes it rather hard to follow the >>>>> flow of the conversation. >>>>> On Mon, 2012-09-03 at 18:10 +0100, Casey DeLorme wrote: >>>>>> As stated, you can alias shutdown to do exactly what you need, it can >>>>>> be as simple as a series of hard-coded operations to a complex custom >>>>>> shell script that parses your domains and closes each with feedback. >>>>> >>>>> Xen ships the "xendomains" initscript which can halt guest on shutdown >>>>> as well as automatically start specific guests on boot. It can also be >>>>> configured to suspend/resume them or (I think) migrate them away. >>>>> >>>>> For diagnosing the crash itself more details will be required than were >>>>> provided in the original post. Please see >>>>> http://wiki.xen.org/wiki/Reporting_Bugs_against_Xen for some guidance. >>>>> At a minimum we would need a capture (serial console or photo) of the >>>>> crash backtrace. >>>>> >>>>> Ian. >>>>> >>>>> >>>> I found out that it hangs during re-boot of dom0 when having more >>>> Network interfaces involved, like: >>>> vif = [ 'mac=06:46:AB:CC:11:01, ip=', '', '', >>>> 'mac=06:04:AB:BB:11:03, bridge=VLAN20, script=vif-bridge', '', >>>> 'mac=06:04:AB:BB:11:05, bridge=VLAN40, script=vif-bridge' ] >>> >>> 6 interfaces total, 3 of which have a random mac on each reboot and all >>> get put on the default bridge? >> >> No, not really. The bridge is different for each interface. > > You have three lots of '' which will all go onto the same bridge AFAICT > (whichever one is determined to be the default) That is right. As long as I put nothing inside that it should be a different script to execute, it will use default for '' > >>> If it is a hang then you might have some luck using hte magic sysrq keys >>> to print lists of blocked tasks. I'm not sure in Squeeze but you might >>> need to enable this as described in Documentation/sysrq.txt in the Linux >>> source. >>> >>> Blocked tasks are listed with SysRQ-'w'. If you have serial console then >>> 't' will list all task, but that list can be quite long so it is useless >>> without a serial console. >> >> List is empty. SysRQ -w and SysRQ-t shows nothing at all. > > You might need to increase the log verbosity with SysRQ-9 first? I did and now I got more Information. But due to the amount of data which slips over the console screen I am not able to record properly. Can you advice what to do here? > >> There is nothing running anymore. >> It shows periodically: INFO: task xenwatch:12 blocked for more than 120 seconds > > What is the very last thing printed before this? There is nothing before. Just that message pops up periodically. > >> Seems that the xenwatch is blocking the reboot here, is that assumption correct? But strange enough that I can't >> see any process anymore with the SysRQ -t or SysRQ -w > > The xenwatch thread ought to count as a process for at least the > purposes of SysRQ-t if not -w. Could be, but due to the amount it slips over the screen, that I am not able to read it line by line. Please advice a procedure to record. > >> >>>> In the Logfile of /var/log/message you can find this as the last line: >>>> Sep 8 15:44:28 rootsrv01 shutdown[2445]: shutting down for system reboot >>>> Sep 8 15:44:31 rootsrv01 kernel: [ 73.716246] VLAN20: port 1(vif2.3) entering forwarding state >>>> Sep 8 15:44:31 rootsrv01 kernel: [ 74.500111] VLAN40: port 1(vif2.5) entering forwarding state >>>> Sep 8 15:44:34 rootsrv01 kernel: [ 77.317431] VLAN20: port 1(vif2.3) entering disabled state >>>> Sep 8 15:44:34 rootsrv01 kernel: [ 77.317490] VLAN20: port 1(vif2.3) entering disabled state >>>> Sep 8 15:44:36 rootsrv01 kernel: [ 79.368685] VLAN40: port 1(vif2.5) entering disabled state >>>> Sep 8 15:44:36 rootsrv01 kernel: [ 79.369156] VLAN40: port 1(vif2.5) entering disabled state >>>> Sep 8 15:44:37 rootsrv01 kernel: Kernel logging (proc) stopped. >>>> Sep 8 15:44:37 rootsrv01 rsyslogd: [origin software="rsyslogd" swVersion="4.6.4" x-pid="890" x-info="http://www.rsyslog.com"] exiting on signal 15. >>>> >>>> In the /var/log/daemong.log you can find this message: >>>> Sep 8 15:44:37 rootsrv01 acpid: exiting >>>> Sep 8 15:44:37 rootsrv01 rpc.statd[750]: Caught signal 15, un-registering and exiting >>> >>> All the above (both message and daemon.log) look like normal parts of >>> shutting down to me. >>> >>>> Sep 8 15:44:37 rootsrv01 udevd-work[2276]: '/etc/xen/scripts/vif-setup offline type_if=vif' unexpected exit with status 0x000f >>> >>> This might be worth following up on. >> >> When putting a "sleep 5" in stop section of the /etc/init.d/xendomains: >> case "$1" in >> start) >> start >> rc_status >> if test -f $LOCKFILE; then rc_status -v; fi >> ;; >> >> stop) >> stop >> rc_status -v >> sleep 5 >> ;; >> >> then the system shuts down as expected and is rebooting properly. >> In the daemon.log file I couldn't find the error: Sep 8 15:44:37 rootsrv01 udevd-work[2276]: '/etc/xen/scripts/vif-setup offline type_if=vif' unexpected exit with status 0x000f >> anymore. It seems that it disappeared after putting a delay inside. Could it be a race condition here during shutdown, with the udev-daemon?? > > It could be a race with the guests actually shuting down vs the rest of > the initscripts running. > > Really the initscript ought to wait, the default at least with the > script shipped with xen is to do so, by using shutdown --wait. can you > confirm whether or not this is happening for you? At least I can see that the shutdown --wait is in the scripts. So it seems that the init script is waiting. But independent from that, something must be still in use. Which block the reboot process. > > Possibly someone is trying to talk to xenstore after xenstored has > exited -- I expect that would cause the sorts of blocked for 120 > messages you are seeing. > Could be, but we need to find out what is blocking the shutdown. I do not know what else I can do in order to measure and collect data for investigation. Let me know what else I can do? You can easiliy reproduce this issue, when using more that 3 Network devices. I installed that now on several machines at home and I have on all the same issue when using more than 2-3 network Interfaces. > > > _______________________________________________ > Xen-users mailing list > Xen-users@lists.xen.org > http://lists.xen.org/xen-users _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Wed Sep 12 00:26:31 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Wed, 12 Sep 2012 00:26:31 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TBalU-0006iN-GB; Wed, 12 Sep 2012 00:25:12 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TBalR-0006iF-8W for xen-users@lists.xen.org; Wed, 12 Sep 2012 00:25:10 +0000 Received: from [85.158.143.99:27816] by server-3.bemta-4.messagelabs.com id 34/F3-08232-466DF405; Wed, 12 Sep 2012 00:25:08 +0000 X-Env-Sender: mike.a.collins@ark-net.org X-Msg-Ref: server-2.tower-216.messagelabs.com!1347409503!24508608!1 X-Originating-IP: [216.33.127.80] X-SpamReason: No, hits=0.5 required=7.0 tests=BODY_RANDOM_LONG X-StarScan-Received: X-StarScan-Version: 6.6.1.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 14383 invoked from network); 12 Sep 2012 00:25:03 -0000 Received: from mta11.charter.net (HELO mta11.charter.net) (216.33.127.80) by server-2.tower-216.messagelabs.com with SMTP; 12 Sep 2012 00:25:03 -0000 Received: from imp11 ([10.20.200.11]) by mta11.charter.net (InterMail vM.8.01.05.02 201-2260-151-103-20110920) with ESMTP id <20120912002502.YBYZ10966.mta11.charter.net@imp11> for ; Tue, 11 Sep 2012 20:25:02 -0400 Received: from mail.ark-net.org ([75.138.215.251]) by imp11 with smtp.charter.net id y0R21j00U5S18aK050R2LH; Tue, 11 Sep 2012 20:25:02 -0400 X-Authority-Analysis: v=1.1 cv=Mv9Cy8NsQItTEAHnXr6fCNbI23lcrkmyMeqLv9HU3yU= c=1 sm=1 a=0bCt-fb661UA:10 a=Q-lh5XB8xgUA:10 a=VCxxn1A5iYMA:10 a=NqYyV4q_xg0A:10 a=wPDyFdB5xvgA:10 a=IkcTkHD0fZMA:10 a=4A50YBgeEUJTzIKlCdeDOQ==:17 a=-g-7CrJqAAAA:8 a=pSDxxfrZAAAA:8 a=20KFwNOVAAAA:8 a=tJxwftSMFhSheoO_9GgA:9 a=QEXdDO2ut3YA:10 a=Elr449XH5AsA:10 a=jEp0ucaQiEUA:10 a=-nm3JPuCHhnj7VM3:21 a=8isSTCofgk37nZwm:21 a=4A50YBgeEUJTzIKlCdeDOQ==:117 Received: from localhost (unknown [127.0.0.1]) by mail.ark-net.org (Postfix) with ESMTP id 974A0203DF for ; Wed, 12 Sep 2012 00:25:19 +0000 (UTC) X-Virus-Scanned: amavisd-new at ark-net.org Received: from mail.ark-net.org ([127.0.0.1]) by localhost (mail.ark-net.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id zlYHncT+ZNMW for ; Tue, 11 Sep 2012 20:24:37 -0400 (EDT) Received: from 192.168.1.12 (unknown [192.168.1.12]) by mail.ark-net.org (Postfix) with ESMTP id C168E203D1 for ; Tue, 11 Sep 2012 20:24:37 -0400 (EDT) MIME-Version: 1.0 Date: Tue, 11 Sep 2012 20:40:34 -0400 From: "Michael A. Collins" To: Mail-Reply-To: In-Reply-To: <1347374568.7226.12.camel@wotan2> References: <504D17ED.9030105@yahoo.co.uk> <1347374568.7226.12.camel@wotan2> Message-ID: <6c6a19bf07700c9915c0c0facef6df21@192.168.1.11> X-Sender: mike.a.collins@ark-net.org User-Agent: Roundcube Webmail/0.6-beta Subject: Re: [Xen-users] Stall on CPU X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list Reply-To: mike.a.collins@ark-net.org List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset="us-ascii"; Format="flowed" Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org On 11.09.2012 10:42, Stephan Seitz wrote: > Hi, > > I've also seen that "rcu sched detected stalls on CPU x", but on > dom0, not domU. > The dom0 which had this error (leading to a complete system stop) is > running xen 4.1.3 > and vanilla 3.5.2 as dom0 kernel. > I know, I should go with the xenified kernels, but I'm currently > evaluating tmem features on recent > kernels. > > Another machine which hit that "rcu sched" was a baremetal 3.1.1 > acting as scst target. > > I've got the feeling the error can be triggered by heavy I/O, but to > be honest, I don't have > any glue what to do against it. > > Cheers, > > - Stephan > I am having the same issue on a newly updated dom0. I have stack traces below, but it seems to be only when I reboot or shutdown the dom0. It stalls for 15 mins or so and then finally gives up and finishes. The stack trace looks like it has something to do with a timer issue and I saw some posts awhile ago about setting the timesource=jiffies on the command-line, but I have not tried it. Here's the stack trace: Sep 11 19:37:28 xen-server01 kernel: [76610.242073] INFO: rcu_sched self-detected stall on CPU { 0} (t=299981 jiffies) Sep 11 19:37:28 xen-server01 kernel: [76610.242281] Pid: 0, comm: swapper/0 Tainted: G O 3.6.0-rc4+ #2 Sep 11 19:37:28 xen-server01 kernel: [76610.242385] Call Trace: Sep 11 19:37:28 xen-server01 kernel: [76610.242474] [] rcu_check_callbacks+0x4d2/0x640 Sep 11 19:37:28 xen-server01 kernel: [76610.242594] [] ? tick_nohz_handler+0xf0/0xf0 Sep 11 19:37:28 xen-server01 kernel: [76610.242698] [] update_process_times+0x43/0x80 Sep 11 19:37:28 xen-server01 kernel: [76610.242799] [] tick_sched_timer+0x67/0xd0 Sep 11 19:37:28 xen-server01 kernel: [76610.242900] [] __run_hrtimer+0x7f/0x1d0 Sep 11 19:37:28 xen-server01 kernel: [76610.243008] [] ? xen_clocksource_get_cycles+0x9/0x10 Sep 11 19:37:28 xen-server01 kernel: [76610.243111] [] ? ktime_get_update_offsets+0x47/0xd0 Sep 11 19:37:28 xen-server01 kernel: [76610.243214] [] hrtimer_interrupt+0xfe/0x250 Sep 11 19:37:28 xen-server01 kernel: [76610.243315] [] xen_timer_interrupt+0x2d/0x1b0 Sep 11 19:37:28 xen-server01 kernel: [76610.243417] [] ? xen_hypercall_sched_op+0xa/0x20 Sep 11 19:37:28 xen-server01 kernel: [76610.243520] [] ? radix_tree_lookup+0xb/0x10 Sep 11 19:37:28 xen-server01 kernel: [76610.243621] [] ? irq_to_desc+0x12/0x20 Sep 11 19:37:28 xen-server01 kernel: [76610.243720] [] ? irq_get_irq_data+0x9/0x10 Sep 11 19:37:28 xen-server01 kernel: [76610.243821] [] handle_irq_event_percpu+0x5d/0x200 Sep 11 19:37:28 xen-server01 kernel: [76610.243924] [] handle_percpu_irq+0x43/0x60 Sep 11 19:37:28 xen-server01 kernel: [76610.244026] [] __xen_evtchn_do_upcall+0x1a6/0x260 Sep 11 19:37:28 xen-server01 kernel: [76610.244129] [] xen_evtchn_do_upcall+0x2a/0x40 Sep 11 19:37:28 xen-server01 kernel: [76610.244231] [] xen_do_hypervisor_callback+0x1e/0x30 Sep 11 19:37:28 xen-server01 kernel: [76610.244334] [] ? xen_hypercall_sched_op+0xa/0x20 Sep 11 19:37:28 xen-server01 kernel: [76610.244448] [] ? xen_hypercall_sched_op+0xa/0x20 Sep 11 19:37:28 xen-server01 kernel: [76610.244551] [] ? xen_safe_halt+0x10/0x20 Sep 11 19:37:28 xen-server01 kernel: [76610.244651] [] ? default_idle+0x58/0x1b0 Sep 11 19:37:28 xen-server01 kernel: [76610.244751] [] ? cpu_idle+0x8f/0xc0 Sep 11 19:37:28 xen-server01 kernel: [76610.244851] [] ? rest_init+0x6d/0x80 Sep 11 19:37:28 xen-server01 kernel: [76610.244951] [] ? start_kernel+0x341/0x34e Sep 11 19:37:28 xen-server01 kernel: [76610.245051] [] ? repair_env_string+0x59/0x59 Sep 11 19:37:28 xen-server01 kernel: [76610.245154] [] ? x86_64_start_reservations+0x132/0x137 Sep 11 19:37:28 xen-server01 kernel: [76610.245260] [] ? xen_start_kernel+0x626/0x62d Here's some more info: (XEN) ACPI: INT_SRC_OVR (bus 0 bus_irq 0 global_irq 2 dfl dfl) (XEN) ACPI: INT_SRC_OVR (bus 0 bus_irq 9 global_irq 9 high level) (XEN) Enabling APIC mode: Flat. Using 1 I/O APICs (XEN) ACPI: HPET id: 0x8086a801 base: 0xfed00000 (XEN) Xen ERST support is initialized. (XEN) Using ACPI (MADT) for SMP configuration information (XEN) SMP: Allowing 8 CPUs (0 hotplug CPUs) (XEN) IRQ limits: 24 GSI, 1528 MSI/MSI-X (XEN) Using scheduler: SMP Credit Scheduler (credit) (XEN) Detected 2533.348 MHz processor. (XEN) Initing memory sharing. (XEN) mce_intel.c:1239: MCA Capability: BCAST 1 SER 0 CMCI 1 firstbank 0 extended MCE MSR 0 (XEN) Intel machine check reporting enabled (XEN) PCI: MCFG configuration 0: base a0000000 segment 0000 buses 00 - ff (XEN) PCI: MCFG area at a0000000 reserved in E820 (XEN) PCI: Using MCFG for segment 0000 bus 00-ff (XEN) Intel VT-d supported page sizes: 4kB. (XEN) Intel VT-d Snoop Control enabled. (XEN) Intel VT-d Dom0 DMA Passthrough not enabled. (XEN) Intel VT-d Queued Invalidation enabled. (XEN) Intel VT-d Interrupt Remapping not enabled. (XEN) Intel VT-d Shared EPT tables not enabled. (XEN) I/O virtualisation enabled (XEN) - Dom0 mode: Relaxed (XEN) ENABLING IO-APIC IRQs (XEN) -> Using new ACK method (XEN) ..TIMER: vector=0xF0 apic1=0 pin1=2 apic2=-1 pin2=-1 (XEN) Platform timer is 14.318MHz HPET (XEN) Allocated console ring of 32 KiB. (XEN) VMX: Supported advanced features: (XEN) - APIC MMIO access virtualisation (XEN) - APIC TPR shadow (XEN) - Extended Page Tables (EPT) (XEN) - Virtual-Processor Identifiers (VPID) (XEN) - Virtual NMI (XEN) - MSR direct-access bitmap (XEN) HVM: ASIDs enabled. (XEN) HVM: VMX enabled (XEN) HVM: Hardware Assisted Paging (HAP) detected (XEN) HVM: HAP page sizes: 4kB, 2MB (XEN) Brought up 8 CPUs (XEN) tmem: initialized comp=0 dedup=0 tze=0 global-lock=0 (XEN) HPET: 8 timers (8 will be used for broadcast) (XEN) ACPI sleep modes: S3 (XEN) mcheck_poll: Machine check polling timer started. (XEN) *** LOADING DOMAIN 0 *** (XEN) elf_parse_binary: phdr: paddr=0x1000000 memsz=0xa69000 (XEN) elf_parse_binary: phdr: paddr=0x1c00000 memsz=0xc30e8 (XEN) elf_parse_binary: phdr: paddr=0x1cc4000 memsz=0x144c0 (XEN) elf_parse_binary: phdr: paddr=0x1cd9000 memsz=0x5c2000 (XEN) elf_parse_binary: memory: 0x1000000 -> 0x229b000 (XEN) elf_xen_parse_note: GUEST_OS = "linux" (XEN) elf_xen_parse_note: GUEST_VERSION = "2.6" (XEN) elf_xen_parse_note: XEN_VERSION = "xen-3.0" (XEN) elf_xen_parse_note: VIRT_BASE = 0xffffffff80000000 (XEN) elf_xen_parse_note: ENTRY = 0xffffffff81cd9210 (XEN) elf_xen_parse_note: HYPERCALL_PAGE = 0xffffffff81001000 (XEN) elf_xen_parse_note: FEATURES = "!writable_page_tables|pae_pgdir_above_4gb" (XEN) elf_xen_parse_note: PAE_MODE = "yes" (XEN) elf_xen_parse_note: LOADER = "generic" (XEN) elf_xen_parse_note: unknown xen elf note (0xd) (XEN) elf_xen_parse_note: SUSPEND_CANCEL = 0x1 (XEN) elf_xen_parse_note: HV_START_LOW = 0xffff800000000000 (XEN) elf_xen_parse_note: PADDR_OFFSET = 0x0 (XEN) elf_xen_addr_calc_check: addresses: (XEN) virt_base = 0xffffffff80000000 (XEN) elf_paddr_offset = 0x0 (XEN) virt_offset = 0xffffffff80000000 (XEN) virt_kstart = 0xffffffff81000000 (XEN) virt_kend = 0xffffffff8229b000 (XEN) virt_entry = 0xffffffff81cd9210 (XEN) p2m_base = 0xffffffffffffffff (XEN) Xen kernel: 64-bit, lsb, compat32 (XEN) Dom0 kernel: 64-bit, PAE, lsb, paddr 0x1000000 -> 0x229b000 (XEN) PHYSICAL MEMORY ARRANGEMENT: (XEN) Dom0 alloc.: 0000000840000000->0000000844000000 (505427 pages to be allocated) (XEN) Init. ramdisk: 000000085f653000->000000085ffffa00 (XEN) VIRTUAL MEMORY ARRANGEMENT: (XEN) Loaded kernel: ffffffff81000000->ffffffff8229b000 (XEN) Init. ramdisk: ffffffff8229b000->ffffffff82c47a00 (XEN) Phys-Mach map: ffffffff82c48000->ffffffff83048000 (XEN) Start info: ffffffff83048000->ffffffff830484b4 (XEN) Page tables: ffffffff83049000->ffffffff83066000 (XEN) Boot stack: ffffffff83066000->ffffffff83067000 (XEN) TOTAL: ffffffff80000000->ffffffff83400000 (XEN) ENTRY ADDRESS: ffffffff81cd9210 (XEN) Dom0 has maximum 2 VCPUs (XEN) elf_load_binary: phdr 0 at 0xffffffff81000000 -> 0xffffffff81a69000 (XEN) elf_load_binary: phdr 1 at 0xffffffff81c00000 -> 0xffffffff81cc30e8 (XEN) elf_load_binary: phdr 2 at 0xffffffff81cc4000 -> 0xffffffff81cd84c0 (XEN) elf_load_binary: phdr 3 at 0xffffffff81cd9000 -> 0xffffffff81d82000 (XEN) Scrubbing Free RAM: ..............................................................................................................................................................................................................................................................................................................done. (XEN) Initial low memory virq threshold set at 0x4000 pages. (XEN) Std. Loglevel: Errors, warnings and info (XEN) Guest Loglevel: All (XEN) Xen is relinquishing VGA console. (XEN) *** Serial input -> DOM0 (type 'CTRL-a' three times to switch input to Xen) (XEN) Freed 240kB init memory. mapping kernel into physical memory about to get started... [ 0.000000] Initializing cgroup subsys cpuset [ 0.000000] Initializing cgroup subsys cpu [ 0.000000] Linux version 3.6.0-rc4+ (root@xen-server01.ark-net.org) (gcc version 4.5.1 20100924 (Red Hat 4.5.1-4) (GCC) ) #2 SMP Mon Sep 10 14:42:44 EDT 2012 [ 0.000000] Command line: ro root=/dev/mapper/vg_xenserver01-LV_ROOT rd_LVM_LV=vg_xenserver01/LV_ROOT rd_LVM_LV=vg_xenserver01/LV_SWAP rd_NO_LUKS rd_NO_MD rd_NO_DM LANG=en_US.UTF-8 SYSFONT=latarcyrheb-sun16 KEYTABLE=us nomodeset ixen-pciback.passthrough=1 xen-pciback.hide=(0d:08.0)(0d:09.0)(0a:00.0) earlyprintk=xen [ 0.000000] Freeing 99-100 pfn range: 103 pages freed [ 0.000000] Released 103 pages of unused memory [ 0.000000] Set 402563 page(s) to 1-1 mapping [ 0.000000] Populating 80000-80067 pfn range: 103 pages added [ 0.000000] e820: BIOS-provided physical RAM map: [ 0.000000] Xen: [mem 0x0000000000000000-0x0000000000098fff] usable [ 0.000000] Xen: [mem 0x0000000000099400-0x00000000000fffff] reserved [ 0.000000] Xen: [mem 0x0000000000100000-0x000000009dbe3fff] usable [ 0.000000] Xen: [mem 0x000000009dbe4000-0x000000009dcb5fff] ACPI NVS [ 0.000000] Xen: [mem 0x000000009dcb6000-0x000000009f6a3fff] ACPI data [ 0.000000] Xen: [mem 0x000000009f6a4000-0x000000009f6defff] reserved [ 0.000000] Xen: [mem 0x000000009f6df000-0x000000009f789fff] ACPI data [ 0.000000] Xen: [mem 0x000000009f78a000-0x000000009f7defff] ACPI NVS [ 0.000000] Xen: [mem 0x000000009f7df000-0x000000009f7fffff] ACPI data [ 0.000000] Xen: [mem 0x000000009f800000-0x00000000afffffff] reserved [ 0.000000] Xen: [mem 0x00000000fec00000-0x00000000fec00fff] reserved [ 0.000000] Xen: [mem 0x00000000fed1c000-0x00000000fed1ffff] reserved [ 0.000000] Xen: [mem 0x00000000fee00000-0x00000000fee00fff] reserved [ 0.000000] Xen: [mem 0x00000000ff800000-0x00000000ffffffff] reserved [ 0.000000] Xen: [mem 0x0000000100000000-0x00000005e2888fff] usable [ 0.000000] Xen: [mem 0x00000005e2889000-0x000000085fffffff] unusable [ 0.000000] bootconsole [xenboot0] enabled [ 0.000000] NX (Execute Disable) protection: active [ 0.000000] DMI 2.5 present. [ 0.000000] No AGP bridge found [ 0.000000] e820: last_pfn = 0x5e2889 max_arch_pfn = 0x400000000 [ 0.000000] e820: last_pfn = 0x9dbe4 max_arch_pfn = 0x400000000 [ 0.000000] found SMP MP-table at [mem 0x000fda10-0x000fda1f] mapped at [ffff8800000fda10] [ 0.000000] init_memory_mapping: [mem 0x00000000-0x9dbe3fff] [ 0.000000] init_memory_mapping: [mem 0x100000000-0x5e2888fff] [ 0.000000] RAMDISK: [mem 0x0229b000-0x02c47fff] [ 0.000000] ACPI: RSDP 00000000000f0410 00024 (v02 INTEL ) [ 0.000000] ACPI: XSDT 000000009f7fd120 00094 (v01 INTEL S3420GPX 00000000 01000013) [ 0.000000] ACPI: FACP 000000009f7fb000 000F4 (v04 INTEL S3420GPX 00000000 MSFT 0100000D) [ 0.000000] ACPI: DSDT 000000009f7f5000 055D6 (v02 INTEL S3420GPX 00000003 MSFT 0100000D) [ 0.000000] ACPI: FACS 000000009f78a000 00040 [ 0.000000] ACPI: APIC 000000009f7f4000 000BC (v02 INTEL S3420GPX 00000000 MSFT 0100000D) [ 0.000000] ACPI: MCFG 000000009f7f3000 0003C (v01 INTEL S3420GPX 00000001 MSFT 0100000D) [ 0.000000] ACPI: HPET 000000009f7f2000 00038 (v01 INTEL S3420GPX 00000001 MSFT 0100000D) [ 0.000000] ACPI: SLIT 000000009f7f1000 00030 (v01 INTEL S3420GPX 00000001 MSFT 0100000D) [ 0.000000] ACPI: SPCR 000000009f7f0000 00050 (v01 INTEL S3420GPX 00000000 MSFT 0100000D) [ 0.000000] ACPI: WDDT 000000009f7ef000 00040 (v01 INTEL S3420GPX 00000000 MSFT 0100000D) [ 0.000000] ACPI: SSDT 000000009f7e4000 0AEF4 (v02 INTEL SSDT PM 00004000 INTL 20061109) [ 0.000000] ACPI: SSDT 000000009f7e3000 001D8 (v02 INTEL IPMI 00004000 INTL 20061109) [ 0.000000] ACPI: XMAR 000000009f7e2000 000A8 (v01 INTEL S3420GPX 00000001 MSFT 0100000D) [ 0.000000] ACPI: HEST 000000009f7e1000 000A8 (v01 INTEL S3420GPX 00000001 INTL 00000001) [ 0.000000] ACPI: BERT 000000009f7e0000 00030 (v01 INTEL S3420GPX 00000001 INTL 00000001) [ 0.000000] ACPI: ERST 000000009f7df000 00230 (v01 INTEL S3420GPX 00000001 INTL 00000001) [ 0.000000] ACPI: EINJ 000000009f789000 00130 (v01 INTEL S3420GPX 00000001 INTL 00000001) [ 0.000000] NUMA: Warning: node ids are out of bound, from=-1 to=-1 distance=10 [ 0.000000] No NUMA configuration found [ 0.000000] Faking a node at [mem 0x0000000000000000-0x00000005e2888fff] [ 0.000000] Initmem setup node 0 [mem 0x00000000-0x5e2888fff] [ 0.000000] NODE_DATA [mem 0x80063000-0x80066fff] [ 0.000000] Zone ranges: [ 0.000000] DMA [mem 0x00010000-0x00ffffff] [ 0.000000] DMA32 [mem 0x01000000-0xffffffff] [ 0.000000] Normal [mem 0x100000000-0x5e2888fff] [ 0.000000] Movable zone start for each node [ 0.000000] Early memory node ranges [ 0.000000] node 0: [mem 0x00010000-0x00098fff] [ 0.000000] node 0: [mem 0x00100000-0x9dbe3fff] [ 0.000000] node 0: [mem 0x100000000-0x5e2888fff] [ 0.000000] ACPI: PM-Timer IO Port: 0x408 [ 0.000000] ACPI: LAPIC (acpi_id[0x00] lapic_id[0x00] enabled) [ 0.000000] ACPI: LAPIC (acpi_id[0x01] lapic_id[0x02] enabled) [ 0.000000] ACPI: LAPIC (acpi_id[0x02] lapic_id[0x04] enabled) [ 0.000000] ACPI: LAPIC (acpi_id[0x03] lapic_id[0x06] enabled) [ 0.000000] ACPI: LAPIC (acpi_id[0x04] lapic_id[0x01] enabled) [ 0.000000] ACPI: LAPIC (acpi_id[0x05] lapic_id[0x03] enabled) [ 0.000000] ACPI: LAPIC (acpi_id[0x06] lapic_id[0x05] enabled) [ 0.000000] ACPI: LAPIC (acpi_id[0x07] lapic_id[0x07] enabled) [ 0.000000] ACPI: LAPIC_NMI (acpi_id[0x00] high level lint[0x1]) [ 0.000000] ACPI: LAPIC_NMI (acpi_id[0x01] high level lint[0x1]) [ 0.000000] ACPI: LAPIC_NMI (acpi_id[0x02] high level lint[0x1]) [ 0.000000] ACPI: LAPIC_NMI (acpi_id[0x03] high level lint[0x1]) [ 0.000000] ACPI: LAPIC_NMI (acpi_id[0x04] high level lint[0x1]) [ 0.000000] ACPI: LAPIC_NMI (acpi_id[0x05] high level lint[0x1]) [ 0.000000] ACPI: LAPIC_NMI (acpi_id[0x06] high level lint[0x1]) [ 0.000000] ACPI: LAPIC_NMI (acpi_id[0x07] high level lint[0x1]) [ 0.000000] ACPI: IOAPIC (id[0x08] address[0xfec00000] gsi_base[0]) [ 0.000000] IOAPIC[0]: apic_id 8, version 32, address 0xfec00000, GSI 0-23 [ 0.000000] ACPI: INT_SRC_OVR (bus 0 bus_irq 0 global_irq 2 dfl dfl) [ 0.000000] ACPI: INT_SRC_OVR (bus 0 bus_irq 9 global_irq 9 high level) [ 0.000000] Using ACPI (MADT) for SMP configuration information [ 0.000000] ACPI: HPET id: 0x8086a801 base: 0xfed00000 [ 0.000000] smpboot: Allowing 8 CPUs, 0 hotplug CPUs [ 0.000000] PM: Registered nosave memory: 0000000000099000 - 000000000009a000 [ 0.000000] PM: Registered nosave memory: 000000000009a000 - 0000000000100000 [ 0.000000] PM: Registered nosave memory: 000000009dbe4000 - 000000009dcb6000 [ 0.000000] PM: Registered nosave memory: 000000009dcb6000 - 000000009f6a4000 [ 0.000000] PM: Registered nosave memory: 000000009f6a4000 - 000000009f6df000 [ 0.000000] PM: Registered nosave memory: 000000009f6df000 - 000000009f78a000 [ 0.000000] PM: Registered nosave memory: 000000009f78a000 - 000000009f7df000 [ 0.000000] PM: Registered nosave memory: 000000009f7df000 - 000000009f800000 [ 0.000000] PM: Registered nosave memory: 000000009f800000 - 00000000b0000000 [ 0.000000] PM: Registered nosave memory: 00000000b0000000 - 00000000fec00000 [ 0.000000] PM: Registered nosave memory: 00000000fec00000 - 00000000fec01000 [ 0.000000] PM: Registered nosave memory: 00000000fec01000 - 00000000fed1c000 [ 0.000000] PM: Registered nosave memory: 00000000fed1c000 - 00000000fed20000 [ 0.000000] PM: Registered nosave memory: 00000000fed20000 - 00000000fee00000 [ 0.000000] PM: Registered nosave memory: 00000000fee00000 - 00000000fee01000 [ 0.000000] PM: Registered nosave memory: 00000000fee01000 - 00000000ff800000 [ 0.000000] PM: Registered nosave memory: 00000000ff800000 - 0000000100000000 [ 0.000000] e820: [mem 0xb0000000-0xfebfffff] available for PCI devices [ 0.000000] Booting paravirtualized kernel on Xen [ 0.000000] Xen version: 4.3-unstable (preserve-AD) [ 0.000000] setup_percpu: NR_CPUS:64 nr_cpumask_bits:64 nr_cpu_ids:8 nr_node_ids:1 [ 0.000000] PERCPU: Embedded 28 pages/cpu @ffff88007fe00000 s83136 r8192 d23360 u262144 [ 7.896640] Built 1 zonelists in Zone order, mobility grouping on. Total pages: 5670523 [ 7.896644] Policy zone: Normal [ 7.896647] Kernel command line: ro root=/dev/mapper/vg_xenserver01-LV_ROOT rd_LVM_LV=vg_xenserver01/LV_ROOT rd_LVM_LV=vg_xenserver01/LV_SWAP rd_NO_LUKS rd_NO_MD rd_NO_DM LANG=en_US.UTF-8 SYSFONT=latarcyrheb-sun16 KEYTABLE=us nomodeset ixen-pciback.passthrough=1 xen-pciback.hide=(0d:08.0)(0d:09.0)(0a:00.0) earlyprintk=xen [ 7.896813] PID hash table entries: 4096 (order: 3, 32768 bytes) [ 7.896819] __ex_table already sorted, skipping sort [ 7.931839] software IO TLB [mem 0x62a00000-0x669fffff] (64MB) mapped at [ffff880062a00000-ffff8800669fffff] [ 7.939410] Memory: 1592636k/24683044k available (8177k kernel code, 1610316k absent, 21480092k reserved, 4886k data, 728k init) [ 7.939490] SLUB: Genslabs=15, HWalign=64, Order=0-3, MinObjects=0, CPUs=2, Nodes=1 [ 7.939516] Hierarchical RCU implementation. [ 7.939518] RCU restricting CPUs from NR_CPUS=64 to nr_cpu_ids=2. [ 7.939527] NR_IRQS:4352 nr_irqs:512 16 [ 7.939587] xen: sci override: global_irq=9 trigger=0 polarity=0 [ 7.939610] xen: acpi sci 9 [ 7.942204] Console: colour VGA+ 80x25 [ 7.942209] console [tty0] enabled, bootconsole disabled (XEN) traps.c:2584:d0 Domain attempted WRMSR 00000000000000e2 from 0x0000000006008403 to 0x0000000000008403. (XEN) traps.c:2584:d0 Domain attempted WRMSR 00000000000000e2 from 0x0000000006008403 to 0x0000000000008403. (XEN) Cannot bind IRQ2 to dom0. In use by 'cascade'. (XEN) Cannot bind IRQ2 to dom0. In use by 'cascade'. (XEN) Cannot bind IRQ2 to dom0. In use by 'cascade'. (XEN) Cannot bind IRQ2 to dom0. In use by 'cascade'. (XEN) Cannot bind IRQ2 to dom0. In use by 'cascade'. (XEN) Cannot bind IRQ2 to dom0. In use by 'cascade'. (XEN) Cannot bind IRQ2 to dom0. In use by 'cascade'. (XEN) Cannot bind IRQ2 to dom0. In use by 'cascade'. (XEN) Monitor-Mwait will be used to enter C1 state (XEN) Monitor-Mwait will be used to enter C3 state Kernel dmesg: [ 0.000000] Initializing cgroup subsys cpuset [ 0.000000] Initializing cgroup subsys cpu [ 0.000000] Linux version 3.6.0-rc4+ (root@xen-server01.ark-net.org) (gcc version 4.5.1 20100924 (Red Hat 4.5.1-4) (GCC) ) #2 SMP Mon Sep 10 14:42:44 EDT 2012 [ 0.000000] Command line: ro root=/dev/mapper/vg_xenserver01-LV_ROOT rd_LVM_LV=vg_xenserver01/LV_ROOT rd_LVM_LV=vg_xenserver01/LV_SWAP rd_NO_LUKS rd_NO_MD rd_NO_DM LANG=en_US.UTF-8 SYSFONT=latarcyrheb-sun16 KEYTABLE=us nomodeset ixen-pciback.passthrough=1 xen-pciback.hide=(0d:08.0)(0d:09.0)(0a:00.0) earlyprintk=xen [ 0.000000] Freeing 99-100 pfn range: 103 pages freed [ 0.000000] 1-1 mapping on 99->100 [ 0.000000] 1-1 mapping on 9dbe4->100000 [ 0.000000] Released 103 pages of unused memory [ 0.000000] Set 402563 page(s) to 1-1 mapping [ 0.000000] Populating 80000-80067 pfn range: 103 pages added [ 0.000000] e820: BIOS-provided physical RAM map: [ 0.000000] Xen: [mem 0x0000000000000000-0x0000000000098fff] usable [ 0.000000] Xen: [mem 0x0000000000099400-0x00000000000fffff] reserved [ 0.000000] Xen: [mem 0x0000000000100000-0x000000009dbe3fff] usable [ 0.000000] Xen: [mem 0x000000009dbe4000-0x000000009dcb5fff] ACPI NVS [ 0.000000] Xen: [mem 0x000000009dcb6000-0x000000009f6a3fff] ACPI data [ 0.000000] Xen: [mem 0x000000009f6a4000-0x000000009f6defff] reserved [ 0.000000] Xen: [mem 0x000000009f6df000-0x000000009f789fff] ACPI data [ 0.000000] Xen: [mem 0x000000009f78a000-0x000000009f7defff] ACPI NVS [ 0.000000] Xen: [mem 0x000000009f7df000-0x000000009f7fffff] ACPI data [ 0.000000] Xen: [mem 0x000000009f800000-0x00000000afffffff] reserved [ 0.000000] Xen: [mem 0x00000000fec00000-0x00000000fec00fff] reserved [ 0.000000] Xen: [mem 0x00000000fed1c000-0x00000000fed1ffff] reserved [ 0.000000] Xen: [mem 0x00000000fee00000-0x00000000fee00fff] reserved [ 0.000000] Xen: [mem 0x00000000ff800000-0x00000000ffffffff] reserved [ 0.000000] Xen: [mem 0x0000000100000000-0x00000005e2888fff] usable [ 0.000000] Xen: [mem 0x00000005e2889000-0x000000085fffffff] unusable [ 0.000000] bootconsole [xenboot0] enabled [ 0.000000] NX (Execute Disable) protection: active [ 0.000000] DMI 2.5 present. [ 0.000000] DMI: Intel Corporation S3420GP/S3420GP, BIOS S3420GP.86B.01.00.0050.090220111526 09/02/2011 [ 0.000000] e820: update [mem 0x00000000-0x0000ffff] usable ==> reserved [ 0.000000] e820: remove [mem 0x000a0000-0x000fffff] usable [ 0.000000] No AGP bridge found [ 0.000000] e820: last_pfn = 0x5e2889 max_arch_pfn = 0x400000000 [ 0.000000] e820: last_pfn = 0x9dbe4 max_arch_pfn = 0x400000000 [ 0.000000] found SMP MP-table at [mem 0x000fda10-0x000fda1f] mapped at [ffff8800000fda10] [ 0.000000] initial memory mapped: [mem 0x00000000-0x02c47fff] [ 0.000000] Base memory trampoline at [ffff880000093000] 93000 size 24576 [ 0.000000] init_memory_mapping: [mem 0x00000000-0x9dbe3fff] [ 0.000000] [mem 0x00000000-0x9dbe3fff] page 4k [ 0.000000] kernel direct mapping tables up to 0x9dbe3fff @ [mem 0x00b0e000-0x00ffffff] [ 0.000000] xen: setting RW the range fe0000 - 1000000 [ 0.000000] init_memory_mapping: [mem 0x100000000-0x5e2888fff] [ 0.000000] [mem 0x100000000-0x5e2888fff] page 4k [ 0.000000] kernel direct mapping tables up to 0x5e2888fff @ [mem 0x7d139000-0x80066fff] [ 0.000000] xen: setting RW the range 7f862000 - 80067000 [ 0.000000] RAMDISK: [mem 0x0229b000-0x02c47fff] [ 0.000000] ACPI: RSDP 00000000000f0410 00024 (v02 INTEL ) [ 0.000000] ACPI: XSDT 000000009f7fd120 00094 (v01 INTEL S3420GPX 00000000 01000013) [ 0.000000] ACPI: FACP 000000009f7fb000 000F4 (v04 INTEL S3420GPX 00000000 MSFT 0100000D) [ 0.000000] ACPI: DSDT 000000009f7f5000 055D6 (v02 INTEL S3420GPX 00000003 MSFT 0100000D) [ 0.000000] ACPI: FACS 000000009f78a000 00040 [ 0.000000] ACPI: APIC 000000009f7f4000 000BC (v02 INTEL S3420GPX 00000000 MSFT 0100000D) [ 0.000000] ACPI: MCFG 000000009f7f3000 0003C (v01 INTEL S3420GPX 00000001 MSFT 0100000D) [ 0.000000] ACPI: HPET 000000009f7f2000 00038 (v01 INTEL S3420GPX 00000001 MSFT 0100000D) [ 0.000000] ACPI: SLIT 000000009f7f1000 00030 (v01 INTEL S3420GPX 00000001 MSFT 0100000D) [ 0.000000] ACPI: SPCR 000000009f7f0000 00050 (v01 INTEL S3420GPX 00000000 MSFT 0100000D) [ 0.000000] ACPI: WDDT 000000009f7ef000 00040 (v01 INTEL S3420GPX 00000000 MSFT 0100000D) [ 0.000000] ACPI: SSDT 000000009f7e4000 0AEF4 (v02 INTEL SSDT PM 00004000 INTL 20061109) [ 0.000000] ACPI: SSDT 000000009f7e3000 001D8 (v02 INTEL IPMI 00004000 INTL 20061109) [ 0.000000] ACPI: XMAR 000000009f7e2000 000A8 (v01 INTEL S3420GPX 00000001 MSFT 0100000D) [ 0.000000] ACPI: HEST 000000009f7e1000 000A8 (v01 INTEL S3420GPX 00000001 INTL 00000001) [ 0.000000] ACPI: BERT 000000009f7e0000 00030 (v01 INTEL S3420GPX 00000001 INTL 00000001) [ 0.000000] ACPI: ERST 000000009f7df000 00230 (v01 INTEL S3420GPX 00000001 INTL 00000001) [ 0.000000] ACPI: EINJ 000000009f789000 00130 (v01 INTEL S3420GPX 00000001 INTL 00000001) [ 0.000000] ACPI: Local APIC address 0xfee00000 [ 0.000000] NUMA: Initialized distance table, cnt=1 [ 0.000000] NUMA: Warning: node ids are out of bound, from=-1 to=-1 distance=10 [ 0.000000] No NUMA configuration found [ 0.000000] Faking a node at [mem 0x0000000000000000-0x00000005e2888fff] [ 0.000000] Initmem setup node 0 [mem 0x00000000-0x5e2888fff] [ 0.000000] NODE_DATA [mem 0x80063000-0x80066fff] [ 0.000000] Zone ranges: [ 0.000000] DMA [mem 0x00010000-0x00ffffff] [ 0.000000] DMA32 [mem 0x01000000-0xffffffff] [ 0.000000] Normal [mem 0x100000000-0x5e2888fff] [ 0.000000] Movable zone start for each node [ 0.000000] Early memory node ranges [ 0.000000] node 0: [mem 0x00010000-0x00098fff] [ 0.000000] node 0: [mem 0x00100000-0x9dbe3fff] [ 0.000000] node 0: [mem 0x100000000-0x5e2888fff] [ 0.000000] On node 0 totalpages: 5768182 [ 0.000000] DMA zone: 64 pages used for memmap [ 0.000000] DMA zone: 1240 pages reserved [ 0.000000] DMA zone: 2673 pages, LIFO batch:0 [ 0.000000] DMA32 zone: 16320 pages used for memmap [ 0.000000] DMA32 zone: 625700 pages, LIFO batch:31 [ 0.000000] Normal zone: 80035 pages used for memmap [ 0.000000] Normal zone: 5042150 pages, LIFO batch:31 [ 0.000000] ACPI: PM-Timer IO Port: 0x408 [ 0.000000] ACPI: Local APIC address 0xfee00000 [ 0.000000] ACPI: LAPIC (acpi_id[0x00] lapic_id[0x00] enabled) [ 0.000000] ACPI: LAPIC (acpi_id[0x01] lapic_id[0x02] enabled) [ 0.000000] ACPI: LAPIC (acpi_id[0x02] lapic_id[0x04] enabled) [ 0.000000] ACPI: LAPIC (acpi_id[0x03] lapic_id[0x06] enabled) [ 0.000000] ACPI: LAPIC (acpi_id[0x04] lapic_id[0x01] enabled) [ 0.000000] ACPI: LAPIC (acpi_id[0x05] lapic_id[0x03] enabled) [ 0.000000] ACPI: LAPIC (acpi_id[0x06] lapic_id[0x05] enabled) [ 0.000000] ACPI: LAPIC (acpi_id[0x07] lapic_id[0x07] enabled) [ 0.000000] ACPI: LAPIC_NMI (acpi_id[0x00] high level lint[0x1]) [ 0.000000] ACPI: LAPIC_NMI (acpi_id[0x01] high level lint[0x1]) [ 0.000000] ACPI: LAPIC_NMI (acpi_id[0x02] high level lint[0x1]) [ 0.000000] ACPI: LAPIC_NMI (acpi_id[0x03] high level lint[0x1]) [ 0.000000] ACPI: LAPIC_NMI (acpi_id[0x04] high level lint[0x1]) [ 0.000000] ACPI: LAPIC_NMI (acpi_id[0x05] high level lint[0x1]) [ 0.000000] ACPI: LAPIC_NMI (acpi_id[0x06] high level lint[0x1]) [ 0.000000] ACPI: LAPIC_NMI (acpi_id[0x07] high level lint[0x1]) [ 0.000000] ACPI: IOAPIC (id[0x08] address[0xfec00000] gsi_base[0]) [ 0.000000] IOAPIC[0]: apic_id 8, version 32, address 0xfec00000, GSI 0-23 [ 0.000000] ACPI: INT_SRC_OVR (bus 0 bus_irq 0 global_irq 2 dfl dfl) [ 0.000000] ACPI: INT_SRC_OVR (bus 0 bus_irq 9 global_irq 9 high level) [ 0.000000] ACPI: IRQ0 used by override. [ 0.000000] ACPI: IRQ2 used by override. [ 0.000000] ACPI: IRQ9 used by override. [ 0.000000] Using ACPI (MADT) for SMP configuration information [ 0.000000] ACPI: HPET id: 0x8086a801 base: 0xfed00000 [ 0.000000] smpboot: Allowing 8 CPUs, 0 hotplug CPUs [ 0.000000] nr_irqs_gsi: 40 [ 0.000000] PM: Registered nosave memory: 0000000000099000 - 000000000009a000 [ 0.000000] PM: Registered nosave memory: 000000000009a000 - 0000000000100000 [ 0.000000] PM: Registered nosave memory: 000000009dbe4000 - 000000009dcb6000 [ 0.000000] PM: Registered nosave memory: 000000009dcb6000 - 000000009f6a4000 [ 0.000000] PM: Registered nosave memory: 000000009f6a4000 - 000000009f6df000 [ 0.000000] PM: Registered nosave memory: 000000009f6df000 - 000000009f78a000 [ 0.000000] PM: Registered nosave memory: 000000009f78a000 - 000000009f7df000 [ 0.000000] PM: Registered nosave memory: 000000009f7df000 - 000000009f800000 [ 0.000000] PM: Registered nosave memory: 000000009f800000 - 00000000b0000000 [ 0.000000] PM: Registered nosave memory: 00000000b0000000 - 00000000fec00000 [ 0.000000] PM: Registered nosave memory: 00000000fec00000 - 00000000fec01000 [ 0.000000] PM: Registered nosave memory: 00000000fec01000 - 00000000fed1c000 [ 0.000000] PM: Registered nosave memory: 00000000fed1c000 - 00000000fed20000 [ 0.000000] PM: Registered nosave memory: 00000000fed20000 - 00000000fee00000 [ 0.000000] PM: Registered nosave memory: 00000000fee00000 - 00000000fee01000 [ 0.000000] PM: Registered nosave memory: 00000000fee01000 - 00000000ff800000 [ 0.000000] PM: Registered nosave memory: 00000000ff800000 - 0000000100000000 [ 0.000000] e820: [mem 0xb0000000-0xfebfffff] available for PCI devices [ 0.000000] Booting paravirtualized kernel on Xen [ 0.000000] Xen version: 4.3-unstable (preserve-AD) [ 0.000000] setup_percpu: NR_CPUS:64 nr_cpumask_bits:64 nr_cpu_ids:8 nr_node_ids:1 [ 0.000000] PERCPU: Embedded 28 pages/cpu @ffff88007fe00000 s83136 r8192 d23360 u262144 [ 0.000000] pcpu-alloc: s83136 r8192 d23360 u262144 alloc=1*2097152 [ 0.000000] pcpu-alloc: [0] 0 1 2 3 4 5 6 7 [ 7.896640] Built 1 zonelists in Zone order, mobility grouping on. Total pages: 5670523 [ 7.896644] Policy zone: Normal [ 7.896647] Kernel command line: ro root=/dev/mapper/vg_xenserver01-LV_ROOT rd_LVM_LV=vg_xenserver01/LV_ROOT rd_LVM_LV=vg_xenserver01/LV_SWAP rd_NO_LUKS rd_NO_MD rd_NO_DM LANG=en_US.UTF-8 SYSFONT=latarcyrheb-sun16 KEYTABLE=us nomodeset ixen-pciback.passthrough=1 xen-pciback.hide=(0d:08.0)(0d:09.0)(0a:00.0) earlyprintk=xen [ 7.896813] PID hash table entries: 4096 (order: 3, 32768 bytes) [ 7.896819] __ex_table already sorted, skipping sort [ 7.931839] software IO TLB [mem 0x62a00000-0x669fffff] (64MB) mapped at [ffff880062a00000-ffff8800669fffff] [ 7.939410] Memory: 1592636k/24683044k available (8177k kernel code, 1610316k absent, 21480092k reserved, 4886k data, 728k init) [ 7.939490] SLUB: Genslabs=15, HWalign=64, Order=0-3, MinObjects=0, CPUs=2, Nodes=1 [ 7.939516] Hierarchical RCU implementation. [ 7.939518] RCU restricting CPUs from NR_CPUS=64 to nr_cpu_ids=2. [ 7.939527] NR_IRQS:4352 nr_irqs:512 16 [ 7.939587] xen: sci override: global_irq=9 trigger=0 polarity=0 [ 7.939590] xen: registering gsi 9 triggering 0 polarity 0 [ 7.939603] xen: --> pirq=9 -> irq=9 (gsi=9) [ 7.939610] xen: acpi sci 9 [ 7.939615] xen: --> pirq=1 -> irq=1 (gsi=1) [ 7.939618] xen: --> pirq=2 -> irq=2 (gsi=2) [ 7.939621] xen: --> pirq=3 -> irq=3 (gsi=3) [ 7.939624] xen: --> pirq=4 -> irq=4 (gsi=4) [ 7.939627] xen: --> pirq=5 -> irq=5 (gsi=5) [ 7.939630] xen: --> pirq=6 -> irq=6 (gsi=6) [ 7.939633] xen: --> pirq=7 -> irq=7 (gsi=7) [ 7.939636] xen: --> pirq=8 -> irq=8 (gsi=8) [ 7.939639] xen: --> pirq=10 -> irq=10 (gsi=10) [ 7.939642] xen: --> pirq=11 -> irq=11 (gsi=11) [ 7.939645] xen: --> pirq=12 -> irq=12 (gsi=12) [ 7.939648] xen: --> pirq=13 -> irq=13 (gsi=13) [ 7.939651] xen: --> pirq=14 -> irq=14 (gsi=14) [ 7.939654] xen: --> pirq=15 -> irq=15 (gsi=15) [ 7.942204] Console: colour VGA+ 80x25 [ 7.942209] console [tty0] enabled, bootconsole disabled [ 7.942303] Xen: using vcpuop timer interface [ 7.942307] installing Xen timer for CPU 0 [ 7.942388] tsc: Detected 2533.348 MHz processor [ 7.942452] Calibrating delay loop (skipped), value calculated using timer frequency.. 5066.69 BogoMIPS (lpj=2533348) [ 7.942579] pid_max: default: 32768 minimum: 301 [ 7.942665] Security Framework initialized [ 7.942726] SELinux: Initializing. [ 7.942792] SELinux: Starting in permissive mode [ 7.946946] Dentry cache hash table entries: 4194304 (order: 13, 33554432 bytes) [ 7.957309] Inode-cache hash table entries: 2097152 (order: 12, 16777216 bytes) [ 7.961265] Mount-cache hash table entries: 256 [ 7.961582] Initializing cgroup subsys cpuacct [ 7.961644] Initializing cgroup subsys freezer [ 7.961759] CPU: Physical Processor ID: 0 [ 7.961817] CPU: Processor Core ID: 0 [ 7.961876] mce: CPU supports 2 MCE banks [ 7.961949] Last level iTLB entries: 4KB 512, 2MB 7, 4MB 7 [ 7.961949] Last level dTLB entries: 4KB 512, 2MB 32, 4MB 32 [ 7.961949] tlb_flushall_shift is 0x6 [ 7.964384] ACPI: Core revision 20120711 [ 7.976039] cpu 0 spinlock event irq 41 [ 7.976113] Performance Events: unsupported p6 CPU model 30 no PMU driver, software events only. [ 7.976529] installing Xen timer for CPU 1 [ 7.976677] cpu 1 spinlock event irq 48 [ 7.976995] Brought up 2 CPUs [ 7.977609] PM: Registering ACPI NVS region [mem 0x9dbe4000-0x9dcb5fff] (860160 bytes) [ 7.977846] PM: Registering ACPI NVS region [mem 0x9f78a000-0x9f7defff] (348160 bytes) [ 7.978107] Grant tables using version 2 layout. [ 7.978263] Grant table initialized [ 7.978425] RTC time: 23:56:03, date: 09/11/12 [ 7.978590] NET: Registered protocol family 16 [ 7.978902] kworker/u:0 (17) used greatest stack depth: 6336 bytes left [ 7.979061] kworker/u:0 (18) used greatest stack depth: 5816 bytes left [ 7.979937] ACPI FADT declares the system doesn't support PCIe ASPM, so disable it [ 7.980167] ACPI: bus type pci registered [ 7.980981] PCI: MMCONFIG for domain 0000 [bus 00-ff] at [mem 0xa0000000-0xafffffff] (base 0xa0000000) [ 7.981215] PCI: MMCONFIG at [mem 0xa0000000-0xafffffff] reserved in E820 [ 8.024972] PCI: Using configuration type 1 for base access [ 8.025320] kworker/u:0 (42) used greatest stack depth: 5360 bytes left [ 8.041080] bio: create slab at 0 [ 8.041391] ACPI: Added _OSI(Module Device) [ 8.041527] ACPI: Added _OSI(Processor Device) [ 8.041661] ACPI: Added _OSI(3.0 _SCP Extensions) [ 8.041796] ACPI: Added _OSI(Processor Aggregator Device) [ 8.043144] ACPI: EC: Look up EC in DSDT [ 8.043299] ACPI Error: Field [CPB3] at 96 exceeds Buffer [NULL] size 64 (bits) (20120711/dsopcode-236) [ 8.043619] ACPI Error: Method parse/execution failed [\_SB_._OSC] (Node ffff88005f474550), AE_AML_BUFFER_LIMIT (20120711/psparse-536) [ 8.052059] ACPI: Interpreter enabled [ 8.052195] ACPI: (supports S0 S1 S5) [ 8.052470] ACPI: Using IOAPIC for interrupt routing [ 8.067768] ACPI: No dock devices found. [ 8.067906] PCI: Using host bridge windows from ACPI; if necessary, use "pci=nocrs" and report a bug [ 8.068402] ACPI: PCI Root Bridge [PCI0] (domain 0000 [bus 00-fe]) [ 8.068935] pci_root PNP0A08:00: ignoring host bridge window [mem 0x000c4000-0x000cbfff] (conflicts with Video ROM [mem 0x000c0000-0x000c7fff]) [ 8.069248] PCI host bridge to bus 0000:00 [ 8.069386] pci_bus 0000:00: busn_res: [bus 00-fe] is inserted under domain [bus 00-ff] [ 8.069388] pci_bus 0000:00: root bus resource [bus 00-fe] [ 8.069526] pci_bus 0000:00: root bus resource [io 0x0000-0x0cf7] [ 8.069666] pci_bus 0000:00: root bus resource [io 0x0d00-0xffff] [ 8.069806] pci_bus 0000:00: root bus resource [mem 0x000a0000-0x000bffff] [ 8.069973] pci_bus 0000:00: root bus resource [mem 0xfed40000-0xfedfffff] [ 8.070120] pci_bus 0000:00: root bus resource [mem 0xb0000000-0xfdffffff] [ 8.070279] pci 0000:00:00.0: [8086:d130] type 00 class 0x060000 [ 8.070379] pci 0000:00:03.0: [8086:d138] type 01 class 0x060400 [ 8.070466] pci 0000:00:03.0: PME# supported from D0 D3hot D3cold [ 8.070512] pci 0000:00:08.0: [8086:d155] type 00 class 0x088000 [ 8.070627] pci 0000:00:08.1: [8086:d156] type 00 class 0x088000 [ 8.070742] pci 0000:00:08.2: [8086:d157] type 00 class 0x088000 [ 8.070851] pci 0000:00:08.3: [8086:d158] type 00 class 0x088000 [ 8.070961] pci 0000:00:10.0: [8086:d150] type 00 class 0x088000 [ 8.071080] pci 0000:00:10.1: [8086:d151] type 00 class 0x088000 [ 8.071214] pci 0000:00:19.0: [8086:10ef] type 00 class 0x020000 [ 8.071245] pci 0000:00:19.0: reg 10: [mem 0xba700000-0xba71ffff] [ 8.071259] pci 0000:00:19.0: reg 14: [mem 0xba725000-0xba725fff] [ 8.071273] pci 0000:00:19.0: reg 18: [io 0x4040-0x405f] [ 8.071365] pci 0000:00:19.0: PME# supported from D0 D3hot D3cold [ 8.071407] pci 0000:00:1a.0: [8086:3b3c] type 00 class 0x0c0320 [ 8.071439] pci 0000:00:1a.0: reg 10: [mem 0xba722000-0xba7223ff] [ 8.071566] pci 0000:00:1a.0: PME# supported from D0 D3hot D3cold [ 8.071604] pci 0000:00:1c.0: [8086:3b42] type 01 class 0x060400 [ 8.071705] pci 0000:00:1c.0: PME# supported from D0 D3hot D3cold [ 8.071749] pci 0000:00:1c.4: [8086:3b4a] type 01 class 0x060400 [ 8.071848] pci 0000:00:1c.4: PME# supported from D0 D3hot D3cold [ 8.071888] pci 0000:00:1c.6: [8086:3b4e] type 01 class 0x060400 [ 8.071987] pci 0000:00:1c.6: PME# supported from D0 D3hot D3cold [ 8.072026] pci 0000:00:1c.7: [8086:3b50] type 01 class 0x060400 [ 8.072138] pci 0000:00:1c.7: PME# supported from D0 D3hot D3cold [ 8.072184] pci 0000:00:1d.0: [8086:3b34] type 00 class 0x0c0320 [ 8.072217] pci 0000:00:1d.0: reg 10: [mem 0xba721000-0xba7213ff] [ 8.072348] pci 0000:00:1d.0: PME# supported from D0 D3hot D3cold [ 8.072383] pci 0000:00:1e.0: [8086:244e] type 01 class 0x060401 [ 8.072482] pci 0000:00:1f.0: [8086:3b14] type 00 class 0x060100 [ 8.072665] pci 0000:00:1f.2: [8086:3b22] type 00 class 0x010601 [ 8.072697] pci 0000:00:1f.2: reg 10: [io 0x4068-0x406f] [ 8.072711] pci 0000:00:1f.2: reg 14: [io 0x4074-0x4077] [ 8.072725] pci 0000:00:1f.2: reg 18: [io 0x4060-0x4067] [ 8.072738] pci 0000:00:1f.2: reg 1c: [io 0x4070-0x4073] [ 8.072752] pci 0000:00:1f.2: reg 20: [io 0x4020-0x403f] [ 8.072765] pci 0000:00:1f.2: reg 24: [mem 0xba720000-0xba7207ff] [ 8.072828] pci 0000:00:1f.2: PME# supported from D3hot [ 8.072861] pci 0000:00:1f.3: [8086:3b30] type 00 class 0x0c0500 [ 8.072885] pci 0000:00:1f.3: reg 10: [mem 0xba723000-0xba7230ff 64bit] [ 8.072923] pci 0000:00:1f.3: reg 20: [io 0x4000-0x401f] [ 8.073033] pci_bus 0000:01: busn_res: [bus 01-05] is inserted under [bus 00-fe] [ 8.073053] pci 0000:01:00.0: [111d:806f] type 01 class 0x060400 [ 8.073150] pci 0000:01:00.0: PME# supported from D0 D3hot D3cold [ 8.073571] pci 0000:00:03.0: PCI bridge to [bus 01-05] [ 8.073714] pci 0000:00:03.0: bridge window [io 0x3000-0x3fff] [ 8.073719] pci 0000:00:03.0: bridge window [mem 0xba600000-0xba6fffff] [ 8.073783] pci_bus 0000:02: busn_res: [bus 02-05] is inserted under [bus 01-05] [ 8.073806] pci 0000:02:02.0: [111d:806f] type 01 class 0x060400 [ 8.073909] pci 0000:02:02.0: PME# supported from D0 D3hot D3cold [ 8.073954] pci 0000:02:03.0: [111d:806f] type 01 class 0x060400 [ 8.074056] pci 0000:02:03.0: PME# supported from D0 D3hot D3cold [ 8.074100] pci 0000:02:04.0: [111d:806f] type 01 class 0x060400 [ 8.074202] pci 0000:02:04.0: PME# supported from D0 D3hot D3cold [ 8.074280] pci 0000:01:00.0: PCI bridge to [bus 02-05] [ 8.074429] pci 0000:01:00.0: bridge window [io 0x3000-0x3fff] [ 8.074435] pci 0000:01:00.0: bridge window [mem 0xba600000-0xba6fffff] [ 8.074512] pci_bus 0000:03: busn_res: [bus 03] is inserted under [bus 02-05] [ 8.074516] pci 0000:02:02.0: PCI bridge to [bus 03] [ 8.074749] pci_bus 0000:04: busn_res: [bus 04] is inserted under [bus 02-05] [ 8.074753] pci 0000:02:03.0: PCI bridge to [bus 04] [ 8.074982] pci_bus 0000:05: busn_res: [bus 05] is inserted under [bus 02-05] [ 8.075004] pci 0000:05:00.0: [1000:0079] type 00 class 0x010400 [ 8.075023] pci 0000:05:00.0: reg 10: [io 0x3000-0x30ff] [ 8.075046] pci 0000:05:00.0: reg 14: [mem 0xba640000-0xba643fff 64bit] [ 8.075068] pci 0000:05:00.0: reg 1c: [mem 0xba600000-0xba63ffff 64bit] [ 8.075097] pci 0000:05:00.0: reg 30: [mem 0xfffc0000-0xffffffff pref] [ 8.075145] pci 0000:05:00.0: supports D1 D2 [ 8.075195] pci 0000:02:04.0: PCI bridge to [bus 05] [ 8.075348] pci 0000:02:04.0: bridge window [io 0x3000-0x3fff] [ 8.075355] pci 0000:02:04.0: bridge window [mem 0xba600000-0xba6fffff] [ 8.075472] pci_bus 0000:06: busn_res: [bus 06-08] is inserted under [bus 00-fe] [ 8.075506] pci 0000:06:00.0: [8086:10c9] type 00 class 0x020000 [ 8.075527] pci 0000:06:00.0: reg 10: [mem 0xba420000-0xba43ffff] [ 8.075545] pci 0000:06:00.0: reg 14: [mem 0xba000000-0xba3fffff] [ 8.075562] pci 0000:06:00.0: reg 18: [io 0x2020-0x203f] [ 8.075579] pci 0000:06:00.0: reg 1c: [mem 0xba4c4000-0xba4c7fff] [ 8.075627] pci 0000:06:00.0: reg 30: [mem 0xffc00000-0xffffffff pref] [ 8.075688] pci 0000:06:00.0: PME# supported from D0 D3hot D3cold [ 8.075754] pci 0000:06:00.0: reg 184: [mem 0xba440000-0xba443fff 64bit] [ 8.075783] pci 0000:06:00.0: reg 190: [mem 0xba460000-0xba463fff 64bit] [ 8.075839] pci 0000:06:00.1: [8086:10c9] type 00 class 0x020000 [ 8.075860] pci 0000:06:00.1: reg 10: [mem 0xba400000-0xba41ffff] [ 8.075877] pci 0000:06:00.1: reg 14: [mem 0xb9c00000-0xb9ffffff] [ 8.075895] pci 0000:06:00.1: reg 18: [io 0x2000-0x201f] [ 8.075912] pci 0000:06:00.1: reg 1c: [mem 0xba4c0000-0xba4c3fff] [ 8.075960] pci 0000:06:00.1: reg 30: [mem 0xffc00000-0xffffffff pref] [ 8.076021] pci 0000:06:00.1: PME# supported from D0 D3hot D3cold [ 8.076076] pci 0000:06:00.1: reg 184: [mem 0xba480000-0xba483fff 64bit] [ 8.076105] pci 0000:06:00.1: reg 190: [mem 0xba4a0000-0xba4a3fff 64bit] [ 8.078634] pci 0000:00:1c.0: PCI bridge to [bus 06-08] [ 8.078788] pci 0000:00:1c.0: bridge window [io 0x2000-0x2fff] [ 8.078793] pci 0000:00:1c.0: bridge window [mem 0xb9c00000-0xba4fffff] [ 8.078871] pci_bus 0000:09: busn_res: [bus 09] is inserted under [bus 00-fe] [ 8.078910] pci 0000:09:00.0: [8086:10d3] type 00 class 0x020000 [ 8.078939] pci 0000:09:00.0: reg 10: [mem 0xba500000-0xba51ffff] [ 8.078987] pci 0000:09:00.0: reg 18: [io 0x1000-0x101f] [ 8.079010] pci 0000:09:00.0: reg 1c: [mem 0xba520000-0xba523fff] [ 8.079150] pci 0000:09:00.0: PME# supported from D0 D3hot D3cold [ 8.081852] pci 0000:00:1c.4: PCI bridge to [bus 09] [ 8.082007] pci 0000:00:1c.4: bridge window [io 0x1000-0x1fff] [ 8.082012] pci 0000:00:1c.4: bridge window [mem 0xba500000-0xba5fffff] [ 8.082090] pci_bus 0000:0a: busn_res: [bus 0a] is inserted under [bus 00-fe] [ 8.082120] pci 0000:0a:00.0: [102b:0522] type 00 class 0x030000 [ 8.082145] pci 0000:0a:00.0: reg 10: [mem 0xb8000000-0xb8ffffff pref] [ 8.082166] pci 0000:0a:00.0: reg 14: [mem 0xb9800000-0xb9803fff] [ 8.082186] pci 0000:0a:00.0: reg 18: [mem 0xb9000000-0xb97fffff] [ 8.082266] pci 0000:0a:00.0: reg 30: [mem 0xffff0000-0xffffffff pref] [ 8.085090] pci 0000:00:1c.6: PCI bridge to [bus 0a] [ 8.085255] pci 0000:00:1c.6: bridge window [mem 0xb9000000-0xb98fffff] [ 8.085264] pci 0000:00:1c.6: bridge window [mem 0xb8000000-0xb8ffffff 64bit pref] [ 8.085334] pci_bus 0000:0b: busn_res: [bus 0b] is inserted under [bus 00-fe] [ 8.085338] pci 0000:00:1c.7: PCI bridge to [bus 0b] [ 8.085529] pci_bus 0000:0c: busn_res: [bus 0c-0d] is inserted under [bus 00-fe] [ 8.085550] pci 0000:0c:00.0: [3388:0021] type 01 class 0x060400 [ 8.085651] pci 0000:0c:00.0: supports D1 D2 [ 8.085653] pci 0000:0c:00.0: PME# supported from D1 D2 D3hot D3cold [ 8.085733] pci 0000:00:1e.0: PCI bridge to [bus 0c-0d] (subtractive decode) [ 8.085891] pci 0000:00:1e.0: bridge window [mem 0xb0000000-0xb7ffffff 64bit pref] [ 8.085893] pci 0000:00:1e.0: bridge window [io 0x0000-0x0cf7] (subtractive decode) [ 8.085895] pci 0000:00:1e.0: bridge window [io 0x0d00-0xffff] (subtractive decode) [ 8.085897] pci 0000:00:1e.0: bridge window [mem 0x000a0000-0x000bffff] (subtractive decode) [ 8.085899] pci 0000:00:1e.0: bridge window [mem 0xfed40000-0xfedfffff] (subtractive decode) [ 8.085900] pci 0000:00:1e.0: bridge window [mem 0xb0000000-0xfdffffff] (subtractive decode) [ 8.085959] pci_bus 0000:0d: busn_res: [bus 0d] is inserted under [bus 0c-0d] [ 8.085997] pci 0000:0d:08.0: [4444:0016] type 00 class 0x040000 [ 8.086027] pci 0000:0d:08.0: reg 10: [mem 0xb4000000-0xb7ffffff pref] [ 8.086194] pci 0000:0d:09.0: [4444:0016] type 00 class 0x040000 [ 8.086224] pci 0000:0d:09.0: reg 10: [mem 0xb0000000-0xb3ffffff pref] [ 8.086419] pci 0000:0c:00.0: PCI bridge to [bus 0d] [ 8.086574] pci 0000:0c:00.0: bridge window [mem 0xb0000000-0xb7ffffff pref] [ 8.086631] ACPI: PCI Interrupt Routing Table [\_SB_.PCI0._PRT] [ 8.086740] ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.MRP1._PRT] [ 8.086764] ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.MRP1.GRP1._PRT] [ 8.086806] ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.MRP1.GRP1.G2P1._PRT] [ 8.086872] ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.MRP1.GRP1.G2P2._PRT] [ 8.086937] ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.MRP1.GRP1.G2P3._PRT] [ 8.087015] ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.PEX0._PRT] [ 8.087065] ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.PEX4._PRT] [ 8.087084] ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.PEX6._PRT] [ 8.087103] ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.PEX7._PRT] [ 8.087149] ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.IP2P._PRT] [ 8.087273] pci0000:00: Unable to request _OSC control (_OSC support mask: 0x0f) [ 8.094005] ACPI: PCI Interrupt Link [LNKA] (IRQs 3 4 5 6 7 9 *10 11 12 14 15) [ 8.094894] ACPI: PCI Interrupt Link [LNKB] (IRQs 3 4 5 6 7 9 10 *11 12 14 15) [ 8.095754] ACPI: PCI Interrupt Link [LNKC] (IRQs 3 4 *5 6 7 9 10 11 12 14 15) [ 8.096622] ACPI: PCI Interrupt Link [LNKD] (IRQs 3 4 5 6 7 9 10 *11 12 14 15) [ 8.097484] ACPI: PCI Interrupt Link [LNKE] (IRQs 3 4 5 6 7 9 10 11 12 14 15) *0, disabled. [ 8.098449] ACPI: PCI Interrupt Link [LNKF] (IRQs 3 4 5 6 7 *9 10 11 12 14 15) [ 8.099325] ACPI: PCI Interrupt Link [LNKG] (IRQs 3 4 5 6 7 9 10 11 12 14 15) *0, disabled. [ 8.100275] ACPI: PCI Interrupt Link [LNKH] (IRQs 3 4 5 6 7 9 *10 11 12 14 15) [ 8.101225] xen/balloon: Initialising balloon driver. [ 8.184758] xen-balloon: Initialising balloon driver. [ 8.185074] xen/balloon: Xen selfballooning driver disabled for domain0. [ 8.185368] vgaarb: device added: PCI:0000:0a:00.0,decodes=io+mem,owns=io+mem,locks=none [ 8.185590] vgaarb: loaded [ 8.185719] vgaarb: bridge control possible 0000:0a:00.0 [ 8.186090] SCSI subsystem initialized [ 8.186225] ACPI: bus type scsi registered [ 8.186551] libata version 3.00 loaded. [ 8.186778] ACPI: bus type usb registered [ 8.187038] usbcore: registered new interface driver usbfs [ 8.187257] usbcore: registered new interface driver hub [ 8.187492] usbcore: registered new device driver usb [ 8.187844] pps_core: LinuxPPS API ver. 1 registered [ 8.187983] pps_core: Software ver. 5.3.6 - Copyright 2005-2007 Rodolfo Giometti [ 8.188268] PTP clock support registered [ 8.188684] Advanced Linux Sound Architecture Driver Version 1.0.25. [ 8.188828] PCI: Using ACPI for IRQ routing [ 8.201594] PCI: Discovered peer bus ff [ 8.201727] PCI: root bus ff: using default resources [ 8.201729] PCI: Probing PCI hardware (bus ff) [ 8.201802] PCI host bridge to bus 0000:ff [ 8.201939] pci_bus 0000:ff: root bus resource [io 0x0000-0xffff] [ 8.202082] pci_bus 0000:ff: root bus resource [mem 0x00000000-0xfffffffff] [ 8.202226] pci_bus 0000:ff: No busn resource found for root bus, will use [bus ff-ff] [ 8.202464] pci_bus 0000:ff: busn_res: [bus ff] is inserted under domain [bus 00-ff] [ 8.202478] pci 0000:ff:00.0: [8086:2c50] type 00 class 0x060000 [ 8.202533] pci 0000:ff:00.1: [8086:2c81] type 00 class 0x060000 [ 8.202591] pci 0000:ff:02.0: [8086:2c90] type 00 class 0x060000 [ 8.202641] pci 0000:ff:02.1: [8086:2c91] type 00 class 0x060000 [ 8.202698] pci 0000:ff:03.0: [8086:2c98] type 00 class 0x060000 [ 8.202748] pci 0000:ff:03.1: [8086:2c99] type 00 class 0x060000 [ 8.202797] pci 0000:ff:03.2: [8086:2c9a] type 00 class 0x060000 [ 8.202848] pci 0000:ff:03.4: [8086:2c9c] type 00 class 0x060000 [ 8.202901] pci 0000:ff:04.0: [8086:2ca0] type 00 class 0x060000 [ 8.202951] pci 0000:ff:04.1: [8086:2ca1] type 00 class 0x060000 [ 8.203001] pci 0000:ff:04.2: [8086:2ca2] type 00 class 0x060000 [ 8.203050] pci 0000:ff:04.3: [8086:2ca3] type 00 class 0x060000 [ 8.203105] pci 0000:ff:05.0: [8086:2ca8] type 00 class 0x060000 [ 8.203155] pci 0000:ff:05.1: [8086:2ca9] type 00 class 0x060000 [ 8.203205] pci 0000:ff:05.2: [8086:2caa] type 00 class 0x060000 [ 8.203254] pci 0000:ff:05.3: [8086:2cab] type 00 class 0x060000 [ 8.203337] pci_bus 0000:ff: busn_res: [bus ff] end is updated to ff [ 8.204457] PCI: pci_cache_line_size set to 64 bytes [ 8.204685] e820: reserve RAM buffer [mem 0x00099000-0x0009ffff] [ 8.204687] e820: reserve RAM buffer [mem 0x9dbe4000-0x9fffffff] [ 8.204689] e820: reserve RAM buffer [mem 0x5e2889000-0x5e3ffffff] [ 8.205242] NetLabel: Initializing [ 8.205375] NetLabel: domain hash size = 128 [ 8.205509] NetLabel: protocols = UNLABELED CIPSOv4 [ 8.205654] NetLabel: unlabeled traffic allowed by default [ 8.205820] cfg80211: Calling CRDA to update world regulatory domain [ 8.206051] Switching to clocksource xen [ 8.211838] pnp: PnP ACPI init [ 8.211980] ACPI: bus type pnp registered [ 8.212403] pnp 00:00: [bus 00-fe] [ 8.212406] pnp 00:00: [io 0x0cf8-0x0cff] [ 8.212408] pnp 00:00: [io 0x0000-0x0cf7 window] [ 8.212410] pnp 00:00: [io 0x0d00-0xffff window] [ 8.212412] pnp 00:00: [mem 0x000a0000-0x000bffff window] [ 8.212414] pnp 00:00: [mem 0x000c4000-0x000cbfff window] [ 8.212415] pnp 00:00: [mem 0xfed40000-0xfedfffff window] [ 8.212417] pnp 00:00: [mem 0xb0000000-0xfdffffff window] [ 8.212419] pnp 00:00: [mem 0x00000000 window] [ 8.212560] pnp 00:00: Plug and Play ACPI device, IDs PNP0a08 PNP0a03 (active) [ 8.212571] pnp 00:01: [mem 0xfec00000-0xfecfffff] [ 8.212641] pnp 00:01: Plug and Play ACPI device, IDs PNP0003 (active) [ 8.212838] pnp 00:02: [io 0x0000-0x000f] [ 8.212840] pnp 00:02: [io 0x0081-0x0083] [ 8.212841] pnp 00:02: [io 0x0087] [ 8.212843] pnp 00:02: [io 0x0089-0x008b] [ 8.212844] pnp 00:02: [io 0x008f] [ 8.212846] pnp 00:02: [io 0x00c0-0x00df] [ 8.212848] pnp 00:02: [dma 4] [ 8.212944] pnp 00:02: Plug and Play ACPI device, IDs PNP0200 (active) [ 8.212955] pnp 00:03: [io 0x0070-0x0071] [ 8.212956] pnp 00:03: [io 0x0074-0x0077] [ 8.212959] xen: registering gsi 8 triggering 1 polarity 0 [ 8.212968] pnp 00:03: [irq 8] [ 8.213063] pnp 00:03: Plug and Play ACPI device, IDs PNP0b00 (active) [ 8.213075] pnp 00:04: [io 0x00f0] [ 8.213077] xen: registering gsi 13 triggering 1 polarity 0 [ 8.213082] pnp 00:04: [irq 13] [ 8.213177] pnp 00:04: Plug and Play ACPI device, IDs PNP0c04 (active) [ 8.213189] pnp 00:05: [io 0x0061] [ 8.213295] pnp 00:05: Plug and Play ACPI device, IDs PNP0800 (active) [ 8.213335] pnp 00:06: [mem 0xfed00000-0xfed003ff] [ 8.213434] pnp 00:06: Plug and Play ACPI device, IDs PNP0103 (active) [ 8.213448] pnp 00:07: [io 0x0500-0x057f] [ 8.213450] pnp 00:07: [io 0x0600-0x061f] [ 8.213451] pnp 00:07: [io 0x0880-0x0883] [ 8.213453] pnp 00:07: [io 0x0ca4-0x0ca5] [ 8.213454] pnp 00:07: [io 0x0400-0x047f] [ 8.213456] pnp 00:07: [io 0x0092] [ 8.213457] pnp 00:07: [io 0x0010-0x001f] [ 8.213459] pnp 00:07: [io 0x0072-0x0073] [ 8.213460] pnp 00:07: [io 0x0080] [ 8.213462] pnp 00:07: [io 0x0084-0x0086] [ 8.213463] pnp 00:07: [io 0x0088] [ 8.213467] pnp 00:07: [io 0x008c-0x008e] [ 8.213469] pnp 00:07: [io 0x0090-0x009f] [ 8.213471] pnp 00:07: [io 0x0800-0x081f] [ 8.213472] pnp 00:07: [io 0x0ca2-0x0ca3] [ 8.213474] pnp 00:07: [mem 0xfed1c000-0xfed3fffe] [ 8.213475] pnp 00:07: [mem 0xff000000-0xffffffff] [ 8.213477] pnp 00:07: [mem 0xfee00000-0xfeefffff] [ 8.213478] pnp 00:07: [mem 0xfe900000-0xfe90001f] [ 8.213480] pnp 00:07: [mem 0xfea00000-0xfea0001f] [ 8.213482] pnp 00:07: [mem 0xfed1b000-0xfed1bfff] [ 8.213483] pnp 00:07: [mem 0xfed14000-0xfed17ffe] [ 8.213485] pnp 00:07: [mem 0xfed18000-0xfed18ffe] [ 8.213486] pnp 00:07: [mem 0xfed19000-0xfed19ffe] [ 8.213644] system 00:07: [io 0x0500-0x057f] has been reserved [ 8.213787] system 00:07: [io 0x0600-0x061f] has been reserved [ 8.213928] system 00:07: [io 0x0880-0x0883] has been reserved [ 8.214070] system 00:07: [io 0x0ca4-0x0ca5] has been reserved [ 8.214213] system 00:07: [io 0x0400-0x047f] has been reserved [ 8.214369] system 00:07: [io 0x0800-0x081f] has been reserved [ 8.214509] system 00:07: [io 0x0ca2-0x0ca3] has been reserved [ 8.214650] system 00:07: [mem 0xfed1c000-0xfed3fffe] could not be reserved [ 8.214794] system 00:07: [mem 0xff000000-0xffffffff] could not be reserved [ 8.214937] system 00:07: [mem 0xfee00000-0xfeefffff] could not be reserved [ 8.215081] system 00:07: [mem 0xfe900000-0xfe90001f] has been reserved [ 8.215224] system 00:07: [mem 0xfea00000-0xfea0001f] has been reserved [ 8.215375] system 00:07: [mem 0xfed1b000-0xfed1bfff] has been reserved [ 8.215518] system 00:07: [mem 0xfed14000-0xfed17ffe] has been reserved [ 8.215660] system 00:07: [mem 0xfed18000-0xfed18ffe] has been reserved [ 8.215803] system 00:07: [mem 0xfed19000-0xfed19ffe] has been reserved [ 8.215949] system 00:07: Plug and Play ACPI device, IDs PNP0c02 (active) [ 8.216077] pnp 00:08: [io 0x03f8-0x03ff] [ 8.216079] xen: registering gsi 4 triggering 1 polarity 0 [ 8.216085] pnp 00:08: [irq 4] [ 8.216215] pnp 00:08: Plug and Play ACPI device, IDs PNP0501 (active) [ 8.216361] pnp 00:09: [io 0x02f8-0x02ff] [ 8.216364] xen: registering gsi 3 triggering 1 polarity 0 [ 8.216369] pnp 00:09: [irq 3] [ 8.216496] pnp 00:09: Plug and Play ACPI device, IDs PNP0501 (active) [ 8.216539] pnp 00:0a: [io 0x0ca2] [ 8.216540] pnp 00:0a: [io 0x0ca3] [ 8.216640] pnp 00:0a: Plug and Play ACPI device, IDs IPI0001 (active) [ 8.216686] pnp: PnP ACPI: found 11 devices [ 8.216823] ACPI: ACPI bus type pnp unregistered [ 8.217028] pciback 0000:0a:00.0: seizing device [ 8.217169] pciback 0000:0d:08.0: seizing device [ 8.217322] pciback 0000:0d:09.0: seizing device [ 8.227141] PM-Timer failed consistency check (0x0xffffff) - aborting. [ 8.227308] pci 0000:05:00.0: no compatible bridge window for [mem 0xfffc0000-0xffffffff pref] [ 8.227541] pci 0000:06:00.0: no compatible bridge window for [mem 0xffc00000-0xffffffff pref] [ 8.227772] pci 0000:06:00.1: no compatible bridge window for [mem 0xffc00000-0xffffffff pref] [ 8.227996] pciback 0000:0a:00.0: no compatible bridge window for [mem 0xffff0000-0xffffffff pref] [ 8.228384] pci 0000:00:1c.0: BAR 15: assigned [mem 0xba800000-0xbaffffff pref] [ 8.228624] pci 0000:00:03.0: BAR 15: assigned [mem 0xb9900000-0xb99fffff pref] [ 8.228845] pci 0000:01:00.0: BAR 15: assigned [mem 0xb9900000-0xb99fffff pref] [ 8.229065] pci 0000:02:04.0: BAR 15: assigned [mem 0xb9900000-0xb99fffff pref] [ 8.229285] pci 0000:02:02.0: PCI bridge to [bus 03] [ 8.229450] pci 0000:02:03.0: PCI bridge to [bus 04] [ 8.229608] pci 0000:05:00.0: BAR 6: assigned [mem 0xb9900000-0xb993ffff pref] [ 8.229829] pci 0000:02:04.0: PCI bridge to [bus 05] [ 8.229968] pci 0000:02:04.0: bridge window [io 0x3000-0x3fff] [ 8.230116] pci 0000:02:04.0: bridge window [mem 0xba600000-0xba6fffff] [ 8.230264] pci 0000:02:04.0: bridge window [mem 0xb9900000-0xb99fffff pref] [ 8.230498] pci 0000:01:00.0: PCI bridge to [bus 02-05] [ 8.230638] pci 0000:01:00.0: bridge window [io 0x3000-0x3fff] [ 8.230787] pci 0000:01:00.0: bridge window [mem 0xba600000-0xba6fffff] [ 8.230936] pci 0000:01:00.0: bridge window [mem 0xb9900000-0xb99fffff pref] [ 8.231163] pci 0000:00:03.0: PCI bridge to [bus 01-05] [ 8.231311] pci 0000:00:03.0: bridge window [io 0x3000-0x3fff] [ 8.231458] pci 0000:00:03.0: bridge window [mem 0xba600000-0xba6fffff] [ 8.231604] pci 0000:00:03.0: bridge window [mem 0xb9900000-0xb99fffff pref] [ 8.231832] pci 0000:06:00.0: BAR 6: assigned [mem 0xba800000-0xbabfffff pref] [ 8.232054] pci 0000:06:00.1: BAR 6: assigned [mem 0xbac00000-0xbaffffff pref] [ 8.232272] pci 0000:00:1c.0: PCI bridge to [bus 06-08] [ 8.232419] pci 0000:00:1c.0: bridge window [io 0x2000-0x2fff] [ 8.232566] pci 0000:00:1c.0: bridge window [mem 0xb9c00000-0xba4fffff] [ 8.232713] pci 0000:00:1c.0: bridge window [mem 0xba800000-0xbaffffff pref] [ 8.232940] pci 0000:00:1c.4: PCI bridge to [bus 09] [ 8.233079] pci 0000:00:1c.4: bridge window [io 0x1000-0x1fff] [ 8.233225] pci 0000:00:1c.4: bridge window [mem 0xba500000-0xba5fffff] [ 8.233389] pciback 0000:0a:00.0: BAR 6: assigned [mem 0xb9810000-0xb981ffff pref] [ 8.234875] pci 0000:00:1c.6: PCI bridge to [bus 0a] [ 8.235020] pci 0000:00:1c.6: bridge window [mem 0xb9000000-0xb98fffff] [ 8.235167] pci 0000:00:1c.6: bridge window [mem 0xb8000000-0xb8ffffff 64bit pref] [ 8.235403] pci 0000:00:1c.7: PCI bridge to [bus 0b] [ 8.235555] pci 0000:0c:00.0: PCI bridge to [bus 0d] [ 8.235702] pci 0000:0c:00.0: bridge window [mem 0xb0000000-0xb7ffffff pref] [ 8.235926] pci 0000:00:1e.0: PCI bridge to [bus 0c-0d] [ 8.236072] pci 0000:00:1e.0: bridge window [mem 0xb0000000-0xb7ffffff 64bit pref] [ 8.236311] xen: registering gsi 16 triggering 0 polarity 1 [ 8.236325] xen: --> pirq=16 -> irq=16 (gsi=16) [ 8.236363] xen: registering gsi 16 triggering 0 polarity 1 [ 8.236364] Already setup the GSI :16 [ 8.236502] xen: registering gsi 16 triggering 0 polarity 1 [ 8.236503] Already setup the GSI :16 [ 8.236640] xen: registering gsi 18 triggering 0 polarity 1 [ 8.236645] xen: --> pirq=18 -> irq=18 (gsi=18) [ 8.236655] xen: registering gsi 19 triggering 0 polarity 1 [ 8.236659] xen: --> pirq=19 -> irq=19 (gsi=19) [ 8.236671] pci 0000:00:1e.0: setting latency timer to 64 [ 8.236683] pci 0000:0c:00.0: setting latency timer to 64 [ 8.236688] pci_bus 0000:00: resource 4 [io 0x0000-0x0cf7] [ 8.236689] pci_bus 0000:00: resource 5 [io 0x0d00-0xffff] [ 8.236691] pci_bus 0000:00: resource 6 [mem 0x000a0000-0x000bffff] [ 8.236693] pci_bus 0000:00: resource 7 [mem 0xfed40000-0xfedfffff] [ 8.236695] pci_bus 0000:00: resource 8 [mem 0xb0000000-0xfdffffff] [ 8.236697] pci_bus 0000:01: resource 0 [io 0x3000-0x3fff] [ 8.236698] pci_bus 0000:01: resource 1 [mem 0xba600000-0xba6fffff] [ 8.236700] pci_bus 0000:01: resource 2 [mem 0xb9900000-0xb99fffff pref] [ 8.236702] pci_bus 0000:02: resource 0 [io 0x3000-0x3fff] [ 8.236704] pci_bus 0000:02: resource 1 [mem 0xba600000-0xba6fffff] [ 8.236705] pci_bus 0000:02: resource 2 [mem 0xb9900000-0xb99fffff pref] [ 8.236707] pci_bus 0000:05: resource 0 [io 0x3000-0x3fff] [ 8.236709] pci_bus 0000:05: resource 1 [mem 0xba600000-0xba6fffff] [ 8.236711] pci_bus 0000:05: resource 2 [mem 0xb9900000-0xb99fffff pref] [ 8.236713] pci_bus 0000:06: resource 0 [io 0x2000-0x2fff] [ 8.236714] pci_bus 0000:06: resource 1 [mem 0xb9c00000-0xba4fffff] [ 8.236716] pci_bus 0000:06: resource 2 [mem 0xba800000-0xbaffffff pref] [ 8.236718] pci_bus 0000:09: resource 0 [io 0x1000-0x1fff] [ 8.236720] pci_bus 0000:09: resource 1 [mem 0xba500000-0xba5fffff] [ 8.236722] pci_bus 0000:0a: resource 1 [mem 0xb9000000-0xb98fffff] [ 8.236723] pci_bus 0000:0a: resource 2 [mem 0xb8000000-0xb8ffffff 64bit pref] [ 8.236725] pci_bus 0000:0c: resource 2 [mem 0xb0000000-0xb7ffffff 64bit pref] [ 8.236727] pci_bus 0000:0c: resource 4 [io 0x0000-0x0cf7] [ 8.236729] pci_bus 0000:0c: resource 5 [io 0x0d00-0xffff] [ 8.236731] pci_bus 0000:0c: resource 6 [mem 0x000a0000-0x000bffff] [ 8.236732] pci_bus 0000:0c: resource 7 [mem 0xfed40000-0xfedfffff] [ 8.236734] pci_bus 0000:0c: resource 8 [mem 0xb0000000-0xfdffffff] [ 8.236736] pci_bus 0000:0d: resource 2 [mem 0xb0000000-0xb7ffffff pref] [ 8.236738] pci_bus 0000:ff: resource 4 [io 0x0000-0xffff] [ 8.236740] pci_bus 0000:ff: resource 5 [mem 0x00000000-0xfffffffff] [ 8.236763] NET: Registered protocol family 2 [ 8.238065] TCP established hash table entries: 524288 (order: 11, 8388608 bytes) [ 8.240818] TCP bind hash table entries: 65536 (order: 8, 1048576 bytes) [ 8.241264] TCP: Hash tables configured (established 524288 bind 65536) [ 8.241438] TCP: reno registered [ 8.241656] UDP hash table entries: 16384 (order: 7, 524288 bytes) [ 8.242075] UDP-Lite hash table entries: 16384 (order: 7, 524288 bytes) [ 8.242504] NET: Registered protocol family 1 [ 8.242740] RPC: Registered named UNIX socket transport module. [ 8.242881] RPC: Registered udp transport module. [ 8.243016] RPC: Registered tcp transport module. [ 8.243152] RPC: Registered tcp NFSv4.1 backchannel transport module. [ 8.243385] xen: registering gsi 21 triggering 0 polarity 1 [ 8.243401] xen: --> pirq=21 -> irq=21 (gsi=21) [ 8.243570] xen: registering gsi 23 triggering 0 polarity 1 [ 8.243576] xen: --> pirq=23 -> irq=23 (gsi=23) [ 8.243767] pciback 0000:0a:00.0: Boot video device [ 8.243820] PCI: CLS 64 bytes, default 64 [ 8.243866] Trying to unpack rootfs image as initramfs... [ 8.253804] Freeing initrd memory: 9908k freed [ 8.256693] microcode: CPU0 sig=0x106e5, pf=0x2, revision=0x4 [ 8.256848] microcode: CPU1 sig=0x106e5, pf=0x2, revision=0x4 [ 8.257058] microcode: Microcode Update Driver: v2.00 , Peter Oruba [ 8.257666] audit: initializing netlink socket (disabled) [ 8.257818] type=2000 audit(1347407764.232:1): initialized [ 8.276545] HugeTLB registered 2 MB page size, pre-allocated 0 pages [ 8.281167] VFS: Disk quotas dquot_6.5.2 [ 8.281421] Dquot-cache hash table entries: 512 (order 0, 4096 bytes) [ 8.283066] NFS: Registering the id_resolver key type [ 8.283211] Key type id_resolver registered [ 8.283357] Key type id_legacy registered [ 8.283567] SGI XFS with ACLs, security attributes, realtime, large block/inode numbers, no debug enabled [ 8.284744] msgmni has been set to 3129 [ 8.284989] SELinux: Registering netfilter hooks [ 8.286777] modprobe (799) used greatest stack depth: 5320 bytes left [ 8.294555] Block layer SCSI generic (bsg) driver version 0.4 loaded (major 251) [ 8.294780] io scheduler noop registered [ 8.294914] io scheduler deadline registered [ 8.295055] io scheduler cfq registered (default) [ 8.296316] pci_hotplug: PCI Hot Plug PCI Core version: 0.5 [ 8.296579] intel_idle: MWAIT substates: 0x1120 [ 8.296590] intel_idle: v0.4 model 0x1E [ 8.296592] intel_idle: lapic_timer_reliable_states 0x2 [ 8.296615] intel_idle: intel_idle yielding to none [ 8.296810] input: Sleep Button as /devices/LNXSYSTM:00/device:00/PNP0C0E:00/input/input0 [ 8.297037] ACPI: Sleep Button [SLPB] [ 8.297254] input: Power Button as /devices/LNXSYSTM:00/LNXPWRBN:00/input/input1 [ 8.297490] ACPI: Power Button [PWRF] [ 8.297881] ACPI: Requesting acpi_cpufreq [ 8.299639] modprobe (826) used greatest stack depth: 5304 bytes left [ 8.299791] Monitor-Mwait will be used to enter C-1 state [ 8.299846] Monitor-Mwait will be used to enter C-3 state [ 8.302929] Event-channel device installed. [ 8.303179] xen: registering gsi 17 triggering 0 polarity 1 [ 8.303195] xen: --> pirq=17 -> irq=17 (gsi=17) [ 8.324372] xen: registering gsi 16 triggering 0 polarity 1 [ 8.324377] Already setup the GSI :16 [ 8.346384] xen: registering gsi 17 triggering 0 polarity 1 [ 8.346388] Already setup the GSI :17 [ 8.368397] xen-pciback: backend is vpci [ 8.369297] Serial: 8250/16550 driver, 4 ports, IRQ sharing enabled [ 8.634432] serial8250: ttyS0 at I/O 0x3f8 (irq = 4) is a 16550A [ 8.899430] serial8250: ttyS1 at I/O 0x2f8 (irq = 3) is a 16550A [ 8.920793] 00:08: ttyS0 at I/O 0x3f8 (irq = 4) is a 16550A [ 8.941879] 00:09: ttyS1 at I/O 0x2f8 (irq = 3) is a 16550A [ 8.942386] hpet_acpi_add: no address or irqs in _CRS [ 8.942651] Non-volatile memory driver v1.3 [ 8.942770] Linux agpgart interface v0.103 [ 8.943179] [drm] Initialized drm 1.1.0 20060810 [ 8.946254] brd: module loaded [ 8.947815] loop: module loaded [ 8.948406] ahci 0000:00:1f.2: version 3.0 [ 8.948416] xen: registering gsi 18 triggering 0 polarity 1 [ 8.948418] Already setup the GSI :18 [ 8.959344] ahci 0000:00:1f.2: AHCI 0001.0300 32 slots 6 ports 3 Gbps 0x3f impl SATA mode [ 8.959545] ahci 0000:00:1f.2: flags: 64bit ncq sntf pm led clo pio slum part sxs apst [ 8.959736] ahci 0000:00:1f.2: setting latency timer to 64 [ 8.961433] scsi0 : ahci [ 8.961726] scsi1 : ahci [ 8.962008] scsi2 : ahci [ 8.962295] scsi3 : ahci [ 8.962576] scsi4 : ahci [ 8.962856] scsi5 : ahci [ 8.963098] ata1: SATA max UDMA/133 abar m2048@0xba720000 port 0xba720100 irq 18 [ 8.963297] ata2: SATA max UDMA/133 abar m2048@0xba720000 port 0xba720180 irq 18 [ 8.963484] ata3: SATA max UDMA/133 abar m2048@0xba720000 port 0xba720200 irq 18 [ 8.963669] ata4: SATA max UDMA/133 abar m2048@0xba720000 port 0xba720280 irq 18 [ 8.963853] ata5: SATA max UDMA/133 abar m2048@0xba720000 port 0xba720300 irq 18 [ 8.964038] ata6: SATA max UDMA/133 abar m2048@0xba720000 port 0xba720380 irq 18 [ 8.964820] e100: Intel(R) PRO/100 Network Driver, 3.5.24-k2-NAPI [ 8.964945] e100: Copyright(c) 1999-2006 Intel Corporation [ 8.965137] e1000: Intel(R) PRO/1000 Network Driver - version 7.3.21-k8-NAPI [ 8.965265] e1000: Copyright (c) 1999-2006 Intel Corporation. [ 8.965478] e1000e: Intel(R) PRO/1000 Network Driver - 2.0.0-k [ 8.965602] e1000e: Copyright(c) 1999 - 2012 Intel Corporation. [ 8.965738] xen: registering gsi 16 triggering 0 polarity 1 [ 8.965740] Already setup the GSI :16 [ 8.965862] e1000e 0000:00:19.0: setting latency timer to 64 [ 8.965950] e1000e 0000:00:19.0: Interrupt Throttling Rate (ints/sec) set to dynamic conservative mode [ 9.207156] e1000e 0000:00:19.0: eth0: (PCI Express:2.5GT/s:Width x1) 00:1e:67:0f:1a:e7 [ 9.207358] e1000e 0000:00:19.0: eth0: Intel(R) PRO/1000 Network Connection [ 9.207519] e1000e 0000:00:19.0: eth0: MAC: 9, PHY: 9, PBA No: 0310FF-0FF [ 9.207655] e1000e 0000:09:00.0: Disabling ASPM L0s L1 [ 9.207784] xen: registering gsi 16 triggering 0 polarity 1 [ 9.207786] Already setup the GSI :16 [ 9.208043] e1000e 0000:09:00.0: Interrupt Throttling Rate (ints/sec) set to dynamic conservative mode [ 9.268326] ata2: SATA link down (SStatus 0 SControl 300) [ 9.268488] ata1: SATA link down (SStatus 0 SControl 300) [ 9.269330] ata4: SATA link up 1.5 Gbps (SStatus 113 SControl 300) [ 9.269489] ata6: SATA link down (SStatus 0 SControl 300) [ 9.270324] ata5: SATA link down (SStatus 0 SControl 300) [ 9.271322] ata3: SATA link down (SStatus 0 SControl 300) [ 9.288740] ata4.00: ATA-7: HDS724040KLSA80, KFAOA46A, max UDMA/133 [ 9.288880] ata4.00: 781422768 sectors, multi 0: LBA48 [ 9.293215] ata4.00: configured for UDMA/133 [ 9.293467] scsi 3:0:0:0: Direct-Access ATA HDS724040KLSA80 KFAO PQ: 0 ANSI: 5 [ 9.293938] sd 3:0:0:0: [sda] 781422768 512-byte logical blocks: (400 GB/372 GiB) [ 9.294020] sd 3:0:0:0: Attached scsi generic sg0 type 0 [ 9.294384] sd 3:0:0:0: [sda] Write Protect is off [ 9.294506] sd 3:0:0:0: [sda] Mode Sense: 00 3a 00 00 [ 9.294549] sd 3:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA [ 9.310067] sda: sda1 sda2 [ 9.310627] sd 3:0:0:0: [sda] Attached SCSI disk [ 9.313819] e1000e 0000:09:00.0: eth1: (PCI Express:2.5GT/s:Width x1) 00:1e:67:0f:1a:e6 [ 9.314009] e1000e 0000:09:00.0: eth1: Intel(R) PRO/1000 Network Connection [ 9.314219] e1000e 0000:09:00.0: eth1: MAC: 3, PHY: 8, PBA No: 1010FF-0FF [ 9.314431] igb: Intel(R) Gigabit Ethernet Network Driver - version 4.0.1-k [ 9.314558] igb: Copyright (c) 2007-2012 Intel Corporation. [ 9.314697] xen: registering gsi 16 triggering 0 polarity 1 [ 9.314699] Already setup the GSI :16 [ 9.476748] igb 0000:06:00.0: added PHC on eth2 [ 9.476869] igb 0000:06:00.0: Intel(R) Gigabit Ethernet Network Connection [ 9.476995] igb 0000:06:00.0: eth2: (PCIe:2.5Gb/s:Width x4) 90:e2:ba:00:9f:c4 [ 9.477202] igb 0000:06:00.0: eth2: PBA No: E43709-006 [ 9.477330] igb 0000:06:00.0: Using legacy interrupts. 1 rx queue(s), 1 tx queue(s) [ 9.477527] xen: registering gsi 17 triggering 0 polarity 1 [ 9.477530] Already setup the GSI :17 [ 9.639745] igb 0000:06:00.1: added PHC on eth3 [ 9.639865] igb 0000:06:00.1: Intel(R) Gigabit Ethernet Network Connection [ 9.639992] igb 0000:06:00.1: eth3: (PCIe:2.5Gb/s:Width x4) 90:e2:ba:00:9f:c5 [ 9.640199] igb 0000:06:00.1: eth3: PBA No: E43709-006 [ 9.640326] igb 0000:06:00.1: Using legacy interrupts. 1 rx queue(s), 1 tx queue(s) [ 9.640584] igbvf: Intel(R) Gigabit Virtual Function Network Driver - version 2.0.1-k [ 9.640773] igbvf: Copyright (c) 2009 - 2012 Intel Corporation. [ 9.640965] ixgbe: Intel(R) 10 Gigabit PCI Express Network Driver - version 3.9.15-k [ 9.641153] ixgbe: Copyright (c) 1999-2012 Intel Corporation. [ 9.641364] ixgb: Intel(R) PRO/10GbE Network Driver - version 1.0.135-k2-NAPI [ 9.641492] ixgb: Copyright (c) 1999-2008 Intel Corporation. [ 9.641688] Initialising Xen virtual ethernet driver. [ 9.642096] ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver [ 9.642222] ehci_hcd: block sizes: qh 104 qtd 96 itd 192 sitd 96 [ 9.642240] xen: registering gsi 21 triggering 0 polarity 1 [ 9.642243] Already setup the GSI :21 [ 9.642385] ehci_hcd 0000:00:1a.0: setting latency timer to 64 [ 9.642390] ehci_hcd 0000:00:1a.0: EHCI Host Controller [ 9.642588] ehci_hcd 0000:00:1a.0: new USB bus registered, assigned bus number 1 [ 9.642780] ehci_hcd 0000:00:1a.0: reset hcs_params 0x200002 dbg=2 cc=0 pcc=0 ordered !ppc ports=2 [ 9.642784] ehci_hcd 0000:00:1a.0: reset hcc_params 36881 caching frame 1024 64 bit addr [ 9.642811] ehci_hcd 0000:00:1a.0: support lpm [ 9.642818] ehci_hcd 0000:00:1a.0: reset command 0080012 (park)=0 ithresh=8 Periodic period=1024 Reset HALT [ 9.646736] ehci_hcd 0000:00:1a.0: debug port 2 [ 9.646864] ehci_hcd 0000:00:1a.0: cache line size of 64 is not supported [ 9.646866] ehci_hcd 0000:00:1a.0: supports USB remote wakeup [ 9.646883] ehci_hcd 0000:00:1a.0: irq 21, io mem 0xba722000 [ 9.647009] ehci_hcd 0000:00:1a.0: init command 0010001 (park)=0 ithresh=1 period=1024 RUN [ 9.652306] ehci_hcd 0000:00:1a.0: USB 2.0 started, EHCI 1.00 [ 9.652475] usb usb1: default language 0x0409 [ 9.652480] usb usb1: udev 1, busnum 1, minor = 0 [ 9.652483] usb usb1: New USB device found, idVendor=1d6b, idProduct=0002 [ 9.652609] usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1 [ 9.652793] usb usb1: Product: EHCI Host Controller [ 9.652912] usb usb1: Manufacturer: Linux 3.6.0-rc4+ ehci_hcd [ 9.653034] usb usb1: SerialNumber: 0000:00:1a.0 [ 9.653253] usb usb1: usb_probe_device [ 9.653256] usb usb1: configuration #1 chosen from 1 choice [ 9.653263] usb usb1: adding 1-0:1.0 (config #1, interface 0) [ 9.653337] hub 1-0:1.0: usb_probe_interface [ 9.653339] hub 1-0:1.0: usb_probe_interface - got id [ 9.653341] hub 1-0:1.0: USB hub found [ 9.653461] hub 1-0:1.0: 2 ports detected [ 9.653579] hub 1-0:1.0: standalone hub [ 9.653581] hub 1-0:1.0: no power switching (usb 1.0) [ 9.653582] hub 1-0:1.0: individual port over-current protection [ 9.653584] hub 1-0:1.0: power on to power good time: 20ms [ 9.653587] hub 1-0:1.0: local power source is good [ 9.653589] hub 1-0:1.0: trying to enable port power on non-switchable hub [ 9.653643] xen: registering gsi 23 triggering 0 polarity 1 [ 9.653646] Already setup the GSI :23 [ 9.653779] ehci_hcd 0000:00:1d.0: setting latency timer to 64 [ 9.653783] ehci_hcd 0000:00:1d.0: EHCI Host Controller [ 9.653984] ehci_hcd 0000:00:1d.0: new USB bus registered, assigned bus number 2 [ 9.655049] ehci_hcd 0000:00:1d.0: reset hcs_params 0x200002 dbg=2 cc=0 pcc=0 ordered !ppc ports=2 [ 9.655052] ehci_hcd 0000:00:1d.0: reset hcc_params 36881 caching frame 1024 64 bit addr [ 9.655079] ehci_hcd 0000:00:1d.0: support lpm [ 9.655086] ehci_hcd 0000:00:1d.0: reset command 0080012 (park)=0 ithresh=8 Periodic period=1024 Reset HALT [ 9.658994] ehci_hcd 0000:00:1d.0: debug port 2 [ 9.659122] ehci_hcd 0000:00:1d.0: cache line size of 64 is not supported [ 9.659124] ehci_hcd 0000:00:1d.0: supports USB remote wakeup [ 9.659142] ehci_hcd 0000:00:1d.0: irq 23, io mem 0xba721000 [ 9.659267] ehci_hcd 0000:00:1d.0: init command 0010001 (park)=0 ithresh=1 period=1024 RUN [ 9.664307] ehci_hcd 0000:00:1d.0: USB 2.0 started, EHCI 1.00 [ 9.664473] usb usb2: default language 0x0409 [ 9.664478] usb usb2: udev 1, busnum 2, minor = 128 [ 9.664480] usb usb2: New USB device found, idVendor=1d6b, idProduct=0002 [ 9.664606] usb usb2: New USB device strings: Mfr=3, Product=2, SerialNumber=1 [ 9.664790] usb usb2: Product: EHCI Host Controller [ 9.664909] usb usb2: Manufacturer: Linux 3.6.0-rc4+ ehci_hcd [ 9.665031] usb usb2: SerialNumber: 0000:00:1d.0 [ 9.665245] usb usb2: usb_probe_device [ 9.665247] usb usb2: configuration #1 chosen from 1 choice [ 9.665253] usb usb2: adding 2-0:1.0 (config #1, interface 0) [ 9.665330] hub 2-0:1.0: usb_probe_interface [ 9.665332] hub 2-0:1.0: usb_probe_interface - got id [ 9.665334] hub 2-0:1.0: USB hub found [ 9.665453] hub 2-0:1.0: 2 ports detected [ 9.665571] hub 2-0:1.0: standalone hub [ 9.665572] hub 2-0:1.0: no power switching (usb 1.0) [ 9.665574] hub 2-0:1.0: individual port over-current protection [ 9.665575] hub 2-0:1.0: power on to power good time: 20ms [ 9.665578] hub 2-0:1.0: local power source is good [ 9.665580] hub 2-0:1.0: trying to enable port power on non-switchable hub [ 9.665692] ohci_hcd: USB 1.1 'Open' Host Controller (OHCI) Driver [ 9.665817] ohci_hcd: block sizes: ed 80 td 96 [ 9.665891] uhci_hcd: USB Universal Host Controller Interface driver [ 9.666161] usbcore: registered new interface driver usblp [ 9.666293] Initializing USB Mass Storage driver... [ 9.666490] usbcore: registered new interface driver usb-storage [ 9.666615] USB Mass Storage support registered. [ 9.666808] usbcore: registered new interface driver libusual [ 9.667199] i8042: PNP: No PS/2 controller found. Probing ports directly. [ 9.668216] i8042: No controller found [ 9.668403] mousedev: PS/2 mouse device common for all mice [ 9.668852] rtc_cmos 00:03: RTC can wake from S4 [ 9.669150] rtc_cmos 00:03: rtc core: registered rtc_cmos as rtc0 [ 9.669324] rtc0: alarms up to one month, y3k, 114 bytes nvram [ 9.669527] xen: registering gsi 18 triggering 0 polarity 1 [ 9.669529] Already setup the GSI :18 [ 9.669934] device-mapper: ioctl: 4.23.0-ioctl (2012-07-25) initialised: dm-devel@redhat.com [ 9.670209] EFI Variables Facility v0.08 2004-May-17 [ 9.671662] usbcore: registered new interface driver usbhid [ 9.671786] usbhid: USB HID core driver [ 9.674147] Netfilter messages via NETLINK v0.30. [ 9.674277] nf_conntrack version 0.5.0 (16384 buckets, 65536 max) [ 9.674636] ctnetlink v0.93: registering with nfnetlink. [ 9.674876] ip_tables: (C) 2000-2006 Netfilter Core Team [ 9.675020] TCP: cubic registered [ 9.675133] Initializing XFRM netlink socket [ 9.675252] NET: Registered protocol family 17 [ 9.675412] Key type dns_resolver registered [ 9.676059] PM: Hibernation image not present or could not be loaded. [ 9.676069] registered taskstats version 1 [ 9.676823] Magic number: 12:177:959 [ 9.677007] console [netcon0] enabled [ 9.677122] netconsole: network logging started [ 9.677353] ALSA device list: [ 9.677467] No soundcards found. [ 9.677783] Freeing unused kernel memory: 728k freed [ 9.678013] Write protecting the kernel read-only data: 12288k [ 9.681039] Freeing unused kernel memory: 4k freed [ 9.681601] Freeing unused kernel memory: 1628k freed [ 9.717761] dracut: dracut-006-6.fc14 [ 9.737240] udev[1121]: starting version 161 [ 9.753319] ehci_hcd 0000:00:1a.0: GetStatus port:1 status 001803 0 ACK POWER sig=j CSC CONNECT [ 9.753325] hub 1-0:1.0: port 1: status 0501 change 0001 [ 9.765332] ehci_hcd 0000:00:1d.0: GetStatus port:1 status 001803 0 ACK POWER sig=j CSC CONNECT [ 9.765338] hub 2-0:1.0: port 1: status 0501 change 0001 [ 9.783489] dracut: Starting plymouth daemon [ 9.853421] hub 1-0:1.0: state 7 ports 2 chg 0002 evt 0000 [ 9.853431] hub 1-0:1.0: port 1, status 0501, change 0000, 480 Mb/s [ 9.904532] ehci_hcd 0000:00:1a.0: port 1 reset complete, port enabled [ 9.904539] ehci_hcd 0000:00:1a.0: GetStatus port:1 status 001005 0 ACK POWER sig=se0 PE CONNECT [ 9.955314] usb 1-1: new high-speed USB device number 2 using ehci_hcd [ 9.993881] blkid (1519) used greatest stack depth: 4976 bytes left [ 10.006529] ehci_hcd 0000:00:1a.0: port 1 reset complete, port enabled [ 10.006535] ehci_hcd 0000:00:1a.0: GetStatus port:1 status 001005 0 ACK POWER sig=se0 PE CONNECT [ 10.069433] ehci_hcd 0000:00:1a.0: set dev address 2 for port 1 [ 10.069441] ehci_hcd 0000:00:1a.0: LPM: no device attached [ 10.069678] usb 1-1: udev 2, busnum 1, minor = 1 [ 10.069683] usb 1-1: New USB device found, idVendor=8087, idProduct=0020 [ 10.069826] usb 1-1: New USB device strings: Mfr=0, Product=0, SerialNumber=0 [ 10.070042] usb 1-1: usb_probe_device [ 10.070046] usb 1-1: configuration #1 chosen from 1 choice [ 10.070198] usb 1-1: adding 1-1:1.0 (config #1, interface 0) [ 10.070309] hub 1-1:1.0: usb_probe_interface [ 10.070312] hub 1-1:1.0: usb_probe_interface - got id [ 10.070314] hub 1-1:1.0: USB hub found [ 10.070555] hub 1-1:1.0: 6 ports detected [ 10.070686] hub 1-1:1.0: standalone hub [ 10.070687] hub 1-1:1.0: individual port power switching [ 10.070689] hub 1-1:1.0: individual port over-current protection [ 10.070690] hub 1-1:1.0: Single TT [ 10.070692] hub 1-1:1.0: TT requires at most 8 FS bit times (666 ns) [ 10.070693] hub 1-1:1.0: Port indicators are supported [ 10.070695] hub 1-1:1.0: power on to power good time: 100ms [ 10.070922] hub 1-1:1.0: local power source is good [ 10.070926] hub 1-1:1.0: enabling power on all ports [ 10.071742] hub 2-0:1.0: state 7 ports 2 chg 0002 evt 0000 [ 10.071756] hub 2-0:1.0: port 1, status 0501, change 0000, 480 Mb/s [ 10.122528] ehci_hcd 0000:00:1d.0: port 1 reset complete, port enabled [ 10.122535] ehci_hcd 0000:00:1d.0: GetStatus port:1 status 001005 0 ACK POWER sig=se0 PE CONNECT [ 10.126354] dracut: Scanning devices sda2 for LVM logical volumes vg_xenserver01/LV_ROOT vg_xenserver01/LV_SWAP [ 10.139504] dracut: inactive '/dev/vg_xenserver01/LV_ROOT' [351.56 GiB] inherit [ 10.139862] dracut: inactive '/dev/vg_xenserver01/LV_SWAP' [20.53 GiB] inherit [ 10.172176] usb 1-1: link qh256-0001/ffff880002615c80 start 1 [1/0 us] [ 10.173315] usb 2-1: new high-speed USB device number 2 using ehci_hcd [ 10.188415] dracut: /dev/mapper/vg_xenserver01-LV_ROOT not set up by udev: Falling back to direct node creation. [ 10.188936] dracut: /dev/mapper/vg_xenserver01-LV_SWAP not set up by udev: Falling back to direct node creation. [ 10.189425] dracut: The link /dev/vg_xenserver01/LV_ROOT should had been created by udev but it was not found. Falling back to direct link creation. [ 10.189926] dracut: The link /dev/vg_xenserver01/LV_SWAP should had been created by udev but it was not found. Falling back to direct link creation. [ 10.224527] ehci_hcd 0000:00:1d.0: port 1 reset complete, port enabled [ 10.224533] ehci_hcd 0000:00:1d.0: GetStatus port:1 status 001005 0 ACK POWER sig=se0 PE CONNECT [ 10.287440] ehci_hcd 0000:00:1d.0: set dev address 2 for port 1 [ 10.287446] ehci_hcd 0000:00:1d.0: LPM: no device attached [ 10.287691] usb 2-1: udev 2, busnum 2, minor = 129 [ 10.287695] usb 2-1: New USB device found, idVendor=8087, idProduct=0020 [ 10.287833] usb 2-1: New USB device strings: Mfr=0, Product=0, SerialNumber=0 [ 10.289159] usb 2-1: usb_probe_device [ 10.289164] usb 2-1: configuration #1 chosen from 1 choice [ 10.289325] usb 2-1: adding 2-1:1.0 (config #1, interface 0) [ 10.291004] hub 2-1:1.0: usb_probe_interface [ 10.291008] hub 2-1:1.0: usb_probe_interface - got id [ 10.291011] hub 2-1:1.0: USB hub found [ 10.291189] hub 2-1:1.0: 6 ports detected [ 10.291330] hub 2-1:1.0: standalone hub [ 10.291332] hub 2-1:1.0: individual port power switching [ 10.291334] hub 2-1:1.0: individual port over-current protection [ 10.291336] hub 2-1:1.0: Single TT [ 10.291337] hub 2-1:1.0: TT requires at most 8 FS bit times (666 ns) [ 10.291339] hub 2-1:1.0: Port indicators are supported [ 10.291340] hub 2-1:1.0: power on to power good time: 100ms [ 10.291563] hub 2-1:1.0: local power source is good [ 10.291568] hub 2-1:1.0: enabling power on all ports [ 10.292384] hub 1-1:1.0: state 7 ports 6 chg 0000 evt 0000 [ 10.392563] hub 2-1:1.0: port 2: status 0101 change 0001 [ 10.465255] EXT4-fs (dm-0): INFO: recovery required on readonly filesystem [ 10.465393] EXT4-fs (dm-0): write access will be enabled during recovery [ 10.492324] usb 2-1: link qh256-0001/ffff880002615e00 start 1 [1/0 us] [ 10.492362] hub 2-1:1.0: state 7 ports 6 chg 0004 evt 0000 [ 10.492449] hub 2-1:1.0: port 2, status 0101, change 0000, 12 Mb/s [ 10.503436] hub 2-1:1.0: port 2 not reset yet, waiting 10ms [ 10.565442] usb 2-1.2: new full-speed USB device number 3 using ehci_hcd [ 10.576444] hub 2-1:1.0: port 2 not reset yet, waiting 10ms [ 10.651061] usb 2-1.2: skipped 1 descriptor after interface [ 10.651067] usb 2-1.2: skipped 1 descriptor after interface [ 10.651184] usb 2-1.2: default language 0x0409 [ 10.651809] usb 2-1.2: udev 3, busnum 2, minor = 130 [ 10.651813] usb 2-1.2: New USB device found, idVendor=046b, idProduct=ff10 [ 10.651955] usb 2-1.2: New USB device strings: Mfr=1, Product=2, SerialNumber=3 [ 10.652140] usb 2-1.2: Product: Virtual Keyboard and Mouse [ 10.652261] usb 2-1.2: Manufacturer: American Megatrends Inc. [ 10.652389] usb 2-1.2: SerialNumber: serial [ 10.652627] usb 2-1.2: usb_probe_device [ 10.652631] usb 2-1.2: configuration #1 chosen from 1 choice [ 10.652996] usb 2-1.2: adding 2-1.2:1.0 (config #1, interface 0) [ 10.653320] usbhid 2-1.2:1.0: usb_probe_interface [ 10.653324] usbhid 2-1.2:1.0: usb_probe_interface - got id [ 10.654370] input: American Megatrends Inc. Virtual Keyboard and Mouse as /devices/pci0000:00/0000:00:1d.0/usb2/2-1/2-1.2/2-1.2:1.0/input/input2 [ 10.654605] usb 2-1.2: link qh8-0601/ffff88005f597480 start 2 [1/2 us] [ 10.654782] hid-generic 0003:046B:FF10.0001: input,hidraw0: USB HID v1.10 Keyboard [American Megatrends Inc. Virtual Keyboard and Mouse] on usb-0000:00:1d.0-1.2/input0 [ 10.655095] usb 2-1.2: adding 2-1.2:1.1 (config #1, interface 1) [ 10.655431] usbhid 2-1.2:1.1: usb_probe_interface [ 10.655433] usbhid 2-1.2:1.1: usb_probe_interface - got id [ 10.656222] input: American Megatrends Inc. Virtual Keyboard and Mouse as /devices/pci0000:00/0000:00:1d.0/usb2/2-1/2-1.2/2-1.2:1.1/input/input3 [ 10.656629] hid-generic 0003:046B:FF10.0002: input,hidraw1: USB HID v1.10 Mouse [American Megatrends Inc. Virtual Keyboard and Mouse] on usb-0000:00:1d.0-1.2/input1 [ 10.972958] EXT4-fs (dm-0): recovery complete [ 10.980394] EXT4-fs (dm-0): mounted filesystem with ordered data mode. Opts: (null) [ 10.981003] mount (1853) used greatest stack depth: 4152 bytes left [ 11.028675] dracut: Mounted root filesystem /dev/mapper/vg_xenserver01-LV_ROOT [ 11.107399] dracut: Loading SELinux policy [ 11.338949] SELinux: Disabled at runtime. [ 11.339092] SELinux: Unregistering netfilter hooks [ 11.370311] type=1404 audit(1347407767.345:2): selinux=0 auid=4294967295 ses=4294967295 [ 11.417676] dracut: /sbin/load_policy: Can't load policy: No such file or directory [ 11.477195] dracut: Switching root [ 12.550782] udev[1905]: starting version 161 [ 12.676942] megasas: 00.00.06.15-rc1 Mon. Mar. 19 17:00:00 PDT 2012 [ 12.677116] megasas: 0x1000:0x0079:0x8086:0x9264: bus 5:slot 0:func 0 [ 12.677334] xen: registering gsi 16 triggering 0 polarity 1 [ 12.677340] Already setup the GSI :16 [ 12.684527] megasas: FW now in Ready state [ 12.707309] megasas_init_mfi: fw_support_ieee=0 [ 12.707384] megasas: INIT adapter done [ 12.771541] scsi6 : LSI SAS based MegaRAID driver [ 12.773245] scsi 6:0:1:0: Direct-Access ATA WDC WD1002FBYS-1 0C06 PQ: 0 ANSI: 5 [ 12.775513] scsi 6:0:3:0: Direct-Access ATA WDC WD1002FBYS-1 0C06 PQ: 0 ANSI: 5 [ 12.805736] scsi 6:2:0:0: Direct-Access INTEL RT3WB080 2.13 PQ: 0 ANSI: 5 [ 12.806076] sd 6:2:0:0: Attached scsi generic sg1 type 0 [ 12.806437] sd 6:2:0:0: [sdb] 1951170560 512-byte logical blocks: (998 GB/930 GiB) [ 12.806868] sd 6:2:0:0: [sdb] Write Protect is off [ 12.807008] sd 6:2:0:0: [sdb] Mode Sense: 1f 00 00 08 [ 12.807199] sd 6:2:0:0: [sdb] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA [ 12.824596] sdb: sdb1 sdb2 [ 12.825369] sd 6:2:0:0: [sdb] Attached SCSI disk [ 13.829099] ip (2154) used greatest stack depth: 3784 bytes left [ 19.761112] EXT4-fs (dm-0): re-mounted. Opts: (null) [ 19.978154] EXT4-fs (sda1): mounting ext2 file system using the ext4 subsystem [ 19.979455] EXT4-fs (sda1): mounted filesystem without journal. Opts: (null) [ 20.228555] Adding 21528572k swap on /dev/mapper/vg_xenserver01-LV_SWAP. Priority:-1 extents:1 across:21528572k Finally xl info: host : xen-server01.ark-net.org release : 3.6.0-rc4+ version : #2 SMP Mon Sep 10 14:42:44 EDT 2012 machine : x86_64 nr_cpus : 8 max_cpu_id : 7 nr_nodes : 1 cores_per_socket : 4 threads_per_core : 2 cpu_mhz : 2533 hw_caps : bfebfbff:28100800:00000000:00003b40:0098e3fd:00000000:00000001:00000000 virt_caps : hvm hvm_directio total_memory : 32731 free_memory : 30255 sharing_freed_memory : 0 sharing_used_memory : 0 free_cpus : 0 xen_major : 4 xen_minor : 3 xen_extra : -unstable xen_caps : xen-3.0-x86_64 xen-3.0-x86_32p hvm-3.0-x86_32 hvm-3.0-x86_32p hvm-3.0-x86_64 xen_scheduler : credit xen_pagesize : 4096 platform_params : virt_start=0xffff800000000000 xen_changeset : unavailable xen_commandline : dom0_mem=2G iommu=pv msi=1 dom0_max_vcpus=2 dom0_vcpus_pin tmem loglvl=info conring_size=134217728 console_to_ring cc_compiler : gcc (GCC) 4.5.1 20100924 (Red Hat 4.5.1-4) cc_compile_by : root cc_compile_domain : ark-net.org cc_compile_date : Mon Sep 10 19:53:51 EDT 2012 xend_config_format : 4 Maybe this helps. Mike _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Wed Sep 12 00:26:31 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Wed, 12 Sep 2012 00:26:31 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TBalU-0006iN-GB; Wed, 12 Sep 2012 00:25:12 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TBalR-0006iF-8W for xen-users@lists.xen.org; Wed, 12 Sep 2012 00:25:10 +0000 Received: from [85.158.143.99:27816] by server-3.bemta-4.messagelabs.com id 34/F3-08232-466DF405; Wed, 12 Sep 2012 00:25:08 +0000 X-Env-Sender: mike.a.collins@ark-net.org X-Msg-Ref: server-2.tower-216.messagelabs.com!1347409503!24508608!1 X-Originating-IP: [216.33.127.80] X-SpamReason: No, hits=0.5 required=7.0 tests=BODY_RANDOM_LONG X-StarScan-Received: X-StarScan-Version: 6.6.1.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 14383 invoked from network); 12 Sep 2012 00:25:03 -0000 Received: from mta11.charter.net (HELO mta11.charter.net) (216.33.127.80) by server-2.tower-216.messagelabs.com with SMTP; 12 Sep 2012 00:25:03 -0000 Received: from imp11 ([10.20.200.11]) by mta11.charter.net (InterMail vM.8.01.05.02 201-2260-151-103-20110920) with ESMTP id <20120912002502.YBYZ10966.mta11.charter.net@imp11> for ; Tue, 11 Sep 2012 20:25:02 -0400 Received: from mail.ark-net.org ([75.138.215.251]) by imp11 with smtp.charter.net id y0R21j00U5S18aK050R2LH; Tue, 11 Sep 2012 20:25:02 -0400 X-Authority-Analysis: v=1.1 cv=Mv9Cy8NsQItTEAHnXr6fCNbI23lcrkmyMeqLv9HU3yU= c=1 sm=1 a=0bCt-fb661UA:10 a=Q-lh5XB8xgUA:10 a=VCxxn1A5iYMA:10 a=NqYyV4q_xg0A:10 a=wPDyFdB5xvgA:10 a=IkcTkHD0fZMA:10 a=4A50YBgeEUJTzIKlCdeDOQ==:17 a=-g-7CrJqAAAA:8 a=pSDxxfrZAAAA:8 a=20KFwNOVAAAA:8 a=tJxwftSMFhSheoO_9GgA:9 a=QEXdDO2ut3YA:10 a=Elr449XH5AsA:10 a=jEp0ucaQiEUA:10 a=-nm3JPuCHhnj7VM3:21 a=8isSTCofgk37nZwm:21 a=4A50YBgeEUJTzIKlCdeDOQ==:117 Received: from localhost (unknown [127.0.0.1]) by mail.ark-net.org (Postfix) with ESMTP id 974A0203DF for ; Wed, 12 Sep 2012 00:25:19 +0000 (UTC) X-Virus-Scanned: amavisd-new at ark-net.org Received: from mail.ark-net.org ([127.0.0.1]) by localhost (mail.ark-net.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id zlYHncT+ZNMW for ; Tue, 11 Sep 2012 20:24:37 -0400 (EDT) Received: from 192.168.1.12 (unknown [192.168.1.12]) by mail.ark-net.org (Postfix) with ESMTP id C168E203D1 for ; Tue, 11 Sep 2012 20:24:37 -0400 (EDT) MIME-Version: 1.0 Date: Tue, 11 Sep 2012 20:40:34 -0400 From: "Michael A. Collins" To: Mail-Reply-To: In-Reply-To: <1347374568.7226.12.camel@wotan2> References: <504D17ED.9030105@yahoo.co.uk> <1347374568.7226.12.camel@wotan2> Message-ID: <6c6a19bf07700c9915c0c0facef6df21@192.168.1.11> X-Sender: mike.a.collins@ark-net.org User-Agent: Roundcube Webmail/0.6-beta Subject: Re: [Xen-users] Stall on CPU X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list Reply-To: mike.a.collins@ark-net.org List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset="us-ascii"; Format="flowed" Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org On 11.09.2012 10:42, Stephan Seitz wrote: > Hi, > > I've also seen that "rcu sched detected stalls on CPU x", but on > dom0, not domU. > The dom0 which had this error (leading to a complete system stop) is > running xen 4.1.3 > and vanilla 3.5.2 as dom0 kernel. > I know, I should go with the xenified kernels, but I'm currently > evaluating tmem features on recent > kernels. > > Another machine which hit that "rcu sched" was a baremetal 3.1.1 > acting as scst target. > > I've got the feeling the error can be triggered by heavy I/O, but to > be honest, I don't have > any glue what to do against it. > > Cheers, > > - Stephan > I am having the same issue on a newly updated dom0. I have stack traces below, but it seems to be only when I reboot or shutdown the dom0. It stalls for 15 mins or so and then finally gives up and finishes. The stack trace looks like it has something to do with a timer issue and I saw some posts awhile ago about setting the timesource=jiffies on the command-line, but I have not tried it. Here's the stack trace: Sep 11 19:37:28 xen-server01 kernel: [76610.242073] INFO: rcu_sched self-detected stall on CPU { 0} (t=299981 jiffies) Sep 11 19:37:28 xen-server01 kernel: [76610.242281] Pid: 0, comm: swapper/0 Tainted: G O 3.6.0-rc4+ #2 Sep 11 19:37:28 xen-server01 kernel: [76610.242385] Call Trace: Sep 11 19:37:28 xen-server01 kernel: [76610.242474] [] rcu_check_callbacks+0x4d2/0x640 Sep 11 19:37:28 xen-server01 kernel: [76610.242594] [] ? tick_nohz_handler+0xf0/0xf0 Sep 11 19:37:28 xen-server01 kernel: [76610.242698] [] update_process_times+0x43/0x80 Sep 11 19:37:28 xen-server01 kernel: [76610.242799] [] tick_sched_timer+0x67/0xd0 Sep 11 19:37:28 xen-server01 kernel: [76610.242900] [] __run_hrtimer+0x7f/0x1d0 Sep 11 19:37:28 xen-server01 kernel: [76610.243008] [] ? xen_clocksource_get_cycles+0x9/0x10 Sep 11 19:37:28 xen-server01 kernel: [76610.243111] [] ? ktime_get_update_offsets+0x47/0xd0 Sep 11 19:37:28 xen-server01 kernel: [76610.243214] [] hrtimer_interrupt+0xfe/0x250 Sep 11 19:37:28 xen-server01 kernel: [76610.243315] [] xen_timer_interrupt+0x2d/0x1b0 Sep 11 19:37:28 xen-server01 kernel: [76610.243417] [] ? xen_hypercall_sched_op+0xa/0x20 Sep 11 19:37:28 xen-server01 kernel: [76610.243520] [] ? radix_tree_lookup+0xb/0x10 Sep 11 19:37:28 xen-server01 kernel: [76610.243621] [] ? irq_to_desc+0x12/0x20 Sep 11 19:37:28 xen-server01 kernel: [76610.243720] [] ? irq_get_irq_data+0x9/0x10 Sep 11 19:37:28 xen-server01 kernel: [76610.243821] [] handle_irq_event_percpu+0x5d/0x200 Sep 11 19:37:28 xen-server01 kernel: [76610.243924] [] handle_percpu_irq+0x43/0x60 Sep 11 19:37:28 xen-server01 kernel: [76610.244026] [] __xen_evtchn_do_upcall+0x1a6/0x260 Sep 11 19:37:28 xen-server01 kernel: [76610.244129] [] xen_evtchn_do_upcall+0x2a/0x40 Sep 11 19:37:28 xen-server01 kernel: [76610.244231] [] xen_do_hypervisor_callback+0x1e/0x30 Sep 11 19:37:28 xen-server01 kernel: [76610.244334] [] ? xen_hypercall_sched_op+0xa/0x20 Sep 11 19:37:28 xen-server01 kernel: [76610.244448] [] ? xen_hypercall_sched_op+0xa/0x20 Sep 11 19:37:28 xen-server01 kernel: [76610.244551] [] ? xen_safe_halt+0x10/0x20 Sep 11 19:37:28 xen-server01 kernel: [76610.244651] [] ? default_idle+0x58/0x1b0 Sep 11 19:37:28 xen-server01 kernel: [76610.244751] [] ? cpu_idle+0x8f/0xc0 Sep 11 19:37:28 xen-server01 kernel: [76610.244851] [] ? rest_init+0x6d/0x80 Sep 11 19:37:28 xen-server01 kernel: [76610.244951] [] ? start_kernel+0x341/0x34e Sep 11 19:37:28 xen-server01 kernel: [76610.245051] [] ? repair_env_string+0x59/0x59 Sep 11 19:37:28 xen-server01 kernel: [76610.245154] [] ? x86_64_start_reservations+0x132/0x137 Sep 11 19:37:28 xen-server01 kernel: [76610.245260] [] ? xen_start_kernel+0x626/0x62d Here's some more info: (XEN) ACPI: INT_SRC_OVR (bus 0 bus_irq 0 global_irq 2 dfl dfl) (XEN) ACPI: INT_SRC_OVR (bus 0 bus_irq 9 global_irq 9 high level) (XEN) Enabling APIC mode: Flat. Using 1 I/O APICs (XEN) ACPI: HPET id: 0x8086a801 base: 0xfed00000 (XEN) Xen ERST support is initialized. (XEN) Using ACPI (MADT) for SMP configuration information (XEN) SMP: Allowing 8 CPUs (0 hotplug CPUs) (XEN) IRQ limits: 24 GSI, 1528 MSI/MSI-X (XEN) Using scheduler: SMP Credit Scheduler (credit) (XEN) Detected 2533.348 MHz processor. (XEN) Initing memory sharing. (XEN) mce_intel.c:1239: MCA Capability: BCAST 1 SER 0 CMCI 1 firstbank 0 extended MCE MSR 0 (XEN) Intel machine check reporting enabled (XEN) PCI: MCFG configuration 0: base a0000000 segment 0000 buses 00 - ff (XEN) PCI: MCFG area at a0000000 reserved in E820 (XEN) PCI: Using MCFG for segment 0000 bus 00-ff (XEN) Intel VT-d supported page sizes: 4kB. (XEN) Intel VT-d Snoop Control enabled. (XEN) Intel VT-d Dom0 DMA Passthrough not enabled. (XEN) Intel VT-d Queued Invalidation enabled. (XEN) Intel VT-d Interrupt Remapping not enabled. (XEN) Intel VT-d Shared EPT tables not enabled. (XEN) I/O virtualisation enabled (XEN) - Dom0 mode: Relaxed (XEN) ENABLING IO-APIC IRQs (XEN) -> Using new ACK method (XEN) ..TIMER: vector=0xF0 apic1=0 pin1=2 apic2=-1 pin2=-1 (XEN) Platform timer is 14.318MHz HPET (XEN) Allocated console ring of 32 KiB. (XEN) VMX: Supported advanced features: (XEN) - APIC MMIO access virtualisation (XEN) - APIC TPR shadow (XEN) - Extended Page Tables (EPT) (XEN) - Virtual-Processor Identifiers (VPID) (XEN) - Virtual NMI (XEN) - MSR direct-access bitmap (XEN) HVM: ASIDs enabled. (XEN) HVM: VMX enabled (XEN) HVM: Hardware Assisted Paging (HAP) detected (XEN) HVM: HAP page sizes: 4kB, 2MB (XEN) Brought up 8 CPUs (XEN) tmem: initialized comp=0 dedup=0 tze=0 global-lock=0 (XEN) HPET: 8 timers (8 will be used for broadcast) (XEN) ACPI sleep modes: S3 (XEN) mcheck_poll: Machine check polling timer started. (XEN) *** LOADING DOMAIN 0 *** (XEN) elf_parse_binary: phdr: paddr=0x1000000 memsz=0xa69000 (XEN) elf_parse_binary: phdr: paddr=0x1c00000 memsz=0xc30e8 (XEN) elf_parse_binary: phdr: paddr=0x1cc4000 memsz=0x144c0 (XEN) elf_parse_binary: phdr: paddr=0x1cd9000 memsz=0x5c2000 (XEN) elf_parse_binary: memory: 0x1000000 -> 0x229b000 (XEN) elf_xen_parse_note: GUEST_OS = "linux" (XEN) elf_xen_parse_note: GUEST_VERSION = "2.6" (XEN) elf_xen_parse_note: XEN_VERSION = "xen-3.0" (XEN) elf_xen_parse_note: VIRT_BASE = 0xffffffff80000000 (XEN) elf_xen_parse_note: ENTRY = 0xffffffff81cd9210 (XEN) elf_xen_parse_note: HYPERCALL_PAGE = 0xffffffff81001000 (XEN) elf_xen_parse_note: FEATURES = "!writable_page_tables|pae_pgdir_above_4gb" (XEN) elf_xen_parse_note: PAE_MODE = "yes" (XEN) elf_xen_parse_note: LOADER = "generic" (XEN) elf_xen_parse_note: unknown xen elf note (0xd) (XEN) elf_xen_parse_note: SUSPEND_CANCEL = 0x1 (XEN) elf_xen_parse_note: HV_START_LOW = 0xffff800000000000 (XEN) elf_xen_parse_note: PADDR_OFFSET = 0x0 (XEN) elf_xen_addr_calc_check: addresses: (XEN) virt_base = 0xffffffff80000000 (XEN) elf_paddr_offset = 0x0 (XEN) virt_offset = 0xffffffff80000000 (XEN) virt_kstart = 0xffffffff81000000 (XEN) virt_kend = 0xffffffff8229b000 (XEN) virt_entry = 0xffffffff81cd9210 (XEN) p2m_base = 0xffffffffffffffff (XEN) Xen kernel: 64-bit, lsb, compat32 (XEN) Dom0 kernel: 64-bit, PAE, lsb, paddr 0x1000000 -> 0x229b000 (XEN) PHYSICAL MEMORY ARRANGEMENT: (XEN) Dom0 alloc.: 0000000840000000->0000000844000000 (505427 pages to be allocated) (XEN) Init. ramdisk: 000000085f653000->000000085ffffa00 (XEN) VIRTUAL MEMORY ARRANGEMENT: (XEN) Loaded kernel: ffffffff81000000->ffffffff8229b000 (XEN) Init. ramdisk: ffffffff8229b000->ffffffff82c47a00 (XEN) Phys-Mach map: ffffffff82c48000->ffffffff83048000 (XEN) Start info: ffffffff83048000->ffffffff830484b4 (XEN) Page tables: ffffffff83049000->ffffffff83066000 (XEN) Boot stack: ffffffff83066000->ffffffff83067000 (XEN) TOTAL: ffffffff80000000->ffffffff83400000 (XEN) ENTRY ADDRESS: ffffffff81cd9210 (XEN) Dom0 has maximum 2 VCPUs (XEN) elf_load_binary: phdr 0 at 0xffffffff81000000 -> 0xffffffff81a69000 (XEN) elf_load_binary: phdr 1 at 0xffffffff81c00000 -> 0xffffffff81cc30e8 (XEN) elf_load_binary: phdr 2 at 0xffffffff81cc4000 -> 0xffffffff81cd84c0 (XEN) elf_load_binary: phdr 3 at 0xffffffff81cd9000 -> 0xffffffff81d82000 (XEN) Scrubbing Free RAM: ..............................................................................................................................................................................................................................................................................................................done. (XEN) Initial low memory virq threshold set at 0x4000 pages. (XEN) Std. Loglevel: Errors, warnings and info (XEN) Guest Loglevel: All (XEN) Xen is relinquishing VGA console. (XEN) *** Serial input -> DOM0 (type 'CTRL-a' three times to switch input to Xen) (XEN) Freed 240kB init memory. mapping kernel into physical memory about to get started... [ 0.000000] Initializing cgroup subsys cpuset [ 0.000000] Initializing cgroup subsys cpu [ 0.000000] Linux version 3.6.0-rc4+ (root@xen-server01.ark-net.org) (gcc version 4.5.1 20100924 (Red Hat 4.5.1-4) (GCC) ) #2 SMP Mon Sep 10 14:42:44 EDT 2012 [ 0.000000] Command line: ro root=/dev/mapper/vg_xenserver01-LV_ROOT rd_LVM_LV=vg_xenserver01/LV_ROOT rd_LVM_LV=vg_xenserver01/LV_SWAP rd_NO_LUKS rd_NO_MD rd_NO_DM LANG=en_US.UTF-8 SYSFONT=latarcyrheb-sun16 KEYTABLE=us nomodeset ixen-pciback.passthrough=1 xen-pciback.hide=(0d:08.0)(0d:09.0)(0a:00.0) earlyprintk=xen [ 0.000000] Freeing 99-100 pfn range: 103 pages freed [ 0.000000] Released 103 pages of unused memory [ 0.000000] Set 402563 page(s) to 1-1 mapping [ 0.000000] Populating 80000-80067 pfn range: 103 pages added [ 0.000000] e820: BIOS-provided physical RAM map: [ 0.000000] Xen: [mem 0x0000000000000000-0x0000000000098fff] usable [ 0.000000] Xen: [mem 0x0000000000099400-0x00000000000fffff] reserved [ 0.000000] Xen: [mem 0x0000000000100000-0x000000009dbe3fff] usable [ 0.000000] Xen: [mem 0x000000009dbe4000-0x000000009dcb5fff] ACPI NVS [ 0.000000] Xen: [mem 0x000000009dcb6000-0x000000009f6a3fff] ACPI data [ 0.000000] Xen: [mem 0x000000009f6a4000-0x000000009f6defff] reserved [ 0.000000] Xen: [mem 0x000000009f6df000-0x000000009f789fff] ACPI data [ 0.000000] Xen: [mem 0x000000009f78a000-0x000000009f7defff] ACPI NVS [ 0.000000] Xen: [mem 0x000000009f7df000-0x000000009f7fffff] ACPI data [ 0.000000] Xen: [mem 0x000000009f800000-0x00000000afffffff] reserved [ 0.000000] Xen: [mem 0x00000000fec00000-0x00000000fec00fff] reserved [ 0.000000] Xen: [mem 0x00000000fed1c000-0x00000000fed1ffff] reserved [ 0.000000] Xen: [mem 0x00000000fee00000-0x00000000fee00fff] reserved [ 0.000000] Xen: [mem 0x00000000ff800000-0x00000000ffffffff] reserved [ 0.000000] Xen: [mem 0x0000000100000000-0x00000005e2888fff] usable [ 0.000000] Xen: [mem 0x00000005e2889000-0x000000085fffffff] unusable [ 0.000000] bootconsole [xenboot0] enabled [ 0.000000] NX (Execute Disable) protection: active [ 0.000000] DMI 2.5 present. [ 0.000000] No AGP bridge found [ 0.000000] e820: last_pfn = 0x5e2889 max_arch_pfn = 0x400000000 [ 0.000000] e820: last_pfn = 0x9dbe4 max_arch_pfn = 0x400000000 [ 0.000000] found SMP MP-table at [mem 0x000fda10-0x000fda1f] mapped at [ffff8800000fda10] [ 0.000000] init_memory_mapping: [mem 0x00000000-0x9dbe3fff] [ 0.000000] init_memory_mapping: [mem 0x100000000-0x5e2888fff] [ 0.000000] RAMDISK: [mem 0x0229b000-0x02c47fff] [ 0.000000] ACPI: RSDP 00000000000f0410 00024 (v02 INTEL ) [ 0.000000] ACPI: XSDT 000000009f7fd120 00094 (v01 INTEL S3420GPX 00000000 01000013) [ 0.000000] ACPI: FACP 000000009f7fb000 000F4 (v04 INTEL S3420GPX 00000000 MSFT 0100000D) [ 0.000000] ACPI: DSDT 000000009f7f5000 055D6 (v02 INTEL S3420GPX 00000003 MSFT 0100000D) [ 0.000000] ACPI: FACS 000000009f78a000 00040 [ 0.000000] ACPI: APIC 000000009f7f4000 000BC (v02 INTEL S3420GPX 00000000 MSFT 0100000D) [ 0.000000] ACPI: MCFG 000000009f7f3000 0003C (v01 INTEL S3420GPX 00000001 MSFT 0100000D) [ 0.000000] ACPI: HPET 000000009f7f2000 00038 (v01 INTEL S3420GPX 00000001 MSFT 0100000D) [ 0.000000] ACPI: SLIT 000000009f7f1000 00030 (v01 INTEL S3420GPX 00000001 MSFT 0100000D) [ 0.000000] ACPI: SPCR 000000009f7f0000 00050 (v01 INTEL S3420GPX 00000000 MSFT 0100000D) [ 0.000000] ACPI: WDDT 000000009f7ef000 00040 (v01 INTEL S3420GPX 00000000 MSFT 0100000D) [ 0.000000] ACPI: SSDT 000000009f7e4000 0AEF4 (v02 INTEL SSDT PM 00004000 INTL 20061109) [ 0.000000] ACPI: SSDT 000000009f7e3000 001D8 (v02 INTEL IPMI 00004000 INTL 20061109) [ 0.000000] ACPI: XMAR 000000009f7e2000 000A8 (v01 INTEL S3420GPX 00000001 MSFT 0100000D) [ 0.000000] ACPI: HEST 000000009f7e1000 000A8 (v01 INTEL S3420GPX 00000001 INTL 00000001) [ 0.000000] ACPI: BERT 000000009f7e0000 00030 (v01 INTEL S3420GPX 00000001 INTL 00000001) [ 0.000000] ACPI: ERST 000000009f7df000 00230 (v01 INTEL S3420GPX 00000001 INTL 00000001) [ 0.000000] ACPI: EINJ 000000009f789000 00130 (v01 INTEL S3420GPX 00000001 INTL 00000001) [ 0.000000] NUMA: Warning: node ids are out of bound, from=-1 to=-1 distance=10 [ 0.000000] No NUMA configuration found [ 0.000000] Faking a node at [mem 0x0000000000000000-0x00000005e2888fff] [ 0.000000] Initmem setup node 0 [mem 0x00000000-0x5e2888fff] [ 0.000000] NODE_DATA [mem 0x80063000-0x80066fff] [ 0.000000] Zone ranges: [ 0.000000] DMA [mem 0x00010000-0x00ffffff] [ 0.000000] DMA32 [mem 0x01000000-0xffffffff] [ 0.000000] Normal [mem 0x100000000-0x5e2888fff] [ 0.000000] Movable zone start for each node [ 0.000000] Early memory node ranges [ 0.000000] node 0: [mem 0x00010000-0x00098fff] [ 0.000000] node 0: [mem 0x00100000-0x9dbe3fff] [ 0.000000] node 0: [mem 0x100000000-0x5e2888fff] [ 0.000000] ACPI: PM-Timer IO Port: 0x408 [ 0.000000] ACPI: LAPIC (acpi_id[0x00] lapic_id[0x00] enabled) [ 0.000000] ACPI: LAPIC (acpi_id[0x01] lapic_id[0x02] enabled) [ 0.000000] ACPI: LAPIC (acpi_id[0x02] lapic_id[0x04] enabled) [ 0.000000] ACPI: LAPIC (acpi_id[0x03] lapic_id[0x06] enabled) [ 0.000000] ACPI: LAPIC (acpi_id[0x04] lapic_id[0x01] enabled) [ 0.000000] ACPI: LAPIC (acpi_id[0x05] lapic_id[0x03] enabled) [ 0.000000] ACPI: LAPIC (acpi_id[0x06] lapic_id[0x05] enabled) [ 0.000000] ACPI: LAPIC (acpi_id[0x07] lapic_id[0x07] enabled) [ 0.000000] ACPI: LAPIC_NMI (acpi_id[0x00] high level lint[0x1]) [ 0.000000] ACPI: LAPIC_NMI (acpi_id[0x01] high level lint[0x1]) [ 0.000000] ACPI: LAPIC_NMI (acpi_id[0x02] high level lint[0x1]) [ 0.000000] ACPI: LAPIC_NMI (acpi_id[0x03] high level lint[0x1]) [ 0.000000] ACPI: LAPIC_NMI (acpi_id[0x04] high level lint[0x1]) [ 0.000000] ACPI: LAPIC_NMI (acpi_id[0x05] high level lint[0x1]) [ 0.000000] ACPI: LAPIC_NMI (acpi_id[0x06] high level lint[0x1]) [ 0.000000] ACPI: LAPIC_NMI (acpi_id[0x07] high level lint[0x1]) [ 0.000000] ACPI: IOAPIC (id[0x08] address[0xfec00000] gsi_base[0]) [ 0.000000] IOAPIC[0]: apic_id 8, version 32, address 0xfec00000, GSI 0-23 [ 0.000000] ACPI: INT_SRC_OVR (bus 0 bus_irq 0 global_irq 2 dfl dfl) [ 0.000000] ACPI: INT_SRC_OVR (bus 0 bus_irq 9 global_irq 9 high level) [ 0.000000] Using ACPI (MADT) for SMP configuration information [ 0.000000] ACPI: HPET id: 0x8086a801 base: 0xfed00000 [ 0.000000] smpboot: Allowing 8 CPUs, 0 hotplug CPUs [ 0.000000] PM: Registered nosave memory: 0000000000099000 - 000000000009a000 [ 0.000000] PM: Registered nosave memory: 000000000009a000 - 0000000000100000 [ 0.000000] PM: Registered nosave memory: 000000009dbe4000 - 000000009dcb6000 [ 0.000000] PM: Registered nosave memory: 000000009dcb6000 - 000000009f6a4000 [ 0.000000] PM: Registered nosave memory: 000000009f6a4000 - 000000009f6df000 [ 0.000000] PM: Registered nosave memory: 000000009f6df000 - 000000009f78a000 [ 0.000000] PM: Registered nosave memory: 000000009f78a000 - 000000009f7df000 [ 0.000000] PM: Registered nosave memory: 000000009f7df000 - 000000009f800000 [ 0.000000] PM: Registered nosave memory: 000000009f800000 - 00000000b0000000 [ 0.000000] PM: Registered nosave memory: 00000000b0000000 - 00000000fec00000 [ 0.000000] PM: Registered nosave memory: 00000000fec00000 - 00000000fec01000 [ 0.000000] PM: Registered nosave memory: 00000000fec01000 - 00000000fed1c000 [ 0.000000] PM: Registered nosave memory: 00000000fed1c000 - 00000000fed20000 [ 0.000000] PM: Registered nosave memory: 00000000fed20000 - 00000000fee00000 [ 0.000000] PM: Registered nosave memory: 00000000fee00000 - 00000000fee01000 [ 0.000000] PM: Registered nosave memory: 00000000fee01000 - 00000000ff800000 [ 0.000000] PM: Registered nosave memory: 00000000ff800000 - 0000000100000000 [ 0.000000] e820: [mem 0xb0000000-0xfebfffff] available for PCI devices [ 0.000000] Booting paravirtualized kernel on Xen [ 0.000000] Xen version: 4.3-unstable (preserve-AD) [ 0.000000] setup_percpu: NR_CPUS:64 nr_cpumask_bits:64 nr_cpu_ids:8 nr_node_ids:1 [ 0.000000] PERCPU: Embedded 28 pages/cpu @ffff88007fe00000 s83136 r8192 d23360 u262144 [ 7.896640] Built 1 zonelists in Zone order, mobility grouping on. Total pages: 5670523 [ 7.896644] Policy zone: Normal [ 7.896647] Kernel command line: ro root=/dev/mapper/vg_xenserver01-LV_ROOT rd_LVM_LV=vg_xenserver01/LV_ROOT rd_LVM_LV=vg_xenserver01/LV_SWAP rd_NO_LUKS rd_NO_MD rd_NO_DM LANG=en_US.UTF-8 SYSFONT=latarcyrheb-sun16 KEYTABLE=us nomodeset ixen-pciback.passthrough=1 xen-pciback.hide=(0d:08.0)(0d:09.0)(0a:00.0) earlyprintk=xen [ 7.896813] PID hash table entries: 4096 (order: 3, 32768 bytes) [ 7.896819] __ex_table already sorted, skipping sort [ 7.931839] software IO TLB [mem 0x62a00000-0x669fffff] (64MB) mapped at [ffff880062a00000-ffff8800669fffff] [ 7.939410] Memory: 1592636k/24683044k available (8177k kernel code, 1610316k absent, 21480092k reserved, 4886k data, 728k init) [ 7.939490] SLUB: Genslabs=15, HWalign=64, Order=0-3, MinObjects=0, CPUs=2, Nodes=1 [ 7.939516] Hierarchical RCU implementation. [ 7.939518] RCU restricting CPUs from NR_CPUS=64 to nr_cpu_ids=2. [ 7.939527] NR_IRQS:4352 nr_irqs:512 16 [ 7.939587] xen: sci override: global_irq=9 trigger=0 polarity=0 [ 7.939610] xen: acpi sci 9 [ 7.942204] Console: colour VGA+ 80x25 [ 7.942209] console [tty0] enabled, bootconsole disabled (XEN) traps.c:2584:d0 Domain attempted WRMSR 00000000000000e2 from 0x0000000006008403 to 0x0000000000008403. (XEN) traps.c:2584:d0 Domain attempted WRMSR 00000000000000e2 from 0x0000000006008403 to 0x0000000000008403. (XEN) Cannot bind IRQ2 to dom0. In use by 'cascade'. (XEN) Cannot bind IRQ2 to dom0. In use by 'cascade'. (XEN) Cannot bind IRQ2 to dom0. In use by 'cascade'. (XEN) Cannot bind IRQ2 to dom0. In use by 'cascade'. (XEN) Cannot bind IRQ2 to dom0. In use by 'cascade'. (XEN) Cannot bind IRQ2 to dom0. In use by 'cascade'. (XEN) Cannot bind IRQ2 to dom0. In use by 'cascade'. (XEN) Cannot bind IRQ2 to dom0. In use by 'cascade'. (XEN) Monitor-Mwait will be used to enter C1 state (XEN) Monitor-Mwait will be used to enter C3 state Kernel dmesg: [ 0.000000] Initializing cgroup subsys cpuset [ 0.000000] Initializing cgroup subsys cpu [ 0.000000] Linux version 3.6.0-rc4+ (root@xen-server01.ark-net.org) (gcc version 4.5.1 20100924 (Red Hat 4.5.1-4) (GCC) ) #2 SMP Mon Sep 10 14:42:44 EDT 2012 [ 0.000000] Command line: ro root=/dev/mapper/vg_xenserver01-LV_ROOT rd_LVM_LV=vg_xenserver01/LV_ROOT rd_LVM_LV=vg_xenserver01/LV_SWAP rd_NO_LUKS rd_NO_MD rd_NO_DM LANG=en_US.UTF-8 SYSFONT=latarcyrheb-sun16 KEYTABLE=us nomodeset ixen-pciback.passthrough=1 xen-pciback.hide=(0d:08.0)(0d:09.0)(0a:00.0) earlyprintk=xen [ 0.000000] Freeing 99-100 pfn range: 103 pages freed [ 0.000000] 1-1 mapping on 99->100 [ 0.000000] 1-1 mapping on 9dbe4->100000 [ 0.000000] Released 103 pages of unused memory [ 0.000000] Set 402563 page(s) to 1-1 mapping [ 0.000000] Populating 80000-80067 pfn range: 103 pages added [ 0.000000] e820: BIOS-provided physical RAM map: [ 0.000000] Xen: [mem 0x0000000000000000-0x0000000000098fff] usable [ 0.000000] Xen: [mem 0x0000000000099400-0x00000000000fffff] reserved [ 0.000000] Xen: [mem 0x0000000000100000-0x000000009dbe3fff] usable [ 0.000000] Xen: [mem 0x000000009dbe4000-0x000000009dcb5fff] ACPI NVS [ 0.000000] Xen: [mem 0x000000009dcb6000-0x000000009f6a3fff] ACPI data [ 0.000000] Xen: [mem 0x000000009f6a4000-0x000000009f6defff] reserved [ 0.000000] Xen: [mem 0x000000009f6df000-0x000000009f789fff] ACPI data [ 0.000000] Xen: [mem 0x000000009f78a000-0x000000009f7defff] ACPI NVS [ 0.000000] Xen: [mem 0x000000009f7df000-0x000000009f7fffff] ACPI data [ 0.000000] Xen: [mem 0x000000009f800000-0x00000000afffffff] reserved [ 0.000000] Xen: [mem 0x00000000fec00000-0x00000000fec00fff] reserved [ 0.000000] Xen: [mem 0x00000000fed1c000-0x00000000fed1ffff] reserved [ 0.000000] Xen: [mem 0x00000000fee00000-0x00000000fee00fff] reserved [ 0.000000] Xen: [mem 0x00000000ff800000-0x00000000ffffffff] reserved [ 0.000000] Xen: [mem 0x0000000100000000-0x00000005e2888fff] usable [ 0.000000] Xen: [mem 0x00000005e2889000-0x000000085fffffff] unusable [ 0.000000] bootconsole [xenboot0] enabled [ 0.000000] NX (Execute Disable) protection: active [ 0.000000] DMI 2.5 present. [ 0.000000] DMI: Intel Corporation S3420GP/S3420GP, BIOS S3420GP.86B.01.00.0050.090220111526 09/02/2011 [ 0.000000] e820: update [mem 0x00000000-0x0000ffff] usable ==> reserved [ 0.000000] e820: remove [mem 0x000a0000-0x000fffff] usable [ 0.000000] No AGP bridge found [ 0.000000] e820: last_pfn = 0x5e2889 max_arch_pfn = 0x400000000 [ 0.000000] e820: last_pfn = 0x9dbe4 max_arch_pfn = 0x400000000 [ 0.000000] found SMP MP-table at [mem 0x000fda10-0x000fda1f] mapped at [ffff8800000fda10] [ 0.000000] initial memory mapped: [mem 0x00000000-0x02c47fff] [ 0.000000] Base memory trampoline at [ffff880000093000] 93000 size 24576 [ 0.000000] init_memory_mapping: [mem 0x00000000-0x9dbe3fff] [ 0.000000] [mem 0x00000000-0x9dbe3fff] page 4k [ 0.000000] kernel direct mapping tables up to 0x9dbe3fff @ [mem 0x00b0e000-0x00ffffff] [ 0.000000] xen: setting RW the range fe0000 - 1000000 [ 0.000000] init_memory_mapping: [mem 0x100000000-0x5e2888fff] [ 0.000000] [mem 0x100000000-0x5e2888fff] page 4k [ 0.000000] kernel direct mapping tables up to 0x5e2888fff @ [mem 0x7d139000-0x80066fff] [ 0.000000] xen: setting RW the range 7f862000 - 80067000 [ 0.000000] RAMDISK: [mem 0x0229b000-0x02c47fff] [ 0.000000] ACPI: RSDP 00000000000f0410 00024 (v02 INTEL ) [ 0.000000] ACPI: XSDT 000000009f7fd120 00094 (v01 INTEL S3420GPX 00000000 01000013) [ 0.000000] ACPI: FACP 000000009f7fb000 000F4 (v04 INTEL S3420GPX 00000000 MSFT 0100000D) [ 0.000000] ACPI: DSDT 000000009f7f5000 055D6 (v02 INTEL S3420GPX 00000003 MSFT 0100000D) [ 0.000000] ACPI: FACS 000000009f78a000 00040 [ 0.000000] ACPI: APIC 000000009f7f4000 000BC (v02 INTEL S3420GPX 00000000 MSFT 0100000D) [ 0.000000] ACPI: MCFG 000000009f7f3000 0003C (v01 INTEL S3420GPX 00000001 MSFT 0100000D) [ 0.000000] ACPI: HPET 000000009f7f2000 00038 (v01 INTEL S3420GPX 00000001 MSFT 0100000D) [ 0.000000] ACPI: SLIT 000000009f7f1000 00030 (v01 INTEL S3420GPX 00000001 MSFT 0100000D) [ 0.000000] ACPI: SPCR 000000009f7f0000 00050 (v01 INTEL S3420GPX 00000000 MSFT 0100000D) [ 0.000000] ACPI: WDDT 000000009f7ef000 00040 (v01 INTEL S3420GPX 00000000 MSFT 0100000D) [ 0.000000] ACPI: SSDT 000000009f7e4000 0AEF4 (v02 INTEL SSDT PM 00004000 INTL 20061109) [ 0.000000] ACPI: SSDT 000000009f7e3000 001D8 (v02 INTEL IPMI 00004000 INTL 20061109) [ 0.000000] ACPI: XMAR 000000009f7e2000 000A8 (v01 INTEL S3420GPX 00000001 MSFT 0100000D) [ 0.000000] ACPI: HEST 000000009f7e1000 000A8 (v01 INTEL S3420GPX 00000001 INTL 00000001) [ 0.000000] ACPI: BERT 000000009f7e0000 00030 (v01 INTEL S3420GPX 00000001 INTL 00000001) [ 0.000000] ACPI: ERST 000000009f7df000 00230 (v01 INTEL S3420GPX 00000001 INTL 00000001) [ 0.000000] ACPI: EINJ 000000009f789000 00130 (v01 INTEL S3420GPX 00000001 INTL 00000001) [ 0.000000] ACPI: Local APIC address 0xfee00000 [ 0.000000] NUMA: Initialized distance table, cnt=1 [ 0.000000] NUMA: Warning: node ids are out of bound, from=-1 to=-1 distance=10 [ 0.000000] No NUMA configuration found [ 0.000000] Faking a node at [mem 0x0000000000000000-0x00000005e2888fff] [ 0.000000] Initmem setup node 0 [mem 0x00000000-0x5e2888fff] [ 0.000000] NODE_DATA [mem 0x80063000-0x80066fff] [ 0.000000] Zone ranges: [ 0.000000] DMA [mem 0x00010000-0x00ffffff] [ 0.000000] DMA32 [mem 0x01000000-0xffffffff] [ 0.000000] Normal [mem 0x100000000-0x5e2888fff] [ 0.000000] Movable zone start for each node [ 0.000000] Early memory node ranges [ 0.000000] node 0: [mem 0x00010000-0x00098fff] [ 0.000000] node 0: [mem 0x00100000-0x9dbe3fff] [ 0.000000] node 0: [mem 0x100000000-0x5e2888fff] [ 0.000000] On node 0 totalpages: 5768182 [ 0.000000] DMA zone: 64 pages used for memmap [ 0.000000] DMA zone: 1240 pages reserved [ 0.000000] DMA zone: 2673 pages, LIFO batch:0 [ 0.000000] DMA32 zone: 16320 pages used for memmap [ 0.000000] DMA32 zone: 625700 pages, LIFO batch:31 [ 0.000000] Normal zone: 80035 pages used for memmap [ 0.000000] Normal zone: 5042150 pages, LIFO batch:31 [ 0.000000] ACPI: PM-Timer IO Port: 0x408 [ 0.000000] ACPI: Local APIC address 0xfee00000 [ 0.000000] ACPI: LAPIC (acpi_id[0x00] lapic_id[0x00] enabled) [ 0.000000] ACPI: LAPIC (acpi_id[0x01] lapic_id[0x02] enabled) [ 0.000000] ACPI: LAPIC (acpi_id[0x02] lapic_id[0x04] enabled) [ 0.000000] ACPI: LAPIC (acpi_id[0x03] lapic_id[0x06] enabled) [ 0.000000] ACPI: LAPIC (acpi_id[0x04] lapic_id[0x01] enabled) [ 0.000000] ACPI: LAPIC (acpi_id[0x05] lapic_id[0x03] enabled) [ 0.000000] ACPI: LAPIC (acpi_id[0x06] lapic_id[0x05] enabled) [ 0.000000] ACPI: LAPIC (acpi_id[0x07] lapic_id[0x07] enabled) [ 0.000000] ACPI: LAPIC_NMI (acpi_id[0x00] high level lint[0x1]) [ 0.000000] ACPI: LAPIC_NMI (acpi_id[0x01] high level lint[0x1]) [ 0.000000] ACPI: LAPIC_NMI (acpi_id[0x02] high level lint[0x1]) [ 0.000000] ACPI: LAPIC_NMI (acpi_id[0x03] high level lint[0x1]) [ 0.000000] ACPI: LAPIC_NMI (acpi_id[0x04] high level lint[0x1]) [ 0.000000] ACPI: LAPIC_NMI (acpi_id[0x05] high level lint[0x1]) [ 0.000000] ACPI: LAPIC_NMI (acpi_id[0x06] high level lint[0x1]) [ 0.000000] ACPI: LAPIC_NMI (acpi_id[0x07] high level lint[0x1]) [ 0.000000] ACPI: IOAPIC (id[0x08] address[0xfec00000] gsi_base[0]) [ 0.000000] IOAPIC[0]: apic_id 8, version 32, address 0xfec00000, GSI 0-23 [ 0.000000] ACPI: INT_SRC_OVR (bus 0 bus_irq 0 global_irq 2 dfl dfl) [ 0.000000] ACPI: INT_SRC_OVR (bus 0 bus_irq 9 global_irq 9 high level) [ 0.000000] ACPI: IRQ0 used by override. [ 0.000000] ACPI: IRQ2 used by override. [ 0.000000] ACPI: IRQ9 used by override. [ 0.000000] Using ACPI (MADT) for SMP configuration information [ 0.000000] ACPI: HPET id: 0x8086a801 base: 0xfed00000 [ 0.000000] smpboot: Allowing 8 CPUs, 0 hotplug CPUs [ 0.000000] nr_irqs_gsi: 40 [ 0.000000] PM: Registered nosave memory: 0000000000099000 - 000000000009a000 [ 0.000000] PM: Registered nosave memory: 000000000009a000 - 0000000000100000 [ 0.000000] PM: Registered nosave memory: 000000009dbe4000 - 000000009dcb6000 [ 0.000000] PM: Registered nosave memory: 000000009dcb6000 - 000000009f6a4000 [ 0.000000] PM: Registered nosave memory: 000000009f6a4000 - 000000009f6df000 [ 0.000000] PM: Registered nosave memory: 000000009f6df000 - 000000009f78a000 [ 0.000000] PM: Registered nosave memory: 000000009f78a000 - 000000009f7df000 [ 0.000000] PM: Registered nosave memory: 000000009f7df000 - 000000009f800000 [ 0.000000] PM: Registered nosave memory: 000000009f800000 - 00000000b0000000 [ 0.000000] PM: Registered nosave memory: 00000000b0000000 - 00000000fec00000 [ 0.000000] PM: Registered nosave memory: 00000000fec00000 - 00000000fec01000 [ 0.000000] PM: Registered nosave memory: 00000000fec01000 - 00000000fed1c000 [ 0.000000] PM: Registered nosave memory: 00000000fed1c000 - 00000000fed20000 [ 0.000000] PM: Registered nosave memory: 00000000fed20000 - 00000000fee00000 [ 0.000000] PM: Registered nosave memory: 00000000fee00000 - 00000000fee01000 [ 0.000000] PM: Registered nosave memory: 00000000fee01000 - 00000000ff800000 [ 0.000000] PM: Registered nosave memory: 00000000ff800000 - 0000000100000000 [ 0.000000] e820: [mem 0xb0000000-0xfebfffff] available for PCI devices [ 0.000000] Booting paravirtualized kernel on Xen [ 0.000000] Xen version: 4.3-unstable (preserve-AD) [ 0.000000] setup_percpu: NR_CPUS:64 nr_cpumask_bits:64 nr_cpu_ids:8 nr_node_ids:1 [ 0.000000] PERCPU: Embedded 28 pages/cpu @ffff88007fe00000 s83136 r8192 d23360 u262144 [ 0.000000] pcpu-alloc: s83136 r8192 d23360 u262144 alloc=1*2097152 [ 0.000000] pcpu-alloc: [0] 0 1 2 3 4 5 6 7 [ 7.896640] Built 1 zonelists in Zone order, mobility grouping on. Total pages: 5670523 [ 7.896644] Policy zone: Normal [ 7.896647] Kernel command line: ro root=/dev/mapper/vg_xenserver01-LV_ROOT rd_LVM_LV=vg_xenserver01/LV_ROOT rd_LVM_LV=vg_xenserver01/LV_SWAP rd_NO_LUKS rd_NO_MD rd_NO_DM LANG=en_US.UTF-8 SYSFONT=latarcyrheb-sun16 KEYTABLE=us nomodeset ixen-pciback.passthrough=1 xen-pciback.hide=(0d:08.0)(0d:09.0)(0a:00.0) earlyprintk=xen [ 7.896813] PID hash table entries: 4096 (order: 3, 32768 bytes) [ 7.896819] __ex_table already sorted, skipping sort [ 7.931839] software IO TLB [mem 0x62a00000-0x669fffff] (64MB) mapped at [ffff880062a00000-ffff8800669fffff] [ 7.939410] Memory: 1592636k/24683044k available (8177k kernel code, 1610316k absent, 21480092k reserved, 4886k data, 728k init) [ 7.939490] SLUB: Genslabs=15, HWalign=64, Order=0-3, MinObjects=0, CPUs=2, Nodes=1 [ 7.939516] Hierarchical RCU implementation. [ 7.939518] RCU restricting CPUs from NR_CPUS=64 to nr_cpu_ids=2. [ 7.939527] NR_IRQS:4352 nr_irqs:512 16 [ 7.939587] xen: sci override: global_irq=9 trigger=0 polarity=0 [ 7.939590] xen: registering gsi 9 triggering 0 polarity 0 [ 7.939603] xen: --> pirq=9 -> irq=9 (gsi=9) [ 7.939610] xen: acpi sci 9 [ 7.939615] xen: --> pirq=1 -> irq=1 (gsi=1) [ 7.939618] xen: --> pirq=2 -> irq=2 (gsi=2) [ 7.939621] xen: --> pirq=3 -> irq=3 (gsi=3) [ 7.939624] xen: --> pirq=4 -> irq=4 (gsi=4) [ 7.939627] xen: --> pirq=5 -> irq=5 (gsi=5) [ 7.939630] xen: --> pirq=6 -> irq=6 (gsi=6) [ 7.939633] xen: --> pirq=7 -> irq=7 (gsi=7) [ 7.939636] xen: --> pirq=8 -> irq=8 (gsi=8) [ 7.939639] xen: --> pirq=10 -> irq=10 (gsi=10) [ 7.939642] xen: --> pirq=11 -> irq=11 (gsi=11) [ 7.939645] xen: --> pirq=12 -> irq=12 (gsi=12) [ 7.939648] xen: --> pirq=13 -> irq=13 (gsi=13) [ 7.939651] xen: --> pirq=14 -> irq=14 (gsi=14) [ 7.939654] xen: --> pirq=15 -> irq=15 (gsi=15) [ 7.942204] Console: colour VGA+ 80x25 [ 7.942209] console [tty0] enabled, bootconsole disabled [ 7.942303] Xen: using vcpuop timer interface [ 7.942307] installing Xen timer for CPU 0 [ 7.942388] tsc: Detected 2533.348 MHz processor [ 7.942452] Calibrating delay loop (skipped), value calculated using timer frequency.. 5066.69 BogoMIPS (lpj=2533348) [ 7.942579] pid_max: default: 32768 minimum: 301 [ 7.942665] Security Framework initialized [ 7.942726] SELinux: Initializing. [ 7.942792] SELinux: Starting in permissive mode [ 7.946946] Dentry cache hash table entries: 4194304 (order: 13, 33554432 bytes) [ 7.957309] Inode-cache hash table entries: 2097152 (order: 12, 16777216 bytes) [ 7.961265] Mount-cache hash table entries: 256 [ 7.961582] Initializing cgroup subsys cpuacct [ 7.961644] Initializing cgroup subsys freezer [ 7.961759] CPU: Physical Processor ID: 0 [ 7.961817] CPU: Processor Core ID: 0 [ 7.961876] mce: CPU supports 2 MCE banks [ 7.961949] Last level iTLB entries: 4KB 512, 2MB 7, 4MB 7 [ 7.961949] Last level dTLB entries: 4KB 512, 2MB 32, 4MB 32 [ 7.961949] tlb_flushall_shift is 0x6 [ 7.964384] ACPI: Core revision 20120711 [ 7.976039] cpu 0 spinlock event irq 41 [ 7.976113] Performance Events: unsupported p6 CPU model 30 no PMU driver, software events only. [ 7.976529] installing Xen timer for CPU 1 [ 7.976677] cpu 1 spinlock event irq 48 [ 7.976995] Brought up 2 CPUs [ 7.977609] PM: Registering ACPI NVS region [mem 0x9dbe4000-0x9dcb5fff] (860160 bytes) [ 7.977846] PM: Registering ACPI NVS region [mem 0x9f78a000-0x9f7defff] (348160 bytes) [ 7.978107] Grant tables using version 2 layout. [ 7.978263] Grant table initialized [ 7.978425] RTC time: 23:56:03, date: 09/11/12 [ 7.978590] NET: Registered protocol family 16 [ 7.978902] kworker/u:0 (17) used greatest stack depth: 6336 bytes left [ 7.979061] kworker/u:0 (18) used greatest stack depth: 5816 bytes left [ 7.979937] ACPI FADT declares the system doesn't support PCIe ASPM, so disable it [ 7.980167] ACPI: bus type pci registered [ 7.980981] PCI: MMCONFIG for domain 0000 [bus 00-ff] at [mem 0xa0000000-0xafffffff] (base 0xa0000000) [ 7.981215] PCI: MMCONFIG at [mem 0xa0000000-0xafffffff] reserved in E820 [ 8.024972] PCI: Using configuration type 1 for base access [ 8.025320] kworker/u:0 (42) used greatest stack depth: 5360 bytes left [ 8.041080] bio: create slab at 0 [ 8.041391] ACPI: Added _OSI(Module Device) [ 8.041527] ACPI: Added _OSI(Processor Device) [ 8.041661] ACPI: Added _OSI(3.0 _SCP Extensions) [ 8.041796] ACPI: Added _OSI(Processor Aggregator Device) [ 8.043144] ACPI: EC: Look up EC in DSDT [ 8.043299] ACPI Error: Field [CPB3] at 96 exceeds Buffer [NULL] size 64 (bits) (20120711/dsopcode-236) [ 8.043619] ACPI Error: Method parse/execution failed [\_SB_._OSC] (Node ffff88005f474550), AE_AML_BUFFER_LIMIT (20120711/psparse-536) [ 8.052059] ACPI: Interpreter enabled [ 8.052195] ACPI: (supports S0 S1 S5) [ 8.052470] ACPI: Using IOAPIC for interrupt routing [ 8.067768] ACPI: No dock devices found. [ 8.067906] PCI: Using host bridge windows from ACPI; if necessary, use "pci=nocrs" and report a bug [ 8.068402] ACPI: PCI Root Bridge [PCI0] (domain 0000 [bus 00-fe]) [ 8.068935] pci_root PNP0A08:00: ignoring host bridge window [mem 0x000c4000-0x000cbfff] (conflicts with Video ROM [mem 0x000c0000-0x000c7fff]) [ 8.069248] PCI host bridge to bus 0000:00 [ 8.069386] pci_bus 0000:00: busn_res: [bus 00-fe] is inserted under domain [bus 00-ff] [ 8.069388] pci_bus 0000:00: root bus resource [bus 00-fe] [ 8.069526] pci_bus 0000:00: root bus resource [io 0x0000-0x0cf7] [ 8.069666] pci_bus 0000:00: root bus resource [io 0x0d00-0xffff] [ 8.069806] pci_bus 0000:00: root bus resource [mem 0x000a0000-0x000bffff] [ 8.069973] pci_bus 0000:00: root bus resource [mem 0xfed40000-0xfedfffff] [ 8.070120] pci_bus 0000:00: root bus resource [mem 0xb0000000-0xfdffffff] [ 8.070279] pci 0000:00:00.0: [8086:d130] type 00 class 0x060000 [ 8.070379] pci 0000:00:03.0: [8086:d138] type 01 class 0x060400 [ 8.070466] pci 0000:00:03.0: PME# supported from D0 D3hot D3cold [ 8.070512] pci 0000:00:08.0: [8086:d155] type 00 class 0x088000 [ 8.070627] pci 0000:00:08.1: [8086:d156] type 00 class 0x088000 [ 8.070742] pci 0000:00:08.2: [8086:d157] type 00 class 0x088000 [ 8.070851] pci 0000:00:08.3: [8086:d158] type 00 class 0x088000 [ 8.070961] pci 0000:00:10.0: [8086:d150] type 00 class 0x088000 [ 8.071080] pci 0000:00:10.1: [8086:d151] type 00 class 0x088000 [ 8.071214] pci 0000:00:19.0: [8086:10ef] type 00 class 0x020000 [ 8.071245] pci 0000:00:19.0: reg 10: [mem 0xba700000-0xba71ffff] [ 8.071259] pci 0000:00:19.0: reg 14: [mem 0xba725000-0xba725fff] [ 8.071273] pci 0000:00:19.0: reg 18: [io 0x4040-0x405f] [ 8.071365] pci 0000:00:19.0: PME# supported from D0 D3hot D3cold [ 8.071407] pci 0000:00:1a.0: [8086:3b3c] type 00 class 0x0c0320 [ 8.071439] pci 0000:00:1a.0: reg 10: [mem 0xba722000-0xba7223ff] [ 8.071566] pci 0000:00:1a.0: PME# supported from D0 D3hot D3cold [ 8.071604] pci 0000:00:1c.0: [8086:3b42] type 01 class 0x060400 [ 8.071705] pci 0000:00:1c.0: PME# supported from D0 D3hot D3cold [ 8.071749] pci 0000:00:1c.4: [8086:3b4a] type 01 class 0x060400 [ 8.071848] pci 0000:00:1c.4: PME# supported from D0 D3hot D3cold [ 8.071888] pci 0000:00:1c.6: [8086:3b4e] type 01 class 0x060400 [ 8.071987] pci 0000:00:1c.6: PME# supported from D0 D3hot D3cold [ 8.072026] pci 0000:00:1c.7: [8086:3b50] type 01 class 0x060400 [ 8.072138] pci 0000:00:1c.7: PME# supported from D0 D3hot D3cold [ 8.072184] pci 0000:00:1d.0: [8086:3b34] type 00 class 0x0c0320 [ 8.072217] pci 0000:00:1d.0: reg 10: [mem 0xba721000-0xba7213ff] [ 8.072348] pci 0000:00:1d.0: PME# supported from D0 D3hot D3cold [ 8.072383] pci 0000:00:1e.0: [8086:244e] type 01 class 0x060401 [ 8.072482] pci 0000:00:1f.0: [8086:3b14] type 00 class 0x060100 [ 8.072665] pci 0000:00:1f.2: [8086:3b22] type 00 class 0x010601 [ 8.072697] pci 0000:00:1f.2: reg 10: [io 0x4068-0x406f] [ 8.072711] pci 0000:00:1f.2: reg 14: [io 0x4074-0x4077] [ 8.072725] pci 0000:00:1f.2: reg 18: [io 0x4060-0x4067] [ 8.072738] pci 0000:00:1f.2: reg 1c: [io 0x4070-0x4073] [ 8.072752] pci 0000:00:1f.2: reg 20: [io 0x4020-0x403f] [ 8.072765] pci 0000:00:1f.2: reg 24: [mem 0xba720000-0xba7207ff] [ 8.072828] pci 0000:00:1f.2: PME# supported from D3hot [ 8.072861] pci 0000:00:1f.3: [8086:3b30] type 00 class 0x0c0500 [ 8.072885] pci 0000:00:1f.3: reg 10: [mem 0xba723000-0xba7230ff 64bit] [ 8.072923] pci 0000:00:1f.3: reg 20: [io 0x4000-0x401f] [ 8.073033] pci_bus 0000:01: busn_res: [bus 01-05] is inserted under [bus 00-fe] [ 8.073053] pci 0000:01:00.0: [111d:806f] type 01 class 0x060400 [ 8.073150] pci 0000:01:00.0: PME# supported from D0 D3hot D3cold [ 8.073571] pci 0000:00:03.0: PCI bridge to [bus 01-05] [ 8.073714] pci 0000:00:03.0: bridge window [io 0x3000-0x3fff] [ 8.073719] pci 0000:00:03.0: bridge window [mem 0xba600000-0xba6fffff] [ 8.073783] pci_bus 0000:02: busn_res: [bus 02-05] is inserted under [bus 01-05] [ 8.073806] pci 0000:02:02.0: [111d:806f] type 01 class 0x060400 [ 8.073909] pci 0000:02:02.0: PME# supported from D0 D3hot D3cold [ 8.073954] pci 0000:02:03.0: [111d:806f] type 01 class 0x060400 [ 8.074056] pci 0000:02:03.0: PME# supported from D0 D3hot D3cold [ 8.074100] pci 0000:02:04.0: [111d:806f] type 01 class 0x060400 [ 8.074202] pci 0000:02:04.0: PME# supported from D0 D3hot D3cold [ 8.074280] pci 0000:01:00.0: PCI bridge to [bus 02-05] [ 8.074429] pci 0000:01:00.0: bridge window [io 0x3000-0x3fff] [ 8.074435] pci 0000:01:00.0: bridge window [mem 0xba600000-0xba6fffff] [ 8.074512] pci_bus 0000:03: busn_res: [bus 03] is inserted under [bus 02-05] [ 8.074516] pci 0000:02:02.0: PCI bridge to [bus 03] [ 8.074749] pci_bus 0000:04: busn_res: [bus 04] is inserted under [bus 02-05] [ 8.074753] pci 0000:02:03.0: PCI bridge to [bus 04] [ 8.074982] pci_bus 0000:05: busn_res: [bus 05] is inserted under [bus 02-05] [ 8.075004] pci 0000:05:00.0: [1000:0079] type 00 class 0x010400 [ 8.075023] pci 0000:05:00.0: reg 10: [io 0x3000-0x30ff] [ 8.075046] pci 0000:05:00.0: reg 14: [mem 0xba640000-0xba643fff 64bit] [ 8.075068] pci 0000:05:00.0: reg 1c: [mem 0xba600000-0xba63ffff 64bit] [ 8.075097] pci 0000:05:00.0: reg 30: [mem 0xfffc0000-0xffffffff pref] [ 8.075145] pci 0000:05:00.0: supports D1 D2 [ 8.075195] pci 0000:02:04.0: PCI bridge to [bus 05] [ 8.075348] pci 0000:02:04.0: bridge window [io 0x3000-0x3fff] [ 8.075355] pci 0000:02:04.0: bridge window [mem 0xba600000-0xba6fffff] [ 8.075472] pci_bus 0000:06: busn_res: [bus 06-08] is inserted under [bus 00-fe] [ 8.075506] pci 0000:06:00.0: [8086:10c9] type 00 class 0x020000 [ 8.075527] pci 0000:06:00.0: reg 10: [mem 0xba420000-0xba43ffff] [ 8.075545] pci 0000:06:00.0: reg 14: [mem 0xba000000-0xba3fffff] [ 8.075562] pci 0000:06:00.0: reg 18: [io 0x2020-0x203f] [ 8.075579] pci 0000:06:00.0: reg 1c: [mem 0xba4c4000-0xba4c7fff] [ 8.075627] pci 0000:06:00.0: reg 30: [mem 0xffc00000-0xffffffff pref] [ 8.075688] pci 0000:06:00.0: PME# supported from D0 D3hot D3cold [ 8.075754] pci 0000:06:00.0: reg 184: [mem 0xba440000-0xba443fff 64bit] [ 8.075783] pci 0000:06:00.0: reg 190: [mem 0xba460000-0xba463fff 64bit] [ 8.075839] pci 0000:06:00.1: [8086:10c9] type 00 class 0x020000 [ 8.075860] pci 0000:06:00.1: reg 10: [mem 0xba400000-0xba41ffff] [ 8.075877] pci 0000:06:00.1: reg 14: [mem 0xb9c00000-0xb9ffffff] [ 8.075895] pci 0000:06:00.1: reg 18: [io 0x2000-0x201f] [ 8.075912] pci 0000:06:00.1: reg 1c: [mem 0xba4c0000-0xba4c3fff] [ 8.075960] pci 0000:06:00.1: reg 30: [mem 0xffc00000-0xffffffff pref] [ 8.076021] pci 0000:06:00.1: PME# supported from D0 D3hot D3cold [ 8.076076] pci 0000:06:00.1: reg 184: [mem 0xba480000-0xba483fff 64bit] [ 8.076105] pci 0000:06:00.1: reg 190: [mem 0xba4a0000-0xba4a3fff 64bit] [ 8.078634] pci 0000:00:1c.0: PCI bridge to [bus 06-08] [ 8.078788] pci 0000:00:1c.0: bridge window [io 0x2000-0x2fff] [ 8.078793] pci 0000:00:1c.0: bridge window [mem 0xb9c00000-0xba4fffff] [ 8.078871] pci_bus 0000:09: busn_res: [bus 09] is inserted under [bus 00-fe] [ 8.078910] pci 0000:09:00.0: [8086:10d3] type 00 class 0x020000 [ 8.078939] pci 0000:09:00.0: reg 10: [mem 0xba500000-0xba51ffff] [ 8.078987] pci 0000:09:00.0: reg 18: [io 0x1000-0x101f] [ 8.079010] pci 0000:09:00.0: reg 1c: [mem 0xba520000-0xba523fff] [ 8.079150] pci 0000:09:00.0: PME# supported from D0 D3hot D3cold [ 8.081852] pci 0000:00:1c.4: PCI bridge to [bus 09] [ 8.082007] pci 0000:00:1c.4: bridge window [io 0x1000-0x1fff] [ 8.082012] pci 0000:00:1c.4: bridge window [mem 0xba500000-0xba5fffff] [ 8.082090] pci_bus 0000:0a: busn_res: [bus 0a] is inserted under [bus 00-fe] [ 8.082120] pci 0000:0a:00.0: [102b:0522] type 00 class 0x030000 [ 8.082145] pci 0000:0a:00.0: reg 10: [mem 0xb8000000-0xb8ffffff pref] [ 8.082166] pci 0000:0a:00.0: reg 14: [mem 0xb9800000-0xb9803fff] [ 8.082186] pci 0000:0a:00.0: reg 18: [mem 0xb9000000-0xb97fffff] [ 8.082266] pci 0000:0a:00.0: reg 30: [mem 0xffff0000-0xffffffff pref] [ 8.085090] pci 0000:00:1c.6: PCI bridge to [bus 0a] [ 8.085255] pci 0000:00:1c.6: bridge window [mem 0xb9000000-0xb98fffff] [ 8.085264] pci 0000:00:1c.6: bridge window [mem 0xb8000000-0xb8ffffff 64bit pref] [ 8.085334] pci_bus 0000:0b: busn_res: [bus 0b] is inserted under [bus 00-fe] [ 8.085338] pci 0000:00:1c.7: PCI bridge to [bus 0b] [ 8.085529] pci_bus 0000:0c: busn_res: [bus 0c-0d] is inserted under [bus 00-fe] [ 8.085550] pci 0000:0c:00.0: [3388:0021] type 01 class 0x060400 [ 8.085651] pci 0000:0c:00.0: supports D1 D2 [ 8.085653] pci 0000:0c:00.0: PME# supported from D1 D2 D3hot D3cold [ 8.085733] pci 0000:00:1e.0: PCI bridge to [bus 0c-0d] (subtractive decode) [ 8.085891] pci 0000:00:1e.0: bridge window [mem 0xb0000000-0xb7ffffff 64bit pref] [ 8.085893] pci 0000:00:1e.0: bridge window [io 0x0000-0x0cf7] (subtractive decode) [ 8.085895] pci 0000:00:1e.0: bridge window [io 0x0d00-0xffff] (subtractive decode) [ 8.085897] pci 0000:00:1e.0: bridge window [mem 0x000a0000-0x000bffff] (subtractive decode) [ 8.085899] pci 0000:00:1e.0: bridge window [mem 0xfed40000-0xfedfffff] (subtractive decode) [ 8.085900] pci 0000:00:1e.0: bridge window [mem 0xb0000000-0xfdffffff] (subtractive decode) [ 8.085959] pci_bus 0000:0d: busn_res: [bus 0d] is inserted under [bus 0c-0d] [ 8.085997] pci 0000:0d:08.0: [4444:0016] type 00 class 0x040000 [ 8.086027] pci 0000:0d:08.0: reg 10: [mem 0xb4000000-0xb7ffffff pref] [ 8.086194] pci 0000:0d:09.0: [4444:0016] type 00 class 0x040000 [ 8.086224] pci 0000:0d:09.0: reg 10: [mem 0xb0000000-0xb3ffffff pref] [ 8.086419] pci 0000:0c:00.0: PCI bridge to [bus 0d] [ 8.086574] pci 0000:0c:00.0: bridge window [mem 0xb0000000-0xb7ffffff pref] [ 8.086631] ACPI: PCI Interrupt Routing Table [\_SB_.PCI0._PRT] [ 8.086740] ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.MRP1._PRT] [ 8.086764] ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.MRP1.GRP1._PRT] [ 8.086806] ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.MRP1.GRP1.G2P1._PRT] [ 8.086872] ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.MRP1.GRP1.G2P2._PRT] [ 8.086937] ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.MRP1.GRP1.G2P3._PRT] [ 8.087015] ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.PEX0._PRT] [ 8.087065] ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.PEX4._PRT] [ 8.087084] ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.PEX6._PRT] [ 8.087103] ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.PEX7._PRT] [ 8.087149] ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.IP2P._PRT] [ 8.087273] pci0000:00: Unable to request _OSC control (_OSC support mask: 0x0f) [ 8.094005] ACPI: PCI Interrupt Link [LNKA] (IRQs 3 4 5 6 7 9 *10 11 12 14 15) [ 8.094894] ACPI: PCI Interrupt Link [LNKB] (IRQs 3 4 5 6 7 9 10 *11 12 14 15) [ 8.095754] ACPI: PCI Interrupt Link [LNKC] (IRQs 3 4 *5 6 7 9 10 11 12 14 15) [ 8.096622] ACPI: PCI Interrupt Link [LNKD] (IRQs 3 4 5 6 7 9 10 *11 12 14 15) [ 8.097484] ACPI: PCI Interrupt Link [LNKE] (IRQs 3 4 5 6 7 9 10 11 12 14 15) *0, disabled. [ 8.098449] ACPI: PCI Interrupt Link [LNKF] (IRQs 3 4 5 6 7 *9 10 11 12 14 15) [ 8.099325] ACPI: PCI Interrupt Link [LNKG] (IRQs 3 4 5 6 7 9 10 11 12 14 15) *0, disabled. [ 8.100275] ACPI: PCI Interrupt Link [LNKH] (IRQs 3 4 5 6 7 9 *10 11 12 14 15) [ 8.101225] xen/balloon: Initialising balloon driver. [ 8.184758] xen-balloon: Initialising balloon driver. [ 8.185074] xen/balloon: Xen selfballooning driver disabled for domain0. [ 8.185368] vgaarb: device added: PCI:0000:0a:00.0,decodes=io+mem,owns=io+mem,locks=none [ 8.185590] vgaarb: loaded [ 8.185719] vgaarb: bridge control possible 0000:0a:00.0 [ 8.186090] SCSI subsystem initialized [ 8.186225] ACPI: bus type scsi registered [ 8.186551] libata version 3.00 loaded. [ 8.186778] ACPI: bus type usb registered [ 8.187038] usbcore: registered new interface driver usbfs [ 8.187257] usbcore: registered new interface driver hub [ 8.187492] usbcore: registered new device driver usb [ 8.187844] pps_core: LinuxPPS API ver. 1 registered [ 8.187983] pps_core: Software ver. 5.3.6 - Copyright 2005-2007 Rodolfo Giometti [ 8.188268] PTP clock support registered [ 8.188684] Advanced Linux Sound Architecture Driver Version 1.0.25. [ 8.188828] PCI: Using ACPI for IRQ routing [ 8.201594] PCI: Discovered peer bus ff [ 8.201727] PCI: root bus ff: using default resources [ 8.201729] PCI: Probing PCI hardware (bus ff) [ 8.201802] PCI host bridge to bus 0000:ff [ 8.201939] pci_bus 0000:ff: root bus resource [io 0x0000-0xffff] [ 8.202082] pci_bus 0000:ff: root bus resource [mem 0x00000000-0xfffffffff] [ 8.202226] pci_bus 0000:ff: No busn resource found for root bus, will use [bus ff-ff] [ 8.202464] pci_bus 0000:ff: busn_res: [bus ff] is inserted under domain [bus 00-ff] [ 8.202478] pci 0000:ff:00.0: [8086:2c50] type 00 class 0x060000 [ 8.202533] pci 0000:ff:00.1: [8086:2c81] type 00 class 0x060000 [ 8.202591] pci 0000:ff:02.0: [8086:2c90] type 00 class 0x060000 [ 8.202641] pci 0000:ff:02.1: [8086:2c91] type 00 class 0x060000 [ 8.202698] pci 0000:ff:03.0: [8086:2c98] type 00 class 0x060000 [ 8.202748] pci 0000:ff:03.1: [8086:2c99] type 00 class 0x060000 [ 8.202797] pci 0000:ff:03.2: [8086:2c9a] type 00 class 0x060000 [ 8.202848] pci 0000:ff:03.4: [8086:2c9c] type 00 class 0x060000 [ 8.202901] pci 0000:ff:04.0: [8086:2ca0] type 00 class 0x060000 [ 8.202951] pci 0000:ff:04.1: [8086:2ca1] type 00 class 0x060000 [ 8.203001] pci 0000:ff:04.2: [8086:2ca2] type 00 class 0x060000 [ 8.203050] pci 0000:ff:04.3: [8086:2ca3] type 00 class 0x060000 [ 8.203105] pci 0000:ff:05.0: [8086:2ca8] type 00 class 0x060000 [ 8.203155] pci 0000:ff:05.1: [8086:2ca9] type 00 class 0x060000 [ 8.203205] pci 0000:ff:05.2: [8086:2caa] type 00 class 0x060000 [ 8.203254] pci 0000:ff:05.3: [8086:2cab] type 00 class 0x060000 [ 8.203337] pci_bus 0000:ff: busn_res: [bus ff] end is updated to ff [ 8.204457] PCI: pci_cache_line_size set to 64 bytes [ 8.204685] e820: reserve RAM buffer [mem 0x00099000-0x0009ffff] [ 8.204687] e820: reserve RAM buffer [mem 0x9dbe4000-0x9fffffff] [ 8.204689] e820: reserve RAM buffer [mem 0x5e2889000-0x5e3ffffff] [ 8.205242] NetLabel: Initializing [ 8.205375] NetLabel: domain hash size = 128 [ 8.205509] NetLabel: protocols = UNLABELED CIPSOv4 [ 8.205654] NetLabel: unlabeled traffic allowed by default [ 8.205820] cfg80211: Calling CRDA to update world regulatory domain [ 8.206051] Switching to clocksource xen [ 8.211838] pnp: PnP ACPI init [ 8.211980] ACPI: bus type pnp registered [ 8.212403] pnp 00:00: [bus 00-fe] [ 8.212406] pnp 00:00: [io 0x0cf8-0x0cff] [ 8.212408] pnp 00:00: [io 0x0000-0x0cf7 window] [ 8.212410] pnp 00:00: [io 0x0d00-0xffff window] [ 8.212412] pnp 00:00: [mem 0x000a0000-0x000bffff window] [ 8.212414] pnp 00:00: [mem 0x000c4000-0x000cbfff window] [ 8.212415] pnp 00:00: [mem 0xfed40000-0xfedfffff window] [ 8.212417] pnp 00:00: [mem 0xb0000000-0xfdffffff window] [ 8.212419] pnp 00:00: [mem 0x00000000 window] [ 8.212560] pnp 00:00: Plug and Play ACPI device, IDs PNP0a08 PNP0a03 (active) [ 8.212571] pnp 00:01: [mem 0xfec00000-0xfecfffff] [ 8.212641] pnp 00:01: Plug and Play ACPI device, IDs PNP0003 (active) [ 8.212838] pnp 00:02: [io 0x0000-0x000f] [ 8.212840] pnp 00:02: [io 0x0081-0x0083] [ 8.212841] pnp 00:02: [io 0x0087] [ 8.212843] pnp 00:02: [io 0x0089-0x008b] [ 8.212844] pnp 00:02: [io 0x008f] [ 8.212846] pnp 00:02: [io 0x00c0-0x00df] [ 8.212848] pnp 00:02: [dma 4] [ 8.212944] pnp 00:02: Plug and Play ACPI device, IDs PNP0200 (active) [ 8.212955] pnp 00:03: [io 0x0070-0x0071] [ 8.212956] pnp 00:03: [io 0x0074-0x0077] [ 8.212959] xen: registering gsi 8 triggering 1 polarity 0 [ 8.212968] pnp 00:03: [irq 8] [ 8.213063] pnp 00:03: Plug and Play ACPI device, IDs PNP0b00 (active) [ 8.213075] pnp 00:04: [io 0x00f0] [ 8.213077] xen: registering gsi 13 triggering 1 polarity 0 [ 8.213082] pnp 00:04: [irq 13] [ 8.213177] pnp 00:04: Plug and Play ACPI device, IDs PNP0c04 (active) [ 8.213189] pnp 00:05: [io 0x0061] [ 8.213295] pnp 00:05: Plug and Play ACPI device, IDs PNP0800 (active) [ 8.213335] pnp 00:06: [mem 0xfed00000-0xfed003ff] [ 8.213434] pnp 00:06: Plug and Play ACPI device, IDs PNP0103 (active) [ 8.213448] pnp 00:07: [io 0x0500-0x057f] [ 8.213450] pnp 00:07: [io 0x0600-0x061f] [ 8.213451] pnp 00:07: [io 0x0880-0x0883] [ 8.213453] pnp 00:07: [io 0x0ca4-0x0ca5] [ 8.213454] pnp 00:07: [io 0x0400-0x047f] [ 8.213456] pnp 00:07: [io 0x0092] [ 8.213457] pnp 00:07: [io 0x0010-0x001f] [ 8.213459] pnp 00:07: [io 0x0072-0x0073] [ 8.213460] pnp 00:07: [io 0x0080] [ 8.213462] pnp 00:07: [io 0x0084-0x0086] [ 8.213463] pnp 00:07: [io 0x0088] [ 8.213467] pnp 00:07: [io 0x008c-0x008e] [ 8.213469] pnp 00:07: [io 0x0090-0x009f] [ 8.213471] pnp 00:07: [io 0x0800-0x081f] [ 8.213472] pnp 00:07: [io 0x0ca2-0x0ca3] [ 8.213474] pnp 00:07: [mem 0xfed1c000-0xfed3fffe] [ 8.213475] pnp 00:07: [mem 0xff000000-0xffffffff] [ 8.213477] pnp 00:07: [mem 0xfee00000-0xfeefffff] [ 8.213478] pnp 00:07: [mem 0xfe900000-0xfe90001f] [ 8.213480] pnp 00:07: [mem 0xfea00000-0xfea0001f] [ 8.213482] pnp 00:07: [mem 0xfed1b000-0xfed1bfff] [ 8.213483] pnp 00:07: [mem 0xfed14000-0xfed17ffe] [ 8.213485] pnp 00:07: [mem 0xfed18000-0xfed18ffe] [ 8.213486] pnp 00:07: [mem 0xfed19000-0xfed19ffe] [ 8.213644] system 00:07: [io 0x0500-0x057f] has been reserved [ 8.213787] system 00:07: [io 0x0600-0x061f] has been reserved [ 8.213928] system 00:07: [io 0x0880-0x0883] has been reserved [ 8.214070] system 00:07: [io 0x0ca4-0x0ca5] has been reserved [ 8.214213] system 00:07: [io 0x0400-0x047f] has been reserved [ 8.214369] system 00:07: [io 0x0800-0x081f] has been reserved [ 8.214509] system 00:07: [io 0x0ca2-0x0ca3] has been reserved [ 8.214650] system 00:07: [mem 0xfed1c000-0xfed3fffe] could not be reserved [ 8.214794] system 00:07: [mem 0xff000000-0xffffffff] could not be reserved [ 8.214937] system 00:07: [mem 0xfee00000-0xfeefffff] could not be reserved [ 8.215081] system 00:07: [mem 0xfe900000-0xfe90001f] has been reserved [ 8.215224] system 00:07: [mem 0xfea00000-0xfea0001f] has been reserved [ 8.215375] system 00:07: [mem 0xfed1b000-0xfed1bfff] has been reserved [ 8.215518] system 00:07: [mem 0xfed14000-0xfed17ffe] has been reserved [ 8.215660] system 00:07: [mem 0xfed18000-0xfed18ffe] has been reserved [ 8.215803] system 00:07: [mem 0xfed19000-0xfed19ffe] has been reserved [ 8.215949] system 00:07: Plug and Play ACPI device, IDs PNP0c02 (active) [ 8.216077] pnp 00:08: [io 0x03f8-0x03ff] [ 8.216079] xen: registering gsi 4 triggering 1 polarity 0 [ 8.216085] pnp 00:08: [irq 4] [ 8.216215] pnp 00:08: Plug and Play ACPI device, IDs PNP0501 (active) [ 8.216361] pnp 00:09: [io 0x02f8-0x02ff] [ 8.216364] xen: registering gsi 3 triggering 1 polarity 0 [ 8.216369] pnp 00:09: [irq 3] [ 8.216496] pnp 00:09: Plug and Play ACPI device, IDs PNP0501 (active) [ 8.216539] pnp 00:0a: [io 0x0ca2] [ 8.216540] pnp 00:0a: [io 0x0ca3] [ 8.216640] pnp 00:0a: Plug and Play ACPI device, IDs IPI0001 (active) [ 8.216686] pnp: PnP ACPI: found 11 devices [ 8.216823] ACPI: ACPI bus type pnp unregistered [ 8.217028] pciback 0000:0a:00.0: seizing device [ 8.217169] pciback 0000:0d:08.0: seizing device [ 8.217322] pciback 0000:0d:09.0: seizing device [ 8.227141] PM-Timer failed consistency check (0x0xffffff) - aborting. [ 8.227308] pci 0000:05:00.0: no compatible bridge window for [mem 0xfffc0000-0xffffffff pref] [ 8.227541] pci 0000:06:00.0: no compatible bridge window for [mem 0xffc00000-0xffffffff pref] [ 8.227772] pci 0000:06:00.1: no compatible bridge window for [mem 0xffc00000-0xffffffff pref] [ 8.227996] pciback 0000:0a:00.0: no compatible bridge window for [mem 0xffff0000-0xffffffff pref] [ 8.228384] pci 0000:00:1c.0: BAR 15: assigned [mem 0xba800000-0xbaffffff pref] [ 8.228624] pci 0000:00:03.0: BAR 15: assigned [mem 0xb9900000-0xb99fffff pref] [ 8.228845] pci 0000:01:00.0: BAR 15: assigned [mem 0xb9900000-0xb99fffff pref] [ 8.229065] pci 0000:02:04.0: BAR 15: assigned [mem 0xb9900000-0xb99fffff pref] [ 8.229285] pci 0000:02:02.0: PCI bridge to [bus 03] [ 8.229450] pci 0000:02:03.0: PCI bridge to [bus 04] [ 8.229608] pci 0000:05:00.0: BAR 6: assigned [mem 0xb9900000-0xb993ffff pref] [ 8.229829] pci 0000:02:04.0: PCI bridge to [bus 05] [ 8.229968] pci 0000:02:04.0: bridge window [io 0x3000-0x3fff] [ 8.230116] pci 0000:02:04.0: bridge window [mem 0xba600000-0xba6fffff] [ 8.230264] pci 0000:02:04.0: bridge window [mem 0xb9900000-0xb99fffff pref] [ 8.230498] pci 0000:01:00.0: PCI bridge to [bus 02-05] [ 8.230638] pci 0000:01:00.0: bridge window [io 0x3000-0x3fff] [ 8.230787] pci 0000:01:00.0: bridge window [mem 0xba600000-0xba6fffff] [ 8.230936] pci 0000:01:00.0: bridge window [mem 0xb9900000-0xb99fffff pref] [ 8.231163] pci 0000:00:03.0: PCI bridge to [bus 01-05] [ 8.231311] pci 0000:00:03.0: bridge window [io 0x3000-0x3fff] [ 8.231458] pci 0000:00:03.0: bridge window [mem 0xba600000-0xba6fffff] [ 8.231604] pci 0000:00:03.0: bridge window [mem 0xb9900000-0xb99fffff pref] [ 8.231832] pci 0000:06:00.0: BAR 6: assigned [mem 0xba800000-0xbabfffff pref] [ 8.232054] pci 0000:06:00.1: BAR 6: assigned [mem 0xbac00000-0xbaffffff pref] [ 8.232272] pci 0000:00:1c.0: PCI bridge to [bus 06-08] [ 8.232419] pci 0000:00:1c.0: bridge window [io 0x2000-0x2fff] [ 8.232566] pci 0000:00:1c.0: bridge window [mem 0xb9c00000-0xba4fffff] [ 8.232713] pci 0000:00:1c.0: bridge window [mem 0xba800000-0xbaffffff pref] [ 8.232940] pci 0000:00:1c.4: PCI bridge to [bus 09] [ 8.233079] pci 0000:00:1c.4: bridge window [io 0x1000-0x1fff] [ 8.233225] pci 0000:00:1c.4: bridge window [mem 0xba500000-0xba5fffff] [ 8.233389] pciback 0000:0a:00.0: BAR 6: assigned [mem 0xb9810000-0xb981ffff pref] [ 8.234875] pci 0000:00:1c.6: PCI bridge to [bus 0a] [ 8.235020] pci 0000:00:1c.6: bridge window [mem 0xb9000000-0xb98fffff] [ 8.235167] pci 0000:00:1c.6: bridge window [mem 0xb8000000-0xb8ffffff 64bit pref] [ 8.235403] pci 0000:00:1c.7: PCI bridge to [bus 0b] [ 8.235555] pci 0000:0c:00.0: PCI bridge to [bus 0d] [ 8.235702] pci 0000:0c:00.0: bridge window [mem 0xb0000000-0xb7ffffff pref] [ 8.235926] pci 0000:00:1e.0: PCI bridge to [bus 0c-0d] [ 8.236072] pci 0000:00:1e.0: bridge window [mem 0xb0000000-0xb7ffffff 64bit pref] [ 8.236311] xen: registering gsi 16 triggering 0 polarity 1 [ 8.236325] xen: --> pirq=16 -> irq=16 (gsi=16) [ 8.236363] xen: registering gsi 16 triggering 0 polarity 1 [ 8.236364] Already setup the GSI :16 [ 8.236502] xen: registering gsi 16 triggering 0 polarity 1 [ 8.236503] Already setup the GSI :16 [ 8.236640] xen: registering gsi 18 triggering 0 polarity 1 [ 8.236645] xen: --> pirq=18 -> irq=18 (gsi=18) [ 8.236655] xen: registering gsi 19 triggering 0 polarity 1 [ 8.236659] xen: --> pirq=19 -> irq=19 (gsi=19) [ 8.236671] pci 0000:00:1e.0: setting latency timer to 64 [ 8.236683] pci 0000:0c:00.0: setting latency timer to 64 [ 8.236688] pci_bus 0000:00: resource 4 [io 0x0000-0x0cf7] [ 8.236689] pci_bus 0000:00: resource 5 [io 0x0d00-0xffff] [ 8.236691] pci_bus 0000:00: resource 6 [mem 0x000a0000-0x000bffff] [ 8.236693] pci_bus 0000:00: resource 7 [mem 0xfed40000-0xfedfffff] [ 8.236695] pci_bus 0000:00: resource 8 [mem 0xb0000000-0xfdffffff] [ 8.236697] pci_bus 0000:01: resource 0 [io 0x3000-0x3fff] [ 8.236698] pci_bus 0000:01: resource 1 [mem 0xba600000-0xba6fffff] [ 8.236700] pci_bus 0000:01: resource 2 [mem 0xb9900000-0xb99fffff pref] [ 8.236702] pci_bus 0000:02: resource 0 [io 0x3000-0x3fff] [ 8.236704] pci_bus 0000:02: resource 1 [mem 0xba600000-0xba6fffff] [ 8.236705] pci_bus 0000:02: resource 2 [mem 0xb9900000-0xb99fffff pref] [ 8.236707] pci_bus 0000:05: resource 0 [io 0x3000-0x3fff] [ 8.236709] pci_bus 0000:05: resource 1 [mem 0xba600000-0xba6fffff] [ 8.236711] pci_bus 0000:05: resource 2 [mem 0xb9900000-0xb99fffff pref] [ 8.236713] pci_bus 0000:06: resource 0 [io 0x2000-0x2fff] [ 8.236714] pci_bus 0000:06: resource 1 [mem 0xb9c00000-0xba4fffff] [ 8.236716] pci_bus 0000:06: resource 2 [mem 0xba800000-0xbaffffff pref] [ 8.236718] pci_bus 0000:09: resource 0 [io 0x1000-0x1fff] [ 8.236720] pci_bus 0000:09: resource 1 [mem 0xba500000-0xba5fffff] [ 8.236722] pci_bus 0000:0a: resource 1 [mem 0xb9000000-0xb98fffff] [ 8.236723] pci_bus 0000:0a: resource 2 [mem 0xb8000000-0xb8ffffff 64bit pref] [ 8.236725] pci_bus 0000:0c: resource 2 [mem 0xb0000000-0xb7ffffff 64bit pref] [ 8.236727] pci_bus 0000:0c: resource 4 [io 0x0000-0x0cf7] [ 8.236729] pci_bus 0000:0c: resource 5 [io 0x0d00-0xffff] [ 8.236731] pci_bus 0000:0c: resource 6 [mem 0x000a0000-0x000bffff] [ 8.236732] pci_bus 0000:0c: resource 7 [mem 0xfed40000-0xfedfffff] [ 8.236734] pci_bus 0000:0c: resource 8 [mem 0xb0000000-0xfdffffff] [ 8.236736] pci_bus 0000:0d: resource 2 [mem 0xb0000000-0xb7ffffff pref] [ 8.236738] pci_bus 0000:ff: resource 4 [io 0x0000-0xffff] [ 8.236740] pci_bus 0000:ff: resource 5 [mem 0x00000000-0xfffffffff] [ 8.236763] NET: Registered protocol family 2 [ 8.238065] TCP established hash table entries: 524288 (order: 11, 8388608 bytes) [ 8.240818] TCP bind hash table entries: 65536 (order: 8, 1048576 bytes) [ 8.241264] TCP: Hash tables configured (established 524288 bind 65536) [ 8.241438] TCP: reno registered [ 8.241656] UDP hash table entries: 16384 (order: 7, 524288 bytes) [ 8.242075] UDP-Lite hash table entries: 16384 (order: 7, 524288 bytes) [ 8.242504] NET: Registered protocol family 1 [ 8.242740] RPC: Registered named UNIX socket transport module. [ 8.242881] RPC: Registered udp transport module. [ 8.243016] RPC: Registered tcp transport module. [ 8.243152] RPC: Registered tcp NFSv4.1 backchannel transport module. [ 8.243385] xen: registering gsi 21 triggering 0 polarity 1 [ 8.243401] xen: --> pirq=21 -> irq=21 (gsi=21) [ 8.243570] xen: registering gsi 23 triggering 0 polarity 1 [ 8.243576] xen: --> pirq=23 -> irq=23 (gsi=23) [ 8.243767] pciback 0000:0a:00.0: Boot video device [ 8.243820] PCI: CLS 64 bytes, default 64 [ 8.243866] Trying to unpack rootfs image as initramfs... [ 8.253804] Freeing initrd memory: 9908k freed [ 8.256693] microcode: CPU0 sig=0x106e5, pf=0x2, revision=0x4 [ 8.256848] microcode: CPU1 sig=0x106e5, pf=0x2, revision=0x4 [ 8.257058] microcode: Microcode Update Driver: v2.00 , Peter Oruba [ 8.257666] audit: initializing netlink socket (disabled) [ 8.257818] type=2000 audit(1347407764.232:1): initialized [ 8.276545] HugeTLB registered 2 MB page size, pre-allocated 0 pages [ 8.281167] VFS: Disk quotas dquot_6.5.2 [ 8.281421] Dquot-cache hash table entries: 512 (order 0, 4096 bytes) [ 8.283066] NFS: Registering the id_resolver key type [ 8.283211] Key type id_resolver registered [ 8.283357] Key type id_legacy registered [ 8.283567] SGI XFS with ACLs, security attributes, realtime, large block/inode numbers, no debug enabled [ 8.284744] msgmni has been set to 3129 [ 8.284989] SELinux: Registering netfilter hooks [ 8.286777] modprobe (799) used greatest stack depth: 5320 bytes left [ 8.294555] Block layer SCSI generic (bsg) driver version 0.4 loaded (major 251) [ 8.294780] io scheduler noop registered [ 8.294914] io scheduler deadline registered [ 8.295055] io scheduler cfq registered (default) [ 8.296316] pci_hotplug: PCI Hot Plug PCI Core version: 0.5 [ 8.296579] intel_idle: MWAIT substates: 0x1120 [ 8.296590] intel_idle: v0.4 model 0x1E [ 8.296592] intel_idle: lapic_timer_reliable_states 0x2 [ 8.296615] intel_idle: intel_idle yielding to none [ 8.296810] input: Sleep Button as /devices/LNXSYSTM:00/device:00/PNP0C0E:00/input/input0 [ 8.297037] ACPI: Sleep Button [SLPB] [ 8.297254] input: Power Button as /devices/LNXSYSTM:00/LNXPWRBN:00/input/input1 [ 8.297490] ACPI: Power Button [PWRF] [ 8.297881] ACPI: Requesting acpi_cpufreq [ 8.299639] modprobe (826) used greatest stack depth: 5304 bytes left [ 8.299791] Monitor-Mwait will be used to enter C-1 state [ 8.299846] Monitor-Mwait will be used to enter C-3 state [ 8.302929] Event-channel device installed. [ 8.303179] xen: registering gsi 17 triggering 0 polarity 1 [ 8.303195] xen: --> pirq=17 -> irq=17 (gsi=17) [ 8.324372] xen: registering gsi 16 triggering 0 polarity 1 [ 8.324377] Already setup the GSI :16 [ 8.346384] xen: registering gsi 17 triggering 0 polarity 1 [ 8.346388] Already setup the GSI :17 [ 8.368397] xen-pciback: backend is vpci [ 8.369297] Serial: 8250/16550 driver, 4 ports, IRQ sharing enabled [ 8.634432] serial8250: ttyS0 at I/O 0x3f8 (irq = 4) is a 16550A [ 8.899430] serial8250: ttyS1 at I/O 0x2f8 (irq = 3) is a 16550A [ 8.920793] 00:08: ttyS0 at I/O 0x3f8 (irq = 4) is a 16550A [ 8.941879] 00:09: ttyS1 at I/O 0x2f8 (irq = 3) is a 16550A [ 8.942386] hpet_acpi_add: no address or irqs in _CRS [ 8.942651] Non-volatile memory driver v1.3 [ 8.942770] Linux agpgart interface v0.103 [ 8.943179] [drm] Initialized drm 1.1.0 20060810 [ 8.946254] brd: module loaded [ 8.947815] loop: module loaded [ 8.948406] ahci 0000:00:1f.2: version 3.0 [ 8.948416] xen: registering gsi 18 triggering 0 polarity 1 [ 8.948418] Already setup the GSI :18 [ 8.959344] ahci 0000:00:1f.2: AHCI 0001.0300 32 slots 6 ports 3 Gbps 0x3f impl SATA mode [ 8.959545] ahci 0000:00:1f.2: flags: 64bit ncq sntf pm led clo pio slum part sxs apst [ 8.959736] ahci 0000:00:1f.2: setting latency timer to 64 [ 8.961433] scsi0 : ahci [ 8.961726] scsi1 : ahci [ 8.962008] scsi2 : ahci [ 8.962295] scsi3 : ahci [ 8.962576] scsi4 : ahci [ 8.962856] scsi5 : ahci [ 8.963098] ata1: SATA max UDMA/133 abar m2048@0xba720000 port 0xba720100 irq 18 [ 8.963297] ata2: SATA max UDMA/133 abar m2048@0xba720000 port 0xba720180 irq 18 [ 8.963484] ata3: SATA max UDMA/133 abar m2048@0xba720000 port 0xba720200 irq 18 [ 8.963669] ata4: SATA max UDMA/133 abar m2048@0xba720000 port 0xba720280 irq 18 [ 8.963853] ata5: SATA max UDMA/133 abar m2048@0xba720000 port 0xba720300 irq 18 [ 8.964038] ata6: SATA max UDMA/133 abar m2048@0xba720000 port 0xba720380 irq 18 [ 8.964820] e100: Intel(R) PRO/100 Network Driver, 3.5.24-k2-NAPI [ 8.964945] e100: Copyright(c) 1999-2006 Intel Corporation [ 8.965137] e1000: Intel(R) PRO/1000 Network Driver - version 7.3.21-k8-NAPI [ 8.965265] e1000: Copyright (c) 1999-2006 Intel Corporation. [ 8.965478] e1000e: Intel(R) PRO/1000 Network Driver - 2.0.0-k [ 8.965602] e1000e: Copyright(c) 1999 - 2012 Intel Corporation. [ 8.965738] xen: registering gsi 16 triggering 0 polarity 1 [ 8.965740] Already setup the GSI :16 [ 8.965862] e1000e 0000:00:19.0: setting latency timer to 64 [ 8.965950] e1000e 0000:00:19.0: Interrupt Throttling Rate (ints/sec) set to dynamic conservative mode [ 9.207156] e1000e 0000:00:19.0: eth0: (PCI Express:2.5GT/s:Width x1) 00:1e:67:0f:1a:e7 [ 9.207358] e1000e 0000:00:19.0: eth0: Intel(R) PRO/1000 Network Connection [ 9.207519] e1000e 0000:00:19.0: eth0: MAC: 9, PHY: 9, PBA No: 0310FF-0FF [ 9.207655] e1000e 0000:09:00.0: Disabling ASPM L0s L1 [ 9.207784] xen: registering gsi 16 triggering 0 polarity 1 [ 9.207786] Already setup the GSI :16 [ 9.208043] e1000e 0000:09:00.0: Interrupt Throttling Rate (ints/sec) set to dynamic conservative mode [ 9.268326] ata2: SATA link down (SStatus 0 SControl 300) [ 9.268488] ata1: SATA link down (SStatus 0 SControl 300) [ 9.269330] ata4: SATA link up 1.5 Gbps (SStatus 113 SControl 300) [ 9.269489] ata6: SATA link down (SStatus 0 SControl 300) [ 9.270324] ata5: SATA link down (SStatus 0 SControl 300) [ 9.271322] ata3: SATA link down (SStatus 0 SControl 300) [ 9.288740] ata4.00: ATA-7: HDS724040KLSA80, KFAOA46A, max UDMA/133 [ 9.288880] ata4.00: 781422768 sectors, multi 0: LBA48 [ 9.293215] ata4.00: configured for UDMA/133 [ 9.293467] scsi 3:0:0:0: Direct-Access ATA HDS724040KLSA80 KFAO PQ: 0 ANSI: 5 [ 9.293938] sd 3:0:0:0: [sda] 781422768 512-byte logical blocks: (400 GB/372 GiB) [ 9.294020] sd 3:0:0:0: Attached scsi generic sg0 type 0 [ 9.294384] sd 3:0:0:0: [sda] Write Protect is off [ 9.294506] sd 3:0:0:0: [sda] Mode Sense: 00 3a 00 00 [ 9.294549] sd 3:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA [ 9.310067] sda: sda1 sda2 [ 9.310627] sd 3:0:0:0: [sda] Attached SCSI disk [ 9.313819] e1000e 0000:09:00.0: eth1: (PCI Express:2.5GT/s:Width x1) 00:1e:67:0f:1a:e6 [ 9.314009] e1000e 0000:09:00.0: eth1: Intel(R) PRO/1000 Network Connection [ 9.314219] e1000e 0000:09:00.0: eth1: MAC: 3, PHY: 8, PBA No: 1010FF-0FF [ 9.314431] igb: Intel(R) Gigabit Ethernet Network Driver - version 4.0.1-k [ 9.314558] igb: Copyright (c) 2007-2012 Intel Corporation. [ 9.314697] xen: registering gsi 16 triggering 0 polarity 1 [ 9.314699] Already setup the GSI :16 [ 9.476748] igb 0000:06:00.0: added PHC on eth2 [ 9.476869] igb 0000:06:00.0: Intel(R) Gigabit Ethernet Network Connection [ 9.476995] igb 0000:06:00.0: eth2: (PCIe:2.5Gb/s:Width x4) 90:e2:ba:00:9f:c4 [ 9.477202] igb 0000:06:00.0: eth2: PBA No: E43709-006 [ 9.477330] igb 0000:06:00.0: Using legacy interrupts. 1 rx queue(s), 1 tx queue(s) [ 9.477527] xen: registering gsi 17 triggering 0 polarity 1 [ 9.477530] Already setup the GSI :17 [ 9.639745] igb 0000:06:00.1: added PHC on eth3 [ 9.639865] igb 0000:06:00.1: Intel(R) Gigabit Ethernet Network Connection [ 9.639992] igb 0000:06:00.1: eth3: (PCIe:2.5Gb/s:Width x4) 90:e2:ba:00:9f:c5 [ 9.640199] igb 0000:06:00.1: eth3: PBA No: E43709-006 [ 9.640326] igb 0000:06:00.1: Using legacy interrupts. 1 rx queue(s), 1 tx queue(s) [ 9.640584] igbvf: Intel(R) Gigabit Virtual Function Network Driver - version 2.0.1-k [ 9.640773] igbvf: Copyright (c) 2009 - 2012 Intel Corporation. [ 9.640965] ixgbe: Intel(R) 10 Gigabit PCI Express Network Driver - version 3.9.15-k [ 9.641153] ixgbe: Copyright (c) 1999-2012 Intel Corporation. [ 9.641364] ixgb: Intel(R) PRO/10GbE Network Driver - version 1.0.135-k2-NAPI [ 9.641492] ixgb: Copyright (c) 1999-2008 Intel Corporation. [ 9.641688] Initialising Xen virtual ethernet driver. [ 9.642096] ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver [ 9.642222] ehci_hcd: block sizes: qh 104 qtd 96 itd 192 sitd 96 [ 9.642240] xen: registering gsi 21 triggering 0 polarity 1 [ 9.642243] Already setup the GSI :21 [ 9.642385] ehci_hcd 0000:00:1a.0: setting latency timer to 64 [ 9.642390] ehci_hcd 0000:00:1a.0: EHCI Host Controller [ 9.642588] ehci_hcd 0000:00:1a.0: new USB bus registered, assigned bus number 1 [ 9.642780] ehci_hcd 0000:00:1a.0: reset hcs_params 0x200002 dbg=2 cc=0 pcc=0 ordered !ppc ports=2 [ 9.642784] ehci_hcd 0000:00:1a.0: reset hcc_params 36881 caching frame 1024 64 bit addr [ 9.642811] ehci_hcd 0000:00:1a.0: support lpm [ 9.642818] ehci_hcd 0000:00:1a.0: reset command 0080012 (park)=0 ithresh=8 Periodic period=1024 Reset HALT [ 9.646736] ehci_hcd 0000:00:1a.0: debug port 2 [ 9.646864] ehci_hcd 0000:00:1a.0: cache line size of 64 is not supported [ 9.646866] ehci_hcd 0000:00:1a.0: supports USB remote wakeup [ 9.646883] ehci_hcd 0000:00:1a.0: irq 21, io mem 0xba722000 [ 9.647009] ehci_hcd 0000:00:1a.0: init command 0010001 (park)=0 ithresh=1 period=1024 RUN [ 9.652306] ehci_hcd 0000:00:1a.0: USB 2.0 started, EHCI 1.00 [ 9.652475] usb usb1: default language 0x0409 [ 9.652480] usb usb1: udev 1, busnum 1, minor = 0 [ 9.652483] usb usb1: New USB device found, idVendor=1d6b, idProduct=0002 [ 9.652609] usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1 [ 9.652793] usb usb1: Product: EHCI Host Controller [ 9.652912] usb usb1: Manufacturer: Linux 3.6.0-rc4+ ehci_hcd [ 9.653034] usb usb1: SerialNumber: 0000:00:1a.0 [ 9.653253] usb usb1: usb_probe_device [ 9.653256] usb usb1: configuration #1 chosen from 1 choice [ 9.653263] usb usb1: adding 1-0:1.0 (config #1, interface 0) [ 9.653337] hub 1-0:1.0: usb_probe_interface [ 9.653339] hub 1-0:1.0: usb_probe_interface - got id [ 9.653341] hub 1-0:1.0: USB hub found [ 9.653461] hub 1-0:1.0: 2 ports detected [ 9.653579] hub 1-0:1.0: standalone hub [ 9.653581] hub 1-0:1.0: no power switching (usb 1.0) [ 9.653582] hub 1-0:1.0: individual port over-current protection [ 9.653584] hub 1-0:1.0: power on to power good time: 20ms [ 9.653587] hub 1-0:1.0: local power source is good [ 9.653589] hub 1-0:1.0: trying to enable port power on non-switchable hub [ 9.653643] xen: registering gsi 23 triggering 0 polarity 1 [ 9.653646] Already setup the GSI :23 [ 9.653779] ehci_hcd 0000:00:1d.0: setting latency timer to 64 [ 9.653783] ehci_hcd 0000:00:1d.0: EHCI Host Controller [ 9.653984] ehci_hcd 0000:00:1d.0: new USB bus registered, assigned bus number 2 [ 9.655049] ehci_hcd 0000:00:1d.0: reset hcs_params 0x200002 dbg=2 cc=0 pcc=0 ordered !ppc ports=2 [ 9.655052] ehci_hcd 0000:00:1d.0: reset hcc_params 36881 caching frame 1024 64 bit addr [ 9.655079] ehci_hcd 0000:00:1d.0: support lpm [ 9.655086] ehci_hcd 0000:00:1d.0: reset command 0080012 (park)=0 ithresh=8 Periodic period=1024 Reset HALT [ 9.658994] ehci_hcd 0000:00:1d.0: debug port 2 [ 9.659122] ehci_hcd 0000:00:1d.0: cache line size of 64 is not supported [ 9.659124] ehci_hcd 0000:00:1d.0: supports USB remote wakeup [ 9.659142] ehci_hcd 0000:00:1d.0: irq 23, io mem 0xba721000 [ 9.659267] ehci_hcd 0000:00:1d.0: init command 0010001 (park)=0 ithresh=1 period=1024 RUN [ 9.664307] ehci_hcd 0000:00:1d.0: USB 2.0 started, EHCI 1.00 [ 9.664473] usb usb2: default language 0x0409 [ 9.664478] usb usb2: udev 1, busnum 2, minor = 128 [ 9.664480] usb usb2: New USB device found, idVendor=1d6b, idProduct=0002 [ 9.664606] usb usb2: New USB device strings: Mfr=3, Product=2, SerialNumber=1 [ 9.664790] usb usb2: Product: EHCI Host Controller [ 9.664909] usb usb2: Manufacturer: Linux 3.6.0-rc4+ ehci_hcd [ 9.665031] usb usb2: SerialNumber: 0000:00:1d.0 [ 9.665245] usb usb2: usb_probe_device [ 9.665247] usb usb2: configuration #1 chosen from 1 choice [ 9.665253] usb usb2: adding 2-0:1.0 (config #1, interface 0) [ 9.665330] hub 2-0:1.0: usb_probe_interface [ 9.665332] hub 2-0:1.0: usb_probe_interface - got id [ 9.665334] hub 2-0:1.0: USB hub found [ 9.665453] hub 2-0:1.0: 2 ports detected [ 9.665571] hub 2-0:1.0: standalone hub [ 9.665572] hub 2-0:1.0: no power switching (usb 1.0) [ 9.665574] hub 2-0:1.0: individual port over-current protection [ 9.665575] hub 2-0:1.0: power on to power good time: 20ms [ 9.665578] hub 2-0:1.0: local power source is good [ 9.665580] hub 2-0:1.0: trying to enable port power on non-switchable hub [ 9.665692] ohci_hcd: USB 1.1 'Open' Host Controller (OHCI) Driver [ 9.665817] ohci_hcd: block sizes: ed 80 td 96 [ 9.665891] uhci_hcd: USB Universal Host Controller Interface driver [ 9.666161] usbcore: registered new interface driver usblp [ 9.666293] Initializing USB Mass Storage driver... [ 9.666490] usbcore: registered new interface driver usb-storage [ 9.666615] USB Mass Storage support registered. [ 9.666808] usbcore: registered new interface driver libusual [ 9.667199] i8042: PNP: No PS/2 controller found. Probing ports directly. [ 9.668216] i8042: No controller found [ 9.668403] mousedev: PS/2 mouse device common for all mice [ 9.668852] rtc_cmos 00:03: RTC can wake from S4 [ 9.669150] rtc_cmos 00:03: rtc core: registered rtc_cmos as rtc0 [ 9.669324] rtc0: alarms up to one month, y3k, 114 bytes nvram [ 9.669527] xen: registering gsi 18 triggering 0 polarity 1 [ 9.669529] Already setup the GSI :18 [ 9.669934] device-mapper: ioctl: 4.23.0-ioctl (2012-07-25) initialised: dm-devel@redhat.com [ 9.670209] EFI Variables Facility v0.08 2004-May-17 [ 9.671662] usbcore: registered new interface driver usbhid [ 9.671786] usbhid: USB HID core driver [ 9.674147] Netfilter messages via NETLINK v0.30. [ 9.674277] nf_conntrack version 0.5.0 (16384 buckets, 65536 max) [ 9.674636] ctnetlink v0.93: registering with nfnetlink. [ 9.674876] ip_tables: (C) 2000-2006 Netfilter Core Team [ 9.675020] TCP: cubic registered [ 9.675133] Initializing XFRM netlink socket [ 9.675252] NET: Registered protocol family 17 [ 9.675412] Key type dns_resolver registered [ 9.676059] PM: Hibernation image not present or could not be loaded. [ 9.676069] registered taskstats version 1 [ 9.676823] Magic number: 12:177:959 [ 9.677007] console [netcon0] enabled [ 9.677122] netconsole: network logging started [ 9.677353] ALSA device list: [ 9.677467] No soundcards found. [ 9.677783] Freeing unused kernel memory: 728k freed [ 9.678013] Write protecting the kernel read-only data: 12288k [ 9.681039] Freeing unused kernel memory: 4k freed [ 9.681601] Freeing unused kernel memory: 1628k freed [ 9.717761] dracut: dracut-006-6.fc14 [ 9.737240] udev[1121]: starting version 161 [ 9.753319] ehci_hcd 0000:00:1a.0: GetStatus port:1 status 001803 0 ACK POWER sig=j CSC CONNECT [ 9.753325] hub 1-0:1.0: port 1: status 0501 change 0001 [ 9.765332] ehci_hcd 0000:00:1d.0: GetStatus port:1 status 001803 0 ACK POWER sig=j CSC CONNECT [ 9.765338] hub 2-0:1.0: port 1: status 0501 change 0001 [ 9.783489] dracut: Starting plymouth daemon [ 9.853421] hub 1-0:1.0: state 7 ports 2 chg 0002 evt 0000 [ 9.853431] hub 1-0:1.0: port 1, status 0501, change 0000, 480 Mb/s [ 9.904532] ehci_hcd 0000:00:1a.0: port 1 reset complete, port enabled [ 9.904539] ehci_hcd 0000:00:1a.0: GetStatus port:1 status 001005 0 ACK POWER sig=se0 PE CONNECT [ 9.955314] usb 1-1: new high-speed USB device number 2 using ehci_hcd [ 9.993881] blkid (1519) used greatest stack depth: 4976 bytes left [ 10.006529] ehci_hcd 0000:00:1a.0: port 1 reset complete, port enabled [ 10.006535] ehci_hcd 0000:00:1a.0: GetStatus port:1 status 001005 0 ACK POWER sig=se0 PE CONNECT [ 10.069433] ehci_hcd 0000:00:1a.0: set dev address 2 for port 1 [ 10.069441] ehci_hcd 0000:00:1a.0: LPM: no device attached [ 10.069678] usb 1-1: udev 2, busnum 1, minor = 1 [ 10.069683] usb 1-1: New USB device found, idVendor=8087, idProduct=0020 [ 10.069826] usb 1-1: New USB device strings: Mfr=0, Product=0, SerialNumber=0 [ 10.070042] usb 1-1: usb_probe_device [ 10.070046] usb 1-1: configuration #1 chosen from 1 choice [ 10.070198] usb 1-1: adding 1-1:1.0 (config #1, interface 0) [ 10.070309] hub 1-1:1.0: usb_probe_interface [ 10.070312] hub 1-1:1.0: usb_probe_interface - got id [ 10.070314] hub 1-1:1.0: USB hub found [ 10.070555] hub 1-1:1.0: 6 ports detected [ 10.070686] hub 1-1:1.0: standalone hub [ 10.070687] hub 1-1:1.0: individual port power switching [ 10.070689] hub 1-1:1.0: individual port over-current protection [ 10.070690] hub 1-1:1.0: Single TT [ 10.070692] hub 1-1:1.0: TT requires at most 8 FS bit times (666 ns) [ 10.070693] hub 1-1:1.0: Port indicators are supported [ 10.070695] hub 1-1:1.0: power on to power good time: 100ms [ 10.070922] hub 1-1:1.0: local power source is good [ 10.070926] hub 1-1:1.0: enabling power on all ports [ 10.071742] hub 2-0:1.0: state 7 ports 2 chg 0002 evt 0000 [ 10.071756] hub 2-0:1.0: port 1, status 0501, change 0000, 480 Mb/s [ 10.122528] ehci_hcd 0000:00:1d.0: port 1 reset complete, port enabled [ 10.122535] ehci_hcd 0000:00:1d.0: GetStatus port:1 status 001005 0 ACK POWER sig=se0 PE CONNECT [ 10.126354] dracut: Scanning devices sda2 for LVM logical volumes vg_xenserver01/LV_ROOT vg_xenserver01/LV_SWAP [ 10.139504] dracut: inactive '/dev/vg_xenserver01/LV_ROOT' [351.56 GiB] inherit [ 10.139862] dracut: inactive '/dev/vg_xenserver01/LV_SWAP' [20.53 GiB] inherit [ 10.172176] usb 1-1: link qh256-0001/ffff880002615c80 start 1 [1/0 us] [ 10.173315] usb 2-1: new high-speed USB device number 2 using ehci_hcd [ 10.188415] dracut: /dev/mapper/vg_xenserver01-LV_ROOT not set up by udev: Falling back to direct node creation. [ 10.188936] dracut: /dev/mapper/vg_xenserver01-LV_SWAP not set up by udev: Falling back to direct node creation. [ 10.189425] dracut: The link /dev/vg_xenserver01/LV_ROOT should had been created by udev but it was not found. Falling back to direct link creation. [ 10.189926] dracut: The link /dev/vg_xenserver01/LV_SWAP should had been created by udev but it was not found. Falling back to direct link creation. [ 10.224527] ehci_hcd 0000:00:1d.0: port 1 reset complete, port enabled [ 10.224533] ehci_hcd 0000:00:1d.0: GetStatus port:1 status 001005 0 ACK POWER sig=se0 PE CONNECT [ 10.287440] ehci_hcd 0000:00:1d.0: set dev address 2 for port 1 [ 10.287446] ehci_hcd 0000:00:1d.0: LPM: no device attached [ 10.287691] usb 2-1: udev 2, busnum 2, minor = 129 [ 10.287695] usb 2-1: New USB device found, idVendor=8087, idProduct=0020 [ 10.287833] usb 2-1: New USB device strings: Mfr=0, Product=0, SerialNumber=0 [ 10.289159] usb 2-1: usb_probe_device [ 10.289164] usb 2-1: configuration #1 chosen from 1 choice [ 10.289325] usb 2-1: adding 2-1:1.0 (config #1, interface 0) [ 10.291004] hub 2-1:1.0: usb_probe_interface [ 10.291008] hub 2-1:1.0: usb_probe_interface - got id [ 10.291011] hub 2-1:1.0: USB hub found [ 10.291189] hub 2-1:1.0: 6 ports detected [ 10.291330] hub 2-1:1.0: standalone hub [ 10.291332] hub 2-1:1.0: individual port power switching [ 10.291334] hub 2-1:1.0: individual port over-current protection [ 10.291336] hub 2-1:1.0: Single TT [ 10.291337] hub 2-1:1.0: TT requires at most 8 FS bit times (666 ns) [ 10.291339] hub 2-1:1.0: Port indicators are supported [ 10.291340] hub 2-1:1.0: power on to power good time: 100ms [ 10.291563] hub 2-1:1.0: local power source is good [ 10.291568] hub 2-1:1.0: enabling power on all ports [ 10.292384] hub 1-1:1.0: state 7 ports 6 chg 0000 evt 0000 [ 10.392563] hub 2-1:1.0: port 2: status 0101 change 0001 [ 10.465255] EXT4-fs (dm-0): INFO: recovery required on readonly filesystem [ 10.465393] EXT4-fs (dm-0): write access will be enabled during recovery [ 10.492324] usb 2-1: link qh256-0001/ffff880002615e00 start 1 [1/0 us] [ 10.492362] hub 2-1:1.0: state 7 ports 6 chg 0004 evt 0000 [ 10.492449] hub 2-1:1.0: port 2, status 0101, change 0000, 12 Mb/s [ 10.503436] hub 2-1:1.0: port 2 not reset yet, waiting 10ms [ 10.565442] usb 2-1.2: new full-speed USB device number 3 using ehci_hcd [ 10.576444] hub 2-1:1.0: port 2 not reset yet, waiting 10ms [ 10.651061] usb 2-1.2: skipped 1 descriptor after interface [ 10.651067] usb 2-1.2: skipped 1 descriptor after interface [ 10.651184] usb 2-1.2: default language 0x0409 [ 10.651809] usb 2-1.2: udev 3, busnum 2, minor = 130 [ 10.651813] usb 2-1.2: New USB device found, idVendor=046b, idProduct=ff10 [ 10.651955] usb 2-1.2: New USB device strings: Mfr=1, Product=2, SerialNumber=3 [ 10.652140] usb 2-1.2: Product: Virtual Keyboard and Mouse [ 10.652261] usb 2-1.2: Manufacturer: American Megatrends Inc. [ 10.652389] usb 2-1.2: SerialNumber: serial [ 10.652627] usb 2-1.2: usb_probe_device [ 10.652631] usb 2-1.2: configuration #1 chosen from 1 choice [ 10.652996] usb 2-1.2: adding 2-1.2:1.0 (config #1, interface 0) [ 10.653320] usbhid 2-1.2:1.0: usb_probe_interface [ 10.653324] usbhid 2-1.2:1.0: usb_probe_interface - got id [ 10.654370] input: American Megatrends Inc. Virtual Keyboard and Mouse as /devices/pci0000:00/0000:00:1d.0/usb2/2-1/2-1.2/2-1.2:1.0/input/input2 [ 10.654605] usb 2-1.2: link qh8-0601/ffff88005f597480 start 2 [1/2 us] [ 10.654782] hid-generic 0003:046B:FF10.0001: input,hidraw0: USB HID v1.10 Keyboard [American Megatrends Inc. Virtual Keyboard and Mouse] on usb-0000:00:1d.0-1.2/input0 [ 10.655095] usb 2-1.2: adding 2-1.2:1.1 (config #1, interface 1) [ 10.655431] usbhid 2-1.2:1.1: usb_probe_interface [ 10.655433] usbhid 2-1.2:1.1: usb_probe_interface - got id [ 10.656222] input: American Megatrends Inc. Virtual Keyboard and Mouse as /devices/pci0000:00/0000:00:1d.0/usb2/2-1/2-1.2/2-1.2:1.1/input/input3 [ 10.656629] hid-generic 0003:046B:FF10.0002: input,hidraw1: USB HID v1.10 Mouse [American Megatrends Inc. Virtual Keyboard and Mouse] on usb-0000:00:1d.0-1.2/input1 [ 10.972958] EXT4-fs (dm-0): recovery complete [ 10.980394] EXT4-fs (dm-0): mounted filesystem with ordered data mode. Opts: (null) [ 10.981003] mount (1853) used greatest stack depth: 4152 bytes left [ 11.028675] dracut: Mounted root filesystem /dev/mapper/vg_xenserver01-LV_ROOT [ 11.107399] dracut: Loading SELinux policy [ 11.338949] SELinux: Disabled at runtime. [ 11.339092] SELinux: Unregistering netfilter hooks [ 11.370311] type=1404 audit(1347407767.345:2): selinux=0 auid=4294967295 ses=4294967295 [ 11.417676] dracut: /sbin/load_policy: Can't load policy: No such file or directory [ 11.477195] dracut: Switching root [ 12.550782] udev[1905]: starting version 161 [ 12.676942] megasas: 00.00.06.15-rc1 Mon. Mar. 19 17:00:00 PDT 2012 [ 12.677116] megasas: 0x1000:0x0079:0x8086:0x9264: bus 5:slot 0:func 0 [ 12.677334] xen: registering gsi 16 triggering 0 polarity 1 [ 12.677340] Already setup the GSI :16 [ 12.684527] megasas: FW now in Ready state [ 12.707309] megasas_init_mfi: fw_support_ieee=0 [ 12.707384] megasas: INIT adapter done [ 12.771541] scsi6 : LSI SAS based MegaRAID driver [ 12.773245] scsi 6:0:1:0: Direct-Access ATA WDC WD1002FBYS-1 0C06 PQ: 0 ANSI: 5 [ 12.775513] scsi 6:0:3:0: Direct-Access ATA WDC WD1002FBYS-1 0C06 PQ: 0 ANSI: 5 [ 12.805736] scsi 6:2:0:0: Direct-Access INTEL RT3WB080 2.13 PQ: 0 ANSI: 5 [ 12.806076] sd 6:2:0:0: Attached scsi generic sg1 type 0 [ 12.806437] sd 6:2:0:0: [sdb] 1951170560 512-byte logical blocks: (998 GB/930 GiB) [ 12.806868] sd 6:2:0:0: [sdb] Write Protect is off [ 12.807008] sd 6:2:0:0: [sdb] Mode Sense: 1f 00 00 08 [ 12.807199] sd 6:2:0:0: [sdb] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA [ 12.824596] sdb: sdb1 sdb2 [ 12.825369] sd 6:2:0:0: [sdb] Attached SCSI disk [ 13.829099] ip (2154) used greatest stack depth: 3784 bytes left [ 19.761112] EXT4-fs (dm-0): re-mounted. Opts: (null) [ 19.978154] EXT4-fs (sda1): mounting ext2 file system using the ext4 subsystem [ 19.979455] EXT4-fs (sda1): mounted filesystem without journal. Opts: (null) [ 20.228555] Adding 21528572k swap on /dev/mapper/vg_xenserver01-LV_SWAP. Priority:-1 extents:1 across:21528572k Finally xl info: host : xen-server01.ark-net.org release : 3.6.0-rc4+ version : #2 SMP Mon Sep 10 14:42:44 EDT 2012 machine : x86_64 nr_cpus : 8 max_cpu_id : 7 nr_nodes : 1 cores_per_socket : 4 threads_per_core : 2 cpu_mhz : 2533 hw_caps : bfebfbff:28100800:00000000:00003b40:0098e3fd:00000000:00000001:00000000 virt_caps : hvm hvm_directio total_memory : 32731 free_memory : 30255 sharing_freed_memory : 0 sharing_used_memory : 0 free_cpus : 0 xen_major : 4 xen_minor : 3 xen_extra : -unstable xen_caps : xen-3.0-x86_64 xen-3.0-x86_32p hvm-3.0-x86_32 hvm-3.0-x86_32p hvm-3.0-x86_64 xen_scheduler : credit xen_pagesize : 4096 platform_params : virt_start=0xffff800000000000 xen_changeset : unavailable xen_commandline : dom0_mem=2G iommu=pv msi=1 dom0_max_vcpus=2 dom0_vcpus_pin tmem loglvl=info conring_size=134217728 console_to_ring cc_compiler : gcc (GCC) 4.5.1 20100924 (Red Hat 4.5.1-4) cc_compile_by : root cc_compile_domain : ark-net.org cc_compile_date : Mon Sep 10 19:53:51 EDT 2012 xend_config_format : 4 Maybe this helps. Mike _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Wed Sep 12 01:49:37 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Wed, 12 Sep 2012 01:49:37 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TBc3r-0002rI-8K; Wed, 12 Sep 2012 01:48:15 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TBc3p-0002rD-II for xen-users@lists.xensource.com; Wed, 12 Sep 2012 01:48:13 +0000 Received: from [85.158.143.35:11812] by server-1.bemta-4.messagelabs.com id 15/57-12504-CD9EF405; Wed, 12 Sep 2012 01:48:12 +0000 X-Env-Sender: mike.a.collins@ark-net.org X-Msg-Ref: server-6.tower-21.messagelabs.com!1347414491!17811481!1 X-Originating-IP: [216.33.127.81] X-SpamReason: No, hits=0.0 required=7.0 tests= X-StarScan-Received: X-StarScan-Version: 6.6.1.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 17353 invoked from network); 12 Sep 2012 01:48:11 -0000 Received: from mta21.charter.net (HELO mta21.charter.net) (216.33.127.81) by server-6.tower-21.messagelabs.com with SMTP; 12 Sep 2012 01:48:11 -0000 Received: from imp11 ([10.20.200.11]) by mta21.charter.net (InterMail vM.8.01.05.02 201-2260-151-103-20110920) with ESMTP id <20120912014810.XWTM12025.mta21.charter.net@imp11>; Tue, 11 Sep 2012 21:48:10 -0400 Received: from mail.ark-net.org ([75.138.215.251]) by imp11 with smtp.charter.net id y1oA1j00F5S18aK051oA6w; Tue, 11 Sep 2012 21:48:10 -0400 X-Authority-Analysis: v=1.1 cv=Mv9Cy8NsQItTEAHnXr6fCNbI23lcrkmyMeqLv9HU3yU= c=1 sm=1 a=0bCt-fb661UA:10 a=yvU03qplA7IA:10 a=VCxxn1A5iYMA:10 a=NqYyV4q_xg0A:10 a=wPDyFdB5xvgA:10 a=IkcTkHD0fZMA:10 a=4A50YBgeEUJTzIKlCdeDOQ==:17 a=SEF7xSSsAAAA:8 a=fjDLDQZ3q9GLMH2E2LwA:9 a=QEXdDO2ut3YA:10 a=4A50YBgeEUJTzIKlCdeDOQ==:117 Received: from localhost (unknown [127.0.0.1]) by mail.ark-net.org (Postfix) with ESMTP id 419DF203DF; Wed, 12 Sep 2012 01:48:28 +0000 (UTC) X-Virus-Scanned: amavisd-new at ark-net.org Received: from mail.ark-net.org ([127.0.0.1]) by localhost (mail.ark-net.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id pb3XL1qAJgtd; Tue, 11 Sep 2012 21:47:53 -0400 (EDT) Received: from 192.168.1.12 (unknown [192.168.1.12]) by mail.ark-net.org (Postfix) with ESMTP id E84A9203D1; Tue, 11 Sep 2012 21:47:52 -0400 (EDT) MIME-Version: 1.0 Date: Tue, 11 Sep 2012 22:03:49 -0400 From: "Michael A. Collins" To: =?UTF-8?Q?Pasi_K=C3=A4rkk=C3=A4inen?= Mail-Reply-To: In-Reply-To: <20120907053251.GE8912@reaktio.net> References: <6035A0D088A63A46850C3988ED045A4B289D3F42@BITCOM1.int.sbss.com.au> <013501cd870d$10617740$312465c0$@ark-net.org> <20120906150653.GZ8912@reaktio.net> <030d01cd8c8e$f13d8d40$d3b8a7c0$@ark-net.org> <20120907053251.GE8912@reaktio.net> Message-ID: X-Sender: mike.a.collins@ark-net.org User-Agent: Roundcube Webmail/0.6-beta Cc: 'James Harper' , xen-users@lists.xensource.com Subject: Re: [Xen-users] emulated rtl8139 driver, openvswitch, and offload X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list Reply-To: mike.a.collins@ark-net.org List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: base64 Content-Type: text/plain; charset="utf-8"; Format="flowed" Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org T24gMDcuMDkuMjAxMiAwMTozMiwgUGFzaSBLw6Rya2vDpGluZW4gd3JvdGU6Cj4gT24gVGh1LCBT ZXAgMDYsIDIwMTIgYXQgMDg6MjI6NTdQTSAtMDQwMCwgTWljaGFlbCBBLiBDb2xsaW5zIHdyb3Rl Ogo+PiA+IC0tLS0tT3JpZ2luYWwgTWVzc2FnZS0tLS0tCj4+ID4gRnJvbTogUGFzaSBLw6Rya2vD pGluZW4gW21haWx0bzpwYXNpa0Bpa2kuZmldCj4+ID4gU2VudDogVGh1cnNkYXksIFNlcHRlbWJl ciAwNiwgMjAxMiAxMTowNyBBTQo+PiA+IFRvOiBNaWNoYWVsIEEuIENvbGxpbnMKPj4gPiBDYzog J0phbWVzIEhhcnBlcic7IHhlbi11c2Vyc0BsaXN0cy54ZW5zb3VyY2UuY29tCj4+ID4gU3ViamVj dDogUmU6IFtYZW4tdXNlcnNdIGVtdWxhdGVkIHJ0bDgxMzkgZHJpdmVyLCBvcGVudnN3aXRjaCwg YW5kIAo+PiBvZmZsb2FkCj4+ID4KPj4gPiBPbiBUaHUsIEF1ZyAzMCwgMjAxMiBhdCAwODoxMDoz OVBNIC0wNDAwLCBNaWNoYWVsIEEuIENvbGxpbnMgCj4+IHdyb3RlOgo+PiA+ID4gSmFtZXMsCj4+ ID4gPiAgICAgSSBoYXZlIG5vdCBiZWVuIGFibGUgdG8gcmVsaWFibHkgZGlzYWJsZSBMYXJnZSBT ZW5kIE9mZmxvYWQsCj4+ID4gPiBDaGVja3N1bSBPZmZsb2FkIGFuZCBTY2F0dGVyL0dhdGhlciB0 aHJvdWdoIHRoZSBkZXZpY2UgbWFuYWdlciAKPj4gR1VJIG9uCj4+ID4gPiBXaW5kb3dzIDIwMDgg MzJiaXQvNjRiaXQgd2l0aCBwdl9kcml2ZXJzIGluc3RhbGxlZC4gIFRoZSBYZW4gTmV0Cj4+ID4g PiBEZXZpY2UgRHJpdmVyIHdpbGwgZmFpbCB0byBzdGFydCBhbmQgdGhlbSB0aGUgZG9tMCB3aWxs IHBhbmljIAo+PiBhbmQKPj4gPiA+IHJlYm9vdC4gIEkgYW0gdmVyeSBzY2FyZWQgdG8gY29udGlu dWUhICBUaGlzIGhhcHBlbmVkIHRvIG1lIAo+PiB0d2ljZQo+PiA+ID4gdG9kYXkgd2hpbGUgSSB3 YXMgZ29pbmcgdGhyb3VnaCBhbmQgZGlzYWJsaW5nIEdTTy9UU08vR1JPIG9uIG15Cj4+ID4gPiBi cm9hZGNvbSBibngyIGludGVyZmFjZXMgdG8gZml4IGEgc2VyaW91cyBpc3N1ZSB3ZSBoYXZlIHdp dGgKPj4gPiA+IGludGVyLUhvc3QgbmV0d29yayB0cmFmZmljLiAgSXMgdGhlcmUgYSB3YXkgdG8g ZG8gdGhpcyB0aGF0IAo+PiBkb2Vzbid0Cj4+IGludm9sdmUKPj4gPiBjcmFzaGluZyB0aGUgZG9t MCBhbmQgY2F1c2luZyB0aGUgd2hvbGUgYm94IHRvIHJlYm9vdD8KPj4gPiA+IEFsc28sIGlzIHRo ZXJlIGEgZ3VpZGUgdG8gdXBkYXRpbmcgdGhlIGRyaXZlcnM/ICBJIHdvdWxkIGxpa2UgdG8KPj4g PiA+IGluc3RhbGwgdGhlIGxhdGVzdCAzNTcgZHJpdmVycywgYnV0IHRoZSBvbmUgdGltZSBJIHRy aWVkIAo+PiB1bmluc3RhbGxpbmcKPj4gPiA+IHRoZW0gSSBoYWQgYSBCU09EIGFuZCBoYWQgdG8g cmVpbWFnZS4KPj4gPiA+Cj4+ID4KPj4gPiBXaGF0IGRvbTAga2VybmVsIHZlcnNpb24gYXJlIHlv dSB1c2luZz8gQWxzbyB3aGF0IFhlbiB2ZXJzaW9uPwo+PiA+Cj4+ID4gZG9tMCBjcmFzaGluZyB3 aGVuIGNoYW5naW5nIHNldHRpbmdzIGluIHRoZSBkb21VIGlzIGEgdmVyeSBzZXJpb3VzIAo+PiBi dWchCj4+ID4KPj4gPgo+PiA+IC0tIFBhc2kKPj4gPgo+PiBMaW51eCB2ZXJzaW9uOiAzLjUuMC1y YzIKPj4gWGVuIHZlcnNpb246IFhlbiA0LjIgdW5zdGFibGUgY2hhbmdlc2V0OiAyNTQ2Nwo+Pgo+ PiBJIGNhbiB0ZXN0IHdpdGggYSBtb3JlIHJlY2VudCB2ZXJzaW9uIG9yIFhlbiBvciB0aGUga2Vy bmVsIHRoaXMgCj4+IHdlZWtlbmQuICBJCj4+IGNhbiBjYXB0dXJlIHNlcmlhbCBjb25zb2xlIGxv Z3MgYW5kIHdoYXRldmVyIGVsc2UgaXMgbmVlZGVkLgo+Pgo+Cj4gTWFrZSBzdXJlIHlvdSB1cGRh dGUgeW91ciBYZW4gdG8gbGF0ZXN0IHZlcnNpb24sIGFuZCBhbHNvIHlvdXIgZG9tMCAKPiBrZXJu ZWwKPiB0byBhdCBsZWFzdCAzLjUuMy4KPgo+IC0tIFBhc2kKCgoKSSBoYXZlIG5vdCBiZWVuIGFi bGUgdG8gcmVwcm9kdWNlIHRoaXMgYXQgaG9tZSwgYnV0IEknbSBub3QgdXNpbmcgCkJyb2FkY29t IG5pY3MuICBJIGhhdmUgaW50ZWwgbmljcywgc28gSSdtIHRoaW5raW5nIGl0J3MgcmVsYXRlZCB0 byAKQnJvYWRjb20uICBJIHdpbGwgbmVlZCB0byB0ZXN0IHRoaXMgYXQgdGhlIG9mZmljZSwgc28g aXQnbGwgYmUgYSBmZXcgCmRheXMgYmVmb3JlIEkgZ2V0IGFueXRoaW5nIG9mIHN1YnN0YW5jZS4K TWlrZQoKCl9fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fClhl bi11c2VycyBtYWlsaW5nIGxpc3QKWGVuLXVzZXJzQGxpc3RzLnhlbi5vcmcKaHR0cDovL2xpc3Rz Lnhlbi5vcmcveGVuLXVzZXJz From xen-users-bounces@lists.xen.org Wed Sep 12 01:49:37 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Wed, 12 Sep 2012 01:49:37 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TBc3r-0002rI-8K; Wed, 12 Sep 2012 01:48:15 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TBc3p-0002rD-II for xen-users@lists.xensource.com; Wed, 12 Sep 2012 01:48:13 +0000 Received: from [85.158.143.35:11812] by server-1.bemta-4.messagelabs.com id 15/57-12504-CD9EF405; Wed, 12 Sep 2012 01:48:12 +0000 X-Env-Sender: mike.a.collins@ark-net.org X-Msg-Ref: server-6.tower-21.messagelabs.com!1347414491!17811481!1 X-Originating-IP: [216.33.127.81] X-SpamReason: No, hits=0.0 required=7.0 tests= X-StarScan-Received: X-StarScan-Version: 6.6.1.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 17353 invoked from network); 12 Sep 2012 01:48:11 -0000 Received: from mta21.charter.net (HELO mta21.charter.net) (216.33.127.81) by server-6.tower-21.messagelabs.com with SMTP; 12 Sep 2012 01:48:11 -0000 Received: from imp11 ([10.20.200.11]) by mta21.charter.net (InterMail vM.8.01.05.02 201-2260-151-103-20110920) with ESMTP id <20120912014810.XWTM12025.mta21.charter.net@imp11>; Tue, 11 Sep 2012 21:48:10 -0400 Received: from mail.ark-net.org ([75.138.215.251]) by imp11 with smtp.charter.net id y1oA1j00F5S18aK051oA6w; Tue, 11 Sep 2012 21:48:10 -0400 X-Authority-Analysis: v=1.1 cv=Mv9Cy8NsQItTEAHnXr6fCNbI23lcrkmyMeqLv9HU3yU= c=1 sm=1 a=0bCt-fb661UA:10 a=yvU03qplA7IA:10 a=VCxxn1A5iYMA:10 a=NqYyV4q_xg0A:10 a=wPDyFdB5xvgA:10 a=IkcTkHD0fZMA:10 a=4A50YBgeEUJTzIKlCdeDOQ==:17 a=SEF7xSSsAAAA:8 a=fjDLDQZ3q9GLMH2E2LwA:9 a=QEXdDO2ut3YA:10 a=4A50YBgeEUJTzIKlCdeDOQ==:117 Received: from localhost (unknown [127.0.0.1]) by mail.ark-net.org (Postfix) with ESMTP id 419DF203DF; Wed, 12 Sep 2012 01:48:28 +0000 (UTC) X-Virus-Scanned: amavisd-new at ark-net.org Received: from mail.ark-net.org ([127.0.0.1]) by localhost (mail.ark-net.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id pb3XL1qAJgtd; Tue, 11 Sep 2012 21:47:53 -0400 (EDT) Received: from 192.168.1.12 (unknown [192.168.1.12]) by mail.ark-net.org (Postfix) with ESMTP id E84A9203D1; Tue, 11 Sep 2012 21:47:52 -0400 (EDT) MIME-Version: 1.0 Date: Tue, 11 Sep 2012 22:03:49 -0400 From: "Michael A. Collins" To: =?UTF-8?Q?Pasi_K=C3=A4rkk=C3=A4inen?= Mail-Reply-To: In-Reply-To: <20120907053251.GE8912@reaktio.net> References: <6035A0D088A63A46850C3988ED045A4B289D3F42@BITCOM1.int.sbss.com.au> <013501cd870d$10617740$312465c0$@ark-net.org> <20120906150653.GZ8912@reaktio.net> <030d01cd8c8e$f13d8d40$d3b8a7c0$@ark-net.org> <20120907053251.GE8912@reaktio.net> Message-ID: X-Sender: mike.a.collins@ark-net.org User-Agent: Roundcube Webmail/0.6-beta Cc: 'James Harper' , xen-users@lists.xensource.com Subject: Re: [Xen-users] emulated rtl8139 driver, openvswitch, and offload X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list Reply-To: mike.a.collins@ark-net.org List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: base64 Content-Type: text/plain; charset="utf-8"; Format="flowed" Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org T24gMDcuMDkuMjAxMiAwMTozMiwgUGFzaSBLw6Rya2vDpGluZW4gd3JvdGU6Cj4gT24gVGh1LCBT ZXAgMDYsIDIwMTIgYXQgMDg6MjI6NTdQTSAtMDQwMCwgTWljaGFlbCBBLiBDb2xsaW5zIHdyb3Rl Ogo+PiA+IC0tLS0tT3JpZ2luYWwgTWVzc2FnZS0tLS0tCj4+ID4gRnJvbTogUGFzaSBLw6Rya2vD pGluZW4gW21haWx0bzpwYXNpa0Bpa2kuZmldCj4+ID4gU2VudDogVGh1cnNkYXksIFNlcHRlbWJl ciAwNiwgMjAxMiAxMTowNyBBTQo+PiA+IFRvOiBNaWNoYWVsIEEuIENvbGxpbnMKPj4gPiBDYzog J0phbWVzIEhhcnBlcic7IHhlbi11c2Vyc0BsaXN0cy54ZW5zb3VyY2UuY29tCj4+ID4gU3ViamVj dDogUmU6IFtYZW4tdXNlcnNdIGVtdWxhdGVkIHJ0bDgxMzkgZHJpdmVyLCBvcGVudnN3aXRjaCwg YW5kIAo+PiBvZmZsb2FkCj4+ID4KPj4gPiBPbiBUaHUsIEF1ZyAzMCwgMjAxMiBhdCAwODoxMDoz OVBNIC0wNDAwLCBNaWNoYWVsIEEuIENvbGxpbnMgCj4+IHdyb3RlOgo+PiA+ID4gSmFtZXMsCj4+ ID4gPiAgICAgSSBoYXZlIG5vdCBiZWVuIGFibGUgdG8gcmVsaWFibHkgZGlzYWJsZSBMYXJnZSBT ZW5kIE9mZmxvYWQsCj4+ID4gPiBDaGVja3N1bSBPZmZsb2FkIGFuZCBTY2F0dGVyL0dhdGhlciB0 aHJvdWdoIHRoZSBkZXZpY2UgbWFuYWdlciAKPj4gR1VJIG9uCj4+ID4gPiBXaW5kb3dzIDIwMDgg MzJiaXQvNjRiaXQgd2l0aCBwdl9kcml2ZXJzIGluc3RhbGxlZC4gIFRoZSBYZW4gTmV0Cj4+ID4g PiBEZXZpY2UgRHJpdmVyIHdpbGwgZmFpbCB0byBzdGFydCBhbmQgdGhlbSB0aGUgZG9tMCB3aWxs IHBhbmljIAo+PiBhbmQKPj4gPiA+IHJlYm9vdC4gIEkgYW0gdmVyeSBzY2FyZWQgdG8gY29udGlu dWUhICBUaGlzIGhhcHBlbmVkIHRvIG1lIAo+PiB0d2ljZQo+PiA+ID4gdG9kYXkgd2hpbGUgSSB3 YXMgZ29pbmcgdGhyb3VnaCBhbmQgZGlzYWJsaW5nIEdTTy9UU08vR1JPIG9uIG15Cj4+ID4gPiBi cm9hZGNvbSBibngyIGludGVyZmFjZXMgdG8gZml4IGEgc2VyaW91cyBpc3N1ZSB3ZSBoYXZlIHdp dGgKPj4gPiA+IGludGVyLUhvc3QgbmV0d29yayB0cmFmZmljLiAgSXMgdGhlcmUgYSB3YXkgdG8g ZG8gdGhpcyB0aGF0IAo+PiBkb2Vzbid0Cj4+IGludm9sdmUKPj4gPiBjcmFzaGluZyB0aGUgZG9t MCBhbmQgY2F1c2luZyB0aGUgd2hvbGUgYm94IHRvIHJlYm9vdD8KPj4gPiA+IEFsc28sIGlzIHRo ZXJlIGEgZ3VpZGUgdG8gdXBkYXRpbmcgdGhlIGRyaXZlcnM/ICBJIHdvdWxkIGxpa2UgdG8KPj4g PiA+IGluc3RhbGwgdGhlIGxhdGVzdCAzNTcgZHJpdmVycywgYnV0IHRoZSBvbmUgdGltZSBJIHRy aWVkIAo+PiB1bmluc3RhbGxpbmcKPj4gPiA+IHRoZW0gSSBoYWQgYSBCU09EIGFuZCBoYWQgdG8g cmVpbWFnZS4KPj4gPiA+Cj4+ID4KPj4gPiBXaGF0IGRvbTAga2VybmVsIHZlcnNpb24gYXJlIHlv dSB1c2luZz8gQWxzbyB3aGF0IFhlbiB2ZXJzaW9uPwo+PiA+Cj4+ID4gZG9tMCBjcmFzaGluZyB3 aGVuIGNoYW5naW5nIHNldHRpbmdzIGluIHRoZSBkb21VIGlzIGEgdmVyeSBzZXJpb3VzIAo+PiBi dWchCj4+ID4KPj4gPgo+PiA+IC0tIFBhc2kKPj4gPgo+PiBMaW51eCB2ZXJzaW9uOiAzLjUuMC1y YzIKPj4gWGVuIHZlcnNpb246IFhlbiA0LjIgdW5zdGFibGUgY2hhbmdlc2V0OiAyNTQ2Nwo+Pgo+ PiBJIGNhbiB0ZXN0IHdpdGggYSBtb3JlIHJlY2VudCB2ZXJzaW9uIG9yIFhlbiBvciB0aGUga2Vy bmVsIHRoaXMgCj4+IHdlZWtlbmQuICBJCj4+IGNhbiBjYXB0dXJlIHNlcmlhbCBjb25zb2xlIGxv Z3MgYW5kIHdoYXRldmVyIGVsc2UgaXMgbmVlZGVkLgo+Pgo+Cj4gTWFrZSBzdXJlIHlvdSB1cGRh dGUgeW91ciBYZW4gdG8gbGF0ZXN0IHZlcnNpb24sIGFuZCBhbHNvIHlvdXIgZG9tMCAKPiBrZXJu ZWwKPiB0byBhdCBsZWFzdCAzLjUuMy4KPgo+IC0tIFBhc2kKCgoKSSBoYXZlIG5vdCBiZWVuIGFi bGUgdG8gcmVwcm9kdWNlIHRoaXMgYXQgaG9tZSwgYnV0IEknbSBub3QgdXNpbmcgCkJyb2FkY29t IG5pY3MuICBJIGhhdmUgaW50ZWwgbmljcywgc28gSSdtIHRoaW5raW5nIGl0J3MgcmVsYXRlZCB0 byAKQnJvYWRjb20uICBJIHdpbGwgbmVlZCB0byB0ZXN0IHRoaXMgYXQgdGhlIG9mZmljZSwgc28g aXQnbGwgYmUgYSBmZXcgCmRheXMgYmVmb3JlIEkgZ2V0IGFueXRoaW5nIG9mIHN1YnN0YW5jZS4K TWlrZQoKCl9fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fClhl bi11c2VycyBtYWlsaW5nIGxpc3QKWGVuLXVzZXJzQGxpc3RzLnhlbi5vcmcKaHR0cDovL2xpc3Rz Lnhlbi5vcmcveGVuLXVzZXJz From xen-users-bounces@lists.xen.org Wed Sep 12 08:14:51 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Wed, 12 Sep 2012 08:14:51 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TBi4r-0005mK-Iz; Wed, 12 Sep 2012 08:13:41 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TBi4q-0005m6-Be for xen-users@lists.xen.org; Wed, 12 Sep 2012 08:13:40 +0000 Received: from [85.158.143.35:7603] by server-2.bemta-4.messagelabs.com id 21/80-21239-33440505; Wed, 12 Sep 2012 08:13:39 +0000 X-Env-Sender: Ian.Campbell@citrix.com X-Msg-Ref: server-9.tower-21.messagelabs.com!1347437618!6825041!1 X-Originating-IP: [62.200.22.115] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogNjIuMjAwLjIyLjExNSA9PiAxMDg3NTM=\n X-StarScan-Received: X-StarScan-Version: 6.6.1.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 6560 invoked from network); 12 Sep 2012 08:13:38 -0000 Received: from smtp.eu.citrix.com (HELO SMTP.EU.CITRIX.COM) (62.200.22.115) by server-9.tower-21.messagelabs.com with RC4-SHA encrypted SMTP; 12 Sep 2012 08:13:38 -0000 X-IronPort-AV: E=Sophos;i="4.80,408,1344211200"; d="scan'208";a="14487622" Received: from lonpmailmx01.citrite.net ([10.30.203.162]) by LONPIPO01.EU.CITRIX.COM with ESMTP/TLS/RC4-MD5; 12 Sep 2012 08:13:38 +0000 Received: from [127.0.0.1] (10.80.16.67) by smtprelay.citrix.com (10.30.203.162) with Microsoft SMTP Server id 8.3.279.1; Wed, 12 Sep 2012 09:13:38 +0100 Message-ID: <1347437617.25803.17.camel@dagon.hellion.org.uk> From: Ian Campbell To: Maik Brauer Date: Wed, 12 Sep 2012 09:13:37 +0100 In-Reply-To: <4BCC413D-1697-4681-AF28-118D1623AF1C@mbs-systems.net> References: <9F8FD2B0-450A-4A6E-A929-BA240ED1D997@mbs-systems.net> <1346746297.32462.37.camel@zakaz.uk.xensource.com> <1347266386.5305.17.camel@zakaz.uk.xensource.com> <4957C391-6070-47C1-A2AC-991ED1C1766A@mbs-systems.net> <1347289853.5305.105.camel@zakaz.uk.xensource.com> <4BCC413D-1697-4681-AF28-118D1623AF1C@mbs-systems.net> Organization: Citrix Systems, Inc. X-Mailer: Evolution 3.4.3-1 MIME-Version: 1.0 Cc: "xen-users@lists.xen.org" Subject: Re: [Xen-users] Dom0 crashed when rebooting whilst DomU are running X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org On Tue, 2012-09-11 at 23:46 +0100, Maik Brauer wrote: > >>>> I found out that it hangs during re-boot of dom0 when having more > >>>> Network interfaces involved, like: > >>>> vif = [ 'mac=06:46:AB:CC:11:01, ip=', '', '', > >>>> 'mac=06:04:AB:BB:11:03, bridge=VLAN20, script=vif-bridge', '', > >>>> 'mac=06:04:AB:BB:11:05, bridge=VLAN40, script=vif-bridge' ] > >>> > >>> 6 interfaces total, 3 of which have a random mac on each reboot and all > >>> get put on the default bridge? > >> > >> No, not really. The bridge is different for each interface. > > > > You have three lots of '' which will all go onto the same bridge AFAICT > > (whichever one is determined to be the default) > > That is right. As long as I put nothing inside that it should be a > different script to execute, it will use default for '' The default is "vif-bridge". Have you changed the default? If not then your configuration as shown will put three interfaces on the *same* bridge. Is this really what you want? You claim above that the bridge is different for each interface, but unless you have changed something somewhere then this is not the case. Since you are having problems it is important to identify everything which you have changed from the defaults. > >> List is empty. SysRQ -w and SysRQ-t shows nothing at all. > > > > You might need to increase the log verbosity with SysRQ-9 first? > > I did and now I got more Information. But due to the amount of data which slips over the console screen I am not able > to record properly. Can you advice what to do here? Like I said "that list can be quite long so it is useless without a serial console": http://wiki.xen.org/wiki/Xen_Serial_Console Depending on your distro you might also find this info in the logs under /var/log somewhere. > > > >> There is nothing running anymore. > >> It shows periodically: INFO: task xenwatch:12 blocked for more than 120 seconds > > > > What is the very last thing printed before this? > > There is nothing before. So the output is silent from boot until this message comes up? That seems unlikely, since there should be plenty of messages from the shutdown process itself if nothing else. What is the last message one the screen before this one? In fact what is the entire last screenfull of output? > > Really the initscript ought to wait, the default at least with the > > script shipped with xen is to do so, by using shutdown --wait. can you > > confirm whether or not this is happening for you? > > At least I can see that the shutdown --wait is in the scripts. So it seems that the init script is waiting. > But independent from that, something must be still in use. Which block the reboot process. > > > > Possibly someone is trying to talk to xenstore after xenstored has > > exited -- I expect that would cause the sorts of blocked for 120 > > messages you are seeing. > > > Could be, but we need to find out what is blocking the shutdown. I do not know what else I can do in order to measure and collect > data for investigation. Did you add debugging to the hotplug scripts like I suggested a couple of mails back? If you run the xendomains script by hand and then *immediately* after it exits run "xl list" have the domains actually gone? You could even stick some calls to xl list into the script itself and verify that the domains are indeed shutting down as expected. BTW Are you using xl or xend? Ian. _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Wed Sep 12 08:14:51 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Wed, 12 Sep 2012 08:14:51 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TBi4r-0005mK-Iz; Wed, 12 Sep 2012 08:13:41 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TBi4q-0005m6-Be for xen-users@lists.xen.org; Wed, 12 Sep 2012 08:13:40 +0000 Received: from [85.158.143.35:7603] by server-2.bemta-4.messagelabs.com id 21/80-21239-33440505; Wed, 12 Sep 2012 08:13:39 +0000 X-Env-Sender: Ian.Campbell@citrix.com X-Msg-Ref: server-9.tower-21.messagelabs.com!1347437618!6825041!1 X-Originating-IP: [62.200.22.115] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogNjIuMjAwLjIyLjExNSA9PiAxMDg3NTM=\n X-StarScan-Received: X-StarScan-Version: 6.6.1.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 6560 invoked from network); 12 Sep 2012 08:13:38 -0000 Received: from smtp.eu.citrix.com (HELO SMTP.EU.CITRIX.COM) (62.200.22.115) by server-9.tower-21.messagelabs.com with RC4-SHA encrypted SMTP; 12 Sep 2012 08:13:38 -0000 X-IronPort-AV: E=Sophos;i="4.80,408,1344211200"; d="scan'208";a="14487622" Received: from lonpmailmx01.citrite.net ([10.30.203.162]) by LONPIPO01.EU.CITRIX.COM with ESMTP/TLS/RC4-MD5; 12 Sep 2012 08:13:38 +0000 Received: from [127.0.0.1] (10.80.16.67) by smtprelay.citrix.com (10.30.203.162) with Microsoft SMTP Server id 8.3.279.1; Wed, 12 Sep 2012 09:13:38 +0100 Message-ID: <1347437617.25803.17.camel@dagon.hellion.org.uk> From: Ian Campbell To: Maik Brauer Date: Wed, 12 Sep 2012 09:13:37 +0100 In-Reply-To: <4BCC413D-1697-4681-AF28-118D1623AF1C@mbs-systems.net> References: <9F8FD2B0-450A-4A6E-A929-BA240ED1D997@mbs-systems.net> <1346746297.32462.37.camel@zakaz.uk.xensource.com> <1347266386.5305.17.camel@zakaz.uk.xensource.com> <4957C391-6070-47C1-A2AC-991ED1C1766A@mbs-systems.net> <1347289853.5305.105.camel@zakaz.uk.xensource.com> <4BCC413D-1697-4681-AF28-118D1623AF1C@mbs-systems.net> Organization: Citrix Systems, Inc. X-Mailer: Evolution 3.4.3-1 MIME-Version: 1.0 Cc: "xen-users@lists.xen.org" Subject: Re: [Xen-users] Dom0 crashed when rebooting whilst DomU are running X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org On Tue, 2012-09-11 at 23:46 +0100, Maik Brauer wrote: > >>>> I found out that it hangs during re-boot of dom0 when having more > >>>> Network interfaces involved, like: > >>>> vif = [ 'mac=06:46:AB:CC:11:01, ip=', '', '', > >>>> 'mac=06:04:AB:BB:11:03, bridge=VLAN20, script=vif-bridge', '', > >>>> 'mac=06:04:AB:BB:11:05, bridge=VLAN40, script=vif-bridge' ] > >>> > >>> 6 interfaces total, 3 of which have a random mac on each reboot and all > >>> get put on the default bridge? > >> > >> No, not really. The bridge is different for each interface. > > > > You have three lots of '' which will all go onto the same bridge AFAICT > > (whichever one is determined to be the default) > > That is right. As long as I put nothing inside that it should be a > different script to execute, it will use default for '' The default is "vif-bridge". Have you changed the default? If not then your configuration as shown will put three interfaces on the *same* bridge. Is this really what you want? You claim above that the bridge is different for each interface, but unless you have changed something somewhere then this is not the case. Since you are having problems it is important to identify everything which you have changed from the defaults. > >> List is empty. SysRQ -w and SysRQ-t shows nothing at all. > > > > You might need to increase the log verbosity with SysRQ-9 first? > > I did and now I got more Information. But due to the amount of data which slips over the console screen I am not able > to record properly. Can you advice what to do here? Like I said "that list can be quite long so it is useless without a serial console": http://wiki.xen.org/wiki/Xen_Serial_Console Depending on your distro you might also find this info in the logs under /var/log somewhere. > > > >> There is nothing running anymore. > >> It shows periodically: INFO: task xenwatch:12 blocked for more than 120 seconds > > > > What is the very last thing printed before this? > > There is nothing before. So the output is silent from boot until this message comes up? That seems unlikely, since there should be plenty of messages from the shutdown process itself if nothing else. What is the last message one the screen before this one? In fact what is the entire last screenfull of output? > > Really the initscript ought to wait, the default at least with the > > script shipped with xen is to do so, by using shutdown --wait. can you > > confirm whether or not this is happening for you? > > At least I can see that the shutdown --wait is in the scripts. So it seems that the init script is waiting. > But independent from that, something must be still in use. Which block the reboot process. > > > > Possibly someone is trying to talk to xenstore after xenstored has > > exited -- I expect that would cause the sorts of blocked for 120 > > messages you are seeing. > > > Could be, but we need to find out what is blocking the shutdown. I do not know what else I can do in order to measure and collect > data for investigation. Did you add debugging to the hotplug scripts like I suggested a couple of mails back? If you run the xendomains script by hand and then *immediately* after it exits run "xl list" have the domains actually gone? You could even stick some calls to xl list into the script itself and verify that the domains are indeed shutting down as expected. BTW Are you using xl or xend? Ian. _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Wed Sep 12 10:25:00 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Wed, 12 Sep 2012 10:25:00 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TBk6v-0007Zd-Fu; Wed, 12 Sep 2012 10:23:57 +0000 Received: from mail27.messagelabs.com ([193.109.254.147]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TBk6t-0007ZY-5i for xen-users@lists.xen.org; Wed, 12 Sep 2012 10:23:55 +0000 X-Env-Sender: Ian.Campbell@citrix.com X-Msg-Ref: server-7.tower-27.messagelabs.com!1347445427!3000182!1 X-Originating-IP: [62.200.22.115] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogNjIuMjAwLjIyLjExNSA9PiAxMDg4MjM=\n X-StarScan-Received: X-StarScan-Version: 6.6.1.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 17488 invoked from network); 12 Sep 2012 10:23:49 -0000 Received: from smtp.eu.citrix.com (HELO SMTP.EU.CITRIX.COM) (62.200.22.115) by server-7.tower-27.messagelabs.com with RC4-SHA encrypted SMTP; 12 Sep 2012 10:23:49 -0000 X-IronPort-AV: E=Sophos;i="4.80,408,1344211200"; d="scan'208";a="14491752" Received: from lonpmailmx01.citrite.net ([10.30.203.162]) by LONPIPO01.EU.CITRIX.COM with ESMTP/TLS/RC4-MD5; 12 Sep 2012 10:23:19 +0000 Received: from [10.80.2.42] (10.80.2.42) by LONPMAILMX01.citrite.net (10.30.203.162) with Microsoft SMTP Server id 8.3.279.1; Wed, 12 Sep 2012 11:23:19 +0100 Message-ID: <1347445398.24226.37.camel@zakaz.uk.xensource.com> From: Ian Campbell To: Maik Brauer Date: Wed, 12 Sep 2012 11:23:18 +0100 In-Reply-To: <4BCC413D-1697-4681-AF28-118D1623AF1C@mbs-systems.net> References: <9F8FD2B0-450A-4A6E-A929-BA240ED1D997@mbs-systems.net> <1346746297.32462.37.camel@zakaz.uk.xensource.com> <1347266386.5305.17.camel@zakaz.uk.xensource.com> <4957C391-6070-47C1-A2AC-991ED1C1766A@mbs-systems.net> <1347289853.5305.105.camel@zakaz.uk.xensource.com> <4BCC413D-1697-4681-AF28-118D1623AF1C@mbs-systems.net> Organization: Citrix Systems, Inc. X-Mailer: Evolution 3.4.3-1 MIME-Version: 1.0 Cc: "xen-users@lists.xen.org" Subject: Re: [Xen-users] Dom0 crashed when rebooting whilst DomU are running X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org On Tue, 2012-09-11 at 23:46 +0100, Maik Brauer wrote: > You can easiliy reproduce this issue, when using more that 3 Network > devices. I installed a PV guest on Debian Wheezy using 5 vifs all on the same bridge and could not reproduce this, the domain was successfully shutdown on reboot. I also replaced the Debian xendomains script with the one from xen-4.1-testing (since Debian's differs). Still no repro. Ian. _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Wed Sep 12 10:25:00 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Wed, 12 Sep 2012 10:25:00 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TBk6v-0007Zd-Fu; Wed, 12 Sep 2012 10:23:57 +0000 Received: from mail27.messagelabs.com ([193.109.254.147]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TBk6t-0007ZY-5i for xen-users@lists.xen.org; Wed, 12 Sep 2012 10:23:55 +0000 X-Env-Sender: Ian.Campbell@citrix.com X-Msg-Ref: server-7.tower-27.messagelabs.com!1347445427!3000182!1 X-Originating-IP: [62.200.22.115] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogNjIuMjAwLjIyLjExNSA9PiAxMDg4MjM=\n X-StarScan-Received: X-StarScan-Version: 6.6.1.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 17488 invoked from network); 12 Sep 2012 10:23:49 -0000 Received: from smtp.eu.citrix.com (HELO SMTP.EU.CITRIX.COM) (62.200.22.115) by server-7.tower-27.messagelabs.com with RC4-SHA encrypted SMTP; 12 Sep 2012 10:23:49 -0000 X-IronPort-AV: E=Sophos;i="4.80,408,1344211200"; d="scan'208";a="14491752" Received: from lonpmailmx01.citrite.net ([10.30.203.162]) by LONPIPO01.EU.CITRIX.COM with ESMTP/TLS/RC4-MD5; 12 Sep 2012 10:23:19 +0000 Received: from [10.80.2.42] (10.80.2.42) by LONPMAILMX01.citrite.net (10.30.203.162) with Microsoft SMTP Server id 8.3.279.1; Wed, 12 Sep 2012 11:23:19 +0100 Message-ID: <1347445398.24226.37.camel@zakaz.uk.xensource.com> From: Ian Campbell To: Maik Brauer Date: Wed, 12 Sep 2012 11:23:18 +0100 In-Reply-To: <4BCC413D-1697-4681-AF28-118D1623AF1C@mbs-systems.net> References: <9F8FD2B0-450A-4A6E-A929-BA240ED1D997@mbs-systems.net> <1346746297.32462.37.camel@zakaz.uk.xensource.com> <1347266386.5305.17.camel@zakaz.uk.xensource.com> <4957C391-6070-47C1-A2AC-991ED1C1766A@mbs-systems.net> <1347289853.5305.105.camel@zakaz.uk.xensource.com> <4BCC413D-1697-4681-AF28-118D1623AF1C@mbs-systems.net> Organization: Citrix Systems, Inc. X-Mailer: Evolution 3.4.3-1 MIME-Version: 1.0 Cc: "xen-users@lists.xen.org" Subject: Re: [Xen-users] Dom0 crashed when rebooting whilst DomU are running X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org On Tue, 2012-09-11 at 23:46 +0100, Maik Brauer wrote: > You can easiliy reproduce this issue, when using more that 3 Network > devices. I installed a PV guest on Debian Wheezy using 5 vifs all on the same bridge and could not reproduce this, the domain was successfully shutdown on reboot. I also replaced the Debian xendomains script with the one from xen-4.1-testing (since Debian's differs). Still no repro. Ian. _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Wed Sep 12 12:09:07 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Wed, 12 Sep 2012 12:09:07 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TBljT-0001Wk-VX; Wed, 12 Sep 2012 12:07:51 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TBljS-0001Wf-WF for xen-users@lists.xen.org; Wed, 12 Sep 2012 12:07:51 +0000 Received: from [85.158.138.51:53248] by server-11.bemta-3.messagelabs.com id C5/04-30250-61B70505; Wed, 12 Sep 2012 12:07:50 +0000 X-Env-Sender: delentef@gmail.com X-Msg-Ref: server-12.tower-174.messagelabs.com!1347451668!22200162!1 X-Originating-IP: [209.85.214.173] X-SpamReason: No, hits=1.5 required=7.0 tests=HTML_00_10,HTML_MESSAGE, ML_RADAR_SPEW_LINKS_14,RCVD_BY_IP,spamassassin: X-StarScan-Received: X-StarScan-Version: 6.6.1.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 11208 invoked from network); 12 Sep 2012 12:07:49 -0000 Received: from mail-ob0-f173.google.com (HELO mail-ob0-f173.google.com) (209.85.214.173) by server-12.tower-174.messagelabs.com with RC4-SHA encrypted SMTP; 12 Sep 2012 12:07:49 -0000 Received: by obbta14 with SMTP id ta14so3103124obb.32 for ; Wed, 12 Sep 2012 05:07:47 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:date:message-id:subject:from:to:content-type; bh=j4hFWrOrCOeeQq6CFg5I3XunWOeV3VJaqOze5F0KXcc=; b=mHEE7Tub//QTap0uN2Ws9Cu6reTsuqJNOlJuJTFEi8tjZ9o8ObbbUF/3MZqIY8haJs XcrQz1A8mAFMsVWTbv+s5seAau+/znxdcw6r+DdD5VZRgSab35EQYhFWkliyoteVM0pt rKdGBiVaeBkYRQZ90E/BPuCfBnuyZIwfIC8YNjcU3ooVVpLzCxMM1vo5PskqOPEW2hHv CXIEISL3ffPYrUQOPfmuvm3mHJGl6qNMRdu0C3CjoBwRy6zH6+aNVvPcaBlvHal3rcj5 o1s0Cy1ZYE0N5SSRauL16EbLhigGhgLQOjmUNLhE/ijNRzsrmOLVNqGdQPSJHa2laqMj 13NQ== MIME-Version: 1.0 Received: by 10.60.22.104 with SMTP id c8mr21720266oef.2.1347451667760; Wed, 12 Sep 2012 05:07:47 -0700 (PDT) Received: by 10.60.65.74 with HTTP; Wed, 12 Sep 2012 05:07:47 -0700 (PDT) Date: Wed, 12 Sep 2012 14:07:47 +0200 Message-ID: From: Fabrice Delente To: xen-users@lists.xen.org Subject: [Xen-users] No network connection after dom0 crash X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============5131067665371832317==" Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org --===============5131067665371832317== Content-Type: multipart/alternative; boundary=e89a8fb1ff2c02445204c9800a23 --e89a8fb1ff2c02445204c9800a23 Content-Type: text/plain; charset=UTF-8 Hello. I have experienced a dom0 crash after trying to start 4 virtual machines (the first 3rd started ok, and starting the 4th resulted in a xend crash). After rebooting the physical server, I restarted 2 of the virtual machines. One is under Windows XP, and had no problem connecting to the network with the static IP I assigned it. The other is under Debian Squeeze, has its network interface and its route set up correctly, but cannot be pinged and cannot ping the outside world. I tried pinging the gateway, I tried using DHCP, I tried bringing down eth0 and then bringing it up again manually with ifconfig eth0 up , as well as setting the gateway with route add default gw, but no success. On a physical machine, I'd say the cable is not hooked up in the socket. Any hint on this? Thanks! -- Fabrice DELENTE --e89a8fb1ff2c02445204c9800a23 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Hello.

I have experienced a dom0 crash after trying to start 4 virtu= al machines (the first 3rd started ok, and starting the 4th resulted in a x= end crash).

After rebooting the physical server, I restarted 2 of th= e virtual machines. One is under Windows XP, and had no problem connecting = to the network with the static IP I assigned it.

The other is under Debian Squeeze, has its network interface and its ro= ute set up correctly, but cannot be pinged and cannot ping the outside worl= d. I tried pinging the gateway, I tried using DHCP, I tried bringing down e= th0 and then bringing it up again manually with ifconfig eth0 up <IP>= , as well as setting the gateway with route add default gw, but no success.= On a physical machine, I'd say the cable is not hooked up in the socke= t.

Any hint on this?

Thanks!

--
Fabrice DE= LENTE
--e89a8fb1ff2c02445204c9800a23-- --===============5131067665371832317== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users --===============5131067665371832317==-- From xen-users-bounces@lists.xen.org Wed Sep 12 12:09:07 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Wed, 12 Sep 2012 12:09:07 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TBljT-0001Wk-VX; Wed, 12 Sep 2012 12:07:51 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TBljS-0001Wf-WF for xen-users@lists.xen.org; Wed, 12 Sep 2012 12:07:51 +0000 Received: from [85.158.138.51:53248] by server-11.bemta-3.messagelabs.com id C5/04-30250-61B70505; Wed, 12 Sep 2012 12:07:50 +0000 X-Env-Sender: delentef@gmail.com X-Msg-Ref: server-12.tower-174.messagelabs.com!1347451668!22200162!1 X-Originating-IP: [209.85.214.173] X-SpamReason: No, hits=1.5 required=7.0 tests=HTML_00_10,HTML_MESSAGE, ML_RADAR_SPEW_LINKS_14,RCVD_BY_IP,spamassassin: X-StarScan-Received: X-StarScan-Version: 6.6.1.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 11208 invoked from network); 12 Sep 2012 12:07:49 -0000 Received: from mail-ob0-f173.google.com (HELO mail-ob0-f173.google.com) (209.85.214.173) by server-12.tower-174.messagelabs.com with RC4-SHA encrypted SMTP; 12 Sep 2012 12:07:49 -0000 Received: by obbta14 with SMTP id ta14so3103124obb.32 for ; Wed, 12 Sep 2012 05:07:47 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:date:message-id:subject:from:to:content-type; bh=j4hFWrOrCOeeQq6CFg5I3XunWOeV3VJaqOze5F0KXcc=; b=mHEE7Tub//QTap0uN2Ws9Cu6reTsuqJNOlJuJTFEi8tjZ9o8ObbbUF/3MZqIY8haJs XcrQz1A8mAFMsVWTbv+s5seAau+/znxdcw6r+DdD5VZRgSab35EQYhFWkliyoteVM0pt rKdGBiVaeBkYRQZ90E/BPuCfBnuyZIwfIC8YNjcU3ooVVpLzCxMM1vo5PskqOPEW2hHv CXIEISL3ffPYrUQOPfmuvm3mHJGl6qNMRdu0C3CjoBwRy6zH6+aNVvPcaBlvHal3rcj5 o1s0Cy1ZYE0N5SSRauL16EbLhigGhgLQOjmUNLhE/ijNRzsrmOLVNqGdQPSJHa2laqMj 13NQ== MIME-Version: 1.0 Received: by 10.60.22.104 with SMTP id c8mr21720266oef.2.1347451667760; Wed, 12 Sep 2012 05:07:47 -0700 (PDT) Received: by 10.60.65.74 with HTTP; Wed, 12 Sep 2012 05:07:47 -0700 (PDT) Date: Wed, 12 Sep 2012 14:07:47 +0200 Message-ID: From: Fabrice Delente To: xen-users@lists.xen.org Subject: [Xen-users] No network connection after dom0 crash X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============5131067665371832317==" Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org --===============5131067665371832317== Content-Type: multipart/alternative; boundary=e89a8fb1ff2c02445204c9800a23 --e89a8fb1ff2c02445204c9800a23 Content-Type: text/plain; charset=UTF-8 Hello. I have experienced a dom0 crash after trying to start 4 virtual machines (the first 3rd started ok, and starting the 4th resulted in a xend crash). After rebooting the physical server, I restarted 2 of the virtual machines. One is under Windows XP, and had no problem connecting to the network with the static IP I assigned it. The other is under Debian Squeeze, has its network interface and its route set up correctly, but cannot be pinged and cannot ping the outside world. I tried pinging the gateway, I tried using DHCP, I tried bringing down eth0 and then bringing it up again manually with ifconfig eth0 up , as well as setting the gateway with route add default gw, but no success. On a physical machine, I'd say the cable is not hooked up in the socket. Any hint on this? Thanks! -- Fabrice DELENTE --e89a8fb1ff2c02445204c9800a23 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Hello.

I have experienced a dom0 crash after trying to start 4 virtu= al machines (the first 3rd started ok, and starting the 4th resulted in a x= end crash).

After rebooting the physical server, I restarted 2 of th= e virtual machines. One is under Windows XP, and had no problem connecting = to the network with the static IP I assigned it.

The other is under Debian Squeeze, has its network interface and its ro= ute set up correctly, but cannot be pinged and cannot ping the outside worl= d. I tried pinging the gateway, I tried using DHCP, I tried bringing down e= th0 and then bringing it up again manually with ifconfig eth0 up <IP>= , as well as setting the gateway with route add default gw, but no success.= On a physical machine, I'd say the cable is not hooked up in the socke= t.

Any hint on this?

Thanks!

--
Fabrice DE= LENTE
--e89a8fb1ff2c02445204c9800a23-- --===============5131067665371832317== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users --===============5131067665371832317==-- From xen-users-bounces@lists.xen.org Wed Sep 12 20:48:56 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Wed, 12 Sep 2012 20:48:56 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TBtqL-00040U-9K; Wed, 12 Sep 2012 20:47:29 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TBtqJ-00040P-HT for xen-users@lists.xen.org; Wed, 12 Sep 2012 20:47:27 +0000 Received: from [85.158.143.35:49315] by server-3.bemta-4.messagelabs.com id BB/4A-08232-ED4F0505; Wed, 12 Sep 2012 20:47:26 +0000 X-Env-Sender: maik.brauer@mbs-systems.net X-Msg-Ref: server-7.tower-21.messagelabs.com!1347482846!12164788!1 X-Originating-IP: [188.40.240.248] X-SpamReason: No, hits=0.0 required=7.0 tests= X-StarScan-Received: X-StarScan-Version: 6.6.1.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 16060 invoked from network); 12 Sep 2012 20:47:26 -0000 Received: from mx1.mbs-systems.net (HELO mx1.mbs-systems.net) (188.40.240.248) by server-7.tower-21.messagelabs.com with SMTP; 12 Sep 2012 20:47:26 -0000 Received: from localhost (localhost [127.0.0.1]) by mx1.mbs-systems.net (Postfix) with ESMTP id ED3EA5C30B; Wed, 12 Sep 2012 22:48:28 +0200 (CEST) Received: from mx1.mbs-systems.net ([127.0.0.1]) by localhost (mta.mbs-systems.net [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id IyBQVz6JzNBx; Wed, 12 Sep 2012 22:48:27 +0200 (CEST) Received: from maiks-macbookpro.fritz.box (dslb-094-221-230-009.pools.arcor-ip.net [94.221.230.9]) by mx1.mbs-systems.net (Postfix) with ESMTPSA id A62C65C287; Wed, 12 Sep 2012 22:48:27 +0200 (CEST) Mime-Version: 1.0 (Apple Message framework v1278) From: Maik Brauer In-Reply-To: <1347445398.24226.37.camel@zakaz.uk.xensource.com> Date: Wed, 12 Sep 2012 22:47:21 +0200 Message-Id: <5CB14C04-2A76-4747-8209-EB5122DF7239@mbs-systems.net> References: <9F8FD2B0-450A-4A6E-A929-BA240ED1D997@mbs-systems.net> <1346746297.32462.37.camel@zakaz.uk.xensource.com> <1347266386.5305.17.camel@zakaz.uk.xensource.com> <4957C391-6070-47C1-A2AC-991ED1C1766A@mbs-systems.net> <1347289853.5305.105.camel@zakaz.uk.xensource.com> <4BCC413D-1697-4681-AF28-118D1623AF1C@mbs-systems.net> <1347445398.24226.37.camel@zakaz.uk.xensource.com> To: Ian Campbell X-Mailer: Apple Mail (2.1278) Cc: xen-users@lists.xen.org Subject: Re: [Xen-users] Dom0 crashed when rebooting whilst DomU are running X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org On Sep 12, 2012, at 12:23 PM, Ian Campbell wrote: > On Tue, 2012-09-11 at 23:46 +0100, Maik Brauer wrote: >> You can easiliy reproduce this issue, when using more that 3 Network >> devices. > > I installed a PV guest on Debian Wheezy using 5 vifs all on the same > bridge and could not reproduce this, the domain was successfully > shutdown on reboot. > > I also replaced the Debian xendomains script with the one from > xen-4.1-testing (since Debian's differs). Still no repro. > Hi Ian, please try it with the stable squeeze one. Because I am currently not using an unstable version. I have customers running on that machines so I can't experiment. Can you please try with Debian 64bit? > Ian. > > > _______________________________________________ > Xen-users mailing list > Xen-users@lists.xen.org > http://lists.xen.org/xen-users _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Wed Sep 12 20:48:56 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Wed, 12 Sep 2012 20:48:56 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TBtqL-00040U-9K; Wed, 12 Sep 2012 20:47:29 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TBtqJ-00040P-HT for xen-users@lists.xen.org; Wed, 12 Sep 2012 20:47:27 +0000 Received: from [85.158.143.35:49315] by server-3.bemta-4.messagelabs.com id BB/4A-08232-ED4F0505; Wed, 12 Sep 2012 20:47:26 +0000 X-Env-Sender: maik.brauer@mbs-systems.net X-Msg-Ref: server-7.tower-21.messagelabs.com!1347482846!12164788!1 X-Originating-IP: [188.40.240.248] X-SpamReason: No, hits=0.0 required=7.0 tests= X-StarScan-Received: X-StarScan-Version: 6.6.1.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 16060 invoked from network); 12 Sep 2012 20:47:26 -0000 Received: from mx1.mbs-systems.net (HELO mx1.mbs-systems.net) (188.40.240.248) by server-7.tower-21.messagelabs.com with SMTP; 12 Sep 2012 20:47:26 -0000 Received: from localhost (localhost [127.0.0.1]) by mx1.mbs-systems.net (Postfix) with ESMTP id ED3EA5C30B; Wed, 12 Sep 2012 22:48:28 +0200 (CEST) Received: from mx1.mbs-systems.net ([127.0.0.1]) by localhost (mta.mbs-systems.net [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id IyBQVz6JzNBx; Wed, 12 Sep 2012 22:48:27 +0200 (CEST) Received: from maiks-macbookpro.fritz.box (dslb-094-221-230-009.pools.arcor-ip.net [94.221.230.9]) by mx1.mbs-systems.net (Postfix) with ESMTPSA id A62C65C287; Wed, 12 Sep 2012 22:48:27 +0200 (CEST) Mime-Version: 1.0 (Apple Message framework v1278) From: Maik Brauer In-Reply-To: <1347445398.24226.37.camel@zakaz.uk.xensource.com> Date: Wed, 12 Sep 2012 22:47:21 +0200 Message-Id: <5CB14C04-2A76-4747-8209-EB5122DF7239@mbs-systems.net> References: <9F8FD2B0-450A-4A6E-A929-BA240ED1D997@mbs-systems.net> <1346746297.32462.37.camel@zakaz.uk.xensource.com> <1347266386.5305.17.camel@zakaz.uk.xensource.com> <4957C391-6070-47C1-A2AC-991ED1C1766A@mbs-systems.net> <1347289853.5305.105.camel@zakaz.uk.xensource.com> <4BCC413D-1697-4681-AF28-118D1623AF1C@mbs-systems.net> <1347445398.24226.37.camel@zakaz.uk.xensource.com> To: Ian Campbell X-Mailer: Apple Mail (2.1278) Cc: xen-users@lists.xen.org Subject: Re: [Xen-users] Dom0 crashed when rebooting whilst DomU are running X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org On Sep 12, 2012, at 12:23 PM, Ian Campbell wrote: > On Tue, 2012-09-11 at 23:46 +0100, Maik Brauer wrote: >> You can easiliy reproduce this issue, when using more that 3 Network >> devices. > > I installed a PV guest on Debian Wheezy using 5 vifs all on the same > bridge and could not reproduce this, the domain was successfully > shutdown on reboot. > > I also replaced the Debian xendomains script with the one from > xen-4.1-testing (since Debian's differs). Still no repro. > Hi Ian, please try it with the stable squeeze one. Because I am currently not using an unstable version. I have customers running on that machines so I can't experiment. Can you please try with Debian 64bit? > Ian. > > > _______________________________________________ > Xen-users mailing list > Xen-users@lists.xen.org > http://lists.xen.org/xen-users _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Wed Sep 12 21:32:31 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Wed, 12 Sep 2012 21:32:31 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TBuWg-0004VC-4v; Wed, 12 Sep 2012 21:31:14 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TBuWe-0004V7-NX for xen-users@lists.xen.org; Wed, 12 Sep 2012 21:31:13 +0000 Received: from [85.158.138.51:31552] by server-11.bemta-3.messagelabs.com id DD/0E-30250-E1FF0505; Wed, 12 Sep 2012 21:31:10 +0000 X-Env-Sender: maik.brauer@mbs-systems.net X-Msg-Ref: server-2.tower-174.messagelabs.com!1347485469!30215068!1 X-Originating-IP: [188.40.240.248] X-SpamReason: No, hits=0.5 required=7.0 tests=BODY_RANDOM_LONG X-StarScan-Received: X-StarScan-Version: 6.6.1.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 7728 invoked from network); 12 Sep 2012 21:31:09 -0000 Received: from mx1.mbs-systems.net (HELO mx1.mbs-systems.net) (188.40.240.248) by server-2.tower-174.messagelabs.com with SMTP; 12 Sep 2012 21:31:09 -0000 Received: from localhost (localhost [127.0.0.1]) by mx1.mbs-systems.net (Postfix) with ESMTP id 14B1D5C30B; Wed, 12 Sep 2012 23:32:12 +0200 (CEST) Received: from mx1.mbs-systems.net ([127.0.0.1]) by localhost (mta.mbs-systems.net [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ALqHOKv2hVuz; Wed, 12 Sep 2012 23:32:10 +0200 (CEST) Received: from maiks-macbookpro.fritz.box (dslb-094-221-230-009.pools.arcor-ip.net [94.221.230.9]) by mx1.mbs-systems.net (Postfix) with ESMTPSA id ACA4A5C287; Wed, 12 Sep 2012 23:32:10 +0200 (CEST) Mime-Version: 1.0 (Apple Message framework v1278) From: Maik Brauer In-Reply-To: <1347437617.25803.17.camel@dagon.hellion.org.uk> Date: Wed, 12 Sep 2012 23:31:05 +0200 Message-Id: <6B236806-1A92-4321-8E1A-A97CF584DEB2@mbs-systems.net> References: <9F8FD2B0-450A-4A6E-A929-BA240ED1D997@mbs-systems.net> <1346746297.32462.37.camel@zakaz.uk.xensource.com> <1347266386.5305.17.camel@zakaz.uk.xensource.com> <4957C391-6070-47C1-A2AC-991ED1C1766A@mbs-systems.net> <1347289853.5305.105.camel@zakaz.uk.xensource.com> <4BCC413D-1697-4681-AF28-118D1623AF1C@mbs-systems.net> <1347437617.25803.17.camel@dagon.hellion.org.uk> To: Ian Campbell X-Mailer: Apple Mail (2.1278) Cc: "xen-users@lists.xen.org" Subject: Re: [Xen-users] Dom0 crashed when rebooting whilst DomU are running X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org On Sep 12, 2012, at 10:13 AM, Ian Campbell wrote: > On Tue, 2012-09-11 at 23:46 +0100, Maik Brauer wrote: >>>>>> I found out that it hangs during re-boot of dom0 when having more >>>>>> Network interfaces involved, like: >>>>>> vif = [ 'mac=06:46:AB:CC:11:01, ip=', '', '', >>>>>> 'mac=06:04:AB:BB:11:03, bridge=VLAN20, script=vif-bridge', '', >>>>>> 'mac=06:04:AB:BB:11:05, bridge=VLAN40, script=vif-bridge' ] >>>>> >>>>> 6 interfaces total, 3 of which have a random mac on each reboot and all >>>>> get put on the default bridge? >>>> >>>> No, not really. The bridge is different for each interface. >>> >>> You have three lots of '' which will all go onto the same bridge AFAICT >>> (whichever one is determined to be the default) >> >> That is right. As long as I put nothing inside that it should be a >> different script to execute, it will use default for '' > > The default is "vif-bridge". Have you changed the default? No I did not change this default script. Everything is at is has been delivered in the Xen Source package. > > If not then your configuration as shown will put three interfaces on the > *same* bridge. Is this really what you want? No, because it will "not" put everything on the same bridge, because the default setting is "routed mode" due to the fact that my providers network configuration has changed the routing. Therefore in xend-config.sxp we have the following disabled: #(network-script network-route) #(vif-script vif-route) and the next one enabled: (network-script network-route) (vif-script vif-route) So basically you can see them as placeholder for the eth1, eth2 and eth4 devices in the Guest domU. For the other 2 interfaces it is different. They should be bridged (different from default). Therefore I have to put the "script=vif-bridge" in the config as shown above. See below the output of brctl show: bridge name bridge id STP enabled interfaces VLAN11 8000.000000000000 no VLAN12 8000.000000000000 no VLAN20 8000.feffffffffff no vif2.3 VLAN30 8000.000000000000 no VLAN40 8000.feffffffffff no vif2.5 > > You claim above that the bridge is different for each interface, but > unless you have changed something somewhere then this is not the case. > Since you are having problems it is important to identify everything > which you have changed from the defaults. No, I am saying that the bridge name is different. Not that the script is different. I am just creating isolated bridges VLAN20, VLAN30, VLAN40, and so on in order to connect special network interfaces together from different domU's. > >>>> List is empty. SysRQ -w and SysRQ-t shows nothing at all. >>> >>> You might need to increase the log verbosity with SysRQ-9 first? >> >> I did and now I got more Information. But due to the amount of data which slips over the console screen I am not able >> to record properly. Can you advice what to do here? > > Like I said "that list can be quite long so it is useless > without a serial console": http://wiki.xen.org/wiki/Xen_Serial_Console This will be a challenge. > > Depending on your distro you might also find this info in the logs > under /var/log somewhere. > There is not really useful information available. It will not print the info we need. I checked it already. >>> >>>> There is nothing running anymore. >>>> It shows periodically: INFO: task xenwatch:12 blocked for more than 120 seconds >>> >>> What is the very last thing printed before this? >> >> There is nothing before. > > So the output is silent from boot until this message comes up? That > seems unlikely, since there should be plenty of messages from the > shutdown process itself if nothing else. Yes there a plenty of messages. Let me put some lines below: Stopping NFS Daemon Stopping portmap daemon. Deconfiguring network interfaces Listening on LPF/eth0/00:1c:42:77:7a:29 Sending on LPF/eth0/00:1c:42:77:7a:29 DHCPRELEASE on eth0 Cleaning up ifdown. Saving system clock. Deactivating swap. Will now restart. [ 720.213710] INFO: task xenwatch:12 blocked for more than 120 seconds [ 720.213.753] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message [ 840.212.745] INFO: task reboot:3347 blocked for more than 120 seconds [ 840.212.785] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message (last INFO messages will repeat infinitely) > > What is the last message one the screen before this one? In fact what is > the entire last screenfull of output? > See above. >>> Really the initscript ought to wait, the default at least with the >>> script shipped with xen is to do so, by using shutdown --wait. can you >>> confirm whether or not this is happening for you? >> >> At least I can see that the shutdown --wait is in the scripts. So it seems that the init script is waiting. >> But independent from that, something must be still in use. Which block the reboot process. >>> >>> Possibly someone is trying to talk to xenstore after xenstored has >>> exited -- I expect that would cause the sorts of blocked for 120 >>> messages you are seeing. >>> >> Could be, but we need to find out what is blocking the shutdown. I do not know what else I can do in order to measure and collect >> data for investigation. > > Did you add debugging to the hotplug scripts like I suggested a couple > of mails back? No I didn't up to now. > > If you run the xendomains script by hand and then *immediately* after it > exits run "xl list" have the domains actually gone? You could even stick > some calls to xl list into the script itself and verify that the domains > are indeed shutting down as expected. root@xenserver:/etc/xen/scripts# xm list Name ID Mem VCPUs State Time(s) Domain-0 0 880 1 r----- 82.4 dnssrv01-v6 3 128 1 -b---- 4.5 root@xenserver:/etc/xen/scripts# /etc/init.d/xendomains stop Shutting down Xen domains: dnssrv01-v6(save)... [done]. root@xenserver:/etc/xen/scripts# xm list Name ID Mem VCPUs State Time(s) Domain-0 0 880 1 r----- 89.4 root@xenserver:/etc/xen/scripts# > > BTW Are you using xl or xend? I am using xend. > > Ian. > > > _______________________________________________ > Xen-users mailing list > Xen-users@lists.xen.org > http://lists.xen.org/xen-users _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Wed Sep 12 21:32:31 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Wed, 12 Sep 2012 21:32:31 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TBuWg-0004VC-4v; Wed, 12 Sep 2012 21:31:14 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TBuWe-0004V7-NX for xen-users@lists.xen.org; Wed, 12 Sep 2012 21:31:13 +0000 Received: from [85.158.138.51:31552] by server-11.bemta-3.messagelabs.com id DD/0E-30250-E1FF0505; Wed, 12 Sep 2012 21:31:10 +0000 X-Env-Sender: maik.brauer@mbs-systems.net X-Msg-Ref: server-2.tower-174.messagelabs.com!1347485469!30215068!1 X-Originating-IP: [188.40.240.248] X-SpamReason: No, hits=0.5 required=7.0 tests=BODY_RANDOM_LONG X-StarScan-Received: X-StarScan-Version: 6.6.1.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 7728 invoked from network); 12 Sep 2012 21:31:09 -0000 Received: from mx1.mbs-systems.net (HELO mx1.mbs-systems.net) (188.40.240.248) by server-2.tower-174.messagelabs.com with SMTP; 12 Sep 2012 21:31:09 -0000 Received: from localhost (localhost [127.0.0.1]) by mx1.mbs-systems.net (Postfix) with ESMTP id 14B1D5C30B; Wed, 12 Sep 2012 23:32:12 +0200 (CEST) Received: from mx1.mbs-systems.net ([127.0.0.1]) by localhost (mta.mbs-systems.net [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ALqHOKv2hVuz; Wed, 12 Sep 2012 23:32:10 +0200 (CEST) Received: from maiks-macbookpro.fritz.box (dslb-094-221-230-009.pools.arcor-ip.net [94.221.230.9]) by mx1.mbs-systems.net (Postfix) with ESMTPSA id ACA4A5C287; Wed, 12 Sep 2012 23:32:10 +0200 (CEST) Mime-Version: 1.0 (Apple Message framework v1278) From: Maik Brauer In-Reply-To: <1347437617.25803.17.camel@dagon.hellion.org.uk> Date: Wed, 12 Sep 2012 23:31:05 +0200 Message-Id: <6B236806-1A92-4321-8E1A-A97CF584DEB2@mbs-systems.net> References: <9F8FD2B0-450A-4A6E-A929-BA240ED1D997@mbs-systems.net> <1346746297.32462.37.camel@zakaz.uk.xensource.com> <1347266386.5305.17.camel@zakaz.uk.xensource.com> <4957C391-6070-47C1-A2AC-991ED1C1766A@mbs-systems.net> <1347289853.5305.105.camel@zakaz.uk.xensource.com> <4BCC413D-1697-4681-AF28-118D1623AF1C@mbs-systems.net> <1347437617.25803.17.camel@dagon.hellion.org.uk> To: Ian Campbell X-Mailer: Apple Mail (2.1278) Cc: "xen-users@lists.xen.org" Subject: Re: [Xen-users] Dom0 crashed when rebooting whilst DomU are running X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org On Sep 12, 2012, at 10:13 AM, Ian Campbell wrote: > On Tue, 2012-09-11 at 23:46 +0100, Maik Brauer wrote: >>>>>> I found out that it hangs during re-boot of dom0 when having more >>>>>> Network interfaces involved, like: >>>>>> vif = [ 'mac=06:46:AB:CC:11:01, ip=', '', '', >>>>>> 'mac=06:04:AB:BB:11:03, bridge=VLAN20, script=vif-bridge', '', >>>>>> 'mac=06:04:AB:BB:11:05, bridge=VLAN40, script=vif-bridge' ] >>>>> >>>>> 6 interfaces total, 3 of which have a random mac on each reboot and all >>>>> get put on the default bridge? >>>> >>>> No, not really. The bridge is different for each interface. >>> >>> You have three lots of '' which will all go onto the same bridge AFAICT >>> (whichever one is determined to be the default) >> >> That is right. As long as I put nothing inside that it should be a >> different script to execute, it will use default for '' > > The default is "vif-bridge". Have you changed the default? No I did not change this default script. Everything is at is has been delivered in the Xen Source package. > > If not then your configuration as shown will put three interfaces on the > *same* bridge. Is this really what you want? No, because it will "not" put everything on the same bridge, because the default setting is "routed mode" due to the fact that my providers network configuration has changed the routing. Therefore in xend-config.sxp we have the following disabled: #(network-script network-route) #(vif-script vif-route) and the next one enabled: (network-script network-route) (vif-script vif-route) So basically you can see them as placeholder for the eth1, eth2 and eth4 devices in the Guest domU. For the other 2 interfaces it is different. They should be bridged (different from default). Therefore I have to put the "script=vif-bridge" in the config as shown above. See below the output of brctl show: bridge name bridge id STP enabled interfaces VLAN11 8000.000000000000 no VLAN12 8000.000000000000 no VLAN20 8000.feffffffffff no vif2.3 VLAN30 8000.000000000000 no VLAN40 8000.feffffffffff no vif2.5 > > You claim above that the bridge is different for each interface, but > unless you have changed something somewhere then this is not the case. > Since you are having problems it is important to identify everything > which you have changed from the defaults. No, I am saying that the bridge name is different. Not that the script is different. I am just creating isolated bridges VLAN20, VLAN30, VLAN40, and so on in order to connect special network interfaces together from different domU's. > >>>> List is empty. SysRQ -w and SysRQ-t shows nothing at all. >>> >>> You might need to increase the log verbosity with SysRQ-9 first? >> >> I did and now I got more Information. But due to the amount of data which slips over the console screen I am not able >> to record properly. Can you advice what to do here? > > Like I said "that list can be quite long so it is useless > without a serial console": http://wiki.xen.org/wiki/Xen_Serial_Console This will be a challenge. > > Depending on your distro you might also find this info in the logs > under /var/log somewhere. > There is not really useful information available. It will not print the info we need. I checked it already. >>> >>>> There is nothing running anymore. >>>> It shows periodically: INFO: task xenwatch:12 blocked for more than 120 seconds >>> >>> What is the very last thing printed before this? >> >> There is nothing before. > > So the output is silent from boot until this message comes up? That > seems unlikely, since there should be plenty of messages from the > shutdown process itself if nothing else. Yes there a plenty of messages. Let me put some lines below: Stopping NFS Daemon Stopping portmap daemon. Deconfiguring network interfaces Listening on LPF/eth0/00:1c:42:77:7a:29 Sending on LPF/eth0/00:1c:42:77:7a:29 DHCPRELEASE on eth0 Cleaning up ifdown. Saving system clock. Deactivating swap. Will now restart. [ 720.213710] INFO: task xenwatch:12 blocked for more than 120 seconds [ 720.213.753] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message [ 840.212.745] INFO: task reboot:3347 blocked for more than 120 seconds [ 840.212.785] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message (last INFO messages will repeat infinitely) > > What is the last message one the screen before this one? In fact what is > the entire last screenfull of output? > See above. >>> Really the initscript ought to wait, the default at least with the >>> script shipped with xen is to do so, by using shutdown --wait. can you >>> confirm whether or not this is happening for you? >> >> At least I can see that the shutdown --wait is in the scripts. So it seems that the init script is waiting. >> But independent from that, something must be still in use. Which block the reboot process. >>> >>> Possibly someone is trying to talk to xenstore after xenstored has >>> exited -- I expect that would cause the sorts of blocked for 120 >>> messages you are seeing. >>> >> Could be, but we need to find out what is blocking the shutdown. I do not know what else I can do in order to measure and collect >> data for investigation. > > Did you add debugging to the hotplug scripts like I suggested a couple > of mails back? No I didn't up to now. > > If you run the xendomains script by hand and then *immediately* after it > exits run "xl list" have the domains actually gone? You could even stick > some calls to xl list into the script itself and verify that the domains > are indeed shutting down as expected. root@xenserver:/etc/xen/scripts# xm list Name ID Mem VCPUs State Time(s) Domain-0 0 880 1 r----- 82.4 dnssrv01-v6 3 128 1 -b---- 4.5 root@xenserver:/etc/xen/scripts# /etc/init.d/xendomains stop Shutting down Xen domains: dnssrv01-v6(save)... [done]. root@xenserver:/etc/xen/scripts# xm list Name ID Mem VCPUs State Time(s) Domain-0 0 880 1 r----- 89.4 root@xenserver:/etc/xen/scripts# > > BTW Are you using xl or xend? I am using xend. > > Ian. > > > _______________________________________________ > Xen-users mailing list > Xen-users@lists.xen.org > http://lists.xen.org/xen-users _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Wed Sep 12 22:24:56 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Wed, 12 Sep 2012 22:24:56 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TBvLY-00056N-L8; Wed, 12 Sep 2012 22:23:48 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TBvLX-00056I-27 for xen-users@lists.xen.org; Wed, 12 Sep 2012 22:23:47 +0000 Received: from [85.158.139.83:65278] by server-9.bemta-5.messagelabs.com id 71/FC-20529-27B01505; Wed, 12 Sep 2012 22:23:46 +0000 X-Env-Sender: skippyvondrake@gmail.com X-Msg-Ref: server-6.tower-182.messagelabs.com!1347488625!26293090!1 X-Originating-IP: [209.85.212.173] X-SpamReason: No, hits=0.3 required=7.0 tests=ML_RADAR_SPEW_LINKS_14, RCVD_BY_IP,spamassassin: X-StarScan-Received: X-StarScan-Version: 6.6.1.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 32194 invoked from network); 12 Sep 2012 22:23:45 -0000 Received: from mail-wi0-f173.google.com (HELO mail-wi0-f173.google.com) (209.85.212.173) by server-6.tower-182.messagelabs.com with RC4-SHA encrypted SMTP; 12 Sep 2012 22:23:45 -0000 Received: by wibhm6 with SMTP id hm6so4722876wib.14 for ; Wed, 12 Sep 2012 15:23:45 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:date:message-id:subject:from:to:content-type; bh=lYmI8UQjTtTuK79pm0y0bM1OeId4YKRK6KkSVZf6ihY=; b=c8JpvPQDGwMHQUV993LKDDdnJJHmVMO2quMW8/J3gAFWRUrMGujmXhg2H+3wQOMJs+ dFNCRO7KA0XM8CTwmavtG0VUXJvaV5EZIzY1QzhC1VhlHsnPRcUL5yR7H8e4Ko29ItAm 2/ZjLUxT5mGJfagB4QiyCJYDVQ0o+ysWeWIBWFrQvAAFqnKaFcAuWlxywYdl/g6b6ohW 0XWYPBJbFbR7sOirFUoRM3L4Ok2FtEcgaS9cyj/DWSuqR3WaHtb6Vzs/mvDSkzbt4w2a P3jrIgJGvCrF2TJZLwQI8RjFGGKEkboNRKsXbm82Vvwsmi4PUSu3GGK7+A40D5cYx+YC 2i+w== MIME-Version: 1.0 Received: by 10.216.132.135 with SMTP id o7mr22061wei.6.1347488625583; Wed, 12 Sep 2012 15:23:45 -0700 (PDT) Received: by 10.194.79.103 with HTTP; Wed, 12 Sep 2012 15:23:45 -0700 (PDT) Date: Wed, 12 Sep 2012 18:23:45 -0400 Message-ID: From: Skippy VonDrake To: xen-users@lists.xen.org Subject: [Xen-users] new pv stuck in pause X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org Following a Xen tutorial but can't get the VM (PV Squeeze) running. After doing: # xm create -c /etc/xen/tutorial-pv-guest.cfg The prompt just sits there. Opening another terminal: # xm list /usr/lib/python2.7/dist-packages Name ID Mem VCPUs State Time(s) Domain-0 0 7199 4 r----- 40.6 tutorial-pv-guest 1 512 0 --p--- 0.0 I'm using Ubuntu 12.04 (64bit) and got Xen built from source using the "make world" instructions. Not sure what information to provide so I pasted a few logs on pastebin. http://pastebin.com/jwjBFnhE xend log http://pastebin.com/4Bv2EKGK pv creation log http://pastebin.com/73eaFs6m xen-tools-conf Hope this is a simple problem... _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Wed Sep 12 22:24:56 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Wed, 12 Sep 2012 22:24:56 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TBvLY-00056N-L8; Wed, 12 Sep 2012 22:23:48 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TBvLX-00056I-27 for xen-users@lists.xen.org; Wed, 12 Sep 2012 22:23:47 +0000 Received: from [85.158.139.83:65278] by server-9.bemta-5.messagelabs.com id 71/FC-20529-27B01505; Wed, 12 Sep 2012 22:23:46 +0000 X-Env-Sender: skippyvondrake@gmail.com X-Msg-Ref: server-6.tower-182.messagelabs.com!1347488625!26293090!1 X-Originating-IP: [209.85.212.173] X-SpamReason: No, hits=0.3 required=7.0 tests=ML_RADAR_SPEW_LINKS_14, RCVD_BY_IP,spamassassin: X-StarScan-Received: X-StarScan-Version: 6.6.1.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 32194 invoked from network); 12 Sep 2012 22:23:45 -0000 Received: from mail-wi0-f173.google.com (HELO mail-wi0-f173.google.com) (209.85.212.173) by server-6.tower-182.messagelabs.com with RC4-SHA encrypted SMTP; 12 Sep 2012 22:23:45 -0000 Received: by wibhm6 with SMTP id hm6so4722876wib.14 for ; Wed, 12 Sep 2012 15:23:45 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:date:message-id:subject:from:to:content-type; bh=lYmI8UQjTtTuK79pm0y0bM1OeId4YKRK6KkSVZf6ihY=; b=c8JpvPQDGwMHQUV993LKDDdnJJHmVMO2quMW8/J3gAFWRUrMGujmXhg2H+3wQOMJs+ dFNCRO7KA0XM8CTwmavtG0VUXJvaV5EZIzY1QzhC1VhlHsnPRcUL5yR7H8e4Ko29ItAm 2/ZjLUxT5mGJfagB4QiyCJYDVQ0o+ysWeWIBWFrQvAAFqnKaFcAuWlxywYdl/g6b6ohW 0XWYPBJbFbR7sOirFUoRM3L4Ok2FtEcgaS9cyj/DWSuqR3WaHtb6Vzs/mvDSkzbt4w2a P3jrIgJGvCrF2TJZLwQI8RjFGGKEkboNRKsXbm82Vvwsmi4PUSu3GGK7+A40D5cYx+YC 2i+w== MIME-Version: 1.0 Received: by 10.216.132.135 with SMTP id o7mr22061wei.6.1347488625583; Wed, 12 Sep 2012 15:23:45 -0700 (PDT) Received: by 10.194.79.103 with HTTP; Wed, 12 Sep 2012 15:23:45 -0700 (PDT) Date: Wed, 12 Sep 2012 18:23:45 -0400 Message-ID: From: Skippy VonDrake To: xen-users@lists.xen.org Subject: [Xen-users] new pv stuck in pause X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org Following a Xen tutorial but can't get the VM (PV Squeeze) running. After doing: # xm create -c /etc/xen/tutorial-pv-guest.cfg The prompt just sits there. Opening another terminal: # xm list /usr/lib/python2.7/dist-packages Name ID Mem VCPUs State Time(s) Domain-0 0 7199 4 r----- 40.6 tutorial-pv-guest 1 512 0 --p--- 0.0 I'm using Ubuntu 12.04 (64bit) and got Xen built from source using the "make world" instructions. Not sure what information to provide so I pasted a few logs on pastebin. http://pastebin.com/jwjBFnhE xend log http://pastebin.com/4Bv2EKGK pv creation log http://pastebin.com/73eaFs6m xen-tools-conf Hope this is a simple problem... _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Wed Sep 12 22:36:33 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Wed, 12 Sep 2012 22:36:33 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TBvWq-0005SI-2z; Wed, 12 Sep 2012 22:35:28 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TBvWp-0005SC-6H for xen-users@lists.xen.org; Wed, 12 Sep 2012 22:35:27 +0000 Received: from [85.158.143.99:8322] by server-3.bemta-4.messagelabs.com id CB/1C-08232-E2E01505; Wed, 12 Sep 2012 22:35:26 +0000 X-Env-Sender: fajar@fajar.net X-Msg-Ref: server-15.tower-216.messagelabs.com!1347489324!30037799!1 X-Originating-IP: [209.85.214.173] X-SpamReason: No, hits=0.3 required=7.0 tests=RCVD_BY_IP X-StarScan-Received: X-StarScan-Version: 6.6.1.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 30894 invoked from network); 12 Sep 2012 22:35:25 -0000 Received: from mail-ob0-f173.google.com (HELO mail-ob0-f173.google.com) (209.85.214.173) by server-15.tower-216.messagelabs.com with RC4-SHA encrypted SMTP; 12 Sep 2012 22:35:25 -0000 Received: by obbta14 with SMTP id ta14so4318599obb.32 for ; Wed, 12 Sep 2012 15:35:23 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:x-gm-message-state; bh=S9PgRdyFWdE9Kvv0S97gITsSH9wvEw1FSZMqUkXlI9U=; b=b0AONTc8Yq4BCsUs7RnDa+r6dc7Tz2M/RLMl16XM0tczLyzbNewCa/gfUul+4Jo5mw 1644SkNd4j8QJUAyUAlbB+Wyd57gPH+oyaHVO7aoP5ToGtuf1n5r02vVwJitfEc/BUhQ hrgRwQO3M6J12hJBkBIvKbSpRMxenV+yh33ALVWn80dIn+s4z/59cCCjLZeAJH3WUqlt qdQO7vmBRKAMaBGu/IqCFIgc14wl2OFiIkj8E+f9uMdUHFFchkmtaZ40F+ltQ+pBT5YG RPdVTX+EjmRJhj8B91ed4S0sVtCl8yU/Hzx1ticgYiK+PgroMVypgwOBLMAUS+gUc2u2 OSPg== MIME-Version: 1.0 Received: by 10.60.7.138 with SMTP id j10mr24161628oea.104.1347489323701; Wed, 12 Sep 2012 15:35:23 -0700 (PDT) Received: by 10.60.6.230 with HTTP; Wed, 12 Sep 2012 15:35:23 -0700 (PDT) In-Reply-To: References: Date: Thu, 13 Sep 2012 05:35:23 +0700 Message-ID: From: "Fajar A. Nugraha" To: Skippy VonDrake X-Gm-Message-State: ALoCoQlsrpNhIYOdWsI64urHXg1XZi7uFOf/fVFkeZjq+5bgGzcN2exulzPDBBDToVFmLcqHgarN Cc: xen-users@lists.xen.org Subject: Re: [Xen-users] new pv stuck in pause X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org On Thu, Sep 13, 2012 at 5:23 AM, Skippy VonDrake wrote: > Following a Xen tutorial but can't get the VM (PV Squeeze) running. > > After doing: > # xm create -c /etc/xen/tutorial-pv-guest.cfg > > The prompt just sits there. > Opening another terminal: > > # xm list > /usr/lib/python2.7/dist-packages > Name ID Mem VCPUs State Time(s) > Domain-0 0 7199 4 r----- 40.6 > tutorial-pv-guest 1 512 0 --p--- 0.0 > > I'm using Ubuntu 12.04 (64bit) and got Xen built from source using > the "make world" instructions. > Not sure what information to provide so I pasted a few logs on pastebin. > > http://pastebin.com/jwjBFnhE xend log [2012-09-12 17:32:48 2533] DEBUG (XendBootloader:113) Launching bootloader as ['/usr/bin/pygrub', '--args=root=/dev/xvda2 ro ', '--output=/var/run/xend/boot/xenbl.748', '/dev/vg0/tutorial-pv-guest-disk']. That looks wrong. pygrub shouldn't need any "args", Try commenting-out whatever line in "/etc/xen/tutorial-pv-guest.cfg" that has a "root=/dev/xvda2 ro" in it. Also, what happens when you run "pygrub -i /dev/vg0/tutorial-pv-guest-disk" manually? -- Fajar _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Wed Sep 12 22:36:33 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Wed, 12 Sep 2012 22:36:33 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TBvWq-0005SI-2z; Wed, 12 Sep 2012 22:35:28 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TBvWp-0005SC-6H for xen-users@lists.xen.org; Wed, 12 Sep 2012 22:35:27 +0000 Received: from [85.158.143.99:8322] by server-3.bemta-4.messagelabs.com id CB/1C-08232-E2E01505; Wed, 12 Sep 2012 22:35:26 +0000 X-Env-Sender: fajar@fajar.net X-Msg-Ref: server-15.tower-216.messagelabs.com!1347489324!30037799!1 X-Originating-IP: [209.85.214.173] X-SpamReason: No, hits=0.3 required=7.0 tests=RCVD_BY_IP X-StarScan-Received: X-StarScan-Version: 6.6.1.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 30894 invoked from network); 12 Sep 2012 22:35:25 -0000 Received: from mail-ob0-f173.google.com (HELO mail-ob0-f173.google.com) (209.85.214.173) by server-15.tower-216.messagelabs.com with RC4-SHA encrypted SMTP; 12 Sep 2012 22:35:25 -0000 Received: by obbta14 with SMTP id ta14so4318599obb.32 for ; Wed, 12 Sep 2012 15:35:23 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:x-gm-message-state; bh=S9PgRdyFWdE9Kvv0S97gITsSH9wvEw1FSZMqUkXlI9U=; b=b0AONTc8Yq4BCsUs7RnDa+r6dc7Tz2M/RLMl16XM0tczLyzbNewCa/gfUul+4Jo5mw 1644SkNd4j8QJUAyUAlbB+Wyd57gPH+oyaHVO7aoP5ToGtuf1n5r02vVwJitfEc/BUhQ hrgRwQO3M6J12hJBkBIvKbSpRMxenV+yh33ALVWn80dIn+s4z/59cCCjLZeAJH3WUqlt qdQO7vmBRKAMaBGu/IqCFIgc14wl2OFiIkj8E+f9uMdUHFFchkmtaZ40F+ltQ+pBT5YG RPdVTX+EjmRJhj8B91ed4S0sVtCl8yU/Hzx1ticgYiK+PgroMVypgwOBLMAUS+gUc2u2 OSPg== MIME-Version: 1.0 Received: by 10.60.7.138 with SMTP id j10mr24161628oea.104.1347489323701; Wed, 12 Sep 2012 15:35:23 -0700 (PDT) Received: by 10.60.6.230 with HTTP; Wed, 12 Sep 2012 15:35:23 -0700 (PDT) In-Reply-To: References: Date: Thu, 13 Sep 2012 05:35:23 +0700 Message-ID: From: "Fajar A. Nugraha" To: Skippy VonDrake X-Gm-Message-State: ALoCoQlsrpNhIYOdWsI64urHXg1XZi7uFOf/fVFkeZjq+5bgGzcN2exulzPDBBDToVFmLcqHgarN Cc: xen-users@lists.xen.org Subject: Re: [Xen-users] new pv stuck in pause X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org On Thu, Sep 13, 2012 at 5:23 AM, Skippy VonDrake wrote: > Following a Xen tutorial but can't get the VM (PV Squeeze) running. > > After doing: > # xm create -c /etc/xen/tutorial-pv-guest.cfg > > The prompt just sits there. > Opening another terminal: > > # xm list > /usr/lib/python2.7/dist-packages > Name ID Mem VCPUs State Time(s) > Domain-0 0 7199 4 r----- 40.6 > tutorial-pv-guest 1 512 0 --p--- 0.0 > > I'm using Ubuntu 12.04 (64bit) and got Xen built from source using > the "make world" instructions. > Not sure what information to provide so I pasted a few logs on pastebin. > > http://pastebin.com/jwjBFnhE xend log [2012-09-12 17:32:48 2533] DEBUG (XendBootloader:113) Launching bootloader as ['/usr/bin/pygrub', '--args=root=/dev/xvda2 ro ', '--output=/var/run/xend/boot/xenbl.748', '/dev/vg0/tutorial-pv-guest-disk']. That looks wrong. pygrub shouldn't need any "args", Try commenting-out whatever line in "/etc/xen/tutorial-pv-guest.cfg" that has a "root=/dev/xvda2 ro" in it. Also, what happens when you run "pygrub -i /dev/vg0/tutorial-pv-guest-disk" manually? -- Fajar _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Thu Sep 13 05:40:28 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Thu, 13 Sep 2012 05:40:28 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TC28o-0004l6-Qc; Thu, 13 Sep 2012 05:39:06 +0000 Received: from mail27.messagelabs.com ([193.109.254.147]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TC28n-0004l1-Ps for xen-users@lists.xen.org; Thu, 13 Sep 2012 05:39:05 +0000 X-Env-Sender: Ian.Campbell@citrix.com X-Msg-Ref: server-10.tower-27.messagelabs.com!1347514739!5642478!1 X-Originating-IP: [62.200.22.115] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogNjIuMjAwLjIyLjExNSA9PiAxMDg4Njg=\n X-StarScan-Received: X-StarScan-Version: 6.6.1.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 24828 invoked from network); 13 Sep 2012 05:38:59 -0000 Received: from smtp.eu.citrix.com (HELO SMTP.EU.CITRIX.COM) (62.200.22.115) by server-10.tower-27.messagelabs.com with RC4-SHA encrypted SMTP; 13 Sep 2012 05:38:59 -0000 X-IronPort-AV: E=Sophos;i="4.80,413,1344211200"; d="scan'208";a="14509365" Received: from lonpmailmx01.citrite.net ([10.30.203.162]) by LONPIPO01.EU.CITRIX.COM with ESMTP/TLS/RC4-MD5; 13 Sep 2012 05:38:59 +0000 Received: from [127.0.0.1] (10.80.16.67) by smtprelay.citrix.com (10.30.203.162) with Microsoft SMTP Server id 8.3.279.1; Thu, 13 Sep 2012 06:38:59 +0100 Message-ID: <1347514738.25803.26.camel@dagon.hellion.org.uk> From: Ian Campbell To: Maik Brauer Date: Thu, 13 Sep 2012 06:38:58 +0100 In-Reply-To: <5CB14C04-2A76-4747-8209-EB5122DF7239@mbs-systems.net> References: <9F8FD2B0-450A-4A6E-A929-BA240ED1D997@mbs-systems.net> <1346746297.32462.37.camel@zakaz.uk.xensource.com> <1347266386.5305.17.camel@zakaz.uk.xensource.com> <4957C391-6070-47C1-A2AC-991ED1C1766A@mbs-systems.net> <1347289853.5305.105.camel@zakaz.uk.xensource.com> <4BCC413D-1697-4681-AF28-118D1623AF1C@mbs-systems.net> <1347445398.24226.37.camel@zakaz.uk.xensource.com> <5CB14C04-2A76-4747-8209-EB5122DF7239@mbs-systems.net> Organization: Citrix Systems, Inc. X-Mailer: Evolution 3.4.3-1 MIME-Version: 1.0 Cc: "xen-users@lists.xen.org" Subject: Re: [Xen-users] Dom0 crashed when rebooting whilst DomU are running X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org On Wed, 2012-09-12 at 21:47 +0100, Maik Brauer wrote: > On Sep 12, 2012, at 12:23 PM, Ian Campbell wrote: > > > On Tue, 2012-09-11 at 23:46 +0100, Maik Brauer wrote: > >> You can easiliy reproduce this issue, when using more that 3 Network > >> devices. > > > > I installed a PV guest on Debian Wheezy using 5 vifs all on the same > > bridge and could not reproduce this, the domain was successfully > > shutdown on reboot. > > > > I also replaced the Debian xendomains script with the one from > > xen-4.1-testing (since Debian's differs). Still no repro. > > > Hi Ian, please try it with the stable squeeze one. Because I am currently not using an unstable version. > I have customers running on that machines so I can't experiment. Can you please try with Debian 64bit? In your initial mail you said you were running a 4.1.3 hypervisor. Squeeze has 4.0. Which is it? Ian. > > > > Ian. > > > > > > _______________________________________________ > > Xen-users mailing list > > Xen-users@lists.xen.org > > http://lists.xen.org/xen-users > > > > _______________________________________________ > Xen-users mailing list > Xen-users@lists.xen.org > http://lists.xen.org/xen-users _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Thu Sep 13 05:40:28 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Thu, 13 Sep 2012 05:40:28 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TC28o-0004l6-Qc; Thu, 13 Sep 2012 05:39:06 +0000 Received: from mail27.messagelabs.com ([193.109.254.147]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TC28n-0004l1-Ps for xen-users@lists.xen.org; Thu, 13 Sep 2012 05:39:05 +0000 X-Env-Sender: Ian.Campbell@citrix.com X-Msg-Ref: server-10.tower-27.messagelabs.com!1347514739!5642478!1 X-Originating-IP: [62.200.22.115] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogNjIuMjAwLjIyLjExNSA9PiAxMDg4Njg=\n X-StarScan-Received: X-StarScan-Version: 6.6.1.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 24828 invoked from network); 13 Sep 2012 05:38:59 -0000 Received: from smtp.eu.citrix.com (HELO SMTP.EU.CITRIX.COM) (62.200.22.115) by server-10.tower-27.messagelabs.com with RC4-SHA encrypted SMTP; 13 Sep 2012 05:38:59 -0000 X-IronPort-AV: E=Sophos;i="4.80,413,1344211200"; d="scan'208";a="14509365" Received: from lonpmailmx01.citrite.net ([10.30.203.162]) by LONPIPO01.EU.CITRIX.COM with ESMTP/TLS/RC4-MD5; 13 Sep 2012 05:38:59 +0000 Received: from [127.0.0.1] (10.80.16.67) by smtprelay.citrix.com (10.30.203.162) with Microsoft SMTP Server id 8.3.279.1; Thu, 13 Sep 2012 06:38:59 +0100 Message-ID: <1347514738.25803.26.camel@dagon.hellion.org.uk> From: Ian Campbell To: Maik Brauer Date: Thu, 13 Sep 2012 06:38:58 +0100 In-Reply-To: <5CB14C04-2A76-4747-8209-EB5122DF7239@mbs-systems.net> References: <9F8FD2B0-450A-4A6E-A929-BA240ED1D997@mbs-systems.net> <1346746297.32462.37.camel@zakaz.uk.xensource.com> <1347266386.5305.17.camel@zakaz.uk.xensource.com> <4957C391-6070-47C1-A2AC-991ED1C1766A@mbs-systems.net> <1347289853.5305.105.camel@zakaz.uk.xensource.com> <4BCC413D-1697-4681-AF28-118D1623AF1C@mbs-systems.net> <1347445398.24226.37.camel@zakaz.uk.xensource.com> <5CB14C04-2A76-4747-8209-EB5122DF7239@mbs-systems.net> Organization: Citrix Systems, Inc. X-Mailer: Evolution 3.4.3-1 MIME-Version: 1.0 Cc: "xen-users@lists.xen.org" Subject: Re: [Xen-users] Dom0 crashed when rebooting whilst DomU are running X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org On Wed, 2012-09-12 at 21:47 +0100, Maik Brauer wrote: > On Sep 12, 2012, at 12:23 PM, Ian Campbell wrote: > > > On Tue, 2012-09-11 at 23:46 +0100, Maik Brauer wrote: > >> You can easiliy reproduce this issue, when using more that 3 Network > >> devices. > > > > I installed a PV guest on Debian Wheezy using 5 vifs all on the same > > bridge and could not reproduce this, the domain was successfully > > shutdown on reboot. > > > > I also replaced the Debian xendomains script with the one from > > xen-4.1-testing (since Debian's differs). Still no repro. > > > Hi Ian, please try it with the stable squeeze one. Because I am currently not using an unstable version. > I have customers running on that machines so I can't experiment. Can you please try with Debian 64bit? In your initial mail you said you were running a 4.1.3 hypervisor. Squeeze has 4.0. Which is it? Ian. > > > > Ian. > > > > > > _______________________________________________ > > Xen-users mailing list > > Xen-users@lists.xen.org > > http://lists.xen.org/xen-users > > > > _______________________________________________ > Xen-users mailing list > Xen-users@lists.xen.org > http://lists.xen.org/xen-users _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Thu Sep 13 05:53:05 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Thu, 13 Sep 2012 05:53:05 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TC2LC-00052u-H1; Thu, 13 Sep 2012 05:51:54 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TC2LA-00052l-Rs for xen-users@lists.xen.org; Thu, 13 Sep 2012 05:51:53 +0000 Received: from [85.158.143.35:25773] by server-2.bemta-4.messagelabs.com id A1/2D-21239-87471505; Thu, 13 Sep 2012 05:51:52 +0000 X-Env-Sender: Ian.Campbell@citrix.com X-Msg-Ref: server-2.tower-21.messagelabs.com!1347515482!7040772!1 X-Originating-IP: [62.200.22.115] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogNjIuMjAwLjIyLjExNSA9PiAxMDg4Njg=\n X-StarScan-Received: X-StarScan-Version: 6.6.1.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 30999 invoked from network); 13 Sep 2012 05:51:23 -0000 Received: from smtp.ctxuk.citrix.com (HELO SMTP.EU.CITRIX.COM) (62.200.22.115) by server-2.tower-21.messagelabs.com with RC4-SHA encrypted SMTP; 13 Sep 2012 05:51:23 -0000 X-IronPort-AV: E=Sophos;i="4.80,415,1344211200"; d="scan'208";a="14509460" Received: from lonpmailmx01.citrite.net ([10.30.203.162]) by LONPIPO01.EU.CITRIX.COM with ESMTP/TLS/RC4-MD5; 13 Sep 2012 05:51:22 +0000 Received: from [127.0.0.1] (10.80.16.66) by smtprelay.citrix.com (10.30.203.162) with Microsoft SMTP Server id 8.3.279.1; Thu, 13 Sep 2012 06:51:22 +0100 Message-ID: <1347515481.25803.36.camel@dagon.hellion.org.uk> From: Ian Campbell To: Maik Brauer Date: Thu, 13 Sep 2012 06:51:21 +0100 In-Reply-To: <5CB14C04-2A76-4747-8209-EB5122DF7239@mbs-systems.net> References: <9F8FD2B0-450A-4A6E-A929-BA240ED1D997@mbs-systems.net> <1346746297.32462.37.camel@zakaz.uk.xensource.com> <1347266386.5305.17.camel@zakaz.uk.xensource.com> <4957C391-6070-47C1-A2AC-991ED1C1766A@mbs-systems.net> <1347289853.5305.105.camel@zakaz.uk.xensource.com> <4BCC413D-1697-4681-AF28-118D1623AF1C@mbs-systems.net> <1347445398.24226.37.camel@zakaz.uk.xensource.com> <5CB14C04-2A76-4747-8209-EB5122DF7239@mbs-systems.net> Organization: Citrix Systems, Inc. X-Mailer: Evolution 3.4.3-1 MIME-Version: 1.0 Cc: "xen-users@lists.xen.org" Subject: Re: [Xen-users] Dom0 crashed when rebooting whilst DomU are running X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org On Wed, 2012-09-12 at 21:47 +0100, Maik Brauer wrote: > On Sep 12, 2012, at 12:23 PM, Ian Campbell wrote: > > > On Tue, 2012-09-11 at 23:46 +0100, Maik Brauer wrote: > >> You can easiliy reproduce this issue, when using more that 3 Network > >> devices. > > > > I installed a PV guest on Debian Wheezy using 5 vifs all on the same > > bridge and could not reproduce this, the domain was successfully > > shutdown on reboot. > > > > I also replaced the Debian xendomains script with the one from > > xen-4.1-testing (since Debian's differs). Still no repro. > > > Hi Ian, please try it with the stable squeeze one. Because I am currently not using an unstable version. > I have customers running on that machines so I can't experiment. What about one of the several machines you have installed at home which show this issue? _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Thu Sep 13 05:53:05 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Thu, 13 Sep 2012 05:53:05 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TC2LC-00052u-H1; Thu, 13 Sep 2012 05:51:54 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TC2LA-00052l-Rs for xen-users@lists.xen.org; Thu, 13 Sep 2012 05:51:53 +0000 Received: from [85.158.143.35:25773] by server-2.bemta-4.messagelabs.com id A1/2D-21239-87471505; Thu, 13 Sep 2012 05:51:52 +0000 X-Env-Sender: Ian.Campbell@citrix.com X-Msg-Ref: server-2.tower-21.messagelabs.com!1347515482!7040772!1 X-Originating-IP: [62.200.22.115] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogNjIuMjAwLjIyLjExNSA9PiAxMDg4Njg=\n X-StarScan-Received: X-StarScan-Version: 6.6.1.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 30999 invoked from network); 13 Sep 2012 05:51:23 -0000 Received: from smtp.ctxuk.citrix.com (HELO SMTP.EU.CITRIX.COM) (62.200.22.115) by server-2.tower-21.messagelabs.com with RC4-SHA encrypted SMTP; 13 Sep 2012 05:51:23 -0000 X-IronPort-AV: E=Sophos;i="4.80,415,1344211200"; d="scan'208";a="14509460" Received: from lonpmailmx01.citrite.net ([10.30.203.162]) by LONPIPO01.EU.CITRIX.COM with ESMTP/TLS/RC4-MD5; 13 Sep 2012 05:51:22 +0000 Received: from [127.0.0.1] (10.80.16.66) by smtprelay.citrix.com (10.30.203.162) with Microsoft SMTP Server id 8.3.279.1; Thu, 13 Sep 2012 06:51:22 +0100 Message-ID: <1347515481.25803.36.camel@dagon.hellion.org.uk> From: Ian Campbell To: Maik Brauer Date: Thu, 13 Sep 2012 06:51:21 +0100 In-Reply-To: <5CB14C04-2A76-4747-8209-EB5122DF7239@mbs-systems.net> References: <9F8FD2B0-450A-4A6E-A929-BA240ED1D997@mbs-systems.net> <1346746297.32462.37.camel@zakaz.uk.xensource.com> <1347266386.5305.17.camel@zakaz.uk.xensource.com> <4957C391-6070-47C1-A2AC-991ED1C1766A@mbs-systems.net> <1347289853.5305.105.camel@zakaz.uk.xensource.com> <4BCC413D-1697-4681-AF28-118D1623AF1C@mbs-systems.net> <1347445398.24226.37.camel@zakaz.uk.xensource.com> <5CB14C04-2A76-4747-8209-EB5122DF7239@mbs-systems.net> Organization: Citrix Systems, Inc. X-Mailer: Evolution 3.4.3-1 MIME-Version: 1.0 Cc: "xen-users@lists.xen.org" Subject: Re: [Xen-users] Dom0 crashed when rebooting whilst DomU are running X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org On Wed, 2012-09-12 at 21:47 +0100, Maik Brauer wrote: > On Sep 12, 2012, at 12:23 PM, Ian Campbell wrote: > > > On Tue, 2012-09-11 at 23:46 +0100, Maik Brauer wrote: > >> You can easiliy reproduce this issue, when using more that 3 Network > >> devices. > > > > I installed a PV guest on Debian Wheezy using 5 vifs all on the same > > bridge and could not reproduce this, the domain was successfully > > shutdown on reboot. > > > > I also replaced the Debian xendomains script with the one from > > xen-4.1-testing (since Debian's differs). Still no repro. > > > Hi Ian, please try it with the stable squeeze one. Because I am currently not using an unstable version. > I have customers running on that machines so I can't experiment. What about one of the several machines you have installed at home which show this issue? _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Thu Sep 13 05:53:07 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Thu, 13 Sep 2012 05:53:07 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TC2LD-000533-45; Thu, 13 Sep 2012 05:51:55 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TC2LB-00052l-A8 for xen-users@lists.xen.org; Thu, 13 Sep 2012 05:51:53 +0000 Received: from [85.158.143.35:25798] by server-2.bemta-4.messagelabs.com id 92/2D-21239-87471505; Thu, 13 Sep 2012 05:51:52 +0000 X-Env-Sender: Ian.Campbell@citrix.com X-Msg-Ref: server-2.tower-21.messagelabs.com!1347515482!7040772!2 X-Originating-IP: [62.200.22.115] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogNjIuMjAwLjIyLjExNSA9PiAxMDg4Njg=\n X-StarScan-Received: X-StarScan-Version: 6.6.1.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 31101 invoked from network); 13 Sep 2012 05:51:26 -0000 Received: from smtp.ctxuk.citrix.com (HELO SMTP.EU.CITRIX.COM) (62.200.22.115) by server-2.tower-21.messagelabs.com with RC4-SHA encrypted SMTP; 13 Sep 2012 05:51:26 -0000 X-IronPort-AV: E=Sophos;i="4.80,415,1344211200"; d="scan'208";a="14509461" Received: from lonpmailmx01.citrite.net ([10.30.203.162]) by LONPIPO01.EU.CITRIX.COM with ESMTP/TLS/RC4-MD5; 13 Sep 2012 05:51:26 +0000 Received: from [127.0.0.1] (10.80.16.66) by smtprelay.citrix.com (10.30.203.162) with Microsoft SMTP Server id 8.3.279.1; Thu, 13 Sep 2012 06:51:26 +0100 Message-ID: <1347515485.25803.37.camel@dagon.hellion.org.uk> From: Ian Campbell To: Maik Brauer Date: Thu, 13 Sep 2012 06:51:25 +0100 In-Reply-To: <6B236806-1A92-4321-8E1A-A97CF584DEB2@mbs-systems.net> References: <9F8FD2B0-450A-4A6E-A929-BA240ED1D997@mbs-systems.net> <1346746297.32462.37.camel@zakaz.uk.xensource.com> <1347266386.5305.17.camel@zakaz.uk.xensource.com> <4957C391-6070-47C1-A2AC-991ED1C1766A@mbs-systems.net> <1347289853.5305.105.camel@zakaz.uk.xensource.com> <4BCC413D-1697-4681-AF28-118D1623AF1C@mbs-systems.net> <1347437617.25803.17.camel@dagon.hellion.org.uk> <6B236806-1A92-4321-8E1A-A97CF584DEB2@mbs-systems.net> Organization: Citrix Systems, Inc. X-Mailer: Evolution 3.4.3-1 MIME-Version: 1.0 Cc: "xen-users@lists.xen.org" Subject: Re: [Xen-users] Dom0 crashed when rebooting whilst DomU are running X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org On Wed, 2012-09-12 at 22:31 +0100, Maik Brauer wrote: > On Sep 12, 2012, at 10:13 AM, Ian Campbell wrote: > > The default is "vif-bridge". Have you changed the default? > > No I did not change this default script. Everything is at is has been delivered in the Xen Source package. No, it isn't, you say below that you have changed xend-config.sxp > > > > If not then your configuration as shown will put three interfaces on the > > *same* bridge. Is this really what you want? > > No, because it will "not" put everything on the same bridge, because the default setting is "routed mode" due to the fact that > my providers network configuration has changed the routing. Therefore in xend-config.sxp we have the following disabled: > #(network-script network-route) > #(vif-script vif-route) > > and the next one enabled: > (network-script network-route) > (vif-script vif-route) So you have changed the default then, haven't you! You have edited xend-config.sxp to change the default vif-script and network-script! What else have you changed from the defaults? > So basically you can see them as placeholder for the eth1, eth2 and eth4 devices in the Guest domU. > For the other 2 interfaces it is different. They should be bridged (different from default). Do you mean routed here? Do you understand the difference between routing and bridging? > Therefore I have to > put the "script=vif-bridge" in the config as shown above. See below the output of brctl show: > bridge name bridge id STP enabled interfaces > VLAN11 8000.000000000000 no > VLAN12 8000.000000000000 no > VLAN20 8000.feffffffffff no vif2.3 > VLAN30 8000.000000000000 no > VLAN40 8000.feffffffffff no vif2.5 > > > > > You claim above that the bridge is different for each interface, but > > unless you have changed something somewhere then this is not the case. > > Since you are having problems it is important to identify everything > > which you have changed from the defaults. > > No, I am saying that the bridge name is different. Not that the script is different. I am just creating isolated bridges > VLAN20, VLAN30, VLAN40, and so on in order to connect special network interfaces together from different domU's. Except it turns out that half your interfaces aren't even using bridging and aren't using vif-bridge at all! Please, it is important to give all the facts and to be precise when you are asking people to debug a remote system. > >>>> List is empty. SysRQ -w and SysRQ-t shows nothing at all. > >>> > >>> You might need to increase the log verbosity with SysRQ-9 first? > >> > >> I did and now I got more Information. But due to the amount of data > which slips over the console screen I am not able > >> to record properly. Can you advice what to do here? Did you try SysRQ-w -- given the point at which your logs show the hang this should provide a much smaller amount of output than Sysrq-l and be much more manageable. In particular it will be useful to know what the "xenwatch" and "reboot" processes are waiting for. > > Did you add debugging to the hotplug scripts like I suggested a couple > > of mails back? > > No I didn't up to now. Please do. For both the vif-bridge and vif-route scripts. Ian. _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Thu Sep 13 05:53:07 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Thu, 13 Sep 2012 05:53:07 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TC2LD-000533-45; Thu, 13 Sep 2012 05:51:55 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TC2LB-00052l-A8 for xen-users@lists.xen.org; Thu, 13 Sep 2012 05:51:53 +0000 Received: from [85.158.143.35:25798] by server-2.bemta-4.messagelabs.com id 92/2D-21239-87471505; Thu, 13 Sep 2012 05:51:52 +0000 X-Env-Sender: Ian.Campbell@citrix.com X-Msg-Ref: server-2.tower-21.messagelabs.com!1347515482!7040772!2 X-Originating-IP: [62.200.22.115] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogNjIuMjAwLjIyLjExNSA9PiAxMDg4Njg=\n X-StarScan-Received: X-StarScan-Version: 6.6.1.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 31101 invoked from network); 13 Sep 2012 05:51:26 -0000 Received: from smtp.ctxuk.citrix.com (HELO SMTP.EU.CITRIX.COM) (62.200.22.115) by server-2.tower-21.messagelabs.com with RC4-SHA encrypted SMTP; 13 Sep 2012 05:51:26 -0000 X-IronPort-AV: E=Sophos;i="4.80,415,1344211200"; d="scan'208";a="14509461" Received: from lonpmailmx01.citrite.net ([10.30.203.162]) by LONPIPO01.EU.CITRIX.COM with ESMTP/TLS/RC4-MD5; 13 Sep 2012 05:51:26 +0000 Received: from [127.0.0.1] (10.80.16.66) by smtprelay.citrix.com (10.30.203.162) with Microsoft SMTP Server id 8.3.279.1; Thu, 13 Sep 2012 06:51:26 +0100 Message-ID: <1347515485.25803.37.camel@dagon.hellion.org.uk> From: Ian Campbell To: Maik Brauer Date: Thu, 13 Sep 2012 06:51:25 +0100 In-Reply-To: <6B236806-1A92-4321-8E1A-A97CF584DEB2@mbs-systems.net> References: <9F8FD2B0-450A-4A6E-A929-BA240ED1D997@mbs-systems.net> <1346746297.32462.37.camel@zakaz.uk.xensource.com> <1347266386.5305.17.camel@zakaz.uk.xensource.com> <4957C391-6070-47C1-A2AC-991ED1C1766A@mbs-systems.net> <1347289853.5305.105.camel@zakaz.uk.xensource.com> <4BCC413D-1697-4681-AF28-118D1623AF1C@mbs-systems.net> <1347437617.25803.17.camel@dagon.hellion.org.uk> <6B236806-1A92-4321-8E1A-A97CF584DEB2@mbs-systems.net> Organization: Citrix Systems, Inc. X-Mailer: Evolution 3.4.3-1 MIME-Version: 1.0 Cc: "xen-users@lists.xen.org" Subject: Re: [Xen-users] Dom0 crashed when rebooting whilst DomU are running X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org On Wed, 2012-09-12 at 22:31 +0100, Maik Brauer wrote: > On Sep 12, 2012, at 10:13 AM, Ian Campbell wrote: > > The default is "vif-bridge". Have you changed the default? > > No I did not change this default script. Everything is at is has been delivered in the Xen Source package. No, it isn't, you say below that you have changed xend-config.sxp > > > > If not then your configuration as shown will put three interfaces on the > > *same* bridge. Is this really what you want? > > No, because it will "not" put everything on the same bridge, because the default setting is "routed mode" due to the fact that > my providers network configuration has changed the routing. Therefore in xend-config.sxp we have the following disabled: > #(network-script network-route) > #(vif-script vif-route) > > and the next one enabled: > (network-script network-route) > (vif-script vif-route) So you have changed the default then, haven't you! You have edited xend-config.sxp to change the default vif-script and network-script! What else have you changed from the defaults? > So basically you can see them as placeholder for the eth1, eth2 and eth4 devices in the Guest domU. > For the other 2 interfaces it is different. They should be bridged (different from default). Do you mean routed here? Do you understand the difference between routing and bridging? > Therefore I have to > put the "script=vif-bridge" in the config as shown above. See below the output of brctl show: > bridge name bridge id STP enabled interfaces > VLAN11 8000.000000000000 no > VLAN12 8000.000000000000 no > VLAN20 8000.feffffffffff no vif2.3 > VLAN30 8000.000000000000 no > VLAN40 8000.feffffffffff no vif2.5 > > > > > You claim above that the bridge is different for each interface, but > > unless you have changed something somewhere then this is not the case. > > Since you are having problems it is important to identify everything > > which you have changed from the defaults. > > No, I am saying that the bridge name is different. Not that the script is different. I am just creating isolated bridges > VLAN20, VLAN30, VLAN40, and so on in order to connect special network interfaces together from different domU's. Except it turns out that half your interfaces aren't even using bridging and aren't using vif-bridge at all! Please, it is important to give all the facts and to be precise when you are asking people to debug a remote system. > >>>> List is empty. SysRQ -w and SysRQ-t shows nothing at all. > >>> > >>> You might need to increase the log verbosity with SysRQ-9 first? > >> > >> I did and now I got more Information. But due to the amount of data > which slips over the console screen I am not able > >> to record properly. Can you advice what to do here? Did you try SysRQ-w -- given the point at which your logs show the hang this should provide a much smaller amount of output than Sysrq-l and be much more manageable. In particular it will be useful to know what the "xenwatch" and "reboot" processes are waiting for. > > Did you add debugging to the hotplug scripts like I suggested a couple > > of mails back? > > No I didn't up to now. Please do. For both the vif-bridge and vif-route scripts. Ian. _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Thu Sep 13 08:55:53 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Thu, 13 Sep 2012 08:55:53 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TC5C8-0008Jb-9A; Thu, 13 Sep 2012 08:54:44 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TC5C6-0008JW-LW for xen-users@lists.xen.org; Thu, 13 Sep 2012 08:54:42 +0000 Received: from [85.158.143.35:9464] by server-2.bemta-4.messagelabs.com id 70/37-21239-15F91505; Thu, 13 Sep 2012 08:54:41 +0000 X-Env-Sender: maik.brauer@mbs-systems.net X-Msg-Ref: server-14.tower-21.messagelabs.com!1347526448!18121103!1 X-Originating-IP: [188.40.240.248] X-SpamReason: No, hits=0.0 required=7.0 tests= X-StarScan-Received: X-StarScan-Version: 6.6.1.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 25274 invoked from network); 13 Sep 2012 08:54:13 -0000 Received: from mx1.mbs-systems.net (HELO mx1.mbs-systems.net) (188.40.240.248) by server-14.tower-21.messagelabs.com with SMTP; 13 Sep 2012 08:54:13 -0000 Received: from localhost (localhost [127.0.0.1]) by mx1.mbs-systems.net (Postfix) with ESMTP id DA0B25C30B; Thu, 13 Sep 2012 10:55:10 +0200 (CEST) Received: from mx1.mbs-systems.net ([127.0.0.1]) by localhost (mta.mbs-systems.net [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id l6G1EFY87ODE; Thu, 13 Sep 2012 10:55:09 +0200 (CEST) Received: from [62.213.145.97] (unknown [62.213.145.97]) by mx1.mbs-systems.net (Postfix) with ESMTPSA id 369805C2DA; Thu, 13 Sep 2012 10:55:09 +0200 (CEST) Mime-Version: 1.0 (Apple Message framework v1278) From: Maik Brauer In-Reply-To: <1347514738.25803.26.camel@dagon.hellion.org.uk> Date: Thu, 13 Sep 2012 10:54:03 +0200 Message-Id: References: <9F8FD2B0-450A-4A6E-A929-BA240ED1D997@mbs-systems.net> <1346746297.32462.37.camel@zakaz.uk.xensource.com> <1347266386.5305.17.camel@zakaz.uk.xensource.com> <4957C391-6070-47C1-A2AC-991ED1C1766A@mbs-systems.net> <1347289853.5305.105.camel@zakaz.uk.xensource.com> <4BCC413D-1697-4681-AF28-118D1623AF1C@mbs-systems.net> <1347445398.24226.37.camel@zakaz.uk.xensource.com> <5CB14C04-2A76-4747-8209-EB5122DF7239@mbs-systems.net> <1347514738.25803.26.camel@dagon.hellion.org.uk> To: Ian Campbell X-Mailer: Apple Mail (2.1278) Cc: "xen-users@lists.xen.org" Subject: Re: [Xen-users] Dom0 crashed when rebooting whilst DomU are running X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org On Sep 13, 2012, at 7:38 AM, Ian Campbell wrote: > On Wed, 2012-09-12 at 21:47 +0100, Maik Brauer wrote: >> On Sep 12, 2012, at 12:23 PM, Ian Campbell wrote: >> >>> On Tue, 2012-09-11 at 23:46 +0100, Maik Brauer wrote: >>>> You can easiliy reproduce this issue, when using more that 3 Network >>>> devices. >>> >>> I installed a PV guest on Debian Wheezy using 5 vifs all on the same >>> bridge and could not reproduce this, the domain was successfully >>> shutdown on reboot. >>> >>> I also replaced the Debian xendomains script with the one from >>> xen-4.1-testing (since Debian's differs). Still no repro. >>> >> Hi Ian, please try it with the stable squeeze one. Because I am currently not using an unstable version. >> I have customers running on that machines so I can't experiment. Can you please try with Debian 64bit? > > In your initial mail you said you were running a 4.1.3 hypervisor. > Squeeze has 4.0. Which is it? I am using Debian 5.0.7 (SQUEEZE), with the 4.1.3 Hypervisor and 2.6.32-5-xen-amd64 kernel. I am not using the Standard Packaged Hypervisor (4.0) shipped with Debian SQUEEZE. > > Ian. > >> >> >>> Ian. >>> >>> >>> _______________________________________________ >>> Xen-users mailing list >>> Xen-users@lists.xen.org >>> http://lists.xen.org/xen-users >> >> >> >> _______________________________________________ >> Xen-users mailing list >> Xen-users@lists.xen.org >> http://lists.xen.org/xen-users > > > > _______________________________________________ > Xen-users mailing list > Xen-users@lists.xen.org > http://lists.xen.org/xen-users _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Thu Sep 13 08:55:53 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Thu, 13 Sep 2012 08:55:53 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TC5C8-0008Jb-9A; Thu, 13 Sep 2012 08:54:44 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TC5C6-0008JW-LW for xen-users@lists.xen.org; Thu, 13 Sep 2012 08:54:42 +0000 Received: from [85.158.143.35:9464] by server-2.bemta-4.messagelabs.com id 70/37-21239-15F91505; Thu, 13 Sep 2012 08:54:41 +0000 X-Env-Sender: maik.brauer@mbs-systems.net X-Msg-Ref: server-14.tower-21.messagelabs.com!1347526448!18121103!1 X-Originating-IP: [188.40.240.248] X-SpamReason: No, hits=0.0 required=7.0 tests= X-StarScan-Received: X-StarScan-Version: 6.6.1.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 25274 invoked from network); 13 Sep 2012 08:54:13 -0000 Received: from mx1.mbs-systems.net (HELO mx1.mbs-systems.net) (188.40.240.248) by server-14.tower-21.messagelabs.com with SMTP; 13 Sep 2012 08:54:13 -0000 Received: from localhost (localhost [127.0.0.1]) by mx1.mbs-systems.net (Postfix) with ESMTP id DA0B25C30B; Thu, 13 Sep 2012 10:55:10 +0200 (CEST) Received: from mx1.mbs-systems.net ([127.0.0.1]) by localhost (mta.mbs-systems.net [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id l6G1EFY87ODE; Thu, 13 Sep 2012 10:55:09 +0200 (CEST) Received: from [62.213.145.97] (unknown [62.213.145.97]) by mx1.mbs-systems.net (Postfix) with ESMTPSA id 369805C2DA; Thu, 13 Sep 2012 10:55:09 +0200 (CEST) Mime-Version: 1.0 (Apple Message framework v1278) From: Maik Brauer In-Reply-To: <1347514738.25803.26.camel@dagon.hellion.org.uk> Date: Thu, 13 Sep 2012 10:54:03 +0200 Message-Id: References: <9F8FD2B0-450A-4A6E-A929-BA240ED1D997@mbs-systems.net> <1346746297.32462.37.camel@zakaz.uk.xensource.com> <1347266386.5305.17.camel@zakaz.uk.xensource.com> <4957C391-6070-47C1-A2AC-991ED1C1766A@mbs-systems.net> <1347289853.5305.105.camel@zakaz.uk.xensource.com> <4BCC413D-1697-4681-AF28-118D1623AF1C@mbs-systems.net> <1347445398.24226.37.camel@zakaz.uk.xensource.com> <5CB14C04-2A76-4747-8209-EB5122DF7239@mbs-systems.net> <1347514738.25803.26.camel@dagon.hellion.org.uk> To: Ian Campbell X-Mailer: Apple Mail (2.1278) Cc: "xen-users@lists.xen.org" Subject: Re: [Xen-users] Dom0 crashed when rebooting whilst DomU are running X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org On Sep 13, 2012, at 7:38 AM, Ian Campbell wrote: > On Wed, 2012-09-12 at 21:47 +0100, Maik Brauer wrote: >> On Sep 12, 2012, at 12:23 PM, Ian Campbell wrote: >> >>> On Tue, 2012-09-11 at 23:46 +0100, Maik Brauer wrote: >>>> You can easiliy reproduce this issue, when using more that 3 Network >>>> devices. >>> >>> I installed a PV guest on Debian Wheezy using 5 vifs all on the same >>> bridge and could not reproduce this, the domain was successfully >>> shutdown on reboot. >>> >>> I also replaced the Debian xendomains script with the one from >>> xen-4.1-testing (since Debian's differs). Still no repro. >>> >> Hi Ian, please try it with the stable squeeze one. Because I am currently not using an unstable version. >> I have customers running on that machines so I can't experiment. Can you please try with Debian 64bit? > > In your initial mail you said you were running a 4.1.3 hypervisor. > Squeeze has 4.0. Which is it? I am using Debian 5.0.7 (SQUEEZE), with the 4.1.3 Hypervisor and 2.6.32-5-xen-amd64 kernel. I am not using the Standard Packaged Hypervisor (4.0) shipped with Debian SQUEEZE. > > Ian. > >> >> >>> Ian. >>> >>> >>> _______________________________________________ >>> Xen-users mailing list >>> Xen-users@lists.xen.org >>> http://lists.xen.org/xen-users >> >> >> >> _______________________________________________ >> Xen-users mailing list >> Xen-users@lists.xen.org >> http://lists.xen.org/xen-users > > > > _______________________________________________ > Xen-users mailing list > Xen-users@lists.xen.org > http://lists.xen.org/xen-users _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Thu Sep 13 08:57:00 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Thu, 13 Sep 2012 08:57:00 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TC5DL-0008NU-Vm; Thu, 13 Sep 2012 08:55:59 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TC5DK-0008NM-SX for xen-users@lists.xen.org; Thu, 13 Sep 2012 08:55:59 +0000 Received: from [85.158.138.51:57360] by server-5.bemta-3.messagelabs.com id B2/BA-13133-D9F91505; Thu, 13 Sep 2012 08:55:57 +0000 X-Env-Sender: maik.brauer@mbs-systems.net X-Msg-Ref: server-13.tower-174.messagelabs.com!1347526557!11640501!1 X-Originating-IP: [188.40.240.248] X-SpamReason: No, hits=0.0 required=7.0 tests= X-StarScan-Received: X-StarScan-Version: 6.6.1.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 5566 invoked from network); 13 Sep 2012 08:55:57 -0000 Received: from mx1.mbs-systems.net (HELO mx1.mbs-systems.net) (188.40.240.248) by server-13.tower-174.messagelabs.com with SMTP; 13 Sep 2012 08:55:57 -0000 Received: from localhost (localhost [127.0.0.1]) by mx1.mbs-systems.net (Postfix) with ESMTP id 968845C30B; Thu, 13 Sep 2012 10:57:00 +0200 (CEST) Received: from mx1.mbs-systems.net ([127.0.0.1]) by localhost (mta.mbs-systems.net [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 3bM-OHqbJ4-l; Thu, 13 Sep 2012 10:57:00 +0200 (CEST) Received: from [62.213.145.97] (unknown [62.213.145.97]) by mx1.mbs-systems.net (Postfix) with ESMTPSA id 4C7C15C2DA; Thu, 13 Sep 2012 10:57:00 +0200 (CEST) Mime-Version: 1.0 (Apple Message framework v1278) From: Maik Brauer In-Reply-To: <1347515481.25803.36.camel@dagon.hellion.org.uk> Date: Thu, 13 Sep 2012 10:55:56 +0200 Message-Id: References: <9F8FD2B0-450A-4A6E-A929-BA240ED1D997@mbs-systems.net> <1346746297.32462.37.camel@zakaz.uk.xensource.com> <1347266386.5305.17.camel@zakaz.uk.xensource.com> <4957C391-6070-47C1-A2AC-991ED1C1766A@mbs-systems.net> <1347289853.5305.105.camel@zakaz.uk.xensource.com> <4BCC413D-1697-4681-AF28-118D1623AF1C@mbs-systems.net> <1347445398.24226.37.camel@zakaz.uk.xensource.com> <5CB14C04-2A76-4747-8209-EB5122DF7239@mbs-systems.net> <1347515481.25803.36.camel@dagon.hellion.org.uk> To: Ian Campbell X-Mailer: Apple Mail (2.1278) Cc: xen-users@lists.xen.org Subject: Re: [Xen-users] Dom0 crashed when rebooting whilst DomU are running X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org On Sep 13, 2012, at 7:51 AM, Ian Campbell wrote: > On Wed, 2012-09-12 at 21:47 +0100, Maik Brauer wrote: >> On Sep 12, 2012, at 12:23 PM, Ian Campbell wrote: >> >>> On Tue, 2012-09-11 at 23:46 +0100, Maik Brauer wrote: >>>> You can easiliy reproduce this issue, when using more that 3 Network >>>> devices. >>> >>> I installed a PV guest on Debian Wheezy using 5 vifs all on the same >>> bridge and could not reproduce this, the domain was successfully >>> shutdown on reboot. >>> >>> I also replaced the Debian xendomains script with the one from >>> xen-4.1-testing (since Debian's differs). Still no repro. >>> >> Hi Ian, please try it with the stable squeeze one. Because I am currently not using an unstable version. >> I have customers running on that machines so I can't experiment. > > What about one of the several machines you have installed at home which > show this issue? > I will try to install it on a WHEEZY machine for testing. But this will not help me, because at the end I need it working on Production machines. And I do not want to install this WHEEZY in production. > > > _______________________________________________ > Xen-users mailing list > Xen-users@lists.xen.org > http://lists.xen.org/xen-users _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Thu Sep 13 08:57:00 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Thu, 13 Sep 2012 08:57:00 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TC5DL-0008NU-Vm; Thu, 13 Sep 2012 08:55:59 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TC5DK-0008NM-SX for xen-users@lists.xen.org; Thu, 13 Sep 2012 08:55:59 +0000 Received: from [85.158.138.51:57360] by server-5.bemta-3.messagelabs.com id B2/BA-13133-D9F91505; Thu, 13 Sep 2012 08:55:57 +0000 X-Env-Sender: maik.brauer@mbs-systems.net X-Msg-Ref: server-13.tower-174.messagelabs.com!1347526557!11640501!1 X-Originating-IP: [188.40.240.248] X-SpamReason: No, hits=0.0 required=7.0 tests= X-StarScan-Received: X-StarScan-Version: 6.6.1.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 5566 invoked from network); 13 Sep 2012 08:55:57 -0000 Received: from mx1.mbs-systems.net (HELO mx1.mbs-systems.net) (188.40.240.248) by server-13.tower-174.messagelabs.com with SMTP; 13 Sep 2012 08:55:57 -0000 Received: from localhost (localhost [127.0.0.1]) by mx1.mbs-systems.net (Postfix) with ESMTP id 968845C30B; Thu, 13 Sep 2012 10:57:00 +0200 (CEST) Received: from mx1.mbs-systems.net ([127.0.0.1]) by localhost (mta.mbs-systems.net [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 3bM-OHqbJ4-l; Thu, 13 Sep 2012 10:57:00 +0200 (CEST) Received: from [62.213.145.97] (unknown [62.213.145.97]) by mx1.mbs-systems.net (Postfix) with ESMTPSA id 4C7C15C2DA; Thu, 13 Sep 2012 10:57:00 +0200 (CEST) Mime-Version: 1.0 (Apple Message framework v1278) From: Maik Brauer In-Reply-To: <1347515481.25803.36.camel@dagon.hellion.org.uk> Date: Thu, 13 Sep 2012 10:55:56 +0200 Message-Id: References: <9F8FD2B0-450A-4A6E-A929-BA240ED1D997@mbs-systems.net> <1346746297.32462.37.camel@zakaz.uk.xensource.com> <1347266386.5305.17.camel@zakaz.uk.xensource.com> <4957C391-6070-47C1-A2AC-991ED1C1766A@mbs-systems.net> <1347289853.5305.105.camel@zakaz.uk.xensource.com> <4BCC413D-1697-4681-AF28-118D1623AF1C@mbs-systems.net> <1347445398.24226.37.camel@zakaz.uk.xensource.com> <5CB14C04-2A76-4747-8209-EB5122DF7239@mbs-systems.net> <1347515481.25803.36.camel@dagon.hellion.org.uk> To: Ian Campbell X-Mailer: Apple Mail (2.1278) Cc: xen-users@lists.xen.org Subject: Re: [Xen-users] Dom0 crashed when rebooting whilst DomU are running X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org On Sep 13, 2012, at 7:51 AM, Ian Campbell wrote: > On Wed, 2012-09-12 at 21:47 +0100, Maik Brauer wrote: >> On Sep 12, 2012, at 12:23 PM, Ian Campbell wrote: >> >>> On Tue, 2012-09-11 at 23:46 +0100, Maik Brauer wrote: >>>> You can easiliy reproduce this issue, when using more that 3 Network >>>> devices. >>> >>> I installed a PV guest on Debian Wheezy using 5 vifs all on the same >>> bridge and could not reproduce this, the domain was successfully >>> shutdown on reboot. >>> >>> I also replaced the Debian xendomains script with the one from >>> xen-4.1-testing (since Debian's differs). Still no repro. >>> >> Hi Ian, please try it with the stable squeeze one. Because I am currently not using an unstable version. >> I have customers running on that machines so I can't experiment. > > What about one of the several machines you have installed at home which > show this issue? > I will try to install it on a WHEEZY machine for testing. But this will not help me, because at the end I need it working on Production machines. And I do not want to install this WHEEZY in production. > > > _______________________________________________ > Xen-users mailing list > Xen-users@lists.xen.org > http://lists.xen.org/xen-users _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Thu Sep 13 08:59:30 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Thu, 13 Sep 2012 08:59:30 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TC5Fx-0000Ce-PF; Thu, 13 Sep 2012 08:58:41 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TC5Fv-0000CM-Tb for xen-users@lists.xen.org; Thu, 13 Sep 2012 08:58:40 +0000 Received: from [85.158.138.51:37467] by server-12.bemta-3.messagelabs.com id EC/F3-10384-F30A1505; Thu, 13 Sep 2012 08:58:39 +0000 X-Env-Sender: Ian.Campbell@citrix.com X-Msg-Ref: server-11.tower-174.messagelabs.com!1347526718!30302281!1 X-Originating-IP: [62.200.22.115] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogNjIuMjAwLjIyLjExNSA9PiAxMDg4Njg=\n X-StarScan-Received: X-StarScan-Version: 6.6.1.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 9793 invoked from network); 13 Sep 2012 08:58:38 -0000 Received: from smtp.eu.citrix.com (HELO SMTP.EU.CITRIX.COM) (62.200.22.115) by server-11.tower-174.messagelabs.com with RC4-SHA encrypted SMTP; 13 Sep 2012 08:58:38 -0000 X-IronPort-AV: E=Sophos;i="4.80,416,1344211200"; d="scan'208";a="14513535" Received: from lonpmailmx01.citrite.net ([10.30.203.162]) by LONPIPO01.EU.CITRIX.COM with ESMTP/TLS/RC4-MD5; 13 Sep 2012 08:58:38 +0000 Received: from [10.80.2.42] (10.80.2.42) by LONPMAILMX01.citrite.net (10.30.203.162) with Microsoft SMTP Server id 8.3.279.1; Thu, 13 Sep 2012 09:58:38 +0100 Message-ID: <1347526716.24226.70.camel@zakaz.uk.xensource.com> From: Ian Campbell To: Maik Brauer Date: Thu, 13 Sep 2012 09:58:36 +0100 In-Reply-To: References: <9F8FD2B0-450A-4A6E-A929-BA240ED1D997@mbs-systems.net> <1346746297.32462.37.camel@zakaz.uk.xensource.com> <1347266386.5305.17.camel@zakaz.uk.xensource.com> <4957C391-6070-47C1-A2AC-991ED1C1766A@mbs-systems.net> <1347289853.5305.105.camel@zakaz.uk.xensource.com> <4BCC413D-1697-4681-AF28-118D1623AF1C@mbs-systems.net> <1347445398.24226.37.camel@zakaz.uk.xensource.com> <5CB14C04-2A76-4747-8209-EB5122DF7239@mbs-systems.net> <1347515481.25803.36.camel@dagon.hellion.org.uk> Organization: Citrix Systems, Inc. X-Mailer: Evolution 3.4.3-1 MIME-Version: 1.0 Cc: "xen-users@lists.xen.org" Subject: Re: [Xen-users] Dom0 crashed when rebooting whilst DomU are running X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org On Thu, 2012-09-13 at 09:55 +0100, Maik Brauer wrote: > I will try to install it on a WHEEZY machine for testing. But this will not help me, because > at the end I need it working on Production machines. And I do not want to install this WHEEZY in production. Why not install a test system with exactly the same software as you use in production? _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Thu Sep 13 08:59:30 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Thu, 13 Sep 2012 08:59:30 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TC5Fx-0000Ce-PF; Thu, 13 Sep 2012 08:58:41 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TC5Fv-0000CM-Tb for xen-users@lists.xen.org; Thu, 13 Sep 2012 08:58:40 +0000 Received: from [85.158.138.51:37467] by server-12.bemta-3.messagelabs.com id EC/F3-10384-F30A1505; Thu, 13 Sep 2012 08:58:39 +0000 X-Env-Sender: Ian.Campbell@citrix.com X-Msg-Ref: server-11.tower-174.messagelabs.com!1347526718!30302281!1 X-Originating-IP: [62.200.22.115] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogNjIuMjAwLjIyLjExNSA9PiAxMDg4Njg=\n X-StarScan-Received: X-StarScan-Version: 6.6.1.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 9793 invoked from network); 13 Sep 2012 08:58:38 -0000 Received: from smtp.eu.citrix.com (HELO SMTP.EU.CITRIX.COM) (62.200.22.115) by server-11.tower-174.messagelabs.com with RC4-SHA encrypted SMTP; 13 Sep 2012 08:58:38 -0000 X-IronPort-AV: E=Sophos;i="4.80,416,1344211200"; d="scan'208";a="14513535" Received: from lonpmailmx01.citrite.net ([10.30.203.162]) by LONPIPO01.EU.CITRIX.COM with ESMTP/TLS/RC4-MD5; 13 Sep 2012 08:58:38 +0000 Received: from [10.80.2.42] (10.80.2.42) by LONPMAILMX01.citrite.net (10.30.203.162) with Microsoft SMTP Server id 8.3.279.1; Thu, 13 Sep 2012 09:58:38 +0100 Message-ID: <1347526716.24226.70.camel@zakaz.uk.xensource.com> From: Ian Campbell To: Maik Brauer Date: Thu, 13 Sep 2012 09:58:36 +0100 In-Reply-To: References: <9F8FD2B0-450A-4A6E-A929-BA240ED1D997@mbs-systems.net> <1346746297.32462.37.camel@zakaz.uk.xensource.com> <1347266386.5305.17.camel@zakaz.uk.xensource.com> <4957C391-6070-47C1-A2AC-991ED1C1766A@mbs-systems.net> <1347289853.5305.105.camel@zakaz.uk.xensource.com> <4BCC413D-1697-4681-AF28-118D1623AF1C@mbs-systems.net> <1347445398.24226.37.camel@zakaz.uk.xensource.com> <5CB14C04-2A76-4747-8209-EB5122DF7239@mbs-systems.net> <1347515481.25803.36.camel@dagon.hellion.org.uk> Organization: Citrix Systems, Inc. X-Mailer: Evolution 3.4.3-1 MIME-Version: 1.0 Cc: "xen-users@lists.xen.org" Subject: Re: [Xen-users] Dom0 crashed when rebooting whilst DomU are running X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org On Thu, 2012-09-13 at 09:55 +0100, Maik Brauer wrote: > I will try to install it on a WHEEZY machine for testing. But this will not help me, because > at the end I need it working on Production machines. And I do not want to install this WHEEZY in production. Why not install a test system with exactly the same software as you use in production? _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Thu Sep 13 09:10:22 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Thu, 13 Sep 2012 09:10:22 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TC5QQ-0000qL-8O; Thu, 13 Sep 2012 09:09:30 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TC5QP-0000qE-Gx for xen-users@lists.xen.org; Thu, 13 Sep 2012 09:09:29 +0000 Received: from [85.158.139.83:60795] by server-12.bemta-5.messagelabs.com id 50/CE-19338-8C2A1505; Thu, 13 Sep 2012 09:09:28 +0000 X-Env-Sender: maik.brauer@mbs-systems.net X-Msg-Ref: server-3.tower-182.messagelabs.com!1347527352!30247928!1 X-Originating-IP: [188.40.240.248] X-SpamReason: No, hits=0.0 required=7.0 tests= X-StarScan-Received: X-StarScan-Version: 6.6.1.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 28898 invoked from network); 13 Sep 2012 09:09:12 -0000 Received: from mx1.mbs-systems.net (HELO mx1.mbs-systems.net) (188.40.240.248) by server-3.tower-182.messagelabs.com with SMTP; 13 Sep 2012 09:09:12 -0000 Received: from localhost (localhost [127.0.0.1]) by mx1.mbs-systems.net (Postfix) with ESMTP id 579065C30C; Thu, 13 Sep 2012 11:10:15 +0200 (CEST) Received: from mx1.mbs-systems.net ([127.0.0.1]) by localhost (mta.mbs-systems.net [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id vBLEgH71fdWh; Thu, 13 Sep 2012 11:10:14 +0200 (CEST) Received: from [62.213.145.97] (unknown [62.213.145.97]) by mx1.mbs-systems.net (Postfix) with ESMTPSA id 157BE5C2DA; Thu, 13 Sep 2012 11:10:14 +0200 (CEST) Mime-Version: 1.0 (Apple Message framework v1278) From: Maik Brauer In-Reply-To: <1347526716.24226.70.camel@zakaz.uk.xensource.com> Date: Thu, 13 Sep 2012 11:09:09 +0200 Message-Id: <051FE94A-4663-4044-B7E1-5A518CF13A18@mbs-systems.net> References: <9F8FD2B0-450A-4A6E-A929-BA240ED1D997@mbs-systems.net> <1346746297.32462.37.camel@zakaz.uk.xensource.com> <1347266386.5305.17.camel@zakaz.uk.xensource.com> <4957C391-6070-47C1-A2AC-991ED1C1766A@mbs-systems.net> <1347289853.5305.105.camel@zakaz.uk.xensource.com> <4BCC413D-1697-4681-AF28-118D1623AF1C@mbs-systems.net> <1347445398.24226.37.camel@zakaz.uk.xensource.com> <5CB14C04-2A76-4747-8209-EB5122DF7239@mbs-systems.net> <1347515481.25803.36.camel@dagon.hellion.org.uk> <1347526716.24226.70.camel@zakaz.uk.xensource.com> To: Ian Campbell X-Mailer: Apple Mail (2.1278) Cc: "xen-users@lists.xen.org" Subject: Re: [Xen-users] Dom0 crashed when rebooting whilst DomU are running X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org On Sep 13, 2012, at 10:58 AM, Ian Campbell wrote: > On Thu, 2012-09-13 at 09:55 +0100, Maik Brauer wrote: >> I will try to install it on a WHEEZY machine for testing. But this will not help me, because >> at the end I need it working on Production machines. And I do not want to install this WHEEZY in production. > > Why not install a test system with exactly the same software as you use > in production? > Yes, as I said, I will install a test system with the software I want to use. But even this is working afterwards, I will not use this in production, because wheezy is still not stable. > _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Thu Sep 13 09:10:22 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Thu, 13 Sep 2012 09:10:22 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TC5QQ-0000qL-8O; Thu, 13 Sep 2012 09:09:30 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TC5QP-0000qE-Gx for xen-users@lists.xen.org; Thu, 13 Sep 2012 09:09:29 +0000 Received: from [85.158.139.83:60795] by server-12.bemta-5.messagelabs.com id 50/CE-19338-8C2A1505; Thu, 13 Sep 2012 09:09:28 +0000 X-Env-Sender: maik.brauer@mbs-systems.net X-Msg-Ref: server-3.tower-182.messagelabs.com!1347527352!30247928!1 X-Originating-IP: [188.40.240.248] X-SpamReason: No, hits=0.0 required=7.0 tests= X-StarScan-Received: X-StarScan-Version: 6.6.1.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 28898 invoked from network); 13 Sep 2012 09:09:12 -0000 Received: from mx1.mbs-systems.net (HELO mx1.mbs-systems.net) (188.40.240.248) by server-3.tower-182.messagelabs.com with SMTP; 13 Sep 2012 09:09:12 -0000 Received: from localhost (localhost [127.0.0.1]) by mx1.mbs-systems.net (Postfix) with ESMTP id 579065C30C; Thu, 13 Sep 2012 11:10:15 +0200 (CEST) Received: from mx1.mbs-systems.net ([127.0.0.1]) by localhost (mta.mbs-systems.net [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id vBLEgH71fdWh; Thu, 13 Sep 2012 11:10:14 +0200 (CEST) Received: from [62.213.145.97] (unknown [62.213.145.97]) by mx1.mbs-systems.net (Postfix) with ESMTPSA id 157BE5C2DA; Thu, 13 Sep 2012 11:10:14 +0200 (CEST) Mime-Version: 1.0 (Apple Message framework v1278) From: Maik Brauer In-Reply-To: <1347526716.24226.70.camel@zakaz.uk.xensource.com> Date: Thu, 13 Sep 2012 11:09:09 +0200 Message-Id: <051FE94A-4663-4044-B7E1-5A518CF13A18@mbs-systems.net> References: <9F8FD2B0-450A-4A6E-A929-BA240ED1D997@mbs-systems.net> <1346746297.32462.37.camel@zakaz.uk.xensource.com> <1347266386.5305.17.camel@zakaz.uk.xensource.com> <4957C391-6070-47C1-A2AC-991ED1C1766A@mbs-systems.net> <1347289853.5305.105.camel@zakaz.uk.xensource.com> <4BCC413D-1697-4681-AF28-118D1623AF1C@mbs-systems.net> <1347445398.24226.37.camel@zakaz.uk.xensource.com> <5CB14C04-2A76-4747-8209-EB5122DF7239@mbs-systems.net> <1347515481.25803.36.camel@dagon.hellion.org.uk> <1347526716.24226.70.camel@zakaz.uk.xensource.com> To: Ian Campbell X-Mailer: Apple Mail (2.1278) Cc: "xen-users@lists.xen.org" Subject: Re: [Xen-users] Dom0 crashed when rebooting whilst DomU are running X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org On Sep 13, 2012, at 10:58 AM, Ian Campbell wrote: > On Thu, 2012-09-13 at 09:55 +0100, Maik Brauer wrote: >> I will try to install it on a WHEEZY machine for testing. But this will not help me, because >> at the end I need it working on Production machines. And I do not want to install this WHEEZY in production. > > Why not install a test system with exactly the same software as you use > in production? > Yes, as I said, I will install a test system with the software I want to use. But even this is working afterwards, I will not use this in production, because wheezy is still not stable. > _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Thu Sep 13 09:29:12 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Thu, 13 Sep 2012 09:29:12 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TC5in-0001Fz-94; Thu, 13 Sep 2012 09:28:29 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TC5il-0001Fu-T9 for xen-users@lists.xen.org; Thu, 13 Sep 2012 09:28:28 +0000 Received: from [85.158.143.99:39029] by server-2.bemta-4.messagelabs.com id E3/F5-21239-B37A1505; Thu, 13 Sep 2012 09:28:27 +0000 X-Env-Sender: Ian.Campbell@citrix.com X-Msg-Ref: server-13.tower-216.messagelabs.com!1347528501!29227044!1 X-Originating-IP: [62.200.22.115] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogNjIuMjAwLjIyLjExNSA9PiAxMDkwMjg=\n X-StarScan-Received: X-StarScan-Version: 6.6.1.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 26947 invoked from network); 13 Sep 2012 09:28:22 -0000 Received: from smtp.ctxuk.citrix.com (HELO SMTP.EU.CITRIX.COM) (62.200.22.115) by server-13.tower-216.messagelabs.com with RC4-SHA encrypted SMTP; 13 Sep 2012 09:28:22 -0000 X-IronPort-AV: E=Sophos;i="4.80,416,1344211200"; d="scan'208";a="14514507" Received: from lonpmailmx01.citrite.net ([10.30.203.162]) by LONPIPO01.EU.CITRIX.COM with ESMTP/TLS/RC4-MD5; 13 Sep 2012 09:28:05 +0000 Received: from [10.80.2.42] (10.80.2.42) by LONPMAILMX01.citrite.net (10.30.203.162) with Microsoft SMTP Server id 8.3.279.1; Thu, 13 Sep 2012 10:28:04 +0100 Message-ID: <1347528483.24226.75.camel@zakaz.uk.xensource.com> From: Ian Campbell To: Maik Brauer Date: Thu, 13 Sep 2012 10:28:03 +0100 In-Reply-To: <051FE94A-4663-4044-B7E1-5A518CF13A18@mbs-systems.net> References: <9F8FD2B0-450A-4A6E-A929-BA240ED1D997@mbs-systems.net> <1346746297.32462.37.camel@zakaz.uk.xensource.com> <1347266386.5305.17.camel@zakaz.uk.xensource.com> <4957C391-6070-47C1-A2AC-991ED1C1766A@mbs-systems.net> <1347289853.5305.105.camel@zakaz.uk.xensource.com> <4BCC413D-1697-4681-AF28-118D1623AF1C@mbs-systems.net> <1347445398.24226.37.camel@zakaz.uk.xensource.com> <5CB14C04-2A76-4747-8209-EB5122DF7239@mbs-systems.net> <1347515481.25803.36.camel@dagon.hellion.org.uk> <1347526716.24226.70.camel@zakaz.uk.xensource.com> <051FE94A-4663-4044-B7E1-5A518CF13A18@mbs-systems.net> Organization: Citrix Systems, Inc. X-Mailer: Evolution 3.4.3-1 MIME-Version: 1.0 Cc: "xen-users@lists.xen.org" Subject: Re: [Xen-users] Dom0 crashed when rebooting whilst DomU are running X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org On Thu, 2012-09-13 at 10:09 +0100, Maik Brauer wrote: > On Sep 13, 2012, at 10:58 AM, Ian Campbell wrote: > > > On Thu, 2012-09-13 at 09:55 +0100, Maik Brauer wrote: > >> I will try to install it on a WHEEZY machine for testing. But this will not help me, because > >> at the end I need it working on Production machines. And I do not want to install this WHEEZY in production. > > > > Why not install a test system with exactly the same software as you use > > in production? > > > Yes, as I said, I will install a test system with the software I want to use. But even this is working afterwards, I will > not use this in production, because wheezy is still not stable. Why Wheezy? What we need here is a system which has the same software as you use in production, which reproduces the issue and which you can play with and experiment with as much as you like without disturbing your customers. I'm not asking you to install Wheezy here, although if you think it will help and you can reproduce the issue with that configuration then go ahead. Please just be sure to be very clear about which exact environment any specific results you report were obtained in. Ian. _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Thu Sep 13 09:29:12 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Thu, 13 Sep 2012 09:29:12 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TC5in-0001Fz-94; Thu, 13 Sep 2012 09:28:29 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TC5il-0001Fu-T9 for xen-users@lists.xen.org; Thu, 13 Sep 2012 09:28:28 +0000 Received: from [85.158.143.99:39029] by server-2.bemta-4.messagelabs.com id E3/F5-21239-B37A1505; Thu, 13 Sep 2012 09:28:27 +0000 X-Env-Sender: Ian.Campbell@citrix.com X-Msg-Ref: server-13.tower-216.messagelabs.com!1347528501!29227044!1 X-Originating-IP: [62.200.22.115] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogNjIuMjAwLjIyLjExNSA9PiAxMDkwMjg=\n X-StarScan-Received: X-StarScan-Version: 6.6.1.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 26947 invoked from network); 13 Sep 2012 09:28:22 -0000 Received: from smtp.ctxuk.citrix.com (HELO SMTP.EU.CITRIX.COM) (62.200.22.115) by server-13.tower-216.messagelabs.com with RC4-SHA encrypted SMTP; 13 Sep 2012 09:28:22 -0000 X-IronPort-AV: E=Sophos;i="4.80,416,1344211200"; d="scan'208";a="14514507" Received: from lonpmailmx01.citrite.net ([10.30.203.162]) by LONPIPO01.EU.CITRIX.COM with ESMTP/TLS/RC4-MD5; 13 Sep 2012 09:28:05 +0000 Received: from [10.80.2.42] (10.80.2.42) by LONPMAILMX01.citrite.net (10.30.203.162) with Microsoft SMTP Server id 8.3.279.1; Thu, 13 Sep 2012 10:28:04 +0100 Message-ID: <1347528483.24226.75.camel@zakaz.uk.xensource.com> From: Ian Campbell To: Maik Brauer Date: Thu, 13 Sep 2012 10:28:03 +0100 In-Reply-To: <051FE94A-4663-4044-B7E1-5A518CF13A18@mbs-systems.net> References: <9F8FD2B0-450A-4A6E-A929-BA240ED1D997@mbs-systems.net> <1346746297.32462.37.camel@zakaz.uk.xensource.com> <1347266386.5305.17.camel@zakaz.uk.xensource.com> <4957C391-6070-47C1-A2AC-991ED1C1766A@mbs-systems.net> <1347289853.5305.105.camel@zakaz.uk.xensource.com> <4BCC413D-1697-4681-AF28-118D1623AF1C@mbs-systems.net> <1347445398.24226.37.camel@zakaz.uk.xensource.com> <5CB14C04-2A76-4747-8209-EB5122DF7239@mbs-systems.net> <1347515481.25803.36.camel@dagon.hellion.org.uk> <1347526716.24226.70.camel@zakaz.uk.xensource.com> <051FE94A-4663-4044-B7E1-5A518CF13A18@mbs-systems.net> Organization: Citrix Systems, Inc. X-Mailer: Evolution 3.4.3-1 MIME-Version: 1.0 Cc: "xen-users@lists.xen.org" Subject: Re: [Xen-users] Dom0 crashed when rebooting whilst DomU are running X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org On Thu, 2012-09-13 at 10:09 +0100, Maik Brauer wrote: > On Sep 13, 2012, at 10:58 AM, Ian Campbell wrote: > > > On Thu, 2012-09-13 at 09:55 +0100, Maik Brauer wrote: > >> I will try to install it on a WHEEZY machine for testing. But this will not help me, because > >> at the end I need it working on Production machines. And I do not want to install this WHEEZY in production. > > > > Why not install a test system with exactly the same software as you use > > in production? > > > Yes, as I said, I will install a test system with the software I want to use. But even this is working afterwards, I will > not use this in production, because wheezy is still not stable. Why Wheezy? What we need here is a system which has the same software as you use in production, which reproduces the issue and which you can play with and experiment with as much as you like without disturbing your customers. I'm not asking you to install Wheezy here, although if you think it will help and you can reproduce the issue with that configuration then go ahead. Please just be sure to be very clear about which exact environment any specific results you report were obtained in. Ian. _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Thu Sep 13 09:44:57 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Thu, 13 Sep 2012 09:44:57 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TC5y3-0001hA-Ej; Thu, 13 Sep 2012 09:44:15 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TC5y2-0001h2-EV for xen-users@lists.xen.org; Thu, 13 Sep 2012 09:44:14 +0000 Received: from [85.158.143.35:13566] by server-1.bemta-4.messagelabs.com id 59/86-12504-DEAA1505; Thu, 13 Sep 2012 09:44:13 +0000 X-Env-Sender: maik.brauer@mbs-systems.net X-Msg-Ref: server-6.tower-21.messagelabs.com!1347529453!18064393!1 X-Originating-IP: [188.40.240.248] X-SpamReason: No, hits=0.5 required=7.0 tests=BODY_RANDOM_LONG X-StarScan-Received: X-StarScan-Version: 6.6.1.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 1644 invoked from network); 13 Sep 2012 09:44:13 -0000 Received: from mx1.mbs-systems.net (HELO mx1.mbs-systems.net) (188.40.240.248) by server-6.tower-21.messagelabs.com with SMTP; 13 Sep 2012 09:44:13 -0000 Received: from localhost (localhost [127.0.0.1]) by mx1.mbs-systems.net (Postfix) with ESMTP id 568075C30C; Thu, 13 Sep 2012 11:45:16 +0200 (CEST) Received: from mx1.mbs-systems.net ([127.0.0.1]) by localhost (mta.mbs-systems.net [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id rDNkHWMs1Hjw; Thu, 13 Sep 2012 11:45:15 +0200 (CEST) Received: from [62.213.145.97] (unknown [62.213.145.97]) by mx1.mbs-systems.net (Postfix) with ESMTPSA id 7D4E45C2DA; Thu, 13 Sep 2012 11:45:15 +0200 (CEST) Mime-Version: 1.0 (Apple Message framework v1278) From: Maik Brauer In-Reply-To: <1347528483.24226.75.camel@zakaz.uk.xensource.com> Date: Thu, 13 Sep 2012 11:44:11 +0200 Message-Id: <680DAA9E-E2BE-46AC-8BC8-498010275484@mbs-systems.net> References: <9F8FD2B0-450A-4A6E-A929-BA240ED1D997@mbs-systems.net> <1346746297.32462.37.camel@zakaz.uk.xensource.com> <1347266386.5305.17.camel@zakaz.uk.xensource.com> <4957C391-6070-47C1-A2AC-991ED1C1766A@mbs-systems.net> <1347289853.5305.105.camel@zakaz.uk.xensource.com> <4BCC413D-1697-4681-AF28-118D1623AF1C@mbs-systems.net> <1347445398.24226.37.camel@zakaz.uk.xensource.com> <5CB14C04-2A76-4747-8209-EB5122DF7239@mbs-systems.net> <1347515481.25803.36.camel@dagon.hellion.org.uk> <1347526716.24226.70.camel@zakaz.uk.xensource.com> <051FE94A-4663-4044-B7E1-5A518CF13A18@mbs-systems.net> <1347528483.24226.75.camel@zakaz.uk.xensource.com> To: Ian Campbell X-Mailer: Apple Mail (2.1278) Cc: "xen-users@lists.xen.org" Subject: Re: [Xen-users] Dom0 crashed when rebooting whilst DomU are running X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org On Sep 13, 2012, at 11:28 AM, Ian Campbell wrote: > On Thu, 2012-09-13 at 10:09 +0100, Maik Brauer wrote: >> On Sep 13, 2012, at 10:58 AM, Ian Campbell wrote: >> >>> On Thu, 2012-09-13 at 09:55 +0100, Maik Brauer wrote: >>>> I will try to install it on a WHEEZY machine for testing. But this will not help me, because >>>> at the end I need it working on Production machines. And I do not want to install this WHEEZY in production. >>> >>> Why not install a test system with exactly the same software as you use >>> in production? >>> >> Yes, as I said, I will install a test system with the software I want to use. But even this is working afterwards, I will >> not use this in production, because wheezy is still not stable. > > Why Wheezy? What we need here is a system which has the same software as > you use in production, which reproduces the issue and which you can play > with and experiment with as much as you like without disturbing your > customers. > I have that already as mentioned in my last threads. What I can do, is that I can provide the VM on a webserver for you, where you can download the VM. Than you have the environment where you can reproduce the issue. Is that OK for you. I am using Parallels for the Test-Setup System. > I'm not asking you to install Wheezy here, although if you think it will > help and you can reproduce the issue with that configuration then go > ahead. > > Please just be sure to be very clear about which exact environment any > specific results you report were obtained in. > > Ian. > _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Thu Sep 13 09:44:57 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Thu, 13 Sep 2012 09:44:57 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TC5y3-0001hA-Ej; Thu, 13 Sep 2012 09:44:15 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TC5y2-0001h2-EV for xen-users@lists.xen.org; Thu, 13 Sep 2012 09:44:14 +0000 Received: from [85.158.143.35:13566] by server-1.bemta-4.messagelabs.com id 59/86-12504-DEAA1505; Thu, 13 Sep 2012 09:44:13 +0000 X-Env-Sender: maik.brauer@mbs-systems.net X-Msg-Ref: server-6.tower-21.messagelabs.com!1347529453!18064393!1 X-Originating-IP: [188.40.240.248] X-SpamReason: No, hits=0.5 required=7.0 tests=BODY_RANDOM_LONG X-StarScan-Received: X-StarScan-Version: 6.6.1.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 1644 invoked from network); 13 Sep 2012 09:44:13 -0000 Received: from mx1.mbs-systems.net (HELO mx1.mbs-systems.net) (188.40.240.248) by server-6.tower-21.messagelabs.com with SMTP; 13 Sep 2012 09:44:13 -0000 Received: from localhost (localhost [127.0.0.1]) by mx1.mbs-systems.net (Postfix) with ESMTP id 568075C30C; Thu, 13 Sep 2012 11:45:16 +0200 (CEST) Received: from mx1.mbs-systems.net ([127.0.0.1]) by localhost (mta.mbs-systems.net [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id rDNkHWMs1Hjw; Thu, 13 Sep 2012 11:45:15 +0200 (CEST) Received: from [62.213.145.97] (unknown [62.213.145.97]) by mx1.mbs-systems.net (Postfix) with ESMTPSA id 7D4E45C2DA; Thu, 13 Sep 2012 11:45:15 +0200 (CEST) Mime-Version: 1.0 (Apple Message framework v1278) From: Maik Brauer In-Reply-To: <1347528483.24226.75.camel@zakaz.uk.xensource.com> Date: Thu, 13 Sep 2012 11:44:11 +0200 Message-Id: <680DAA9E-E2BE-46AC-8BC8-498010275484@mbs-systems.net> References: <9F8FD2B0-450A-4A6E-A929-BA240ED1D997@mbs-systems.net> <1346746297.32462.37.camel@zakaz.uk.xensource.com> <1347266386.5305.17.camel@zakaz.uk.xensource.com> <4957C391-6070-47C1-A2AC-991ED1C1766A@mbs-systems.net> <1347289853.5305.105.camel@zakaz.uk.xensource.com> <4BCC413D-1697-4681-AF28-118D1623AF1C@mbs-systems.net> <1347445398.24226.37.camel@zakaz.uk.xensource.com> <5CB14C04-2A76-4747-8209-EB5122DF7239@mbs-systems.net> <1347515481.25803.36.camel@dagon.hellion.org.uk> <1347526716.24226.70.camel@zakaz.uk.xensource.com> <051FE94A-4663-4044-B7E1-5A518CF13A18@mbs-systems.net> <1347528483.24226.75.camel@zakaz.uk.xensource.com> To: Ian Campbell X-Mailer: Apple Mail (2.1278) Cc: "xen-users@lists.xen.org" Subject: Re: [Xen-users] Dom0 crashed when rebooting whilst DomU are running X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org On Sep 13, 2012, at 11:28 AM, Ian Campbell wrote: > On Thu, 2012-09-13 at 10:09 +0100, Maik Brauer wrote: >> On Sep 13, 2012, at 10:58 AM, Ian Campbell wrote: >> >>> On Thu, 2012-09-13 at 09:55 +0100, Maik Brauer wrote: >>>> I will try to install it on a WHEEZY machine for testing. But this will not help me, because >>>> at the end I need it working on Production machines. And I do not want to install this WHEEZY in production. >>> >>> Why not install a test system with exactly the same software as you use >>> in production? >>> >> Yes, as I said, I will install a test system with the software I want to use. But even this is working afterwards, I will >> not use this in production, because wheezy is still not stable. > > Why Wheezy? What we need here is a system which has the same software as > you use in production, which reproduces the issue and which you can play > with and experiment with as much as you like without disturbing your > customers. > I have that already as mentioned in my last threads. What I can do, is that I can provide the VM on a webserver for you, where you can download the VM. Than you have the environment where you can reproduce the issue. Is that OK for you. I am using Parallels for the Test-Setup System. > I'm not asking you to install Wheezy here, although if you think it will > help and you can reproduce the issue with that configuration then go > ahead. > > Please just be sure to be very clear about which exact environment any > specific results you report were obtained in. > > Ian. > _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Thu Sep 13 09:52:53 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Thu, 13 Sep 2012 09:52:53 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TC65a-0001zN-LO; Thu, 13 Sep 2012 09:52:02 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TC65Y-0001zI-L2 for xen-users@lists.xen.org; Thu, 13 Sep 2012 09:52:00 +0000 Received: from [85.158.138.51:24548] by server-7.bemta-3.messagelabs.com id 85/82-32000-FBCA1505; Thu, 13 Sep 2012 09:51:59 +0000 X-Env-Sender: Ian.Campbell@citrix.com X-Msg-Ref: server-8.tower-174.messagelabs.com!1347529918!30286810!1 X-Originating-IP: [62.200.22.115] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogNjIuMjAwLjIyLjExNSA9PiAxMDkwMjg=\n X-StarScan-Received: X-StarScan-Version: 6.6.1.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 18798 invoked from network); 13 Sep 2012 09:51:59 -0000 Received: from smtp.eu.citrix.com (HELO SMTP.EU.CITRIX.COM) (62.200.22.115) by server-8.tower-174.messagelabs.com with RC4-SHA encrypted SMTP; 13 Sep 2012 09:51:59 -0000 X-IronPort-AV: E=Sophos;i="4.80,416,1344211200"; d="scan'208";a="14515159" Received: from lonpmailmx01.citrite.net ([10.30.203.162]) by LONPIPO01.EU.CITRIX.COM with ESMTP/TLS/RC4-MD5; 13 Sep 2012 09:51:58 +0000 Received: from [10.80.2.42] (10.80.2.42) by LONPMAILMX01.citrite.net (10.30.203.162) with Microsoft SMTP Server id 8.3.279.1; Thu, 13 Sep 2012 10:51:57 +0100 Message-ID: <1347529916.24226.80.camel@zakaz.uk.xensource.com> From: Ian Campbell To: Maik Brauer Date: Thu, 13 Sep 2012 10:51:56 +0100 In-Reply-To: <680DAA9E-E2BE-46AC-8BC8-498010275484@mbs-systems.net> References: <9F8FD2B0-450A-4A6E-A929-BA240ED1D997@mbs-systems.net> <1346746297.32462.37.camel@zakaz.uk.xensource.com> <1347266386.5305.17.camel@zakaz.uk.xensource.com> <4957C391-6070-47C1-A2AC-991ED1C1766A@mbs-systems.net> <1347289853.5305.105.camel@zakaz.uk.xensource.com> <4BCC413D-1697-4681-AF28-118D1623AF1C@mbs-systems.net> <1347445398.24226.37.camel@zakaz.uk.xensource.com> <5CB14C04-2A76-4747-8209-EB5122DF7239@mbs-systems.net> <1347515481.25803.36.camel@dagon.hellion.org.uk> <1347526716.24226.70.camel@zakaz.uk.xensource.com> <051FE94A-4663-4044-B7E1-5A518CF13A18@mbs-systems.net> <1347528483.24226.75.camel@zakaz.uk.xensource.com> <680DAA9E-E2BE-46AC-8BC8-498010275484@mbs-systems.net> Organization: Citrix Systems, Inc. X-Mailer: Evolution 3.4.3-1 MIME-Version: 1.0 Cc: "xen-users@lists.xen.org" Subject: Re: [Xen-users] Dom0 crashed when rebooting whilst DomU are running X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org On Thu, 2012-09-13 at 10:44 +0100, Maik Brauer wrote: > On Sep 13, 2012, at 11:28 AM, Ian Campbell wrote: > > > On Thu, 2012-09-13 at 10:09 +0100, Maik Brauer wrote: > >> On Sep 13, 2012, at 10:58 AM, Ian Campbell wrote: > >> > >>> On Thu, 2012-09-13 at 09:55 +0100, Maik Brauer wrote: > >>>> I will try to install it on a WHEEZY machine for testing. But this will not help me, because > >>>> at the end I need it working on Production machines. And I do not want to install this WHEEZY in production. > >>> > >>> Why not install a test system with exactly the same software as you use > >>> in production? > >>> > >> Yes, as I said, I will install a test system with the software I want to use. But even this is working afterwards, I will > >> not use this in production, because wheezy is still not stable. > > > > Why Wheezy? What we need here is a system which has the same software as > > you use in production, which reproduces the issue and which you can play > > with and experiment with as much as you like without disturbing your > > customers. > > > I have that already as mentioned in my last threads. The reason we are having this sub thread is that you said: "I have customers running on that machines so I can't experiment.". If you have a test machine where you can reproduce the issue which you can experiment with then please feel free to use it. > What I can do, is that I can > provide the VM on a webserver for you, where you can download the VM. > Than you have the environment where you can reproduce the issue. Is that OK for you. > I am using Parallels for the Test-Setup System. I'm afraid I don't have time any more to do anything other than suggest avenues for you to investigate and experiments for you to try. Ian. _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Thu Sep 13 09:52:53 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Thu, 13 Sep 2012 09:52:53 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TC65a-0001zN-LO; Thu, 13 Sep 2012 09:52:02 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TC65Y-0001zI-L2 for xen-users@lists.xen.org; Thu, 13 Sep 2012 09:52:00 +0000 Received: from [85.158.138.51:24548] by server-7.bemta-3.messagelabs.com id 85/82-32000-FBCA1505; Thu, 13 Sep 2012 09:51:59 +0000 X-Env-Sender: Ian.Campbell@citrix.com X-Msg-Ref: server-8.tower-174.messagelabs.com!1347529918!30286810!1 X-Originating-IP: [62.200.22.115] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogNjIuMjAwLjIyLjExNSA9PiAxMDkwMjg=\n X-StarScan-Received: X-StarScan-Version: 6.6.1.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 18798 invoked from network); 13 Sep 2012 09:51:59 -0000 Received: from smtp.eu.citrix.com (HELO SMTP.EU.CITRIX.COM) (62.200.22.115) by server-8.tower-174.messagelabs.com with RC4-SHA encrypted SMTP; 13 Sep 2012 09:51:59 -0000 X-IronPort-AV: E=Sophos;i="4.80,416,1344211200"; d="scan'208";a="14515159" Received: from lonpmailmx01.citrite.net ([10.30.203.162]) by LONPIPO01.EU.CITRIX.COM with ESMTP/TLS/RC4-MD5; 13 Sep 2012 09:51:58 +0000 Received: from [10.80.2.42] (10.80.2.42) by LONPMAILMX01.citrite.net (10.30.203.162) with Microsoft SMTP Server id 8.3.279.1; Thu, 13 Sep 2012 10:51:57 +0100 Message-ID: <1347529916.24226.80.camel@zakaz.uk.xensource.com> From: Ian Campbell To: Maik Brauer Date: Thu, 13 Sep 2012 10:51:56 +0100 In-Reply-To: <680DAA9E-E2BE-46AC-8BC8-498010275484@mbs-systems.net> References: <9F8FD2B0-450A-4A6E-A929-BA240ED1D997@mbs-systems.net> <1346746297.32462.37.camel@zakaz.uk.xensource.com> <1347266386.5305.17.camel@zakaz.uk.xensource.com> <4957C391-6070-47C1-A2AC-991ED1C1766A@mbs-systems.net> <1347289853.5305.105.camel@zakaz.uk.xensource.com> <4BCC413D-1697-4681-AF28-118D1623AF1C@mbs-systems.net> <1347445398.24226.37.camel@zakaz.uk.xensource.com> <5CB14C04-2A76-4747-8209-EB5122DF7239@mbs-systems.net> <1347515481.25803.36.camel@dagon.hellion.org.uk> <1347526716.24226.70.camel@zakaz.uk.xensource.com> <051FE94A-4663-4044-B7E1-5A518CF13A18@mbs-systems.net> <1347528483.24226.75.camel@zakaz.uk.xensource.com> <680DAA9E-E2BE-46AC-8BC8-498010275484@mbs-systems.net> Organization: Citrix Systems, Inc. X-Mailer: Evolution 3.4.3-1 MIME-Version: 1.0 Cc: "xen-users@lists.xen.org" Subject: Re: [Xen-users] Dom0 crashed when rebooting whilst DomU are running X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org On Thu, 2012-09-13 at 10:44 +0100, Maik Brauer wrote: > On Sep 13, 2012, at 11:28 AM, Ian Campbell wrote: > > > On Thu, 2012-09-13 at 10:09 +0100, Maik Brauer wrote: > >> On Sep 13, 2012, at 10:58 AM, Ian Campbell wrote: > >> > >>> On Thu, 2012-09-13 at 09:55 +0100, Maik Brauer wrote: > >>>> I will try to install it on a WHEEZY machine for testing. But this will not help me, because > >>>> at the end I need it working on Production machines. And I do not want to install this WHEEZY in production. > >>> > >>> Why not install a test system with exactly the same software as you use > >>> in production? > >>> > >> Yes, as I said, I will install a test system with the software I want to use. But even this is working afterwards, I will > >> not use this in production, because wheezy is still not stable. > > > > Why Wheezy? What we need here is a system which has the same software as > > you use in production, which reproduces the issue and which you can play > > with and experiment with as much as you like without disturbing your > > customers. > > > I have that already as mentioned in my last threads. The reason we are having this sub thread is that you said: "I have customers running on that machines so I can't experiment.". If you have a test machine where you can reproduce the issue which you can experiment with then please feel free to use it. > What I can do, is that I can > provide the VM on a webserver for you, where you can download the VM. > Than you have the environment where you can reproduce the issue. Is that OK for you. > I am using Parallels for the Test-Setup System. I'm afraid I don't have time any more to do anything other than suggest avenues for you to investigate and experiments for you to try. Ian. _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Thu Sep 13 12:27:18 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Thu, 13 Sep 2012 12:27:18 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TC8Uu-00062h-0Y; Thu, 13 Sep 2012 12:26:20 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TC8Us-00062Z-9d for xen-users@lists.xen.org; Thu, 13 Sep 2012 12:26:18 +0000 Received: from [85.158.137.99:6815] by server-3.bemta-3.messagelabs.com id 4A/20-21322-9E0D1505; Thu, 13 Sep 2012 12:26:17 +0000 X-Env-Sender: mailinglists@websitemanagers.com.au X-Msg-Ref: server-15.tower-217.messagelabs.com!1347539172!15128379!1 X-Originating-IP: [203.56.191.70] X-SpamReason: No, hits=0.0 required=7.0 tests= X-StarScan-Received: X-StarScan-Version: 6.6.1.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 8037 invoked from network); 13 Sep 2012 12:26:16 -0000 Received: from unknown (HELO hammer.websitemanagers.com.au) (203.56.191.70) by server-15.tower-217.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 13 Sep 2012 12:26:16 -0000 Received: (qmail 6716 invoked by uid 1011); 13 Sep 2012 12:25:41 -0000 Received: from 124.246.8.196 by hammer (envelope-from , uid 1008) with qmail-scanner-1.24 (clamdscan: 0.97.3/15349. spamassassin: 3.3.1. Clear:RC:1(124.246.8.196):. Processed in 0.054531 secs); 13 Sep 2012 12:25:41 -0000 Received: from unknown (HELO ?192.168.2.90?) (124.246.8.196) by 0 with SMTP; 13 Sep 2012 12:25:41 -0000 Message-ID: <5051D0C5.5070600@websitemanagers.com.au> Date: Thu, 13 Sep 2012 22:25:41 +1000 From: Adam Goryachev Organization: Website Managers User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:15.0) Gecko/20120827 Thunderbird/15.0 MIME-Version: 1.0 To: xen-users@lists.xen.org Subject: [Xen-users] Poor Windows 2003 + GPLPV performance compared to VMWare X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org I have an application server running on MS Windows 2003, which was a clean install on VMWare last year (after a failed migration attempt to XenServer). At this point, a benchmark (actually a live process run regularly on the machine) produced a result of 7800 to 7900 transactions per second I've recently migrated this to Xen by: 1) Uninstall VMWare tools 2) Shutdown Windows 3) Use VMWare to download the vmdk 4) Write the VMDK file (dd) to the same LVM that contained the VMWare storage area (which was exported by iSCSI to VMWare 5) Installed Debian Testing with Xen 4.1 6) Using the exactl same iSCSI server/LVM config etc, started the VM 7) Installed the GPLPV drivers Everything seemed to work, and all was good. Then, the user ran the above process, and got consistently, results of approx 2500 transactions per second I increased the vcpus from 2 to 4, but this didn't change the result at all. I modifed the domU config for the disk line from hda to xvda, and the result increased slightly to 2560 / sec (these tests are just one off tests, no verification of actual performance increase etc...). In any case, I seem to have a significant loss of performance on the domU when compared to VMWare. The storage server/network is identical The dom0 machine is identical to the VMWare machine Here is my current domU config file: kernel = "/usr/lib/xen-4.1/boot/hvmloader" builder = 'hvm' memory = 4096 shadow_memory = 12 device_model = '/usr/lib/xen-default/bin/qemu-dm' localtime = 1 name = "vm1" cpus = "2,3,4,5" # Which physical CPU's to allow vcpus = 4 # How many Virtual CPU's to present viridian = 1 disk = [ 'phy:/dev/disk/by-path/ip-10.30.10.23:3260-iscsi-iqn.2012-06.domain:vm1-lun-0,xvda,w' ] vif = ['bridge=xenbr0, mac=00:16:3e:39:10:1a'] boot = 'c' sdl = 0 vnc = 1 vncdisplay = 10 vncviewer = 0 vncconsole = 0 vncunused = 0 stdvga = 1 usb = 1 usbdevice = 'tablet' acpi = 1 apic = 1 on_reboot = 'restart' on_poweroff = 'destroy' on_crash = 'restart' audio = 0 Any suggestions on how to improve performance would be greatly appreciated. Thank you, Adam -- Adam Goryachev Website Managers www.websitemanagers.com.au _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Thu Sep 13 12:27:18 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Thu, 13 Sep 2012 12:27:18 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TC8Uu-00062h-0Y; Thu, 13 Sep 2012 12:26:20 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TC8Us-00062Z-9d for xen-users@lists.xen.org; Thu, 13 Sep 2012 12:26:18 +0000 Received: from [85.158.137.99:6815] by server-3.bemta-3.messagelabs.com id 4A/20-21322-9E0D1505; Thu, 13 Sep 2012 12:26:17 +0000 X-Env-Sender: mailinglists@websitemanagers.com.au X-Msg-Ref: server-15.tower-217.messagelabs.com!1347539172!15128379!1 X-Originating-IP: [203.56.191.70] X-SpamReason: No, hits=0.0 required=7.0 tests= X-StarScan-Received: X-StarScan-Version: 6.6.1.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 8037 invoked from network); 13 Sep 2012 12:26:16 -0000 Received: from unknown (HELO hammer.websitemanagers.com.au) (203.56.191.70) by server-15.tower-217.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 13 Sep 2012 12:26:16 -0000 Received: (qmail 6716 invoked by uid 1011); 13 Sep 2012 12:25:41 -0000 Received: from 124.246.8.196 by hammer (envelope-from , uid 1008) with qmail-scanner-1.24 (clamdscan: 0.97.3/15349. spamassassin: 3.3.1. Clear:RC:1(124.246.8.196):. Processed in 0.054531 secs); 13 Sep 2012 12:25:41 -0000 Received: from unknown (HELO ?192.168.2.90?) (124.246.8.196) by 0 with SMTP; 13 Sep 2012 12:25:41 -0000 Message-ID: <5051D0C5.5070600@websitemanagers.com.au> Date: Thu, 13 Sep 2012 22:25:41 +1000 From: Adam Goryachev Organization: Website Managers User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:15.0) Gecko/20120827 Thunderbird/15.0 MIME-Version: 1.0 To: xen-users@lists.xen.org Subject: [Xen-users] Poor Windows 2003 + GPLPV performance compared to VMWare X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org I have an application server running on MS Windows 2003, which was a clean install on VMWare last year (after a failed migration attempt to XenServer). At this point, a benchmark (actually a live process run regularly on the machine) produced a result of 7800 to 7900 transactions per second I've recently migrated this to Xen by: 1) Uninstall VMWare tools 2) Shutdown Windows 3) Use VMWare to download the vmdk 4) Write the VMDK file (dd) to the same LVM that contained the VMWare storage area (which was exported by iSCSI to VMWare 5) Installed Debian Testing with Xen 4.1 6) Using the exactl same iSCSI server/LVM config etc, started the VM 7) Installed the GPLPV drivers Everything seemed to work, and all was good. Then, the user ran the above process, and got consistently, results of approx 2500 transactions per second I increased the vcpus from 2 to 4, but this didn't change the result at all. I modifed the domU config for the disk line from hda to xvda, and the result increased slightly to 2560 / sec (these tests are just one off tests, no verification of actual performance increase etc...). In any case, I seem to have a significant loss of performance on the domU when compared to VMWare. The storage server/network is identical The dom0 machine is identical to the VMWare machine Here is my current domU config file: kernel = "/usr/lib/xen-4.1/boot/hvmloader" builder = 'hvm' memory = 4096 shadow_memory = 12 device_model = '/usr/lib/xen-default/bin/qemu-dm' localtime = 1 name = "vm1" cpus = "2,3,4,5" # Which physical CPU's to allow vcpus = 4 # How many Virtual CPU's to present viridian = 1 disk = [ 'phy:/dev/disk/by-path/ip-10.30.10.23:3260-iscsi-iqn.2012-06.domain:vm1-lun-0,xvda,w' ] vif = ['bridge=xenbr0, mac=00:16:3e:39:10:1a'] boot = 'c' sdl = 0 vnc = 1 vncdisplay = 10 vncviewer = 0 vncconsole = 0 vncunused = 0 stdvga = 1 usb = 1 usbdevice = 'tablet' acpi = 1 apic = 1 on_reboot = 'restart' on_poweroff = 'destroy' on_crash = 'restart' audio = 0 Any suggestions on how to improve performance would be greatly appreciated. Thank you, Adam -- Adam Goryachev Website Managers www.websitemanagers.com.au _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Thu Sep 13 12:50:49 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Thu, 13 Sep 2012 12:50:49 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TC8rY-0006Zg-QP; Thu, 13 Sep 2012 12:49:44 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TC8rW-0006Zb-Nb for xen-users@lists.xen.org; Thu, 13 Sep 2012 12:49:42 +0000 Received: from [85.158.143.99:28507] by server-2.bemta-4.messagelabs.com id F3/A4-21239-566D1505; Thu, 13 Sep 2012 12:49:41 +0000 X-Env-Sender: mailinglists@websitemanagers.com.au X-Msg-Ref: server-7.tower-216.messagelabs.com!1347540576!24060222!1 X-Originating-IP: [203.56.191.70] X-SpamReason: No, hits=0.0 required=7.0 tests= X-StarScan-Received: X-StarScan-Version: 6.6.1.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 25679 invoked from network); 13 Sep 2012 12:49:39 -0000 Received: from unknown (HELO hammer.websitemanagers.com.au) (203.56.191.70) by server-7.tower-216.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 13 Sep 2012 12:49:39 -0000 Received: (qmail 14494 invoked by uid 1011); 13 Sep 2012 12:49:05 -0000 Received: from 124.246.8.196 by hammer (envelope-from , uid 1008) with qmail-scanner-1.24 (clamdscan: 0.97.3/15349. spamassassin: 3.3.1. Clear:RC:1(124.246.8.196):. Processed in 0.064589 secs); 13 Sep 2012 12:49:05 -0000 Received: from unknown (HELO ?192.168.2.90?) (124.246.8.196) by 0 with SMTP; 13 Sep 2012 12:49:05 -0000 Message-ID: <5051D641.4090204@websitemanagers.com.au> Date: Thu, 13 Sep 2012 22:49:05 +1000 From: Adam Goryachev Organization: Website Managers User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:15.0) Gecko/20120827 Thunderbird/15.0 MIME-Version: 1.0 To: xen-users@lists.xen.org References: <5051D0C5.5070600@websitemanagers.com.au> In-Reply-To: <5051D0C5.5070600@websitemanagers.com.au> Subject: Re: [Xen-users] Poor Windows 2003 + GPLPV performance compared to VMWare X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org Additional information accidentally omitted: The dom0 machine is a debian testing running Xen 4.1 xm info host : pm08 release : 3.2.0-3-amd64 version : #1 SMP Mon Jul 23 02:45:17 UTC 2012 machine : x86_64 nr_cpus : 6 nr_nodes : 1 cores_per_socket : 6 threads_per_core : 1 cpu_mhz : 3300 hw_caps : 178bf3ff:efd3fbff:00000000:00001310:00802001:00000000:000837ff:00000000 virt_caps : hvm total_memory : 16351 free_memory : 2 free_cpus : 0 xen_major : 4 xen_minor : 1 xen_extra : .3 xen_caps : xen-3.0-x86_64 xen-3.0-x86_32p hvm-3.0-x86_32 hvm-3.0-x86_32p hvm-3.0-x86_64 xen_scheduler : credit xen_pagesize : 4096 platform_params : virt_start=0xffff800000000000 xen_changeset : unavailable xen_commandline : placeholder cc_compiler : gcc version 4.7.1 (Debian 4.7.1-7) cc_compile_by : waldi cc_compile_domain : debian.org cc_compile_date : Fri Aug 17 09:41:02 UTC 2012 xend_config_format : 4 If I should provide any other information, please let me know. Regards, Adam On 13/09/12 22:25, Adam Goryachev wrote: > I have an application server running on MS Windows 2003, which was a > clean install on VMWare last year (after a failed migration attempt to > XenServer). > > At this point, a benchmark (actually a live process run regularly on the > machine) produced a result of 7800 to 7900 transactions per second > > I've recently migrated this to Xen by: > 1) Uninstall VMWare tools > 2) Shutdown Windows > 3) Use VMWare to download the vmdk > 4) Write the VMDK file (dd) to the same LVM that contained the VMWare > storage area (which was exported by iSCSI to VMWare > 5) Installed Debian Testing with Xen 4.1 > 6) Using the exactl same iSCSI server/LVM config etc, started the VM > 7) Installed the GPLPV drivers > > Everything seemed to work, and all was good. > > Then, the user ran the above process, and got consistently, results of > approx 2500 transactions per second > > I increased the vcpus from 2 to 4, but this didn't change the result at all. > > I modifed the domU config for the disk line from hda to xvda, and the > result increased slightly to 2560 / sec (these tests are just one off > tests, no verification of actual performance increase etc...). > > In any case, I seem to have a significant loss of performance on the > domU when compared to VMWare. > > The storage server/network is identical > The dom0 machine is identical to the VMWare machine > > Here is my current domU config file: > > kernel = "/usr/lib/xen-4.1/boot/hvmloader" > builder = 'hvm' > memory = 4096 > shadow_memory = 12 > device_model = '/usr/lib/xen-default/bin/qemu-dm' > localtime = 1 > name = "vm1" > cpus = "2,3,4,5" # Which physical CPU's to allow > vcpus = 4 # How many Virtual CPU's to present > viridian = 1 > disk = [ > 'phy:/dev/disk/by-path/ip-10.30.10.23:3260-iscsi-iqn.2012-06.domain:vm1-lun-0,xvda,w' > ] > vif = ['bridge=xenbr0, mac=00:16:3e:39:10:1a'] > boot = 'c' > sdl = 0 > vnc = 1 > vncdisplay = 10 > vncviewer = 0 > vncconsole = 0 > vncunused = 0 > stdvga = 1 > usb = 1 > usbdevice = 'tablet' > acpi = 1 > apic = 1 > on_reboot = 'restart' > on_poweroff = 'destroy' > on_crash = 'restart' > audio = 0 > > Any suggestions on how to improve performance would be greatly appreciated. > > Thank you, > Adam > -- Adam Goryachev Website Managers www.websitemanagers.com.au _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Thu Sep 13 12:50:49 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Thu, 13 Sep 2012 12:50:49 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TC8rY-0006Zg-QP; Thu, 13 Sep 2012 12:49:44 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TC8rW-0006Zb-Nb for xen-users@lists.xen.org; Thu, 13 Sep 2012 12:49:42 +0000 Received: from [85.158.143.99:28507] by server-2.bemta-4.messagelabs.com id F3/A4-21239-566D1505; Thu, 13 Sep 2012 12:49:41 +0000 X-Env-Sender: mailinglists@websitemanagers.com.au X-Msg-Ref: server-7.tower-216.messagelabs.com!1347540576!24060222!1 X-Originating-IP: [203.56.191.70] X-SpamReason: No, hits=0.0 required=7.0 tests= X-StarScan-Received: X-StarScan-Version: 6.6.1.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 25679 invoked from network); 13 Sep 2012 12:49:39 -0000 Received: from unknown (HELO hammer.websitemanagers.com.au) (203.56.191.70) by server-7.tower-216.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 13 Sep 2012 12:49:39 -0000 Received: (qmail 14494 invoked by uid 1011); 13 Sep 2012 12:49:05 -0000 Received: from 124.246.8.196 by hammer (envelope-from , uid 1008) with qmail-scanner-1.24 (clamdscan: 0.97.3/15349. spamassassin: 3.3.1. Clear:RC:1(124.246.8.196):. Processed in 0.064589 secs); 13 Sep 2012 12:49:05 -0000 Received: from unknown (HELO ?192.168.2.90?) (124.246.8.196) by 0 with SMTP; 13 Sep 2012 12:49:05 -0000 Message-ID: <5051D641.4090204@websitemanagers.com.au> Date: Thu, 13 Sep 2012 22:49:05 +1000 From: Adam Goryachev Organization: Website Managers User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:15.0) Gecko/20120827 Thunderbird/15.0 MIME-Version: 1.0 To: xen-users@lists.xen.org References: <5051D0C5.5070600@websitemanagers.com.au> In-Reply-To: <5051D0C5.5070600@websitemanagers.com.au> Subject: Re: [Xen-users] Poor Windows 2003 + GPLPV performance compared to VMWare X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org Additional information accidentally omitted: The dom0 machine is a debian testing running Xen 4.1 xm info host : pm08 release : 3.2.0-3-amd64 version : #1 SMP Mon Jul 23 02:45:17 UTC 2012 machine : x86_64 nr_cpus : 6 nr_nodes : 1 cores_per_socket : 6 threads_per_core : 1 cpu_mhz : 3300 hw_caps : 178bf3ff:efd3fbff:00000000:00001310:00802001:00000000:000837ff:00000000 virt_caps : hvm total_memory : 16351 free_memory : 2 free_cpus : 0 xen_major : 4 xen_minor : 1 xen_extra : .3 xen_caps : xen-3.0-x86_64 xen-3.0-x86_32p hvm-3.0-x86_32 hvm-3.0-x86_32p hvm-3.0-x86_64 xen_scheduler : credit xen_pagesize : 4096 platform_params : virt_start=0xffff800000000000 xen_changeset : unavailable xen_commandline : placeholder cc_compiler : gcc version 4.7.1 (Debian 4.7.1-7) cc_compile_by : waldi cc_compile_domain : debian.org cc_compile_date : Fri Aug 17 09:41:02 UTC 2012 xend_config_format : 4 If I should provide any other information, please let me know. Regards, Adam On 13/09/12 22:25, Adam Goryachev wrote: > I have an application server running on MS Windows 2003, which was a > clean install on VMWare last year (after a failed migration attempt to > XenServer). > > At this point, a benchmark (actually a live process run regularly on the > machine) produced a result of 7800 to 7900 transactions per second > > I've recently migrated this to Xen by: > 1) Uninstall VMWare tools > 2) Shutdown Windows > 3) Use VMWare to download the vmdk > 4) Write the VMDK file (dd) to the same LVM that contained the VMWare > storage area (which was exported by iSCSI to VMWare > 5) Installed Debian Testing with Xen 4.1 > 6) Using the exactl same iSCSI server/LVM config etc, started the VM > 7) Installed the GPLPV drivers > > Everything seemed to work, and all was good. > > Then, the user ran the above process, and got consistently, results of > approx 2500 transactions per second > > I increased the vcpus from 2 to 4, but this didn't change the result at all. > > I modifed the domU config for the disk line from hda to xvda, and the > result increased slightly to 2560 / sec (these tests are just one off > tests, no verification of actual performance increase etc...). > > In any case, I seem to have a significant loss of performance on the > domU when compared to VMWare. > > The storage server/network is identical > The dom0 machine is identical to the VMWare machine > > Here is my current domU config file: > > kernel = "/usr/lib/xen-4.1/boot/hvmloader" > builder = 'hvm' > memory = 4096 > shadow_memory = 12 > device_model = '/usr/lib/xen-default/bin/qemu-dm' > localtime = 1 > name = "vm1" > cpus = "2,3,4,5" # Which physical CPU's to allow > vcpus = 4 # How many Virtual CPU's to present > viridian = 1 > disk = [ > 'phy:/dev/disk/by-path/ip-10.30.10.23:3260-iscsi-iqn.2012-06.domain:vm1-lun-0,xvda,w' > ] > vif = ['bridge=xenbr0, mac=00:16:3e:39:10:1a'] > boot = 'c' > sdl = 0 > vnc = 1 > vncdisplay = 10 > vncviewer = 0 > vncconsole = 0 > vncunused = 0 > stdvga = 1 > usb = 1 > usbdevice = 'tablet' > acpi = 1 > apic = 1 > on_reboot = 'restart' > on_poweroff = 'destroy' > on_crash = 'restart' > audio = 0 > > Any suggestions on how to improve performance would be greatly appreciated. > > Thank you, > Adam > -- Adam Goryachev Website Managers www.websitemanagers.com.au _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Thu Sep 13 13:15:04 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Thu, 13 Sep 2012 13:15:04 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TC9FE-0006ya-BC; Thu, 13 Sep 2012 13:14:12 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TC9FD-0006yV-9x for xen-users@lists.xen.org; Thu, 13 Sep 2012 13:14:11 +0000 Received: from [85.158.139.83:45822] by server-11.bemta-5.messagelabs.com id C9/CA-24658-22CD1505; Thu, 13 Sep 2012 13:14:10 +0000 X-Env-Sender: asim.mcp@gmail.com X-Msg-Ref: server-6.tower-182.messagelabs.com!1347542048!26443369!1 X-Originating-IP: [209.85.212.45] X-SpamReason: No, hits=1.2 required=7.0 tests=HTML_20_30,HTML_MESSAGE, ML_RADAR_SPEW_LINKS_14,RCVD_BY_IP,spamassassin: X-StarScan-Received: X-StarScan-Version: 6.6.1.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 7518 invoked from network); 13 Sep 2012 13:14:09 -0000 Received: from mail-vb0-f45.google.com (HELO mail-vb0-f45.google.com) (209.85.212.45) by server-6.tower-182.messagelabs.com with RC4-SHA encrypted SMTP; 13 Sep 2012 13:14:09 -0000 Received: by vbip1 with SMTP id p1so4205073vbi.32 for ; Thu, 13 Sep 2012 06:14:08 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:from:date:message-id:subject:to:content-type; bh=jjS4ELON4Y5bUFjMpSP0jCdBEpy1INHHlL//p68oIqs=; b=g/vT8nDLnrVLGRvVm5A50GpMOse5TM5kd1u/oJUIQ1Gce/UhqPZTvbh2hygXySA9rt nIUpUMVa/PTv0qc+Xj5t3qHTv6aAUCL7uVTNK8T9PmZMqrSifwWni8ylqT6KUupXRJme CQBBYkkLqmPkOH8T6yH7pnvATyIkkMx3j/l+EHf+0RrHRLqHXVV/8DuTI1HbhiyJSSbT puPJNiWjTqCKqZSusL6FOxpfJKPi+tSKbduY5XxhvRM9D5s6fkjhB075sRF6vb5/8nEn b27/iTbFFV9RsvdyL/5P7EGlDZY1YGoPlS89u9ENbDxJhndsXJ8Xle9zFmzRbsnagN7c b36A== Received: by 10.52.240.171 with SMTP id wb11mr987250vdc.86.1347542048398; Thu, 13 Sep 2012 06:14:08 -0700 (PDT) MIME-Version: 1.0 Received: by 10.220.203.10 with HTTP; Thu, 13 Sep 2012 06:13:48 -0700 (PDT) From: asim hafeez Date: Thu, 13 Sep 2012 18:13:48 +0500 Message-ID: To: xen-users@lists.xen.org Subject: [Xen-users] hvm cifs image boot issue X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============8797246836471627602==" Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org --===============8797246836471627602== Content-Type: multipart/alternative; boundary=20cf307ca3dc1d5ea304c9951585 --20cf307ca3dc1d5ea304c9951585 Content-Type: text/plain; charset=ISO-8859-1 Hi, I've all of the .img files to a network share, whenever i want to boot a machine using any server i just use cifs path. I've configured Xen4.1.x with Linux Kernel 3.5.x. HVM is working if the .img file is copied to local system's disk. If i se cifs path it does not boot. and shows 0MByets on VNC console for HDD. Kindly help in this regards -- Best Regards Asim --20cf307ca3dc1d5ea304c9951585 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Hi,

I've all of the .img files to a network share, w= henever i want to boot a machine using any server i just use cifs path. I&#= 39;ve configured Xen4.1.x with Linux Kernel 3.5.x.
HVM is working= if the .img file is copied to local system's disk. If i se cifs path i= t does not boot. and shows 0MByets on VNC console for HDD.=A0

Kindly help in this regards

--
Best R= egards
Asim
--20cf307ca3dc1d5ea304c9951585-- --===============8797246836471627602== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users --===============8797246836471627602==-- From xen-users-bounces@lists.xen.org Thu Sep 13 13:15:04 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Thu, 13 Sep 2012 13:15:04 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TC9FE-0006ya-BC; Thu, 13 Sep 2012 13:14:12 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TC9FD-0006yV-9x for xen-users@lists.xen.org; Thu, 13 Sep 2012 13:14:11 +0000 Received: from [85.158.139.83:45822] by server-11.bemta-5.messagelabs.com id C9/CA-24658-22CD1505; Thu, 13 Sep 2012 13:14:10 +0000 X-Env-Sender: asim.mcp@gmail.com X-Msg-Ref: server-6.tower-182.messagelabs.com!1347542048!26443369!1 X-Originating-IP: [209.85.212.45] X-SpamReason: No, hits=1.2 required=7.0 tests=HTML_20_30,HTML_MESSAGE, ML_RADAR_SPEW_LINKS_14,RCVD_BY_IP,spamassassin: X-StarScan-Received: X-StarScan-Version: 6.6.1.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 7518 invoked from network); 13 Sep 2012 13:14:09 -0000 Received: from mail-vb0-f45.google.com (HELO mail-vb0-f45.google.com) (209.85.212.45) by server-6.tower-182.messagelabs.com with RC4-SHA encrypted SMTP; 13 Sep 2012 13:14:09 -0000 Received: by vbip1 with SMTP id p1so4205073vbi.32 for ; Thu, 13 Sep 2012 06:14:08 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:from:date:message-id:subject:to:content-type; bh=jjS4ELON4Y5bUFjMpSP0jCdBEpy1INHHlL//p68oIqs=; b=g/vT8nDLnrVLGRvVm5A50GpMOse5TM5kd1u/oJUIQ1Gce/UhqPZTvbh2hygXySA9rt nIUpUMVa/PTv0qc+Xj5t3qHTv6aAUCL7uVTNK8T9PmZMqrSifwWni8ylqT6KUupXRJme CQBBYkkLqmPkOH8T6yH7pnvATyIkkMx3j/l+EHf+0RrHRLqHXVV/8DuTI1HbhiyJSSbT puPJNiWjTqCKqZSusL6FOxpfJKPi+tSKbduY5XxhvRM9D5s6fkjhB075sRF6vb5/8nEn b27/iTbFFV9RsvdyL/5P7EGlDZY1YGoPlS89u9ENbDxJhndsXJ8Xle9zFmzRbsnagN7c b36A== Received: by 10.52.240.171 with SMTP id wb11mr987250vdc.86.1347542048398; Thu, 13 Sep 2012 06:14:08 -0700 (PDT) MIME-Version: 1.0 Received: by 10.220.203.10 with HTTP; Thu, 13 Sep 2012 06:13:48 -0700 (PDT) From: asim hafeez Date: Thu, 13 Sep 2012 18:13:48 +0500 Message-ID: To: xen-users@lists.xen.org Subject: [Xen-users] hvm cifs image boot issue X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============8797246836471627602==" Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org --===============8797246836471627602== Content-Type: multipart/alternative; boundary=20cf307ca3dc1d5ea304c9951585 --20cf307ca3dc1d5ea304c9951585 Content-Type: text/plain; charset=ISO-8859-1 Hi, I've all of the .img files to a network share, whenever i want to boot a machine using any server i just use cifs path. I've configured Xen4.1.x with Linux Kernel 3.5.x. HVM is working if the .img file is copied to local system's disk. If i se cifs path it does not boot. and shows 0MByets on VNC console for HDD. Kindly help in this regards -- Best Regards Asim --20cf307ca3dc1d5ea304c9951585 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Hi,

I've all of the .img files to a network share, w= henever i want to boot a machine using any server i just use cifs path. I&#= 39;ve configured Xen4.1.x with Linux Kernel 3.5.x.
HVM is working= if the .img file is copied to local system's disk. If i se cifs path i= t does not boot. and shows 0MByets on VNC console for HDD.=A0

Kindly help in this regards

--
Best R= egards
Asim
--20cf307ca3dc1d5ea304c9951585-- --===============8797246836471627602== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users --===============8797246836471627602==-- From xen-users-bounces@lists.xen.org Thu Sep 13 15:24:09 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Thu, 13 Sep 2012 15:24:09 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TCBG6-00051R-IJ; Thu, 13 Sep 2012 15:23:14 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TCBG5-00051J-2m for xen-users@lists.xen.org; Thu, 13 Sep 2012 15:23:13 +0000 Received: from [85.158.143.99:43140] by server-1.bemta-4.messagelabs.com id BC/05-12504-06AF1505; Thu, 13 Sep 2012 15:23:12 +0000 X-Env-Sender: jmok@attglobal.net X-Msg-Ref: server-9.tower-216.messagelabs.com!1347549790!30244773!1 X-Originating-IP: [202.14.67.92] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: QmFkIElQOiAyMDIuMTQuNjcuOTIgPT4gMTYzMDE2\n,sa_preprocessor: QmFkIElQOiAyMDIuMTQuNjcuOTIgPT4gMTYzMDE2\n X-StarScan-Received: X-StarScan-Version: 6.6.1.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 4819 invoked from network); 13 Sep 2012 15:23:11 -0000 Received: from smtp1-hkg1.pacific.net.hk (HELO smtp1-hkg1.pacific.net.hk) (202.14.67.92) by server-9.tower-216.messagelabs.com with SMTP; 13 Sep 2012 15:23:11 -0000 Received: from [127.0.0.1] ([210.17.159.154]) by smtp1-hkg1.pacific.net.hk with ESMTP id q8DFN7BS005747 for ; Thu, 13 Sep 2012 23:23:08 +0800 Message-ID: <5051FA5B.3070105@attglobal.net> Date: Thu, 13 Sep 2012 23:23:07 +0800 From: John Mok User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.2; en-US; rv:1.9.2.28) Gecko/20120306 Thunderbird/3.1.20 MIME-Version: 1.0 To: xen-users@lists.xen.org Subject: [Xen-users] Intel igb driver 3.2.10-k failed to work on Xen 4.1.2 kernel X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset="us-ascii"; Format="flowed" Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org Hi, I tried to use Intel quad-port ethernet adapter on a server running Ubuntu 12.04.1 (kernel 3.2.27), but the igb driver (version 3.2.10-k) failed to work on Xen 4.1.2 kernel in bridge mode. The content of /etc/network/interfaces follows :- auto xenbr0 iface xenbr0 inet static address ..... ...... bridge_ports eth0 auto eth0 iface eth0 inet manual I checked with brctl and there was no associated interface (i.e. eth0 was missing). The bridge interface appeared to be up and running but no traffic could go through (e.g. ping failed). I tried to add the 2nd ethernet port to the bridge and the command completed successfully, but still no traffic could pass through. The igb driver worked normally when booted to kernel 3.2.27 (not Xen kernel). I hope someone could advise what went wrong and how to fix it. Thanks a lot. John Mok _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Thu Sep 13 15:24:09 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Thu, 13 Sep 2012 15:24:09 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TCBG6-00051R-IJ; Thu, 13 Sep 2012 15:23:14 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TCBG5-00051J-2m for xen-users@lists.xen.org; Thu, 13 Sep 2012 15:23:13 +0000 Received: from [85.158.143.99:43140] by server-1.bemta-4.messagelabs.com id BC/05-12504-06AF1505; Thu, 13 Sep 2012 15:23:12 +0000 X-Env-Sender: jmok@attglobal.net X-Msg-Ref: server-9.tower-216.messagelabs.com!1347549790!30244773!1 X-Originating-IP: [202.14.67.92] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: QmFkIElQOiAyMDIuMTQuNjcuOTIgPT4gMTYzMDE2\n,sa_preprocessor: QmFkIElQOiAyMDIuMTQuNjcuOTIgPT4gMTYzMDE2\n X-StarScan-Received: X-StarScan-Version: 6.6.1.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 4819 invoked from network); 13 Sep 2012 15:23:11 -0000 Received: from smtp1-hkg1.pacific.net.hk (HELO smtp1-hkg1.pacific.net.hk) (202.14.67.92) by server-9.tower-216.messagelabs.com with SMTP; 13 Sep 2012 15:23:11 -0000 Received: from [127.0.0.1] ([210.17.159.154]) by smtp1-hkg1.pacific.net.hk with ESMTP id q8DFN7BS005747 for ; Thu, 13 Sep 2012 23:23:08 +0800 Message-ID: <5051FA5B.3070105@attglobal.net> Date: Thu, 13 Sep 2012 23:23:07 +0800 From: John Mok User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.2; en-US; rv:1.9.2.28) Gecko/20120306 Thunderbird/3.1.20 MIME-Version: 1.0 To: xen-users@lists.xen.org Subject: [Xen-users] Intel igb driver 3.2.10-k failed to work on Xen 4.1.2 kernel X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset="us-ascii"; Format="flowed" Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org Hi, I tried to use Intel quad-port ethernet adapter on a server running Ubuntu 12.04.1 (kernel 3.2.27), but the igb driver (version 3.2.10-k) failed to work on Xen 4.1.2 kernel in bridge mode. The content of /etc/network/interfaces follows :- auto xenbr0 iface xenbr0 inet static address ..... ...... bridge_ports eth0 auto eth0 iface eth0 inet manual I checked with brctl and there was no associated interface (i.e. eth0 was missing). The bridge interface appeared to be up and running but no traffic could go through (e.g. ping failed). I tried to add the 2nd ethernet port to the bridge and the command completed successfully, but still no traffic could pass through. The igb driver worked normally when booted to kernel 3.2.27 (not Xen kernel). I hope someone could advise what went wrong and how to fix it. Thanks a lot. John Mok _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Thu Sep 13 15:26:21 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Thu, 13 Sep 2012 15:26:21 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TCBIK-0005F1-Ct; Thu, 13 Sep 2012 15:25:32 +0000 Received: from mail27.messagelabs.com ([193.109.254.147]) by lists.xen.org with smtp (Exim 4.72) (envelope-from ) id 1TC93v-0006uP-Se for xen-users@lists.xen.org; Thu, 13 Sep 2012 13:02:32 +0000 X-Env-Sender: maxwell.p.bottiger.civ@mail.mil X-Msg-Ref: server-3.tower-27.messagelabs.com!1347541279!8910250!1 X-Originating-IP: [131.64.100.6] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogMTMxLjY0LjEwMC42ID0+IDM5MjMy\n X-StarScan-Received: X-StarScan-Version: 6.6.1.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 17520 invoked from network); 13 Sep 2012 13:01:20 -0000 Received: from edge-cols.mail.mil (HELO edge-cols.mail.mil) (131.64.100.6) by server-3.tower-27.messagelabs.com with SMTP; 13 Sep 2012 13:01:20 -0000 Received: from UCOLHP3D.easf.csd.disa.mil (131.64.100.143) by UCOLHP4Z.easf.csd.disa.mil (131.64.100.6) with Microsoft SMTP Server (TLS) id 14.2.309.2; Thu, 13 Sep 2012 13:01:38 +0000 Received: from UCOLHP9L.easf.csd.disa.mil ([169.254.5.127]) by UCOLHP3D.easf.csd.disa.mil ([131.64.100.143]) with mapi id 14.02.0309.003; Thu, 13 Sep 2012 13:01:36 +0000 From: "Bottiger, Maxwell P CIV (US)" To: "xen-users@lists.xen.org" Thread-Topic: Need help understanding imported OVAs (UNCLASSIFIED) Thread-Index: Ac2Rr7xcKEIS0AOGTOGPLSq827Wzuw== Importance: high X-Priority: 1 Date: Thu, 13 Sep 2012 13:01:34 +0000 Message-ID: Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [152.229.77.7] MIME-Version: 1.0 X-Mailman-Approved-At: Thu, 13 Sep 2012 15:25:31 +0000 Subject: [Xen-users] Need help understanding imported OVAs (UNCLASSIFIED) X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============8865010308857826979==" Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org --===============8865010308857826979== Content-Language: en-US Content-Type: multipart/alternative; boundary="_000_FFB0E6FE75570040804E119216C9974C3B636AF0ucolhp9leasfcsd_" --_000_FFB0E6FE75570040804E119216C9974C3B636AF0ucolhp9leasfcsd_ Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Classification: UNCLASSIFIED Caveats: FOUO Hi, I'm _very_ new to Xen and just started playing with it a couple days ago. = So far, mostly so good. I am confused by VM migration though. I have a co= uple of installs I downloaded from stacklet and when using those, I can mov= e a running VM from server to server. However, if I import an OVA VM I cre= ated in VirutalBox, I cannot move the VM without shutting it down. Is this= a PV vs. HVM issue? Thanks! Maxwell Bottiger Battlefield Management Branch - Edgewood Chemical Biological Center maxwell.bottiger@us.army.mil 410-436-4404 Classification: UNCLASSIFIED Caveats: FOUO --_000_FFB0E6FE75570040804E119216C9974C3B636AF0ucolhp9leasfcsd_ Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Classification: UNCLASSIFIED
Caveats: FOUO

Hi,

 

I’m _very_ new to Xen and just started = playing with it a couple days ago.  So far, mostly so good.  I am= confused by VM migration though.  I have a couple of installs I downl= oaded from stacklet and when using those, I can move a running VM from server to server.  However, if I import an OVA VM I c= reated in VirutalBox, I cannot move the VM without shutting it down.  = Is this a PV vs. HVM issue?

 

Thanks!

 

Maxwell Bottiger

Battlefield Management Branch - Edgewood Chemical Bi= ological Center

maxwell.bottiger@us.army.mil

410-436-4404

 


Classification: UNCLASSIFIED
Caveats: FOUO

--_000_FFB0E6FE75570040804E119216C9974C3B636AF0ucolhp9leasfcsd_-- --===============8865010308857826979== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users --===============8865010308857826979==-- From xen-users-bounces@lists.xen.org Thu Sep 13 15:26:21 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Thu, 13 Sep 2012 15:26:21 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TCBIK-0005F1-Ct; Thu, 13 Sep 2012 15:25:32 +0000 Received: from mail27.messagelabs.com ([193.109.254.147]) by lists.xen.org with smtp (Exim 4.72) (envelope-from ) id 1TC93v-0006uP-Se for xen-users@lists.xen.org; Thu, 13 Sep 2012 13:02:32 +0000 X-Env-Sender: maxwell.p.bottiger.civ@mail.mil X-Msg-Ref: server-3.tower-27.messagelabs.com!1347541279!8910250!1 X-Originating-IP: [131.64.100.6] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogMTMxLjY0LjEwMC42ID0+IDM5MjMy\n X-StarScan-Received: X-StarScan-Version: 6.6.1.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 17520 invoked from network); 13 Sep 2012 13:01:20 -0000 Received: from edge-cols.mail.mil (HELO edge-cols.mail.mil) (131.64.100.6) by server-3.tower-27.messagelabs.com with SMTP; 13 Sep 2012 13:01:20 -0000 Received: from UCOLHP3D.easf.csd.disa.mil (131.64.100.143) by UCOLHP4Z.easf.csd.disa.mil (131.64.100.6) with Microsoft SMTP Server (TLS) id 14.2.309.2; Thu, 13 Sep 2012 13:01:38 +0000 Received: from UCOLHP9L.easf.csd.disa.mil ([169.254.5.127]) by UCOLHP3D.easf.csd.disa.mil ([131.64.100.143]) with mapi id 14.02.0309.003; Thu, 13 Sep 2012 13:01:36 +0000 From: "Bottiger, Maxwell P CIV (US)" To: "xen-users@lists.xen.org" Thread-Topic: Need help understanding imported OVAs (UNCLASSIFIED) Thread-Index: Ac2Rr7xcKEIS0AOGTOGPLSq827Wzuw== Importance: high X-Priority: 1 Date: Thu, 13 Sep 2012 13:01:34 +0000 Message-ID: Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [152.229.77.7] MIME-Version: 1.0 X-Mailman-Approved-At: Thu, 13 Sep 2012 15:25:31 +0000 Subject: [Xen-users] Need help understanding imported OVAs (UNCLASSIFIED) X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============8865010308857826979==" Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org --===============8865010308857826979== Content-Language: en-US Content-Type: multipart/alternative; boundary="_000_FFB0E6FE75570040804E119216C9974C3B636AF0ucolhp9leasfcsd_" --_000_FFB0E6FE75570040804E119216C9974C3B636AF0ucolhp9leasfcsd_ Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Classification: UNCLASSIFIED Caveats: FOUO Hi, I'm _very_ new to Xen and just started playing with it a couple days ago. = So far, mostly so good. I am confused by VM migration though. I have a co= uple of installs I downloaded from stacklet and when using those, I can mov= e a running VM from server to server. However, if I import an OVA VM I cre= ated in VirutalBox, I cannot move the VM without shutting it down. Is this= a PV vs. HVM issue? Thanks! Maxwell Bottiger Battlefield Management Branch - Edgewood Chemical Biological Center maxwell.bottiger@us.army.mil 410-436-4404 Classification: UNCLASSIFIED Caveats: FOUO --_000_FFB0E6FE75570040804E119216C9974C3B636AF0ucolhp9leasfcsd_ Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Classification: UNCLASSIFIED
Caveats: FOUO

Hi,

 

I’m _very_ new to Xen and just started = playing with it a couple days ago.  So far, mostly so good.  I am= confused by VM migration though.  I have a couple of installs I downl= oaded from stacklet and when using those, I can move a running VM from server to server.  However, if I import an OVA VM I c= reated in VirutalBox, I cannot move the VM without shutting it down.  = Is this a PV vs. HVM issue?

 

Thanks!

 

Maxwell Bottiger

Battlefield Management Branch - Edgewood Chemical Bi= ological Center

maxwell.bottiger@us.army.mil

410-436-4404

 


Classification: UNCLASSIFIED
Caveats: FOUO

--_000_FFB0E6FE75570040804E119216C9974C3B636AF0ucolhp9leasfcsd_-- --===============8865010308857826979== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users --===============8865010308857826979==-- From xen-users-bounces@lists.xen.org Thu Sep 13 15:57:40 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Thu, 13 Sep 2012 15:57:40 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TCBmb-0007FI-FL; Thu, 13 Sep 2012 15:56:49 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TCBma-0007F4-7F for xen-users@lists.xen.org; Thu, 13 Sep 2012 15:56:48 +0000 Received: from [85.158.143.35:31731] by server-3.bemta-4.messagelabs.com id 09/8C-08232-F3202505; Thu, 13 Sep 2012 15:56:47 +0000 X-Env-Sender: skippyvondrake@gmail.com X-Msg-Ref: server-16.tower-21.messagelabs.com!1347551803!15662880!1 X-Originating-IP: [74.125.82.173] X-SpamReason: No, hits=0.3 required=7.0 tests=ML_RADAR_SPEW_LINKS_14, RCVD_BY_IP,spamassassin: X-StarScan-Received: X-StarScan-Version: 6.6.1.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 25299 invoked from network); 13 Sep 2012 15:56:43 -0000 Received: from mail-we0-f173.google.com (HELO mail-we0-f173.google.com) (74.125.82.173) by server-16.tower-21.messagelabs.com with RC4-SHA encrypted SMTP; 13 Sep 2012 15:56:43 -0000 Received: by weyz53 with SMTP id z53so2116781wey.32 for ; Thu, 13 Sep 2012 08:56:43 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=r1s2xVOQ8139XpUT0OPtH+9ZIRCyDOVHIchcnp1Fh/k=; b=lrWBGzvhar7lqLC7y2LqBdjhgDnQR3kZCr0Do6l2XxSZQLrxQT9sn5V2/aTCP1/Bmu BmCCIBc2l+8RQ/DdE+1RkmJd2hTAFBrjfU4Pq+4qHn7+hZiKmacMdmtjzHDpJiwUWtw0 rdj/xagYTNvyqsYtTLY/dWGU+X8bkGYFmTYt6UD6UZE1rNHvRDEaZLWTINSekkpUxY4A KLIZp+B6gMsK/t1+PjpF/PP4+l46FCTCJbc7RBlmOZBqQdrOAsxE3FjrLt5x7/0hls3/ nezlULEF9HETZdl9WX7G1N4PI/E2PtWnobU9u4YvUHqslcgE/LDefVyYdlauW7qMtLi+ NwEA== MIME-Version: 1.0 Received: by 10.180.84.169 with SMTP id a9mr421481wiz.8.1347551803191; Thu, 13 Sep 2012 08:56:43 -0700 (PDT) Received: by 10.194.79.103 with HTTP; Thu, 13 Sep 2012 08:56:43 -0700 (PDT) In-Reply-To: References: Date: Thu, 13 Sep 2012 11:56:43 -0400 Message-ID: From: Skippy VonDrake To: "Fajar A. Nugraha" Cc: xen-users@lists.xen.org Subject: Re: [Xen-users] new pv stuck in pause X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org Much thanks, Fajar! Your suggestion for the "manual" launch helped me solve this. After attempting that launch I got python related errors. Before doing the "make world" I'd installed python from source - with limited success. But that was a mistake for it mucked up the Xen setup. I had Python in /usr/lib AND in /usr/local/lib. Same version of Python (2.7.3). The xen scripts were located in directories based off the /usr/lib python install. So I had previously done some tweaking to get xen to use THAT python. Obviously I hadn't done enough. So long story short - I changed/created sym links from the /usr/local python install to the other. Forcing everything to use the right one. For others that may have run into this - previously I noticed that 'site-packages' (where the xen scripts were installed) was not included in the sys.path. Only 'dist-packages'. (Which I believe was based on some new Ubuntu model). But since that is where the xen stuff was put - I used 'sitecustomize.py' to append the 'site-packages' dir to Python's sys.path. The VM is now running and accessible. Thanks again, Fajar! _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Thu Sep 13 15:57:40 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Thu, 13 Sep 2012 15:57:40 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TCBmb-0007FI-FL; Thu, 13 Sep 2012 15:56:49 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TCBma-0007F4-7F for xen-users@lists.xen.org; Thu, 13 Sep 2012 15:56:48 +0000 Received: from [85.158.143.35:31731] by server-3.bemta-4.messagelabs.com id 09/8C-08232-F3202505; Thu, 13 Sep 2012 15:56:47 +0000 X-Env-Sender: skippyvondrake@gmail.com X-Msg-Ref: server-16.tower-21.messagelabs.com!1347551803!15662880!1 X-Originating-IP: [74.125.82.173] X-SpamReason: No, hits=0.3 required=7.0 tests=ML_RADAR_SPEW_LINKS_14, RCVD_BY_IP,spamassassin: X-StarScan-Received: X-StarScan-Version: 6.6.1.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 25299 invoked from network); 13 Sep 2012 15:56:43 -0000 Received: from mail-we0-f173.google.com (HELO mail-we0-f173.google.com) (74.125.82.173) by server-16.tower-21.messagelabs.com with RC4-SHA encrypted SMTP; 13 Sep 2012 15:56:43 -0000 Received: by weyz53 with SMTP id z53so2116781wey.32 for ; Thu, 13 Sep 2012 08:56:43 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=r1s2xVOQ8139XpUT0OPtH+9ZIRCyDOVHIchcnp1Fh/k=; b=lrWBGzvhar7lqLC7y2LqBdjhgDnQR3kZCr0Do6l2XxSZQLrxQT9sn5V2/aTCP1/Bmu BmCCIBc2l+8RQ/DdE+1RkmJd2hTAFBrjfU4Pq+4qHn7+hZiKmacMdmtjzHDpJiwUWtw0 rdj/xagYTNvyqsYtTLY/dWGU+X8bkGYFmTYt6UD6UZE1rNHvRDEaZLWTINSekkpUxY4A KLIZp+B6gMsK/t1+PjpF/PP4+l46FCTCJbc7RBlmOZBqQdrOAsxE3FjrLt5x7/0hls3/ nezlULEF9HETZdl9WX7G1N4PI/E2PtWnobU9u4YvUHqslcgE/LDefVyYdlauW7qMtLi+ NwEA== MIME-Version: 1.0 Received: by 10.180.84.169 with SMTP id a9mr421481wiz.8.1347551803191; Thu, 13 Sep 2012 08:56:43 -0700 (PDT) Received: by 10.194.79.103 with HTTP; Thu, 13 Sep 2012 08:56:43 -0700 (PDT) In-Reply-To: References: Date: Thu, 13 Sep 2012 11:56:43 -0400 Message-ID: From: Skippy VonDrake To: "Fajar A. Nugraha" Cc: xen-users@lists.xen.org Subject: Re: [Xen-users] new pv stuck in pause X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org Much thanks, Fajar! Your suggestion for the "manual" launch helped me solve this. After attempting that launch I got python related errors. Before doing the "make world" I'd installed python from source - with limited success. But that was a mistake for it mucked up the Xen setup. I had Python in /usr/lib AND in /usr/local/lib. Same version of Python (2.7.3). The xen scripts were located in directories based off the /usr/lib python install. So I had previously done some tweaking to get xen to use THAT python. Obviously I hadn't done enough. So long story short - I changed/created sym links from the /usr/local python install to the other. Forcing everything to use the right one. For others that may have run into this - previously I noticed that 'site-packages' (where the xen scripts were installed) was not included in the sys.path. Only 'dist-packages'. (Which I believe was based on some new Ubuntu model). But since that is where the xen stuff was put - I used 'sitecustomize.py' to append the 'site-packages' dir to Python's sys.path. The VM is now running and accessible. Thanks again, Fajar! _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Thu Sep 13 17:21:36 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Thu, 13 Sep 2012 17:21:36 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TCD5n-0001s9-1I; Thu, 13 Sep 2012 17:20:43 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TCD5l-0001s2-KV for xen-users@lists.xen.org; Thu, 13 Sep 2012 17:20:41 +0000 Received: from [85.158.138.51:2559] by server-4.bemta-3.messagelabs.com id 7D/70-24831-8E512505; Thu, 13 Sep 2012 17:20:40 +0000 X-Env-Sender: slackmoehrle@gmail.com X-Msg-Ref: server-13.tower-174.messagelabs.com!1347556839!11749870!1 X-Originating-IP: [209.85.217.173] X-SpamReason: No, hits=0.3 required=7.0 tests=ML_RADAR_SPEW_LINKS_14, RCVD_BY_IP,spamassassin: X-StarScan-Received: X-StarScan-Version: 6.6.1.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 31138 invoked from network); 13 Sep 2012 17:20:40 -0000 Received: from mail-lb0-f173.google.com (HELO mail-lb0-f173.google.com) (209.85.217.173) by server-13.tower-174.messagelabs.com with RC4-SHA encrypted SMTP; 13 Sep 2012 17:20:40 -0000 Received: by lbbgm13 with SMTP id gm13so2589547lbb.32 for ; Thu, 13 Sep 2012 10:20:39 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:from:date:message-id:subject:to:content-type; bh=OPeYQTRJu9hIlAU62GHMGjIx7yHxyyfkA9+HDyYaFik=; b=phu7NZoqO30QoGzmU9kcgrlP3ZnqJj+OOmr51w90M4NkmMpnTCvI43Attnv4ReF5bz uDdHqLgg/SOlU3Yf9YLVEtUa4Dv9dX/80+HJsxtGk8HKQNx0LbJujjLci019EpYpbGOO fsU/aB0Xz2b81ClVwt4x4bIquVZBKe5IaHdfToIVZ8t2uOB99c+JavTS8bm4D7t8SfYO Z1K28px30I24fA50B7iQV2xQ/5n11i8cP35M370YD5orOQvMUaiJggh7/4ou7vHWq8ZM EyzlSyut9g0GbCPkIMNIdslYIyb6Z9Du+JzxylVMCDtI4fbdCzqoG6rw7D2anYXzHRyk u15w== Received: by 10.112.28.233 with SMTP id e9mr158921lbh.43.1347556839536; Thu, 13 Sep 2012 10:20:39 -0700 (PDT) MIME-Version: 1.0 Received: by 10.112.17.163 with HTTP; Thu, 13 Sep 2012 10:20:19 -0700 (PDT) From: "Jason T. Slack-Moehrle" Date: Thu, 13 Sep 2012 10:20:19 -0700 Message-ID: To: xen-users@lists.xen.org Subject: [Xen-users] Xen Newbie on a Lenovo U160 X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org I want to buy a Lenovo U160 laptop, Core-i7, 16gb DDR3, 500gb HD What I am trying to accomplish is to use a Hypervisor that boots up and then have a Windows, Linus and OS X VM that also gets started up and I can interact between them while still on the same laptop. I have a fair number of reasons for wanting this between software development for all of these platforms to pen-testing, etc. Can anyone shed some light on if what I want to accomplish is realistic, if this Lenovo U160 will be hardware compatible, etc? Does anyone have any screenshots of Xen running with VM's open? -Jason _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Thu Sep 13 17:21:36 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Thu, 13 Sep 2012 17:21:36 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TCD5n-0001s9-1I; Thu, 13 Sep 2012 17:20:43 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TCD5l-0001s2-KV for xen-users@lists.xen.org; Thu, 13 Sep 2012 17:20:41 +0000 Received: from [85.158.138.51:2559] by server-4.bemta-3.messagelabs.com id 7D/70-24831-8E512505; Thu, 13 Sep 2012 17:20:40 +0000 X-Env-Sender: slackmoehrle@gmail.com X-Msg-Ref: server-13.tower-174.messagelabs.com!1347556839!11749870!1 X-Originating-IP: [209.85.217.173] X-SpamReason: No, hits=0.3 required=7.0 tests=ML_RADAR_SPEW_LINKS_14, RCVD_BY_IP,spamassassin: X-StarScan-Received: X-StarScan-Version: 6.6.1.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 31138 invoked from network); 13 Sep 2012 17:20:40 -0000 Received: from mail-lb0-f173.google.com (HELO mail-lb0-f173.google.com) (209.85.217.173) by server-13.tower-174.messagelabs.com with RC4-SHA encrypted SMTP; 13 Sep 2012 17:20:40 -0000 Received: by lbbgm13 with SMTP id gm13so2589547lbb.32 for ; Thu, 13 Sep 2012 10:20:39 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:from:date:message-id:subject:to:content-type; bh=OPeYQTRJu9hIlAU62GHMGjIx7yHxyyfkA9+HDyYaFik=; b=phu7NZoqO30QoGzmU9kcgrlP3ZnqJj+OOmr51w90M4NkmMpnTCvI43Attnv4ReF5bz uDdHqLgg/SOlU3Yf9YLVEtUa4Dv9dX/80+HJsxtGk8HKQNx0LbJujjLci019EpYpbGOO fsU/aB0Xz2b81ClVwt4x4bIquVZBKe5IaHdfToIVZ8t2uOB99c+JavTS8bm4D7t8SfYO Z1K28px30I24fA50B7iQV2xQ/5n11i8cP35M370YD5orOQvMUaiJggh7/4ou7vHWq8ZM EyzlSyut9g0GbCPkIMNIdslYIyb6Z9Du+JzxylVMCDtI4fbdCzqoG6rw7D2anYXzHRyk u15w== Received: by 10.112.28.233 with SMTP id e9mr158921lbh.43.1347556839536; Thu, 13 Sep 2012 10:20:39 -0700 (PDT) MIME-Version: 1.0 Received: by 10.112.17.163 with HTTP; Thu, 13 Sep 2012 10:20:19 -0700 (PDT) From: "Jason T. Slack-Moehrle" Date: Thu, 13 Sep 2012 10:20:19 -0700 Message-ID: To: xen-users@lists.xen.org Subject: [Xen-users] Xen Newbie on a Lenovo U160 X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org I want to buy a Lenovo U160 laptop, Core-i7, 16gb DDR3, 500gb HD What I am trying to accomplish is to use a Hypervisor that boots up and then have a Windows, Linus and OS X VM that also gets started up and I can interact between them while still on the same laptop. I have a fair number of reasons for wanting this between software development for all of these platforms to pen-testing, etc. Can anyone shed some light on if what I want to accomplish is realistic, if this Lenovo U160 will be hardware compatible, etc? Does anyone have any screenshots of Xen running with VM's open? -Jason _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Thu Sep 13 18:47:30 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Thu, 13 Sep 2012 18:47:30 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TCEQi-0004TV-C4; Thu, 13 Sep 2012 18:46:24 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TCEQh-0004TO-3m for xen-users@lists.xen.org; Thu, 13 Sep 2012 18:46:23 +0000 Received: from [85.158.138.51:45333] by server-11.bemta-3.messagelabs.com id F1/AC-30250-EF922505; Thu, 13 Sep 2012 18:46:22 +0000 X-Env-Sender: vinicius.ruoso@gmail.com X-Msg-Ref: server-13.tower-174.messagelabs.com!1347561980!11757666!1 X-Originating-IP: [209.85.214.173] X-SpamReason: No, hits=0.3 required=7.0 tests=ML_RADAR_SPEW_LINKS_14, RCVD_BY_IP,spamassassin: X-StarScan-Received: X-StarScan-Version: 6.6.1.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 23321 invoked from network); 13 Sep 2012 18:46:21 -0000 Received: from mail-ob0-f173.google.com (HELO mail-ob0-f173.google.com) (209.85.214.173) by server-13.tower-174.messagelabs.com with RC4-SHA encrypted SMTP; 13 Sep 2012 18:46:21 -0000 Received: by obbta14 with SMTP id ta14so6257044obb.32 for ; Thu, 13 Sep 2012 11:46:19 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:date:message-id:subject:from:to:content-type :content-transfer-encoding; bh=oxPJSAkpa6loQCGSu0lLYrwKnp4K4IpkyZpwHp+Pt9Y=; b=qm3wExthXvMikRfoqiriwt9H+SaBa1GaSFueT1q63qRVM8oJs42YljK5GtWqP8K3X8 v2WrPRyNGL2lQ6ztuCXSOyej2Q1iJMi/l5Y4zvzS6iNtf3tRtHOgxdPakM+gSHe0nZhr H7Ddt0QlmkmrbCdymJZ3ThOQY6c8PJgE0edejdvZO3Gs0Ar9ecqFMV02Xo1bZ0q/7IqN fgLCEkXY9Sx/MEEqwO+9auKZQ7K7nZuIwlDLZCEY44J5M5uVoFEA/p7GYHbvPuWP8FwH h5VqJ3jjxHR6ppZeBt40NS4tyi09iZ2qdQhES6eQi5UcqodrRm4gRYQX/UCMYtUAReg+ SmYg== MIME-Version: 1.0 Received: by 10.60.29.134 with SMTP id k6mr309207oeh.5.1347561979794; Thu, 13 Sep 2012 11:46:19 -0700 (PDT) Received: by 10.76.135.106 with HTTP; Thu, 13 Sep 2012 11:46:19 -0700 (PDT) Date: Thu, 13 Sep 2012 15:46:19 -0300 Message-ID: From: Vinicius Kwiecien Ruoso To: xen-users@lists.xen.org Subject: [Xen-users] Xen Networking X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org Hi! This is my first contact with xen, and I think it's great. I'm just having some networking problems. Let me explain how is my server situation. I have a server that act as a gateway with two network interfaces. eth0 is the interface used in the local network (ip: 172.16.10.1, 255.255.2= 55.0) eth1 is the interface connected to the internet modem (dhcp) I have a vpn interface as well (ip: 172.16.10.1, 255.255.0.0) configured with tinc. I share the internet connection with the local network using nat... (route -n && iptables) output below... Everything works great with this configuration. I've read a lot of docs about xen networking, but didn't manage to get it working. What I want to do is to give the VM the IP 172.16.10.50, 255.255.255.0 gw 172.16.10.1, just like any other machine in the local network. First things first. I've managed to install a windows xp with xen. I did it without any network configuration, i.e, no vif option at win.cfg file. OK. Now I have an installed windows, but no networking. It makes sense to me the usage of a bridge with eth0. What do you suggest? Here are the things I've tried: - vif =3D [ 'type=3Dioemu, ip=3D172.16.10.50' ] - vif =3D [ 'bridge=3Dxenbr0' ] - vif =3D [ 'type=3Dioemu, bridge=3Dxenbr0' ] I've tried those with different configurations in /etc/network/interfaces using: auto eth0 iface eth0 inet static address 172.16.10.1 netmask 255.255.255.0 auto xenbr0 iface xenbr0 inet static address 172.16.10.50 netmask 255.255.255.0 bridge_ports eth0 also didn't work. When I configure the interfaces like this and run /etc/init.d/networking restart, the eth0 looses it IP address, and nothing works anymore... I'm using Ubuntu 12.04 server... xen version 4.1.2 and 3.2.0-30-generic kernel... Thanks a lot for any help with that! Vinicius 8<-------------------------------------------- $ route -n Destino Roteador M=E1scaraGen. Op=E7=F5es M=E9trica Ref = Uso Iface 0.0.0.0 192.168.254.254 0.0.0.0 UG 100 0 0 eth1 172.16.0.0 0.0.0.0 255.255.0.0 U 0 0 0 vpn 172.16.10.0 0.0.0.0 255.255.255.0 U 0 0 0 eth0 192.168.254.0 0.0.0.0 255.255.255.0 U 0 0 0 eth1 $ iptables -t nat -L Chain PREROUTING (policy ACCEPT) target prot opt source destination Chain INPUT (policy ACCEPT) target prot opt source destination Chain OUTPUT (policy ACCEPT) target prot opt source destination Chain POSTROUTING (policy ACCEPT) target prot opt source destination MASQUERADE all -- 172.16.10.0/24 anywhere _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Thu Sep 13 18:47:30 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Thu, 13 Sep 2012 18:47:30 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TCEQi-0004TV-C4; Thu, 13 Sep 2012 18:46:24 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TCEQh-0004TO-3m for xen-users@lists.xen.org; Thu, 13 Sep 2012 18:46:23 +0000 Received: from [85.158.138.51:45333] by server-11.bemta-3.messagelabs.com id F1/AC-30250-EF922505; Thu, 13 Sep 2012 18:46:22 +0000 X-Env-Sender: vinicius.ruoso@gmail.com X-Msg-Ref: server-13.tower-174.messagelabs.com!1347561980!11757666!1 X-Originating-IP: [209.85.214.173] X-SpamReason: No, hits=0.3 required=7.0 tests=ML_RADAR_SPEW_LINKS_14, RCVD_BY_IP,spamassassin: X-StarScan-Received: X-StarScan-Version: 6.6.1.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 23321 invoked from network); 13 Sep 2012 18:46:21 -0000 Received: from mail-ob0-f173.google.com (HELO mail-ob0-f173.google.com) (209.85.214.173) by server-13.tower-174.messagelabs.com with RC4-SHA encrypted SMTP; 13 Sep 2012 18:46:21 -0000 Received: by obbta14 with SMTP id ta14so6257044obb.32 for ; Thu, 13 Sep 2012 11:46:19 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:date:message-id:subject:from:to:content-type :content-transfer-encoding; bh=oxPJSAkpa6loQCGSu0lLYrwKnp4K4IpkyZpwHp+Pt9Y=; b=qm3wExthXvMikRfoqiriwt9H+SaBa1GaSFueT1q63qRVM8oJs42YljK5GtWqP8K3X8 v2WrPRyNGL2lQ6ztuCXSOyej2Q1iJMi/l5Y4zvzS6iNtf3tRtHOgxdPakM+gSHe0nZhr H7Ddt0QlmkmrbCdymJZ3ThOQY6c8PJgE0edejdvZO3Gs0Ar9ecqFMV02Xo1bZ0q/7IqN fgLCEkXY9Sx/MEEqwO+9auKZQ7K7nZuIwlDLZCEY44J5M5uVoFEA/p7GYHbvPuWP8FwH h5VqJ3jjxHR6ppZeBt40NS4tyi09iZ2qdQhES6eQi5UcqodrRm4gRYQX/UCMYtUAReg+ SmYg== MIME-Version: 1.0 Received: by 10.60.29.134 with SMTP id k6mr309207oeh.5.1347561979794; Thu, 13 Sep 2012 11:46:19 -0700 (PDT) Received: by 10.76.135.106 with HTTP; Thu, 13 Sep 2012 11:46:19 -0700 (PDT) Date: Thu, 13 Sep 2012 15:46:19 -0300 Message-ID: From: Vinicius Kwiecien Ruoso To: xen-users@lists.xen.org Subject: [Xen-users] Xen Networking X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org Hi! This is my first contact with xen, and I think it's great. I'm just having some networking problems. Let me explain how is my server situation. I have a server that act as a gateway with two network interfaces. eth0 is the interface used in the local network (ip: 172.16.10.1, 255.255.2= 55.0) eth1 is the interface connected to the internet modem (dhcp) I have a vpn interface as well (ip: 172.16.10.1, 255.255.0.0) configured with tinc. I share the internet connection with the local network using nat... (route -n && iptables) output below... Everything works great with this configuration. I've read a lot of docs about xen networking, but didn't manage to get it working. What I want to do is to give the VM the IP 172.16.10.50, 255.255.255.0 gw 172.16.10.1, just like any other machine in the local network. First things first. I've managed to install a windows xp with xen. I did it without any network configuration, i.e, no vif option at win.cfg file. OK. Now I have an installed windows, but no networking. It makes sense to me the usage of a bridge with eth0. What do you suggest? Here are the things I've tried: - vif =3D [ 'type=3Dioemu, ip=3D172.16.10.50' ] - vif =3D [ 'bridge=3Dxenbr0' ] - vif =3D [ 'type=3Dioemu, bridge=3Dxenbr0' ] I've tried those with different configurations in /etc/network/interfaces using: auto eth0 iface eth0 inet static address 172.16.10.1 netmask 255.255.255.0 auto xenbr0 iface xenbr0 inet static address 172.16.10.50 netmask 255.255.255.0 bridge_ports eth0 also didn't work. When I configure the interfaces like this and run /etc/init.d/networking restart, the eth0 looses it IP address, and nothing works anymore... I'm using Ubuntu 12.04 server... xen version 4.1.2 and 3.2.0-30-generic kernel... Thanks a lot for any help with that! Vinicius 8<-------------------------------------------- $ route -n Destino Roteador M=E1scaraGen. Op=E7=F5es M=E9trica Ref = Uso Iface 0.0.0.0 192.168.254.254 0.0.0.0 UG 100 0 0 eth1 172.16.0.0 0.0.0.0 255.255.0.0 U 0 0 0 vpn 172.16.10.0 0.0.0.0 255.255.255.0 U 0 0 0 eth0 192.168.254.0 0.0.0.0 255.255.255.0 U 0 0 0 eth1 $ iptables -t nat -L Chain PREROUTING (policy ACCEPT) target prot opt source destination Chain INPUT (policy ACCEPT) target prot opt source destination Chain OUTPUT (policy ACCEPT) target prot opt source destination Chain POSTROUTING (policy ACCEPT) target prot opt source destination MASQUERADE all -- 172.16.10.0/24 anywhere _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Thu Sep 13 20:24:50 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Thu, 13 Sep 2012 20:24:50 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TCFwp-0005Pg-Ux; Thu, 13 Sep 2012 20:23:39 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TCFwo-0005Pb-5L for xen-users@lists.xen.org; Thu, 13 Sep 2012 20:23:38 +0000 Received: from [85.158.137.99:3785] by server-7.bemta-3.messagelabs.com id 6D/2F-32000-9C042505; Thu, 13 Sep 2012 20:23:37 +0000 X-Env-Sender: alk@ondore.com X-Msg-Ref: server-5.tower-217.messagelabs.com!1347567815!12814892!1 X-Originating-IP: [184.172.38.138] X-SpamReason: No, hits=0.0 required=7.0 tests= X-StarScan-Received: X-StarScan-Version: 6.6.1.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 14655 invoked from network); 13 Sep 2012 20:23:36 -0000 Received: from host0a.ondore-systems.com (HELO host0a.ondore-systems.com) (184.172.38.138) by server-5.tower-217.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 13 Sep 2012 20:23:36 -0000 Received: from [189.253.108.90] (port=39113 helo=mail.ondore.i) by host0a.ondore-systems.com with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.77) (envelope-from ) id 1TCFwk-0003dA-IK for xen-users@lists.xen.org; Thu, 13 Sep 2012 15:23:34 -0500 Received: from [10.13.34.156] (alk-desktop.sys.ondore.i [10.13.34.156]) by mail.ondore.i (Postfix) with ESMTPSA id 73156A209 for ; Thu, 13 Sep 2012 15:23:32 -0500 (CDT) Message-ID: <505240C4.3060403@ondore.com> Date: Thu, 13 Sep 2012 15:23:32 -0500 From: Alexandre Kouznetsov User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:14.0) Gecko/20120714 Thunderbird/14.0 MIME-Version: 1.0 To: xen-users@lists.xen.org References: In-Reply-To: X-AntiAbuse: This header was added to track abuse, please include it with any abuse report X-AntiAbuse: Primary Hostname - host0a.ondore-systems.com X-AntiAbuse: Original Domain - lists.xen.org X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12] X-AntiAbuse: Sender Address Domain - ondore.com Subject: Re: [Xen-users] Xen Networking X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset="iso-8859-1"; Format="flowed" Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org Hello. Approach one issue at time. First thing first, get a stable networking = configuration on your Dom0. Read http://wiki.xensource.com/xenwiki/XenNetworking , it has nice pictures. El 13/09/12 13:46, Vinicius Kwiecien Ruoso escribi=F3: > eth0 is the interface used in the local network (ip: 172.16.10.1, 255.255= .255.0) > eth1 is the interface connected to the internet modem (dhcp) Good. > I have a vpn interface as well (ip: 172.16.10.1, 255.255.0.0) > configured with tinc. Forget this one for the moment, shut it down while troubleshooting, if = possible. Reduce the variables. > What I want to do is to give the VM the IP 172.16.10.50, 255.255.255.0 > gw 172.16.10.1, just like any other machine in the local network. That seems the right setup. > OK. Now I have an installed windows, but no networking. > It makes sense to me the usage of a bridge with eth0. Windows is not a guest system I would start with, but should work anyway. > What do you suggest? #vif =3D [ 'mac=3D00:16:3e:XX:XX:XX,bridge=3Dxenbr0' ] vif =3D [ 'type=3Dioemu,mac=3D00:16:3e:XX:XX:XX,bridge=3Dxenbr0' ] Us the same valid MAC in both cases. Comment out the second line and = uncomment the first, when (and if) you install PV drivers. > I've tried those with different configurations in /etc/network/interfaces > > using: > auto eth0 > iface eth0 inet static > address 172.16.10.1 > netmask 255.255.255.0 > > auto xenbr0 > iface xenbr0 inet static > address 172.16.10.50 > netmask 255.255.255.0 > bridge_ports eth0 Don't do that. Do not set up IP address on the eth0 itself AND the = bridge, configure only one address once. configure Dom0's address, leave = the VM to deal with it's IP address on it's own. You probably started like this: auto eth0 iface eth0 inet static address 172.16.10.1 netmask 255.255.255.0 End like this: #auto eth0 #iface eth0 inet static # address 172.16.10.1 # netmask 255.255.255.0 auto xenbr0 iface xenbr0 inet static address 172.16.10.1 netmask 255.255.255.0 bridge_ports eth0 > also didn't work. When I configure the interfaces like this and run > /etc/init.d/networking restart, the eth0 looses it IP address, and > nothing works anymore... Note, that while you already have VMs running, a "networking restart" is = not a good idea: a starting VM will attach it's network interface to a = existing bridge, after a "network restart" this on-the-fly configuration = will be broken. If there is no running VM's, "network restart" should be a valid operation. I am leaving out of this the masquerading setup. It's complete different = matter, approach it once your networking is fine. Cheers. -- = Alexandre Kouznetsov _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Thu Sep 13 20:24:50 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Thu, 13 Sep 2012 20:24:50 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TCFwp-0005Pg-Ux; Thu, 13 Sep 2012 20:23:39 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TCFwo-0005Pb-5L for xen-users@lists.xen.org; Thu, 13 Sep 2012 20:23:38 +0000 Received: from [85.158.137.99:3785] by server-7.bemta-3.messagelabs.com id 6D/2F-32000-9C042505; Thu, 13 Sep 2012 20:23:37 +0000 X-Env-Sender: alk@ondore.com X-Msg-Ref: server-5.tower-217.messagelabs.com!1347567815!12814892!1 X-Originating-IP: [184.172.38.138] X-SpamReason: No, hits=0.0 required=7.0 tests= X-StarScan-Received: X-StarScan-Version: 6.6.1.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 14655 invoked from network); 13 Sep 2012 20:23:36 -0000 Received: from host0a.ondore-systems.com (HELO host0a.ondore-systems.com) (184.172.38.138) by server-5.tower-217.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 13 Sep 2012 20:23:36 -0000 Received: from [189.253.108.90] (port=39113 helo=mail.ondore.i) by host0a.ondore-systems.com with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.77) (envelope-from ) id 1TCFwk-0003dA-IK for xen-users@lists.xen.org; Thu, 13 Sep 2012 15:23:34 -0500 Received: from [10.13.34.156] (alk-desktop.sys.ondore.i [10.13.34.156]) by mail.ondore.i (Postfix) with ESMTPSA id 73156A209 for ; Thu, 13 Sep 2012 15:23:32 -0500 (CDT) Message-ID: <505240C4.3060403@ondore.com> Date: Thu, 13 Sep 2012 15:23:32 -0500 From: Alexandre Kouznetsov User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:14.0) Gecko/20120714 Thunderbird/14.0 MIME-Version: 1.0 To: xen-users@lists.xen.org References: In-Reply-To: X-AntiAbuse: This header was added to track abuse, please include it with any abuse report X-AntiAbuse: Primary Hostname - host0a.ondore-systems.com X-AntiAbuse: Original Domain - lists.xen.org X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12] X-AntiAbuse: Sender Address Domain - ondore.com Subject: Re: [Xen-users] Xen Networking X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset="iso-8859-1"; Format="flowed" Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org Hello. Approach one issue at time. First thing first, get a stable networking = configuration on your Dom0. Read http://wiki.xensource.com/xenwiki/XenNetworking , it has nice pictures. El 13/09/12 13:46, Vinicius Kwiecien Ruoso escribi=F3: > eth0 is the interface used in the local network (ip: 172.16.10.1, 255.255= .255.0) > eth1 is the interface connected to the internet modem (dhcp) Good. > I have a vpn interface as well (ip: 172.16.10.1, 255.255.0.0) > configured with tinc. Forget this one for the moment, shut it down while troubleshooting, if = possible. Reduce the variables. > What I want to do is to give the VM the IP 172.16.10.50, 255.255.255.0 > gw 172.16.10.1, just like any other machine in the local network. That seems the right setup. > OK. Now I have an installed windows, but no networking. > It makes sense to me the usage of a bridge with eth0. Windows is not a guest system I would start with, but should work anyway. > What do you suggest? #vif =3D [ 'mac=3D00:16:3e:XX:XX:XX,bridge=3Dxenbr0' ] vif =3D [ 'type=3Dioemu,mac=3D00:16:3e:XX:XX:XX,bridge=3Dxenbr0' ] Us the same valid MAC in both cases. Comment out the second line and = uncomment the first, when (and if) you install PV drivers. > I've tried those with different configurations in /etc/network/interfaces > > using: > auto eth0 > iface eth0 inet static > address 172.16.10.1 > netmask 255.255.255.0 > > auto xenbr0 > iface xenbr0 inet static > address 172.16.10.50 > netmask 255.255.255.0 > bridge_ports eth0 Don't do that. Do not set up IP address on the eth0 itself AND the = bridge, configure only one address once. configure Dom0's address, leave = the VM to deal with it's IP address on it's own. You probably started like this: auto eth0 iface eth0 inet static address 172.16.10.1 netmask 255.255.255.0 End like this: #auto eth0 #iface eth0 inet static # address 172.16.10.1 # netmask 255.255.255.0 auto xenbr0 iface xenbr0 inet static address 172.16.10.1 netmask 255.255.255.0 bridge_ports eth0 > also didn't work. When I configure the interfaces like this and run > /etc/init.d/networking restart, the eth0 looses it IP address, and > nothing works anymore... Note, that while you already have VMs running, a "networking restart" is = not a good idea: a starting VM will attach it's network interface to a = existing bridge, after a "network restart" this on-the-fly configuration = will be broken. If there is no running VM's, "network restart" should be a valid operation. I am leaving out of this the masquerading setup. It's complete different = matter, approach it once your networking is fine. Cheers. -- = Alexandre Kouznetsov _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Thu Sep 13 21:56:11 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Thu, 13 Sep 2012 21:56:11 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TCHN9-0006XC-1B; Thu, 13 Sep 2012 21:54:55 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TCHN7-0006X7-Ir for xen-users@lists.xen.org; Thu, 13 Sep 2012 21:54:53 +0000 Received: from [85.158.143.99:47575] by server-2.bemta-4.messagelabs.com id 23/94-21239-C2652505; Thu, 13 Sep 2012 21:54:52 +0000 X-Env-Sender: fajar@fajar.net X-Msg-Ref: server-10.tower-216.messagelabs.com!1347573291!23838506!1 X-Originating-IP: [209.85.219.45] X-SpamReason: No, hits=0.3 required=7.0 tests=RCVD_BY_IP X-StarScan-Received: X-StarScan-Version: 6.6.1.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 28195 invoked from network); 13 Sep 2012 21:54:52 -0000 Received: from mail-oa0-f45.google.com (HELO mail-oa0-f45.google.com) (209.85.219.45) by server-10.tower-216.messagelabs.com with RC4-SHA encrypted SMTP; 13 Sep 2012 21:54:52 -0000 Received: by oagn12 with SMTP id n12so2860124oag.32 for ; Thu, 13 Sep 2012 14:54:50 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:x-gm-message-state; bh=WHNyMF1MxWd0gPrmGbc6ds6fQ1j4IYamK6kER05Dcak=; b=PYixGowb/FzJ0m5choGWU8GWTYjs0U1W0nC+zkp56wVn8ctwPpHsMjqr8vNKI8aB3y TT0xiclzh1P8L3WVtWk/JkgyPko4NWKTINVQSVh4dMFTtXp9MgBPL18EGS7a+vVXALYr 7v+yezcr8w/CNYuMVz1vz6OWe/vBr8E9AET4CUoACyjGqQ0l1c/mvJkvH2FFvKvqpp86 TDq9X1EIgiZKn5QsfQ+ZXwM3tcsO410LmnrPRxbWyBy2RUVPkrg9wUTjN+Fnk73cVaX2 xPYDKpd1fBtunAgaIJ4C+PBTL1g5MvJExJQqc4cgzJ7j4veBI4L6PhowAbikwWCy46TO ru5Q== MIME-Version: 1.0 Received: by 10.60.8.39 with SMTP id o7mr633375oea.122.1347573290567; Thu, 13 Sep 2012 14:54:50 -0700 (PDT) Received: by 10.60.6.230 with HTTP; Thu, 13 Sep 2012 14:54:50 -0700 (PDT) In-Reply-To: References: Date: Fri, 14 Sep 2012 04:54:50 +0700 Message-ID: From: "Fajar A. Nugraha" To: Vinicius Kwiecien Ruoso X-Gm-Message-State: ALoCoQkOVwxzhiBDk/Dz/DdieVF6xu++/c3XsPIQ174ePYUnkpMQGg0gsI3YxM3YaAKmGqR8Rti0 Cc: xen-users@lists.xen.org Subject: Re: [Xen-users] Xen Networking X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org On Fri, Sep 14, 2012 at 1:46 AM, Vinicius Kwiecien Ruoso wrote: > I've tried those with different configurations in /etc/network/interfaces > > using: > auto eth0 > iface eth0 inet static > address 172.16.10.1 > netmask 255.255.255.0 > > auto xenbr0 > iface xenbr0 inet static > address 172.16.10.50 > netmask 255.255.255.0 > bridge_ports eth0 > > > also didn't work. When I configure the interfaces like this and run > /etc/init.d/networking restart, the eth0 looses it IP address, and > nothing works anymore... Duh. Your config is wrong. If eth0 is part of the bridge, then you put the IP on the bridge, not on eth0. Examples (both assume you use dhcp, adjust as needed): - http://wiki.xen.org/wiki/Xen_Beginners_Guide#Setup_Linux_Bridge_for_guest_networking - http://wiki.1tux.org/wiki/Ubuntu/Bridge -- Fajar _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Thu Sep 13 21:56:11 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Thu, 13 Sep 2012 21:56:11 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TCHN9-0006XC-1B; Thu, 13 Sep 2012 21:54:55 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TCHN7-0006X7-Ir for xen-users@lists.xen.org; Thu, 13 Sep 2012 21:54:53 +0000 Received: from [85.158.143.99:47575] by server-2.bemta-4.messagelabs.com id 23/94-21239-C2652505; Thu, 13 Sep 2012 21:54:52 +0000 X-Env-Sender: fajar@fajar.net X-Msg-Ref: server-10.tower-216.messagelabs.com!1347573291!23838506!1 X-Originating-IP: [209.85.219.45] X-SpamReason: No, hits=0.3 required=7.0 tests=RCVD_BY_IP X-StarScan-Received: X-StarScan-Version: 6.6.1.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 28195 invoked from network); 13 Sep 2012 21:54:52 -0000 Received: from mail-oa0-f45.google.com (HELO mail-oa0-f45.google.com) (209.85.219.45) by server-10.tower-216.messagelabs.com with RC4-SHA encrypted SMTP; 13 Sep 2012 21:54:52 -0000 Received: by oagn12 with SMTP id n12so2860124oag.32 for ; Thu, 13 Sep 2012 14:54:50 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:x-gm-message-state; bh=WHNyMF1MxWd0gPrmGbc6ds6fQ1j4IYamK6kER05Dcak=; b=PYixGowb/FzJ0m5choGWU8GWTYjs0U1W0nC+zkp56wVn8ctwPpHsMjqr8vNKI8aB3y TT0xiclzh1P8L3WVtWk/JkgyPko4NWKTINVQSVh4dMFTtXp9MgBPL18EGS7a+vVXALYr 7v+yezcr8w/CNYuMVz1vz6OWe/vBr8E9AET4CUoACyjGqQ0l1c/mvJkvH2FFvKvqpp86 TDq9X1EIgiZKn5QsfQ+ZXwM3tcsO410LmnrPRxbWyBy2RUVPkrg9wUTjN+Fnk73cVaX2 xPYDKpd1fBtunAgaIJ4C+PBTL1g5MvJExJQqc4cgzJ7j4veBI4L6PhowAbikwWCy46TO ru5Q== MIME-Version: 1.0 Received: by 10.60.8.39 with SMTP id o7mr633375oea.122.1347573290567; Thu, 13 Sep 2012 14:54:50 -0700 (PDT) Received: by 10.60.6.230 with HTTP; Thu, 13 Sep 2012 14:54:50 -0700 (PDT) In-Reply-To: References: Date: Fri, 14 Sep 2012 04:54:50 +0700 Message-ID: From: "Fajar A. Nugraha" To: Vinicius Kwiecien Ruoso X-Gm-Message-State: ALoCoQkOVwxzhiBDk/Dz/DdieVF6xu++/c3XsPIQ174ePYUnkpMQGg0gsI3YxM3YaAKmGqR8Rti0 Cc: xen-users@lists.xen.org Subject: Re: [Xen-users] Xen Networking X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org On Fri, Sep 14, 2012 at 1:46 AM, Vinicius Kwiecien Ruoso wrote: > I've tried those with different configurations in /etc/network/interfaces > > using: > auto eth0 > iface eth0 inet static > address 172.16.10.1 > netmask 255.255.255.0 > > auto xenbr0 > iface xenbr0 inet static > address 172.16.10.50 > netmask 255.255.255.0 > bridge_ports eth0 > > > also didn't work. When I configure the interfaces like this and run > /etc/init.d/networking restart, the eth0 looses it IP address, and > nothing works anymore... Duh. Your config is wrong. If eth0 is part of the bridge, then you put the IP on the bridge, not on eth0. Examples (both assume you use dhcp, adjust as needed): - http://wiki.xen.org/wiki/Xen_Beginners_Guide#Setup_Linux_Bridge_for_guest_networking - http://wiki.1tux.org/wiki/Ubuntu/Bridge -- Fajar _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Fri Sep 14 07:54:50 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Fri, 14 Sep 2012 07:54:50 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TCQiR-0006gb-UW; Fri, 14 Sep 2012 07:53:31 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TCQiP-0006gW-S5 for xen-users@lists.xen.org; Fri, 14 Sep 2012 07:53:30 +0000 Received: from [85.158.138.51:7309] by server-7.bemta-3.messagelabs.com id 0C/7D-32000-972E2505; Fri, 14 Sep 2012 07:53:29 +0000 X-Env-Sender: james.harper@bendigoit.com.au X-Msg-Ref: server-16.tower-174.messagelabs.com!1347609205!30419519!1 X-Originating-IP: [203.16.207.99] X-SpamReason: No, hits=0.0 required=7.0 tests= X-StarScan-Received: X-StarScan-Version: 6.6.1.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 6134 invoked from network); 14 Sep 2012 07:53:27 -0000 Received: from mail.bendigoit.com.au (HELO smtp2.bendigoit.com.au) (203.16.207.99) by server-16.tower-174.messagelabs.com with AES256-SHA encrypted SMTP; 14 Sep 2012 07:53:27 -0000 Received: from [2001:388:e000:712:a5ca:4fd3:14f:ad5d] (helo=BITCOM1.int.sbss.com.au) by smtp2.bendigoit.com.au with esmtp (Exim 4.72) (envelope-from ) id 1TCQiI-0001En-H3; Fri, 14 Sep 2012 17:53:22 +1000 Received: from BITCOM1.int.sbss.com.au ([fe80::a5ca:4fd3:14f:ad5d]) by BITCOM1.int.sbss.com.au ([fe80::a5ca:4fd3:14f:ad5d%12]) with mapi id 14.01.0379.000; Fri, 14 Sep 2012 17:53:14 +1000 From: James Harper To: Adam Goryachev , "xen-users@lists.xen.org" Thread-Topic: [Xen-users] Poor Windows 2003 + GPLPV performance compared to VMWare Thread-Index: AQHNkazQlsMWuA2xT0e0G95Jil+zU5eJdx7g Date: Fri, 14 Sep 2012 07:53:13 +0000 Message-ID: <6035A0D088A63A46850C3988ED045A4B29B7A328@BITCOM1.int.sbss.com.au> References: <5051D0C5.5070600@websitemanagers.com.au> In-Reply-To: <5051D0C5.5070600@websitemanagers.com.au> Accept-Language: en-AU, en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [120.151.4.232] x-tm-as-product-ver: SMEX-10.2.0.2087-7.000.1014-19182.005 x-tm-as-result: No--44.485400-0.000000-31 x-tm-as-user-approved-sender: Yes x-tm-as-user-blocked-sender: No MIME-Version: 1.0 X-Really-From-Bendigo-IT: magichashvalue Subject: Re: [Xen-users] Poor Windows 2003 + GPLPV performance compared to VMWare X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org Is it AMD or Intel architecture? You mention iSCSI... is your benchmark measuring disk activity or some combination of things to give a total performance benchmark? If I understand correctly, you have iSCSI, then Xen, then GPLPV. Is there a way you could test iscsi performance in Dom0 without involving a DomU? The probably is that there are a few layers involved here so it's hard to know which one is letting you down. James > -----Original Message----- > From: xen-users-bounces@lists.xen.org [mailto:xen-users- > bounces@lists.xen.org] On Behalf Of Adam Goryachev > Sent: Thursday, 13 September 2012 10:26 PM > To: xen-users@lists.xen.org > Subject: [Xen-users] Poor Windows 2003 + GPLPV performance compared to > VMWare > > I have an application server running on MS Windows 2003, which was a clean > install on VMWare last year (after a failed migration attempt to XenServer). > > At this point, a benchmark (actually a live process run regularly on the > machine) produced a result of 7800 to 7900 transactions per second > > I've recently migrated this to Xen by: > 1) Uninstall VMWare tools > 2) Shutdown Windows > 3) Use VMWare to download the vmdk > 4) Write the VMDK file (dd) to the same LVM that contained the VMWare > storage area (which was exported by iSCSI to VMWare > 5) Installed Debian Testing with Xen 4.1 > 6) Using the exactl same iSCSI server/LVM config etc, started the VM > 7) Installed the GPLPV drivers > > Everything seemed to work, and all was good. > > Then, the user ran the above process, and got consistently, results of approx > 2500 transactions per second > > I increased the vcpus from 2 to 4, but this didn't change the result at all. > > I modifed the domU config for the disk line from hda to xvda, and the result > increased slightly to 2560 / sec (these tests are just one off tests, no > verification of actual performance increase etc...). > > In any case, I seem to have a significant loss of performance on the domU > when compared to VMWare. > > The storage server/network is identical > The dom0 machine is identical to the VMWare machine > > Here is my current domU config file: > > kernel = "/usr/lib/xen-4.1/boot/hvmloader" > builder = 'hvm' > memory = 4096 > shadow_memory = 12 > device_model = '/usr/lib/xen-default/bin/qemu-dm' > localtime = 1 > name = "vm1" > cpus = "2,3,4,5" # Which physical CPU's to allow > vcpus = 4 # How many Virtual CPU's to present > viridian = 1 > disk = [ > 'phy:/dev/disk/by-path/ip-10.30.10.23:3260-iscsi-iqn.2012-06.domain:vm1- > lun-0,xvda,w' > ] > vif = ['bridge=xenbr0, mac=00:16:3e:39:10:1a'] > boot = 'c' > sdl = 0 > vnc = 1 > vncdisplay = 10 > vncviewer = 0 > vncconsole = 0 > vncunused = 0 > stdvga = 1 > usb = 1 > usbdevice = 'tablet' > acpi = 1 > apic = 1 > on_reboot = 'restart' > on_poweroff = 'destroy' > on_crash = 'restart' > audio = 0 > > Any suggestions on how to improve performance would be greatly > appreciated. > > Thank you, > Adam > > -- > Adam Goryachev > Website Managers > www.websitemanagers.com.au > > > _______________________________________________ > Xen-users mailing list > Xen-users@lists.xen.org > http://lists.xen.org/xen-users _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Fri Sep 14 07:54:50 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Fri, 14 Sep 2012 07:54:50 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TCQiR-0006gb-UW; Fri, 14 Sep 2012 07:53:31 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TCQiP-0006gW-S5 for xen-users@lists.xen.org; Fri, 14 Sep 2012 07:53:30 +0000 Received: from [85.158.138.51:7309] by server-7.bemta-3.messagelabs.com id 0C/7D-32000-972E2505; Fri, 14 Sep 2012 07:53:29 +0000 X-Env-Sender: james.harper@bendigoit.com.au X-Msg-Ref: server-16.tower-174.messagelabs.com!1347609205!30419519!1 X-Originating-IP: [203.16.207.99] X-SpamReason: No, hits=0.0 required=7.0 tests= X-StarScan-Received: X-StarScan-Version: 6.6.1.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 6134 invoked from network); 14 Sep 2012 07:53:27 -0000 Received: from mail.bendigoit.com.au (HELO smtp2.bendigoit.com.au) (203.16.207.99) by server-16.tower-174.messagelabs.com with AES256-SHA encrypted SMTP; 14 Sep 2012 07:53:27 -0000 Received: from [2001:388:e000:712:a5ca:4fd3:14f:ad5d] (helo=BITCOM1.int.sbss.com.au) by smtp2.bendigoit.com.au with esmtp (Exim 4.72) (envelope-from ) id 1TCQiI-0001En-H3; Fri, 14 Sep 2012 17:53:22 +1000 Received: from BITCOM1.int.sbss.com.au ([fe80::a5ca:4fd3:14f:ad5d]) by BITCOM1.int.sbss.com.au ([fe80::a5ca:4fd3:14f:ad5d%12]) with mapi id 14.01.0379.000; Fri, 14 Sep 2012 17:53:14 +1000 From: James Harper To: Adam Goryachev , "xen-users@lists.xen.org" Thread-Topic: [Xen-users] Poor Windows 2003 + GPLPV performance compared to VMWare Thread-Index: AQHNkazQlsMWuA2xT0e0G95Jil+zU5eJdx7g Date: Fri, 14 Sep 2012 07:53:13 +0000 Message-ID: <6035A0D088A63A46850C3988ED045A4B29B7A328@BITCOM1.int.sbss.com.au> References: <5051D0C5.5070600@websitemanagers.com.au> In-Reply-To: <5051D0C5.5070600@websitemanagers.com.au> Accept-Language: en-AU, en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [120.151.4.232] x-tm-as-product-ver: SMEX-10.2.0.2087-7.000.1014-19182.005 x-tm-as-result: No--44.485400-0.000000-31 x-tm-as-user-approved-sender: Yes x-tm-as-user-blocked-sender: No MIME-Version: 1.0 X-Really-From-Bendigo-IT: magichashvalue Subject: Re: [Xen-users] Poor Windows 2003 + GPLPV performance compared to VMWare X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org Is it AMD or Intel architecture? You mention iSCSI... is your benchmark measuring disk activity or some combination of things to give a total performance benchmark? If I understand correctly, you have iSCSI, then Xen, then GPLPV. Is there a way you could test iscsi performance in Dom0 without involving a DomU? The probably is that there are a few layers involved here so it's hard to know which one is letting you down. James > -----Original Message----- > From: xen-users-bounces@lists.xen.org [mailto:xen-users- > bounces@lists.xen.org] On Behalf Of Adam Goryachev > Sent: Thursday, 13 September 2012 10:26 PM > To: xen-users@lists.xen.org > Subject: [Xen-users] Poor Windows 2003 + GPLPV performance compared to > VMWare > > I have an application server running on MS Windows 2003, which was a clean > install on VMWare last year (after a failed migration attempt to XenServer). > > At this point, a benchmark (actually a live process run regularly on the > machine) produced a result of 7800 to 7900 transactions per second > > I've recently migrated this to Xen by: > 1) Uninstall VMWare tools > 2) Shutdown Windows > 3) Use VMWare to download the vmdk > 4) Write the VMDK file (dd) to the same LVM that contained the VMWare > storage area (which was exported by iSCSI to VMWare > 5) Installed Debian Testing with Xen 4.1 > 6) Using the exactl same iSCSI server/LVM config etc, started the VM > 7) Installed the GPLPV drivers > > Everything seemed to work, and all was good. > > Then, the user ran the above process, and got consistently, results of approx > 2500 transactions per second > > I increased the vcpus from 2 to 4, but this didn't change the result at all. > > I modifed the domU config for the disk line from hda to xvda, and the result > increased slightly to 2560 / sec (these tests are just one off tests, no > verification of actual performance increase etc...). > > In any case, I seem to have a significant loss of performance on the domU > when compared to VMWare. > > The storage server/network is identical > The dom0 machine is identical to the VMWare machine > > Here is my current domU config file: > > kernel = "/usr/lib/xen-4.1/boot/hvmloader" > builder = 'hvm' > memory = 4096 > shadow_memory = 12 > device_model = '/usr/lib/xen-default/bin/qemu-dm' > localtime = 1 > name = "vm1" > cpus = "2,3,4,5" # Which physical CPU's to allow > vcpus = 4 # How many Virtual CPU's to present > viridian = 1 > disk = [ > 'phy:/dev/disk/by-path/ip-10.30.10.23:3260-iscsi-iqn.2012-06.domain:vm1- > lun-0,xvda,w' > ] > vif = ['bridge=xenbr0, mac=00:16:3e:39:10:1a'] > boot = 'c' > sdl = 0 > vnc = 1 > vncdisplay = 10 > vncviewer = 0 > vncconsole = 0 > vncunused = 0 > stdvga = 1 > usb = 1 > usbdevice = 'tablet' > acpi = 1 > apic = 1 > on_reboot = 'restart' > on_poweroff = 'destroy' > on_crash = 'restart' > audio = 0 > > Any suggestions on how to improve performance would be greatly > appreciated. > > Thank you, > Adam > > -- > Adam Goryachev > Website Managers > www.websitemanagers.com.au > > > _______________________________________________ > Xen-users mailing list > Xen-users@lists.xen.org > http://lists.xen.org/xen-users _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Fri Sep 14 08:06:13 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Fri, 14 Sep 2012 08:06:13 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TCQtJ-0007Nb-Cr; Fri, 14 Sep 2012 08:04:45 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TCQtH-0007NW-M3 for xen-users@lists.xen.org; Fri, 14 Sep 2012 08:04:44 +0000 Received: from [85.158.138.51:45787] by server-5.bemta-3.messagelabs.com id C2/08-13133-A15E2505; Fri, 14 Sep 2012 08:04:42 +0000 X-Env-Sender: Ian.Campbell@citrix.com X-Msg-Ref: server-12.tower-174.messagelabs.com!1347609882!22571808!1 X-Originating-IP: [62.200.22.115] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogNjIuMjAwLjIyLjExNSA9PiAxMDkxNTg=\n X-StarScan-Received: X-StarScan-Version: 6.6.1.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 27652 invoked from network); 14 Sep 2012 08:04:42 -0000 Received: from smtp.ctxuk.citrix.com (HELO SMTP.EU.CITRIX.COM) (62.200.22.115) by server-12.tower-174.messagelabs.com with RC4-SHA encrypted SMTP; 14 Sep 2012 08:04:42 -0000 X-IronPort-AV: E=Sophos;i="4.80,422,1344211200"; d="scan'208";a="14538577" Received: from lonpmailmx01.citrite.net ([10.30.203.162]) by LONPIPO01.EU.CITRIX.COM with ESMTP/TLS/RC4-MD5; 14 Sep 2012 08:04:41 +0000 Received: from [10.80.2.42] (10.80.2.42) by LONPMAILMX01.citrite.net (10.30.203.162) with Microsoft SMTP Server id 8.3.279.1; Fri, 14 Sep 2012 09:04:41 +0100 Message-ID: <1347609879.24226.148.camel@zakaz.uk.xensource.com> From: Ian Campbell To: Adam Goryachev Date: Fri, 14 Sep 2012 09:04:39 +0100 In-Reply-To: <5051D0C5.5070600@websitemanagers.com.au> References: <5051D0C5.5070600@websitemanagers.com.au> Organization: Citrix Systems, Inc. X-Mailer: Evolution 3.4.3-1 MIME-Version: 1.0 Cc: "xen-users@lists.xen.org" Subject: Re: [Xen-users] Poor Windows 2003 + GPLPV performance compared to VMWare X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org On Thu, 2012-09-13 at 13:25 +0100, Adam Goryachev wrote: > Then, the user ran the above process, and got consistently, results of > approx 2500 transactions per second Are you certain the GPLPV drivers have taken hold and you aren't using emulated devices? I don't know how you can tell from within Windows but from dom0 you can look in the output of "xenstore-ls -fp" for the "state" node associated with each device frontend -- they should be in state 4 (connected). [...] > memory = 4096 > shadow_memory = 12 This seems low to me. The default is 1M per CPU, plus 8K per M of RAM, which is 4M + 8*4096K = 4M+32M = 36M. Do you have any reason to second guess this? (Usually this option is used to increase shadow RAM where the workload demands it). Does your system have HAP (hardware assisted paging, EPT or NPT on Intel/AMD respectively)? > device_model = '/usr/lib/xen-default/bin/qemu-dm' > localtime = 1 > name = "vm1" > cpus = "2,3,4,5" # Which physical CPU's to allow Have you pinned dom0 to use pCPU 1 and/p pCPUs > 6? How many dom0 vcpus have you configured? Does your system have any NUMA properties? And as James suggests it would also be useful to benchmark iSCSI running in dom0 and perhaps even running on the same system without Xen (just Linux) using the same kernel. I'm not sure if VMware offers something similar which could be used for comparison. Ian. _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Fri Sep 14 08:06:13 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Fri, 14 Sep 2012 08:06:13 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TCQtJ-0007Nb-Cr; Fri, 14 Sep 2012 08:04:45 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TCQtH-0007NW-M3 for xen-users@lists.xen.org; Fri, 14 Sep 2012 08:04:44 +0000 Received: from [85.158.138.51:45787] by server-5.bemta-3.messagelabs.com id C2/08-13133-A15E2505; Fri, 14 Sep 2012 08:04:42 +0000 X-Env-Sender: Ian.Campbell@citrix.com X-Msg-Ref: server-12.tower-174.messagelabs.com!1347609882!22571808!1 X-Originating-IP: [62.200.22.115] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogNjIuMjAwLjIyLjExNSA9PiAxMDkxNTg=\n X-StarScan-Received: X-StarScan-Version: 6.6.1.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 27652 invoked from network); 14 Sep 2012 08:04:42 -0000 Received: from smtp.ctxuk.citrix.com (HELO SMTP.EU.CITRIX.COM) (62.200.22.115) by server-12.tower-174.messagelabs.com with RC4-SHA encrypted SMTP; 14 Sep 2012 08:04:42 -0000 X-IronPort-AV: E=Sophos;i="4.80,422,1344211200"; d="scan'208";a="14538577" Received: from lonpmailmx01.citrite.net ([10.30.203.162]) by LONPIPO01.EU.CITRIX.COM with ESMTP/TLS/RC4-MD5; 14 Sep 2012 08:04:41 +0000 Received: from [10.80.2.42] (10.80.2.42) by LONPMAILMX01.citrite.net (10.30.203.162) with Microsoft SMTP Server id 8.3.279.1; Fri, 14 Sep 2012 09:04:41 +0100 Message-ID: <1347609879.24226.148.camel@zakaz.uk.xensource.com> From: Ian Campbell To: Adam Goryachev Date: Fri, 14 Sep 2012 09:04:39 +0100 In-Reply-To: <5051D0C5.5070600@websitemanagers.com.au> References: <5051D0C5.5070600@websitemanagers.com.au> Organization: Citrix Systems, Inc. X-Mailer: Evolution 3.4.3-1 MIME-Version: 1.0 Cc: "xen-users@lists.xen.org" Subject: Re: [Xen-users] Poor Windows 2003 + GPLPV performance compared to VMWare X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org On Thu, 2012-09-13 at 13:25 +0100, Adam Goryachev wrote: > Then, the user ran the above process, and got consistently, results of > approx 2500 transactions per second Are you certain the GPLPV drivers have taken hold and you aren't using emulated devices? I don't know how you can tell from within Windows but from dom0 you can look in the output of "xenstore-ls -fp" for the "state" node associated with each device frontend -- they should be in state 4 (connected). [...] > memory = 4096 > shadow_memory = 12 This seems low to me. The default is 1M per CPU, plus 8K per M of RAM, which is 4M + 8*4096K = 4M+32M = 36M. Do you have any reason to second guess this? (Usually this option is used to increase shadow RAM where the workload demands it). Does your system have HAP (hardware assisted paging, EPT or NPT on Intel/AMD respectively)? > device_model = '/usr/lib/xen-default/bin/qemu-dm' > localtime = 1 > name = "vm1" > cpus = "2,3,4,5" # Which physical CPU's to allow Have you pinned dom0 to use pCPU 1 and/p pCPUs > 6? How many dom0 vcpus have you configured? Does your system have any NUMA properties? And as James suggests it would also be useful to benchmark iSCSI running in dom0 and perhaps even running on the same system without Xen (just Linux) using the same kernel. I'm not sure if VMware offers something similar which could be used for comparison. Ian. _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Fri Sep 14 13:12:59 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Fri, 14 Sep 2012 13:12:59 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TCVgO-0003Yv-Lt; Fri, 14 Sep 2012 13:11:44 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TCVgN-0003Yo-39 for xen-users@lists.xen.org; Fri, 14 Sep 2012 13:11:43 +0000 Received: from [85.158.143.35:12485] by server-1.bemta-4.messagelabs.com id 5D/F2-12504-E0D23505; Fri, 14 Sep 2012 13:11:42 +0000 X-Env-Sender: mailinglists@websitemanagers.com.au X-Msg-Ref: server-6.tower-21.messagelabs.com!1347628297!18264403!1 X-Originating-IP: [203.56.191.70] X-SpamReason: No, hits=0.0 required=7.0 tests= X-StarScan-Received: X-StarScan-Version: 6.6.1.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 24200 invoked from network); 14 Sep 2012 13:11:40 -0000 Received: from unknown (HELO hammer.websitemanagers.com.au) (203.56.191.70) by server-6.tower-21.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 14 Sep 2012 13:11:40 -0000 Received: (qmail 5432 invoked by uid 1011); 14 Sep 2012 13:11:06 -0000 Received: from 124.246.8.196 by hammer (envelope-from , uid 1008) with qmail-scanner-1.24 (clamdscan: 0.97.3/15354. spamassassin: 3.3.1. Clear:RC:1(124.246.8.196):. Processed in 0.103502 secs); 14 Sep 2012 13:11:06 -0000 Received: from unknown (HELO ?192.168.2.90?) (124.246.8.196) by 0 with SMTP; 14 Sep 2012 13:11:06 -0000 Message-ID: <50532CE9.5080601@websitemanagers.com.au> Date: Fri, 14 Sep 2012 23:11:05 +1000 From: Adam Goryachev Organization: Website Managers User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:15.0) Gecko/20120827 Thunderbird/15.0 MIME-Version: 1.0 To: Ian Campbell References: <5051D0C5.5070600@websitemanagers.com.au> <1347609879.24226.148.camel@zakaz.uk.xensource.com> In-Reply-To: <1347609879.24226.148.camel@zakaz.uk.xensource.com> Cc: "xen-users@lists.xen.org" Subject: Re: [Xen-users] Poor Windows 2003 + GPLPV performance compared to VMWare X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: base64 Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org T24gMTQvMDkvMTIgMTg6MDQsIElhbiBDYW1wYmVsbCB3cm90ZToKPiBPbiBUaHUsIDIwMTItMDkt MTMgYXQgMTM6MjUgKzAxMDAsIEFkYW0gR29yeWFjaGV2IHdyb3RlOgo+PiBUaGVuLCB0aGUgdXNl ciByYW4gdGhlIGFib3ZlIHByb2Nlc3MsIGFuZCBnb3QgY29uc2lzdGVudGx5LCByZXN1bHRzIG9m Cj4+IGFwcHJveCAyNTAwIHRyYW5zYWN0aW9ucyBwZXIgc2Vjb25kCj4gCj4gQXJlIHlvdSBjZXJ0 YWluIHRoZSBHUExQViBkcml2ZXJzIGhhdmUgdGFrZW4gaG9sZCBhbmQgeW91IGFyZW4ndCB1c2lu Zwo+IGVtdWxhdGVkIGRldmljZXM/CgpXaXRoaW4gV2luZG93cywgRGV2aWNlIE1hbmFnZXIgc2hv d3MgdGhlIERpc2sgRHJpdmVzIGFzICJYRVYgUFYgRElTSwpTQ1NJIERpc2sgRGV2aWNlIiwgdGhp cyBpcyB0aGUgbmV3ZXN0IG9uZSB3aGljaCBpdCBkZXRlY3RlZCBhbmQKaW5zdGFsbGVkIGFmdGVy IEkgY2hhbmdlZCB0aGUgY29uZmlnIGZyb20gaGRhIHRvIHh2ZGEuCgo+IEkgZG9uJ3Qga25vdyBo b3cgeW91IGNhbiB0ZWxsIGZyb20gd2l0aGluIFdpbmRvd3MgYnV0IGZyb20gZG9tMCB5b3UgY2Fu Cj4gbG9vayBpbiB0aGUgb3V0cHV0IG9mICJ4ZW5zdG9yZS1scyAtZnAiIGZvciB0aGUgInN0YXRl IiBub2RlIGFzc29jaWF0ZWQKPiB3aXRoIGVhY2ggZGV2aWNlIGZyb250ZW5kIC0tIHRoZXkgc2hv dWxkIGJlIGluIHN0YXRlIDQgKGNvbm5lY3RlZCkuCgpyb290QHBtMDg6fiMgeGVuc3RvcmUtbHMg LWZwfGdyZXAgc3RhdGV8Z3JlcCB2YmQKL2xvY2FsL2RvbWFpbi8wL2JhY2tlbmQvdmJkLzgvNTE3 MTIvc3RhdGUgPSAiNCIgICAobjAscjgpCi9sb2NhbC9kb21haW4vOC9kZXZpY2UvdmJkLzUxNzEy L3N0YXRlID0gIjQiICAgKG44LHIwKQoKSSBhc3N1bWUgZG9tIGlkIDggaXMgdGhlIFZNLCBhbmQg ZG9tMCBpcyB0aGUgZmlyc3QgbGluZSBhYm92ZS4KCj4gWy4uLl0KPj4gbWVtb3J5ICAgICAgICA9 IDQwOTYKPj4gc2hhZG93X21lbW9yeSAgICA9IDEyCj4gCj4gVGhpcyBzZWVtcyBsb3cgdG8gbWUu IFRoZSBkZWZhdWx0IGlzIDFNIHBlciBDUFUsIHBsdXMgOEsgcGVyIE0gb2YgUkFNLAo+IHdoaWNo IGlzIDRNICsgOCo0MDk2SyA9IDRNKzMyTSA9IDM2TS4gRG8geW91IGhhdmUgYW55IHJlYXNvbiB0 byBzZWNvbmQKPiBndWVzcyB0aGlzPyAoVXN1YWxseSB0aGlzIG9wdGlvbiBpcyB1c2VkIHRvIGlu Y3JlYXNlIHNoYWRvdyBSQU0gd2hlcmUKPiB0aGUgd29ya2xvYWQgZGVtYW5kcyBpdCkuCgpPSywg SSBtdXN0IGFkbWl0IEkgaGF2ZSBubyBpZGVhLCBJIGNvcGllZCB0aGlzIHZhbHVlIGZyb20gYW4g ZXhhbXBsZSBhCmxvbmcgdGltZSBhZ28sIGFuZCBJJ3ZlIGp1c3QgY29waWVkIGl0IGludG8gZWFj aCBuZXcgdm0gYXMgSSBnby4KCkZyb20gaGVyZToKaHR0cDovL3dpa2kucHJnbXIuY29tL21lZGlh d2lraS9pbmRleC5waHAvQ2hhcHRlcl8xMjpfSFZNOl9CZXlvbmRfUGFyYXZpcnR1YWxpemF0aW9u Ckl0IHNheXM6ClRoZSBzaGFkb3dfbWVtb3J5IGRpcmVjdGl2ZSBzcGVjaWZpZXMgdGhlIGFtb3Vu dCBvZiBtZW1vcnkgdG8gdXNlIGZvcgpzaGFkb3cgcGFnZSB0YWJsZXMuIChTaGFkb3cgcGFnZSB0 YWJsZXMsIG9mIGNvdXJzZSwgYXJlIHRoZQphZm9yZW1lbnRpb25lZCBjb3BpZXMgb2YgdGhlIHRh YmxlcyB0aGF0IG1hcCBwcm9jZXNzLXZpcnR1YWwgbWVtb3J5IHRvCnBoeXNpY2FsIG1lbW9yeS4p IFhlbiBhZHZpc2VzIGFsbG9jYXRpbmcgYXQgbGVhc3QgMktCIHBlciBNQiBvZiBkb21haW4KbWVt b3J5LCBhbmQg4oCcYSBmZXfigJ0gTUIgcGVyIHZpcnR1YWwgQ1BVLiBOb3RlIHRoYXQgdGhpcyBt ZW1vcnkgaXMgaW4KYWRkaXRpb24gdG8gdGhlIGRvbVXigJlzIGFsbG9jYXRpb24gc3BlY2lmaWVk IGluIHRoZSBtZW1vcnkgbGluZS4KCkknbSBub3QgcmVhbGx5IHN1cmUgd2hlcmUgdG8gZmluZCBk ZWZpbml0aXZlIGRvY3VtZW50YXRpb24gb24gYWxsIHRoZQpjb25maWcgZmlsZSBvcHRpb25zIHdp dGhpbiB4ZW4uLi4uIEkgd2lsbCByZS1ydW4gdGhlIHRlc3Qgd2l0aApzaGFkb3dfbWVtb3J5ID0g MzYgYW5kIGxldCB5b3Uga25vdy4gV2FzIGdvaW5nIHRvIHJ1biBpdCBub3cgYW5kIGFkdmlzZSwK YnV0IHNvbWUgc2NoZWR1bGVkIHRhc2sgaGFzIHN0YXJ0ZWQsIHNvIHdpbGwgd2FpdCB1bnRpbCBp dCBpcyBmaW5pc2hlZAphbmQgcmUtdGVzdC4KCj4gRG9lcyB5b3VyIHN5c3RlbSBoYXZlIEhBUCAo aGFyZHdhcmUgYXNzaXN0ZWQgcGFnaW5nLCBFUFQgb3IgTlBUIG9uCj4gSW50ZWwvQU1EIHJlc3Bl Y3RpdmVseSk/CgooWEVOKSBIVk06IEFTSURzIGVuYWJsZWQuCihYRU4pIFNWTTogU3VwcG9ydGVk IGFkdmFuY2VkIGZlYXR1cmVzOgooWEVOKSAgLSBOZXN0ZWQgUGFnZSBUYWJsZXMgKE5QVCkKKFhF TikgIC0gTGFzdCBCcmFuY2ggUmVjb3JkIChMQlIpIFZpcnR1YWxpc2F0aW9uCihYRU4pICAtIE5l eHQtUklQIFNhdmVkIG9uICNWTUVYSVQKKFhFTikgIC0gUGF1c2UtSW50ZXJjZXB0IEZpbHRlcgoo WEVOKSBIVk06IFNWTSBlbmFibGVkCihYRU4pIEhWTTogSGFyZHdhcmUgQXNzaXN0ZWQgUGFnaW5n IChIQVApIGRldGVjdGVkCihYRU4pIEhWTTogSEFQIHBhZ2Ugc2l6ZXM6IDRrQiwgMk1CLCAxR0IK CkknbSBndWVzc2luZyB0aGF0IGlzIGEgeWVzIHRvIEhBUCBhbmQgTlBUIGJ1dCBubyBmb3IgRVBU Li4uLgoKVGhpcyBpcyBhIEFNRCBQaGVub20odG0pIElJIFg2IDExMDBUIFByb2Nlc3NvcgoKPj4g ZGV2aWNlX21vZGVsICAgID0gJy91c3IvbGliL3hlbi1kZWZhdWx0L2Jpbi9xZW11LWRtJwo+PiBs b2NhbHRpbWUgICAgPSAxCj4+IG5hbWUgICAgICAgID0gInZtMSIKPj4gY3B1cyAgICAgICAgPSAi MiwzLDQsNSIgICAgIyBXaGljaCBwaHlzaWNhbCBDUFUncyB0byBhbGxvdwo+IAo+IEhhdmUgeW91 IHBpbm5lZCBkb20wIHRvIHVzZSBwQ1BVIDEgYW5kL3AgcENQVXMgPiA2PwoKTm8sIGhvdyBzaG91 bGQgSSBwaW4gZG9tMCB0byBjcHUwID8KCkFsc28sIHhtIHZjcHUtbGlzdCBzaG93cyB0aGlzOgp4 bSB2Y3B1LWxpc3QKTmFtZSAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgSUQgIFZDUFUg ICBDUFUgU3RhdGUgICBUaW1lKHMpIENQVQpBZmZpbml0eQpEb21haW4tMCAgICAgICAgICAgICAg ICAgICAgICAgICAgICAgMCAgICAgMCAgICAgMCAgIHItLSAgIDM0MDkzLjQgYW55IGNwdQpEb21h aW4tMCAgICAgICAgICAgICAgICAgICAgICAgICAgICAgMCAgICAgMSAgICAgNSAgIC1iLSAgICAx MjM5LjMgYW55IGNwdQpEb21haW4tMCAgICAgICAgICAgICAgICAgICAgICAgICAgICAgMCAgICAg MiAgICAgMSAgIC1iLSAgICAxMTM0LjQgYW55IGNwdQpEb21haW4tMCAgICAgICAgICAgICAgICAg ICAgICAgICAgICAgMCAgICAgMyAgICAgMyAgIC1iLSAgICAxMDQ5LjkgYW55IGNwdQpEb21haW4t MCAgICAgICAgICAgICAgICAgICAgICAgICAgICAgMCAgICAgNCAgICAgMCAgIC1iLSAgICAxMzQw LjUgYW55IGNwdQpEb21haW4tMCAgICAgICAgICAgICAgICAgICAgICAgICAgICAgMCAgICAgNSAg ICAgMiAgIC1iLSAgICAxMTIzLjIgYW55IGNwdQp2bTEgICAgICAgICAgICAgICAgICAgICAgICAg ICAgICAgICAgOSAgICAgMCAgICAgMiAgIC1iLSAgICAgIDIwLjUgMi01CnZtMSAgICAgICAgICAg ICAgICAgICAgICAgICAgICAgICAgICA5ICAgICAxICAgICA0ICAgLWItICAgICAgMTUuMiAyLTUK dm0xICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgIDkgICAgIDIgICAgIDMgICAtYi0g ICAgICAxNC45IDItNQp2bTEgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgOSAgICAg MyAgICAgNCAgIC1iLSAgICAgIDE1LjEgMi01CgpJJ3ZlIHNldCB0aGUgdm0gdG8gdXNlIGNwdXMg MiwzLDQsNSBidXQgaG93IGRvIEkgZm9yY2UgaXQgc286CnZjcHUgMCA9IDIKdmNwdSAxID0gMwp2 Y3B1IDIgPSA0CnZjcHUgMyA9IDUKCldpdGhvdXQgcnVubmluZzoKeG0gdmNwdS1waW4gdm0xIDAg Mgp4bSB2Y3B1LXBpbiB2bTEgMSAzCnhtIHZjcHUtcGluIHZtMSAyIDQKeG0gdmNwdS1waW4gdm0x IDMgNQoKPiBIb3cgbWFueSBkb20wIHZjcHVzIGhhdmUgeW91IGNvbmZpZ3VyZWQ/CgpJIGFzc3Vt ZSBieSBkZWZhdWx0IGl0IHRha2VzIGFsbCBvZiB0aGVtLi4uCgo+IERvZXMgeW91ciBzeXN0ZW0g aGF2ZSBhbnkgTlVNQSBwcm9wZXJ0aWVzPwoKSSBkb24ndCByZWFsbHkgdW5kZXJzdGFuZCB0aGlz IHF1ZXN0aW9uLi4uLiBpcyB0aGVyZSBhIHNpbXBsZSBtZXRob2QgdG8KY2hlY2s/IEl0IGlzIGEg QU1EIFBoZW5vbSh0bSkgSUkgWDYgMTEwMFQgUHJvY2Vzc29yIG9uIGEgcmVhc29uYWJsZQpkZXNr dG9wIG1vdGhlcmJvYXJkLCBub3RoaW5nIGZhbmN5Li4uLgoKPiBBbmQgYXMgSmFtZXMgc3VnZ2Vz dHMgaXQgd291bGQgYWxzbyBiZSB1c2VmdWwgdG8gYmVuY2htYXJrIGlTQ1NJIHJ1bm5pbmcKPiBp biBkb20wIGFuZCBwZXJoYXBzIGV2ZW4gcnVubmluZyBvbiB0aGUgc2FtZSBzeXN0ZW0gd2l0aG91 dCBYZW4gKGp1c3QKPiBMaW51eCkgdXNpbmcgdGhlIHNhbWUga2VybmVsLiBJJ20gbm90IHN1cmUg aWYgVk13YXJlIG9mZmVycyBzb21ldGhpbmcKPiBzaW1pbGFyIHdoaWNoIGNvdWxkIGJlIHVzZWQg Zm9yIGNvbXBhcmlzb24uCgpXZWxsLCB0aGF0IGlzIHdoZXJlIHRoaW5ncyBzdGFydCB0byBnZXQg Y29tcGxpY2F0ZWQgcmF0aGVyIHF1aWNrbHkuLi4KVGhlcmUgYXJlIGEgbG90IG9mIGxheWVycyBo ZXJlLCBidXQgSSdkIHByZWZlciB0byBsb29rIGF0IHRoZSBpc3N1ZXMKY2xvc2VyIHRvIHhlbiBm aXJzdCwgc2luY2Ugdm13YXJlIHdhcyB3b3JraW5nIGZyb20gYW4gaWRlbnRpY2FsbHkKY29uZmln dXJlZCBzYW4vZXRjLCBzbyBub3RoaW5nIGF0IGFsbCBoYXMgY2hhbmdlZCB0aGVyZS4gVWx0aW1h dGVseSwgdGhlCnNhbiBpcyB1c2luZyAzIHggU1NEIGluIFJBSUQ1LiBJIGhhdmUgZG9uZSB2YXJp b3VzIHRlc3RpbmcgaW4gdGhlIHBhc3QKZnJvbSBwbGFpbiBsaW51eCAod2l0aCBvbGRlciBrZXJu ZWwgMi42LjMyIGZyb20gZGViaWFuIHN0YWJsZSkgYW5kCmFjaGlldmVkIHJlYXNvbmFibGUgZmln dXJlcyAoSSBkb24ndCByZWNhbGwgZXhhY3RseSkuCgpUaGFuayB5b3UgZm9yIHlvdXIgcmVzcG9u c2VzLCBpZiB0aGVyZSBpcyBhbnkgZnVydGhlciBpbmZvcm1hdGlvbiBJIGNhbgpwcm92aWRlLCBv ciBhZGRpdGlvbmFsIHN1Z2dlc3Rpb25zIHlvdSBhcmUgYWJsZSB0byBtYWtlLCBJJ2QgYmUgcmVh bGx5CmFwcHJlY2lhdGl2ZS4KClJlZ2FyZHMsCkFkYW0KCi0tIApBZGFtIEdvcnlhY2hldgpXZWJz aXRlIE1hbmFnZXJzCnd3dy53ZWJzaXRlbWFuYWdlcnMuY29tLmF1CgpfX19fX19fX19fX19fX19f X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fXwpYZW4tdXNlcnMgbWFpbGluZyBsaXN0Clhl bi11c2Vyc0BsaXN0cy54ZW4ub3JnCmh0dHA6Ly9saXN0cy54ZW4ub3JnL3hlbi11c2Vycw== From xen-users-bounces@lists.xen.org Fri Sep 14 13:12:59 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Fri, 14 Sep 2012 13:12:59 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TCVgO-0003Yv-Lt; Fri, 14 Sep 2012 13:11:44 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TCVgN-0003Yo-39 for xen-users@lists.xen.org; Fri, 14 Sep 2012 13:11:43 +0000 Received: from [85.158.143.35:12485] by server-1.bemta-4.messagelabs.com id 5D/F2-12504-E0D23505; Fri, 14 Sep 2012 13:11:42 +0000 X-Env-Sender: mailinglists@websitemanagers.com.au X-Msg-Ref: server-6.tower-21.messagelabs.com!1347628297!18264403!1 X-Originating-IP: [203.56.191.70] X-SpamReason: No, hits=0.0 required=7.0 tests= X-StarScan-Received: X-StarScan-Version: 6.6.1.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 24200 invoked from network); 14 Sep 2012 13:11:40 -0000 Received: from unknown (HELO hammer.websitemanagers.com.au) (203.56.191.70) by server-6.tower-21.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 14 Sep 2012 13:11:40 -0000 Received: (qmail 5432 invoked by uid 1011); 14 Sep 2012 13:11:06 -0000 Received: from 124.246.8.196 by hammer (envelope-from , uid 1008) with qmail-scanner-1.24 (clamdscan: 0.97.3/15354. spamassassin: 3.3.1. Clear:RC:1(124.246.8.196):. Processed in 0.103502 secs); 14 Sep 2012 13:11:06 -0000 Received: from unknown (HELO ?192.168.2.90?) (124.246.8.196) by 0 with SMTP; 14 Sep 2012 13:11:06 -0000 Message-ID: <50532CE9.5080601@websitemanagers.com.au> Date: Fri, 14 Sep 2012 23:11:05 +1000 From: Adam Goryachev Organization: Website Managers User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:15.0) Gecko/20120827 Thunderbird/15.0 MIME-Version: 1.0 To: Ian Campbell References: <5051D0C5.5070600@websitemanagers.com.au> <1347609879.24226.148.camel@zakaz.uk.xensource.com> In-Reply-To: <1347609879.24226.148.camel@zakaz.uk.xensource.com> Cc: "xen-users@lists.xen.org" Subject: Re: [Xen-users] Poor Windows 2003 + GPLPV performance compared to VMWare X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: base64 Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org T24gMTQvMDkvMTIgMTg6MDQsIElhbiBDYW1wYmVsbCB3cm90ZToKPiBPbiBUaHUsIDIwMTItMDkt MTMgYXQgMTM6MjUgKzAxMDAsIEFkYW0gR29yeWFjaGV2IHdyb3RlOgo+PiBUaGVuLCB0aGUgdXNl ciByYW4gdGhlIGFib3ZlIHByb2Nlc3MsIGFuZCBnb3QgY29uc2lzdGVudGx5LCByZXN1bHRzIG9m Cj4+IGFwcHJveCAyNTAwIHRyYW5zYWN0aW9ucyBwZXIgc2Vjb25kCj4gCj4gQXJlIHlvdSBjZXJ0 YWluIHRoZSBHUExQViBkcml2ZXJzIGhhdmUgdGFrZW4gaG9sZCBhbmQgeW91IGFyZW4ndCB1c2lu Zwo+IGVtdWxhdGVkIGRldmljZXM/CgpXaXRoaW4gV2luZG93cywgRGV2aWNlIE1hbmFnZXIgc2hv d3MgdGhlIERpc2sgRHJpdmVzIGFzICJYRVYgUFYgRElTSwpTQ1NJIERpc2sgRGV2aWNlIiwgdGhp cyBpcyB0aGUgbmV3ZXN0IG9uZSB3aGljaCBpdCBkZXRlY3RlZCBhbmQKaW5zdGFsbGVkIGFmdGVy IEkgY2hhbmdlZCB0aGUgY29uZmlnIGZyb20gaGRhIHRvIHh2ZGEuCgo+IEkgZG9uJ3Qga25vdyBo b3cgeW91IGNhbiB0ZWxsIGZyb20gd2l0aGluIFdpbmRvd3MgYnV0IGZyb20gZG9tMCB5b3UgY2Fu Cj4gbG9vayBpbiB0aGUgb3V0cHV0IG9mICJ4ZW5zdG9yZS1scyAtZnAiIGZvciB0aGUgInN0YXRl IiBub2RlIGFzc29jaWF0ZWQKPiB3aXRoIGVhY2ggZGV2aWNlIGZyb250ZW5kIC0tIHRoZXkgc2hv dWxkIGJlIGluIHN0YXRlIDQgKGNvbm5lY3RlZCkuCgpyb290QHBtMDg6fiMgeGVuc3RvcmUtbHMg LWZwfGdyZXAgc3RhdGV8Z3JlcCB2YmQKL2xvY2FsL2RvbWFpbi8wL2JhY2tlbmQvdmJkLzgvNTE3 MTIvc3RhdGUgPSAiNCIgICAobjAscjgpCi9sb2NhbC9kb21haW4vOC9kZXZpY2UvdmJkLzUxNzEy L3N0YXRlID0gIjQiICAgKG44LHIwKQoKSSBhc3N1bWUgZG9tIGlkIDggaXMgdGhlIFZNLCBhbmQg ZG9tMCBpcyB0aGUgZmlyc3QgbGluZSBhYm92ZS4KCj4gWy4uLl0KPj4gbWVtb3J5ICAgICAgICA9 IDQwOTYKPj4gc2hhZG93X21lbW9yeSAgICA9IDEyCj4gCj4gVGhpcyBzZWVtcyBsb3cgdG8gbWUu IFRoZSBkZWZhdWx0IGlzIDFNIHBlciBDUFUsIHBsdXMgOEsgcGVyIE0gb2YgUkFNLAo+IHdoaWNo IGlzIDRNICsgOCo0MDk2SyA9IDRNKzMyTSA9IDM2TS4gRG8geW91IGhhdmUgYW55IHJlYXNvbiB0 byBzZWNvbmQKPiBndWVzcyB0aGlzPyAoVXN1YWxseSB0aGlzIG9wdGlvbiBpcyB1c2VkIHRvIGlu Y3JlYXNlIHNoYWRvdyBSQU0gd2hlcmUKPiB0aGUgd29ya2xvYWQgZGVtYW5kcyBpdCkuCgpPSywg SSBtdXN0IGFkbWl0IEkgaGF2ZSBubyBpZGVhLCBJIGNvcGllZCB0aGlzIHZhbHVlIGZyb20gYW4g ZXhhbXBsZSBhCmxvbmcgdGltZSBhZ28sIGFuZCBJJ3ZlIGp1c3QgY29waWVkIGl0IGludG8gZWFj aCBuZXcgdm0gYXMgSSBnby4KCkZyb20gaGVyZToKaHR0cDovL3dpa2kucHJnbXIuY29tL21lZGlh d2lraS9pbmRleC5waHAvQ2hhcHRlcl8xMjpfSFZNOl9CZXlvbmRfUGFyYXZpcnR1YWxpemF0aW9u Ckl0IHNheXM6ClRoZSBzaGFkb3dfbWVtb3J5IGRpcmVjdGl2ZSBzcGVjaWZpZXMgdGhlIGFtb3Vu dCBvZiBtZW1vcnkgdG8gdXNlIGZvcgpzaGFkb3cgcGFnZSB0YWJsZXMuIChTaGFkb3cgcGFnZSB0 YWJsZXMsIG9mIGNvdXJzZSwgYXJlIHRoZQphZm9yZW1lbnRpb25lZCBjb3BpZXMgb2YgdGhlIHRh YmxlcyB0aGF0IG1hcCBwcm9jZXNzLXZpcnR1YWwgbWVtb3J5IHRvCnBoeXNpY2FsIG1lbW9yeS4p IFhlbiBhZHZpc2VzIGFsbG9jYXRpbmcgYXQgbGVhc3QgMktCIHBlciBNQiBvZiBkb21haW4KbWVt b3J5LCBhbmQg4oCcYSBmZXfigJ0gTUIgcGVyIHZpcnR1YWwgQ1BVLiBOb3RlIHRoYXQgdGhpcyBt ZW1vcnkgaXMgaW4KYWRkaXRpb24gdG8gdGhlIGRvbVXigJlzIGFsbG9jYXRpb24gc3BlY2lmaWVk IGluIHRoZSBtZW1vcnkgbGluZS4KCkknbSBub3QgcmVhbGx5IHN1cmUgd2hlcmUgdG8gZmluZCBk ZWZpbml0aXZlIGRvY3VtZW50YXRpb24gb24gYWxsIHRoZQpjb25maWcgZmlsZSBvcHRpb25zIHdp dGhpbiB4ZW4uLi4uIEkgd2lsbCByZS1ydW4gdGhlIHRlc3Qgd2l0aApzaGFkb3dfbWVtb3J5ID0g MzYgYW5kIGxldCB5b3Uga25vdy4gV2FzIGdvaW5nIHRvIHJ1biBpdCBub3cgYW5kIGFkdmlzZSwK YnV0IHNvbWUgc2NoZWR1bGVkIHRhc2sgaGFzIHN0YXJ0ZWQsIHNvIHdpbGwgd2FpdCB1bnRpbCBp dCBpcyBmaW5pc2hlZAphbmQgcmUtdGVzdC4KCj4gRG9lcyB5b3VyIHN5c3RlbSBoYXZlIEhBUCAo aGFyZHdhcmUgYXNzaXN0ZWQgcGFnaW5nLCBFUFQgb3IgTlBUIG9uCj4gSW50ZWwvQU1EIHJlc3Bl Y3RpdmVseSk/CgooWEVOKSBIVk06IEFTSURzIGVuYWJsZWQuCihYRU4pIFNWTTogU3VwcG9ydGVk IGFkdmFuY2VkIGZlYXR1cmVzOgooWEVOKSAgLSBOZXN0ZWQgUGFnZSBUYWJsZXMgKE5QVCkKKFhF TikgIC0gTGFzdCBCcmFuY2ggUmVjb3JkIChMQlIpIFZpcnR1YWxpc2F0aW9uCihYRU4pICAtIE5l eHQtUklQIFNhdmVkIG9uICNWTUVYSVQKKFhFTikgIC0gUGF1c2UtSW50ZXJjZXB0IEZpbHRlcgoo WEVOKSBIVk06IFNWTSBlbmFibGVkCihYRU4pIEhWTTogSGFyZHdhcmUgQXNzaXN0ZWQgUGFnaW5n IChIQVApIGRldGVjdGVkCihYRU4pIEhWTTogSEFQIHBhZ2Ugc2l6ZXM6IDRrQiwgMk1CLCAxR0IK CkknbSBndWVzc2luZyB0aGF0IGlzIGEgeWVzIHRvIEhBUCBhbmQgTlBUIGJ1dCBubyBmb3IgRVBU Li4uLgoKVGhpcyBpcyBhIEFNRCBQaGVub20odG0pIElJIFg2IDExMDBUIFByb2Nlc3NvcgoKPj4g ZGV2aWNlX21vZGVsICAgID0gJy91c3IvbGliL3hlbi1kZWZhdWx0L2Jpbi9xZW11LWRtJwo+PiBs b2NhbHRpbWUgICAgPSAxCj4+IG5hbWUgICAgICAgID0gInZtMSIKPj4gY3B1cyAgICAgICAgPSAi MiwzLDQsNSIgICAgIyBXaGljaCBwaHlzaWNhbCBDUFUncyB0byBhbGxvdwo+IAo+IEhhdmUgeW91 IHBpbm5lZCBkb20wIHRvIHVzZSBwQ1BVIDEgYW5kL3AgcENQVXMgPiA2PwoKTm8sIGhvdyBzaG91 bGQgSSBwaW4gZG9tMCB0byBjcHUwID8KCkFsc28sIHhtIHZjcHUtbGlzdCBzaG93cyB0aGlzOgp4 bSB2Y3B1LWxpc3QKTmFtZSAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgSUQgIFZDUFUg ICBDUFUgU3RhdGUgICBUaW1lKHMpIENQVQpBZmZpbml0eQpEb21haW4tMCAgICAgICAgICAgICAg ICAgICAgICAgICAgICAgMCAgICAgMCAgICAgMCAgIHItLSAgIDM0MDkzLjQgYW55IGNwdQpEb21h aW4tMCAgICAgICAgICAgICAgICAgICAgICAgICAgICAgMCAgICAgMSAgICAgNSAgIC1iLSAgICAx MjM5LjMgYW55IGNwdQpEb21haW4tMCAgICAgICAgICAgICAgICAgICAgICAgICAgICAgMCAgICAg MiAgICAgMSAgIC1iLSAgICAxMTM0LjQgYW55IGNwdQpEb21haW4tMCAgICAgICAgICAgICAgICAg ICAgICAgICAgICAgMCAgICAgMyAgICAgMyAgIC1iLSAgICAxMDQ5LjkgYW55IGNwdQpEb21haW4t MCAgICAgICAgICAgICAgICAgICAgICAgICAgICAgMCAgICAgNCAgICAgMCAgIC1iLSAgICAxMzQw LjUgYW55IGNwdQpEb21haW4tMCAgICAgICAgICAgICAgICAgICAgICAgICAgICAgMCAgICAgNSAg ICAgMiAgIC1iLSAgICAxMTIzLjIgYW55IGNwdQp2bTEgICAgICAgICAgICAgICAgICAgICAgICAg ICAgICAgICAgOSAgICAgMCAgICAgMiAgIC1iLSAgICAgIDIwLjUgMi01CnZtMSAgICAgICAgICAg ICAgICAgICAgICAgICAgICAgICAgICA5ICAgICAxICAgICA0ICAgLWItICAgICAgMTUuMiAyLTUK dm0xICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgIDkgICAgIDIgICAgIDMgICAtYi0g ICAgICAxNC45IDItNQp2bTEgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgOSAgICAg MyAgICAgNCAgIC1iLSAgICAgIDE1LjEgMi01CgpJJ3ZlIHNldCB0aGUgdm0gdG8gdXNlIGNwdXMg MiwzLDQsNSBidXQgaG93IGRvIEkgZm9yY2UgaXQgc286CnZjcHUgMCA9IDIKdmNwdSAxID0gMwp2 Y3B1IDIgPSA0CnZjcHUgMyA9IDUKCldpdGhvdXQgcnVubmluZzoKeG0gdmNwdS1waW4gdm0xIDAg Mgp4bSB2Y3B1LXBpbiB2bTEgMSAzCnhtIHZjcHUtcGluIHZtMSAyIDQKeG0gdmNwdS1waW4gdm0x IDMgNQoKPiBIb3cgbWFueSBkb20wIHZjcHVzIGhhdmUgeW91IGNvbmZpZ3VyZWQ/CgpJIGFzc3Vt ZSBieSBkZWZhdWx0IGl0IHRha2VzIGFsbCBvZiB0aGVtLi4uCgo+IERvZXMgeW91ciBzeXN0ZW0g aGF2ZSBhbnkgTlVNQSBwcm9wZXJ0aWVzPwoKSSBkb24ndCByZWFsbHkgdW5kZXJzdGFuZCB0aGlz IHF1ZXN0aW9uLi4uLiBpcyB0aGVyZSBhIHNpbXBsZSBtZXRob2QgdG8KY2hlY2s/IEl0IGlzIGEg QU1EIFBoZW5vbSh0bSkgSUkgWDYgMTEwMFQgUHJvY2Vzc29yIG9uIGEgcmVhc29uYWJsZQpkZXNr dG9wIG1vdGhlcmJvYXJkLCBub3RoaW5nIGZhbmN5Li4uLgoKPiBBbmQgYXMgSmFtZXMgc3VnZ2Vz dHMgaXQgd291bGQgYWxzbyBiZSB1c2VmdWwgdG8gYmVuY2htYXJrIGlTQ1NJIHJ1bm5pbmcKPiBp biBkb20wIGFuZCBwZXJoYXBzIGV2ZW4gcnVubmluZyBvbiB0aGUgc2FtZSBzeXN0ZW0gd2l0aG91 dCBYZW4gKGp1c3QKPiBMaW51eCkgdXNpbmcgdGhlIHNhbWUga2VybmVsLiBJJ20gbm90IHN1cmUg aWYgVk13YXJlIG9mZmVycyBzb21ldGhpbmcKPiBzaW1pbGFyIHdoaWNoIGNvdWxkIGJlIHVzZWQg Zm9yIGNvbXBhcmlzb24uCgpXZWxsLCB0aGF0IGlzIHdoZXJlIHRoaW5ncyBzdGFydCB0byBnZXQg Y29tcGxpY2F0ZWQgcmF0aGVyIHF1aWNrbHkuLi4KVGhlcmUgYXJlIGEgbG90IG9mIGxheWVycyBo ZXJlLCBidXQgSSdkIHByZWZlciB0byBsb29rIGF0IHRoZSBpc3N1ZXMKY2xvc2VyIHRvIHhlbiBm aXJzdCwgc2luY2Ugdm13YXJlIHdhcyB3b3JraW5nIGZyb20gYW4gaWRlbnRpY2FsbHkKY29uZmln dXJlZCBzYW4vZXRjLCBzbyBub3RoaW5nIGF0IGFsbCBoYXMgY2hhbmdlZCB0aGVyZS4gVWx0aW1h dGVseSwgdGhlCnNhbiBpcyB1c2luZyAzIHggU1NEIGluIFJBSUQ1LiBJIGhhdmUgZG9uZSB2YXJp b3VzIHRlc3RpbmcgaW4gdGhlIHBhc3QKZnJvbSBwbGFpbiBsaW51eCAod2l0aCBvbGRlciBrZXJu ZWwgMi42LjMyIGZyb20gZGViaWFuIHN0YWJsZSkgYW5kCmFjaGlldmVkIHJlYXNvbmFibGUgZmln dXJlcyAoSSBkb24ndCByZWNhbGwgZXhhY3RseSkuCgpUaGFuayB5b3UgZm9yIHlvdXIgcmVzcG9u c2VzLCBpZiB0aGVyZSBpcyBhbnkgZnVydGhlciBpbmZvcm1hdGlvbiBJIGNhbgpwcm92aWRlLCBv ciBhZGRpdGlvbmFsIHN1Z2dlc3Rpb25zIHlvdSBhcmUgYWJsZSB0byBtYWtlLCBJJ2QgYmUgcmVh bGx5CmFwcHJlY2lhdGl2ZS4KClJlZ2FyZHMsCkFkYW0KCi0tIApBZGFtIEdvcnlhY2hldgpXZWJz aXRlIE1hbmFnZXJzCnd3dy53ZWJzaXRlbWFuYWdlcnMuY29tLmF1CgpfX19fX19fX19fX19fX19f X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fXwpYZW4tdXNlcnMgbWFpbGluZyBsaXN0Clhl bi11c2Vyc0BsaXN0cy54ZW4ub3JnCmh0dHA6Ly9saXN0cy54ZW4ub3JnL3hlbi11c2Vycw== From xen-users-bounces@lists.xen.org Fri Sep 14 13:32:10 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Fri, 14 Sep 2012 13:32:10 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TCVyy-0005P2-Ub; Fri, 14 Sep 2012 13:30:56 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TCVyw-0005Op-Iq for xen-users@lists.xen.org; Fri, 14 Sep 2012 13:30:55 +0000 Received: from [85.158.138.51:53805] by server-8.bemta-3.messagelabs.com id 54/62-24700-D8133505; Fri, 14 Sep 2012 13:30:53 +0000 X-Env-Sender: Ian.Campbell@citrix.com X-Msg-Ref: server-2.tower-174.messagelabs.com!1347629452!30545822!1 X-Originating-IP: [62.200.22.115] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogNjIuMjAwLjIyLjExNSA9PiAxMDkyOTU=\n X-StarScan-Received: X-StarScan-Version: 6.6.1.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 24604 invoked from network); 14 Sep 2012 13:30:52 -0000 Received: from smtp.eu.citrix.com (HELO SMTP.EU.CITRIX.COM) (62.200.22.115) by server-2.tower-174.messagelabs.com with RC4-SHA encrypted SMTP; 14 Sep 2012 13:30:52 -0000 X-IronPort-AV: E=Sophos;i="4.80,423,1344211200"; d="scan'208";a="14547418" Received: from lonpmailmx01.citrite.net ([10.30.203.162]) by LONPIPO01.EU.CITRIX.COM with ESMTP/TLS/RC4-MD5; 14 Sep 2012 13:30:17 +0000 Received: from [10.80.2.42] (10.80.2.42) by LONPMAILMX01.citrite.net (10.30.203.162) with Microsoft SMTP Server id 8.3.279.1; Fri, 14 Sep 2012 14:30:17 +0100 Message-ID: <1347629416.24226.208.camel@zakaz.uk.xensource.com> From: Ian Campbell To: Adam Goryachev Date: Fri, 14 Sep 2012 14:30:16 +0100 In-Reply-To: <50532CE9.5080601@websitemanagers.com.au> References: <5051D0C5.5070600@websitemanagers.com.au> <1347609879.24226.148.camel@zakaz.uk.xensource.com> <50532CE9.5080601@websitemanagers.com.au> Organization: Citrix Systems, Inc. X-Mailer: Evolution 3.4.3-1 MIME-Version: 1.0 Cc: "xen-users@lists.xen.org" Subject: Re: [Xen-users] Poor Windows 2003 + GPLPV performance compared to VMWare X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: base64 Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org T24gRnJpLCAyMDEyLTA5LTE0IGF0IDE0OjExICswMTAwLCBBZGFtIEdvcnlhY2hldiB3cm90ZToK PiBPbiAxNC8wOS8xMiAxODowNCwgSWFuIENhbXBiZWxsIHdyb3RlOgo+ID4gT24gVGh1LCAyMDEy LTA5LTEzIGF0IDEzOjI1ICswMTAwLCBBZGFtIEdvcnlhY2hldiB3cm90ZToKPiA+PiBUaGVuLCB0 aGUgdXNlciByYW4gdGhlIGFib3ZlIHByb2Nlc3MsIGFuZCBnb3QgY29uc2lzdGVudGx5LCByZXN1 bHRzIG9mCj4gPj4gYXBwcm94IDI1MDAgdHJhbnNhY3Rpb25zIHBlciBzZWNvbmQKPiA+IAo+ID4g QXJlIHlvdSBjZXJ0YWluIHRoZSBHUExQViBkcml2ZXJzIGhhdmUgdGFrZW4gaG9sZCBhbmQgeW91 IGFyZW4ndCB1c2luZwo+ID4gZW11bGF0ZWQgZGV2aWNlcz8KPiAKPiBXaXRoaW4gV2luZG93cywg RGV2aWNlIE1hbmFnZXIgc2hvd3MgdGhlIERpc2sgRHJpdmVzIGFzICJYRVYgUFYgRElTSwo+IFND U0kgRGlzayBEZXZpY2UiLCB0aGlzIGlzIHRoZSBuZXdlc3Qgb25lIHdoaWNoIGl0IGRldGVjdGVk IGFuZAo+IGluc3RhbGxlZCBhZnRlciBJIGNoYW5nZWQgdGhlIGNvbmZpZyBmcm9tIGhkYSB0byB4 dmRhLgo+IAo+ID4gSSBkb24ndCBrbm93IGhvdyB5b3UgY2FuIHRlbGwgZnJvbSB3aXRoaW4gV2lu ZG93cyBidXQgZnJvbSBkb20wIHlvdSBjYW4KPiA+IGxvb2sgaW4gdGhlIG91dHB1dCBvZiAieGVu c3RvcmUtbHMgLWZwIiBmb3IgdGhlICJzdGF0ZSIgbm9kZSBhc3NvY2lhdGVkCj4gPiB3aXRoIGVh Y2ggZGV2aWNlIGZyb250ZW5kIC0tIHRoZXkgc2hvdWxkIGJlIGluIHN0YXRlIDQgKGNvbm5lY3Rl ZCkuCj4gCj4gcm9vdEBwbTA4On4jIHhlbnN0b3JlLWxzIC1mcHxncmVwIHN0YXRlfGdyZXAgdmJk Cj4gL2xvY2FsL2RvbWFpbi8wL2JhY2tlbmQvdmJkLzgvNTE3MTIvc3RhdGUgPSAiNCIgICAobjAs cjgpCj4gL2xvY2FsL2RvbWFpbi84L2RldmljZS92YmQvNTE3MTIvc3RhdGUgPSAiNCIgICAobjgs cjApCj4gCj4gSSBhc3N1bWUgZG9tIGlkIDggaXMgdGhlIFZNLCBhbmQgZG9tMCBpcyB0aGUgZmly c3QgbGluZSBhYm92ZS4KPiAKPiA+IFsuLi5dCj4gPj4gbWVtb3J5ICAgICAgICA9IDQwOTYKPiA+ PiBzaGFkb3dfbWVtb3J5ICAgID0gMTIKPiA+IAo+ID4gVGhpcyBzZWVtcyBsb3cgdG8gbWUuIFRo ZSBkZWZhdWx0IGlzIDFNIHBlciBDUFUsIHBsdXMgOEsgcGVyIE0gb2YgUkFNLAo+ID4gd2hpY2gg aXMgNE0gKyA4KjQwOTZLID0gNE0rMzJNID0gMzZNLiBEbyB5b3UgaGF2ZSBhbnkgcmVhc29uIHRv IHNlY29uZAo+ID4gZ3Vlc3MgdGhpcz8gKFVzdWFsbHkgdGhpcyBvcHRpb24gaXMgdXNlZCB0byBp bmNyZWFzZSBzaGFkb3cgUkFNIHdoZXJlCj4gPiB0aGUgd29ya2xvYWQgZGVtYW5kcyBpdCkuCj4g Cj4gT0ssIEkgbXVzdCBhZG1pdCBJIGhhdmUgbm8gaWRlYSwgSSBjb3BpZWQgdGhpcyB2YWx1ZSBm cm9tIGFuIGV4YW1wbGUgYQo+IGxvbmcgdGltZSBhZ28sIGFuZCBJJ3ZlIGp1c3QgY29waWVkIGl0 IGludG8gZWFjaCBuZXcgdm0gYXMgSSBnby4KPiAKPiBGcm9tIGhlcmU6Cj4gaHR0cDovL3dpa2ku cHJnbXIuY29tL21lZGlhd2lraS9pbmRleC5waHAvQ2hhcHRlcl8xMjpfSFZNOl9CZXlvbmRfUGFy YXZpcnR1YWxpemF0aW9uCj4gSXQgc2F5czoKPiBUaGUgc2hhZG93X21lbW9yeSBkaXJlY3RpdmUg c3BlY2lmaWVzIHRoZSBhbW91bnQgb2YgbWVtb3J5IHRvIHVzZSBmb3IKPiBzaGFkb3cgcGFnZSB0 YWJsZXMuIChTaGFkb3cgcGFnZSB0YWJsZXMsIG9mIGNvdXJzZSwgYXJlIHRoZQo+IGFmb3JlbWVu dGlvbmVkIGNvcGllcyBvZiB0aGUgdGFibGVzIHRoYXQgbWFwIHByb2Nlc3MtdmlydHVhbCBtZW1v cnkgdG8KPiBwaHlzaWNhbCBtZW1vcnkuKSBYZW4gYWR2aXNlcyBhbGxvY2F0aW5nIGF0IGxlYXN0 IDJLQiBwZXIgTUIgb2YgZG9tYWluCj4gbWVtb3J5LCBhbmQg4oCcYSBmZXfigJ0gTUIgcGVyIHZp cnR1YWwgQ1BVLiBOb3RlIHRoYXQgdGhpcyBtZW1vcnkgaXMgaW4KPiBhZGRpdGlvbiB0byB0aGUg ZG9tVeKAmXMgYWxsb2NhdGlvbiBzcGVjaWZpZWQgaW4gdGhlIG1lbW9yeSBsaW5lLgo+IAo+IEkn bSBub3QgcmVhbGx5IHN1cmUgd2hlcmUgdG8gZmluZCBkZWZpbml0aXZlIGRvY3VtZW50YXRpb24g b24gYWxsIHRoZQo+IGNvbmZpZyBmaWxlIG9wdGlvbnMgd2l0aGluIHhlbi4uLi4KCmh0dHA6Ly94 ZW5iaXRzLnhlbi5vcmcvZG9jcy80LjItdGVzdGluZy8gaGFzIG1hbiBwYWdlcyBmb3IgdGhlIGNv bmZpZwpmaWxlcy4gVGhlc2UgYXJlIGFsc28gaW5zdGFsbGVkIG9uIHRoZSBob3N0IGFzIHBhcnQg b2YgdGhlIGJ1aWxkLgoKSWYgeW91IGFyZSB1c2luZyB4ZW5kIHRoZW4gdGhlIHhtIG9uZXMgYXJl IGEgYml0IGxhY2tpbmcuIEhvd2V2ZXIgeGwgaXMKbW9zdGx5IGNvbXBhdGlibGUgd2l0aCB4bSBz byB0aGUgeGwgbWFucGFnZXMgbGFyZ2VseSBhcHBseS4gVGhlcmUncyBhbHNvCmEgYnVuY2ggb2Yg c3R1ZmYgb24gaHR0cDovL3dpa2kueGVuLm9yZy93aWtpLgoKPiAoWEVOKSBIVk06IEFTSURzIGVu YWJsZWQuCj4gKFhFTikgU1ZNOiBTdXBwb3J0ZWQgYWR2YW5jZWQgZmVhdHVyZXM6Cj4gKFhFTikg IC0gTmVzdGVkIFBhZ2UgVGFibGVzIChOUFQpCj4gKFhFTikgIC0gTGFzdCBCcmFuY2ggUmVjb3Jk IChMQlIpIFZpcnR1YWxpc2F0aW9uCj4gKFhFTikgIC0gTmV4dC1SSVAgU2F2ZWQgb24gI1ZNRVhJ VAo+IChYRU4pICAtIFBhdXNlLUludGVyY2VwdCBGaWx0ZXIKPiAoWEVOKSBIVk06IFNWTSBlbmFi bGVkCj4gKFhFTikgSFZNOiBIYXJkd2FyZSBBc3Npc3RlZCBQYWdpbmcgKEhBUCkgZGV0ZWN0ZWQK PiAoWEVOKSBIVk06IEhBUCBwYWdlIHNpemVzOiA0a0IsIDJNQiwgMUdCCj4gCj4gSSdtIGd1ZXNz aW5nIHRoYXQgaXMgYSB5ZXMgdG8gSEFQIGFuZCBOUFQgYnV0IG5vIGZvciBFUFQuLi4uCj4gCj4g VGhpcyBpcyBhIEFNRCBQaGVub20odG0pIElJIFg2IDExMDBUIFByb2Nlc3NvcgoKRVBUIGlzIHRo ZSBJbnRlbCBlcXVpdmFsZW50IG9mIE5QVCBzbyB5b3Ugd291bGRuJ3QgaGF2ZSB0aGF0IG9uZS4K Cj4gPj4gZGV2aWNlX21vZGVsICAgID0gJy91c3IvbGliL3hlbi1kZWZhdWx0L2Jpbi9xZW11LWRt Jwo+ID4+IGxvY2FsdGltZSAgICA9IDEKPiA+PiBuYW1lICAgICAgICA9ICJ2bTEiCj4gPj4gY3B1 cyAgICAgICAgPSAiMiwzLDQsNSIgICAgIyBXaGljaCBwaHlzaWNhbCBDUFUncyB0byBhbGxvdwo+ ID4gCj4gPiBIYXZlIHlvdSBwaW5uZWQgZG9tMCB0byB1c2UgcENQVSAxIGFuZC9wIHBDUFVzID4g Nj8KPiAKPiBObywgaG93IHNob3VsZCBJIHBpbiBkb20wIHRvIGNwdTAgPwoKZG9tMF92Y3B1c19w aW4gYXMgZGVzY3JpYmVkIGluCmh0dHA6Ly94ZW5iaXRzLnhlbi5vcmcvZG9jcy80LjItdGVzdGlu Zy9taXNjL3hlbi1jb21tYW5kLWxpbmUuaHRtbAoKPiBBbHNvLCB4bSB2Y3B1LWxpc3Qgc2hvd3Mg dGhpczoKPiB4bSB2Y3B1LWxpc3QKPiBOYW1lICAgICAgICAgICAgICAgICAgICAgICAgICAgICAg ICBJRCAgVkNQVSAgIENQVSBTdGF0ZSAgIFRpbWUocykgQ1BVCj4gQWZmaW5pdHkKPiBEb21haW4t MCAgICAgICAgICAgICAgICAgICAgICAgICAgICAgMCAgICAgMCAgICAgMCAgIHItLSAgIDM0MDkz LjQgYW55IGNwdQo+IERvbWFpbi0wICAgICAgICAgICAgICAgICAgICAgICAgICAgICAwICAgICAx ICAgICA1ICAgLWItICAgIDEyMzkuMyBhbnkgY3B1Cj4gRG9tYWluLTAgICAgICAgICAgICAgICAg ICAgICAgICAgICAgIDAgICAgIDIgICAgIDEgICAtYi0gICAgMTEzNC40IGFueSBjcHUKPiBEb21h aW4tMCAgICAgICAgICAgICAgICAgICAgICAgICAgICAgMCAgICAgMyAgICAgMyAgIC1iLSAgICAx MDQ5LjkgYW55IGNwdQo+IERvbWFpbi0wICAgICAgICAgICAgICAgICAgICAgICAgICAgICAwICAg ICA0ICAgICAwICAgLWItICAgIDEzNDAuNSBhbnkgY3B1Cj4gRG9tYWluLTAgICAgICAgICAgICAg ICAgICAgICAgICAgICAgIDAgICAgIDUgICAgIDIgICAtYi0gICAgMTEyMy4yIGFueSBjcHUKPiB2 bTEgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgOSAgICAgMCAgICAgMiAgIC1iLSAg ICAgIDIwLjUgMi01Cj4gdm0xICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgIDkgICAg IDEgICAgIDQgICAtYi0gICAgICAxNS4yIDItNQo+IHZtMSAgICAgICAgICAgICAgICAgICAgICAg ICAgICAgICAgICA5ICAgICAyICAgICAzICAgLWItICAgICAgMTQuOSAyLTUKPiB2bTEgICAgICAg ICAgICAgICAgICAgICAgICAgICAgICAgICAgOSAgICAgMyAgICAgNCAgIC1iLSAgICAgIDE1LjEg Mi01Cj4gCj4gSSd2ZSBzZXQgdGhlIHZtIHRvIHVzZSBjcHVzIDIsMyw0LDUgYnV0IGhvdyBkbyBJ IGZvcmNlIGl0IHNvOgo+IHZjcHUgMCA9IDIKPiB2Y3B1IDEgPSAzCj4gdmNwdSAyID0gNAo+IHZj cHUgMyA9IDUKPiAKPiBXaXRob3V0IHJ1bm5pbmc6Cj4geG0gdmNwdS1waW4gdm0xIDAgMgo+IHht IHZjcHUtcGluIHZtMSAxIDMKPiB4bSB2Y3B1LXBpbiB2bTEgMiA0Cj4geG0gdmNwdS1waW4gdm0x IDMgNQoKWW91IGhhdmU6CiAgICAgICAgY3B1cyA9ICIyLDMsNCw1Igp3aGljaCBtZWFucyAibGV0 IGFsbCB0aGUgZ3Vlc3RzIFZDUFVzIHJ1biBvbiBhbnkgb2YgUENQVVMgMi01Ii4KCkl0IHNvdW5k cyBsaWtlIHdoYXQgeW91IGFyZSBhc2tpbmcgZm9yIGFib3ZlIGlzOgogICAgICAgIGNwdXMgPSBb MiwzLDQsNV0KV2hpY2ggZm9yY2VzIGd1ZXN0IHZjcHUwPT5wY3B1PTIsIDE9PjMsIDI9PjQgYW5k IDM9PjUuCgpTdWJ0bGUgSSBhZ3JlZS4KCkRvIHlvdSBoYXZlIGEgc3BlY2lmaWMgcmVhc29uIGZv ciBwaW5uaW5nPyBJJ2QgYmUgdGVtcHRlZCB0byBqdXN0IGxldAp0aGUgc2NoZWR1bGVyIGRvIGl0 cyB0aGluZyB1bmxlc3MvdW50aWwgeW91IGRldGVybWluZSB0aGF0IGl0IGlzIGNhdXNpbmcKcHJv YmxlbXMuCgo+ID4gSG93IG1hbnkgZG9tMCB2Y3B1cyBoYXZlIHlvdSBjb25maWd1cmVkPwo+IAo+ IEkgYXNzdW1lIGJ5IGRlZmF1bHQgaXQgdGFrZXMgYWxsIG9mIHRoZW0uLi4KCkNvcnJlY3QuIGRv bTBfbWF4X3ZjcHVzIHdpbGwgYWRqdXN0IHRoaXMgZm9yIHlvdS4KCj4gPiBEb2VzIHlvdXIgc3lz dGVtIGhhdmUgYW55IE5VTUEgcHJvcGVydGllcz8KPiAKPiBJIGRvbid0IHJlYWxseSB1bmRlcnN0 YW5kIHRoaXMgcXVlc3Rpb24uLi4uIGlzIHRoZXJlIGEgc2ltcGxlIG1ldGhvZCB0bwo+IGNoZWNr PyBJdCBpcyBhIEFNRCBQaGVub20odG0pIElJIFg2IDExMDBUIFByb2Nlc3NvciBvbiBhIHJlYXNv bmFibGUKPiBkZXNrdG9wIG1vdGhlcmJvYXJkLCBub3RoaW5nIGZhbmN5Li4uLgo+IAo+ID4gQW5k IGFzIEphbWVzIHN1Z2dlc3RzIGl0IHdvdWxkIGFsc28gYmUgdXNlZnVsIHRvIGJlbmNobWFyayBp U0NTSSBydW5uaW5nCj4gPiBpbiBkb20wIGFuZCBwZXJoYXBzIGV2ZW4gcnVubmluZyBvbiB0aGUg c2FtZSBzeXN0ZW0gd2l0aG91dCBYZW4gKGp1c3QKPiA+IExpbnV4KSB1c2luZyB0aGUgc2FtZSBr ZXJuZWwuIEknbSBub3Qgc3VyZSBpZiBWTXdhcmUgb2ZmZXJzIHNvbWV0aGluZwo+ID4gc2ltaWxh ciB3aGljaCBjb3VsZCBiZSB1c2VkIGZvciBjb21wYXJpc29uLgo+IAo+IFdlbGwsIHRoYXQgaXMg d2hlcmUgdGhpbmdzIHN0YXJ0IHRvIGdldCBjb21wbGljYXRlZCByYXRoZXIgcXVpY2tseS4uLgo+ IFRoZXJlIGFyZSBhIGxvdCBvZiBsYXllcnMgaGVyZSwgYnV0IEknZCBwcmVmZXIgdG8gbG9vayBh dCB0aGUgaXNzdWVzCj4gY2xvc2VyIHRvIHhlbiBmaXJzdCwgc2luY2Ugdm13YXJlIHdhcyB3b3Jr aW5nIGZyb20gYW4gaWRlbnRpY2FsbHkKPiBjb25maWd1cmVkIHNhbi9ldGMsIHNvIG5vdGhpbmcg YXQgYWxsIGhhcyBjaGFuZ2VkIHRoZXJlLiBVbHRpbWF0ZWx5LCB0aGUKPiBzYW4gaXMgdXNpbmcg MyB4IFNTRCBpbiBSQUlENS4gSSBoYXZlIGRvbmUgdmFyaW91cyB0ZXN0aW5nIGluIHRoZSBwYXN0 Cj4gZnJvbSBwbGFpbiBsaW51eCAod2l0aCBvbGRlciBrZXJuZWwgMi42LjMyIGZyb20gZGViaWFu IHN0YWJsZSkgYW5kCj4gYWNoaWV2ZWQgcmVhc29uYWJsZSBmaWd1cmVzIChJIGRvbid0IHJlY2Fs bCBleGFjdGx5KS4KCkkgd2FzIHdvcnJpZWQgYWJvdXQgdGhlIExpbnV4IHNpZGUgcmF0aGVyIHRo YW4gdGhlIFNBTiBpdHNlbGYsIGJ1dCBpdApzb3VuZHMgbGlrZSB5b3UndmUgZ290IHRoYXQgY292 ZXJlZC4KCj4gVGhhbmsgeW91IGZvciB5b3VyIHJlc3BvbnNlcywgaWYgdGhlcmUgaXMgYW55IGZ1 cnRoZXIgaW5mb3JtYXRpb24gSSBjYW4KPiBwcm92aWRlLCBvciBhZGRpdGlvbmFsIHN1Z2dlc3Rp b25zIHlvdSBhcmUgYWJsZSB0byBtYWtlLCBJJ2QgYmUgcmVhbGx5Cj4gYXBwcmVjaWF0aXZlLgo+ IAo+IFJlZ2FyZHMsCj4gQWRhbQo+IAoKCgpfX19fX19fX19fX19fX19fX19fX19fX19fX19fX19f X19fX19fX19fX19fX19fXwpYZW4tdXNlcnMgbWFpbGluZyBsaXN0Clhlbi11c2Vyc0BsaXN0cy54 ZW4ub3JnCmh0dHA6Ly9saXN0cy54ZW4ub3JnL3hlbi11c2Vycw== From xen-users-bounces@lists.xen.org Fri Sep 14 13:32:10 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Fri, 14 Sep 2012 13:32:10 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TCVyy-0005P2-Ub; Fri, 14 Sep 2012 13:30:56 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TCVyw-0005Op-Iq for xen-users@lists.xen.org; Fri, 14 Sep 2012 13:30:55 +0000 Received: from [85.158.138.51:53805] by server-8.bemta-3.messagelabs.com id 54/62-24700-D8133505; Fri, 14 Sep 2012 13:30:53 +0000 X-Env-Sender: Ian.Campbell@citrix.com X-Msg-Ref: server-2.tower-174.messagelabs.com!1347629452!30545822!1 X-Originating-IP: [62.200.22.115] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogNjIuMjAwLjIyLjExNSA9PiAxMDkyOTU=\n X-StarScan-Received: X-StarScan-Version: 6.6.1.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 24604 invoked from network); 14 Sep 2012 13:30:52 -0000 Received: from smtp.eu.citrix.com (HELO SMTP.EU.CITRIX.COM) (62.200.22.115) by server-2.tower-174.messagelabs.com with RC4-SHA encrypted SMTP; 14 Sep 2012 13:30:52 -0000 X-IronPort-AV: E=Sophos;i="4.80,423,1344211200"; d="scan'208";a="14547418" Received: from lonpmailmx01.citrite.net ([10.30.203.162]) by LONPIPO01.EU.CITRIX.COM with ESMTP/TLS/RC4-MD5; 14 Sep 2012 13:30:17 +0000 Received: from [10.80.2.42] (10.80.2.42) by LONPMAILMX01.citrite.net (10.30.203.162) with Microsoft SMTP Server id 8.3.279.1; Fri, 14 Sep 2012 14:30:17 +0100 Message-ID: <1347629416.24226.208.camel@zakaz.uk.xensource.com> From: Ian Campbell To: Adam Goryachev Date: Fri, 14 Sep 2012 14:30:16 +0100 In-Reply-To: <50532CE9.5080601@websitemanagers.com.au> References: <5051D0C5.5070600@websitemanagers.com.au> <1347609879.24226.148.camel@zakaz.uk.xensource.com> <50532CE9.5080601@websitemanagers.com.au> Organization: Citrix Systems, Inc. X-Mailer: Evolution 3.4.3-1 MIME-Version: 1.0 Cc: "xen-users@lists.xen.org" Subject: Re: [Xen-users] Poor Windows 2003 + GPLPV performance compared to VMWare X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: base64 Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org T24gRnJpLCAyMDEyLTA5LTE0IGF0IDE0OjExICswMTAwLCBBZGFtIEdvcnlhY2hldiB3cm90ZToK PiBPbiAxNC8wOS8xMiAxODowNCwgSWFuIENhbXBiZWxsIHdyb3RlOgo+ID4gT24gVGh1LCAyMDEy LTA5LTEzIGF0IDEzOjI1ICswMTAwLCBBZGFtIEdvcnlhY2hldiB3cm90ZToKPiA+PiBUaGVuLCB0 aGUgdXNlciByYW4gdGhlIGFib3ZlIHByb2Nlc3MsIGFuZCBnb3QgY29uc2lzdGVudGx5LCByZXN1 bHRzIG9mCj4gPj4gYXBwcm94IDI1MDAgdHJhbnNhY3Rpb25zIHBlciBzZWNvbmQKPiA+IAo+ID4g QXJlIHlvdSBjZXJ0YWluIHRoZSBHUExQViBkcml2ZXJzIGhhdmUgdGFrZW4gaG9sZCBhbmQgeW91 IGFyZW4ndCB1c2luZwo+ID4gZW11bGF0ZWQgZGV2aWNlcz8KPiAKPiBXaXRoaW4gV2luZG93cywg RGV2aWNlIE1hbmFnZXIgc2hvd3MgdGhlIERpc2sgRHJpdmVzIGFzICJYRVYgUFYgRElTSwo+IFND U0kgRGlzayBEZXZpY2UiLCB0aGlzIGlzIHRoZSBuZXdlc3Qgb25lIHdoaWNoIGl0IGRldGVjdGVk IGFuZAo+IGluc3RhbGxlZCBhZnRlciBJIGNoYW5nZWQgdGhlIGNvbmZpZyBmcm9tIGhkYSB0byB4 dmRhLgo+IAo+ID4gSSBkb24ndCBrbm93IGhvdyB5b3UgY2FuIHRlbGwgZnJvbSB3aXRoaW4gV2lu ZG93cyBidXQgZnJvbSBkb20wIHlvdSBjYW4KPiA+IGxvb2sgaW4gdGhlIG91dHB1dCBvZiAieGVu c3RvcmUtbHMgLWZwIiBmb3IgdGhlICJzdGF0ZSIgbm9kZSBhc3NvY2lhdGVkCj4gPiB3aXRoIGVh Y2ggZGV2aWNlIGZyb250ZW5kIC0tIHRoZXkgc2hvdWxkIGJlIGluIHN0YXRlIDQgKGNvbm5lY3Rl ZCkuCj4gCj4gcm9vdEBwbTA4On4jIHhlbnN0b3JlLWxzIC1mcHxncmVwIHN0YXRlfGdyZXAgdmJk Cj4gL2xvY2FsL2RvbWFpbi8wL2JhY2tlbmQvdmJkLzgvNTE3MTIvc3RhdGUgPSAiNCIgICAobjAs cjgpCj4gL2xvY2FsL2RvbWFpbi84L2RldmljZS92YmQvNTE3MTIvc3RhdGUgPSAiNCIgICAobjgs cjApCj4gCj4gSSBhc3N1bWUgZG9tIGlkIDggaXMgdGhlIFZNLCBhbmQgZG9tMCBpcyB0aGUgZmly c3QgbGluZSBhYm92ZS4KPiAKPiA+IFsuLi5dCj4gPj4gbWVtb3J5ICAgICAgICA9IDQwOTYKPiA+ PiBzaGFkb3dfbWVtb3J5ICAgID0gMTIKPiA+IAo+ID4gVGhpcyBzZWVtcyBsb3cgdG8gbWUuIFRo ZSBkZWZhdWx0IGlzIDFNIHBlciBDUFUsIHBsdXMgOEsgcGVyIE0gb2YgUkFNLAo+ID4gd2hpY2gg aXMgNE0gKyA4KjQwOTZLID0gNE0rMzJNID0gMzZNLiBEbyB5b3UgaGF2ZSBhbnkgcmVhc29uIHRv IHNlY29uZAo+ID4gZ3Vlc3MgdGhpcz8gKFVzdWFsbHkgdGhpcyBvcHRpb24gaXMgdXNlZCB0byBp bmNyZWFzZSBzaGFkb3cgUkFNIHdoZXJlCj4gPiB0aGUgd29ya2xvYWQgZGVtYW5kcyBpdCkuCj4g Cj4gT0ssIEkgbXVzdCBhZG1pdCBJIGhhdmUgbm8gaWRlYSwgSSBjb3BpZWQgdGhpcyB2YWx1ZSBm cm9tIGFuIGV4YW1wbGUgYQo+IGxvbmcgdGltZSBhZ28sIGFuZCBJJ3ZlIGp1c3QgY29waWVkIGl0 IGludG8gZWFjaCBuZXcgdm0gYXMgSSBnby4KPiAKPiBGcm9tIGhlcmU6Cj4gaHR0cDovL3dpa2ku cHJnbXIuY29tL21lZGlhd2lraS9pbmRleC5waHAvQ2hhcHRlcl8xMjpfSFZNOl9CZXlvbmRfUGFy YXZpcnR1YWxpemF0aW9uCj4gSXQgc2F5czoKPiBUaGUgc2hhZG93X21lbW9yeSBkaXJlY3RpdmUg c3BlY2lmaWVzIHRoZSBhbW91bnQgb2YgbWVtb3J5IHRvIHVzZSBmb3IKPiBzaGFkb3cgcGFnZSB0 YWJsZXMuIChTaGFkb3cgcGFnZSB0YWJsZXMsIG9mIGNvdXJzZSwgYXJlIHRoZQo+IGFmb3JlbWVu dGlvbmVkIGNvcGllcyBvZiB0aGUgdGFibGVzIHRoYXQgbWFwIHByb2Nlc3MtdmlydHVhbCBtZW1v cnkgdG8KPiBwaHlzaWNhbCBtZW1vcnkuKSBYZW4gYWR2aXNlcyBhbGxvY2F0aW5nIGF0IGxlYXN0 IDJLQiBwZXIgTUIgb2YgZG9tYWluCj4gbWVtb3J5LCBhbmQg4oCcYSBmZXfigJ0gTUIgcGVyIHZp cnR1YWwgQ1BVLiBOb3RlIHRoYXQgdGhpcyBtZW1vcnkgaXMgaW4KPiBhZGRpdGlvbiB0byB0aGUg ZG9tVeKAmXMgYWxsb2NhdGlvbiBzcGVjaWZpZWQgaW4gdGhlIG1lbW9yeSBsaW5lLgo+IAo+IEkn bSBub3QgcmVhbGx5IHN1cmUgd2hlcmUgdG8gZmluZCBkZWZpbml0aXZlIGRvY3VtZW50YXRpb24g b24gYWxsIHRoZQo+IGNvbmZpZyBmaWxlIG9wdGlvbnMgd2l0aGluIHhlbi4uLi4KCmh0dHA6Ly94 ZW5iaXRzLnhlbi5vcmcvZG9jcy80LjItdGVzdGluZy8gaGFzIG1hbiBwYWdlcyBmb3IgdGhlIGNv bmZpZwpmaWxlcy4gVGhlc2UgYXJlIGFsc28gaW5zdGFsbGVkIG9uIHRoZSBob3N0IGFzIHBhcnQg b2YgdGhlIGJ1aWxkLgoKSWYgeW91IGFyZSB1c2luZyB4ZW5kIHRoZW4gdGhlIHhtIG9uZXMgYXJl IGEgYml0IGxhY2tpbmcuIEhvd2V2ZXIgeGwgaXMKbW9zdGx5IGNvbXBhdGlibGUgd2l0aCB4bSBz byB0aGUgeGwgbWFucGFnZXMgbGFyZ2VseSBhcHBseS4gVGhlcmUncyBhbHNvCmEgYnVuY2ggb2Yg c3R1ZmYgb24gaHR0cDovL3dpa2kueGVuLm9yZy93aWtpLgoKPiAoWEVOKSBIVk06IEFTSURzIGVu YWJsZWQuCj4gKFhFTikgU1ZNOiBTdXBwb3J0ZWQgYWR2YW5jZWQgZmVhdHVyZXM6Cj4gKFhFTikg IC0gTmVzdGVkIFBhZ2UgVGFibGVzIChOUFQpCj4gKFhFTikgIC0gTGFzdCBCcmFuY2ggUmVjb3Jk IChMQlIpIFZpcnR1YWxpc2F0aW9uCj4gKFhFTikgIC0gTmV4dC1SSVAgU2F2ZWQgb24gI1ZNRVhJ VAo+IChYRU4pICAtIFBhdXNlLUludGVyY2VwdCBGaWx0ZXIKPiAoWEVOKSBIVk06IFNWTSBlbmFi bGVkCj4gKFhFTikgSFZNOiBIYXJkd2FyZSBBc3Npc3RlZCBQYWdpbmcgKEhBUCkgZGV0ZWN0ZWQK PiAoWEVOKSBIVk06IEhBUCBwYWdlIHNpemVzOiA0a0IsIDJNQiwgMUdCCj4gCj4gSSdtIGd1ZXNz aW5nIHRoYXQgaXMgYSB5ZXMgdG8gSEFQIGFuZCBOUFQgYnV0IG5vIGZvciBFUFQuLi4uCj4gCj4g VGhpcyBpcyBhIEFNRCBQaGVub20odG0pIElJIFg2IDExMDBUIFByb2Nlc3NvcgoKRVBUIGlzIHRo ZSBJbnRlbCBlcXVpdmFsZW50IG9mIE5QVCBzbyB5b3Ugd291bGRuJ3QgaGF2ZSB0aGF0IG9uZS4K Cj4gPj4gZGV2aWNlX21vZGVsICAgID0gJy91c3IvbGliL3hlbi1kZWZhdWx0L2Jpbi9xZW11LWRt Jwo+ID4+IGxvY2FsdGltZSAgICA9IDEKPiA+PiBuYW1lICAgICAgICA9ICJ2bTEiCj4gPj4gY3B1 cyAgICAgICAgPSAiMiwzLDQsNSIgICAgIyBXaGljaCBwaHlzaWNhbCBDUFUncyB0byBhbGxvdwo+ ID4gCj4gPiBIYXZlIHlvdSBwaW5uZWQgZG9tMCB0byB1c2UgcENQVSAxIGFuZC9wIHBDUFVzID4g Nj8KPiAKPiBObywgaG93IHNob3VsZCBJIHBpbiBkb20wIHRvIGNwdTAgPwoKZG9tMF92Y3B1c19w aW4gYXMgZGVzY3JpYmVkIGluCmh0dHA6Ly94ZW5iaXRzLnhlbi5vcmcvZG9jcy80LjItdGVzdGlu Zy9taXNjL3hlbi1jb21tYW5kLWxpbmUuaHRtbAoKPiBBbHNvLCB4bSB2Y3B1LWxpc3Qgc2hvd3Mg dGhpczoKPiB4bSB2Y3B1LWxpc3QKPiBOYW1lICAgICAgICAgICAgICAgICAgICAgICAgICAgICAg ICBJRCAgVkNQVSAgIENQVSBTdGF0ZSAgIFRpbWUocykgQ1BVCj4gQWZmaW5pdHkKPiBEb21haW4t MCAgICAgICAgICAgICAgICAgICAgICAgICAgICAgMCAgICAgMCAgICAgMCAgIHItLSAgIDM0MDkz LjQgYW55IGNwdQo+IERvbWFpbi0wICAgICAgICAgICAgICAgICAgICAgICAgICAgICAwICAgICAx ICAgICA1ICAgLWItICAgIDEyMzkuMyBhbnkgY3B1Cj4gRG9tYWluLTAgICAgICAgICAgICAgICAg ICAgICAgICAgICAgIDAgICAgIDIgICAgIDEgICAtYi0gICAgMTEzNC40IGFueSBjcHUKPiBEb21h aW4tMCAgICAgICAgICAgICAgICAgICAgICAgICAgICAgMCAgICAgMyAgICAgMyAgIC1iLSAgICAx MDQ5LjkgYW55IGNwdQo+IERvbWFpbi0wICAgICAgICAgICAgICAgICAgICAgICAgICAgICAwICAg ICA0ICAgICAwICAgLWItICAgIDEzNDAuNSBhbnkgY3B1Cj4gRG9tYWluLTAgICAgICAgICAgICAg ICAgICAgICAgICAgICAgIDAgICAgIDUgICAgIDIgICAtYi0gICAgMTEyMy4yIGFueSBjcHUKPiB2 bTEgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgOSAgICAgMCAgICAgMiAgIC1iLSAg ICAgIDIwLjUgMi01Cj4gdm0xICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgIDkgICAg IDEgICAgIDQgICAtYi0gICAgICAxNS4yIDItNQo+IHZtMSAgICAgICAgICAgICAgICAgICAgICAg ICAgICAgICAgICA5ICAgICAyICAgICAzICAgLWItICAgICAgMTQuOSAyLTUKPiB2bTEgICAgICAg ICAgICAgICAgICAgICAgICAgICAgICAgICAgOSAgICAgMyAgICAgNCAgIC1iLSAgICAgIDE1LjEg Mi01Cj4gCj4gSSd2ZSBzZXQgdGhlIHZtIHRvIHVzZSBjcHVzIDIsMyw0LDUgYnV0IGhvdyBkbyBJ IGZvcmNlIGl0IHNvOgo+IHZjcHUgMCA9IDIKPiB2Y3B1IDEgPSAzCj4gdmNwdSAyID0gNAo+IHZj cHUgMyA9IDUKPiAKPiBXaXRob3V0IHJ1bm5pbmc6Cj4geG0gdmNwdS1waW4gdm0xIDAgMgo+IHht IHZjcHUtcGluIHZtMSAxIDMKPiB4bSB2Y3B1LXBpbiB2bTEgMiA0Cj4geG0gdmNwdS1waW4gdm0x IDMgNQoKWW91IGhhdmU6CiAgICAgICAgY3B1cyA9ICIyLDMsNCw1Igp3aGljaCBtZWFucyAibGV0 IGFsbCB0aGUgZ3Vlc3RzIFZDUFVzIHJ1biBvbiBhbnkgb2YgUENQVVMgMi01Ii4KCkl0IHNvdW5k cyBsaWtlIHdoYXQgeW91IGFyZSBhc2tpbmcgZm9yIGFib3ZlIGlzOgogICAgICAgIGNwdXMgPSBb MiwzLDQsNV0KV2hpY2ggZm9yY2VzIGd1ZXN0IHZjcHUwPT5wY3B1PTIsIDE9PjMsIDI9PjQgYW5k IDM9PjUuCgpTdWJ0bGUgSSBhZ3JlZS4KCkRvIHlvdSBoYXZlIGEgc3BlY2lmaWMgcmVhc29uIGZv ciBwaW5uaW5nPyBJJ2QgYmUgdGVtcHRlZCB0byBqdXN0IGxldAp0aGUgc2NoZWR1bGVyIGRvIGl0 cyB0aGluZyB1bmxlc3MvdW50aWwgeW91IGRldGVybWluZSB0aGF0IGl0IGlzIGNhdXNpbmcKcHJv YmxlbXMuCgo+ID4gSG93IG1hbnkgZG9tMCB2Y3B1cyBoYXZlIHlvdSBjb25maWd1cmVkPwo+IAo+ IEkgYXNzdW1lIGJ5IGRlZmF1bHQgaXQgdGFrZXMgYWxsIG9mIHRoZW0uLi4KCkNvcnJlY3QuIGRv bTBfbWF4X3ZjcHVzIHdpbGwgYWRqdXN0IHRoaXMgZm9yIHlvdS4KCj4gPiBEb2VzIHlvdXIgc3lz dGVtIGhhdmUgYW55IE5VTUEgcHJvcGVydGllcz8KPiAKPiBJIGRvbid0IHJlYWxseSB1bmRlcnN0 YW5kIHRoaXMgcXVlc3Rpb24uLi4uIGlzIHRoZXJlIGEgc2ltcGxlIG1ldGhvZCB0bwo+IGNoZWNr PyBJdCBpcyBhIEFNRCBQaGVub20odG0pIElJIFg2IDExMDBUIFByb2Nlc3NvciBvbiBhIHJlYXNv bmFibGUKPiBkZXNrdG9wIG1vdGhlcmJvYXJkLCBub3RoaW5nIGZhbmN5Li4uLgo+IAo+ID4gQW5k IGFzIEphbWVzIHN1Z2dlc3RzIGl0IHdvdWxkIGFsc28gYmUgdXNlZnVsIHRvIGJlbmNobWFyayBp U0NTSSBydW5uaW5nCj4gPiBpbiBkb20wIGFuZCBwZXJoYXBzIGV2ZW4gcnVubmluZyBvbiB0aGUg c2FtZSBzeXN0ZW0gd2l0aG91dCBYZW4gKGp1c3QKPiA+IExpbnV4KSB1c2luZyB0aGUgc2FtZSBr ZXJuZWwuIEknbSBub3Qgc3VyZSBpZiBWTXdhcmUgb2ZmZXJzIHNvbWV0aGluZwo+ID4gc2ltaWxh ciB3aGljaCBjb3VsZCBiZSB1c2VkIGZvciBjb21wYXJpc29uLgo+IAo+IFdlbGwsIHRoYXQgaXMg d2hlcmUgdGhpbmdzIHN0YXJ0IHRvIGdldCBjb21wbGljYXRlZCByYXRoZXIgcXVpY2tseS4uLgo+ IFRoZXJlIGFyZSBhIGxvdCBvZiBsYXllcnMgaGVyZSwgYnV0IEknZCBwcmVmZXIgdG8gbG9vayBh dCB0aGUgaXNzdWVzCj4gY2xvc2VyIHRvIHhlbiBmaXJzdCwgc2luY2Ugdm13YXJlIHdhcyB3b3Jr aW5nIGZyb20gYW4gaWRlbnRpY2FsbHkKPiBjb25maWd1cmVkIHNhbi9ldGMsIHNvIG5vdGhpbmcg YXQgYWxsIGhhcyBjaGFuZ2VkIHRoZXJlLiBVbHRpbWF0ZWx5LCB0aGUKPiBzYW4gaXMgdXNpbmcg MyB4IFNTRCBpbiBSQUlENS4gSSBoYXZlIGRvbmUgdmFyaW91cyB0ZXN0aW5nIGluIHRoZSBwYXN0 Cj4gZnJvbSBwbGFpbiBsaW51eCAod2l0aCBvbGRlciBrZXJuZWwgMi42LjMyIGZyb20gZGViaWFu IHN0YWJsZSkgYW5kCj4gYWNoaWV2ZWQgcmVhc29uYWJsZSBmaWd1cmVzIChJIGRvbid0IHJlY2Fs bCBleGFjdGx5KS4KCkkgd2FzIHdvcnJpZWQgYWJvdXQgdGhlIExpbnV4IHNpZGUgcmF0aGVyIHRo YW4gdGhlIFNBTiBpdHNlbGYsIGJ1dCBpdApzb3VuZHMgbGlrZSB5b3UndmUgZ290IHRoYXQgY292 ZXJlZC4KCj4gVGhhbmsgeW91IGZvciB5b3VyIHJlc3BvbnNlcywgaWYgdGhlcmUgaXMgYW55IGZ1 cnRoZXIgaW5mb3JtYXRpb24gSSBjYW4KPiBwcm92aWRlLCBvciBhZGRpdGlvbmFsIHN1Z2dlc3Rp b25zIHlvdSBhcmUgYWJsZSB0byBtYWtlLCBJJ2QgYmUgcmVhbGx5Cj4gYXBwcmVjaWF0aXZlLgo+ IAo+IFJlZ2FyZHMsCj4gQWRhbQo+IAoKCgpfX19fX19fX19fX19fX19fX19fX19fX19fX19fX19f X19fX19fX19fX19fX19fXwpYZW4tdXNlcnMgbWFpbGluZyBsaXN0Clhlbi11c2Vyc0BsaXN0cy54 ZW4ub3JnCmh0dHA6Ly9saXN0cy54ZW4ub3JnL3hlbi11c2Vycw== From xen-users-bounces@lists.xen.org Fri Sep 14 14:55:08 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Fri, 14 Sep 2012 14:55:08 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TCXHU-0001bA-37; Fri, 14 Sep 2012 14:54:08 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TCXHS-0001aq-8D for xen-users@lists.xen.org; Fri, 14 Sep 2012 14:54:06 +0000 Received: from [85.158.139.211:65106] by server-7.bemta-5.messagelabs.com id 9B/59-19703-D0543505; Fri, 14 Sep 2012 14:54:05 +0000 X-Env-Sender: mailinglists@websitemanagers.com.au X-Msg-Ref: server-12.tower-206.messagelabs.com!1347634440!18543329!1 X-Originating-IP: [203.56.191.70] X-SpamReason: No, hits=0.0 required=7.0 tests= X-StarScan-Received: X-StarScan-Version: 6.6.1.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 15910 invoked from network); 14 Sep 2012 14:54:04 -0000 Received: from unknown (HELO hammer.websitemanagers.com.au) (203.56.191.70) by server-12.tower-206.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 14 Sep 2012 14:54:04 -0000 Received: (qmail 3742 invoked by uid 1011); 14 Sep 2012 14:53:29 -0000 Received: from 220.233.87.52 by hammer (envelope-from , uid 1008) with qmail-scanner-1.24 (clamdscan: 0.97.3/15354. spamassassin: 3.3.1. Clear:RC:1(220.233.87.52):. Processed in 0.05417 secs); 14 Sep 2012 14:53:29 -0000 Received: from unknown (HELO ?192.168.2.90?) (220.233.87.52) by 0 with SMTP; 14 Sep 2012 14:53:29 -0000 Message-ID: <505344E8.2030400@websitemanagers.com.au> Date: Sat, 15 Sep 2012 00:53:28 +1000 From: Adam Goryachev Organization: Website Managers User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:15.0) Gecko/20120827 Thunderbird/15.0 MIME-Version: 1.0 To: Ian Campbell References: <5051D0C5.5070600@websitemanagers.com.au> <1347609879.24226.148.camel@zakaz.uk.xensource.com> <50532CE9.5080601@websitemanagers.com.au> <1347629416.24226.208.camel@zakaz.uk.xensource.com> In-Reply-To: <1347629416.24226.208.camel@zakaz.uk.xensource.com> Cc: "xen-users@lists.xen.org" Subject: Re: [Xen-users] Poor Windows 2003 + GPLPV performance compared to VMWare X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org On 14/09/12 23:30, Ian Campbell wrote: > http://xenbits.xen.org/docs/4.2-testing/ has man pages for the config > files. These are also installed on the host as part of the build. > > If you are using xend then the xm ones are a bit lacking. However xl is > mostly compatible with xm so the xl manpages largely apply. There's also > a bunch of stuff on http://wiki.xen.org/wiki. Thanks for the pointer, I'm using 4.1 though, but I guess most of it will still be the same. >>>> device_model = '/usr/lib/xen-default/bin/qemu-dm' >>>> localtime = 1 >>>> name = "vm1" >>>> cpus = "2,3,4,5" # Which physical CPU's to allow >>> >>> Have you pinned dom0 to use pCPU 1 and/p pCPUs > 6? >> >> No, how should I pin dom0 to cpu0 ? > > dom0_vcpus_pin as described in > http://xenbits.xen.org/docs/4.2-testing/misc/xen-command-line.html Thanks, I'll need to reboot the dom0 to apply this, will do as soon as this current scheduled task is complete. > You have: > cpus = "2,3,4,5" > which means "let all the guests VCPUs run on any of PCPUS 2-5". > > It sounds like what you are asking for above is: > cpus = [2,3,4,5] > Which forces guest vcpu0=>pcpu=2, 1=>3, 2=>4 and 3=>5. > > Subtle I agree. Ugh... ok, I'll give that a try. BTW, it would seem this is different from xen 4.0 (from debian stable) where it seems to magically do what I meant to say, or I'm just lucky on those machines :) > Do you have a specific reason for pinning? I'd be tempted to just let > the scheduler do its thing unless/until you determine that it is causing > problems. The only reason for pinning is: a) To stop the scheduler from moving the vCPU around on the pCPU, from my understanding this improves performance b) when running multiple DOMU, I either want a bunch of DOMU to share one cpu, while I want one or more dedicated CPU other DOMU. (ie, I use this as a type of prioritisation/performance tuning. In this case, there is only a single VM, though if some hardware is lost (other physical machines) then will end up with multiple VM's... >>> How many dom0 vcpus have you configured? >> >> I assume by default it takes all of them... > > Correct. dom0_max_vcpus will adjust this for you. Will adjust on the next reboot.... >>> And as James suggests it would also be useful to benchmark iSCSI running >>> in dom0 and perhaps even running on the same system without Xen (just >>> Linux) using the same kernel. I'm not sure if VMware offers something >>> similar which could be used for comparison. >> >> Well, that is where things start to get complicated rather quickly... >> There are a lot of layers here, but I'd prefer to look at the issues >> closer to xen first, since vmware was working from an identically >> configured san/etc, so nothing at all has changed there. Ultimately, the >> san is using 3 x SSD in RAID5. I have done various testing in the past >> from plain linux (with older kernel 2.6.32 from debian stable) and >> achieved reasonable figures (I don't recall exactly). > > I was worried about the Linux side rather than the SAN itself, but it > sounds like you've got that covered. At this stage, the limiting performance should be the single gig ethernet for the physical machine to connect to the network. (The san side has 4 x gig ethernet). This is a live network/system, but it has been a work in progress for the past 12 months... I'll update further once I can get some testing and answers... Will do a test with only changing the shadow_memory, and then if no big improvement, will reboot with the changes to the dom0 cpus etc, and test again. Thank you for your advice. Regards, adam -- Adam Goryachev Website Managers www.websitemanagers.com.au _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Fri Sep 14 14:55:08 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Fri, 14 Sep 2012 14:55:08 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TCXHU-0001bA-37; Fri, 14 Sep 2012 14:54:08 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TCXHS-0001aq-8D for xen-users@lists.xen.org; Fri, 14 Sep 2012 14:54:06 +0000 Received: from [85.158.139.211:65106] by server-7.bemta-5.messagelabs.com id 9B/59-19703-D0543505; Fri, 14 Sep 2012 14:54:05 +0000 X-Env-Sender: mailinglists@websitemanagers.com.au X-Msg-Ref: server-12.tower-206.messagelabs.com!1347634440!18543329!1 X-Originating-IP: [203.56.191.70] X-SpamReason: No, hits=0.0 required=7.0 tests= X-StarScan-Received: X-StarScan-Version: 6.6.1.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 15910 invoked from network); 14 Sep 2012 14:54:04 -0000 Received: from unknown (HELO hammer.websitemanagers.com.au) (203.56.191.70) by server-12.tower-206.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 14 Sep 2012 14:54:04 -0000 Received: (qmail 3742 invoked by uid 1011); 14 Sep 2012 14:53:29 -0000 Received: from 220.233.87.52 by hammer (envelope-from , uid 1008) with qmail-scanner-1.24 (clamdscan: 0.97.3/15354. spamassassin: 3.3.1. Clear:RC:1(220.233.87.52):. Processed in 0.05417 secs); 14 Sep 2012 14:53:29 -0000 Received: from unknown (HELO ?192.168.2.90?) (220.233.87.52) by 0 with SMTP; 14 Sep 2012 14:53:29 -0000 Message-ID: <505344E8.2030400@websitemanagers.com.au> Date: Sat, 15 Sep 2012 00:53:28 +1000 From: Adam Goryachev Organization: Website Managers User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:15.0) Gecko/20120827 Thunderbird/15.0 MIME-Version: 1.0 To: Ian Campbell References: <5051D0C5.5070600@websitemanagers.com.au> <1347609879.24226.148.camel@zakaz.uk.xensource.com> <50532CE9.5080601@websitemanagers.com.au> <1347629416.24226.208.camel@zakaz.uk.xensource.com> In-Reply-To: <1347629416.24226.208.camel@zakaz.uk.xensource.com> Cc: "xen-users@lists.xen.org" Subject: Re: [Xen-users] Poor Windows 2003 + GPLPV performance compared to VMWare X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org On 14/09/12 23:30, Ian Campbell wrote: > http://xenbits.xen.org/docs/4.2-testing/ has man pages for the config > files. These are also installed on the host as part of the build. > > If you are using xend then the xm ones are a bit lacking. However xl is > mostly compatible with xm so the xl manpages largely apply. There's also > a bunch of stuff on http://wiki.xen.org/wiki. Thanks for the pointer, I'm using 4.1 though, but I guess most of it will still be the same. >>>> device_model = '/usr/lib/xen-default/bin/qemu-dm' >>>> localtime = 1 >>>> name = "vm1" >>>> cpus = "2,3,4,5" # Which physical CPU's to allow >>> >>> Have you pinned dom0 to use pCPU 1 and/p pCPUs > 6? >> >> No, how should I pin dom0 to cpu0 ? > > dom0_vcpus_pin as described in > http://xenbits.xen.org/docs/4.2-testing/misc/xen-command-line.html Thanks, I'll need to reboot the dom0 to apply this, will do as soon as this current scheduled task is complete. > You have: > cpus = "2,3,4,5" > which means "let all the guests VCPUs run on any of PCPUS 2-5". > > It sounds like what you are asking for above is: > cpus = [2,3,4,5] > Which forces guest vcpu0=>pcpu=2, 1=>3, 2=>4 and 3=>5. > > Subtle I agree. Ugh... ok, I'll give that a try. BTW, it would seem this is different from xen 4.0 (from debian stable) where it seems to magically do what I meant to say, or I'm just lucky on those machines :) > Do you have a specific reason for pinning? I'd be tempted to just let > the scheduler do its thing unless/until you determine that it is causing > problems. The only reason for pinning is: a) To stop the scheduler from moving the vCPU around on the pCPU, from my understanding this improves performance b) when running multiple DOMU, I either want a bunch of DOMU to share one cpu, while I want one or more dedicated CPU other DOMU. (ie, I use this as a type of prioritisation/performance tuning. In this case, there is only a single VM, though if some hardware is lost (other physical machines) then will end up with multiple VM's... >>> How many dom0 vcpus have you configured? >> >> I assume by default it takes all of them... > > Correct. dom0_max_vcpus will adjust this for you. Will adjust on the next reboot.... >>> And as James suggests it would also be useful to benchmark iSCSI running >>> in dom0 and perhaps even running on the same system without Xen (just >>> Linux) using the same kernel. I'm not sure if VMware offers something >>> similar which could be used for comparison. >> >> Well, that is where things start to get complicated rather quickly... >> There are a lot of layers here, but I'd prefer to look at the issues >> closer to xen first, since vmware was working from an identically >> configured san/etc, so nothing at all has changed there. Ultimately, the >> san is using 3 x SSD in RAID5. I have done various testing in the past >> from plain linux (with older kernel 2.6.32 from debian stable) and >> achieved reasonable figures (I don't recall exactly). > > I was worried about the Linux side rather than the SAN itself, but it > sounds like you've got that covered. At this stage, the limiting performance should be the single gig ethernet for the physical machine to connect to the network. (The san side has 4 x gig ethernet). This is a live network/system, but it has been a work in progress for the past 12 months... I'll update further once I can get some testing and answers... Will do a test with only changing the shadow_memory, and then if no big improvement, will reboot with the changes to the dom0 cpus etc, and test again. Thank you for your advice. Regards, adam -- Adam Goryachev Website Managers www.websitemanagers.com.au _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Fri Sep 14 16:00:17 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Fri, 14 Sep 2012 16:00:17 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TCYIQ-0004vK-TX; Fri, 14 Sep 2012 15:59:10 +0000 Received: from mail27.messagelabs.com ([193.109.254.147]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TCYIQ-0004v9-0I for xen-users@lists.xen.org; Fri, 14 Sep 2012 15:59:10 +0000 X-Env-Sender: vinicius.ruoso@gmail.com X-Msg-Ref: server-3.tower-27.messagelabs.com!1347638342!9075533!1 X-Originating-IP: [209.85.214.173] X-SpamReason: No, hits=0.3 required=7.0 tests=ML_RADAR_SPEW_LINKS_14, RCVD_BY_IP,spamassassin: X-StarScan-Received: X-StarScan-Version: 6.6.1.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 4164 invoked from network); 14 Sep 2012 15:59:03 -0000 Received: from mail-ob0-f173.google.com (HELO mail-ob0-f173.google.com) (209.85.214.173) by server-3.tower-27.messagelabs.com with RC4-SHA encrypted SMTP; 14 Sep 2012 15:59:03 -0000 Received: by obbta14 with SMTP id ta14so8046169obb.32 for ; Fri, 14 Sep 2012 08:59:02 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=jLxub3XBOU5qKJotD/vv4DyYQwbLeB3whAj69ihz4Fk=; b=TTUFUx3vnfVJPAsxuuVq5brpsgjPgE8mM17ZqFVC+FKcgxWLvfaBrE7Ze5lp1nzvaB UG6HWfyW52aDtmVhLHAMrsyLjCtaqydEXLxO8qsoAW0E7c3tMEucvH8+DTPlHgYxweFA WDrLOoVb7du9zYFvi08CfLSBzNRIh9hvoWtFsMTVR0km3URFrwqqyNrcy/ks+29tTdlE 5FhHjhk0nZ0comsda5j71QOCQAY7NrnNAkp97XA5MBR0L0yn6XYPinJq+Y5mg4ssNs2G 9n3u3QW2MErpmxJ8j4e1KBBpT8Fy02XIQ9ZppzGgikvfiPWDgHzB27MPtYv5L4Y56uoJ yTrQ== MIME-Version: 1.0 Received: by 10.60.12.8 with SMTP id u8mr3978358oeb.46.1347638342176; Fri, 14 Sep 2012 08:59:02 -0700 (PDT) Received: by 10.76.135.106 with HTTP; Fri, 14 Sep 2012 08:59:02 -0700 (PDT) In-Reply-To: References: Date: Fri, 14 Sep 2012 12:59:02 -0300 Message-ID: From: Vinicius Kwiecien Ruoso To: "Fajar A. Nugraha" Cc: xen-users@lists.xen.org Subject: Re: [Xen-users] Xen Networking X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org Hi! Thanks for your responses! Both answers were very helpfull. Everything worked just great: VPN, the nat and the VM LAN. My mistake was that in the interfaces file I was always declaring both the eth0 and the xenbr0 (even with the eth0 with no configurations). Now I just have another question. Assume I'm going to create a new VM, and it will have the same parameters as this one (bridge eth0). I should create another bridge (xenbr1), or it will automatically use the existing bridge (xenbr0)? Also, I'm trying to install windows server 2008 instead of the xp. I get a blue screen with the 0x0...7E error. I've checked the list for previous errors like this, and trying the following. - Used 2 different isos (one downloaded from MS) and another from a DVD. - with the DVD iso I get the blue screen just after the "windows loading files" - with the MS iso I get the blue screen a few seconds after the GUI is launched saying "starting windows" - I've changed the DVD configuration file from file:/ to tap:aio: - I've all acpi,apic and pae = 1 in the config Any ideas? Should I send another email with a different subject? Thanks again for your suggestions. Vinicius 2012/9/13 Fajar A. Nugraha : > On Fri, Sep 14, 2012 at 1:46 AM, Vinicius Kwiecien Ruoso > wrote: >> I've tried those with different configurations in /etc/network/interfaces >> >> using: >> auto eth0 >> iface eth0 inet static >> address 172.16.10.1 >> netmask 255.255.255.0 >> >> auto xenbr0 >> iface xenbr0 inet static >> address 172.16.10.50 >> netmask 255.255.255.0 >> bridge_ports eth0 >> >> >> also didn't work. When I configure the interfaces like this and run >> /etc/init.d/networking restart, the eth0 looses it IP address, and >> nothing works anymore... > > Duh. Your config is wrong. > > If eth0 is part of the bridge, then you put the IP on the bridge, not on eth0. > Examples (both assume you use dhcp, adjust as needed): > - http://wiki.xen.org/wiki/Xen_Beginners_Guide#Setup_Linux_Bridge_for_guest_networking > - http://wiki.1tux.org/wiki/Ubuntu/Bridge > > -- > Fajar _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Fri Sep 14 16:00:17 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Fri, 14 Sep 2012 16:00:17 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TCYIQ-0004vK-TX; Fri, 14 Sep 2012 15:59:10 +0000 Received: from mail27.messagelabs.com ([193.109.254.147]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TCYIQ-0004v9-0I for xen-users@lists.xen.org; Fri, 14 Sep 2012 15:59:10 +0000 X-Env-Sender: vinicius.ruoso@gmail.com X-Msg-Ref: server-3.tower-27.messagelabs.com!1347638342!9075533!1 X-Originating-IP: [209.85.214.173] X-SpamReason: No, hits=0.3 required=7.0 tests=ML_RADAR_SPEW_LINKS_14, RCVD_BY_IP,spamassassin: X-StarScan-Received: X-StarScan-Version: 6.6.1.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 4164 invoked from network); 14 Sep 2012 15:59:03 -0000 Received: from mail-ob0-f173.google.com (HELO mail-ob0-f173.google.com) (209.85.214.173) by server-3.tower-27.messagelabs.com with RC4-SHA encrypted SMTP; 14 Sep 2012 15:59:03 -0000 Received: by obbta14 with SMTP id ta14so8046169obb.32 for ; Fri, 14 Sep 2012 08:59:02 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=jLxub3XBOU5qKJotD/vv4DyYQwbLeB3whAj69ihz4Fk=; b=TTUFUx3vnfVJPAsxuuVq5brpsgjPgE8mM17ZqFVC+FKcgxWLvfaBrE7Ze5lp1nzvaB UG6HWfyW52aDtmVhLHAMrsyLjCtaqydEXLxO8qsoAW0E7c3tMEucvH8+DTPlHgYxweFA WDrLOoVb7du9zYFvi08CfLSBzNRIh9hvoWtFsMTVR0km3URFrwqqyNrcy/ks+29tTdlE 5FhHjhk0nZ0comsda5j71QOCQAY7NrnNAkp97XA5MBR0L0yn6XYPinJq+Y5mg4ssNs2G 9n3u3QW2MErpmxJ8j4e1KBBpT8Fy02XIQ9ZppzGgikvfiPWDgHzB27MPtYv5L4Y56uoJ yTrQ== MIME-Version: 1.0 Received: by 10.60.12.8 with SMTP id u8mr3978358oeb.46.1347638342176; Fri, 14 Sep 2012 08:59:02 -0700 (PDT) Received: by 10.76.135.106 with HTTP; Fri, 14 Sep 2012 08:59:02 -0700 (PDT) In-Reply-To: References: Date: Fri, 14 Sep 2012 12:59:02 -0300 Message-ID: From: Vinicius Kwiecien Ruoso To: "Fajar A. Nugraha" Cc: xen-users@lists.xen.org Subject: Re: [Xen-users] Xen Networking X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org Hi! Thanks for your responses! Both answers were very helpfull. Everything worked just great: VPN, the nat and the VM LAN. My mistake was that in the interfaces file I was always declaring both the eth0 and the xenbr0 (even with the eth0 with no configurations). Now I just have another question. Assume I'm going to create a new VM, and it will have the same parameters as this one (bridge eth0). I should create another bridge (xenbr1), or it will automatically use the existing bridge (xenbr0)? Also, I'm trying to install windows server 2008 instead of the xp. I get a blue screen with the 0x0...7E error. I've checked the list for previous errors like this, and trying the following. - Used 2 different isos (one downloaded from MS) and another from a DVD. - with the DVD iso I get the blue screen just after the "windows loading files" - with the MS iso I get the blue screen a few seconds after the GUI is launched saying "starting windows" - I've changed the DVD configuration file from file:/ to tap:aio: - I've all acpi,apic and pae = 1 in the config Any ideas? Should I send another email with a different subject? Thanks again for your suggestions. Vinicius 2012/9/13 Fajar A. Nugraha : > On Fri, Sep 14, 2012 at 1:46 AM, Vinicius Kwiecien Ruoso > wrote: >> I've tried those with different configurations in /etc/network/interfaces >> >> using: >> auto eth0 >> iface eth0 inet static >> address 172.16.10.1 >> netmask 255.255.255.0 >> >> auto xenbr0 >> iface xenbr0 inet static >> address 172.16.10.50 >> netmask 255.255.255.0 >> bridge_ports eth0 >> >> >> also didn't work. When I configure the interfaces like this and run >> /etc/init.d/networking restart, the eth0 looses it IP address, and >> nothing works anymore... > > Duh. Your config is wrong. > > If eth0 is part of the bridge, then you put the IP on the bridge, not on eth0. > Examples (both assume you use dhcp, adjust as needed): > - http://wiki.xen.org/wiki/Xen_Beginners_Guide#Setup_Linux_Bridge_for_guest_networking > - http://wiki.1tux.org/wiki/Ubuntu/Bridge > > -- > Fajar _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Fri Sep 14 18:01:32 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Fri, 14 Sep 2012 18:01:32 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TCaBV-0000Dc-M8; Fri, 14 Sep 2012 18:00:09 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TCaBT-0000DX-B0 for xen-users@lists.xen.org; Fri, 14 Sep 2012 18:00:07 +0000 Received: from [85.158.137.99:49817] by server-12.bemta-3.messagelabs.com id 0D/49-10384-4A073505; Fri, 14 Sep 2012 18:00:04 +0000 X-Env-Sender: linux@thehobsons.co.uk X-Msg-Ref: server-9.tower-217.messagelabs.com!1347645601!14555437!1 X-Originating-IP: [81.174.135.208] X-SpamReason: No, hits=0.0 required=7.0 tests= X-StarScan-Received: X-StarScan-Version: 6.6.1.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 8806 invoked from network); 14 Sep 2012 18:00:03 -0000 Received: from patsy.thehobsons.co.uk (HELO patsy.thehobsons.co.uk) (81.174.135.208) by server-9.tower-217.messagelabs.com with SMTP; 14 Sep 2012 18:00:03 -0000 Received: from localhost (localhost [127.0.0.1]) by patsy.thehobsons.co.uk (Postfix) with ESMTP id 119D010401B for ; Fri, 14 Sep 2012 18:59:51 +0100 (BST) Received: from patsy.thehobsons.co.uk ([127.0.0.1]) by localhost (patsy.thehobsons.co.uk [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id PDQfSwAiwTWO for ; Fri, 14 Sep 2012 18:59:50 +0100 (BST) Received: from simon.thehobsons.co.uk (simons-macbookpro.thehobsons.co.uk [192.168.0.202]) by patsy.thehobsons.co.uk (Postfix) with ESMTP id A1D9C10401A for ; Fri, 14 Sep 2012 18:59:50 +0100 (BST) Mime-Version: 1.0 Message-Id: In-Reply-To: References: Date: Fri, 14 Sep 2012 18:59:42 +0100 To: xen-users@lists.xen.org From: Simon Hobson Subject: Re: [Xen-users] Xen Networking X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset="us-ascii"; Format="flowed" Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org Vinicius Kwiecien Ruoso wrote: >Assume I'm going to create a new VM, >and it will have the same parameters as this one (bridge eth0). I >should create another bridge (xenbr1), or it will automatically use >the existing bridge (xenbr0)? Normally you would want to be using the same network setup. So when specifying the VIF entry for the new VM, specify the same xenbr0. It may help to take a step back and consider what all this represents. The bridge is analogous to a physical switch. The VM is analogous to a physical box. And if you don't do anything special in the Dom0 then that isn't really analogous to anything - but if doing NAT, then it's analogous to a standalone router doing NAT. So having got your standalone router doing NAT, and a physical switch allowing devices to be connected to it, you can connect multiple servers to that same switch. In the same way, once you've got the Dom0 with NAT and a bridge running, you can connect multiple VMs to the one bridge. -- Simon Hobson Visit http://www.magpiesnestpublishing.co.uk/ for books by acclaimed author Gladys Hobson. Novels - poetry - short stories - ideal as Christmas stocking fillers. Some available as e-books. _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Fri Sep 14 18:01:32 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Fri, 14 Sep 2012 18:01:32 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TCaBV-0000Dc-M8; Fri, 14 Sep 2012 18:00:09 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TCaBT-0000DX-B0 for xen-users@lists.xen.org; Fri, 14 Sep 2012 18:00:07 +0000 Received: from [85.158.137.99:49817] by server-12.bemta-3.messagelabs.com id 0D/49-10384-4A073505; Fri, 14 Sep 2012 18:00:04 +0000 X-Env-Sender: linux@thehobsons.co.uk X-Msg-Ref: server-9.tower-217.messagelabs.com!1347645601!14555437!1 X-Originating-IP: [81.174.135.208] X-SpamReason: No, hits=0.0 required=7.0 tests= X-StarScan-Received: X-StarScan-Version: 6.6.1.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 8806 invoked from network); 14 Sep 2012 18:00:03 -0000 Received: from patsy.thehobsons.co.uk (HELO patsy.thehobsons.co.uk) (81.174.135.208) by server-9.tower-217.messagelabs.com with SMTP; 14 Sep 2012 18:00:03 -0000 Received: from localhost (localhost [127.0.0.1]) by patsy.thehobsons.co.uk (Postfix) with ESMTP id 119D010401B for ; Fri, 14 Sep 2012 18:59:51 +0100 (BST) Received: from patsy.thehobsons.co.uk ([127.0.0.1]) by localhost (patsy.thehobsons.co.uk [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id PDQfSwAiwTWO for ; Fri, 14 Sep 2012 18:59:50 +0100 (BST) Received: from simon.thehobsons.co.uk (simons-macbookpro.thehobsons.co.uk [192.168.0.202]) by patsy.thehobsons.co.uk (Postfix) with ESMTP id A1D9C10401A for ; Fri, 14 Sep 2012 18:59:50 +0100 (BST) Mime-Version: 1.0 Message-Id: In-Reply-To: References: Date: Fri, 14 Sep 2012 18:59:42 +0100 To: xen-users@lists.xen.org From: Simon Hobson Subject: Re: [Xen-users] Xen Networking X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset="us-ascii"; Format="flowed" Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org Vinicius Kwiecien Ruoso wrote: >Assume I'm going to create a new VM, >and it will have the same parameters as this one (bridge eth0). I >should create another bridge (xenbr1), or it will automatically use >the existing bridge (xenbr0)? Normally you would want to be using the same network setup. So when specifying the VIF entry for the new VM, specify the same xenbr0. It may help to take a step back and consider what all this represents. The bridge is analogous to a physical switch. The VM is analogous to a physical box. And if you don't do anything special in the Dom0 then that isn't really analogous to anything - but if doing NAT, then it's analogous to a standalone router doing NAT. So having got your standalone router doing NAT, and a physical switch allowing devices to be connected to it, you can connect multiple servers to that same switch. In the same way, once you've got the Dom0 with NAT and a bridge running, you can connect multiple VMs to the one bridge. -- Simon Hobson Visit http://www.magpiesnestpublishing.co.uk/ for books by acclaimed author Gladys Hobson. Novels - poetry - short stories - ideal as Christmas stocking fillers. Some available as e-books. _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Fri Sep 14 18:37:35 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Fri, 14 Sep 2012 18:37:35 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TCakX-0000yw-8v; Fri, 14 Sep 2012 18:36:21 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TCakW-0000yr-BD for xen-users@lists.xen.org; Fri, 14 Sep 2012 18:36:20 +0000 Received: from [85.158.143.99:61547] by server-2.bemta-4.messagelabs.com id CE/EE-21239-32973505; Fri, 14 Sep 2012 18:36:19 +0000 X-Env-Sender: vinicius.ruoso@gmail.com X-Msg-Ref: server-14.tower-216.messagelabs.com!1347647770!20790905!1 X-Originating-IP: [209.85.214.173] X-SpamReason: No, hits=0.3 required=7.0 tests=ML_RADAR_SPEW_LINKS_14, RCVD_BY_IP,spamassassin: X-StarScan-Received: X-StarScan-Version: 6.6.1.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 12146 invoked from network); 14 Sep 2012 18:36:12 -0000 Received: from mail-ob0-f173.google.com (HELO mail-ob0-f173.google.com) (209.85.214.173) by server-14.tower-216.messagelabs.com with RC4-SHA encrypted SMTP; 14 Sep 2012 18:36:12 -0000 Received: by obbta14 with SMTP id ta14so8317904obb.32 for ; Fri, 14 Sep 2012 11:36:10 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=ZuRXKJuvCh3eX4oc2/xJ056oRAkt8GBypDr8d8K2AD0=; b=yCaP048sByq9BCpYETEGLXcRVEPoae7KC6hMxOFtP8IKpUl8TP0FlfVmsHd1cdtoGu QdATq0uz2pGgwi1r6vp0jy0FeFtHFHRB27e1bnlmyc1Hfv0+LrN2u6Q3B1L4olqHdT4C VjE3KqU+c5Jkhb69mdpwxgSNoeQmwSwopzUUK6aqd5l87IhBmInGxoveT2pInOR4eNp2 V3WskXEwxMJe7RZcKSuo9gdeYBJ2ZUkBo3ljZdG0iCstMynBlt0dhWKXsnHtwihMyXKT vntJ+N8qZQ8qUct4zacwKYrhuycOiDTr2g7tcuARCkVwfNL1D8uhqLAm5OzNX2EaeRid OJww== MIME-Version: 1.0 Received: by 10.60.26.133 with SMTP id l5mr4856040oeg.60.1347647770278; Fri, 14 Sep 2012 11:36:10 -0700 (PDT) Received: by 10.76.135.106 with HTTP; Fri, 14 Sep 2012 11:36:10 -0700 (PDT) In-Reply-To: References: Date: Fri, 14 Sep 2012 15:36:10 -0300 Message-ID: From: Vinicius Kwiecien Ruoso To: Simon Hobson Cc: xen-users@lists.xen.org Subject: Re: [Xen-users] Xen Networking X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org Perfect. Thanks a lot for this explanation Simon! 2012/9/14 Simon Hobson : > Vinicius Kwiecien Ruoso wrote: > >> Assume I'm going to create a new VM, >> and it will have the same parameters as this one (bridge eth0). I >> should create another bridge (xenbr1), or it will automatically use >> the existing bridge (xenbr0)? > > > Normally you would want to be using the same network setup. So when > specifying the VIF entry for the new VM, specify the same xenbr0. > > It may help to take a step back and consider what all this represents. The > bridge is analogous to a physical switch. The VM is analogous to a physical > box. And if you don't do anything special in the Dom0 then that isn't really > analogous to anything - but if doing NAT, then it's analogous to a > standalone router doing NAT. > > So having got your standalone router doing NAT, and a physical switch > allowing devices to be connected to it, you can connect multiple servers to > that same switch. In the same way, once you've got the Dom0 with NAT and a > bridge running, you can connect multiple VMs to the one bridge. > > -- > Simon Hobson > > Visit http://www.magpiesnestpublishing.co.uk/ for books by acclaimed > author Gladys Hobson. Novels - poetry - short stories - ideal as > Christmas stocking fillers. Some available as e-books. > > _______________________________________________ > Xen-users mailing list > Xen-users@lists.xen.org > http://lists.xen.org/xen-users _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Fri Sep 14 18:37:35 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Fri, 14 Sep 2012 18:37:35 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TCakX-0000yw-8v; Fri, 14 Sep 2012 18:36:21 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TCakW-0000yr-BD for xen-users@lists.xen.org; Fri, 14 Sep 2012 18:36:20 +0000 Received: from [85.158.143.99:61547] by server-2.bemta-4.messagelabs.com id CE/EE-21239-32973505; Fri, 14 Sep 2012 18:36:19 +0000 X-Env-Sender: vinicius.ruoso@gmail.com X-Msg-Ref: server-14.tower-216.messagelabs.com!1347647770!20790905!1 X-Originating-IP: [209.85.214.173] X-SpamReason: No, hits=0.3 required=7.0 tests=ML_RADAR_SPEW_LINKS_14, RCVD_BY_IP,spamassassin: X-StarScan-Received: X-StarScan-Version: 6.6.1.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 12146 invoked from network); 14 Sep 2012 18:36:12 -0000 Received: from mail-ob0-f173.google.com (HELO mail-ob0-f173.google.com) (209.85.214.173) by server-14.tower-216.messagelabs.com with RC4-SHA encrypted SMTP; 14 Sep 2012 18:36:12 -0000 Received: by obbta14 with SMTP id ta14so8317904obb.32 for ; Fri, 14 Sep 2012 11:36:10 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=ZuRXKJuvCh3eX4oc2/xJ056oRAkt8GBypDr8d8K2AD0=; b=yCaP048sByq9BCpYETEGLXcRVEPoae7KC6hMxOFtP8IKpUl8TP0FlfVmsHd1cdtoGu QdATq0uz2pGgwi1r6vp0jy0FeFtHFHRB27e1bnlmyc1Hfv0+LrN2u6Q3B1L4olqHdT4C VjE3KqU+c5Jkhb69mdpwxgSNoeQmwSwopzUUK6aqd5l87IhBmInGxoveT2pInOR4eNp2 V3WskXEwxMJe7RZcKSuo9gdeYBJ2ZUkBo3ljZdG0iCstMynBlt0dhWKXsnHtwihMyXKT vntJ+N8qZQ8qUct4zacwKYrhuycOiDTr2g7tcuARCkVwfNL1D8uhqLAm5OzNX2EaeRid OJww== MIME-Version: 1.0 Received: by 10.60.26.133 with SMTP id l5mr4856040oeg.60.1347647770278; Fri, 14 Sep 2012 11:36:10 -0700 (PDT) Received: by 10.76.135.106 with HTTP; Fri, 14 Sep 2012 11:36:10 -0700 (PDT) In-Reply-To: References: Date: Fri, 14 Sep 2012 15:36:10 -0300 Message-ID: From: Vinicius Kwiecien Ruoso To: Simon Hobson Cc: xen-users@lists.xen.org Subject: Re: [Xen-users] Xen Networking X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org Perfect. Thanks a lot for this explanation Simon! 2012/9/14 Simon Hobson : > Vinicius Kwiecien Ruoso wrote: > >> Assume I'm going to create a new VM, >> and it will have the same parameters as this one (bridge eth0). I >> should create another bridge (xenbr1), or it will automatically use >> the existing bridge (xenbr0)? > > > Normally you would want to be using the same network setup. So when > specifying the VIF entry for the new VM, specify the same xenbr0. > > It may help to take a step back and consider what all this represents. The > bridge is analogous to a physical switch. The VM is analogous to a physical > box. And if you don't do anything special in the Dom0 then that isn't really > analogous to anything - but if doing NAT, then it's analogous to a > standalone router doing NAT. > > So having got your standalone router doing NAT, and a physical switch > allowing devices to be connected to it, you can connect multiple servers to > that same switch. In the same way, once you've got the Dom0 with NAT and a > bridge running, you can connect multiple VMs to the one bridge. > > -- > Simon Hobson > > Visit http://www.magpiesnestpublishing.co.uk/ for books by acclaimed > author Gladys Hobson. Novels - poetry - short stories - ideal as > Christmas stocking fillers. Some available as e-books. > > _______________________________________________ > Xen-users mailing list > Xen-users@lists.xen.org > http://lists.xen.org/xen-users _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Sat Sep 15 05:15:27 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Sat, 15 Sep 2012 05:15:27 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TCkhc-0001qC-88; Sat, 15 Sep 2012 05:14:00 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TCkhb-0001q5-Gm for xen-users@lists.xensource.com; Sat, 15 Sep 2012 05:13:59 +0000 Received: from [85.158.143.99:53952] by server-1.bemta-4.messagelabs.com id 25/57-12504-69E04505; Sat, 15 Sep 2012 05:13:58 +0000 X-Env-Sender: pingh.cd@gmail.com X-Msg-Ref: server-10.tower-216.messagelabs.com!1347686037!24030334!1 X-Originating-IP: [216.139.236.26] X-SpamReason: No, hits=0.0 required=7.0 tests=ML_RADAR_SPEW_LINKS_14, spamassassin: X-StarScan-Received: X-StarScan-Version: 6.6.1.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 9789 invoked from network); 15 Sep 2012 05:13:58 -0000 Received: from sam.nabble.com (HELO sam.nabble.com) (216.139.236.26) by server-10.tower-216.messagelabs.com with AES256-SHA encrypted SMTP; 15 Sep 2012 05:13:58 -0000 Received: from [192.168.236.26] (helo=sam.nabble.com) by sam.nabble.com with esmtp (Exim 4.72) (envelope-from ) id 1TCkhY-0001Au-DC for xen-users@lists.xensource.com; Fri, 14 Sep 2012 22:13:56 -0700 Date: Fri, 14 Sep 2012 22:13:56 -0700 (PDT) From: Robin hp To: xen-users@lists.xensource.com Message-ID: <1347686036401-5711286.post@n5.nabble.com> In-Reply-To: <1347611471854-5711212.post@n5.nabble.com> References: <1347611471854-5711212.post@n5.nabble.com> MIME-Version: 1.0 Subject: Re: [Xen-users] Performance of PVM and HVM X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org more details: Physical machine: cpu-I5 3.1G, RAM 16G -- View this message in context: http://xen.1045712.n5.nabble.com/Performance-of-PVM-and-HVM-tp5711212p5711286.html Sent from the Xen - User mailing list archive at Nabble.com. _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Sat Sep 15 05:15:27 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Sat, 15 Sep 2012 05:15:27 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TCkhc-0001qC-88; Sat, 15 Sep 2012 05:14:00 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TCkhb-0001q5-Gm for xen-users@lists.xensource.com; Sat, 15 Sep 2012 05:13:59 +0000 Received: from [85.158.143.99:53952] by server-1.bemta-4.messagelabs.com id 25/57-12504-69E04505; Sat, 15 Sep 2012 05:13:58 +0000 X-Env-Sender: pingh.cd@gmail.com X-Msg-Ref: server-10.tower-216.messagelabs.com!1347686037!24030334!1 X-Originating-IP: [216.139.236.26] X-SpamReason: No, hits=0.0 required=7.0 tests=ML_RADAR_SPEW_LINKS_14, spamassassin: X-StarScan-Received: X-StarScan-Version: 6.6.1.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 9789 invoked from network); 15 Sep 2012 05:13:58 -0000 Received: from sam.nabble.com (HELO sam.nabble.com) (216.139.236.26) by server-10.tower-216.messagelabs.com with AES256-SHA encrypted SMTP; 15 Sep 2012 05:13:58 -0000 Received: from [192.168.236.26] (helo=sam.nabble.com) by sam.nabble.com with esmtp (Exim 4.72) (envelope-from ) id 1TCkhY-0001Au-DC for xen-users@lists.xensource.com; Fri, 14 Sep 2012 22:13:56 -0700 Date: Fri, 14 Sep 2012 22:13:56 -0700 (PDT) From: Robin hp To: xen-users@lists.xensource.com Message-ID: <1347686036401-5711286.post@n5.nabble.com> In-Reply-To: <1347611471854-5711212.post@n5.nabble.com> References: <1347611471854-5711212.post@n5.nabble.com> MIME-Version: 1.0 Subject: Re: [Xen-users] Performance of PVM and HVM X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org more details: Physical machine: cpu-I5 3.1G, RAM 16G -- View this message in context: http://xen.1045712.n5.nabble.com/Performance-of-PVM-and-HVM-tp5711212p5711286.html Sent from the Xen - User mailing list archive at Nabble.com. _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Sat Sep 15 06:01:02 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Sat, 15 Sep 2012 06:01:02 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TClQ6-0002Fi-25; Sat, 15 Sep 2012 05:59:58 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TClQ4-0002Fd-Hy for xen-users@lists.xen.org; Sat, 15 Sep 2012 05:59:56 +0000 Received: from [85.158.139.211:63666] by server-9.bemta-5.messagelabs.com id CC/5D-20529-B5914505; Sat, 15 Sep 2012 05:59:55 +0000 X-Env-Sender: james.harper@bendigoit.com.au X-Msg-Ref: server-5.tower-206.messagelabs.com!1347688792!18601418!1 X-Originating-IP: [203.16.207.99] X-SpamReason: No, hits=0.0 required=7.0 tests= X-StarScan-Received: X-StarScan-Version: 6.6.1.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 1578 invoked from network); 15 Sep 2012 05:59:55 -0000 Received: from mail.bendigoit.com.au (HELO smtp2.bendigoit.com.au) (203.16.207.99) by server-5.tower-206.messagelabs.com with AES256-SHA encrypted SMTP; 15 Sep 2012 05:59:55 -0000 Received: from [2001:388:e000:712:a5ca:4fd3:14f:ad5d] (helo=BITCOM1.int.sbss.com.au) by smtp2.bendigoit.com.au with esmtp (Exim 4.72) (envelope-from ) id 1TClPs-0005Eo-2r; Sat, 15 Sep 2012 15:59:44 +1000 Received: from BITCOM1.int.sbss.com.au ([fe80::a5ca:4fd3:14f:ad5d]) by BITCOM1.int.sbss.com.au ([fe80::a5ca:4fd3:14f:ad5d%12]) with mapi id 14.01.0379.000; Sat, 15 Sep 2012 15:59:38 +1000 From: James Harper To: Adam Goryachev , Ian Campbell Thread-Topic: [Xen-users] Poor Windows 2003 + GPLPV performance compared to VMWare Thread-Index: AQHNkazQlsMWuA2xT0e0G95Jil+zU5eI1DCAgABVnoCAAcD6YA== Date: Sat, 15 Sep 2012 05:59:36 +0000 Message-ID: <6035A0D088A63A46850C3988ED045A4B29B9266E@BITCOM1.int.sbss.com.au> References: <5051D0C5.5070600@websitemanagers.com.au> <1347609879.24226.148.camel@zakaz.uk.xensource.com> <50532CE9.5080601@websitemanagers.com.au> In-Reply-To: <50532CE9.5080601@websitemanagers.com.au> Accept-Language: en-AU, en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [192.168.204.6] x-tm-as-product-ver: SMEX-10.2.0.2087-7.000.1014-19184.002 x-tm-as-result: No--33.091000-0.000000-31 x-tm-as-user-approved-sender: Yes x-tm-as-user-blocked-sender: No MIME-Version: 1.0 X-Really-From-Bendigo-IT: magichashvalue Cc: "xen-users@lists.xen.org" Subject: Re: [Xen-users] Poor Windows 2003 + GPLPV performance compared to VMWare X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org > > Are you certain the GPLPV drivers have taken hold and you aren't using > > emulated devices? > > Within Windows, Device Manager shows the Disk Drives as "XEV PV DISK SCSI > Disk Device", this is the newest one which it detected and installed after I > changed the config from hda to xvda. > That's definitely using GPLPV. Changing hda to xvda should have any impact on anything that GPLPV cares about. Can you confirm that you definitely are running Windows 2003 SP2? Anything prior will have a big impact on performance. James _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Sat Sep 15 06:01:02 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Sat, 15 Sep 2012 06:01:02 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TClQ6-0002Fi-25; Sat, 15 Sep 2012 05:59:58 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TClQ4-0002Fd-Hy for xen-users@lists.xen.org; Sat, 15 Sep 2012 05:59:56 +0000 Received: from [85.158.139.211:63666] by server-9.bemta-5.messagelabs.com id CC/5D-20529-B5914505; Sat, 15 Sep 2012 05:59:55 +0000 X-Env-Sender: james.harper@bendigoit.com.au X-Msg-Ref: server-5.tower-206.messagelabs.com!1347688792!18601418!1 X-Originating-IP: [203.16.207.99] X-SpamReason: No, hits=0.0 required=7.0 tests= X-StarScan-Received: X-StarScan-Version: 6.6.1.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 1578 invoked from network); 15 Sep 2012 05:59:55 -0000 Received: from mail.bendigoit.com.au (HELO smtp2.bendigoit.com.au) (203.16.207.99) by server-5.tower-206.messagelabs.com with AES256-SHA encrypted SMTP; 15 Sep 2012 05:59:55 -0000 Received: from [2001:388:e000:712:a5ca:4fd3:14f:ad5d] (helo=BITCOM1.int.sbss.com.au) by smtp2.bendigoit.com.au with esmtp (Exim 4.72) (envelope-from ) id 1TClPs-0005Eo-2r; Sat, 15 Sep 2012 15:59:44 +1000 Received: from BITCOM1.int.sbss.com.au ([fe80::a5ca:4fd3:14f:ad5d]) by BITCOM1.int.sbss.com.au ([fe80::a5ca:4fd3:14f:ad5d%12]) with mapi id 14.01.0379.000; Sat, 15 Sep 2012 15:59:38 +1000 From: James Harper To: Adam Goryachev , Ian Campbell Thread-Topic: [Xen-users] Poor Windows 2003 + GPLPV performance compared to VMWare Thread-Index: AQHNkazQlsMWuA2xT0e0G95Jil+zU5eI1DCAgABVnoCAAcD6YA== Date: Sat, 15 Sep 2012 05:59:36 +0000 Message-ID: <6035A0D088A63A46850C3988ED045A4B29B9266E@BITCOM1.int.sbss.com.au> References: <5051D0C5.5070600@websitemanagers.com.au> <1347609879.24226.148.camel@zakaz.uk.xensource.com> <50532CE9.5080601@websitemanagers.com.au> In-Reply-To: <50532CE9.5080601@websitemanagers.com.au> Accept-Language: en-AU, en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [192.168.204.6] x-tm-as-product-ver: SMEX-10.2.0.2087-7.000.1014-19184.002 x-tm-as-result: No--33.091000-0.000000-31 x-tm-as-user-approved-sender: Yes x-tm-as-user-blocked-sender: No MIME-Version: 1.0 X-Really-From-Bendigo-IT: magichashvalue Cc: "xen-users@lists.xen.org" Subject: Re: [Xen-users] Poor Windows 2003 + GPLPV performance compared to VMWare X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org > > Are you certain the GPLPV drivers have taken hold and you aren't using > > emulated devices? > > Within Windows, Device Manager shows the Disk Drives as "XEV PV DISK SCSI > Disk Device", this is the newest one which it detected and installed after I > changed the config from hda to xvda. > That's definitely using GPLPV. Changing hda to xvda should have any impact on anything that GPLPV cares about. Can you confirm that you definitely are running Windows 2003 SP2? Anything prior will have a big impact on performance. James _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Sat Sep 15 17:49:52 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Sat, 15 Sep 2012 17:49:52 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TCwTc-0007B3-Va; Sat, 15 Sep 2012 17:48:20 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TCwTb-0007Ay-9t for xen-users@lists.xen.org; Sat, 15 Sep 2012 17:48:19 +0000 Received: from [85.158.137.99:11505] by server-4.bemta-3.messagelabs.com id CF/5E-24831-26FB4505; Sat, 15 Sep 2012 17:48:18 +0000 X-Env-Sender: jasonkobrien@gmail.com X-Msg-Ref: server-7.tower-217.messagelabs.com!1347731297!13021367!1 X-Originating-IP: [209.85.214.45] X-SpamReason: No, hits=0.6 required=7.0 tests=MAILTO_TO_SPAM_ADDR, RCVD_BY_IP X-StarScan-Received: X-StarScan-Version: 6.6.1.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 19060 invoked from network); 15 Sep 2012 17:48:17 -0000 Received: from mail-bk0-f45.google.com (HELO mail-bk0-f45.google.com) (209.85.214.45) by server-7.tower-217.messagelabs.com with RC4-SHA encrypted SMTP; 15 Sep 2012 17:48:17 -0000 Received: by bkcji1 with SMTP id ji1so1592526bkc.32 for ; Sat, 15 Sep 2012 10:48:17 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:content-type; bh=1EQR7tuzgV9VkNrOvUFa/xqQbNM+9Y/HvSzaUsgEJ24=; b=YSNFWDvhyxT19KKcMVy0ThQ+dJKNT5jwfuGGfWezaoWrI4GweJQAVxHmV4TIeA2ifv rgoEN9fSuTZDhFxgWWveGHamClOEKgKUTrJGEtR7XhdS75zVcm/ZVnEfyaExm2hrZ+/l hu877q3vS7SObm1EqoOblmvRHs3kXVucZNLEg3NKJCPdMIueYZ/JbHdEDfiOsGy3yOeL QBXrlhMFLCjWbcUnZk4uCWP82uN7Rh1QexH0RVuv6zlPXcih1+jjFF9AG0zehcahI238 TfNVAtAzkyGu5Uw/lXbyC6S0M11M+jcRRBHqBYalry/WdYRD+Da8ApSimDo59N5k2U+O xEWg== MIME-Version: 1.0 Received: by 10.204.129.24 with SMTP id m24mr2863992bks.134.1347731297290; Sat, 15 Sep 2012 10:48:17 -0700 (PDT) Received: by 10.205.33.10 with HTTP; Sat, 15 Sep 2012 10:48:17 -0700 (PDT) In-Reply-To: References: Date: Sat, 15 Sep 2012 13:48:17 -0400 X-Google-Sender-Auth: x_2wHjHQmhN79vbWjJro9i_Sbfo Message-ID: From: "Jason O'Brien" To: xen-users@lists.xen.org Subject: Re: [Xen-users] Can't pass through onboard Intel HDA, works in KVM X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org On Sat, Sep 1, 2012 at 7:54 PM, Jason O'Brien wrote: > With the kernel option 'xen-pciback.hide=(00:14.2) > xen-pciback.permissive', Xen-4.2.0-rc3 is unable to pass through my > onboard Intel HDA audio adapter to a Windows7 guest. I tried doing the > same in KVM and it worked immediately without issue. On the guest, I > get a "High Definition Audio Controller" with the correct > vendor/device ID, and an error of "This device cannot start. (Code > 10)". I've tried a bunch of combinations, including late binding to > pciback, with no luck. > > Has anyone seen this before? It seems to be the only thing that won't > work.. secondary passthrough of my AMD HD6850 in Xen works great (but > not in KVM unfortunately), as does passing through the USB > controllers. There's another google hit for a guy with a similar > problem, but it turned out he was using pci-stub instead of pciback > (which, as the below info shows, I am not). > > Thanks for your time, > Jason > I went ahead and tested this on kernel 3.4.6 (vs 3.5.2, which is what I was running) and it works fine, so this is likely a PCI passthrough regression in kernel 3.5. The patch on the xen-devel thread didn't do the trick for me, I'll give reverting the questionable commit a try. _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Sat Sep 15 17:49:52 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Sat, 15 Sep 2012 17:49:52 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TCwTc-0007B3-Va; Sat, 15 Sep 2012 17:48:20 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TCwTb-0007Ay-9t for xen-users@lists.xen.org; Sat, 15 Sep 2012 17:48:19 +0000 Received: from [85.158.137.99:11505] by server-4.bemta-3.messagelabs.com id CF/5E-24831-26FB4505; Sat, 15 Sep 2012 17:48:18 +0000 X-Env-Sender: jasonkobrien@gmail.com X-Msg-Ref: server-7.tower-217.messagelabs.com!1347731297!13021367!1 X-Originating-IP: [209.85.214.45] X-SpamReason: No, hits=0.6 required=7.0 tests=MAILTO_TO_SPAM_ADDR, RCVD_BY_IP X-StarScan-Received: X-StarScan-Version: 6.6.1.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 19060 invoked from network); 15 Sep 2012 17:48:17 -0000 Received: from mail-bk0-f45.google.com (HELO mail-bk0-f45.google.com) (209.85.214.45) by server-7.tower-217.messagelabs.com with RC4-SHA encrypted SMTP; 15 Sep 2012 17:48:17 -0000 Received: by bkcji1 with SMTP id ji1so1592526bkc.32 for ; Sat, 15 Sep 2012 10:48:17 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:content-type; bh=1EQR7tuzgV9VkNrOvUFa/xqQbNM+9Y/HvSzaUsgEJ24=; b=YSNFWDvhyxT19KKcMVy0ThQ+dJKNT5jwfuGGfWezaoWrI4GweJQAVxHmV4TIeA2ifv rgoEN9fSuTZDhFxgWWveGHamClOEKgKUTrJGEtR7XhdS75zVcm/ZVnEfyaExm2hrZ+/l hu877q3vS7SObm1EqoOblmvRHs3kXVucZNLEg3NKJCPdMIueYZ/JbHdEDfiOsGy3yOeL QBXrlhMFLCjWbcUnZk4uCWP82uN7Rh1QexH0RVuv6zlPXcih1+jjFF9AG0zehcahI238 TfNVAtAzkyGu5Uw/lXbyC6S0M11M+jcRRBHqBYalry/WdYRD+Da8ApSimDo59N5k2U+O xEWg== MIME-Version: 1.0 Received: by 10.204.129.24 with SMTP id m24mr2863992bks.134.1347731297290; Sat, 15 Sep 2012 10:48:17 -0700 (PDT) Received: by 10.205.33.10 with HTTP; Sat, 15 Sep 2012 10:48:17 -0700 (PDT) In-Reply-To: References: Date: Sat, 15 Sep 2012 13:48:17 -0400 X-Google-Sender-Auth: x_2wHjHQmhN79vbWjJro9i_Sbfo Message-ID: From: "Jason O'Brien" To: xen-users@lists.xen.org Subject: Re: [Xen-users] Can't pass through onboard Intel HDA, works in KVM X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org On Sat, Sep 1, 2012 at 7:54 PM, Jason O'Brien wrote: > With the kernel option 'xen-pciback.hide=(00:14.2) > xen-pciback.permissive', Xen-4.2.0-rc3 is unable to pass through my > onboard Intel HDA audio adapter to a Windows7 guest. I tried doing the > same in KVM and it worked immediately without issue. On the guest, I > get a "High Definition Audio Controller" with the correct > vendor/device ID, and an error of "This device cannot start. (Code > 10)". I've tried a bunch of combinations, including late binding to > pciback, with no luck. > > Has anyone seen this before? It seems to be the only thing that won't > work.. secondary passthrough of my AMD HD6850 in Xen works great (but > not in KVM unfortunately), as does passing through the USB > controllers. There's another google hit for a guy with a similar > problem, but it turned out he was using pci-stub instead of pciback > (which, as the below info shows, I am not). > > Thanks for your time, > Jason > I went ahead and tested this on kernel 3.4.6 (vs 3.5.2, which is what I was running) and it works fine, so this is likely a PCI passthrough regression in kernel 3.5. The patch on the xen-devel thread didn't do the trick for me, I'll give reverting the questionable commit a try. _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Sun Sep 16 12:24:55 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Sun, 16 Sep 2012 12:24:55 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TDDst-0001Nf-2R; Sun, 16 Sep 2012 12:23:35 +0000 Received: from mail27.messagelabs.com ([193.109.254.147]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TDDsr-0001Na-GP for xen-users@lists.xensource.com; Sun, 16 Sep 2012 12:23:33 +0000 X-Env-Sender: andy@strugglers.net X-Msg-Ref: server-13.tower-27.messagelabs.com!1347798207!10104218!1 X-Originating-IP: [85.119.80.223] X-SpamReason: No, hits=0.5 required=7.0 tests=BODY_RANDOM_LONG X-StarScan-Received: X-StarScan-Version: 6.6.1.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 22418 invoked from network); 16 Sep 2012 12:23:27 -0000 Received: from bitfolk.com (HELO mail.bitfolk.com) (85.119.80.223) by server-13.tower-27.messagelabs.com with AES256-SHA encrypted SMTP; 16 Sep 2012 12:23:27 -0000 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=bitfolk.com; s=alpha; h=Subject:Content-Type:MIME-Version:Message-ID:To:From:Date; bh=f1qeZjeGHxKuPFS/suU7JoLQobv47OZc3qXRhbUmMXY=; b=yfUP0fjewEmxtFqXfAP0zGNoQ9nCGTo+iuXJQACblNtzV2mBtu+IWKza9POv2gSTxdB7XuqpE1tiNuJ9iab8bwMrLvdnZuRJWdIaUzE8V2WItb2SK/4RW+YBcyTU25Bz; Received: from andy by mail.bitfolk.com with local (Exim 4.72) (envelope-from ) id 1TDDsk-0006pr-5R for xen-users@lists.xensource.com; Sun, 16 Sep 2012 12:23:26 +0000 Date: Sun, 16 Sep 2012 12:23:26 +0000 From: Andy Smith To: xen-users@lists.xensource.com Message-ID: <20120916122326.GA3867@bitfolk.com> MIME-Version: 1.0 Content-Disposition: inline OpenPGP: id=BF15490B; url=http://strugglers.net/~andy/pubkey.asc X-URL: http://strugglers.net/wiki/User:Andy User-Agent: Mutt/1.5.20 (2009-06-14) X-Virus-Scanner: Scanned by ClamAV on mail.bitfolk.com at Sun, 16 Sep 2012 12:23:26 +0000 X-SA-Exim-Connect-IP: X-SA-Exim-Mail-From: andy@strugglers.net X-Spam-Checker-Version: SpamAssassin 3.3.1 (2010-03-16) on spamd3.lon.bitfolk.com X-Spam-Level: X-Spam-ASN: X-Spam-Status: No, score=-0.0 required=5.0 tests=NO_RELAYS shortcircuit=no autolearn=disabled version=3.3.1 X-Spam-Report: * -0.0 NO_RELAYS Informational: message was not relayed via SMTP X-SA-Exim-Version: 4.2.1 (built Mon, 22 Mar 2010 06:51:10 +0000) X-SA-Exim-Scanned: Yes (on mail.bitfolk.com) Subject: [Xen-users] How are you measuring CPU usage? X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org Hello, Recently I've received some complaints that there is excessive but intermittent latency of network traffic to domUs on some of my servers. Upon investigation it seems that on some servers, indeed traffic is occasionally delayed by up to 140ms where something like 5ms RTT would be expected. The average RTT is not unusual; since this is only occasional packets it only affects the worst case and standard deviation. What seems likely is that these servers are overloaded for CPU. I have tried the various tweaks of the credit scheduler but the fact remains that the credit scheduler has a 30ms time slice, so I believe that when the server is so loaded that domUs are competing for CPU time, I could expect that a CPU hog gets the CPu for 30ms before handing over to a non-hog who gets a 30ms penalty on an RTT measurement. Clearly the answer is to not overload the servers, and it's one I completely agree with. However, I am not sure how best to measure this. I do not have control over what the domUs do, so their CPU usage profile can change. I need to monitor this in order to know when I need to move or restrict a domU. I need to know when there is actual overloading taking place, without having to measure network traffic RTT. For a long while I've been measuring CPU usage for the entirety of a physical piece of hardware by watching the CPU time counters as displayed by "xm list --long". By feeding that into stats software like MRTG or Cacti, that gives me the time used per period which in turn gives me the percentage of CPU used by every domU and the dom0. Using the above method, one of my possibly overloaded servers shows about 87% average CPU usage. Up until now, I thought that was acceptable. I think the problem is that this is based on 5 minute averages. Notably the problems most often happen at the top of the hour and on 5 minute intervals, and also at 4am. Sounds like typical cron job frequencies, right? It's not caused by cron jobs on the dom0 (there are almost none, and I disabled them all to verify). I'm thinking that at the top of the hour and sometimes at 5 minute intervals there are several domUs competing for CPU for a short amount of time, and not getting it. This is being averaged away over the 5 minute span so as to appear reasonable even though it's actually causing some problems. So, how are other people monitoring their CPU usage? Are you doing more frequent polls such as every minute or even more frequent than that? Is there a better way to read a domU's CPU time counter than parsing the output of "xm list --long"? Is it available cheaply from somewhere in /sys or is there an API or anything? Cheers, Andy _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Sun Sep 16 12:24:55 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Sun, 16 Sep 2012 12:24:55 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TDDst-0001Nf-2R; Sun, 16 Sep 2012 12:23:35 +0000 Received: from mail27.messagelabs.com ([193.109.254.147]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TDDsr-0001Na-GP for xen-users@lists.xensource.com; Sun, 16 Sep 2012 12:23:33 +0000 X-Env-Sender: andy@strugglers.net X-Msg-Ref: server-13.tower-27.messagelabs.com!1347798207!10104218!1 X-Originating-IP: [85.119.80.223] X-SpamReason: No, hits=0.5 required=7.0 tests=BODY_RANDOM_LONG X-StarScan-Received: X-StarScan-Version: 6.6.1.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 22418 invoked from network); 16 Sep 2012 12:23:27 -0000 Received: from bitfolk.com (HELO mail.bitfolk.com) (85.119.80.223) by server-13.tower-27.messagelabs.com with AES256-SHA encrypted SMTP; 16 Sep 2012 12:23:27 -0000 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=bitfolk.com; s=alpha; h=Subject:Content-Type:MIME-Version:Message-ID:To:From:Date; bh=f1qeZjeGHxKuPFS/suU7JoLQobv47OZc3qXRhbUmMXY=; b=yfUP0fjewEmxtFqXfAP0zGNoQ9nCGTo+iuXJQACblNtzV2mBtu+IWKza9POv2gSTxdB7XuqpE1tiNuJ9iab8bwMrLvdnZuRJWdIaUzE8V2WItb2SK/4RW+YBcyTU25Bz; Received: from andy by mail.bitfolk.com with local (Exim 4.72) (envelope-from ) id 1TDDsk-0006pr-5R for xen-users@lists.xensource.com; Sun, 16 Sep 2012 12:23:26 +0000 Date: Sun, 16 Sep 2012 12:23:26 +0000 From: Andy Smith To: xen-users@lists.xensource.com Message-ID: <20120916122326.GA3867@bitfolk.com> MIME-Version: 1.0 Content-Disposition: inline OpenPGP: id=BF15490B; url=http://strugglers.net/~andy/pubkey.asc X-URL: http://strugglers.net/wiki/User:Andy User-Agent: Mutt/1.5.20 (2009-06-14) X-Virus-Scanner: Scanned by ClamAV on mail.bitfolk.com at Sun, 16 Sep 2012 12:23:26 +0000 X-SA-Exim-Connect-IP: X-SA-Exim-Mail-From: andy@strugglers.net X-Spam-Checker-Version: SpamAssassin 3.3.1 (2010-03-16) on spamd3.lon.bitfolk.com X-Spam-Level: X-Spam-ASN: X-Spam-Status: No, score=-0.0 required=5.0 tests=NO_RELAYS shortcircuit=no autolearn=disabled version=3.3.1 X-Spam-Report: * -0.0 NO_RELAYS Informational: message was not relayed via SMTP X-SA-Exim-Version: 4.2.1 (built Mon, 22 Mar 2010 06:51:10 +0000) X-SA-Exim-Scanned: Yes (on mail.bitfolk.com) Subject: [Xen-users] How are you measuring CPU usage? X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org Hello, Recently I've received some complaints that there is excessive but intermittent latency of network traffic to domUs on some of my servers. Upon investigation it seems that on some servers, indeed traffic is occasionally delayed by up to 140ms where something like 5ms RTT would be expected. The average RTT is not unusual; since this is only occasional packets it only affects the worst case and standard deviation. What seems likely is that these servers are overloaded for CPU. I have tried the various tweaks of the credit scheduler but the fact remains that the credit scheduler has a 30ms time slice, so I believe that when the server is so loaded that domUs are competing for CPU time, I could expect that a CPU hog gets the CPu for 30ms before handing over to a non-hog who gets a 30ms penalty on an RTT measurement. Clearly the answer is to not overload the servers, and it's one I completely agree with. However, I am not sure how best to measure this. I do not have control over what the domUs do, so their CPU usage profile can change. I need to monitor this in order to know when I need to move or restrict a domU. I need to know when there is actual overloading taking place, without having to measure network traffic RTT. For a long while I've been measuring CPU usage for the entirety of a physical piece of hardware by watching the CPU time counters as displayed by "xm list --long". By feeding that into stats software like MRTG or Cacti, that gives me the time used per period which in turn gives me the percentage of CPU used by every domU and the dom0. Using the above method, one of my possibly overloaded servers shows about 87% average CPU usage. Up until now, I thought that was acceptable. I think the problem is that this is based on 5 minute averages. Notably the problems most often happen at the top of the hour and on 5 minute intervals, and also at 4am. Sounds like typical cron job frequencies, right? It's not caused by cron jobs on the dom0 (there are almost none, and I disabled them all to verify). I'm thinking that at the top of the hour and sometimes at 5 minute intervals there are several domUs competing for CPU for a short amount of time, and not getting it. This is being averaged away over the 5 minute span so as to appear reasonable even though it's actually causing some problems. So, how are other people monitoring their CPU usage? Are you doing more frequent polls such as every minute or even more frequent than that? Is there a better way to read a domU's CPU time counter than parsing the output of "xm list --long"? Is it available cheaply from somewhere in /sys or is there an API or anything? Cheers, Andy _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Sun Sep 16 13:05:39 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Sun, 16 Sep 2012 13:05:39 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TDEW5-0001p8-LW; Sun, 16 Sep 2012 13:04:05 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TDDLK-0000xz-1P for xen-users@lists.xen.org; Sun, 16 Sep 2012 11:48:54 +0000 Received: from [85.158.137.99:16014] by server-3.bemta-3.messagelabs.com id 54/83-21322-5ACB5505; Sun, 16 Sep 2012 11:48:53 +0000 X-Env-Sender: me@eddy-ilg.net X-Msg-Ref: server-13.tower-217.messagelabs.com!1347796132!17887720!1 X-Originating-IP: [5.9.53.202] X-SpamReason: No, hits=0.2 required=7.0 tests=RCVD_ILLEGAL_IP X-StarScan-Received: X-StarScan-Version: 6.6.1.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 23257 invoked from network); 16 Sep 2012 11:48:52 -0000 Received: from mail.univation.de (HELO mail.univation.de) (5.9.53.202) by server-13.tower-217.messagelabs.com with SMTP; 16 Sep 2012 11:48:52 -0000 Received: from localhost (localhost [127.0.0.1]) by mail.univation.de (Postfix) with ESMTP id 8F01018C60 for ; Sun, 16 Sep 2012 13:48:52 +0200 (CEST) X-Virus-Scanned: Debian amavisd-new at mail.univation.de Received: from mail.univation.de ([5.9.53.202]) by localhost (mail.univation.de [127.0.0.1]) (amavisd-new, port 10024) with LMTP id zv+eTdfJpOal for ; Sun, 16 Sep 2012 13:48:51 +0200 (CEST) Received: from [192.168.2.32] (p5B13AB54.dip.t-dialin.net [91.19.171.84]) (Authenticated sender: eddy-ilg) by mail.univation.de (Postfix) with ESMTPSA id D1039BED4 for ; Sun, 16 Sep 2012 13:48:50 +0200 (CEST) Message-ID: <5055BCA9.7010206@eddy-ilg.net> Date: Sun, 16 Sep 2012 13:48:57 +0200 From: Eddy Ilg User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:15.0) Gecko/20120907 Thunderbird/15.0.1 MIME-Version: 1.0 To: xen-users@lists.xen.org X-Mailman-Approved-At: Sun, 16 Sep 2012 13:04:04 +0000 Subject: [Xen-users] xen-hypervisor and dynamic memory? X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list Reply-To: me@eddy-ilg.net List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset="us-ascii"; Format="flowed" Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org Dear Xen List, I am new to xen and have successfully setup a dom-0 and some dom-Us. The only drawback is that I'd like to assign a fixed minimum amount of memory to the dom-Us and allow them to make dynamic use of still available memory (like a memory pool). Is this possible at all with xen-hypervisor? (I didn't find any solutions) Best regards, Eddy _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Sun Sep 16 13:05:39 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Sun, 16 Sep 2012 13:05:39 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TDEW5-0001p8-LW; Sun, 16 Sep 2012 13:04:05 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TDDLK-0000xz-1P for xen-users@lists.xen.org; Sun, 16 Sep 2012 11:48:54 +0000 Received: from [85.158.137.99:16014] by server-3.bemta-3.messagelabs.com id 54/83-21322-5ACB5505; Sun, 16 Sep 2012 11:48:53 +0000 X-Env-Sender: me@eddy-ilg.net X-Msg-Ref: server-13.tower-217.messagelabs.com!1347796132!17887720!1 X-Originating-IP: [5.9.53.202] X-SpamReason: No, hits=0.2 required=7.0 tests=RCVD_ILLEGAL_IP X-StarScan-Received: X-StarScan-Version: 6.6.1.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 23257 invoked from network); 16 Sep 2012 11:48:52 -0000 Received: from mail.univation.de (HELO mail.univation.de) (5.9.53.202) by server-13.tower-217.messagelabs.com with SMTP; 16 Sep 2012 11:48:52 -0000 Received: from localhost (localhost [127.0.0.1]) by mail.univation.de (Postfix) with ESMTP id 8F01018C60 for ; Sun, 16 Sep 2012 13:48:52 +0200 (CEST) X-Virus-Scanned: Debian amavisd-new at mail.univation.de Received: from mail.univation.de ([5.9.53.202]) by localhost (mail.univation.de [127.0.0.1]) (amavisd-new, port 10024) with LMTP id zv+eTdfJpOal for ; Sun, 16 Sep 2012 13:48:51 +0200 (CEST) Received: from [192.168.2.32] (p5B13AB54.dip.t-dialin.net [91.19.171.84]) (Authenticated sender: eddy-ilg) by mail.univation.de (Postfix) with ESMTPSA id D1039BED4 for ; Sun, 16 Sep 2012 13:48:50 +0200 (CEST) Message-ID: <5055BCA9.7010206@eddy-ilg.net> Date: Sun, 16 Sep 2012 13:48:57 +0200 From: Eddy Ilg User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:15.0) Gecko/20120907 Thunderbird/15.0.1 MIME-Version: 1.0 To: xen-users@lists.xen.org X-Mailman-Approved-At: Sun, 16 Sep 2012 13:04:04 +0000 Subject: [Xen-users] xen-hypervisor and dynamic memory? X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list Reply-To: me@eddy-ilg.net List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset="us-ascii"; Format="flowed" Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org Dear Xen List, I am new to xen and have successfully setup a dom-0 and some dom-Us. The only drawback is that I'd like to assign a fixed minimum amount of memory to the dom-Us and allow them to make dynamic use of still available memory (like a memory pool). Is this possible at all with xen-hypervisor? (I didn't find any solutions) Best regards, Eddy _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Sun Sep 16 13:20:34 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Sun, 16 Sep 2012 13:20:34 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TDEkb-0002BM-C9; Sun, 16 Sep 2012 13:19:05 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TDEka-0002BF-8t for xen-users@lists.xen.org; Sun, 16 Sep 2012 13:19:04 +0000 Received: from [85.158.139.83:46770] by server-4.bemta-5.messagelabs.com id 69/14-23042-7C1D5505; Sun, 16 Sep 2012 13:19:03 +0000 X-Env-Sender: fajar@fajar.net X-Msg-Ref: server-13.tower-182.messagelabs.com!1347801541!30186126!1 X-Originating-IP: [209.85.219.45] X-SpamReason: No, hits=0.3 required=7.0 tests=RCVD_BY_IP X-StarScan-Received: X-StarScan-Version: 6.6.1.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 13743 invoked from network); 16 Sep 2012 13:19:02 -0000 Received: from mail-oa0-f45.google.com (HELO mail-oa0-f45.google.com) (209.85.219.45) by server-13.tower-182.messagelabs.com with RC4-SHA encrypted SMTP; 16 Sep 2012 13:19:02 -0000 Received: by oagn12 with SMTP id n12so5018504oag.32 for ; Sun, 16 Sep 2012 06:19:01 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:x-gm-message-state; bh=AnJN7OTV6zmMrn0ydIwzj09eroR4/CKZRg9/QrRbFZc=; b=jPZ2DHNBD/OSbwDdIyz9+iljbQj2ScoNSEwvMcoWS6rsa+d/TFmpd8Hjj4LN4jBnGy 86+kJxS2iaBvdQFV9blPrNTvMGlttml7G4P6RTU9kwTVXSeWUgPUQLl3DTamljmG7ZVk PvE77O6R6g3VtyDY2YIlTLY5WOWv6akN6CnFJEz/ZSaXbWrVzKILcVYS2ne/JRpLH9uF aUA0ACI2UyWT7VVlR6JvJoxKY8K+c3f4PK5M8zivsIlhpFPVxh9zdys0IyKUbhU9k/UI Cmal12XWUsTTRbC9bQFQBGPfaOXSA1uNKlZMcy6As8IwxBG8HJU/tcvm2MNhbTdOvdaT yAug== MIME-Version: 1.0 Received: by 10.182.202.39 with SMTP id kf7mr9379829obc.37.1347801541310; Sun, 16 Sep 2012 06:19:01 -0700 (PDT) Received: by 10.60.6.230 with HTTP; Sun, 16 Sep 2012 06:19:01 -0700 (PDT) In-Reply-To: <5055BCA9.7010206@eddy-ilg.net> References: <5055BCA9.7010206@eddy-ilg.net> Date: Sun, 16 Sep 2012 20:19:01 +0700 Message-ID: From: "Fajar A. Nugraha" To: me@eddy-ilg.net X-Gm-Message-State: ALoCoQnNWqDgaMXibHHtG2cwt6AA3Q0SAP/RA+ep6WkQEK67zfq5kq4UUpN0lAHkO8rjzHAaNU7f Cc: xen-users@lists.xen.org Subject: Re: [Xen-users] xen-hypervisor and dynamic memory? X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org On Sun, Sep 16, 2012 at 6:48 PM, Eddy Ilg wrote: > Dear Xen List, > > > I am new to xen and have successfully setup a dom-0 and some dom-Us. The > only drawback is that I'd like to assign a fixed minimum amount of memory to > the dom-Us and allow them to make dynamic use of still available memory > (like a memory pool). > > Is this possible at all with xen-hypervisor? (I didn't find any solutions) Short answer: no. Long answer: probably yes, if you use tmem-enabled kernels. This thread (and the links in it) probably gives most info: http://xen.1045712.n5.nabble.com/Transcendent-Memory-quot-tmem-quot-capable-kernel-now-publicly-released-td5587302.html -- Fajar _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Sun Sep 16 13:20:34 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Sun, 16 Sep 2012 13:20:34 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TDEkb-0002BM-C9; Sun, 16 Sep 2012 13:19:05 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TDEka-0002BF-8t for xen-users@lists.xen.org; Sun, 16 Sep 2012 13:19:04 +0000 Received: from [85.158.139.83:46770] by server-4.bemta-5.messagelabs.com id 69/14-23042-7C1D5505; Sun, 16 Sep 2012 13:19:03 +0000 X-Env-Sender: fajar@fajar.net X-Msg-Ref: server-13.tower-182.messagelabs.com!1347801541!30186126!1 X-Originating-IP: [209.85.219.45] X-SpamReason: No, hits=0.3 required=7.0 tests=RCVD_BY_IP X-StarScan-Received: X-StarScan-Version: 6.6.1.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 13743 invoked from network); 16 Sep 2012 13:19:02 -0000 Received: from mail-oa0-f45.google.com (HELO mail-oa0-f45.google.com) (209.85.219.45) by server-13.tower-182.messagelabs.com with RC4-SHA encrypted SMTP; 16 Sep 2012 13:19:02 -0000 Received: by oagn12 with SMTP id n12so5018504oag.32 for ; Sun, 16 Sep 2012 06:19:01 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:x-gm-message-state; bh=AnJN7OTV6zmMrn0ydIwzj09eroR4/CKZRg9/QrRbFZc=; b=jPZ2DHNBD/OSbwDdIyz9+iljbQj2ScoNSEwvMcoWS6rsa+d/TFmpd8Hjj4LN4jBnGy 86+kJxS2iaBvdQFV9blPrNTvMGlttml7G4P6RTU9kwTVXSeWUgPUQLl3DTamljmG7ZVk PvE77O6R6g3VtyDY2YIlTLY5WOWv6akN6CnFJEz/ZSaXbWrVzKILcVYS2ne/JRpLH9uF aUA0ACI2UyWT7VVlR6JvJoxKY8K+c3f4PK5M8zivsIlhpFPVxh9zdys0IyKUbhU9k/UI Cmal12XWUsTTRbC9bQFQBGPfaOXSA1uNKlZMcy6As8IwxBG8HJU/tcvm2MNhbTdOvdaT yAug== MIME-Version: 1.0 Received: by 10.182.202.39 with SMTP id kf7mr9379829obc.37.1347801541310; Sun, 16 Sep 2012 06:19:01 -0700 (PDT) Received: by 10.60.6.230 with HTTP; Sun, 16 Sep 2012 06:19:01 -0700 (PDT) In-Reply-To: <5055BCA9.7010206@eddy-ilg.net> References: <5055BCA9.7010206@eddy-ilg.net> Date: Sun, 16 Sep 2012 20:19:01 +0700 Message-ID: From: "Fajar A. Nugraha" To: me@eddy-ilg.net X-Gm-Message-State: ALoCoQnNWqDgaMXibHHtG2cwt6AA3Q0SAP/RA+ep6WkQEK67zfq5kq4UUpN0lAHkO8rjzHAaNU7f Cc: xen-users@lists.xen.org Subject: Re: [Xen-users] xen-hypervisor and dynamic memory? X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org On Sun, Sep 16, 2012 at 6:48 PM, Eddy Ilg wrote: > Dear Xen List, > > > I am new to xen and have successfully setup a dom-0 and some dom-Us. The > only drawback is that I'd like to assign a fixed minimum amount of memory to > the dom-Us and allow them to make dynamic use of still available memory > (like a memory pool). > > Is this possible at all with xen-hypervisor? (I didn't find any solutions) Short answer: no. Long answer: probably yes, if you use tmem-enabled kernels. This thread (and the links in it) probably gives most info: http://xen.1045712.n5.nabble.com/Transcendent-Memory-quot-tmem-quot-capable-kernel-now-publicly-released-td5587302.html -- Fajar _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Sun Sep 16 13:52:00 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Sun, 16 Sep 2012 13:52:00 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TDFF0-0002Zb-71; Sun, 16 Sep 2012 13:50:30 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TDFEy-0002ZW-Q9 for xen-users@lists.xen.org; Sun, 16 Sep 2012 13:50:29 +0000 Received: from [85.158.137.99:54018] by server-7.bemta-3.messagelabs.com id 85/05-32000-329D5505; Sun, 16 Sep 2012 13:50:27 +0000 X-Env-Sender: dion@concero.nl X-Msg-Ref: server-13.tower-217.messagelabs.com!1347803426!17894418!1 X-Originating-IP: [80.101.154.29] X-SpamReason: No, hits=0.0 required=7.0 tests= X-StarScan-Received: X-StarScan-Version: 6.6.1.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 22942 invoked from network); 16 Sep 2012 13:50:27 -0000 Received: from concero.xs4all.nl (HELO buri.noordwolde.concero.nl) (80.101.154.29) by server-13.tower-217.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 16 Sep 2012 13:50:27 -0000 Received: from cygnus.noordwolde.concero.nl (black-hole.noordwolde.concero.nl [192.168.4.254]) (authenticated bits=0) by buri.noordwolde.concero.nl (8.13.4/8.13.4/SuSE Linux 0.7) with ESMTP id q8GDoPL6011806 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for ; Sun, 16 Sep 2012 15:50:25 +0200 Message-ID: <5055D921.1000001@concero.nl> Date: Sun, 16 Sep 2012 15:50:25 +0200 From: Dion Kant Organization: CONCERO User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.2.20) Gecko/20110804 SUSE/3.1.12 Thunderbird/3.1.12 MIME-Version: 1.0 To: xen-users@lists.xen.org References: <5051D0C5.5070600@websitemanagers.com.au> In-Reply-To: <5051D0C5.5070600@websitemanagers.com.au> X-Enigmail-Version: 1.1.2 Subject: Re: [Xen-users] Poor Windows 2003 + GPLPV performance compared to VMWare X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org Adam, Can you give it a retry with the Windows DomU running from a file container? mount another LV somewhere on dom0 (e.g. /var/lib/xen/images/windows) Use "qemu-img convert your.vmdk -O raw /var/lib/xen/images/windows/disk0.raw" to create the file container I see significant disk I/O performance improvement on all my Windows DomU's when running them from file containers as compared to running them directly from a block device. Cheers, Dion On 09/13/2012 02:25 PM, Adam Goryachev wrote: > I have an application server running on MS Windows 2003, which was a > clean install on VMWare last year (after a failed migration attempt to > XenServer). > > At this point, a benchmark (actually a live process run regularly on the > machine) produced a result of 7800 to 7900 transactions per second > > I've recently migrated this to Xen by: > 1) Uninstall VMWare tools > 2) Shutdown Windows > 3) Use VMWare to download the vmdk > 4) Write the VMDK file (dd) to the same LVM that contained the VMWare > storage area (which was exported by iSCSI to VMWare > 5) Installed Debian Testing with Xen 4.1 > 6) Using the exactl same iSCSI server/LVM config etc, started the VM > 7) Installed the GPLPV drivers > > Everything seemed to work, and all was good. > > Then, the user ran the above process, and got consistently, results of > approx 2500 transactions per second > > I increased the vcpus from 2 to 4, but this didn't change the result at all. > > I modifed the domU config for the disk line from hda to xvda, and the > result increased slightly to 2560 / sec (these tests are just one off > tests, no verification of actual performance increase etc...). > > In any case, I seem to have a significant loss of performance on the > domU when compared to VMWare. > > The storage server/network is identical > The dom0 machine is identical to the VMWare machine > > Here is my current domU config file: > > kernel = "/usr/lib/xen-4.1/boot/hvmloader" > builder = 'hvm' > memory = 4096 > shadow_memory = 12 > device_model = '/usr/lib/xen-default/bin/qemu-dm' > localtime = 1 > name = "vm1" > cpus = "2,3,4,5" # Which physical CPU's to allow > vcpus = 4 # How many Virtual CPU's to present > viridian = 1 > disk = [ > 'phy:/dev/disk/by-path/ip-10.30.10.23:3260-iscsi-iqn.2012-06.domain:vm1-lun-0,xvda,w' > ] > vif = ['bridge=xenbr0, mac=00:16:3e:39:10:1a'] > boot = 'c' > sdl = 0 > vnc = 1 > vncdisplay = 10 > vncviewer = 0 > vncconsole = 0 > vncunused = 0 > stdvga = 1 > usb = 1 > usbdevice = 'tablet' > acpi = 1 > apic = 1 > on_reboot = 'restart' > on_poweroff = 'destroy' > on_crash = 'restart' > audio = 0 > > Any suggestions on how to improve performance would be greatly appreciated. > > Thank you, > Adam > _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Sun Sep 16 13:52:00 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Sun, 16 Sep 2012 13:52:00 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TDFF0-0002Zb-71; Sun, 16 Sep 2012 13:50:30 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TDFEy-0002ZW-Q9 for xen-users@lists.xen.org; Sun, 16 Sep 2012 13:50:29 +0000 Received: from [85.158.137.99:54018] by server-7.bemta-3.messagelabs.com id 85/05-32000-329D5505; Sun, 16 Sep 2012 13:50:27 +0000 X-Env-Sender: dion@concero.nl X-Msg-Ref: server-13.tower-217.messagelabs.com!1347803426!17894418!1 X-Originating-IP: [80.101.154.29] X-SpamReason: No, hits=0.0 required=7.0 tests= X-StarScan-Received: X-StarScan-Version: 6.6.1.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 22942 invoked from network); 16 Sep 2012 13:50:27 -0000 Received: from concero.xs4all.nl (HELO buri.noordwolde.concero.nl) (80.101.154.29) by server-13.tower-217.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 16 Sep 2012 13:50:27 -0000 Received: from cygnus.noordwolde.concero.nl (black-hole.noordwolde.concero.nl [192.168.4.254]) (authenticated bits=0) by buri.noordwolde.concero.nl (8.13.4/8.13.4/SuSE Linux 0.7) with ESMTP id q8GDoPL6011806 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for ; Sun, 16 Sep 2012 15:50:25 +0200 Message-ID: <5055D921.1000001@concero.nl> Date: Sun, 16 Sep 2012 15:50:25 +0200 From: Dion Kant Organization: CONCERO User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.2.20) Gecko/20110804 SUSE/3.1.12 Thunderbird/3.1.12 MIME-Version: 1.0 To: xen-users@lists.xen.org References: <5051D0C5.5070600@websitemanagers.com.au> In-Reply-To: <5051D0C5.5070600@websitemanagers.com.au> X-Enigmail-Version: 1.1.2 Subject: Re: [Xen-users] Poor Windows 2003 + GPLPV performance compared to VMWare X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org Adam, Can you give it a retry with the Windows DomU running from a file container? mount another LV somewhere on dom0 (e.g. /var/lib/xen/images/windows) Use "qemu-img convert your.vmdk -O raw /var/lib/xen/images/windows/disk0.raw" to create the file container I see significant disk I/O performance improvement on all my Windows DomU's when running them from file containers as compared to running them directly from a block device. Cheers, Dion On 09/13/2012 02:25 PM, Adam Goryachev wrote: > I have an application server running on MS Windows 2003, which was a > clean install on VMWare last year (after a failed migration attempt to > XenServer). > > At this point, a benchmark (actually a live process run regularly on the > machine) produced a result of 7800 to 7900 transactions per second > > I've recently migrated this to Xen by: > 1) Uninstall VMWare tools > 2) Shutdown Windows > 3) Use VMWare to download the vmdk > 4) Write the VMDK file (dd) to the same LVM that contained the VMWare > storage area (which was exported by iSCSI to VMWare > 5) Installed Debian Testing with Xen 4.1 > 6) Using the exactl same iSCSI server/LVM config etc, started the VM > 7) Installed the GPLPV drivers > > Everything seemed to work, and all was good. > > Then, the user ran the above process, and got consistently, results of > approx 2500 transactions per second > > I increased the vcpus from 2 to 4, but this didn't change the result at all. > > I modifed the domU config for the disk line from hda to xvda, and the > result increased slightly to 2560 / sec (these tests are just one off > tests, no verification of actual performance increase etc...). > > In any case, I seem to have a significant loss of performance on the > domU when compared to VMWare. > > The storage server/network is identical > The dom0 machine is identical to the VMWare machine > > Here is my current domU config file: > > kernel = "/usr/lib/xen-4.1/boot/hvmloader" > builder = 'hvm' > memory = 4096 > shadow_memory = 12 > device_model = '/usr/lib/xen-default/bin/qemu-dm' > localtime = 1 > name = "vm1" > cpus = "2,3,4,5" # Which physical CPU's to allow > vcpus = 4 # How many Virtual CPU's to present > viridian = 1 > disk = [ > 'phy:/dev/disk/by-path/ip-10.30.10.23:3260-iscsi-iqn.2012-06.domain:vm1-lun-0,xvda,w' > ] > vif = ['bridge=xenbr0, mac=00:16:3e:39:10:1a'] > boot = 'c' > sdl = 0 > vnc = 1 > vncdisplay = 10 > vncviewer = 0 > vncconsole = 0 > vncunused = 0 > stdvga = 1 > usb = 1 > usbdevice = 'tablet' > acpi = 1 > apic = 1 > on_reboot = 'restart' > on_poweroff = 'destroy' > on_crash = 'restart' > audio = 0 > > Any suggestions on how to improve performance would be greatly appreciated. > > Thank you, > Adam > _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Sun Sep 16 14:48:52 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Sun, 16 Sep 2012 14:48:52 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TDG8U-00037k-1S; Sun, 16 Sep 2012 14:47:50 +0000 Received: from mail27.messagelabs.com ([193.109.254.147]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TDG8S-00037c-GI for xen-users@lists.xen.org; Sun, 16 Sep 2012 14:47:48 +0000 X-Env-Sender: rulerof@gmail.com X-Msg-Ref: server-4.tower-27.messagelabs.com!1347806861!10641218!1 X-Originating-IP: [209.85.216.173] X-SpamReason: No, hits=0.3 required=7.0 tests=ML_RADAR_SPEW_LINKS_14, RCVD_BY_IP,spamassassin: X-StarScan-Received: X-StarScan-Version: 6.6.1.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 29152 invoked from network); 16 Sep 2012 14:47:42 -0000 Received: from mail-qc0-f173.google.com (HELO mail-qc0-f173.google.com) (209.85.216.173) by server-4.tower-27.messagelabs.com with RC4-SHA encrypted SMTP; 16 Sep 2012 14:47:42 -0000 Received: by qcab12 with SMTP id b12so5211688qca.32 for ; Sun, 16 Sep 2012 07:47:41 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=from:mime-version:date:message-id:subject:to:content-type; bh=ewJDCc6sLe8M0aFAsWoyy8+o8rNwSzcTQi4QetwaSew=; b=AfBoDtHn6NiWFVfI/q1LSac4WIVMGfcf4wDXJqtXHhP9Zk+gtjfVVfFFtuYCkXri7X QgNzs96BoZTosNDgumc94Aoil3ysocGNebLgDi6Zosx8IrObM8swg714K8DxpFYwBUNL yid+KgbVMTrS3OYk8ARnrEEx9ZBblgP2rHU+jIaY9PevPB6kUS5R1bLSE8+6UcEK7whQ RScxhuDNVyHotHcuIsAuY27Hjb6RpUgmNFD9VxMzudKyNcKSLw7EcEgtBU/+puQvuMH8 60G+mgGLz7LZvmPByaOWIrotsoYT3v1KSttMMMRQstrEG6orw3cyt/lYvDYWpuQFZ/SZ Dr9g== Received: by 10.224.183.79 with SMTP id cf15mr21297605qab.16.1347806861045; Sun, 16 Sep 2012 07:47:41 -0700 (PDT) From: Andrew Bobulsky Mime-Version: 1.0 (1.0) Date: Sun, 16 Sep 2012 10:47:41 -0400 Message-ID: <-1335041117523102809@unknownmsgid> To: "dion@concero.nl" , "xen-users@lists.xen.org" Subject: [Xen-users] File container vs. raw disk mapping or others? X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org Hello Dion, and other listfolk, Regarding your email to Adam (I didn't want to thread-jack for the purpose of my question): >mount another LV somewhere on dom0 (e.g. /var/lib/xen/images/windows) >Use "qemu-img convert your.vmdk -O raw >/var/lib/xen/images/windows/disk0.raw" to create the file container >I see significant disk I/O performance improvement on all my Windows >DomU's when running them from file containers as compared to running >them directly from a block device. Is this truly the best formula you've determined for getting the best performance from a Windows DomU? I know that to ask the question is a bit like beating a dead horse, but in my time on reading the list, browsing the website, and reading the wiki, I've never come up with a clear answer, and none of my own testing has been thorough enough to answer this myself. Further, if you know, does that recommendation change if one isn't using GPLPV? Basically, should my Windows DomU storage be: block device (DAS/SAN) > LVM volume > raw disk file > DomU? Is there a different setup for optimal performance without GPLPV, or am I missing a step such as mounting the image to a loopback device and then mapping the raw loopback dev to my DomU? I recognize that it's possible that there is no clear answer due to various factors, such as Xen version, Dom0 OS, kernel, and so on, and perhaps that's why I don't have a good answer in my head either. I'm also curious if sacrificing flexibility (by omitting LVM, for example) allows for better performance to the Windows DomU.... So many questions :P Thanks, Andrew Bobulsky _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Sun Sep 16 14:48:52 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Sun, 16 Sep 2012 14:48:52 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TDG8U-00037k-1S; Sun, 16 Sep 2012 14:47:50 +0000 Received: from mail27.messagelabs.com ([193.109.254.147]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TDG8S-00037c-GI for xen-users@lists.xen.org; Sun, 16 Sep 2012 14:47:48 +0000 X-Env-Sender: rulerof@gmail.com X-Msg-Ref: server-4.tower-27.messagelabs.com!1347806861!10641218!1 X-Originating-IP: [209.85.216.173] X-SpamReason: No, hits=0.3 required=7.0 tests=ML_RADAR_SPEW_LINKS_14, RCVD_BY_IP,spamassassin: X-StarScan-Received: X-StarScan-Version: 6.6.1.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 29152 invoked from network); 16 Sep 2012 14:47:42 -0000 Received: from mail-qc0-f173.google.com (HELO mail-qc0-f173.google.com) (209.85.216.173) by server-4.tower-27.messagelabs.com with RC4-SHA encrypted SMTP; 16 Sep 2012 14:47:42 -0000 Received: by qcab12 with SMTP id b12so5211688qca.32 for ; Sun, 16 Sep 2012 07:47:41 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=from:mime-version:date:message-id:subject:to:content-type; bh=ewJDCc6sLe8M0aFAsWoyy8+o8rNwSzcTQi4QetwaSew=; b=AfBoDtHn6NiWFVfI/q1LSac4WIVMGfcf4wDXJqtXHhP9Zk+gtjfVVfFFtuYCkXri7X QgNzs96BoZTosNDgumc94Aoil3ysocGNebLgDi6Zosx8IrObM8swg714K8DxpFYwBUNL yid+KgbVMTrS3OYk8ARnrEEx9ZBblgP2rHU+jIaY9PevPB6kUS5R1bLSE8+6UcEK7whQ RScxhuDNVyHotHcuIsAuY27Hjb6RpUgmNFD9VxMzudKyNcKSLw7EcEgtBU/+puQvuMH8 60G+mgGLz7LZvmPByaOWIrotsoYT3v1KSttMMMRQstrEG6orw3cyt/lYvDYWpuQFZ/SZ Dr9g== Received: by 10.224.183.79 with SMTP id cf15mr21297605qab.16.1347806861045; Sun, 16 Sep 2012 07:47:41 -0700 (PDT) From: Andrew Bobulsky Mime-Version: 1.0 (1.0) Date: Sun, 16 Sep 2012 10:47:41 -0400 Message-ID: <-1335041117523102809@unknownmsgid> To: "dion@concero.nl" , "xen-users@lists.xen.org" Subject: [Xen-users] File container vs. raw disk mapping or others? X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org Hello Dion, and other listfolk, Regarding your email to Adam (I didn't want to thread-jack for the purpose of my question): >mount another LV somewhere on dom0 (e.g. /var/lib/xen/images/windows) >Use "qemu-img convert your.vmdk -O raw >/var/lib/xen/images/windows/disk0.raw" to create the file container >I see significant disk I/O performance improvement on all my Windows >DomU's when running them from file containers as compared to running >them directly from a block device. Is this truly the best formula you've determined for getting the best performance from a Windows DomU? I know that to ask the question is a bit like beating a dead horse, but in my time on reading the list, browsing the website, and reading the wiki, I've never come up with a clear answer, and none of my own testing has been thorough enough to answer this myself. Further, if you know, does that recommendation change if one isn't using GPLPV? Basically, should my Windows DomU storage be: block device (DAS/SAN) > LVM volume > raw disk file > DomU? Is there a different setup for optimal performance without GPLPV, or am I missing a step such as mounting the image to a loopback device and then mapping the raw loopback dev to my DomU? I recognize that it's possible that there is no clear answer due to various factors, such as Xen version, Dom0 OS, kernel, and so on, and perhaps that's why I don't have a good answer in my head either. I'm also curious if sacrificing flexibility (by omitting LVM, for example) allows for better performance to the Windows DomU.... So many questions :P Thanks, Andrew Bobulsky _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Sun Sep 16 15:27:58 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Sun, 16 Sep 2012 15:27:58 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TDGkJ-0003px-90; Sun, 16 Sep 2012 15:26:55 +0000 Received: from mail27.messagelabs.com ([193.109.254.147]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TDGkI-0003ps-B4 for xen-users@lists.xen.org; Sun, 16 Sep 2012 15:26:54 +0000 X-Env-Sender: rulerof@gmail.com X-Msg-Ref: server-2.tower-27.messagelabs.com!1347809207!11188044!1 X-Originating-IP: [209.85.216.173] X-SpamReason: No, hits=0.3 required=7.0 tests=ML_RADAR_SPEW_LINKS_14, RCVD_BY_IP,spamassassin: X-StarScan-Received: X-StarScan-Version: 6.6.1.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 3838 invoked from network); 16 Sep 2012 15:26:48 -0000 Received: from mail-qc0-f173.google.com (HELO mail-qc0-f173.google.com) (209.85.216.173) by server-2.tower-27.messagelabs.com with RC4-SHA encrypted SMTP; 16 Sep 2012 15:26:48 -0000 Received: by qcab12 with SMTP id b12so5230503qca.32 for ; Sun, 16 Sep 2012 08:26:46 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=references:from:in-reply-to:mime-version:date:message-id:subject:to :cc:content-type; bh=IbjznFVJSWgdywwP03G9AIIC7q9jmz0wz2fDJhPMVOw=; b=mTP/PifRRZHOw+N4weZ1mgaoAPAI/5Q4Y/xVyXEPKNAsyztu53XyASePYwAlULGmrt wUaY32uNb6o5ism6hrWDcRGAcshlV7+8+hf/Yuuc2WGj7jQh1/1v74AsDl587XvDhyBC IlX/swUQhCvE84oY2dTevqE1zpB4U/mdYBWKjJb9vVKda2Px4KoAZplP5NDckMAgMz6a VtLm0aEQUNwoXDNHyY34sqBnu1styGIxB40aM0z8NjYQxhjXaPcyJljU77G9jyLT4pEC ctaJdiNwzbrcXXnlWghinfztURzWlE7cv8gbdXszTnZXhyDsDzbyhfUmXSB0n+hrNwWP AowQ== Received: by 10.229.135.85 with SMTP id m21mr5786421qct.44.1347809206733; Sun, 16 Sep 2012 08:26:46 -0700 (PDT) References: <5051D0C5.5070600@websitemanagers.com.au> <1347609879.24226.148.camel@zakaz.uk.xensource.com> <50532CE9.5080601@websitemanagers.com.au> <1347629416.24226.208.camel@zakaz.uk.xensource.com> <505344E8.2030400@websitemanagers.com.au> From: Andrew Bobulsky In-Reply-To: <505344E8.2030400@websitemanagers.com.au> Mime-Version: 1.0 (1.0) Date: Sun, 16 Sep 2012 11:26:46 -0400 Message-ID: <5912014629263308793@unknownmsgid> To: Adam Goryachev Cc: "xen-users@lists.xen.org" , Ian Campbell Subject: Re: [Xen-users] Poor Windows 2003 + GPLPV performance compared to VMWare X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org Hello Adam, On Sep 14, 2012, at 10:57 AM, Adam Goryachev wrote: >>>> And as James suggests it would also be useful to benchmark iSCSI running >>>> in dom0 and perhaps even running on the same system without Xen (just >>>> Linux) using the same kernel. I'm not sure if VMware offers something >>>> similar which could be used for comparison. >>> >>> Well, that is where things start to get complicated rather quickly... >>> There are a lot of layers here, but I'd prefer to look at the issues >>> closer to xen first, since vmware was working from an identically >>> configured san/etc, so nothing at all has changed there. Ultimately, the >>> san is using 3 x SSD in RAID5. I have done various testing in the past >>> from plain linux (with older kernel 2.6.32 from debian stable) and >>> achieved reasonable figures (I don't recall exactly). >> >> I was worried about the Linux side rather than the SAN itself, but it >> sounds like you've got that covered. > > At this stage, the limiting performance should be the single gig > ethernet for the physical machine to connect to the network. (The san > side has 4 x gig ethernet). I'm finding myself fascinated with this thread you've started, lots of details going on and I'm really hopeful you figure this out. However, in case you don't, I may have a suggestion: Is it an option for you to connect this DomU to your iSCSI LUN directly? Bypass the initiator in Dom0, and the uncertainty of your disk assignment to the DomU? With Windows prior to NT6, you of course need to download from Microsoft and install the iSCSI initiator, but with that, you could create a dedicated LUN on your SAN and use that device as the backing store for your application's data. If you like the idea, try installing the initiator and connecting to a small RAM disk on your SAN (or something where you know the storage IOPs won't be a limiting factor) and benchmark the disk with IOMeter or CrystalDiskMark, compare that to the performance of the Xen-mapped disk, and see if that will yield the appropriate throughput for your needs. If you want to go deeper down the rabbit hole (so to speak), you could also try booting the DomU directly from your SAN, as Xen bundles iPXE as its HVM network boot ROM. With your DomU already existing as raw data on an iSCSI LUN, you could basically install the initiator and sanbootconf package, configure a DHCP reservation (or the ROM, if the NVRAM storage works with the Xen NIC), and boot right up. And finally, and also the deepest down the rabbit hole that I'd suggest going, if your host supports PCI passthrough *and* you have a "spare" NIC available, you could assign that NIC directly to your DomU and use my first suggestion. The DomU will be "tied" to the host at that point though, so if you're looking to leverage migration or failover, it's not a good idea :P Best of luck to you, and, while I hope you don't need my suggestions, I'd be glad to be of any assistance if you have some questions! Cheers, Andrew Bobulsky _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Sun Sep 16 15:27:58 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Sun, 16 Sep 2012 15:27:58 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TDGkJ-0003px-90; Sun, 16 Sep 2012 15:26:55 +0000 Received: from mail27.messagelabs.com ([193.109.254.147]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TDGkI-0003ps-B4 for xen-users@lists.xen.org; Sun, 16 Sep 2012 15:26:54 +0000 X-Env-Sender: rulerof@gmail.com X-Msg-Ref: server-2.tower-27.messagelabs.com!1347809207!11188044!1 X-Originating-IP: [209.85.216.173] X-SpamReason: No, hits=0.3 required=7.0 tests=ML_RADAR_SPEW_LINKS_14, RCVD_BY_IP,spamassassin: X-StarScan-Received: X-StarScan-Version: 6.6.1.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 3838 invoked from network); 16 Sep 2012 15:26:48 -0000 Received: from mail-qc0-f173.google.com (HELO mail-qc0-f173.google.com) (209.85.216.173) by server-2.tower-27.messagelabs.com with RC4-SHA encrypted SMTP; 16 Sep 2012 15:26:48 -0000 Received: by qcab12 with SMTP id b12so5230503qca.32 for ; Sun, 16 Sep 2012 08:26:46 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=references:from:in-reply-to:mime-version:date:message-id:subject:to :cc:content-type; bh=IbjznFVJSWgdywwP03G9AIIC7q9jmz0wz2fDJhPMVOw=; b=mTP/PifRRZHOw+N4weZ1mgaoAPAI/5Q4Y/xVyXEPKNAsyztu53XyASePYwAlULGmrt wUaY32uNb6o5ism6hrWDcRGAcshlV7+8+hf/Yuuc2WGj7jQh1/1v74AsDl587XvDhyBC IlX/swUQhCvE84oY2dTevqE1zpB4U/mdYBWKjJb9vVKda2Px4KoAZplP5NDckMAgMz6a VtLm0aEQUNwoXDNHyY34sqBnu1styGIxB40aM0z8NjYQxhjXaPcyJljU77G9jyLT4pEC ctaJdiNwzbrcXXnlWghinfztURzWlE7cv8gbdXszTnZXhyDsDzbyhfUmXSB0n+hrNwWP AowQ== Received: by 10.229.135.85 with SMTP id m21mr5786421qct.44.1347809206733; Sun, 16 Sep 2012 08:26:46 -0700 (PDT) References: <5051D0C5.5070600@websitemanagers.com.au> <1347609879.24226.148.camel@zakaz.uk.xensource.com> <50532CE9.5080601@websitemanagers.com.au> <1347629416.24226.208.camel@zakaz.uk.xensource.com> <505344E8.2030400@websitemanagers.com.au> From: Andrew Bobulsky In-Reply-To: <505344E8.2030400@websitemanagers.com.au> Mime-Version: 1.0 (1.0) Date: Sun, 16 Sep 2012 11:26:46 -0400 Message-ID: <5912014629263308793@unknownmsgid> To: Adam Goryachev Cc: "xen-users@lists.xen.org" , Ian Campbell Subject: Re: [Xen-users] Poor Windows 2003 + GPLPV performance compared to VMWare X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org Hello Adam, On Sep 14, 2012, at 10:57 AM, Adam Goryachev wrote: >>>> And as James suggests it would also be useful to benchmark iSCSI running >>>> in dom0 and perhaps even running on the same system without Xen (just >>>> Linux) using the same kernel. I'm not sure if VMware offers something >>>> similar which could be used for comparison. >>> >>> Well, that is where things start to get complicated rather quickly... >>> There are a lot of layers here, but I'd prefer to look at the issues >>> closer to xen first, since vmware was working from an identically >>> configured san/etc, so nothing at all has changed there. Ultimately, the >>> san is using 3 x SSD in RAID5. I have done various testing in the past >>> from plain linux (with older kernel 2.6.32 from debian stable) and >>> achieved reasonable figures (I don't recall exactly). >> >> I was worried about the Linux side rather than the SAN itself, but it >> sounds like you've got that covered. > > At this stage, the limiting performance should be the single gig > ethernet for the physical machine to connect to the network. (The san > side has 4 x gig ethernet). I'm finding myself fascinated with this thread you've started, lots of details going on and I'm really hopeful you figure this out. However, in case you don't, I may have a suggestion: Is it an option for you to connect this DomU to your iSCSI LUN directly? Bypass the initiator in Dom0, and the uncertainty of your disk assignment to the DomU? With Windows prior to NT6, you of course need to download from Microsoft and install the iSCSI initiator, but with that, you could create a dedicated LUN on your SAN and use that device as the backing store for your application's data. If you like the idea, try installing the initiator and connecting to a small RAM disk on your SAN (or something where you know the storage IOPs won't be a limiting factor) and benchmark the disk with IOMeter or CrystalDiskMark, compare that to the performance of the Xen-mapped disk, and see if that will yield the appropriate throughput for your needs. If you want to go deeper down the rabbit hole (so to speak), you could also try booting the DomU directly from your SAN, as Xen bundles iPXE as its HVM network boot ROM. With your DomU already existing as raw data on an iSCSI LUN, you could basically install the initiator and sanbootconf package, configure a DHCP reservation (or the ROM, if the NVRAM storage works with the Xen NIC), and boot right up. And finally, and also the deepest down the rabbit hole that I'd suggest going, if your host supports PCI passthrough *and* you have a "spare" NIC available, you could assign that NIC directly to your DomU and use my first suggestion. The DomU will be "tied" to the host at that point though, so if you're looking to leverage migration or failover, it's not a good idea :P Best of luck to you, and, while I hope you don't need my suggestions, I'd be glad to be of any assistance if you have some questions! Cheers, Andrew Bobulsky _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Sun Sep 16 17:29:23 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Sun, 16 Sep 2012 17:29:23 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TDIde-0005tL-Fc; Sun, 16 Sep 2012 17:28:10 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TDIdb-0005tD-Tl for xen-users@lists.xen.org; Sun, 16 Sep 2012 17:28:08 +0000 Received: from [85.158.143.99:46417] by server-1.bemta-4.messagelabs.com id D5/DE-12504-72C06505; Sun, 16 Sep 2012 17:28:07 +0000 X-Env-Sender: myrdhn@gmail.com X-Msg-Ref: server-4.tower-216.messagelabs.com!1347816485!25278789!1 X-Originating-IP: [209.85.216.52] X-SpamReason: No, hits=0.4 required=7.0 tests=HTML_50_60,HTML_MESSAGE, ML_RADAR_SPEW_LINKS_14,RCVD_BY_IP,spamassassin: X-StarScan-Received: X-StarScan-Version: 6.6.1.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 12476 invoked from network); 16 Sep 2012 17:28:06 -0000 Received: from mail-qa0-f52.google.com (HELO mail-qa0-f52.google.com) (209.85.216.52) by server-4.tower-216.messagelabs.com with RC4-SHA encrypted SMTP; 16 Sep 2012 17:28:06 -0000 Received: by qabg14 with SMTP id g14so1177978qab.11 for ; Sun, 16 Sep 2012 10:28:05 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=from:to:subject:date:message-id:mime-version:content-type:x-mailer :thread-index:content-language; bh=3FE8EEyhLd2oEg0wn/kYneK81anItqa3rfRdnTaai54=; b=NqJnhann8ESTQtSiVD155KCbpvDht9xskA8mxH/91IGg1CAnW2YcYNpy43/FRynj35 Gu26OSRoJrmmn38RiPAYAkAMLzeBo+2/TV3ZHwEwv4MltCdm1r2tvx1CxL2Y7nvgAzfT 6iKUcyUtFR627xBfbj+ft9dWp5R4ND4EdfozeuY5FFQ/Z0dRVivvft6wIK0KDilvWOQU 2wEwsTjyVCaRhoMhx+ibZKoeeHNz62nJs6DN8e85IVuKvcwppDJcxTeLubMhP1dxk403 2ARiUbxWa+Bh4rA83Sr4+s4KZQHaQZx0dfJQfOjxSr7yuPcQ2cRwXwcuKmoheYSBvy3z F87w== Received: by 10.224.175.204 with SMTP id bb12mr22125165qab.14.1347816484967; Sun, 16 Sep 2012 10:28:04 -0700 (PDT) Received: from Belldandy (c-76-119-253-48.hsd1.ma.comcast.net. [76.119.253.48]) by mx.google.com with ESMTPS id h8sm11654433qap.16.2012.09.16.10.28.03 (version=TLSv1/SSLv3 cipher=OTHER); Sun, 16 Sep 2012 10:28:04 -0700 (PDT) From: "Marc Tousignant" To: Date: Sun, 16 Sep 2012 13:28:06 -0400 Message-ID: <003601cd9430$a381db70$ea859250$@gmail.com> MIME-Version: 1.0 X-Mailer: Microsoft Outlook 14.0 Thread-Index: Ac2ULEQ+iZ4G3QhYQkWQx6+MidWqNQ== Content-Language: en-us Subject: [Xen-users] Setting up XEN domU causes RAID5 to fail? X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============1941137569312017699==" Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org This is a multipart message in MIME format. --===============1941137569312017699== Content-Type: multipart/alternative; boundary="----=_NextPart_000_0037_01CD940F.1C71C210" Content-Language: en-us This is a multipart message in MIME format. ------=_NextPart_000_0037_01CD940F.1C71C210 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit This may be a coincidence or not, but I'm building a new XEN system for myself for work purposes. I support several different versions of a software that cannot be installed at the same time, so I decided I wanted to setup a XEN domU for each. I had 5 spare 500GB drives so I put them in my system and partitioned them so I have a RAID1 boot, a RAID5 root and a RAID5 images. I got linux (Funtoo) installed on the root with my kernel on the boot. XEN is installed as well and setup and running. I created a xen_images folder and a iso _images folder both in the /images folder. I downloaded the ISO's for the OS's I need to install into iso_images. I then created several .img files in the xen_images folder using dd. For example (dd if=/dev/zero of=/images/xen_images/Win7x86_Base.img bs=1 count=1 seek=50G) I then started my first xen domU booting from the Win7 ISO I had and started the install. I got to the point where it formatted the "drive" and started installing, it failed on the extraction step saying my "DVD" was bad. When I went back to check the md5/sha on the ISO I noticed that both of my RAID5's "lost" several members. The RAID1 is fine. Strangely enough the system stays up with an OS drive that is supposedly failed, granted a lot of functionality is lost, like missing files etc on the missing parts of the RAID5 root # cat /proc/mdstat Personalities : [raid1] [raid6] [raid5] [raid4] [multipath] md2 : active raid5 sda5[0](F) sde5[4](F) sdd5[3](F) sdc5[2] sdb5[1] 1724864512 blocks super 1.2 level 5, 512k chunk, algorithm 2 [5/2] [_UU__] md1 : active raid5 sda4[5](F) sde4[6](F) sdd4[7](F) sdc4[2] sdb4[1] 209713152 blocks level 5, 512k chunk, algorithm 2 [5/2] [_UU__] md0 : active raid1 sda1[0] sde1[4] sdd1[3] sdc1[2] sdb1[1] 511936 blocks [5/5] [UUUUU] If I check the drives I get informed that the md superblock has vanished on the missing drives. A reboot fails, because the RAID5's are out of sync, and I have to go into the busybox shell in order to repair them. After repairing, and forcing a fsck, the system checks out again as good. I cannot get it to fail the RAID5's again unless I attempt to start the domU install again. Anyone run into this or something similar before? MarcT ------=_NextPart_000_0037_01CD940F.1C71C210 Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable

This may = be a coincidence or not, but I’m building a new XEN system for = myself for work purposes.

I support = several different versions of a software that cannot be installed at the = same time, so I decided I wanted to setup a XEN domU for = each.

 

I had 5 spare 500GB drives so I put them in my system = and partitioned them so I have a RAID1 boot, a RAID5 root and a RAID5 = images.

I got linux (Funtoo) = installed on the root with my kernel on the boot. XEN is installed as = well and setup and running.

I created = a xen_images folder and a iso _images folder both in the /images = folder.

I downloaded the ISO’s = for the OS’s I need to install into iso_images.

I then created several .img files in the xen_images = folder using dd. For example (dd if=3D/dev/zero = of=3D/images/xen_images/Win7x86_Base.img bs=3D1 count=3D1 = seek=3D50G)

 

I then started my first xen domU booting from the Win7 = ISO I had and started the install.

I = got to the point where it formatted the “drive” and started = installing, it failed on the extraction step saying my “DVD” = was bad.

When I went back to check = the md5/sha on the ISO I noticed that both of my RAID5’s = “lost” several members. The RAID1 is fine.

Strangely enough the system stays up with an OS drive = that is supposedly failed, granted a lot of functionality is lost, like = missing files etc on the missing parts of the RAID5 = root

 

# cat /proc/mdstat

Personalities : [raid1] [raid6] [raid5] [raid4] = [multipath]

md2 : active raid5 = sda5[0](F) sde5[4](F) sdd5[3](F) sdc5[2] sdb5[1]

      1724864512 blocks super = 1.2 level 5, 512k chunk, algorithm 2 [5/2] [_UU__]

 

md1 : active = raid5 sda4[5](F) sde4[6](F) sdd4[7](F) sdc4[2] sdb4[1]

      209713152 blocks level = 5, 512k chunk, algorithm 2 [5/2] [_UU__]

 

md0 : active = raid1 sda1[0] sde1[4] sdd1[3] sdc1[2] sdb1[1]

      511936 blocks [5/5] = [UUUUU]

 

If I check the drives I get informed that the md = superblock has vanished on the missing drives.

A reboot fails, because the RAID5’s are out of = sync, and I have to go into the busybox shell in order to repair = them.

After repairing, and forcing a = fsck, the system checks out again as good. I cannot get it to fail the = RAID5’s again unless I attempt to start the domU install = again.

 

Anyone run into this or something similar = before?

 

MarcT

------=_NextPart_000_0037_01CD940F.1C71C210-- --===============1941137569312017699== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users --===============1941137569312017699==-- From xen-users-bounces@lists.xen.org Sun Sep 16 17:29:23 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Sun, 16 Sep 2012 17:29:23 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TDIde-0005tL-Fc; Sun, 16 Sep 2012 17:28:10 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TDIdb-0005tD-Tl for xen-users@lists.xen.org; Sun, 16 Sep 2012 17:28:08 +0000 Received: from [85.158.143.99:46417] by server-1.bemta-4.messagelabs.com id D5/DE-12504-72C06505; Sun, 16 Sep 2012 17:28:07 +0000 X-Env-Sender: myrdhn@gmail.com X-Msg-Ref: server-4.tower-216.messagelabs.com!1347816485!25278789!1 X-Originating-IP: [209.85.216.52] X-SpamReason: No, hits=0.4 required=7.0 tests=HTML_50_60,HTML_MESSAGE, ML_RADAR_SPEW_LINKS_14,RCVD_BY_IP,spamassassin: X-StarScan-Received: X-StarScan-Version: 6.6.1.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 12476 invoked from network); 16 Sep 2012 17:28:06 -0000 Received: from mail-qa0-f52.google.com (HELO mail-qa0-f52.google.com) (209.85.216.52) by server-4.tower-216.messagelabs.com with RC4-SHA encrypted SMTP; 16 Sep 2012 17:28:06 -0000 Received: by qabg14 with SMTP id g14so1177978qab.11 for ; Sun, 16 Sep 2012 10:28:05 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=from:to:subject:date:message-id:mime-version:content-type:x-mailer :thread-index:content-language; bh=3FE8EEyhLd2oEg0wn/kYneK81anItqa3rfRdnTaai54=; b=NqJnhann8ESTQtSiVD155KCbpvDht9xskA8mxH/91IGg1CAnW2YcYNpy43/FRynj35 Gu26OSRoJrmmn38RiPAYAkAMLzeBo+2/TV3ZHwEwv4MltCdm1r2tvx1CxL2Y7nvgAzfT 6iKUcyUtFR627xBfbj+ft9dWp5R4ND4EdfozeuY5FFQ/Z0dRVivvft6wIK0KDilvWOQU 2wEwsTjyVCaRhoMhx+ibZKoeeHNz62nJs6DN8e85IVuKvcwppDJcxTeLubMhP1dxk403 2ARiUbxWa+Bh4rA83Sr4+s4KZQHaQZx0dfJQfOjxSr7yuPcQ2cRwXwcuKmoheYSBvy3z F87w== Received: by 10.224.175.204 with SMTP id bb12mr22125165qab.14.1347816484967; Sun, 16 Sep 2012 10:28:04 -0700 (PDT) Received: from Belldandy (c-76-119-253-48.hsd1.ma.comcast.net. [76.119.253.48]) by mx.google.com with ESMTPS id h8sm11654433qap.16.2012.09.16.10.28.03 (version=TLSv1/SSLv3 cipher=OTHER); Sun, 16 Sep 2012 10:28:04 -0700 (PDT) From: "Marc Tousignant" To: Date: Sun, 16 Sep 2012 13:28:06 -0400 Message-ID: <003601cd9430$a381db70$ea859250$@gmail.com> MIME-Version: 1.0 X-Mailer: Microsoft Outlook 14.0 Thread-Index: Ac2ULEQ+iZ4G3QhYQkWQx6+MidWqNQ== Content-Language: en-us Subject: [Xen-users] Setting up XEN domU causes RAID5 to fail? X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============1941137569312017699==" Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org This is a multipart message in MIME format. --===============1941137569312017699== Content-Type: multipart/alternative; boundary="----=_NextPart_000_0037_01CD940F.1C71C210" Content-Language: en-us This is a multipart message in MIME format. ------=_NextPart_000_0037_01CD940F.1C71C210 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit This may be a coincidence or not, but I'm building a new XEN system for myself for work purposes. I support several different versions of a software that cannot be installed at the same time, so I decided I wanted to setup a XEN domU for each. I had 5 spare 500GB drives so I put them in my system and partitioned them so I have a RAID1 boot, a RAID5 root and a RAID5 images. I got linux (Funtoo) installed on the root with my kernel on the boot. XEN is installed as well and setup and running. I created a xen_images folder and a iso _images folder both in the /images folder. I downloaded the ISO's for the OS's I need to install into iso_images. I then created several .img files in the xen_images folder using dd. For example (dd if=/dev/zero of=/images/xen_images/Win7x86_Base.img bs=1 count=1 seek=50G) I then started my first xen domU booting from the Win7 ISO I had and started the install. I got to the point where it formatted the "drive" and started installing, it failed on the extraction step saying my "DVD" was bad. When I went back to check the md5/sha on the ISO I noticed that both of my RAID5's "lost" several members. The RAID1 is fine. Strangely enough the system stays up with an OS drive that is supposedly failed, granted a lot of functionality is lost, like missing files etc on the missing parts of the RAID5 root # cat /proc/mdstat Personalities : [raid1] [raid6] [raid5] [raid4] [multipath] md2 : active raid5 sda5[0](F) sde5[4](F) sdd5[3](F) sdc5[2] sdb5[1] 1724864512 blocks super 1.2 level 5, 512k chunk, algorithm 2 [5/2] [_UU__] md1 : active raid5 sda4[5](F) sde4[6](F) sdd4[7](F) sdc4[2] sdb4[1] 209713152 blocks level 5, 512k chunk, algorithm 2 [5/2] [_UU__] md0 : active raid1 sda1[0] sde1[4] sdd1[3] sdc1[2] sdb1[1] 511936 blocks [5/5] [UUUUU] If I check the drives I get informed that the md superblock has vanished on the missing drives. A reboot fails, because the RAID5's are out of sync, and I have to go into the busybox shell in order to repair them. After repairing, and forcing a fsck, the system checks out again as good. I cannot get it to fail the RAID5's again unless I attempt to start the domU install again. Anyone run into this or something similar before? MarcT ------=_NextPart_000_0037_01CD940F.1C71C210 Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable

This may = be a coincidence or not, but I’m building a new XEN system for = myself for work purposes.

I support = several different versions of a software that cannot be installed at the = same time, so I decided I wanted to setup a XEN domU for = each.

 

I had 5 spare 500GB drives so I put them in my system = and partitioned them so I have a RAID1 boot, a RAID5 root and a RAID5 = images.

I got linux (Funtoo) = installed on the root with my kernel on the boot. XEN is installed as = well and setup and running.

I created = a xen_images folder and a iso _images folder both in the /images = folder.

I downloaded the ISO’s = for the OS’s I need to install into iso_images.

I then created several .img files in the xen_images = folder using dd. For example (dd if=3D/dev/zero = of=3D/images/xen_images/Win7x86_Base.img bs=3D1 count=3D1 = seek=3D50G)

 

I then started my first xen domU booting from the Win7 = ISO I had and started the install.

I = got to the point where it formatted the “drive” and started = installing, it failed on the extraction step saying my “DVD” = was bad.

When I went back to check = the md5/sha on the ISO I noticed that both of my RAID5’s = “lost” several members. The RAID1 is fine.

Strangely enough the system stays up with an OS drive = that is supposedly failed, granted a lot of functionality is lost, like = missing files etc on the missing parts of the RAID5 = root

 

# cat /proc/mdstat

Personalities : [raid1] [raid6] [raid5] [raid4] = [multipath]

md2 : active raid5 = sda5[0](F) sde5[4](F) sdd5[3](F) sdc5[2] sdb5[1]

      1724864512 blocks super = 1.2 level 5, 512k chunk, algorithm 2 [5/2] [_UU__]

 

md1 : active = raid5 sda4[5](F) sde4[6](F) sdd4[7](F) sdc4[2] sdb4[1]

      209713152 blocks level = 5, 512k chunk, algorithm 2 [5/2] [_UU__]

 

md0 : active = raid1 sda1[0] sde1[4] sdd1[3] sdc1[2] sdb1[1]

      511936 blocks [5/5] = [UUUUU]

 

If I check the drives I get informed that the md = superblock has vanished on the missing drives.

A reboot fails, because the RAID5’s are out of = sync, and I have to go into the busybox shell in order to repair = them.

After repairing, and forcing a = fsck, the system checks out again as good. I cannot get it to fail the = RAID5’s again unless I attempt to start the domU install = again.

 

Anyone run into this or something similar = before?

 

MarcT

------=_NextPart_000_0037_01CD940F.1C71C210-- --===============1941137569312017699== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users --===============1941137569312017699==-- From xen-users-bounces@lists.xen.org Sun Sep 16 18:07:50 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Sun, 16 Sep 2012 18:07:50 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TDJF6-0006Yg-Hj; Sun, 16 Sep 2012 18:06:52 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TDJF5-0006Yb-HB for xen-users@lists.xen.org; Sun, 16 Sep 2012 18:06:51 +0000 Received: from [85.158.138.51:51519] by server-11.bemta-3.messagelabs.com id F2/CE-30250-A3516505; Sun, 16 Sep 2012 18:06:50 +0000 X-Env-Sender: darkshvein@gmail.com X-Msg-Ref: server-14.tower-174.messagelabs.com!1347818807!24424280!1 X-Originating-IP: [209.85.160.45] X-SpamReason: No, hits=1.5 required=7.0 tests=HTML_00_10,HTML_MESSAGE, ML_RADAR_SPEW_LINKS_14,RCVD_BY_IP,spamassassin: X-StarScan-Received: X-StarScan-Version: 6.6.1.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 10616 invoked from network); 16 Sep 2012 18:06:49 -0000 Received: from mail-pb0-f45.google.com (HELO mail-pb0-f45.google.com) (209.85.160.45) by server-14.tower-174.messagelabs.com with RC4-SHA encrypted SMTP; 16 Sep 2012 18:06:49 -0000 Received: by pbbrp12 with SMTP id rp12so8180638pbb.32 for ; Sun, 16 Sep 2012 11:06:47 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:date:message-id:subject:from:to:content-type; bh=aVzan9HfTG+hxqEdhR8A5cLA0QrjMtAziU8t8cfAzlQ=; b=aUtD/h701y5+7HirDwHOAhyHG+1NjT1v0hIRKh6/FrynqgczIFG806hUGHY3T7X8Af jV59gozk/J5/8jT2XqbdAUESHTMk6btbOE+8nueczoZITicVGMk9Brb4IlCaO2WGqG8f BtImaqVJnDfQLhcwlnSJz9ODK86tdjN3PyQNS+SgseD1G5GyS1In9nFK6Dqqzqp9Swhb n68ceb9cRAZUdVVj2fclNfIpn+68QBUcMetulemKvUDzf7tYJ8abv23VwxFdLIVF14bv UGopZCOBLf4MQ1Ft5KcpDjwDLvHU//H1XLf4zRcksDkt/Go43yiShpNe8++w09seCneL kMfQ== MIME-Version: 1.0 Received: by 10.66.88.40 with SMTP id bd8mr15528279pab.36.1347818807137; Sun, 16 Sep 2012 11:06:47 -0700 (PDT) Received: by 10.68.60.133 with HTTP; Sun, 16 Sep 2012 11:06:47 -0700 (PDT) Date: Sun, 16 Sep 2012 22:06:47 +0400 Message-ID: From: Stanley Tweedle To: xen-users@lists.xen.org Subject: [Xen-users] System with second radeon card can't boot X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============6023009832798402606==" Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org --===============6023009832798402606== Content-Type: multipart/alternative; boundary=20cf3068481938961a04c9d5858d --20cf3068481938961a04c9d5858d Content-Type: text/plain; charset=ISO-8859-1 Hi. I bought radeon HD 2600pro, instead 8400gs, and debian kernel with hypervisor(and without) can't boot. I removed iommu=1 and other xen-specific grub boot options, - useless. Currently, 'radeon' driver not in blacklist. 'fglrx' not installed. No signal to monitor from both sources(cards). Primary card is radeon 6850(usually for win7 domU). Ubuntu boot successful. :-( ) Any suggestions? Ofc, a little offtop, but I have no ideas. Gigabyte GA-970A-DS3, 01:00.0 VGA compatible controller: Advanced Micro Devices [AMD] nee ATI Barts PRO [ATI Radeon HD 6800 Series] 05:00.0 VGA compatible controller: Advanced Micro Devices [AMD] nee ATI RV630 [Radeon HD 2600 Series] --20cf3068481938961a04c9d5858d Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Hi. I bought radeon HD 2600pro, instead 8400gs, and debian kernel with hype= rvisor(and without) can't boot. I removed iommu=3D1 and other xen-speci= fic grub boot options, - useless.=A0 Currently, 'radeon' driver no= t in blacklist. 'fglrx' not installed. No signal to monitor from bo= th sources(cards). Primary card is radeon 6850(usually for win7 domU). Ubun= tu boot successful. :-(=A0=A0 )
Any suggestions?
Ofc, a little offtop, but I have no ideas.
Gigabyte = GA-970A-DS3,
01:00.0 VGA compatible controller: Advanced Micro Devices [= AMD] nee ATI Barts PRO [ATI Radeon HD 6800 Series]
05:00.0 VGA compatibl= e controller: Advanced Micro Devices [AMD] nee ATI RV630 [Radeon HD 2600 Se= ries]
--20cf3068481938961a04c9d5858d-- --===============6023009832798402606== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users --===============6023009832798402606==-- From xen-users-bounces@lists.xen.org Sun Sep 16 18:07:50 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Sun, 16 Sep 2012 18:07:50 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TDJF6-0006Yg-Hj; Sun, 16 Sep 2012 18:06:52 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TDJF5-0006Yb-HB for xen-users@lists.xen.org; Sun, 16 Sep 2012 18:06:51 +0000 Received: from [85.158.138.51:51519] by server-11.bemta-3.messagelabs.com id F2/CE-30250-A3516505; Sun, 16 Sep 2012 18:06:50 +0000 X-Env-Sender: darkshvein@gmail.com X-Msg-Ref: server-14.tower-174.messagelabs.com!1347818807!24424280!1 X-Originating-IP: [209.85.160.45] X-SpamReason: No, hits=1.5 required=7.0 tests=HTML_00_10,HTML_MESSAGE, ML_RADAR_SPEW_LINKS_14,RCVD_BY_IP,spamassassin: X-StarScan-Received: X-StarScan-Version: 6.6.1.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 10616 invoked from network); 16 Sep 2012 18:06:49 -0000 Received: from mail-pb0-f45.google.com (HELO mail-pb0-f45.google.com) (209.85.160.45) by server-14.tower-174.messagelabs.com with RC4-SHA encrypted SMTP; 16 Sep 2012 18:06:49 -0000 Received: by pbbrp12 with SMTP id rp12so8180638pbb.32 for ; Sun, 16 Sep 2012 11:06:47 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:date:message-id:subject:from:to:content-type; bh=aVzan9HfTG+hxqEdhR8A5cLA0QrjMtAziU8t8cfAzlQ=; b=aUtD/h701y5+7HirDwHOAhyHG+1NjT1v0hIRKh6/FrynqgczIFG806hUGHY3T7X8Af jV59gozk/J5/8jT2XqbdAUESHTMk6btbOE+8nueczoZITicVGMk9Brb4IlCaO2WGqG8f BtImaqVJnDfQLhcwlnSJz9ODK86tdjN3PyQNS+SgseD1G5GyS1In9nFK6Dqqzqp9Swhb n68ceb9cRAZUdVVj2fclNfIpn+68QBUcMetulemKvUDzf7tYJ8abv23VwxFdLIVF14bv UGopZCOBLf4MQ1Ft5KcpDjwDLvHU//H1XLf4zRcksDkt/Go43yiShpNe8++w09seCneL kMfQ== MIME-Version: 1.0 Received: by 10.66.88.40 with SMTP id bd8mr15528279pab.36.1347818807137; Sun, 16 Sep 2012 11:06:47 -0700 (PDT) Received: by 10.68.60.133 with HTTP; Sun, 16 Sep 2012 11:06:47 -0700 (PDT) Date: Sun, 16 Sep 2012 22:06:47 +0400 Message-ID: From: Stanley Tweedle To: xen-users@lists.xen.org Subject: [Xen-users] System with second radeon card can't boot X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============6023009832798402606==" Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org --===============6023009832798402606== Content-Type: multipart/alternative; boundary=20cf3068481938961a04c9d5858d --20cf3068481938961a04c9d5858d Content-Type: text/plain; charset=ISO-8859-1 Hi. I bought radeon HD 2600pro, instead 8400gs, and debian kernel with hypervisor(and without) can't boot. I removed iommu=1 and other xen-specific grub boot options, - useless. Currently, 'radeon' driver not in blacklist. 'fglrx' not installed. No signal to monitor from both sources(cards). Primary card is radeon 6850(usually for win7 domU). Ubuntu boot successful. :-( ) Any suggestions? Ofc, a little offtop, but I have no ideas. Gigabyte GA-970A-DS3, 01:00.0 VGA compatible controller: Advanced Micro Devices [AMD] nee ATI Barts PRO [ATI Radeon HD 6800 Series] 05:00.0 VGA compatible controller: Advanced Micro Devices [AMD] nee ATI RV630 [Radeon HD 2600 Series] --20cf3068481938961a04c9d5858d Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Hi. I bought radeon HD 2600pro, instead 8400gs, and debian kernel with hype= rvisor(and without) can't boot. I removed iommu=3D1 and other xen-speci= fic grub boot options, - useless.=A0 Currently, 'radeon' driver no= t in blacklist. 'fglrx' not installed. No signal to monitor from bo= th sources(cards). Primary card is radeon 6850(usually for win7 domU). Ubun= tu boot successful. :-(=A0=A0 )
Any suggestions?
Ofc, a little offtop, but I have no ideas.
Gigabyte = GA-970A-DS3,
01:00.0 VGA compatible controller: Advanced Micro Devices [= AMD] nee ATI Barts PRO [ATI Radeon HD 6800 Series]
05:00.0 VGA compatibl= e controller: Advanced Micro Devices [AMD] nee ATI RV630 [Radeon HD 2600 Se= ries]
--20cf3068481938961a04c9d5858d-- --===============6023009832798402606== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users --===============6023009832798402606==-- From xen-users-bounces@lists.xen.org Sun Sep 16 18:09:25 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Sun, 16 Sep 2012 18:09:25 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TDJGZ-0006eL-9B; Sun, 16 Sep 2012 18:08:23 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TDJGX-0006e5-Gg for xen-users@lists.xen.org; Sun, 16 Sep 2012 18:08:21 +0000 Received: from [85.158.139.211:20324] by server-6.bemta-5.messagelabs.com id 30/BA-21336-49516505; Sun, 16 Sep 2012 18:08:20 +0000 X-Env-Sender: Ian.Campbell@citrix.com X-Msg-Ref: server-14.tower-206.messagelabs.com!1347818900!18716565!1 X-Originating-IP: [62.200.22.115] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogNjIuMjAwLjIyLjExNSA9PiAxMDk2MzE=\n X-StarScan-Received: X-StarScan-Version: 6.6.1.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 14040 invoked from network); 16 Sep 2012 18:08:20 -0000 Received: from smtp.ctxuk.citrix.com (HELO SMTP.EU.CITRIX.COM) (62.200.22.115) by server-14.tower-206.messagelabs.com with RC4-SHA encrypted SMTP; 16 Sep 2012 18:08:20 -0000 X-IronPort-AV: E=Sophos;i="4.80,431,1344211200"; d="scan'208";a="14566431" Received: from lonpmailmx01.citrite.net ([10.30.203.162]) by LONPIPO01.EU.CITRIX.COM with ESMTP/TLS/RC4-MD5; 16 Sep 2012 18:08:20 +0000 Received: from [127.0.0.1] (10.80.16.67) by smtprelay.citrix.com (10.30.203.162) with Microsoft SMTP Server id 8.3.279.1; Sun, 16 Sep 2012 19:08:20 +0100 Message-ID: <1347818899.25803.75.camel@dagon.hellion.org.uk> From: Ian Campbell To: Marc Tousignant Date: Sun, 16 Sep 2012 19:08:19 +0100 In-Reply-To: <003601cd9430$a381db70$ea859250$@gmail.com> References: <003601cd9430$a381db70$ea859250$@gmail.com> Organization: Citrix Systems, Inc. X-Mailer: Evolution 3.4.3-1 MIME-Version: 1.0 Cc: "xen-users@lists.xen.org" Subject: Re: [Xen-users] Setting up XEN domU causes RAID5 to fail? X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: base64 Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org T24gU3VuLCAyMDEyLTA5LTE2IGF0IDE4OjI4ICswMTAwLCBNYXJjIFRvdXNpZ25hbnQgd3JvdGU6 Cgo+IEkgdGhlbiBjcmVhdGVkIHNldmVyYWwgLmltZyBmaWxlcyBpbiB0aGUgeGVuX2ltYWdlcyBm b2xkZXIgdXNpbmcgZGQuCj4gRm9yIGV4YW1wbGUgKGRkIGlmPS9kZXYvemVybyBvZj0vaW1hZ2Vz L3hlbl9pbWFnZXMvV2luN3g4Nl9CYXNlLmltZwo+IGJzPTEgY291bnQ9MSBzZWVrPTUwRykKWy4u Ll0KPiBJIGdvdCB0byB0aGUgcG9pbnQgd2hlcmUgaXQgZm9ybWF0dGVkIHRoZSDigJxkcml2ZeKA nSBhbmQgc3RhcnRlZAo+IGluc3RhbGxpbmcsIGl0IGZhaWxlZCBvbiB0aGUgZXh0cmFjdGlvbiBz dGVwIHNheWluZyBteSDigJxEVkTigJ0gd2FzIGJhZC4KCldoYXQgZG9lcyB5b3VyIGd1ZXN0IGNv bmZpZyBmaWxlIGxvb2sgbGlrZSwgaW4gcGFydGljdWxhciB0aGUgZGlzayBsaW5lLgoKSXMgdGhl cmUgYW55IGNoYW5jZSB0aGF0IHlvdSBoYXZlIGFjY2lkZW50YWxseSBwb2ludGVkIHRoZSBWTSdz IGRpc2tzIGF0Cm9uZSBvciBtb3JlIG9mIHRoZSBwaHlzaWNhbCBkaXNrcyB3aGljaCBtYWtlcyB1 cCB5b3VyIFJBSUQgYXJyYXk/CgpJYW4uCgoKCl9fX19fX19fX19fX19fX19fX19fX19fX19fX19f X19fX19fX19fX19fX19fX19fClhlbi11c2VycyBtYWlsaW5nIGxpc3QKWGVuLXVzZXJzQGxpc3Rz Lnhlbi5vcmcKaHR0cDovL2xpc3RzLnhlbi5vcmcveGVuLXVzZXJz From xen-users-bounces@lists.xen.org Sun Sep 16 18:09:25 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Sun, 16 Sep 2012 18:09:25 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TDJGZ-0006eL-9B; Sun, 16 Sep 2012 18:08:23 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TDJGX-0006e5-Gg for xen-users@lists.xen.org; Sun, 16 Sep 2012 18:08:21 +0000 Received: from [85.158.139.211:20324] by server-6.bemta-5.messagelabs.com id 30/BA-21336-49516505; Sun, 16 Sep 2012 18:08:20 +0000 X-Env-Sender: Ian.Campbell@citrix.com X-Msg-Ref: server-14.tower-206.messagelabs.com!1347818900!18716565!1 X-Originating-IP: [62.200.22.115] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogNjIuMjAwLjIyLjExNSA9PiAxMDk2MzE=\n X-StarScan-Received: X-StarScan-Version: 6.6.1.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 14040 invoked from network); 16 Sep 2012 18:08:20 -0000 Received: from smtp.ctxuk.citrix.com (HELO SMTP.EU.CITRIX.COM) (62.200.22.115) by server-14.tower-206.messagelabs.com with RC4-SHA encrypted SMTP; 16 Sep 2012 18:08:20 -0000 X-IronPort-AV: E=Sophos;i="4.80,431,1344211200"; d="scan'208";a="14566431" Received: from lonpmailmx01.citrite.net ([10.30.203.162]) by LONPIPO01.EU.CITRIX.COM with ESMTP/TLS/RC4-MD5; 16 Sep 2012 18:08:20 +0000 Received: from [127.0.0.1] (10.80.16.67) by smtprelay.citrix.com (10.30.203.162) with Microsoft SMTP Server id 8.3.279.1; Sun, 16 Sep 2012 19:08:20 +0100 Message-ID: <1347818899.25803.75.camel@dagon.hellion.org.uk> From: Ian Campbell To: Marc Tousignant Date: Sun, 16 Sep 2012 19:08:19 +0100 In-Reply-To: <003601cd9430$a381db70$ea859250$@gmail.com> References: <003601cd9430$a381db70$ea859250$@gmail.com> Organization: Citrix Systems, Inc. X-Mailer: Evolution 3.4.3-1 MIME-Version: 1.0 Cc: "xen-users@lists.xen.org" Subject: Re: [Xen-users] Setting up XEN domU causes RAID5 to fail? X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: base64 Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org T24gU3VuLCAyMDEyLTA5LTE2IGF0IDE4OjI4ICswMTAwLCBNYXJjIFRvdXNpZ25hbnQgd3JvdGU6 Cgo+IEkgdGhlbiBjcmVhdGVkIHNldmVyYWwgLmltZyBmaWxlcyBpbiB0aGUgeGVuX2ltYWdlcyBm b2xkZXIgdXNpbmcgZGQuCj4gRm9yIGV4YW1wbGUgKGRkIGlmPS9kZXYvemVybyBvZj0vaW1hZ2Vz L3hlbl9pbWFnZXMvV2luN3g4Nl9CYXNlLmltZwo+IGJzPTEgY291bnQ9MSBzZWVrPTUwRykKWy4u Ll0KPiBJIGdvdCB0byB0aGUgcG9pbnQgd2hlcmUgaXQgZm9ybWF0dGVkIHRoZSDigJxkcml2ZeKA nSBhbmQgc3RhcnRlZAo+IGluc3RhbGxpbmcsIGl0IGZhaWxlZCBvbiB0aGUgZXh0cmFjdGlvbiBz dGVwIHNheWluZyBteSDigJxEVkTigJ0gd2FzIGJhZC4KCldoYXQgZG9lcyB5b3VyIGd1ZXN0IGNv bmZpZyBmaWxlIGxvb2sgbGlrZSwgaW4gcGFydGljdWxhciB0aGUgZGlzayBsaW5lLgoKSXMgdGhl cmUgYW55IGNoYW5jZSB0aGF0IHlvdSBoYXZlIGFjY2lkZW50YWxseSBwb2ludGVkIHRoZSBWTSdz IGRpc2tzIGF0Cm9uZSBvciBtb3JlIG9mIHRoZSBwaHlzaWNhbCBkaXNrcyB3aGljaCBtYWtlcyB1 cCB5b3VyIFJBSUQgYXJyYXk/CgpJYW4uCgoKCl9fX19fX19fX19fX19fX19fX19fX19fX19fX19f X19fX19fX19fX19fX19fX19fClhlbi11c2VycyBtYWlsaW5nIGxpc3QKWGVuLXVzZXJzQGxpc3Rz Lnhlbi5vcmcKaHR0cDovL2xpc3RzLnhlbi5vcmcveGVuLXVzZXJz From xen-users-bounces@lists.xen.org Sun Sep 16 19:05:53 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Sun, 16 Sep 2012 19:05:53 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TDK9B-0007ke-45; Sun, 16 Sep 2012 19:04:49 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TDK99-0007kZ-2a for xen-users@lists.xensource.com; Sun, 16 Sep 2012 19:04:47 +0000 Received: from [85.158.143.35:52966] by server-1.bemta-4.messagelabs.com id FE/75-12504-EC226505; Sun, 16 Sep 2012 19:04:46 +0000 X-Env-Sender: peter.phaal@gmail.com X-Msg-Ref: server-14.tower-21.messagelabs.com!1347822284!18556096!1 X-Originating-IP: [209.85.216.171] X-SpamReason: No, hits=0.8 required=7.0 tests=BODY_RANDOM_LONG, ML_RADAR_SPEW_LINKS_14, ML_RADAR_SPEW_LINKS_23, RCVD_BY_IP, spamassassin: X-StarScan-Received: X-StarScan-Version: 6.6.1.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 2672 invoked from network); 16 Sep 2012 19:04:45 -0000 Received: from mail-qc0-f171.google.com (HELO mail-qc0-f171.google.com) (209.85.216.171) by server-14.tower-21.messagelabs.com with RC4-SHA encrypted SMTP; 16 Sep 2012 19:04:45 -0000 Received: by qcad1 with SMTP id d1so4838413qca.30 for ; Sun, 16 Sep 2012 12:04:44 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=80cQ6IWfPlr/If1+4Prsu1ENA2zanwju1eBv6tWaX2M=; b=rnfuMsJPATflX0ktm+pr4nqLYNlUfL9fHp9ul9393AdCk0O6dlQGGVpb05QbggGu8L 0OW3SyuCrelvpqN6LdF8lqd99xZ59Drbh1C7Up+MJ8fMpB48rPg9ZcxsqnUYZFUlpBMS vIuWdDghaQHdl3RUtHdjsd3I+JDdlLTCYmhlc6+NkafXYTvMnlQ+TxlsjfxZRmAPV+m7 /pC1j6KAVbFv2nb406IOmFDFZG/qmdj9FNjHBN1qFk2MUGLuxU3JKGH24rPimuDek3Vr csfkm7Trx60N64yGVR90zKf2hO66I28NNqf60jFxoDWC2BSqG4lIFMefla2ujoRJiwO8 7Png== MIME-Version: 1.0 Received: by 10.229.134.208 with SMTP id k16mr6100054qct.13.1347822283773; Sun, 16 Sep 2012 12:04:43 -0700 (PDT) Received: by 10.49.15.133 with HTTP; Sun, 16 Sep 2012 12:04:43 -0700 (PDT) In-Reply-To: <20120916122326.GA3867@bitfolk.com> References: <20120916122326.GA3867@bitfolk.com> Date: Sun, 16 Sep 2012 12:04:43 -0700 Message-ID: From: Peter Phaal To: Andy Smith Cc: xen-users@lists.xensource.com Subject: Re: [Xen-users] How are you measuring CPU usage? X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org Andy, You might want to take a look at installing Host sFlow agents on your hypervisors. The agent is extremely lightweight, directly accesses statistics using libxenstat and exports them using the sFlow protocol (XDR/UDP) to a remote collector. http://host-sflow.sourceforge.net/ Ganglia can be used to collect the data from your hypervisors and report performance: http://blog.sflow.com/2012/01/using-ganglia-to-monitor-virtual.html Are you using the Open vSwitch? It also includes sFlow support and can give you a better handle on network performance: http://openvswitch.org/ Peter On Sun, Sep 16, 2012 at 5:23 AM, Andy Smith wrote: > Is there a better way to read a domU's CPU time counter than parsing > the output of "xm list --long"? Is it available cheaply from > somewhere in /sys or is there an API or anything? _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Sun Sep 16 19:05:53 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Sun, 16 Sep 2012 19:05:53 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TDK9B-0007ke-45; Sun, 16 Sep 2012 19:04:49 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TDK99-0007kZ-2a for xen-users@lists.xensource.com; Sun, 16 Sep 2012 19:04:47 +0000 Received: from [85.158.143.35:52966] by server-1.bemta-4.messagelabs.com id FE/75-12504-EC226505; Sun, 16 Sep 2012 19:04:46 +0000 X-Env-Sender: peter.phaal@gmail.com X-Msg-Ref: server-14.tower-21.messagelabs.com!1347822284!18556096!1 X-Originating-IP: [209.85.216.171] X-SpamReason: No, hits=0.8 required=7.0 tests=BODY_RANDOM_LONG, ML_RADAR_SPEW_LINKS_14, ML_RADAR_SPEW_LINKS_23, RCVD_BY_IP, spamassassin: X-StarScan-Received: X-StarScan-Version: 6.6.1.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 2672 invoked from network); 16 Sep 2012 19:04:45 -0000 Received: from mail-qc0-f171.google.com (HELO mail-qc0-f171.google.com) (209.85.216.171) by server-14.tower-21.messagelabs.com with RC4-SHA encrypted SMTP; 16 Sep 2012 19:04:45 -0000 Received: by qcad1 with SMTP id d1so4838413qca.30 for ; Sun, 16 Sep 2012 12:04:44 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=80cQ6IWfPlr/If1+4Prsu1ENA2zanwju1eBv6tWaX2M=; b=rnfuMsJPATflX0ktm+pr4nqLYNlUfL9fHp9ul9393AdCk0O6dlQGGVpb05QbggGu8L 0OW3SyuCrelvpqN6LdF8lqd99xZ59Drbh1C7Up+MJ8fMpB48rPg9ZcxsqnUYZFUlpBMS vIuWdDghaQHdl3RUtHdjsd3I+JDdlLTCYmhlc6+NkafXYTvMnlQ+TxlsjfxZRmAPV+m7 /pC1j6KAVbFv2nb406IOmFDFZG/qmdj9FNjHBN1qFk2MUGLuxU3JKGH24rPimuDek3Vr csfkm7Trx60N64yGVR90zKf2hO66I28NNqf60jFxoDWC2BSqG4lIFMefla2ujoRJiwO8 7Png== MIME-Version: 1.0 Received: by 10.229.134.208 with SMTP id k16mr6100054qct.13.1347822283773; Sun, 16 Sep 2012 12:04:43 -0700 (PDT) Received: by 10.49.15.133 with HTTP; Sun, 16 Sep 2012 12:04:43 -0700 (PDT) In-Reply-To: <20120916122326.GA3867@bitfolk.com> References: <20120916122326.GA3867@bitfolk.com> Date: Sun, 16 Sep 2012 12:04:43 -0700 Message-ID: From: Peter Phaal To: Andy Smith Cc: xen-users@lists.xensource.com Subject: Re: [Xen-users] How are you measuring CPU usage? X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org Andy, You might want to take a look at installing Host sFlow agents on your hypervisors. The agent is extremely lightweight, directly accesses statistics using libxenstat and exports them using the sFlow protocol (XDR/UDP) to a remote collector. http://host-sflow.sourceforge.net/ Ganglia can be used to collect the data from your hypervisors and report performance: http://blog.sflow.com/2012/01/using-ganglia-to-monitor-virtual.html Are you using the Open vSwitch? It also includes sFlow support and can give you a better handle on network performance: http://openvswitch.org/ Peter On Sun, Sep 16, 2012 at 5:23 AM, Andy Smith wrote: > Is there a better way to read a domU's CPU time counter than parsing > the output of "xm list --long"? Is it available cheaply from > somewhere in /sys or is there an API or anything? _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Sun Sep 16 19:37:25 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Sun, 16 Sep 2012 19:37:25 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TDKds-0008H3-Jb; Sun, 16 Sep 2012 19:36:32 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TDKdq-0008Gv-Q5 for xen-users@lists.xen.org; Sun, 16 Sep 2012 19:36:30 +0000 Received: from [85.158.143.35:35940] by server-3.bemta-4.messagelabs.com id C0/08-08232-E3A26505; Sun, 16 Sep 2012 19:36:30 +0000 X-Env-Sender: myrdhn@gmail.com X-Msg-Ref: server-13.tower-21.messagelabs.com!1347824186!17125715!1 X-Originating-IP: [209.85.216.173] X-SpamReason: No, hits=0.3 required=7.0 tests=ML_RADAR_SPEW_LINKS_14, RCVD_BY_IP,spamassassin: X-StarScan-Received: X-StarScan-Version: 6.6.1.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 18533 invoked from network); 16 Sep 2012 19:36:27 -0000 Received: from mail-qc0-f173.google.com (HELO mail-qc0-f173.google.com) (209.85.216.173) by server-13.tower-21.messagelabs.com with RC4-SHA encrypted SMTP; 16 Sep 2012 19:36:27 -0000 Received: by qcab12 with SMTP id b12so5315518qca.32 for ; Sun, 16 Sep 2012 12:36:26 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=from:to:cc:references:in-reply-to:subject:date:message-id :mime-version:content-type:content-transfer-encoding:x-mailer :thread-index:content-language; bh=o68+1syeGnrXPoi8ttMmtPLpArIEpfqii4Jn9qGyBZk=; b=LXcDSYmA+UXbYb+HD9OpLMqWvBon1OJnHxZMDjYGkP613F2DOnad2TIjsbe9y6Ynbx YqYWefIK0yV4DlLbMBtliWSr01u/k3LL3giVdNnYhyuyFFNg4+CF6jf8qxMAxrpc4pPy bvBgHblyVUCHtAlaEhasoYgn+o0CdKmPuMRice6aLXoJ1u5YFb6o5Zn2cAbXDpH6XLnp lduFl4Z3zVOsoKuPvr0M1upc8fuJjPeIOobskmbI4Q5lsHiN33nko/j/4fM8C/kVyCuJ 8RF14B9k7Ffi7P6UxfNur8KO8C7nR7zotpMlLXB21DoMkNqbXcyso9y+F3gKRR79wm2l I8qw== Received: by 10.224.53.18 with SMTP id k18mr23200090qag.1.1347824186101; Sun, 16 Sep 2012 12:36:26 -0700 (PDT) Received: from Belldandy (c-76-119-253-48.hsd1.ma.comcast.net. [76.119.253.48]) by mx.google.com with ESMTPS id et6sm12012243qab.8.2012.09.16.12.36.25 (version=TLSv1/SSLv3 cipher=OTHER); Sun, 16 Sep 2012 12:36:25 -0700 (PDT) From: "Marc Tousignant" To: "'Ian Campbell'" References: <003601cd9430$a381db70$ea859250$@gmail.com> <1347818899.25803.75.camel@dagon.hellion.org.uk> In-Reply-To: <1347818899.25803.75.camel@dagon.hellion.org.uk> Date: Sun, 16 Sep 2012 15:36:28 -0400 Message-ID: <004d01cd9442$91c2d670$b5488350$@gmail.com> MIME-Version: 1.0 X-Mailer: Microsoft Outlook 14.0 Thread-Index: AQEtIveC4IhcOcllJOhnnzkXfTJ4EAF4akKmmMJ7RwA= Content-Language: en-us Cc: xen-users@lists.xen.org Subject: Re: [Xen-users] Setting up XEN domU causes RAID5 to fail? X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: base64 Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org T24gU3VuLCAyMDEyLTA5LTE2IGF0IDE4OjI4ICswMTAwLCBNYXJjIFRvdXNpZ25hbnQgd3JvdGU6 Cgo+IEkgdGhlbiBjcmVhdGVkIHNldmVyYWwgLmltZyBmaWxlcyBpbiB0aGUgeGVuX2ltYWdlcyBm b2xkZXIgdXNpbmcgZGQuCj4gRm9yIGV4YW1wbGUgKGRkIGlmPS9kZXYvemVybyBvZj0vaW1hZ2Vz L3hlbl9pbWFnZXMvV2luN3g4Nl9CYXNlLmltZwo+IGJzPTEgY291bnQ9MSBzZWVrPTUwRykKWy4u Ll0KPiBJIGdvdCB0byB0aGUgcG9pbnQgd2hlcmUgaXQgZm9ybWF0dGVkIHRoZSDigJxkcml2ZeKA nSBhbmQgc3RhcnRlZCAKPiBpbnN0YWxsaW5nLCBpdCBmYWlsZWQgb24gdGhlIGV4dHJhY3Rpb24g c3RlcCBzYXlpbmcgbXkg4oCcRFZE4oCdIHdhcyBiYWQuCgpXaGF0IGRvZXMgeW91ciBndWVzdCBj b25maWcgZmlsZSBsb29rIGxpa2UsIGluIHBhcnRpY3VsYXIgdGhlIGRpc2sgbGluZS4KCklzIHRo ZXJlIGFueSBjaGFuY2UgdGhhdCB5b3UgaGF2ZSBhY2NpZGVudGFsbHkgcG9pbnRlZCB0aGUgVk0n cyBkaXNrcyBhdCBvbmUgb3IgbW9yZSBvZiB0aGUgcGh5c2ljYWwgZGlza3Mgd2hpY2ggbWFrZXMg dXAgeW91ciBSQUlEIGFycmF5PwoKSWFuLgotLS0tCgpOb3BlLCBubyBjaGFuY2UuCgpIZXJlIGlz IHRoZSBlbnRpcmUgY29uZmlnOgoKa2VybmVsID0gIi91c3IvbGliL3hlbi9ib290L2h2bWxvYWRl ciIKYnVpbGRlcj0naHZtJwptZW1vcnkgPSAxMDI0CiNtZW1vcnkgPSAyMDQ4CgojIFNob3VsZCBi ZSBhdCBsZWFzdCAyS0IgcGVyIE1CIG9mIGRvbWFpbiBtZW1vcnksIHBsdXMgYSBmZXcgTUIgcGVy IHZjcHUuCnNoYWRvd19tZW1vcnkgPSA4Cm5hbWUgPSAiV2luN3g4Nl9CYXNlIgp2ZmIgPSBbICd0 eXBlPXZuYyx2bmNkaXNwbGF5PTExLHZuY3Bhc3N3ZD1ldmExdW5pdCcgXQp2aWYgPSBbICdtYWM9 MDA6MTY6M0U6MzM6NUU6RjksIGJyaWRnZT14ZW5icjAnIF0KYWNwaSA9IDEKYXBpYyA9IDEKZGlz ayA9IFsgJ3RhcDphaW86Ly9pbWFnZXMveGVuX2ltYWdlcy9XaW43eDg2X0Jhc2UuaW1nLGhkYSx3 JywgJ3RhcDphaW86Ly9pbWFnZXMvaXNvX2ltYWdlcy9lbl93aW5kb3dzXzdfZW50ZXJwcmlzZV93 aXRoX3NwMV94ODZfZHZkX3VfNjc3NzEwLmlzbyxoZGM6Y2Ryb20scicgXQojZGlzayA9IFsgJ3Rh cDphaW86Ly9pbWFnZXMveGVuX2ltYWdlcy9XaW43eDg2X2Jhc2UuaW1nLGhkYSx3JyBdCgpkZXZp Y2VfbW9kZWwgPSAnL3Vzci9saWI2NC94ZW4vYmluL3FlbXUtZG0nCgojLS0tLS0tLS0tLS0tLS0t LS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0t LS0tLS0KIyBib290IG9uIGZsb3BweSAoYSksIGhhcmQgZGlzayAoYykgb3IgQ0QtUk9NIChkKQoj IGRlZmF1bHQ6IGhhcmQgZGlzaywgY2Qtcm9tLCBmbG9wcHkKYm9vdD0iZGMiCnZuY3VudXNlZD0x CnNkbD0wCgpzZXJpYWw9J3B0eScKdXNiZGV2aWNlPSd0YWJsZXQnCnZjcHVzPTEKY3B1cyA9IFsn MSddCmxvY2FsdGltZSA9IDEKdXNiID0gMQoKCgpfX19fX19fX19fX19fX19fX19fX19fX19fX19f X19fX19fX19fX19fX19fX19fXwpYZW4tdXNlcnMgbWFpbGluZyBsaXN0Clhlbi11c2Vyc0BsaXN0 cy54ZW4ub3JnCmh0dHA6Ly9saXN0cy54ZW4ub3JnL3hlbi11c2Vycw== From xen-users-bounces@lists.xen.org Sun Sep 16 19:37:25 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Sun, 16 Sep 2012 19:37:25 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TDKds-0008H3-Jb; Sun, 16 Sep 2012 19:36:32 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TDKdq-0008Gv-Q5 for xen-users@lists.xen.org; Sun, 16 Sep 2012 19:36:30 +0000 Received: from [85.158.143.35:35940] by server-3.bemta-4.messagelabs.com id C0/08-08232-E3A26505; Sun, 16 Sep 2012 19:36:30 +0000 X-Env-Sender: myrdhn@gmail.com X-Msg-Ref: server-13.tower-21.messagelabs.com!1347824186!17125715!1 X-Originating-IP: [209.85.216.173] X-SpamReason: No, hits=0.3 required=7.0 tests=ML_RADAR_SPEW_LINKS_14, RCVD_BY_IP,spamassassin: X-StarScan-Received: X-StarScan-Version: 6.6.1.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 18533 invoked from network); 16 Sep 2012 19:36:27 -0000 Received: from mail-qc0-f173.google.com (HELO mail-qc0-f173.google.com) (209.85.216.173) by server-13.tower-21.messagelabs.com with RC4-SHA encrypted SMTP; 16 Sep 2012 19:36:27 -0000 Received: by qcab12 with SMTP id b12so5315518qca.32 for ; Sun, 16 Sep 2012 12:36:26 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=from:to:cc:references:in-reply-to:subject:date:message-id :mime-version:content-type:content-transfer-encoding:x-mailer :thread-index:content-language; bh=o68+1syeGnrXPoi8ttMmtPLpArIEpfqii4Jn9qGyBZk=; b=LXcDSYmA+UXbYb+HD9OpLMqWvBon1OJnHxZMDjYGkP613F2DOnad2TIjsbe9y6Ynbx YqYWefIK0yV4DlLbMBtliWSr01u/k3LL3giVdNnYhyuyFFNg4+CF6jf8qxMAxrpc4pPy bvBgHblyVUCHtAlaEhasoYgn+o0CdKmPuMRice6aLXoJ1u5YFb6o5Zn2cAbXDpH6XLnp lduFl4Z3zVOsoKuPvr0M1upc8fuJjPeIOobskmbI4Q5lsHiN33nko/j/4fM8C/kVyCuJ 8RF14B9k7Ffi7P6UxfNur8KO8C7nR7zotpMlLXB21DoMkNqbXcyso9y+F3gKRR79wm2l I8qw== Received: by 10.224.53.18 with SMTP id k18mr23200090qag.1.1347824186101; Sun, 16 Sep 2012 12:36:26 -0700 (PDT) Received: from Belldandy (c-76-119-253-48.hsd1.ma.comcast.net. [76.119.253.48]) by mx.google.com with ESMTPS id et6sm12012243qab.8.2012.09.16.12.36.25 (version=TLSv1/SSLv3 cipher=OTHER); Sun, 16 Sep 2012 12:36:25 -0700 (PDT) From: "Marc Tousignant" To: "'Ian Campbell'" References: <003601cd9430$a381db70$ea859250$@gmail.com> <1347818899.25803.75.camel@dagon.hellion.org.uk> In-Reply-To: <1347818899.25803.75.camel@dagon.hellion.org.uk> Date: Sun, 16 Sep 2012 15:36:28 -0400 Message-ID: <004d01cd9442$91c2d670$b5488350$@gmail.com> MIME-Version: 1.0 X-Mailer: Microsoft Outlook 14.0 Thread-Index: AQEtIveC4IhcOcllJOhnnzkXfTJ4EAF4akKmmMJ7RwA= Content-Language: en-us Cc: xen-users@lists.xen.org Subject: Re: [Xen-users] Setting up XEN domU causes RAID5 to fail? X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: base64 Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org T24gU3VuLCAyMDEyLTA5LTE2IGF0IDE4OjI4ICswMTAwLCBNYXJjIFRvdXNpZ25hbnQgd3JvdGU6 Cgo+IEkgdGhlbiBjcmVhdGVkIHNldmVyYWwgLmltZyBmaWxlcyBpbiB0aGUgeGVuX2ltYWdlcyBm b2xkZXIgdXNpbmcgZGQuCj4gRm9yIGV4YW1wbGUgKGRkIGlmPS9kZXYvemVybyBvZj0vaW1hZ2Vz L3hlbl9pbWFnZXMvV2luN3g4Nl9CYXNlLmltZwo+IGJzPTEgY291bnQ9MSBzZWVrPTUwRykKWy4u Ll0KPiBJIGdvdCB0byB0aGUgcG9pbnQgd2hlcmUgaXQgZm9ybWF0dGVkIHRoZSDigJxkcml2ZeKA nSBhbmQgc3RhcnRlZCAKPiBpbnN0YWxsaW5nLCBpdCBmYWlsZWQgb24gdGhlIGV4dHJhY3Rpb24g c3RlcCBzYXlpbmcgbXkg4oCcRFZE4oCdIHdhcyBiYWQuCgpXaGF0IGRvZXMgeW91ciBndWVzdCBj b25maWcgZmlsZSBsb29rIGxpa2UsIGluIHBhcnRpY3VsYXIgdGhlIGRpc2sgbGluZS4KCklzIHRo ZXJlIGFueSBjaGFuY2UgdGhhdCB5b3UgaGF2ZSBhY2NpZGVudGFsbHkgcG9pbnRlZCB0aGUgVk0n cyBkaXNrcyBhdCBvbmUgb3IgbW9yZSBvZiB0aGUgcGh5c2ljYWwgZGlza3Mgd2hpY2ggbWFrZXMg dXAgeW91ciBSQUlEIGFycmF5PwoKSWFuLgotLS0tCgpOb3BlLCBubyBjaGFuY2UuCgpIZXJlIGlz IHRoZSBlbnRpcmUgY29uZmlnOgoKa2VybmVsID0gIi91c3IvbGliL3hlbi9ib290L2h2bWxvYWRl ciIKYnVpbGRlcj0naHZtJwptZW1vcnkgPSAxMDI0CiNtZW1vcnkgPSAyMDQ4CgojIFNob3VsZCBi ZSBhdCBsZWFzdCAyS0IgcGVyIE1CIG9mIGRvbWFpbiBtZW1vcnksIHBsdXMgYSBmZXcgTUIgcGVy IHZjcHUuCnNoYWRvd19tZW1vcnkgPSA4Cm5hbWUgPSAiV2luN3g4Nl9CYXNlIgp2ZmIgPSBbICd0 eXBlPXZuYyx2bmNkaXNwbGF5PTExLHZuY3Bhc3N3ZD1ldmExdW5pdCcgXQp2aWYgPSBbICdtYWM9 MDA6MTY6M0U6MzM6NUU6RjksIGJyaWRnZT14ZW5icjAnIF0KYWNwaSA9IDEKYXBpYyA9IDEKZGlz ayA9IFsgJ3RhcDphaW86Ly9pbWFnZXMveGVuX2ltYWdlcy9XaW43eDg2X0Jhc2UuaW1nLGhkYSx3 JywgJ3RhcDphaW86Ly9pbWFnZXMvaXNvX2ltYWdlcy9lbl93aW5kb3dzXzdfZW50ZXJwcmlzZV93 aXRoX3NwMV94ODZfZHZkX3VfNjc3NzEwLmlzbyxoZGM6Y2Ryb20scicgXQojZGlzayA9IFsgJ3Rh cDphaW86Ly9pbWFnZXMveGVuX2ltYWdlcy9XaW43eDg2X2Jhc2UuaW1nLGhkYSx3JyBdCgpkZXZp Y2VfbW9kZWwgPSAnL3Vzci9saWI2NC94ZW4vYmluL3FlbXUtZG0nCgojLS0tLS0tLS0tLS0tLS0t LS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0t LS0tLS0KIyBib290IG9uIGZsb3BweSAoYSksIGhhcmQgZGlzayAoYykgb3IgQ0QtUk9NIChkKQoj IGRlZmF1bHQ6IGhhcmQgZGlzaywgY2Qtcm9tLCBmbG9wcHkKYm9vdD0iZGMiCnZuY3VudXNlZD0x CnNkbD0wCgpzZXJpYWw9J3B0eScKdXNiZGV2aWNlPSd0YWJsZXQnCnZjcHVzPTEKY3B1cyA9IFsn MSddCmxvY2FsdGltZSA9IDEKdXNiID0gMQoKCgpfX19fX19fX19fX19fX19fX19fX19fX19fX19f X19fX19fX19fX19fX19fX19fXwpYZW4tdXNlcnMgbWFpbGluZyBsaXN0Clhlbi11c2Vyc0BsaXN0 cy54ZW4ub3JnCmh0dHA6Ly9saXN0cy54ZW4ub3JnL3hlbi11c2Vycw== From xen-users-bounces@lists.xen.org Sun Sep 16 20:07:07 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Sun, 16 Sep 2012 20:07:07 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TDL6Z-0000cV-SA; Sun, 16 Sep 2012 20:06:11 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TDL6Y-0000cL-5P for xen-users@lists.xen.org; Sun, 16 Sep 2012 20:06:10 +0000 Received: from [85.158.137.99:63094] by server-12.bemta-3.messagelabs.com id 77/0A-10384-13136505; Sun, 16 Sep 2012 20:06:09 +0000 X-Env-Sender: myrdhn@gmail.com X-Msg-Ref: server-15.tower-217.messagelabs.com!1347825967!15531042!1 X-Originating-IP: [209.85.216.173] X-SpamReason: No, hits=0.3 required=7.0 tests=ML_RADAR_SPEW_LINKS_14, RCVD_BY_IP,spamassassin: X-StarScan-Received: X-StarScan-Version: 6.6.1.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 31876 invoked from network); 16 Sep 2012 20:06:08 -0000 Received: from mail-qc0-f173.google.com (HELO mail-qc0-f173.google.com) (209.85.216.173) by server-15.tower-217.messagelabs.com with RC4-SHA encrypted SMTP; 16 Sep 2012 20:06:08 -0000 Received: by qcab12 with SMTP id b12so5330263qca.32 for ; Sun, 16 Sep 2012 13:06:07 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=from:to:cc:references:in-reply-to:subject:date:message-id :mime-version:content-type:content-transfer-encoding:x-mailer :thread-index:content-language; bh=QVvsG9Gm4QZvKBYp9WhYFwU5vupi5STyIobwCkZ3q7o=; b=qfN2jWfXGAAJ20imRy9E6S2sb6M5brqOu0L28aYMtAddHjKXvVEDt/4tGvi2UH/D/X h6qMlgIH7JUoy0GX242J7YJHgCdYE/3CGcpEoEazPetBhiRNI3ysuj+M5ZIKl05wQ6PT sxKlcijp9+CdRlgss8UlmkVWF0e2PJJs+Emscts+EkK3AVHizZteU3XySSHiSmYTzQJg jZAdbJ8W4Jy9KIIAw2G200oI/Fuq+mb9yAV/o/of724g4BSR1e+XYPcVZHwQFekkqa3r oe2Fym6isW2KDf9r2FlPiCvudpgbGP/JBG7+VSjdyyCW+iolyfVP7/eZebwvw7AmcmPm LBGg== Received: by 10.224.71.74 with SMTP id g10mr23026013qaj.34.1347825967326; Sun, 16 Sep 2012 13:06:07 -0700 (PDT) Received: from Belldandy (c-76-119-253-48.hsd1.ma.comcast.net. [76.119.253.48]) by mx.google.com with ESMTPS id go9sm12113260qab.21.2012.09.16.13.06.05 (version=TLSv1/SSLv3 cipher=OTHER); Sun, 16 Sep 2012 13:06:06 -0700 (PDT) From: "Marc Tousignant" To: "'Ian Campbell'" References: <003601cd9430$a381db70$ea859250$@gmail.com> <1347818899.25803.75.camel@dagon.hellion.org.uk> In-Reply-To: <1347818899.25803.75.camel@dagon.hellion.org.uk> Date: Sun, 16 Sep 2012 16:06:08 -0400 Message-ID: <004e01cd9446$b7636b20$262a4160$@gmail.com> MIME-Version: 1.0 X-Mailer: Microsoft Outlook 14.0 Thread-Index: AQEtIveC4IhcOcllJOhnnzkXfTJ4EAF4akKmmMKDcPA= Content-Language: en-us Cc: xen-users@lists.xen.org Subject: Re: [Xen-users] Setting up XEN domU causes RAID5 to fail? X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: base64 Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org RllJLCBJIHN3aXRjaGVkIHRvIGZpbGU6IGFuZCBzdGlsbCB0aGUgc2FtZSBpc3N1ZSBvY2N1cnJl ZCwgd2l0aCBvbmUgZXhjZXB0aW9uLi4gVGhpcyB0aW1lIGl0ICJsb3N0IiB0aGUgUkFJRCBtZW1i ZXJzIHdoaWxlIGJvb3Rpbmcgb2ZmIHRoZSBJU08uIEkgaGFkbid0IGV2ZW4gZ290dGVuIHRvIHRo ZSBpbnN0YWxsIHNjcmVlbnMgeWV0LgoKLS0tLS1PcmlnaW5hbCBNZXNzYWdlLS0tLS0KRnJvbTog SWFuIENhbXBiZWxsIFttYWlsdG86SWFuLkNhbXBiZWxsQGNpdHJpeC5jb21dIApTZW50OiBTdW5k YXksIFNlcHRlbWJlciAxNiwgMjAxMiAyOjA4IFBNClRvOiBNYXJjIFRvdXNpZ25hbnQKQ2M6IHhl bi11c2Vyc0BsaXN0cy54ZW4ub3JnClN1YmplY3Q6IFJlOiBbWGVuLXVzZXJzXSBTZXR0aW5nIHVw IFhFTiBkb21VIGNhdXNlcyBSQUlENSB0byBmYWlsPwoKT24gU3VuLCAyMDEyLTA5LTE2IGF0IDE4 OjI4ICswMTAwLCBNYXJjIFRvdXNpZ25hbnQgd3JvdGU6Cgo+IEkgdGhlbiBjcmVhdGVkIHNldmVy YWwgLmltZyBmaWxlcyBpbiB0aGUgeGVuX2ltYWdlcyBmb2xkZXIgdXNpbmcgZGQuCj4gRm9yIGV4 YW1wbGUgKGRkIGlmPS9kZXYvemVybyBvZj0vaW1hZ2VzL3hlbl9pbWFnZXMvV2luN3g4Nl9CYXNl LmltZwo+IGJzPTEgY291bnQ9MSBzZWVrPTUwRykKWy4uLl0KPiBJIGdvdCB0byB0aGUgcG9pbnQg d2hlcmUgaXQgZm9ybWF0dGVkIHRoZSDigJxkcml2ZeKAnSBhbmQgc3RhcnRlZCAKPiBpbnN0YWxs aW5nLCBpdCBmYWlsZWQgb24gdGhlIGV4dHJhY3Rpb24gc3RlcCBzYXlpbmcgbXkg4oCcRFZE4oCd IHdhcyBiYWQuCgpXaGF0IGRvZXMgeW91ciBndWVzdCBjb25maWcgZmlsZSBsb29rIGxpa2UsIGlu IHBhcnRpY3VsYXIgdGhlIGRpc2sgbGluZS4KCklzIHRoZXJlIGFueSBjaGFuY2UgdGhhdCB5b3Ug aGF2ZSBhY2NpZGVudGFsbHkgcG9pbnRlZCB0aGUgVk0ncyBkaXNrcyBhdCBvbmUgb3IgbW9yZSBv ZiB0aGUgcGh5c2ljYWwgZGlza3Mgd2hpY2ggbWFrZXMgdXAgeW91ciBSQUlEIGFycmF5PwoKSWFu LgoKCgpfX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fXwpYZW4t dXNlcnMgbWFpbGluZyBsaXN0Clhlbi11c2Vyc0BsaXN0cy54ZW4ub3JnCmh0dHA6Ly9saXN0cy54 ZW4ub3JnL3hlbi11c2Vycw== From xen-users-bounces@lists.xen.org Sun Sep 16 20:07:07 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Sun, 16 Sep 2012 20:07:07 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TDL6Z-0000cV-SA; Sun, 16 Sep 2012 20:06:11 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TDL6Y-0000cL-5P for xen-users@lists.xen.org; Sun, 16 Sep 2012 20:06:10 +0000 Received: from [85.158.137.99:63094] by server-12.bemta-3.messagelabs.com id 77/0A-10384-13136505; Sun, 16 Sep 2012 20:06:09 +0000 X-Env-Sender: myrdhn@gmail.com X-Msg-Ref: server-15.tower-217.messagelabs.com!1347825967!15531042!1 X-Originating-IP: [209.85.216.173] X-SpamReason: No, hits=0.3 required=7.0 tests=ML_RADAR_SPEW_LINKS_14, RCVD_BY_IP,spamassassin: X-StarScan-Received: X-StarScan-Version: 6.6.1.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 31876 invoked from network); 16 Sep 2012 20:06:08 -0000 Received: from mail-qc0-f173.google.com (HELO mail-qc0-f173.google.com) (209.85.216.173) by server-15.tower-217.messagelabs.com with RC4-SHA encrypted SMTP; 16 Sep 2012 20:06:08 -0000 Received: by qcab12 with SMTP id b12so5330263qca.32 for ; Sun, 16 Sep 2012 13:06:07 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=from:to:cc:references:in-reply-to:subject:date:message-id :mime-version:content-type:content-transfer-encoding:x-mailer :thread-index:content-language; bh=QVvsG9Gm4QZvKBYp9WhYFwU5vupi5STyIobwCkZ3q7o=; b=qfN2jWfXGAAJ20imRy9E6S2sb6M5brqOu0L28aYMtAddHjKXvVEDt/4tGvi2UH/D/X h6qMlgIH7JUoy0GX242J7YJHgCdYE/3CGcpEoEazPetBhiRNI3ysuj+M5ZIKl05wQ6PT sxKlcijp9+CdRlgss8UlmkVWF0e2PJJs+Emscts+EkK3AVHizZteU3XySSHiSmYTzQJg jZAdbJ8W4Jy9KIIAw2G200oI/Fuq+mb9yAV/o/of724g4BSR1e+XYPcVZHwQFekkqa3r oe2Fym6isW2KDf9r2FlPiCvudpgbGP/JBG7+VSjdyyCW+iolyfVP7/eZebwvw7AmcmPm LBGg== Received: by 10.224.71.74 with SMTP id g10mr23026013qaj.34.1347825967326; Sun, 16 Sep 2012 13:06:07 -0700 (PDT) Received: from Belldandy (c-76-119-253-48.hsd1.ma.comcast.net. [76.119.253.48]) by mx.google.com with ESMTPS id go9sm12113260qab.21.2012.09.16.13.06.05 (version=TLSv1/SSLv3 cipher=OTHER); Sun, 16 Sep 2012 13:06:06 -0700 (PDT) From: "Marc Tousignant" To: "'Ian Campbell'" References: <003601cd9430$a381db70$ea859250$@gmail.com> <1347818899.25803.75.camel@dagon.hellion.org.uk> In-Reply-To: <1347818899.25803.75.camel@dagon.hellion.org.uk> Date: Sun, 16 Sep 2012 16:06:08 -0400 Message-ID: <004e01cd9446$b7636b20$262a4160$@gmail.com> MIME-Version: 1.0 X-Mailer: Microsoft Outlook 14.0 Thread-Index: AQEtIveC4IhcOcllJOhnnzkXfTJ4EAF4akKmmMKDcPA= Content-Language: en-us Cc: xen-users@lists.xen.org Subject: Re: [Xen-users] Setting up XEN domU causes RAID5 to fail? X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: base64 Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org RllJLCBJIHN3aXRjaGVkIHRvIGZpbGU6IGFuZCBzdGlsbCB0aGUgc2FtZSBpc3N1ZSBvY2N1cnJl ZCwgd2l0aCBvbmUgZXhjZXB0aW9uLi4gVGhpcyB0aW1lIGl0ICJsb3N0IiB0aGUgUkFJRCBtZW1i ZXJzIHdoaWxlIGJvb3Rpbmcgb2ZmIHRoZSBJU08uIEkgaGFkbid0IGV2ZW4gZ290dGVuIHRvIHRo ZSBpbnN0YWxsIHNjcmVlbnMgeWV0LgoKLS0tLS1PcmlnaW5hbCBNZXNzYWdlLS0tLS0KRnJvbTog SWFuIENhbXBiZWxsIFttYWlsdG86SWFuLkNhbXBiZWxsQGNpdHJpeC5jb21dIApTZW50OiBTdW5k YXksIFNlcHRlbWJlciAxNiwgMjAxMiAyOjA4IFBNClRvOiBNYXJjIFRvdXNpZ25hbnQKQ2M6IHhl bi11c2Vyc0BsaXN0cy54ZW4ub3JnClN1YmplY3Q6IFJlOiBbWGVuLXVzZXJzXSBTZXR0aW5nIHVw IFhFTiBkb21VIGNhdXNlcyBSQUlENSB0byBmYWlsPwoKT24gU3VuLCAyMDEyLTA5LTE2IGF0IDE4 OjI4ICswMTAwLCBNYXJjIFRvdXNpZ25hbnQgd3JvdGU6Cgo+IEkgdGhlbiBjcmVhdGVkIHNldmVy YWwgLmltZyBmaWxlcyBpbiB0aGUgeGVuX2ltYWdlcyBmb2xkZXIgdXNpbmcgZGQuCj4gRm9yIGV4 YW1wbGUgKGRkIGlmPS9kZXYvemVybyBvZj0vaW1hZ2VzL3hlbl9pbWFnZXMvV2luN3g4Nl9CYXNl LmltZwo+IGJzPTEgY291bnQ9MSBzZWVrPTUwRykKWy4uLl0KPiBJIGdvdCB0byB0aGUgcG9pbnQg d2hlcmUgaXQgZm9ybWF0dGVkIHRoZSDigJxkcml2ZeKAnSBhbmQgc3RhcnRlZCAKPiBpbnN0YWxs aW5nLCBpdCBmYWlsZWQgb24gdGhlIGV4dHJhY3Rpb24gc3RlcCBzYXlpbmcgbXkg4oCcRFZE4oCd IHdhcyBiYWQuCgpXaGF0IGRvZXMgeW91ciBndWVzdCBjb25maWcgZmlsZSBsb29rIGxpa2UsIGlu IHBhcnRpY3VsYXIgdGhlIGRpc2sgbGluZS4KCklzIHRoZXJlIGFueSBjaGFuY2UgdGhhdCB5b3Ug aGF2ZSBhY2NpZGVudGFsbHkgcG9pbnRlZCB0aGUgVk0ncyBkaXNrcyBhdCBvbmUgb3IgbW9yZSBv ZiB0aGUgcGh5c2ljYWwgZGlza3Mgd2hpY2ggbWFrZXMgdXAgeW91ciBSQUlEIGFycmF5PwoKSWFu LgoKCgpfX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fXwpYZW4t dXNlcnMgbWFpbGluZyBsaXN0Clhlbi11c2Vyc0BsaXN0cy54ZW4ub3JnCmh0dHA6Ly9saXN0cy54 ZW4ub3JnL3hlbi11c2Vycw== From xen-users-bounces@lists.xen.org Sun Sep 16 20:52:24 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Sun, 16 Sep 2012 20:52:24 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TDLoO-00015N-OA; Sun, 16 Sep 2012 20:51:28 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TDLoN-00015I-Lf for xen-users@lists.xen.org; Sun, 16 Sep 2012 20:51:27 +0000 Received: from [85.158.143.99:6263] by server-3.bemta-4.messagelabs.com id 42/A9-08232-ECB36505; Sun, 16 Sep 2012 20:51:26 +0000 X-Env-Sender: andy@strugglers.net X-Msg-Ref: server-11.tower-216.messagelabs.com!1347828686!23047317!1 X-Originating-IP: [85.119.80.223] X-SpamReason: No, hits=0.0 required=7.0 tests=ML_RADAR_SPEW_LINKS_23, spamassassin: X-StarScan-Received: X-StarScan-Version: 6.6.1.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 31532 invoked from network); 16 Sep 2012 20:51:26 -0000 Received: from bitfolk.com (HELO mail.bitfolk.com) (85.119.80.223) by server-11.tower-216.messagelabs.com with AES256-SHA encrypted SMTP; 16 Sep 2012 20:51:26 -0000 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=bitfolk.com; s=alpha; h=Subject:In-Reply-To:Content-Type:MIME-Version:References:Message-ID:To:From:Date; bh=9cyx3632jQHWMxGIUgq3vKR9zX+0Q2UTH13pjXttVfk=; b=0swvO3g/j+F/0SD7F0A8RosuV3r05W+4BZM+UYm6ZsV1LvpwqbvSkQvw1hKw6QdlqYR6CqUvB5t1fN6AASYUs40xdXbzG69h9tSqO4/oAE3p3vwbFjWTpRp00a6qfkq4; Received: from andy by mail.bitfolk.com with local (Exim 4.72) (envelope-from ) id 1TDLoL-0000o8-M4 for xen-users@lists.xen.org; Sun, 16 Sep 2012 20:51:25 +0000 Date: Sun, 16 Sep 2012 20:51:25 +0000 From: Andy Smith To: xen-users@lists.xen.org Message-ID: <20120916205125.GD3867@bitfolk.com> References: <20120916122326.GA3867@bitfolk.com> MIME-Version: 1.0 Content-Disposition: inline In-Reply-To: OpenPGP: id=BF15490B; url=http://strugglers.net/~andy/pubkey.asc X-URL: http://strugglers.net/wiki/User:Andy User-Agent: Mutt/1.5.20 (2009-06-14) X-Virus-Scanner: Scanned by ClamAV on mail.bitfolk.com at Sun, 16 Sep 2012 20:51:25 +0000 X-SA-Exim-Connect-IP: X-SA-Exim-Mail-From: andy@strugglers.net X-Spam-Checker-Version: SpamAssassin 3.3.1 (2010-03-16) on spamd2.lon.bitfolk.com X-Spam-Level: X-Spam-ASN: X-Spam-Status: No, score=-0.0 required=5.0 tests=NO_RELAYS shortcircuit=no autolearn=disabled version=3.3.1 X-Spam-Report: * -0.0 NO_RELAYS Informational: message was not relayed via SMTP X-SA-Exim-Version: 4.2.1 (built Mon, 22 Mar 2010 06:51:10 +0000) X-SA-Exim-Scanned: Yes (on mail.bitfolk.com) Subject: Re: [Xen-users] How are you measuring CPU usage? X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org Hi Peter, On Sun, Sep 16, 2012 at 12:04:43PM -0700, Peter Phaal wrote: > You might want to take a look at installing Host sFlow agents on your > hypervisors. The agent is extremely lightweight, directly accesses > statistics using libxenstat and exports them using the sFlow protocol > (XDR/UDP) to a remote collector. > http://host-sflow.sourceforge.net/ Interesting, thanks. I'm probably not interested in replacing *all* of my stats with this right now, but it looks like libxenstat and this may be a good start if I want to do higher-frequency stats gathering for my own purposes. > Are you using the Open vSwitch? It also includes sFlow support and can > give you a better handle on network performance: > http://openvswitch.org/ Not yet, but that is good to know, thanks. Cheers, Andy _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Sun Sep 16 20:52:24 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Sun, 16 Sep 2012 20:52:24 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TDLoO-00015N-OA; Sun, 16 Sep 2012 20:51:28 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TDLoN-00015I-Lf for xen-users@lists.xen.org; Sun, 16 Sep 2012 20:51:27 +0000 Received: from [85.158.143.99:6263] by server-3.bemta-4.messagelabs.com id 42/A9-08232-ECB36505; Sun, 16 Sep 2012 20:51:26 +0000 X-Env-Sender: andy@strugglers.net X-Msg-Ref: server-11.tower-216.messagelabs.com!1347828686!23047317!1 X-Originating-IP: [85.119.80.223] X-SpamReason: No, hits=0.0 required=7.0 tests=ML_RADAR_SPEW_LINKS_23, spamassassin: X-StarScan-Received: X-StarScan-Version: 6.6.1.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 31532 invoked from network); 16 Sep 2012 20:51:26 -0000 Received: from bitfolk.com (HELO mail.bitfolk.com) (85.119.80.223) by server-11.tower-216.messagelabs.com with AES256-SHA encrypted SMTP; 16 Sep 2012 20:51:26 -0000 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=bitfolk.com; s=alpha; h=Subject:In-Reply-To:Content-Type:MIME-Version:References:Message-ID:To:From:Date; bh=9cyx3632jQHWMxGIUgq3vKR9zX+0Q2UTH13pjXttVfk=; b=0swvO3g/j+F/0SD7F0A8RosuV3r05W+4BZM+UYm6ZsV1LvpwqbvSkQvw1hKw6QdlqYR6CqUvB5t1fN6AASYUs40xdXbzG69h9tSqO4/oAE3p3vwbFjWTpRp00a6qfkq4; Received: from andy by mail.bitfolk.com with local (Exim 4.72) (envelope-from ) id 1TDLoL-0000o8-M4 for xen-users@lists.xen.org; Sun, 16 Sep 2012 20:51:25 +0000 Date: Sun, 16 Sep 2012 20:51:25 +0000 From: Andy Smith To: xen-users@lists.xen.org Message-ID: <20120916205125.GD3867@bitfolk.com> References: <20120916122326.GA3867@bitfolk.com> MIME-Version: 1.0 Content-Disposition: inline In-Reply-To: OpenPGP: id=BF15490B; url=http://strugglers.net/~andy/pubkey.asc X-URL: http://strugglers.net/wiki/User:Andy User-Agent: Mutt/1.5.20 (2009-06-14) X-Virus-Scanner: Scanned by ClamAV on mail.bitfolk.com at Sun, 16 Sep 2012 20:51:25 +0000 X-SA-Exim-Connect-IP: X-SA-Exim-Mail-From: andy@strugglers.net X-Spam-Checker-Version: SpamAssassin 3.3.1 (2010-03-16) on spamd2.lon.bitfolk.com X-Spam-Level: X-Spam-ASN: X-Spam-Status: No, score=-0.0 required=5.0 tests=NO_RELAYS shortcircuit=no autolearn=disabled version=3.3.1 X-Spam-Report: * -0.0 NO_RELAYS Informational: message was not relayed via SMTP X-SA-Exim-Version: 4.2.1 (built Mon, 22 Mar 2010 06:51:10 +0000) X-SA-Exim-Scanned: Yes (on mail.bitfolk.com) Subject: Re: [Xen-users] How are you measuring CPU usage? X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org Hi Peter, On Sun, Sep 16, 2012 at 12:04:43PM -0700, Peter Phaal wrote: > You might want to take a look at installing Host sFlow agents on your > hypervisors. The agent is extremely lightweight, directly accesses > statistics using libxenstat and exports them using the sFlow protocol > (XDR/UDP) to a remote collector. > http://host-sflow.sourceforge.net/ Interesting, thanks. I'm probably not interested in replacing *all* of my stats with this right now, but it looks like libxenstat and this may be a good start if I want to do higher-frequency stats gathering for my own purposes. > Are you using the Open vSwitch? It also includes sFlow support and can > give you a better handle on network performance: > http://openvswitch.org/ Not yet, but that is good to know, thanks. Cheers, Andy _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Sun Sep 16 22:31:10 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Sun, 16 Sep 2012 22:31:10 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TDNLp-00023f-Az; Sun, 16 Sep 2012 22:30:05 +0000 Received: from mail27.messagelabs.com ([193.109.254.147]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TDNLn-00023a-Rr for xen-users@lists.xen.org; Sun, 16 Sep 2012 22:30:04 +0000 X-Env-Sender: cdelorme@gmail.com X-Msg-Ref: server-10.tower-27.messagelabs.com!1347834596!6064197!1 X-Originating-IP: [209.85.219.45] X-SpamReason: No, hits=0.4 required=7.0 tests=HTML_30_40,HTML_MESSAGE, ML_RADAR_SPEW_LINKS_14,RCVD_BY_IP,spamassassin: X-StarScan-Received: X-StarScan-Version: 6.6.1.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 10223 invoked from network); 16 Sep 2012 22:29:57 -0000 Received: from mail-oa0-f45.google.com (HELO mail-oa0-f45.google.com) (209.85.219.45) by server-10.tower-27.messagelabs.com with RC4-SHA encrypted SMTP; 16 Sep 2012 22:29:57 -0000 Received: by oagn12 with SMTP id n12so5270270oag.32 for ; Sun, 16 Sep 2012 15:29:55 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:date:message-id:subject:from:to:content-type; bh=mY34qKDpituWKjxdjgh0z5HwH+BhOwRK13Ovbr+znx8=; b=Pg5NeBJ+/Ydjt49L19lPp0hOQCa3i86P4xc3sRBIAJvMqLO1y781xZq2/liBi31rD8 ZGNRwgyG/HopubUZtLQCrnkuo9dhLJ/p5dHFlmcrVfuDSRNkhbJWeuBH60tl3tVZY1YT GxpLtMeWyHTTpC3Ti+WNj/2lLdcriEycJTYkOhwFt94XjWSdk/abY0dmIuEHWVhRmqzH PEyo9izkeJshIMRaGvuyWM2CZ776ZRqOlkwpWScHIfM47AsGWDRsafynDjlc4UeUuEP7 Cshy7z580OyqtKwdftudvrEPjliDiWjqE4UDxJQkyG9Wyxc6p5xKw9TxcChrCZL6y7xO Yv1w== MIME-Version: 1.0 Received: by 10.60.170.229 with SMTP id ap5mr9825534oec.101.1347834595580; Sun, 16 Sep 2012 15:29:55 -0700 (PDT) Received: by 10.76.115.197 with HTTP; Sun, 16 Sep 2012 15:29:55 -0700 (PDT) Date: Sun, 16 Sep 2012 18:29:55 -0400 Message-ID: From: Casey DeLorme To: xen-users@lists.xen.org Subject: [Xen-users] Personal Comprehensive Xen Documentation X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============9209528223388011864==" Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org --===============9209528223388011864== Content-Type: multipart/alternative; boundary=bcaec54b4ac0491c3c04c9d932af --bcaec54b4ac0491c3c04c9d932af Content-Type: text/plain; charset=ISO-8859-1 Hello Xen Users, I have been testing Xen 4.2 since April, and have just finished creating comprehensive documentation to reproduce my personal system. I have posted the documentation on the Xen Wiki: http://wiki.xen.org/wiki/Comprehensive_Xen_Debian_Wheezy_PCI_Passthrough_Tutorial Additionally I created a visual aid that walks through the entire process as well: http://www.youtube.com/watch?v=mnTj6_kDIeg&list=PLC70DC33D993CEB44&feature=plpp_play_all Success with Xen seems to depend on a lot of variables, so my documentation is very specific, but it should be useful regardless. The guide covers: - Installing UEFI Debian Wheezy Beta 1 Dom0 - Compiling Custom Linux Kernel for Xen - Compiling Xen 4.2 - Configuring Xen 4.2 - Installing Windows HVM - PCI Passthrough for USB and Graphics Devices The last video is a performance demonstration video of a Windows 7 HVM. I hope this helps others looking to do something similar, and would appreciate feedback to improve it in the future. Thank you, ~Casey DeLorme --bcaec54b4ac0491c3c04c9d932af Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable
Hello Xen Users,

I have been testing Xen 4.2 = since April, and have just finished creating comprehensive documentation to= reproduce my personal system.

I have posted the d= ocumentation on the Xen Wiki:

Additionally I = created a visual aid that walks through the entire process as well:
=

The guide covers:

- Installing= UEFI Debian Wheezy Beta 1 Dom0
- Compiling Custom Linux Kernel for Xen
- Compiling Xen 4.2<= /div>
- Configuring Xen 4.2
- Installing Windows HVM
- PCI Passthrough for USB and Graphics Devices

The last video is a performance demonstration video of a Windows 7 HVM.

I hope this helps others looking to do something simi= lar, and would appreciate feedback to improve it in the future.

Thank you,

~Casey DeLorme
--bcaec54b4ac0491c3c04c9d932af-- --===============9209528223388011864== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users --===============9209528223388011864==-- From xen-users-bounces@lists.xen.org Sun Sep 16 22:31:10 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Sun, 16 Sep 2012 22:31:10 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TDNLp-00023f-Az; Sun, 16 Sep 2012 22:30:05 +0000 Received: from mail27.messagelabs.com ([193.109.254.147]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TDNLn-00023a-Rr for xen-users@lists.xen.org; Sun, 16 Sep 2012 22:30:04 +0000 X-Env-Sender: cdelorme@gmail.com X-Msg-Ref: server-10.tower-27.messagelabs.com!1347834596!6064197!1 X-Originating-IP: [209.85.219.45] X-SpamReason: No, hits=0.4 required=7.0 tests=HTML_30_40,HTML_MESSAGE, ML_RADAR_SPEW_LINKS_14,RCVD_BY_IP,spamassassin: X-StarScan-Received: X-StarScan-Version: 6.6.1.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 10223 invoked from network); 16 Sep 2012 22:29:57 -0000 Received: from mail-oa0-f45.google.com (HELO mail-oa0-f45.google.com) (209.85.219.45) by server-10.tower-27.messagelabs.com with RC4-SHA encrypted SMTP; 16 Sep 2012 22:29:57 -0000 Received: by oagn12 with SMTP id n12so5270270oag.32 for ; Sun, 16 Sep 2012 15:29:55 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:date:message-id:subject:from:to:content-type; bh=mY34qKDpituWKjxdjgh0z5HwH+BhOwRK13Ovbr+znx8=; b=Pg5NeBJ+/Ydjt49L19lPp0hOQCa3i86P4xc3sRBIAJvMqLO1y781xZq2/liBi31rD8 ZGNRwgyG/HopubUZtLQCrnkuo9dhLJ/p5dHFlmcrVfuDSRNkhbJWeuBH60tl3tVZY1YT GxpLtMeWyHTTpC3Ti+WNj/2lLdcriEycJTYkOhwFt94XjWSdk/abY0dmIuEHWVhRmqzH PEyo9izkeJshIMRaGvuyWM2CZ776ZRqOlkwpWScHIfM47AsGWDRsafynDjlc4UeUuEP7 Cshy7z580OyqtKwdftudvrEPjliDiWjqE4UDxJQkyG9Wyxc6p5xKw9TxcChrCZL6y7xO Yv1w== MIME-Version: 1.0 Received: by 10.60.170.229 with SMTP id ap5mr9825534oec.101.1347834595580; Sun, 16 Sep 2012 15:29:55 -0700 (PDT) Received: by 10.76.115.197 with HTTP; Sun, 16 Sep 2012 15:29:55 -0700 (PDT) Date: Sun, 16 Sep 2012 18:29:55 -0400 Message-ID: From: Casey DeLorme To: xen-users@lists.xen.org Subject: [Xen-users] Personal Comprehensive Xen Documentation X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============9209528223388011864==" Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org --===============9209528223388011864== Content-Type: multipart/alternative; boundary=bcaec54b4ac0491c3c04c9d932af --bcaec54b4ac0491c3c04c9d932af Content-Type: text/plain; charset=ISO-8859-1 Hello Xen Users, I have been testing Xen 4.2 since April, and have just finished creating comprehensive documentation to reproduce my personal system. I have posted the documentation on the Xen Wiki: http://wiki.xen.org/wiki/Comprehensive_Xen_Debian_Wheezy_PCI_Passthrough_Tutorial Additionally I created a visual aid that walks through the entire process as well: http://www.youtube.com/watch?v=mnTj6_kDIeg&list=PLC70DC33D993CEB44&feature=plpp_play_all Success with Xen seems to depend on a lot of variables, so my documentation is very specific, but it should be useful regardless. The guide covers: - Installing UEFI Debian Wheezy Beta 1 Dom0 - Compiling Custom Linux Kernel for Xen - Compiling Xen 4.2 - Configuring Xen 4.2 - Installing Windows HVM - PCI Passthrough for USB and Graphics Devices The last video is a performance demonstration video of a Windows 7 HVM. I hope this helps others looking to do something similar, and would appreciate feedback to improve it in the future. Thank you, ~Casey DeLorme --bcaec54b4ac0491c3c04c9d932af Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable
Hello Xen Users,

I have been testing Xen 4.2 = since April, and have just finished creating comprehensive documentation to= reproduce my personal system.

I have posted the d= ocumentation on the Xen Wiki:

Additionally I = created a visual aid that walks through the entire process as well:
=

The guide covers:

- Installing= UEFI Debian Wheezy Beta 1 Dom0
- Compiling Custom Linux Kernel for Xen
- Compiling Xen 4.2<= /div>
- Configuring Xen 4.2
- Installing Windows HVM
- PCI Passthrough for USB and Graphics Devices

The last video is a performance demonstration video of a Windows 7 HVM.

I hope this helps others looking to do something simi= lar, and would appreciate feedback to improve it in the future.

Thank you,

~Casey DeLorme
--bcaec54b4ac0491c3c04c9d932af-- --===============9209528223388011864== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users --===============9209528223388011864==-- From xen-users-bounces@lists.xen.org Sun Sep 16 23:28:16 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Sun, 16 Sep 2012 23:28:16 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TDOF6-0002Yo-8V; Sun, 16 Sep 2012 23:27:12 +0000 Received: from mail27.messagelabs.com ([193.109.254.147]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TDOF4-0002Yg-MG for xen-users@lists.xen.org; Sun, 16 Sep 2012 23:27:10 +0000 X-Env-Sender: ajlill@ajlc.waterloo.on.ca X-Msg-Ref: server-12.tower-27.messagelabs.com!1347838022!11252506!1 X-Originating-IP: [64.7.134.25] X-SpamReason: No, hits=0.0 required=7.0 tests= X-StarScan-Received: X-StarScan-Version: 6.6.1.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 23438 invoked from network); 16 Sep 2012 23:27:04 -0000 Received: from ajlill.sentex.ca (HELO mail.ajlc.waterloo.on.ca) (64.7.134.25) by server-12.tower-27.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 16 Sep 2012 23:27:04 -0000 Received: from [10.19.61.4] (gloria.ajlc.waterloo.on.ca [10.19.61.4]) (authenticated bits=0) by mail.ajlc.waterloo.on.ca (8.14.3/8.14.3/Debian-9.4) with ESMTP id q8GNQr8H001321 for ; Sun, 16 Sep 2012 19:26:54 -0400 Message-ID: <5056603D.8030007@ajlc.waterloo.on.ca> Date: Sun, 16 Sep 2012 19:26:53 -0400 From: Tony Lill User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:15.0) Gecko/20120827 Thunderbird/15.0 MIME-Version: 1.0 To: xen-users@lists.xen.org References: <003601cd9430$a381db70$ea859250$@gmail.com> <1347818899.25803.75.camel@dagon.hellion.org.uk> <004e01cd9446$b7636b20$262a4160$@gmail.com> In-Reply-To: <004e01cd9446$b7636b20$262a4160$@gmail.com> X-Enigmail-Version: 1.4.4 X-Spam-Status: No, score=-101.3 required=5.0 tests=ALL_TRUSTED,AWL, RP_MATCHES_RCVD,USER_IN_WHITELIST autolearn=ham version=3.3.1 X-Spam-Checker-Version: SpamAssassin 3.3.1 (2010-03-16) on mail.ajlc.waterloo.on.ca Subject: Re: [Xen-users] Setting up XEN domU causes RAID5 to fail? X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: base64 Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org LS0tLS1CRUdJTiBQR1AgU0lHTkVEIE1FU1NBR0UtLS0tLQpIYXNoOiBTSEExCgpBcmUgdGhlcmUg YW55IG1lc3NhZ2VzIGluIHRoZSBrZXJuZWwgbG9nIG9yIGRtZXNnIHJlZ2FyZGluZyB0aGVzZSBk aXNrcz8KCk9uIDA5LzE2LzIwMTIgMDQ6MDYgUE0sIE1hcmMgVG91c2lnbmFudCB3cm90ZToKPiBG WUksIEkgc3dpdGNoZWQgdG8gZmlsZTogYW5kIHN0aWxsIHRoZSBzYW1lIGlzc3VlIG9jY3VycmVk LCB3aXRoCj4gb25lIGV4Y2VwdGlvbi4uIFRoaXMgdGltZSBpdCAibG9zdCIgdGhlIFJBSUQgbWVt YmVycyB3aGlsZSBib290aW5nCj4gb2ZmIHRoZSBJU08uIEkgaGFkbid0IGV2ZW4gZ290dGVuIHRv IHRoZSBpbnN0YWxsIHNjcmVlbnMgeWV0Lgo+IAo+IC0tLS0tT3JpZ2luYWwgTWVzc2FnZS0tLS0t IEZyb206IElhbiBDYW1wYmVsbAo+IFttYWlsdG86SWFuLkNhbXBiZWxsQGNpdHJpeC5jb21dIFNl bnQ6IFN1bmRheSwgU2VwdGVtYmVyIDE2LCAyMDEyCj4gMjowOCBQTSBUbzogTWFyYyBUb3VzaWdu YW50IENjOiB4ZW4tdXNlcnNAbGlzdHMueGVuLm9yZyBTdWJqZWN0Ogo+IFJlOiBbWGVuLXVzZXJz XSBTZXR0aW5nIHVwIFhFTiBkb21VIGNhdXNlcyBSQUlENSB0byBmYWlsPwo+IAo+IE9uIFN1biwg MjAxMi0wOS0xNiBhdCAxODoyOCArMDEwMCwgTWFyYyBUb3VzaWduYW50IHdyb3RlOgo+IAo+PiBJ IHRoZW4gY3JlYXRlZCBzZXZlcmFsIC5pbWcgZmlsZXMgaW4gdGhlIHhlbl9pbWFnZXMgZm9sZGVy IHVzaW5nCj4+IGRkLiBGb3IgZXhhbXBsZSAoZGQgaWY9L2Rldi96ZXJvCj4+IG9mPS9pbWFnZXMv eGVuX2ltYWdlcy9XaW43eDg2X0Jhc2UuaW1nIGJzPTEgY291bnQ9MSBzZWVrPTUwRykKPiBbLi4u XQo+PiBJIGdvdCB0byB0aGUgcG9pbnQgd2hlcmUgaXQgZm9ybWF0dGVkIHRoZSDigJxkcml2ZeKA nSBhbmQgc3RhcnRlZCAKPj4gaW5zdGFsbGluZywgaXQgZmFpbGVkIG9uIHRoZSBleHRyYWN0aW9u IHN0ZXAgc2F5aW5nIG15IOKAnERWROKAnSB3YXMKPj4gYmFkLgo+IAo+IFdoYXQgZG9lcyB5b3Vy IGd1ZXN0IGNvbmZpZyBmaWxlIGxvb2sgbGlrZSwgaW4gcGFydGljdWxhciB0aGUgZGlzawo+IGxp bmUuCj4gCj4gSXMgdGhlcmUgYW55IGNoYW5jZSB0aGF0IHlvdSBoYXZlIGFjY2lkZW50YWxseSBw b2ludGVkIHRoZSBWTSdzCj4gZGlza3MgYXQgb25lIG9yIG1vcmUgb2YgdGhlIHBoeXNpY2FsIGRp c2tzIHdoaWNoIG1ha2VzIHVwIHlvdXIgUkFJRAo+IGFycmF5Pwo+IAo+IElhbi4KPiAKPiAKPiAK PiBfX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fXyBYZW4tdXNl cnMgbWFpbGluZwo+IGxpc3QgWGVuLXVzZXJzQGxpc3RzLnhlbi5vcmcgaHR0cDovL2xpc3RzLnhl bi5vcmcveGVuLXVzZXJzCj4gCgotIC0tIApUb255IExpbGwsIE9DVCwgICAgICAgICAgICAgICAg ICAgIFRvbnkuTGlsbEBBSkxDLldhdGVybG9vLk9OLkNBClByZXNpZGVudCwgQS4gSi4gTGlsbCBD b25zdWx0YW50cyAgICAgICAgICAgICAgICAgKDUxOSkgNjUwIDA2NjAKNTM5IEdyYW5kIFZhbGxl eSBEci4sIENhbWJyaWRnZSwgT250LiBOM0ggMlMyICAgICAoNTE5KSAyNDEgMjQ2MQotIC0tLS0t LS0tLS0tLS0tLSBodHRwOi8vd3d3LmFqbGMud2F0ZXJsb28ub24uY2EvIC0tLS0tLS0tLS0tLS0t LS0KCgotLS0tLUJFR0lOIFBHUCBTSUdOQVRVUkUtLS0tLQpWZXJzaW9uOiBHbnVQRyB2MS40LjEw IChHTlUvTGludXgpCkNvbW1lbnQ6IFVzaW5nIEdudVBHIHdpdGggTW96aWxsYSAtIGh0dHA6Ly93 d3cuZW5pZ21haWwubmV0LwoKaUVZRUFSRUNBQVlGQWxCV1lEMEFDZ2tRR1M4eVpxMXV2eEJyT0FD Zlp2Y29ydDJmU0l2MWpUSUw0STY1OGFydAozZU1BbjJBQXRwZk1TeEhvQkF3L3ZwN1dFM3U4ams2 awo9enlkeAotLS0tLUVORCBQR1AgU0lHTkFUVVJFLS0tLS0KCl9fX19fX19fX19fX19fX19fX19f X19fX19fX19fX19fX19fX19fX19fX19fX19fClhlbi11c2VycyBtYWlsaW5nIGxpc3QKWGVuLXVz ZXJzQGxpc3RzLnhlbi5vcmcKaHR0cDovL2xpc3RzLnhlbi5vcmcveGVuLXVzZXJz From xen-users-bounces@lists.xen.org Sun Sep 16 23:28:16 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Sun, 16 Sep 2012 23:28:16 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TDOF6-0002Yo-8V; Sun, 16 Sep 2012 23:27:12 +0000 Received: from mail27.messagelabs.com ([193.109.254.147]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TDOF4-0002Yg-MG for xen-users@lists.xen.org; Sun, 16 Sep 2012 23:27:10 +0000 X-Env-Sender: ajlill@ajlc.waterloo.on.ca X-Msg-Ref: server-12.tower-27.messagelabs.com!1347838022!11252506!1 X-Originating-IP: [64.7.134.25] X-SpamReason: No, hits=0.0 required=7.0 tests= X-StarScan-Received: X-StarScan-Version: 6.6.1.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 23438 invoked from network); 16 Sep 2012 23:27:04 -0000 Received: from ajlill.sentex.ca (HELO mail.ajlc.waterloo.on.ca) (64.7.134.25) by server-12.tower-27.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 16 Sep 2012 23:27:04 -0000 Received: from [10.19.61.4] (gloria.ajlc.waterloo.on.ca [10.19.61.4]) (authenticated bits=0) by mail.ajlc.waterloo.on.ca (8.14.3/8.14.3/Debian-9.4) with ESMTP id q8GNQr8H001321 for ; Sun, 16 Sep 2012 19:26:54 -0400 Message-ID: <5056603D.8030007@ajlc.waterloo.on.ca> Date: Sun, 16 Sep 2012 19:26:53 -0400 From: Tony Lill User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:15.0) Gecko/20120827 Thunderbird/15.0 MIME-Version: 1.0 To: xen-users@lists.xen.org References: <003601cd9430$a381db70$ea859250$@gmail.com> <1347818899.25803.75.camel@dagon.hellion.org.uk> <004e01cd9446$b7636b20$262a4160$@gmail.com> In-Reply-To: <004e01cd9446$b7636b20$262a4160$@gmail.com> X-Enigmail-Version: 1.4.4 X-Spam-Status: No, score=-101.3 required=5.0 tests=ALL_TRUSTED,AWL, RP_MATCHES_RCVD,USER_IN_WHITELIST autolearn=ham version=3.3.1 X-Spam-Checker-Version: SpamAssassin 3.3.1 (2010-03-16) on mail.ajlc.waterloo.on.ca Subject: Re: [Xen-users] Setting up XEN domU causes RAID5 to fail? X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: base64 Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org LS0tLS1CRUdJTiBQR1AgU0lHTkVEIE1FU1NBR0UtLS0tLQpIYXNoOiBTSEExCgpBcmUgdGhlcmUg YW55IG1lc3NhZ2VzIGluIHRoZSBrZXJuZWwgbG9nIG9yIGRtZXNnIHJlZ2FyZGluZyB0aGVzZSBk aXNrcz8KCk9uIDA5LzE2LzIwMTIgMDQ6MDYgUE0sIE1hcmMgVG91c2lnbmFudCB3cm90ZToKPiBG WUksIEkgc3dpdGNoZWQgdG8gZmlsZTogYW5kIHN0aWxsIHRoZSBzYW1lIGlzc3VlIG9jY3VycmVk LCB3aXRoCj4gb25lIGV4Y2VwdGlvbi4uIFRoaXMgdGltZSBpdCAibG9zdCIgdGhlIFJBSUQgbWVt YmVycyB3aGlsZSBib290aW5nCj4gb2ZmIHRoZSBJU08uIEkgaGFkbid0IGV2ZW4gZ290dGVuIHRv IHRoZSBpbnN0YWxsIHNjcmVlbnMgeWV0Lgo+IAo+IC0tLS0tT3JpZ2luYWwgTWVzc2FnZS0tLS0t IEZyb206IElhbiBDYW1wYmVsbAo+IFttYWlsdG86SWFuLkNhbXBiZWxsQGNpdHJpeC5jb21dIFNl bnQ6IFN1bmRheSwgU2VwdGVtYmVyIDE2LCAyMDEyCj4gMjowOCBQTSBUbzogTWFyYyBUb3VzaWdu YW50IENjOiB4ZW4tdXNlcnNAbGlzdHMueGVuLm9yZyBTdWJqZWN0Ogo+IFJlOiBbWGVuLXVzZXJz XSBTZXR0aW5nIHVwIFhFTiBkb21VIGNhdXNlcyBSQUlENSB0byBmYWlsPwo+IAo+IE9uIFN1biwg MjAxMi0wOS0xNiBhdCAxODoyOCArMDEwMCwgTWFyYyBUb3VzaWduYW50IHdyb3RlOgo+IAo+PiBJ IHRoZW4gY3JlYXRlZCBzZXZlcmFsIC5pbWcgZmlsZXMgaW4gdGhlIHhlbl9pbWFnZXMgZm9sZGVy IHVzaW5nCj4+IGRkLiBGb3IgZXhhbXBsZSAoZGQgaWY9L2Rldi96ZXJvCj4+IG9mPS9pbWFnZXMv eGVuX2ltYWdlcy9XaW43eDg2X0Jhc2UuaW1nIGJzPTEgY291bnQ9MSBzZWVrPTUwRykKPiBbLi4u XQo+PiBJIGdvdCB0byB0aGUgcG9pbnQgd2hlcmUgaXQgZm9ybWF0dGVkIHRoZSDigJxkcml2ZeKA nSBhbmQgc3RhcnRlZCAKPj4gaW5zdGFsbGluZywgaXQgZmFpbGVkIG9uIHRoZSBleHRyYWN0aW9u IHN0ZXAgc2F5aW5nIG15IOKAnERWROKAnSB3YXMKPj4gYmFkLgo+IAo+IFdoYXQgZG9lcyB5b3Vy IGd1ZXN0IGNvbmZpZyBmaWxlIGxvb2sgbGlrZSwgaW4gcGFydGljdWxhciB0aGUgZGlzawo+IGxp bmUuCj4gCj4gSXMgdGhlcmUgYW55IGNoYW5jZSB0aGF0IHlvdSBoYXZlIGFjY2lkZW50YWxseSBw b2ludGVkIHRoZSBWTSdzCj4gZGlza3MgYXQgb25lIG9yIG1vcmUgb2YgdGhlIHBoeXNpY2FsIGRp c2tzIHdoaWNoIG1ha2VzIHVwIHlvdXIgUkFJRAo+IGFycmF5Pwo+IAo+IElhbi4KPiAKPiAKPiAK PiBfX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fXyBYZW4tdXNl cnMgbWFpbGluZwo+IGxpc3QgWGVuLXVzZXJzQGxpc3RzLnhlbi5vcmcgaHR0cDovL2xpc3RzLnhl bi5vcmcveGVuLXVzZXJzCj4gCgotIC0tIApUb255IExpbGwsIE9DVCwgICAgICAgICAgICAgICAg ICAgIFRvbnkuTGlsbEBBSkxDLldhdGVybG9vLk9OLkNBClByZXNpZGVudCwgQS4gSi4gTGlsbCBD b25zdWx0YW50cyAgICAgICAgICAgICAgICAgKDUxOSkgNjUwIDA2NjAKNTM5IEdyYW5kIFZhbGxl eSBEci4sIENhbWJyaWRnZSwgT250LiBOM0ggMlMyICAgICAoNTE5KSAyNDEgMjQ2MQotIC0tLS0t LS0tLS0tLS0tLSBodHRwOi8vd3d3LmFqbGMud2F0ZXJsb28ub24uY2EvIC0tLS0tLS0tLS0tLS0t LS0KCgotLS0tLUJFR0lOIFBHUCBTSUdOQVRVUkUtLS0tLQpWZXJzaW9uOiBHbnVQRyB2MS40LjEw IChHTlUvTGludXgpCkNvbW1lbnQ6IFVzaW5nIEdudVBHIHdpdGggTW96aWxsYSAtIGh0dHA6Ly93 d3cuZW5pZ21haWwubmV0LwoKaUVZRUFSRUNBQVlGQWxCV1lEMEFDZ2tRR1M4eVpxMXV2eEJyT0FD Zlp2Y29ydDJmU0l2MWpUSUw0STY1OGFydAozZU1BbjJBQXRwZk1TeEhvQkF3L3ZwN1dFM3U4ams2 awo9enlkeAotLS0tLUVORCBQR1AgU0lHTkFUVVJFLS0tLS0KCl9fX19fX19fX19fX19fX19fX19f X19fX19fX19fX19fX19fX19fX19fX19fX19fClhlbi11c2VycyBtYWlsaW5nIGxpc3QKWGVuLXVz ZXJzQGxpc3RzLnhlbi5vcmcKaHR0cDovL2xpc3RzLnhlbi5vcmcveGVuLXVzZXJz From xen-users-bounces@lists.xen.org Mon Sep 17 01:19:01 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Mon, 17 Sep 2012 01:19:01 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TDPyD-0007QJ-3d; Mon, 17 Sep 2012 01:17:53 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TDPyB-0007QE-9g for xen-users@lists.xensource.com; Mon, 17 Sep 2012 01:17:51 +0000 Received: from [85.158.143.35:32255] by server-1.bemta-4.messagelabs.com id 4F/35-12504-E3A76505; Mon, 17 Sep 2012 01:17:50 +0000 X-Env-Sender: pingh.cd@gmail.com X-Msg-Ref: server-16.tower-21.messagelabs.com!1347844668!16040619!1 X-Originating-IP: [216.139.236.26] X-SpamReason: No, hits=0.0 required=7.0 tests=ML_RADAR_SPEW_LINKS_14, spamassassin: X-StarScan-Received: X-StarScan-Version: 6.6.1.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 21916 invoked from network); 17 Sep 2012 01:17:50 -0000 Received: from sam.nabble.com (HELO sam.nabble.com) (216.139.236.26) by server-16.tower-21.messagelabs.com with AES256-SHA encrypted SMTP; 17 Sep 2012 01:17:50 -0000 Received: from [192.168.236.26] (helo=sam.nabble.com) by sam.nabble.com with esmtp (Exim 4.72) (envelope-from ) id 1TDPy8-0008U3-AE for xen-users@lists.xensource.com; Sun, 16 Sep 2012 18:17:48 -0700 Date: Sun, 16 Sep 2012 18:17:48 -0700 (PDT) From: Robin hp To: xen-users@lists.xensource.com Message-ID: <1347844668292-5711304.post@n5.nabble.com> In-Reply-To: <1347611471854-5711212.post@n5.nabble.com> References: <1347611471854-5711212.post@n5.nabble.com> MIME-Version: 1.0 Subject: Re: [Xen-users] Performance of PVM and HVM X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org no one care about this -- View this message in context: http://xen.1045712.n5.nabble.com/Performance-of-PVM-and-HVM-tp5711212p5711304.html Sent from the Xen - User mailing list archive at Nabble.com. _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Mon Sep 17 01:19:01 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Mon, 17 Sep 2012 01:19:01 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TDPyD-0007QJ-3d; Mon, 17 Sep 2012 01:17:53 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TDPyB-0007QE-9g for xen-users@lists.xensource.com; Mon, 17 Sep 2012 01:17:51 +0000 Received: from [85.158.143.35:32255] by server-1.bemta-4.messagelabs.com id 4F/35-12504-E3A76505; Mon, 17 Sep 2012 01:17:50 +0000 X-Env-Sender: pingh.cd@gmail.com X-Msg-Ref: server-16.tower-21.messagelabs.com!1347844668!16040619!1 X-Originating-IP: [216.139.236.26] X-SpamReason: No, hits=0.0 required=7.0 tests=ML_RADAR_SPEW_LINKS_14, spamassassin: X-StarScan-Received: X-StarScan-Version: 6.6.1.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 21916 invoked from network); 17 Sep 2012 01:17:50 -0000 Received: from sam.nabble.com (HELO sam.nabble.com) (216.139.236.26) by server-16.tower-21.messagelabs.com with AES256-SHA encrypted SMTP; 17 Sep 2012 01:17:50 -0000 Received: from [192.168.236.26] (helo=sam.nabble.com) by sam.nabble.com with esmtp (Exim 4.72) (envelope-from ) id 1TDPy8-0008U3-AE for xen-users@lists.xensource.com; Sun, 16 Sep 2012 18:17:48 -0700 Date: Sun, 16 Sep 2012 18:17:48 -0700 (PDT) From: Robin hp To: xen-users@lists.xensource.com Message-ID: <1347844668292-5711304.post@n5.nabble.com> In-Reply-To: <1347611471854-5711212.post@n5.nabble.com> References: <1347611471854-5711212.post@n5.nabble.com> MIME-Version: 1.0 Subject: Re: [Xen-users] Performance of PVM and HVM X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org no one care about this -- View this message in context: http://xen.1045712.n5.nabble.com/Performance-of-PVM-and-HVM-tp5711212p5711304.html Sent from the Xen - User mailing list archive at Nabble.com. _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Mon Sep 17 01:44:39 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Mon, 17 Sep 2012 01:44:39 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TDQN9-0007p1-O1; Mon, 17 Sep 2012 01:43:39 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TDQN8-0007ow-9S for xen-users@lists.xensource.com; Mon, 17 Sep 2012 01:43:38 +0000 Received: from [85.158.143.99:54985] by server-2.bemta-4.messagelabs.com id B3/A5-21239-94086505; Mon, 17 Sep 2012 01:43:37 +0000 X-Env-Sender: fajar@fajar.net X-Msg-Ref: server-6.tower-216.messagelabs.com!1347846215!23574714!1 X-Originating-IP: [209.85.214.171] X-SpamReason: No, hits=0.3 required=7.0 tests=RCVD_BY_IP X-StarScan-Received: X-StarScan-Version: 6.6.1.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 32665 invoked from network); 17 Sep 2012 01:43:37 -0000 Received: from mail-ob0-f171.google.com (HELO mail-ob0-f171.google.com) (209.85.214.171) by server-6.tower-216.messagelabs.com with RC4-SHA encrypted SMTP; 17 Sep 2012 01:43:37 -0000 Received: by obqv19 with SMTP id v19so11330596obq.30 for ; Sun, 16 Sep 2012 18:43:35 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:x-gm-message-state; bh=8r42vZM684eSPXbWheL05zZNdCyUcAVRo7T2LUXXr20=; b=MtacVEHTTGW+ethyAHlZqd1vq0YQFIBxmBchzRPVvZmPYgoh1S1NOVmAbvUA0uB89u ZeQyq2J3aGdED/K0HYKEU/lrVB5DK6h0Rr4LRVnuQoQ1G8FGWWKBEeBzjIFO3tb3C6qJ XO1AjyvZPovQM/F23ucA8cg3AITCYfeiiHupWdcvUaaBdu5ejju3epTghQW267T0Xv9Y u6JATJiHd6YCqbHJRAakXabUwum4qyPnz675CPlgKPELiPhxWKiQAfqmp2jAj590qptK sK0no8IQNss6iiSXazMp2Sag8LYeeGINlKU1RRhHcWoVsJVHvOyf0BVgwDX84vsR/5l4 PuTQ== MIME-Version: 1.0 Received: by 10.182.118.2 with SMTP id ki2mr10168224obb.101.1347846215476; Sun, 16 Sep 2012 18:43:35 -0700 (PDT) Received: by 10.60.6.230 with HTTP; Sun, 16 Sep 2012 18:43:35 -0700 (PDT) In-Reply-To: <1347844668292-5711304.post@n5.nabble.com> References: <1347611471854-5711212.post@n5.nabble.com> <1347844668292-5711304.post@n5.nabble.com> Date: Mon, 17 Sep 2012 08:43:35 +0700 Message-ID: From: "Fajar A. Nugraha" To: Robin hp X-Gm-Message-State: ALoCoQl7BKzNv+lz2uQeeTpAAXAqcZGeSqKOBbfzBp4ICxLvgJPPP7Nj5VfybA4VM0rd/BM8jwBw Cc: xen-users@lists.xensource.com Subject: Re: [Xen-users] Performance of PVM and HVM X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org On Mon, Sep 17, 2012 at 8:17 AM, Robin hp wrote: > no one care about this How could anyone care if all they received are useless oneliners? Hint #1: look at the nable page you're posting from. There's a big warning "This post has NOT been accepted by the mailing list yet." Hint #2: Don't use nabble. Join the list instead. Try reposting your question, directy to this list, so that others can see (and probably respond to) your question. -- Fajar _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Mon Sep 17 01:44:39 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Mon, 17 Sep 2012 01:44:39 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TDQN9-0007p1-O1; Mon, 17 Sep 2012 01:43:39 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TDQN8-0007ow-9S for xen-users@lists.xensource.com; Mon, 17 Sep 2012 01:43:38 +0000 Received: from [85.158.143.99:54985] by server-2.bemta-4.messagelabs.com id B3/A5-21239-94086505; Mon, 17 Sep 2012 01:43:37 +0000 X-Env-Sender: fajar@fajar.net X-Msg-Ref: server-6.tower-216.messagelabs.com!1347846215!23574714!1 X-Originating-IP: [209.85.214.171] X-SpamReason: No, hits=0.3 required=7.0 tests=RCVD_BY_IP X-StarScan-Received: X-StarScan-Version: 6.6.1.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 32665 invoked from network); 17 Sep 2012 01:43:37 -0000 Received: from mail-ob0-f171.google.com (HELO mail-ob0-f171.google.com) (209.85.214.171) by server-6.tower-216.messagelabs.com with RC4-SHA encrypted SMTP; 17 Sep 2012 01:43:37 -0000 Received: by obqv19 with SMTP id v19so11330596obq.30 for ; Sun, 16 Sep 2012 18:43:35 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:x-gm-message-state; bh=8r42vZM684eSPXbWheL05zZNdCyUcAVRo7T2LUXXr20=; b=MtacVEHTTGW+ethyAHlZqd1vq0YQFIBxmBchzRPVvZmPYgoh1S1NOVmAbvUA0uB89u ZeQyq2J3aGdED/K0HYKEU/lrVB5DK6h0Rr4LRVnuQoQ1G8FGWWKBEeBzjIFO3tb3C6qJ XO1AjyvZPovQM/F23ucA8cg3AITCYfeiiHupWdcvUaaBdu5ejju3epTghQW267T0Xv9Y u6JATJiHd6YCqbHJRAakXabUwum4qyPnz675CPlgKPELiPhxWKiQAfqmp2jAj590qptK sK0no8IQNss6iiSXazMp2Sag8LYeeGINlKU1RRhHcWoVsJVHvOyf0BVgwDX84vsR/5l4 PuTQ== MIME-Version: 1.0 Received: by 10.182.118.2 with SMTP id ki2mr10168224obb.101.1347846215476; Sun, 16 Sep 2012 18:43:35 -0700 (PDT) Received: by 10.60.6.230 with HTTP; Sun, 16 Sep 2012 18:43:35 -0700 (PDT) In-Reply-To: <1347844668292-5711304.post@n5.nabble.com> References: <1347611471854-5711212.post@n5.nabble.com> <1347844668292-5711304.post@n5.nabble.com> Date: Mon, 17 Sep 2012 08:43:35 +0700 Message-ID: From: "Fajar A. Nugraha" To: Robin hp X-Gm-Message-State: ALoCoQl7BKzNv+lz2uQeeTpAAXAqcZGeSqKOBbfzBp4ICxLvgJPPP7Nj5VfybA4VM0rd/BM8jwBw Cc: xen-users@lists.xensource.com Subject: Re: [Xen-users] Performance of PVM and HVM X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org On Mon, Sep 17, 2012 at 8:17 AM, Robin hp wrote: > no one care about this How could anyone care if all they received are useless oneliners? Hint #1: look at the nable page you're posting from. There's a big warning "This post has NOT been accepted by the mailing list yet." Hint #2: Don't use nabble. Join the list instead. Try reposting your question, directy to this list, so that others can see (and probably respond to) your question. -- Fajar _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Mon Sep 17 01:53:08 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Mon, 17 Sep 2012 01:53:08 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TDQVP-0008Bz-CG; Mon, 17 Sep 2012 01:52:11 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TDQVN-0008Bp-9v for xen-users@lists.xen.org; Mon, 17 Sep 2012 01:52:09 +0000 Received: from [85.158.143.99:45336] by server-2.bemta-4.messagelabs.com id CB/08-21239-84286505; Mon, 17 Sep 2012 01:52:08 +0000 X-Env-Sender: myrdhn@gmail.com X-Msg-Ref: server-16.tower-216.messagelabs.com!1347846726!19364992!1 X-Originating-IP: [209.85.216.173] X-SpamReason: No, hits=0.3 required=7.0 tests=ML_RADAR_SPEW_LINKS_14, RCVD_BY_IP,spamassassin: X-StarScan-Received: X-StarScan-Version: 6.6.1.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 2876 invoked from network); 17 Sep 2012 01:52:07 -0000 Received: from mail-qc0-f173.google.com (HELO mail-qc0-f173.google.com) (209.85.216.173) by server-16.tower-216.messagelabs.com with RC4-SHA encrypted SMTP; 17 Sep 2012 01:52:07 -0000 Received: by qcab12 with SMTP id b12so5497443qca.32 for ; Sun, 16 Sep 2012 18:52:06 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=from:to:references:in-reply-to:subject:date:message-id:mime-version :content-type:content-transfer-encoding:x-mailer:thread-index :content-language; bh=VjTYvYiJq8C6kM//+9m/Fw5sUeAQe2iYDraH7y+6aTo=; b=bvr4Ds+mZ11rmBtq2VUeNo9ItpIEF/DPdZ0DC6WPUyBWEeRxrGD3V0Tp1IZ8J8+p4a gjv5Zu9f5h3u3IxM0bXUB6+b26x1t78NFFydF6kpl3SGnW6yk90JplEGEZERdXDMjH1G q5WY51aq0kZE+1Y+CYBie43H9+QeGq8ooP6LEHAMwXB8Bi7VF2V9LgNpleSbdUHlRa6M gXuOXZigvqdB9Cxoh/ovRsaVUYyn/MiX/ASFCM4oW8ovxZiJe1AaMzl7qa/nqaC/KxJo DYFwxeHlvaFlSJAE5a8bQ0abLPqPZKaDkx50RC7gZZENcu9rhOWe6u6gDC173iGEhSWA FGsw== Received: by 10.229.135.136 with SMTP id n8mr6491869qct.42.1347846726414; Sun, 16 Sep 2012 18:52:06 -0700 (PDT) Received: from Belldandy (c-76-119-253-48.hsd1.ma.comcast.net. [76.119.253.48]) by mx.google.com with ESMTPS id dg10sm13311002qab.12.2012.09.16.18.52.05 (version=TLSv1/SSLv3 cipher=OTHER); Sun, 16 Sep 2012 18:52:05 -0700 (PDT) From: "Marc Tousignant" To: "'Tony Lill'" , References: <003601cd9430$a381db70$ea859250$@gmail.com> <1347818899.25803.75.camel@dagon.hellion.org.uk> <004e01cd9446$b7636b20$262a4160$@gmail.com> <5056603D.8030007@ajlc.waterloo.on.ca> In-Reply-To: <5056603D.8030007@ajlc.waterloo.on.ca> Date: Sun, 16 Sep 2012 21:52:08 -0400 Message-ID: <006701cd9477$0d045820$270d0860$@gmail.com> MIME-Version: 1.0 X-Mailer: Microsoft Outlook 14.0 Thread-Index: AQEtIveC4IhcOcllJOhnnzkXfTJ4EAF4akKmAbXW2NwBi1ebzJio2tzw Content-Language: en-us Subject: Re: [Xen-users] Setting up XEN domU causes RAID5 to fail? X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: base64 Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org Tm8gbWVzc2FnZXMgaW4gZG1lc2cgb3Igb24gdGhlIGNvbnNvbGUsIHRob3VnaCB0byBiZSBmYWly LCB0aGUgcm9vdCBwYXJ0aXRpb24gaXMgImJyb2tlbiIgYXQgdGhhdCBwb2ludCBhbmQgY2FuJ3Qg d3JpdGUgdG8gYW55IGZpbGVzLgpJIGp1c3QgdGVzdGVkIGFnYWluIHRvIGJlIHN1cmUsIHRoaXMg dGltZSBJIGNhbnQgZXZlbiBjYXQgdGhlIGxvZ3MuCgotLS0tLU9yaWdpbmFsIE1lc3NhZ2UtLS0t LQpGcm9tOiB4ZW4tdXNlcnMtYm91bmNlc0BsaXN0cy54ZW4ub3JnIFttYWlsdG86eGVuLXVzZXJz LWJvdW5jZXNAbGlzdHMueGVuLm9yZ10gT24gQmVoYWxmIE9mIFRvbnkgTGlsbApTZW50OiBTdW5k YXksIFNlcHRlbWJlciAxNiwgMjAxMiA3OjI3IFBNClRvOiB4ZW4tdXNlcnNAbGlzdHMueGVuLm9y ZwpTdWJqZWN0OiBSZTogW1hlbi11c2Vyc10gU2V0dGluZyB1cCBYRU4gZG9tVSBjYXVzZXMgUkFJ RDUgdG8gZmFpbD8KCi0tLS0tQkVHSU4gUEdQIFNJR05FRCBNRVNTQUdFLS0tLS0KSGFzaDogU0hB MQoKQXJlIHRoZXJlIGFueSBtZXNzYWdlcyBpbiB0aGUga2VybmVsIGxvZyBvciBkbWVzZyByZWdh cmRpbmcgdGhlc2UgZGlza3M/CgpPbiAwOS8xNi8yMDEyIDA0OjA2IFBNLCBNYXJjIFRvdXNpZ25h bnQgd3JvdGU6Cj4gRllJLCBJIHN3aXRjaGVkIHRvIGZpbGU6IGFuZCBzdGlsbCB0aGUgc2FtZSBp c3N1ZSBvY2N1cnJlZCwgd2l0aCBvbmUgCj4gZXhjZXB0aW9uLi4gVGhpcyB0aW1lIGl0ICJsb3N0 IiB0aGUgUkFJRCBtZW1iZXJzIHdoaWxlIGJvb3Rpbmcgb2ZmIHRoZSAKPiBJU08uIEkgaGFkbid0 IGV2ZW4gZ290dGVuIHRvIHRoZSBpbnN0YWxsIHNjcmVlbnMgeWV0Lgo+IAo+IC0tLS0tT3JpZ2lu YWwgTWVzc2FnZS0tLS0tIEZyb206IElhbiBDYW1wYmVsbCAKPiBbbWFpbHRvOklhbi5DYW1wYmVs bEBjaXRyaXguY29tXSBTZW50OiBTdW5kYXksIFNlcHRlbWJlciAxNiwgMjAxMgo+IDI6MDggUE0g VG86IE1hcmMgVG91c2lnbmFudCBDYzogeGVuLXVzZXJzQGxpc3RzLnhlbi5vcmcgU3ViamVjdDoK PiBSZTogW1hlbi11c2Vyc10gU2V0dGluZyB1cCBYRU4gZG9tVSBjYXVzZXMgUkFJRDUgdG8gZmFp bD8KPiAKPiBPbiBTdW4sIDIwMTItMDktMTYgYXQgMTg6MjggKzAxMDAsIE1hcmMgVG91c2lnbmFu dCB3cm90ZToKPiAKPj4gSSB0aGVuIGNyZWF0ZWQgc2V2ZXJhbCAuaW1nIGZpbGVzIGluIHRoZSB4 ZW5faW1hZ2VzIGZvbGRlciB1c2luZyBkZC4gCj4+IEZvciBleGFtcGxlIChkZCBpZj0vZGV2L3pl cm8gb2Y9L2ltYWdlcy94ZW5faW1hZ2VzL1dpbjd4ODZfQmFzZS5pbWcgCj4+IGJzPTEgY291bnQ9 MSBzZWVrPTUwRykKPiBbLi4uXQo+PiBJIGdvdCB0byB0aGUgcG9pbnQgd2hlcmUgaXQgZm9ybWF0 dGVkIHRoZSDigJxkcml2ZeKAnSBhbmQgc3RhcnRlZCAKPj4gaW5zdGFsbGluZywgaXQgZmFpbGVk IG9uIHRoZSBleHRyYWN0aW9uIHN0ZXAgc2F5aW5nIG15IOKAnERWROKAnSB3YXMgYmFkLgo+IAo+ IFdoYXQgZG9lcyB5b3VyIGd1ZXN0IGNvbmZpZyBmaWxlIGxvb2sgbGlrZSwgaW4gcGFydGljdWxh ciB0aGUgZGlzayAKPiBsaW5lLgo+IAo+IElzIHRoZXJlIGFueSBjaGFuY2UgdGhhdCB5b3UgaGF2 ZSBhY2NpZGVudGFsbHkgcG9pbnRlZCB0aGUgVk0ncyBkaXNrcyAKPiBhdCBvbmUgb3IgbW9yZSBv ZiB0aGUgcGh5c2ljYWwgZGlza3Mgd2hpY2ggbWFrZXMgdXAgeW91ciBSQUlEIGFycmF5Pwo+IAo+ IElhbi4KPiAKPiAKPiAKPiBfX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19f X19fX19fXyBYZW4tdXNlcnMgbWFpbGluZyBsaXN0IAo+IFhlbi11c2Vyc0BsaXN0cy54ZW4ub3Jn IGh0dHA6Ly9saXN0cy54ZW4ub3JnL3hlbi11c2Vycwo+IAoKLSAtLSAKVG9ueSBMaWxsLCBPQ1Qs ICAgICAgICAgICAgICAgICAgICBUb255LkxpbGxAQUpMQy5XYXRlcmxvby5PTi5DQQpQcmVzaWRl bnQsIEEuIEouIExpbGwgQ29uc3VsdGFudHMgICAgICAgICAgICAgICAgICg1MTkpIDY1MCAwNjYw CjUzOSBHcmFuZCBWYWxsZXkgRHIuLCBDYW1icmlkZ2UsIE9udC4gTjNIIDJTMiAgICAgKDUxOSkg MjQxIDI0NjEKLSAtLS0tLS0tLS0tLS0tLS0gaHR0cDovL3d3dy5hamxjLndhdGVybG9vLm9uLmNh LyAtLS0tLS0tLS0tLS0tLS0tCgoKLS0tLS1CRUdJTiBQR1AgU0lHTkFUVVJFLS0tLS0KVmVyc2lv bjogR251UEcgdjEuNC4xMCAoR05VL0xpbnV4KQpDb21tZW50OiBVc2luZyBHbnVQRyB3aXRoIE1v emlsbGEgLSBodHRwOi8vd3d3LmVuaWdtYWlsLm5ldC8KCmlFWUVBUkVDQUFZRkFsQldZRDBBQ2dr UUdTOHlacTF1dnhCck9BQ2ZadmNvcnQyZlNJdjFqVElMNEk2NThhcnQKM2VNQW4yQUF0cGZNU3hI b0JBdy92cDdXRTN1OGprNmsKPXp5ZHgKLS0tLS1FTkQgUEdQIFNJR05BVFVSRS0tLS0tCgpfX19f X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fXwpYZW4tdXNlcnMgbWFp bGluZyBsaXN0Clhlbi11c2Vyc0BsaXN0cy54ZW4ub3JnCmh0dHA6Ly9saXN0cy54ZW4ub3JnL3hl bi11c2VycwoKCl9fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19f Clhlbi11c2VycyBtYWlsaW5nIGxpc3QKWGVuLXVzZXJzQGxpc3RzLnhlbi5vcmcKaHR0cDovL2xp c3RzLnhlbi5vcmcveGVuLXVzZXJz From xen-users-bounces@lists.xen.org Mon Sep 17 01:53:08 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Mon, 17 Sep 2012 01:53:08 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TDQVP-0008Bz-CG; Mon, 17 Sep 2012 01:52:11 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TDQVN-0008Bp-9v for xen-users@lists.xen.org; Mon, 17 Sep 2012 01:52:09 +0000 Received: from [85.158.143.99:45336] by server-2.bemta-4.messagelabs.com id CB/08-21239-84286505; Mon, 17 Sep 2012 01:52:08 +0000 X-Env-Sender: myrdhn@gmail.com X-Msg-Ref: server-16.tower-216.messagelabs.com!1347846726!19364992!1 X-Originating-IP: [209.85.216.173] X-SpamReason: No, hits=0.3 required=7.0 tests=ML_RADAR_SPEW_LINKS_14, RCVD_BY_IP,spamassassin: X-StarScan-Received: X-StarScan-Version: 6.6.1.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 2876 invoked from network); 17 Sep 2012 01:52:07 -0000 Received: from mail-qc0-f173.google.com (HELO mail-qc0-f173.google.com) (209.85.216.173) by server-16.tower-216.messagelabs.com with RC4-SHA encrypted SMTP; 17 Sep 2012 01:52:07 -0000 Received: by qcab12 with SMTP id b12so5497443qca.32 for ; Sun, 16 Sep 2012 18:52:06 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=from:to:references:in-reply-to:subject:date:message-id:mime-version :content-type:content-transfer-encoding:x-mailer:thread-index :content-language; bh=VjTYvYiJq8C6kM//+9m/Fw5sUeAQe2iYDraH7y+6aTo=; b=bvr4Ds+mZ11rmBtq2VUeNo9ItpIEF/DPdZ0DC6WPUyBWEeRxrGD3V0Tp1IZ8J8+p4a gjv5Zu9f5h3u3IxM0bXUB6+b26x1t78NFFydF6kpl3SGnW6yk90JplEGEZERdXDMjH1G q5WY51aq0kZE+1Y+CYBie43H9+QeGq8ooP6LEHAMwXB8Bi7VF2V9LgNpleSbdUHlRa6M gXuOXZigvqdB9Cxoh/ovRsaVUYyn/MiX/ASFCM4oW8ovxZiJe1AaMzl7qa/nqaC/KxJo DYFwxeHlvaFlSJAE5a8bQ0abLPqPZKaDkx50RC7gZZENcu9rhOWe6u6gDC173iGEhSWA FGsw== Received: by 10.229.135.136 with SMTP id n8mr6491869qct.42.1347846726414; Sun, 16 Sep 2012 18:52:06 -0700 (PDT) Received: from Belldandy (c-76-119-253-48.hsd1.ma.comcast.net. [76.119.253.48]) by mx.google.com with ESMTPS id dg10sm13311002qab.12.2012.09.16.18.52.05 (version=TLSv1/SSLv3 cipher=OTHER); Sun, 16 Sep 2012 18:52:05 -0700 (PDT) From: "Marc Tousignant" To: "'Tony Lill'" , References: <003601cd9430$a381db70$ea859250$@gmail.com> <1347818899.25803.75.camel@dagon.hellion.org.uk> <004e01cd9446$b7636b20$262a4160$@gmail.com> <5056603D.8030007@ajlc.waterloo.on.ca> In-Reply-To: <5056603D.8030007@ajlc.waterloo.on.ca> Date: Sun, 16 Sep 2012 21:52:08 -0400 Message-ID: <006701cd9477$0d045820$270d0860$@gmail.com> MIME-Version: 1.0 X-Mailer: Microsoft Outlook 14.0 Thread-Index: AQEtIveC4IhcOcllJOhnnzkXfTJ4EAF4akKmAbXW2NwBi1ebzJio2tzw Content-Language: en-us Subject: Re: [Xen-users] Setting up XEN domU causes RAID5 to fail? X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: base64 Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org Tm8gbWVzc2FnZXMgaW4gZG1lc2cgb3Igb24gdGhlIGNvbnNvbGUsIHRob3VnaCB0byBiZSBmYWly LCB0aGUgcm9vdCBwYXJ0aXRpb24gaXMgImJyb2tlbiIgYXQgdGhhdCBwb2ludCBhbmQgY2FuJ3Qg d3JpdGUgdG8gYW55IGZpbGVzLgpJIGp1c3QgdGVzdGVkIGFnYWluIHRvIGJlIHN1cmUsIHRoaXMg dGltZSBJIGNhbnQgZXZlbiBjYXQgdGhlIGxvZ3MuCgotLS0tLU9yaWdpbmFsIE1lc3NhZ2UtLS0t LQpGcm9tOiB4ZW4tdXNlcnMtYm91bmNlc0BsaXN0cy54ZW4ub3JnIFttYWlsdG86eGVuLXVzZXJz LWJvdW5jZXNAbGlzdHMueGVuLm9yZ10gT24gQmVoYWxmIE9mIFRvbnkgTGlsbApTZW50OiBTdW5k YXksIFNlcHRlbWJlciAxNiwgMjAxMiA3OjI3IFBNClRvOiB4ZW4tdXNlcnNAbGlzdHMueGVuLm9y ZwpTdWJqZWN0OiBSZTogW1hlbi11c2Vyc10gU2V0dGluZyB1cCBYRU4gZG9tVSBjYXVzZXMgUkFJ RDUgdG8gZmFpbD8KCi0tLS0tQkVHSU4gUEdQIFNJR05FRCBNRVNTQUdFLS0tLS0KSGFzaDogU0hB MQoKQXJlIHRoZXJlIGFueSBtZXNzYWdlcyBpbiB0aGUga2VybmVsIGxvZyBvciBkbWVzZyByZWdh cmRpbmcgdGhlc2UgZGlza3M/CgpPbiAwOS8xNi8yMDEyIDA0OjA2IFBNLCBNYXJjIFRvdXNpZ25h bnQgd3JvdGU6Cj4gRllJLCBJIHN3aXRjaGVkIHRvIGZpbGU6IGFuZCBzdGlsbCB0aGUgc2FtZSBp c3N1ZSBvY2N1cnJlZCwgd2l0aCBvbmUgCj4gZXhjZXB0aW9uLi4gVGhpcyB0aW1lIGl0ICJsb3N0 IiB0aGUgUkFJRCBtZW1iZXJzIHdoaWxlIGJvb3Rpbmcgb2ZmIHRoZSAKPiBJU08uIEkgaGFkbid0 IGV2ZW4gZ290dGVuIHRvIHRoZSBpbnN0YWxsIHNjcmVlbnMgeWV0Lgo+IAo+IC0tLS0tT3JpZ2lu YWwgTWVzc2FnZS0tLS0tIEZyb206IElhbiBDYW1wYmVsbCAKPiBbbWFpbHRvOklhbi5DYW1wYmVs bEBjaXRyaXguY29tXSBTZW50OiBTdW5kYXksIFNlcHRlbWJlciAxNiwgMjAxMgo+IDI6MDggUE0g VG86IE1hcmMgVG91c2lnbmFudCBDYzogeGVuLXVzZXJzQGxpc3RzLnhlbi5vcmcgU3ViamVjdDoK PiBSZTogW1hlbi11c2Vyc10gU2V0dGluZyB1cCBYRU4gZG9tVSBjYXVzZXMgUkFJRDUgdG8gZmFp bD8KPiAKPiBPbiBTdW4sIDIwMTItMDktMTYgYXQgMTg6MjggKzAxMDAsIE1hcmMgVG91c2lnbmFu dCB3cm90ZToKPiAKPj4gSSB0aGVuIGNyZWF0ZWQgc2V2ZXJhbCAuaW1nIGZpbGVzIGluIHRoZSB4 ZW5faW1hZ2VzIGZvbGRlciB1c2luZyBkZC4gCj4+IEZvciBleGFtcGxlIChkZCBpZj0vZGV2L3pl cm8gb2Y9L2ltYWdlcy94ZW5faW1hZ2VzL1dpbjd4ODZfQmFzZS5pbWcgCj4+IGJzPTEgY291bnQ9 MSBzZWVrPTUwRykKPiBbLi4uXQo+PiBJIGdvdCB0byB0aGUgcG9pbnQgd2hlcmUgaXQgZm9ybWF0 dGVkIHRoZSDigJxkcml2ZeKAnSBhbmQgc3RhcnRlZCAKPj4gaW5zdGFsbGluZywgaXQgZmFpbGVk IG9uIHRoZSBleHRyYWN0aW9uIHN0ZXAgc2F5aW5nIG15IOKAnERWROKAnSB3YXMgYmFkLgo+IAo+ IFdoYXQgZG9lcyB5b3VyIGd1ZXN0IGNvbmZpZyBmaWxlIGxvb2sgbGlrZSwgaW4gcGFydGljdWxh ciB0aGUgZGlzayAKPiBsaW5lLgo+IAo+IElzIHRoZXJlIGFueSBjaGFuY2UgdGhhdCB5b3UgaGF2 ZSBhY2NpZGVudGFsbHkgcG9pbnRlZCB0aGUgVk0ncyBkaXNrcyAKPiBhdCBvbmUgb3IgbW9yZSBv ZiB0aGUgcGh5c2ljYWwgZGlza3Mgd2hpY2ggbWFrZXMgdXAgeW91ciBSQUlEIGFycmF5Pwo+IAo+ IElhbi4KPiAKPiAKPiAKPiBfX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19f X19fX19fXyBYZW4tdXNlcnMgbWFpbGluZyBsaXN0IAo+IFhlbi11c2Vyc0BsaXN0cy54ZW4ub3Jn IGh0dHA6Ly9saXN0cy54ZW4ub3JnL3hlbi11c2Vycwo+IAoKLSAtLSAKVG9ueSBMaWxsLCBPQ1Qs ICAgICAgICAgICAgICAgICAgICBUb255LkxpbGxAQUpMQy5XYXRlcmxvby5PTi5DQQpQcmVzaWRl bnQsIEEuIEouIExpbGwgQ29uc3VsdGFudHMgICAgICAgICAgICAgICAgICg1MTkpIDY1MCAwNjYw CjUzOSBHcmFuZCBWYWxsZXkgRHIuLCBDYW1icmlkZ2UsIE9udC4gTjNIIDJTMiAgICAgKDUxOSkg MjQxIDI0NjEKLSAtLS0tLS0tLS0tLS0tLS0gaHR0cDovL3d3dy5hamxjLndhdGVybG9vLm9uLmNh LyAtLS0tLS0tLS0tLS0tLS0tCgoKLS0tLS1CRUdJTiBQR1AgU0lHTkFUVVJFLS0tLS0KVmVyc2lv bjogR251UEcgdjEuNC4xMCAoR05VL0xpbnV4KQpDb21tZW50OiBVc2luZyBHbnVQRyB3aXRoIE1v emlsbGEgLSBodHRwOi8vd3d3LmVuaWdtYWlsLm5ldC8KCmlFWUVBUkVDQUFZRkFsQldZRDBBQ2dr UUdTOHlacTF1dnhCck9BQ2ZadmNvcnQyZlNJdjFqVElMNEk2NThhcnQKM2VNQW4yQUF0cGZNU3hI b0JBdy92cDdXRTN1OGprNmsKPXp5ZHgKLS0tLS1FTkQgUEdQIFNJR05BVFVSRS0tLS0tCgpfX19f X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fXwpYZW4tdXNlcnMgbWFp bGluZyBsaXN0Clhlbi11c2Vyc0BsaXN0cy54ZW4ub3JnCmh0dHA6Ly9saXN0cy54ZW4ub3JnL3hl bi11c2VycwoKCl9fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19f Clhlbi11c2VycyBtYWlsaW5nIGxpc3QKWGVuLXVzZXJzQGxpc3RzLnhlbi5vcmcKaHR0cDovL2xp c3RzLnhlbi5vcmcveGVuLXVzZXJz From xen-users-bounces@lists.xen.org Mon Sep 17 02:12:58 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Mon, 17 Sep 2012 02:12:58 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TDQoh-0000ZY-Jg; Mon, 17 Sep 2012 02:12:07 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TDQof-0000ZT-5Q for xen-users@lists.xen.org; Mon, 17 Sep 2012 02:12:05 +0000 Received: from [85.158.139.83:21040] by server-4.bemta-5.messagelabs.com id 4E/E4-23042-4F686505; Mon, 17 Sep 2012 02:12:04 +0000 X-Env-Sender: ajlill@ajlc.waterloo.on.ca X-Msg-Ref: server-5.tower-182.messagelabs.com!1347847921!30442158!1 X-Originating-IP: [64.7.134.25] X-SpamReason: No, hits=0.0 required=7.0 tests= X-StarScan-Received: X-StarScan-Version: 6.6.1.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 17805 invoked from network); 17 Sep 2012 02:12:03 -0000 Received: from ajlill.sentex.ca (HELO mail.ajlc.waterloo.on.ca) (64.7.134.25) by server-5.tower-182.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 17 Sep 2012 02:12:03 -0000 Received: from [10.19.61.4] (gloria.ajlc.waterloo.on.ca [10.19.61.4]) (authenticated bits=0) by mail.ajlc.waterloo.on.ca (8.14.3/8.14.3/Debian-9.4) with ESMTP id q8H2Bs8u028210 for ; Sun, 16 Sep 2012 22:11:54 -0400 Message-ID: <505686EA.9060801@ajlc.waterloo.on.ca> Date: Sun, 16 Sep 2012 22:11:54 -0400 From: Tony Lill User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:15.0) Gecko/20120827 Thunderbird/15.0 MIME-Version: 1.0 To: xen-users@lists.xen.org References: <003601cd9430$a381db70$ea859250$@gmail.com> <1347818899.25803.75.camel@dagon.hellion.org.uk> <004e01cd9446$b7636b20$262a4160$@gmail.com> <5056603D.8030007@ajlc.waterloo.on.ca> <006701cd9477$0d045820$270d0860$@gmail.com> In-Reply-To: <006701cd9477$0d045820$270d0860$@gmail.com> X-Enigmail-Version: 1.4.4 X-Spam-Status: No, score=-101.3 required=5.0 tests=ALL_TRUSTED,AWL, RP_MATCHES_RCVD,USER_IN_WHITELIST autolearn=ham version=3.3.1 X-Spam-Checker-Version: SpamAssassin 3.3.1 (2010-03-16) on mail.ajlc.waterloo.on.ca Subject: Re: [Xen-users] Setting up XEN domU causes RAID5 to fail? X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="windows-1252" Content-Transfer-Encoding: quoted-printable Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 When I tried to upgrade my xen systems to a pvops xen/linux combo, I found that high disk I/O would cause disk errors and caused disks to be thrown out of the raid and all sorts of other badness. High of course, is a relative term. For one of my boxes, copying a large file was enough, on another, it needed something like running backups on several VMs simultaneously or trying to start my VM's while rebuilding the raid. FWIW, I went back to Xen 3.4.4 and the SLES1 xenlinux kernel and they've been rock solid. On 09/16/2012 09:52 PM, Marc Tousignant wrote: > No messages in dmesg or on the console, though to be fair, the > root partition is "broken" at that point and can't write to any > files. I just tested again to be sure, this time I cant even cat > the logs. > = > -----Original Message----- From: xen-users-bounces@lists.xen.org = > [mailto:xen-users-bounces@lists.xen.org] On Behalf Of Tony Lill = > Sent: Sunday, September 16, 2012 7:27 PM To: = > xen-users@lists.xen.org Subject: Re: [Xen-users] Setting up XEN = > domU causes RAID5 to fail? > = > Are there any messages in the kernel log or dmesg regarding these = > disks? > = > On 09/16/2012 04:06 PM, Marc Tousignant wrote: >> FYI, I switched to file: and still the same issue occurred, with = >> one exception.. This time it "lost" the RAID members while = >> booting off the ISO. I hadn't even gotten to the install screens = >> yet. > = >> -----Original Message----- From: Ian Campbell = >> [mailto:Ian.Campbell@citrix.com] Sent: Sunday, September 16, 2012 >> 2:08 PM To: Marc Tousignant Cc: xen-users@lists.xen.org Subject: >> Re: [Xen-users] Setting up XEN domU causes RAID5 to fail? > = >> On Sun, 2012-09-16 at 18:28 +0100, Marc Tousignant wrote: > = >>> I then created several .img files in the xen_images folder = >>> using dd. For example (dd if=3D/dev/zero = >>> of=3D/images/xen_images/Win7x86_Base.img bs=3D1 count=3D1 seek=3D50G) >> [...] >>> I got to the point where it formatted the =93drive=94 and started = >>> installing, it failed on the extraction step saying my =93DVD=94 = >>> was bad. > = >> What does your guest config file look like, in particular the = >> disk line. > = >> Is there any chance that you have accidentally pointed the VM's = >> disks at one or more of the physical disks which makes up your = >> RAID array? > = >> Ian. > = > = > = >> _______________________________________________ Xen-users >> mailing list Xen-users@lists.xen.org >> http://lists.xen.org/xen-users > = > = > = > _______________________________________________ Xen-users mailing = > list Xen-users@lists.xen.org http://lists.xen.org/xen-users > = > = > _______________________________________________ Xen-users mailing = > list Xen-users@lists.xen.org http://lists.xen.org/xen-users > = - -- = Tony Lill, OCT, Tony.Lill@AJLC.Waterloo.ON.CA President, A. J. Lill Consultants (519) 650 0660 539 Grand Valley Dr., Cambridge, Ont. N3H 2S2 (519) 241 2461 - --------------- http://www.ajlc.waterloo.on.ca/ ---------------- -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.10 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://www.enigmail.net/ iEYEARECAAYFAlBWhuoACgkQGS8yZq1uvxATEACbB6d3xJ/hgvf5fXClnvHNC2SA G88AniIiriGdvl10JF49zyfBh01WEuvQ =3DoRVn -----END PGP SIGNATURE----- _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Mon Sep 17 02:12:58 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Mon, 17 Sep 2012 02:12:58 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TDQoh-0000ZY-Jg; Mon, 17 Sep 2012 02:12:07 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TDQof-0000ZT-5Q for xen-users@lists.xen.org; Mon, 17 Sep 2012 02:12:05 +0000 Received: from [85.158.139.83:21040] by server-4.bemta-5.messagelabs.com id 4E/E4-23042-4F686505; Mon, 17 Sep 2012 02:12:04 +0000 X-Env-Sender: ajlill@ajlc.waterloo.on.ca X-Msg-Ref: server-5.tower-182.messagelabs.com!1347847921!30442158!1 X-Originating-IP: [64.7.134.25] X-SpamReason: No, hits=0.0 required=7.0 tests= X-StarScan-Received: X-StarScan-Version: 6.6.1.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 17805 invoked from network); 17 Sep 2012 02:12:03 -0000 Received: from ajlill.sentex.ca (HELO mail.ajlc.waterloo.on.ca) (64.7.134.25) by server-5.tower-182.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 17 Sep 2012 02:12:03 -0000 Received: from [10.19.61.4] (gloria.ajlc.waterloo.on.ca [10.19.61.4]) (authenticated bits=0) by mail.ajlc.waterloo.on.ca (8.14.3/8.14.3/Debian-9.4) with ESMTP id q8H2Bs8u028210 for ; Sun, 16 Sep 2012 22:11:54 -0400 Message-ID: <505686EA.9060801@ajlc.waterloo.on.ca> Date: Sun, 16 Sep 2012 22:11:54 -0400 From: Tony Lill User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:15.0) Gecko/20120827 Thunderbird/15.0 MIME-Version: 1.0 To: xen-users@lists.xen.org References: <003601cd9430$a381db70$ea859250$@gmail.com> <1347818899.25803.75.camel@dagon.hellion.org.uk> <004e01cd9446$b7636b20$262a4160$@gmail.com> <5056603D.8030007@ajlc.waterloo.on.ca> <006701cd9477$0d045820$270d0860$@gmail.com> In-Reply-To: <006701cd9477$0d045820$270d0860$@gmail.com> X-Enigmail-Version: 1.4.4 X-Spam-Status: No, score=-101.3 required=5.0 tests=ALL_TRUSTED,AWL, RP_MATCHES_RCVD,USER_IN_WHITELIST autolearn=ham version=3.3.1 X-Spam-Checker-Version: SpamAssassin 3.3.1 (2010-03-16) on mail.ajlc.waterloo.on.ca Subject: Re: [Xen-users] Setting up XEN domU causes RAID5 to fail? X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="windows-1252" Content-Transfer-Encoding: quoted-printable Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 When I tried to upgrade my xen systems to a pvops xen/linux combo, I found that high disk I/O would cause disk errors and caused disks to be thrown out of the raid and all sorts of other badness. High of course, is a relative term. For one of my boxes, copying a large file was enough, on another, it needed something like running backups on several VMs simultaneously or trying to start my VM's while rebuilding the raid. FWIW, I went back to Xen 3.4.4 and the SLES1 xenlinux kernel and they've been rock solid. On 09/16/2012 09:52 PM, Marc Tousignant wrote: > No messages in dmesg or on the console, though to be fair, the > root partition is "broken" at that point and can't write to any > files. I just tested again to be sure, this time I cant even cat > the logs. > = > -----Original Message----- From: xen-users-bounces@lists.xen.org = > [mailto:xen-users-bounces@lists.xen.org] On Behalf Of Tony Lill = > Sent: Sunday, September 16, 2012 7:27 PM To: = > xen-users@lists.xen.org Subject: Re: [Xen-users] Setting up XEN = > domU causes RAID5 to fail? > = > Are there any messages in the kernel log or dmesg regarding these = > disks? > = > On 09/16/2012 04:06 PM, Marc Tousignant wrote: >> FYI, I switched to file: and still the same issue occurred, with = >> one exception.. This time it "lost" the RAID members while = >> booting off the ISO. I hadn't even gotten to the install screens = >> yet. > = >> -----Original Message----- From: Ian Campbell = >> [mailto:Ian.Campbell@citrix.com] Sent: Sunday, September 16, 2012 >> 2:08 PM To: Marc Tousignant Cc: xen-users@lists.xen.org Subject: >> Re: [Xen-users] Setting up XEN domU causes RAID5 to fail? > = >> On Sun, 2012-09-16 at 18:28 +0100, Marc Tousignant wrote: > = >>> I then created several .img files in the xen_images folder = >>> using dd. For example (dd if=3D/dev/zero = >>> of=3D/images/xen_images/Win7x86_Base.img bs=3D1 count=3D1 seek=3D50G) >> [...] >>> I got to the point where it formatted the =93drive=94 and started = >>> installing, it failed on the extraction step saying my =93DVD=94 = >>> was bad. > = >> What does your guest config file look like, in particular the = >> disk line. > = >> Is there any chance that you have accidentally pointed the VM's = >> disks at one or more of the physical disks which makes up your = >> RAID array? > = >> Ian. > = > = > = >> _______________________________________________ Xen-users >> mailing list Xen-users@lists.xen.org >> http://lists.xen.org/xen-users > = > = > = > _______________________________________________ Xen-users mailing = > list Xen-users@lists.xen.org http://lists.xen.org/xen-users > = > = > _______________________________________________ Xen-users mailing = > list Xen-users@lists.xen.org http://lists.xen.org/xen-users > = - -- = Tony Lill, OCT, Tony.Lill@AJLC.Waterloo.ON.CA President, A. J. Lill Consultants (519) 650 0660 539 Grand Valley Dr., Cambridge, Ont. N3H 2S2 (519) 241 2461 - --------------- http://www.ajlc.waterloo.on.ca/ ---------------- -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.10 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://www.enigmail.net/ iEYEARECAAYFAlBWhuoACgkQGS8yZq1uvxATEACbB6d3xJ/hgvf5fXClnvHNC2SA G88AniIiriGdvl10JF49zyfBh01WEuvQ =3DoRVn -----END PGP SIGNATURE----- _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Mon Sep 17 02:56:51 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Mon, 17 Sep 2012 02:56:51 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TDRV5-0000ze-Cf; Mon, 17 Sep 2012 02:55:55 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TDRV3-0000zZ-Do for xen-users@lists.xen.org; Mon, 17 Sep 2012 02:55:53 +0000 Received: from [85.158.137.99:22111] by server-6.bemta-3.messagelabs.com id BC/92-29694-83196505; Mon, 17 Sep 2012 02:55:52 +0000 X-Env-Sender: myrdhn@gmail.com X-Msg-Ref: server-9.tower-217.messagelabs.com!1347850549!14750767!1 X-Originating-IP: [209.85.216.45] X-SpamReason: No, hits=0.3 required=7.0 tests=ML_RADAR_SPEW_LINKS_14, RCVD_BY_IP,spamassassin: X-StarScan-Received: X-StarScan-Version: 6.6.1.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 15425 invoked from network); 17 Sep 2012 02:55:51 -0000 Received: from mail-qa0-f45.google.com (HELO mail-qa0-f45.google.com) (209.85.216.45) by server-9.tower-217.messagelabs.com with RC4-SHA encrypted SMTP; 17 Sep 2012 02:55:51 -0000 Received: by qadc10 with SMTP id c10so1433139qad.11 for ; Sun, 16 Sep 2012 19:55:49 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=from:to:references:in-reply-to:subject:date:message-id:mime-version :content-type:content-transfer-encoding:x-mailer:thread-index :content-language; bh=rx88eaE8KXM99lokYQ54VuwRMMHnq79HzY90VhkxXf0=; b=bkAIkifJOnmvOtxUUNXW5fM5XcR9hCeG9/oZ1DLv4GiI+Qn49kD47eIQkFneXEdWjg uVXnHbEIV0P5t88r1yspPlLBoLoJnQR4cuYWsWCbJhT1VRMyEjHVMek0mtDpIFeZnGjL lKCEmyhYHr7tjTrlTiC3DpIsVuipAxY9jC7UPEL5LxoffS4H44JhKkA7qJNO1o7PZtVe ipZtT5CxK1l6OVKpCAtuAP+At1DqTvsVcRtZTnJoKZ6nBwLnfarko3v0/XQSso+GeK/R 71rscK9SP5NDNWYKt8eVYLXaLqykOYcZpJ9axUhhtjPTelW3mPLjTdQn88oPqIXCxuo5 X2bw== Received: by 10.229.137.71 with SMTP id v7mr6408862qct.137.1347850549535; Sun, 16 Sep 2012 19:55:49 -0700 (PDT) Received: from Belldandy (c-76-119-253-48.hsd1.ma.comcast.net. [76.119.253.48]) by mx.google.com with ESMTPS id l3sm13524414qan.19.2012.09.16.19.55.48 (version=TLSv1/SSLv3 cipher=OTHER); Sun, 16 Sep 2012 19:55:49 -0700 (PDT) From: "Marc Tousignant" To: "'Tony Lill'" , References: <003601cd9430$a381db70$ea859250$@gmail.com> <1347818899.25803.75.camel@dagon.hellion.org.uk> <004e01cd9446$b7636b20$262a4160$@gmail.com> <5056603D.8030007@ajlc.waterloo.on.ca> <006701cd9477$0d045820$270d0860$@gmail.com> <505686EA.9060801@ajlc.waterloo.on.ca> In-Reply-To: <505686EA.9060801@ajlc.waterloo.on.ca> Date: Sun, 16 Sep 2012 22:55:51 -0400 Message-ID: <006e01cd947f$f3c25890$db4709b0$@gmail.com> MIME-Version: 1.0 X-Mailer: Microsoft Outlook 14.0 Thread-Index: AQEtIveC4IhcOcllJOhnnzkXfTJ4EAF4akKmAbXW2NwBi1ebzAHmfEp2AbO1nFOYjBs4wA== Content-Language: en-us Subject: Re: [Xen-users] Setting up XEN domU causes RAID5 to fail? X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org Maybe that is my issue. I'll ask one of my coworkers if he can misplace a 2TB drive and I can eliminate the RAID. I had a few 500GB drives laying around and decided to repurpose them. MarcT -----Original Message----- From: xen-users-bounces@lists.xen.org [mailto:xen-users-bounces@lists.xen.org] On Behalf Of Tony Lill Sent: Sunday, September 16, 2012 10:12 PM To: xen-users@lists.xen.org Subject: Re: [Xen-users] Setting up XEN domU causes RAID5 to fail? -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 When I tried to upgrade my xen systems to a pvops xen/linux combo, I found that high disk I/O would cause disk errors and caused disks to be thrown out of the raid and all sorts of other badness. High of course, is a relative term. For one of my boxes, copying a large file was enough, on another, it needed something like running backups on several VMs simultaneously or trying to start my VM's while rebuilding the raid. FWIW, I went back to Xen 3.4.4 and the SLES1 xenlinux kernel and they've been rock solid. On 09/16/2012 09:52 PM, Marc Tousignant wrote: > No messages in dmesg or on the console, though to be fair, the root > partition is "broken" at that point and can't write to any files. I > just tested again to be sure, this time I cant even cat the logs. > > -----Original Message----- From: xen-users-bounces@lists.xen.org > [mailto:xen-users-bounces@lists.xen.org] On Behalf Of Tony Lill > Sent: Sunday, September 16, 2012 7:27 PM To: > xen-users@lists.xen.org Subject: Re: [Xen-users] Setting up XEN domU > causes RAID5 to fail? > > Are there any messages in the kernel log or dmesg regarding these > disks? > > On 09/16/2012 04:06 PM, Marc Tousignant wrote: >> FYI, I switched to file: and still the same issue occurred, with one >> exception.. This time it "lost" the RAID members while booting off >> the ISO. I hadn't even gotten to the install screens yet. > >> -----Original Message----- From: Ian Campbell >> [mailto:Ian.Campbell@citrix.com] Sent: Sunday, September 16, 2012 >> 2:08 PM To: Marc Tousignant Cc: xen-users@lists.xen.org Subject: >> Re: [Xen-users] Setting up XEN domU causes RAID5 to fail? > >> On Sun, 2012-09-16 at 18:28 +0100, Marc Tousignant wrote: > >>> I then created several .img files in the xen_images folder using dd. >>> For example (dd if=/dev/zero of=/images/xen_images/Win7x86_Base.img >>> bs=1 count=1 seek=50G) >> [...] >>> I got to the point where it formatted the "drive" and started >>> installing, it failed on the extraction step saying my "DVD" >>> was bad. > >> What does your guest config file look like, in particular the disk >> line. > >> Is there any chance that you have accidentally pointed the VM's disks >> at one or more of the physical disks which makes up your RAID array? > >> Ian. > > > >> _______________________________________________ Xen-users mailing >> list Xen-users@lists.xen.org http://lists.xen.org/xen-users > > > > _______________________________________________ Xen-users mailing list > Xen-users@lists.xen.org http://lists.xen.org/xen-users > > > _______________________________________________ Xen-users mailing list > Xen-users@lists.xen.org http://lists.xen.org/xen-users > - -- Tony Lill, OCT, Tony.Lill@AJLC.Waterloo.ON.CA President, A. J. Lill Consultants (519) 650 0660 539 Grand Valley Dr., Cambridge, Ont. N3H 2S2 (519) 241 2461 - --------------- http://www.ajlc.waterloo.on.ca/ ---------------- -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.10 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://www.enigmail.net/ iEYEARECAAYFAlBWhuoACgkQGS8yZq1uvxATEACbB6d3xJ/hgvf5fXClnvHNC2SA G88AniIiriGdvl10JF49zyfBh01WEuvQ =oRVn -----END PGP SIGNATURE----- _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Mon Sep 17 02:56:51 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Mon, 17 Sep 2012 02:56:51 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TDRV5-0000ze-Cf; Mon, 17 Sep 2012 02:55:55 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TDRV3-0000zZ-Do for xen-users@lists.xen.org; Mon, 17 Sep 2012 02:55:53 +0000 Received: from [85.158.137.99:22111] by server-6.bemta-3.messagelabs.com id BC/92-29694-83196505; Mon, 17 Sep 2012 02:55:52 +0000 X-Env-Sender: myrdhn@gmail.com X-Msg-Ref: server-9.tower-217.messagelabs.com!1347850549!14750767!1 X-Originating-IP: [209.85.216.45] X-SpamReason: No, hits=0.3 required=7.0 tests=ML_RADAR_SPEW_LINKS_14, RCVD_BY_IP,spamassassin: X-StarScan-Received: X-StarScan-Version: 6.6.1.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 15425 invoked from network); 17 Sep 2012 02:55:51 -0000 Received: from mail-qa0-f45.google.com (HELO mail-qa0-f45.google.com) (209.85.216.45) by server-9.tower-217.messagelabs.com with RC4-SHA encrypted SMTP; 17 Sep 2012 02:55:51 -0000 Received: by qadc10 with SMTP id c10so1433139qad.11 for ; Sun, 16 Sep 2012 19:55:49 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=from:to:references:in-reply-to:subject:date:message-id:mime-version :content-type:content-transfer-encoding:x-mailer:thread-index :content-language; bh=rx88eaE8KXM99lokYQ54VuwRMMHnq79HzY90VhkxXf0=; b=bkAIkifJOnmvOtxUUNXW5fM5XcR9hCeG9/oZ1DLv4GiI+Qn49kD47eIQkFneXEdWjg uVXnHbEIV0P5t88r1yspPlLBoLoJnQR4cuYWsWCbJhT1VRMyEjHVMek0mtDpIFeZnGjL lKCEmyhYHr7tjTrlTiC3DpIsVuipAxY9jC7UPEL5LxoffS4H44JhKkA7qJNO1o7PZtVe ipZtT5CxK1l6OVKpCAtuAP+At1DqTvsVcRtZTnJoKZ6nBwLnfarko3v0/XQSso+GeK/R 71rscK9SP5NDNWYKt8eVYLXaLqykOYcZpJ9axUhhtjPTelW3mPLjTdQn88oPqIXCxuo5 X2bw== Received: by 10.229.137.71 with SMTP id v7mr6408862qct.137.1347850549535; Sun, 16 Sep 2012 19:55:49 -0700 (PDT) Received: from Belldandy (c-76-119-253-48.hsd1.ma.comcast.net. [76.119.253.48]) by mx.google.com with ESMTPS id l3sm13524414qan.19.2012.09.16.19.55.48 (version=TLSv1/SSLv3 cipher=OTHER); Sun, 16 Sep 2012 19:55:49 -0700 (PDT) From: "Marc Tousignant" To: "'Tony Lill'" , References: <003601cd9430$a381db70$ea859250$@gmail.com> <1347818899.25803.75.camel@dagon.hellion.org.uk> <004e01cd9446$b7636b20$262a4160$@gmail.com> <5056603D.8030007@ajlc.waterloo.on.ca> <006701cd9477$0d045820$270d0860$@gmail.com> <505686EA.9060801@ajlc.waterloo.on.ca> In-Reply-To: <505686EA.9060801@ajlc.waterloo.on.ca> Date: Sun, 16 Sep 2012 22:55:51 -0400 Message-ID: <006e01cd947f$f3c25890$db4709b0$@gmail.com> MIME-Version: 1.0 X-Mailer: Microsoft Outlook 14.0 Thread-Index: AQEtIveC4IhcOcllJOhnnzkXfTJ4EAF4akKmAbXW2NwBi1ebzAHmfEp2AbO1nFOYjBs4wA== Content-Language: en-us Subject: Re: [Xen-users] Setting up XEN domU causes RAID5 to fail? X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org Maybe that is my issue. I'll ask one of my coworkers if he can misplace a 2TB drive and I can eliminate the RAID. I had a few 500GB drives laying around and decided to repurpose them. MarcT -----Original Message----- From: xen-users-bounces@lists.xen.org [mailto:xen-users-bounces@lists.xen.org] On Behalf Of Tony Lill Sent: Sunday, September 16, 2012 10:12 PM To: xen-users@lists.xen.org Subject: Re: [Xen-users] Setting up XEN domU causes RAID5 to fail? -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 When I tried to upgrade my xen systems to a pvops xen/linux combo, I found that high disk I/O would cause disk errors and caused disks to be thrown out of the raid and all sorts of other badness. High of course, is a relative term. For one of my boxes, copying a large file was enough, on another, it needed something like running backups on several VMs simultaneously or trying to start my VM's while rebuilding the raid. FWIW, I went back to Xen 3.4.4 and the SLES1 xenlinux kernel and they've been rock solid. On 09/16/2012 09:52 PM, Marc Tousignant wrote: > No messages in dmesg or on the console, though to be fair, the root > partition is "broken" at that point and can't write to any files. I > just tested again to be sure, this time I cant even cat the logs. > > -----Original Message----- From: xen-users-bounces@lists.xen.org > [mailto:xen-users-bounces@lists.xen.org] On Behalf Of Tony Lill > Sent: Sunday, September 16, 2012 7:27 PM To: > xen-users@lists.xen.org Subject: Re: [Xen-users] Setting up XEN domU > causes RAID5 to fail? > > Are there any messages in the kernel log or dmesg regarding these > disks? > > On 09/16/2012 04:06 PM, Marc Tousignant wrote: >> FYI, I switched to file: and still the same issue occurred, with one >> exception.. This time it "lost" the RAID members while booting off >> the ISO. I hadn't even gotten to the install screens yet. > >> -----Original Message----- From: Ian Campbell >> [mailto:Ian.Campbell@citrix.com] Sent: Sunday, September 16, 2012 >> 2:08 PM To: Marc Tousignant Cc: xen-users@lists.xen.org Subject: >> Re: [Xen-users] Setting up XEN domU causes RAID5 to fail? > >> On Sun, 2012-09-16 at 18:28 +0100, Marc Tousignant wrote: > >>> I then created several .img files in the xen_images folder using dd. >>> For example (dd if=/dev/zero of=/images/xen_images/Win7x86_Base.img >>> bs=1 count=1 seek=50G) >> [...] >>> I got to the point where it formatted the "drive" and started >>> installing, it failed on the extraction step saying my "DVD" >>> was bad. > >> What does your guest config file look like, in particular the disk >> line. > >> Is there any chance that you have accidentally pointed the VM's disks >> at one or more of the physical disks which makes up your RAID array? > >> Ian. > > > >> _______________________________________________ Xen-users mailing >> list Xen-users@lists.xen.org http://lists.xen.org/xen-users > > > > _______________________________________________ Xen-users mailing list > Xen-users@lists.xen.org http://lists.xen.org/xen-users > > > _______________________________________________ Xen-users mailing list > Xen-users@lists.xen.org http://lists.xen.org/xen-users > - -- Tony Lill, OCT, Tony.Lill@AJLC.Waterloo.ON.CA President, A. J. Lill Consultants (519) 650 0660 539 Grand Valley Dr., Cambridge, Ont. N3H 2S2 (519) 241 2461 - --------------- http://www.ajlc.waterloo.on.ca/ ---------------- -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.10 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://www.enigmail.net/ iEYEARECAAYFAlBWhuoACgkQGS8yZq1uvxATEACbB6d3xJ/hgvf5fXClnvHNC2SA G88AniIiriGdvl10JF49zyfBh01WEuvQ =oRVn -----END PGP SIGNATURE----- _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Mon Sep 17 03:13:27 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Mon, 17 Sep 2012 03:13:27 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TDRlC-0001ln-AQ; Mon, 17 Sep 2012 03:12:34 +0000 Received: from mail27.messagelabs.com ([193.109.254.147]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TDRl9-0001ld-W0 for xen-users@lists.xensource.com; Mon, 17 Sep 2012 03:12:32 +0000 X-Env-Sender: pingh.cd@gmail.com X-Msg-Ref: server-2.tower-27.messagelabs.com!1347851543!11226400!1 X-Originating-IP: [216.139.236.26] X-SpamReason: No, hits=0.5 required=7.0 tests=BODY_RANDOM_LONG, ML_RADAR_SPEW_LINKS_14,spamassassin: X-StarScan-Received: X-StarScan-Version: 6.6.1.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 22022 invoked from network); 17 Sep 2012 03:12:24 -0000 Received: from sam.nabble.com (HELO sam.nabble.com) (216.139.236.26) by server-2.tower-27.messagelabs.com with AES256-SHA encrypted SMTP; 17 Sep 2012 03:12:24 -0000 Received: from [192.168.236.26] (helo=sam.nabble.com) by sam.nabble.com with esmtp (Exim 4.72) (envelope-from ) id 1TDRl0-00070p-VQ for xen-users@lists.xensource.com; Sun, 16 Sep 2012 20:12:23 -0700 Date: Sun, 16 Sep 2012 20:12:22 -0700 (PDT) From: Robin hp To: xen-users@lists.xensource.com Message-ID: <1347851542961-5711309.post@n5.nabble.com> MIME-Version: 1.0 Subject: [Xen-users] Performance of PVM and HVM X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org Recently, I met a strange issue about vm's performance. I downloaded Jeremy's branch of xen/next-2.6.32 (version:2.6.32.57)for dom0, and compiled xen-4.1.3 source code for xend service, then I used Unixbench to test the performance of native, dom0, and domU(HVM and PVM). By the way, I set 4 vcpus and 2048M memory for each VM. And I got the following results: It seems that dom0's performance is so bad from native, and PVM so on. But HVM's performance is better than my expected, it's so close to native. It's weird to me, or it's just a normal thing? Is any one else experiencing this? Any reply or suggests will be appreciated. ========native:(2.6.32.57 without xen)============ System: localhost.localdomain: GNU/Linux OS: GNU/Linux -- 2.6.32.57 -- #1 SMP Thu Sep 6 10:42:38 CST 2012 Machine: x86_64 (x86_64) Language: en_US.utf8 (charmap="UTF-8", collate="UTF-8") CPU 0: Intel(R) Core(TM) i5-2400 CPU @ 3.10GHz (6185.3 bogomips) Hyper-Threading, x86-64, MMX, Physical Address Ext, SYSENTER/SYSEXIT, SYSCALL/SYSRET, Intel virtualization CPU 1: Intel(R) Core(TM) i5-2400 CPU @ 3.10GHz (6185.9 bogomips) Hyper-Threading, x86-64, MMX, Physical Address Ext, SYSENTER/SYSEXIT, SYSCALL/SYSRET, Intel virtualization CPU 2: Intel(R) Core(TM) i5-2400 CPU @ 3.10GHz (6185.9 bogomips) Hyper-Threading, x86-64, MMX, Physical Address Ext, SYSENTER/SYSEXIT, SYSCALL/SYSRET, Intel virtualization CPU 3: Intel(R) Core(TM) i5-2400 CPU @ 3.10GHz (6185.9 bogomips) Hyper-Threading, x86-64, MMX, Physical Address Ext, SYSENTER/SYSEXIT, SYSCALL/SYSRET, Intel virtualization 11:01:15 up 9 min, 2 users, load average: 0.15, 0.41, 0.26; runlevel 5 Double-Precision Whetstone 4023.5 MWIPS (9.9 s, 7 samples) Execl Throughput 2384.2 lps (29.7 s, 2 samples) File Copy 1024 bufsize 2000 maxblocks 1134757.4 KBps (30.0 s, 2 samples) File Copy 256 bufsize 500 maxblocks 312913.0 KBps (30.0 s, 2 samples) File Copy 4096 bufsize 8000 maxblocks 2731953.1 KBps (30.0 s, 2 samples) Pipe Throughput 2043709.3 lps (10.0 s, 7 samples) Pipe-based Context Switching 105547.0 lps (10.0 s, 7 samples) Process Creation 10013.4 lps (30.0 s, 2 samples) Shell Scripts (1 concurrent) 4158.8 lpm (60.0 s, 2 samples) Shell Scripts (8 concurrent) 2961.2 lpm (60.0 s, 2 samples) System Call Overhead 4431920.0 lps (10.0 s, 7 samples) System Benchmarks Index Values BASELINE RESULT INDEX Dhrystone 2 using register variables 116700.0 37435723.9 3207.9 Double-Precision Whetstone 55.0 4023.5 731.5 Execl Throughput 43.0 2384.2 554.5 File Copy 1024 bufsize 2000 maxblocks 3960.0 1134757.4 2865.5 File Copy 256 bufsize 500 maxblocks 1655.0 312913.0 1890.7 File Copy 4096 bufsize 8000 maxblocks 5800.0 2731953.1 4710.3 Pipe Throughput 12440.0 2043709.3 1642.9 Pipe-based Context Switching 4000.0 105547.0 263.9 Process Creation 126.0 10013.4 794.7 Shell Scripts (1 concurrent) 42.4 4158.8 980.9 Shell Scripts (8 concurrent) 6.0 2961.2 4935.4 System Call Overhead 15000.0 4431920.0 2954.6 ======== System Benchmarks Index Score 1529.3 ------------------------------------------------------------------------ Benchmark Run: Thu Sep 06 2012 11:30:07 - 11:59:09 4 CPUs in system; running 4 parallel copies of tests Dhrystone 2 using register variables 141361626.6 lps (10.0 s, 7 samples) Double-Precision Whetstone 15160.0 MWIPS (9.9 s, 7 samples) Execl Throughput 20000.9 lps (29.6 s, 2 samples) File Copy 1024 bufsize 2000 maxblocks 1127449.6 KBps (30.0 s, 2 samples) File Copy 256 bufsize 500 maxblocks 299709.9 KBps (30.0 s, 2 samples) File Copy 4096 bufsize 8000 maxblocks 3197973.3 KBps (30.0 s, 2 samples) Pipe Throughput 7732066.4 lps (10.0 s, 7 samples) Pipe-based Context Switching 1801378.7 lps (10.0 s, 7 samples) Process Creation 75567.5 lps (30.0 s, 2 samples) Shell Scripts (1 concurrent) 25427.3 lpm (60.0 s, 2 samples) Shell Scripts (8 concurrent) 3397.8 lpm (60.0 s, 2 samples) System Call Overhead 12278676.0 lps (10.0 s, 7 samples) System Benchmarks Index Values BASELINE RESULT INDEX Dhrystone 2 using register variables 116700.0 141361626.6 12113.2 Double-Precision Whetstone 55.0 15160.0 2756.4 Execl Throughput 43.0 20000.9 4651.4 File Copy 1024 bufsize 2000 maxblocks 3960.0 1127449.6 2847.1 File Copy 256 bufsize 500 maxblocks 1655.0 299709.9 1810.9 File Copy 4096 bufsize 8000 maxblocks 5800.0 3197973.3 5513.7 Pipe Throughput 12440.0 7732066.4 6215.5 Pipe-based Context Switching 4000.0 1801378.7 4503.4 Process Creation 126.0 75567.5 5997.4 Shell Scripts (1 concurrent) 42.4 25427.3 5997.0 Shell Scripts (8 concurrent) 6.0 3397.8 5663.1 System Call Overhead 15000.0 12278676.0 8185.8 ======== System Benchmarks Index Score 4929.8 ========native:(2.6.32.57 with xen)============ System: localhost.localdomain: GNU/Linux OS: GNU/Linux -- 2.6.32.57 -- #1 SMP Wed Sep 5 16:17:40 CST 2012 Machine: x86_64 (x86_64) Language: en_US.utf8 (charmap="UTF-8", collate="UTF-8") CPU 0: Intel(R) Core(TM) i5-2400 CPU @ 3.10GHz (6185.9 bogomips) Hyper-Threading, x86-64, MMX, Physical Address Ext, SYSENTER/SYSEXIT, SYSCALL/SYSRET CPU 1: Intel(R) Core(TM) i5-2400 CPU @ 3.10GHz (6185.9 bogomips) Hyper-Threading, x86-64, MMX, Physical Address Ext, SYSENTER/SYSEXIT, SYSCALL/SYSRET CPU 2: Intel(R) Core(TM) i5-2400 CPU @ 3.10GHz (6185.9 bogomips) Hyper-Threading, x86-64, MMX, Physical Address Ext, SYSENTER/SYSEXIT, SYSCALL/SYSRET CPU 3: Intel(R) Core(TM) i5-2400 CPU @ 3.10GHz (6185.9 bogomips) Hyper-Threading, x86-64, MMX, Physical Address Ext, SYSENTER/SYSEXIT, SYSCALL/SYSRET 16:39:07 up 5 min, 2 users, load average: 0.41, 0.14, 0.05; runlevel 5 Double-Precision Whetstone 4014.3 MWIPS (10.0 s, 7 samples) Execl Throughput 1539.9 lps (29.7 s, 2 samples) File Copy 1024 bufsize 2000 maxblocks 230816.4 KBps (30.0 s, 2 samples) File Copy 256 bufsize 500 maxblocks 59384.4 KBps (30.0 s, 2 samples) File Copy 4096 bufsize 8000 maxblocks 799672.5 KBps (30.0 s, 2 samples) Pipe Throughput 464331.1 lps (10.0 s, 7 samples) Pipe-based Context Switching 84464.6 lps (10.0 s, 7 samples) Process Creation 1416.4 lps (30.0 s, 2 samples) Shell Scripts (1 concurrent) 1777.9 lpm (60.0 s, 2 samples) Shell Scripts (8 concurrent) 1077.6 lpm (60.1 s, 2 samples) System Call Overhead 588951.1 lps (10.0 s, 7 samples) System Benchmarks Index Values BASELINE RESULT INDEX Dhrystone 2 using register variables 116700.0 37551405.9 3217.8 Double-Precision Whetstone 55.0 4014.3 729.9 Execl Throughput 43.0 1539.9 358.1 File Copy 1024 bufsize 2000 maxblocks 3960.0 230816.4 582.9 File Copy 256 bufsize 500 maxblocks 1655.0 59384.4 358.8 File Copy 4096 bufsize 8000 maxblocks 5800.0 799672.5 1378.7 Pipe Throughput 12440.0 464331.1 373.3 Pipe-based Context Switching 4000.0 84464.6 211.2 Process Creation 126.0 1416.4 112.4 Shell Scripts (1 concurrent) 42.4 1777.9 419.3 Shell Scripts (8 concurrent) 6.0 1077.6 1796.0 System Call Overhead 15000.0 588951.1 392.6 ======== System Benchmarks Index Score 541.5 ------------------------------------------------------------------------ Benchmark Run: Wed Sep 05 2012 17:08:17 - 17:37:42 4 CPUs in system; running 4 parallel copies of tests Dhrystone 2 using register variables 141651867.8 lps (10.0 s, 7 samples) Double-Precision Whetstone 15164.7 MWIPS (9.9 s, 7 samples) Execl Throughput 4973.0 lps (29.5 s, 2 samples) File Copy 1024 bufsize 2000 maxblocks 314355.0 KBps (30.0 s, 2 samples) File Copy 256 bufsize 500 maxblocks 80269.7 KBps (30.0 s, 2 samples) File Copy 4096 bufsize 8000 maxblocks 1157706.6 KBps (30.0 s, 2 samples) Pipe Throughput 1733674.4 lps (10.0 s, 7 samples) Pipe-based Context Switching 336552.6 lps (10.0 s, 7 samples) Process Creation 10207.0 lps (30.0 s, 2 samples) Shell Scripts (1 concurrent) 8880.3 lpm (60.0 s, 2 samples) Shell Scripts (8 concurrent) 1197.1 lpm (60.1 s, 2 samples) System Call Overhead 2126022.5 lps (10.0 s, 7 samples) System Benchmarks Index Values BASELINE RESULT INDEX Dhrystone 2 using register variables 116700.0 141651867.8 12138.1 Double-Precision Whetstone 55.0 15164.7 2757.2 Execl Throughput 43.0 4973.0 1156.5 File Copy 1024 bufsize 2000 maxblocks 3960.0 314355.0 793.8 File Copy 256 bufsize 500 maxblocks 1655.0 80269.7 485.0 File Copy 4096 bufsize 8000 maxblocks 5800.0 1157706.6 1996.0 Pipe Throughput 12440.0 1733674.4 1393.6 Pipe-based Context Switching 4000.0 336552.6 841.4 Process Creation 126.0 10207.0 810.1 Shell Scripts (1 concurrent) 42.4 8880.3 2094.4 Shell Scripts (8 concurrent) 6.0 1197.1 1995.2 System Call Overhead 15000.0 2126022.5 1417.3 ======== System Benchmarks Index Score 1532.1 ========native:(PVM rhel6.1)============ System: xenpv1.myxen.com: GNU/Linux OS: GNU/Linux -- 2.6.32-131.0.15.el6.x86_64 -- #1 SMP Tue May 10 15:42:40 EDT 2011 Machine: x86_64 (x86_64) Language: en_US.utf8 (charmap="UTF-8", collate="UTF-8") CPU 0: Intel(R) Core(TM) i5-2400 CPU @ 3.10GHz (6186.4 bogomips) Hyper-Threading, x86-64, MMX, Physical Address Ext, SYSCALL/SYSRET CPU 1: Intel(R) Core(TM) i5-2400 CPU @ 3.10GHz (6186.4 bogomips) Hyper-Threading, x86-64, MMX, Physical Address Ext, SYSCALL/SYSRET CPU 2: Intel(R) Core(TM) i5-2400 CPU @ 3.10GHz (6186.4 bogomips) Hyper-Threading, x86-64, MMX, Physical Address Ext, SYSCALL/SYSRET CPU 3: Intel(R) Core(TM) i5-2400 CPU @ 3.10GHz (6186.4 bogomips) Hyper-Threading, x86-64, MMX, Physical Address Ext, SYSCALL/SYSRET 09:21:10 up 1 min, 1 user, load average: 0.09, 0.03, 0.00; runlevel 3 ------------------------------------------------------------------------ Benchmark Run: Fri Sep 14 2012 09:21:10 - 09:49:19 4 CPUs in system; running 1 parallel copy of tests Dhrystone 2 using register variables 36560766.3 lps (10.0 s, 7 samples) Double-Precision Whetstone 3962.1 MWIPS (9.9 s, 7 samples) Execl Throughput 798.0 lps (30.0 s, 2 samples) File Copy 1024 bufsize 2000 maxblocks 307212.1 KBps (30.0 s, 2 samples) File Copy 256 bufsize 500 maxblocks 77826.9 KBps (30.0 s, 2 samples) File Copy 4096 bufsize 8000 maxblocks 989297.2 KBps (30.0 s, 2 samples) Pipe Throughput 415705.7 lps (10.0 s, 7 samples) Pipe-based Context Switching 82646.7 lps (10.0 s, 7 samples) Process Creation 1643.2 lps (30.0 s, 2 samples) Shell Scripts (1 concurrent) 2111.5 lpm (60.0 s, 2 samples) Shell Scripts (8 concurrent) 1222.8 lpm (60.1 s, 2 samples) System Call Overhead 442797.7 lps (10.0 s, 7 samples) System Benchmarks Index Values BASELINE RESULT INDEX Dhrystone 2 using register variables 116700.0 36560766.3 3132.9 Double-Precision Whetstone 55.0 3962.1 720.4 Execl Throughput 43.0 798.0 185.6 File Copy 1024 bufsize 2000 maxblocks 3960.0 307212.1 775.8 File Copy 256 bufsize 500 maxblocks 1655.0 77826.9 470.3 File Copy 4096 bufsize 8000 maxblocks 5800.0 989297.2 1705.7 Pipe Throughput 12440.0 415705.7 334.2 Pipe-based Context Switching 4000.0 82646.7 206.6 Process Creation 126.0 1643.2 130.4 Shell Scripts (1 concurrent) 42.4 2111.5 498.0 Shell Scripts (8 concurrent) 6.0 1222.8 2038.0 System Call Overhead 15000.0 442797.7 295.2 ======== System Benchmarks Index Score 546.1 ------------------------------------------------------------------------ Benchmark Run: Fri Sep 14 2012 09:49:19 - 10:17:31 4 CPUs in system; running 4 parallel copies of tests Dhrystone 2 using register variables 139304316.2 lps (10.0 s, 7 samples) Double-Precision Whetstone 14960.7 MWIPS (9.9 s, 7 samples) Execl Throughput 5607.6 lps (30.0 s, 2 samples) File Copy 1024 bufsize 2000 maxblocks 498246.2 KBps (30.0 s, 2 samples) File Copy 256 bufsize 500 maxblocks 121580.0 KBps (30.0 s, 2 samples) File Copy 4096 bufsize 8000 maxblocks 1649657.6 KBps (30.1 s, 2 samples) Pipe Throughput 1574427.7 lps (10.0 s, 7 samples) Pipe-based Context Switching 327122.9 lps (10.0 s, 7 samples) Process Creation 10641.0 lps (30.0 s, 2 samples) Shell Scripts (1 concurrent) 9917.6 lpm (60.0 s, 2 samples) Shell Scripts (8 concurrent) 1351.8 lpm (60.1 s, 2 samples) System Call Overhead 1605775.2 lps (10.0 s, 7 samples) System Benchmarks Index Values BASELINE RESULT INDEX Dhrystone 2 using register variables 116700.0 139304316.2 11937.0 Double-Precision Whetstone 55.0 14960.7 2720.1 Execl Throughput 43.0 5607.6 1304.1 File Copy 1024 bufsize 2000 maxblocks 3960.0 498246.2 1258.2 File Copy 256 bufsize 500 maxblocks 1655.0 121580.0 734.6 File Copy 4096 bufsize 8000 maxblocks 5800.0 1649657.6 2844.2 Pipe Throughput 12440.0 1574427.7 1265.6 Pipe-based Context Switching 4000.0 327122.9 817.8 Process Creation 126.0 10641.0 844.5 Shell Scripts (1 concurrent) 42.4 9917.6 2339.0 Shell Scripts (8 concurrent) 6.0 1351.8 2253.0 System Call Overhead 15000.0 1605775.2 1070.5 ======== System Benchmarks Index Score 1691.6 ========native:(HVM rhel6.1)============ System: hvmserver0.myxen.com: GNU/Linux OS: GNU/Linux -- 2.6.32-131.0.15.el6.x86_64 -- #1 SMP Tue May 10 15:42:40 EDT 2011 Machine: x86_64 (x86_64) Language: en_US.utf8 (charmap="UTF-8", collate="UTF-8") CPU 0: Intel(R) Core(TM) i5-2400 CPU @ 3.10GHz (6186.4 bogomips) Hyper-Threading, x86-64, MMX, Physical Address Ext, SYSCALL/SYSRET CPU 1: Intel(R) Core(TM) i5-2400 CPU @ 3.10GHz (6185.2 bogomips) Hyper-Threading, x86-64, MMX, Physical Address Ext, SYSCALL/SYSRET CPU 2: Intel(R) Core(TM) i5-2400 CPU @ 3.10GHz (6185.4 bogomips) Hyper-Threading, x86-64, MMX, Physical Address Ext, SYSCALL/SYSRET CPU 3: Intel(R) Core(TM) i5-2400 CPU @ 3.10GHz (6185.4 bogomips) Hyper-Threading, x86-64, MMX, Physical Address Ext, SYSCALL/SYSRET 10:21:14 up 2 min, 1 user, load average: 0.13, 0.12, 0.05; runlevel 3 ------------------------------------------------------------------------ Benchmark Run: Fri Sep 14 2012 10:21:14 - 10:49:17 4 CPUs in system; running 1 parallel copy of tests Dhrystone 2 using register variables 35232485.6 lps (10.0 s, 7 samples) Double-Precision Whetstone 3877.4 MWIPS (9.7 s, 7 samples) Execl Throughput 1939.8 lps (30.0 s, 2 samples) File Copy 1024 bufsize 2000 maxblocks 966506.7 KBps (30.0 s, 2 samples) File Copy 256 bufsize 500 maxblocks 266621.2 KBps (30.0 s, 2 samples) File Copy 4096 bufsize 8000 maxblocks 2444019.5 KBps (30.0 s, 2 samples) Pipe Throughput 1590900.5 lps (10.0 s, 7 samples) Pipe-based Context Switching 368541.3 lps (10.0 s, 7 samples) Process Creation 5577.5 lps (30.0 s, 2 samples) Shell Scripts (1 concurrent) 3881.2 lpm (60.0 s, 2 samples) Shell Scripts (8 concurrent) 2650.3 lpm (60.0 s, 2 samples) System Call Overhead 2509799.8 lps (10.0 s, 7 samples) System Benchmarks Index Values BASELINE RESULT INDEX Dhrystone 2 using register variables 116700.0 35232485.6 3019.1 Double-Precision Whetstone 55.0 3877.4 705.0 Execl Throughput 43.0 1939.8 451.1 File Copy 1024 bufsize 2000 maxblocks 3960.0 966506.7 2440.7 File Copy 256 bufsize 500 maxblocks 1655.0 266621.2 1611.0 File Copy 4096 bufsize 8000 maxblocks 5800.0 2444019.5 4213.8 Pipe Throughput 12440.0 1590900.5 1278.9 Pipe-based Context Switching 4000.0 368541.3 921.4 Process Creation 126.0 5577.5 442.7 Shell Scripts (1 concurrent) 42.4 3881.2 915.4 Shell Scripts (8 concurrent) 6.0 2650.3 4417.2 System Call Overhead 15000.0 2509799.8 1673.2 ======== System Benchmarks Index Score 1398.8 ------------------------------------------------------------------------ Benchmark Run: Fri Sep 14 2012 10:49:17 - 11:17:26 4 CPUs in system; running 4 parallel copies of tests Dhrystone 2 using register variables 133445381.8 lps (10.0 s, 7 samples) Double-Precision Whetstone 14620.1 MWIPS (9.9 s, 7 samples) Execl Throughput 17582.8 lps (30.0 s, 2 samples) File Copy 1024 bufsize 2000 maxblocks 1126655.3 KBps (30.0 s, 2 samples) File Copy 256 bufsize 500 maxblocks 301996.7 KBps (30.0 s, 2 samples) File Copy 4096 bufsize 8000 maxblocks 3221205.1 KBps (30.0 s, 2 samples) Pipe Throughput 6244159.7 lps (10.0 s, 7 samples) Pipe-based Context Switching 1508547.2 lps (10.0 s, 7 samples) Process Creation 57311.4 lps (30.0 s, 2 samples) Shell Scripts (1 concurrent) 21936.7 lpm (60.0 s, 2 samples) Shell Scripts (8 concurrent) 2931.2 lpm (60.0 s, 2 samples) System Call Overhead 7935430.4 lps (10.0 s, 7 samples) System Benchmarks Index Values BASELINE RESULT INDEX Dhrystone 2 using register variables 116700.0 133445381.8 11434.9 Double-Precision Whetstone 55.0 14620.1 2658.2 Execl Throughput 43.0 17582.8 4089.0 File Copy 1024 bufsize 2000 maxblocks 3960.0 1126655.3 2845.1 File Copy 256 bufsize 500 maxblocks 1655.0 301996.7 1824.8 File Copy 4096 bufsize 8000 maxblocks 5800.0 3221205.1 5553.8 Pipe Throughput 12440.0 6244159.7 5019.4 Pipe-based Context Switching 4000.0 1508547.2 3771.4 Process Creation 126.0 57311.4 4548.5 Shell Scripts (1 concurrent) 42.4 21936.7 5173.8 Shell Scripts (8 concurrent) 6.0 2931.2 4885.4 System Call Overhead 15000.0 7935430.4 5290.3 ======== System Benchmarks Index Score 4311.5 -- View this message in context: http://xen.1045712.n5.nabble.com/Performance-of-PVM-and-HVM-tp5711309.html Sent from the Xen - User mailing list archive at Nabble.com. _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Mon Sep 17 03:13:27 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Mon, 17 Sep 2012 03:13:27 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TDRlC-0001ln-AQ; Mon, 17 Sep 2012 03:12:34 +0000 Received: from mail27.messagelabs.com ([193.109.254.147]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TDRl9-0001ld-W0 for xen-users@lists.xensource.com; Mon, 17 Sep 2012 03:12:32 +0000 X-Env-Sender: pingh.cd@gmail.com X-Msg-Ref: server-2.tower-27.messagelabs.com!1347851543!11226400!1 X-Originating-IP: [216.139.236.26] X-SpamReason: No, hits=0.5 required=7.0 tests=BODY_RANDOM_LONG, ML_RADAR_SPEW_LINKS_14,spamassassin: X-StarScan-Received: X-StarScan-Version: 6.6.1.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 22022 invoked from network); 17 Sep 2012 03:12:24 -0000 Received: from sam.nabble.com (HELO sam.nabble.com) (216.139.236.26) by server-2.tower-27.messagelabs.com with AES256-SHA encrypted SMTP; 17 Sep 2012 03:12:24 -0000 Received: from [192.168.236.26] (helo=sam.nabble.com) by sam.nabble.com with esmtp (Exim 4.72) (envelope-from ) id 1TDRl0-00070p-VQ for xen-users@lists.xensource.com; Sun, 16 Sep 2012 20:12:23 -0700 Date: Sun, 16 Sep 2012 20:12:22 -0700 (PDT) From: Robin hp To: xen-users@lists.xensource.com Message-ID: <1347851542961-5711309.post@n5.nabble.com> MIME-Version: 1.0 Subject: [Xen-users] Performance of PVM and HVM X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org Recently, I met a strange issue about vm's performance. I downloaded Jeremy's branch of xen/next-2.6.32 (version:2.6.32.57)for dom0, and compiled xen-4.1.3 source code for xend service, then I used Unixbench to test the performance of native, dom0, and domU(HVM and PVM). By the way, I set 4 vcpus and 2048M memory for each VM. And I got the following results: It seems that dom0's performance is so bad from native, and PVM so on. But HVM's performance is better than my expected, it's so close to native. It's weird to me, or it's just a normal thing? Is any one else experiencing this? Any reply or suggests will be appreciated. ========native:(2.6.32.57 without xen)============ System: localhost.localdomain: GNU/Linux OS: GNU/Linux -- 2.6.32.57 -- #1 SMP Thu Sep 6 10:42:38 CST 2012 Machine: x86_64 (x86_64) Language: en_US.utf8 (charmap="UTF-8", collate="UTF-8") CPU 0: Intel(R) Core(TM) i5-2400 CPU @ 3.10GHz (6185.3 bogomips) Hyper-Threading, x86-64, MMX, Physical Address Ext, SYSENTER/SYSEXIT, SYSCALL/SYSRET, Intel virtualization CPU 1: Intel(R) Core(TM) i5-2400 CPU @ 3.10GHz (6185.9 bogomips) Hyper-Threading, x86-64, MMX, Physical Address Ext, SYSENTER/SYSEXIT, SYSCALL/SYSRET, Intel virtualization CPU 2: Intel(R) Core(TM) i5-2400 CPU @ 3.10GHz (6185.9 bogomips) Hyper-Threading, x86-64, MMX, Physical Address Ext, SYSENTER/SYSEXIT, SYSCALL/SYSRET, Intel virtualization CPU 3: Intel(R) Core(TM) i5-2400 CPU @ 3.10GHz (6185.9 bogomips) Hyper-Threading, x86-64, MMX, Physical Address Ext, SYSENTER/SYSEXIT, SYSCALL/SYSRET, Intel virtualization 11:01:15 up 9 min, 2 users, load average: 0.15, 0.41, 0.26; runlevel 5 Double-Precision Whetstone 4023.5 MWIPS (9.9 s, 7 samples) Execl Throughput 2384.2 lps (29.7 s, 2 samples) File Copy 1024 bufsize 2000 maxblocks 1134757.4 KBps (30.0 s, 2 samples) File Copy 256 bufsize 500 maxblocks 312913.0 KBps (30.0 s, 2 samples) File Copy 4096 bufsize 8000 maxblocks 2731953.1 KBps (30.0 s, 2 samples) Pipe Throughput 2043709.3 lps (10.0 s, 7 samples) Pipe-based Context Switching 105547.0 lps (10.0 s, 7 samples) Process Creation 10013.4 lps (30.0 s, 2 samples) Shell Scripts (1 concurrent) 4158.8 lpm (60.0 s, 2 samples) Shell Scripts (8 concurrent) 2961.2 lpm (60.0 s, 2 samples) System Call Overhead 4431920.0 lps (10.0 s, 7 samples) System Benchmarks Index Values BASELINE RESULT INDEX Dhrystone 2 using register variables 116700.0 37435723.9 3207.9 Double-Precision Whetstone 55.0 4023.5 731.5 Execl Throughput 43.0 2384.2 554.5 File Copy 1024 bufsize 2000 maxblocks 3960.0 1134757.4 2865.5 File Copy 256 bufsize 500 maxblocks 1655.0 312913.0 1890.7 File Copy 4096 bufsize 8000 maxblocks 5800.0 2731953.1 4710.3 Pipe Throughput 12440.0 2043709.3 1642.9 Pipe-based Context Switching 4000.0 105547.0 263.9 Process Creation 126.0 10013.4 794.7 Shell Scripts (1 concurrent) 42.4 4158.8 980.9 Shell Scripts (8 concurrent) 6.0 2961.2 4935.4 System Call Overhead 15000.0 4431920.0 2954.6 ======== System Benchmarks Index Score 1529.3 ------------------------------------------------------------------------ Benchmark Run: Thu Sep 06 2012 11:30:07 - 11:59:09 4 CPUs in system; running 4 parallel copies of tests Dhrystone 2 using register variables 141361626.6 lps (10.0 s, 7 samples) Double-Precision Whetstone 15160.0 MWIPS (9.9 s, 7 samples) Execl Throughput 20000.9 lps (29.6 s, 2 samples) File Copy 1024 bufsize 2000 maxblocks 1127449.6 KBps (30.0 s, 2 samples) File Copy 256 bufsize 500 maxblocks 299709.9 KBps (30.0 s, 2 samples) File Copy 4096 bufsize 8000 maxblocks 3197973.3 KBps (30.0 s, 2 samples) Pipe Throughput 7732066.4 lps (10.0 s, 7 samples) Pipe-based Context Switching 1801378.7 lps (10.0 s, 7 samples) Process Creation 75567.5 lps (30.0 s, 2 samples) Shell Scripts (1 concurrent) 25427.3 lpm (60.0 s, 2 samples) Shell Scripts (8 concurrent) 3397.8 lpm (60.0 s, 2 samples) System Call Overhead 12278676.0 lps (10.0 s, 7 samples) System Benchmarks Index Values BASELINE RESULT INDEX Dhrystone 2 using register variables 116700.0 141361626.6 12113.2 Double-Precision Whetstone 55.0 15160.0 2756.4 Execl Throughput 43.0 20000.9 4651.4 File Copy 1024 bufsize 2000 maxblocks 3960.0 1127449.6 2847.1 File Copy 256 bufsize 500 maxblocks 1655.0 299709.9 1810.9 File Copy 4096 bufsize 8000 maxblocks 5800.0 3197973.3 5513.7 Pipe Throughput 12440.0 7732066.4 6215.5 Pipe-based Context Switching 4000.0 1801378.7 4503.4 Process Creation 126.0 75567.5 5997.4 Shell Scripts (1 concurrent) 42.4 25427.3 5997.0 Shell Scripts (8 concurrent) 6.0 3397.8 5663.1 System Call Overhead 15000.0 12278676.0 8185.8 ======== System Benchmarks Index Score 4929.8 ========native:(2.6.32.57 with xen)============ System: localhost.localdomain: GNU/Linux OS: GNU/Linux -- 2.6.32.57 -- #1 SMP Wed Sep 5 16:17:40 CST 2012 Machine: x86_64 (x86_64) Language: en_US.utf8 (charmap="UTF-8", collate="UTF-8") CPU 0: Intel(R) Core(TM) i5-2400 CPU @ 3.10GHz (6185.9 bogomips) Hyper-Threading, x86-64, MMX, Physical Address Ext, SYSENTER/SYSEXIT, SYSCALL/SYSRET CPU 1: Intel(R) Core(TM) i5-2400 CPU @ 3.10GHz (6185.9 bogomips) Hyper-Threading, x86-64, MMX, Physical Address Ext, SYSENTER/SYSEXIT, SYSCALL/SYSRET CPU 2: Intel(R) Core(TM) i5-2400 CPU @ 3.10GHz (6185.9 bogomips) Hyper-Threading, x86-64, MMX, Physical Address Ext, SYSENTER/SYSEXIT, SYSCALL/SYSRET CPU 3: Intel(R) Core(TM) i5-2400 CPU @ 3.10GHz (6185.9 bogomips) Hyper-Threading, x86-64, MMX, Physical Address Ext, SYSENTER/SYSEXIT, SYSCALL/SYSRET 16:39:07 up 5 min, 2 users, load average: 0.41, 0.14, 0.05; runlevel 5 Double-Precision Whetstone 4014.3 MWIPS (10.0 s, 7 samples) Execl Throughput 1539.9 lps (29.7 s, 2 samples) File Copy 1024 bufsize 2000 maxblocks 230816.4 KBps (30.0 s, 2 samples) File Copy 256 bufsize 500 maxblocks 59384.4 KBps (30.0 s, 2 samples) File Copy 4096 bufsize 8000 maxblocks 799672.5 KBps (30.0 s, 2 samples) Pipe Throughput 464331.1 lps (10.0 s, 7 samples) Pipe-based Context Switching 84464.6 lps (10.0 s, 7 samples) Process Creation 1416.4 lps (30.0 s, 2 samples) Shell Scripts (1 concurrent) 1777.9 lpm (60.0 s, 2 samples) Shell Scripts (8 concurrent) 1077.6 lpm (60.1 s, 2 samples) System Call Overhead 588951.1 lps (10.0 s, 7 samples) System Benchmarks Index Values BASELINE RESULT INDEX Dhrystone 2 using register variables 116700.0 37551405.9 3217.8 Double-Precision Whetstone 55.0 4014.3 729.9 Execl Throughput 43.0 1539.9 358.1 File Copy 1024 bufsize 2000 maxblocks 3960.0 230816.4 582.9 File Copy 256 bufsize 500 maxblocks 1655.0 59384.4 358.8 File Copy 4096 bufsize 8000 maxblocks 5800.0 799672.5 1378.7 Pipe Throughput 12440.0 464331.1 373.3 Pipe-based Context Switching 4000.0 84464.6 211.2 Process Creation 126.0 1416.4 112.4 Shell Scripts (1 concurrent) 42.4 1777.9 419.3 Shell Scripts (8 concurrent) 6.0 1077.6 1796.0 System Call Overhead 15000.0 588951.1 392.6 ======== System Benchmarks Index Score 541.5 ------------------------------------------------------------------------ Benchmark Run: Wed Sep 05 2012 17:08:17 - 17:37:42 4 CPUs in system; running 4 parallel copies of tests Dhrystone 2 using register variables 141651867.8 lps (10.0 s, 7 samples) Double-Precision Whetstone 15164.7 MWIPS (9.9 s, 7 samples) Execl Throughput 4973.0 lps (29.5 s, 2 samples) File Copy 1024 bufsize 2000 maxblocks 314355.0 KBps (30.0 s, 2 samples) File Copy 256 bufsize 500 maxblocks 80269.7 KBps (30.0 s, 2 samples) File Copy 4096 bufsize 8000 maxblocks 1157706.6 KBps (30.0 s, 2 samples) Pipe Throughput 1733674.4 lps (10.0 s, 7 samples) Pipe-based Context Switching 336552.6 lps (10.0 s, 7 samples) Process Creation 10207.0 lps (30.0 s, 2 samples) Shell Scripts (1 concurrent) 8880.3 lpm (60.0 s, 2 samples) Shell Scripts (8 concurrent) 1197.1 lpm (60.1 s, 2 samples) System Call Overhead 2126022.5 lps (10.0 s, 7 samples) System Benchmarks Index Values BASELINE RESULT INDEX Dhrystone 2 using register variables 116700.0 141651867.8 12138.1 Double-Precision Whetstone 55.0 15164.7 2757.2 Execl Throughput 43.0 4973.0 1156.5 File Copy 1024 bufsize 2000 maxblocks 3960.0 314355.0 793.8 File Copy 256 bufsize 500 maxblocks 1655.0 80269.7 485.0 File Copy 4096 bufsize 8000 maxblocks 5800.0 1157706.6 1996.0 Pipe Throughput 12440.0 1733674.4 1393.6 Pipe-based Context Switching 4000.0 336552.6 841.4 Process Creation 126.0 10207.0 810.1 Shell Scripts (1 concurrent) 42.4 8880.3 2094.4 Shell Scripts (8 concurrent) 6.0 1197.1 1995.2 System Call Overhead 15000.0 2126022.5 1417.3 ======== System Benchmarks Index Score 1532.1 ========native:(PVM rhel6.1)============ System: xenpv1.myxen.com: GNU/Linux OS: GNU/Linux -- 2.6.32-131.0.15.el6.x86_64 -- #1 SMP Tue May 10 15:42:40 EDT 2011 Machine: x86_64 (x86_64) Language: en_US.utf8 (charmap="UTF-8", collate="UTF-8") CPU 0: Intel(R) Core(TM) i5-2400 CPU @ 3.10GHz (6186.4 bogomips) Hyper-Threading, x86-64, MMX, Physical Address Ext, SYSCALL/SYSRET CPU 1: Intel(R) Core(TM) i5-2400 CPU @ 3.10GHz (6186.4 bogomips) Hyper-Threading, x86-64, MMX, Physical Address Ext, SYSCALL/SYSRET CPU 2: Intel(R) Core(TM) i5-2400 CPU @ 3.10GHz (6186.4 bogomips) Hyper-Threading, x86-64, MMX, Physical Address Ext, SYSCALL/SYSRET CPU 3: Intel(R) Core(TM) i5-2400 CPU @ 3.10GHz (6186.4 bogomips) Hyper-Threading, x86-64, MMX, Physical Address Ext, SYSCALL/SYSRET 09:21:10 up 1 min, 1 user, load average: 0.09, 0.03, 0.00; runlevel 3 ------------------------------------------------------------------------ Benchmark Run: Fri Sep 14 2012 09:21:10 - 09:49:19 4 CPUs in system; running 1 parallel copy of tests Dhrystone 2 using register variables 36560766.3 lps (10.0 s, 7 samples) Double-Precision Whetstone 3962.1 MWIPS (9.9 s, 7 samples) Execl Throughput 798.0 lps (30.0 s, 2 samples) File Copy 1024 bufsize 2000 maxblocks 307212.1 KBps (30.0 s, 2 samples) File Copy 256 bufsize 500 maxblocks 77826.9 KBps (30.0 s, 2 samples) File Copy 4096 bufsize 8000 maxblocks 989297.2 KBps (30.0 s, 2 samples) Pipe Throughput 415705.7 lps (10.0 s, 7 samples) Pipe-based Context Switching 82646.7 lps (10.0 s, 7 samples) Process Creation 1643.2 lps (30.0 s, 2 samples) Shell Scripts (1 concurrent) 2111.5 lpm (60.0 s, 2 samples) Shell Scripts (8 concurrent) 1222.8 lpm (60.1 s, 2 samples) System Call Overhead 442797.7 lps (10.0 s, 7 samples) System Benchmarks Index Values BASELINE RESULT INDEX Dhrystone 2 using register variables 116700.0 36560766.3 3132.9 Double-Precision Whetstone 55.0 3962.1 720.4 Execl Throughput 43.0 798.0 185.6 File Copy 1024 bufsize 2000 maxblocks 3960.0 307212.1 775.8 File Copy 256 bufsize 500 maxblocks 1655.0 77826.9 470.3 File Copy 4096 bufsize 8000 maxblocks 5800.0 989297.2 1705.7 Pipe Throughput 12440.0 415705.7 334.2 Pipe-based Context Switching 4000.0 82646.7 206.6 Process Creation 126.0 1643.2 130.4 Shell Scripts (1 concurrent) 42.4 2111.5 498.0 Shell Scripts (8 concurrent) 6.0 1222.8 2038.0 System Call Overhead 15000.0 442797.7 295.2 ======== System Benchmarks Index Score 546.1 ------------------------------------------------------------------------ Benchmark Run: Fri Sep 14 2012 09:49:19 - 10:17:31 4 CPUs in system; running 4 parallel copies of tests Dhrystone 2 using register variables 139304316.2 lps (10.0 s, 7 samples) Double-Precision Whetstone 14960.7 MWIPS (9.9 s, 7 samples) Execl Throughput 5607.6 lps (30.0 s, 2 samples) File Copy 1024 bufsize 2000 maxblocks 498246.2 KBps (30.0 s, 2 samples) File Copy 256 bufsize 500 maxblocks 121580.0 KBps (30.0 s, 2 samples) File Copy 4096 bufsize 8000 maxblocks 1649657.6 KBps (30.1 s, 2 samples) Pipe Throughput 1574427.7 lps (10.0 s, 7 samples) Pipe-based Context Switching 327122.9 lps (10.0 s, 7 samples) Process Creation 10641.0 lps (30.0 s, 2 samples) Shell Scripts (1 concurrent) 9917.6 lpm (60.0 s, 2 samples) Shell Scripts (8 concurrent) 1351.8 lpm (60.1 s, 2 samples) System Call Overhead 1605775.2 lps (10.0 s, 7 samples) System Benchmarks Index Values BASELINE RESULT INDEX Dhrystone 2 using register variables 116700.0 139304316.2 11937.0 Double-Precision Whetstone 55.0 14960.7 2720.1 Execl Throughput 43.0 5607.6 1304.1 File Copy 1024 bufsize 2000 maxblocks 3960.0 498246.2 1258.2 File Copy 256 bufsize 500 maxblocks 1655.0 121580.0 734.6 File Copy 4096 bufsize 8000 maxblocks 5800.0 1649657.6 2844.2 Pipe Throughput 12440.0 1574427.7 1265.6 Pipe-based Context Switching 4000.0 327122.9 817.8 Process Creation 126.0 10641.0 844.5 Shell Scripts (1 concurrent) 42.4 9917.6 2339.0 Shell Scripts (8 concurrent) 6.0 1351.8 2253.0 System Call Overhead 15000.0 1605775.2 1070.5 ======== System Benchmarks Index Score 1691.6 ========native:(HVM rhel6.1)============ System: hvmserver0.myxen.com: GNU/Linux OS: GNU/Linux -- 2.6.32-131.0.15.el6.x86_64 -- #1 SMP Tue May 10 15:42:40 EDT 2011 Machine: x86_64 (x86_64) Language: en_US.utf8 (charmap="UTF-8", collate="UTF-8") CPU 0: Intel(R) Core(TM) i5-2400 CPU @ 3.10GHz (6186.4 bogomips) Hyper-Threading, x86-64, MMX, Physical Address Ext, SYSCALL/SYSRET CPU 1: Intel(R) Core(TM) i5-2400 CPU @ 3.10GHz (6185.2 bogomips) Hyper-Threading, x86-64, MMX, Physical Address Ext, SYSCALL/SYSRET CPU 2: Intel(R) Core(TM) i5-2400 CPU @ 3.10GHz (6185.4 bogomips) Hyper-Threading, x86-64, MMX, Physical Address Ext, SYSCALL/SYSRET CPU 3: Intel(R) Core(TM) i5-2400 CPU @ 3.10GHz (6185.4 bogomips) Hyper-Threading, x86-64, MMX, Physical Address Ext, SYSCALL/SYSRET 10:21:14 up 2 min, 1 user, load average: 0.13, 0.12, 0.05; runlevel 3 ------------------------------------------------------------------------ Benchmark Run: Fri Sep 14 2012 10:21:14 - 10:49:17 4 CPUs in system; running 1 parallel copy of tests Dhrystone 2 using register variables 35232485.6 lps (10.0 s, 7 samples) Double-Precision Whetstone 3877.4 MWIPS (9.7 s, 7 samples) Execl Throughput 1939.8 lps (30.0 s, 2 samples) File Copy 1024 bufsize 2000 maxblocks 966506.7 KBps (30.0 s, 2 samples) File Copy 256 bufsize 500 maxblocks 266621.2 KBps (30.0 s, 2 samples) File Copy 4096 bufsize 8000 maxblocks 2444019.5 KBps (30.0 s, 2 samples) Pipe Throughput 1590900.5 lps (10.0 s, 7 samples) Pipe-based Context Switching 368541.3 lps (10.0 s, 7 samples) Process Creation 5577.5 lps (30.0 s, 2 samples) Shell Scripts (1 concurrent) 3881.2 lpm (60.0 s, 2 samples) Shell Scripts (8 concurrent) 2650.3 lpm (60.0 s, 2 samples) System Call Overhead 2509799.8 lps (10.0 s, 7 samples) System Benchmarks Index Values BASELINE RESULT INDEX Dhrystone 2 using register variables 116700.0 35232485.6 3019.1 Double-Precision Whetstone 55.0 3877.4 705.0 Execl Throughput 43.0 1939.8 451.1 File Copy 1024 bufsize 2000 maxblocks 3960.0 966506.7 2440.7 File Copy 256 bufsize 500 maxblocks 1655.0 266621.2 1611.0 File Copy 4096 bufsize 8000 maxblocks 5800.0 2444019.5 4213.8 Pipe Throughput 12440.0 1590900.5 1278.9 Pipe-based Context Switching 4000.0 368541.3 921.4 Process Creation 126.0 5577.5 442.7 Shell Scripts (1 concurrent) 42.4 3881.2 915.4 Shell Scripts (8 concurrent) 6.0 2650.3 4417.2 System Call Overhead 15000.0 2509799.8 1673.2 ======== System Benchmarks Index Score 1398.8 ------------------------------------------------------------------------ Benchmark Run: Fri Sep 14 2012 10:49:17 - 11:17:26 4 CPUs in system; running 4 parallel copies of tests Dhrystone 2 using register variables 133445381.8 lps (10.0 s, 7 samples) Double-Precision Whetstone 14620.1 MWIPS (9.9 s, 7 samples) Execl Throughput 17582.8 lps (30.0 s, 2 samples) File Copy 1024 bufsize 2000 maxblocks 1126655.3 KBps (30.0 s, 2 samples) File Copy 256 bufsize 500 maxblocks 301996.7 KBps (30.0 s, 2 samples) File Copy 4096 bufsize 8000 maxblocks 3221205.1 KBps (30.0 s, 2 samples) Pipe Throughput 6244159.7 lps (10.0 s, 7 samples) Pipe-based Context Switching 1508547.2 lps (10.0 s, 7 samples) Process Creation 57311.4 lps (30.0 s, 2 samples) Shell Scripts (1 concurrent) 21936.7 lpm (60.0 s, 2 samples) Shell Scripts (8 concurrent) 2931.2 lpm (60.0 s, 2 samples) System Call Overhead 7935430.4 lps (10.0 s, 7 samples) System Benchmarks Index Values BASELINE RESULT INDEX Dhrystone 2 using register variables 116700.0 133445381.8 11434.9 Double-Precision Whetstone 55.0 14620.1 2658.2 Execl Throughput 43.0 17582.8 4089.0 File Copy 1024 bufsize 2000 maxblocks 3960.0 1126655.3 2845.1 File Copy 256 bufsize 500 maxblocks 1655.0 301996.7 1824.8 File Copy 4096 bufsize 8000 maxblocks 5800.0 3221205.1 5553.8 Pipe Throughput 12440.0 6244159.7 5019.4 Pipe-based Context Switching 4000.0 1508547.2 3771.4 Process Creation 126.0 57311.4 4548.5 Shell Scripts (1 concurrent) 42.4 21936.7 5173.8 Shell Scripts (8 concurrent) 6.0 2931.2 4885.4 System Call Overhead 15000.0 7935430.4 5290.3 ======== System Benchmarks Index Score 4311.5 -- View this message in context: http://xen.1045712.n5.nabble.com/Performance-of-PVM-and-HVM-tp5711309.html Sent from the Xen - User mailing list archive at Nabble.com. _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Mon Sep 17 04:44:51 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Mon, 17 Sep 2012 04:44:51 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TDTBU-0002xd-84; Mon, 17 Sep 2012 04:43:48 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TDTBS-0002xV-21 for xen-users@lists.xensource.com; Mon, 17 Sep 2012 04:43:46 +0000 Received: from [85.158.138.51:37749] by server-9.bemta-3.messagelabs.com id F0/B6-15390-18AA6505; Mon, 17 Sep 2012 04:43:45 +0000 X-Env-Sender: fajar@fajar.net X-Msg-Ref: server-7.tower-174.messagelabs.com!1347857023!21922067!1 X-Originating-IP: [209.85.214.171] X-SpamReason: No, hits=0.3 required=7.0 tests=RCVD_BY_IP X-StarScan-Received: X-StarScan-Version: 6.6.1.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 12385 invoked from network); 17 Sep 2012 04:43:44 -0000 Received: from mail-ob0-f171.google.com (HELO mail-ob0-f171.google.com) (209.85.214.171) by server-7.tower-174.messagelabs.com with RC4-SHA encrypted SMTP; 17 Sep 2012 04:43:44 -0000 Received: by obqv19 with SMTP id v19so11471700obq.30 for ; Sun, 16 Sep 2012 21:43:42 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:x-gm-message-state; bh=Jom7LSRTuvfSXH9+OhbRWFhnjyBj834XoLH2AEn3kvU=; b=d29P2pZ4XbM1u1BvAzD4/+AYNfP6Q0D4Wq27W2Hkm2HoGOpDTeh3OhCIVbQeclZ2G6 9o852UCDQwA51MSyaVz1AdXW/lq8q0bDLRdmBh8ClqBxtlo4+tS/pBwkQ0WMLFlWqAyu xZ/OquSqfV4qim/otS29ZuK465Ua3GsHO1sRIOEpqXD/ZIVxLzN3dwKE7ymzrvcKZgOR eHh+gHD+ydbfEBwwyRwpWHiD6dOhvtivbX4cHNVrWZQtHScTYkuNfGESb5xZhiVKMjSv Hmnzua1aALSNOtM3uXhtTvKtEcr3grzzEAkfi11RzZnGsdNMTm50Oru5TMRolLOiWNRj 41Rw== MIME-Version: 1.0 Received: by 10.182.202.39 with SMTP id kf7mr10576042obc.37.1347857022858; Sun, 16 Sep 2012 21:43:42 -0700 (PDT) Received: by 10.60.6.230 with HTTP; Sun, 16 Sep 2012 21:43:42 -0700 (PDT) In-Reply-To: <1347851542961-5711309.post@n5.nabble.com> References: <1347851542961-5711309.post@n5.nabble.com> Date: Mon, 17 Sep 2012 11:43:42 +0700 Message-ID: From: "Fajar A. Nugraha" To: Robin hp X-Gm-Message-State: ALoCoQmh5NnOC6mo5Y3/Hg6A3KxDpQHGDQceY2ogcV+cJDmDXs1GvM7LcjVUXdS7hACtkjFk3yIK Cc: xen-users@lists.xensource.com Subject: Re: [Xen-users] Performance of PVM and HVM X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org On Mon, Sep 17, 2012 at 10:12 AM, Robin hp wrote: > Recently, I met a strange issue about vm's performance. > > I downloaded Jeremy's branch of xen/next-2.6.32 (version:2.6.32.57)for dom0, > and compiled xen-4.1.3 source code for xend service, then I used Unixbench > to test the performance of native, dom0, and domU(HVM and PVM). By the way, > I set 4 vcpus and 2048M memory for each VM. And I got the following results: > > It seems that dom0's performance is so bad from native, and PVM so on. How do you test native? For "fair" comparison, you need to make sure that native has the same cpu and memory as dom0/domU tested. For cpu, you can disable some of them using /sys/devices/system/cpu/cpu1/online, and for memory you might need to use "mem=2G" kernel boot parameter. > But > HVM's performance is better than my expected, it's so close to native. Do you file:/ ? If yes, that would be the effect of dom0 cache. Try using block devices with phy:/ Others might comment more about this. -- Fajar _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Mon Sep 17 04:44:51 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Mon, 17 Sep 2012 04:44:51 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TDTBU-0002xd-84; Mon, 17 Sep 2012 04:43:48 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TDTBS-0002xV-21 for xen-users@lists.xensource.com; Mon, 17 Sep 2012 04:43:46 +0000 Received: from [85.158.138.51:37749] by server-9.bemta-3.messagelabs.com id F0/B6-15390-18AA6505; Mon, 17 Sep 2012 04:43:45 +0000 X-Env-Sender: fajar@fajar.net X-Msg-Ref: server-7.tower-174.messagelabs.com!1347857023!21922067!1 X-Originating-IP: [209.85.214.171] X-SpamReason: No, hits=0.3 required=7.0 tests=RCVD_BY_IP X-StarScan-Received: X-StarScan-Version: 6.6.1.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 12385 invoked from network); 17 Sep 2012 04:43:44 -0000 Received: from mail-ob0-f171.google.com (HELO mail-ob0-f171.google.com) (209.85.214.171) by server-7.tower-174.messagelabs.com with RC4-SHA encrypted SMTP; 17 Sep 2012 04:43:44 -0000 Received: by obqv19 with SMTP id v19so11471700obq.30 for ; Sun, 16 Sep 2012 21:43:42 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:x-gm-message-state; bh=Jom7LSRTuvfSXH9+OhbRWFhnjyBj834XoLH2AEn3kvU=; b=d29P2pZ4XbM1u1BvAzD4/+AYNfP6Q0D4Wq27W2Hkm2HoGOpDTeh3OhCIVbQeclZ2G6 9o852UCDQwA51MSyaVz1AdXW/lq8q0bDLRdmBh8ClqBxtlo4+tS/pBwkQ0WMLFlWqAyu xZ/OquSqfV4qim/otS29ZuK465Ua3GsHO1sRIOEpqXD/ZIVxLzN3dwKE7ymzrvcKZgOR eHh+gHD+ydbfEBwwyRwpWHiD6dOhvtivbX4cHNVrWZQtHScTYkuNfGESb5xZhiVKMjSv Hmnzua1aALSNOtM3uXhtTvKtEcr3grzzEAkfi11RzZnGsdNMTm50Oru5TMRolLOiWNRj 41Rw== MIME-Version: 1.0 Received: by 10.182.202.39 with SMTP id kf7mr10576042obc.37.1347857022858; Sun, 16 Sep 2012 21:43:42 -0700 (PDT) Received: by 10.60.6.230 with HTTP; Sun, 16 Sep 2012 21:43:42 -0700 (PDT) In-Reply-To: <1347851542961-5711309.post@n5.nabble.com> References: <1347851542961-5711309.post@n5.nabble.com> Date: Mon, 17 Sep 2012 11:43:42 +0700 Message-ID: From: "Fajar A. Nugraha" To: Robin hp X-Gm-Message-State: ALoCoQmh5NnOC6mo5Y3/Hg6A3KxDpQHGDQceY2ogcV+cJDmDXs1GvM7LcjVUXdS7hACtkjFk3yIK Cc: xen-users@lists.xensource.com Subject: Re: [Xen-users] Performance of PVM and HVM X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org On Mon, Sep 17, 2012 at 10:12 AM, Robin hp wrote: > Recently, I met a strange issue about vm's performance. > > I downloaded Jeremy's branch of xen/next-2.6.32 (version:2.6.32.57)for dom0, > and compiled xen-4.1.3 source code for xend service, then I used Unixbench > to test the performance of native, dom0, and domU(HVM and PVM). By the way, > I set 4 vcpus and 2048M memory for each VM. And I got the following results: > > It seems that dom0's performance is so bad from native, and PVM so on. How do you test native? For "fair" comparison, you need to make sure that native has the same cpu and memory as dom0/domU tested. For cpu, you can disable some of them using /sys/devices/system/cpu/cpu1/online, and for memory you might need to use "mem=2G" kernel boot parameter. > But > HVM's performance is better than my expected, it's so close to native. Do you file:/ ? If yes, that would be the effect of dom0 cache. Try using block devices with phy:/ Others might comment more about this. -- Fajar _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Mon Sep 17 05:59:43 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Mon, 17 Sep 2012 05:59:43 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TDULu-0003fR-8D; Mon, 17 Sep 2012 05:58:38 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TDULt-0003fM-GN for xen-users@lists.xensource.com; Mon, 17 Sep 2012 05:58:37 +0000 Received: from [85.158.139.83:50805] by server-5.bemta-5.messagelabs.com id 3E/1D-30514-C0CB6505; Mon, 17 Sep 2012 05:58:36 +0000 X-Env-Sender: pingh.cd@gmail.com X-Msg-Ref: server-6.tower-182.messagelabs.com!1347861512!26898024!1 X-Originating-IP: [216.139.236.26] X-SpamReason: No, hits=0.0 required=7.0 tests=ML_RADAR_SPEW_LINKS_14, spamassassin: X-StarScan-Received: X-StarScan-Version: 6.6.1.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 16849 invoked from network); 17 Sep 2012 05:58:33 -0000 Received: from sam.nabble.com (HELO sam.nabble.com) (216.139.236.26) by server-6.tower-182.messagelabs.com with AES256-SHA encrypted SMTP; 17 Sep 2012 05:58:33 -0000 Received: from [192.168.236.26] (helo=sam.nabble.com) by sam.nabble.com with esmtp (Exim 4.72) (envelope-from ) id 1TDULo-0003fS-6w for xen-users@lists.xensource.com; Sun, 16 Sep 2012 22:58:32 -0700 Date: Sun, 16 Sep 2012 22:58:32 -0700 (PDT) From: Robin hp To: xen-users@lists.xensource.com Message-ID: <1347861512207-5711311.post@n5.nabble.com> In-Reply-To: References: <1347851542961-5711309.post@n5.nabble.com> MIME-Version: 1.0 Subject: Re: [Xen-users] Performance of PVM and HVM X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org >How do you test native? >For "fair" comparison, you need to make sure that native has the same >cpu and memory as dom0/domU tested. For cpu, you can disable some of >them using /sys/devices/system/cpu/cpu1/online, and for memory you >might need to use "mem=2G" kernel boot parameter. >Thanks for Fajar's reply. Yes, All native,pvm and hvm have the same configurations. >Do you file:/ ? If yes, that would be the effect of dom0 cache. Try >using block devices with phy:/ >Others might comment more about this. I didn't use phy:/ for hvm, but I used file:/ for pvm, and the results were not different. For more testing, I used dd (bs=1024M count=8)to test writing speed for native, pvm and hvm. Following is the results: (2G RAM, 4cpu 3.1G) Native 159MB/s Dom0 137MB/s pvm(Phy:/) 52MB/s pvm(file:/) 684MB/s (As you said, I guess that's because of the effect of dom0 cache) hvm(file:/) 840MB/s What wired me is that most docs about xen told me pvm's performance is better, but the results of my testing told difference. -- View this message in context: http://xen.1045712.n5.nabble.com/Performance-of-PVM-and-HVM-tp5711309p5711311.html Sent from the Xen - User mailing list archive at Nabble.com. _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Mon Sep 17 05:59:43 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Mon, 17 Sep 2012 05:59:43 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TDULu-0003fR-8D; Mon, 17 Sep 2012 05:58:38 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TDULt-0003fM-GN for xen-users@lists.xensource.com; Mon, 17 Sep 2012 05:58:37 +0000 Received: from [85.158.139.83:50805] by server-5.bemta-5.messagelabs.com id 3E/1D-30514-C0CB6505; Mon, 17 Sep 2012 05:58:36 +0000 X-Env-Sender: pingh.cd@gmail.com X-Msg-Ref: server-6.tower-182.messagelabs.com!1347861512!26898024!1 X-Originating-IP: [216.139.236.26] X-SpamReason: No, hits=0.0 required=7.0 tests=ML_RADAR_SPEW_LINKS_14, spamassassin: X-StarScan-Received: X-StarScan-Version: 6.6.1.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 16849 invoked from network); 17 Sep 2012 05:58:33 -0000 Received: from sam.nabble.com (HELO sam.nabble.com) (216.139.236.26) by server-6.tower-182.messagelabs.com with AES256-SHA encrypted SMTP; 17 Sep 2012 05:58:33 -0000 Received: from [192.168.236.26] (helo=sam.nabble.com) by sam.nabble.com with esmtp (Exim 4.72) (envelope-from ) id 1TDULo-0003fS-6w for xen-users@lists.xensource.com; Sun, 16 Sep 2012 22:58:32 -0700 Date: Sun, 16 Sep 2012 22:58:32 -0700 (PDT) From: Robin hp To: xen-users@lists.xensource.com Message-ID: <1347861512207-5711311.post@n5.nabble.com> In-Reply-To: References: <1347851542961-5711309.post@n5.nabble.com> MIME-Version: 1.0 Subject: Re: [Xen-users] Performance of PVM and HVM X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org >How do you test native? >For "fair" comparison, you need to make sure that native has the same >cpu and memory as dom0/domU tested. For cpu, you can disable some of >them using /sys/devices/system/cpu/cpu1/online, and for memory you >might need to use "mem=2G" kernel boot parameter. >Thanks for Fajar's reply. Yes, All native,pvm and hvm have the same configurations. >Do you file:/ ? If yes, that would be the effect of dom0 cache. Try >using block devices with phy:/ >Others might comment more about this. I didn't use phy:/ for hvm, but I used file:/ for pvm, and the results were not different. For more testing, I used dd (bs=1024M count=8)to test writing speed for native, pvm and hvm. Following is the results: (2G RAM, 4cpu 3.1G) Native 159MB/s Dom0 137MB/s pvm(Phy:/) 52MB/s pvm(file:/) 684MB/s (As you said, I guess that's because of the effect of dom0 cache) hvm(file:/) 840MB/s What wired me is that most docs about xen told me pvm's performance is better, but the results of my testing told difference. -- View this message in context: http://xen.1045712.n5.nabble.com/Performance-of-PVM-and-HVM-tp5711309p5711311.html Sent from the Xen - User mailing list archive at Nabble.com. _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Mon Sep 17 06:02:19 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Mon, 17 Sep 2012 06:02:19 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TDUOb-0003ru-1o; Mon, 17 Sep 2012 06:01:25 +0000 Received: from mail27.messagelabs.com ([193.109.254.147]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TDUOZ-0003rb-6X for xen-users@lists.xensource.com; Mon, 17 Sep 2012 06:01:23 +0000 X-Env-Sender: pingh.cd@gmail.com X-Msg-Ref: server-10.tower-27.messagelabs.com!1347861671!6090530!1 X-Originating-IP: [216.139.236.26] X-SpamReason: No, hits=0.0 required=7.0 tests=ML_RADAR_SPEW_LINKS_14, spamassassin: X-StarScan-Received: X-StarScan-Version: 6.6.1.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 25841 invoked from network); 17 Sep 2012 06:01:12 -0000 Received: from sam.nabble.com (HELO sam.nabble.com) (216.139.236.26) by server-10.tower-27.messagelabs.com with AES256-SHA encrypted SMTP; 17 Sep 2012 06:01:12 -0000 Received: from [192.168.236.26] (helo=sam.nabble.com) by sam.nabble.com with esmtp (Exim 4.72) (envelope-from ) id 1TDUOM-0004Wx-V3 for xen-users@lists.xensource.com; Sun, 16 Sep 2012 23:01:10 -0700 Date: Sun, 16 Sep 2012 23:01:10 -0700 (PDT) From: Robin hp To: xen-users@lists.xensource.com Message-ID: <1347861670953-5711312.post@n5.nabble.com> In-Reply-To: <1347851542961-5711309.post@n5.nabble.com> References: <1347851542961-5711309.post@n5.nabble.com> MIME-Version: 1.0 Subject: Re: [Xen-users] Performance of PVM and HVM X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org >How do you test native? >For "fair" comparison, you need to make sure that native has the same >cpu and memory as dom0/domU tested. For cpu, you can disable some of >them using /sys/devices/system/cpu/cpu1/online, and for memory you >might need to use "mem=2G" kernel boot parameter. >Thanks for Fajar's reply. Yes, All native,pvm and hvm have the same configurations. >Do you file:/ ? If yes, that would be the effect of dom0 cache. Try >using block devices with phy:/ >Others might comment more about this. I didn't use phy:/ for hvm, but I used file:/ for pvm, and the results were not different. For more testing, I used dd (bs=1024M count=8)to test writing speed for native, pvm and hvm. Following is the results: (2G RAM, 4cpu 3.1G) Native 159MB/s Dom0 137MB/s pvm(Phy:/) 52MB/s pvm(file:/) 684MB/s (As you said, I guess that's because of the effect of dom0 cache) hvm(file:/) 840MB/s What wired me is that most docs about xen told me pvm's performance is better, but the results of my testing told difference. -- View this message in context: http://xen.1045712.n5.nabble.com/Performance-of-PVM-and-HVM-tp5711309p5711312.html Sent from the Xen - User mailing list archive at Nabble.com. _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Mon Sep 17 06:02:19 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Mon, 17 Sep 2012 06:02:19 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TDUOb-0003ru-1o; Mon, 17 Sep 2012 06:01:25 +0000 Received: from mail27.messagelabs.com ([193.109.254.147]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TDUOZ-0003rb-6X for xen-users@lists.xensource.com; Mon, 17 Sep 2012 06:01:23 +0000 X-Env-Sender: pingh.cd@gmail.com X-Msg-Ref: server-10.tower-27.messagelabs.com!1347861671!6090530!1 X-Originating-IP: [216.139.236.26] X-SpamReason: No, hits=0.0 required=7.0 tests=ML_RADAR_SPEW_LINKS_14, spamassassin: X-StarScan-Received: X-StarScan-Version: 6.6.1.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 25841 invoked from network); 17 Sep 2012 06:01:12 -0000 Received: from sam.nabble.com (HELO sam.nabble.com) (216.139.236.26) by server-10.tower-27.messagelabs.com with AES256-SHA encrypted SMTP; 17 Sep 2012 06:01:12 -0000 Received: from [192.168.236.26] (helo=sam.nabble.com) by sam.nabble.com with esmtp (Exim 4.72) (envelope-from ) id 1TDUOM-0004Wx-V3 for xen-users@lists.xensource.com; Sun, 16 Sep 2012 23:01:10 -0700 Date: Sun, 16 Sep 2012 23:01:10 -0700 (PDT) From: Robin hp To: xen-users@lists.xensource.com Message-ID: <1347861670953-5711312.post@n5.nabble.com> In-Reply-To: <1347851542961-5711309.post@n5.nabble.com> References: <1347851542961-5711309.post@n5.nabble.com> MIME-Version: 1.0 Subject: Re: [Xen-users] Performance of PVM and HVM X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org >How do you test native? >For "fair" comparison, you need to make sure that native has the same >cpu and memory as dom0/domU tested. For cpu, you can disable some of >them using /sys/devices/system/cpu/cpu1/online, and for memory you >might need to use "mem=2G" kernel boot parameter. >Thanks for Fajar's reply. Yes, All native,pvm and hvm have the same configurations. >Do you file:/ ? If yes, that would be the effect of dom0 cache. Try >using block devices with phy:/ >Others might comment more about this. I didn't use phy:/ for hvm, but I used file:/ for pvm, and the results were not different. For more testing, I used dd (bs=1024M count=8)to test writing speed for native, pvm and hvm. Following is the results: (2G RAM, 4cpu 3.1G) Native 159MB/s Dom0 137MB/s pvm(Phy:/) 52MB/s pvm(file:/) 684MB/s (As you said, I guess that's because of the effect of dom0 cache) hvm(file:/) 840MB/s What wired me is that most docs about xen told me pvm's performance is better, but the results of my testing told difference. -- View this message in context: http://xen.1045712.n5.nabble.com/Performance-of-PVM-and-HVM-tp5711309p5711312.html Sent from the Xen - User mailing list archive at Nabble.com. _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Mon Sep 17 06:03:27 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Mon, 17 Sep 2012 06:03:27 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TDUPq-00040J-Og; Mon, 17 Sep 2012 06:02:42 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TDUPp-000403-9s for xen-users@lists.xensource.com; Mon, 17 Sep 2012 06:02:41 +0000 Received: from [85.158.143.35:35597] by server-3.bemta-4.messagelabs.com id 61/A7-08232-00DB6505; Mon, 17 Sep 2012 06:02:40 +0000 X-Env-Sender: pingh.cd@gmail.com X-Msg-Ref: server-2.tower-21.messagelabs.com!1347861749!7556357!1 X-Originating-IP: [216.139.236.26] X-SpamReason: No, hits=0.0 required=7.0 tests=ML_RADAR_SPEW_LINKS_14, spamassassin: X-StarScan-Received: X-StarScan-Version: 6.6.1.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 25697 invoked from network); 17 Sep 2012 06:02:30 -0000 Received: from sam.nabble.com (HELO sam.nabble.com) (216.139.236.26) by server-2.tower-21.messagelabs.com with AES256-SHA encrypted SMTP; 17 Sep 2012 06:02:30 -0000 Received: from [192.168.236.26] (helo=sam.nabble.com) by sam.nabble.com with esmtp (Exim 4.72) (envelope-from ) id 1TDUPd-0005BA-6z for xen-users@lists.xensource.com; Sun, 16 Sep 2012 23:02:29 -0700 Date: Sun, 16 Sep 2012 23:02:29 -0700 (PDT) From: Robin hp To: xen-users@lists.xensource.com Message-ID: <1347861749209-5711313.post@n5.nabble.com> In-Reply-To: References: <1347851542961-5711309.post@n5.nabble.com> MIME-Version: 1.0 Subject: Re: [Xen-users] Performance of PVM and HVM X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org >How do you test native? >For "fair" comparison, you need to make sure that native has the same >cpu and memory as dom0/domU tested. For cpu, you can disable some of >them using /sys/devices/system/cpu/cpu1/online, and for memory you >might need to use "mem=2G" kernel boot parameter. >Thanks for Fajar's reply. Yes, All native,pvm and hvm have the same configurations. >Do you file:/ ? If yes, that would be the effect of dom0 cache. Try >using block devices with phy:/ >Others might comment more about this. I didn't use phy:/ for hvm, but I used file:/ for pvm, and the results were not different. For more testing, I used dd (bs=1024M count=8)to test writing speed for native, pvm and hvm. Following is the results: (2G RAM, 4cpu 3.1G) Native 159MB/s Dom0 137MB/s pvm(Phy:/) 52MB/s pvm(file:/) 684MB/s (As you said, I guess that's because of the effect of dom0 cache) hvm(file:/) 840MB/s What wired me is that most docs about xen told me pvm's performance is better, but the results of my testing told difference. -- View this message in context: http://xen.1045712.n5.nabble.com/Performance-of-PVM-and-HVM-tp5711309p5711313.html Sent from the Xen - User mailing list archive at Nabble.com. _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Mon Sep 17 06:03:27 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Mon, 17 Sep 2012 06:03:27 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TDUPq-00040J-Og; Mon, 17 Sep 2012 06:02:42 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TDUPp-000403-9s for xen-users@lists.xensource.com; Mon, 17 Sep 2012 06:02:41 +0000 Received: from [85.158.143.35:35597] by server-3.bemta-4.messagelabs.com id 61/A7-08232-00DB6505; Mon, 17 Sep 2012 06:02:40 +0000 X-Env-Sender: pingh.cd@gmail.com X-Msg-Ref: server-2.tower-21.messagelabs.com!1347861749!7556357!1 X-Originating-IP: [216.139.236.26] X-SpamReason: No, hits=0.0 required=7.0 tests=ML_RADAR_SPEW_LINKS_14, spamassassin: X-StarScan-Received: X-StarScan-Version: 6.6.1.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 25697 invoked from network); 17 Sep 2012 06:02:30 -0000 Received: from sam.nabble.com (HELO sam.nabble.com) (216.139.236.26) by server-2.tower-21.messagelabs.com with AES256-SHA encrypted SMTP; 17 Sep 2012 06:02:30 -0000 Received: from [192.168.236.26] (helo=sam.nabble.com) by sam.nabble.com with esmtp (Exim 4.72) (envelope-from ) id 1TDUPd-0005BA-6z for xen-users@lists.xensource.com; Sun, 16 Sep 2012 23:02:29 -0700 Date: Sun, 16 Sep 2012 23:02:29 -0700 (PDT) From: Robin hp To: xen-users@lists.xensource.com Message-ID: <1347861749209-5711313.post@n5.nabble.com> In-Reply-To: References: <1347851542961-5711309.post@n5.nabble.com> MIME-Version: 1.0 Subject: Re: [Xen-users] Performance of PVM and HVM X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org >How do you test native? >For "fair" comparison, you need to make sure that native has the same >cpu and memory as dom0/domU tested. For cpu, you can disable some of >them using /sys/devices/system/cpu/cpu1/online, and for memory you >might need to use "mem=2G" kernel boot parameter. >Thanks for Fajar's reply. Yes, All native,pvm and hvm have the same configurations. >Do you file:/ ? If yes, that would be the effect of dom0 cache. Try >using block devices with phy:/ >Others might comment more about this. I didn't use phy:/ for hvm, but I used file:/ for pvm, and the results were not different. For more testing, I used dd (bs=1024M count=8)to test writing speed for native, pvm and hvm. Following is the results: (2G RAM, 4cpu 3.1G) Native 159MB/s Dom0 137MB/s pvm(Phy:/) 52MB/s pvm(file:/) 684MB/s (As you said, I guess that's because of the effect of dom0 cache) hvm(file:/) 840MB/s What wired me is that most docs about xen told me pvm's performance is better, but the results of my testing told difference. -- View this message in context: http://xen.1045712.n5.nabble.com/Performance-of-PVM-and-HVM-tp5711309p5711313.html Sent from the Xen - User mailing list archive at Nabble.com. _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Mon Sep 17 06:19:16 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Mon, 17 Sep 2012 06:19:16 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TDUfA-0004kF-Hu; Mon, 17 Sep 2012 06:18:32 +0000 Received: from mail27.messagelabs.com ([193.109.254.147]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TDUf8-0004kA-Iy for xen-users@lists.xensource.com; Mon, 17 Sep 2012 06:18:30 +0000 X-Env-Sender: fajar@fajar.net X-Msg-Ref: server-6.tower-27.messagelabs.com!1347862700!5695833!1 X-Originating-IP: [209.85.219.43] X-SpamReason: No, hits=0.3 required=7.0 tests=RCVD_BY_IP X-StarScan-Received: X-StarScan-Version: 6.6.1.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 1761 invoked from network); 17 Sep 2012 06:18:22 -0000 Received: from mail-oa0-f43.google.com (HELO mail-oa0-f43.google.com) (209.85.219.43) by server-6.tower-27.messagelabs.com with RC4-SHA encrypted SMTP; 17 Sep 2012 06:18:22 -0000 Received: by oagl10 with SMTP id l10so5946470oag.30 for ; Sun, 16 Sep 2012 23:18:19 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:x-gm-message-state; bh=ZEnHtD5Ceb2UKrvi+HRYbw24SkyQEwd9WiqYE+HY7Mw=; b=O8Res71bQSZsPu9+in2grG7gCDQYSWt2Pv9zapxbAl+fbyPoh5ehMi8BcLtp9OMRmA wM7CRycJ2cWzykALdSN+DzkDN7ci2dD79FVHshggGkJVRU225oGF6AOPyCZbEgxoLRBB uvmhPRM/xQw4CB1IqsaSF2mEj5gpmx/lFwknlVf5rT4MFK76RFZc44OhfIr1IJ6RtWxA +B8yYyasVYT2A1/4Tkba7n4UxTUJUJF051QCiP6Bgl4xtY1Z5fCQgh1OJiCp9seEVSzg vtRGLIJK+5KmI45jUU0idyIOmSkc0Eq4O6TOJ9hhNw221QwCSQ0z55rC9q+KLl02yqcn U9Iw== MIME-Version: 1.0 Received: by 10.60.13.71 with SMTP id f7mr10822711oec.43.1347862699427; Sun, 16 Sep 2012 23:18:19 -0700 (PDT) Received: by 10.60.6.230 with HTTP; Sun, 16 Sep 2012 23:18:19 -0700 (PDT) In-Reply-To: <1347861512207-5711311.post@n5.nabble.com> References: <1347851542961-5711309.post@n5.nabble.com> <1347861512207-5711311.post@n5.nabble.com> Date: Mon, 17 Sep 2012 13:18:19 +0700 Message-ID: From: "Fajar A. Nugraha" To: Robin hp X-Gm-Message-State: ALoCoQn8rtvfp5tzt84tx0GfpYxlvNfXNklEs0mankTpVkBblagJW45pFoxbdwzmob2ChrqNyGUd Cc: xen-users@lists.xensource.com Subject: Re: [Xen-users] Performance of PVM and HVM X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org On Mon, Sep 17, 2012 at 12:58 PM, Robin hp wrote: >>How do you test native? > >>For "fair" comparison, you need to make sure that native has the same >>cpu and memory as dom0/domU tested. For cpu, you can disable some of >>them using /sys/devices/system/cpu/cpu1/online, and for memory you >>might need to use "mem=2G" kernel boot parameter. > >>Thanks for Fajar's reply. > > Yes, All native,pvm and hvm have the same configurations. Are you sure? setting native parameters can be tricky. > > >>Do you file:/ ? If yes, that would be the effect of dom0 cache. Try >>using block devices with phy:/ > >>Others might comment more about this. > > I didn't use phy:/ for hvm, but I used file:/ for pvm, and the results were > not different. meaning what? you've retested with phy? if not, you should. > For more testing, I used dd (bs=1024M count=8)to test writing speed for > native, pvm and hvm. Following is the results: dd is almost useless for benchmarking purposes. Personally I'd say use real workloads. For example, in the past I was choosing the best virtualization platform to run mysql. So I used sysbench on vmware, kvm, and xen. The end result was almost the same, so I ended up choosing vmware for that project because it was easier to maintain. > What wired me is that most docs about xen told me pvm's performance is > better, but the results of my testing told difference. It depends. 64bit pv have some performance penalty for some syscalls which does not exist in 32bit pv or hvm (search the list archive for details). In some cases this doesn't matter, and other pv-guest benefits more than compensate for this penalty. There's an ongoing effort to create hybrid guest to address this issue, but it's not ready yet. Again, at this point I suggest you: - use phy - use a benchmark similar to the workload you're going to use ... and if you have time, try kvm as well :) -- Fajar _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Mon Sep 17 06:19:16 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Mon, 17 Sep 2012 06:19:16 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TDUfA-0004kF-Hu; Mon, 17 Sep 2012 06:18:32 +0000 Received: from mail27.messagelabs.com ([193.109.254.147]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TDUf8-0004kA-Iy for xen-users@lists.xensource.com; Mon, 17 Sep 2012 06:18:30 +0000 X-Env-Sender: fajar@fajar.net X-Msg-Ref: server-6.tower-27.messagelabs.com!1347862700!5695833!1 X-Originating-IP: [209.85.219.43] X-SpamReason: No, hits=0.3 required=7.0 tests=RCVD_BY_IP X-StarScan-Received: X-StarScan-Version: 6.6.1.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 1761 invoked from network); 17 Sep 2012 06:18:22 -0000 Received: from mail-oa0-f43.google.com (HELO mail-oa0-f43.google.com) (209.85.219.43) by server-6.tower-27.messagelabs.com with RC4-SHA encrypted SMTP; 17 Sep 2012 06:18:22 -0000 Received: by oagl10 with SMTP id l10so5946470oag.30 for ; Sun, 16 Sep 2012 23:18:19 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:x-gm-message-state; bh=ZEnHtD5Ceb2UKrvi+HRYbw24SkyQEwd9WiqYE+HY7Mw=; b=O8Res71bQSZsPu9+in2grG7gCDQYSWt2Pv9zapxbAl+fbyPoh5ehMi8BcLtp9OMRmA wM7CRycJ2cWzykALdSN+DzkDN7ci2dD79FVHshggGkJVRU225oGF6AOPyCZbEgxoLRBB uvmhPRM/xQw4CB1IqsaSF2mEj5gpmx/lFwknlVf5rT4MFK76RFZc44OhfIr1IJ6RtWxA +B8yYyasVYT2A1/4Tkba7n4UxTUJUJF051QCiP6Bgl4xtY1Z5fCQgh1OJiCp9seEVSzg vtRGLIJK+5KmI45jUU0idyIOmSkc0Eq4O6TOJ9hhNw221QwCSQ0z55rC9q+KLl02yqcn U9Iw== MIME-Version: 1.0 Received: by 10.60.13.71 with SMTP id f7mr10822711oec.43.1347862699427; Sun, 16 Sep 2012 23:18:19 -0700 (PDT) Received: by 10.60.6.230 with HTTP; Sun, 16 Sep 2012 23:18:19 -0700 (PDT) In-Reply-To: <1347861512207-5711311.post@n5.nabble.com> References: <1347851542961-5711309.post@n5.nabble.com> <1347861512207-5711311.post@n5.nabble.com> Date: Mon, 17 Sep 2012 13:18:19 +0700 Message-ID: From: "Fajar A. Nugraha" To: Robin hp X-Gm-Message-State: ALoCoQn8rtvfp5tzt84tx0GfpYxlvNfXNklEs0mankTpVkBblagJW45pFoxbdwzmob2ChrqNyGUd Cc: xen-users@lists.xensource.com Subject: Re: [Xen-users] Performance of PVM and HVM X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org On Mon, Sep 17, 2012 at 12:58 PM, Robin hp wrote: >>How do you test native? > >>For "fair" comparison, you need to make sure that native has the same >>cpu and memory as dom0/domU tested. For cpu, you can disable some of >>them using /sys/devices/system/cpu/cpu1/online, and for memory you >>might need to use "mem=2G" kernel boot parameter. > >>Thanks for Fajar's reply. > > Yes, All native,pvm and hvm have the same configurations. Are you sure? setting native parameters can be tricky. > > >>Do you file:/ ? If yes, that would be the effect of dom0 cache. Try >>using block devices with phy:/ > >>Others might comment more about this. > > I didn't use phy:/ for hvm, but I used file:/ for pvm, and the results were > not different. meaning what? you've retested with phy? if not, you should. > For more testing, I used dd (bs=1024M count=8)to test writing speed for > native, pvm and hvm. Following is the results: dd is almost useless for benchmarking purposes. Personally I'd say use real workloads. For example, in the past I was choosing the best virtualization platform to run mysql. So I used sysbench on vmware, kvm, and xen. The end result was almost the same, so I ended up choosing vmware for that project because it was easier to maintain. > What wired me is that most docs about xen told me pvm's performance is > better, but the results of my testing told difference. It depends. 64bit pv have some performance penalty for some syscalls which does not exist in 32bit pv or hvm (search the list archive for details). In some cases this doesn't matter, and other pv-guest benefits more than compensate for this penalty. There's an ongoing effort to create hybrid guest to address this issue, but it's not ready yet. Again, at this point I suggest you: - use phy - use a benchmark similar to the workload you're going to use ... and if you have time, try kvm as well :) -- Fajar _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Mon Sep 17 06:58:17 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Mon, 17 Sep 2012 06:58:17 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TDVH0-0005Su-8M; Mon, 17 Sep 2012 06:57:38 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TDVGz-0005Sg-7i for xen-users@lists.xen.org; Mon, 17 Sep 2012 06:57:37 +0000 Received: from [85.158.139.211:31951] by server-3.bemta-5.messagelabs.com id 51/81-21836-0E9C6505; Mon, 17 Sep 2012 06:57:36 +0000 X-Env-Sender: Rudi@softdux.com X-Msg-Ref: server-16.tower-206.messagelabs.com!1347865054!18849478!1 X-Originating-IP: [64.191.118.125] X-SpamReason: No, hits=0.3 required=7.0 tests=RCVD_BY_IP X-StarScan-Received: X-StarScan-Version: 6.6.1.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 21622 invoked from network); 17 Sep 2012 06:57:35 -0000 Received: from mercury.securehosting.co.za (HELO mercury.securehosting.co.za) (64.191.118.125) by server-16.tower-206.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 17 Sep 2012 06:57:35 -0000 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=softdux.com; s=default; h=Content-Type:Cc:To:Subject:Message-ID:Date:From:References:In-Reply-To:Reply-To:MIME-Version; bh=6XYoTopVIagxl0aPHufiB/CyKJite2fvTnbwGmqm48g=; b=ANOip6Nvv7GA0g8nq0Fr033o3Qf7RXsb7ckIQ18cdZPBUf/odOeD988K+4DZOyOXb4iO8oQqhzUIf/vebRhMF3Chy6cVuf0s8lF1CiKIxbIPVsojqdNpTBEcmcLxHDtK; Received: from localhost ([127.0.0.1]:36127 helo=mercury.securehosting.co.za) by mercury.securehosting.co.za with esmtpa (Exim 4.77) (envelope-from ) id 1TDVPb-003Ack-E3 for xen-users@lists.xen.org; Mon, 17 Sep 2012 09:06:31 +0200 Received: from mail-vb0-f45.google.com ([209.85.212.45] helo=mail-vb0-f45.google.com) by mercury.securehosting.co.za with ESMTP (ASSP 1.9); 17 Sep 2012 09:06:30 +0200 Received: by vbip1 with SMTP id p1so8302899vbi.32 for ; Sun, 16 Sep 2012 23:57:33 -0700 (PDT) Received: by 10.220.155.203 with SMTP id t11mr6882636vcw.36.1347865053847; Sun, 16 Sep 2012 23:57:33 -0700 (PDT) MIME-Version: 1.0 Received: by 10.58.225.228 with HTTP; Sun, 16 Sep 2012 23:57:03 -0700 (PDT) In-Reply-To: <006e01cd947f$f3c25890$db4709b0$@gmail.com> References: <003601cd9430$a381db70$ea859250$@gmail.com> <1347818899.25803.75.camel@dagon.hellion.org.uk> <004e01cd9446$b7636b20$262a4160$@gmail.com> <5056603D.8030007@ajlc.waterloo.on.ca> <006701cd9477$0d045820$270d0860$@gmail.com> <505686EA.9060801@ajlc.waterloo.on.ca> <006e01cd947f$f3c25890$db4709b0$@gmail.com> From: Rudi Ahlers Date: Mon, 17 Sep 2012 08:57:03 +0200 Message-ID: To: Marc Tousignant X-AntiAbuse: This header was added to track abuse, please include it with any abuse report X-AntiAbuse: Primary Hostname - mercury.securehosting.co.za X-AntiAbuse: Original Domain - lists.xen.org X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12] X-AntiAbuse: Sender Address Domain - softdux.com X-Source: X-Source-Args: X-Source-Dir: Cc: xen-users@lists.xen.org, Tony Lill Subject: Re: [Xen-users] Setting up XEN domU causes RAID5 to fail? X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list Reply-To: rudi@softdux.com List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org On Mon, Sep 17, 2012 at 4:55 AM, Marc Tousignant wrote: > Maybe that is my issue. I'll ask one of my coworkers if he can misplace a > 2TB drive and I can eliminate the RAID. I had a few 500GB drives laying > around and decided to repurpose them. > > MarcT > > Have you tried doing this with RAID 6 or RAID 10 instead? -- Kind Regards Rudi Ahlers SoftDux Website: http://www.SoftDux.com Technical Blog: http://Blog.SoftDux.com Cell: 082 554 7532 Fax: 086 268 8492 _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Mon Sep 17 06:58:17 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Mon, 17 Sep 2012 06:58:17 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TDVH0-0005Su-8M; Mon, 17 Sep 2012 06:57:38 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TDVGz-0005Sg-7i for xen-users@lists.xen.org; Mon, 17 Sep 2012 06:57:37 +0000 Received: from [85.158.139.211:31951] by server-3.bemta-5.messagelabs.com id 51/81-21836-0E9C6505; Mon, 17 Sep 2012 06:57:36 +0000 X-Env-Sender: Rudi@softdux.com X-Msg-Ref: server-16.tower-206.messagelabs.com!1347865054!18849478!1 X-Originating-IP: [64.191.118.125] X-SpamReason: No, hits=0.3 required=7.0 tests=RCVD_BY_IP X-StarScan-Received: X-StarScan-Version: 6.6.1.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 21622 invoked from network); 17 Sep 2012 06:57:35 -0000 Received: from mercury.securehosting.co.za (HELO mercury.securehosting.co.za) (64.191.118.125) by server-16.tower-206.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 17 Sep 2012 06:57:35 -0000 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=softdux.com; s=default; h=Content-Type:Cc:To:Subject:Message-ID:Date:From:References:In-Reply-To:Reply-To:MIME-Version; bh=6XYoTopVIagxl0aPHufiB/CyKJite2fvTnbwGmqm48g=; b=ANOip6Nvv7GA0g8nq0Fr033o3Qf7RXsb7ckIQ18cdZPBUf/odOeD988K+4DZOyOXb4iO8oQqhzUIf/vebRhMF3Chy6cVuf0s8lF1CiKIxbIPVsojqdNpTBEcmcLxHDtK; Received: from localhost ([127.0.0.1]:36127 helo=mercury.securehosting.co.za) by mercury.securehosting.co.za with esmtpa (Exim 4.77) (envelope-from ) id 1TDVPb-003Ack-E3 for xen-users@lists.xen.org; Mon, 17 Sep 2012 09:06:31 +0200 Received: from mail-vb0-f45.google.com ([209.85.212.45] helo=mail-vb0-f45.google.com) by mercury.securehosting.co.za with ESMTP (ASSP 1.9); 17 Sep 2012 09:06:30 +0200 Received: by vbip1 with SMTP id p1so8302899vbi.32 for ; Sun, 16 Sep 2012 23:57:33 -0700 (PDT) Received: by 10.220.155.203 with SMTP id t11mr6882636vcw.36.1347865053847; Sun, 16 Sep 2012 23:57:33 -0700 (PDT) MIME-Version: 1.0 Received: by 10.58.225.228 with HTTP; Sun, 16 Sep 2012 23:57:03 -0700 (PDT) In-Reply-To: <006e01cd947f$f3c25890$db4709b0$@gmail.com> References: <003601cd9430$a381db70$ea859250$@gmail.com> <1347818899.25803.75.camel@dagon.hellion.org.uk> <004e01cd9446$b7636b20$262a4160$@gmail.com> <5056603D.8030007@ajlc.waterloo.on.ca> <006701cd9477$0d045820$270d0860$@gmail.com> <505686EA.9060801@ajlc.waterloo.on.ca> <006e01cd947f$f3c25890$db4709b0$@gmail.com> From: Rudi Ahlers Date: Mon, 17 Sep 2012 08:57:03 +0200 Message-ID: To: Marc Tousignant X-AntiAbuse: This header was added to track abuse, please include it with any abuse report X-AntiAbuse: Primary Hostname - mercury.securehosting.co.za X-AntiAbuse: Original Domain - lists.xen.org X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12] X-AntiAbuse: Sender Address Domain - softdux.com X-Source: X-Source-Args: X-Source-Dir: Cc: xen-users@lists.xen.org, Tony Lill Subject: Re: [Xen-users] Setting up XEN domU causes RAID5 to fail? X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list Reply-To: rudi@softdux.com List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org On Mon, Sep 17, 2012 at 4:55 AM, Marc Tousignant wrote: > Maybe that is my issue. I'll ask one of my coworkers if he can misplace a > 2TB drive and I can eliminate the RAID. I had a few 500GB drives laying > around and decided to repurpose them. > > MarcT > > Have you tried doing this with RAID 6 or RAID 10 instead? -- Kind Regards Rudi Ahlers SoftDux Website: http://www.SoftDux.com Technical Blog: http://Blog.SoftDux.com Cell: 082 554 7532 Fax: 086 268 8492 _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Mon Sep 17 07:47:17 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Mon, 17 Sep 2012 07:47:17 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TDW2E-0006Qs-QO; Mon, 17 Sep 2012 07:46:26 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TDW2D-0006Qn-DK for xen-users@lists.xen.org; Mon, 17 Sep 2012 07:46:25 +0000 Received: from [85.158.137.99:23536] by server-11.bemta-3.messagelabs.com id 74/9A-30250-055D6505; Mon, 17 Sep 2012 07:46:24 +0000 X-Env-Sender: myrdhn@gmail.com X-Msg-Ref: server-10.tower-217.messagelabs.com!1347867982!17950124!1 X-Originating-IP: [209.85.216.173] X-SpamReason: No, hits=0.3 required=7.0 tests=ML_RADAR_SPEW_LINKS_14, RCVD_BY_IP,spamassassin: X-StarScan-Received: X-StarScan-Version: 6.6.1.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 4970 invoked from network); 17 Sep 2012 07:46:23 -0000 Received: from mail-qc0-f173.google.com (HELO mail-qc0-f173.google.com) (209.85.216.173) by server-10.tower-217.messagelabs.com with RC4-SHA encrypted SMTP; 17 Sep 2012 07:46:23 -0000 Received: by qcab12 with SMTP id b12so5681725qca.32 for ; Mon, 17 Sep 2012 00:46:22 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=from:to:cc:references:in-reply-to:subject:date:message-id :mime-version:content-type:content-transfer-encoding:x-mailer :thread-index:content-language; bh=bADNvQ45P2Wvc0k1PF5p7y3d1y9fEIpK8s6t6MRnXwU=; b=DtLJhExFEUFvMbL6rnVzQabyU3Ph9JI54e5EZB+ysxcvbFT/4OpGv/J0/VlM92EYfb avq9SaKMxOUdvuFrdOKenD+ElYvpN+6hry/pUxggaaAtk2X6VrkLpbnu7QL6IMGJWTQs zdjMnuReyl75WXvBxb2dlmF17NOY7u+NriTULOWIndwdXQiLjaWo73BN+d52KYrS7eUK /PvLn61g2j1oLP6Um3jOsmIlLm/c+xXHXobtRD6yCtgWPSId5CJ75PdRmsPz7964EX/m O3wr4QoQBaSGQq7kL+NSMgSjRkm0XC3BABG00wqXll/HB6T7LAaM85GiDzeMm3LJ0ORD gR7A== Received: by 10.224.187.146 with SMTP id cw18mr17150601qab.35.1347867982255; Mon, 17 Sep 2012 00:46:22 -0700 (PDT) Received: from Belldandy (c-76-119-253-48.hsd1.ma.comcast.net. [76.119.253.48]) by mx.google.com with ESMTPS id et6sm14297506qab.8.2012.09.17.00.46.20 (version=TLSv1/SSLv3 cipher=OTHER); Mon, 17 Sep 2012 00:46:21 -0700 (PDT) From: "Marc Tousignant" To: References: <003601cd9430$a381db70$ea859250$@gmail.com> <1347818899.25803.75.camel@dagon.hellion.org.uk> <004e01cd9446$b7636b20$262a4160$@gmail.com> <5056603D.8030007@ajlc.waterloo.on.ca> <006701cd9477$0d045820$270d0860$@gmail.com> <505686EA.9060801@ajlc.waterloo.on.ca> <006e01cd947f$f3c25890$db4709b0$@gmail.com> In-Reply-To: Date: Mon, 17 Sep 2012 03:46:24 -0400 Message-ID: <006f01cd94a8$8a8e98b0$9fabca10$@gmail.com> MIME-Version: 1.0 X-Mailer: Microsoft Outlook 14.0 Thread-Index: AQEtIveC4IhcOcllJOhnnzkXfTJ4EAF4akKmAbXW2NwBi1ebzAHmfEp2AbO1nFMDDcP2QwIt2Zc6mGKMjvA= Content-Language: en-us Cc: xen-users@lists.xen.org, 'Tony Lill' Subject: Re: [Xen-users] Setting up XEN domU causes RAID5 to fail? X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org RAID1+0 is also a no go due to loss of space, and uselessness. If you want speed and redundancy and have the drives for RAID1+0, just go with RAID6 I'd lose too much space with RAID6, I have plans for all ~1.8TB, the loss of ~500GB would be too much of a hit. I do have a second machine running XEN with software RAID1 and hardware RAID5 without issues. The drives in this config are both physical and file based. No issues and I have been running for over 2 years moving from 3 all the way to 4 without incident. -----Original Message----- From: xen-users-bounces@lists.xen.org [mailto:xen-users-bounces@lists.xen.org] On Behalf Of Rudi Ahlers Sent: Monday, September 17, 2012 2:57 AM To: Marc Tousignant Cc: xen-users@lists.xen.org; Tony Lill Subject: Re: [Xen-users] Setting up XEN domU causes RAID5 to fail? On Mon, Sep 17, 2012 at 4:55 AM, Marc Tousignant wrote: > Maybe that is my issue. I'll ask one of my coworkers if he can > misplace a 2TB drive and I can eliminate the RAID. I had a few 500GB > drives laying around and decided to repurpose them. > > MarcT > > Have you tried doing this with RAID 6 or RAID 10 instead? -- Kind Regards Rudi Ahlers SoftDux Website: http://www.SoftDux.com Technical Blog: http://Blog.SoftDux.com Cell: 082 554 7532 Fax: 086 268 8492 _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Mon Sep 17 07:47:17 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Mon, 17 Sep 2012 07:47:17 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TDW2E-0006Qs-QO; Mon, 17 Sep 2012 07:46:26 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TDW2D-0006Qn-DK for xen-users@lists.xen.org; Mon, 17 Sep 2012 07:46:25 +0000 Received: from [85.158.137.99:23536] by server-11.bemta-3.messagelabs.com id 74/9A-30250-055D6505; Mon, 17 Sep 2012 07:46:24 +0000 X-Env-Sender: myrdhn@gmail.com X-Msg-Ref: server-10.tower-217.messagelabs.com!1347867982!17950124!1 X-Originating-IP: [209.85.216.173] X-SpamReason: No, hits=0.3 required=7.0 tests=ML_RADAR_SPEW_LINKS_14, RCVD_BY_IP,spamassassin: X-StarScan-Received: X-StarScan-Version: 6.6.1.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 4970 invoked from network); 17 Sep 2012 07:46:23 -0000 Received: from mail-qc0-f173.google.com (HELO mail-qc0-f173.google.com) (209.85.216.173) by server-10.tower-217.messagelabs.com with RC4-SHA encrypted SMTP; 17 Sep 2012 07:46:23 -0000 Received: by qcab12 with SMTP id b12so5681725qca.32 for ; Mon, 17 Sep 2012 00:46:22 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=from:to:cc:references:in-reply-to:subject:date:message-id :mime-version:content-type:content-transfer-encoding:x-mailer :thread-index:content-language; bh=bADNvQ45P2Wvc0k1PF5p7y3d1y9fEIpK8s6t6MRnXwU=; b=DtLJhExFEUFvMbL6rnVzQabyU3Ph9JI54e5EZB+ysxcvbFT/4OpGv/J0/VlM92EYfb avq9SaKMxOUdvuFrdOKenD+ElYvpN+6hry/pUxggaaAtk2X6VrkLpbnu7QL6IMGJWTQs zdjMnuReyl75WXvBxb2dlmF17NOY7u+NriTULOWIndwdXQiLjaWo73BN+d52KYrS7eUK /PvLn61g2j1oLP6Um3jOsmIlLm/c+xXHXobtRD6yCtgWPSId5CJ75PdRmsPz7964EX/m O3wr4QoQBaSGQq7kL+NSMgSjRkm0XC3BABG00wqXll/HB6T7LAaM85GiDzeMm3LJ0ORD gR7A== Received: by 10.224.187.146 with SMTP id cw18mr17150601qab.35.1347867982255; Mon, 17 Sep 2012 00:46:22 -0700 (PDT) Received: from Belldandy (c-76-119-253-48.hsd1.ma.comcast.net. [76.119.253.48]) by mx.google.com with ESMTPS id et6sm14297506qab.8.2012.09.17.00.46.20 (version=TLSv1/SSLv3 cipher=OTHER); Mon, 17 Sep 2012 00:46:21 -0700 (PDT) From: "Marc Tousignant" To: References: <003601cd9430$a381db70$ea859250$@gmail.com> <1347818899.25803.75.camel@dagon.hellion.org.uk> <004e01cd9446$b7636b20$262a4160$@gmail.com> <5056603D.8030007@ajlc.waterloo.on.ca> <006701cd9477$0d045820$270d0860$@gmail.com> <505686EA.9060801@ajlc.waterloo.on.ca> <006e01cd947f$f3c25890$db4709b0$@gmail.com> In-Reply-To: Date: Mon, 17 Sep 2012 03:46:24 -0400 Message-ID: <006f01cd94a8$8a8e98b0$9fabca10$@gmail.com> MIME-Version: 1.0 X-Mailer: Microsoft Outlook 14.0 Thread-Index: AQEtIveC4IhcOcllJOhnnzkXfTJ4EAF4akKmAbXW2NwBi1ebzAHmfEp2AbO1nFMDDcP2QwIt2Zc6mGKMjvA= Content-Language: en-us Cc: xen-users@lists.xen.org, 'Tony Lill' Subject: Re: [Xen-users] Setting up XEN domU causes RAID5 to fail? X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org RAID1+0 is also a no go due to loss of space, and uselessness. If you want speed and redundancy and have the drives for RAID1+0, just go with RAID6 I'd lose too much space with RAID6, I have plans for all ~1.8TB, the loss of ~500GB would be too much of a hit. I do have a second machine running XEN with software RAID1 and hardware RAID5 without issues. The drives in this config are both physical and file based. No issues and I have been running for over 2 years moving from 3 all the way to 4 without incident. -----Original Message----- From: xen-users-bounces@lists.xen.org [mailto:xen-users-bounces@lists.xen.org] On Behalf Of Rudi Ahlers Sent: Monday, September 17, 2012 2:57 AM To: Marc Tousignant Cc: xen-users@lists.xen.org; Tony Lill Subject: Re: [Xen-users] Setting up XEN domU causes RAID5 to fail? On Mon, Sep 17, 2012 at 4:55 AM, Marc Tousignant wrote: > Maybe that is my issue. I'll ask one of my coworkers if he can > misplace a 2TB drive and I can eliminate the RAID. I had a few 500GB > drives laying around and decided to repurpose them. > > MarcT > > Have you tried doing this with RAID 6 or RAID 10 instead? -- Kind Regards Rudi Ahlers SoftDux Website: http://www.SoftDux.com Technical Blog: http://Blog.SoftDux.com Cell: 082 554 7532 Fax: 086 268 8492 _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Mon Sep 17 08:05:42 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Mon, 17 Sep 2012 08:05:42 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TDWK6-0007Gm-Nb; Mon, 17 Sep 2012 08:04:54 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TDWK5-0007Gh-CT for xen-users@lists.xen.org; Mon, 17 Sep 2012 08:04:53 +0000 Received: from [85.158.139.211:43923] by server-2.bemta-5.messagelabs.com id 2C/52-11456-4A9D6505; Mon, 17 Sep 2012 08:04:52 +0000 X-Env-Sender: Rudi@softdux.com X-Msg-Ref: server-5.tower-206.messagelabs.com!1347869090!18773283!1 X-Originating-IP: [64.191.118.125] X-SpamReason: No, hits=0.3 required=7.0 tests=RCVD_BY_IP X-StarScan-Received: X-StarScan-Version: 6.6.1.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 6028 invoked from network); 17 Sep 2012 08:04:51 -0000 Received: from mercury.securehosting.co.za (HELO mercury.securehosting.co.za) (64.191.118.125) by server-5.tower-206.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 17 Sep 2012 08:04:51 -0000 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=softdux.com; s=default; h=Content-Type:Cc:To:Subject:Message-ID:Date:From:References:In-Reply-To:Reply-To:MIME-Version; bh=/9pn52c2c+IJ4V7wHuQeeNuPgGqHzKUdGRsJ6/2zXRo=; b=jENXCNyt+62xmCDa6w2oXdS4LkbplimpVl+I8f/ngxMzMnrFmrlOMKUD8JCaU+ekviDQCN4Bu9XthdsDMFyTgck8Iukig/j3bpWplNZanbaIq2sn/Y5SY5XJiRJMta4i; Received: from localhost ([127.0.0.1]:37085 helo=mercury.securehosting.co.za) by mercury.securehosting.co.za with esmtpa (Exim 4.77) (envelope-from ) id 1TDWSh-003NPJ-J3 for xen-users@lists.xen.org; Mon, 17 Sep 2012 10:13:47 +0200 Received: from mail-vb0-f45.google.com ([209.85.212.45] helo=mail-vb0-f45.google.com) by mercury.securehosting.co.za with ESMTP (ASSP 1.9); 17 Sep 2012 10:13:47 +0200 Received: by vbip1 with SMTP id p1so8361682vbi.32 for ; Mon, 17 Sep 2012 01:04:50 -0700 (PDT) Received: by 10.52.68.226 with SMTP id z2mr3064022vdt.76.1347869089992; Mon, 17 Sep 2012 01:04:49 -0700 (PDT) MIME-Version: 1.0 Received: by 10.58.225.228 with HTTP; Mon, 17 Sep 2012 01:04:19 -0700 (PDT) In-Reply-To: <006f01cd94a8$8a8e98b0$9fabca10$@gmail.com> References: <003601cd9430$a381db70$ea859250$@gmail.com> <1347818899.25803.75.camel@dagon.hellion.org.uk> <004e01cd9446$b7636b20$262a4160$@gmail.com> <5056603D.8030007@ajlc.waterloo.on.ca> <006701cd9477$0d045820$270d0860$@gmail.com> <505686EA.9060801@ajlc.waterloo.on.ca> <006e01cd947f$f3c25890$db4709b0$@gmail.com> <006f01cd94a8$8a8e98b0$9fabca10$@gmail.com> From: Rudi Ahlers Date: Mon, 17 Sep 2012 10:04:19 +0200 Message-ID: To: Marc Tousignant X-AntiAbuse: This header was added to track abuse, please include it with any abuse report X-AntiAbuse: Primary Hostname - mercury.securehosting.co.za X-AntiAbuse: Original Domain - lists.xen.org X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12] X-AntiAbuse: Sender Address Domain - softdux.com X-Source: X-Source-Args: X-Source-Dir: Cc: xen-users@lists.xen.org, Tony Lill Subject: Re: [Xen-users] Setting up XEN domU causes RAID5 to fail? X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list Reply-To: rudi@softdux.com List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org On Mon, Sep 17, 2012 at 9:46 AM, Marc Tousignant wrote: > RAID1+0 is also a no go due to loss of space, and uselessness. If you want > speed and redundancy and have the drives for RAID1+0, just go with RAID6 > I'd lose too much space with RAID6, I have plans for all ~1.8TB, the loss of > ~500GB would be too much of a hit. > RAID5 with no spare drive (i.e. another 500GB loss) has 0 redundancy, and rebuild on RAID5 is often too high for production. If this is what caused your problems, then RAID6 / RAID10 would be better since it could sustain the high IO demands. a single 2TB drive gives no redundancy either, but could yield slightly better IO since it won't need to "rebuild' the parity while installing Windows. > I do have a second machine running XEN with software RAID1 and hardware > RAID5 without issues. The drives in this config are both physical and file > based. No issues and I have been running for over 2 years moving from 3 all > the way to 4 without incident. > > -----Original Message----- > From: xen-users-bounces@lists.xen.org > [mailto:xen-users-bounces@lists.xen.org] On Behalf Of Rudi Ahlers > Sent: Monday, September 17, 2012 2:57 AM > To: Marc Tousignant > Cc: xen-users@lists.xen.org; Tony Lill > Subject: Re: [Xen-users] Setting up XEN domU causes RAID5 to fail? > > On Mon, Sep 17, 2012 at 4:55 AM, Marc Tousignant wrote: >> Maybe that is my issue. I'll ask one of my coworkers if he can >> misplace a 2TB drive and I can eliminate the RAID. I had a few 500GB >> drives laying around and decided to repurpose them. >> >> MarcT >> >> > > > > > Have you tried doing this with RAID 6 or RAID 10 instead? > > > > -- > Kind Regards > Rudi Ahlers > SoftDux > > Website: http://www.SoftDux.com > Technical Blog: http://Blog.SoftDux.com > Cell: 082 554 7532 > Fax: 086 268 8492 > > _______________________________________________ > Xen-users mailing list > Xen-users@lists.xen.org > http://lists.xen.org/xen-users > -- Kind Regards Rudi Ahlers SoftDux Website: http://www.SoftDux.com Technical Blog: http://Blog.SoftDux.com Cell: 082 554 7532 Fax: 086 268 8492 _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Mon Sep 17 08:05:42 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Mon, 17 Sep 2012 08:05:42 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TDWK6-0007Gm-Nb; Mon, 17 Sep 2012 08:04:54 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TDWK5-0007Gh-CT for xen-users@lists.xen.org; Mon, 17 Sep 2012 08:04:53 +0000 Received: from [85.158.139.211:43923] by server-2.bemta-5.messagelabs.com id 2C/52-11456-4A9D6505; Mon, 17 Sep 2012 08:04:52 +0000 X-Env-Sender: Rudi@softdux.com X-Msg-Ref: server-5.tower-206.messagelabs.com!1347869090!18773283!1 X-Originating-IP: [64.191.118.125] X-SpamReason: No, hits=0.3 required=7.0 tests=RCVD_BY_IP X-StarScan-Received: X-StarScan-Version: 6.6.1.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 6028 invoked from network); 17 Sep 2012 08:04:51 -0000 Received: from mercury.securehosting.co.za (HELO mercury.securehosting.co.za) (64.191.118.125) by server-5.tower-206.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 17 Sep 2012 08:04:51 -0000 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=softdux.com; s=default; h=Content-Type:Cc:To:Subject:Message-ID:Date:From:References:In-Reply-To:Reply-To:MIME-Version; bh=/9pn52c2c+IJ4V7wHuQeeNuPgGqHzKUdGRsJ6/2zXRo=; b=jENXCNyt+62xmCDa6w2oXdS4LkbplimpVl+I8f/ngxMzMnrFmrlOMKUD8JCaU+ekviDQCN4Bu9XthdsDMFyTgck8Iukig/j3bpWplNZanbaIq2sn/Y5SY5XJiRJMta4i; Received: from localhost ([127.0.0.1]:37085 helo=mercury.securehosting.co.za) by mercury.securehosting.co.za with esmtpa (Exim 4.77) (envelope-from ) id 1TDWSh-003NPJ-J3 for xen-users@lists.xen.org; Mon, 17 Sep 2012 10:13:47 +0200 Received: from mail-vb0-f45.google.com ([209.85.212.45] helo=mail-vb0-f45.google.com) by mercury.securehosting.co.za with ESMTP (ASSP 1.9); 17 Sep 2012 10:13:47 +0200 Received: by vbip1 with SMTP id p1so8361682vbi.32 for ; Mon, 17 Sep 2012 01:04:50 -0700 (PDT) Received: by 10.52.68.226 with SMTP id z2mr3064022vdt.76.1347869089992; Mon, 17 Sep 2012 01:04:49 -0700 (PDT) MIME-Version: 1.0 Received: by 10.58.225.228 with HTTP; Mon, 17 Sep 2012 01:04:19 -0700 (PDT) In-Reply-To: <006f01cd94a8$8a8e98b0$9fabca10$@gmail.com> References: <003601cd9430$a381db70$ea859250$@gmail.com> <1347818899.25803.75.camel@dagon.hellion.org.uk> <004e01cd9446$b7636b20$262a4160$@gmail.com> <5056603D.8030007@ajlc.waterloo.on.ca> <006701cd9477$0d045820$270d0860$@gmail.com> <505686EA.9060801@ajlc.waterloo.on.ca> <006e01cd947f$f3c25890$db4709b0$@gmail.com> <006f01cd94a8$8a8e98b0$9fabca10$@gmail.com> From: Rudi Ahlers Date: Mon, 17 Sep 2012 10:04:19 +0200 Message-ID: To: Marc Tousignant X-AntiAbuse: This header was added to track abuse, please include it with any abuse report X-AntiAbuse: Primary Hostname - mercury.securehosting.co.za X-AntiAbuse: Original Domain - lists.xen.org X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12] X-AntiAbuse: Sender Address Domain - softdux.com X-Source: X-Source-Args: X-Source-Dir: Cc: xen-users@lists.xen.org, Tony Lill Subject: Re: [Xen-users] Setting up XEN domU causes RAID5 to fail? X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list Reply-To: rudi@softdux.com List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org On Mon, Sep 17, 2012 at 9:46 AM, Marc Tousignant wrote: > RAID1+0 is also a no go due to loss of space, and uselessness. If you want > speed and redundancy and have the drives for RAID1+0, just go with RAID6 > I'd lose too much space with RAID6, I have plans for all ~1.8TB, the loss of > ~500GB would be too much of a hit. > RAID5 with no spare drive (i.e. another 500GB loss) has 0 redundancy, and rebuild on RAID5 is often too high for production. If this is what caused your problems, then RAID6 / RAID10 would be better since it could sustain the high IO demands. a single 2TB drive gives no redundancy either, but could yield slightly better IO since it won't need to "rebuild' the parity while installing Windows. > I do have a second machine running XEN with software RAID1 and hardware > RAID5 without issues. The drives in this config are both physical and file > based. No issues and I have been running for over 2 years moving from 3 all > the way to 4 without incident. > > -----Original Message----- > From: xen-users-bounces@lists.xen.org > [mailto:xen-users-bounces@lists.xen.org] On Behalf Of Rudi Ahlers > Sent: Monday, September 17, 2012 2:57 AM > To: Marc Tousignant > Cc: xen-users@lists.xen.org; Tony Lill > Subject: Re: [Xen-users] Setting up XEN domU causes RAID5 to fail? > > On Mon, Sep 17, 2012 at 4:55 AM, Marc Tousignant wrote: >> Maybe that is my issue. I'll ask one of my coworkers if he can >> misplace a 2TB drive and I can eliminate the RAID. I had a few 500GB >> drives laying around and decided to repurpose them. >> >> MarcT >> >> > > > > > Have you tried doing this with RAID 6 or RAID 10 instead? > > > > -- > Kind Regards > Rudi Ahlers > SoftDux > > Website: http://www.SoftDux.com > Technical Blog: http://Blog.SoftDux.com > Cell: 082 554 7532 > Fax: 086 268 8492 > > _______________________________________________ > Xen-users mailing list > Xen-users@lists.xen.org > http://lists.xen.org/xen-users > -- Kind Regards Rudi Ahlers SoftDux Website: http://www.SoftDux.com Technical Blog: http://Blog.SoftDux.com Cell: 082 554 7532 Fax: 086 268 8492 _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Mon Sep 17 08:12:08 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Mon, 17 Sep 2012 08:12:08 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TDWQP-0007VC-Se; Mon, 17 Sep 2012 08:11:25 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TDWQO-0007V6-Ds for xen-users@lists.xen.org; Mon, 17 Sep 2012 08:11:24 +0000 Received: from [85.158.138.51:15841] by server-12.bemta-3.messagelabs.com id A5/98-10384-B2BD6505; Mon, 17 Sep 2012 08:11:23 +0000 X-Env-Sender: joost@antarean.org X-Msg-Ref: server-8.tower-174.messagelabs.com!1347869483!30774552!1 X-Originating-IP: [212.54.42.165] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogMjEyLjU0LjQyLjE2NSA9PiAxNDU3Mjk=\n X-StarScan-Received: X-StarScan-Version: 6.6.1.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 6475 invoked from network); 17 Sep 2012 08:11:23 -0000 Received: from smtpq2.tb.mail.iss.as9143.net (HELO smtpq2.tb.mail.iss.as9143.net) (212.54.42.165) by server-8.tower-174.messagelabs.com with SMTP; 17 Sep 2012 08:11:23 -0000 Received: from [212.54.42.134] (helo=smtp3.tb.mail.iss.as9143.net) by smtpq2.tb.mail.iss.as9143.net with esmtp (Exim 4.71) (envelope-from ) id 1TDWQN-0006cs-4f for xen-users@lists.xen.org; Mon, 17 Sep 2012 10:11:23 +0200 Received: from 54698b76.cm-12-2c.dynamic.ziggo.nl ([84.105.139.118] helo=data.antarean.org) by smtp3.tb.mail.iss.as9143.net with esmtp (Exim 4.71) (envelope-from ) id 1TDWQM-0005aE-1j for xen-users@lists.xen.org; Mon, 17 Sep 2012 10:11:23 +0200 Received: from localhost (localhost [127.0.0.1]) by data.antarean.org (Postfix) with ESMTP id ABC7D16E8 for ; Mon, 17 Sep 2012 10:13:30 +0200 (CEST) X-Virus-Scanned: amavisd-new at antarean.org Received: from data.antarean.org ([127.0.0.1]) by localhost (data.antarean.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id OitlBgzgzOTb for ; Mon, 17 Sep 2012 10:13:28 +0200 (CEST) Received: from www.antarean.org (net.antarean.org [10.10.11.5]) by data.antarean.org (Postfix) with ESMTP id B1BC3902 for ; Mon, 17 Sep 2012 10:13:28 +0200 (CEST) Received: from 62.132.204.72 (SquirrelMail authenticated user joost) by www.antarean.org with HTTP; Mon, 17 Sep 2012 10:13:28 +0200 Message-ID: In-Reply-To: <505686EA.9060801@ajlc.waterloo.on.ca> References: <003601cd9430$a381db70$ea859250$@gmail.com> <1347818899.25803.75.camel@dagon.hellion.org.uk> <004e01cd9446$b7636b20$262a4160$@gmail.com> <5056603D.8030007@ajlc.waterloo.on.ca> <006701cd9477$0d045820$270d0860$@gmail.com> <505686EA.9060801@ajlc.waterloo.on.ca> Date: Mon, 17 Sep 2012 10:13:28 +0200 From: "J. Roeleveld" To: xen-users@lists.xen.org User-Agent: SquirrelMail/1.4.21 MIME-Version: 1.0 X-Priority: 3 (Normal) Importance: Normal X-Ziggo-spambar: - X-Ziggo-spamscore: -1.5 X-Ziggo-spamreport: BAYES_00=-1.9, FSL_RCVD_USER=0.001, RDNS_DYNAMIC=0.982, RP_MATCHES_RCVD=-0.538 X-Ziggo-Spam-Status: No X-Spam-Status: No X-Spam-Flag: No Subject: Re: [Xen-users] Setting up XEN domU causes RAID5 to fail? X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org On Mon, September 17, 2012 4:11 am, Tony Lill wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > When I tried to upgrade my xen systems to a pvops xen/linux combo, I > found that high disk I/O would cause disk errors and caused disks to > be thrown out of the raid and all sorts of other badness. High of > course, is a relative term. For one of my boxes, copying a large file > was enough, on another, it needed something like running backups on > several VMs simultaneously or trying to start my VM's while rebuilding > the raid. > > FWIW, I went back to Xen 3.4.4 and the SLES1 xenlinux kernel and > they've been rock solid. This could be related to Xen version, but can also be related to the use of desktop-drives in a RAID-configuration. Linux Software raid is more tolerant than hardware raid, but it still doesn't like it if a disk dissappears/fails/acts up and will then kick it out. I'm surprised there are no messages in the logs as I have always seen at least a message from the raid-stack when a disk was thrown out. Are those drives SMART-compliant? If yes, try running a self-test on those drives to see if there are any detectable problems. Other possible cause: The PSU can't handle the load of all the drives and the CPU going full speed. You could also try to do some heavy load on those drives by simultaneously copying "/dev/zero" to each of the drives. -- Joost _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Mon Sep 17 08:12:08 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Mon, 17 Sep 2012 08:12:08 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TDWQP-0007VC-Se; Mon, 17 Sep 2012 08:11:25 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TDWQO-0007V6-Ds for xen-users@lists.xen.org; Mon, 17 Sep 2012 08:11:24 +0000 Received: from [85.158.138.51:15841] by server-12.bemta-3.messagelabs.com id A5/98-10384-B2BD6505; Mon, 17 Sep 2012 08:11:23 +0000 X-Env-Sender: joost@antarean.org X-Msg-Ref: server-8.tower-174.messagelabs.com!1347869483!30774552!1 X-Originating-IP: [212.54.42.165] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogMjEyLjU0LjQyLjE2NSA9PiAxNDU3Mjk=\n X-StarScan-Received: X-StarScan-Version: 6.6.1.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 6475 invoked from network); 17 Sep 2012 08:11:23 -0000 Received: from smtpq2.tb.mail.iss.as9143.net (HELO smtpq2.tb.mail.iss.as9143.net) (212.54.42.165) by server-8.tower-174.messagelabs.com with SMTP; 17 Sep 2012 08:11:23 -0000 Received: from [212.54.42.134] (helo=smtp3.tb.mail.iss.as9143.net) by smtpq2.tb.mail.iss.as9143.net with esmtp (Exim 4.71) (envelope-from ) id 1TDWQN-0006cs-4f for xen-users@lists.xen.org; Mon, 17 Sep 2012 10:11:23 +0200 Received: from 54698b76.cm-12-2c.dynamic.ziggo.nl ([84.105.139.118] helo=data.antarean.org) by smtp3.tb.mail.iss.as9143.net with esmtp (Exim 4.71) (envelope-from ) id 1TDWQM-0005aE-1j for xen-users@lists.xen.org; Mon, 17 Sep 2012 10:11:23 +0200 Received: from localhost (localhost [127.0.0.1]) by data.antarean.org (Postfix) with ESMTP id ABC7D16E8 for ; Mon, 17 Sep 2012 10:13:30 +0200 (CEST) X-Virus-Scanned: amavisd-new at antarean.org Received: from data.antarean.org ([127.0.0.1]) by localhost (data.antarean.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id OitlBgzgzOTb for ; Mon, 17 Sep 2012 10:13:28 +0200 (CEST) Received: from www.antarean.org (net.antarean.org [10.10.11.5]) by data.antarean.org (Postfix) with ESMTP id B1BC3902 for ; Mon, 17 Sep 2012 10:13:28 +0200 (CEST) Received: from 62.132.204.72 (SquirrelMail authenticated user joost) by www.antarean.org with HTTP; Mon, 17 Sep 2012 10:13:28 +0200 Message-ID: In-Reply-To: <505686EA.9060801@ajlc.waterloo.on.ca> References: <003601cd9430$a381db70$ea859250$@gmail.com> <1347818899.25803.75.camel@dagon.hellion.org.uk> <004e01cd9446$b7636b20$262a4160$@gmail.com> <5056603D.8030007@ajlc.waterloo.on.ca> <006701cd9477$0d045820$270d0860$@gmail.com> <505686EA.9060801@ajlc.waterloo.on.ca> Date: Mon, 17 Sep 2012 10:13:28 +0200 From: "J. Roeleveld" To: xen-users@lists.xen.org User-Agent: SquirrelMail/1.4.21 MIME-Version: 1.0 X-Priority: 3 (Normal) Importance: Normal X-Ziggo-spambar: - X-Ziggo-spamscore: -1.5 X-Ziggo-spamreport: BAYES_00=-1.9, FSL_RCVD_USER=0.001, RDNS_DYNAMIC=0.982, RP_MATCHES_RCVD=-0.538 X-Ziggo-Spam-Status: No X-Spam-Status: No X-Spam-Flag: No Subject: Re: [Xen-users] Setting up XEN domU causes RAID5 to fail? X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org On Mon, September 17, 2012 4:11 am, Tony Lill wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > When I tried to upgrade my xen systems to a pvops xen/linux combo, I > found that high disk I/O would cause disk errors and caused disks to > be thrown out of the raid and all sorts of other badness. High of > course, is a relative term. For one of my boxes, copying a large file > was enough, on another, it needed something like running backups on > several VMs simultaneously or trying to start my VM's while rebuilding > the raid. > > FWIW, I went back to Xen 3.4.4 and the SLES1 xenlinux kernel and > they've been rock solid. This could be related to Xen version, but can also be related to the use of desktop-drives in a RAID-configuration. Linux Software raid is more tolerant than hardware raid, but it still doesn't like it if a disk dissappears/fails/acts up and will then kick it out. I'm surprised there are no messages in the logs as I have always seen at least a message from the raid-stack when a disk was thrown out. Are those drives SMART-compliant? If yes, try running a self-test on those drives to see if there are any detectable problems. Other possible cause: The PSU can't handle the load of all the drives and the CPU going full speed. You could also try to do some heavy load on those drives by simultaneously copying "/dev/zero" to each of the drives. -- Joost _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Mon Sep 17 08:55:23 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Mon, 17 Sep 2012 08:55:23 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TDX6I-0000AC-R8; Mon, 17 Sep 2012 08:54:42 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TDX6G-00009y-Pt for xen-users@lists.xen.org; Mon, 17 Sep 2012 08:54:41 +0000 Received: from [85.158.138.51:44952] by server-10.bemta-3.messagelabs.com id DB/EF-10411-F45E6505; Mon, 17 Sep 2012 08:54:39 +0000 X-Env-Sender: Ian.Campbell@citrix.com X-Msg-Ref: server-15.tower-174.messagelabs.com!1347872079!29047183!1 X-Originating-IP: [62.200.22.115] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogNjIuMjAwLjIyLjExNSA9PiAxMDk2Mzg=\n X-StarScan-Received: X-StarScan-Version: 6.6.1.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 308 invoked from network); 17 Sep 2012 08:54:39 -0000 Received: from smtp.eu.citrix.com (HELO SMTP.EU.CITRIX.COM) (62.200.22.115) by server-15.tower-174.messagelabs.com with RC4-SHA encrypted SMTP; 17 Sep 2012 08:54:39 -0000 X-IronPort-AV: E=Sophos;i="4.80,434,1344211200"; d="scan'208";a="14573489" Received: from lonpmailmx01.citrite.net ([10.30.203.162]) by LONPIPO01.EU.CITRIX.COM with ESMTP/TLS/RC4-MD5; 17 Sep 2012 08:54:38 +0000 Received: from [10.80.2.42] (10.80.2.42) by LONPMAILMX01.citrite.net (10.30.203.162) with Microsoft SMTP Server id 8.3.279.1; Mon, 17 Sep 2012 09:54:39 +0100 Message-ID: <1347872077.14977.23.camel@zakaz.uk.xensource.com> From: Ian Campbell To: Adam Goryachev Date: Mon, 17 Sep 2012 09:54:37 +0100 In-Reply-To: <505344E8.2030400@websitemanagers.com.au> References: <5051D0C5.5070600@websitemanagers.com.au> <1347609879.24226.148.camel@zakaz.uk.xensource.com> <50532CE9.5080601@websitemanagers.com.au> <1347629416.24226.208.camel@zakaz.uk.xensource.com> <505344E8.2030400@websitemanagers.com.au> Organization: Citrix Systems, Inc. X-Mailer: Evolution 3.4.3-1 MIME-Version: 1.0 Cc: "xen-users@lists.xen.org" Subject: Re: [Xen-users] Poor Windows 2003 + GPLPV performance compared to VMWare X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org On Fri, 2012-09-14 at 15:53 +0100, Adam Goryachev wrote: > On 14/09/12 23:30, Ian Campbell wrote: > > http://xenbits.xen.org/docs/4.2-testing/ has man pages for the config > > files. These are also installed on the host as part of the build. > > > > If you are using xend then the xm ones are a bit lacking. However xl is > > mostly compatible with xm so the xl manpages largely apply. There's also > > a bunch of stuff on http://wiki.xen.org/wiki. > > Thanks for the pointer, I'm using 4.1 though, but I guess most of it > will still be the same. Right. > > > You have: > > cpus = "2,3,4,5" > > which means "let all the guests VCPUs run on any of PCPUS 2-5". > > > > It sounds like what you are asking for above is: > > cpus = [2,3,4,5] > > Which forces guest vcpu0=>pcpu=2, 1=>3, 2=>4 and 3=>5. > > > > Subtle I agree. > > Ugh... ok, I'll give that a try. BTW, it would seem this is different > from xen 4.0 (from debian stable) where it seems to magically do what I > meant to say, or I'm just lucky on those machines :) It's not impossible, xend is largely unmaintained but it does get occasional "obvious" fixes (which sometimes turn out not to be so obvious) > > Do you have a specific reason for pinning? I'd be tempted to just let > > the scheduler do its thing unless/until you determine that it is causing > > problems. > > The only reason for pinning is: > a) To stop the scheduler from moving the vCPU around on the pCPU, from > my understanding this improves performance It can, it can also cause the opposite if not used carefully. I'm no expert on scheduling vs. pinning but one thing to watch for in particular is the relationship between dom0 and guest VCPUs when pinning one or both of them. Depending on the workload either putting them on the same or distinct sets of pCPUs can be beneficial. I've also heard that mixing pinned and unpinned VCPUs on a pCPU can cause unexpected behaviours. > b) when running multiple DOMU, I either want a bunch of DOMU to share > one cpu, while I want one or more dedicated CPU other DOMU. (ie, I use > this as a type of prioritisation/performance tuning. You might find cpupools in 4.1+ quite handy for managing this. > In this case, there is only a single VM, though if some hardware is lost > (other physical machines) then will end up with multiple VM's... Don't forget that dom0 counts as a VM as well. Ian. _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Mon Sep 17 08:55:23 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Mon, 17 Sep 2012 08:55:23 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TDX6I-0000AC-R8; Mon, 17 Sep 2012 08:54:42 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TDX6G-00009y-Pt for xen-users@lists.xen.org; Mon, 17 Sep 2012 08:54:41 +0000 Received: from [85.158.138.51:44952] by server-10.bemta-3.messagelabs.com id DB/EF-10411-F45E6505; Mon, 17 Sep 2012 08:54:39 +0000 X-Env-Sender: Ian.Campbell@citrix.com X-Msg-Ref: server-15.tower-174.messagelabs.com!1347872079!29047183!1 X-Originating-IP: [62.200.22.115] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogNjIuMjAwLjIyLjExNSA9PiAxMDk2Mzg=\n X-StarScan-Received: X-StarScan-Version: 6.6.1.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 308 invoked from network); 17 Sep 2012 08:54:39 -0000 Received: from smtp.eu.citrix.com (HELO SMTP.EU.CITRIX.COM) (62.200.22.115) by server-15.tower-174.messagelabs.com with RC4-SHA encrypted SMTP; 17 Sep 2012 08:54:39 -0000 X-IronPort-AV: E=Sophos;i="4.80,434,1344211200"; d="scan'208";a="14573489" Received: from lonpmailmx01.citrite.net ([10.30.203.162]) by LONPIPO01.EU.CITRIX.COM with ESMTP/TLS/RC4-MD5; 17 Sep 2012 08:54:38 +0000 Received: from [10.80.2.42] (10.80.2.42) by LONPMAILMX01.citrite.net (10.30.203.162) with Microsoft SMTP Server id 8.3.279.1; Mon, 17 Sep 2012 09:54:39 +0100 Message-ID: <1347872077.14977.23.camel@zakaz.uk.xensource.com> From: Ian Campbell To: Adam Goryachev Date: Mon, 17 Sep 2012 09:54:37 +0100 In-Reply-To: <505344E8.2030400@websitemanagers.com.au> References: <5051D0C5.5070600@websitemanagers.com.au> <1347609879.24226.148.camel@zakaz.uk.xensource.com> <50532CE9.5080601@websitemanagers.com.au> <1347629416.24226.208.camel@zakaz.uk.xensource.com> <505344E8.2030400@websitemanagers.com.au> Organization: Citrix Systems, Inc. X-Mailer: Evolution 3.4.3-1 MIME-Version: 1.0 Cc: "xen-users@lists.xen.org" Subject: Re: [Xen-users] Poor Windows 2003 + GPLPV performance compared to VMWare X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org On Fri, 2012-09-14 at 15:53 +0100, Adam Goryachev wrote: > On 14/09/12 23:30, Ian Campbell wrote: > > http://xenbits.xen.org/docs/4.2-testing/ has man pages for the config > > files. These are also installed on the host as part of the build. > > > > If you are using xend then the xm ones are a bit lacking. However xl is > > mostly compatible with xm so the xl manpages largely apply. There's also > > a bunch of stuff on http://wiki.xen.org/wiki. > > Thanks for the pointer, I'm using 4.1 though, but I guess most of it > will still be the same. Right. > > > You have: > > cpus = "2,3,4,5" > > which means "let all the guests VCPUs run on any of PCPUS 2-5". > > > > It sounds like what you are asking for above is: > > cpus = [2,3,4,5] > > Which forces guest vcpu0=>pcpu=2, 1=>3, 2=>4 and 3=>5. > > > > Subtle I agree. > > Ugh... ok, I'll give that a try. BTW, it would seem this is different > from xen 4.0 (from debian stable) where it seems to magically do what I > meant to say, or I'm just lucky on those machines :) It's not impossible, xend is largely unmaintained but it does get occasional "obvious" fixes (which sometimes turn out not to be so obvious) > > Do you have a specific reason for pinning? I'd be tempted to just let > > the scheduler do its thing unless/until you determine that it is causing > > problems. > > The only reason for pinning is: > a) To stop the scheduler from moving the vCPU around on the pCPU, from > my understanding this improves performance It can, it can also cause the opposite if not used carefully. I'm no expert on scheduling vs. pinning but one thing to watch for in particular is the relationship between dom0 and guest VCPUs when pinning one or both of them. Depending on the workload either putting them on the same or distinct sets of pCPUs can be beneficial. I've also heard that mixing pinned and unpinned VCPUs on a pCPU can cause unexpected behaviours. > b) when running multiple DOMU, I either want a bunch of DOMU to share > one cpu, while I want one or more dedicated CPU other DOMU. (ie, I use > this as a type of prioritisation/performance tuning. You might find cpupools in 4.1+ quite handy for managing this. > In this case, there is only a single VM, though if some hardware is lost > (other physical machines) then will end up with multiple VM's... Don't forget that dom0 counts as a VM as well. Ian. _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Mon Sep 17 08:55:23 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Mon, 17 Sep 2012 08:55:23 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TDX6C-00009p-6u; Mon, 17 Sep 2012 08:54:36 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TDX6B-00009k-3m for xen-users@lists.xen.org; Mon, 17 Sep 2012 08:54:35 +0000 Received: from [85.158.138.51:25219] by server-11.bemta-3.messagelabs.com id 56/29-30250-A45E6505; Mon, 17 Sep 2012 08:54:34 +0000 X-Env-Sender: Ian.Campbell@citrix.com X-Msg-Ref: server-2.tower-174.messagelabs.com!1347872073!30807979!1 X-Originating-IP: [62.200.22.115] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogNjIuMjAwLjIyLjExNSA9PiAxMDk2Mzg=\n X-StarScan-Received: X-StarScan-Version: 6.6.1.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 17415 invoked from network); 17 Sep 2012 08:54:33 -0000 Received: from smtp.ctxuk.citrix.com (HELO SMTP.EU.CITRIX.COM) (62.200.22.115) by server-2.tower-174.messagelabs.com with RC4-SHA encrypted SMTP; 17 Sep 2012 08:54:33 -0000 X-IronPort-AV: E=Sophos;i="4.80,434,1344211200"; d="scan'208";a="14573487" Received: from lonpmailmx01.citrite.net ([10.30.203.162]) by LONPIPO01.EU.CITRIX.COM with ESMTP/TLS/RC4-MD5; 17 Sep 2012 08:54:33 +0000 Received: from [10.80.2.42] (10.80.2.42) by LONPMAILMX01.citrite.net (10.30.203.162) with Microsoft SMTP Server id 8.3.279.1; Mon, 17 Sep 2012 09:54:33 +0100 Message-ID: <1347872072.14977.22.camel@zakaz.uk.xensource.com> From: Ian Campbell To: Adam Goryachev Date: Mon, 17 Sep 2012 09:54:32 +0100 In-Reply-To: <1347629416.24226.208.camel@zakaz.uk.xensource.com> References: <5051D0C5.5070600@websitemanagers.com.au> <1347609879.24226.148.camel@zakaz.uk.xensource.com> <50532CE9.5080601@websitemanagers.com.au> <1347629416.24226.208.camel@zakaz.uk.xensource.com> Organization: Citrix Systems, Inc. X-Mailer: Evolution 3.4.3-1 MIME-Version: 1.0 Cc: "xen-users@lists.xen.org" Subject: Re: [Xen-users] Poor Windows 2003 + GPLPV performance compared to VMWare X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org On Fri, 2012-09-14 at 14:30 +0100, Ian Campbell wrote: > > > Does your system have any NUMA properties? > > > > I don't really understand this question.... is there a simple method to > > check? It is a AMD Phenom(tm) II X6 1100T Processor on a reasonable > > desktop motherboard, nothing fancy.... I don't have a NUMA system to hand, but on my non-NUMA system I see in the logs: (XEN) No NUMA configuration found You should see that or something more informative. Also at least in 4.2 "xl info -n" gives some details. Not sure if xm has the same option? Ian. _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Mon Sep 17 08:55:23 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Mon, 17 Sep 2012 08:55:23 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TDX6C-00009p-6u; Mon, 17 Sep 2012 08:54:36 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TDX6B-00009k-3m for xen-users@lists.xen.org; Mon, 17 Sep 2012 08:54:35 +0000 Received: from [85.158.138.51:25219] by server-11.bemta-3.messagelabs.com id 56/29-30250-A45E6505; Mon, 17 Sep 2012 08:54:34 +0000 X-Env-Sender: Ian.Campbell@citrix.com X-Msg-Ref: server-2.tower-174.messagelabs.com!1347872073!30807979!1 X-Originating-IP: [62.200.22.115] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogNjIuMjAwLjIyLjExNSA9PiAxMDk2Mzg=\n X-StarScan-Received: X-StarScan-Version: 6.6.1.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 17415 invoked from network); 17 Sep 2012 08:54:33 -0000 Received: from smtp.ctxuk.citrix.com (HELO SMTP.EU.CITRIX.COM) (62.200.22.115) by server-2.tower-174.messagelabs.com with RC4-SHA encrypted SMTP; 17 Sep 2012 08:54:33 -0000 X-IronPort-AV: E=Sophos;i="4.80,434,1344211200"; d="scan'208";a="14573487" Received: from lonpmailmx01.citrite.net ([10.30.203.162]) by LONPIPO01.EU.CITRIX.COM with ESMTP/TLS/RC4-MD5; 17 Sep 2012 08:54:33 +0000 Received: from [10.80.2.42] (10.80.2.42) by LONPMAILMX01.citrite.net (10.30.203.162) with Microsoft SMTP Server id 8.3.279.1; Mon, 17 Sep 2012 09:54:33 +0100 Message-ID: <1347872072.14977.22.camel@zakaz.uk.xensource.com> From: Ian Campbell To: Adam Goryachev Date: Mon, 17 Sep 2012 09:54:32 +0100 In-Reply-To: <1347629416.24226.208.camel@zakaz.uk.xensource.com> References: <5051D0C5.5070600@websitemanagers.com.au> <1347609879.24226.148.camel@zakaz.uk.xensource.com> <50532CE9.5080601@websitemanagers.com.au> <1347629416.24226.208.camel@zakaz.uk.xensource.com> Organization: Citrix Systems, Inc. X-Mailer: Evolution 3.4.3-1 MIME-Version: 1.0 Cc: "xen-users@lists.xen.org" Subject: Re: [Xen-users] Poor Windows 2003 + GPLPV performance compared to VMWare X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org On Fri, 2012-09-14 at 14:30 +0100, Ian Campbell wrote: > > > Does your system have any NUMA properties? > > > > I don't really understand this question.... is there a simple method to > > check? It is a AMD Phenom(tm) II X6 1100T Processor on a reasonable > > desktop motherboard, nothing fancy.... I don't have a NUMA system to hand, but on my non-NUMA system I see in the logs: (XEN) No NUMA configuration found You should see that or something more informative. Also at least in 4.2 "xl info -n" gives some details. Not sure if xm has the same option? Ian. _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Mon Sep 17 11:33:11 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Mon, 17 Sep 2012 11:33:11 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TDZYj-000557-NN; Mon, 17 Sep 2012 11:32:13 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TDZYh-00054o-Up for xen-users@lists.xen.org; Mon, 17 Sep 2012 11:32:12 +0000 Received: from [85.158.143.35:23491] by server-3.bemta-4.messagelabs.com id 77/0D-08232-A3A07505; Mon, 17 Sep 2012 11:32:10 +0000 X-Env-Sender: lars.kurth.xen@gmail.com X-Msg-Ref: server-10.tower-21.messagelabs.com!1347881511!10495837!1 X-Originating-IP: [209.85.214.45] X-SpamReason: No, hits=0.9 required=7.0 tests=BODY_RANDOM_LONG, HTML_30_40, HTML_MESSAGE, ML_RADAR_SPEW_LINKS_16, RCVD_BY_IP, spamassassin: X-StarScan-Received: X-StarScan-Version: 6.6.1.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 22698 invoked from network); 17 Sep 2012 11:31:53 -0000 Received: from mail-bk0-f45.google.com (HELO mail-bk0-f45.google.com) (209.85.214.45) by server-10.tower-21.messagelabs.com with RC4-SHA encrypted SMTP; 17 Sep 2012 11:31:53 -0000 Received: by bkcji1 with SMTP id ji1so2152604bkc.32 for ; Mon, 17 Sep 2012 04:31:51 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=sender:message-id:date:from:reply-to:user-agent:mime-version:to :subject:content-type; bh=O9f1qgevS4UMn+byKYSSZLXZAdF/aJIKWb5QlG2QyrU=; b=A2hyECCMOXB2mvalKzBIBl3QQM8FBp4t4drCSaJ9rPEbi/gEzbmFhI0HsZB7bCWL08 VCxwm9kSNU1V/cugqwbe+IZH/7oQCKPm+TPRjmMiSsVMUSYak+grmS6gNev5rL60ctwK jQo42C1vJ2K/PWr2Mw4y6JW9qay5T/1nJjbiN+Miqx7pvFgfPLd0YRFyyh5QasI0f6o8 f0AZfliV6bLpYk20Uo9XF2LX0KbWVm1Ow0LSJyquL6dw4voxXnagkVRdV6If6pBXV8nC HTB9LaGxKxOJDwVjzSM0vJvX3t1oGhP/APKud7Fb/cUawOkeiAjNhI7f5u+009xRp6xz l6ig== Received: by 10.205.120.16 with SMTP id fw16mr4054797bkc.102.1347881510902; Mon, 17 Sep 2012 04:31:50 -0700 (PDT) Received: from [172.16.26.11] (b0fb5b35.bb.sky.com. [176.251.91.53]) by mx.google.com with ESMTPS id n5sm5166099bkv.14.2012.09.17.04.31.49 (version=SSLv3 cipher=OTHER); Mon, 17 Sep 2012 04:31:50 -0700 (PDT) Message-ID: <50570A24.2000905@xen.org> Date: Mon, 17 Sep 2012 12:31:48 +0100 From: Lars Kurth User-Agent: Mozilla/5.0 (Windows NT 6.1; rv:15.0) Gecko/20120907 Thunderbird/15.0.1 MIME-Version: 1.0 To: xen-users@lists.xen.org, xen-announce@lists.xen.org Subject: [Xen-users] Xen 4.2.0 Released! X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list Reply-To: lars.kurth@xen.org List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============1086458984947120423==" Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org This is a multi-part message in MIME format. --===============1086458984947120423== Content-Type: multipart/alternative; boundary="------------010702040202080003090402" This is a multi-part message in MIME format. --------------010702040202080003090402 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 8bit Dear Community Members, Xen.org is pleased to announce the release of Xen 4.2.0. The release is available from the download page: * *Xen Hypervisor 4.2.0*: Download (archives ), Source (tag RELEASE-4.2.0) This release is the culmination of 18 months and almost 2900 commits and almost 300K lines of code of development effort, by 124 individuals from 43 organizations. New Features The release incorporates many new features and improvements to existing features. There are improvements across the board including to Security, Scalability, Performance and Documentation. *XL is now the default toolstack*: Significant effort has gone in to the XL tool toolstack in this release and it is now feature complete and robust enough that we have made it the default. This toolstack can now replace xend in the majority of deployments, see XL vs Xend Feature Comparison . As well as improving XL the underlying libxl library has been significantly improved and supports the majority of the most common toolstack features. In addition the API has been declared stable which should make it even easier for external toolstack such as libvirt and XCP's xapi to make full use of this functionality in the future. *Large Systems*: Following on from the improvements made in 4.1 Xen now supports even larger systems, with up to 4095 host CPUs and up to 512 guest CPUs. In addition toolstack feature like the ability to automatically create a CPUPOOL per NUMA node and more intelligent placement of guest VCPUs on NUMA nodes have further improved the Xen experience on large systems. Other new features, such as multiple PCI segment support have also made a positive impact on such systems. *Improved security*: The XSM/Flask subsystem has seen several enhancements, including improved support for disaggregated systems and a rewritten example policy which is clearer and simpler to modify to suit local requirements. *Documentation*: The Xen documentation has been much improved, both the wiki . This is in no small part down to the success of the Xen Document Days so thanks to all who have taken part. You can find more information in the release notes and feature list on the wiki. Upstreaming The Xen project continues to work closely with our upstreams. Of particular note in this release cycle is the upstreaming of the HVM device model support into upstream qemu . After the Linux dom0 support (merged upstream in 3.0 in the 4.1 release cycle) the qemu-derived device model was the largest remaining piece of code which required upstreaming. Support for Xen was merged into upstream prior to the qemu 0.15 release and is supported as an option using the XL toolstack. It will become the default in 4.3. Alongside this support we have also gained support for SeaBIOS (a cleaner and more maintainable legacy BIOS, used by default when upstream qemu is selected) and Tianocore/OVMF (a UEFI BIOS). Support for Xen has been merged into the upstreams of both of these projects during the Xen 4.2 development cycle. More Information Links to useful wiki pages and other resources can be found on the Xen support page . Thanks Contributions were made to this release by 124 individuals from 43 organizations, and that's not counting contributions to external projects such as the BSDs, Linux or qemu. Many thanks to everyone who contributed to this release, either through code, testing, documentation or in any other way. The diagram below shows organisations which contributed more than 1% in lines of code to the Xen 4.2 release. Several items in the diagram discribe groups of people or organisations: /Individual/ covers contributions by individuals whose affiliation is unknown, /Misc/ covers contributions by commercial organisations which did not go above 1% individually and /University/ covers contributions by Universities which did not go above 1% individually. Xen 4.2 Contribution Stats I did also want to list the top 20 contributors to Xen 4.2 (in terms of commits/and lines of code). These are: * Jan Beulich (338 commits/40357 LOC) * Roger Pau Monne (87/36932) * Ian Campbell (504/32009) * Stefano Stabellini (124/29130) * Ian Jackson (174/27900) * Daniel De Graaf (79/11103) * David Vrabel (45/11075 * Tim Deegan (143/8790) * Christoph Egger (67/8590) * Matt Wilson (9/8508) * Andrés Lagar-Cavilla (115/8050) * Keir Fraser (143/5593) * Wei Wang (34/5577) * Anthony Perard (45/5289) * Olaf Hering (154/4296) * Qing He (20/4179) * George Dunlap (75/4088) * Dario Faggioli (30/3742) * Shriram Rajagopalan (21/3481) * Jonathan Davies (3/3230) For a complete breakdown see the Acknowledgement page . A big thank you again! Best Regards Lars --------------010702040202080003090402 Content-Type: multipart/related; boundary="------------040701070906020708020505" --------------040701070906020708020505 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit

Dear Community Members,

Xen.org is pleased to announce the release of Xen 4.2.0. The release is available from the download page:

This release is the culmination of 18 months and almost 2900 commits and almost 300K lines of code of development effort, by 124 individuals from 43 organizations.

New Features

The release incorporates many new features and improvements to existing features. There are improvements across the board including to Security, Scalability, Performance and Documentation.

XL is now the default toolstack: Significant effort has gone in to the XL tool toolstack in this release and it is now feature complete and robust enough that we have made it the default. This toolstack can now replace xend in the majority of deployments, see XL vs Xend Feature Comparison. As well as improving XL the underlying libxl library has been significantly improved and supports the majority of the most common toolstack features. In addition the API has been declared stable which should make it even easier for external toolstack such as libvirt and XCP’s xapi to make full use of this functionality in the future.

Large Systems: Following on from the improvements made in 4.1 Xen now supports even larger systems, with up to 4095 host CPUs and up to 512 guest CPUs. In addition toolstack feature like the ability to automatically create a CPUPOOL per NUMA node and more intelligent placement of guest VCPUs on NUMA nodes have further improved the Xen experience on large systems. Other new features, such as multiple PCI segment support have also made a positive impact on such systems.

Improved security: The XSM/Flask subsystem has seen several enhancements, including improved support for disaggregated systems and a rewritten example policy which is clearer and simpler to modify to suit local requirements.

Documentation: The Xen documentation has been much improved, both the wiki. This is in no small part down to the success of the Xen Document Days so thanks to all who have taken part.

You can find more information in the release notes and feature list on the wiki.

Upstreaming

The Xen project continues to work closely with our upstreams.

Of particular note in this release cycle is the upstreaming of the HVM device model support into upstream qemu. After the Linux dom0 support (merged upstream in 3.0 in the 4.1 release cycle) the qemu-derived device model was the largest remaining piece of code which required upstreaming. Support for Xen was merged into upstream prior to the qemu 0.15 release and is supported as an option using the XL toolstack. It will become the default in 4.3. Alongside this support we have also gained support for SeaBIOS (a cleaner and more maintainable legacy BIOS, used by default when upstream qemu is selected) and Tianocore/OVMF (a UEFI BIOS). Support for Xen has been merged into the upstreams of both of these projects during the Xen 4.2 development cycle.

More Information

Links to useful wiki pages and other resources can be found on the Xen support page.

Thanks

Contributions were made to this release by 124 individuals from 43 organizations, and that’s not counting contributions to external projects such as the BSDs, Linux or qemu. Many thanks to everyone who contributed to this release, either through code, testing, documentation or in any other way.

The diagram below shows organisations which contributed more than 1% in lines of code to the Xen 4.2 release. Several items in the diagram discribe groups of people or organisations: Individual covers contributions by individuals whose affiliation is unknown, Misc covers contributions by commercial organisations which did not go above 1% individually and University covers contributions by Universities which did not go above 1% individually.

Xen 4.2 Contribution Stats

I did also want to list the top 20 contributors to Xen 4.2 (in terms of commits/and lines of code). These are:

  • Jan Beulich (338 commits/40357 LOC)
  • Roger Pau Monne (87/36932)
  • Ian Campbell (504/32009)
  • Stefano Stabellini (124/29130)
  • Ian Jackson (174/27900)
  • Daniel De Graaf (79/11103)
  • David Vrabel (45/11075
  • Tim Deegan (143/8790)
  • Christoph Egger (67/8590)
  • Matt Wilson (9/8508)
  • Andrés Lagar-Cavilla (115/8050)
  • Keir Fraser (143/5593)
  • Wei Wang (34/5577)
  • Anthony Perard (45/5289)
  • Olaf Hering (154/4296)
  • Qing He (20/4179)
  • George Dunlap (75/4088)
  • Dario Faggioli (30/3742)
  • Shriram Rajagopalan (21/3481)
  • Jonathan Davies (3/3230)

For a complete breakdown see the Acknowledgement page. A big thank you again!

Best Regards
Lars

--------------040701070906020708020505 Content-Type: image/png; name="Contribution-stats2.png" Content-Transfer-Encoding: base64 Content-ID: Content-Disposition: inline; filename="Contribution-stats2.png" iVBORw0KGgoAAAANSUhEUgAAAiUAAAHFCAIAAACiox6jAAAAAXNSR0IArs4c6QAAAARnQU1B AACxjwv8YQUAAAAJcEhZcwAADsMAAA7DAcdvqGQAAAAadEVYdFNvZnR3YXJlAFBhaW50Lk5F VCB2My41LjEwMPRyoQAAa3ZJREFUeF7tvXlwFde16M3/r24q+ePWu7deqpKbSt3cylDlm9RL mffl+jp+uY6f4ziO4xib2DFxsAgeGBwMBDAyxgyWkAUIEEITiEHMEtYEYtDIKEDGDAIkTIxj Y8c2+BowFsLmW3326T67593du3fv7l6qU3B0tHsPq7vX76y1V6817Bb+oARQAigBlABKIHwJ DAt/CBwBJYASQAmgBFACt5A3eBGgBFACKAGUgAgJIG9ESBnHQAmgBFACKAHkDV4DKAGUAEoA JSBCAsgbEVLGMVACKAGUAEoAeYPXAEoAJYASQAmIkADyRoSUcQyUAEoAJYASQN7gNYASQAmg BFACIiSAvBEhZRwDJYASQAmgBJA3eA2gBFACKAGUgAgJIG9ESBnHQAmgBFACKAHkDV4DKAGU AEoAJSBCAmnkTX/x8GGZn+HF/UTG5k/CkL2YUcKYOfapSUDYSRQ2EOeTq82bvsE4j+HSXVxF J1ZKkYwWEm/oi47o9rzmSNZnNWhzHplSblJiLlDzuNKIJMBEcqvS8G2AuNBzr7vyDDOyWGVu 9oavIHYS4XkStb6sbg6eAwU4vd4ONd73znd9WFpCzO3sTTLYOiMB/rwxX0Sqdne/+/2cFO8X V+j2jc2UvM/UjzyYjuE5FeqE0+pF05fhnHabZer54Ti0ETXqZZoze63G4Ck5R97wHIjpmuDQ iH3OoWoJ9mlwWDN24UUCnHlDX0a67zbKrRWO4uFxcfHog5I65+68nE/GtnxnaGHi5C4EkYZt diLDhxsdpnZmbu6S1ClAQXN25A3jmZSqmboglzs9bC3B9+qWSsJxnwxX3th80w1XRjwuLh59 pJg3t24ZnT+RGDfZszi8uNm0QcdyCVJXbzjfjEyTSBpv2G6j8LUE2zxYrglsw1kCPHnj7Tut yaK2cf9nvmvSvg+qnaVLJPt39bsuxAQY7msXf5quU903Xe1Ak+mWiz5wmJLtbcBDFNnrwtCV 88aA5kEy2J5u87G4BnVKxPFCMAhIf9bVI51Out0dkO0YDvWnb9h4Y3/xeJ+zR3+aN+E4ylmR IcOlohO141Vh+qMuHofuh6+WID0b1IPt+XeVCWftit0ZJcCRN7kLyfXrIYvrXO1Oc45Q2lHd gWbhjepbycUHOPCGHsO87RQGb3iJwqxADDER2pl3Epr+1tVJw+2kWnRrop3NYnPtWE669U2s GTcQchiYNw7+NPuLx+lCtZ6zT964D8QsZ/31br9s16uUmTectYQJm7bXrKtMEA4CJMCRN0af iu3sLRpaXIX0FazqOqvvRnbKxer6IjeUC2+yd53uGztZCwtvrAfQH55T3TxFYeE8Vz6yVCLu QtMOY1cQLt8eLcY0KVzWk268tjROZSLcffGGmr3T9o3zxeN0oZrvB5+8oU0HizuCQc5eLhWd +eB8VbDIPTQtoYreYOsY7lyLW0/QZp0AZR6DIcTzxuaiNN04lu0sPnRXncZABSeVQX+Lt5+S gz/NC2/4isJCidhegNYjs87HrlsdcIz2kCWsjR+ynnTDDNSBjV8V3GyyXDfU1J0Pcrh4LK8d p9788sZxIBY5e7lU7OjNRjrTpcLIG8ZL0bqZNoYJ//SNa/3tMQY6O85TFM8bu5vMeJG4XErm b1qGO9v+ZmZUGZRvKds1b/uGsyj09oWj2mQVLrm0Tfev5RVvMij1M7B1ydBPQnmbV3YaeuPG h31DW1Vu33ZZLx5HlmQnzoM3xs1J3V6G2T2cXZ6HS8U0gHryzVcFR/uG8dawbmaaB9O1F2c1 Hpu5c+RN7q51UnW216TxD6yqx9W+MWkQVpVh+mbHmTfcRWHcArZ/wtubHcGiR6ivu3mm52lp BlhtkWleP9aTTt1fFieFZb4+TBsbp6iPOYfIG5qdFqK2cIi5PB7HfJWy+TG5agk3K8j4PdHx 2ouNzo7zRDnyxhQUay0X128ujk4R89Eh8sbW5OLkT+MtClXgep1j9Y3dm45k+K6uE5WVTmFj gLd56Y0va2XiktrCi2kTL96w+RLdLxV3+8bV1aBTBGwONcZbg82+Ybv24qzGYzN3nryhgONw sTN+J7FxG4fMG93uOvWVnSTjsZy6hbMp2BLNw/jQwpQXzOpcWPfIOm93p7yFUmFyyvlYqcsX eo03VsYp5Wdx86OZWK6J1cecQ7RvGJ2f+lOoysHytmW/Ktj0ek7owbWE5UVl/rrDdO3FRmfH eaJceaOLpjV7703Wba6JxTdi5tvY5quQ/Zdyc886nWWKT3MIJ6Mdw9SC2b520bGcwUWRWQOl NZ1vfpcZUiEW7g4QR3Mm15ONnlE+5qC76ZvQaunUKTYHILLZArGwb+h7ULcsSs7eLhXKS+t4 lbL50xQhUndNUC1hvqgsb0mWay/Oajw2c+fMG8dweLNWMblAXPWllZ6kr7DcloUf3rg+2WD1 ZVo9iL51LKfkogYNwvAqCpvv+Xaq1FpoFjtA6rTsDAA7Hlnc4oYxcwuOgje2k8lMy5ZADl9W TOqdjoSw0gi2U1BkHWAgNzl7vFScbmrdVcFm3+g8BWYnqDctYf3AmMUt6SaT2GjseE+UO2/0 XwJzl5Prs3/GO5zZvqEdXbmHOm3dzk53su4+t1E7ZlsoeynrF2BhMtnejsZ7wa8ojHrE+Wu7 lVFHLma3+VjaEqYHfaxBZNJ1ukl6Oen2N55lL9qHliFaRr0XKW8ygwfgjaVGd7g8nfiak7L7 VcHOG25awtxR5vRa3pLmL1Me7Np4q3lpZh8Ob6RZHk4EJYASQAmgBCSRAPJGkhOB00AJoARQ AgmXAPIm4ScYl4cSQAmgBCSRAPJGkhOB00AJoARQAgmXAPIm4ScYl4cSQAmgBCSRAPJGkhOB 00AJoARQAgmXAPIm4ScYl4cSQAmgBCSRAPJGkhOB00AJoARQAgmXAPIm4ScYl4cSQAmgBCSR APJGkhOB00AJoARQAgmXAPIm4ScYl4cSQAmgBCSRAPJGkhOB00AJoARQAgmXAPIm4ScYl4cS QAmgBCSRAPJGkhOB00AJoARQAgmXAPIm4ScYl4cSQAmgBCSRAPJGkhOB00AJoARQAgmXAPIm 4ScYl4cSQAmgBCSRAPJGkhOB00AJoARQAgmXAPIm4Sc4jsv74sub/33t7/Trw/++cOHvJ7VX deMRy9fa7W/0nnmPvD7+78/iuHacM0ogwRJA3iT45Mq4NMKSy1cuEnicfLsDXvtObfb0unNs Bfvr7nHVE4qb4DVj+U6glMakwRs3ZRQQzgklkFwJIG+Se24jXdnQzRvAlY8/fRegcv79YwCV 4+f3eIKKQ2N22Li2HD2nDlC0or5n0+7jaBVFesng4MmXAPIm+edYzAqvXr/8weW/vnXxKEeu 2CHHlSJBGhB7aH5NJxhDF3t7B69cESNAHAUlkHgJIG8Sf4rDWuDnN67Btsrbfz8OtsuBvjpe tgtLP0Fwwn7so8+XV/30DnhtfPTh3S9OP7qyCvBzc3AwLIFivyiBpEsAeZP0M8xvfTeGrpN9 l1MXug+d2cYChpDasDMjSMtZ05cS3hheW554rH32rL5t9Z+8/TY/6WJPKIHkSwB5k/xzHGSF wBjwkp3928Ej/S0hwcNHt0Eown5sxfT5lryhPwTTp+vVeWdbmq9cvBhEzngsSiANEkDepOEs e14jbMb87cPTx97a5QMGAg5hZ0aQlhsmvuDKG7oB2D37iovO7d6FPjfPFxwekA4JIG/ScZ4Z VgmRyhBOBhv+PWcbBTAjyBBmivx0bIWPlzONNoz6vSfe0I1bp7wADjc0ehiuO2ySIgkgb1J0 si2XCtv+Fy+dgy2ZIAAQfKwA3vy/5yp8w8Zg9BxcWgIPGqX9OsP1owRu3ULepPQq+PSzj+Gx mN5zOwSjgstwAngzfuoKLrzROqn9zQPgbYMIt5RecLhslADyJm3XAOz/w8aMVJv/PggkgDcL X1zIlzdabxBiABbPx/39abv2cL0oAbRv0nINwLMy8XKaecovQDZvfvx/vjUs+/Otb48kOzrj /5l88t3x2Q2ekSO+8j9H/DjT3mH/Zs3Ul0LijdYtxBfAMz0YVJ2WOxDXifZN4q+Bzz7/FB7J lD8EwJOVY2PfjP9nFSQKeDKAgTdf+T9zfjp2zrf/5x0/yOKHvHHhzaZnngubN1r/LRPHQ1Rb 4i9FXCBKAO2bZF4DEGwGz80ISC3jiRO8Grv6037w3WEZzBh5A5//8725SDYH+2b1ffcK442W xeDY2jWYPieZNySuKiOBZPGmOQ8cJ3nN2rnN/E5/1F88fHhxsh3nEAgw8N7haJ//58UV9vxp Rn+a5j1T/WmAH9XWceeNlslGMHJguFU//xk8QIpONtTPiZRAcnijsCWvGf7VeKPCBf4nn9F/ TNrZBIMGwppjGm/mlU+u9o3iT1N9a7ltG4AQbN5kvoEQ68fOvrHLZCMSP+hkS9otiutJmn2j R4qBN0mlDWT+h5CzhO3QOBPIlTeZMAEtZIBEDSjbNll/mhoyYMcblkw2YtgDwWzoZENFnRgJ JMe+IadED5WsPw1caIl0pAFpIHtmsl1nluCx5s29d+SC0OB9BjAZ4waCBbLsUfdvspEFdrzx mskmbPagky0xCjflC0k2b9STSzxq8G/Gl5KAHRx4jAae1kwhaQh+bOwb4IoaDp2DjRYykGGP 6k8jUQO2vAmQySZU9oCT7a9dnSnXWbj8+EogDbzJ2jzZ/2Ju6RDSCK4343V/Jez2DP40pnRq lrzhlckmPPDUP/XkOwcPxFfp4MxTK4HE8yaHF9XV1pwXTwMHEp1B4FnYqjwW/YfKG+6ZbEIC D9g6mKQgtYo7pgtPDm/U2GfiUckiRWfMqP40LYDtzjvv1Pwv5M1tt912+fJl2c4lPLOJpKFB GCpvwstkEwZ4oPAoZqGW7YbF+dhJIDm84XKO9+/fDxC6fv06l96CdwKkOf3OvljYHCInGaSq jeuxAjLZcAcPJGT77OOPg19v2ANKIFQJIG+M4q2trX3kkUdCFTpL5xB7Bnlo+O/TlP0XmHH3 lym77tlX5hPy8/2pJZkPp99Pfn94erbN9lHfv23UBu2QqN+4MiNIg01jxvLiwcRs7jYQ5T9N VOpSf/8/iWD/+fvZIX78rW995VvzrapWe50DxLBBNjZMT8Byc2GbqCSAvLGQ/Lx586ZOnRrV KYFxIbdmGM/TFD2sIAT+pXgDaPnXcdsz7AGoZN5vmPqvGfCUjLvtv4qy+CFvZHkFwYnrsbwy 2Siw0biSIcr8b//Dt779v6t++r8f+YqGH/KG2wuqHpzYtBELjEZ48+LQDhJA3lgLZ9SoUdXV 1eIvHSjkHHbSMx1vwLjRjJhTm+FPQBoDb/R8kgI5rszw3YBfJhswZYwsMfAGgPSfP+BGGhpa 8JQoJgAVf/PiiK4SQN5Yiwi2cO655562tjZXCfJqAA40CHQWYEPQ/AC00LxRSZP1p1HskQIz mnB848T1wLkzSvhYG4qj7B+06giqoZP1p4GVo7InFN6QJWDYNK97E/vhJQHkja0kIVDt9ttv 7+vr4yVrh34g9ZmwhzcZeKPSBTxsYP0ofjZ6dyd69rhiw3cDbplsgDc5+0bBjM6Ugb+Cq01p o/xknGyhgKfmwXs375h75dolAdcwDoEScJUA8sZJROfPnw87QhrSOR97a5cAs0YbwoE3xJ+m tgQrR9m2ybaXKWTAN05cD+SWyUbHmzv0rrOsqy37Ib+QATO01tRMyl9xz7yVD/WeaXXVBdgA JRC2BJA3LhIOL0IaMgVE8lSNbj9GjRGg4wUyvIFggWwcgdp++v3ShKi5YsN3g/W/e5STqQFB AapNo7DnHx75MbFg4PPsexVC3/9PTiFqhpnXjv89wEZ7rW6ZgYZO2PoU+3eWAPLG/QoJI0Ia MjoLc6DRlg31fKsalkbFQ2txa+pGjha3phyni6KONFbNN06cD+ScyUZ1l4HoNGeabttGbRBS 1MCy2jE0b9DQcb/VsUXIEkDeMAmYY4Q0mDVhR6CJ9M5FMlZIvIlLJhsWC2xj8XgDbNDQYbrV Q2xkLAcZ4lCydo28YT0zXCKkocazeLMmEiSEOmhIvFky4zUWVS5/GwgTKKgZYccb+Hx25f1d vRtYL31s5yYBywvScJCSWysvbzhdf9it2+T9HXnDek4DRkhDuHMkuzWh6v2oOg+JN3HMZGMJ PxIm4Poqr5/w4eULrDcAtrOXAANvSCpHJYejruD98OLiXNH7XL2uzFB0Skg1xzD1WfYj6hO1 ZyU1cXG2+opcfEPeeLiNfEdIQxBaGPkColL3kY8bEm84ZrKJ0AYyhAk4UwcNHQ/3fxDeaJmD dRUhFVYQbGSokXlrQBIZFP6sy2qv/q40Vv+Qe0857pS3FOC4rDZAJ8gbb8LzGiH9xZc3IQ1a 5Ao6YRMIiTe8MtlECBsY2hwmgIaOt5vce2tX+4ZKVE+jIwcfijK5tmpG+0yUD8WbXBemesaZ VvSn+hbel8b3COSNZ3myR0hDdmcMDQgDdWHwhl8mm1Ce3GRk2MbC51zpYtkADR3PioA6wI03 +mIpOXY48oY2dOjCKvY0yZX4ytk0yJsgJ1aOY1kipCFlAP/szpFGIYdBDn99hsEbbplswskU wMKblff+zDlMwBVFta0vXx+8KsdNFqdZuPDG4A2zMk8s7BvqqJzfzeBts/WnaT405E2cLiTb uTpESEPE86kL3f40KR7FIoEweMMtk010vGEME3CmTsnGpzCIwKuKcuaNcfMltxvj4k/LmUV5 ENmmbu5oz9ARptjEC2T+Rv6M+zdez6eU7S0jpC9fuYihASzMCNImDN5wy2QTEW8gTAB8Yq4W DEsDyH/Td36flPccTireEsD9G//nzxwh/fc3egf2tQbRpHgsiwTC4A2/TDbR7N+UrX+ahSXs bdoOr/Z/b+CRKAErCSBvAl0XWoT0FzduvNPedmbjBuV1sp1FaWIb3xLgzhvOmWyEmzi+wwSc 8YPbOYG0Ax5skgDyJuhFARHSd/zkJ281NWZhk0HOmwM7fStTPNBVAtx5M3laGcuGvJxtgocJ OFAHt3OCKgg8npIA8ibo5fDp22+f3bKZho3yftvWw2ebXfUmNvAnAe68iXUmGy5hAs7Jb44P tAe9T/B4lMCtW8ibQFcBbNgYSUNcahs39HfuwHhofzhxPYo7b+KbyYZjmICzb61lf1mgWwUP Rgkgb3xfAzeGbuY2bFTGGNhz9nibq+rEBj4kwJ03G0f/UU5fmeusuIcJOFCnunEyPp3jW2Pg gSCB1Ng3VEqhzIlXo9a12HT6CV63S+PqZzda958/2d1jZ9xon5/o3+NDn+IhzhLgzpuYZrIJ KUzAATnFtU9c/Oic2/2Bf0cJWEsgFbwhOevoB59UuMD/2kNTrE9FAWyaugY2tvbBa6C90wU5 dZuP9rcgP/hKgC9v/jCpwtWMkLBBqGECzts5/Rd6UKGiBHxIIBW8IXJx4A37M7iXP71et+cs gQ286naeemvXLmfk9O9swo0cmXkT00w2YYcJOCOn90yrD3WDh6RcAinljeZPIyUpdKm+7a+I v1+6RsOGIOf13X3nGhtckHMUN3Iypak5vfjaN3HMZCMsTMCBOoiclMPDx/JTyxtVVsSjpib+ dgDPxQ+vbNl1WrNs6De7Ok701211Rs7pPnwIVFLebBw3UUJ3mfOURIYJOCAHi4T60LlpPiTl vMk60rL/2Vs659/9xJI02ocHuo9bPIVDx63VbT7Wj6lu+CCHr30Tu0w24sMEHJCDaW/SzA+v a08zb3J4ydWNsDJwzvz1Y2fYkL8e6z7q4lXb0XDozDZePqU098ORN7HLZBNVmIADcvDRHK9q N7XtU8EbfbWjLFJ0xozqTzPHqJ0Y+JAFNqTNmc79zsgZ2I95bjiYOBx5E7tMNhGGCTggp669 KLU6FBfOLoFU8IZdHIaWh068xw4b0vLcnnaXCGnM5hk4aoAjb+KVyWbdnx7lVXSAPVE0Y8tN u+cN3Rz0fa/hgWmQAPLG9iyfPnnGK2xIhPS57S3OyMFsngGdgRx5E69MNuXrn2XU/pE0W90y A5GTBmz4XiPyxlp0N/YsuLri1x37TvhAzo72k84R0v1N9ZjNMwhyOPImRplsNs59JhKKeBoU kJPCnDeWwYQmzWLMcXIrGxdr2DQm7n/i2lcd/aSmJ+sj6b5xEPqByBsLEQNsri+7G16+kdPe edI5XA2zeUrCm7hkspEwTMCOQ6Vbnkkbclh4o2wYQ1VoHTSyn+mAo1SfHq42o3eZM+xhfFQw dHD4HAB5YxTcUHcpgU1A5PR0H3P2qmE2T9/I4WXfxCiTzdqVf/ZkZ0TbOG3IYeANIYfCDMpK yXzYTH9m+MTwiAbJzOVT18twGPJGdxaGDtXQsAmIHNeEnpjN0x9yePEmLplsZA4TcLBy0rOX 484bDRy63FkmCBk/MD4SqBg/xf0ykMPfHJA3OblZwiYgcvo79zpZOdu2YjZPH8jhxZuq6XNi kVlA8jABO+SkJ3zAlTcUN2hkqB/nHgDMmC85K8iCN2jf+EOdXEcNnWgwWzbBHWuuCT0xm2eE vIlFJptYhAnYISclz+W48Ub/BGBuF4a2esBuUbFjy5u4mzfpqX/jSLebfTucYRPEylESejY1 O1g5/ZjN0+MTObzsG/kz2cQoTMAOOWlIeOPCGwMmcr/qUpxAAFruWfRcfFrOf6ZQK9betBTV W7PnDSNsNOS0dlln7XSInIYIaeeEnn1nMJunh7wDXHjz6/ExKHsTrzABO+SkPJO0ySrRPqDc ZYpNo8JEZ9+QUGiMh5bLH+ZzNjff7mGxbOg2V6pH+kDOPueEnpjN04uJw4U38meyiWOYgB1y sESbTw2VrMNSHS/w5aULn1c+6JU30N4fcnodE3r2YzZPZuRw4Y38mWxiGiZgiRxIw4OFqJPF Dj+rSS9vvrx26fPVj/uADTnEH3JOdx502sg5tNvH5nkKD+HCm3WTZ8gcnBbrMAFL5BSuefTy p+/70VJ4TFIkkFbe3Bwc3DLeN2yCIMcloSdm82SwcrjwRuZMNgkIE7BETnHtE2lLPZAUUvBZ R0p5c6N1bkDY+EaOEiHd2upg5WA2T1eLjQtvZM5kk4wwAUvklNdPSM9zoHyUdIJ6SSNvhg5U coGNb+Q0tZ1ySOgJ2Tx7zjS46tw0NwjOmz9NKZfWmZakMAFL5NS2vpwgFYpL8SCB1PHmZn8b R9j4Rg4k9HSIkB7Y13qgry7NRHFee3DeyJzJJklhAnbhag1dJR60FDZNigTSxZsv3j91vew+ 7ryBDi+te7apw1u9nAPdxx28apjN0wE5wXkjbSab5IUJ2CFn/5t1SdGiuA5WCaSIN19++r6/ 6GdGPvlAzonuIw7IwWyedsgJzhs5M9lAmEDRmseiTe0sbHSIkH7ngz5WRYXtEiGB1PDm5uDn tX9kJIfvZj6Q45TQc9tWLMtmiZzgvJEzk01tZZyKDgQnE4arJQIiHhaRFt5oJdR8s4TxQB/I Obdrj52Vg9k8w+CNnJls1v7hIfjKH1yJx6sHjB3woK3j3zQVvPGUIY2RKw7NvCLHOaEnZvM0 IyegfSNnJpvK2vHxQgWv2eJGTvw5wrqC5PMm7G0bS/B4RQ4k9BzYts3Oyjl1FrN56rJ5BuSN hJls0hMmYKYUbuSwauv4t0s6b3jkEfBn8XhFTmfnibNbNlsjB7N56pMOBOSNbJlsUhUmgHkH 4k8N/ytIOG+Gukv90YLLUYCc19s9BEkf7X7DdiMHs3lSyAnIG9ky2aQtTAAfAvWvsGN+ZJJ5 c/OtvVywEaSTv295sQ6iAVr7GF8nu3tskYPZPFXkBOTNqp//TJ7kAukME7BEDm7kxJwm7tNP LG8i2baxJJNX5Ay0d9oh53QfbuQoGzlBeCNbJpvUhgkkaSPHEp8G7ZurKa2WVVM+yWu+dYuq umbS2Gobd1UeixaJ5U3w9M9BzBrDsZ6Q45zQE7N5BuSNVJls0hwmkKSNHFfe6LDRnKevCu3E m1hQhH2SyeTN0KEajrTg0pUn5CgR0o0NllYOZvMMyJuaabMlcaZhmEBiNnJceJOrD63TzBnO NEMd6exPlkLKx3l5yqfwQZZFuZLU8YZTAnmjJEnLlEST7eUJObs6Ttgl9IRsnilP5RnEnyZP JhsME0hMajUX3uRoYeZNv8mfptAp42dTfjS8kD7iTZtbtxLHGyF5a3yTzBNyIKGnXYR0yrN5 BuFN7YiHZLBvMEzA4XHR2BWf5s2bnL+NAgzZAFJBxO7Dkqll0ngjoSctyF7Ose6jdrEDac7m 6Zs38mSywTAB5/QEpVuekUlPuswlgD/N0r6x4k3G7EHeSHRVfPHhQEjlBnwbNJYHXqyfu2XX acYI6TOd+62Rk+Jsnr55I0kmGwwTYMmFE6PwaLd4AZ2LTPGRZawU1XYxOMl0v1JtFNPGZidI IiXsPJUE2TeQSmDjWL5gCK+3d5qWsCPHLqFnf1tzOsuy+ebN8hmFkTvTMEyABTbQBrxqV65d io0qdZlo1jzJhAZkfWIaWLJ/o+IFisHsofZvKMzEO0A6ObyR35NmoBc7ciBC+tz2FutwtaNt KYwd8M0bGTLZYJgAI2+g2abd85LCG1yHIoGE8CYunjTfyHFI6JnCbJ6+eRN5JpvVj/4qhUUH 2AFjbtl/oQdVdWIkkBDexMiT5hs57Z0nrcPV6ja/0b8jVVaOb95EnskGwwS8sgdqsg3dHEyM wk35QpLAm6Ej68PbaBHQM7tjraf7mLVXLWXZPP3xJvJMNhte+pNXbYvtQQI7D1WlXE0nZvmx 582Xly7EIibNmVvsyLFL6Nmfpmye/ngTbSYbCBNYtHYU8sOHBGL3OE5i8MB9IbHnzY2WlwSY IAKGYEdOf+deSysnPdk8/fEm2kw261f82YeqxUOIBMrrJ3DXfdiheAnEmzcyVBzgiKKBXetZ HspREnru2mWBnLrNKcnm6Y83EWaywTCB4ODsOdUoXj/iiHwlEGfexOqBG0YsMSLHLqFnSrJ5 +uNNhJlsMEwgOG8K1zyaoMdx+Krx2PQWY94MHdvKqMTj1YwRORAhbZnQMw3ZPH3wJsJMNhgm EBw2pIe69qLYaFacqJUE4sqbL69d+nzliHiBhH22jMjZZ5fQ83jCy7L54E1UmWwwTIAXbEg/ 5987hpo8vhKIK2+GukvZ1XccWzIip9cmoWeys3n64E1UmWwwTIAvb0o2PoWP4yBvhEogptkE vGKPETmnOw9axA4kOpunD95EkskGwwT4wob0FqM8nkLVYhwGi6V9k5gYaFcCMSLn3J52M3L6 O3ckNZunD95sGPV78Zk6MUwgDN5A4ACaOHGAi8Uc48ebhMVAuyLn7J4trkHSSoR0a6sFchKa zdMHb8RnssEwgTBggyZOTElDph033iQxBtoVOW927nZFTlPbqXONDWbkJDKbp1feiM9kg2EC 4cEGekYTJ6bUiRlv0mbcaChiQY51Qs+6zUf7WxKWzdMrbwpfXCTYmYZhAqHyBndxkDciJBDf PNCuRoxrAxbkHOg+buFV29l06My2JCHHK28EZ7LBMIGwYSObiTP213PML0oh0sXW6JLQSvG0 3I9Shs1UwBOaZOqw0VU/tcPUutPmfnTaWDk2Ly9Tjpr+yVWtFqG7Y+dPS61x48nKOdF9xAI5 ycrm6ZU3gjPZYJiAAN5IZeIw8EZT7hn2ZH9TYWJAU7b+p/Kp1iLHG+qg5jzS1KIfGiE0qwzF q4WRJn77N2k2bjwhxzKhZ5KyeXrlzdoHfyXMn4ZhAmJgI5WJ44U3BA+kprQVJ3QWTq6BJW9U WiBveHMTjRtPyDm3a4/RyqnbfKy/NRleNU+8EZnJBsIElqwbLUzh4kCSPIvjkTcaZ2g/mM4A ylo4FEfM/jTKHWbZT04Fo33jGUdo3NAbPK57OUpCz6ZmA3ISk83TE29mTF8uzrgpfR4ZIFIC 81Y+JEMSTx+8sbVviNlj+rPJD0b2hAh00L7xDBSnA9C4MUcTHN271zlI2jKhZzKyeXrijbBM NhgmIJI02lgt+8u4Khs/nXnkjYYHO04Q4KjYyczIct9FPR554+es2R6Dxo1l9NrBvYedkdPZ eeLsls1Gx9rJ2Gfz9MQbYZlsqtdNiEThpnxQqP4ZuYnjiTeK88s+XoAoQQUgw4cTK4f8aLyB N+rH2lYP8oYfb9C4cQiVdkXO0e43zOFqcc/m6Yk3YjLZbJjxVMr1foTLl8HEcVR47PHQVAQA HTits2+o3ZrcPo8hrloLSTDaRhif5oImNG6cH81xRU5f1yEjcmKezdMTbwRkssEwgQhhA0PL YOLw+4Kd5J5kzy+Axo3rc6DQwBU5A+2dxtiBOGfzZOeNmEw2GzBMIJO5OcLXzkNVSdbTSVmb 7Ly50TiNReFiG2fkWCb0PHu8Labh0ey8EZDJBsMEIsSMNjRmVIsFkqTmzZeXLiBI2CXgjBwl QtqU0DOm2TzZeSMgkw2GCcjAG5hD3/l9sdC5aZ6k1LxJfBFPdpYwtnRGzq6OE/11W3WOtXhm 82TnTdiZbDBMQBLYwDSqGyenWZXHYu0S8+bm4PWy+xj1LDbTJNCx74RDkLQ5oWf/zqbYlWVj 502omWwwTEAe2JCZfHj5QizUbmonKS9vho5tRYr4kMDVFb92Rs6x7qPG2IG4ZfNk5E3YmWww TEA23kgfGJ1a0GQXLi9vMAzaB2zIIa7IOdO534CceGXzZOTNrOlLw8tkg2ECssFGqgyeaQeL zfol5c0X7x7zrW3xQBbkGBN6xiqbJyNvQs1kg2ECEvIGptR7phV1vbQSkJQ3N1peQmwElICz lQMR0ue2t9BWTv+Ohp4zDbGIkGbkzfpJfwnJvsEwATlhA7Mqr58grbbFicnImy+vXQqoavFw FscaJPQc2LaNRk5csnky8iakTDYYJiAtbMjELn50DjW7nBKQkTdDByoRGLwk4GzltHeeNCb0 jEM2T0behJTJBsMEJOcNRg3ICRuYlYy8+XzlCF7aFvtx3cvp6T5miB043r9bcq8aC2/GT10R hjMNwgTmVf9GcoWb8ulBOrWhm4PS6tw0T0w63tx8uwchwV0CV6pHtnadtnsu52R3jw450mfz ZOFNSJlsVq3FimpR5kljRGnPqcY0q3Vp1y4db27sWcBd22KHIAFn5Ay0d+tiB+TO5snCmzAy 2ayf/AdGfYfNopVA6ZZnpNW5aZ6YZLy5Ofh55YOIh5Ak4IAcJaHnrl00cmTO5snCm03PPMfd n7Zk3eho1SiOzi4BjBqQEGxy8eZmf1tIqha7JRJwQI45oeeps5ImkGbhDfdMNhgmwK7rZWjZ 0FUiTOH+pGi1+UWNrqu3lq3taTU5rUqa+iba6mj85ScXb/CxGwFcdEAOREjrEnrKms3TlTfc M9lgmIAMCPE0B6hQwF9f2vTIwBsHyjhME3kT2jn88vMrmKBTAG+crZx93cfpCGk5s3m68oZ7 JhsME/Ck6yVpfP69Y6GpK13H3nkDBky2FvStW7n3Gl4yb5qLh6tVorO0ou0kONy6EzFL9jeK RPbNzb4dYrQtjuKMHENCz/4j0oVHu/KGbyYbDBOQhB9epyGs6CcDb1RyDCOcYeFN/61bevuG PkjR98gbf9TLHDW47QUkgUgJgGOtpdM6SPp050E6dkC2bJ6uvOGbyQbDBLwqeknaF9c+EUAh eTiUgTcGf5ov3iiAgR8Lw0jPHg8zF9xUFvsGc9iIJI021qV1zzZ1nLF8LufcnvYcciTL5unK G46ZbDBMQBJ4+JuGmCg1UbwhdNCog/aNX1wOHVkficLFQe2QY0joCdk8D53ZJkneAVfe8Mpk g2EC/rS8PEe1HV7tVyd5OM4Xb7J2SmZPJmuy6PdvTP603IyUg/KatXA2xe9G2T0eZi64qSz2 zeCW8aj6o5KAHXKa2k6da2zQrBx5snk684ZjJhsME5CHHP5mIseDn1ZhZsRKGTZseHGxFjtg 4g0BidKIwMewC5Q1dfSdCEaIp+Gk4I0SmZZ5OgRfUUnADjnGhJ5yZPN05g2vTDYYJuBPxct2 1OVP3/ekEyNsnLTwZ5MopeANRqZFhRl6XDvkHOg+TscOvDmwM3KvmjNv1kx9iUtmAQwTkI0c /ubT1bshQoQwD02sF3+P6TAPEnVDKXiDOdNk4A3MwQ45J7qPaMjpb6o/fLY5WuQ484ZLJhsM E/Cn3CU8qrpxctRqFsfPSkAK3mDONEl444Cc/s69OeREnc3TmTfBM9lgmICE2AgypSvXLqHK l0EC0fPmi/dP2WrbZ74OFuaTz2j7Oj8p+Jfchtmwn/wwc+APnySfZX+9+/pL//rjf/nXE7gb 5FcCYOXU7TEGSSvharvg0w3kFW02TwfePPp8eXBnGoYJBFHuEh7be6ZVBm2Lc4ieN0OHaix5 U/8TBSHwr4E31K8Kh0489JUfP/ST68sARV+vz+KHvMGXfwn8fcuLZuQoCT2bmjXknOjfE5VX zYE3wTPZ1I7/vYQaE6cURAKrW2agrpdBAtHzxjkS2itv9O39K1zElSVydAk9o8vm6cCb4Jls MEwgiGaX81io+Hl98KoMCjflc4iYN66R0GbeaA411dDJ+tPAylFtHcQMHwlYIqez84SW0DOq bJ4OvNkw8YUg/rQNSybIqTFxVgElcHygPeW6XoblR8wb10hoW3tF2drR+81g2wa2cODfDJEy TjY+ajfN/Vgi52j3G7nYgaMR1Mhx4s2o3/vmDYQJFNSMCKjX8HA5JVDXXiSDwk35HCLmjWsk tL1/DMyarxS8pBEFflXwk22PIQP8WGuJnL6uQxpyxGfztOPN/3uuIkgmm9Wr/yynrsRZBZeA HIkGUo6bWxHzxjUSms2+gWCBLHvU9j98EkPUQkbOQHtnFjnCs3na8SZIJhsMEwiu0yXvAbdw IsddlLz54sMBB1eVEp+W+yE4UUOflc9zzjTdto3qTzOEsaXZJ8Zl7WYrByKk32ptJcgRnM3T jjdBMtlgmIDktAg+vf4LPZEr3JRPIEreuG7ecFGU2AkvCbzX+NqWXbp6OXRCz4H94vLc2PHG dyYbDBMIrs3l70FMruiUE8V5+VHyxnXzhpeixH54SeCdpiUG5OzqONFftzXrWBOVzdOON/4y 2WCYgPyo4DJDfAonchZGyZvBjWN56UHsR5gEzMihE3qKyeZpxxt/mWwwTICLNpe/k3krH4pc 4aZ8ApHxxvXJG2EKFAfyKgEzco51H81u5DTV95xpCDvvgCVv/GWywTAB+TnBcYZiyn1yhQpd xJNrx1F0Fhlvbr6116uaw/bySMCMnDOd+7PICT+bpyVv/GWywTABjtpc/q5CSqR2ePrt5pdB n9PV0uyqDuQKduYO1vFGLdLmo3CBU20dq3FDwVFkvLFLmyaPSsWZOEvAjBwtoWfY2TwteeMj kw2GCchPCL4zDOmpT1feKAo9BxlQ/dkC0gxKPccbHRWa8zyWypGilltkvBnc9gIq9LhLwIAc JaHn9hZi5YSazdOSN14z2WCYAF9VHoveQnrq04U3imljCRiFAXl5uTprOSZohkxeXrbatE0n ObMpN4KCqGK1+HTmY8q4UjDFMG44ld8i443rk55x18Upmb8BOZDQc2DbNgU527Ye7W8JaSPH mjceM9lgmEAsCMF9kmE89enMG1vcEAxQJFJ5A8DIWi+5FrnPKKOIMloov1sGVqTbnE1E2zfu 4zIYXn6aRMMb5yc9U6KpE7PMgV3rN7b2aS8toWd42TzNvIFMNp7SpmGYAHc9HpcOw3jqk5k3 ObMlQwOjjyv7uw4tKkeseEPvCVHFqOktH+29gTc6b5zVuH5w4npMNLwZOrY1MdoWFwISMCCn p/tYNnYgnGyeZt54zWSDYQJxwQP3eYbx1KeLP824HW/JAIo/lryxspJsLCfkjR58Qx2LUU0n TAIG5Jzs7iHI6TvTzt2rZubNwhcXsts3GCbAXYnHqMMwnvp0ixfI2CE5i8KNN0pzkz/N4Hwj MQfWwPHLG2pcV0vFX4No7BsMFkgYbMhyDMgZaO9WkBNCNk8zb9gz2dQ8eC8WHYgRHrhPNaqn PnOhzDnPl40/jdrfH17cTAWz0f6z7LaPIRIggwFL3qgxA2q8AIQNaD/aPKx680cW66Oi4c3n K0ckUuHiomjkKAk9d+0KI5unmTfsmWzW1EzirsKww3hJ4PKn7/NUotgXswQi4A1mFkg2lmjk KBHSjQ0Kcg7t5uhVM/Nm9X33svjTMEwgXmAIabbn3zvGrCGxIU8JRMCbL94/lWyFi6ujkZNL 6NnHbSPHwBv2TDbLaseEpMKw2xhJoOdUI08lin0xSyAC3mAZgjQAqa+tQYuQ3td9/OyWzWDl 8MrmaeANYyabjcXjY6QTcarhSWDnoSpmDYkNeUogAt4MHahMg8LFNb7ZuVtDDkno2c8pm6eB NxXT57s60zBMIDz1Hbuea1tf5qlEsS9mCUTAmxstL6EuTokEaOSc7jwIyBnY13qgry7gXo6B NyyZbDBMIHZUCG/CIWW1Yda66W0YAW8+r/1jSrQtLhMkQCPn3J52QE7wbJ5G3rhlssEwgfB0 dxx7jiokOr2cUVceAW9QC6dNAhpyIEKaJPQMmM2T5g1LJhsME4gjFUKd85Vrl1D7i5eAaN58 eelC2rQtrpe2cpraTikR0tu2Hj7b7NurRvPGNZMNhgmEqrhj2vk7H/SJ17Y4omjeYJm11OJH s3LaO09CuFqQbJ40b5wz2WCYQEx5EPa0jw+0o/YXLwHRvBk60ZBahYsL15BDEnr2+83mSfPG OZMNhgmErbhj2n8YWTvFq+/YjSicN4dqUO2mWQI93QdJkPSJ7iOAnFNn/TwESvPGIZMNhgnE FAYCph1Soc/YAUDwhEXz5saeBWnWtrh2kMDBvYcJcvo790I2zzf6d3jdyKF545DJBsMEBCju mA5RXj9BsKrF4UACwnnTOA11LkqAIEcJV9u1p39Hw6Ez2zwhR+ONQyYbDBOIKQnETLtwzaMI APESEM2bwY1jUduiBDQrR0no2dTsNZunxhu7TDYYJiBGa8d6lDAKS4vX4PEaUTRvsBIBwkaT ALFydrSf7K/betpLNk+NN3aZbDBMINYkEDP5ix+dk09Z06VrvM7O87HG8jteB/TeXjRvUNui BGgJEOSQhJ7s2Tw13lhmssEwATH6Ou6j9J3f511hWh/xq1m7zS+6KbNmzzHDWISa6s7mT8gb /dn58tP3UduiBAwSIMg52v0GezZPjTfrf/eoOVNn2fqn464Kcf4CJNB7plVm3nifG/JGL7Mv 3j2G2hYlYJYAQQ4k9IRsniyBA4Q3lplsNhY+J0BV4RAJkADHKjjM9o2ChOLi4VBRGn6yFaFB SWq1pvPyoEFzRm0Skwj+ohSAVj8hf9RZSxbHWtaTputZZ7tktrq8s8/mCKH+tJv9bahtUQJm CVxd8euOfScAOQPtnSzZPAlvzJlsVt77s4KaEQlQhbgEARLg+MinF96onMk5xXJMAQBoGMrC QPdHMycsj7Xkjd4fl+kp4bwZOrYVtS1KwFICBDkQIf1Wa6trNk/CmyUzXjM40zBMQICaTswQ EfFGs2pUKtAmjGLp6OybjO1jhEOOE9bHWvMmAzP1JxW8weQCy+5G3thJgCAHEnoO7GhxzuZJ eGPIZANhArMr70+MNsSFhC2Bhq4SXn4iL/aNV95kgUPbIn54o9BGHVo9Pun2DVb2RN44SoAg Z1fHiYEup7JshDebxoyl7RsMEwhbQSesf44pbQLxRiFBzlFm9Kdlt2vy8pTdnCwfc5ywPjbn qss56ChLSPlzGuwbTGaDxo2rBAhyDnQfd8jmSXhDZ7LBMIGEwUDAcjhWlQ7Em8w+CvFzDS9u Lh5u8KcR4GQJoQUO6IIITMdqAQjDi4s1B10uYACiEpA3rpoIG6REAgQ5kNDTLpsnwIbOZINh AgK0c/KGqG6czMufhv0wSkBofBraNykBRvBlEuSc7j54tL/FHCENvJk7o0RzpmGYQPJgIGBF yBtGSHBsJpY3mKwT92+YJQDIadt7cmB/tzmbJ/BGy2SDYQICVHMihyiufYKjJsWuWCQglDeD 214I/s0Xe0iPBK5Uj+zYd/LsG3sNJg7wRstkg2ECiYSBgEUhb1gIwbcN8gYDlKWWACBn377j fWe6aOQAb0gmGwwTEKCXkzoERM/zVabYm6sExPIGixEwe5PSY8S4rhSQ03ug982BXRpySCYb DBNIKgmErctVP2IDvhIQypvPVz/uqlywAUrALAFAzvFDh3vONBDkkEw2GCYgTC8ndaChm4N8 9Sn25iwB5I3U3iRkjyYBQM7pY/sIbyCTDYYJJJUBItd1+dP3kRAiJYC8Qd7ERgKAnLOn2oE3 kMkGwwRE6uWkjoW8EQkbGAt5Extti7YOSOBq1SMn+1vXrXg5qRoQ1yVSAsgb5A0CACVgK4FP Nkx4t6mwYPUjIrUSjpVUCSBvkDeobVECWQlcXfvkh1unnalfvHN97apFW8oLtzVVrt5aW5FU 9YfrEiwB5A3yBrVtWiVQ+eClzROPNy/c27R625ZthSu75uVve2l0DbxWzKvbsbKsraBgYXVL 2QZ0pt0jWC8ndTiMT0PepFXbpu/RnE82PPvX11852Lx8/Y7GBU37X63dV1DcSgCjvYA0jVvL uvKfaZm3+OnFnQdXTHq5/IGkqj9cl2AJCNa2OBzGCyDeBEngWs1jH2154WjTkvUtGwuad0/a 3jtna09hye6Xn1lnYIxm02xpWNxROqXz4d/ULKj57Zy2tqIxa2vLBKskHC7BEkAACJaAUN5g /rQUxZiV3QfOsdONC3a1VC9vef0Xm/dNaOl9Zdth2ktmiRniPVvfULR720sdj/6ma+Qjc4vq ob7I2sqqgyvGLarIT7D6w6WJlECM8tmIL8QZEoeQN4K+3SeeNFdqx7xbnw/mC9Dl6W1tAJjR TUdebO619JLZkabqtbq1TflN7dM7n368/YFf7hs7ZsKrzQCbWRVth6ffXlazGp1pIjVyssfi mK8TrlXzi1bZjsBwp4l7i5D4wLtb5A3yxo8EPqseAeYL0KVue+3cphagC7x+13DI1UvmTJrN nc93LZhIbt29kyaPmtMKsBld3Ll/9i/BuCmuqEm2BsTViZQA8oY3Tdz7Q9740baJN1bMCwS6 nGuY39lSAebLw3XdBDCevGTOpFm158m2jTO1L4m7ZxdqNXp3lEwB46ZqdeWi8r+I1Ec4VrIl EAVvoKZzXrFaPTpTOFqrJZ2rGJ37KFtaWmmkFZB2V+oSt0DeIG8sJAAPvrxfNw3Ml+qWrS80 7NLo4s9L5kya8p2P7mx5qfMPj2iw2VRYocFmRfVmgE3vwt/NLt2abPWHqxMsAY71PZn9acCb YcMIRZS35J2eJtRvCp0sWkjME7epIW+QN3dfVx98aW5ZvbCpkaZLQC+ZK2nqO6ZCrLN2u0Io 2vKi9RpsppZ1AGzgVVFTVlJcKlgf4XDJlkBEvFFtFgU4FjSh7B1A0zBi1qB94wYyq7/f2LMg hZ4oCZcMzjHy4As4x0bVdRgAw8VLZkealYu3QkQA2DSr28ZArDP9xXDv6CfzC1/XYDNyfnv3 3IeJcfNCZeOCiqeTrf5wdYIlIC9vNCSpWhR544c3QwcqJVS+iZ8SOMe0B19mNrSa6cLXS2ZH mpqlW1ZvnwSkqdr9exLrTMNm37PPjZ2/XYMNvKkvKyLGTUn1stn5KwUrIxwu8RLYtHueHy1m dYwXf5qLfZPZ0DECB3nj50wNHVmfeOUe/QIzzjH6wRdLwASJJbMjiitpADZarDN9i3ZNm/nI Kztp2Cxe2Uhg0zv33qdXNi5ZtDjx6g8XKFgCde1FfrQYf96oMQNqSIA5hAB54+dM3ezbEb06 TlzaGMgKY3jwxRIwoXrJWEhDxzrTsIFENTRp4P24JV2H8u8ivNm0qnD6q+sLKkYLVkY4XOIl wJE3frRhKo8RGi9w8+0e5E1ACUBWGPODL3aA8fHEpVfbhYU0hlhnOjoAEtUYYEPy1mjGzcPL N86bsjzxug8XKF4CLfvLUqnzo1y0UN588f6pgNo2dYdnssJYPvgSuZeMhTTmWGcNNpCoZkHR FgNs4NeNFWUENsS4+cvybUuXFIlXRjhi4iXQ1bshStWbyrGF8ubLT99PHTA8uu8gK4zdgy/y eMksSfPK2LVryzeRiADyMsQ666ID1EQ1Bt4UVLVqsIGdm/tK1r3w9JK55SMSr/twgeIlcHyg PZU6P8pFC+XNrZuDyBtaAiQrDFR8sXzwRUIvmQNpVm0fp5HGHOusi3tWE9UYYEPy1mi82bFy FkQKvDoNE0JjtZtQJPDOB31Rqt5Uji2WN7duXS+7L83IcX3wRVovGSNpLGOdadi0vTTPEIpG qAPbNiRvDXkdzb9j5LJV02atWbJ8rvhvvjhiGiRw5dqlVOr8KBctmjefr348PbxhefBFci+Z 3SYN8Z7RNk021nnCk5bPIpAP6UQ1BuOmpmqNBht4s7t65mOV9eMefhUTQqdB9YtfY4yKEUTJ B95ji+bN4JbxieUN24MvcfGSeSLNhs7xWl5nS94YEtUYYKPlrdEZN6X1C+egMy0UV5J4/S7b iByTdfLWyUnuTzRvbjROSwxv2B98iZeXzI4088fVmm0au1hnmjrdox6nE9UYYDNqQQfJW6O9 wLi5a9G68U+8VrJipmx6CueTDAlwTGaTZD7wXpto3gx1l8aUN54efImpl8yBNOtW1lbvGKNF BJA3O1rz6bzOlpaNOVGNgTctS2fSsIH3o0tX/rm6afKoYnSmJUO5S7gKfNiTN0qY+hPOm2Nb 48Ebjw++xN1L5pU0DrHOzolqDLApXVlvgA3UVftJ0eopU6oWzcPHPNGZFpYE2g6vZlKQ2Iir BETzRtoUAz4efEmGl8wraZRY54ppDkEB2p9aX3nN/Dgn/cmk0k4tb41GnRfKK0dVbRv76zkL yydJ+L0Yp5QMCfSeaeWqSLEzJgmI5s2Xly7IYN/4e/AlYV4yr6RxjXWmE9XULqh2hg2UG+gq eMLSuJmxaMu0pxYlQ6/hKuSUwPn3jjEpSGzEVQKieQOTj+QRHH8PviTVS+aVNCyxzq6Jagz4 ofPW0MbNL5dtem5EwZLiJXLqKZxVMiTw4eULXBUpdsYkgQh483ntH8M2cYI8+GLJmN/WH5q0 vXfO1p7Ckt2vPL+BV1JLefopfH5D7eo15ogAII1rrLOhZtrUwkZnywb+Suet0WBzZOlo2LmB 0mrgTMPqaslQ69KuYujmIJOCxEZcJRABb260vMSZN8EefHHwks1qOFK4smte/jZ5wMB9JkCa 9etqKltHGWLP4FeWWGeWRDUG/Dy92GLbhtRVA95MenbpS+OWSauncGIJkEDhmke5alHsjFUC EfAmeEh0wAdfnL1k8zccLChu5a7WJezQgTSMsc4siWrM5QZ2Lxxv2LYhRaMBNmOqG8C4wepq CdDpMi+hvH4Cq4Jka2f+rgafUIeSCmpqPbXsH5rz4DO1lKfyi6mMNNvgcWoVBW9ONHiyb7g8 +JJOL5kd5JxJwxjrTMOmvmC5qw+NNDDkrdHAQ4wbKK0GvJlf+bjM2grnFncJcKwkTZQ9A2+G 5+UN1wEHCDN8uLl0dJzo4X2uEfDmi3ePOfGG04MvKfeS+SMNe6wzHYq2vGg9I2xmVbSZLRvN uIFIAYANVleLuzaXf/47D1V5V5VOR7DwprgZjBzNhMlUiKY+UStGU7WktcbEEFJ+DBYS30WI 6C0C3nx57RLNG14PvqCXzNll52zTsMc6syeqMeetocsN0OApW1UCxs3UcsWZhtXV5NfXcZ8h 98o3TLzpV1iSBQ7Bi+mDW4AWo1dNsYOK+0XAQMAYEfAGVnWsZamnii92LEEvGcu20GtTNq3f VGF5S5APm9qndzrmdbZLVDPh1WZGywaamfPWaEWj7164GhKmPf/UYkgIjdXV4q7N5Z8/92Bo Nt7c0nCSxYqZN0qL3KaOAoBE4eZWNLz5857jnhDi2nhCS28aYslY6EK3cSWNp1hnQ6KaUXNa 2WGzonqzpSeNFI0G4wZKq4FxUzgTE0KHlcFFfgyImWEYlQhYeZOlh2rFWPCG2BgUdZA3RrMr IxzKClTdjXpfJW0Rrjh23hUhzg1GNx15sbk3PbFk3EnjNdaZho1rohrncgM0eKBoNBg3wBso raZEpmF1tRXIm3AlwD04jTFegPjEiHLMOshseQMN1b8p/6M/TWUOCeOjvY7UxhcBjoVLcudf P/DKm8Q/cemVKHbtXW2abKzz04+z5EAzt3FNVGOAjWXeGg05xLgZUV4HsMHqamK+4Kd8lIau Eu4bFcz2DeGIyg/LDR01NkD7Ck+FEMQePHz8aQ68saDNrVvnLl9l4Q16yTxBiIU0Wztf6Mp/ xh9pukY+sqBoC7sPjbSsLyuy86Qdnf1fWeOmtF5J0InV1dC4CV8CPacaufMGO2SUAH/eqCaj AnHV1jFOZvDmF7+uO2BGDnrJPAFGa7wkf6tzRAB8//IR6+wjUY2BRotXNtrBhhSNBuOGlFYD 3mB1tZRbHmKW/84HfYzKEZtxl0AYvFEnCbQBj5pqDRpMwed2HQPeoJfMH2B0pNm6xCH2DP4E sc67GvM7Hv2NP7MGjto7caKn6ABCHbu8NXTRaOANlFYD2EB1NTHqBkdJuQQwcxp3irB3GB5v so60XOSfHjiNO44nOy9ZQJC4Hq7YNG6k8R3r7CNRjTlvTVvRGFfjhpRWA94sLsDqauHuk6cc M2T5pVueYVeO2JK7BELiTc6Rpu7fNOfpedO7d8BVpWIDSwkwkkaJdV48ybdNQw5kT1TDUm5A w8/R/DtGLlsFsHmsUtm5wepqCAMxEmjZX8Zdh2KH7BIIyptcqgV9mF8OLqo/zfDY7OWPriBO vEqAkTRBYp3pRDVVRWu9RgeQ9nZ5azTekJ0beEFpNYANVlcTo21xFO6ZBdhVLbYECQTlTRAh Lpy61avCTW17RtIEjHXWYNM96vG5RfX+YDO6uNMubw1dVw1gQ0qrKY/dYHW18OOyEDYggcuf vh9EZeGxASUQJW/qq/emlh/sC18xr6729ULniADy1yCxzrTbbd+zz3lKVENj6bdz2naUTHHY toE/HVwxjhg3pLQaVldDEoiRQHHtEwHVJR4eUAJR8ga3cJypw06agLHOuhScU6f5CEXTkOOQ t8Zg3ABvJk8sA9i88nypGHWDo6RcAnXtRQHVJR4eUAJR8ga3cOx4w06a4LHOQRLVsOet0WCj GTektBpWV0s5A0Quf/+bdQHVJR4eUAJR8gamjls4BuSwk4ZLrDMNG6+JaszlBrrnPuzsSYO/ vlBeSZxppLQaVlcTqXBTPtbFj84FVJd4eEAJRMwb3MLReOOJNFxinTXYQKKakqJN/qIDtKMa Sue4woYUjaYjBbC6WsoZIGz5hWvoAs8B1SYe7lMCEfMGt3CANxWFrBEBYNNwiXUOnqjGU94a Q9ForbSa4kxbViBM4+BAaZYAbt74RATXwyLmTcq3cKpeq1vblM8Se0ba7GjN7/Sb19nywU9/ iWoMsJlU2nko/y5244aUViMJobG6WpoZIHLt+OQNV3D47Cxi3qR2C8craXjFOtPU6Zg5+5FX dgZ0o0EAdFfBE66wgQYl1cuIM42UVsPqaiK1LY51ffCqTx2Jh/GTQPS8SdsWjlfScIx1pmHT MH9ZQNKQwzdWlLHARtu5UUqrzanNRqZhdTV8zFOIBKobJ/PTmdiTfwlEz5u+oxfYH36MdUuv pOEb68wlUY0BUQVVrSyw0YpGa6XVgDcTH1vwcvkD+L0bJSBAAm2HV/vXkRyOzKT9yuX40hUF 01KC6RNMGqsmc5iFBF1Ez5uhGzdfGbs21iBxnbxX0sBWzevt0zonPBkw26b5cAhF852oxgAb 53IDlkWjFeMmU1oNq6sJULI4hCaBsCOhLTUApd4BHsOHD9cqdlK8Uf5CKk1DIeRcjkkl4XFe Xu4ICVDBZQrR8waWsXlFp6vKHnf7t+Erwo9+XpNpOelHpOrqdyZlD3x45Nf/ceQ45U9yvWqW blnTMo09IgBa8o115pWoxlxuwDVvjaFoNF1aDXizqPwvqBBRAgIkICASmoU3xcVg5BCiWPOG Uugkvz5VbpqLspegEyl4c/zgeRdOZHDy8+9keQPs+frthS+NLvz5P/70d1n8kDcSvYA0q7dP 8kQaJdZ5az53m4Z02B0sUY2BNzVVaxg9ab1z7yVFo+E1MVNaDaurCVCyOIQmAQGR0Ey86Vc4 kzFmLPxpOmeaVs5F11ACXASeghS8uX5t0NGlBlz59s8frvmdDW+0zyXhjQ/ShBHrTHNr9+xC LtEBpJMXy9sZYUPv3Gil1bC6GsJApAT6L/QE1pMuHTDyJlPsGEwcM0ZI1ZYsdHLVwzRChb0A Uf1LwRtY7JqFu+xooVozOd5o/jSwcrS/ygAbf6RRYp3njgvJrIFuNxVWcITNqAUdLHlrtKLR D5TUEONGK62G1dVEatuUjzVv5UMCCkiz8iZj2gxXPGuGcmBZL5tq/ZDdguyPPo5AFBnCGUcW 3tgmGgBP2rCsr8zCjoG/whaO0kb5yTjZonGp+SNNSLHOfBPVGFjVsnQmu3Gj1VXTSqsBbGaO LUm5EsTlC5OAAGcaaGZ23mRMHPjJ8gZ+U8mj7tZQEQQ0hcLR/6J7lYU34FKzRsXPf6pjvQ4q EDWgoCjLoShCBsAN6I80JNa58w+PhGfW7B39ZH7h6xwtG+iKpdyAuWg0wObnJetJaTWsriZM 1eJAIAEBzjRvvMmYOBpvsr8RHZchjwE3Fh+IZgTP8WThDaxpZWGrs3Wit2+ymzpwiPr5pB8J DFED0qwt37Rq+zhPEQGkcUixzrqsaBMnjp2/nS9sGPPWmItG06XVsLoaYkCYBMQ403jq46T3 JRFvetrPsPNGt22j+tPUaOlwXWpBSBNerDP3RDUGVo2c386Yt0bbuRm5bBXZudFKq2F1NWGq FgcCCWzaPS/pCjxm65OIN/Ln7gxCmlBjnWnYtMxbzNesIb3VlxWxb9tAy/3lz2uw+WP168ST Bq+lJQtRFaIExEgAc3TKhiOJeOMcpRZVIAAZNwhpwo51DiNRje+8Neai0XRpNayuJkbP4igg gdmV9wuITJNNoUs+H7l44/7gp/Dws4CkCTvWmQ5F45WoxnfeGnPRaLq0GsDm1WllqApRAmIk ICYyTXL9Ltv05OIN5FKbP259tKaMNvr8cbXrqjb4iwgAmybsWGddopqxYya82hyGGw3KDbQV jfHkSaOLRtOl1bC6mhg9i6MQCZx/75hs2hbnIxdv4Hw0rj4QOW8U0qysrd4xxkfsGRwiINZZ F4o2afKoOa1hwAb6XFtZ5RU2B1eM03Zu4A0prYbV1RADIiVQsvEpVO4SSkA63ly88HGEvAlI GjGxzuElqjFAa1ZFm1fYQPs5VWUab7TSasCb12ahM0353o0vARLo6t0gobbFKUnHGzgly2c1 ikdOcNKIiXWmYcM3UY0BNqOLO/fP/qVX3tB11ejSaoozrWy2AEWDQ6AEQAJXrl1C5S6hBGTk zf6dp0TyJjhphMU609EBy4vWh+RDI92ylxugmaQVjaZLq2F1NWSASAmsbpkhoarFKYEEZOTN lU8+E1OBLThpwIG2fVd+59OPh5eWxtxzGIlqDOjylLdG443RuFFLq2F1NZHaFsfCx26kZZuM vAFhrV/aFqqJU/j8hvXraipbR/mLCCBHCYt1NtRM456oxgCbqWUdXt1opD1t3Ny1aJ0WKYDV 1ZABwiSAOWykhY2k9g1Mq+/ohZB4w4U0SqzzqukibRoyVsfM2Y+8sjNUNxrkrWEvN0Bj6Y2C X9FhaVppNayuJkzV4kAggZb9ZTIr3JTPTVL7Bs7Kgj9v4oscLqQRHOssIFGNgV5e89aYi0YT 6kyZUqXlsFmyoBRVIUpAk8CzD38VsiH/cFwmVG8cqSWi/Xx9pBLC96Mfkg/+40fZo175ztf/ 5TvPMkT3XfzoXMp1uszLl5c3bdve4MUbLqTJxjpPHSPerOl8+Dc1C2pCNWtI54tXNvrzpNFF ow2l1bC6GpJGJ4EMOe7+D5U3NEKAPRnAAJC+/vB/5K/4j7v/RcMPeePyqm19WWZti3OTlzdc ogZ4kUZ8rDMdiragaIsA2Ixb0nUo/y5/vNm0qpB2pk0r2aoZN1hdzVVLpqkBIOSrd79yz0gL 3sCfshAy8MaqsTV4xFS7QWz4loC8vIElbV/f49vEeW3KpvXrqwNGBIBNQ2KdOx79jXizBkbc F1qiGgPA/OWtIXAyGDd0aTWsrpYmlrjbHypIrHgDxk3OY5b1p4GVox3iKsnSLc/41oPxOhBK gca0yLTUvPnw4ic+eKOQZlNFkMAz7Vjxsc7CEtUYeLOxosyfZQNH1a+aTxs3L1Q2asYNvCmo GO2qKbBBKiQAnrRhWbeYyWTJGTdG5xt42JQDMwXjFSebLdUiDIP+xeZ95peBYdlC0mRfKhgu kDdhfT/wFBjNkTSRxDobEtWEHYqmIaegqtU3bI7m30HXVTNECrzyPEYKuH/rTwVsLEIDKH4o UQPmHRqwcpQPs3ByDBkoXPNohNUHXHmj1JCmGGP41av2RN54lRhre8Z0ahxJE1Wss7BENVzy 1lgWjQbY0KXVlOpqS4rSokzdtrJRDrQEDPYN/GqyXbI7PXCU2vhHP7QPUdv/Zh2rTgmhnQtv FNMmr1k3LhCH8EdhR17e8IzNUwxUUn8MdNKZRRpvcjaTofsQ1silS6n9aWSFzunUOJImwlhn umZa2IlqaN7Ato2/vDWWRaMNpdWwuhoyxk4COt5QfjY6ZjpHINWflg2hNqEdSqtdH7zKRSH6 68SFNxpccr1rCMogw0yL3CHWBys4oswcaBQL4sSAN3bPfnIkTYSxzroNm9FP5he+LiAUTRui pmqNb08aHLi7eia9c/PLZZueG1Ggbd5gdTXkjRgJRP6MZzDe5EwZiz0eC9xkQaNrHHRLyB9n PR8VA97AmpbM2EYHDizJ37p+83IuEQHQSYSxzoIT1fDKW6MhyrhzU6GLFFiyrECMusFR0iwB MG4izwYd0J+WcaxlXGualaLZLs68iYVRQ1EpHrzRMkYrpNm6hBdpoo11pmHTNW2msOgAQp1R Czr85a2xLBpNrBw6Ydq4h199ufyBNOtBXLsYCURu3IA6dYsXMDjN6F/1TjHV1MkFFChtjdFs 2WMstoU8GxyCD4gHb6DOdPWCBo6kiSSvs90TPK2vvCbSh0bGalk6M4gnzVA0GmBDl1bD6mpi VC2OIoNxw6ay7cKhdbFmCmbITx7EEFBmT/bT7EcW8QIBI6zZ1hC8VTx4A+s8/nYzL7Mm8lhn OjpATKIaA89KV9YHhI2haLShtBpWV0MSiJGADMZNcC2cnh5iw5ubX9xY0zE2IHJkiHUWn6jG AJtJpZ2+89ZolHqhvJKOFPjN8i30M54TH1uAzjQxCjfNo8THuEkPUFxWGhvewDrOvNvumzcy xDrrogPGjpla2CjejQblBroKngho3PSUjqVhoxg3VGk1pdrNvOVp1oO4djESQOMmdhyLE29A uFsPTPWBnNfbp3VGkdfZbsNm76TJo+a0iocNjBgkb41GKbquGsDGUFoNq6uJ0bYpHwWNm9jB BiYcAm8ye15UnJ66B6Z9FCAbw/kPejzxprbjma7FkyJJtWk3aNtL8wSHonHJW2NXNBp4Q5dW w+pqKceAsOWjcYO8uaWwJa+ZfthVhQv8T4AT6EnYlpaWnz/47yzIkSfWOapENQb76enFHLZt DEWjiVftLzNW0Zs3WF1NmM5N7UBo3MQRNuHYN3qkGHjjmza9vb133nnnPffcs//wblfeNO95 sfPpx6Uya6BmmshENeZyA7sXjg+4baOUHlj4O8POzWOV9TRs4H1x+YTU6kFcuBgJoHGDvMlJ QA+VrD8NQsf9OdIuXrw4atSo2267ra2tjYyx81iRHXLkiXWmadc96nHBiWoMvAmYt8Zu50aJ FKBKqwFssLqaGIWb5lEgFXTkCQViqu4jn3YI+zd2LjPiUVMfe2IpAHH58uX8/PxvfvOb1dXV tKQ++vSvZt5ArHP7uhelsmnIZPY9+9yEV5sjiQ4gg86qaAtu2ZjrqpFIATphmvLYzaLFaVaF uHYBEog2FXTkKjvWExDGm6zNk/2PwdIpLS39t3/7N+DN9evXzSLu7qukkbOrMb/zD49ICBvx iWoMYIO8Nftn/5ILbwxFo4E3htJqWF1NgLZN+RBQxDPCOjex1vUyTF4Mb3J4UV1tzVq2BpAC bMzk6j6o7/70pz+BJ81ORp8NXoZHaiTJ6yxVohoDb4LnrbEsGk12caZMqaI3b7C6WsphIGD5 /Rd6ZNCbOAd/EuDMm1z+H6poqs6YUf1pwRObHulbL1usM52opnZBdYQ+NDL0iurNXCwb6MRs 3BhKq2F1NQHaNuVD1La+7E/N4VGSSIAzb0Su6osbg/v+8HsZfWgjH1lQtCVy2Ewt6+AFm965 9969UDFo6NeMBZto4wYSQs+vfDzlChGXH54EIAb6w8sXRGoYHIu7BGLMG5DFx0ePyMabvaOf jCRRjQFvXPLW2BWNBuoYSqsBeLC6WniqFnsGCWAMNHftL77DePMG5HV68UIW5Kz9/tfUjaGv PfMzJWys/YEf30c++uaPsz387Hvf/dr31maCyvy99k6cGFWiGgNv6suKeBk3R/PvMNRVU3Zu 9KXVlMg0rK5mqnOMnOAlAYiBjrZitHjVnMgRY8+bwcuXGLxqP75PBYkCngxg4M13v39X+wN3 PfO1b7yaxQ954/MVYaIaA2wWr2zkBRtz0WhzaTWADVZX46VYsR9LCRwfaE+k/k3bomLPGzhh H3R1sEPi1W8Oy2DGyBv4/L7hPkkDvdUXLI98w4ZMgFfeGkIsS+PGUFoNq6shJEKVgPxhAteX 3W1+0SzRAqlYnjtMMISSwBs4PW++nO+MnJw/TfOeqf40wI9q6/jhDSSqqSpaKwlsfjunra1o TNjGzfRX1xty2JSsmBmqxsHOUyuBeSsfkj+bgAtvgDa5QtHBI3NjzKOE8Aa8at2/Y3reUwGP YZMGtm0AQvBvZjeHWD+Mr8gT1Rg4x6XcAI2r58qqDWFphtJqJCE0VldLLQ/CXnjPqUb59Ss7 b9S10Dm/tPd0zWkFS7nfkwKphPAGzuK725vZIAFhAlrIAIkaULZtsv40LyEDkSeqMcCGV94a jTfmotHm0mpYXS1shZvm/svrJ8gPG5ghoz+NcqZZ8caQzJh6btF3mmPZpJcc3oBk35gxzRo5 w7+RC0KD9xnAZFpCsECWPer+TS6ywJlekKhGklA0Qp3RxZ288tbYFY22LK2G1dXSzINQ1x6j B25ceZPR+8RcIdCxtG/ILk/WlqGNHe0w2fjhdT6J4s21v70DuylWnACuaBlzckFoum0b1Z/G EjXQ+sprkmzYkGnAts2Okikct22gK0vj5rmVTYadm2lPLQpV6WDnqZVA2+HVXtVZVO3ZeKPM Tt3KseQNmX6WOsVAp6S40bTzkijewKre3rKJzavGukNj7k2GRDUG2nHMW+Ng3JhLqymP3Swo Ta1CxIWHJ4F45eV05o1Wa5KYOBmIkMqUmtVjAEumWRKBkzTeQJKbwxPHh4ScrpGPlBRtksqy gclwzFujweZoyShDmAD8ai6tBrxZUPF0eEoHe06nBGLkSWOzqKi8khpZ1M+GFxfnZdCjc6Bl mlGfJCSOOmm8gZN05a1zNl41/zYNAEySRDXmcgPdcx/m60mzLBptGSmA1dXSyYOwV40Vbtgw Fr9WCeQNnIS3Vq/ia+LIk6jGwJuG0jncYWMuGm1ZWg2rq4WtdtPZf3Xj5PjpUZwxmwSSyRvw qh2dMokXcjpmzn7klZ2yudFgPnzz1jgUjbYsrYbV1dLJg1BXjbWi2fR2XFslkzdKRPwHHzA+ AeqMJXkS1RiAN6m081D+XWKMG3NpNYDNvCnLQ1U92HkKJdB3fl9cVSnOm0ECieUNrP3DA/uD mDhSJaoxwAYCoLsKnuAOG+hw3arXzJECo6q2GcKgsbpaCmEQ9pLr2osYVBY2ibEEkswbOC3n a9f5Qw4kqplbVC+hD41MiXveGoei0YAfQ2k1khAaq6uFrX9T1X9x7RNDNwdjrEpx6gwSSDhv QAK2SQfsk6TJlqjGgL2CqtYwLBvLotGWpdWwulqqSCBgsRAA/c4HfQz6CpvEWwLJ5w2k8jyQ 90d2K6d76jSpEtUYYMO33ADNLcui0Zal1ZTItOVzBaghHCIlEsDyNvHGCPPsk88bEMV/nznN +ETO7tmF0vrQQspboyFn06pC884NfDLp2aWGzRusrpYSDIhZ5s5DVcz6ChvGWwKp4A2conde 3+Zq4kiYqMYAv5qqNSF50qCu2t0LV5t5Yy6tBuxZOKdMjCbCURIvAflrqcVbwUs2+7TwBsR+ qqjQDjlyJqoxwObF8vaQYGNXNBrwYy6tBrzB6mqJx4CYBcYrSZpkqjuW00kRb+Ah0EPPjjUj BxLV5Be+LrMbDeY2akFHGHlrHIpGA2zMpdWwupoYRZyGUaBw5+VP34+l1sRJ+5VAingDIjIX LJA2UY2Bfy1LZ4o3bv6y3OKxm0Xz8DHPe9LAg1DXCAFp59875ldr4XFxlUC6eANn6YOuDs3E 8Zqo5v5Zu328gltOYZQbyKWCzr9j5LJV5p2buxate/6pxebHPBeWTwpVE2HnaZBALKpEx1Wp Szzv1PEGzsVAZTkgp2H+Mq8k8AEbOMTrKGLy1mi82Vs52TIszVxaDdiD1dXSAIOw19iyv0xi lYhTC1ECaeQNbORsXdXkAwPieTNyfntIeWuc66op1QdmrTEbN1hdLWxdnPj+V7fMCFGfYddy SyCNvIEzcvX60ISyQ16RI5439WVF4W3b2BWNtiuthtXVEg+DsBdYsvGp64NX5VaJfma3sbXP /KI6oqtHU0U+lRa6Kmt0VbVcjbaE1FpTVptS3igbOZevP7Voryfk0Lz5v/d8d9iwYd94jOzo zPsG/AI/P5qXbTN+7Ne+Pvb/ZvZ7PA1BNw4vb427cVNabzZuXhq3LGx9hP0nWAIQkPbh5Qt+ 1Ln0xwTjjcoTrdg0XW4a1t6clxjipJc3cB7f+fDayFc72HmQ400GJ9/7UZY3wJ6v3VNz/6ya 7339F7dn8UPe+OdNeHlrNNgcXDHOcucGIgWeG1Fg4UxbtDjB2hCXFrYE+i/0SA8OnxPkwxuw aAhYKPD4nJCsh6WaN3BSTr/zCeT2Z0SOyhvgyne/N3737Ta80T73zRuYUlvRmFA9adD5i5Xl lrz5c3WTGTZYXS1sdZzs/pNdIjoYb4hvRPnJ2jEaeGTFhu95pZ03ILgj/R954o1qzeR4o/nT wMrR/qoZQ4yd083WVlaFDRvLotEEP1OmVJl5g9XVks2DUFfX0FXiW0PF4sBgvNG8ZcqWTV5z xpuWGA+a/vwhbxR57O59j4UKCkLAkzYs6ysz2DHZv8IWjtJG+ck42Tzv38yqaAsbNtB/SfUy S+PGsrQaVlcLVR0nu/M0VFFj4A0FEJ27DH7J/SkLGvSnxeJbRpBJbu76qytyFKI89ouc9UtB RY0aUFCU5ZAaMuDaLd1gdHHn/tm/DJs3DsaNubQaqa42t3xEstUiri4MCaQBNqB23HijWCwZ y0X5od9n9mpM9g0JWlPbK79p74PoOAmORfsmdxIqdpx1ZoMhHlpv32Q3daCN+vm8b2RC1Dzx ZkfJlLBh42Dc/HLZJstIgcKZmBAac9h4lkBKYMOmxqm4Z52vzC4emv48KbRJczy05VWyaNsp Bzw48Ea3baP600i0NDtvQs1bo2Gst+i3lp40+PCFykbLSAGsrhbGd/9k94mwYeNQulqhfWM8 3w7ICfV5z6llHQIsG7ui0YRA5tJqxJn2cvkDyVaOuDq+EkDYpAsjzKtF3liIyg454fEG8taE V26ApWg0wMaytBpWV+OriNPQG8KGWf2mriHyxvqUWyInPN6EnbfGtWi0XWk1rK6WBkJwXCPC JnUM8bJg5I2ttGp2D7BvvQRpuXhloxhPWu/cey2LRgNsIFLAcudm8qhijsoIu0q2BBA2XnRv Gtsib5zOem37W0FAwnLsuCVdh/LvEsObTasK7SIFLEurAYGwulqyCcFxdQibNALE45qRNy4C CxU5YvLWOBeNBgLZlVZTNm+wutoKz3HAHJV4XLpC2HhUvCltjrxxP/HhIWdjRZkYywZG2V09 0864sYsUwOpqcVH30c4TYeOuRLBFRgLIG6YLgSX7AIv3THC5Adei0YRAlqXVwLhZUrwkWkWG o8svAYQNkwbBRsgbT9dA5/H32TNJu7JHTN4ajTcOxs1jlRalbkjswIKKp+XXdzjDCCWAsPGk Q7Ax2jceroHj5y95qpdjRx3glpi8Na47N4pxY1VaDWDzyvOlESoyHFp+CbTsL/Nw82BTlAD6 07xeA29d/NRrVVAzdWqq1gjbtnEoGk0iBcY/8Zp1DhusroaRAjYSmF15f8+pRq/3DrZHCaB9 4/kauHRlcELZIVePmV0DYXlrXItGA2/sSqsBgeZXPi7/V2ycoXgJFK559J0P+jzfNngASgDt G3/XwNXrQ7PWvuEDOaMWdIjJW+NaNNqhtBrABquridfjsRixdMszV65d8nfX4FEoAbRv/F8D zsmkLWnUsnSmSE8ajPVCeaVdGLRdaTUlMm1ZQSzUH05SpAQ27Z43dHPQ/w2DR6ZeAsibQJeA p0dzSlfWC4bNwRXj7GADn89YtMVy5warq4lU4nEZa/+bdYFuFTwYJYD+tODXwIG+v7MErU0q 7XTNW1P3s/+hFg/9H8+PvT0Dp+88SD769+9kWTX2Gz/4X9+oU/7k/rIrGk0SplmWVgMCYXW1 uDBAzDznrXyo/0JP8DslwT2c2bjB/KLWCyU9qZppDOWi9TVAA0lO7UpXuDpQjwEORvsmgPDU Q9/58NozS/c7bOdAuYGugifcCPGdB1WQKODJAAbe/OBntx2eftvz/+sfF2XxQ964vxyKRjuU VlOcacvnilFkOIr8EijZ+NSHly9wuEkS3QV33oQgLeRNCEKNqsvBoS8WbDlhhxyveWsW/fuw DGaMvIHPHxzhThpCIwfjxq60GsBm4mMLsLqa/BgQM8Pa1pevD16N6p6K0bgBeKOYPsXFw4kX QzOCCBzgb1rtac0oyhWazrZW2ublKT1kGhsLUWe6alZHyDay7FmAwNG+4Snk1/dfMCOnoKqV xRwhdMn60zTvmepPA/yotg4Tb5yNmzHVDZY7N1hdTYwej8Uo+Dgnu2oIxhuVM5QTLWuM5LCg WieUlaI66TKA0Uild93BEiyOhE/NPbOvNkBL5E0A4VkdevqdT0YVdWnUeXqx+7aNmUYKeAyb NLBtAxCCfzNEItaPw8vZuJn+6no73pSsmBkLbYiTDE8C8Djn8YF2zjdGorsLxhsLVqiQULFA QUPd4lX+Vw0azQoiJKEtJRveaMAR62ZD3vC/D+CB0MmVhwE5kLdm98LxjMaNvhmECWghAyRq QNm2yfrT3EIGoK6aQ1iaXWk1IBBWVwtPicelZ3ic8+JH5/jfFYnukYE3FBJ08QK0PZJ7r1GA AEf71SrUwJIYOepY2zeq3SMWN5gfOrTboGLHWW95a0b8Yy4IDd5nAJOBEAQLZNmj7t/kIgss YeZQVw04NLXc1pm2uGB5XNQizjMMCaxumYGPc/pQCW68yRgdqhmjjz1z4U3GPIHdGRVXFsCx Q0a2qR1vjD37WLb3Q9C+8S4z5iM+Obv/2LxfMNs3wBXNVs4Foem2bVR/mkPUgEPRaOfSalhd LQwNHpc+wYeGT9gw39k+GlLb+LT3SyGRgz+N7L9kHWdkVFNHOt7Q0QKkY51tpPrgcj3pJuNj Xd4OQd54k5fX1jevX/nrltnMyGGKBXDuzdm4sSutBrCZObYkLsoR58lXApClBoOevd7aCWhv ii0IfU3Im9BFDAN4NHT8U8fZuHEorYbV1fhq8Bj1tvNQFWapEaEFZBvDai8o7Dkib8KWcLZ/ MYbOjpWzHCIFRpTX2YWlYXW1GBGC11QhNOD8e8cE3QA4DEoA89kIvgZCNXSO5t8xctkqB97Y lVbD6mq8NHiM+oHSnPgsp+DbH4dD+0b0NRCeoeNQNNq5tBrwZmnJwhjpSpxqEAmAWYP50ETf 9jheRgLIm2guBDB0ji/4Ncc4AlfjxqG0GlZXC6K+43Us7tZEc8PjqMibaK+BL4YG/7ZjGS/k OBs3YN9MmVJlt3mD1dXixQx/sy2vn4B1OaO95XF0tG8ivgauXjh+YuGI4NQZXbrSYefmscp6 h0gBrK7mT4PH5Sh4tqard0PEFzoOjxJAf5oM10BwQ8e5rppDaTWAEFZXiws2/M0TcjxjygAZ bnOcA+7fSHQNgKHTt3y0P0PHoWi0c2k14M1rs8r8KTI8SnIJwFOcGO4s0R2OU0H7RrZr4PLJ Dq9xBK7GzQuVjU7ONKyutuIeycnhdXoQgdZzqlG2axvngxLA/RvprgFwr13sWNU7+78YbR1n 4wbsm8kTy+x4g9XVvKpyydvDVg1EoOGDNdLd1TghjE+T+Rq4ceWjt7e96oqcI0tHO4QJwJ8c SqthdTXJ4eF1erBVc/nT92W+qnFuKZcA2jdSXwDX3jt7puJp33XVgDcOpdWAN4vK/+JVqWF7 CSVQ3TgZt2qkvpNxcmjfxOUa+PStI5bUcS4a7RopgNXVJCSH1ykhaeJyF+M8MT4tTteAmTrO RaOdS6spCaEXlHrVbtheHglg+Fmc7l6cK9o3cbwGNOq4Gjd3LVr3/FOLHSLTFpZPkkd74kzY JQCk6Tu/L45Xb1LnvO/UZvOLWqy+0IyuEICuQJpW/IyUg1Z+xNZDC/sE4f5N2BIOpX+gzvrm OudIAYfSalhdjV25S9USctIgaUK5o4J1GpA3hkrTuoLTzXlJIg7yJtiFFunRf/34k7nb94Ed YwmeaXNqnR67KV4ilSbFyThLYNPueZj9LNK7zWlwTrxRiksPz8sbnqswLe2KfU4MeeNTcPIc 9vHVz/6/X/zq/uWbaeo4l1YDDhVUjEYVL78E4Hmahq4SjHKW53aznAkf3iiuteHFxcCc4n7J F+x3esgbv5KT5ri6uroHHnhgcOhm84mB31W/TqjjUFoNq6vJjxmYIeQIgCSb+OSmNPdZiPaN uleTsWsUGwd5E4vTnspJAmwAOdrSD5x/d0pd2/gnXnNwpmF1NZmRA5s0vWdaU3ktx3XRDPYN xRBTvIC6f5NZvu6vcRWI3bzRvon3Gb148eI//dM/mdfw0QefNK7vnDFmiSV15lc+LrPCTefc wKCBVDToOovjDenGG8Vo0TZldOEAFnjJRKxpCILfdDiKo3hyc0bexPv85Wd+HNZw8uhATUkD FB3QwPPqNEwILVeCztUtM44PtMf7QsTZu0iAinvWucsszRk6SDpBtMH80HG/TcC4ARPHdRWf Xb3euf1IwZSVymOeywrSaUDIturi2ifQoHG9dLFBkiSA9k2MzyaJFPC0gIt/+2jXwZqSjU/J pnzTMx/ATMv+sosfnfN04rAxSiABEkDexPgkGiIFPK3kw8sX2g6vRvAI4xxsz0BkMz5D4+kq xcYJkwDyRuwJzeSpoDyyat4KenuQLRrSLlLA63oAPBB3CylShGneVA0E1gxgBpM3e70ssX0i JYC8EXdaSVwKnUoJtgUzcNFiUPR5lhyn5hop4HVhEBm1/8062LtOFQ9CWiyIEYQJLPd6FrA9 SiDBEkDeiD65DrzxQJtbtxgjBfwtr/9CD2xlo9HjiUbElIH8ZkM3B/2JHY9CCSRbAsgb0edX D5WsPw2sHNXWYZqPj0gBpn5NjeD5dgjVrWsvAmXqSfmmpDHsykBmMzRl/F1deFTaJIC8EX3G rY0Y4lFTw+5dd3CCRAr4XjA43IA9EFsFNb5SghPLZYLZB3YMiAKfzfR9LeGB6ZQA8kb0ebfi Tfaz7H9ulg6vSIGAK4dQK/heD6ZP4oPcYIG1rS9DOB+4GdFXFvCywcPTLAHkjeizb+JNDi/q n1xKXnCPFAguAnC7QQgW4IdYP/NWPhRfAwhSMsMSYCE9pxoxriz4tYE9oAQ0CSBvxF0MuZp9 VN0+nTGj+tPoFBZ33nmnlj6WvPnqV7/KklNA3MKsRjIQSFobCJxjQBewXQCWQBd0kUV72eDo yZYA8iZZ55ff8z1hyAWcUaDT4QVP/ICKh5120PVh7wbBlj4ZBWKUYVB4EcPlyrVLYawR+0QJ oATsJIC8Sc61wff5nkjkogEJeACBxQQPjC9CMu2FlkokZxAHRQk4SAB5k7TLg9fzPUmTC64H JYASiFoCyJuozwDv8bk838N7UtgfSgAlgBK4hbxJ2kXA5fmepAkF14MSQAlIIAHkjQQngesU gj/fw3U62BlKACWAEshKAHmTtEsh+PM9SZMIrgclgBKQQwLIGznOA49Z+Hu+h8fI2AdKACWA EnCXAPLGXUbYAiWAEkAJoASCSwB5E1yG2ANKACWAEkAJuEsAeeMuI2yBEkAJoARQAsElgLwJ LkPsASWAEkAJoATcJYC8cZcRtkAJoARQAiiB4BJA3gSXIfaAEkAJoARQAu4SQN64ywhboARQ AigBlEBwCSBvgssQe0AJoARQAigBdwkgb9xlhC1QAigBlABKILgE/n/nw+EfZ4S+dAAAAABJ RU5ErkJggg== --------------040701070906020708020505-- --------------010702040202080003090402-- --===============1086458984947120423== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users --===============1086458984947120423==-- From xen-users-bounces@lists.xen.org Mon Sep 17 11:33:11 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Mon, 17 Sep 2012 11:33:11 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TDZYj-000557-NN; Mon, 17 Sep 2012 11:32:13 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TDZYh-00054o-Up for xen-users@lists.xen.org; Mon, 17 Sep 2012 11:32:12 +0000 Received: from [85.158.143.35:23491] by server-3.bemta-4.messagelabs.com id 77/0D-08232-A3A07505; Mon, 17 Sep 2012 11:32:10 +0000 X-Env-Sender: lars.kurth.xen@gmail.com X-Msg-Ref: server-10.tower-21.messagelabs.com!1347881511!10495837!1 X-Originating-IP: [209.85.214.45] X-SpamReason: No, hits=0.9 required=7.0 tests=BODY_RANDOM_LONG, HTML_30_40, HTML_MESSAGE, ML_RADAR_SPEW_LINKS_16, RCVD_BY_IP, spamassassin: X-StarScan-Received: X-StarScan-Version: 6.6.1.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 22698 invoked from network); 17 Sep 2012 11:31:53 -0000 Received: from mail-bk0-f45.google.com (HELO mail-bk0-f45.google.com) (209.85.214.45) by server-10.tower-21.messagelabs.com with RC4-SHA encrypted SMTP; 17 Sep 2012 11:31:53 -0000 Received: by bkcji1 with SMTP id ji1so2152604bkc.32 for ; Mon, 17 Sep 2012 04:31:51 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=sender:message-id:date:from:reply-to:user-agent:mime-version:to :subject:content-type; bh=O9f1qgevS4UMn+byKYSSZLXZAdF/aJIKWb5QlG2QyrU=; b=A2hyECCMOXB2mvalKzBIBl3QQM8FBp4t4drCSaJ9rPEbi/gEzbmFhI0HsZB7bCWL08 VCxwm9kSNU1V/cugqwbe+IZH/7oQCKPm+TPRjmMiSsVMUSYak+grmS6gNev5rL60ctwK jQo42C1vJ2K/PWr2Mw4y6JW9qay5T/1nJjbiN+Miqx7pvFgfPLd0YRFyyh5QasI0f6o8 f0AZfliV6bLpYk20Uo9XF2LX0KbWVm1Ow0LSJyquL6dw4voxXnagkVRdV6If6pBXV8nC HTB9LaGxKxOJDwVjzSM0vJvX3t1oGhP/APKud7Fb/cUawOkeiAjNhI7f5u+009xRp6xz l6ig== Received: by 10.205.120.16 with SMTP id fw16mr4054797bkc.102.1347881510902; Mon, 17 Sep 2012 04:31:50 -0700 (PDT) Received: from [172.16.26.11] (b0fb5b35.bb.sky.com. [176.251.91.53]) by mx.google.com with ESMTPS id n5sm5166099bkv.14.2012.09.17.04.31.49 (version=SSLv3 cipher=OTHER); Mon, 17 Sep 2012 04:31:50 -0700 (PDT) Message-ID: <50570A24.2000905@xen.org> Date: Mon, 17 Sep 2012 12:31:48 +0100 From: Lars Kurth User-Agent: Mozilla/5.0 (Windows NT 6.1; rv:15.0) Gecko/20120907 Thunderbird/15.0.1 MIME-Version: 1.0 To: xen-users@lists.xen.org, xen-announce@lists.xen.org Subject: [Xen-users] Xen 4.2.0 Released! X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list Reply-To: lars.kurth@xen.org List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============1086458984947120423==" Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org This is a multi-part message in MIME format. --===============1086458984947120423== Content-Type: multipart/alternative; boundary="------------010702040202080003090402" This is a multi-part message in MIME format. --------------010702040202080003090402 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 8bit Dear Community Members, Xen.org is pleased to announce the release of Xen 4.2.0. The release is available from the download page: * *Xen Hypervisor 4.2.0*: Download (archives ), Source (tag RELEASE-4.2.0) This release is the culmination of 18 months and almost 2900 commits and almost 300K lines of code of development effort, by 124 individuals from 43 organizations. New Features The release incorporates many new features and improvements to existing features. There are improvements across the board including to Security, Scalability, Performance and Documentation. *XL is now the default toolstack*: Significant effort has gone in to the XL tool toolstack in this release and it is now feature complete and robust enough that we have made it the default. This toolstack can now replace xend in the majority of deployments, see XL vs Xend Feature Comparison . As well as improving XL the underlying libxl library has been significantly improved and supports the majority of the most common toolstack features. In addition the API has been declared stable which should make it even easier for external toolstack such as libvirt and XCP's xapi to make full use of this functionality in the future. *Large Systems*: Following on from the improvements made in 4.1 Xen now supports even larger systems, with up to 4095 host CPUs and up to 512 guest CPUs. In addition toolstack feature like the ability to automatically create a CPUPOOL per NUMA node and more intelligent placement of guest VCPUs on NUMA nodes have further improved the Xen experience on large systems. Other new features, such as multiple PCI segment support have also made a positive impact on such systems. *Improved security*: The XSM/Flask subsystem has seen several enhancements, including improved support for disaggregated systems and a rewritten example policy which is clearer and simpler to modify to suit local requirements. *Documentation*: The Xen documentation has been much improved, both the wiki . This is in no small part down to the success of the Xen Document Days so thanks to all who have taken part. You can find more information in the release notes and feature list on the wiki. Upstreaming The Xen project continues to work closely with our upstreams. Of particular note in this release cycle is the upstreaming of the HVM device model support into upstream qemu . After the Linux dom0 support (merged upstream in 3.0 in the 4.1 release cycle) the qemu-derived device model was the largest remaining piece of code which required upstreaming. Support for Xen was merged into upstream prior to the qemu 0.15 release and is supported as an option using the XL toolstack. It will become the default in 4.3. Alongside this support we have also gained support for SeaBIOS (a cleaner and more maintainable legacy BIOS, used by default when upstream qemu is selected) and Tianocore/OVMF (a UEFI BIOS). Support for Xen has been merged into the upstreams of both of these projects during the Xen 4.2 development cycle. More Information Links to useful wiki pages and other resources can be found on the Xen support page . Thanks Contributions were made to this release by 124 individuals from 43 organizations, and that's not counting contributions to external projects such as the BSDs, Linux or qemu. Many thanks to everyone who contributed to this release, either through code, testing, documentation or in any other way. The diagram below shows organisations which contributed more than 1% in lines of code to the Xen 4.2 release. Several items in the diagram discribe groups of people or organisations: /Individual/ covers contributions by individuals whose affiliation is unknown, /Misc/ covers contributions by commercial organisations which did not go above 1% individually and /University/ covers contributions by Universities which did not go above 1% individually. Xen 4.2 Contribution Stats I did also want to list the top 20 contributors to Xen 4.2 (in terms of commits/and lines of code). These are: * Jan Beulich (338 commits/40357 LOC) * Roger Pau Monne (87/36932) * Ian Campbell (504/32009) * Stefano Stabellini (124/29130) * Ian Jackson (174/27900) * Daniel De Graaf (79/11103) * David Vrabel (45/11075 * Tim Deegan (143/8790) * Christoph Egger (67/8590) * Matt Wilson (9/8508) * Andrés Lagar-Cavilla (115/8050) * Keir Fraser (143/5593) * Wei Wang (34/5577) * Anthony Perard (45/5289) * Olaf Hering (154/4296) * Qing He (20/4179) * George Dunlap (75/4088) * Dario Faggioli (30/3742) * Shriram Rajagopalan (21/3481) * Jonathan Davies (3/3230) For a complete breakdown see the Acknowledgement page . A big thank you again! Best Regards Lars --------------010702040202080003090402 Content-Type: multipart/related; boundary="------------040701070906020708020505" --------------040701070906020708020505 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit

Dear Community Members,

Xen.org is pleased to announce the release of Xen 4.2.0. The release is available from the download page:

This release is the culmination of 18 months and almost 2900 commits and almost 300K lines of code of development effort, by 124 individuals from 43 organizations.

New Features

The release incorporates many new features and improvements to existing features. There are improvements across the board including to Security, Scalability, Performance and Documentation.

XL is now the default toolstack: Significant effort has gone in to the XL tool toolstack in this release and it is now feature complete and robust enough that we have made it the default. This toolstack can now replace xend in the majority of deployments, see XL vs Xend Feature Comparison. As well as improving XL the underlying libxl library has been significantly improved and supports the majority of the most common toolstack features. In addition the API has been declared stable which should make it even easier for external toolstack such as libvirt and XCP’s xapi to make full use of this functionality in the future.

Large Systems: Following on from the improvements made in 4.1 Xen now supports even larger systems, with up to 4095 host CPUs and up to 512 guest CPUs. In addition toolstack feature like the ability to automatically create a CPUPOOL per NUMA node and more intelligent placement of guest VCPUs on NUMA nodes have further improved the Xen experience on large systems. Other new features, such as multiple PCI segment support have also made a positive impact on such systems.

Improved security: The XSM/Flask subsystem has seen several enhancements, including improved support for disaggregated systems and a rewritten example policy which is clearer and simpler to modify to suit local requirements.

Documentation: The Xen documentation has been much improved, both the wiki. This is in no small part down to the success of the Xen Document Days so thanks to all who have taken part.

You can find more information in the release notes and feature list on the wiki.

Upstreaming

The Xen project continues to work closely with our upstreams.

Of particular note in this release cycle is the upstreaming of the HVM device model support into upstream qemu. After the Linux dom0 support (merged upstream in 3.0 in the 4.1 release cycle) the qemu-derived device model was the largest remaining piece of code which required upstreaming. Support for Xen was merged into upstream prior to the qemu 0.15 release and is supported as an option using the XL toolstack. It will become the default in 4.3. Alongside this support we have also gained support for SeaBIOS (a cleaner and more maintainable legacy BIOS, used by default when upstream qemu is selected) and Tianocore/OVMF (a UEFI BIOS). Support for Xen has been merged into the upstreams of both of these projects during the Xen 4.2 development cycle.

More Information

Links to useful wiki pages and other resources can be found on the Xen support page.

Thanks

Contributions were made to this release by 124 individuals from 43 organizations, and that’s not counting contributions to external projects such as the BSDs, Linux or qemu. Many thanks to everyone who contributed to this release, either through code, testing, documentation or in any other way.

The diagram below shows organisations which contributed more than 1% in lines of code to the Xen 4.2 release. Several items in the diagram discribe groups of people or organisations: Individual covers contributions by individuals whose affiliation is unknown, Misc covers contributions by commercial organisations which did not go above 1% individually and University covers contributions by Universities which did not go above 1% individually.

Xen 4.2 Contribution Stats

I did also want to list the top 20 contributors to Xen 4.2 (in terms of commits/and lines of code). These are:

  • Jan Beulich (338 commits/40357 LOC)
  • Roger Pau Monne (87/36932)
  • Ian Campbell (504/32009)
  • Stefano Stabellini (124/29130)
  • Ian Jackson (174/27900)
  • Daniel De Graaf (79/11103)
  • David Vrabel (45/11075
  • Tim Deegan (143/8790)
  • Christoph Egger (67/8590)
  • Matt Wilson (9/8508)
  • Andrés Lagar-Cavilla (115/8050)
  • Keir Fraser (143/5593)
  • Wei Wang (34/5577)
  • Anthony Perard (45/5289)
  • Olaf Hering (154/4296)
  • Qing He (20/4179)
  • George Dunlap (75/4088)
  • Dario Faggioli (30/3742)
  • Shriram Rajagopalan (21/3481)
  • Jonathan Davies (3/3230)

For a complete breakdown see the Acknowledgement page. A big thank you again!

Best Regards
Lars

--------------040701070906020708020505 Content-Type: image/png; name="Contribution-stats2.png" Content-Transfer-Encoding: base64 Content-ID: Content-Disposition: inline; filename="Contribution-stats2.png" iVBORw0KGgoAAAANSUhEUgAAAiUAAAHFCAIAAACiox6jAAAAAXNSR0IArs4c6QAAAARnQU1B AACxjwv8YQUAAAAJcEhZcwAADsMAAA7DAcdvqGQAAAAadEVYdFNvZnR3YXJlAFBhaW50Lk5F VCB2My41LjEwMPRyoQAAa3ZJREFUeF7tvXlwFde16M3/r24q+ePWu7deqpKbSt3cylDlm9RL mffl+jp+uY6f4ziO4xib2DFxsAgeGBwMBDAyxgyWkAUIEEITiEHMEtYEYtDIKEDGDAIkTIxj Y8c2+BowFsLmW3326T67593du3fv7l6qU3B0tHsPq7vX76y1V6817Bb+oARQAigBlABKIHwJ DAt/CBwBJYASQAmgBFACt5A3eBGgBFACKAGUgAgJIG9ESBnHQAmgBFACKAHkDV4DKAGUAEoA JSBCAsgbEVLGMVACKAGUAEoAeYPXAEoAJYASQAmIkADyRoSUcQyUAEoAJYASQN7gNYASQAmg BFACIiSAvBEhZRwDJYASQAmgBJA3eA2gBFACKAGUgAgJIG9ESBnHQAmgBFACKAHkDV4DKAGU AEoAJSBCAmnkTX/x8GGZn+HF/UTG5k/CkL2YUcKYOfapSUDYSRQ2EOeTq82bvsE4j+HSXVxF J1ZKkYwWEm/oi47o9rzmSNZnNWhzHplSblJiLlDzuNKIJMBEcqvS8G2AuNBzr7vyDDOyWGVu 9oavIHYS4XkStb6sbg6eAwU4vd4ONd73znd9WFpCzO3sTTLYOiMB/rwxX0Sqdne/+/2cFO8X V+j2jc2UvM/UjzyYjuE5FeqE0+pF05fhnHabZer54Ti0ETXqZZoze63G4Ck5R97wHIjpmuDQ iH3OoWoJ9mlwWDN24UUCnHlDX0a67zbKrRWO4uFxcfHog5I65+68nE/GtnxnaGHi5C4EkYZt diLDhxsdpnZmbu6S1ClAQXN25A3jmZSqmboglzs9bC3B9+qWSsJxnwxX3th80w1XRjwuLh59 pJg3t24ZnT+RGDfZszi8uNm0QcdyCVJXbzjfjEyTSBpv2G6j8LUE2zxYrglsw1kCPHnj7Tut yaK2cf9nvmvSvg+qnaVLJPt39bsuxAQY7msXf5quU903Xe1Ak+mWiz5wmJLtbcBDFNnrwtCV 88aA5kEy2J5u87G4BnVKxPFCMAhIf9bVI51Out0dkO0YDvWnb9h4Y3/xeJ+zR3+aN+E4ylmR IcOlohO141Vh+qMuHofuh6+WID0b1IPt+XeVCWftit0ZJcCRN7kLyfXrIYvrXO1Oc45Q2lHd gWbhjepbycUHOPCGHsO87RQGb3iJwqxADDER2pl3Epr+1tVJw+2kWnRrop3NYnPtWE669U2s GTcQchiYNw7+NPuLx+lCtZ6zT964D8QsZ/31br9s16uUmTectYQJm7bXrKtMEA4CJMCRN0af iu3sLRpaXIX0FazqOqvvRnbKxer6IjeUC2+yd53uGztZCwtvrAfQH55T3TxFYeE8Vz6yVCLu QtMOY1cQLt8eLcY0KVzWk268tjROZSLcffGGmr3T9o3zxeN0oZrvB5+8oU0HizuCQc5eLhWd +eB8VbDIPTQtoYreYOsY7lyLW0/QZp0AZR6DIcTzxuaiNN04lu0sPnRXncZABSeVQX+Lt5+S gz/NC2/4isJCidhegNYjs87HrlsdcIz2kCWsjR+ynnTDDNSBjV8V3GyyXDfU1J0Pcrh4LK8d p9788sZxIBY5e7lU7OjNRjrTpcLIG8ZL0bqZNoYJ//SNa/3tMQY6O85TFM8bu5vMeJG4XErm b1qGO9v+ZmZUGZRvKds1b/uGsyj09oWj2mQVLrm0Tfev5RVvMij1M7B1ydBPQnmbV3YaeuPG h31DW1Vu33ZZLx5HlmQnzoM3xs1J3V6G2T2cXZ6HS8U0gHryzVcFR/uG8dawbmaaB9O1F2c1 Hpu5c+RN7q51UnW216TxD6yqx9W+MWkQVpVh+mbHmTfcRWHcArZ/wtubHcGiR6ivu3mm52lp BlhtkWleP9aTTt1fFieFZb4+TBsbp6iPOYfIG5qdFqK2cIi5PB7HfJWy+TG5agk3K8j4PdHx 2ouNzo7zRDnyxhQUay0X128ujk4R89Eh8sbW5OLkT+MtClXgep1j9Y3dm45k+K6uE5WVTmFj gLd56Y0va2XiktrCi2kTL96w+RLdLxV3+8bV1aBTBGwONcZbg82+Ybv24qzGYzN3nryhgONw sTN+J7FxG4fMG93uOvWVnSTjsZy6hbMp2BLNw/jQwpQXzOpcWPfIOm93p7yFUmFyyvlYqcsX eo03VsYp5Wdx86OZWK6J1cecQ7RvGJ2f+lOoysHytmW/Ktj0ek7owbWE5UVl/rrDdO3FRmfH eaJceaOLpjV7703Wba6JxTdi5tvY5quQ/Zdyc886nWWKT3MIJ6Mdw9SC2b520bGcwUWRWQOl NZ1vfpcZUiEW7g4QR3Mm15ONnlE+5qC76ZvQaunUKTYHILLZArGwb+h7ULcsSs7eLhXKS+t4 lbL50xQhUndNUC1hvqgsb0mWay/Oajw2c+fMG8dweLNWMblAXPWllZ6kr7DcloUf3rg+2WD1 ZVo9iL51LKfkogYNwvAqCpvv+Xaq1FpoFjtA6rTsDAA7Hlnc4oYxcwuOgje2k8lMy5ZADl9W TOqdjoSw0gi2U1BkHWAgNzl7vFScbmrdVcFm3+g8BWYnqDctYf3AmMUt6SaT2GjseE+UO2/0 XwJzl5Prs3/GO5zZvqEdXbmHOm3dzk53su4+t1E7ZlsoeynrF2BhMtnejsZ7wa8ojHrE+Wu7 lVFHLma3+VjaEqYHfaxBZNJ1ukl6Oen2N55lL9qHliFaRr0XKW8ygwfgjaVGd7g8nfiak7L7 VcHOG25awtxR5vRa3pLmL1Me7Np4q3lpZh8Ob6RZHk4EJYASQAmgBCSRAPJGkhOB00AJoARQ AgmXAPIm4ScYl4cSQAmgBCSRAPJGkhOB00AJoARQAgmXAPIm4ScYl4cSQAmgBCSRAPJGkhOB 00AJoARQAgmXAPIm4ScYl4cSQAmgBCSRAPJGkhOB00AJoARQAgmXAPIm4ScYl4cSQAmgBCSR APJGkhOB00AJoARQAgmXAPIm4ScYl4cSQAmgBCSRAPJGkhOB00AJoARQAgmXAPIm4ScYl4cS QAmgBCSRAPJGkhOB00AJoARQAgmXAPIm4ScYl4cSQAmgBCSRAPJGkhOB00AJoARQAgmXAPIm 4ScYl4cSQAmgBCSRAPJGkhOB00AJoARQAgmXAPIm4Sc4jsv74sub/33t7/Trw/++cOHvJ7VX deMRy9fa7W/0nnmPvD7+78/iuHacM0ogwRJA3iT45Mq4NMKSy1cuEnicfLsDXvtObfb0unNs Bfvr7nHVE4qb4DVj+U6glMakwRs3ZRQQzgklkFwJIG+Se24jXdnQzRvAlY8/fRegcv79YwCV 4+f3eIKKQ2N22Li2HD2nDlC0or5n0+7jaBVFesng4MmXAPIm+edYzAqvXr/8weW/vnXxKEeu 2CHHlSJBGhB7aH5NJxhDF3t7B69cESNAHAUlkHgJIG8Sf4rDWuDnN67Btsrbfz8OtsuBvjpe tgtLP0Fwwn7so8+XV/30DnhtfPTh3S9OP7qyCvBzc3AwLIFivyiBpEsAeZP0M8xvfTeGrpN9 l1MXug+d2cYChpDasDMjSMtZ05cS3hheW554rH32rL5t9Z+8/TY/6WJPKIHkSwB5k/xzHGSF wBjwkp3928Ej/S0hwcNHt0Eown5sxfT5lryhPwTTp+vVeWdbmq9cvBhEzngsSiANEkDepOEs e14jbMb87cPTx97a5QMGAg5hZ0aQlhsmvuDKG7oB2D37iovO7d6FPjfPFxwekA4JIG/ScZ4Z VgmRyhBOBhv+PWcbBTAjyBBmivx0bIWPlzONNoz6vSfe0I1bp7wADjc0ehiuO2ySIgkgb1J0 si2XCtv+Fy+dgy2ZIAAQfKwA3vy/5yp8w8Zg9BxcWgIPGqX9OsP1owRu3ULepPQq+PSzj+Gx mN5zOwSjgstwAngzfuoKLrzROqn9zQPgbYMIt5RecLhslADyJm3XAOz/w8aMVJv/PggkgDcL X1zIlzdabxBiABbPx/39abv2cL0oAbRv0nINwLMy8XKaecovQDZvfvx/vjUs+/Otb48kOzrj /5l88t3x2Q2ekSO+8j9H/DjT3mH/Zs3Ul0LijdYtxBfAMz0YVJ2WOxDXifZN4q+Bzz7/FB7J lD8EwJOVY2PfjP9nFSQKeDKAgTdf+T9zfjp2zrf/5x0/yOKHvHHhzaZnngubN1r/LRPHQ1Rb 4i9FXCBKAO2bZF4DEGwGz80ISC3jiRO8Grv6037w3WEZzBh5A5//8725SDYH+2b1ffcK442W xeDY2jWYPieZNySuKiOBZPGmOQ8cJ3nN2rnN/E5/1F88fHhxsh3nEAgw8N7haJ//58UV9vxp Rn+a5j1T/WmAH9XWceeNlslGMHJguFU//xk8QIpONtTPiZRAcnijsCWvGf7VeKPCBf4nn9F/ TNrZBIMGwppjGm/mlU+u9o3iT1N9a7ltG4AQbN5kvoEQ68fOvrHLZCMSP+hkS9otiutJmn2j R4qBN0mlDWT+h5CzhO3QOBPIlTeZMAEtZIBEDSjbNll/mhoyYMcblkw2YtgDwWzoZENFnRgJ JMe+IadED5WsPw1caIl0pAFpIHtmsl1nluCx5s29d+SC0OB9BjAZ4waCBbLsUfdvspEFdrzx mskmbPagky0xCjflC0k2b9STSzxq8G/Gl5KAHRx4jAae1kwhaQh+bOwb4IoaDp2DjRYykGGP 6k8jUQO2vAmQySZU9oCT7a9dnSnXWbj8+EogDbzJ2jzZ/2Ju6RDSCK4343V/Jez2DP40pnRq lrzhlckmPPDUP/XkOwcPxFfp4MxTK4HE8yaHF9XV1pwXTwMHEp1B4FnYqjwW/YfKG+6ZbEIC D9g6mKQgtYo7pgtPDm/U2GfiUckiRWfMqP40LYDtzjvv1Pwv5M1tt912+fJl2c4lPLOJpKFB GCpvwstkEwZ4oPAoZqGW7YbF+dhJIDm84XKO9+/fDxC6fv06l96CdwKkOf3OvljYHCInGaSq jeuxAjLZcAcPJGT77OOPg19v2ANKIFQJIG+M4q2trX3kkUdCFTpL5xB7Bnlo+O/TlP0XmHH3 lym77tlX5hPy8/2pJZkPp99Pfn94erbN9lHfv23UBu2QqN+4MiNIg01jxvLiwcRs7jYQ5T9N VOpSf/8/iWD/+fvZIX78rW995VvzrapWe50DxLBBNjZMT8Byc2GbqCSAvLGQ/Lx586ZOnRrV KYFxIbdmGM/TFD2sIAT+pXgDaPnXcdsz7AGoZN5vmPqvGfCUjLvtv4qy+CFvZHkFwYnrsbwy 2Siw0biSIcr8b//Dt779v6t++r8f+YqGH/KG2wuqHpzYtBELjEZ48+LQDhJA3lgLZ9SoUdXV 1eIvHSjkHHbSMx1vwLjRjJhTm+FPQBoDb/R8kgI5rszw3YBfJhswZYwsMfAGgPSfP+BGGhpa 8JQoJgAVf/PiiK4SQN5Yiwi2cO655562tjZXCfJqAA40CHQWYEPQ/AC00LxRSZP1p1HskQIz mnB848T1wLkzSvhYG4qj7B+06giqoZP1p4GVo7InFN6QJWDYNK97E/vhJQHkja0kIVDt9ttv 7+vr4yVrh34g9ZmwhzcZeKPSBTxsYP0ofjZ6dyd69rhiw3cDbplsgDc5+0bBjM6Ugb+Cq01p o/xknGyhgKfmwXs375h75dolAdcwDoEScJUA8sZJROfPnw87QhrSOR97a5cAs0YbwoE3xJ+m tgQrR9m2ybaXKWTAN05cD+SWyUbHmzv0rrOsqy37Ib+QATO01tRMyl9xz7yVD/WeaXXVBdgA JRC2BJA3LhIOL0IaMgVE8lSNbj9GjRGg4wUyvIFggWwcgdp++v3ShKi5YsN3g/W/e5STqQFB AapNo7DnHx75MbFg4PPsexVC3/9PTiFqhpnXjv89wEZ7rW6ZgYZO2PoU+3eWAPLG/QoJI0Ia MjoLc6DRlg31fKsalkbFQ2txa+pGjha3phyni6KONFbNN06cD+ScyUZ1l4HoNGeabttGbRBS 1MCy2jE0b9DQcb/VsUXIEkDeMAmYY4Q0mDVhR6CJ9M5FMlZIvIlLJhsWC2xj8XgDbNDQYbrV Q2xkLAcZ4lCydo28YT0zXCKkocazeLMmEiSEOmhIvFky4zUWVS5/GwgTKKgZYccb+Hx25f1d vRtYL31s5yYBywvScJCSWysvbzhdf9it2+T9HXnDek4DRkhDuHMkuzWh6v2oOg+JN3HMZGMJ PxIm4Poqr5/w4eULrDcAtrOXAANvSCpHJYejruD98OLiXNH7XL2uzFB0Skg1xzD1WfYj6hO1 ZyU1cXG2+opcfEPeeLiNfEdIQxBaGPkColL3kY8bEm84ZrKJ0AYyhAk4UwcNHQ/3fxDeaJmD dRUhFVYQbGSokXlrQBIZFP6sy2qv/q40Vv+Qe0857pS3FOC4rDZAJ8gbb8LzGiH9xZc3IQ1a 5Ao6YRMIiTe8MtlECBsY2hwmgIaOt5vce2tX+4ZKVE+jIwcfijK5tmpG+0yUD8WbXBemesaZ VvSn+hbel8b3COSNZ3myR0hDdmcMDQgDdWHwhl8mm1Ce3GRk2MbC51zpYtkADR3PioA6wI03 +mIpOXY48oY2dOjCKvY0yZX4ytk0yJsgJ1aOY1kipCFlAP/szpFGIYdBDn99hsEbbplswskU wMKblff+zDlMwBVFta0vXx+8KsdNFqdZuPDG4A2zMk8s7BvqqJzfzeBts/WnaT405E2cLiTb uTpESEPE86kL3f40KR7FIoEweMMtk010vGEME3CmTsnGpzCIwKuKcuaNcfMltxvj4k/LmUV5 ENmmbu5oz9ARptjEC2T+Rv6M+zdez6eU7S0jpC9fuYihASzMCNImDN5wy2QTEW8gTAB8Yq4W DEsDyH/Td36flPccTireEsD9G//nzxwh/fc3egf2tQbRpHgsiwTC4A2/TDbR7N+UrX+ahSXs bdoOr/Z/b+CRKAErCSBvAl0XWoT0FzduvNPedmbjBuV1sp1FaWIb3xLgzhvOmWyEmzi+wwSc 8YPbOYG0Ax5skgDyJuhFARHSd/zkJ281NWZhk0HOmwM7fStTPNBVAtx5M3laGcuGvJxtgocJ OFAHt3OCKgg8npIA8ibo5fDp22+f3bKZho3yftvWw2ebXfUmNvAnAe68iXUmGy5hAs7Jb44P tAe9T/B4lMCtW8ibQFcBbNgYSUNcahs39HfuwHhofzhxPYo7b+KbyYZjmICzb61lf1mgWwUP Rgkgb3xfAzeGbuY2bFTGGNhz9nibq+rEBj4kwJ03G0f/UU5fmeusuIcJOFCnunEyPp3jW2Pg gSCB1Ng3VEqhzIlXo9a12HT6CV63S+PqZzda958/2d1jZ9xon5/o3+NDn+IhzhLgzpuYZrIJ KUzAATnFtU9c/Oic2/2Bf0cJWEsgFbwhOevoB59UuMD/2kNTrE9FAWyaugY2tvbBa6C90wU5 dZuP9rcgP/hKgC9v/jCpwtWMkLBBqGECzts5/Rd6UKGiBHxIIBW8IXJx4A37M7iXP71et+cs gQ286naeemvXLmfk9O9swo0cmXkT00w2YYcJOCOn90yrD3WDh6RcAinljeZPIyUpdKm+7a+I v1+6RsOGIOf13X3nGhtckHMUN3Iypak5vfjaN3HMZCMsTMCBOoiclMPDx/JTyxtVVsSjpib+ dgDPxQ+vbNl1WrNs6De7Ok701211Rs7pPnwIVFLebBw3UUJ3mfOURIYJOCAHi4T60LlpPiTl vMk60rL/2Vs659/9xJI02ocHuo9bPIVDx63VbT7Wj6lu+CCHr30Tu0w24sMEHJCDaW/SzA+v a08zb3J4ydWNsDJwzvz1Y2fYkL8e6z7q4lXb0XDozDZePqU098ORN7HLZBNVmIADcvDRHK9q N7XtU8EbfbWjLFJ0xozqTzPHqJ0Y+JAFNqTNmc79zsgZ2I95bjiYOBx5E7tMNhGGCTggp669 KLU6FBfOLoFU8IZdHIaWh068xw4b0vLcnnaXCGnM5hk4aoAjb+KVyWbdnx7lVXSAPVE0Y8tN u+cN3Rz0fa/hgWmQAPLG9iyfPnnGK2xIhPS57S3OyMFsngGdgRx5E69MNuXrn2XU/pE0W90y A5GTBmz4XiPyxlp0N/YsuLri1x37TvhAzo72k84R0v1N9ZjNMwhyOPImRplsNs59JhKKeBoU kJPCnDeWwYQmzWLMcXIrGxdr2DQm7n/i2lcd/aSmJ+sj6b5xEPqByBsLEQNsri+7G16+kdPe edI5XA2zeUrCm7hkspEwTMCOQ6Vbnkkbclh4o2wYQ1VoHTSyn+mAo1SfHq42o3eZM+xhfFQw dHD4HAB5YxTcUHcpgU1A5PR0H3P2qmE2T9/I4WXfxCiTzdqVf/ZkZ0TbOG3IYeANIYfCDMpK yXzYTH9m+MTwiAbJzOVT18twGPJGdxaGDtXQsAmIHNeEnpjN0x9yePEmLplsZA4TcLBy0rOX 484bDRy63FkmCBk/MD4SqBg/xf0ykMPfHJA3OblZwiYgcvo79zpZOdu2YjZPH8jhxZuq6XNi kVlA8jABO+SkJ3zAlTcUN2hkqB/nHgDMmC85K8iCN2jf+EOdXEcNnWgwWzbBHWuuCT0xm2eE vIlFJptYhAnYISclz+W48Ub/BGBuF4a2esBuUbFjy5u4mzfpqX/jSLebfTucYRPEylESejY1 O1g5/ZjN0+MTObzsG/kz2cQoTMAOOWlIeOPCGwMmcr/qUpxAAFruWfRcfFrOf6ZQK9betBTV W7PnDSNsNOS0dlln7XSInIYIaeeEnn1nMJunh7wDXHjz6/ExKHsTrzABO+SkPJO0ySrRPqDc ZYpNo8JEZ9+QUGiMh5bLH+ZzNjff7mGxbOg2V6pH+kDOPueEnpjN04uJw4U38meyiWOYgB1y sESbTw2VrMNSHS/w5aULn1c+6JU30N4fcnodE3r2YzZPZuRw4Y38mWxiGiZgiRxIw4OFqJPF Dj+rSS9vvrx26fPVj/uADTnEH3JOdx502sg5tNvH5nkKD+HCm3WTZ8gcnBbrMAFL5BSuefTy p+/70VJ4TFIkkFbe3Bwc3DLeN2yCIMcloSdm82SwcrjwRuZMNgkIE7BETnHtE2lLPZAUUvBZ R0p5c6N1bkDY+EaOEiHd2upg5WA2T1eLjQtvZM5kk4wwAUvklNdPSM9zoHyUdIJ6SSNvhg5U coGNb+Q0tZ1ySOgJ2Tx7zjS46tw0NwjOmz9NKZfWmZakMAFL5NS2vpwgFYpL8SCB1PHmZn8b R9j4Rg4k9HSIkB7Y13qgry7NRHFee3DeyJzJJklhAnbhag1dJR60FDZNigTSxZsv3j91vew+ 7ryBDi+te7apw1u9nAPdxx28apjN0wE5wXkjbSab5IUJ2CFn/5t1SdGiuA5WCaSIN19++r6/ 6GdGPvlAzonuIw7IwWyedsgJzhs5M9lAmEDRmseiTe0sbHSIkH7ngz5WRYXtEiGB1PDm5uDn tX9kJIfvZj6Q45TQc9tWLMtmiZzgvJEzk01tZZyKDgQnE4arJQIiHhaRFt5oJdR8s4TxQB/I Obdrj52Vg9k8w+CNnJls1v7hIfjKH1yJx6sHjB3woK3j3zQVvPGUIY2RKw7NvCLHOaEnZvM0 IyegfSNnJpvK2vHxQgWv2eJGTvw5wrqC5PMm7G0bS/B4RQ4k9BzYts3Oyjl1FrN56rJ5BuSN hJls0hMmYKYUbuSwauv4t0s6b3jkEfBn8XhFTmfnibNbNlsjB7N56pMOBOSNbJlsUhUmgHkH 4k8N/ytIOG+Gukv90YLLUYCc19s9BEkf7X7DdiMHs3lSyAnIG9ky2aQtTAAfAvWvsGN+ZJJ5 c/OtvVywEaSTv295sQ6iAVr7GF8nu3tskYPZPFXkBOTNqp//TJ7kAukME7BEDm7kxJwm7tNP LG8i2baxJJNX5Ay0d9oh53QfbuQoGzlBeCNbJpvUhgkkaSPHEp8G7ZurKa2WVVM+yWu+dYuq umbS2Gobd1UeixaJ5U3w9M9BzBrDsZ6Q45zQE7N5BuSNVJls0hwmkKSNHFfe6LDRnKevCu3E m1hQhH2SyeTN0KEajrTg0pUn5CgR0o0NllYOZvMMyJuaabMlcaZhmEBiNnJceJOrD63TzBnO NEMd6exPlkLKx3l5yqfwQZZFuZLU8YZTAnmjJEnLlEST7eUJObs6Ttgl9IRsnilP5RnEnyZP JhsME0hMajUX3uRoYeZNv8mfptAp42dTfjS8kD7iTZtbtxLHGyF5a3yTzBNyIKGnXYR0yrN5 BuFN7YiHZLBvMEzA4XHR2BWf5s2bnL+NAgzZAFJBxO7Dkqll0ngjoSctyF7Ose6jdrEDac7m 6Zs38mSywTAB5/QEpVuekUlPuswlgD/N0r6x4k3G7EHeSHRVfPHhQEjlBnwbNJYHXqyfu2XX acYI6TOd+62Rk+Jsnr55I0kmGwwTYMmFE6PwaLd4AZ2LTPGRZawU1XYxOMl0v1JtFNPGZidI IiXsPJUE2TeQSmDjWL5gCK+3d5qWsCPHLqFnf1tzOsuy+ebN8hmFkTvTMEyABTbQBrxqV65d io0qdZlo1jzJhAZkfWIaWLJ/o+IFisHsofZvKMzEO0A6ObyR35NmoBc7ciBC+tz2FutwtaNt KYwd8M0bGTLZYJgAI2+g2abd85LCG1yHIoGE8CYunjTfyHFI6JnCbJ6+eRN5JpvVj/4qhUUH 2AFjbtl/oQdVdWIkkBDexMiT5hs57Z0nrcPV6ja/0b8jVVaOb95EnskGwwS8sgdqsg3dHEyM wk35QpLAm6Ej68PbaBHQM7tjraf7mLVXLWXZPP3xJvJMNhte+pNXbYvtQQI7D1WlXE0nZvmx 582Xly7EIibNmVvsyLFL6Nmfpmye/ngTbSYbCBNYtHYU8sOHBGL3OE5i8MB9IbHnzY2WlwSY IAKGYEdOf+deSysnPdk8/fEm2kw261f82YeqxUOIBMrrJ3DXfdiheAnEmzcyVBzgiKKBXetZ HspREnru2mWBnLrNKcnm6Y83EWaywTCB4ODsOdUoXj/iiHwlEGfexOqBG0YsMSLHLqFnSrJ5 +uNNhJlsMEwgOG8K1zyaoMdx+Krx2PQWY94MHdvKqMTj1YwRORAhbZnQMw3ZPH3wJsJMNhgm EBw2pIe69qLYaFacqJUE4sqbL69d+nzliHiBhH22jMjZZ5fQ83jCy7L54E1UmWwwTIAXbEg/ 5987hpo8vhKIK2+GukvZ1XccWzIip9cmoWeys3n64E1UmWwwTIAvb0o2PoWP4yBvhEogptkE vGKPETmnOw9axA4kOpunD95EkskGwwT4wob0FqM8nkLVYhwGi6V9k5gYaFcCMSLn3J52M3L6 O3ckNZunD95sGPV78Zk6MUwgDN5A4ACaOHGAi8Uc48ebhMVAuyLn7J4trkHSSoR0a6sFchKa zdMHb8RnssEwgTBggyZOTElDph033iQxBtoVOW927nZFTlPbqXONDWbkJDKbp1feiM9kg2EC 4cEGekYTJ6bUiRlv0mbcaChiQY51Qs+6zUf7WxKWzdMrbwpfXCTYmYZhAqHyBndxkDciJBDf PNCuRoxrAxbkHOg+buFV29l06My2JCHHK28EZ7LBMIGwYSObiTP213PML0oh0sXW6JLQSvG0 3I9Shs1UwBOaZOqw0VU/tcPUutPmfnTaWDk2Ly9Tjpr+yVWtFqG7Y+dPS61x48nKOdF9xAI5 ycrm6ZU3gjPZYJiAAN5IZeIw8EZT7hn2ZH9TYWJAU7b+p/Kp1iLHG+qg5jzS1KIfGiE0qwzF q4WRJn77N2k2bjwhxzKhZ5KyeXrlzdoHfyXMn4ZhAmJgI5WJ44U3BA+kprQVJ3QWTq6BJW9U WiBveHMTjRtPyDm3a4/RyqnbfKy/NRleNU+8EZnJBsIElqwbLUzh4kCSPIvjkTcaZ2g/mM4A ylo4FEfM/jTKHWbZT04Fo33jGUdo3NAbPK57OUpCz6ZmA3ISk83TE29mTF8uzrgpfR4ZIFIC 81Y+JEMSTx+8sbVviNlj+rPJD0b2hAh00L7xDBSnA9C4MUcTHN271zlI2jKhZzKyeXrijbBM NhgmIJI02lgt+8u4Khs/nXnkjYYHO04Q4KjYyczIct9FPR554+es2R6Dxo1l9NrBvYedkdPZ eeLsls1Gx9rJ2Gfz9MQbYZlsqtdNiEThpnxQqP4ZuYnjiTeK88s+XoAoQQUgw4cTK4f8aLyB N+rH2lYP8oYfb9C4cQiVdkXO0e43zOFqcc/m6Yk3YjLZbJjxVMr1foTLl8HEcVR47PHQVAQA HTits2+o3ZrcPo8hrloLSTDaRhif5oImNG6cH81xRU5f1yEjcmKezdMTbwRkssEwgQhhA0PL YOLw+4Kd5J5kzy+Axo3rc6DQwBU5A+2dxtiBOGfzZOeNmEw2GzBMIJO5OcLXzkNVSdbTSVmb 7Ly50TiNReFiG2fkWCb0PHu8Labh0ey8EZDJBsMEIsSMNjRmVIsFkqTmzZeXLiBI2CXgjBwl QtqU0DOm2TzZeSMgkw2GCcjAG5hD3/l9sdC5aZ6k1LxJfBFPdpYwtnRGzq6OE/11W3WOtXhm 82TnTdiZbDBMQBLYwDSqGyenWZXHYu0S8+bm4PWy+xj1LDbTJNCx74RDkLQ5oWf/zqbYlWVj 502omWwwTEAe2JCZfHj5QizUbmonKS9vho5tRYr4kMDVFb92Rs6x7qPG2IG4ZfNk5E3YmWww TEA23kgfGJ1a0GQXLi9vMAzaB2zIIa7IOdO534CceGXzZOTNrOlLw8tkg2ECssFGqgyeaQeL zfol5c0X7x7zrW3xQBbkGBN6xiqbJyNvQs1kg2ECEvIGptR7phV1vbQSkJQ3N1peQmwElICz lQMR0ue2t9BWTv+Ohp4zDbGIkGbkzfpJfwnJvsEwATlhA7Mqr58grbbFicnImy+vXQqoavFw FscaJPQc2LaNRk5csnky8iakTDYYJiAtbMjELn50DjW7nBKQkTdDByoRGLwk4GzltHeeNCb0 jEM2T0behJTJBsMEJOcNRg3ICRuYlYy8+XzlCF7aFvtx3cvp6T5miB043r9bcq8aC2/GT10R hjMNwgTmVf9GcoWb8ulBOrWhm4PS6tw0T0w63tx8uwchwV0CV6pHtnadtnsu52R3jw450mfz ZOFNSJlsVq3FimpR5kljRGnPqcY0q3Vp1y4db27sWcBd22KHIAFn5Ay0d+tiB+TO5snCmzAy 2ayf/AdGfYfNopVA6ZZnpNW5aZ6YZLy5Ofh55YOIh5Ak4IAcJaHnrl00cmTO5snCm03PPMfd n7Zk3eho1SiOzi4BjBqQEGxy8eZmf1tIqha7JRJwQI45oeeps5ImkGbhDfdMNhgmwK7rZWjZ 0FUiTOH+pGi1+UWNrqu3lq3taTU5rUqa+iba6mj85ScXb/CxGwFcdEAOREjrEnrKms3TlTfc M9lgmIAMCPE0B6hQwF9f2vTIwBsHyjhME3kT2jn88vMrmKBTAG+crZx93cfpCGk5s3m68oZ7 JhsME/Ck6yVpfP69Y6GpK13H3nkDBky2FvStW7n3Gl4yb5qLh6tVorO0ou0kONy6EzFL9jeK RPbNzb4dYrQtjuKMHENCz/4j0oVHu/KGbyYbDBOQhB9epyGs6CcDb1RyDCOcYeFN/61bevuG PkjR98gbf9TLHDW47QUkgUgJgGOtpdM6SPp050E6dkC2bJ6uvOGbyQbDBLwqeknaF9c+EUAh eTiUgTcGf5ov3iiAgR8Lw0jPHg8zF9xUFvsGc9iIJI021qV1zzZ1nLF8LufcnvYcciTL5unK G46ZbDBMQBJ4+JuGmCg1UbwhdNCog/aNX1wOHVkficLFQe2QY0joCdk8D53ZJkneAVfe8Mpk g2EC/rS8PEe1HV7tVyd5OM4Xb7J2SmZPJmuy6PdvTP603IyUg/KatXA2xe9G2T0eZi64qSz2 zeCW8aj6o5KAHXKa2k6da2zQrBx5snk684ZjJhsME5CHHP5mIseDn1ZhZsRKGTZseHGxFjtg 4g0BidKIwMewC5Q1dfSdCEaIp+Gk4I0SmZZ5OgRfUUnADjnGhJ5yZPN05g2vTDYYJuBPxct2 1OVP3/ekEyNsnLTwZ5MopeANRqZFhRl6XDvkHOg+TscOvDmwM3KvmjNv1kx9iUtmAQwTkI0c /ubT1bshQoQwD02sF3+P6TAPEnVDKXiDOdNk4A3MwQ45J7qPaMjpb6o/fLY5WuQ484ZLJhsM E/Cn3CU8qrpxctRqFsfPSkAK3mDONEl444Cc/s69OeREnc3TmTfBM9lgmICE2AgypSvXLqHK l0EC0fPmi/dP2WrbZ74OFuaTz2j7Oj8p+Jfchtmwn/wwc+APnySfZX+9+/pL//rjf/nXE7gb 5FcCYOXU7TEGSSvharvg0w3kFW02TwfePPp8eXBnGoYJBFHuEh7be6ZVBm2Lc4ieN0OHaix5 U/8TBSHwr4E31K8Kh0489JUfP/ST68sARV+vz+KHvMGXfwn8fcuLZuQoCT2bmjXknOjfE5VX zYE3wTPZ1I7/vYQaE6cURAKrW2agrpdBAtHzxjkS2itv9O39K1zElSVydAk9o8vm6cCb4Jls MEwgiGaX81io+Hl98KoMCjflc4iYN66R0GbeaA411dDJ+tPAylFtHcQMHwlYIqez84SW0DOq bJ4OvNkw8YUg/rQNSybIqTFxVgElcHygPeW6XoblR8wb10hoW3tF2drR+81g2wa2cODfDJEy TjY+ajfN/Vgi52j3G7nYgaMR1Mhx4s2o3/vmDYQJFNSMCKjX8HA5JVDXXiSDwk35HCLmjWsk tL1/DMyarxS8pBEFflXwk22PIQP8WGuJnL6uQxpyxGfztOPN/3uuIkgmm9Wr/yynrsRZBZeA HIkGUo6bWxHzxjUSms2+gWCBLHvU9j98EkPUQkbOQHtnFjnCs3na8SZIJhsMEwiu0yXvAbdw IsddlLz54sMBB1eVEp+W+yE4UUOflc9zzjTdto3qTzOEsaXZJ8Zl7WYrByKk32ptJcgRnM3T jjdBMtlgmIDktAg+vf4LPZEr3JRPIEreuG7ecFGU2AkvCbzX+NqWXbp6OXRCz4H94vLc2PHG dyYbDBMIrs3l70FMruiUE8V5+VHyxnXzhpeixH54SeCdpiUG5OzqONFftzXrWBOVzdOON/4y 2WCYgPyo4DJDfAonchZGyZvBjWN56UHsR5gEzMihE3qKyeZpxxt/mWwwTICLNpe/k3krH4pc 4aZ8ApHxxvXJG2EKFAfyKgEzco51H81u5DTV95xpCDvvgCVv/GWywTAB+TnBcYZiyn1yhQpd xJNrx1F0Fhlvbr6116uaw/bySMCMnDOd+7PICT+bpyVv/GWywTABjtpc/q5CSqR2ePrt5pdB n9PV0uyqDuQKduYO1vFGLdLmo3CBU20dq3FDwVFkvLFLmyaPSsWZOEvAjBwtoWfY2TwteeMj kw2GCchPCL4zDOmpT1feKAo9BxlQ/dkC0gxKPccbHRWa8zyWypGilltkvBnc9gIq9LhLwIAc JaHn9hZi5YSazdOSN14z2WCYAF9VHoveQnrq04U3imljCRiFAXl5uTprOSZohkxeXrbatE0n ObMpN4KCqGK1+HTmY8q4UjDFMG44ld8i443rk55x18Upmb8BOZDQc2DbNgU527Ye7W8JaSPH mjceM9lgmEAsCMF9kmE89enMG1vcEAxQJFJ5A8DIWi+5FrnPKKOIMloov1sGVqTbnE1E2zfu 4zIYXn6aRMMb5yc9U6KpE7PMgV3rN7b2aS8toWd42TzNvIFMNp7SpmGYAHc9HpcOw3jqk5k3 ObMlQwOjjyv7uw4tKkeseEPvCVHFqOktH+29gTc6b5zVuH5w4npMNLwZOrY1MdoWFwISMCCn p/tYNnYgnGyeZt54zWSDYQJxwQP3eYbx1KeLP824HW/JAIo/lryxspJsLCfkjR58Qx2LUU0n TAIG5Jzs7iHI6TvTzt2rZubNwhcXsts3GCbAXYnHqMMwnvp0ixfI2CE5i8KNN0pzkz/N4Hwj MQfWwPHLG2pcV0vFX4No7BsMFkgYbMhyDMgZaO9WkBNCNk8zb9gz2dQ8eC8WHYgRHrhPNaqn PnOhzDnPl40/jdrfH17cTAWz0f6z7LaPIRIggwFL3qgxA2q8AIQNaD/aPKx680cW66Oi4c3n K0ckUuHiomjkKAk9d+0KI5unmTfsmWzW1EzirsKww3hJ4PKn7/NUotgXswQi4A1mFkg2lmjk KBHSjQ0Kcg7t5uhVM/Nm9X33svjTMEwgXmAIabbn3zvGrCGxIU8JRMCbL94/lWyFi6ujkZNL 6NnHbSPHwBv2TDbLaseEpMKw2xhJoOdUI08lin0xSyAC3mAZgjQAqa+tQYuQ3td9/OyWzWDl 8MrmaeANYyabjcXjY6QTcarhSWDnoSpmDYkNeUogAt4MHahMg8LFNb7ZuVtDDkno2c8pm6eB NxXT57s60zBMIDz1Hbuea1tf5qlEsS9mCUTAmxstL6EuTokEaOSc7jwIyBnY13qgry7gXo6B NyyZbDBMIHZUCG/CIWW1Yda66W0YAW8+r/1jSrQtLhMkQCPn3J52QE7wbJ5G3rhlssEwgfB0 dxx7jiokOr2cUVceAW9QC6dNAhpyIEKaJPQMmM2T5g1LJhsME4gjFUKd85Vrl1D7i5eAaN58 eelC2rQtrpe2cpraTikR0tu2Hj7b7NurRvPGNZMNhgmEqrhj2vk7H/SJ17Y4omjeYJm11OJH s3LaO09CuFqQbJ40b5wz2WCYQEx5EPa0jw+0o/YXLwHRvBk60ZBahYsL15BDEnr2+83mSfPG OZMNhgmErbhj2n8YWTvFq+/YjSicN4dqUO2mWQI93QdJkPSJ7iOAnFNn/TwESvPGIZMNhgnE FAYCph1Soc/YAUDwhEXz5saeBWnWtrh2kMDBvYcJcvo790I2zzf6d3jdyKF545DJBsMEBCju mA5RXj9BsKrF4UACwnnTOA11LkqAIEcJV9u1p39Hw6Ez2zwhR+ONQyYbDBOIKQnETLtwzaMI APESEM2bwY1jUduiBDQrR0no2dTsNZunxhu7TDYYJiBGa8d6lDAKS4vX4PEaUTRvsBIBwkaT ALFydrSf7K/betpLNk+NN3aZbDBMINYkEDP5ix+dk09Z06VrvM7O87HG8jteB/TeXjRvUNui BGgJEOSQhJ7s2Tw13lhmssEwATH6Ou6j9J3f511hWh/xq1m7zS+6KbNmzzHDWISa6s7mT8gb /dn58tP3UduiBAwSIMg52v0GezZPjTfrf/eoOVNn2fqn464Kcf4CJNB7plVm3nifG/JGL7Mv 3j2G2hYlYJYAQQ4k9IRsniyBA4Q3lplsNhY+J0BV4RAJkADHKjjM9o2ChOLi4VBRGn6yFaFB SWq1pvPyoEFzRm0Skwj+ohSAVj8hf9RZSxbHWtaTputZZ7tktrq8s8/mCKH+tJv9bahtUQJm CVxd8euOfScAOQPtnSzZPAlvzJlsVt77s4KaEQlQhbgEARLg+MinF96onMk5xXJMAQBoGMrC QPdHMycsj7Xkjd4fl+kp4bwZOrYVtS1KwFICBDkQIf1Wa6trNk/CmyUzXjM40zBMQICaTswQ EfFGs2pUKtAmjGLp6OybjO1jhEOOE9bHWvMmAzP1JxW8weQCy+5G3thJgCAHEnoO7GhxzuZJ eGPIZANhArMr70+MNsSFhC2Bhq4SXn4iL/aNV95kgUPbIn54o9BGHVo9Pun2DVb2RN44SoAg Z1fHiYEup7JshDebxoyl7RsMEwhbQSesf44pbQLxRiFBzlFm9Kdlt2vy8pTdnCwfc5ywPjbn qss56ChLSPlzGuwbTGaDxo2rBAhyDnQfd8jmSXhDZ7LBMIGEwUDAcjhWlQ7Em8w+CvFzDS9u Lh5u8KcR4GQJoQUO6IIITMdqAQjDi4s1B10uYACiEpA3rpoIG6REAgQ5kNDTLpsnwIbOZINh AgK0c/KGqG6czMufhv0wSkBofBraNykBRvBlEuSc7j54tL/FHCENvJk7o0RzpmGYQPJgIGBF yBtGSHBsJpY3mKwT92+YJQDIadt7cmB/tzmbJ/BGy2SDYQICVHMihyiufYKjJsWuWCQglDeD 214I/s0Xe0iPBK5Uj+zYd/LsG3sNJg7wRstkg2ECiYSBgEUhb1gIwbcN8gYDlKWWACBn377j fWe6aOQAb0gmGwwTEKCXkzoERM/zVabYm6sExPIGixEwe5PSY8S4rhSQ03ug982BXRpySCYb DBNIKgmErctVP2IDvhIQypvPVz/uqlywAUrALAFAzvFDh3vONBDkkEw2GCYgTC8ndaChm4N8 9Sn25iwB5I3U3iRkjyYBQM7pY/sIbyCTDYYJJJUBItd1+dP3kRAiJYC8Qd7ERgKAnLOn2oE3 kMkGwwRE6uWkjoW8EQkbGAt5Extti7YOSOBq1SMn+1vXrXg5qRoQ1yVSAsgb5A0CACVgK4FP Nkx4t6mwYPUjIrUSjpVUCSBvkDeobVECWQlcXfvkh1unnalfvHN97apFW8oLtzVVrt5aW5FU 9YfrEiwB5A3yBrVtWiVQ+eClzROPNy/c27R625ZthSu75uVve2l0DbxWzKvbsbKsraBgYXVL 2QZ0pt0jWC8ndTiMT0PepFXbpu/RnE82PPvX11852Lx8/Y7GBU37X63dV1DcSgCjvYA0jVvL uvKfaZm3+OnFnQdXTHq5/IGkqj9cl2AJCNa2OBzGCyDeBEngWs1jH2154WjTkvUtGwuad0/a 3jtna09hye6Xn1lnYIxm02xpWNxROqXz4d/ULKj57Zy2tqIxa2vLBKskHC7BEkAACJaAUN5g /rQUxZiV3QfOsdONC3a1VC9vef0Xm/dNaOl9Zdth2ktmiRniPVvfULR720sdj/6ma+Qjc4vq ob7I2sqqgyvGLarIT7D6w6WJlECM8tmIL8QZEoeQN4K+3SeeNFdqx7xbnw/mC9Dl6W1tAJjR TUdebO619JLZkabqtbq1TflN7dM7n368/YFf7hs7ZsKrzQCbWRVth6ffXlazGp1pIjVyssfi mK8TrlXzi1bZjsBwp4l7i5D4wLtb5A3yxo8EPqseAeYL0KVue+3cphagC7x+13DI1UvmTJrN nc93LZhIbt29kyaPmtMKsBld3Ll/9i/BuCmuqEm2BsTViZQA8oY3Tdz7Q9740baJN1bMCwS6 nGuY39lSAebLw3XdBDCevGTOpFm158m2jTO1L4m7ZxdqNXp3lEwB46ZqdeWi8r+I1Ec4VrIl EAVvoKZzXrFaPTpTOFqrJZ2rGJ37KFtaWmmkFZB2V+oSt0DeIG8sJAAPvrxfNw3Ml+qWrS80 7NLo4s9L5kya8p2P7mx5qfMPj2iw2VRYocFmRfVmgE3vwt/NLt2abPWHqxMsAY71PZn9acCb YcMIRZS35J2eJtRvCp0sWkjME7epIW+QN3dfVx98aW5ZvbCpkaZLQC+ZK2nqO6ZCrLN2u0Io 2vKi9RpsppZ1AGzgVVFTVlJcKlgf4XDJlkBEvFFtFgU4FjSh7B1A0zBi1qB94wYyq7/f2LMg hZ4oCZcMzjHy4As4x0bVdRgAw8VLZkealYu3QkQA2DSr28ZArDP9xXDv6CfzC1/XYDNyfnv3 3IeJcfNCZeOCiqeTrf5wdYIlIC9vNCSpWhR544c3QwcqJVS+iZ8SOMe0B19mNrSa6cLXS2ZH mpqlW1ZvnwSkqdr9exLrTMNm37PPjZ2/XYMNvKkvKyLGTUn1stn5KwUrIxwu8RLYtHueHy1m dYwXf5qLfZPZ0DECB3nj50wNHVmfeOUe/QIzzjH6wRdLwASJJbMjiitpADZarDN9i3ZNm/nI Kztp2Cxe2Uhg0zv33qdXNi5ZtDjx6g8XKFgCde1FfrQYf96oMQNqSIA5hAB54+dM3ezbEb06 TlzaGMgKY3jwxRIwoXrJWEhDxzrTsIFENTRp4P24JV2H8u8ivNm0qnD6q+sLKkYLVkY4XOIl wJE3frRhKo8RGi9w8+0e5E1ACUBWGPODL3aA8fHEpVfbhYU0hlhnOjoAEtUYYEPy1mjGzcPL N86bsjzxug8XKF4CLfvLUqnzo1y0UN588f6pgNo2dYdnssJYPvgSuZeMhTTmWGcNNpCoZkHR FgNs4NeNFWUENsS4+cvybUuXFIlXRjhi4iXQ1bshStWbyrGF8ubLT99PHTA8uu8gK4zdgy/y eMksSfPK2LVryzeRiADyMsQ666ID1EQ1Bt4UVLVqsIGdm/tK1r3w9JK55SMSr/twgeIlcHyg PZU6P8pFC+XNrZuDyBtaAiQrDFR8sXzwRUIvmQNpVm0fp5HGHOusi3tWE9UYYEPy1mi82bFy FkQKvDoNE0JjtZtQJPDOB31Rqt5Uji2WN7duXS+7L83IcX3wRVovGSNpLGOdadi0vTTPEIpG qAPbNiRvDXkdzb9j5LJV02atWbJ8rvhvvjhiGiRw5dqlVOr8KBctmjefr348PbxhefBFci+Z 3SYN8Z7RNk021nnCk5bPIpAP6UQ1BuOmpmqNBht4s7t65mOV9eMefhUTQqdB9YtfY4yKEUTJ B95ji+bN4JbxieUN24MvcfGSeSLNhs7xWl5nS94YEtUYYKPlrdEZN6X1C+egMy0UV5J4/S7b iByTdfLWyUnuTzRvbjROSwxv2B98iZeXzI4088fVmm0au1hnmjrdox6nE9UYYDNqQQfJW6O9 wLi5a9G68U+8VrJipmx6CueTDAlwTGaTZD7wXpto3gx1l8aUN54efImpl8yBNOtW1lbvGKNF BJA3O1rz6bzOlpaNOVGNgTctS2fSsIH3o0tX/rm6afKoYnSmJUO5S7gKfNiTN0qY+hPOm2Nb 48Ebjw++xN1L5pU0DrHOzolqDLApXVlvgA3UVftJ0eopU6oWzcPHPNGZFpYE2g6vZlKQ2Iir BETzRtoUAz4efEmGl8wraZRY54ppDkEB2p9aX3nN/Dgn/cmk0k4tb41GnRfKK0dVbRv76zkL yydJ+L0Yp5QMCfSeaeWqSLEzJgmI5s2Xly7IYN/4e/AlYV4yr6RxjXWmE9XULqh2hg2UG+gq eMLSuJmxaMu0pxYlQ6/hKuSUwPn3jjEpSGzEVQKieQOTj+QRHH8PviTVS+aVNCyxzq6Jagz4 ofPW0MbNL5dtem5EwZLiJXLqKZxVMiTw4eULXBUpdsYkgQh483ntH8M2cYI8+GLJmN/WH5q0 vXfO1p7Ckt2vPL+BV1JLefopfH5D7eo15ogAII1rrLOhZtrUwkZnywb+Suet0WBzZOlo2LmB 0mrgTMPqaslQ69KuYujmIJOCxEZcJRABb260vMSZN8EefHHwks1qOFK4smte/jZ5wMB9JkCa 9etqKltHGWLP4FeWWGeWRDUG/Dy92GLbhtRVA95MenbpS+OWSauncGIJkEDhmke5alHsjFUC EfAmeEh0wAdfnL1k8zccLChu5a7WJezQgTSMsc4siWrM5QZ2Lxxv2LYhRaMBNmOqG8C4wepq CdDpMi+hvH4Cq4Jka2f+rgafUIeSCmpqPbXsH5rz4DO1lKfyi6mMNNvgcWoVBW9ONHiyb7g8 +JJOL5kd5JxJwxjrTMOmvmC5qw+NNDDkrdHAQ4wbKK0GvJlf+bjM2grnFncJcKwkTZQ9A2+G 5+UN1wEHCDN8uLl0dJzo4X2uEfDmi3ePOfGG04MvKfeS+SMNe6wzHYq2vGg9I2xmVbSZLRvN uIFIAYANVleLuzaXf/47D1V5V5VOR7DwprgZjBzNhMlUiKY+UStGU7WktcbEEFJ+DBYS30WI 6C0C3nx57RLNG14PvqCXzNll52zTsMc6syeqMeetocsN0OApW1UCxs3UcsWZhtXV5NfXcZ8h 98o3TLzpV1iSBQ7Bi+mDW4AWo1dNsYOK+0XAQMAYEfAGVnWsZamnii92LEEvGcu20GtTNq3f VGF5S5APm9qndzrmdbZLVDPh1WZGywaamfPWaEWj7164GhKmPf/UYkgIjdXV4q7N5Z8/92Bo Nt7c0nCSxYqZN0qL3KaOAoBE4eZWNLz5857jnhDi2nhCS28aYslY6EK3cSWNp1hnQ6KaUXNa 2WGzonqzpSeNFI0G4wZKq4FxUzgTE0KHlcFFfgyImWEYlQhYeZOlh2rFWPCG2BgUdZA3RrMr IxzKClTdjXpfJW0Rrjh23hUhzg1GNx15sbk3PbFk3EnjNdaZho1rohrncgM0eKBoNBg3wBso raZEpmF1tRXIm3AlwD04jTFegPjEiHLMOshseQMN1b8p/6M/TWUOCeOjvY7UxhcBjoVLcudf P/DKm8Q/cemVKHbtXW2abKzz04+z5EAzt3FNVGOAjWXeGg05xLgZUV4HsMHqamK+4Kd8lIau Eu4bFcz2DeGIyg/LDR01NkD7Ck+FEMQePHz8aQ68saDNrVvnLl9l4Q16yTxBiIU0Wztf6Mp/ xh9pukY+sqBoC7sPjbSsLyuy86Qdnf1fWeOmtF5J0InV1dC4CV8CPacaufMGO2SUAH/eqCaj AnHV1jFOZvDmF7+uO2BGDnrJPAFGa7wkf6tzRAB8//IR6+wjUY2BRotXNtrBhhSNBuOGlFYD 3mB1tZRbHmKW/84HfYzKEZtxl0AYvFEnCbQBj5pqDRpMwed2HQPeoJfMH2B0pNm6xCH2DP4E sc67GvM7Hv2NP7MGjto7caKn6ABCHbu8NXTRaOANlFYD2EB1NTHqBkdJuQQwcxp3irB3GB5v so60XOSfHjiNO44nOy9ZQJC4Hq7YNG6k8R3r7CNRjTlvTVvRGFfjhpRWA94sLsDqauHuk6cc M2T5pVueYVeO2JK7BELiTc6Rpu7fNOfpedO7d8BVpWIDSwkwkkaJdV48ybdNQw5kT1TDUm5A w8/R/DtGLlsFsHmsUtm5wepqCAMxEmjZX8Zdh2KH7BIIyptcqgV9mF8OLqo/zfDY7OWPriBO vEqAkTRBYp3pRDVVRWu9RgeQ9nZ5azTekJ0beEFpNYANVlcTo21xFO6ZBdhVLbYECQTlTRAh Lpy61avCTW17RtIEjHXWYNM96vG5RfX+YDO6uNMubw1dVw1gQ0qrKY/dYHW18OOyEDYggcuf vh9EZeGxASUQJW/qq/emlh/sC18xr6729ULniADy1yCxzrTbbd+zz3lKVENj6bdz2naUTHHY toE/HVwxjhg3pLQaVldDEoiRQHHtEwHVJR4eUAJR8ga3cJypw06agLHOuhScU6f5CEXTkOOQ t8Zg3ABvJk8sA9i88nypGHWDo6RcAnXtRQHVJR4eUAJR8ga3cOx4w06a4LHOQRLVsOet0WCj GTektBpWV0s5A0Quf/+bdQHVJR4eUAJR8gamjls4BuSwk4ZLrDMNG6+JaszlBrrnPuzsSYO/ vlBeSZxppLQaVlcTqXBTPtbFj84FVJd4eEAJRMwb3MLReOOJNFxinTXYQKKakqJN/qIDtKMa Sue4woYUjaYjBbC6WsoZIGz5hWvoAs8B1SYe7lMCEfMGt3CANxWFrBEBYNNwiXUOnqjGU94a Q9ForbSa4kxbViBM4+BAaZYAbt74RATXwyLmTcq3cKpeq1vblM8Se0ba7GjN7/Sb19nywU9/ iWoMsJlU2nko/y5244aUViMJobG6WpoZIHLt+OQNV3D47Cxi3qR2C8craXjFOtPU6Zg5+5FX dgZ0o0EAdFfBE66wgQYl1cuIM42UVsPqaiK1LY51ffCqTx2Jh/GTQPS8SdsWjlfScIx1pmHT MH9ZQNKQwzdWlLHARtu5UUqrzanNRqZhdTV8zFOIBKobJ/PTmdiTfwlEz5u+oxfYH36MdUuv pOEb68wlUY0BUQVVrSyw0YpGa6XVgDcTH1vwcvkD+L0bJSBAAm2HV/vXkRyOzKT9yuX40hUF 01KC6RNMGqsmc5iFBF1Ez5uhGzdfGbs21iBxnbxX0sBWzevt0zonPBkw26b5cAhF852oxgAb 53IDlkWjFeMmU1oNq6sJULI4hCaBsCOhLTUApd4BHsOHD9cqdlK8Uf5CKk1DIeRcjkkl4XFe Xu4ICVDBZQrR8waWsXlFp6vKHnf7t+Erwo9+XpNpOelHpOrqdyZlD3x45Nf/ceQ45U9yvWqW blnTMo09IgBa8o115pWoxlxuwDVvjaFoNF1aDXizqPwvqBBRAgIkICASmoU3xcVg5BCiWPOG Uugkvz5VbpqLspegEyl4c/zgeRdOZHDy8+9keQPs+frthS+NLvz5P/70d1n8kDcSvYA0q7dP 8kQaJdZ5az53m4Z02B0sUY2BNzVVaxg9ab1z7yVFo+E1MVNaDaurCVCyOIQmAQGR0Ey86Vc4 kzFmLPxpOmeaVs5F11ACXASeghS8uX5t0NGlBlz59s8frvmdDW+0zyXhjQ/ShBHrTHNr9+xC LtEBpJMXy9sZYUPv3Gil1bC6GsJApAT6L/QE1pMuHTDyJlPsGEwcM0ZI1ZYsdHLVwzRChb0A Uf1LwRtY7JqFu+xooVozOd5o/jSwcrS/ygAbf6RRYp3njgvJrIFuNxVWcITNqAUdLHlrtKLR D5TUEONGK62G1dVEatuUjzVv5UMCCkiz8iZj2gxXPGuGcmBZL5tq/ZDdguyPPo5AFBnCGUcW 3tgmGgBP2rCsr8zCjoG/whaO0kb5yTjZonGp+SNNSLHOfBPVGFjVsnQmu3Gj1VXTSqsBbGaO LUm5EsTlC5OAAGcaaGZ23mRMHPjJ8gZ+U8mj7tZQEQQ0hcLR/6J7lYU34FKzRsXPf6pjvQ4q EDWgoCjLoShCBsAN6I80JNa58w+PhGfW7B39ZH7h6xwtG+iKpdyAuWg0wObnJetJaTWsriZM 1eJAIAEBzjRvvMmYOBpvsr8RHZchjwE3Fh+IZgTP8WThDaxpZWGrs3Wit2+ymzpwiPr5pB8J DFED0qwt37Rq+zhPEQGkcUixzrqsaBMnjp2/nS9sGPPWmItG06XVsLoaYkCYBMQ403jq46T3 JRFvetrPsPNGt22j+tPUaOlwXWpBSBNerDP3RDUGVo2c386Yt0bbuRm5bBXZudFKq2F1NWGq FgcCCWzaPS/pCjxm65OIN/Ln7gxCmlBjnWnYtMxbzNesIb3VlxWxb9tAy/3lz2uw+WP168ST Bq+lJQtRFaIExEgAc3TKhiOJeOMcpRZVIAAZNwhpwo51DiNRje+8Neai0XRpNayuJkbP4igg gdmV9wuITJNNoUs+H7l44/7gp/Dws4CkCTvWmQ5F45WoxnfeGnPRaLq0GsDm1WllqApRAmIk ICYyTXL9Ltv05OIN5FKbP259tKaMNvr8cbXrqjb4iwgAmybsWGddopqxYya82hyGGw3KDbQV jfHkSaOLRtOl1bC6mhg9i6MQCZx/75hs2hbnIxdv4Hw0rj4QOW8U0qysrd4xxkfsGRwiINZZ F4o2afKoOa1hwAb6XFtZ5RU2B1eM03Zu4A0prYbV1RADIiVQsvEpVO4SSkA63ly88HGEvAlI GjGxzuElqjFAa1ZFm1fYQPs5VWUab7TSasCb12ahM0353o0vARLo6t0gobbFKUnHGzgly2c1 ikdOcNKIiXWmYcM3UY0BNqOLO/fP/qVX3tB11ejSaoozrWy2AEWDQ6AEQAJXrl1C5S6hBGTk zf6dp0TyJjhphMU609EBy4vWh+RDI92ylxugmaQVjaZLq2F1NWSASAmsbpkhoarFKYEEZOTN lU8+E1OBLThpwIG2fVd+59OPh5eWxtxzGIlqDOjylLdG443RuFFLq2F1NZHaFsfCx26kZZuM vAFhrV/aFqqJU/j8hvXraipbR/mLCCBHCYt1NtRM456oxgCbqWUdXt1opD1t3Ny1aJ0WKYDV 1ZABwiSAOWykhY2k9g1Mq+/ohZB4w4U0SqzzqukibRoyVsfM2Y+8sjNUNxrkrWEvN0Bj6Y2C X9FhaVppNayuJkzV4kAggZb9ZTIr3JTPTVL7Bs7Kgj9v4oscLqQRHOssIFGNgV5e89aYi0YT 6kyZUqXlsFmyoBRVIUpAk8CzD38VsiH/cFwmVG8cqSWi/Xx9pBLC96Mfkg/+40fZo175ztf/ 5TvPMkT3XfzoXMp1uszLl5c3bdve4MUbLqTJxjpPHSPerOl8+Dc1C2pCNWtI54tXNvrzpNFF ow2l1bC6GpJGJ4EMOe7+D5U3NEKAPRnAAJC+/vB/5K/4j7v/RcMPeePyqm19WWZti3OTlzdc ogZ4kUZ8rDMdiragaIsA2Ixb0nUo/y5/vNm0qpB2pk0r2aoZN1hdzVVLpqkBIOSrd79yz0gL 3sCfshAy8MaqsTV4xFS7QWz4loC8vIElbV/f49vEeW3KpvXrqwNGBIBNQ2KdOx79jXizBkbc F1qiGgPA/OWtIXAyGDd0aTWsrpYmlrjbHypIrHgDxk3OY5b1p4GVox3iKsnSLc/41oPxOhBK gca0yLTUvPnw4ic+eKOQZlNFkMAz7Vjxsc7CEtUYeLOxosyfZQNH1a+aTxs3L1Q2asYNvCmo GO2qKbBBKiQAnrRhWbeYyWTJGTdG5xt42JQDMwXjFSebLdUiDIP+xeZ95peBYdlC0mRfKhgu kDdhfT/wFBjNkTSRxDobEtWEHYqmIaegqtU3bI7m30HXVTNECrzyPEYKuH/rTwVsLEIDKH4o UQPmHRqwcpQPs3ByDBkoXPNohNUHXHmj1JCmGGP41av2RN54lRhre8Z0ahxJE1Wss7BENVzy 1lgWjQbY0KXVlOpqS4rSokzdtrJRDrQEDPYN/GqyXbI7PXCU2vhHP7QPUdv/Zh2rTgmhnQtv FNMmr1k3LhCH8EdhR17e8IzNUwxUUn8MdNKZRRpvcjaTofsQ1silS6n9aWSFzunUOJImwlhn umZa2IlqaN7Ato2/vDWWRaMNpdWwuhoyxk4COt5QfjY6ZjpHINWflg2hNqEdSqtdH7zKRSH6 68SFNxpccr1rCMogw0yL3CHWBys4oswcaBQL4sSAN3bPfnIkTYSxzroNm9FP5he+LiAUTRui pmqNb08aHLi7eia9c/PLZZueG1Ggbd5gdTXkjRgJRP6MZzDe5EwZiz0eC9xkQaNrHHRLyB9n PR8VA97AmpbM2EYHDizJ37p+83IuEQHQSYSxzoIT1fDKW6MhyrhzU6GLFFiyrECMusFR0iwB MG4izwYd0J+WcaxlXGualaLZLs68iYVRQ1EpHrzRMkYrpNm6hBdpoo11pmHTNW2msOgAQp1R Czr85a2xLBpNrBw6Ydq4h199ufyBNOtBXLsYCURu3IA6dYsXMDjN6F/1TjHV1MkFFChtjdFs 2WMstoU8GxyCD4gHb6DOdPWCBo6kiSSvs90TPK2vvCbSh0bGalk6M4gnzVA0GmBDl1bD6mpi VC2OIoNxw6ay7cKhdbFmCmbITx7EEFBmT/bT7EcW8QIBI6zZ1hC8VTx4A+s8/nYzL7Mm8lhn OjpATKIaA89KV9YHhI2haLShtBpWV0MSiJGADMZNcC2cnh5iw5ubX9xY0zE2IHJkiHUWn6jG AJtJpZ2+89ZolHqhvJKOFPjN8i30M54TH1uAzjQxCjfNo8THuEkPUFxWGhvewDrOvNvumzcy xDrrogPGjpla2CjejQblBroKngho3PSUjqVhoxg3VGk1pdrNvOVp1oO4djESQOMmdhyLE29A uFsPTPWBnNfbp3VGkdfZbsNm76TJo+a0iocNjBgkb41GKbquGsDGUFoNq6uJ0bYpHwWNm9jB BiYcAm8ye15UnJ66B6Z9FCAbw/kPejzxprbjma7FkyJJtWk3aNtL8wSHonHJW2NXNBp4Q5dW w+pqKceAsOWjcYO8uaWwJa+ZfthVhQv8T4AT6EnYlpaWnz/47yzIkSfWOapENQb76enFHLZt DEWjiVftLzNW0Zs3WF1NmM5N7UBo3MQRNuHYN3qkGHjjmza9vb133nnnPffcs//wblfeNO95 sfPpx6Uya6BmmshENeZyA7sXjg+4baOUHlj4O8POzWOV9TRs4H1x+YTU6kFcuBgJoHGDvMlJ QA+VrD8NQsf9OdIuXrw4atSo2267ra2tjYyx81iRHXLkiXWmadc96nHBiWoMvAmYt8Zu50aJ FKBKqwFssLqaGIWb5lEgFXTkCQViqu4jn3YI+zd2LjPiUVMfe2IpAHH58uX8/PxvfvOb1dXV tKQ++vSvZt5ArHP7uhelsmnIZPY9+9yEV5sjiQ4gg86qaAtu2ZjrqpFIATphmvLYzaLFaVaF uHYBEog2FXTkKjvWExDGm6zNk/2PwdIpLS39t3/7N+DN9evXzSLu7qukkbOrMb/zD49ICBvx iWoMYIO8Nftn/5ILbwxFo4E3htJqWF1NgLZN+RBQxDPCOjex1vUyTF4Mb3J4UV1tzVq2BpAC bMzk6j6o7/70pz+BJ81ORp8NXoZHaiTJ6yxVohoDb4LnrbEsGk12caZMqaI3b7C6WsphIGD5 /Rd6ZNCbOAd/EuDMm1z+H6poqs6YUf1pwRObHulbL1usM52opnZBdYQ+NDL0iurNXCwb6MRs 3BhKq2F1NQHaNuVD1La+7E/N4VGSSIAzb0Su6osbg/v+8HsZfWgjH1lQtCVy2Ewt6+AFm965 9969UDFo6NeMBZto4wYSQs+vfDzlChGXH54EIAb6w8sXRGoYHIu7BGLMG5DFx0ePyMabvaOf jCRRjQFvXPLW2BWNBuoYSqsBeLC6WniqFnsGCWAMNHftL77DePMG5HV68UIW5Kz9/tfUjaGv PfMzJWys/YEf30c++uaPsz387Hvf/dr31maCyvy99k6cGFWiGgNv6suKeBk3R/PvMNRVU3Zu 9KXVlMg0rK5mqnOMnOAlAYiBjrZitHjVnMgRY8+bwcuXGLxqP75PBYkCngxg4M13v39X+wN3 PfO1b7yaxQ954/MVYaIaA2wWr2zkBRtz0WhzaTWADVZX46VYsR9LCRwfaE+k/k3bomLPGzhh H3R1sEPi1W8Oy2DGyBv4/L7hPkkDvdUXLI98w4ZMgFfeGkIsS+PGUFoNq6shJEKVgPxhAteX 3W1+0SzRAqlYnjtMMISSwBs4PW++nO+MnJw/TfOeqf40wI9q6/jhDSSqqSpaKwlsfjunra1o TNjGzfRX1xty2JSsmBmqxsHOUyuBeSsfkj+bgAtvgDa5QtHBI3NjzKOE8Aa8at2/Y3reUwGP YZMGtm0AQvBvZjeHWD+Mr8gT1Rg4x6XcAI2r58qqDWFphtJqJCE0VldLLQ/CXnjPqUb59Ss7 b9S10Dm/tPd0zWkFS7nfkwKphPAGzuK725vZIAFhAlrIAIkaULZtsv40LyEDkSeqMcCGV94a jTfmotHm0mpYXS1shZvm/svrJ8gPG5ghoz+NcqZZ8caQzJh6btF3mmPZpJcc3oBk35gxzRo5 w7+RC0KD9xnAZFpCsECWPer+TS6ywJlekKhGklA0Qp3RxZ288tbYFY22LK2G1dXSzINQ1x6j B25ceZPR+8RcIdCxtG/ILk/WlqGNHe0w2fjhdT6J4s21v70DuylWnACuaBlzckFoum0b1Z/G EjXQ+sprkmzYkGnAts2Okikct22gK0vj5rmVTYadm2lPLQpV6WDnqZVA2+HVXtVZVO3ZeKPM Tt3KseQNmX6WOsVAp6S40bTzkijewKre3rKJzavGukNj7k2GRDUG2nHMW+Ng3JhLqymP3Swo Ta1CxIWHJ4F45eV05o1Wa5KYOBmIkMqUmtVjAEumWRKBkzTeQJKbwxPHh4ScrpGPlBRtksqy gclwzFujweZoyShDmAD8ai6tBrxZUPF0eEoHe06nBGLkSWOzqKi8khpZ1M+GFxfnZdCjc6Bl mlGfJCSOOmm8gZN05a1zNl41/zYNAEySRDXmcgPdcx/m60mzLBptGSmA1dXSyYOwV40Vbtgw Fr9WCeQNnIS3Vq/ia+LIk6jGwJuG0jncYWMuGm1ZWg2rq4WtdtPZf3Xj5PjpUZwxmwSSyRvw qh2dMokXcjpmzn7klZ2yudFgPnzz1jgUjbYsrYbV1dLJg1BXjbWi2fR2XFslkzdKRPwHHzA+ AeqMJXkS1RiAN6m081D+XWKMG3NpNYDNvCnLQ1U92HkKJdB3fl9cVSnOm0ECieUNrP3DA/uD mDhSJaoxwAYCoLsKnuAOG+hw3arXzJECo6q2GcKgsbpaCmEQ9pLr2osYVBY2ibEEkswbOC3n a9f5Qw4kqplbVC+hD41MiXveGoei0YAfQ2k1khAaq6uFrX9T1X9x7RNDNwdjrEpx6gwSSDhv QAK2SQfsk6TJlqjGgL2CqtYwLBvLotGWpdWwulqqSCBgsRAA/c4HfQz6CpvEWwLJ5w2k8jyQ 90d2K6d76jSpEtUYYMO33ADNLcui0Zal1ZTItOVzBaghHCIlEsDyNvHGCPPsk88bEMV/nznN +ETO7tmF0vrQQspboyFn06pC884NfDLp2aWGzRusrpYSDIhZ5s5DVcz6ChvGWwKp4A2conde 3+Zq4kiYqMYAv5qqNSF50qCu2t0LV5t5Yy6tBuxZOKdMjCbCURIvAflrqcVbwUs2+7TwBsR+ qqjQDjlyJqoxwObF8vaQYGNXNBrwYy6tBrzB6mqJx4CYBcYrSZpkqjuW00kRb+Ah0EPPjjUj BxLV5Be+LrMbDeY2akFHGHlrHIpGA2zMpdWwupoYRZyGUaBw5+VP34+l1sRJ+5VAingDIjIX LJA2UY2Bfy1LZ4o3bv6y3OKxm0Xz8DHPe9LAg1DXCAFp59875ldr4XFxlUC6eANn6YOuDs3E 8Zqo5v5Zu328gltOYZQbyKWCzr9j5LJV5p2buxate/6pxebHPBeWTwpVE2HnaZBALKpEx1Wp Szzv1PEGzsVAZTkgp2H+Mq8k8AEbOMTrKGLy1mi82Vs52TIszVxaDdiD1dXSAIOw19iyv0xi lYhTC1ECaeQNbORsXdXkAwPieTNyfntIeWuc66op1QdmrTEbN1hdLWxdnPj+V7fMCFGfYddy SyCNvIEzcvX60ISyQ16RI5439WVF4W3b2BWNtiuthtXVEg+DsBdYsvGp64NX5VaJfma3sbXP /KI6oqtHU0U+lRa6Kmt0VbVcjbaE1FpTVptS3igbOZevP7Voryfk0Lz5v/d8d9iwYd94jOzo zPsG/AI/P5qXbTN+7Ne+Pvb/ZvZ7PA1BNw4vb427cVNabzZuXhq3LGx9hP0nWAIQkPbh5Qt+ 1Ln0xwTjjcoTrdg0XW4a1t6clxjipJc3cB7f+fDayFc72HmQ400GJ9/7UZY3wJ6v3VNz/6ya 7339F7dn8UPe+OdNeHlrNNgcXDHOcucGIgWeG1Fg4UxbtDjB2hCXFrYE+i/0SA8OnxPkwxuw aAhYKPD4nJCsh6WaN3BSTr/zCeT2Z0SOyhvgyne/N3737Ta80T73zRuYUlvRmFA9adD5i5Xl lrz5c3WTGTZYXS1sdZzs/pNdIjoYb4hvRPnJ2jEaeGTFhu95pZ03ILgj/R954o1qzeR4o/nT wMrR/qoZQ4yd083WVlaFDRvLotEEP1OmVJl5g9XVks2DUFfX0FXiW0PF4sBgvNG8ZcqWTV5z xpuWGA+a/vwhbxR57O59j4UKCkLAkzYs6ysz2DHZv8IWjtJG+ck42Tzv38yqaAsbNtB/SfUy S+PGsrQaVlcLVR0nu/M0VFFj4A0FEJ27DH7J/SkLGvSnxeJbRpBJbu76qytyFKI89ouc9UtB RY0aUFCU5ZAaMuDaLd1gdHHn/tm/DJs3DsaNubQaqa42t3xEstUiri4MCaQBNqB23HijWCwZ y0X5od9n9mpM9g0JWlPbK79p74PoOAmORfsmdxIqdpx1ZoMhHlpv32Q3daCN+vm8b2RC1Dzx ZkfJlLBh42Dc/HLZJstIgcKZmBAac9h4lkBKYMOmxqm4Z52vzC4emv48KbRJczy05VWyaNsp Bzw48Ea3baP600i0NDtvQs1bo2Gst+i3lp40+PCFykbLSAGsrhbGd/9k94mwYeNQulqhfWM8 3w7ICfV5z6llHQIsG7ui0YRA5tJqxJn2cvkDyVaOuDq+EkDYpAsjzKtF3liIyg454fEG8taE V26ApWg0wMaytBpWV+OriNPQG8KGWf2mriHyxvqUWyInPN6EnbfGtWi0XWk1rK6WBkJwXCPC JnUM8bJg5I2ttGp2D7BvvQRpuXhloxhPWu/cey2LRgNsIFLAcudm8qhijsoIu0q2BBA2XnRv Gtsib5zOem37W0FAwnLsuCVdh/LvEsObTasK7SIFLEurAYGwulqyCcFxdQibNALE45qRNy4C CxU5YvLWOBeNBgLZlVZTNm+wutoKz3HAHJV4XLpC2HhUvCltjrxxP/HhIWdjRZkYywZG2V09 0864sYsUwOpqcVH30c4TYeOuRLBFRgLIG6YLgSX7AIv3THC5Adei0YRAlqXVwLhZUrwkWkWG o8svAYQNkwbBRsgbT9dA5/H32TNJu7JHTN4ajTcOxs1jlRalbkjswIKKp+XXdzjDCCWAsPGk Q7Ax2jceroHj5y95qpdjRx3glpi8Na47N4pxY1VaDWDzyvOlESoyHFp+CbTsL/Nw82BTlAD6 07xeA29d/NRrVVAzdWqq1gjbtnEoGk0iBcY/8Zp1DhusroaRAjYSmF15f8+pRq/3DrZHCaB9 4/kauHRlcELZIVePmV0DYXlrXItGA2/sSqsBgeZXPi7/V2ycoXgJFK559J0P+jzfNngASgDt G3/XwNXrQ7PWvuEDOaMWdIjJW+NaNNqhtBrABquridfjsRixdMszV65d8nfX4FEoAbRv/F8D zsmkLWnUsnSmSE8ajPVCeaVdGLRdaTUlMm1ZQSzUH05SpAQ27Z43dHPQ/w2DR6ZeAsibQJeA p0dzSlfWC4bNwRXj7GADn89YtMVy5warq4lU4nEZa/+bdYFuFTwYJYD+tODXwIG+v7MErU0q 7XTNW1P3s/+hFg/9H8+PvT0Dp+88SD769+9kWTX2Gz/4X9+oU/7k/rIrGk0SplmWVgMCYXW1 uDBAzDznrXyo/0JP8DslwT2c2bjB/KLWCyU9qZppDOWi9TVAA0lO7UpXuDpQjwEORvsmgPDU Q9/58NozS/c7bOdAuYGugifcCPGdB1WQKODJAAbe/OBntx2eftvz/+sfF2XxQ964vxyKRjuU VlOcacvnilFkOIr8EijZ+NSHly9wuEkS3QV33oQgLeRNCEKNqsvBoS8WbDlhhxyveWsW/fuw DGaMvIHPHxzhThpCIwfjxq60GsBm4mMLsLqa/BgQM8Pa1pevD16N6p6K0bgBeKOYPsXFw4kX QzOCCBzgb1rtac0oyhWazrZW2ublKT1kGhsLUWe6alZHyDay7FmAwNG+4Snk1/dfMCOnoKqV xRwhdMn60zTvmepPA/yotg4Tb5yNmzHVDZY7N1hdTYwej8Uo+Dgnu2oIxhuVM5QTLWuM5LCg WieUlaI66TKA0Uild93BEiyOhE/NPbOvNkBL5E0A4VkdevqdT0YVdWnUeXqx+7aNmUYKeAyb NLBtAxCCfzNEItaPw8vZuJn+6no73pSsmBkLbYiTDE8C8Djn8YF2zjdGorsLxhsLVqiQULFA QUPd4lX+Vw0azQoiJKEtJRveaMAR62ZD3vC/D+CB0MmVhwE5kLdm98LxjMaNvhmECWghAyRq QNm2yfrT3EIGoK6aQ1iaXWk1IBBWVwtPicelZ3ic8+JH5/jfFYnukYE3FBJ08QK0PZJ7r1GA AEf71SrUwJIYOepY2zeq3SMWN5gfOrTboGLHWW95a0b8Yy4IDd5nAJOBEAQLZNmj7t/kIgss YeZQVw04NLXc1pm2uGB5XNQizjMMCaxumYGPc/pQCW68yRgdqhmjjz1z4U3GPIHdGRVXFsCx Q0a2qR1vjD37WLb3Q9C+8S4z5iM+Obv/2LxfMNs3wBXNVs4Foem2bVR/mkPUgEPRaOfSalhd LQwNHpc+wYeGT9gw39k+GlLb+LT3SyGRgz+N7L9kHWdkVFNHOt7Q0QKkY51tpPrgcj3pJuNj Xd4OQd54k5fX1jevX/nrltnMyGGKBXDuzdm4sSutBrCZObYkLsoR58lXApClBoOevd7aCWhv ii0IfU3Im9BFDAN4NHT8U8fZuHEorYbV1fhq8Bj1tvNQFWapEaEFZBvDai8o7Dkib8KWcLZ/ MYbOjpWzHCIFRpTX2YWlYXW1GBGC11QhNOD8e8cE3QA4DEoA89kIvgZCNXSO5t8xctkqB97Y lVbD6mq8NHiM+oHSnPgsp+DbH4dD+0b0NRCeoeNQNNq5tBrwZmnJwhjpSpxqEAmAWYP50ETf 9jheRgLIm2guBDB0ji/4Ncc4AlfjxqG0GlZXC6K+43Us7tZEc8PjqMibaK+BL4YG/7ZjGS/k OBs3YN9MmVJlt3mD1dXixQx/sy2vn4B1OaO95XF0tG8ivgauXjh+YuGI4NQZXbrSYefmscp6 h0gBrK7mT4PH5Sh4tqard0PEFzoOjxJAf5oM10BwQ8e5rppDaTWAEFZXiws2/M0TcjxjygAZ bnOcA+7fSHQNgKHTt3y0P0PHoWi0c2k14M1rs8r8KTI8SnIJwFOcGO4s0R2OU0H7RrZr4PLJ Dq9xBK7GzQuVjU7ONKyutuIeycnhdXoQgdZzqlG2axvngxLA/RvprgFwr13sWNU7+78YbR1n 4wbsm8kTy+x4g9XVvKpyydvDVg1EoOGDNdLd1TghjE+T+Rq4ceWjt7e96oqcI0tHO4QJwJ8c SqthdTXJ4eF1erBVc/nT92W+qnFuKZcA2jdSXwDX3jt7puJp33XVgDcOpdWAN4vK/+JVqWF7 CSVQ3TgZt2qkvpNxcmjfxOUa+PStI5bUcS4a7RopgNXVJCSH1ykhaeJyF+M8MT4tTteAmTrO RaOdS6spCaEXlHrVbtheHglg+Fmc7l6cK9o3cbwGNOq4Gjd3LVr3/FOLHSLTFpZPkkd74kzY JQCk6Tu/L45Xb1LnvO/UZvOLWqy+0IyuEICuQJpW/IyUg1Z+xNZDC/sE4f5N2BIOpX+gzvrm OudIAYfSalhdjV25S9USctIgaUK5o4J1GpA3hkrTuoLTzXlJIg7yJtiFFunRf/34k7nb94Ed YwmeaXNqnR67KV4ilSbFyThLYNPueZj9LNK7zWlwTrxRiksPz8sbnqswLe2KfU4MeeNTcPIc 9vHVz/6/X/zq/uWbaeo4l1YDDhVUjEYVL78E4Hmahq4SjHKW53aznAkf3iiuteHFxcCc4n7J F+x3esgbv5KT5ri6uroHHnhgcOhm84mB31W/TqjjUFoNq6vJjxmYIeQIgCSb+OSmNPdZiPaN uleTsWsUGwd5E4vTnspJAmwAOdrSD5x/d0pd2/gnXnNwpmF1NZmRA5s0vWdaU3ktx3XRDPYN xRBTvIC6f5NZvu6vcRWI3bzRvon3Gb148eI//dM/mdfw0QefNK7vnDFmiSV15lc+LrPCTefc wKCBVDToOovjDenGG8Vo0TZldOEAFnjJRKxpCILfdDiKo3hyc0bexPv85Wd+HNZw8uhATUkD FB3QwPPqNEwILVeCztUtM44PtMf7QsTZu0iAinvWucsszRk6SDpBtMH80HG/TcC4ARPHdRWf Xb3euf1IwZSVymOeywrSaUDIturi2ifQoHG9dLFBkiSA9k2MzyaJFPC0gIt/+2jXwZqSjU/J pnzTMx/ATMv+sosfnfN04rAxSiABEkDexPgkGiIFPK3kw8sX2g6vRvAI4xxsz0BkMz5D4+kq xcYJkwDyRuwJzeSpoDyyat4KenuQLRrSLlLA63oAPBB3CylShGneVA0E1gxgBpM3e70ssX0i JYC8EXdaSVwKnUoJtgUzcNFiUPR5lhyn5hop4HVhEBm1/8062LtOFQ9CWiyIEYQJLPd6FrA9 SiDBEkDeiD65DrzxQJtbtxgjBfwtr/9CD2xlo9HjiUbElIH8ZkM3B/2JHY9CCSRbAsgb0edX D5WsPw2sHNXWYZqPj0gBpn5NjeD5dgjVrWsvAmXqSfmmpDHsykBmMzRl/F1deFTaJIC8EX3G rY0Y4lFTw+5dd3CCRAr4XjA43IA9EFsFNb5SghPLZYLZB3YMiAKfzfR9LeGB6ZQA8kb0ebfi Tfaz7H9ulg6vSIGAK4dQK/heD6ZP4oPcYIG1rS9DOB+4GdFXFvCywcPTLAHkjeizb+JNDi/q n1xKXnCPFAguAnC7QQgW4IdYP/NWPhRfAwhSMsMSYCE9pxoxriz4tYE9oAQ0CSBvxF0MuZp9 VN0+nTGj+tPoFBZ33nmnlj6WvPnqV7/KklNA3MKsRjIQSFobCJxjQBewXQCWQBd0kUV72eDo yZYA8iZZ55ff8z1hyAWcUaDT4QVP/ICKh5120PVh7wbBlj4ZBWKUYVB4EcPlyrVLYawR+0QJ oATsJIC8Sc61wff5nkjkogEJeACBxQQPjC9CMu2FlkokZxAHRQk4SAB5k7TLg9fzPUmTC64H JYASiFoCyJuozwDv8bk838N7UtgfSgAlgBK4hbxJ2kXA5fmepAkF14MSQAlIIAHkjQQngesU gj/fw3U62BlKACWAEshKAHmTtEsh+PM9SZMIrgclgBKQQwLIGznOA49Z+Hu+h8fI2AdKACWA EnCXAPLGXUbYAiWAEkAJoASCSwB5E1yG2ANKACWAEkAJuEsAeeMuI2yBEkAJoARQAsElgLwJ LkPsASWAEkAJoATcJYC8cZcRtkAJoARQAiiB4BJA3gSXIfaAEkAJoARQAu4SQN64ywhboARQ AigBlEBwCSBvgssQe0AJoARQAigBdwkgb9xlhC1QAigBlABKILgE/n/nw+EfZ4S+dAAAAABJ RU5ErkJggg== --------------040701070906020708020505-- --------------010702040202080003090402-- --===============1086458984947120423== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users --===============1086458984947120423==-- From xen-users-bounces@lists.xen.org Mon Sep 17 12:43:20 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Mon, 17 Sep 2012 12:43:20 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TDaeW-00072U-2g; Mon, 17 Sep 2012 12:42:16 +0000 Received: from mail27.messagelabs.com ([193.109.254.147]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TDZN3-0004kh-5O for xen-users@lists.xen.org; Mon, 17 Sep 2012 11:20:09 +0000 X-Env-Sender: nitin.kobain@gmail.com X-Msg-Ref: server-2.tower-27.messagelabs.com!1347880801!11281124!1 X-Originating-IP: [209.85.220.173] X-SpamReason: No, hits=1.2 required=7.0 tests=HTML_10_20,HTML_MESSAGE, ML_RADAR_SPEW_LINKS_14,RCVD_BY_IP,spamassassin: X-StarScan-Received: X-StarScan-Version: 6.6.1.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 26673 invoked from network); 17 Sep 2012 11:20:02 -0000 Received: from mail-vc0-f173.google.com (HELO mail-vc0-f173.google.com) (209.85.220.173) by server-2.tower-27.messagelabs.com with RC4-SHA encrypted SMTP; 17 Sep 2012 11:20:02 -0000 Received: by vcbfl15 with SMTP id fl15so8667392vcb.32 for ; Mon, 17 Sep 2012 04:20:01 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:from:date:message-id:subject:to:content-type; bh=4ydL2ixMz3PYJdfmAN5MEJtthuaa+XCltu4TjMC6/W8=; b=09fIFKLlYj0lrN2gNMujpbJk5ua/kn4ki9vMaWIivzaN6//BJodfnKksjMSzlrPGmN U0LWBO1RhHvPfRDprNWk0X3UIJjNIkmwPlUIT1coLYU1/gVSyv9flpDsu4a+Pvr4aeiw LmWBWSBFRl3cLRmFa89rC2H9moQ6BU/FFijJ0gv8oYpBy0+pHWS3cAHUokxlYbGetbUh DITD/Dj7tIyOUbl5j56gh6KryvkMnU8/zPkHW7pChaXabkgbkNHv3Ifwe9eoOKY+AF79 n84e9gAJHoUE6bB57DlfiDJMrXdT65NjiLntuUMQb4lWM6zX7xnAtQTN2WkUkTY/Edeg r72w== Received: by 10.220.142.16 with SMTP id o16mr7180839vcu.3.1347880801586; Mon, 17 Sep 2012 04:20:01 -0700 (PDT) MIME-Version: 1.0 Received: by 10.58.102.37 with HTTP; Mon, 17 Sep 2012 04:19:21 -0700 (PDT) From: Nitin Gupta Date: Mon, 17 Sep 2012 16:49:21 +0530 Message-ID: To: xen-users@lists.xen.org X-Mailman-Approved-At: Mon, 17 Sep 2012 12:42:14 +0000 Subject: [Xen-users] /proc/xen/capabilities file not present in DomU X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============6940999449281262290==" Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org --===============6940999449281262290== Content-Type: multipart/alternative; boundary=f46d043be0b660cf2704c9e3f474 --f46d043be0b660cf2704c9e3f474 Content-Type: text/plain; charset=ISO-8859-1 Is it possible that '/proc/xen/capabilities' file is not present in DomU ? I have installed debian as domU, but it does not show above-mentioned file. Is something wrong with my installation? How can I verify my setup? -- Thanks, Nitin Gupta --f46d043be0b660cf2704c9e3f474 Content-Type: text/html; charset=ISO-8859-1 Is it possible that '/proc/xen/capabilities' file is not present in DomU ?

I have installed debian as domU, but it does not show above-mentioned file. Is something wrong with my installation? How can I verify my setup?

--
Thanks,
Nitin Gupta

--f46d043be0b660cf2704c9e3f474-- --===============6940999449281262290== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users --===============6940999449281262290==-- From xen-users-bounces@lists.xen.org Mon Sep 17 12:43:20 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Mon, 17 Sep 2012 12:43:20 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TDaeW-00072U-2g; Mon, 17 Sep 2012 12:42:16 +0000 Received: from mail27.messagelabs.com ([193.109.254.147]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TDZN3-0004kh-5O for xen-users@lists.xen.org; Mon, 17 Sep 2012 11:20:09 +0000 X-Env-Sender: nitin.kobain@gmail.com X-Msg-Ref: server-2.tower-27.messagelabs.com!1347880801!11281124!1 X-Originating-IP: [209.85.220.173] X-SpamReason: No, hits=1.2 required=7.0 tests=HTML_10_20,HTML_MESSAGE, ML_RADAR_SPEW_LINKS_14,RCVD_BY_IP,spamassassin: X-StarScan-Received: X-StarScan-Version: 6.6.1.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 26673 invoked from network); 17 Sep 2012 11:20:02 -0000 Received: from mail-vc0-f173.google.com (HELO mail-vc0-f173.google.com) (209.85.220.173) by server-2.tower-27.messagelabs.com with RC4-SHA encrypted SMTP; 17 Sep 2012 11:20:02 -0000 Received: by vcbfl15 with SMTP id fl15so8667392vcb.32 for ; Mon, 17 Sep 2012 04:20:01 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:from:date:message-id:subject:to:content-type; bh=4ydL2ixMz3PYJdfmAN5MEJtthuaa+XCltu4TjMC6/W8=; b=09fIFKLlYj0lrN2gNMujpbJk5ua/kn4ki9vMaWIivzaN6//BJodfnKksjMSzlrPGmN U0LWBO1RhHvPfRDprNWk0X3UIJjNIkmwPlUIT1coLYU1/gVSyv9flpDsu4a+Pvr4aeiw LmWBWSBFRl3cLRmFa89rC2H9moQ6BU/FFijJ0gv8oYpBy0+pHWS3cAHUokxlYbGetbUh DITD/Dj7tIyOUbl5j56gh6KryvkMnU8/zPkHW7pChaXabkgbkNHv3Ifwe9eoOKY+AF79 n84e9gAJHoUE6bB57DlfiDJMrXdT65NjiLntuUMQb4lWM6zX7xnAtQTN2WkUkTY/Edeg r72w== Received: by 10.220.142.16 with SMTP id o16mr7180839vcu.3.1347880801586; Mon, 17 Sep 2012 04:20:01 -0700 (PDT) MIME-Version: 1.0 Received: by 10.58.102.37 with HTTP; Mon, 17 Sep 2012 04:19:21 -0700 (PDT) From: Nitin Gupta Date: Mon, 17 Sep 2012 16:49:21 +0530 Message-ID: To: xen-users@lists.xen.org X-Mailman-Approved-At: Mon, 17 Sep 2012 12:42:14 +0000 Subject: [Xen-users] /proc/xen/capabilities file not present in DomU X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============6940999449281262290==" Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org --===============6940999449281262290== Content-Type: multipart/alternative; boundary=f46d043be0b660cf2704c9e3f474 --f46d043be0b660cf2704c9e3f474 Content-Type: text/plain; charset=ISO-8859-1 Is it possible that '/proc/xen/capabilities' file is not present in DomU ? I have installed debian as domU, but it does not show above-mentioned file. Is something wrong with my installation? How can I verify my setup? -- Thanks, Nitin Gupta --f46d043be0b660cf2704c9e3f474 Content-Type: text/html; charset=ISO-8859-1 Is it possible that '/proc/xen/capabilities' file is not present in DomU ?

I have installed debian as domU, but it does not show above-mentioned file. Is something wrong with my installation? How can I verify my setup?

--
Thanks,
Nitin Gupta

--f46d043be0b660cf2704c9e3f474-- --===============6940999449281262290== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users --===============6940999449281262290==-- From xen-users-bounces@lists.xen.org Mon Sep 17 14:40:06 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Mon, 17 Sep 2012 14:40:06 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TDcTa-0001pI-5s; Mon, 17 Sep 2012 14:39:06 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TDcTY-0001ow-6E for xen-users@lists.xen.org; Mon, 17 Sep 2012 14:39:04 +0000 Received: from [85.158.138.51:42629] by server-11.bemta-3.messagelabs.com id 4C/51-30250-70637505; Mon, 17 Sep 2012 14:39:03 +0000 X-Env-Sender: peter.phaal@gmail.com X-Msg-Ref: server-8.tower-174.messagelabs.com!1347892741!30839970!1 X-Originating-IP: [209.85.216.173] X-SpamReason: No, hits=0.3 required=7.0 tests=ML_RADAR_SPEW_LINKS_14, RCVD_BY_IP,spamassassin: X-StarScan-Received: X-StarScan-Version: 6.6.1.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 17444 invoked from network); 17 Sep 2012 14:39:02 -0000 Received: from mail-qc0-f173.google.com (HELO mail-qc0-f173.google.com) (209.85.216.173) by server-8.tower-174.messagelabs.com with RC4-SHA encrypted SMTP; 17 Sep 2012 14:39:02 -0000 Received: by qcab12 with SMTP id b12so6034483qca.32 for ; Mon, 17 Sep 2012 07:39:00 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=qOEfGqvewfcmd/DvB0jHwGxcFSyR9JJO4bNjhfOs5VQ=; b=CiTQApC+BeQ06s6Fmk/7Qz4RPEOiakAFSZt0/myY3LK2sxN3iLsgl3SY4f8K8QFE4L x7lSIVAinLjt8YTw9QKL+obYh6uVIouwR6cq+IHYFupdelZ+8ExbvI25FlqA2s78ioLe bYjojVhDV6MQNhW/tPfxqXHmMhX/3N756kkt/CtC/oHu6fmZb2Jz+G4Sn6+lIknxGgLA tIBCYH8WmEEn8J9esvClwuc1GGT0nMvLCKxnrYQJoOPVQd0qbA13dn4i18c9ccwDEOxk 9UZk2NYQR3xtp3xPI/SM4QoMEVHBRUtHoJNWxXjQDjf5o2+hPgAOKl12RUwxdHQ/D2aD b3Eg== MIME-Version: 1.0 Received: by 10.224.185.148 with SMTP id co20mr28030757qab.4.1347892740617; Mon, 17 Sep 2012 07:39:00 -0700 (PDT) Received: by 10.49.15.133 with HTTP; Mon, 17 Sep 2012 07:39:00 -0700 (PDT) In-Reply-To: <20120916205125.GD3867@bitfolk.com> References: <20120916122326.GA3867@bitfolk.com> <20120916205125.GD3867@bitfolk.com> Date: Mon, 17 Sep 2012 07:39:00 -0700 Message-ID: From: Peter Phaal To: Andy Smith Cc: xen-users@lists.xen.org Subject: Re: [Xen-users] How are you measuring CPU usage? X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org If you want to roll your own analysis then the following document describes the standard sFlow metrics that the Host sFlow agent is exporting: http://sflow.org/sflow_host.txt sflowtool is an open source sFlow decoder. http://blog.sflow.com/2011/12/sflowtool.html You can either take the C source code and incorporate it directly in your project, or parse the ASCII output and send it to the tool of your choice. sflow2graphite is a Perl script for converting sFlow messages to Graphite's metric format: http://blog.sflow.com/2012/01/graphite.html On Sun, Sep 16, 2012 at 1:51 PM, Andy Smith wrote: > Interesting, thanks. > > I'm probably not interested in replacing *all* of my stats with > this right now, but it looks like libxenstat and this may be a good > start if I want to do higher-frequency stats gathering for my own > purposes. _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Mon Sep 17 14:40:06 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Mon, 17 Sep 2012 14:40:06 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TDcTa-0001pI-5s; Mon, 17 Sep 2012 14:39:06 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TDcTY-0001ow-6E for xen-users@lists.xen.org; Mon, 17 Sep 2012 14:39:04 +0000 Received: from [85.158.138.51:42629] by server-11.bemta-3.messagelabs.com id 4C/51-30250-70637505; Mon, 17 Sep 2012 14:39:03 +0000 X-Env-Sender: peter.phaal@gmail.com X-Msg-Ref: server-8.tower-174.messagelabs.com!1347892741!30839970!1 X-Originating-IP: [209.85.216.173] X-SpamReason: No, hits=0.3 required=7.0 tests=ML_RADAR_SPEW_LINKS_14, RCVD_BY_IP,spamassassin: X-StarScan-Received: X-StarScan-Version: 6.6.1.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 17444 invoked from network); 17 Sep 2012 14:39:02 -0000 Received: from mail-qc0-f173.google.com (HELO mail-qc0-f173.google.com) (209.85.216.173) by server-8.tower-174.messagelabs.com with RC4-SHA encrypted SMTP; 17 Sep 2012 14:39:02 -0000 Received: by qcab12 with SMTP id b12so6034483qca.32 for ; Mon, 17 Sep 2012 07:39:00 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=qOEfGqvewfcmd/DvB0jHwGxcFSyR9JJO4bNjhfOs5VQ=; b=CiTQApC+BeQ06s6Fmk/7Qz4RPEOiakAFSZt0/myY3LK2sxN3iLsgl3SY4f8K8QFE4L x7lSIVAinLjt8YTw9QKL+obYh6uVIouwR6cq+IHYFupdelZ+8ExbvI25FlqA2s78ioLe bYjojVhDV6MQNhW/tPfxqXHmMhX/3N756kkt/CtC/oHu6fmZb2Jz+G4Sn6+lIknxGgLA tIBCYH8WmEEn8J9esvClwuc1GGT0nMvLCKxnrYQJoOPVQd0qbA13dn4i18c9ccwDEOxk 9UZk2NYQR3xtp3xPI/SM4QoMEVHBRUtHoJNWxXjQDjf5o2+hPgAOKl12RUwxdHQ/D2aD b3Eg== MIME-Version: 1.0 Received: by 10.224.185.148 with SMTP id co20mr28030757qab.4.1347892740617; Mon, 17 Sep 2012 07:39:00 -0700 (PDT) Received: by 10.49.15.133 with HTTP; Mon, 17 Sep 2012 07:39:00 -0700 (PDT) In-Reply-To: <20120916205125.GD3867@bitfolk.com> References: <20120916122326.GA3867@bitfolk.com> <20120916205125.GD3867@bitfolk.com> Date: Mon, 17 Sep 2012 07:39:00 -0700 Message-ID: From: Peter Phaal To: Andy Smith Cc: xen-users@lists.xen.org Subject: Re: [Xen-users] How are you measuring CPU usage? X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org If you want to roll your own analysis then the following document describes the standard sFlow metrics that the Host sFlow agent is exporting: http://sflow.org/sflow_host.txt sflowtool is an open source sFlow decoder. http://blog.sflow.com/2011/12/sflowtool.html You can either take the C source code and incorporate it directly in your project, or parse the ASCII output and send it to the tool of your choice. sflow2graphite is a Perl script for converting sFlow messages to Graphite's metric format: http://blog.sflow.com/2012/01/graphite.html On Sun, Sep 16, 2012 at 1:51 PM, Andy Smith wrote: > Interesting, thanks. > > I'm probably not interested in replacing *all* of my stats with > this right now, but it looks like libxenstat and this may be a good > start if I want to do higher-frequency stats gathering for my own > purposes. _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Mon Sep 17 15:23:16 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Mon, 17 Sep 2012 15:23:16 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TDd9L-0003UC-Ta; Mon, 17 Sep 2012 15:22:15 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TDd9K-0003U7-2K for xen-users@lists.xen.org; Mon, 17 Sep 2012 15:22:14 +0000 Received: from [85.158.138.51:12806] by server-11.bemta-3.messagelabs.com id 55/87-30250-52047505; Mon, 17 Sep 2012 15:22:13 +0000 X-Env-Sender: pasik@iki.fi X-Msg-Ref: server-12.tower-174.messagelabs.com!1347895332!22959859!1 X-Originating-IP: [192.89.123.25] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogMTkyLjg5LjEyMy4yNSA9PiA1MDQ5ODc=\n X-StarScan-Received: X-StarScan-Version: 6.6.1.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 31603 invoked from network); 17 Sep 2012 15:22:12 -0000 Received: from smtp.tele.fi (HELO smtp.tele.fi) (192.89.123.25) by server-12.tower-174.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 17 Sep 2012 15:22:12 -0000 X-Originating-Ip: [194.89.68.22] Received: from ydin.reaktio.net (reaktio.net [194.89.68.22]) by smtp.tele.fi (Postfix) with ESMTP id 905CB2A20; Mon, 17 Sep 2012 18:22:11 +0300 (EEST) Received: by ydin.reaktio.net (Postfix, from userid 1001) id 032382005D; Mon, 17 Sep 2012 18:22:10 +0300 (EEST) Date: Mon, 17 Sep 2012 18:22:10 +0300 From: Pasi =?iso-8859-1?Q?K=E4rkk=E4inen?= To: nathan@gossamer-threads.com Message-ID: <20120917152210.GK8912@reaktio.net> References: MIME-Version: 1.0 Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.20 (2009-06-14) Cc: xen-users@lists.xen.org Subject: Re: [Xen-users] Xen 4.1.4 release imminent? X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org On Thu, Sep 06, 2012 at 10:14:46PM +0000, nathan@gossamer-threads.com wrote: > Hi, > > Just wondering if there's a release of xen 4.1.4 being planned for the > near future to bundle up the recent XSA's? > At least I'm not aware of such plans. You can grab xen-4.1-testing.hg which has all the securify fixes in it: http://xenbits.xen.org/hg/xen-4.1-testing.hg/ It's currently at version 4.1.4-pre. Hopefully that helps, -- Pasi _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Mon Sep 17 15:23:16 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Mon, 17 Sep 2012 15:23:16 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TDd9L-0003UC-Ta; Mon, 17 Sep 2012 15:22:15 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TDd9K-0003U7-2K for xen-users@lists.xen.org; Mon, 17 Sep 2012 15:22:14 +0000 Received: from [85.158.138.51:12806] by server-11.bemta-3.messagelabs.com id 55/87-30250-52047505; Mon, 17 Sep 2012 15:22:13 +0000 X-Env-Sender: pasik@iki.fi X-Msg-Ref: server-12.tower-174.messagelabs.com!1347895332!22959859!1 X-Originating-IP: [192.89.123.25] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogMTkyLjg5LjEyMy4yNSA9PiA1MDQ5ODc=\n X-StarScan-Received: X-StarScan-Version: 6.6.1.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 31603 invoked from network); 17 Sep 2012 15:22:12 -0000 Received: from smtp.tele.fi (HELO smtp.tele.fi) (192.89.123.25) by server-12.tower-174.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 17 Sep 2012 15:22:12 -0000 X-Originating-Ip: [194.89.68.22] Received: from ydin.reaktio.net (reaktio.net [194.89.68.22]) by smtp.tele.fi (Postfix) with ESMTP id 905CB2A20; Mon, 17 Sep 2012 18:22:11 +0300 (EEST) Received: by ydin.reaktio.net (Postfix, from userid 1001) id 032382005D; Mon, 17 Sep 2012 18:22:10 +0300 (EEST) Date: Mon, 17 Sep 2012 18:22:10 +0300 From: Pasi =?iso-8859-1?Q?K=E4rkk=E4inen?= To: nathan@gossamer-threads.com Message-ID: <20120917152210.GK8912@reaktio.net> References: MIME-Version: 1.0 Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.20 (2009-06-14) Cc: xen-users@lists.xen.org Subject: Re: [Xen-users] Xen 4.1.4 release imminent? X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org On Thu, Sep 06, 2012 at 10:14:46PM +0000, nathan@gossamer-threads.com wrote: > Hi, > > Just wondering if there's a release of xen 4.1.4 being planned for the > near future to bundle up the recent XSA's? > At least I'm not aware of such plans. You can grab xen-4.1-testing.hg which has all the securify fixes in it: http://xenbits.xen.org/hg/xen-4.1-testing.hg/ It's currently at version 4.1.4-pre. Hopefully that helps, -- Pasi _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Mon Sep 17 17:17:27 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Mon, 17 Sep 2012 17:17:27 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TDevq-00014V-VY; Mon, 17 Sep 2012 17:16:26 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TDevp-000145-QK for xen-users@lists.xen.org; Mon, 17 Sep 2012 17:16:25 +0000 Received: from [85.158.138.51:10440] by server-4.bemta-3.messagelabs.com id 38/6B-24831-7EA57505; Mon, 17 Sep 2012 17:16:23 +0000 X-Env-Sender: dunlapg@gmail.com X-Msg-Ref: server-6.tower-174.messagelabs.com!1347902182!22872578!1 X-Originating-IP: [74.125.82.173] X-SpamReason: No, hits=0.3 required=7.0 tests=RCVD_BY_IP X-StarScan-Received: X-StarScan-Version: 6.6.1.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 1698 invoked from network); 17 Sep 2012 17:16:23 -0000 Received: from mail-we0-f173.google.com (HELO mail-we0-f173.google.com) (74.125.82.173) by server-6.tower-174.messagelabs.com with RC4-SHA encrypted SMTP; 17 Sep 2012 17:16:23 -0000 Received: by weyz53 with SMTP id z53so4761742wey.32 for ; Mon, 17 Sep 2012 10:16:22 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:date:x-google-sender-auth:message-id:subject :from:to:content-type; bh=YgwfEtDpTEO5qNtiLjLhj/TBE+mLKwMAkpn0wxP2EHA=; b=0gcjLb0u1WKYVW5u33ENSartw7YSMZtVl+ks+jhWTuzp258xtEmpP7HrTzaULPGLBg kqMOTmI0miXiGGz3gCjWFUzyEvRl/RopRHJRog2lf+RVW3KdUae9PO64r+Np8SSX9KPx kCFct/wwI3DdY4j7L65LMhUrQ1IDp6h9Gos32XFwOCRil/EJbD5NJoO49hlbe8iXJW2w Rp7B3+9whn6McUH8wikmJH0ymD9tDVqHvp1ADpasqs3wovzGi5WkQigy2p4OPzDlwNdU XlToOIdOGDQjueCi1gbGmTNbQ0LXX1GajBykdBTJehhFAbcsBZ5OLudHOyUrT1VU/Pvi DHXg== MIME-Version: 1.0 Received: by 10.180.109.129 with SMTP id hs1mr17535889wib.0.1347902182533; Mon, 17 Sep 2012 10:16:22 -0700 (PDT) Received: by 10.223.94.75 with HTTP; Mon, 17 Sep 2012 10:16:22 -0700 (PDT) Date: Mon, 17 Sep 2012 18:16:22 +0100 X-Google-Sender-Auth: IDMIhoye6JU342CTTZQh3qzFzgQ Message-ID: From: George Dunlap To: xen-devel@lists.xen.org, xen-users@lists.xen.org, xen-announce@lists.xen.org Subject: [Xen-users] Experimenting with UserVoice.com X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org One of the issues in any software project can be the disconnect between what users want or would find useful, and the developers' idea of what users want or would find useful, and Xen is no exception. To help address this issue, I am going to start experimenting with a website called UserVoice. UserVoice allows users to do two things: * Suggest improvements or features * "Vote" for which improvements or features they think are most important. You can find the Xen.org uservoice page here: http://xenorg.uservoice.com You can either create an account, or log in with an existing Google or Facebook account. Obviously we can't promise that everything that is suggested or voted highly will be implemented! But hopefully it will give the developers a better idea what our users are thinking. To make sure that the site is as useful as possible, please try focus on *things you want to do*, rather than *how* you want to be able to do them. That will help us choose the best way to help you; or perhaps point you to an existing way of doing something that's already available. Enjoy! -George _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Mon Sep 17 17:17:27 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Mon, 17 Sep 2012 17:17:27 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TDevq-00014V-VY; Mon, 17 Sep 2012 17:16:26 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TDevp-000145-QK for xen-users@lists.xen.org; Mon, 17 Sep 2012 17:16:25 +0000 Received: from [85.158.138.51:10440] by server-4.bemta-3.messagelabs.com id 38/6B-24831-7EA57505; Mon, 17 Sep 2012 17:16:23 +0000 X-Env-Sender: dunlapg@gmail.com X-Msg-Ref: server-6.tower-174.messagelabs.com!1347902182!22872578!1 X-Originating-IP: [74.125.82.173] X-SpamReason: No, hits=0.3 required=7.0 tests=RCVD_BY_IP X-StarScan-Received: X-StarScan-Version: 6.6.1.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 1698 invoked from network); 17 Sep 2012 17:16:23 -0000 Received: from mail-we0-f173.google.com (HELO mail-we0-f173.google.com) (74.125.82.173) by server-6.tower-174.messagelabs.com with RC4-SHA encrypted SMTP; 17 Sep 2012 17:16:23 -0000 Received: by weyz53 with SMTP id z53so4761742wey.32 for ; Mon, 17 Sep 2012 10:16:22 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:date:x-google-sender-auth:message-id:subject :from:to:content-type; bh=YgwfEtDpTEO5qNtiLjLhj/TBE+mLKwMAkpn0wxP2EHA=; b=0gcjLb0u1WKYVW5u33ENSartw7YSMZtVl+ks+jhWTuzp258xtEmpP7HrTzaULPGLBg kqMOTmI0miXiGGz3gCjWFUzyEvRl/RopRHJRog2lf+RVW3KdUae9PO64r+Np8SSX9KPx kCFct/wwI3DdY4j7L65LMhUrQ1IDp6h9Gos32XFwOCRil/EJbD5NJoO49hlbe8iXJW2w Rp7B3+9whn6McUH8wikmJH0ymD9tDVqHvp1ADpasqs3wovzGi5WkQigy2p4OPzDlwNdU XlToOIdOGDQjueCi1gbGmTNbQ0LXX1GajBykdBTJehhFAbcsBZ5OLudHOyUrT1VU/Pvi DHXg== MIME-Version: 1.0 Received: by 10.180.109.129 with SMTP id hs1mr17535889wib.0.1347902182533; Mon, 17 Sep 2012 10:16:22 -0700 (PDT) Received: by 10.223.94.75 with HTTP; Mon, 17 Sep 2012 10:16:22 -0700 (PDT) Date: Mon, 17 Sep 2012 18:16:22 +0100 X-Google-Sender-Auth: IDMIhoye6JU342CTTZQh3qzFzgQ Message-ID: From: George Dunlap To: xen-devel@lists.xen.org, xen-users@lists.xen.org, xen-announce@lists.xen.org Subject: [Xen-users] Experimenting with UserVoice.com X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org One of the issues in any software project can be the disconnect between what users want or would find useful, and the developers' idea of what users want or would find useful, and Xen is no exception. To help address this issue, I am going to start experimenting with a website called UserVoice. UserVoice allows users to do two things: * Suggest improvements or features * "Vote" for which improvements or features they think are most important. You can find the Xen.org uservoice page here: http://xenorg.uservoice.com You can either create an account, or log in with an existing Google or Facebook account. Obviously we can't promise that everything that is suggested or voted highly will be implemented! But hopefully it will give the developers a better idea what our users are thinking. To make sure that the site is as useful as possible, please try focus on *things you want to do*, rather than *how* you want to be able to do them. That will help us choose the best way to help you; or perhaps point you to an existing way of doing something that's already available. Enjoy! -George _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Mon Sep 17 20:35:49 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Mon, 17 Sep 2012 20:35:49 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TDi1S-0007oG-T8; Mon, 17 Sep 2012 20:34:26 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TDi1R-0007oB-9t for xen-users@lists.xensource.com; Mon, 17 Sep 2012 20:34:25 +0000 Received: from [85.158.139.83:16288] by server-7.bemta-5.messagelabs.com id 9C/3E-19703-05987505; Mon, 17 Sep 2012 20:34:24 +0000 X-Env-Sender: kclo2000@gmail.com X-Msg-Ref: server-5.tower-182.messagelabs.com!1347914063!30588583!1 X-Originating-IP: [74.125.82.171] X-SpamReason: No, hits=1.2 required=7.0 tests=HTML_10_20,HTML_MESSAGE, ML_RADAR_SPEW_LINKS_14,RCVD_BY_IP,spamassassin: X-StarScan-Received: X-StarScan-Version: 6.6.1.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 28262 invoked from network); 17 Sep 2012 20:34:23 -0000 Received: from mail-we0-f171.google.com (HELO mail-we0-f171.google.com) (74.125.82.171) by server-5.tower-182.messagelabs.com with RC4-SHA encrypted SMTP; 17 Sep 2012 20:34:23 -0000 Received: by weys43 with SMTP id s43so4883817wey.30 for ; Mon, 17 Sep 2012 13:34:23 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:date:message-id:subject:from:to:content-type; bh=lredbE/IohfuqpKIDtHi0P1EJFyu7JqUhjQh7I1q5VE=; b=dmXK2wN2mndn+v9hClW12Qb6Tvms+yMs77++F7LPCo6kEresPjSnoiWsm72kFRxR8x mBwe1BzTQDaEYA1isvtflwrTlaCYoehjpfEFEzxGyJzOszHotNYkGv7cMbjH46wwcevn ZgJ6Evgm1erO0k+iFoylKA6T/AVsBN9DxLT0CuV1LQSISJmRf8nAah0zhXsMXzwC3yDg LpcSdrHFXqoIHFPtgsrep+xH+ZTQ8E93E8Lsz9l6/zLGMOJm42wWZV85Ja792k0hj7NE wL+D/Q6QzBC93fVqkgs9P+7dbQaMdFi8pPeBVrRfWUn8UAvbPuXjzbiYckkL7rc7CAjX RyEA== MIME-Version: 1.0 Received: by 10.216.233.208 with SMTP id p58mr6202484weq.56.1347914063595; Mon, 17 Sep 2012 13:34:23 -0700 (PDT) Received: by 10.194.18.170 with HTTP; Mon, 17 Sep 2012 13:34:23 -0700 (PDT) Date: Tue, 18 Sep 2012 04:34:23 +0800 Message-ID: From: KC LO To: xen-users@lists.xensource.com Subject: [Xen-users] Existing Xen 3.4 work with OpenStack or CloudStack X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============5309962895243443140==" Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org --===============5309962895243443140== Content-Type: multipart/alternative; boundary=000e0cd517f4f2c82904c9ebb2de --000e0cd517f4f2c82904c9ebb2de Content-Type: text/plain; charset=ISO-8859-1 Dear all, We have a pool of servers running CentOS5+Xen3.4.4. Any suggested method to use OpenStack or CloudStack if I want to manage existing VM through a Cloud Mgt platform. I searched doc on OpenStack or CloudStack that they will work for registering new server and creating new VM and not to registered existing VM . Cheers! --000e0cd517f4f2c82904c9ebb2de Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Dear all,

We have a pool of servers running CentOS5+Xen3= .4.4. =A0Any suggested method to use OpenStack or CloudStack if I want to m= anage existing VM through a Cloud Mgt platform. =A0I searched doc on OpenSt= ack or CloudStack that they will work for registering new server and creati= ng new VM and not to registered existing VM .

Cheers!
--000e0cd517f4f2c82904c9ebb2de-- --===============5309962895243443140== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users --===============5309962895243443140==-- From xen-users-bounces@lists.xen.org Mon Sep 17 20:35:49 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Mon, 17 Sep 2012 20:35:49 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TDi1S-0007oG-T8; Mon, 17 Sep 2012 20:34:26 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TDi1R-0007oB-9t for xen-users@lists.xensource.com; Mon, 17 Sep 2012 20:34:25 +0000 Received: from [85.158.139.83:16288] by server-7.bemta-5.messagelabs.com id 9C/3E-19703-05987505; Mon, 17 Sep 2012 20:34:24 +0000 X-Env-Sender: kclo2000@gmail.com X-Msg-Ref: server-5.tower-182.messagelabs.com!1347914063!30588583!1 X-Originating-IP: [74.125.82.171] X-SpamReason: No, hits=1.2 required=7.0 tests=HTML_10_20,HTML_MESSAGE, ML_RADAR_SPEW_LINKS_14,RCVD_BY_IP,spamassassin: X-StarScan-Received: X-StarScan-Version: 6.6.1.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 28262 invoked from network); 17 Sep 2012 20:34:23 -0000 Received: from mail-we0-f171.google.com (HELO mail-we0-f171.google.com) (74.125.82.171) by server-5.tower-182.messagelabs.com with RC4-SHA encrypted SMTP; 17 Sep 2012 20:34:23 -0000 Received: by weys43 with SMTP id s43so4883817wey.30 for ; Mon, 17 Sep 2012 13:34:23 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:date:message-id:subject:from:to:content-type; bh=lredbE/IohfuqpKIDtHi0P1EJFyu7JqUhjQh7I1q5VE=; b=dmXK2wN2mndn+v9hClW12Qb6Tvms+yMs77++F7LPCo6kEresPjSnoiWsm72kFRxR8x mBwe1BzTQDaEYA1isvtflwrTlaCYoehjpfEFEzxGyJzOszHotNYkGv7cMbjH46wwcevn ZgJ6Evgm1erO0k+iFoylKA6T/AVsBN9DxLT0CuV1LQSISJmRf8nAah0zhXsMXzwC3yDg LpcSdrHFXqoIHFPtgsrep+xH+ZTQ8E93E8Lsz9l6/zLGMOJm42wWZV85Ja792k0hj7NE wL+D/Q6QzBC93fVqkgs9P+7dbQaMdFi8pPeBVrRfWUn8UAvbPuXjzbiYckkL7rc7CAjX RyEA== MIME-Version: 1.0 Received: by 10.216.233.208 with SMTP id p58mr6202484weq.56.1347914063595; Mon, 17 Sep 2012 13:34:23 -0700 (PDT) Received: by 10.194.18.170 with HTTP; Mon, 17 Sep 2012 13:34:23 -0700 (PDT) Date: Tue, 18 Sep 2012 04:34:23 +0800 Message-ID: From: KC LO To: xen-users@lists.xensource.com Subject: [Xen-users] Existing Xen 3.4 work with OpenStack or CloudStack X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============5309962895243443140==" Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org --===============5309962895243443140== Content-Type: multipart/alternative; boundary=000e0cd517f4f2c82904c9ebb2de --000e0cd517f4f2c82904c9ebb2de Content-Type: text/plain; charset=ISO-8859-1 Dear all, We have a pool of servers running CentOS5+Xen3.4.4. Any suggested method to use OpenStack or CloudStack if I want to manage existing VM through a Cloud Mgt platform. I searched doc on OpenStack or CloudStack that they will work for registering new server and creating new VM and not to registered existing VM . Cheers! --000e0cd517f4f2c82904c9ebb2de Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Dear all,

We have a pool of servers running CentOS5+Xen3= .4.4. =A0Any suggested method to use OpenStack or CloudStack if I want to m= anage existing VM through a Cloud Mgt platform. =A0I searched doc on OpenSt= ack or CloudStack that they will work for registering new server and creati= ng new VM and not to registered existing VM .

Cheers!
--000e0cd517f4f2c82904c9ebb2de-- --===============5309962895243443140== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users --===============5309962895243443140==-- From xen-users-bounces@lists.xen.org Mon Sep 17 20:41:58 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Mon, 17 Sep 2012 20:41:58 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TDi7b-00083V-Uw; Mon, 17 Sep 2012 20:40:47 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TDi7Z-00083L-Mx for xen-users@lists.xen.org; Mon, 17 Sep 2012 20:40:45 +0000 Received: from [85.158.139.211:56046] by server-10.bemta-5.messagelabs.com id 61/99-10969-CCA87505; Mon, 17 Sep 2012 20:40:44 +0000 X-Env-Sender: dan@soleks.com X-Msg-Ref: server-4.tower-206.messagelabs.com!1347914441!18938401!1 X-Originating-IP: [199.175.126.195] X-SpamReason: No, hits=0.9 required=7.0 tests=HTML_10_20,HTML_MESSAGE X-StarScan-Received: X-StarScan-Version: 6.6.1.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 8664 invoked from network); 17 Sep 2012 20:40:42 -0000 Received: from smtp.soleks.com (HELO mail-smtp00.soleks.net) (199.175.126.195) by server-4.tower-206.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 17 Sep 2012 20:40:42 -0000 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=soleks.com; s=x; h=Content-Transfer-Encoding:Content-Type:MIME-Version:In-Reply-To:References:Subject:To:From:Date:Message-ID; bh=Y4bNbeOJk30oVTvNroCjMkKAZ8LDR1XNhHqEtqmAEUM=; b=rX1Oby0ZHLoqfx416dZEsjCtBjV6NUquQ+ImicQH2yExbdzHazugDV1GZcEWHWQIpP3gpMMrVZVx71ST+t+1ABE7kyf0uuujz91CmFKJ+lNkA/SjyKl0AJFiymACaf3b; Received: from localhost ([127.0.0.1]) by mail-smtp00.soleks.net with smtp (Exim 4.74) (envelope-from ) id 1TDj7G-0005ux-N2 for xen-users@lists.xen.org; Mon, 17 Sep 2012 14:44:30 -0700 Received: from mail-webmail00.soleks.net ([192.168.230.224] helo=webmail.soleks.net) by mail-smtp00.soleks.net with esmtpa (Exim 4.74) (envelope-from ) id 1TDj7A-0005ur-8p for xen-users@lists.xen.org; Mon, 17 Sep 2012 14:44:28 -0700 Received: from S010678cd8e7ac150.vf.shawcable.net (S010678cd8e7ac150.vf.shawcable.net [174.1.142.40]) by webmail.soleks.com (Horde Framework) with HTTP; Mon, 17 Sep 2012 14:34:28 -0700 Message-ID: <20120917143428.15851guj4mm04tq8@webmail.soleks.com> Date: Mon, 17 Sep 2012 14:34:28 -0700 From: dan@soleks.com To: xen-users@lists.xen.org References: In-Reply-To: MIME-Version: 1.0 User-Agent: Internet Messaging Program (IMP) H3 (4.3.9) X-GMS-IP-Reputation: 0 X-GMS-DCC-Result: A X-GMS-SpamScanned: a9ceb0cad40d3a94211ee78614a31c05 X-DSPAM-Result: Innocent X-DSPAM-Processed: Mon Sep 17 14:44:30 2012 X-DSPAM-Confidence: 0.9899 X-DSPAM-Probability: 0.0000 X-DSPAM-Signature: 438,505799be18372144413269 X-DSPAM-Factors: 27, of, 0.01000, of, 0.01000, IMP, 0.01000, IMP, 0.01000, was+sent+using, 0.01000, was+sent+using, 0.01000, Messaging+Program, 0.01000, Messaging+Program, 0.01000, sent+#+#+the, 0.01000, sent+#+#+the, 0.01000, using+#+the, 0.01000, using+#+the, 0.01000, sent+#+#+#+Internet, 0.01000, sent+#+#+#+Internet, 0.01000, This+#+was+sent, 0.01000, This+#+was+sent, 0.01000, sent+#+#+the+Internet, 0.01000, sent+#+#+the+Internet, 0.01000, message, 0.01000, message, 0.01000, was+sent+#+IMP, 0.01000, was+sent+#+IMP, 0.01000, IMP+the+#+Messaging, 0.01000, IMP+the+#+Messaging, 0.01000, was+sent, 0.01000, was+sent, 0.01000, was+#+using, 0.01000 X-GMS-SpamScore: 0 Subject: Re: [Xen-users] Existing Xen 3.4 work with OpenStack or CloudStack X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============2761675694465728676==" Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org This message is in MIME format. --===============2761675694465728676== Content-Type: multipart/alternative; boundary="=_8sc6fcouboso0k" Content-Transfer-Encoding: 7bit This message is in MIME format. --=_8sc6fcouboso0k Content-Type: text/plain; charset=ISO-8859-1 Content-Description: Plaintext Version of Message Content-Disposition: inline Content-Transfer-Encoding: 7bit As i know both openstack and cloudstack doesn't work with baremetal XEN, they require XAPI (Xen Cloud Platform or XenServer ). If you are targeting baremetal XEN i think you have only one option - Eucaliptus. > Dear all, > > We have a pool of servers running CentOS5+Xen3.4.4. Any suggested method > to use OpenStack or CloudStack if I want to manage existing VM through a > Cloud Mgt platform. I searched doc on OpenStack or CloudStack that they > will work for registering new server and creating new VM and not to > registered existing VM . > > Cheers! > ---------------------------------------------------------------- This message was sent using IMP, the Internet Messaging Program. --=_8sc6fcouboso0k Content-Type: text/html; charset=ISO-8859-1 Content-Description: HTML Version of Message Content-Disposition: inline Content-Transfer-Encoding: 7bit  As i know both openstack and cloudstack doesn't work with baremetal XEN, they require XAPI (Xen Cloud Platform or XenServer ). If you are targeting baremetal XEN i think you have only one option - Eucaliptus.
> Dear all,
>
> We have a pool of servers running CentOS5+Xen3.4.4.  Any suggested method
> to use OpenStack or CloudStack if I want to manage existing VM through a
> Cloud Mgt platform.  I searched doc on OpenStack or CloudStack that they
> will work for registering new server and creating new VM and not to
> registered existing VM .
>
> Cheers!
>


----------------------------------------------------------------
This message was sent using IMP, the Internet Messaging Program.
--=_8sc6fcouboso0k-- --===============2761675694465728676== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users --===============2761675694465728676==-- From xen-users-bounces@lists.xen.org Mon Sep 17 20:41:58 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Mon, 17 Sep 2012 20:41:58 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TDi7b-00083V-Uw; Mon, 17 Sep 2012 20:40:47 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TDi7Z-00083L-Mx for xen-users@lists.xen.org; Mon, 17 Sep 2012 20:40:45 +0000 Received: from [85.158.139.211:56046] by server-10.bemta-5.messagelabs.com id 61/99-10969-CCA87505; Mon, 17 Sep 2012 20:40:44 +0000 X-Env-Sender: dan@soleks.com X-Msg-Ref: server-4.tower-206.messagelabs.com!1347914441!18938401!1 X-Originating-IP: [199.175.126.195] X-SpamReason: No, hits=0.9 required=7.0 tests=HTML_10_20,HTML_MESSAGE X-StarScan-Received: X-StarScan-Version: 6.6.1.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 8664 invoked from network); 17 Sep 2012 20:40:42 -0000 Received: from smtp.soleks.com (HELO mail-smtp00.soleks.net) (199.175.126.195) by server-4.tower-206.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 17 Sep 2012 20:40:42 -0000 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=soleks.com; s=x; h=Content-Transfer-Encoding:Content-Type:MIME-Version:In-Reply-To:References:Subject:To:From:Date:Message-ID; bh=Y4bNbeOJk30oVTvNroCjMkKAZ8LDR1XNhHqEtqmAEUM=; b=rX1Oby0ZHLoqfx416dZEsjCtBjV6NUquQ+ImicQH2yExbdzHazugDV1GZcEWHWQIpP3gpMMrVZVx71ST+t+1ABE7kyf0uuujz91CmFKJ+lNkA/SjyKl0AJFiymACaf3b; Received: from localhost ([127.0.0.1]) by mail-smtp00.soleks.net with smtp (Exim 4.74) (envelope-from ) id 1TDj7G-0005ux-N2 for xen-users@lists.xen.org; Mon, 17 Sep 2012 14:44:30 -0700 Received: from mail-webmail00.soleks.net ([192.168.230.224] helo=webmail.soleks.net) by mail-smtp00.soleks.net with esmtpa (Exim 4.74) (envelope-from ) id 1TDj7A-0005ur-8p for xen-users@lists.xen.org; Mon, 17 Sep 2012 14:44:28 -0700 Received: from S010678cd8e7ac150.vf.shawcable.net (S010678cd8e7ac150.vf.shawcable.net [174.1.142.40]) by webmail.soleks.com (Horde Framework) with HTTP; Mon, 17 Sep 2012 14:34:28 -0700 Message-ID: <20120917143428.15851guj4mm04tq8@webmail.soleks.com> Date: Mon, 17 Sep 2012 14:34:28 -0700 From: dan@soleks.com To: xen-users@lists.xen.org References: In-Reply-To: MIME-Version: 1.0 User-Agent: Internet Messaging Program (IMP) H3 (4.3.9) X-GMS-IP-Reputation: 0 X-GMS-DCC-Result: A X-GMS-SpamScanned: a9ceb0cad40d3a94211ee78614a31c05 X-DSPAM-Result: Innocent X-DSPAM-Processed: Mon Sep 17 14:44:30 2012 X-DSPAM-Confidence: 0.9899 X-DSPAM-Probability: 0.0000 X-DSPAM-Signature: 438,505799be18372144413269 X-DSPAM-Factors: 27, of, 0.01000, of, 0.01000, IMP, 0.01000, IMP, 0.01000, was+sent+using, 0.01000, was+sent+using, 0.01000, Messaging+Program, 0.01000, Messaging+Program, 0.01000, sent+#+#+the, 0.01000, sent+#+#+the, 0.01000, using+#+the, 0.01000, using+#+the, 0.01000, sent+#+#+#+Internet, 0.01000, sent+#+#+#+Internet, 0.01000, This+#+was+sent, 0.01000, This+#+was+sent, 0.01000, sent+#+#+the+Internet, 0.01000, sent+#+#+the+Internet, 0.01000, message, 0.01000, message, 0.01000, was+sent+#+IMP, 0.01000, was+sent+#+IMP, 0.01000, IMP+the+#+Messaging, 0.01000, IMP+the+#+Messaging, 0.01000, was+sent, 0.01000, was+sent, 0.01000, was+#+using, 0.01000 X-GMS-SpamScore: 0 Subject: Re: [Xen-users] Existing Xen 3.4 work with OpenStack or CloudStack X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============2761675694465728676==" Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org This message is in MIME format. --===============2761675694465728676== Content-Type: multipart/alternative; boundary="=_8sc6fcouboso0k" Content-Transfer-Encoding: 7bit This message is in MIME format. --=_8sc6fcouboso0k Content-Type: text/plain; charset=ISO-8859-1 Content-Description: Plaintext Version of Message Content-Disposition: inline Content-Transfer-Encoding: 7bit As i know both openstack and cloudstack doesn't work with baremetal XEN, they require XAPI (Xen Cloud Platform or XenServer ). If you are targeting baremetal XEN i think you have only one option - Eucaliptus. > Dear all, > > We have a pool of servers running CentOS5+Xen3.4.4. Any suggested method > to use OpenStack or CloudStack if I want to manage existing VM through a > Cloud Mgt platform. I searched doc on OpenStack or CloudStack that they > will work for registering new server and creating new VM and not to > registered existing VM . > > Cheers! > ---------------------------------------------------------------- This message was sent using IMP, the Internet Messaging Program. --=_8sc6fcouboso0k Content-Type: text/html; charset=ISO-8859-1 Content-Description: HTML Version of Message Content-Disposition: inline Content-Transfer-Encoding: 7bit  As i know both openstack and cloudstack doesn't work with baremetal XEN, they require XAPI (Xen Cloud Platform or XenServer ). If you are targeting baremetal XEN i think you have only one option - Eucaliptus.
> Dear all,
>
> We have a pool of servers running CentOS5+Xen3.4.4.  Any suggested method
> to use OpenStack or CloudStack if I want to manage existing VM through a
> Cloud Mgt platform.  I searched doc on OpenStack or CloudStack that they
> will work for registering new server and creating new VM and not to
> registered existing VM .
>
> Cheers!
>


----------------------------------------------------------------
This message was sent using IMP, the Internet Messaging Program.
--=_8sc6fcouboso0k-- --===============2761675694465728676== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users --===============2761675694465728676==-- From xen-users-bounces@lists.xen.org Tue Sep 18 01:24:02 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Tue, 18 Sep 2012 01:24:02 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TDmWL-0001Gi-55; Tue, 18 Sep 2012 01:22:37 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TDmWK-0001Gc-D7 for xen-users@lists.xensource.com; Tue, 18 Sep 2012 01:22:36 +0000 Received: from [85.158.143.35:19718] by server-3.bemta-4.messagelabs.com id 69/42-08232-BDCC7505; Tue, 18 Sep 2012 01:22:35 +0000 X-Env-Sender: pingh.cd@gmail.com X-Msg-Ref: server-14.tower-21.messagelabs.com!1347931353!18746583!1 X-Originating-IP: [216.139.236.26] X-SpamReason: No, hits=0.0 required=7.0 tests=ML_RADAR_SPEW_LINKS_14, spamassassin: X-StarScan-Received: X-StarScan-Version: 6.6.1.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 9272 invoked from network); 18 Sep 2012 01:22:34 -0000 Received: from sam.nabble.com (HELO sam.nabble.com) (216.139.236.26) by server-14.tower-21.messagelabs.com with AES256-SHA encrypted SMTP; 18 Sep 2012 01:22:34 -0000 Received: from [192.168.236.26] (helo=sam.nabble.com) by sam.nabble.com with esmtp (Exim 4.72) (envelope-from ) id 1TDmWG-0000ho-A8 for xen-users@lists.xensource.com; Mon, 17 Sep 2012 18:22:32 -0700 Date: Mon, 17 Sep 2012 18:22:32 -0700 (PDT) From: Robin hp To: xen-users@lists.xensource.com Message-ID: <1347931352294-5711338.post@n5.nabble.com> In-Reply-To: References: <1347851542961-5711309.post@n5.nabble.com> MIME-Version: 1.0 Subject: Re: [Xen-users] Performance of PVM and HVM X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org >Are you sure? setting native parameters can be tricky. I used a simple method, just keep one 4G RAM in the Computer for the native test, and I have just one cpu with 4 cores. So, I did this test in the same conditions. > I didn't use phy:/ for hvm, but I used file:/ for pvm, and the results > were > not different. >meaning what? you've retested with phy? if not, you should. I mean that I used file:/ and phy:/ for pvm, not used phy:/ for hvm. But I will try that later and post the result. >dd is almost useless for benchmarking purposes. >Personally I'd say use real workloads. For example, in the past I was >choosing the best virtualization platform to run mysql. So I used >sysbench on vmware, kvm, and xen. The end result was almost the same, >so I ended up choosing vmware for that project because it was easier >to maintain. You are right, I tried to use fio for the r/w testing, but still have no result. >It depends. >64bit pv have some performance penalty for some syscalls which does >not exist in 32bit pv or hvm (search the list archive for details). In >some cases this doesn't matter, and other pv-guest benefits more than >compensate for this penalty. I heard about this before, and I installed a 32-bit pvm, but nothing was changed. Maybe it's because my host was 64-bit system. >There's an ongoing effort to create hybrid guest to address this >issue, but it's not ready yet. >Again, at this point I suggest you: >- use phy >- use a benchmark similar to the workload you're going to use >... and if you have time, try kvm as well :) I have tested kvm, and the score of unixbenck of kvm was so close to that of pvm. -- -- View this message in context: http://xen.1045712.n5.nabble.com/Performance-of-PVM-and-HVM-tp5711309p5711338.html Sent from the Xen - User mailing list archive at Nabble.com. _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Tue Sep 18 01:24:02 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Tue, 18 Sep 2012 01:24:02 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TDmWL-0001Gi-55; Tue, 18 Sep 2012 01:22:37 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TDmWK-0001Gc-D7 for xen-users@lists.xensource.com; Tue, 18 Sep 2012 01:22:36 +0000 Received: from [85.158.143.35:19718] by server-3.bemta-4.messagelabs.com id 69/42-08232-BDCC7505; Tue, 18 Sep 2012 01:22:35 +0000 X-Env-Sender: pingh.cd@gmail.com X-Msg-Ref: server-14.tower-21.messagelabs.com!1347931353!18746583!1 X-Originating-IP: [216.139.236.26] X-SpamReason: No, hits=0.0 required=7.0 tests=ML_RADAR_SPEW_LINKS_14, spamassassin: X-StarScan-Received: X-StarScan-Version: 6.6.1.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 9272 invoked from network); 18 Sep 2012 01:22:34 -0000 Received: from sam.nabble.com (HELO sam.nabble.com) (216.139.236.26) by server-14.tower-21.messagelabs.com with AES256-SHA encrypted SMTP; 18 Sep 2012 01:22:34 -0000 Received: from [192.168.236.26] (helo=sam.nabble.com) by sam.nabble.com with esmtp (Exim 4.72) (envelope-from ) id 1TDmWG-0000ho-A8 for xen-users@lists.xensource.com; Mon, 17 Sep 2012 18:22:32 -0700 Date: Mon, 17 Sep 2012 18:22:32 -0700 (PDT) From: Robin hp To: xen-users@lists.xensource.com Message-ID: <1347931352294-5711338.post@n5.nabble.com> In-Reply-To: References: <1347851542961-5711309.post@n5.nabble.com> MIME-Version: 1.0 Subject: Re: [Xen-users] Performance of PVM and HVM X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org >Are you sure? setting native parameters can be tricky. I used a simple method, just keep one 4G RAM in the Computer for the native test, and I have just one cpu with 4 cores. So, I did this test in the same conditions. > I didn't use phy:/ for hvm, but I used file:/ for pvm, and the results > were > not different. >meaning what? you've retested with phy? if not, you should. I mean that I used file:/ and phy:/ for pvm, not used phy:/ for hvm. But I will try that later and post the result. >dd is almost useless for benchmarking purposes. >Personally I'd say use real workloads. For example, in the past I was >choosing the best virtualization platform to run mysql. So I used >sysbench on vmware, kvm, and xen. The end result was almost the same, >so I ended up choosing vmware for that project because it was easier >to maintain. You are right, I tried to use fio for the r/w testing, but still have no result. >It depends. >64bit pv have some performance penalty for some syscalls which does >not exist in 32bit pv or hvm (search the list archive for details). In >some cases this doesn't matter, and other pv-guest benefits more than >compensate for this penalty. I heard about this before, and I installed a 32-bit pvm, but nothing was changed. Maybe it's because my host was 64-bit system. >There's an ongoing effort to create hybrid guest to address this >issue, but it's not ready yet. >Again, at this point I suggest you: >- use phy >- use a benchmark similar to the workload you're going to use >... and if you have time, try kvm as well :) I have tested kvm, and the score of unixbenck of kvm was so close to that of pvm. -- -- View this message in context: http://xen.1045712.n5.nabble.com/Performance-of-PVM-and-HVM-tp5711309p5711338.html Sent from the Xen - User mailing list archive at Nabble.com. _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Tue Sep 18 01:25:37 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Tue, 18 Sep 2012 01:25:37 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TDmY2-0001Lo-UF; Tue, 18 Sep 2012 01:24:22 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TDmY1-0001Le-N9 for xen-users@lists.xensource.com; Tue, 18 Sep 2012 01:24:21 +0000 Received: from [85.158.139.211:5880] by server-7.bemta-5.messagelabs.com id BC/BD-19703-44DC7505; Tue, 18 Sep 2012 01:24:20 +0000 X-Env-Sender: pingh.cd@gmail.com X-Msg-Ref: server-13.tower-206.messagelabs.com!1347931459!14948855!1 X-Originating-IP: [216.139.236.26] X-SpamReason: No, hits=0.0 required=7.0 tests=ML_RADAR_SPEW_LINKS_14, spamassassin: X-StarScan-Received: X-StarScan-Version: 6.6.1.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 13815 invoked from network); 18 Sep 2012 01:24:20 -0000 Received: from sam.nabble.com (HELO sam.nabble.com) (216.139.236.26) by server-13.tower-206.messagelabs.com with AES256-SHA encrypted SMTP; 18 Sep 2012 01:24:20 -0000 Received: from [192.168.236.26] (helo=sam.nabble.com) by sam.nabble.com with esmtp (Exim 4.72) (envelope-from ) id 1TDmXy-0000vR-GI for xen-users@lists.xensource.com; Mon, 17 Sep 2012 18:24:18 -0700 Date: Mon, 17 Sep 2012 18:24:18 -0700 (PDT) From: Robin hp To: xen-users@lists.xensource.com Message-ID: <1347931458498-5711339.post@n5.nabble.com> In-Reply-To: References: MIME-Version: 1.0 Subject: Re: [Xen-users] Existing Xen 3.4 work with OpenStack or CloudStack X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org KC LO wrote > > Dear all, > > We have a pool of servers running CentOS5+Xen3.4.4. Any suggested method > to use OpenStack or CloudStack if I want to manage existing VM through a > Cloud Mgt platform. I searched doc on OpenStack or CloudStack that they > will work for registering new server and creating new VM and not to > registered existing VM . > > Cheers! > convirture could be a good choice. -- View this message in context: http://xen.1045712.n5.nabble.com/Existing-Xen-3-4-work-with-OpenStack-or-CloudStack-tp5711328p5711339.html Sent from the Xen - User mailing list archive at Nabble.com. _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Tue Sep 18 01:25:37 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Tue, 18 Sep 2012 01:25:37 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TDmY2-0001Lo-UF; Tue, 18 Sep 2012 01:24:22 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TDmY1-0001Le-N9 for xen-users@lists.xensource.com; Tue, 18 Sep 2012 01:24:21 +0000 Received: from [85.158.139.211:5880] by server-7.bemta-5.messagelabs.com id BC/BD-19703-44DC7505; Tue, 18 Sep 2012 01:24:20 +0000 X-Env-Sender: pingh.cd@gmail.com X-Msg-Ref: server-13.tower-206.messagelabs.com!1347931459!14948855!1 X-Originating-IP: [216.139.236.26] X-SpamReason: No, hits=0.0 required=7.0 tests=ML_RADAR_SPEW_LINKS_14, spamassassin: X-StarScan-Received: X-StarScan-Version: 6.6.1.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 13815 invoked from network); 18 Sep 2012 01:24:20 -0000 Received: from sam.nabble.com (HELO sam.nabble.com) (216.139.236.26) by server-13.tower-206.messagelabs.com with AES256-SHA encrypted SMTP; 18 Sep 2012 01:24:20 -0000 Received: from [192.168.236.26] (helo=sam.nabble.com) by sam.nabble.com with esmtp (Exim 4.72) (envelope-from ) id 1TDmXy-0000vR-GI for xen-users@lists.xensource.com; Mon, 17 Sep 2012 18:24:18 -0700 Date: Mon, 17 Sep 2012 18:24:18 -0700 (PDT) From: Robin hp To: xen-users@lists.xensource.com Message-ID: <1347931458498-5711339.post@n5.nabble.com> In-Reply-To: References: MIME-Version: 1.0 Subject: Re: [Xen-users] Existing Xen 3.4 work with OpenStack or CloudStack X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org KC LO wrote > > Dear all, > > We have a pool of servers running CentOS5+Xen3.4.4. Any suggested method > to use OpenStack or CloudStack if I want to manage existing VM through a > Cloud Mgt platform. I searched doc on OpenStack or CloudStack that they > will work for registering new server and creating new VM and not to > registered existing VM . > > Cheers! > convirture could be a good choice. -- View this message in context: http://xen.1045712.n5.nabble.com/Existing-Xen-3-4-work-with-OpenStack-or-CloudStack-tp5711328p5711339.html Sent from the Xen - User mailing list archive at Nabble.com. _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Tue Sep 18 06:23:42 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Tue, 18 Sep 2012 06:23:42 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TDrCU-00040y-C2; Tue, 18 Sep 2012 06:22:26 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TDrCS-00040t-NM for xen-users@lists.xen.org; Tue, 18 Sep 2012 06:22:24 +0000 Received: from [85.158.143.35:6706] by server-1.bemta-4.messagelabs.com id 78/A5-12504-F1318505; Tue, 18 Sep 2012 06:22:23 +0000 X-Env-Sender: murali.rajam@gmail.com X-Msg-Ref: server-3.tower-21.messagelabs.com!1347949342!14131241!1 X-Originating-IP: [209.85.210.173] X-SpamReason: No, hits=0.3 required=7.0 tests=ML_RADAR_SPEW_LINKS_14, RCVD_BY_IP,spamassassin: X-StarScan-Received: X-StarScan-Version: 6.6.1.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 4130 invoked from network); 18 Sep 2012 06:22:23 -0000 Received: from mail-iy0-f173.google.com (HELO mail-iy0-f173.google.com) (209.85.210.173) by server-3.tower-21.messagelabs.com with RC4-SHA encrypted SMTP; 18 Sep 2012 06:22:23 -0000 Received: by iakx26 with SMTP id x26so7319576iak.32 for ; Mon, 17 Sep 2012 23:22:21 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:date:message-id:subject:from:to:content-type; bh=mA3qGQOt622os9gzKFgKKweq/DSIVjCxJPlNcRFrsYg=; b=kWu7Ogc3bv26XpWzyd3hGO8mhc3d4gIwqPWht0I/URywhiVlAqmi6tIeaHv+S4rF1B DiLpqoZMIEjBdSBObgQkhscZa7qKup85IGYICZvk8DZOUe3a05+5H01IFk1hrWGxPmww UFSZUa27pAFobuDwyJ0KcYHDmJVIVv5AME/7a7fglNxVp/D0lrO5AUM9+Y17YuMVtnjm 2o7EMnR4NCPD+PRzn98B3Czju5lSl5F7IAL2Eu3OsryzO0Ft35SmU7q3S1sB7Nv3r+tu oFKw/QvsX9rgUywS/yKL2cYyNGqCLkKdf1JlRV64wXda7Cn5qHWqmkT9T306BOoi+BIx zZgw== MIME-Version: 1.0 Received: by 10.50.159.201 with SMTP id xe9mr9437682igb.63.1347949341668; Mon, 17 Sep 2012 23:22:21 -0700 (PDT) Received: by 10.64.70.69 with HTTP; Mon, 17 Sep 2012 23:22:21 -0700 (PDT) Date: Mon, 17 Sep 2012 23:22:21 -0700 Message-ID: From: Murali raja Muniraju To: xen-users@lists.xen.org Subject: [Xen-users] Query regarding striped logical volume X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org Hi All, I am trying to create a striped logical volume and would like to import a vm on the striped logical volume. How do I specify during xe vm-import, to use the created logical volume as the VM's disk. Currently xe vm-import only takes sr-uuid as a argument. -- __MURALI__ _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Tue Sep 18 06:23:42 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Tue, 18 Sep 2012 06:23:42 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TDrCU-00040y-C2; Tue, 18 Sep 2012 06:22:26 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TDrCS-00040t-NM for xen-users@lists.xen.org; Tue, 18 Sep 2012 06:22:24 +0000 Received: from [85.158.143.35:6706] by server-1.bemta-4.messagelabs.com id 78/A5-12504-F1318505; Tue, 18 Sep 2012 06:22:23 +0000 X-Env-Sender: murali.rajam@gmail.com X-Msg-Ref: server-3.tower-21.messagelabs.com!1347949342!14131241!1 X-Originating-IP: [209.85.210.173] X-SpamReason: No, hits=0.3 required=7.0 tests=ML_RADAR_SPEW_LINKS_14, RCVD_BY_IP,spamassassin: X-StarScan-Received: X-StarScan-Version: 6.6.1.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 4130 invoked from network); 18 Sep 2012 06:22:23 -0000 Received: from mail-iy0-f173.google.com (HELO mail-iy0-f173.google.com) (209.85.210.173) by server-3.tower-21.messagelabs.com with RC4-SHA encrypted SMTP; 18 Sep 2012 06:22:23 -0000 Received: by iakx26 with SMTP id x26so7319576iak.32 for ; Mon, 17 Sep 2012 23:22:21 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:date:message-id:subject:from:to:content-type; bh=mA3qGQOt622os9gzKFgKKweq/DSIVjCxJPlNcRFrsYg=; b=kWu7Ogc3bv26XpWzyd3hGO8mhc3d4gIwqPWht0I/URywhiVlAqmi6tIeaHv+S4rF1B DiLpqoZMIEjBdSBObgQkhscZa7qKup85IGYICZvk8DZOUe3a05+5H01IFk1hrWGxPmww UFSZUa27pAFobuDwyJ0KcYHDmJVIVv5AME/7a7fglNxVp/D0lrO5AUM9+Y17YuMVtnjm 2o7EMnR4NCPD+PRzn98B3Czju5lSl5F7IAL2Eu3OsryzO0Ft35SmU7q3S1sB7Nv3r+tu oFKw/QvsX9rgUywS/yKL2cYyNGqCLkKdf1JlRV64wXda7Cn5qHWqmkT9T306BOoi+BIx zZgw== MIME-Version: 1.0 Received: by 10.50.159.201 with SMTP id xe9mr9437682igb.63.1347949341668; Mon, 17 Sep 2012 23:22:21 -0700 (PDT) Received: by 10.64.70.69 with HTTP; Mon, 17 Sep 2012 23:22:21 -0700 (PDT) Date: Mon, 17 Sep 2012 23:22:21 -0700 Message-ID: From: Murali raja Muniraju To: xen-users@lists.xen.org Subject: [Xen-users] Query regarding striped logical volume X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org Hi All, I am trying to create a striped logical volume and would like to import a vm on the striped logical volume. How do I specify during xe vm-import, to use the created logical volume as the VM's disk. Currently xe vm-import only takes sr-uuid as a argument. -- __MURALI__ _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Tue Sep 18 07:45:27 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Tue, 18 Sep 2012 07:45:27 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TDsTt-0006IQ-BX; Tue, 18 Sep 2012 07:44:29 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TDsTr-0006I1-NN for xen-users@lists.xen.org; Tue, 18 Sep 2012 07:44:27 +0000 Received: from [85.158.139.211:13716] by server-1.bemta-5.messagelabs.com id 66/E9-32692-A5628505; Tue, 18 Sep 2012 07:44:26 +0000 X-Env-Sender: Ian.Campbell@citrix.com X-Msg-Ref: server-6.tower-206.messagelabs.com!1347954265!18976194!1 X-Originating-IP: [62.200.22.115] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogNjIuMjAwLjIyLjExNSA9PiAxMDk2NzI=\n X-StarScan-Received: X-StarScan-Version: 6.6.1.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 31114 invoked from network); 18 Sep 2012 07:44:25 -0000 Received: from smtp.ctxuk.citrix.com (HELO SMTP.EU.CITRIX.COM) (62.200.22.115) by server-6.tower-206.messagelabs.com with RC4-SHA encrypted SMTP; 18 Sep 2012 07:44:25 -0000 X-IronPort-AV: E=Sophos;i="4.80,441,1344211200"; d="scan'208";a="14596696" Received: from lonpmailmx01.citrite.net ([10.30.203.162]) by LONPIPO01.EU.CITRIX.COM with ESMTP/TLS/RC4-MD5; 18 Sep 2012 07:44:25 +0000 Received: from [127.0.0.1] (10.80.16.67) by smtprelay.citrix.com (10.30.203.162) with Microsoft SMTP Server id 8.3.279.1; Tue, 18 Sep 2012 08:44:25 +0100 Message-ID: <1347954264.25803.93.camel@dagon.hellion.org.uk> From: Ian Campbell To: Murali raja Muniraju Date: Tue, 18 Sep 2012 08:44:24 +0100 In-Reply-To: References: Organization: Citrix Systems, Inc. X-Mailer: Evolution 3.4.3-1 MIME-Version: 1.0 Cc: "xen-users@lists.xen.org" , xen-api@lists.xen.org Subject: Re: [Xen-users] Query regarding striped logical volume X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org Hi Murali, Questions about XCP are better addressed to the (badly named) xen-api@list. I've CCd it for you now. On Tue, 2012-09-18 at 07:22 +0100, Murali raja Muniraju wrote: > Hi All, > I am trying to create a striped logical volume and would like to > import a vm on the striped logical volume. How do I specify during xe > vm-import, to use the created logical volume as the VM's disk. > Currently xe vm-import only takes sr-uuid as a argument. > _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Tue Sep 18 07:45:27 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Tue, 18 Sep 2012 07:45:27 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TDsTt-0006IQ-BX; Tue, 18 Sep 2012 07:44:29 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TDsTr-0006I1-NN for xen-users@lists.xen.org; Tue, 18 Sep 2012 07:44:27 +0000 Received: from [85.158.139.211:13716] by server-1.bemta-5.messagelabs.com id 66/E9-32692-A5628505; Tue, 18 Sep 2012 07:44:26 +0000 X-Env-Sender: Ian.Campbell@citrix.com X-Msg-Ref: server-6.tower-206.messagelabs.com!1347954265!18976194!1 X-Originating-IP: [62.200.22.115] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogNjIuMjAwLjIyLjExNSA9PiAxMDk2NzI=\n X-StarScan-Received: X-StarScan-Version: 6.6.1.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 31114 invoked from network); 18 Sep 2012 07:44:25 -0000 Received: from smtp.ctxuk.citrix.com (HELO SMTP.EU.CITRIX.COM) (62.200.22.115) by server-6.tower-206.messagelabs.com with RC4-SHA encrypted SMTP; 18 Sep 2012 07:44:25 -0000 X-IronPort-AV: E=Sophos;i="4.80,441,1344211200"; d="scan'208";a="14596696" Received: from lonpmailmx01.citrite.net ([10.30.203.162]) by LONPIPO01.EU.CITRIX.COM with ESMTP/TLS/RC4-MD5; 18 Sep 2012 07:44:25 +0000 Received: from [127.0.0.1] (10.80.16.67) by smtprelay.citrix.com (10.30.203.162) with Microsoft SMTP Server id 8.3.279.1; Tue, 18 Sep 2012 08:44:25 +0100 Message-ID: <1347954264.25803.93.camel@dagon.hellion.org.uk> From: Ian Campbell To: Murali raja Muniraju Date: Tue, 18 Sep 2012 08:44:24 +0100 In-Reply-To: References: Organization: Citrix Systems, Inc. X-Mailer: Evolution 3.4.3-1 MIME-Version: 1.0 Cc: "xen-users@lists.xen.org" , xen-api@lists.xen.org Subject: Re: [Xen-users] Query regarding striped logical volume X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org Hi Murali, Questions about XCP are better addressed to the (badly named) xen-api@list. I've CCd it for you now. On Tue, 2012-09-18 at 07:22 +0100, Murali raja Muniraju wrote: > Hi All, > I am trying to create a striped logical volume and would like to > import a vm on the striped logical volume. How do I specify during xe > vm-import, to use the created logical volume as the VM's disk. > Currently xe vm-import only takes sr-uuid as a argument. > _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Tue Sep 18 12:12:51 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Tue, 18 Sep 2012 12:12:51 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TDwdo-00039q-Km; Tue, 18 Sep 2012 12:11:00 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TDu8c-0000RW-68 for xen-users@lists.xen.org; Tue, 18 Sep 2012 09:30:38 +0000 Received: from [85.158.139.83:34607] by server-6.bemta-5.messagelabs.com id 39/B6-21336-D3F38505; Tue, 18 Sep 2012 09:30:37 +0000 X-Env-Sender: Chris.Moseley@Senior.co.uk X-Msg-Ref: server-10.tower-182.messagelabs.com!1347960635!31281814!1 X-Originating-IP: [217.36.58.162] X-SpamReason: No, hits=0.0 required=7.0 tests=HTML_MESSAGE X-StarScan-Received: X-StarScan-Version: 6.6.1.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 19938 invoked from network); 18 Sep 2012 09:30:36 -0000 Received: from hqmail2.senior.co.uk (HELO hqmail.senior.co.uk) (217.36.58.162) by server-10.tower-182.messagelabs.com with AES128-SHA encrypted SMTP; 18 Sep 2012 09:30:36 -0000 Received: from SNR-GS1-MAIL1.senior.co.uk ([fe80::1b1:d6cf:3e47:fdc1]) by SNR-GS1-MAIL1.senior.co.uk ([fe80::1b1:d6cf:3e47:fdc1%10]) with mapi id 14.01.0355.002; Tue, 18 Sep 2012 10:30:34 +0100 From: Chris Moseley To: "xen-users@lists.xen.org" Thread-Topic: Virtual web servers losing connection to virtual database servers Thread-Index: Ac2VgClWpL1sjMWDRXmfIGzxEUhDbA== Date: Tue, 18 Sep 2012 09:30:33 +0000 Message-ID: <3EEC64C357EE854C8F1B8A9A94AD7137D9913D@SNR-GS1-MAIL1.senior.co.uk> Accept-Language: en-GB, en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [192.168.80.82] x-pmwin-version: 3.1.0.0, Antivirus-Engine: 3.35.1, Antivirus-Data: 4.81G MIME-Version: 1.0 X-Mailman-Approved-At: Tue, 18 Sep 2012 12:11:00 +0000 Subject: [Xen-users] Virtual web servers losing connection to virtual database servers X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============6676072918538908124==" Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org --===============6676072918538908124== Content-Language: en-US Content-Type: multipart/alternative; boundary="_000_3EEC64C357EE854C8F1B8A9A94AD7137D9913DSNRGS1MAIL1senior_" --_000_3EEC64C357EE854C8F1B8A9A94AD7137D9913DSNRGS1MAIL1senior_ Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Apologies if I've posted this to the wrong list or anything. We host websites on virtual servers over Xen. Over the last few weeks we ha= ve experienced several service outages with our web servers losing connecti= on to the database servers at seemingly random intervals (can happen in the= middle of the night, or during peak hours). connectivity between the serve= rs is restored immediately if we RD on to the web server, browse to the DB = server in windows explorer (via its local network IP) and then enter authen= tication details in access prompt. The web servers are all Windows, the DB servers are both Windows (MSSQL) an= d Linux (MySQl). The errors that the sites produce during the problem are either: "A network-related or instance-specific error occurred while establishing a= connection to SQL Server. The server was not found or was not accessible. = Verify that the instance name is correct and that SQL Server is configured = to allow remote connections. (provider: Named Pipes Provider, error: 40 - C= ould not open a connection to SQL Server)" Or "System.InvalidOperationException: Timeout expired. The timeout period elap= sed prior to obtaining a connection from the pool. This may have occurred b= ecause all pooled connections were in use and max pool size was reached." Could anyone offer any advice on this or point me in a particular direction= ? Thanks. Chris Moseley --_000_3EEC64C357EE854C8F1B8A9A94AD7137D9913DSNRGS1MAIL1senior_ Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable

Apologies if I’ve posted this to the wrong lis= t or anything.

 

We host websites on virtual servers over Xen. Over t= he last few weeks we have experienced several service outages with our web = servers losing connection to the database servers at seemingly random intervals (can happen in the middle of the night, or during peak ho= urs). connectivity between the servers is restored immediately if we RD on = to the web server, browse to the DB server in windows explorer (via its loc= al network IP) and then enter authentication details in access prompt.

The web servers are all Windows, the DB servers are = both Windows (MSSQL) and Linux (MySQl).

The errors that the sites produce during the problem= are either:

"A network-related or instance-specific error o= ccurred while establishing a connection to SQL Server. The server was not f= ound or was not accessible. Verify that the instance name is correct and that SQL Server is configured to allow remote connections. (pr= ovider: Named Pipes Provider, error: 40 - Could not open a connection to SQ= L Server)"

Or

"System.InvalidOperationException: Timeout expi= red. The timeout period elapsed prior to obtaining a connection from the po= ol. This may have occurred because all pooled connections were in use and max pool size was reached."

Could anyone offer any advice on this or point me in= a particular direction? Thanks.

Chris Mo= seley

 

--_000_3EEC64C357EE854C8F1B8A9A94AD7137D9913DSNRGS1MAIL1senior_-- --===============6676072918538908124== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users --===============6676072918538908124==-- From xen-users-bounces@lists.xen.org Tue Sep 18 12:12:51 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Tue, 18 Sep 2012 12:12:51 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TDwdo-00039q-Km; Tue, 18 Sep 2012 12:11:00 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TDu8c-0000RW-68 for xen-users@lists.xen.org; Tue, 18 Sep 2012 09:30:38 +0000 Received: from [85.158.139.83:34607] by server-6.bemta-5.messagelabs.com id 39/B6-21336-D3F38505; Tue, 18 Sep 2012 09:30:37 +0000 X-Env-Sender: Chris.Moseley@Senior.co.uk X-Msg-Ref: server-10.tower-182.messagelabs.com!1347960635!31281814!1 X-Originating-IP: [217.36.58.162] X-SpamReason: No, hits=0.0 required=7.0 tests=HTML_MESSAGE X-StarScan-Received: X-StarScan-Version: 6.6.1.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 19938 invoked from network); 18 Sep 2012 09:30:36 -0000 Received: from hqmail2.senior.co.uk (HELO hqmail.senior.co.uk) (217.36.58.162) by server-10.tower-182.messagelabs.com with AES128-SHA encrypted SMTP; 18 Sep 2012 09:30:36 -0000 Received: from SNR-GS1-MAIL1.senior.co.uk ([fe80::1b1:d6cf:3e47:fdc1]) by SNR-GS1-MAIL1.senior.co.uk ([fe80::1b1:d6cf:3e47:fdc1%10]) with mapi id 14.01.0355.002; Tue, 18 Sep 2012 10:30:34 +0100 From: Chris Moseley To: "xen-users@lists.xen.org" Thread-Topic: Virtual web servers losing connection to virtual database servers Thread-Index: Ac2VgClWpL1sjMWDRXmfIGzxEUhDbA== Date: Tue, 18 Sep 2012 09:30:33 +0000 Message-ID: <3EEC64C357EE854C8F1B8A9A94AD7137D9913D@SNR-GS1-MAIL1.senior.co.uk> Accept-Language: en-GB, en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [192.168.80.82] x-pmwin-version: 3.1.0.0, Antivirus-Engine: 3.35.1, Antivirus-Data: 4.81G MIME-Version: 1.0 X-Mailman-Approved-At: Tue, 18 Sep 2012 12:11:00 +0000 Subject: [Xen-users] Virtual web servers losing connection to virtual database servers X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============6676072918538908124==" Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org --===============6676072918538908124== Content-Language: en-US Content-Type: multipart/alternative; boundary="_000_3EEC64C357EE854C8F1B8A9A94AD7137D9913DSNRGS1MAIL1senior_" --_000_3EEC64C357EE854C8F1B8A9A94AD7137D9913DSNRGS1MAIL1senior_ Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Apologies if I've posted this to the wrong list or anything. We host websites on virtual servers over Xen. Over the last few weeks we ha= ve experienced several service outages with our web servers losing connecti= on to the database servers at seemingly random intervals (can happen in the= middle of the night, or during peak hours). connectivity between the serve= rs is restored immediately if we RD on to the web server, browse to the DB = server in windows explorer (via its local network IP) and then enter authen= tication details in access prompt. The web servers are all Windows, the DB servers are both Windows (MSSQL) an= d Linux (MySQl). The errors that the sites produce during the problem are either: "A network-related or instance-specific error occurred while establishing a= connection to SQL Server. The server was not found or was not accessible. = Verify that the instance name is correct and that SQL Server is configured = to allow remote connections. (provider: Named Pipes Provider, error: 40 - C= ould not open a connection to SQL Server)" Or "System.InvalidOperationException: Timeout expired. The timeout period elap= sed prior to obtaining a connection from the pool. This may have occurred b= ecause all pooled connections were in use and max pool size was reached." Could anyone offer any advice on this or point me in a particular direction= ? Thanks. Chris Moseley --_000_3EEC64C357EE854C8F1B8A9A94AD7137D9913DSNRGS1MAIL1senior_ Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable

Apologies if I’ve posted this to the wrong lis= t or anything.

 

We host websites on virtual servers over Xen. Over t= he last few weeks we have experienced several service outages with our web = servers losing connection to the database servers at seemingly random intervals (can happen in the middle of the night, or during peak ho= urs). connectivity between the servers is restored immediately if we RD on = to the web server, browse to the DB server in windows explorer (via its loc= al network IP) and then enter authentication details in access prompt.

The web servers are all Windows, the DB servers are = both Windows (MSSQL) and Linux (MySQl).

The errors that the sites produce during the problem= are either:

"A network-related or instance-specific error o= ccurred while establishing a connection to SQL Server. The server was not f= ound or was not accessible. Verify that the instance name is correct and that SQL Server is configured to allow remote connections. (pr= ovider: Named Pipes Provider, error: 40 - Could not open a connection to SQ= L Server)"

Or

"System.InvalidOperationException: Timeout expi= red. The timeout period elapsed prior to obtaining a connection from the po= ol. This may have occurred because all pooled connections were in use and max pool size was reached."

Could anyone offer any advice on this or point me in= a particular direction? Thanks.

Chris Mo= seley

 

--_000_3EEC64C357EE854C8F1B8A9A94AD7137D9913DSNRGS1MAIL1senior_-- --===============6676072918538908124== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users --===============6676072918538908124==-- From xen-users-bounces@lists.xen.org Tue Sep 18 12:26:27 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Tue, 18 Sep 2012 12:26:27 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TDwrA-0003Ua-7R; Tue, 18 Sep 2012 12:24:48 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TDwr9-0003UU-3h for xen-users@lists.xen.org; Tue, 18 Sep 2012 12:24:47 +0000 Received: from [85.158.143.99:60274] by server-1.bemta-4.messagelabs.com id 7A/65-12504-E0868505; Tue, 18 Sep 2012 12:24:46 +0000 X-Env-Sender: mailinglists@websitemanagers.com.au X-Msg-Ref: server-4.tower-216.messagelabs.com!1347971082!25534362!1 X-Originating-IP: [203.56.191.70] X-SpamReason: No, hits=0.0 required=7.0 tests= X-StarScan-Received: X-StarScan-Version: 6.6.1.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 13982 invoked from network); 18 Sep 2012 12:24:45 -0000 Received: from unknown (HELO hammer.websitemanagers.com.au) (203.56.191.70) by server-4.tower-216.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 18 Sep 2012 12:24:45 -0000 Received: (qmail 6780 invoked by uid 1011); 18 Sep 2012 12:24:11 -0000 Received: from 220.233.87.52 by hammer (envelope-from , uid 1008) with qmail-scanner-1.24 (clamdscan: 0.97.3/15367. spamassassin: 3.3.1. Clear:RC:1(220.233.87.52):. Processed in 0.054554 secs); 18 Sep 2012 12:24:11 -0000 Received: from unknown (HELO ?192.168.2.90?) (220.233.87.52) by 0 with SMTP; 18 Sep 2012 12:24:11 -0000 Message-ID: <505867EA.5060403@websitemanagers.com.au> Date: Tue, 18 Sep 2012 22:24:10 +1000 From: Adam Goryachev Organization: Website Managers User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:15.0) Gecko/20120827 Thunderbird/15.0 MIME-Version: 1.0 To: xen-users@lists.xen.org References: <5051D0C5.5070600@websitemanagers.com.au> <1347609879.24226.148.camel@zakaz.uk.xensource.com> <50532CE9.5080601@websitemanagers.com.au> <1347629416.24226.208.camel@zakaz.uk.xensource.com> <1347872072.14977.22.camel@zakaz.uk.xensource.com> In-Reply-To: <1347872072.14977.22.camel@zakaz.uk.xensource.com> Subject: Re: [Xen-users] Poor Windows 2003 + GPLPV performance compared to VMWare X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org On 17/09/12 18:54, Ian Campbell wrote: > On Fri, 2012-09-14 at 14:30 +0100, Ian Campbell wrote: >>>> Does your system have any NUMA properties? >>> I don't really understand this question.... is there a simple method to >>> check? It is a AMD Phenom(tm) II X6 1100T Processor on a reasonable >>> desktop motherboard, nothing fancy.... > I don't have a NUMA system to hand, but on my non-NUMA system I see in > the logs: > (XEN) No NUMA configuration found > > You should see that or something more informative. "xm dmesg|grep -i numa" produces no output, so again, I still have no definitive answer to this. Actually, got it... : dmesg|grep -i numa [ 0.000000] Scanning NUMA topology in Northbridge 24 [ 0.000000] No NUMA configuration found That is not xen, that is the normal kernel... or perhaps xen has hidden the numa config from linux... I'm really not sure... > Also at least in 4.2 "xl info -n" gives some details. Not sure if xm has > the same option? This is getting better. xm info -n numa_info : none Amongst lots of other interesting information. So, seems pretty definitive that there is no numa support here. Is this still relevant to the diagnosis of very slow windows domu? Thanks for your help and patience. Regards, Adam -- Adam Goryachev Website Managers www.websitemanagers.com.au _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Tue Sep 18 12:26:27 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Tue, 18 Sep 2012 12:26:27 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TDwrA-0003Ua-7R; Tue, 18 Sep 2012 12:24:48 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TDwr9-0003UU-3h for xen-users@lists.xen.org; Tue, 18 Sep 2012 12:24:47 +0000 Received: from [85.158.143.99:60274] by server-1.bemta-4.messagelabs.com id 7A/65-12504-E0868505; Tue, 18 Sep 2012 12:24:46 +0000 X-Env-Sender: mailinglists@websitemanagers.com.au X-Msg-Ref: server-4.tower-216.messagelabs.com!1347971082!25534362!1 X-Originating-IP: [203.56.191.70] X-SpamReason: No, hits=0.0 required=7.0 tests= X-StarScan-Received: X-StarScan-Version: 6.6.1.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 13982 invoked from network); 18 Sep 2012 12:24:45 -0000 Received: from unknown (HELO hammer.websitemanagers.com.au) (203.56.191.70) by server-4.tower-216.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 18 Sep 2012 12:24:45 -0000 Received: (qmail 6780 invoked by uid 1011); 18 Sep 2012 12:24:11 -0000 Received: from 220.233.87.52 by hammer (envelope-from , uid 1008) with qmail-scanner-1.24 (clamdscan: 0.97.3/15367. spamassassin: 3.3.1. Clear:RC:1(220.233.87.52):. Processed in 0.054554 secs); 18 Sep 2012 12:24:11 -0000 Received: from unknown (HELO ?192.168.2.90?) (220.233.87.52) by 0 with SMTP; 18 Sep 2012 12:24:11 -0000 Message-ID: <505867EA.5060403@websitemanagers.com.au> Date: Tue, 18 Sep 2012 22:24:10 +1000 From: Adam Goryachev Organization: Website Managers User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:15.0) Gecko/20120827 Thunderbird/15.0 MIME-Version: 1.0 To: xen-users@lists.xen.org References: <5051D0C5.5070600@websitemanagers.com.au> <1347609879.24226.148.camel@zakaz.uk.xensource.com> <50532CE9.5080601@websitemanagers.com.au> <1347629416.24226.208.camel@zakaz.uk.xensource.com> <1347872072.14977.22.camel@zakaz.uk.xensource.com> In-Reply-To: <1347872072.14977.22.camel@zakaz.uk.xensource.com> Subject: Re: [Xen-users] Poor Windows 2003 + GPLPV performance compared to VMWare X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org On 17/09/12 18:54, Ian Campbell wrote: > On Fri, 2012-09-14 at 14:30 +0100, Ian Campbell wrote: >>>> Does your system have any NUMA properties? >>> I don't really understand this question.... is there a simple method to >>> check? It is a AMD Phenom(tm) II X6 1100T Processor on a reasonable >>> desktop motherboard, nothing fancy.... > I don't have a NUMA system to hand, but on my non-NUMA system I see in > the logs: > (XEN) No NUMA configuration found > > You should see that or something more informative. "xm dmesg|grep -i numa" produces no output, so again, I still have no definitive answer to this. Actually, got it... : dmesg|grep -i numa [ 0.000000] Scanning NUMA topology in Northbridge 24 [ 0.000000] No NUMA configuration found That is not xen, that is the normal kernel... or perhaps xen has hidden the numa config from linux... I'm really not sure... > Also at least in 4.2 "xl info -n" gives some details. Not sure if xm has > the same option? This is getting better. xm info -n numa_info : none Amongst lots of other interesting information. So, seems pretty definitive that there is no numa support here. Is this still relevant to the diagnosis of very slow windows domu? Thanks for your help and patience. Regards, Adam -- Adam Goryachev Website Managers www.websitemanagers.com.au _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Tue Sep 18 12:44:57 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Tue, 18 Sep 2012 12:44:57 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TDx9h-00044M-Je; Tue, 18 Sep 2012 12:43:57 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TDx9g-00044H-Kb for xen-users@lists.xen.org; Tue, 18 Sep 2012 12:43:57 +0000 Received: from [85.158.139.211:38610] by server-7.bemta-5.messagelabs.com id 25/2A-19703-B8C68505; Tue, 18 Sep 2012 12:43:55 +0000 X-Env-Sender: asim.mcp@gmail.com X-Msg-Ref: server-14.tower-206.messagelabs.com!1347972231!18972183!1 X-Originating-IP: [209.85.220.173] X-SpamReason: No, hits=0.9 required=7.0 tests=HTML_40_50,HTML_MESSAGE, ML_RADAR_SPEW_LINKS_14,RCVD_BY_IP,spamassassin: X-StarScan-Received: X-StarScan-Version: 6.6.1.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 2971 invoked from network); 18 Sep 2012 12:43:52 -0000 Received: from mail-vc0-f173.google.com (HELO mail-vc0-f173.google.com) (209.85.220.173) by server-14.tower-206.messagelabs.com with RC4-SHA encrypted SMTP; 18 Sep 2012 12:43:52 -0000 Received: by vcbfl15 with SMTP id fl15so10325050vcb.32 for ; Tue, 18 Sep 2012 05:43:51 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :content-type; bh=TUJZlc8i2c1SNyxjBlxpm0r9f1lL1s6rhLZ28kt2Npw=; b=NoZ5UWjvd7cGmQbVKrfiLVtU63CdIYPCbHA52gaLjyqB9mcisnZQYf01w8xQtUrw2k ZpVC/YoYTmixm/h80ImahziTo8L8+iRh1La4Qujp9dYdS56KDY3Jes6WkG1LC2pE4RgD As6b1ulTWu7zqDkjDNktnFC0AQP4vyQ3VpllciLH9QvGTUbv8Tqcz9MKapO957G1fsAx Gttd1IUBE0kEWVQoIywprc8afDib0/D2t13RGR+tghYzYhtiwOKHDJNZDtjCOJ3ywvBm pl4RyxERYvIFz4BhMqSZ+UmJr+G8Ma/SE8g/RE3LS07evB8TbQmdKGKdIkL5/utah3HS aI+Q== Received: by 10.52.95.46 with SMTP id dh14mr4986406vdb.114.1347972231040; Tue, 18 Sep 2012 05:43:51 -0700 (PDT) MIME-Version: 1.0 Received: by 10.220.203.10 with HTTP; Tue, 18 Sep 2012 05:43:30 -0700 (PDT) In-Reply-To: References: From: asim hafeez Date: Tue, 18 Sep 2012 17:43:30 +0500 Message-ID: To: xen-users@lists.xen.org Subject: Re: [Xen-users] hvm cifs image boot issue X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============4381860054759753507==" Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org --===============4381860054759753507== Content-Type: multipart/alternative; boundary=20cf3071cc68ff8eef04c9f93d88 --20cf3071cc68ff8eef04c9f93d88 Content-Type: text/plain; charset=ISO-8859-1 Anyone please help in this regard. Is this qemu issue or xen issue? On Thu, Sep 13, 2012 at 6:13 PM, asim hafeez wrote: > Hi, > > I've all of the .img files to a network share, whenever i want to boot a > machine using any server i just use cifs path. I've configured Xen4.1.x > with Linux Kernel 3.5.x. > HVM is working if the .img file is copied to local system's disk. If i se > cifs path it does not boot. and shows 0MByets on VNC console for HDD. > > Kindly help in this regards > > -- > Best Regards > Asim > -- Best Regards Asim --20cf3071cc68ff8eef04c9f93d88 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Anyone please help in this regard.

Is this qemu issue or= xen issue?

On Thu, Sep 13, 2012 at 6:13 = PM, asim hafeez <asim.mcp@gmail.com> wrote:
Hi,

I've all of the .= img files to a network share, whenever i want to boot a machine using any s= erver i just use cifs path. I've configured Xen4.1.x with Linux Kernel = 3.5.x.
HVM is working if the .img file is copied to local system's disk. = If i se cifs path it does not boot. and shows 0MByets on VNC console for HD= D.=A0

Kindly help in this regards

--
Best Regards
Asim



--

Best Reg= ards
Asim
--20cf3071cc68ff8eef04c9f93d88-- --===============4381860054759753507== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users --===============4381860054759753507==-- From xen-users-bounces@lists.xen.org Tue Sep 18 12:44:57 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Tue, 18 Sep 2012 12:44:57 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TDx9h-00044M-Je; Tue, 18 Sep 2012 12:43:57 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TDx9g-00044H-Kb for xen-users@lists.xen.org; Tue, 18 Sep 2012 12:43:57 +0000 Received: from [85.158.139.211:38610] by server-7.bemta-5.messagelabs.com id 25/2A-19703-B8C68505; Tue, 18 Sep 2012 12:43:55 +0000 X-Env-Sender: asim.mcp@gmail.com X-Msg-Ref: server-14.tower-206.messagelabs.com!1347972231!18972183!1 X-Originating-IP: [209.85.220.173] X-SpamReason: No, hits=0.9 required=7.0 tests=HTML_40_50,HTML_MESSAGE, ML_RADAR_SPEW_LINKS_14,RCVD_BY_IP,spamassassin: X-StarScan-Received: X-StarScan-Version: 6.6.1.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 2971 invoked from network); 18 Sep 2012 12:43:52 -0000 Received: from mail-vc0-f173.google.com (HELO mail-vc0-f173.google.com) (209.85.220.173) by server-14.tower-206.messagelabs.com with RC4-SHA encrypted SMTP; 18 Sep 2012 12:43:52 -0000 Received: by vcbfl15 with SMTP id fl15so10325050vcb.32 for ; Tue, 18 Sep 2012 05:43:51 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :content-type; bh=TUJZlc8i2c1SNyxjBlxpm0r9f1lL1s6rhLZ28kt2Npw=; b=NoZ5UWjvd7cGmQbVKrfiLVtU63CdIYPCbHA52gaLjyqB9mcisnZQYf01w8xQtUrw2k ZpVC/YoYTmixm/h80ImahziTo8L8+iRh1La4Qujp9dYdS56KDY3Jes6WkG1LC2pE4RgD As6b1ulTWu7zqDkjDNktnFC0AQP4vyQ3VpllciLH9QvGTUbv8Tqcz9MKapO957G1fsAx Gttd1IUBE0kEWVQoIywprc8afDib0/D2t13RGR+tghYzYhtiwOKHDJNZDtjCOJ3ywvBm pl4RyxERYvIFz4BhMqSZ+UmJr+G8Ma/SE8g/RE3LS07evB8TbQmdKGKdIkL5/utah3HS aI+Q== Received: by 10.52.95.46 with SMTP id dh14mr4986406vdb.114.1347972231040; Tue, 18 Sep 2012 05:43:51 -0700 (PDT) MIME-Version: 1.0 Received: by 10.220.203.10 with HTTP; Tue, 18 Sep 2012 05:43:30 -0700 (PDT) In-Reply-To: References: From: asim hafeez Date: Tue, 18 Sep 2012 17:43:30 +0500 Message-ID: To: xen-users@lists.xen.org Subject: Re: [Xen-users] hvm cifs image boot issue X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============4381860054759753507==" Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org --===============4381860054759753507== Content-Type: multipart/alternative; boundary=20cf3071cc68ff8eef04c9f93d88 --20cf3071cc68ff8eef04c9f93d88 Content-Type: text/plain; charset=ISO-8859-1 Anyone please help in this regard. Is this qemu issue or xen issue? On Thu, Sep 13, 2012 at 6:13 PM, asim hafeez wrote: > Hi, > > I've all of the .img files to a network share, whenever i want to boot a > machine using any server i just use cifs path. I've configured Xen4.1.x > with Linux Kernel 3.5.x. > HVM is working if the .img file is copied to local system's disk. If i se > cifs path it does not boot. and shows 0MByets on VNC console for HDD. > > Kindly help in this regards > > -- > Best Regards > Asim > -- Best Regards Asim --20cf3071cc68ff8eef04c9f93d88 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Anyone please help in this regard.

Is this qemu issue or= xen issue?

On Thu, Sep 13, 2012 at 6:13 = PM, asim hafeez <asim.mcp@gmail.com> wrote:
Hi,

I've all of the .= img files to a network share, whenever i want to boot a machine using any s= erver i just use cifs path. I've configured Xen4.1.x with Linux Kernel = 3.5.x.
HVM is working if the .img file is copied to local system's disk. = If i se cifs path it does not boot. and shows 0MByets on VNC console for HD= D.=A0

Kindly help in this regards

--
Best Regards
Asim



--

Best Reg= ards
Asim
--20cf3071cc68ff8eef04c9f93d88-- --===============4381860054759753507== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users --===============4381860054759753507==-- From xen-users-bounces@lists.xen.org Tue Sep 18 12:53:11 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Tue, 18 Sep 2012 12:53:11 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TDxHv-0004MA-RZ; Tue, 18 Sep 2012 12:52:27 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TDxHu-0004M0-7O for xen-users@lists.xen.org; Tue, 18 Sep 2012 12:52:26 +0000 Received: from [85.158.139.211:63047] by server-11.bemta-5.messagelabs.com id F9/F8-24658-98E68505; Tue, 18 Sep 2012 12:52:25 +0000 X-Env-Sender: mailinglists@websitemanagers.com.au X-Msg-Ref: server-15.tower-206.messagelabs.com!1347972740!19073862!1 X-Originating-IP: [203.56.191.70] X-SpamReason: No, hits=0.5 required=7.0 tests=BODY_RANDOM_LONG X-StarScan-Received: X-StarScan-Version: 6.6.1.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 9747 invoked from network); 18 Sep 2012 12:52:24 -0000 Received: from unknown (HELO hammer.websitemanagers.com.au) (203.56.191.70) by server-15.tower-206.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 18 Sep 2012 12:52:24 -0000 Received: (qmail 15819 invoked by uid 1011); 18 Sep 2012 12:51:49 -0000 Received: from 124.246.8.196 by hammer (envelope-from , uid 1008) with qmail-scanner-1.24 (clamdscan: 0.97.3/15367. spamassassin: 3.3.1. Clear:RC:1(124.246.8.196):. Processed in 0.066435 secs); 18 Sep 2012 12:51:49 -0000 Received: from unknown (HELO ?192.168.2.90?) (124.246.8.196) by 0 with SMTP; 18 Sep 2012 12:51:49 -0000 Message-ID: <50586E65.7090502@websitemanagers.com.au> Date: Tue, 18 Sep 2012 22:51:49 +1000 From: Adam Goryachev Organization: Website Managers User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:15.0) Gecko/20120827 Thunderbird/15.0 MIME-Version: 1.0 To: xen-users@lists.xen.org References: <5051D0C5.5070600@websitemanagers.com.au> <5055D921.1000001@concero.nl> In-Reply-To: <5055D921.1000001@concero.nl> Subject: Re: [Xen-users] Poor Windows 2003 + GPLPV performance compared to VMWare X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org On 16/09/12 23:50, Dion Kant wrote: > Adam, > > Can you give it a retry with the Windows DomU running from a file container? > > mount another LV somewhere on dom0 (e.g. /var/lib/xen/images/windows) > Use "qemu-img convert your.vmdk -O raw > /var/lib/xen/images/windows/disk0.raw" to create the file container > > I see significant disk I/O performance improvement on all my Windows > DomU's when running them from file containers as compared to running > them directly from a block device. > I'd really like to try this and see if it helps, but I'm not sure how I can achieve that. The dom0 machine has a 60GB SSD drive internally, and the VM is 230G, so I don't think I can put it on the local system. Also, I don't think I would need to convert it, the disk is already in raw format... I should be able to simply do: dd if=/dev/sdX of=disk0.raw where sdX is whatever disk linux has assigned to this iSCSI device. In any case, I can't do this at this stage. About the only thing I could consider would be to make a copy of the VM onto another host (not on the SAN) and share that to the dom0 using NFS, which would then get me a file based image (over NFS) to HDD backed storage. Though I think this is changing far too many factors to really be useful (the SAN is SSD backed btw). Finally, I was always of the impression that physical devices provided better performance due to lower overhead. I presume you are suggesting better performance from RAM based caching on the dom0. disk = [ 'phy:/dev/disk/by-path/ip-172.30.10.23:3260-iscsi-iqn.2012-06.domain:host-lun-0,xvda,w' ] Could I simply change that line to this: disk = [ 'file:/dev/disk/by-path/ip-172.30.10.23:3260-iscsi-iqn.2012-06.domain:host-lun-0,xvda,w' ] Since a device is just a file... or would that not make a difference? OK, well, it doesn't work: Error: Disk image does not exist: /dev/sdd (well, originally it had the above path, but I tried the direct /dev/sdd and same error). Any further suggestions please? Thanks, Adam -- Adam Goryachev Website Managers www.websitemanagers.com.au _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Tue Sep 18 12:53:11 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Tue, 18 Sep 2012 12:53:11 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TDxHv-0004MA-RZ; Tue, 18 Sep 2012 12:52:27 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TDxHu-0004M0-7O for xen-users@lists.xen.org; Tue, 18 Sep 2012 12:52:26 +0000 Received: from [85.158.139.211:63047] by server-11.bemta-5.messagelabs.com id F9/F8-24658-98E68505; Tue, 18 Sep 2012 12:52:25 +0000 X-Env-Sender: mailinglists@websitemanagers.com.au X-Msg-Ref: server-15.tower-206.messagelabs.com!1347972740!19073862!1 X-Originating-IP: [203.56.191.70] X-SpamReason: No, hits=0.5 required=7.0 tests=BODY_RANDOM_LONG X-StarScan-Received: X-StarScan-Version: 6.6.1.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 9747 invoked from network); 18 Sep 2012 12:52:24 -0000 Received: from unknown (HELO hammer.websitemanagers.com.au) (203.56.191.70) by server-15.tower-206.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 18 Sep 2012 12:52:24 -0000 Received: (qmail 15819 invoked by uid 1011); 18 Sep 2012 12:51:49 -0000 Received: from 124.246.8.196 by hammer (envelope-from , uid 1008) with qmail-scanner-1.24 (clamdscan: 0.97.3/15367. spamassassin: 3.3.1. Clear:RC:1(124.246.8.196):. Processed in 0.066435 secs); 18 Sep 2012 12:51:49 -0000 Received: from unknown (HELO ?192.168.2.90?) (124.246.8.196) by 0 with SMTP; 18 Sep 2012 12:51:49 -0000 Message-ID: <50586E65.7090502@websitemanagers.com.au> Date: Tue, 18 Sep 2012 22:51:49 +1000 From: Adam Goryachev Organization: Website Managers User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:15.0) Gecko/20120827 Thunderbird/15.0 MIME-Version: 1.0 To: xen-users@lists.xen.org References: <5051D0C5.5070600@websitemanagers.com.au> <5055D921.1000001@concero.nl> In-Reply-To: <5055D921.1000001@concero.nl> Subject: Re: [Xen-users] Poor Windows 2003 + GPLPV performance compared to VMWare X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org On 16/09/12 23:50, Dion Kant wrote: > Adam, > > Can you give it a retry with the Windows DomU running from a file container? > > mount another LV somewhere on dom0 (e.g. /var/lib/xen/images/windows) > Use "qemu-img convert your.vmdk -O raw > /var/lib/xen/images/windows/disk0.raw" to create the file container > > I see significant disk I/O performance improvement on all my Windows > DomU's when running them from file containers as compared to running > them directly from a block device. > I'd really like to try this and see if it helps, but I'm not sure how I can achieve that. The dom0 machine has a 60GB SSD drive internally, and the VM is 230G, so I don't think I can put it on the local system. Also, I don't think I would need to convert it, the disk is already in raw format... I should be able to simply do: dd if=/dev/sdX of=disk0.raw where sdX is whatever disk linux has assigned to this iSCSI device. In any case, I can't do this at this stage. About the only thing I could consider would be to make a copy of the VM onto another host (not on the SAN) and share that to the dom0 using NFS, which would then get me a file based image (over NFS) to HDD backed storage. Though I think this is changing far too many factors to really be useful (the SAN is SSD backed btw). Finally, I was always of the impression that physical devices provided better performance due to lower overhead. I presume you are suggesting better performance from RAM based caching on the dom0. disk = [ 'phy:/dev/disk/by-path/ip-172.30.10.23:3260-iscsi-iqn.2012-06.domain:host-lun-0,xvda,w' ] Could I simply change that line to this: disk = [ 'file:/dev/disk/by-path/ip-172.30.10.23:3260-iscsi-iqn.2012-06.domain:host-lun-0,xvda,w' ] Since a device is just a file... or would that not make a difference? OK, well, it doesn't work: Error: Disk image does not exist: /dev/sdd (well, originally it had the above path, but I tried the direct /dev/sdd and same error). Any further suggestions please? Thanks, Adam -- Adam Goryachev Website Managers www.websitemanagers.com.au _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Tue Sep 18 13:07:53 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Tue, 18 Sep 2012 13:07:53 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TDxW9-0004qE-J0; Tue, 18 Sep 2012 13:07:09 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TDxW7-0004q9-S4 for xen-users@lists.xen.org; Tue, 18 Sep 2012 13:07:08 +0000 Received: from [85.158.138.51:18061] by server-4.bemta-3.messagelabs.com id 1B/03-24831-BF178505; Tue, 18 Sep 2012 13:07:07 +0000 X-Env-Sender: mailinglists@websitemanagers.com.au X-Msg-Ref: server-16.tower-174.messagelabs.com!1347973622!30946793!1 X-Originating-IP: [203.56.191.70] X-SpamReason: No, hits=0.0 required=7.0 tests= X-StarScan-Received: X-StarScan-Version: 6.6.1.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 28580 invoked from network); 18 Sep 2012 13:07:05 -0000 Received: from unknown (HELO hammer.websitemanagers.com.au) (203.56.191.70) by server-16.tower-174.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 18 Sep 2012 13:07:05 -0000 Received: (qmail 20824 invoked by uid 1011); 18 Sep 2012 13:06:31 -0000 Received: from 124.246.8.196 by hammer (envelope-from , uid 1008) with qmail-scanner-1.24 (clamdscan: 0.97.3/15367. spamassassin: 3.3.1. Clear:RC:1(124.246.8.196):. Processed in 0.160486 secs); 18 Sep 2012 13:06:31 -0000 Received: from unknown (HELO ?192.168.2.90?) (124.246.8.196) by 0 with SMTP; 18 Sep 2012 13:06:31 -0000 Message-ID: <505871D6.2060801@websitemanagers.com.au> Date: Tue, 18 Sep 2012 23:06:30 +1000 From: Adam Goryachev Organization: Website Managers User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:15.0) Gecko/20120827 Thunderbird/15.0 MIME-Version: 1.0 To: xen-users@lists.xen.org References: <5051D0C5.5070600@websitemanagers.com.au> <1347609879.24226.148.camel@zakaz.uk.xensource.com> <50532CE9.5080601@websitemanagers.com.au> <1347629416.24226.208.camel@zakaz.uk.xensource.com> <505344E8.2030400@websitemanagers.com.au> In-Reply-To: <505344E8.2030400@websitemanagers.com.au> Subject: Re: [Xen-users] Poor Windows 2003 + GPLPV performance compared to VMWare X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org On 15/09/12 00:53, Adam Goryachev wrote: > On 14/09/12 23:30, Ian Campbell wrote: > >>>>> device_model = '/usr/lib/xen-default/bin/qemu-dm' >>>>> localtime = 1 >>>>> name = "vm1" >>>>> cpus = "2,3,4,5" # Which physical CPU's to allow >>>> Have you pinned dom0 to use pCPU 1 and/p pCPUs > 6? >>> No, how should I pin dom0 to cpu0 ? >> dom0_vcpus_pin as described in >> http://xenbits.xen.org/docs/4.2-testing/misc/xen-command-line.html > Thanks, I'll need to reboot the dom0 to apply this, will do as soon as > this current scheduled task is complete. OK, I have pinned dom0 to cpu0, and this had no effect on performance. >> You have: >> cpus = "2,3,4,5" >> which means "let all the guests VCPUs run on any of PCPUS 2-5". >> >> It sounds like what you are asking for above is: >> cpus = [2,3,4,5] >> Which forces guest vcpu0=>pcpu=2, 1=>3, 2=>4 and 3=>5. >> >> Subtle I agree. > Ugh... ok, I'll give that a try. BTW, it would seem this is different > from xen 4.0 (from debian stable) where it seems to magically do what I > meant to say, or I'm just lucky on those machines :) Actually, the above syntax doesn't work: cpus = [2,3,4,5] # Which physical CPU's to allow Error: 'int' object has no attribute 'split' Once I reverted to: cpus = "2,3,4,5" I can then boot again, but on reboot I get this: xm vcpu-list Name ID VCPU CPU State Time(s) CPU Affinity Domain-0 0 0 0 r-- 148.9 0 cobweb 6 0 5 --- 0.5 2-5 cobweb 6 1 - --p 0.0 2-5 cobweb 6 2 - --p 0.0 2-5 cobweb 6 3 - --p 0.0 2-5 So it isn't pinning each vcpu to a specific cpu... but I suppose it should be smart enough to do it well anyway... Performance is still at the same level. >> Do you have a specific reason for pinning? I'd be tempted to just let >> the scheduler do its thing unless/until you determine that it is causing >> problems. > The only reason for pinning is: > a) To stop the scheduler from moving the vCPU around on the pCPU, from > my understanding this improves performance > b) when running multiple DOMU, I either want a bunch of DOMU to share > one cpu, while I want one or more dedicated CPU other DOMU. (ie, I use > this as a type of prioritisation/performance tuning. > > In this case, there is only a single VM, though if some hardware is lost > (other physical machines) then will end up with multiple VM's... > >>>> How many dom0 vcpus have you configured? >>> I assume by default it takes all of them... >> Correct. dom0_max_vcpus will adjust this for you. > Will adjust on the next reboot.... Done, dom0 is set to 1 cpu, but still makes no difference to performance. >>>> And as James suggests it would also be useful to benchmark iSCSI running >>>> in dom0 and perhaps even running on the same system without Xen (just >>>> Linux) using the same kernel. I'm not sure if VMware offers something >>>> similar which could be used for comparison. >>> Well, that is where things start to get complicated rather quickly... >>> There are a lot of layers here, but I'd prefer to look at the issues >>> closer to xen first, since vmware was working from an identically >>> configured san/etc, so nothing at all has changed there. Ultimately, the >>> san is using 3 x SSD in RAID5. I have done various testing in the past >>> from plain linux (with older kernel 2.6.32 from debian stable) and >>> achieved reasonable figures (I don't recall exactly). >> I was worried about the Linux side rather than the SAN itself, but it >> sounds like you've got that covered. > At this stage, the limiting performance should be the single gig > ethernet for the physical machine to connect to the network. (The san > side has 4 x gig ethernet). > > This is a live network/system, but it has been a work in progress for > the past 12 months... > > I'll update further once I can get some testing and answers... Will do a > test with only changing the shadow_memory, and then if no big > improvement, will reboot with the changes to the dom0 cpus etc, and test > again. > I'm really at a bit of a loss on where to go from here.... The standard performance improvements don't seem to make any difference at all, and I'm running out of ideas.... Could you suggest a "standard" tool which would allow me to test disk IO performance (this is my initial suspicion for slow performance), and also CPU performance (I'm starting to suspect this too now) in both windows (domU), linux (domU I can create one for testing) and Linux (dom0). Then I can see where performance is lost (CPU/disk) and at what layer (dom0/domU) etc... Thanks, Adam -- Adam Goryachev Website Managers www.websitemanagers.com.au _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Tue Sep 18 13:07:53 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Tue, 18 Sep 2012 13:07:53 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TDxW9-0004qE-J0; Tue, 18 Sep 2012 13:07:09 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TDxW7-0004q9-S4 for xen-users@lists.xen.org; Tue, 18 Sep 2012 13:07:08 +0000 Received: from [85.158.138.51:18061] by server-4.bemta-3.messagelabs.com id 1B/03-24831-BF178505; Tue, 18 Sep 2012 13:07:07 +0000 X-Env-Sender: mailinglists@websitemanagers.com.au X-Msg-Ref: server-16.tower-174.messagelabs.com!1347973622!30946793!1 X-Originating-IP: [203.56.191.70] X-SpamReason: No, hits=0.0 required=7.0 tests= X-StarScan-Received: X-StarScan-Version: 6.6.1.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 28580 invoked from network); 18 Sep 2012 13:07:05 -0000 Received: from unknown (HELO hammer.websitemanagers.com.au) (203.56.191.70) by server-16.tower-174.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 18 Sep 2012 13:07:05 -0000 Received: (qmail 20824 invoked by uid 1011); 18 Sep 2012 13:06:31 -0000 Received: from 124.246.8.196 by hammer (envelope-from , uid 1008) with qmail-scanner-1.24 (clamdscan: 0.97.3/15367. spamassassin: 3.3.1. Clear:RC:1(124.246.8.196):. Processed in 0.160486 secs); 18 Sep 2012 13:06:31 -0000 Received: from unknown (HELO ?192.168.2.90?) (124.246.8.196) by 0 with SMTP; 18 Sep 2012 13:06:31 -0000 Message-ID: <505871D6.2060801@websitemanagers.com.au> Date: Tue, 18 Sep 2012 23:06:30 +1000 From: Adam Goryachev Organization: Website Managers User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:15.0) Gecko/20120827 Thunderbird/15.0 MIME-Version: 1.0 To: xen-users@lists.xen.org References: <5051D0C5.5070600@websitemanagers.com.au> <1347609879.24226.148.camel@zakaz.uk.xensource.com> <50532CE9.5080601@websitemanagers.com.au> <1347629416.24226.208.camel@zakaz.uk.xensource.com> <505344E8.2030400@websitemanagers.com.au> In-Reply-To: <505344E8.2030400@websitemanagers.com.au> Subject: Re: [Xen-users] Poor Windows 2003 + GPLPV performance compared to VMWare X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org On 15/09/12 00:53, Adam Goryachev wrote: > On 14/09/12 23:30, Ian Campbell wrote: > >>>>> device_model = '/usr/lib/xen-default/bin/qemu-dm' >>>>> localtime = 1 >>>>> name = "vm1" >>>>> cpus = "2,3,4,5" # Which physical CPU's to allow >>>> Have you pinned dom0 to use pCPU 1 and/p pCPUs > 6? >>> No, how should I pin dom0 to cpu0 ? >> dom0_vcpus_pin as described in >> http://xenbits.xen.org/docs/4.2-testing/misc/xen-command-line.html > Thanks, I'll need to reboot the dom0 to apply this, will do as soon as > this current scheduled task is complete. OK, I have pinned dom0 to cpu0, and this had no effect on performance. >> You have: >> cpus = "2,3,4,5" >> which means "let all the guests VCPUs run on any of PCPUS 2-5". >> >> It sounds like what you are asking for above is: >> cpus = [2,3,4,5] >> Which forces guest vcpu0=>pcpu=2, 1=>3, 2=>4 and 3=>5. >> >> Subtle I agree. > Ugh... ok, I'll give that a try. BTW, it would seem this is different > from xen 4.0 (from debian stable) where it seems to magically do what I > meant to say, or I'm just lucky on those machines :) Actually, the above syntax doesn't work: cpus = [2,3,4,5] # Which physical CPU's to allow Error: 'int' object has no attribute 'split' Once I reverted to: cpus = "2,3,4,5" I can then boot again, but on reboot I get this: xm vcpu-list Name ID VCPU CPU State Time(s) CPU Affinity Domain-0 0 0 0 r-- 148.9 0 cobweb 6 0 5 --- 0.5 2-5 cobweb 6 1 - --p 0.0 2-5 cobweb 6 2 - --p 0.0 2-5 cobweb 6 3 - --p 0.0 2-5 So it isn't pinning each vcpu to a specific cpu... but I suppose it should be smart enough to do it well anyway... Performance is still at the same level. >> Do you have a specific reason for pinning? I'd be tempted to just let >> the scheduler do its thing unless/until you determine that it is causing >> problems. > The only reason for pinning is: > a) To stop the scheduler from moving the vCPU around on the pCPU, from > my understanding this improves performance > b) when running multiple DOMU, I either want a bunch of DOMU to share > one cpu, while I want one or more dedicated CPU other DOMU. (ie, I use > this as a type of prioritisation/performance tuning. > > In this case, there is only a single VM, though if some hardware is lost > (other physical machines) then will end up with multiple VM's... > >>>> How many dom0 vcpus have you configured? >>> I assume by default it takes all of them... >> Correct. dom0_max_vcpus will adjust this for you. > Will adjust on the next reboot.... Done, dom0 is set to 1 cpu, but still makes no difference to performance. >>>> And as James suggests it would also be useful to benchmark iSCSI running >>>> in dom0 and perhaps even running on the same system without Xen (just >>>> Linux) using the same kernel. I'm not sure if VMware offers something >>>> similar which could be used for comparison. >>> Well, that is where things start to get complicated rather quickly... >>> There are a lot of layers here, but I'd prefer to look at the issues >>> closer to xen first, since vmware was working from an identically >>> configured san/etc, so nothing at all has changed there. Ultimately, the >>> san is using 3 x SSD in RAID5. I have done various testing in the past >>> from plain linux (with older kernel 2.6.32 from debian stable) and >>> achieved reasonable figures (I don't recall exactly). >> I was worried about the Linux side rather than the SAN itself, but it >> sounds like you've got that covered. > At this stage, the limiting performance should be the single gig > ethernet for the physical machine to connect to the network. (The san > side has 4 x gig ethernet). > > This is a live network/system, but it has been a work in progress for > the past 12 months... > > I'll update further once I can get some testing and answers... Will do a > test with only changing the shadow_memory, and then if no big > improvement, will reboot with the changes to the dom0 cpus etc, and test > again. > I'm really at a bit of a loss on where to go from here.... The standard performance improvements don't seem to make any difference at all, and I'm running out of ideas.... Could you suggest a "standard" tool which would allow me to test disk IO performance (this is my initial suspicion for slow performance), and also CPU performance (I'm starting to suspect this too now) in both windows (domU), linux (domU I can create one for testing) and Linux (dom0). Then I can see where performance is lost (CPU/disk) and at what layer (dom0/domU) etc... Thanks, Adam -- Adam Goryachev Website Managers www.websitemanagers.com.au _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Tue Sep 18 13:15:21 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Tue, 18 Sep 2012 13:15:21 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TDxdU-0005NV-3x; Tue, 18 Sep 2012 13:14:44 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TDxdS-0005N8-7u for xen-users@lists.xen.org; Tue, 18 Sep 2012 13:14:42 +0000 Received: from [85.158.138.51:17600] by server-4.bemta-3.messagelabs.com id C6/13-24831-1C378505; Tue, 18 Sep 2012 13:14:41 +0000 X-Env-Sender: mailinglists@websitemanagers.com.au X-Msg-Ref: server-3.tower-174.messagelabs.com!1347974076!22947221!1 X-Originating-IP: [203.56.191.70] X-SpamReason: No, hits=0.0 required=7.0 tests= X-StarScan-Received: X-StarScan-Version: 6.6.1.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 27801 invoked from network); 18 Sep 2012 13:14:40 -0000 Received: from unknown (HELO hammer.websitemanagers.com.au) (203.56.191.70) by server-3.tower-174.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 18 Sep 2012 13:14:40 -0000 Received: (qmail 23190 invoked by uid 1011); 18 Sep 2012 13:14:06 -0000 Received: from 124.246.8.196 by hammer (envelope-from , uid 1008) with qmail-scanner-1.24 (clamdscan: 0.97.3/15367. spamassassin: 3.3.1. Clear:RC:1(124.246.8.196):. Processed in 0.182405 secs); 18 Sep 2012 13:14:06 -0000 Received: from unknown (HELO ?192.168.2.90?) (124.246.8.196) by 0 with SMTP; 18 Sep 2012 13:14:05 -0000 Message-ID: <5058739D.9060505@websitemanagers.com.au> Date: Tue, 18 Sep 2012 23:14:05 +1000 From: Adam Goryachev Organization: Website Managers User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:15.0) Gecko/20120827 Thunderbird/15.0 MIME-Version: 1.0 To: James Harper References: <5051D0C5.5070600@websitemanagers.com.au> <1347609879.24226.148.camel@zakaz.uk.xensource.com> <50532CE9.5080601@websitemanagers.com.au> <6035A0D088A63A46850C3988ED045A4B29B9266E@BITCOM1.int.sbss.com.au> In-Reply-To: <6035A0D088A63A46850C3988ED045A4B29B9266E@BITCOM1.int.sbss.com.au> Cc: "xen-users@lists.xen.org" , Ian Campbell Subject: Re: [Xen-users] Poor Windows 2003 + GPLPV performance compared to VMWare X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org On 15/09/12 15:59, James Harper wrote: >>> Are you certain the GPLPV drivers have taken hold and you aren't using >>> emulated devices? >> >> Within Windows, Device Manager shows the Disk Drives as "XEV PV DISK SCSI >> Disk Device", this is the newest one which it detected and installed after I >> changed the config from hda to xvda. >> > > That's definitely using GPLPV. Changing hda to xvda should have any impact on anything that GPLPV cares about. > > Can you confirm that you definitely are running Windows 2003 SP2? Anything prior will have a big impact on performance. Hmmm, ooops, to be honest I almost didn't bother checking this to confirm, as I assumed it would obviously be the latest service pack. However, it would seem that I am very wrong, it is Windows 2003 service pack 1. I'll see if I can get all the latest service packs installed and updated, and then re-test and see how it goes. Thanks so much for your suggestion. Regards, Adam -- Adam Goryachev Website Managers www.websitemanagers.com.au _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Tue Sep 18 13:15:21 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Tue, 18 Sep 2012 13:15:21 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TDxdU-0005NV-3x; Tue, 18 Sep 2012 13:14:44 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TDxdS-0005N8-7u for xen-users@lists.xen.org; Tue, 18 Sep 2012 13:14:42 +0000 Received: from [85.158.138.51:17600] by server-4.bemta-3.messagelabs.com id C6/13-24831-1C378505; Tue, 18 Sep 2012 13:14:41 +0000 X-Env-Sender: mailinglists@websitemanagers.com.au X-Msg-Ref: server-3.tower-174.messagelabs.com!1347974076!22947221!1 X-Originating-IP: [203.56.191.70] X-SpamReason: No, hits=0.0 required=7.0 tests= X-StarScan-Received: X-StarScan-Version: 6.6.1.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 27801 invoked from network); 18 Sep 2012 13:14:40 -0000 Received: from unknown (HELO hammer.websitemanagers.com.au) (203.56.191.70) by server-3.tower-174.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 18 Sep 2012 13:14:40 -0000 Received: (qmail 23190 invoked by uid 1011); 18 Sep 2012 13:14:06 -0000 Received: from 124.246.8.196 by hammer (envelope-from , uid 1008) with qmail-scanner-1.24 (clamdscan: 0.97.3/15367. spamassassin: 3.3.1. Clear:RC:1(124.246.8.196):. Processed in 0.182405 secs); 18 Sep 2012 13:14:06 -0000 Received: from unknown (HELO ?192.168.2.90?) (124.246.8.196) by 0 with SMTP; 18 Sep 2012 13:14:05 -0000 Message-ID: <5058739D.9060505@websitemanagers.com.au> Date: Tue, 18 Sep 2012 23:14:05 +1000 From: Adam Goryachev Organization: Website Managers User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:15.0) Gecko/20120827 Thunderbird/15.0 MIME-Version: 1.0 To: James Harper References: <5051D0C5.5070600@websitemanagers.com.au> <1347609879.24226.148.camel@zakaz.uk.xensource.com> <50532CE9.5080601@websitemanagers.com.au> <6035A0D088A63A46850C3988ED045A4B29B9266E@BITCOM1.int.sbss.com.au> In-Reply-To: <6035A0D088A63A46850C3988ED045A4B29B9266E@BITCOM1.int.sbss.com.au> Cc: "xen-users@lists.xen.org" , Ian Campbell Subject: Re: [Xen-users] Poor Windows 2003 + GPLPV performance compared to VMWare X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org On 15/09/12 15:59, James Harper wrote: >>> Are you certain the GPLPV drivers have taken hold and you aren't using >>> emulated devices? >> >> Within Windows, Device Manager shows the Disk Drives as "XEV PV DISK SCSI >> Disk Device", this is the newest one which it detected and installed after I >> changed the config from hda to xvda. >> > > That's definitely using GPLPV. Changing hda to xvda should have any impact on anything that GPLPV cares about. > > Can you confirm that you definitely are running Windows 2003 SP2? Anything prior will have a big impact on performance. Hmmm, ooops, to be honest I almost didn't bother checking this to confirm, as I assumed it would obviously be the latest service pack. However, it would seem that I am very wrong, it is Windows 2003 service pack 1. I'll see if I can get all the latest service packs installed and updated, and then re-test and see how it goes. Thanks so much for your suggestion. Regards, Adam -- Adam Goryachev Website Managers www.websitemanagers.com.au _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Tue Sep 18 13:21:08 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Tue, 18 Sep 2012 13:21:08 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TDxjB-0006Ed-K8; Tue, 18 Sep 2012 13:20:37 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TDxjA-0006ES-3e for xen-users@lists.xen.org; Tue, 18 Sep 2012 13:20:36 +0000 Received: from [85.158.138.51:56469] by server-9.bemta-3.messagelabs.com id 70/FC-15390-32578505; Tue, 18 Sep 2012 13:20:35 +0000 X-Env-Sender: fajar@fajar.net X-Msg-Ref: server-8.tower-174.messagelabs.com!1347974432!30985145!1 X-Originating-IP: [209.85.214.173] X-SpamReason: No, hits=0.3 required=7.0 tests=RCVD_BY_IP X-StarScan-Received: X-StarScan-Version: 6.6.1.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 24467 invoked from network); 18 Sep 2012 13:20:33 -0000 Received: from mail-ob0-f173.google.com (HELO mail-ob0-f173.google.com) (209.85.214.173) by server-8.tower-174.messagelabs.com with RC4-SHA encrypted SMTP; 18 Sep 2012 13:20:33 -0000 Received: by obbta14 with SMTP id ta14so13064896obb.32 for ; Tue, 18 Sep 2012 06:20:31 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:x-gm-message-state; bh=IMQwH1UPo7ZeLKJVQB2w2EBADu9NIjJb4EM9Vu73FCk=; b=DaCnyrcLa2ARUz2whD91saGw3A3GIqnRTbCAvup9aqp/Z30CuRDw5LozsVbNqkJ0Je rtTb+z8bfrRwp4ho6MF7eOYabMGGQkNw3KZmGVCEUCLXvQW5yBAnY6Y3GJzXeSACbXp0 4PnxUsECDa3kfPV8xwJbASK81oqu4xHqU9X3Voj10N/BaaZaZB5I12l9bb62ax0cTNkq G8lBBlM+ue2ox0zIJmXgu7oqstYWZ3Hd1TdN0x3ydxwxsNl6cC8+cw4eexx6rzfO4tAL nn2dQUvmT1FAP95e4X/QpxyyL1H0GUEQlNi+8HHQ76w/8G9T86aMul6Lh1yITj/Z86Gb jlWg== MIME-Version: 1.0 Received: by 10.60.12.42 with SMTP id v10mr59232oeb.131.1347974431873; Tue, 18 Sep 2012 06:20:31 -0700 (PDT) Received: by 10.60.6.230 with HTTP; Tue, 18 Sep 2012 06:20:31 -0700 (PDT) In-Reply-To: <505871D6.2060801@websitemanagers.com.au> References: <5051D0C5.5070600@websitemanagers.com.au> <1347609879.24226.148.camel@zakaz.uk.xensource.com> <50532CE9.5080601@websitemanagers.com.au> <1347629416.24226.208.camel@zakaz.uk.xensource.com> <505344E8.2030400@websitemanagers.com.au> <505871D6.2060801@websitemanagers.com.au> Date: Tue, 18 Sep 2012 20:20:31 +0700 Message-ID: From: "Fajar A. Nugraha" To: Adam Goryachev X-Gm-Message-State: ALoCoQl4FFM875GnlirmgC4KZFeB6iZV47//+OoKe5RMT5Nb3ZW14M2FEX+KH5xZ1Qs0jInoOclL Cc: xen-users@lists.xen.org Subject: Re: [Xen-users] Poor Windows 2003 + GPLPV performance compared to VMWare X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org On Tue, Sep 18, 2012 at 8:06 PM, Adam Goryachev wrote: > Could you suggest a "standard" tool which would allow me to test disk IO > performance (this is my initial suspicion for slow performance), and I'd suggest you try fio, with random read/write load, and data size at least twice the ammount of memory. > also CPU performance (I'm starting to suspect this too now) in both not sure about that one. And I'm not sure it would be useful either. What is your application, and what kind of load was it? If it was a synthetic load, then it's already a good benchmark tool. However if it's live load that you can't control, I suggest you try something like sysbench to test sql performance. I usually use sysbench with mysql and 1 million rows. -- Fajar _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Tue Sep 18 13:21:08 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Tue, 18 Sep 2012 13:21:08 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TDxjB-0006Ed-K8; Tue, 18 Sep 2012 13:20:37 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TDxjA-0006ES-3e for xen-users@lists.xen.org; Tue, 18 Sep 2012 13:20:36 +0000 Received: from [85.158.138.51:56469] by server-9.bemta-3.messagelabs.com id 70/FC-15390-32578505; Tue, 18 Sep 2012 13:20:35 +0000 X-Env-Sender: fajar@fajar.net X-Msg-Ref: server-8.tower-174.messagelabs.com!1347974432!30985145!1 X-Originating-IP: [209.85.214.173] X-SpamReason: No, hits=0.3 required=7.0 tests=RCVD_BY_IP X-StarScan-Received: X-StarScan-Version: 6.6.1.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 24467 invoked from network); 18 Sep 2012 13:20:33 -0000 Received: from mail-ob0-f173.google.com (HELO mail-ob0-f173.google.com) (209.85.214.173) by server-8.tower-174.messagelabs.com with RC4-SHA encrypted SMTP; 18 Sep 2012 13:20:33 -0000 Received: by obbta14 with SMTP id ta14so13064896obb.32 for ; Tue, 18 Sep 2012 06:20:31 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:x-gm-message-state; bh=IMQwH1UPo7ZeLKJVQB2w2EBADu9NIjJb4EM9Vu73FCk=; b=DaCnyrcLa2ARUz2whD91saGw3A3GIqnRTbCAvup9aqp/Z30CuRDw5LozsVbNqkJ0Je rtTb+z8bfrRwp4ho6MF7eOYabMGGQkNw3KZmGVCEUCLXvQW5yBAnY6Y3GJzXeSACbXp0 4PnxUsECDa3kfPV8xwJbASK81oqu4xHqU9X3Voj10N/BaaZaZB5I12l9bb62ax0cTNkq G8lBBlM+ue2ox0zIJmXgu7oqstYWZ3Hd1TdN0x3ydxwxsNl6cC8+cw4eexx6rzfO4tAL nn2dQUvmT1FAP95e4X/QpxyyL1H0GUEQlNi+8HHQ76w/8G9T86aMul6Lh1yITj/Z86Gb jlWg== MIME-Version: 1.0 Received: by 10.60.12.42 with SMTP id v10mr59232oeb.131.1347974431873; Tue, 18 Sep 2012 06:20:31 -0700 (PDT) Received: by 10.60.6.230 with HTTP; Tue, 18 Sep 2012 06:20:31 -0700 (PDT) In-Reply-To: <505871D6.2060801@websitemanagers.com.au> References: <5051D0C5.5070600@websitemanagers.com.au> <1347609879.24226.148.camel@zakaz.uk.xensource.com> <50532CE9.5080601@websitemanagers.com.au> <1347629416.24226.208.camel@zakaz.uk.xensource.com> <505344E8.2030400@websitemanagers.com.au> <505871D6.2060801@websitemanagers.com.au> Date: Tue, 18 Sep 2012 20:20:31 +0700 Message-ID: From: "Fajar A. Nugraha" To: Adam Goryachev X-Gm-Message-State: ALoCoQl4FFM875GnlirmgC4KZFeB6iZV47//+OoKe5RMT5Nb3ZW14M2FEX+KH5xZ1Qs0jInoOclL Cc: xen-users@lists.xen.org Subject: Re: [Xen-users] Poor Windows 2003 + GPLPV performance compared to VMWare X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org On Tue, Sep 18, 2012 at 8:06 PM, Adam Goryachev wrote: > Could you suggest a "standard" tool which would allow me to test disk IO > performance (this is my initial suspicion for slow performance), and I'd suggest you try fio, with random read/write load, and data size at least twice the ammount of memory. > also CPU performance (I'm starting to suspect this too now) in both not sure about that one. And I'm not sure it would be useful either. What is your application, and what kind of load was it? If it was a synthetic load, then it's already a good benchmark tool. However if it's live load that you can't control, I suggest you try something like sysbench to test sql performance. I usually use sysbench with mysql and 1 million rows. -- Fajar _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Tue Sep 18 13:50:48 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Tue, 18 Sep 2012 13:50:48 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TDyBh-0007Cc-Cj; Tue, 18 Sep 2012 13:50:05 +0000 Received: from mail27.messagelabs.com ([193.109.254.147]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TDyBg-0007CE-2U for xen-users@lists.xen.org; Tue, 18 Sep 2012 13:50:04 +0000 X-Env-Sender: mailinglists@websitemanagers.com.au X-Msg-Ref: server-4.tower-27.messagelabs.com!1347976193!10900616!1 X-Originating-IP: [203.56.191.70] X-SpamReason: No, hits=0.5 required=7.0 tests=BODY_RANDOM_LONG X-StarScan-Received: X-StarScan-Version: 6.6.1.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 16260 invoked from network); 18 Sep 2012 13:49:57 -0000 Received: from unknown (HELO hammer.websitemanagers.com.au) (203.56.191.70) by server-4.tower-27.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 18 Sep 2012 13:49:57 -0000 Received: (qmail 2162 invoked by uid 1011); 18 Sep 2012 13:49:21 -0000 Received: from 220.233.87.52 by hammer (envelope-from , uid 1008) with qmail-scanner-1.24 (clamdscan: 0.97.3/15367. spamassassin: 3.3.1. Clear:RC:1(220.233.87.52):. Processed in 0.146929 secs); 18 Sep 2012 13:49:21 -0000 Received: from unknown (HELO ?192.168.2.90?) (220.233.87.52) by 0 with SMTP; 18 Sep 2012 13:49:21 -0000 Message-ID: <50587BE1.7040002@websitemanagers.com.au> Date: Tue, 18 Sep 2012 23:49:21 +1000 From: Adam Goryachev Organization: Website Managers User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:15.0) Gecko/20120827 Thunderbird/15.0 MIME-Version: 1.0 To: "Fajar A. Nugraha" References: <5051D0C5.5070600@websitemanagers.com.au> <1347609879.24226.148.camel@zakaz.uk.xensource.com> <50532CE9.5080601@websitemanagers.com.au> <1347629416.24226.208.camel@zakaz.uk.xensource.com> <505344E8.2030400@websitemanagers.com.au> <505871D6.2060801@websitemanagers.com.au> In-Reply-To: Cc: xen-users@lists.xen.org Subject: Re: [Xen-users] Poor Windows 2003 + GPLPV performance compared to VMWare X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org On 18/09/12 23:20, Fajar A. Nugraha wrote: > On Tue, Sep 18, 2012 at 8:06 PM, Adam Goryachev > wrote: >> Could you suggest a "standard" tool which would allow me to test disk IO >> performance (this is my initial suspicion for slow performance), and > > I'd suggest you try fio, with random read/write load, and data size at > least twice the ammount of memory. Thanks, will give this a go tomorrow night.. >> also CPU performance (I'm starting to suspect this too now) in both > > not sure about that one. And I'm not sure it would be useful either. > > What is your application, and what kind of load was it? If it was a > synthetic load, then it's already a good benchmark tool. However if > it's live load that you can't control, I suggest you try something > like sysbench to test sql performance. I usually use sysbench with > mysql and 1 million rows. The load is a "live" load, it uses some sort of Database (proprietary, non standard), and I am running a "maintenance" task of some sort which is used regularly to do backups of the system. A very similar task is also run when doing a "upgrade" to the program, etc. As far as I can tell, it is creating a new "database/table" and copying the current database/table into this new one. I assume there are the standard transactions/locking/etc associated. The values obtained from these processes vary significantly (as per normal) for each data type or table. My measurements are based on the speed of the first table in the pre-backup process. Normal backup time for this table would be about 10 minutes, I'm usually just letting it run for about 30 seconds to a minute, as the speed remains fairly constant throughout the process. So, I'm currently seeing speeds of approx 2500 transactions / sec, and "normal" should be around 7000 / sec (where normal is the speed of the same domU under vmware ESXi, and also comparable on a standalone physical machine (original, older machine). For now, I'm going to try and get service pack 2 installed before I proceed, if things are still looking bad after that, I'll proceed with doing some performance testing to see if I can pinpoint what is causing the slowdown (disk, cpu, ram, etc...) Thanks again for your help and suggestions. Regards, Adam -- Adam Goryachev Website Managers www.websitemanagers.com.au _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Tue Sep 18 13:50:48 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Tue, 18 Sep 2012 13:50:48 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TDyBh-0007Cc-Cj; Tue, 18 Sep 2012 13:50:05 +0000 Received: from mail27.messagelabs.com ([193.109.254.147]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TDyBg-0007CE-2U for xen-users@lists.xen.org; Tue, 18 Sep 2012 13:50:04 +0000 X-Env-Sender: mailinglists@websitemanagers.com.au X-Msg-Ref: server-4.tower-27.messagelabs.com!1347976193!10900616!1 X-Originating-IP: [203.56.191.70] X-SpamReason: No, hits=0.5 required=7.0 tests=BODY_RANDOM_LONG X-StarScan-Received: X-StarScan-Version: 6.6.1.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 16260 invoked from network); 18 Sep 2012 13:49:57 -0000 Received: from unknown (HELO hammer.websitemanagers.com.au) (203.56.191.70) by server-4.tower-27.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 18 Sep 2012 13:49:57 -0000 Received: (qmail 2162 invoked by uid 1011); 18 Sep 2012 13:49:21 -0000 Received: from 220.233.87.52 by hammer (envelope-from , uid 1008) with qmail-scanner-1.24 (clamdscan: 0.97.3/15367. spamassassin: 3.3.1. Clear:RC:1(220.233.87.52):. Processed in 0.146929 secs); 18 Sep 2012 13:49:21 -0000 Received: from unknown (HELO ?192.168.2.90?) (220.233.87.52) by 0 with SMTP; 18 Sep 2012 13:49:21 -0000 Message-ID: <50587BE1.7040002@websitemanagers.com.au> Date: Tue, 18 Sep 2012 23:49:21 +1000 From: Adam Goryachev Organization: Website Managers User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:15.0) Gecko/20120827 Thunderbird/15.0 MIME-Version: 1.0 To: "Fajar A. Nugraha" References: <5051D0C5.5070600@websitemanagers.com.au> <1347609879.24226.148.camel@zakaz.uk.xensource.com> <50532CE9.5080601@websitemanagers.com.au> <1347629416.24226.208.camel@zakaz.uk.xensource.com> <505344E8.2030400@websitemanagers.com.au> <505871D6.2060801@websitemanagers.com.au> In-Reply-To: Cc: xen-users@lists.xen.org Subject: Re: [Xen-users] Poor Windows 2003 + GPLPV performance compared to VMWare X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org On 18/09/12 23:20, Fajar A. Nugraha wrote: > On Tue, Sep 18, 2012 at 8:06 PM, Adam Goryachev > wrote: >> Could you suggest a "standard" tool which would allow me to test disk IO >> performance (this is my initial suspicion for slow performance), and > > I'd suggest you try fio, with random read/write load, and data size at > least twice the ammount of memory. Thanks, will give this a go tomorrow night.. >> also CPU performance (I'm starting to suspect this too now) in both > > not sure about that one. And I'm not sure it would be useful either. > > What is your application, and what kind of load was it? If it was a > synthetic load, then it's already a good benchmark tool. However if > it's live load that you can't control, I suggest you try something > like sysbench to test sql performance. I usually use sysbench with > mysql and 1 million rows. The load is a "live" load, it uses some sort of Database (proprietary, non standard), and I am running a "maintenance" task of some sort which is used regularly to do backups of the system. A very similar task is also run when doing a "upgrade" to the program, etc. As far as I can tell, it is creating a new "database/table" and copying the current database/table into this new one. I assume there are the standard transactions/locking/etc associated. The values obtained from these processes vary significantly (as per normal) for each data type or table. My measurements are based on the speed of the first table in the pre-backup process. Normal backup time for this table would be about 10 minutes, I'm usually just letting it run for about 30 seconds to a minute, as the speed remains fairly constant throughout the process. So, I'm currently seeing speeds of approx 2500 transactions / sec, and "normal" should be around 7000 / sec (where normal is the speed of the same domU under vmware ESXi, and also comparable on a standalone physical machine (original, older machine). For now, I'm going to try and get service pack 2 installed before I proceed, if things are still looking bad after that, I'll proceed with doing some performance testing to see if I can pinpoint what is causing the slowdown (disk, cpu, ram, etc...) Thanks again for your help and suggestions. Regards, Adam -- Adam Goryachev Website Managers www.websitemanagers.com.au _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Wed Sep 19 02:41:32 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Wed, 19 Sep 2012 02:41:32 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TEACF-0000Vu-MA; Wed, 19 Sep 2012 02:39:27 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TEACE-0000Vk-I2 for xen-users@lists.xen.org; Wed, 19 Sep 2012 02:39:26 +0000 Received: from [85.158.137.99:19409] by server-10.bemta-3.messagelabs.com id 87/B9-10411-D5039505; Wed, 19 Sep 2012 02:39:25 +0000 X-Env-Sender: matthiasblankenhaus@yahoo.com X-Msg-Ref: server-2.tower-217.messagelabs.com!1348022364!18114712!1 X-Originating-IP: [98.139.91.90] X-SpamReason: No, hits=0.9 required=7.0 tests=HTML_20_30,HTML_MESSAGE, ML_RADAR_SPEW_LINKS_12,ML_RADAR_SPEW_LINKS_14,spamassassin: X-StarScan-Received: X-StarScan-Version: 6.6.1.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 6388 invoked from network); 19 Sep 2012 02:39:24 -0000 Received: from nm20.bullet.mail.sp2.yahoo.com (HELO nm20.bullet.mail.sp2.yahoo.com) (98.139.91.90) by server-2.tower-217.messagelabs.com with SMTP; 19 Sep 2012 02:39:24 -0000 Received: from [98.139.91.61] by nm20.bullet.mail.sp2.yahoo.com with NNFMP; 19 Sep 2012 02:39:23 -0000 Received: from [98.139.91.24] by tm1.bullet.mail.sp2.yahoo.com with NNFMP; 19 Sep 2012 02:39:23 -0000 Received: from [127.0.0.1] by omp1024.mail.sp2.yahoo.com with NNFMP; 19 Sep 2012 02:39:23 -0000 X-Yahoo-Newman-Property: ymail-3 X-Yahoo-Newman-Id: 472533.85122.bm@omp1024.mail.sp2.yahoo.com Received: (qmail 68434 invoked by uid 60001); 19 Sep 2012 02:39:23 -0000 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.com; s=s1024; t=1348022363; bh=WdXmZM3NDtHYjN83wKDYOhCTBtTAYJ/AJ5ZnQLLOzCQ=; h=X-YMail-OSG:Received:X-Mailer:Message-ID:Date:From:Reply-To:Subject:To:MIME-Version:Content-Type; b=VWJpZHInh/2ZQBYSu4wcHG0/W1X2GEWHLx4D9yLW0KPv4nNuVVp3GNicbxjXhijStypqac6gIuQRai0VY7njVrLuNDgCMw1JNF0wuxjNarWVLICfxhdNTNTY0SB5aGAtX2xPDyRJ7k9mRDXTXhcYMgidBqqsPdoSKZb0TzwMPB8= DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com; h=X-YMail-OSG:Received:X-Mailer:Message-ID:Date:From:Reply-To:Subject:To:MIME-Version:Content-Type; b=SKTX/OA3K5YmtXZs9r6uSCPe0I+kWeGaqZ4VkaI7sFe/isA5nMFpHV0oapL8d54XE3iBYMZPUsiAtmrxn++hjDIm00sjjiPJd6aqBXuLWvYUHjVvmqbW+YUTVrnvN2ph0YstKo7+wnWdgJ91No8LEaDpPX2R4QsGhdOOC/7nyiQ=; X-YMail-OSG: PksH3_0VM1nwI1Ug27mCoEPXUF3KiLtoRpcnmxoYnTqLA3l vUhOJgwv7FGrEBTBrMK_pUzJqp5nCkSZxYFXBcnW.9kHGXLePaR6qdPNgk3B VokY_8WB74R3XAj75qKRfgdgXXB.XiBvMwImIfkhJb2dYlm4ZaTibxIMOo18 fl0ux3Ucru0PKciGS4CcjCYoVaCRrK.SBesFMFOc0WBHcbjZcv.8TNRuEbwE Dece1CQBZvNsFhrRVtSY9HTu5lcrGViZRIrEj38inGKeWiqKZTv.S2l.jVOh sRtesMFAMw3p7McdR5T8uH5G4LB1hOlLRf4r1eBkXGiEmKZxSe.eFKobddOc 7EsCU1D1iLbdt6DZ3FYCG4MPY7ARmGvqr.bwsIPf7JWlnJXi6PtGncZAyXwk yH.OmTHxu8Q3DxoB8MRnTOR.HMZMiRhpS.u7M45AEC.VzjxdlOXr7puQCAD6 ZNS_HyoNj_epTTacb2sP4wBd4aY946Q-- Received: from [143.127.128.10] by web39403.mail.mud.yahoo.com via HTTP; Tue, 18 Sep 2012 19:39:22 PDT X-Mailer: YahooMailWebService/0.8.121.416 Message-ID: <1348022362.41972.YahooMailNeo@web39403.mail.mud.yahoo.com> Date: Tue, 18 Sep 2012 19:39:22 -0700 (PDT) From: Matthias Blankenhaus To: "xen-users@lists.xen.org" MIME-Version: 1.0 Subject: [Xen-users] Can't boot PV from qcow image X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list Reply-To: Matthias Blankenhaus List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============2041575950849110008==" Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org --===============2041575950849110008== Content-Type: multipart/alternative; boundary="908107500-1803031041-1348022362=:41972" --908107500-1803031041-1348022362=:41972 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: quoted-printable Howdy !=0A=0AI have been trying for more than 2 days to work this out witho= ut success. While I am able to identify a qcow image as a block device with= in the=0Aguest, so far I can not use a qcow or qcow2 images as a block devi= ce due to IO errors.=A0 As a reference, I am able to mount raw images via l= oopback device through DOM0.=0A=0AHere is my setting:=0ADOM0=0A- Xen 4.2.0= =0A- Debian wheezy with 3.1.0-rc8 / 64bit [without blktap2 patch]=0A- nfs m= ounted guest images=0A=0ADOM-U=0A- PV=0A- CentOS 6.2 with 2.6.33.20.x86_64 = /, no initrd=0A- no grub=0A- Xen guest disk config:=0Adisk =3D ['format=3Dr= aw,vdev=3Dxvda,target=3D/dev/loop0','tap:qcow:/var/lib/xen-images/21339039-= df03-43e2-b94f-2b600e2492b2/rootfs.qcow,xvdb,w'=0A=0AWhen attempting to acc= ess the qcow backed device (xvdb) I get these errors:=0A=0A# less /var/log/= messages=0A...=0ASep 19 01:26:15 kernel: [=A0 189.596610] Buffer I/O error = on device xvdb, logical block 163967=0ASep 19 01:26:15 kernel: [=A0 189.936= 239] end_request: I/O error, dev xvdb, sector 1311744=0ASep 19 01:26:15 ker= nel: [=A0 189.940237] Buffer I/O error on device xvdb, logical block 163968= =0ASep 19 01:26:16 kernel: [=A0 190.276228] end_request: I/O error, dev xvd= b, sector 1572864=0A...=0A=0AMeanwhile, on DOM0 I see the following output = in the process tree:=0A...=0Aroot=A0=A0=A0=A0=A0=A0 911=A0=A0=A0=A0 2=A0 0 = 01:49 ?=A0=A0=A0=A0=A0=A0=A0 00:00:00 [blkback.59.xvda]=0Aroot=A0=A0=A0=A0= =A0=A0 848=A0=A0=A0=A0 1=A0 0 01:49 ?=A0=A0=A0=A0=A0=A0=A0 00:00:10 /usr/li= b/xen/bin/qemu-system-i386 -xen-domid 59 -chardev socket,id=3Dlib=0A=0AThe = block back-end kernel thread is backing my rootfs which is mapped to a loop= back device on DOM0.=A0 I think qemu was launched to=0Aback the qcow device= .=A0 Thus, this matches my conceptional understanding of how things should = work.=0A=0AUltimately, I am looking for a way to boot PVs from disk image u= sing Xen 4.2.=A0 I was able to do this under Xen 4.1.x using a raw disk ima= ge in conjunction with the tap:aio option for the guests' disk spec and wit= hout using a loopback mount on DOM0.=0A=0AYour help is much appreciated,=0A= Matthias --908107500-1803031041-1348022362=:41972 Content-Type: text/html; charset=iso-8859-1 Content-Transfer-Encoding: quoted-printable
Howdy !

I have= been trying for more than 2 days to work this out without success. While I= am able to identify a qcow image as a block device within the
guest, so= far I can not use a qcow or qcow2 images as a block device due to IO error= s.  As a reference, I am able to mount raw images via loopback device = through DOM0.

Here is my setting:
DOM0
- Xen 4.2.0
- Debian= wheezy with 3.1.0-rc8 / 64bit [without blktap2 patch]
- nfs mounted gue= st images

DOM-U
- PV
- CentOS 6.2 with 2.6.33.20.x86_64 /, no = initrd
- no grub
- Xen guest disk config:
disk =3D ['format=3Draw,= vdev=3Dxvda,target=3D/dev/loop0','tap:qcow:/var/lib/xen-images/21339039-df0= 3-43e2-b94f-2b600e2492b2/rootfs.qcow,xvdb,w'

When attempting to acce= ss the qcow backed device (xvdb) I get these errors:

# less /var/log/messages
...
Sep 19 01:26:15 kernel: [  189.596610] Bu= ffer I/O error on device xvdb, logical block 163967
Sep 19 01:26:15 kern= el: [  189.936239] end_request: I/O error, dev xvdb, sector 1311744Sep 19 01:26:15 kernel: [  189.940237] Buffer I/O error on device xvd= b, logical block 163968
Sep 19 01:26:16 kernel: [  190.276228] end_= request: I/O error, dev xvdb, sector 1572864
...

Meanwhile, on DO= M0 I see the following output in the process tree:
...
root &nbs= p;     911     2  0 01:49 ?&nb= sp;       00:00:00 [blkback.59.xvda]
root&= nbsp;      848     1  0 0= 1:49 ?        00:00:10 /usr/lib/xen/bin/= qemu-system-i386 -xen-domid 59 -chardev socket,id=3Dlib

The block ba= ck-end kernel thread is backing my rootfs which is mapped to a loopback device on DOM0.  I think qemu was launched to
back the qc= ow device.  Thus, this matches my conceptional understanding of how th= ings should work.

Ultimately, I am looking for a way to boot PVs fro= m disk image using Xen 4.2.  I was able to do this under Xen 4.1.x usi= ng a raw disk image in conjunction with the tap:aio option for the guests' = disk spec and without using a loopback mount on DOM0.

Your help is m= uch appreciated,
Matthias

--908107500-1803031041-1348022362=:41972-- --===============2041575950849110008== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users --===============2041575950849110008==-- From xen-users-bounces@lists.xen.org Wed Sep 19 02:41:32 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Wed, 19 Sep 2012 02:41:32 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TEACF-0000Vu-MA; Wed, 19 Sep 2012 02:39:27 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TEACE-0000Vk-I2 for xen-users@lists.xen.org; Wed, 19 Sep 2012 02:39:26 +0000 Received: from [85.158.137.99:19409] by server-10.bemta-3.messagelabs.com id 87/B9-10411-D5039505; Wed, 19 Sep 2012 02:39:25 +0000 X-Env-Sender: matthiasblankenhaus@yahoo.com X-Msg-Ref: server-2.tower-217.messagelabs.com!1348022364!18114712!1 X-Originating-IP: [98.139.91.90] X-SpamReason: No, hits=0.9 required=7.0 tests=HTML_20_30,HTML_MESSAGE, ML_RADAR_SPEW_LINKS_12,ML_RADAR_SPEW_LINKS_14,spamassassin: X-StarScan-Received: X-StarScan-Version: 6.6.1.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 6388 invoked from network); 19 Sep 2012 02:39:24 -0000 Received: from nm20.bullet.mail.sp2.yahoo.com (HELO nm20.bullet.mail.sp2.yahoo.com) (98.139.91.90) by server-2.tower-217.messagelabs.com with SMTP; 19 Sep 2012 02:39:24 -0000 Received: from [98.139.91.61] by nm20.bullet.mail.sp2.yahoo.com with NNFMP; 19 Sep 2012 02:39:23 -0000 Received: from [98.139.91.24] by tm1.bullet.mail.sp2.yahoo.com with NNFMP; 19 Sep 2012 02:39:23 -0000 Received: from [127.0.0.1] by omp1024.mail.sp2.yahoo.com with NNFMP; 19 Sep 2012 02:39:23 -0000 X-Yahoo-Newman-Property: ymail-3 X-Yahoo-Newman-Id: 472533.85122.bm@omp1024.mail.sp2.yahoo.com Received: (qmail 68434 invoked by uid 60001); 19 Sep 2012 02:39:23 -0000 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.com; s=s1024; t=1348022363; bh=WdXmZM3NDtHYjN83wKDYOhCTBtTAYJ/AJ5ZnQLLOzCQ=; h=X-YMail-OSG:Received:X-Mailer:Message-ID:Date:From:Reply-To:Subject:To:MIME-Version:Content-Type; b=VWJpZHInh/2ZQBYSu4wcHG0/W1X2GEWHLx4D9yLW0KPv4nNuVVp3GNicbxjXhijStypqac6gIuQRai0VY7njVrLuNDgCMw1JNF0wuxjNarWVLICfxhdNTNTY0SB5aGAtX2xPDyRJ7k9mRDXTXhcYMgidBqqsPdoSKZb0TzwMPB8= DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com; h=X-YMail-OSG:Received:X-Mailer:Message-ID:Date:From:Reply-To:Subject:To:MIME-Version:Content-Type; b=SKTX/OA3K5YmtXZs9r6uSCPe0I+kWeGaqZ4VkaI7sFe/isA5nMFpHV0oapL8d54XE3iBYMZPUsiAtmrxn++hjDIm00sjjiPJd6aqBXuLWvYUHjVvmqbW+YUTVrnvN2ph0YstKo7+wnWdgJ91No8LEaDpPX2R4QsGhdOOC/7nyiQ=; X-YMail-OSG: PksH3_0VM1nwI1Ug27mCoEPXUF3KiLtoRpcnmxoYnTqLA3l vUhOJgwv7FGrEBTBrMK_pUzJqp5nCkSZxYFXBcnW.9kHGXLePaR6qdPNgk3B VokY_8WB74R3XAj75qKRfgdgXXB.XiBvMwImIfkhJb2dYlm4ZaTibxIMOo18 fl0ux3Ucru0PKciGS4CcjCYoVaCRrK.SBesFMFOc0WBHcbjZcv.8TNRuEbwE Dece1CQBZvNsFhrRVtSY9HTu5lcrGViZRIrEj38inGKeWiqKZTv.S2l.jVOh sRtesMFAMw3p7McdR5T8uH5G4LB1hOlLRf4r1eBkXGiEmKZxSe.eFKobddOc 7EsCU1D1iLbdt6DZ3FYCG4MPY7ARmGvqr.bwsIPf7JWlnJXi6PtGncZAyXwk yH.OmTHxu8Q3DxoB8MRnTOR.HMZMiRhpS.u7M45AEC.VzjxdlOXr7puQCAD6 ZNS_HyoNj_epTTacb2sP4wBd4aY946Q-- Received: from [143.127.128.10] by web39403.mail.mud.yahoo.com via HTTP; Tue, 18 Sep 2012 19:39:22 PDT X-Mailer: YahooMailWebService/0.8.121.416 Message-ID: <1348022362.41972.YahooMailNeo@web39403.mail.mud.yahoo.com> Date: Tue, 18 Sep 2012 19:39:22 -0700 (PDT) From: Matthias Blankenhaus To: "xen-users@lists.xen.org" MIME-Version: 1.0 Subject: [Xen-users] Can't boot PV from qcow image X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list Reply-To: Matthias Blankenhaus List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============2041575950849110008==" Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org --===============2041575950849110008== Content-Type: multipart/alternative; boundary="908107500-1803031041-1348022362=:41972" --908107500-1803031041-1348022362=:41972 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: quoted-printable Howdy !=0A=0AI have been trying for more than 2 days to work this out witho= ut success. While I am able to identify a qcow image as a block device with= in the=0Aguest, so far I can not use a qcow or qcow2 images as a block devi= ce due to IO errors.=A0 As a reference, I am able to mount raw images via l= oopback device through DOM0.=0A=0AHere is my setting:=0ADOM0=0A- Xen 4.2.0= =0A- Debian wheezy with 3.1.0-rc8 / 64bit [without blktap2 patch]=0A- nfs m= ounted guest images=0A=0ADOM-U=0A- PV=0A- CentOS 6.2 with 2.6.33.20.x86_64 = /, no initrd=0A- no grub=0A- Xen guest disk config:=0Adisk =3D ['format=3Dr= aw,vdev=3Dxvda,target=3D/dev/loop0','tap:qcow:/var/lib/xen-images/21339039-= df03-43e2-b94f-2b600e2492b2/rootfs.qcow,xvdb,w'=0A=0AWhen attempting to acc= ess the qcow backed device (xvdb) I get these errors:=0A=0A# less /var/log/= messages=0A...=0ASep 19 01:26:15 kernel: [=A0 189.596610] Buffer I/O error = on device xvdb, logical block 163967=0ASep 19 01:26:15 kernel: [=A0 189.936= 239] end_request: I/O error, dev xvdb, sector 1311744=0ASep 19 01:26:15 ker= nel: [=A0 189.940237] Buffer I/O error on device xvdb, logical block 163968= =0ASep 19 01:26:16 kernel: [=A0 190.276228] end_request: I/O error, dev xvd= b, sector 1572864=0A...=0A=0AMeanwhile, on DOM0 I see the following output = in the process tree:=0A...=0Aroot=A0=A0=A0=A0=A0=A0 911=A0=A0=A0=A0 2=A0 0 = 01:49 ?=A0=A0=A0=A0=A0=A0=A0 00:00:00 [blkback.59.xvda]=0Aroot=A0=A0=A0=A0= =A0=A0 848=A0=A0=A0=A0 1=A0 0 01:49 ?=A0=A0=A0=A0=A0=A0=A0 00:00:10 /usr/li= b/xen/bin/qemu-system-i386 -xen-domid 59 -chardev socket,id=3Dlib=0A=0AThe = block back-end kernel thread is backing my rootfs which is mapped to a loop= back device on DOM0.=A0 I think qemu was launched to=0Aback the qcow device= .=A0 Thus, this matches my conceptional understanding of how things should = work.=0A=0AUltimately, I am looking for a way to boot PVs from disk image u= sing Xen 4.2.=A0 I was able to do this under Xen 4.1.x using a raw disk ima= ge in conjunction with the tap:aio option for the guests' disk spec and wit= hout using a loopback mount on DOM0.=0A=0AYour help is much appreciated,=0A= Matthias --908107500-1803031041-1348022362=:41972 Content-Type: text/html; charset=iso-8859-1 Content-Transfer-Encoding: quoted-printable
Howdy !

I have= been trying for more than 2 days to work this out without success. While I= am able to identify a qcow image as a block device within the
guest, so= far I can not use a qcow or qcow2 images as a block device due to IO error= s.  As a reference, I am able to mount raw images via loopback device = through DOM0.

Here is my setting:
DOM0
- Xen 4.2.0
- Debian= wheezy with 3.1.0-rc8 / 64bit [without blktap2 patch]
- nfs mounted gue= st images

DOM-U
- PV
- CentOS 6.2 with 2.6.33.20.x86_64 /, no = initrd
- no grub
- Xen guest disk config:
disk =3D ['format=3Draw,= vdev=3Dxvda,target=3D/dev/loop0','tap:qcow:/var/lib/xen-images/21339039-df0= 3-43e2-b94f-2b600e2492b2/rootfs.qcow,xvdb,w'

When attempting to acce= ss the qcow backed device (xvdb) I get these errors:

# less /var/log/messages
...
Sep 19 01:26:15 kernel: [  189.596610] Bu= ffer I/O error on device xvdb, logical block 163967
Sep 19 01:26:15 kern= el: [  189.936239] end_request: I/O error, dev xvdb, sector 1311744Sep 19 01:26:15 kernel: [  189.940237] Buffer I/O error on device xvd= b, logical block 163968
Sep 19 01:26:16 kernel: [  190.276228] end_= request: I/O error, dev xvdb, sector 1572864
...

Meanwhile, on DO= M0 I see the following output in the process tree:
...
root &nbs= p;     911     2  0 01:49 ?&nb= sp;       00:00:00 [blkback.59.xvda]
root&= nbsp;      848     1  0 0= 1:49 ?        00:00:10 /usr/lib/xen/bin/= qemu-system-i386 -xen-domid 59 -chardev socket,id=3Dlib

The block ba= ck-end kernel thread is backing my rootfs which is mapped to a loopback device on DOM0.  I think qemu was launched to
back the qc= ow device.  Thus, this matches my conceptional understanding of how th= ings should work.

Ultimately, I am looking for a way to boot PVs fro= m disk image using Xen 4.2.  I was able to do this under Xen 4.1.x usi= ng a raw disk image in conjunction with the tap:aio option for the guests' = disk spec and without using a loopback mount on DOM0.

Your help is m= uch appreciated,
Matthias

--908107500-1803031041-1348022362=:41972-- --===============2041575950849110008== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users --===============2041575950849110008==-- From xen-users-bounces@lists.xen.org Wed Sep 19 08:26:43 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Wed, 19 Sep 2012 08:26:43 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TEFaS-0005HA-3E; Wed, 19 Sep 2012 08:24:48 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TEFaP-0005H2-K3 for xen-users@lists.xen.org; Wed, 19 Sep 2012 08:24:46 +0000 Received: from [85.158.139.211:57447] by server-1.bemta-5.messagelabs.com id 27/9A-32692-C4189505; Wed, 19 Sep 2012 08:24:44 +0000 X-Env-Sender: Ian.Campbell@citrix.com X-Msg-Ref: server-10.tower-206.messagelabs.com!1348043083!19098599!1 X-Originating-IP: [62.200.22.115] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogNjIuMjAwLjIyLjExNSA9PiAxMTAwNzc=\n X-StarScan-Received: X-StarScan-Version: 6.6.1.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 27411 invoked from network); 19 Sep 2012 08:24:44 -0000 Received: from smtp.eu.citrix.com (HELO SMTP.EU.CITRIX.COM) (62.200.22.115) by server-10.tower-206.messagelabs.com with RC4-SHA encrypted SMTP; 19 Sep 2012 08:24:44 -0000 X-IronPort-AV: E=Sophos;i="4.80,447,1344211200"; d="scan'208";a="14623560" Received: from lonpmailmx01.citrite.net ([10.30.203.162]) by LONPIPO01.EU.CITRIX.COM with ESMTP/TLS/RC4-MD5; 19 Sep 2012 08:24:43 +0000 Received: from [10.80.2.42] (10.80.2.42) by LONPMAILMX01.citrite.net (10.30.203.162) with Microsoft SMTP Server id 8.3.279.1; Wed, 19 Sep 2012 09:24:43 +0100 Message-ID: <1348043081.14977.72.camel@zakaz.uk.xensource.com> From: Ian Campbell To: Adam Goryachev Date: Wed, 19 Sep 2012 09:24:41 +0100 In-Reply-To: <505867EA.5060403@websitemanagers.com.au> References: <5051D0C5.5070600@websitemanagers.com.au> <1347609879.24226.148.camel@zakaz.uk.xensource.com> <50532CE9.5080601@websitemanagers.com.au> <1347629416.24226.208.camel@zakaz.uk.xensource.com> <1347872072.14977.22.camel@zakaz.uk.xensource.com> <505867EA.5060403@websitemanagers.com.au> Organization: Citrix Systems, Inc. X-Mailer: Evolution 3.4.3-1 MIME-Version: 1.0 Cc: "xen-users@lists.xen.org" Subject: Re: [Xen-users] Poor Windows 2003 + GPLPV performance compared to VMWare X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org On Tue, 2012-09-18 at 13:24 +0100, Adam Goryachev wrote: > On 17/09/12 18:54, Ian Campbell wrote: > > On Fri, 2012-09-14 at 14:30 +0100, Ian Campbell wrote: > >>>> Does your system have any NUMA properties? > >>> I don't really understand this question.... is there a simple method to > >>> check? It is a AMD Phenom(tm) II X6 1100T Processor on a reasonable > >>> desktop motherboard, nothing fancy.... > > I don't have a NUMA system to hand, but on my non-NUMA system I see in > > the logs: > > (XEN) No NUMA configuration found > > > > You should see that or something more informative. > "xm dmesg|grep -i numa" produces no output, so again, I still have no > definitive answer to this. > > Actually, got it... : > dmesg|grep -i numa > [ 0.000000] Scanning NUMA topology in Northbridge 24 > [ 0.000000] No NUMA configuration found > > That is not xen, that is the normal kernel... or perhaps xen has hidden > the numa config from linux... I'm really not sure... > > Also at least in 4.2 "xl info -n" gives some details. Not sure if xm has > > the same option? > This is getting better. > xm info -n > numa_info : none > > Amongst lots of other interesting information. > > So, seems pretty definitive that there is no numa support here. > > Is this still relevant to the diagnosis of very slow windows domu? No, I was thinking of issues like front/backend on different NUMA nodes and the like. Ian. _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Wed Sep 19 08:26:43 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Wed, 19 Sep 2012 08:26:43 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TEFaS-0005HA-3E; Wed, 19 Sep 2012 08:24:48 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TEFaP-0005H2-K3 for xen-users@lists.xen.org; Wed, 19 Sep 2012 08:24:46 +0000 Received: from [85.158.139.211:57447] by server-1.bemta-5.messagelabs.com id 27/9A-32692-C4189505; Wed, 19 Sep 2012 08:24:44 +0000 X-Env-Sender: Ian.Campbell@citrix.com X-Msg-Ref: server-10.tower-206.messagelabs.com!1348043083!19098599!1 X-Originating-IP: [62.200.22.115] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogNjIuMjAwLjIyLjExNSA9PiAxMTAwNzc=\n X-StarScan-Received: X-StarScan-Version: 6.6.1.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 27411 invoked from network); 19 Sep 2012 08:24:44 -0000 Received: from smtp.eu.citrix.com (HELO SMTP.EU.CITRIX.COM) (62.200.22.115) by server-10.tower-206.messagelabs.com with RC4-SHA encrypted SMTP; 19 Sep 2012 08:24:44 -0000 X-IronPort-AV: E=Sophos;i="4.80,447,1344211200"; d="scan'208";a="14623560" Received: from lonpmailmx01.citrite.net ([10.30.203.162]) by LONPIPO01.EU.CITRIX.COM with ESMTP/TLS/RC4-MD5; 19 Sep 2012 08:24:43 +0000 Received: from [10.80.2.42] (10.80.2.42) by LONPMAILMX01.citrite.net (10.30.203.162) with Microsoft SMTP Server id 8.3.279.1; Wed, 19 Sep 2012 09:24:43 +0100 Message-ID: <1348043081.14977.72.camel@zakaz.uk.xensource.com> From: Ian Campbell To: Adam Goryachev Date: Wed, 19 Sep 2012 09:24:41 +0100 In-Reply-To: <505867EA.5060403@websitemanagers.com.au> References: <5051D0C5.5070600@websitemanagers.com.au> <1347609879.24226.148.camel@zakaz.uk.xensource.com> <50532CE9.5080601@websitemanagers.com.au> <1347629416.24226.208.camel@zakaz.uk.xensource.com> <1347872072.14977.22.camel@zakaz.uk.xensource.com> <505867EA.5060403@websitemanagers.com.au> Organization: Citrix Systems, Inc. X-Mailer: Evolution 3.4.3-1 MIME-Version: 1.0 Cc: "xen-users@lists.xen.org" Subject: Re: [Xen-users] Poor Windows 2003 + GPLPV performance compared to VMWare X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org On Tue, 2012-09-18 at 13:24 +0100, Adam Goryachev wrote: > On 17/09/12 18:54, Ian Campbell wrote: > > On Fri, 2012-09-14 at 14:30 +0100, Ian Campbell wrote: > >>>> Does your system have any NUMA properties? > >>> I don't really understand this question.... is there a simple method to > >>> check? It is a AMD Phenom(tm) II X6 1100T Processor on a reasonable > >>> desktop motherboard, nothing fancy.... > > I don't have a NUMA system to hand, but on my non-NUMA system I see in > > the logs: > > (XEN) No NUMA configuration found > > > > You should see that or something more informative. > "xm dmesg|grep -i numa" produces no output, so again, I still have no > definitive answer to this. > > Actually, got it... : > dmesg|grep -i numa > [ 0.000000] Scanning NUMA topology in Northbridge 24 > [ 0.000000] No NUMA configuration found > > That is not xen, that is the normal kernel... or perhaps xen has hidden > the numa config from linux... I'm really not sure... > > Also at least in 4.2 "xl info -n" gives some details. Not sure if xm has > > the same option? > This is getting better. > xm info -n > numa_info : none > > Amongst lots of other interesting information. > > So, seems pretty definitive that there is no numa support here. > > Is this still relevant to the diagnosis of very slow windows domu? No, I was thinking of issues like front/backend on different NUMA nodes and the like. Ian. _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Wed Sep 19 08:43:04 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Wed, 19 Sep 2012 08:43:04 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TEFqo-0005nq-C2; Wed, 19 Sep 2012 08:41:42 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TEFqm-0005nl-HW for xen-users@lists.xen.org; Wed, 19 Sep 2012 08:41:40 +0000 Received: from [85.158.143.35:35155] by server-3.bemta-4.messagelabs.com id A5/19-10986-34589505; Wed, 19 Sep 2012 08:41:39 +0000 X-Env-Sender: Ian.Campbell@citrix.com X-Msg-Ref: server-11.tower-21.messagelabs.com!1348044097!12127773!1 X-Originating-IP: [62.200.22.115] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogNjIuMjAwLjIyLjExNSA9PiAxMTAwNzc=\n X-StarScan-Received: X-StarScan-Version: 6.6.1.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 31378 invoked from network); 19 Sep 2012 08:41:38 -0000 Received: from smtp.ctxuk.citrix.com (HELO SMTP.EU.CITRIX.COM) (62.200.22.115) by server-11.tower-21.messagelabs.com with RC4-SHA encrypted SMTP; 19 Sep 2012 08:41:38 -0000 X-IronPort-AV: E=Sophos;i="4.80,447,1344211200"; d="scan'208";a="14624035" Received: from lonpmailmx01.citrite.net ([10.30.203.162]) by LONPIPO01.EU.CITRIX.COM with ESMTP/TLS/RC4-MD5; 19 Sep 2012 08:41:37 +0000 Received: from [10.80.2.42] (10.80.2.42) by LONPMAILMX01.citrite.net (10.30.203.162) with Microsoft SMTP Server id 8.3.279.1; Wed, 19 Sep 2012 09:41:37 +0100 Message-ID: <1348044096.14977.84.camel@zakaz.uk.xensource.com> From: Ian Campbell To: Adam Goryachev Date: Wed, 19 Sep 2012 09:41:36 +0100 In-Reply-To: <505871D6.2060801@websitemanagers.com.au> References: <5051D0C5.5070600@websitemanagers.com.au> <1347609879.24226.148.camel@zakaz.uk.xensource.com> <50532CE9.5080601@websitemanagers.com.au> <1347629416.24226.208.camel@zakaz.uk.xensource.com> <505344E8.2030400@websitemanagers.com.au> <505871D6.2060801@websitemanagers.com.au> Organization: Citrix Systems, Inc. X-Mailer: Evolution 3.4.3-1 MIME-Version: 1.0 Cc: "xen-users@lists.xen.org" Subject: Re: [Xen-users] Poor Windows 2003 + GPLPV performance compared to VMWare X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org On Tue, 2012-09-18 at 14:06 +0100, Adam Goryachev wrote: > On 15/09/12 00:53, Adam Goryachev wrote: > > On 14/09/12 23:30, Ian Campbell wrote: > > > >>>>> device_model = '/usr/lib/xen-default/bin/qemu-dm' > >>>>> localtime = 1 > >>>>> name = "vm1" > >>>>> cpus = "2,3,4,5" # Which physical CPU's to allow > >>>> Have you pinned dom0 to use pCPU 1 and/p pCPUs > 6? > >>> No, how should I pin dom0 to cpu0 ? > >> dom0_vcpus_pin as described in > >> http://xenbits.xen.org/docs/4.2-testing/misc/xen-command-line.html > > Thanks, I'll need to reboot the dom0 to apply this, will do as soon as > > this current scheduled task is complete. > OK, I have pinned dom0 to cpu0, and this had no effect on performance. > >> You have: > >> cpus = "2,3,4,5" > >> which means "let all the guests VCPUs run on any of PCPUS 2-5". > >> > >> It sounds like what you are asking for above is: > >> cpus = [2,3,4,5] > >> Which forces guest vcpu0=>pcpu=2, 1=>3, 2=>4 and 3=>5. > >> > >> Subtle I agree. > > Ugh... ok, I'll give that a try. BTW, it would seem this is different > > from xen 4.0 (from debian stable) where it seems to magically do what I > > meant to say, or I'm just lucky on those machines :) > Actually, the above syntax doesn't work: > cpus = [2,3,4,5] # Which physical CPU's to allow > Error: 'int' object has no attribute 'split' Is it ["2","3"...] then I wonder? > Once I reverted to: > cpus = "2,3,4,5" > I can then boot again, but on reboot I get this: > xm vcpu-list > Name ID VCPU CPU State Time(s) CPU > Affinity > Domain-0 0 0 0 r-- 148.9 0 > cobweb 6 0 5 --- 0.5 2-5 > cobweb 6 1 - --p 0.0 2-5 > cobweb 6 2 - --p 0.0 2-5 > cobweb 6 3 - --p 0.0 2-5 > > So it isn't pinning each vcpu to a specific cpu... but I suppose it > should be smart enough to do it well anyway... > Performance is still at the same level. To be honest I wouldn't expect it to make much difference at this stage. I notice the state is "--p" for all but VCPU0 -- which means they are paused. It's probably just that you ran the xm vcpu-list before Windows booted as far as brining up secondary CPUs but it would be worth checking that Windows is actually bringing up / using all the CPUs! Once the VM is fully booted then the state for each vcpu should either be "r--" (running) or "-b-" (currently blocked). I presume something like Windows task manager will also confirm that all the CPUs are in use. > I'm really at a bit of a loss on where to go from here.... The standard > performance improvements don't seem to make any difference at all, and > I'm running out of ideas.... > > Could you suggest a "standard" tool which would allow me to test disk IO > performance (this is my initial suspicion for slow performance), and > also CPU performance (I'm starting to suspect this too now) in both > windows (domU), linux (domU I can create one for testing) and Linux > (dom0). Then I can see where performance is lost (CPU/disk) and at what > layer (dom0/domU) etc... Fajar's suggestion of fio is a good one. Ian. _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Wed Sep 19 08:43:04 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Wed, 19 Sep 2012 08:43:04 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TEFqo-0005nq-C2; Wed, 19 Sep 2012 08:41:42 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TEFqm-0005nl-HW for xen-users@lists.xen.org; Wed, 19 Sep 2012 08:41:40 +0000 Received: from [85.158.143.35:35155] by server-3.bemta-4.messagelabs.com id A5/19-10986-34589505; Wed, 19 Sep 2012 08:41:39 +0000 X-Env-Sender: Ian.Campbell@citrix.com X-Msg-Ref: server-11.tower-21.messagelabs.com!1348044097!12127773!1 X-Originating-IP: [62.200.22.115] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogNjIuMjAwLjIyLjExNSA9PiAxMTAwNzc=\n X-StarScan-Received: X-StarScan-Version: 6.6.1.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 31378 invoked from network); 19 Sep 2012 08:41:38 -0000 Received: from smtp.ctxuk.citrix.com (HELO SMTP.EU.CITRIX.COM) (62.200.22.115) by server-11.tower-21.messagelabs.com with RC4-SHA encrypted SMTP; 19 Sep 2012 08:41:38 -0000 X-IronPort-AV: E=Sophos;i="4.80,447,1344211200"; d="scan'208";a="14624035" Received: from lonpmailmx01.citrite.net ([10.30.203.162]) by LONPIPO01.EU.CITRIX.COM with ESMTP/TLS/RC4-MD5; 19 Sep 2012 08:41:37 +0000 Received: from [10.80.2.42] (10.80.2.42) by LONPMAILMX01.citrite.net (10.30.203.162) with Microsoft SMTP Server id 8.3.279.1; Wed, 19 Sep 2012 09:41:37 +0100 Message-ID: <1348044096.14977.84.camel@zakaz.uk.xensource.com> From: Ian Campbell To: Adam Goryachev Date: Wed, 19 Sep 2012 09:41:36 +0100 In-Reply-To: <505871D6.2060801@websitemanagers.com.au> References: <5051D0C5.5070600@websitemanagers.com.au> <1347609879.24226.148.camel@zakaz.uk.xensource.com> <50532CE9.5080601@websitemanagers.com.au> <1347629416.24226.208.camel@zakaz.uk.xensource.com> <505344E8.2030400@websitemanagers.com.au> <505871D6.2060801@websitemanagers.com.au> Organization: Citrix Systems, Inc. X-Mailer: Evolution 3.4.3-1 MIME-Version: 1.0 Cc: "xen-users@lists.xen.org" Subject: Re: [Xen-users] Poor Windows 2003 + GPLPV performance compared to VMWare X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org On Tue, 2012-09-18 at 14:06 +0100, Adam Goryachev wrote: > On 15/09/12 00:53, Adam Goryachev wrote: > > On 14/09/12 23:30, Ian Campbell wrote: > > > >>>>> device_model = '/usr/lib/xen-default/bin/qemu-dm' > >>>>> localtime = 1 > >>>>> name = "vm1" > >>>>> cpus = "2,3,4,5" # Which physical CPU's to allow > >>>> Have you pinned dom0 to use pCPU 1 and/p pCPUs > 6? > >>> No, how should I pin dom0 to cpu0 ? > >> dom0_vcpus_pin as described in > >> http://xenbits.xen.org/docs/4.2-testing/misc/xen-command-line.html > > Thanks, I'll need to reboot the dom0 to apply this, will do as soon as > > this current scheduled task is complete. > OK, I have pinned dom0 to cpu0, and this had no effect on performance. > >> You have: > >> cpus = "2,3,4,5" > >> which means "let all the guests VCPUs run on any of PCPUS 2-5". > >> > >> It sounds like what you are asking for above is: > >> cpus = [2,3,4,5] > >> Which forces guest vcpu0=>pcpu=2, 1=>3, 2=>4 and 3=>5. > >> > >> Subtle I agree. > > Ugh... ok, I'll give that a try. BTW, it would seem this is different > > from xen 4.0 (from debian stable) where it seems to magically do what I > > meant to say, or I'm just lucky on those machines :) > Actually, the above syntax doesn't work: > cpus = [2,3,4,5] # Which physical CPU's to allow > Error: 'int' object has no attribute 'split' Is it ["2","3"...] then I wonder? > Once I reverted to: > cpus = "2,3,4,5" > I can then boot again, but on reboot I get this: > xm vcpu-list > Name ID VCPU CPU State Time(s) CPU > Affinity > Domain-0 0 0 0 r-- 148.9 0 > cobweb 6 0 5 --- 0.5 2-5 > cobweb 6 1 - --p 0.0 2-5 > cobweb 6 2 - --p 0.0 2-5 > cobweb 6 3 - --p 0.0 2-5 > > So it isn't pinning each vcpu to a specific cpu... but I suppose it > should be smart enough to do it well anyway... > Performance is still at the same level. To be honest I wouldn't expect it to make much difference at this stage. I notice the state is "--p" for all but VCPU0 -- which means they are paused. It's probably just that you ran the xm vcpu-list before Windows booted as far as brining up secondary CPUs but it would be worth checking that Windows is actually bringing up / using all the CPUs! Once the VM is fully booted then the state for each vcpu should either be "r--" (running) or "-b-" (currently blocked). I presume something like Windows task manager will also confirm that all the CPUs are in use. > I'm really at a bit of a loss on where to go from here.... The standard > performance improvements don't seem to make any difference at all, and > I'm running out of ideas.... > > Could you suggest a "standard" tool which would allow me to test disk IO > performance (this is my initial suspicion for slow performance), and > also CPU performance (I'm starting to suspect this too now) in both > windows (domU), linux (domU I can create one for testing) and Linux > (dom0). Then I can see where performance is lost (CPU/disk) and at what > layer (dom0/domU) etc... Fajar's suggestion of fio is a good one. Ian. _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Wed Sep 19 09:45:43 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Wed, 19 Sep 2012 09:45:43 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TEGon-0006jW-ED; Wed, 19 Sep 2012 09:43:41 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TEGol-0006jR-V0 for xen-users@lists.xen.org; Wed, 19 Sep 2012 09:43:40 +0000 Received: from [85.158.143.99:33685] by server-1.bemta-4.messagelabs.com id EB/18-05684-BC399505; Wed, 19 Sep 2012 09:43:39 +0000 X-Env-Sender: mailinglists@websitemanagers.com.au X-Msg-Ref: server-10.tower-216.messagelabs.com!1348047814!24525138!1 X-Originating-IP: [203.56.191.70] X-SpamReason: No, hits=0.0 required=7.0 tests= X-StarScan-Received: X-StarScan-Version: 6.6.1.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 28891 invoked from network); 19 Sep 2012 09:43:37 -0000 Received: from unknown (HELO hammer.websitemanagers.com.au) (203.56.191.70) by server-10.tower-216.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 19 Sep 2012 09:43:37 -0000 Received: (qmail 29226 invoked by uid 1011); 19 Sep 2012 09:43:03 -0000 Received: from 220.233.87.52 by hammer (envelope-from , uid 1008) with qmail-scanner-1.24 (clamdscan: 0.97.3/15370. spamassassin: 3.3.1. Clear:RC:1(220.233.87.52):. Processed in 0.0553709999999999 secs); 19 Sep 2012 09:43:03 -0000 Received: from unknown (HELO ?192.168.2.90?) (220.233.87.52) by 0 with SMTP; 19 Sep 2012 09:43:02 -0000 Message-ID: <505993A6.2080804@websitemanagers.com.au> Date: Wed, 19 Sep 2012 19:43:02 +1000 From: Adam Goryachev Organization: Website Managers User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:15.0) Gecko/20120827 Thunderbird/15.0 MIME-Version: 1.0 To: xen-users@lists.xen.org References: <5051D0C5.5070600@websitemanagers.com.au> <1347609879.24226.148.camel@zakaz.uk.xensource.com> <50532CE9.5080601@websitemanagers.com.au> <1347629416.24226.208.camel@zakaz.uk.xensource.com> <505344E8.2030400@websitemanagers.com.au> <505871D6.2060801@websitemanagers.com.au> <1348044096.14977.84.camel@zakaz.uk.xensource.com> In-Reply-To: <1348044096.14977.84.camel@zakaz.uk.xensource.com> Subject: Re: [Xen-users] Poor Windows 2003 + GPLPV performance compared to VMWare X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org On 19/09/12 18:41, Ian Campbell wrote: > On Tue, 2012-09-18 at 14:06 +0100, Adam Goryachev wrote: >> On 15/09/12 00:53, Adam Goryachev wrote: >>> On 14/09/12 23:30, Ian Campbell wrote: >>> >>>>>>> device_model = '/usr/lib/xen-default/bin/qemu-dm' >>>>>>> localtime = 1 >>>>>>> name = "vm1" >>>>>>> cpus = "2,3,4,5" # Which physical CPU's to allow >>>>>> Have you pinned dom0 to use pCPU 1 and/p pCPUs > 6? >>>>> No, how should I pin dom0 to cpu0 ? >>>> dom0_vcpus_pin as described in >>>> http://xenbits.xen.org/docs/4.2-testing/misc/xen-command-line.html >>> Thanks, I'll need to reboot the dom0 to apply this, will do as soon as >>> this current scheduled task is complete. >> OK, I have pinned dom0 to cpu0, and this had no effect on performance. >>>> You have: >>>> cpus = "2,3,4,5" >>>> which means "let all the guests VCPUs run on any of PCPUS 2-5". >>>> >>>> It sounds like what you are asking for above is: >>>> cpus = [2,3,4,5] >>>> Which forces guest vcpu0=>pcpu=2, 1=>3, 2=>4 and 3=>5. >>>> >>>> Subtle I agree. >>> Ugh... ok, I'll give that a try. BTW, it would seem this is different >>> from xen 4.0 (from debian stable) where it seems to magically do what I >>> meant to say, or I'm just lucky on those machines :) >> Actually, the above syntax doesn't work: >> cpus = [2,3,4,5] # Which physical CPU's to allow >> Error: 'int' object has no attribute 'split' > Is it ["2","3"...] then I wonder? > >> Once I reverted to: >> cpus = "2,3,4,5" >> I can then boot again, but on reboot I get this: >> xm vcpu-list >> Name ID VCPU CPU State Time(s) CPU >> Affinity >> Domain-0 0 0 0 r-- 148.9 0 >> cobweb 6 0 5 --- 0.5 2-5 >> cobweb 6 1 - --p 0.0 2-5 >> cobweb 6 2 - --p 0.0 2-5 >> cobweb 6 3 - --p 0.0 2-5 >> >> So it isn't pinning each vcpu to a specific cpu... but I suppose it >> should be smart enough to do it well anyway... >> Performance is still at the same level. > To be honest I wouldn't expect it to make much difference at this stage. > > I notice the state is "--p" for all but VCPU0 -- which means they are > paused. > > It's probably just that you ran the xm vcpu-list before Windows booted > as far as brining up secondary CPUs but it would be worth checking that > Windows is actually bringing up / using all the CPUs! > > Once the VM is fully booted then the state for each vcpu should either > be "r--" (running) or "-b-" (currently blocked). I presume something > like Windows task manager will also confirm that all the CPUs are in > use. That's correct, cpu time was only .5s, so very likely it was pretty immediately after I did the create. Once the machine is up and running I see all 4 vcpu's in b or r state, and the cpu time column incrementing. Within Windows task manager I also see all 4 vcpu's being used during the process I am running. Windows reports approx 50% cpu utilisation, and that actually equates fairly well to 50% of each vcpu, ie, the work load is well balanced across all 4 cores (I don't know if that is by chance, etc... but it is good). I've updated to SP2, and will re-test in the next few hours, failing that, I'll move back to performance measuring with fio/etc. Thanks for all the suggestions and help so far I really appreciate it. Regards, Adam -- Adam Goryachev Website Managers www.websitemanagers.com.au _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Wed Sep 19 09:45:43 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Wed, 19 Sep 2012 09:45:43 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TEGon-0006jW-ED; Wed, 19 Sep 2012 09:43:41 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TEGol-0006jR-V0 for xen-users@lists.xen.org; Wed, 19 Sep 2012 09:43:40 +0000 Received: from [85.158.143.99:33685] by server-1.bemta-4.messagelabs.com id EB/18-05684-BC399505; Wed, 19 Sep 2012 09:43:39 +0000 X-Env-Sender: mailinglists@websitemanagers.com.au X-Msg-Ref: server-10.tower-216.messagelabs.com!1348047814!24525138!1 X-Originating-IP: [203.56.191.70] X-SpamReason: No, hits=0.0 required=7.0 tests= X-StarScan-Received: X-StarScan-Version: 6.6.1.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 28891 invoked from network); 19 Sep 2012 09:43:37 -0000 Received: from unknown (HELO hammer.websitemanagers.com.au) (203.56.191.70) by server-10.tower-216.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 19 Sep 2012 09:43:37 -0000 Received: (qmail 29226 invoked by uid 1011); 19 Sep 2012 09:43:03 -0000 Received: from 220.233.87.52 by hammer (envelope-from , uid 1008) with qmail-scanner-1.24 (clamdscan: 0.97.3/15370. spamassassin: 3.3.1. Clear:RC:1(220.233.87.52):. Processed in 0.0553709999999999 secs); 19 Sep 2012 09:43:03 -0000 Received: from unknown (HELO ?192.168.2.90?) (220.233.87.52) by 0 with SMTP; 19 Sep 2012 09:43:02 -0000 Message-ID: <505993A6.2080804@websitemanagers.com.au> Date: Wed, 19 Sep 2012 19:43:02 +1000 From: Adam Goryachev Organization: Website Managers User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:15.0) Gecko/20120827 Thunderbird/15.0 MIME-Version: 1.0 To: xen-users@lists.xen.org References: <5051D0C5.5070600@websitemanagers.com.au> <1347609879.24226.148.camel@zakaz.uk.xensource.com> <50532CE9.5080601@websitemanagers.com.au> <1347629416.24226.208.camel@zakaz.uk.xensource.com> <505344E8.2030400@websitemanagers.com.au> <505871D6.2060801@websitemanagers.com.au> <1348044096.14977.84.camel@zakaz.uk.xensource.com> In-Reply-To: <1348044096.14977.84.camel@zakaz.uk.xensource.com> Subject: Re: [Xen-users] Poor Windows 2003 + GPLPV performance compared to VMWare X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org On 19/09/12 18:41, Ian Campbell wrote: > On Tue, 2012-09-18 at 14:06 +0100, Adam Goryachev wrote: >> On 15/09/12 00:53, Adam Goryachev wrote: >>> On 14/09/12 23:30, Ian Campbell wrote: >>> >>>>>>> device_model = '/usr/lib/xen-default/bin/qemu-dm' >>>>>>> localtime = 1 >>>>>>> name = "vm1" >>>>>>> cpus = "2,3,4,5" # Which physical CPU's to allow >>>>>> Have you pinned dom0 to use pCPU 1 and/p pCPUs > 6? >>>>> No, how should I pin dom0 to cpu0 ? >>>> dom0_vcpus_pin as described in >>>> http://xenbits.xen.org/docs/4.2-testing/misc/xen-command-line.html >>> Thanks, I'll need to reboot the dom0 to apply this, will do as soon as >>> this current scheduled task is complete. >> OK, I have pinned dom0 to cpu0, and this had no effect on performance. >>>> You have: >>>> cpus = "2,3,4,5" >>>> which means "let all the guests VCPUs run on any of PCPUS 2-5". >>>> >>>> It sounds like what you are asking for above is: >>>> cpus = [2,3,4,5] >>>> Which forces guest vcpu0=>pcpu=2, 1=>3, 2=>4 and 3=>5. >>>> >>>> Subtle I agree. >>> Ugh... ok, I'll give that a try. BTW, it would seem this is different >>> from xen 4.0 (from debian stable) where it seems to magically do what I >>> meant to say, or I'm just lucky on those machines :) >> Actually, the above syntax doesn't work: >> cpus = [2,3,4,5] # Which physical CPU's to allow >> Error: 'int' object has no attribute 'split' > Is it ["2","3"...] then I wonder? > >> Once I reverted to: >> cpus = "2,3,4,5" >> I can then boot again, but on reboot I get this: >> xm vcpu-list >> Name ID VCPU CPU State Time(s) CPU >> Affinity >> Domain-0 0 0 0 r-- 148.9 0 >> cobweb 6 0 5 --- 0.5 2-5 >> cobweb 6 1 - --p 0.0 2-5 >> cobweb 6 2 - --p 0.0 2-5 >> cobweb 6 3 - --p 0.0 2-5 >> >> So it isn't pinning each vcpu to a specific cpu... but I suppose it >> should be smart enough to do it well anyway... >> Performance is still at the same level. > To be honest I wouldn't expect it to make much difference at this stage. > > I notice the state is "--p" for all but VCPU0 -- which means they are > paused. > > It's probably just that you ran the xm vcpu-list before Windows booted > as far as brining up secondary CPUs but it would be worth checking that > Windows is actually bringing up / using all the CPUs! > > Once the VM is fully booted then the state for each vcpu should either > be "r--" (running) or "-b-" (currently blocked). I presume something > like Windows task manager will also confirm that all the CPUs are in > use. That's correct, cpu time was only .5s, so very likely it was pretty immediately after I did the create. Once the machine is up and running I see all 4 vcpu's in b or r state, and the cpu time column incrementing. Within Windows task manager I also see all 4 vcpu's being used during the process I am running. Windows reports approx 50% cpu utilisation, and that actually equates fairly well to 50% of each vcpu, ie, the work load is well balanced across all 4 cores (I don't know if that is by chance, etc... but it is good). I've updated to SP2, and will re-test in the next few hours, failing that, I'll move back to performance measuring with fio/etc. Thanks for all the suggestions and help so far I really appreciate it. Regards, Adam -- Adam Goryachev Website Managers www.websitemanagers.com.au _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Wed Sep 19 12:24:44 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Wed, 19 Sep 2012 12:24:44 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TEJIu-0001Nf-JV; Wed, 19 Sep 2012 12:22:56 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TEJGD-0001JB-PX for xen-users@lists.xen.org; Wed, 19 Sep 2012 12:20:09 +0000 Received: from [85.158.139.83:2535] by server-2.bemta-5.messagelabs.com id 6C/07-11456-878B9505; Wed, 19 Sep 2012 12:20:08 +0000 X-Env-Sender: adam@websitemanagers.com.au X-Msg-Ref: server-4.tower-182.messagelabs.com!1348057204!26673556!1 X-Originating-IP: [203.56.191.70] X-SpamReason: No, hits=0.0 required=7.0 tests= X-StarScan-Received: X-StarScan-Version: 6.6.1.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 23921 invoked from network); 19 Sep 2012 12:20:07 -0000 Received: from unknown (HELO hammer.websitemanagers.com.au) (203.56.191.70) by server-4.tower-182.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 19 Sep 2012 12:20:07 -0000 Received: (qmail 31249 invoked by uid 1011); 19 Sep 2012 12:19:31 -0000 Received: from 124.246.8.196 by hammer (envelope-from , uid 1008) with qmail-scanner-1.24 (clamdscan: 0.97.3/15370. spamassassin: 3.3.1. Clear:RC:1(124.246.8.196):. Processed in 0.055536 secs); 19 Sep 2012 12:19:31 -0000 Received: from unknown (HELO ?192.168.2.90?) (124.246.8.196) by 0 with SMTP; 19 Sep 2012 12:19:31 -0000 Message-ID: <5059B853.9030903@websitemanagers.com.au> Date: Wed, 19 Sep 2012 22:19:31 +1000 From: Adam Goryachev User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:15.0) Gecko/20120827 Thunderbird/15.0 MIME-Version: 1.0 To: xen-users@lists.xen.org References: <5051D0C5.5070600@websitemanagers.com.au> <1347609879.24226.148.camel@zakaz.uk.xensource.com> <50532CE9.5080601@websitemanagers.com.au> <1347629416.24226.208.camel@zakaz.uk.xensource.com> <505344E8.2030400@websitemanagers.com.au> <505871D6.2060801@websitemanagers.com.au> <1348044096.14977.84.camel@zakaz.uk.xensource.com> <505993A6.2080804@websitemanagers.com.au> In-Reply-To: <505993A6.2080804@websitemanagers.com.au> X-Mailman-Approved-At: Wed, 19 Sep 2012 12:22:55 +0000 Subject: Re: [Xen-users] SOLVED - Poor Windows 2003 + GPLPV performance compared to VMWare X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org On 19/09/12 19:43, Adam Goryachev wrote: > On 19/09/12 18:41, Ian Campbell wrote: >> On Tue, 2012-09-18 at 14:06 +0100, Adam Goryachev wrote: >>> On 15/09/12 00:53, Adam Goryachev wrote: >>>> On 14/09/12 23:30, Ian Campbell wrote: >>>> >>>> You have: >>>> cpus = "2,3,4,5" >>>> which means "let all the guests VCPUs run on any of PCPUS 2-5". >>>> >>>> It sounds like what you are asking for above is: >>>> cpus = [2,3,4,5] >>>> Which forces guest vcpu0=>pcpu=2, 1=>3, 2=>4 and 3=>5. >>>> >>>> Subtle I agree. >>>> >>> Actually, the above syntax doesn't work: >>> cpus = [2,3,4,5] # Which physical CPU's to allow >>> Error: 'int' object has no attribute 'split' >> Is it ["2","3"...] then I wonder? I'm not sure, I won't play with it now, and I expect that it will not make a lot of difference. In fact, I might remove all those lines completely, and let xen organise who gets to run on which cpu. I've now got a dedicated cpu (number 0) for the dom0, and the domU's can all share the remaining cpu's. Of course, 99.9% of the time, there will only be a single domU on any physical box, the other 0.1% of the time, xen can deal with the squabling... > I've updated to SP2, and will re-test in the next few hours, Excellent news, the issue is completely resolved, and in fact, performance is now better than vmware, and better than the old original physical box pre-virtualisation. The entire task now completed in 30 minutes, the previous best was 40 minutes (ie, prior to xen). I made note before that I was getting around 2500 transactions / sec, and this was too slow, just now, I'm getting around 7900 transactions / sec. The only change was the installation of Windows 2003 Service Pack 2. So, thank you so much to everyone that made suggestions, or discussed different aspects of the system. Hopefully this will assist someone else now or in the future, to ensure they have SP2 installed or suffer the horrible performance. Regards, Adam -- Adam Goryachev Website Managers Ph: +61 2 8304 0000 adam@websitemanagers.com.au Fax: +61 2 8304 0001 www.websitemanagers.com.au _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Wed Sep 19 12:24:44 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Wed, 19 Sep 2012 12:24:44 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TEJIu-0001Nf-JV; Wed, 19 Sep 2012 12:22:56 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TEJGD-0001JB-PX for xen-users@lists.xen.org; Wed, 19 Sep 2012 12:20:09 +0000 Received: from [85.158.139.83:2535] by server-2.bemta-5.messagelabs.com id 6C/07-11456-878B9505; Wed, 19 Sep 2012 12:20:08 +0000 X-Env-Sender: adam@websitemanagers.com.au X-Msg-Ref: server-4.tower-182.messagelabs.com!1348057204!26673556!1 X-Originating-IP: [203.56.191.70] X-SpamReason: No, hits=0.0 required=7.0 tests= X-StarScan-Received: X-StarScan-Version: 6.6.1.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 23921 invoked from network); 19 Sep 2012 12:20:07 -0000 Received: from unknown (HELO hammer.websitemanagers.com.au) (203.56.191.70) by server-4.tower-182.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 19 Sep 2012 12:20:07 -0000 Received: (qmail 31249 invoked by uid 1011); 19 Sep 2012 12:19:31 -0000 Received: from 124.246.8.196 by hammer (envelope-from , uid 1008) with qmail-scanner-1.24 (clamdscan: 0.97.3/15370. spamassassin: 3.3.1. Clear:RC:1(124.246.8.196):. Processed in 0.055536 secs); 19 Sep 2012 12:19:31 -0000 Received: from unknown (HELO ?192.168.2.90?) (124.246.8.196) by 0 with SMTP; 19 Sep 2012 12:19:31 -0000 Message-ID: <5059B853.9030903@websitemanagers.com.au> Date: Wed, 19 Sep 2012 22:19:31 +1000 From: Adam Goryachev User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:15.0) Gecko/20120827 Thunderbird/15.0 MIME-Version: 1.0 To: xen-users@lists.xen.org References: <5051D0C5.5070600@websitemanagers.com.au> <1347609879.24226.148.camel@zakaz.uk.xensource.com> <50532CE9.5080601@websitemanagers.com.au> <1347629416.24226.208.camel@zakaz.uk.xensource.com> <505344E8.2030400@websitemanagers.com.au> <505871D6.2060801@websitemanagers.com.au> <1348044096.14977.84.camel@zakaz.uk.xensource.com> <505993A6.2080804@websitemanagers.com.au> In-Reply-To: <505993A6.2080804@websitemanagers.com.au> X-Mailman-Approved-At: Wed, 19 Sep 2012 12:22:55 +0000 Subject: Re: [Xen-users] SOLVED - Poor Windows 2003 + GPLPV performance compared to VMWare X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org On 19/09/12 19:43, Adam Goryachev wrote: > On 19/09/12 18:41, Ian Campbell wrote: >> On Tue, 2012-09-18 at 14:06 +0100, Adam Goryachev wrote: >>> On 15/09/12 00:53, Adam Goryachev wrote: >>>> On 14/09/12 23:30, Ian Campbell wrote: >>>> >>>> You have: >>>> cpus = "2,3,4,5" >>>> which means "let all the guests VCPUs run on any of PCPUS 2-5". >>>> >>>> It sounds like what you are asking for above is: >>>> cpus = [2,3,4,5] >>>> Which forces guest vcpu0=>pcpu=2, 1=>3, 2=>4 and 3=>5. >>>> >>>> Subtle I agree. >>>> >>> Actually, the above syntax doesn't work: >>> cpus = [2,3,4,5] # Which physical CPU's to allow >>> Error: 'int' object has no attribute 'split' >> Is it ["2","3"...] then I wonder? I'm not sure, I won't play with it now, and I expect that it will not make a lot of difference. In fact, I might remove all those lines completely, and let xen organise who gets to run on which cpu. I've now got a dedicated cpu (number 0) for the dom0, and the domU's can all share the remaining cpu's. Of course, 99.9% of the time, there will only be a single domU on any physical box, the other 0.1% of the time, xen can deal with the squabling... > I've updated to SP2, and will re-test in the next few hours, Excellent news, the issue is completely resolved, and in fact, performance is now better than vmware, and better than the old original physical box pre-virtualisation. The entire task now completed in 30 minutes, the previous best was 40 minutes (ie, prior to xen). I made note before that I was getting around 2500 transactions / sec, and this was too slow, just now, I'm getting around 7900 transactions / sec. The only change was the installation of Windows 2003 Service Pack 2. So, thank you so much to everyone that made suggestions, or discussed different aspects of the system. Hopefully this will assist someone else now or in the future, to ensure they have SP2 installed or suffer the horrible performance. Regards, Adam -- Adam Goryachev Website Managers Ph: +61 2 8304 0000 adam@websitemanagers.com.au Fax: +61 2 8304 0001 www.websitemanagers.com.au _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Wed Sep 19 12:24:44 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Wed, 19 Sep 2012 12:24:44 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TEJIw-0001Nw-8P; Wed, 19 Sep 2012 12:22:58 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TEJIu-0001Ne-Ru for xen-users@lists.xen.org; Wed, 19 Sep 2012 12:22:57 +0000 Received: from [85.158.138.51:18877] by server-11.bemta-3.messagelabs.com id 9E/50-30250-029B9505; Wed, 19 Sep 2012 12:22:56 +0000 X-Env-Sender: myrdhn@gmail.com X-Msg-Ref: server-11.tower-174.messagelabs.com!1348057374!31157183!1 X-Originating-IP: [209.85.216.173] X-SpamReason: No, hits=0.3 required=7.0 tests=HTML_MESSAGE, ML_RADAR_SPEW_LINKS_14,RCVD_BY_IP,spamassassin: X-StarScan-Received: X-StarScan-Version: 6.6.1.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 2162 invoked from network); 19 Sep 2012 12:22:55 -0000 Received: from mail-qc0-f173.google.com (HELO mail-qc0-f173.google.com) (209.85.216.173) by server-11.tower-174.messagelabs.com with RC4-SHA encrypted SMTP; 19 Sep 2012 12:22:55 -0000 Received: by qcab12 with SMTP id b12so956019qca.32 for ; Wed, 19 Sep 2012 05:22:53 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=from:to:subject:date:message-id:mime-version:content-type:x-mailer :thread-index:content-language; bh=1/G4P3l4oQo08ZvGbZrLyfHqNBvsLrj1/I3MRPOw+fw=; b=nb6L1EFKgOsTgv/RdsG9kimSY2ApC+tUCVB5HuggK4g2N8SswRVE65wAtzEk3b7qDc sI9PgHigW+vkkOxYAXBzuj+lsHnEkfbwI/FTTtfqQkKrx4h/6cYEhplGELH69Bm7jIdZ /Xl3U7pwOKDMQEObYEMEwSL8ncFbAj2qCzWH8VOLQj/5HGa3GmiYjFjTGPulQwW9h/mI VeOitapnWr2zopOwwND0zHAyTHqXGHueZ1Ez/1I3dXIjVcuoGGhVX4dfyuvY5khWOg9f 9RUSkUrA5s2Xy6MZCWJ0gtpeipwBMU/C8C7bAnQ024uNiOMYZbKON/2wJFguNh97AuCz jwgg== Received: by 10.224.185.5 with SMTP id cm5mr6531883qab.87.1348057373824; Wed, 19 Sep 2012 05:22:53 -0700 (PDT) Received: from Belldandy (c-76-119-253-48.hsd1.ma.comcast.net. [76.119.253.48]) by mx.google.com with ESMTPS id k6sm3818023qac.0.2012.09.19.05.22.52 (version=TLSv1/SSLv3 cipher=OTHER); Wed, 19 Sep 2012 05:22:53 -0700 (PDT) From: "Marc Tousignant" To: Date: Wed, 19 Sep 2012 08:22:54 -0400 Message-ID: <004201cd9661$7fc4cb10$7f4e6130$@gmail.com> MIME-Version: 1.0 X-Mailer: Microsoft Outlook 14.0 Thread-Index: Ac2WYM+xxwqSiBtUTt+iykop4ZrNUw== Content-Language: en-us Subject: [Xen-users] PCIe/VGA passthrough X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============3145999641321287381==" Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org This is a multipart message in MIME format. --===============3145999641321287381== Content-Type: multipart/alternative; boundary="----=_NextPart_000_0043_01CD963F.F8B4B1B0" Content-Language: en-us This is a multipart message in MIME format. ------=_NextPart_000_0043_01CD963F.F8B4B1B0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit I'm trying to follow the guides written by David Techer and Teo En Ming on passing through my video card to one of my virtual machines. However, I had run into an interesting conumdrum. Both of them have a similar section about getting the memory ranges for the MMIO BARS: root@mercury:~# dmesg | grep 01:00.0 | grep BAR [ 2.883158] pci 0000:01:00.0: BAR 0: reserving [mem 0xf8000000-0xf9ffffff flags 0x40200] (d=0, p=0) [ 2.883161] pci 0000:01:00.0: BAR 1: reserving [mem 0xd0000000-0xd7ffffff flags 0x14220c] (d=0, p=0) [ 2.883163] pci 0000:01:00.0: BAR 3: reserving [mem 0xd8000000-0xdbffffff flags 0x14220c] (d=0, p=0) [ 2.883166] pci 0000:01:00.0: BAR 5: reserving [io 0xe000-0xe07f flags 0x40101] (d=0, p=0) dmesg | grep 01:00.0 | grep "pci.*mem" [ 0.120488] pci 0000:01:00.0: reg 10: [mem 0xd2000000-0xd2ffffff] [ 0.120508] pci 0000:01:00.0: reg 14: [mem 0xc0000000-0xcfffffff 64bit pref] [ 0.120528] pci 0000:01:00.0: reg 1c: [mem 0xd0000000-0xd1ffffff 64bit pref] [ 0.120556] pci 0000:01:00.0: reg 30: [mem 0xd3000000-0xd307ffff pref] Well, here is my problem.. dmesg | grep 01:00.0 pci 0000:01:00.0: BAR 6: assigned [mem 0xcd000000-0xcd01ffff pref] pci 0000:01:00.0: Boot video device pci 0000:01:00.0: Signaling PME through PCIe PME interrupt I only have a single range. Did I do something wrong somewhere in my kernel? And if so, what? MarcT ------=_NextPart_000_0043_01CD963F.F8B4B1B0 Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable

I’m trying to follow the guides written = by David Techer and Teo En Ming on passing through my video card to one of my virtual = machines. However, I had run into an interesting = conumdrum.

 

Both of them have a similar section about getting the memory ranges for = the MMIO BARS:

 

root@mercury:~# dmesg | grep 01:00.0 | grep = BAR

[    2.883158] pci 0000:01:00.0: BAR 0: = reserving [mem 0xf8000000-0xf9ffffff flags 0x40200] (d=3D0, = p=3D0)

[    2.883161] pci 0000:01:00.0: BAR 1: = reserving [mem 0xd0000000-0xd7ffffff flags 0x14220c] (d=3D0, = p=3D0)

[    2.883163] pci 0000:01:00.0: BAR 3: = reserving [mem 0xd8000000-0xdbffffff flags 0x14220c] (d=3D0, = p=3D0)

[    2.883166] pci 0000:01:00.0: BAR 5: = reserving [io  0xe000-0xe07f flags 0x40101] (d=3D0, = p=3D0)

 

dmesg | grep = 01:00.0 | grep "pci.*mem"

[ 0.120488] = pci 0000:01:00.0: reg 10: [mem = 0xd2000000-0xd2ffffff]

[ 0.120508] = pci 0000:01:00.0: reg 14: [mem 0xc0000000-0xcfffffff 64bit = pref]

[ 0.120528] = pci 0000:01:00.0: reg 1c: [mem 0xd0000000-0xd1ffffff 64bit = pref]

[ 0.120556] pci = 0000:01:00.0: reg 30: [mem 0xd3000000-0xd307ffff = pref]

 <= /span>

Well, here is my = problem..

dmesg | grep 01:00.0

pci 0000:01:00.0: BAR 6: assigned [mem 0xcd000000-0xcd01ffff = pref]

pci 0000:01:00.0: Boot video device

pci 0000:01:00.0: Signaling PME through PCIe PME = interrupt

 

I only have a single range. Did I do something wrong somewhere in my = kernel? And if so, what?

 

MarcT

------=_NextPart_000_0043_01CD963F.F8B4B1B0-- --===============3145999641321287381== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users --===============3145999641321287381==-- From xen-users-bounces@lists.xen.org Wed Sep 19 12:24:44 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Wed, 19 Sep 2012 12:24:44 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TEJIw-0001Nw-8P; Wed, 19 Sep 2012 12:22:58 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TEJIu-0001Ne-Ru for xen-users@lists.xen.org; Wed, 19 Sep 2012 12:22:57 +0000 Received: from [85.158.138.51:18877] by server-11.bemta-3.messagelabs.com id 9E/50-30250-029B9505; Wed, 19 Sep 2012 12:22:56 +0000 X-Env-Sender: myrdhn@gmail.com X-Msg-Ref: server-11.tower-174.messagelabs.com!1348057374!31157183!1 X-Originating-IP: [209.85.216.173] X-SpamReason: No, hits=0.3 required=7.0 tests=HTML_MESSAGE, ML_RADAR_SPEW_LINKS_14,RCVD_BY_IP,spamassassin: X-StarScan-Received: X-StarScan-Version: 6.6.1.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 2162 invoked from network); 19 Sep 2012 12:22:55 -0000 Received: from mail-qc0-f173.google.com (HELO mail-qc0-f173.google.com) (209.85.216.173) by server-11.tower-174.messagelabs.com with RC4-SHA encrypted SMTP; 19 Sep 2012 12:22:55 -0000 Received: by qcab12 with SMTP id b12so956019qca.32 for ; Wed, 19 Sep 2012 05:22:53 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=from:to:subject:date:message-id:mime-version:content-type:x-mailer :thread-index:content-language; bh=1/G4P3l4oQo08ZvGbZrLyfHqNBvsLrj1/I3MRPOw+fw=; b=nb6L1EFKgOsTgv/RdsG9kimSY2ApC+tUCVB5HuggK4g2N8SswRVE65wAtzEk3b7qDc sI9PgHigW+vkkOxYAXBzuj+lsHnEkfbwI/FTTtfqQkKrx4h/6cYEhplGELH69Bm7jIdZ /Xl3U7pwOKDMQEObYEMEwSL8ncFbAj2qCzWH8VOLQj/5HGa3GmiYjFjTGPulQwW9h/mI VeOitapnWr2zopOwwND0zHAyTHqXGHueZ1Ez/1I3dXIjVcuoGGhVX4dfyuvY5khWOg9f 9RUSkUrA5s2Xy6MZCWJ0gtpeipwBMU/C8C7bAnQ024uNiOMYZbKON/2wJFguNh97AuCz jwgg== Received: by 10.224.185.5 with SMTP id cm5mr6531883qab.87.1348057373824; Wed, 19 Sep 2012 05:22:53 -0700 (PDT) Received: from Belldandy (c-76-119-253-48.hsd1.ma.comcast.net. [76.119.253.48]) by mx.google.com with ESMTPS id k6sm3818023qac.0.2012.09.19.05.22.52 (version=TLSv1/SSLv3 cipher=OTHER); Wed, 19 Sep 2012 05:22:53 -0700 (PDT) From: "Marc Tousignant" To: Date: Wed, 19 Sep 2012 08:22:54 -0400 Message-ID: <004201cd9661$7fc4cb10$7f4e6130$@gmail.com> MIME-Version: 1.0 X-Mailer: Microsoft Outlook 14.0 Thread-Index: Ac2WYM+xxwqSiBtUTt+iykop4ZrNUw== Content-Language: en-us Subject: [Xen-users] PCIe/VGA passthrough X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============3145999641321287381==" Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org This is a multipart message in MIME format. --===============3145999641321287381== Content-Type: multipart/alternative; boundary="----=_NextPart_000_0043_01CD963F.F8B4B1B0" Content-Language: en-us This is a multipart message in MIME format. ------=_NextPart_000_0043_01CD963F.F8B4B1B0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit I'm trying to follow the guides written by David Techer and Teo En Ming on passing through my video card to one of my virtual machines. However, I had run into an interesting conumdrum. Both of them have a similar section about getting the memory ranges for the MMIO BARS: root@mercury:~# dmesg | grep 01:00.0 | grep BAR [ 2.883158] pci 0000:01:00.0: BAR 0: reserving [mem 0xf8000000-0xf9ffffff flags 0x40200] (d=0, p=0) [ 2.883161] pci 0000:01:00.0: BAR 1: reserving [mem 0xd0000000-0xd7ffffff flags 0x14220c] (d=0, p=0) [ 2.883163] pci 0000:01:00.0: BAR 3: reserving [mem 0xd8000000-0xdbffffff flags 0x14220c] (d=0, p=0) [ 2.883166] pci 0000:01:00.0: BAR 5: reserving [io 0xe000-0xe07f flags 0x40101] (d=0, p=0) dmesg | grep 01:00.0 | grep "pci.*mem" [ 0.120488] pci 0000:01:00.0: reg 10: [mem 0xd2000000-0xd2ffffff] [ 0.120508] pci 0000:01:00.0: reg 14: [mem 0xc0000000-0xcfffffff 64bit pref] [ 0.120528] pci 0000:01:00.0: reg 1c: [mem 0xd0000000-0xd1ffffff 64bit pref] [ 0.120556] pci 0000:01:00.0: reg 30: [mem 0xd3000000-0xd307ffff pref] Well, here is my problem.. dmesg | grep 01:00.0 pci 0000:01:00.0: BAR 6: assigned [mem 0xcd000000-0xcd01ffff pref] pci 0000:01:00.0: Boot video device pci 0000:01:00.0: Signaling PME through PCIe PME interrupt I only have a single range. Did I do something wrong somewhere in my kernel? And if so, what? MarcT ------=_NextPart_000_0043_01CD963F.F8B4B1B0 Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable

I’m trying to follow the guides written = by David Techer and Teo En Ming on passing through my video card to one of my virtual = machines. However, I had run into an interesting = conumdrum.

 

Both of them have a similar section about getting the memory ranges for = the MMIO BARS:

 

root@mercury:~# dmesg | grep 01:00.0 | grep = BAR

[    2.883158] pci 0000:01:00.0: BAR 0: = reserving [mem 0xf8000000-0xf9ffffff flags 0x40200] (d=3D0, = p=3D0)

[    2.883161] pci 0000:01:00.0: BAR 1: = reserving [mem 0xd0000000-0xd7ffffff flags 0x14220c] (d=3D0, = p=3D0)

[    2.883163] pci 0000:01:00.0: BAR 3: = reserving [mem 0xd8000000-0xdbffffff flags 0x14220c] (d=3D0, = p=3D0)

[    2.883166] pci 0000:01:00.0: BAR 5: = reserving [io  0xe000-0xe07f flags 0x40101] (d=3D0, = p=3D0)

 

dmesg | grep = 01:00.0 | grep "pci.*mem"

[ 0.120488] = pci 0000:01:00.0: reg 10: [mem = 0xd2000000-0xd2ffffff]

[ 0.120508] = pci 0000:01:00.0: reg 14: [mem 0xc0000000-0xcfffffff 64bit = pref]

[ 0.120528] = pci 0000:01:00.0: reg 1c: [mem 0xd0000000-0xd1ffffff 64bit = pref]

[ 0.120556] pci = 0000:01:00.0: reg 30: [mem 0xd3000000-0xd307ffff = pref]

 <= /span>

Well, here is my = problem..

dmesg | grep 01:00.0

pci 0000:01:00.0: BAR 6: assigned [mem 0xcd000000-0xcd01ffff = pref]

pci 0000:01:00.0: Boot video device

pci 0000:01:00.0: Signaling PME through PCIe PME = interrupt

 

I only have a single range. Did I do something wrong somewhere in my = kernel? And if so, what?

 

MarcT

------=_NextPart_000_0043_01CD963F.F8B4B1B0-- --===============3145999641321287381== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users --===============3145999641321287381==-- From xen-users-bounces@lists.xen.org Wed Sep 19 12:29:17 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Wed, 19 Sep 2012 12:29:17 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TEJNa-0001t2-MR; Wed, 19 Sep 2012 12:27:46 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TEJNZ-0001sq-Eu for xen-users@lists.xen.org; Wed, 19 Sep 2012 12:27:45 +0000 Received: from [85.158.139.83:53920] by server-5.bemta-5.messagelabs.com id 54/C5-30514-04AB9505; Wed, 19 Sep 2012 12:27:44 +0000 X-Env-Sender: Ian.Campbell@citrix.com X-Msg-Ref: server-4.tower-182.messagelabs.com!1348057664!26675032!1 X-Originating-IP: [62.200.22.115] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogNjIuMjAwLjIyLjExNSA9PiAxMTAxNzU=\n X-StarScan-Received: X-StarScan-Version: 6.6.1.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 22783 invoked from network); 19 Sep 2012 12:27:44 -0000 Received: from smtp.eu.citrix.com (HELO SMTP.EU.CITRIX.COM) (62.200.22.115) by server-4.tower-182.messagelabs.com with RC4-SHA encrypted SMTP; 19 Sep 2012 12:27:44 -0000 X-IronPort-AV: E=Sophos;i="4.80,447,1344211200"; d="scan'208";a="14630254" Received: from lonpmailmx01.citrite.net ([10.30.203.162]) by LONPIPO01.EU.CITRIX.COM with ESMTP/TLS/RC4-MD5; 19 Sep 2012 12:27:28 +0000 Received: from [10.80.2.42] (10.80.2.42) by LONPMAILMX01.citrite.net (10.30.203.162) with Microsoft SMTP Server id 8.3.279.1; Wed, 19 Sep 2012 13:27:28 +0100 Message-ID: <1348057647.14977.104.camel@zakaz.uk.xensource.com> From: Ian Campbell To: Adam Goryachev Date: Wed, 19 Sep 2012 13:27:27 +0100 In-Reply-To: <5059B853.9030903@websitemanagers.com.au> References: <5051D0C5.5070600@websitemanagers.com.au> <1347609879.24226.148.camel@zakaz.uk.xensource.com> <50532CE9.5080601@websitemanagers.com.au> <1347629416.24226.208.camel@zakaz.uk.xensource.com> <505344E8.2030400@websitemanagers.com.au> <505871D6.2060801@websitemanagers.com.au> <1348044096.14977.84.camel@zakaz.uk.xensource.com> <505993A6.2080804@websitemanagers.com.au> <5059B853.9030903@websitemanagers.com.au> Organization: Citrix Systems, Inc. X-Mailer: Evolution 3.4.3-1 MIME-Version: 1.0 Cc: "xen-users@lists.xen.org" , James Harper Subject: Re: [Xen-users] SOLVED - Poor Windows 2003 + GPLPV performance compared to VMWare X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org On Wed, 2012-09-19 at 13:19 +0100, Adam Goryachev wrote: > On 19/09/12 19:43, Adam Goryachev wrote: > > I've updated to SP2, and will re-test in the next few hours, > > Excellent news, the issue is completely resolved, and in fact, > performance is now better than vmware, and better than the old original > physical box pre-virtualisation. The entire task now completed in 30 > minutes, the previous best was 40 minutes (ie, prior to xen). Excellent news! James, since you suggested it, do you happen to know what it is about pre-SP2 W2K3 that is so bad? Do those versions beat on the TPR or something else? (Just curious) Ian. _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Wed Sep 19 12:29:17 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Wed, 19 Sep 2012 12:29:17 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TEJNa-0001t2-MR; Wed, 19 Sep 2012 12:27:46 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TEJNZ-0001sq-Eu for xen-users@lists.xen.org; Wed, 19 Sep 2012 12:27:45 +0000 Received: from [85.158.139.83:53920] by server-5.bemta-5.messagelabs.com id 54/C5-30514-04AB9505; Wed, 19 Sep 2012 12:27:44 +0000 X-Env-Sender: Ian.Campbell@citrix.com X-Msg-Ref: server-4.tower-182.messagelabs.com!1348057664!26675032!1 X-Originating-IP: [62.200.22.115] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogNjIuMjAwLjIyLjExNSA9PiAxMTAxNzU=\n X-StarScan-Received: X-StarScan-Version: 6.6.1.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 22783 invoked from network); 19 Sep 2012 12:27:44 -0000 Received: from smtp.eu.citrix.com (HELO SMTP.EU.CITRIX.COM) (62.200.22.115) by server-4.tower-182.messagelabs.com with RC4-SHA encrypted SMTP; 19 Sep 2012 12:27:44 -0000 X-IronPort-AV: E=Sophos;i="4.80,447,1344211200"; d="scan'208";a="14630254" Received: from lonpmailmx01.citrite.net ([10.30.203.162]) by LONPIPO01.EU.CITRIX.COM with ESMTP/TLS/RC4-MD5; 19 Sep 2012 12:27:28 +0000 Received: from [10.80.2.42] (10.80.2.42) by LONPMAILMX01.citrite.net (10.30.203.162) with Microsoft SMTP Server id 8.3.279.1; Wed, 19 Sep 2012 13:27:28 +0100 Message-ID: <1348057647.14977.104.camel@zakaz.uk.xensource.com> From: Ian Campbell To: Adam Goryachev Date: Wed, 19 Sep 2012 13:27:27 +0100 In-Reply-To: <5059B853.9030903@websitemanagers.com.au> References: <5051D0C5.5070600@websitemanagers.com.au> <1347609879.24226.148.camel@zakaz.uk.xensource.com> <50532CE9.5080601@websitemanagers.com.au> <1347629416.24226.208.camel@zakaz.uk.xensource.com> <505344E8.2030400@websitemanagers.com.au> <505871D6.2060801@websitemanagers.com.au> <1348044096.14977.84.camel@zakaz.uk.xensource.com> <505993A6.2080804@websitemanagers.com.au> <5059B853.9030903@websitemanagers.com.au> Organization: Citrix Systems, Inc. X-Mailer: Evolution 3.4.3-1 MIME-Version: 1.0 Cc: "xen-users@lists.xen.org" , James Harper Subject: Re: [Xen-users] SOLVED - Poor Windows 2003 + GPLPV performance compared to VMWare X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org On Wed, 2012-09-19 at 13:19 +0100, Adam Goryachev wrote: > On 19/09/12 19:43, Adam Goryachev wrote: > > I've updated to SP2, and will re-test in the next few hours, > > Excellent news, the issue is completely resolved, and in fact, > performance is now better than vmware, and better than the old original > physical box pre-virtualisation. The entire task now completed in 30 > minutes, the previous best was 40 minutes (ie, prior to xen). Excellent news! James, since you suggested it, do you happen to know what it is about pre-SP2 W2K3 that is so bad? Do those versions beat on the TPR or something else? (Just curious) Ian. _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Wed Sep 19 12:38:56 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Wed, 19 Sep 2012 12:38:56 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TEJXM-0002ps-7F; Wed, 19 Sep 2012 12:37:52 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TEJXJ-0002pY-SI for xen-users@lists.xen.org; Wed, 19 Sep 2012 12:37:51 +0000 Received: from [85.158.137.99:52160] by server-10.bemta-3.messagelabs.com id B3/28-10411-D9CB9505; Wed, 19 Sep 2012 12:37:49 +0000 X-Env-Sender: myrdhn@gmail.com X-Msg-Ref: server-9.tower-217.messagelabs.com!1348058266!15145293!1 X-Originating-IP: [209.85.216.52] X-SpamReason: No, hits=0.3 required=7.0 tests=HTML_MESSAGE, ML_RADAR_SPEW_LINKS_14,RCVD_BY_IP,spamassassin: X-StarScan-Received: X-StarScan-Version: 6.6.1.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 15641 invoked from network); 19 Sep 2012 12:37:47 -0000 Received: from mail-qa0-f52.google.com (HELO mail-qa0-f52.google.com) (209.85.216.52) by server-9.tower-217.messagelabs.com with RC4-SHA encrypted SMTP; 19 Sep 2012 12:37:47 -0000 Received: by qabg14 with SMTP id g14so981623qab.11 for ; Wed, 19 Sep 2012 05:37:46 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=from:to:references:in-reply-to:subject:date:message-id:mime-version :content-type:x-mailer:thread-index:content-language; bh=+bigMf3NdGYgtcVWoxx1D6ga16FRe+mrdwvX02mTHlw=; b=gHtR2U+N8+F1ELymfVOqVYg7RFef3+WFVfjUzPyizFWic2h3d6arUN5D6hXtgouUQf Sn9xSHOc35uddY4Fkj2xasHOHFwfBlrHXLXJlEb7FopLNS1VIqr3qxbd81tqpLFeOQq1 p9iPEix5p6+6OrWe1V9PsdKJr6S2bcLzmCbuJ9+JRnvLzVUT9smyQwbURhWnNtvcggTT DVUqra70QJNG8aoS1EAco6BjduStwMW1HLYH6OKsRzcNhQb0OAJ0KSy82E/Ay0FT4Wc1 vr1TpvRohL8CaakolDlMjGzR9jmsvq4FUeVdaE20qGP3SNPO1+y0xdHkzd8BnFBQbYRK ebfQ== Received: by 10.229.137.76 with SMTP id v12mr1927975qct.67.1348058266338; Wed, 19 Sep 2012 05:37:46 -0700 (PDT) Received: from Belldandy (c-76-119-253-48.hsd1.ma.comcast.net. [76.119.253.48]) by mx.google.com with ESMTPS id ck11sm3842821qab.17.2012.09.19.05.37.45 (version=TLSv1/SSLv3 cipher=OTHER); Wed, 19 Sep 2012 05:37:45 -0700 (PDT) From: "Marc Tousignant" To: References: In-Reply-To: Date: Wed, 19 Sep 2012 08:37:47 -0400 Message-ID: <004701cd9663$93bc91f0$bb35b5d0$@gmail.com> MIME-Version: 1.0 X-Mailer: Microsoft Outlook 14.0 Thread-Index: Ac2WYM+xxwqSiBtUTt+iykop4ZrNUwAAnGGQ Content-Language: en-us Subject: Re: [Xen-users] PCIe/VGA passthrough X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============7549776052285344815==" Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org This is a multipart message in MIME format. --===============7549776052285344815== Content-Type: multipart/alternative; boundary="----=_NextPart_000_0048_01CD9642.0CAE4D50" Content-Language: en-us This is a multipart message in MIME format. ------=_NextPart_000_0048_01CD9642.0CAE4D50 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit I know, I know, replying to myself. Trying to preempt a question about my video card. MarcT lspci -vv returns the following on my card: 01:00.0 VGA compatible controller: NVIDIA Corporation G80 [GeForce 8800 GTX] (rev a2) (prog-if 00 [VGA controller]) Subsystem: eVga.com. Corp. Device c837 Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- From: Marc Tousignant [mailto:myrdhn@gmail.com] Sent: Wednesday, September 19, 2012 8:23 AM To: xen-users@lists.xen.org Subject: PCIe/VGA passthrough I'm trying to follow the guides written by David Techer and Teo En Ming on passing through my video card to one of my virtual machines. However, I had run into an interesting conumdrum. Both of them have a similar section about getting the memory ranges for the MMIO BARS: root@mercury:~# dmesg | grep 01:00.0 | grep BAR [ 2.883158] pci 0000:01:00.0: BAR 0: reserving [mem 0xf8000000-0xf9ffffff flags 0x40200] (d=0, p=0) [ 2.883161] pci 0000:01:00.0: BAR 1: reserving [mem 0xd0000000-0xd7ffffff flags 0x14220c] (d=0, p=0) [ 2.883163] pci 0000:01:00.0: BAR 3: reserving [mem 0xd8000000-0xdbffffff flags 0x14220c] (d=0, p=0) [ 2.883166] pci 0000:01:00.0: BAR 5: reserving [io 0xe000-0xe07f flags 0x40101] (d=0, p=0) dmesg | grep 01:00.0 | grep "pci.*mem" [ 0.120488] pci 0000:01:00.0: reg 10: [mem 0xd2000000-0xd2ffffff] [ 0.120508] pci 0000:01:00.0: reg 14: [mem 0xc0000000-0xcfffffff 64bit pref] [ 0.120528] pci 0000:01:00.0: reg 1c: [mem 0xd0000000-0xd1ffffff 64bit pref] [ 0.120556] pci 0000:01:00.0: reg 30: [mem 0xd3000000-0xd307ffff pref] Well, here is my problem.. dmesg | grep 01:00.0 pci 0000:01:00.0: BAR 6: assigned [mem 0xcd000000-0xcd01ffff pref] pci 0000:01:00.0: Boot video device pci 0000:01:00.0: Signaling PME through PCIe PME interrupt I only have a single range. Did I do something wrong somewhere in my kernel? And if so, what? MarcT ------=_NextPart_000_0048_01CD9642.0CAE4D50 Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable

I know, I know, replying to myself. Trying to = preempt a question about my video card.

 

MarcT

 

lspci –vv returns = the following on my card:

01:00.0 VGA compatible = controller: NVIDIA Corporation G80 [GeForce 8800 GTX] (rev a2) (prog-if = 00 [VGA controller])

        = Subsystem: eVga.com. Corp. Device c837

        = Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- = Stepping- SERR- FastB2B- DisINTx-

        = Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=3Dfast >TAbort- = <TAbort- <MAbort- >SERR- <PERR- = INTx-

        = Latency: 0, Cache Line Size: 64 bytes

        = Interrupt: pin A routed to IRQ 10

        = Region 0: Memory at cc000000 (32-bit, non-prefetchable) = [size=3D16M]

        = Region 1: Memory at b0000000 (64-bit, prefetchable) = [size=3D256M]

   =      Region 3: Memory at ca000000 (64-bit, = non-prefetchable) [size=3D32M]

        = Region 5: I/O ports at 9c00 [size=3D128]

        = [virtual] Expansion ROM at cd000000 [disabled] = [size=3D128K]

        = Capabilities: [60] Power Management version 2

        &= nbsp;       Flags: PMEClk- DSI- D1- D2- = AuxCurrent=3D0mA PME(D0-,D1-,D2-,D3hot-,D3cold-)

        &= nbsp;       Status: D0 NoSoftRst- = PME-Enable- DSel=3D0 DScale=3D0 PME-

        = Capabilities: [68] MSI: Enable- Count=3D1/1 Maskable- = 64bit+

        &= nbsp;       Address: = 0000000000000000  Data: 0000

        = Capabilities: [78] Express (v1) Endpoint, MSI 00

        &= nbsp;       DevCap: MaxPayload 128 bytes, = PhantFunc 0, Latency L0s <256ns, L1 <4us

        &= nbsp;           &n= bsp;   ExtTag- AttnBtn- AttnInd- PwrInd- RBE- = FLReset-

        &= nbsp;       DevCtl: Report errors: = Correctable- Non-Fatal- Fatal- Unsupported-

        &= nbsp;           &n= bsp;   RlxdOrd+ ExtTag- PhantFunc- AuxPwr- = NoSnoop+

        &= nbsp;           &n= bsp;   MaxPayload 128 bytes, MaxReadReq 512 = bytes

        &= nbsp;       DevSta: CorrErr- UncorrErr+ = FatalErr- UnsuppReq+ AuxPwr- TransPend-

        &= nbsp;       LnkCap: Port #0, Speed = 2.5GT/s, Width x16, ASPM L0s L1, Latency L0 <256ns, L1 = <4us

        &= nbsp;           &n= bsp;   ClockPM- Surprise- LLActRep- = BwNot-

        &= nbsp;       LnkCtl: ASPM Disabled; RCB 128 = bytes Disabled- Retrain- CommClk+

        &= nbsp;           &n= bsp;   ExtSynch- ClockPM- AutWidDis- BWInt- = AutBWInt-

        &= nbsp;       LnkSta: Speed 2.5GT/s, Width = x16, TrErr- Train- SlotClk+ DLActive- BWMgmt- = ABWMgmt-

        = Capabilities: [100 v1] Virtual Channel

        &= nbsp;       Caps:   LPEVC=3D0 = RefClk=3D100ns PATEntryBits=3D1

        &= nbsp;       Arb:    Fixed- = WRR32- WRR64- WRR128-

        &= nbsp;       Ctrl:   = ArbSelect=3DFixed

        &= nbsp;       Status: = InProgress-

        &= nbsp;       VC0:    = Caps:   PATOffset=3D00 MaxTimeSlots=3D1 = RejSnoopTrans-

        &= nbsp;           &n= bsp;   Arb:    Fixed- WRR32- WRR64- WRR128- = TWRR128- WRR256-

        &= nbsp;           &n= bsp;   Ctrl:   Enable+ ID=3D0 ArbSelect=3DFixed = TC/VC=3Dff

        &= nbsp;           &n= bsp;   Status: NegoPending- = InProgress-

        = Capabilities: [128 v1] Power Budgeting <?>

 

From:= = Marc Tousignant [mailto:myrdhn@gmail.com]
Sent: Wednesday, = September 19, 2012 8:23 AM
To: = xen-users@lists.xen.org
Subject: PCIe/VGA = passthrough

 

I’m trying to follow the guides written = by David Techer and Teo En Ming on passing through my video card to one of my virtual = machines. However, I had run into an interesting = conumdrum.

 

Both of them have a similar section about getting the memory ranges for = the MMIO BARS:

 

root@mercury:~# dmesg | grep 01:00.0 | grep = BAR

[    2.883158] pci 0000:01:00.0: BAR 0: = reserving [mem 0xf8000000-0xf9ffffff flags 0x40200] (d=3D0, = p=3D0)

[    2.883161] pci 0000:01:00.0: BAR 1: = reserving [mem 0xd0000000-0xd7ffffff flags 0x14220c] (d=3D0, = p=3D0)

[    2.883163] pci 0000:01:00.0: BAR 3: = reserving [mem 0xd8000000-0xdbffffff flags 0x14220c] (d=3D0, = p=3D0)

[    2.883166] pci 0000:01:00.0: BAR 5: = reserving [io  0xe000-0xe07f flags 0x40101] (d=3D0, = p=3D0)

 

dmesg | grep = 01:00.0 | grep "pci.*mem"

[ 0.120488] = pci 0000:01:00.0: reg 10: [mem = 0xd2000000-0xd2ffffff]

[ 0.120508] = pci 0000:01:00.0: reg 14: [mem 0xc0000000-0xcfffffff 64bit = pref]

[ 0.120528] = pci 0000:01:00.0: reg 1c: [mem 0xd0000000-0xd1ffffff 64bit = pref]

[ 0.120556] pci = 0000:01:00.0: reg 30: [mem 0xd3000000-0xd307ffff = pref]

 <= /span>

Well, here is my = problem..

dmesg | grep 01:00.0

pci 0000:01:00.0: BAR 6: assigned [mem 0xcd000000-0xcd01ffff = pref]

pci 0000:01:00.0: Boot video device

pci 0000:01:00.0: Signaling PME through PCIe PME = interrupt

 

I only have a single range. Did I do something wrong somewhere in my = kernel? And if so, what?

 

MarcT

------=_NextPart_000_0048_01CD9642.0CAE4D50-- --===============7549776052285344815== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users --===============7549776052285344815==-- From xen-users-bounces@lists.xen.org Wed Sep 19 12:38:56 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Wed, 19 Sep 2012 12:38:56 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TEJXM-0002ps-7F; Wed, 19 Sep 2012 12:37:52 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TEJXJ-0002pY-SI for xen-users@lists.xen.org; Wed, 19 Sep 2012 12:37:51 +0000 Received: from [85.158.137.99:52160] by server-10.bemta-3.messagelabs.com id B3/28-10411-D9CB9505; Wed, 19 Sep 2012 12:37:49 +0000 X-Env-Sender: myrdhn@gmail.com X-Msg-Ref: server-9.tower-217.messagelabs.com!1348058266!15145293!1 X-Originating-IP: [209.85.216.52] X-SpamReason: No, hits=0.3 required=7.0 tests=HTML_MESSAGE, ML_RADAR_SPEW_LINKS_14,RCVD_BY_IP,spamassassin: X-StarScan-Received: X-StarScan-Version: 6.6.1.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 15641 invoked from network); 19 Sep 2012 12:37:47 -0000 Received: from mail-qa0-f52.google.com (HELO mail-qa0-f52.google.com) (209.85.216.52) by server-9.tower-217.messagelabs.com with RC4-SHA encrypted SMTP; 19 Sep 2012 12:37:47 -0000 Received: by qabg14 with SMTP id g14so981623qab.11 for ; Wed, 19 Sep 2012 05:37:46 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=from:to:references:in-reply-to:subject:date:message-id:mime-version :content-type:x-mailer:thread-index:content-language; bh=+bigMf3NdGYgtcVWoxx1D6ga16FRe+mrdwvX02mTHlw=; b=gHtR2U+N8+F1ELymfVOqVYg7RFef3+WFVfjUzPyizFWic2h3d6arUN5D6hXtgouUQf Sn9xSHOc35uddY4Fkj2xasHOHFwfBlrHXLXJlEb7FopLNS1VIqr3qxbd81tqpLFeOQq1 p9iPEix5p6+6OrWe1V9PsdKJr6S2bcLzmCbuJ9+JRnvLzVUT9smyQwbURhWnNtvcggTT DVUqra70QJNG8aoS1EAco6BjduStwMW1HLYH6OKsRzcNhQb0OAJ0KSy82E/Ay0FT4Wc1 vr1TpvRohL8CaakolDlMjGzR9jmsvq4FUeVdaE20qGP3SNPO1+y0xdHkzd8BnFBQbYRK ebfQ== Received: by 10.229.137.76 with SMTP id v12mr1927975qct.67.1348058266338; Wed, 19 Sep 2012 05:37:46 -0700 (PDT) Received: from Belldandy (c-76-119-253-48.hsd1.ma.comcast.net. [76.119.253.48]) by mx.google.com with ESMTPS id ck11sm3842821qab.17.2012.09.19.05.37.45 (version=TLSv1/SSLv3 cipher=OTHER); Wed, 19 Sep 2012 05:37:45 -0700 (PDT) From: "Marc Tousignant" To: References: In-Reply-To: Date: Wed, 19 Sep 2012 08:37:47 -0400 Message-ID: <004701cd9663$93bc91f0$bb35b5d0$@gmail.com> MIME-Version: 1.0 X-Mailer: Microsoft Outlook 14.0 Thread-Index: Ac2WYM+xxwqSiBtUTt+iykop4ZrNUwAAnGGQ Content-Language: en-us Subject: Re: [Xen-users] PCIe/VGA passthrough X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============7549776052285344815==" Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org This is a multipart message in MIME format. --===============7549776052285344815== Content-Type: multipart/alternative; boundary="----=_NextPart_000_0048_01CD9642.0CAE4D50" Content-Language: en-us This is a multipart message in MIME format. ------=_NextPart_000_0048_01CD9642.0CAE4D50 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit I know, I know, replying to myself. Trying to preempt a question about my video card. MarcT lspci -vv returns the following on my card: 01:00.0 VGA compatible controller: NVIDIA Corporation G80 [GeForce 8800 GTX] (rev a2) (prog-if 00 [VGA controller]) Subsystem: eVga.com. Corp. Device c837 Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- From: Marc Tousignant [mailto:myrdhn@gmail.com] Sent: Wednesday, September 19, 2012 8:23 AM To: xen-users@lists.xen.org Subject: PCIe/VGA passthrough I'm trying to follow the guides written by David Techer and Teo En Ming on passing through my video card to one of my virtual machines. However, I had run into an interesting conumdrum. Both of them have a similar section about getting the memory ranges for the MMIO BARS: root@mercury:~# dmesg | grep 01:00.0 | grep BAR [ 2.883158] pci 0000:01:00.0: BAR 0: reserving [mem 0xf8000000-0xf9ffffff flags 0x40200] (d=0, p=0) [ 2.883161] pci 0000:01:00.0: BAR 1: reserving [mem 0xd0000000-0xd7ffffff flags 0x14220c] (d=0, p=0) [ 2.883163] pci 0000:01:00.0: BAR 3: reserving [mem 0xd8000000-0xdbffffff flags 0x14220c] (d=0, p=0) [ 2.883166] pci 0000:01:00.0: BAR 5: reserving [io 0xe000-0xe07f flags 0x40101] (d=0, p=0) dmesg | grep 01:00.0 | grep "pci.*mem" [ 0.120488] pci 0000:01:00.0: reg 10: [mem 0xd2000000-0xd2ffffff] [ 0.120508] pci 0000:01:00.0: reg 14: [mem 0xc0000000-0xcfffffff 64bit pref] [ 0.120528] pci 0000:01:00.0: reg 1c: [mem 0xd0000000-0xd1ffffff 64bit pref] [ 0.120556] pci 0000:01:00.0: reg 30: [mem 0xd3000000-0xd307ffff pref] Well, here is my problem.. dmesg | grep 01:00.0 pci 0000:01:00.0: BAR 6: assigned [mem 0xcd000000-0xcd01ffff pref] pci 0000:01:00.0: Boot video device pci 0000:01:00.0: Signaling PME through PCIe PME interrupt I only have a single range. Did I do something wrong somewhere in my kernel? And if so, what? MarcT ------=_NextPart_000_0048_01CD9642.0CAE4D50 Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable

I know, I know, replying to myself. Trying to = preempt a question about my video card.

 

MarcT

 

lspci –vv returns = the following on my card:

01:00.0 VGA compatible = controller: NVIDIA Corporation G80 [GeForce 8800 GTX] (rev a2) (prog-if = 00 [VGA controller])

        = Subsystem: eVga.com. Corp. Device c837

        = Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- = Stepping- SERR- FastB2B- DisINTx-

        = Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=3Dfast >TAbort- = <TAbort- <MAbort- >SERR- <PERR- = INTx-

        = Latency: 0, Cache Line Size: 64 bytes

        = Interrupt: pin A routed to IRQ 10

        = Region 0: Memory at cc000000 (32-bit, non-prefetchable) = [size=3D16M]

        = Region 1: Memory at b0000000 (64-bit, prefetchable) = [size=3D256M]

   =      Region 3: Memory at ca000000 (64-bit, = non-prefetchable) [size=3D32M]

        = Region 5: I/O ports at 9c00 [size=3D128]

        = [virtual] Expansion ROM at cd000000 [disabled] = [size=3D128K]

        = Capabilities: [60] Power Management version 2

        &= nbsp;       Flags: PMEClk- DSI- D1- D2- = AuxCurrent=3D0mA PME(D0-,D1-,D2-,D3hot-,D3cold-)

        &= nbsp;       Status: D0 NoSoftRst- = PME-Enable- DSel=3D0 DScale=3D0 PME-

        = Capabilities: [68] MSI: Enable- Count=3D1/1 Maskable- = 64bit+

        &= nbsp;       Address: = 0000000000000000  Data: 0000

        = Capabilities: [78] Express (v1) Endpoint, MSI 00

        &= nbsp;       DevCap: MaxPayload 128 bytes, = PhantFunc 0, Latency L0s <256ns, L1 <4us

        &= nbsp;           &n= bsp;   ExtTag- AttnBtn- AttnInd- PwrInd- RBE- = FLReset-

        &= nbsp;       DevCtl: Report errors: = Correctable- Non-Fatal- Fatal- Unsupported-

        &= nbsp;           &n= bsp;   RlxdOrd+ ExtTag- PhantFunc- AuxPwr- = NoSnoop+

        &= nbsp;           &n= bsp;   MaxPayload 128 bytes, MaxReadReq 512 = bytes

        &= nbsp;       DevSta: CorrErr- UncorrErr+ = FatalErr- UnsuppReq+ AuxPwr- TransPend-

        &= nbsp;       LnkCap: Port #0, Speed = 2.5GT/s, Width x16, ASPM L0s L1, Latency L0 <256ns, L1 = <4us

        &= nbsp;           &n= bsp;   ClockPM- Surprise- LLActRep- = BwNot-

        &= nbsp;       LnkCtl: ASPM Disabled; RCB 128 = bytes Disabled- Retrain- CommClk+

        &= nbsp;           &n= bsp;   ExtSynch- ClockPM- AutWidDis- BWInt- = AutBWInt-

        &= nbsp;       LnkSta: Speed 2.5GT/s, Width = x16, TrErr- Train- SlotClk+ DLActive- BWMgmt- = ABWMgmt-

        = Capabilities: [100 v1] Virtual Channel

        &= nbsp;       Caps:   LPEVC=3D0 = RefClk=3D100ns PATEntryBits=3D1

        &= nbsp;       Arb:    Fixed- = WRR32- WRR64- WRR128-

        &= nbsp;       Ctrl:   = ArbSelect=3DFixed

        &= nbsp;       Status: = InProgress-

        &= nbsp;       VC0:    = Caps:   PATOffset=3D00 MaxTimeSlots=3D1 = RejSnoopTrans-

        &= nbsp;           &n= bsp;   Arb:    Fixed- WRR32- WRR64- WRR128- = TWRR128- WRR256-

        &= nbsp;           &n= bsp;   Ctrl:   Enable+ ID=3D0 ArbSelect=3DFixed = TC/VC=3Dff

        &= nbsp;           &n= bsp;   Status: NegoPending- = InProgress-

        = Capabilities: [128 v1] Power Budgeting <?>

 

From:= = Marc Tousignant [mailto:myrdhn@gmail.com]
Sent: Wednesday, = September 19, 2012 8:23 AM
To: = xen-users@lists.xen.org
Subject: PCIe/VGA = passthrough

 

I’m trying to follow the guides written = by David Techer and Teo En Ming on passing through my video card to one of my virtual = machines. However, I had run into an interesting = conumdrum.

 

Both of them have a similar section about getting the memory ranges for = the MMIO BARS:

 

root@mercury:~# dmesg | grep 01:00.0 | grep = BAR

[    2.883158] pci 0000:01:00.0: BAR 0: = reserving [mem 0xf8000000-0xf9ffffff flags 0x40200] (d=3D0, = p=3D0)

[    2.883161] pci 0000:01:00.0: BAR 1: = reserving [mem 0xd0000000-0xd7ffffff flags 0x14220c] (d=3D0, = p=3D0)

[    2.883163] pci 0000:01:00.0: BAR 3: = reserving [mem 0xd8000000-0xdbffffff flags 0x14220c] (d=3D0, = p=3D0)

[    2.883166] pci 0000:01:00.0: BAR 5: = reserving [io  0xe000-0xe07f flags 0x40101] (d=3D0, = p=3D0)

 

dmesg | grep = 01:00.0 | grep "pci.*mem"

[ 0.120488] = pci 0000:01:00.0: reg 10: [mem = 0xd2000000-0xd2ffffff]

[ 0.120508] = pci 0000:01:00.0: reg 14: [mem 0xc0000000-0xcfffffff 64bit = pref]

[ 0.120528] = pci 0000:01:00.0: reg 1c: [mem 0xd0000000-0xd1ffffff 64bit = pref]

[ 0.120556] pci = 0000:01:00.0: reg 30: [mem 0xd3000000-0xd307ffff = pref]

 <= /span>

Well, here is my = problem..

dmesg | grep 01:00.0

pci 0000:01:00.0: BAR 6: assigned [mem 0xcd000000-0xcd01ffff = pref]

pci 0000:01:00.0: Boot video device

pci 0000:01:00.0: Signaling PME through PCIe PME = interrupt

 

I only have a single range. Did I do something wrong somewhere in my = kernel? And if so, what?

 

MarcT

------=_NextPart_000_0048_01CD9642.0CAE4D50-- --===============7549776052285344815== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users --===============7549776052285344815==-- From xen-users-bounces@lists.xen.org Wed Sep 19 12:57:10 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Wed, 19 Sep 2012 12:57:10 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TEJop-0003X5-Qr; Wed, 19 Sep 2012 12:55:55 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TEJoo-0003X0-97 for xen-users@lists.xen.org; Wed, 19 Sep 2012 12:55:54 +0000 Received: from [85.158.137.99:9827] by server-7.bemta-3.messagelabs.com id 69/B4-32000-9D0C9505; Wed, 19 Sep 2012 12:55:53 +0000 X-Env-Sender: james.harper@bendigoit.com.au X-Msg-Ref: server-14.tower-217.messagelabs.com!1348059349!18285565!1 X-Originating-IP: [203.16.207.99] X-SpamReason: No, hits=0.0 required=7.0 tests= X-StarScan-Received: X-StarScan-Version: 6.6.1.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 20498 invoked from network); 19 Sep 2012 12:55:52 -0000 Received: from mail.bendigoit.com.au (HELO smtp2.bendigoit.com.au) (203.16.207.99) by server-14.tower-217.messagelabs.com with AES256-SHA encrypted SMTP; 19 Sep 2012 12:55:52 -0000 Received: from [2001:388:e000:712:a5ca:4fd3:14f:ad5d] (helo=BITCOM1.int.sbss.com.au) by smtp2.bendigoit.com.au with esmtp (Exim 4.72) (envelope-from ) id 1TEJoe-0007yJ-RF; Wed, 19 Sep 2012 22:55:44 +1000 Received: from BITCOM1.int.sbss.com.au ([fe80::a5ca:4fd3:14f:ad5d]) by BITCOM1.int.sbss.com.au ([fe80::a5ca:4fd3:14f:ad5d%12]) with mapi id 14.01.0379.000; Wed, 19 Sep 2012 22:55:44 +1000 From: James Harper To: Adam Goryachev , "xen-users@lists.xen.org" Thread-Topic: [Xen-users] SOLVED - Poor Windows 2003 + GPLPV performance compared to VMWare Thread-Index: AQHNlmNftMdt2SzZFUqD/VEO8wSySJeRndjg Date: Wed, 19 Sep 2012 12:55:43 +0000 Message-ID: <6035A0D088A63A46850C3988ED045A4B29BA8BB9@BITCOM1.int.sbss.com.au> References: <5051D0C5.5070600@websitemanagers.com.au> <1347609879.24226.148.camel@zakaz.uk.xensource.com> <50532CE9.5080601@websitemanagers.com.au> <1347629416.24226.208.camel@zakaz.uk.xensource.com> <505344E8.2030400@websitemanagers.com.au> <505871D6.2060801@websitemanagers.com.au> <1348044096.14977.84.camel@zakaz.uk.xensource.com> <505993A6.2080804@websitemanagers.com.au> <5059B853.9030903@websitemanagers.com.au> In-Reply-To: <5059B853.9030903@websitemanagers.com.au> Accept-Language: en-AU, en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [172.16.3.132] x-tm-as-product-ver: SMEX-10.2.0.2087-7.000.1014-19192.007 x-tm-as-result: No--35.592000-0.000000-31 x-tm-as-user-approved-sender: Yes x-tm-as-user-blocked-sender: No MIME-Version: 1.0 X-Really-From-Bendigo-IT: magichashvalue Subject: Re: [Xen-users] SOLVED - Poor Windows 2003 + GPLPV performance compared to VMWare X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org > > Excellent news, the issue is completely resolved, and in fact, performance is > now better than vmware, and better than the old original physical box pre- > virtualisation. The entire task now completed in 30 minutes, the previous > best was 40 minutes (ie, prior to xen). > I wasn't expecting it to be faster. Are you comparing 2003sp1 under VMWare with 2003sp2 under Xen? > I made note before that I was getting around 2500 transactions / sec, and this > was too slow, just now, I'm getting around 7900 transactions / sec. The only > change was the installation of Windows 2003 Service Pack 2. Microsoft updated Windows 2003 with SP2 to remove the use of the TPR register, which was a big performance hit on a virtual system. You can add /PATCHTPR to boot.ini to patch the windows kernel to use an alternate method of TPR access under AMD systems, and to cache reads of TPR under Intel systems, but I thought the xen guys had implemented their own acceleration of this in xen itself? SP2 is definitely the best option for 2003, but XP and 2000 don't have this performance enhancement so I thought I'd mention it here too. James _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Wed Sep 19 12:57:10 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Wed, 19 Sep 2012 12:57:10 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TEJop-0003X5-Qr; Wed, 19 Sep 2012 12:55:55 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TEJoo-0003X0-97 for xen-users@lists.xen.org; Wed, 19 Sep 2012 12:55:54 +0000 Received: from [85.158.137.99:9827] by server-7.bemta-3.messagelabs.com id 69/B4-32000-9D0C9505; Wed, 19 Sep 2012 12:55:53 +0000 X-Env-Sender: james.harper@bendigoit.com.au X-Msg-Ref: server-14.tower-217.messagelabs.com!1348059349!18285565!1 X-Originating-IP: [203.16.207.99] X-SpamReason: No, hits=0.0 required=7.0 tests= X-StarScan-Received: X-StarScan-Version: 6.6.1.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 20498 invoked from network); 19 Sep 2012 12:55:52 -0000 Received: from mail.bendigoit.com.au (HELO smtp2.bendigoit.com.au) (203.16.207.99) by server-14.tower-217.messagelabs.com with AES256-SHA encrypted SMTP; 19 Sep 2012 12:55:52 -0000 Received: from [2001:388:e000:712:a5ca:4fd3:14f:ad5d] (helo=BITCOM1.int.sbss.com.au) by smtp2.bendigoit.com.au with esmtp (Exim 4.72) (envelope-from ) id 1TEJoe-0007yJ-RF; Wed, 19 Sep 2012 22:55:44 +1000 Received: from BITCOM1.int.sbss.com.au ([fe80::a5ca:4fd3:14f:ad5d]) by BITCOM1.int.sbss.com.au ([fe80::a5ca:4fd3:14f:ad5d%12]) with mapi id 14.01.0379.000; Wed, 19 Sep 2012 22:55:44 +1000 From: James Harper To: Adam Goryachev , "xen-users@lists.xen.org" Thread-Topic: [Xen-users] SOLVED - Poor Windows 2003 + GPLPV performance compared to VMWare Thread-Index: AQHNlmNftMdt2SzZFUqD/VEO8wSySJeRndjg Date: Wed, 19 Sep 2012 12:55:43 +0000 Message-ID: <6035A0D088A63A46850C3988ED045A4B29BA8BB9@BITCOM1.int.sbss.com.au> References: <5051D0C5.5070600@websitemanagers.com.au> <1347609879.24226.148.camel@zakaz.uk.xensource.com> <50532CE9.5080601@websitemanagers.com.au> <1347629416.24226.208.camel@zakaz.uk.xensource.com> <505344E8.2030400@websitemanagers.com.au> <505871D6.2060801@websitemanagers.com.au> <1348044096.14977.84.camel@zakaz.uk.xensource.com> <505993A6.2080804@websitemanagers.com.au> <5059B853.9030903@websitemanagers.com.au> In-Reply-To: <5059B853.9030903@websitemanagers.com.au> Accept-Language: en-AU, en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [172.16.3.132] x-tm-as-product-ver: SMEX-10.2.0.2087-7.000.1014-19192.007 x-tm-as-result: No--35.592000-0.000000-31 x-tm-as-user-approved-sender: Yes x-tm-as-user-blocked-sender: No MIME-Version: 1.0 X-Really-From-Bendigo-IT: magichashvalue Subject: Re: [Xen-users] SOLVED - Poor Windows 2003 + GPLPV performance compared to VMWare X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org > > Excellent news, the issue is completely resolved, and in fact, performance is > now better than vmware, and better than the old original physical box pre- > virtualisation. The entire task now completed in 30 minutes, the previous > best was 40 minutes (ie, prior to xen). > I wasn't expecting it to be faster. Are you comparing 2003sp1 under VMWare with 2003sp2 under Xen? > I made note before that I was getting around 2500 transactions / sec, and this > was too slow, just now, I'm getting around 7900 transactions / sec. The only > change was the installation of Windows 2003 Service Pack 2. Microsoft updated Windows 2003 with SP2 to remove the use of the TPR register, which was a big performance hit on a virtual system. You can add /PATCHTPR to boot.ini to patch the windows kernel to use an alternate method of TPR access under AMD systems, and to cache reads of TPR under Intel systems, but I thought the xen guys had implemented their own acceleration of this in xen itself? SP2 is definitely the best option for 2003, but XP and 2000 don't have this performance enhancement so I thought I'd mention it here too. James _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Wed Sep 19 13:01:29 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Wed, 19 Sep 2012 13:01:29 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TEJtL-0003zL-Hv; Wed, 19 Sep 2012 13:00:35 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TEJtJ-0003zD-JY for xen-users@lists.xen.org; Wed, 19 Sep 2012 13:00:33 +0000 Received: from [85.158.137.99:33885] by server-12.bemta-3.messagelabs.com id D5/BF-10384-0F1C9505; Wed, 19 Sep 2012 13:00:32 +0000 X-Env-Sender: james.harper@bendigoit.com.au X-Msg-Ref: server-10.tower-217.messagelabs.com!1348059628!18318700!1 X-Originating-IP: [203.16.224.4] X-SpamReason: No, hits=0.0 required=7.0 tests= X-StarScan-Received: X-StarScan-Version: 6.6.1.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 11888 invoked from network); 19 Sep 2012 13:00:31 -0000 Received: from smtp1.bendigoit.com.au (HELO smtp1.bendigoit.com.au) (203.16.224.4) by server-10.tower-217.messagelabs.com with AES256-SHA encrypted SMTP; 19 Sep 2012 13:00:31 -0000 Received: from [2001:388:e000:712:a5ca:4fd3:14f:ad5d] (helo=BITCOM1.int.sbss.com.au) by smtp1.bendigoit.com.au with esmtp (Exim 4.69) (envelope-from ) id 1TEJt5-0000Ah-RO; Wed, 19 Sep 2012 23:00:20 +1000 Received: from BITCOM1.int.sbss.com.au ([fe80::a5ca:4fd3:14f:ad5d]) by BITCOM1.int.sbss.com.au ([fe80::a5ca:4fd3:14f:ad5d%12]) with mapi id 14.01.0379.000; Wed, 19 Sep 2012 23:00:20 +1000 From: James Harper To: Ian Campbell , Adam Goryachev Thread-Topic: [Xen-users] SOLVED - Poor Windows 2003 + GPLPV performance compared to VMWare Thread-Index: AQHNlmI3pGsFoFq0f0aiFBIRZwZ93peRn3xg Date: Wed, 19 Sep 2012 13:00:18 +0000 Message-ID: <6035A0D088A63A46850C3988ED045A4B29BA8C0B@BITCOM1.int.sbss.com.au> References: <5051D0C5.5070600@websitemanagers.com.au> <1347609879.24226.148.camel@zakaz.uk.xensource.com> <50532CE9.5080601@websitemanagers.com.au> <1347629416.24226.208.camel@zakaz.uk.xensource.com> <505344E8.2030400@websitemanagers.com.au> <505871D6.2060801@websitemanagers.com.au> <1348044096.14977.84.camel@zakaz.uk.xensource.com> <505993A6.2080804@websitemanagers.com.au> <5059B853.9030903@websitemanagers.com.au> <1348057647.14977.104.camel@zakaz.uk.xensource.com> In-Reply-To: <1348057647.14977.104.camel@zakaz.uk.xensource.com> Accept-Language: en-AU, en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [172.16.3.132] x-tm-as-product-ver: SMEX-10.2.0.2087-7.000.1014-19192.007 x-tm-as-result: No--39.740000-0.000000-31 x-tm-as-user-approved-sender: Yes x-tm-as-user-blocked-sender: No MIME-Version: 1.0 X-Really-From-Bendigo-IT: magichashvalue Cc: "xen-users@lists.xen.org" Subject: Re: [Xen-users] SOLVED - Poor Windows 2003 + GPLPV performance compared to VMWare X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org > > On Wed, 2012-09-19 at 13:19 +0100, Adam Goryachev wrote: > > On 19/09/12 19:43, Adam Goryachev wrote: > > > I've updated to SP2, and will re-test in the next few hours, > > > > Excellent news, the issue is completely resolved, and in fact, > > performance is now better than vmware, and better than the old > > original physical box pre-virtualisation. The entire task now > > completed in 30 minutes, the previous best was 40 minutes (ie, prior to > xen). > > Excellent news! > > James, since you suggested it, do you happen to know what it is about > pre-SP2 W2K3 that is so bad? Do those versions beat on the TPR or > something else? > > (Just curious) > Yes it will almost certainly be TPR access. I actually thought MS made the change in SP1 but maybe it was SP2 (don't know if the OP upgraded from RTM to sp2 or sp1 to sp2, but quite possibly I just don't remember :) The change they made means that the TPR doesn't get touched at all anymore, so is much faster. For prior versions (and XP and 2000), GPLPV can patch AMD systems to use the CR8 (I think) registr for TPR access which is much faster. For Intel, the best I could do was cache TPR so that reads were fast... it's still quite a speedup. I thought Xen optimised this for Intel though and my patching wasn't necessary anymore? Or maybe the OP is running a version of xen that doesn't have that feature?? James _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Wed Sep 19 13:01:29 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Wed, 19 Sep 2012 13:01:29 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TEJtL-0003zL-Hv; Wed, 19 Sep 2012 13:00:35 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TEJtJ-0003zD-JY for xen-users@lists.xen.org; Wed, 19 Sep 2012 13:00:33 +0000 Received: from [85.158.137.99:33885] by server-12.bemta-3.messagelabs.com id D5/BF-10384-0F1C9505; Wed, 19 Sep 2012 13:00:32 +0000 X-Env-Sender: james.harper@bendigoit.com.au X-Msg-Ref: server-10.tower-217.messagelabs.com!1348059628!18318700!1 X-Originating-IP: [203.16.224.4] X-SpamReason: No, hits=0.0 required=7.0 tests= X-StarScan-Received: X-StarScan-Version: 6.6.1.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 11888 invoked from network); 19 Sep 2012 13:00:31 -0000 Received: from smtp1.bendigoit.com.au (HELO smtp1.bendigoit.com.au) (203.16.224.4) by server-10.tower-217.messagelabs.com with AES256-SHA encrypted SMTP; 19 Sep 2012 13:00:31 -0000 Received: from [2001:388:e000:712:a5ca:4fd3:14f:ad5d] (helo=BITCOM1.int.sbss.com.au) by smtp1.bendigoit.com.au with esmtp (Exim 4.69) (envelope-from ) id 1TEJt5-0000Ah-RO; Wed, 19 Sep 2012 23:00:20 +1000 Received: from BITCOM1.int.sbss.com.au ([fe80::a5ca:4fd3:14f:ad5d]) by BITCOM1.int.sbss.com.au ([fe80::a5ca:4fd3:14f:ad5d%12]) with mapi id 14.01.0379.000; Wed, 19 Sep 2012 23:00:20 +1000 From: James Harper To: Ian Campbell , Adam Goryachev Thread-Topic: [Xen-users] SOLVED - Poor Windows 2003 + GPLPV performance compared to VMWare Thread-Index: AQHNlmI3pGsFoFq0f0aiFBIRZwZ93peRn3xg Date: Wed, 19 Sep 2012 13:00:18 +0000 Message-ID: <6035A0D088A63A46850C3988ED045A4B29BA8C0B@BITCOM1.int.sbss.com.au> References: <5051D0C5.5070600@websitemanagers.com.au> <1347609879.24226.148.camel@zakaz.uk.xensource.com> <50532CE9.5080601@websitemanagers.com.au> <1347629416.24226.208.camel@zakaz.uk.xensource.com> <505344E8.2030400@websitemanagers.com.au> <505871D6.2060801@websitemanagers.com.au> <1348044096.14977.84.camel@zakaz.uk.xensource.com> <505993A6.2080804@websitemanagers.com.au> <5059B853.9030903@websitemanagers.com.au> <1348057647.14977.104.camel@zakaz.uk.xensource.com> In-Reply-To: <1348057647.14977.104.camel@zakaz.uk.xensource.com> Accept-Language: en-AU, en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [172.16.3.132] x-tm-as-product-ver: SMEX-10.2.0.2087-7.000.1014-19192.007 x-tm-as-result: No--39.740000-0.000000-31 x-tm-as-user-approved-sender: Yes x-tm-as-user-blocked-sender: No MIME-Version: 1.0 X-Really-From-Bendigo-IT: magichashvalue Cc: "xen-users@lists.xen.org" Subject: Re: [Xen-users] SOLVED - Poor Windows 2003 + GPLPV performance compared to VMWare X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org > > On Wed, 2012-09-19 at 13:19 +0100, Adam Goryachev wrote: > > On 19/09/12 19:43, Adam Goryachev wrote: > > > I've updated to SP2, and will re-test in the next few hours, > > > > Excellent news, the issue is completely resolved, and in fact, > > performance is now better than vmware, and better than the old > > original physical box pre-virtualisation. The entire task now > > completed in 30 minutes, the previous best was 40 minutes (ie, prior to > xen). > > Excellent news! > > James, since you suggested it, do you happen to know what it is about > pre-SP2 W2K3 that is so bad? Do those versions beat on the TPR or > something else? > > (Just curious) > Yes it will almost certainly be TPR access. I actually thought MS made the change in SP1 but maybe it was SP2 (don't know if the OP upgraded from RTM to sp2 or sp1 to sp2, but quite possibly I just don't remember :) The change they made means that the TPR doesn't get touched at all anymore, so is much faster. For prior versions (and XP and 2000), GPLPV can patch AMD systems to use the CR8 (I think) registr for TPR access which is much faster. For Intel, the best I could do was cache TPR so that reads were fast... it's still quite a speedup. I thought Xen optimised this for Intel though and my patching wasn't necessary anymore? Or maybe the OP is running a version of xen that doesn't have that feature?? James _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Wed Sep 19 13:01:30 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Wed, 19 Sep 2012 13:01:30 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TEJtP-0003zw-6m; Wed, 19 Sep 2012 13:00:39 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TEJtO-0003zk-8W for xen-users@lists.xen.org; Wed, 19 Sep 2012 13:00:38 +0000 Received: from [85.158.139.83:17832] by server-9.bemta-5.messagelabs.com id AE/24-20529-5F1C9505; Wed, 19 Sep 2012 13:00:37 +0000 X-Env-Sender: mailinglists@websitemanagers.com.au X-Msg-Ref: server-10.tower-182.messagelabs.com!1348059633!31494546!1 X-Originating-IP: [203.56.191.70] X-SpamReason: No, hits=0.0 required=7.0 tests= X-StarScan-Received: X-StarScan-Version: 6.6.1.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 22767 invoked from network); 19 Sep 2012 13:00:36 -0000 Received: from unknown (HELO hammer.websitemanagers.com.au) (203.56.191.70) by server-10.tower-182.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 19 Sep 2012 13:00:36 -0000 Received: (qmail 8513 invoked by uid 1011); 19 Sep 2012 13:00:01 -0000 Received: from 124.246.8.196 by hammer (envelope-from , uid 1008) with qmail-scanner-1.24 (clamdscan: 0.97.3/15370. spamassassin: 3.3.1. Clear:RC:1(124.246.8.196):. Processed in 0.078162 secs); 19 Sep 2012 13:00:01 -0000 Received: from unknown (HELO ?192.168.2.90?) (124.246.8.196) by 0 with SMTP; 19 Sep 2012 13:00:01 -0000 Message-ID: <5059C1D0.6080401@websitemanagers.com.au> Date: Wed, 19 Sep 2012 23:00:00 +1000 From: Adam Goryachev Organization: Website Managers User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:15.0) Gecko/20120827 Thunderbird/15.0 MIME-Version: 1.0 To: James Harper References: <5051D0C5.5070600@websitemanagers.com.au> <1347609879.24226.148.camel@zakaz.uk.xensource.com> <50532CE9.5080601@websitemanagers.com.au> <1347629416.24226.208.camel@zakaz.uk.xensource.com> <505344E8.2030400@websitemanagers.com.au> <505871D6.2060801@websitemanagers.com.au> <1348044096.14977.84.camel@zakaz.uk.xensource.com> <505993A6.2080804@websitemanagers.com.au> <5059B853.9030903@websitemanagers.com.au> <6035A0D088A63A46850C3988ED045A4B29BA8BB9@BITCOM1.int.sbss.com.au> In-Reply-To: <6035A0D088A63A46850C3988ED045A4B29BA8BB9@BITCOM1.int.sbss.com.au> Cc: "xen-users@lists.xen.org" Subject: Re: [Xen-users] SOLVED - Poor Windows 2003 + GPLPV performance compared to VMWare X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org On 19/09/12 22:55, James Harper wrote: >> Excellent news, the issue is completely resolved, and in fact, performance is >> now better than vmware, and better than the old original physical box pre- >> virtualisation. The entire task now completed in 30 minutes, the previous >> best was 40 minutes (ie, prior to xen). >> > I wasn't expecting it to be faster. Are you comparing 2003sp1 under VMWare with 2003sp2 under Xen? Yes, comparing SP1 under VMWare to SP2 under Xen. (So not entirely fair, but at the end of the day, it looks good for me and Xen :) >> I made note before that I was getting around 2500 transactions / sec, and this >> was too slow, just now, I'm getting around 7900 transactions / sec. The only >> change was the installation of Windows 2003 Service Pack 2. > Microsoft updated Windows 2003 with SP2 to remove the use of the TPR register, which was a big performance hit on a virtual system. You can add /PATCHTPR to boot.ini to patch the windows kernel to use an alternate method of TPR access under AMD systems, and to cache reads of TPR under Intel systems, but I thought the xen guys had implemented their own acceleration of this in xen itself? Are you saying the SP1 with the /PATCHTPR will work well (not that I'm interested in this, but just interested), or are you saying the with SP2 you can use /PATCHTPR to improve performance even further (this would be interesting)? Regards, Adam -- Adam Goryachev Website Managers www.websitemanagers.com.au _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Wed Sep 19 13:01:30 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Wed, 19 Sep 2012 13:01:30 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TEJtP-0003zw-6m; Wed, 19 Sep 2012 13:00:39 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TEJtO-0003zk-8W for xen-users@lists.xen.org; Wed, 19 Sep 2012 13:00:38 +0000 Received: from [85.158.139.83:17832] by server-9.bemta-5.messagelabs.com id AE/24-20529-5F1C9505; Wed, 19 Sep 2012 13:00:37 +0000 X-Env-Sender: mailinglists@websitemanagers.com.au X-Msg-Ref: server-10.tower-182.messagelabs.com!1348059633!31494546!1 X-Originating-IP: [203.56.191.70] X-SpamReason: No, hits=0.0 required=7.0 tests= X-StarScan-Received: X-StarScan-Version: 6.6.1.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 22767 invoked from network); 19 Sep 2012 13:00:36 -0000 Received: from unknown (HELO hammer.websitemanagers.com.au) (203.56.191.70) by server-10.tower-182.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 19 Sep 2012 13:00:36 -0000 Received: (qmail 8513 invoked by uid 1011); 19 Sep 2012 13:00:01 -0000 Received: from 124.246.8.196 by hammer (envelope-from , uid 1008) with qmail-scanner-1.24 (clamdscan: 0.97.3/15370. spamassassin: 3.3.1. Clear:RC:1(124.246.8.196):. Processed in 0.078162 secs); 19 Sep 2012 13:00:01 -0000 Received: from unknown (HELO ?192.168.2.90?) (124.246.8.196) by 0 with SMTP; 19 Sep 2012 13:00:01 -0000 Message-ID: <5059C1D0.6080401@websitemanagers.com.au> Date: Wed, 19 Sep 2012 23:00:00 +1000 From: Adam Goryachev Organization: Website Managers User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:15.0) Gecko/20120827 Thunderbird/15.0 MIME-Version: 1.0 To: James Harper References: <5051D0C5.5070600@websitemanagers.com.au> <1347609879.24226.148.camel@zakaz.uk.xensource.com> <50532CE9.5080601@websitemanagers.com.au> <1347629416.24226.208.camel@zakaz.uk.xensource.com> <505344E8.2030400@websitemanagers.com.au> <505871D6.2060801@websitemanagers.com.au> <1348044096.14977.84.camel@zakaz.uk.xensource.com> <505993A6.2080804@websitemanagers.com.au> <5059B853.9030903@websitemanagers.com.au> <6035A0D088A63A46850C3988ED045A4B29BA8BB9@BITCOM1.int.sbss.com.au> In-Reply-To: <6035A0D088A63A46850C3988ED045A4B29BA8BB9@BITCOM1.int.sbss.com.au> Cc: "xen-users@lists.xen.org" Subject: Re: [Xen-users] SOLVED - Poor Windows 2003 + GPLPV performance compared to VMWare X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org On 19/09/12 22:55, James Harper wrote: >> Excellent news, the issue is completely resolved, and in fact, performance is >> now better than vmware, and better than the old original physical box pre- >> virtualisation. The entire task now completed in 30 minutes, the previous >> best was 40 minutes (ie, prior to xen). >> > I wasn't expecting it to be faster. Are you comparing 2003sp1 under VMWare with 2003sp2 under Xen? Yes, comparing SP1 under VMWare to SP2 under Xen. (So not entirely fair, but at the end of the day, it looks good for me and Xen :) >> I made note before that I was getting around 2500 transactions / sec, and this >> was too slow, just now, I'm getting around 7900 transactions / sec. The only >> change was the installation of Windows 2003 Service Pack 2. > Microsoft updated Windows 2003 with SP2 to remove the use of the TPR register, which was a big performance hit on a virtual system. You can add /PATCHTPR to boot.ini to patch the windows kernel to use an alternate method of TPR access under AMD systems, and to cache reads of TPR under Intel systems, but I thought the xen guys had implemented their own acceleration of this in xen itself? Are you saying the SP1 with the /PATCHTPR will work well (not that I'm interested in this, but just interested), or are you saying the with SP2 you can use /PATCHTPR to improve performance even further (this would be interesting)? Regards, Adam -- Adam Goryachev Website Managers www.websitemanagers.com.au _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Wed Sep 19 13:09:12 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Wed, 19 Sep 2012 13:09:12 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TEK0s-00052Q-Os; Wed, 19 Sep 2012 13:08:22 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TEK0r-000527-9b for xen-users@lists.xen.org; Wed, 19 Sep 2012 13:08:21 +0000 Received: from [85.158.139.211:7475] by server-2.bemta-5.messagelabs.com id 24/5C-11456-4C3C9505; Wed, 19 Sep 2012 13:08:20 +0000 X-Env-Sender: james.harper@bendigoit.com.au X-Msg-Ref: server-13.tower-206.messagelabs.com!1348060096!15187273!1 X-Originating-IP: [203.16.207.99] X-SpamReason: No, hits=0.0 required=7.0 tests= X-StarScan-Received: X-StarScan-Version: 6.6.1.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 8656 invoked from network); 19 Sep 2012 13:08:19 -0000 Received: from smtp2.bendigoit.com.au (HELO smtp2.bendigoit.com.au) (203.16.207.99) by server-13.tower-206.messagelabs.com with AES256-SHA encrypted SMTP; 19 Sep 2012 13:08:19 -0000 Received: from [2001:388:e000:712:a5ca:4fd3:14f:ad5d] (helo=BITCOM1.int.sbss.com.au) by smtp2.bendigoit.com.au with esmtp (Exim 4.72) (envelope-from ) id 1TEK0l-000825-0w; Wed, 19 Sep 2012 23:08:15 +1000 Received: from BITCOM1.int.sbss.com.au ([fe80::a5ca:4fd3:14f:ad5d]) by BITCOM1.int.sbss.com.au ([fe80::a5ca:4fd3:14f:ad5d%12]) with mapi id 14.01.0379.000; Wed, 19 Sep 2012 23:08:14 +1000 From: James Harper To: Adam Goryachev Thread-Topic: [Xen-users] SOLVED - Poor Windows 2003 + GPLPV performance compared to VMWare Thread-Index: AQHNlmNftMdt2SzZFUqD/VEO8wSySJeRndjg//9bGACAAKkxAA== Date: Wed, 19 Sep 2012 13:08:13 +0000 Message-ID: <6035A0D088A63A46850C3988ED045A4B29BA8CB2@BITCOM1.int.sbss.com.au> References: <5051D0C5.5070600@websitemanagers.com.au> <1347609879.24226.148.camel@zakaz.uk.xensource.com> <50532CE9.5080601@websitemanagers.com.au> <1347629416.24226.208.camel@zakaz.uk.xensource.com> <505344E8.2030400@websitemanagers.com.au> <505871D6.2060801@websitemanagers.com.au> <1348044096.14977.84.camel@zakaz.uk.xensource.com> <505993A6.2080804@websitemanagers.com.au> <5059B853.9030903@websitemanagers.com.au> <6035A0D088A63A46850C3988ED045A4B29BA8BB9@BITCOM1.int.sbss.com.au> <5059C1D0.6080401@websitemanagers.com.au> In-Reply-To: <5059C1D0.6080401@websitemanagers.com.au> Accept-Language: en-AU, en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [172.16.3.132] x-tm-as-product-ver: SMEX-10.2.0.2087-7.000.1014-19192.007 x-tm-as-result: No--34.498800-0.000000-31 x-tm-as-user-approved-sender: Yes x-tm-as-user-blocked-sender: No MIME-Version: 1.0 X-Really-From-Bendigo-IT: magichashvalue Cc: "xen-users@lists.xen.org" Subject: Re: [Xen-users] SOLVED - Poor Windows 2003 + GPLPV performance compared to VMWare X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org > > Microsoft updated Windows 2003 with SP2 to remove the use of the TPR > > register, which was a big performance hit on a virtual system. You can add > > /PATCHTPR to boot.ini to patch the windows kernel to use an alternate > > method of TPR access under AMD systems, and to cache reads of TPR under > > Intel systems, but I thought the xen guys had implemented their own > > acceleration of this in xen itself? > > Are you saying the SP1 with the /PATCHTPR will work well (not that I'm > interested in this, but just interested), or are you saying the with SP2 > you can use /PATCHTPR to improve performance even further (this would be > interesting)? > The former. The TPR register is what Windows uses to manage interrupt priorities, and is accessed many many times per second. Every access causes a VMEXIT, so a whole lot of work gets done every time it is accessed. /PATCHTPR modifies the windows kernel a bit to change the way this is accessed. With SP2, Microsoft modified the kernel to manage interrupt priorities a different way so the TPR register is not used at all, which virtualises much better. /PATCHTPR is still useful for XP and 2000 which don't have these optimisations though. James _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Wed Sep 19 13:09:12 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Wed, 19 Sep 2012 13:09:12 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TEK0s-00052Q-Os; Wed, 19 Sep 2012 13:08:22 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TEK0r-000527-9b for xen-users@lists.xen.org; Wed, 19 Sep 2012 13:08:21 +0000 Received: from [85.158.139.211:7475] by server-2.bemta-5.messagelabs.com id 24/5C-11456-4C3C9505; Wed, 19 Sep 2012 13:08:20 +0000 X-Env-Sender: james.harper@bendigoit.com.au X-Msg-Ref: server-13.tower-206.messagelabs.com!1348060096!15187273!1 X-Originating-IP: [203.16.207.99] X-SpamReason: No, hits=0.0 required=7.0 tests= X-StarScan-Received: X-StarScan-Version: 6.6.1.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 8656 invoked from network); 19 Sep 2012 13:08:19 -0000 Received: from smtp2.bendigoit.com.au (HELO smtp2.bendigoit.com.au) (203.16.207.99) by server-13.tower-206.messagelabs.com with AES256-SHA encrypted SMTP; 19 Sep 2012 13:08:19 -0000 Received: from [2001:388:e000:712:a5ca:4fd3:14f:ad5d] (helo=BITCOM1.int.sbss.com.au) by smtp2.bendigoit.com.au with esmtp (Exim 4.72) (envelope-from ) id 1TEK0l-000825-0w; Wed, 19 Sep 2012 23:08:15 +1000 Received: from BITCOM1.int.sbss.com.au ([fe80::a5ca:4fd3:14f:ad5d]) by BITCOM1.int.sbss.com.au ([fe80::a5ca:4fd3:14f:ad5d%12]) with mapi id 14.01.0379.000; Wed, 19 Sep 2012 23:08:14 +1000 From: James Harper To: Adam Goryachev Thread-Topic: [Xen-users] SOLVED - Poor Windows 2003 + GPLPV performance compared to VMWare Thread-Index: AQHNlmNftMdt2SzZFUqD/VEO8wSySJeRndjg//9bGACAAKkxAA== Date: Wed, 19 Sep 2012 13:08:13 +0000 Message-ID: <6035A0D088A63A46850C3988ED045A4B29BA8CB2@BITCOM1.int.sbss.com.au> References: <5051D0C5.5070600@websitemanagers.com.au> <1347609879.24226.148.camel@zakaz.uk.xensource.com> <50532CE9.5080601@websitemanagers.com.au> <1347629416.24226.208.camel@zakaz.uk.xensource.com> <505344E8.2030400@websitemanagers.com.au> <505871D6.2060801@websitemanagers.com.au> <1348044096.14977.84.camel@zakaz.uk.xensource.com> <505993A6.2080804@websitemanagers.com.au> <5059B853.9030903@websitemanagers.com.au> <6035A0D088A63A46850C3988ED045A4B29BA8BB9@BITCOM1.int.sbss.com.au> <5059C1D0.6080401@websitemanagers.com.au> In-Reply-To: <5059C1D0.6080401@websitemanagers.com.au> Accept-Language: en-AU, en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [172.16.3.132] x-tm-as-product-ver: SMEX-10.2.0.2087-7.000.1014-19192.007 x-tm-as-result: No--34.498800-0.000000-31 x-tm-as-user-approved-sender: Yes x-tm-as-user-blocked-sender: No MIME-Version: 1.0 X-Really-From-Bendigo-IT: magichashvalue Cc: "xen-users@lists.xen.org" Subject: Re: [Xen-users] SOLVED - Poor Windows 2003 + GPLPV performance compared to VMWare X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org > > Microsoft updated Windows 2003 with SP2 to remove the use of the TPR > > register, which was a big performance hit on a virtual system. You can add > > /PATCHTPR to boot.ini to patch the windows kernel to use an alternate > > method of TPR access under AMD systems, and to cache reads of TPR under > > Intel systems, but I thought the xen guys had implemented their own > > acceleration of this in xen itself? > > Are you saying the SP1 with the /PATCHTPR will work well (not that I'm > interested in this, but just interested), or are you saying the with SP2 > you can use /PATCHTPR to improve performance even further (this would be > interesting)? > The former. The TPR register is what Windows uses to manage interrupt priorities, and is accessed many many times per second. Every access causes a VMEXIT, so a whole lot of work gets done every time it is accessed. /PATCHTPR modifies the windows kernel a bit to change the way this is accessed. With SP2, Microsoft modified the kernel to manage interrupt priorities a different way so the TPR register is not used at all, which virtualises much better. /PATCHTPR is still useful for XP and 2000 which don't have these optimisations though. James _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Wed Sep 19 13:13:40 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Wed, 19 Sep 2012 13:13:40 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TEK5F-0005bT-7X; Wed, 19 Sep 2012 13:12:53 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TEK5D-0005bG-Nf for xen-users@lists.xen.org; Wed, 19 Sep 2012 13:12:51 +0000 Received: from [85.158.143.35:48389] by server-3.bemta-4.messagelabs.com id E0/95-10986-3D4C9505; Wed, 19 Sep 2012 13:12:51 +0000 X-Env-Sender: Ian.Campbell@citrix.com X-Msg-Ref: server-2.tower-21.messagelabs.com!1348060369!7978778!1 X-Originating-IP: [62.200.22.115] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogNjIuMjAwLjIyLjExNSA9PiAxMTAxNzU=\n X-StarScan-Received: X-StarScan-Version: 6.6.1.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 16332 invoked from network); 19 Sep 2012 13:12:50 -0000 Received: from smtp.ctxuk.citrix.com (HELO SMTP.EU.CITRIX.COM) (62.200.22.115) by server-2.tower-21.messagelabs.com with RC4-SHA encrypted SMTP; 19 Sep 2012 13:12:50 -0000 X-IronPort-AV: E=Sophos;i="4.80,447,1344211200"; d="scan'208";a="14631539" Received: from lonpmailmx01.citrite.net ([10.30.203.162]) by LONPIPO01.EU.CITRIX.COM with ESMTP/TLS/RC4-MD5; 19 Sep 2012 13:12:49 +0000 Received: from [10.80.2.42] (10.80.2.42) by LONPMAILMX01.citrite.net (10.30.203.162) with Microsoft SMTP Server id 8.3.279.1; Wed, 19 Sep 2012 14:12:49 +0100 Message-ID: <1348060368.14977.125.camel@zakaz.uk.xensource.com> From: Ian Campbell To: James Harper Date: Wed, 19 Sep 2012 14:12:48 +0100 In-Reply-To: <6035A0D088A63A46850C3988ED045A4B29BA8C0B@BITCOM1.int.sbss.com.au> References: <5051D0C5.5070600@websitemanagers.com.au> <1347609879.24226.148.camel@zakaz.uk.xensource.com> <50532CE9.5080601@websitemanagers.com.au> <1347629416.24226.208.camel@zakaz.uk.xensource.com> <505344E8.2030400@websitemanagers.com.au> <505871D6.2060801@websitemanagers.com.au> <1348044096.14977.84.camel@zakaz.uk.xensource.com> <505993A6.2080804@websitemanagers.com.au> <5059B853.9030903@websitemanagers.com.au> <1348057647.14977.104.camel@zakaz.uk.xensource.com> <6035A0D088A63A46850C3988ED045A4B29BA8C0B@BITCOM1.int.sbss.com.au> Organization: Citrix Systems, Inc. X-Mailer: Evolution 3.4.3-1 MIME-Version: 1.0 Cc: "xen-users@lists.xen.org" , Adam Goryachev Subject: Re: [Xen-users] SOLVED - Poor Windows 2003 + GPLPV performance compared to VMWare X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org On Wed, 2012-09-19 at 14:00 +0100, James Harper wrote: > > > > On Wed, 2012-09-19 at 13:19 +0100, Adam Goryachev wrote: > > > On 19/09/12 19:43, Adam Goryachev wrote: > > > > I've updated to SP2, and will re-test in the next few hours, > > > > > > Excellent news, the issue is completely resolved, and in fact, > > > performance is now better than vmware, and better than the old > > > original physical box pre-virtualisation. The entire task now > > > completed in 30 minutes, the previous best was 40 minutes (ie, prior to > > xen). > > > > Excellent news! > > > > James, since you suggested it, do you happen to know what it is about > > pre-SP2 W2K3 that is so bad? Do those versions beat on the TPR or > > something else? > > > > (Just curious) > > > > Yes it will almost certainly be TPR access. I actually thought MS made > the change in SP1 but maybe it was SP2 (don't know if the OP upgraded > from RTM to sp2 or sp1 to sp2, but quite possibly I just don't > remember :) > > The change they made means that the TPR doesn't get touched at all > anymore, so is much faster. > > For prior versions (and XP and 2000), GPLPV can patch AMD systems to > use the CR8 (I think) registr for TPR access which is much faster. For > Intel, the best I could do was cache TPR so that reads were fast... > it's still quite a speedup. I thought Xen optimised this for Intel > though and my patching wasn't necessary anymore? Or maybe the OP is > running a version of xen that doesn't have that feature?? I think there was a h/w feature introduced at some point on both AMD and Intel which also optimised these vmexits away. I'm not 100% sure of the specifics though. Ian _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Wed Sep 19 13:13:40 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Wed, 19 Sep 2012 13:13:40 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TEK5F-0005bT-7X; Wed, 19 Sep 2012 13:12:53 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TEK5D-0005bG-Nf for xen-users@lists.xen.org; Wed, 19 Sep 2012 13:12:51 +0000 Received: from [85.158.143.35:48389] by server-3.bemta-4.messagelabs.com id E0/95-10986-3D4C9505; Wed, 19 Sep 2012 13:12:51 +0000 X-Env-Sender: Ian.Campbell@citrix.com X-Msg-Ref: server-2.tower-21.messagelabs.com!1348060369!7978778!1 X-Originating-IP: [62.200.22.115] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogNjIuMjAwLjIyLjExNSA9PiAxMTAxNzU=\n X-StarScan-Received: X-StarScan-Version: 6.6.1.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 16332 invoked from network); 19 Sep 2012 13:12:50 -0000 Received: from smtp.ctxuk.citrix.com (HELO SMTP.EU.CITRIX.COM) (62.200.22.115) by server-2.tower-21.messagelabs.com with RC4-SHA encrypted SMTP; 19 Sep 2012 13:12:50 -0000 X-IronPort-AV: E=Sophos;i="4.80,447,1344211200"; d="scan'208";a="14631539" Received: from lonpmailmx01.citrite.net ([10.30.203.162]) by LONPIPO01.EU.CITRIX.COM with ESMTP/TLS/RC4-MD5; 19 Sep 2012 13:12:49 +0000 Received: from [10.80.2.42] (10.80.2.42) by LONPMAILMX01.citrite.net (10.30.203.162) with Microsoft SMTP Server id 8.3.279.1; Wed, 19 Sep 2012 14:12:49 +0100 Message-ID: <1348060368.14977.125.camel@zakaz.uk.xensource.com> From: Ian Campbell To: James Harper Date: Wed, 19 Sep 2012 14:12:48 +0100 In-Reply-To: <6035A0D088A63A46850C3988ED045A4B29BA8C0B@BITCOM1.int.sbss.com.au> References: <5051D0C5.5070600@websitemanagers.com.au> <1347609879.24226.148.camel@zakaz.uk.xensource.com> <50532CE9.5080601@websitemanagers.com.au> <1347629416.24226.208.camel@zakaz.uk.xensource.com> <505344E8.2030400@websitemanagers.com.au> <505871D6.2060801@websitemanagers.com.au> <1348044096.14977.84.camel@zakaz.uk.xensource.com> <505993A6.2080804@websitemanagers.com.au> <5059B853.9030903@websitemanagers.com.au> <1348057647.14977.104.camel@zakaz.uk.xensource.com> <6035A0D088A63A46850C3988ED045A4B29BA8C0B@BITCOM1.int.sbss.com.au> Organization: Citrix Systems, Inc. X-Mailer: Evolution 3.4.3-1 MIME-Version: 1.0 Cc: "xen-users@lists.xen.org" , Adam Goryachev Subject: Re: [Xen-users] SOLVED - Poor Windows 2003 + GPLPV performance compared to VMWare X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org On Wed, 2012-09-19 at 14:00 +0100, James Harper wrote: > > > > On Wed, 2012-09-19 at 13:19 +0100, Adam Goryachev wrote: > > > On 19/09/12 19:43, Adam Goryachev wrote: > > > > I've updated to SP2, and will re-test in the next few hours, > > > > > > Excellent news, the issue is completely resolved, and in fact, > > > performance is now better than vmware, and better than the old > > > original physical box pre-virtualisation. The entire task now > > > completed in 30 minutes, the previous best was 40 minutes (ie, prior to > > xen). > > > > Excellent news! > > > > James, since you suggested it, do you happen to know what it is about > > pre-SP2 W2K3 that is so bad? Do those versions beat on the TPR or > > something else? > > > > (Just curious) > > > > Yes it will almost certainly be TPR access. I actually thought MS made > the change in SP1 but maybe it was SP2 (don't know if the OP upgraded > from RTM to sp2 or sp1 to sp2, but quite possibly I just don't > remember :) > > The change they made means that the TPR doesn't get touched at all > anymore, so is much faster. > > For prior versions (and XP and 2000), GPLPV can patch AMD systems to > use the CR8 (I think) registr for TPR access which is much faster. For > Intel, the best I could do was cache TPR so that reads were fast... > it's still quite a speedup. I thought Xen optimised this for Intel > though and my patching wasn't necessary anymore? Or maybe the OP is > running a version of xen that doesn't have that feature?? I think there was a h/w feature introduced at some point on both AMD and Intel which also optimised these vmexits away. I'm not 100% sure of the specifics though. Ian _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Wed Sep 19 16:06:43 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Wed, 19 Sep 2012 16:06:43 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TEMm4-0001u3-JT; Wed, 19 Sep 2012 16:05:16 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TEMm2-0001tI-LU for xen-users@lists.xen.org; Wed, 19 Sep 2012 16:05:14 +0000 Received: from [85.158.139.83:18030] by server-4.bemta-5.messagelabs.com id 01/81-23042-93DE9505; Wed, 19 Sep 2012 16:05:13 +0000 X-Env-Sender: lars.kurth.xen@gmail.com X-Msg-Ref: server-5.tower-182.messagelabs.com!1348070710!30908264!1 X-Originating-IP: [209.85.212.45] X-SpamReason: No, hits=0.9 required=7.0 tests=HTML_40_50,HTML_MESSAGE, RCVD_BY_IP X-StarScan-Received: X-StarScan-Version: 6.6.1.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 27776 invoked from network); 19 Sep 2012 16:05:11 -0000 Received: from mail-vb0-f45.google.com (HELO mail-vb0-f45.google.com) (209.85.212.45) by server-5.tower-182.messagelabs.com with RC4-SHA encrypted SMTP; 19 Sep 2012 16:05:11 -0000 Received: by vbip1 with SMTP id p1so1680774vbi.32 for ; Wed, 19 Sep 2012 09:05:09 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=sender:message-id:date:from:reply-to:user-agent:mime-version:to :subject:content-type; bh=jntIgkVlvCEDH4f+xVZ4PX0SpX0DBEPD8Jo6+5W6oP8=; b=C8HIxbRAg32B3/SM7TuogTZod1PnWsHvv7mhQmispJE9htfdJWVBBtUnGzYJiaS7dw G4H5RPKO+qpLHxMJI0gCtF2zjOM/4xzMAfko3p+sG/xaHWxVCumybX73KR01225do+Qy 7B14GPkGroKa+Lu9Hr1nZ31evouhPSaHIroyUPyomYRMHZ4KeE/5Xccny+wH9QGqzYZB u278t79/H2GfbdedIrFHQ3oGM5hGshC4nH8EwmOWfobzYvmnbhaTmlgTCeQ+ihTmoe34 6BAij0mwiJmPWPrGEsuX/sP2/fO6Asub+8u2SM1kX4KorNfK4RQUhbrdaZzfb5vjJO8i Nw8w== Received: by 10.221.2.76 with SMTP id nt12mr2183375vcb.12.1348070709689; Wed, 19 Sep 2012 09:05:09 -0700 (PDT) Received: from [172.16.26.11] (firewall.ctxuk.citrix.com. [62.200.22.2]) by mx.google.com with ESMTPS id j13sm564537vej.3.2012.09.19.09.05.06 (version=SSLv3 cipher=OTHER); Wed, 19 Sep 2012 09:05:08 -0700 (PDT) Message-ID: <5059ED2F.9080507@xen.org> Date: Wed, 19 Sep 2012 17:05:03 +0100 From: Lars Kurth User-Agent: Mozilla/5.0 (Windows NT 6.1; rv:15.0) Gecko/20120907 Thunderbird/15.0.1 MIME-Version: 1.0 To: "xen-devel@lists.xen.org" , xen-users@lists.xen.org, "xen-api@lists.xen.org" , xen-arm@lists.xen.org Subject: [Xen-users] Xen Document Day: Sept 24th, 2012 on IRC freenode #xendocs X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list Reply-To: lars.kurth@xen.org List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============0054762311931401561==" Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org This is a multi-part message in MIME format. --===============0054762311931401561== Content-Type: multipart/alternative; boundary="------------060509060401040904060408" This is a multi-part message in MIME format. --------------060509060401040904060408 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Hi, everybody. A quick reminder that the next Xen Document Day is happening next Monday. More info on document days at http://wiki.xen.org/wiki/Xen_Document_Days Hope to see you on IRC! Feel free to add stuff to the TODO list (http://wiki.xen.org/wiki/Xen_Document_Days/TODO) or put your name besides an item if you intend to work on it. I just cleaned up the list in preparation for Monday. Best Regards Lars ********************* * Xen Document Days * ********************* We have another Xen document day come up next Monday. Xen Document Days are for people who care about Xen Documentation and want to improve it. We introduced Documentation Days, because working on documentation in parallel with like minded-people, is just more fun than working alone! Everybody who can contribute is welcome to join! For a list of items that need work, check out the community maintained TODO list (http://wiki.xen.org/wiki/Xen_Document_Days/TODO). Of course, you can work on anything you like: the list just provides suggestions. How do I participate? ===================== - Join us on IRC: freenode channel #xendocs - Tell people what you intend to work on (to avoid doing something somebody else is already working on) - Fix some documentation - Help others - And above all: have fun! --------------060509060401040904060408 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit
Hi,

everybody. A quick reminder that the next Xen Document Day is happening next Monday. More info on document days at http://wiki.xen.org/wiki/Xen_Document_Days

Hope to see you on IRC! Feel free to add stuff to the TODO list (http://wiki.xen.org/wiki/Xen_Document_Days/TODO) or put your name besides an item if you intend to work on it. I just cleaned up the list in preparation for Monday.

Best Regards
Lars

*********************
* Xen Document Days *
*********************

We have another Xen document day come up next Monday. Xen Document Days are for people who care about Xen Documentation and want to improve it. We introduced Documentation Days, because working on documentation in parallel with like minded-people, is just more fun than working alone! Everybody who can contribute is welcome to join!

For a list of items that need work, check out the community maintained TODO list (http://wiki.xen.org/wiki/Xen_Document_Days/TODO). Of course, you can work on anything you like: the list just provides suggestions.

How do I participate?
=====================

- Join us on IRC: freenode channel #xendocs
- Tell people what you intend to work on (to avoid doing something somebody
  else is already working on)
- Fix some documentation
- Help others
- And above all: have fun!
--------------060509060401040904060408-- --===============0054762311931401561== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users --===============0054762311931401561==-- From xen-users-bounces@lists.xen.org Wed Sep 19 16:06:43 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Wed, 19 Sep 2012 16:06:43 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TEMm4-0001u3-JT; Wed, 19 Sep 2012 16:05:16 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TEMm2-0001tI-LU for xen-users@lists.xen.org; Wed, 19 Sep 2012 16:05:14 +0000 Received: from [85.158.139.83:18030] by server-4.bemta-5.messagelabs.com id 01/81-23042-93DE9505; Wed, 19 Sep 2012 16:05:13 +0000 X-Env-Sender: lars.kurth.xen@gmail.com X-Msg-Ref: server-5.tower-182.messagelabs.com!1348070710!30908264!1 X-Originating-IP: [209.85.212.45] X-SpamReason: No, hits=0.9 required=7.0 tests=HTML_40_50,HTML_MESSAGE, RCVD_BY_IP X-StarScan-Received: X-StarScan-Version: 6.6.1.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 27776 invoked from network); 19 Sep 2012 16:05:11 -0000 Received: from mail-vb0-f45.google.com (HELO mail-vb0-f45.google.com) (209.85.212.45) by server-5.tower-182.messagelabs.com with RC4-SHA encrypted SMTP; 19 Sep 2012 16:05:11 -0000 Received: by vbip1 with SMTP id p1so1680774vbi.32 for ; Wed, 19 Sep 2012 09:05:09 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=sender:message-id:date:from:reply-to:user-agent:mime-version:to :subject:content-type; bh=jntIgkVlvCEDH4f+xVZ4PX0SpX0DBEPD8Jo6+5W6oP8=; b=C8HIxbRAg32B3/SM7TuogTZod1PnWsHvv7mhQmispJE9htfdJWVBBtUnGzYJiaS7dw G4H5RPKO+qpLHxMJI0gCtF2zjOM/4xzMAfko3p+sG/xaHWxVCumybX73KR01225do+Qy 7B14GPkGroKa+Lu9Hr1nZ31evouhPSaHIroyUPyomYRMHZ4KeE/5Xccny+wH9QGqzYZB u278t79/H2GfbdedIrFHQ3oGM5hGshC4nH8EwmOWfobzYvmnbhaTmlgTCeQ+ihTmoe34 6BAij0mwiJmPWPrGEsuX/sP2/fO6Asub+8u2SM1kX4KorNfK4RQUhbrdaZzfb5vjJO8i Nw8w== Received: by 10.221.2.76 with SMTP id nt12mr2183375vcb.12.1348070709689; Wed, 19 Sep 2012 09:05:09 -0700 (PDT) Received: from [172.16.26.11] (firewall.ctxuk.citrix.com. [62.200.22.2]) by mx.google.com with ESMTPS id j13sm564537vej.3.2012.09.19.09.05.06 (version=SSLv3 cipher=OTHER); Wed, 19 Sep 2012 09:05:08 -0700 (PDT) Message-ID: <5059ED2F.9080507@xen.org> Date: Wed, 19 Sep 2012 17:05:03 +0100 From: Lars Kurth User-Agent: Mozilla/5.0 (Windows NT 6.1; rv:15.0) Gecko/20120907 Thunderbird/15.0.1 MIME-Version: 1.0 To: "xen-devel@lists.xen.org" , xen-users@lists.xen.org, "xen-api@lists.xen.org" , xen-arm@lists.xen.org Subject: [Xen-users] Xen Document Day: Sept 24th, 2012 on IRC freenode #xendocs X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list Reply-To: lars.kurth@xen.org List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============0054762311931401561==" Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org This is a multi-part message in MIME format. --===============0054762311931401561== Content-Type: multipart/alternative; boundary="------------060509060401040904060408" This is a multi-part message in MIME format. --------------060509060401040904060408 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Hi, everybody. A quick reminder that the next Xen Document Day is happening next Monday. More info on document days at http://wiki.xen.org/wiki/Xen_Document_Days Hope to see you on IRC! Feel free to add stuff to the TODO list (http://wiki.xen.org/wiki/Xen_Document_Days/TODO) or put your name besides an item if you intend to work on it. I just cleaned up the list in preparation for Monday. Best Regards Lars ********************* * Xen Document Days * ********************* We have another Xen document day come up next Monday. Xen Document Days are for people who care about Xen Documentation and want to improve it. We introduced Documentation Days, because working on documentation in parallel with like minded-people, is just more fun than working alone! Everybody who can contribute is welcome to join! For a list of items that need work, check out the community maintained TODO list (http://wiki.xen.org/wiki/Xen_Document_Days/TODO). Of course, you can work on anything you like: the list just provides suggestions. How do I participate? ===================== - Join us on IRC: freenode channel #xendocs - Tell people what you intend to work on (to avoid doing something somebody else is already working on) - Fix some documentation - Help others - And above all: have fun! --------------060509060401040904060408 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit
Hi,

everybody. A quick reminder that the next Xen Document Day is happening next Monday. More info on document days at http://wiki.xen.org/wiki/Xen_Document_Days

Hope to see you on IRC! Feel free to add stuff to the TODO list (http://wiki.xen.org/wiki/Xen_Document_Days/TODO) or put your name besides an item if you intend to work on it. I just cleaned up the list in preparation for Monday.

Best Regards
Lars

*********************
* Xen Document Days *
*********************

We have another Xen document day come up next Monday. Xen Document Days are for people who care about Xen Documentation and want to improve it. We introduced Documentation Days, because working on documentation in parallel with like minded-people, is just more fun than working alone! Everybody who can contribute is welcome to join!

For a list of items that need work, check out the community maintained TODO list (http://wiki.xen.org/wiki/Xen_Document_Days/TODO). Of course, you can work on anything you like: the list just provides suggestions.

How do I participate?
=====================

- Join us on IRC: freenode channel #xendocs
- Tell people what you intend to work on (to avoid doing something somebody
  else is already working on)
- Fix some documentation
- Help others
- And above all: have fun!
--------------060509060401040904060408-- --===============0054762311931401561== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users --===============0054762311931401561==-- From xen-users-bounces@lists.xen.org Wed Sep 19 16:44:43 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Wed, 19 Sep 2012 16:44:43 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TENNJ-00031N-A0; Wed, 19 Sep 2012 16:43:45 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TENNH-00030r-LP for xen-users@lists.xen.org; Wed, 19 Sep 2012 16:43:44 +0000 Received: from [85.158.143.35:18115] by server-1.bemta-4.messagelabs.com id F4/39-05684-C36F9505; Wed, 19 Sep 2012 16:43:40 +0000 X-Env-Sender: singapore.mr.teo.en.ming@gmail.com X-Msg-Ref: server-8.tower-21.messagelabs.com!1348073014!15743053!1 X-Originating-IP: [209.85.160.45] X-SpamReason: No, hits=0.3 required=7.0 tests=ML_RADAR_SPEW_LINKS_14, RCVD_BY_IP,spamassassin: X-StarScan-Received: X-StarScan-Version: 6.6.1.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 8473 invoked from network); 19 Sep 2012 16:43:36 -0000 Received: from mail-pb0-f45.google.com (HELO mail-pb0-f45.google.com) (209.85.160.45) by server-8.tower-21.messagelabs.com with RC4-SHA encrypted SMTP; 19 Sep 2012 16:43:36 -0000 Received: by pbbrp12 with SMTP id rp12so2940985pbb.32 for ; Wed, 19 Sep 2012 09:43:34 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:disposition-notification-to:date:from:user-agent :mime-version:to:subject:content-type; bh=NhAEaT4RaQ8zkEU7XpSw6qrmedYXSJI/PPxUpKjERxI=; b=PY64vJkQntPimOZfS+lN+Kc9Wdu9kNOYzaynZygyOix+/LXQ7f5uzDMHhsZ/8W/6wi /dd9Y3cnqR46x9GuSX0ecbVPok8fGdTmI5JcLvL3gL8DFGksVOE/750FE85+IFYg00MS JXYNHf6Ap7UAPsq5VL2eIlPYgdaO4pYTuSqjlnaisF3xVC+H2yLjnbnrSnlAhqtjplZe j+RnW+1Wv35p2lDtgtlDXxUJRjs4BHY9Hz/lwnRha5OPSw/JMw+Hsz9ZOkzaZDY2Nb/J ZEFiji9ByKzqLQkTgHaxwHhGDksSDYKMA242Iyb6suSp567j94rqZXLqdiRucI1IVmAt xASg== Received: by 10.68.116.228 with SMTP id jz4mr8786686pbb.166.1348073014138; Wed, 19 Sep 2012 09:43:34 -0700 (PDT) Received: from [192.168.1.2] (cm70.gamma203.maxonline.com.sg. [202.156.203.70]) by mx.google.com with ESMTPS id b6sm984792paz.9.2012.09.19.09.43.31 (version=SSLv3 cipher=OTHER); Wed, 19 Sep 2012 09:43:33 -0700 (PDT) Message-ID: <5059F632.3050808@gmail.com> Date: Thu, 20 Sep 2012 00:43:30 +0800 From: "Teo En Ming (Zhang Enming)" User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:10.0.2) Gecko/20120216 Thunderbird/10.0.2 MIME-Version: 1.0 To: "xen-users@lists.xen.org" , "xen-devel@lists.xen.org" , 'Teo En Ming' Content-Type: multipart/mixed; boundary="------------060301030907070908060303" Subject: [Xen-users] VGA Passthrough with Xen 4.3-unstable? X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org This is a multi-part message in MIME format. --------------060301030907070908060303 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Dear All, I have tried to apply VGA passthrough patches hosted at Jean David Techer's website to Xen 4.3-unstable. However, I cannot get VGA passthrough to work with Xen 4.3-unstable. Are the VGA passthrough patches hosted at David Techer's website incompatible with Xen 4.3-unstable? This is David Techer's website: http://www.davidgis.fr/blog/index.php?2011/12/07/860-xen-42unstable-patches-for-vga-pass-through I have also provided error logs in this email for troubleshooting purposes. Please advise. Thank you very much. -- Yours sincerely, Mr. Teo En Ming (Zhang Enming) Singapore --------------060301030907070908060303 Content-Type: text/x-log; name="qemu-dm-Windows8.log" Content-Transfer-Encoding: 7bit Content-Disposition: attachment; filename="qemu-dm-Windows8.log" domid: 21 Strip off blktap sub-type prefix to /etc/xen/images/windows8.img (drv 'aio') Using file /etc/xen/images/windows8.img in read-write mode Strip off blktap sub-type prefix to /home/flyon/windows8.iso (drv 'aio') Using file /home/flyon/windows8.iso in read-only mode Watching /local/domain/0/device-model/21/logdirty/cmd Watching /local/domain/0/device-model/21/command Watching /local/domain/21/cpu qemu_map_cache_init nr_buckets = 10000 size 4194304 shared page at pfn feffd buffered io page at pfn feffb Guest uuid = 40290d87-cbd9-4656-841b-ba3d95621163 Register xen platform. Done register platform. platform_fixed_ioport: changed ro/rw state of ROM memory area. now is rw state. xs_read(/local/domain/0/device-model/21/xen_extended_power_mgmt): read error medium change watch on `hdc' (index: 1): aio:/home/flyon/windows8.iso I/O request not ready: 0, ptr: 0, port: 0, data: 0, count: 0, size: 0 Log-dirty: no command yet. I/O request not ready: 0, ptr: 0, port: 0, data: 0, count: 0, size: 0 I/O request not ready: 0, ptr: 0, port: 0, data: 0, count: 0, size: 0 vcpu-set: watch node error. I/O request not ready: 0, ptr: 0, port: 0, data: 0, count: 0, size: 0 xs_read(/local/domain/21/log-throttling): read error qemu: ignoring not-understood drive `/local/domain/21/log-throttling' medium change watch on `/local/domain/21/log-throttling' - unknown device, ignored I/O request not ready: 0, ptr: 0, port: 0, data: 0, count: 0, size: 0 I/O request not ready: 0, ptr: 0, port: 0, data: 0, count: 0, size: 0 I/O request not ready: 0, ptr: 0, port: 0, data: 0, count: 0, size: 0 I/O request not ready: 0, ptr: 0, port: 0, data: 0, count: 0, size: 0 I/O request not ready: 0, ptr: 0, port: 0, data: 0, count: 0, size: 0 I/O request not ready: 0, ptr: 0, port: 0, data: 0, count: 0, size: 0 I/O request not ready: 0, ptr: 0, port: 0, data: 0, count: 0, size: 0 I/O request not ready: 0, ptr: 0, port: 0, data: 0, count: 0, size: 0 platform_fixed_ioport: changed ro/rw state of ROM memory area. now is rw state. platform_fixed_ioport: changed ro/rw state of ROM memory area. now is ro state. --------------060301030907070908060303 Content-Type: text/plain; name="qemu-dm-Windows8.log.1" Content-Transfer-Encoding: 7bit Content-Disposition: attachment; filename="qemu-dm-Windows8.log.1" domid: 20 Strip off blktap sub-type prefix to /etc/xen/images/windows8.img (drv 'aio') Using file /etc/xen/images/windows8.img in read-write mode Strip off blktap sub-type prefix to /home/flyon/windows8.iso (drv 'aio') Using file /home/flyon/windows8.iso in read-only mode Watching /local/domain/0/device-model/20/logdirty/cmd Watching /local/domain/0/device-model/20/command Watching /local/domain/20/cpu qemu_map_cache_init nr_buckets = 10000 size 4194304 shared page at pfn feffd buffered io page at pfn feffb Guest uuid = 4a77731a-8b25-4fd8-ac7c-f4d607784917 Register xen platform. Done register platform. platform_fixed_ioport: changed ro/rw state of ROM memory area. now is rw state. xs_read(/local/domain/0/device-model/20/xen_extended_power_mgmt): read error medium change watch on `hdc' (index: 1): aio:/home/flyon/windows8.iso I/O request not ready: 0, ptr: 0, port: 0, data: 0, count: 0, size: 0 Log-dirty: no command yet. I/O request not ready: 0, ptr: 0, port: 0, data: 0, count: 0, size: 0 I/O request not ready: 0, ptr: 0, port: 0, data: 0, count: 0, size: 0 vcpu-set: watch node error. I/O request not ready: 0, ptr: 0, port: 0, data: 0, count: 0, size: 0 xs_read(/local/domain/20/log-throttling): read error qemu: ignoring not-understood drive `/local/domain/20/log-throttling' medium change watch on `/local/domain/20/log-throttling' - unknown device, ignored I/O request not ready: 0, ptr: 0, port: 0, data: 0, count: 0, size: 0 I/O request not ready: 0, ptr: 0, port: 0, data: 0, count: 0, size: 0 I/O request not ready: 0, ptr: 0, port: 0, data: 0, count: 0, size: 0 I/O request not ready: 0, ptr: 0, port: 0, data: 0, count: 0, size: 0 I/O request not ready: 0, ptr: 0, port: 0, data: 0, count: 0, size: 0 I/O request not ready: 0, ptr: 0, port: 0, data: 0, count: 0, size: 0 I/O request not ready: 0, ptr: 0, port: 0, data: 0, count: 0, size: 0 I/O request not ready: 0, ptr: 0, port: 0, data: 0, count: 0, size: 0 platform_fixed_ioport: changed ro/rw state of ROM memory area. now is rw state. platform_fixed_ioport: changed ro/rw state of ROM memory area. now is ro state. reset requested in cpu_handle_ioreq. Issued domain 20 reboot --------------060301030907070908060303 Content-Type: text/plain; name="qemu-dm-Windows8.log.2" Content-Transfer-Encoding: 7bit Content-Disposition: attachment; filename="qemu-dm-Windows8.log.2" domid: 19 Strip off blktap sub-type prefix to /etc/xen/images/windows8.img (drv 'aio') Using file /etc/xen/images/windows8.img in read-write mode Strip off blktap sub-type prefix to /home/flyon/windows8.iso (drv 'aio') Using file /home/flyon/windows8.iso in read-only mode Watching /local/domain/0/device-model/19/logdirty/cmd Watching /local/domain/0/device-model/19/command Watching /local/domain/19/cpu qemu_map_cache_init nr_buckets = 10000 size 4194304 shared page at pfn feffd buffered io page at pfn feffb Guest uuid = e72e564f-812a-49dd-9c78-d76a957ebeab Register xen platform. Done register platform. platform_fixed_ioport: changed ro/rw state of ROM memory area. now is rw state. xs_read(/local/domain/0/device-model/19/xen_extended_power_mgmt): read error medium change watch on `hdc' (index: 1): aio:/home/flyon/windows8.iso I/O request not ready: 0, ptr: 0, port: 0, data: 0, count: 0, size: 0 Log-dirty: no command yet. I/O request not ready: 0, ptr: 0, port: 0, data: 0, count: 0, size: 0 I/O request not ready: 0, ptr: 0, port: 0, data: 0, count: 0, size: 0 vcpu-set: watch node error. I/O request not ready: 0, ptr: 0, port: 0, data: 0, count: 0, size: 0 xs_read(/local/domain/19/log-throttling): read error qemu: ignoring not-understood drive `/local/domain/19/log-throttling' medium change watch on `/local/domain/19/log-throttling' - unknown device, ignored I/O request not ready: 0, ptr: 0, port: 0, data: 0, count: 0, size: 0 I/O request not ready: 0, ptr: 0, port: 0, data: 0, count: 0, size: 0 I/O request not ready: 0, ptr: 0, port: 0, data: 0, count: 0, size: 0 I/O request not ready: 0, ptr: 0, port: 0, data: 0, count: 0, size: 0 I/O request not ready: 0, ptr: 0, port: 0, data: 0, count: 0, size: 0 I/O request not ready: 0, ptr: 0, port: 0, data: 0, count: 0, size: 0 I/O request not ready: 0, ptr: 0, port: 0, data: 0, count: 0, size: 0 I/O request not ready: 0, ptr: 0, port: 0, data: 0, count: 0, size: 0 platform_fixed_ioport: changed ro/rw state of ROM memory area. now is rw state. platform_fixed_ioport: changed ro/rw state of ROM memory area. now is ro state. reset requested in cpu_handle_ioreq. Issued domain 19 reboot --------------060301030907070908060303 Content-Type: text/plain; name="qemu-dm-Windows8.log.3" Content-Transfer-Encoding: 7bit Content-Disposition: attachment; filename="qemu-dm-Windows8.log.3" domid: 18 Strip off blktap sub-type prefix to /etc/xen/images/windows8.img (drv 'aio') Using file /etc/xen/images/windows8.img in read-write mode Strip off blktap sub-type prefix to /home/flyon/windows8.iso (drv 'aio') Using file /home/flyon/windows8.iso in read-only mode Watching /local/domain/0/device-model/18/logdirty/cmd Watching /local/domain/0/device-model/18/command Watching /local/domain/18/cpu qemu_map_cache_init nr_buckets = 10000 size 4194304 shared page at pfn feffd buffered io page at pfn feffb Guest uuid = 54da941e-ff5f-4db6-919a-00579c8fccc3 Register xen platform. Done register platform. platform_fixed_ioport: changed ro/rw state of ROM memory area. now is rw state. xs_read(/local/domain/0/device-model/18/xen_extended_power_mgmt): read error medium change watch on `hdc' (index: 1): aio:/home/flyon/windows8.iso I/O request not ready: 0, ptr: 0, port: 0, data: 0, count: 0, size: 0 Log-dirty: no command yet. I/O request not ready: 0, ptr: 0, port: 0, data: 0, count: 0, size: 0 I/O request not ready: 0, ptr: 0, port: 0, data: 0, count: 0, size: 0 vcpu-set: watch node error. I/O request not ready: 0, ptr: 0, port: 0, data: 0, count: 0, size: 0 xs_read(/local/domain/18/log-throttling): read error qemu: ignoring not-understood drive `/local/domain/18/log-throttling' medium change watch on `/local/domain/18/log-throttling' - unknown device, ignored I/O request not ready: 0, ptr: 0, port: 0, data: 0, count: 0, size: 0 I/O request not ready: 0, ptr: 0, port: 0, data: 0, count: 0, size: 0 I/O request not ready: 0, ptr: 0, port: 0, data: 0, count: 0, size: 0 I/O request not ready: 0, ptr: 0, port: 0, data: 0, count: 0, size: 0 I/O request not ready: 0, ptr: 0, port: 0, data: 0, count: 0, size: 0 I/O request not ready: 0, ptr: 0, port: 0, data: 0, count: 0, size: 0 I/O request not ready: 0, ptr: 0, port: 0, data: 0, count: 0, size: 0 I/O request not ready: 0, ptr: 0, port: 0, data: 0, count: 0, size: 0 platform_fixed_ioport: changed ro/rw state of ROM memory area. now is rw state. platform_fixed_ioport: changed ro/rw state of ROM memory area. now is ro state. reset requested in cpu_handle_ioreq. Issued domain 18 reboot --------------060301030907070908060303 Content-Type: text/plain; name="qemu-dm-Windows8.log.4" Content-Transfer-Encoding: 7bit Content-Disposition: attachment; filename="qemu-dm-Windows8.log.4" domid: 17 Strip off blktap sub-type prefix to /etc/xen/images/windows8.img (drv 'aio') Using file /etc/xen/images/windows8.img in read-write mode Strip off blktap sub-type prefix to /home/flyon/windows8.iso (drv 'aio') Using file /home/flyon/windows8.iso in read-only mode Watching /local/domain/0/device-model/17/logdirty/cmd Watching /local/domain/0/device-model/17/command Watching /local/domain/17/cpu qemu_map_cache_init nr_buckets = 10000 size 4194304 shared page at pfn feffd buffered io page at pfn feffb Guest uuid = 467e63fb-1054-4b1e-bb58-0ac6a2fe77ef Register xen platform. Done register platform. platform_fixed_ioport: changed ro/rw state of ROM memory area. now is rw state. xs_read(/local/domain/0/device-model/17/xen_extended_power_mgmt): read error medium change watch on `hdc' (index: 1): aio:/home/flyon/windows8.iso I/O request not ready: 0, ptr: 0, port: 0, data: 0, count: 0, size: 0 Log-dirty: no command yet. I/O request not ready: 0, ptr: 0, port: 0, data: 0, count: 0, size: 0 I/O request not ready: 0, ptr: 0, port: 0, data: 0, count: 0, size: 0 vcpu-set: watch node error. I/O request not ready: 0, ptr: 0, port: 0, data: 0, count: 0, size: 0 xs_read(/local/domain/17/log-throttling): read error qemu: ignoring not-understood drive `/local/domain/17/log-throttling' medium change watch on `/local/domain/17/log-throttling' - unknown device, ignored I/O request not ready: 0, ptr: 0, port: 0, data: 0, count: 0, size: 0 I/O request not ready: 0, ptr: 0, port: 0, data: 0, count: 0, size: 0 I/O request not ready: 0, ptr: 0, port: 0, data: 0, count: 0, size: 0 I/O request not ready: 0, ptr: 0, port: 0, data: 0, count: 0, size: 0 I/O request not ready: 0, ptr: 0, port: 0, data: 0, count: 0, size: 0 I/O request not ready: 0, ptr: 0, port: 0, data: 0, count: 0, size: 0 I/O request not ready: 0, ptr: 0, port: 0, data: 0, count: 0, size: 0 I/O request not ready: 0, ptr: 0, port: 0, data: 0, count: 0, size: 0 platform_fixed_ioport: changed ro/rw state of ROM memory area. now is rw state. platform_fixed_ioport: changed ro/rw state of ROM memory area. now is ro state. reset requested in cpu_handle_ioreq. Issued domain 17 reboot --------------060301030907070908060303 Content-Type: text/plain; name="qemu-dm-Windows8.log.5" Content-Transfer-Encoding: 7bit Content-Disposition: attachment; filename="qemu-dm-Windows8.log.5" domid: 16 Strip off blktap sub-type prefix to /etc/xen/images/windows8.img (drv 'aio') Using file /etc/xen/images/windows8.img in read-write mode Strip off blktap sub-type prefix to /home/flyon/windows8.iso (drv 'aio') Using file /home/flyon/windows8.iso in read-only mode Watching /local/domain/0/device-model/16/logdirty/cmd Watching /local/domain/0/device-model/16/command Watching /local/domain/16/cpu qemu_map_cache_init nr_buckets = 10000 size 4194304 shared page at pfn feffd buffered io page at pfn feffb Guest uuid = fbe85911-c17d-4b2d-9ae0-33b2211cb22f Register xen platform. Done register platform. platform_fixed_ioport: changed ro/rw state of ROM memory area. now is rw state. xs_read(/local/domain/0/device-model/16/xen_extended_power_mgmt): read error medium change watch on `hdc' (index: 1): aio:/home/flyon/windows8.iso I/O request not ready: 0, ptr: 0, port: 0, data: 0, count: 0, size: 0 Log-dirty: no command yet. I/O request not ready: 0, ptr: 0, port: 0, data: 0, count: 0, size: 0 I/O request not ready: 0, ptr: 0, port: 0, data: 0, count: 0, size: 0 vcpu-set: watch node error. I/O request not ready: 0, ptr: 0, port: 0, data: 0, count: 0, size: 0 xs_read(/local/domain/16/log-throttling): read error qemu: ignoring not-understood drive `/local/domain/16/log-throttling' medium change watch on `/local/domain/16/log-throttling' - unknown device, ignored I/O request not ready: 0, ptr: 0, port: 0, data: 0, count: 0, size: 0 I/O request not ready: 0, ptr: 0, port: 0, data: 0, count: 0, size: 0 I/O request not ready: 0, ptr: 0, port: 0, data: 0, count: 0, size: 0 I/O request not ready: 0, ptr: 0, port: 0, data: 0, count: 0, size: 0 I/O request not ready: 0, ptr: 0, port: 0, data: 0, count: 0, size: 0 I/O request not ready: 0, ptr: 0, port: 0, data: 0, count: 0, size: 0 I/O request not ready: 0, ptr: 0, port: 0, data: 0, count: 0, size: 0 I/O request not ready: 0, ptr: 0, port: 0, data: 0, count: 0, size: 0 platform_fixed_ioport: changed ro/rw state of ROM memory area. now is rw state. platform_fixed_ioport: changed ro/rw state of ROM memory area. now is ro state. reset requested in cpu_handle_ioreq. Issued domain 16 reboot --------------060301030907070908060303 Content-Type: text/plain; name="qemu-dm-Windows8.log.6" Content-Transfer-Encoding: 7bit Content-Disposition: attachment; filename="qemu-dm-Windows8.log.6" domid: 15 Strip off blktap sub-type prefix to /etc/xen/images/windows8.img (drv 'aio') Using file /etc/xen/images/windows8.img in read-write mode Strip off blktap sub-type prefix to /home/flyon/windows8.iso (drv 'aio') Using file /home/flyon/windows8.iso in read-only mode Watching /local/domain/0/device-model/15/logdirty/cmd Watching /local/domain/0/device-model/15/command Watching /local/domain/15/cpu qemu_map_cache_init nr_buckets = 10000 size 4194304 shared page at pfn feffd buffered io page at pfn feffb Guest uuid = 6ffa0353-1b02-4747-87f6-e30cb6067a76 Register xen platform. Done register platform. platform_fixed_ioport: changed ro/rw state of ROM memory area. now is rw state. xs_read(/local/domain/0/device-model/15/xen_extended_power_mgmt): read error medium change watch on `hdc' (index: 1): aio:/home/flyon/windows8.iso I/O request not ready: 0, ptr: 0, port: 0, data: 0, count: 0, size: 0 Log-dirty: no command yet. I/O request not ready: 0, ptr: 0, port: 0, data: 0, count: 0, size: 0 I/O request not ready: 0, ptr: 0, port: 0, data: 0, count: 0, size: 0 vcpu-set: watch node error. I/O request not ready: 0, ptr: 0, port: 0, data: 0, count: 0, size: 0 xs_read(/local/domain/15/log-throttling): read error qemu: ignoring not-understood drive `/local/domain/15/log-throttling' medium change watch on `/local/domain/15/log-throttling' - unknown device, ignored I/O request not ready: 0, ptr: 0, port: 0, data: 0, count: 0, size: 0 I/O request not ready: 0, ptr: 0, port: 0, data: 0, count: 0, size: 0 I/O request not ready: 0, ptr: 0, port: 0, data: 0, count: 0, size: 0 I/O request not ready: 0, ptr: 0, port: 0, data: 0, count: 0, size: 0 I/O request not ready: 0, ptr: 0, port: 0, data: 0, count: 0, size: 0 I/O request not ready: 0, ptr: 0, port: 0, data: 0, count: 0, size: 0 I/O request not ready: 0, ptr: 0, port: 0, data: 0, count: 0, size: 0 I/O request not ready: 0, ptr: 0, port: 0, data: 0, count: 0, size: 0 platform_fixed_ioport: changed ro/rw state of ROM memory area. now is rw state. platform_fixed_ioport: changed ro/rw state of ROM memory area. now is ro state. reset requested in cpu_handle_ioreq. Issued domain 15 reboot --------------060301030907070908060303 Content-Type: text/plain; name="qemu-dm-Windows8.log.7" Content-Transfer-Encoding: 7bit Content-Disposition: attachment; filename="qemu-dm-Windows8.log.7" domid: 14 Strip off blktap sub-type prefix to /etc/xen/images/windows8.img (drv 'aio') Using file /etc/xen/images/windows8.img in read-write mode Strip off blktap sub-type prefix to /home/flyon/windows8.iso (drv 'aio') Using file /home/flyon/windows8.iso in read-only mode Watching /local/domain/0/device-model/14/logdirty/cmd Watching /local/domain/0/device-model/14/command Watching /local/domain/14/cpu qemu_map_cache_init nr_buckets = 10000 size 4194304 shared page at pfn feffd buffered io page at pfn feffb Guest uuid = 908cd1e3-59b3-41f3-88a9-6d846fdbb675 Register xen platform. Done register platform. platform_fixed_ioport: changed ro/rw state of ROM memory area. now is rw state. xs_read(/local/domain/0/device-model/14/xen_extended_power_mgmt): read error medium change watch on `hdc' (index: 1): aio:/home/flyon/windows8.iso I/O request not ready: 0, ptr: 0, port: 0, data: 0, count: 0, size: 0 Log-dirty: no command yet. I/O request not ready: 0, ptr: 0, port: 0, data: 0, count: 0, size: 0 I/O request not ready: 0, ptr: 0, port: 0, data: 0, count: 0, size: 0 vcpu-set: watch node error. I/O request not ready: 0, ptr: 0, port: 0, data: 0, count: 0, size: 0 xs_read(/local/domain/14/log-throttling): read error qemu: ignoring not-understood drive `/local/domain/14/log-throttling' medium change watch on `/local/domain/14/log-throttling' - unknown device, ignored I/O request not ready: 0, ptr: 0, port: 0, data: 0, count: 0, size: 0 I/O request not ready: 0, ptr: 0, port: 0, data: 0, count: 0, size: 0 I/O request not ready: 0, ptr: 0, port: 0, data: 0, count: 0, size: 0 I/O request not ready: 0, ptr: 0, port: 0, data: 0, count: 0, size: 0 I/O request not ready: 0, ptr: 0, port: 0, data: 0, count: 0, size: 0 I/O request not ready: 0, ptr: 0, port: 0, data: 0, count: 0, size: 0 I/O request not ready: 0, ptr: 0, port: 0, data: 0, count: 0, size: 0 I/O request not ready: 0, ptr: 0, port: 0, data: 0, count: 0, size: 0 platform_fixed_ioport: changed ro/rw state of ROM memory area. now is rw state. platform_fixed_ioport: changed ro/rw state of ROM memory area. now is ro state. reset requested in cpu_handle_ioreq. Issued domain 14 reboot --------------060301030907070908060303 Content-Type: text/plain; name="qemu-dm-Windows8.log.8" Content-Transfer-Encoding: 7bit Content-Disposition: attachment; filename="qemu-dm-Windows8.log.8" domid: 13 Strip off blktap sub-type prefix to /etc/xen/images/windows8.img (drv 'aio') Using file /etc/xen/images/windows8.img in read-write mode Strip off blktap sub-type prefix to /home/flyon/windows8.iso (drv 'aio') Using file /home/flyon/windows8.iso in read-only mode Watching /local/domain/0/device-model/13/logdirty/cmd Watching /local/domain/0/device-model/13/command Watching /local/domain/13/cpu qemu_map_cache_init nr_buckets = 10000 size 4194304 shared page at pfn feffd buffered io page at pfn feffb Guest uuid = 7a9ba58a-35c9-4ad3-af42-5f371268d141 Register xen platform. Done register platform. platform_fixed_ioport: changed ro/rw state of ROM memory area. now is rw state. xs_read(/local/domain/0/device-model/13/xen_extended_power_mgmt): read error medium change watch on `hdc' (index: 1): aio:/home/flyon/windows8.iso I/O request not ready: 0, ptr: 0, port: 0, data: 0, count: 0, size: 0 Log-dirty: no command yet. I/O request not ready: 0, ptr: 0, port: 0, data: 0, count: 0, size: 0 I/O request not ready: 0, ptr: 0, port: 0, data: 0, count: 0, size: 0 vcpu-set: watch node error. I/O request not ready: 0, ptr: 0, port: 0, data: 0, count: 0, size: 0 xs_read(/local/domain/13/log-throttling): read error qemu: ignoring not-understood drive `/local/domain/13/log-throttling' medium change watch on `/local/domain/13/log-throttling' - unknown device, ignored I/O request not ready: 0, ptr: 0, port: 0, data: 0, count: 0, size: 0 I/O request not ready: 0, ptr: 0, port: 0, data: 0, count: 0, size: 0 I/O request not ready: 0, ptr: 0, port: 0, data: 0, count: 0, size: 0 I/O request not ready: 0, ptr: 0, port: 0, data: 0, count: 0, size: 0 I/O request not ready: 0, ptr: 0, port: 0, data: 0, count: 0, size: 0 I/O request not ready: 0, ptr: 0, port: 0, data: 0, count: 0, size: 0 I/O request not ready: 0, ptr: 0, port: 0, data: 0, count: 0, size: 0 I/O request not ready: 0, ptr: 0, port: 0, data: 0, count: 0, size: 0 platform_fixed_ioport: changed ro/rw state of ROM memory area. now is rw state. platform_fixed_ioport: changed ro/rw state of ROM memory area. now is ro state. reset requested in cpu_handle_ioreq. Issued domain 13 reboot --------------060301030907070908060303 Content-Type: text/plain; name="qemu-dm-Windows8.log.9" Content-Transfer-Encoding: 7bit Content-Disposition: attachment; filename="qemu-dm-Windows8.log.9" domid: 12 Strip off blktap sub-type prefix to /etc/xen/images/windows8.img (drv 'aio') Using file /etc/xen/images/windows8.img in read-write mode Strip off blktap sub-type prefix to /home/flyon/windows8.iso (drv 'aio') Using file /home/flyon/windows8.iso in read-only mode Watching /local/domain/0/device-model/12/logdirty/cmd Watching /local/domain/0/device-model/12/command Watching /local/domain/12/cpu qemu_map_cache_init nr_buckets = 10000 size 4194304 shared page at pfn feffd buffered io page at pfn feffb Guest uuid = 3fdbe19b-2484-4f51-a781-45feccb66d65 Register xen platform. Done register platform. platform_fixed_ioport: changed ro/rw state of ROM memory area. now is rw state. xs_read(/local/domain/0/device-model/12/xen_extended_power_mgmt): read error medium change watch on `hdc' (index: 1): aio:/home/flyon/windows8.iso I/O request not ready: 0, ptr: 0, port: 0, data: 0, count: 0, size: 0 Log-dirty: no command yet. I/O request not ready: 0, ptr: 0, port: 0, data: 0, count: 0, size: 0 I/O request not ready: 0, ptr: 0, port: 0, data: 0, count: 0, size: 0 vcpu-set: watch node error. I/O request not ready: 0, ptr: 0, port: 0, data: 0, count: 0, size: 0 xs_read(/local/domain/12/log-throttling): read error qemu: ignoring not-understood drive `/local/domain/12/log-throttling' medium change watch on `/local/domain/12/log-throttling' - unknown device, ignored I/O request not ready: 0, ptr: 0, port: 0, data: 0, count: 0, size: 0 I/O request not ready: 0, ptr: 0, port: 0, data: 0, count: 0, size: 0 I/O request not ready: 0, ptr: 0, port: 0, data: 0, count: 0, size: 0 I/O request not ready: 0, ptr: 0, port: 0, data: 0, count: 0, size: 0 I/O request not ready: 0, ptr: 0, port: 0, data: 0, count: 0, size: 0 I/O request not ready: 0, ptr: 0, port: 0, data: 0, count: 0, size: 0 I/O request not ready: 0, ptr: 0, port: 0, data: 0, count: 0, size: 0 I/O request not ready: 0, ptr: 0, port: 0, data: 0, count: 0, size: 0 platform_fixed_ioport: changed ro/rw state of ROM memory area. now is rw state. platform_fixed_ioport: changed ro/rw state of ROM memory area. now is ro state. reset requested in cpu_handle_ioreq. Issued domain 12 reboot --------------060301030907070908060303 Content-Type: text/plain; name="qemu-dm-Windows8.log.10" Content-Transfer-Encoding: 7bit Content-Disposition: attachment; filename="qemu-dm-Windows8.log.10" domid: 11 Strip off blktap sub-type prefix to /etc/xen/images/windows8.img (drv 'aio') Using file /etc/xen/images/windows8.img in read-write mode Strip off blktap sub-type prefix to /home/flyon/windows8.iso (drv 'aio') Using file /home/flyon/windows8.iso in read-only mode Watching /local/domain/0/device-model/11/logdirty/cmd Watching /local/domain/0/device-model/11/command Watching /local/domain/11/cpu qemu_map_cache_init nr_buckets = 10000 size 4194304 shared page at pfn feffd buffered io page at pfn feffb Guest uuid = ce6cf88a-65c6-4bf2-ab37-6881a1909bb5 Register xen platform. Done register platform. platform_fixed_ioport: changed ro/rw state of ROM memory area. now is rw state. xs_read(/local/domain/0/device-model/11/xen_extended_power_mgmt): read error medium change watch on `hdc' (index: 1): aio:/home/flyon/windows8.iso I/O request not ready: 0, ptr: 0, port: 0, data: 0, count: 0, size: 0 Log-dirty: no command yet. I/O request not ready: 0, ptr: 0, port: 0, data: 0, count: 0, size: 0 I/O request not ready: 0, ptr: 0, port: 0, data: 0, count: 0, size: 0 vcpu-set: watch node error. I/O request not ready: 0, ptr: 0, port: 0, data: 0, count: 0, size: 0 xs_read(/local/domain/11/log-throttling): read error qemu: ignoring not-understood drive `/local/domain/11/log-throttling' medium change watch on `/local/domain/11/log-throttling' - unknown device, ignored I/O request not ready: 0, ptr: 0, port: 0, data: 0, count: 0, size: 0 I/O request not ready: 0, ptr: 0, port: 0, data: 0, count: 0, size: 0 I/O request not ready: 0, ptr: 0, port: 0, data: 0, count: 0, size: 0 I/O request not ready: 0, ptr: 0, port: 0, data: 0, count: 0, size: 0 I/O request not ready: 0, ptr: 0, port: 0, data: 0, count: 0, size: 0 I/O request not ready: 0, ptr: 0, port: 0, data: 0, count: 0, size: 0 I/O request not ready: 0, ptr: 0, port: 0, data: 0, count: 0, size: 0 I/O request not ready: 0, ptr: 0, port: 0, data: 0, count: 0, size: 0 platform_fixed_ioport: changed ro/rw state of ROM memory area. now is rw state. platform_fixed_ioport: changed ro/rw state of ROM memory area. now is ro state. reset requested in cpu_handle_ioreq. Issued domain 11 reboot --------------060301030907070908060303 Content-Type: text/plain; name="Windows8.txt" Content-Transfer-Encoding: base64 Content-Disposition: attachment; filename="Windows8.txt" IyBYTCBkb21haW4gY29uZmlndXJhdGlvbiBmaWxlIGZvciBXaW5kb3dzIDggQ29uc3VtZXIg UHJldmlldyA2NC1iaXQgRW5nbGlzaCBIVk0gZG9tVQ0KIyBQbGVhc2UgcmVmZXIgdG8gIm1h biB4bC5jZmciIGZvciBmdXJ0aGVyIGV4cGxhbmF0aW9ucy4NCiMgU2VlIGFsc28gZG9jcy9t aXNjL3hsLW5ldHdvcmstY29uZmlndXJhdGlvbi5tYXJrZG93biBhbmQNCiMgZG9jcy9taXNj L3hsLWRpc2stY29uZmlndXJhdGlvbi50eHQNCiMgV3JpdHRlbiBieSBUZW8gRW4gTWluZyAo WmhhbmcgRW5taW5nKQ0KIyBFbWFpbDogdGVvLmVuLm1pbmdAZ21haWwuY29tDQojIE1vYmls ZSBQaG9uZTogKzY1LTgzNjktMjYxOA0KIyBDb3VudHJ5OiBTaW5nYXBvcmUNCiMgRGF0ZTog MTggTWFyIDIwMTIgU3VuDQpuYW1lPSJXaW5kb3dzOCINCiMgUHJvZHVjdCBLZXk6IFdKQlJY LTJON0IyLUNDQkY2LVZQUDk3LVI4OFhWDQpidWlsZGVyPSJodm0iDQp2Y3B1cz0xMg0KbWVt b3J5PTEyMDAwDQpvbl9wb3dlcm9mZj0iZGVzdHJveSINCm9uX3JlYm9vdD0icmVzdGFydCIN Cm9uX2NyYXNoPSJkZXN0cm95Ig0KZGlzaz1bICdmb3JtYXQ9cmF3LCB2ZGV2PWhkYSwgYWNj ZXNzPXJ3LCB0YXJnZXQ9L2V0Yy94ZW4vaW1hZ2VzL3dpbmRvd3M4LmltZycsICdmb3JtYXQ9 cmF3LCB2ZGV2PWhkYywgYWNjZXNzPXJvLCBkZXZ0eXBlPWNkcm9tLCB0YXJnZXQ9L2hvbWUv Zmx5b24vd2luZG93czguaXNvJyBdDQp2aWY9WyAnYnJpZGdlPWV0aDAsdHlwZT1pb2VtdSxt b2RlbD1lMTAwMCcgXQ0KI2Jvb3Q9W2N8ZHxuXQ0KIyBTZWxlY3RzIHRoZSBlbXVsYXRlZCB2 aXJ0dWFsIGRldmljZSB0byBib290IGZyb20uIE9wdGlvbnMgYXJlIGhhcmQgZGlzayAoYyks IGNkLXJvbSAoZCkgb3IgbmV0d29yay9QWEUgKG4pLg0KIyBNdWx0aXBsZSBvcHRpb25zIGNh biBiZSBnaXZlbiBhbmQgd2lsbCBiZSBhdHRlbXB0ZWQgaW4gdGhlIG9yZGVyIHRoZXkgYXJl IGdpdmVuLiBlLmcuIHRvIGJvb3QgZnJvbSBjZC1yb20NCiMgYnV0IGZhbGxiYWNrIHRvIHRo ZSBoYXJkIGRpc2sgeW91IGNhbiBnaXZlIGRjLiBUaGUgZGVmYXVsdCBpcyBjZC4NCmJvb3Q9 ImRjIg0KYWNwaT0xDQp4ZW5fcGxhdGZvcm1fcGNpPTENCnZpcmlkaWFuPTENCnN0ZHZnYT0x DQoNCnZuYz0xDQp2bmNsaXN0ZW49IjE5Mi4xNjguMjUuNTAiDQp2bmNkaXNwbGF5PTANCnZu Y3VudXNlZD0xDQp2bmNwYXNzd2Q9IiINCnNkbD0wDQp1c2I9MQ0KdXNiZGV2aWNlPSJ0YWJs ZXQiDQojIEVuYWJsZSBYZW4gVkdBIFBhc3N0aHJvdWdoDQpnZnhfcGFzc3RocnU9MQ0KIyBW R0EgUGFzc3Rocm91Z2ggTlZJRElBIFF1YWRybyA2MDAwDQpwY2kgPSBbICcwZDowMC4wJyBd DQojIFBDSSBQYXNzdGhyb3VnaCBJbnRlbCBIRCBBdWRpbyBDb250cm9sbGVyLg0KI3BjaSA9 IFsgJzAwOjFiLjAnIF0NCiMgUENJIFBhc3N0aHJvdWdoIGFsbCB0aGUgVVNCIENvbnRyb2xs ZXJzLg0KIyBwY2kgPSBbICcwMDoxYS4wJywnMDA6MWEuMScsJzAwOjFhLjInLCcwMDoxYS43 JywnMDA6MWQuMCcsJzAwOjFkLjEnLCcwMDoxZC4yJywnMDA6MWQuNycgXQ== --------------060301030907070908060303 Content-Type: text/plain; name="xen1.txt" Content-Transfer-Encoding: base64 Content-Disposition: attachment; filename="xen1.txt" DQpbICAgIDIuNzI1MzE4XSBwY2kgMDAwMDowZDowMC4wOiByZWcgMTA6IFttZW0gMHhmODAw MDAwMC0weGY5ZmZmZmZmXQ0KWyAgICAyLjcyNTMyOF0gcGNpIDAwMDA6MGQ6MDAuMDogcmVn IDE0OiBbbWVtIDB4ZDgwMDAwMDAtMHhkZmZmZmZmZiA2NGJpdCBwcmVmXQ0KWyAgICAyLjcy NTMzOF0gcGNpIDAwMDA6MGQ6MDAuMDogcmVnIDFjOiBbbWVtIDB4ZDQwMDAwMDAtMHhkN2Zm ZmZmZiA2NGJpdCBwcmVmXQ0KWyAgICAyLjcyNTM1MV0gcGNpIDAwMDA6MGQ6MDAuMDogcmVn IDMwOiBbbWVtIDB4MDAwMDAwMDAtMHgwMDA3ZmZmZiBwcmVmXQ0KWyAgICAyLjc2MzE1MF0g cGNpIDAwMDA6MGQ6MDAuMDogQkFSIDY6IGFzc2lnbmVkIFttZW0gMHhmN2YwMDAwMC0weGY3 ZjdmZmZmIHByZWZdDQoNCjFzdCBtZW1vcnkgcmFuZ2UNCj09PT09PT09PT09PT09PT0NCg0K bWF4ID0gMHhmOWZmZmZmZiA9IDQxOTQzMDM5OTkNCm1pbiA9IDB4ZjgwMDAwMDAgPSA0MTYw NzQ5NTY4DQpkaWZmZXJlbmNlPW1heCAtIG1pbiArMSA9IDQxOTQzMDM5OTkgLSA0MTYwNzQ5 NTY4ICsxPSAzMzU1NDQzMiA9IDB4MDIwMDAwMDANCg0KbWF4ID0gMHhGOUZGRkZGRg0KbWlu ID0gMHhGODAwMDAwMA0KZGlmZiA9IDB4MDIwMDAwMDANCg0KMm5kIG1lbW9yeSByYW5nZQ0K PT09PT09PT09PT09PT09PQ0KDQptYXggPSAweGRmZmZmZmZmID0gMzc1ODA5NjM4Mw0KbWlu ID0gMHhkODAwMDAwMCA9IDM2MjM4Nzg2NTYNCmRpZmZlcmVuY2UgPSBtYXggLSBtaW4gKyAx ID0gMzc1ODA5NjM4MyAtIDM2MjM4Nzg2NTYgKyAxID0gMTM0MjE3NzI4ID0gMHgwODAwMDAw MA0KDQptYXggPSAweERGRkZGRkZGDQptaW4gPSAweEQ4MDAwMDAwDQpkaWZmPSAweDA4MDAw MDAwDQoNCjNyZCBtZW1vcnkgcmFuZ2UNCj09PT09PT09PT09PT09PT0NCg0KbWF4ID0gMHhk N2ZmZmZmZiA9IDM2MjM4Nzg2NTUNCm1pbiA9IDB4ZDQwMDAwMDAgPSAzNTU2NzY5NzkyDQpk aWZmZXJlbmNlID0gbWF4IC0gbWluICsgMSA9IDM2MjM4Nzg2NTUgLSAzNTU2NzY5NzkyICsg MSA9IDY3MTA4ODY0ID0gMHgwNDAwMDAwMA0KDQptYXggPSAweEQ3RkZGRkZGDQptaW4gPSAw eEQ0MDAwMDAwDQpkaWZmPSAweDA0MDAwMDAwDQoNCjR0aCBtZW1vcnkgcmFuZ2UNCj09PT09 PT09PT09PT09PT0NCg0KbWF4ID0gMHgwMDA3ZmZmZiA9IDUyNDI4Nw0KbWluID0gMHgwMDAw MDAwMCA9IDANCmRpZmZlcmVuY2UgPSBtYXggLSBtaW4gKzEgPSA1MjQyODcgLSAwICsgMSA9 IDUyNDI4OCA9IDB4MDAwODAwMDANCg0KbWF4ID0gMHgwMDA3RkZGRg0KbWluID0gMHgwMDAw MDAwMA0KZGlmZj0gMHgwMDA4MDAwMA0KDQoNClVVSUQgZDVlYzZiN2YtZTFkYi00YjQ2LWIw NTAtZDBiZDQ2NDAzZjU5DQoNCnZtbGludXotMy41LjQteGVuLWZyYW5rLmx5b24tc2dwDQpp bml0cmQuaW1nLTMuNS40LXhlbi1mcmFuay5seW9uLXNncA0KeGVuLmd6DQoNCnJvb3Q9L2Rl di9tYXBwZXIvc25vdy1yb290IHJvIG5vbW9kZXNldA0KDQpmbHlvbkBzbm93On4kIGxzcGNp IC1uIHwgZ3JlcCAiMGQ6MDAuMCINCjBkOjAwLjAgMDMwMDogMTBkZTowNmQ4IChyZXYgYTMp DQoNCj09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09DQoN CiMhL2Jpbi9zaA0Kc2V0IC14DQojIw0KU3RhcnRzIFNob3Jld2FsbCBGaXJld2FsbA0Kc3Vk byBzZXJ2aWNlIHNob3Jld2FsbCByZXN0YXJ0DQojIw0KTG9hZHMgcGNpLXN0dWIga2VybmVs IG1vZHVsZQ0Kc3VkbyBtb2Rwcm9iZSBwY2ktc3R1Yg0KIyMNClBhc3N0aHJvdWdoIFBhbGl0 IE5WSURJQSBHZWZvcmNlIDg0MDAgR1MgUENJZSB4MTYgVkdBIGNhcmQNCiMgZWNobyAiDQpQ YXNzdGhyb3VnaCBQYWxpdCBOVklESUEgR2Vmb3JjZSA4NDAwIEdTIFZHQSBjYXJkLiINCnN1 ZG8gY2htb2Qgbyt3IC9zeXMvYnVzL3BjaS9kcml2ZXJzL3BjaS1zdHViL25ld19pZA0Kc3Vk byBjaG1vZCBvK3cgL3N5cy9idXMvcGNpL2RldmljZXMvMDAwMDowMTowMC4wL2RyaXZlci91 bmJpbmQNCnN1ZG8gY2htb2Qgbyt3IC9zeXMvYnVzL3BjaS9kcml2ZXJzL3BjaS1zdHViL2Jp bmQNCmVjaG8gIjEwZGUgMTBjMyIgPiAvc3lzL2J1cy9wY2kvZHJpdmVycy9wY2ktc3R1Yi9u ZXdfaWQNCmVjaG8gIjAwMDA6MDE6MDAuMCIgPiAvc3lzL2J1cy9wY2kvZGV2aWNlcy8wMDAw OjAxOjAwLjAvZHJpdmVyL3VuYmluZA0KZWNobyAiMDAwMDowMTowMC4wIiA+IC9zeXMvYnVz L3BjaS9kcml2ZXJzL3BjaS1zdHViL2JpbmQNCiMjDQpQYXNzdGhyb3VnaCBJbnRlbCBIRCBB dWRpbyBDb250cm9sbGVyDQojIGVjaG8gIg0KUGFzc3Rocm91Z2ggSW50ZWwgSEQgQXVkaW8g Q29udHJvbGxlci4iDQpzdWRvIGNobW9kIG8rdyAvc3lzL2J1cy9wY2kvZHJpdmVycy9wY2kt c3R1Yi9uZXdfaWQNCnN1ZG8gY2htb2Qgbyt3IC9zeXMvYnVzL3BjaS9kZXZpY2VzLzAwMDA6 MDA6MWIuMC9kcml2ZXIvdW5iaW5kDQpzdWRvIGNobW9kIG8rdyAvc3lzL2J1cy9wY2kvZHJp dmVycy9wY2ktc3R1Yi9iaW5kDQplY2hvICI4MDg2IDNhNmUiID4gL3N5cy9idXMvcGNpL2Ry aXZlcnMvcGNpLXN0dWIvbmV3X2lkDQplY2hvICIwMDAwOjAwOjFiLjAiID4gL3N5cy9idXMv cGNpL2RldmljZXMvMDAwMDowMDoxYi4wL2RyaXZlci91bmJpbmQNCmVjaG8gIjAwMDA6MDA6 MWIuMCIgPiAvc3lzL2J1cy9wY2kvZHJpdmVycy9wY2ktc3R1Yi9iaW5kDQojIw0KV2FpdCBm b3IgMTAgc2Vjb25kcw0KI3MNCmxlZXAgMTANCiMjDQpTdGFydCBXaW5kb3dzIEhWTSBkb21V IHdpdGggVkdBIFBhc3N0aHJvdWdoDQojDQojc3VkbyB4bCBjcmVhdGUgL2V0Yy94ZW4vV2lu ZG93c1hQSG9tZUVkaXRpb25TUDMNCnN1ZG8geGwgY3JlYXRlIC9ldGMveGVuL1dpbmRvd3M4 Q29uc3VtZXJQcmV2aWV3NjRiaXRFbmdsaXNo --------------060301030907070908060303 Content-Type: text/x-log; name="xend.log" Content-Transfer-Encoding: quoted-printable Content-Disposition: attachment; filename="xend.log" [2012-09-19 20:48:44 1730] INFO (SrvDaemon:332) Xend Daemon started [2012-09-19 20:48:44 1730] INFO (SrvDaemon:336) Xend changeset: Mon Sep 1= 7 21:12:21 2012 +0100 25925:d1c3375c3f11. [2012-09-19 20:48:44 1730] DEBUG (tcp:96) Listening on :8002 [2012-09-19 20:48:47 1730] DEBUG (XendNode:332) pscsi record count: 9 [2012-09-19 20:48:47 1730] DEBUG (XendCPUPool:747) recreate_active_pools [2012-09-19 20:48:47 1730] DEBUG (XendDomainInfo:151) XendDomainInfo.recr= eate({'max_vcpu_id': 23, 'cpu_time': 20156983226L, 'ssidref': 0, 'hvm': 0= , 'shutdown_reason': 255, 'dying': 0, 'online_vcpus': 24, 'domid': 0, 'pa= used': 0, 'crashed': 0, 'running': 1, 'maxmem_kb': 17179869180L, 'shutdow= n': 0, 'mem_kb': 24692524L, 'blocked': 0, 'handle': [0, 0, 0, 0, 0, 0, 0,= 0, 0, 0, 0, 0, 0, 0, 0, 0], 'cpupool': 0, 'name': 'Domain-0'}) [2012-09-19 20:48:47 1730] INFO (XendDomainInfo:169) Recreating domain 0,= UUID 00000000-0000-0000-0000-000000000000. at /local/domain/0 [2012-09-19 20:48:47 1730] DEBUG (XendDomainInfo:3426) Storing VM details= : {'on_xend_stop': 'ignore', 'pool_name': 'Pool-0', 'shadow_memory': '0',= 'uuid': '00000000-0000-0000-0000-000000000000', 'on_reboot': 'restart', = 'image': "(linux (kernel '') (superpages 0) (nomigrate 0) (tsc_mode 0))",= 'on_poweroff': 'destroy', 'bootloader_args': '', 'on_xend_start': 'ignor= e', 'on_crash': 'restart', 'xend/restart_count': '0', 'vcpus': '24', 'vcp= u_avail': '16777215', 'bootloader': '', 'name': 'Domain-0'} [2012-09-19 20:48:47 1730] DEBUG (XendDomainInfo:1795) Storing domain det= ails: {'cpu/3/availability': 'online', 'cpu/6/availability': 'online', 'v= m': '/vm/00000000-0000-0000-0000-000000000000', 'cpu/22/availability': 'o= nline', 'control/platform-feature-multiprocessor-suspend': '1', 'cpu/17/a= vailability': 'online', 'cpu/14/availability': 'online', 'console/limit':= '1048576', 'cpu/2/availability': 'online', 'cpu/11/availability': 'onlin= e', 'cpu/1/availability': 'online', 'cpu/7/availability': 'online', 'memo= ry/target': '24692524', 'cpu/20/availability': 'online', 'control/platfor= m-feature-xs_reset_watches': '1', 'cpu/15/availability': 'online', 'descr= iption': '', 'cpu/13/availability': 'online', 'cpu/8/availability': 'onli= ne', 'cpu/9/availability': 'online', 'cpu/5/availability': 'online', 'cpu= /23/availability': 'online', 'cpu/0/availability': 'online', 'cpu/18/avai= lability': 'online', 'console/type': 'xenconsoled', 'cpu/12/availability'= : 'online', 'cpu/19/availability': 'online', 'name': 'Domain-0', 'domid':= '0', 'cpu/4/availability': 'online', 'cpu/16/availability': 'online', 'c= pu/21/availability': 'online', 'cpu/10/availability': 'online'} [2012-09-19 20:48:47 1730] DEBUG (XendDomain:476) Adding Domain: 0 [2012-09-19 20:48:47 1730] DEBUG (XendDomain:410) number of vcpus to use = is 0 [2012-09-19 20:48:47 1730] DEBUG (XendDomainInfo:1882) XendDomainInfo.han= dleShutdownWatch [2012-09-19 20:48:47 1730] WARNING (XendAPI:708) API call: VBD.set_device= not found [2012-09-19 20:48:47 1730] WARNING (XendAPI:708) API call: VBD.set_type n= ot found [2012-09-19 20:48:47 1730] WARNING (XendAPI:708) API call: session.get_al= l_records not found [2012-09-19 20:48:47 1730] WARNING (XendAPI:708) API call: event.get_reco= rd not found [2012-09-19 20:48:47 1730] WARNING (XendAPI:708) API call: event.get_all = not found [2012-09-19 20:48:47 1730] WARNING (XendAPI:708) API call: VIF.set_device= not found [2012-09-19 20:48:47 1730] WARNING (XendAPI:708) API call: VIF.set_MAC no= t found [2012-09-19 20:48:47 1730] WARNING (XendAPI:708) API call: VIF.set_MTU no= t found [2012-09-19 20:48:47 1730] WARNING (XendAPI:708) API call: debug.get_all = not found [2012-09-19 20:48:47 1730] INFO (XMLRPCServer:161) Opening Unix domain so= cket XML-RPC server on /var/run/xend/xen-api.sock; authentication has bee= n disabled for this server. [2012-09-19 20:48:47 1730] INFO (XMLRPCServer:161) Opening Unix domain so= cket XML-RPC server on /var/run/xend/xmlrpc.sock. [2012-09-19 21:00:22 1730] DEBUG (SrvServer:77) SrvServer.cleanup() [2012-09-19 21:00:22 1730] DEBUG (XMLRPCServer:251) XMLRPCServer.cleanup(= ) [2012-09-19 21:00:22 1730] DEBUG (XMLRPCServer:251) XMLRPCServer.cleanup(= ) [2012-09-19 21:00:22 1730] DEBUG (XendDomain:644) cleanup_domains [2012-09-19 21:00:22 1729] INFO (SrvDaemon:220) Xend exited with status 0= =2E [2012-09-19 21:03:31 1691] INFO (SrvDaemon:332) Xend Daemon started [2012-09-19 21:03:31 1691] INFO (SrvDaemon:336) Xend changeset: Mon Sep 1= 7 21:12:21 2012 +0100 25925:d1c3375c3f11. [2012-09-19 21:03:31 1691] DEBUG (tcp:96) Listening on :8002 [2012-09-19 21:03:33 1691] DEBUG (XendNode:332) pscsi record count: 9 [2012-09-19 21:03:33 1691] DEBUG (XendCPUPool:747) recreate_active_pools [2012-09-19 21:03:33 1691] DEBUG (XendDomainInfo:151) XendDomainInfo.recr= eate({'max_vcpu_id': 23, 'cpu_time': 17093476257L, 'ssidref': 0, 'hvm': 0= , 'shutdown_reason': 255, 'dying': 0, 'online_vcpus': 24, 'domid': 0, 'pa= used': 0, 'crashed': 0, 'running': 1, 'maxmem_kb': 17179869180L, 'shutdow= n': 0, 'mem_kb': 24692524L, 'blocked': 0, 'handle': [0, 0, 0, 0, 0, 0, 0,= 0, 0, 0, 0, 0, 0, 0, 0, 0], 'cpupool': 0, 'name': 'Domain-0'}) [2012-09-19 21:03:33 1691] INFO (XendDomainInfo:169) Recreating domain 0,= UUID 00000000-0000-0000-0000-000000000000. at /local/domain/0 [2012-09-19 21:03:33 1691] DEBUG (XendDomainInfo:3426) Storing VM details= : {'on_xend_stop': 'ignore', 'pool_name': 'Pool-0', 'shadow_memory': '0',= 'uuid': '00000000-0000-0000-0000-000000000000', 'on_reboot': 'restart', = 'image': "(linux (kernel '') (superpages 0) (nomigrate 0) (tsc_mode 0))",= 'on_poweroff': 'destroy', 'bootloader_args': '', 'on_xend_start': 'ignor= e', 'on_crash': 'restart', 'xend/restart_count': '0', 'vcpus': '24', 'vcp= u_avail': '16777215', 'bootloader': '', 'name': 'Domain-0'} [2012-09-19 21:03:33 1691] DEBUG (XendDomainInfo:1795) Storing domain det= ails: {'cpu/3/availability': 'online', 'cpu/6/availability': 'online', 'v= m': '/vm/00000000-0000-0000-0000-000000000000', 'cpu/22/availability': 'o= nline', 'control/platform-feature-multiprocessor-suspend': '1', 'cpu/17/a= vailability': 'online', 'cpu/14/availability': 'online', 'console/limit':= '1048576', 'cpu/2/availability': 'online', 'cpu/11/availability': 'onlin= e', 'cpu/1/availability': 'online', 'cpu/7/availability': 'online', 'memo= ry/target': '24692524', 'cpu/20/availability': 'online', 'control/platfor= m-feature-xs_reset_watches': '1', 'cpu/15/availability': 'online', 'descr= iption': '', 'cpu/13/availability': 'online', 'cpu/8/availability': 'onli= ne', 'cpu/9/availability': 'online', 'cpu/5/availability': 'online', 'cpu= /23/availability': 'online', 'cpu/0/availability': 'online', 'cpu/18/avai= lability': 'online', 'console/type': 'xenconsoled', 'cpu/12/availability'= : 'online', 'cpu/19/availability': 'online', 'name': 'Domain-0', 'domid':= '0', 'cpu/4/availability': 'online', 'cpu/16/availability': 'online', 'c= pu/21/availability': 'online', 'cpu/10/availability': 'online'} [2012-09-19 21:03:33 1691] DEBUG (XendDomain:476) Adding Domain: 0 [2012-09-19 21:03:33 1691] DEBUG (XendDomain:410) number of vcpus to use = is 0 [2012-09-19 21:03:33 1691] DEBUG (XendDomainInfo:1882) XendDomainInfo.han= dleShutdownWatch [2012-09-19 21:03:33 1691] WARNING (XendAPI:708) API call: VBD.set_device= not found [2012-09-19 21:03:33 1691] WARNING (XendAPI:708) API call: VBD.set_type n= ot found [2012-09-19 21:03:33 1691] WARNING (XendAPI:708) API call: session.get_al= l_records not found [2012-09-19 21:03:33 1691] WARNING (XendAPI:708) API call: event.get_reco= rd not found [2012-09-19 21:03:33 1691] WARNING (XendAPI:708) API call: event.get_all = not found [2012-09-19 21:03:33 1691] WARNING (XendAPI:708) API call: VIF.set_device= not found [2012-09-19 21:03:33 1691] WARNING (XendAPI:708) API call: VIF.set_MAC no= t found [2012-09-19 21:03:33 1691] WARNING (XendAPI:708) API call: VIF.set_MTU no= t found [2012-09-19 21:03:34 1691] WARNING (XendAPI:708) API call: debug.get_all = not found [2012-09-19 21:03:34 1691] INFO (XMLRPCServer:161) Opening Unix domain so= cket XML-RPC server on /var/run/xend/xen-api.sock; authentication has bee= n disabled for this server. [2012-09-19 21:03:34 1691] INFO (XMLRPCServer:161) Opening Unix domain so= cket XML-RPC server on /var/run/xend/xmlrpc.sock. [2012-09-19 22:18:22 1691] DEBUG (SrvServer:77) SrvServer.cleanup() [2012-09-19 22:18:22 1691] DEBUG (XMLRPCServer:251) XMLRPCServer.cleanup(= ) [2012-09-19 22:18:22 1691] DEBUG (XMLRPCServer:251) XMLRPCServer.cleanup(= ) [2012-09-19 22:18:22 1691] DEBUG (XendDomain:644) cleanup_domains [2012-09-19 22:18:22 1689] INFO (SrvDaemon:220) Xend exited with status 0= =2E [2012-09-19 22:37:19 6950] INFO (SrvDaemon:332) Xend Daemon started [2012-09-19 22:37:19 6950] INFO (SrvDaemon:336) Xend changeset: Mon Sep 1= 7 21:12:21 2012 +0100 25925:d1c3375c3f11. [2012-09-19 22:37:19 6950] DEBUG (tcp:96) Listening on :8002 [2012-09-19 22:37:22 6950] DEBUG (XendNode:332) pscsi record count: 12 [2012-09-19 22:37:22 6950] DEBUG (XendCPUPool:747) recreate_active_pools [2012-09-19 22:37:22 6950] DEBUG (XendDomainInfo:151) XendDomainInfo.recr= eate({'max_vcpu_id': 23, 'cpu_time': 3726170848291L, 'ssidref': 0, 'hvm':= 0, 'shutdown_reason': 255, 'dying': 0, 'online_vcpus': 24, 'domid': 0, '= paused': 0, 'crashed': 0, 'running': 1, 'maxmem_kb': 17179869180L, 'shutd= own': 0, 'mem_kb': 12293932L, 'blocked': 0, 'handle': [0, 0, 0, 0, 0, 0, = 0, 0, 0, 0, 0, 0, 0, 0, 0, 0], 'cpupool': 0, 'name': 'Domain-0'}) [2012-09-19 22:37:22 6950] INFO (XendDomainInfo:169) Recreating domain 0,= UUID 00000000-0000-0000-0000-000000000000. at /local/domain/0 [2012-09-19 22:37:22 6950] DEBUG (XendDomain:476) Adding Domain: 0 [2012-09-19 22:37:22 6950] DEBUG (XendDomainInfo:1882) XendDomainInfo.han= dleShutdownWatch [2012-09-19 22:37:22 6950] DEBUG (XendDomain:410) number of vcpus to use = is 0 [2012-09-19 22:37:22 6950] WARNING (XendAPI:708) API call: VBD.set_device= not found [2012-09-19 22:37:22 6950] WARNING (XendAPI:708) API call: VBD.set_type n= ot found [2012-09-19 22:37:22 6950] WARNING (XendAPI:708) API call: session.get_al= l_records not found [2012-09-19 22:37:22 6950] WARNING (XendAPI:708) API call: event.get_reco= rd not found [2012-09-19 22:37:22 6950] WARNING (XendAPI:708) API call: event.get_all = not found [2012-09-19 22:37:22 6950] WARNING (XendAPI:708) API call: VIF.set_device= not found [2012-09-19 22:37:22 6950] WARNING (XendAPI:708) API call: VIF.set_MAC no= t found [2012-09-19 22:37:22 6950] WARNING (XendAPI:708) API call: VIF.set_MTU no= t found [2012-09-19 22:37:22 6950] WARNING (XendAPI:708) API call: debug.get_all = not found [2012-09-19 22:37:22 6950] INFO (XMLRPCServer:161) Opening Unix domain so= cket XML-RPC server on /var/run/xend/xen-api.sock; authentication has bee= n disabled for this server. [2012-09-19 22:37:22 6950] INFO (XMLRPCServer:161) Opening Unix domain so= cket XML-RPC server on /var/run/xend/xmlrpc.sock. [2012-09-19 22:38:16 6950] DEBUG (SrvServer:77) SrvServer.cleanup() [2012-09-19 22:38:16 6950] DEBUG (XMLRPCServer:251) XMLRPCServer.cleanup(= ) [2012-09-19 22:38:16 6950] DEBUG (XMLRPCServer:251) XMLRPCServer.cleanup(= ) [2012-09-19 22:38:16 6950] DEBUG (XendDomain:644) cleanup_domains [2012-09-19 22:38:16 6949] INFO (SrvDaemon:220) Xend exited with status 0= =2E --------------060301030907070908060303 Content-Type: text/x-log; name="xend-debug.log" Content-Transfer-Encoding: 7bit Content-Disposition: attachment; filename="xend-debug.log" Xend started at Wed Sep 19 20:48:44 2012. cat: /sys/bus/scsi/devices/target1:0:0/vendor: No such file or directory cat: /sys/bus/scsi/devices/target1:0:0/model: No such file or directory cat: /sys/bus/scsi/devices/target1:0:0/type: No such file or directory cat: /sys/bus/scsi/devices/target1:0:0/rev: No such file or directory cat: /sys/bus/scsi/devices/target1:0:0/scsi_level: No such file or directory cat: /sys/bus/scsi/devices/target2:0:0/vendor: No such file or directory cat: /sys/bus/scsi/devices/target2:0:0/model: No such file or directory cat: /sys/bus/scsi/devices/target2:0:0/type: No such file or directory cat: /sys/bus/scsi/devices/target2:0:0/rev: No such file or directory cat: /sys/bus/scsi/devices/target2:0:0/scsi_level: No such file or directory cat: /sys/bus/scsi/devices/target2:3:0/vendor: No such file or directory cat: /sys/bus/scsi/devices/target2:3:0/model: No such file or directory cat: /sys/bus/scsi/devices/target2:3:0/type: No such file or directory cat: /sys/bus/scsi/devices/target2:3:0/rev: No such file or directory cat: /sys/bus/scsi/devices/target2:3:0/scsi_level: No such file or directory cat: /sys/bus/scsi/devices/host0/vendor: No such file or directory cat: /sys/bus/scsi/devices/host0/model: No such file or directory cat: /sys/bus/scsi/devices/host0/type: No such file or directory cat: /sys/bus/scsi/devices/host0/rev: No such file or directory cat: /sys/bus/scsi/devices/host0/scsi_level: No such file or directory cat: /sys/bus/scsi/devices/host1/vendor: No such file or directory cat: /sys/bus/scsi/devices/host1/model: No such file or directory cat: /sys/bus/scsi/devices/host1/type: No such file or directory cat: /sys/bus/scsi/devices/host1/rev: No such file or directory cat: /sys/bus/scsi/devices/host1/scsi_level: No such file or directory cat: /sys/bus/scsi/devices/host2/vendor: No such file or directory cat: /sys/bus/scsi/devices/host2/model: No such file or directory cat: /sys/bus/scsi/devices/host2/type: No such file or directory cat: /sys/bus/scsi/devices/host2/rev: No such file or directory cat: /sys/bus/scsi/devices/host2/scsi_level: No such file or directory Xend started at Wed Sep 19 21:03:31 2012. cat: /sys/bus/scsi/devices/target1:0:0/vendor: No such file or directory cat: /sys/bus/scsi/devices/target1:0:0/model: No such file or directory cat: /sys/bus/scsi/devices/target1:0:0/type: No such file or directory cat: /sys/bus/scsi/devices/target1:0:0/rev: No such file or directory cat: /sys/bus/scsi/devices/target1:0:0/scsi_level: No such file or directory cat: /sys/bus/scsi/devices/target2:0:0/vendor: No such file or directory cat: /sys/bus/scsi/devices/target2:0:0/model: No such file or directory cat: /sys/bus/scsi/devices/target2:0:0/type: No such file or directory cat: /sys/bus/scsi/devices/target2:0:0/rev: No such file or directory cat: /sys/bus/scsi/devices/target2:0:0/scsi_level: No such file or directory cat: /sys/bus/scsi/devices/target2:3:0/vendor: No such file or directory cat: /sys/bus/scsi/devices/target2:3:0/model: No such file or directory cat: /sys/bus/scsi/devices/target2:3:0/type: No such file or directory cat: /sys/bus/scsi/devices/target2:3:0/rev: No such file or directory cat: /sys/bus/scsi/devices/target2:3:0/scsi_level: No such file or directory cat: /sys/bus/scsi/devices/host0/vendor: No such file or directory cat: /sys/bus/scsi/devices/host0/model: No such file or directory cat: /sys/bus/scsi/devices/host0/type: No such file or directory cat: /sys/bus/scsi/devices/host0/rev: No such file or directory cat: /sys/bus/scsi/devices/host0/scsi_level: No such file or directory cat: /sys/bus/scsi/devices/host1/vendor: No such file or directory cat: /sys/bus/scsi/devices/host1/model: No such file or directory cat: /sys/bus/scsi/devices/host1/type: No such file or directory cat: /sys/bus/scsi/devices/host1/rev: No such file or directory cat: /sys/bus/scsi/devices/host1/scsi_level: No such file or directory cat: /sys/bus/scsi/devices/host2/vendor: No such file or directory cat: /sys/bus/scsi/devices/host2/model: No such file or directory cat: /sys/bus/scsi/devices/host2/type: No such file or directory cat: /sys/bus/scsi/devices/host2/rev: No such file or directory cat: /sys/bus/scsi/devices/host2/scsi_level: No such file or directory Xend started at Wed Sep 19 22:37:19 2012. cat: /sys/bus/scsi/devices/target1:0:0/vendor: No such file or directory cat: /sys/bus/scsi/devices/target1:0:0/model: No such file or directory cat: /sys/bus/scsi/devices/target1:0:0/type: No such file or directory cat: /sys/bus/scsi/devices/target1:0:0/rev: No such file or directory cat: /sys/bus/scsi/devices/target1:0:0/scsi_level: No such file or directory cat: /sys/bus/scsi/devices/target2:0:0/vendor: No such file or directory cat: /sys/bus/scsi/devices/target2:0:0/model: No such file or directory cat: /sys/bus/scsi/devices/target2:0:0/type: No such file or directory cat: /sys/bus/scsi/devices/target2:0:0/rev: No such file or directory cat: /sys/bus/scsi/devices/target2:0:0/scsi_level: No such file or directory cat: /sys/bus/scsi/devices/target2:3:0/vendor: No such file or directory cat: /sys/bus/scsi/devices/target2:3:0/model: No such file or directory cat: /sys/bus/scsi/devices/target2:3:0/type: No such file or directory cat: /sys/bus/scsi/devices/target2:3:0/rev: No such file or directory cat: /sys/bus/scsi/devices/target2:3:0/scsi_level: No such file or directory cat: /sys/bus/scsi/devices/target3:0:0/vendor: No such file or directory cat: /sys/bus/scsi/devices/target3:0:0/model: No such file or directory cat: /sys/bus/scsi/devices/target3:0:0/type: No such file or directory cat: /sys/bus/scsi/devices/target3:0:0/rev: No such file or directory cat: /sys/bus/scsi/devices/target3:0:0/scsi_level: No such file or directory cat: /sys/bus/scsi/devices/host0/vendor: No such file or directory cat: /sys/bus/scsi/devices/host0/model: No such file or directory cat: /sys/bus/scsi/devices/host0/type: No such file or directory cat: /sys/bus/scsi/devices/host0/rev: No such file or directory cat: /sys/bus/scsi/devices/host0/scsi_level: No such file or directory cat: /sys/bus/scsi/devices/host1/vendor: No such file or directory cat: /sys/bus/scsi/devices/host1/model: No such file or directory cat: /sys/bus/scsi/devices/host1/type: No such file or directory cat: /sys/bus/scsi/devices/host1/rev: No such file or directory cat: /sys/bus/scsi/devices/host1/scsi_level: No such file or directory cat: /sys/bus/scsi/devices/host2/vendor: No such file or directory cat: /sys/bus/scsi/devices/host2/model: No such file or directory cat: /sys/bus/scsi/devices/host2/type: No such file or directory cat: /sys/bus/scsi/devices/host2/rev: No such file or directory cat: /sys/bus/scsi/devices/host2/scsi_level: No such file or directory cat: /sys/bus/scsi/devices/host3/vendor: No such file or directory cat: /sys/bus/scsi/devices/host3/model: No such file or directory cat: /sys/bus/scsi/devices/host3/type: No such file or directory cat: /sys/bus/scsi/devices/host3/rev: No such file or directory cat: /sys/bus/scsi/devices/host3/scsi_level: No such file or directory --------------060301030907070908060303 Content-Type: text/x-log; name="xen-hotplug.log" Content-Transfer-Encoding: 7bit Content-Disposition: attachment; filename="xen-hotplug.log" RTNETLINK answers: Operation not supported RTNETLINK answers: Operation not supported RTNETLINK answers: Operation not supported RTNETLINK answers: Operation not supported RTNETLINK answers: Operation not supported RTNETLINK answers: Operation not supported RTNETLINK answers: Operation not supported RTNETLINK answers: Operation not supported RTNETLINK answers: Operation not supported RTNETLINK answers: Operation not supported RTNETLINK answers: Operation not supported RTNETLINK answers: Operation not supported RTNETLINK answers: Operation not supported RTNETLINK answers: Operation not supported RTNETLINK answers: Operation not supported RTNETLINK answers: Operation not supported RTNETLINK answers: Operation not supported RTNETLINK answers: Operation not supported RTNETLINK answers: Operation not supported RTNETLINK answers: Operation not supported --------------060301030907070908060303 Content-Type: text/x-log; name="xl-Windows8.log" Content-Transfer-Encoding: 7bit Content-Disposition: attachment; filename="xl-Windows8.log" Waiting for domain Windows8 (domid 9) to die [pid 7447] Domain 9 has shut down, reason code 1 0x1 Action for shutdown reason code 1 is restart Domain 9 needs to be cleaned up: destroying the domain libxl: error: libxl_pci.c:1001:libxl__device_pci_reset: The kernel doesn't support reset from sysfs for PCI device 0000:0d:00.0 libxl: error: libxl_pci.c:1265:do_pci_remove: xc_deassign_device failed Done. Rebooting now xc: info: VIRTUAL MEMORY ARRANGEMENT: Loader: 0000000000100000->00000000001ad64c TOTAL: 0000000000000000->00000000ff800000 ENTRY ADDRESS: 0000000000100000 xc: info: PHYSICAL MEMORY ALLOCATION: 4KB PAGES: 0x0000000000000200 2MB PAGES: 0x00000000000003fb 1GB PAGES: 0x0000000000000002 libxl: error: libxl_pci.c:1055:libxl__device_pci_add: PCI device 0:d:0.0 is not assignable Waiting for domain Windows8 (domid 10) to die [pid 7447] Domain 10 has shut down, reason code 1 0x1 Action for shutdown reason code 1 is restart Domain 10 needs to be cleaned up: destroying the domain libxl: error: libxl_pci.c:1001:libxl__device_pci_reset: The kernel doesn't support reset from sysfs for PCI device 0000:0d:00.0 libxl: error: libxl_pci.c:1265:do_pci_remove: xc_deassign_device failed Done. Rebooting now xc: info: VIRTUAL MEMORY ARRANGEMENT: Loader: 0000000000100000->00000000001ad64c TOTAL: 0000000000000000->00000000ff800000 ENTRY ADDRESS: 0000000000100000 xc: info: PHYSICAL MEMORY ALLOCATION: 4KB PAGES: 0x0000000000000200 2MB PAGES: 0x00000000000003fb 1GB PAGES: 0x0000000000000002 libxl: error: libxl_pci.c:1055:libxl__device_pci_add: PCI device 0:d:0.0 is not assignable Waiting for domain Windows8 (domid 11) to die [pid 7447] Domain 11 has shut down, reason code 1 0x1 Action for shutdown reason code 1 is restart Domain 11 needs to be cleaned up: destroying the domain libxl: error: libxl_pci.c:1001:libxl__device_pci_reset: The kernel doesn't support reset from sysfs for PCI device 0000:0d:00.0 libxl: error: libxl_pci.c:1265:do_pci_remove: xc_deassign_device failed Done. Rebooting now xc: info: VIRTUAL MEMORY ARRANGEMENT: Loader: 0000000000100000->00000000001ad64c TOTAL: 0000000000000000->00000000ff800000 ENTRY ADDRESS: 0000000000100000 xc: info: PHYSICAL MEMORY ALLOCATION: 4KB PAGES: 0x0000000000000200 2MB PAGES: 0x00000000000003fb 1GB PAGES: 0x0000000000000002 libxl: error: libxl_pci.c:1055:libxl__device_pci_add: PCI device 0:d:0.0 is not assignable Waiting for domain Windows8 (domid 12) to die [pid 7447] Domain 12 has shut down, reason code 1 0x1 Action for shutdown reason code 1 is restart Domain 12 needs to be cleaned up: destroying the domain libxl: error: libxl_pci.c:1001:libxl__device_pci_reset: The kernel doesn't support reset from sysfs for PCI device 0000:0d:00.0 libxl: error: libxl_pci.c:1265:do_pci_remove: xc_deassign_device failed Done. Rebooting now xc: info: VIRTUAL MEMORY ARRANGEMENT: Loader: 0000000000100000->00000000001ad64c TOTAL: 0000000000000000->00000000ff800000 ENTRY ADDRESS: 0000000000100000 xc: info: PHYSICAL MEMORY ALLOCATION: 4KB PAGES: 0x0000000000000200 2MB PAGES: 0x00000000000003fb 1GB PAGES: 0x0000000000000002 libxl: error: libxl_pci.c:1055:libxl__device_pci_add: PCI device 0:d:0.0 is not assignable Waiting for domain Windows8 (domid 13) to die [pid 7447] Domain 13 has shut down, reason code 1 0x1 Action for shutdown reason code 1 is restart Domain 13 needs to be cleaned up: destroying the domain libxl: error: libxl_pci.c:1001:libxl__device_pci_reset: The kernel doesn't support reset from sysfs for PCI device 0000:0d:00.0 libxl: error: libxl_pci.c:1265:do_pci_remove: xc_deassign_device failed Done. Rebooting now xc: info: VIRTUAL MEMORY ARRANGEMENT: Loader: 0000000000100000->00000000001ad64c TOTAL: 0000000000000000->00000000ff800000 ENTRY ADDRESS: 0000000000100000 xc: info: PHYSICAL MEMORY ALLOCATION: 4KB PAGES: 0x0000000000000200 2MB PAGES: 0x00000000000003fb 1GB PAGES: 0x0000000000000002 libxl: error: libxl_pci.c:1055:libxl__device_pci_add: PCI device 0:d:0.0 is not assignable Waiting for domain Windows8 (domid 14) to die [pid 7447] Domain 14 has shut down, reason code 1 0x1 Action for shutdown reason code 1 is restart Domain 14 needs to be cleaned up: destroying the domain libxl: error: libxl_pci.c:1001:libxl__device_pci_reset: The kernel doesn't support reset from sysfs for PCI device 0000:0d:00.0 libxl: error: libxl_pci.c:1265:do_pci_remove: xc_deassign_device failed Done. Rebooting now xc: info: VIRTUAL MEMORY ARRANGEMENT: Loader: 0000000000100000->00000000001ad64c TOTAL: 0000000000000000->00000000ff800000 ENTRY ADDRESS: 0000000000100000 xc: info: PHYSICAL MEMORY ALLOCATION: 4KB PAGES: 0x0000000000000200 2MB PAGES: 0x00000000000003fb 1GB PAGES: 0x0000000000000002 libxl: error: libxl_pci.c:1055:libxl__device_pci_add: PCI device 0:d:0.0 is not assignable Waiting for domain Windows8 (domid 15) to die [pid 7447] Domain 15 has shut down, reason code 1 0x1 Action for shutdown reason code 1 is restart Domain 15 needs to be cleaned up: destroying the domain libxl: error: libxl_pci.c:1001:libxl__device_pci_reset: The kernel doesn't support reset from sysfs for PCI device 0000:0d:00.0 libxl: error: libxl_pci.c:1265:do_pci_remove: xc_deassign_device failed Done. Rebooting now xc: info: VIRTUAL MEMORY ARRANGEMENT: Loader: 0000000000100000->00000000001ad64c TOTAL: 0000000000000000->00000000ff800000 ENTRY ADDRESS: 0000000000100000 xc: info: PHYSICAL MEMORY ALLOCATION: 4KB PAGES: 0x0000000000000200 2MB PAGES: 0x00000000000003fb 1GB PAGES: 0x0000000000000002 libxl: error: libxl_pci.c:1055:libxl__device_pci_add: PCI device 0:d:0.0 is not assignable Waiting for domain Windows8 (domid 16) to die [pid 7447] Domain 16 has shut down, reason code 1 0x1 Action for shutdown reason code 1 is restart Domain 16 needs to be cleaned up: destroying the domain libxl: error: libxl_pci.c:1001:libxl__device_pci_reset: The kernel doesn't support reset from sysfs for PCI device 0000:0d:00.0 libxl: error: libxl_pci.c:1265:do_pci_remove: xc_deassign_device failed Done. Rebooting now xc: info: VIRTUAL MEMORY ARRANGEMENT: Loader: 0000000000100000->00000000001ad64c TOTAL: 0000000000000000->00000000ff800000 ENTRY ADDRESS: 0000000000100000 xc: info: PHYSICAL MEMORY ALLOCATION: 4KB PAGES: 0x0000000000000200 2MB PAGES: 0x00000000000003fb 1GB PAGES: 0x0000000000000002 libxl: error: libxl_pci.c:1055:libxl__device_pci_add: PCI device 0:d:0.0 is not assignable Waiting for domain Windows8 (domid 17) to die [pid 7447] Domain 17 has shut down, reason code 1 0x1 Action for shutdown reason code 1 is restart Domain 17 needs to be cleaned up: destroying the domain libxl: error: libxl_pci.c:1001:libxl__device_pci_reset: The kernel doesn't support reset from sysfs for PCI device 0000:0d:00.0 libxl: error: libxl_pci.c:1265:do_pci_remove: xc_deassign_device failed Done. Rebooting now xc: info: VIRTUAL MEMORY ARRANGEMENT: Loader: 0000000000100000->00000000001ad64c TOTAL: 0000000000000000->00000000ff800000 ENTRY ADDRESS: 0000000000100000 xc: info: PHYSICAL MEMORY ALLOCATION: 4KB PAGES: 0x0000000000000200 2MB PAGES: 0x00000000000003fb 1GB PAGES: 0x0000000000000002 libxl: error: libxl_pci.c:1055:libxl__device_pci_add: PCI device 0:d:0.0 is not assignable Waiting for domain Windows8 (domid 18) to die [pid 7447] Domain 18 has shut down, reason code 1 0x1 Action for shutdown reason code 1 is restart Domain 18 needs to be cleaned up: destroying the domain libxl: error: libxl_pci.c:1001:libxl__device_pci_reset: The kernel doesn't support reset from sysfs for PCI device 0000:0d:00.0 libxl: error: libxl_pci.c:1265:do_pci_remove: xc_deassign_device failed Done. Rebooting now xc: info: VIRTUAL MEMORY ARRANGEMENT: Loader: 0000000000100000->00000000001ad64c TOTAL: 0000000000000000->00000000ff800000 ENTRY ADDRESS: 0000000000100000 xc: info: PHYSICAL MEMORY ALLOCATION: 4KB PAGES: 0x0000000000000200 2MB PAGES: 0x00000000000003fb 1GB PAGES: 0x0000000000000002 libxl: error: libxl_pci.c:1055:libxl__device_pci_add: PCI device 0:d:0.0 is not assignable Waiting for domain Windows8 (domid 19) to die [pid 7447] Domain 19 has shut down, reason code 1 0x1 Action for shutdown reason code 1 is restart Domain 19 needs to be cleaned up: destroying the domain libxl: error: libxl_pci.c:1001:libxl__device_pci_reset: The kernel doesn't support reset from sysfs for PCI device 0000:0d:00.0 libxl: error: libxl_pci.c:1265:do_pci_remove: xc_deassign_device failed Done. Rebooting now xc: info: VIRTUAL MEMORY ARRANGEMENT: Loader: 0000000000100000->00000000001ad64c TOTAL: 0000000000000000->00000000ff800000 ENTRY ADDRESS: 0000000000100000 xc: info: PHYSICAL MEMORY ALLOCATION: 4KB PAGES: 0x0000000000000200 2MB PAGES: 0x00000000000003fb 1GB PAGES: 0x0000000000000002 libxl: error: libxl_pci.c:1055:libxl__device_pci_add: PCI device 0:d:0.0 is not assignable Waiting for domain Windows8 (domid 20) to die [pid 7447] Domain 20 has shut down, reason code 1 0x1 Action for shutdown reason code 1 is restart Domain 20 needs to be cleaned up: destroying the domain libxl: error: libxl_pci.c:1001:libxl__device_pci_reset: The kernel doesn't support reset from sysfs for PCI device 0000:0d:00.0 libxl: error: libxl_pci.c:1265:do_pci_remove: xc_deassign_device failed Done. Rebooting now xc: info: VIRTUAL MEMORY ARRANGEMENT: Loader: 0000000000100000->00000000001ad64c TOTAL: 0000000000000000->00000000ff800000 ENTRY ADDRESS: 0000000000100000 xc: info: PHYSICAL MEMORY ALLOCATION: 4KB PAGES: 0x0000000000000200 2MB PAGES: 0x00000000000003fb 1GB PAGES: 0x0000000000000002 libxl: error: libxl_pci.c:1055:libxl__device_pci_add: PCI device 0:d:0.0 is not assignable Waiting for domain Windows8 (domid 21) to die [pid 7447] --------------060301030907070908060303 Content-Type: text/plain; name="xl-Windows8.log.1" Content-Transfer-Encoding: 7bit Content-Disposition: attachment; filename="xl-Windows8.log.1" Waiting for domain Windows8 (domid 2) to die [pid 5545] Domain 2 has shut down, reason code 1 0x1 Action for shutdown reason code 1 is restart Domain 2 needs to be cleaned up: destroying the domain libxl: error: libxl_pci.c:1001:libxl__device_pci_reset: The kernel doesn't support reset from sysfs for PCI device 0000:0d:00.0 libxl: error: libxl_pci.c:1265:do_pci_remove: xc_deassign_device failed Done. Rebooting now xc: info: VIRTUAL MEMORY ARRANGEMENT: Loader: 0000000000100000->00000000001ad64c TOTAL: 0000000000000000->00000000ff800000 ENTRY ADDRESS: 0000000000100000 xc: info: PHYSICAL MEMORY ALLOCATION: 4KB PAGES: 0x0000000000000200 2MB PAGES: 0x00000000000003fb 1GB PAGES: 0x0000000000000002 libxl: error: libxl_pci.c:1055:libxl__device_pci_add: PCI device 0:d:0.0 is not assignable Waiting for domain Windows8 (domid 3) to die [pid 5545] Domain 3 has shut down, reason code 1 0x1 Action for shutdown reason code 1 is restart Domain 3 needs to be cleaned up: destroying the domain libxl: error: libxl_pci.c:1001:libxl__device_pci_reset: The kernel doesn't support reset from sysfs for PCI device 0000:0d:00.0 libxl: error: libxl_pci.c:1265:do_pci_remove: xc_deassign_device failed Done. Rebooting now xc: info: VIRTUAL MEMORY ARRANGEMENT: Loader: 0000000000100000->00000000001ad64c TOTAL: 0000000000000000->00000000ff800000 ENTRY ADDRESS: 0000000000100000 xc: info: PHYSICAL MEMORY ALLOCATION: 4KB PAGES: 0x0000000000000200 2MB PAGES: 0x00000000000003fb 1GB PAGES: 0x0000000000000002 libxl: error: libxl_pci.c:1055:libxl__device_pci_add: PCI device 0:d:0.0 is not assignable Waiting for domain Windows8 (domid 4) to die [pid 5545] Domain 4 has shut down, reason code 1 0x1 Action for shutdown reason code 1 is restart Domain 4 needs to be cleaned up: destroying the domain libxl: error: libxl_pci.c:1001:libxl__device_pci_reset: The kernel doesn't support reset from sysfs for PCI device 0000:0d:00.0 libxl: error: libxl_pci.c:1265:do_pci_remove: xc_deassign_device failed Done. Rebooting now xc: info: VIRTUAL MEMORY ARRANGEMENT: Loader: 0000000000100000->00000000001ad64c TOTAL: 0000000000000000->00000000ff800000 ENTRY ADDRESS: 0000000000100000 xc: info: PHYSICAL MEMORY ALLOCATION: 4KB PAGES: 0x0000000000000200 2MB PAGES: 0x00000000000003fb 1GB PAGES: 0x0000000000000002 libxl: error: libxl_pci.c:1055:libxl__device_pci_add: PCI device 0:d:0.0 is not assignable Waiting for domain Windows8 (domid 5) to die [pid 5545] Domain 5 has shut down, reason code 1 0x1 Action for shutdown reason code 1 is restart Domain 5 needs to be cleaned up: destroying the domain libxl: error: libxl_pci.c:1001:libxl__device_pci_reset: The kernel doesn't support reset from sysfs for PCI device 0000:0d:00.0 libxl: error: libxl_pci.c:1265:do_pci_remove: xc_deassign_device failed Done. Rebooting now xc: info: VIRTUAL MEMORY ARRANGEMENT: Loader: 0000000000100000->00000000001ad64c TOTAL: 0000000000000000->00000000ff800000 ENTRY ADDRESS: 0000000000100000 xc: info: PHYSICAL MEMORY ALLOCATION: 4KB PAGES: 0x0000000000000200 2MB PAGES: 0x00000000000003fb 1GB PAGES: 0x0000000000000002 libxl: error: libxl_pci.c:1055:libxl__device_pci_add: PCI device 0:d:0.0 is not assignable Waiting for domain Windows8 (domid 6) to die [pid 5545] Domain 6 has shut down, reason code 1 0x1 Action for shutdown reason code 1 is restart Domain 6 needs to be cleaned up: destroying the domain libxl: error: libxl_pci.c:1001:libxl__device_pci_reset: The kernel doesn't support reset from sysfs for PCI device 0000:0d:00.0 libxl: error: libxl_pci.c:1265:do_pci_remove: xc_deassign_device failed Done. Rebooting now xc: info: VIRTUAL MEMORY ARRANGEMENT: Loader: 0000000000100000->00000000001ad64c TOTAL: 0000000000000000->00000000ff800000 ENTRY ADDRESS: 0000000000100000 xc: info: PHYSICAL MEMORY ALLOCATION: 4KB PAGES: 0x0000000000000200 2MB PAGES: 0x00000000000003fb 1GB PAGES: 0x0000000000000002 libxl: error: libxl_pci.c:1055:libxl__device_pci_add: PCI device 0:d:0.0 is not assignable Waiting for domain Windows8 (domid 7) to die [pid 5545] Domain 7 has shut down, reason code 1 0x1 Action for shutdown reason code 1 is restart Domain 7 needs to be cleaned up: destroying the domain libxl: error: libxl_pci.c:1001:libxl__device_pci_reset: The kernel doesn't support reset from sysfs for PCI device 0000:0d:00.0 libxl: error: libxl_pci.c:1265:do_pci_remove: xc_deassign_device failed Done. Rebooting now xc: info: VIRTUAL MEMORY ARRANGEMENT: Loader: 0000000000100000->00000000001ad64c TOTAL: 0000000000000000->00000000ff800000 ENTRY ADDRESS: 0000000000100000 xc: info: PHYSICAL MEMORY ALLOCATION: 4KB PAGES: 0x0000000000000200 2MB PAGES: 0x00000000000003fb 1GB PAGES: 0x0000000000000002 libxl: error: libxl_pci.c:1055:libxl__device_pci_add: PCI device 0:d:0.0 is not assignable Waiting for domain Windows8 (domid 8) to die [pid 5545] Domain 8 has been destroyed. --------------060301030907070908060303 Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users --------------060301030907070908060303-- From xen-users-bounces@lists.xen.org Wed Sep 19 16:44:43 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Wed, 19 Sep 2012 16:44:43 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TENNJ-00031N-A0; Wed, 19 Sep 2012 16:43:45 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TENNH-00030r-LP for xen-users@lists.xen.org; Wed, 19 Sep 2012 16:43:44 +0000 Received: from [85.158.143.35:18115] by server-1.bemta-4.messagelabs.com id F4/39-05684-C36F9505; Wed, 19 Sep 2012 16:43:40 +0000 X-Env-Sender: singapore.mr.teo.en.ming@gmail.com X-Msg-Ref: server-8.tower-21.messagelabs.com!1348073014!15743053!1 X-Originating-IP: [209.85.160.45] X-SpamReason: No, hits=0.3 required=7.0 tests=ML_RADAR_SPEW_LINKS_14, RCVD_BY_IP,spamassassin: X-StarScan-Received: X-StarScan-Version: 6.6.1.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 8473 invoked from network); 19 Sep 2012 16:43:36 -0000 Received: from mail-pb0-f45.google.com (HELO mail-pb0-f45.google.com) (209.85.160.45) by server-8.tower-21.messagelabs.com with RC4-SHA encrypted SMTP; 19 Sep 2012 16:43:36 -0000 Received: by pbbrp12 with SMTP id rp12so2940985pbb.32 for ; Wed, 19 Sep 2012 09:43:34 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:disposition-notification-to:date:from:user-agent :mime-version:to:subject:content-type; bh=NhAEaT4RaQ8zkEU7XpSw6qrmedYXSJI/PPxUpKjERxI=; b=PY64vJkQntPimOZfS+lN+Kc9Wdu9kNOYzaynZygyOix+/LXQ7f5uzDMHhsZ/8W/6wi /dd9Y3cnqR46x9GuSX0ecbVPok8fGdTmI5JcLvL3gL8DFGksVOE/750FE85+IFYg00MS JXYNHf6Ap7UAPsq5VL2eIlPYgdaO4pYTuSqjlnaisF3xVC+H2yLjnbnrSnlAhqtjplZe j+RnW+1Wv35p2lDtgtlDXxUJRjs4BHY9Hz/lwnRha5OPSw/JMw+Hsz9ZOkzaZDY2Nb/J ZEFiji9ByKzqLQkTgHaxwHhGDksSDYKMA242Iyb6suSp567j94rqZXLqdiRucI1IVmAt xASg== Received: by 10.68.116.228 with SMTP id jz4mr8786686pbb.166.1348073014138; Wed, 19 Sep 2012 09:43:34 -0700 (PDT) Received: from [192.168.1.2] (cm70.gamma203.maxonline.com.sg. [202.156.203.70]) by mx.google.com with ESMTPS id b6sm984792paz.9.2012.09.19.09.43.31 (version=SSLv3 cipher=OTHER); Wed, 19 Sep 2012 09:43:33 -0700 (PDT) Message-ID: <5059F632.3050808@gmail.com> Date: Thu, 20 Sep 2012 00:43:30 +0800 From: "Teo En Ming (Zhang Enming)" User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:10.0.2) Gecko/20120216 Thunderbird/10.0.2 MIME-Version: 1.0 To: "xen-users@lists.xen.org" , "xen-devel@lists.xen.org" , 'Teo En Ming' Content-Type: multipart/mixed; boundary="------------060301030907070908060303" Subject: [Xen-users] VGA Passthrough with Xen 4.3-unstable? X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org This is a multi-part message in MIME format. --------------060301030907070908060303 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Dear All, I have tried to apply VGA passthrough patches hosted at Jean David Techer's website to Xen 4.3-unstable. However, I cannot get VGA passthrough to work with Xen 4.3-unstable. Are the VGA passthrough patches hosted at David Techer's website incompatible with Xen 4.3-unstable? This is David Techer's website: http://www.davidgis.fr/blog/index.php?2011/12/07/860-xen-42unstable-patches-for-vga-pass-through I have also provided error logs in this email for troubleshooting purposes. Please advise. Thank you very much. -- Yours sincerely, Mr. Teo En Ming (Zhang Enming) Singapore --------------060301030907070908060303 Content-Type: text/x-log; name="qemu-dm-Windows8.log" Content-Transfer-Encoding: 7bit Content-Disposition: attachment; filename="qemu-dm-Windows8.log" domid: 21 Strip off blktap sub-type prefix to /etc/xen/images/windows8.img (drv 'aio') Using file /etc/xen/images/windows8.img in read-write mode Strip off blktap sub-type prefix to /home/flyon/windows8.iso (drv 'aio') Using file /home/flyon/windows8.iso in read-only mode Watching /local/domain/0/device-model/21/logdirty/cmd Watching /local/domain/0/device-model/21/command Watching /local/domain/21/cpu qemu_map_cache_init nr_buckets = 10000 size 4194304 shared page at pfn feffd buffered io page at pfn feffb Guest uuid = 40290d87-cbd9-4656-841b-ba3d95621163 Register xen platform. Done register platform. platform_fixed_ioport: changed ro/rw state of ROM memory area. now is rw state. xs_read(/local/domain/0/device-model/21/xen_extended_power_mgmt): read error medium change watch on `hdc' (index: 1): aio:/home/flyon/windows8.iso I/O request not ready: 0, ptr: 0, port: 0, data: 0, count: 0, size: 0 Log-dirty: no command yet. I/O request not ready: 0, ptr: 0, port: 0, data: 0, count: 0, size: 0 I/O request not ready: 0, ptr: 0, port: 0, data: 0, count: 0, size: 0 vcpu-set: watch node error. I/O request not ready: 0, ptr: 0, port: 0, data: 0, count: 0, size: 0 xs_read(/local/domain/21/log-throttling): read error qemu: ignoring not-understood drive `/local/domain/21/log-throttling' medium change watch on `/local/domain/21/log-throttling' - unknown device, ignored I/O request not ready: 0, ptr: 0, port: 0, data: 0, count: 0, size: 0 I/O request not ready: 0, ptr: 0, port: 0, data: 0, count: 0, size: 0 I/O request not ready: 0, ptr: 0, port: 0, data: 0, count: 0, size: 0 I/O request not ready: 0, ptr: 0, port: 0, data: 0, count: 0, size: 0 I/O request not ready: 0, ptr: 0, port: 0, data: 0, count: 0, size: 0 I/O request not ready: 0, ptr: 0, port: 0, data: 0, count: 0, size: 0 I/O request not ready: 0, ptr: 0, port: 0, data: 0, count: 0, size: 0 I/O request not ready: 0, ptr: 0, port: 0, data: 0, count: 0, size: 0 platform_fixed_ioport: changed ro/rw state of ROM memory area. now is rw state. platform_fixed_ioport: changed ro/rw state of ROM memory area. now is ro state. --------------060301030907070908060303 Content-Type: text/plain; name="qemu-dm-Windows8.log.1" Content-Transfer-Encoding: 7bit Content-Disposition: attachment; filename="qemu-dm-Windows8.log.1" domid: 20 Strip off blktap sub-type prefix to /etc/xen/images/windows8.img (drv 'aio') Using file /etc/xen/images/windows8.img in read-write mode Strip off blktap sub-type prefix to /home/flyon/windows8.iso (drv 'aio') Using file /home/flyon/windows8.iso in read-only mode Watching /local/domain/0/device-model/20/logdirty/cmd Watching /local/domain/0/device-model/20/command Watching /local/domain/20/cpu qemu_map_cache_init nr_buckets = 10000 size 4194304 shared page at pfn feffd buffered io page at pfn feffb Guest uuid = 4a77731a-8b25-4fd8-ac7c-f4d607784917 Register xen platform. Done register platform. platform_fixed_ioport: changed ro/rw state of ROM memory area. now is rw state. xs_read(/local/domain/0/device-model/20/xen_extended_power_mgmt): read error medium change watch on `hdc' (index: 1): aio:/home/flyon/windows8.iso I/O request not ready: 0, ptr: 0, port: 0, data: 0, count: 0, size: 0 Log-dirty: no command yet. I/O request not ready: 0, ptr: 0, port: 0, data: 0, count: 0, size: 0 I/O request not ready: 0, ptr: 0, port: 0, data: 0, count: 0, size: 0 vcpu-set: watch node error. I/O request not ready: 0, ptr: 0, port: 0, data: 0, count: 0, size: 0 xs_read(/local/domain/20/log-throttling): read error qemu: ignoring not-understood drive `/local/domain/20/log-throttling' medium change watch on `/local/domain/20/log-throttling' - unknown device, ignored I/O request not ready: 0, ptr: 0, port: 0, data: 0, count: 0, size: 0 I/O request not ready: 0, ptr: 0, port: 0, data: 0, count: 0, size: 0 I/O request not ready: 0, ptr: 0, port: 0, data: 0, count: 0, size: 0 I/O request not ready: 0, ptr: 0, port: 0, data: 0, count: 0, size: 0 I/O request not ready: 0, ptr: 0, port: 0, data: 0, count: 0, size: 0 I/O request not ready: 0, ptr: 0, port: 0, data: 0, count: 0, size: 0 I/O request not ready: 0, ptr: 0, port: 0, data: 0, count: 0, size: 0 I/O request not ready: 0, ptr: 0, port: 0, data: 0, count: 0, size: 0 platform_fixed_ioport: changed ro/rw state of ROM memory area. now is rw state. platform_fixed_ioport: changed ro/rw state of ROM memory area. now is ro state. reset requested in cpu_handle_ioreq. Issued domain 20 reboot --------------060301030907070908060303 Content-Type: text/plain; name="qemu-dm-Windows8.log.2" Content-Transfer-Encoding: 7bit Content-Disposition: attachment; filename="qemu-dm-Windows8.log.2" domid: 19 Strip off blktap sub-type prefix to /etc/xen/images/windows8.img (drv 'aio') Using file /etc/xen/images/windows8.img in read-write mode Strip off blktap sub-type prefix to /home/flyon/windows8.iso (drv 'aio') Using file /home/flyon/windows8.iso in read-only mode Watching /local/domain/0/device-model/19/logdirty/cmd Watching /local/domain/0/device-model/19/command Watching /local/domain/19/cpu qemu_map_cache_init nr_buckets = 10000 size 4194304 shared page at pfn feffd buffered io page at pfn feffb Guest uuid = e72e564f-812a-49dd-9c78-d76a957ebeab Register xen platform. Done register platform. platform_fixed_ioport: changed ro/rw state of ROM memory area. now is rw state. xs_read(/local/domain/0/device-model/19/xen_extended_power_mgmt): read error medium change watch on `hdc' (index: 1): aio:/home/flyon/windows8.iso I/O request not ready: 0, ptr: 0, port: 0, data: 0, count: 0, size: 0 Log-dirty: no command yet. I/O request not ready: 0, ptr: 0, port: 0, data: 0, count: 0, size: 0 I/O request not ready: 0, ptr: 0, port: 0, data: 0, count: 0, size: 0 vcpu-set: watch node error. I/O request not ready: 0, ptr: 0, port: 0, data: 0, count: 0, size: 0 xs_read(/local/domain/19/log-throttling): read error qemu: ignoring not-understood drive `/local/domain/19/log-throttling' medium change watch on `/local/domain/19/log-throttling' - unknown device, ignored I/O request not ready: 0, ptr: 0, port: 0, data: 0, count: 0, size: 0 I/O request not ready: 0, ptr: 0, port: 0, data: 0, count: 0, size: 0 I/O request not ready: 0, ptr: 0, port: 0, data: 0, count: 0, size: 0 I/O request not ready: 0, ptr: 0, port: 0, data: 0, count: 0, size: 0 I/O request not ready: 0, ptr: 0, port: 0, data: 0, count: 0, size: 0 I/O request not ready: 0, ptr: 0, port: 0, data: 0, count: 0, size: 0 I/O request not ready: 0, ptr: 0, port: 0, data: 0, count: 0, size: 0 I/O request not ready: 0, ptr: 0, port: 0, data: 0, count: 0, size: 0 platform_fixed_ioport: changed ro/rw state of ROM memory area. now is rw state. platform_fixed_ioport: changed ro/rw state of ROM memory area. now is ro state. reset requested in cpu_handle_ioreq. Issued domain 19 reboot --------------060301030907070908060303 Content-Type: text/plain; name="qemu-dm-Windows8.log.3" Content-Transfer-Encoding: 7bit Content-Disposition: attachment; filename="qemu-dm-Windows8.log.3" domid: 18 Strip off blktap sub-type prefix to /etc/xen/images/windows8.img (drv 'aio') Using file /etc/xen/images/windows8.img in read-write mode Strip off blktap sub-type prefix to /home/flyon/windows8.iso (drv 'aio') Using file /home/flyon/windows8.iso in read-only mode Watching /local/domain/0/device-model/18/logdirty/cmd Watching /local/domain/0/device-model/18/command Watching /local/domain/18/cpu qemu_map_cache_init nr_buckets = 10000 size 4194304 shared page at pfn feffd buffered io page at pfn feffb Guest uuid = 54da941e-ff5f-4db6-919a-00579c8fccc3 Register xen platform. Done register platform. platform_fixed_ioport: changed ro/rw state of ROM memory area. now is rw state. xs_read(/local/domain/0/device-model/18/xen_extended_power_mgmt): read error medium change watch on `hdc' (index: 1): aio:/home/flyon/windows8.iso I/O request not ready: 0, ptr: 0, port: 0, data: 0, count: 0, size: 0 Log-dirty: no command yet. I/O request not ready: 0, ptr: 0, port: 0, data: 0, count: 0, size: 0 I/O request not ready: 0, ptr: 0, port: 0, data: 0, count: 0, size: 0 vcpu-set: watch node error. I/O request not ready: 0, ptr: 0, port: 0, data: 0, count: 0, size: 0 xs_read(/local/domain/18/log-throttling): read error qemu: ignoring not-understood drive `/local/domain/18/log-throttling' medium change watch on `/local/domain/18/log-throttling' - unknown device, ignored I/O request not ready: 0, ptr: 0, port: 0, data: 0, count: 0, size: 0 I/O request not ready: 0, ptr: 0, port: 0, data: 0, count: 0, size: 0 I/O request not ready: 0, ptr: 0, port: 0, data: 0, count: 0, size: 0 I/O request not ready: 0, ptr: 0, port: 0, data: 0, count: 0, size: 0 I/O request not ready: 0, ptr: 0, port: 0, data: 0, count: 0, size: 0 I/O request not ready: 0, ptr: 0, port: 0, data: 0, count: 0, size: 0 I/O request not ready: 0, ptr: 0, port: 0, data: 0, count: 0, size: 0 I/O request not ready: 0, ptr: 0, port: 0, data: 0, count: 0, size: 0 platform_fixed_ioport: changed ro/rw state of ROM memory area. now is rw state. platform_fixed_ioport: changed ro/rw state of ROM memory area. now is ro state. reset requested in cpu_handle_ioreq. Issued domain 18 reboot --------------060301030907070908060303 Content-Type: text/plain; name="qemu-dm-Windows8.log.4" Content-Transfer-Encoding: 7bit Content-Disposition: attachment; filename="qemu-dm-Windows8.log.4" domid: 17 Strip off blktap sub-type prefix to /etc/xen/images/windows8.img (drv 'aio') Using file /etc/xen/images/windows8.img in read-write mode Strip off blktap sub-type prefix to /home/flyon/windows8.iso (drv 'aio') Using file /home/flyon/windows8.iso in read-only mode Watching /local/domain/0/device-model/17/logdirty/cmd Watching /local/domain/0/device-model/17/command Watching /local/domain/17/cpu qemu_map_cache_init nr_buckets = 10000 size 4194304 shared page at pfn feffd buffered io page at pfn feffb Guest uuid = 467e63fb-1054-4b1e-bb58-0ac6a2fe77ef Register xen platform. Done register platform. platform_fixed_ioport: changed ro/rw state of ROM memory area. now is rw state. xs_read(/local/domain/0/device-model/17/xen_extended_power_mgmt): read error medium change watch on `hdc' (index: 1): aio:/home/flyon/windows8.iso I/O request not ready: 0, ptr: 0, port: 0, data: 0, count: 0, size: 0 Log-dirty: no command yet. I/O request not ready: 0, ptr: 0, port: 0, data: 0, count: 0, size: 0 I/O request not ready: 0, ptr: 0, port: 0, data: 0, count: 0, size: 0 vcpu-set: watch node error. I/O request not ready: 0, ptr: 0, port: 0, data: 0, count: 0, size: 0 xs_read(/local/domain/17/log-throttling): read error qemu: ignoring not-understood drive `/local/domain/17/log-throttling' medium change watch on `/local/domain/17/log-throttling' - unknown device, ignored I/O request not ready: 0, ptr: 0, port: 0, data: 0, count: 0, size: 0 I/O request not ready: 0, ptr: 0, port: 0, data: 0, count: 0, size: 0 I/O request not ready: 0, ptr: 0, port: 0, data: 0, count: 0, size: 0 I/O request not ready: 0, ptr: 0, port: 0, data: 0, count: 0, size: 0 I/O request not ready: 0, ptr: 0, port: 0, data: 0, count: 0, size: 0 I/O request not ready: 0, ptr: 0, port: 0, data: 0, count: 0, size: 0 I/O request not ready: 0, ptr: 0, port: 0, data: 0, count: 0, size: 0 I/O request not ready: 0, ptr: 0, port: 0, data: 0, count: 0, size: 0 platform_fixed_ioport: changed ro/rw state of ROM memory area. now is rw state. platform_fixed_ioport: changed ro/rw state of ROM memory area. now is ro state. reset requested in cpu_handle_ioreq. Issued domain 17 reboot --------------060301030907070908060303 Content-Type: text/plain; name="qemu-dm-Windows8.log.5" Content-Transfer-Encoding: 7bit Content-Disposition: attachment; filename="qemu-dm-Windows8.log.5" domid: 16 Strip off blktap sub-type prefix to /etc/xen/images/windows8.img (drv 'aio') Using file /etc/xen/images/windows8.img in read-write mode Strip off blktap sub-type prefix to /home/flyon/windows8.iso (drv 'aio') Using file /home/flyon/windows8.iso in read-only mode Watching /local/domain/0/device-model/16/logdirty/cmd Watching /local/domain/0/device-model/16/command Watching /local/domain/16/cpu qemu_map_cache_init nr_buckets = 10000 size 4194304 shared page at pfn feffd buffered io page at pfn feffb Guest uuid = fbe85911-c17d-4b2d-9ae0-33b2211cb22f Register xen platform. Done register platform. platform_fixed_ioport: changed ro/rw state of ROM memory area. now is rw state. xs_read(/local/domain/0/device-model/16/xen_extended_power_mgmt): read error medium change watch on `hdc' (index: 1): aio:/home/flyon/windows8.iso I/O request not ready: 0, ptr: 0, port: 0, data: 0, count: 0, size: 0 Log-dirty: no command yet. I/O request not ready: 0, ptr: 0, port: 0, data: 0, count: 0, size: 0 I/O request not ready: 0, ptr: 0, port: 0, data: 0, count: 0, size: 0 vcpu-set: watch node error. I/O request not ready: 0, ptr: 0, port: 0, data: 0, count: 0, size: 0 xs_read(/local/domain/16/log-throttling): read error qemu: ignoring not-understood drive `/local/domain/16/log-throttling' medium change watch on `/local/domain/16/log-throttling' - unknown device, ignored I/O request not ready: 0, ptr: 0, port: 0, data: 0, count: 0, size: 0 I/O request not ready: 0, ptr: 0, port: 0, data: 0, count: 0, size: 0 I/O request not ready: 0, ptr: 0, port: 0, data: 0, count: 0, size: 0 I/O request not ready: 0, ptr: 0, port: 0, data: 0, count: 0, size: 0 I/O request not ready: 0, ptr: 0, port: 0, data: 0, count: 0, size: 0 I/O request not ready: 0, ptr: 0, port: 0, data: 0, count: 0, size: 0 I/O request not ready: 0, ptr: 0, port: 0, data: 0, count: 0, size: 0 I/O request not ready: 0, ptr: 0, port: 0, data: 0, count: 0, size: 0 platform_fixed_ioport: changed ro/rw state of ROM memory area. now is rw state. platform_fixed_ioport: changed ro/rw state of ROM memory area. now is ro state. reset requested in cpu_handle_ioreq. Issued domain 16 reboot --------------060301030907070908060303 Content-Type: text/plain; name="qemu-dm-Windows8.log.6" Content-Transfer-Encoding: 7bit Content-Disposition: attachment; filename="qemu-dm-Windows8.log.6" domid: 15 Strip off blktap sub-type prefix to /etc/xen/images/windows8.img (drv 'aio') Using file /etc/xen/images/windows8.img in read-write mode Strip off blktap sub-type prefix to /home/flyon/windows8.iso (drv 'aio') Using file /home/flyon/windows8.iso in read-only mode Watching /local/domain/0/device-model/15/logdirty/cmd Watching /local/domain/0/device-model/15/command Watching /local/domain/15/cpu qemu_map_cache_init nr_buckets = 10000 size 4194304 shared page at pfn feffd buffered io page at pfn feffb Guest uuid = 6ffa0353-1b02-4747-87f6-e30cb6067a76 Register xen platform. Done register platform. platform_fixed_ioport: changed ro/rw state of ROM memory area. now is rw state. xs_read(/local/domain/0/device-model/15/xen_extended_power_mgmt): read error medium change watch on `hdc' (index: 1): aio:/home/flyon/windows8.iso I/O request not ready: 0, ptr: 0, port: 0, data: 0, count: 0, size: 0 Log-dirty: no command yet. I/O request not ready: 0, ptr: 0, port: 0, data: 0, count: 0, size: 0 I/O request not ready: 0, ptr: 0, port: 0, data: 0, count: 0, size: 0 vcpu-set: watch node error. I/O request not ready: 0, ptr: 0, port: 0, data: 0, count: 0, size: 0 xs_read(/local/domain/15/log-throttling): read error qemu: ignoring not-understood drive `/local/domain/15/log-throttling' medium change watch on `/local/domain/15/log-throttling' - unknown device, ignored I/O request not ready: 0, ptr: 0, port: 0, data: 0, count: 0, size: 0 I/O request not ready: 0, ptr: 0, port: 0, data: 0, count: 0, size: 0 I/O request not ready: 0, ptr: 0, port: 0, data: 0, count: 0, size: 0 I/O request not ready: 0, ptr: 0, port: 0, data: 0, count: 0, size: 0 I/O request not ready: 0, ptr: 0, port: 0, data: 0, count: 0, size: 0 I/O request not ready: 0, ptr: 0, port: 0, data: 0, count: 0, size: 0 I/O request not ready: 0, ptr: 0, port: 0, data: 0, count: 0, size: 0 I/O request not ready: 0, ptr: 0, port: 0, data: 0, count: 0, size: 0 platform_fixed_ioport: changed ro/rw state of ROM memory area. now is rw state. platform_fixed_ioport: changed ro/rw state of ROM memory area. now is ro state. reset requested in cpu_handle_ioreq. Issued domain 15 reboot --------------060301030907070908060303 Content-Type: text/plain; name="qemu-dm-Windows8.log.7" Content-Transfer-Encoding: 7bit Content-Disposition: attachment; filename="qemu-dm-Windows8.log.7" domid: 14 Strip off blktap sub-type prefix to /etc/xen/images/windows8.img (drv 'aio') Using file /etc/xen/images/windows8.img in read-write mode Strip off blktap sub-type prefix to /home/flyon/windows8.iso (drv 'aio') Using file /home/flyon/windows8.iso in read-only mode Watching /local/domain/0/device-model/14/logdirty/cmd Watching /local/domain/0/device-model/14/command Watching /local/domain/14/cpu qemu_map_cache_init nr_buckets = 10000 size 4194304 shared page at pfn feffd buffered io page at pfn feffb Guest uuid = 908cd1e3-59b3-41f3-88a9-6d846fdbb675 Register xen platform. Done register platform. platform_fixed_ioport: changed ro/rw state of ROM memory area. now is rw state. xs_read(/local/domain/0/device-model/14/xen_extended_power_mgmt): read error medium change watch on `hdc' (index: 1): aio:/home/flyon/windows8.iso I/O request not ready: 0, ptr: 0, port: 0, data: 0, count: 0, size: 0 Log-dirty: no command yet. I/O request not ready: 0, ptr: 0, port: 0, data: 0, count: 0, size: 0 I/O request not ready: 0, ptr: 0, port: 0, data: 0, count: 0, size: 0 vcpu-set: watch node error. I/O request not ready: 0, ptr: 0, port: 0, data: 0, count: 0, size: 0 xs_read(/local/domain/14/log-throttling): read error qemu: ignoring not-understood drive `/local/domain/14/log-throttling' medium change watch on `/local/domain/14/log-throttling' - unknown device, ignored I/O request not ready: 0, ptr: 0, port: 0, data: 0, count: 0, size: 0 I/O request not ready: 0, ptr: 0, port: 0, data: 0, count: 0, size: 0 I/O request not ready: 0, ptr: 0, port: 0, data: 0, count: 0, size: 0 I/O request not ready: 0, ptr: 0, port: 0, data: 0, count: 0, size: 0 I/O request not ready: 0, ptr: 0, port: 0, data: 0, count: 0, size: 0 I/O request not ready: 0, ptr: 0, port: 0, data: 0, count: 0, size: 0 I/O request not ready: 0, ptr: 0, port: 0, data: 0, count: 0, size: 0 I/O request not ready: 0, ptr: 0, port: 0, data: 0, count: 0, size: 0 platform_fixed_ioport: changed ro/rw state of ROM memory area. now is rw state. platform_fixed_ioport: changed ro/rw state of ROM memory area. now is ro state. reset requested in cpu_handle_ioreq. Issued domain 14 reboot --------------060301030907070908060303 Content-Type: text/plain; name="qemu-dm-Windows8.log.8" Content-Transfer-Encoding: 7bit Content-Disposition: attachment; filename="qemu-dm-Windows8.log.8" domid: 13 Strip off blktap sub-type prefix to /etc/xen/images/windows8.img (drv 'aio') Using file /etc/xen/images/windows8.img in read-write mode Strip off blktap sub-type prefix to /home/flyon/windows8.iso (drv 'aio') Using file /home/flyon/windows8.iso in read-only mode Watching /local/domain/0/device-model/13/logdirty/cmd Watching /local/domain/0/device-model/13/command Watching /local/domain/13/cpu qemu_map_cache_init nr_buckets = 10000 size 4194304 shared page at pfn feffd buffered io page at pfn feffb Guest uuid = 7a9ba58a-35c9-4ad3-af42-5f371268d141 Register xen platform. Done register platform. platform_fixed_ioport: changed ro/rw state of ROM memory area. now is rw state. xs_read(/local/domain/0/device-model/13/xen_extended_power_mgmt): read error medium change watch on `hdc' (index: 1): aio:/home/flyon/windows8.iso I/O request not ready: 0, ptr: 0, port: 0, data: 0, count: 0, size: 0 Log-dirty: no command yet. I/O request not ready: 0, ptr: 0, port: 0, data: 0, count: 0, size: 0 I/O request not ready: 0, ptr: 0, port: 0, data: 0, count: 0, size: 0 vcpu-set: watch node error. I/O request not ready: 0, ptr: 0, port: 0, data: 0, count: 0, size: 0 xs_read(/local/domain/13/log-throttling): read error qemu: ignoring not-understood drive `/local/domain/13/log-throttling' medium change watch on `/local/domain/13/log-throttling' - unknown device, ignored I/O request not ready: 0, ptr: 0, port: 0, data: 0, count: 0, size: 0 I/O request not ready: 0, ptr: 0, port: 0, data: 0, count: 0, size: 0 I/O request not ready: 0, ptr: 0, port: 0, data: 0, count: 0, size: 0 I/O request not ready: 0, ptr: 0, port: 0, data: 0, count: 0, size: 0 I/O request not ready: 0, ptr: 0, port: 0, data: 0, count: 0, size: 0 I/O request not ready: 0, ptr: 0, port: 0, data: 0, count: 0, size: 0 I/O request not ready: 0, ptr: 0, port: 0, data: 0, count: 0, size: 0 I/O request not ready: 0, ptr: 0, port: 0, data: 0, count: 0, size: 0 platform_fixed_ioport: changed ro/rw state of ROM memory area. now is rw state. platform_fixed_ioport: changed ro/rw state of ROM memory area. now is ro state. reset requested in cpu_handle_ioreq. Issued domain 13 reboot --------------060301030907070908060303 Content-Type: text/plain; name="qemu-dm-Windows8.log.9" Content-Transfer-Encoding: 7bit Content-Disposition: attachment; filename="qemu-dm-Windows8.log.9" domid: 12 Strip off blktap sub-type prefix to /etc/xen/images/windows8.img (drv 'aio') Using file /etc/xen/images/windows8.img in read-write mode Strip off blktap sub-type prefix to /home/flyon/windows8.iso (drv 'aio') Using file /home/flyon/windows8.iso in read-only mode Watching /local/domain/0/device-model/12/logdirty/cmd Watching /local/domain/0/device-model/12/command Watching /local/domain/12/cpu qemu_map_cache_init nr_buckets = 10000 size 4194304 shared page at pfn feffd buffered io page at pfn feffb Guest uuid = 3fdbe19b-2484-4f51-a781-45feccb66d65 Register xen platform. Done register platform. platform_fixed_ioport: changed ro/rw state of ROM memory area. now is rw state. xs_read(/local/domain/0/device-model/12/xen_extended_power_mgmt): read error medium change watch on `hdc' (index: 1): aio:/home/flyon/windows8.iso I/O request not ready: 0, ptr: 0, port: 0, data: 0, count: 0, size: 0 Log-dirty: no command yet. I/O request not ready: 0, ptr: 0, port: 0, data: 0, count: 0, size: 0 I/O request not ready: 0, ptr: 0, port: 0, data: 0, count: 0, size: 0 vcpu-set: watch node error. I/O request not ready: 0, ptr: 0, port: 0, data: 0, count: 0, size: 0 xs_read(/local/domain/12/log-throttling): read error qemu: ignoring not-understood drive `/local/domain/12/log-throttling' medium change watch on `/local/domain/12/log-throttling' - unknown device, ignored I/O request not ready: 0, ptr: 0, port: 0, data: 0, count: 0, size: 0 I/O request not ready: 0, ptr: 0, port: 0, data: 0, count: 0, size: 0 I/O request not ready: 0, ptr: 0, port: 0, data: 0, count: 0, size: 0 I/O request not ready: 0, ptr: 0, port: 0, data: 0, count: 0, size: 0 I/O request not ready: 0, ptr: 0, port: 0, data: 0, count: 0, size: 0 I/O request not ready: 0, ptr: 0, port: 0, data: 0, count: 0, size: 0 I/O request not ready: 0, ptr: 0, port: 0, data: 0, count: 0, size: 0 I/O request not ready: 0, ptr: 0, port: 0, data: 0, count: 0, size: 0 platform_fixed_ioport: changed ro/rw state of ROM memory area. now is rw state. platform_fixed_ioport: changed ro/rw state of ROM memory area. now is ro state. reset requested in cpu_handle_ioreq. Issued domain 12 reboot --------------060301030907070908060303 Content-Type: text/plain; name="qemu-dm-Windows8.log.10" Content-Transfer-Encoding: 7bit Content-Disposition: attachment; filename="qemu-dm-Windows8.log.10" domid: 11 Strip off blktap sub-type prefix to /etc/xen/images/windows8.img (drv 'aio') Using file /etc/xen/images/windows8.img in read-write mode Strip off blktap sub-type prefix to /home/flyon/windows8.iso (drv 'aio') Using file /home/flyon/windows8.iso in read-only mode Watching /local/domain/0/device-model/11/logdirty/cmd Watching /local/domain/0/device-model/11/command Watching /local/domain/11/cpu qemu_map_cache_init nr_buckets = 10000 size 4194304 shared page at pfn feffd buffered io page at pfn feffb Guest uuid = ce6cf88a-65c6-4bf2-ab37-6881a1909bb5 Register xen platform. Done register platform. platform_fixed_ioport: changed ro/rw state of ROM memory area. now is rw state. xs_read(/local/domain/0/device-model/11/xen_extended_power_mgmt): read error medium change watch on `hdc' (index: 1): aio:/home/flyon/windows8.iso I/O request not ready: 0, ptr: 0, port: 0, data: 0, count: 0, size: 0 Log-dirty: no command yet. I/O request not ready: 0, ptr: 0, port: 0, data: 0, count: 0, size: 0 I/O request not ready: 0, ptr: 0, port: 0, data: 0, count: 0, size: 0 vcpu-set: watch node error. I/O request not ready: 0, ptr: 0, port: 0, data: 0, count: 0, size: 0 xs_read(/local/domain/11/log-throttling): read error qemu: ignoring not-understood drive `/local/domain/11/log-throttling' medium change watch on `/local/domain/11/log-throttling' - unknown device, ignored I/O request not ready: 0, ptr: 0, port: 0, data: 0, count: 0, size: 0 I/O request not ready: 0, ptr: 0, port: 0, data: 0, count: 0, size: 0 I/O request not ready: 0, ptr: 0, port: 0, data: 0, count: 0, size: 0 I/O request not ready: 0, ptr: 0, port: 0, data: 0, count: 0, size: 0 I/O request not ready: 0, ptr: 0, port: 0, data: 0, count: 0, size: 0 I/O request not ready: 0, ptr: 0, port: 0, data: 0, count: 0, size: 0 I/O request not ready: 0, ptr: 0, port: 0, data: 0, count: 0, size: 0 I/O request not ready: 0, ptr: 0, port: 0, data: 0, count: 0, size: 0 platform_fixed_ioport: changed ro/rw state of ROM memory area. now is rw state. platform_fixed_ioport: changed ro/rw state of ROM memory area. now is ro state. reset requested in cpu_handle_ioreq. Issued domain 11 reboot --------------060301030907070908060303 Content-Type: text/plain; name="Windows8.txt" Content-Transfer-Encoding: base64 Content-Disposition: attachment; filename="Windows8.txt" IyBYTCBkb21haW4gY29uZmlndXJhdGlvbiBmaWxlIGZvciBXaW5kb3dzIDggQ29uc3VtZXIg UHJldmlldyA2NC1iaXQgRW5nbGlzaCBIVk0gZG9tVQ0KIyBQbGVhc2UgcmVmZXIgdG8gIm1h biB4bC5jZmciIGZvciBmdXJ0aGVyIGV4cGxhbmF0aW9ucy4NCiMgU2VlIGFsc28gZG9jcy9t aXNjL3hsLW5ldHdvcmstY29uZmlndXJhdGlvbi5tYXJrZG93biBhbmQNCiMgZG9jcy9taXNj L3hsLWRpc2stY29uZmlndXJhdGlvbi50eHQNCiMgV3JpdHRlbiBieSBUZW8gRW4gTWluZyAo WmhhbmcgRW5taW5nKQ0KIyBFbWFpbDogdGVvLmVuLm1pbmdAZ21haWwuY29tDQojIE1vYmls ZSBQaG9uZTogKzY1LTgzNjktMjYxOA0KIyBDb3VudHJ5OiBTaW5nYXBvcmUNCiMgRGF0ZTog MTggTWFyIDIwMTIgU3VuDQpuYW1lPSJXaW5kb3dzOCINCiMgUHJvZHVjdCBLZXk6IFdKQlJY LTJON0IyLUNDQkY2LVZQUDk3LVI4OFhWDQpidWlsZGVyPSJodm0iDQp2Y3B1cz0xMg0KbWVt b3J5PTEyMDAwDQpvbl9wb3dlcm9mZj0iZGVzdHJveSINCm9uX3JlYm9vdD0icmVzdGFydCIN Cm9uX2NyYXNoPSJkZXN0cm95Ig0KZGlzaz1bICdmb3JtYXQ9cmF3LCB2ZGV2PWhkYSwgYWNj ZXNzPXJ3LCB0YXJnZXQ9L2V0Yy94ZW4vaW1hZ2VzL3dpbmRvd3M4LmltZycsICdmb3JtYXQ9 cmF3LCB2ZGV2PWhkYywgYWNjZXNzPXJvLCBkZXZ0eXBlPWNkcm9tLCB0YXJnZXQ9L2hvbWUv Zmx5b24vd2luZG93czguaXNvJyBdDQp2aWY9WyAnYnJpZGdlPWV0aDAsdHlwZT1pb2VtdSxt b2RlbD1lMTAwMCcgXQ0KI2Jvb3Q9W2N8ZHxuXQ0KIyBTZWxlY3RzIHRoZSBlbXVsYXRlZCB2 aXJ0dWFsIGRldmljZSB0byBib290IGZyb20uIE9wdGlvbnMgYXJlIGhhcmQgZGlzayAoYyks IGNkLXJvbSAoZCkgb3IgbmV0d29yay9QWEUgKG4pLg0KIyBNdWx0aXBsZSBvcHRpb25zIGNh biBiZSBnaXZlbiBhbmQgd2lsbCBiZSBhdHRlbXB0ZWQgaW4gdGhlIG9yZGVyIHRoZXkgYXJl IGdpdmVuLiBlLmcuIHRvIGJvb3QgZnJvbSBjZC1yb20NCiMgYnV0IGZhbGxiYWNrIHRvIHRo ZSBoYXJkIGRpc2sgeW91IGNhbiBnaXZlIGRjLiBUaGUgZGVmYXVsdCBpcyBjZC4NCmJvb3Q9 ImRjIg0KYWNwaT0xDQp4ZW5fcGxhdGZvcm1fcGNpPTENCnZpcmlkaWFuPTENCnN0ZHZnYT0x DQoNCnZuYz0xDQp2bmNsaXN0ZW49IjE5Mi4xNjguMjUuNTAiDQp2bmNkaXNwbGF5PTANCnZu Y3VudXNlZD0xDQp2bmNwYXNzd2Q9IiINCnNkbD0wDQp1c2I9MQ0KdXNiZGV2aWNlPSJ0YWJs ZXQiDQojIEVuYWJsZSBYZW4gVkdBIFBhc3N0aHJvdWdoDQpnZnhfcGFzc3RocnU9MQ0KIyBW R0EgUGFzc3Rocm91Z2ggTlZJRElBIFF1YWRybyA2MDAwDQpwY2kgPSBbICcwZDowMC4wJyBd DQojIFBDSSBQYXNzdGhyb3VnaCBJbnRlbCBIRCBBdWRpbyBDb250cm9sbGVyLg0KI3BjaSA9 IFsgJzAwOjFiLjAnIF0NCiMgUENJIFBhc3N0aHJvdWdoIGFsbCB0aGUgVVNCIENvbnRyb2xs ZXJzLg0KIyBwY2kgPSBbICcwMDoxYS4wJywnMDA6MWEuMScsJzAwOjFhLjInLCcwMDoxYS43 JywnMDA6MWQuMCcsJzAwOjFkLjEnLCcwMDoxZC4yJywnMDA6MWQuNycgXQ== --------------060301030907070908060303 Content-Type: text/plain; name="xen1.txt" Content-Transfer-Encoding: base64 Content-Disposition: attachment; filename="xen1.txt" DQpbICAgIDIuNzI1MzE4XSBwY2kgMDAwMDowZDowMC4wOiByZWcgMTA6IFttZW0gMHhmODAw MDAwMC0weGY5ZmZmZmZmXQ0KWyAgICAyLjcyNTMyOF0gcGNpIDAwMDA6MGQ6MDAuMDogcmVn IDE0OiBbbWVtIDB4ZDgwMDAwMDAtMHhkZmZmZmZmZiA2NGJpdCBwcmVmXQ0KWyAgICAyLjcy NTMzOF0gcGNpIDAwMDA6MGQ6MDAuMDogcmVnIDFjOiBbbWVtIDB4ZDQwMDAwMDAtMHhkN2Zm ZmZmZiA2NGJpdCBwcmVmXQ0KWyAgICAyLjcyNTM1MV0gcGNpIDAwMDA6MGQ6MDAuMDogcmVn IDMwOiBbbWVtIDB4MDAwMDAwMDAtMHgwMDA3ZmZmZiBwcmVmXQ0KWyAgICAyLjc2MzE1MF0g cGNpIDAwMDA6MGQ6MDAuMDogQkFSIDY6IGFzc2lnbmVkIFttZW0gMHhmN2YwMDAwMC0weGY3 ZjdmZmZmIHByZWZdDQoNCjFzdCBtZW1vcnkgcmFuZ2UNCj09PT09PT09PT09PT09PT0NCg0K bWF4ID0gMHhmOWZmZmZmZiA9IDQxOTQzMDM5OTkNCm1pbiA9IDB4ZjgwMDAwMDAgPSA0MTYw NzQ5NTY4DQpkaWZmZXJlbmNlPW1heCAtIG1pbiArMSA9IDQxOTQzMDM5OTkgLSA0MTYwNzQ5 NTY4ICsxPSAzMzU1NDQzMiA9IDB4MDIwMDAwMDANCg0KbWF4ID0gMHhGOUZGRkZGRg0KbWlu ID0gMHhGODAwMDAwMA0KZGlmZiA9IDB4MDIwMDAwMDANCg0KMm5kIG1lbW9yeSByYW5nZQ0K PT09PT09PT09PT09PT09PQ0KDQptYXggPSAweGRmZmZmZmZmID0gMzc1ODA5NjM4Mw0KbWlu ID0gMHhkODAwMDAwMCA9IDM2MjM4Nzg2NTYNCmRpZmZlcmVuY2UgPSBtYXggLSBtaW4gKyAx ID0gMzc1ODA5NjM4MyAtIDM2MjM4Nzg2NTYgKyAxID0gMTM0MjE3NzI4ID0gMHgwODAwMDAw MA0KDQptYXggPSAweERGRkZGRkZGDQptaW4gPSAweEQ4MDAwMDAwDQpkaWZmPSAweDA4MDAw MDAwDQoNCjNyZCBtZW1vcnkgcmFuZ2UNCj09PT09PT09PT09PT09PT0NCg0KbWF4ID0gMHhk N2ZmZmZmZiA9IDM2MjM4Nzg2NTUNCm1pbiA9IDB4ZDQwMDAwMDAgPSAzNTU2NzY5NzkyDQpk aWZmZXJlbmNlID0gbWF4IC0gbWluICsgMSA9IDM2MjM4Nzg2NTUgLSAzNTU2NzY5NzkyICsg MSA9IDY3MTA4ODY0ID0gMHgwNDAwMDAwMA0KDQptYXggPSAweEQ3RkZGRkZGDQptaW4gPSAw eEQ0MDAwMDAwDQpkaWZmPSAweDA0MDAwMDAwDQoNCjR0aCBtZW1vcnkgcmFuZ2UNCj09PT09 PT09PT09PT09PT0NCg0KbWF4ID0gMHgwMDA3ZmZmZiA9IDUyNDI4Nw0KbWluID0gMHgwMDAw MDAwMCA9IDANCmRpZmZlcmVuY2UgPSBtYXggLSBtaW4gKzEgPSA1MjQyODcgLSAwICsgMSA9 IDUyNDI4OCA9IDB4MDAwODAwMDANCg0KbWF4ID0gMHgwMDA3RkZGRg0KbWluID0gMHgwMDAw MDAwMA0KZGlmZj0gMHgwMDA4MDAwMA0KDQoNClVVSUQgZDVlYzZiN2YtZTFkYi00YjQ2LWIw NTAtZDBiZDQ2NDAzZjU5DQoNCnZtbGludXotMy41LjQteGVuLWZyYW5rLmx5b24tc2dwDQpp bml0cmQuaW1nLTMuNS40LXhlbi1mcmFuay5seW9uLXNncA0KeGVuLmd6DQoNCnJvb3Q9L2Rl di9tYXBwZXIvc25vdy1yb290IHJvIG5vbW9kZXNldA0KDQpmbHlvbkBzbm93On4kIGxzcGNp IC1uIHwgZ3JlcCAiMGQ6MDAuMCINCjBkOjAwLjAgMDMwMDogMTBkZTowNmQ4IChyZXYgYTMp DQoNCj09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09DQoN CiMhL2Jpbi9zaA0Kc2V0IC14DQojIw0KU3RhcnRzIFNob3Jld2FsbCBGaXJld2FsbA0Kc3Vk byBzZXJ2aWNlIHNob3Jld2FsbCByZXN0YXJ0DQojIw0KTG9hZHMgcGNpLXN0dWIga2VybmVs IG1vZHVsZQ0Kc3VkbyBtb2Rwcm9iZSBwY2ktc3R1Yg0KIyMNClBhc3N0aHJvdWdoIFBhbGl0 IE5WSURJQSBHZWZvcmNlIDg0MDAgR1MgUENJZSB4MTYgVkdBIGNhcmQNCiMgZWNobyAiDQpQ YXNzdGhyb3VnaCBQYWxpdCBOVklESUEgR2Vmb3JjZSA4NDAwIEdTIFZHQSBjYXJkLiINCnN1 ZG8gY2htb2Qgbyt3IC9zeXMvYnVzL3BjaS9kcml2ZXJzL3BjaS1zdHViL25ld19pZA0Kc3Vk byBjaG1vZCBvK3cgL3N5cy9idXMvcGNpL2RldmljZXMvMDAwMDowMTowMC4wL2RyaXZlci91 bmJpbmQNCnN1ZG8gY2htb2Qgbyt3IC9zeXMvYnVzL3BjaS9kcml2ZXJzL3BjaS1zdHViL2Jp bmQNCmVjaG8gIjEwZGUgMTBjMyIgPiAvc3lzL2J1cy9wY2kvZHJpdmVycy9wY2ktc3R1Yi9u ZXdfaWQNCmVjaG8gIjAwMDA6MDE6MDAuMCIgPiAvc3lzL2J1cy9wY2kvZGV2aWNlcy8wMDAw OjAxOjAwLjAvZHJpdmVyL3VuYmluZA0KZWNobyAiMDAwMDowMTowMC4wIiA+IC9zeXMvYnVz L3BjaS9kcml2ZXJzL3BjaS1zdHViL2JpbmQNCiMjDQpQYXNzdGhyb3VnaCBJbnRlbCBIRCBB dWRpbyBDb250cm9sbGVyDQojIGVjaG8gIg0KUGFzc3Rocm91Z2ggSW50ZWwgSEQgQXVkaW8g Q29udHJvbGxlci4iDQpzdWRvIGNobW9kIG8rdyAvc3lzL2J1cy9wY2kvZHJpdmVycy9wY2kt c3R1Yi9uZXdfaWQNCnN1ZG8gY2htb2Qgbyt3IC9zeXMvYnVzL3BjaS9kZXZpY2VzLzAwMDA6 MDA6MWIuMC9kcml2ZXIvdW5iaW5kDQpzdWRvIGNobW9kIG8rdyAvc3lzL2J1cy9wY2kvZHJp dmVycy9wY2ktc3R1Yi9iaW5kDQplY2hvICI4MDg2IDNhNmUiID4gL3N5cy9idXMvcGNpL2Ry aXZlcnMvcGNpLXN0dWIvbmV3X2lkDQplY2hvICIwMDAwOjAwOjFiLjAiID4gL3N5cy9idXMv cGNpL2RldmljZXMvMDAwMDowMDoxYi4wL2RyaXZlci91bmJpbmQNCmVjaG8gIjAwMDA6MDA6 MWIuMCIgPiAvc3lzL2J1cy9wY2kvZHJpdmVycy9wY2ktc3R1Yi9iaW5kDQojIw0KV2FpdCBm b3IgMTAgc2Vjb25kcw0KI3MNCmxlZXAgMTANCiMjDQpTdGFydCBXaW5kb3dzIEhWTSBkb21V IHdpdGggVkdBIFBhc3N0aHJvdWdoDQojDQojc3VkbyB4bCBjcmVhdGUgL2V0Yy94ZW4vV2lu ZG93c1hQSG9tZUVkaXRpb25TUDMNCnN1ZG8geGwgY3JlYXRlIC9ldGMveGVuL1dpbmRvd3M4 Q29uc3VtZXJQcmV2aWV3NjRiaXRFbmdsaXNo --------------060301030907070908060303 Content-Type: text/x-log; name="xend.log" Content-Transfer-Encoding: quoted-printable Content-Disposition: attachment; filename="xend.log" [2012-09-19 20:48:44 1730] INFO (SrvDaemon:332) Xend Daemon started [2012-09-19 20:48:44 1730] INFO (SrvDaemon:336) Xend changeset: Mon Sep 1= 7 21:12:21 2012 +0100 25925:d1c3375c3f11. [2012-09-19 20:48:44 1730] DEBUG (tcp:96) Listening on :8002 [2012-09-19 20:48:47 1730] DEBUG (XendNode:332) pscsi record count: 9 [2012-09-19 20:48:47 1730] DEBUG (XendCPUPool:747) recreate_active_pools [2012-09-19 20:48:47 1730] DEBUG (XendDomainInfo:151) XendDomainInfo.recr= eate({'max_vcpu_id': 23, 'cpu_time': 20156983226L, 'ssidref': 0, 'hvm': 0= , 'shutdown_reason': 255, 'dying': 0, 'online_vcpus': 24, 'domid': 0, 'pa= used': 0, 'crashed': 0, 'running': 1, 'maxmem_kb': 17179869180L, 'shutdow= n': 0, 'mem_kb': 24692524L, 'blocked': 0, 'handle': [0, 0, 0, 0, 0, 0, 0,= 0, 0, 0, 0, 0, 0, 0, 0, 0], 'cpupool': 0, 'name': 'Domain-0'}) [2012-09-19 20:48:47 1730] INFO (XendDomainInfo:169) Recreating domain 0,= UUID 00000000-0000-0000-0000-000000000000. at /local/domain/0 [2012-09-19 20:48:47 1730] DEBUG (XendDomainInfo:3426) Storing VM details= : {'on_xend_stop': 'ignore', 'pool_name': 'Pool-0', 'shadow_memory': '0',= 'uuid': '00000000-0000-0000-0000-000000000000', 'on_reboot': 'restart', = 'image': "(linux (kernel '') (superpages 0) (nomigrate 0) (tsc_mode 0))",= 'on_poweroff': 'destroy', 'bootloader_args': '', 'on_xend_start': 'ignor= e', 'on_crash': 'restart', 'xend/restart_count': '0', 'vcpus': '24', 'vcp= u_avail': '16777215', 'bootloader': '', 'name': 'Domain-0'} [2012-09-19 20:48:47 1730] DEBUG (XendDomainInfo:1795) Storing domain det= ails: {'cpu/3/availability': 'online', 'cpu/6/availability': 'online', 'v= m': '/vm/00000000-0000-0000-0000-000000000000', 'cpu/22/availability': 'o= nline', 'control/platform-feature-multiprocessor-suspend': '1', 'cpu/17/a= vailability': 'online', 'cpu/14/availability': 'online', 'console/limit':= '1048576', 'cpu/2/availability': 'online', 'cpu/11/availability': 'onlin= e', 'cpu/1/availability': 'online', 'cpu/7/availability': 'online', 'memo= ry/target': '24692524', 'cpu/20/availability': 'online', 'control/platfor= m-feature-xs_reset_watches': '1', 'cpu/15/availability': 'online', 'descr= iption': '', 'cpu/13/availability': 'online', 'cpu/8/availability': 'onli= ne', 'cpu/9/availability': 'online', 'cpu/5/availability': 'online', 'cpu= /23/availability': 'online', 'cpu/0/availability': 'online', 'cpu/18/avai= lability': 'online', 'console/type': 'xenconsoled', 'cpu/12/availability'= : 'online', 'cpu/19/availability': 'online', 'name': 'Domain-0', 'domid':= '0', 'cpu/4/availability': 'online', 'cpu/16/availability': 'online', 'c= pu/21/availability': 'online', 'cpu/10/availability': 'online'} [2012-09-19 20:48:47 1730] DEBUG (XendDomain:476) Adding Domain: 0 [2012-09-19 20:48:47 1730] DEBUG (XendDomain:410) number of vcpus to use = is 0 [2012-09-19 20:48:47 1730] DEBUG (XendDomainInfo:1882) XendDomainInfo.han= dleShutdownWatch [2012-09-19 20:48:47 1730] WARNING (XendAPI:708) API call: VBD.set_device= not found [2012-09-19 20:48:47 1730] WARNING (XendAPI:708) API call: VBD.set_type n= ot found [2012-09-19 20:48:47 1730] WARNING (XendAPI:708) API call: session.get_al= l_records not found [2012-09-19 20:48:47 1730] WARNING (XendAPI:708) API call: event.get_reco= rd not found [2012-09-19 20:48:47 1730] WARNING (XendAPI:708) API call: event.get_all = not found [2012-09-19 20:48:47 1730] WARNING (XendAPI:708) API call: VIF.set_device= not found [2012-09-19 20:48:47 1730] WARNING (XendAPI:708) API call: VIF.set_MAC no= t found [2012-09-19 20:48:47 1730] WARNING (XendAPI:708) API call: VIF.set_MTU no= t found [2012-09-19 20:48:47 1730] WARNING (XendAPI:708) API call: debug.get_all = not found [2012-09-19 20:48:47 1730] INFO (XMLRPCServer:161) Opening Unix domain so= cket XML-RPC server on /var/run/xend/xen-api.sock; authentication has bee= n disabled for this server. [2012-09-19 20:48:47 1730] INFO (XMLRPCServer:161) Opening Unix domain so= cket XML-RPC server on /var/run/xend/xmlrpc.sock. [2012-09-19 21:00:22 1730] DEBUG (SrvServer:77) SrvServer.cleanup() [2012-09-19 21:00:22 1730] DEBUG (XMLRPCServer:251) XMLRPCServer.cleanup(= ) [2012-09-19 21:00:22 1730] DEBUG (XMLRPCServer:251) XMLRPCServer.cleanup(= ) [2012-09-19 21:00:22 1730] DEBUG (XendDomain:644) cleanup_domains [2012-09-19 21:00:22 1729] INFO (SrvDaemon:220) Xend exited with status 0= =2E [2012-09-19 21:03:31 1691] INFO (SrvDaemon:332) Xend Daemon started [2012-09-19 21:03:31 1691] INFO (SrvDaemon:336) Xend changeset: Mon Sep 1= 7 21:12:21 2012 +0100 25925:d1c3375c3f11. [2012-09-19 21:03:31 1691] DEBUG (tcp:96) Listening on :8002 [2012-09-19 21:03:33 1691] DEBUG (XendNode:332) pscsi record count: 9 [2012-09-19 21:03:33 1691] DEBUG (XendCPUPool:747) recreate_active_pools [2012-09-19 21:03:33 1691] DEBUG (XendDomainInfo:151) XendDomainInfo.recr= eate({'max_vcpu_id': 23, 'cpu_time': 17093476257L, 'ssidref': 0, 'hvm': 0= , 'shutdown_reason': 255, 'dying': 0, 'online_vcpus': 24, 'domid': 0, 'pa= used': 0, 'crashed': 0, 'running': 1, 'maxmem_kb': 17179869180L, 'shutdow= n': 0, 'mem_kb': 24692524L, 'blocked': 0, 'handle': [0, 0, 0, 0, 0, 0, 0,= 0, 0, 0, 0, 0, 0, 0, 0, 0], 'cpupool': 0, 'name': 'Domain-0'}) [2012-09-19 21:03:33 1691] INFO (XendDomainInfo:169) Recreating domain 0,= UUID 00000000-0000-0000-0000-000000000000. at /local/domain/0 [2012-09-19 21:03:33 1691] DEBUG (XendDomainInfo:3426) Storing VM details= : {'on_xend_stop': 'ignore', 'pool_name': 'Pool-0', 'shadow_memory': '0',= 'uuid': '00000000-0000-0000-0000-000000000000', 'on_reboot': 'restart', = 'image': "(linux (kernel '') (superpages 0) (nomigrate 0) (tsc_mode 0))",= 'on_poweroff': 'destroy', 'bootloader_args': '', 'on_xend_start': 'ignor= e', 'on_crash': 'restart', 'xend/restart_count': '0', 'vcpus': '24', 'vcp= u_avail': '16777215', 'bootloader': '', 'name': 'Domain-0'} [2012-09-19 21:03:33 1691] DEBUG (XendDomainInfo:1795) Storing domain det= ails: {'cpu/3/availability': 'online', 'cpu/6/availability': 'online', 'v= m': '/vm/00000000-0000-0000-0000-000000000000', 'cpu/22/availability': 'o= nline', 'control/platform-feature-multiprocessor-suspend': '1', 'cpu/17/a= vailability': 'online', 'cpu/14/availability': 'online', 'console/limit':= '1048576', 'cpu/2/availability': 'online', 'cpu/11/availability': 'onlin= e', 'cpu/1/availability': 'online', 'cpu/7/availability': 'online', 'memo= ry/target': '24692524', 'cpu/20/availability': 'online', 'control/platfor= m-feature-xs_reset_watches': '1', 'cpu/15/availability': 'online', 'descr= iption': '', 'cpu/13/availability': 'online', 'cpu/8/availability': 'onli= ne', 'cpu/9/availability': 'online', 'cpu/5/availability': 'online', 'cpu= /23/availability': 'online', 'cpu/0/availability': 'online', 'cpu/18/avai= lability': 'online', 'console/type': 'xenconsoled', 'cpu/12/availability'= : 'online', 'cpu/19/availability': 'online', 'name': 'Domain-0', 'domid':= '0', 'cpu/4/availability': 'online', 'cpu/16/availability': 'online', 'c= pu/21/availability': 'online', 'cpu/10/availability': 'online'} [2012-09-19 21:03:33 1691] DEBUG (XendDomain:476) Adding Domain: 0 [2012-09-19 21:03:33 1691] DEBUG (XendDomain:410) number of vcpus to use = is 0 [2012-09-19 21:03:33 1691] DEBUG (XendDomainInfo:1882) XendDomainInfo.han= dleShutdownWatch [2012-09-19 21:03:33 1691] WARNING (XendAPI:708) API call: VBD.set_device= not found [2012-09-19 21:03:33 1691] WARNING (XendAPI:708) API call: VBD.set_type n= ot found [2012-09-19 21:03:33 1691] WARNING (XendAPI:708) API call: session.get_al= l_records not found [2012-09-19 21:03:33 1691] WARNING (XendAPI:708) API call: event.get_reco= rd not found [2012-09-19 21:03:33 1691] WARNING (XendAPI:708) API call: event.get_all = not found [2012-09-19 21:03:33 1691] WARNING (XendAPI:708) API call: VIF.set_device= not found [2012-09-19 21:03:33 1691] WARNING (XendAPI:708) API call: VIF.set_MAC no= t found [2012-09-19 21:03:33 1691] WARNING (XendAPI:708) API call: VIF.set_MTU no= t found [2012-09-19 21:03:34 1691] WARNING (XendAPI:708) API call: debug.get_all = not found [2012-09-19 21:03:34 1691] INFO (XMLRPCServer:161) Opening Unix domain so= cket XML-RPC server on /var/run/xend/xen-api.sock; authentication has bee= n disabled for this server. [2012-09-19 21:03:34 1691] INFO (XMLRPCServer:161) Opening Unix domain so= cket XML-RPC server on /var/run/xend/xmlrpc.sock. [2012-09-19 22:18:22 1691] DEBUG (SrvServer:77) SrvServer.cleanup() [2012-09-19 22:18:22 1691] DEBUG (XMLRPCServer:251) XMLRPCServer.cleanup(= ) [2012-09-19 22:18:22 1691] DEBUG (XMLRPCServer:251) XMLRPCServer.cleanup(= ) [2012-09-19 22:18:22 1691] DEBUG (XendDomain:644) cleanup_domains [2012-09-19 22:18:22 1689] INFO (SrvDaemon:220) Xend exited with status 0= =2E [2012-09-19 22:37:19 6950] INFO (SrvDaemon:332) Xend Daemon started [2012-09-19 22:37:19 6950] INFO (SrvDaemon:336) Xend changeset: Mon Sep 1= 7 21:12:21 2012 +0100 25925:d1c3375c3f11. [2012-09-19 22:37:19 6950] DEBUG (tcp:96) Listening on :8002 [2012-09-19 22:37:22 6950] DEBUG (XendNode:332) pscsi record count: 12 [2012-09-19 22:37:22 6950] DEBUG (XendCPUPool:747) recreate_active_pools [2012-09-19 22:37:22 6950] DEBUG (XendDomainInfo:151) XendDomainInfo.recr= eate({'max_vcpu_id': 23, 'cpu_time': 3726170848291L, 'ssidref': 0, 'hvm':= 0, 'shutdown_reason': 255, 'dying': 0, 'online_vcpus': 24, 'domid': 0, '= paused': 0, 'crashed': 0, 'running': 1, 'maxmem_kb': 17179869180L, 'shutd= own': 0, 'mem_kb': 12293932L, 'blocked': 0, 'handle': [0, 0, 0, 0, 0, 0, = 0, 0, 0, 0, 0, 0, 0, 0, 0, 0], 'cpupool': 0, 'name': 'Domain-0'}) [2012-09-19 22:37:22 6950] INFO (XendDomainInfo:169) Recreating domain 0,= UUID 00000000-0000-0000-0000-000000000000. at /local/domain/0 [2012-09-19 22:37:22 6950] DEBUG (XendDomain:476) Adding Domain: 0 [2012-09-19 22:37:22 6950] DEBUG (XendDomainInfo:1882) XendDomainInfo.han= dleShutdownWatch [2012-09-19 22:37:22 6950] DEBUG (XendDomain:410) number of vcpus to use = is 0 [2012-09-19 22:37:22 6950] WARNING (XendAPI:708) API call: VBD.set_device= not found [2012-09-19 22:37:22 6950] WARNING (XendAPI:708) API call: VBD.set_type n= ot found [2012-09-19 22:37:22 6950] WARNING (XendAPI:708) API call: session.get_al= l_records not found [2012-09-19 22:37:22 6950] WARNING (XendAPI:708) API call: event.get_reco= rd not found [2012-09-19 22:37:22 6950] WARNING (XendAPI:708) API call: event.get_all = not found [2012-09-19 22:37:22 6950] WARNING (XendAPI:708) API call: VIF.set_device= not found [2012-09-19 22:37:22 6950] WARNING (XendAPI:708) API call: VIF.set_MAC no= t found [2012-09-19 22:37:22 6950] WARNING (XendAPI:708) API call: VIF.set_MTU no= t found [2012-09-19 22:37:22 6950] WARNING (XendAPI:708) API call: debug.get_all = not found [2012-09-19 22:37:22 6950] INFO (XMLRPCServer:161) Opening Unix domain so= cket XML-RPC server on /var/run/xend/xen-api.sock; authentication has bee= n disabled for this server. [2012-09-19 22:37:22 6950] INFO (XMLRPCServer:161) Opening Unix domain so= cket XML-RPC server on /var/run/xend/xmlrpc.sock. [2012-09-19 22:38:16 6950] DEBUG (SrvServer:77) SrvServer.cleanup() [2012-09-19 22:38:16 6950] DEBUG (XMLRPCServer:251) XMLRPCServer.cleanup(= ) [2012-09-19 22:38:16 6950] DEBUG (XMLRPCServer:251) XMLRPCServer.cleanup(= ) [2012-09-19 22:38:16 6950] DEBUG (XendDomain:644) cleanup_domains [2012-09-19 22:38:16 6949] INFO (SrvDaemon:220) Xend exited with status 0= =2E --------------060301030907070908060303 Content-Type: text/x-log; name="xend-debug.log" Content-Transfer-Encoding: 7bit Content-Disposition: attachment; filename="xend-debug.log" Xend started at Wed Sep 19 20:48:44 2012. cat: /sys/bus/scsi/devices/target1:0:0/vendor: No such file or directory cat: /sys/bus/scsi/devices/target1:0:0/model: No such file or directory cat: /sys/bus/scsi/devices/target1:0:0/type: No such file or directory cat: /sys/bus/scsi/devices/target1:0:0/rev: No such file or directory cat: /sys/bus/scsi/devices/target1:0:0/scsi_level: No such file or directory cat: /sys/bus/scsi/devices/target2:0:0/vendor: No such file or directory cat: /sys/bus/scsi/devices/target2:0:0/model: No such file or directory cat: /sys/bus/scsi/devices/target2:0:0/type: No such file or directory cat: /sys/bus/scsi/devices/target2:0:0/rev: No such file or directory cat: /sys/bus/scsi/devices/target2:0:0/scsi_level: No such file or directory cat: /sys/bus/scsi/devices/target2:3:0/vendor: No such file or directory cat: /sys/bus/scsi/devices/target2:3:0/model: No such file or directory cat: /sys/bus/scsi/devices/target2:3:0/type: No such file or directory cat: /sys/bus/scsi/devices/target2:3:0/rev: No such file or directory cat: /sys/bus/scsi/devices/target2:3:0/scsi_level: No such file or directory cat: /sys/bus/scsi/devices/host0/vendor: No such file or directory cat: /sys/bus/scsi/devices/host0/model: No such file or directory cat: /sys/bus/scsi/devices/host0/type: No such file or directory cat: /sys/bus/scsi/devices/host0/rev: No such file or directory cat: /sys/bus/scsi/devices/host0/scsi_level: No such file or directory cat: /sys/bus/scsi/devices/host1/vendor: No such file or directory cat: /sys/bus/scsi/devices/host1/model: No such file or directory cat: /sys/bus/scsi/devices/host1/type: No such file or directory cat: /sys/bus/scsi/devices/host1/rev: No such file or directory cat: /sys/bus/scsi/devices/host1/scsi_level: No such file or directory cat: /sys/bus/scsi/devices/host2/vendor: No such file or directory cat: /sys/bus/scsi/devices/host2/model: No such file or directory cat: /sys/bus/scsi/devices/host2/type: No such file or directory cat: /sys/bus/scsi/devices/host2/rev: No such file or directory cat: /sys/bus/scsi/devices/host2/scsi_level: No such file or directory Xend started at Wed Sep 19 21:03:31 2012. cat: /sys/bus/scsi/devices/target1:0:0/vendor: No such file or directory cat: /sys/bus/scsi/devices/target1:0:0/model: No such file or directory cat: /sys/bus/scsi/devices/target1:0:0/type: No such file or directory cat: /sys/bus/scsi/devices/target1:0:0/rev: No such file or directory cat: /sys/bus/scsi/devices/target1:0:0/scsi_level: No such file or directory cat: /sys/bus/scsi/devices/target2:0:0/vendor: No such file or directory cat: /sys/bus/scsi/devices/target2:0:0/model: No such file or directory cat: /sys/bus/scsi/devices/target2:0:0/type: No such file or directory cat: /sys/bus/scsi/devices/target2:0:0/rev: No such file or directory cat: /sys/bus/scsi/devices/target2:0:0/scsi_level: No such file or directory cat: /sys/bus/scsi/devices/target2:3:0/vendor: No such file or directory cat: /sys/bus/scsi/devices/target2:3:0/model: No such file or directory cat: /sys/bus/scsi/devices/target2:3:0/type: No such file or directory cat: /sys/bus/scsi/devices/target2:3:0/rev: No such file or directory cat: /sys/bus/scsi/devices/target2:3:0/scsi_level: No such file or directory cat: /sys/bus/scsi/devices/host0/vendor: No such file or directory cat: /sys/bus/scsi/devices/host0/model: No such file or directory cat: /sys/bus/scsi/devices/host0/type: No such file or directory cat: /sys/bus/scsi/devices/host0/rev: No such file or directory cat: /sys/bus/scsi/devices/host0/scsi_level: No such file or directory cat: /sys/bus/scsi/devices/host1/vendor: No such file or directory cat: /sys/bus/scsi/devices/host1/model: No such file or directory cat: /sys/bus/scsi/devices/host1/type: No such file or directory cat: /sys/bus/scsi/devices/host1/rev: No such file or directory cat: /sys/bus/scsi/devices/host1/scsi_level: No such file or directory cat: /sys/bus/scsi/devices/host2/vendor: No such file or directory cat: /sys/bus/scsi/devices/host2/model: No such file or directory cat: /sys/bus/scsi/devices/host2/type: No such file or directory cat: /sys/bus/scsi/devices/host2/rev: No such file or directory cat: /sys/bus/scsi/devices/host2/scsi_level: No such file or directory Xend started at Wed Sep 19 22:37:19 2012. cat: /sys/bus/scsi/devices/target1:0:0/vendor: No such file or directory cat: /sys/bus/scsi/devices/target1:0:0/model: No such file or directory cat: /sys/bus/scsi/devices/target1:0:0/type: No such file or directory cat: /sys/bus/scsi/devices/target1:0:0/rev: No such file or directory cat: /sys/bus/scsi/devices/target1:0:0/scsi_level: No such file or directory cat: /sys/bus/scsi/devices/target2:0:0/vendor: No such file or directory cat: /sys/bus/scsi/devices/target2:0:0/model: No such file or directory cat: /sys/bus/scsi/devices/target2:0:0/type: No such file or directory cat: /sys/bus/scsi/devices/target2:0:0/rev: No such file or directory cat: /sys/bus/scsi/devices/target2:0:0/scsi_level: No such file or directory cat: /sys/bus/scsi/devices/target2:3:0/vendor: No such file or directory cat: /sys/bus/scsi/devices/target2:3:0/model: No such file or directory cat: /sys/bus/scsi/devices/target2:3:0/type: No such file or directory cat: /sys/bus/scsi/devices/target2:3:0/rev: No such file or directory cat: /sys/bus/scsi/devices/target2:3:0/scsi_level: No such file or directory cat: /sys/bus/scsi/devices/target3:0:0/vendor: No such file or directory cat: /sys/bus/scsi/devices/target3:0:0/model: No such file or directory cat: /sys/bus/scsi/devices/target3:0:0/type: No such file or directory cat: /sys/bus/scsi/devices/target3:0:0/rev: No such file or directory cat: /sys/bus/scsi/devices/target3:0:0/scsi_level: No such file or directory cat: /sys/bus/scsi/devices/host0/vendor: No such file or directory cat: /sys/bus/scsi/devices/host0/model: No such file or directory cat: /sys/bus/scsi/devices/host0/type: No such file or directory cat: /sys/bus/scsi/devices/host0/rev: No such file or directory cat: /sys/bus/scsi/devices/host0/scsi_level: No such file or directory cat: /sys/bus/scsi/devices/host1/vendor: No such file or directory cat: /sys/bus/scsi/devices/host1/model: No such file or directory cat: /sys/bus/scsi/devices/host1/type: No such file or directory cat: /sys/bus/scsi/devices/host1/rev: No such file or directory cat: /sys/bus/scsi/devices/host1/scsi_level: No such file or directory cat: /sys/bus/scsi/devices/host2/vendor: No such file or directory cat: /sys/bus/scsi/devices/host2/model: No such file or directory cat: /sys/bus/scsi/devices/host2/type: No such file or directory cat: /sys/bus/scsi/devices/host2/rev: No such file or directory cat: /sys/bus/scsi/devices/host2/scsi_level: No such file or directory cat: /sys/bus/scsi/devices/host3/vendor: No such file or directory cat: /sys/bus/scsi/devices/host3/model: No such file or directory cat: /sys/bus/scsi/devices/host3/type: No such file or directory cat: /sys/bus/scsi/devices/host3/rev: No such file or directory cat: /sys/bus/scsi/devices/host3/scsi_level: No such file or directory --------------060301030907070908060303 Content-Type: text/x-log; name="xen-hotplug.log" Content-Transfer-Encoding: 7bit Content-Disposition: attachment; filename="xen-hotplug.log" RTNETLINK answers: Operation not supported RTNETLINK answers: Operation not supported RTNETLINK answers: Operation not supported RTNETLINK answers: Operation not supported RTNETLINK answers: Operation not supported RTNETLINK answers: Operation not supported RTNETLINK answers: Operation not supported RTNETLINK answers: Operation not supported RTNETLINK answers: Operation not supported RTNETLINK answers: Operation not supported RTNETLINK answers: Operation not supported RTNETLINK answers: Operation not supported RTNETLINK answers: Operation not supported RTNETLINK answers: Operation not supported RTNETLINK answers: Operation not supported RTNETLINK answers: Operation not supported RTNETLINK answers: Operation not supported RTNETLINK answers: Operation not supported RTNETLINK answers: Operation not supported RTNETLINK answers: Operation not supported --------------060301030907070908060303 Content-Type: text/x-log; name="xl-Windows8.log" Content-Transfer-Encoding: 7bit Content-Disposition: attachment; filename="xl-Windows8.log" Waiting for domain Windows8 (domid 9) to die [pid 7447] Domain 9 has shut down, reason code 1 0x1 Action for shutdown reason code 1 is restart Domain 9 needs to be cleaned up: destroying the domain libxl: error: libxl_pci.c:1001:libxl__device_pci_reset: The kernel doesn't support reset from sysfs for PCI device 0000:0d:00.0 libxl: error: libxl_pci.c:1265:do_pci_remove: xc_deassign_device failed Done. Rebooting now xc: info: VIRTUAL MEMORY ARRANGEMENT: Loader: 0000000000100000->00000000001ad64c TOTAL: 0000000000000000->00000000ff800000 ENTRY ADDRESS: 0000000000100000 xc: info: PHYSICAL MEMORY ALLOCATION: 4KB PAGES: 0x0000000000000200 2MB PAGES: 0x00000000000003fb 1GB PAGES: 0x0000000000000002 libxl: error: libxl_pci.c:1055:libxl__device_pci_add: PCI device 0:d:0.0 is not assignable Waiting for domain Windows8 (domid 10) to die [pid 7447] Domain 10 has shut down, reason code 1 0x1 Action for shutdown reason code 1 is restart Domain 10 needs to be cleaned up: destroying the domain libxl: error: libxl_pci.c:1001:libxl__device_pci_reset: The kernel doesn't support reset from sysfs for PCI device 0000:0d:00.0 libxl: error: libxl_pci.c:1265:do_pci_remove: xc_deassign_device failed Done. Rebooting now xc: info: VIRTUAL MEMORY ARRANGEMENT: Loader: 0000000000100000->00000000001ad64c TOTAL: 0000000000000000->00000000ff800000 ENTRY ADDRESS: 0000000000100000 xc: info: PHYSICAL MEMORY ALLOCATION: 4KB PAGES: 0x0000000000000200 2MB PAGES: 0x00000000000003fb 1GB PAGES: 0x0000000000000002 libxl: error: libxl_pci.c:1055:libxl__device_pci_add: PCI device 0:d:0.0 is not assignable Waiting for domain Windows8 (domid 11) to die [pid 7447] Domain 11 has shut down, reason code 1 0x1 Action for shutdown reason code 1 is restart Domain 11 needs to be cleaned up: destroying the domain libxl: error: libxl_pci.c:1001:libxl__device_pci_reset: The kernel doesn't support reset from sysfs for PCI device 0000:0d:00.0 libxl: error: libxl_pci.c:1265:do_pci_remove: xc_deassign_device failed Done. Rebooting now xc: info: VIRTUAL MEMORY ARRANGEMENT: Loader: 0000000000100000->00000000001ad64c TOTAL: 0000000000000000->00000000ff800000 ENTRY ADDRESS: 0000000000100000 xc: info: PHYSICAL MEMORY ALLOCATION: 4KB PAGES: 0x0000000000000200 2MB PAGES: 0x00000000000003fb 1GB PAGES: 0x0000000000000002 libxl: error: libxl_pci.c:1055:libxl__device_pci_add: PCI device 0:d:0.0 is not assignable Waiting for domain Windows8 (domid 12) to die [pid 7447] Domain 12 has shut down, reason code 1 0x1 Action for shutdown reason code 1 is restart Domain 12 needs to be cleaned up: destroying the domain libxl: error: libxl_pci.c:1001:libxl__device_pci_reset: The kernel doesn't support reset from sysfs for PCI device 0000:0d:00.0 libxl: error: libxl_pci.c:1265:do_pci_remove: xc_deassign_device failed Done. Rebooting now xc: info: VIRTUAL MEMORY ARRANGEMENT: Loader: 0000000000100000->00000000001ad64c TOTAL: 0000000000000000->00000000ff800000 ENTRY ADDRESS: 0000000000100000 xc: info: PHYSICAL MEMORY ALLOCATION: 4KB PAGES: 0x0000000000000200 2MB PAGES: 0x00000000000003fb 1GB PAGES: 0x0000000000000002 libxl: error: libxl_pci.c:1055:libxl__device_pci_add: PCI device 0:d:0.0 is not assignable Waiting for domain Windows8 (domid 13) to die [pid 7447] Domain 13 has shut down, reason code 1 0x1 Action for shutdown reason code 1 is restart Domain 13 needs to be cleaned up: destroying the domain libxl: error: libxl_pci.c:1001:libxl__device_pci_reset: The kernel doesn't support reset from sysfs for PCI device 0000:0d:00.0 libxl: error: libxl_pci.c:1265:do_pci_remove: xc_deassign_device failed Done. Rebooting now xc: info: VIRTUAL MEMORY ARRANGEMENT: Loader: 0000000000100000->00000000001ad64c TOTAL: 0000000000000000->00000000ff800000 ENTRY ADDRESS: 0000000000100000 xc: info: PHYSICAL MEMORY ALLOCATION: 4KB PAGES: 0x0000000000000200 2MB PAGES: 0x00000000000003fb 1GB PAGES: 0x0000000000000002 libxl: error: libxl_pci.c:1055:libxl__device_pci_add: PCI device 0:d:0.0 is not assignable Waiting for domain Windows8 (domid 14) to die [pid 7447] Domain 14 has shut down, reason code 1 0x1 Action for shutdown reason code 1 is restart Domain 14 needs to be cleaned up: destroying the domain libxl: error: libxl_pci.c:1001:libxl__device_pci_reset: The kernel doesn't support reset from sysfs for PCI device 0000:0d:00.0 libxl: error: libxl_pci.c:1265:do_pci_remove: xc_deassign_device failed Done. Rebooting now xc: info: VIRTUAL MEMORY ARRANGEMENT: Loader: 0000000000100000->00000000001ad64c TOTAL: 0000000000000000->00000000ff800000 ENTRY ADDRESS: 0000000000100000 xc: info: PHYSICAL MEMORY ALLOCATION: 4KB PAGES: 0x0000000000000200 2MB PAGES: 0x00000000000003fb 1GB PAGES: 0x0000000000000002 libxl: error: libxl_pci.c:1055:libxl__device_pci_add: PCI device 0:d:0.0 is not assignable Waiting for domain Windows8 (domid 15) to die [pid 7447] Domain 15 has shut down, reason code 1 0x1 Action for shutdown reason code 1 is restart Domain 15 needs to be cleaned up: destroying the domain libxl: error: libxl_pci.c:1001:libxl__device_pci_reset: The kernel doesn't support reset from sysfs for PCI device 0000:0d:00.0 libxl: error: libxl_pci.c:1265:do_pci_remove: xc_deassign_device failed Done. Rebooting now xc: info: VIRTUAL MEMORY ARRANGEMENT: Loader: 0000000000100000->00000000001ad64c TOTAL: 0000000000000000->00000000ff800000 ENTRY ADDRESS: 0000000000100000 xc: info: PHYSICAL MEMORY ALLOCATION: 4KB PAGES: 0x0000000000000200 2MB PAGES: 0x00000000000003fb 1GB PAGES: 0x0000000000000002 libxl: error: libxl_pci.c:1055:libxl__device_pci_add: PCI device 0:d:0.0 is not assignable Waiting for domain Windows8 (domid 16) to die [pid 7447] Domain 16 has shut down, reason code 1 0x1 Action for shutdown reason code 1 is restart Domain 16 needs to be cleaned up: destroying the domain libxl: error: libxl_pci.c:1001:libxl__device_pci_reset: The kernel doesn't support reset from sysfs for PCI device 0000:0d:00.0 libxl: error: libxl_pci.c:1265:do_pci_remove: xc_deassign_device failed Done. Rebooting now xc: info: VIRTUAL MEMORY ARRANGEMENT: Loader: 0000000000100000->00000000001ad64c TOTAL: 0000000000000000->00000000ff800000 ENTRY ADDRESS: 0000000000100000 xc: info: PHYSICAL MEMORY ALLOCATION: 4KB PAGES: 0x0000000000000200 2MB PAGES: 0x00000000000003fb 1GB PAGES: 0x0000000000000002 libxl: error: libxl_pci.c:1055:libxl__device_pci_add: PCI device 0:d:0.0 is not assignable Waiting for domain Windows8 (domid 17) to die [pid 7447] Domain 17 has shut down, reason code 1 0x1 Action for shutdown reason code 1 is restart Domain 17 needs to be cleaned up: destroying the domain libxl: error: libxl_pci.c:1001:libxl__device_pci_reset: The kernel doesn't support reset from sysfs for PCI device 0000:0d:00.0 libxl: error: libxl_pci.c:1265:do_pci_remove: xc_deassign_device failed Done. Rebooting now xc: info: VIRTUAL MEMORY ARRANGEMENT: Loader: 0000000000100000->00000000001ad64c TOTAL: 0000000000000000->00000000ff800000 ENTRY ADDRESS: 0000000000100000 xc: info: PHYSICAL MEMORY ALLOCATION: 4KB PAGES: 0x0000000000000200 2MB PAGES: 0x00000000000003fb 1GB PAGES: 0x0000000000000002 libxl: error: libxl_pci.c:1055:libxl__device_pci_add: PCI device 0:d:0.0 is not assignable Waiting for domain Windows8 (domid 18) to die [pid 7447] Domain 18 has shut down, reason code 1 0x1 Action for shutdown reason code 1 is restart Domain 18 needs to be cleaned up: destroying the domain libxl: error: libxl_pci.c:1001:libxl__device_pci_reset: The kernel doesn't support reset from sysfs for PCI device 0000:0d:00.0 libxl: error: libxl_pci.c:1265:do_pci_remove: xc_deassign_device failed Done. Rebooting now xc: info: VIRTUAL MEMORY ARRANGEMENT: Loader: 0000000000100000->00000000001ad64c TOTAL: 0000000000000000->00000000ff800000 ENTRY ADDRESS: 0000000000100000 xc: info: PHYSICAL MEMORY ALLOCATION: 4KB PAGES: 0x0000000000000200 2MB PAGES: 0x00000000000003fb 1GB PAGES: 0x0000000000000002 libxl: error: libxl_pci.c:1055:libxl__device_pci_add: PCI device 0:d:0.0 is not assignable Waiting for domain Windows8 (domid 19) to die [pid 7447] Domain 19 has shut down, reason code 1 0x1 Action for shutdown reason code 1 is restart Domain 19 needs to be cleaned up: destroying the domain libxl: error: libxl_pci.c:1001:libxl__device_pci_reset: The kernel doesn't support reset from sysfs for PCI device 0000:0d:00.0 libxl: error: libxl_pci.c:1265:do_pci_remove: xc_deassign_device failed Done. Rebooting now xc: info: VIRTUAL MEMORY ARRANGEMENT: Loader: 0000000000100000->00000000001ad64c TOTAL: 0000000000000000->00000000ff800000 ENTRY ADDRESS: 0000000000100000 xc: info: PHYSICAL MEMORY ALLOCATION: 4KB PAGES: 0x0000000000000200 2MB PAGES: 0x00000000000003fb 1GB PAGES: 0x0000000000000002 libxl: error: libxl_pci.c:1055:libxl__device_pci_add: PCI device 0:d:0.0 is not assignable Waiting for domain Windows8 (domid 20) to die [pid 7447] Domain 20 has shut down, reason code 1 0x1 Action for shutdown reason code 1 is restart Domain 20 needs to be cleaned up: destroying the domain libxl: error: libxl_pci.c:1001:libxl__device_pci_reset: The kernel doesn't support reset from sysfs for PCI device 0000:0d:00.0 libxl: error: libxl_pci.c:1265:do_pci_remove: xc_deassign_device failed Done. Rebooting now xc: info: VIRTUAL MEMORY ARRANGEMENT: Loader: 0000000000100000->00000000001ad64c TOTAL: 0000000000000000->00000000ff800000 ENTRY ADDRESS: 0000000000100000 xc: info: PHYSICAL MEMORY ALLOCATION: 4KB PAGES: 0x0000000000000200 2MB PAGES: 0x00000000000003fb 1GB PAGES: 0x0000000000000002 libxl: error: libxl_pci.c:1055:libxl__device_pci_add: PCI device 0:d:0.0 is not assignable Waiting for domain Windows8 (domid 21) to die [pid 7447] --------------060301030907070908060303 Content-Type: text/plain; name="xl-Windows8.log.1" Content-Transfer-Encoding: 7bit Content-Disposition: attachment; filename="xl-Windows8.log.1" Waiting for domain Windows8 (domid 2) to die [pid 5545] Domain 2 has shut down, reason code 1 0x1 Action for shutdown reason code 1 is restart Domain 2 needs to be cleaned up: destroying the domain libxl: error: libxl_pci.c:1001:libxl__device_pci_reset: The kernel doesn't support reset from sysfs for PCI device 0000:0d:00.0 libxl: error: libxl_pci.c:1265:do_pci_remove: xc_deassign_device failed Done. Rebooting now xc: info: VIRTUAL MEMORY ARRANGEMENT: Loader: 0000000000100000->00000000001ad64c TOTAL: 0000000000000000->00000000ff800000 ENTRY ADDRESS: 0000000000100000 xc: info: PHYSICAL MEMORY ALLOCATION: 4KB PAGES: 0x0000000000000200 2MB PAGES: 0x00000000000003fb 1GB PAGES: 0x0000000000000002 libxl: error: libxl_pci.c:1055:libxl__device_pci_add: PCI device 0:d:0.0 is not assignable Waiting for domain Windows8 (domid 3) to die [pid 5545] Domain 3 has shut down, reason code 1 0x1 Action for shutdown reason code 1 is restart Domain 3 needs to be cleaned up: destroying the domain libxl: error: libxl_pci.c:1001:libxl__device_pci_reset: The kernel doesn't support reset from sysfs for PCI device 0000:0d:00.0 libxl: error: libxl_pci.c:1265:do_pci_remove: xc_deassign_device failed Done. Rebooting now xc: info: VIRTUAL MEMORY ARRANGEMENT: Loader: 0000000000100000->00000000001ad64c TOTAL: 0000000000000000->00000000ff800000 ENTRY ADDRESS: 0000000000100000 xc: info: PHYSICAL MEMORY ALLOCATION: 4KB PAGES: 0x0000000000000200 2MB PAGES: 0x00000000000003fb 1GB PAGES: 0x0000000000000002 libxl: error: libxl_pci.c:1055:libxl__device_pci_add: PCI device 0:d:0.0 is not assignable Waiting for domain Windows8 (domid 4) to die [pid 5545] Domain 4 has shut down, reason code 1 0x1 Action for shutdown reason code 1 is restart Domain 4 needs to be cleaned up: destroying the domain libxl: error: libxl_pci.c:1001:libxl__device_pci_reset: The kernel doesn't support reset from sysfs for PCI device 0000:0d:00.0 libxl: error: libxl_pci.c:1265:do_pci_remove: xc_deassign_device failed Done. Rebooting now xc: info: VIRTUAL MEMORY ARRANGEMENT: Loader: 0000000000100000->00000000001ad64c TOTAL: 0000000000000000->00000000ff800000 ENTRY ADDRESS: 0000000000100000 xc: info: PHYSICAL MEMORY ALLOCATION: 4KB PAGES: 0x0000000000000200 2MB PAGES: 0x00000000000003fb 1GB PAGES: 0x0000000000000002 libxl: error: libxl_pci.c:1055:libxl__device_pci_add: PCI device 0:d:0.0 is not assignable Waiting for domain Windows8 (domid 5) to die [pid 5545] Domain 5 has shut down, reason code 1 0x1 Action for shutdown reason code 1 is restart Domain 5 needs to be cleaned up: destroying the domain libxl: error: libxl_pci.c:1001:libxl__device_pci_reset: The kernel doesn't support reset from sysfs for PCI device 0000:0d:00.0 libxl: error: libxl_pci.c:1265:do_pci_remove: xc_deassign_device failed Done. Rebooting now xc: info: VIRTUAL MEMORY ARRANGEMENT: Loader: 0000000000100000->00000000001ad64c TOTAL: 0000000000000000->00000000ff800000 ENTRY ADDRESS: 0000000000100000 xc: info: PHYSICAL MEMORY ALLOCATION: 4KB PAGES: 0x0000000000000200 2MB PAGES: 0x00000000000003fb 1GB PAGES: 0x0000000000000002 libxl: error: libxl_pci.c:1055:libxl__device_pci_add: PCI device 0:d:0.0 is not assignable Waiting for domain Windows8 (domid 6) to die [pid 5545] Domain 6 has shut down, reason code 1 0x1 Action for shutdown reason code 1 is restart Domain 6 needs to be cleaned up: destroying the domain libxl: error: libxl_pci.c:1001:libxl__device_pci_reset: The kernel doesn't support reset from sysfs for PCI device 0000:0d:00.0 libxl: error: libxl_pci.c:1265:do_pci_remove: xc_deassign_device failed Done. Rebooting now xc: info: VIRTUAL MEMORY ARRANGEMENT: Loader: 0000000000100000->00000000001ad64c TOTAL: 0000000000000000->00000000ff800000 ENTRY ADDRESS: 0000000000100000 xc: info: PHYSICAL MEMORY ALLOCATION: 4KB PAGES: 0x0000000000000200 2MB PAGES: 0x00000000000003fb 1GB PAGES: 0x0000000000000002 libxl: error: libxl_pci.c:1055:libxl__device_pci_add: PCI device 0:d:0.0 is not assignable Waiting for domain Windows8 (domid 7) to die [pid 5545] Domain 7 has shut down, reason code 1 0x1 Action for shutdown reason code 1 is restart Domain 7 needs to be cleaned up: destroying the domain libxl: error: libxl_pci.c:1001:libxl__device_pci_reset: The kernel doesn't support reset from sysfs for PCI device 0000:0d:00.0 libxl: error: libxl_pci.c:1265:do_pci_remove: xc_deassign_device failed Done. Rebooting now xc: info: VIRTUAL MEMORY ARRANGEMENT: Loader: 0000000000100000->00000000001ad64c TOTAL: 0000000000000000->00000000ff800000 ENTRY ADDRESS: 0000000000100000 xc: info: PHYSICAL MEMORY ALLOCATION: 4KB PAGES: 0x0000000000000200 2MB PAGES: 0x00000000000003fb 1GB PAGES: 0x0000000000000002 libxl: error: libxl_pci.c:1055:libxl__device_pci_add: PCI device 0:d:0.0 is not assignable Waiting for domain Windows8 (domid 8) to die [pid 5545] Domain 8 has been destroyed. --------------060301030907070908060303 Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users --------------060301030907070908060303-- From xen-users-bounces@lists.xen.org Wed Sep 19 17:43:12 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Wed, 19 Sep 2012 17:43:12 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TEOHl-0004d8-VE; Wed, 19 Sep 2012 17:42:05 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TEOHl-0004d3-4t for xen-users@lists.xen.org; Wed, 19 Sep 2012 17:42:05 +0000 Received: from [85.158.138.51:24040] by server-2.bemta-3.messagelabs.com id ED/B4-04862-CE30A505; Wed, 19 Sep 2012 17:42:04 +0000 X-Env-Sender: myrdhn@gmail.com X-Msg-Ref: server-2.tower-174.messagelabs.com!1348076522!31186788!1 X-Originating-IP: [209.85.216.173] X-SpamReason: No, hits=0.3 required=7.0 tests=ML_RADAR_SPEW_LINKS_14, RCVD_BY_IP,spamassassin: X-StarScan-Received: X-StarScan-Version: 6.6.1.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 30284 invoked from network); 19 Sep 2012 17:42:03 -0000 Received: from mail-qc0-f173.google.com (HELO mail-qc0-f173.google.com) (209.85.216.173) by server-2.tower-174.messagelabs.com with RC4-SHA encrypted SMTP; 19 Sep 2012 17:42:03 -0000 Received: by qcab12 with SMTP id b12so1295968qca.32 for ; Wed, 19 Sep 2012 10:42:02 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=from:to:cc:subject:date:message-id:mime-version:content-type :content-transfer-encoding:x-mailer:thread-index:content-language; bh=VgRzZjf8ZXdUiTGPNAzx5zdbT+gt3Qi14f9xxQrxWyc=; b=Int23r/5XbDs8Z/5NHixclA608ne8fMTI5npYN61d6/4o0oiT0krdbHGdjgK6rZBmC 5p5yDr244vzcjGwflnMN2keBaTXSvuOsv/3KW8QOrcHchx+gLGDUT2343wXmjkRsuvSQ DVU7OrszHLsKKvjieT2XgZOstBDJYbcr4JGm3bYFQODReyaySk4ctR0oMMs7MmbWVvPW KD3RZnWWvo7gOybzE+UUHF5TyEQ3/t+9dTQ8W9k2OxDSL7fnWrd9ZWle3ia9ogcWn+tI 7NuDSZ6e2QwBwHgDEG2HSBbIzesov2Zlo2QAAvS6CL5vhETkYnl+iwziq2Jn/RIkY+ME s+uw== Received: by 10.224.222.13 with SMTP id ie13mr8716075qab.69.1348076522001; Wed, 19 Sep 2012 10:42:02 -0700 (PDT) Received: from Belldandy (c-76-119-253-48.hsd1.ma.comcast.net. [76.119.253.48]) by mx.google.com with ESMTPS id l3sm4713226qan.19.2012.09.19.10.42.00 (version=TLSv1/SSLv3 cipher=OTHER); Wed, 19 Sep 2012 10:42:01 -0700 (PDT) From: "Marc Tousignant" To: "'Dariusz Krempa'" Date: Wed, 19 Sep 2012 13:42:03 -0400 Message-ID: <008f01cd968e$15260cb0$3f722610$@gmail.com> MIME-Version: 1.0 X-Mailer: Microsoft Outlook 14.0 Thread-Index: Ac2WjZfP7Gva2X3qRXeqArPf5Tgv7A== Content-Language: en-us Cc: xen-users@lists.xen.org Subject: Re: [Xen-users] Solved - PCIe/VGA passthrough X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org -----Original Message----- From: Dariusz Krempa [mailto:imperiaonline4@gmail.com] Sent: Wednesday, September 19, 2012 11:23 AM To: Marc Tousignant Subject: Re: [Xen-users] PCIe/VGA passthrough 2012/9/19 Marc Tousignant : > > > -----Original Message----- > From: Dariusz Krempa [mailto:imperiaonline4@gmail.com] > Sent: Wednesday, September 19, 2012 9:29 AM > To: Marc Tousignant > Subject: Re: [Xen-users] PCIe/VGA passthrough > > > Hi. > I've spend last few days to turn on vga passthrough on my box and > finally i did it. Everything what i've read about configurations tells > me that its not possible with my MB (Asus P8H67 + Asus GTX560 Top), but... > I followed also tutorial from Teo En Ming and i did patch from David > Gis. I have no BAR's, then i used ranges from dmesg | grep '1:00.0' | > grep mem and did patch like following David's Gis and Teo En Ming descriptions. > > I'm not yet sure that is full success, but Gpu-z and Cpu-z recognized > my hardware, also benchmark from Unigin heaven is pretty good. I did > pciback configuration for window xp DomU not like Teo En Ming with > pci-stub. I hope this will helpfully for You. > > --- > > Unfortunately, this was not helpful at all. I'm only seeing 1 BAR/mem > line pci 0000:01:00.0: BAR 6: assigned [mem 0xcd000000-0xcd01ffff > pref] > > But my video card has ranges: > Region 0: Memory at cc000000 (32-bit, non-prefetchable) [size=16M] > Region 1: Memory at b0000000 (64-bit, prefetchable) [size=256M] > Region 3: Memory at ca000000 (64-bit, non-prefetchable) [size=32M] > Region 5: I/O ports at 9c00 [size=128] What the dmesg seems to > be finding is the one line from the lspci output on my card: > [virtual] Expansion ROM at cd000000 [disabled] [size=128K] > > MarcT > I am totally newbie with linux and Xen, but i think You could rebuild Dom0 or Xen or both, but first try to see what You get from this and compare to David's Gis output. I have for all "=y" grep -i xen /boot/config ---- Solved it. Turns out you can't find the memory without first setting up the kernel commands to hide the device. dmesg | grep 01:00.0 | grep "pci.*mem" pci 0000:01:00.0: BAR 0: assigned [mem 0xcc000000-0xccffffff] pci 0000:01:00.0: BAR 1: assigned [mem 0xb0000000-0xbfffffff 64bit pref] pci 0000:01:00.0: BAR 3: assigned [mem 0xca000000-0xcbffffff 64bit] pci 0000:01:00.0: BAR 6: assigned [mem 0xcd000000-0xcd01ffff pref] MarcT _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Wed Sep 19 17:43:12 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Wed, 19 Sep 2012 17:43:12 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TEOHl-0004d8-VE; Wed, 19 Sep 2012 17:42:05 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TEOHl-0004d3-4t for xen-users@lists.xen.org; Wed, 19 Sep 2012 17:42:05 +0000 Received: from [85.158.138.51:24040] by server-2.bemta-3.messagelabs.com id ED/B4-04862-CE30A505; Wed, 19 Sep 2012 17:42:04 +0000 X-Env-Sender: myrdhn@gmail.com X-Msg-Ref: server-2.tower-174.messagelabs.com!1348076522!31186788!1 X-Originating-IP: [209.85.216.173] X-SpamReason: No, hits=0.3 required=7.0 tests=ML_RADAR_SPEW_LINKS_14, RCVD_BY_IP,spamassassin: X-StarScan-Received: X-StarScan-Version: 6.6.1.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 30284 invoked from network); 19 Sep 2012 17:42:03 -0000 Received: from mail-qc0-f173.google.com (HELO mail-qc0-f173.google.com) (209.85.216.173) by server-2.tower-174.messagelabs.com with RC4-SHA encrypted SMTP; 19 Sep 2012 17:42:03 -0000 Received: by qcab12 with SMTP id b12so1295968qca.32 for ; Wed, 19 Sep 2012 10:42:02 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=from:to:cc:subject:date:message-id:mime-version:content-type :content-transfer-encoding:x-mailer:thread-index:content-language; bh=VgRzZjf8ZXdUiTGPNAzx5zdbT+gt3Qi14f9xxQrxWyc=; b=Int23r/5XbDs8Z/5NHixclA608ne8fMTI5npYN61d6/4o0oiT0krdbHGdjgK6rZBmC 5p5yDr244vzcjGwflnMN2keBaTXSvuOsv/3KW8QOrcHchx+gLGDUT2343wXmjkRsuvSQ DVU7OrszHLsKKvjieT2XgZOstBDJYbcr4JGm3bYFQODReyaySk4ctR0oMMs7MmbWVvPW KD3RZnWWvo7gOybzE+UUHF5TyEQ3/t+9dTQ8W9k2OxDSL7fnWrd9ZWle3ia9ogcWn+tI 7NuDSZ6e2QwBwHgDEG2HSBbIzesov2Zlo2QAAvS6CL5vhETkYnl+iwziq2Jn/RIkY+ME s+uw== Received: by 10.224.222.13 with SMTP id ie13mr8716075qab.69.1348076522001; Wed, 19 Sep 2012 10:42:02 -0700 (PDT) Received: from Belldandy (c-76-119-253-48.hsd1.ma.comcast.net. [76.119.253.48]) by mx.google.com with ESMTPS id l3sm4713226qan.19.2012.09.19.10.42.00 (version=TLSv1/SSLv3 cipher=OTHER); Wed, 19 Sep 2012 10:42:01 -0700 (PDT) From: "Marc Tousignant" To: "'Dariusz Krempa'" Date: Wed, 19 Sep 2012 13:42:03 -0400 Message-ID: <008f01cd968e$15260cb0$3f722610$@gmail.com> MIME-Version: 1.0 X-Mailer: Microsoft Outlook 14.0 Thread-Index: Ac2WjZfP7Gva2X3qRXeqArPf5Tgv7A== Content-Language: en-us Cc: xen-users@lists.xen.org Subject: Re: [Xen-users] Solved - PCIe/VGA passthrough X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org -----Original Message----- From: Dariusz Krempa [mailto:imperiaonline4@gmail.com] Sent: Wednesday, September 19, 2012 11:23 AM To: Marc Tousignant Subject: Re: [Xen-users] PCIe/VGA passthrough 2012/9/19 Marc Tousignant : > > > -----Original Message----- > From: Dariusz Krempa [mailto:imperiaonline4@gmail.com] > Sent: Wednesday, September 19, 2012 9:29 AM > To: Marc Tousignant > Subject: Re: [Xen-users] PCIe/VGA passthrough > > > Hi. > I've spend last few days to turn on vga passthrough on my box and > finally i did it. Everything what i've read about configurations tells > me that its not possible with my MB (Asus P8H67 + Asus GTX560 Top), but... > I followed also tutorial from Teo En Ming and i did patch from David > Gis. I have no BAR's, then i used ranges from dmesg | grep '1:00.0' | > grep mem and did patch like following David's Gis and Teo En Ming descriptions. > > I'm not yet sure that is full success, but Gpu-z and Cpu-z recognized > my hardware, also benchmark from Unigin heaven is pretty good. I did > pciback configuration for window xp DomU not like Teo En Ming with > pci-stub. I hope this will helpfully for You. > > --- > > Unfortunately, this was not helpful at all. I'm only seeing 1 BAR/mem > line pci 0000:01:00.0: BAR 6: assigned [mem 0xcd000000-0xcd01ffff > pref] > > But my video card has ranges: > Region 0: Memory at cc000000 (32-bit, non-prefetchable) [size=16M] > Region 1: Memory at b0000000 (64-bit, prefetchable) [size=256M] > Region 3: Memory at ca000000 (64-bit, non-prefetchable) [size=32M] > Region 5: I/O ports at 9c00 [size=128] What the dmesg seems to > be finding is the one line from the lspci output on my card: > [virtual] Expansion ROM at cd000000 [disabled] [size=128K] > > MarcT > I am totally newbie with linux and Xen, but i think You could rebuild Dom0 or Xen or both, but first try to see what You get from this and compare to David's Gis output. I have for all "=y" grep -i xen /boot/config ---- Solved it. Turns out you can't find the memory without first setting up the kernel commands to hide the device. dmesg | grep 01:00.0 | grep "pci.*mem" pci 0000:01:00.0: BAR 0: assigned [mem 0xcc000000-0xccffffff] pci 0000:01:00.0: BAR 1: assigned [mem 0xb0000000-0xbfffffff 64bit pref] pci 0000:01:00.0: BAR 3: assigned [mem 0xca000000-0xcbffffff 64bit] pci 0000:01:00.0: BAR 6: assigned [mem 0xcd000000-0xcd01ffff pref] MarcT _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Thu Sep 20 03:41:53 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Thu, 20 Sep 2012 03:41:53 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TEXck-0004zH-DS; Thu, 20 Sep 2012 03:40:22 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TEXcj-0004zC-Bj for Xen-users@lists.xen.org; Thu, 20 Sep 2012 03:40:21 +0000 Received: from [85.158.143.35:46622] by server-3.bemta-4.messagelabs.com id 48/F4-10986-4209A505; Thu, 20 Sep 2012 03:40:20 +0000 X-Env-Sender: jrfleet@istech-corp.com X-Msg-Ref: server-16.tower-21.messagelabs.com!1348112416!16578818!1 X-Originating-IP: [209.85.220.173] X-SpamReason: No, hits=1.2 required=7.0 tests=HTML_20_30,HTML_MESSAGE, RCVD_BY_IP X-StarScan-Received: X-StarScan-Version: 6.6.1.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 18985 invoked from network); 20 Sep 2012 03:40:18 -0000 Received: from mail-vc0-f173.google.com (HELO mail-vc0-f173.google.com) (209.85.220.173) by server-16.tower-21.messagelabs.com with RC4-SHA encrypted SMTP; 20 Sep 2012 03:40:18 -0000 Received: by vcbfl15 with SMTP id fl15so2450523vcb.32 for ; Wed, 19 Sep 2012 20:40:16 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type:x-gm-message-state; bh=yOZh0X9YfQfiJN7qK4jHHHmnpB3azk9C7gFbzn88TfA=; b=c+5ir/8VYt0y6yu8DaR5y/1bPqleQX1H2tf4I4jM5ZEUMBDNfSNBAqTtXP8kimFHvN VNebLaW7mQ1RG8A+mUbboy6t3O2d+ll2HTHvZwLU10BePjCYIB5bExVW9HOewG/im93x YMzz50On76l6od0+Nx9Wv/OrVbL5ztQhNcvR7jAkZ3jCHOSxAQeuOMwsHL2o2nEJ0x4t dkT7PzaOZsgw2fsNA3/VKwwZK5p3xID+ZphgQNOuXIXZbIWT43xuQxicAfbeRCqxqhqp g8ZFY6j/jEPdaq5bgfJugDfWyo6Yh4Y5cox1nR5DWumknVg70WFuM4x74+RVT39SFh75 riCA== MIME-Version: 1.0 Received: by 10.58.132.239 with SMTP id ox15mr293520veb.59.1348112416463; Wed, 19 Sep 2012 20:40:16 -0700 (PDT) Received: by 10.58.127.97 with HTTP; Wed, 19 Sep 2012 20:40:16 -0700 (PDT) In-Reply-To: <008f01cd968e$15260cb0$3f722610$@gmail.com> References: <008f01cd968e$15260cb0$3f722610$@gmail.com> Date: Wed, 19 Sep 2012 23:40:16 -0400 Message-ID: From: James Fleet To: Xen-users@lists.xen.org X-Gm-Message-State: ALoCoQlqOOQAJOyaJH9YxkY8pu11MDoIfyusnrbn4MFxtN7mFBUbP9Lix0vGMgNG4y9ua50B0urF Subject: Re: [Xen-users] Solved - PCIe/VGA passthrough X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============2545213961682813236==" Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org --===============2545213961682813236== Content-Type: multipart/alternative; boundary=047d7b6d7c22b359ef04ca19e13f --047d7b6d7c22b359ef04ca19e13f Content-Type: text/plain; charset=ISO-8859-1 Please remove me from this list. On Wed, Sep 19, 2012 at 1:42 PM, Marc Tousignant wrote: > > > -----Original Message----- > From: Dariusz Krempa [mailto:imperiaonline4@gmail.com] > Sent: Wednesday, September 19, 2012 11:23 AM > To: Marc Tousignant > Subject: Re: [Xen-users] PCIe/VGA passthrough > > 2012/9/19 Marc Tousignant : > > > > > > -----Original Message----- > > From: Dariusz Krempa [mailto:imperiaonline4@gmail.com] > > Sent: Wednesday, September 19, 2012 9:29 AM > > To: Marc Tousignant > > Subject: Re: [Xen-users] PCIe/VGA passthrough > > > > > > Hi. > > I've spend last few days to turn on vga passthrough on my box and > > finally i did it. Everything what i've read about configurations tells > > me that its not possible with my MB (Asus P8H67 + Asus GTX560 Top), > but... > > I followed also tutorial from Teo En Ming and i did patch from David > > Gis. I have no BAR's, then i used ranges from dmesg | grep '1:00.0' | > > grep mem and did patch like following David's Gis and Teo En Ming > descriptions. > > > > I'm not yet sure that is full success, but Gpu-z and Cpu-z recognized > > my hardware, also benchmark from Unigin heaven is pretty good. I did > > pciback configuration for window xp DomU not like Teo En Ming with > > pci-stub. I hope this will helpfully for You. > > > > --- > > > > Unfortunately, this was not helpful at all. I'm only seeing 1 BAR/mem > > line pci 0000:01:00.0: BAR 6: assigned [mem 0xcd000000-0xcd01ffff > > pref] > > > > But my video card has ranges: > > Region 0: Memory at cc000000 (32-bit, non-prefetchable) > [size=16M] > > Region 1: Memory at b0000000 (64-bit, prefetchable) [size=256M] > > Region 3: Memory at ca000000 (64-bit, non-prefetchable) > [size=32M] > > Region 5: I/O ports at 9c00 [size=128] What the dmesg seems to > > be finding is the one line from the lspci output on my card: > > [virtual] Expansion ROM at cd000000 [disabled] [size=128K] > > > > MarcT > > > > I am totally newbie with linux and Xen, but i think You could rebuild > Dom0 or Xen or both, but first try to see what You get from this and > compare > to David's Gis output. I have for all "=y" > > grep -i xen /boot/config > > ---- > > Solved it. Turns out you can't find the memory without first setting up the > kernel commands to hide the device. > > dmesg | grep 01:00.0 | grep "pci.*mem" > pci 0000:01:00.0: BAR 0: assigned [mem 0xcc000000-0xccffffff] > pci 0000:01:00.0: BAR 1: assigned [mem 0xb0000000-0xbfffffff 64bit pref] > pci 0000:01:00.0: BAR 3: assigned [mem 0xca000000-0xcbffffff 64bit] > pci 0000:01:00.0: BAR 6: assigned [mem 0xcd000000-0xcd01ffff pref] > > MarcT > > > _______________________________________________ > Xen-users mailing list > Xen-users@lists.xen.org > http://lists.xen.org/xen-users > -- James R. Fleet Innovative Solutions Technology 484 Williamsport Pike #135 Martinsburg, WV 25404 888.809.0223 ext.702 --047d7b6d7c22b359ef04ca19e13f Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable
Please remove me from this list.
On Wed, = Sep 19, 2012 at 1:42 PM, Marc Tousignant <myrdhn@gmail.com> w= rote:


-----Original Message-----
From: Dariusz Krempa [mailto:im= periaonline4@gmail.com]
Sent: Wednesday, September 19, 2012 11:23 AM
To: Marc Tousignant
Subject: Re: [Xen-users] PCIe/VGA passthrough

2012/9/19 Marc Tousignant <myrdhn@gm= ail.com>:
>
>
> -----Original Message-----
> From: Dariusz Krempa [mailto:imperiaonline4@gmail.com]
> Sent: Wednesday, September 19, 2012 9:29 AM
> To: Marc Tousignant
> Subject: Re: [Xen-users] PCIe/VGA passthrough
>
>
> Hi.
> I've spend last few days to turn on vga passthrough on my box and<= br> > finally i did it. Everything what i've read about configurations t= ells
> me that its not possible with my MB (Asus P8H67 + Asus GTX560 Top), bu= t...
> I followed also tutorial from Teo En Ming and i did patch from David > Gis. I have no BAR's, then i used ranges from dmesg | grep '1:= 00.0' |
> grep mem and did patch like following David's Gis and Teo En Ming<= br> descriptions.
>
> I'm not yet sure that is full success, but Gpu-z and Cpu-z recogni= zed
> my hardware, also benchmark from Unigin heaven is pretty good. I did > pciback configuration for window xp DomU not like Teo En Ming with
> pci-stub. I hope this will helpfully for You.
>
> ---
>
> Unfortunately, this was not helpful at all. I'm only seeing 1 BAR/= mem
> line pci 0000:01:00.0: BAR 6: assigned [mem 0xcd000000-0xcd01ffff
> pref]
>
> But my video card has ranges:
> =A0 =A0 =A0 =A0 Region 0: Memory at cc000000 (32-bit, non-prefetchable= ) [size=3D16M]
> =A0 =A0 =A0 =A0 Region 1: Memory at b0000000 (64-bit, prefetchable) [s= ize=3D256M]
> =A0 =A0 =A0 =A0 Region 3: Memory at ca000000 (64-bit, non-prefetchable= ) [size=3D32M]
> =A0 =A0 =A0 =A0 Region 5: I/O ports at 9c00 [size=3D128] What the dmes= g seems to
> be finding is the one line from the lspci output on my card:
> =A0 =A0 =A0 =A0 =A0[virtual] Expansion ROM at cd000000 [disabled] [siz= e=3D128K]
>
> MarcT
>

I am totally newbie with linux and Xen, but i think You could rebuild
Dom0 or Xen or both, but first try to see what You get from this and compar= e
to David's Gis output. I have for all "=3Dy"

grep -i xen /boot/config

----

Solved it. Turns out you can't find the memory without first setting up= the
kernel commands to hide the device.

dmesg | grep 01:00.0 | grep "pci.*mem"
pci 0000:01:00.0: BAR 0: assigned [mem 0xcc000000-0xccffffff]
pci 0000:01:00.0: BAR 1: assigned [mem 0xb0000000-0xbfffffff 64bit pref] pci 0000:01:00.0: BAR 3: assigned [mem 0xca000000-0xcbffffff 64bit]
pci 0000:01:00.0: BAR 6: assigned [mem 0xcd000000-0xcd01ffff pref]

MarcT


_______________________________________________
Xen-users mailing list
Xen-users@lists.xen.org
http://lists.x= en.org/xen-users



--
James R. Fle= et=A0
Innovative Solutions Technology
484 Williamsport Pike=A0 #135=
Martinsburg, WV 25404
=A0888.809.0223 ext.702
--047d7b6d7c22b359ef04ca19e13f-- --===============2545213961682813236== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users --===============2545213961682813236==-- From xen-users-bounces@lists.xen.org Thu Sep 20 03:41:53 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Thu, 20 Sep 2012 03:41:53 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TEXck-0004zH-DS; Thu, 20 Sep 2012 03:40:22 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TEXcj-0004zC-Bj for Xen-users@lists.xen.org; Thu, 20 Sep 2012 03:40:21 +0000 Received: from [85.158.143.35:46622] by server-3.bemta-4.messagelabs.com id 48/F4-10986-4209A505; Thu, 20 Sep 2012 03:40:20 +0000 X-Env-Sender: jrfleet@istech-corp.com X-Msg-Ref: server-16.tower-21.messagelabs.com!1348112416!16578818!1 X-Originating-IP: [209.85.220.173] X-SpamReason: No, hits=1.2 required=7.0 tests=HTML_20_30,HTML_MESSAGE, RCVD_BY_IP X-StarScan-Received: X-StarScan-Version: 6.6.1.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 18985 invoked from network); 20 Sep 2012 03:40:18 -0000 Received: from mail-vc0-f173.google.com (HELO mail-vc0-f173.google.com) (209.85.220.173) by server-16.tower-21.messagelabs.com with RC4-SHA encrypted SMTP; 20 Sep 2012 03:40:18 -0000 Received: by vcbfl15 with SMTP id fl15so2450523vcb.32 for ; Wed, 19 Sep 2012 20:40:16 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type:x-gm-message-state; bh=yOZh0X9YfQfiJN7qK4jHHHmnpB3azk9C7gFbzn88TfA=; b=c+5ir/8VYt0y6yu8DaR5y/1bPqleQX1H2tf4I4jM5ZEUMBDNfSNBAqTtXP8kimFHvN VNebLaW7mQ1RG8A+mUbboy6t3O2d+ll2HTHvZwLU10BePjCYIB5bExVW9HOewG/im93x YMzz50On76l6od0+Nx9Wv/OrVbL5ztQhNcvR7jAkZ3jCHOSxAQeuOMwsHL2o2nEJ0x4t dkT7PzaOZsgw2fsNA3/VKwwZK5p3xID+ZphgQNOuXIXZbIWT43xuQxicAfbeRCqxqhqp g8ZFY6j/jEPdaq5bgfJugDfWyo6Yh4Y5cox1nR5DWumknVg70WFuM4x74+RVT39SFh75 riCA== MIME-Version: 1.0 Received: by 10.58.132.239 with SMTP id ox15mr293520veb.59.1348112416463; Wed, 19 Sep 2012 20:40:16 -0700 (PDT) Received: by 10.58.127.97 with HTTP; Wed, 19 Sep 2012 20:40:16 -0700 (PDT) In-Reply-To: <008f01cd968e$15260cb0$3f722610$@gmail.com> References: <008f01cd968e$15260cb0$3f722610$@gmail.com> Date: Wed, 19 Sep 2012 23:40:16 -0400 Message-ID: From: James Fleet To: Xen-users@lists.xen.org X-Gm-Message-State: ALoCoQlqOOQAJOyaJH9YxkY8pu11MDoIfyusnrbn4MFxtN7mFBUbP9Lix0vGMgNG4y9ua50B0urF Subject: Re: [Xen-users] Solved - PCIe/VGA passthrough X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============2545213961682813236==" Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org --===============2545213961682813236== Content-Type: multipart/alternative; boundary=047d7b6d7c22b359ef04ca19e13f --047d7b6d7c22b359ef04ca19e13f Content-Type: text/plain; charset=ISO-8859-1 Please remove me from this list. On Wed, Sep 19, 2012 at 1:42 PM, Marc Tousignant wrote: > > > -----Original Message----- > From: Dariusz Krempa [mailto:imperiaonline4@gmail.com] > Sent: Wednesday, September 19, 2012 11:23 AM > To: Marc Tousignant > Subject: Re: [Xen-users] PCIe/VGA passthrough > > 2012/9/19 Marc Tousignant : > > > > > > -----Original Message----- > > From: Dariusz Krempa [mailto:imperiaonline4@gmail.com] > > Sent: Wednesday, September 19, 2012 9:29 AM > > To: Marc Tousignant > > Subject: Re: [Xen-users] PCIe/VGA passthrough > > > > > > Hi. > > I've spend last few days to turn on vga passthrough on my box and > > finally i did it. Everything what i've read about configurations tells > > me that its not possible with my MB (Asus P8H67 + Asus GTX560 Top), > but... > > I followed also tutorial from Teo En Ming and i did patch from David > > Gis. I have no BAR's, then i used ranges from dmesg | grep '1:00.0' | > > grep mem and did patch like following David's Gis and Teo En Ming > descriptions. > > > > I'm not yet sure that is full success, but Gpu-z and Cpu-z recognized > > my hardware, also benchmark from Unigin heaven is pretty good. I did > > pciback configuration for window xp DomU not like Teo En Ming with > > pci-stub. I hope this will helpfully for You. > > > > --- > > > > Unfortunately, this was not helpful at all. I'm only seeing 1 BAR/mem > > line pci 0000:01:00.0: BAR 6: assigned [mem 0xcd000000-0xcd01ffff > > pref] > > > > But my video card has ranges: > > Region 0: Memory at cc000000 (32-bit, non-prefetchable) > [size=16M] > > Region 1: Memory at b0000000 (64-bit, prefetchable) [size=256M] > > Region 3: Memory at ca000000 (64-bit, non-prefetchable) > [size=32M] > > Region 5: I/O ports at 9c00 [size=128] What the dmesg seems to > > be finding is the one line from the lspci output on my card: > > [virtual] Expansion ROM at cd000000 [disabled] [size=128K] > > > > MarcT > > > > I am totally newbie with linux and Xen, but i think You could rebuild > Dom0 or Xen or both, but first try to see what You get from this and > compare > to David's Gis output. I have for all "=y" > > grep -i xen /boot/config > > ---- > > Solved it. Turns out you can't find the memory without first setting up the > kernel commands to hide the device. > > dmesg | grep 01:00.0 | grep "pci.*mem" > pci 0000:01:00.0: BAR 0: assigned [mem 0xcc000000-0xccffffff] > pci 0000:01:00.0: BAR 1: assigned [mem 0xb0000000-0xbfffffff 64bit pref] > pci 0000:01:00.0: BAR 3: assigned [mem 0xca000000-0xcbffffff 64bit] > pci 0000:01:00.0: BAR 6: assigned [mem 0xcd000000-0xcd01ffff pref] > > MarcT > > > _______________________________________________ > Xen-users mailing list > Xen-users@lists.xen.org > http://lists.xen.org/xen-users > -- James R. Fleet Innovative Solutions Technology 484 Williamsport Pike #135 Martinsburg, WV 25404 888.809.0223 ext.702 --047d7b6d7c22b359ef04ca19e13f Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable
Please remove me from this list.
On Wed, = Sep 19, 2012 at 1:42 PM, Marc Tousignant <myrdhn@gmail.com> w= rote:


-----Original Message-----
From: Dariusz Krempa [mailto:im= periaonline4@gmail.com]
Sent: Wednesday, September 19, 2012 11:23 AM
To: Marc Tousignant
Subject: Re: [Xen-users] PCIe/VGA passthrough

2012/9/19 Marc Tousignant <myrdhn@gm= ail.com>:
>
>
> -----Original Message-----
> From: Dariusz Krempa [mailto:imperiaonline4@gmail.com]
> Sent: Wednesday, September 19, 2012 9:29 AM
> To: Marc Tousignant
> Subject: Re: [Xen-users] PCIe/VGA passthrough
>
>
> Hi.
> I've spend last few days to turn on vga passthrough on my box and<= br> > finally i did it. Everything what i've read about configurations t= ells
> me that its not possible with my MB (Asus P8H67 + Asus GTX560 Top), bu= t...
> I followed also tutorial from Teo En Ming and i did patch from David > Gis. I have no BAR's, then i used ranges from dmesg | grep '1:= 00.0' |
> grep mem and did patch like following David's Gis and Teo En Ming<= br> descriptions.
>
> I'm not yet sure that is full success, but Gpu-z and Cpu-z recogni= zed
> my hardware, also benchmark from Unigin heaven is pretty good. I did > pciback configuration for window xp DomU not like Teo En Ming with
> pci-stub. I hope this will helpfully for You.
>
> ---
>
> Unfortunately, this was not helpful at all. I'm only seeing 1 BAR/= mem
> line pci 0000:01:00.0: BAR 6: assigned [mem 0xcd000000-0xcd01ffff
> pref]
>
> But my video card has ranges:
> =A0 =A0 =A0 =A0 Region 0: Memory at cc000000 (32-bit, non-prefetchable= ) [size=3D16M]
> =A0 =A0 =A0 =A0 Region 1: Memory at b0000000 (64-bit, prefetchable) [s= ize=3D256M]
> =A0 =A0 =A0 =A0 Region 3: Memory at ca000000 (64-bit, non-prefetchable= ) [size=3D32M]
> =A0 =A0 =A0 =A0 Region 5: I/O ports at 9c00 [size=3D128] What the dmes= g seems to
> be finding is the one line from the lspci output on my card:
> =A0 =A0 =A0 =A0 =A0[virtual] Expansion ROM at cd000000 [disabled] [siz= e=3D128K]
>
> MarcT
>

I am totally newbie with linux and Xen, but i think You could rebuild
Dom0 or Xen or both, but first try to see what You get from this and compar= e
to David's Gis output. I have for all "=3Dy"

grep -i xen /boot/config

----

Solved it. Turns out you can't find the memory without first setting up= the
kernel commands to hide the device.

dmesg | grep 01:00.0 | grep "pci.*mem"
pci 0000:01:00.0: BAR 0: assigned [mem 0xcc000000-0xccffffff]
pci 0000:01:00.0: BAR 1: assigned [mem 0xb0000000-0xbfffffff 64bit pref] pci 0000:01:00.0: BAR 3: assigned [mem 0xca000000-0xcbffffff 64bit]
pci 0000:01:00.0: BAR 6: assigned [mem 0xcd000000-0xcd01ffff pref]

MarcT


_______________________________________________
Xen-users mailing list
Xen-users@lists.xen.org
http://lists.x= en.org/xen-users



--
James R. Fle= et=A0
Innovative Solutions Technology
484 Williamsport Pike=A0 #135=
Martinsburg, WV 25404
=A0888.809.0223 ext.702
--047d7b6d7c22b359ef04ca19e13f-- --===============2545213961682813236== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users --===============2545213961682813236==-- From xen-users-bounces@lists.xen.org Thu Sep 20 06:40:25 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Thu, 20 Sep 2012 06:40:25 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TEaPl-0006Pu-QO; Thu, 20 Sep 2012 06:39:09 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TEK58-0005ad-2J for xen-users@lists.xen.org; Wed, 19 Sep 2012 13:12:46 +0000 Received: from [85.158.139.83:60635] by server-3.bemta-5.messagelabs.com id 1C/F9-21836-DC4C9505; Wed, 19 Sep 2012 13:12:45 +0000 X-Env-Sender: adam@websitemanagers.com.au X-Msg-Ref: server-6.tower-182.messagelabs.com!1348060360!27328089!1 X-Originating-IP: [203.56.191.70] X-SpamReason: No, hits=0.0 required=7.0 tests= X-StarScan-Received: X-StarScan-Version: 6.6.1.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 22062 invoked from network); 19 Sep 2012 13:12:44 -0000 Received: from unknown (HELO hammer.websitemanagers.com.au) (203.56.191.70) by server-6.tower-182.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 19 Sep 2012 13:12:44 -0000 Received: (qmail 11228 invoked by uid 1011); 19 Sep 2012 13:12:10 -0000 Received: from 124.246.8.196 by hammer (envelope-from , uid 1008) with qmail-scanner-1.24 (clamdscan: 0.97.3/15370. spamassassin: 3.3.1. Clear:RC:1(124.246.8.196):. Processed in 0.059082 secs); 19 Sep 2012 13:12:10 -0000 Received: from unknown (HELO ?192.168.2.90?) (124.246.8.196) by 0 with SMTP; 19 Sep 2012 13:12:10 -0000 Message-ID: <5059C4A9.2060403@websitemanagers.com.au> Date: Wed, 19 Sep 2012 23:12:09 +1000 From: Adam Goryachev User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:15.0) Gecko/20120827 Thunderbird/15.0 MIME-Version: 1.0 To: James Harper References: <5051D0C5.5070600@websitemanagers.com.au> <1347609879.24226.148.camel@zakaz.uk.xensource.com> <50532CE9.5080601@websitemanagers.com.au> <1347629416.24226.208.camel@zakaz.uk.xensource.com> <505344E8.2030400@websitemanagers.com.au> <505871D6.2060801@websitemanagers.com.au> <1348044096.14977.84.camel@zakaz.uk.xensource.com> <505993A6.2080804@websitemanagers.com.au> <5059B853.9030903@websitemanagers.com.au> <1348057647.14977.104.camel@zakaz.uk.xensource.com> <6035A0D088A63A46850C3988ED045A4B29BA8C0B@BITCOM1.int.sbss.com.au> In-Reply-To: <6035A0D088A63A46850C3988ED045A4B29BA8C0B@BITCOM1.int.sbss.com.au> X-Mailman-Approved-At: Thu, 20 Sep 2012 06:39:08 +0000 Cc: "xen-users@lists.xen.org" , Ian Campbell Subject: Re: [Xen-users] SOLVED - Poor Windows 2003 + GPLPV performance compared to VMWare X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org On 19/09/12 23:00, James Harper wrote: >> On Wed, 2012-09-19 at 13:19 +0100, Adam Goryachev wrote: >>> On 19/09/12 19:43, Adam Goryachev wrote: >>>> I've updated to SP2, and will re-test in the next few hours, >>> Excellent news, the issue is completely resolved, and in fact, >>> performance is now better than vmware, and better than the old >>> original physical box pre-virtualisation. The entire task now >>> completed in 30 minutes, the previous best was 40 minutes (ie, prior to >> xen). >> >> Excellent news! >> >> James, since you suggested it, do you happen to know what it is about >> pre-SP2 W2K3 that is so bad? Do those versions beat on the TPR or >> something else? >> >> (Just curious) >> > Yes it will almost certainly be TPR access. I actually thought MS made the change in SP1 but maybe it was SP2 (don't know if the OP upgraded from RTM to sp2 or sp1 to sp2, but quite possibly I just don't remember :) Nope, definitely had SP1, and installed SP2 to get the performance boost (massive performance boost). > The change they made means that the TPR doesn't get touched at all anymore, so is much faster. > > For prior versions (and XP and 2000), GPLPV can patch AMD systems to use the CR8 (I think) registr for TPR access which is much faster. For Intel, the best I could do was cache TPR so that reads were fast... it's still quite a speedup. Am running this on AMD, with the GPLPV drivers, so I guess something isn't working right with that optimisation... Specifically, using the AMD Phenom(tm) II X6 1100T Processor Perhaps this processor doesn't have the CR8 register, maybe an opteron is needed or something? > I thought Xen optimised this for Intel though and my patching wasn't necessary anymore? Or maybe the OP is running a version of xen that doesn't have that feature?? So Xen is patched only for Intel, and therefore I missed out again since I am on AMD, or my xen doesn't have this feature. xen_major : 4 xen_minor : 1 xen_extra : .3 All software is Debian Testing current. Sure, I'd be happy to get additional performance from further tuning, but I'm seriously happy at this stage of things... Now all I need to do is get a modem working with a serial port over ethernet device.... That I'll leave to another day/thread :) Regards, Adam -- Adam Goryachev Website Managers Ph: +61 2 8304 0000 adam@websitemanagers.com.au Fax: +61 2 8304 0001 www.websitemanagers.com.au _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Thu Sep 20 06:40:25 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Thu, 20 Sep 2012 06:40:25 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TEaPl-0006Pu-QO; Thu, 20 Sep 2012 06:39:09 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TEK58-0005ad-2J for xen-users@lists.xen.org; Wed, 19 Sep 2012 13:12:46 +0000 Received: from [85.158.139.83:60635] by server-3.bemta-5.messagelabs.com id 1C/F9-21836-DC4C9505; Wed, 19 Sep 2012 13:12:45 +0000 X-Env-Sender: adam@websitemanagers.com.au X-Msg-Ref: server-6.tower-182.messagelabs.com!1348060360!27328089!1 X-Originating-IP: [203.56.191.70] X-SpamReason: No, hits=0.0 required=7.0 tests= X-StarScan-Received: X-StarScan-Version: 6.6.1.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 22062 invoked from network); 19 Sep 2012 13:12:44 -0000 Received: from unknown (HELO hammer.websitemanagers.com.au) (203.56.191.70) by server-6.tower-182.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 19 Sep 2012 13:12:44 -0000 Received: (qmail 11228 invoked by uid 1011); 19 Sep 2012 13:12:10 -0000 Received: from 124.246.8.196 by hammer (envelope-from , uid 1008) with qmail-scanner-1.24 (clamdscan: 0.97.3/15370. spamassassin: 3.3.1. Clear:RC:1(124.246.8.196):. Processed in 0.059082 secs); 19 Sep 2012 13:12:10 -0000 Received: from unknown (HELO ?192.168.2.90?) (124.246.8.196) by 0 with SMTP; 19 Sep 2012 13:12:10 -0000 Message-ID: <5059C4A9.2060403@websitemanagers.com.au> Date: Wed, 19 Sep 2012 23:12:09 +1000 From: Adam Goryachev User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:15.0) Gecko/20120827 Thunderbird/15.0 MIME-Version: 1.0 To: James Harper References: <5051D0C5.5070600@websitemanagers.com.au> <1347609879.24226.148.camel@zakaz.uk.xensource.com> <50532CE9.5080601@websitemanagers.com.au> <1347629416.24226.208.camel@zakaz.uk.xensource.com> <505344E8.2030400@websitemanagers.com.au> <505871D6.2060801@websitemanagers.com.au> <1348044096.14977.84.camel@zakaz.uk.xensource.com> <505993A6.2080804@websitemanagers.com.au> <5059B853.9030903@websitemanagers.com.au> <1348057647.14977.104.camel@zakaz.uk.xensource.com> <6035A0D088A63A46850C3988ED045A4B29BA8C0B@BITCOM1.int.sbss.com.au> In-Reply-To: <6035A0D088A63A46850C3988ED045A4B29BA8C0B@BITCOM1.int.sbss.com.au> X-Mailman-Approved-At: Thu, 20 Sep 2012 06:39:08 +0000 Cc: "xen-users@lists.xen.org" , Ian Campbell Subject: Re: [Xen-users] SOLVED - Poor Windows 2003 + GPLPV performance compared to VMWare X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org On 19/09/12 23:00, James Harper wrote: >> On Wed, 2012-09-19 at 13:19 +0100, Adam Goryachev wrote: >>> On 19/09/12 19:43, Adam Goryachev wrote: >>>> I've updated to SP2, and will re-test in the next few hours, >>> Excellent news, the issue is completely resolved, and in fact, >>> performance is now better than vmware, and better than the old >>> original physical box pre-virtualisation. The entire task now >>> completed in 30 minutes, the previous best was 40 minutes (ie, prior to >> xen). >> >> Excellent news! >> >> James, since you suggested it, do you happen to know what it is about >> pre-SP2 W2K3 that is so bad? Do those versions beat on the TPR or >> something else? >> >> (Just curious) >> > Yes it will almost certainly be TPR access. I actually thought MS made the change in SP1 but maybe it was SP2 (don't know if the OP upgraded from RTM to sp2 or sp1 to sp2, but quite possibly I just don't remember :) Nope, definitely had SP1, and installed SP2 to get the performance boost (massive performance boost). > The change they made means that the TPR doesn't get touched at all anymore, so is much faster. > > For prior versions (and XP and 2000), GPLPV can patch AMD systems to use the CR8 (I think) registr for TPR access which is much faster. For Intel, the best I could do was cache TPR so that reads were fast... it's still quite a speedup. Am running this on AMD, with the GPLPV drivers, so I guess something isn't working right with that optimisation... Specifically, using the AMD Phenom(tm) II X6 1100T Processor Perhaps this processor doesn't have the CR8 register, maybe an opteron is needed or something? > I thought Xen optimised this for Intel though and my patching wasn't necessary anymore? Or maybe the OP is running a version of xen that doesn't have that feature?? So Xen is patched only for Intel, and therefore I missed out again since I am on AMD, or my xen doesn't have this feature. xen_major : 4 xen_minor : 1 xen_extra : .3 All software is Debian Testing current. Sure, I'd be happy to get additional performance from further tuning, but I'm seriously happy at this stage of things... Now all I need to do is get a modem working with a serial port over ethernet device.... That I'll leave to another day/thread :) Regards, Adam -- Adam Goryachev Website Managers Ph: +61 2 8304 0000 adam@websitemanagers.com.au Fax: +61 2 8304 0001 www.websitemanagers.com.au _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Thu Sep 20 08:59:02 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Thu, 20 Sep 2012 08:59:02 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TEca6-0003yt-0I; Thu, 20 Sep 2012 08:57:58 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TEca3-0003yQ-Kp for xen-users@lists.xen.org; Thu, 20 Sep 2012 08:57:55 +0000 Received: from [85.158.137.99:19967] by server-12.bemta-3.messagelabs.com id F2/E1-10384-29ADA505; Thu, 20 Sep 2012 08:57:54 +0000 X-Env-Sender: dion@concero.nl X-Msg-Ref: server-15.tower-217.messagelabs.com!1348131473!16058752!1 X-Originating-IP: [80.101.154.29] X-SpamReason: No, hits=0.0 required=7.0 tests= X-StarScan-Received: X-StarScan-Version: 6.6.1.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 2073 invoked from network); 20 Sep 2012 08:57:54 -0000 Received: from concero.xs4all.nl (HELO buri.noordwolde.concero.nl) (80.101.154.29) by server-15.tower-217.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 20 Sep 2012 08:57:54 -0000 Received: from cygnus.noordwolde.concero.nl (192871200.nfra.nl [192.87.1.200]) (authenticated bits=0) by buri.noordwolde.concero.nl (8.13.4/8.13.4/SuSE Linux 0.7) with ESMTP id q8K8vqJk002529 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for ; Thu, 20 Sep 2012 10:57:53 +0200 Message-ID: <505ADA90.2000609@concero.nl> Date: Thu, 20 Sep 2012 10:57:52 +0200 From: Dion Kant Organization: CONCERO User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.2.20) Gecko/20110804 SUSE/3.1.12 Thunderbird/3.1.12 MIME-Version: 1.0 To: "xen-users@lists.xen.org" X-Enigmail-Version: 1.1.2 Subject: [Xen-users] GPLPV Disk performance block device vs. file based backend X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org Dear all, I have two Windows 2008 VMs with latest gplpv drivers installed. One is based on a file container name="wsrv-file" disk=[ 'file:/var/lib/xen/images/wsrv-file/disk0.raw,xvda,w', ] and the other one is based on a block device. name="wsrv-bd" disk=[ 'phy:/dev/vg0/wsrv-bd,xvda,w', ] The block device represents a logical volume consisting of 4 disks and is configured with 4 stripes. The file lives on another logical volume in the same volume group and is formatted with XFS. Now I measure more than a factor 3 better I/O performance on the file based VM as compared to the block device based VM. I don't think it is a cache issue which is tricking me. Details of my test and setup are given below. Hardware: Supermicro X8DTU 2x CPU E5620 RAM 12 GB (6x2GB DIMM) Disks: 4x 2TB Controller (Adaptec) SMC AOC-USAS-S4i (driver: aacraid) Disk setup JBOD Software: openSuSE 12.2 x86_64 distribution00000 kernel: 3.4.6-2.10-xen Xen: 4.1.3_01-5.6.200000 dom0 lives on a 80 GB RAID10 at the outside of the disks, the remaining partitions are directly (no raid) to a volume group. The VM disks live on logical volumes in that volume group. Both Windows VMs are similar Windows Server 2008 R2 Enterprise all updates installed. They are assigned 4 cpus (no pinning) and 4 GB RAM. Test setup: When running a test, only one VM is running, no other things are happening (just the test) . Installed Cygwin and use dd for writing to disk: sync; time (dd if=/dev/zero of=test.bin bs=4096 count=5000000; sync) Measured time is used to calculate streaming rate, but this could hide caching in dom0. However, while running the test, in dom0 a vmstat -n 1 is running so the actual write performance to the block devices can be observed in dom0. Note we are not looking for some marginal effect! I noticed that for the file based VM, the "bo" results from vmstat are doubled, i.e. the bytes written to the disk file living on the LV are counted twice. This does not happen for a block device based disk. 00000 block device based: 150 MB/s file based: >450 MB/s I have reproduced this behaviour using previous versions of openSUSE (older Xen) and other Windows versions (XP, 2003). Furthermore I observed this behaviour on other hardware, mostly tested this on Supermicro mother boards. I can provide more details if required and I can do more testing as well. Regards, Dion _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Thu Sep 20 08:59:02 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Thu, 20 Sep 2012 08:59:02 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TEca6-0003yt-0I; Thu, 20 Sep 2012 08:57:58 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TEca3-0003yQ-Kp for xen-users@lists.xen.org; Thu, 20 Sep 2012 08:57:55 +0000 Received: from [85.158.137.99:19967] by server-12.bemta-3.messagelabs.com id F2/E1-10384-29ADA505; Thu, 20 Sep 2012 08:57:54 +0000 X-Env-Sender: dion@concero.nl X-Msg-Ref: server-15.tower-217.messagelabs.com!1348131473!16058752!1 X-Originating-IP: [80.101.154.29] X-SpamReason: No, hits=0.0 required=7.0 tests= X-StarScan-Received: X-StarScan-Version: 6.6.1.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 2073 invoked from network); 20 Sep 2012 08:57:54 -0000 Received: from concero.xs4all.nl (HELO buri.noordwolde.concero.nl) (80.101.154.29) by server-15.tower-217.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 20 Sep 2012 08:57:54 -0000 Received: from cygnus.noordwolde.concero.nl (192871200.nfra.nl [192.87.1.200]) (authenticated bits=0) by buri.noordwolde.concero.nl (8.13.4/8.13.4/SuSE Linux 0.7) with ESMTP id q8K8vqJk002529 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for ; Thu, 20 Sep 2012 10:57:53 +0200 Message-ID: <505ADA90.2000609@concero.nl> Date: Thu, 20 Sep 2012 10:57:52 +0200 From: Dion Kant Organization: CONCERO User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.2.20) Gecko/20110804 SUSE/3.1.12 Thunderbird/3.1.12 MIME-Version: 1.0 To: "xen-users@lists.xen.org" X-Enigmail-Version: 1.1.2 Subject: [Xen-users] GPLPV Disk performance block device vs. file based backend X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org Dear all, I have two Windows 2008 VMs with latest gplpv drivers installed. One is based on a file container name="wsrv-file" disk=[ 'file:/var/lib/xen/images/wsrv-file/disk0.raw,xvda,w', ] and the other one is based on a block device. name="wsrv-bd" disk=[ 'phy:/dev/vg0/wsrv-bd,xvda,w', ] The block device represents a logical volume consisting of 4 disks and is configured with 4 stripes. The file lives on another logical volume in the same volume group and is formatted with XFS. Now I measure more than a factor 3 better I/O performance on the file based VM as compared to the block device based VM. I don't think it is a cache issue which is tricking me. Details of my test and setup are given below. Hardware: Supermicro X8DTU 2x CPU E5620 RAM 12 GB (6x2GB DIMM) Disks: 4x 2TB Controller (Adaptec) SMC AOC-USAS-S4i (driver: aacraid) Disk setup JBOD Software: openSuSE 12.2 x86_64 distribution00000 kernel: 3.4.6-2.10-xen Xen: 4.1.3_01-5.6.200000 dom0 lives on a 80 GB RAID10 at the outside of the disks, the remaining partitions are directly (no raid) to a volume group. The VM disks live on logical volumes in that volume group. Both Windows VMs are similar Windows Server 2008 R2 Enterprise all updates installed. They are assigned 4 cpus (no pinning) and 4 GB RAM. Test setup: When running a test, only one VM is running, no other things are happening (just the test) . Installed Cygwin and use dd for writing to disk: sync; time (dd if=/dev/zero of=test.bin bs=4096 count=5000000; sync) Measured time is used to calculate streaming rate, but this could hide caching in dom0. However, while running the test, in dom0 a vmstat -n 1 is running so the actual write performance to the block devices can be observed in dom0. Note we are not looking for some marginal effect! I noticed that for the file based VM, the "bo" results from vmstat are doubled, i.e. the bytes written to the disk file living on the LV are counted twice. This does not happen for a block device based disk. 00000 block device based: 150 MB/s file based: >450 MB/s I have reproduced this behaviour using previous versions of openSUSE (older Xen) and other Windows versions (XP, 2003). Furthermore I observed this behaviour on other hardware, mostly tested this on Supermicro mother boards. I can provide more details if required and I can do more testing as well. Regards, Dion _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Thu Sep 20 10:18:13 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Thu, 20 Sep 2012 10:18:13 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TEdoa-0006jp-Py; Thu, 20 Sep 2012 10:17:00 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TEdoZ-0006jk-S6 for xen-users@lists.xen.org; Thu, 20 Sep 2012 10:17:00 +0000 Received: from [85.158.143.35:60681] by server-3.bemta-4.messagelabs.com id 68/E5-10986-B1DEA505; Thu, 20 Sep 2012 10:16:59 +0000 X-Env-Sender: fajar@fajar.net X-Msg-Ref: server-16.tower-21.messagelabs.com!1348136213!16633505!1 X-Originating-IP: [209.85.219.45] X-SpamReason: No, hits=0.3 required=7.0 tests=RCVD_BY_IP X-StarScan-Received: X-StarScan-Version: 6.6.1.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 28677 invoked from network); 20 Sep 2012 10:16:54 -0000 Received: from mail-oa0-f45.google.com (HELO mail-oa0-f45.google.com) (209.85.219.45) by server-16.tower-21.messagelabs.com with RC4-SHA encrypted SMTP; 20 Sep 2012 10:16:54 -0000 Received: by oagn12 with SMTP id n12so2515054oag.32 for ; Thu, 20 Sep 2012 03:16:53 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:x-gm-message-state; bh=5qpZXiqXYA3lzP0PXFa3rkUL0x/mio2kllLmU5WGtEc=; b=lqd9R6bpOnWSeM9p40j77j3MJVcowLSttXTKul4tAPkUsU3IhN2S7LE7VEg+Tq6+Bs q0JBvSNMvBDTtFLS3ZSInl2lNniV8SiTGoHcVLSc48T2F+AO+4/bLXEJGOgIjs/B3dQH ACxTbcu+pm+p2ALP+yZB/gKpLjdTstZ0Ep68jGggAUDUO983guG6HVph25kiIjo7eB1S gW/iOk9Y7MIqGPgXasE1XLiZHgWINsswiikRI6J8hdbBp9I3Vi3E1LCgf8zsCHkr3aty kUEXCEpHIHu6c2qNcreiYTSVUej+mtMW7OTR5ukfycPt4vEJWL1BoITi0a/0vQZnQ2VP b03g== MIME-Version: 1.0 Received: by 10.182.10.71 with SMTP id g7mr883168obb.84.1348136213070; Thu, 20 Sep 2012 03:16:53 -0700 (PDT) Received: by 10.60.6.230 with HTTP; Thu, 20 Sep 2012 03:16:53 -0700 (PDT) In-Reply-To: <505ADA90.2000609@concero.nl> References: <505ADA90.2000609@concero.nl> Date: Thu, 20 Sep 2012 17:16:53 +0700 Message-ID: From: "Fajar A. Nugraha" To: Dion Kant X-Gm-Message-State: ALoCoQmxD08/m/f/WFvVXp5bNiuOtKVrd6WK5gnBmxERsplJ1p4NGhPgsEaQl+BJeXezV5+Iftzh Cc: "xen-users@lists.xen.org" Subject: Re: [Xen-users] GPLPV Disk performance block device vs. file based backend X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org On Thu, Sep 20, 2012 at 3:57 PM, Dion Kant wrote: > name="wsrv-file" > disk=[ 'file:/var/lib/xen/images/wsrv-file/disk0.raw,xvda,w', ] > name="wsrv-bd" > disk=[ 'phy:/dev/vg0/wsrv-bd,xvda,w', ] > Now I measure more than a factor 3 better I/O performance on the file > based VM as compared to the block device based VM. I don't think it is a > cache issue which is tricking me. I'm 99.9% sure it tricks you :) > sync; time (dd if=/dev/zero of=test.bin bs=4096 count=5000000; sync) dd is terrible for benchmark purposes. I'd suggest fio, random rw, data size at least twice RAM. > I noticed that for the file based VM, the "bo" results from vmstat are > doubled, i.e. the bytes written to the disk file living on the LV are > counted twice. probably because file:/ uses loopback, which is counted as another block device. > I can provide more details if required and I can do more testing as well. There are many factors involved: file vs phy, file-backed vs LV-backed, windows, gplpv, etc. What I suggest is: - use linux pv domU, one backed with LV, the other with file - use tap:aio for the file-backed one (NOT file:/) - use fio for testing That SHOULD eliminate most other factors, and allow you to focus on file-tap vs LV-phy. -- Fajar _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Thu Sep 20 10:18:13 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Thu, 20 Sep 2012 10:18:13 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TEdoa-0006jp-Py; Thu, 20 Sep 2012 10:17:00 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TEdoZ-0006jk-S6 for xen-users@lists.xen.org; Thu, 20 Sep 2012 10:17:00 +0000 Received: from [85.158.143.35:60681] by server-3.bemta-4.messagelabs.com id 68/E5-10986-B1DEA505; Thu, 20 Sep 2012 10:16:59 +0000 X-Env-Sender: fajar@fajar.net X-Msg-Ref: server-16.tower-21.messagelabs.com!1348136213!16633505!1 X-Originating-IP: [209.85.219.45] X-SpamReason: No, hits=0.3 required=7.0 tests=RCVD_BY_IP X-StarScan-Received: X-StarScan-Version: 6.6.1.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 28677 invoked from network); 20 Sep 2012 10:16:54 -0000 Received: from mail-oa0-f45.google.com (HELO mail-oa0-f45.google.com) (209.85.219.45) by server-16.tower-21.messagelabs.com with RC4-SHA encrypted SMTP; 20 Sep 2012 10:16:54 -0000 Received: by oagn12 with SMTP id n12so2515054oag.32 for ; Thu, 20 Sep 2012 03:16:53 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:x-gm-message-state; bh=5qpZXiqXYA3lzP0PXFa3rkUL0x/mio2kllLmU5WGtEc=; b=lqd9R6bpOnWSeM9p40j77j3MJVcowLSttXTKul4tAPkUsU3IhN2S7LE7VEg+Tq6+Bs q0JBvSNMvBDTtFLS3ZSInl2lNniV8SiTGoHcVLSc48T2F+AO+4/bLXEJGOgIjs/B3dQH ACxTbcu+pm+p2ALP+yZB/gKpLjdTstZ0Ep68jGggAUDUO983guG6HVph25kiIjo7eB1S gW/iOk9Y7MIqGPgXasE1XLiZHgWINsswiikRI6J8hdbBp9I3Vi3E1LCgf8zsCHkr3aty kUEXCEpHIHu6c2qNcreiYTSVUej+mtMW7OTR5ukfycPt4vEJWL1BoITi0a/0vQZnQ2VP b03g== MIME-Version: 1.0 Received: by 10.182.10.71 with SMTP id g7mr883168obb.84.1348136213070; Thu, 20 Sep 2012 03:16:53 -0700 (PDT) Received: by 10.60.6.230 with HTTP; Thu, 20 Sep 2012 03:16:53 -0700 (PDT) In-Reply-To: <505ADA90.2000609@concero.nl> References: <505ADA90.2000609@concero.nl> Date: Thu, 20 Sep 2012 17:16:53 +0700 Message-ID: From: "Fajar A. Nugraha" To: Dion Kant X-Gm-Message-State: ALoCoQmxD08/m/f/WFvVXp5bNiuOtKVrd6WK5gnBmxERsplJ1p4NGhPgsEaQl+BJeXezV5+Iftzh Cc: "xen-users@lists.xen.org" Subject: Re: [Xen-users] GPLPV Disk performance block device vs. file based backend X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org On Thu, Sep 20, 2012 at 3:57 PM, Dion Kant wrote: > name="wsrv-file" > disk=[ 'file:/var/lib/xen/images/wsrv-file/disk0.raw,xvda,w', ] > name="wsrv-bd" > disk=[ 'phy:/dev/vg0/wsrv-bd,xvda,w', ] > Now I measure more than a factor 3 better I/O performance on the file > based VM as compared to the block device based VM. I don't think it is a > cache issue which is tricking me. I'm 99.9% sure it tricks you :) > sync; time (dd if=/dev/zero of=test.bin bs=4096 count=5000000; sync) dd is terrible for benchmark purposes. I'd suggest fio, random rw, data size at least twice RAM. > I noticed that for the file based VM, the "bo" results from vmstat are > doubled, i.e. the bytes written to the disk file living on the LV are > counted twice. probably because file:/ uses loopback, which is counted as another block device. > I can provide more details if required and I can do more testing as well. There are many factors involved: file vs phy, file-backed vs LV-backed, windows, gplpv, etc. What I suggest is: - use linux pv domU, one backed with LV, the other with file - use tap:aio for the file-backed one (NOT file:/) - use fio for testing That SHOULD eliminate most other factors, and allow you to focus on file-tap vs LV-phy. -- Fajar _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Thu Sep 20 11:32:12 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Thu, 20 Sep 2012 11:32:12 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TEeyI-0001sU-Lp; Thu, 20 Sep 2012 11:31:06 +0000 Received: from mail27.messagelabs.com ([193.109.254.147]) by lists.xen.org with smtp (Exim 4.72) (envelope-from ) id 1TEcLD-00036s-Q7 for xen-users@lists.xen.org; Thu, 20 Sep 2012 08:42:36 +0000 X-Env-Sender: Artem.Metra@gmx.de X-Msg-Ref: server-14.tower-27.messagelabs.com!1348130548!4720128!1 X-Originating-IP: [213.165.64.22] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: QmFkIElQOiAyMTMuMTY1LjY0LjIyID0+IDI1MzEzMA==\n,sa_preprocessor: QmFkIElQOiAyMTMuMTY1LjY0LjIyID0+IDI1MzEzMA==\n, ML_RADAR_SPEW_LINKS_14, spamassassin: X-StarScan-Received: X-StarScan-Version: 6.6.1.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 5137 invoked from network); 20 Sep 2012 08:42:28 -0000 Received: from mailout-de.gmx.net (HELO mailout-de.gmx.net) (213.165.64.22) by server-14.tower-27.messagelabs.com with SMTP; 20 Sep 2012 08:42:28 -0000 Received: (qmail 21839 invoked by uid 0); 20 Sep 2012 08:42:28 -0000 Received: from 129.217.43.51 by www014.gmx.net with HTTP; Thu, 20 Sep 2012 10:42:27 +0200 (CEST) Date: Thu, 20 Sep 2012 10:42:27 +0200 From: "Artem Metra" Message-ID: <20120920084227.97760@gmx.net> MIME-Version: 1.0 To: xen-users@lists.xen.org X-Authenticated: #142584949 X-Flags: 0001 X-Mailer: WWW-Mail 6100 (Global Message Exchange) X-Priority: 3 X-Provags-ID: V01U2FsdGVkX1+/ydhxrpW/oaPPA9MXCZ3PfueCUO/wgoezpwOMhn +SzNBJFQ1Ffw2btiH59bKVhcD1oT7+sDz80Q== X-GMX-UID: pLMocFRHeSEqaBTPFHwhpwl+IGRvb4BV X-Mailman-Approved-At: Thu, 20 Sep 2012 11:31:03 +0000 Subject: [Xen-users] Xen 4.2 and Remus X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org Hallo, I have a small question about remus in xen 4.2. I'm working with Debian as dom0 system. When I start a guest everything works fine. When I activate remus with the follwing command: xl remus 5 192.168.0.123 the following error occurs: xc: error: read_exact_timed failed (read rc: 0, errno: 0): Internal error xc: error: Error when reading batch size (0 = Success): Internal error xc: error: error when buffering batch, finishing (0 = Success): Internal error migration target: Remus Failover for domain 5 Does somebody know a solution or can tell me whats the problem is? Best regards Artem _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Thu Sep 20 11:32:12 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Thu, 20 Sep 2012 11:32:12 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TEeyI-0001sU-Lp; Thu, 20 Sep 2012 11:31:06 +0000 Received: from mail27.messagelabs.com ([193.109.254.147]) by lists.xen.org with smtp (Exim 4.72) (envelope-from ) id 1TEcLD-00036s-Q7 for xen-users@lists.xen.org; Thu, 20 Sep 2012 08:42:36 +0000 X-Env-Sender: Artem.Metra@gmx.de X-Msg-Ref: server-14.tower-27.messagelabs.com!1348130548!4720128!1 X-Originating-IP: [213.165.64.22] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: QmFkIElQOiAyMTMuMTY1LjY0LjIyID0+IDI1MzEzMA==\n,sa_preprocessor: QmFkIElQOiAyMTMuMTY1LjY0LjIyID0+IDI1MzEzMA==\n, ML_RADAR_SPEW_LINKS_14, spamassassin: X-StarScan-Received: X-StarScan-Version: 6.6.1.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 5137 invoked from network); 20 Sep 2012 08:42:28 -0000 Received: from mailout-de.gmx.net (HELO mailout-de.gmx.net) (213.165.64.22) by server-14.tower-27.messagelabs.com with SMTP; 20 Sep 2012 08:42:28 -0000 Received: (qmail 21839 invoked by uid 0); 20 Sep 2012 08:42:28 -0000 Received: from 129.217.43.51 by www014.gmx.net with HTTP; Thu, 20 Sep 2012 10:42:27 +0200 (CEST) Date: Thu, 20 Sep 2012 10:42:27 +0200 From: "Artem Metra" Message-ID: <20120920084227.97760@gmx.net> MIME-Version: 1.0 To: xen-users@lists.xen.org X-Authenticated: #142584949 X-Flags: 0001 X-Mailer: WWW-Mail 6100 (Global Message Exchange) X-Priority: 3 X-Provags-ID: V01U2FsdGVkX1+/ydhxrpW/oaPPA9MXCZ3PfueCUO/wgoezpwOMhn +SzNBJFQ1Ffw2btiH59bKVhcD1oT7+sDz80Q== X-GMX-UID: pLMocFRHeSEqaBTPFHwhpwl+IGRvb4BV X-Mailman-Approved-At: Thu, 20 Sep 2012 11:31:03 +0000 Subject: [Xen-users] Xen 4.2 and Remus X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org Hallo, I have a small question about remus in xen 4.2. I'm working with Debian as dom0 system. When I start a guest everything works fine. When I activate remus with the follwing command: xl remus 5 192.168.0.123 the following error occurs: xc: error: read_exact_timed failed (read rc: 0, errno: 0): Internal error xc: error: Error when reading batch size (0 = Success): Internal error xc: error: error when buffering batch, finishing (0 = Success): Internal error migration target: Remus Failover for domain 5 Does somebody know a solution or can tell me whats the problem is? Best regards Artem _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Thu Sep 20 12:43:38 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Thu, 20 Sep 2012 12:43:38 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TEg5M-00065V-86; Thu, 20 Sep 2012 12:42:28 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TEg5K-00065N-CF for xen-users@lists.xen.org; Thu, 20 Sep 2012 12:42:26 +0000 Received: from [85.158.143.35:22140] by server-2.bemta-4.messagelabs.com id 62/32-06610-13F0B505; Thu, 20 Sep 2012 12:42:25 +0000 X-Env-Sender: james.harper@bendigoit.com.au X-Msg-Ref: server-6.tower-21.messagelabs.com!1348144941!19131595!1 X-Originating-IP: [203.16.224.4] X-SpamReason: No, hits=0.0 required=7.0 tests= X-StarScan-Received: X-StarScan-Version: 6.6.1.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 14726 invoked from network); 20 Sep 2012 12:42:24 -0000 Received: from smtp1.bendigoit.com.au (HELO smtp1.bendigoit.com.au) (203.16.224.4) by server-6.tower-21.messagelabs.com with AES256-SHA encrypted SMTP; 20 Sep 2012 12:42:24 -0000 Received: from [2001:388:e000:712:a5ca:4fd3:14f:ad5d] (helo=BITCOM1.int.sbss.com.au) by smtp1.bendigoit.com.au with esmtp (Exim 4.69) (envelope-from ) id 1TEg5A-0007Tw-TL; Thu, 20 Sep 2012 22:42:17 +1000 Received: from BITCOM1.int.sbss.com.au ([fe80::a5ca:4fd3:14f:ad5d]) by BITCOM1.int.sbss.com.au ([fe80::a5ca:4fd3:14f:ad5d%12]) with mapi id 14.01.0379.000; Thu, 20 Sep 2012 22:42:17 +1000 From: James Harper To: Adam Goryachev Thread-Topic: [Xen-users] SOLVED - Poor Windows 2003 + GPLPV performance compared to VMWare Thread-Index: AQHNlmI3pGsFoFq0f0aiFBIRZwZ93peRn3xg//9c24CAAjFQgA== Date: Thu, 20 Sep 2012 12:42:15 +0000 Message-ID: <6035A0D088A63A46850C3988ED045A4B29BAB8A0@BITCOM1.int.sbss.com.au> References: <5051D0C5.5070600@websitemanagers.com.au> <1347609879.24226.148.camel@zakaz.uk.xensource.com> <50532CE9.5080601@websitemanagers.com.au> <1347629416.24226.208.camel@zakaz.uk.xensource.com> <505344E8.2030400@websitemanagers.com.au> <505871D6.2060801@websitemanagers.com.au> <1348044096.14977.84.camel@zakaz.uk.xensource.com> <505993A6.2080804@websitemanagers.com.au> <5059B853.9030903@websitemanagers.com.au> <1348057647.14977.104.camel@zakaz.uk.xensource.com> <6035A0D088A63A46850C3988ED045A4B29BA8C0B@BITCOM1.int.sbss.com.au> <5059C4A9.2060403@websitemanagers.com.au> In-Reply-To: <5059C4A9.2060403@websitemanagers.com.au> Accept-Language: en-AU, en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [172.16.3.132] x-tm-as-product-ver: SMEX-10.2.0.2087-7.000.1014-19196.002 x-tm-as-result: No--26.742100-0.000000-31 x-tm-as-user-approved-sender: Yes x-tm-as-user-blocked-sender: No MIME-Version: 1.0 X-Really-From-Bendigo-IT: magichashvalue Cc: "xen-users@lists.xen.org" , Ian Campbell Subject: Re: [Xen-users] SOLVED - Poor Windows 2003 + GPLPV performance compared to VMWare X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org > > I thought Xen optimised this for Intel though and my patching wasn't > necessary anymore? Or maybe the OP is running a version of xen that > doesn't have that feature?? > So Xen is patched only for Intel, and therefore I missed out again since I am > on AMD, or my xen doesn't have this feature. > xen_major : 4 > xen_minor : 1 > xen_extra : .3 > With 2003 sp2, none of the optimisation is necessary as 2003sp2 doesn't use the TPR at all. James _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Thu Sep 20 12:43:38 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Thu, 20 Sep 2012 12:43:38 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TEg5M-00065V-86; Thu, 20 Sep 2012 12:42:28 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TEg5K-00065N-CF for xen-users@lists.xen.org; Thu, 20 Sep 2012 12:42:26 +0000 Received: from [85.158.143.35:22140] by server-2.bemta-4.messagelabs.com id 62/32-06610-13F0B505; Thu, 20 Sep 2012 12:42:25 +0000 X-Env-Sender: james.harper@bendigoit.com.au X-Msg-Ref: server-6.tower-21.messagelabs.com!1348144941!19131595!1 X-Originating-IP: [203.16.224.4] X-SpamReason: No, hits=0.0 required=7.0 tests= X-StarScan-Received: X-StarScan-Version: 6.6.1.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 14726 invoked from network); 20 Sep 2012 12:42:24 -0000 Received: from smtp1.bendigoit.com.au (HELO smtp1.bendigoit.com.au) (203.16.224.4) by server-6.tower-21.messagelabs.com with AES256-SHA encrypted SMTP; 20 Sep 2012 12:42:24 -0000 Received: from [2001:388:e000:712:a5ca:4fd3:14f:ad5d] (helo=BITCOM1.int.sbss.com.au) by smtp1.bendigoit.com.au with esmtp (Exim 4.69) (envelope-from ) id 1TEg5A-0007Tw-TL; Thu, 20 Sep 2012 22:42:17 +1000 Received: from BITCOM1.int.sbss.com.au ([fe80::a5ca:4fd3:14f:ad5d]) by BITCOM1.int.sbss.com.au ([fe80::a5ca:4fd3:14f:ad5d%12]) with mapi id 14.01.0379.000; Thu, 20 Sep 2012 22:42:17 +1000 From: James Harper To: Adam Goryachev Thread-Topic: [Xen-users] SOLVED - Poor Windows 2003 + GPLPV performance compared to VMWare Thread-Index: AQHNlmI3pGsFoFq0f0aiFBIRZwZ93peRn3xg//9c24CAAjFQgA== Date: Thu, 20 Sep 2012 12:42:15 +0000 Message-ID: <6035A0D088A63A46850C3988ED045A4B29BAB8A0@BITCOM1.int.sbss.com.au> References: <5051D0C5.5070600@websitemanagers.com.au> <1347609879.24226.148.camel@zakaz.uk.xensource.com> <50532CE9.5080601@websitemanagers.com.au> <1347629416.24226.208.camel@zakaz.uk.xensource.com> <505344E8.2030400@websitemanagers.com.au> <505871D6.2060801@websitemanagers.com.au> <1348044096.14977.84.camel@zakaz.uk.xensource.com> <505993A6.2080804@websitemanagers.com.au> <5059B853.9030903@websitemanagers.com.au> <1348057647.14977.104.camel@zakaz.uk.xensource.com> <6035A0D088A63A46850C3988ED045A4B29BA8C0B@BITCOM1.int.sbss.com.au> <5059C4A9.2060403@websitemanagers.com.au> In-Reply-To: <5059C4A9.2060403@websitemanagers.com.au> Accept-Language: en-AU, en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [172.16.3.132] x-tm-as-product-ver: SMEX-10.2.0.2087-7.000.1014-19196.002 x-tm-as-result: No--26.742100-0.000000-31 x-tm-as-user-approved-sender: Yes x-tm-as-user-blocked-sender: No MIME-Version: 1.0 X-Really-From-Bendigo-IT: magichashvalue Cc: "xen-users@lists.xen.org" , Ian Campbell Subject: Re: [Xen-users] SOLVED - Poor Windows 2003 + GPLPV performance compared to VMWare X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org > > I thought Xen optimised this for Intel though and my patching wasn't > necessary anymore? Or maybe the OP is running a version of xen that > doesn't have that feature?? > So Xen is patched only for Intel, and therefore I missed out again since I am > on AMD, or my xen doesn't have this feature. > xen_major : 4 > xen_minor : 1 > xen_extra : .3 > With 2003 sp2, none of the optimisation is necessary as 2003sp2 doesn't use the TPR at all. James _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Thu Sep 20 14:17:57 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Thu, 20 Sep 2012 14:17:57 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TEhYa-0001Po-AY; Thu, 20 Sep 2012 14:16:44 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TEhYZ-0001Pd-5v for xen-users@lists.xen.org; Thu, 20 Sep 2012 14:16:43 +0000 Received: from [85.158.137.99:39646] by server-12.bemta-3.messagelabs.com id 44/B8-10384-A452B505; Thu, 20 Sep 2012 14:16:42 +0000 X-Env-Sender: dion@concero.nl X-Msg-Ref: server-12.tower-217.messagelabs.com!1348150601!15349436!1 X-Originating-IP: [80.101.154.29] X-SpamReason: No, hits=0.0 required=7.0 tests= X-StarScan-Received: X-StarScan-Version: 6.6.1.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 10188 invoked from network); 20 Sep 2012 14:16:41 -0000 Received: from concero.xs4all.nl (HELO buri.noordwolde.concero.nl) (80.101.154.29) by server-12.tower-217.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 20 Sep 2012 14:16:41 -0000 Received: from cygnus.noordwolde.concero.nl (192871200.nfra.nl [192.87.1.200]) (authenticated bits=0) by buri.noordwolde.concero.nl (8.13.4/8.13.4/SuSE Linux 0.7) with ESMTP id q8KEGd3Q006086 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 20 Sep 2012 16:16:39 +0200 Message-ID: <505B2547.2050401@concero.nl> Date: Thu, 20 Sep 2012 16:16:39 +0200 From: Dion Kant Organization: CONCERO User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.2.20) Gecko/20110804 SUSE/3.1.12 Thunderbird/3.1.12 MIME-Version: 1.0 To: "Fajar A. Nugraha" References: <505ADA90.2000609@concero.nl> In-Reply-To: X-Enigmail-Version: 1.1.2 Cc: "xen-users@lists.xen.org" Subject: Re: [Xen-users] GPLPV Disk performance block device vs. file based backend X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org On 09/20/2012 12:16 PM, Fajar A. Nugraha wrote: > On Thu, Sep 20, 2012 at 3:57 PM, Dion Kant wrote: > > >> Now I measure more than a factor 3 better I/O performance on the file >> based VM as compared to the block device based VM. I don't think it is a >> cache issue which is tricking me. > I'm 99.9% sure it tricks you :) Hi Fajar, Thank you for leaving me 0.01% of uncertainty ;) >> sync; time (dd if=/dev/zero of=test.bin bs=4096 count=5000000; sync) > dd is terrible for benchmark purposes. I'd suggest fio, random rw, > data size at least twice RAM. I don't care about random rw, I am looking at the speed of which nicely ordered data is streamed to a set of disks, observed with vmstat in dom0. Note I write 20GB, so I have plenty time to make sure that all caches are filled in dom0 and writing to the disks has to start. There is 8 GB in dom0 left, furthermore the sync of Cygwin really does its job. I'll have a look at fio anyway..... >> I noticed that for the file based VM, the "bo" results from vmstat are >> doubled, i.e. the bytes written to the disk file living on the LV are >> counted twice. > probably because file:/ uses loopback, which is counted as another block device. Ok that shall be the reason. >> I can provide more details if required and I can do more testing as well. > There are many factors involved: file vs phy, file-backed vs > LV-backed, windows, gplpv, etc. What I suggest is: > > - use linux pv domU, one backed with LV, the other with file > - use tap:aio for the file-backed one (NOT file:/) > - use fio for testing > > That SHOULD eliminate most other factors, and allow you to focus on > file-tap vs LV-phy. I don't have this issue with Linux PV domUs. I think it is something related to GPLPV or HVM. I'll do this anyway again and report on the results. If I recall correctly from my tests in the past with PV Linux, using phy: tap:aio or file: only differs a little bit (<10%). Here we are talking about a factor >3. Thanks, Dion _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Thu Sep 20 14:17:57 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Thu, 20 Sep 2012 14:17:57 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TEhYa-0001Po-AY; Thu, 20 Sep 2012 14:16:44 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TEhYZ-0001Pd-5v for xen-users@lists.xen.org; Thu, 20 Sep 2012 14:16:43 +0000 Received: from [85.158.137.99:39646] by server-12.bemta-3.messagelabs.com id 44/B8-10384-A452B505; Thu, 20 Sep 2012 14:16:42 +0000 X-Env-Sender: dion@concero.nl X-Msg-Ref: server-12.tower-217.messagelabs.com!1348150601!15349436!1 X-Originating-IP: [80.101.154.29] X-SpamReason: No, hits=0.0 required=7.0 tests= X-StarScan-Received: X-StarScan-Version: 6.6.1.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 10188 invoked from network); 20 Sep 2012 14:16:41 -0000 Received: from concero.xs4all.nl (HELO buri.noordwolde.concero.nl) (80.101.154.29) by server-12.tower-217.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 20 Sep 2012 14:16:41 -0000 Received: from cygnus.noordwolde.concero.nl (192871200.nfra.nl [192.87.1.200]) (authenticated bits=0) by buri.noordwolde.concero.nl (8.13.4/8.13.4/SuSE Linux 0.7) with ESMTP id q8KEGd3Q006086 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 20 Sep 2012 16:16:39 +0200 Message-ID: <505B2547.2050401@concero.nl> Date: Thu, 20 Sep 2012 16:16:39 +0200 From: Dion Kant Organization: CONCERO User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.2.20) Gecko/20110804 SUSE/3.1.12 Thunderbird/3.1.12 MIME-Version: 1.0 To: "Fajar A. Nugraha" References: <505ADA90.2000609@concero.nl> In-Reply-To: X-Enigmail-Version: 1.1.2 Cc: "xen-users@lists.xen.org" Subject: Re: [Xen-users] GPLPV Disk performance block device vs. file based backend X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org On 09/20/2012 12:16 PM, Fajar A. Nugraha wrote: > On Thu, Sep 20, 2012 at 3:57 PM, Dion Kant wrote: > > >> Now I measure more than a factor 3 better I/O performance on the file >> based VM as compared to the block device based VM. I don't think it is a >> cache issue which is tricking me. > I'm 99.9% sure it tricks you :) Hi Fajar, Thank you for leaving me 0.01% of uncertainty ;) >> sync; time (dd if=/dev/zero of=test.bin bs=4096 count=5000000; sync) > dd is terrible for benchmark purposes. I'd suggest fio, random rw, > data size at least twice RAM. I don't care about random rw, I am looking at the speed of which nicely ordered data is streamed to a set of disks, observed with vmstat in dom0. Note I write 20GB, so I have plenty time to make sure that all caches are filled in dom0 and writing to the disks has to start. There is 8 GB in dom0 left, furthermore the sync of Cygwin really does its job. I'll have a look at fio anyway..... >> I noticed that for the file based VM, the "bo" results from vmstat are >> doubled, i.e. the bytes written to the disk file living on the LV are >> counted twice. > probably because file:/ uses loopback, which is counted as another block device. Ok that shall be the reason. >> I can provide more details if required and I can do more testing as well. > There are many factors involved: file vs phy, file-backed vs > LV-backed, windows, gplpv, etc. What I suggest is: > > - use linux pv domU, one backed with LV, the other with file > - use tap:aio for the file-backed one (NOT file:/) > - use fio for testing > > That SHOULD eliminate most other factors, and allow you to focus on > file-tap vs LV-phy. I don't have this issue with Linux PV domUs. I think it is something related to GPLPV or HVM. I'll do this anyway again and report on the results. If I recall correctly from my tests in the past with PV Linux, using phy: tap:aio or file: only differs a little bit (<10%). Here we are talking about a factor >3. Thanks, Dion _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Thu Sep 20 15:47:48 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Thu, 20 Sep 2012 15:47:48 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TEixX-0003aU-B4; Thu, 20 Sep 2012 15:46:35 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TEilc-0002yU-MQ for xen-users@lists.xen.org; Thu, 20 Sep 2012 15:34:16 +0000 Received: from [85.158.139.211:17274] by server-6.bemta-5.messagelabs.com id 7D/84-21336-7773B505; Thu, 20 Sep 2012 15:34:15 +0000 X-Env-Sender: kevin.parker092@gmail.com X-Msg-Ref: server-15.tower-206.messagelabs.com!1348155253!19395672!1 X-Originating-IP: [209.85.223.173] X-SpamReason: No, hits=0.3 required=7.0 tests=HTML_MESSAGE, ML_RADAR_SPEW_LINKS_14,RCVD_BY_IP,spamassassin: X-StarScan-Received: X-StarScan-Version: 6.6.1.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 29356 invoked from network); 20 Sep 2012 15:34:14 -0000 Received: from mail-ie0-f173.google.com (HELO mail-ie0-f173.google.com) (209.85.223.173) by server-15.tower-206.messagelabs.com with RC4-SHA encrypted SMTP; 20 Sep 2012 15:34:14 -0000 Received: by iebc10 with SMTP id c10so4646488ieb.32 for ; Thu, 20 Sep 2012 08:34:13 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:date:message-id:subject:from:to:content-type; bh=zyPtYNhIviosu115OklzZArKsDPp/bMtzrXY5tAahjg=; b=AooAk5rpURKHdUUU2CZn7+c3E48rNC5iVhEYwWY1q39hLzL/+gWiGy2hZOOcf57pMN WxDVJaHH/3vFq1m6btGFQh5j3OHu5vTt3z1SruWe34SleV2X8U+g0q1RmqnRzfsQziwP HZY0l9cb7Ws990UR+GrWjydmjY/ekmuz/5UXpyRdj6k5v33bJTOA3U0vuUOJ+25M8IRE ulDZ8N/CQ1UGlgwoT7wBWk5M6ytrx32JE/XTQfl+9YHWnzMmVHOLjUIKT1DQ3GCXZub4 zRTBTfiVZw7QexK4uNufxtO440pOAHp2Uxw/ZNkSXNo8lUwqcbzkLqx96t6vvaniUqyT UZrA== MIME-Version: 1.0 Received: by 10.50.53.199 with SMTP id d7mr1141283igp.47.1348155253267; Thu, 20 Sep 2012 08:34:13 -0700 (PDT) Received: by 10.64.48.163 with HTTP; Thu, 20 Sep 2012 08:34:13 -0700 (PDT) Date: Thu, 20 Sep 2012 21:04:13 +0530 Message-ID: From: kevin parker To: xen-users@lists.xen.org X-Mailman-Approved-At: Thu, 20 Sep 2012 15:46:34 +0000 Subject: [Xen-users] Running Linux VM in para mode with Intel VT enabled X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============3750777965205162439==" Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org --===============3750777965205162439== Content-Type: multipart/alternative; boundary=f46d04339c4cf91c8f04ca23daca --f46d04339c4cf91c8f04ca23daca Content-Type: text/plain; charset=ISO-8859-1 Hi all, I am having a server running XEN,with ubuntu 12.04 as Domain 0. Intel VT is turned on by default and i dont want to run any Windows OS as VM.In that case 1. how can i makesure that all the created VM will be in paravirtualized mode even with VT enabled? I have heard that in Full Virtualization hypervisor needs to work hard for emulating all the underlying hardware,which may reduce performance for too much i/o specific applications when compared to para mode. *2.Can i be able to run Linux VM in para mode with VT enabled? 3.Will simply turning on VT support changes virtualization type from para to full for all vms created on that machine? 4.Will there be any performance improvement for VM running Linux OS if VT is enabled?* *5.Is it normal to miss vmx flag in /proc/cpuinfo after booting to XEN kernel,even with VT enabled?* *Regards,* *Kevin* --f46d04339c4cf91c8f04ca23daca Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Hi all,
=A0 =A0 =A0 =A0=A0I am having a server running XEN,wit= h ubuntu 12.04 as Domain 0.

Intel VT is turned on by default and i dont want to run any Windows OS as V= M.In that case

1. how can i makesure that all the create=
d VM will be in
paravirtualized mode even with VT enabled?

I have heard that in Full Virtualization hypervisor needs to work hard for = emulating all the underlying hardware,which may reduce performance for too = much i/o specific applications when compared to para mode.

2.Can i be able to run Linux VM in par=
a mode with VT enabled?

3.Will simply turning on VT support changes virtualization type from para t=
o full for all vms created on that machine?

4.Will there be any performance improvement for VM running Linux OS if VT i=
s enabled?
5.Is it normal to miss vmx flag in /proc/cpuinfo after booting to XEN ke=
rnel,even with VT enabled?

Regards,
Kevin
--f46d04339c4cf91c8f04ca23daca-- --===============3750777965205162439== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users --===============3750777965205162439==-- From xen-users-bounces@lists.xen.org Thu Sep 20 15:47:48 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Thu, 20 Sep 2012 15:47:48 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TEixX-0003aU-B4; Thu, 20 Sep 2012 15:46:35 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TEilc-0002yU-MQ for xen-users@lists.xen.org; Thu, 20 Sep 2012 15:34:16 +0000 Received: from [85.158.139.211:17274] by server-6.bemta-5.messagelabs.com id 7D/84-21336-7773B505; Thu, 20 Sep 2012 15:34:15 +0000 X-Env-Sender: kevin.parker092@gmail.com X-Msg-Ref: server-15.tower-206.messagelabs.com!1348155253!19395672!1 X-Originating-IP: [209.85.223.173] X-SpamReason: No, hits=0.3 required=7.0 tests=HTML_MESSAGE, ML_RADAR_SPEW_LINKS_14,RCVD_BY_IP,spamassassin: X-StarScan-Received: X-StarScan-Version: 6.6.1.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 29356 invoked from network); 20 Sep 2012 15:34:14 -0000 Received: from mail-ie0-f173.google.com (HELO mail-ie0-f173.google.com) (209.85.223.173) by server-15.tower-206.messagelabs.com with RC4-SHA encrypted SMTP; 20 Sep 2012 15:34:14 -0000 Received: by iebc10 with SMTP id c10so4646488ieb.32 for ; Thu, 20 Sep 2012 08:34:13 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:date:message-id:subject:from:to:content-type; bh=zyPtYNhIviosu115OklzZArKsDPp/bMtzrXY5tAahjg=; b=AooAk5rpURKHdUUU2CZn7+c3E48rNC5iVhEYwWY1q39hLzL/+gWiGy2hZOOcf57pMN WxDVJaHH/3vFq1m6btGFQh5j3OHu5vTt3z1SruWe34SleV2X8U+g0q1RmqnRzfsQziwP HZY0l9cb7Ws990UR+GrWjydmjY/ekmuz/5UXpyRdj6k5v33bJTOA3U0vuUOJ+25M8IRE ulDZ8N/CQ1UGlgwoT7wBWk5M6ytrx32JE/XTQfl+9YHWnzMmVHOLjUIKT1DQ3GCXZub4 zRTBTfiVZw7QexK4uNufxtO440pOAHp2Uxw/ZNkSXNo8lUwqcbzkLqx96t6vvaniUqyT UZrA== MIME-Version: 1.0 Received: by 10.50.53.199 with SMTP id d7mr1141283igp.47.1348155253267; Thu, 20 Sep 2012 08:34:13 -0700 (PDT) Received: by 10.64.48.163 with HTTP; Thu, 20 Sep 2012 08:34:13 -0700 (PDT) Date: Thu, 20 Sep 2012 21:04:13 +0530 Message-ID: From: kevin parker To: xen-users@lists.xen.org X-Mailman-Approved-At: Thu, 20 Sep 2012 15:46:34 +0000 Subject: [Xen-users] Running Linux VM in para mode with Intel VT enabled X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============3750777965205162439==" Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org --===============3750777965205162439== Content-Type: multipart/alternative; boundary=f46d04339c4cf91c8f04ca23daca --f46d04339c4cf91c8f04ca23daca Content-Type: text/plain; charset=ISO-8859-1 Hi all, I am having a server running XEN,with ubuntu 12.04 as Domain 0. Intel VT is turned on by default and i dont want to run any Windows OS as VM.In that case 1. how can i makesure that all the created VM will be in paravirtualized mode even with VT enabled? I have heard that in Full Virtualization hypervisor needs to work hard for emulating all the underlying hardware,which may reduce performance for too much i/o specific applications when compared to para mode. *2.Can i be able to run Linux VM in para mode with VT enabled? 3.Will simply turning on VT support changes virtualization type from para to full for all vms created on that machine? 4.Will there be any performance improvement for VM running Linux OS if VT is enabled?* *5.Is it normal to miss vmx flag in /proc/cpuinfo after booting to XEN kernel,even with VT enabled?* *Regards,* *Kevin* --f46d04339c4cf91c8f04ca23daca Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Hi all,
=A0 =A0 =A0 =A0=A0I am having a server running XEN,wit= h ubuntu 12.04 as Domain 0.

Intel VT is turned on by default and i dont want to run any Windows OS as V= M.In that case

1. how can i makesure that all the create=
d VM will be in
paravirtualized mode even with VT enabled?

I have heard that in Full Virtualization hypervisor needs to work hard for = emulating all the underlying hardware,which may reduce performance for too = much i/o specific applications when compared to para mode.

2.Can i be able to run Linux VM in par=
a mode with VT enabled?

3.Will simply turning on VT support changes virtualization type from para t=
o full for all vms created on that machine?

4.Will there be any performance improvement for VM running Linux OS if VT i=
s enabled?
5.Is it normal to miss vmx flag in /proc/cpuinfo after booting to XEN ke=
rnel,even with VT enabled?

Regards,
Kevin
--f46d04339c4cf91c8f04ca23daca-- --===============3750777965205162439== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users --===============3750777965205162439==-- From xen-users-bounces@lists.xen.org Thu Sep 20 15:59:36 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Thu, 20 Sep 2012 15:59:36 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TEj99-0004Mz-8x; Thu, 20 Sep 2012 15:58:35 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TEj97-0004Mt-HJ for xen-users@lists.xen.org; Thu, 20 Sep 2012 15:58:33 +0000 Received: from [85.158.143.99:42109] by server-3.bemta-4.messagelabs.com id B2/DC-10986-82D3B505; Thu, 20 Sep 2012 15:58:32 +0000 X-Env-Sender: fajar@fajar.net X-Msg-Ref: server-11.tower-216.messagelabs.com!1348156711!23630327!1 X-Originating-IP: [209.85.214.173] X-SpamReason: No, hits=0.3 required=7.0 tests=RCVD_BY_IP X-StarScan-Received: X-StarScan-Version: 6.6.1.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 26114 invoked from network); 20 Sep 2012 15:58:32 -0000 Received: from mail-ob0-f173.google.com (HELO mail-ob0-f173.google.com) (209.85.214.173) by server-11.tower-216.messagelabs.com with RC4-SHA encrypted SMTP; 20 Sep 2012 15:58:32 -0000 Received: by obbta14 with SMTP id ta14so2945110obb.32 for ; Thu, 20 Sep 2012 08:58:30 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:x-gm-message-state; bh=oRg0Tk7c0pvcFKDR1seose5IKMCund50Ja4ugL7aHS4=; b=Q8K1It18uukUivnaLuM+uToWbn54i435TkOQU3ChcBCsuBhYt6rZO/2oKO0xOtVgu3 hkWZFnyA+DswdY7wgv2PyZ7rJZfBEHbbOeHDrdXAt0pa9rngsH4OWZuQLeWnCQzuFVs/ 2+KJlUU4/63Mg7k44Fp6LW/+gH8OveNtCb5xyd+ef8r/mCC3njncFn8IOdp40+Fqw16K GeqBH2T8dDZoUWfOepP5q9GaJKzIKopk0qDpKC6hRbQYnMHUG3mjd0Yl3kBcAdx7wE8z oaGkyx71AHzoPY9Uy70BuJ0VQCM3cGlWoPQgegXEyfcN3CR7EH36tVumg5c2okkBViBz d6Ug== MIME-Version: 1.0 Received: by 10.182.49.102 with SMTP id t6mr1666040obn.94.1348156710726; Thu, 20 Sep 2012 08:58:30 -0700 (PDT) Received: by 10.60.6.230 with HTTP; Thu, 20 Sep 2012 08:58:30 -0700 (PDT) In-Reply-To: References: Date: Thu, 20 Sep 2012 22:58:30 +0700 Message-ID: From: "Fajar A. Nugraha" To: kevin parker X-Gm-Message-State: ALoCoQma8BKi34c//gd34YFHpcsgzggldwX1pjb4OP7EhVwp7u+zJbVJ2EKaZ83qyHeIIGRe5VuI Cc: xen-users@lists.xen.org Subject: Re: [Xen-users] Running Linux VM in para mode with Intel VT enabled X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org On Thu, Sep 20, 2012 at 10:34 PM, kevin parker wrote: > 1. how can i makesure that all the created VM will be in > paravirtualized mode even with VT enabled? Depends on how you create the VMs. For example, if you create it by hand, then if you DON'T have a line "builder='hvm'" in the VM config file, then you're using PV. If you use some kind of frontend (e.g. libvirt) it should have an option to choose VM type. > 2.Can i be able to run Linux VM in para mode with VT enabled? yes > 3.Will simply turning on VT support changes virtualization type from para to > full for all vms created on that machine? no > 4.Will there be any performance improvement for VM running Linux OS if VT is > enabled? no > 5.Is it normal to miss vmx flag in /proc/cpuinfo after booting to XEN > kernel,even with VT enabled? yes. Xen intentionally hides it because xen uses it, and no other process in the dom0 can use it anyway. -- Fajar _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Thu Sep 20 15:59:36 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Thu, 20 Sep 2012 15:59:36 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TEj99-0004Mz-8x; Thu, 20 Sep 2012 15:58:35 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TEj97-0004Mt-HJ for xen-users@lists.xen.org; Thu, 20 Sep 2012 15:58:33 +0000 Received: from [85.158.143.99:42109] by server-3.bemta-4.messagelabs.com id B2/DC-10986-82D3B505; Thu, 20 Sep 2012 15:58:32 +0000 X-Env-Sender: fajar@fajar.net X-Msg-Ref: server-11.tower-216.messagelabs.com!1348156711!23630327!1 X-Originating-IP: [209.85.214.173] X-SpamReason: No, hits=0.3 required=7.0 tests=RCVD_BY_IP X-StarScan-Received: X-StarScan-Version: 6.6.1.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 26114 invoked from network); 20 Sep 2012 15:58:32 -0000 Received: from mail-ob0-f173.google.com (HELO mail-ob0-f173.google.com) (209.85.214.173) by server-11.tower-216.messagelabs.com with RC4-SHA encrypted SMTP; 20 Sep 2012 15:58:32 -0000 Received: by obbta14 with SMTP id ta14so2945110obb.32 for ; Thu, 20 Sep 2012 08:58:30 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:x-gm-message-state; bh=oRg0Tk7c0pvcFKDR1seose5IKMCund50Ja4ugL7aHS4=; b=Q8K1It18uukUivnaLuM+uToWbn54i435TkOQU3ChcBCsuBhYt6rZO/2oKO0xOtVgu3 hkWZFnyA+DswdY7wgv2PyZ7rJZfBEHbbOeHDrdXAt0pa9rngsH4OWZuQLeWnCQzuFVs/ 2+KJlUU4/63Mg7k44Fp6LW/+gH8OveNtCb5xyd+ef8r/mCC3njncFn8IOdp40+Fqw16K GeqBH2T8dDZoUWfOepP5q9GaJKzIKopk0qDpKC6hRbQYnMHUG3mjd0Yl3kBcAdx7wE8z oaGkyx71AHzoPY9Uy70BuJ0VQCM3cGlWoPQgegXEyfcN3CR7EH36tVumg5c2okkBViBz d6Ug== MIME-Version: 1.0 Received: by 10.182.49.102 with SMTP id t6mr1666040obn.94.1348156710726; Thu, 20 Sep 2012 08:58:30 -0700 (PDT) Received: by 10.60.6.230 with HTTP; Thu, 20 Sep 2012 08:58:30 -0700 (PDT) In-Reply-To: References: Date: Thu, 20 Sep 2012 22:58:30 +0700 Message-ID: From: "Fajar A. Nugraha" To: kevin parker X-Gm-Message-State: ALoCoQma8BKi34c//gd34YFHpcsgzggldwX1pjb4OP7EhVwp7u+zJbVJ2EKaZ83qyHeIIGRe5VuI Cc: xen-users@lists.xen.org Subject: Re: [Xen-users] Running Linux VM in para mode with Intel VT enabled X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org On Thu, Sep 20, 2012 at 10:34 PM, kevin parker wrote: > 1. how can i makesure that all the created VM will be in > paravirtualized mode even with VT enabled? Depends on how you create the VMs. For example, if you create it by hand, then if you DON'T have a line "builder='hvm'" in the VM config file, then you're using PV. If you use some kind of frontend (e.g. libvirt) it should have an option to choose VM type. > 2.Can i be able to run Linux VM in para mode with VT enabled? yes > 3.Will simply turning on VT support changes virtualization type from para to > full for all vms created on that machine? no > 4.Will there be any performance improvement for VM running Linux OS if VT is > enabled? no > 5.Is it normal to miss vmx flag in /proc/cpuinfo after booting to XEN > kernel,even with VT enabled? yes. Xen intentionally hides it because xen uses it, and no other process in the dom0 can use it anyway. -- Fajar _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Thu Sep 20 16:34:24 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Thu, 20 Sep 2012 16:34:24 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TEjgs-0005dy-Gz; Thu, 20 Sep 2012 16:33:26 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TEjgr-0005ds-98 for xen-users@lists.xen.org; Thu, 20 Sep 2012 16:33:25 +0000 Received: from [85.158.138.51:64414] by server-8.bemta-3.messagelabs.com id 98/29-24700-4554B505; Thu, 20 Sep 2012 16:33:24 +0000 X-Env-Sender: singapore.mr.teo.en.ming@gmail.com X-Msg-Ref: server-14.tower-174.messagelabs.com!1348158801!25022072!1 X-Originating-IP: [209.85.160.45] X-SpamReason: No, hits=0.3 required=7.0 tests=ML_RADAR_SPEW_LINKS_14, RCVD_BY_IP,spamassassin: X-StarScan-Received: X-StarScan-Version: 6.6.1.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 29217 invoked from network); 20 Sep 2012 16:33:23 -0000 Received: from mail-pb0-f45.google.com (HELO mail-pb0-f45.google.com) (209.85.160.45) by server-14.tower-174.messagelabs.com with RC4-SHA encrypted SMTP; 20 Sep 2012 16:33:23 -0000 Received: by pbbrp12 with SMTP id rp12so5577907pbb.32 for ; Thu, 20 Sep 2012 09:33:21 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:user-agent:mime-version:to:subject:references :in-reply-to:content-type:content-transfer-encoding; bh=e3ElmdDsAJDKBjzONcOVe2c6hxnj2psxQJtO945jhOg=; b=zbnAp1dEexHOItNZXl7C3zxXMXUD/R3Ja0FTP/W9eLUq9wQUlzo+X9Sp3lvlqlH3WR SY8qXr7zjHKB6YSmHmoDocjtZy9S1JRt7yLv1lNk1DrNBkzLjOPtCEAaooRQM4rh1pmN l3GkbHV/T9mFsteLUb2zKS/4adwsCy3KfaSusZbeFGzdBLNA1/tUkLrj2kE2HpuQgQuT 8VbEWEER3iGkZmTI8jZugyY9BbHNwNdLL64CP2KfFu154/DD7xo24sNVV7LmjHQTwC5Z ULdG2ujroVdjUnMFTdB3A4bdK8BSpBX4gfwms00LQpUftG4hpepxS/Xs8Ayd0SIMRfAM 89OQ== Received: by 10.68.197.100 with SMTP id it4mr8457180pbc.16.1348158801307; Thu, 20 Sep 2012 09:33:21 -0700 (PDT) Received: from [192.168.1.2] (cm70.gamma203.maxonline.com.sg. [202.156.203.70]) by mx.google.com with ESMTPS id wf7sm3726399pbc.34.2012.09.20.09.33.19 (version=SSLv3 cipher=OTHER); Thu, 20 Sep 2012 09:33:20 -0700 (PDT) Message-ID: <505B454D.2080003@gmail.com> Date: Fri, 21 Sep 2012 00:33:17 +0800 From: "Teo En Ming (Zhang Enming)" User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:10.0.2) Gecko/20120216 Thunderbird/10.0.2 MIME-Version: 1.0 To: Marc Tousignant , "xen-users@lists.xen.org" , "Teo En Ming (Zhang Enming)" References: <008f01cd968e$15260cb0$3f722610$@gmail.com> In-Reply-To: <008f01cd968e$15260cb0$3f722610$@gmail.com> Subject: Re: [Xen-users] Solved - PCIe/VGA passthrough X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset="us-ascii"; Format="flowed" Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org On 20/09/2012 01:42, Marc Tousignant wrote: > > -----Original Message----- > From: Dariusz Krempa [mailto:imperiaonline4@gmail.com] > Sent: Wednesday, September 19, 2012 11:23 AM > To: Marc Tousignant > Subject: Re: [Xen-users] PCIe/VGA passthrough > > 2012/9/19 Marc Tousignant: >> >> -----Original Message----- >> From: Dariusz Krempa [mailto:imperiaonline4@gmail.com] >> Sent: Wednesday, September 19, 2012 9:29 AM >> To: Marc Tousignant >> Subject: Re: [Xen-users] PCIe/VGA passthrough >> >> >> Hi. >> I've spend last few days to turn on vga passthrough on my box and >> finally i did it. Everything what i've read about configurations tells >> me that its not possible with my MB (Asus P8H67 + Asus GTX560 Top), but... >> I followed also tutorial from Teo En Ming and i did patch from David >> Gis. I have no BAR's, then i used ranges from dmesg | grep '1:00.0' | >> grep mem and did patch like following David's Gis and Teo En Ming > descriptions. >> I'm not yet sure that is full success, but Gpu-z and Cpu-z recognized >> my hardware, also benchmark from Unigin heaven is pretty good. I did >> pciback configuration for window xp DomU not like Teo En Ming with >> pci-stub. I hope this will helpfully for You. >> >> --- >> >> Unfortunately, this was not helpful at all. I'm only seeing 1 BAR/mem >> line pci 0000:01:00.0: BAR 6: assigned [mem 0xcd000000-0xcd01ffff >> pref] >> >> But my video card has ranges: >> Region 0: Memory at cc000000 (32-bit, non-prefetchable) [size=16M] >> Region 1: Memory at b0000000 (64-bit, prefetchable) [size=256M] >> Region 3: Memory at ca000000 (64-bit, non-prefetchable) [size=32M] >> Region 5: I/O ports at 9c00 [size=128] What the dmesg seems to >> be finding is the one line from the lspci output on my card: >> [virtual] Expansion ROM at cd000000 [disabled] [size=128K] >> >> MarcT >> > I am totally newbie with linux and Xen, but i think You could rebuild > Dom0 or Xen or both, but first try to see what You get from this and compare > to David's Gis output. I have for all "=y" > > grep -i xen /boot/config > > ---- > > Solved it. Turns out you can't find the memory without first setting up the > kernel commands to hide the device. > > dmesg | grep 01:00.0 | grep "pci.*mem" > pci 0000:01:00.0: BAR 0: assigned [mem 0xcc000000-0xccffffff] > pci 0000:01:00.0: BAR 1: assigned [mem 0xb0000000-0xbfffffff 64bit pref] > pci 0000:01:00.0: BAR 3: assigned [mem 0xca000000-0xcbffffff 64bit] > pci 0000:01:00.0: BAR 6: assigned [mem 0xcd000000-0xcd01ffff pref] > > MarcT > > > _______________________________________________ > Xen-users mailing list > Xen-users@lists.xen.org > http://lists.xen.org/xen-users > Dear MarcT, May I know the exact steps you have taken to get all the BARs? I don't have any BAR at all. Solved it. Turns out you can't find the memory without first setting up the kernel commands to hide the device. dmesg | grep 01:00.0 | grep "pci.*mem" pci 0000:01:00.0: BAR 0: assigned [mem 0xcc000000-0xccffffff] pci 0000:01:00.0: BAR 1: assigned [mem 0xb0000000-0xbfffffff 64bit pref] pci 0000:01:00.0: BAR 3: assigned [mem 0xca000000-0xcbffffff 64bit] pci 0000:01:00.0: BAR 6: assigned [mem 0xcd000000-0xcd01ffff pref] -- Yours sincerely, Mr. Teo En Ming (Zhang Enming) Singapore _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Thu Sep 20 16:34:24 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Thu, 20 Sep 2012 16:34:24 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TEjgs-0005dy-Gz; Thu, 20 Sep 2012 16:33:26 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TEjgr-0005ds-98 for xen-users@lists.xen.org; Thu, 20 Sep 2012 16:33:25 +0000 Received: from [85.158.138.51:64414] by server-8.bemta-3.messagelabs.com id 98/29-24700-4554B505; Thu, 20 Sep 2012 16:33:24 +0000 X-Env-Sender: singapore.mr.teo.en.ming@gmail.com X-Msg-Ref: server-14.tower-174.messagelabs.com!1348158801!25022072!1 X-Originating-IP: [209.85.160.45] X-SpamReason: No, hits=0.3 required=7.0 tests=ML_RADAR_SPEW_LINKS_14, RCVD_BY_IP,spamassassin: X-StarScan-Received: X-StarScan-Version: 6.6.1.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 29217 invoked from network); 20 Sep 2012 16:33:23 -0000 Received: from mail-pb0-f45.google.com (HELO mail-pb0-f45.google.com) (209.85.160.45) by server-14.tower-174.messagelabs.com with RC4-SHA encrypted SMTP; 20 Sep 2012 16:33:23 -0000 Received: by pbbrp12 with SMTP id rp12so5577907pbb.32 for ; Thu, 20 Sep 2012 09:33:21 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:user-agent:mime-version:to:subject:references :in-reply-to:content-type:content-transfer-encoding; bh=e3ElmdDsAJDKBjzONcOVe2c6hxnj2psxQJtO945jhOg=; b=zbnAp1dEexHOItNZXl7C3zxXMXUD/R3Ja0FTP/W9eLUq9wQUlzo+X9Sp3lvlqlH3WR SY8qXr7zjHKB6YSmHmoDocjtZy9S1JRt7yLv1lNk1DrNBkzLjOPtCEAaooRQM4rh1pmN l3GkbHV/T9mFsteLUb2zKS/4adwsCy3KfaSusZbeFGzdBLNA1/tUkLrj2kE2HpuQgQuT 8VbEWEER3iGkZmTI8jZugyY9BbHNwNdLL64CP2KfFu154/DD7xo24sNVV7LmjHQTwC5Z ULdG2ujroVdjUnMFTdB3A4bdK8BSpBX4gfwms00LQpUftG4hpepxS/Xs8Ayd0SIMRfAM 89OQ== Received: by 10.68.197.100 with SMTP id it4mr8457180pbc.16.1348158801307; Thu, 20 Sep 2012 09:33:21 -0700 (PDT) Received: from [192.168.1.2] (cm70.gamma203.maxonline.com.sg. [202.156.203.70]) by mx.google.com with ESMTPS id wf7sm3726399pbc.34.2012.09.20.09.33.19 (version=SSLv3 cipher=OTHER); Thu, 20 Sep 2012 09:33:20 -0700 (PDT) Message-ID: <505B454D.2080003@gmail.com> Date: Fri, 21 Sep 2012 00:33:17 +0800 From: "Teo En Ming (Zhang Enming)" User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:10.0.2) Gecko/20120216 Thunderbird/10.0.2 MIME-Version: 1.0 To: Marc Tousignant , "xen-users@lists.xen.org" , "Teo En Ming (Zhang Enming)" References: <008f01cd968e$15260cb0$3f722610$@gmail.com> In-Reply-To: <008f01cd968e$15260cb0$3f722610$@gmail.com> Subject: Re: [Xen-users] Solved - PCIe/VGA passthrough X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset="us-ascii"; Format="flowed" Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org On 20/09/2012 01:42, Marc Tousignant wrote: > > -----Original Message----- > From: Dariusz Krempa [mailto:imperiaonline4@gmail.com] > Sent: Wednesday, September 19, 2012 11:23 AM > To: Marc Tousignant > Subject: Re: [Xen-users] PCIe/VGA passthrough > > 2012/9/19 Marc Tousignant: >> >> -----Original Message----- >> From: Dariusz Krempa [mailto:imperiaonline4@gmail.com] >> Sent: Wednesday, September 19, 2012 9:29 AM >> To: Marc Tousignant >> Subject: Re: [Xen-users] PCIe/VGA passthrough >> >> >> Hi. >> I've spend last few days to turn on vga passthrough on my box and >> finally i did it. Everything what i've read about configurations tells >> me that its not possible with my MB (Asus P8H67 + Asus GTX560 Top), but... >> I followed also tutorial from Teo En Ming and i did patch from David >> Gis. I have no BAR's, then i used ranges from dmesg | grep '1:00.0' | >> grep mem and did patch like following David's Gis and Teo En Ming > descriptions. >> I'm not yet sure that is full success, but Gpu-z and Cpu-z recognized >> my hardware, also benchmark from Unigin heaven is pretty good. I did >> pciback configuration for window xp DomU not like Teo En Ming with >> pci-stub. I hope this will helpfully for You. >> >> --- >> >> Unfortunately, this was not helpful at all. I'm only seeing 1 BAR/mem >> line pci 0000:01:00.0: BAR 6: assigned [mem 0xcd000000-0xcd01ffff >> pref] >> >> But my video card has ranges: >> Region 0: Memory at cc000000 (32-bit, non-prefetchable) [size=16M] >> Region 1: Memory at b0000000 (64-bit, prefetchable) [size=256M] >> Region 3: Memory at ca000000 (64-bit, non-prefetchable) [size=32M] >> Region 5: I/O ports at 9c00 [size=128] What the dmesg seems to >> be finding is the one line from the lspci output on my card: >> [virtual] Expansion ROM at cd000000 [disabled] [size=128K] >> >> MarcT >> > I am totally newbie with linux and Xen, but i think You could rebuild > Dom0 or Xen or both, but first try to see what You get from this and compare > to David's Gis output. I have for all "=y" > > grep -i xen /boot/config > > ---- > > Solved it. Turns out you can't find the memory without first setting up the > kernel commands to hide the device. > > dmesg | grep 01:00.0 | grep "pci.*mem" > pci 0000:01:00.0: BAR 0: assigned [mem 0xcc000000-0xccffffff] > pci 0000:01:00.0: BAR 1: assigned [mem 0xb0000000-0xbfffffff 64bit pref] > pci 0000:01:00.0: BAR 3: assigned [mem 0xca000000-0xcbffffff 64bit] > pci 0000:01:00.0: BAR 6: assigned [mem 0xcd000000-0xcd01ffff pref] > > MarcT > > > _______________________________________________ > Xen-users mailing list > Xen-users@lists.xen.org > http://lists.xen.org/xen-users > Dear MarcT, May I know the exact steps you have taken to get all the BARs? I don't have any BAR at all. Solved it. Turns out you can't find the memory without first setting up the kernel commands to hide the device. dmesg | grep 01:00.0 | grep "pci.*mem" pci 0000:01:00.0: BAR 0: assigned [mem 0xcc000000-0xccffffff] pci 0000:01:00.0: BAR 1: assigned [mem 0xb0000000-0xbfffffff 64bit pref] pci 0000:01:00.0: BAR 3: assigned [mem 0xca000000-0xcbffffff 64bit] pci 0000:01:00.0: BAR 6: assigned [mem 0xcd000000-0xcd01ffff pref] -- Yours sincerely, Mr. Teo En Ming (Zhang Enming) Singapore _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Thu Sep 20 17:05:20 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Thu, 20 Sep 2012 17:05:20 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TEkAj-0006N6-PJ; Thu, 20 Sep 2012 17:04:17 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TEkAi-0006N1-Ki for Xen-users@lists.xen.org; Thu, 20 Sep 2012 17:04:16 +0000 Received: from [85.158.139.83:58897] by server-4.bemta-5.messagelabs.com id 2F/34-23042-F8C4B505; Thu, 20 Sep 2012 17:04:15 +0000 X-Env-Sender: imperiaonline4@gmail.com X-Msg-Ref: server-15.tower-182.messagelabs.com!1348160653!29228696!1 X-Originating-IP: [209.85.219.45] X-SpamReason: No, hits=0.3 required=7.0 tests=ML_RADAR_SPEW_LINKS_14, RCVD_BY_IP,spamassassin: X-StarScan-Received: X-StarScan-Version: 6.6.1.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 10148 invoked from network); 20 Sep 2012 17:04:15 -0000 Received: from mail-oa0-f45.google.com (HELO mail-oa0-f45.google.com) (209.85.219.45) by server-15.tower-182.messagelabs.com with RC4-SHA encrypted SMTP; 20 Sep 2012 17:04:15 -0000 Received: by oagn12 with SMTP id n12so3071729oag.32 for ; Thu, 20 Sep 2012 10:04:13 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:date:message-id:subject:from:to:content-type; bh=+eUL8EimdHbd9Z0TAufZ17S/n1/V+aQWoLi7yPKlkHs=; b=W00QnLhRtmScJ550AgErTcvaTCjfbqUpLsRQHUobl9PMleqBWhB00jT0lT993dJJJK PEdvUfBikcCeCziGjI8nt9WUA7F0anbiXcv7O/6fH/Psej7A/2Ox/IwVKaSOhcVR8ZOk JdqjNnGRATbWwf+icnBqLi9EgJ3E35wSdxqD2lzAgZsrKUEMfHR11jkmaYCBI0tu0Y+Q GJ9d+yfYoHvcKR3RYZtwfus1+gvmlJjf4OcviNk7xhJmSAWlbPNlkzfb9bsnEzuV+de5 hgaqtuP5O69QltPb6QjgwEIrQE5+iwOk2ym2Lb69QeMoDAN3AYtSAXYD0sKykncsbFm5 uOFA== MIME-Version: 1.0 Received: by 10.60.171.114 with SMTP id at18mr1103897oec.24.1348160653179; Thu, 20 Sep 2012 10:04:13 -0700 (PDT) Received: by 10.60.58.234 with HTTP; Thu, 20 Sep 2012 10:04:13 -0700 (PDT) Date: Thu, 20 Sep 2012 19:04:13 +0200 Message-ID: From: Dariusz Krempa To: Xen-users@lists.xen.org Subject: [Xen-users] Ejecting cdrom from hvm machine leads to errors X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org Hi. I've tried to insert cdrom into hvm but without results, then i thought maybe something helpfully will happened when i first eject cdrom. After using commandline xl cd-eject DomainId xvdc happened nothing, looks like command goes fine, but after that any command: cd-insert or cd-eject shows error Violation of protection Memory Storage Capacity I have xen 4.2-rc4 on ubuntu 12.04 with Dom0 from Teo En Ming tutorial _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Thu Sep 20 17:05:20 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Thu, 20 Sep 2012 17:05:20 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TEkAj-0006N6-PJ; Thu, 20 Sep 2012 17:04:17 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TEkAi-0006N1-Ki for Xen-users@lists.xen.org; Thu, 20 Sep 2012 17:04:16 +0000 Received: from [85.158.139.83:58897] by server-4.bemta-5.messagelabs.com id 2F/34-23042-F8C4B505; Thu, 20 Sep 2012 17:04:15 +0000 X-Env-Sender: imperiaonline4@gmail.com X-Msg-Ref: server-15.tower-182.messagelabs.com!1348160653!29228696!1 X-Originating-IP: [209.85.219.45] X-SpamReason: No, hits=0.3 required=7.0 tests=ML_RADAR_SPEW_LINKS_14, RCVD_BY_IP,spamassassin: X-StarScan-Received: X-StarScan-Version: 6.6.1.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 10148 invoked from network); 20 Sep 2012 17:04:15 -0000 Received: from mail-oa0-f45.google.com (HELO mail-oa0-f45.google.com) (209.85.219.45) by server-15.tower-182.messagelabs.com with RC4-SHA encrypted SMTP; 20 Sep 2012 17:04:15 -0000 Received: by oagn12 with SMTP id n12so3071729oag.32 for ; Thu, 20 Sep 2012 10:04:13 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:date:message-id:subject:from:to:content-type; bh=+eUL8EimdHbd9Z0TAufZ17S/n1/V+aQWoLi7yPKlkHs=; b=W00QnLhRtmScJ550AgErTcvaTCjfbqUpLsRQHUobl9PMleqBWhB00jT0lT993dJJJK PEdvUfBikcCeCziGjI8nt9WUA7F0anbiXcv7O/6fH/Psej7A/2Ox/IwVKaSOhcVR8ZOk JdqjNnGRATbWwf+icnBqLi9EgJ3E35wSdxqD2lzAgZsrKUEMfHR11jkmaYCBI0tu0Y+Q GJ9d+yfYoHvcKR3RYZtwfus1+gvmlJjf4OcviNk7xhJmSAWlbPNlkzfb9bsnEzuV+de5 hgaqtuP5O69QltPb6QjgwEIrQE5+iwOk2ym2Lb69QeMoDAN3AYtSAXYD0sKykncsbFm5 uOFA== MIME-Version: 1.0 Received: by 10.60.171.114 with SMTP id at18mr1103897oec.24.1348160653179; Thu, 20 Sep 2012 10:04:13 -0700 (PDT) Received: by 10.60.58.234 with HTTP; Thu, 20 Sep 2012 10:04:13 -0700 (PDT) Date: Thu, 20 Sep 2012 19:04:13 +0200 Message-ID: From: Dariusz Krempa To: Xen-users@lists.xen.org Subject: [Xen-users] Ejecting cdrom from hvm machine leads to errors X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org Hi. I've tried to insert cdrom into hvm but without results, then i thought maybe something helpfully will happened when i first eject cdrom. After using commandline xl cd-eject DomainId xvdc happened nothing, looks like command goes fine, but after that any command: cd-insert or cd-eject shows error Violation of protection Memory Storage Capacity I have xen 4.2-rc4 on ubuntu 12.04 with Dom0 from Teo En Ming tutorial _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Thu Sep 20 17:13:07 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Thu, 20 Sep 2012 17:13:07 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TEkIP-0006ly-J0; Thu, 20 Sep 2012 17:12:13 +0000 Received: from mail27.messagelabs.com ([193.109.254.147]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TEkIO-0006lT-Ac for Xen-users@lists.xen.org; Thu, 20 Sep 2012 17:12:12 +0000 X-Env-Sender: imperiaonline4@gmail.com X-Msg-Ref: server-4.tower-27.messagelabs.com!1348161091!11205451!1 X-Originating-IP: [209.85.214.173] X-SpamReason: No, hits=0.3 required=7.0 tests=ML_RADAR_SPEW_LINKS_14, RCVD_BY_IP,spamassassin: X-StarScan-Received: X-StarScan-Version: 6.6.1.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 14807 invoked from network); 20 Sep 2012 17:11:34 -0000 Received: from mail-ob0-f173.google.com (HELO mail-ob0-f173.google.com) (209.85.214.173) by server-4.tower-27.messagelabs.com with RC4-SHA encrypted SMTP; 20 Sep 2012 17:11:34 -0000 Received: by obbta14 with SMTP id ta14so3047498obb.32 for ; Thu, 20 Sep 2012 10:11:30 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; bh=+eUL8EimdHbd9Z0TAufZ17S/n1/V+aQWoLi7yPKlkHs=; b=G0YXcWt4hbVLITKpw6ggQFNEpUBohVdVNnQlTR4E25///EpjvfkCsJZ3zUnuK4hq+B S9WRfyhd7yd3BH8v49V8AdC/3SGNx4mRx2wL6ndQMFIXzVPAWBNE3OMnIk07F9nlDMlD C567xfglwVPa9XQHtdlhXbxBB3ZgfpojyuKiDkHb3ANqrD6t8QVL8AYW3XU2psuYEN48 Lzp+Jwf99+w1uX0yofHBbeqpS4SSJ1oysPD9OLgFrZ8weAMBnADYQjy5Fd84V7LnSIh5 G/GuFh6X8DZx8hAw7cGT1iZMUSTv5aTixEIuYvkgpDXzv3uWd+bayob25NcTlxLj44PR ngmw== MIME-Version: 1.0 Received: by 10.60.171.114 with SMTP id at18mr1121398oec.24.1348161090268; Thu, 20 Sep 2012 10:11:30 -0700 (PDT) Received: by 10.60.58.234 with HTTP; Thu, 20 Sep 2012 10:11:30 -0700 (PDT) In-Reply-To: References: Date: Thu, 20 Sep 2012 19:11:30 +0200 Message-ID: From: Dariusz Krempa To: Xen-users@lists.xen.org Subject: [Xen-users] Ejecting cdrom from hvm machine leads to errors X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org Hi. I've tried to insert cdrom into hvm but without results, then i thought maybe something helpfully will happened when i first eject cdrom. After using commandline xl cd-eject DomainId xvdc happened nothing, looks like command goes fine, but after that any command: cd-insert or cd-eject shows error Violation of protection Memory Storage Capacity I have xen 4.2-rc4 on ubuntu 12.04 with Dom0 from Teo En Ming tutorial _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Thu Sep 20 17:13:07 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Thu, 20 Sep 2012 17:13:07 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TEkIP-0006ly-J0; Thu, 20 Sep 2012 17:12:13 +0000 Received: from mail27.messagelabs.com ([193.109.254.147]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TEkIO-0006lT-Ac for Xen-users@lists.xen.org; Thu, 20 Sep 2012 17:12:12 +0000 X-Env-Sender: imperiaonline4@gmail.com X-Msg-Ref: server-4.tower-27.messagelabs.com!1348161091!11205451!1 X-Originating-IP: [209.85.214.173] X-SpamReason: No, hits=0.3 required=7.0 tests=ML_RADAR_SPEW_LINKS_14, RCVD_BY_IP,spamassassin: X-StarScan-Received: X-StarScan-Version: 6.6.1.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 14807 invoked from network); 20 Sep 2012 17:11:34 -0000 Received: from mail-ob0-f173.google.com (HELO mail-ob0-f173.google.com) (209.85.214.173) by server-4.tower-27.messagelabs.com with RC4-SHA encrypted SMTP; 20 Sep 2012 17:11:34 -0000 Received: by obbta14 with SMTP id ta14so3047498obb.32 for ; Thu, 20 Sep 2012 10:11:30 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; bh=+eUL8EimdHbd9Z0TAufZ17S/n1/V+aQWoLi7yPKlkHs=; b=G0YXcWt4hbVLITKpw6ggQFNEpUBohVdVNnQlTR4E25///EpjvfkCsJZ3zUnuK4hq+B S9WRfyhd7yd3BH8v49V8AdC/3SGNx4mRx2wL6ndQMFIXzVPAWBNE3OMnIk07F9nlDMlD C567xfglwVPa9XQHtdlhXbxBB3ZgfpojyuKiDkHb3ANqrD6t8QVL8AYW3XU2psuYEN48 Lzp+Jwf99+w1uX0yofHBbeqpS4SSJ1oysPD9OLgFrZ8weAMBnADYQjy5Fd84V7LnSIh5 G/GuFh6X8DZx8hAw7cGT1iZMUSTv5aTixEIuYvkgpDXzv3uWd+bayob25NcTlxLj44PR ngmw== MIME-Version: 1.0 Received: by 10.60.171.114 with SMTP id at18mr1121398oec.24.1348161090268; Thu, 20 Sep 2012 10:11:30 -0700 (PDT) Received: by 10.60.58.234 with HTTP; Thu, 20 Sep 2012 10:11:30 -0700 (PDT) In-Reply-To: References: Date: Thu, 20 Sep 2012 19:11:30 +0200 Message-ID: From: Dariusz Krempa To: Xen-users@lists.xen.org Subject: [Xen-users] Ejecting cdrom from hvm machine leads to errors X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org Hi. I've tried to insert cdrom into hvm but without results, then i thought maybe something helpfully will happened when i first eject cdrom. After using commandline xl cd-eject DomainId xvdc happened nothing, looks like command goes fine, but after that any command: cd-insert or cd-eject shows error Violation of protection Memory Storage Capacity I have xen 4.2-rc4 on ubuntu 12.04 with Dom0 from Teo En Ming tutorial _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Thu Sep 20 18:03:34 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Thu, 20 Sep 2012 18:03:34 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TEl59-0007wv-4j; Thu, 20 Sep 2012 18:02:35 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TEl58-0007wq-0d for xen-users@lists.xen.org; Thu, 20 Sep 2012 18:02:34 +0000 Received: from [85.158.143.99:22538] by server-1.bemta-4.messagelabs.com id 89/DA-05684-93A5B505; Thu, 20 Sep 2012 18:02:33 +0000 X-Env-Sender: matthiasblankenhaus@yahoo.com X-Msg-Ref: server-13.tower-216.messagelabs.com!1348164151!30253692!1 X-Originating-IP: [98.139.91.240] X-SpamReason: No, hits=0.0 required=7.0 tests=HTML_MESSAGE, ML_RADAR_SPEW_LINKS_12,ML_RADAR_SPEW_LINKS_14,ML_RADAR_SPEW_LINKS_6, spamassassin: X-StarScan-Received: X-StarScan-Version: 6.6.1.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 2310 invoked from network); 20 Sep 2012 18:02:32 -0000 Received: from nm11-vm0.bullet.mail.sp2.yahoo.com (HELO nm11-vm0.bullet.mail.sp2.yahoo.com) (98.139.91.240) by server-13.tower-216.messagelabs.com with SMTP; 20 Sep 2012 18:02:32 -0000 Received: from [98.139.91.66] by nm11.bullet.mail.sp2.yahoo.com with NNFMP; 20 Sep 2012 18:02:30 -0000 Received: from [98.139.91.14] by tm6.bullet.mail.sp2.yahoo.com with NNFMP; 20 Sep 2012 18:02:30 -0000 Received: from [127.0.0.1] by omp1014.mail.sp2.yahoo.com with NNFMP; 20 Sep 2012 18:02:30 -0000 X-Yahoo-Newman-Property: ymail-3 X-Yahoo-Newman-Id: 827590.45047.bm@omp1014.mail.sp2.yahoo.com Received: (qmail 26768 invoked by uid 60001); 20 Sep 2012 18:02:30 -0000 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.com; s=s1024; t=1348164150; bh=T5PDmc/JyPQ49+Gm4vt3b2laEVJy8amfjdSA2hxIXnc=; h=X-YMail-OSG:Received:X-Mailer:References:Message-ID:Date:From:Reply-To:Subject:To:In-Reply-To:MIME-Version:Content-Type; b=bUn6RaWtTES58dptw/q34HBoQlhky6GW4NgzkSSaC2ck53IfIhQizCaPI0NSxclRGNMkXcuJBqpm8QdIa1VmX/mWHZB2PnZT3+1FzwPGA4izl4LmQj7JE2dsmtgO1C7Ov+C1Ipt+DxlJDMqOSUDrfvPlNPTN4fv+oSgPxLsonm8= DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com; h=X-YMail-OSG:Received:X-Mailer:References:Message-ID:Date:From:Reply-To:Subject:To:In-Reply-To:MIME-Version:Content-Type; b=XoIDG2RoxgizAjA20DhHWxavJzojIULFoPCqhOqTBnfWdc1Q4OA7w2DPtLEVyzO9BLJnnUz+ZTCRV5YuAvbSPsckdVJblFTbTWCTixBDPPm0+/KwO2hh8MLGx5NF2bjzL8nadoAGTI/Ks2jaOGYGfia/J5L8ojeB6BoMnF9Nios=; X-YMail-OSG: dKWHlNgVM1mG6BLJFCZelj3mz0X_wqKalhKV0Mvqsiom0r4 uvknHef3S_ciNiChPyAJ7om1RZZl9cFFAAe2j.91DYeeKlMBToN75QmoMQhq 4QlRwnjbku_XVpOaAWIeXWMM_7xesECI2Sir9Ogw6jLehdqNOTRuDPF50roA 9PeDid9eA_cnw915Fh6HvvsZfmK8.9jhcExLbBOtGIkVx5xOzReFHFo8A3i0 _vrelG4ODqVZCtj6B1qah0Hfcuw_p8YMbcZcXhgvFWMCsL_wmUlgfeLYcHy9 zuDKS6TGDYdH3SCg3XwIt.tlyGcmzI7Mm31LDJPaNYvEp4iuxqLIdH9KWsBH q1o01I1eLvC.bOXc2cUKlKiMJ8gT.Advl_8ICgvHeWPQ4CfgIK764q3DstC8 l8zQ37SzQvdGCKDmECmee7ohFa0Sb2BD4z3aHfYCFzQUdKVkG0Du1h_nkaPU 0ZirWfWgp54ByCmQTPiBKZLctuzOr_DiGNK70IcMXQFqu7ow0x13GWz18emr h08OwnPWY1smosILnagKAs2as_zYVUi148lTGNO05uQ.aXcGAH5zk Received: from [67.170.238.86] by web39405.mail.mud.yahoo.com via HTTP; Thu, 20 Sep 2012 11:02:30 PDT X-Mailer: YahooMailWebService/0.8.121.416 References: Message-ID: <1348164150.25406.YahooMailNeo@web39405.mail.mud.yahoo.com> Date: Thu, 20 Sep 2012 11:02:30 -0700 (PDT) From: Matthias Blankenhaus To: "xen-users@lists.xen.org" In-Reply-To: MIME-Version: 1.0 Subject: Re: [Xen-users] Running Linux VM in para mode with Intel VT enabled X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list Reply-To: Matthias Blankenhaus List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============0937135777534634169==" Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org --===============0937135777534634169== Content-Type: multipart/alternative; boundary="-154443274-1924262819-1348164150=:25406" ---154443274-1924262819-1348164150=:25406 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: quoted-printable =0A=0A=0A=0A=0A>________________________________=0A> From: kevin parker =0A>To: xen-users@lists.xen.org =0A>Sent: Thursday,= September 20, 2012 8:34 AM=0A>Subject: [Xen-users] Running Linux VM in par= a mode with Intel VT enabled=0A> =0A>=0A>Hi all,=0A>=A0 =A0 =A0 =A0=A0I am = having a server running XEN,with ubuntu 12.04 as Domain 0.=0A>Intel VT is t= urned on by default and i dont want to run any Windows OS as VM.In that cas= e=0A>1. how can i makesure that all the created VM will be in=0Aparavirtual= ized mode even with VT enabled? =0A>I have heard that in Full Virtualizatio= n hypervisor needs to work hard for emulating all the underlying hardware,w= hich may reduce performance for too much i/o specific applications when com= pared to para mode.=0AThe difference between running a guest vm as a PV vs.= as a HVM is controlled by the guest vm's configuration.=A0=A0 In particula= r, if your guest vm's configuration contains the following lines, then the = guest would be launched as a HVM:=0A=0Akernel =3D '/usr/lib/xen-4.0/boot/hv= mloader'=0Abuilder=3D'hvm'=0AThus, if you want to ensure that your Ubunto g= uests runs as a PV you need to specify something along the following lines:= =0Akernel =3D '/boot/vmlinuz-2.6.33.20.x86_64'=A0=A0=A0=A0=A0=A0 # substitu= te this with your specific Ubuntu kernel=0Aramdisk =3D '/boot/initrd-2.6.33= .20.x86_64'=A0 # substitute this with your specific Ubuntu ramdisk, if you = want to use it, this is optional=0A=0Aextra =3D 'selinux=3D0 elevator=3Dnoo= p'=A0 # not strictly necessary, but allows you to pass parameters during bo= ot to the kernel=0A=0AFor more infos check this out: http://xenbits.xen.org= /docs/unstable/man/xl.cfg.5.html#paravirtualised__pv__guest_specific_option= s=0A=0A=0A=0A2.Can i be able to run Linux VM in para mode with VT enabled? = 3.Will simply turning on VT support changes virtualization type from para t= o full for all vms created on that machine? 4.Will there be any performance= improvement for VM running Linux OS if VT is enabled?=0A>5.Is it normal to= miss vmx flag in /proc/cpuinfo after booting to XEN kernel,even with VT en= abled?=0A>=0A>=0A>Regards,=0A>Kevin=0A>____________________________________= ___________=0A>Xen-users mailing list=0A>Xen-users@lists.xen.org=0A>http://= lists.xen.org/xen-users=0A>=0A> ---154443274-1924262819-1348164150=:25406 Content-Type: text/html; charset=iso-8859-1 Content-Transfer-Encoding: quoted-printable


From: kevin parker <= ;kevin.parker092@gmail.com>
To= : xen-users@lists.xen.org
Sent: Thursday, September 20, 2012 8:34 AM
Subject: [Xen-users] Running Linux VM in para mode with Int= el VT enabled

=0A
Hi all,        I am having = a server running XEN,with ubuntu 12.04 as Domain 0.
=0A
=0AIntel VT is turned on by defaul= t and i dont want to run any Windows OS as VM.In that case
1. how can i makesure that all =
the created VM will be in=0Aparavirtualized mode even with VT enabled?=0A
=0AI have heard= that in Full Virtualization hypervisor needs to work hard for emulating al= l the underlying hardware,which may reduce performance for too much i/o spe= cific applications when compared to para mode.
The difference between running a guest vm = as a PV vs. as a HVM is controlled by the guest vm's configuration. &n= bsp; In particular, if your guest vm's configuration contains the following= lines, then the guest would be launched as a HVM:
kernel =3D '/usr/lib/xen-4.0/boot/hvmloader'=0Abuilder=
=3D'hvm'
Thus, if you want to ensure that your Ubunto guests runs as a PV you nee= d to specify something along the following lines:
kernel =3D '/boot/vmlinuz-2.6.3= 3.20.x86_64'       # substitute this with you= r specific Ubuntu kernel
ramdisk =3D '/boot/initrd-2.6.33.20.x= 86_64'  # substitute this with your specific Ubuntu ramdisk, if you want to use it, this is optional
extra = =3D 'selinux=3D0 elevator=3Dnoop'  # not strictly necessary, but allow= s you to pass parameters during boot to the kernel
For more infos check = this out: http://xenbits.xen.org/docs/unstable/man/xl.cfg.5.html#paravirtua= lised__pv__guest_specific_options


2.Can i be=
 able to run Linux VM in para mode with VT enabled?=0A=0A3.Will simply turn=
ing on VT support changes virtualization type from para to full for all vms=
 created on that machine?=0A=0A4.Will there be any performance improvement =
for VM running Linux OS if VT is enabled?
=
5.Is it normal to miss vmx flag in /proc/cpuinfo after booting to XEN ke=
rnel,even with VT enabled?

Regards,
Kevin
=0A

_______________________________= ________________
Xen-users mailing list
Xen-users@lists.xe= n.org
h= ttp://lists.xen.org/xen-users

=
---154443274-1924262819-1348164150=:25406-- --===============0937135777534634169== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users --===============0937135777534634169==-- From xen-users-bounces@lists.xen.org Thu Sep 20 18:03:34 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Thu, 20 Sep 2012 18:03:34 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TEl59-0007wv-4j; Thu, 20 Sep 2012 18:02:35 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TEl58-0007wq-0d for xen-users@lists.xen.org; Thu, 20 Sep 2012 18:02:34 +0000 Received: from [85.158.143.99:22538] by server-1.bemta-4.messagelabs.com id 89/DA-05684-93A5B505; Thu, 20 Sep 2012 18:02:33 +0000 X-Env-Sender: matthiasblankenhaus@yahoo.com X-Msg-Ref: server-13.tower-216.messagelabs.com!1348164151!30253692!1 X-Originating-IP: [98.139.91.240] X-SpamReason: No, hits=0.0 required=7.0 tests=HTML_MESSAGE, ML_RADAR_SPEW_LINKS_12,ML_RADAR_SPEW_LINKS_14,ML_RADAR_SPEW_LINKS_6, spamassassin: X-StarScan-Received: X-StarScan-Version: 6.6.1.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 2310 invoked from network); 20 Sep 2012 18:02:32 -0000 Received: from nm11-vm0.bullet.mail.sp2.yahoo.com (HELO nm11-vm0.bullet.mail.sp2.yahoo.com) (98.139.91.240) by server-13.tower-216.messagelabs.com with SMTP; 20 Sep 2012 18:02:32 -0000 Received: from [98.139.91.66] by nm11.bullet.mail.sp2.yahoo.com with NNFMP; 20 Sep 2012 18:02:30 -0000 Received: from [98.139.91.14] by tm6.bullet.mail.sp2.yahoo.com with NNFMP; 20 Sep 2012 18:02:30 -0000 Received: from [127.0.0.1] by omp1014.mail.sp2.yahoo.com with NNFMP; 20 Sep 2012 18:02:30 -0000 X-Yahoo-Newman-Property: ymail-3 X-Yahoo-Newman-Id: 827590.45047.bm@omp1014.mail.sp2.yahoo.com Received: (qmail 26768 invoked by uid 60001); 20 Sep 2012 18:02:30 -0000 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.com; s=s1024; t=1348164150; bh=T5PDmc/JyPQ49+Gm4vt3b2laEVJy8amfjdSA2hxIXnc=; h=X-YMail-OSG:Received:X-Mailer:References:Message-ID:Date:From:Reply-To:Subject:To:In-Reply-To:MIME-Version:Content-Type; b=bUn6RaWtTES58dptw/q34HBoQlhky6GW4NgzkSSaC2ck53IfIhQizCaPI0NSxclRGNMkXcuJBqpm8QdIa1VmX/mWHZB2PnZT3+1FzwPGA4izl4LmQj7JE2dsmtgO1C7Ov+C1Ipt+DxlJDMqOSUDrfvPlNPTN4fv+oSgPxLsonm8= DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com; h=X-YMail-OSG:Received:X-Mailer:References:Message-ID:Date:From:Reply-To:Subject:To:In-Reply-To:MIME-Version:Content-Type; b=XoIDG2RoxgizAjA20DhHWxavJzojIULFoPCqhOqTBnfWdc1Q4OA7w2DPtLEVyzO9BLJnnUz+ZTCRV5YuAvbSPsckdVJblFTbTWCTixBDPPm0+/KwO2hh8MLGx5NF2bjzL8nadoAGTI/Ks2jaOGYGfia/J5L8ojeB6BoMnF9Nios=; X-YMail-OSG: dKWHlNgVM1mG6BLJFCZelj3mz0X_wqKalhKV0Mvqsiom0r4 uvknHef3S_ciNiChPyAJ7om1RZZl9cFFAAe2j.91DYeeKlMBToN75QmoMQhq 4QlRwnjbku_XVpOaAWIeXWMM_7xesECI2Sir9Ogw6jLehdqNOTRuDPF50roA 9PeDid9eA_cnw915Fh6HvvsZfmK8.9jhcExLbBOtGIkVx5xOzReFHFo8A3i0 _vrelG4ODqVZCtj6B1qah0Hfcuw_p8YMbcZcXhgvFWMCsL_wmUlgfeLYcHy9 zuDKS6TGDYdH3SCg3XwIt.tlyGcmzI7Mm31LDJPaNYvEp4iuxqLIdH9KWsBH q1o01I1eLvC.bOXc2cUKlKiMJ8gT.Advl_8ICgvHeWPQ4CfgIK764q3DstC8 l8zQ37SzQvdGCKDmECmee7ohFa0Sb2BD4z3aHfYCFzQUdKVkG0Du1h_nkaPU 0ZirWfWgp54ByCmQTPiBKZLctuzOr_DiGNK70IcMXQFqu7ow0x13GWz18emr h08OwnPWY1smosILnagKAs2as_zYVUi148lTGNO05uQ.aXcGAH5zk Received: from [67.170.238.86] by web39405.mail.mud.yahoo.com via HTTP; Thu, 20 Sep 2012 11:02:30 PDT X-Mailer: YahooMailWebService/0.8.121.416 References: Message-ID: <1348164150.25406.YahooMailNeo@web39405.mail.mud.yahoo.com> Date: Thu, 20 Sep 2012 11:02:30 -0700 (PDT) From: Matthias Blankenhaus To: "xen-users@lists.xen.org" In-Reply-To: MIME-Version: 1.0 Subject: Re: [Xen-users] Running Linux VM in para mode with Intel VT enabled X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list Reply-To: Matthias Blankenhaus List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============0937135777534634169==" Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org --===============0937135777534634169== Content-Type: multipart/alternative; boundary="-154443274-1924262819-1348164150=:25406" ---154443274-1924262819-1348164150=:25406 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: quoted-printable =0A=0A=0A=0A=0A>________________________________=0A> From: kevin parker =0A>To: xen-users@lists.xen.org =0A>Sent: Thursday,= September 20, 2012 8:34 AM=0A>Subject: [Xen-users] Running Linux VM in par= a mode with Intel VT enabled=0A> =0A>=0A>Hi all,=0A>=A0 =A0 =A0 =A0=A0I am = having a server running XEN,with ubuntu 12.04 as Domain 0.=0A>Intel VT is t= urned on by default and i dont want to run any Windows OS as VM.In that cas= e=0A>1. how can i makesure that all the created VM will be in=0Aparavirtual= ized mode even with VT enabled? =0A>I have heard that in Full Virtualizatio= n hypervisor needs to work hard for emulating all the underlying hardware,w= hich may reduce performance for too much i/o specific applications when com= pared to para mode.=0AThe difference between running a guest vm as a PV vs.= as a HVM is controlled by the guest vm's configuration.=A0=A0 In particula= r, if your guest vm's configuration contains the following lines, then the = guest would be launched as a HVM:=0A=0Akernel =3D '/usr/lib/xen-4.0/boot/hv= mloader'=0Abuilder=3D'hvm'=0AThus, if you want to ensure that your Ubunto g= uests runs as a PV you need to specify something along the following lines:= =0Akernel =3D '/boot/vmlinuz-2.6.33.20.x86_64'=A0=A0=A0=A0=A0=A0 # substitu= te this with your specific Ubuntu kernel=0Aramdisk =3D '/boot/initrd-2.6.33= .20.x86_64'=A0 # substitute this with your specific Ubuntu ramdisk, if you = want to use it, this is optional=0A=0Aextra =3D 'selinux=3D0 elevator=3Dnoo= p'=A0 # not strictly necessary, but allows you to pass parameters during bo= ot to the kernel=0A=0AFor more infos check this out: http://xenbits.xen.org= /docs/unstable/man/xl.cfg.5.html#paravirtualised__pv__guest_specific_option= s=0A=0A=0A=0A2.Can i be able to run Linux VM in para mode with VT enabled? = 3.Will simply turning on VT support changes virtualization type from para t= o full for all vms created on that machine? 4.Will there be any performance= improvement for VM running Linux OS if VT is enabled?=0A>5.Is it normal to= miss vmx flag in /proc/cpuinfo after booting to XEN kernel,even with VT en= abled?=0A>=0A>=0A>Regards,=0A>Kevin=0A>____________________________________= ___________=0A>Xen-users mailing list=0A>Xen-users@lists.xen.org=0A>http://= lists.xen.org/xen-users=0A>=0A> ---154443274-1924262819-1348164150=:25406 Content-Type: text/html; charset=iso-8859-1 Content-Transfer-Encoding: quoted-printable


From: kevin parker <= ;kevin.parker092@gmail.com>
To= : xen-users@lists.xen.org
Sent: Thursday, September 20, 2012 8:34 AM
Subject: [Xen-users] Running Linux VM in para mode with Int= el VT enabled

=0A
Hi all,        I am having = a server running XEN,with ubuntu 12.04 as Domain 0.
=0A
=0AIntel VT is turned on by defaul= t and i dont want to run any Windows OS as VM.In that case
1. how can i makesure that all =
the created VM will be in=0Aparavirtualized mode even with VT enabled?=0A
=0AI have heard= that in Full Virtualization hypervisor needs to work hard for emulating al= l the underlying hardware,which may reduce performance for too much i/o spe= cific applications when compared to para mode.
The difference between running a guest vm = as a PV vs. as a HVM is controlled by the guest vm's configuration. &n= bsp; In particular, if your guest vm's configuration contains the following= lines, then the guest would be launched as a HVM:
kernel =3D '/usr/lib/xen-4.0/boot/hvmloader'=0Abuilder=
=3D'hvm'
Thus, if you want to ensure that your Ubunto guests runs as a PV you nee= d to specify something along the following lines:
kernel =3D '/boot/vmlinuz-2.6.3= 3.20.x86_64'       # substitute this with you= r specific Ubuntu kernel
ramdisk =3D '/boot/initrd-2.6.33.20.x= 86_64'  # substitute this with your specific Ubuntu ramdisk, if you want to use it, this is optional
extra = =3D 'selinux=3D0 elevator=3Dnoop'  # not strictly necessary, but allow= s you to pass parameters during boot to the kernel
For more infos check = this out: http://xenbits.xen.org/docs/unstable/man/xl.cfg.5.html#paravirtua= lised__pv__guest_specific_options


2.Can i be=
 able to run Linux VM in para mode with VT enabled?=0A=0A3.Will simply turn=
ing on VT support changes virtualization type from para to full for all vms=
 created on that machine?=0A=0A4.Will there be any performance improvement =
for VM running Linux OS if VT is enabled?
=
5.Is it normal to miss vmx flag in /proc/cpuinfo after booting to XEN ke=
rnel,even with VT enabled?

Regards,
Kevin
=0A

_______________________________= ________________
Xen-users mailing list
Xen-users@lists.xe= n.org
h= ttp://lists.xen.org/xen-users

=
---154443274-1924262819-1348164150=:25406-- --===============0937135777534634169== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users --===============0937135777534634169==-- From xen-users-bounces@lists.xen.org Thu Sep 20 18:07:46 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Thu, 20 Sep 2012 18:07:46 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TEl9K-0008Cv-3A; Thu, 20 Sep 2012 18:06:54 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TEl9I-0008Cp-I4 for xen-users@lists.xen.org; Thu, 20 Sep 2012 18:06:52 +0000 Received: from [85.158.139.211:55495] by server-5.bemta-5.messagelabs.com id F1/89-30514-B3B5B505; Thu, 20 Sep 2012 18:06:51 +0000 X-Env-Sender: matthiasblankenhaus@yahoo.com X-Msg-Ref: server-12.tower-206.messagelabs.com!1348164410!18361436!1 X-Originating-IP: [98.138.229.25] X-SpamReason: No, hits=0.6 required=7.0 tests=HTML_40_50,HTML_MESSAGE, ML_RADAR_SPEW_LINKS_12,ML_RADAR_SPEW_LINKS_14,spamassassin: X-StarScan-Received: X-StarScan-Version: 6.6.1.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 1989 invoked from network); 20 Sep 2012 18:06:51 -0000 Received: from nm32.bullet.mail.ne1.yahoo.com (HELO nm32.bullet.mail.ne1.yahoo.com) (98.138.229.25) by server-12.tower-206.messagelabs.com with SMTP; 20 Sep 2012 18:06:51 -0000 Received: from [98.138.90.48] by nm32.bullet.mail.ne1.yahoo.com with NNFMP; 20 Sep 2012 18:06:50 -0000 Received: from [98.138.89.175] by tm1.bullet.mail.ne1.yahoo.com with NNFMP; 20 Sep 2012 18:06:50 -0000 Received: from [127.0.0.1] by omp1031.mail.ne1.yahoo.com with NNFMP; 20 Sep 2012 18:06:50 -0000 X-Yahoo-Newman-Property: ymail-3 X-Yahoo-Newman-Id: 364652.4129.bm@omp1031.mail.ne1.yahoo.com Received: (qmail 94859 invoked by uid 60001); 20 Sep 2012 18:06:50 -0000 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.com; s=s1024; t=1348164409; bh=otUl4ijtea86+YPOjs647BYvIWqyceIfWldiRIVQRrw=; h=X-YMail-OSG:Received:X-Mailer:Message-ID:Date:From:Reply-To:Subject:To:MIME-Version:Content-Type; b=aFlWw3tdPu4bcrHrkW8OGHUSsSIYlv/8PhnaAuyZmFP02o5/G7VC/dbgyQNsi5X+IcC0HQ7r3lfBSom4tm5s6+erxWqAcls/0VmGUEWOPStMu47l310sCuwKOmyCaEp5xW/elgREcF6psidADFUi2oSYRXlhLvhVSgBNPoIo5hM= DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com; h=X-YMail-OSG:Received:X-Mailer:Message-ID:Date:From:Reply-To:Subject:To:MIME-Version:Content-Type; b=K7aSMF9rX3cH1Ug8K0Z9TIzK9PBFLS5SIsTawy0fiJfwbOg9jPePPYW9VfHrxJyOY5HrKG2edpHWvdUsn0SqpPQRNtadixY654yvVm2BNEf7LamLUqrcAhhs/5YeCWNkkl0cFjtLy2te4OEGwTWycYiavAqdvmP5XMSRr+AMW7U=; X-YMail-OSG: QP_QSa4VM1mwo.CSCQ0oey08fc61LwIk.sNh18vbqNJsbnd ZoJStbzQdsbil0QBn9MsxtmyEyp6RcbQ6AduD_qv98ocX7BPij3ckZp9B02l 7UJd5mUTGAHv6TUDHNZ3rOwUj.JO6CyjksCNTItdiRopZ6K8DDAoV2fZNk8t ptoJ6URp.hjQWdPcjyTPhEuMVAUP9WGdIMyaTAcmUbWR6dSj2VgP_RZdUIhn dI.US9sOaLUNsA7Xkks2KcS_gYsgUnqSwzEXXZWRK0LHWJgErJRxcBys10ac DSghxXAlzMdWuBg_zDRSuX918swhuCCd7QVIQsMait8On0i_d4.DlRbbhr8_ ZUQsnaDMgK_P5oPOwywKbRFLvM8zLauaA4bhf48UlbE4Bgz42PnHLQJ0f7Qz RzrhbSwW7aZsmp17HOX70819Y_hW_6IAjAAgHfULgKY44J8EiBSEffKmJaZU ohVnfU68uvQaOszY1cTjoa1gwghYl7ozXAYEhB1xOOVDNtw-- Received: from [67.170.238.86] by web39403.mail.mud.yahoo.com via HTTP; Thu, 20 Sep 2012 11:06:49 PDT X-Mailer: YahooMailWebService/0.8.121.416 Message-ID: <1348164409.93241.YahooMailNeo@web39403.mail.mud.yahoo.com> Date: Thu, 20 Sep 2012 11:06:49 -0700 (PDT) From: Matthias Blankenhaus To: "xen-users@lists.xen.org" MIME-Version: 1.0 Subject: [Xen-users] Simplest way to create pv guest with xl w/o qemu X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list Reply-To: Matthias Blankenhaus List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============7410233296541526934==" Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org --===============7410233296541526934== Content-Type: multipart/alternative; boundary="908107500-1905675103-1348164409=:93241" --908107500-1905675103-1348164409=:93241 Content-Type: text/plain; charset=us-ascii Hello ! What is the simplest way to create a PV guest using Xen 4.x that runs without a qemu process on DOM0 ? I am specifically interested in the block device aspect of this. Thanx, Matthias --908107500-1905675103-1348164409=:93241 Content-Type: text/html; charset=us-ascii
Hello !

What is the simplest way to create a PV guest using Xen 4.x that runs without a qemu process on DOM0 ? I am specifically
interested in the block device aspect of this.

Thanx,
Matthias

--908107500-1905675103-1348164409=:93241-- --===============7410233296541526934== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users --===============7410233296541526934==-- From xen-users-bounces@lists.xen.org Thu Sep 20 18:07:46 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Thu, 20 Sep 2012 18:07:46 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TEl9K-0008Cv-3A; Thu, 20 Sep 2012 18:06:54 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TEl9I-0008Cp-I4 for xen-users@lists.xen.org; Thu, 20 Sep 2012 18:06:52 +0000 Received: from [85.158.139.211:55495] by server-5.bemta-5.messagelabs.com id F1/89-30514-B3B5B505; Thu, 20 Sep 2012 18:06:51 +0000 X-Env-Sender: matthiasblankenhaus@yahoo.com X-Msg-Ref: server-12.tower-206.messagelabs.com!1348164410!18361436!1 X-Originating-IP: [98.138.229.25] X-SpamReason: No, hits=0.6 required=7.0 tests=HTML_40_50,HTML_MESSAGE, ML_RADAR_SPEW_LINKS_12,ML_RADAR_SPEW_LINKS_14,spamassassin: X-StarScan-Received: X-StarScan-Version: 6.6.1.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 1989 invoked from network); 20 Sep 2012 18:06:51 -0000 Received: from nm32.bullet.mail.ne1.yahoo.com (HELO nm32.bullet.mail.ne1.yahoo.com) (98.138.229.25) by server-12.tower-206.messagelabs.com with SMTP; 20 Sep 2012 18:06:51 -0000 Received: from [98.138.90.48] by nm32.bullet.mail.ne1.yahoo.com with NNFMP; 20 Sep 2012 18:06:50 -0000 Received: from [98.138.89.175] by tm1.bullet.mail.ne1.yahoo.com with NNFMP; 20 Sep 2012 18:06:50 -0000 Received: from [127.0.0.1] by omp1031.mail.ne1.yahoo.com with NNFMP; 20 Sep 2012 18:06:50 -0000 X-Yahoo-Newman-Property: ymail-3 X-Yahoo-Newman-Id: 364652.4129.bm@omp1031.mail.ne1.yahoo.com Received: (qmail 94859 invoked by uid 60001); 20 Sep 2012 18:06:50 -0000 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.com; s=s1024; t=1348164409; bh=otUl4ijtea86+YPOjs647BYvIWqyceIfWldiRIVQRrw=; h=X-YMail-OSG:Received:X-Mailer:Message-ID:Date:From:Reply-To:Subject:To:MIME-Version:Content-Type; b=aFlWw3tdPu4bcrHrkW8OGHUSsSIYlv/8PhnaAuyZmFP02o5/G7VC/dbgyQNsi5X+IcC0HQ7r3lfBSom4tm5s6+erxWqAcls/0VmGUEWOPStMu47l310sCuwKOmyCaEp5xW/elgREcF6psidADFUi2oSYRXlhLvhVSgBNPoIo5hM= DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com; h=X-YMail-OSG:Received:X-Mailer:Message-ID:Date:From:Reply-To:Subject:To:MIME-Version:Content-Type; b=K7aSMF9rX3cH1Ug8K0Z9TIzK9PBFLS5SIsTawy0fiJfwbOg9jPePPYW9VfHrxJyOY5HrKG2edpHWvdUsn0SqpPQRNtadixY654yvVm2BNEf7LamLUqrcAhhs/5YeCWNkkl0cFjtLy2te4OEGwTWycYiavAqdvmP5XMSRr+AMW7U=; X-YMail-OSG: QP_QSa4VM1mwo.CSCQ0oey08fc61LwIk.sNh18vbqNJsbnd ZoJStbzQdsbil0QBn9MsxtmyEyp6RcbQ6AduD_qv98ocX7BPij3ckZp9B02l 7UJd5mUTGAHv6TUDHNZ3rOwUj.JO6CyjksCNTItdiRopZ6K8DDAoV2fZNk8t ptoJ6URp.hjQWdPcjyTPhEuMVAUP9WGdIMyaTAcmUbWR6dSj2VgP_RZdUIhn dI.US9sOaLUNsA7Xkks2KcS_gYsgUnqSwzEXXZWRK0LHWJgErJRxcBys10ac DSghxXAlzMdWuBg_zDRSuX918swhuCCd7QVIQsMait8On0i_d4.DlRbbhr8_ ZUQsnaDMgK_P5oPOwywKbRFLvM8zLauaA4bhf48UlbE4Bgz42PnHLQJ0f7Qz RzrhbSwW7aZsmp17HOX70819Y_hW_6IAjAAgHfULgKY44J8EiBSEffKmJaZU ohVnfU68uvQaOszY1cTjoa1gwghYl7ozXAYEhB1xOOVDNtw-- Received: from [67.170.238.86] by web39403.mail.mud.yahoo.com via HTTP; Thu, 20 Sep 2012 11:06:49 PDT X-Mailer: YahooMailWebService/0.8.121.416 Message-ID: <1348164409.93241.YahooMailNeo@web39403.mail.mud.yahoo.com> Date: Thu, 20 Sep 2012 11:06:49 -0700 (PDT) From: Matthias Blankenhaus To: "xen-users@lists.xen.org" MIME-Version: 1.0 Subject: [Xen-users] Simplest way to create pv guest with xl w/o qemu X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list Reply-To: Matthias Blankenhaus List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============7410233296541526934==" Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org --===============7410233296541526934== Content-Type: multipart/alternative; boundary="908107500-1905675103-1348164409=:93241" --908107500-1905675103-1348164409=:93241 Content-Type: text/plain; charset=us-ascii Hello ! What is the simplest way to create a PV guest using Xen 4.x that runs without a qemu process on DOM0 ? I am specifically interested in the block device aspect of this. Thanx, Matthias --908107500-1905675103-1348164409=:93241 Content-Type: text/html; charset=us-ascii
Hello !

What is the simplest way to create a PV guest using Xen 4.x that runs without a qemu process on DOM0 ? I am specifically
interested in the block device aspect of this.

Thanx,
Matthias

--908107500-1905675103-1348164409=:93241-- --===============7410233296541526934== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users --===============7410233296541526934==-- From xen-users-bounces@lists.xen.org Thu Sep 20 21:13:39 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Thu, 20 Sep 2012 21:13:39 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TEo2l-0001qI-Gg; Thu, 20 Sep 2012 21:12:19 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TEo2k-0001qD-1i for xen-users@lists.xen.org; Thu, 20 Sep 2012 21:12:18 +0000 Received: from [85.158.143.35:13973] by server-3.bemta-4.messagelabs.com id 09/CA-10986-1B68B505; Thu, 20 Sep 2012 21:12:17 +0000 X-Env-Sender: shades_of_grey@earthlink.net X-Msg-Ref: server-15.tower-21.messagelabs.com!1348175535!14511896!1 X-Originating-IP: [209.86.89.62] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: QmFkIElQOiAyMDkuODYuODkuNjIgPT4gMzc1Ng==\n,sa_preprocessor: QmFkIElQOiAyMDkuODYuODkuNjIgPT4gMzc1Ng==\n,ML_RADAR_SPEW_LINKS_14, spamassassin: X-StarScan-Received: X-StarScan-Version: 6.6.1.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 20062 invoked from network); 20 Sep 2012 21:12:16 -0000 Received: from elasmtp-dupuy.atl.sa.earthlink.net (HELO elasmtp-dupuy.atl.sa.earthlink.net) (209.86.89.62) by server-15.tower-21.messagelabs.com with SMTP; 20 Sep 2012 21:12:16 -0000 DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=dk20050327; d=earthlink.net; b=c3LBd9vvoPCpUjH62bVniphhzzfshccBsllkKKZcwFP6Jywu407EeOpgljhZJidD; h=Received:Message-ID:Date:From:User-Agent:MIME-Version:To:Subject:Content-Type:Content-Transfer-Encoding:X-ELNK-Trace:X-Originating-IP; Received: from [66.167.250.229] (helo=[192.168.1.13]) by elasmtp-dupuy.atl.sa.earthlink.net with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.67) (envelope-from ) id 1TEo2h-0006xC-Es; Thu, 20 Sep 2012 17:12:15 -0400 Message-ID: <505B86AE.9040507@earthlink.net> Date: Thu, 20 Sep 2012 17:12:14 -0400 From: ShadesOfGrey User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:15.0) Gecko/20120907 Thunderbird/15.0.1 MIME-Version: 1.0 To: xen-users@lists.xen.org, kvm@vger.kernel.org X-ELNK-Trace: 0fe7bc40aa99bc8fc963772e86942a7b94f5150ab1c16ac0485087bba56e60097d4035fc596bf455dc8e0ae6be31778a350badd9bab72f9c350badd9bab72f9c X-Originating-IP: 66.167.250.229 Subject: [Xen-users] Recommendations for Virtulization Hardware X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset="us-ascii"; Format="flowed" Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org I'm looking to build a new personal computer. I want it to function as a Linux desktop, provide network services for my home, and lastly, occasional Windows gaming. From what I've gathered, virtualization using a Type 1 Hypervisor supporting PCI/VGA pass-through like KVM or Xen would be an attractive solution for my needs. For reference, reading these threads on Ars Technica may be helpful to understand where I'm coming from, http://arstechnica.com/civis/viewtopic.php?f=6&t=1175674 and http://arstechnica.com/civis/viewtopic.php?f=11&t=1181867. But basically, I use Linux as my primary OS and would rather avoid dual booting or building two boxes just to play Windows games when I want to play Windows games. I'm also intrigued by the concept of virtualization and would like to experiment with it as a solution for my case. My problem is isolating which hardware to choose, specifically which combination of CPU, motherboard and video card. Previously I had been relying on web searches to glean information from gaming and enthusiast web sites and tech specs from motherboard manufacturers. After what I learned during my participation in the referenced threads at Ars Technica, I find myself back at square one. Instead of trying to guess what hardware support KVM & Xen, and vice versa. I'd like to know what hardware KVM & Xen users are actually using to run KVM & Xen? Particularly with consideration for 3D gaming and current generation hardware, BTW. If there is need for further clarification, I'll answer any queries you might have. _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Thu Sep 20 21:13:39 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Thu, 20 Sep 2012 21:13:39 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TEo2l-0001qI-Gg; Thu, 20 Sep 2012 21:12:19 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TEo2k-0001qD-1i for xen-users@lists.xen.org; Thu, 20 Sep 2012 21:12:18 +0000 Received: from [85.158.143.35:13973] by server-3.bemta-4.messagelabs.com id 09/CA-10986-1B68B505; Thu, 20 Sep 2012 21:12:17 +0000 X-Env-Sender: shades_of_grey@earthlink.net X-Msg-Ref: server-15.tower-21.messagelabs.com!1348175535!14511896!1 X-Originating-IP: [209.86.89.62] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: QmFkIElQOiAyMDkuODYuODkuNjIgPT4gMzc1Ng==\n,sa_preprocessor: QmFkIElQOiAyMDkuODYuODkuNjIgPT4gMzc1Ng==\n,ML_RADAR_SPEW_LINKS_14, spamassassin: X-StarScan-Received: X-StarScan-Version: 6.6.1.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 20062 invoked from network); 20 Sep 2012 21:12:16 -0000 Received: from elasmtp-dupuy.atl.sa.earthlink.net (HELO elasmtp-dupuy.atl.sa.earthlink.net) (209.86.89.62) by server-15.tower-21.messagelabs.com with SMTP; 20 Sep 2012 21:12:16 -0000 DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=dk20050327; d=earthlink.net; b=c3LBd9vvoPCpUjH62bVniphhzzfshccBsllkKKZcwFP6Jywu407EeOpgljhZJidD; h=Received:Message-ID:Date:From:User-Agent:MIME-Version:To:Subject:Content-Type:Content-Transfer-Encoding:X-ELNK-Trace:X-Originating-IP; Received: from [66.167.250.229] (helo=[192.168.1.13]) by elasmtp-dupuy.atl.sa.earthlink.net with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.67) (envelope-from ) id 1TEo2h-0006xC-Es; Thu, 20 Sep 2012 17:12:15 -0400 Message-ID: <505B86AE.9040507@earthlink.net> Date: Thu, 20 Sep 2012 17:12:14 -0400 From: ShadesOfGrey User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:15.0) Gecko/20120907 Thunderbird/15.0.1 MIME-Version: 1.0 To: xen-users@lists.xen.org, kvm@vger.kernel.org X-ELNK-Trace: 0fe7bc40aa99bc8fc963772e86942a7b94f5150ab1c16ac0485087bba56e60097d4035fc596bf455dc8e0ae6be31778a350badd9bab72f9c350badd9bab72f9c X-Originating-IP: 66.167.250.229 Subject: [Xen-users] Recommendations for Virtulization Hardware X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset="us-ascii"; Format="flowed" Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org I'm looking to build a new personal computer. I want it to function as a Linux desktop, provide network services for my home, and lastly, occasional Windows gaming. From what I've gathered, virtualization using a Type 1 Hypervisor supporting PCI/VGA pass-through like KVM or Xen would be an attractive solution for my needs. For reference, reading these threads on Ars Technica may be helpful to understand where I'm coming from, http://arstechnica.com/civis/viewtopic.php?f=6&t=1175674 and http://arstechnica.com/civis/viewtopic.php?f=11&t=1181867. But basically, I use Linux as my primary OS and would rather avoid dual booting or building two boxes just to play Windows games when I want to play Windows games. I'm also intrigued by the concept of virtualization and would like to experiment with it as a solution for my case. My problem is isolating which hardware to choose, specifically which combination of CPU, motherboard and video card. Previously I had been relying on web searches to glean information from gaming and enthusiast web sites and tech specs from motherboard manufacturers. After what I learned during my participation in the referenced threads at Ars Technica, I find myself back at square one. Instead of trying to guess what hardware support KVM & Xen, and vice versa. I'd like to know what hardware KVM & Xen users are actually using to run KVM & Xen? Particularly with consideration for 3D gaming and current generation hardware, BTW. If there is need for further clarification, I'll answer any queries you might have. _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Thu Sep 20 21:34:52 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Thu, 20 Sep 2012 21:34:52 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TEoNZ-0002uY-CU; Thu, 20 Sep 2012 21:33:49 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TEoNX-0002uP-QF for xen-users@lists.xen.org; Thu, 20 Sep 2012 21:33:47 +0000 Received: from [85.158.143.99:64232] by server-2.bemta-4.messagelabs.com id E2/4E-06610-BBB8B505; Thu, 20 Sep 2012 21:33:47 +0000 X-Env-Sender: nunomagalhaes@eu.ipp.pt X-Msg-Ref: server-15.tower-216.messagelabs.com!1348176825!31170444!1 X-Originating-IP: [209.85.214.173] X-SpamReason: No, hits=0.3 required=7.0 tests=RCVD_BY_IP X-StarScan-Received: X-StarScan-Version: 6.6.1.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 16316 invoked from network); 20 Sep 2012 21:33:46 -0000 Received: from mail-ob0-f173.google.com (HELO mail-ob0-f173.google.com) (209.85.214.173) by server-15.tower-216.messagelabs.com with RC4-SHA encrypted SMTP; 20 Sep 2012 21:33:46 -0000 Received: by obbta14 with SMTP id ta14so3378230obb.32 for ; Thu, 20 Sep 2012 14:33:45 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :content-type:content-transfer-encoding:x-gm-message-state; bh=UvOhqss6mfTpw7H6Smjyy7AsBcdeOp+TCjHB4CxGuug=; b=O0LmxBowlDHXcOd+4uEFw2y2/Lc72cV0PHc4Iz/EyCVm0w3cQr/wf+fxYXgFjGhl4s Tkho1yLRJxsqwndWS8H/bS5ksZ+wyV8FQOwfnkY4PaR8CZhPcUBS999+swpdWeA5V+mM Y+Q1GKACLtqFD5orRWtL6QMfKHt0We6jNgDJoQV/TEMCJp4Cd+5butEq87g6LyyndOei qVYJvY62JTJPLNnLcTAVdX7FXBrgnlxGJineTfKGHP34Vpx1Hi2m6s732L7KULG/G7fZ jCoBQatigKagbqiBm5+KFtMWIJt4sqWSvdKjP4VXM12UGRAvNoBc5ZqdBQ+6SPyLPEvP SfzA== Received: by 10.60.19.195 with SMTP id h3mr2332995oee.102.1348176825105; Thu, 20 Sep 2012 14:33:45 -0700 (PDT) MIME-Version: 1.0 Received: by 10.60.17.195 with HTTP; Thu, 20 Sep 2012 14:33:24 -0700 (PDT) In-Reply-To: <505B86AE.9040507@earthlink.net> References: <505B86AE.9040507@earthlink.net> From: =?UTF-8?Q?Nuno_Magalh=C3=A3es?= Date: Thu, 20 Sep 2012 22:33:24 +0100 Message-ID: To: xen-users@lists.xen.org, kvm@vger.kernel.org X-Gm-Message-State: ALoCoQkgld2cuS+2orsUUqEGINBGPrD45keWJRw5fssLzXK/8Ic8nyF1VrJYkC5vWWolRnV+EVf2 Subject: Re: [Xen-users] Recommendations for Virtulization Hardware X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: base64 Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org SGksCgpKdXN0IGEgWGVuIG5ld2JpZSBteXNlbGYsIGJ1dCBmcm9tIHdoYXQgaSd2ZSBnYXRoZXJl ZCBhbmQgZmlkZGxlZCwgWGVuCihQKVZNcyBkb24ndCBjb21lIHdpdGggYSBncmFwaGljcyBjYXJk LiBZb3UnZCBoYXZlIHRvIHJlbW90ZSB0byB5b3VyCldpbmRvd3MgSFZNIHRvIHBsYXkgZ2FtZXMu IFlvdSBjYW4gZmlkZGxlIHdpdGggUENJIHBhc3MgdGhyb3VnaCBmb3IKc29tZSB2aWRlbyBjYXJk cyBhbmQgdGhlcmUncyBzb21lIFZHQSBwYXNzdHJvdWdoIGFzIHdlbGwsIGJ1dCBpIGRvbid0CnRo aW5rIHJ1bm5pbmcgYSByZWNlbnQgZ2FtZSBvbiBhIFZNIHdvdWxkIHByb3ZpZGUgZ29vZCByZXN1 bHRzIChpJ20KdGhpbmtpbmcgRlBTcyBoZXJlLCBub3Qgc29saXRhaXJlIG9yIHNpbWNpdHkpLgoK QXMgZm9yIGhhcmR3YXJlIGkgY29uc2lkZXJlZCBhbiBBVEkvQXN1cyBib2FyZCB3aXRoIGEgUGhl bm9tIElJIFg2IGFuZAoxNkdCIG9yIEREUjMgYSB3aGlsZSBhZ28sIHBsdXMgYm94LCBQU1UsIG5v IGRpc2tzLCBhcm91bmQgNTAw4oKsLi4uIFlNTVYKYW5kIHlvdXIgbmVlZHMgYXMgd2VsbC4KCkp1 c3QgbXkgaWxsLWluZm9ybWVkIDJjLiBIVEgKCk51bm8KCl9fX19fX19fX19fX19fX19fX19fX19f X19fX19fX19fX19fX19fX19fX19fX19fClhlbi11c2VycyBtYWlsaW5nIGxpc3QKWGVuLXVzZXJz QGxpc3RzLnhlbi5vcmcKaHR0cDovL2xpc3RzLnhlbi5vcmcveGVuLXVzZXJz From xen-users-bounces@lists.xen.org Thu Sep 20 21:34:52 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Thu, 20 Sep 2012 21:34:52 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TEoNZ-0002uY-CU; Thu, 20 Sep 2012 21:33:49 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TEoNX-0002uP-QF for xen-users@lists.xen.org; Thu, 20 Sep 2012 21:33:47 +0000 Received: from [85.158.143.99:64232] by server-2.bemta-4.messagelabs.com id E2/4E-06610-BBB8B505; Thu, 20 Sep 2012 21:33:47 +0000 X-Env-Sender: nunomagalhaes@eu.ipp.pt X-Msg-Ref: server-15.tower-216.messagelabs.com!1348176825!31170444!1 X-Originating-IP: [209.85.214.173] X-SpamReason: No, hits=0.3 required=7.0 tests=RCVD_BY_IP X-StarScan-Received: X-StarScan-Version: 6.6.1.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 16316 invoked from network); 20 Sep 2012 21:33:46 -0000 Received: from mail-ob0-f173.google.com (HELO mail-ob0-f173.google.com) (209.85.214.173) by server-15.tower-216.messagelabs.com with RC4-SHA encrypted SMTP; 20 Sep 2012 21:33:46 -0000 Received: by obbta14 with SMTP id ta14so3378230obb.32 for ; Thu, 20 Sep 2012 14:33:45 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :content-type:content-transfer-encoding:x-gm-message-state; bh=UvOhqss6mfTpw7H6Smjyy7AsBcdeOp+TCjHB4CxGuug=; b=O0LmxBowlDHXcOd+4uEFw2y2/Lc72cV0PHc4Iz/EyCVm0w3cQr/wf+fxYXgFjGhl4s Tkho1yLRJxsqwndWS8H/bS5ksZ+wyV8FQOwfnkY4PaR8CZhPcUBS999+swpdWeA5V+mM Y+Q1GKACLtqFD5orRWtL6QMfKHt0We6jNgDJoQV/TEMCJp4Cd+5butEq87g6LyyndOei qVYJvY62JTJPLNnLcTAVdX7FXBrgnlxGJineTfKGHP34Vpx1Hi2m6s732L7KULG/G7fZ jCoBQatigKagbqiBm5+KFtMWIJt4sqWSvdKjP4VXM12UGRAvNoBc5ZqdBQ+6SPyLPEvP SfzA== Received: by 10.60.19.195 with SMTP id h3mr2332995oee.102.1348176825105; Thu, 20 Sep 2012 14:33:45 -0700 (PDT) MIME-Version: 1.0 Received: by 10.60.17.195 with HTTP; Thu, 20 Sep 2012 14:33:24 -0700 (PDT) In-Reply-To: <505B86AE.9040507@earthlink.net> References: <505B86AE.9040507@earthlink.net> From: =?UTF-8?Q?Nuno_Magalh=C3=A3es?= Date: Thu, 20 Sep 2012 22:33:24 +0100 Message-ID: To: xen-users@lists.xen.org, kvm@vger.kernel.org X-Gm-Message-State: ALoCoQkgld2cuS+2orsUUqEGINBGPrD45keWJRw5fssLzXK/8Ic8nyF1VrJYkC5vWWolRnV+EVf2 Subject: Re: [Xen-users] Recommendations for Virtulization Hardware X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: base64 Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org SGksCgpKdXN0IGEgWGVuIG5ld2JpZSBteXNlbGYsIGJ1dCBmcm9tIHdoYXQgaSd2ZSBnYXRoZXJl ZCBhbmQgZmlkZGxlZCwgWGVuCihQKVZNcyBkb24ndCBjb21lIHdpdGggYSBncmFwaGljcyBjYXJk LiBZb3UnZCBoYXZlIHRvIHJlbW90ZSB0byB5b3VyCldpbmRvd3MgSFZNIHRvIHBsYXkgZ2FtZXMu IFlvdSBjYW4gZmlkZGxlIHdpdGggUENJIHBhc3MgdGhyb3VnaCBmb3IKc29tZSB2aWRlbyBjYXJk cyBhbmQgdGhlcmUncyBzb21lIFZHQSBwYXNzdHJvdWdoIGFzIHdlbGwsIGJ1dCBpIGRvbid0CnRo aW5rIHJ1bm5pbmcgYSByZWNlbnQgZ2FtZSBvbiBhIFZNIHdvdWxkIHByb3ZpZGUgZ29vZCByZXN1 bHRzIChpJ20KdGhpbmtpbmcgRlBTcyBoZXJlLCBub3Qgc29saXRhaXJlIG9yIHNpbWNpdHkpLgoK QXMgZm9yIGhhcmR3YXJlIGkgY29uc2lkZXJlZCBhbiBBVEkvQXN1cyBib2FyZCB3aXRoIGEgUGhl bm9tIElJIFg2IGFuZAoxNkdCIG9yIEREUjMgYSB3aGlsZSBhZ28sIHBsdXMgYm94LCBQU1UsIG5v IGRpc2tzLCBhcm91bmQgNTAw4oKsLi4uIFlNTVYKYW5kIHlvdXIgbmVlZHMgYXMgd2VsbC4KCkp1 c3QgbXkgaWxsLWluZm9ybWVkIDJjLiBIVEgKCk51bm8KCl9fX19fX19fX19fX19fX19fX19fX19f X19fX19fX19fX19fX19fX19fX19fX19fClhlbi11c2VycyBtYWlsaW5nIGxpc3QKWGVuLXVzZXJz QGxpc3RzLnhlbi5vcmcKaHR0cDovL2xpc3RzLnhlbi5vcmcveGVuLXVzZXJz From xen-users-bounces@lists.xen.org Thu Sep 20 22:00:00 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Thu, 20 Sep 2012 22:00:00 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TEoly-0003K2-W5; Thu, 20 Sep 2012 21:59:02 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TEogw-0003J0-JG for xen-users@lists.xen.org; Thu, 20 Sep 2012 21:53:50 +0000 Received: from [85.158.139.211:41206] by server-10.bemta-5.messagelabs.com id 28/D1-10969-D609B505; Thu, 20 Sep 2012 21:53:49 +0000 X-Env-Sender: alex.williamson@redhat.com X-Msg-Ref: server-13.tower-206.messagelabs.com!1348178028!15389908!1 X-Originating-IP: [209.132.183.28] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogMjA5LjEzMi4xODMuMjggPT4gNTcwODk=\n X-StarScan-Received: X-StarScan-Version: 6.6.1.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 5012 invoked from network); 20 Sep 2012 21:53:49 -0000 Received: from mx1.redhat.com (HELO mx1.redhat.com) (209.132.183.28) by server-13.tower-206.messagelabs.com with SMTP; 20 Sep 2012 21:53:49 -0000 Received: from int-mx01.intmail.prod.int.phx2.redhat.com (int-mx01.intmail.prod.int.phx2.redhat.com [10.5.11.11]) by mx1.redhat.com (8.14.4/8.14.4) with ESMTP id q8KLrk51009272 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Thu, 20 Sep 2012 17:53:46 -0400 Received: from [10.3.113.111] (ovpn-113-111.phx2.redhat.com [10.3.113.111]) by int-mx01.intmail.prod.int.phx2.redhat.com (8.13.8/8.13.8) with ESMTP id q8KLrjL9026156; Thu, 20 Sep 2012 17:53:46 -0400 Message-ID: <1348178025.2320.23.camel@ul30vt.home> From: Alex Williamson To: ShadesOfGrey Date: Thu, 20 Sep 2012 15:53:45 -0600 In-Reply-To: <505B86AE.9040507@earthlink.net> References: <505B86AE.9040507@earthlink.net> Mime-Version: 1.0 X-Scanned-By: MIMEDefang 2.67 on 10.5.11.11 X-Mailman-Approved-At: Thu, 20 Sep 2012 21:59:02 +0000 Cc: xen-users@lists.xen.org, kvm@vger.kernel.org Subject: Re: [Xen-users] Recommendations for Virtulization Hardware X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org On Thu, 2012-09-20 at 17:12 -0400, ShadesOfGrey wrote: > I'm looking to build a new personal computer. I want it to function as > a Linux desktop, provide network services for my home, and lastly, > occasional Windows gaming. From what I've gathered, virtualization > using a Type 1 Hypervisor supporting PCI/VGA pass-through like KVM or > Xen would be an attractive solution for my needs. For reference, > reading these threads on Ars Technica may be helpful to understand where > I'm coming from, > http://arstechnica.com/civis/viewtopic.php?f=6&t=1175674 and > http://arstechnica.com/civis/viewtopic.php?f=11&t=1181867. But > basically, I use Linux as my primary OS and would rather avoid dual > booting or building two boxes just to play Windows games when I want to > play Windows games. I'm also intrigued by the concept of virtualization > and would like to experiment with it as a solution for my case. > > My problem is isolating which hardware to choose, specifically which > combination of CPU, motherboard and video card. Previously I had been > relying on web searches to glean information from gaming and enthusiast > web sites and tech specs from motherboard manufacturers. After what I > learned during my participation in the referenced threads at Ars > Technica, I find myself back at square one. Instead of trying to guess > what hardware support KVM & Xen, and vice versa. I'd like to know what > hardware KVM & Xen users are actually using to run KVM & Xen? > Particularly with consideration for 3D gaming and current generation > hardware, BTW. > > If there is need for further clarification, I'll answer any queries you > might have. There have been a couple success reports of using AMD/ATI graphics cards on Intel VT-d systems with KVM device assignment. Nvidia cards have not met with the same degree of success. In both our cases, the graphics device was assigned to a Windows guest as a secondary graphics head. For me, Windows took over the assigned device as the primary graphics, disabling the emulated graphics. For my slow HD 5450, 3dMark seems to get a similar score to what others see on bare metal. Graphics device assignment on KVM is getting better, but should be considered experimental at best. Thanks, Alex _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Thu Sep 20 22:00:00 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Thu, 20 Sep 2012 22:00:00 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TEoly-0003K2-W5; Thu, 20 Sep 2012 21:59:02 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TEogw-0003J0-JG for xen-users@lists.xen.org; Thu, 20 Sep 2012 21:53:50 +0000 Received: from [85.158.139.211:41206] by server-10.bemta-5.messagelabs.com id 28/D1-10969-D609B505; Thu, 20 Sep 2012 21:53:49 +0000 X-Env-Sender: alex.williamson@redhat.com X-Msg-Ref: server-13.tower-206.messagelabs.com!1348178028!15389908!1 X-Originating-IP: [209.132.183.28] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogMjA5LjEzMi4xODMuMjggPT4gNTcwODk=\n X-StarScan-Received: X-StarScan-Version: 6.6.1.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 5012 invoked from network); 20 Sep 2012 21:53:49 -0000 Received: from mx1.redhat.com (HELO mx1.redhat.com) (209.132.183.28) by server-13.tower-206.messagelabs.com with SMTP; 20 Sep 2012 21:53:49 -0000 Received: from int-mx01.intmail.prod.int.phx2.redhat.com (int-mx01.intmail.prod.int.phx2.redhat.com [10.5.11.11]) by mx1.redhat.com (8.14.4/8.14.4) with ESMTP id q8KLrk51009272 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Thu, 20 Sep 2012 17:53:46 -0400 Received: from [10.3.113.111] (ovpn-113-111.phx2.redhat.com [10.3.113.111]) by int-mx01.intmail.prod.int.phx2.redhat.com (8.13.8/8.13.8) with ESMTP id q8KLrjL9026156; Thu, 20 Sep 2012 17:53:46 -0400 Message-ID: <1348178025.2320.23.camel@ul30vt.home> From: Alex Williamson To: ShadesOfGrey Date: Thu, 20 Sep 2012 15:53:45 -0600 In-Reply-To: <505B86AE.9040507@earthlink.net> References: <505B86AE.9040507@earthlink.net> Mime-Version: 1.0 X-Scanned-By: MIMEDefang 2.67 on 10.5.11.11 X-Mailman-Approved-At: Thu, 20 Sep 2012 21:59:02 +0000 Cc: xen-users@lists.xen.org, kvm@vger.kernel.org Subject: Re: [Xen-users] Recommendations for Virtulization Hardware X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org On Thu, 2012-09-20 at 17:12 -0400, ShadesOfGrey wrote: > I'm looking to build a new personal computer. I want it to function as > a Linux desktop, provide network services for my home, and lastly, > occasional Windows gaming. From what I've gathered, virtualization > using a Type 1 Hypervisor supporting PCI/VGA pass-through like KVM or > Xen would be an attractive solution for my needs. For reference, > reading these threads on Ars Technica may be helpful to understand where > I'm coming from, > http://arstechnica.com/civis/viewtopic.php?f=6&t=1175674 and > http://arstechnica.com/civis/viewtopic.php?f=11&t=1181867. But > basically, I use Linux as my primary OS and would rather avoid dual > booting or building two boxes just to play Windows games when I want to > play Windows games. I'm also intrigued by the concept of virtualization > and would like to experiment with it as a solution for my case. > > My problem is isolating which hardware to choose, specifically which > combination of CPU, motherboard and video card. Previously I had been > relying on web searches to glean information from gaming and enthusiast > web sites and tech specs from motherboard manufacturers. After what I > learned during my participation in the referenced threads at Ars > Technica, I find myself back at square one. Instead of trying to guess > what hardware support KVM & Xen, and vice versa. I'd like to know what > hardware KVM & Xen users are actually using to run KVM & Xen? > Particularly with consideration for 3D gaming and current generation > hardware, BTW. > > If there is need for further clarification, I'll answer any queries you > might have. There have been a couple success reports of using AMD/ATI graphics cards on Intel VT-d systems with KVM device assignment. Nvidia cards have not met with the same degree of success. In both our cases, the graphics device was assigned to a Windows guest as a secondary graphics head. For me, Windows took over the assigned device as the primary graphics, disabling the emulated graphics. For my slow HD 5450, 3dMark seems to get a similar score to what others see on bare metal. Graphics device assignment on KVM is getting better, but should be considered experimental at best. Thanks, Alex _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Thu Sep 20 22:10:41 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Thu, 20 Sep 2012 22:10:41 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TEowO-0003oI-Og; Thu, 20 Sep 2012 22:09:48 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TEowN-0003o9-4L for xen-users@lists.xen.org; Thu, 20 Sep 2012 22:09:47 +0000 Received: from [85.158.139.211:44524] by server-10.bemta-5.messagelabs.com id 52/8B-10969-A249B505; Thu, 20 Sep 2012 22:09:46 +0000 X-Env-Sender: matthiasblankenhaus@yahoo.com X-Msg-Ref: server-7.tower-206.messagelabs.com!1348178985!18919411!1 X-Originating-IP: [98.138.91.135] X-SpamReason: No, hits=0.0 required=7.0 tests=HTML_MESSAGE, ML_RADAR_SPEW_LINKS_12,ML_RADAR_SPEW_LINKS_14,ML_RADAR_SPEW_LINKS_6, spamassassin: X-StarScan-Received: X-StarScan-Version: 6.6.1.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 11757 invoked from network); 20 Sep 2012 22:09:45 -0000 Received: from nm5-vm3.bullet.mail.ne1.yahoo.com (HELO nm5-vm3.bullet.mail.ne1.yahoo.com) (98.138.91.135) by server-7.tower-206.messagelabs.com with SMTP; 20 Sep 2012 22:09:45 -0000 Received: from [98.138.90.53] by nm5.bullet.mail.ne1.yahoo.com with NNFMP; 20 Sep 2012 22:09:44 -0000 Received: from [98.138.87.8] by tm6.bullet.mail.ne1.yahoo.com with NNFMP; 20 Sep 2012 22:09:44 -0000 Received: from [127.0.0.1] by omp1008.mail.ne1.yahoo.com with NNFMP; 20 Sep 2012 22:09:44 -0000 X-Yahoo-Newman-Property: ymail-3 X-Yahoo-Newman-Id: 633475.62322.bm@omp1008.mail.ne1.yahoo.com Received: (qmail 32361 invoked by uid 60001); 20 Sep 2012 22:09:44 -0000 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.com; s=s1024; t=1348178984; bh=xJp5gKcc2YbLi7W5KboZUrTf9QO2KXM7sjxeb04ipGk=; h=X-YMail-OSG:Received:X-Mailer:References:Message-ID:Date:From:Reply-To:Subject:To:In-Reply-To:MIME-Version:Content-Type; b=CeL3eDsMgv8+ybQMVRM55hjRvFkYJb8MQnCEJxWwwDSGU1DZaUfzArkcnHMAAUkOUcObZ4m9FGgEBINqzLuAowYR1/XT8KJyOUu7MWh7pMl58K3TnV+PZNV+nuWjoDqkpuDh3f5hWE1Hhtl5rIl8n+vz93iuFAU37gwUfY+Fts4= DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com; h=X-YMail-OSG:Received:X-Mailer:References:Message-ID:Date:From:Reply-To:Subject:To:In-Reply-To:MIME-Version:Content-Type; b=kO83GT89ost8EyesXdfrUHJpSzsqM9lhsRIZUpc8vy/dncp0VypA6l3SOp/EYapw4jZrAQZQWW/FyToEaA+419CT1SJfQS9K9dve30EYUMK3GDfR/ahbeut/lfEfnhp7vasY2Bi5TAGgkkoW49xyoutCjYUwrAsCnoPFR7vUfUE=; X-YMail-OSG: OiGJKAgVM1lvmMuNa4OtYr2zyfjXwOsLJN792KUIIaPSdBW wvnKs31A09j_o0_kKOS4hbw_mnhcFZlrTMLOmIPSbP7NWgRxfU58NVeZamaL awqRm7qJT7lcV.qqQuoMtnNeWeiECl5RE_b1OfN2PrEj2VgYI408WUEZmNmQ l0_Oq35AGmMWVBXmlmzWjtkoVlVtcchr03pTTYneQHXcXcFiyJvydKTVR3LQ Gwyb51iHkV4Tsv.3_dpELmsNzwO2tmnusK4yULEPrigd5Bk1w9BSNyKu3fCc clIyUN0IC6_jxeWQNmvO9uiqgIzZSEnW.hFtmOrhyrUCCF.MAfEeq5MkmxDU N3u0lQG_4NdE24RTXmRKzFQ2iNtE3XIZVFoH1YNLAosBl2WlABGd5CuLaUZY h9haRJM.mYijWa2w1zrYMFg8LwdWBXTfzq4iwJDhN04ay06Vpajf1EYQNtB3 wNx1xLD.bHHFDHnzPRDslcyPA2smnZpQlTMJ94Cu0Yn57i_HlrsThrLanGOC xC78M5wyOfYOc Received: from [143.127.128.10] by web39403.mail.mud.yahoo.com via HTTP; Thu, 20 Sep 2012 15:09:43 PDT X-Mailer: YahooMailWebService/0.8.121.416 References: <1348174904.65439.YahooMailNeo@web39403.mail.mud.yahoo.com> Message-ID: <1348178983.32300.YahooMailNeo@web39403.mail.mud.yahoo.com> Date: Thu, 20 Sep 2012 15:09:43 -0700 (PDT) From: Matthias Blankenhaus To: "xen-users@lists.xen.org" In-Reply-To: <1348174904.65439.YahooMailNeo@web39403.mail.mud.yahoo.com> MIME-Version: 1.0 Subject: Re: [Xen-users] /proc/xen/capabilities file not present in DomU X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list Reply-To: Matthias Blankenhaus List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============2376527443197686555==" Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org --===============2376527443197686555== Content-Type: multipart/alternative; boundary="908107500-1813756614-1348178983=:32300" --908107500-1813756614-1348178983=:32300 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: quoted-printable =0A=0A=0A=0A=0A>________________________________=0A> From: Nitin Gupta =0A>To: xen-users@lists.xen.org =0A>Sent: Monday, Septe= mber 17, 2012 4:19 AM=0A>Subject: [Xen-users] /proc/xen/capabilities file n= ot present in DomU=0A> =0A>=0A>Is it possible that '/proc/xen/capabilities'= file is not present in DomU ?=0A>=0A>=0AI guess you did not mount the xenf= s filesystem.=A0 Try this:=0A=0A# mount -t xenfs xenfs /proc/xen/=0A=0ABTW,= the capabilities file under /proc/xen on a domu should be empty.=0A=0A=0A= =0A>I have installed debian as domU, but it does not show above-mentioned f= ile. Is something wrong with my installation? How can I verify my setup?=0A= >=0A>I don't think that mounting xenfs in a domu is necessary.=A0 My domu's= work just fine without it.=0A=0A=0A=0A>-- =0A>Thanks,=0A>Nitin Gupta=0A>= =0A>=0A>_______________________________________________=0A>Xen-users mailin= g list=0A>Xen-users@lists.xen.org=0A>http://lists.xen.org/xen-users=0A>=0A>= =0A=0A=0A> --908107500-1813756614-1348178983=:32300 Content-Type: text/html; charset=iso-8859-1 Content-Transfer-Encoding: quoted-printable

=
From: Nitin Gupta <nitin.kobain@gmail.com>
= To: xen-users@lists.xen.or= g
Sent:=0A Monday, Sep= tember 17, 2012 4:19 AM
Subject: [Xen-users] /proc/xen/capabilities file not present in DomU
<= /font>

=0A
Is it possible that '/proc/x= en/capabilities' file is not present in DomU ?

I guess you did not mount the xenfs filesystem.  Try this:
# mount -t xenfs xenfs /proc/xen/

BTW, the capabilities file under= /proc/xen on a domu should be empty.


I hav= e installed debian as domU, but it does not show above-mentioned file. Is s= omething wrong with my installation? How can I verify my setup?
=0A=0A
I don't think that mounting xenfs in a dom= u is necessary.  My domu's work just fine without it.

<= /div>

--
Thanks,
Nitin Gupta

=0A

______________= _________________________________
Xen-users mailing list
Xen-users@lists.xen.org
http://l= ists.xen.org/xen-users



--908107500-1813756614-1348178983=:32300-- --===============2376527443197686555== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users --===============2376527443197686555==-- From xen-users-bounces@lists.xen.org Thu Sep 20 22:10:41 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Thu, 20 Sep 2012 22:10:41 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TEowO-0003oI-Og; Thu, 20 Sep 2012 22:09:48 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TEowN-0003o9-4L for xen-users@lists.xen.org; Thu, 20 Sep 2012 22:09:47 +0000 Received: from [85.158.139.211:44524] by server-10.bemta-5.messagelabs.com id 52/8B-10969-A249B505; Thu, 20 Sep 2012 22:09:46 +0000 X-Env-Sender: matthiasblankenhaus@yahoo.com X-Msg-Ref: server-7.tower-206.messagelabs.com!1348178985!18919411!1 X-Originating-IP: [98.138.91.135] X-SpamReason: No, hits=0.0 required=7.0 tests=HTML_MESSAGE, ML_RADAR_SPEW_LINKS_12,ML_RADAR_SPEW_LINKS_14,ML_RADAR_SPEW_LINKS_6, spamassassin: X-StarScan-Received: X-StarScan-Version: 6.6.1.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 11757 invoked from network); 20 Sep 2012 22:09:45 -0000 Received: from nm5-vm3.bullet.mail.ne1.yahoo.com (HELO nm5-vm3.bullet.mail.ne1.yahoo.com) (98.138.91.135) by server-7.tower-206.messagelabs.com with SMTP; 20 Sep 2012 22:09:45 -0000 Received: from [98.138.90.53] by nm5.bullet.mail.ne1.yahoo.com with NNFMP; 20 Sep 2012 22:09:44 -0000 Received: from [98.138.87.8] by tm6.bullet.mail.ne1.yahoo.com with NNFMP; 20 Sep 2012 22:09:44 -0000 Received: from [127.0.0.1] by omp1008.mail.ne1.yahoo.com with NNFMP; 20 Sep 2012 22:09:44 -0000 X-Yahoo-Newman-Property: ymail-3 X-Yahoo-Newman-Id: 633475.62322.bm@omp1008.mail.ne1.yahoo.com Received: (qmail 32361 invoked by uid 60001); 20 Sep 2012 22:09:44 -0000 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.com; s=s1024; t=1348178984; bh=xJp5gKcc2YbLi7W5KboZUrTf9QO2KXM7sjxeb04ipGk=; h=X-YMail-OSG:Received:X-Mailer:References:Message-ID:Date:From:Reply-To:Subject:To:In-Reply-To:MIME-Version:Content-Type; b=CeL3eDsMgv8+ybQMVRM55hjRvFkYJb8MQnCEJxWwwDSGU1DZaUfzArkcnHMAAUkOUcObZ4m9FGgEBINqzLuAowYR1/XT8KJyOUu7MWh7pMl58K3TnV+PZNV+nuWjoDqkpuDh3f5hWE1Hhtl5rIl8n+vz93iuFAU37gwUfY+Fts4= DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com; h=X-YMail-OSG:Received:X-Mailer:References:Message-ID:Date:From:Reply-To:Subject:To:In-Reply-To:MIME-Version:Content-Type; b=kO83GT89ost8EyesXdfrUHJpSzsqM9lhsRIZUpc8vy/dncp0VypA6l3SOp/EYapw4jZrAQZQWW/FyToEaA+419CT1SJfQS9K9dve30EYUMK3GDfR/ahbeut/lfEfnhp7vasY2Bi5TAGgkkoW49xyoutCjYUwrAsCnoPFR7vUfUE=; X-YMail-OSG: OiGJKAgVM1lvmMuNa4OtYr2zyfjXwOsLJN792KUIIaPSdBW wvnKs31A09j_o0_kKOS4hbw_mnhcFZlrTMLOmIPSbP7NWgRxfU58NVeZamaL awqRm7qJT7lcV.qqQuoMtnNeWeiECl5RE_b1OfN2PrEj2VgYI408WUEZmNmQ l0_Oq35AGmMWVBXmlmzWjtkoVlVtcchr03pTTYneQHXcXcFiyJvydKTVR3LQ Gwyb51iHkV4Tsv.3_dpELmsNzwO2tmnusK4yULEPrigd5Bk1w9BSNyKu3fCc clIyUN0IC6_jxeWQNmvO9uiqgIzZSEnW.hFtmOrhyrUCCF.MAfEeq5MkmxDU N3u0lQG_4NdE24RTXmRKzFQ2iNtE3XIZVFoH1YNLAosBl2WlABGd5CuLaUZY h9haRJM.mYijWa2w1zrYMFg8LwdWBXTfzq4iwJDhN04ay06Vpajf1EYQNtB3 wNx1xLD.bHHFDHnzPRDslcyPA2smnZpQlTMJ94Cu0Yn57i_HlrsThrLanGOC xC78M5wyOfYOc Received: from [143.127.128.10] by web39403.mail.mud.yahoo.com via HTTP; Thu, 20 Sep 2012 15:09:43 PDT X-Mailer: YahooMailWebService/0.8.121.416 References: <1348174904.65439.YahooMailNeo@web39403.mail.mud.yahoo.com> Message-ID: <1348178983.32300.YahooMailNeo@web39403.mail.mud.yahoo.com> Date: Thu, 20 Sep 2012 15:09:43 -0700 (PDT) From: Matthias Blankenhaus To: "xen-users@lists.xen.org" In-Reply-To: <1348174904.65439.YahooMailNeo@web39403.mail.mud.yahoo.com> MIME-Version: 1.0 Subject: Re: [Xen-users] /proc/xen/capabilities file not present in DomU X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list Reply-To: Matthias Blankenhaus List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============2376527443197686555==" Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org --===============2376527443197686555== Content-Type: multipart/alternative; boundary="908107500-1813756614-1348178983=:32300" --908107500-1813756614-1348178983=:32300 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: quoted-printable =0A=0A=0A=0A=0A>________________________________=0A> From: Nitin Gupta =0A>To: xen-users@lists.xen.org =0A>Sent: Monday, Septe= mber 17, 2012 4:19 AM=0A>Subject: [Xen-users] /proc/xen/capabilities file n= ot present in DomU=0A> =0A>=0A>Is it possible that '/proc/xen/capabilities'= file is not present in DomU ?=0A>=0A>=0AI guess you did not mount the xenf= s filesystem.=A0 Try this:=0A=0A# mount -t xenfs xenfs /proc/xen/=0A=0ABTW,= the capabilities file under /proc/xen on a domu should be empty.=0A=0A=0A= =0A>I have installed debian as domU, but it does not show above-mentioned f= ile. Is something wrong with my installation? How can I verify my setup?=0A= >=0A>I don't think that mounting xenfs in a domu is necessary.=A0 My domu's= work just fine without it.=0A=0A=0A=0A>-- =0A>Thanks,=0A>Nitin Gupta=0A>= =0A>=0A>_______________________________________________=0A>Xen-users mailin= g list=0A>Xen-users@lists.xen.org=0A>http://lists.xen.org/xen-users=0A>=0A>= =0A=0A=0A> --908107500-1813756614-1348178983=:32300 Content-Type: text/html; charset=iso-8859-1 Content-Transfer-Encoding: quoted-printable

=
From: Nitin Gupta <nitin.kobain@gmail.com>
= To: xen-users@lists.xen.or= g
Sent:=0A Monday, Sep= tember 17, 2012 4:19 AM
Subject: [Xen-users] /proc/xen/capabilities file not present in DomU
<= /font>

=0A
Is it possible that '/proc/x= en/capabilities' file is not present in DomU ?

I guess you did not mount the xenfs filesystem.  Try this:
# mount -t xenfs xenfs /proc/xen/

BTW, the capabilities file under= /proc/xen on a domu should be empty.


I hav= e installed debian as domU, but it does not show above-mentioned file. Is s= omething wrong with my installation? How can I verify my setup?
=0A=0A
I don't think that mounting xenfs in a dom= u is necessary.  My domu's work just fine without it.

<= /div>

--
Thanks,
Nitin Gupta

=0A

______________= _________________________________
Xen-users mailing list
Xen-users@lists.xen.org
http://l= ists.xen.org/xen-users



--908107500-1813756614-1348178983=:32300-- --===============2376527443197686555== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users --===============2376527443197686555==-- From xen-users-bounces@lists.xen.org Thu Sep 20 23:53:53 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Thu, 20 Sep 2012 23:53:53 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TEqXx-0004hP-U0; Thu, 20 Sep 2012 23:52:41 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TEqXw-0004hK-7R for xen-users@lists.xen.org; Thu, 20 Sep 2012 23:52:40 +0000 Received: from [85.158.139.83:46429] by server-14.bemta-5.messagelabs.com id 3B/25-13084-74CAB505; Thu, 20 Sep 2012 23:52:39 +0000 X-Env-Sender: myrdhn@gmail.com X-Msg-Ref: server-10.tower-182.messagelabs.com!1348185157!31741092!1 X-Originating-IP: [209.85.216.173] X-SpamReason: No, hits=0.3 required=7.0 tests=ML_RADAR_SPEW_LINKS_14, RCVD_BY_IP,spamassassin: X-StarScan-Received: X-StarScan-Version: 6.6.1.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 5183 invoked from network); 20 Sep 2012 23:52:38 -0000 Received: from mail-qc0-f173.google.com (HELO mail-qc0-f173.google.com) (209.85.216.173) by server-10.tower-182.messagelabs.com with RC4-SHA encrypted SMTP; 20 Sep 2012 23:52:38 -0000 Received: by qcab12 with SMTP id b12so2773630qca.32 for ; Thu, 20 Sep 2012 16:52:37 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=from:to:references:in-reply-to:subject:date:message-id:mime-version :content-type:content-transfer-encoding:x-mailer:thread-index :content-language; bh=QVkoPRgn4xfQd6ut5PLIQbSRxxacWWRvzf7R5n/omhc=; b=GhW/h4f9nFg/Td1jRNDNO4tfHkG+89VxY5JFOvpVuGgTQzIhSuPyzMkPKMvrbczMs3 +a3xXAnjVn5uWbW+Nv3WWga6uUp6LCLKg1qlfpaSQYLCYavD/TaH2jh3e83NnRrb0Ry9 wJ6knydZXjpVZ7u4L6sTQt/zu6J42tfniNXL+qli9XUhFr6OrF0tX7HuJH33Y4e6SlRy sznTH+VzB3PdUtzmtQ6wM/rkMDtEpDkfI7OlVP0eEV+yC3cZs0t4E1KI13g1LW0wdiMv dk+kGtpxphuGCzsynCBleWX95gfutDTmroUoMOKXgxvT/ZIT/7brsq7jR210e+iqapa3 vodw== Received: by 10.229.122.220 with SMTP id m28mr2309899qcr.49.1348185157453; Thu, 20 Sep 2012 16:52:37 -0700 (PDT) Received: from Belldandy (c-76-119-253-48.hsd1.ma.comcast.net. [76.119.253.48]) by mx.google.com with ESMTPS id dp3sm10227661qab.21.2012.09.20.16.52.35 (version=TLSv1/SSLv3 cipher=OTHER); Thu, 20 Sep 2012 16:52:36 -0700 (PDT) From: "Marc Tousignant" To: "'Teo En Ming \(Zhang Enming\)'" , References: <008f01cd968e$15260cb0$3f722610$@gmail.com> <505B454D.2080003@gmail.com> In-Reply-To: <505B454D.2080003@gmail.com> Date: Thu, 20 Sep 2012 19:52:39 -0400 Message-ID: <00c601cd978b$05c27210$11475630$@gmail.com> MIME-Version: 1.0 X-Mailer: Microsoft Outlook 14.0 Thread-Index: AQKcb9jloExcuPRXz0Adw3E5ucRw8wNltL4hldrq4mA= Content-Language: en-us Subject: Re: [Xen-users] Solved - PCIe/VGA passthrough X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org Dear MarcT, May I know the exact steps you have taken to get all the BARs? I don't have any BAR at all. Solved it. Turns out you can't find the memory without first setting up the kernel commands to hide the device. dmesg | grep 01:00.0 | grep "pci.*mem" pci 0000:01:00.0: BAR 0: assigned [mem 0xcc000000-0xccffffff] pci 0000:01:00.0: BAR 1: assigned [mem 0xb0000000-0xbfffffff 64bit pref] pci 0000:01:00.0: BAR 3: assigned [mem 0xca000000-0xcbffffff 64bit] pci 0000:01:00.0: BAR 6: assigned [mem 0xcd000000-0xcd01ffff pref] -- Yours sincerely, Mr. Teo En Ming (Zhang Enming) Singapore Teo En Ming, I'm not sure how exactly, they just showed up. I'm using a kernel I built from source on the Funtoo distro of linux. I just got video pass through to work as of this morning. I'm using 4.2 release, with patches applied. My video card is an EVGA nVidia 8800 GTX I'm having trouble now because I can't pass through my USB hubs and for some reason pvusb is missing so I cant pass through the device itself. _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Thu Sep 20 23:53:53 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Thu, 20 Sep 2012 23:53:53 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TEqXx-0004hP-U0; Thu, 20 Sep 2012 23:52:41 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TEqXw-0004hK-7R for xen-users@lists.xen.org; Thu, 20 Sep 2012 23:52:40 +0000 Received: from [85.158.139.83:46429] by server-14.bemta-5.messagelabs.com id 3B/25-13084-74CAB505; Thu, 20 Sep 2012 23:52:39 +0000 X-Env-Sender: myrdhn@gmail.com X-Msg-Ref: server-10.tower-182.messagelabs.com!1348185157!31741092!1 X-Originating-IP: [209.85.216.173] X-SpamReason: No, hits=0.3 required=7.0 tests=ML_RADAR_SPEW_LINKS_14, RCVD_BY_IP,spamassassin: X-StarScan-Received: X-StarScan-Version: 6.6.1.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 5183 invoked from network); 20 Sep 2012 23:52:38 -0000 Received: from mail-qc0-f173.google.com (HELO mail-qc0-f173.google.com) (209.85.216.173) by server-10.tower-182.messagelabs.com with RC4-SHA encrypted SMTP; 20 Sep 2012 23:52:38 -0000 Received: by qcab12 with SMTP id b12so2773630qca.32 for ; Thu, 20 Sep 2012 16:52:37 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=from:to:references:in-reply-to:subject:date:message-id:mime-version :content-type:content-transfer-encoding:x-mailer:thread-index :content-language; bh=QVkoPRgn4xfQd6ut5PLIQbSRxxacWWRvzf7R5n/omhc=; b=GhW/h4f9nFg/Td1jRNDNO4tfHkG+89VxY5JFOvpVuGgTQzIhSuPyzMkPKMvrbczMs3 +a3xXAnjVn5uWbW+Nv3WWga6uUp6LCLKg1qlfpaSQYLCYavD/TaH2jh3e83NnRrb0Ry9 wJ6knydZXjpVZ7u4L6sTQt/zu6J42tfniNXL+qli9XUhFr6OrF0tX7HuJH33Y4e6SlRy sznTH+VzB3PdUtzmtQ6wM/rkMDtEpDkfI7OlVP0eEV+yC3cZs0t4E1KI13g1LW0wdiMv dk+kGtpxphuGCzsynCBleWX95gfutDTmroUoMOKXgxvT/ZIT/7brsq7jR210e+iqapa3 vodw== Received: by 10.229.122.220 with SMTP id m28mr2309899qcr.49.1348185157453; Thu, 20 Sep 2012 16:52:37 -0700 (PDT) Received: from Belldandy (c-76-119-253-48.hsd1.ma.comcast.net. [76.119.253.48]) by mx.google.com with ESMTPS id dp3sm10227661qab.21.2012.09.20.16.52.35 (version=TLSv1/SSLv3 cipher=OTHER); Thu, 20 Sep 2012 16:52:36 -0700 (PDT) From: "Marc Tousignant" To: "'Teo En Ming \(Zhang Enming\)'" , References: <008f01cd968e$15260cb0$3f722610$@gmail.com> <505B454D.2080003@gmail.com> In-Reply-To: <505B454D.2080003@gmail.com> Date: Thu, 20 Sep 2012 19:52:39 -0400 Message-ID: <00c601cd978b$05c27210$11475630$@gmail.com> MIME-Version: 1.0 X-Mailer: Microsoft Outlook 14.0 Thread-Index: AQKcb9jloExcuPRXz0Adw3E5ucRw8wNltL4hldrq4mA= Content-Language: en-us Subject: Re: [Xen-users] Solved - PCIe/VGA passthrough X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org Dear MarcT, May I know the exact steps you have taken to get all the BARs? I don't have any BAR at all. Solved it. Turns out you can't find the memory without first setting up the kernel commands to hide the device. dmesg | grep 01:00.0 | grep "pci.*mem" pci 0000:01:00.0: BAR 0: assigned [mem 0xcc000000-0xccffffff] pci 0000:01:00.0: BAR 1: assigned [mem 0xb0000000-0xbfffffff 64bit pref] pci 0000:01:00.0: BAR 3: assigned [mem 0xca000000-0xcbffffff 64bit] pci 0000:01:00.0: BAR 6: assigned [mem 0xcd000000-0xcd01ffff pref] -- Yours sincerely, Mr. Teo En Ming (Zhang Enming) Singapore Teo En Ming, I'm not sure how exactly, they just showed up. I'm using a kernel I built from source on the Funtoo distro of linux. I just got video pass through to work as of this morning. I'm using 4.2 release, with patches applied. My video card is an EVGA nVidia 8800 GTX I'm having trouble now because I can't pass through my USB hubs and for some reason pvusb is missing so I cant pass through the device itself. _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Fri Sep 21 04:57:04 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Fri, 21 Sep 2012 04:57:04 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TEvHF-0003CI-HK; Fri, 21 Sep 2012 04:55:45 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TEvHD-0003CD-9d for xen-users@lists.xen.org; Fri, 21 Sep 2012 04:55:43 +0000 Received: from [85.158.143.35:64869] by server-3.bemta-4.messagelabs.com id 88/A3-10986-E43FB505; Fri, 21 Sep 2012 04:55:42 +0000 X-Env-Sender: myrdhn@gmail.com X-Msg-Ref: server-9.tower-21.messagelabs.com!1348203340!8196068!1 X-Originating-IP: [209.85.216.173] X-SpamReason: No, hits=0.6 required=7.0 tests=HTML_60_70,HTML_MESSAGE, ML_RADAR_SPEW_LINKS_14,RCVD_BY_IP,spamassassin: X-StarScan-Received: X-StarScan-Version: 6.6.1.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 3514 invoked from network); 21 Sep 2012 04:55:41 -0000 Received: from mail-qc0-f173.google.com (HELO mail-qc0-f173.google.com) (209.85.216.173) by server-9.tower-21.messagelabs.com with RC4-SHA encrypted SMTP; 21 Sep 2012 04:55:41 -0000 Received: by qcab12 with SMTP id b12so2964437qca.32 for ; Thu, 20 Sep 2012 21:55:39 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=from:to:subject:date:message-id:mime-version:content-type:x-mailer :thread-index:content-language; bh=2odvh8s7w0FDOuQuQStnP9cCxjcyhsPSH4mVVKoSp6I=; b=lz1iQVCI0chxHj4bc+c54kENr67/qi46nx9Q1yQdNGPkkuNLGI7VTbuqgjrYO3ol/d UWNYI8lodB9qoYkCmREEnZkWDz2a7m7dQhQNUGxXr0iA9AgtVOsSFmehbhPRLhD/w5IG /uN63hKSOsUs8T8gGNlBAgeLj05fNxP9DYoTmioFZ1+P/04MMomjs4OgR2dwUhLNATdM 3PHjCI2xr6ScaUd6aThbbosmnfpwUfWTAuV7NUIlxPUjN8IbMZHO7TH7GhLmXIKCRw2t 6NYQh2u/dthgD/ZfrJq/cetYZvfgdUXLKnpPlTqzvOO/PTo/u12BoNjNRxHQKsHK09RU 7pAQ== Received: by 10.224.9.9 with SMTP id j9mr9851555qaj.32.1348203339644; Thu, 20 Sep 2012 21:55:39 -0700 (PDT) Received: from Belldandy (c-76-119-253-48.hsd1.ma.comcast.net. [76.119.253.48]) by mx.google.com with ESMTPS id y18sm11197173qaa.15.2012.09.20.21.55.38 (version=TLSv1/SSLv3 cipher=OTHER); Thu, 20 Sep 2012 21:55:39 -0700 (PDT) From: "Marc Tousignant" To: Date: Fri, 21 Sep 2012 00:55:42 -0400 Message-ID: <002401cd97b5$5b49f260$11ddd720$@gmail.com> MIME-Version: 1.0 X-Mailer: Microsoft Outlook 14.0 Thread-Index: Ac2Xs2cgJJod9eQ+RE6Vv5eyJlEFbQ== Content-Language: en-us Subject: [Xen-users] Need help with passing through USB hub or devices X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============7280093169164174519==" Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org This is a multipart message in MIME format. --===============7280093169164174519== Content-Type: multipart/alternative; boundary="----=_NextPart_000_0025_01CD9793.D43A9C50" Content-Language: en-us This is a multipart message in MIME format. ------=_NextPart_000_0025_01CD9793.D43A9C50 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit So, I'm getting further and further to completing my setup following the guides written about passthrough of PCIe video. I have the video display from the domU client going to the physical display, but I cannot get the keyboard to work, I haven't even connected a mouse yet. I attempted to pass through the USB hubs outright, but that failed as the keyboard just stopped working. It would not respond in the domU and I could nolonger get the caps lock to light up. Reconnecting or changing ports had no effect. Attempting to add the usb hub afterwards using xl pci-attach failed as well. But this time, it did not even attach the device. TheOldMan ~ # xl pci-assignable-list 0000:00:0b.0 TheOldMan ~ # xl pci-attach 1 0000:00:0b.0 libxl: error: libxl_pci.c:960:do_pci_add: xc_assign_device failed TheOldMan ~ # xl pci-assignable-list 0000:00:0b.0 TheOldMan ~ # xl pci-list 1 Vdev Device 05.0 0000:01:00.0 06.0 0000:00:0f.1 The reason I am trying to pass through the usb hub is 2 fold: First off, I would prefer not having to go into the console to add my keyboard/mouse each time I start. Second, I cannot seem to get into the console to save my life. I have vnc setup for console, however after connecting, I can't type anything. That's not to say that the keyboard is useless. Ctrl+alt+1 and ctrl+alt+2 switch between "serial0 console" and "parallel0 console" in the vnc window. In the hopes that all it was that the echo was off, I attempted to enter the usb_add line for my keyboard to no effect. Trying to access the console from a ssh connection in putty also fails. TheOldMan ~ # xl console Office xenconsole: Could not read tty from store: No such file or directory The standard fix I found searching for this error was "start xenconsoled". Well here is what I say about that. TheOldMan ~ # ps augx | grep xenconsoled root 6146 0.0 0.0 25168 1052 ? SLl 20:08 0:00 /usr/sbin/xenconsoled --pid-file=/var/run/xenconsoled.pid root 6888 0.0 0.0 8148 880 pts/0 S+ 20:53 0:00 grep --colour=auto xenconsoled Here is my config: name="Office" firmware_override = "/usr/lib/xen/boot/hvmloader" builder="hvm" vcpus=2 memory=2048 on_poweroff="destroy" on_reboot="restart" on_crash="destroy" disk = [ 'tap:aio://images/xen_images/Office.img,hda,w', 'tap:aio://images/iso_images/en_windows_7_enterprise_with_sp1_x64_dvd_u_6776 51.iso,hdc:cdrom,r' ] #disk = [ 'tap:aio://images/xen_images/Office.img,hda,w' ] vif = [ 'mac=00:16:3E:33:5E:F9, bridge=xenbr0' ] #vif = [ 'bridge=xenbr0,type=ioemu,model=e1000' ] boot="dc" acpi=1 xen_platform_pci=1 viridian=1 stdvga=1 vnc=1 vnclisten="192.168.1.102" vncconsole=1 vncconsole=1 vncdisplay=0 vncunused=1 vncpasswd="" sdl=0 usb=1 usbdevice="tablet" gfx_passthru=1 audio=1 pci = [ '01:00.0','00:0f.1' ] I can get more info if needed. I really want to get this project done. MarcT ------=_NextPart_000_0025_01CD9793.D43A9C50 Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable

So, = I’m getting further and further to completing my setup following = the guides written about passthrough of PCIe video.

I have the video display from the domU client going to = the physical display, but I cannot get the keyboard to work, I = haven’t even connected a mouse yet.

 

I attempted = to pass through the USB hubs outright, but that failed as the keyboard = just stopped working. It would not respond in the domU and I could = nolonger get the caps lock to light up. Reconnecting or changing ports = had no effect.

Attempting to add the = usb hub afterwards using xl pci-attach failed as well. But this time, it = did not even attach the device.

TheOldMan ~ # xl = pci-assignable-list

0000:00:0b.0

TheOldMan ~ # xl pci-attach = 1 0000:00:0b.0

libxl: error: libxl_pci.c:960:do_pci_add: = xc_assign_device failed

TheOldMan ~ # xl = pci-assignable-list

0000:00:0b.0

TheOldMan ~ # xl pci-list = 1

Vdev = Device

05.0 0000:01:00.0

06.0 = 0000:00:0f.1

 

The reason I am trying to pass through the usb hub is = 2 fold:

         &= nbsp;      First off, I would prefer not having = to go into the console to add my keyboard/mouse each time I = start.

         &= nbsp;      Second, I cannot seem to get into = the console to save my life.

 

I have vnc = setup for console, however after connecting, I can’t type = anything. That’s not to say that the keyboard is useless. = Ctrl+alt+1 and ctrl+alt+2 switch between “serial0 console” = and “parallel0 console” in the vnc window. In the hopes that = all it was that the echo was off, I attempted to enter the usb_add line = for my keyboard to no effect.

 

Trying to = access the console from a ssh connection in putty also = fails.

TheOldMan ~ # xl console = Office

xenconsole: Could not read tty = from store: No such file or directory

The standard fix I found searching for this error was = “start xenconsoled”. Well here is what I say about = that.

TheOldMan ~ # ps augx | grep = xenconsoled

root      6146  = 0.0  0.0  25168  1052 = ?        SLl  20:08   = 0:00 /usr/sbin/xenconsoled = --pid-file=3D/var/run/xenconsoled.pid

root      6888  = 0.0  0.0   8148   880 pts/0    = S+   20:53   0:00 grep --colour=3Dauto = xenconsoled

 

Here is my config:

 

name=3D"Office"

 

firmware_override =3D = "/usr/lib/xen/boot/hvmloader"

builder=3D"hvm"

 

vcpus=3D2

 

memory=3D2048

 

on_poweroff=3D"destroy"

on_reboot=3D"restart"

=

on_crash=3D"destroy"

<= p class=3DMsoNormal style=3D'margin-left:.5in'> 

disk =3D [ = 'tap:aio://images/xen_images/Office.img,hda,w', = 'tap:aio://images/iso_images/en_windows_7_enterprise_with_sp1_x64_dvd_u_6= 77651.iso,hdc:cdrom,r' ]

#disk =3D [ = 'tap:aio://images/xen_images/Office.img,hda,w' ]

 

vif =3D [ = 'mac=3D00:16:3E:33:5E:F9, bridge=3Dxenbr0' ]

#vif =3D [ = 'bridge=3Dxenbr0,type=3Dioemu,model=3De1000' ]

 

boot=3D"dc"

 

acpi=3D1

 

xen_platform_pci=3D1

 

viridian=3D1

 

stdvga=3D1

 

vnc=3D1

vnclisten=3D"192.168.1.102"

vncconsole=3D1

vncconsole=3D1

vncdisplay=3D0

vncunused=3D1

vncpasswd=3D""

sdl=3D0

 

usb=3D1

usbdevice=3D"tablet"

<= p class=3DMsoNormal style=3D'margin-left:.5in'> 

gfx_passthru=3D1

audio=3D1

 

pci =3D [ = '01:00.0','00:0f.1' ]

 

I can get = more info if needed. I really want to get this project = done.

 

MarcT

------=_NextPart_000_0025_01CD9793.D43A9C50-- --===============7280093169164174519== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users --===============7280093169164174519==-- From xen-users-bounces@lists.xen.org Fri Sep 21 04:57:04 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Fri, 21 Sep 2012 04:57:04 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TEvHF-0003CI-HK; Fri, 21 Sep 2012 04:55:45 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TEvHD-0003CD-9d for xen-users@lists.xen.org; Fri, 21 Sep 2012 04:55:43 +0000 Received: from [85.158.143.35:64869] by server-3.bemta-4.messagelabs.com id 88/A3-10986-E43FB505; Fri, 21 Sep 2012 04:55:42 +0000 X-Env-Sender: myrdhn@gmail.com X-Msg-Ref: server-9.tower-21.messagelabs.com!1348203340!8196068!1 X-Originating-IP: [209.85.216.173] X-SpamReason: No, hits=0.6 required=7.0 tests=HTML_60_70,HTML_MESSAGE, ML_RADAR_SPEW_LINKS_14,RCVD_BY_IP,spamassassin: X-StarScan-Received: X-StarScan-Version: 6.6.1.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 3514 invoked from network); 21 Sep 2012 04:55:41 -0000 Received: from mail-qc0-f173.google.com (HELO mail-qc0-f173.google.com) (209.85.216.173) by server-9.tower-21.messagelabs.com with RC4-SHA encrypted SMTP; 21 Sep 2012 04:55:41 -0000 Received: by qcab12 with SMTP id b12so2964437qca.32 for ; Thu, 20 Sep 2012 21:55:39 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=from:to:subject:date:message-id:mime-version:content-type:x-mailer :thread-index:content-language; bh=2odvh8s7w0FDOuQuQStnP9cCxjcyhsPSH4mVVKoSp6I=; b=lz1iQVCI0chxHj4bc+c54kENr67/qi46nx9Q1yQdNGPkkuNLGI7VTbuqgjrYO3ol/d UWNYI8lodB9qoYkCmREEnZkWDz2a7m7dQhQNUGxXr0iA9AgtVOsSFmehbhPRLhD/w5IG /uN63hKSOsUs8T8gGNlBAgeLj05fNxP9DYoTmioFZ1+P/04MMomjs4OgR2dwUhLNATdM 3PHjCI2xr6ScaUd6aThbbosmnfpwUfWTAuV7NUIlxPUjN8IbMZHO7TH7GhLmXIKCRw2t 6NYQh2u/dthgD/ZfrJq/cetYZvfgdUXLKnpPlTqzvOO/PTo/u12BoNjNRxHQKsHK09RU 7pAQ== Received: by 10.224.9.9 with SMTP id j9mr9851555qaj.32.1348203339644; Thu, 20 Sep 2012 21:55:39 -0700 (PDT) Received: from Belldandy (c-76-119-253-48.hsd1.ma.comcast.net. [76.119.253.48]) by mx.google.com with ESMTPS id y18sm11197173qaa.15.2012.09.20.21.55.38 (version=TLSv1/SSLv3 cipher=OTHER); Thu, 20 Sep 2012 21:55:39 -0700 (PDT) From: "Marc Tousignant" To: Date: Fri, 21 Sep 2012 00:55:42 -0400 Message-ID: <002401cd97b5$5b49f260$11ddd720$@gmail.com> MIME-Version: 1.0 X-Mailer: Microsoft Outlook 14.0 Thread-Index: Ac2Xs2cgJJod9eQ+RE6Vv5eyJlEFbQ== Content-Language: en-us Subject: [Xen-users] Need help with passing through USB hub or devices X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============7280093169164174519==" Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org This is a multipart message in MIME format. --===============7280093169164174519== Content-Type: multipart/alternative; boundary="----=_NextPart_000_0025_01CD9793.D43A9C50" Content-Language: en-us This is a multipart message in MIME format. ------=_NextPart_000_0025_01CD9793.D43A9C50 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit So, I'm getting further and further to completing my setup following the guides written about passthrough of PCIe video. I have the video display from the domU client going to the physical display, but I cannot get the keyboard to work, I haven't even connected a mouse yet. I attempted to pass through the USB hubs outright, but that failed as the keyboard just stopped working. It would not respond in the domU and I could nolonger get the caps lock to light up. Reconnecting or changing ports had no effect. Attempting to add the usb hub afterwards using xl pci-attach failed as well. But this time, it did not even attach the device. TheOldMan ~ # xl pci-assignable-list 0000:00:0b.0 TheOldMan ~ # xl pci-attach 1 0000:00:0b.0 libxl: error: libxl_pci.c:960:do_pci_add: xc_assign_device failed TheOldMan ~ # xl pci-assignable-list 0000:00:0b.0 TheOldMan ~ # xl pci-list 1 Vdev Device 05.0 0000:01:00.0 06.0 0000:00:0f.1 The reason I am trying to pass through the usb hub is 2 fold: First off, I would prefer not having to go into the console to add my keyboard/mouse each time I start. Second, I cannot seem to get into the console to save my life. I have vnc setup for console, however after connecting, I can't type anything. That's not to say that the keyboard is useless. Ctrl+alt+1 and ctrl+alt+2 switch between "serial0 console" and "parallel0 console" in the vnc window. In the hopes that all it was that the echo was off, I attempted to enter the usb_add line for my keyboard to no effect. Trying to access the console from a ssh connection in putty also fails. TheOldMan ~ # xl console Office xenconsole: Could not read tty from store: No such file or directory The standard fix I found searching for this error was "start xenconsoled". Well here is what I say about that. TheOldMan ~ # ps augx | grep xenconsoled root 6146 0.0 0.0 25168 1052 ? SLl 20:08 0:00 /usr/sbin/xenconsoled --pid-file=/var/run/xenconsoled.pid root 6888 0.0 0.0 8148 880 pts/0 S+ 20:53 0:00 grep --colour=auto xenconsoled Here is my config: name="Office" firmware_override = "/usr/lib/xen/boot/hvmloader" builder="hvm" vcpus=2 memory=2048 on_poweroff="destroy" on_reboot="restart" on_crash="destroy" disk = [ 'tap:aio://images/xen_images/Office.img,hda,w', 'tap:aio://images/iso_images/en_windows_7_enterprise_with_sp1_x64_dvd_u_6776 51.iso,hdc:cdrom,r' ] #disk = [ 'tap:aio://images/xen_images/Office.img,hda,w' ] vif = [ 'mac=00:16:3E:33:5E:F9, bridge=xenbr0' ] #vif = [ 'bridge=xenbr0,type=ioemu,model=e1000' ] boot="dc" acpi=1 xen_platform_pci=1 viridian=1 stdvga=1 vnc=1 vnclisten="192.168.1.102" vncconsole=1 vncconsole=1 vncdisplay=0 vncunused=1 vncpasswd="" sdl=0 usb=1 usbdevice="tablet" gfx_passthru=1 audio=1 pci = [ '01:00.0','00:0f.1' ] I can get more info if needed. I really want to get this project done. MarcT ------=_NextPart_000_0025_01CD9793.D43A9C50 Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable

So, = I’m getting further and further to completing my setup following = the guides written about passthrough of PCIe video.

I have the video display from the domU client going to = the physical display, but I cannot get the keyboard to work, I = haven’t even connected a mouse yet.

 

I attempted = to pass through the USB hubs outright, but that failed as the keyboard = just stopped working. It would not respond in the domU and I could = nolonger get the caps lock to light up. Reconnecting or changing ports = had no effect.

Attempting to add the = usb hub afterwards using xl pci-attach failed as well. But this time, it = did not even attach the device.

TheOldMan ~ # xl = pci-assignable-list

0000:00:0b.0

TheOldMan ~ # xl pci-attach = 1 0000:00:0b.0

libxl: error: libxl_pci.c:960:do_pci_add: = xc_assign_device failed

TheOldMan ~ # xl = pci-assignable-list

0000:00:0b.0

TheOldMan ~ # xl pci-list = 1

Vdev = Device

05.0 0000:01:00.0

06.0 = 0000:00:0f.1

 

The reason I am trying to pass through the usb hub is = 2 fold:

         &= nbsp;      First off, I would prefer not having = to go into the console to add my keyboard/mouse each time I = start.

         &= nbsp;      Second, I cannot seem to get into = the console to save my life.

 

I have vnc = setup for console, however after connecting, I can’t type = anything. That’s not to say that the keyboard is useless. = Ctrl+alt+1 and ctrl+alt+2 switch between “serial0 console” = and “parallel0 console” in the vnc window. In the hopes that = all it was that the echo was off, I attempted to enter the usb_add line = for my keyboard to no effect.

 

Trying to = access the console from a ssh connection in putty also = fails.

TheOldMan ~ # xl console = Office

xenconsole: Could not read tty = from store: No such file or directory

The standard fix I found searching for this error was = “start xenconsoled”. Well here is what I say about = that.

TheOldMan ~ # ps augx | grep = xenconsoled

root      6146  = 0.0  0.0  25168  1052 = ?        SLl  20:08   = 0:00 /usr/sbin/xenconsoled = --pid-file=3D/var/run/xenconsoled.pid

root      6888  = 0.0  0.0   8148   880 pts/0    = S+   20:53   0:00 grep --colour=3Dauto = xenconsoled

 

Here is my config:

 

name=3D"Office"

 

firmware_override =3D = "/usr/lib/xen/boot/hvmloader"

builder=3D"hvm"

 

vcpus=3D2

 

memory=3D2048

 

on_poweroff=3D"destroy"

on_reboot=3D"restart"

=

on_crash=3D"destroy"

<= p class=3DMsoNormal style=3D'margin-left:.5in'> 

disk =3D [ = 'tap:aio://images/xen_images/Office.img,hda,w', = 'tap:aio://images/iso_images/en_windows_7_enterprise_with_sp1_x64_dvd_u_6= 77651.iso,hdc:cdrom,r' ]

#disk =3D [ = 'tap:aio://images/xen_images/Office.img,hda,w' ]

 

vif =3D [ = 'mac=3D00:16:3E:33:5E:F9, bridge=3Dxenbr0' ]

#vif =3D [ = 'bridge=3Dxenbr0,type=3Dioemu,model=3De1000' ]

 

boot=3D"dc"

 

acpi=3D1

 

xen_platform_pci=3D1

 

viridian=3D1

 

stdvga=3D1

 

vnc=3D1

vnclisten=3D"192.168.1.102"

vncconsole=3D1

vncconsole=3D1

vncdisplay=3D0

vncunused=3D1

vncpasswd=3D""

sdl=3D0

 

usb=3D1

usbdevice=3D"tablet"

<= p class=3DMsoNormal style=3D'margin-left:.5in'> 

gfx_passthru=3D1

audio=3D1

 

pci =3D [ = '01:00.0','00:0f.1' ]

 

I can get = more info if needed. I really want to get this project = done.

 

MarcT

------=_NextPart_000_0025_01CD9793.D43A9C50-- --===============7280093169164174519== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users --===============7280093169164174519==-- From xen-users-bounces@lists.xen.org Fri Sep 21 08:22:47 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Fri, 21 Sep 2012 08:22:47 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TEyUY-0007TK-Li; Fri, 21 Sep 2012 08:21:42 +0000 Received: from mail27.messagelabs.com ([193.109.254.147]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TEyUX-0007T7-DN; Fri, 21 Sep 2012 08:21:41 +0000 X-Env-Sender: shinepf@gmail.com X-Msg-Ref: server-13.tower-27.messagelabs.com!1348215688!10747957!1 X-Originating-IP: [209.85.214.173] X-SpamReason: No, hits=0.9 required=7.0 tests=HTML_40_50,HTML_MESSAGE, ML_RADAR_SPEW_LINKS_14,RCVD_BY_IP,spamassassin: X-StarScan-Received: X-StarScan-Version: 6.6.1.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 4648 invoked from network); 21 Sep 2012 08:21:30 -0000 Received: from mail-ob0-f173.google.com (HELO mail-ob0-f173.google.com) (209.85.214.173) by server-13.tower-27.messagelabs.com with RC4-SHA encrypted SMTP; 21 Sep 2012 08:21:30 -0000 Received: by obbta14 with SMTP id ta14so3888492obb.32 for ; Fri, 21 Sep 2012 01:21:28 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:date:message-id:subject:from:to:content-type; bh=mZqzsM02L1qUkM3OkVj6u2fz7QJSeCt+HIh0VO7r16c=; b=MSUddKAZikV15dA8jzPoZT+T3+52LBx/HKFYlSPbMDKx/nFQdiNeukz3Z052EdGzYW n69g5dCB59S7+QDBKhXRKhL5J3EtTc0P2cXXR0L4j7MsfXWqgf+fJLxn2duRwZ/G258p oxY0boHjHhKRPHEDc2353j3Uo7pQIuhRrdo0mbULpa2+1HbL46LkIN7oMP7gu+pnFh9c H/+CeDMzVr4fGYDiWX1aoPzHllI16Hf5V4StGdMvfCqNRURLfJmJDWYj80mR+fXLhUA8 HEccjh/vRTYztXNVgYwSwpXVn+NNSiaTyh5amuJNRzY+YzX4ImYqsvvByP53GgfAyyFn Kkzg== MIME-Version: 1.0 Received: by 10.60.171.174 with SMTP id av14mr3379269oec.61.1348215688222; Fri, 21 Sep 2012 01:21:28 -0700 (PDT) Received: by 10.182.16.135 with HTTP; Fri, 21 Sep 2012 01:21:28 -0700 (PDT) Date: Fri, 21 Sep 2012 18:21:28 +1000 Message-ID: From: pf shineyear To: xen-api@lists.xen.org, xen-users@lists.xen.org Subject: [Xen-users] INTERNAL_ERROR: [ Hotplug.Device_timeout(_) ]; throwing CANNOT_PLUG_VIF X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============5588857633045122444==" Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org --===============5588857633045122444== Content-Type: multipart/alternative; boundary=bcaec54a32522d562004ca31edc6 --bcaec54a32522d562004ca31edc6 Content-Type: text/plain; charset=ISO-8859-1 hi all : i have a problem with this when i startup a new instance on a very clean XCP server : INTERNAL_ERROR: [ Hotplug.Device_timeout(_) ]; throwing CANNOT_PLUG_VIF then xe vm-start command just return: Cannot plug VIF VIF: 7cfd05f8-6ace-00c1-95e4-ecfb1801f89c anyone can help me with this ?? thanks alot~ --bcaec54a32522d562004ca31edc6 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable hi all :

=A0 =A0 i have a problem with this when i start= up a new instance on a very clean XCP server :

=A0= =A0=A0INTERNAL_ERROR: [ Hotplug.Device_timeout(_) ]; throwing CANNOT_PLUG_= VIF

=A0 =A0 then xe vm-start command just return:


=A0 =A0=A0Cannot plug VIF
=A0 =A0 = VIF: 7cfd05f8-6ace-00c1-95e4-ecfb1801f89c



=A0 =A0 anyone can help me with this ??=A0

<= div>=A0 =A0=A0
thanks alot~
--bcaec54a32522d562004ca31edc6-- --===============5588857633045122444== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users --===============5588857633045122444==-- From xen-users-bounces@lists.xen.org Fri Sep 21 08:22:47 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Fri, 21 Sep 2012 08:22:47 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TEyUY-0007TK-Li; Fri, 21 Sep 2012 08:21:42 +0000 Received: from mail27.messagelabs.com ([193.109.254.147]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TEyUX-0007T7-DN; Fri, 21 Sep 2012 08:21:41 +0000 X-Env-Sender: shinepf@gmail.com X-Msg-Ref: server-13.tower-27.messagelabs.com!1348215688!10747957!1 X-Originating-IP: [209.85.214.173] X-SpamReason: No, hits=0.9 required=7.0 tests=HTML_40_50,HTML_MESSAGE, ML_RADAR_SPEW_LINKS_14,RCVD_BY_IP,spamassassin: X-StarScan-Received: X-StarScan-Version: 6.6.1.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 4648 invoked from network); 21 Sep 2012 08:21:30 -0000 Received: from mail-ob0-f173.google.com (HELO mail-ob0-f173.google.com) (209.85.214.173) by server-13.tower-27.messagelabs.com with RC4-SHA encrypted SMTP; 21 Sep 2012 08:21:30 -0000 Received: by obbta14 with SMTP id ta14so3888492obb.32 for ; Fri, 21 Sep 2012 01:21:28 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:date:message-id:subject:from:to:content-type; bh=mZqzsM02L1qUkM3OkVj6u2fz7QJSeCt+HIh0VO7r16c=; b=MSUddKAZikV15dA8jzPoZT+T3+52LBx/HKFYlSPbMDKx/nFQdiNeukz3Z052EdGzYW n69g5dCB59S7+QDBKhXRKhL5J3EtTc0P2cXXR0L4j7MsfXWqgf+fJLxn2duRwZ/G258p oxY0boHjHhKRPHEDc2353j3Uo7pQIuhRrdo0mbULpa2+1HbL46LkIN7oMP7gu+pnFh9c H/+CeDMzVr4fGYDiWX1aoPzHllI16Hf5V4StGdMvfCqNRURLfJmJDWYj80mR+fXLhUA8 HEccjh/vRTYztXNVgYwSwpXVn+NNSiaTyh5amuJNRzY+YzX4ImYqsvvByP53GgfAyyFn Kkzg== MIME-Version: 1.0 Received: by 10.60.171.174 with SMTP id av14mr3379269oec.61.1348215688222; Fri, 21 Sep 2012 01:21:28 -0700 (PDT) Received: by 10.182.16.135 with HTTP; Fri, 21 Sep 2012 01:21:28 -0700 (PDT) Date: Fri, 21 Sep 2012 18:21:28 +1000 Message-ID: From: pf shineyear To: xen-api@lists.xen.org, xen-users@lists.xen.org Subject: [Xen-users] INTERNAL_ERROR: [ Hotplug.Device_timeout(_) ]; throwing CANNOT_PLUG_VIF X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============5588857633045122444==" Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org --===============5588857633045122444== Content-Type: multipart/alternative; boundary=bcaec54a32522d562004ca31edc6 --bcaec54a32522d562004ca31edc6 Content-Type: text/plain; charset=ISO-8859-1 hi all : i have a problem with this when i startup a new instance on a very clean XCP server : INTERNAL_ERROR: [ Hotplug.Device_timeout(_) ]; throwing CANNOT_PLUG_VIF then xe vm-start command just return: Cannot plug VIF VIF: 7cfd05f8-6ace-00c1-95e4-ecfb1801f89c anyone can help me with this ?? thanks alot~ --bcaec54a32522d562004ca31edc6 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable hi all :

=A0 =A0 i have a problem with this when i start= up a new instance on a very clean XCP server :

=A0= =A0=A0INTERNAL_ERROR: [ Hotplug.Device_timeout(_) ]; throwing CANNOT_PLUG_= VIF

=A0 =A0 then xe vm-start command just return:


=A0 =A0=A0Cannot plug VIF
=A0 =A0 = VIF: 7cfd05f8-6ace-00c1-95e4-ecfb1801f89c



=A0 =A0 anyone can help me with this ??=A0

<= div>=A0 =A0=A0
thanks alot~
--bcaec54a32522d562004ca31edc6-- --===============5588857633045122444== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users --===============5588857633045122444==-- From xen-users-bounces@lists.xen.org Fri Sep 21 13:09:20 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Fri, 21 Sep 2012 13:09:20 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TF2xr-0005Y1-7B; Fri, 21 Sep 2012 13:08:15 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TEysy-00085i-7M for xen-users@lists.xen.org; Fri, 21 Sep 2012 08:46:56 +0000 Received: from [85.158.143.99:46026] by server-3.bemta-4.messagelabs.com id 85/6B-10986-F792C505; Fri, 21 Sep 2012 08:46:55 +0000 X-Env-Sender: lukas@laukamp.me X-Msg-Ref: server-9.tower-216.messagelabs.com!1348217214!31264539!1 X-Originating-IP: [5.9.218.245] X-SpamReason: No, hits=0.7 required=7.0 tests=BODY_RANDOM_LONG, RCVD_ILLEGAL_IP X-StarScan-Received: X-StarScan-Version: 6.6.1.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 18510 invoked from network); 21 Sep 2012 08:46:54 -0000 Received: from mailer0.lippux.de (HELO mailer0.lippux.de) (5.9.218.245) by server-9.tower-216.messagelabs.com with SMTP; 21 Sep 2012 08:46:54 -0000 Received: from localhost (localhost [127.0.0.1]) by mailer0.lippux.de (Postfix) with ESMTP id 8E7E8422570 for ; Fri, 21 Sep 2012 10:46:54 +0200 (CEST) X-Virus-Scanned: Debian amavisd-new at mailer0.lippux.de Received: from mailer0.lippux.de ([127.0.0.1]) by localhost (mailer0.lippux.de [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id t6mEqpslRR-4 for ; Fri, 21 Sep 2012 10:46:54 +0200 (CEST) Received: by mailer0.lippux.de (Postfix, from userid 33) id 37A9442257B; Fri, 21 Sep 2012 10:46:54 +0200 (CEST) To: X-PHP-Originating-Script: 0:main.inc MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="=_9426c50732c409617e0267e2dc8a7504" Date: Fri, 21 Sep 2012 10:46:54 +0200 From: Lukas Laukamp Message-ID: <9d23dfce1e8d125f8d370c827ea94378@laukamp.me> X-Sender: lukas@laukamp.me User-Agent: Roundcube Webmail/0.7.1 X-Mailman-Approved-At: Fri, 21 Sep 2012 13:08:13 +0000 Subject: [Xen-users] Xen 4.2 (backported packages) can't load Dom0 (Kernel 2.6.32-5-xen-amd64) X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org --=_9426c50732c409617e0267e2dc8a7504 Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset=UTF-8; format=flowed Hey all, I have a problem with Xen 4.2 on Debian Squeeze with Kernel 2.6.32-5-xen-amd64. I rebuilded the source packages from Debian experimental trunk on Squeeze and installed them. Also I installed the Kernel 2.6.32-5-xen-amd64 from the Debian Squeeze trunk. Now it looks like that Xen can't load the Dom0. After registering netback strange modprobe errors appear. In the attachment is a screenshot of the errors. I also build Xen directly from source without packaging it and it works fine with the 2.6.32-5-xen-amd64 kernel. So I think it's a problem which only appears in the packages with the Debian patches. Does someone have an idea how to solve this issue? Best Regards --=_9426c50732c409617e0267e2dc8a7504 Content-Transfer-Encoding: base64 Content-Type: application/octet-stream; name=xen-dom0.png Content-Disposition: attachment; filename=xen-dom0.png iVBORw0KGgoAAAANSUhEUgAAAtAAAAGQCAIAAAAIhcA6AAAAA3NCSVQICAjb4U/gAAAAF3RFWHRH ZW5lcmF0b3IgVmVyc2lvbgAwLjkuMSqKm2cAAAAwdEVYdERvbWFpbiBVVUlEADQ3MjBiYjcwLThj ZDgtZjhkMS1jYTZiLTlhMmFjOTRmZDczMnzf/TUAAAA3dEVYdEh5cGVydmlzb3IgVVJJAHFlbXUr c3NoOi8vbHVrYXNANS45LjE2LjIyOTo1MDAwMC9zeXN0ZW1SiP2zAAAAGnRFWHRHZW5lcmF0b3Ig QXBwAHZpcnQtbWFuYWdlcqvpgfMAAAAYdEVYdERvbWFpbiBOYW1lAGRlYmlhbi1kZXZlbP0O5PsA ACAASURBVHic7d3Rmqwor4Bhe565SC+xLnMf1D9sWkgIISDa33syawqBiICoVfZxAAAAAAAAPN3P 9z+fzyd9dJ7nTcE4w1By7Z9UlW9/yVgmpQKVpDLVmMvhW+Cl/JEyU4RSIc0NfJXGlvb9x5rBNSn4 w9ajlDCanS1wEF1yLWh5X0M59qvZ8sCe/sn/5zzP21cbKYbqSbcr1yZJR3/Dpo3LjGVSOaWWSXl4 9lybaDZdeKcNb4GVw2pe8OVJtNqj8g2kU6MyUsq6juHJwZ7FTYqw2VDSLlsq2nPAApJ/2psscbkO Ng4kJdcmSSFuv4L5fD5MarCLPdNXx1eX2SNoPEK7ey8LgRH/3h0AGr73pd8xxaR5uXqju3lvuffp jOPOc/Wu1UiB7giNSdLnC4KX5FV/j3XsI54jYs2hP2GUuqijuksLxLbD+PNKYKVd7nAkvotpJdcm ST5KaamucrpRkvS6pFxRK550yVu9G9y8S+y7nd515znf08teh9/KVgrU69I/XxP8IF8X7a3i8o9L UrU18v+NaqhUzozJgdUGHoQ7HFvLr7RCknx1rWFcEHRdMb/jSZB+dW63sjX0uhacJlN/HrxF0UW6 +ZSvOUL2ndUGnmi7BUf47LBJkptenTSF+W5l+3KFiL2mTN43I4801MrWSHU9es3X22L6cYkaX6w2 8FDbPVJB1e33Hh592sDLPKg38iQFSHZZcEjPsPNtyqGr5NokKcSDptdt+eb9TVZa4cFvsl9G1fG1 lRu/FvOsQ4k/7kkv/pJO5Equ/ZOqqjOI/dttZVJZZvl5NZePVFc14GokxuDL1LIuKZdxF0IKdERo SZK+pnBv8NVjV/2Kq70uS157Uc3g7bVUy/wel8He26xFKRMAAAAAAAAAAAAAAAAAAAAAAAAA3upJ P4t15No/qcrys9iyQCWpTDXmclB+FTlSoFJIcwNfpTPepLJmcE0K/uj8nW0ZRrOzBQ6iS64FLe9r KH4Wi7/j14u/zvO8fbWRYjC+zUbJtUnS0d+waeMyY5lUTqllUh6ePdcmmk0X3mnDW2DlsJoXfHkS rfaofAPpXKuMlLKuY3hysGdxkyJsNpS0y7rzt4g9AKbb5U2jl+tg4xyh5NokKcTtE8rn89ltFYKd xZ7pq+Ory+wRNB4h8Bds98fbcPHJ/pj706V5ufkqzOr+9j6dcbxbs3rXaqRAd4TGJOnzBcFL8qrP OX8OcHzN0XxN6uCzmHzxkbfAOwYy4LPLHY7EdzGt5NokyUcpLdVVTmFKkl6XlCtqxZMueau3l5Xb zpfslrqat7KlCMvb/iMF+iLU69I/XxP8IF8X7a3i8o9LUrU18v+NaqhUTmCbfzJRZQKzcYdja/mV VkiSr641jAuCrivmd0zH+tW53crW0OtacKF/Cn9oxp7dkUu6+ZSvOQb3vewM4TeQgEm2W3CEzw6b JLnp1UnTje9W9qQb4Bax15TJ+ybikYZa2Rqprkev+XpbTD8uN44vYAfbPVJB1e33Hh592sDLPKg3 MnaAZJcFh/QMO9+mHLpKrk2SQjBhjfPN+5ucLcKD32S/jKrjaysrvxbzrGMH5J704i/pRK7k2j+p qjqh2L/dViaVZZafV3P5SHVVA65GYgy+TC3rknIZdyGkQEeEliTpawr3Bl89dtWvuNrrsuS1F9UM 3l5LtczvcRnsvZaKfHECAAAAAAAAAAAAAAAAAAAAAAAAwHM96Wexjlz7J1VZfhZbFqgklanGXA7K ryJHClQKaW7gq3TGm1TWDK5JwR+dv7Mtw2h2tsBBdMm1oOV9DcXPYvF3/Hrx13met682UgzGl9so uTZJOvobNm1cZiyTyim1TMrDs+faRLPpwjtteAusHFbzgi9PotUelW8gnRqVkVLWdQxPDvYsblKE zYaSdtlS0Z4DFpDs8qbRy3WwcSApuTZJCnH7Fczn82FSg13smb46vrrMHkHjEQJ/wXZ/vA0Xn+yP uT9dmpebr8Ks7m/v0xnHnefqXauRAt0RGpOkzxcEL8mrPuf8ubLxNUfzNamDz2LyxUfeAu8YyIDP Lnc4Et/FtJJrkyQfpbRUVzmFKUl6XVKuqBVPuuSt3g1u3iX23U7vuvOc7+llr8NvZSsF6nXpn68J fpCvi/ZWcfnHJanaGvn/RjVUKiekzfPSuO+IZ+EOx9byK62QJF9daxgXBF1XzO+YkfWrc7uVraHX teBC/xT+0Iw9uyOXdPMpXyWM77ty4wrY2XYLjvDZYZMkN706aQrz3cqedAPcIvaaMnnfHeyRhlrZ GqmuR58Re1tMPy43ji9gB9s9UkHV7fceHn3awMs8qDcydoBklwWH9Aw736YcukquTZJCMGGN8837 m5wtwoPfZL+MquNrK3d9LWb292CAWE968Zc0upRc+ydVVWcu+7fbyqSyzPLzai4fqa5qwNVIjMGX qcrj7a6dujTLYIGOCC1J0tcU7g2+euyqX3G112XJay+qGby9lmqZ3+My2HstFTmCBAAAAAAAAAAA AAAAAAAAAAAAAIBHe9LPYh259k+qsvwstixQSSpTjbkclF9FjhSoFNLcwFfpjDeprBlck4I/On9n W4bR7GyBg+iSa0HL+xrKPfc6XhMA3OvXi7/O87x9tZFiML5FR8m1SdLR37Bp4zJjmVROqWVSHp49 1yaaTRfeacNbYOWwmhd8eRKt9qh8A+lcq4yUsq5jeHKwZ3GTImw2lLTLlursYQA72OVNo5fVunG0 KLk2SQpx+2XK5/Nh5oJd7Jm+Or66zB5B4xE6qjOGwcjFPrb74224+GR/zP3p0oTYfBVmdX97n844 3q1ZvWs1UqA7QmOS9PmC4CV51eecP1c2vubQnzBKXdRR3aUFQtqBlQQeapc7HInvYlrJtUmSj1Ja qqucwpQkvS4pV9SKJ02U1Vu+ym3nS3ZLXc1b2VKE5W3/kQJ9Eep16Z+vCX6Qr4v2VnH5xyWp2hr5 /0Y1VCpnWZtzSxJ74g7H1vIrrZAkX11rGBcEXVfM75h29atzu5Wtode14I7dKfyhGXt2Ry7p5lO+ 5njH3UrAYbsFR/jssEmSm16dNIX5bmVPugFuEXtNmbxvch9pqJWtkep69Jqvt8X047JsfL2v2+Md tnukgqrb7z08+rSBl3lQb2TsAMkuCw7pGXa+TTl0lVybJIVgwhrnm/c3OVuEB7/JfhlVx9dWdvha TBnG7G/JAL2e9OIvafwoufZPqqrOXPZvt5VJZZnl59VcPlJd1YCrkRiDL1PLuqRcxl0IKdARoSVJ +prCvcFXj131K672uix57UU1g7fXUi3ze1wGe6+lomrGTSZzAAAAAAAAAAAAAAAAAAAAAAAAAJjh ST+LdeTaP6nK8rPYskD7j+XsuRyUX0WOFKgU0tzAV+mMN6msGVyTgj86f2dbhtHsbIGD6JJrQcv7 Gso99yojizdwYE+/Xvx1nuftq40Ug/EtOkquTZKO/oZNG5cZy6RySi2T8vDsuTbRbLrwThveAiuH 1bzgy5NotUflG0jnWmWklHUdw5ODPYubFGGzoaRdtlTXmwTca5c3jV6W5MY5Qsm1SVKI269UPp8P sxjsYs/01fHVZfYIGo/QUV1vEnC77f54Gy4+2R9zf7o0LzdfhVnd394bxY53a1bvWo0U6I7QmCR9 viB4SV71OefPlY2vOZqvSR18FpMvPvIWCGkHZSW3501K4GuXOxyJ72JaybVJko9+KSOdgJUkvS4p V9SKJ82G1dvLym3nS3ZLXc1b2VKE5W3/kQJ9Eep16Z+vCX6Qr4v2VnH5xyWp2hr5/0Y1VCqHdQD+ OO5wbC2/0gpJ8tW1hnFB0HXF/I4pXr86t1vZGnpdC+7YncIfmrFnd+SSbj7la44F+w7sabsFR/js sEmSm16dNIX5bmVPugFuEXtNmbxvch9pqJWtkep69Jqvt8X043Lj+AJ2sN0jFVTdfu/h0acNvMyD eiNjB0h2WXBIz7Dzbcqhq+TaJCkEE9Y437y/ydkiPPhN9suoOr62ssPXYoD9PenFX9KJXMm1f1JV deayf7utTCrLLD+v5vKR6qoGXI3EGHyZWtYl5TLuQkiBjggtSdLXFO4Nvnrsql9xtddlyWsvqhm8 vZZqmd/jMth7LRWVGZUkAAAAAAAAAAAAAAAAAAAAAAAAAHiBJ/0s1per+WNaqSLlB6J6mV0/3FWq vpB+62/8RZzld4D2CBXKryJHClQKaW7gq3TGm1TWDK5JwR+dv7Mtw2h2tsCfxV5yLWh5X0ON/yyW H77iKX69+Os8z9tXGykG41t09FzKi48OdX+V2vUyq3obNm1cZiyTyim1TMr3155rE82mC++04S2w cljNC776PhV96EmnRilXta5jeHKwZ3GTImw2lLTLlor2HLCAZJc3jV6ug40DSc/VXG3oxXYlTR3z t1/BfD4fJjXYxZ7pq8O8y+wRNB4h8Bds98fbAvnmuzR3lBmVpHmXGp/sj7k/XdmA0p3n6v72Pp1x 3HnOs5TVhd/KHnzTqPL5guAledXnnD9XNr7maL4mdfBZTL74yFvgHQMZ8NluweF75O/IVZ21Hd/b mMpyr6UMyTdXKrmi9voy+V5ORflRqJ6ius5e5VdJLBnzhaN0V7+rQF+Eel3652uCHzR4Ou+qotxT pTVSHzs6+5viUuZIUZfSgGfZbsGxjDL5Xq4UjUmTgpRmFl+Sr641LLX3ngPeMS/rV+d2K1tDr2vB WucU/tCMPbsjl3TzqbrCdlNuXAE7227BsXJ20Mu5zFZK0lRKLcrZ13dxNukGuEXepIFz6PvuYI80 1MrWuNw1fKjeFtOPy43jC9jBLl8ahe72ew+PPm3gZR7UGxk7QLLLgqP6A5PyTvJl6FpyvQAT1jjf vL/J2SI8+E32y8j467MbzfvOuO6tMx7e6kkv/pJGl5SrHP/SbV57mVKSUpdeWlV15rpMauU3BJWk sszyc+Urh72U5i0DrkZiDL5MjfpdxqVZBgt0RGhJkr6mcG/w1WNXnpKVr2ZXNxgZRPoAL6O111It 83tcBnuvpSJHkAAAAAAAAAAAAAAAAAAAAAAAAADwaE/6WWwzo/4G6PHfUvqSlLrW8/3qNfzdiPu/ P6Dc5epvTQeriC0QAHb268Vf53nevtpIMdjfolPdMi+tLFCqS8nlS/q6t2EHbfiepdmU96AEem6X AACHXf6WyuWS1/5HB6TToZJRqct3DnjQmWOTUDcJAwCwzC4LDjfL7RD3c4RluaRCel8Zqb+DUrqH b3nrolJaNZcUvBSGcZeld2uWfG2o77LyufEVmUrk+z9mAoARu/wtleR7syG2wEN+j7JUV5krrWy6 cvnkqyjfk51qJFIjSAXmt3wut3/0XFLwShhpS8d+VRkLtO9yWfLlw7I0va4cqw0Ar/f4Oxy62LsU yiWyuy6dfjUcVUX+9Korfj2MzU+fI214Fo/8jKXpaz53PACwv+0WHIHTbnMeD5z9p54z9KVPSPnp tk1XyfY7DRua1NP+4HdsAcBiu0cqUR73vY176Tf8MRUtD+Av2GXBIT1lz7cZ+XpHntdSl16jvsII /xqKYrwupWXsda3c5XAr90sqkDUHgNd70ou/pFXIZTNl7pa+hKE/ia+m6t/nsNSlsLSDJRKlrey5 8g0suZo7q4dRfufUEmHVSIFdu3zZ3liX8jVbAACe4dG3HBRv3S8AeL1dHqlg3FtPxm/dLwD4U37u DgCRNnk0Fu6t+wUAAAAAAAAAAAAAQPIz7+l49YeFedK2D+OVyJ9Of+nI+/YXALCJf/I/VRVb9HPP Xs+N3I2fgQAAprrnb6n8wTP6Jmh5AMAtGgsO40stm2/DrCZV3zKpv+GxfI2jg15XM2NibA33i0GV GPQXdEqlNd+eufmjLgDAsyl/MeRyNrJsln9iz3L50PLvEc0ylZ3SI9E3U+o17lozsK7wemsHAMDH /0hFOj+9+ypZ3+tS+svv3wbpuhUUGB4AAPdyLjik2/ivp/w1Mqk10pqjmt29MrM/WwEA4HaVv6Xy xHPV5k8EzvNkHQAA+MuuCw7OiEaOr1zoa46uNVP+RRBjFnvJ9m+EuJMAAH/NT/WUkG7UX1KNvxxR ki5l6k8ELGGUeS30AvUI9SSlNboKbAavN1RXy5d5lRpDkgAA2Frv9XdXOQAAYJJ7XvzVpXmhzDU0 AACb+7k7ABP9WcC9pQEAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAEOPHstHn8/n+4zzPmcGsrksPQwpAStok8qMV/LF3hL7Svv/oLbPa Gqm0apl56u3N6LBPL7UbjDl8l8ve+8RWLcWOyhfzNdQmc++9/rFstLKNdjgel1OOMWmHyA81wk3E RpgP466Sqxun0r4um+WpvdVtYpNe2mUw5thdrh70J7bqxRM78y1oqBGmBQdeI50s36drvxyzxuUC 5blrDgDrhc+9n8/ncfPPv+UFon6HWfo85SoLka5By9ZXLjr1ILsibAZf3RElyR1GrGaE1Ru/evO6 27BZ2ow2tLftyuWCow19SalJpTv8vWNZoddlDL7rYdalXmOuwENs7L29EVqqO4TxVX7i6BvjozIV W456e2v4chkjLHOFN5Tx1FY9cL2D6Ll+LIf50p/KLY2F5BX31lXSD4A9QmPAzSRLUQse4/kiLOkH 3ZhkPPRde2Rfv/aWnH9YFlv2T8uOjLehPcm4pb0EneV8oxTYFYavrq4jZaTvTm+ExlrumqWNEYZ3 15AuOmMQWWo3dviRFniuf5U0Y8t2kbI06yonet13s89/3+5RJogFeuuqbj+1tynNu7KhesWeS47a OP+MfZMupB+O753SSs0IfbHpI91XbFddt8zRva2hW5lrpVv2a3ZPiG32wVG5LW3B0dTbCtK16STp mB21UFcewqhJ/BZbBbMDx9HcpB9K9AiNJTQ/OabNADu0oS6qVeflWul9+zWjY4+Pyg3Ff2n00uj3 ttd5nsvWN4Bk/364f4QzpAn9QbaaYDGVPiqf2HtjFhyXPU9tdONgyEPSZ1LlsPmSjFHNFl7X/gVO 5ZvoZ/fDcfYIx8vfM5fPjftlnGBpw/FcKwuUCn/TlcDPIX/dyZiUNrgUXR0MjrrSv8t/6PumRGgM viupnBGMdYXrilBvXl8bKkdZj7C5R9Xgu4qqFiiVWRbrqHGwDR1JyvfODtdY1neq+cUUY99oHmV9 v7rqyjfwPRoOidBSi5RLH1llLqVvSPvljtDX2WK7qLEuKam3ofTOpp8dArsNAGA7Ky/l342WhNHQ l0YB4KG4ZAQWM/0tFQAASu7HmgAAAAAAAAAAAABKL/kOR+8PuowFPvSRpBS88rQ1PKkZ3u0FbhKG r8B8g8ACHdy/LFXeHtFb4Mh+6b9FrJbpHl8PnU+AKC/58/SM5KY05ZUv2AhPCg+D/Spz9f4Q0RfG DLFVj+yXtA44/yNl6Q3j9jYHdhC24Fg5lhbUJU03U0XtVxn8ZWLNp7/wpLzS8pORAi/lvGa/ugq8 tICRr3ktwkdKV4Fd+6XntdTeXG0oYbDmAGLew1GdLpM0Dqt3Ly//W+bS66p+0hWGEkn1tF2N0Jck FZ7iqUaiFygF/xpM2WX3CC/8UpH0idI/q71XL1wq8DAPotlYNAAjAu5wSMuIrpucxlzNGbC3wCrl Vmq1QF+Ssl9pS0eB+lxcXkzPS1IuFn0FHurhfu5+dRUotYCRr3kl1S3zbnnpovmeVve6d+jl24Sv AxxNPSMM4DVG73CUY/L874/qfj80DldLLvtq47LBDNISp9zMsV8jYbzY4Ln2TS63CkLaJLx5H32k 6GxAuKEFhzQm01m2mirRc/nG/8r5Qqprxn65KRWFJ8WGoTfUc/ert8CuBbc9jHn9cE3fjq3F3Ros UACF/5FK8wSgPEGQSLliZ0PpIUVI4VKNC/ZrN4G3l7dqqPDb5rffh1euHI61IwXAizkXHMrUk8+e 9jWHkitkmrvM6akKd+HGp/WL90uiVB2eFB6GUvij98tXoEXZK3zNm28zY7UxvtIaaSjHFdFIGCzX AOeLvz7qY+PqZFdNylOlXMa6zv++Fd8s8JJX/zaGEvxgUlQbVue125MUvQXqDeWO8Pb9GinQUp0x S7N5HQUqYV+2MTaUu883dS0OlOlLD4PVBnCz8eubF6NxAABvctubRlnyAwDwdyz9WyrNZxz4GrlF DAAAAAAAAAAAAAAAnsj0HQ7pN2xugT+Km/d7udnCW9Ve42Frw+rPZIy/A3wxy+9Iq7m+/5C66O0N 6NuvGWF8/xE720gvDVp2ONzdZs1BmffLbccvunvDwFOYfqUSfuD1As/zLM9q53+OrFMqSdWitnJX YPbmzbfPN5CK+gvcv1WWGmqTBtznN9i3rL9n1+5r3mUHJZ8E7PXquaRClFy+MPAgt/0sNsTgCY93 XQCv9weXxV0u9yGMJ3s9V3O1UebyhYFn+Tc/zMpL90r6ffjqNbRe4Ob0/Wq2RvNWrfE1qfYCN6R0 Nn2/HJ3NV2CzLr3eaoFlapPUOMZcjjZs1ms/Xu6WL1Ob7LONFIP+wEVKkjZOHN3GGKE+Y8e+eqDZ vBKWC6hq3OHQH8Ip9+F7C1Sk8tMNiXKSkpKaJYecrZXWKOeFakNJc4q7QDt7806dPlIY5S4bW+P4 3Sy+AvW6Ustceo4+HBw900fpG7798tXla/ljTkNVS7Ps8ue/L09Yur27eaWm8B0U97ScslfXK9Xx peTy1TVYIB5B+/P0zfE/fjniyPXtjnkhStI+ms1YbqA3b9RuKs1bnVnual6pNc7zzGcoe3iW3tu1 s5al5BpSdTPmcceu7dNQiq5IUiesDhxF7BFxh2EpM/3veJn4s7QFR9Pf7HwjM2PvLBZb4KMpe3oW f7dvsECf3Y5FGc+8CO9t+WOD9Up+Yu69IXHErTwcYeR5lTKlDcJnwt3GEQLFf2nUchduE5vcu4ud cf6gS2cDbuF7kLF/GIwvRIlZcFzO3Km7z15trF8xTBp7+gRx18JokwXZxSWq/Ln14TouvsfJj34I vUnwUXUNjsrxMMqHDrHNa8xlDyOnXyJK48t3YanketCVKtx+jt99qNrb9KS0waXoao9RCryUKX1u T1IK9ClvgTZbQwmgOnRHCjTGX+Zd2bzNHuVojTLg6mwbsstHceDsBY70+WokUmB62M0NLMFb6uo6 lEpdOqUuY5zV8KQC9TC66joMu9ybqxmGJX7j+JJylWEoqVNnbABYZP87DUav2REAf9mzX/wFvB73 lgG8g+lvqQCP8+h7s+4b4wAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAKLP5/P5fO6OAkDDv5aN0mA+zzOkVqnAfNbIky6ziTFJKXAH4a1q r/GwtWF1Epcy2vfCvePfjGWuwQIdGR3lhAfvCyO2ZL1GaZf3MWlm23mXFc0uWqaGJzXDu73ATcLw FZhvEFig3T+WjcLHj17geZ7lWe38z5Htv5JULWordwVmb958+3wDqSiLvK9HXZW6WzLqEIyUE9gN 5vUoqeRtB5fR0+NfIJ8fjt9jNjwpPAz2q8zVO+v6wpCYFhzbGlxPcCf2Ro4Dt/PysenRwfus2WX7 5dqCwX7LUQ5cuF+Cv7RtfsoJT8orLT8ZKfBSzmv2q6vASwsY+ZpX8W95xVntc83SU66ykMsnDz3H 6/vVbI3mzVu9lRwF7k/paeVOOfZXasNqqrE0pWM3Pyw/b1aX9B5lKdqytGaP8g3Yaml6XfmH9mWE sWXsl3rjM5vegNJBsSdJhRubVw/yufOJ7qHnnUBl9wgv/FJR+UnjDoc07PPbLL4bPpaNv1L5aUFX DhUpqVlyyOhSWqNcyVUbqjpzjRRoZ2/e8W56ucIoI1G6k/uMWy3T0VuMleoLUHs5h2t8KWFIpaVP YhuqmkWpK9/l8KNjXCweYy1fDVgp0Jek7JexeR1dVBn+4UnKtOwr8FAP93P3q6vAwTHla96S9qXR Zim9ZyDfPpcn4zSffilJ+2g2ozT3OQrsojRvdeUxUq9+Lhlf0BjLnLTaCC/T3SBRzTuvoVayrzYu G8xgHObfkSKNxDyj7+g8/Zh2eUc3DnG5lghpk67mNf1KRfI3D+GycW7Z+DWHIG/VwOl+Rvssm78m XeLPO5tuyHewVg4rqa605qhus/gkqlQUnhQbht5Qz92v3gK7Ftz2MHqLiv/SqHQrL7yicfptomX+ 4GkAWCB28lk/s0mPP3aeVMcFTstbNVT46eb285fUvMpIiVlwXPY81Tf7eK9v8UsjRtHXHHd1rNs7 dKCofZnUAZqVvuZALBMy+YTPbMqhzJPyf89Y6Bh7lFJ1eFJ4GErhj94vX4EWZa/wNW++zWWzn7y4 8hG7JSmv4BJ9+blS4KVM6XN7klKgj9LcUhhKANUJZaRAY/xl3mXNq2/v6xtKkmW/qnXp8ZfHSz+U 4cHr4UlhNMdyb66R/erq8z4f9RF1+Mx2RI8vZQaw7FdXXUrwi5MUvQXqDeWO8Pb9GinQUp0xS7N5 lQIBYBfG62+UaDrs7Nkv/gLwDpwpgdf7uTsAADiO6AegfxANCAAAAAAAAOCLR7wAADzX/79p1PcL FuW3MY4CeQYJAMArDf1KJfaWQ1qgXN5tAAAA/rTAxxxlUfknPE8BAODR/vdI5fKOwvzD9Ca+4/db xsrN8nKrBR7FfQvjcxMerwAA8Gj/e6TSfOF8+QrnlCX/9yXvRf7QRHpuws0MAADex/QdDm4wAACA Ef+2N/nPmmUHixsAAN6Hv6UCAACmi1lwjH/x4vKVDv6sLQAAb/K/P94m/cH78sMLy69Ryl++SMXy 4i8AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA0M+XXQAACb9J REFUAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAACD6+f7n8/mkj87zHCw0L00q8LvNJckdRrU0S4F6 xvzzy05dytR32bdf1VyXwPL/HYnQ7fP5hBSVwosKbJNKZ1QhHUq9A1yyW+JpBh+4d4NFObLf0uVu Vw7YG4eeMk/qqU88ZH+zv138k//PeZ5RE8f5n6M2D1ZnxjyjtI1So6NAPWNVvl/Viqp1+Ro2ZdEX UtXteyP0CSnk65ZBuKDS8CqMna25RLBoBh+4d4NF9WZvrtRfybgkvSUMvWO7zw77+MvrjOSf9iad midXvbelQqQtLaVZCuxdbYSsxgI1G8cxBT9xGL9beVCUfugben/cVoP6L3BMsO6zA3bz79TSpQcT 53lGdRdf51PCeFBvVoL83jidN5lWLz6qqV13TZUy9TDyo5Zy2e/QlvWW9z+VJMt+Oe4hN9kfjhxj Q6+rokPdL18HcBxKO+NB0TuAxNdFBzubEkYZQ7mZZSz7WuP43Q56tOPTl68fOpKarWG8vn398jf+ DkeirDb0XLEn+7LA8d4srbiX3SSYcSHbtUDJNy4zWu6LKvOO4wDlLf/9h/EObblfx+/lmnLCuNSo 75evNeyXfXrqYJ/vWoUr++XrAL5D2YywWrtSl9IBjJXau+hgZyvpAzaVXBYoVaSMlEH6eshei68f +pL01pD2yHcoH23WHY7mIjr92z0JDnKHUd21/H+XrTmkipSkNfTAUmsr3aOrV6T9Ne54yNnXlzHf /TyYXl2rjWpdvUOvGvygrg4QtTY9fneYrowpuyNLVxdt1jVjgDen6wXGrwaT5mxjXKgNhqHskWU+ fJkpCw798tG+TQhfGJLA8TBOX3MsDibRLwHTGDu2aUafqOAd5ThWGyN9fhO7BbwyngXzZJX7ds54 dVW+leWyc43Da+ZDo/hHKn+n7V6m63blCP3+4R+5tWhUHpTXjy86wN80qWPv/7Ri/wgDTfwOx5fx NCY9LXMUZS9whtefD6qMhybfjDXHhW/Bt2yZOIMUvN4BHr3L4d7abZS5wjjHGmebQ22NqQ1liXD/ I9Ul/sVfygxS3UZ6nq18xUavrrfAS6qlQGNRxlSJEl71f+0xdIVhDLLa7OXDcimM6sCzzCmXWpSb wFERVgOz1NWVJGmOL73peruiHqFlIBuT9A7gO5SWnbIfypFR3NtF543lcsAaW14aKV0Dtgz+EJri EuThav/wUdlM8rWhsl/2hgXwPC+7pACATUx/pAIAAPBzdwDARgKfLQIAAAAAAAAAgAXyry7yNUYA qGKqfJD/vWk09tG15Vdbzd+4On7r5fg9qv4jpWrGsq4ZP+iKVf3xamCx4SVDMulQ+vQGs1Xwx3F8 gt7UPrhfShib/CoyqqF2oxy4qJZv9o3Fg6I8lJYAolrj169U0ivPRqTIlBeoVc/QeUZpG6VGR4FS xvM3S5bj9y5Xk9SdmGtG7b7jxSXIoK3m/d5gtgo+sB+O7Nf+w2H/CN0WdMhmFSsHheWKeqr4n8U2 T676aiMVIm1pKc1SoGMU6QuU3tJ0lwK3mqmPgePVu5pUar/dyjA22WWfRwd/r9uvVfY3aaqk5XNR rTHrr8V+SU8fzrg/Z+o7gfnCCDlZ9lZ3FEPI9yK8yza9uQKdY393tFw15sfx8nSsmnQMt2G5mZRL eTmju64yqVngjIYyMl4SNF/U2IzwdL1pVB8O9qGn7JovjOP3rkkf2nuUpYsqpXXdVPeNL/eolKbK riCrSb651zjxdoU3OCqNh9LeD31hTHzxl7La0HPFntHLApthfDKO6vTCB+UPMi4LICUpz+7Ipcfj aCX30k26s1IGX06gll02toZ0RuxqQ19dvjCU1lDacLBvKMGX/VBhjNA+9FI5l3/nn5ThjR+vrjCa heRD7/uP8Y7dG6EUmCOM8OCNQVZT9eFWDaMZXlfktxxKaVQ6WkMy6w5Hc5ZM/zZ24nDVMC7BfIe0 PcLZq41LRbpqGHe1dunsv8/ha96RXdZHWr5Zvi/GGi257KuNy+dKpZbY7AU2M27eD0vS/g4er1hn 8cdZLjHcqNlQvdOXb3wp3DOJEoZxp7omPWnhEtsaecldGzvCmLLgkA5n/ollmxC+MByWzTXLarFw R9LbXIPNG9ViSr9NV5z2uvRc8xZYvTNLVwBfK4dDoDzscrr3HeXFdghMbyhHhJu0vBSG3m1GqusK YzFHGPGPVG5vBexv8WojSvM2rGPGkXI1dzl8dgu0yfGaQT/KOx+UxXzDYWWBhLE+jOl/vC2tgHSX oKsTlrEoe4HuaPehBDx1X3zN69jYsX2gvA2VMPLN7MNPyWXcZb2u8A5gLPBxqw37flmOsvs0cNfx Ci/QPhyM05dvfIW7MYzw1hjvG74wflLm9NHgTKEMwuo25Y0pKQxpFaLUZSnwknopUCpNSpVOSEoY vewRljuV9wzLLtsjmbTaOFpf9GnucrU6Xxs6wiiTpCCNdfkOpX1kdfUNaQQNBn8W3wB1R6i7xGMM o6xL3y9fGIfcvJfYysYpcxmTyl3WI2zukS+MriQffZctZygpyd5txuuqFqgrD2Wz9zoiBN5pfKm+ 0rOifRbaFtjc3PdwAEgcd3egM95WzC1u/03CCPfW/cJUP3cHAPjFPquagbuOs+3fBwAAAAAAAAAA AAAAAAAAAAAAAAAAUX7c76AcT1JeZhf4MkEAAHC7H+X9Lb1vF24m5dwl8PYkAAAe539vGi3fzJ9I fxvl+yLh74k/P/0rSVJpFry0GACA52q/2ly6l5AWFuU2UpLyR4bcYQAAgP0N/Xn68zyl1YOSBAAA /pqOBUf+xxjzf18WFkpSiOrfhOQPRQIAsLOfy1c3Lt8Vnfcrla6fojR/pcI3SQEAQB9uVwAA8DJD 3+EIxCIDAIAX+7k7gP+nvBMMAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAADz+D2AdaNOyuipZAAAAAElF TkSuQmCC --=_9426c50732c409617e0267e2dc8a7504 Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users --=_9426c50732c409617e0267e2dc8a7504-- From xen-users-bounces@lists.xen.org Fri Sep 21 13:09:20 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Fri, 21 Sep 2012 13:09:20 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TF2xr-0005Y1-7B; Fri, 21 Sep 2012 13:08:15 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TEysy-00085i-7M for xen-users@lists.xen.org; Fri, 21 Sep 2012 08:46:56 +0000 Received: from [85.158.143.99:46026] by server-3.bemta-4.messagelabs.com id 85/6B-10986-F792C505; Fri, 21 Sep 2012 08:46:55 +0000 X-Env-Sender: lukas@laukamp.me X-Msg-Ref: server-9.tower-216.messagelabs.com!1348217214!31264539!1 X-Originating-IP: [5.9.218.245] X-SpamReason: No, hits=0.7 required=7.0 tests=BODY_RANDOM_LONG, RCVD_ILLEGAL_IP X-StarScan-Received: X-StarScan-Version: 6.6.1.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 18510 invoked from network); 21 Sep 2012 08:46:54 -0000 Received: from mailer0.lippux.de (HELO mailer0.lippux.de) (5.9.218.245) by server-9.tower-216.messagelabs.com with SMTP; 21 Sep 2012 08:46:54 -0000 Received: from localhost (localhost [127.0.0.1]) by mailer0.lippux.de (Postfix) with ESMTP id 8E7E8422570 for ; Fri, 21 Sep 2012 10:46:54 +0200 (CEST) X-Virus-Scanned: Debian amavisd-new at mailer0.lippux.de Received: from mailer0.lippux.de ([127.0.0.1]) by localhost (mailer0.lippux.de [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id t6mEqpslRR-4 for ; Fri, 21 Sep 2012 10:46:54 +0200 (CEST) Received: by mailer0.lippux.de (Postfix, from userid 33) id 37A9442257B; Fri, 21 Sep 2012 10:46:54 +0200 (CEST) To: X-PHP-Originating-Script: 0:main.inc MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="=_9426c50732c409617e0267e2dc8a7504" Date: Fri, 21 Sep 2012 10:46:54 +0200 From: Lukas Laukamp Message-ID: <9d23dfce1e8d125f8d370c827ea94378@laukamp.me> X-Sender: lukas@laukamp.me User-Agent: Roundcube Webmail/0.7.1 X-Mailman-Approved-At: Fri, 21 Sep 2012 13:08:13 +0000 Subject: [Xen-users] Xen 4.2 (backported packages) can't load Dom0 (Kernel 2.6.32-5-xen-amd64) X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org --=_9426c50732c409617e0267e2dc8a7504 Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset=UTF-8; format=flowed Hey all, I have a problem with Xen 4.2 on Debian Squeeze with Kernel 2.6.32-5-xen-amd64. I rebuilded the source packages from Debian experimental trunk on Squeeze and installed them. Also I installed the Kernel 2.6.32-5-xen-amd64 from the Debian Squeeze trunk. Now it looks like that Xen can't load the Dom0. After registering netback strange modprobe errors appear. In the attachment is a screenshot of the errors. I also build Xen directly from source without packaging it and it works fine with the 2.6.32-5-xen-amd64 kernel. So I think it's a problem which only appears in the packages with the Debian patches. Does someone have an idea how to solve this issue? Best Regards --=_9426c50732c409617e0267e2dc8a7504 Content-Transfer-Encoding: base64 Content-Type: application/octet-stream; name=xen-dom0.png Content-Disposition: attachment; filename=xen-dom0.png iVBORw0KGgoAAAANSUhEUgAAAtAAAAGQCAIAAAAIhcA6AAAAA3NCSVQICAjb4U/gAAAAF3RFWHRH ZW5lcmF0b3IgVmVyc2lvbgAwLjkuMSqKm2cAAAAwdEVYdERvbWFpbiBVVUlEADQ3MjBiYjcwLThj ZDgtZjhkMS1jYTZiLTlhMmFjOTRmZDczMnzf/TUAAAA3dEVYdEh5cGVydmlzb3IgVVJJAHFlbXUr c3NoOi8vbHVrYXNANS45LjE2LjIyOTo1MDAwMC9zeXN0ZW1SiP2zAAAAGnRFWHRHZW5lcmF0b3Ig QXBwAHZpcnQtbWFuYWdlcqvpgfMAAAAYdEVYdERvbWFpbiBOYW1lAGRlYmlhbi1kZXZlbP0O5PsA ACAASURBVHic7d3Rmqwor4Bhe565SC+xLnMf1D9sWkgIISDa33syawqBiICoVfZxAAAAAAAAPN3P 9z+fzyd9dJ7nTcE4w1By7Z9UlW9/yVgmpQKVpDLVmMvhW+Cl/JEyU4RSIc0NfJXGlvb9x5rBNSn4 w9ajlDCanS1wEF1yLWh5X0M59qvZ8sCe/sn/5zzP21cbKYbqSbcr1yZJR3/Dpo3LjGVSOaWWSXl4 9lybaDZdeKcNb4GVw2pe8OVJtNqj8g2kU6MyUsq6juHJwZ7FTYqw2VDSLlsq2nPAApJ/2psscbkO Ng4kJdcmSSFuv4L5fD5MarCLPdNXx1eX2SNoPEK7ey8LgRH/3h0AGr73pd8xxaR5uXqju3lvuffp jOPOc/Wu1UiB7giNSdLnC4KX5FV/j3XsI54jYs2hP2GUuqijuksLxLbD+PNKYKVd7nAkvotpJdcm ST5KaamucrpRkvS6pFxRK550yVu9G9y8S+y7nd515znf08teh9/KVgrU69I/XxP8IF8X7a3i8o9L UrU18v+NaqhUzozJgdUGHoQ7HFvLr7RCknx1rWFcEHRdMb/jSZB+dW63sjX0uhacJlN/HrxF0UW6 +ZSvOUL2ndUGnmi7BUf47LBJkptenTSF+W5l+3KFiL2mTN43I4801MrWSHU9es3X22L6cYkaX6w2 8FDbPVJB1e33Hh592sDLPKg38iQFSHZZcEjPsPNtyqGr5NokKcSDptdt+eb9TVZa4cFvsl9G1fG1 lRu/FvOsQ4k/7kkv/pJO5Equ/ZOqqjOI/dttZVJZZvl5NZePVFc14GokxuDL1LIuKZdxF0IKdERo SZK+pnBv8NVjV/2Kq70uS157Uc3g7bVUy/wel8He26xFKRMAAAAAAAAAAAAAAAAAAAAAAAAA3upJ P4t15No/qcrys9iyQCWpTDXmclB+FTlSoFJIcwNfpTPepLJmcE0K/uj8nW0ZRrOzBQ6iS64FLe9r KH4Wi7/j14u/zvO8fbWRYjC+zUbJtUnS0d+waeMyY5lUTqllUh6ePdcmmk0X3mnDW2DlsJoXfHkS rfaofAPpXKuMlLKuY3hysGdxkyJsNpS0y7rzt4g9AKbb5U2jl+tg4xyh5NokKcTtE8rn89ltFYKd xZ7pq+Ory+wRNB4h8Bds98fbcPHJ/pj706V5ufkqzOr+9j6dcbxbs3rXaqRAd4TGJOnzBcFL8qrP OX8OcHzN0XxN6uCzmHzxkbfAOwYy4LPLHY7EdzGt5NokyUcpLdVVTmFKkl6XlCtqxZMueau3l5Xb zpfslrqat7KlCMvb/iMF+iLU69I/XxP8IF8X7a3i8o9LUrU18v+NaqhUTmCbfzJRZQKzcYdja/mV VkiSr641jAuCrivmd0zH+tW53crW0OtacKF/Cn9oxp7dkUu6+ZSvOQb3vewM4TeQgEm2W3CEzw6b JLnp1UnTje9W9qQb4Bax15TJ+ybikYZa2Rqprkev+XpbTD8uN44vYAfbPVJB1e33Hh592sDLPKg3 MnaAZJcFh/QMO9+mHLpKrk2SQjBhjfPN+5ucLcKD32S/jKrjaysrvxbzrGMH5J704i/pRK7k2j+p qjqh2L/dViaVZZafV3P5SHVVA65GYgy+TC3rknIZdyGkQEeEliTpawr3Bl89dtWvuNrrsuS1F9UM 3l5LtczvcRnsvZaKfHECAAAAAAAAAAAAAAAAAAAAAAAAwHM96Wexjlz7J1VZfhZbFqgklanGXA7K ryJHClQKaW7gq3TGm1TWDK5JwR+dv7Mtw2h2tsBBdMm1oOV9DcXPYvF3/Hrx13met682UgzGl9so uTZJOvobNm1cZiyTyim1TMrDs+faRLPpwjtteAusHFbzgi9PotUelW8gnRqVkVLWdQxPDvYsblKE zYaSdtlS0Z4DFpDs8qbRy3WwcSApuTZJCnH7Fczn82FSg13smb46vrrMHkHjEQJ/wXZ/vA0Xn+yP uT9dmpebr8Ks7m/v0xnHnefqXauRAt0RGpOkzxcEL8mrPuf8ubLxNUfzNamDz2LyxUfeAu8YyIDP Lnc4Et/FtJJrkyQfpbRUVzmFKUl6XVKuqBVPuuSt3g1u3iX23U7vuvOc7+llr8NvZSsF6nXpn68J fpCvi/ZWcfnHJanaGvn/RjVUKiekzfPSuO+IZ+EOx9byK62QJF9daxgXBF1XzO+YkfWrc7uVraHX teBC/xT+0Iw9uyOXdPMpXyWM77ty4wrY2XYLjvDZYZMkN706aQrz3cqedAPcIvaaMnnfHeyRhlrZ GqmuR58Re1tMPy43ji9gB9s9UkHV7fceHn3awMs8qDcydoBklwWH9Aw736YcukquTZJCMGGN8837 m5wtwoPfZL+MquNrK3d9LWb292CAWE968Zc0upRc+ydVVWcu+7fbyqSyzPLzai4fqa5qwNVIjMGX qcrj7a6dujTLYIGOCC1J0tcU7g2+euyqX3G112XJay+qGby9lmqZ3+My2HstFTmCBAAAAAAAAAAA AAAAAAAAAAAAAIBHe9LPYh259k+qsvwstixQSSpTjbkclF9FjhSoFNLcwFfpjDeprBlck4I/On9n W4bR7GyBg+iSa0HL+xrKPfc6XhMA3OvXi7/O87x9tZFiML5FR8m1SdLR37Bp4zJjmVROqWVSHp49 1yaaTRfeacNbYOWwmhd8eRKt9qh8A+lcq4yUsq5jeHKwZ3GTImw2lLTLlursYQA72OVNo5fVunG0 KLk2SQpx+2XK5/Nh5oJd7Jm+Or66zB5B4xE6qjOGwcjFPrb74224+GR/zP3p0oTYfBVmdX97n844 3q1ZvWs1UqA7QmOS9PmC4CV51eecP1c2vubQnzBKXdRR3aUFQtqBlQQeapc7HInvYlrJtUmSj1Ja qqucwpQkvS4pV9SKJ02U1Vu+ym3nS3ZLXc1b2VKE5W3/kQJ9Eep16Z+vCX6Qr4v2VnH5xyWp2hr5 /0Y1VCpnWZtzSxJ74g7H1vIrrZAkX11rGBcEXVfM75h29atzu5Wtode14I7dKfyhGXt2Ry7p5lO+ 5njH3UrAYbsFR/jssEmSm16dNIX5bmVPugFuEXtNmbxvch9pqJWtkep69Jqvt8X047JsfL2v2+Md tnukgqrb7z08+rSBl3lQb2TsAMkuCw7pGXa+TTl0lVybJIVgwhrnm/c3OVuEB7/JfhlVx9dWdvha TBnG7G/JAL2e9OIvafwoufZPqqrOXPZvt5VJZZnl59VcPlJd1YCrkRiDL1PLuqRcxl0IKdARoSVJ +prCvcFXj131K672uix57UU1g7fXUi3ze1wGe6+lomrGTSZzAAAAAAAAAAAAAAAAAAAAAAAAAJjh ST+LdeTaP6nK8rPYskD7j+XsuRyUX0WOFKgU0tzAV+mMN6msGVyTgj86f2dbhtHsbIGD6JJrQcv7 Gso99yojizdwYE+/Xvx1nuftq40Ug/EtOkquTZKO/oZNG5cZy6RySi2T8vDsuTbRbLrwThveAiuH 1bzgy5NotUflG0jnWmWklHUdw5ODPYubFGGzoaRdtlTXmwTca5c3jV6W5MY5Qsm1SVKI269UPp8P sxjsYs/01fHVZfYIGo/QUV1vEnC77f54Gy4+2R9zf7o0LzdfhVnd394bxY53a1bvWo0U6I7QmCR9 viB4SV71OefPlY2vOZqvSR18FpMvPvIWCGkHZSW3501K4GuXOxyJ72JaybVJko9+KSOdgJUkvS4p V9SKJ82G1dvLym3nS3ZLXc1b2VKE5W3/kQJ9Eep16Z+vCX6Qr4v2VnH5xyWp2hr5/0Y1VCqHdQD+ OO5wbC2/0gpJ8tW1hnFB0HXF/I4pXr86t1vZGnpdC+7YncIfmrFnd+SSbj7la44F+w7sabsFR/js sEmSm16dNIX5bmVPugFuEXtNmbxvch9pqJWtkep69Jqvt8X043Lj+AJ2sN0jFVTdfu/h0acNvMyD eiNjB0h2WXBIz7Dzbcqhq+TaJCkEE9Y437y/ydkiPPhN9suoOr62ssPXYoD9PenFX9KJXMm1f1JV deayf7utTCrLLD+v5vKR6qoGXI3EGHyZWtYl5TLuQkiBjggtSdLXFO4Nvnrsql9xtddlyWsvqhm8 vZZqmd/jMth7LRWVGZUkAAAAAAAAAAAAAAAAAAAAAAAAAHiBJ/0s1per+WNaqSLlB6J6mV0/3FWq vpB+62/8RZzld4D2CBXKryJHClQKaW7gq3TGm1TWDK5JwR+dv7Mtw2h2tsCfxV5yLWh5X0ON/yyW H77iKX69+Os8z9tXGykG41t09FzKi48OdX+V2vUyq3obNm1cZiyTyim1TMr3155rE82mC++04S2w cljNC776PhV96EmnRilXta5jeHKwZ3GTImw2lLTLlor2HLCAZJc3jV6ug40DSc/VXG3oxXYlTR3z t1/BfD4fJjXYxZ7pq8O8y+wRNB4h8Bds98fbAvnmuzR3lBmVpHmXGp/sj7k/XdmA0p3n6v72Pp1x 3HnOs5TVhd/KHnzTqPL5guAledXnnD9XNr7maL4mdfBZTL74yFvgHQMZ8NluweF75O/IVZ21Hd/b mMpyr6UMyTdXKrmi9voy+V5ORflRqJ6ius5e5VdJLBnzhaN0V7+rQF+Eel3652uCHzR4Ou+qotxT pTVSHzs6+5viUuZIUZfSgGfZbsGxjDL5Xq4UjUmTgpRmFl+Sr641LLX3ngPeMS/rV+d2K1tDr2vB WucU/tCMPbsjl3TzqbrCdlNuXAE7227BsXJ20Mu5zFZK0lRKLcrZ13dxNukGuEXepIFz6PvuYI80 1MrWuNw1fKjeFtOPy43jC9jBLl8ahe72ew+PPm3gZR7UGxk7QLLLgqP6A5PyTvJl6FpyvQAT1jjf vL/J2SI8+E32y8j467MbzfvOuO6tMx7e6kkv/pJGl5SrHP/SbV57mVKSUpdeWlV15rpMauU3BJWk sszyc+Urh72U5i0DrkZiDL5MjfpdxqVZBgt0RGhJkr6mcG/w1WNXnpKVr2ZXNxgZRPoAL6O111It 83tcBnuvpSJHkAAAAAAAAAAAAAAAAAAAAAAAAADwaE/6WWwzo/4G6PHfUvqSlLrW8/3qNfzdiPu/ P6Dc5epvTQeriC0QAHb268Vf53nevtpIMdjfolPdMi+tLFCqS8nlS/q6t2EHbfiepdmU96AEem6X AACHXf6WyuWS1/5HB6TToZJRqct3DnjQmWOTUDcJAwCwzC4LDjfL7RD3c4RluaRCel8Zqb+DUrqH b3nrolJaNZcUvBSGcZeld2uWfG2o77LyufEVmUrk+z9mAoARu/wtleR7syG2wEN+j7JUV5krrWy6 cvnkqyjfk51qJFIjSAXmt3wut3/0XFLwShhpS8d+VRkLtO9yWfLlw7I0va4cqw0Ar/f4Oxy62LsU yiWyuy6dfjUcVUX+9Korfj2MzU+fI214Fo/8jKXpaz53PACwv+0WHIHTbnMeD5z9p54z9KVPSPnp tk1XyfY7DRua1NP+4HdsAcBiu0cqUR73vY176Tf8MRUtD+Av2GXBIT1lz7cZ+XpHntdSl16jvsII /xqKYrwupWXsda3c5XAr90sqkDUHgNd70ou/pFXIZTNl7pa+hKE/ia+m6t/nsNSlsLSDJRKlrey5 8g0suZo7q4dRfufUEmHVSIFdu3zZ3liX8jVbAACe4dG3HBRv3S8AeL1dHqlg3FtPxm/dLwD4U37u DgCRNnk0Fu6t+wUAAAAAAAAAAAAAQPIz7+l49YeFedK2D+OVyJ9Of+nI+/YXALCJf/I/VRVb9HPP Xs+N3I2fgQAAprrnb6n8wTP6Jmh5AMAtGgsO40stm2/DrCZV3zKpv+GxfI2jg15XM2NibA33i0GV GPQXdEqlNd+eufmjLgDAsyl/MeRyNrJsln9iz3L50PLvEc0ylZ3SI9E3U+o17lozsK7wemsHAMDH /0hFOj+9+ypZ3+tS+svv3wbpuhUUGB4AAPdyLjik2/ivp/w1Mqk10pqjmt29MrM/WwEA4HaVv6Xy xHPV5k8EzvNkHQAA+MuuCw7OiEaOr1zoa46uNVP+RRBjFnvJ9m+EuJMAAH/NT/WUkG7UX1KNvxxR ki5l6k8ELGGUeS30AvUI9SSlNboKbAavN1RXy5d5lRpDkgAA2Frv9XdXOQAAYJJ7XvzVpXmhzDU0 AACb+7k7ABP9WcC9pQEAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAEOPHstHn8/n+4zzPmcGsrksPQwpAStok8qMV/LF3hL7Svv/oLbPa Gqm0apl56u3N6LBPL7UbjDl8l8ve+8RWLcWOyhfzNdQmc++9/rFstLKNdjgel1OOMWmHyA81wk3E RpgP466Sqxun0r4um+WpvdVtYpNe2mUw5thdrh70J7bqxRM78y1oqBGmBQdeI50s36drvxyzxuUC 5blrDgDrhc+9n8/ncfPPv+UFon6HWfo85SoLka5By9ZXLjr1ILsibAZf3RElyR1GrGaE1Ru/evO6 27BZ2ow2tLftyuWCow19SalJpTv8vWNZoddlDL7rYdalXmOuwENs7L29EVqqO4TxVX7i6BvjozIV W456e2v4chkjLHOFN5Tx1FY9cL2D6Ll+LIf50p/KLY2F5BX31lXSD4A9QmPAzSRLUQse4/kiLOkH 3ZhkPPRde2Rfv/aWnH9YFlv2T8uOjLehPcm4pb0EneV8oxTYFYavrq4jZaTvTm+ExlrumqWNEYZ3 15AuOmMQWWo3dviRFniuf5U0Y8t2kbI06yonet13s89/3+5RJogFeuuqbj+1tynNu7KhesWeS47a OP+MfZMupB+O753SSs0IfbHpI91XbFddt8zRva2hW5lrpVv2a3ZPiG32wVG5LW3B0dTbCtK16STp mB21UFcewqhJ/BZbBbMDx9HcpB9K9AiNJTQ/OabNADu0oS6qVeflWul9+zWjY4+Pyg3Ff2n00uj3 ttd5nsvWN4Bk/364f4QzpAn9QbaaYDGVPiqf2HtjFhyXPU9tdONgyEPSZ1LlsPmSjFHNFl7X/gVO 5ZvoZ/fDcfYIx8vfM5fPjftlnGBpw/FcKwuUCn/TlcDPIX/dyZiUNrgUXR0MjrrSv8t/6PumRGgM viupnBGMdYXrilBvXl8bKkdZj7C5R9Xgu4qqFiiVWRbrqHGwDR1JyvfODtdY1neq+cUUY99oHmV9 v7rqyjfwPRoOidBSi5RLH1llLqVvSPvljtDX2WK7qLEuKam3ofTOpp8dArsNAGA7Ky/l342WhNHQ l0YB4KG4ZAQWM/0tFQAASu7HmgAAAAAAAAAAAABKL/kOR+8PuowFPvSRpBS88rQ1PKkZ3u0FbhKG r8B8g8ACHdy/LFXeHtFb4Mh+6b9FrJbpHl8PnU+AKC/58/SM5KY05ZUv2AhPCg+D/Spz9f4Q0RfG DLFVj+yXtA44/yNl6Q3j9jYHdhC24Fg5lhbUJU03U0XtVxn8ZWLNp7/wpLzS8pORAi/lvGa/ugq8 tICRr3ktwkdKV4Fd+6XntdTeXG0oYbDmAGLew1GdLpM0Dqt3Ly//W+bS66p+0hWGEkn1tF2N0Jck FZ7iqUaiFygF/xpM2WX3CC/8UpH0idI/q71XL1wq8DAPotlYNAAjAu5wSMuIrpucxlzNGbC3wCrl Vmq1QF+Ssl9pS0eB+lxcXkzPS1IuFn0FHurhfu5+dRUotYCRr3kl1S3zbnnpovmeVve6d+jl24Sv AxxNPSMM4DVG73CUY/L874/qfj80DldLLvtq47LBDNISp9zMsV8jYbzY4Ln2TS63CkLaJLx5H32k 6GxAuKEFhzQm01m2mirRc/nG/8r5Qqprxn65KRWFJ8WGoTfUc/ert8CuBbc9jHn9cE3fjq3F3Ros UACF/5FK8wSgPEGQSLliZ0PpIUVI4VKNC/ZrN4G3l7dqqPDb5rffh1euHI61IwXAizkXHMrUk8+e 9jWHkitkmrvM6akKd+HGp/WL90uiVB2eFB6GUvij98tXoEXZK3zNm28zY7UxvtIaaSjHFdFIGCzX AOeLvz7qY+PqZFdNylOlXMa6zv++Fd8s8JJX/zaGEvxgUlQbVue125MUvQXqDeWO8Pb9GinQUp0x S7N5HQUqYV+2MTaUu883dS0OlOlLD4PVBnCz8eubF6NxAABvctubRlnyAwDwdyz9WyrNZxz4GrlF DAAAAAAAAAAAAAAAnsj0HQ7pN2xugT+Km/d7udnCW9Ve42Frw+rPZIy/A3wxy+9Iq7m+/5C66O0N 6NuvGWF8/xE720gvDVp2ONzdZs1BmffLbccvunvDwFOYfqUSfuD1As/zLM9q53+OrFMqSdWitnJX YPbmzbfPN5CK+gvcv1WWGmqTBtznN9i3rL9n1+5r3mUHJZ8E7PXquaRClFy+MPAgt/0sNsTgCY93 XQCv9weXxV0u9yGMJ3s9V3O1UebyhYFn+Tc/zMpL90r6ffjqNbRe4Ob0/Wq2RvNWrfE1qfYCN6R0 Nn2/HJ3NV2CzLr3eaoFlapPUOMZcjjZs1ms/Xu6WL1Ob7LONFIP+wEVKkjZOHN3GGKE+Y8e+eqDZ vBKWC6hq3OHQH8Ip9+F7C1Sk8tMNiXKSkpKaJYecrZXWKOeFakNJc4q7QDt7806dPlIY5S4bW+P4 3Sy+AvW6Ustceo4+HBw900fpG7798tXla/ljTkNVS7Ps8ue/L09Yur27eaWm8B0U97ScslfXK9Xx peTy1TVYIB5B+/P0zfE/fjniyPXtjnkhStI+ms1YbqA3b9RuKs1bnVnual6pNc7zzGcoe3iW3tu1 s5al5BpSdTPmcceu7dNQiq5IUiesDhxF7BFxh2EpM/3veJn4s7QFR9Pf7HwjM2PvLBZb4KMpe3oW f7dvsECf3Y5FGc+8CO9t+WOD9Up+Yu69IXHErTwcYeR5lTKlDcJnwt3GEQLFf2nUchduE5vcu4ud cf6gS2cDbuF7kLF/GIwvRIlZcFzO3Km7z15trF8xTBp7+gRx18JokwXZxSWq/Ln14TouvsfJj34I vUnwUXUNjsrxMMqHDrHNa8xlDyOnXyJK48t3YanketCVKtx+jt99qNrb9KS0waXoao9RCryUKX1u T1IK9ClvgTZbQwmgOnRHCjTGX+Zd2bzNHuVojTLg6mwbsstHceDsBY70+WokUmB62M0NLMFb6uo6 lEpdOqUuY5zV8KQC9TC66joMu9ybqxmGJX7j+JJylWEoqVNnbABYZP87DUav2REAf9mzX/wFvB73 lgG8g+lvqQCP8+h7s+4b4wAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAKLP5/P5fO6OAkDDv5aN0mA+zzOkVqnAfNbIky6ziTFJKXAH4a1q r/GwtWF1Epcy2vfCvePfjGWuwQIdGR3lhAfvCyO2ZL1GaZf3MWlm23mXFc0uWqaGJzXDu73ATcLw FZhvEFig3T+WjcLHj17geZ7lWe38z5Htv5JULWordwVmb958+3wDqSiLvK9HXZW6WzLqEIyUE9gN 5vUoqeRtB5fR0+NfIJ8fjt9jNjwpPAz2q8zVO+v6wpCYFhzbGlxPcCf2Ro4Dt/PysenRwfus2WX7 5dqCwX7LUQ5cuF+Cv7RtfsoJT8orLT8ZKfBSzmv2q6vASwsY+ZpX8W95xVntc83SU66ykMsnDz3H 6/vVbI3mzVu9lRwF7k/paeVOOfZXasNqqrE0pWM3Pyw/b1aX9B5lKdqytGaP8g3Yaml6XfmH9mWE sWXsl3rjM5vegNJBsSdJhRubVw/yufOJ7qHnnUBl9wgv/FJR+UnjDoc07PPbLL4bPpaNv1L5aUFX DhUpqVlyyOhSWqNcyVUbqjpzjRRoZ2/e8W56ucIoI1G6k/uMWy3T0VuMleoLUHs5h2t8KWFIpaVP YhuqmkWpK9/l8KNjXCweYy1fDVgp0Jek7JexeR1dVBn+4UnKtOwr8FAP93P3q6vAwTHla96S9qXR Zim9ZyDfPpcn4zSffilJ+2g2ozT3OQrsojRvdeUxUq9+Lhlf0BjLnLTaCC/T3SBRzTuvoVayrzYu G8xgHObfkSKNxDyj7+g8/Zh2eUc3DnG5lghpk67mNf1KRfI3D+GycW7Z+DWHIG/VwOl+Rvssm78m XeLPO5tuyHewVg4rqa605qhus/gkqlQUnhQbht5Qz92v3gK7Ftz2MHqLiv/SqHQrL7yicfptomX+ 4GkAWCB28lk/s0mPP3aeVMcFTstbNVT46eb285fUvMpIiVlwXPY81Tf7eK9v8UsjRtHXHHd1rNs7 dKCofZnUAZqVvuZALBMy+YTPbMqhzJPyf89Y6Bh7lFJ1eFJ4GErhj94vX4EWZa/wNW++zWWzn7y4 8hG7JSmv4BJ9+blS4KVM6XN7klKgj9LcUhhKANUJZaRAY/xl3mXNq2/v6xtKkmW/qnXp8ZfHSz+U 4cHr4UlhNMdyb66R/erq8z4f9RF1+Mx2RI8vZQaw7FdXXUrwi5MUvQXqDeWO8Pb9GinQUp0xS7N5 lQIBYBfG62+UaDrs7Nkv/gLwDpwpgdf7uTsAADiO6AegfxANCAAAAAAAAOCLR7wAADzX/79p1PcL FuW3MY4CeQYJAMArDf1KJfaWQ1qgXN5tAAAA/rTAxxxlUfknPE8BAODR/vdI5fKOwvzD9Ca+4/db xsrN8nKrBR7FfQvjcxMerwAA8Gj/e6TSfOF8+QrnlCX/9yXvRf7QRHpuws0MAADex/QdDm4wAACA Ef+2N/nPmmUHixsAAN6Hv6UCAACmi1lwjH/x4vKVDv6sLQAAb/K/P94m/cH78sMLy69Ryl++SMXy 4i8AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA0M+XXQAACb9J REFUAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAACD6+f7n8/mkj87zHCw0L00q8LvNJckdRrU0S4F6 xvzzy05dytR32bdf1VyXwPL/HYnQ7fP5hBSVwosKbJNKZ1QhHUq9A1yyW+JpBh+4d4NFObLf0uVu Vw7YG4eeMk/qqU88ZH+zv138k//PeZ5RE8f5n6M2D1ZnxjyjtI1So6NAPWNVvl/Viqp1+Ro2ZdEX UtXteyP0CSnk65ZBuKDS8CqMna25RLBoBh+4d4NF9WZvrtRfybgkvSUMvWO7zw77+MvrjOSf9iad midXvbelQqQtLaVZCuxdbYSsxgI1G8cxBT9xGL9beVCUfugben/cVoP6L3BMsO6zA3bz79TSpQcT 53lGdRdf51PCeFBvVoL83jidN5lWLz6qqV13TZUy9TDyo5Zy2e/QlvWW9z+VJMt+Oe4hN9kfjhxj Q6+rokPdL18HcBxKO+NB0TuAxNdFBzubEkYZQ7mZZSz7WuP43Q56tOPTl68fOpKarWG8vn398jf+ DkeirDb0XLEn+7LA8d4srbiX3SSYcSHbtUDJNy4zWu6LKvOO4wDlLf/9h/EObblfx+/lmnLCuNSo 75evNeyXfXrqYJ/vWoUr++XrAL5D2YywWrtSl9IBjJXau+hgZyvpAzaVXBYoVaSMlEH6eshei68f +pL01pD2yHcoH23WHY7mIjr92z0JDnKHUd21/H+XrTmkipSkNfTAUmsr3aOrV6T9Ne54yNnXlzHf /TyYXl2rjWpdvUOvGvygrg4QtTY9fneYrowpuyNLVxdt1jVjgDen6wXGrwaT5mxjXKgNhqHskWU+ fJkpCw798tG+TQhfGJLA8TBOX3MsDibRLwHTGDu2aUafqOAd5ThWGyN9fhO7BbwyngXzZJX7ds54 dVW+leWyc43Da+ZDo/hHKn+n7V6m63blCP3+4R+5tWhUHpTXjy86wN80qWPv/7Ri/wgDTfwOx5fx NCY9LXMUZS9whtefD6qMhybfjDXHhW/Bt2yZOIMUvN4BHr3L4d7abZS5wjjHGmebQ22NqQ1liXD/ I9Ul/sVfygxS3UZ6nq18xUavrrfAS6qlQGNRxlSJEl71f+0xdIVhDLLa7OXDcimM6sCzzCmXWpSb wFERVgOz1NWVJGmOL73peruiHqFlIBuT9A7gO5SWnbIfypFR3NtF543lcsAaW14aKV0Dtgz+EJri EuThav/wUdlM8rWhsl/2hgXwPC+7pACATUx/pAIAAPBzdwDARgKfLQIAAAAAAAAAgAXyry7yNUYA qGKqfJD/vWk09tG15Vdbzd+4On7r5fg9qv4jpWrGsq4ZP+iKVf3xamCx4SVDMulQ+vQGs1Xwx3F8 gt7UPrhfShib/CoyqqF2oxy4qJZv9o3Fg6I8lJYAolrj169U0ivPRqTIlBeoVc/QeUZpG6VGR4FS xvM3S5bj9y5Xk9SdmGtG7b7jxSXIoK3m/d5gtgo+sB+O7Nf+w2H/CN0WdMhmFSsHheWKeqr4n8U2 T676aiMVIm1pKc1SoGMU6QuU3tJ0lwK3mqmPgePVu5pUar/dyjA22WWfRwd/r9uvVfY3aaqk5XNR rTHrr8V+SU8fzrg/Z+o7gfnCCDlZ9lZ3FEPI9yK8yza9uQKdY393tFw15sfx8nSsmnQMt2G5mZRL eTmju64yqVngjIYyMl4SNF/U2IzwdL1pVB8O9qGn7JovjOP3rkkf2nuUpYsqpXXdVPeNL/eolKbK riCrSb651zjxdoU3OCqNh9LeD31hTHzxl7La0HPFntHLApthfDKO6vTCB+UPMi4LICUpz+7Ipcfj aCX30k26s1IGX06gll02toZ0RuxqQ19dvjCU1lDacLBvKMGX/VBhjNA+9FI5l3/nn5ThjR+vrjCa heRD7/uP8Y7dG6EUmCOM8OCNQVZT9eFWDaMZXlfktxxKaVQ6WkMy6w5Hc5ZM/zZ24nDVMC7BfIe0 PcLZq41LRbpqGHe1dunsv8/ha96RXdZHWr5Zvi/GGi257KuNy+dKpZbY7AU2M27eD0vS/g4er1hn 8cdZLjHcqNlQvdOXb3wp3DOJEoZxp7omPWnhEtsaecldGzvCmLLgkA5n/ollmxC+MByWzTXLarFw R9LbXIPNG9ViSr9NV5z2uvRc8xZYvTNLVwBfK4dDoDzscrr3HeXFdghMbyhHhJu0vBSG3m1GqusK YzFHGPGPVG5vBexv8WojSvM2rGPGkXI1dzl8dgu0yfGaQT/KOx+UxXzDYWWBhLE+jOl/vC2tgHSX oKsTlrEoe4HuaPehBDx1X3zN69jYsX2gvA2VMPLN7MNPyWXcZb2u8A5gLPBxqw37flmOsvs0cNfx Ci/QPhyM05dvfIW7MYzw1hjvG74wflLm9NHgTKEMwuo25Y0pKQxpFaLUZSnwknopUCpNSpVOSEoY vewRljuV9wzLLtsjmbTaOFpf9GnucrU6Xxs6wiiTpCCNdfkOpX1kdfUNaQQNBn8W3wB1R6i7xGMM o6xL3y9fGIfcvJfYysYpcxmTyl3WI2zukS+MriQffZctZygpyd5txuuqFqgrD2Wz9zoiBN5pfKm+ 0rOifRbaFtjc3PdwAEgcd3egM95WzC1u/03CCPfW/cJUP3cHAPjFPquagbuOs+3fBwAAAAAAAAAA AAAAAAAAAAAAAAAAUX7c76AcT1JeZhf4MkEAAHC7H+X9Lb1vF24m5dwl8PYkAAAe539vGi3fzJ9I fxvl+yLh74k/P/0rSVJpFry0GACA52q/2ly6l5AWFuU2UpLyR4bcYQAAgP0N/Xn68zyl1YOSBAAA /pqOBUf+xxjzf18WFkpSiOrfhOQPRQIAsLOfy1c3Lt8Vnfcrla6fojR/pcI3SQEAQB9uVwAA8DJD 3+EIxCIDAIAX+7k7gP+nvBMMAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAADz+D2AdaNOyuipZAAAAAElF TkSuQmCC --=_9426c50732c409617e0267e2dc8a7504 Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users --=_9426c50732c409617e0267e2dc8a7504-- From xen-users-bounces@lists.xen.org Fri Sep 21 13:09:20 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Fri, 21 Sep 2012 13:09:20 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TF2xr-0005YA-Qz; Fri, 21 Sep 2012 13:08:15 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TEzqL-0000Y3-5B for xen-users@lists.xen.org; Fri, 21 Sep 2012 09:48:17 +0000 Received: from [85.158.139.211:43273] by server-12.bemta-5.messagelabs.com id 24/24-22670-0E73C505; Fri, 21 Sep 2012 09:48:16 +0000 X-Env-Sender: richard.warburton@gmail.com X-Msg-Ref: server-9.tower-206.messagelabs.com!1348220894!17924130!1 X-Originating-IP: [209.85.212.45] X-SpamReason: No, hits=0.8 required=7.0 tests=BODY_RANDOM_LONG, ML_RADAR_SPEW_LINKS_14,RCVD_BY_IP,spamassassin: X-StarScan-Received: X-StarScan-Version: 6.6.1.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 21278 invoked from network); 21 Sep 2012 09:48:15 -0000 Received: from mail-vb0-f45.google.com (HELO mail-vb0-f45.google.com) (209.85.212.45) by server-9.tower-206.messagelabs.com with RC4-SHA encrypted SMTP; 21 Sep 2012 09:48:15 -0000 Received: by vbip1 with SMTP id p1so4353853vbi.32 for ; Fri, 21 Sep 2012 02:48:14 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:date:message-id:subject:from:to:content-type; bh=HENc9M5bqcHQS7SwMmES0++WE4pP3MpmiPBDgwOt34Q=; b=FLH2YW+3wKZTk+icqTuw77rIgVW4Svt3mMo4UNGjeDIH0jxwOU5pFwIrHBV0DZSLlu C9vu0Su+7v835Evlv16k5k7hnIG+sEDaGEW8+gPXPIYw4/eKwNdm2tPljOCzCVlcBuwv qjGNJJgL2HY02wQDbmZC0G8jHPXx+9SLyG9RWai44rvY3+Cv0f5jnrtwEtlnma1/Jntr VPY0EUfJ2BxEEp66zyfiozdfmzhtDMrcjvZV4QLHVVx7NuxXr/scYqImlPLcRqWwHyZi y9DABdGLXhIPlXXbEH+5RHlMvttyLy+QKI/tVlHSlwUkMoy5rkssR/gGvRE5flhFPINV PRfw== MIME-Version: 1.0 Received: by 10.220.228.131 with SMTP id je3mr2637597vcb.73.1348220894302; Fri, 21 Sep 2012 02:48:14 -0700 (PDT) Received: by 10.220.212.139 with HTTP; Fri, 21 Sep 2012 02:48:14 -0700 (PDT) Date: Fri, 21 Sep 2012 10:48:14 +0100 Message-ID: From: Richard Warburton To: xen-users@lists.xen.org X-Mailman-Approved-At: Fri, 21 Sep 2012 13:08:13 +0000 Subject: [Xen-users] CPU Usage statistics Issue X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org Hey, I'm currently trying to measure the CPU Usage of a process that's running on a Linode VM, which is virtualised using Xen. It appears to exhibit very weird CPU Usage statistics and I was wondering if anyone could explain how/why this is happening. I am running a series of processes, each of which entirely pegs a core. Pegging 1 Core = 14% of CPU Pegging 2 Cores = 28% of CPU Pegging 3 Cores = 60% of CPU Pegging 4 Cores = 100% of CPU Those are the CPU stats as listed in both vmstat and top - so I'm presuming that they're coming from /proc/stat. I'm not seeing any 'steal' time at all, so I presume that I have access to all the CPU cores nominally available, I have appended the contents of /proc/cpuinfo to the bottom of the page. The weird thing is that if you look at the processes' individual CPU Usage measurement then it is listed as 100% (ie a whole core). I would consequently expected vmstat to be listing 25%, 50%, 75%, 100% on a 4 core box. Thanks for any help explaining what is going on here. regards, Richard processor : 0 vendor_id : GenuineIntel cpu family : 6 model : 26 model name : Intel(R) Xeon(R) CPU L5520 @ 2.27GHz stepping : 5 cpu MHz : 2266.746 cache size : 8192 KB fdiv_bug : no hlt_bug : no f00f_bug : no coma_bug : no fpu : yes fpu_exception : yes cpuid level : 11 wp : yes flags : fpu de tsc msr pae cx8 cmov pat clflush mmx fxsr sse sse2 ss ht nx constant_tsc nonstop_tsc pni ssse3 sse4_1 sse4_2 popcnt hypervisor bogomips : 4533.49 clflush size : 64 cache_alignment : 64 address sizes : 40 bits physical, 48 bits virtual power management: processor : 1 vendor_id : GenuineIntel cpu family : 6 model : 26 model name : Intel(R) Xeon(R) CPU L5520 @ 2.27GHz stepping : 5 cpu MHz : 2266.746 cache size : 8192 KB fdiv_bug : no hlt_bug : no f00f_bug : no coma_bug : no fpu : yes fpu_exception : yes cpuid level : 11 wp : yes flags : fpu de tsc msr pae cx8 cmov pat clflush mmx fxsr sse sse2 ss ht nx constant_tsc nonstop_tsc pni ssse3 sse4_1 sse4_2 popcnt hypervisor bogomips : 4533.49 clflush size : 64 cache_alignment : 64 address sizes : 40 bits physical, 48 bits virtual power management: processor : 2 vendor_id : GenuineIntel cpu family : 6 model : 26 model name : Intel(R) Xeon(R) CPU L5520 @ 2.27GHz stepping : 5 cpu MHz : 2266.746 cache size : 8192 KB fdiv_bug : no hlt_bug : no f00f_bug : no coma_bug : no fpu : yes fpu_exception : yes cpuid level : 11 wp : yes flags : fpu de tsc msr pae cx8 cmov pat clflush mmx fxsr sse sse2 ss ht nx constant_tsc nonstop_tsc pni ssse3 sse4_1 sse4_2 popcnt hypervisor bogomips : 4533.49 clflush size : 64 cache_alignment : 64 address sizes : 40 bits physical, 48 bits virtual power management: processor : 3 vendor_id : GenuineIntel cpu family : 6 model : 26 model name : Intel(R) Xeon(R) CPU L5520 @ 2.27GHz stepping : 5 cpu MHz : 2266.746 cache size : 8192 KB fdiv_bug : no hlt_bug : no f00f_bug : no coma_bug : no fpu : yes fpu_exception : yes cpuid level : 11 wp : yes flags : fpu de tsc msr pae cx8 cmov pat clflush mmx fxsr sse sse2 ss ht nx constant_tsc nonstop_tsc pni ssse3 sse4_1 sse4_2 popcnt hypervisor bogomips : 4533.49 clflush size : 64 cache_alignment : 64 address sizes : 40 bits physical, 48 bits virtual power management: _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Fri Sep 21 13:09:20 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Fri, 21 Sep 2012 13:09:20 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TF2xr-0005YA-Qz; Fri, 21 Sep 2012 13:08:15 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TEzqL-0000Y3-5B for xen-users@lists.xen.org; Fri, 21 Sep 2012 09:48:17 +0000 Received: from [85.158.139.211:43273] by server-12.bemta-5.messagelabs.com id 24/24-22670-0E73C505; Fri, 21 Sep 2012 09:48:16 +0000 X-Env-Sender: richard.warburton@gmail.com X-Msg-Ref: server-9.tower-206.messagelabs.com!1348220894!17924130!1 X-Originating-IP: [209.85.212.45] X-SpamReason: No, hits=0.8 required=7.0 tests=BODY_RANDOM_LONG, ML_RADAR_SPEW_LINKS_14,RCVD_BY_IP,spamassassin: X-StarScan-Received: X-StarScan-Version: 6.6.1.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 21278 invoked from network); 21 Sep 2012 09:48:15 -0000 Received: from mail-vb0-f45.google.com (HELO mail-vb0-f45.google.com) (209.85.212.45) by server-9.tower-206.messagelabs.com with RC4-SHA encrypted SMTP; 21 Sep 2012 09:48:15 -0000 Received: by vbip1 with SMTP id p1so4353853vbi.32 for ; Fri, 21 Sep 2012 02:48:14 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:date:message-id:subject:from:to:content-type; bh=HENc9M5bqcHQS7SwMmES0++WE4pP3MpmiPBDgwOt34Q=; b=FLH2YW+3wKZTk+icqTuw77rIgVW4Svt3mMo4UNGjeDIH0jxwOU5pFwIrHBV0DZSLlu C9vu0Su+7v835Evlv16k5k7hnIG+sEDaGEW8+gPXPIYw4/eKwNdm2tPljOCzCVlcBuwv qjGNJJgL2HY02wQDbmZC0G8jHPXx+9SLyG9RWai44rvY3+Cv0f5jnrtwEtlnma1/Jntr VPY0EUfJ2BxEEp66zyfiozdfmzhtDMrcjvZV4QLHVVx7NuxXr/scYqImlPLcRqWwHyZi y9DABdGLXhIPlXXbEH+5RHlMvttyLy+QKI/tVlHSlwUkMoy5rkssR/gGvRE5flhFPINV PRfw== MIME-Version: 1.0 Received: by 10.220.228.131 with SMTP id je3mr2637597vcb.73.1348220894302; Fri, 21 Sep 2012 02:48:14 -0700 (PDT) Received: by 10.220.212.139 with HTTP; Fri, 21 Sep 2012 02:48:14 -0700 (PDT) Date: Fri, 21 Sep 2012 10:48:14 +0100 Message-ID: From: Richard Warburton To: xen-users@lists.xen.org X-Mailman-Approved-At: Fri, 21 Sep 2012 13:08:13 +0000 Subject: [Xen-users] CPU Usage statistics Issue X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org Hey, I'm currently trying to measure the CPU Usage of a process that's running on a Linode VM, which is virtualised using Xen. It appears to exhibit very weird CPU Usage statistics and I was wondering if anyone could explain how/why this is happening. I am running a series of processes, each of which entirely pegs a core. Pegging 1 Core = 14% of CPU Pegging 2 Cores = 28% of CPU Pegging 3 Cores = 60% of CPU Pegging 4 Cores = 100% of CPU Those are the CPU stats as listed in both vmstat and top - so I'm presuming that they're coming from /proc/stat. I'm not seeing any 'steal' time at all, so I presume that I have access to all the CPU cores nominally available, I have appended the contents of /proc/cpuinfo to the bottom of the page. The weird thing is that if you look at the processes' individual CPU Usage measurement then it is listed as 100% (ie a whole core). I would consequently expected vmstat to be listing 25%, 50%, 75%, 100% on a 4 core box. Thanks for any help explaining what is going on here. regards, Richard processor : 0 vendor_id : GenuineIntel cpu family : 6 model : 26 model name : Intel(R) Xeon(R) CPU L5520 @ 2.27GHz stepping : 5 cpu MHz : 2266.746 cache size : 8192 KB fdiv_bug : no hlt_bug : no f00f_bug : no coma_bug : no fpu : yes fpu_exception : yes cpuid level : 11 wp : yes flags : fpu de tsc msr pae cx8 cmov pat clflush mmx fxsr sse sse2 ss ht nx constant_tsc nonstop_tsc pni ssse3 sse4_1 sse4_2 popcnt hypervisor bogomips : 4533.49 clflush size : 64 cache_alignment : 64 address sizes : 40 bits physical, 48 bits virtual power management: processor : 1 vendor_id : GenuineIntel cpu family : 6 model : 26 model name : Intel(R) Xeon(R) CPU L5520 @ 2.27GHz stepping : 5 cpu MHz : 2266.746 cache size : 8192 KB fdiv_bug : no hlt_bug : no f00f_bug : no coma_bug : no fpu : yes fpu_exception : yes cpuid level : 11 wp : yes flags : fpu de tsc msr pae cx8 cmov pat clflush mmx fxsr sse sse2 ss ht nx constant_tsc nonstop_tsc pni ssse3 sse4_1 sse4_2 popcnt hypervisor bogomips : 4533.49 clflush size : 64 cache_alignment : 64 address sizes : 40 bits physical, 48 bits virtual power management: processor : 2 vendor_id : GenuineIntel cpu family : 6 model : 26 model name : Intel(R) Xeon(R) CPU L5520 @ 2.27GHz stepping : 5 cpu MHz : 2266.746 cache size : 8192 KB fdiv_bug : no hlt_bug : no f00f_bug : no coma_bug : no fpu : yes fpu_exception : yes cpuid level : 11 wp : yes flags : fpu de tsc msr pae cx8 cmov pat clflush mmx fxsr sse sse2 ss ht nx constant_tsc nonstop_tsc pni ssse3 sse4_1 sse4_2 popcnt hypervisor bogomips : 4533.49 clflush size : 64 cache_alignment : 64 address sizes : 40 bits physical, 48 bits virtual power management: processor : 3 vendor_id : GenuineIntel cpu family : 6 model : 26 model name : Intel(R) Xeon(R) CPU L5520 @ 2.27GHz stepping : 5 cpu MHz : 2266.746 cache size : 8192 KB fdiv_bug : no hlt_bug : no f00f_bug : no coma_bug : no fpu : yes fpu_exception : yes cpuid level : 11 wp : yes flags : fpu de tsc msr pae cx8 cmov pat clflush mmx fxsr sse sse2 ss ht nx constant_tsc nonstop_tsc pni ssse3 sse4_1 sse4_2 popcnt hypervisor bogomips : 4533.49 clflush size : 64 cache_alignment : 64 address sizes : 40 bits physical, 48 bits virtual power management: _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Fri Sep 21 13:09:23 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Fri, 21 Sep 2012 13:09:23 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TF2xs-0005YJ-Ex; Fri, 21 Sep 2012 13:08:16 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TF068-0000e5-AE for xen-users@lists.xen.org; Fri, 21 Sep 2012 10:04:36 +0000 Received: from [85.158.139.83:43498] by server-15.bemta-5.messagelabs.com id 5F/9B-23541-3BB3C505; Fri, 21 Sep 2012 10:04:35 +0000 X-Env-Sender: lukas@laukamp.me X-Msg-Ref: server-15.tower-182.messagelabs.com!1348221873!29324373!1 X-Originating-IP: [5.9.218.245] X-SpamReason: No, hits=0.7 required=7.0 tests=BODY_RANDOM_LONG, RCVD_ILLEGAL_IP X-StarScan-Received: X-StarScan-Version: 6.6.1.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 28869 invoked from network); 21 Sep 2012 10:04:33 -0000 Received: from mailer0.lippux.de (HELO mailer0.lippux.de) (5.9.218.245) by server-15.tower-182.messagelabs.com with SMTP; 21 Sep 2012 10:04:33 -0000 Received: from localhost (localhost [127.0.0.1]) by mailer0.lippux.de (Postfix) with ESMTP id B6CD44225B1 for ; Fri, 21 Sep 2012 12:04:33 +0200 (CEST) X-Virus-Scanned: Debian amavisd-new at mailer0.lippux.de Received: from mailer0.lippux.de ([127.0.0.1]) by localhost (mailer0.lippux.de [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id SSwaBt8Cd7a5 for ; Fri, 21 Sep 2012 12:04:33 +0200 (CEST) Received: from [127.0.0.1] (unknown [5.9.218.242]) (Authenticated sender: lukas@laukamp.me) by mailer0.lippux.de (Postfix) with ESMTPSA id 223B242259B for ; Fri, 21 Sep 2012 12:04:32 +0200 (CEST) Message-ID: <505C3BA7.5010105@laukamp.me> Date: Fri, 21 Sep 2012 12:04:23 +0200 From: Lukas Laukamp User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:15.0) Gecko/20120907 Thunderbird/15.0.1 MIME-Version: 1.0 To: xen-users@lists.xen.org Content-Type: multipart/mixed; boundary="------------050000060501030900090607" X-Mailman-Approved-At: Fri, 21 Sep 2012 13:08:13 +0000 Subject: [Xen-users] Xen 4.2 (backported packages) can't load Dom0 (Kernel 2.6.32-5-xen-amd64) X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org This is a multi-part message in MIME format. --------------050000060501030900090607 Content-Type: text/plain; charset=ISO-8859-15; format=flowed Content-Transfer-Encoding: 7bit Hey all, I have a problem with Xen 4.2 on Debian Squeeze with Kernel 2.6.32-5-xen-amd64. I rebuilded the source packages from Debian experimental trunk on Squeeze and installed them. Also I installed the Kernel 2.6.32-5-xen-amd64 from the Debian Squeeze trunk. Now it looks like that Xen can't load the Dom0. After registering netback strange modprobe errors appear. In the attachment is a screenshot of the errors. I also build Xen directly from source without packaging it and it works fine with the 2.6.32-5-xen-amd64 kernel. So I think it's a problem which only appears in the packages with the Debian patches. Does someone have an idea how to solve this issue? Best Regards --------------050000060501030900090607 Content-Type: image/png; name="xen-dom0.png" Content-Transfer-Encoding: base64 Content-Disposition: attachment; filename="xen-dom0.png" iVBORw0KGgoAAAANSUhEUgAAAtAAAAGQCAIAAAAIhcA6AAAAA3NCSVQICAjb4U/gAAAAF3RF WHRHZW5lcmF0b3IgVmVyc2lvbgAwLjkuMSqKm2cAAAAwdEVYdERvbWFpbiBVVUlEADQ3MjBi YjcwLThjZDgtZjhkMS1jYTZiLTlhMmFjOTRmZDczMnzf/TUAAAA3dEVYdEh5cGVydmlzb3Ig VVJJAHFlbXUrc3NoOi8vbHVrYXNANS45LjE2LjIyOTo1MDAwMC9zeXN0ZW1SiP2zAAAAGnRF WHRHZW5lcmF0b3IgQXBwAHZpcnQtbWFuYWdlcqvpgfMAAAAYdEVYdERvbWFpbiBOYW1lAGRl Ymlhbi1kZXZlbP0O5PsAACAASURBVHic7d3Rmqwor4Bhe565SC+xLnMf1D9sWkgIISDa33sy awqBiICoVfZxAAAAAAAAPN3P9z+fzyd9dJ7nTcE4w1By7Z9UlW9/yVgmpQKVpDLVmMvhW+Cl /JEyU4RSIc0NfJXGlvb9x5rBNSn4w9ajlDCanS1wEF1yLWh5X0M59qvZ8sCe/sn/5zzP21cb KYbqSbcr1yZJR3/Dpo3LjGVSOaWWSXl49lybaDZdeKcNb4GVw2pe8OVJtNqj8g2kU6MyUsq6 juHJwZ7FTYqw2VDSLlsq2nPAApJ/2psscbkONg4kJdcmSSFuv4L5fD5MarCLPdNXx1eX2SNo PEK7ey8LgRH/3h0AGr73pd8xxaR5uXqju3lvuffpjOPOc/Wu1UiB7giNSdLnC4KX5FV/j3Xs I54jYs2hP2GUuqijuksLxLbD+PNKYKVd7nAkvotpJdcmST5KaamucrpRkvS6pFxRK550yVu9 G9y8S+y7nd515znf08teh9/KVgrU69I/XxP8IF8X7a3i8o9LUrU18v+NaqhUzozJgdUGHoQ7 HFvLr7RCknx1rWFcEHRdMb/jSZB+dW63sjX0uhacJlN/HrxF0UW6+ZSvOUL2ndUGnmi7BUf4 7LBJkptenTSF+W5l+3KFiL2mTN43I4801MrWSHU9es3X22L6cYkaX6w28FDbPVJB1e33Hh59 2sDLPKg38iQFSHZZcEjPsPNtyqGr5NokKcSDptdt+eb9TVZa4cFvsl9G1fG1lRu/FvOsQ4k/ 7kkv/pJO5Equ/ZOqqjOI/dttZVJZZvl5NZePVFc14GokxuDL1LIuKZdxF0IKdERoSZK+pnBv 8NVjV/2Kq70uS157Uc3g7bVUy/wel8He26xFKRMAAAAAAAAAAAAAAAAAAAAAAAAA3upJP4t1 5No/qcrys9iyQCWpTDXmclB+FTlSoFJIcwNfpTPepLJmcE0K/uj8nW0ZRrOzBQ6iS64FLe9r KH4Wi7/j14u/zvO8fbWRYjC+zUbJtUnS0d+waeMyY5lUTqllUh6ePdcmmk0X3mnDW2DlsJoX fHkSrfaofAPpXKuMlLKuY3hysGdxkyJsNpS0y7rzt4g9AKbb5U2jl+tg4xyh5NokKcTtE8rn 89ltFYKdxZ7pq+Ory+wRNB4h8Bds98fbcPHJ/pj706V5ufkqzOr+9j6dcbxbs3rXaqRAd4TG JOnzBcFL8qrPOX8OcHzN0XxN6uCzmHzxkbfAOwYy4LPLHY7EdzGt5NokyUcpLdVVTmFKkl6X lCtqxZMueau3l5Xbzpfslrqat7KlCMvb/iMF+iLU69I/XxP8IF8X7a3i8o9LUrU18v+NaqhU TmCbfzJRZQKzcYdja/mVVkiSr641jAuCrivmd0zH+tW53crW0OtacKF/Cn9oxp7dkUu6+ZSv OQb3vewM4TeQgEm2W3CEzw6bJLnp1UnTje9W9qQb4Bax15TJ+ybikYZa2Rqprkev+XpbTD8u N44vYAfbPVJB1e33Hh592sDLPKg3MnaAZJcFh/QMO9+mHLpKrk2SQjBhjfPN+5ucLcKD32S/ jKrjaysrvxbzrGMH5J704i/pRK7k2j+pqjqh2L/dViaVZZafV3P5SHVVA65GYgy+TC3rknIZ dyGkQEeEliTpawr3Bl89dtWvuNrrsuS1F9UM3l5LtczvcRnsvZaKfHECAAAAAAAAAAAAAAAA AAAAAAAAwHM96Wexjlz7J1VZfhZbFqgklanGXA7KryJHClQKaW7gq3TGm1TWDK5JwR+dv7Mt w2h2tsBBdMm1oOV9DcXPYvF3/Hrx13met682UgzGl9souTZJOvobNm1cZiyTyim1TMrDs+fa RLPpwjtteAusHFbzgi9PotUelW8gnRqVkVLWdQxPDvYsblKEzYaSdtlS0Z4DFpDs8qbRy3Ww cSApuTZJCnH7Fczn82FSg13smb46vrrMHkHjEQJ/wXZ/vA0Xn+yPuT9dmpebr8Ks7m/v0xnH nefqXauRAt0RGpOkzxcEL8mrPuf8ubLxNUfzNamDz2LyxUfeAu8YyIDPLnc4Et/FtJJrkyQf pbRUVzmFKUl6XVKuqBVPuuSt3g1u3iX23U7vuvOc7+llr8NvZSsF6nXpn68JfpCvi/ZWcfnH JanaGvn/RjVUKiekzfPSuO+IZ+EOx9byK62QJF9daxgXBF1XzO+YkfWrc7uVraHXteBC/xT+ 0Iw9uyOXdPMpXyWM77ty4wrY2XYLjvDZYZMkN706aQrz3cqedAPcIvaaMnnfHeyRhlrZGqmu R58Re1tMPy43ji9gB9s9UkHV7fceHn3awMs8qDcydoBklwWH9Aw736YcukquTZJCMGGN8837 m5wtwoPfZL+MquNrK3d9LWb292CAWE968Zc0upRc+ydVVWcu+7fbyqSyzPLzai4fqa5qwNVI jMGXqcrj7a6dujTLYIGOCC1J0tcU7g2+euyqX3G112XJay+qGby9lmqZ3+My2HstFTmCBAAA AAAAAAAAAAAAAAAAAAAAAIBHe9LPYh259k+qsvwstixQSSpTjbkclF9FjhSoFNLcwFfpjDep rBlck4I/On9nW4bR7GyBg+iSa0HL+xrKPfc6XhMA3OvXi7/O87x9tZFiML5FR8m1SdLR37Bp 4zJjmVROqWVSHp491yaaTRfeacNbYOWwmhd8eRKt9qh8A+lcq4yUsq5jeHKwZ3GTImw2lLTL lursYQA72OVNo5fVunG0KLk2SQpx+2XK5/Nh5oJd7Jm+Or66zB5B4xE6qjOGwcjFPrb74224 +GR/zP3p0oTYfBVmdX97n8443q1ZvWs1UqA7QmOS9PmC4CV51eecP1c2vubQnzBKXdRR3aUF QtqBlQQeapc7HInvYlrJtUmSj1JaqqucwpQkvS4pV9SKJ02U1Vu+ym3nS3ZLXc1b2VKE5W3/ kQJ9Eep16Z+vCX6Qr4v2VnH5xyWp2hr5/0Y1VCpnWZtzSxJ74g7H1vIrrZAkX11rGBcEXVfM 75h29atzu5Wtode14I7dKfyhGXt2Ry7p5lO+5njH3UrAYbsFR/jssEmSm16dNIX5bmVPugFu EXtNmbxvch9pqJWtkep69Jqvt8X047JsfL2v2+Mdtnukgqrb7z08+rSBl3lQb2TsAMkuCw7p GXa+TTl0lVybJIVgwhrnm/c3OVuEB7/JfhlVx9dWdvhaTBnG7G/JAL2e9OIvafwoufZPqqrO XPZvt5VJZZnl59VcPlJd1YCrkRiDL1PLuqRcxl0IKdARoSVJ+prCvcFXj131K672uix57UU1 g7fXUi3ze1wGe6+lomrGTSZzAAAAAAAAAAAAAAAAAAAAAAAAAJjhST+LdeTaP6nK8rPYskD7 j+XsuRyUX0WOFKgU0tzAV+mMN6msGVyTgj86f2dbhtHsbIGD6JJrQcv7Gso99yojizdwYE+/ Xvx1nuftq40Ug/EtOkquTZKO/oZNG5cZy6RySi2T8vDsuTbRbLrwThveAiuH1bzgy5NotUfl G0jnWmWklHUdw5ODPYubFGGzoaRdtlTXmwTca5c3jV6W5MY5Qsm1SVKI269UPp8PsxjsYs/0 1fHVZfYIGo/QUV1vEnC77f54Gy4+2R9zf7o0LzdfhVnd394bxY53a1bvWo0U6I7QmCR9viB4 SV71OefPlY2vOZqvSR18FpMvPvIWCGkHZSW3501K4GuXOxyJ72JaybVJko9+KSOdgJUkvS4p V9SKJ82G1dvLym3nS3ZLXc1b2VKE5W3/kQJ9Eep16Z+vCX6Qr4v2VnH5xyWp2hr5/0Y1VCqH dQD+OO5wbC2/0gpJ8tW1hnFB0HXF/I4pXr86t1vZGnpdC+7YncIfmrFnd+SSbj7la44F+w7s absFR/jssEmSm16dNIX5bmVPugFuEXtNmbxvch9pqJWtkep69Jqvt8X043Lj+AJ2sN0jFVTd fu/h0acNvMyDeiNjB0h2WXBIz7Dzbcqhq+TaJCkEE9Y437y/ydkiPPhN9suoOr62ssPXYoD9 PenFX9KJXMm1f1JVdeayf7utTCrLLD+v5vKR6qoGXI3EGHyZWtYl5TLuQkiBjggtSdLXFO4N vnrsql9xtddlyWsvqhm8vZZqmd/jMth7LRWVGZUkAAAAAAAAAAAAAAAAAAAAAAAAAHiBJ/0s 1per+WNaqSLlB6J6mV0/3FWqvpB+62/8RZzld4D2CBXKryJHClQKaW7gq3TGm1TWDK5JwR+d v7Mtw2h2tsCfxV5yLWh5X0ON/yyWH77iKX69+Os8z9tXGykG41t09FzKi48OdX+V2vUyq3ob Nm1cZiyTyim1TMr3155rE82mC++04S2wcljNC776PhV96EmnRilXta5jeHKwZ3GTImw2lLTL lor2HLCAZJc3jV6ug40DSc/VXG3oxXYlTR3zt1/BfD4fJjXYxZ7pq8O8y+wRNB4h8Bds98fb AvnmuzR3lBmVpHmXGp/sj7k/XdmA0p3n6v72Pp1x3HnOs5TVhd/KHnzTqPL5guAledXnnD9X Nr7maL4mdfBZTL74yFvgHQMZ8NluweF75O/IVZ21Hd/bmMpyr6UMyTdXKrmi9voy+V5ORflR qJ6ius5e5VdJLBnzhaN0V7+rQF+Eel3652uCHzR4Ou+qotxTpTVSHzs6+5viUuZIUZfSgGfZ bsGxjDL5Xq4UjUmTgpRmFl+Sr641LLX3ngPeMS/rV+d2K1tDr2vBWucU/tCMPbsjl3TzqbrC dlNuXAE7227BsXJ20Mu5zFZK0lRKLcrZ13dxNukGuEXepIFz6PvuYI801MrWuNw1fKjeFtOP y43jC9jBLl8ahe72ew+PPm3gZR7UGxk7QLLLgqP6A5PyTvJl6FpyvQAT1jjfvL/J2SI8+E32 y8j467MbzfvOuO6tMx7e6kkv/pJGl5SrHP/SbV57mVKSUpdeWlV15rpMauU3BJWksszyc+Ur h72U5i0DrkZiDL5MjfpdxqVZBgt0RGhJkr6mcG/w1WNXnpKVr2ZXNxgZRPoAL6O111It83tc BnuvpSJHkAAAAAAAAAAAAAAAAAAAAAAAAADwaE/6WWwzo/4G6PHfUvqSlLrW8/3qNfzdiPu/ P6Dc5epvTQeriC0QAHb268Vf53nevtpIMdjfolPdMi+tLFCqS8nlS/q6t2EHbfiepdmU96AE em6XAACHXf6WyuWS1/5HB6TToZJRqct3DnjQmWOTUDcJAwCwzC4LDjfL7RD3c4RluaRCel8Z qb+DUrqHb3nrolJaNZcUvBSGcZeld2uWfG2o77LyufEVmUrk+z9mAoARu/wtleR7syG2wEN+ j7JUV5krrWy6cvnkqyjfk51qJFIjSAXmt3wut3/0XFLwShhpS8d+VRkLtO9yWfLlw7I0va4c qw0Ar/f4Oxy62LsUyiWyuy6dfjUcVUX+9Korfj2MzU+fI214Fo/8jKXpaz53PACwv+0WHIHT bnMeD5z9p54z9KVPSPnptk1XyfY7DRua1NP+4HdsAcBiu0cqUR73vY176Tf8MRUtD+Av2GXB IT1lz7cZ+XpHntdSl16jvsII/xqKYrwupWXsda3c5XAr90sqkDUHgNd70ou/pFXIZTNl7pa+ hKE/ia+m6t/nsNSlsLSDJRKlrey58g0suZo7q4dRfufUEmHVSIFdu3zZ3liX8jVbAACe4dG3 HBRv3S8AeL1dHqlg3FtPxm/dLwD4U37uDgCRNnk0Fu6t+wUAAAAAAAAAAAAAQPIz7+l49YeF edK2D+OVyJ9Of+nI+/YXALCJf/I/VRVb9HPPXs+N3I2fgQAAprrnb6n8wTP6Jmh5AMAtGgsO 40stm2/DrCZV3zKpv+GxfI2jg15XM2NibA33i0GVGPQXdEqlNd+eufmjLgDAsyl/MeRyNrJs ln9iz3L50PLvEc0ylZ3SI9E3U+o17lozsK7wemsHAMDH/0hFOj+9+ypZ3+tS+svv3wbpuhUU GB4AAPdyLjik2/ivp/w1Mqk10pqjmt29MrM/WwEA4HaVv6XyxHPV5k8EzvNkHQAA+MuuCw7O iEaOr1zoa46uNVP+RRBjFnvJ9m+EuJMAAH/NT/WUkG7UX1KNvxxRki5l6k8ELGGUeS30AvUI 9SSlNboKbAavN1RXy5d5lRpDkgAA2Frv9XdXOQAAYJJ7XvzVpXmhzDU0AACb+7k7ABP9WcC9 pQEAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAEOPHstHn8/n+4zzPmcGsrksPQwpAStok8qMV/LF3hL7Svv/oLbPaGqm0apl5 6u3N6LBPL7UbjDl8l8ve+8RWLcWOyhfzNdQmc++9/rFstLKNdjgel1OOMWmHyA81wk3ERpgP 466Sqxun0r4um+WpvdVtYpNe2mUw5thdrh70J7bqxRM78y1oqBGmBQdeI50s36drvxyzxuUC 5blrDgDrhc+9n8/ncfPPv+UFon6HWfo85SoLka5By9ZXLjr1ILsibAZf3RElyR1GrGaE1Ru/ evO627BZ2ow2tLftyuWCow19SalJpTv8vWNZoddlDL7rYdalXmOuwENs7L29EVqqO4TxVX7i 6BvjozIVW456e2v4chkjLHOFN5Tx1FY9cL2D6Ll+LIf50p/KLY2F5BX31lXSD4A9QmPAzSRL UQse4/kiLOkH3ZhkPPRde2Rfv/aWnH9YFlv2T8uOjLehPcm4pb0EneV8oxTYFYavrq4jZaTv Tm+ExlrumqWNEYZ315AuOmMQWWo3dviRFniuf5U0Y8t2kbI06yonet13s89/3+5RJogFeuuq bj+1tynNu7KhesWeS47aOP+MfZMupB+O753SSs0IfbHpI91XbFddt8zRva2hW5lrpVv2a3ZP iG32wVG5LW3B0dTbCtK16STpmB21UFcewqhJ/BZbBbMDx9HcpB9K9AiNJTQ/OabNADu0oS6q VeflWul9+zWjY4+Pyg3Ff2n00uj3ttd5nsvWN4Bk/364f4QzpAn9QbaaYDGVPiqf2HtjFhyX PU9tdONgyEPSZ1LlsPmSjFHNFl7X/gVO5ZvoZ/fDcfYIx8vfM5fPjftlnGBpw/FcKwuUCn/T lcDPIX/dyZiUNrgUXR0MjrrSv8t/6PumRGgMviupnBGMdYXrilBvXl8bKkdZj7C5R9Xgu4qq FiiVWRbrqHGwDR1JyvfODtdY1neq+cUUY99oHmV9v7rqyjfwPRoOidBSi5RLH1llLqVvSPvl jtDX2WK7qLEuKam3ofTOpp8dArsNAGA7Ky/l342WhNHQl0YB4KG4ZAQWM/0tFQAASu7HmgAA AAAAAAAAAABKL/kOR+8PuowFPvSRpBS88rQ1PKkZ3u0FbhKGr8B8g8ACHdy/LFXeHtFb4Mh+ 6b9FrJbpHl8PnU+AKC/58/SM5KY05ZUv2AhPCg+D/Spz9f4Q0RfGDLFVj+yXtA44/yNl6Q3j 9jYHdhC24Fg5lhbUJU03U0XtVxn8ZWLNp7/wpLzS8pORAi/lvGa/ugq8tICRr3ktwkdKV4Fd +6XntdTeXG0oYbDmAGLew1GdLpM0Dqt3Ly//W+bS66p+0hWGEkn1tF2N0JckFZ7iqUaiFygF /xpM2WX3CC/8UpH0idI/q71XL1wq8DAPotlYNAAjAu5wSMuIrpucxlzNGbC3wCrlVmq1QF+S sl9pS0eB+lxcXkzPS1IuFn0FHurhfu5+dRUotYCRr3kl1S3zbnnpovmeVve6d+jl24SvAxxN PSMM4DVG73CUY/L874/qfj80DldLLvtq47LBDNISp9zMsV8jYbzY4Ln2TS63CkLaJLx5H32k 6GxAuKEFhzQm01m2mirRc/nG/8r5Qqprxn65KRWFJ8WGoTfUc/ert8CuBbc9jHn9cE3fjq3F 3RosUACF/5FK8wSgPEGQSLliZ0PpIUVI4VKNC/ZrN4G3l7dqqPDb5rffh1euHI61IwXAizkX HMrUk8+e9jWHkitkmrvM6akKd+HGp/WL90uiVB2eFB6GUvij98tXoEXZK3zNm28zY7UxvtIa aSjHFdFIGCzXAOeLvz7qY+PqZFdNylOlXMa6zv++Fd8s8JJX/zaGEvxgUlQbVue125MUvQXq DeWO8Pb9GinQUp0xS7N5HQUqYV+2MTaUu883dS0OlOlLD4PVBnCz8eubF6NxAABvctubRlny AwDwdyz9WyrNZxz4GrlFDAAAAAAAAAAAAAAAnsj0HQ7pN2xugT+Km/d7udnCW9Ve42Frw+rP ZIy/A3wxy+9Iq7m+/5C66O0N6NuvGWF8/xE720gvDVp2ONzdZs1BmffLbccvunvDwFOYfqUS fuD1As/zLM9q53+OrFMqSdWitnJXYPbmzbfPN5CK+gvcv1WWGmqTBtznN9i3rL9n1+5r3mUH JZ8E7PXquaRClFy+MPAgt/0sNsTgCY93XQCv9weXxV0u9yGMJ3s9V3O1UebyhYFn+Tc/zMpL 90r6ffjqNbRe4Ob0/Wq2RvNWrfE1qfYCN6R0Nn2/HJ3NV2CzLr3eaoFlapPUOMZcjjZs1ms/ Xu6WL1Ob7LONFIP+wEVKkjZOHN3GGKE+Y8e+eqDZvBKWC6hq3OHQH8Ip9+F7C1Sk8tMNiXKS kpKaJYecrZXWKOeFakNJc4q7QDt7806dPlIY5S4bW+P43Sy+AvW6Ustceo4+HBw900fpG779 8tXla/ljTkNVS7Ps8ue/L09Yur27eaWm8B0U97ScslfXK9XxpeTy1TVYIB5B+/P0zfE/fjni yPXtjnkhStI+ms1YbqA3b9RuKs1bnVnual6pNc7zzGcoe3iW3tu1s5al5BpSdTPmcceu7dNQ iq5IUiesDhxF7BFxh2EpM/3veJn4s7QFR9Pf7HwjM2PvLBZb4KMpe3oWf7dvsECf3Y5FGc+8 CO9t+WOD9Up+Yu69IXHErTwcYeR5lTKlDcJnwt3GEQLFf2nUchduE5vcu4udcf6gS2cDbuF7 kLF/GIwvRIlZcFzO3Km7z15trF8xTBp7+gRx18JokwXZxSWq/Ln14TouvsfJj34IvUnwUXUN jsrxMMqHDrHNa8xlDyOnXyJK48t3YanketCVKtx+jt99qNrb9KS0waXoao9RCryUKX1uT1IK 9ClvgTZbQwmgOnRHCjTGX+Zd2bzNHuVojTLg6mwbsstHceDsBY70+WokUmB62M0NLMFb6uo6 lEpdOqUuY5zV8KQC9TC66joMu9ybqxmGJX7j+JJylWEoqVNnbABYZP87DUav2REAf9mzX/wF vB73lgG8g+lvqQCP8+h7s+4b4wAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAKLP5/P5fO6OAkDDv5aN0mA+zzOkVqnAfNbIky6z iTFJKXAH4a1qr/GwtWF1Epcy2vfCvePfjGWuwQIdGR3lhAfvCyO2ZL1GaZf3MWlm23mXFc0u WqaGJzXDu73ATcLwFZhvEFig3T+WjcLHj17geZ7lWe38z5Htv5JULWordwVmb958+3wDqSiL vK9HXZW6WzLqEIyUE9gN5vUoqeRtB5fR0+NfIJ8fjt9jNjwpPAz2q8zVO+v6wpCYFhzbGlxP cCf2Ro4Dt/PysenRwfus2WX75dqCwX7LUQ5cuF+Cv7RtfsoJT8orLT8ZKfBSzmv2q6vASwsY +ZpX8W95xVntc83SU66ykMsnDz3H6/vVbI3mzVu9lRwF7k/paeVOOfZXasNqqrE0pWM3Pyw/ b1aX9B5lKdqytGaP8g3Yaml6XfmH9mWEsWXsl3rjM5vegNJBsSdJhRubVw/yufOJ7qHnnUBl 9wgv/FJR+UnjDoc07PPbLL4bPpaNv1L5aUFXDhUpqVlyyOhSWqNcyVUbqjpzjRRoZ2/e8W56 ucIoI1G6k/uMWy3T0VuMleoLUHs5h2t8KWFIpaVPYhuqmkWpK9/l8KNjXCweYy1fDVgp0Jek 7JexeR1dVBn+4UnKtOwr8FAP93P3q6vAwTHla96S9qXRZim9ZyDfPpcn4zSffilJ+2g2ozT3 OQrsojRvdeUxUq9+Lhlf0BjLnLTaCC/T3SBRzTuvoVayrzYuG8xgHObfkSKNxDyj7+g8/Zh2 eUc3DnG5lghpk67mNf1KRfI3D+GycW7Z+DWHIG/VwOl+Rvssm78mXeLPO5tuyHewVg4rqa60 5qhus/gkqlQUnhQbht5Qz92v3gK7Ftz2MHqLiv/SqHQrL7yicfptomX+4GkAWCB28lk/s0mP P3aeVMcFTstbNVT46eb285fUvMpIiVlwXPY81Tf7eK9v8UsjRtHXHHd1rNs7dKCofZnUAZqV vuZALBMy+YTPbMqhzJPyf89Y6Bh7lFJ1eFJ4GErhj94vX4EWZa/wNW++zWWzn7y48hG7JSmv 4BJ9+blS4KVM6XN7klKgj9LcUhhKANUJZaRAY/xl3mXNq2/v6xtKkmW/qnXp8ZfHSz+U4cHr 4UlhNMdyb66R/erq8z4f9RF1+Mx2RI8vZQaw7FdXXUrwi5MUvQXqDeWO8Pb9GinQUp0xS7N5 lQIBYBfG62+UaDrs7Nkv/gLwDpwpgdf7uTsAADiO6AegfxANCAAAAAAAAOCLR7wAADzX/79p 1PcLFuW3MY4CeQYJAMArDf1KJfaWQ1qgXN5tAAAA/rTAxxxlUfknPE8BAODR/vdI5fKOwvzD 9Ca+4/dbxsrN8nKrBR7FfQvjcxMerwAA8Gj/e6TSfOF8+QrnlCX/9yXvRf7QRHpuws0MAADe x/QdDm4wAACAEf+2N/nPmmUHixsAAN6Hv6UCAACmi1lwjH/x4vKVDv6sLQAAb/K/P94m/cH7 8sMLy69Ryl++SMXy4i8AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAA0M+XXQAACb9JREFUAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAACD6+f7n8/mkj87z HCw0L00q8LvNJckdRrU0S4F6xvzzy05dytR32bdf1VyXwPL/HYnQ7fP5hBSVwosKbJNKZ1Qh HUq9A1yyW+JpBh+4d4NFObLf0uVuVw7YG4eeMk/qqU88ZH+zv138k//PeZ5RE8f5n6M2D1Zn xjyjtI1So6NAPWNVvl/Viqp1+Ro2ZdEXUtXteyP0CSnk65ZBuKDS8CqMna25RLBoBh+4d4NF 9WZvrtRfybgkvSUMvWO7zw77+MvrjOSf9iadmidXvbelQqQtLaVZCuxdbYSsxgI1G8cxBT9x GL9beVCUfugben/cVoP6L3BMsO6zA3bz79TSpQcT53lGdRdf51PCeFBvVoL83jidN5lWLz6q qV13TZUy9TDyo5Zy2e/QlvWW9z+VJMt+Oe4hN9kfjhxjQ6+rokPdL18HcBxKO+NB0TuAxNdF BzubEkYZQ7mZZSz7WuP43Q56tOPTl68fOpKarWG8vn398jf+DkeirDb0XLEn+7LA8d4srbiX 3SSYcSHbtUDJNy4zWu6LKvOO4wDlLf/9h/EObblfx+/lmnLCuNSo75evNeyXfXrqYJ/vWoUr ++XrAL5D2YywWrtSl9IBjJXau+hgZyvpAzaVXBYoVaSMlEH6eshei68f+pL01pD2yHcoH23W HY7mIjr92z0JDnKHUd21/H+XrTmkipSkNfTAUmsr3aOrV6T9Ne54yNnXlzHf/TyYXl2rjWpd vUOvGvygrg4QtTY9fneYrowpuyNLVxdt1jVjgDen6wXGrwaT5mxjXKgNhqHskWU+fJkpCw79 8tG+TQhfGJLA8TBOX3MsDibRLwHTGDu2aUafqOAd5ThWGyN9fhO7BbwyngXzZJX7ds54dVW+ leWyc43Da+ZDo/hHKn+n7V6m63blCP3+4R+5tWhUHpTXjy86wN80qWPv/7Ri/wgDTfwOx5fx NCY9LXMUZS9whtefD6qMhybfjDXHhW/Bt2yZOIMUvN4BHr3L4d7abZS5wjjHGmebQ22NqQ1l iXD/I9Ul/sVfygxS3UZ6nq18xUavrrfAS6qlQGNRxlSJEl71f+0xdIVhDLLa7OXDcimM6sCz zCmXWpSbwFERVgOz1NWVJGmOL73peruiHqFlIBuT9A7gO5SWnbIfypFR3NtF543lcsAaW14a KV0Dtgz+EJriEuThav/wUdlM8rWhsl/2hgXwPC+7pACATUx/pAIAAPBzdwDARgKfLQIAAAAA AAAAgAXyry7yNUYAqGKqfJD/vWk09tG15Vdbzd+4On7r5fg9qv4jpWrGsq4ZP+iKVf3xamCx 4SVDMulQ+vQGs1Xwx3F8gt7UPrhfShib/CoyqqF2oxy4qJZv9o3Fg6I8lJYAolrj169U0ivP RqTIlBeoVc/QeUZpG6VGR4FSxvM3S5bj9y5Xk9SdmGtG7b7jxSXIoK3m/d5gtgo+sB+O7Nf+ w2H/CN0WdMhmFSsHheWKeqr4n8U2T676aiMVIm1pKc1SoGMU6QuU3tJ0lwK3mqmPgePVu5pU ar/dyjA22WWfRwd/r9uvVfY3aaqk5XNRrTHrr8V+SU8fzrg/Z+o7gfnCCDlZ9lZ3FEPI9yK8 yza9uQKdY393tFw15sfx8nSsmnQMt2G5mZRLeTmju64yqVngjIYyMl4SNF/U2IzwdL1pVB8O 9qGn7JovjOP3rkkf2nuUpYsqpXXdVPeNL/eolKbKriCrSb651zjxdoU3OCqNh9LeD31hTHzx l7La0HPFntHLApthfDKO6vTCB+UPMi4LICUpz+7IpcfjaCX30k26s1IGX06gll02toZ0Ruxq Q19dvjCU1lDacLBvKMGX/VBhjNA+9FI5l3/nn5ThjR+vrjCaheRD7/uP8Y7dG6EUmCOM8OCN QVZT9eFWDaMZXlfktxxKaVQ6WkMy6w5Hc5ZM/zZ24nDVMC7BfIe0PcLZq41LRbpqGHe1duns v8/ha96RXdZHWr5Zvi/GGi257KuNy+dKpZbY7AU2M27eD0vS/g4er1hn8cdZLjHcqNlQvdOX b3wp3DOJEoZxp7omPWnhEtsaecldGzvCmLLgkA5n/ollmxC+MByWzTXLarFwR9LbXIPNG9Vi Sr9NV5z2uvRc8xZYvTNLVwBfK4dDoDzscrr3HeXFdghMbyhHhJu0vBSG3m1GqusKYzFHGPGP VG5vBexv8WojSvM2rGPGkXI1dzl8dgu0yfGaQT/KOx+UxXzDYWWBhLE+jOl/vC2tgHSXoKsT lrEoe4HuaPehBDx1X3zN69jYsX2gvA2VMPLN7MNPyWXcZb2u8A5gLPBxqw37flmOsvs0cNfx Ci/QPhyM05dvfIW7MYzw1hjvG74wflLm9NHgTKEMwuo25Y0pKQxpFaLUZSnwknopUCpNSpVO SEoYvewRljuV9wzLLtsjmbTaOFpf9GnucrU6Xxs6wiiTpCCNdfkOpX1kdfUNaQQNBn8W3wB1 R6i7xGMMo6xL3y9fGIfcvJfYysYpcxmTyl3WI2zukS+MriQffZctZygpyd5txuuqFqgrD2Wz 9zoiBN5pfKm+0rOifRbaFtjc3PdwAEgcd3egM95WzC1u/03CCPfW/cJUP3cHAPjFPquagbuO s+3fBwAAAAAAAAAAAAAAAAAAAAAAAAAAUX7c76AcT1JeZhf4MkEAAHC7H+X9Lb1vF24m5dwl 8PYkAAAe539vGi3fzJ9Ifxvl+yLh74k/P/0rSVJpFry0GACA52q/2ly6l5AWFuU2UpLyR4bc YQAAgP0N/Xn68zyl1YOSBAAA/pqOBUf+xxjzf18WFkpSiOrfhOQPRQIAsLOfy1c3Lt8Vnfcr la6fojR/pcI3SQEAQB9uVwAA8DJD3+EIxCIDAIAX+7k7gP+nvBMMAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAADz+D2AdaNOyuipZAAAAAElFTkSuQmCC --------------050000060501030900090607 Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users --------------050000060501030900090607-- From xen-users-bounces@lists.xen.org Fri Sep 21 13:09:23 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Fri, 21 Sep 2012 13:09:23 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TF2xs-0005YJ-Ex; Fri, 21 Sep 2012 13:08:16 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TF068-0000e5-AE for xen-users@lists.xen.org; Fri, 21 Sep 2012 10:04:36 +0000 Received: from [85.158.139.83:43498] by server-15.bemta-5.messagelabs.com id 5F/9B-23541-3BB3C505; Fri, 21 Sep 2012 10:04:35 +0000 X-Env-Sender: lukas@laukamp.me X-Msg-Ref: server-15.tower-182.messagelabs.com!1348221873!29324373!1 X-Originating-IP: [5.9.218.245] X-SpamReason: No, hits=0.7 required=7.0 tests=BODY_RANDOM_LONG, RCVD_ILLEGAL_IP X-StarScan-Received: X-StarScan-Version: 6.6.1.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 28869 invoked from network); 21 Sep 2012 10:04:33 -0000 Received: from mailer0.lippux.de (HELO mailer0.lippux.de) (5.9.218.245) by server-15.tower-182.messagelabs.com with SMTP; 21 Sep 2012 10:04:33 -0000 Received: from localhost (localhost [127.0.0.1]) by mailer0.lippux.de (Postfix) with ESMTP id B6CD44225B1 for ; Fri, 21 Sep 2012 12:04:33 +0200 (CEST) X-Virus-Scanned: Debian amavisd-new at mailer0.lippux.de Received: from mailer0.lippux.de ([127.0.0.1]) by localhost (mailer0.lippux.de [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id SSwaBt8Cd7a5 for ; Fri, 21 Sep 2012 12:04:33 +0200 (CEST) Received: from [127.0.0.1] (unknown [5.9.218.242]) (Authenticated sender: lukas@laukamp.me) by mailer0.lippux.de (Postfix) with ESMTPSA id 223B242259B for ; Fri, 21 Sep 2012 12:04:32 +0200 (CEST) Message-ID: <505C3BA7.5010105@laukamp.me> Date: Fri, 21 Sep 2012 12:04:23 +0200 From: Lukas Laukamp User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:15.0) Gecko/20120907 Thunderbird/15.0.1 MIME-Version: 1.0 To: xen-users@lists.xen.org Content-Type: multipart/mixed; boundary="------------050000060501030900090607" X-Mailman-Approved-At: Fri, 21 Sep 2012 13:08:13 +0000 Subject: [Xen-users] Xen 4.2 (backported packages) can't load Dom0 (Kernel 2.6.32-5-xen-amd64) X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org This is a multi-part message in MIME format. --------------050000060501030900090607 Content-Type: text/plain; charset=ISO-8859-15; format=flowed Content-Transfer-Encoding: 7bit Hey all, I have a problem with Xen 4.2 on Debian Squeeze with Kernel 2.6.32-5-xen-amd64. I rebuilded the source packages from Debian experimental trunk on Squeeze and installed them. Also I installed the Kernel 2.6.32-5-xen-amd64 from the Debian Squeeze trunk. Now it looks like that Xen can't load the Dom0. After registering netback strange modprobe errors appear. In the attachment is a screenshot of the errors. I also build Xen directly from source without packaging it and it works fine with the 2.6.32-5-xen-amd64 kernel. So I think it's a problem which only appears in the packages with the Debian patches. Does someone have an idea how to solve this issue? Best Regards --------------050000060501030900090607 Content-Type: image/png; name="xen-dom0.png" Content-Transfer-Encoding: base64 Content-Disposition: attachment; filename="xen-dom0.png" iVBORw0KGgoAAAANSUhEUgAAAtAAAAGQCAIAAAAIhcA6AAAAA3NCSVQICAjb4U/gAAAAF3RF WHRHZW5lcmF0b3IgVmVyc2lvbgAwLjkuMSqKm2cAAAAwdEVYdERvbWFpbiBVVUlEADQ3MjBi YjcwLThjZDgtZjhkMS1jYTZiLTlhMmFjOTRmZDczMnzf/TUAAAA3dEVYdEh5cGVydmlzb3Ig VVJJAHFlbXUrc3NoOi8vbHVrYXNANS45LjE2LjIyOTo1MDAwMC9zeXN0ZW1SiP2zAAAAGnRF WHRHZW5lcmF0b3IgQXBwAHZpcnQtbWFuYWdlcqvpgfMAAAAYdEVYdERvbWFpbiBOYW1lAGRl Ymlhbi1kZXZlbP0O5PsAACAASURBVHic7d3Rmqwor4Bhe565SC+xLnMf1D9sWkgIISDa33sy awqBiICoVfZxAAAAAAAAPN3P9z+fzyd9dJ7nTcE4w1By7Z9UlW9/yVgmpQKVpDLVmMvhW+Cl /JEyU4RSIc0NfJXGlvb9x5rBNSn4w9ajlDCanS1wEF1yLWh5X0M59qvZ8sCe/sn/5zzP21cb KYbqSbcr1yZJR3/Dpo3LjGVSOaWWSXl49lybaDZdeKcNb4GVw2pe8OVJtNqj8g2kU6MyUsq6 juHJwZ7FTYqw2VDSLlsq2nPAApJ/2psscbkONg4kJdcmSSFuv4L5fD5MarCLPdNXx1eX2SNo PEK7ey8LgRH/3h0AGr73pd8xxaR5uXqju3lvuffpjOPOc/Wu1UiB7giNSdLnC4KX5FV/j3Xs I54jYs2hP2GUuqijuksLxLbD+PNKYKVd7nAkvotpJdcmST5KaamucrpRkvS6pFxRK550yVu9 G9y8S+y7nd515znf08teh9/KVgrU69I/XxP8IF8X7a3i8o9LUrU18v+NaqhUzozJgdUGHoQ7 HFvLr7RCknx1rWFcEHRdMb/jSZB+dW63sjX0uhacJlN/HrxF0UW6+ZSvOUL2ndUGnmi7BUf4 7LBJkptenTSF+W5l+3KFiL2mTN43I4801MrWSHU9es3X22L6cYkaX6w28FDbPVJB1e33Hh59 2sDLPKg38iQFSHZZcEjPsPNtyqGr5NokKcSDptdt+eb9TVZa4cFvsl9G1fG1lRu/FvOsQ4k/ 7kkv/pJO5Equ/ZOqqjOI/dttZVJZZvl5NZePVFc14GokxuDL1LIuKZdxF0IKdERoSZK+pnBv 8NVjV/2Kq70uS157Uc3g7bVUy/wel8He26xFKRMAAAAAAAAAAAAAAAAAAAAAAAAA3upJP4t1 5No/qcrys9iyQCWpTDXmclB+FTlSoFJIcwNfpTPepLJmcE0K/uj8nW0ZRrOzBQ6iS64FLe9r KH4Wi7/j14u/zvO8fbWRYjC+zUbJtUnS0d+waeMyY5lUTqllUh6ePdcmmk0X3mnDW2DlsJoX fHkSrfaofAPpXKuMlLKuY3hysGdxkyJsNpS0y7rzt4g9AKbb5U2jl+tg4xyh5NokKcTtE8rn 89ltFYKdxZ7pq+Ory+wRNB4h8Bds98fbcPHJ/pj706V5ufkqzOr+9j6dcbxbs3rXaqRAd4TG JOnzBcFL8qrPOX8OcHzN0XxN6uCzmHzxkbfAOwYy4LPLHY7EdzGt5NokyUcpLdVVTmFKkl6X lCtqxZMueau3l5Xbzpfslrqat7KlCMvb/iMF+iLU69I/XxP8IF8X7a3i8o9LUrU18v+NaqhU TmCbfzJRZQKzcYdja/mVVkiSr641jAuCrivmd0zH+tW53crW0OtacKF/Cn9oxp7dkUu6+ZSv OQb3vewM4TeQgEm2W3CEzw6bJLnp1UnTje9W9qQb4Bax15TJ+ybikYZa2Rqprkev+XpbTD8u N44vYAfbPVJB1e33Hh592sDLPKg3MnaAZJcFh/QMO9+mHLpKrk2SQjBhjfPN+5ucLcKD32S/ jKrjaysrvxbzrGMH5J704i/pRK7k2j+pqjqh2L/dViaVZZafV3P5SHVVA65GYgy+TC3rknIZ dyGkQEeEliTpawr3Bl89dtWvuNrrsuS1F9UM3l5LtczvcRnsvZaKfHECAAAAAAAAAAAAAAAA AAAAAAAAwHM96Wexjlz7J1VZfhZbFqgklanGXA7KryJHClQKaW7gq3TGm1TWDK5JwR+dv7Mt w2h2tsBBdMm1oOV9DcXPYvF3/Hrx13met682UgzGl9souTZJOvobNm1cZiyTyim1TMrDs+fa RLPpwjtteAusHFbzgi9PotUelW8gnRqVkVLWdQxPDvYsblKEzYaSdtlS0Z4DFpDs8qbRy3Ww cSApuTZJCnH7Fczn82FSg13smb46vrrMHkHjEQJ/wXZ/vA0Xn+yPuT9dmpebr8Ks7m/v0xnH nefqXauRAt0RGpOkzxcEL8mrPuf8ubLxNUfzNamDz2LyxUfeAu8YyIDPLnc4Et/FtJJrkyQf pbRUVzmFKUl6XVKuqBVPuuSt3g1u3iX23U7vuvOc7+llr8NvZSsF6nXpn68JfpCvi/ZWcfnH JanaGvn/RjVUKiekzfPSuO+IZ+EOx9byK62QJF9daxgXBF1XzO+YkfWrc7uVraHXteBC/xT+ 0Iw9uyOXdPMpXyWM77ty4wrY2XYLjvDZYZMkN706aQrz3cqedAPcIvaaMnnfHeyRhlrZGqmu R58Re1tMPy43ji9gB9s9UkHV7fceHn3awMs8qDcydoBklwWH9Aw736YcukquTZJCMGGN8837 m5wtwoPfZL+MquNrK3d9LWb292CAWE968Zc0upRc+ydVVWcu+7fbyqSyzPLzai4fqa5qwNVI jMGXqcrj7a6dujTLYIGOCC1J0tcU7g2+euyqX3G112XJay+qGby9lmqZ3+My2HstFTmCBAAA AAAAAAAAAAAAAAAAAAAAAIBHe9LPYh259k+qsvwstixQSSpTjbkclF9FjhSoFNLcwFfpjDep rBlck4I/On9nW4bR7GyBg+iSa0HL+xrKPfc6XhMA3OvXi7/O87x9tZFiML5FR8m1SdLR37Bp 4zJjmVROqWVSHp491yaaTRfeacNbYOWwmhd8eRKt9qh8A+lcq4yUsq5jeHKwZ3GTImw2lLTL lursYQA72OVNo5fVunG0KLk2SQpx+2XK5/Nh5oJd7Jm+Or66zB5B4xE6qjOGwcjFPrb74224 +GR/zP3p0oTYfBVmdX97n8443q1ZvWs1UqA7QmOS9PmC4CV51eecP1c2vubQnzBKXdRR3aUF QtqBlQQeapc7HInvYlrJtUmSj1JaqqucwpQkvS4pV9SKJ02U1Vu+ym3nS3ZLXc1b2VKE5W3/ kQJ9Eep16Z+vCX6Qr4v2VnH5xyWp2hr5/0Y1VCpnWZtzSxJ74g7H1vIrrZAkX11rGBcEXVfM 75h29atzu5Wtode14I7dKfyhGXt2Ry7p5lO+5njH3UrAYbsFR/jssEmSm16dNIX5bmVPugFu EXtNmbxvch9pqJWtkep69Jqvt8X047JsfL2v2+Mdtnukgqrb7z08+rSBl3lQb2TsAMkuCw7p GXa+TTl0lVybJIVgwhrnm/c3OVuEB7/JfhlVx9dWdvhaTBnG7G/JAL2e9OIvafwoufZPqqrO XPZvt5VJZZnl59VcPlJd1YCrkRiDL1PLuqRcxl0IKdARoSVJ+prCvcFXj131K672uix57UU1 g7fXUi3ze1wGe6+lomrGTSZzAAAAAAAAAAAAAAAAAAAAAAAAAJjhST+LdeTaP6nK8rPYskD7 j+XsuRyUX0WOFKgU0tzAV+mMN6msGVyTgj86f2dbhtHsbIGD6JJrQcv7Gso99yojizdwYE+/ Xvx1nuftq40Ug/EtOkquTZKO/oZNG5cZy6RySi2T8vDsuTbRbLrwThveAiuH1bzgy5NotUfl G0jnWmWklHUdw5ODPYubFGGzoaRdtlTXmwTca5c3jV6W5MY5Qsm1SVKI269UPp8PsxjsYs/0 1fHVZfYIGo/QUV1vEnC77f54Gy4+2R9zf7o0LzdfhVnd394bxY53a1bvWo0U6I7QmCR9viB4 SV71OefPlY2vOZqvSR18FpMvPvIWCGkHZSW3501K4GuXOxyJ72JaybVJko9+KSOdgJUkvS4p V9SKJ82G1dvLym3nS3ZLXc1b2VKE5W3/kQJ9Eep16Z+vCX6Qr4v2VnH5xyWp2hr5/0Y1VCqH dQD+OO5wbC2/0gpJ8tW1hnFB0HXF/I4pXr86t1vZGnpdC+7YncIfmrFnd+SSbj7la44F+w7s absFR/jssEmSm16dNIX5bmVPugFuEXtNmbxvch9pqJWtkep69Jqvt8X043Lj+AJ2sN0jFVTd fu/h0acNvMyDeiNjB0h2WXBIz7Dzbcqhq+TaJCkEE9Y437y/ydkiPPhN9suoOr62ssPXYoD9 PenFX9KJXMm1f1JVdeayf7utTCrLLD+v5vKR6qoGXI3EGHyZWtYl5TLuQkiBjggtSdLXFO4N vnrsql9xtddlyWsvqhm8vZZqmd/jMth7LRWVGZUkAAAAAAAAAAAAAAAAAAAAAAAAAHiBJ/0s 1per+WNaqSLlB6J6mV0/3FWqvpB+62/8RZzld4D2CBXKryJHClQKaW7gq3TGm1TWDK5JwR+d v7Mtw2h2tsCfxV5yLWh5X0ON/yyWH77iKX69+Os8z9tXGykG41t09FzKi48OdX+V2vUyq3ob Nm1cZiyTyim1TMr3155rE82mC++04S2wcljNC776PhV96EmnRilXta5jeHKwZ3GTImw2lLTL lor2HLCAZJc3jV6ug40DSc/VXG3oxXYlTR3zt1/BfD4fJjXYxZ7pq8O8y+wRNB4h8Bds98fb AvnmuzR3lBmVpHmXGp/sj7k/XdmA0p3n6v72Pp1x3HnOs5TVhd/KHnzTqPL5guAledXnnD9X Nr7maL4mdfBZTL74yFvgHQMZ8NluweF75O/IVZ21Hd/bmMpyr6UMyTdXKrmi9voy+V5ORflR qJ6ius5e5VdJLBnzhaN0V7+rQF+Eel3652uCHzR4Ou+qotxTpTVSHzs6+5viUuZIUZfSgGfZ bsGxjDL5Xq4UjUmTgpRmFl+Sr641LLX3ngPeMS/rV+d2K1tDr2vBWucU/tCMPbsjl3TzqbrC dlNuXAE7227BsXJ20Mu5zFZK0lRKLcrZ13dxNukGuEXepIFz6PvuYI801MrWuNw1fKjeFtOP y43jC9jBLl8ahe72ew+PPm3gZR7UGxk7QLLLgqP6A5PyTvJl6FpyvQAT1jjfvL/J2SI8+E32 y8j467MbzfvOuO6tMx7e6kkv/pJGl5SrHP/SbV57mVKSUpdeWlV15rpMauU3BJWksszyc+Ur h72U5i0DrkZiDL5MjfpdxqVZBgt0RGhJkr6mcG/w1WNXnpKVr2ZXNxgZRPoAL6O111It83tc BnuvpSJHkAAAAAAAAAAAAAAAAAAAAAAAAADwaE/6WWwzo/4G6PHfUvqSlLrW8/3qNfzdiPu/ P6Dc5epvTQeriC0QAHb268Vf53nevtpIMdjfolPdMi+tLFCqS8nlS/q6t2EHbfiepdmU96AE em6XAACHXf6WyuWS1/5HB6TToZJRqct3DnjQmWOTUDcJAwCwzC4LDjfL7RD3c4RluaRCel8Z qb+DUrqHb3nrolJaNZcUvBSGcZeld2uWfG2o77LyufEVmUrk+z9mAoARu/wtleR7syG2wEN+ j7JUV5krrWy6cvnkqyjfk51qJFIjSAXmt3wut3/0XFLwShhpS8d+VRkLtO9yWfLlw7I0va4c qw0Ar/f4Oxy62LsUyiWyuy6dfjUcVUX+9Korfj2MzU+fI214Fo/8jKXpaz53PACwv+0WHIHT bnMeD5z9p54z9KVPSPnptk1XyfY7DRua1NP+4HdsAcBiu0cqUR73vY176Tf8MRUtD+Av2GXB IT1lz7cZ+XpHntdSl16jvsII/xqKYrwupWXsda3c5XAr90sqkDUHgNd70ou/pFXIZTNl7pa+ hKE/ia+m6t/nsNSlsLSDJRKlrey58g0suZo7q4dRfufUEmHVSIFdu3zZ3liX8jVbAACe4dG3 HBRv3S8AeL1dHqlg3FtPxm/dLwD4U37uDgCRNnk0Fu6t+wUAAAAAAAAAAAAAQPIz7+l49YeF edK2D+OVyJ9Of+nI+/YXALCJf/I/VRVb9HPPXs+N3I2fgQAAprrnb6n8wTP6Jmh5AMAtGgsO 40stm2/DrCZV3zKpv+GxfI2jg15XM2NibA33i0GVGPQXdEqlNd+eufmjLgDAsyl/MeRyNrJs ln9iz3L50PLvEc0ylZ3SI9E3U+o17lozsK7wemsHAMDH/0hFOj+9+ypZ3+tS+svv3wbpuhUU GB4AAPdyLjik2/ivp/w1Mqk10pqjmt29MrM/WwEA4HaVv6XyxHPV5k8EzvNkHQAA+MuuCw7O iEaOr1zoa46uNVP+RRBjFnvJ9m+EuJMAAH/NT/WUkG7UX1KNvxxRki5l6k8ELGGUeS30AvUI 9SSlNboKbAavN1RXy5d5lRpDkgAA2Frv9XdXOQAAYJJ7XvzVpXmhzDU0AACb+7k7ABP9WcC9 pQEAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAEOPHstHn8/n+4zzPmcGsrksPQwpAStok8qMV/LF3hL7Svv/oLbPaGqm0apl5 6u3N6LBPL7UbjDl8l8ve+8RWLcWOyhfzNdQmc++9/rFstLKNdjgel1OOMWmHyA81wk3ERpgP 466Sqxun0r4um+WpvdVtYpNe2mUw5thdrh70J7bqxRM78y1oqBGmBQdeI50s36drvxyzxuUC 5blrDgDrhc+9n8/ncfPPv+UFon6HWfo85SoLka5By9ZXLjr1ILsibAZf3RElyR1GrGaE1Ru/ evO627BZ2ow2tLftyuWCow19SalJpTv8vWNZoddlDL7rYdalXmOuwENs7L29EVqqO4TxVX7i 6BvjozIVW456e2v4chkjLHOFN5Tx1FY9cL2D6Ll+LIf50p/KLY2F5BX31lXSD4A9QmPAzSRL UQse4/kiLOkH3ZhkPPRde2Rfv/aWnH9YFlv2T8uOjLehPcm4pb0EneV8oxTYFYavrq4jZaTv Tm+ExlrumqWNEYZ315AuOmMQWWo3dviRFniuf5U0Y8t2kbI06yonet13s89/3+5RJogFeuuq bj+1tynNu7KhesWeS47aOP+MfZMupB+O753SSs0IfbHpI91XbFddt8zRva2hW5lrpVv2a3ZP iG32wVG5LW3B0dTbCtK16STpmB21UFcewqhJ/BZbBbMDx9HcpB9K9AiNJTQ/OabNADu0oS6q VeflWul9+zWjY4+Pyg3Ff2n00uj3ttd5nsvWN4Bk/364f4QzpAn9QbaaYDGVPiqf2HtjFhyX PU9tdONgyEPSZ1LlsPmSjFHNFl7X/gVO5ZvoZ/fDcfYIx8vfM5fPjftlnGBpw/FcKwuUCn/T lcDPIX/dyZiUNrgUXR0MjrrSv8t/6PumRGgMviupnBGMdYXrilBvXl8bKkdZj7C5R9Xgu4qq FiiVWRbrqHGwDR1JyvfODtdY1neq+cUUY99oHmV9v7rqyjfwPRoOidBSi5RLH1llLqVvSPvl jtDX2WK7qLEuKam3ofTOpp8dArsNAGA7Ky/l342WhNHQl0YB4KG4ZAQWM/0tFQAASu7HmgAA AAAAAAAAAABKL/kOR+8PuowFPvSRpBS88rQ1PKkZ3u0FbhKGr8B8g8ACHdy/LFXeHtFb4Mh+ 6b9FrJbpHl8PnU+AKC/58/SM5KY05ZUv2AhPCg+D/Spz9f4Q0RfGDLFVj+yXtA44/yNl6Q3j 9jYHdhC24Fg5lhbUJU03U0XtVxn8ZWLNp7/wpLzS8pORAi/lvGa/ugq8tICRr3ktwkdKV4Fd +6XntdTeXG0oYbDmAGLew1GdLpM0Dqt3Ly//W+bS66p+0hWGEkn1tF2N0JckFZ7iqUaiFygF /xpM2WX3CC/8UpH0idI/q71XL1wq8DAPotlYNAAjAu5wSMuIrpucxlzNGbC3wCrlVmq1QF+S sl9pS0eB+lxcXkzPS1IuFn0FHurhfu5+dRUotYCRr3kl1S3zbnnpovmeVve6d+jl24SvAxxN PSMM4DVG73CUY/L874/qfj80DldLLvtq47LBDNISp9zMsV8jYbzY4Ln2TS63CkLaJLx5H32k 6GxAuKEFhzQm01m2mirRc/nG/8r5Qqprxn65KRWFJ8WGoTfUc/ert8CuBbc9jHn9cE3fjq3F 3RosUACF/5FK8wSgPEGQSLliZ0PpIUVI4VKNC/ZrN4G3l7dqqPDb5rffh1euHI61IwXAizkX HMrUk8+e9jWHkitkmrvM6akKd+HGp/WL90uiVB2eFB6GUvij98tXoEXZK3zNm28zY7UxvtIa aSjHFdFIGCzXAOeLvz7qY+PqZFdNylOlXMa6zv++Fd8s8JJX/zaGEvxgUlQbVue125MUvQXq DeWO8Pb9GinQUp0xS7N5HQUqYV+2MTaUu883dS0OlOlLD4PVBnCz8eubF6NxAABvctubRlny AwDwdyz9WyrNZxz4GrlFDAAAAAAAAAAAAAAAnsj0HQ7pN2xugT+Km/d7udnCW9Ve42Frw+rP ZIy/A3wxy+9Iq7m+/5C66O0N6NuvGWF8/xE720gvDVp2ONzdZs1BmffLbccvunvDwFOYfqUS fuD1As/zLM9q53+OrFMqSdWitnJXYPbmzbfPN5CK+gvcv1WWGmqTBtznN9i3rL9n1+5r3mUH JZ8E7PXquaRClFy+MPAgt/0sNsTgCY93XQCv9weXxV0u9yGMJ3s9V3O1UebyhYFn+Tc/zMpL 90r6ffjqNbRe4Ob0/Wq2RvNWrfE1qfYCN6R0Nn2/HJ3NV2CzLr3eaoFlapPUOMZcjjZs1ms/ Xu6WL1Ob7LONFIP+wEVKkjZOHN3GGKE+Y8e+eqDZvBKWC6hq3OHQH8Ip9+F7C1Sk8tMNiXKS kpKaJYecrZXWKOeFakNJc4q7QDt7806dPlIY5S4bW+P43Sy+AvW6Ustceo4+HBw900fpG779 8tXla/ljTkNVS7Ps8ue/L09Yur27eaWm8B0U97ScslfXK9XxpeTy1TVYIB5B+/P0zfE/fjni yPXtjnkhStI+ms1YbqA3b9RuKs1bnVnual6pNc7zzGcoe3iW3tu1s5al5BpSdTPmcceu7dNQ iq5IUiesDhxF7BFxh2EpM/3veJn4s7QFR9Pf7HwjM2PvLBZb4KMpe3oWf7dvsECf3Y5FGc+8 CO9t+WOD9Up+Yu69IXHErTwcYeR5lTKlDcJnwt3GEQLFf2nUchduE5vcu4udcf6gS2cDbuF7 kLF/GIwvRIlZcFzO3Km7z15trF8xTBp7+gRx18JokwXZxSWq/Ln14TouvsfJj34IvUnwUXUN jsrxMMqHDrHNa8xlDyOnXyJK48t3YanketCVKtx+jt99qNrb9KS0waXoao9RCryUKX1uT1IK 9ClvgTZbQwmgOnRHCjTGX+Zd2bzNHuVojTLg6mwbsstHceDsBY70+WokUmB62M0NLMFb6uo6 lEpdOqUuY5zV8KQC9TC66joMu9ybqxmGJX7j+JJylWEoqVNnbABYZP87DUav2REAf9mzX/wF vB73lgG8g+lvqQCP8+h7s+4b4wAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAKLP5/P5fO6OAkDDv5aN0mA+zzOkVqnAfNbIky6z iTFJKXAH4a1qr/GwtWF1Epcy2vfCvePfjGWuwQIdGR3lhAfvCyO2ZL1GaZf3MWlm23mXFc0u WqaGJzXDu73ATcLwFZhvEFig3T+WjcLHj17geZ7lWe38z5Htv5JULWordwVmb958+3wDqSiL vK9HXZW6WzLqEIyUE9gN5vUoqeRtB5fR0+NfIJ8fjt9jNjwpPAz2q8zVO+v6wpCYFhzbGlxP cCf2Ro4Dt/PysenRwfus2WX75dqCwX7LUQ5cuF+Cv7RtfsoJT8orLT8ZKfBSzmv2q6vASwsY +ZpX8W95xVntc83SU66ykMsnDz3H6/vVbI3mzVu9lRwF7k/paeVOOfZXasNqqrE0pWM3Pyw/ b1aX9B5lKdqytGaP8g3Yaml6XfmH9mWEsWXsl3rjM5vegNJBsSdJhRubVw/yufOJ7qHnnUBl 9wgv/FJR+UnjDoc07PPbLL4bPpaNv1L5aUFXDhUpqVlyyOhSWqNcyVUbqjpzjRRoZ2/e8W56 ucIoI1G6k/uMWy3T0VuMleoLUHs5h2t8KWFIpaVPYhuqmkWpK9/l8KNjXCweYy1fDVgp0Jek 7JexeR1dVBn+4UnKtOwr8FAP93P3q6vAwTHla96S9qXRZim9ZyDfPpcn4zSffilJ+2g2ozT3 OQrsojRvdeUxUq9+Lhlf0BjLnLTaCC/T3SBRzTuvoVayrzYuG8xgHObfkSKNxDyj7+g8/Zh2 eUc3DnG5lghpk67mNf1KRfI3D+GycW7Z+DWHIG/VwOl+Rvssm78mXeLPO5tuyHewVg4rqa60 5qhus/gkqlQUnhQbht5Qz92v3gK7Ftz2MHqLiv/SqHQrL7yicfptomX+4GkAWCB28lk/s0mP P3aeVMcFTstbNVT46eb285fUvMpIiVlwXPY81Tf7eK9v8UsjRtHXHHd1rNs7dKCofZnUAZqV vuZALBMy+YTPbMqhzJPyf89Y6Bh7lFJ1eFJ4GErhj94vX4EWZa/wNW++zWWzn7y48hG7JSmv 4BJ9+blS4KVM6XN7klKgj9LcUhhKANUJZaRAY/xl3mXNq2/v6xtKkmW/qnXp8ZfHSz+U4cHr 4UlhNMdyb66R/erq8z4f9RF1+Mx2RI8vZQaw7FdXXUrwi5MUvQXqDeWO8Pb9GinQUp0xS7N5 lQIBYBfG62+UaDrs7Nkv/gLwDpwpgdf7uTsAADiO6AegfxANCAAAAAAAAOCLR7wAADzX/79p 1PcLFuW3MY4CeQYJAMArDf1KJfaWQ1qgXN5tAAAA/rTAxxxlUfknPE8BAODR/vdI5fKOwvzD 9Ca+4/dbxsrN8nKrBR7FfQvjcxMerwAA8Gj/e6TSfOF8+QrnlCX/9yXvRf7QRHpuws0MAADe x/QdDm4wAACAEf+2N/nPmmUHixsAAN6Hv6UCAACmi1lwjH/x4vKVDv6sLQAAb/K/P94m/cH7 8sMLy69Ryl++SMXy4i8AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAA0M+XXQAACb9JREFUAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAACD6+f7n8/mkj87z HCw0L00q8LvNJckdRrU0S4F6xvzzy05dytR32bdf1VyXwPL/HYnQ7fP5hBSVwosKbJNKZ1Qh HUq9A1yyW+JpBh+4d4NFObLf0uVuVw7YG4eeMk/qqU88ZH+zv138k//PeZ5RE8f5n6M2D1Zn xjyjtI1So6NAPWNVvl/Viqp1+Ro2ZdEXUtXteyP0CSnk65ZBuKDS8CqMna25RLBoBh+4d4NF 9WZvrtRfybgkvSUMvWO7zw77+MvrjOSf9iadmidXvbelQqQtLaVZCuxdbYSsxgI1G8cxBT9x GL9beVCUfugben/cVoP6L3BMsO6zA3bz79TSpQcT53lGdRdf51PCeFBvVoL83jidN5lWLz6q qV13TZUy9TDyo5Zy2e/QlvWW9z+VJMt+Oe4hN9kfjhxjQ6+rokPdL18HcBxKO+NB0TuAxNdF BzubEkYZQ7mZZSz7WuP43Q56tOPTl68fOpKarWG8vn398jf+DkeirDb0XLEn+7LA8d4srbiX 3SSYcSHbtUDJNy4zWu6LKvOO4wDlLf/9h/EObblfx+/lmnLCuNSo75evNeyXfXrqYJ/vWoUr ++XrAL5D2YywWrtSl9IBjJXau+hgZyvpAzaVXBYoVaSMlEH6eshei68f+pL01pD2yHcoH23W HY7mIjr92z0JDnKHUd21/H+XrTmkipSkNfTAUmsr3aOrV6T9Ne54yNnXlzHf/TyYXl2rjWpd vUOvGvygrg4QtTY9fneYrowpuyNLVxdt1jVjgDen6wXGrwaT5mxjXKgNhqHskWU+fJkpCw79 8tG+TQhfGJLA8TBOX3MsDibRLwHTGDu2aUafqOAd5ThWGyN9fhO7BbwyngXzZJX7ds54dVW+ leWyc43Da+ZDo/hHKn+n7V6m63blCP3+4R+5tWhUHpTXjy86wN80qWPv/7Ri/wgDTfwOx5fx NCY9LXMUZS9whtefD6qMhybfjDXHhW/Bt2yZOIMUvN4BHr3L4d7abZS5wjjHGmebQ22NqQ1l iXD/I9Ul/sVfygxS3UZ6nq18xUavrrfAS6qlQGNRxlSJEl71f+0xdIVhDLLa7OXDcimM6sCz zCmXWpSbwFERVgOz1NWVJGmOL73peruiHqFlIBuT9A7gO5SWnbIfypFR3NtF543lcsAaW14a KV0Dtgz+EJriEuThav/wUdlM8rWhsl/2hgXwPC+7pACATUx/pAIAAPBzdwDARgKfLQIAAAAA AAAAgAXyry7yNUYAqGKqfJD/vWk09tG15Vdbzd+4On7r5fg9qv4jpWrGsq4ZP+iKVf3xamCx 4SVDMulQ+vQGs1Xwx3F8gt7UPrhfShib/CoyqqF2oxy4qJZv9o3Fg6I8lJYAolrj169U0ivP RqTIlBeoVc/QeUZpG6VGR4FSxvM3S5bj9y5Xk9SdmGtG7b7jxSXIoK3m/d5gtgo+sB+O7Nf+ w2H/CN0WdMhmFSsHheWKeqr4n8U2T676aiMVIm1pKc1SoGMU6QuU3tJ0lwK3mqmPgePVu5pU ar/dyjA22WWfRwd/r9uvVfY3aaqk5XNRrTHrr8V+SU8fzrg/Z+o7gfnCCDlZ9lZ3FEPI9yK8 yza9uQKdY393tFw15sfx8nSsmnQMt2G5mZRLeTmju64yqVngjIYyMl4SNF/U2IzwdL1pVB8O 9qGn7JovjOP3rkkf2nuUpYsqpXXdVPeNL/eolKbKriCrSb651zjxdoU3OCqNh9LeD31hTHzx l7La0HPFntHLApthfDKO6vTCB+UPMi4LICUpz+7IpcfjaCX30k26s1IGX06gll02toZ0Ruxq Q19dvjCU1lDacLBvKMGX/VBhjNA+9FI5l3/nn5ThjR+vrjCaheRD7/uP8Y7dG6EUmCOM8OCN QVZT9eFWDaMZXlfktxxKaVQ6WkMy6w5Hc5ZM/zZ24nDVMC7BfIe0PcLZq41LRbpqGHe1duns v8/ha96RXdZHWr5Zvi/GGi257KuNy+dKpZbY7AU2M27eD0vS/g4er1hn8cdZLjHcqNlQvdOX b3wp3DOJEoZxp7omPWnhEtsaecldGzvCmLLgkA5n/ollmxC+MByWzTXLarFwR9LbXIPNG9Vi Sr9NV5z2uvRc8xZYvTNLVwBfK4dDoDzscrr3HeXFdghMbyhHhJu0vBSG3m1GqusKYzFHGPGP VG5vBexv8WojSvM2rGPGkXI1dzl8dgu0yfGaQT/KOx+UxXzDYWWBhLE+jOl/vC2tgHSXoKsT lrEoe4HuaPehBDx1X3zN69jYsX2gvA2VMPLN7MNPyWXcZb2u8A5gLPBxqw37flmOsvs0cNfx Ci/QPhyM05dvfIW7MYzw1hjvG74wflLm9NHgTKEMwuo25Y0pKQxpFaLUZSnwknopUCpNSpVO SEoYvewRljuV9wzLLtsjmbTaOFpf9GnucrU6Xxs6wiiTpCCNdfkOpX1kdfUNaQQNBn8W3wB1 R6i7xGMMo6xL3y9fGIfcvJfYysYpcxmTyl3WI2zukS+MriQffZctZygpyd5txuuqFqgrD2Wz 9zoiBN5pfKm+0rOifRbaFtjc3PdwAEgcd3egM95WzC1u/03CCPfW/cJUP3cHAPjFPquagbuO s+3fBwAAAAAAAAAAAAAAAAAAAAAAAAAAUX7c76AcT1JeZhf4MkEAAHC7H+X9Lb1vF24m5dwl 8PYkAAAe539vGi3fzJ9Ifxvl+yLh74k/P/0rSVJpFry0GACA52q/2ly6l5AWFuU2UpLyR4bc YQAAgP0N/Xn68zyl1YOSBAAA/pqOBUf+xxjzf18WFkpSiOrfhOQPRQIAsLOfy1c3Lt8Vnfcr la6fojR/pcI3SQEAQB9uVwAA8DJD3+EIxCIDAIAX+7k7gP+nvBMMAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAADz+D2AdaNOyuipZAAAAAElFTkSuQmCC --------------050000060501030900090607 Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users --------------050000060501030900090607-- From xen-users-bounces@lists.xen.org Fri Sep 21 15:23:48 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Fri, 21 Sep 2012 15:23:48 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TF53v-0000vv-Q9; Fri, 21 Sep 2012 15:22:39 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TF53t-0000vq-Qo for xen-users@lists.xen.org; Fri, 21 Sep 2012 15:22:38 +0000 Received: from [85.158.137.99:29856] by server-11.bemta-3.messagelabs.com id 3D/8A-30250-C368C505; Fri, 21 Sep 2012 15:22:36 +0000 X-Env-Sender: gu99roax@student.chalmers.se X-Msg-Ref: server-12.tower-217.messagelabs.com!1348240955!15504125!1 X-Originating-IP: [213.199.154.143] X-SpamReason: No, hits=0.5 required=7.0 tests=BODY_RANDOM_LONG X-StarScan-Received: X-StarScan-Version: 6.6.1.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 10158 invoked from network); 21 Sep 2012 15:22:35 -0000 Received: from db3ehsobe005.messaging.microsoft.com (HELO db3outboundpool.messaging.microsoft.com) (213.199.154.143) by server-12.tower-217.messagelabs.com with AES128-SHA encrypted SMTP; 21 Sep 2012 15:22:35 -0000 Received: from mail75-db3-R.bigfish.com (10.3.81.228) by DB3EHSOBE004.bigfish.com (10.3.84.24) with Microsoft SMTP Server id 14.1.225.23; Fri, 21 Sep 2012 15:22:34 +0000 Received: from mail75-db3 (localhost [127.0.0.1]) by mail75-db3-R.bigfish.com (Postfix) with ESMTP id D55F22A011D for ; Fri, 21 Sep 2012 15:22:34 +0000 (UTC) X-Forefront-Antispam-Report: CIP:207.46.4.203; KIP:(null); UIP:(null); IPV:NLI; H:SN2PRD0102HT027.prod.exchangelabs.com; RD:none; EFVD:NLI X-SpamScore: -3 X-BigFish: PS-3(zz98dI1503M936eI1432Id6f1izz1d18h1202h1d1ah1d2ah1082kzz17326ah8275bh8275dh177df4h172cdfhc704dhz2dh2a8h668h839h8e2h8e3hd25hf0ah107ah10d2h1288h12a5h12a9h12bdh137ahbe9i1155h) Received: from mail75-db3 (localhost.localdomain [127.0.0.1]) by mail75-db3 (MessageSwitch) id 1348240952658676_12430; Fri, 21 Sep 2012 15:22:32 +0000 (UTC) Received: from DB3EHSMHS012.bigfish.com (unknown [10.3.81.252]) by mail75-db3.bigfish.com (Postfix) with ESMTP id 93114400142 for ; Fri, 21 Sep 2012 15:22:32 +0000 (UTC) Received: from SN2PRD0102HT027.prod.exchangelabs.com (207.46.4.203) by DB3EHSMHS012.bigfish.com (10.3.87.112) with Microsoft SMTP Server (TLS) id 14.1.225.23; Fri, 21 Sep 2012 15:22:29 +0000 Received: from [10.40.137.93] (217.208.204.161) by pod51000.outlook.com (10.27.90.95) with Microsoft SMTP Server (TLS) id 14.15.108.4; Fri, 21 Sep 2012 15:22:28 +0000 Message-ID: <505C8630.2090002@student.chalmers.se> Date: Fri, 21 Sep 2012 17:22:24 +0200 From: Robin Axelsson User-Agent: Mozilla/5.0 (Windows NT 5.2; WOW64; rv:9.0) Gecko/20111222 Thunderbird/9.0.1 MIME-Version: 1.0 To: References: <505B86AE.9040507@earthlink.net> In-Reply-To: <505B86AE.9040507@earthlink.net> X-Originating-IP: [217.208.204.161] X-OriginatorOrg: student.chalmers.se Subject: Re: [Xen-users] Recommendations for Virtulization Hardware X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list Reply-To: gu99roax@student.chalmers.se List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset="us-ascii"; Format="flowed" Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org If you want to be able to use PCI and VGA passthrough you basically need to make sure that your hardware supports either AMD-Vi (formerly known as AMD-IOMMU) or Intel VT-d extensions. In the Intel case it limits your choice of Motherboard (it must be supported in the BIOS) and CPU. In the AMD case it limits only your choice of motherboard. A good start is to check out one of these pages: http://wiki.xensource.com/xenwiki/VTdHowTo http://wiki.xen.org/wiki/VTd_HowTo A word of warning here is that parts of the documentation is somewhat dated. You can also communicate with e.g. Gigabyte, Asus or ASRock customer support and ask them if a particular motherboard supports these extensions. Most motherboards also have downloadable user manuals, if the BIOS settings in those pages shows options to enable/disable VT-d or AMD-Vi/IOMMU extensions then you will be ok with that motherboard. The other thing is choice of GPU for VGA passthrough and it is preferable that the GPU supports FLR or Function Level Reset as it is called. Thing is that the hardware needs to be reset somehow as it is passed through to the host. This is best done with FLR and nVidia is known to supply firmware patches for some of their Geforce cards with this support and it is said to be supported by default with their Quadro cards. FLR is not the only way to reset a PCI device, a reset could be trigged through the ACPI power management framework by temporarily cutting power to the affected PCI slot. These reset methods are called d3d0 and bus reset. The question however, is if this works on PCI cards that use auxiliary power directly from the PSU. There is a pdf document on the VMWare website (http://www.vmware.com/files/pdf/techpaper/vsp_4_vmdirectpath_host.pdf) about this: ----------------------- Reset Method Possible values for the reset method include flr, d3d0, link, bridge, or default. The default setting is described as follows. If a device supports function level reset (FLR), ESX always uses FLR. If the device does not support FLR, ESX next defaults to link reset and bus reset in that order. Link reset and bus reset might prevent some devices from being assigned to different virtual machines, or from being assigned between the VMkernel and virtual machines. In the absence of FLR, it is possible to use PCI Power Management capability (D3 to D0 transitions) to trigger a reset. Most of the Intel NICs and various other HBAs support this mode. ----------------------- There are indications from people that d3d0 also work with PCI cards that take power from auxiliary inputs. I suggest that you take a look at the following youtube clip and read the comments there: http://www.youtube.com/watch?v=Gtmwnx-k2qg So it seems that it works although it may be a bit more quirky. It doesn't hurt to take that discussion (particularly about FLR support) with nVidia and/or AMD. When it comes to virtualization, the technology has come very far, but it is still lacking considerably when it comes to sharing GPUs and also to some degree when it comes to sharing I/O devices (especially when you intend to run many virtual machines on a single system). The GPU today consists of three types of components; the processing unit, graphics memory and the video output unit/adapter and it is not clear as to how to share these components seamlessly between the host and virtual machines with minimal overhead. Whereas there are VT-x extensions that allows you to pretty seamlessly share CPU cores between VMs and the host there are currently none for the processing unit. It is also not clear how the hardware can assist with sharing TV/monitor screen estate between machines with all 3D effects such as Aqua for Win7 and the whatnot enabled for all machines. Especially when considering the dynamics of plugging and unplugging computer monitors to multiport/eyefinity graphics cards and the ability to change screen resolution. Things are improving for sure and a lot of research is likely going into this. I don't know what's happening in the GPU frontline but I know that the next thing with passthrough is the SR-IOV that allows PCI units to present several virtual instances of oneself to several virtual machines. It's a cool thing, I recommend further reading about this here: http://www.intel.com/content/www/us/en/pci-express/pci-sig-sr-iov-primer-sr-iov-technology-paper.html http://blog.scottlowe.org/2009/12/02/what-is-sr-iov/ It is likely to take a few years before something useful will come out of it. In the meanwhile, unless you want to use several GPUs which might not be a bad thing as a lot of monitors these days have several inputs, you can resort to using a remote desktop client to integrate one machine with another. Virtualbox for example use RDP through which you can interact with your virtual machine. In a similar manner you can set up a VNC server on your Linux host and establish a connection to it through your Windows VM. You will not get full 3D functionality (such as Aqua) through the client although there is a growing support for it through VirtualGL extensions that are coming to VNC and perhaps the Spice protocol. But some clients might even allow for seamless mode that lets you mix Linux and Windows windows on the same desktop like this for example: http://i.techrepublic.com.com/blogs/seamless.png http://www.youtube.com/watch?v=eQr8iI0yZH4 Just keep in mind that this is still a little bit of uncharted territory so there may be a few bumps on the way and it may not work as smooth as you would desire. I see that your demands are somewhat multifaceted. I believe that you also want to use diffent services such as using your machine as a file server with the possible intention of using filesystems such as ZFS. If you do, you should be careful with your selection of hardware for these particular purposes. If you want to get full protection against data corruption from ZFS, your choice of hardware gets rather limited when it comes to choice of hard drives, host bus adapter and network controller. The most stable implementation of ZFS is found with Illumos based operating systems (such as OpenIndiana, SmartOS, OmniOS, Belenix etc) or Solaris if you choose to download it from Oracle's website. With these operating systems you are most likely to want to use hardware that has certified drivers for it. That way you are less likely to run into problems later on. That implies that you will be limited to choosing Intel based network adapters and LSI based SAS controllers. There should be _no_ hardware RAID functionality in the SAS controller that merely should be run in IT mode (or Initiator-Target mode). That requires the LSI controller to be flashed with IT firmware in most cases. The objective here is to make sure that _all_ errors that might occur with the hard drives are reported all the way to the software level and that nothing is concealed of obfuscated by internal error handling in the hardware. It is therefore recommended to use SAS hard drives instead of S-ATA (which also are fully compatible with SAS controllers). SAS hard drives are not much more expensive than similar SATA drives and you get a higher reliability out of them. It is also recommended to have at least two drive redundancy simply because if one drive is dead and you swap it, it is not uncommon that another drive dies in the rebuild process of the RAID cluster because of the added strain the rebuild process (or 'resilvering' as it is called in Solaris terms) put on the drives. Of course, the system should communicate directly to the hard drive hardware and not be obfuscated by some virtual abstraction layer in between which means that you either run ZFS on the metal or through PCI passthrough of the SAS (and perhaps also network) adapters. Also, it is highly recommended that you use ECC RAM for such applications and it doesn't hurt to dedicate a few gigs of it to the ZFS as RAM is used for cache. The good news is that most motherboards with good chipsets support ECC RAM even though you might not find anything about it in the user manuals. I admire your persistence with pursuing this undertaking and wish you the best of luck with it! Robin. On 2012-09-20 23:12, ShadesOfGrey wrote: > I'm looking to build a new personal computer. I want it to function > as a Linux desktop, provide network services for my home, and lastly, > occasional Windows gaming. From what I've gathered, virtualization > using a Type 1 Hypervisor supporting PCI/VGA pass-through like KVM or > Xen would be an attractive solution for my needs. For reference, > reading these threads on Ars Technica may be helpful to understand > where I'm coming from, > http://arstechnica.com/civis/viewtopic.php?f=6&t=1175674 and > http://arstechnica.com/civis/viewtopic.php?f=11&t=1181867. But > basically, I use Linux as my primary OS and would rather avoid dual > booting or building two boxes just to play Windows games when I want > to play Windows games. I'm also intrigued by the concept of > virtualization and would like to experiment with it as a solution for > my case. > > My problem is isolating which hardware to choose, specifically which > combination of CPU, motherboard and video card. Previously I had been > relying on web searches to glean information from gaming and > enthusiast web sites and tech specs from motherboard manufacturers. > After what I learned during my participation in the referenced threads > at Ars Technica, I find myself back at square one. Instead of trying > to guess what hardware support KVM & Xen, and vice versa. I'd like to > know what hardware KVM & Xen users are actually using to run KVM & > Xen? Particularly with consideration for 3D gaming and current > generation hardware, BTW. > > If there is need for further clarification, I'll answer any queries > you might have. > > _______________________________________________ > Xen-users mailing list > Xen-users@lists.xen.org > http://lists.xen.org/xen-users > > _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Fri Sep 21 15:23:48 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Fri, 21 Sep 2012 15:23:48 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TF53v-0000vv-Q9; Fri, 21 Sep 2012 15:22:39 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TF53t-0000vq-Qo for xen-users@lists.xen.org; Fri, 21 Sep 2012 15:22:38 +0000 Received: from [85.158.137.99:29856] by server-11.bemta-3.messagelabs.com id 3D/8A-30250-C368C505; Fri, 21 Sep 2012 15:22:36 +0000 X-Env-Sender: gu99roax@student.chalmers.se X-Msg-Ref: server-12.tower-217.messagelabs.com!1348240955!15504125!1 X-Originating-IP: [213.199.154.143] X-SpamReason: No, hits=0.5 required=7.0 tests=BODY_RANDOM_LONG X-StarScan-Received: X-StarScan-Version: 6.6.1.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 10158 invoked from network); 21 Sep 2012 15:22:35 -0000 Received: from db3ehsobe005.messaging.microsoft.com (HELO db3outboundpool.messaging.microsoft.com) (213.199.154.143) by server-12.tower-217.messagelabs.com with AES128-SHA encrypted SMTP; 21 Sep 2012 15:22:35 -0000 Received: from mail75-db3-R.bigfish.com (10.3.81.228) by DB3EHSOBE004.bigfish.com (10.3.84.24) with Microsoft SMTP Server id 14.1.225.23; Fri, 21 Sep 2012 15:22:34 +0000 Received: from mail75-db3 (localhost [127.0.0.1]) by mail75-db3-R.bigfish.com (Postfix) with ESMTP id D55F22A011D for ; Fri, 21 Sep 2012 15:22:34 +0000 (UTC) X-Forefront-Antispam-Report: CIP:207.46.4.203; KIP:(null); UIP:(null); IPV:NLI; H:SN2PRD0102HT027.prod.exchangelabs.com; RD:none; EFVD:NLI X-SpamScore: -3 X-BigFish: PS-3(zz98dI1503M936eI1432Id6f1izz1d18h1202h1d1ah1d2ah1082kzz17326ah8275bh8275dh177df4h172cdfhc704dhz2dh2a8h668h839h8e2h8e3hd25hf0ah107ah10d2h1288h12a5h12a9h12bdh137ahbe9i1155h) Received: from mail75-db3 (localhost.localdomain [127.0.0.1]) by mail75-db3 (MessageSwitch) id 1348240952658676_12430; Fri, 21 Sep 2012 15:22:32 +0000 (UTC) Received: from DB3EHSMHS012.bigfish.com (unknown [10.3.81.252]) by mail75-db3.bigfish.com (Postfix) with ESMTP id 93114400142 for ; Fri, 21 Sep 2012 15:22:32 +0000 (UTC) Received: from SN2PRD0102HT027.prod.exchangelabs.com (207.46.4.203) by DB3EHSMHS012.bigfish.com (10.3.87.112) with Microsoft SMTP Server (TLS) id 14.1.225.23; Fri, 21 Sep 2012 15:22:29 +0000 Received: from [10.40.137.93] (217.208.204.161) by pod51000.outlook.com (10.27.90.95) with Microsoft SMTP Server (TLS) id 14.15.108.4; Fri, 21 Sep 2012 15:22:28 +0000 Message-ID: <505C8630.2090002@student.chalmers.se> Date: Fri, 21 Sep 2012 17:22:24 +0200 From: Robin Axelsson User-Agent: Mozilla/5.0 (Windows NT 5.2; WOW64; rv:9.0) Gecko/20111222 Thunderbird/9.0.1 MIME-Version: 1.0 To: References: <505B86AE.9040507@earthlink.net> In-Reply-To: <505B86AE.9040507@earthlink.net> X-Originating-IP: [217.208.204.161] X-OriginatorOrg: student.chalmers.se Subject: Re: [Xen-users] Recommendations for Virtulization Hardware X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list Reply-To: gu99roax@student.chalmers.se List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset="us-ascii"; Format="flowed" Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org If you want to be able to use PCI and VGA passthrough you basically need to make sure that your hardware supports either AMD-Vi (formerly known as AMD-IOMMU) or Intel VT-d extensions. In the Intel case it limits your choice of Motherboard (it must be supported in the BIOS) and CPU. In the AMD case it limits only your choice of motherboard. A good start is to check out one of these pages: http://wiki.xensource.com/xenwiki/VTdHowTo http://wiki.xen.org/wiki/VTd_HowTo A word of warning here is that parts of the documentation is somewhat dated. You can also communicate with e.g. Gigabyte, Asus or ASRock customer support and ask them if a particular motherboard supports these extensions. Most motherboards also have downloadable user manuals, if the BIOS settings in those pages shows options to enable/disable VT-d or AMD-Vi/IOMMU extensions then you will be ok with that motherboard. The other thing is choice of GPU for VGA passthrough and it is preferable that the GPU supports FLR or Function Level Reset as it is called. Thing is that the hardware needs to be reset somehow as it is passed through to the host. This is best done with FLR and nVidia is known to supply firmware patches for some of their Geforce cards with this support and it is said to be supported by default with their Quadro cards. FLR is not the only way to reset a PCI device, a reset could be trigged through the ACPI power management framework by temporarily cutting power to the affected PCI slot. These reset methods are called d3d0 and bus reset. The question however, is if this works on PCI cards that use auxiliary power directly from the PSU. There is a pdf document on the VMWare website (http://www.vmware.com/files/pdf/techpaper/vsp_4_vmdirectpath_host.pdf) about this: ----------------------- Reset Method Possible values for the reset method include flr, d3d0, link, bridge, or default. The default setting is described as follows. If a device supports function level reset (FLR), ESX always uses FLR. If the device does not support FLR, ESX next defaults to link reset and bus reset in that order. Link reset and bus reset might prevent some devices from being assigned to different virtual machines, or from being assigned between the VMkernel and virtual machines. In the absence of FLR, it is possible to use PCI Power Management capability (D3 to D0 transitions) to trigger a reset. Most of the Intel NICs and various other HBAs support this mode. ----------------------- There are indications from people that d3d0 also work with PCI cards that take power from auxiliary inputs. I suggest that you take a look at the following youtube clip and read the comments there: http://www.youtube.com/watch?v=Gtmwnx-k2qg So it seems that it works although it may be a bit more quirky. It doesn't hurt to take that discussion (particularly about FLR support) with nVidia and/or AMD. When it comes to virtualization, the technology has come very far, but it is still lacking considerably when it comes to sharing GPUs and also to some degree when it comes to sharing I/O devices (especially when you intend to run many virtual machines on a single system). The GPU today consists of three types of components; the processing unit, graphics memory and the video output unit/adapter and it is not clear as to how to share these components seamlessly between the host and virtual machines with minimal overhead. Whereas there are VT-x extensions that allows you to pretty seamlessly share CPU cores between VMs and the host there are currently none for the processing unit. It is also not clear how the hardware can assist with sharing TV/monitor screen estate between machines with all 3D effects such as Aqua for Win7 and the whatnot enabled for all machines. Especially when considering the dynamics of plugging and unplugging computer monitors to multiport/eyefinity graphics cards and the ability to change screen resolution. Things are improving for sure and a lot of research is likely going into this. I don't know what's happening in the GPU frontline but I know that the next thing with passthrough is the SR-IOV that allows PCI units to present several virtual instances of oneself to several virtual machines. It's a cool thing, I recommend further reading about this here: http://www.intel.com/content/www/us/en/pci-express/pci-sig-sr-iov-primer-sr-iov-technology-paper.html http://blog.scottlowe.org/2009/12/02/what-is-sr-iov/ It is likely to take a few years before something useful will come out of it. In the meanwhile, unless you want to use several GPUs which might not be a bad thing as a lot of monitors these days have several inputs, you can resort to using a remote desktop client to integrate one machine with another. Virtualbox for example use RDP through which you can interact with your virtual machine. In a similar manner you can set up a VNC server on your Linux host and establish a connection to it through your Windows VM. You will not get full 3D functionality (such as Aqua) through the client although there is a growing support for it through VirtualGL extensions that are coming to VNC and perhaps the Spice protocol. But some clients might even allow for seamless mode that lets you mix Linux and Windows windows on the same desktop like this for example: http://i.techrepublic.com.com/blogs/seamless.png http://www.youtube.com/watch?v=eQr8iI0yZH4 Just keep in mind that this is still a little bit of uncharted territory so there may be a few bumps on the way and it may not work as smooth as you would desire. I see that your demands are somewhat multifaceted. I believe that you also want to use diffent services such as using your machine as a file server with the possible intention of using filesystems such as ZFS. If you do, you should be careful with your selection of hardware for these particular purposes. If you want to get full protection against data corruption from ZFS, your choice of hardware gets rather limited when it comes to choice of hard drives, host bus adapter and network controller. The most stable implementation of ZFS is found with Illumos based operating systems (such as OpenIndiana, SmartOS, OmniOS, Belenix etc) or Solaris if you choose to download it from Oracle's website. With these operating systems you are most likely to want to use hardware that has certified drivers for it. That way you are less likely to run into problems later on. That implies that you will be limited to choosing Intel based network adapters and LSI based SAS controllers. There should be _no_ hardware RAID functionality in the SAS controller that merely should be run in IT mode (or Initiator-Target mode). That requires the LSI controller to be flashed with IT firmware in most cases. The objective here is to make sure that _all_ errors that might occur with the hard drives are reported all the way to the software level and that nothing is concealed of obfuscated by internal error handling in the hardware. It is therefore recommended to use SAS hard drives instead of S-ATA (which also are fully compatible with SAS controllers). SAS hard drives are not much more expensive than similar SATA drives and you get a higher reliability out of them. It is also recommended to have at least two drive redundancy simply because if one drive is dead and you swap it, it is not uncommon that another drive dies in the rebuild process of the RAID cluster because of the added strain the rebuild process (or 'resilvering' as it is called in Solaris terms) put on the drives. Of course, the system should communicate directly to the hard drive hardware and not be obfuscated by some virtual abstraction layer in between which means that you either run ZFS on the metal or through PCI passthrough of the SAS (and perhaps also network) adapters. Also, it is highly recommended that you use ECC RAM for such applications and it doesn't hurt to dedicate a few gigs of it to the ZFS as RAM is used for cache. The good news is that most motherboards with good chipsets support ECC RAM even though you might not find anything about it in the user manuals. I admire your persistence with pursuing this undertaking and wish you the best of luck with it! Robin. On 2012-09-20 23:12, ShadesOfGrey wrote: > I'm looking to build a new personal computer. I want it to function > as a Linux desktop, provide network services for my home, and lastly, > occasional Windows gaming. From what I've gathered, virtualization > using a Type 1 Hypervisor supporting PCI/VGA pass-through like KVM or > Xen would be an attractive solution for my needs. For reference, > reading these threads on Ars Technica may be helpful to understand > where I'm coming from, > http://arstechnica.com/civis/viewtopic.php?f=6&t=1175674 and > http://arstechnica.com/civis/viewtopic.php?f=11&t=1181867. But > basically, I use Linux as my primary OS and would rather avoid dual > booting or building two boxes just to play Windows games when I want > to play Windows games. I'm also intrigued by the concept of > virtualization and would like to experiment with it as a solution for > my case. > > My problem is isolating which hardware to choose, specifically which > combination of CPU, motherboard and video card. Previously I had been > relying on web searches to glean information from gaming and > enthusiast web sites and tech specs from motherboard manufacturers. > After what I learned during my participation in the referenced threads > at Ars Technica, I find myself back at square one. Instead of trying > to guess what hardware support KVM & Xen, and vice versa. I'd like to > know what hardware KVM & Xen users are actually using to run KVM & > Xen? Particularly with consideration for 3D gaming and current > generation hardware, BTW. > > If there is need for further clarification, I'll answer any queries > you might have. > > _______________________________________________ > Xen-users mailing list > Xen-users@lists.xen.org > http://lists.xen.org/xen-users > > _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Fri Sep 21 15:32:31 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Fri, 21 Sep 2012 15:32:31 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TF5CN-0001BM-6B; Fri, 21 Sep 2012 15:31:23 +0000 Received: from mail27.messagelabs.com ([193.109.254.147]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TF5CM-0001BG-9p for xen-users@lists.xen.org; Fri, 21 Sep 2012 15:31:22 +0000 X-Env-Sender: rulerof@gmail.com X-Msg-Ref: server-10.tower-27.messagelabs.com!1348241473!6730587!1 X-Originating-IP: [209.85.216.52] X-SpamReason: No, hits=0.4 required=7.0 tests=HTML_50_60,HTML_MESSAGE, ML_RADAR_SPEW_LINKS_14,RCVD_BY_IP,spamassassin: X-StarScan-Received: X-StarScan-Version: 6.6.1.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 18486 invoked from network); 21 Sep 2012 15:31:14 -0000 Received: from mail-qa0-f52.google.com (HELO mail-qa0-f52.google.com) (209.85.216.52) by server-10.tower-27.messagelabs.com with RC4-SHA encrypted SMTP; 21 Sep 2012 15:31:14 -0000 Received: by qabg24 with SMTP id g24so769654qab.11 for ; Fri, 21 Sep 2012 08:31:13 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=references:from:in-reply-to:mime-version:date:message-id:subject:to :cc:content-type; bh=ZELbBrTmXoCPrlky+guY6yhCMx0A13oRwKAWftOzBss=; b=gCLQbK3RRyyO4yGZ0Y7ucaqc0pPjx42qQrCphGypoc6ZhHbNZixO8JeQs1Pv+fY8+v pHH6UreFHryYyMRy2LsWqQweoXCAbDee2q8cjsQbE8JAvp6ppakYbfyHiORySBmce6zV aH6tZHL/oOD6GSNBE1/GD+91uhITogy1DM6+52LAD4yljEPxPzRXY+R+apSGyCOy/z2x U3fVP/caXsH4R8yyRftvjzADEO7N+bfjAOCQEZ5qDP4w1WsbUJxRN1skxU9ZqC34JkuO /rpVM9TdKNuwCSmwbMjnlaJiqNcQKex5NCs5199hUxTrN1rS6hcQfhsU/itMlLIrlCcx U2jw== Received: by 10.224.193.193 with SMTP id dv1mr13257432qab.29.1348241472974; Fri, 21 Sep 2012 08:31:12 -0700 (PDT) References: <002401cd97b5$5b49f260$11ddd720$@gmail.com> From: Andrew Bobulsky In-Reply-To: <002401cd97b5$5b49f260$11ddd720$@gmail.com> Mime-Version: 1.0 (1.0) Date: Fri, 21 Sep 2012 11:31:10 -0400 Message-ID: <-3027552229290597468@unknownmsgid> To: Marc Tousignant Cc: "xen-users@lists.xen.org" Subject: Re: [Xen-users] Need help with passing through USB hub or devices X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============5750461949487764283==" Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org --===============5750461949487764283== Content-Type: multipart/alternative; boundary=20cf300fb0dd116e4c04ca37eece --20cf300fb0dd116e4c04ca37eece Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: quoted-printable Hello Marc, On Sep 21, 2012, at 12:58 AM, Marc Tousignant wrote: So, I=92m getting further and further to completing my setup following the guides written about passthrough of PCIe video. I have the video display from the domU client going to the physical display, but I cannot get the keyboard to work, I haven=92t even connected = a mouse yet. I attempted to pass through the USB hubs outright, but that failed as the keyboard just stopped working. It would not respond in the domU and I could nolonger get the caps lock to light up. Reconnecting or changing ports had no effect. Attempting to add the usb hub afterwards using xl pci-attach failed as well. But this time, it did not even attach the device. TheOldMan ~ # xl pci-assignable-list 0000:00:0b.0 TheOldMan ~ # xl pci-attach 1 0000:00:0b.0 libxl: error: libxl_pci.c:960:do_pci_add: xc_assign_device failed TheOldMan ~ # xl pci-assignable-list 0000:00:0b.0 TheOldMan ~ # xl pci-list 1 Vdev Device 05.0 0000:01:00.0 06.0 0000:00:0f.1 The reason I am trying to pass through the usb hub is 2 fold: First off, I would prefer not having to go into the console to add my keyboard/mouse each time I start. Second, I cannot seem to get into the console to save my life. I have vnc setup for console, however after connecting, I can=92t type anything. That=92s not to say that the keyboard is useless. Ctrl+alt+1 and ctrl+alt+2 switch between =93serial0 console=94 and =93parallel0 console=94= in the vnc window. In the hopes that all it was that the echo was off, I attempted to enter the usb_add line for my keyboard to no effect. Trying to access the console from a ssh connection in putty also fails. TheOldMan ~ # xl console Office xenconsole: Could not read tty from store: No such file or directory The standard fix I found searching for this error was =93start xenconsoled= =94. Well here is what I say about that. TheOldMan ~ # ps augx | grep xenconsoled root 6146 0.0 0.0 25168 1052 ? SLl 20:08 0:00 /usr/sbin/xenconsoled --pid-file=3D/var/run/xenconsoled.pid root 6888 0.0 0.0 8148 880 pts/0 S+ 20:53 0:00 grep --colour=3Dauto xenconsoled Here is my config: name=3D"Office" firmware_override =3D "/usr/lib/xen/boot/hvmloader" builder=3D"hvm" vcpus=3D2 memory=3D2048 on_poweroff=3D"destroy" on_reboot=3D"restart" on_crash=3D"destroy" disk =3D [ 'tap:aio://images/xen_images/Office.img,hda,w', 'tap:aio://images/iso_images/en_windows_7_enterprise_with_sp1_x64_dvd_u_677= 651.iso,hdc:cdrom,r' ] #disk =3D [ 'tap:aio://images/xen_images/Office.img,hda,w' ] vif =3D [ 'mac=3D00:16:3E:33:5E:F9, bridge=3Dxenbr0' ] #vif =3D [ 'bridge=3Dxenbr0,type=3Dioemu,model=3De1000' ] boot=3D"dc" acpi=3D1 xen_platform_pci=3D1 viridian=3D1 stdvga=3D1 vnc=3D1 vnclisten=3D"192.168.1.102" vncconsole=3D1 vncconsole=3D1 vncdisplay=3D0 vncunused=3D1 vncpasswd=3D"" sdl=3D0 usb=3D1 usbdevice=3D"tablet" gfx_passthru=3D1 audio=3D1 pci =3D [ '01:00.0','00:0f.1' ] I can get more info if needed. I really want to get this project done. MarcT _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users Would you mind pasting us the contents of your Dom0's "lspci" output? It won't quite help me troubleshoot your inability to use the console, but you may need to pass multiple PCI devices to get USB to work. It's a bit of a maze of different controller devices, and you need to pass several in many scenarios. Cheers, Andrew Bobulsky --20cf300fb0dd116e4c04ca37eece Content-Type: text/html; charset=windows-1252 Content-Transfer-Encoding: quoted-printable
Hello Marc,

On Sep= 21, 2012, at 12:58 AM, Marc Tousignant <myrdhn@gmail.com> wrote:

So, I=92m get= ting further and further to completing my setup following the guides writte= n about passthrough of PCIe video.

I have the vid= eo display from the domU client going to the physical display, but I cannot= get the keyboard to work, I haven=92t even connected a mouse yet.

=A0

I attempted to pass th= rough the USB hubs outright, but that failed as the keyboard just stopped w= orking. It would not respond in the domU and I could nolonger get the caps = lock to light up. Reconnecting or changing ports had no effect.

Attempting to add the usb hub afterwards using xl pc= i-attach failed as well. But this time, it did not even attach the device.<= /p>

TheOldMan ~ # xl pci-a= ssignable-list

0000:00:0b.0

TheOldMan ~ # xl pci-attach 1 000= 0:00:0b.0

libxl: error= : libxl_pci.c:960:do_pci_add: xc_assign_device failed

TheOldMan ~ # xl pci-assi= gnable-list

0000:00:0b= .0

TheOldMan ~ # xl pc= i-list 1

Vdev Device

05.0 0000:01:00.0

06.0 0000:00:0f.1

=A0

The reason I am trying to pass through the usb hub i= s 2 fold:

=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0= =A0=A0 First off, I would prefer not having to go into the console to add m= y keyboard/mouse each time I start.

=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0 Second= , I cannot seem to get into the console to save my life.

=A0

I have vnc setup for console, however= after connecting, I can=92t type anything. That=92s not to say that the ke= yboard is useless. Ctrl+alt+1 and ctrl+alt+2 switch between =93serial0 cons= ole=94 and =93parallel0 console=94 in the vnc window. In the hopes that all= it was that the echo was off, I attempted to enter the usb_add line for my= keyboard to no effect.

=A0

Trying to access the c= onsole from a ssh connection in putty also fails.

TheOldMan ~ # xl console Office

xenconsole: Coul= d not read tty from store: No such file or directory

The standard fix I found searching for this error wa= s =93start xenconsoled=94. Well here is what I say about that.

TheOldMan ~ # ps augx | grep xenconsoled

root=A0=A0=A0=A0=A0 6146=A0 0.0=A0 0.0=A0 25168=A0 1052 ?=A0=A0=A0=A0=A0=A0= =A0 SLl=A0 20:08=A0=A0 0:00 /usr/sbin/xenconsoled --pid-file=3D/var/run/xen= consoled.pid

root=A0=A0=A0=A0=A0 6888=A0 0.0=A0 0= .0=A0=A0 8148=A0=A0 880 pts/0=A0=A0=A0 S+=A0=A0 20:53=A0=A0 0:00 grep --col= our=3Dauto xenconsoled

=A0

Here is my config:

=

=A0

name=3D"Office"

=A0

firmware_override =3D "/usr/lib/xen/boot/hvmloader"

builder=3D"hvm"

=A0

vcpus=3D2

=A0

memory=3D2048

=A0

on_poweroff=3D"destroy"

on_reboot=3D"restart= "

on_crash=3D&quo= t;destroy"

=A0

disk =3D [ 'tap:aio://images/xen_images/Office.img,hda,w', 'tap= :aio://images/iso_images/en_windows_7_enterprise_with_sp1_x64_dvd_u_677651.= iso,hdc:cdrom,r' ]

#disk =3D [ 'tap:aio://images/xen_images/Office.img,hda,w' ]

=A0

vif =3D [ 'mac=3D00:16:3E:33:5E:F9, bri= dge=3Dxenbr0' ]

#v= if =3D [ 'bridge=3Dxenbr0,type=3Dioemu,model=3De1000' ]

=A0

boot=3D"dc"

=A0

acpi=3D1

=A0

xen_platform_pci=3D1

=A0

viridian=3D1

=A0

stdvga=3D1

=A0

vnc=3D1

vnclisten=3D"192.168.1.102"

vncconsole=3D1

vncconsole=3D1

vncdisplay=3D0

vncunused=3D1

vncpasswd=3D""

sdl=3D0

=A0

usb=3D1

usbdevice=3D"tablet"

=A0

gfx_passthru=3D1

audio= =3D1

=A0

pci =3D [ '01:00.0','= 00:0f.1' ]

=A0

I can get more info if= needed. I really want to get this project done.

= =A0

MarcT

_______________________________________________
= Xen-users mailing list
Xen-users@lists.xen.org
http://lists.xen.org/xen-users

Would you mind pasting us the contents of your Dom0&#= 39;s "lspci" output?

It won't quite = help me troubleshoot your inability to use the console, but you may need to= pass multiple PCI devices to get USB to work. =A0It's a bit of a maze = of different controller devices, and you need to pass several in many scena= rios.=A0

Cheers,
Andrew Bobulsky
--20cf300fb0dd116e4c04ca37eece-- --===============5750461949487764283== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users --===============5750461949487764283==-- From xen-users-bounces@lists.xen.org Fri Sep 21 15:32:31 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Fri, 21 Sep 2012 15:32:31 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TF5CN-0001BM-6B; Fri, 21 Sep 2012 15:31:23 +0000 Received: from mail27.messagelabs.com ([193.109.254.147]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TF5CM-0001BG-9p for xen-users@lists.xen.org; Fri, 21 Sep 2012 15:31:22 +0000 X-Env-Sender: rulerof@gmail.com X-Msg-Ref: server-10.tower-27.messagelabs.com!1348241473!6730587!1 X-Originating-IP: [209.85.216.52] X-SpamReason: No, hits=0.4 required=7.0 tests=HTML_50_60,HTML_MESSAGE, ML_RADAR_SPEW_LINKS_14,RCVD_BY_IP,spamassassin: X-StarScan-Received: X-StarScan-Version: 6.6.1.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 18486 invoked from network); 21 Sep 2012 15:31:14 -0000 Received: from mail-qa0-f52.google.com (HELO mail-qa0-f52.google.com) (209.85.216.52) by server-10.tower-27.messagelabs.com with RC4-SHA encrypted SMTP; 21 Sep 2012 15:31:14 -0000 Received: by qabg24 with SMTP id g24so769654qab.11 for ; Fri, 21 Sep 2012 08:31:13 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=references:from:in-reply-to:mime-version:date:message-id:subject:to :cc:content-type; bh=ZELbBrTmXoCPrlky+guY6yhCMx0A13oRwKAWftOzBss=; b=gCLQbK3RRyyO4yGZ0Y7ucaqc0pPjx42qQrCphGypoc6ZhHbNZixO8JeQs1Pv+fY8+v pHH6UreFHryYyMRy2LsWqQweoXCAbDee2q8cjsQbE8JAvp6ppakYbfyHiORySBmce6zV aH6tZHL/oOD6GSNBE1/GD+91uhITogy1DM6+52LAD4yljEPxPzRXY+R+apSGyCOy/z2x U3fVP/caXsH4R8yyRftvjzADEO7N+bfjAOCQEZ5qDP4w1WsbUJxRN1skxU9ZqC34JkuO /rpVM9TdKNuwCSmwbMjnlaJiqNcQKex5NCs5199hUxTrN1rS6hcQfhsU/itMlLIrlCcx U2jw== Received: by 10.224.193.193 with SMTP id dv1mr13257432qab.29.1348241472974; Fri, 21 Sep 2012 08:31:12 -0700 (PDT) References: <002401cd97b5$5b49f260$11ddd720$@gmail.com> From: Andrew Bobulsky In-Reply-To: <002401cd97b5$5b49f260$11ddd720$@gmail.com> Mime-Version: 1.0 (1.0) Date: Fri, 21 Sep 2012 11:31:10 -0400 Message-ID: <-3027552229290597468@unknownmsgid> To: Marc Tousignant Cc: "xen-users@lists.xen.org" Subject: Re: [Xen-users] Need help with passing through USB hub or devices X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============5750461949487764283==" Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org --===============5750461949487764283== Content-Type: multipart/alternative; boundary=20cf300fb0dd116e4c04ca37eece --20cf300fb0dd116e4c04ca37eece Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: quoted-printable Hello Marc, On Sep 21, 2012, at 12:58 AM, Marc Tousignant wrote: So, I=92m getting further and further to completing my setup following the guides written about passthrough of PCIe video. I have the video display from the domU client going to the physical display, but I cannot get the keyboard to work, I haven=92t even connected = a mouse yet. I attempted to pass through the USB hubs outright, but that failed as the keyboard just stopped working. It would not respond in the domU and I could nolonger get the caps lock to light up. Reconnecting or changing ports had no effect. Attempting to add the usb hub afterwards using xl pci-attach failed as well. But this time, it did not even attach the device. TheOldMan ~ # xl pci-assignable-list 0000:00:0b.0 TheOldMan ~ # xl pci-attach 1 0000:00:0b.0 libxl: error: libxl_pci.c:960:do_pci_add: xc_assign_device failed TheOldMan ~ # xl pci-assignable-list 0000:00:0b.0 TheOldMan ~ # xl pci-list 1 Vdev Device 05.0 0000:01:00.0 06.0 0000:00:0f.1 The reason I am trying to pass through the usb hub is 2 fold: First off, I would prefer not having to go into the console to add my keyboard/mouse each time I start. Second, I cannot seem to get into the console to save my life. I have vnc setup for console, however after connecting, I can=92t type anything. That=92s not to say that the keyboard is useless. Ctrl+alt+1 and ctrl+alt+2 switch between =93serial0 console=94 and =93parallel0 console=94= in the vnc window. In the hopes that all it was that the echo was off, I attempted to enter the usb_add line for my keyboard to no effect. Trying to access the console from a ssh connection in putty also fails. TheOldMan ~ # xl console Office xenconsole: Could not read tty from store: No such file or directory The standard fix I found searching for this error was =93start xenconsoled= =94. Well here is what I say about that. TheOldMan ~ # ps augx | grep xenconsoled root 6146 0.0 0.0 25168 1052 ? SLl 20:08 0:00 /usr/sbin/xenconsoled --pid-file=3D/var/run/xenconsoled.pid root 6888 0.0 0.0 8148 880 pts/0 S+ 20:53 0:00 grep --colour=3Dauto xenconsoled Here is my config: name=3D"Office" firmware_override =3D "/usr/lib/xen/boot/hvmloader" builder=3D"hvm" vcpus=3D2 memory=3D2048 on_poweroff=3D"destroy" on_reboot=3D"restart" on_crash=3D"destroy" disk =3D [ 'tap:aio://images/xen_images/Office.img,hda,w', 'tap:aio://images/iso_images/en_windows_7_enterprise_with_sp1_x64_dvd_u_677= 651.iso,hdc:cdrom,r' ] #disk =3D [ 'tap:aio://images/xen_images/Office.img,hda,w' ] vif =3D [ 'mac=3D00:16:3E:33:5E:F9, bridge=3Dxenbr0' ] #vif =3D [ 'bridge=3Dxenbr0,type=3Dioemu,model=3De1000' ] boot=3D"dc" acpi=3D1 xen_platform_pci=3D1 viridian=3D1 stdvga=3D1 vnc=3D1 vnclisten=3D"192.168.1.102" vncconsole=3D1 vncconsole=3D1 vncdisplay=3D0 vncunused=3D1 vncpasswd=3D"" sdl=3D0 usb=3D1 usbdevice=3D"tablet" gfx_passthru=3D1 audio=3D1 pci =3D [ '01:00.0','00:0f.1' ] I can get more info if needed. I really want to get this project done. MarcT _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users Would you mind pasting us the contents of your Dom0's "lspci" output? It won't quite help me troubleshoot your inability to use the console, but you may need to pass multiple PCI devices to get USB to work. It's a bit of a maze of different controller devices, and you need to pass several in many scenarios. Cheers, Andrew Bobulsky --20cf300fb0dd116e4c04ca37eece Content-Type: text/html; charset=windows-1252 Content-Transfer-Encoding: quoted-printable
Hello Marc,

On Sep= 21, 2012, at 12:58 AM, Marc Tousignant <myrdhn@gmail.com> wrote:

So, I=92m get= ting further and further to completing my setup following the guides writte= n about passthrough of PCIe video.

I have the vid= eo display from the domU client going to the physical display, but I cannot= get the keyboard to work, I haven=92t even connected a mouse yet.

=A0

I attempted to pass th= rough the USB hubs outright, but that failed as the keyboard just stopped w= orking. It would not respond in the domU and I could nolonger get the caps = lock to light up. Reconnecting or changing ports had no effect.

Attempting to add the usb hub afterwards using xl pc= i-attach failed as well. But this time, it did not even attach the device.<= /p>

TheOldMan ~ # xl pci-a= ssignable-list

0000:00:0b.0

TheOldMan ~ # xl pci-attach 1 000= 0:00:0b.0

libxl: error= : libxl_pci.c:960:do_pci_add: xc_assign_device failed

TheOldMan ~ # xl pci-assi= gnable-list

0000:00:0b= .0

TheOldMan ~ # xl pc= i-list 1

Vdev Device

05.0 0000:01:00.0

06.0 0000:00:0f.1

=A0

The reason I am trying to pass through the usb hub i= s 2 fold:

=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0= =A0=A0 First off, I would prefer not having to go into the console to add m= y keyboard/mouse each time I start.

=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0 Second= , I cannot seem to get into the console to save my life.

=A0

I have vnc setup for console, however= after connecting, I can=92t type anything. That=92s not to say that the ke= yboard is useless. Ctrl+alt+1 and ctrl+alt+2 switch between =93serial0 cons= ole=94 and =93parallel0 console=94 in the vnc window. In the hopes that all= it was that the echo was off, I attempted to enter the usb_add line for my= keyboard to no effect.

=A0

Trying to access the c= onsole from a ssh connection in putty also fails.

TheOldMan ~ # xl console Office

xenconsole: Coul= d not read tty from store: No such file or directory

The standard fix I found searching for this error wa= s =93start xenconsoled=94. Well here is what I say about that.

TheOldMan ~ # ps augx | grep xenconsoled

root=A0=A0=A0=A0=A0 6146=A0 0.0=A0 0.0=A0 25168=A0 1052 ?=A0=A0=A0=A0=A0=A0= =A0 SLl=A0 20:08=A0=A0 0:00 /usr/sbin/xenconsoled --pid-file=3D/var/run/xen= consoled.pid

root=A0=A0=A0=A0=A0 6888=A0 0.0=A0 0= .0=A0=A0 8148=A0=A0 880 pts/0=A0=A0=A0 S+=A0=A0 20:53=A0=A0 0:00 grep --col= our=3Dauto xenconsoled

=A0

Here is my config:

=

=A0

name=3D"Office"

=A0

firmware_override =3D "/usr/lib/xen/boot/hvmloader"

builder=3D"hvm"

=A0

vcpus=3D2

=A0

memory=3D2048

=A0

on_poweroff=3D"destroy"

on_reboot=3D"restart= "

on_crash=3D&quo= t;destroy"

=A0

disk =3D [ 'tap:aio://images/xen_images/Office.img,hda,w', 'tap= :aio://images/iso_images/en_windows_7_enterprise_with_sp1_x64_dvd_u_677651.= iso,hdc:cdrom,r' ]

#disk =3D [ 'tap:aio://images/xen_images/Office.img,hda,w' ]

=A0

vif =3D [ 'mac=3D00:16:3E:33:5E:F9, bri= dge=3Dxenbr0' ]

#v= if =3D [ 'bridge=3Dxenbr0,type=3Dioemu,model=3De1000' ]

=A0

boot=3D"dc"

=A0

acpi=3D1

=A0

xen_platform_pci=3D1

=A0

viridian=3D1

=A0

stdvga=3D1

=A0

vnc=3D1

vnclisten=3D"192.168.1.102"

vncconsole=3D1

vncconsole=3D1

vncdisplay=3D0

vncunused=3D1

vncpasswd=3D""

sdl=3D0

=A0

usb=3D1

usbdevice=3D"tablet"

=A0

gfx_passthru=3D1

audio= =3D1

=A0

pci =3D [ '01:00.0','= 00:0f.1' ]

=A0

I can get more info if= needed. I really want to get this project done.

= =A0

MarcT

_______________________________________________
= Xen-users mailing list
Xen-users@lists.xen.org
http://lists.xen.org/xen-users

Would you mind pasting us the contents of your Dom0&#= 39;s "lspci" output?

It won't quite = help me troubleshoot your inability to use the console, but you may need to= pass multiple PCI devices to get USB to work. =A0It's a bit of a maze = of different controller devices, and you need to pass several in many scena= rios.=A0

Cheers,
Andrew Bobulsky
--20cf300fb0dd116e4c04ca37eece-- --===============5750461949487764283== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users --===============5750461949487764283==-- From xen-users-bounces@lists.xen.org Fri Sep 21 15:56:07 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Fri, 21 Sep 2012 15:56:07 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TF5ZM-0001wH-I6; Fri, 21 Sep 2012 15:55:08 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TF5ZK-0001w9-PZ for xen-users@lists.xensource.com; Fri, 21 Sep 2012 15:55:06 +0000 Received: from [85.158.139.211:39434] by server-6.bemta-5.messagelabs.com id 75/F2-21336-9DD8C505; Fri, 21 Sep 2012 15:55:05 +0000 X-Env-Sender: gcexu-xen-users@m.gmane.org X-Msg-Ref: server-9.tower-206.messagelabs.com!1348242904!17976149!1 X-Originating-IP: [80.91.229.3] X-SpamReason: No, hits=1.7 required=7.0 tests=ML_RADAR_SPEW_LINKS_14, RCVD_BY_IP,RCVD_NUMERIC_HELO,spamassassin: X-StarScan-Received: X-StarScan-Version: 6.6.1.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 28148 invoked from network); 21 Sep 2012 15:55:05 -0000 Received: from plane.gmane.org (HELO plane.gmane.org) (80.91.229.3) by server-9.tower-206.messagelabs.com with AES256-SHA encrypted SMTP; 21 Sep 2012 15:55:05 -0000 Received: from list by plane.gmane.org with local (Exim 4.69) (envelope-from ) id 1TF5ZI-0000YC-2k for xen-users@lists.xensource.com; Fri, 21 Sep 2012 17:55:04 +0200 Received: from 198.203.224.219 ([198.203.224.219]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Fri, 21 Sep 2012 17:55:04 +0200 Received: from Jim.molnar by 198.203.224.219 with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Fri, 21 Sep 2012 17:55:04 +0200 X-Injected-Via-Gmane: http://gmane.org/ To: xen-users@lists.xensource.com From: Jim Molnar Date: Fri, 21 Sep 2012 15:51:37 +0000 (UTC) Lines: 31 Message-ID: References: <1342190462.7075.128.camel@wotan2> <6035A0D088A63A46850C3988ED045A4B2998FF73@BITCOM1.int.sbss.com.au> Mime-Version: 1.0 X-Complaints-To: usenet@ger.gmane.org X-Gmane-NNTP-Posting-Host: sea.gmane.org User-Agent: Loom/3.14 (http://gmane.org/) X-Loom-IP: 198.203.224.219 (Mozilla/5.0 (Windows NT 6.1; WOW64; rv:15.0) Gecko/20100101 Firefox/15.0.1) Subject: Re: [Xen-users] win2008 crashes unde xen X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org James Harper bendigoit.com.au> writes: > > > > > I have 358 drivers and error looks like this one > > http://jbeekman.nl/bsod20120117_1953.png > > > > If that is your BSoD then the crash does appear to be in xenvbd.sys which is a GPLPV driver. Can you have a look > in c:\windows\minidump and see if there is a file in there that approximately matches the time of your bluescreen? > > If so, can you zip it up and email it to me? I also need to know the exact version of GPLPV you are using so I can > load the correct symbols in the debugger. > > Thanks > > James > Hey James, We're using your Driver as well 11.0.308 and we're having the issue of a BSOD during Exchange 2010 replication. Was this issue ever fixed? Do you still need a dump from the Debug version of the driver? If anyone knows the fix to this please email me - jim.molnar "at" Gmail dot com Thanks a lot. Jim. _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Fri Sep 21 15:56:07 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Fri, 21 Sep 2012 15:56:07 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TF5ZM-0001wH-I6; Fri, 21 Sep 2012 15:55:08 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TF5ZK-0001w9-PZ for xen-users@lists.xensource.com; Fri, 21 Sep 2012 15:55:06 +0000 Received: from [85.158.139.211:39434] by server-6.bemta-5.messagelabs.com id 75/F2-21336-9DD8C505; Fri, 21 Sep 2012 15:55:05 +0000 X-Env-Sender: gcexu-xen-users@m.gmane.org X-Msg-Ref: server-9.tower-206.messagelabs.com!1348242904!17976149!1 X-Originating-IP: [80.91.229.3] X-SpamReason: No, hits=1.7 required=7.0 tests=ML_RADAR_SPEW_LINKS_14, RCVD_BY_IP,RCVD_NUMERIC_HELO,spamassassin: X-StarScan-Received: X-StarScan-Version: 6.6.1.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 28148 invoked from network); 21 Sep 2012 15:55:05 -0000 Received: from plane.gmane.org (HELO plane.gmane.org) (80.91.229.3) by server-9.tower-206.messagelabs.com with AES256-SHA encrypted SMTP; 21 Sep 2012 15:55:05 -0000 Received: from list by plane.gmane.org with local (Exim 4.69) (envelope-from ) id 1TF5ZI-0000YC-2k for xen-users@lists.xensource.com; Fri, 21 Sep 2012 17:55:04 +0200 Received: from 198.203.224.219 ([198.203.224.219]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Fri, 21 Sep 2012 17:55:04 +0200 Received: from Jim.molnar by 198.203.224.219 with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Fri, 21 Sep 2012 17:55:04 +0200 X-Injected-Via-Gmane: http://gmane.org/ To: xen-users@lists.xensource.com From: Jim Molnar Date: Fri, 21 Sep 2012 15:51:37 +0000 (UTC) Lines: 31 Message-ID: References: <1342190462.7075.128.camel@wotan2> <6035A0D088A63A46850C3988ED045A4B2998FF73@BITCOM1.int.sbss.com.au> Mime-Version: 1.0 X-Complaints-To: usenet@ger.gmane.org X-Gmane-NNTP-Posting-Host: sea.gmane.org User-Agent: Loom/3.14 (http://gmane.org/) X-Loom-IP: 198.203.224.219 (Mozilla/5.0 (Windows NT 6.1; WOW64; rv:15.0) Gecko/20100101 Firefox/15.0.1) Subject: Re: [Xen-users] win2008 crashes unde xen X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org James Harper bendigoit.com.au> writes: > > > > > I have 358 drivers and error looks like this one > > http://jbeekman.nl/bsod20120117_1953.png > > > > If that is your BSoD then the crash does appear to be in xenvbd.sys which is a GPLPV driver. Can you have a look > in c:\windows\minidump and see if there is a file in there that approximately matches the time of your bluescreen? > > If so, can you zip it up and email it to me? I also need to know the exact version of GPLPV you are using so I can > load the correct symbols in the debugger. > > Thanks > > James > Hey James, We're using your Driver as well 11.0.308 and we're having the issue of a BSOD during Exchange 2010 replication. Was this issue ever fixed? Do you still need a dump from the Debug version of the driver? If anyone knows the fix to this please email me - jim.molnar "at" Gmail dot com Thanks a lot. Jim. _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Fri Sep 21 16:03:15 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Fri, 21 Sep 2012 16:03:15 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TF5gP-0002dz-Np; Fri, 21 Sep 2012 16:02:25 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TF5gN-0002du-Rq for xen-users@lists.xen.org; Fri, 21 Sep 2012 16:02:23 +0000 Received: from [85.158.139.211:42033] by server-1.bemta-5.messagelabs.com id 38/70-04809-E8F8C505; Fri, 21 Sep 2012 16:02:22 +0000 X-Env-Sender: reklov@unitedklasens.de X-Msg-Ref: server-3.tower-206.messagelabs.com!1348243342!19475481!1 X-Originating-IP: [37.17.224.13] X-SpamReason: No, hits=0.0 required=7.0 tests=ML_RADAR_SPEW_LINKS_23, spamassassin: X-StarScan-Received: X-StarScan-Version: 6.6.1.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 11285 invoked from network); 21 Sep 2012 16:02:22 -0000 Received: from webgo24-server13.de (HELO webgo24-server13.de) (37.17.224.13) by server-3.tower-206.messagelabs.com with SMTP; 21 Sep 2012 16:02:22 -0000 Received: from [192.168.42.13] (HSI-KBW-078-042-024-173.hsi3.kabel-badenwuerttemberg.de [78.42.24.173]) by webgo24-server13.de (Postfix) with ESMTPSA id DF3E830409A6; Fri, 21 Sep 2012 18:02:21 +0200 (CEST) Message-ID: <505C8F8D.6000007@unitedklasens.de> Date: Fri, 21 Sep 2012 18:02:21 +0200 From: Volker Klasen User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:10.0.6esrpre) Gecko/20120817 Icedove/10.0.6 MIME-Version: 1.0 To: Marc Tousignant References: <002401cd97b5$5b49f260$11ddd720$@gmail.com> In-Reply-To: <002401cd97b5$5b49f260$11ddd720$@gmail.com> X-Enigmail-Version: 1.4.1 Cc: xen-users@lists.xen.org Subject: Re: [Xen-users] Need help with passing through USB hub or devices X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi Marc, > I have the video display from the domU client going to the physical > display, but I cannot get the keyboard to work, I haven't even > connected a mouse yet. > > I can get more info if needed. I really want to get this project > done. which kernel do you use? I have the same problem with kernel 3.5; 3.4 works fine. This problem seems to be a known bug, cf. [1] and [2]. Hoping for it to be fixed in 3.6 Cheers, Volker [1] http://lists.xen.org/archives/html/xen-devel/2012-08/msg00562.html [2] http://lists.xen.org/archives/html/xen-users/2012-08/msg00219.html -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.12 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAlBcj40ACgkQgKD4KXUzSrgBHwCePAZdO4XjTc5n3zNWYkeUy+m+ hPYAoNGl+G3a2l7xHbBxVwRgAPa9eXaY =jwG0 -----END PGP SIGNATURE----- _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Fri Sep 21 16:03:15 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Fri, 21 Sep 2012 16:03:15 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TF5gP-0002dz-Np; Fri, 21 Sep 2012 16:02:25 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TF5gN-0002du-Rq for xen-users@lists.xen.org; Fri, 21 Sep 2012 16:02:23 +0000 Received: from [85.158.139.211:42033] by server-1.bemta-5.messagelabs.com id 38/70-04809-E8F8C505; Fri, 21 Sep 2012 16:02:22 +0000 X-Env-Sender: reklov@unitedklasens.de X-Msg-Ref: server-3.tower-206.messagelabs.com!1348243342!19475481!1 X-Originating-IP: [37.17.224.13] X-SpamReason: No, hits=0.0 required=7.0 tests=ML_RADAR_SPEW_LINKS_23, spamassassin: X-StarScan-Received: X-StarScan-Version: 6.6.1.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 11285 invoked from network); 21 Sep 2012 16:02:22 -0000 Received: from webgo24-server13.de (HELO webgo24-server13.de) (37.17.224.13) by server-3.tower-206.messagelabs.com with SMTP; 21 Sep 2012 16:02:22 -0000 Received: from [192.168.42.13] (HSI-KBW-078-042-024-173.hsi3.kabel-badenwuerttemberg.de [78.42.24.173]) by webgo24-server13.de (Postfix) with ESMTPSA id DF3E830409A6; Fri, 21 Sep 2012 18:02:21 +0200 (CEST) Message-ID: <505C8F8D.6000007@unitedklasens.de> Date: Fri, 21 Sep 2012 18:02:21 +0200 From: Volker Klasen User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:10.0.6esrpre) Gecko/20120817 Icedove/10.0.6 MIME-Version: 1.0 To: Marc Tousignant References: <002401cd97b5$5b49f260$11ddd720$@gmail.com> In-Reply-To: <002401cd97b5$5b49f260$11ddd720$@gmail.com> X-Enigmail-Version: 1.4.1 Cc: xen-users@lists.xen.org Subject: Re: [Xen-users] Need help with passing through USB hub or devices X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi Marc, > I have the video display from the domU client going to the physical > display, but I cannot get the keyboard to work, I haven't even > connected a mouse yet. > > I can get more info if needed. I really want to get this project > done. which kernel do you use? I have the same problem with kernel 3.5; 3.4 works fine. This problem seems to be a known bug, cf. [1] and [2]. Hoping for it to be fixed in 3.6 Cheers, Volker [1] http://lists.xen.org/archives/html/xen-devel/2012-08/msg00562.html [2] http://lists.xen.org/archives/html/xen-users/2012-08/msg00219.html -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.12 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAlBcj40ACgkQgKD4KXUzSrgBHwCePAZdO4XjTc5n3zNWYkeUy+m+ hPYAoNGl+G3a2l7xHbBxVwRgAPa9eXaY =jwG0 -----END PGP SIGNATURE----- _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Fri Sep 21 16:31:19 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Fri, 21 Sep 2012 16:31:19 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TF67X-0004WV-Rz; Fri, 21 Sep 2012 16:30:27 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TF67W-0004WG-Dh for xen-users@lists.xen.org; Fri, 21 Sep 2012 16:30:26 +0000 Received: from [85.158.139.211:27221] by server-4.bemta-5.messagelabs.com id 57/17-23042-1269C505; Fri, 21 Sep 2012 16:30:25 +0000 X-Env-Sender: rulerof@gmail.com X-Msg-Ref: server-14.tower-206.messagelabs.com!1348245022!19435578!1 X-Originating-IP: [209.85.216.52] X-SpamReason: No, hits=0.3 required=7.0 tests=ML_RADAR_SPEW_LINKS_14, RCVD_BY_IP,spamassassin: X-StarScan-Received: X-StarScan-Version: 6.6.1.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 22208 invoked from network); 21 Sep 2012 16:30:23 -0000 Received: from mail-qa0-f52.google.com (HELO mail-qa0-f52.google.com) (209.85.216.52) by server-14.tower-206.messagelabs.com with RC4-SHA encrypted SMTP; 21 Sep 2012 16:30:23 -0000 Received: by qabg24 with SMTP id g24so827010qab.11 for ; Fri, 21 Sep 2012 09:30:22 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc:content-type:content-transfer-encoding; bh=K5dKrMqlt0RE4fzmRKz0pdb6OXZVz3q5uYUFfwh+OWs=; b=NZi+/VpyBCUAL2cCaXdKs8mLPNz0H8rpyil6DC1AEAiqB30/Tk9j1hGf0XJhs3sLOw 5qSYG2L6J9outVRypcl/MPWL7La5nG5snEubGCrxqYmfywprrRC3t1+nNvIxq7cquEMZ iXdgKpS2kF+A9ohvTo18N24KEA18BiHlzDAqCXu4ewRrv6zI3UQizCTqafzCGa9F2EMq f/fcerWUzSTTp+YMzpzjR9VWHD94Ho8SMOO74Q4OpRV33VQBc3BoUK5ZP0fO9JWZ+cvY /YtBC5dZ65NKrEeFdlctb2DoEXF4nQ48bt/7NsX6KlNeP7KlKdHF6Grv9IBR0VG2E6IY mvww== Received: by 10.229.136.8 with SMTP id p8mr3736824qct.3.1348245022034; Fri, 21 Sep 2012 09:30:22 -0700 (PDT) Mime-Version: 1.0 (1.0) References: <505B86AE.9040507@earthlink.net> In-Reply-To: <505B86AE.9040507@earthlink.net> From: Andrew Bobulsky Date: Fri, 21 Sep 2012 12:30:21 -0400 Message-ID: <-4689096786842132042@unknownmsgid> To: ShadesOfGrey Cc: "xen-users@lists.xen.org" , Casey DeLorme , "kvm@vger.kernel.org" Subject: Re: [Xen-users] Recommendations for Virtulization Hardware X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org (CC'ing Casey on this, as I recommend his setup for an Intel-based solution) Hello ShadesOfGrey, Hehehe, talk about timing ;) On Sep 20, 2012, at 5:15 PM, ShadesOfGrey wrote: > I'm looking to build a new personal computer. I want it to function as a Linux desktop, provide network services for my home, and lastly, occasional Windows gaming. From what I've gathered, virtualization using a Type 1 Hypervisor supporting PCI/VGA pass-through like KVM or Xen would be an attractive solution for my needs. For reference, reading these threads on Ars Technica may be helpful to understand where I'm coming from, http://arstechnica.com/civis/viewtopic.php?f=6&t=1175674 and http://arstechnica.com/civis/viewtopic.php?f=11&t=1181867. But basically, I use Linux as my primary OS and would rather avoid dual booting or building two boxes just to play Windows games when I want to play Windows games. I'm also intrigued by the concept of virtualization and would like to experiment with it as a solution for my case. > > My problem is isolating which hardware to choose, specifically which combination of CPU, motherboard and video card. Previously I had been relying on web searches to glean information from gaming and enthusiast web sites and tech specs from motherboard manufacturers. After what I learned during my participation in the referenced threads at Ars Technica, I find myself back at square one. Instead of trying to guess what hardware support KVM & Xen, and vice versa. I'd like to know what hardware KVM & Xen users are actually using to run KVM & Xen? Particularly with consideration for 3D gaming and current generation hardware, BTW. > > If there is need for further clarification, I'll answer any queries you might have. > > _______________________________________________ > Xen-users mailing list > Xen-users@lists.xen.org > http://lists.xen.org/xen-users As one of the folks on the list who has done this---probably to the most extreme degree---I can tell you it's good stuff. It brings the joys of datacenter consolidation to your gaming desktop, and also to your wallet ;) While my setup is now slightly dated, the 990FX chipset is still at the top of the AMD offering, so you can shop around on CPUs, and buy a cheaper "secondary" USB controller if you're not looking to cram in a 4-to-1 ratio. I've never had much success passing through the onboard USB from an AMD system, so I highly recommend picking up a little PCIe x1 controller at the least. That said, I'm convinced that highpoint has one of the coincidentally-best products on the market for people looking to do this, but I digress! Take a look at, specifically, this post I made to the list some months back, and I'll follow with some errata: http://lists.xen.org/archives/html/xen-users/2012-05/msg00328.html First, I've tested all of the hardware in the build that I recommended, and indeed ended up building a four-headed unit. It works like magic. Came in handy a few weeks ago when several of my friends and I piled into a couple cars for a vacation where we wanted to play games (yup, we're total nerds), but we couldn't fit four desktop cases in addition to our stuff in the cars. :) Second, by the time I got around to building it, the Antec One Hundred wasn't available. Finding a case that supports 8 expansion slots is a tough thing, but I found another similarly priced one, and it was a dream to build. I recommend it highly if you think you may want to max out your slots and/or go deeper down the rabbit hole with consolidated desktops: http://www.newegg.com/Product/Product.aspx?Item=N82E16811112238 Aside from being a very solid case for the price point (good features for screwless installation as well), to give you an idea of the size, it is laid out in such a way that I could fit dual-GPU cards in it (Radeon 5970s). I ultimately had to remove the HDD mounts to pull it off, but you shouldn't have that problem... Mostly because AMDs dual GPU cards won't work for this, so don't buy one for this build. It's a problem with the PCIe switching hardware (well, the firmware thereof, probably) that they use. I'll save you the rambling, but let's just say that it should work, but doesn't :( Also, the case does look good! ;) Finally, and this is unfortunate, for the AMD build, *I* recommend you use ESXi. While Xen _does_ work with the hardware that I've listed, I've never been able to get the VMs to work properly with the GPLPV drivers, and these are crucial to performance. I really, really want to bring this project back up on Xen though, and will try again now that 4.2 has gone RTM. If you aren't buying anytime soon and would like to hit me up in a few weeks, by all means drop me a line, and I'll let you know if I've gotten around to it. ---------------- So, for the Intel route! Casey DeLorme has, just this week, posted a fantastic set of detailed videos and documentation on his setup, where he basically does exactly what you're trying to accomplish. You can find links to all of the documentation, which I'm pretty sure covers his exact hardware, along with videos of the installation process he used and a detailed, written guide. Fine work if you ask me ;) http://lists.xen.org/archives/html/xen-users/2012-09/msg00191.html As far as his hardware goes, I'm not sure if it's the latest Intel chips or not. I've been eyeballing the i7-3770 myself (NOT the 3770K, that one will not work, as [in my opinion] Intel has a pension for artificially crippling their products for profit). Haven't found a board yet, but then again I started eyeballing hardware a day or two ago. Cheers, Andrew Bobulsky _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Fri Sep 21 16:31:19 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Fri, 21 Sep 2012 16:31:19 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TF67X-0004WV-Rz; Fri, 21 Sep 2012 16:30:27 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TF67W-0004WG-Dh for xen-users@lists.xen.org; Fri, 21 Sep 2012 16:30:26 +0000 Received: from [85.158.139.211:27221] by server-4.bemta-5.messagelabs.com id 57/17-23042-1269C505; Fri, 21 Sep 2012 16:30:25 +0000 X-Env-Sender: rulerof@gmail.com X-Msg-Ref: server-14.tower-206.messagelabs.com!1348245022!19435578!1 X-Originating-IP: [209.85.216.52] X-SpamReason: No, hits=0.3 required=7.0 tests=ML_RADAR_SPEW_LINKS_14, RCVD_BY_IP,spamassassin: X-StarScan-Received: X-StarScan-Version: 6.6.1.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 22208 invoked from network); 21 Sep 2012 16:30:23 -0000 Received: from mail-qa0-f52.google.com (HELO mail-qa0-f52.google.com) (209.85.216.52) by server-14.tower-206.messagelabs.com with RC4-SHA encrypted SMTP; 21 Sep 2012 16:30:23 -0000 Received: by qabg24 with SMTP id g24so827010qab.11 for ; Fri, 21 Sep 2012 09:30:22 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc:content-type:content-transfer-encoding; bh=K5dKrMqlt0RE4fzmRKz0pdb6OXZVz3q5uYUFfwh+OWs=; b=NZi+/VpyBCUAL2cCaXdKs8mLPNz0H8rpyil6DC1AEAiqB30/Tk9j1hGf0XJhs3sLOw 5qSYG2L6J9outVRypcl/MPWL7La5nG5snEubGCrxqYmfywprrRC3t1+nNvIxq7cquEMZ iXdgKpS2kF+A9ohvTo18N24KEA18BiHlzDAqCXu4ewRrv6zI3UQizCTqafzCGa9F2EMq f/fcerWUzSTTp+YMzpzjR9VWHD94Ho8SMOO74Q4OpRV33VQBc3BoUK5ZP0fO9JWZ+cvY /YtBC5dZ65NKrEeFdlctb2DoEXF4nQ48bt/7NsX6KlNeP7KlKdHF6Grv9IBR0VG2E6IY mvww== Received: by 10.229.136.8 with SMTP id p8mr3736824qct.3.1348245022034; Fri, 21 Sep 2012 09:30:22 -0700 (PDT) Mime-Version: 1.0 (1.0) References: <505B86AE.9040507@earthlink.net> In-Reply-To: <505B86AE.9040507@earthlink.net> From: Andrew Bobulsky Date: Fri, 21 Sep 2012 12:30:21 -0400 Message-ID: <-4689096786842132042@unknownmsgid> To: ShadesOfGrey Cc: "xen-users@lists.xen.org" , Casey DeLorme , "kvm@vger.kernel.org" Subject: Re: [Xen-users] Recommendations for Virtulization Hardware X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org (CC'ing Casey on this, as I recommend his setup for an Intel-based solution) Hello ShadesOfGrey, Hehehe, talk about timing ;) On Sep 20, 2012, at 5:15 PM, ShadesOfGrey wrote: > I'm looking to build a new personal computer. I want it to function as a Linux desktop, provide network services for my home, and lastly, occasional Windows gaming. From what I've gathered, virtualization using a Type 1 Hypervisor supporting PCI/VGA pass-through like KVM or Xen would be an attractive solution for my needs. For reference, reading these threads on Ars Technica may be helpful to understand where I'm coming from, http://arstechnica.com/civis/viewtopic.php?f=6&t=1175674 and http://arstechnica.com/civis/viewtopic.php?f=11&t=1181867. But basically, I use Linux as my primary OS and would rather avoid dual booting or building two boxes just to play Windows games when I want to play Windows games. I'm also intrigued by the concept of virtualization and would like to experiment with it as a solution for my case. > > My problem is isolating which hardware to choose, specifically which combination of CPU, motherboard and video card. Previously I had been relying on web searches to glean information from gaming and enthusiast web sites and tech specs from motherboard manufacturers. After what I learned during my participation in the referenced threads at Ars Technica, I find myself back at square one. Instead of trying to guess what hardware support KVM & Xen, and vice versa. I'd like to know what hardware KVM & Xen users are actually using to run KVM & Xen? Particularly with consideration for 3D gaming and current generation hardware, BTW. > > If there is need for further clarification, I'll answer any queries you might have. > > _______________________________________________ > Xen-users mailing list > Xen-users@lists.xen.org > http://lists.xen.org/xen-users As one of the folks on the list who has done this---probably to the most extreme degree---I can tell you it's good stuff. It brings the joys of datacenter consolidation to your gaming desktop, and also to your wallet ;) While my setup is now slightly dated, the 990FX chipset is still at the top of the AMD offering, so you can shop around on CPUs, and buy a cheaper "secondary" USB controller if you're not looking to cram in a 4-to-1 ratio. I've never had much success passing through the onboard USB from an AMD system, so I highly recommend picking up a little PCIe x1 controller at the least. That said, I'm convinced that highpoint has one of the coincidentally-best products on the market for people looking to do this, but I digress! Take a look at, specifically, this post I made to the list some months back, and I'll follow with some errata: http://lists.xen.org/archives/html/xen-users/2012-05/msg00328.html First, I've tested all of the hardware in the build that I recommended, and indeed ended up building a four-headed unit. It works like magic. Came in handy a few weeks ago when several of my friends and I piled into a couple cars for a vacation where we wanted to play games (yup, we're total nerds), but we couldn't fit four desktop cases in addition to our stuff in the cars. :) Second, by the time I got around to building it, the Antec One Hundred wasn't available. Finding a case that supports 8 expansion slots is a tough thing, but I found another similarly priced one, and it was a dream to build. I recommend it highly if you think you may want to max out your slots and/or go deeper down the rabbit hole with consolidated desktops: http://www.newegg.com/Product/Product.aspx?Item=N82E16811112238 Aside from being a very solid case for the price point (good features for screwless installation as well), to give you an idea of the size, it is laid out in such a way that I could fit dual-GPU cards in it (Radeon 5970s). I ultimately had to remove the HDD mounts to pull it off, but you shouldn't have that problem... Mostly because AMDs dual GPU cards won't work for this, so don't buy one for this build. It's a problem with the PCIe switching hardware (well, the firmware thereof, probably) that they use. I'll save you the rambling, but let's just say that it should work, but doesn't :( Also, the case does look good! ;) Finally, and this is unfortunate, for the AMD build, *I* recommend you use ESXi. While Xen _does_ work with the hardware that I've listed, I've never been able to get the VMs to work properly with the GPLPV drivers, and these are crucial to performance. I really, really want to bring this project back up on Xen though, and will try again now that 4.2 has gone RTM. If you aren't buying anytime soon and would like to hit me up in a few weeks, by all means drop me a line, and I'll let you know if I've gotten around to it. ---------------- So, for the Intel route! Casey DeLorme has, just this week, posted a fantastic set of detailed videos and documentation on his setup, where he basically does exactly what you're trying to accomplish. You can find links to all of the documentation, which I'm pretty sure covers his exact hardware, along with videos of the installation process he used and a detailed, written guide. Fine work if you ask me ;) http://lists.xen.org/archives/html/xen-users/2012-09/msg00191.html As far as his hardware goes, I'm not sure if it's the latest Intel chips or not. I've been eyeballing the i7-3770 myself (NOT the 3770K, that one will not work, as [in my opinion] Intel has a pension for artificially crippling their products for profit). Haven't found a board yet, but then again I started eyeballing hardware a day or two ago. Cheers, Andrew Bobulsky _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Fri Sep 21 17:03:30 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Fri, 21 Sep 2012 17:03:30 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TF6cX-0005Gc-7n; Fri, 21 Sep 2012 17:02:29 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TF6cV-0005GX-H4 for xen-users@lists.xen.org; Fri, 21 Sep 2012 17:02:27 +0000 Received: from [85.158.139.83:60480] by server-16.bemta-5.messagelabs.com id 70/AC-11718-2AD9C505; Fri, 21 Sep 2012 17:02:26 +0000 X-Env-Sender: cdelorme@gmail.com X-Msg-Ref: server-11.tower-182.messagelabs.com!1348246942!24370219!1 X-Originating-IP: [209.85.219.45] X-SpamReason: No, hits=1.2 required=7.0 tests=HTML_10_20,HTML_MESSAGE, ML_RADAR_SPEW_LINKS_14,RCVD_BY_IP,spamassassin: X-StarScan-Received: X-StarScan-Version: 6.6.1.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 30136 invoked from network); 21 Sep 2012 17:02:24 -0000 Received: from mail-oa0-f45.google.com (HELO mail-oa0-f45.google.com) (209.85.219.45) by server-11.tower-182.messagelabs.com with RC4-SHA encrypted SMTP; 21 Sep 2012 17:02:24 -0000 Received: by oagn12 with SMTP id n12so4574933oag.32 for ; Fri, 21 Sep 2012 10:02:22 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=+LcdGKWIldl/tM0FK8Vbo5qVrZ27eacYhLIzX0Hib9E=; b=ZWGMwtrtcRv1W+RVuSdXY7SwJcKoy2T8feOZZ5KqZGDL7gOekPslu8fRRCMHjBqBaG I6HRD/FXk2zFJpa/WjnJhy6mEf3qYuOf+dbh/g7jIQ6e2BXE7RKKNV7pGd4fVztXlRRz eeFF0daSTpCRer3KEGBJWLnxtTA115qCMXkjJvZ6R/X6wlupYwR8CrtWPnzpbOn+mZLd 6aeLI3ruZJIgWhwffMEU3XbEkL8aKr649Je5xaehdYTlQOYbPZpdUUh0QTOhuoy1kA2b c4u6KZzZMtQGC6Iri9Mz3MG/9tLJtFYi6QKQh1ywpLfd1zcUR/cz8Wx3O5iZeAC2NnuT Tm8Q== MIME-Version: 1.0 Received: by 10.60.22.196 with SMTP id g4mr4430897oef.95.1348246941852; Fri, 21 Sep 2012 10:02:21 -0700 (PDT) Received: by 10.76.19.148 with HTTP; Fri, 21 Sep 2012 10:02:21 -0700 (PDT) In-Reply-To: <-4689096786842132042@unknownmsgid> References: <505B86AE.9040507@earthlink.net> <-4689096786842132042@unknownmsgid> Date: Fri, 21 Sep 2012 13:02:21 -0400 Message-ID: From: Casey DeLorme To: Andrew Bobulsky Cc: "xen-users@lists.xen.org" , ShadesOfGrey , "kvm@vger.kernel.org" Subject: Re: [Xen-users] Recommendations for Virtulization Hardware X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============4879325329583822335==" Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org --===============4879325329583822335== Content-Type: multipart/alternative; boundary=e89a8fb2038809e60f04ca393414 --e89a8fb2038809e60f04ca393414 Content-Type: text/plain; charset=ISO-8859-1 Thanks for the CC Andrew, I responded in private since I didn't want to spam the list. Since we're on the subject of the latest hardware, my system was using a Z68 Motherboard Chipset and Core i7 SandyBridge CPU (2600). I just sold it to a friend and upgraded to the latest. Now running an IvyBridge 3770, Z77 Motherboard Chipset (ASRock Z77 Extreme 9), and similar components for the rest. The Extreme 9 price is extremely high, I wouldn't recommend it unless you have the money, their Z77 Extreme 6 is priced at the same as the Z68 Extreme4 Gen3, and has all the same features plus more USB 3.0. I would give that one a shake if you are looking for newest components. The hardest part of switching from the Extreme4 Gen3 was remapping the USB ports to USB controllers by PCI BDF in Linux, because I haven't found an easy way to do that using the systems information yet. As soon as I'm done putting together the details, I'll append the new hardware information to the wiki. As for changes, the new Z77 chipset has onboard USB 3.0 in exchange for some of the formerly USB 2.0 ports. In my performance demo video I showed that USB 2.0 speeds are sub-par, but even SUB 2.0 devices can hit higher rates when connected to a USB 3.0 port. As far as the IvyBridge CPU, onboard graphics are noticeably better in Dom0, and file decompression in my Windows HVM appears to be faster. I have not run any benchmark tests yet. I compiled the new Xen 4.2 stable, as tagged in the new 4.2 testing branch, but I may try the older revision of Xen in my guide. I am getting an error on the first-launch attempt of any virtual machine with passed devices. When I try again it works, but it's 5 lines worth of errors which makes the following success seem less joyful. I tried kernel 3.5.4, and it appears to be suffering the same passthrough bugs as 3.5.2, so I would avoid 3.5+ still. I ended up with Kernel 3.4.11, which is working. One good bit of news was I kept my SSD, so I was able to just recreate the HVM configuration and launch Windows without problems. Only issues were new drivers, and Windows asking to reactivate due to HW changes. Hope this information helps, ~Casey On Fri, Sep 21, 2012 at 12:30 PM, Andrew Bobulsky wrote: > (CC'ing Casey on this, as I recommend his setup for an Intel-based > solution) > > Hello ShadesOfGrey, > > Hehehe, talk about timing ;) > > On Sep 20, 2012, at 5:15 PM, ShadesOfGrey > wrote: > > > I'm looking to build a new personal computer. I want it to function as > a Linux desktop, provide network services for my home, and lastly, > occasional Windows gaming. From what I've gathered, virtualization using a > Type 1 Hypervisor supporting PCI/VGA pass-through like KVM or Xen would be > an attractive solution for my needs. For reference, reading these threads > on Ars Technica may be helpful to understand where I'm coming from, > http://arstechnica.com/civis/viewtopic.php?f=6&t=1175674 and > http://arstechnica.com/civis/viewtopic.php?f=11&t=1181867. But basically, > I use Linux as my primary OS and would rather avoid dual booting or > building two boxes just to play Windows games when I want to play Windows > games. I'm also intrigued by the concept of virtualization and would like > to experiment with it as a solution for my case. > > > > My problem is isolating which hardware to choose, specifically which > combination of CPU, motherboard and video card. Previously I had been > relying on web searches to glean information from gaming and enthusiast web > sites and tech specs from motherboard manufacturers. After what I learned > during my participation in the referenced threads at Ars Technica, I find > myself back at square one. Instead of trying to guess what hardware > support KVM & Xen, and vice versa. I'd like to know what hardware KVM & > Xen users are actually using to run KVM & Xen? Particularly with > consideration for 3D gaming and current generation hardware, BTW. > > > > If there is need for further clarification, I'll answer any queries you > might have. > > > > _______________________________________________ > > Xen-users mailing list > > Xen-users@lists.xen.org > > http://lists.xen.org/xen-users > > As one of the folks on the list who has done this---probably to the > most extreme degree---I can tell you it's good stuff. It brings the > joys of datacenter consolidation to your gaming desktop, and also to > your wallet ;) > > While my setup is now slightly dated, the 990FX chipset is still at > the top of the AMD offering, so you can shop around on CPUs, and buy a > cheaper "secondary" USB controller if you're not looking to cram in a > 4-to-1 ratio. I've never had much success passing through the onboard > USB from an AMD system, so I highly recommend picking up a little PCIe > x1 controller at the least. That said, I'm convinced that highpoint > has one of the coincidentally-best products on the market for people > looking to do this, but I digress! > > Take a look at, specifically, this post I made to the list some months > back, and I'll follow with some errata: > http://lists.xen.org/archives/html/xen-users/2012-05/msg00328.html > > First, I've tested all of the hardware in the build that I > recommended, and indeed ended up building a four-headed unit. It works > like magic. Came in handy a few weeks ago when several of my friends > and I piled into a couple cars for a vacation where we wanted to play > games (yup, we're total nerds), but we couldn't fit four desktop cases > in addition to our stuff in the cars. :) > > Second, by the time I got around to building it, the Antec One Hundred > wasn't available. Finding a case that supports 8 expansion slots is a > tough thing, but I found another similarly priced one, and it was a > dream to build. I recommend it highly if you think you may want to > max out your slots and/or go deeper down the rabbit hole with > consolidated desktops: > http://www.newegg.com/Product/Product.aspx?Item=N82E16811112238 > > Aside from being a very solid case for the price point (good features > for screwless installation as well), to give you an idea of the size, > it is laid out in such a way that I could fit dual-GPU cards in it > (Radeon 5970s). I ultimately had to remove the HDD mounts to pull it > off, but you shouldn't have that problem... Mostly because AMDs dual > GPU cards won't work for this, so don't buy one for this build. It's > a problem with the PCIe switching hardware (well, the firmware > thereof, probably) that they use. I'll save you the rambling, but > let's just say that it should work, but doesn't :( > > Also, the case does look good! ;) > > Finally, and this is unfortunate, for the AMD build, *I* recommend you > use ESXi. While Xen _does_ work with the hardware that I've listed, > I've never been able to get the VMs to work properly with the GPLPV > drivers, and these are crucial to performance. I really, really want > to bring this project back up on Xen though, and will try again now > that 4.2 has gone RTM. If you aren't buying anytime soon and would > like to hit me up in a few weeks, by all means drop me a line, and > I'll let you know if I've gotten around to it. > > > ---------------- > > > So, for the Intel route! > > Casey DeLorme has, just this week, posted a fantastic set of detailed > videos and documentation on his setup, where he basically does exactly > what you're trying to accomplish. You can find links to all of the > documentation, which I'm pretty sure covers his exact hardware, along > with videos of the installation process he used and a detailed, > written guide. Fine work if you ask me ;) > > http://lists.xen.org/archives/html/xen-users/2012-09/msg00191.html > > As far as his hardware goes, I'm not sure if it's the latest Intel > chips or not. I've been eyeballing the i7-3770 myself (NOT the 3770K, > that one will not work, as [in my opinion] Intel has a pension for > artificially crippling their products for profit). Haven't found a > board yet, but then again I started eyeballing hardware a day or two > ago. > > > > Cheers, > Andrew Bobulsky > --e89a8fb2038809e60f04ca393414 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable
Thanks for the CC Andrew,

I responded in= private since I didn't want to spam the list.

Since we're on the subject of the latest hardware, my system was using= a Z68 Motherboard Chipset and Core i7 SandyBridge CPU (2600). =A0I just so= ld it to a friend and upgraded to the latest.

Now running an IvyBridge 3770, Z77 Motherboard Chipset = (ASRock Z77 Extreme 9), and similar components for the rest. =A0The Extreme= 9 price is extremely high, I wouldn't recommend it unless you have the= money, their Z77 Extreme 6 is priced at the same as the Z68 Extreme4 Gen3,= and has all the same features plus more USB 3.0. =A0I would give that one = a shake if you are looking for newest components. =A0The hardest part of sw= itching from the Extreme4 Gen3 was remapping the USB ports to USB controlle= rs by PCI BDF in Linux, because I haven't found an easy way to do that = using the systems information yet.

As soon as I'm done putting together the details, I= 'll append the new hardware information to the wiki.

As for changes, the new Z77 chipset has onboard USB 3.0 in exchange = for some of the formerly USB 2.0 ports. =A0In my performance demo video I s= howed that USB 2.0 speeds are sub-par, but even SUB 2.0 devices can hit hig= her rates when connected to a USB 3.0 port. =A0As far as the IvyBridge CPU,= onboard graphics are noticeably better in Dom0, and file decompression in = my Windows HVM appears to be faster. =A0I have not run any benchmark tests = yet.


I compiled the new Xen 4.2 stable, as ta= gged in the new 4.2 testing branch, but I may try the older revision of Xen= in my guide. =A0I am getting an error on the first-launch attempt of any v= irtual machine with passed devices. =A0When I try again it works, but it= 9;s 5 lines worth of errors which makes the following success seem less joy= ful.

I tried kernel 3.5.4, and it appears to be suffering th= e same passthrough bugs as 3.5.2, so I would avoid 3.5+ still. =A0I ended u= p with Kernel 3.4.11, which is working.

One good b= it of news was I kept my SSD, so I was able to just recreate the HVM config= uration and launch Windows without problems. =A0Only issues were new driver= s, and Windows asking to reactivate due to HW changes.


Hope this information helps,
=

~Casey

On= Fri, Sep 21, 2012 at 12:30 PM, Andrew Bobulsky <rulerof@gmail.com>= wrote:
(CC'ing Casey on this, as I recommend hi= s setup for an Intel-based solution)

Hello ShadesOfGrey,

Hehehe, talk about timing ;)

On Sep 20, 2012, at 5:15 PM, ShadesOfGrey <shades_of_grey@earthlink.net> wrote:

> I'm looking to build a new personal computer. =A0I want it to func= tion as a Linux desktop, provide network services for my home, and lastly, = occasional Windows gaming. =A0From what I've gathered, virtualization u= sing a Type 1 Hypervisor supporting PCI/VGA pass-through like KVM or Xen wo= uld be an attractive solution for my needs. =A0For reference, reading these= threads on Ars Technica may be helpful to understand where I'm coming = from, http://arstechnica.com/civis/viewtopic.php?f=3D6&= amp;t=3D1175674 and http://arstechnica.com/civis/v= iewtopic.php?f=3D11&t=3D1181867. But basically, I use Linux as my p= rimary OS and would rather avoid dual booting or building two boxes just to= play Windows games when I want to play Windows games. =A0I'm also intr= igued by the concept of virtualization and would like to experiment with it= as a solution for my case.
>
> My problem is isolating which hardware to choose, specifically which c= ombination of CPU, motherboard and video card. =A0Previously I had been rel= ying on web searches to glean information from gaming and enthusiast web si= tes and tech specs from motherboard manufacturers. =A0After what I learned = during my participation in the referenced threads at Ars Technica, I find m= yself back at square one. =A0Instead of trying to guess what hardware suppo= rt KVM & Xen, and vice versa. =A0I'd like to know what hardware KVM= & Xen users are actually using to run KVM & Xen? Particularly with= consideration for 3D gaming and current generation hardware, BTW.
>
> If there is need for further clarification, I'll answer any querie= s you might have.
>
> _______________________________________________
> Xen-users mailing list
> Xen-users@lists.xen.org=
> http://li= sts.xen.org/xen-users

As one of the folks on the list who has done this---probably to= the
most extreme degree---I can tell you it's good stuff. =A0It brings the<= br> joys of datacenter consolidation to your gaming desktop, and also to
your wallet ;)

While my setup is now slightly dated, the 990FX chipset is still at
the top of the AMD offering, so you can shop around on CPUs, and buy a
cheaper "secondary" USB controller if you're not looking to c= ram in a
4-to-1 ratio. =A0I've never had much success passing through the onboar= d
USB from an AMD system, so I highly recommend picking up a little PCIe
x1 controller at the least. =A0That said, I'm convinced that highpoint<= br> has one of the coincidentally-best products on the market for people
looking to do this, but I digress!

Take a look at, specifically, this post I made to the list some months
back, and I'll follow with some errata:
http://lists.xen.org/archives/html/xen-users/2012-05/= msg00328.html

First, I've tested all of the hardware in the build that I
recommended, and indeed ended up building a four-headed unit. It works
like magic. Came in handy a few weeks ago when several of my friends
and I piled into a couple cars for a vacation where we wanted to play
games (yup, we're total nerds), but we couldn't fit four desktop ca= ses
in addition to our stuff in the cars. :)

Second, by the time I got around to building it, the Antec One Hundred
wasn't available. Finding a case that supports 8 expansion slots is a tough thing, but I found another similarly priced one, and it was a
dream to build. =A0I recommend it highly if you think you may want to
max out your slots and/or go deeper down the rabbit hole with
consolidated desktops:
http://www.newegg.com/Product/Product.aspx?Item=3DN82E= 16811112238

Aside from being a very solid case for the price point (good features
for screwless installation as well), to give you an idea of the size,
it is laid out in such a way that I could fit dual-GPU cards in it
(Radeon 5970s). =A0I ultimately had to remove the HDD mounts to pull it
off, but you shouldn't have that problem... Mostly because AMDs dual GPU cards won't work for this, so don't buy one for this build. =A0= It's
a problem with the PCIe switching hardware (well, the firmware
thereof, probably) that they use. =A0I'll save you the rambling, but let's just say that it should work, but doesn't :(

Also, the case does look good! ;)

Finally, and this is unfortunate, for the AMD build, *I* recommend you
use ESXi. While Xen _does_ work with the hardware that I've listed,
I've never been able to get the VMs to work properly with the GPLPV
drivers, and these are crucial to performance. =A0I really, really want
to bring this project back up on Xen though, and will try again now
that 4.2 has gone RTM. =A0If you aren't buying anytime soon and would like to hit me up in a few weeks, by all means drop me a line, and
I'll let you know if I've gotten around to it.


----------------


So, for the Intel route!

Casey DeLorme has, just this week, posted a fantastic set of detailed
videos and documentation on his setup, where he basically does exactly
what you're trying to accomplish. =A0You can find links to all of the documentation, which I'm pretty sure covers his exact hardware, along with videos of the installation process he used and a detailed,
written guide. Fine work if you ask me ;)

http://lists.xen.org/archives/html/xen-users/2012-09/= msg00191.html

As far as his hardware goes, I'm not sure if it's the latest Intel<= br> chips or not. =A0I've been eyeballing the i7-3770 myself (NOT the 3770K= ,
that one will not work, as [in my opinion] Intel has a pension for
artificially crippling their products for profit). =A0Haven't found a board yet, but then again I started eyeballing hardware a day or two
ago.



Cheers,
Andrew Bobulsky

--e89a8fb2038809e60f04ca393414-- --===============4879325329583822335== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users --===============4879325329583822335==-- From xen-users-bounces@lists.xen.org Fri Sep 21 17:03:30 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Fri, 21 Sep 2012 17:03:30 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TF6cX-0005Gc-7n; Fri, 21 Sep 2012 17:02:29 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TF6cV-0005GX-H4 for xen-users@lists.xen.org; Fri, 21 Sep 2012 17:02:27 +0000 Received: from [85.158.139.83:60480] by server-16.bemta-5.messagelabs.com id 70/AC-11718-2AD9C505; Fri, 21 Sep 2012 17:02:26 +0000 X-Env-Sender: cdelorme@gmail.com X-Msg-Ref: server-11.tower-182.messagelabs.com!1348246942!24370219!1 X-Originating-IP: [209.85.219.45] X-SpamReason: No, hits=1.2 required=7.0 tests=HTML_10_20,HTML_MESSAGE, ML_RADAR_SPEW_LINKS_14,RCVD_BY_IP,spamassassin: X-StarScan-Received: X-StarScan-Version: 6.6.1.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 30136 invoked from network); 21 Sep 2012 17:02:24 -0000 Received: from mail-oa0-f45.google.com (HELO mail-oa0-f45.google.com) (209.85.219.45) by server-11.tower-182.messagelabs.com with RC4-SHA encrypted SMTP; 21 Sep 2012 17:02:24 -0000 Received: by oagn12 with SMTP id n12so4574933oag.32 for ; Fri, 21 Sep 2012 10:02:22 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=+LcdGKWIldl/tM0FK8Vbo5qVrZ27eacYhLIzX0Hib9E=; b=ZWGMwtrtcRv1W+RVuSdXY7SwJcKoy2T8feOZZ5KqZGDL7gOekPslu8fRRCMHjBqBaG I6HRD/FXk2zFJpa/WjnJhy6mEf3qYuOf+dbh/g7jIQ6e2BXE7RKKNV7pGd4fVztXlRRz eeFF0daSTpCRer3KEGBJWLnxtTA115qCMXkjJvZ6R/X6wlupYwR8CrtWPnzpbOn+mZLd 6aeLI3ruZJIgWhwffMEU3XbEkL8aKr649Je5xaehdYTlQOYbPZpdUUh0QTOhuoy1kA2b c4u6KZzZMtQGC6Iri9Mz3MG/9tLJtFYi6QKQh1ywpLfd1zcUR/cz8Wx3O5iZeAC2NnuT Tm8Q== MIME-Version: 1.0 Received: by 10.60.22.196 with SMTP id g4mr4430897oef.95.1348246941852; Fri, 21 Sep 2012 10:02:21 -0700 (PDT) Received: by 10.76.19.148 with HTTP; Fri, 21 Sep 2012 10:02:21 -0700 (PDT) In-Reply-To: <-4689096786842132042@unknownmsgid> References: <505B86AE.9040507@earthlink.net> <-4689096786842132042@unknownmsgid> Date: Fri, 21 Sep 2012 13:02:21 -0400 Message-ID: From: Casey DeLorme To: Andrew Bobulsky Cc: "xen-users@lists.xen.org" , ShadesOfGrey , "kvm@vger.kernel.org" Subject: Re: [Xen-users] Recommendations for Virtulization Hardware X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============4879325329583822335==" Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org --===============4879325329583822335== Content-Type: multipart/alternative; boundary=e89a8fb2038809e60f04ca393414 --e89a8fb2038809e60f04ca393414 Content-Type: text/plain; charset=ISO-8859-1 Thanks for the CC Andrew, I responded in private since I didn't want to spam the list. Since we're on the subject of the latest hardware, my system was using a Z68 Motherboard Chipset and Core i7 SandyBridge CPU (2600). I just sold it to a friend and upgraded to the latest. Now running an IvyBridge 3770, Z77 Motherboard Chipset (ASRock Z77 Extreme 9), and similar components for the rest. The Extreme 9 price is extremely high, I wouldn't recommend it unless you have the money, their Z77 Extreme 6 is priced at the same as the Z68 Extreme4 Gen3, and has all the same features plus more USB 3.0. I would give that one a shake if you are looking for newest components. The hardest part of switching from the Extreme4 Gen3 was remapping the USB ports to USB controllers by PCI BDF in Linux, because I haven't found an easy way to do that using the systems information yet. As soon as I'm done putting together the details, I'll append the new hardware information to the wiki. As for changes, the new Z77 chipset has onboard USB 3.0 in exchange for some of the formerly USB 2.0 ports. In my performance demo video I showed that USB 2.0 speeds are sub-par, but even SUB 2.0 devices can hit higher rates when connected to a USB 3.0 port. As far as the IvyBridge CPU, onboard graphics are noticeably better in Dom0, and file decompression in my Windows HVM appears to be faster. I have not run any benchmark tests yet. I compiled the new Xen 4.2 stable, as tagged in the new 4.2 testing branch, but I may try the older revision of Xen in my guide. I am getting an error on the first-launch attempt of any virtual machine with passed devices. When I try again it works, but it's 5 lines worth of errors which makes the following success seem less joyful. I tried kernel 3.5.4, and it appears to be suffering the same passthrough bugs as 3.5.2, so I would avoid 3.5+ still. I ended up with Kernel 3.4.11, which is working. One good bit of news was I kept my SSD, so I was able to just recreate the HVM configuration and launch Windows without problems. Only issues were new drivers, and Windows asking to reactivate due to HW changes. Hope this information helps, ~Casey On Fri, Sep 21, 2012 at 12:30 PM, Andrew Bobulsky wrote: > (CC'ing Casey on this, as I recommend his setup for an Intel-based > solution) > > Hello ShadesOfGrey, > > Hehehe, talk about timing ;) > > On Sep 20, 2012, at 5:15 PM, ShadesOfGrey > wrote: > > > I'm looking to build a new personal computer. I want it to function as > a Linux desktop, provide network services for my home, and lastly, > occasional Windows gaming. From what I've gathered, virtualization using a > Type 1 Hypervisor supporting PCI/VGA pass-through like KVM or Xen would be > an attractive solution for my needs. For reference, reading these threads > on Ars Technica may be helpful to understand where I'm coming from, > http://arstechnica.com/civis/viewtopic.php?f=6&t=1175674 and > http://arstechnica.com/civis/viewtopic.php?f=11&t=1181867. But basically, > I use Linux as my primary OS and would rather avoid dual booting or > building two boxes just to play Windows games when I want to play Windows > games. I'm also intrigued by the concept of virtualization and would like > to experiment with it as a solution for my case. > > > > My problem is isolating which hardware to choose, specifically which > combination of CPU, motherboard and video card. Previously I had been > relying on web searches to glean information from gaming and enthusiast web > sites and tech specs from motherboard manufacturers. After what I learned > during my participation in the referenced threads at Ars Technica, I find > myself back at square one. Instead of trying to guess what hardware > support KVM & Xen, and vice versa. I'd like to know what hardware KVM & > Xen users are actually using to run KVM & Xen? Particularly with > consideration for 3D gaming and current generation hardware, BTW. > > > > If there is need for further clarification, I'll answer any queries you > might have. > > > > _______________________________________________ > > Xen-users mailing list > > Xen-users@lists.xen.org > > http://lists.xen.org/xen-users > > As one of the folks on the list who has done this---probably to the > most extreme degree---I can tell you it's good stuff. It brings the > joys of datacenter consolidation to your gaming desktop, and also to > your wallet ;) > > While my setup is now slightly dated, the 990FX chipset is still at > the top of the AMD offering, so you can shop around on CPUs, and buy a > cheaper "secondary" USB controller if you're not looking to cram in a > 4-to-1 ratio. I've never had much success passing through the onboard > USB from an AMD system, so I highly recommend picking up a little PCIe > x1 controller at the least. That said, I'm convinced that highpoint > has one of the coincidentally-best products on the market for people > looking to do this, but I digress! > > Take a look at, specifically, this post I made to the list some months > back, and I'll follow with some errata: > http://lists.xen.org/archives/html/xen-users/2012-05/msg00328.html > > First, I've tested all of the hardware in the build that I > recommended, and indeed ended up building a four-headed unit. It works > like magic. Came in handy a few weeks ago when several of my friends > and I piled into a couple cars for a vacation where we wanted to play > games (yup, we're total nerds), but we couldn't fit four desktop cases > in addition to our stuff in the cars. :) > > Second, by the time I got around to building it, the Antec One Hundred > wasn't available. Finding a case that supports 8 expansion slots is a > tough thing, but I found another similarly priced one, and it was a > dream to build. I recommend it highly if you think you may want to > max out your slots and/or go deeper down the rabbit hole with > consolidated desktops: > http://www.newegg.com/Product/Product.aspx?Item=N82E16811112238 > > Aside from being a very solid case for the price point (good features > for screwless installation as well), to give you an idea of the size, > it is laid out in such a way that I could fit dual-GPU cards in it > (Radeon 5970s). I ultimately had to remove the HDD mounts to pull it > off, but you shouldn't have that problem... Mostly because AMDs dual > GPU cards won't work for this, so don't buy one for this build. It's > a problem with the PCIe switching hardware (well, the firmware > thereof, probably) that they use. I'll save you the rambling, but > let's just say that it should work, but doesn't :( > > Also, the case does look good! ;) > > Finally, and this is unfortunate, for the AMD build, *I* recommend you > use ESXi. While Xen _does_ work with the hardware that I've listed, > I've never been able to get the VMs to work properly with the GPLPV > drivers, and these are crucial to performance. I really, really want > to bring this project back up on Xen though, and will try again now > that 4.2 has gone RTM. If you aren't buying anytime soon and would > like to hit me up in a few weeks, by all means drop me a line, and > I'll let you know if I've gotten around to it. > > > ---------------- > > > So, for the Intel route! > > Casey DeLorme has, just this week, posted a fantastic set of detailed > videos and documentation on his setup, where he basically does exactly > what you're trying to accomplish. You can find links to all of the > documentation, which I'm pretty sure covers his exact hardware, along > with videos of the installation process he used and a detailed, > written guide. Fine work if you ask me ;) > > http://lists.xen.org/archives/html/xen-users/2012-09/msg00191.html > > As far as his hardware goes, I'm not sure if it's the latest Intel > chips or not. I've been eyeballing the i7-3770 myself (NOT the 3770K, > that one will not work, as [in my opinion] Intel has a pension for > artificially crippling their products for profit). Haven't found a > board yet, but then again I started eyeballing hardware a day or two > ago. > > > > Cheers, > Andrew Bobulsky > --e89a8fb2038809e60f04ca393414 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable
Thanks for the CC Andrew,

I responded in= private since I didn't want to spam the list.

Since we're on the subject of the latest hardware, my system was using= a Z68 Motherboard Chipset and Core i7 SandyBridge CPU (2600). =A0I just so= ld it to a friend and upgraded to the latest.

Now running an IvyBridge 3770, Z77 Motherboard Chipset = (ASRock Z77 Extreme 9), and similar components for the rest. =A0The Extreme= 9 price is extremely high, I wouldn't recommend it unless you have the= money, their Z77 Extreme 6 is priced at the same as the Z68 Extreme4 Gen3,= and has all the same features plus more USB 3.0. =A0I would give that one = a shake if you are looking for newest components. =A0The hardest part of sw= itching from the Extreme4 Gen3 was remapping the USB ports to USB controlle= rs by PCI BDF in Linux, because I haven't found an easy way to do that = using the systems information yet.

As soon as I'm done putting together the details, I= 'll append the new hardware information to the wiki.

As for changes, the new Z77 chipset has onboard USB 3.0 in exchange = for some of the formerly USB 2.0 ports. =A0In my performance demo video I s= howed that USB 2.0 speeds are sub-par, but even SUB 2.0 devices can hit hig= her rates when connected to a USB 3.0 port. =A0As far as the IvyBridge CPU,= onboard graphics are noticeably better in Dom0, and file decompression in = my Windows HVM appears to be faster. =A0I have not run any benchmark tests = yet.


I compiled the new Xen 4.2 stable, as ta= gged in the new 4.2 testing branch, but I may try the older revision of Xen= in my guide. =A0I am getting an error on the first-launch attempt of any v= irtual machine with passed devices. =A0When I try again it works, but it= 9;s 5 lines worth of errors which makes the following success seem less joy= ful.

I tried kernel 3.5.4, and it appears to be suffering th= e same passthrough bugs as 3.5.2, so I would avoid 3.5+ still. =A0I ended u= p with Kernel 3.4.11, which is working.

One good b= it of news was I kept my SSD, so I was able to just recreate the HVM config= uration and launch Windows without problems. =A0Only issues were new driver= s, and Windows asking to reactivate due to HW changes.


Hope this information helps,
=

~Casey

On= Fri, Sep 21, 2012 at 12:30 PM, Andrew Bobulsky <rulerof@gmail.com>= wrote:
(CC'ing Casey on this, as I recommend hi= s setup for an Intel-based solution)

Hello ShadesOfGrey,

Hehehe, talk about timing ;)

On Sep 20, 2012, at 5:15 PM, ShadesOfGrey <shades_of_grey@earthlink.net> wrote:

> I'm looking to build a new personal computer. =A0I want it to func= tion as a Linux desktop, provide network services for my home, and lastly, = occasional Windows gaming. =A0From what I've gathered, virtualization u= sing a Type 1 Hypervisor supporting PCI/VGA pass-through like KVM or Xen wo= uld be an attractive solution for my needs. =A0For reference, reading these= threads on Ars Technica may be helpful to understand where I'm coming = from, http://arstechnica.com/civis/viewtopic.php?f=3D6&= amp;t=3D1175674 and http://arstechnica.com/civis/v= iewtopic.php?f=3D11&t=3D1181867. But basically, I use Linux as my p= rimary OS and would rather avoid dual booting or building two boxes just to= play Windows games when I want to play Windows games. =A0I'm also intr= igued by the concept of virtualization and would like to experiment with it= as a solution for my case.
>
> My problem is isolating which hardware to choose, specifically which c= ombination of CPU, motherboard and video card. =A0Previously I had been rel= ying on web searches to glean information from gaming and enthusiast web si= tes and tech specs from motherboard manufacturers. =A0After what I learned = during my participation in the referenced threads at Ars Technica, I find m= yself back at square one. =A0Instead of trying to guess what hardware suppo= rt KVM & Xen, and vice versa. =A0I'd like to know what hardware KVM= & Xen users are actually using to run KVM & Xen? Particularly with= consideration for 3D gaming and current generation hardware, BTW.
>
> If there is need for further clarification, I'll answer any querie= s you might have.
>
> _______________________________________________
> Xen-users mailing list
> Xen-users@lists.xen.org=
> http://li= sts.xen.org/xen-users

As one of the folks on the list who has done this---probably to= the
most extreme degree---I can tell you it's good stuff. =A0It brings the<= br> joys of datacenter consolidation to your gaming desktop, and also to
your wallet ;)

While my setup is now slightly dated, the 990FX chipset is still at
the top of the AMD offering, so you can shop around on CPUs, and buy a
cheaper "secondary" USB controller if you're not looking to c= ram in a
4-to-1 ratio. =A0I've never had much success passing through the onboar= d
USB from an AMD system, so I highly recommend picking up a little PCIe
x1 controller at the least. =A0That said, I'm convinced that highpoint<= br> has one of the coincidentally-best products on the market for people
looking to do this, but I digress!

Take a look at, specifically, this post I made to the list some months
back, and I'll follow with some errata:
http://lists.xen.org/archives/html/xen-users/2012-05/= msg00328.html

First, I've tested all of the hardware in the build that I
recommended, and indeed ended up building a four-headed unit. It works
like magic. Came in handy a few weeks ago when several of my friends
and I piled into a couple cars for a vacation where we wanted to play
games (yup, we're total nerds), but we couldn't fit four desktop ca= ses
in addition to our stuff in the cars. :)

Second, by the time I got around to building it, the Antec One Hundred
wasn't available. Finding a case that supports 8 expansion slots is a tough thing, but I found another similarly priced one, and it was a
dream to build. =A0I recommend it highly if you think you may want to
max out your slots and/or go deeper down the rabbit hole with
consolidated desktops:
http://www.newegg.com/Product/Product.aspx?Item=3DN82E= 16811112238

Aside from being a very solid case for the price point (good features
for screwless installation as well), to give you an idea of the size,
it is laid out in such a way that I could fit dual-GPU cards in it
(Radeon 5970s). =A0I ultimately had to remove the HDD mounts to pull it
off, but you shouldn't have that problem... Mostly because AMDs dual GPU cards won't work for this, so don't buy one for this build. =A0= It's
a problem with the PCIe switching hardware (well, the firmware
thereof, probably) that they use. =A0I'll save you the rambling, but let's just say that it should work, but doesn't :(

Also, the case does look good! ;)

Finally, and this is unfortunate, for the AMD build, *I* recommend you
use ESXi. While Xen _does_ work with the hardware that I've listed,
I've never been able to get the VMs to work properly with the GPLPV
drivers, and these are crucial to performance. =A0I really, really want
to bring this project back up on Xen though, and will try again now
that 4.2 has gone RTM. =A0If you aren't buying anytime soon and would like to hit me up in a few weeks, by all means drop me a line, and
I'll let you know if I've gotten around to it.


----------------


So, for the Intel route!

Casey DeLorme has, just this week, posted a fantastic set of detailed
videos and documentation on his setup, where he basically does exactly
what you're trying to accomplish. =A0You can find links to all of the documentation, which I'm pretty sure covers his exact hardware, along with videos of the installation process he used and a detailed,
written guide. Fine work if you ask me ;)

http://lists.xen.org/archives/html/xen-users/2012-09/= msg00191.html

As far as his hardware goes, I'm not sure if it's the latest Intel<= br> chips or not. =A0I've been eyeballing the i7-3770 myself (NOT the 3770K= ,
that one will not work, as [in my opinion] Intel has a pension for
artificially crippling their products for profit). =A0Haven't found a board yet, but then again I started eyeballing hardware a day or two
ago.



Cheers,
Andrew Bobulsky

--e89a8fb2038809e60f04ca393414-- --===============4879325329583822335== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users --===============4879325329583822335==-- From xen-users-bounces@lists.xen.org Fri Sep 21 17:21:02 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Fri, 21 Sep 2012 17:21:02 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TF6tZ-0005ul-Ts; Fri, 21 Sep 2012 17:20:05 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TF6tX-0005ug-Vp for xen-users@lists.xen.org; Fri, 21 Sep 2012 17:20:04 +0000 Received: from [85.158.143.35:48717] by server-1.bemta-4.messagelabs.com id E6/25-05684-3C1AC505; Fri, 21 Sep 2012 17:20:03 +0000 X-Env-Sender: al@ohosting.org.ua X-Msg-Ref: server-16.tower-21.messagelabs.com!1348248001!13139405!1 X-Originating-IP: [195.248.169.244] X-SpamReason: No, hits=0.6 required=7.0 tests=HTML_40_50,HTML_MESSAGE X-StarScan-Received: X-StarScan-Version: 6.6.1.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 25288 invoked from network); 21 Sep 2012 17:20:02 -0000 Received: from ohosting.org.ua (HELO c2.ohosting.org.ua) (195.248.169.244) by server-16.tower-21.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 21 Sep 2012 17:20:02 -0000 Received: from wixen2 (100.197.151.178.triolan.net [178.151.197.100] (may be forged)) (authenticated bits=0) by c2.ohosting.org.ua (8.14.5/8.14.5) with ESMTP id q8LHJWlM022975 for ; Fri, 21 Sep 2012 20:19:32 +0300 Message-ID: <16FF8151C9424E26BA080528790E8B5D@wixen2> From: "Likarpenkov Alexander" To: Date: Fri, 21 Sep 2012 20:18:10 +0300 MIME-Version: 1.0 X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Windows Mail 6.0.6002.18005 X-MimeOLE: Produced By Microsoft MimeOLE V6.1.7601.17609 Subject: [Xen-users] Which version of the kernel to choose for stable VGA/PCI/USB Pass passthrough (Konrad, Jeremy or other) X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============2585555346962625350==" Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org This is a multi-part message in MIME format. --===============2585555346962625350== Content-Type: multipart/alternative; boundary="----=_NextPart_000_007A_01CD9836.384EB2B0" This is a multi-part message in MIME format. ------=_NextPart_000_007A_01CD9836.384EB2B0 Content-Type: text/plain; charset="koi8-r" Content-Transfer-Encoding: quoted-printable My latest stable production release is: 2.6.32.48 and xen 4.1.2 on = ubuntu 10.10 x64 was 9 months and again it's time to try the new version. Yesterday = installed ubuntu 4.12 and xen4.2.=20 Old configs work immediately with both xm and with xl manager correctly. = Standard kernel 3.2.0-29-generic. The last time I download the kernel using git #git clone git://git.kernel.org/pub/scm/linux/kernel/git/jeremy/xen.git = jeremy #git tag | grep '3 \. ' v3.0 v3.0-rc1 v3.0-rc2 v3.0-rc3 v3.0-rc4 v3.0-rc5 v3.0-rc6 v3.0-rc7 v3.1-rc1 v3.1-rc2 v3.1-rc3 v3.1-rc4 v3.1-rc5 v3.1-rc6 v3.1-rc7 v3.1-rc8 v3.1-rc9 #git clone git://git.kernel.org/pub/scm/linux/kernel/git/konrad/xen.git = konrad #git tag | grep '3\.' 3.3-with-some-3.4-patches stable/for-jens-3.4-tag stable/for-linus-3.4-rc1-tag stable/for-linus-3.4-rc3-tag stable/for-linus-3.4-rc4-tag stable/for-linus-3.4-rc6-tag stable/for-linus-3.4-tag stable/for-linus-3.4-tag-two stable/for-linus-3.5-rc0-tag stable/for-linus-3.5-rc2-tag stable/for-linus-3.6-rc0-tag stable/for-linus-3.6-rc1-tag stable/for-linus-3.6-rc3-tag stable/for-linus-3.6-rc4-tag stable/for-linus-3.6-rc6-tag stable/for-linus-fixes-3.3-rc3 stable/for-linus-fixes-3.3-rc5 testing-3.5-with-extra v3.0 v3.0-rc1 v3.0-rc2 v3.0-rc3 v3.0-rc4 v3.0-rc5 v3.0-rc6 v3.0-rc7 v3.1-rc1 v3.1-rc10 v3.1-rc2 v3.1-rc3 v3.1-rc4 v3.1-rc5 v3.1-rc6 v3.1-rc7 v3.1-rc8 v3.1-rc9 The question is: which version and from what source to take to get a working stable = kernel for VGA / PCI / USB Pass passthrough? ------=_NextPart_000_007A_01CD9836.384EB2B0 Content-Type: text/html; charset="koi8-r" Content-Transfer-Encoding: quoted-printable
My latest stable = production release is:=20 2.6.32.48 and xen 4.1.2 on ubuntu 10.10 x64
 
was 9 months and again it's time to try = the new=20 version. Yesterday installed ubuntu 4.12 and xen4.2.
Old configs = work=20 immediately with both xm and with xl manager correctly.
Standard = kernel=20 3.2.0-29-generic.
The last time I download the kernel using git

#git clone=20 git://git.kernel.org/pub/scm/linux/kernel/git/jeremy/xen.git = jeremy
#git tag=20 | grep '3 \.=20 '
 v3.0
 v3.0-rc1
 v3.0-rc2
 v3.0-rc3
=  v3.0-rc4
 v3.0-rc5
 v3.0-rc6
 v3.0-rc7
&= nbsp;v3.1-rc1
 v3.1-rc2
 v3.1-rc3
 v3.1-rc4
&n= bsp;v3.1-rc5
 v3.1-rc6
 v3.1-rc7
 v3.1-rc8
&nb= sp;v3.1-rc9
 
#git clone = git://git.kernel.org/pub/scm/linux/kernel/git/konrad/xen.git=20 konrad
#git tag | grep=20 '3\.'
3.3-with-some-3.4-patches
stable/for-jens-3.4-tag
stable/f= or-linus-3.4-rc1-tag
stable/for-linus-3.4-rc3-tag
stable/for-linus-= 3.4-rc4-tag
stable/for-linus-3.4-rc6-tag
stable/for-linus-3.4-tagstable/for-linus-3.4-tag-two
stable/for-linus-3.5-rc0-tag
stable/= for-linus-3.5-rc2-tag
stable/for-linus-3.6-rc0-tag
stable/for-linus= -3.6-rc1-tag
stable/for-linus-3.6-rc3-tag
stable/for-linus-3.6-rc4-= tag
stable/for-linus-3.6-rc6-tag
stable/for-linus-fixes-3.3-rc3
= stable/for-linus-fixes-3.3-rc5
testing-3.5-with-extra
v3.0
v3.0-= rc1
v3.0-rc2
v3.0-rc3
v3.0-rc4
v3.0-rc5
v3.0-rc6
v3.0-r= c7
v3.1-rc1
v3.1-rc10
v3.1-rc2
v3.1-rc3
v3.1-rc4
v3.1-r= c5
v3.1-rc6
v3.1-rc7
v3.1-rc8
v3.1-rc9
 
The question is:
which version and from what source to take to = get a=20 working stable kernel for VGA / PCI / USB Pass passthrough?
 
 
 
------=_NextPart_000_007A_01CD9836.384EB2B0-- --===============2585555346962625350== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users --===============2585555346962625350==-- From xen-users-bounces@lists.xen.org Fri Sep 21 17:21:02 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Fri, 21 Sep 2012 17:21:02 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TF6tZ-0005ul-Ts; Fri, 21 Sep 2012 17:20:05 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TF6tX-0005ug-Vp for xen-users@lists.xen.org; Fri, 21 Sep 2012 17:20:04 +0000 Received: from [85.158.143.35:48717] by server-1.bemta-4.messagelabs.com id E6/25-05684-3C1AC505; Fri, 21 Sep 2012 17:20:03 +0000 X-Env-Sender: al@ohosting.org.ua X-Msg-Ref: server-16.tower-21.messagelabs.com!1348248001!13139405!1 X-Originating-IP: [195.248.169.244] X-SpamReason: No, hits=0.6 required=7.0 tests=HTML_40_50,HTML_MESSAGE X-StarScan-Received: X-StarScan-Version: 6.6.1.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 25288 invoked from network); 21 Sep 2012 17:20:02 -0000 Received: from ohosting.org.ua (HELO c2.ohosting.org.ua) (195.248.169.244) by server-16.tower-21.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 21 Sep 2012 17:20:02 -0000 Received: from wixen2 (100.197.151.178.triolan.net [178.151.197.100] (may be forged)) (authenticated bits=0) by c2.ohosting.org.ua (8.14.5/8.14.5) with ESMTP id q8LHJWlM022975 for ; Fri, 21 Sep 2012 20:19:32 +0300 Message-ID: <16FF8151C9424E26BA080528790E8B5D@wixen2> From: "Likarpenkov Alexander" To: Date: Fri, 21 Sep 2012 20:18:10 +0300 MIME-Version: 1.0 X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Windows Mail 6.0.6002.18005 X-MimeOLE: Produced By Microsoft MimeOLE V6.1.7601.17609 Subject: [Xen-users] Which version of the kernel to choose for stable VGA/PCI/USB Pass passthrough (Konrad, Jeremy or other) X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============2585555346962625350==" Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org This is a multi-part message in MIME format. --===============2585555346962625350== Content-Type: multipart/alternative; boundary="----=_NextPart_000_007A_01CD9836.384EB2B0" This is a multi-part message in MIME format. ------=_NextPart_000_007A_01CD9836.384EB2B0 Content-Type: text/plain; charset="koi8-r" Content-Transfer-Encoding: quoted-printable My latest stable production release is: 2.6.32.48 and xen 4.1.2 on = ubuntu 10.10 x64 was 9 months and again it's time to try the new version. Yesterday = installed ubuntu 4.12 and xen4.2.=20 Old configs work immediately with both xm and with xl manager correctly. = Standard kernel 3.2.0-29-generic. The last time I download the kernel using git #git clone git://git.kernel.org/pub/scm/linux/kernel/git/jeremy/xen.git = jeremy #git tag | grep '3 \. ' v3.0 v3.0-rc1 v3.0-rc2 v3.0-rc3 v3.0-rc4 v3.0-rc5 v3.0-rc6 v3.0-rc7 v3.1-rc1 v3.1-rc2 v3.1-rc3 v3.1-rc4 v3.1-rc5 v3.1-rc6 v3.1-rc7 v3.1-rc8 v3.1-rc9 #git clone git://git.kernel.org/pub/scm/linux/kernel/git/konrad/xen.git = konrad #git tag | grep '3\.' 3.3-with-some-3.4-patches stable/for-jens-3.4-tag stable/for-linus-3.4-rc1-tag stable/for-linus-3.4-rc3-tag stable/for-linus-3.4-rc4-tag stable/for-linus-3.4-rc6-tag stable/for-linus-3.4-tag stable/for-linus-3.4-tag-two stable/for-linus-3.5-rc0-tag stable/for-linus-3.5-rc2-tag stable/for-linus-3.6-rc0-tag stable/for-linus-3.6-rc1-tag stable/for-linus-3.6-rc3-tag stable/for-linus-3.6-rc4-tag stable/for-linus-3.6-rc6-tag stable/for-linus-fixes-3.3-rc3 stable/for-linus-fixes-3.3-rc5 testing-3.5-with-extra v3.0 v3.0-rc1 v3.0-rc2 v3.0-rc3 v3.0-rc4 v3.0-rc5 v3.0-rc6 v3.0-rc7 v3.1-rc1 v3.1-rc10 v3.1-rc2 v3.1-rc3 v3.1-rc4 v3.1-rc5 v3.1-rc6 v3.1-rc7 v3.1-rc8 v3.1-rc9 The question is: which version and from what source to take to get a working stable = kernel for VGA / PCI / USB Pass passthrough? ------=_NextPart_000_007A_01CD9836.384EB2B0 Content-Type: text/html; charset="koi8-r" Content-Transfer-Encoding: quoted-printable
My latest stable = production release is:=20 2.6.32.48 and xen 4.1.2 on ubuntu 10.10 x64
 
was 9 months and again it's time to try = the new=20 version. Yesterday installed ubuntu 4.12 and xen4.2.
Old configs = work=20 immediately with both xm and with xl manager correctly.
Standard = kernel=20 3.2.0-29-generic.
The last time I download the kernel using git

#git clone=20 git://git.kernel.org/pub/scm/linux/kernel/git/jeremy/xen.git = jeremy
#git tag=20 | grep '3 \.=20 '
 v3.0
 v3.0-rc1
 v3.0-rc2
 v3.0-rc3
=  v3.0-rc4
 v3.0-rc5
 v3.0-rc6
 v3.0-rc7
&= nbsp;v3.1-rc1
 v3.1-rc2
 v3.1-rc3
 v3.1-rc4
&n= bsp;v3.1-rc5
 v3.1-rc6
 v3.1-rc7
 v3.1-rc8
&nb= sp;v3.1-rc9
 
#git clone = git://git.kernel.org/pub/scm/linux/kernel/git/konrad/xen.git=20 konrad
#git tag | grep=20 '3\.'
3.3-with-some-3.4-patches
stable/for-jens-3.4-tag
stable/f= or-linus-3.4-rc1-tag
stable/for-linus-3.4-rc3-tag
stable/for-linus-= 3.4-rc4-tag
stable/for-linus-3.4-rc6-tag
stable/for-linus-3.4-tagstable/for-linus-3.4-tag-two
stable/for-linus-3.5-rc0-tag
stable/= for-linus-3.5-rc2-tag
stable/for-linus-3.6-rc0-tag
stable/for-linus= -3.6-rc1-tag
stable/for-linus-3.6-rc3-tag
stable/for-linus-3.6-rc4-= tag
stable/for-linus-3.6-rc6-tag
stable/for-linus-fixes-3.3-rc3
= stable/for-linus-fixes-3.3-rc5
testing-3.5-with-extra
v3.0
v3.0-= rc1
v3.0-rc2
v3.0-rc3
v3.0-rc4
v3.0-rc5
v3.0-rc6
v3.0-r= c7
v3.1-rc1
v3.1-rc10
v3.1-rc2
v3.1-rc3
v3.1-rc4
v3.1-r= c5
v3.1-rc6
v3.1-rc7
v3.1-rc8
v3.1-rc9
 
The question is:
which version and from what source to take to = get a=20 working stable kernel for VGA / PCI / USB Pass passthrough?
 
 
 
------=_NextPart_000_007A_01CD9836.384EB2B0-- --===============2585555346962625350== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users --===============2585555346962625350==-- From xen-users-bounces@lists.xen.org Fri Sep 21 17:36:02 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Fri, 21 Sep 2012 17:36:02 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TF78D-0006aT-IM; Fri, 21 Sep 2012 17:35:13 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TF78B-0006aO-FJ for xen-users@lists.xen.org; Fri, 21 Sep 2012 17:35:11 +0000 Received: from [85.158.139.83:53608] by server-12.bemta-5.messagelabs.com id B0/8D-22670-E45AC505; Fri, 21 Sep 2012 17:35:10 +0000 X-Env-Sender: james-xen@dingwall.me.uk X-Msg-Ref: server-4.tower-182.messagelabs.com!1348248909!27058591!1 X-Originating-IP: [81.103.221.48] X-SpamReason: No, hits=0.5 required=7.0 tests=BODY_RANDOM_LONG X-StarScan-Received: X-StarScan-Version: 6.6.1.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 21699 invoked from network); 21 Sep 2012 17:35:09 -0000 Received: from mtaout02-winn.ispmail.ntl.com (HELO mtaout02-winn.ispmail.ntl.com) (81.103.221.48) by server-4.tower-182.messagelabs.com with SMTP; 21 Sep 2012 17:35:09 -0000 Received: from know-smtpout-1.server.virginmedia.net ([62.254.123.4]) by mtaout02-winn.ispmail.ntl.com (InterMail vM.7.08.04.00 201-2186-134-20080326) with ESMTP id <20120921173509.DCBV1732.mtaout02-winn.ispmail.ntl.com@know-smtpout-1.server.virginmedia.net> for ; Fri, 21 Sep 2012 18:35:09 +0100 Received: from [82.32.104.97] (helo=dingwall.me.uk) by know-smtpout-1.server.virginmedia.net with esmtp (Exim 4.63) (envelope-from ) id 1TF76U-0007wR-DR for xen-users@lists.xen.org; Fri, 21 Sep 2012 18:33:26 +0100 Received: (qmail 8165 invoked from network); 21 Sep 2012 17:33:26 -0000 Received: from apache0.xen.dingwall.me.uk (HELO webmail.private.dingwall.me.uk) (192.168.1.35) by mail0.xen.dingwall.me.uk with SMTP; 21 Sep 2012 17:33:26 -0000 MIME-Version: 1.0 Date: Fri, 21 Sep 2012 18:33:26 +0100 From: James Dingwall To: Message-ID: <8ec6beeb954eedd1c295135653ccdd56@imap.dingwall.me.uk> X-Sender: james-xen@dingwall.me.uk User-Agent: Roundcube Webmail/0.8.1 X-Cloudmark-Analysis: v=1.1 cv=AUhbpHVS+xhHrj9wLCYAQoYnFLYUZdbP8UM0GmH2jwk= c=1 sm=0 a=LJ0inPZW_QAA:10 a=YlJ9p4b1FGEA:10 a=IkcTkHD0fZMA:10 a=8dh4EtM8HNnLMrmA_DQA:9 a=QEXdDO2ut3YA:10 a=HpAAvcLHHh0Zw7uRqdWCyQ==:117 Subject: [Xen-users] Xen 4.2.0 - CPU Frequency Scaling X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset="us-ascii"; Format="flowed" Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org Hi, This has been a problem since the xen-acpi-processor code was added to the kernel source. I wasn't sure if the problem I was seeing was related to the old version (4.1.2) of Xen that I was using but now I'm on 4.2.0 and it still exists I thought I would check if I have a misconfiguration or if I have discovered a problem. My system is a dual AMD Opteron(tm) Processor 2423 HE on Linux kernel 3.4.8. The xen command line is: console=vga,com2 com2=115200,8n1 dom0_mem=max:2048M dom0_max_vcpus=2 dom0_vcpus_pin The CPU scaling information reported by xenpm is below. The problem is that only cpuid 1 can be managed separately, all the others are bundled together and cannot be handled independently which used to be possible with the old xen kernel. If further information would be useful please let me know. Thanks, James # xenpm get-cpufreq-para cpu id : 0 affected_cpus : 0 2 3 4 5 6 7 8 9 10 11 cpuinfo frequency : max [2000000] min [800000] cur [800000] scaling_driver : scaling_avail_gov : userspace performance powersave ondemand current_governor : ondemand ondemand specific : sampling_rate : max [10000000] min [10000] cur [20000] up_threshold : 80 scaling_avail_freq : 2000000 1500000 1300000 1000000 *800000 scaling frequency : max [2000000] min [800000] cur [800000] cpu id : 1 affected_cpus : 1 cpuinfo frequency : max [2000000] min [800000] cur [800000] scaling_driver : scaling_avail_gov : userspace performance powersave ondemand current_governor : ondemand ondemand specific : sampling_rate : max [10000000] min [10000] cur [20000] up_threshold : 80 scaling_avail_freq : 2000000 1500000 1300000 1000000 *800000 scaling frequency : max [2000000] min [800000] cur [800000] cpu id : 2 affected_cpus : 0 2 3 4 5 6 7 8 9 10 11 cpuinfo frequency : max [2000000] min [800000] cur [800000] scaling_driver : scaling_avail_gov : userspace performance powersave ondemand current_governor : ondemand ondemand specific : sampling_rate : max [10000000] min [10000] cur [20000] up_threshold : 80 scaling_avail_freq : 2000000 1500000 1300000 1000000 *800000 scaling frequency : max [2000000] min [800000] cur [800000] cpu id : 3 affected_cpus : 0 2 3 4 5 6 7 8 9 10 11 cpuinfo frequency : max [2000000] min [800000] cur [800000] scaling_driver : scaling_avail_gov : userspace performance powersave ondemand current_governor : ondemand ondemand specific : sampling_rate : max [10000000] min [10000] cur [20000] up_threshold : 80 scaling_avail_freq : 2000000 1500000 1300000 1000000 *800000 scaling frequency : max [2000000] min [800000] cur [800000] cpu id : 4 affected_cpus : 0 2 3 4 5 6 7 8 9 10 11 cpuinfo frequency : max [2000000] min [800000] cur [800000] scaling_driver : scaling_avail_gov : userspace performance powersave ondemand current_governor : ondemand ondemand specific : sampling_rate : max [10000000] min [10000] cur [20000] up_threshold : 80 scaling_avail_freq : 2000000 1500000 1300000 1000000 *800000 scaling frequency : max [2000000] min [800000] cur [800000] cpu id : 5 affected_cpus : 0 2 3 4 5 6 7 8 9 10 11 cpuinfo frequency : max [2000000] min [800000] cur [800000] scaling_driver : scaling_avail_gov : userspace performance powersave ondemand current_governor : ondemand ondemand specific : sampling_rate : max [10000000] min [10000] cur [20000] up_threshold : 80 scaling_avail_freq : 2000000 1500000 1300000 1000000 *800000 scaling frequency : max [2000000] min [800000] cur [800000] cpu id : 6 affected_cpus : 0 2 3 4 5 6 7 8 9 10 11 cpuinfo frequency : max [2000000] min [800000] cur [800000] scaling_driver : scaling_avail_gov : userspace performance powersave ondemand current_governor : ondemand ondemand specific : sampling_rate : max [10000000] min [10000] cur [20000] up_threshold : 80 scaling_avail_freq : 2000000 1500000 1300000 1000000 *800000 scaling frequency : max [2000000] min [800000] cur [800000] cpu id : 7 affected_cpus : 0 2 3 4 5 6 7 8 9 10 11 cpuinfo frequency : max [2000000] min [800000] cur [800000] scaling_driver : scaling_avail_gov : userspace performance powersave ondemand current_governor : ondemand ondemand specific : sampling_rate : max [10000000] min [10000] cur [20000] up_threshold : 80 scaling_avail_freq : 2000000 1500000 1300000 1000000 *800000 scaling frequency : max [2000000] min [800000] cur [800000] cpu id : 8 affected_cpus : 0 2 3 4 5 6 7 8 9 10 11 cpuinfo frequency : max [2000000] min [800000] cur [800000] scaling_driver : scaling_avail_gov : userspace performance powersave ondemand current_governor : ondemand ondemand specific : sampling_rate : max [10000000] min [10000] cur [20000] up_threshold : 80 scaling_avail_freq : 2000000 1500000 1300000 1000000 *800000 scaling frequency : max [2000000] min [800000] cur [800000] cpu id : 9 affected_cpus : 0 2 3 4 5 6 7 8 9 10 11 cpuinfo frequency : max [2000000] min [800000] cur [800000] scaling_driver : scaling_avail_gov : userspace performance powersave ondemand current_governor : ondemand ondemand specific : sampling_rate : max [10000000] min [10000] cur [20000] up_threshold : 80 scaling_avail_freq : 2000000 1500000 1300000 1000000 *800000 scaling frequency : max [2000000] min [800000] cur [800000] cpu id : 10 affected_cpus : 0 2 3 4 5 6 7 8 9 10 11 cpuinfo frequency : max [2000000] min [800000] cur [800000] scaling_driver : scaling_avail_gov : userspace performance powersave ondemand current_governor : ondemand ondemand specific : sampling_rate : max [10000000] min [10000] cur [20000] up_threshold : 80 scaling_avail_freq : 2000000 1500000 1300000 1000000 *800000 scaling frequency : max [2000000] min [800000] cur [800000] cpu id : 11 affected_cpus : 0 2 3 4 5 6 7 8 9 10 11 cpuinfo frequency : max [2000000] min [800000] cur [800000] scaling_driver : scaling_avail_gov : userspace performance powersave ondemand current_governor : ondemand ondemand specific : sampling_rate : max [10000000] min [10000] cur [20000] up_threshold : 80 scaling_avail_freq : 2000000 1500000 1300000 1000000 *800000 scaling frequency : max [2000000] min [800000] cur [800000] _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Fri Sep 21 17:36:02 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Fri, 21 Sep 2012 17:36:02 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TF78D-0006aT-IM; Fri, 21 Sep 2012 17:35:13 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TF78B-0006aO-FJ for xen-users@lists.xen.org; Fri, 21 Sep 2012 17:35:11 +0000 Received: from [85.158.139.83:53608] by server-12.bemta-5.messagelabs.com id B0/8D-22670-E45AC505; Fri, 21 Sep 2012 17:35:10 +0000 X-Env-Sender: james-xen@dingwall.me.uk X-Msg-Ref: server-4.tower-182.messagelabs.com!1348248909!27058591!1 X-Originating-IP: [81.103.221.48] X-SpamReason: No, hits=0.5 required=7.0 tests=BODY_RANDOM_LONG X-StarScan-Received: X-StarScan-Version: 6.6.1.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 21699 invoked from network); 21 Sep 2012 17:35:09 -0000 Received: from mtaout02-winn.ispmail.ntl.com (HELO mtaout02-winn.ispmail.ntl.com) (81.103.221.48) by server-4.tower-182.messagelabs.com with SMTP; 21 Sep 2012 17:35:09 -0000 Received: from know-smtpout-1.server.virginmedia.net ([62.254.123.4]) by mtaout02-winn.ispmail.ntl.com (InterMail vM.7.08.04.00 201-2186-134-20080326) with ESMTP id <20120921173509.DCBV1732.mtaout02-winn.ispmail.ntl.com@know-smtpout-1.server.virginmedia.net> for ; Fri, 21 Sep 2012 18:35:09 +0100 Received: from [82.32.104.97] (helo=dingwall.me.uk) by know-smtpout-1.server.virginmedia.net with esmtp (Exim 4.63) (envelope-from ) id 1TF76U-0007wR-DR for xen-users@lists.xen.org; Fri, 21 Sep 2012 18:33:26 +0100 Received: (qmail 8165 invoked from network); 21 Sep 2012 17:33:26 -0000 Received: from apache0.xen.dingwall.me.uk (HELO webmail.private.dingwall.me.uk) (192.168.1.35) by mail0.xen.dingwall.me.uk with SMTP; 21 Sep 2012 17:33:26 -0000 MIME-Version: 1.0 Date: Fri, 21 Sep 2012 18:33:26 +0100 From: James Dingwall To: Message-ID: <8ec6beeb954eedd1c295135653ccdd56@imap.dingwall.me.uk> X-Sender: james-xen@dingwall.me.uk User-Agent: Roundcube Webmail/0.8.1 X-Cloudmark-Analysis: v=1.1 cv=AUhbpHVS+xhHrj9wLCYAQoYnFLYUZdbP8UM0GmH2jwk= c=1 sm=0 a=LJ0inPZW_QAA:10 a=YlJ9p4b1FGEA:10 a=IkcTkHD0fZMA:10 a=8dh4EtM8HNnLMrmA_DQA:9 a=QEXdDO2ut3YA:10 a=HpAAvcLHHh0Zw7uRqdWCyQ==:117 Subject: [Xen-users] Xen 4.2.0 - CPU Frequency Scaling X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset="us-ascii"; Format="flowed" Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org Hi, This has been a problem since the xen-acpi-processor code was added to the kernel source. I wasn't sure if the problem I was seeing was related to the old version (4.1.2) of Xen that I was using but now I'm on 4.2.0 and it still exists I thought I would check if I have a misconfiguration or if I have discovered a problem. My system is a dual AMD Opteron(tm) Processor 2423 HE on Linux kernel 3.4.8. The xen command line is: console=vga,com2 com2=115200,8n1 dom0_mem=max:2048M dom0_max_vcpus=2 dom0_vcpus_pin The CPU scaling information reported by xenpm is below. The problem is that only cpuid 1 can be managed separately, all the others are bundled together and cannot be handled independently which used to be possible with the old xen kernel. If further information would be useful please let me know. Thanks, James # xenpm get-cpufreq-para cpu id : 0 affected_cpus : 0 2 3 4 5 6 7 8 9 10 11 cpuinfo frequency : max [2000000] min [800000] cur [800000] scaling_driver : scaling_avail_gov : userspace performance powersave ondemand current_governor : ondemand ondemand specific : sampling_rate : max [10000000] min [10000] cur [20000] up_threshold : 80 scaling_avail_freq : 2000000 1500000 1300000 1000000 *800000 scaling frequency : max [2000000] min [800000] cur [800000] cpu id : 1 affected_cpus : 1 cpuinfo frequency : max [2000000] min [800000] cur [800000] scaling_driver : scaling_avail_gov : userspace performance powersave ondemand current_governor : ondemand ondemand specific : sampling_rate : max [10000000] min [10000] cur [20000] up_threshold : 80 scaling_avail_freq : 2000000 1500000 1300000 1000000 *800000 scaling frequency : max [2000000] min [800000] cur [800000] cpu id : 2 affected_cpus : 0 2 3 4 5 6 7 8 9 10 11 cpuinfo frequency : max [2000000] min [800000] cur [800000] scaling_driver : scaling_avail_gov : userspace performance powersave ondemand current_governor : ondemand ondemand specific : sampling_rate : max [10000000] min [10000] cur [20000] up_threshold : 80 scaling_avail_freq : 2000000 1500000 1300000 1000000 *800000 scaling frequency : max [2000000] min [800000] cur [800000] cpu id : 3 affected_cpus : 0 2 3 4 5 6 7 8 9 10 11 cpuinfo frequency : max [2000000] min [800000] cur [800000] scaling_driver : scaling_avail_gov : userspace performance powersave ondemand current_governor : ondemand ondemand specific : sampling_rate : max [10000000] min [10000] cur [20000] up_threshold : 80 scaling_avail_freq : 2000000 1500000 1300000 1000000 *800000 scaling frequency : max [2000000] min [800000] cur [800000] cpu id : 4 affected_cpus : 0 2 3 4 5 6 7 8 9 10 11 cpuinfo frequency : max [2000000] min [800000] cur [800000] scaling_driver : scaling_avail_gov : userspace performance powersave ondemand current_governor : ondemand ondemand specific : sampling_rate : max [10000000] min [10000] cur [20000] up_threshold : 80 scaling_avail_freq : 2000000 1500000 1300000 1000000 *800000 scaling frequency : max [2000000] min [800000] cur [800000] cpu id : 5 affected_cpus : 0 2 3 4 5 6 7 8 9 10 11 cpuinfo frequency : max [2000000] min [800000] cur [800000] scaling_driver : scaling_avail_gov : userspace performance powersave ondemand current_governor : ondemand ondemand specific : sampling_rate : max [10000000] min [10000] cur [20000] up_threshold : 80 scaling_avail_freq : 2000000 1500000 1300000 1000000 *800000 scaling frequency : max [2000000] min [800000] cur [800000] cpu id : 6 affected_cpus : 0 2 3 4 5 6 7 8 9 10 11 cpuinfo frequency : max [2000000] min [800000] cur [800000] scaling_driver : scaling_avail_gov : userspace performance powersave ondemand current_governor : ondemand ondemand specific : sampling_rate : max [10000000] min [10000] cur [20000] up_threshold : 80 scaling_avail_freq : 2000000 1500000 1300000 1000000 *800000 scaling frequency : max [2000000] min [800000] cur [800000] cpu id : 7 affected_cpus : 0 2 3 4 5 6 7 8 9 10 11 cpuinfo frequency : max [2000000] min [800000] cur [800000] scaling_driver : scaling_avail_gov : userspace performance powersave ondemand current_governor : ondemand ondemand specific : sampling_rate : max [10000000] min [10000] cur [20000] up_threshold : 80 scaling_avail_freq : 2000000 1500000 1300000 1000000 *800000 scaling frequency : max [2000000] min [800000] cur [800000] cpu id : 8 affected_cpus : 0 2 3 4 5 6 7 8 9 10 11 cpuinfo frequency : max [2000000] min [800000] cur [800000] scaling_driver : scaling_avail_gov : userspace performance powersave ondemand current_governor : ondemand ondemand specific : sampling_rate : max [10000000] min [10000] cur [20000] up_threshold : 80 scaling_avail_freq : 2000000 1500000 1300000 1000000 *800000 scaling frequency : max [2000000] min [800000] cur [800000] cpu id : 9 affected_cpus : 0 2 3 4 5 6 7 8 9 10 11 cpuinfo frequency : max [2000000] min [800000] cur [800000] scaling_driver : scaling_avail_gov : userspace performance powersave ondemand current_governor : ondemand ondemand specific : sampling_rate : max [10000000] min [10000] cur [20000] up_threshold : 80 scaling_avail_freq : 2000000 1500000 1300000 1000000 *800000 scaling frequency : max [2000000] min [800000] cur [800000] cpu id : 10 affected_cpus : 0 2 3 4 5 6 7 8 9 10 11 cpuinfo frequency : max [2000000] min [800000] cur [800000] scaling_driver : scaling_avail_gov : userspace performance powersave ondemand current_governor : ondemand ondemand specific : sampling_rate : max [10000000] min [10000] cur [20000] up_threshold : 80 scaling_avail_freq : 2000000 1500000 1300000 1000000 *800000 scaling frequency : max [2000000] min [800000] cur [800000] cpu id : 11 affected_cpus : 0 2 3 4 5 6 7 8 9 10 11 cpuinfo frequency : max [2000000] min [800000] cur [800000] scaling_driver : scaling_avail_gov : userspace performance powersave ondemand current_governor : ondemand ondemand specific : sampling_rate : max [10000000] min [10000] cur [20000] up_threshold : 80 scaling_avail_freq : 2000000 1500000 1300000 1000000 *800000 scaling frequency : max [2000000] min [800000] cur [800000] _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Fri Sep 21 17:49:48 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Fri, 21 Sep 2012 17:49:48 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TF7Li-0007C2-5P; Fri, 21 Sep 2012 17:49:10 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TF7Lg-0007Br-Ha for xen-users@lists.xen.org; Fri, 21 Sep 2012 17:49:08 +0000 Received: from [85.158.139.83:40273] by server-15.bemta-5.messagelabs.com id E3/74-23541-398AC505; Fri, 21 Sep 2012 17:49:07 +0000 X-Env-Sender: cdelorme@gmail.com X-Msg-Ref: server-14.tower-182.messagelabs.com!1348249745!27311415!1 X-Originating-IP: [209.85.214.173] X-SpamReason: No, hits=1.2 required=7.0 tests=HTML_20_30,HTML_MESSAGE, ML_RADAR_SPEW_LINKS_14,RCVD_BY_IP,spamassassin: X-StarScan-Received: X-StarScan-Version: 6.6.1.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 814 invoked from network); 21 Sep 2012 17:49:07 -0000 Received: from mail-ob0-f173.google.com (HELO mail-ob0-f173.google.com) (209.85.214.173) by server-14.tower-182.messagelabs.com with RC4-SHA encrypted SMTP; 21 Sep 2012 17:49:07 -0000 Received: by obbta14 with SMTP id ta14so4552598obb.32 for ; Fri, 21 Sep 2012 10:49:05 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:date:message-id:subject:from:to:content-type; bh=y0URc/zrkMBQB84gbuwyQ1P6Mbdt/1WCdlIIQkNyXdM=; b=camfXRDBepzkvsiGUCS5rqR/iuXSeFBbMwOItLxTM3CB/yRu4W2KVFjpQRnLpVnH/f on28lH3Y0mZCoD0WMmbCGI7yNqa9xKVQ+OL393Pyv4tapAPlV4TDcWjacoCQHY6Za4Na 8nCe21zUB1YB/RWMz/St5RDAmYNnp0b3QPFR3JC0kJElb2rl5MQIgZrzUL+rrQjfMNGL 3CxyqGybALnTjQ0MO8ouvP0mH4brejTc3DLs4EKuPV0ie7m7altt88YMffEinOqkTpr2 Ob6aSpOx5rw/kwtkCPRWr9Y1w5AxkCLnkohz7NOEIGGiZyj5YMGto0FuzTzHMMrB35hd szpQ== MIME-Version: 1.0 Received: by 10.182.146.46 with SMTP id sz14mr4377634obb.76.1348249745461; Fri, 21 Sep 2012 10:49:05 -0700 (PDT) Received: by 10.76.19.148 with HTTP; Fri, 21 Sep 2012 10:49:05 -0700 (PDT) Date: Fri, 21 Sep 2012 13:49:05 -0400 Message-ID: From: Casey DeLorme To: xen-users@lists.xen.org Subject: [Xen-users] xl create bug on first-attempt with passthrough X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============7423365782102528225==" Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org --===============7423365782102528225== Content-Type: multipart/alternative; boundary=f46d0444e92b25901204ca39db1d --f46d0444e92b25901204ca39db1d Content-Type: text/plain; charset=ISO-8859-1 Hello, I recently swapped some components, and rebuilt my system. Changes to the configuration: - Wheezy Beta 1 > Wheezy Beta 2 - Kernel 3.4.9 > Kernel 3.4.11 I have tested the new Xen 4.2 stable, and Xen unstable revision 25777, both are giving me the same error so I do not believe it is related to a change in Xen. The first attempt to pass a PCI device after booting the system gives me these messages (on "xl create"): libxl: error: libxl_dom.c:557:libxl__build_hvm: hvm building failed libxl: error: libxl_create.c:901:domcreate_rebuild_done: cannot (re-)build domain: -3 libxl: error: libxl_dm.c:1239:libxl__destroy_device_model: could not find device-model's pid for dom 1 libxl: error: libxl.c:1427:libxl__destroy_domid: libxl__destroy_device_model failed for 1 The baffling part is that all subsequent attempts are successful. So if I rerun "xl create" it works, and I can do it as many times as I want. If I reboot then I get the error again. Any ideas what the cause could be? Thanks, ~Casey DeLorme --f46d0444e92b25901204ca39db1d Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable
Hello,

I recently swapped some components, an= d rebuilt my system.

Changes to the configuration:=

- Wheezy Beta 1 =A0> =A0Wheezy Beta 2
- Kernel 3.4.9 =A0 > =A0Kernel 3.4.11

I have te= sted the new Xen 4.2 stable, and Xen unstable revision 25777, both are givi= ng me the same error so I do not believe it is related to a change in Xen.<= /div>

The first attempt to pass a PCI device after booting th= e system gives me these messages (on "xl create"):

=
libxl: error: libxl_dom.c:557:libxl__build_hvm: hvm building fai= led
libxl: error: libxl_create.c:901:domcreate_rebuild_done: cannot (re-)b= uild domain: -3
libxl: error: libxl_dm.c:1239:libxl__destroy_devi= ce_model: could not find device-model's pid for dom 1
libxl: = error: libxl.c:1427:libxl__destroy_domid: libxl__destroy_device_model faile= d for 1


The baffling part is that all subsequent= attempts are successful. =A0So if I rerun "xl create" it works, = and I can do it as many times as I want. =A0If I reboot then I get the erro= r again.

Any ideas what the cause could be?

=
Thanks,

~Casey DeLorme
--f46d0444e92b25901204ca39db1d-- --===============7423365782102528225== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users --===============7423365782102528225==-- From xen-users-bounces@lists.xen.org Fri Sep 21 17:49:48 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Fri, 21 Sep 2012 17:49:48 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TF7Li-0007C2-5P; Fri, 21 Sep 2012 17:49:10 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TF7Lg-0007Br-Ha for xen-users@lists.xen.org; Fri, 21 Sep 2012 17:49:08 +0000 Received: from [85.158.139.83:40273] by server-15.bemta-5.messagelabs.com id E3/74-23541-398AC505; Fri, 21 Sep 2012 17:49:07 +0000 X-Env-Sender: cdelorme@gmail.com X-Msg-Ref: server-14.tower-182.messagelabs.com!1348249745!27311415!1 X-Originating-IP: [209.85.214.173] X-SpamReason: No, hits=1.2 required=7.0 tests=HTML_20_30,HTML_MESSAGE, ML_RADAR_SPEW_LINKS_14,RCVD_BY_IP,spamassassin: X-StarScan-Received: X-StarScan-Version: 6.6.1.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 814 invoked from network); 21 Sep 2012 17:49:07 -0000 Received: from mail-ob0-f173.google.com (HELO mail-ob0-f173.google.com) (209.85.214.173) by server-14.tower-182.messagelabs.com with RC4-SHA encrypted SMTP; 21 Sep 2012 17:49:07 -0000 Received: by obbta14 with SMTP id ta14so4552598obb.32 for ; Fri, 21 Sep 2012 10:49:05 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:date:message-id:subject:from:to:content-type; bh=y0URc/zrkMBQB84gbuwyQ1P6Mbdt/1WCdlIIQkNyXdM=; b=camfXRDBepzkvsiGUCS5rqR/iuXSeFBbMwOItLxTM3CB/yRu4W2KVFjpQRnLpVnH/f on28lH3Y0mZCoD0WMmbCGI7yNqa9xKVQ+OL393Pyv4tapAPlV4TDcWjacoCQHY6Za4Na 8nCe21zUB1YB/RWMz/St5RDAmYNnp0b3QPFR3JC0kJElb2rl5MQIgZrzUL+rrQjfMNGL 3CxyqGybALnTjQ0MO8ouvP0mH4brejTc3DLs4EKuPV0ie7m7altt88YMffEinOqkTpr2 Ob6aSpOx5rw/kwtkCPRWr9Y1w5AxkCLnkohz7NOEIGGiZyj5YMGto0FuzTzHMMrB35hd szpQ== MIME-Version: 1.0 Received: by 10.182.146.46 with SMTP id sz14mr4377634obb.76.1348249745461; Fri, 21 Sep 2012 10:49:05 -0700 (PDT) Received: by 10.76.19.148 with HTTP; Fri, 21 Sep 2012 10:49:05 -0700 (PDT) Date: Fri, 21 Sep 2012 13:49:05 -0400 Message-ID: From: Casey DeLorme To: xen-users@lists.xen.org Subject: [Xen-users] xl create bug on first-attempt with passthrough X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============7423365782102528225==" Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org --===============7423365782102528225== Content-Type: multipart/alternative; boundary=f46d0444e92b25901204ca39db1d --f46d0444e92b25901204ca39db1d Content-Type: text/plain; charset=ISO-8859-1 Hello, I recently swapped some components, and rebuilt my system. Changes to the configuration: - Wheezy Beta 1 > Wheezy Beta 2 - Kernel 3.4.9 > Kernel 3.4.11 I have tested the new Xen 4.2 stable, and Xen unstable revision 25777, both are giving me the same error so I do not believe it is related to a change in Xen. The first attempt to pass a PCI device after booting the system gives me these messages (on "xl create"): libxl: error: libxl_dom.c:557:libxl__build_hvm: hvm building failed libxl: error: libxl_create.c:901:domcreate_rebuild_done: cannot (re-)build domain: -3 libxl: error: libxl_dm.c:1239:libxl__destroy_device_model: could not find device-model's pid for dom 1 libxl: error: libxl.c:1427:libxl__destroy_domid: libxl__destroy_device_model failed for 1 The baffling part is that all subsequent attempts are successful. So if I rerun "xl create" it works, and I can do it as many times as I want. If I reboot then I get the error again. Any ideas what the cause could be? Thanks, ~Casey DeLorme --f46d0444e92b25901204ca39db1d Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable
Hello,

I recently swapped some components, an= d rebuilt my system.

Changes to the configuration:=

- Wheezy Beta 1 =A0> =A0Wheezy Beta 2
- Kernel 3.4.9 =A0 > =A0Kernel 3.4.11

I have te= sted the new Xen 4.2 stable, and Xen unstable revision 25777, both are givi= ng me the same error so I do not believe it is related to a change in Xen.<= /div>

The first attempt to pass a PCI device after booting th= e system gives me these messages (on "xl create"):

=
libxl: error: libxl_dom.c:557:libxl__build_hvm: hvm building fai= led
libxl: error: libxl_create.c:901:domcreate_rebuild_done: cannot (re-)b= uild domain: -3
libxl: error: libxl_dm.c:1239:libxl__destroy_devi= ce_model: could not find device-model's pid for dom 1
libxl: = error: libxl.c:1427:libxl__destroy_domid: libxl__destroy_device_model faile= d for 1


The baffling part is that all subsequent= attempts are successful. =A0So if I rerun "xl create" it works, = and I can do it as many times as I want. =A0If I reboot then I get the erro= r again.

Any ideas what the cause could be?

=
Thanks,

~Casey DeLorme
--f46d0444e92b25901204ca39db1d-- --===============7423365782102528225== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users --===============7423365782102528225==-- From xen-users-bounces@lists.xen.org Fri Sep 21 18:07:48 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Fri, 21 Sep 2012 18:07:48 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TF7cw-0007tE-D5; Fri, 21 Sep 2012 18:06:58 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TF7cu-0007t9-Pp for xen-users@lists.xen.org; Fri, 21 Sep 2012 18:06:56 +0000 Received: from [85.158.143.99:40960] by server-2.bemta-4.messagelabs.com id 79/3E-06610-0CCAC505; Fri, 21 Sep 2012 18:06:56 +0000 X-Env-Sender: jbergmans@bergmans.com X-Msg-Ref: server-10.tower-216.messagelabs.com!1348250814!24882031!1 X-Originating-IP: [206.166.251.101] X-SpamReason: No, hits=0.3 required=7.0 tests=HTML_60_70,HTML_MESSAGE X-StarScan-Received: X-StarScan-Version: 6.6.1.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 20213 invoked from network); 21 Sep 2012 18:06:54 -0000 Received: from 101.moth3.hiwaay.net (HELO moth3.hiwaay.net) (206.166.251.101) by server-10.tower-216.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 21 Sep 2012 18:06:54 -0000 X-No-Relay: not in my network Received: from [192.168.1.100] (adsl-71-129-59-86.dsl.irvnca.pacbell.net [71.129.59.86]) by moth3.hiwaay.net (Postfix) with ESMTPA id CBA2C5080170 for ; Fri, 21 Sep 2012 13:06:52 -0500 (CDT) From: John Bergmans Date: Fri, 21 Sep 2012 11:06:51 -0700 Message-Id: <6D09C18D-3866-4DE4-B576-D1492B760EC2@bergmans.com> To: xen-users@lists.xen.org Mime-Version: 1.0 (Apple Message framework v1084) X-Mailer: Apple Mail (2.1084) Subject: [Xen-users] Testing High-Frequency Virtual Server Monitoring X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============7818871878570687130==" Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org --===============7818871878570687130== Content-Type: multipart/alternative; boundary=Apple-Mail-2-576424607 --Apple-Mail-2-576424607 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=us-ascii Hi xen-users. I've developed "collectdViewer", a system for high-frequency (2x per = second), browser-based server monitoring that uses collectd for = statistics collection: http://collectdviewer.com. It turns out that there's a "libvirt" plugin for collectd which should, = in theory, enable collectdViewer to monitor the performance of servers = virtualized by Xen, without the need to install a daemon in the virtual = server itself (http://collectd.org/wiki/index.php/Plugin:libvirt) Since I'm not familiar with Xen, I'm wondering if anyone on this list = would be interested in working with me to demonstrate this capability. = Here's a schematic of what how I think the demo system would be put = together: = http://collectdviewer.com/applications.html#high_frequency_monitoring_for_= virtual_servers Please contact me if you'd like to collaborate or have any questions. Regards, John Bergmans Principal Engineer / Owner Bergmans Mechatronics LLC 714-474-8956 @jbergmans www.bergmans.com skype: johnbergmans --Apple-Mail-2-576424607 Content-Transfer-Encoding: quoted-printable Content-Type: text/html; charset=us-ascii http://collectdviewer.com.

=
It turns out that there's a "libvirt" plugin for collectd = which should, in theory, enable collectdViewer to monitor the = performance of servers virtualized by Xen, without the need to install a = daemon in the virtual server itself (http://collectd= .org/wiki/index.php/Plugin:libvirt)

Since I'm not = familiar with Xen, I'm wondering if anyone on this list would be = interested in working with me to demonstrate this capability. =  Here's a schematic of what how I think the demo system would be = put together: http://collectdviewer.com/applications.html#high_= frequency_monitoring_for_virtual_servers

Plea= se contact me if you'd like to collaborate or have any = questions.

Regards,

John Bergmans
Principal Engineer / = Owner
714-474-8956
@jbergmans



= --Apple-Mail-2-576424607-- --===============7818871878570687130== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users --===============7818871878570687130==-- From xen-users-bounces@lists.xen.org Fri Sep 21 18:07:48 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Fri, 21 Sep 2012 18:07:48 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TF7cw-0007tE-D5; Fri, 21 Sep 2012 18:06:58 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TF7cu-0007t9-Pp for xen-users@lists.xen.org; Fri, 21 Sep 2012 18:06:56 +0000 Received: from [85.158.143.99:40960] by server-2.bemta-4.messagelabs.com id 79/3E-06610-0CCAC505; Fri, 21 Sep 2012 18:06:56 +0000 X-Env-Sender: jbergmans@bergmans.com X-Msg-Ref: server-10.tower-216.messagelabs.com!1348250814!24882031!1 X-Originating-IP: [206.166.251.101] X-SpamReason: No, hits=0.3 required=7.0 tests=HTML_60_70,HTML_MESSAGE X-StarScan-Received: X-StarScan-Version: 6.6.1.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 20213 invoked from network); 21 Sep 2012 18:06:54 -0000 Received: from 101.moth3.hiwaay.net (HELO moth3.hiwaay.net) (206.166.251.101) by server-10.tower-216.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 21 Sep 2012 18:06:54 -0000 X-No-Relay: not in my network Received: from [192.168.1.100] (adsl-71-129-59-86.dsl.irvnca.pacbell.net [71.129.59.86]) by moth3.hiwaay.net (Postfix) with ESMTPA id CBA2C5080170 for ; Fri, 21 Sep 2012 13:06:52 -0500 (CDT) From: John Bergmans Date: Fri, 21 Sep 2012 11:06:51 -0700 Message-Id: <6D09C18D-3866-4DE4-B576-D1492B760EC2@bergmans.com> To: xen-users@lists.xen.org Mime-Version: 1.0 (Apple Message framework v1084) X-Mailer: Apple Mail (2.1084) Subject: [Xen-users] Testing High-Frequency Virtual Server Monitoring X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============7818871878570687130==" Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org --===============7818871878570687130== Content-Type: multipart/alternative; boundary=Apple-Mail-2-576424607 --Apple-Mail-2-576424607 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=us-ascii Hi xen-users. I've developed "collectdViewer", a system for high-frequency (2x per = second), browser-based server monitoring that uses collectd for = statistics collection: http://collectdviewer.com. It turns out that there's a "libvirt" plugin for collectd which should, = in theory, enable collectdViewer to monitor the performance of servers = virtualized by Xen, without the need to install a daemon in the virtual = server itself (http://collectd.org/wiki/index.php/Plugin:libvirt) Since I'm not familiar with Xen, I'm wondering if anyone on this list = would be interested in working with me to demonstrate this capability. = Here's a schematic of what how I think the demo system would be put = together: = http://collectdviewer.com/applications.html#high_frequency_monitoring_for_= virtual_servers Please contact me if you'd like to collaborate or have any questions. Regards, John Bergmans Principal Engineer / Owner Bergmans Mechatronics LLC 714-474-8956 @jbergmans www.bergmans.com skype: johnbergmans --Apple-Mail-2-576424607 Content-Transfer-Encoding: quoted-printable Content-Type: text/html; charset=us-ascii http://collectdviewer.com.

=
It turns out that there's a "libvirt" plugin for collectd = which should, in theory, enable collectdViewer to monitor the = performance of servers virtualized by Xen, without the need to install a = daemon in the virtual server itself (http://collectd= .org/wiki/index.php/Plugin:libvirt)

Since I'm not = familiar with Xen, I'm wondering if anyone on this list would be = interested in working with me to demonstrate this capability. =  Here's a schematic of what how I think the demo system would be = put together: http://collectdviewer.com/applications.html#high_= frequency_monitoring_for_virtual_servers

Plea= se contact me if you'd like to collaborate or have any = questions.

Regards,

John Bergmans
Principal Engineer / = Owner
714-474-8956
@jbergmans



= --Apple-Mail-2-576424607-- --===============7818871878570687130== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users --===============7818871878570687130==-- From xen-users-bounces@lists.xen.org Fri Sep 21 18:29:41 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Fri, 21 Sep 2012 18:29:41 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TF7xx-0008NU-Uj; Fri, 21 Sep 2012 18:28:41 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TF7xw-0008NP-Ts for xen-users@lists.xensource.com; Fri, 21 Sep 2012 18:28:41 +0000 Received: from [85.158.137.99:4471] by server-10.bemta-3.messagelabs.com id 24/81-10411-8D1BC505; Fri, 21 Sep 2012 18:28:40 +0000 X-Env-Sender: ricardo.meb.jesus@gmail.com X-Msg-Ref: server-16.tower-217.messagelabs.com!1348252116!18649161!1 X-Originating-IP: [209.85.160.43] X-SpamReason: No, hits=0.3 required=7.0 tests=ML_RADAR_SPEW_LINKS_14, RCVD_BY_IP,spamassassin: X-StarScan-Received: X-StarScan-Version: 6.6.1.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 24433 invoked from network); 21 Sep 2012 18:28:38 -0000 Received: from mail-pb0-f43.google.com (HELO mail-pb0-f43.google.com) (209.85.160.43) by server-16.tower-217.messagelabs.com with RC4-SHA encrypted SMTP; 21 Sep 2012 18:28:38 -0000 Received: by pbbrq2 with SMTP id rq2so10472620pbb.30 for ; Fri, 21 Sep 2012 11:28:36 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=57HxoF1f7TT23IfdjV5pumyDOwoNtu99iUqOMpraE1c=; b=ZHldRYITeRSfbbipstrgYAIGTb/b1p8YyGAcTyIB0ZLqUVJEBlWBd0ROruAf+KqQ/O gC/kraLk3LwQpUflHZJJqt1jCOXNrkQA7yWd1qVPRLSSWc1KCSp5iOtwPQao2V3swHC5 PwQk0JprVX+/DWezmA9sgp7Xas5N0qk5Mz0C3R89m+qblBiGPsb/sbgHRdDiHgyEtrlr JwvlRLI4ZjX0OYsv7Vq/EkAl8F9aOYek6zGlketGQqOXp+69w4w8BCbMGgZxOZM5UIZ7 KkuUPZep6suMOm4PCoLvClUjIw5R8Z8JZlU+MlRN4zFPGxUSxME90nRuWtrYQSc9yLO2 gn/Q== MIME-Version: 1.0 Received: by 10.68.221.72 with SMTP id qc8mr17788305pbc.63.1348252115785; Fri, 21 Sep 2012 11:28:35 -0700 (PDT) Received: by 10.66.85.99 with HTTP; Fri, 21 Sep 2012 11:28:35 -0700 (PDT) In-Reply-To: References: <1342190462.7075.128.camel@wotan2> <6035A0D088A63A46850C3988ED045A4B2998FF73@BITCOM1.int.sbss.com.au> Date: Fri, 21 Sep 2012 19:28:35 +0100 Message-ID: From: Ricardo Jesus To: Jim Molnar Cc: xen-users@lists.xensource.com Subject: Re: [Xen-users] win2008 crashes unde xen X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org Does your Windows HVM config contain viridian=1? On Fri, Sep 21, 2012 at 4:51 PM, Jim Molnar wrote: > > > James Harper bendigoit.com.au> writes: > >> >> > >> > I have 358 drivers and error looks like this one >> > http://jbeekman.nl/bsod20120117_1953.png >> > >> >> If that is your BSoD then the crash does appear to be in xenvbd.sys which is a > GPLPV driver. Can you have a look >> in c:\windows\minidump and see if there is a file in there that approximately > matches the time of your bluescreen? >> >> If so, can you zip it up and email it to me? I also need to know the exact > version of GPLPV you are using so I can >> load the correct symbols in the debugger. >> >> Thanks >> >> James >> > > Hey James, We're using your Driver as well 11.0.308 and we're having the issue > of a BSOD during Exchange 2010 replication. Was this issue ever fixed? Do you > still need a dump from the Debug version of the driver? If anyone knows the fix > to this please email me - jim.molnar "at" Gmail dot com Thanks a lot. > > Jim. > > > > _______________________________________________ > Xen-users mailing list > Xen-users@lists.xen.org > http://lists.xen.org/xen-users _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Fri Sep 21 18:29:41 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Fri, 21 Sep 2012 18:29:41 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TF7xx-0008NU-Uj; Fri, 21 Sep 2012 18:28:41 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TF7xw-0008NP-Ts for xen-users@lists.xensource.com; Fri, 21 Sep 2012 18:28:41 +0000 Received: from [85.158.137.99:4471] by server-10.bemta-3.messagelabs.com id 24/81-10411-8D1BC505; Fri, 21 Sep 2012 18:28:40 +0000 X-Env-Sender: ricardo.meb.jesus@gmail.com X-Msg-Ref: server-16.tower-217.messagelabs.com!1348252116!18649161!1 X-Originating-IP: [209.85.160.43] X-SpamReason: No, hits=0.3 required=7.0 tests=ML_RADAR_SPEW_LINKS_14, RCVD_BY_IP,spamassassin: X-StarScan-Received: X-StarScan-Version: 6.6.1.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 24433 invoked from network); 21 Sep 2012 18:28:38 -0000 Received: from mail-pb0-f43.google.com (HELO mail-pb0-f43.google.com) (209.85.160.43) by server-16.tower-217.messagelabs.com with RC4-SHA encrypted SMTP; 21 Sep 2012 18:28:38 -0000 Received: by pbbrq2 with SMTP id rq2so10472620pbb.30 for ; Fri, 21 Sep 2012 11:28:36 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=57HxoF1f7TT23IfdjV5pumyDOwoNtu99iUqOMpraE1c=; b=ZHldRYITeRSfbbipstrgYAIGTb/b1p8YyGAcTyIB0ZLqUVJEBlWBd0ROruAf+KqQ/O gC/kraLk3LwQpUflHZJJqt1jCOXNrkQA7yWd1qVPRLSSWc1KCSp5iOtwPQao2V3swHC5 PwQk0JprVX+/DWezmA9sgp7Xas5N0qk5Mz0C3R89m+qblBiGPsb/sbgHRdDiHgyEtrlr JwvlRLI4ZjX0OYsv7Vq/EkAl8F9aOYek6zGlketGQqOXp+69w4w8BCbMGgZxOZM5UIZ7 KkuUPZep6suMOm4PCoLvClUjIw5R8Z8JZlU+MlRN4zFPGxUSxME90nRuWtrYQSc9yLO2 gn/Q== MIME-Version: 1.0 Received: by 10.68.221.72 with SMTP id qc8mr17788305pbc.63.1348252115785; Fri, 21 Sep 2012 11:28:35 -0700 (PDT) Received: by 10.66.85.99 with HTTP; Fri, 21 Sep 2012 11:28:35 -0700 (PDT) In-Reply-To: References: <1342190462.7075.128.camel@wotan2> <6035A0D088A63A46850C3988ED045A4B2998FF73@BITCOM1.int.sbss.com.au> Date: Fri, 21 Sep 2012 19:28:35 +0100 Message-ID: From: Ricardo Jesus To: Jim Molnar Cc: xen-users@lists.xensource.com Subject: Re: [Xen-users] win2008 crashes unde xen X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org Does your Windows HVM config contain viridian=1? On Fri, Sep 21, 2012 at 4:51 PM, Jim Molnar wrote: > > > James Harper bendigoit.com.au> writes: > >> >> > >> > I have 358 drivers and error looks like this one >> > http://jbeekman.nl/bsod20120117_1953.png >> > >> >> If that is your BSoD then the crash does appear to be in xenvbd.sys which is a > GPLPV driver. Can you have a look >> in c:\windows\minidump and see if there is a file in there that approximately > matches the time of your bluescreen? >> >> If so, can you zip it up and email it to me? I also need to know the exact > version of GPLPV you are using so I can >> load the correct symbols in the debugger. >> >> Thanks >> >> James >> > > Hey James, We're using your Driver as well 11.0.308 and we're having the issue > of a BSOD during Exchange 2010 replication. Was this issue ever fixed? Do you > still need a dump from the Debug version of the driver? If anyone knows the fix > to this please email me - jim.molnar "at" Gmail dot com Thanks a lot. > > Jim. > > > > _______________________________________________ > Xen-users mailing list > Xen-users@lists.xen.org > http://lists.xen.org/xen-users _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Fri Sep 21 18:36:12 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Fri, 21 Sep 2012 18:36:12 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TF84T-0000F8-0k; Fri, 21 Sep 2012 18:35:25 +0000 Received: from mail27.messagelabs.com ([193.109.254.147]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TF84R-0000F3-De for xen-users@lists.xen.org; Fri, 21 Sep 2012 18:35:23 +0000 X-Env-Sender: skippyvondrake@gmail.com X-Msg-Ref: server-10.tower-27.messagelabs.com!1348252516!6744953!1 X-Originating-IP: [209.85.212.173] X-SpamReason: No, hits=0.3 required=7.0 tests=ML_RADAR_SPEW_LINKS_14, RCVD_BY_IP,spamassassin: X-StarScan-Received: X-StarScan-Version: 6.6.1.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 7703 invoked from network); 21 Sep 2012 18:35:17 -0000 Received: from mail-wi0-f173.google.com (HELO mail-wi0-f173.google.com) (209.85.212.173) by server-10.tower-27.messagelabs.com with RC4-SHA encrypted SMTP; 21 Sep 2012 18:35:17 -0000 Received: by wibhm6 with SMTP id hm6so1976577wib.14 for ; Fri, 21 Sep 2012 11:35:16 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:date:message-id:subject:from:to:content-type; bh=upZKyST4A6rMSE7TXM+NKJyS+De21hbCgUqT9G6gTbc=; b=Rcj5NsNymf/B66QyjGeI6hsi/u7bpDUGLCtsH0LDiGSBVC4+SdzWYuJQB/CokF1aTA 7TMYl7NErE6A08n7G4vjnzVfc3DrQeEouE4t2qLyQaihwIPmEiql/48VI5jScm9Nffso dKKgiECcKX3OqjXhERfalmLeCCY+JqNMVGl+ADn7pDyIy9KI0X/bPXJfqTSC1wGQJfPf el8Nn0UXwz1EqIPld2bKJG1CO9Q2YHI16kS9ZMCQmEwkLOrchH+sX4yfOMIxJIUC5bU2 1Pv/KlEeWPotyPhnk1d/l9ns9cPfcbbxaEZJ6TQM+p+J+wqPnTIdA7xWH7QM080Pm845 G0Fg== MIME-Version: 1.0 Received: by 10.180.82.164 with SMTP id j4mr6033338wiy.18.1348252516723; Fri, 21 Sep 2012 11:35:16 -0700 (PDT) Received: by 10.194.21.197 with HTTP; Fri, 21 Sep 2012 11:35:16 -0700 (PDT) Date: Fri, 21 Sep 2012 14:35:16 -0400 Message-ID: From: Skippy VonDrake To: xen-users@lists.xen.org Subject: [Xen-users] xl cfg disk option for lvm and cdrom X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org I configured an LogicalVolume of 15G to install an XP hvm on. But I don't know how to define the 'disk' configuration for the config script for "xl create". I also don't know the format for the cdrom disk entry. As a general guide I'm using the example in xen sources (./tools/examples/xlexample.hvm) # pvs PV VG Fmt Attr PSize PFree /dev/sda11 guestsVG lvm2 a- 119.29g 104.29g # vgs VG #PV #LV #SN Attr VSize VFree guestsVG 1 1 0 wz--n- 119.29g 104.29g lvs LV VG Attr LSize Origin Snap% Move Log Copy% Convert xpVol guestsVG -wi-a- 15.00g disk = [ 'guestsVG/xpVol,raw,xvda,rw','/dev/sr0,raw,hdc,devtype=cdrom' ] The above line is obviously wrong. What is the correct format? My cdrom is /dev/sr0. I compiled a "mainline" kernel (3.5.4) using the guide at http://wiki.xen.org/wiki/Mainline_Linux_Kernel_Configs on Ubuntu 12.04. _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Fri Sep 21 18:36:12 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Fri, 21 Sep 2012 18:36:12 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TF84T-0000F8-0k; Fri, 21 Sep 2012 18:35:25 +0000 Received: from mail27.messagelabs.com ([193.109.254.147]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TF84R-0000F3-De for xen-users@lists.xen.org; Fri, 21 Sep 2012 18:35:23 +0000 X-Env-Sender: skippyvondrake@gmail.com X-Msg-Ref: server-10.tower-27.messagelabs.com!1348252516!6744953!1 X-Originating-IP: [209.85.212.173] X-SpamReason: No, hits=0.3 required=7.0 tests=ML_RADAR_SPEW_LINKS_14, RCVD_BY_IP,spamassassin: X-StarScan-Received: X-StarScan-Version: 6.6.1.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 7703 invoked from network); 21 Sep 2012 18:35:17 -0000 Received: from mail-wi0-f173.google.com (HELO mail-wi0-f173.google.com) (209.85.212.173) by server-10.tower-27.messagelabs.com with RC4-SHA encrypted SMTP; 21 Sep 2012 18:35:17 -0000 Received: by wibhm6 with SMTP id hm6so1976577wib.14 for ; Fri, 21 Sep 2012 11:35:16 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:date:message-id:subject:from:to:content-type; bh=upZKyST4A6rMSE7TXM+NKJyS+De21hbCgUqT9G6gTbc=; b=Rcj5NsNymf/B66QyjGeI6hsi/u7bpDUGLCtsH0LDiGSBVC4+SdzWYuJQB/CokF1aTA 7TMYl7NErE6A08n7G4vjnzVfc3DrQeEouE4t2qLyQaihwIPmEiql/48VI5jScm9Nffso dKKgiECcKX3OqjXhERfalmLeCCY+JqNMVGl+ADn7pDyIy9KI0X/bPXJfqTSC1wGQJfPf el8Nn0UXwz1EqIPld2bKJG1CO9Q2YHI16kS9ZMCQmEwkLOrchH+sX4yfOMIxJIUC5bU2 1Pv/KlEeWPotyPhnk1d/l9ns9cPfcbbxaEZJ6TQM+p+J+wqPnTIdA7xWH7QM080Pm845 G0Fg== MIME-Version: 1.0 Received: by 10.180.82.164 with SMTP id j4mr6033338wiy.18.1348252516723; Fri, 21 Sep 2012 11:35:16 -0700 (PDT) Received: by 10.194.21.197 with HTTP; Fri, 21 Sep 2012 11:35:16 -0700 (PDT) Date: Fri, 21 Sep 2012 14:35:16 -0400 Message-ID: From: Skippy VonDrake To: xen-users@lists.xen.org Subject: [Xen-users] xl cfg disk option for lvm and cdrom X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org I configured an LogicalVolume of 15G to install an XP hvm on. But I don't know how to define the 'disk' configuration for the config script for "xl create". I also don't know the format for the cdrom disk entry. As a general guide I'm using the example in xen sources (./tools/examples/xlexample.hvm) # pvs PV VG Fmt Attr PSize PFree /dev/sda11 guestsVG lvm2 a- 119.29g 104.29g # vgs VG #PV #LV #SN Attr VSize VFree guestsVG 1 1 0 wz--n- 119.29g 104.29g lvs LV VG Attr LSize Origin Snap% Move Log Copy% Convert xpVol guestsVG -wi-a- 15.00g disk = [ 'guestsVG/xpVol,raw,xvda,rw','/dev/sr0,raw,hdc,devtype=cdrom' ] The above line is obviously wrong. What is the correct format? My cdrom is /dev/sr0. I compiled a "mainline" kernel (3.5.4) using the guide at http://wiki.xen.org/wiki/Mainline_Linux_Kernel_Configs on Ubuntu 12.04. _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Fri Sep 21 18:41:06 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Fri, 21 Sep 2012 18:41:06 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TF89I-0000Vp-Vt; Fri, 21 Sep 2012 18:40:24 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TF89H-0000Vg-Cn for xen-users@lists.xen.org; Fri, 21 Sep 2012 18:40:23 +0000 Received: from [85.158.137.99:36955] by server-13.bemta-3.messagelabs.com id F7/FF-01606-694BC505; Fri, 21 Sep 2012 18:40:22 +0000 X-Env-Sender: peter.phaal@gmail.com X-Msg-Ref: server-15.tower-217.messagelabs.com!1348252819!16285644!1 X-Originating-IP: [209.85.216.52] X-SpamReason: No, hits=0.3 required=7.0 tests=ML_RADAR_SPEW_LINKS_14, ML_RADAR_SPEW_LINKS_23,RCVD_BY_IP,spamassassin: X-StarScan-Received: X-StarScan-Version: 6.6.1.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 31497 invoked from network); 21 Sep 2012 18:40:20 -0000 Received: from mail-qa0-f52.google.com (HELO mail-qa0-f52.google.com) (209.85.216.52) by server-15.tower-217.messagelabs.com with RC4-SHA encrypted SMTP; 21 Sep 2012 18:40:20 -0000 Received: by qabg24 with SMTP id g24so946380qab.11 for ; Fri, 21 Sep 2012 11:40:19 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=i9dQ7ueX36Phn3D2lUkuhEM1OAchhKnQc1o/iYo69T8=; b=ku/wOQ6bKsNDyGAulxBjqoQpbZB+K41Rc73N+3m8U2Dbf8qOjsc0nzj/58TSOOag9J 7SuADSYgWjeewczbo3QjcUHPNcNEgzEoMby8FKOH++AxNZvMw7S2tsXAKf7030Ay6egc KKQ9exaODB7M7npBYQsf7ehhEGXZeHt1Ey+4xr36KicNiIk3KdGey0wd05J5DjycDfE6 lgD2efHDSPThQZgP5Txtmb493m0ERp0qohO3pyeUpeW8qhPgSYiI6+A0+pBGSNlaWjdt dNIvHLiYpYEJkBs6UdHn6NrAcFm2dhXb6Zko7MUO/Rh3yShZzbGFl0vPC7BzRIa1Zz8u 5fjQ== MIME-Version: 1.0 Received: by 10.224.196.132 with SMTP id eg4mr14154845qab.93.1348252818994; Fri, 21 Sep 2012 11:40:18 -0700 (PDT) Received: by 10.49.15.133 with HTTP; Fri, 21 Sep 2012 11:40:18 -0700 (PDT) In-Reply-To: <6D09C18D-3866-4DE4-B576-D1492B760EC2@bergmans.com> References: <6D09C18D-3866-4DE4-B576-D1492B760EC2@bergmans.com> Date: Fri, 21 Sep 2012 11:40:18 -0700 Message-ID: From: Peter Phaal To: John Bergmans Cc: xen-users@lists.xen.org Subject: Re: [Xen-users] Testing High-Frequency Virtual Server Monitoring X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org John, I looks like an interesting project. You may want to look at using Host sFlow agents on the Xen hypervisors (rather than collectd agents): http://host-sflow.sourceforge.net/ The Host sFlow agent (hsflowd) is very efficient, it directly links to Xen's libxenstat library to pick up statistics and exports a full range of standard Hypervisor and virtual machine metrics: http://sflow.org/sflow_host.txt FYI The sFlow metrics are compatible with libvirt. There are a lot of similarities between the sFlow and collectd protocols, both send metrics as XDR encoded data structures over UDP. Looking at your diagram, all you would need to do is add an sFlow input to your AMQP message broker. Here is a link with some resources: http://blog.sflow.com/2010/01/developer-resources.html Another possible route to incorporating the sFlow metrics would be to use Ganglia's gmond daemon. It accepts sFlow metrics and stores their latest values in a hash table. You can then poll gmond using TCP to retrieving an XML document containing all the metrics. http://blog.sflow.com/2011/07/ganglia-32-released.html http://code.google.com/p/embeddedgmetric/wiki/ParsingGmond Cheers, Peter On Fri, Sep 21, 2012 at 11:06 AM, John Bergmans wrote: > Hi xen-users. > > I've developed "collectdViewer", a system for high-frequency (2x per > second), browser-based server monitoring that uses collectd for statistics > collection: http://collectdviewer.com. > > It turns out that there's a "libvirt" plugin for collectd which should, in > theory, enable collectdViewer to monitor the performance of servers > virtualized by Xen, without the need to install a daemon in the virtual > server itself (http://collectd.org/wiki/index.php/Plugin:libvirt) > > Since I'm not familiar with Xen, I'm wondering if anyone on this list would > be interested in working with me to demonstrate this capability. Here's a > schematic of what how I think the demo system would be put together: > http://collectdviewer.com/applications.html#high_frequency_monitoring_for_virtual_servers > > Please contact me if you'd like to collaborate or have any questions. > > Regards, > > John Bergmans > Principal Engineer / Owner > Bergmans Mechatronics LLC > 714-474-8956 > @jbergmans > www.bergmans.com > skype: johnbergmans > > > > > > _______________________________________________ > Xen-users mailing list > Xen-users@lists.xen.org > http://lists.xen.org/xen-users _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Fri Sep 21 18:41:06 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Fri, 21 Sep 2012 18:41:06 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TF89I-0000Vp-Vt; Fri, 21 Sep 2012 18:40:24 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TF89H-0000Vg-Cn for xen-users@lists.xen.org; Fri, 21 Sep 2012 18:40:23 +0000 Received: from [85.158.137.99:36955] by server-13.bemta-3.messagelabs.com id F7/FF-01606-694BC505; Fri, 21 Sep 2012 18:40:22 +0000 X-Env-Sender: peter.phaal@gmail.com X-Msg-Ref: server-15.tower-217.messagelabs.com!1348252819!16285644!1 X-Originating-IP: [209.85.216.52] X-SpamReason: No, hits=0.3 required=7.0 tests=ML_RADAR_SPEW_LINKS_14, ML_RADAR_SPEW_LINKS_23,RCVD_BY_IP,spamassassin: X-StarScan-Received: X-StarScan-Version: 6.6.1.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 31497 invoked from network); 21 Sep 2012 18:40:20 -0000 Received: from mail-qa0-f52.google.com (HELO mail-qa0-f52.google.com) (209.85.216.52) by server-15.tower-217.messagelabs.com with RC4-SHA encrypted SMTP; 21 Sep 2012 18:40:20 -0000 Received: by qabg24 with SMTP id g24so946380qab.11 for ; Fri, 21 Sep 2012 11:40:19 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=i9dQ7ueX36Phn3D2lUkuhEM1OAchhKnQc1o/iYo69T8=; b=ku/wOQ6bKsNDyGAulxBjqoQpbZB+K41Rc73N+3m8U2Dbf8qOjsc0nzj/58TSOOag9J 7SuADSYgWjeewczbo3QjcUHPNcNEgzEoMby8FKOH++AxNZvMw7S2tsXAKf7030Ay6egc KKQ9exaODB7M7npBYQsf7ehhEGXZeHt1Ey+4xr36KicNiIk3KdGey0wd05J5DjycDfE6 lgD2efHDSPThQZgP5Txtmb493m0ERp0qohO3pyeUpeW8qhPgSYiI6+A0+pBGSNlaWjdt dNIvHLiYpYEJkBs6UdHn6NrAcFm2dhXb6Zko7MUO/Rh3yShZzbGFl0vPC7BzRIa1Zz8u 5fjQ== MIME-Version: 1.0 Received: by 10.224.196.132 with SMTP id eg4mr14154845qab.93.1348252818994; Fri, 21 Sep 2012 11:40:18 -0700 (PDT) Received: by 10.49.15.133 with HTTP; Fri, 21 Sep 2012 11:40:18 -0700 (PDT) In-Reply-To: <6D09C18D-3866-4DE4-B576-D1492B760EC2@bergmans.com> References: <6D09C18D-3866-4DE4-B576-D1492B760EC2@bergmans.com> Date: Fri, 21 Sep 2012 11:40:18 -0700 Message-ID: From: Peter Phaal To: John Bergmans Cc: xen-users@lists.xen.org Subject: Re: [Xen-users] Testing High-Frequency Virtual Server Monitoring X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org John, I looks like an interesting project. You may want to look at using Host sFlow agents on the Xen hypervisors (rather than collectd agents): http://host-sflow.sourceforge.net/ The Host sFlow agent (hsflowd) is very efficient, it directly links to Xen's libxenstat library to pick up statistics and exports a full range of standard Hypervisor and virtual machine metrics: http://sflow.org/sflow_host.txt FYI The sFlow metrics are compatible with libvirt. There are a lot of similarities between the sFlow and collectd protocols, both send metrics as XDR encoded data structures over UDP. Looking at your diagram, all you would need to do is add an sFlow input to your AMQP message broker. Here is a link with some resources: http://blog.sflow.com/2010/01/developer-resources.html Another possible route to incorporating the sFlow metrics would be to use Ganglia's gmond daemon. It accepts sFlow metrics and stores their latest values in a hash table. You can then poll gmond using TCP to retrieving an XML document containing all the metrics. http://blog.sflow.com/2011/07/ganglia-32-released.html http://code.google.com/p/embeddedgmetric/wiki/ParsingGmond Cheers, Peter On Fri, Sep 21, 2012 at 11:06 AM, John Bergmans wrote: > Hi xen-users. > > I've developed "collectdViewer", a system for high-frequency (2x per > second), browser-based server monitoring that uses collectd for statistics > collection: http://collectdviewer.com. > > It turns out that there's a "libvirt" plugin for collectd which should, in > theory, enable collectdViewer to monitor the performance of servers > virtualized by Xen, without the need to install a daemon in the virtual > server itself (http://collectd.org/wiki/index.php/Plugin:libvirt) > > Since I'm not familiar with Xen, I'm wondering if anyone on this list would > be interested in working with me to demonstrate this capability. Here's a > schematic of what how I think the demo system would be put together: > http://collectdviewer.com/applications.html#high_frequency_monitoring_for_virtual_servers > > Please contact me if you'd like to collaborate or have any questions. > > Regards, > > John Bergmans > Principal Engineer / Owner > Bergmans Mechatronics LLC > 714-474-8956 > @jbergmans > www.bergmans.com > skype: johnbergmans > > > > > > _______________________________________________ > Xen-users mailing list > Xen-users@lists.xen.org > http://lists.xen.org/xen-users _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Fri Sep 21 20:18:42 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Fri, 21 Sep 2012 20:18:42 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TF9fU-0005Ga-C3; Fri, 21 Sep 2012 20:17:44 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TF9dj-0005DG-9J for xen-users@lists.xensource.com; Fri, 21 Sep 2012 20:15:55 +0000 Received: from [85.158.138.51:54245] by server-15.bemta-3.messagelabs.com id EC/57-09665-AFACC505; Fri, 21 Sep 2012 20:15:54 +0000 X-Env-Sender: jim.molnar@gmail.com X-Msg-Ref: server-9.tower-174.messagelabs.com!1348258553!29831120!1 X-Originating-IP: [209.85.212.177] X-SpamReason: No, hits=1.2 required=7.0 tests=HTML_20_30,HTML_MESSAGE, ML_RADAR_SPEW_LINKS_14,RCVD_BY_IP,spamassassin: X-StarScan-Received: X-StarScan-Version: 6.6.1.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 9739 invoked from network); 21 Sep 2012 20:15:53 -0000 Received: from mail-wi0-f177.google.com (HELO mail-wi0-f177.google.com) (209.85.212.177) by server-9.tower-174.messagelabs.com with RC4-SHA encrypted SMTP; 21 Sep 2012 20:15:53 -0000 Received: by wibhn17 with SMTP id hn17so2132357wib.6 for ; Fri, 21 Sep 2012 13:15:53 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type; bh=9/nx5Pm80OyCbUrfsQL8KFs07UfwYTc3pgXOpCxIkNY=; b=ymxCWtxK4vSJdQOdRsDl9ucAkWg/S1tkIRFOdLQb2TizPokQbnQzRkEWtn/13HtVuE gWLlwOQukO9yCAQaVgHbo/N+YMVgQwwHHcYa/KyhSouNw3M9C+pRVIsMqeaMs/gH+FHS vZeBdd9JnNZ37EyPfdYB6TVflECRGglDKQ/lG/KvBnjWbxfe4hCzCg9GklhLAcyOQUBb odc6Yf8VASz43Onyo53tKhSNSVqKB/VTbFK1OnDYqZlHQDIXiJPn2hDnwUa7PYPrZLUU I8stWeR9H45Q4HvTEf5KiWQULsryzfm0hoG2CGIlVnc1BCSp4bqWGc8wI/freb+cao8h +fXw== Received: by 10.216.225.27 with SMTP id y27mr1517715wep.141.1348258552972; Fri, 21 Sep 2012 13:15:52 -0700 (PDT) MIME-Version: 1.0 Received: by 10.216.9.212 with HTTP; Fri, 21 Sep 2012 13:15:32 -0700 (PDT) In-Reply-To: References: <1342190462.7075.128.camel@wotan2> <6035A0D088A63A46850C3988ED045A4B2998FF73@BITCOM1.int.sbss.com.au> From: Jim Molnar Date: Fri, 21 Sep 2012 16:15:32 -0400 Message-ID: To: Ricardo Jesus X-Mailman-Approved-At: Fri, 21 Sep 2012 20:17:43 +0000 Cc: xen-users@lists.xensource.com Subject: Re: [Xen-users] win2008 crashes unde xen X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============5054425493286893703==" Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org --===============5054425493286893703== Content-Type: multipart/alternative; boundary=0016e6dd98331d861804ca3be80e --0016e6dd98331d861804ca3be80e Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: quoted-printable I'm not familiar with that configuration. Here's a normal config for one of our VM's Here is a copy of the vm config file for one of the working vm=92s. Should it be added in here ? If so where? Does it effect any other machines on the same host at all? Sorry I'm fairly new to Xen. ---------------------------------- name =3D 'tryprx3expmb2' kernel =3D "/usr/lib/xen/boot/hvmloader" builder=3D'hvm' memory =3D 24576 vcpus =3D 8 on_poweroff =3D 'destroy' on_reboot =3D 'restart' on_crash =3D 'destroy' vif =3D [ 'mac=3D00:16:3e:00:13:c2, type=3Dioemu, bridge=3Dbr0' ] pae=3D1 acpi =3D 1 apic =3D 1 #disk =3D [ 'phy:/dev/iscsi/svc4_sg01_std_vg01-tryprx3expmb2_01,hda,w','phy:/dev/iscsi/= svc4_sg01_econo_vg01-tryprx3expmb2_02,hdb,w' ] disk =3D [ 'phy:/dev/iscsi/svc4_sg01_std_vg01-tryprx3expmb2_01,hda,w', 'phy:/dev/iscsi/svc4_sg01_econo_vg01-tryprx3expmb2_02,hdb,w', 'phy:/dev/iscsi/svc4_sg01_econo_vg01-tryprx3expmb2_03,hdc,w', 'phy:/dev/iscsi/svc4_sg01_econo_vg01-tryprx3expmb2_04,hdd,w', 'phy:/dev/iscsi/svc4_sg01_econo_vg01-tryprx3expmb2_05,hde,w', 'phy:/dev/iscsi/svc4_sg01_econo_vg01-tryprx3expmb2_06,hdf,w', 'phy:/dev/iscsi/svc4_sg01_econo_vg01-tryprx3expmb2_07,hdg,w', 'phy:/dev/iscsi/svc4_sg01_econo_vg01-tryprx3expmb2_08,hdh,w', 'phy:/dev/iscsi/svc4_sg01_econo_vg01-tryprx3expmb2_09,hdi,w', 'phy:/dev/iscsi/svc4_sg01_econo_vg01-tryprx3expmb2_10,hdj,w', 'phy:/dev/iscsi/svc4_sg01_econo_vg01-tryprx3expmb2_11,hdk,w' , 'phy:/dev/iscsi/svc4_sg01_econo_vg01-tryprx3expmb2_12,hdl,w', 'phy:/dev/iscsi/svc4_sg01_econo_vg01-tryprx3expmb2_13,hdm,w', 'phy:/dev/iscsi/svc4_sg01_econo_vg01-tryprx3expmb2_14,hdn,w' , 'phy:/dev/iscsi/svc4_sg01_econo_vg01-tryprx3expmb2_15,hdo,w', 'phy:/dev/iscsi/svc4_sg01_econo_vg01-tryprx3expmb2_16,hdp,w' , 'phy:/dev/iscsi/svc4_sg01_econo_vg01-tryprx3expmb2_17,hdq,w', 'phy:/dev/iscsi/svc4_sg01_econo_vg01-tryprx3expmb2_18,hdr,w', 'phy:/dev/iscsi/svc4_sg01_econo_vg01-tryprx3expmb2_19,hds,w', 'phy:/dev/iscsi/svc4_sg01_econo_vg01-tryprx3expmb2_20,hdt,w' ] device_model =3D '/usr/lib64/xen/bin/qemu-dm' # boot on hard disk (c) or CD-ROM (d) # default: hard disk, cd-rom, floppy boot=3D"c" sdl=3D0 vnc=3D1 vncconsole=3D1 vncpasswd=3D'' serial=3D'pty' usbdevice=3D'tablet' localtime=3D1 cpus =3D '^0' ---------------------------------------- On Fri, Sep 21, 2012 at 2:28 PM, Ricardo Jesus wrote: > Does your Windows HVM config contain viridian=3D1? > > On Fri, Sep 21, 2012 at 4:51 PM, Jim Molnar wrote: > > > > > > James Harper bendigoit.com.au> writes: > > > >> > >> > > >> > I have 358 drivers and error looks like this one > >> > http://jbeekman.nl/bsod20120117_1953.png > >> > > >> > >> If that is your BSoD then the crash does appear to be in xenvbd.sys > which is a > > GPLPV driver. Can you have a look > >> in c:\windows\minidump and see if there is a file in there that > approximately > > matches the time of your bluescreen? > >> > >> If so, can you zip it up and email it to me? I also need to know the > exact > > version of GPLPV you are using so I can > >> load the correct symbols in the debugger. > >> > >> Thanks > >> > >> James > >> > > > > Hey James, We're using your Driver as well 11.0.308 and we're having th= e > issue > > of a BSOD during Exchange 2010 replication. Was this issue ever fixed= ? > Do you > > still need a dump from the Debug version of the driver? If anyone know= s > the fix > > to this please email me - jim.molnar "at" Gmail dot com Thanks a lot. > > > > Jim. > > > > > > > > _______________________________________________ > > Xen-users mailing list > > Xen-users@lists.xen.org > > http://lists.xen.org/xen-users > --0016e6dd98331d861804ca3be80e Content-Type: text/html; charset=windows-1252 Content-Transfer-Encoding: quoted-printable I'm not familiar with that configuration.=A0 Here's a normal config= for one of our VM's

=A0

Here is a copy of the vm config file for one = of the working vm=92s.=A0 Should it be added in here ?=A0 If so where?=A0 D= oes it effect any other machines on the same host at all? Sorry I'm fai= rly new to Xen.

----------------------------------

name =3D 'tryprx3expmb2&#= 39;
kernel =3D "/usr/lib/xen/boot/hvmloader"
builder=3D'= ;hvm'
memory =3D 24576
vcpus =3D 8

on_poweroff =3D 'de= stroy'
on_reboot =3D 'restart'
on_crash =3D 'destroy'

vi= f =3D [ 'mac=3D00:16:3e:00:13:c2, type=3Dioemu, bridge=3Dbr0' ]
= pae=3D1
acpi =3D 1
apic =3D 1
#disk =3D [=A0 'phy:/dev/iscsi/s= vc4_sg01_std_vg01-tryprx3expmb2_01,hda,w','phy:/dev/iscsi/svc4_sg01= _econo_vg01-tryprx3expmb2_02,hdb,w'=A0 ]
disk =3D [=A0 'phy:/dev/iscsi/svc4_sg01_std_vg01-tryprx3expmb2_01,hda,w= ', 'phy:/dev/iscsi/svc4_sg01_econo_vg01-tryprx3expmb2_02,hdb,w'= ,=A0 'phy:/dev/iscsi/svc4_sg01_econo_vg01-tryprx3expmb2_03,hdc,w', = 'phy:/dev/iscsi/svc4_sg01_econo_vg01-tryprx3expmb2_04,hdd,w', '= phy:/dev/iscsi/svc4_sg01_econo_vg01-tryprx3expmb2_05,hde,w', 'phy:/= dev/iscsi/svc4_sg01_econo_vg01-tryprx3expmb2_06,hdf,w', 'phy:/dev/i= scsi/svc4_sg01_econo_vg01-tryprx3expmb2_07,hdg,w', 'phy:/dev/iscsi/= svc4_sg01_econo_vg01-tryprx3expmb2_08,hdh,w', 'phy:/dev/iscsi/svc4_= sg01_econo_vg01-tryprx3expmb2_09,hdi,w', 'phy:/dev/iscsi/svc4_sg01_= econo_vg01-tryprx3expmb2_10,hdj,w', 'phy:/dev/iscsi/svc4_sg01_econo= _vg01-tryprx3expmb2_11,hdk,w' , 'phy:/dev/iscsi/svc4_sg01_econo_vg0= 1-tryprx3expmb2_12,hdl,w', 'phy:/dev/iscsi/svc4_sg01_econo_vg01-try= prx3expmb2_13,hdm,w', 'phy:/dev/iscsi/svc4_sg01_econo_vg01-tryprx3e= xpmb2_14,hdn,w' , 'phy:/dev/iscsi/svc4_sg01_econo_vg01-tryprx3expmb= 2_15,hdo,w', 'phy:/dev/iscsi/svc4_sg01_econo_vg01-tryprx3expmb2_16,= hdp,w' , 'phy:/dev/iscsi/svc4_sg01_econo_vg01-tryprx3expmb2_17,hdq,= w', 'phy:/dev/iscsi/svc4_sg01_econo_vg01-tryprx3expmb2_18,hdr,w'= ;, 'phy:/dev/iscsi/svc4_sg01_econo_vg01-tryprx3expmb2_19,hds,w', &#= 39;phy:/dev/iscsi/svc4_sg01_econo_vg01-tryprx3expmb2_20,hdt,w' ]


device_model =3D '/usr/lib64/xen/bin/qemu-dm'

# boot= on=A0 hard disk (c) or CD-ROM (d)
# default: hard disk, cd-rom, floppy<= br>boot=3D"c"
sdl=3D0
vnc=3D1
vncconsole=3D1
vncpassw= d=3D''
serial=3D'pty'
usbdevice=3D'tablet'
localtime=3D1
= cpus =3D '^0'

----------------------------------------

On Fri, Sep 21, 2012 at 2:28 PM, Ricardo J= esus <ricardo.meb.jesus@gmail.com> wrote:
Does your Windows HVM config contain viridia= n=3D1?

On Fri, Sep 21, 2012 at 4:51 PM, Jim Molnar <Jim.molnar@gmail.com> wrote:
>
>
> James Harper <james.harper <at> bendigoit.com.au> writes:
>
>>
>> >
>> > I have 358 drivers and error looks like this one
>> > http://jbeekman.nl/bsod20120117_1953.png
>> >
>>
>> If that is your BSoD then the crash does appear to be in xenvbd.sy= s which is a
> GPLPV driver. Can you have a look
>> in c:\windows\minidump and see if there is a file in there that ap= proximately
> matches the time of your bluescreen?
>>
>> If so, can you zip it up and email it to me? I also need to know t= he exact
> version of GPLPV you are using so I can
>> load the correct symbols in the debugger.
>>
>> Thanks
>>
>> James
>>
>
> Hey James, We're using your Driver as well 11.0.308 and we're = having the issue
> of a BSOD during Exchange 2010 replication. =A0 Was this issue ever fi= xed? =A0Do you
> still need a dump from the Debug version of the driver? =A0If anyone k= nows the fix
> to this please email me - jim.molnar "at" Gmail dot com =A0T= hanks a lot.
>
> Jim.
>
>
>
> _______________________________________________
> Xen-users mailing list
> Xen-users@lists.xen.org=
> http://li= sts.xen.org/xen-users

--0016e6dd98331d861804ca3be80e-- --===============5054425493286893703== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users --===============5054425493286893703==-- From xen-users-bounces@lists.xen.org Fri Sep 21 20:18:42 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Fri, 21 Sep 2012 20:18:42 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TF9fU-0005Ga-C3; Fri, 21 Sep 2012 20:17:44 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TF9dj-0005DG-9J for xen-users@lists.xensource.com; Fri, 21 Sep 2012 20:15:55 +0000 Received: from [85.158.138.51:54245] by server-15.bemta-3.messagelabs.com id EC/57-09665-AFACC505; Fri, 21 Sep 2012 20:15:54 +0000 X-Env-Sender: jim.molnar@gmail.com X-Msg-Ref: server-9.tower-174.messagelabs.com!1348258553!29831120!1 X-Originating-IP: [209.85.212.177] X-SpamReason: No, hits=1.2 required=7.0 tests=HTML_20_30,HTML_MESSAGE, ML_RADAR_SPEW_LINKS_14,RCVD_BY_IP,spamassassin: X-StarScan-Received: X-StarScan-Version: 6.6.1.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 9739 invoked from network); 21 Sep 2012 20:15:53 -0000 Received: from mail-wi0-f177.google.com (HELO mail-wi0-f177.google.com) (209.85.212.177) by server-9.tower-174.messagelabs.com with RC4-SHA encrypted SMTP; 21 Sep 2012 20:15:53 -0000 Received: by wibhn17 with SMTP id hn17so2132357wib.6 for ; Fri, 21 Sep 2012 13:15:53 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type; bh=9/nx5Pm80OyCbUrfsQL8KFs07UfwYTc3pgXOpCxIkNY=; b=ymxCWtxK4vSJdQOdRsDl9ucAkWg/S1tkIRFOdLQb2TizPokQbnQzRkEWtn/13HtVuE gWLlwOQukO9yCAQaVgHbo/N+YMVgQwwHHcYa/KyhSouNw3M9C+pRVIsMqeaMs/gH+FHS vZeBdd9JnNZ37EyPfdYB6TVflECRGglDKQ/lG/KvBnjWbxfe4hCzCg9GklhLAcyOQUBb odc6Yf8VASz43Onyo53tKhSNSVqKB/VTbFK1OnDYqZlHQDIXiJPn2hDnwUa7PYPrZLUU I8stWeR9H45Q4HvTEf5KiWQULsryzfm0hoG2CGIlVnc1BCSp4bqWGc8wI/freb+cao8h +fXw== Received: by 10.216.225.27 with SMTP id y27mr1517715wep.141.1348258552972; Fri, 21 Sep 2012 13:15:52 -0700 (PDT) MIME-Version: 1.0 Received: by 10.216.9.212 with HTTP; Fri, 21 Sep 2012 13:15:32 -0700 (PDT) In-Reply-To: References: <1342190462.7075.128.camel@wotan2> <6035A0D088A63A46850C3988ED045A4B2998FF73@BITCOM1.int.sbss.com.au> From: Jim Molnar Date: Fri, 21 Sep 2012 16:15:32 -0400 Message-ID: To: Ricardo Jesus X-Mailman-Approved-At: Fri, 21 Sep 2012 20:17:43 +0000 Cc: xen-users@lists.xensource.com Subject: Re: [Xen-users] win2008 crashes unde xen X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============5054425493286893703==" Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org --===============5054425493286893703== Content-Type: multipart/alternative; boundary=0016e6dd98331d861804ca3be80e --0016e6dd98331d861804ca3be80e Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: quoted-printable I'm not familiar with that configuration. Here's a normal config for one of our VM's Here is a copy of the vm config file for one of the working vm=92s. Should it be added in here ? If so where? Does it effect any other machines on the same host at all? Sorry I'm fairly new to Xen. ---------------------------------- name =3D 'tryprx3expmb2' kernel =3D "/usr/lib/xen/boot/hvmloader" builder=3D'hvm' memory =3D 24576 vcpus =3D 8 on_poweroff =3D 'destroy' on_reboot =3D 'restart' on_crash =3D 'destroy' vif =3D [ 'mac=3D00:16:3e:00:13:c2, type=3Dioemu, bridge=3Dbr0' ] pae=3D1 acpi =3D 1 apic =3D 1 #disk =3D [ 'phy:/dev/iscsi/svc4_sg01_std_vg01-tryprx3expmb2_01,hda,w','phy:/dev/iscsi/= svc4_sg01_econo_vg01-tryprx3expmb2_02,hdb,w' ] disk =3D [ 'phy:/dev/iscsi/svc4_sg01_std_vg01-tryprx3expmb2_01,hda,w', 'phy:/dev/iscsi/svc4_sg01_econo_vg01-tryprx3expmb2_02,hdb,w', 'phy:/dev/iscsi/svc4_sg01_econo_vg01-tryprx3expmb2_03,hdc,w', 'phy:/dev/iscsi/svc4_sg01_econo_vg01-tryprx3expmb2_04,hdd,w', 'phy:/dev/iscsi/svc4_sg01_econo_vg01-tryprx3expmb2_05,hde,w', 'phy:/dev/iscsi/svc4_sg01_econo_vg01-tryprx3expmb2_06,hdf,w', 'phy:/dev/iscsi/svc4_sg01_econo_vg01-tryprx3expmb2_07,hdg,w', 'phy:/dev/iscsi/svc4_sg01_econo_vg01-tryprx3expmb2_08,hdh,w', 'phy:/dev/iscsi/svc4_sg01_econo_vg01-tryprx3expmb2_09,hdi,w', 'phy:/dev/iscsi/svc4_sg01_econo_vg01-tryprx3expmb2_10,hdj,w', 'phy:/dev/iscsi/svc4_sg01_econo_vg01-tryprx3expmb2_11,hdk,w' , 'phy:/dev/iscsi/svc4_sg01_econo_vg01-tryprx3expmb2_12,hdl,w', 'phy:/dev/iscsi/svc4_sg01_econo_vg01-tryprx3expmb2_13,hdm,w', 'phy:/dev/iscsi/svc4_sg01_econo_vg01-tryprx3expmb2_14,hdn,w' , 'phy:/dev/iscsi/svc4_sg01_econo_vg01-tryprx3expmb2_15,hdo,w', 'phy:/dev/iscsi/svc4_sg01_econo_vg01-tryprx3expmb2_16,hdp,w' , 'phy:/dev/iscsi/svc4_sg01_econo_vg01-tryprx3expmb2_17,hdq,w', 'phy:/dev/iscsi/svc4_sg01_econo_vg01-tryprx3expmb2_18,hdr,w', 'phy:/dev/iscsi/svc4_sg01_econo_vg01-tryprx3expmb2_19,hds,w', 'phy:/dev/iscsi/svc4_sg01_econo_vg01-tryprx3expmb2_20,hdt,w' ] device_model =3D '/usr/lib64/xen/bin/qemu-dm' # boot on hard disk (c) or CD-ROM (d) # default: hard disk, cd-rom, floppy boot=3D"c" sdl=3D0 vnc=3D1 vncconsole=3D1 vncpasswd=3D'' serial=3D'pty' usbdevice=3D'tablet' localtime=3D1 cpus =3D '^0' ---------------------------------------- On Fri, Sep 21, 2012 at 2:28 PM, Ricardo Jesus wrote: > Does your Windows HVM config contain viridian=3D1? > > On Fri, Sep 21, 2012 at 4:51 PM, Jim Molnar wrote: > > > > > > James Harper bendigoit.com.au> writes: > > > >> > >> > > >> > I have 358 drivers and error looks like this one > >> > http://jbeekman.nl/bsod20120117_1953.png > >> > > >> > >> If that is your BSoD then the crash does appear to be in xenvbd.sys > which is a > > GPLPV driver. Can you have a look > >> in c:\windows\minidump and see if there is a file in there that > approximately > > matches the time of your bluescreen? > >> > >> If so, can you zip it up and email it to me? I also need to know the > exact > > version of GPLPV you are using so I can > >> load the correct symbols in the debugger. > >> > >> Thanks > >> > >> James > >> > > > > Hey James, We're using your Driver as well 11.0.308 and we're having th= e > issue > > of a BSOD during Exchange 2010 replication. Was this issue ever fixed= ? > Do you > > still need a dump from the Debug version of the driver? If anyone know= s > the fix > > to this please email me - jim.molnar "at" Gmail dot com Thanks a lot. > > > > Jim. > > > > > > > > _______________________________________________ > > Xen-users mailing list > > Xen-users@lists.xen.org > > http://lists.xen.org/xen-users > --0016e6dd98331d861804ca3be80e Content-Type: text/html; charset=windows-1252 Content-Transfer-Encoding: quoted-printable I'm not familiar with that configuration.=A0 Here's a normal config= for one of our VM's

=A0

Here is a copy of the vm config file for one = of the working vm=92s.=A0 Should it be added in here ?=A0 If so where?=A0 D= oes it effect any other machines on the same host at all? Sorry I'm fai= rly new to Xen.

----------------------------------

name =3D 'tryprx3expmb2&#= 39;
kernel =3D "/usr/lib/xen/boot/hvmloader"
builder=3D'= ;hvm'
memory =3D 24576
vcpus =3D 8

on_poweroff =3D 'de= stroy'
on_reboot =3D 'restart'
on_crash =3D 'destroy'

vi= f =3D [ 'mac=3D00:16:3e:00:13:c2, type=3Dioemu, bridge=3Dbr0' ]
= pae=3D1
acpi =3D 1
apic =3D 1
#disk =3D [=A0 'phy:/dev/iscsi/s= vc4_sg01_std_vg01-tryprx3expmb2_01,hda,w','phy:/dev/iscsi/svc4_sg01= _econo_vg01-tryprx3expmb2_02,hdb,w'=A0 ]
disk =3D [=A0 'phy:/dev/iscsi/svc4_sg01_std_vg01-tryprx3expmb2_01,hda,w= ', 'phy:/dev/iscsi/svc4_sg01_econo_vg01-tryprx3expmb2_02,hdb,w'= ,=A0 'phy:/dev/iscsi/svc4_sg01_econo_vg01-tryprx3expmb2_03,hdc,w', = 'phy:/dev/iscsi/svc4_sg01_econo_vg01-tryprx3expmb2_04,hdd,w', '= phy:/dev/iscsi/svc4_sg01_econo_vg01-tryprx3expmb2_05,hde,w', 'phy:/= dev/iscsi/svc4_sg01_econo_vg01-tryprx3expmb2_06,hdf,w', 'phy:/dev/i= scsi/svc4_sg01_econo_vg01-tryprx3expmb2_07,hdg,w', 'phy:/dev/iscsi/= svc4_sg01_econo_vg01-tryprx3expmb2_08,hdh,w', 'phy:/dev/iscsi/svc4_= sg01_econo_vg01-tryprx3expmb2_09,hdi,w', 'phy:/dev/iscsi/svc4_sg01_= econo_vg01-tryprx3expmb2_10,hdj,w', 'phy:/dev/iscsi/svc4_sg01_econo= _vg01-tryprx3expmb2_11,hdk,w' , 'phy:/dev/iscsi/svc4_sg01_econo_vg0= 1-tryprx3expmb2_12,hdl,w', 'phy:/dev/iscsi/svc4_sg01_econo_vg01-try= prx3expmb2_13,hdm,w', 'phy:/dev/iscsi/svc4_sg01_econo_vg01-tryprx3e= xpmb2_14,hdn,w' , 'phy:/dev/iscsi/svc4_sg01_econo_vg01-tryprx3expmb= 2_15,hdo,w', 'phy:/dev/iscsi/svc4_sg01_econo_vg01-tryprx3expmb2_16,= hdp,w' , 'phy:/dev/iscsi/svc4_sg01_econo_vg01-tryprx3expmb2_17,hdq,= w', 'phy:/dev/iscsi/svc4_sg01_econo_vg01-tryprx3expmb2_18,hdr,w'= ;, 'phy:/dev/iscsi/svc4_sg01_econo_vg01-tryprx3expmb2_19,hds,w', &#= 39;phy:/dev/iscsi/svc4_sg01_econo_vg01-tryprx3expmb2_20,hdt,w' ]


device_model =3D '/usr/lib64/xen/bin/qemu-dm'

# boot= on=A0 hard disk (c) or CD-ROM (d)
# default: hard disk, cd-rom, floppy<= br>boot=3D"c"
sdl=3D0
vnc=3D1
vncconsole=3D1
vncpassw= d=3D''
serial=3D'pty'
usbdevice=3D'tablet'
localtime=3D1
= cpus =3D '^0'

----------------------------------------

On Fri, Sep 21, 2012 at 2:28 PM, Ricardo J= esus <ricardo.meb.jesus@gmail.com> wrote:
Does your Windows HVM config contain viridia= n=3D1?

On Fri, Sep 21, 2012 at 4:51 PM, Jim Molnar <Jim.molnar@gmail.com> wrote:
>
>
> James Harper <james.harper <at> bendigoit.com.au> writes:
>
>>
>> >
>> > I have 358 drivers and error looks like this one
>> > http://jbeekman.nl/bsod20120117_1953.png
>> >
>>
>> If that is your BSoD then the crash does appear to be in xenvbd.sy= s which is a
> GPLPV driver. Can you have a look
>> in c:\windows\minidump and see if there is a file in there that ap= proximately
> matches the time of your bluescreen?
>>
>> If so, can you zip it up and email it to me? I also need to know t= he exact
> version of GPLPV you are using so I can
>> load the correct symbols in the debugger.
>>
>> Thanks
>>
>> James
>>
>
> Hey James, We're using your Driver as well 11.0.308 and we're = having the issue
> of a BSOD during Exchange 2010 replication. =A0 Was this issue ever fi= xed? =A0Do you
> still need a dump from the Debug version of the driver? =A0If anyone k= nows the fix
> to this please email me - jim.molnar "at" Gmail dot com =A0T= hanks a lot.
>
> Jim.
>
>
>
> _______________________________________________
> Xen-users mailing list
> Xen-users@lists.xen.org=
> http://li= sts.xen.org/xen-users

--0016e6dd98331d861804ca3be80e-- --===============5054425493286893703== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users --===============5054425493286893703==-- From xen-users-bounces@lists.xen.org Sat Sep 22 01:02:47 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Sat, 22 Sep 2012 01:02:47 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TFE5z-000404-DC; Sat, 22 Sep 2012 01:01:23 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TFE5x-0003eS-Kl for xen-users@lists.xen.org; Sat, 22 Sep 2012 01:01:22 +0000 Received: from [85.158.137.99:55879] by server-11.bemta-3.messagelabs.com id 4C/63-30250-0ED0D505; Sat, 22 Sep 2012 01:01:20 +0000 X-Env-Sender: krouzinh@gmail.com X-Msg-Ref: server-16.tower-217.messagelabs.com!1348275677!18671100!1 X-Originating-IP: [209.85.160.45] X-SpamReason: No, hits=0.4 required=7.0 tests=HTML_30_40,HTML_MESSAGE, ML_RADAR_SPEW_LINKS_14,RCVD_BY_IP,spamassassin: X-StarScan-Received: X-StarScan-Version: 6.6.1.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 15182 invoked from network); 22 Sep 2012 01:01:18 -0000 Received: from mail-pb0-f45.google.com (HELO mail-pb0-f45.google.com) (209.85.160.45) by server-16.tower-217.messagelabs.com with RC4-SHA encrypted SMTP; 22 Sep 2012 01:01:18 -0000 Received: by pbbrp12 with SMTP id rp12so8799720pbb.32 for ; Fri, 21 Sep 2012 18:01:16 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:from:date:message-id:subject:to:content-type; bh=5hP7tEoirbzUJvnbMsEpWZYfsyPsObqUnRMJqSwYK0o=; b=P9rONsZED8xPvUsoZg2+KCfegIgEcLdwh5W3/rDwqA809zAN1oba1sIHfkqRC0Im8P 9E6kuvE+5Sr3aWz8sZ+AKY6uO9NGK8kXRlAm++ibCyz5/OCgKXguQfK0ImsMAYJ5q881 lhuLwIjHFloSSMpGAYpsbEbpGVMNitTQSAVd0QsYwaIA9HZOvKya5TP/3E1nyzGex81P ViT2kPysrSoSjJ6pxmnhqbRnNN4L55Gmzglj0y0fi+CPcnJ3eyXt9H6pC0s3rQLsXoc2 Mh5fgIrBSEDWhA4Ta10tkgUTxvhuy+4xR6XkntH2LJ8y9/BukpqaurhffpcnJGmPRMSU 1Ebw== Received: by 10.66.75.232 with SMTP id f8mr16898318paw.59.1348275676407; Fri, 21 Sep 2012 18:01:16 -0700 (PDT) MIME-Version: 1.0 Received: by 10.66.135.5 with HTTP; Fri, 21 Sep 2012 18:00:36 -0700 (PDT) From: Carol Date: Fri, 21 Sep 2012 22:00:36 -0300 Message-ID: To: xen-users@lists.xen.org Subject: [Xen-users] Route networking xen 4 X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============1698442214203510209==" Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org --===============1698442214203510209== Content-Type: multipart/alternative; boundary=f46d042dfd55c0663f04ca3fe4b4 --f46d042dfd55c0663f04ca3fe4b4 Content-Type: text/plain; charset=ISO-8859-1 Hey guys, I'm facing some issues on route networking. Could someone give me a hand with route networking configuration on xen 4, please? I just wanna make dom0 communicates with domU by pinging each other, but it doesn't seem to get the network working at all. Ive been stucked on this a week or so! Here it goes some configuration on my machine - Ubuntu 12.04: first of all, my xen settings: #cat /etc/xen/xend-config.sxp (logfile /var/log/xen/xend.log) (loglevel DEBUG) (xend-unix-server yes) (network-script network-route) (vif-script vif-route) (dom0-min-mem 196) (total_available_memory 0) (dom0-cpus 0) (vncpasswd '') - #cat /etc/xen/xenroute.cfg bootloader = '/usr/lib/xen-default/bin/pygrub' vcpus = '1' memory = '526' root = '/dev/xvda2 ro' disk = [ 'file:/xen/domains/xenroute/disk.img,xvda2,w', 'file:/xen/domains/xenroute/swap.img,xvda1,w', ] name = 'xenroute' vif = [ 'ip=10.0.0.1,mac=00:16:3E:1C:4C:D3' ] on_poweroff = 'destroy' on_reboot = 'restart' on_crash = 'restart' --------------------------------------------------------------------- Dom0 settings: dom0# ifconfig eth0 Link encap:Ethernet HWaddr bc:ae:c5:9f:50:0c inet addr:192.168.0.4 Bcast:192.168.0.255 Mask:255.255.255.0 UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:0 errors:0 dropped:0 overruns:0 frame:0 TX packets:0 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:0 (0.0 B) TX bytes:0 (0.0 B) Interrupt:50 lo Link encap:Local Loopback inet addr:127.0.0.1 Mask:255.0.0.0 inet6 addr: ::1/128 Scope:Host UP LOOPBACK RUNNING MTU:16436 Metric:1 RX packets:2733 errors:0 dropped:0 overruns:0 frame:0 TX packets:2733 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:295895 (295.8 KB) TX bytes:295895 (295.8 KB) vif19.0 Link encap:Ethernet HWaddr fe:ff:ff:ff:ff:ff inet6 addr: fe80::fcff:ffff:feff:ffff/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:6 errors:0 dropped:0 overruns:0 frame:0 TX packets:709 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:32 RX bytes:384 (384.0 B) TX bytes:162795 (162.7 KB) virbr0 Link encap:Ethernet HWaddr a2:d6:e7:30:f3:9e inet addr:192.168.122.1 Bcast:192.168.122.255 Mask:255.255.255.0 UP BROADCAST MULTICAST MTU:1500 Metric:1 RX packets:0 errors:0 dropped:0 overruns:0 frame:0 TX packets:0 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:0 (0.0 B) TX bytes:0 (0.0 B) wlan0 Link encap:Ethernet HWaddr 00:26:c7:d3:28:2e inet addr:192.168.1.104 Bcast:192.168.1.255 Mask:255.255.255.0 inet6 addr: fe80::226:c7ff:fed3:282e/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:73574 errors:0 dropped:0 overruns:0 frame:0 TX packets:39730 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:73693058 (73.6 MB) TX bytes:4576434 (4.5 MB) - dom0# cat /etc/network/interfaces auto lo iface lo inet loopback auto eth0 iface eth0 inet static address 192.168.0.4 netmask 255.255.255.0 network 192.168.0.0 broadcast 192.168.0.255 gateway 192.168.0.1 - dom0# iptables -L Chain INPUT (policy ACCEPT) target prot opt source destination ACCEPT udp -- anywhere anywhere udp dpt:domain ACCEPT tcp -- anywhere anywhere tcp dpt:domain ACCEPT udp -- anywhere anywhere udp dpt:bootps ACCEPT tcp -- anywhere anywhere tcp dpt:bootps Chain FORWARD (policy ACCEPT) target prot opt source destination ACCEPT all -- anywhere anywhere PHYSDEV match --physdev-out vif19.0 --physdev-is-bridged ACCEPT udp -- anywhere anywhere PHYSDEV match --physdev-in vif19.0 --physdev-is-bridged udp spt:bootpc dpt:bootps ACCEPT all -- anywhere anywhere PHYSDEV match --physdev-out vif19.0 --physdev-is-bridged ACCEPT all -- xenroute anywhere PHYSDEV match --physdev-in vif19.0 --physdev-is-bridged ACCEPT all -- anywhere 192.168.122.0/24 state RELATED,ESTABLISHED ACCEPT all -- 192.168.122.0/24 anywhere ACCEPT all -- anywhere anywhere REJECT all -- anywhere anywhere reject-with icmp-port-unreachable REJECT all -- anywhere anywhere reject-with icmp-port-unreachable Chain OUTPUT (policy ACCEPT) target prot opt source destination - dom0# iptables -t nat -L Chain PREROUTING (policy ACCEPT) target prot opt source destination Chain INPUT (policy ACCEPT) target prot opt source destination Chain OUTPUT (policy ACCEPT) target prot opt source destination Chain POSTROUTING (policy ACCEPT) target prot opt source destination MASQUERADE tcp -- 192.168.122.0/24 !192.168.122.0/24 masq ports: 1024-65535 MASQUERADE udp -- 192.168.122.0/24 !192.168.122.0/24 masq ports: 1024-65535 MASQUERADE all -- 192.168.122.0/24 !192.168.122.0/24 MASQUERADE all -- 10.0.0.0 anywhere MASQUERADE all -- 10.0.0.0 anywhere MASQUERADE all -- anywhere anywhere MASQUERADE all -- 10.0.0.0 anywhere - dom0# sysctl -p net.ipv4.conf.all.rp_filter = 1 net.ipv4.icmp_echo_ignore_broadcasts = 1 net.ipv4.ip_forward = 1 net.ipv4.conf.default.proxy_arp = 1 net.ipv4.conf.all.proxy_arp = 1 ------------------------ My domU is named xenroute, and it has the following settings: xenroute:~# ifconfig eth0 Link encap:Ethernet HWaddr 00:16:3e:1c:4c:d3 inet addr:10.0.0.1 Bcast:10.255.255.255 Mask:255.0.0.0 inet6 addr: fe80::216:3eff:fe1c:4cd3/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:751 errors:0 dropped:0 overruns:0 frame:0 TX packets:6 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:157123 (157.1 KB) TX bytes:468 (468.0 B) Interrupt:10 lo Link encap:Local Loopback inet addr:127.0.0.1 Mask:255.0.0.0 inet6 addr: ::1/128 Scope:Host UP LOOPBACK RUNNING MTU:16436 Metric:1 RX packets:0 errors:0 dropped:0 overruns:0 frame:0 TX packets:0 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:0 (0.0 B) TX bytes:0 (0.0 B) - xenroute:~# cat /etc/network/interfaces auto lo iface lo inet loopback auto eth0 iface eth0 inet static address 10.0.0.1 gateway 192.168.0.1 # 10.0.0.254 netmask 255.255.2552.255 To set up my network I followed this tutorial : http://wiki.kartbuilding.net/index.php/Xen_Networking#Two-way_Routed_Network_2 Any clue? Appreciate your attention! Carol --f46d042dfd55c0663f04ca3fe4b4 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable

Hey guys,

I'm facing some issues on = route networking. Could someone give me a hand with route networking config= uration on xen 4, please?
I just wanna make dom0 communicates with domU = by pinging each other, but it=A0doesn't seem to get the network working= at all. Ive been stucked on this a week or so!

Here it goes some configuration on my machine - Ubuntu 12.0= 4:

first of all, my xen settings:

#ca= t /etc/xen/xend-config.sxp

(logfile /var/log/xen/xend.log)
(loglevel DEBUG)
(xen= d-unix-server yes)
(network-script network-route)
(vif-script vif-rou= te)
(dom0-min-mem 196)
(total_available_memory 0)
(dom0-cpus 0) (vncpasswd '')

-

#cat /etc/xen/xenroute.cfg=A0

bootloader =3D '/usr/lib/xen-default/bin/pygrub'vcpus =A0 =A0 =A0 =3D '1'
memory=A0 =A0 =A0 =3D '526'root=A0 =A0 =A0 =A0 =3D '/dev/xvda2 ro'
disk=A0 =A0 =A0 =A0 = =3D [
=A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 'file:/xen/domains/xenrout= e/disk.img,xvda2,w',
=A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 'file:/xen/domains/xenroute/swap.im= g,xvda1,w',
=A0 =A0 =A0 =A0 =A0 =A0 =A0 ]
name=A0 =A0 =A0 =A0 =3D= 'xenroute'
vif =A0 =A0 =A0 =A0 =3D [ 'ip=3D10.0.0.1,mac=3D0= 0:16:3E:1C:4C:D3' ]
on_poweroff =3D 'destroy'
on_reboot =A0 =3D 'restart'
on_crash=A0 =A0 =3D 'restart'= ;

-----------------------------------------------------------= ----------

Dom0 settings:

dom0# ifconfig

eth0 =A0 =A0 =A0Link encap:Ethernet = =A0HWaddr bc:ae:c5:9f:50:0c =A0
=A0 =A0 =A0 =A0 =A0 inet addr:192.168.0.= 4 =A0Bcast:192.168.0.255 =A0Mask:255.255.255.0
=A0 =A0 =A0 =A0 =A0 UP BR= OADCAST RUNNING MULTICAST =A0MTU:1500 =A0Metric:1
=A0 =A0 =A0 =A0 =A0 RX packets:0 errors:0 dropped:0 overruns:0 frame:0
= =A0 =A0 =A0 =A0 =A0 TX packets:0 errors:0 dropped:0 overruns:0 carrier:0=A0 =A0 =A0 =A0 =A0 collisions:0 txqueuelen:1000
=A0 =A0 =A0 =A0 =A0 RX= bytes:0 (0.0 B) =A0TX bytes:0 (0.0 B)
=A0 =A0 =A0 =A0 =A0 Interrupt:50

lo =A0 =A0 =A0 =A0Link encap:Local = Loopback =A0
=A0 =A0 =A0 =A0 =A0 inet addr:127.0.0.1 =A0Mask:255.0.0.0=A0 =A0 =A0 =A0 =A0 inet6 addr: ::1/128 Scope:Host
=A0 =A0 =A0 =A0 =A0= UP LOOPBACK RUNNING =A0MTU:16436 =A0Metric:1
=A0 =A0 =A0 =A0 =A0 RX pac= kets:2733 errors:0 dropped:0 overruns:0 frame:0
=A0 =A0 =A0 =A0 =A0 TX packets:2733 errors:0 dropped:0 overruns:0 carrier:0=
=A0 =A0 =A0 =A0 =A0 collisions:0 txqueuelen:0
=A0 =A0 =A0 =A0 =A0 R= X bytes:295895 (295.8 KB) =A0TX bytes:295895 (295.8 KB)

vif19.0 =A0 = Link encap:Ethernet =A0HWaddr fe:ff:ff:ff:ff:ff =A0
=A0 =A0 =A0 =A0 =A0 inet6 addr: fe80::fcff:ffff:feff:ffff/64 Scope:Link
= =A0 =A0 =A0 =A0 =A0 UP BROADCAST RUNNING MULTICAST =A0MTU:1500 =A0Metric:1<= br>=A0 =A0 =A0 =A0 =A0 RX packets:6 errors:0 dropped:0 overruns:0 frame:0=A0 =A0 =A0 =A0 =A0 TX packets:709 errors:0 dropped:0 overruns:0 carrier:= 0
=A0 =A0 =A0 =A0 =A0 collisions:0 txqueuelen:32
=A0 =A0 =A0 =A0 =A0 RX b= ytes:384 (384.0 B) =A0TX bytes:162795 (162.7 KB)

virbr0 =A0 =A0Link = encap:Ethernet =A0HWaddr a2:d6:e7:30:f3:9e =A0
=A0 =A0 =A0 =A0 =A0 inet = addr:192.168.122.1 =A0Bcast:192.168.122.255 =A0Mask:255.255.255.0
=A0 =A0 =A0 =A0 =A0 UP BROADCAST MULTICAST =A0MTU:1500 =A0Metric:1
=A0 = =A0 =A0 =A0 =A0 RX packets:0 errors:0 dropped:0 overruns:0 frame:0
=A0 = =A0 =A0 =A0 =A0 TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
=A0= =A0 =A0 =A0 =A0 collisions:0 txqueuelen:0
=A0 =A0 =A0 =A0 =A0 RX bytes:0 (0.0 B) =A0TX bytes:0 (0.0 B)

wlan0 = =A0 =A0 Link encap:Ethernet =A0HWaddr 00:26:c7:d3:28:2e =A0
=A0 =A0 =A0 = =A0 =A0 inet addr:192.168.1.104 =A0Bcast:192.168.1.255 =A0Mask:255.255.255.= 0
=A0 =A0 =A0 =A0 =A0 inet6 addr: fe80::226:c7ff:fed3:282e/64 Scope:Link=
=A0 =A0 =A0 =A0 =A0 UP BROADCAST RUNNING MULTICAST =A0MTU:1500 =A0Metric:1<= br>=A0 =A0 =A0 =A0 =A0 RX packets:73574 errors:0 dropped:0 overruns:0 frame= :0
=A0 =A0 =A0 =A0 =A0 TX packets:39730 errors:0 dropped:0 overruns:0 ca= rrier:0
=A0 =A0 =A0 =A0 =A0 collisions:0 txqueuelen:1000
=A0 =A0 =A0 =A0 =A0 RX bytes:73693058 (73.6 MB) =A0TX bytes:4576434 (4.5 MB= )

-

dom0# cat /etc/network/interfaces

auto lo
iface lo inet loopback
auto eth0
iface eth0 inet stat= ic
=A0 =A0address =A0 192.168.0.4
=A0 =A0netmask =A0 255.255.255.0
=A0 =A0network =A0 192.168.0.0
=A0 = =A0broadcast 192.168.0.255
=A0 =A0gateway =A0 192.168.0.1

-

dom0# iptables -L

Chain INPUT (policy ACCEPT)
targe= t =A0 =A0 prot opt source =A0 =A0 =A0 =A0 =A0 =A0 =A0 destination =A0 =A0 = =A0 =A0
ACCEPT =A0 =A0 udp =A0-- =A0anywhere =A0 =A0 =A0 =A0 =A0 =A0 anywhere =A0 = =A0 =A0 =A0 =A0 =A0 udp dpt:domain
ACCEPT =A0 =A0 tcp =A0-- =A0anywhere = =A0 =A0 =A0 =A0 =A0 =A0 anywhere =A0 =A0 =A0 =A0 =A0 =A0 tcp dpt:domain
= ACCEPT =A0 =A0 udp =A0-- =A0anywhere =A0 =A0 =A0 =A0 =A0 =A0 anywhere =A0 = =A0 =A0 =A0 =A0 =A0 udp dpt:bootps
ACCEPT =A0 =A0 tcp =A0-- =A0anywhere =A0 =A0 =A0 =A0 =A0 =A0 anywhere =A0 = =A0 =A0 =A0 =A0 =A0 tcp dpt:bootps

Chain FORWARD (policy ACCEPT)
= target =A0 =A0 prot opt source =A0 =A0 =A0 =A0 =A0 =A0 =A0 destination =A0 = =A0 =A0 =A0
ACCEPT =A0 =A0 all =A0-- =A0anywhere =A0 =A0 =A0 =A0 =A0 = =A0 anywhere =A0 =A0 =A0 =A0 =A0 =A0 PHYSDEV match --physdev-out vif19.0 --= physdev-is-bridged
ACCEPT =A0 =A0 udp =A0-- =A0anywhere =A0 =A0 =A0 =A0 =A0 =A0 anywhere =A0 = =A0 =A0 =A0 =A0 =A0 PHYSDEV match --physdev-in vif19.0 --physdev-is-bridged= udp spt:bootpc dpt:bootps
ACCEPT =A0 =A0 all =A0-- =A0anywhere =A0 =A0 = =A0 =A0 =A0 =A0 anywhere =A0 =A0 =A0 =A0 =A0 =A0 PHYSDEV match --physdev-ou= t vif19.0 --physdev-is-bridged
ACCEPT =A0 =A0 all =A0-- =A0xenroute =A0 =A0 =A0 =A0 =A0 =A0 anywhere =A0 = =A0 =A0 =A0 =A0 =A0 PHYSDEV match --physdev-in vif19.0 --physdev-is-bridged=
ACCEPT =A0 =A0 all =A0-- =A0anywhere =A0 =A0 =A0 =A0 =A0 =A0 192.168.122.0/24 =A0 =A0 state RELATED,ESTABL= ISHED
ACCEPT =A0 =A0 all =A0-- =A0192.168.122= .0/24 =A0 =A0 anywhere =A0 =A0 =A0 =A0 =A0 =A0
ACCEPT =A0 =A0 all = =A0-- =A0anywhere =A0 =A0 =A0 =A0 =A0 =A0 anywhere =A0 =A0 =A0 =A0 =A0 =A0<= br>REJECT =A0 =A0 all =A0-- =A0anywhere =A0 =A0 =A0 =A0 =A0 =A0 anywhere = =A0 =A0 =A0 =A0 =A0 =A0 reject-with icmp-port-unreachable
REJECT =A0 =A0 all =A0-- =A0anywhere =A0 =A0 =A0 =A0 =A0 =A0 anywhere =A0 = =A0 =A0 =A0 =A0 =A0 reject-with icmp-port-unreachable

Chain OUTPUT (= policy ACCEPT)
target =A0 =A0 prot opt source =A0 =A0 =A0 =A0 =A0 =A0 = =A0 destination =A0 =A0 =A0 =A0

-

dom0# iptables -t nat -L
Chain PREROUTING (policy ACCEPT)
target =A0 =A0 prot opt source =A0 = =A0 =A0 =A0 =A0 =A0 =A0 destination =A0 =A0 =A0 =A0

Chain INPUT (po= licy ACCEPT)
target =A0 =A0 prot opt source =A0 =A0 =A0 =A0 =A0 =A0 =A0 = destination =A0 =A0 =A0 =A0

Chain OUTPUT (policy ACCEPT)
target =A0 =A0 prot opt source =A0 =A0 =A0 =A0 =A0 =A0 =A0 destination =A0 = =A0 =A0 =A0

Chain POSTROUTING (policy ACCEPT)
target =A0 =A0 pro= t opt source =A0 =A0 =A0 =A0 =A0 =A0 =A0 destination =A0 =A0 =A0 =A0
MA= SQUERADE =A0tcp =A0-- =A0192.168.122.0/= 24 =A0 =A0!192.168.122.0/24 =A0= =A0 masq ports: 1024-65535
MASQUERADE =A0udp =A0-- =A0192.168.122.= 0/24 =A0 =A0!192.168.122.0/24 = =A0 =A0 masq ports: 1024-65535
MASQUERADE =A0all =A0-- =A0192.168.122.0/24 =A0 =A0!192.168.122.0/24 =A0 =A0
MASQUERADE =A0all =A0-- =A010.0.0.0 =A0 =A0 =A0 =A0 =A0 =A0 anywhere =A0 = =A0 =A0 =A0 =A0 =A0
MASQUERADE =A0all =A0-- =A010.0.0.0 =A0 =A0 =A0 =A0 = =A0 =A0 anywhere =A0 =A0 =A0 =A0 =A0 =A0
MASQUERADE =A0all =A0-- =A0anyw= here =A0 =A0 =A0 =A0 =A0 =A0 anywhere =A0 =A0 =A0 =A0 =A0 =A0
MASQUERADE= =A0all =A0-- =A010.0.0.0 =A0 =A0 =A0 =A0 =A0 =A0 anywhere

-

dom0# sysctl -p

net.ipv4.conf.all.rp_filter= =3D 1
net.ipv4.icmp_echo_ignore_broadcasts =3D 1
net.ipv4.ip_forward= =3D 1
net.ipv4.conf.default.proxy_arp =3D 1
net.ipv4.conf.all.proxy_= arp =3D 1

------------------------

My domU is named xenroute, and it has t= he following settings:

xenroute:~# ifconfig

eth0 =A0 =A0 =A0L= ink encap:Ethernet =A0HWaddr 00:16:3e:1c:4c:d3 =A0
=A0 =A0 =A0 =A0 =A0 i= net addr:10.0.0.1 =A0Bcast:10.255.255.255 =A0Mask:255.0.0.0
=A0 =A0 =A0 =A0 =A0 inet6 addr: fe80::216:3eff:fe1c:4cd3/64 Scope:Link
= =A0 =A0 =A0 =A0 =A0 UP BROADCAST RUNNING MULTICAST =A0MTU:1500 =A0Metric:1<= br>=A0 =A0 =A0 =A0 =A0 RX packets:751 errors:0 dropped:0 overruns:0 frame:0=
=A0 =A0 =A0 =A0 =A0 TX packets:6 errors:0 dropped:0 overruns:0 carrier:= 0
=A0 =A0 =A0 =A0 =A0 collisions:0 txqueuelen:1000
=A0 =A0 =A0 =A0 =A0 RX= bytes:157123 (157.1 KB) =A0TX bytes:468 (468.0 B)
=A0 =A0 =A0 =A0 =A0 I= nterrupt:10

lo =A0 =A0 =A0 =A0Link encap:Local Loopback =A0
=A0 = =A0 =A0 =A0 =A0 inet addr:127.0.0.1 =A0Mask:255.0.0.0
=A0 =A0 =A0 =A0 =A0 inet6 addr: ::1/128 Scope:Host
=A0 =A0 =A0 =A0 =A0 U= P LOOPBACK RUNNING =A0MTU:16436 =A0Metric:1
=A0 =A0 =A0 =A0 =A0 RX packe= ts:0 errors:0 dropped:0 overruns:0 frame:0
=A0 =A0 =A0 =A0 =A0 TX packet= s:0 errors:0 dropped:0 overruns:0 carrier:0
=A0 =A0 =A0 =A0 =A0 collisions:0 txqueuelen:0
=A0 =A0 =A0 =A0 =A0 RX by= tes:0 (0.0 B) =A0TX bytes:0 (0.0 B)
-

xenroute:~# cat /etc/networ= k/interfaces

auto lo
iface lo inet loopback

auto eth0
= iface eth0 inet static
=A0address 10.0.0.1
=A0gateway 192.168.0.1 # 10.0.0.254
=A0netmask 25= 5.255.2552.255

To set up my network I followed t= his tutorial : http://wiki.kartbuilding.net/index.php/Xen_N= etworking#Two-way_Routed_Network_2

Any clue?

Appreciate=A0your attention!

Carol

--f46d042dfd55c0663f04ca3fe4b4-- --===============1698442214203510209== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users --===============1698442214203510209==-- From xen-users-bounces@lists.xen.org Sat Sep 22 01:02:47 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Sat, 22 Sep 2012 01:02:47 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TFE5z-000404-DC; Sat, 22 Sep 2012 01:01:23 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TFE5x-0003eS-Kl for xen-users@lists.xen.org; Sat, 22 Sep 2012 01:01:22 +0000 Received: from [85.158.137.99:55879] by server-11.bemta-3.messagelabs.com id 4C/63-30250-0ED0D505; Sat, 22 Sep 2012 01:01:20 +0000 X-Env-Sender: krouzinh@gmail.com X-Msg-Ref: server-16.tower-217.messagelabs.com!1348275677!18671100!1 X-Originating-IP: [209.85.160.45] X-SpamReason: No, hits=0.4 required=7.0 tests=HTML_30_40,HTML_MESSAGE, ML_RADAR_SPEW_LINKS_14,RCVD_BY_IP,spamassassin: X-StarScan-Received: X-StarScan-Version: 6.6.1.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 15182 invoked from network); 22 Sep 2012 01:01:18 -0000 Received: from mail-pb0-f45.google.com (HELO mail-pb0-f45.google.com) (209.85.160.45) by server-16.tower-217.messagelabs.com with RC4-SHA encrypted SMTP; 22 Sep 2012 01:01:18 -0000 Received: by pbbrp12 with SMTP id rp12so8799720pbb.32 for ; Fri, 21 Sep 2012 18:01:16 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:from:date:message-id:subject:to:content-type; bh=5hP7tEoirbzUJvnbMsEpWZYfsyPsObqUnRMJqSwYK0o=; b=P9rONsZED8xPvUsoZg2+KCfegIgEcLdwh5W3/rDwqA809zAN1oba1sIHfkqRC0Im8P 9E6kuvE+5Sr3aWz8sZ+AKY6uO9NGK8kXRlAm++ibCyz5/OCgKXguQfK0ImsMAYJ5q881 lhuLwIjHFloSSMpGAYpsbEbpGVMNitTQSAVd0QsYwaIA9HZOvKya5TP/3E1nyzGex81P ViT2kPysrSoSjJ6pxmnhqbRnNN4L55Gmzglj0y0fi+CPcnJ3eyXt9H6pC0s3rQLsXoc2 Mh5fgIrBSEDWhA4Ta10tkgUTxvhuy+4xR6XkntH2LJ8y9/BukpqaurhffpcnJGmPRMSU 1Ebw== Received: by 10.66.75.232 with SMTP id f8mr16898318paw.59.1348275676407; Fri, 21 Sep 2012 18:01:16 -0700 (PDT) MIME-Version: 1.0 Received: by 10.66.135.5 with HTTP; Fri, 21 Sep 2012 18:00:36 -0700 (PDT) From: Carol Date: Fri, 21 Sep 2012 22:00:36 -0300 Message-ID: To: xen-users@lists.xen.org Subject: [Xen-users] Route networking xen 4 X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============1698442214203510209==" Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org --===============1698442214203510209== Content-Type: multipart/alternative; boundary=f46d042dfd55c0663f04ca3fe4b4 --f46d042dfd55c0663f04ca3fe4b4 Content-Type: text/plain; charset=ISO-8859-1 Hey guys, I'm facing some issues on route networking. Could someone give me a hand with route networking configuration on xen 4, please? I just wanna make dom0 communicates with domU by pinging each other, but it doesn't seem to get the network working at all. Ive been stucked on this a week or so! Here it goes some configuration on my machine - Ubuntu 12.04: first of all, my xen settings: #cat /etc/xen/xend-config.sxp (logfile /var/log/xen/xend.log) (loglevel DEBUG) (xend-unix-server yes) (network-script network-route) (vif-script vif-route) (dom0-min-mem 196) (total_available_memory 0) (dom0-cpus 0) (vncpasswd '') - #cat /etc/xen/xenroute.cfg bootloader = '/usr/lib/xen-default/bin/pygrub' vcpus = '1' memory = '526' root = '/dev/xvda2 ro' disk = [ 'file:/xen/domains/xenroute/disk.img,xvda2,w', 'file:/xen/domains/xenroute/swap.img,xvda1,w', ] name = 'xenroute' vif = [ 'ip=10.0.0.1,mac=00:16:3E:1C:4C:D3' ] on_poweroff = 'destroy' on_reboot = 'restart' on_crash = 'restart' --------------------------------------------------------------------- Dom0 settings: dom0# ifconfig eth0 Link encap:Ethernet HWaddr bc:ae:c5:9f:50:0c inet addr:192.168.0.4 Bcast:192.168.0.255 Mask:255.255.255.0 UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:0 errors:0 dropped:0 overruns:0 frame:0 TX packets:0 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:0 (0.0 B) TX bytes:0 (0.0 B) Interrupt:50 lo Link encap:Local Loopback inet addr:127.0.0.1 Mask:255.0.0.0 inet6 addr: ::1/128 Scope:Host UP LOOPBACK RUNNING MTU:16436 Metric:1 RX packets:2733 errors:0 dropped:0 overruns:0 frame:0 TX packets:2733 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:295895 (295.8 KB) TX bytes:295895 (295.8 KB) vif19.0 Link encap:Ethernet HWaddr fe:ff:ff:ff:ff:ff inet6 addr: fe80::fcff:ffff:feff:ffff/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:6 errors:0 dropped:0 overruns:0 frame:0 TX packets:709 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:32 RX bytes:384 (384.0 B) TX bytes:162795 (162.7 KB) virbr0 Link encap:Ethernet HWaddr a2:d6:e7:30:f3:9e inet addr:192.168.122.1 Bcast:192.168.122.255 Mask:255.255.255.0 UP BROADCAST MULTICAST MTU:1500 Metric:1 RX packets:0 errors:0 dropped:0 overruns:0 frame:0 TX packets:0 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:0 (0.0 B) TX bytes:0 (0.0 B) wlan0 Link encap:Ethernet HWaddr 00:26:c7:d3:28:2e inet addr:192.168.1.104 Bcast:192.168.1.255 Mask:255.255.255.0 inet6 addr: fe80::226:c7ff:fed3:282e/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:73574 errors:0 dropped:0 overruns:0 frame:0 TX packets:39730 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:73693058 (73.6 MB) TX bytes:4576434 (4.5 MB) - dom0# cat /etc/network/interfaces auto lo iface lo inet loopback auto eth0 iface eth0 inet static address 192.168.0.4 netmask 255.255.255.0 network 192.168.0.0 broadcast 192.168.0.255 gateway 192.168.0.1 - dom0# iptables -L Chain INPUT (policy ACCEPT) target prot opt source destination ACCEPT udp -- anywhere anywhere udp dpt:domain ACCEPT tcp -- anywhere anywhere tcp dpt:domain ACCEPT udp -- anywhere anywhere udp dpt:bootps ACCEPT tcp -- anywhere anywhere tcp dpt:bootps Chain FORWARD (policy ACCEPT) target prot opt source destination ACCEPT all -- anywhere anywhere PHYSDEV match --physdev-out vif19.0 --physdev-is-bridged ACCEPT udp -- anywhere anywhere PHYSDEV match --physdev-in vif19.0 --physdev-is-bridged udp spt:bootpc dpt:bootps ACCEPT all -- anywhere anywhere PHYSDEV match --physdev-out vif19.0 --physdev-is-bridged ACCEPT all -- xenroute anywhere PHYSDEV match --physdev-in vif19.0 --physdev-is-bridged ACCEPT all -- anywhere 192.168.122.0/24 state RELATED,ESTABLISHED ACCEPT all -- 192.168.122.0/24 anywhere ACCEPT all -- anywhere anywhere REJECT all -- anywhere anywhere reject-with icmp-port-unreachable REJECT all -- anywhere anywhere reject-with icmp-port-unreachable Chain OUTPUT (policy ACCEPT) target prot opt source destination - dom0# iptables -t nat -L Chain PREROUTING (policy ACCEPT) target prot opt source destination Chain INPUT (policy ACCEPT) target prot opt source destination Chain OUTPUT (policy ACCEPT) target prot opt source destination Chain POSTROUTING (policy ACCEPT) target prot opt source destination MASQUERADE tcp -- 192.168.122.0/24 !192.168.122.0/24 masq ports: 1024-65535 MASQUERADE udp -- 192.168.122.0/24 !192.168.122.0/24 masq ports: 1024-65535 MASQUERADE all -- 192.168.122.0/24 !192.168.122.0/24 MASQUERADE all -- 10.0.0.0 anywhere MASQUERADE all -- 10.0.0.0 anywhere MASQUERADE all -- anywhere anywhere MASQUERADE all -- 10.0.0.0 anywhere - dom0# sysctl -p net.ipv4.conf.all.rp_filter = 1 net.ipv4.icmp_echo_ignore_broadcasts = 1 net.ipv4.ip_forward = 1 net.ipv4.conf.default.proxy_arp = 1 net.ipv4.conf.all.proxy_arp = 1 ------------------------ My domU is named xenroute, and it has the following settings: xenroute:~# ifconfig eth0 Link encap:Ethernet HWaddr 00:16:3e:1c:4c:d3 inet addr:10.0.0.1 Bcast:10.255.255.255 Mask:255.0.0.0 inet6 addr: fe80::216:3eff:fe1c:4cd3/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:751 errors:0 dropped:0 overruns:0 frame:0 TX packets:6 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:157123 (157.1 KB) TX bytes:468 (468.0 B) Interrupt:10 lo Link encap:Local Loopback inet addr:127.0.0.1 Mask:255.0.0.0 inet6 addr: ::1/128 Scope:Host UP LOOPBACK RUNNING MTU:16436 Metric:1 RX packets:0 errors:0 dropped:0 overruns:0 frame:0 TX packets:0 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:0 (0.0 B) TX bytes:0 (0.0 B) - xenroute:~# cat /etc/network/interfaces auto lo iface lo inet loopback auto eth0 iface eth0 inet static address 10.0.0.1 gateway 192.168.0.1 # 10.0.0.254 netmask 255.255.2552.255 To set up my network I followed this tutorial : http://wiki.kartbuilding.net/index.php/Xen_Networking#Two-way_Routed_Network_2 Any clue? Appreciate your attention! Carol --f46d042dfd55c0663f04ca3fe4b4 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable

Hey guys,

I'm facing some issues on = route networking. Could someone give me a hand with route networking config= uration on xen 4, please?
I just wanna make dom0 communicates with domU = by pinging each other, but it=A0doesn't seem to get the network working= at all. Ive been stucked on this a week or so!

Here it goes some configuration on my machine - Ubuntu 12.0= 4:

first of all, my xen settings:

#ca= t /etc/xen/xend-config.sxp

(logfile /var/log/xen/xend.log)
(loglevel DEBUG)
(xen= d-unix-server yes)
(network-script network-route)
(vif-script vif-rou= te)
(dom0-min-mem 196)
(total_available_memory 0)
(dom0-cpus 0) (vncpasswd '')

-

#cat /etc/xen/xenroute.cfg=A0

bootloader =3D '/usr/lib/xen-default/bin/pygrub'vcpus =A0 =A0 =A0 =3D '1'
memory=A0 =A0 =A0 =3D '526'root=A0 =A0 =A0 =A0 =3D '/dev/xvda2 ro'
disk=A0 =A0 =A0 =A0 = =3D [
=A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 'file:/xen/domains/xenrout= e/disk.img,xvda2,w',
=A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 'file:/xen/domains/xenroute/swap.im= g,xvda1,w',
=A0 =A0 =A0 =A0 =A0 =A0 =A0 ]
name=A0 =A0 =A0 =A0 =3D= 'xenroute'
vif =A0 =A0 =A0 =A0 =3D [ 'ip=3D10.0.0.1,mac=3D0= 0:16:3E:1C:4C:D3' ]
on_poweroff =3D 'destroy'
on_reboot =A0 =3D 'restart'
on_crash=A0 =A0 =3D 'restart'= ;

-----------------------------------------------------------= ----------

Dom0 settings:

dom0# ifconfig

eth0 =A0 =A0 =A0Link encap:Ethernet = =A0HWaddr bc:ae:c5:9f:50:0c =A0
=A0 =A0 =A0 =A0 =A0 inet addr:192.168.0.= 4 =A0Bcast:192.168.0.255 =A0Mask:255.255.255.0
=A0 =A0 =A0 =A0 =A0 UP BR= OADCAST RUNNING MULTICAST =A0MTU:1500 =A0Metric:1
=A0 =A0 =A0 =A0 =A0 RX packets:0 errors:0 dropped:0 overruns:0 frame:0
= =A0 =A0 =A0 =A0 =A0 TX packets:0 errors:0 dropped:0 overruns:0 carrier:0=A0 =A0 =A0 =A0 =A0 collisions:0 txqueuelen:1000
=A0 =A0 =A0 =A0 =A0 RX= bytes:0 (0.0 B) =A0TX bytes:0 (0.0 B)
=A0 =A0 =A0 =A0 =A0 Interrupt:50

lo =A0 =A0 =A0 =A0Link encap:Local = Loopback =A0
=A0 =A0 =A0 =A0 =A0 inet addr:127.0.0.1 =A0Mask:255.0.0.0=A0 =A0 =A0 =A0 =A0 inet6 addr: ::1/128 Scope:Host
=A0 =A0 =A0 =A0 =A0= UP LOOPBACK RUNNING =A0MTU:16436 =A0Metric:1
=A0 =A0 =A0 =A0 =A0 RX pac= kets:2733 errors:0 dropped:0 overruns:0 frame:0
=A0 =A0 =A0 =A0 =A0 TX packets:2733 errors:0 dropped:0 overruns:0 carrier:0=
=A0 =A0 =A0 =A0 =A0 collisions:0 txqueuelen:0
=A0 =A0 =A0 =A0 =A0 R= X bytes:295895 (295.8 KB) =A0TX bytes:295895 (295.8 KB)

vif19.0 =A0 = Link encap:Ethernet =A0HWaddr fe:ff:ff:ff:ff:ff =A0
=A0 =A0 =A0 =A0 =A0 inet6 addr: fe80::fcff:ffff:feff:ffff/64 Scope:Link
= =A0 =A0 =A0 =A0 =A0 UP BROADCAST RUNNING MULTICAST =A0MTU:1500 =A0Metric:1<= br>=A0 =A0 =A0 =A0 =A0 RX packets:6 errors:0 dropped:0 overruns:0 frame:0=A0 =A0 =A0 =A0 =A0 TX packets:709 errors:0 dropped:0 overruns:0 carrier:= 0
=A0 =A0 =A0 =A0 =A0 collisions:0 txqueuelen:32
=A0 =A0 =A0 =A0 =A0 RX b= ytes:384 (384.0 B) =A0TX bytes:162795 (162.7 KB)

virbr0 =A0 =A0Link = encap:Ethernet =A0HWaddr a2:d6:e7:30:f3:9e =A0
=A0 =A0 =A0 =A0 =A0 inet = addr:192.168.122.1 =A0Bcast:192.168.122.255 =A0Mask:255.255.255.0
=A0 =A0 =A0 =A0 =A0 UP BROADCAST MULTICAST =A0MTU:1500 =A0Metric:1
=A0 = =A0 =A0 =A0 =A0 RX packets:0 errors:0 dropped:0 overruns:0 frame:0
=A0 = =A0 =A0 =A0 =A0 TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
=A0= =A0 =A0 =A0 =A0 collisions:0 txqueuelen:0
=A0 =A0 =A0 =A0 =A0 RX bytes:0 (0.0 B) =A0TX bytes:0 (0.0 B)

wlan0 = =A0 =A0 Link encap:Ethernet =A0HWaddr 00:26:c7:d3:28:2e =A0
=A0 =A0 =A0 = =A0 =A0 inet addr:192.168.1.104 =A0Bcast:192.168.1.255 =A0Mask:255.255.255.= 0
=A0 =A0 =A0 =A0 =A0 inet6 addr: fe80::226:c7ff:fed3:282e/64 Scope:Link=
=A0 =A0 =A0 =A0 =A0 UP BROADCAST RUNNING MULTICAST =A0MTU:1500 =A0Metric:1<= br>=A0 =A0 =A0 =A0 =A0 RX packets:73574 errors:0 dropped:0 overruns:0 frame= :0
=A0 =A0 =A0 =A0 =A0 TX packets:39730 errors:0 dropped:0 overruns:0 ca= rrier:0
=A0 =A0 =A0 =A0 =A0 collisions:0 txqueuelen:1000
=A0 =A0 =A0 =A0 =A0 RX bytes:73693058 (73.6 MB) =A0TX bytes:4576434 (4.5 MB= )

-

dom0# cat /etc/network/interfaces

auto lo
iface lo inet loopback
auto eth0
iface eth0 inet stat= ic
=A0 =A0address =A0 192.168.0.4
=A0 =A0netmask =A0 255.255.255.0
=A0 =A0network =A0 192.168.0.0
=A0 = =A0broadcast 192.168.0.255
=A0 =A0gateway =A0 192.168.0.1

-

dom0# iptables -L

Chain INPUT (policy ACCEPT)
targe= t =A0 =A0 prot opt source =A0 =A0 =A0 =A0 =A0 =A0 =A0 destination =A0 =A0 = =A0 =A0
ACCEPT =A0 =A0 udp =A0-- =A0anywhere =A0 =A0 =A0 =A0 =A0 =A0 anywhere =A0 = =A0 =A0 =A0 =A0 =A0 udp dpt:domain
ACCEPT =A0 =A0 tcp =A0-- =A0anywhere = =A0 =A0 =A0 =A0 =A0 =A0 anywhere =A0 =A0 =A0 =A0 =A0 =A0 tcp dpt:domain
= ACCEPT =A0 =A0 udp =A0-- =A0anywhere =A0 =A0 =A0 =A0 =A0 =A0 anywhere =A0 = =A0 =A0 =A0 =A0 =A0 udp dpt:bootps
ACCEPT =A0 =A0 tcp =A0-- =A0anywhere =A0 =A0 =A0 =A0 =A0 =A0 anywhere =A0 = =A0 =A0 =A0 =A0 =A0 tcp dpt:bootps

Chain FORWARD (policy ACCEPT)
= target =A0 =A0 prot opt source =A0 =A0 =A0 =A0 =A0 =A0 =A0 destination =A0 = =A0 =A0 =A0
ACCEPT =A0 =A0 all =A0-- =A0anywhere =A0 =A0 =A0 =A0 =A0 = =A0 anywhere =A0 =A0 =A0 =A0 =A0 =A0 PHYSDEV match --physdev-out vif19.0 --= physdev-is-bridged
ACCEPT =A0 =A0 udp =A0-- =A0anywhere =A0 =A0 =A0 =A0 =A0 =A0 anywhere =A0 = =A0 =A0 =A0 =A0 =A0 PHYSDEV match --physdev-in vif19.0 --physdev-is-bridged= udp spt:bootpc dpt:bootps
ACCEPT =A0 =A0 all =A0-- =A0anywhere =A0 =A0 = =A0 =A0 =A0 =A0 anywhere =A0 =A0 =A0 =A0 =A0 =A0 PHYSDEV match --physdev-ou= t vif19.0 --physdev-is-bridged
ACCEPT =A0 =A0 all =A0-- =A0xenroute =A0 =A0 =A0 =A0 =A0 =A0 anywhere =A0 = =A0 =A0 =A0 =A0 =A0 PHYSDEV match --physdev-in vif19.0 --physdev-is-bridged=
ACCEPT =A0 =A0 all =A0-- =A0anywhere =A0 =A0 =A0 =A0 =A0 =A0 192.168.122.0/24 =A0 =A0 state RELATED,ESTABL= ISHED
ACCEPT =A0 =A0 all =A0-- =A0192.168.122= .0/24 =A0 =A0 anywhere =A0 =A0 =A0 =A0 =A0 =A0
ACCEPT =A0 =A0 all = =A0-- =A0anywhere =A0 =A0 =A0 =A0 =A0 =A0 anywhere =A0 =A0 =A0 =A0 =A0 =A0<= br>REJECT =A0 =A0 all =A0-- =A0anywhere =A0 =A0 =A0 =A0 =A0 =A0 anywhere = =A0 =A0 =A0 =A0 =A0 =A0 reject-with icmp-port-unreachable
REJECT =A0 =A0 all =A0-- =A0anywhere =A0 =A0 =A0 =A0 =A0 =A0 anywhere =A0 = =A0 =A0 =A0 =A0 =A0 reject-with icmp-port-unreachable

Chain OUTPUT (= policy ACCEPT)
target =A0 =A0 prot opt source =A0 =A0 =A0 =A0 =A0 =A0 = =A0 destination =A0 =A0 =A0 =A0

-

dom0# iptables -t nat -L
Chain PREROUTING (policy ACCEPT)
target =A0 =A0 prot opt source =A0 = =A0 =A0 =A0 =A0 =A0 =A0 destination =A0 =A0 =A0 =A0

Chain INPUT (po= licy ACCEPT)
target =A0 =A0 prot opt source =A0 =A0 =A0 =A0 =A0 =A0 =A0 = destination =A0 =A0 =A0 =A0

Chain OUTPUT (policy ACCEPT)
target =A0 =A0 prot opt source =A0 =A0 =A0 =A0 =A0 =A0 =A0 destination =A0 = =A0 =A0 =A0

Chain POSTROUTING (policy ACCEPT)
target =A0 =A0 pro= t opt source =A0 =A0 =A0 =A0 =A0 =A0 =A0 destination =A0 =A0 =A0 =A0
MA= SQUERADE =A0tcp =A0-- =A0192.168.122.0/= 24 =A0 =A0!192.168.122.0/24 =A0= =A0 masq ports: 1024-65535
MASQUERADE =A0udp =A0-- =A0192.168.122.= 0/24 =A0 =A0!192.168.122.0/24 = =A0 =A0 masq ports: 1024-65535
MASQUERADE =A0all =A0-- =A0192.168.122.0/24 =A0 =A0!192.168.122.0/24 =A0 =A0
MASQUERADE =A0all =A0-- =A010.0.0.0 =A0 =A0 =A0 =A0 =A0 =A0 anywhere =A0 = =A0 =A0 =A0 =A0 =A0
MASQUERADE =A0all =A0-- =A010.0.0.0 =A0 =A0 =A0 =A0 = =A0 =A0 anywhere =A0 =A0 =A0 =A0 =A0 =A0
MASQUERADE =A0all =A0-- =A0anyw= here =A0 =A0 =A0 =A0 =A0 =A0 anywhere =A0 =A0 =A0 =A0 =A0 =A0
MASQUERADE= =A0all =A0-- =A010.0.0.0 =A0 =A0 =A0 =A0 =A0 =A0 anywhere

-

dom0# sysctl -p

net.ipv4.conf.all.rp_filter= =3D 1
net.ipv4.icmp_echo_ignore_broadcasts =3D 1
net.ipv4.ip_forward= =3D 1
net.ipv4.conf.default.proxy_arp =3D 1
net.ipv4.conf.all.proxy_= arp =3D 1

------------------------

My domU is named xenroute, and it has t= he following settings:

xenroute:~# ifconfig

eth0 =A0 =A0 =A0L= ink encap:Ethernet =A0HWaddr 00:16:3e:1c:4c:d3 =A0
=A0 =A0 =A0 =A0 =A0 i= net addr:10.0.0.1 =A0Bcast:10.255.255.255 =A0Mask:255.0.0.0
=A0 =A0 =A0 =A0 =A0 inet6 addr: fe80::216:3eff:fe1c:4cd3/64 Scope:Link
= =A0 =A0 =A0 =A0 =A0 UP BROADCAST RUNNING MULTICAST =A0MTU:1500 =A0Metric:1<= br>=A0 =A0 =A0 =A0 =A0 RX packets:751 errors:0 dropped:0 overruns:0 frame:0=
=A0 =A0 =A0 =A0 =A0 TX packets:6 errors:0 dropped:0 overruns:0 carrier:= 0
=A0 =A0 =A0 =A0 =A0 collisions:0 txqueuelen:1000
=A0 =A0 =A0 =A0 =A0 RX= bytes:157123 (157.1 KB) =A0TX bytes:468 (468.0 B)
=A0 =A0 =A0 =A0 =A0 I= nterrupt:10

lo =A0 =A0 =A0 =A0Link encap:Local Loopback =A0
=A0 = =A0 =A0 =A0 =A0 inet addr:127.0.0.1 =A0Mask:255.0.0.0
=A0 =A0 =A0 =A0 =A0 inet6 addr: ::1/128 Scope:Host
=A0 =A0 =A0 =A0 =A0 U= P LOOPBACK RUNNING =A0MTU:16436 =A0Metric:1
=A0 =A0 =A0 =A0 =A0 RX packe= ts:0 errors:0 dropped:0 overruns:0 frame:0
=A0 =A0 =A0 =A0 =A0 TX packet= s:0 errors:0 dropped:0 overruns:0 carrier:0
=A0 =A0 =A0 =A0 =A0 collisions:0 txqueuelen:0
=A0 =A0 =A0 =A0 =A0 RX by= tes:0 (0.0 B) =A0TX bytes:0 (0.0 B)
-

xenroute:~# cat /etc/networ= k/interfaces

auto lo
iface lo inet loopback

auto eth0
= iface eth0 inet static
=A0address 10.0.0.1
=A0gateway 192.168.0.1 # 10.0.0.254
=A0netmask 25= 5.255.2552.255

To set up my network I followed t= his tutorial : http://wiki.kartbuilding.net/index.php/Xen_N= etworking#Two-way_Routed_Network_2

Any clue?

Appreciate=A0your attention!

Carol

--f46d042dfd55c0663f04ca3fe4b4-- --===============1698442214203510209== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users --===============1698442214203510209==-- From xen-users-bounces@lists.xen.org Sat Sep 22 04:29:27 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Sat, 22 Sep 2012 04:29:27 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TFHJp-0004Z7-0h; Sat, 22 Sep 2012 04:27:53 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TFHJm-0004Z2-Ol for xen-users@lists.xen.org; Sat, 22 Sep 2012 04:27:50 +0000 Received: from [85.158.143.35:36060] by server-3.bemta-4.messagelabs.com id 4E/FA-10986-64E3D505; Sat, 22 Sep 2012 04:27:50 +0000 X-Env-Sender: myrdhn@gmail.com X-Msg-Ref: server-13.tower-21.messagelabs.com!1348288068!18007164!1 X-Originating-IP: [209.85.216.45] X-SpamReason: No, hits=0.8 required=7.0 tests=BODY_RANDOM_LONG, ML_RADAR_SPEW_LINKS_14,RCVD_BY_IP,spamassassin: X-StarScan-Received: X-StarScan-Version: 6.6.1.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 16205 invoked from network); 22 Sep 2012 04:27:49 -0000 Received: from mail-qa0-f45.google.com (HELO mail-qa0-f45.google.com) (209.85.216.45) by server-13.tower-21.messagelabs.com with RC4-SHA encrypted SMTP; 22 Sep 2012 04:27:49 -0000 Received: by qadc10 with SMTP id c10so1999706qad.11 for ; Fri, 21 Sep 2012 21:27:48 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=from:to:cc:references:in-reply-to:subject:date:message-id :mime-version:content-type:content-transfer-encoding:x-mailer :thread-index:content-language; bh=qoEkoncI/Ffnd+WjQ0JTzisvCn5nOckq4Ban0yciu7M=; b=zl8a9Z5cvgiq2ff9n3fSzHipdvTdxl9fCjtOT39uXa9bOaPjKgjqgnV6/AkGU7JttN KnRw/FEZ41rAXlj2J9zwBMDEHgJ484mcgD9wFhNb/pGtV1tAgsMQo7A6xCg1j42N4AAA esnXb4o691jmN15f6bF9pu8SoBq916mokJ3p/KPlnfULIw5xgDdVkgEMateV6jSsS6qk zrrwsMMOu6Ju3+qBr9JYRqgdnSD2z7CsadJLsC531o09NltFY4UbtmmKjp9Tmrv6kZ8r fddP+GMT/edgGPpzSNAsUpng2A1ZpIHyymXINvjXzosrArYrlniNoFQ/+hTjzec1FqRi 6kVg== Received: by 10.224.31.202 with SMTP id z10mr16903477qac.86.1348288068138; Fri, 21 Sep 2012 21:27:48 -0700 (PDT) Received: from Belldandy (c-76-119-253-48.hsd1.ma.comcast.net. [76.119.253.48]) by mx.google.com with ESMTPS id d11sm15449610qaj.18.2012.09.21.21.27.47 (version=TLSv1/SSLv3 cipher=OTHER); Fri, 21 Sep 2012 21:27:47 -0700 (PDT) From: "Marc Tousignant" To: "'Volker Klasen'" , "'Andrew Bobulsky'" References: <002401cd97b5$5b49f260$11ddd720$@gmail.com> <505C8F8D.6000007@unitedklasens.de> In-Reply-To: <505C8F8D.6000007@unitedklasens.de> Date: Sat, 22 Sep 2012 00:27:52 -0400 Message-ID: <009001cd987a$a22777a0$e67666e0$@gmail.com> MIME-Version: 1.0 X-Mailer: Microsoft Outlook 14.0 Thread-Index: AQFWNXDrCGkumsC8LJ/AaHSr1Ri4dQJHcDYcmHJOByA= Content-Language: en-us Cc: xen-users@lists.xen.org Subject: Re: [Xen-users] Need help with passing through USB hub or devices X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org Volker, 3.5 as well. TheOldMan ~ # uname -r 3.5.3-gentoo Andrew, TheOldMan ~ # lspci 00:00.0 Host bridge: NVIDIA Corporation C55 Host Bridge (rev a2) 00:00.1 RAM memory: NVIDIA Corporation C55 Memory Controller (rev a1) 00:00.2 RAM memory: NVIDIA Corporation C55 Memory Controller (rev a1) 00:00.3 RAM memory: NVIDIA Corporation C55 Memory Controller (rev a1) 00:00.4 RAM memory: NVIDIA Corporation C55 Memory Controller (rev a1) 00:00.5 RAM memory: NVIDIA Corporation C55 Memory Controller (rev a2) 00:00.6 RAM memory: NVIDIA Corporation C55 Memory Controller (rev a1) 00:00.7 RAM memory: NVIDIA Corporation C55 Memory Controller (rev a1) 00:01.0 RAM memory: NVIDIA Corporation C55 Memory Controller (rev a1) 00:01.1 RAM memory: NVIDIA Corporation C55 Memory Controller (rev a1) 00:01.2 RAM memory: NVIDIA Corporation C55 Memory Controller (rev a1) 00:01.3 RAM memory: NVIDIA Corporation C55 Memory Controller (rev a1) 00:01.4 RAM memory: NVIDIA Corporation C55 Memory Controller (rev a1) 00:01.5 RAM memory: NVIDIA Corporation C55 Memory Controller (rev a1) 00:01.6 RAM memory: NVIDIA Corporation C55 Memory Controller (rev a1) 00:02.0 RAM memory: NVIDIA Corporation C55 Memory Controller (rev a1) 00:02.1 RAM memory: NVIDIA Corporation C55 Memory Controller (rev a1) 00:02.2 RAM memory: NVIDIA Corporation C55 Memory Controller (rev a1) 00:03.0 PCI bridge: NVIDIA Corporation C55 PCI Express bridge (rev a1) 00:09.0 RAM memory: NVIDIA Corporation MCP55 Memory Controller (rev a1) 00:0a.0 ISA bridge: NVIDIA Corporation MCP55 LPC Bridge (rev a2) 00:0a.1 SMBus: NVIDIA Corporation MCP55 SMBus (rev a2) 00:0b.0 USB controller: NVIDIA Corporation MCP55 USB Controller (rev a1) 00:0b.1 USB controller: NVIDIA Corporation MCP55 USB Controller (rev a2) 00:0d.0 IDE interface: NVIDIA Corporation MCP55 IDE (rev a1) 00:0e.0 IDE interface: NVIDIA Corporation MCP55 SATA Controller (rev a2) 00:0e.1 IDE interface: NVIDIA Corporation MCP55 SATA Controller (rev a2) 00:0e.2 IDE interface: NVIDIA Corporation MCP55 SATA Controller (rev a2) 00:0f.0 PCI bridge: NVIDIA Corporation MCP55 PCI bridge (rev a2) 00:0f.1 Audio device: NVIDIA Corporation MCP55 High Definition Audio (rev a2) 00:11.0 Bridge: NVIDIA Corporation MCP55 Ethernet (rev a2) 00:12.0 Bridge: NVIDIA Corporation MCP55 Ethernet (rev a2) 01:00.0 VGA compatible controller: NVIDIA Corporation G80 [GeForce 8800 GTX] (rev a2) 02:07.0 FireWire (IEEE 1394): Texas Instruments TSB43AB22A IEEE-1394a-2000 Controller (PHY/Link) [iOHCI-Lynx] I did attempt to pass through both 00:0b.0 and 00:0b.1 at the same time, There was no change in behavior. Marc _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Sat Sep 22 04:29:27 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Sat, 22 Sep 2012 04:29:27 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TFHJp-0004Z7-0h; Sat, 22 Sep 2012 04:27:53 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TFHJm-0004Z2-Ol for xen-users@lists.xen.org; Sat, 22 Sep 2012 04:27:50 +0000 Received: from [85.158.143.35:36060] by server-3.bemta-4.messagelabs.com id 4E/FA-10986-64E3D505; Sat, 22 Sep 2012 04:27:50 +0000 X-Env-Sender: myrdhn@gmail.com X-Msg-Ref: server-13.tower-21.messagelabs.com!1348288068!18007164!1 X-Originating-IP: [209.85.216.45] X-SpamReason: No, hits=0.8 required=7.0 tests=BODY_RANDOM_LONG, ML_RADAR_SPEW_LINKS_14,RCVD_BY_IP,spamassassin: X-StarScan-Received: X-StarScan-Version: 6.6.1.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 16205 invoked from network); 22 Sep 2012 04:27:49 -0000 Received: from mail-qa0-f45.google.com (HELO mail-qa0-f45.google.com) (209.85.216.45) by server-13.tower-21.messagelabs.com with RC4-SHA encrypted SMTP; 22 Sep 2012 04:27:49 -0000 Received: by qadc10 with SMTP id c10so1999706qad.11 for ; Fri, 21 Sep 2012 21:27:48 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=from:to:cc:references:in-reply-to:subject:date:message-id :mime-version:content-type:content-transfer-encoding:x-mailer :thread-index:content-language; bh=qoEkoncI/Ffnd+WjQ0JTzisvCn5nOckq4Ban0yciu7M=; b=zl8a9Z5cvgiq2ff9n3fSzHipdvTdxl9fCjtOT39uXa9bOaPjKgjqgnV6/AkGU7JttN KnRw/FEZ41rAXlj2J9zwBMDEHgJ484mcgD9wFhNb/pGtV1tAgsMQo7A6xCg1j42N4AAA esnXb4o691jmN15f6bF9pu8SoBq916mokJ3p/KPlnfULIw5xgDdVkgEMateV6jSsS6qk zrrwsMMOu6Ju3+qBr9JYRqgdnSD2z7CsadJLsC531o09NltFY4UbtmmKjp9Tmrv6kZ8r fddP+GMT/edgGPpzSNAsUpng2A1ZpIHyymXINvjXzosrArYrlniNoFQ/+hTjzec1FqRi 6kVg== Received: by 10.224.31.202 with SMTP id z10mr16903477qac.86.1348288068138; Fri, 21 Sep 2012 21:27:48 -0700 (PDT) Received: from Belldandy (c-76-119-253-48.hsd1.ma.comcast.net. [76.119.253.48]) by mx.google.com with ESMTPS id d11sm15449610qaj.18.2012.09.21.21.27.47 (version=TLSv1/SSLv3 cipher=OTHER); Fri, 21 Sep 2012 21:27:47 -0700 (PDT) From: "Marc Tousignant" To: "'Volker Klasen'" , "'Andrew Bobulsky'" References: <002401cd97b5$5b49f260$11ddd720$@gmail.com> <505C8F8D.6000007@unitedklasens.de> In-Reply-To: <505C8F8D.6000007@unitedklasens.de> Date: Sat, 22 Sep 2012 00:27:52 -0400 Message-ID: <009001cd987a$a22777a0$e67666e0$@gmail.com> MIME-Version: 1.0 X-Mailer: Microsoft Outlook 14.0 Thread-Index: AQFWNXDrCGkumsC8LJ/AaHSr1Ri4dQJHcDYcmHJOByA= Content-Language: en-us Cc: xen-users@lists.xen.org Subject: Re: [Xen-users] Need help with passing through USB hub or devices X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org Volker, 3.5 as well. TheOldMan ~ # uname -r 3.5.3-gentoo Andrew, TheOldMan ~ # lspci 00:00.0 Host bridge: NVIDIA Corporation C55 Host Bridge (rev a2) 00:00.1 RAM memory: NVIDIA Corporation C55 Memory Controller (rev a1) 00:00.2 RAM memory: NVIDIA Corporation C55 Memory Controller (rev a1) 00:00.3 RAM memory: NVIDIA Corporation C55 Memory Controller (rev a1) 00:00.4 RAM memory: NVIDIA Corporation C55 Memory Controller (rev a1) 00:00.5 RAM memory: NVIDIA Corporation C55 Memory Controller (rev a2) 00:00.6 RAM memory: NVIDIA Corporation C55 Memory Controller (rev a1) 00:00.7 RAM memory: NVIDIA Corporation C55 Memory Controller (rev a1) 00:01.0 RAM memory: NVIDIA Corporation C55 Memory Controller (rev a1) 00:01.1 RAM memory: NVIDIA Corporation C55 Memory Controller (rev a1) 00:01.2 RAM memory: NVIDIA Corporation C55 Memory Controller (rev a1) 00:01.3 RAM memory: NVIDIA Corporation C55 Memory Controller (rev a1) 00:01.4 RAM memory: NVIDIA Corporation C55 Memory Controller (rev a1) 00:01.5 RAM memory: NVIDIA Corporation C55 Memory Controller (rev a1) 00:01.6 RAM memory: NVIDIA Corporation C55 Memory Controller (rev a1) 00:02.0 RAM memory: NVIDIA Corporation C55 Memory Controller (rev a1) 00:02.1 RAM memory: NVIDIA Corporation C55 Memory Controller (rev a1) 00:02.2 RAM memory: NVIDIA Corporation C55 Memory Controller (rev a1) 00:03.0 PCI bridge: NVIDIA Corporation C55 PCI Express bridge (rev a1) 00:09.0 RAM memory: NVIDIA Corporation MCP55 Memory Controller (rev a1) 00:0a.0 ISA bridge: NVIDIA Corporation MCP55 LPC Bridge (rev a2) 00:0a.1 SMBus: NVIDIA Corporation MCP55 SMBus (rev a2) 00:0b.0 USB controller: NVIDIA Corporation MCP55 USB Controller (rev a1) 00:0b.1 USB controller: NVIDIA Corporation MCP55 USB Controller (rev a2) 00:0d.0 IDE interface: NVIDIA Corporation MCP55 IDE (rev a1) 00:0e.0 IDE interface: NVIDIA Corporation MCP55 SATA Controller (rev a2) 00:0e.1 IDE interface: NVIDIA Corporation MCP55 SATA Controller (rev a2) 00:0e.2 IDE interface: NVIDIA Corporation MCP55 SATA Controller (rev a2) 00:0f.0 PCI bridge: NVIDIA Corporation MCP55 PCI bridge (rev a2) 00:0f.1 Audio device: NVIDIA Corporation MCP55 High Definition Audio (rev a2) 00:11.0 Bridge: NVIDIA Corporation MCP55 Ethernet (rev a2) 00:12.0 Bridge: NVIDIA Corporation MCP55 Ethernet (rev a2) 01:00.0 VGA compatible controller: NVIDIA Corporation G80 [GeForce 8800 GTX] (rev a2) 02:07.0 FireWire (IEEE 1394): Texas Instruments TSB43AB22A IEEE-1394a-2000 Controller (PHY/Link) [iOHCI-Lynx] I did attempt to pass through both 00:0b.0 and 00:0b.1 at the same time, There was no change in behavior. Marc _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Sat Sep 22 06:20:13 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Sat, 22 Sep 2012 06:20:13 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TFJ3E-0005dQ-62; Sat, 22 Sep 2012 06:18:52 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TFJ3B-0005dL-R8 for xen-users@lists.xen.org; Sat, 22 Sep 2012 06:18:50 +0000 Received: from [85.158.143.35:47461] by server-2.bemta-4.messagelabs.com id 06/5E-06610-8485D505; Sat, 22 Sep 2012 06:18:48 +0000 X-Env-Sender: nd@syndicat.com X-Msg-Ref: server-14.tower-21.messagelabs.com!1348294728!15893808!1 X-Originating-IP: [62.146.89.62] X-SpamReason: No, hits=0.0 required=7.0 tests= X-StarScan-Received: X-StarScan-Version: 6.6.1.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 26812 invoked from network); 22 Sep 2012 06:18:48 -0000 Received: from ffm-dr1.syndicat.com (HELO ffm-dr1.syndicat.com) (62.146.89.62) by server-14.tower-21.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 22 Sep 2012 06:18:48 -0000 Received: from localhost.syndicat.com ([127.0.0.1] helo=localhost) by ffm-dr1.syndicat.com with esmtp (Syndicat.com PostHamster 8.1.4.76) (envelope-from ) id 1TFJ39-0001nd-NA; Sat, 22 Sep 2012 08:18:47 +0200 X-Virus-Scanned: amavisd-new at syndicat.com Received: from ffm-dr1.syndicat.com ([127.0.0.1]) by localhost (ffm-dr1.syndicat.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id UXcsapOAFcIq; Sat, 22 Sep 2012 08:18:47 +0200 (CEST) Received: from p5dc3f371.dip.t-dialin.net ([93.195.243.113] helo=htc.syndicat) by ffm-dr1.syndicat.com with esmtpsa (TLSv1:RC4-MD5:128) (Syndicat.com PostHamster 8.1.4.76) (envelope-from ) id 1TFJ39-0001aJ-4f; Sat, 22 Sep 2012 08:18:47 +0200 User-Agent: K-9 Mail for Android In-Reply-To: References: MIME-Version: 1.0 From: "Niels Dettenbach (Syndicat IT&Internet)" Date: Sat, 22 Sep 2012 08:18:28 +0200 To: Carol ,xen-users@lists.xen.org Message-ID: <1d317091-00a0-4959-8254-d75a832f77de@email.android.com> Subject: Re: [Xen-users] Route networking xen 4 X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 Carol schrieb: >auto lo >iface lo inet loopback > >auto eth0 >iface eth0 inet static > address 10.0.0.1 > gateway 192.168.0.1 # 10.0.0.254 > netmask 255.255.2552.255 Typo?!? And: - - why do you have a bridge on Dom0 if you want to do routing? - - your vif seems not configured on Dom0 yet - - check your other netmasks hth Cheers, Niels. - -- Niels Dettenbach Syndicat IT&Internet http://www.syndicat.com -----BEGIN PGP SIGNATURE----- Version: APG v1.0.8 iIEEAREIAEEFAlBdWDM6HE5pZWxzIERldHRlbmJhY2ggKFN5bmRpY2F0IElUJklu dGVybmV0KSA8bmRAc3luZGljYXQuY29tPgAKCRBU3ERlZRyiDTT3AJ9qqxNLEQgl JjguD7mB8zEwNV1DdwCfcH5tvXeemzpXO3CN+5XRiQG3jJ4= =z2c8 -----END PGP SIGNATURE----- _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Sat Sep 22 06:20:13 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Sat, 22 Sep 2012 06:20:13 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TFJ3E-0005dQ-62; Sat, 22 Sep 2012 06:18:52 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TFJ3B-0005dL-R8 for xen-users@lists.xen.org; Sat, 22 Sep 2012 06:18:50 +0000 Received: from [85.158.143.35:47461] by server-2.bemta-4.messagelabs.com id 06/5E-06610-8485D505; Sat, 22 Sep 2012 06:18:48 +0000 X-Env-Sender: nd@syndicat.com X-Msg-Ref: server-14.tower-21.messagelabs.com!1348294728!15893808!1 X-Originating-IP: [62.146.89.62] X-SpamReason: No, hits=0.0 required=7.0 tests= X-StarScan-Received: X-StarScan-Version: 6.6.1.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 26812 invoked from network); 22 Sep 2012 06:18:48 -0000 Received: from ffm-dr1.syndicat.com (HELO ffm-dr1.syndicat.com) (62.146.89.62) by server-14.tower-21.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 22 Sep 2012 06:18:48 -0000 Received: from localhost.syndicat.com ([127.0.0.1] helo=localhost) by ffm-dr1.syndicat.com with esmtp (Syndicat.com PostHamster 8.1.4.76) (envelope-from ) id 1TFJ39-0001nd-NA; Sat, 22 Sep 2012 08:18:47 +0200 X-Virus-Scanned: amavisd-new at syndicat.com Received: from ffm-dr1.syndicat.com ([127.0.0.1]) by localhost (ffm-dr1.syndicat.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id UXcsapOAFcIq; Sat, 22 Sep 2012 08:18:47 +0200 (CEST) Received: from p5dc3f371.dip.t-dialin.net ([93.195.243.113] helo=htc.syndicat) by ffm-dr1.syndicat.com with esmtpsa (TLSv1:RC4-MD5:128) (Syndicat.com PostHamster 8.1.4.76) (envelope-from ) id 1TFJ39-0001aJ-4f; Sat, 22 Sep 2012 08:18:47 +0200 User-Agent: K-9 Mail for Android In-Reply-To: References: MIME-Version: 1.0 From: "Niels Dettenbach (Syndicat IT&Internet)" Date: Sat, 22 Sep 2012 08:18:28 +0200 To: Carol ,xen-users@lists.xen.org Message-ID: <1d317091-00a0-4959-8254-d75a832f77de@email.android.com> Subject: Re: [Xen-users] Route networking xen 4 X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 Carol schrieb: >auto lo >iface lo inet loopback > >auto eth0 >iface eth0 inet static > address 10.0.0.1 > gateway 192.168.0.1 # 10.0.0.254 > netmask 255.255.2552.255 Typo?!? And: - - why do you have a bridge on Dom0 if you want to do routing? - - your vif seems not configured on Dom0 yet - - check your other netmasks hth Cheers, Niels. - -- Niels Dettenbach Syndicat IT&Internet http://www.syndicat.com -----BEGIN PGP SIGNATURE----- Version: APG v1.0.8 iIEEAREIAEEFAlBdWDM6HE5pZWxzIERldHRlbmJhY2ggKFN5bmRpY2F0IElUJklu dGVybmV0KSA8bmRAc3luZGljYXQuY29tPgAKCRBU3ERlZRyiDTT3AJ9qqxNLEQgl JjguD7mB8zEwNV1DdwCfcH5tvXeemzpXO3CN+5XRiQG3jJ4= =z2c8 -----END PGP SIGNATURE----- _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Sat Sep 22 14:07:12 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Sat, 22 Sep 2012 14:07:12 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TFQL6-0000ks-Ch; Sat, 22 Sep 2012 14:05:48 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TFP8U-00008Z-QE for xen-users@lists.xen.org; Sat, 22 Sep 2012 12:48:42 +0000 Received: from [85.158.143.99:40197] by server-2.bemta-4.messagelabs.com id 45/E1-06610-9A3BD505; Sat, 22 Sep 2012 12:48:41 +0000 X-Env-Sender: lukas@laukamp.me X-Msg-Ref: server-11.tower-216.messagelabs.com!1348318120!23838407!1 X-Originating-IP: [5.9.218.245] X-SpamReason: No, hits=1.3 required=7.0 tests=BODY_RANDOM_LONG, HTML_40_50,HTML_MESSAGE,RCVD_ILLEGAL_IP X-StarScan-Received: X-StarScan-Version: 6.6.1.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 27819 invoked from network); 22 Sep 2012 12:48:41 -0000 Received: from mailer0.lippux.de (HELO mailer0.lippux.de) (5.9.218.245) by server-11.tower-216.messagelabs.com with SMTP; 22 Sep 2012 12:48:41 -0000 Received: from localhost (localhost [127.0.0.1]) by mailer0.lippux.de (Postfix) with ESMTP id 622DC422871 for ; Sat, 22 Sep 2012 14:48:40 +0200 (CEST) X-Virus-Scanned: Debian amavisd-new at mailer0.lippux.de Received: from mailer0.lippux.de ([127.0.0.1]) by localhost (mailer0.lippux.de [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id w0-kmZqoL39a for ; Sat, 22 Sep 2012 14:48:36 +0200 (CEST) Received: from [127.0.0.1] (unknown [5.9.218.242]) (Authenticated sender: lukas@laukamp.me) by mailer0.lippux.de (Postfix) with ESMTPSA id BDE0542286C for ; Sat, 22 Sep 2012 14:48:35 +0200 (CEST) Message-ID: <505DB39B.9060605@laukamp.me> Date: Sat, 22 Sep 2012 14:48:27 +0200 From: Lukas Laukamp User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:15.0) Gecko/20120907 Thunderbird/15.0.1 MIME-Version: 1.0 To: xen-users@lists.xen.org References: <505C3BA7.5010105@laukamp.me> In-Reply-To: <505C3BA7.5010105@laukamp.me> X-Mailman-Approved-At: Sat, 22 Sep 2012 14:05:46 +0000 Subject: Re: [Xen-users] [SOLVED] Xen 4.2 (backported packages) can't load Dom0 (Kernel 2.6.32-5-xen-amd64) X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============6283842352846981637==" Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org This is a multi-part message in MIME format. --===============6283842352846981637== Content-Type: multipart/alternative; boundary="------------020803000204020803030404" This is a multi-part message in MIME format. --------------020803000204020803030404 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Am 21.09.2012 12:04, schrieb Lukas Laukamp: > Hey all, > > I have a problem with Xen 4.2 on Debian Squeeze with Kernel > 2.6.32-5-xen-amd64. I rebuilded the source packages from Debian > experimental trunk on Squeeze and installed them. Also I installed the > Kernel 2.6.32-5-xen-amd64 from the Debian Squeeze trunk. Now it looks > like that Xen can't load the Dom0. After registering netback strange > modprobe errors appear. In the attachment is a screenshot of the errors. > > I also build Xen directly from source without packaging it and it > works fine with the 2.6.32-5-xen-amd64 kernel. So I think it's a > problem which only appears in the packages with the Debian patches. > > Does someone have an idea how to solve this issue? > > Best Regards > > > > > _______________________________________________ > Xen-users mailing list > Xen-users@lists.xen.org > http://lists.xen.org/xen-users Hey all, I could solve the problem with a Serial console, it was related to a device of the testsystem which wasn't handeled correct. Best Regards --------------020803000204020803030404 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit
Am 21.09.2012 12:04, schrieb Lukas Laukamp:
Hey all,

I have a problem with Xen 4.2 on Debian Squeeze with Kernel 2.6.32-5-xen-amd64. I rebuilded the source packages from Debian experimental trunk on Squeeze and installed them. Also I installed the Kernel 2.6.32-5-xen-amd64 from the Debian Squeeze trunk. Now it looks like that Xen can't load the Dom0. After registering netback strange modprobe errors appear. In the attachment is a screenshot of the errors.

I also build Xen directly from source without packaging it and it works fine with the 2.6.32-5-xen-amd64 kernel. So I think it's a problem which only appears in the packages with the Debian patches.

Does someone have an idea how to solve this issue?

Best Regards 




_______________________________________________
Xen-users mailing list
Xen-users@lists.xen.org
http://lists.xen.org/xen-users

Hey all,

I could solve the problem with a Serial console, it was related to a device of the testsystem which wasn't handeled correct.

Best Regards
--------------020803000204020803030404-- --===============6283842352846981637== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users --===============6283842352846981637==-- From xen-users-bounces@lists.xen.org Sat Sep 22 14:07:12 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Sat, 22 Sep 2012 14:07:12 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TFQL6-0000ks-Ch; Sat, 22 Sep 2012 14:05:48 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TFP8U-00008Z-QE for xen-users@lists.xen.org; Sat, 22 Sep 2012 12:48:42 +0000 Received: from [85.158.143.99:40197] by server-2.bemta-4.messagelabs.com id 45/E1-06610-9A3BD505; Sat, 22 Sep 2012 12:48:41 +0000 X-Env-Sender: lukas@laukamp.me X-Msg-Ref: server-11.tower-216.messagelabs.com!1348318120!23838407!1 X-Originating-IP: [5.9.218.245] X-SpamReason: No, hits=1.3 required=7.0 tests=BODY_RANDOM_LONG, HTML_40_50,HTML_MESSAGE,RCVD_ILLEGAL_IP X-StarScan-Received: X-StarScan-Version: 6.6.1.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 27819 invoked from network); 22 Sep 2012 12:48:41 -0000 Received: from mailer0.lippux.de (HELO mailer0.lippux.de) (5.9.218.245) by server-11.tower-216.messagelabs.com with SMTP; 22 Sep 2012 12:48:41 -0000 Received: from localhost (localhost [127.0.0.1]) by mailer0.lippux.de (Postfix) with ESMTP id 622DC422871 for ; Sat, 22 Sep 2012 14:48:40 +0200 (CEST) X-Virus-Scanned: Debian amavisd-new at mailer0.lippux.de Received: from mailer0.lippux.de ([127.0.0.1]) by localhost (mailer0.lippux.de [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id w0-kmZqoL39a for ; Sat, 22 Sep 2012 14:48:36 +0200 (CEST) Received: from [127.0.0.1] (unknown [5.9.218.242]) (Authenticated sender: lukas@laukamp.me) by mailer0.lippux.de (Postfix) with ESMTPSA id BDE0542286C for ; Sat, 22 Sep 2012 14:48:35 +0200 (CEST) Message-ID: <505DB39B.9060605@laukamp.me> Date: Sat, 22 Sep 2012 14:48:27 +0200 From: Lukas Laukamp User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:15.0) Gecko/20120907 Thunderbird/15.0.1 MIME-Version: 1.0 To: xen-users@lists.xen.org References: <505C3BA7.5010105@laukamp.me> In-Reply-To: <505C3BA7.5010105@laukamp.me> X-Mailman-Approved-At: Sat, 22 Sep 2012 14:05:46 +0000 Subject: Re: [Xen-users] [SOLVED] Xen 4.2 (backported packages) can't load Dom0 (Kernel 2.6.32-5-xen-amd64) X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============6283842352846981637==" Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org This is a multi-part message in MIME format. --===============6283842352846981637== Content-Type: multipart/alternative; boundary="------------020803000204020803030404" This is a multi-part message in MIME format. --------------020803000204020803030404 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Am 21.09.2012 12:04, schrieb Lukas Laukamp: > Hey all, > > I have a problem with Xen 4.2 on Debian Squeeze with Kernel > 2.6.32-5-xen-amd64. I rebuilded the source packages from Debian > experimental trunk on Squeeze and installed them. Also I installed the > Kernel 2.6.32-5-xen-amd64 from the Debian Squeeze trunk. Now it looks > like that Xen can't load the Dom0. After registering netback strange > modprobe errors appear. In the attachment is a screenshot of the errors. > > I also build Xen directly from source without packaging it and it > works fine with the 2.6.32-5-xen-amd64 kernel. So I think it's a > problem which only appears in the packages with the Debian patches. > > Does someone have an idea how to solve this issue? > > Best Regards > > > > > _______________________________________________ > Xen-users mailing list > Xen-users@lists.xen.org > http://lists.xen.org/xen-users Hey all, I could solve the problem with a Serial console, it was related to a device of the testsystem which wasn't handeled correct. Best Regards --------------020803000204020803030404 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit
Am 21.09.2012 12:04, schrieb Lukas Laukamp:
Hey all,

I have a problem with Xen 4.2 on Debian Squeeze with Kernel 2.6.32-5-xen-amd64. I rebuilded the source packages from Debian experimental trunk on Squeeze and installed them. Also I installed the Kernel 2.6.32-5-xen-amd64 from the Debian Squeeze trunk. Now it looks like that Xen can't load the Dom0. After registering netback strange modprobe errors appear. In the attachment is a screenshot of the errors.

I also build Xen directly from source without packaging it and it works fine with the 2.6.32-5-xen-amd64 kernel. So I think it's a problem which only appears in the packages with the Debian patches.

Does someone have an idea how to solve this issue?

Best Regards 




_______________________________________________
Xen-users mailing list
Xen-users@lists.xen.org
http://lists.xen.org/xen-users

Hey all,

I could solve the problem with a Serial console, it was related to a device of the testsystem which wasn't handeled correct.

Best Regards
--------------020803000204020803030404-- --===============6283842352846981637== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users --===============6283842352846981637==-- From xen-users-bounces@lists.xen.org Sat Sep 22 14:07:25 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Sat, 22 Sep 2012 14:07:25 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TFQLT-0000lb-1c; Sat, 22 Sep 2012 14:06:11 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TFQLR-0000lU-OI for xen-users@lists.xen.org; Sat, 22 Sep 2012 14:06:09 +0000 Received: from [85.158.143.35:2849] by server-1.bemta-4.messagelabs.com id 5A/32-05684-1D5CD505; Sat, 22 Sep 2012 14:06:09 +0000 X-Env-Sender: krouzinh@gmail.com X-Msg-Ref: server-16.tower-21.messagelabs.com!1348322764!13214501!1 X-Originating-IP: [209.85.160.45] X-SpamReason: No, hits=0.4 required=7.0 tests=HTML_50_60,HTML_MESSAGE, ML_RADAR_SPEW_LINKS_14,RCVD_BY_IP,spamassassin: X-StarScan-Received: X-StarScan-Version: 6.6.1.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 23050 invoked from network); 22 Sep 2012 14:06:06 -0000 Received: from mail-pb0-f45.google.com (HELO mail-pb0-f45.google.com) (209.85.160.45) by server-16.tower-21.messagelabs.com with RC4-SHA encrypted SMTP; 22 Sep 2012 14:06:06 -0000 Received: by pbbrp12 with SMTP id rp12so9596620pbb.32 for ; Sat, 22 Sep 2012 07:06:04 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type; bh=FXoxOw7PriqISICLKJ1TuNJkp3RJ8wAK+9zMriwjc2w=; b=wyKYUgLgnYW1aB1EtHbSzX19DTgAPiy5156rQlHs9u6EcH55fWk9eGDymqDcvBTXnM IS2iuumSA+8idNLJjbtrs4U/4M1TIP+MIQSxt+i+SdZloY27rD+jYXpsC2R2D30MbJIB cfTG1JbziuDA+BPwDbG6wzaWLMJxwhWSfyqGVLIq8hRAmfnW8Jd2dQ/6DLOZSSTCbuqj dtvGJF5uUKruEfgxMDiikVIHvbcVoNQ9AKIKX6cnBifToyFgxaX4BzmLn0ktCuEMV1bj rOqPYqqKDAYdvOt/8H+mgy14Kpr3fV9J+fnfxSxR43eEBv4tghatqooOpTwHIIGQPCiF /3HQ== Received: by 10.66.77.170 with SMTP id t10mr20528023paw.0.1348322764179; Sat, 22 Sep 2012 07:06:04 -0700 (PDT) MIME-Version: 1.0 Received: by 10.66.135.5 with HTTP; Sat, 22 Sep 2012 07:05:24 -0700 (PDT) In-Reply-To: <1d317091-00a0-4959-8254-d75a832f77de@email.android.com> References: <1d317091-00a0-4959-8254-d75a832f77de@email.android.com> From: Carol Date: Sat, 22 Sep 2012 11:05:24 -0300 Message-ID: To: "Niels Dettenbach (Syndicat IT&Internet)" Cc: xen-users@lists.xen.org Subject: Re: [Xen-users] Route networking xen 4 X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============3721583603660423672==" Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org --===============3721583603660423672== Content-Type: multipart/alternative; boundary=f46d042f9de866c9b204ca4adb97 --f46d042f9de866c9b204ca4adb97 Content-Type: text/plain; charset=ISO-8859-1 Thanks for your reply! I have never worked with network and virtualization before, that's why I am kinda lost trying to get this thing working. >auto lo > >iface lo inet loopback > > > >auto eth0 > >iface eth0 inet static > > address 10.0.0.1 > > gateway 192.168.0.1 # 10.0.0.254 > > netmask 255.255.2552.255 > > Typo?!? > I'm sorry, didn't get why it would be typo? And: > - - why do you have a bridge on Dom0 if you want to do routing? Maybe because I tried to run a bridge networking before trying route? How would I remove this bridge set up? > - - your vif seems not configured on Dom0 yet > How do I configure vif devices? > - - check your other netmasks > which ones? Sorry for my ignorance - Carol --f46d042f9de866c9b204ca4adb97 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Thanks for your reply!

I have never worked with network and vi= rtualization before, that's why I am kinda lost trying to get this thin= g working.


>auto lo
>iface lo inet loopback
>
>auto eth0
>iface eth0 inet static
> address 10.0.0.1
> gateway 192.168.0.1 # 10.0.0.254
> netmask 255.255.2552.255

Typo?!?

I'm sorry, didn't= get why it would be typo?=A0

And:
- - why do you have a bridge on Dom0 if you want to do routing?

Maybe because I tried to run a bridge networking befor= e trying route? How would I remove this bridge set up?
=A0
- - your vif seems not configured on Dom0 yet

How do I configure vif devices?
=A0
- - check your other netmasks

which one= s?

Sorry for my ignorance

- Carol
--f46d042f9de866c9b204ca4adb97-- --===============3721583603660423672== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users --===============3721583603660423672==-- From xen-users-bounces@lists.xen.org Sat Sep 22 14:07:25 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Sat, 22 Sep 2012 14:07:25 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TFQLT-0000lb-1c; Sat, 22 Sep 2012 14:06:11 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TFQLR-0000lU-OI for xen-users@lists.xen.org; Sat, 22 Sep 2012 14:06:09 +0000 Received: from [85.158.143.35:2849] by server-1.bemta-4.messagelabs.com id 5A/32-05684-1D5CD505; Sat, 22 Sep 2012 14:06:09 +0000 X-Env-Sender: krouzinh@gmail.com X-Msg-Ref: server-16.tower-21.messagelabs.com!1348322764!13214501!1 X-Originating-IP: [209.85.160.45] X-SpamReason: No, hits=0.4 required=7.0 tests=HTML_50_60,HTML_MESSAGE, ML_RADAR_SPEW_LINKS_14,RCVD_BY_IP,spamassassin: X-StarScan-Received: X-StarScan-Version: 6.6.1.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 23050 invoked from network); 22 Sep 2012 14:06:06 -0000 Received: from mail-pb0-f45.google.com (HELO mail-pb0-f45.google.com) (209.85.160.45) by server-16.tower-21.messagelabs.com with RC4-SHA encrypted SMTP; 22 Sep 2012 14:06:06 -0000 Received: by pbbrp12 with SMTP id rp12so9596620pbb.32 for ; Sat, 22 Sep 2012 07:06:04 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type; bh=FXoxOw7PriqISICLKJ1TuNJkp3RJ8wAK+9zMriwjc2w=; b=wyKYUgLgnYW1aB1EtHbSzX19DTgAPiy5156rQlHs9u6EcH55fWk9eGDymqDcvBTXnM IS2iuumSA+8idNLJjbtrs4U/4M1TIP+MIQSxt+i+SdZloY27rD+jYXpsC2R2D30MbJIB cfTG1JbziuDA+BPwDbG6wzaWLMJxwhWSfyqGVLIq8hRAmfnW8Jd2dQ/6DLOZSSTCbuqj dtvGJF5uUKruEfgxMDiikVIHvbcVoNQ9AKIKX6cnBifToyFgxaX4BzmLn0ktCuEMV1bj rOqPYqqKDAYdvOt/8H+mgy14Kpr3fV9J+fnfxSxR43eEBv4tghatqooOpTwHIIGQPCiF /3HQ== Received: by 10.66.77.170 with SMTP id t10mr20528023paw.0.1348322764179; Sat, 22 Sep 2012 07:06:04 -0700 (PDT) MIME-Version: 1.0 Received: by 10.66.135.5 with HTTP; Sat, 22 Sep 2012 07:05:24 -0700 (PDT) In-Reply-To: <1d317091-00a0-4959-8254-d75a832f77de@email.android.com> References: <1d317091-00a0-4959-8254-d75a832f77de@email.android.com> From: Carol Date: Sat, 22 Sep 2012 11:05:24 -0300 Message-ID: To: "Niels Dettenbach (Syndicat IT&Internet)" Cc: xen-users@lists.xen.org Subject: Re: [Xen-users] Route networking xen 4 X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============3721583603660423672==" Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org --===============3721583603660423672== Content-Type: multipart/alternative; boundary=f46d042f9de866c9b204ca4adb97 --f46d042f9de866c9b204ca4adb97 Content-Type: text/plain; charset=ISO-8859-1 Thanks for your reply! I have never worked with network and virtualization before, that's why I am kinda lost trying to get this thing working. >auto lo > >iface lo inet loopback > > > >auto eth0 > >iface eth0 inet static > > address 10.0.0.1 > > gateway 192.168.0.1 # 10.0.0.254 > > netmask 255.255.2552.255 > > Typo?!? > I'm sorry, didn't get why it would be typo? And: > - - why do you have a bridge on Dom0 if you want to do routing? Maybe because I tried to run a bridge networking before trying route? How would I remove this bridge set up? > - - your vif seems not configured on Dom0 yet > How do I configure vif devices? > - - check your other netmasks > which ones? Sorry for my ignorance - Carol --f46d042f9de866c9b204ca4adb97 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Thanks for your reply!

I have never worked with network and vi= rtualization before, that's why I am kinda lost trying to get this thin= g working.


>auto lo
>iface lo inet loopback
>
>auto eth0
>iface eth0 inet static
> address 10.0.0.1
> gateway 192.168.0.1 # 10.0.0.254
> netmask 255.255.2552.255

Typo?!?

I'm sorry, didn't= get why it would be typo?=A0

And:
- - why do you have a bridge on Dom0 if you want to do routing?

Maybe because I tried to run a bridge networking befor= e trying route? How would I remove this bridge set up?
=A0
- - your vif seems not configured on Dom0 yet

How do I configure vif devices?
=A0
- - check your other netmasks

which one= s?

Sorry for my ignorance

- Carol
--f46d042f9de866c9b204ca4adb97-- --===============3721583603660423672== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users --===============3721583603660423672==-- From xen-users-bounces@lists.xen.org Sat Sep 22 16:02:31 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Sat, 22 Sep 2012 16:02:31 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TFS8n-0002Ms-Fd; Sat, 22 Sep 2012 16:01:13 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TFS8l-0002Mn-Q6 for xen-users@lists.xen.org; Sat, 22 Sep 2012 16:01:12 +0000 Received: from [85.158.143.35:35274] by server-2.bemta-4.messagelabs.com id A7/E4-06610-7C0ED505; Sat, 22 Sep 2012 16:01:11 +0000 X-Env-Sender: ajlill@ajlc.waterloo.on.ca X-Msg-Ref: server-9.tower-21.messagelabs.com!1348329665!4681861!1 X-Originating-IP: [64.7.134.25] X-SpamReason: No, hits=0.0 required=7.0 tests= X-StarScan-Received: X-StarScan-Version: 6.6.1.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 29103 invoked from network); 22 Sep 2012 16:01:07 -0000 Received: from ajlill.sentex.ca (HELO mail.ajlc.waterloo.on.ca) (64.7.134.25) by server-9.tower-21.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 22 Sep 2012 16:01:07 -0000 Received: from [10.19.61.4] (gloria.ajlc.waterloo.on.ca [10.19.61.4]) (authenticated bits=0) by mail.ajlc.waterloo.on.ca (8.14.3/8.14.3/Debian-9.4) with ESMTP id q8MG0sfU023915 for ; Sat, 22 Sep 2012 12:00:55 -0400 Message-ID: <505DE0B6.6070602@ajlc.waterloo.on.ca> Date: Sat, 22 Sep 2012 12:00:54 -0400 From: Tony Lill User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:15.0) Gecko/20120827 Thunderbird/15.0 MIME-Version: 1.0 To: xen-users@lists.xen.org References: <003601cd9430$a381db70$ea859250$@gmail.com> <1347818899.25803.75.camel@dagon.hellion.org.uk> <004e01cd9446$b7636b20$262a4160$@gmail.com> <5056603D.8030007@ajlc.waterloo.on.ca> <006701cd9477$0d045820$270d0860$@gmail.com> <505686EA.9060801@ajlc.waterloo.on.ca> <2fe38c876c5367c3121ef41b12e0b8a5.squirrel@www.antarean.org> In-Reply-To: <2fe38c876c5367c3121ef41b12e0b8a5.squirrel@www.antarean.org> X-Enigmail-Version: 1.4.4 X-Spam-Status: No, score=-101.3 required=5.0 tests=ALL_TRUSTED,AWL, RP_MATCHES_RCVD,USER_IN_WHITELIST autolearn=ham version=3.3.1 X-Spam-Checker-Version: SpamAssassin 3.3.1 (2010-03-16) on mail.ajlc.waterloo.on.ca Subject: Re: [Xen-users] Setting up XEN domU causes RAID5 to fail? X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 09/17/2012 02:22 AM, J. Roeleveld wrote: > > On Mon, September 17, 2012 4:11 am, Tony Lill wrote: >> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 >> >> When I tried to upgrade my xen systems to a pvops xen/linux >> combo, I found that high disk I/O would cause disk errors and >> caused disks to be thrown out of the raid and all sorts of other >> badness. High of course, is a relative term. For one of my >> boxes, copying a large file was enough, on another, it needed >> something like running backups on several VMs simultaneously or >> trying to start my VM's while rebuilding the raid. >> >> FWIW, I went back to Xen 3.4.4 and the SLES1 xenlinux kernel and >> they've been rock solid. > > This could be related to Xen version, but can also be related to > the use of desktop-drives in a RAID-configuration. Linux Software > raid is more tolerant than hardware raid, but it still doesn't > like it if a disk dissappears/fails/acts up and will then kick it > out. > > I'm surprised there are no messages in the logs as I have always > seen at least a message from the raid-stack when a disk was thrown > out. On the one box I got tons of messages, the other I got a error message once, and the second time it just hung, after which I stopped trying. > Are those drives SMART-compliant? If yes, try running a self-test > on those drives to see if there are any detectable problems. > > Other possible cause: The PSU can't handle the load of all the > drives and the CPU going full speed. > > You could also try to do some heavy load on those drives by > simultaneously copying "/dev/zero" to each of the drives. The drives are smart compliant and healthy and have worked fine for months/years, same as the PSU. The only difference is the XEN technology. pvops, both self compiled and from the squeeze distro, were totally unstable. On one box I could trash it just by copying a large file. The xenlinux system is rock solid. - -- Tony Lill, OCT, Tony.Lill@AJLC.Waterloo.ON.CA President, A. J. Lill Consultants (519) 650 0660 539 Grand Valley Dr., Cambridge, Ont. N3H 2S2 (519) 241 2461 - --------------- http://www.ajlc.waterloo.on.ca/ ---------------- -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.10 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://www.enigmail.net/ iEYEARECAAYFAlBd4LYACgkQGS8yZq1uvxDvFACeNmeHQZ0HocXmYOBQ+IyMCdyv 3REAn2Mp6co7f1GOYl+1KETkVbYL93D5 =/uBk -----END PGP SIGNATURE----- _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Sat Sep 22 16:02:31 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Sat, 22 Sep 2012 16:02:31 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TFS8n-0002Ms-Fd; Sat, 22 Sep 2012 16:01:13 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TFS8l-0002Mn-Q6 for xen-users@lists.xen.org; Sat, 22 Sep 2012 16:01:12 +0000 Received: from [85.158.143.35:35274] by server-2.bemta-4.messagelabs.com id A7/E4-06610-7C0ED505; Sat, 22 Sep 2012 16:01:11 +0000 X-Env-Sender: ajlill@ajlc.waterloo.on.ca X-Msg-Ref: server-9.tower-21.messagelabs.com!1348329665!4681861!1 X-Originating-IP: [64.7.134.25] X-SpamReason: No, hits=0.0 required=7.0 tests= X-StarScan-Received: X-StarScan-Version: 6.6.1.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 29103 invoked from network); 22 Sep 2012 16:01:07 -0000 Received: from ajlill.sentex.ca (HELO mail.ajlc.waterloo.on.ca) (64.7.134.25) by server-9.tower-21.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 22 Sep 2012 16:01:07 -0000 Received: from [10.19.61.4] (gloria.ajlc.waterloo.on.ca [10.19.61.4]) (authenticated bits=0) by mail.ajlc.waterloo.on.ca (8.14.3/8.14.3/Debian-9.4) with ESMTP id q8MG0sfU023915 for ; Sat, 22 Sep 2012 12:00:55 -0400 Message-ID: <505DE0B6.6070602@ajlc.waterloo.on.ca> Date: Sat, 22 Sep 2012 12:00:54 -0400 From: Tony Lill User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:15.0) Gecko/20120827 Thunderbird/15.0 MIME-Version: 1.0 To: xen-users@lists.xen.org References: <003601cd9430$a381db70$ea859250$@gmail.com> <1347818899.25803.75.camel@dagon.hellion.org.uk> <004e01cd9446$b7636b20$262a4160$@gmail.com> <5056603D.8030007@ajlc.waterloo.on.ca> <006701cd9477$0d045820$270d0860$@gmail.com> <505686EA.9060801@ajlc.waterloo.on.ca> <2fe38c876c5367c3121ef41b12e0b8a5.squirrel@www.antarean.org> In-Reply-To: <2fe38c876c5367c3121ef41b12e0b8a5.squirrel@www.antarean.org> X-Enigmail-Version: 1.4.4 X-Spam-Status: No, score=-101.3 required=5.0 tests=ALL_TRUSTED,AWL, RP_MATCHES_RCVD,USER_IN_WHITELIST autolearn=ham version=3.3.1 X-Spam-Checker-Version: SpamAssassin 3.3.1 (2010-03-16) on mail.ajlc.waterloo.on.ca Subject: Re: [Xen-users] Setting up XEN domU causes RAID5 to fail? X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 09/17/2012 02:22 AM, J. Roeleveld wrote: > > On Mon, September 17, 2012 4:11 am, Tony Lill wrote: >> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 >> >> When I tried to upgrade my xen systems to a pvops xen/linux >> combo, I found that high disk I/O would cause disk errors and >> caused disks to be thrown out of the raid and all sorts of other >> badness. High of course, is a relative term. For one of my >> boxes, copying a large file was enough, on another, it needed >> something like running backups on several VMs simultaneously or >> trying to start my VM's while rebuilding the raid. >> >> FWIW, I went back to Xen 3.4.4 and the SLES1 xenlinux kernel and >> they've been rock solid. > > This could be related to Xen version, but can also be related to > the use of desktop-drives in a RAID-configuration. Linux Software > raid is more tolerant than hardware raid, but it still doesn't > like it if a disk dissappears/fails/acts up and will then kick it > out. > > I'm surprised there are no messages in the logs as I have always > seen at least a message from the raid-stack when a disk was thrown > out. On the one box I got tons of messages, the other I got a error message once, and the second time it just hung, after which I stopped trying. > Are those drives SMART-compliant? If yes, try running a self-test > on those drives to see if there are any detectable problems. > > Other possible cause: The PSU can't handle the load of all the > drives and the CPU going full speed. > > You could also try to do some heavy load on those drives by > simultaneously copying "/dev/zero" to each of the drives. The drives are smart compliant and healthy and have worked fine for months/years, same as the PSU. The only difference is the XEN technology. pvops, both self compiled and from the squeeze distro, were totally unstable. On one box I could trash it just by copying a large file. The xenlinux system is rock solid. - -- Tony Lill, OCT, Tony.Lill@AJLC.Waterloo.ON.CA President, A. J. Lill Consultants (519) 650 0660 539 Grand Valley Dr., Cambridge, Ont. N3H 2S2 (519) 241 2461 - --------------- http://www.ajlc.waterloo.on.ca/ ---------------- -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.10 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://www.enigmail.net/ iEYEARECAAYFAlBd4LYACgkQGS8yZq1uvxDvFACeNmeHQZ0HocXmYOBQ+IyMCdyv 3REAn2Mp6co7f1GOYl+1KETkVbYL93D5 =/uBk -----END PGP SIGNATURE----- _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Sat Sep 22 18:27:09 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Sat, 22 Sep 2012 18:27:09 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TFUON-0003kS-Ei; Sat, 22 Sep 2012 18:25:27 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TFUOL-0003kN-Hj for xen-users@lists.xen.org; Sat, 22 Sep 2012 18:25:25 +0000 Received: from [85.158.139.83:54281] by server-16.bemta-5.messagelabs.com id DD/4D-11718-4920E505; Sat, 22 Sep 2012 18:25:24 +0000 X-Env-Sender: linux@thehobsons.co.uk X-Msg-Ref: server-13.tower-182.messagelabs.com!1348338323!31137877!1 X-Originating-IP: [81.174.135.208] X-SpamReason: No, hits=0.0 required=7.0 tests= X-StarScan-Received: X-StarScan-Version: 6.6.1.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 7664 invoked from network); 22 Sep 2012 18:25:23 -0000 Received: from patsy.thehobsons.co.uk (HELO patsy.thehobsons.co.uk) (81.174.135.208) by server-13.tower-182.messagelabs.com with SMTP; 22 Sep 2012 18:25:23 -0000 Received: from localhost (localhost [127.0.0.1]) by patsy.thehobsons.co.uk (Postfix) with ESMTP id 4499110401A for ; Sat, 22 Sep 2012 19:25:21 +0100 (BST) Received: from patsy.thehobsons.co.uk ([127.0.0.1]) by localhost (patsy.thehobsons.co.uk [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id C-XHPcFCw5pq for ; Sat, 22 Sep 2012 19:25:21 +0100 (BST) Received: from simon.thehobsons.co.uk (simons-macbookpro.thehobsons.co.uk [192.168.0.202]) by patsy.thehobsons.co.uk (Postfix) with ESMTP id BF5DA29F0C for ; Sat, 22 Sep 2012 19:25:20 +0100 (BST) Mime-Version: 1.0 Message-Id: In-Reply-To: References: Date: Sat, 22 Sep 2012 19:25:15 +0100 To: xen-users@lists.xen.org From: Simon Hobson Subject: Re: [Xen-users] Route networking xen 4 X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset="us-ascii"; Format="flowed" Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org Carol wrote: >I'm facing some issues on route networking. >(network-script network-route) The Xen network-scripts are deprecated in favour of host OS supplied config options which are now generally more powerful, flexible, and reliable. >#cat /etc/xen/xenroute.cfg > >bootloader = '/usr/lib/xen-default/bin/pygrub' >vcpus = '1' >memory = '526' >root = '/dev/xvda2 ro' >disk = [ > 'file:/xen/domains/xenroute/disk.img,xvda2,w', > 'file:/xen/domains/xenroute/swap.img,xvda1,w', > ] >name = 'xenroute' >vif = [ 'ip=10.0.0.1,mac=00:16:3E:1C:4C:D3' ] >on_poweroff = 'destroy' >on_reboot = 'restart' >on_crash = 'restart' I personally add "bridge=..." to VIF specifications - but then I'm normally working on systems with multiple bridges. >dom0# cat /etc/network/interfaces > >auto lo >iface lo inet loopback >auto eth0 >iface eth0 inet static > address 192.168.0.4 > netmask 255.255.255.0 > network 192.168.0.0 > broadcast 192.168.0.255 > gateway 192.168.0.1 Network and broadcast are normally not required - the system will work them out. It's no problem to specify them, but it does add scope for errors. I would define the bridge here : auto br0 iface br0 inet static address 10.0.0.254 netmask 255.255.255.0 bridge_ports none This creates a bridge called br0 with no physical interfaces attached - this is correct, it's only used for the DomUs to communicate. You can use any name you like - on my systems they tend to be things like brext, brint, and so on - which makes it easier to keep track of what connects to what. You then need to configure the NAt and any filters between eth0 and br0. To Dom0, br0 is "just another network interface" in most respects. Without enabling forwarding and NAT, Dom0 and DomU will be able to communicate, but DomU will not have external access. >xenroute:~# cat /etc/network/interfaces > >auto lo >iface lo inet loopback > >auto eth0 >iface eth0 inet static > address 10.0.0.1 > gateway 192.168.0.1 # 10.0.0.254 > netmask 255.255.2552.255 The netmask here is invalid (even ignoring the typo), it should probably be 255.255.255.0. Also gateway should be just one value - 10.0.0.254. 192.168.0.1 is not valid on the subnet, and is not directly accessible anyway. >To set up my network I followed this tutorial : >http://wiki.kartbuilding.net/index.php/Xen_Networking#Two-way_Routed_Network_2 That's ancient - last updated over 5 years ago - things have moved on since. That is the big problem following "random" articles off the net. -- Simon Hobson Visit http://www.magpiesnestpublishing.co.uk/ for books by acclaimed author Gladys Hobson. Novels - poetry - short stories - ideal as Christmas stocking fillers. Some available as e-books. _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Sat Sep 22 18:27:09 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Sat, 22 Sep 2012 18:27:09 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TFUON-0003kS-Ei; Sat, 22 Sep 2012 18:25:27 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TFUOL-0003kN-Hj for xen-users@lists.xen.org; Sat, 22 Sep 2012 18:25:25 +0000 Received: from [85.158.139.83:54281] by server-16.bemta-5.messagelabs.com id DD/4D-11718-4920E505; Sat, 22 Sep 2012 18:25:24 +0000 X-Env-Sender: linux@thehobsons.co.uk X-Msg-Ref: server-13.tower-182.messagelabs.com!1348338323!31137877!1 X-Originating-IP: [81.174.135.208] X-SpamReason: No, hits=0.0 required=7.0 tests= X-StarScan-Received: X-StarScan-Version: 6.6.1.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 7664 invoked from network); 22 Sep 2012 18:25:23 -0000 Received: from patsy.thehobsons.co.uk (HELO patsy.thehobsons.co.uk) (81.174.135.208) by server-13.tower-182.messagelabs.com with SMTP; 22 Sep 2012 18:25:23 -0000 Received: from localhost (localhost [127.0.0.1]) by patsy.thehobsons.co.uk (Postfix) with ESMTP id 4499110401A for ; Sat, 22 Sep 2012 19:25:21 +0100 (BST) Received: from patsy.thehobsons.co.uk ([127.0.0.1]) by localhost (patsy.thehobsons.co.uk [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id C-XHPcFCw5pq for ; Sat, 22 Sep 2012 19:25:21 +0100 (BST) Received: from simon.thehobsons.co.uk (simons-macbookpro.thehobsons.co.uk [192.168.0.202]) by patsy.thehobsons.co.uk (Postfix) with ESMTP id BF5DA29F0C for ; Sat, 22 Sep 2012 19:25:20 +0100 (BST) Mime-Version: 1.0 Message-Id: In-Reply-To: References: Date: Sat, 22 Sep 2012 19:25:15 +0100 To: xen-users@lists.xen.org From: Simon Hobson Subject: Re: [Xen-users] Route networking xen 4 X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset="us-ascii"; Format="flowed" Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org Carol wrote: >I'm facing some issues on route networking. >(network-script network-route) The Xen network-scripts are deprecated in favour of host OS supplied config options which are now generally more powerful, flexible, and reliable. >#cat /etc/xen/xenroute.cfg > >bootloader = '/usr/lib/xen-default/bin/pygrub' >vcpus = '1' >memory = '526' >root = '/dev/xvda2 ro' >disk = [ > 'file:/xen/domains/xenroute/disk.img,xvda2,w', > 'file:/xen/domains/xenroute/swap.img,xvda1,w', > ] >name = 'xenroute' >vif = [ 'ip=10.0.0.1,mac=00:16:3E:1C:4C:D3' ] >on_poweroff = 'destroy' >on_reboot = 'restart' >on_crash = 'restart' I personally add "bridge=..." to VIF specifications - but then I'm normally working on systems with multiple bridges. >dom0# cat /etc/network/interfaces > >auto lo >iface lo inet loopback >auto eth0 >iface eth0 inet static > address 192.168.0.4 > netmask 255.255.255.0 > network 192.168.0.0 > broadcast 192.168.0.255 > gateway 192.168.0.1 Network and broadcast are normally not required - the system will work them out. It's no problem to specify them, but it does add scope for errors. I would define the bridge here : auto br0 iface br0 inet static address 10.0.0.254 netmask 255.255.255.0 bridge_ports none This creates a bridge called br0 with no physical interfaces attached - this is correct, it's only used for the DomUs to communicate. You can use any name you like - on my systems they tend to be things like brext, brint, and so on - which makes it easier to keep track of what connects to what. You then need to configure the NAt and any filters between eth0 and br0. To Dom0, br0 is "just another network interface" in most respects. Without enabling forwarding and NAT, Dom0 and DomU will be able to communicate, but DomU will not have external access. >xenroute:~# cat /etc/network/interfaces > >auto lo >iface lo inet loopback > >auto eth0 >iface eth0 inet static > address 10.0.0.1 > gateway 192.168.0.1 # 10.0.0.254 > netmask 255.255.2552.255 The netmask here is invalid (even ignoring the typo), it should probably be 255.255.255.0. Also gateway should be just one value - 10.0.0.254. 192.168.0.1 is not valid on the subnet, and is not directly accessible anyway. >To set up my network I followed this tutorial : >http://wiki.kartbuilding.net/index.php/Xen_Networking#Two-way_Routed_Network_2 That's ancient - last updated over 5 years ago - things have moved on since. That is the big problem following "random" articles off the net. -- Simon Hobson Visit http://www.magpiesnestpublishing.co.uk/ for books by acclaimed author Gladys Hobson. Novels - poetry - short stories - ideal as Christmas stocking fillers. Some available as e-books. _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Sat Sep 22 20:51:52 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Sat, 22 Sep 2012 20:51:52 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TFWeu-00052X-Iz; Sat, 22 Sep 2012 20:50:40 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TFWet-00052S-5M for xen-users@lists.xen.org; Sat, 22 Sep 2012 20:50:39 +0000 Received: from [85.158.139.83:6624] by server-14.bemta-5.messagelabs.com id 43/1D-13084-E942E505; Sat, 22 Sep 2012 20:50:38 +0000 X-Env-Sender: jaceksburghardt@gmail.com X-Msg-Ref: server-4.tower-182.messagelabs.com!1348347036!27153048!1 X-Originating-IP: [209.85.216.169] X-SpamReason: No, hits=1.5 required=7.0 tests=HTML_00_10,HTML_MESSAGE, ML_RADAR_SPEW_LINKS_14,RCVD_BY_IP,spamassassin: X-StarScan-Received: X-StarScan-Version: 6.6.1.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 2678 invoked from network); 22 Sep 2012 20:50:37 -0000 Received: from mail-qc0-f169.google.com (HELO mail-qc0-f169.google.com) (209.85.216.169) by server-4.tower-182.messagelabs.com with RC4-SHA encrypted SMTP; 22 Sep 2012 20:50:37 -0000 Received: by qcsd16 with SMTP id d16so3497120qcs.28 for ; Sat, 22 Sep 2012 13:50:36 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:date:message-id:subject:from:to:content-type; bh=7ei4EadfqItwf5YnFxUjT7jmw35lR1hMOMuIkUFM4xY=; b=O8kLG3MUbJGBenjad7hvaLlDR7S2eZgyI+wQDKzG3Q4PGQ09bkyi95ess1ZmoyS9Oz qTEpT62rYWOES8uWrWI4FWwD4RD0Q1cXkK+uYt88kB9lXWKJmgeXqEdHsixljBR/xsGe SYyiKUJdS0wL+TudEMDXzmglgQWahLU4OIeyu+cg1YBnrxHZTQa6nR4WVNxlTFWmV8Hc QvF/T/lp6ARzBBPgAG8fz/1S3CJmtrcXnhQSY8Rj9b6H3AAkiwlyBn/2DMSnEidu6AFd suemHxbeuW65p0uyqsV7Xo8AdLnGZ9pNKRwAwGKeFpXgW/NlIJogk5nFaPDz3dkH89OV wPqQ== MIME-Version: 1.0 Received: by 10.224.213.198 with SMTP id gx6mr22018628qab.9.1348347036270; Sat, 22 Sep 2012 13:50:36 -0700 (PDT) Received: by 10.49.118.101 with HTTP; Sat, 22 Sep 2012 13:50:36 -0700 (PDT) Date: Sat, 22 Sep 2012 14:50:36 -0600 Message-ID: From: jacek burghardt To: xen-users Subject: [Xen-users] file location X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============0579599251128515518==" Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org --===============0579599251128515518== Content-Type: multipart/alternative; boundary=20cf30050d90217fdd04ca5082b6 --20cf30050d90217fdd04ca5082b6 Content-Type: text/plain; charset=ISO-8859-1 I wonder if anyone knows what creates /var/run/xend/xen-api.sock and whole directory /var/run/xend. I am running arch linux so I need to patch xen-4.2 to use /run/daemons> --20cf30050d90217fdd04ca5082b6 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable I wonder if anyone knows what creates=A0 /var/run/xend/xen-api.sock and who= le directory /var/run/xend. I am running arch linux so I need to patch xen-= 4.2 to use /run/daemons>
--20cf30050d90217fdd04ca5082b6-- --===============0579599251128515518== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users --===============0579599251128515518==-- From xen-users-bounces@lists.xen.org Sat Sep 22 20:51:52 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Sat, 22 Sep 2012 20:51:52 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TFWeu-00052X-Iz; Sat, 22 Sep 2012 20:50:40 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TFWet-00052S-5M for xen-users@lists.xen.org; Sat, 22 Sep 2012 20:50:39 +0000 Received: from [85.158.139.83:6624] by server-14.bemta-5.messagelabs.com id 43/1D-13084-E942E505; Sat, 22 Sep 2012 20:50:38 +0000 X-Env-Sender: jaceksburghardt@gmail.com X-Msg-Ref: server-4.tower-182.messagelabs.com!1348347036!27153048!1 X-Originating-IP: [209.85.216.169] X-SpamReason: No, hits=1.5 required=7.0 tests=HTML_00_10,HTML_MESSAGE, ML_RADAR_SPEW_LINKS_14,RCVD_BY_IP,spamassassin: X-StarScan-Received: X-StarScan-Version: 6.6.1.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 2678 invoked from network); 22 Sep 2012 20:50:37 -0000 Received: from mail-qc0-f169.google.com (HELO mail-qc0-f169.google.com) (209.85.216.169) by server-4.tower-182.messagelabs.com with RC4-SHA encrypted SMTP; 22 Sep 2012 20:50:37 -0000 Received: by qcsd16 with SMTP id d16so3497120qcs.28 for ; Sat, 22 Sep 2012 13:50:36 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:date:message-id:subject:from:to:content-type; bh=7ei4EadfqItwf5YnFxUjT7jmw35lR1hMOMuIkUFM4xY=; b=O8kLG3MUbJGBenjad7hvaLlDR7S2eZgyI+wQDKzG3Q4PGQ09bkyi95ess1ZmoyS9Oz qTEpT62rYWOES8uWrWI4FWwD4RD0Q1cXkK+uYt88kB9lXWKJmgeXqEdHsixljBR/xsGe SYyiKUJdS0wL+TudEMDXzmglgQWahLU4OIeyu+cg1YBnrxHZTQa6nR4WVNxlTFWmV8Hc QvF/T/lp6ARzBBPgAG8fz/1S3CJmtrcXnhQSY8Rj9b6H3AAkiwlyBn/2DMSnEidu6AFd suemHxbeuW65p0uyqsV7Xo8AdLnGZ9pNKRwAwGKeFpXgW/NlIJogk5nFaPDz3dkH89OV wPqQ== MIME-Version: 1.0 Received: by 10.224.213.198 with SMTP id gx6mr22018628qab.9.1348347036270; Sat, 22 Sep 2012 13:50:36 -0700 (PDT) Received: by 10.49.118.101 with HTTP; Sat, 22 Sep 2012 13:50:36 -0700 (PDT) Date: Sat, 22 Sep 2012 14:50:36 -0600 Message-ID: From: jacek burghardt To: xen-users Subject: [Xen-users] file location X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============0579599251128515518==" Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org --===============0579599251128515518== Content-Type: multipart/alternative; boundary=20cf30050d90217fdd04ca5082b6 --20cf30050d90217fdd04ca5082b6 Content-Type: text/plain; charset=ISO-8859-1 I wonder if anyone knows what creates /var/run/xend/xen-api.sock and whole directory /var/run/xend. I am running arch linux so I need to patch xen-4.2 to use /run/daemons> --20cf30050d90217fdd04ca5082b6 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable I wonder if anyone knows what creates=A0 /var/run/xend/xen-api.sock and who= le directory /var/run/xend. I am running arch linux so I need to patch xen-= 4.2 to use /run/daemons>
--20cf30050d90217fdd04ca5082b6-- --===============0579599251128515518== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users --===============0579599251128515518==-- From xen-users-bounces@lists.xen.org Sat Sep 22 23:08:17 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Sat, 22 Sep 2012 23:08:17 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TFYmd-0005xV-78; Sat, 22 Sep 2012 23:06:47 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from <0x0b5c@mawrth.net>) id 1TFWfo-00055Q-G1 for xen-users@lists.xen.org; Sat, 22 Sep 2012 20:51:36 +0000 Received: from [85.158.139.211:18221] by server-1.bemta-5.messagelabs.com id 75/DE-04809-7D42E505; Sat, 22 Sep 2012 20:51:35 +0000 X-Env-Sender: 0x0b5c@mawrth.net X-Msg-Ref: server-12.tower-206.messagelabs.com!1348347094!18578546!1 X-Originating-IP: [96.126.107.192] X-SpamReason: No, hits=0.5 required=7.0 tests=BODY_RANDOM_LONG X-StarScan-Received: X-StarScan-Version: 6.6.1.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 3650 invoked from network); 22 Sep 2012 20:51:35 -0000 Received: from outpost.mawrth.net (HELO outpost.mawrth.net) (96.126.107.192) by server-12.tower-206.messagelabs.com with AES256-SHA encrypted SMTP; 22 Sep 2012 20:51:35 -0000 Received: from wrkq by outpost.mawrth.net with local (Exim 4.72) (envelope-from <0x0b5c@mawrth.net>) id 1TFWfl-0003tv-L9; Sat, 22 Sep 2012 22:51:33 +0200 Date: Sat, 22 Sep 2012 22:51:33 +0200 From: Wojciech Kusiak <0x0b5c@mawrth.net> To: xen-users@lists.xen.org Message-ID: <20120922205133.GA13116@mawrth.net> MIME-Version: 1.0 Content-Disposition: inline User-Agent: Mutt/1.5.20 (2009-06-14) X-Mailman-Approved-At: Sat, 22 Sep 2012 23:06:46 +0000 Subject: [Xen-users] GPLPV .356/2008 R2 x64/xennet.sys - interfaces don't work, bluescreens if xenvbd also installed X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org Good evening. I am in a bit of a weird situation here, so let me apologize up front if this will turn out to be a waste of everyone's time. I have up to date Win 2008 R2 x64 SP1 VMs running at a Xen-based provider not of my choosing. After installing GPLPV rev. 356 (signed from Univention) and rebooting, I'm getting a bluescreen in xennet.sys a few seconds after boot. The VMs have 2 vCPUs each, so it may or may not be related to the 16-cpu issue reported on this list earlier. I have no idea how the underlying Xen host is configured, or what versions it runs. The provides it quite unhelpful (once again - I have no say in the matter of provider choice). In short: Originally, on a test machine, I've installed the whole pack (that being xenpci, xennet, xenvbd, xenscsi, xenusb). It started to bluescreen right after reboot (usually a few seconds after the "Press C+A+D to log on" prompt appeared. The bluescreen was IRQL_NOT_LESS_OR_EQUAL in xennet.sys, but I did not note the hexcodes then. I've undone the setup, tried to install just the xenpci + shutdownmon, cleared the registry for the emulated RTL8139 NICs to reappear, and gave up. Right now I'm testing on a different VM - and I see the following: * xenpci + xennet = no bluescreen, Xen Net adapters appear, but zero network connectivity (the packets in/out counters stay at 0, DHCP info not obtained, etc.) * xenpci + xennet + xenvbd = bluescreen _in xennet.sys_. DRIVER_IRQL_NOT_LESS_OR_EQUAL, happens variously between a few seconds and about 2 minutes after boot. *** STOP 0x000000D1 (0x00000000000000028,0x0000000000000002,0x0000000000000000,0xFFFF8800F9A104) *** xennet.sys - Address FFFF8800F9A104 base at FFFF8800F9700, DateStamp 4f6b1e83 Any hints about what to do to get the xennet adapters running? I don't really need xenvbd - the disks are fast enough without it - but considering this bluescreen happens after installing xenvbd but in xennet, and that the xennet alone doesn't crash but the adapters don't work, I'm reporting these issues together. My main reason for trying to get xennet to work again is that the RTL8139 NICs are causing massive interrupts spam (whole CPU in kernelmode, Process Explorer blames interrupts, network I/O topping around 20 MBit/s). If they shouldn't do that, and there's a way to make them stop doing that, I'd accept that as a "solution". You probably will need additional information - please tell me what's necessary. In case of host information, please be precise - I'll be having a hard time convincing the provider to obtain them, it'd take even longer if they wouldn't understand what we want from them. Best regards, Wojciech Kusiak _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Sat Sep 22 23:08:17 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Sat, 22 Sep 2012 23:08:17 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TFYmd-0005xV-78; Sat, 22 Sep 2012 23:06:47 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from <0x0b5c@mawrth.net>) id 1TFWfo-00055Q-G1 for xen-users@lists.xen.org; Sat, 22 Sep 2012 20:51:36 +0000 Received: from [85.158.139.211:18221] by server-1.bemta-5.messagelabs.com id 75/DE-04809-7D42E505; Sat, 22 Sep 2012 20:51:35 +0000 X-Env-Sender: 0x0b5c@mawrth.net X-Msg-Ref: server-12.tower-206.messagelabs.com!1348347094!18578546!1 X-Originating-IP: [96.126.107.192] X-SpamReason: No, hits=0.5 required=7.0 tests=BODY_RANDOM_LONG X-StarScan-Received: X-StarScan-Version: 6.6.1.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 3650 invoked from network); 22 Sep 2012 20:51:35 -0000 Received: from outpost.mawrth.net (HELO outpost.mawrth.net) (96.126.107.192) by server-12.tower-206.messagelabs.com with AES256-SHA encrypted SMTP; 22 Sep 2012 20:51:35 -0000 Received: from wrkq by outpost.mawrth.net with local (Exim 4.72) (envelope-from <0x0b5c@mawrth.net>) id 1TFWfl-0003tv-L9; Sat, 22 Sep 2012 22:51:33 +0200 Date: Sat, 22 Sep 2012 22:51:33 +0200 From: Wojciech Kusiak <0x0b5c@mawrth.net> To: xen-users@lists.xen.org Message-ID: <20120922205133.GA13116@mawrth.net> MIME-Version: 1.0 Content-Disposition: inline User-Agent: Mutt/1.5.20 (2009-06-14) X-Mailman-Approved-At: Sat, 22 Sep 2012 23:06:46 +0000 Subject: [Xen-users] GPLPV .356/2008 R2 x64/xennet.sys - interfaces don't work, bluescreens if xenvbd also installed X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org Good evening. I am in a bit of a weird situation here, so let me apologize up front if this will turn out to be a waste of everyone's time. I have up to date Win 2008 R2 x64 SP1 VMs running at a Xen-based provider not of my choosing. After installing GPLPV rev. 356 (signed from Univention) and rebooting, I'm getting a bluescreen in xennet.sys a few seconds after boot. The VMs have 2 vCPUs each, so it may or may not be related to the 16-cpu issue reported on this list earlier. I have no idea how the underlying Xen host is configured, or what versions it runs. The provides it quite unhelpful (once again - I have no say in the matter of provider choice). In short: Originally, on a test machine, I've installed the whole pack (that being xenpci, xennet, xenvbd, xenscsi, xenusb). It started to bluescreen right after reboot (usually a few seconds after the "Press C+A+D to log on" prompt appeared. The bluescreen was IRQL_NOT_LESS_OR_EQUAL in xennet.sys, but I did not note the hexcodes then. I've undone the setup, tried to install just the xenpci + shutdownmon, cleared the registry for the emulated RTL8139 NICs to reappear, and gave up. Right now I'm testing on a different VM - and I see the following: * xenpci + xennet = no bluescreen, Xen Net adapters appear, but zero network connectivity (the packets in/out counters stay at 0, DHCP info not obtained, etc.) * xenpci + xennet + xenvbd = bluescreen _in xennet.sys_. DRIVER_IRQL_NOT_LESS_OR_EQUAL, happens variously between a few seconds and about 2 minutes after boot. *** STOP 0x000000D1 (0x00000000000000028,0x0000000000000002,0x0000000000000000,0xFFFF8800F9A104) *** xennet.sys - Address FFFF8800F9A104 base at FFFF8800F9700, DateStamp 4f6b1e83 Any hints about what to do to get the xennet adapters running? I don't really need xenvbd - the disks are fast enough without it - but considering this bluescreen happens after installing xenvbd but in xennet, and that the xennet alone doesn't crash but the adapters don't work, I'm reporting these issues together. My main reason for trying to get xennet to work again is that the RTL8139 NICs are causing massive interrupts spam (whole CPU in kernelmode, Process Explorer blames interrupts, network I/O topping around 20 MBit/s). If they shouldn't do that, and there's a way to make them stop doing that, I'd accept that as a "solution". You probably will need additional information - please tell me what's necessary. In case of host information, please be precise - I'll be having a hard time convincing the provider to obtain them, it'd take even longer if they wouldn't understand what we want from them. Best regards, Wojciech Kusiak _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Sun Sep 23 13:14:32 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Sun, 23 Sep 2012 13:14:32 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TFlzH-0006vX-CF; Sun, 23 Sep 2012 13:12:43 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TFZnA-0006vr-GM for xen-users@lists.xen.org; Sun, 23 Sep 2012 00:11:24 +0000 Received: from [85.158.139.211:35441] by server-3.bemta-5.messagelabs.com id E7/85-21836-BA35E505; Sun, 23 Sep 2012 00:11:23 +0000 X-Env-Sender: lukas@laukamp.me X-Msg-Ref: server-4.tower-206.messagelabs.com!1348359082!19602786!1 X-Originating-IP: [5.9.218.245] X-SpamReason: No, hits=0.3 required=7.0 tests=HTML_50_60,HTML_MESSAGE, RCVD_ILLEGAL_IP X-StarScan-Received: X-StarScan-Version: 6.6.1.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 19871 invoked from network); 23 Sep 2012 00:11:23 -0000 Received: from mailer0.lippux.de (HELO mailer0.lippux.de) (5.9.218.245) by server-4.tower-206.messagelabs.com with SMTP; 23 Sep 2012 00:11:23 -0000 Received: from localhost (localhost [127.0.0.1]) by mailer0.lippux.de (Postfix) with ESMTP id 91AD9421127; Sun, 23 Sep 2012 02:11:22 +0200 (CEST) X-Virus-Scanned: Debian amavisd-new at mailer0.lippux.de Received: from mailer0.lippux.de ([127.0.0.1]) by localhost (mailer0.lippux.de [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id mzE3kSfVoPDP; Sun, 23 Sep 2012 02:11:22 +0200 (CEST) Received: from [127.0.0.1] (unknown [5.9.218.242]) (Authenticated sender: lukas@laukamp.me) by mailer0.lippux.de (Postfix) with ESMTPSA id EAC9342110E; Sun, 23 Sep 2012 02:11:21 +0200 (CEST) Message-ID: <505E53A9.70306@laukamp.me> Date: Sun, 23 Sep 2012 02:11:21 +0200 From: Lukas Laukamp User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:15.0) Gecko/20120907 Thunderbird/15.0.1 MIME-Version: 1.0 To: jacek burghardt References: In-Reply-To: X-Mailman-Approved-At: Sun, 23 Sep 2012 13:12:42 +0000 Cc: xen-users Subject: Re: [Xen-users] file location X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============3656260733181278352==" Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org This is a multi-part message in MIME format. --===============3656260733181278352== Content-Type: multipart/alternative; boundary="------------090208090905060908020407" This is a multi-part message in MIME format. --------------090208090905060908020407 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Am 22.09.2012 22:50, schrieb jacek burghardt: > I wonder if anyone knows what creates /var/run/xend/xen-api.sock and > whole directory /var/run/xend. I am running arch linux so I need to > patch xen-4.2 to use /run/daemons> > > > _______________________________________________ > Xen-users mailing list > Xen-users@lists.xen.org > http://lists.xen.org/xen-users Hi, with which method do you have installed Xen, package or source? This folder by default gets created by xend. If you have installed Xen from source there are no Arch Linux specific patches present in the source code. As a simple fix I would create symlink(s). Best Regards --------------090208090905060908020407 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit
Am 22.09.2012 22:50, schrieb jacek burghardt:
I wonder if anyone knows what creates  /var/run/xend/xen-api.sock and whole directory /var/run/xend. I am running arch linux so I need to patch xen-4.2 to use /run/daemons> 


_______________________________________________
Xen-users mailing list
Xen-users@lists.xen.org
http://lists.xen.org/xen-users

Hi,

with which method do you have installed Xen, package or source? This folder by default gets created by xend. If you have installed Xen from source there are no Arch Linux specific patches present in the source code. As a simple fix I would create symlink(s).

Best Regards
--------------090208090905060908020407-- --===============3656260733181278352== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users --===============3656260733181278352==-- From xen-users-bounces@lists.xen.org Sun Sep 23 13:14:32 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Sun, 23 Sep 2012 13:14:32 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TFlzH-0006vX-CF; Sun, 23 Sep 2012 13:12:43 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TFZnA-0006vr-GM for xen-users@lists.xen.org; Sun, 23 Sep 2012 00:11:24 +0000 Received: from [85.158.139.211:35441] by server-3.bemta-5.messagelabs.com id E7/85-21836-BA35E505; Sun, 23 Sep 2012 00:11:23 +0000 X-Env-Sender: lukas@laukamp.me X-Msg-Ref: server-4.tower-206.messagelabs.com!1348359082!19602786!1 X-Originating-IP: [5.9.218.245] X-SpamReason: No, hits=0.3 required=7.0 tests=HTML_50_60,HTML_MESSAGE, RCVD_ILLEGAL_IP X-StarScan-Received: X-StarScan-Version: 6.6.1.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 19871 invoked from network); 23 Sep 2012 00:11:23 -0000 Received: from mailer0.lippux.de (HELO mailer0.lippux.de) (5.9.218.245) by server-4.tower-206.messagelabs.com with SMTP; 23 Sep 2012 00:11:23 -0000 Received: from localhost (localhost [127.0.0.1]) by mailer0.lippux.de (Postfix) with ESMTP id 91AD9421127; Sun, 23 Sep 2012 02:11:22 +0200 (CEST) X-Virus-Scanned: Debian amavisd-new at mailer0.lippux.de Received: from mailer0.lippux.de ([127.0.0.1]) by localhost (mailer0.lippux.de [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id mzE3kSfVoPDP; Sun, 23 Sep 2012 02:11:22 +0200 (CEST) Received: from [127.0.0.1] (unknown [5.9.218.242]) (Authenticated sender: lukas@laukamp.me) by mailer0.lippux.de (Postfix) with ESMTPSA id EAC9342110E; Sun, 23 Sep 2012 02:11:21 +0200 (CEST) Message-ID: <505E53A9.70306@laukamp.me> Date: Sun, 23 Sep 2012 02:11:21 +0200 From: Lukas Laukamp User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:15.0) Gecko/20120907 Thunderbird/15.0.1 MIME-Version: 1.0 To: jacek burghardt References: In-Reply-To: X-Mailman-Approved-At: Sun, 23 Sep 2012 13:12:42 +0000 Cc: xen-users Subject: Re: [Xen-users] file location X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============3656260733181278352==" Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org This is a multi-part message in MIME format. --===============3656260733181278352== Content-Type: multipart/alternative; boundary="------------090208090905060908020407" This is a multi-part message in MIME format. --------------090208090905060908020407 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Am 22.09.2012 22:50, schrieb jacek burghardt: > I wonder if anyone knows what creates /var/run/xend/xen-api.sock and > whole directory /var/run/xend. I am running arch linux so I need to > patch xen-4.2 to use /run/daemons> > > > _______________________________________________ > Xen-users mailing list > Xen-users@lists.xen.org > http://lists.xen.org/xen-users Hi, with which method do you have installed Xen, package or source? This folder by default gets created by xend. If you have installed Xen from source there are no Arch Linux specific patches present in the source code. As a simple fix I would create symlink(s). Best Regards --------------090208090905060908020407 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit
Am 22.09.2012 22:50, schrieb jacek burghardt:
I wonder if anyone knows what creates  /var/run/xend/xen-api.sock and whole directory /var/run/xend. I am running arch linux so I need to patch xen-4.2 to use /run/daemons> 


_______________________________________________
Xen-users mailing list
Xen-users@lists.xen.org
http://lists.xen.org/xen-users

Hi,

with which method do you have installed Xen, package or source? This folder by default gets created by xend. If you have installed Xen from source there are no Arch Linux specific patches present in the source code. As a simple fix I would create symlink(s).

Best Regards
--------------090208090905060908020407-- --===============3656260733181278352== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users --===============3656260733181278352==-- From xen-users-bounces@lists.xen.org Sun Sep 23 20:18:33 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Sun, 23 Sep 2012 20:18:33 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TFsbv-0001Tk-LG; Sun, 23 Sep 2012 20:17:03 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TFsbu-0001TZ-IS for xen-users@lists.xen.org; Sun, 23 Sep 2012 20:17:02 +0000 Received: from [85.158.139.83:38881] by server-4.bemta-5.messagelabs.com id 36/F2-23042-D3E6F505; Sun, 23 Sep 2012 20:17:01 +0000 X-Env-Sender: awg1@gmx.com X-Msg-Ref: server-2.tower-182.messagelabs.com!1348431421!28914168!1 X-Originating-IP: [213.165.64.43] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogMjEzLjE2NS42NC40MyA9PiAzMDAzNA==\n, ML_RADAR_SPEW_LINKS_14,spamassassin: X-StarScan-Received: X-StarScan-Version: 6.6.1.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 1588 invoked from network); 23 Sep 2012 20:17:01 -0000 Received: from mailout-eu.gmx.com (HELO mailout-eu.gmx.com) (213.165.64.43) by server-2.tower-182.messagelabs.com with SMTP; 23 Sep 2012 20:17:01 -0000 Received: (qmail 31443 invoked by uid 0); 23 Sep 2012 20:17:00 -0000 Received: from 82.35.75.35 by rms-eu009.v300.gmx.net with HTTP Date: Sun, 23 Sep 2012 22:16:59 +0200 From: "Adam Gold" Message-ID: <20120923201659.164740@gmx.com> MIME-Version: 1.0 To: xen-users@lists.xen.org X-Authenticated: #138788998 X-Flags: 0001 X-Mailer: GMX.com Web Mailer x-registered: 0 X-GMX-UID: bAstcD4heSEqJuejLnwh0Vh+IGRvbwDV Subject: [Xen-users] Xen 4.2 - xl error X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: base64 Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org SGkuIMKgSSdtIG5vdCBzdXJlIGlmIEkgc2hvdWxkIGJlIHBvc3RpbmcgdGhpcyB0byB0aGUgZGV2 IGxpc3QgYnV0IHRoZSB3aWtpIG1lbnRpb25lZCB0cnlpbmcgaGVyZSBmaXJzdC4gwqBJJ3ZlIGp1 c3QgaW5zdGFsbGVkIDQuMiBvbiBhIGhvc3QgcnVubmluZyB1YnVudHUgMTIuMDQgYXMgZm9sbG93 czoKLSBkZXBlbmRlbmNpZXM6IGFwdC1nZXQgYnVpbGQtZGVwIHhlbiAmJiBhcHQtZ2V0IGluc3Rh bGwgbGliZ2xpYjIuMC1kZXYgbGlieWFqbC1kZXYKLSBidWlsZDogLi9jb25maWd1cmU7IG1ha2Ug d29ybGQ7IG1ha2UgaW5zdGFsbAoKVGhlIGZvbGxvd2luZyBlcnJvcnMgd2VyZSByZXBvcnRlZCBk dXJpbmcgdGhlIGNvbXBpbGluZyBzdGFnZSBob3dldmVyIEkgd2FzIGFibGUgdG8gcHJvY2VlZCB0 byBtYWtlIGluc3RhbGw6Cm1ha2VbM106IEVudGVyaW5nIGRpcmVjdG9yeSBgL3Jvb3QveGVuLTQu Mi4wL3Rvb2xzL2Zpcm13YXJlJwpHSVQ9Z2l0IC9yb290L3hlbi00LjIuMC90b29scy9maXJtd2Fy ZS8uLi8uLi9zY3JpcHRzL2dpdC1jaGVja291dC5zaCBnaXQ6Ly94ZW5iaXRzLnhlbi5vcmcvc2Vh Ymlvcy5naXQgcmVsLTEuNi4zLjIgc2VhYmlvcy1kaXIKL3Jvb3QveGVuLTQuMi4wL3Rvb2xzL2Zp cm13YXJlLy4uLy4uL3NjcmlwdHMvZ2l0LWNoZWNrb3V0LnNoOiAxNzogL3Jvb3QveGVuLTQuMi4w L3Rvb2xzL2Zpcm13YXJlLy4uLy4uL3NjcmlwdHMvZ2l0LWNoZWNrb3V0LnNoOiBnaXQ6IG5vdCBm b3VuZAptYWtlWzNdOiAqKiogW3NlYWJpb3MtZGlyXSBFcnJvciAxMjcKbWFrZVszXTogTGVhdmlu ZyBkaXJlY3RvcnkgYC9yb290L3hlbi00LjIuMC90b29scy9maXJtd2FyZScKbWFrZVsyXTogKioq IFtzdWJkaXItaW5zdGFsbC1maXJtd2FyZV0gRXJyb3IgMgptYWtlWzJdOiBMZWF2aW5nIGRpcmVj dG9yeSBgL3Jvb3QveGVuLTQuMi4wL3Rvb2xzJwptYWtlWzFdOiAqKiogW3N1YmRpcnMtaW5zdGFs bF0gRXJyb3IgMgptYWtlWzFdOiBMZWF2aW5nIGRpcmVjdG9yeSBgL3Jvb3QveGVuLTQuMi4wL3Rv b2xzJwptYWtlOiAqKiogW2luc3RhbGwtdG9vbHNdIEVycm9yIDIKCkkgcmVib290ZWQgaW50byB0 aGUgeGVuIGtlcm5lbCAoSSBtYW51YWxseSBzZWxlY3RlZCBpdCBmcm9tIHRoZSBncnViIG1lbnUg dG8gYmUgc3VyZSkgYW5kIHRyaWVkICd4bCBpbmZvJy4gwqBJIHJlY2VpdmVkIHRoZSBmb2xsb3dp bmcgbWVzc2FnZTogJ1RoZSBwcm9ncmFtICd4bCcgaXMgY3VycmVudGx5IG5vdCBpbnN0YWxsZWQu IFlvdSBjYW4gaW5zdGFsbCBpdCBieSB0eXBpbmc6IGFwdC1nZXQgaW5zdGFsbCB4ZW4tdXRpbHMt Y29tbW9uJy4KCkkgd2VudCBhaGVhZCB3aXRoIHRoZSBpbnN0YWxsIHNwZWNpZnlpbmcsIHdoZW4g YXNrZWQsIHRvIGtlZXAgdGhlIGN1cnJlbnRseSBpbnN0YWxsZWQgc2NyaXB0cy4gwqBJIHRyaWVk ICd4bCBpbmZvJyBhZ2FpbiBhbmQgcmVjZWl2ZWQgdGhlIGZvbGxvd2luZyBtZXNzYWdlOiAnRVJS T1I6IMKgQ2FuJ3QgZmluZCB2ZXJzaW9uIDQuMiBvZiB4ZW4gdXRpbHMsIGJhaWxpbmcgb3V0IScK Ck5leHQgSSB1bmluc3RhbGxlZCB0aGUgcGFja2FnZSB1c2luZyAnYXB0LWdldCByZW1vdmUgeGVu LXV0aWxzLWNvbW1vbicgYW5kIHRyaWVkIG1hbnVhbGx5IGluc3RhbGxpbmcgd2hhdCBzZWVtcyB0 byBiZSBsaWtlIGEgNC4yIHZlcnNpb24gaGVyZTogaHR0cDovL3BhY2thZ2VzLmRlYmlhbi5vcmcv ZXhwZXJpbWVudGFsL2FsbC94ZW4tdXRpbHMtY29tbW9uL2Rvd25sb2FkLiDCoEkgc3RpbGwgcmVj ZWl2ZWQgdGhlIHNhbWUgZXJyb3IgbWVzc2FnZSBhZnRlciB0cnlpbmcgJ3hsIGluZm8nIGFnYWlu LgoKRllJLCBJIGdldCB0aGUgc2FtZSBlcnJvciBtZXNzYWdlIHdoZW4gSSB0cnkgdXNpbmcgeG0u CgpTaG91bGRuJ3QgdGhlIHNvdXJjZSBjb2RlIGluc3RhbGxhdGlvbiBoYXZlIGluY2x1ZGVkIHhl bi11dGlscy1jb21tb24/IMKgQW55IHN1Z2dlc3Rpb25zIG9uIHdoYXQgSSBzaG91bGQgYmUgZG9p bmcgdG8gc29sdmUgdGhpcz8gwqBIYXBweSB0byBwcm92aWRlIGZ1cnRoZXIgaW5mby4gwqBUaGFu a3MgaW4gYWR2YW5jZS4KCl9fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19f X19fX19fClhlbi11c2VycyBtYWlsaW5nIGxpc3QKWGVuLXVzZXJzQGxpc3RzLnhlbi5vcmcKaHR0 cDovL2xpc3RzLnhlbi5vcmcveGVuLXVzZXJz From xen-users-bounces@lists.xen.org Sun Sep 23 20:18:33 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Sun, 23 Sep 2012 20:18:33 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TFsbv-0001Tk-LG; Sun, 23 Sep 2012 20:17:03 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TFsbu-0001TZ-IS for xen-users@lists.xen.org; Sun, 23 Sep 2012 20:17:02 +0000 Received: from [85.158.139.83:38881] by server-4.bemta-5.messagelabs.com id 36/F2-23042-D3E6F505; Sun, 23 Sep 2012 20:17:01 +0000 X-Env-Sender: awg1@gmx.com X-Msg-Ref: server-2.tower-182.messagelabs.com!1348431421!28914168!1 X-Originating-IP: [213.165.64.43] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogMjEzLjE2NS42NC40MyA9PiAzMDAzNA==\n, ML_RADAR_SPEW_LINKS_14,spamassassin: X-StarScan-Received: X-StarScan-Version: 6.6.1.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 1588 invoked from network); 23 Sep 2012 20:17:01 -0000 Received: from mailout-eu.gmx.com (HELO mailout-eu.gmx.com) (213.165.64.43) by server-2.tower-182.messagelabs.com with SMTP; 23 Sep 2012 20:17:01 -0000 Received: (qmail 31443 invoked by uid 0); 23 Sep 2012 20:17:00 -0000 Received: from 82.35.75.35 by rms-eu009.v300.gmx.net with HTTP Date: Sun, 23 Sep 2012 22:16:59 +0200 From: "Adam Gold" Message-ID: <20120923201659.164740@gmx.com> MIME-Version: 1.0 To: xen-users@lists.xen.org X-Authenticated: #138788998 X-Flags: 0001 X-Mailer: GMX.com Web Mailer x-registered: 0 X-GMX-UID: bAstcD4heSEqJuejLnwh0Vh+IGRvbwDV Subject: [Xen-users] Xen 4.2 - xl error X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: base64 Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org SGkuIMKgSSdtIG5vdCBzdXJlIGlmIEkgc2hvdWxkIGJlIHBvc3RpbmcgdGhpcyB0byB0aGUgZGV2 IGxpc3QgYnV0IHRoZSB3aWtpIG1lbnRpb25lZCB0cnlpbmcgaGVyZSBmaXJzdC4gwqBJJ3ZlIGp1 c3QgaW5zdGFsbGVkIDQuMiBvbiBhIGhvc3QgcnVubmluZyB1YnVudHUgMTIuMDQgYXMgZm9sbG93 czoKLSBkZXBlbmRlbmNpZXM6IGFwdC1nZXQgYnVpbGQtZGVwIHhlbiAmJiBhcHQtZ2V0IGluc3Rh bGwgbGliZ2xpYjIuMC1kZXYgbGlieWFqbC1kZXYKLSBidWlsZDogLi9jb25maWd1cmU7IG1ha2Ug d29ybGQ7IG1ha2UgaW5zdGFsbAoKVGhlIGZvbGxvd2luZyBlcnJvcnMgd2VyZSByZXBvcnRlZCBk dXJpbmcgdGhlIGNvbXBpbGluZyBzdGFnZSBob3dldmVyIEkgd2FzIGFibGUgdG8gcHJvY2VlZCB0 byBtYWtlIGluc3RhbGw6Cm1ha2VbM106IEVudGVyaW5nIGRpcmVjdG9yeSBgL3Jvb3QveGVuLTQu Mi4wL3Rvb2xzL2Zpcm13YXJlJwpHSVQ9Z2l0IC9yb290L3hlbi00LjIuMC90b29scy9maXJtd2Fy ZS8uLi8uLi9zY3JpcHRzL2dpdC1jaGVja291dC5zaCBnaXQ6Ly94ZW5iaXRzLnhlbi5vcmcvc2Vh Ymlvcy5naXQgcmVsLTEuNi4zLjIgc2VhYmlvcy1kaXIKL3Jvb3QveGVuLTQuMi4wL3Rvb2xzL2Zp cm13YXJlLy4uLy4uL3NjcmlwdHMvZ2l0LWNoZWNrb3V0LnNoOiAxNzogL3Jvb3QveGVuLTQuMi4w L3Rvb2xzL2Zpcm13YXJlLy4uLy4uL3NjcmlwdHMvZ2l0LWNoZWNrb3V0LnNoOiBnaXQ6IG5vdCBm b3VuZAptYWtlWzNdOiAqKiogW3NlYWJpb3MtZGlyXSBFcnJvciAxMjcKbWFrZVszXTogTGVhdmlu ZyBkaXJlY3RvcnkgYC9yb290L3hlbi00LjIuMC90b29scy9maXJtd2FyZScKbWFrZVsyXTogKioq IFtzdWJkaXItaW5zdGFsbC1maXJtd2FyZV0gRXJyb3IgMgptYWtlWzJdOiBMZWF2aW5nIGRpcmVj dG9yeSBgL3Jvb3QveGVuLTQuMi4wL3Rvb2xzJwptYWtlWzFdOiAqKiogW3N1YmRpcnMtaW5zdGFs bF0gRXJyb3IgMgptYWtlWzFdOiBMZWF2aW5nIGRpcmVjdG9yeSBgL3Jvb3QveGVuLTQuMi4wL3Rv b2xzJwptYWtlOiAqKiogW2luc3RhbGwtdG9vbHNdIEVycm9yIDIKCkkgcmVib290ZWQgaW50byB0 aGUgeGVuIGtlcm5lbCAoSSBtYW51YWxseSBzZWxlY3RlZCBpdCBmcm9tIHRoZSBncnViIG1lbnUg dG8gYmUgc3VyZSkgYW5kIHRyaWVkICd4bCBpbmZvJy4gwqBJIHJlY2VpdmVkIHRoZSBmb2xsb3dp bmcgbWVzc2FnZTogJ1RoZSBwcm9ncmFtICd4bCcgaXMgY3VycmVudGx5IG5vdCBpbnN0YWxsZWQu IFlvdSBjYW4gaW5zdGFsbCBpdCBieSB0eXBpbmc6IGFwdC1nZXQgaW5zdGFsbCB4ZW4tdXRpbHMt Y29tbW9uJy4KCkkgd2VudCBhaGVhZCB3aXRoIHRoZSBpbnN0YWxsIHNwZWNpZnlpbmcsIHdoZW4g YXNrZWQsIHRvIGtlZXAgdGhlIGN1cnJlbnRseSBpbnN0YWxsZWQgc2NyaXB0cy4gwqBJIHRyaWVk ICd4bCBpbmZvJyBhZ2FpbiBhbmQgcmVjZWl2ZWQgdGhlIGZvbGxvd2luZyBtZXNzYWdlOiAnRVJS T1I6IMKgQ2FuJ3QgZmluZCB2ZXJzaW9uIDQuMiBvZiB4ZW4gdXRpbHMsIGJhaWxpbmcgb3V0IScK Ck5leHQgSSB1bmluc3RhbGxlZCB0aGUgcGFja2FnZSB1c2luZyAnYXB0LWdldCByZW1vdmUgeGVu LXV0aWxzLWNvbW1vbicgYW5kIHRyaWVkIG1hbnVhbGx5IGluc3RhbGxpbmcgd2hhdCBzZWVtcyB0 byBiZSBsaWtlIGEgNC4yIHZlcnNpb24gaGVyZTogaHR0cDovL3BhY2thZ2VzLmRlYmlhbi5vcmcv ZXhwZXJpbWVudGFsL2FsbC94ZW4tdXRpbHMtY29tbW9uL2Rvd25sb2FkLiDCoEkgc3RpbGwgcmVj ZWl2ZWQgdGhlIHNhbWUgZXJyb3IgbWVzc2FnZSBhZnRlciB0cnlpbmcgJ3hsIGluZm8nIGFnYWlu LgoKRllJLCBJIGdldCB0aGUgc2FtZSBlcnJvciBtZXNzYWdlIHdoZW4gSSB0cnkgdXNpbmcgeG0u CgpTaG91bGRuJ3QgdGhlIHNvdXJjZSBjb2RlIGluc3RhbGxhdGlvbiBoYXZlIGluY2x1ZGVkIHhl bi11dGlscy1jb21tb24/IMKgQW55IHN1Z2dlc3Rpb25zIG9uIHdoYXQgSSBzaG91bGQgYmUgZG9p bmcgdG8gc29sdmUgdGhpcz8gwqBIYXBweSB0byBwcm92aWRlIGZ1cnRoZXIgaW5mby4gwqBUaGFu a3MgaW4gYWR2YW5jZS4KCl9fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19f X19fX19fClhlbi11c2VycyBtYWlsaW5nIGxpc3QKWGVuLXVzZXJzQGxpc3RzLnhlbi5vcmcKaHR0 cDovL2xpc3RzLnhlbi5vcmcveGVuLXVzZXJz From xen-users-bounces@lists.xen.org Sun Sep 23 21:43:01 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Sun, 23 Sep 2012 21:43:01 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TFtvk-0002If-J6; Sun, 23 Sep 2012 21:41:36 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TFtvi-0002Ia-QV for xen-users@lists.xen.org; Sun, 23 Sep 2012 21:41:35 +0000 Received: from [85.158.139.83:5080] by server-9.bemta-5.messagelabs.com id 9D/C4-20529-D028F505; Sun, 23 Sep 2012 21:41:33 +0000 X-Env-Sender: giamteckchoon@gmail.com X-Msg-Ref: server-2.tower-182.messagelabs.com!1348436491!28918468!1 X-Originating-IP: [209.85.210.45] X-SpamReason: No, hits=0.3 required=7.0 tests=ML_RADAR_SPEW_LINKS_14, RCVD_BY_IP,spamassassin: X-StarScan-Received: X-StarScan-Version: 6.6.1.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 30328 invoked from network); 23 Sep 2012 21:41:33 -0000 Received: from mail-da0-f45.google.com (HELO mail-da0-f45.google.com) (209.85.210.45) by server-2.tower-182.messagelabs.com with RC4-SHA encrypted SMTP; 23 Sep 2012 21:41:33 -0000 Received: by dadn15 with SMTP id n15so73315dad.32 for ; Sun, 23 Sep 2012 14:41:30 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; bh=Uv+3EJA5gRRDDJJ9g3M72ps4/UxNs4x9jkqXL2je+e4=; b=Q5gfZi4iSWq79ygaZuygGVn5naQhg3k1MH7GfW/+lku4V0KYowE85UnxGfqaEzGmHc UezcIPB0HzV+gkyUCG/yMzomvmcDszIPbW+9RAreGm5NmpjpGgBN5qFHQcMrdNsYZSw5 YtJUto2xEow9VtRIfmBzG41xFEVAwljnH61yYFle6RfRD/VUid6DxbvKOmzol7kOQkE9 5rdsJpyZFITBAJmsgIpUszez1OXoTNhXYQZUePRmKrl7VFNiuOTlEYvuQRrVJiJbWC/D cnpTWSE/DV9NbBMByhk0bhimDpW/yszH6/zMUzFNghpFuvkOioo6fLnbbQZgY941JAIT HI5w== MIME-Version: 1.0 Received: by 10.66.87.138 with SMTP id ay10mr27761608pab.38.1348436490683; Sun, 23 Sep 2012 14:41:30 -0700 (PDT) Received: by 10.68.212.39 with HTTP; Sun, 23 Sep 2012 14:41:30 -0700 (PDT) In-Reply-To: <20120923201659.164740@gmx.com> References: <20120923201659.164740@gmx.com> Date: Mon, 24 Sep 2012 05:41:30 +0800 Message-ID: From: Teck Choon Giam To: Adam Gold Cc: xen-users@lists.xen.org Subject: Re: [Xen-users] Xen 4.2 - xl error X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org On Mon, Sep 24, 2012 at 4:16 AM, Adam Gold wrote: > Hi. I'm not sure if I should be posting this to the dev list but the wiki mentioned trying here first. I've just installed 4.2 on a host running ubuntu 12.04 as follows: > - dependencies: apt-get build-dep xen && apt-get install libglib2.0-dev libyajl-dev > - build: ./configure; make world; make install > > The following errors were reported during the compiling stage however I was able to proceed to make install: > make[3]: Entering directory `/root/xen-4.2.0/tools/firmware' > GIT=git /root/xen-4.2.0/tools/firmware/../../scripts/git-checkout.sh git://xenbits.xen.org/seabios.git rel-1.6.3.2 seabios-dir > /root/xen-4.2.0/tools/firmware/../../scripts/git-checkout.sh: 17: /root/xen-4.2.0/tools/firmware/../../scripts/git-checkout.sh: git: not found Please read the error carefully... ... git: not found ... so you need to install git first. Thanks. Kindest regards, Giam Teck Choon > make[3]: *** [seabios-dir] Error 127 > make[3]: Leaving directory `/root/xen-4.2.0/tools/firmware' > make[2]: *** [subdir-install-firmware] Error 2 > make[2]: Leaving directory `/root/xen-4.2.0/tools' > make[1]: *** [subdirs-install] Error 2 > make[1]: Leaving directory `/root/xen-4.2.0/tools' > make: *** [install-tools] Error 2 > > I rebooted into the xen kernel (I manually selected it from the grub menu to be sure) and tried 'xl info'. I received the following message: 'The program 'xl' is currently not installed. You can install it by typing: apt-get install xen-utils-common'. > > I went ahead with the install specifying, when asked, to keep the currently installed scripts. I tried 'xl info' again and received the following message: 'ERROR: Can't find version 4.2 of xen utils, bailing out!' > > Next I uninstalled the package using 'apt-get remove xen-utils-common' and tried manually installing what seems to be like a 4.2 version here: http://packages.debian.org/experimental/all/xen-utils-common/download. I still received the same error message after trying 'xl info' again. > > FYI, I get the same error message when I try using xm. > > Shouldn't the source code installation have included xen-utils-common? Any suggestions on what I should be doing to solve this? Happy to provide further info. Thanks in advance. > > _______________________________________________ > Xen-users mailing list > Xen-users@lists.xen.org > http://lists.xen.org/xen-users _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Sun Sep 23 21:43:01 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Sun, 23 Sep 2012 21:43:01 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TFtvk-0002If-J6; Sun, 23 Sep 2012 21:41:36 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TFtvi-0002Ia-QV for xen-users@lists.xen.org; Sun, 23 Sep 2012 21:41:35 +0000 Received: from [85.158.139.83:5080] by server-9.bemta-5.messagelabs.com id 9D/C4-20529-D028F505; Sun, 23 Sep 2012 21:41:33 +0000 X-Env-Sender: giamteckchoon@gmail.com X-Msg-Ref: server-2.tower-182.messagelabs.com!1348436491!28918468!1 X-Originating-IP: [209.85.210.45] X-SpamReason: No, hits=0.3 required=7.0 tests=ML_RADAR_SPEW_LINKS_14, RCVD_BY_IP,spamassassin: X-StarScan-Received: X-StarScan-Version: 6.6.1.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 30328 invoked from network); 23 Sep 2012 21:41:33 -0000 Received: from mail-da0-f45.google.com (HELO mail-da0-f45.google.com) (209.85.210.45) by server-2.tower-182.messagelabs.com with RC4-SHA encrypted SMTP; 23 Sep 2012 21:41:33 -0000 Received: by dadn15 with SMTP id n15so73315dad.32 for ; Sun, 23 Sep 2012 14:41:30 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; bh=Uv+3EJA5gRRDDJJ9g3M72ps4/UxNs4x9jkqXL2je+e4=; b=Q5gfZi4iSWq79ygaZuygGVn5naQhg3k1MH7GfW/+lku4V0KYowE85UnxGfqaEzGmHc UezcIPB0HzV+gkyUCG/yMzomvmcDszIPbW+9RAreGm5NmpjpGgBN5qFHQcMrdNsYZSw5 YtJUto2xEow9VtRIfmBzG41xFEVAwljnH61yYFle6RfRD/VUid6DxbvKOmzol7kOQkE9 5rdsJpyZFITBAJmsgIpUszez1OXoTNhXYQZUePRmKrl7VFNiuOTlEYvuQRrVJiJbWC/D cnpTWSE/DV9NbBMByhk0bhimDpW/yszH6/zMUzFNghpFuvkOioo6fLnbbQZgY941JAIT HI5w== MIME-Version: 1.0 Received: by 10.66.87.138 with SMTP id ay10mr27761608pab.38.1348436490683; Sun, 23 Sep 2012 14:41:30 -0700 (PDT) Received: by 10.68.212.39 with HTTP; Sun, 23 Sep 2012 14:41:30 -0700 (PDT) In-Reply-To: <20120923201659.164740@gmx.com> References: <20120923201659.164740@gmx.com> Date: Mon, 24 Sep 2012 05:41:30 +0800 Message-ID: From: Teck Choon Giam To: Adam Gold Cc: xen-users@lists.xen.org Subject: Re: [Xen-users] Xen 4.2 - xl error X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org On Mon, Sep 24, 2012 at 4:16 AM, Adam Gold wrote: > Hi. I'm not sure if I should be posting this to the dev list but the wiki mentioned trying here first. I've just installed 4.2 on a host running ubuntu 12.04 as follows: > - dependencies: apt-get build-dep xen && apt-get install libglib2.0-dev libyajl-dev > - build: ./configure; make world; make install > > The following errors were reported during the compiling stage however I was able to proceed to make install: > make[3]: Entering directory `/root/xen-4.2.0/tools/firmware' > GIT=git /root/xen-4.2.0/tools/firmware/../../scripts/git-checkout.sh git://xenbits.xen.org/seabios.git rel-1.6.3.2 seabios-dir > /root/xen-4.2.0/tools/firmware/../../scripts/git-checkout.sh: 17: /root/xen-4.2.0/tools/firmware/../../scripts/git-checkout.sh: git: not found Please read the error carefully... ... git: not found ... so you need to install git first. Thanks. Kindest regards, Giam Teck Choon > make[3]: *** [seabios-dir] Error 127 > make[3]: Leaving directory `/root/xen-4.2.0/tools/firmware' > make[2]: *** [subdir-install-firmware] Error 2 > make[2]: Leaving directory `/root/xen-4.2.0/tools' > make[1]: *** [subdirs-install] Error 2 > make[1]: Leaving directory `/root/xen-4.2.0/tools' > make: *** [install-tools] Error 2 > > I rebooted into the xen kernel (I manually selected it from the grub menu to be sure) and tried 'xl info'. I received the following message: 'The program 'xl' is currently not installed. You can install it by typing: apt-get install xen-utils-common'. > > I went ahead with the install specifying, when asked, to keep the currently installed scripts. I tried 'xl info' again and received the following message: 'ERROR: Can't find version 4.2 of xen utils, bailing out!' > > Next I uninstalled the package using 'apt-get remove xen-utils-common' and tried manually installing what seems to be like a 4.2 version here: http://packages.debian.org/experimental/all/xen-utils-common/download. I still received the same error message after trying 'xl info' again. > > FYI, I get the same error message when I try using xm. > > Shouldn't the source code installation have included xen-utils-common? Any suggestions on what I should be doing to solve this? Happy to provide further info. Thanks in advance. > > _______________________________________________ > Xen-users mailing list > Xen-users@lists.xen.org > http://lists.xen.org/xen-users _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Mon Sep 24 00:47:51 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Mon, 24 Sep 2012 00:47:51 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TFwoT-0003m5-5A; Mon, 24 Sep 2012 00:46:17 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TFwoR-0003lp-8L for xen-users@lists.xen.org; Mon, 24 Sep 2012 00:46:15 +0000 Received: from [85.158.143.99:18885] by server-1.bemta-4.messagelabs.com id A1/16-05684-55DAF505; Mon, 24 Sep 2012 00:46:13 +0000 X-Env-Sender: singapore.mr.teo.en.ming@gmail.com X-Msg-Ref: server-5.tower-216.messagelabs.com!1348447570!31132103!1 X-Originating-IP: [209.85.160.45] X-SpamReason: No, hits=0.3 required=7.0 tests=ML_RADAR_SPEW_LINKS_14, RCVD_BY_IP,spamassassin: X-StarScan-Received: X-StarScan-Version: 6.6.1.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 13177 invoked from network); 24 Sep 2012 00:46:12 -0000 Received: from mail-pb0-f45.google.com (HELO mail-pb0-f45.google.com) (209.85.160.45) by server-5.tower-216.messagelabs.com with RC4-SHA encrypted SMTP; 24 Sep 2012 00:46:12 -0000 Received: by pbbrp2 with SMTP id rp2so212129pbb.32 for ; Sun, 23 Sep 2012 17:46:10 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:disposition-notification-to:date:from:user-agent :mime-version:to:cc:subject:content-type; bh=lDa7xU0tYQvz8mVL8LJtMHJUs0aI9It4xoMFwFlJBLo=; b=zGP8pqqzT4KWLWC8TiFyOuXzgfQVg6rIo44XqU+QJBK6G81EttXEMDRJ9Bo1hPgYMJ c3drj/yG3QE2UkNbXh+zbCTkQ2QxH88peZxsCsZ9kUBkUqNxk8QXcG8Y9UvShJ2Xywjv zrOiKp0u2mIi9XgE2o9YRnFCJnzbIXT1flZElrIm3sCcv+p7AW0ZCFdNKOBSO4y9lJw6 CHMZQlHriwl3XJ7ZuqeHLjxjrlMrZD32lfGOddRVzzE0IqLVDImKz8uqYmyLIlslhDJj bgL0lfeNQ8L03JPZdjv49QMziAR+ddab6TSS/ed6xRNXwx7cbo7/MEVzW1WjwqY3kNxS QQ8g== Received: by 10.66.87.105 with SMTP id w9mr3338017paz.5.1348447569994; Sun, 23 Sep 2012 17:46:09 -0700 (PDT) Received: from [192.168.1.2] (cm141.gamma206.maxonline.com.sg. [202.156.206.141]) by mx.google.com with ESMTPS id h10sm4630762pav.28.2012.09.23.17.46.07 (version=SSLv3 cipher=OTHER); Sun, 23 Sep 2012 17:46:09 -0700 (PDT) Message-ID: <505FAD4D.7080003@gmail.com> Date: Mon, 24 Sep 2012 08:46:05 +0800 From: "Teo En Ming (Zhang Enming)" User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:10.0.2) Gecko/20120216 Thunderbird/10.0.2 MIME-Version: 1.0 To: "xen-users@lists.xen.org" , "xen-devel@lists.xen.org" Content-Type: multipart/mixed; boundary="------------020100030600030809050601" Cc: "Teo En Ming \(Zhang Enming\)" , Frank Lyon Subject: [Xen-users] Is it possible to passthrough 2 GPUs to a single HVM Guest? X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org This is a multi-part message in MIME format. --------------020100030600030809050601 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Hi, I tried working on Frank Lyon's server. With 2 GPUs (NVIDIA Quadro 6000) plugged in, Windows 7 and Windows 8 HVM guests are unable to start. Windows 7 and WIndows 8 HVM guests only manage to start properly when the 2nd GPU is unplugged out of the server. Is this right? This doesn't make sense. Attached are Frank Lyon's xen configuration files. Please advise. Thank you very much. -- Yours sincerely, Mr. Teo En Ming (Zhang Enming) Singapore --------------020100030600030809050601 Content-Type: text/plain; name="40_custom" Content-Transfer-Encoding: 7bit Content-Disposition: attachment; filename="40_custom" #!/bin/sh exec tail -n +3 $0 # This file provides an easy way to add custom menu entries. Simply type the # menu entries you want to add after this comment. Be careful not to change # the 'exec tail' line above. menuentry 'Ubuntu 12.04 amd64 Release with Xen 4.3-unstable and Linux Kernel 3.5.4-xen-frank.lyon-sgp' --class gnu-linux --class gnu --class os { recordfail insmod part_msdos insmod ext2 search --no-floppy --fs-uuid --set=root d5ec6b7f-e1db-4b46-b050-d0bd46403f59 set root='(hd0,msdos1)' search --no-floppy --fs-uuid --set=root d5ec6b7f-e1db-4b46-b050-d0bd46403f59 multiboot /xen.gz module /vmlinuz-3.5.4-xen-frank.lyon-sgp placeholder root=/dev/mapper/snow-root dom0_mem=1024 console=tty quiet splash vt.handoff=7 nomodeset module /initrd.img-3.5.4-xen-frank.lyon-sgp } --------------020100030600030809050601 Content-Type: text/plain; name="grub" Content-Transfer-Encoding: 7bit Content-Disposition: attachment; filename="grub" # If you change this file, run 'update-grub' afterwards to update # /boot/grub/grub.cfg. # For full documentation of the options in this file, see: # info -f grub -n 'Simple configuration' GRUB_DEFAULT=0 #GRUB_HIDDEN_TIMEOUT=0 GRUB_HIDDEN_TIMEOUT_QUIET=true GRUB_TIMEOUT=50 GRUB_DISTRIBUTOR=`lsb_release -i -s 2> /dev/null || echo Debian` GRUB_CMDLINE_LINUX_DEFAULT="" GRUB_CMDLINE_LINUX="nomodeset" # Uncomment to enable BadRAM filtering, modify to suit your needs # This works with Linux (no patch required) and with any kernel that obtains # the memory map information from GRUB (GNU Mach, kernel of FreeBSD ...) #GRUB_BADRAM="0x01234567,0xfefefefe,0x89abcdef,0xefefefef" # Uncomment to disable graphical terminal (grub-pc only) #GRUB_TERMINAL=console # The resolution used on graphical terminal # note that you can use only modes which your graphic card supports via VBE # you can see them in real GRUB with the command `vbeinfo' #GRUB_GFXMODE=640x480 # Uncomment if you don't want GRUB to pass "root=UUID=xxx" parameter to Linux #GRUB_DISABLE_LINUX_UUID=true # Uncomment to disable generation of recovery mode menu entries #GRUB_DISABLE_RECOVERY="true" # Uncomment to get a beep at grub start #GRUB_INIT_TUNE="480 440 1" --------------020100030600030809050601 Content-Type: text/plain; name="rc.local" Content-Transfer-Encoding: 7bit Content-Disposition: attachment; filename="rc.local" #!/bin/sh -e # # rc.local # # This script is executed at the end of each multiuser runlevel. # Make sure that the script will "exit 0" on success or any other # value on error. # # In order to enable or disable this script just change the execution # bits. # # By default this script does nothing. sudo ifconfig eth0 up sudo route add default gw 192.168.25.1 sudo echo "nameserver 192.168.50.15" >> /etc/resolv.conf sudo echo "nameserver 192.168.50.30" >> /etc/resolv.conf exit 0 --------------020100030600030809050601 Content-Type: text/plain; name="start-windows" Content-Transfer-Encoding: 7bit Content-Disposition: attachment; filename="start-windows" #!/bin/sh set -x # #Loads pci-stub kernel module sudo modprobe pci-stub # #Passthrough NVIDIA Quadro 6000 # echo "Passthrough NVIDIA Quadro 6000 VGA card." sudo chmod o+w /sys/bus/pci/drivers/pci-stub/new_id sudo chmod o+w /sys/bus/pci/devices/0000:0d:00.0/driver/unbind sudo chmod o+w /sys/bus/pci/drivers/pci-stub/bind echo "10de 06d8" > /sys/bus/pci/drivers/pci-stub/new_id echo "0000:0d:00.0" > /sys/bus/pci/devices/0000:0d:00.0/driver/unbind echo "0000:0d:00.0" > /sys/bus/pci/drivers/pci-stub/bind # #Passthrough NVIDIA HD Audio Controller # echo "Passthrough NVIDIA HD Audio Controller." sudo chmod o+w /sys/bus/pci/drivers/pci-stub/new_id sudo chmod o+w /sys/bus/pci/devices/0000:0d:00.1/driver/unbind sudo chmod o+w /sys/bus/pci/drivers/pci-stub/bind echo "10de 0be5" > /sys/bus/pci/drivers/pci-stub/new_id echo "0000:0d:00.1" > /sys/bus/pci/devices/0000:0d:00.1/driver/unbind echo "0000:0d:00.1" > /sys/bus/pci/drivers/pci-stub/bind # #Passthrough 2nd NVIDIA Quadro 6000 # #echo "Passthrough 2nd NVIDIA Quadro 6000 VGA card." #sudo chmod o+w /sys/bus/pci/drivers/pci-stub/new_id #sudo chmod o+w /sys/bus/pci/devices/0000:1b:00.0/driver/unbind #sudo chmod o+w /sys/bus/pci/drivers/pci-stub/bind #echo "10de 06d8" > /sys/bus/pci/drivers/pci-stub/new_id #echo "0000:1b:00.0" > /sys/bus/pci/devices/0000:1b:00.0/driver/unbind #echo "0000:1b:00.0" > /sys/bus/pci/drivers/pci-stub/bind # #Passthrough 2nd NVIDIA HD Audio Controller # #echo "Passthrough 2nd NVIDIA HD Audio Controller." #sudo chmod o+w /sys/bus/pci/drivers/pci-stub/new_id #sudo chmod o+w /sys/bus/pci/devices/0000:1b:00.1/driver/unbind #sudo chmod o+w /sys/bus/pci/drivers/pci-stub/bind #echo "10de 0be5" > /sys/bus/pci/drivers/pci-stub/new_id #echo "0000:1b:00.1" > /sys/bus/pci/devices/0000:1b:00.1/driver/unbind #echo "0000:1b:00.1" > /sys/bus/pci/drivers/pci-stub/bind # #Wait for 10 seconds # sleep 10 # #Start Windows HVM domU with VGA Passthrough # sudo xl create /etc/xen/Windows7 #sudo xl create /etc/xen/Windows8 --------------020100030600030809050601 Content-Type: text/plain; name="Windows7" Content-Transfer-Encoding: 7bit Content-Disposition: attachment; filename="Windows7" # XL domain configuration file for Windows 8 Consumer Preview 64-bit English HVM domU # Please refer to "man xl.cfg" for further explanations. # See also docs/misc/xl-network-configuration.markdown and # docs/misc/xl-disk-configuration.txt # Written by Teo En Ming (Zhang Enming) # Email: teo.en.ming@gmail.com # Mobile Phone: +65-8369-2618 # Country: Singapore # Date: 18 Mar 2012 Sun name="Windows8" # Product Key: WJBRX-2N7B2-CCBF6-VPP97-R88XV builder="hvm" vcpus=2 memory=2048 on_poweroff="destroy" on_reboot="restart" on_crash="destroy" disk=[ 'format=raw, vdev=hda, access=rw, target=/etc/xen/images/windows7.img', 'format=raw, vdev=hdc, access=ro, devtype=cdrom, target=/home/flyon/windows7.iso' ] vif=[ 'bridge=eth0,type=ioemu,model=e1000' ] #boot=[c|d|n] # Selects the emulated virtual device to boot from. Options are hard disk (c), cd-rom (d) or network/PXE (n). # Multiple options can be given and will be attempted in the order they are given. e.g. to boot from cd-rom # but fallback to the hard disk you can give dc. The default is cd. boot="dc" acpi=1 #xen_platform_pci=1 #viridian=1 #stdvga=1 vnc=1 vnclisten="192.168.25.50" vncdisplay=0 vncunused=1 vncpasswd="" sdl=0 usb=1 # Passthrough the USB Keyboard usbdevice = "host:04f2:0110" # Passthrough the USB Optical Mouse usbdevice = "host:046d:c03d" # Enable Xen VGA Passthrough gfx_passthru=1 # VGA Passthrough NVIDIA Quadro 6000 and PCI Passthrough NVIDIA HD Audio Controller, then 2nd NVIDIA Quadro 6000 and 2nd NVIDIA HD Audio Controller #pci = [ '0d:00.0','0d:00.1','1b:00.0','1b:00.1' ] pci = [ '0d:00.0','0d:00.1' ] # PCI Passthrough Intel HD Audio Controller. #pci = [ '00:1b.0' ] # PCI Passthrough all the USB Controllers. # pci = [ '00:1a.0','00:1a.1','00:1a.2','00:1a.7','00:1d.0','00:1d.1','00:1d.2','00:1d.7' ] --------------020100030600030809050601 Content-Type: text/plain; name="Windows8" Content-Transfer-Encoding: 7bit Content-Disposition: attachment; filename="Windows8" # XL domain configuration file for Windows 8 Consumer Preview 64-bit English HVM domU # Please refer to "man xl.cfg" for further explanations. # See also docs/misc/xl-network-configuration.markdown and # docs/misc/xl-disk-configuration.txt # Written by Teo En Ming (Zhang Enming) # Email: teo.en.ming@gmail.com # Mobile Phone: +65-8369-2618 # Country: Singapore # Date: 18 Mar 2012 Sun name="Windows8" # Product Key: WJBRX-2N7B2-CCBF6-VPP97-R88XV builder="hvm" vcpus=2 memory=2048 on_poweroff="destroy" on_reboot="restart" on_crash="destroy" disk=[ 'format=raw, vdev=hda, access=rw, target=/etc/xen/images/windows8.img', 'format=raw, vdev=hdc, access=ro, devtype=cdrom, target=/home/flyon/windows8.iso' ] vif=[ 'bridge=eth0,type=ioemu,model=e1000' ] #boot=[c|d|n] # Selects the emulated virtual device to boot from. Options are hard disk (c), cd-rom (d) or network/PXE (n). # Multiple options can be given and will be attempted in the order they are given. e.g. to boot from cd-rom # but fallback to the hard disk you can give dc. The default is cd. boot="dc" acpi=1 #xen_platform_pci=1 #viridian=1 #stdvga=1 vnc=1 vnclisten="192.168.25.50" vncdisplay=0 vncunused=1 vncpasswd="" sdl=0 usb=1 # Passthrough the USB Keyboard usbdevice = "host:04f2:0110" # Passthrough the USB Optical Mouse usbdevice = "host:046d:c03d" # Enable Xen VGA Passthrough gfx_passthru=1 # VGA Passthrough NVIDIA Quadro 6000 and PCI Passthrough NVIDIA HD Audio Controller, then 2nd NVIDIA Quadro 6000 and 2nd NVIDIA HD Audio Controller #pci = [ '0d:00.0','0d:00.1','1b:00.0','1b:00.1' ] pci = [ '0d:00.0','0d:00.1' ] # PCI Passthrough Intel HD Audio Controller. #pci = [ '00:1b.0' ] # PCI Passthrough all the USB Controllers. # pci = [ '00:1a.0','00:1a.1','00:1a.2','00:1a.7','00:1d.0','00:1d.1','00:1d.2','00:1d.7' ] --------------020100030600030809050601 Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users --------------020100030600030809050601-- From xen-users-bounces@lists.xen.org Mon Sep 24 00:47:51 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Mon, 24 Sep 2012 00:47:51 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TFwoT-0003m5-5A; Mon, 24 Sep 2012 00:46:17 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TFwoR-0003lp-8L for xen-users@lists.xen.org; Mon, 24 Sep 2012 00:46:15 +0000 Received: from [85.158.143.99:18885] by server-1.bemta-4.messagelabs.com id A1/16-05684-55DAF505; Mon, 24 Sep 2012 00:46:13 +0000 X-Env-Sender: singapore.mr.teo.en.ming@gmail.com X-Msg-Ref: server-5.tower-216.messagelabs.com!1348447570!31132103!1 X-Originating-IP: [209.85.160.45] X-SpamReason: No, hits=0.3 required=7.0 tests=ML_RADAR_SPEW_LINKS_14, RCVD_BY_IP,spamassassin: X-StarScan-Received: X-StarScan-Version: 6.6.1.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 13177 invoked from network); 24 Sep 2012 00:46:12 -0000 Received: from mail-pb0-f45.google.com (HELO mail-pb0-f45.google.com) (209.85.160.45) by server-5.tower-216.messagelabs.com with RC4-SHA encrypted SMTP; 24 Sep 2012 00:46:12 -0000 Received: by pbbrp2 with SMTP id rp2so212129pbb.32 for ; Sun, 23 Sep 2012 17:46:10 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:disposition-notification-to:date:from:user-agent :mime-version:to:cc:subject:content-type; bh=lDa7xU0tYQvz8mVL8LJtMHJUs0aI9It4xoMFwFlJBLo=; b=zGP8pqqzT4KWLWC8TiFyOuXzgfQVg6rIo44XqU+QJBK6G81EttXEMDRJ9Bo1hPgYMJ c3drj/yG3QE2UkNbXh+zbCTkQ2QxH88peZxsCsZ9kUBkUqNxk8QXcG8Y9UvShJ2Xywjv zrOiKp0u2mIi9XgE2o9YRnFCJnzbIXT1flZElrIm3sCcv+p7AW0ZCFdNKOBSO4y9lJw6 CHMZQlHriwl3XJ7ZuqeHLjxjrlMrZD32lfGOddRVzzE0IqLVDImKz8uqYmyLIlslhDJj bgL0lfeNQ8L03JPZdjv49QMziAR+ddab6TSS/ed6xRNXwx7cbo7/MEVzW1WjwqY3kNxS QQ8g== Received: by 10.66.87.105 with SMTP id w9mr3338017paz.5.1348447569994; Sun, 23 Sep 2012 17:46:09 -0700 (PDT) Received: from [192.168.1.2] (cm141.gamma206.maxonline.com.sg. [202.156.206.141]) by mx.google.com with ESMTPS id h10sm4630762pav.28.2012.09.23.17.46.07 (version=SSLv3 cipher=OTHER); Sun, 23 Sep 2012 17:46:09 -0700 (PDT) Message-ID: <505FAD4D.7080003@gmail.com> Date: Mon, 24 Sep 2012 08:46:05 +0800 From: "Teo En Ming (Zhang Enming)" User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:10.0.2) Gecko/20120216 Thunderbird/10.0.2 MIME-Version: 1.0 To: "xen-users@lists.xen.org" , "xen-devel@lists.xen.org" Content-Type: multipart/mixed; boundary="------------020100030600030809050601" Cc: "Teo En Ming \(Zhang Enming\)" , Frank Lyon Subject: [Xen-users] Is it possible to passthrough 2 GPUs to a single HVM Guest? X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org This is a multi-part message in MIME format. --------------020100030600030809050601 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Hi, I tried working on Frank Lyon's server. With 2 GPUs (NVIDIA Quadro 6000) plugged in, Windows 7 and Windows 8 HVM guests are unable to start. Windows 7 and WIndows 8 HVM guests only manage to start properly when the 2nd GPU is unplugged out of the server. Is this right? This doesn't make sense. Attached are Frank Lyon's xen configuration files. Please advise. Thank you very much. -- Yours sincerely, Mr. Teo En Ming (Zhang Enming) Singapore --------------020100030600030809050601 Content-Type: text/plain; name="40_custom" Content-Transfer-Encoding: 7bit Content-Disposition: attachment; filename="40_custom" #!/bin/sh exec tail -n +3 $0 # This file provides an easy way to add custom menu entries. Simply type the # menu entries you want to add after this comment. Be careful not to change # the 'exec tail' line above. menuentry 'Ubuntu 12.04 amd64 Release with Xen 4.3-unstable and Linux Kernel 3.5.4-xen-frank.lyon-sgp' --class gnu-linux --class gnu --class os { recordfail insmod part_msdos insmod ext2 search --no-floppy --fs-uuid --set=root d5ec6b7f-e1db-4b46-b050-d0bd46403f59 set root='(hd0,msdos1)' search --no-floppy --fs-uuid --set=root d5ec6b7f-e1db-4b46-b050-d0bd46403f59 multiboot /xen.gz module /vmlinuz-3.5.4-xen-frank.lyon-sgp placeholder root=/dev/mapper/snow-root dom0_mem=1024 console=tty quiet splash vt.handoff=7 nomodeset module /initrd.img-3.5.4-xen-frank.lyon-sgp } --------------020100030600030809050601 Content-Type: text/plain; name="grub" Content-Transfer-Encoding: 7bit Content-Disposition: attachment; filename="grub" # If you change this file, run 'update-grub' afterwards to update # /boot/grub/grub.cfg. # For full documentation of the options in this file, see: # info -f grub -n 'Simple configuration' GRUB_DEFAULT=0 #GRUB_HIDDEN_TIMEOUT=0 GRUB_HIDDEN_TIMEOUT_QUIET=true GRUB_TIMEOUT=50 GRUB_DISTRIBUTOR=`lsb_release -i -s 2> /dev/null || echo Debian` GRUB_CMDLINE_LINUX_DEFAULT="" GRUB_CMDLINE_LINUX="nomodeset" # Uncomment to enable BadRAM filtering, modify to suit your needs # This works with Linux (no patch required) and with any kernel that obtains # the memory map information from GRUB (GNU Mach, kernel of FreeBSD ...) #GRUB_BADRAM="0x01234567,0xfefefefe,0x89abcdef,0xefefefef" # Uncomment to disable graphical terminal (grub-pc only) #GRUB_TERMINAL=console # The resolution used on graphical terminal # note that you can use only modes which your graphic card supports via VBE # you can see them in real GRUB with the command `vbeinfo' #GRUB_GFXMODE=640x480 # Uncomment if you don't want GRUB to pass "root=UUID=xxx" parameter to Linux #GRUB_DISABLE_LINUX_UUID=true # Uncomment to disable generation of recovery mode menu entries #GRUB_DISABLE_RECOVERY="true" # Uncomment to get a beep at grub start #GRUB_INIT_TUNE="480 440 1" --------------020100030600030809050601 Content-Type: text/plain; name="rc.local" Content-Transfer-Encoding: 7bit Content-Disposition: attachment; filename="rc.local" #!/bin/sh -e # # rc.local # # This script is executed at the end of each multiuser runlevel. # Make sure that the script will "exit 0" on success or any other # value on error. # # In order to enable or disable this script just change the execution # bits. # # By default this script does nothing. sudo ifconfig eth0 up sudo route add default gw 192.168.25.1 sudo echo "nameserver 192.168.50.15" >> /etc/resolv.conf sudo echo "nameserver 192.168.50.30" >> /etc/resolv.conf exit 0 --------------020100030600030809050601 Content-Type: text/plain; name="start-windows" Content-Transfer-Encoding: 7bit Content-Disposition: attachment; filename="start-windows" #!/bin/sh set -x # #Loads pci-stub kernel module sudo modprobe pci-stub # #Passthrough NVIDIA Quadro 6000 # echo "Passthrough NVIDIA Quadro 6000 VGA card." sudo chmod o+w /sys/bus/pci/drivers/pci-stub/new_id sudo chmod o+w /sys/bus/pci/devices/0000:0d:00.0/driver/unbind sudo chmod o+w /sys/bus/pci/drivers/pci-stub/bind echo "10de 06d8" > /sys/bus/pci/drivers/pci-stub/new_id echo "0000:0d:00.0" > /sys/bus/pci/devices/0000:0d:00.0/driver/unbind echo "0000:0d:00.0" > /sys/bus/pci/drivers/pci-stub/bind # #Passthrough NVIDIA HD Audio Controller # echo "Passthrough NVIDIA HD Audio Controller." sudo chmod o+w /sys/bus/pci/drivers/pci-stub/new_id sudo chmod o+w /sys/bus/pci/devices/0000:0d:00.1/driver/unbind sudo chmod o+w /sys/bus/pci/drivers/pci-stub/bind echo "10de 0be5" > /sys/bus/pci/drivers/pci-stub/new_id echo "0000:0d:00.1" > /sys/bus/pci/devices/0000:0d:00.1/driver/unbind echo "0000:0d:00.1" > /sys/bus/pci/drivers/pci-stub/bind # #Passthrough 2nd NVIDIA Quadro 6000 # #echo "Passthrough 2nd NVIDIA Quadro 6000 VGA card." #sudo chmod o+w /sys/bus/pci/drivers/pci-stub/new_id #sudo chmod o+w /sys/bus/pci/devices/0000:1b:00.0/driver/unbind #sudo chmod o+w /sys/bus/pci/drivers/pci-stub/bind #echo "10de 06d8" > /sys/bus/pci/drivers/pci-stub/new_id #echo "0000:1b:00.0" > /sys/bus/pci/devices/0000:1b:00.0/driver/unbind #echo "0000:1b:00.0" > /sys/bus/pci/drivers/pci-stub/bind # #Passthrough 2nd NVIDIA HD Audio Controller # #echo "Passthrough 2nd NVIDIA HD Audio Controller." #sudo chmod o+w /sys/bus/pci/drivers/pci-stub/new_id #sudo chmod o+w /sys/bus/pci/devices/0000:1b:00.1/driver/unbind #sudo chmod o+w /sys/bus/pci/drivers/pci-stub/bind #echo "10de 0be5" > /sys/bus/pci/drivers/pci-stub/new_id #echo "0000:1b:00.1" > /sys/bus/pci/devices/0000:1b:00.1/driver/unbind #echo "0000:1b:00.1" > /sys/bus/pci/drivers/pci-stub/bind # #Wait for 10 seconds # sleep 10 # #Start Windows HVM domU with VGA Passthrough # sudo xl create /etc/xen/Windows7 #sudo xl create /etc/xen/Windows8 --------------020100030600030809050601 Content-Type: text/plain; name="Windows7" Content-Transfer-Encoding: 7bit Content-Disposition: attachment; filename="Windows7" # XL domain configuration file for Windows 8 Consumer Preview 64-bit English HVM domU # Please refer to "man xl.cfg" for further explanations. # See also docs/misc/xl-network-configuration.markdown and # docs/misc/xl-disk-configuration.txt # Written by Teo En Ming (Zhang Enming) # Email: teo.en.ming@gmail.com # Mobile Phone: +65-8369-2618 # Country: Singapore # Date: 18 Mar 2012 Sun name="Windows8" # Product Key: WJBRX-2N7B2-CCBF6-VPP97-R88XV builder="hvm" vcpus=2 memory=2048 on_poweroff="destroy" on_reboot="restart" on_crash="destroy" disk=[ 'format=raw, vdev=hda, access=rw, target=/etc/xen/images/windows7.img', 'format=raw, vdev=hdc, access=ro, devtype=cdrom, target=/home/flyon/windows7.iso' ] vif=[ 'bridge=eth0,type=ioemu,model=e1000' ] #boot=[c|d|n] # Selects the emulated virtual device to boot from. Options are hard disk (c), cd-rom (d) or network/PXE (n). # Multiple options can be given and will be attempted in the order they are given. e.g. to boot from cd-rom # but fallback to the hard disk you can give dc. The default is cd. boot="dc" acpi=1 #xen_platform_pci=1 #viridian=1 #stdvga=1 vnc=1 vnclisten="192.168.25.50" vncdisplay=0 vncunused=1 vncpasswd="" sdl=0 usb=1 # Passthrough the USB Keyboard usbdevice = "host:04f2:0110" # Passthrough the USB Optical Mouse usbdevice = "host:046d:c03d" # Enable Xen VGA Passthrough gfx_passthru=1 # VGA Passthrough NVIDIA Quadro 6000 and PCI Passthrough NVIDIA HD Audio Controller, then 2nd NVIDIA Quadro 6000 and 2nd NVIDIA HD Audio Controller #pci = [ '0d:00.0','0d:00.1','1b:00.0','1b:00.1' ] pci = [ '0d:00.0','0d:00.1' ] # PCI Passthrough Intel HD Audio Controller. #pci = [ '00:1b.0' ] # PCI Passthrough all the USB Controllers. # pci = [ '00:1a.0','00:1a.1','00:1a.2','00:1a.7','00:1d.0','00:1d.1','00:1d.2','00:1d.7' ] --------------020100030600030809050601 Content-Type: text/plain; name="Windows8" Content-Transfer-Encoding: 7bit Content-Disposition: attachment; filename="Windows8" # XL domain configuration file for Windows 8 Consumer Preview 64-bit English HVM domU # Please refer to "man xl.cfg" for further explanations. # See also docs/misc/xl-network-configuration.markdown and # docs/misc/xl-disk-configuration.txt # Written by Teo En Ming (Zhang Enming) # Email: teo.en.ming@gmail.com # Mobile Phone: +65-8369-2618 # Country: Singapore # Date: 18 Mar 2012 Sun name="Windows8" # Product Key: WJBRX-2N7B2-CCBF6-VPP97-R88XV builder="hvm" vcpus=2 memory=2048 on_poweroff="destroy" on_reboot="restart" on_crash="destroy" disk=[ 'format=raw, vdev=hda, access=rw, target=/etc/xen/images/windows8.img', 'format=raw, vdev=hdc, access=ro, devtype=cdrom, target=/home/flyon/windows8.iso' ] vif=[ 'bridge=eth0,type=ioemu,model=e1000' ] #boot=[c|d|n] # Selects the emulated virtual device to boot from. Options are hard disk (c), cd-rom (d) or network/PXE (n). # Multiple options can be given and will be attempted in the order they are given. e.g. to boot from cd-rom # but fallback to the hard disk you can give dc. The default is cd. boot="dc" acpi=1 #xen_platform_pci=1 #viridian=1 #stdvga=1 vnc=1 vnclisten="192.168.25.50" vncdisplay=0 vncunused=1 vncpasswd="" sdl=0 usb=1 # Passthrough the USB Keyboard usbdevice = "host:04f2:0110" # Passthrough the USB Optical Mouse usbdevice = "host:046d:c03d" # Enable Xen VGA Passthrough gfx_passthru=1 # VGA Passthrough NVIDIA Quadro 6000 and PCI Passthrough NVIDIA HD Audio Controller, then 2nd NVIDIA Quadro 6000 and 2nd NVIDIA HD Audio Controller #pci = [ '0d:00.0','0d:00.1','1b:00.0','1b:00.1' ] pci = [ '0d:00.0','0d:00.1' ] # PCI Passthrough Intel HD Audio Controller. #pci = [ '00:1b.0' ] # PCI Passthrough all the USB Controllers. # pci = [ '00:1a.0','00:1a.1','00:1a.2','00:1a.7','00:1d.0','00:1d.1','00:1d.2','00:1d.7' ] --------------020100030600030809050601 Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users --------------020100030600030809050601-- From xen-users-bounces@lists.xen.org Mon Sep 24 00:51:20 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Mon, 24 Sep 2012 00:51:20 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TFwsG-000439-Im; Mon, 24 Sep 2012 00:50:12 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TFwsF-00042m-AS for xen-users@lists.xen.org; Mon, 24 Sep 2012 00:50:11 +0000 Received: from [85.158.137.99:11037] by server-14.bemta-3.messagelabs.com id CE/B8-21431-14EAF505; Mon, 24 Sep 2012 00:50:09 +0000 X-Env-Sender: singapore.mr.teo.en.ming@gmail.com X-Msg-Ref: server-16.tower-217.messagelabs.com!1348447806!18817323!1 X-Originating-IP: [209.85.160.45] X-SpamReason: No, hits=0.3 required=7.0 tests=ML_RADAR_SPEW_LINKS_14, RCVD_BY_IP,spamassassin: X-StarScan-Received: X-StarScan-Version: 6.6.1.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 22296 invoked from network); 24 Sep 2012 00:50:08 -0000 Received: from mail-pb0-f45.google.com (HELO mail-pb0-f45.google.com) (209.85.160.45) by server-16.tower-217.messagelabs.com with RC4-SHA encrypted SMTP; 24 Sep 2012 00:50:08 -0000 Received: by pbbrp2 with SMTP id rp2so215787pbb.32 for ; Sun, 23 Sep 2012 17:50:06 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:disposition-notification-to:date:from:user-agent :mime-version:to:subject:references:in-reply-to:content-type :content-transfer-encoding; bh=xnZdvFW4bOHRYUPjCUeddA7ukaQDpy0bamG1qwooBtw=; b=PKg7Z9Ay4NhAF/018wwcGe927hs2FMMz9+sZdBOOuUJVDkCYTw512Ph/Ha4SXbAyQR 3WEcyINMVyPp9m7kqR/24FaOgcJXwsy7NnLSKynWh2hfAVFaDmdIx/Dzx3jEvlES0JlA AEP9W2ycy+jImkr9uAnhXPCuA4S0nuqWRAx0ONjc04EMdYXBqwSgQrBDLcm0C6uNkQar SgptVMwyZyv46IFwzix57Igr3E1MMshyvtnx6u4BsPx3AXd8D2BSOqrbiLrCEws/rm2p S4lF5UCi4xLOZofKViDyqSF0B2oYF5/DCLEGOPC1XskPBAuTmNXmyIhiOKWiBVjphgn0 JHyw== Received: by 10.68.201.104 with SMTP id jz8mr32806234pbc.141.1348447806323; Sun, 23 Sep 2012 17:50:06 -0700 (PDT) Received: from [192.168.1.2] (cm141.gamma206.maxonline.com.sg. [202.156.206.141]) by mx.google.com with ESMTPS id nz6sm895271pbb.50.2012.09.23.17.50.04 (version=SSLv3 cipher=OTHER); Sun, 23 Sep 2012 17:50:05 -0700 (PDT) Message-ID: <505FAE3A.5030109@gmail.com> Date: Mon, 24 Sep 2012 08:50:02 +0800 From: "Teo En Ming (Zhang Enming)" User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:10.0.2) Gecko/20120216 Thunderbird/10.0.2 MIME-Version: 1.0 To: "xen-users@lists.xen.org" , "xen-devel@lists.xen.org" , "Teo En Ming (Zhang Enming)" , Frank Lyon References: <5059F632.3050808@gmail.com> In-Reply-To: <5059F632.3050808@gmail.com> Subject: Re: [Xen-users] VGA Passthrough with Xen 4.3-unstable? X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset="us-ascii"; Format="flowed" Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org On 20/09/2012 00:43, Teo En Ming (Zhang Enming) wrote: > Dear All, > > I have tried to apply VGA passthrough patches hosted at Jean David > Techer's website to Xen 4.3-unstable. However, I cannot get VGA > passthrough to work with Xen 4.3-unstable. Are the VGA passthrough > patches hosted at David Techer's website incompatible with Xen > 4.3-unstable? > > This is David Techer's website: > http://www.davidgis.fr/blog/index.php?2011/12/07/860-xen-42unstable-patches-for-vga-pass-through > > I have also provided error logs in this email for troubleshooting > purposes. > > Please advise. Thank you very much. > Hi Guys, I have found out that VGA Passthrough doesn't work with Xen 4.3-unstable. But VGA Passthrough worked with Xen 4.2-unstable changeset 25099. -- Yours sincerely, Mr. Teo En Ming (Zhang Enming) Singapore _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Mon Sep 24 00:51:20 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Mon, 24 Sep 2012 00:51:20 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TFwsG-000439-Im; Mon, 24 Sep 2012 00:50:12 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TFwsF-00042m-AS for xen-users@lists.xen.org; Mon, 24 Sep 2012 00:50:11 +0000 Received: from [85.158.137.99:11037] by server-14.bemta-3.messagelabs.com id CE/B8-21431-14EAF505; Mon, 24 Sep 2012 00:50:09 +0000 X-Env-Sender: singapore.mr.teo.en.ming@gmail.com X-Msg-Ref: server-16.tower-217.messagelabs.com!1348447806!18817323!1 X-Originating-IP: [209.85.160.45] X-SpamReason: No, hits=0.3 required=7.0 tests=ML_RADAR_SPEW_LINKS_14, RCVD_BY_IP,spamassassin: X-StarScan-Received: X-StarScan-Version: 6.6.1.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 22296 invoked from network); 24 Sep 2012 00:50:08 -0000 Received: from mail-pb0-f45.google.com (HELO mail-pb0-f45.google.com) (209.85.160.45) by server-16.tower-217.messagelabs.com with RC4-SHA encrypted SMTP; 24 Sep 2012 00:50:08 -0000 Received: by pbbrp2 with SMTP id rp2so215787pbb.32 for ; Sun, 23 Sep 2012 17:50:06 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:disposition-notification-to:date:from:user-agent :mime-version:to:subject:references:in-reply-to:content-type :content-transfer-encoding; bh=xnZdvFW4bOHRYUPjCUeddA7ukaQDpy0bamG1qwooBtw=; b=PKg7Z9Ay4NhAF/018wwcGe927hs2FMMz9+sZdBOOuUJVDkCYTw512Ph/Ha4SXbAyQR 3WEcyINMVyPp9m7kqR/24FaOgcJXwsy7NnLSKynWh2hfAVFaDmdIx/Dzx3jEvlES0JlA AEP9W2ycy+jImkr9uAnhXPCuA4S0nuqWRAx0ONjc04EMdYXBqwSgQrBDLcm0C6uNkQar SgptVMwyZyv46IFwzix57Igr3E1MMshyvtnx6u4BsPx3AXd8D2BSOqrbiLrCEws/rm2p S4lF5UCi4xLOZofKViDyqSF0B2oYF5/DCLEGOPC1XskPBAuTmNXmyIhiOKWiBVjphgn0 JHyw== Received: by 10.68.201.104 with SMTP id jz8mr32806234pbc.141.1348447806323; Sun, 23 Sep 2012 17:50:06 -0700 (PDT) Received: from [192.168.1.2] (cm141.gamma206.maxonline.com.sg. [202.156.206.141]) by mx.google.com with ESMTPS id nz6sm895271pbb.50.2012.09.23.17.50.04 (version=SSLv3 cipher=OTHER); Sun, 23 Sep 2012 17:50:05 -0700 (PDT) Message-ID: <505FAE3A.5030109@gmail.com> Date: Mon, 24 Sep 2012 08:50:02 +0800 From: "Teo En Ming (Zhang Enming)" User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:10.0.2) Gecko/20120216 Thunderbird/10.0.2 MIME-Version: 1.0 To: "xen-users@lists.xen.org" , "xen-devel@lists.xen.org" , "Teo En Ming (Zhang Enming)" , Frank Lyon References: <5059F632.3050808@gmail.com> In-Reply-To: <5059F632.3050808@gmail.com> Subject: Re: [Xen-users] VGA Passthrough with Xen 4.3-unstable? X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset="us-ascii"; Format="flowed" Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org On 20/09/2012 00:43, Teo En Ming (Zhang Enming) wrote: > Dear All, > > I have tried to apply VGA passthrough patches hosted at Jean David > Techer's website to Xen 4.3-unstable. However, I cannot get VGA > passthrough to work with Xen 4.3-unstable. Are the VGA passthrough > patches hosted at David Techer's website incompatible with Xen > 4.3-unstable? > > This is David Techer's website: > http://www.davidgis.fr/blog/index.php?2011/12/07/860-xen-42unstable-patches-for-vga-pass-through > > I have also provided error logs in this email for troubleshooting > purposes. > > Please advise. Thank you very much. > Hi Guys, I have found out that VGA Passthrough doesn't work with Xen 4.3-unstable. But VGA Passthrough worked with Xen 4.2-unstable changeset 25099. -- Yours sincerely, Mr. Teo En Ming (Zhang Enming) Singapore _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Mon Sep 24 02:08:36 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Mon, 24 Sep 2012 02:08:36 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TFy4p-0000jH-23; Mon, 24 Sep 2012 02:07:15 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TFy4n-0000jC-PH for xen-users@lists.xen.org; Mon, 24 Sep 2012 02:07:13 +0000 Received: from [85.158.143.35:5456] by server-2.bemta-4.messagelabs.com id 5C/4E-06610-050CF505; Mon, 24 Sep 2012 02:07:12 +0000 X-Env-Sender: robert@digitalsilk.net X-Msg-Ref: server-10.tower-21.messagelabs.com!1348452431!10155293!1 X-Originating-IP: [68.65.40.30] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: QmFkIElQOiA2OC42NS40MC4zMCA9PiAzNDM3Mg==\n,sa_preprocessor: QmFkIElQOiA2OC42NS40MC4zMCA9PiAzNDM3Mg==\n X-StarScan-Received: X-StarScan-Version: 6.6.1.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 21507 invoked from network); 24 Sep 2012 02:07:12 -0000 Received: from rci1.airstreamcomm.net (HELO rci1.airstreamcomm.net) (68.65.40.30) by server-10.tower-21.messagelabs.com with SMTP; 24 Sep 2012 02:07:12 -0000 Received: from osmtp-3.airstreamcomm.net ([64.33.128.247]) by rci1.airstreamcomm.net ({b41767c8-05d3-412c-bba5-a032a1ad4739}) via TCP (outbound) with ESMTP id 20120924020711397 for ; Mon, 24 Sep 2012 02:07:11 +0000 X-RC-FROM: X-RC-RCPT: Received: from bilbo.digitalsilk.net (bal-bb-static3-cisco-ws-20.dsl.airstreamcomm.net [208.157.175.245]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by osmtp-3.airstreamcomm.net (Postfix) with ESMTPS id 8609B77C for ; Sun, 23 Sep 2012 21:07:10 -0500 (CDT) Received: by bilbo.digitalsilk.net (Postfix, from userid 1001) id 9368A1792F; Sun, 23 Sep 2012 21:07:08 -0500 (CDT) X-Spam-Checker-Version: SpamAssassin 3.3.2 (2011-06-06) on bilbo X-Spam-Status: No, hits=-1.0 required=3.0 tests=ALL_TRUSTED X-Spam-Level: Received: from bunsen-wifi.digitalsilk.lan (link.digitalsilk.lan [192.168.2.254]) by bilbo.digitalsilk.net (Postfix) with ESMTP id 75C291792C for ; Sun, 23 Sep 2012 21:07:08 -0500 (CDT) Message-ID: <505FC055.4060004@digitalsilk.net> Date: Sun, 23 Sep 2012 21:07:17 -0500 From: Robert Rust User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:15.0) Gecko/20120907 Thunderbird/15.0.1 MIME-Version: 1.0 To: xen-users@lists.xen.org X-MAG-OUTBOUND: airstream.redcondor.net@64.33.128.240/28 Subject: [Xen-users] can't pass pair of PCI cards to single domU X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset="us-ascii"; Format="flowed" Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org Folks - Any ideas on why I can't pass a pair of HVR-1600 PCI cards to a single DomU? When I try, only a single one shows up. I can pass them to separate DomUs (though I'm having problems getting the one in the second DomU to capture properly, it does show up and gets recognized by the driver for it). Distro: Ubuntu 12.04.1 LTS Kernel: ubuntu stock 3.2.0-31-generic #50 xen: from ubuntu - 4.1.2-2 Any additional information that would be helpful? -Robert _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Mon Sep 24 02:08:36 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Mon, 24 Sep 2012 02:08:36 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TFy4p-0000jH-23; Mon, 24 Sep 2012 02:07:15 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TFy4n-0000jC-PH for xen-users@lists.xen.org; Mon, 24 Sep 2012 02:07:13 +0000 Received: from [85.158.143.35:5456] by server-2.bemta-4.messagelabs.com id 5C/4E-06610-050CF505; Mon, 24 Sep 2012 02:07:12 +0000 X-Env-Sender: robert@digitalsilk.net X-Msg-Ref: server-10.tower-21.messagelabs.com!1348452431!10155293!1 X-Originating-IP: [68.65.40.30] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: QmFkIElQOiA2OC42NS40MC4zMCA9PiAzNDM3Mg==\n,sa_preprocessor: QmFkIElQOiA2OC42NS40MC4zMCA9PiAzNDM3Mg==\n X-StarScan-Received: X-StarScan-Version: 6.6.1.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 21507 invoked from network); 24 Sep 2012 02:07:12 -0000 Received: from rci1.airstreamcomm.net (HELO rci1.airstreamcomm.net) (68.65.40.30) by server-10.tower-21.messagelabs.com with SMTP; 24 Sep 2012 02:07:12 -0000 Received: from osmtp-3.airstreamcomm.net ([64.33.128.247]) by rci1.airstreamcomm.net ({b41767c8-05d3-412c-bba5-a032a1ad4739}) via TCP (outbound) with ESMTP id 20120924020711397 for ; Mon, 24 Sep 2012 02:07:11 +0000 X-RC-FROM: X-RC-RCPT: Received: from bilbo.digitalsilk.net (bal-bb-static3-cisco-ws-20.dsl.airstreamcomm.net [208.157.175.245]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by osmtp-3.airstreamcomm.net (Postfix) with ESMTPS id 8609B77C for ; Sun, 23 Sep 2012 21:07:10 -0500 (CDT) Received: by bilbo.digitalsilk.net (Postfix, from userid 1001) id 9368A1792F; Sun, 23 Sep 2012 21:07:08 -0500 (CDT) X-Spam-Checker-Version: SpamAssassin 3.3.2 (2011-06-06) on bilbo X-Spam-Status: No, hits=-1.0 required=3.0 tests=ALL_TRUSTED X-Spam-Level: Received: from bunsen-wifi.digitalsilk.lan (link.digitalsilk.lan [192.168.2.254]) by bilbo.digitalsilk.net (Postfix) with ESMTP id 75C291792C for ; Sun, 23 Sep 2012 21:07:08 -0500 (CDT) Message-ID: <505FC055.4060004@digitalsilk.net> Date: Sun, 23 Sep 2012 21:07:17 -0500 From: Robert Rust User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:15.0) Gecko/20120907 Thunderbird/15.0.1 MIME-Version: 1.0 To: xen-users@lists.xen.org X-MAG-OUTBOUND: airstream.redcondor.net@64.33.128.240/28 Subject: [Xen-users] can't pass pair of PCI cards to single domU X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset="us-ascii"; Format="flowed" Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org Folks - Any ideas on why I can't pass a pair of HVR-1600 PCI cards to a single DomU? When I try, only a single one shows up. I can pass them to separate DomUs (though I'm having problems getting the one in the second DomU to capture properly, it does show up and gets recognized by the driver for it). Distro: Ubuntu 12.04.1 LTS Kernel: ubuntu stock 3.2.0-31-generic #50 xen: from ubuntu - 4.1.2-2 Any additional information that would be helpful? -Robert _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Mon Sep 24 03:30:12 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Mon, 24 Sep 2012 03:30:12 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TFzLq-0001sG-1f; Mon, 24 Sep 2012 03:28:54 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TFzLn-0001sB-RM for xen-users@lists.xen.org; Mon, 24 Sep 2012 03:28:52 +0000 Received: from [85.158.138.51:31948] by server-6.bemta-3.messagelabs.com id 5E/1D-29694-273DF505; Mon, 24 Sep 2012 03:28:50 +0000 X-Env-Sender: jaceksburghardt@gmail.com X-Msg-Ref: server-4.tower-174.messagelabs.com!1348457328!31183559!1 X-Originating-IP: [209.85.216.173] X-SpamReason: No, hits=1.2 required=7.0 tests=HTML_20_30,HTML_MESSAGE, ML_RADAR_SPEW_LINKS_14,RCVD_BY_IP,spamassassin: X-StarScan-Received: X-StarScan-Version: 6.6.1.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 1493 invoked from network); 24 Sep 2012 03:28:49 -0000 Received: from mail-qc0-f173.google.com (HELO mail-qc0-f173.google.com) (209.85.216.173) by server-4.tower-174.messagelabs.com with RC4-SHA encrypted SMTP; 24 Sep 2012 03:28:49 -0000 Received: by qcab12 with SMTP id b12so984745qca.32 for ; Sun, 23 Sep 2012 20:28:48 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:date:message-id:subject:from:to:content-type; bh=RHtHSW4dSsiywGSjz88Sfd6Pv/okAwtQheujy+I8MSY=; b=FPwUZjh78DgPZUBvLoko4XYL8u7Zwqz4LuNPqKrk9NhC33iiEVpXHYNrTjp0DDvUJG Sk62R+B7Zy3lqNPOsNAeDpclTcDpT7Hx0FnjbRRVZt96zFdf8ef0m4H9c14KFO73HPKO IHsS1JTmGzU64iogsz5lVjwNAcV/nQsLf5W2w4a+/nELLx/yxBWTBionXBb31qXuGtJ4 /hkNfLNShmYdQ2pVcybgZVoz+pcrWZ1/KSTl9vxk0ZcvOjRr7aJSd9e0Pm1mOztfaXlN j29miUKXM8cSxWSOpmUGwPCAxMK5nJCNmONYsBD6KjJmQc1HnpkAMlsmvdZrJV2FQPkP wAZA== MIME-Version: 1.0 Received: by 10.224.180.7 with SMTP id bs7mr29465018qab.37.1348457328215; Sun, 23 Sep 2012 20:28:48 -0700 (PDT) Received: by 10.49.118.101 with HTTP; Sun, 23 Sep 2012 20:28:48 -0700 (PDT) Date: Sun, 23 Sep 2012 21:28:48 -0600 Message-ID: From: jacek burghardt To: xen-users Subject: [Xen-users] server2008rebooting trouble X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============8563744280894467503==" Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org --===============8563744280894467503== Content-Type: multipart/alternative; boundary=20cf302efcd60b060604ca6a3095 --20cf302efcd60b060604ca6a3095 Content-Type: text/plain; charset=ISO-8859-1 I have servers 2008 running on xen 4.2 and 4.3 and the instances will never reboot. Option vcpu=1 will cause freeze on erebbot server 2008 will display shooting down unlese I use xl destroy and then create. When I removed vcpu=1 I get black screen with cursor. I hope someone can help me fix this as any update will cause frozen instance. builder = 'hvm' device_model_version= 'qemu-xen-traditional' viridian = 1 memory = 768 # Should be at least 2KB per MB of domain memory, plus a few MB per vcpu. shadow_memory = 8 name = "win2008c" vif = ['type=ioemu,bridge=xenbr0,model=e1000,script=vif-bridge'] acpi = 1 apic = 1 pae = 1 xen_platform_pci=1 tsc_mode='default' xen_extended_power_mgmt=0 disk = [ 'phy:/dev/volxen/win2008c,xvda,w', 'file:/home/xen/iso/en_visio_2010.iso,xvdc:cdrom,r' ] #----------------------------------------------------------------------------- # boot on floppy (a), hard disk (c) or CD-ROM (d) # default: hard disk, cd-rom, floppy boot="dc" sdl=0 stdvga = 1 serial = 'pty' localtime=1 vnc=1 vncconsole=1 vncpasswd='' vnclisten = '0.0.0.0' vncviewer = 1 on_poweroff = 'destroy' on_reboot = 'restart' on_crash = 'restart' monitor = 1 usb = 1 usbtablet = 1 usbdevice='tablet' --20cf302efcd60b060604ca6a3095 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable I have servers 2008 running on xen 4.2 and 4.3=A0 and the instances will ne= ver reboot. Option vcpu=3D1 will cause freeze on erebbot server 2008 will d= isplay shooting down unlese I use xl destroy and then create. When I remove= d vcpu=3D1 I get black screen with cursor.
I hope someone can help me fix this as any update will cause frozen instanc= e.

builder =3D 'hvm'
device_model_v=
ersion=3D 'qemu-xen-traditional'
viridian =3D 1
memory =3D  7=
68


# Should be at least 2KB per MB of domain memory, plus a few MB per vcp=
u.
shadow_memory =3D 8
name =3D "win2008c"
vif =3D ['=
;type=3Dioemu,bridge=3Dxenbr0,model=3De1000,script=3Dvif-bridge']
ac=
pi =3D 1

apic =3D 1
pae =3D 1
xen_platform_pci=3D1

tsc_mode=3D'defa=
ult'
xen_extended_power_mgmt=3D0

disk =3D [ 'phy:/dev/vol=
xen/win2008c,xvda,w',
         'file:/home/xen/iso/en_visio_2010=
.iso,xvdc:cdrom,r' ]

#--------------------------------------------------------------------------=
---
# boot on floppy (a), hard disk (c) or CD-ROM (d)
# default: hard=
 disk, cd-rom, floppy
boot=3D"dc"
sdl=3D0
stdvga        =
  =3D 1

serial          =3D 'pty'
localtime=3D1
vnc=3D1
vncconsole=
=3D1
vncpasswd=3D''
vnclisten       =3D '0.0.0.0'
=
vncviewer       =3D 1

on_poweroff =3D 'destroy'
on_reboot=
 =3D 'restart'

on_crash =3D 'restart'
monitor =3D 1
usb =3D 1
usbtablet =
=3D 1
usbdevice=3D'tablet'
--20cf302efcd60b060604ca6a3095-- --===============8563744280894467503== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users --===============8563744280894467503==-- From xen-users-bounces@lists.xen.org Mon Sep 24 03:30:12 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Mon, 24 Sep 2012 03:30:12 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TFzLq-0001sG-1f; Mon, 24 Sep 2012 03:28:54 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TFzLn-0001sB-RM for xen-users@lists.xen.org; Mon, 24 Sep 2012 03:28:52 +0000 Received: from [85.158.138.51:31948] by server-6.bemta-3.messagelabs.com id 5E/1D-29694-273DF505; Mon, 24 Sep 2012 03:28:50 +0000 X-Env-Sender: jaceksburghardt@gmail.com X-Msg-Ref: server-4.tower-174.messagelabs.com!1348457328!31183559!1 X-Originating-IP: [209.85.216.173] X-SpamReason: No, hits=1.2 required=7.0 tests=HTML_20_30,HTML_MESSAGE, ML_RADAR_SPEW_LINKS_14,RCVD_BY_IP,spamassassin: X-StarScan-Received: X-StarScan-Version: 6.6.1.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 1493 invoked from network); 24 Sep 2012 03:28:49 -0000 Received: from mail-qc0-f173.google.com (HELO mail-qc0-f173.google.com) (209.85.216.173) by server-4.tower-174.messagelabs.com with RC4-SHA encrypted SMTP; 24 Sep 2012 03:28:49 -0000 Received: by qcab12 with SMTP id b12so984745qca.32 for ; Sun, 23 Sep 2012 20:28:48 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:date:message-id:subject:from:to:content-type; bh=RHtHSW4dSsiywGSjz88Sfd6Pv/okAwtQheujy+I8MSY=; b=FPwUZjh78DgPZUBvLoko4XYL8u7Zwqz4LuNPqKrk9NhC33iiEVpXHYNrTjp0DDvUJG Sk62R+B7Zy3lqNPOsNAeDpclTcDpT7Hx0FnjbRRVZt96zFdf8ef0m4H9c14KFO73HPKO IHsS1JTmGzU64iogsz5lVjwNAcV/nQsLf5W2w4a+/nELLx/yxBWTBionXBb31qXuGtJ4 /hkNfLNShmYdQ2pVcybgZVoz+pcrWZ1/KSTl9vxk0ZcvOjRr7aJSd9e0Pm1mOztfaXlN j29miUKXM8cSxWSOpmUGwPCAxMK5nJCNmONYsBD6KjJmQc1HnpkAMlsmvdZrJV2FQPkP wAZA== MIME-Version: 1.0 Received: by 10.224.180.7 with SMTP id bs7mr29465018qab.37.1348457328215; Sun, 23 Sep 2012 20:28:48 -0700 (PDT) Received: by 10.49.118.101 with HTTP; Sun, 23 Sep 2012 20:28:48 -0700 (PDT) Date: Sun, 23 Sep 2012 21:28:48 -0600 Message-ID: From: jacek burghardt To: xen-users Subject: [Xen-users] server2008rebooting trouble X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============8563744280894467503==" Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org --===============8563744280894467503== Content-Type: multipart/alternative; boundary=20cf302efcd60b060604ca6a3095 --20cf302efcd60b060604ca6a3095 Content-Type: text/plain; charset=ISO-8859-1 I have servers 2008 running on xen 4.2 and 4.3 and the instances will never reboot. Option vcpu=1 will cause freeze on erebbot server 2008 will display shooting down unlese I use xl destroy and then create. When I removed vcpu=1 I get black screen with cursor. I hope someone can help me fix this as any update will cause frozen instance. builder = 'hvm' device_model_version= 'qemu-xen-traditional' viridian = 1 memory = 768 # Should be at least 2KB per MB of domain memory, plus a few MB per vcpu. shadow_memory = 8 name = "win2008c" vif = ['type=ioemu,bridge=xenbr0,model=e1000,script=vif-bridge'] acpi = 1 apic = 1 pae = 1 xen_platform_pci=1 tsc_mode='default' xen_extended_power_mgmt=0 disk = [ 'phy:/dev/volxen/win2008c,xvda,w', 'file:/home/xen/iso/en_visio_2010.iso,xvdc:cdrom,r' ] #----------------------------------------------------------------------------- # boot on floppy (a), hard disk (c) or CD-ROM (d) # default: hard disk, cd-rom, floppy boot="dc" sdl=0 stdvga = 1 serial = 'pty' localtime=1 vnc=1 vncconsole=1 vncpasswd='' vnclisten = '0.0.0.0' vncviewer = 1 on_poweroff = 'destroy' on_reboot = 'restart' on_crash = 'restart' monitor = 1 usb = 1 usbtablet = 1 usbdevice='tablet' --20cf302efcd60b060604ca6a3095 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable I have servers 2008 running on xen 4.2 and 4.3=A0 and the instances will ne= ver reboot. Option vcpu=3D1 will cause freeze on erebbot server 2008 will d= isplay shooting down unlese I use xl destroy and then create. When I remove= d vcpu=3D1 I get black screen with cursor.
I hope someone can help me fix this as any update will cause frozen instanc= e.

builder =3D 'hvm'
device_model_v=
ersion=3D 'qemu-xen-traditional'
viridian =3D 1
memory =3D  7=
68


# Should be at least 2KB per MB of domain memory, plus a few MB per vcp=
u.
shadow_memory =3D 8
name =3D "win2008c"
vif =3D ['=
;type=3Dioemu,bridge=3Dxenbr0,model=3De1000,script=3Dvif-bridge']
ac=
pi =3D 1

apic =3D 1
pae =3D 1
xen_platform_pci=3D1

tsc_mode=3D'defa=
ult'
xen_extended_power_mgmt=3D0

disk =3D [ 'phy:/dev/vol=
xen/win2008c,xvda,w',
         'file:/home/xen/iso/en_visio_2010=
.iso,xvdc:cdrom,r' ]

#--------------------------------------------------------------------------=
---
# boot on floppy (a), hard disk (c) or CD-ROM (d)
# default: hard=
 disk, cd-rom, floppy
boot=3D"dc"
sdl=3D0
stdvga        =
  =3D 1

serial          =3D 'pty'
localtime=3D1
vnc=3D1
vncconsole=
=3D1
vncpasswd=3D''
vnclisten       =3D '0.0.0.0'
=
vncviewer       =3D 1

on_poweroff =3D 'destroy'
on_reboot=
 =3D 'restart'

on_crash =3D 'restart'
monitor =3D 1
usb =3D 1
usbtablet =
=3D 1
usbdevice=3D'tablet'
--20cf302efcd60b060604ca6a3095-- --===============8563744280894467503== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users --===============8563744280894467503==-- From xen-users-bounces@lists.xen.org Mon Sep 24 03:45:00 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Mon, 24 Sep 2012 03:45:00 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TFzaP-0002EC-Od; Mon, 24 Sep 2012 03:43:57 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TFzaN-0002E3-UM for xen-users@lists.xen.org; Mon, 24 Sep 2012 03:43:56 +0000 Received: from [85.158.137.99:46882] by server-5.bemta-3.messagelabs.com id 16/16-13133-AF6DF505; Mon, 24 Sep 2012 03:43:54 +0000 X-Env-Sender: shades_of_grey@earthlink.net X-Msg-Ref: server-13.tower-217.messagelabs.com!1348458233!18849538!1 X-Originating-IP: [209.86.89.70] X-SpamReason: No, hits=0.1 required=7.0 tests=sa_preprocessor: QmFkIElQOiAyMDkuODYuODkuNzAgPT4gMzczOA==\n,sa_preprocessor: QmFkIElQOiAyMDkuODYuODkuNzAgPT4gMzczOA==\n,HTML_30_40,HTML_MESSAGE, ML_RADAR_SPEW_LINKS_14,spamassassin: X-StarScan-Received: X-StarScan-Version: 6.6.1.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 9380 invoked from network); 24 Sep 2012 03:43:53 -0000 Received: from elasmtp-banded.atl.sa.earthlink.net (HELO elasmtp-banded.atl.sa.earthlink.net) (209.86.89.70) by server-13.tower-217.messagelabs.com with SMTP; 24 Sep 2012 03:43:53 -0000 DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=dk20050327; d=earthlink.net; b=cBLC+KXlH81NO1ZHR2haBWH7acYIXdMFkPHxPc4uM7zFhhRW09QdGQPZ2FLhcUgq; h=Received:Message-ID:Date:From:User-Agent:MIME-Version:To:Subject:References:In-Reply-To:Content-Type:X-ELNK-Trace:X-Originating-IP; Received: from [66.167.250.229] (helo=[192.168.1.13]) by elasmtp-banded.atl.sa.earthlink.net with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.67) (envelope-from ) id 1TFzaK-0006XX-Oo for xen-users@lists.xen.org; Sun, 23 Sep 2012 23:43:53 -0400 Message-ID: <505FD6F4.4030605@earthlink.net> Date: Sun, 23 Sep 2012 23:43:48 -0400 From: ShadesOfGrey User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:15.0) Gecko/20120907 Thunderbird/15.0.1 MIME-Version: 1.0 To: xen-users@lists.xen.org References: <505B86AE.9040507@earthlink.net> In-Reply-To: X-ELNK-Trace: 0fe7bc40aa99bc8fc963772e86942a7b94f5150ab1c16ac0485087bba56e60095db2772f721bde7b21e9a4278e6e57ef350badd9bab72f9c350badd9bab72f9c X-Originating-IP: 66.167.250.229 Subject: Re: [Xen-users] Recommendations for Virtulization Hardware X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============1681909649058852811==" Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org This is a multi-part message in MIME format. --===============1681909649058852811== Content-Type: multipart/alternative; boundary="------------070202080301070701010608" This is a multi-part message in MIME format. --------------070202080301070701010608 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 8bit Sorry for the late response, I've had a lot to digest. On 09/20/2012 05:33 PM, Nuno Magalhães wrote: > Hi, > > Just a Xen newbie myself, but from what i've gathered and fiddled, Xen > (P)VMs don't come with a graphics card. You'd have to remote to your > Windows HVM to play games. You can fiddle with PCI pass through for > some video cards and there's some VGA passtrough as well, but i don't > think running a recent game on a VM would provide good results (i'm > thinking FPSs here, not solitaire or simcity). > > As for hardware i considered an ATI/Asus board with a Phenom II X6 and > 16GB or DDR3 a while ago, plus box, PSU, no disks, around 500EUR... YMMV > and your needs as well. > > Just my ill-informed 2c. HTH > > Nuno > > _______________________________________________ > Xen-users mailing list > Xen-users@lists.xen.org > http://lists.xen.org/xen-users My intention was to get a discrete GPU for Windows and pass it through for gaming and use PV drivers with an integrated GPU for the other VMs. I've seen this done in several YouTube videos (including those by Casey DeLorme ref. in this thread) and the performance seems pretty close to a stand-alone Windows install. As much as I'd like to support the underdog, AMD's CPUs are a bit lackluster. Given the workloads I'm looking to support, I don't think an AMD CPU will offer the requisite performance or longevity. On the other hand, it looks like I'll save myself quite a few headaches by choosing AMD for my GPU. --------------070202080301070701010608 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit
Sorry for the late response, I've had a lot to digest.

On 09/20/2012 05:33 PM, Nuno Magalhães wrote:
Hi,

Just a Xen newbie myself, but from what i've gathered and fiddled, Xen
(P)VMs don't come with a graphics card. You'd have to remote to your
Windows HVM to play games. You can fiddle with PCI pass through for
some video cards and there's some VGA passtrough as well, but i don't
think running a recent game on a VM would provide good results (i'm
thinking FPSs here, not solitaire or simcity).

As for hardware i considered an ATI/Asus board with a Phenom II X6 and
16GB or DDR3 a while ago, plus box, PSU, no disks, around 500€... YMMV
and your needs as well.

Just my ill-informed 2c. HTH

Nuno

_______________________________________________
Xen-users mailing list
Xen-users@lists.xen.org
http://lists.xen.org/xen-users

My intention was to get a discrete GPU for Windows and pass it through for gaming and use PV drivers with an integrated GPU for the other VMs.  I've seen this done in several YouTube videos (including those by Casey DeLorme ref. in this thread) and the performance seems pretty close to a stand-alone Windows install.

As much as I'd like to support the underdog, AMD's CPUs are a bit lackluster.  Given the workloads I'm looking to support, I don't think an AMD CPU will offer the requisite performance or longevity.  On the other hand, it looks like I'll save myself quite a few headaches by choosing AMD for my GPU.

--------------070202080301070701010608-- --===============1681909649058852811== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users --===============1681909649058852811==-- From xen-users-bounces@lists.xen.org Mon Sep 24 03:45:00 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Mon, 24 Sep 2012 03:45:00 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TFzaP-0002EC-Od; Mon, 24 Sep 2012 03:43:57 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TFzaN-0002E3-UM for xen-users@lists.xen.org; Mon, 24 Sep 2012 03:43:56 +0000 Received: from [85.158.137.99:46882] by server-5.bemta-3.messagelabs.com id 16/16-13133-AF6DF505; Mon, 24 Sep 2012 03:43:54 +0000 X-Env-Sender: shades_of_grey@earthlink.net X-Msg-Ref: server-13.tower-217.messagelabs.com!1348458233!18849538!1 X-Originating-IP: [209.86.89.70] X-SpamReason: No, hits=0.1 required=7.0 tests=sa_preprocessor: QmFkIElQOiAyMDkuODYuODkuNzAgPT4gMzczOA==\n,sa_preprocessor: QmFkIElQOiAyMDkuODYuODkuNzAgPT4gMzczOA==\n,HTML_30_40,HTML_MESSAGE, ML_RADAR_SPEW_LINKS_14,spamassassin: X-StarScan-Received: X-StarScan-Version: 6.6.1.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 9380 invoked from network); 24 Sep 2012 03:43:53 -0000 Received: from elasmtp-banded.atl.sa.earthlink.net (HELO elasmtp-banded.atl.sa.earthlink.net) (209.86.89.70) by server-13.tower-217.messagelabs.com with SMTP; 24 Sep 2012 03:43:53 -0000 DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=dk20050327; d=earthlink.net; b=cBLC+KXlH81NO1ZHR2haBWH7acYIXdMFkPHxPc4uM7zFhhRW09QdGQPZ2FLhcUgq; h=Received:Message-ID:Date:From:User-Agent:MIME-Version:To:Subject:References:In-Reply-To:Content-Type:X-ELNK-Trace:X-Originating-IP; Received: from [66.167.250.229] (helo=[192.168.1.13]) by elasmtp-banded.atl.sa.earthlink.net with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.67) (envelope-from ) id 1TFzaK-0006XX-Oo for xen-users@lists.xen.org; Sun, 23 Sep 2012 23:43:53 -0400 Message-ID: <505FD6F4.4030605@earthlink.net> Date: Sun, 23 Sep 2012 23:43:48 -0400 From: ShadesOfGrey User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:15.0) Gecko/20120907 Thunderbird/15.0.1 MIME-Version: 1.0 To: xen-users@lists.xen.org References: <505B86AE.9040507@earthlink.net> In-Reply-To: X-ELNK-Trace: 0fe7bc40aa99bc8fc963772e86942a7b94f5150ab1c16ac0485087bba56e60095db2772f721bde7b21e9a4278e6e57ef350badd9bab72f9c350badd9bab72f9c X-Originating-IP: 66.167.250.229 Subject: Re: [Xen-users] Recommendations for Virtulization Hardware X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============1681909649058852811==" Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org This is a multi-part message in MIME format. --===============1681909649058852811== Content-Type: multipart/alternative; boundary="------------070202080301070701010608" This is a multi-part message in MIME format. --------------070202080301070701010608 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 8bit Sorry for the late response, I've had a lot to digest. On 09/20/2012 05:33 PM, Nuno Magalhães wrote: > Hi, > > Just a Xen newbie myself, but from what i've gathered and fiddled, Xen > (P)VMs don't come with a graphics card. You'd have to remote to your > Windows HVM to play games. You can fiddle with PCI pass through for > some video cards and there's some VGA passtrough as well, but i don't > think running a recent game on a VM would provide good results (i'm > thinking FPSs here, not solitaire or simcity). > > As for hardware i considered an ATI/Asus board with a Phenom II X6 and > 16GB or DDR3 a while ago, plus box, PSU, no disks, around 500EUR... YMMV > and your needs as well. > > Just my ill-informed 2c. HTH > > Nuno > > _______________________________________________ > Xen-users mailing list > Xen-users@lists.xen.org > http://lists.xen.org/xen-users My intention was to get a discrete GPU for Windows and pass it through for gaming and use PV drivers with an integrated GPU for the other VMs. I've seen this done in several YouTube videos (including those by Casey DeLorme ref. in this thread) and the performance seems pretty close to a stand-alone Windows install. As much as I'd like to support the underdog, AMD's CPUs are a bit lackluster. Given the workloads I'm looking to support, I don't think an AMD CPU will offer the requisite performance or longevity. On the other hand, it looks like I'll save myself quite a few headaches by choosing AMD for my GPU. --------------070202080301070701010608 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit
Sorry for the late response, I've had a lot to digest.

On 09/20/2012 05:33 PM, Nuno Magalhães wrote:
Hi,

Just a Xen newbie myself, but from what i've gathered and fiddled, Xen
(P)VMs don't come with a graphics card. You'd have to remote to your
Windows HVM to play games. You can fiddle with PCI pass through for
some video cards and there's some VGA passtrough as well, but i don't
think running a recent game on a VM would provide good results (i'm
thinking FPSs here, not solitaire or simcity).

As for hardware i considered an ATI/Asus board with a Phenom II X6 and
16GB or DDR3 a while ago, plus box, PSU, no disks, around 500€... YMMV
and your needs as well.

Just my ill-informed 2c. HTH

Nuno

_______________________________________________
Xen-users mailing list
Xen-users@lists.xen.org
http://lists.xen.org/xen-users

My intention was to get a discrete GPU for Windows and pass it through for gaming and use PV drivers with an integrated GPU for the other VMs.  I've seen this done in several YouTube videos (including those by Casey DeLorme ref. in this thread) and the performance seems pretty close to a stand-alone Windows install.

As much as I'd like to support the underdog, AMD's CPUs are a bit lackluster.  Given the workloads I'm looking to support, I don't think an AMD CPU will offer the requisite performance or longevity.  On the other hand, it looks like I'll save myself quite a few headaches by choosing AMD for my GPU.

--------------070202080301070701010608-- --===============1681909649058852811== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users --===============1681909649058852811==-- From xen-users-bounces@lists.xen.org Mon Sep 24 03:46:03 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Mon, 24 Sep 2012 03:46:03 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TFzbc-0002JF-Fd; Mon, 24 Sep 2012 03:45:12 +0000 Received: from mail27.messagelabs.com ([193.109.254.147]) by lists.xen.org with smtp (Exim 4.72) (envelope-from ) id 1TFzba-0002IY-UT for xen-users@lists.xen.org; Mon, 24 Sep 2012 03:45:11 +0000 X-Env-Sender: shades_of_grey@earthlink.net X-Msg-Ref: server-10.tower-27.messagelabs.com!1348458304!6914709!1 X-Originating-IP: [209.86.89.70] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: QmFkIElQOiAyMDkuODYuODkuNzAgPT4gMzczOA==\n,sa_preprocessor: QmFkIElQOiAyMDkuODYuODkuNzAgPT4gMzczOA==\n,ML_RADAR_SPEW_LINKS_14, spamassassin: X-StarScan-Received: X-StarScan-Version: 6.6.1.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 31842 invoked from network); 24 Sep 2012 03:45:04 -0000 Received: from elasmtp-banded.atl.sa.earthlink.net (HELO elasmtp-banded.atl.sa.earthlink.net) (209.86.89.70) by server-10.tower-27.messagelabs.com with SMTP; 24 Sep 2012 03:45:04 -0000 DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=dk20050327; d=earthlink.net; b=RHg6oqR35Vck/UhBmSh5qmjw0HStDQ7KO1UcrC2gv4BpuZws4m+qXiqMcgF1/pOU; h=Received:Message-ID:Date:From:User-Agent:MIME-Version:To:Subject:References:In-Reply-To:Content-Type:Content-Transfer-Encoding:X-ELNK-Trace:X-Originating-IP; Received: from [66.167.250.229] (helo=[192.168.1.13]) by elasmtp-banded.atl.sa.earthlink.net with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.67) (envelope-from ) id 1TFzbT-0006tM-PS for xen-users@lists.xen.org; Sun, 23 Sep 2012 23:45:04 -0400 Message-ID: <505FD734.4020106@earthlink.net> Date: Sun, 23 Sep 2012 23:44:52 -0400 From: ShadesOfGrey User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:15.0) Gecko/20120907 Thunderbird/15.0.1 MIME-Version: 1.0 To: xen-users@lists.xen.org References: <505B86AE.9040507@earthlink.net> <1348178025.2320.23.camel@ul30vt.home> In-Reply-To: <1348178025.2320.23.camel@ul30vt.home> X-ELNK-Trace: 0fe7bc40aa99bc8fc963772e86942a7b94f5150ab1c16ac0485087bba56e6009217f7a0518ec0cc6ac8ea30d8a12fa57350badd9bab72f9c350badd9bab72f9c X-Originating-IP: 66.167.250.229 Subject: Re: [Xen-users] Recommendations for Virtulization Hardware X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset="us-ascii"; Format="flowed" Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org Sorry for the late response, I've had a lot to digest. On 09/20/2012 05:53 PM, Alex Williamson wrote: > > There have been a couple success reports of using AMD/ATI graphics cards > on Intel VT-d systems with KVM device assignment. Nvidia cards have not > met with the same degree of success. In both our cases, the graphics > device was assigned to a Windows guest as a secondary graphics head. > For me, Windows took over the assigned device as the primary graphics, > disabling the emulated graphics. For my slow HD 5450, 3dMark seems to > get a similar score to what others see on bare metal. > > Graphics device assignment on KVM is getting better, but should be > considered experimental at best. Thanks, > > Alex > > > _______________________________________________ > Xen-users mailing list > Xen-users@lists.xen.org > http://lists.xen.org/xen-users > I had noticed that KVM seems to be behind Xen with respect to PCI/VGA passthrough (among other things). Then again, with information generally being a bit outdated all around, I figured I should at least give KVM a shot. Worst case scenario, I'd try KVM and Xen (or some other Hypervisor) and both fail to offer what I want. My contingency plan is to build a modest second box. Best case, both work and it's just a question of choosing which Hypervisor best fits. In any case, I plan on keeping an eye on both as they develop. _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Mon Sep 24 03:46:03 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Mon, 24 Sep 2012 03:46:03 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TFzbc-0002JF-Fd; Mon, 24 Sep 2012 03:45:12 +0000 Received: from mail27.messagelabs.com ([193.109.254.147]) by lists.xen.org with smtp (Exim 4.72) (envelope-from ) id 1TFzba-0002IY-UT for xen-users@lists.xen.org; Mon, 24 Sep 2012 03:45:11 +0000 X-Env-Sender: shades_of_grey@earthlink.net X-Msg-Ref: server-10.tower-27.messagelabs.com!1348458304!6914709!1 X-Originating-IP: [209.86.89.70] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: QmFkIElQOiAyMDkuODYuODkuNzAgPT4gMzczOA==\n,sa_preprocessor: QmFkIElQOiAyMDkuODYuODkuNzAgPT4gMzczOA==\n,ML_RADAR_SPEW_LINKS_14, spamassassin: X-StarScan-Received: X-StarScan-Version: 6.6.1.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 31842 invoked from network); 24 Sep 2012 03:45:04 -0000 Received: from elasmtp-banded.atl.sa.earthlink.net (HELO elasmtp-banded.atl.sa.earthlink.net) (209.86.89.70) by server-10.tower-27.messagelabs.com with SMTP; 24 Sep 2012 03:45:04 -0000 DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=dk20050327; d=earthlink.net; b=RHg6oqR35Vck/UhBmSh5qmjw0HStDQ7KO1UcrC2gv4BpuZws4m+qXiqMcgF1/pOU; h=Received:Message-ID:Date:From:User-Agent:MIME-Version:To:Subject:References:In-Reply-To:Content-Type:Content-Transfer-Encoding:X-ELNK-Trace:X-Originating-IP; Received: from [66.167.250.229] (helo=[192.168.1.13]) by elasmtp-banded.atl.sa.earthlink.net with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.67) (envelope-from ) id 1TFzbT-0006tM-PS for xen-users@lists.xen.org; Sun, 23 Sep 2012 23:45:04 -0400 Message-ID: <505FD734.4020106@earthlink.net> Date: Sun, 23 Sep 2012 23:44:52 -0400 From: ShadesOfGrey User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:15.0) Gecko/20120907 Thunderbird/15.0.1 MIME-Version: 1.0 To: xen-users@lists.xen.org References: <505B86AE.9040507@earthlink.net> <1348178025.2320.23.camel@ul30vt.home> In-Reply-To: <1348178025.2320.23.camel@ul30vt.home> X-ELNK-Trace: 0fe7bc40aa99bc8fc963772e86942a7b94f5150ab1c16ac0485087bba56e6009217f7a0518ec0cc6ac8ea30d8a12fa57350badd9bab72f9c350badd9bab72f9c X-Originating-IP: 66.167.250.229 Subject: Re: [Xen-users] Recommendations for Virtulization Hardware X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset="us-ascii"; Format="flowed" Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org Sorry for the late response, I've had a lot to digest. On 09/20/2012 05:53 PM, Alex Williamson wrote: > > There have been a couple success reports of using AMD/ATI graphics cards > on Intel VT-d systems with KVM device assignment. Nvidia cards have not > met with the same degree of success. In both our cases, the graphics > device was assigned to a Windows guest as a secondary graphics head. > For me, Windows took over the assigned device as the primary graphics, > disabling the emulated graphics. For my slow HD 5450, 3dMark seems to > get a similar score to what others see on bare metal. > > Graphics device assignment on KVM is getting better, but should be > considered experimental at best. Thanks, > > Alex > > > _______________________________________________ > Xen-users mailing list > Xen-users@lists.xen.org > http://lists.xen.org/xen-users > I had noticed that KVM seems to be behind Xen with respect to PCI/VGA passthrough (among other things). Then again, with information generally being a bit outdated all around, I figured I should at least give KVM a shot. Worst case scenario, I'd try KVM and Xen (or some other Hypervisor) and both fail to offer what I want. My contingency plan is to build a modest second box. Best case, both work and it's just a question of choosing which Hypervisor best fits. In any case, I plan on keeping an eye on both as they develop. _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Mon Sep 24 03:46:10 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Mon, 24 Sep 2012 03:46:10 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TFzbu-0002Kp-5G; Mon, 24 Sep 2012 03:45:30 +0000 Received: from mail27.messagelabs.com ([193.109.254.147]) by lists.xen.org with smtp (Exim 4.72) (envelope-from ) id 1TFzbs-0002KI-Li for xen-users@lists.xen.org; Mon, 24 Sep 2012 03:45:29 +0000 X-Env-Sender: shades_of_grey@earthlink.net X-Msg-Ref: server-12.tower-27.messagelabs.com!1348458320!12105383!1 X-Originating-IP: [209.86.89.62] X-SpamReason: No, hits=0.5 required=7.0 tests=BODY_RANDOM_LONG, ML_RADAR_SPEW_LINKS_14,spamassassin: X-StarScan-Received: X-StarScan-Version: 6.6.1.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 20780 invoked from network); 24 Sep 2012 03:45:20 -0000 Received: from elasmtp-dupuy.atl.sa.earthlink.net (HELO elasmtp-dupuy.atl.sa.earthlink.net) (209.86.89.62) by server-12.tower-27.messagelabs.com with SMTP; 24 Sep 2012 03:45:20 -0000 DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=dk20050327; d=earthlink.net; b=QVrYabwlemzl4HYZvpvaefNFfbLfBUIZo2zDBRsm7p80ScubxbuVQKuGeMNX2Oej; h=Received:Message-ID:Date:From:User-Agent:MIME-Version:To:Subject:References:In-Reply-To:Content-Type:Content-Transfer-Encoding:X-ELNK-Trace:X-Originating-IP; Received: from [66.167.250.229] (helo=[192.168.1.13]) by elasmtp-dupuy.atl.sa.earthlink.net with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.67) (envelope-from ) id 1TFzbj-0005EQ-LM for xen-users@lists.xen.org; Sun, 23 Sep 2012 23:45:19 -0400 Message-ID: <505FD74E.2050405@earthlink.net> Date: Sun, 23 Sep 2012 23:45:18 -0400 From: ShadesOfGrey User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:15.0) Gecko/20120907 Thunderbird/15.0.1 MIME-Version: 1.0 To: xen-users@lists.xen.org References: <505B86AE.9040507@earthlink.net> <505C8630.2090002@student.chalmers.se> In-Reply-To: <505C8630.2090002@student.chalmers.se> X-ELNK-Trace: 0fe7bc40aa99bc8fc963772e86942a7b94f5150ab1c16ac0485087bba56e6009449aff5492b13813c9a49306128aab74350badd9bab72f9c350badd9bab72f9c X-Originating-IP: 66.167.250.229 Subject: Re: [Xen-users] Recommendations for Virtulization Hardware X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset="windows-1252"; Format="flowed" Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org Sorry for the late response, I've had a lot to digest. On 09/21/2012 11:22 AM, Robin Axelsson wrote: > If you want to be able to use PCI and VGA passthrough you basically = > need to make sure that your hardware supports either AMD-Vi (formerly = > known as AMD-IOMMU) or Intel VT-d extensions. In the Intel case it = > limits your choice of Motherboard (it must be supported in the BIOS) = > and CPU. In the AMD case it limits only your choice of motherboard. A = > good start is to check out one of these pages: > > http://wiki.xensource.com/xenwiki/VTdHowTo > http://wiki.xen.org/wiki/VTd_HowTo > > A word of warning here is that parts of the documentation is somewhat = > dated. You can also communicate with e.g. Gigabyte, Asus or ASRock = > customer support and ask them if a particular motherboard supports = > these extensions. Most motherboards also have downloadable user = > manuals, if the BIOS settings in those pages shows options to = > enable/disable VT-d or AMD-Vi/IOMMU extensions then you will be ok = > with that motherboard. > The lack of current information about Xen (and KVM) online has been = frustrating =97 especially finding the many proof of concept videos that = demonstrated possibilities but offered no real specifics. Looking for = specifics, I sought information from gaming and enthusiast sites; I = figured finding confirmation of VT-d and AMD-Vi support on such sites = would be more likely. However, I found that wasn't often the case. I did = determine that ASRock motherboards seem to be the most likely to support = VT-d, ASUS least likely (unless equipped with an Intel 'sanctioned' VT-d = chipset). I had narrowed my choices to two motherboards that appear to = offer VT-d support and was intending to contact the manufacturer before = purchase. Both choices are a bit pricey and I've been reconsidering = whether I should look to other motherboards to reduce costs. > The other thing is choice of GPU for VGA passthrough and it is = > preferable that the GPU supports FLR or Function Level Reset as it is = > called. Thing is that the hardware needs to be reset somehow as it is = > passed through to the host. This is best done with FLR and nVidia is = > known to supply firmware patches for some of their Geforce cards with = > this support and it is said to be supported by default with their = > Quadro cards. FLR is not the only way to reset a PCI device, a reset = > could be trigged through the ACPI power management framework by = > temporarily cutting power to the affected PCI slot. These reset = > methods are called d3d0 and bus reset. The question however, is if = > this works on PCI cards that use auxiliary power directly from the = > PSU. There is a pdf document on the VMWare website = > (http://www.vmware.com/files/pdf/techpaper/vsp_4_vmdirectpath_host.pdf) a= bout = > this: > > ----------------------- > Reset Method > > Possible values for the reset method include flr, d3d0, link, bridge, = > or default. > > The default setting is described as follows. If a device supports = > function level reset (FLR), ESX always uses FLR. If the device does = > not support FLR, ESX next defaults to link reset and bus reset in that = > order. Link reset and bus reset might prevent some devices from being = > assigned to different virtual machines, or from being assigned between = > the VMkernel and virtual machines. In the absence of FLR, it is = > possible to use PCI Power Management capability (D3 to D0 transitions) = > to trigger a reset. Most of the Intel NICs and various other HBAs = > support this mode. > ----------------------- > > > There are indications from people that d3d0 also work with PCI cards = > that take power from auxiliary inputs. I suggest that you take a look = > at the following youtube clip and read the comments there: > > http://www.youtube.com/watch?v=3DGtmwnx-k2qg > > So it seems that it works although it may be a bit more quirky. It = > doesn't hurt to take that discussion (particularly about FLR support) = > with nVidia and/or AMD. > This is precisely the kind of information I was looking for from the = threads I started on Ars Technica. It's just unfortunate that FLR and D3 = D0 support aren't often found in the tech specs of must expansion = hardware. However, now that I know what to ask, I'll try contacting = hardware manufacturers prior to purchasing any expansion hardware. Thank = you! > When it comes to virtualization, the technology has come very far, but = > it is still lacking considerably when it comes to sharing GPUs and = > also to some degree when it comes to sharing I/O devices (especially = > when you intend to run many virtual machines on a single system). The = > GPU today consists of three types of components; the processing unit, = > graphics memory and the video output unit/adapter and it is not clear = > as to how to share these components seamlessly between the host and = > virtual machines with minimal overhead. Whereas there are VT-x = > extensions that allows you to pretty seamlessly share CPU cores = > between VMs and the host there are currently none for the processing = > unit. It is also not clear how the hardware can assist with sharing = > TV/monitor screen estate between machines with all 3D effects such as = > Aqua for Win7 and the whatnot enabled for all machines. Especially = > when considering the dynamics of plugging and unplugging computer = > monitors to multiport/eyefinity graphics cards and the ability to = > change screen resolution. Things are improving for sure and a lot of = > research is likely going into this. I don't know what's happening in = > the GPU frontline but I know that the next thing with passthrough is = > the SR-IOV that allows PCI units to present several virtual instances = > of oneself to several virtual machines. It's a cool thing, I recommend = > further reading about this here: > > http://www.intel.com/content/www/us/en/pci-express/pci-sig-sr-iov-primer-= sr-iov-technology-paper.html = > > http://blog.scottlowe.org/2009/12/02/what-is-sr-iov/ > That is fascinating. Extending virtualization to expansion hardware via = SR-IOV, sure would make the kind of setup I'm attempting a lot easier. = However, if I can replicate what I've seen in proof of concept videos = (namely Casey DeLorme's), I think that will meet my needs for now. As it = stands, I initially intend to reserve any discrete GPU(s) for Windows = and rely on an integrated GPU for all other VMs using PV drivers = (wherever possible). Afterward, I want to experiment with re-assigning = the whatever discrete GPU(s) for GPGPU functions under a Linux VM = whenever the GPU is not going to used for gaming (if at all possible). > It is likely to take a few years before something useful will come out = > of it. In the meanwhile, unless you want to use several GPUs which = > might not be a bad thing as a lot of monitors these days have several = > inputs, you can resort to using a remote desktop client to integrate = > one machine with another. Virtualbox for example use RDP through which = > you can interact with your virtual machine. In a similar manner you = > can set up a VNC server on your Linux host and establish a connection = > to it through your Windows VM. You will not get full 3D functionality = > (such as Aqua) through the client although there is a growing support = > for it through VirtualGL extensions that are coming to VNC and perhaps = > the Spice protocol. But some clients might even allow for seamless = > mode that lets you mix Linux and Windows windows on the same desktop = > like this for example: > > http://i.techrepublic.com.com/blogs/seamless.png > http://www.youtube.com/watch?v=3DeQr8iI0yZH4 > > > Just keep in mind that this is still a little bit of uncharted = > territory so there may be a few bumps on the way and it may not work = > as smooth as you would desire. > > From everything I've read, solutions that rely on any form of remote = display protocols would be limited to a subset of Direct3D functions. = Furthermore, these would vary from one implementation to another, thus = making them far less attractive for gaming than VGA passthrough... Well, = in my opinion anyway. VirtualBox's seamless mode is pretty nifty. But it's a Type 2 Hypervisor = and relies on paravirtualized drivers that also suffer from the same = limitations as remote display protocols. It's great for most things, but = gaming is not one of them. And I'm speaking from personal experience. = Though I haven't used them myself, the same would seem to hold true of = Parallel's and VMWare's 'Workstation' offerings. At least, as far as = I've gathered. FYI, the Type 1 Hypervisors from Parallel's and VMWare* are priced = waaayyy outside my budget. *I only found out about VMWare's 'free' vSphere after I'd written this = response. > > I see that your demands are somewhat multifaceted. I believe that you = > also want to use diffent services such as using your machine as a file = > server with the possible intention of using filesystems such as ZFS. = > If you do, you should be careful with your selection of hardware for = > these particular purposes. If you want to get full protection against = > data corruption from ZFS, your choice of hardware gets rather limited = > when it comes to choice of hard drives, host bus adapter and network = > controller. The most stable implementation of ZFS is found with = > Illumos based operating systems (such as OpenIndiana, SmartOS, OmniOS, = > Belenix etc) or Solaris if you choose to download it from Oracle's = > website. With these operating systems you are most likely to want to = > use hardware that has certified drivers for it. That way you are less = > likely to run into problems later on. That implies that you will be = > limited to choosing Intel based network adapters and LSI based SAS = > controllers. There should be _no_ hardware RAID functionality in the = > SAS controller that merely should be run in IT mode (or = > Initiator-Target mode). That requires the LSI controller to be flashed = > with IT firmware in most cases. The objective here is to make sure = > that _all_ errors that might occur with the hard drives are reported = > all the way to the software level and that nothing is concealed of = > obfuscated by internal error handling in the hardware. It is therefore = > recommended to use SAS hard drives instead of S-ATA (which also are = > fully compatible with SAS controllers). SAS hard drives are not much = > more expensive than similar SATA drives and you get a higher = > reliability out of them. It is also recommended to have at least two = > drive redundancy simply because if one drive is dead and you swap it, = > it is not uncommon that another drive dies in the rebuild process of = > the RAID cluster because of the added strain the rebuild process (or = > 'resilvering' as it is called in Solaris terms) put on the drives. Of = > course, the system should communicate directly to the hard drive = > hardware and not be obfuscated by some virtual abstraction layer in = > between which means that you either run ZFS on the metal or through = > PCI passthrough of the SAS (and perhaps also network) adapters. Also, = > it is highly recommended that you use ECC RAM for such applications = > and it doesn't hurt to dedicate a few gigs of it to the ZFS as RAM is = > used for cache. The good news is that most motherboards with good = > chipsets support ECC RAM even though you might not find anything about = > it in the user manuals. Again, thanks for the thorough explanation. This gives me a great deal = to think about. The more I learn about ZFS, the less appealing it = becomes. And by that I mean the confusion over which version of ZFS is = in what OS? And just how well maintained the OSes supporting ZFS are? = Now I have additional hardware considerations to keep in mind that may = (or may not) make the cost of ZFS RAID-Z pool comparable to a hardware = RAID5/6 solution anyway. Do you have any suggestions as to which of LSI = HBAs I should be considering? I haven't found an HCL for ZFS in my searches. Out of curiosity =97 and if you would happen to know =97 do you think what = you suggest about the HBA and SAS drives for ZFS also applies to Btrfs? = I'm assuming it would, but I'd appreciate some confirmation. It's funny how the "I" in RAID never really seems to apply... Especially = since it looks more and more like using ZFS or Btrfs will require I = commit myself, from the start, to one or the other and a discrete HBA. = Transitioning from an integrated SATA controller(s) and mdadm seems = rather impractical. If I understand what's involved in doing so = correctly. It may turn out that anything other than mdadm is price = prohibitive. > I admire your persistence with pursuing this undertaking and wish you = > the best of luck with it! > Robin. > > Thanks. I've invested too much time in research to not at least make the = attempt. Besides, if all else fails, I can fallback to a two box = solution. That is, if I can get my hypothetical virtualization box to = fit in my budget envelope... _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Mon Sep 24 03:46:10 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Mon, 24 Sep 2012 03:46:10 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TFzbu-0002Kp-5G; Mon, 24 Sep 2012 03:45:30 +0000 Received: from mail27.messagelabs.com ([193.109.254.147]) by lists.xen.org with smtp (Exim 4.72) (envelope-from ) id 1TFzbs-0002KI-Li for xen-users@lists.xen.org; Mon, 24 Sep 2012 03:45:29 +0000 X-Env-Sender: shades_of_grey@earthlink.net X-Msg-Ref: server-12.tower-27.messagelabs.com!1348458320!12105383!1 X-Originating-IP: [209.86.89.62] X-SpamReason: No, hits=0.5 required=7.0 tests=BODY_RANDOM_LONG, ML_RADAR_SPEW_LINKS_14,spamassassin: X-StarScan-Received: X-StarScan-Version: 6.6.1.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 20780 invoked from network); 24 Sep 2012 03:45:20 -0000 Received: from elasmtp-dupuy.atl.sa.earthlink.net (HELO elasmtp-dupuy.atl.sa.earthlink.net) (209.86.89.62) by server-12.tower-27.messagelabs.com with SMTP; 24 Sep 2012 03:45:20 -0000 DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=dk20050327; d=earthlink.net; b=QVrYabwlemzl4HYZvpvaefNFfbLfBUIZo2zDBRsm7p80ScubxbuVQKuGeMNX2Oej; h=Received:Message-ID:Date:From:User-Agent:MIME-Version:To:Subject:References:In-Reply-To:Content-Type:Content-Transfer-Encoding:X-ELNK-Trace:X-Originating-IP; Received: from [66.167.250.229] (helo=[192.168.1.13]) by elasmtp-dupuy.atl.sa.earthlink.net with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.67) (envelope-from ) id 1TFzbj-0005EQ-LM for xen-users@lists.xen.org; Sun, 23 Sep 2012 23:45:19 -0400 Message-ID: <505FD74E.2050405@earthlink.net> Date: Sun, 23 Sep 2012 23:45:18 -0400 From: ShadesOfGrey User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:15.0) Gecko/20120907 Thunderbird/15.0.1 MIME-Version: 1.0 To: xen-users@lists.xen.org References: <505B86AE.9040507@earthlink.net> <505C8630.2090002@student.chalmers.se> In-Reply-To: <505C8630.2090002@student.chalmers.se> X-ELNK-Trace: 0fe7bc40aa99bc8fc963772e86942a7b94f5150ab1c16ac0485087bba56e6009449aff5492b13813c9a49306128aab74350badd9bab72f9c350badd9bab72f9c X-Originating-IP: 66.167.250.229 Subject: Re: [Xen-users] Recommendations for Virtulization Hardware X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset="windows-1252"; Format="flowed" Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org Sorry for the late response, I've had a lot to digest. On 09/21/2012 11:22 AM, Robin Axelsson wrote: > If you want to be able to use PCI and VGA passthrough you basically = > need to make sure that your hardware supports either AMD-Vi (formerly = > known as AMD-IOMMU) or Intel VT-d extensions. In the Intel case it = > limits your choice of Motherboard (it must be supported in the BIOS) = > and CPU. In the AMD case it limits only your choice of motherboard. A = > good start is to check out one of these pages: > > http://wiki.xensource.com/xenwiki/VTdHowTo > http://wiki.xen.org/wiki/VTd_HowTo > > A word of warning here is that parts of the documentation is somewhat = > dated. You can also communicate with e.g. Gigabyte, Asus or ASRock = > customer support and ask them if a particular motherboard supports = > these extensions. Most motherboards also have downloadable user = > manuals, if the BIOS settings in those pages shows options to = > enable/disable VT-d or AMD-Vi/IOMMU extensions then you will be ok = > with that motherboard. > The lack of current information about Xen (and KVM) online has been = frustrating =97 especially finding the many proof of concept videos that = demonstrated possibilities but offered no real specifics. Looking for = specifics, I sought information from gaming and enthusiast sites; I = figured finding confirmation of VT-d and AMD-Vi support on such sites = would be more likely. However, I found that wasn't often the case. I did = determine that ASRock motherboards seem to be the most likely to support = VT-d, ASUS least likely (unless equipped with an Intel 'sanctioned' VT-d = chipset). I had narrowed my choices to two motherboards that appear to = offer VT-d support and was intending to contact the manufacturer before = purchase. Both choices are a bit pricey and I've been reconsidering = whether I should look to other motherboards to reduce costs. > The other thing is choice of GPU for VGA passthrough and it is = > preferable that the GPU supports FLR or Function Level Reset as it is = > called. Thing is that the hardware needs to be reset somehow as it is = > passed through to the host. This is best done with FLR and nVidia is = > known to supply firmware patches for some of their Geforce cards with = > this support and it is said to be supported by default with their = > Quadro cards. FLR is not the only way to reset a PCI device, a reset = > could be trigged through the ACPI power management framework by = > temporarily cutting power to the affected PCI slot. These reset = > methods are called d3d0 and bus reset. The question however, is if = > this works on PCI cards that use auxiliary power directly from the = > PSU. There is a pdf document on the VMWare website = > (http://www.vmware.com/files/pdf/techpaper/vsp_4_vmdirectpath_host.pdf) a= bout = > this: > > ----------------------- > Reset Method > > Possible values for the reset method include flr, d3d0, link, bridge, = > or default. > > The default setting is described as follows. If a device supports = > function level reset (FLR), ESX always uses FLR. If the device does = > not support FLR, ESX next defaults to link reset and bus reset in that = > order. Link reset and bus reset might prevent some devices from being = > assigned to different virtual machines, or from being assigned between = > the VMkernel and virtual machines. In the absence of FLR, it is = > possible to use PCI Power Management capability (D3 to D0 transitions) = > to trigger a reset. Most of the Intel NICs and various other HBAs = > support this mode. > ----------------------- > > > There are indications from people that d3d0 also work with PCI cards = > that take power from auxiliary inputs. I suggest that you take a look = > at the following youtube clip and read the comments there: > > http://www.youtube.com/watch?v=3DGtmwnx-k2qg > > So it seems that it works although it may be a bit more quirky. It = > doesn't hurt to take that discussion (particularly about FLR support) = > with nVidia and/or AMD. > This is precisely the kind of information I was looking for from the = threads I started on Ars Technica. It's just unfortunate that FLR and D3 = D0 support aren't often found in the tech specs of must expansion = hardware. However, now that I know what to ask, I'll try contacting = hardware manufacturers prior to purchasing any expansion hardware. Thank = you! > When it comes to virtualization, the technology has come very far, but = > it is still lacking considerably when it comes to sharing GPUs and = > also to some degree when it comes to sharing I/O devices (especially = > when you intend to run many virtual machines on a single system). The = > GPU today consists of three types of components; the processing unit, = > graphics memory and the video output unit/adapter and it is not clear = > as to how to share these components seamlessly between the host and = > virtual machines with minimal overhead. Whereas there are VT-x = > extensions that allows you to pretty seamlessly share CPU cores = > between VMs and the host there are currently none for the processing = > unit. It is also not clear how the hardware can assist with sharing = > TV/monitor screen estate between machines with all 3D effects such as = > Aqua for Win7 and the whatnot enabled for all machines. Especially = > when considering the dynamics of plugging and unplugging computer = > monitors to multiport/eyefinity graphics cards and the ability to = > change screen resolution. Things are improving for sure and a lot of = > research is likely going into this. I don't know what's happening in = > the GPU frontline but I know that the next thing with passthrough is = > the SR-IOV that allows PCI units to present several virtual instances = > of oneself to several virtual machines. It's a cool thing, I recommend = > further reading about this here: > > http://www.intel.com/content/www/us/en/pci-express/pci-sig-sr-iov-primer-= sr-iov-technology-paper.html = > > http://blog.scottlowe.org/2009/12/02/what-is-sr-iov/ > That is fascinating. Extending virtualization to expansion hardware via = SR-IOV, sure would make the kind of setup I'm attempting a lot easier. = However, if I can replicate what I've seen in proof of concept videos = (namely Casey DeLorme's), I think that will meet my needs for now. As it = stands, I initially intend to reserve any discrete GPU(s) for Windows = and rely on an integrated GPU for all other VMs using PV drivers = (wherever possible). Afterward, I want to experiment with re-assigning = the whatever discrete GPU(s) for GPGPU functions under a Linux VM = whenever the GPU is not going to used for gaming (if at all possible). > It is likely to take a few years before something useful will come out = > of it. In the meanwhile, unless you want to use several GPUs which = > might not be a bad thing as a lot of monitors these days have several = > inputs, you can resort to using a remote desktop client to integrate = > one machine with another. Virtualbox for example use RDP through which = > you can interact with your virtual machine. In a similar manner you = > can set up a VNC server on your Linux host and establish a connection = > to it through your Windows VM. You will not get full 3D functionality = > (such as Aqua) through the client although there is a growing support = > for it through VirtualGL extensions that are coming to VNC and perhaps = > the Spice protocol. But some clients might even allow for seamless = > mode that lets you mix Linux and Windows windows on the same desktop = > like this for example: > > http://i.techrepublic.com.com/blogs/seamless.png > http://www.youtube.com/watch?v=3DeQr8iI0yZH4 > > > Just keep in mind that this is still a little bit of uncharted = > territory so there may be a few bumps on the way and it may not work = > as smooth as you would desire. > > From everything I've read, solutions that rely on any form of remote = display protocols would be limited to a subset of Direct3D functions. = Furthermore, these would vary from one implementation to another, thus = making them far less attractive for gaming than VGA passthrough... Well, = in my opinion anyway. VirtualBox's seamless mode is pretty nifty. But it's a Type 2 Hypervisor = and relies on paravirtualized drivers that also suffer from the same = limitations as remote display protocols. It's great for most things, but = gaming is not one of them. And I'm speaking from personal experience. = Though I haven't used them myself, the same would seem to hold true of = Parallel's and VMWare's 'Workstation' offerings. At least, as far as = I've gathered. FYI, the Type 1 Hypervisors from Parallel's and VMWare* are priced = waaayyy outside my budget. *I only found out about VMWare's 'free' vSphere after I'd written this = response. > > I see that your demands are somewhat multifaceted. I believe that you = > also want to use diffent services such as using your machine as a file = > server with the possible intention of using filesystems such as ZFS. = > If you do, you should be careful with your selection of hardware for = > these particular purposes. If you want to get full protection against = > data corruption from ZFS, your choice of hardware gets rather limited = > when it comes to choice of hard drives, host bus adapter and network = > controller. The most stable implementation of ZFS is found with = > Illumos based operating systems (such as OpenIndiana, SmartOS, OmniOS, = > Belenix etc) or Solaris if you choose to download it from Oracle's = > website. With these operating systems you are most likely to want to = > use hardware that has certified drivers for it. That way you are less = > likely to run into problems later on. That implies that you will be = > limited to choosing Intel based network adapters and LSI based SAS = > controllers. There should be _no_ hardware RAID functionality in the = > SAS controller that merely should be run in IT mode (or = > Initiator-Target mode). That requires the LSI controller to be flashed = > with IT firmware in most cases. The objective here is to make sure = > that _all_ errors that might occur with the hard drives are reported = > all the way to the software level and that nothing is concealed of = > obfuscated by internal error handling in the hardware. It is therefore = > recommended to use SAS hard drives instead of S-ATA (which also are = > fully compatible with SAS controllers). SAS hard drives are not much = > more expensive than similar SATA drives and you get a higher = > reliability out of them. It is also recommended to have at least two = > drive redundancy simply because if one drive is dead and you swap it, = > it is not uncommon that another drive dies in the rebuild process of = > the RAID cluster because of the added strain the rebuild process (or = > 'resilvering' as it is called in Solaris terms) put on the drives. Of = > course, the system should communicate directly to the hard drive = > hardware and not be obfuscated by some virtual abstraction layer in = > between which means that you either run ZFS on the metal or through = > PCI passthrough of the SAS (and perhaps also network) adapters. Also, = > it is highly recommended that you use ECC RAM for such applications = > and it doesn't hurt to dedicate a few gigs of it to the ZFS as RAM is = > used for cache. The good news is that most motherboards with good = > chipsets support ECC RAM even though you might not find anything about = > it in the user manuals. Again, thanks for the thorough explanation. This gives me a great deal = to think about. The more I learn about ZFS, the less appealing it = becomes. And by that I mean the confusion over which version of ZFS is = in what OS? And just how well maintained the OSes supporting ZFS are? = Now I have additional hardware considerations to keep in mind that may = (or may not) make the cost of ZFS RAID-Z pool comparable to a hardware = RAID5/6 solution anyway. Do you have any suggestions as to which of LSI = HBAs I should be considering? I haven't found an HCL for ZFS in my searches. Out of curiosity =97 and if you would happen to know =97 do you think what = you suggest about the HBA and SAS drives for ZFS also applies to Btrfs? = I'm assuming it would, but I'd appreciate some confirmation. It's funny how the "I" in RAID never really seems to apply... Especially = since it looks more and more like using ZFS or Btrfs will require I = commit myself, from the start, to one or the other and a discrete HBA. = Transitioning from an integrated SATA controller(s) and mdadm seems = rather impractical. If I understand what's involved in doing so = correctly. It may turn out that anything other than mdadm is price = prohibitive. > I admire your persistence with pursuing this undertaking and wish you = > the best of luck with it! > Robin. > > Thanks. I've invested too much time in research to not at least make the = attempt. Besides, if all else fails, I can fallback to a two box = solution. That is, if I can get my hypothetical virtualization box to = fit in my budget envelope... _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Mon Sep 24 03:46:26 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Mon, 24 Sep 2012 03:46:26 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TFzcD-0002OI-QJ; Mon, 24 Sep 2012 03:45:49 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TFzcB-0002Ni-Gd for xen-users@lists.xen.org; Mon, 24 Sep 2012 03:45:47 +0000 Received: from [85.158.143.99:58922] by server-3.bemta-4.messagelabs.com id 79/D2-10986-A67DF505; Mon, 24 Sep 2012 03:45:46 +0000 X-Env-Sender: shades_of_grey@earthlink.net X-Msg-Ref: server-4.tower-216.messagelabs.com!1348458343!26189222!1 X-Originating-IP: [209.86.89.61] X-SpamReason: No, hits=0.9 required=7.0 tests=sa_preprocessor: QmFkIElQOiAyMDkuODYuODkuNjEgPT4gMzc0OQ==\n,sa_preprocessor: QmFkIElQOiAyMDkuODYuODkuNjEgPT4gMzc0OQ==\n,HTML_20_30,HTML_MESSAGE, ML_RADAR_SPEW_LINKS_14,ML_RADAR_SPEW_LINKS_23,spamassassin: X-StarScan-Received: X-StarScan-Version: 6.6.1.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 18427 invoked from network); 24 Sep 2012 03:45:43 -0000 Received: from elasmtp-galgo.atl.sa.earthlink.net (HELO elasmtp-galgo.atl.sa.earthlink.net) (209.86.89.61) by server-4.tower-216.messagelabs.com with SMTP; 24 Sep 2012 03:45:43 -0000 DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=dk20050327; d=earthlink.net; b=X4BTuJ/Q8zIxaj3xKmtas02YUAI1de/OhKoz0eUiyqZVECrvwSKquTrSgJrHr80J; h=Received:Message-ID:Date:From:User-Agent:MIME-Version:To:Subject:References:In-Reply-To:Content-Type:X-ELNK-Trace:X-Originating-IP; Received: from [66.167.250.229] (helo=[192.168.1.13]) by elasmtp-galgo.atl.sa.earthlink.net with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.67) (envelope-from ) id 1TFzc6-0003F9-Tt for xen-users@lists.xen.org; Sun, 23 Sep 2012 23:45:43 -0400 Message-ID: <505FD765.6060205@earthlink.net> Date: Sun, 23 Sep 2012 23:45:41 -0400 From: ShadesOfGrey User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:15.0) Gecko/20120907 Thunderbird/15.0.1 MIME-Version: 1.0 To: xen-users@lists.xen.org References: <505B86AE.9040507@earthlink.net> <-4689096786842132042@unknownmsgid> In-Reply-To: <-4689096786842132042@unknownmsgid> X-ELNK-Trace: 0fe7bc40aa99bc8fc963772e86942a7b94f5150ab1c16ac0485087bba56e600948c845263905768382231d4ecb782501350badd9bab72f9c350badd9bab72f9c X-Originating-IP: 66.167.250.229 Subject: Re: [Xen-users] Recommendations for Virtulization Hardware X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============0387764003728109116==" Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org This is a multi-part message in MIME format. --===============0387764003728109116== Content-Type: multipart/alternative; boundary="------------010503010701080102030601" This is a multi-part message in MIME format. --------------010503010701080102030601 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Sorry for the late response, I've had a lot to digest. On 09/21/2012 12:30 PM, Andrew Bobulsky wrote: > (CC'ing Casey on this, as I recommend his setup for an Intel-based solution) > > Hello ShadesOfGrey, > > Hehehe, talk about timing ;) > > > As one of the folks on the list who has done this---probably to the > most extreme degree---I can tell you it's good stuff. It brings the > joys of datacenter consolidation to your gaming desktop, and also to > your wallet ;) > > While my setup is now slightly dated, the 990FX chipset is still at > the top of the AMD offering, so you can shop around on CPUs, and buy a > cheaper "secondary" USB controller if you're not looking to cram in a > 4-to-1 ratio. I've never had much success passing through the onboard > USB from an AMD system, so I highly recommend picking up a little PCIe > x1 controller at the least. That said, I'm convinced that highpoint > has one of the coincidentally-best products on the market for people > looking to do this, but I digress! > > Take a look at, specifically, this post I made to the list some months > back, and I'll follow with some errata: > http://lists.xen.org/archives/html/xen-users/2012-05/msg00328.html I'd like to support AMD... I really would!... if for no other reason than I'd hate to see what would happen if Intel were the only choice for x86 CPUs. But I just can't see myself justifying an AMD build. IIRC, the AMD FX-8150 was roughly on par with an Intel Core i5 2600. I don't think I'll be able to get the level of performance or longevity (five to ten years) I want from an AMD processor. From what Casey DeLorme said in his response, I don't think I'll have a problem with USB if I follow his advice on motherboards. But I'll certainly keep in mind that I may need to pick up additional hardware like an USB HBA. But I'm more concerned about audio. You said you used a "Generic Piece of Crap" USB adapter and advised getting several in case of failure. I'd prefer to get something, shall we say, "more reliable." ;-) To that end, I was thinking of picking up a PCIe or PCI sound card from the Xonar series. But there's a potential problem when passing the PCIe versions through: From what I understand, the PCIe Xonar cards use a PCI to PCIe bridge, which is not uncommon for a lot of hardware. The problem arises in the way in which ASUS implemented this bridge. IIRC, the sound device doesn't appear to be recognized by Xen (or the VM, I forget which), even though it is present. Unfortunately, I can't find the exact reference now. But this posting on the Xen Development list sounds like it resembles the issue I read about. Assuming that's the issue, has Xen been patched to deal with this? If not, could someone recommend a decent PCIe sound card that either doesn't rely on a PCI bridge or presently works with Xen (if not KVM, too)? Of course, this would be moot if I go with a motherboard that has legacy PCI slots. But one of the candidates I was considering is PCIe only. > First, I've tested all of the hardware in the build that I > recommended, and indeed ended up building a four-headed unit. It works > like magic. Came in handy a few weeks ago when several of my friends > and I piled into a couple cars for a vacation where we wanted to play > games (yup, we're total nerds), but we couldn't fit four desktop cases > in addition to our stuff in the cars. :) That sounds sweet. I might ask later how exactly you multiplexed things so you could get four users playing games, at the same time. Because, I have two cases where my original plan may not work as expected. First case, I was going to use Synergy to handle sharing the keyboard and mouse. But that may not work for all potential VMs, as Synergy may not be available to the given OS of a specific VM. Secondly, I have an adolescent nephew who is always disappointed when he visits. The reason being that the only system I have ATM that has the hardware for gaming is a Linux box. Unfortunately for me, he doesn't like any of the Linux games I can acquire (and that my sister would let him play anyway), save one. > > Second, by the time I got around to building it, the Antec One Hundred > wasn't available. Finding a case that supports 8 expansion slots is a > tough thing, but I found another similarly priced one, and it was a > dream to build. I recommend it highly if you think you may want to > max out your slots and/or go deeper down the rabbit hole with > consolidated desktops: > http://www.newegg.com/Product/Product.aspx?Item=N82E16811112238 > > Aside from being a very solid case for the price point (good features > for screwless installation as well), to give you an idea of the size, > it is laid out in such a way that I could fit dual-GPU cards in it > (Radeon 5970s). I ultimately had to remove the HDD mounts to pull it > off, but you shouldn't have that problem... Mostly because AMDs dual > GPU cards won't work for this, so don't buy one for this build. It's > a problem with the PCIe switching hardware (well, the firmware > thereof, probably) that they use. I'll save you the rambling, but > let's just say that it should work, but doesn't :( > > Also, the case does look good! ;) Personally, I've gravitated toward the Xigmatek Elysium. Yeah, it's quite a bit more expensive than either the Antec or Lian Li you recommended. But, then again, it is a monster of a case. My only regret is that I couldn't find the CCC-HSA0DS-U04 model anywhere (well, within the states anyway). Now it appears my second choice, the CCC-HSA0DS-U03 version has been discontinued (per Newegg) and is considerably more expensive than other the models among the retailers I found that carry it... Sorry for the mini-rant. I just never could comprehend the windowed side panel fad. And the two remaining available SKUs (U01 & U02) for the Elysium case have side panel windows. > Finally, and this is unfortunate, for the AMD build, *I* recommend you > use ESXi. While Xen _does_ work with the hardware that I've listed, > I've never been able to get the VMs to work properly with the GPLPV > drivers, and these are crucial to performance. I really, really want > to bring this project back up on Xen though, and will try again now > that 4.2 has gone RTM. If you aren't buying anytime soon and would > like to hit me up in a few weeks, by all means drop me a line, and > I'll let you know if I've gotten around to it. > Would you happen to know if the "free" version of VMware's vSphere Hypervisor is a capable 'alternative' to KVM or Xen for what I'm looking to do? VMWare's FAQ concerning vSphere states that it "was formerly known as VMware ESXi Single Server or free ESXi (often abbreviated to simply "VMware ESXi")." But the VMWare Compatibility Guide , doesn't have an entry for vSphere and the the FAQ doesn't specify which version of ESXi vSphere it is based on. I'd like to at least test as many 'free' solutions as possible. As long as they have the potential to meet my stated requirements, anyway. > > ---------------- > > > So, for the Intel route! > > Casey DeLorme has, just this week, posted a fantastic set of detailed > videos and documentation on his setup, where he basically does exactly > what you're trying to accomplish. You can find links to all of the > documentation, which I'm pretty sure covers his exact hardware, along > with videos of the installation process he used and a detailed, > written guide. Fine work if you ask me ;) > > http://lists.xen.org/archives/html/xen-users/2012-09/msg00191.html > > As far as his hardware goes, I'm not sure if it's the latest Intel > chips or not. I've been eyeballing the i7-3770 myself (NOT the 3770K, > that one will not work, as [in my opinion] Intel has a pension for > artificially crippling their products for profit). Haven't found a > board yet, but then again I started eyeballing hardware a day or two > ago. > It. Is. An. AWESOME. Thing. If Casey hadn't written such a guide, that's what I had intended to do myself. I may yet do so if I use different hardware and/or software... Or perhaps he'd be so kind enough to allow me to piggyback off of his wiki entry if I (as I suspect) settle on Xen? Anyway, as he said in his response, he has upgraded his hardware since writing the guide. And the motherboard he is currently using was one I originally selected as a candidate for my build. Though, I'm now considering other motherboards. I've already exceeded the upper limits of my budget and I have yet to factor in the cost of a discrete GPU. I was looking for more information on how well any given GPU would behave under virtualization and meet certain use-case scenarios, Robin Axelsson really helped there. So, finding way to cut costs here and there, without sacrificing core functionality, really wouldn't hurt. ;-) I do have to agree with you about Intel and their artificial profit centers. I was surprised they bothered with VT-d support in anything other than the Xeon line after all I had learned. Besides the inconsistent support for VT-d among K series Sandy Bridge Core i processors, there's the issue of chipset support. The Zxx desktop chipset is intended for enthusiasts, yet VT-d support is not 'officially sanctioned' by Intel on that chipset. Some nonsense about it not meeting their internal testing standards. No, instead you either use the Qxx or B75 desktop chipsets, switch to server chipsets (and the various tradeoffs that come with them), or hope that your chosen motherboard manufacturer 'unofficially' officially support VT-d on motherboards with other chipsets. As ASRock does and Gigabyte may unofficially support through 'beta' firmware versions (I still haven't nailed down whether the G1.Sniper 3 has really and truly has VT-d support). MSI might, but so far their motherbaord offerings haven't appealed to me in a more general sense. Anyway, the confusing nomenclature and vague technical specifications from Intel all remind me of the 386/486, SX/DX days. And this is why I really hope AMD can get their act together. Without competition, Intel will go back to really gouging its users! > > Cheers, > Andrew Bobulsky > Thanks a heap, Andrew. --------------010503010701080102030601 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit
Sorry for the late response, I've had a lot to digest.

On 09/21/2012 12:30 PM, Andrew Bobulsky wrote:
(CC'ing Casey on this, as I recommend his setup for an Intel-based solution)

Hello ShadesOfGrey,

Hehehe, talk about timing ;)


As one of the folks on the list who has done this---probably to the
most extreme degree---I can tell you it's good stuff.  It brings the
joys of datacenter consolidation to your gaming desktop, and also to
your wallet ;)

While my setup is now slightly dated, the 990FX chipset is still at
the top of the AMD offering, so you can shop around on CPUs, and buy a
cheaper "secondary" USB controller if you're not looking to cram in a
4-to-1 ratio.  I've never had much success passing through the onboard
USB from an AMD system, so I highly recommend picking up a little PCIe
x1 controller at the least.  That said, I'm convinced that highpoint
has one of the coincidentally-best products on the market for people
looking to do this, but I digress!

Take a look at, specifically, this post I made to the list some months
back, and I'll follow with some errata:
http://lists.xen.org/archives/html/xen-users/2012-05/msg00328.html
I'd like to support AMD... I really would!... if for no other reason than I'd hate to see what would happen if Intel were the only choice for x86 CPUs.  But I just can't see myself justifying an AMD build.  IIRC, the AMD FX-8150 was roughly on par with an Intel Core i5 2600.  I don't think I'll be able to get the level of performance or longevity (five to ten years) I want from an AMD processor.

From what Casey DeLorme said in his response, I don't think I'll have a problem with USB if I follow his advice on motherboards.  But I'll certainly keep in mind that I may need to pick up additional hardware like an USB HBA.  But I'm more concerned about audio.  You said you used a "Generic Piece of Crap" USB adapter and advised getting several in case of failure.  I'd prefer to get something, shall we say, "more reliable." ;-) To that end, I was thinking of picking up a PCIe or PCI sound card from the Xonar series.  But there's a potential problem when passing the PCIe versions through:  From what I understand, the PCIe Xonar cards use a PCI to PCIe bridge, which is not uncommon for a lot of hardware.  The problem arises in the way in which ASUS implemented this bridge.  IIRC, the sound device doesn't appear to be recognized by Xen (or the VM, I forget which), even though it is present.  Unfortunately, I can't find the exact reference now.  But this posting on the Xen Development list sounds like it resembles the issue I read about.  Assuming that's the issue, has Xen been patched to deal with this?  If not, could someone recommend  a decent PCIe sound card that either doesn't rely on a PCI bridge  or presently works with Xen (if not KVM, too)?  Of course, this would be moot if I go with a motherboard that has legacy PCI slots.  But one of the candidates I was considering is PCIe only.
 
First, I've tested all of the hardware in the build that I
recommended, and indeed ended up building a four-headed unit. It works
like magic. Came in handy a few weeks ago when several of my friends
and I piled into a couple cars for a vacation where we wanted to play
games (yup, we're total nerds), but we couldn't fit four desktop cases
in addition to our stuff in the cars. :)
That sounds sweet.  I might ask later how exactly you multiplexed things so you could get four users playing games, at the same time. Because, I have two cases where my original plan may not work as expected.  First case, I was going to use Synergy to handle sharing the keyboard and mouse.  But that may not work for all potential VMs, as Synergy may not be available to the given OS of a specific VM.  Secondly, I have an adolescent nephew who is always disappointed when he visits.  The reason being that the only system I have ATM that has the hardware for gaming is a Linux box.  Unfortunately for me, he doesn't like any of the Linux games I can acquire (and that my sister would let him play anyway), save one.
 

Second, by the time I got around to building it, the Antec One Hundred
wasn't available. Finding a case that supports 8 expansion slots is a
tough thing, but I found another similarly priced one, and it was a
dream to build.  I recommend it highly if you think you may want to
max out your slots and/or go deeper down the rabbit hole with
consolidated desktops:
http://www.newegg.com/Product/Product.aspx?Item=N82E16811112238

Aside from being a very solid case for the price point (good features
for screwless installation as well), to give you an idea of the size,
it is laid out in such a way that I could fit dual-GPU cards in it
(Radeon 5970s).  I ultimately had to remove the HDD mounts to pull it
off, but you shouldn't have that problem... Mostly because AMDs dual
GPU cards won't work for this, so don't buy one for this build.  It's
a problem with the PCIe switching hardware (well, the firmware
thereof, probably) that they use.  I'll save you the rambling, but
let's just say that it should work, but doesn't :(

Also, the case does look good! ;)
Personally, I've gravitated toward the Xigmatek Elysium.  Yeah, it's quite a bit more expensive than either the Antec or Lian Li you recommended.  But, then again, it is a monster of a case.  My only regret is that I couldn't find the CCC-HSA0DS-U04 model anywhere (well, within the states anyway).  Now it appears my second choice, the CCC-HSA0DS-U03 version has been discontinued (per Newegg) and is considerably more expensive than other the models among the retailers I found that carry it...

Sorry for the mini-rant.  I just never could comprehend the windowed side panel fad.  And the two remaining available SKUs (U01 & U02) for the Elysium case have side panel windows. 
Finally, and this is unfortunate, for the AMD build, *I* recommend you
use ESXi. While Xen _does_ work with the hardware that I've listed,
I've never been able to get the VMs to work properly with the GPLPV
drivers, and these are crucial to performance.  I really, really want
to bring this project back up on Xen though, and will try again now
that 4.2 has gone RTM.  If you aren't buying anytime soon and would
like to hit me up in a few weeks, by all means drop me a line, and
I'll let you know if I've gotten around to it.
Would you happen to know if the "free" version of VMware's vSphere Hypervisor is a capable 'alternative' to KVM or Xen for what I'm looking to do?  VMWare's FAQ concerning vSphere states that it "was formerly known as VMware ESXi Single Server or free ESXi (often abbreviated to simply “VMware ESXi”)."  But the VMWare Compatibility Guide, doesn't have an entry for vSphere and the the FAQ doesn't specify which version of ESXi vSphere it is based on.

I'd like to at least test as many 'free' solutions as possible.  As long as they have the potential to meet my stated requirements, anyway.
 

----------------


So, for the Intel route!

Casey DeLorme has, just this week, posted a fantastic set of detailed
videos and documentation on his setup, where he basically does exactly
what you're trying to accomplish.  You can find links to all of the
documentation, which I'm pretty sure covers his exact hardware, along
with videos of the installation process he used and a detailed,
written guide. Fine work if you ask me ;)

http://lists.xen.org/archives/html/xen-users/2012-09/msg00191.html

As far as his hardware goes, I'm not sure if it's the latest Intel
chips or not.  I've been eyeballing the i7-3770 myself (NOT the 3770K,
that one will not work, as [in my opinion] Intel has a pension for
artificially crippling their products for profit).  Haven't found a
board yet, but then again I started eyeballing hardware a day or two
ago.
It. Is. An. AWESOME. Thing.

If Casey hadn't written such a guide, that's what I had intended to do myself.  I may yet do so if I use different hardware and/or software...  Or perhaps he'd be so kind enough to allow me to piggyback off of his wiki entry if I (as I suspect) settle on Xen?  Anyway, as he said in his response, he has upgraded his hardware since writing the guide.  And the motherboard he is currently using was one I originally selected as a candidate for my build.  Though, I'm now considering other motherboards.  I've already exceeded the upper limits of my budget and I have yet to factor in the cost of a discrete GPU.  I was looking for more information on how well any given GPU would behave under virtualization and meet certain use-case scenarios,  Robin Axelsson really helped there.

So, finding way to cut costs here and there, without sacrificing core functionality, really wouldn't hurt. ;-)

I do have to agree with you about Intel and their artificial profit centers.  I was surprised they bothered with VT-d support in anything other than the Xeon line after all I had learned.  Besides the inconsistent support for VT-d among K series Sandy Bridge Core i processors, there's the issue of chipset support.  The Zxx desktop chipset is intended for enthusiasts, yet VT-d support is not 'officially sanctioned' by Intel on that chipset.  Some nonsense about it not meeting their internal testing standards.  No, instead you either use the Qxx or B75 desktop chipsets, switch to server chipsets (and the various tradeoffs that come with them), or hope  that your chosen motherboard manufacturer 'unofficially' officially support VT-d on motherboards with other chipsets.  As ASRock does and Gigabyte may unofficially support through 'beta' firmware versions (I still haven't nailed down whether the G1.Sniper 3 has really and truly has VT-d support).  MSI might, but so far their motherbaord offerings haven't appealed to me in a more general sense.  Anyway, the confusing nomenclature and vague technical specifications from Intel all remind me of the 386/486, SX/DX days.  And this is why I really hope AMD can get their act together.  Without competition, Intel will go back to really gouging its users! 

Cheers,
Andrew Bobulsky

Thanks a heap, Andrew.


--------------010503010701080102030601-- --===============0387764003728109116== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users --===============0387764003728109116==-- From xen-users-bounces@lists.xen.org Mon Sep 24 03:46:26 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Mon, 24 Sep 2012 03:46:26 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TFzcD-0002OI-QJ; Mon, 24 Sep 2012 03:45:49 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TFzcB-0002Ni-Gd for xen-users@lists.xen.org; Mon, 24 Sep 2012 03:45:47 +0000 Received: from [85.158.143.99:58922] by server-3.bemta-4.messagelabs.com id 79/D2-10986-A67DF505; Mon, 24 Sep 2012 03:45:46 +0000 X-Env-Sender: shades_of_grey@earthlink.net X-Msg-Ref: server-4.tower-216.messagelabs.com!1348458343!26189222!1 X-Originating-IP: [209.86.89.61] X-SpamReason: No, hits=0.9 required=7.0 tests=sa_preprocessor: QmFkIElQOiAyMDkuODYuODkuNjEgPT4gMzc0OQ==\n,sa_preprocessor: QmFkIElQOiAyMDkuODYuODkuNjEgPT4gMzc0OQ==\n,HTML_20_30,HTML_MESSAGE, ML_RADAR_SPEW_LINKS_14,ML_RADAR_SPEW_LINKS_23,spamassassin: X-StarScan-Received: X-StarScan-Version: 6.6.1.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 18427 invoked from network); 24 Sep 2012 03:45:43 -0000 Received: from elasmtp-galgo.atl.sa.earthlink.net (HELO elasmtp-galgo.atl.sa.earthlink.net) (209.86.89.61) by server-4.tower-216.messagelabs.com with SMTP; 24 Sep 2012 03:45:43 -0000 DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=dk20050327; d=earthlink.net; b=X4BTuJ/Q8zIxaj3xKmtas02YUAI1de/OhKoz0eUiyqZVECrvwSKquTrSgJrHr80J; h=Received:Message-ID:Date:From:User-Agent:MIME-Version:To:Subject:References:In-Reply-To:Content-Type:X-ELNK-Trace:X-Originating-IP; Received: from [66.167.250.229] (helo=[192.168.1.13]) by elasmtp-galgo.atl.sa.earthlink.net with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.67) (envelope-from ) id 1TFzc6-0003F9-Tt for xen-users@lists.xen.org; Sun, 23 Sep 2012 23:45:43 -0400 Message-ID: <505FD765.6060205@earthlink.net> Date: Sun, 23 Sep 2012 23:45:41 -0400 From: ShadesOfGrey User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:15.0) Gecko/20120907 Thunderbird/15.0.1 MIME-Version: 1.0 To: xen-users@lists.xen.org References: <505B86AE.9040507@earthlink.net> <-4689096786842132042@unknownmsgid> In-Reply-To: <-4689096786842132042@unknownmsgid> X-ELNK-Trace: 0fe7bc40aa99bc8fc963772e86942a7b94f5150ab1c16ac0485087bba56e600948c845263905768382231d4ecb782501350badd9bab72f9c350badd9bab72f9c X-Originating-IP: 66.167.250.229 Subject: Re: [Xen-users] Recommendations for Virtulization Hardware X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============0387764003728109116==" Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org This is a multi-part message in MIME format. --===============0387764003728109116== Content-Type: multipart/alternative; boundary="------------010503010701080102030601" This is a multi-part message in MIME format. --------------010503010701080102030601 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Sorry for the late response, I've had a lot to digest. On 09/21/2012 12:30 PM, Andrew Bobulsky wrote: > (CC'ing Casey on this, as I recommend his setup for an Intel-based solution) > > Hello ShadesOfGrey, > > Hehehe, talk about timing ;) > > > As one of the folks on the list who has done this---probably to the > most extreme degree---I can tell you it's good stuff. It brings the > joys of datacenter consolidation to your gaming desktop, and also to > your wallet ;) > > While my setup is now slightly dated, the 990FX chipset is still at > the top of the AMD offering, so you can shop around on CPUs, and buy a > cheaper "secondary" USB controller if you're not looking to cram in a > 4-to-1 ratio. I've never had much success passing through the onboard > USB from an AMD system, so I highly recommend picking up a little PCIe > x1 controller at the least. That said, I'm convinced that highpoint > has one of the coincidentally-best products on the market for people > looking to do this, but I digress! > > Take a look at, specifically, this post I made to the list some months > back, and I'll follow with some errata: > http://lists.xen.org/archives/html/xen-users/2012-05/msg00328.html I'd like to support AMD... I really would!... if for no other reason than I'd hate to see what would happen if Intel were the only choice for x86 CPUs. But I just can't see myself justifying an AMD build. IIRC, the AMD FX-8150 was roughly on par with an Intel Core i5 2600. I don't think I'll be able to get the level of performance or longevity (five to ten years) I want from an AMD processor. From what Casey DeLorme said in his response, I don't think I'll have a problem with USB if I follow his advice on motherboards. But I'll certainly keep in mind that I may need to pick up additional hardware like an USB HBA. But I'm more concerned about audio. You said you used a "Generic Piece of Crap" USB adapter and advised getting several in case of failure. I'd prefer to get something, shall we say, "more reliable." ;-) To that end, I was thinking of picking up a PCIe or PCI sound card from the Xonar series. But there's a potential problem when passing the PCIe versions through: From what I understand, the PCIe Xonar cards use a PCI to PCIe bridge, which is not uncommon for a lot of hardware. The problem arises in the way in which ASUS implemented this bridge. IIRC, the sound device doesn't appear to be recognized by Xen (or the VM, I forget which), even though it is present. Unfortunately, I can't find the exact reference now. But this posting on the Xen Development list sounds like it resembles the issue I read about. Assuming that's the issue, has Xen been patched to deal with this? If not, could someone recommend a decent PCIe sound card that either doesn't rely on a PCI bridge or presently works with Xen (if not KVM, too)? Of course, this would be moot if I go with a motherboard that has legacy PCI slots. But one of the candidates I was considering is PCIe only. > First, I've tested all of the hardware in the build that I > recommended, and indeed ended up building a four-headed unit. It works > like magic. Came in handy a few weeks ago when several of my friends > and I piled into a couple cars for a vacation where we wanted to play > games (yup, we're total nerds), but we couldn't fit four desktop cases > in addition to our stuff in the cars. :) That sounds sweet. I might ask later how exactly you multiplexed things so you could get four users playing games, at the same time. Because, I have two cases where my original plan may not work as expected. First case, I was going to use Synergy to handle sharing the keyboard and mouse. But that may not work for all potential VMs, as Synergy may not be available to the given OS of a specific VM. Secondly, I have an adolescent nephew who is always disappointed when he visits. The reason being that the only system I have ATM that has the hardware for gaming is a Linux box. Unfortunately for me, he doesn't like any of the Linux games I can acquire (and that my sister would let him play anyway), save one. > > Second, by the time I got around to building it, the Antec One Hundred > wasn't available. Finding a case that supports 8 expansion slots is a > tough thing, but I found another similarly priced one, and it was a > dream to build. I recommend it highly if you think you may want to > max out your slots and/or go deeper down the rabbit hole with > consolidated desktops: > http://www.newegg.com/Product/Product.aspx?Item=N82E16811112238 > > Aside from being a very solid case for the price point (good features > for screwless installation as well), to give you an idea of the size, > it is laid out in such a way that I could fit dual-GPU cards in it > (Radeon 5970s). I ultimately had to remove the HDD mounts to pull it > off, but you shouldn't have that problem... Mostly because AMDs dual > GPU cards won't work for this, so don't buy one for this build. It's > a problem with the PCIe switching hardware (well, the firmware > thereof, probably) that they use. I'll save you the rambling, but > let's just say that it should work, but doesn't :( > > Also, the case does look good! ;) Personally, I've gravitated toward the Xigmatek Elysium. Yeah, it's quite a bit more expensive than either the Antec or Lian Li you recommended. But, then again, it is a monster of a case. My only regret is that I couldn't find the CCC-HSA0DS-U04 model anywhere (well, within the states anyway). Now it appears my second choice, the CCC-HSA0DS-U03 version has been discontinued (per Newegg) and is considerably more expensive than other the models among the retailers I found that carry it... Sorry for the mini-rant. I just never could comprehend the windowed side panel fad. And the two remaining available SKUs (U01 & U02) for the Elysium case have side panel windows. > Finally, and this is unfortunate, for the AMD build, *I* recommend you > use ESXi. While Xen _does_ work with the hardware that I've listed, > I've never been able to get the VMs to work properly with the GPLPV > drivers, and these are crucial to performance. I really, really want > to bring this project back up on Xen though, and will try again now > that 4.2 has gone RTM. If you aren't buying anytime soon and would > like to hit me up in a few weeks, by all means drop me a line, and > I'll let you know if I've gotten around to it. > Would you happen to know if the "free" version of VMware's vSphere Hypervisor is a capable 'alternative' to KVM or Xen for what I'm looking to do? VMWare's FAQ concerning vSphere states that it "was formerly known as VMware ESXi Single Server or free ESXi (often abbreviated to simply "VMware ESXi")." But the VMWare Compatibility Guide , doesn't have an entry for vSphere and the the FAQ doesn't specify which version of ESXi vSphere it is based on. I'd like to at least test as many 'free' solutions as possible. As long as they have the potential to meet my stated requirements, anyway. > > ---------------- > > > So, for the Intel route! > > Casey DeLorme has, just this week, posted a fantastic set of detailed > videos and documentation on his setup, where he basically does exactly > what you're trying to accomplish. You can find links to all of the > documentation, which I'm pretty sure covers his exact hardware, along > with videos of the installation process he used and a detailed, > written guide. Fine work if you ask me ;) > > http://lists.xen.org/archives/html/xen-users/2012-09/msg00191.html > > As far as his hardware goes, I'm not sure if it's the latest Intel > chips or not. I've been eyeballing the i7-3770 myself (NOT the 3770K, > that one will not work, as [in my opinion] Intel has a pension for > artificially crippling their products for profit). Haven't found a > board yet, but then again I started eyeballing hardware a day or two > ago. > It. Is. An. AWESOME. Thing. If Casey hadn't written such a guide, that's what I had intended to do myself. I may yet do so if I use different hardware and/or software... Or perhaps he'd be so kind enough to allow me to piggyback off of his wiki entry if I (as I suspect) settle on Xen? Anyway, as he said in his response, he has upgraded his hardware since writing the guide. And the motherboard he is currently using was one I originally selected as a candidate for my build. Though, I'm now considering other motherboards. I've already exceeded the upper limits of my budget and I have yet to factor in the cost of a discrete GPU. I was looking for more information on how well any given GPU would behave under virtualization and meet certain use-case scenarios, Robin Axelsson really helped there. So, finding way to cut costs here and there, without sacrificing core functionality, really wouldn't hurt. ;-) I do have to agree with you about Intel and their artificial profit centers. I was surprised they bothered with VT-d support in anything other than the Xeon line after all I had learned. Besides the inconsistent support for VT-d among K series Sandy Bridge Core i processors, there's the issue of chipset support. The Zxx desktop chipset is intended for enthusiasts, yet VT-d support is not 'officially sanctioned' by Intel on that chipset. Some nonsense about it not meeting their internal testing standards. No, instead you either use the Qxx or B75 desktop chipsets, switch to server chipsets (and the various tradeoffs that come with them), or hope that your chosen motherboard manufacturer 'unofficially' officially support VT-d on motherboards with other chipsets. As ASRock does and Gigabyte may unofficially support through 'beta' firmware versions (I still haven't nailed down whether the G1.Sniper 3 has really and truly has VT-d support). MSI might, but so far their motherbaord offerings haven't appealed to me in a more general sense. Anyway, the confusing nomenclature and vague technical specifications from Intel all remind me of the 386/486, SX/DX days. And this is why I really hope AMD can get their act together. Without competition, Intel will go back to really gouging its users! > > Cheers, > Andrew Bobulsky > Thanks a heap, Andrew. --------------010503010701080102030601 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit
Sorry for the late response, I've had a lot to digest.

On 09/21/2012 12:30 PM, Andrew Bobulsky wrote:
(CC'ing Casey on this, as I recommend his setup for an Intel-based solution)

Hello ShadesOfGrey,

Hehehe, talk about timing ;)


As one of the folks on the list who has done this---probably to the
most extreme degree---I can tell you it's good stuff.  It brings the
joys of datacenter consolidation to your gaming desktop, and also to
your wallet ;)

While my setup is now slightly dated, the 990FX chipset is still at
the top of the AMD offering, so you can shop around on CPUs, and buy a
cheaper "secondary" USB controller if you're not looking to cram in a
4-to-1 ratio.  I've never had much success passing through the onboard
USB from an AMD system, so I highly recommend picking up a little PCIe
x1 controller at the least.  That said, I'm convinced that highpoint
has one of the coincidentally-best products on the market for people
looking to do this, but I digress!

Take a look at, specifically, this post I made to the list some months
back, and I'll follow with some errata:
http://lists.xen.org/archives/html/xen-users/2012-05/msg00328.html
I'd like to support AMD... I really would!... if for no other reason than I'd hate to see what would happen if Intel were the only choice for x86 CPUs.  But I just can't see myself justifying an AMD build.  IIRC, the AMD FX-8150 was roughly on par with an Intel Core i5 2600.  I don't think I'll be able to get the level of performance or longevity (five to ten years) I want from an AMD processor.

From what Casey DeLorme said in his response, I don't think I'll have a problem with USB if I follow his advice on motherboards.  But I'll certainly keep in mind that I may need to pick up additional hardware like an USB HBA.  But I'm more concerned about audio.  You said you used a "Generic Piece of Crap" USB adapter and advised getting several in case of failure.  I'd prefer to get something, shall we say, "more reliable." ;-) To that end, I was thinking of picking up a PCIe or PCI sound card from the Xonar series.  But there's a potential problem when passing the PCIe versions through:  From what I understand, the PCIe Xonar cards use a PCI to PCIe bridge, which is not uncommon for a lot of hardware.  The problem arises in the way in which ASUS implemented this bridge.  IIRC, the sound device doesn't appear to be recognized by Xen (or the VM, I forget which), even though it is present.  Unfortunately, I can't find the exact reference now.  But this posting on the Xen Development list sounds like it resembles the issue I read about.  Assuming that's the issue, has Xen been patched to deal with this?  If not, could someone recommend  a decent PCIe sound card that either doesn't rely on a PCI bridge  or presently works with Xen (if not KVM, too)?  Of course, this would be moot if I go with a motherboard that has legacy PCI slots.  But one of the candidates I was considering is PCIe only.
 
First, I've tested all of the hardware in the build that I
recommended, and indeed ended up building a four-headed unit. It works
like magic. Came in handy a few weeks ago when several of my friends
and I piled into a couple cars for a vacation where we wanted to play
games (yup, we're total nerds), but we couldn't fit four desktop cases
in addition to our stuff in the cars. :)
That sounds sweet.  I might ask later how exactly you multiplexed things so you could get four users playing games, at the same time. Because, I have two cases where my original plan may not work as expected.  First case, I was going to use Synergy to handle sharing the keyboard and mouse.  But that may not work for all potential VMs, as Synergy may not be available to the given OS of a specific VM.  Secondly, I have an adolescent nephew who is always disappointed when he visits.  The reason being that the only system I have ATM that has the hardware for gaming is a Linux box.  Unfortunately for me, he doesn't like any of the Linux games I can acquire (and that my sister would let him play anyway), save one.
 

Second, by the time I got around to building it, the Antec One Hundred
wasn't available. Finding a case that supports 8 expansion slots is a
tough thing, but I found another similarly priced one, and it was a
dream to build.  I recommend it highly if you think you may want to
max out your slots and/or go deeper down the rabbit hole with
consolidated desktops:
http://www.newegg.com/Product/Product.aspx?Item=N82E16811112238

Aside from being a very solid case for the price point (good features
for screwless installation as well), to give you an idea of the size,
it is laid out in such a way that I could fit dual-GPU cards in it
(Radeon 5970s).  I ultimately had to remove the HDD mounts to pull it
off, but you shouldn't have that problem... Mostly because AMDs dual
GPU cards won't work for this, so don't buy one for this build.  It's
a problem with the PCIe switching hardware (well, the firmware
thereof, probably) that they use.  I'll save you the rambling, but
let's just say that it should work, but doesn't :(

Also, the case does look good! ;)
Personally, I've gravitated toward the Xigmatek Elysium.  Yeah, it's quite a bit more expensive than either the Antec or Lian Li you recommended.  But, then again, it is a monster of a case.  My only regret is that I couldn't find the CCC-HSA0DS-U04 model anywhere (well, within the states anyway).  Now it appears my second choice, the CCC-HSA0DS-U03 version has been discontinued (per Newegg) and is considerably more expensive than other the models among the retailers I found that carry it...

Sorry for the mini-rant.  I just never could comprehend the windowed side panel fad.  And the two remaining available SKUs (U01 & U02) for the Elysium case have side panel windows. 
Finally, and this is unfortunate, for the AMD build, *I* recommend you
use ESXi. While Xen _does_ work with the hardware that I've listed,
I've never been able to get the VMs to work properly with the GPLPV
drivers, and these are crucial to performance.  I really, really want
to bring this project back up on Xen though, and will try again now
that 4.2 has gone RTM.  If you aren't buying anytime soon and would
like to hit me up in a few weeks, by all means drop me a line, and
I'll let you know if I've gotten around to it.
Would you happen to know if the "free" version of VMware's vSphere Hypervisor is a capable 'alternative' to KVM or Xen for what I'm looking to do?  VMWare's FAQ concerning vSphere states that it "was formerly known as VMware ESXi Single Server or free ESXi (often abbreviated to simply “VMware ESXi”)."  But the VMWare Compatibility Guide, doesn't have an entry for vSphere and the the FAQ doesn't specify which version of ESXi vSphere it is based on.

I'd like to at least test as many 'free' solutions as possible.  As long as they have the potential to meet my stated requirements, anyway.
 

----------------


So, for the Intel route!

Casey DeLorme has, just this week, posted a fantastic set of detailed
videos and documentation on his setup, where he basically does exactly
what you're trying to accomplish.  You can find links to all of the
documentation, which I'm pretty sure covers his exact hardware, along
with videos of the installation process he used and a detailed,
written guide. Fine work if you ask me ;)

http://lists.xen.org/archives/html/xen-users/2012-09/msg00191.html

As far as his hardware goes, I'm not sure if it's the latest Intel
chips or not.  I've been eyeballing the i7-3770 myself (NOT the 3770K,
that one will not work, as [in my opinion] Intel has a pension for
artificially crippling their products for profit).  Haven't found a
board yet, but then again I started eyeballing hardware a day or two
ago.
It. Is. An. AWESOME. Thing.

If Casey hadn't written such a guide, that's what I had intended to do myself.  I may yet do so if I use different hardware and/or software...  Or perhaps he'd be so kind enough to allow me to piggyback off of his wiki entry if I (as I suspect) settle on Xen?  Anyway, as he said in his response, he has upgraded his hardware since writing the guide.  And the motherboard he is currently using was one I originally selected as a candidate for my build.  Though, I'm now considering other motherboards.  I've already exceeded the upper limits of my budget and I have yet to factor in the cost of a discrete GPU.  I was looking for more information on how well any given GPU would behave under virtualization and meet certain use-case scenarios,  Robin Axelsson really helped there.

So, finding way to cut costs here and there, without sacrificing core functionality, really wouldn't hurt. ;-)

I do have to agree with you about Intel and their artificial profit centers.  I was surprised they bothered with VT-d support in anything other than the Xeon line after all I had learned.  Besides the inconsistent support for VT-d among K series Sandy Bridge Core i processors, there's the issue of chipset support.  The Zxx desktop chipset is intended for enthusiasts, yet VT-d support is not 'officially sanctioned' by Intel on that chipset.  Some nonsense about it not meeting their internal testing standards.  No, instead you either use the Qxx or B75 desktop chipsets, switch to server chipsets (and the various tradeoffs that come with them), or hope  that your chosen motherboard manufacturer 'unofficially' officially support VT-d on motherboards with other chipsets.  As ASRock does and Gigabyte may unofficially support through 'beta' firmware versions (I still haven't nailed down whether the G1.Sniper 3 has really and truly has VT-d support).  MSI might, but so far their motherbaord offerings haven't appealed to me in a more general sense.  Anyway, the confusing nomenclature and vague technical specifications from Intel all remind me of the 386/486, SX/DX days.  And this is why I really hope AMD can get their act together.  Without competition, Intel will go back to really gouging its users! 

Cheers,
Andrew Bobulsky

Thanks a heap, Andrew.


--------------010503010701080102030601-- --===============0387764003728109116== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users --===============0387764003728109116==-- From xen-users-bounces@lists.xen.org Mon Sep 24 03:46:35 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Mon, 24 Sep 2012 03:46:35 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TFzcR-0002RQ-IM; Mon, 24 Sep 2012 03:46:03 +0000 Received: from mail27.messagelabs.com ([193.109.254.147]) by lists.xen.org with smtp (Exim 4.72) (envelope-from ) id 1TFzcP-0002Pq-0G for xen-users@lists.xen.org; Mon, 24 Sep 2012 03:46:01 +0000 X-Env-Sender: shades_of_grey@earthlink.net X-Msg-Ref: server-11.tower-27.messagelabs.com!1348458352!2790683!1 X-Originating-IP: [209.86.89.66] X-SpamReason: No, hits=0.6 required=7.0 tests=BODY_RANDOM_LONG, HTML_30_40,HTML_MESSAGE,ML_RADAR_SPEW_LINKS_14,spamassassin: X-StarScan-Received: X-StarScan-Version: 6.6.1.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 8873 invoked from network); 24 Sep 2012 03:45:52 -0000 Received: from elasmtp-spurfowl.atl.sa.earthlink.net (HELO elasmtp-spurfowl.atl.sa.earthlink.net) (209.86.89.66) by server-11.tower-27.messagelabs.com with SMTP; 24 Sep 2012 03:45:52 -0000 DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=dk20050327; d=earthlink.net; b=ADTKgYyPE6CncvVf6gmsGoFEP6wNEXjgIU6tjQW9Sx+GX25d/xM/JsXQOfsagfNz; h=Received:Message-ID:Date:From:User-Agent:MIME-Version:To:Subject:References:In-Reply-To:Content-Type:X-ELNK-Trace:X-Originating-IP; Received: from [66.167.250.229] (helo=[192.168.1.13]) by elasmtp-spurfowl.atl.sa.earthlink.net with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.67) (envelope-from ) id 1TFzcF-0004cs-FB for xen-users@lists.xen.org; Sun, 23 Sep 2012 23:45:51 -0400 Message-ID: <505FD76E.6000707@earthlink.net> Date: Sun, 23 Sep 2012 23:45:50 -0400 From: ShadesOfGrey User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:15.0) Gecko/20120907 Thunderbird/15.0.1 MIME-Version: 1.0 To: xen-users@lists.xen.org References: <505B86AE.9040507@earthlink.net> <-4689096786842132042@unknownmsgid> In-Reply-To: X-ELNK-Trace: 0fe7bc40aa99bc8fc963772e86942a7b94f5150ab1c16ac0485087bba56e600995638eb3d9f495cc9482422fe497970b350badd9bab72f9c350badd9bab72f9c X-Originating-IP: 66.167.250.229 Subject: Re: [Xen-users] Recommendations for Virtulization Hardware X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============4209421940341483610==" Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org This is a multi-part message in MIME format. --===============4209421940341483610== Content-Type: multipart/alternative; boundary="------------010502070908050400020003" This is a multi-part message in MIME format. --------------010502070908050400020003 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Sorry for the late response, I've had a lot to digest. On 09/21/2012 01:02 PM, Casey DeLorme wrote: > Thanks for the CC Andrew, > > I responded in private since I didn't want to spam the list. > > Since we're on the subject of the latest hardware, my system was using > a Z68 Motherboard Chipset and Core i7 SandyBridge CPU (2600). I just > sold it to a friend and upgraded to the latest. > > Now running an IvyBridge 3770, Z77 Motherboard Chipset (ASRock Z77 > Extreme 9), and similar components for the rest. The Extreme 9 price > is extremely high, I wouldn't recommend it unless you have the money, > their Z77 Extreme 6 is priced at the same as the Z68 Extreme4 Gen3, > and has all the same features plus more USB 3.0. I would give that > one a shake if you are looking for newest components. The hardest > part of switching from the Extreme4 Gen3 was remapping the USB ports > to USB controllers by PCI BDF in Linux, because I haven't found an > easy way to do that using the systems information yet. > Funnily enough, the Extreme9 was one of my two original motherboard candidates, along with the Gigabyte G1.Sniper 3. Though I've expanded that list now to include all of ASRock's Z77 line of motherboards. I might even consider Z77 motherboards from other manufacturers, if I can confirm they support VT-d. I've also been contemplating going with a Q77 motherboard, just to avoid the hassles of determining if a given Z77 motherboard actually has VT-d support. The downside to the Q77 motherboards I have looked at is that they typically lack the integrated extras (e.g. additional SATA/USB controllers) that you find on Z77 motherboards. This makes them less attractive for PCI passthrough. Furthermore, a respondent on the Ars Technica threads suggested that an LGA2011 could be worth a gander. Now, when I started investigating hardware, I had dismissed this option, mostly because they were often very expensive (incl. CPU). More aggravating, the X79 chipset used on desktop LGA2011 motherboards is not officially sanctioned for VT-d. Given it's placement as a desktop workstation chipset, the omission of VT-d just pissed me off. I didn't even bother investigating the possibility that X79 motherboard 'unofficially' supported VT-d. So, in order to get VT-d on LGA2011, you had to level up to a server motherboard. Unfortunately, most of the options that had the mix of features I wanted, ended up being ridiculously expensive, particularly because those motherboards were designed with dual processors in mind. Fortunately, there have been some changes since then. For example, I found this Gigabyte motherboard . It's based on the C606 server chipset but packaged as a desktop motherboard. It is sanctioned by Intel for VT-d and has more RAM capacity. As an added bonus, it includes an integrated SAS controller supplying eight SAS 3GB/s ports. I'm pretty sure it's fake RAID though. No big deal, I'll probably end up using Btrfs, mdadm, or ZFS on that controller anyway. As things stand now, this motherboard would pretty much cost the same as the Extreme9. Going the LGA 2011 route, however, would require I start with two discrete GPUs instead of one. Maybe something like this , combined with something like this or this . All of these considerations have seriously complicated my decision-making process. I still haven't managed to pare down my hardware choices to fit the $2000 budget I have imposed on myself. And those calculations don't even include one discrete GPU! So far, most (not all, e.g. Extreme6) of the suggestions I get haven't helped to reduce costs. Based on your success, I'm sorely tempted to dip into my reserve fund for building a second, more modest box: My contingency plan if my experiments in virtualization failed to produce satisfactory results. > As soon as I'm done putting together the details, I'll append the new > hardware information to the wiki. > > As for changes, the new Z77 chipset has onboard USB 3.0 in exchange > for some of the formerly USB 2.0 ports. In my performance demo video > I showed that USB 2.0 speeds are sub-par, but even SUB 2.0 devices can > hit higher rates when connected to a USB 3.0 port. As far as the > IvyBridge CPU, onboard graphics are noticeably better in Dom0, and > file decompression in my Windows HVM appears to be faster. I have not > run any benchmark tests yet. > I was kind of surprised by that. I can understand that there would be some overhead due to the virtualized environment, but I wondered what would cause such a degradation of performance? I mean I know USB is pretty CPU dependent. However, with a Core i7, I figure there would be enough CPU cycles to spare that only multiple asynchronous connections would cause that kind of performance hit. > > I compiled the new Xen 4.2 stable, as tagged in the new 4.2 testing > branch, but I may try the older revision of Xen in my guide. I am > getting an error on the first-launch attempt of any virtual machine > with passed devices. When I try again it works, but it's 5 lines > worth of errors which makes the following success seem less joyful. > > I tried kernel 3.5.4, and it appears to be suffering the same > passthrough bugs as 3.5.2, so I would avoid 3.5+ still. I ended up > with Kernel 3.4.11, which is working. > I'll keep all that in mind, though I don't have a problem compiling sever kernel images to play with... BTW, would there be any significant problems, that you know of, to compiling and trying several combinations of Linux and Xen during my testing phase? If I went with significantly different hardware, I imagine I might need different combinations of both. But, since I haven't actually gotten to the testing phase, I don't know what easily avoidable pitfalls might be in my path. > One good bit of news was I kept my SSD, so I was able to just recreate > the HVM configuration and launch Windows without problems. Only > issues were new drivers, and Windows asking to reactivate due to HW > changes. > > > Hope this information helps, > > ~Casey > It's all been very helpful. I am in your debt! I'm sure others will be too, once they make use of your guide. BTW, another thing that I've been wondering about. Should I treat Dom0 as an administrative domain and create a separate DomU for my Linux desktop? Or is it safe to reduce the overhead of having a Linux DomU and just use Dom0? I know this is probably more of a stylistic question; after all, you were using your Dom0 for development purposes... but that's significantly different from a general purpose desktop environment. --------------010502070908050400020003 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit
Sorry for the late response, I've had a lot to digest.

On 09/21/2012 01:02 PM, Casey DeLorme wrote:
Thanks for the CC Andrew,

I responded in private since I didn't want to spam the list.

Since we're on the subject of the latest hardware, my system was using a Z68 Motherboard Chipset and Core i7 SandyBridge CPU (2600).  I just sold it to a friend and upgraded to the latest.

Now running an IvyBridge 3770, Z77 Motherboard Chipset (ASRock Z77 Extreme 9), and similar components for the rest.  The Extreme 9 price is extremely high, I wouldn't recommend it unless you have the money, their Z77 Extreme 6 is priced at the same as the Z68 Extreme4 Gen3, and has all the same features plus more USB 3.0.  I would give that one a shake if you are looking for newest components.  The hardest part of switching from the Extreme4 Gen3 was remapping the USB ports to USB controllers by PCI BDF in Linux, because I haven't found an easy way to do that using the systems information yet.

Funnily enough, the Extreme9 was one of my two original motherboard candidates, along with the Gigabyte G1.Sniper 3.  Though I've expanded that list now to include all of ASRock's Z77 line of motherboards.  I might even consider Z77 motherboards from other manufacturers, if I can confirm they support VT-d.

I've also been contemplating going with a Q77 motherboard, just to avoid the hassles of determining if a given Z77 motherboard actually has VT-d support.  The downside to the Q77 motherboards I have looked at is that they typically lack the integrated extras (e.g. additional SATA/USB controllers) that you find on Z77 motherboards.  This makes them less attractive for PCI passthrough. 

Furthermore, a respondent on the Ars Technica threads suggested that an LGA2011 could be worth a gander.  Now, when I started investigating hardware, I had dismissed this option, mostly because they were often very expensive (incl. CPU). More aggravating, the X79 chipset used on desktop LGA2011 motherboards is not officially sanctioned for VT-d.  Given it's placement as a desktop workstation chipset, the omission of VT-d just pissed me off.  I didn't even bother investigating the possibility that X79 motherboard 'unofficially' supported VT-d.  So, in order to get VT-d on LGA2011, you had to level up to a server motherboard.  Unfortunately, most of the options that had the mix of features I wanted, ended up being ridiculously expensive, particularly because those motherboards were designed with dual processors in mind.

Fortunately, there have been some changes since then.  For example, I found this Gigabyte motherboard.  It's based on the C606 server chipset but packaged as a desktop motherboard.  It is sanctioned by Intel for VT-d and has more RAM capacity.  As an added bonus, it includes an integrated SAS controller supplying eight SAS 3GB/s ports.  I'm pretty sure it's fake RAID though.  No big deal, I'll probably end up using Btrfs, mdadm, or ZFS on that controller anyway.  As things stand now, this motherboard would pretty much cost the same as the Extreme9.  Going the LGA 2011 route, however, would require I start with two discrete GPUs instead of one.  Maybe something like this, combined with something like this or this.

All of these considerations have seriously complicated my decision-making process.  I still haven't managed to pare down my hardware choices to fit the $2000 budget I have imposed on myself.  And those calculations don't even include one discrete GPU!  So far, most (not all, e.g. Extreme6) of the suggestions I get haven't helped to reduce costs.  Based on your success, I'm sorely tempted to dip into my reserve fund for building a second, more modest box:  My contingency plan if my experiments in virtualization failed to produce satisfactory results.
As soon as I'm done putting together the details, I'll append the new hardware information to the wiki.

As for changes, the new Z77 chipset has onboard USB 3.0 in exchange for some of the formerly USB 2.0 ports.  In my performance demo video I showed that USB 2.0 speeds are sub-par, but even SUB 2.0 devices can hit higher rates when connected to a USB 3.0 port.  As far as the IvyBridge CPU, onboard graphics are noticeably better in Dom0, and file decompression in my Windows HVM appears to be faster.  I have not run any benchmark tests yet.

I was kind of surprised by that.  I can understand that there would be some overhead due to the virtualized environment, but I wondered what would cause such a degradation of performance?  I mean I know USB is pretty CPU dependent.  However, with a Core i7, I figure there would be enough CPU cycles to spare that only multiple asynchronous connections would cause that kind of performance hit.

I compiled the new Xen 4.2 stable, as tagged in the new 4.2 testing branch, but I may try the older revision of Xen in my guide.  I am getting an error on the first-launch attempt of any virtual machine with passed devices.  When I try again it works, but it's 5 lines worth of errors which makes the following success seem less joyful.

I tried kernel 3.5.4, and it appears to be suffering the same passthrough bugs as 3.5.2, so I would avoid 3.5+ still.  I ended up with Kernel 3.4.11, which is working.

I'll keep all that in mind, though I don't have a problem compiling sever kernel images to play with...  BTW, would there be any significant problems, that you know of, to compiling and trying several combinations of Linux and Xen during my testing phase?  If I went with significantly different hardware, I imagine I might need different combinations of both.  But, since I haven't actually gotten to the testing phase, I don't know what easily avoidable pitfalls might be in my path.
One good bit of news was I kept my SSD, so I was able to just recreate the HVM configuration and launch Windows without problems.  Only issues were new drivers, and Windows asking to reactivate due to HW changes.


Hope this information helps,

~Casey

It's all been very helpful.  I am in your debt!  I'm sure others will be too, once they make use of your guide.

BTW, another thing that I've been wondering about.  Should I treat Dom0 as an  administrative domain and create a separate DomU for my Linux desktop?  Or is it safe to reduce the overhead of having a Linux DomU and just use Dom0?  I know this is probably more of a stylistic question; after all, you were using your Dom0 for development purposes... but that's significantly different from a general purpose desktop environment.

--------------010502070908050400020003-- --===============4209421940341483610== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users --===============4209421940341483610==-- From xen-users-bounces@lists.xen.org Mon Sep 24 03:46:35 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Mon, 24 Sep 2012 03:46:35 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TFzcR-0002RQ-IM; Mon, 24 Sep 2012 03:46:03 +0000 Received: from mail27.messagelabs.com ([193.109.254.147]) by lists.xen.org with smtp (Exim 4.72) (envelope-from ) id 1TFzcP-0002Pq-0G for xen-users@lists.xen.org; Mon, 24 Sep 2012 03:46:01 +0000 X-Env-Sender: shades_of_grey@earthlink.net X-Msg-Ref: server-11.tower-27.messagelabs.com!1348458352!2790683!1 X-Originating-IP: [209.86.89.66] X-SpamReason: No, hits=0.6 required=7.0 tests=BODY_RANDOM_LONG, HTML_30_40,HTML_MESSAGE,ML_RADAR_SPEW_LINKS_14,spamassassin: X-StarScan-Received: X-StarScan-Version: 6.6.1.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 8873 invoked from network); 24 Sep 2012 03:45:52 -0000 Received: from elasmtp-spurfowl.atl.sa.earthlink.net (HELO elasmtp-spurfowl.atl.sa.earthlink.net) (209.86.89.66) by server-11.tower-27.messagelabs.com with SMTP; 24 Sep 2012 03:45:52 -0000 DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=dk20050327; d=earthlink.net; b=ADTKgYyPE6CncvVf6gmsGoFEP6wNEXjgIU6tjQW9Sx+GX25d/xM/JsXQOfsagfNz; h=Received:Message-ID:Date:From:User-Agent:MIME-Version:To:Subject:References:In-Reply-To:Content-Type:X-ELNK-Trace:X-Originating-IP; Received: from [66.167.250.229] (helo=[192.168.1.13]) by elasmtp-spurfowl.atl.sa.earthlink.net with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.67) (envelope-from ) id 1TFzcF-0004cs-FB for xen-users@lists.xen.org; Sun, 23 Sep 2012 23:45:51 -0400 Message-ID: <505FD76E.6000707@earthlink.net> Date: Sun, 23 Sep 2012 23:45:50 -0400 From: ShadesOfGrey User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:15.0) Gecko/20120907 Thunderbird/15.0.1 MIME-Version: 1.0 To: xen-users@lists.xen.org References: <505B86AE.9040507@earthlink.net> <-4689096786842132042@unknownmsgid> In-Reply-To: X-ELNK-Trace: 0fe7bc40aa99bc8fc963772e86942a7b94f5150ab1c16ac0485087bba56e600995638eb3d9f495cc9482422fe497970b350badd9bab72f9c350badd9bab72f9c X-Originating-IP: 66.167.250.229 Subject: Re: [Xen-users] Recommendations for Virtulization Hardware X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============4209421940341483610==" Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org This is a multi-part message in MIME format. --===============4209421940341483610== Content-Type: multipart/alternative; boundary="------------010502070908050400020003" This is a multi-part message in MIME format. --------------010502070908050400020003 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Sorry for the late response, I've had a lot to digest. On 09/21/2012 01:02 PM, Casey DeLorme wrote: > Thanks for the CC Andrew, > > I responded in private since I didn't want to spam the list. > > Since we're on the subject of the latest hardware, my system was using > a Z68 Motherboard Chipset and Core i7 SandyBridge CPU (2600). I just > sold it to a friend and upgraded to the latest. > > Now running an IvyBridge 3770, Z77 Motherboard Chipset (ASRock Z77 > Extreme 9), and similar components for the rest. The Extreme 9 price > is extremely high, I wouldn't recommend it unless you have the money, > their Z77 Extreme 6 is priced at the same as the Z68 Extreme4 Gen3, > and has all the same features plus more USB 3.0. I would give that > one a shake if you are looking for newest components. The hardest > part of switching from the Extreme4 Gen3 was remapping the USB ports > to USB controllers by PCI BDF in Linux, because I haven't found an > easy way to do that using the systems information yet. > Funnily enough, the Extreme9 was one of my two original motherboard candidates, along with the Gigabyte G1.Sniper 3. Though I've expanded that list now to include all of ASRock's Z77 line of motherboards. I might even consider Z77 motherboards from other manufacturers, if I can confirm they support VT-d. I've also been contemplating going with a Q77 motherboard, just to avoid the hassles of determining if a given Z77 motherboard actually has VT-d support. The downside to the Q77 motherboards I have looked at is that they typically lack the integrated extras (e.g. additional SATA/USB controllers) that you find on Z77 motherboards. This makes them less attractive for PCI passthrough. Furthermore, a respondent on the Ars Technica threads suggested that an LGA2011 could be worth a gander. Now, when I started investigating hardware, I had dismissed this option, mostly because they were often very expensive (incl. CPU). More aggravating, the X79 chipset used on desktop LGA2011 motherboards is not officially sanctioned for VT-d. Given it's placement as a desktop workstation chipset, the omission of VT-d just pissed me off. I didn't even bother investigating the possibility that X79 motherboard 'unofficially' supported VT-d. So, in order to get VT-d on LGA2011, you had to level up to a server motherboard. Unfortunately, most of the options that had the mix of features I wanted, ended up being ridiculously expensive, particularly because those motherboards were designed with dual processors in mind. Fortunately, there have been some changes since then. For example, I found this Gigabyte motherboard . It's based on the C606 server chipset but packaged as a desktop motherboard. It is sanctioned by Intel for VT-d and has more RAM capacity. As an added bonus, it includes an integrated SAS controller supplying eight SAS 3GB/s ports. I'm pretty sure it's fake RAID though. No big deal, I'll probably end up using Btrfs, mdadm, or ZFS on that controller anyway. As things stand now, this motherboard would pretty much cost the same as the Extreme9. Going the LGA 2011 route, however, would require I start with two discrete GPUs instead of one. Maybe something like this , combined with something like this or this . All of these considerations have seriously complicated my decision-making process. I still haven't managed to pare down my hardware choices to fit the $2000 budget I have imposed on myself. And those calculations don't even include one discrete GPU! So far, most (not all, e.g. Extreme6) of the suggestions I get haven't helped to reduce costs. Based on your success, I'm sorely tempted to dip into my reserve fund for building a second, more modest box: My contingency plan if my experiments in virtualization failed to produce satisfactory results. > As soon as I'm done putting together the details, I'll append the new > hardware information to the wiki. > > As for changes, the new Z77 chipset has onboard USB 3.0 in exchange > for some of the formerly USB 2.0 ports. In my performance demo video > I showed that USB 2.0 speeds are sub-par, but even SUB 2.0 devices can > hit higher rates when connected to a USB 3.0 port. As far as the > IvyBridge CPU, onboard graphics are noticeably better in Dom0, and > file decompression in my Windows HVM appears to be faster. I have not > run any benchmark tests yet. > I was kind of surprised by that. I can understand that there would be some overhead due to the virtualized environment, but I wondered what would cause such a degradation of performance? I mean I know USB is pretty CPU dependent. However, with a Core i7, I figure there would be enough CPU cycles to spare that only multiple asynchronous connections would cause that kind of performance hit. > > I compiled the new Xen 4.2 stable, as tagged in the new 4.2 testing > branch, but I may try the older revision of Xen in my guide. I am > getting an error on the first-launch attempt of any virtual machine > with passed devices. When I try again it works, but it's 5 lines > worth of errors which makes the following success seem less joyful. > > I tried kernel 3.5.4, and it appears to be suffering the same > passthrough bugs as 3.5.2, so I would avoid 3.5+ still. I ended up > with Kernel 3.4.11, which is working. > I'll keep all that in mind, though I don't have a problem compiling sever kernel images to play with... BTW, would there be any significant problems, that you know of, to compiling and trying several combinations of Linux and Xen during my testing phase? If I went with significantly different hardware, I imagine I might need different combinations of both. But, since I haven't actually gotten to the testing phase, I don't know what easily avoidable pitfalls might be in my path. > One good bit of news was I kept my SSD, so I was able to just recreate > the HVM configuration and launch Windows without problems. Only > issues were new drivers, and Windows asking to reactivate due to HW > changes. > > > Hope this information helps, > > ~Casey > It's all been very helpful. I am in your debt! I'm sure others will be too, once they make use of your guide. BTW, another thing that I've been wondering about. Should I treat Dom0 as an administrative domain and create a separate DomU for my Linux desktop? Or is it safe to reduce the overhead of having a Linux DomU and just use Dom0? I know this is probably more of a stylistic question; after all, you were using your Dom0 for development purposes... but that's significantly different from a general purpose desktop environment. --------------010502070908050400020003 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit
Sorry for the late response, I've had a lot to digest.

On 09/21/2012 01:02 PM, Casey DeLorme wrote:
Thanks for the CC Andrew,

I responded in private since I didn't want to spam the list.

Since we're on the subject of the latest hardware, my system was using a Z68 Motherboard Chipset and Core i7 SandyBridge CPU (2600).  I just sold it to a friend and upgraded to the latest.

Now running an IvyBridge 3770, Z77 Motherboard Chipset (ASRock Z77 Extreme 9), and similar components for the rest.  The Extreme 9 price is extremely high, I wouldn't recommend it unless you have the money, their Z77 Extreme 6 is priced at the same as the Z68 Extreme4 Gen3, and has all the same features plus more USB 3.0.  I would give that one a shake if you are looking for newest components.  The hardest part of switching from the Extreme4 Gen3 was remapping the USB ports to USB controllers by PCI BDF in Linux, because I haven't found an easy way to do that using the systems information yet.

Funnily enough, the Extreme9 was one of my two original motherboard candidates, along with the Gigabyte G1.Sniper 3.  Though I've expanded that list now to include all of ASRock's Z77 line of motherboards.  I might even consider Z77 motherboards from other manufacturers, if I can confirm they support VT-d.

I've also been contemplating going with a Q77 motherboard, just to avoid the hassles of determining if a given Z77 motherboard actually has VT-d support.  The downside to the Q77 motherboards I have looked at is that they typically lack the integrated extras (e.g. additional SATA/USB controllers) that you find on Z77 motherboards.  This makes them less attractive for PCI passthrough. 

Furthermore, a respondent on the Ars Technica threads suggested that an LGA2011 could be worth a gander.  Now, when I started investigating hardware, I had dismissed this option, mostly because they were often very expensive (incl. CPU). More aggravating, the X79 chipset used on desktop LGA2011 motherboards is not officially sanctioned for VT-d.  Given it's placement as a desktop workstation chipset, the omission of VT-d just pissed me off.  I didn't even bother investigating the possibility that X79 motherboard 'unofficially' supported VT-d.  So, in order to get VT-d on LGA2011, you had to level up to a server motherboard.  Unfortunately, most of the options that had the mix of features I wanted, ended up being ridiculously expensive, particularly because those motherboards were designed with dual processors in mind.

Fortunately, there have been some changes since then.  For example, I found this Gigabyte motherboard.  It's based on the C606 server chipset but packaged as a desktop motherboard.  It is sanctioned by Intel for VT-d and has more RAM capacity.  As an added bonus, it includes an integrated SAS controller supplying eight SAS 3GB/s ports.  I'm pretty sure it's fake RAID though.  No big deal, I'll probably end up using Btrfs, mdadm, or ZFS on that controller anyway.  As things stand now, this motherboard would pretty much cost the same as the Extreme9.  Going the LGA 2011 route, however, would require I start with two discrete GPUs instead of one.  Maybe something like this, combined with something like this or this.

All of these considerations have seriously complicated my decision-making process.  I still haven't managed to pare down my hardware choices to fit the $2000 budget I have imposed on myself.  And those calculations don't even include one discrete GPU!  So far, most (not all, e.g. Extreme6) of the suggestions I get haven't helped to reduce costs.  Based on your success, I'm sorely tempted to dip into my reserve fund for building a second, more modest box:  My contingency plan if my experiments in virtualization failed to produce satisfactory results.
As soon as I'm done putting together the details, I'll append the new hardware information to the wiki.

As for changes, the new Z77 chipset has onboard USB 3.0 in exchange for some of the formerly USB 2.0 ports.  In my performance demo video I showed that USB 2.0 speeds are sub-par, but even SUB 2.0 devices can hit higher rates when connected to a USB 3.0 port.  As far as the IvyBridge CPU, onboard graphics are noticeably better in Dom0, and file decompression in my Windows HVM appears to be faster.  I have not run any benchmark tests yet.

I was kind of surprised by that.  I can understand that there would be some overhead due to the virtualized environment, but I wondered what would cause such a degradation of performance?  I mean I know USB is pretty CPU dependent.  However, with a Core i7, I figure there would be enough CPU cycles to spare that only multiple asynchronous connections would cause that kind of performance hit.

I compiled the new Xen 4.2 stable, as tagged in the new 4.2 testing branch, but I may try the older revision of Xen in my guide.  I am getting an error on the first-launch attempt of any virtual machine with passed devices.  When I try again it works, but it's 5 lines worth of errors which makes the following success seem less joyful.

I tried kernel 3.5.4, and it appears to be suffering the same passthrough bugs as 3.5.2, so I would avoid 3.5+ still.  I ended up with Kernel 3.4.11, which is working.

I'll keep all that in mind, though I don't have a problem compiling sever kernel images to play with...  BTW, would there be any significant problems, that you know of, to compiling and trying several combinations of Linux and Xen during my testing phase?  If I went with significantly different hardware, I imagine I might need different combinations of both.  But, since I haven't actually gotten to the testing phase, I don't know what easily avoidable pitfalls might be in my path.
One good bit of news was I kept my SSD, so I was able to just recreate the HVM configuration and launch Windows without problems.  Only issues were new drivers, and Windows asking to reactivate due to HW changes.


Hope this information helps,

~Casey

It's all been very helpful.  I am in your debt!  I'm sure others will be too, once they make use of your guide.

BTW, another thing that I've been wondering about.  Should I treat Dom0 as an  administrative domain and create a separate DomU for my Linux desktop?  Or is it safe to reduce the overhead of having a Linux DomU and just use Dom0?  I know this is probably more of a stylistic question; after all, you were using your Dom0 for development purposes... but that's significantly different from a general purpose desktop environment.

--------------010502070908050400020003-- --===============4209421940341483610== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users --===============4209421940341483610==-- From xen-users-bounces@lists.xen.org Mon Sep 24 03:52:43 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Mon, 24 Sep 2012 03:52:43 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TFziN-0003Tn-6c; Mon, 24 Sep 2012 03:52:11 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TFziL-0003Td-Ss for xen-users@lists.xensource.com; Mon, 24 Sep 2012 03:52:10 +0000 Received: from [85.158.143.35:19742] by server-3.bemta-4.messagelabs.com id F1/75-10986-9E8DF505; Mon, 24 Sep 2012 03:52:09 +0000 X-Env-Sender: matthiasblankenhaus@yahoo.com X-Msg-Ref: server-6.tower-21.messagelabs.com!1348458727!19544031!1 X-Originating-IP: [98.139.91.94] X-SpamReason: No, hits=0.1 required=7.0 tests=HTML_50_60,HTML_MESSAGE, ML_RADAR_SPEW_LINKS_12,ML_RADAR_SPEW_LINKS_14,ML_RADAR_SPEW_LINKS_23, ML_RADAR_SPEW_LINKS_5,ML_RADAR_SPEW_LINKS_6,spamassassin: X-StarScan-Received: X-StarScan-Version: 6.6.1.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 7052 invoked from network); 24 Sep 2012 03:52:08 -0000 Received: from nm24.bullet.mail.sp2.yahoo.com (HELO nm24.bullet.mail.sp2.yahoo.com) (98.139.91.94) by server-6.tower-21.messagelabs.com with SMTP; 24 Sep 2012 03:52:08 -0000 Received: from [98.139.91.70] by nm24.bullet.mail.sp2.yahoo.com with NNFMP; 24 Sep 2012 03:52:07 -0000 Received: from [98.139.91.56] by tm10.bullet.mail.sp2.yahoo.com with NNFMP; 24 Sep 2012 03:52:06 -0000 Received: from [127.0.0.1] by omp1056.mail.sp2.yahoo.com with NNFMP; 24 Sep 2012 03:52:06 -0000 X-Yahoo-Newman-Property: ymail-3 X-Yahoo-Newman-Id: 925452.64209.bm@omp1056.mail.sp2.yahoo.com Received: (qmail 6953 invoked by uid 60001); 24 Sep 2012 03:52:04 -0000 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.com; s=s1024; t=1348458724; bh=QSst/zrFT0+SqemGumtpHKqNSfeucNeH0x1k9XeW9bI=; h=X-YMail-OSG:Received:X-Mailer:References:Message-ID:Date:From:Reply-To:Subject:To:Cc:In-Reply-To:MIME-Version:Content-Type; b=VhrYRXJw6UpNSlLgEyn63BzW3T3EO9lEtnUs3pztBBxbnoVsYInxMd5KAZ2kueGRwuwLHV/r4gV6jJUoZLORPJVNIsr8Dag7SV4W8mDHHch/NG7j/KjJSm1nTDp4MBuRF7OrPX/Jwedj9/w+7iSdacS/RV/osRSWezpxBuxVE6E= DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com; h=X-YMail-OSG:Received:X-Mailer:References:Message-ID:Date:From:Reply-To:Subject:To:Cc:In-Reply-To:MIME-Version:Content-Type; b=4ElsijAjAluyBcWP+RW732Q+Qkngne7PoYQQ35dxuPWGRkgrGCx5tYs6zr2RmMsk5KmF/Zff9cICrwlRa+nsiHbxPg8gU134m+4REEF1h89jsNwkI0krYGORch1TdTID4VUAu+fvKsB0LDiF6PO6FumwesD0w1eUjRVe+JzE7Rk=; X-YMail-OSG: exzJmKQVM1nyZNjg3apfWoMui9Qt21RAR68kr5Wpjmbj_co XhAO.wqG_3LL.83FP_Q_r_aqga6nIYUeK7Tthe2DAJ1xcWNBCzi7Yy1LC2qf SgL_1xscYzu10l_O0LZCxJgIIkDw5WgUt4G19nidGx.LLiQqXX1ZI2AFhqas 4F2P.RdPAHyi3XKaejXjndepcQOsFVszH2mqJEP7vV1uKnyRO4JKzS5WIUFX ot7lPlq7Z_.J.Pcu5ZqHoU3eEneJ5_J8HkonACMLkepMNPf7m10DuzK4C1_d mh47_ueIp_wu2QF9xI1eDR4J6f3jx5DNOkcMfiiti5Mfzci6vxQ9u_U1GWoc cBKLZhWRFJIQDe.3R2CNsN_YWK4IN5J1bY7X7HNp8XBGda163UTQWE1pFyrp qQQ6XUE_fXjg_LP2uhKt055bZH92dtIRDKQ9.Hzo5SaovxeiU1pgYFXhOahF 4cJlaob3gE9s1WKFEn7UdoKP2B4gv0kylgz.ixFAK1AxCLTiA3ypaDoiaIhY saJy1j84M6zt23qjHaMJ9wwwZr0PQJkxOAbJRt3w5CR6_QpOCLQ0UBNqyJKf 5sN9v2me9hBryuFsu3Xbr1V3c1UwGtFMXc3lXPJjZxLet9ScL0LNuvaj5WJ2 9d9aQ6QQLSrMAhQzKGwXVZjt1DWmirHQSUfZ_uI0t72Nd7GJ8t9MAINr.ecR SfQjG1oOFMGJZ2Xy8EHpIqR5dhBSboQZ_8ILyjiBndt8Jvqbr Received: from [143.127.128.10] by web39406.mail.mud.yahoo.com via HTTP; Sun, 23 Sep 2012 20:52:04 PDT X-Mailer: YahooMailWebService/0.8.121.416 References: <1346768637276-5710961.post@n5.nabble.com> Message-ID: <1348458724.88941.YahooMailNeo@web39406.mail.mud.yahoo.com> Date: Sun, 23 Sep 2012 20:52:04 -0700 (PDT) From: Matthias Blankenhaus To: "xen-users@lists.xensource.com" In-Reply-To: <1346768637276-5710961.post@n5.nabble.com> MIME-Version: 1.0 Cc: Kristoffer Harthing Egefelt Subject: Re: [Xen-users] blktap vs qemu backend X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list Reply-To: Matthias Blankenhaus List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============2212120004371717753==" Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org --===============2212120004371717753== Content-Type: multipart/alternative; boundary="411857043-266334378-1348458724=:88941" --411857043-266334378-1348458724=:88941 Content-Type: text/plain; charset=us-ascii Hi Kristoffer ! Did you get a reply for this ? I am very interested in the future of the block device layer as well. Matthias >________________________________ > From: Kristoffer Harthing Egefelt >To: xen-users@lists.xensource.com >Sent: Tuesday, September 4, 2012 7:23 AM >Subject: [Xen-users] blktap vs qemu backend > >Hi, > >I'm trying to figure out if blktap or qemu is the best backend for raw >images? > >Using xen4.2 and kernel 3.2 and 3.5 theres a lot of problems with blktap, >hacking blktap, hanging devices, unbootable domUs (block device errors). > >Performance in the qemu backend actually seems to be quite ok, 5-20% slower >than LVM though - but not that much slower than blktap. > >It seems that a userspace blktap3 is not coming soon >(http://lists.xen.org/archives/html/xen-devel/2012-04/msg00583.html) so >maybe one should just settle with qemu for now. > >- Anybody know where the source code for blktap3 is? >- xl top does not show VBD stats for qemu devices - is this expected? > >Thanks. >Regards >Kristoffer > > > > >-- >View this message in context: http://xen.1045712.n5.nabble.com/blktap-vs-qemu-backend-tp5710961.html >Sent from the Xen - User mailing list archive at Nabble.com. > >_______________________________________________ >Xen-users mailing list >Xen-users@lists.xen.org >http://lists.xen.org/xen-users > > > --411857043-266334378-1348458724=:88941 Content-Type: text/html; charset=us-ascii
Hi Kristoffer !

Did you get a reply for this ? I am very interested in the future of the block device layer as well.

Matthias

From: Kristoffer Harthing Egefelt <k@itoc.dk>
To: xen-users@lists.xensource.com
Sent: Tuesday, September 4, 2012 7:23 AM
Subject: [Xen-users] blktap vs qemu backend

Hi,

I'm trying to figure out if blktap or qemu is the best backend for raw
images?

Using xen4.2 and kernel 3.2 and 3.5 theres a lot of problems with blktap,
hacking blktap, hanging devices, unbootable domUs (block device errors).

Performance in the qemu backend actually seems to be quite ok, 5-20% slower
than LVM though - but not that much slower than blktap.

It seems that a userspace blktap3 is not coming soon
(http://lists.xen.org/archives/html/xen-devel/2012-04/msg00583.html) so
maybe one should just settle with qemu for now.

- Anybody know where the source code for blktap3 is?
- xl top does not show VBD stats for qemu devices - is this expected?

Thanks.
Regards
Kristoffer




--
View this message in context: http://xen.1045712.n5.nabble.com/blktap-vs-qemu-backend-tp5710961.html
Sent from the Xen - User mailing list archive at Nabble.com.

_______________________________________________
Xen-users mailing list
Xen-users@lists.xen.org
http://lists.xen.org/xen-users


--411857043-266334378-1348458724=:88941-- --===============2212120004371717753== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users --===============2212120004371717753==-- From xen-users-bounces@lists.xen.org Mon Sep 24 03:52:43 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Mon, 24 Sep 2012 03:52:43 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TFziN-0003Tn-6c; Mon, 24 Sep 2012 03:52:11 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TFziL-0003Td-Ss for xen-users@lists.xensource.com; Mon, 24 Sep 2012 03:52:10 +0000 Received: from [85.158.143.35:19742] by server-3.bemta-4.messagelabs.com id F1/75-10986-9E8DF505; Mon, 24 Sep 2012 03:52:09 +0000 X-Env-Sender: matthiasblankenhaus@yahoo.com X-Msg-Ref: server-6.tower-21.messagelabs.com!1348458727!19544031!1 X-Originating-IP: [98.139.91.94] X-SpamReason: No, hits=0.1 required=7.0 tests=HTML_50_60,HTML_MESSAGE, ML_RADAR_SPEW_LINKS_12,ML_RADAR_SPEW_LINKS_14,ML_RADAR_SPEW_LINKS_23, ML_RADAR_SPEW_LINKS_5,ML_RADAR_SPEW_LINKS_6,spamassassin: X-StarScan-Received: X-StarScan-Version: 6.6.1.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 7052 invoked from network); 24 Sep 2012 03:52:08 -0000 Received: from nm24.bullet.mail.sp2.yahoo.com (HELO nm24.bullet.mail.sp2.yahoo.com) (98.139.91.94) by server-6.tower-21.messagelabs.com with SMTP; 24 Sep 2012 03:52:08 -0000 Received: from [98.139.91.70] by nm24.bullet.mail.sp2.yahoo.com with NNFMP; 24 Sep 2012 03:52:07 -0000 Received: from [98.139.91.56] by tm10.bullet.mail.sp2.yahoo.com with NNFMP; 24 Sep 2012 03:52:06 -0000 Received: from [127.0.0.1] by omp1056.mail.sp2.yahoo.com with NNFMP; 24 Sep 2012 03:52:06 -0000 X-Yahoo-Newman-Property: ymail-3 X-Yahoo-Newman-Id: 925452.64209.bm@omp1056.mail.sp2.yahoo.com Received: (qmail 6953 invoked by uid 60001); 24 Sep 2012 03:52:04 -0000 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.com; s=s1024; t=1348458724; bh=QSst/zrFT0+SqemGumtpHKqNSfeucNeH0x1k9XeW9bI=; h=X-YMail-OSG:Received:X-Mailer:References:Message-ID:Date:From:Reply-To:Subject:To:Cc:In-Reply-To:MIME-Version:Content-Type; b=VhrYRXJw6UpNSlLgEyn63BzW3T3EO9lEtnUs3pztBBxbnoVsYInxMd5KAZ2kueGRwuwLHV/r4gV6jJUoZLORPJVNIsr8Dag7SV4W8mDHHch/NG7j/KjJSm1nTDp4MBuRF7OrPX/Jwedj9/w+7iSdacS/RV/osRSWezpxBuxVE6E= DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com; h=X-YMail-OSG:Received:X-Mailer:References:Message-ID:Date:From:Reply-To:Subject:To:Cc:In-Reply-To:MIME-Version:Content-Type; b=4ElsijAjAluyBcWP+RW732Q+Qkngne7PoYQQ35dxuPWGRkgrGCx5tYs6zr2RmMsk5KmF/Zff9cICrwlRa+nsiHbxPg8gU134m+4REEF1h89jsNwkI0krYGORch1TdTID4VUAu+fvKsB0LDiF6PO6FumwesD0w1eUjRVe+JzE7Rk=; X-YMail-OSG: exzJmKQVM1nyZNjg3apfWoMui9Qt21RAR68kr5Wpjmbj_co XhAO.wqG_3LL.83FP_Q_r_aqga6nIYUeK7Tthe2DAJ1xcWNBCzi7Yy1LC2qf SgL_1xscYzu10l_O0LZCxJgIIkDw5WgUt4G19nidGx.LLiQqXX1ZI2AFhqas 4F2P.RdPAHyi3XKaejXjndepcQOsFVszH2mqJEP7vV1uKnyRO4JKzS5WIUFX ot7lPlq7Z_.J.Pcu5ZqHoU3eEneJ5_J8HkonACMLkepMNPf7m10DuzK4C1_d mh47_ueIp_wu2QF9xI1eDR4J6f3jx5DNOkcMfiiti5Mfzci6vxQ9u_U1GWoc cBKLZhWRFJIQDe.3R2CNsN_YWK4IN5J1bY7X7HNp8XBGda163UTQWE1pFyrp qQQ6XUE_fXjg_LP2uhKt055bZH92dtIRDKQ9.Hzo5SaovxeiU1pgYFXhOahF 4cJlaob3gE9s1WKFEn7UdoKP2B4gv0kylgz.ixFAK1AxCLTiA3ypaDoiaIhY saJy1j84M6zt23qjHaMJ9wwwZr0PQJkxOAbJRt3w5CR6_QpOCLQ0UBNqyJKf 5sN9v2me9hBryuFsu3Xbr1V3c1UwGtFMXc3lXPJjZxLet9ScL0LNuvaj5WJ2 9d9aQ6QQLSrMAhQzKGwXVZjt1DWmirHQSUfZ_uI0t72Nd7GJ8t9MAINr.ecR SfQjG1oOFMGJZ2Xy8EHpIqR5dhBSboQZ_8ILyjiBndt8Jvqbr Received: from [143.127.128.10] by web39406.mail.mud.yahoo.com via HTTP; Sun, 23 Sep 2012 20:52:04 PDT X-Mailer: YahooMailWebService/0.8.121.416 References: <1346768637276-5710961.post@n5.nabble.com> Message-ID: <1348458724.88941.YahooMailNeo@web39406.mail.mud.yahoo.com> Date: Sun, 23 Sep 2012 20:52:04 -0700 (PDT) From: Matthias Blankenhaus To: "xen-users@lists.xensource.com" In-Reply-To: <1346768637276-5710961.post@n5.nabble.com> MIME-Version: 1.0 Cc: Kristoffer Harthing Egefelt Subject: Re: [Xen-users] blktap vs qemu backend X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list Reply-To: Matthias Blankenhaus List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============2212120004371717753==" Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org --===============2212120004371717753== Content-Type: multipart/alternative; boundary="411857043-266334378-1348458724=:88941" --411857043-266334378-1348458724=:88941 Content-Type: text/plain; charset=us-ascii Hi Kristoffer ! Did you get a reply for this ? I am very interested in the future of the block device layer as well. Matthias >________________________________ > From: Kristoffer Harthing Egefelt >To: xen-users@lists.xensource.com >Sent: Tuesday, September 4, 2012 7:23 AM >Subject: [Xen-users] blktap vs qemu backend > >Hi, > >I'm trying to figure out if blktap or qemu is the best backend for raw >images? > >Using xen4.2 and kernel 3.2 and 3.5 theres a lot of problems with blktap, >hacking blktap, hanging devices, unbootable domUs (block device errors). > >Performance in the qemu backend actually seems to be quite ok, 5-20% slower >than LVM though - but not that much slower than blktap. > >It seems that a userspace blktap3 is not coming soon >(http://lists.xen.org/archives/html/xen-devel/2012-04/msg00583.html) so >maybe one should just settle with qemu for now. > >- Anybody know where the source code for blktap3 is? >- xl top does not show VBD stats for qemu devices - is this expected? > >Thanks. >Regards >Kristoffer > > > > >-- >View this message in context: http://xen.1045712.n5.nabble.com/blktap-vs-qemu-backend-tp5710961.html >Sent from the Xen - User mailing list archive at Nabble.com. > >_______________________________________________ >Xen-users mailing list >Xen-users@lists.xen.org >http://lists.xen.org/xen-users > > > --411857043-266334378-1348458724=:88941 Content-Type: text/html; charset=us-ascii
Hi Kristoffer !

Did you get a reply for this ? I am very interested in the future of the block device layer as well.

Matthias

From: Kristoffer Harthing Egefelt <k@itoc.dk>
To: xen-users@lists.xensource.com
Sent: Tuesday, September 4, 2012 7:23 AM
Subject: [Xen-users] blktap vs qemu backend

Hi,

I'm trying to figure out if blktap or qemu is the best backend for raw
images?

Using xen4.2 and kernel 3.2 and 3.5 theres a lot of problems with blktap,
hacking blktap, hanging devices, unbootable domUs (block device errors).

Performance in the qemu backend actually seems to be quite ok, 5-20% slower
than LVM though - but not that much slower than blktap.

It seems that a userspace blktap3 is not coming soon
(http://lists.xen.org/archives/html/xen-devel/2012-04/msg00583.html) so
maybe one should just settle with qemu for now.

- Anybody know where the source code for blktap3 is?
- xl top does not show VBD stats for qemu devices - is this expected?

Thanks.
Regards
Kristoffer




--
View this message in context: http://xen.1045712.n5.nabble.com/blktap-vs-qemu-backend-tp5710961.html
Sent from the Xen - User mailing list archive at Nabble.com.

_______________________________________________
Xen-users mailing list
Xen-users@lists.xen.org
http://lists.xen.org/xen-users


--411857043-266334378-1348458724=:88941-- --===============2212120004371717753== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users --===============2212120004371717753==-- From xen-users-bounces@lists.xen.org Mon Sep 24 06:26:21 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Mon, 24 Sep 2012 06:26:21 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TG26d-0005W5-HK; Mon, 24 Sep 2012 06:25:23 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TG26c-0005W0-2X for xen-users@lists.xen.org; Mon, 24 Sep 2012 06:25:22 +0000 Received: from [85.158.139.211:14327] by server-1.bemta-5.messagelabs.com id AF/95-09825-1DCFF505; Mon, 24 Sep 2012 06:25:21 +0000 X-Env-Sender: nd@syndicat.com X-Msg-Ref: server-15.tower-206.messagelabs.com!1348467920!19729025!1 X-Originating-IP: [62.146.89.62] X-SpamReason: No, hits=0.0 required=7.0 tests= X-StarScan-Received: X-StarScan-Version: 6.6.1.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 31976 invoked from network); 24 Sep 2012 06:25:20 -0000 Received: from ffm-dr1.syndicat.com (HELO ffm-dr1.syndicat.com) (62.146.89.62) by server-15.tower-206.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 24 Sep 2012 06:25:20 -0000 Received: from localhost.syndicat.com ([127.0.0.1] helo=localhost) by ffm-dr1.syndicat.com with esmtp (Syndicat.com PostHamster 8.1.4.76) (envelope-from ) id 1TG26Z-00000g-Jw; Mon, 24 Sep 2012 08:25:19 +0200 X-Virus-Scanned: amavisd-new at syndicat.com Received: from ffm-dr1.syndicat.com ([127.0.0.1]) by localhost (ffm-dr1.syndicat.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id zHW_UVMIw4xy; Mon, 24 Sep 2012 08:25:18 +0200 (CEST) Received: from p5dc3f55d.dip.t-dialin.net ([93.195.245.93] helo=htc.syndicat) by ffm-dr1.syndicat.com with esmtpsa (TLSv1:RC4-MD5:128) (Syndicat.com PostHamster 8.1.4.76) (envelope-from ) id 1TG26R-0004qs-4A; Mon, 24 Sep 2012 08:25:17 +0200 User-Agent: K-9 Mail for Android In-Reply-To: <20120923201659.164740@gmx.com> References: <20120923201659.164740@gmx.com> MIME-Version: 1.0 From: "Niels Dettenbach (Syndicat IT&Internet)" Date: Mon, 24 Sep 2012 08:24:40 +0200 To: Adam Gold ,xen-users@lists.xen.org Message-ID: <6ef9e91d-0cf6-45b9-bd2e-2369b7f90479@email.android.com> Subject: Re: [Xen-users] Xen 4.2 - xl error X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 Adam Gold schrieb: >make[3]: Entering directory `/root/xen-4.2.0/tools/firmware' >GIT=git /root/xen-4.2.0/tools/firmware/../../scripts/git-checkout.sh >git://xenbits.xen.org/seabios.git rel-1.6.3.2 seabios-dir >/root/xen-4.2.0/tools/firmware/../../scripts/git-checkout.sh: 17: >/root/xen-4.2.0/tools/firmware/../../scripts/git-checkout.sh: git: not >found >make[3]: *** [seabios-dir] Error 127 It seems your system lacks git or git is not in path but the build process need it to fetch some further stuff from the net. hth Cheers, Niels. - -- Niels Dettenbach Syndicat IT&Internet http://www.syndicat.com -----BEGIN PGP SIGNATURE----- Version: APG v1.0.8 iIEEAREIAEEFAlBf/Kc6HE5pZWxzIERldHRlbmJhY2ggKFN5bmRpY2F0IElUJklu dGVybmV0KSA8bmRAc3luZGljYXQuY29tPgAKCRBU3ERlZRyiDWoJAJ46G1UA3dTS IyH5ftjgBSJNcUqrqwCfc5AvKT0QrrZ/prCLBz72+jvCno0= =ySNd -----END PGP SIGNATURE----- _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Mon Sep 24 06:26:21 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Mon, 24 Sep 2012 06:26:21 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TG26d-0005W5-HK; Mon, 24 Sep 2012 06:25:23 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TG26c-0005W0-2X for xen-users@lists.xen.org; Mon, 24 Sep 2012 06:25:22 +0000 Received: from [85.158.139.211:14327] by server-1.bemta-5.messagelabs.com id AF/95-09825-1DCFF505; Mon, 24 Sep 2012 06:25:21 +0000 X-Env-Sender: nd@syndicat.com X-Msg-Ref: server-15.tower-206.messagelabs.com!1348467920!19729025!1 X-Originating-IP: [62.146.89.62] X-SpamReason: No, hits=0.0 required=7.0 tests= X-StarScan-Received: X-StarScan-Version: 6.6.1.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 31976 invoked from network); 24 Sep 2012 06:25:20 -0000 Received: from ffm-dr1.syndicat.com (HELO ffm-dr1.syndicat.com) (62.146.89.62) by server-15.tower-206.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 24 Sep 2012 06:25:20 -0000 Received: from localhost.syndicat.com ([127.0.0.1] helo=localhost) by ffm-dr1.syndicat.com with esmtp (Syndicat.com PostHamster 8.1.4.76) (envelope-from ) id 1TG26Z-00000g-Jw; Mon, 24 Sep 2012 08:25:19 +0200 X-Virus-Scanned: amavisd-new at syndicat.com Received: from ffm-dr1.syndicat.com ([127.0.0.1]) by localhost (ffm-dr1.syndicat.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id zHW_UVMIw4xy; Mon, 24 Sep 2012 08:25:18 +0200 (CEST) Received: from p5dc3f55d.dip.t-dialin.net ([93.195.245.93] helo=htc.syndicat) by ffm-dr1.syndicat.com with esmtpsa (TLSv1:RC4-MD5:128) (Syndicat.com PostHamster 8.1.4.76) (envelope-from ) id 1TG26R-0004qs-4A; Mon, 24 Sep 2012 08:25:17 +0200 User-Agent: K-9 Mail for Android In-Reply-To: <20120923201659.164740@gmx.com> References: <20120923201659.164740@gmx.com> MIME-Version: 1.0 From: "Niels Dettenbach (Syndicat IT&Internet)" Date: Mon, 24 Sep 2012 08:24:40 +0200 To: Adam Gold ,xen-users@lists.xen.org Message-ID: <6ef9e91d-0cf6-45b9-bd2e-2369b7f90479@email.android.com> Subject: Re: [Xen-users] Xen 4.2 - xl error X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 Adam Gold schrieb: >make[3]: Entering directory `/root/xen-4.2.0/tools/firmware' >GIT=git /root/xen-4.2.0/tools/firmware/../../scripts/git-checkout.sh >git://xenbits.xen.org/seabios.git rel-1.6.3.2 seabios-dir >/root/xen-4.2.0/tools/firmware/../../scripts/git-checkout.sh: 17: >/root/xen-4.2.0/tools/firmware/../../scripts/git-checkout.sh: git: not >found >make[3]: *** [seabios-dir] Error 127 It seems your system lacks git or git is not in path but the build process need it to fetch some further stuff from the net. hth Cheers, Niels. - -- Niels Dettenbach Syndicat IT&Internet http://www.syndicat.com -----BEGIN PGP SIGNATURE----- Version: APG v1.0.8 iIEEAREIAEEFAlBf/Kc6HE5pZWxzIERldHRlbmJhY2ggKFN5bmRpY2F0IElUJklu dGVybmV0KSA8bmRAc3luZGljYXQuY29tPgAKCRBU3ERlZRyiDWoJAJ46G1UA3dTS IyH5ftjgBSJNcUqrqwCfc5AvKT0QrrZ/prCLBz72+jvCno0= =ySNd -----END PGP SIGNATURE----- _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Mon Sep 24 08:08:31 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Mon, 24 Sep 2012 08:08:31 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TG3hS-0007Ah-PR; Mon, 24 Sep 2012 08:07:30 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TG3hQ-0007A5-VO for xen-users@lists.xen.org; Mon, 24 Sep 2012 08:07:29 +0000 Received: from [85.158.143.99:60970] by server-3.bemta-4.messagelabs.com id E0/17-10986-FB410605; Mon, 24 Sep 2012 08:07:27 +0000 X-Env-Sender: lars.kurth.xen@gmail.com X-Msg-Ref: server-12.tower-216.messagelabs.com!1348474046!23368681!1 X-Originating-IP: [209.85.217.173] X-SpamReason: No, hits=0.4 required=7.0 tests=HTML_30_40,HTML_MESSAGE, ML_RADAR_SPEW_LINKS_14,RCVD_BY_IP,spamassassin: X-StarScan-Received: X-StarScan-Version: 6.6.1.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 5160 invoked from network); 24 Sep 2012 08:07:26 -0000 Received: from mail-lb0-f173.google.com (HELO mail-lb0-f173.google.com) (209.85.217.173) by server-12.tower-216.messagelabs.com with RC4-SHA encrypted SMTP; 24 Sep 2012 08:07:26 -0000 Received: by lbbgm13 with SMTP id gm13so7838046lbb.32 for ; Mon, 24 Sep 2012 01:07:26 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:date:message-id:subject:from:to:content-type; bh=VQM2rVud5klBfZBJsYP4BZ05g1BoP8iFuZY4r7QOYIY=; b=gYnaJjsP+4u7B2DkjMucZjh96UMsiaqNVhgAcf/Fq1I3raUMz9qpkDylqAXNut51Qe 4eIomwWYOAESOgG0E1h+E27W4wXp4AhOX8TwGbG3YcXijTsJMVLPBc8HrVFSyxJqPeVy uqcAi0V7BSP3EKK8/PRjBtxkKYk9LjczmWiUhK5wVMaTuq5kefsOkGCU6VtiZDahZZg7 XmQ5MZu7i6R/toiLcQUa4jIKpZBIAwnTM+deNCFTTkak898O69KnYQCHs3ByrORMN5YN 3T8IdlWNnz6faDLPYnUTaPC4zUtGF/rjgpxcOkRCOoCnmqgtKKgEZTlKUrOKDZGxpjP6 prRw== MIME-Version: 1.0 Received: by 10.112.26.135 with SMTP id l7mr567705lbg.84.1348474045943; Mon, 24 Sep 2012 01:07:25 -0700 (PDT) Received: by 10.112.120.138 with HTTP; Mon, 24 Sep 2012 01:07:25 -0700 (PDT) Date: Mon, 24 Sep 2012 09:07:25 +0100 Message-ID: From: Lars Kurth To: xen-devel@lists.xen.org, xen-users@lists.xen.org, xen-api@lists.xen.org, xen-arm@lists.xen.org Subject: [Xen-users] [Reminder] Xen Document Day on IRC freenode #xendocs today X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============6400803880133738216==" Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org --===============6400803880133738216== Content-Type: multipart/alternative; boundary=bcaec554d4247f4f0204ca6e143b --bcaec554d4247f4f0204ca6e143b Content-Type: text/plain; charset=ISO-8859-1 Good Morning, we have another document day today! More information about docs day at http://wiki.xen.org/wiki/Xen_Document_Days The TODO list is at http://wiki.xen.org/wiki/Xen_Document_Days/TODO Regards Lars --bcaec554d4247f4f0204ca6e143b Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Good Morning,
we have another document day today! More information about= docs day at http://= wiki.xen.org/wiki/Xen_Document_Days
The TODO list is at http://wiki.xen.org/wiki/Xe= n_Document_Days/TODO
Regards
Lars
--bcaec554d4247f4f0204ca6e143b-- --===============6400803880133738216== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users --===============6400803880133738216==-- From xen-users-bounces@lists.xen.org Mon Sep 24 08:08:31 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Mon, 24 Sep 2012 08:08:31 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TG3hS-0007Ah-PR; Mon, 24 Sep 2012 08:07:30 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TG3hQ-0007A5-VO for xen-users@lists.xen.org; Mon, 24 Sep 2012 08:07:29 +0000 Received: from [85.158.143.99:60970] by server-3.bemta-4.messagelabs.com id E0/17-10986-FB410605; Mon, 24 Sep 2012 08:07:27 +0000 X-Env-Sender: lars.kurth.xen@gmail.com X-Msg-Ref: server-12.tower-216.messagelabs.com!1348474046!23368681!1 X-Originating-IP: [209.85.217.173] X-SpamReason: No, hits=0.4 required=7.0 tests=HTML_30_40,HTML_MESSAGE, ML_RADAR_SPEW_LINKS_14,RCVD_BY_IP,spamassassin: X-StarScan-Received: X-StarScan-Version: 6.6.1.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 5160 invoked from network); 24 Sep 2012 08:07:26 -0000 Received: from mail-lb0-f173.google.com (HELO mail-lb0-f173.google.com) (209.85.217.173) by server-12.tower-216.messagelabs.com with RC4-SHA encrypted SMTP; 24 Sep 2012 08:07:26 -0000 Received: by lbbgm13 with SMTP id gm13so7838046lbb.32 for ; Mon, 24 Sep 2012 01:07:26 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:date:message-id:subject:from:to:content-type; bh=VQM2rVud5klBfZBJsYP4BZ05g1BoP8iFuZY4r7QOYIY=; b=gYnaJjsP+4u7B2DkjMucZjh96UMsiaqNVhgAcf/Fq1I3raUMz9qpkDylqAXNut51Qe 4eIomwWYOAESOgG0E1h+E27W4wXp4AhOX8TwGbG3YcXijTsJMVLPBc8HrVFSyxJqPeVy uqcAi0V7BSP3EKK8/PRjBtxkKYk9LjczmWiUhK5wVMaTuq5kefsOkGCU6VtiZDahZZg7 XmQ5MZu7i6R/toiLcQUa4jIKpZBIAwnTM+deNCFTTkak898O69KnYQCHs3ByrORMN5YN 3T8IdlWNnz6faDLPYnUTaPC4zUtGF/rjgpxcOkRCOoCnmqgtKKgEZTlKUrOKDZGxpjP6 prRw== MIME-Version: 1.0 Received: by 10.112.26.135 with SMTP id l7mr567705lbg.84.1348474045943; Mon, 24 Sep 2012 01:07:25 -0700 (PDT) Received: by 10.112.120.138 with HTTP; Mon, 24 Sep 2012 01:07:25 -0700 (PDT) Date: Mon, 24 Sep 2012 09:07:25 +0100 Message-ID: From: Lars Kurth To: xen-devel@lists.xen.org, xen-users@lists.xen.org, xen-api@lists.xen.org, xen-arm@lists.xen.org Subject: [Xen-users] [Reminder] Xen Document Day on IRC freenode #xendocs today X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============6400803880133738216==" Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org --===============6400803880133738216== Content-Type: multipart/alternative; boundary=bcaec554d4247f4f0204ca6e143b --bcaec554d4247f4f0204ca6e143b Content-Type: text/plain; charset=ISO-8859-1 Good Morning, we have another document day today! More information about docs day at http://wiki.xen.org/wiki/Xen_Document_Days The TODO list is at http://wiki.xen.org/wiki/Xen_Document_Days/TODO Regards Lars --bcaec554d4247f4f0204ca6e143b Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Good Morning,
we have another document day today! More information about= docs day at http://= wiki.xen.org/wiki/Xen_Document_Days
The TODO list is at http://wiki.xen.org/wiki/Xe= n_Document_Days/TODO
Regards
Lars
--bcaec554d4247f4f0204ca6e143b-- --===============6400803880133738216== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users --===============6400803880133738216==-- From xen-users-bounces@lists.xen.org Mon Sep 24 08:35:58 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Mon, 24 Sep 2012 08:35:58 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TG484-0007rk-Pg; Mon, 24 Sep 2012 08:35:00 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TG483-0007rd-6H for xen-users@lists.xen.org; Mon, 24 Sep 2012 08:34:59 +0000 Received: from [85.158.143.99:5484] by server-3.bemta-4.messagelabs.com id 39/E5-10986-23B10605; Mon, 24 Sep 2012 08:34:58 +0000 X-Env-Sender: Ian.Campbell@citrix.com X-Msg-Ref: server-13.tower-216.messagelabs.com!1348475697!30590430!1 X-Originating-IP: [62.200.22.115] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogNjIuMjAwLjIyLjExNSA9PiAxMTA4NDA=\n X-StarScan-Received: X-StarScan-Version: 6.6.1.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 26340 invoked from network); 24 Sep 2012 08:34:57 -0000 Received: from smtp.ctxuk.citrix.com (HELO SMTP.EU.CITRIX.COM) (62.200.22.115) by server-13.tower-216.messagelabs.com with RC4-SHA encrypted SMTP; 24 Sep 2012 08:34:57 -0000 X-IronPort-AV: E=Sophos;i="4.80,474,1344211200"; d="scan'208";a="14715882" Received: from lonpmailmx01.citrite.net ([10.30.203.162]) by LONPIPO01.EU.CITRIX.COM with ESMTP/TLS/RC4-MD5; 24 Sep 2012 08:34:56 +0000 Received: from [10.80.2.42] (10.80.2.42) by LONPMAILMX01.citrite.net (10.30.203.162) with Microsoft SMTP Server id 8.3.279.1; Mon, 24 Sep 2012 09:34:57 +0100 Message-ID: <1348475695.3452.39.camel@zakaz.uk.xensource.com> From: Ian Campbell To: Casey DeLorme Date: Mon, 24 Sep 2012 09:34:55 +0100 In-Reply-To: References: Organization: Citrix Systems, Inc. X-Mailer: Evolution 3.4.3-1 MIME-Version: 1.0 Cc: "xen-users@lists.xen.org" Subject: Re: [Xen-users] xl create bug on first-attempt with passthrough X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org On Fri, 2012-09-21 at 18:49 +0100, Casey DeLorme wrote: > The first attempt to pass a PCI device after booting the system gives > me these messages (on "xl create"): > > > libxl: error: libxl_dom.c:557:libxl__build_hvm: hvm building failed > libxl: error: libxl_create.c:901:domcreate_rebuild_done: cannot (re-)build domain: -3 > libxl: error: libxl_dm.c:1239:libxl__destroy_device_model: could not find device-model's pid for dom 1 > libxl: error: libxl.c:1427:libxl__destroy_domid: libxl__destroy_device_model failed for 1 xl -vvv create might tell you a bit more but it seems likely that the interesting logs will be in /var/log/xen/qemu-dm-.log or in the Xen dmesg. Ian. _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Mon Sep 24 08:35:58 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Mon, 24 Sep 2012 08:35:58 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TG484-0007rk-Pg; Mon, 24 Sep 2012 08:35:00 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TG483-0007rd-6H for xen-users@lists.xen.org; Mon, 24 Sep 2012 08:34:59 +0000 Received: from [85.158.143.99:5484] by server-3.bemta-4.messagelabs.com id 39/E5-10986-23B10605; Mon, 24 Sep 2012 08:34:58 +0000 X-Env-Sender: Ian.Campbell@citrix.com X-Msg-Ref: server-13.tower-216.messagelabs.com!1348475697!30590430!1 X-Originating-IP: [62.200.22.115] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogNjIuMjAwLjIyLjExNSA9PiAxMTA4NDA=\n X-StarScan-Received: X-StarScan-Version: 6.6.1.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 26340 invoked from network); 24 Sep 2012 08:34:57 -0000 Received: from smtp.ctxuk.citrix.com (HELO SMTP.EU.CITRIX.COM) (62.200.22.115) by server-13.tower-216.messagelabs.com with RC4-SHA encrypted SMTP; 24 Sep 2012 08:34:57 -0000 X-IronPort-AV: E=Sophos;i="4.80,474,1344211200"; d="scan'208";a="14715882" Received: from lonpmailmx01.citrite.net ([10.30.203.162]) by LONPIPO01.EU.CITRIX.COM with ESMTP/TLS/RC4-MD5; 24 Sep 2012 08:34:56 +0000 Received: from [10.80.2.42] (10.80.2.42) by LONPMAILMX01.citrite.net (10.30.203.162) with Microsoft SMTP Server id 8.3.279.1; Mon, 24 Sep 2012 09:34:57 +0100 Message-ID: <1348475695.3452.39.camel@zakaz.uk.xensource.com> From: Ian Campbell To: Casey DeLorme Date: Mon, 24 Sep 2012 09:34:55 +0100 In-Reply-To: References: Organization: Citrix Systems, Inc. X-Mailer: Evolution 3.4.3-1 MIME-Version: 1.0 Cc: "xen-users@lists.xen.org" Subject: Re: [Xen-users] xl create bug on first-attempt with passthrough X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org On Fri, 2012-09-21 at 18:49 +0100, Casey DeLorme wrote: > The first attempt to pass a PCI device after booting the system gives > me these messages (on "xl create"): > > > libxl: error: libxl_dom.c:557:libxl__build_hvm: hvm building failed > libxl: error: libxl_create.c:901:domcreate_rebuild_done: cannot (re-)build domain: -3 > libxl: error: libxl_dm.c:1239:libxl__destroy_device_model: could not find device-model's pid for dom 1 > libxl: error: libxl.c:1427:libxl__destroy_domid: libxl__destroy_device_model failed for 1 xl -vvv create might tell you a bit more but it seems likely that the interesting logs will be in /var/log/xen/qemu-dm-.log or in the Xen dmesg. Ian. _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Mon Sep 24 08:39:13 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Mon, 24 Sep 2012 08:39:13 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TG4BI-000896-Hv; Mon, 24 Sep 2012 08:38:20 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TG4BG-000891-Pf for xen-users@lists.xen.org; Mon, 24 Sep 2012 08:38:18 +0000 Received: from [85.158.143.99:39297] by server-2.bemta-4.messagelabs.com id A1/4B-06610-AFB10605; Mon, 24 Sep 2012 08:38:18 +0000 X-Env-Sender: Ian.Campbell@citrix.com X-Msg-Ref: server-9.tower-216.messagelabs.com!1348475897!31538075!1 X-Originating-IP: [62.200.22.115] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogNjIuMjAwLjIyLjExNSA9PiAxMTA4NDA=\n X-StarScan-Received: X-StarScan-Version: 6.6.1.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 512 invoked from network); 24 Sep 2012 08:38:17 -0000 Received: from smtp.eu.citrix.com (HELO SMTP.EU.CITRIX.COM) (62.200.22.115) by server-9.tower-216.messagelabs.com with RC4-SHA encrypted SMTP; 24 Sep 2012 08:38:17 -0000 X-IronPort-AV: E=Sophos;i="4.80,474,1344211200"; d="scan'208";a="14715964" Received: from lonpmailmx01.citrite.net ([10.30.203.162]) by LONPIPO01.EU.CITRIX.COM with ESMTP/TLS/RC4-MD5; 24 Sep 2012 08:38:16 +0000 Received: from [10.80.2.42] (10.80.2.42) by LONPMAILMX01.citrite.net (10.30.203.162) with Microsoft SMTP Server id 8.3.279.1; Mon, 24 Sep 2012 09:38:17 +0100 Message-ID: <1348475895.3452.43.camel@zakaz.uk.xensource.com> From: Ian Campbell To: Skippy VonDrake Date: Mon, 24 Sep 2012 09:38:15 +0100 In-Reply-To: References: Organization: Citrix Systems, Inc. X-Mailer: Evolution 3.4.3-1 MIME-Version: 1.0 Cc: "xen-users@lists.xen.org" Subject: Re: [Xen-users] xl cfg disk option for lvm and cdrom X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org On Fri, 2012-09-21 at 19:35 +0100, Skippy VonDrake wrote: > I configured an LogicalVolume of 15G to install an XP hvm on. > > But I don't know how to define the 'disk' configuration for the config > script for "xl create". > I also don't know the format for the cdrom disk entry. The xl.cfg(5) man pages references docs/misc/xl-disk-configuration.txt which defines the syntax. You can find this in the Xen source tree or online at http://xenbits.xen.org/docs/4.2-testing/ (or .../unstable/). One helpful tip for debugging this sort of thing is to do xl -N block-attach 0 This will print out the result of parsing disk-spec (-N == dry-run) so you can see if it looks like what you were trying to say. Ian. _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Mon Sep 24 08:39:13 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Mon, 24 Sep 2012 08:39:13 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TG4BI-000896-Hv; Mon, 24 Sep 2012 08:38:20 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TG4BG-000891-Pf for xen-users@lists.xen.org; Mon, 24 Sep 2012 08:38:18 +0000 Received: from [85.158.143.99:39297] by server-2.bemta-4.messagelabs.com id A1/4B-06610-AFB10605; Mon, 24 Sep 2012 08:38:18 +0000 X-Env-Sender: Ian.Campbell@citrix.com X-Msg-Ref: server-9.tower-216.messagelabs.com!1348475897!31538075!1 X-Originating-IP: [62.200.22.115] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogNjIuMjAwLjIyLjExNSA9PiAxMTA4NDA=\n X-StarScan-Received: X-StarScan-Version: 6.6.1.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 512 invoked from network); 24 Sep 2012 08:38:17 -0000 Received: from smtp.eu.citrix.com (HELO SMTP.EU.CITRIX.COM) (62.200.22.115) by server-9.tower-216.messagelabs.com with RC4-SHA encrypted SMTP; 24 Sep 2012 08:38:17 -0000 X-IronPort-AV: E=Sophos;i="4.80,474,1344211200"; d="scan'208";a="14715964" Received: from lonpmailmx01.citrite.net ([10.30.203.162]) by LONPIPO01.EU.CITRIX.COM with ESMTP/TLS/RC4-MD5; 24 Sep 2012 08:38:16 +0000 Received: from [10.80.2.42] (10.80.2.42) by LONPMAILMX01.citrite.net (10.30.203.162) with Microsoft SMTP Server id 8.3.279.1; Mon, 24 Sep 2012 09:38:17 +0100 Message-ID: <1348475895.3452.43.camel@zakaz.uk.xensource.com> From: Ian Campbell To: Skippy VonDrake Date: Mon, 24 Sep 2012 09:38:15 +0100 In-Reply-To: References: Organization: Citrix Systems, Inc. X-Mailer: Evolution 3.4.3-1 MIME-Version: 1.0 Cc: "xen-users@lists.xen.org" Subject: Re: [Xen-users] xl cfg disk option for lvm and cdrom X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org On Fri, 2012-09-21 at 19:35 +0100, Skippy VonDrake wrote: > I configured an LogicalVolume of 15G to install an XP hvm on. > > But I don't know how to define the 'disk' configuration for the config > script for "xl create". > I also don't know the format for the cdrom disk entry. The xl.cfg(5) man pages references docs/misc/xl-disk-configuration.txt which defines the syntax. You can find this in the Xen source tree or online at http://xenbits.xen.org/docs/4.2-testing/ (or .../unstable/). One helpful tip for debugging this sort of thing is to do xl -N block-attach 0 This will print out the result of parsing disk-spec (-N == dry-run) so you can see if it looks like what you were trying to say. Ian. _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Mon Sep 24 08:57:09 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Mon, 24 Sep 2012 08:57:09 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TG4Ss-0000V7-MZ; Mon, 24 Sep 2012 08:56:30 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TG4Sr-0000V2-5x for xen-users@lists.xen.org; Mon, 24 Sep 2012 08:56:29 +0000 Received: from [85.158.139.83:58822] by server-11.bemta-5.messagelabs.com id 16/C8-13866-C3020605; Mon, 24 Sep 2012 08:56:28 +0000 X-Env-Sender: cdelorme@gmail.com X-Msg-Ref: server-8.tower-182.messagelabs.com!1348476985!17729926!1 X-Originating-IP: [209.85.219.45] X-SpamReason: No, hits=0.4 required=7.0 tests=HTML_30_40,HTML_MESSAGE, ML_RADAR_SPEW_LINKS_14,RCVD_BY_IP,spamassassin: X-StarScan-Received: X-StarScan-Version: 6.6.1.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 16979 invoked from network); 24 Sep 2012 08:56:27 -0000 Received: from mail-oa0-f45.google.com (HELO mail-oa0-f45.google.com) (209.85.219.45) by server-8.tower-182.messagelabs.com with RC4-SHA encrypted SMTP; 24 Sep 2012 08:56:27 -0000 Received: by oagi18 with SMTP id i18so686140oag.32 for ; Mon, 24 Sep 2012 01:56:25 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=Qr3H6HvsmFe5+2GGmNL2FOlqgEGs/D0jKUUm9JfB7K0=; b=vjB4DYXhW6y1Hdr4dA3g/Wm0B8j1siZxfWPCZg3RGyDETOBGhbmLE0KsbNK0NUKxQx zxB9yf/sXv3cDMr1shHprtPNQCh8P1+9Z+NhmMj3crVj0lrwF4DuhR9Mojp3jsog0+NW X1kDXoPgrNCWWDI6EY37IMmBeaZiTUY/yLjIHHPV8bqoRy+c45WY8he42upEoiodeCaM ozuUmAg5ujcL64lnLUOJ5dTQqayDytunqC0iRYjYhQnv4L1F5jut8qmj9/RrlZNF58pO QvNNtyBUOo8rWzxHThTeOd+zkoml9vyvQxOXfp+G38IO+2O5sKSnn87DxyExHZXT+usa Tw3Q== MIME-Version: 1.0 Received: by 10.182.18.143 with SMTP id w15mr9138249obd.6.1348476985574; Mon, 24 Sep 2012 01:56:25 -0700 (PDT) Received: by 10.76.19.148 with HTTP; Mon, 24 Sep 2012 01:56:25 -0700 (PDT) In-Reply-To: <1348475695.3452.39.camel@zakaz.uk.xensource.com> References: <1348475695.3452.39.camel@zakaz.uk.xensource.com> Date: Mon, 24 Sep 2012 04:56:25 -0400 Message-ID: From: Casey DeLorme To: Ian Campbell Cc: "xen-users@lists.xen.org" Subject: Re: [Xen-users] xl create bug on first-attempt with passthrough X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============7374009390279967536==" Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org --===============7374009390279967536== Content-Type: multipart/alternative; boundary=f46d043c824ab686a804ca6ec3ed --f46d043c824ab686a804ca6ec3ed Content-Type: text/plain; charset=ISO-8859-1 That's the odd part, absolutely no logs are generated when it errors out. Also, if I run the same xl create command immediately after, it works just fine. On Mon, Sep 24, 2012 at 4:34 AM, Ian Campbell wrote: > On Fri, 2012-09-21 at 18:49 +0100, Casey DeLorme wrote: > > The first attempt to pass a PCI device after booting the system gives > > me these messages (on "xl create"): > > > > > > libxl: error: libxl_dom.c:557:libxl__build_hvm: hvm building failed > > libxl: error: libxl_create.c:901:domcreate_rebuild_done: cannot > (re-)build domain: -3 > > libxl: error: libxl_dm.c:1239:libxl__destroy_device_model: could not > find device-model's pid for dom 1 > > libxl: error: libxl.c:1427:libxl__destroy_domid: > libxl__destroy_device_model failed for 1 > > xl -vvv create might tell you a bit more but it seems likely that the > interesting logs will be in /var/log/xen/qemu-dm-.log or in the > Xen dmesg. > > Ian. > > > --f46d043c824ab686a804ca6ec3ed Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable That's the odd part, absolutely no logs are generated when it errors ou= t.

Also, if I run the same xl create command immediately= after, it works just fine.

On Mon= , Sep 24, 2012 at 4:34 AM, Ian Campbell <Ian.Campbell@citrix.com= > wrote:
On Fri, 2012-09-21 at 18:4= 9 +0100, Casey DeLorme wrote:
> The first attempt to pass a PCI device after booting the system gives<= br> > me these messages (on "xl create"):
>
>
> libxl: error: libxl_dom.c:557:libxl__build_hvm: hvm building failed > libxl: error: libxl_create.c:901:domcreate_rebuild_done: cannot (re-)b= uild domain: -3
> libxl: error: libxl_dm.c:1239:libxl__destroy_device_model: could not f= ind device-model's pid for dom 1
> libxl: error: libxl.c:1427:libxl__destroy_domid: libxl__destroy_device= _model failed for 1

xl -vvv create might tell you a bit more but it seems likely that the=
interesting logs will be in /var/log/xen/qemu-dm-<name>.log or in the=
Xen dmesg.

Ian.



--f46d043c824ab686a804ca6ec3ed-- --===============7374009390279967536== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users --===============7374009390279967536==-- From xen-users-bounces@lists.xen.org Mon Sep 24 08:57:09 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Mon, 24 Sep 2012 08:57:09 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TG4Ss-0000V7-MZ; Mon, 24 Sep 2012 08:56:30 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TG4Sr-0000V2-5x for xen-users@lists.xen.org; Mon, 24 Sep 2012 08:56:29 +0000 Received: from [85.158.139.83:58822] by server-11.bemta-5.messagelabs.com id 16/C8-13866-C3020605; Mon, 24 Sep 2012 08:56:28 +0000 X-Env-Sender: cdelorme@gmail.com X-Msg-Ref: server-8.tower-182.messagelabs.com!1348476985!17729926!1 X-Originating-IP: [209.85.219.45] X-SpamReason: No, hits=0.4 required=7.0 tests=HTML_30_40,HTML_MESSAGE, ML_RADAR_SPEW_LINKS_14,RCVD_BY_IP,spamassassin: X-StarScan-Received: X-StarScan-Version: 6.6.1.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 16979 invoked from network); 24 Sep 2012 08:56:27 -0000 Received: from mail-oa0-f45.google.com (HELO mail-oa0-f45.google.com) (209.85.219.45) by server-8.tower-182.messagelabs.com with RC4-SHA encrypted SMTP; 24 Sep 2012 08:56:27 -0000 Received: by oagi18 with SMTP id i18so686140oag.32 for ; Mon, 24 Sep 2012 01:56:25 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=Qr3H6HvsmFe5+2GGmNL2FOlqgEGs/D0jKUUm9JfB7K0=; b=vjB4DYXhW6y1Hdr4dA3g/Wm0B8j1siZxfWPCZg3RGyDETOBGhbmLE0KsbNK0NUKxQx zxB9yf/sXv3cDMr1shHprtPNQCh8P1+9Z+NhmMj3crVj0lrwF4DuhR9Mojp3jsog0+NW X1kDXoPgrNCWWDI6EY37IMmBeaZiTUY/yLjIHHPV8bqoRy+c45WY8he42upEoiodeCaM ozuUmAg5ujcL64lnLUOJ5dTQqayDytunqC0iRYjYhQnv4L1F5jut8qmj9/RrlZNF58pO QvNNtyBUOo8rWzxHThTeOd+zkoml9vyvQxOXfp+G38IO+2O5sKSnn87DxyExHZXT+usa Tw3Q== MIME-Version: 1.0 Received: by 10.182.18.143 with SMTP id w15mr9138249obd.6.1348476985574; Mon, 24 Sep 2012 01:56:25 -0700 (PDT) Received: by 10.76.19.148 with HTTP; Mon, 24 Sep 2012 01:56:25 -0700 (PDT) In-Reply-To: <1348475695.3452.39.camel@zakaz.uk.xensource.com> References: <1348475695.3452.39.camel@zakaz.uk.xensource.com> Date: Mon, 24 Sep 2012 04:56:25 -0400 Message-ID: From: Casey DeLorme To: Ian Campbell Cc: "xen-users@lists.xen.org" Subject: Re: [Xen-users] xl create bug on first-attempt with passthrough X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============7374009390279967536==" Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org --===============7374009390279967536== Content-Type: multipart/alternative; boundary=f46d043c824ab686a804ca6ec3ed --f46d043c824ab686a804ca6ec3ed Content-Type: text/plain; charset=ISO-8859-1 That's the odd part, absolutely no logs are generated when it errors out. Also, if I run the same xl create command immediately after, it works just fine. On Mon, Sep 24, 2012 at 4:34 AM, Ian Campbell wrote: > On Fri, 2012-09-21 at 18:49 +0100, Casey DeLorme wrote: > > The first attempt to pass a PCI device after booting the system gives > > me these messages (on "xl create"): > > > > > > libxl: error: libxl_dom.c:557:libxl__build_hvm: hvm building failed > > libxl: error: libxl_create.c:901:domcreate_rebuild_done: cannot > (re-)build domain: -3 > > libxl: error: libxl_dm.c:1239:libxl__destroy_device_model: could not > find device-model's pid for dom 1 > > libxl: error: libxl.c:1427:libxl__destroy_domid: > libxl__destroy_device_model failed for 1 > > xl -vvv create might tell you a bit more but it seems likely that the > interesting logs will be in /var/log/xen/qemu-dm-.log or in the > Xen dmesg. > > Ian. > > > --f46d043c824ab686a804ca6ec3ed Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable That's the odd part, absolutely no logs are generated when it errors ou= t.

Also, if I run the same xl create command immediately= after, it works just fine.

On Mon= , Sep 24, 2012 at 4:34 AM, Ian Campbell <Ian.Campbell@citrix.com= > wrote:
On Fri, 2012-09-21 at 18:4= 9 +0100, Casey DeLorme wrote:
> The first attempt to pass a PCI device after booting the system gives<= br> > me these messages (on "xl create"):
>
>
> libxl: error: libxl_dom.c:557:libxl__build_hvm: hvm building failed > libxl: error: libxl_create.c:901:domcreate_rebuild_done: cannot (re-)b= uild domain: -3
> libxl: error: libxl_dm.c:1239:libxl__destroy_device_model: could not f= ind device-model's pid for dom 1
> libxl: error: libxl.c:1427:libxl__destroy_domid: libxl__destroy_device= _model failed for 1

xl -vvv create might tell you a bit more but it seems likely that the=
interesting logs will be in /var/log/xen/qemu-dm-<name>.log or in the=
Xen dmesg.

Ian.



--f46d043c824ab686a804ca6ec3ed-- --===============7374009390279967536== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users --===============7374009390279967536==-- From xen-users-bounces@lists.xen.org Mon Sep 24 09:10:20 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Mon, 24 Sep 2012 09:10:20 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TG4fT-00010O-8g; Mon, 24 Sep 2012 09:09:31 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TG4fR-00010I-OL for xen-users@lists.xen.org; Mon, 24 Sep 2012 09:09:29 +0000 Received: from [85.158.143.99:52712] by server-1.bemta-4.messagelabs.com id D1/91-05684-84320605; Mon, 24 Sep 2012 09:09:28 +0000 X-Env-Sender: Ian.Campbell@citrix.com X-Msg-Ref: server-5.tower-216.messagelabs.com!1348477768!31173965!1 X-Originating-IP: [62.200.22.115] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogNjIuMjAwLjIyLjExNSA9PiAxMTA4NDk=\n X-StarScan-Received: X-StarScan-Version: 6.6.1.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 24034 invoked from network); 24 Sep 2012 09:09:28 -0000 Received: from smtp.eu.citrix.com (HELO SMTP.EU.CITRIX.COM) (62.200.22.115) by server-5.tower-216.messagelabs.com with RC4-SHA encrypted SMTP; 24 Sep 2012 09:09:28 -0000 X-IronPort-AV: E=Sophos;i="4.80,474,1344211200"; d="scan'208";a="14716946" Received: from lonpmailmx01.citrite.net ([10.30.203.162]) by LONPIPO01.EU.CITRIX.COM with ESMTP/TLS/RC4-MD5; 24 Sep 2012 09:09:28 +0000 Received: from [10.80.2.42] (10.80.2.42) by LONPMAILMX01.citrite.net (10.30.203.162) with Microsoft SMTP Server id 8.3.279.1; Mon, 24 Sep 2012 10:09:27 +0100 Message-ID: <1348477766.3452.52.camel@zakaz.uk.xensource.com> From: Ian Campbell To: Casey DeLorme Date: Mon, 24 Sep 2012 10:09:26 +0100 In-Reply-To: References: <1348475695.3452.39.camel@zakaz.uk.xensource.com> Organization: Citrix Systems, Inc. X-Mailer: Evolution 3.4.3-1 MIME-Version: 1.0 Cc: "xen-users@lists.xen.org" Subject: Re: [Xen-users] xl create bug on first-attempt with passthrough X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org Can you not top post please, it makes the flow of a conversation hard to follow. On Mon, 2012-09-24 at 09:56 +0100, Casey DeLorme wrote: > That's the odd part, absolutely no logs are generated when it errors > out. Are you sure you have run "xl -vvv create", because AFAICT there is no way that "hvm building failed" can be the first message printed in verbose mode. Ian. _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Mon Sep 24 09:10:20 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Mon, 24 Sep 2012 09:10:20 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TG4fT-00010O-8g; Mon, 24 Sep 2012 09:09:31 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TG4fR-00010I-OL for xen-users@lists.xen.org; Mon, 24 Sep 2012 09:09:29 +0000 Received: from [85.158.143.99:52712] by server-1.bemta-4.messagelabs.com id D1/91-05684-84320605; Mon, 24 Sep 2012 09:09:28 +0000 X-Env-Sender: Ian.Campbell@citrix.com X-Msg-Ref: server-5.tower-216.messagelabs.com!1348477768!31173965!1 X-Originating-IP: [62.200.22.115] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogNjIuMjAwLjIyLjExNSA9PiAxMTA4NDk=\n X-StarScan-Received: X-StarScan-Version: 6.6.1.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 24034 invoked from network); 24 Sep 2012 09:09:28 -0000 Received: from smtp.eu.citrix.com (HELO SMTP.EU.CITRIX.COM) (62.200.22.115) by server-5.tower-216.messagelabs.com with RC4-SHA encrypted SMTP; 24 Sep 2012 09:09:28 -0000 X-IronPort-AV: E=Sophos;i="4.80,474,1344211200"; d="scan'208";a="14716946" Received: from lonpmailmx01.citrite.net ([10.30.203.162]) by LONPIPO01.EU.CITRIX.COM with ESMTP/TLS/RC4-MD5; 24 Sep 2012 09:09:28 +0000 Received: from [10.80.2.42] (10.80.2.42) by LONPMAILMX01.citrite.net (10.30.203.162) with Microsoft SMTP Server id 8.3.279.1; Mon, 24 Sep 2012 10:09:27 +0100 Message-ID: <1348477766.3452.52.camel@zakaz.uk.xensource.com> From: Ian Campbell To: Casey DeLorme Date: Mon, 24 Sep 2012 10:09:26 +0100 In-Reply-To: References: <1348475695.3452.39.camel@zakaz.uk.xensource.com> Organization: Citrix Systems, Inc. X-Mailer: Evolution 3.4.3-1 MIME-Version: 1.0 Cc: "xen-users@lists.xen.org" Subject: Re: [Xen-users] xl create bug on first-attempt with passthrough X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org Can you not top post please, it makes the flow of a conversation hard to follow. On Mon, 2012-09-24 at 09:56 +0100, Casey DeLorme wrote: > That's the odd part, absolutely no logs are generated when it errors > out. Are you sure you have run "xl -vvv create", because AFAICT there is no way that "hvm building failed" can be the first message printed in verbose mode. Ian. _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Mon Sep 24 09:43:32 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Mon, 24 Sep 2012 09:43:32 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TG5Bc-0001bu-IT; Mon, 24 Sep 2012 09:42:44 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TG5Bb-0001bp-7x for xen-users@lists.xen.org; Mon, 24 Sep 2012 09:42:43 +0000 Received: from [85.158.139.83:18310] by server-6.bemta-5.messagelabs.com id B5/30-14717-21B20605; Mon, 24 Sep 2012 09:42:42 +0000 X-Env-Sender: Ian.Campbell@citrix.com X-Msg-Ref: server-6.tower-182.messagelabs.com!1348479761!27940593!1 X-Originating-IP: [62.200.22.115] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogNjIuMjAwLjIyLjExNSA9PiAxMTA4NDk=\n X-StarScan-Received: X-StarScan-Version: 6.6.1.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 18141 invoked from network); 24 Sep 2012 09:42:41 -0000 Received: from smtp.ctxuk.citrix.com (HELO SMTP.EU.CITRIX.COM) (62.200.22.115) by server-6.tower-182.messagelabs.com with RC4-SHA encrypted SMTP; 24 Sep 2012 09:42:41 -0000 X-IronPort-AV: E=Sophos;i="4.80,474,1344211200"; d="scan'208";a="14718028" Received: from lonpmailmx01.citrite.net ([10.30.203.162]) by LONPIPO01.EU.CITRIX.COM with ESMTP/TLS/RC4-MD5; 24 Sep 2012 09:42:40 +0000 Received: from [10.80.2.42] (10.80.2.42) by LONPMAILMX01.citrite.net (10.30.203.162) with Microsoft SMTP Server id 8.3.279.1; Mon, 24 Sep 2012 10:42:40 +0100 Message-ID: <1348479759.3452.59.camel@zakaz.uk.xensource.com> From: Ian Campbell To: Casey DeLorme Date: Mon, 24 Sep 2012 10:42:39 +0100 In-Reply-To: References: <1348475695.3452.39.camel@zakaz.uk.xensource.com> <1348477766.3452.52.camel@zakaz.uk.xensource.com> Organization: Citrix Systems, Inc. X-Mailer: Evolution 3.4.3-1 MIME-Version: 1.0 Cc: xen-users Subject: Re: [Xen-users] xl create bug on first-attempt with passthrough X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org Please can you keep the ML in the loop. I have added it back this time. On Mon, 2012-09-24 at 10:23 +0100, Casey DeLorme wrote: > Sorry it was not intentional, gmail automatically positions my > response above the last message. So please move the cursor before you start typing. This will also give you the opportunity to trim your quotes to the appropriate amount of context. > First attempt after rebooting the platform running "xl -vvv > create /etc/xen/windows.cfg" yields: > > cdelorme@xen:~$ xl -vvv create /etc/xen/windows.cfg > Parsing config from /etc/xen/windows.cfg > libxl: debug: libxl_create.c:1173:do_domain_create: ao 0x1480890: create: how=(nil) callback=(nil) poller=0x1480b80 > libxl: debug: libxl_device.c:229:libxl__device_disk_set_backend: Disk vdev=hda spec.backend=unknown > libxl: debug: libxl_device.c:265:libxl__device_disk_set_backend: Disk vdev=hda, using backend phy > libxl: debug: libxl_create.c:677:initiate_domain_create: running bootloader > libxl: debug: libxl_bootloader.c:321:libxl__bootloader_run: not a PV domain, skipping bootloader > libxl: debug: libxl_event.c:561:libxl__ev_xswatch_deregister: watch w=0x1481bd0: deregister unregistered > libxl: notice: libxl_numa.c:451:libxl__get_numa_candidate: NUMA placement failed, performance might be affected > xc: detail: elf_parse_binary: phdr: paddr=0x100000 memsz=0x9df08 > xc: detail: elf_parse_binary: memory: 0x100000 -> 0x19df08 > xc: info: VIRTUAL MEMORY ARRANGEMENT: > Loader: 0000000000100000->000000000019df08 > TOTAL: 0000000000000000->00000001ff000000 > ENTRY ADDRESS: 0000000000100000 > xc: detail: Failed allocation for dom 1: 2048 extents of order 0 > xc: error: Could not allocate memory for HVM guest. (16 = Device or resource busy): Internal error Here is your actual error message. I have two guesses as to what is happening here. First is that, for some reason, dom0 is too slow to balloon down and xl has failed to notice this somehow. By the time you run your second domain domain 0 has caught up. The other option is that perhaps xl is underestimating the RAM required to start the domain (perhaps passthrough adds some additional memory overhead which it doesn't correctly account for) but by making room for this first domain it inadvertently adds enough slack to the system that a starting the second time succeeds. If this is the case then there is a second order bug here which is that xl didn't balloon backup after the initial domain create failed. Either way this sounds like a bug in xl's autoballooning code, it would be useful to report as such on xen-devel. One obvious solution/workaround would be to use the dom0_mem option and disable auto ballooning. Ian. _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Mon Sep 24 09:43:32 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Mon, 24 Sep 2012 09:43:32 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TG5Bc-0001bu-IT; Mon, 24 Sep 2012 09:42:44 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TG5Bb-0001bp-7x for xen-users@lists.xen.org; Mon, 24 Sep 2012 09:42:43 +0000 Received: from [85.158.139.83:18310] by server-6.bemta-5.messagelabs.com id B5/30-14717-21B20605; Mon, 24 Sep 2012 09:42:42 +0000 X-Env-Sender: Ian.Campbell@citrix.com X-Msg-Ref: server-6.tower-182.messagelabs.com!1348479761!27940593!1 X-Originating-IP: [62.200.22.115] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogNjIuMjAwLjIyLjExNSA9PiAxMTA4NDk=\n X-StarScan-Received: X-StarScan-Version: 6.6.1.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 18141 invoked from network); 24 Sep 2012 09:42:41 -0000 Received: from smtp.ctxuk.citrix.com (HELO SMTP.EU.CITRIX.COM) (62.200.22.115) by server-6.tower-182.messagelabs.com with RC4-SHA encrypted SMTP; 24 Sep 2012 09:42:41 -0000 X-IronPort-AV: E=Sophos;i="4.80,474,1344211200"; d="scan'208";a="14718028" Received: from lonpmailmx01.citrite.net ([10.30.203.162]) by LONPIPO01.EU.CITRIX.COM with ESMTP/TLS/RC4-MD5; 24 Sep 2012 09:42:40 +0000 Received: from [10.80.2.42] (10.80.2.42) by LONPMAILMX01.citrite.net (10.30.203.162) with Microsoft SMTP Server id 8.3.279.1; Mon, 24 Sep 2012 10:42:40 +0100 Message-ID: <1348479759.3452.59.camel@zakaz.uk.xensource.com> From: Ian Campbell To: Casey DeLorme Date: Mon, 24 Sep 2012 10:42:39 +0100 In-Reply-To: References: <1348475695.3452.39.camel@zakaz.uk.xensource.com> <1348477766.3452.52.camel@zakaz.uk.xensource.com> Organization: Citrix Systems, Inc. X-Mailer: Evolution 3.4.3-1 MIME-Version: 1.0 Cc: xen-users Subject: Re: [Xen-users] xl create bug on first-attempt with passthrough X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org Please can you keep the ML in the loop. I have added it back this time. On Mon, 2012-09-24 at 10:23 +0100, Casey DeLorme wrote: > Sorry it was not intentional, gmail automatically positions my > response above the last message. So please move the cursor before you start typing. This will also give you the opportunity to trim your quotes to the appropriate amount of context. > First attempt after rebooting the platform running "xl -vvv > create /etc/xen/windows.cfg" yields: > > cdelorme@xen:~$ xl -vvv create /etc/xen/windows.cfg > Parsing config from /etc/xen/windows.cfg > libxl: debug: libxl_create.c:1173:do_domain_create: ao 0x1480890: create: how=(nil) callback=(nil) poller=0x1480b80 > libxl: debug: libxl_device.c:229:libxl__device_disk_set_backend: Disk vdev=hda spec.backend=unknown > libxl: debug: libxl_device.c:265:libxl__device_disk_set_backend: Disk vdev=hda, using backend phy > libxl: debug: libxl_create.c:677:initiate_domain_create: running bootloader > libxl: debug: libxl_bootloader.c:321:libxl__bootloader_run: not a PV domain, skipping bootloader > libxl: debug: libxl_event.c:561:libxl__ev_xswatch_deregister: watch w=0x1481bd0: deregister unregistered > libxl: notice: libxl_numa.c:451:libxl__get_numa_candidate: NUMA placement failed, performance might be affected > xc: detail: elf_parse_binary: phdr: paddr=0x100000 memsz=0x9df08 > xc: detail: elf_parse_binary: memory: 0x100000 -> 0x19df08 > xc: info: VIRTUAL MEMORY ARRANGEMENT: > Loader: 0000000000100000->000000000019df08 > TOTAL: 0000000000000000->00000001ff000000 > ENTRY ADDRESS: 0000000000100000 > xc: detail: Failed allocation for dom 1: 2048 extents of order 0 > xc: error: Could not allocate memory for HVM guest. (16 = Device or resource busy): Internal error Here is your actual error message. I have two guesses as to what is happening here. First is that, for some reason, dom0 is too slow to balloon down and xl has failed to notice this somehow. By the time you run your second domain domain 0 has caught up. The other option is that perhaps xl is underestimating the RAM required to start the domain (perhaps passthrough adds some additional memory overhead which it doesn't correctly account for) but by making room for this first domain it inadvertently adds enough slack to the system that a starting the second time succeeds. If this is the case then there is a second order bug here which is that xl didn't balloon backup after the initial domain create failed. Either way this sounds like a bug in xl's autoballooning code, it would be useful to report as such on xen-devel. One obvious solution/workaround would be to use the dom0_mem option and disable auto ballooning. Ian. _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Mon Sep 24 10:49:37 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Mon, 24 Sep 2012 10:49:37 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TG6DL-0002Yy-M6; Mon, 24 Sep 2012 10:48:35 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TG6DK-0002Yq-Kk for xen-users@lists.xen.org; Mon, 24 Sep 2012 10:48:34 +0000 Received: from [85.158.143.99:40371] by server-1.bemta-4.messagelabs.com id F8/C8-05684-18A30605; Mon, 24 Sep 2012 10:48:33 +0000 X-Env-Sender: cdelorme@gmail.com X-Msg-Ref: server-13.tower-216.messagelabs.com!1348483711!30613349!1 X-Originating-IP: [209.85.214.173] X-SpamReason: No, hits=0.4 required=7.0 tests=HTML_30_40,HTML_MESSAGE, ML_RADAR_SPEW_LINKS_14,RCVD_BY_IP,spamassassin: X-StarScan-Received: X-StarScan-Version: 6.6.1.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 20932 invoked from network); 24 Sep 2012 10:48:33 -0000 Received: from mail-ob0-f173.google.com (HELO mail-ob0-f173.google.com) (209.85.214.173) by server-13.tower-216.messagelabs.com with RC4-SHA encrypted SMTP; 24 Sep 2012 10:48:33 -0000 Received: by obbta14 with SMTP id ta14so6791744obb.32 for ; Mon, 24 Sep 2012 03:48:31 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=wTPfye7GjoLo2Fs2AKn+sPyyhHlNTW5bzm5P1drpQXg=; b=h50Ze1XPDTYWbM6mfLs/3HijoQxotRO/q0w1Ya85CHsydSUOpyUEPxJvoqRZkUGy6p VsRG8VpMfeOwurlxcMI1Uu/JGxLli3Rk1SY8FP5HcqdrwyfMMVcYLm9FCNe65kS4auRk MPW/SorC5Z6UUAjUYaX3sf4piKf5y4Mn7qy/qM4GJZ9Ws1ObtJvMXXUSmEA8rMMzoZGW aP0lGUjte1GLcNIBbPKdzSdINKiVrB2TeQWWQ3kVK/XpwYAAETVHckfQxQ1+HDcGn+Eq CC1D2Ok5XRJiSxhDtRHWrOEhQBihKl5atbCSonQXm6WJsciKgf5hQjxBNNonn432DwZH WQgA== MIME-Version: 1.0 Received: by 10.60.170.229 with SMTP id ap5mr9340672oec.101.1348483711660; Mon, 24 Sep 2012 03:48:31 -0700 (PDT) Received: by 10.76.19.148 with HTTP; Mon, 24 Sep 2012 03:48:31 -0700 (PDT) In-Reply-To: <1348479759.3452.59.camel@zakaz.uk.xensource.com> References: <1348475695.3452.39.camel@zakaz.uk.xensource.com> <1348477766.3452.52.camel@zakaz.uk.xensource.com> <1348479759.3452.59.camel@zakaz.uk.xensource.com> Date: Mon, 24 Sep 2012 06:48:31 -0400 Message-ID: From: Casey DeLorme To: Ian Campbell Cc: xen-users Subject: Re: [Xen-users] xl create bug on first-attempt with passthrough X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============5330563228343291841==" Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org --===============5330563228343291841== Content-Type: multipart/alternative; boundary=bcaec54b4ac09e72d104ca70540a --bcaec54b4ac09e72d104ca70540a Content-Type: text/plain; charset=ISO-8859-1 Sorry, thought I hit reply all, this time making sure I do it right. I have two guesses as to what is happening here. > > First is that, for some reason, dom0 is too slow to balloon down and xl > has failed to notice this somehow. By the time you run your second > domain domain 0 has caught up. > > The other option is that perhaps xl is underestimating the RAM required > to start the domain (perhaps passthrough adds some additional memory > overhead which it doesn't correctly account for) but by making room for > this first domain it inadvertently adds enough slack to the system that > a starting the second time succeeds. If this is the case then there is a > second order bug here which is that xl didn't balloon backup after the > initial domain create failed. > > You are probably right, I changed some equipment and went from 6GB of RAM and 3 devices to 8GB of RAM and 4 devices. I tried dropping it to 4GB but that didn't seem to solve the problem either. Either way this sounds like a bug in xl's autoballooning code, it would > be useful to report as such on xen-devel. > > Should I forward this response to the xen-devel list, or just create a brand new message? > One obvious solution/workaround would be to use the dom0_mem option and > disable auto ballooning. > > I will give this a try after work today and report back. Thanks very much for your help and advice on this. ~Casey --bcaec54b4ac09e72d104ca70540a Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable
Sorry, thought I hit reply all, this time making sure I do it right.

I have two guesses as to what is happening here.

First is that, for some reason, dom0 is too slow to balloon down and xl
has failed to notice this somehow. By the time you run your second
domain domain 0 has caught up.

The other option is that perhaps xl is underestimating the RAM required
to start the domain (perhaps passthrough adds some additional memory
overhead which it doesn't correctly account for) but by making room for=
this first domain it inadvertently adds enough slack to the system that
a starting the second time succeeds. If this is the case then there is a second order bug here which is that xl didn't balloon backup after the<= br> initial domain create failed.


You are probably right, I changed some= equipment and went from 6GB of RAM and 3 devices to 8GB of RAM and 4 devic= es. =A0I tried dropping it to 4GB but that didn't seem to solve the pro= blem either.

Either way this sounds like a bug in xl's autoballooning code, it would=
be useful to report as such on xen-devel.


Should I forward this response to the = xen-devel list, or just create a brand new message?
=A0
One obvious solution/workaround would be to use the dom0_mem option and
disable auto ballooning.


I will give this a try after work today and report b= ack.

Thanks very much for your help and advice on = this.

~Casey
--bcaec54b4ac09e72d104ca70540a-- --===============5330563228343291841== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users --===============5330563228343291841==-- From xen-users-bounces@lists.xen.org Mon Sep 24 10:49:37 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Mon, 24 Sep 2012 10:49:37 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TG6DL-0002Yy-M6; Mon, 24 Sep 2012 10:48:35 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TG6DK-0002Yq-Kk for xen-users@lists.xen.org; Mon, 24 Sep 2012 10:48:34 +0000 Received: from [85.158.143.99:40371] by server-1.bemta-4.messagelabs.com id F8/C8-05684-18A30605; Mon, 24 Sep 2012 10:48:33 +0000 X-Env-Sender: cdelorme@gmail.com X-Msg-Ref: server-13.tower-216.messagelabs.com!1348483711!30613349!1 X-Originating-IP: [209.85.214.173] X-SpamReason: No, hits=0.4 required=7.0 tests=HTML_30_40,HTML_MESSAGE, ML_RADAR_SPEW_LINKS_14,RCVD_BY_IP,spamassassin: X-StarScan-Received: X-StarScan-Version: 6.6.1.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 20932 invoked from network); 24 Sep 2012 10:48:33 -0000 Received: from mail-ob0-f173.google.com (HELO mail-ob0-f173.google.com) (209.85.214.173) by server-13.tower-216.messagelabs.com with RC4-SHA encrypted SMTP; 24 Sep 2012 10:48:33 -0000 Received: by obbta14 with SMTP id ta14so6791744obb.32 for ; Mon, 24 Sep 2012 03:48:31 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=wTPfye7GjoLo2Fs2AKn+sPyyhHlNTW5bzm5P1drpQXg=; b=h50Ze1XPDTYWbM6mfLs/3HijoQxotRO/q0w1Ya85CHsydSUOpyUEPxJvoqRZkUGy6p VsRG8VpMfeOwurlxcMI1Uu/JGxLli3Rk1SY8FP5HcqdrwyfMMVcYLm9FCNe65kS4auRk MPW/SorC5Z6UUAjUYaX3sf4piKf5y4Mn7qy/qM4GJZ9Ws1ObtJvMXXUSmEA8rMMzoZGW aP0lGUjte1GLcNIBbPKdzSdINKiVrB2TeQWWQ3kVK/XpwYAAETVHckfQxQ1+HDcGn+Eq CC1D2Ok5XRJiSxhDtRHWrOEhQBihKl5atbCSonQXm6WJsciKgf5hQjxBNNonn432DwZH WQgA== MIME-Version: 1.0 Received: by 10.60.170.229 with SMTP id ap5mr9340672oec.101.1348483711660; Mon, 24 Sep 2012 03:48:31 -0700 (PDT) Received: by 10.76.19.148 with HTTP; Mon, 24 Sep 2012 03:48:31 -0700 (PDT) In-Reply-To: <1348479759.3452.59.camel@zakaz.uk.xensource.com> References: <1348475695.3452.39.camel@zakaz.uk.xensource.com> <1348477766.3452.52.camel@zakaz.uk.xensource.com> <1348479759.3452.59.camel@zakaz.uk.xensource.com> Date: Mon, 24 Sep 2012 06:48:31 -0400 Message-ID: From: Casey DeLorme To: Ian Campbell Cc: xen-users Subject: Re: [Xen-users] xl create bug on first-attempt with passthrough X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============5330563228343291841==" Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org --===============5330563228343291841== Content-Type: multipart/alternative; boundary=bcaec54b4ac09e72d104ca70540a --bcaec54b4ac09e72d104ca70540a Content-Type: text/plain; charset=ISO-8859-1 Sorry, thought I hit reply all, this time making sure I do it right. I have two guesses as to what is happening here. > > First is that, for some reason, dom0 is too slow to balloon down and xl > has failed to notice this somehow. By the time you run your second > domain domain 0 has caught up. > > The other option is that perhaps xl is underestimating the RAM required > to start the domain (perhaps passthrough adds some additional memory > overhead which it doesn't correctly account for) but by making room for > this first domain it inadvertently adds enough slack to the system that > a starting the second time succeeds. If this is the case then there is a > second order bug here which is that xl didn't balloon backup after the > initial domain create failed. > > You are probably right, I changed some equipment and went from 6GB of RAM and 3 devices to 8GB of RAM and 4 devices. I tried dropping it to 4GB but that didn't seem to solve the problem either. Either way this sounds like a bug in xl's autoballooning code, it would > be useful to report as such on xen-devel. > > Should I forward this response to the xen-devel list, or just create a brand new message? > One obvious solution/workaround would be to use the dom0_mem option and > disable auto ballooning. > > I will give this a try after work today and report back. Thanks very much for your help and advice on this. ~Casey --bcaec54b4ac09e72d104ca70540a Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable
Sorry, thought I hit reply all, this time making sure I do it right.

I have two guesses as to what is happening here.

First is that, for some reason, dom0 is too slow to balloon down and xl
has failed to notice this somehow. By the time you run your second
domain domain 0 has caught up.

The other option is that perhaps xl is underestimating the RAM required
to start the domain (perhaps passthrough adds some additional memory
overhead which it doesn't correctly account for) but by making room for=
this first domain it inadvertently adds enough slack to the system that
a starting the second time succeeds. If this is the case then there is a second order bug here which is that xl didn't balloon backup after the<= br> initial domain create failed.


You are probably right, I changed some= equipment and went from 6GB of RAM and 3 devices to 8GB of RAM and 4 devic= es. =A0I tried dropping it to 4GB but that didn't seem to solve the pro= blem either.

Either way this sounds like a bug in xl's autoballooning code, it would=
be useful to report as such on xen-devel.


Should I forward this response to the = xen-devel list, or just create a brand new message?
=A0
One obvious solution/workaround would be to use the dom0_mem option and
disable auto ballooning.


I will give this a try after work today and report b= ack.

Thanks very much for your help and advice on = this.

~Casey
--bcaec54b4ac09e72d104ca70540a-- --===============5330563228343291841== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users --===============5330563228343291841==-- From xen-users-bounces@lists.xen.org Mon Sep 24 11:57:34 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Mon, 24 Sep 2012 11:57:34 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TG7HG-0005KB-GB; Mon, 24 Sep 2012 11:56:42 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TG7HE-0005Jc-TD for xen-users@lists.xen.org; Mon, 24 Sep 2012 11:56:41 +0000 Received: from [85.158.139.211:64446] by server-11.bemta-5.messagelabs.com id 73/77-13866-77A40605; Mon, 24 Sep 2012 11:56:39 +0000 X-Env-Sender: singapore.mr.teo.en.ming@gmail.com X-Msg-Ref: server-4.tower-206.messagelabs.com!1348487794!19744968!1 X-Originating-IP: [209.85.160.45] X-SpamReason: No, hits=0.3 required=7.0 tests=ML_RADAR_SPEW_LINKS_14, RCVD_BY_IP,spamassassin: X-StarScan-Received: X-StarScan-Version: 6.6.1.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 23955 invoked from network); 24 Sep 2012 11:56:36 -0000 Received: from mail-pb0-f45.google.com (HELO mail-pb0-f45.google.com) (209.85.160.45) by server-4.tower-206.messagelabs.com with RC4-SHA encrypted SMTP; 24 Sep 2012 11:56:36 -0000 Received: by pbbrp2 with SMTP id rp2so1102708pbb.32 for ; Mon, 24 Sep 2012 04:56:34 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:disposition-notification-to:date:from:user-agent :mime-version:to:subject:content-type; bh=bkoSBOfrlNo1V759dGrXRbg9GLiCN/DnnDtbDYQ0DfM=; b=VruEDClSgvQxy8BPEA6BGrQDC+z+h/BcNyOdDn5lBFkdBqZrkjyFdltyiIE87VWd6f NKKTznGwHeWOM1/D+LlPv+HUMXKzKRsMNSCCC15MxrWhUN4xRfv0lGxhfy5wq3bZgBs6 kYDxMZ06g3u9kpQqa3Tp5SHSQWvacBmBd9LgVNMrlKBVDwE9QUi3/nLTggGrnnJcp/dI yemAsr0OE7L62jaO2cUTo1tpunEpf9z+rs1Evcofp55YjiiuXOX2ajjqhP8GzqXr2cQQ 3UyPruX1P/Cbsv2G6nVb/ZzPqXedy9zdtSs5ds1SfHz/ro15R7Lh2ZkRO90W75c4oJnf 1Sbg== Received: by 10.68.203.230 with SMTP id kt6mr35762427pbc.163.1348487794558; Mon, 24 Sep 2012 04:56:34 -0700 (PDT) Received: from [192.168.1.2] (cm141.gamma206.maxonline.com.sg. [202.156.206.141]) by mx.google.com with ESMTPS id bm8sm8662001pab.3.2012.09.24.04.56.31 (version=SSLv3 cipher=OTHER); Mon, 24 Sep 2012 04:56:34 -0700 (PDT) Message-ID: <50604A6E.3040305@gmail.com> Date: Mon, 24 Sep 2012 19:56:30 +0800 From: "Teo En Ming (Zhang Enming)" User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:10.0.2) Gecko/20120216 Thunderbird/10.0.2 MIME-Version: 1.0 To: "xen-users@lists.xen.org" , "xen-devel@lists.xen.org" , "Teo En Ming (Zhang Enming)" , Frank Lyon , David TECHER , Casey DeLorme , Tobias Geiger Content-Type: multipart/mixed; boundary="------------020803020300030807030301" Subject: [Xen-users] 100% Perfect Success in Xen 4.2-unstable Changeset 25099 VGA Passthrough with NVIDIA Quadro 6000 (Frank Lyon's Xen VGA Passthrough Configuration Files) X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org This is a multi-part message in MIME format. --------------020803020300030807030301 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Dear All, Frank Lyon (Singapore) engaged me to work on Xen VGA Passthrough for him. He started off contemplating VGA Passthrough using Xen Cloud Platform (XCP) but he couldn't get VGA Passthrough to work with it. Then he engaged a tech guy from a software consultancy firm in Singapore but the tech guy he engaged also couldn't get VGA Passthrough to work using Xen Cloud Platform. Finally Frank Lyon engaged me to work on Xen VGA Passthrough for him. I dropped XCP altogether because I have totally no experience with it at all. I finally got 100% perfect success in Xen VGA Passthrough with his NVIDIA Quadro 6000. Here are Frank Lyon's hardware specifications: Server: HP ProLiant DL370G6 Processors: 2x Intel Xeon CPU X5650 @ 2.67 GHz (2 Processors detected, 12 total cores detected per processor) Harddisks: 4X 1TB SAS MDL 6G DP 7.2K Harddisks Memory: 48GB of memory Display adapter: NVIDIA Quadro 6000 Here are Frank Lyon's software configuration: Host Operating System: Ubuntu 12.04 LTS Server CD HVM domU: Windows 7 64-bit and Windows 8 Pro 64-bit Xen Hypervisor version: 4.2-unstable Changeset 25099 Linux Dom0 Kernel: 3.5.4 (I compiled it from sources) Attached in this email are Xen VGA Passthrough configuration files and scripts I have configured for Frank Lyon's Xen VGA Passthrough server. Reference guides/tutorials followed in setting up Frank Lyon's Xen VGA Passthrough server (hosted on Xen Wiki): (1) http://wiki.xen.org/wiki/Building_and_Installing_Xen_4.x_and_Linux_Kernel_3.x_on_Ubuntu_and_Debian_Linux (2) http://wiki.xen.org/wiki/Xen_VGA_Passthrough_to_Windows_8_with_Xen_4.2-unstable The above two are guides/tutorials/HowTo/documentation I have written for (1) building and installing Xen 4.x and Linux Kernel 3.x on Ubuntu and Debian Linux and (2) Xen VGA Passthrough. Dear Jean David Techer, Now I have 100% success in getting Xen VGA Passthrough to work in Frank Lyon's Xen VGA Passthrough server, with Xen VGA Passthrough patches hosted at your personal website. The display adapter which was 100% successfully passed through in Frank Lyon's example is a NVIDIA Quadro 6000. I still have no idea why I have PARTIAL (less than 100%) success with Xen VGA Passthrough with my own NVIDIA Geforce 8400 GS VGA card. As I have told you before, there is a yellow exclamation mark with my NVIDIA Geforce 8400 GS in Device Manager in Windows XP and Windows 8 HVM domUs. I am so totally astonished and elated and happy that I could get 100% success in Xen VGA Passthrough with Frank Lyon's Xen VGA Passthrough server. The Xen VGA Passthrough patches hosted at your personal website definitely works. Thumbs up David Techer! There is ***ABSOLUTELY NO*** yellow exclamation mark with Frank Lyon's NVIDIA Quadro 6000 in Device Manager in Windows 7 and Windows 8 HVM domUs. I really wondered what's the problem with my case. I could get somebody else's Xen VGA Passthrough to work but yet I could not get mine to work 100%. Perhaps I should get another NVIDIA vga card to try out VGA Passthrough. Dear All, Although I have 100% success in Xen VGA Passthrough in Frank Lyon's case, it was done with Xen 4.2-unstable Changeset 25099. I couldn't get Xen VGA Passthrough to work with Xen 4.3-unstable. Perhaps the Xen developers could look into this problem? In addition, I cannot passthrough TWO NVIDIA Quadro 6000 to a single Windows 7 or Windows 8 HVM guest. Anybody knows how I could passthrough two GPUs to a single HVM? Windows 7 and Windows 8 HVM guests would go haywire with the 2nd NVIDIA Quadro 6000 plugged in. The 2nd NVIDIA Quadro 6000 needs to be unplugged. Anybody knows why? Please advise. Thank you very much for your kind attention. -- Yours sincerely, Mr. Teo En Ming (Zhang Enming) Singapore --------------020803020300030807030301 Content-Type: text/plain; name="40_custom" Content-Transfer-Encoding: 7bit Content-Disposition: attachment; filename="40_custom" #!/bin/sh exec tail -n +3 $0 # This file provides an easy way to add custom menu entries. Simply type the # menu entries you want to add after this comment. Be careful not to change # the 'exec tail' line above. menuentry 'Ubuntu 12.04 amd64 Release with Xen 4.3-unstable and Linux Kernel 3.5.4-xen-frank.lyon-sgp' --class gnu-linux --class gnu --class os { recordfail insmod part_msdos insmod ext2 search --no-floppy --fs-uuid --set=root d5ec6b7f-e1db-4b46-b050-d0bd46403f59 set root='(hd0,msdos1)' search --no-floppy --fs-uuid --set=root d5ec6b7f-e1db-4b46-b050-d0bd46403f59 multiboot /xen.gz module /vmlinuz-3.5.4-xen-frank.lyon-sgp placeholder root=/dev/mapper/snow-root dom0_mem=1024 console=tty quiet splash vt.handoff=7 nomodeset module /initrd.img-3.5.4-xen-frank.lyon-sgp } --------------020803020300030807030301 Content-Type: text/plain; name="dsdt.asl" Content-Transfer-Encoding: 7bit Content-Disposition: attachment; filename="dsdt.asl" /****************************************************************************** * DSDT for Xen with Qemu device model * * Copyright (c) 2004, Intel Corporation. * * This program is free software; you can redistribute it and/or modify it * under the terms and conditions of the GNU General Public License, * version 2, as published by the Free Software Foundation. * * This program is distributed in the hope it will be useful, but WITHOUT * ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or * FITNESS FOR A PARTICULAR PURPOSE. See the GNU General Public License for * more details. * * You should have received a copy of the GNU General Public License along with * this program; if not, write to the Free Software Foundation, Inc., 59 Temple * Place - Suite 330, Boston, MA 02111-1307 USA. */ DefinitionBlock ("DSDT.aml", "DSDT", 2, "Xen", "HVM", 0) { Name (\PMBS, 0x0C00) Name (\PMLN, 0x08) Name (\IOB1, 0x00) Name (\IOL1, 0x00) Name (\APCB, 0xFEC00000) Name (\APCL, 0x00010000) Name (\PUID, 0x00) /* _S3 and _S4 are in separate SSDTs */ Name (\_S5, Package (0x04) { 0x00, /* PM1a_CNT.SLP_TYP */ 0x00, /* PM1b_CNT.SLP_TYP */ 0x00, /* reserved */ 0x00 /* reserved */ }) Name(PICD, 0) Method(_PIC, 1) { Store(Arg0, PICD) } Scope (\_SB) { /* ACPI_INFO_PHYSICAL_ADDRESS == 0xFC000000 */ OperationRegion(BIOS, SystemMemory, 0xFC000000, 24) Field(BIOS, ByteAcc, NoLock, Preserve) { UAR1, 1, UAR2, 1, LTP1, 1, HPET, 1, Offset(4), PMIN, 32, PLEN, 32, MSUA, 32, /* MADT checksum address */ MAPA, 32, /* MADT LAPIC0 address */ VGIA, 32 /* VM generation id address */ } /* Fix HCT test for 0x400 pci memory: * - need to report low 640 MB mem as motherboard resource */ Device(MEM0) { Name(_HID, EISAID("PNP0C02")) Name(_CRS, ResourceTemplate() { QWordMemory( ResourceConsumer, PosDecode, MinFixed, MaxFixed, Cacheable, ReadWrite, 0x00000000, 0x00000000, 0x0009ffff, 0x00000000, 0x000a0000) }) } Device (PCI0) { Name (_HID, EisaId ("PNP0A03")) Name (_UID, 0x00) Name (_ADR, 0x00) Name (_BBN, 0x00) /* Make cirrues VGA S3 suspend/resume work in Windows XP/2003 */ Device (VGA) { Name (_ADR, 0x00020000) Method (_S1D, 0, NotSerialized) { Return (0x00) } Method (_S2D, 0, NotSerialized) { Return (0x00) } Method (_S3D, 0, NotSerialized) { Return (0x00) } } Method (_CRS, 0, NotSerialized) { Name (PRT0, ResourceTemplate () { /* bus number is from 0 - 255*/ WordBusNumber( ResourceProducer, MinFixed, MaxFixed, SubDecode, 0x0000, 0x0000, 0x00FF, 0x0000, 0x0100) IO (Decode16, 0x0CF8, 0x0CF8, 0x01, 0x08) WordIO( ResourceProducer, MinFixed, MaxFixed, PosDecode, EntireRange, 0x0000, 0x0000, 0x0CF7, 0x0000, 0x0CF8) WordIO( ResourceProducer, MinFixed, MaxFixed, PosDecode, EntireRange, 0x0000, 0x0D00, 0xFFFF, 0x0000, 0xF300) /* reserve memory for pci devices */ DWordMemory( ResourceProducer, PosDecode, MinFixed, MaxFixed, Cacheable, ReadWrite, 0x00000000, 0x000A0000, 0x000BFFFF, 0x00000000, 0x00020000) /* reserve MMIO BARs of gfx for 1:1 mapping */ DWordMemory( ResourceProducer, PosDecode, MinFixed, MaxFixed, Cacheable, ReadWrite, 0x00000000, 0xF8000000, 0xF9FFFFFF, 0x00000000, 0x02000000) DWordMemory( ResourceProducer, PosDecode, MinFixed, MaxFixed, NonCacheable, ReadWrite, 0x00000000, 0xD8000000, 0xDFFFFFFF, 0x00000000, 0x08000000) DWordMemory( ResourceProducer, PosDecode, MinFixed, MaxFixed, Cacheable, ReadWrite, 0x00000000, 0xD4000000, 0xD7FFFFFF, 0x00000000, 0x04000000) DWordMemory( ResourceProducer, PosDecode, MinFixed, MaxFixed, Cacheable, ReadWrite, 0x00000000, 0xFB000000, 0xFB07FFFF, 0x00000000, 0x00080000, ,, _Y01) }) CreateDWordField(PRT0, \_SB.PCI0._CRS._Y01._MIN, MMIN) CreateDWordField(PRT0, \_SB.PCI0._CRS._Y01._MAX, MMAX) CreateDWordField(PRT0, \_SB.PCI0._CRS._Y01._LEN, MLEN) Store(\_SB.PMIN, MMIN) Store(\_SB.PLEN, MLEN) Add(MMIN, MLEN, MMAX) Subtract(MMAX, One, MMAX) Return (PRT0) } Device(HPET) { Name(_HID, EISAID("PNP0103")) Name(_UID, 0) Method (_STA, 0, NotSerialized) { If(LEqual(\_SB.HPET, 0)) { Return(0x00) } Else { Return(0x0F) } } Name(_CRS, ResourceTemplate() { DWordMemory( ResourceConsumer, PosDecode, MinFixed, MaxFixed, NonCacheable, ReadWrite, 0x00000000, 0xFED00000, 0xFED003FF, 0x00000000, 0x00000400 /* 1K memory: FED00000 - FED003FF */ ) }) } Device (ISA) { Name (_ADR, 0x00010000) /* device 1, fn 0 */ OperationRegion(PIRQ, PCI_Config, 0x60, 0x4) Scope(\) { Field (\_SB.PCI0.ISA.PIRQ, ByteAcc, NoLock, Preserve) { PIRA, 8, PIRB, 8, PIRC, 8, PIRD, 8 } } Device (SYSR) { Name (_HID, EisaId ("PNP0C02")) Name (_UID, 0x01) Name (CRS, ResourceTemplate () { /* TODO: list hidden resources */ IO (Decode16, 0x0010, 0x0010, 0x00, 0x10) IO (Decode16, 0x0022, 0x0022, 0x00, 0x0C) IO (Decode16, 0x0030, 0x0030, 0x00, 0x10) IO (Decode16, 0x0044, 0x0044, 0x00, 0x1C) IO (Decode16, 0x0062, 0x0062, 0x00, 0x02) IO (Decode16, 0x0065, 0x0065, 0x00, 0x0B) IO (Decode16, 0x0072, 0x0072, 0x00, 0x0E) IO (Decode16, 0x0080, 0x0080, 0x00, 0x01) IO (Decode16, 0x0084, 0x0084, 0x00, 0x03) IO (Decode16, 0x0088, 0x0088, 0x00, 0x01) IO (Decode16, 0x008C, 0x008C, 0x00, 0x03) IO (Decode16, 0x0090, 0x0090, 0x00, 0x10) IO (Decode16, 0x00A2, 0x00A2, 0x00, 0x1C) IO (Decode16, 0x00E0, 0x00E0, 0x00, 0x10) IO (Decode16, 0x08A0, 0x08A0, 0x00, 0x04) IO (Decode16, 0x0CC0, 0x0CC0, 0x00, 0x10) IO (Decode16, 0x04D0, 0x04D0, 0x00, 0x02) }) Method (_CRS, 0, NotSerialized) { Return (CRS) } } Device (PIC) { Name (_HID, EisaId ("PNP0000")) Name (_CRS, ResourceTemplate () { IO (Decode16, 0x0020, 0x0020, 0x01, 0x02) IO (Decode16, 0x00A0, 0x00A0, 0x01, 0x02) IRQNoFlags () {2} }) } Device (DMA0) { Name (_HID, EisaId ("PNP0200")) Name (_CRS, ResourceTemplate () { DMA (Compatibility, BusMaster, Transfer8) {4} IO (Decode16, 0x0000, 0x0000, 0x00, 0x10) IO (Decode16, 0x0081, 0x0081, 0x00, 0x03) IO (Decode16, 0x0087, 0x0087, 0x00, 0x01) IO (Decode16, 0x0089, 0x0089, 0x00, 0x03) IO (Decode16, 0x008F, 0x008F, 0x00, 0x01) IO (Decode16, 0x00C0, 0x00C0, 0x00, 0x20) IO (Decode16, 0x0480, 0x0480, 0x00, 0x10) }) } Device (TMR) { Name (_HID, EisaId ("PNP0100")) Name (_CRS, ResourceTemplate () { IO (Decode16, 0x0040, 0x0040, 0x00, 0x04) IRQNoFlags () {0} }) } Device (RTC) { Name (_HID, EisaId ("PNP0B00")) Name (_CRS, ResourceTemplate () { IO (Decode16, 0x0070, 0x0070, 0x00, 0x02) IRQNoFlags () {8} }) } Device (SPKR) { Name (_HID, EisaId ("PNP0800")) Name (_CRS, ResourceTemplate () { IO (Decode16, 0x0061, 0x0061, 0x00, 0x01) }) } Device (PS2M) { Name (_HID, EisaId ("PNP0F13")) Name (_CID, 0x130FD041) Method (_STA, 0, NotSerialized) { Return (0x0F) } Name (_CRS, ResourceTemplate () { IRQNoFlags () {12} }) } Device (PS2K) { Name (_HID, EisaId ("PNP0303")) Name (_CID, 0x0B03D041) Method (_STA, 0, NotSerialized) { Return (0x0F) } Name (_CRS, ResourceTemplate () { IO (Decode16, 0x0060, 0x0060, 0x00, 0x01) IO (Decode16, 0x0064, 0x0064, 0x00, 0x01) IRQNoFlags () {1} }) } Device (FDC0) { Name (_HID, EisaId ("PNP0700")) Method (_STA, 0, NotSerialized) { Return (0x0F) } Name (_CRS, ResourceTemplate () { IO (Decode16, 0x03F0, 0x03F0, 0x01, 0x06) IO (Decode16, 0x03F7, 0x03F7, 0x01, 0x01) IRQNoFlags () {6} DMA (Compatibility, NotBusMaster, Transfer8) {2} }) } Device (UAR1) { Name (_HID, EisaId ("PNP0501")) Name (_UID, 0x01) Method (_STA, 0, NotSerialized) { If(LEqual(\_SB.UAR1, 0)) { Return(0x00) } Else { Return(0x0F) } } Name (_CRS, ResourceTemplate() { IO (Decode16, 0x03F8, 0x03F8, 8, 8) IRQNoFlags () {4} }) } Device (UAR2) { Name (_HID, EisaId ("PNP0501")) Name (_UID, 0x02) Method (_STA, 0, NotSerialized) { If(LEqual(\_SB.UAR2, 0)) { Return(0x00) } Else { Return(0x0F) } } Name (_CRS, ResourceTemplate() { IO (Decode16, 0x02F8, 0x02F8, 8, 8) IRQNoFlags () {3} }) } Device (LTP1) { Name (_HID, EisaId ("PNP0400")) Name (_UID, 0x02) Method (_STA, 0, NotSerialized) { If(LEqual(\_SB.LTP1, 0)) { Return(0x00) } Else { Return(0x0F) } } Name (_CRS, ResourceTemplate() { IO (Decode16, 0x0378, 0x0378, 0x08, 0x08) IRQNoFlags () {7} }) } Device(VGID) { Name(_HID, EisaID ("XEN0000")) Name(_UID, 0x00) Name(_CID, "VM_Gen_Counter") Name(_DDN, "VM_Gen_Counter") Method(_STA, 0, NotSerialized) { If(LEqual(\_SB.VGIA, 0x00000000)) { Return(0x00) } Else { Return(0x0F) } } Name(PKG, Package () { 0x00000000, 0x00000000 }) Method(ADDR, 0, NotSerialized) { Store(\_SB.VGIA, Index(PKG, 0)) Return(PKG) } } } } } } --------------020803020300030807030301 Content-Type: text/plain; name="grub" Content-Transfer-Encoding: 7bit Content-Disposition: attachment; filename="grub" # If you change this file, run 'update-grub' afterwards to update # /boot/grub/grub.cfg. # For full documentation of the options in this file, see: # info -f grub -n 'Simple configuration' GRUB_DEFAULT=13 #GRUB_HIDDEN_TIMEOUT=0 GRUB_HIDDEN_TIMEOUT_QUIET=true GRUB_TIMEOUT=50 GRUB_DISTRIBUTOR=`lsb_release -i -s 2> /dev/null || echo Debian` GRUB_CMDLINE_LINUX_DEFAULT="" GRUB_CMDLINE_LINUX="nomodeset" # Uncomment to enable BadRAM filtering, modify to suit your needs # This works with Linux (no patch required) and with any kernel that obtains # the memory map information from GRUB (GNU Mach, kernel of FreeBSD ...) #GRUB_BADRAM="0x01234567,0xfefefefe,0x89abcdef,0xefefefef" # Uncomment to disable graphical terminal (grub-pc only) #GRUB_TERMINAL=console # The resolution used on graphical terminal # note that you can use only modes which your graphic card supports via VBE # you can see them in real GRUB with the command `vbeinfo' #GRUB_GFXMODE=640x480 # Uncomment if you don't want GRUB to pass "root=UUID=xxx" parameter to Linux #GRUB_DISABLE_LINUX_UUID=true # Uncomment to disable generation of recovery mode menu entries #GRUB_DISABLE_RECOVERY="true" # Uncomment to get a beep at grub start #GRUB_INIT_TUNE="480 440 1" --------------020803020300030807030301 Content-Type: text/plain; name="rc.local" Content-Transfer-Encoding: 7bit Content-Disposition: attachment; filename="rc.local" #!/bin/sh -e # # rc.local # # This script is executed at the end of each multiuser runlevel. # Make sure that the script will "exit 0" on success or any other # value on error. # # In order to enable or disable this script just change the execution # bits. # # By default this script does nothing. sudo ifconfig eth0 up sudo route add default gw 192.168.25.1 sudo echo "nameserver 192.168.50.15" >> /etc/resolv.conf sudo echo "nameserver 192.168.50.30" >> /etc/resolv.conf exit 0 --------------020803020300030807030301 Content-Type: text/plain; name="start-windows" Content-Transfer-Encoding: 7bit Content-Disposition: attachment; filename="start-windows" #!/bin/sh set -x # #Loads pci-stub kernel module sudo modprobe pci-stub # #Passthrough NVIDIA Quadro 6000 # echo "Passthrough NVIDIA Quadro 6000 VGA card." sudo chmod o+w /sys/bus/pci/drivers/pci-stub/new_id sudo chmod o+w /sys/bus/pci/devices/0000:0d:00.0/driver/unbind sudo chmod o+w /sys/bus/pci/drivers/pci-stub/bind echo "10de 06d8" > /sys/bus/pci/drivers/pci-stub/new_id echo "0000:0d:00.0" > /sys/bus/pci/devices/0000:0d:00.0/driver/unbind echo "0000:0d:00.0" > /sys/bus/pci/drivers/pci-stub/bind # #Passthrough NVIDIA HD Audio Controller # echo "Passthrough NVIDIA HD Audio Controller." sudo chmod o+w /sys/bus/pci/drivers/pci-stub/new_id sudo chmod o+w /sys/bus/pci/devices/0000:0d:00.1/driver/unbind sudo chmod o+w /sys/bus/pci/drivers/pci-stub/bind echo "10de 0be5" > /sys/bus/pci/drivers/pci-stub/new_id echo "0000:0d:00.1" > /sys/bus/pci/devices/0000:0d:00.1/driver/unbind echo "0000:0d:00.1" > /sys/bus/pci/drivers/pci-stub/bind # #Passthrough 2nd NVIDIA Quadro 6000 # #echo "Passthrough 2nd NVIDIA Quadro 6000 VGA card." #sudo chmod o+w /sys/bus/pci/drivers/pci-stub/new_id #sudo chmod o+w /sys/bus/pci/devices/0000:1b:00.0/driver/unbind #sudo chmod o+w /sys/bus/pci/drivers/pci-stub/bind #echo "10de 06d8" > /sys/bus/pci/drivers/pci-stub/new_id #echo "0000:1b:00.0" > /sys/bus/pci/devices/0000:1b:00.0/driver/unbind #echo "0000:1b:00.0" > /sys/bus/pci/drivers/pci-stub/bind # #Passthrough 2nd NVIDIA HD Audio Controller # #echo "Passthrough 2nd NVIDIA HD Audio Controller." #sudo chmod o+w /sys/bus/pci/drivers/pci-stub/new_id #sudo chmod o+w /sys/bus/pci/devices/0000:1b:00.1/driver/unbind #sudo chmod o+w /sys/bus/pci/drivers/pci-stub/bind #echo "10de 0be5" > /sys/bus/pci/drivers/pci-stub/new_id #echo "0000:1b:00.1" > /sys/bus/pci/devices/0000:1b:00.1/driver/unbind #echo "0000:1b:00.1" > /sys/bus/pci/drivers/pci-stub/bind # #Passthrough USB 1.1 Controller #3 # echo "Passthrough USB 1.1 Controller #3" sudo chmod o+w /sys/bus/pci/drivers/pci-stub/new_id sudo chmod o+w /sys/bus/pci/devices/0000:00:1d.2/driver/unbind sudo chmod o+w /sys/bus/pci/drivers/pci-stub/bind echo "8086 3a36" > /sys/bus/pci/drivers/pci-stub/new_id echo "0000:00:1d.2" > /sys/bus/pci/devices/0000:00:1d.2/driver/unbind echo "0000:00:1d.2" > /sys/bus/pci/drivers/pci-stub/bind # #Passthrough USB 1.1 Controller #4 # echo "Passthrough USB 1.1 Controller #4" sudo chmod o+w /sys/bus/pci/drivers/pci-stub/new_id sudo chmod o+w /sys/bus/pci/devices/0000:00:1d.3/driver/unbind sudo chmod o+w /sys/bus/pci/drivers/pci-stub/bind echo "8086 3a39" > /sys/bus/pci/drivers/pci-stub/new_id echo "0000:00:1d.3" > /sys/bus/pci/devices/0000:00:1d.3/driver/unbind echo "0000:00:1d.3" > /sys/bus/pci/drivers/pci-stub/bind # #Wait for 10 seconds # sleep 10 # #Start Windows HVM domU with VGA Passthrough # sudo xl create /etc/xen/Windows7 #sudo xl create /etc/xen/Windows8 --------------020803020300030807030301 Content-Type: text/plain; name="Windows7" Content-Transfer-Encoding: 7bit Content-Disposition: attachment; filename="Windows7" # XL domain configuration file for Windows 8 Consumer Preview 64-bit English HVM domU # Please refer to "man xl.cfg" for further explanations. # See also docs/misc/xl-network-configuration.markdown and # docs/misc/xl-disk-configuration.txt # Written by Teo En Ming (Zhang Enming) # Email: teo.en.ming@gmail.com # Mobile Phone: +65-8369-2618 # Country: Singapore # Date: 18 Mar 2012 Sun name="Windows8" # Product Key: WJBRX-2N7B2-CCBF6-VPP97-R88XV builder="hvm" vcpus=2 memory=2048 on_poweroff="destroy" on_reboot="restart" on_crash="destroy" disk=[ 'format=raw, vdev=hda, access=rw, target=/etc/xen/images/windows7.img', 'format=raw, vdev=hdc, access=ro, devtype=cdrom, target=/home/flyon/windows7.iso' ] vif=[ 'bridge=eth0,type=ioemu,model=e1000' ] #boot=[c|d|n] # Selects the emulated virtual device to boot from. Options are hard disk (c), cd-rom (d) or network/PXE (n). # Multiple options can be given and will be attempted in the order they are given. e.g. to boot from cd-rom # but fallback to the hard disk you can give dc. The default is cd. boot="dc" acpi=1 #xen_platform_pci=1 #viridian=1 #stdvga=1 vnc=1 vnclisten="192.168.25.50" vncdisplay=0 vncunused=1 vncpasswd="" sdl=0 usb=1 # Passthrough the USB Keyboard usbdevice = "host:04f2:0110" # Passthrough the USB Optical Mouse usbdevice = "host:046d:c03d" # Enable Xen VGA Passthrough gfx_passthru=1 # VGA Passthrough NVIDIA Quadro 6000 and PCI Passthrough NVIDIA HD Audio Controller, then 2nd NVIDIA Quadro 6000 and 2nd NVIDIA HD Audio Controller #pci = [ '0d:00.0','0d:00.1','1b:00.0','1b:00.1' ] # The last 2 entries are USB 1.1 controllers. pci = [ '0d:00.0','0d:00.1','00:1d.2','00:1d.3' ] # PCI Passthrough Intel HD Audio Controller. #pci = [ '00:1b.0' ] # PCI Passthrough all the USB Controllers. # pci = [ '00:1a.0','00:1a.1','00:1a.2','00:1a.7','00:1d.0','00:1d.1','00:1d.2','00:1d.7' ] --------------020803020300030807030301 Content-Type: text/plain; name="Windows8" Content-Transfer-Encoding: 7bit Content-Disposition: attachment; filename="Windows8" # XL domain configuration file for Windows 8 Consumer Preview 64-bit English HVM domU # Please refer to "man xl.cfg" for further explanations. # See also docs/misc/xl-network-configuration.markdown and # docs/misc/xl-disk-configuration.txt # Written by Teo En Ming (Zhang Enming) # Email: teo.en.ming@gmail.com # Mobile Phone: +65-8369-2618 # Country: Singapore # Date: 18 Mar 2012 Sun name="Windows8" # Product Key: WJBRX-2N7B2-CCBF6-VPP97-R88XV builder="hvm" vcpus=2 memory=2048 on_poweroff="destroy" on_reboot="restart" on_crash="destroy" disk=[ 'format=raw, vdev=hda, access=rw, target=/etc/xen/images/windows8.img', 'format=raw, vdev=hdc, access=ro, devtype=cdrom, target=/home/flyon/windows8.iso' ] vif=[ 'bridge=eth0,type=ioemu,model=e1000' ] #boot=[c|d|n] # Selects the emulated virtual device to boot from. Options are hard disk (c), cd-rom (d) or network/PXE (n). # Multiple options can be given and will be attempted in the order they are given. e.g. to boot from cd-rom # but fallback to the hard disk you can give dc. The default is cd. boot="dc" acpi=1 #xen_platform_pci=1 #viridian=1 #stdvga=1 vnc=1 vnclisten="192.168.25.50" vncdisplay=0 vncunused=1 vncpasswd="" sdl=0 usb=1 # Passthrough the USB Keyboard usbdevice = "host:04f2:0110" # Passthrough the USB Optical Mouse usbdevice = "host:046d:c03d" # Enable Xen VGA Passthrough gfx_passthru=1 # VGA Passthrough NVIDIA Quadro 6000 and PCI Passthrough NVIDIA HD Audio Controller, then 2nd NVIDIA Quadro 6000 and 2nd NVIDIA HD Audio Controller #pci = [ '0d:00.0','0d:00.1','1b:00.0','1b:00.1' ] pci = [ '0d:00.0','0d:00.1' ] # PCI Passthrough Intel HD Audio Controller. #pci = [ '00:1b.0' ] # PCI Passthrough all the USB Controllers. # pci = [ '00:1a.0','00:1a.1','00:1a.2','00:1a.7','00:1d.0','00:1d.1','00:1d.2','00:1d.7' ] --------------020803020300030807030301 Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users --------------020803020300030807030301-- From xen-users-bounces@lists.xen.org Mon Sep 24 11:57:34 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Mon, 24 Sep 2012 11:57:34 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TG7HG-0005KB-GB; Mon, 24 Sep 2012 11:56:42 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TG7HE-0005Jc-TD for xen-users@lists.xen.org; Mon, 24 Sep 2012 11:56:41 +0000 Received: from [85.158.139.211:64446] by server-11.bemta-5.messagelabs.com id 73/77-13866-77A40605; Mon, 24 Sep 2012 11:56:39 +0000 X-Env-Sender: singapore.mr.teo.en.ming@gmail.com X-Msg-Ref: server-4.tower-206.messagelabs.com!1348487794!19744968!1 X-Originating-IP: [209.85.160.45] X-SpamReason: No, hits=0.3 required=7.0 tests=ML_RADAR_SPEW_LINKS_14, RCVD_BY_IP,spamassassin: X-StarScan-Received: X-StarScan-Version: 6.6.1.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 23955 invoked from network); 24 Sep 2012 11:56:36 -0000 Received: from mail-pb0-f45.google.com (HELO mail-pb0-f45.google.com) (209.85.160.45) by server-4.tower-206.messagelabs.com with RC4-SHA encrypted SMTP; 24 Sep 2012 11:56:36 -0000 Received: by pbbrp2 with SMTP id rp2so1102708pbb.32 for ; Mon, 24 Sep 2012 04:56:34 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:disposition-notification-to:date:from:user-agent :mime-version:to:subject:content-type; bh=bkoSBOfrlNo1V759dGrXRbg9GLiCN/DnnDtbDYQ0DfM=; b=VruEDClSgvQxy8BPEA6BGrQDC+z+h/BcNyOdDn5lBFkdBqZrkjyFdltyiIE87VWd6f NKKTznGwHeWOM1/D+LlPv+HUMXKzKRsMNSCCC15MxrWhUN4xRfv0lGxhfy5wq3bZgBs6 kYDxMZ06g3u9kpQqa3Tp5SHSQWvacBmBd9LgVNMrlKBVDwE9QUi3/nLTggGrnnJcp/dI yemAsr0OE7L62jaO2cUTo1tpunEpf9z+rs1Evcofp55YjiiuXOX2ajjqhP8GzqXr2cQQ 3UyPruX1P/Cbsv2G6nVb/ZzPqXedy9zdtSs5ds1SfHz/ro15R7Lh2ZkRO90W75c4oJnf 1Sbg== Received: by 10.68.203.230 with SMTP id kt6mr35762427pbc.163.1348487794558; Mon, 24 Sep 2012 04:56:34 -0700 (PDT) Received: from [192.168.1.2] (cm141.gamma206.maxonline.com.sg. [202.156.206.141]) by mx.google.com with ESMTPS id bm8sm8662001pab.3.2012.09.24.04.56.31 (version=SSLv3 cipher=OTHER); Mon, 24 Sep 2012 04:56:34 -0700 (PDT) Message-ID: <50604A6E.3040305@gmail.com> Date: Mon, 24 Sep 2012 19:56:30 +0800 From: "Teo En Ming (Zhang Enming)" User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:10.0.2) Gecko/20120216 Thunderbird/10.0.2 MIME-Version: 1.0 To: "xen-users@lists.xen.org" , "xen-devel@lists.xen.org" , "Teo En Ming (Zhang Enming)" , Frank Lyon , David TECHER , Casey DeLorme , Tobias Geiger Content-Type: multipart/mixed; boundary="------------020803020300030807030301" Subject: [Xen-users] 100% Perfect Success in Xen 4.2-unstable Changeset 25099 VGA Passthrough with NVIDIA Quadro 6000 (Frank Lyon's Xen VGA Passthrough Configuration Files) X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org This is a multi-part message in MIME format. --------------020803020300030807030301 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Dear All, Frank Lyon (Singapore) engaged me to work on Xen VGA Passthrough for him. He started off contemplating VGA Passthrough using Xen Cloud Platform (XCP) but he couldn't get VGA Passthrough to work with it. Then he engaged a tech guy from a software consultancy firm in Singapore but the tech guy he engaged also couldn't get VGA Passthrough to work using Xen Cloud Platform. Finally Frank Lyon engaged me to work on Xen VGA Passthrough for him. I dropped XCP altogether because I have totally no experience with it at all. I finally got 100% perfect success in Xen VGA Passthrough with his NVIDIA Quadro 6000. Here are Frank Lyon's hardware specifications: Server: HP ProLiant DL370G6 Processors: 2x Intel Xeon CPU X5650 @ 2.67 GHz (2 Processors detected, 12 total cores detected per processor) Harddisks: 4X 1TB SAS MDL 6G DP 7.2K Harddisks Memory: 48GB of memory Display adapter: NVIDIA Quadro 6000 Here are Frank Lyon's software configuration: Host Operating System: Ubuntu 12.04 LTS Server CD HVM domU: Windows 7 64-bit and Windows 8 Pro 64-bit Xen Hypervisor version: 4.2-unstable Changeset 25099 Linux Dom0 Kernel: 3.5.4 (I compiled it from sources) Attached in this email are Xen VGA Passthrough configuration files and scripts I have configured for Frank Lyon's Xen VGA Passthrough server. Reference guides/tutorials followed in setting up Frank Lyon's Xen VGA Passthrough server (hosted on Xen Wiki): (1) http://wiki.xen.org/wiki/Building_and_Installing_Xen_4.x_and_Linux_Kernel_3.x_on_Ubuntu_and_Debian_Linux (2) http://wiki.xen.org/wiki/Xen_VGA_Passthrough_to_Windows_8_with_Xen_4.2-unstable The above two are guides/tutorials/HowTo/documentation I have written for (1) building and installing Xen 4.x and Linux Kernel 3.x on Ubuntu and Debian Linux and (2) Xen VGA Passthrough. Dear Jean David Techer, Now I have 100% success in getting Xen VGA Passthrough to work in Frank Lyon's Xen VGA Passthrough server, with Xen VGA Passthrough patches hosted at your personal website. The display adapter which was 100% successfully passed through in Frank Lyon's example is a NVIDIA Quadro 6000. I still have no idea why I have PARTIAL (less than 100%) success with Xen VGA Passthrough with my own NVIDIA Geforce 8400 GS VGA card. As I have told you before, there is a yellow exclamation mark with my NVIDIA Geforce 8400 GS in Device Manager in Windows XP and Windows 8 HVM domUs. I am so totally astonished and elated and happy that I could get 100% success in Xen VGA Passthrough with Frank Lyon's Xen VGA Passthrough server. The Xen VGA Passthrough patches hosted at your personal website definitely works. Thumbs up David Techer! There is ***ABSOLUTELY NO*** yellow exclamation mark with Frank Lyon's NVIDIA Quadro 6000 in Device Manager in Windows 7 and Windows 8 HVM domUs. I really wondered what's the problem with my case. I could get somebody else's Xen VGA Passthrough to work but yet I could not get mine to work 100%. Perhaps I should get another NVIDIA vga card to try out VGA Passthrough. Dear All, Although I have 100% success in Xen VGA Passthrough in Frank Lyon's case, it was done with Xen 4.2-unstable Changeset 25099. I couldn't get Xen VGA Passthrough to work with Xen 4.3-unstable. Perhaps the Xen developers could look into this problem? In addition, I cannot passthrough TWO NVIDIA Quadro 6000 to a single Windows 7 or Windows 8 HVM guest. Anybody knows how I could passthrough two GPUs to a single HVM? Windows 7 and Windows 8 HVM guests would go haywire with the 2nd NVIDIA Quadro 6000 plugged in. The 2nd NVIDIA Quadro 6000 needs to be unplugged. Anybody knows why? Please advise. Thank you very much for your kind attention. -- Yours sincerely, Mr. Teo En Ming (Zhang Enming) Singapore --------------020803020300030807030301 Content-Type: text/plain; name="40_custom" Content-Transfer-Encoding: 7bit Content-Disposition: attachment; filename="40_custom" #!/bin/sh exec tail -n +3 $0 # This file provides an easy way to add custom menu entries. Simply type the # menu entries you want to add after this comment. Be careful not to change # the 'exec tail' line above. menuentry 'Ubuntu 12.04 amd64 Release with Xen 4.3-unstable and Linux Kernel 3.5.4-xen-frank.lyon-sgp' --class gnu-linux --class gnu --class os { recordfail insmod part_msdos insmod ext2 search --no-floppy --fs-uuid --set=root d5ec6b7f-e1db-4b46-b050-d0bd46403f59 set root='(hd0,msdos1)' search --no-floppy --fs-uuid --set=root d5ec6b7f-e1db-4b46-b050-d0bd46403f59 multiboot /xen.gz module /vmlinuz-3.5.4-xen-frank.lyon-sgp placeholder root=/dev/mapper/snow-root dom0_mem=1024 console=tty quiet splash vt.handoff=7 nomodeset module /initrd.img-3.5.4-xen-frank.lyon-sgp } --------------020803020300030807030301 Content-Type: text/plain; name="dsdt.asl" Content-Transfer-Encoding: 7bit Content-Disposition: attachment; filename="dsdt.asl" /****************************************************************************** * DSDT for Xen with Qemu device model * * Copyright (c) 2004, Intel Corporation. * * This program is free software; you can redistribute it and/or modify it * under the terms and conditions of the GNU General Public License, * version 2, as published by the Free Software Foundation. * * This program is distributed in the hope it will be useful, but WITHOUT * ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or * FITNESS FOR A PARTICULAR PURPOSE. See the GNU General Public License for * more details. * * You should have received a copy of the GNU General Public License along with * this program; if not, write to the Free Software Foundation, Inc., 59 Temple * Place - Suite 330, Boston, MA 02111-1307 USA. */ DefinitionBlock ("DSDT.aml", "DSDT", 2, "Xen", "HVM", 0) { Name (\PMBS, 0x0C00) Name (\PMLN, 0x08) Name (\IOB1, 0x00) Name (\IOL1, 0x00) Name (\APCB, 0xFEC00000) Name (\APCL, 0x00010000) Name (\PUID, 0x00) /* _S3 and _S4 are in separate SSDTs */ Name (\_S5, Package (0x04) { 0x00, /* PM1a_CNT.SLP_TYP */ 0x00, /* PM1b_CNT.SLP_TYP */ 0x00, /* reserved */ 0x00 /* reserved */ }) Name(PICD, 0) Method(_PIC, 1) { Store(Arg0, PICD) } Scope (\_SB) { /* ACPI_INFO_PHYSICAL_ADDRESS == 0xFC000000 */ OperationRegion(BIOS, SystemMemory, 0xFC000000, 24) Field(BIOS, ByteAcc, NoLock, Preserve) { UAR1, 1, UAR2, 1, LTP1, 1, HPET, 1, Offset(4), PMIN, 32, PLEN, 32, MSUA, 32, /* MADT checksum address */ MAPA, 32, /* MADT LAPIC0 address */ VGIA, 32 /* VM generation id address */ } /* Fix HCT test for 0x400 pci memory: * - need to report low 640 MB mem as motherboard resource */ Device(MEM0) { Name(_HID, EISAID("PNP0C02")) Name(_CRS, ResourceTemplate() { QWordMemory( ResourceConsumer, PosDecode, MinFixed, MaxFixed, Cacheable, ReadWrite, 0x00000000, 0x00000000, 0x0009ffff, 0x00000000, 0x000a0000) }) } Device (PCI0) { Name (_HID, EisaId ("PNP0A03")) Name (_UID, 0x00) Name (_ADR, 0x00) Name (_BBN, 0x00) /* Make cirrues VGA S3 suspend/resume work in Windows XP/2003 */ Device (VGA) { Name (_ADR, 0x00020000) Method (_S1D, 0, NotSerialized) { Return (0x00) } Method (_S2D, 0, NotSerialized) { Return (0x00) } Method (_S3D, 0, NotSerialized) { Return (0x00) } } Method (_CRS, 0, NotSerialized) { Name (PRT0, ResourceTemplate () { /* bus number is from 0 - 255*/ WordBusNumber( ResourceProducer, MinFixed, MaxFixed, SubDecode, 0x0000, 0x0000, 0x00FF, 0x0000, 0x0100) IO (Decode16, 0x0CF8, 0x0CF8, 0x01, 0x08) WordIO( ResourceProducer, MinFixed, MaxFixed, PosDecode, EntireRange, 0x0000, 0x0000, 0x0CF7, 0x0000, 0x0CF8) WordIO( ResourceProducer, MinFixed, MaxFixed, PosDecode, EntireRange, 0x0000, 0x0D00, 0xFFFF, 0x0000, 0xF300) /* reserve memory for pci devices */ DWordMemory( ResourceProducer, PosDecode, MinFixed, MaxFixed, Cacheable, ReadWrite, 0x00000000, 0x000A0000, 0x000BFFFF, 0x00000000, 0x00020000) /* reserve MMIO BARs of gfx for 1:1 mapping */ DWordMemory( ResourceProducer, PosDecode, MinFixed, MaxFixed, Cacheable, ReadWrite, 0x00000000, 0xF8000000, 0xF9FFFFFF, 0x00000000, 0x02000000) DWordMemory( ResourceProducer, PosDecode, MinFixed, MaxFixed, NonCacheable, ReadWrite, 0x00000000, 0xD8000000, 0xDFFFFFFF, 0x00000000, 0x08000000) DWordMemory( ResourceProducer, PosDecode, MinFixed, MaxFixed, Cacheable, ReadWrite, 0x00000000, 0xD4000000, 0xD7FFFFFF, 0x00000000, 0x04000000) DWordMemory( ResourceProducer, PosDecode, MinFixed, MaxFixed, Cacheable, ReadWrite, 0x00000000, 0xFB000000, 0xFB07FFFF, 0x00000000, 0x00080000, ,, _Y01) }) CreateDWordField(PRT0, \_SB.PCI0._CRS._Y01._MIN, MMIN) CreateDWordField(PRT0, \_SB.PCI0._CRS._Y01._MAX, MMAX) CreateDWordField(PRT0, \_SB.PCI0._CRS._Y01._LEN, MLEN) Store(\_SB.PMIN, MMIN) Store(\_SB.PLEN, MLEN) Add(MMIN, MLEN, MMAX) Subtract(MMAX, One, MMAX) Return (PRT0) } Device(HPET) { Name(_HID, EISAID("PNP0103")) Name(_UID, 0) Method (_STA, 0, NotSerialized) { If(LEqual(\_SB.HPET, 0)) { Return(0x00) } Else { Return(0x0F) } } Name(_CRS, ResourceTemplate() { DWordMemory( ResourceConsumer, PosDecode, MinFixed, MaxFixed, NonCacheable, ReadWrite, 0x00000000, 0xFED00000, 0xFED003FF, 0x00000000, 0x00000400 /* 1K memory: FED00000 - FED003FF */ ) }) } Device (ISA) { Name (_ADR, 0x00010000) /* device 1, fn 0 */ OperationRegion(PIRQ, PCI_Config, 0x60, 0x4) Scope(\) { Field (\_SB.PCI0.ISA.PIRQ, ByteAcc, NoLock, Preserve) { PIRA, 8, PIRB, 8, PIRC, 8, PIRD, 8 } } Device (SYSR) { Name (_HID, EisaId ("PNP0C02")) Name (_UID, 0x01) Name (CRS, ResourceTemplate () { /* TODO: list hidden resources */ IO (Decode16, 0x0010, 0x0010, 0x00, 0x10) IO (Decode16, 0x0022, 0x0022, 0x00, 0x0C) IO (Decode16, 0x0030, 0x0030, 0x00, 0x10) IO (Decode16, 0x0044, 0x0044, 0x00, 0x1C) IO (Decode16, 0x0062, 0x0062, 0x00, 0x02) IO (Decode16, 0x0065, 0x0065, 0x00, 0x0B) IO (Decode16, 0x0072, 0x0072, 0x00, 0x0E) IO (Decode16, 0x0080, 0x0080, 0x00, 0x01) IO (Decode16, 0x0084, 0x0084, 0x00, 0x03) IO (Decode16, 0x0088, 0x0088, 0x00, 0x01) IO (Decode16, 0x008C, 0x008C, 0x00, 0x03) IO (Decode16, 0x0090, 0x0090, 0x00, 0x10) IO (Decode16, 0x00A2, 0x00A2, 0x00, 0x1C) IO (Decode16, 0x00E0, 0x00E0, 0x00, 0x10) IO (Decode16, 0x08A0, 0x08A0, 0x00, 0x04) IO (Decode16, 0x0CC0, 0x0CC0, 0x00, 0x10) IO (Decode16, 0x04D0, 0x04D0, 0x00, 0x02) }) Method (_CRS, 0, NotSerialized) { Return (CRS) } } Device (PIC) { Name (_HID, EisaId ("PNP0000")) Name (_CRS, ResourceTemplate () { IO (Decode16, 0x0020, 0x0020, 0x01, 0x02) IO (Decode16, 0x00A0, 0x00A0, 0x01, 0x02) IRQNoFlags () {2} }) } Device (DMA0) { Name (_HID, EisaId ("PNP0200")) Name (_CRS, ResourceTemplate () { DMA (Compatibility, BusMaster, Transfer8) {4} IO (Decode16, 0x0000, 0x0000, 0x00, 0x10) IO (Decode16, 0x0081, 0x0081, 0x00, 0x03) IO (Decode16, 0x0087, 0x0087, 0x00, 0x01) IO (Decode16, 0x0089, 0x0089, 0x00, 0x03) IO (Decode16, 0x008F, 0x008F, 0x00, 0x01) IO (Decode16, 0x00C0, 0x00C0, 0x00, 0x20) IO (Decode16, 0x0480, 0x0480, 0x00, 0x10) }) } Device (TMR) { Name (_HID, EisaId ("PNP0100")) Name (_CRS, ResourceTemplate () { IO (Decode16, 0x0040, 0x0040, 0x00, 0x04) IRQNoFlags () {0} }) } Device (RTC) { Name (_HID, EisaId ("PNP0B00")) Name (_CRS, ResourceTemplate () { IO (Decode16, 0x0070, 0x0070, 0x00, 0x02) IRQNoFlags () {8} }) } Device (SPKR) { Name (_HID, EisaId ("PNP0800")) Name (_CRS, ResourceTemplate () { IO (Decode16, 0x0061, 0x0061, 0x00, 0x01) }) } Device (PS2M) { Name (_HID, EisaId ("PNP0F13")) Name (_CID, 0x130FD041) Method (_STA, 0, NotSerialized) { Return (0x0F) } Name (_CRS, ResourceTemplate () { IRQNoFlags () {12} }) } Device (PS2K) { Name (_HID, EisaId ("PNP0303")) Name (_CID, 0x0B03D041) Method (_STA, 0, NotSerialized) { Return (0x0F) } Name (_CRS, ResourceTemplate () { IO (Decode16, 0x0060, 0x0060, 0x00, 0x01) IO (Decode16, 0x0064, 0x0064, 0x00, 0x01) IRQNoFlags () {1} }) } Device (FDC0) { Name (_HID, EisaId ("PNP0700")) Method (_STA, 0, NotSerialized) { Return (0x0F) } Name (_CRS, ResourceTemplate () { IO (Decode16, 0x03F0, 0x03F0, 0x01, 0x06) IO (Decode16, 0x03F7, 0x03F7, 0x01, 0x01) IRQNoFlags () {6} DMA (Compatibility, NotBusMaster, Transfer8) {2} }) } Device (UAR1) { Name (_HID, EisaId ("PNP0501")) Name (_UID, 0x01) Method (_STA, 0, NotSerialized) { If(LEqual(\_SB.UAR1, 0)) { Return(0x00) } Else { Return(0x0F) } } Name (_CRS, ResourceTemplate() { IO (Decode16, 0x03F8, 0x03F8, 8, 8) IRQNoFlags () {4} }) } Device (UAR2) { Name (_HID, EisaId ("PNP0501")) Name (_UID, 0x02) Method (_STA, 0, NotSerialized) { If(LEqual(\_SB.UAR2, 0)) { Return(0x00) } Else { Return(0x0F) } } Name (_CRS, ResourceTemplate() { IO (Decode16, 0x02F8, 0x02F8, 8, 8) IRQNoFlags () {3} }) } Device (LTP1) { Name (_HID, EisaId ("PNP0400")) Name (_UID, 0x02) Method (_STA, 0, NotSerialized) { If(LEqual(\_SB.LTP1, 0)) { Return(0x00) } Else { Return(0x0F) } } Name (_CRS, ResourceTemplate() { IO (Decode16, 0x0378, 0x0378, 0x08, 0x08) IRQNoFlags () {7} }) } Device(VGID) { Name(_HID, EisaID ("XEN0000")) Name(_UID, 0x00) Name(_CID, "VM_Gen_Counter") Name(_DDN, "VM_Gen_Counter") Method(_STA, 0, NotSerialized) { If(LEqual(\_SB.VGIA, 0x00000000)) { Return(0x00) } Else { Return(0x0F) } } Name(PKG, Package () { 0x00000000, 0x00000000 }) Method(ADDR, 0, NotSerialized) { Store(\_SB.VGIA, Index(PKG, 0)) Return(PKG) } } } } } } --------------020803020300030807030301 Content-Type: text/plain; name="grub" Content-Transfer-Encoding: 7bit Content-Disposition: attachment; filename="grub" # If you change this file, run 'update-grub' afterwards to update # /boot/grub/grub.cfg. # For full documentation of the options in this file, see: # info -f grub -n 'Simple configuration' GRUB_DEFAULT=13 #GRUB_HIDDEN_TIMEOUT=0 GRUB_HIDDEN_TIMEOUT_QUIET=true GRUB_TIMEOUT=50 GRUB_DISTRIBUTOR=`lsb_release -i -s 2> /dev/null || echo Debian` GRUB_CMDLINE_LINUX_DEFAULT="" GRUB_CMDLINE_LINUX="nomodeset" # Uncomment to enable BadRAM filtering, modify to suit your needs # This works with Linux (no patch required) and with any kernel that obtains # the memory map information from GRUB (GNU Mach, kernel of FreeBSD ...) #GRUB_BADRAM="0x01234567,0xfefefefe,0x89abcdef,0xefefefef" # Uncomment to disable graphical terminal (grub-pc only) #GRUB_TERMINAL=console # The resolution used on graphical terminal # note that you can use only modes which your graphic card supports via VBE # you can see them in real GRUB with the command `vbeinfo' #GRUB_GFXMODE=640x480 # Uncomment if you don't want GRUB to pass "root=UUID=xxx" parameter to Linux #GRUB_DISABLE_LINUX_UUID=true # Uncomment to disable generation of recovery mode menu entries #GRUB_DISABLE_RECOVERY="true" # Uncomment to get a beep at grub start #GRUB_INIT_TUNE="480 440 1" --------------020803020300030807030301 Content-Type: text/plain; name="rc.local" Content-Transfer-Encoding: 7bit Content-Disposition: attachment; filename="rc.local" #!/bin/sh -e # # rc.local # # This script is executed at the end of each multiuser runlevel. # Make sure that the script will "exit 0" on success or any other # value on error. # # In order to enable or disable this script just change the execution # bits. # # By default this script does nothing. sudo ifconfig eth0 up sudo route add default gw 192.168.25.1 sudo echo "nameserver 192.168.50.15" >> /etc/resolv.conf sudo echo "nameserver 192.168.50.30" >> /etc/resolv.conf exit 0 --------------020803020300030807030301 Content-Type: text/plain; name="start-windows" Content-Transfer-Encoding: 7bit Content-Disposition: attachment; filename="start-windows" #!/bin/sh set -x # #Loads pci-stub kernel module sudo modprobe pci-stub # #Passthrough NVIDIA Quadro 6000 # echo "Passthrough NVIDIA Quadro 6000 VGA card." sudo chmod o+w /sys/bus/pci/drivers/pci-stub/new_id sudo chmod o+w /sys/bus/pci/devices/0000:0d:00.0/driver/unbind sudo chmod o+w /sys/bus/pci/drivers/pci-stub/bind echo "10de 06d8" > /sys/bus/pci/drivers/pci-stub/new_id echo "0000:0d:00.0" > /sys/bus/pci/devices/0000:0d:00.0/driver/unbind echo "0000:0d:00.0" > /sys/bus/pci/drivers/pci-stub/bind # #Passthrough NVIDIA HD Audio Controller # echo "Passthrough NVIDIA HD Audio Controller." sudo chmod o+w /sys/bus/pci/drivers/pci-stub/new_id sudo chmod o+w /sys/bus/pci/devices/0000:0d:00.1/driver/unbind sudo chmod o+w /sys/bus/pci/drivers/pci-stub/bind echo "10de 0be5" > /sys/bus/pci/drivers/pci-stub/new_id echo "0000:0d:00.1" > /sys/bus/pci/devices/0000:0d:00.1/driver/unbind echo "0000:0d:00.1" > /sys/bus/pci/drivers/pci-stub/bind # #Passthrough 2nd NVIDIA Quadro 6000 # #echo "Passthrough 2nd NVIDIA Quadro 6000 VGA card." #sudo chmod o+w /sys/bus/pci/drivers/pci-stub/new_id #sudo chmod o+w /sys/bus/pci/devices/0000:1b:00.0/driver/unbind #sudo chmod o+w /sys/bus/pci/drivers/pci-stub/bind #echo "10de 06d8" > /sys/bus/pci/drivers/pci-stub/new_id #echo "0000:1b:00.0" > /sys/bus/pci/devices/0000:1b:00.0/driver/unbind #echo "0000:1b:00.0" > /sys/bus/pci/drivers/pci-stub/bind # #Passthrough 2nd NVIDIA HD Audio Controller # #echo "Passthrough 2nd NVIDIA HD Audio Controller." #sudo chmod o+w /sys/bus/pci/drivers/pci-stub/new_id #sudo chmod o+w /sys/bus/pci/devices/0000:1b:00.1/driver/unbind #sudo chmod o+w /sys/bus/pci/drivers/pci-stub/bind #echo "10de 0be5" > /sys/bus/pci/drivers/pci-stub/new_id #echo "0000:1b:00.1" > /sys/bus/pci/devices/0000:1b:00.1/driver/unbind #echo "0000:1b:00.1" > /sys/bus/pci/drivers/pci-stub/bind # #Passthrough USB 1.1 Controller #3 # echo "Passthrough USB 1.1 Controller #3" sudo chmod o+w /sys/bus/pci/drivers/pci-stub/new_id sudo chmod o+w /sys/bus/pci/devices/0000:00:1d.2/driver/unbind sudo chmod o+w /sys/bus/pci/drivers/pci-stub/bind echo "8086 3a36" > /sys/bus/pci/drivers/pci-stub/new_id echo "0000:00:1d.2" > /sys/bus/pci/devices/0000:00:1d.2/driver/unbind echo "0000:00:1d.2" > /sys/bus/pci/drivers/pci-stub/bind # #Passthrough USB 1.1 Controller #4 # echo "Passthrough USB 1.1 Controller #4" sudo chmod o+w /sys/bus/pci/drivers/pci-stub/new_id sudo chmod o+w /sys/bus/pci/devices/0000:00:1d.3/driver/unbind sudo chmod o+w /sys/bus/pci/drivers/pci-stub/bind echo "8086 3a39" > /sys/bus/pci/drivers/pci-stub/new_id echo "0000:00:1d.3" > /sys/bus/pci/devices/0000:00:1d.3/driver/unbind echo "0000:00:1d.3" > /sys/bus/pci/drivers/pci-stub/bind # #Wait for 10 seconds # sleep 10 # #Start Windows HVM domU with VGA Passthrough # sudo xl create /etc/xen/Windows7 #sudo xl create /etc/xen/Windows8 --------------020803020300030807030301 Content-Type: text/plain; name="Windows7" Content-Transfer-Encoding: 7bit Content-Disposition: attachment; filename="Windows7" # XL domain configuration file for Windows 8 Consumer Preview 64-bit English HVM domU # Please refer to "man xl.cfg" for further explanations. # See also docs/misc/xl-network-configuration.markdown and # docs/misc/xl-disk-configuration.txt # Written by Teo En Ming (Zhang Enming) # Email: teo.en.ming@gmail.com # Mobile Phone: +65-8369-2618 # Country: Singapore # Date: 18 Mar 2012 Sun name="Windows8" # Product Key: WJBRX-2N7B2-CCBF6-VPP97-R88XV builder="hvm" vcpus=2 memory=2048 on_poweroff="destroy" on_reboot="restart" on_crash="destroy" disk=[ 'format=raw, vdev=hda, access=rw, target=/etc/xen/images/windows7.img', 'format=raw, vdev=hdc, access=ro, devtype=cdrom, target=/home/flyon/windows7.iso' ] vif=[ 'bridge=eth0,type=ioemu,model=e1000' ] #boot=[c|d|n] # Selects the emulated virtual device to boot from. Options are hard disk (c), cd-rom (d) or network/PXE (n). # Multiple options can be given and will be attempted in the order they are given. e.g. to boot from cd-rom # but fallback to the hard disk you can give dc. The default is cd. boot="dc" acpi=1 #xen_platform_pci=1 #viridian=1 #stdvga=1 vnc=1 vnclisten="192.168.25.50" vncdisplay=0 vncunused=1 vncpasswd="" sdl=0 usb=1 # Passthrough the USB Keyboard usbdevice = "host:04f2:0110" # Passthrough the USB Optical Mouse usbdevice = "host:046d:c03d" # Enable Xen VGA Passthrough gfx_passthru=1 # VGA Passthrough NVIDIA Quadro 6000 and PCI Passthrough NVIDIA HD Audio Controller, then 2nd NVIDIA Quadro 6000 and 2nd NVIDIA HD Audio Controller #pci = [ '0d:00.0','0d:00.1','1b:00.0','1b:00.1' ] # The last 2 entries are USB 1.1 controllers. pci = [ '0d:00.0','0d:00.1','00:1d.2','00:1d.3' ] # PCI Passthrough Intel HD Audio Controller. #pci = [ '00:1b.0' ] # PCI Passthrough all the USB Controllers. # pci = [ '00:1a.0','00:1a.1','00:1a.2','00:1a.7','00:1d.0','00:1d.1','00:1d.2','00:1d.7' ] --------------020803020300030807030301 Content-Type: text/plain; name="Windows8" Content-Transfer-Encoding: 7bit Content-Disposition: attachment; filename="Windows8" # XL domain configuration file for Windows 8 Consumer Preview 64-bit English HVM domU # Please refer to "man xl.cfg" for further explanations. # See also docs/misc/xl-network-configuration.markdown and # docs/misc/xl-disk-configuration.txt # Written by Teo En Ming (Zhang Enming) # Email: teo.en.ming@gmail.com # Mobile Phone: +65-8369-2618 # Country: Singapore # Date: 18 Mar 2012 Sun name="Windows8" # Product Key: WJBRX-2N7B2-CCBF6-VPP97-R88XV builder="hvm" vcpus=2 memory=2048 on_poweroff="destroy" on_reboot="restart" on_crash="destroy" disk=[ 'format=raw, vdev=hda, access=rw, target=/etc/xen/images/windows8.img', 'format=raw, vdev=hdc, access=ro, devtype=cdrom, target=/home/flyon/windows8.iso' ] vif=[ 'bridge=eth0,type=ioemu,model=e1000' ] #boot=[c|d|n] # Selects the emulated virtual device to boot from. Options are hard disk (c), cd-rom (d) or network/PXE (n). # Multiple options can be given and will be attempted in the order they are given. e.g. to boot from cd-rom # but fallback to the hard disk you can give dc. The default is cd. boot="dc" acpi=1 #xen_platform_pci=1 #viridian=1 #stdvga=1 vnc=1 vnclisten="192.168.25.50" vncdisplay=0 vncunused=1 vncpasswd="" sdl=0 usb=1 # Passthrough the USB Keyboard usbdevice = "host:04f2:0110" # Passthrough the USB Optical Mouse usbdevice = "host:046d:c03d" # Enable Xen VGA Passthrough gfx_passthru=1 # VGA Passthrough NVIDIA Quadro 6000 and PCI Passthrough NVIDIA HD Audio Controller, then 2nd NVIDIA Quadro 6000 and 2nd NVIDIA HD Audio Controller #pci = [ '0d:00.0','0d:00.1','1b:00.0','1b:00.1' ] pci = [ '0d:00.0','0d:00.1' ] # PCI Passthrough Intel HD Audio Controller. #pci = [ '00:1b.0' ] # PCI Passthrough all the USB Controllers. # pci = [ '00:1a.0','00:1a.1','00:1a.2','00:1a.7','00:1d.0','00:1d.1','00:1d.2','00:1d.7' ] --------------020803020300030807030301 Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users --------------020803020300030807030301-- From xen-users-bounces@lists.xen.org Mon Sep 24 12:50:15 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Mon, 24 Sep 2012 12:50:15 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TG86D-0008WF-VP; Mon, 24 Sep 2012 12:49:21 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TG86B-0008WA-JR for xen-users@lists.xen.org; Mon, 24 Sep 2012 12:49:20 +0000 Received: from [85.158.143.35:44408] by server-3.bemta-4.messagelabs.com id D4/17-10986-EC650605; Mon, 24 Sep 2012 12:49:18 +0000 X-Env-Sender: gu99roax@student.chalmers.se X-Msg-Ref: server-4.tower-21.messagelabs.com!1348490953!7872482!1 X-Originating-IP: [216.32.181.183] X-SpamReason: No, hits=1.4 required=7.0 tests=BODY_RANDOM_LONG, HTML_20_30,HTML_MESSAGE X-StarScan-Received: X-StarScan-Version: 6.6.1.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 27746 invoked from network); 24 Sep 2012 12:49:14 -0000 Received: from ch1ehsobe003.messaging.microsoft.com (HELO ch1outboundpool.messaging.microsoft.com) (216.32.181.183) by server-4.tower-21.messagelabs.com with AES128-SHA encrypted SMTP; 24 Sep 2012 12:49:14 -0000 Received: from mail75-ch1-R.bigfish.com (10.43.68.240) by CH1EHSOBE005.bigfish.com (10.43.70.55) with Microsoft SMTP Server id 14.1.225.23; Mon, 24 Sep 2012 12:49:12 +0000 Received: from mail75-ch1 (localhost [127.0.0.1]) by mail75-ch1-R.bigfish.com (Postfix) with ESMTP id EA212180278 for ; Mon, 24 Sep 2012 12:49:12 +0000 (UTC) X-Forefront-Antispam-Report: CIP:207.46.4.203; KIP:(null); UIP:(null); IPV:NLI; H:SN2PRD0102HT013.prod.exchangelabs.com; RD:none; EFVD:NLI X-SpamScore: -16 X-BigFish: PS-16(zzbb2dI98dI9371I1503M936eIc85eh1b0bI1432I1418I2176M1447Id6f1izz1d18h1202h1d1ah1d2ah1082kzz8275ch17326ah8275bh8275dh172cdfh5eeeKc704dhz2dh2a8h668h839h8e2h8e3hd25hf0ah107ah10d2h1288h12a5h12bdh137ahbe9i1155h) Received: from mail75-ch1 (localhost.localdomain [127.0.0.1]) by mail75-ch1 (MessageSwitch) id 1348490949561117_32047; Mon, 24 Sep 2012 12:49:09 +0000 (UTC) Received: from CH1EHSMHS031.bigfish.com (snatpool2.int.messaging.microsoft.com [10.43.68.236]) by mail75-ch1.bigfish.com (Postfix) with ESMTP id 7D9B416017C for ; Mon, 24 Sep 2012 12:49:09 +0000 (UTC) Received: from SN2PRD0102HT013.prod.exchangelabs.com (207.46.4.203) by CH1EHSMHS031.bigfish.com (10.43.70.31) with Microsoft SMTP Server (TLS) id 14.1.225.23; Mon, 24 Sep 2012 12:49:07 +0000 Received: from [10.40.137.93] (217.208.204.161) by pod51000.outlook.com (10.27.50.107) with Microsoft SMTP Server (TLS) id 14.15.108.4; Mon, 24 Sep 2012 12:49:05 +0000 Message-ID: <506056BC.3010705@student.chalmers.se> Date: Mon, 24 Sep 2012 14:49:00 +0200 From: Robin Axelsson User-Agent: Mozilla/5.0 (Windows NT 5.2; WOW64; rv:9.0) Gecko/20111222 Thunderbird/9.0.1 MIME-Version: 1.0 To: References: <505B86AE.9040507@earthlink.net> <505C8630.2090002@student.chalmers.se> <505FD74E.2050405@earthlink.net> In-Reply-To: <505FD74E.2050405@earthlink.net> X-Originating-IP: [217.208.204.161] X-OriginatorOrg: student.chalmers.se Subject: Re: [Xen-users] Recommendations for Virtulization Hardware X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list Reply-To: gu99roax@student.chalmers.se List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============3543537349546090796==" Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org --===============3543537349546090796== Content-Type: multipart/alternative; boundary="------------030707090408060307080801" --------------030707090408060307080801 Content-Type: text/plain; charset="windows-1252"; format=flowed Content-Transfer-Encoding: quoted-printable On 2012-09-24 05:45, ShadesOfGrey wrote: > Sorry for the late response, I've had a lot to digest. > > On 09/21/2012 11:22 AM, Robin Axelsson wrote: >> If you want to be able to use PCI and VGA passthrough you basically=20 >> need to make sure that your hardware supports either AMD-Vi (formerly=20 >> known as AMD-IOMMU) or Intel VT-d extensions. In the Intel case it=20 >> limits your choice of Motherboard (it must be supported in the BIOS)=20 >> and CPU. In the AMD case it limits only your choice of motherboard. A=20 >> good start is to check out one of these pages: >> >> http://wiki.xensource.com/xenwiki/VTdHowTo >> http://wiki.xen.org/wiki/VTd_HowTo >> >> A word of warning here is that parts of the documentation is somewhat=20 >> dated. You can also communicate with e.g. Gigabyte, Asus or ASRock=20 >> customer support and ask them if a particular motherboard supports=20 >> these extensions. Most motherboards also have downloadable user=20 >> manuals, if the BIOS settings in those pages shows options to=20 >> enable/disable VT-d or AMD-Vi/IOMMU extensions then you will be ok=20 >> with that motherboard. >> > The lack of current information about Xen (and KVM) online has been=20 > frustrating =97 especially finding the many proof of concept videos tha= t=20 > demonstrated possibilities but offered no real specifics. Looking for=20 > specifics, I sought information from gaming and enthusiast sites; I=20 > figured finding confirmation of VT-d and AMD-Vi support on such sites=20 > would be more likely. However, I found that wasn't often the case. I=20 > did determine that ASRock motherboards seem to be the most likely to=20 > support VT-d, ASUS least likely (unless equipped with an Intel=20 > 'sanctioned' VT-d chipset). I had narrowed my choices to two=20 > motherboards that appear to offer VT-d support and was intending to=20 > contact the manufacturer before purchase. Both choices are a bit=20 > pricey and I've been reconsidering whether I should look to other=20 > motherboards to reduce costs. Some motherboards support IOMMU even though it is not found in the user=20 manual or specified on the website. Your best bet is to ask customer=20 support. A guy posted here that he got it working on an Intel=20 motherboard that doesn't even have options for it in the BIOS, so it=20 seems that in some cases it is only up to the CPU. This is not the case=20 with AMD though as I stated before. I have bought a couple of Gigabyte=20 GA990FX-UD7 myself, they are stable and have a good layout. They have=20 support for IOMMU but I haven't tested it thoroughly enough to fully=20 confirm this although I don't believe there would be any problem. It surprises me that ASRock and ASUS are so different. ASRock is, or at=20 least used to be a subsidiary of ASUS so there shouldn't be that much=20 difference between them. >> The other thing is choice of GPU for VGA passthrough and it is=20 >> preferable that the GPU supports FLR or Function Level Reset as it is=20 >> called. Thing is that the hardware needs to be reset somehow as it is=20 >> passed through to the host. This is best done with FLR and nVidia is=20 >> known to supply firmware patches for some of their Geforce cards with=20 >> this support and it is said to be supported by default with their=20 >> Quadro cards. FLR is not the only way to reset a PCI device, a reset=20 >> could be trigged through the ACPI power management framework by=20 >> temporarily cutting power to the affected PCI slot. These reset=20 >> methods are called d3d0 and bus reset. The question however, is if=20 >> this works on PCI cards that use auxiliary power directly from the=20 >> PSU. There is a pdf document on the VMWare website=20 >> (http://www.vmware.com/files/pdf/techpaper/vsp_4_vmdirectpath_host.pdf= )=20 >> about this: >> >> ----------------------- >> Reset Method >> >> Possible values for the reset method include flr, d3d0, link, bridge,=20 >> or default. >> >> The default setting is described as follows. If a device supports=20 >> function level reset (FLR), ESX always uses FLR. If the device does=20 >> not support FLR, ESX next defaults to link reset and bus reset in=20 >> that order. Link reset and bus reset might prevent some devices from=20 >> being assigned to different virtual machines, or from being assigned=20 >> between the VMkernel and virtual machines. In the absence of FLR, it=20 >> is possible to use PCI Power Management capability (D3 to D0=20 >> transitions) to trigger a reset. Most of the Intel NICs and various=20 >> other HBAs support this mode. >> ----------------------- >> >> >> There are indications from people that d3d0 also work with PCI cards=20 >> that take power from auxiliary inputs. I suggest that you take a look=20 >> at the following youtube clip and read the comments there: >> >> http://www.youtube.com/watch?v=3DGtmwnx-k2qg >> >> So it seems that it works although it may be a bit more quirky. It=20 >> doesn't hurt to take that discussion (particularly about FLR support)=20 >> with nVidia and/or AMD. >> > This is precisely the kind of information I was looking for from the=20 > threads I started on Ars Technica. It's just unfortunate that FLR and=20 > D3 D0 support aren't often found in the tech specs of must expansion=20 > hardware. However, now that I know what to ask, I'll try contacting=20 > hardware manufacturers prior to purchasing any expansion hardware.=20 > Thank you! D3 and D0 are power states defined for devices in the ACPI specification=20 and can be used to control the supply voltage (Vcc) to PCI and PCIe=20 devices. You can find more information about it here for example: http://en.wikipedia.org/wiki/Advanced_Configuration_and_Power_Interface --------------- Device states The device states /D0/-/D3/ are device-dependent: * *D0* /Fully On/ is the operating state. * *D1* and *D2* are intermediate power-states whose definition varies by device. * *D3* /Off/ has the device powered off and unresponsive to its bus. --------------- So, either it works for a certain type of hardware or it doesn't and I=20 wouldn't expect a vendor to state this "support" in the specifications=20 since it isn't a "feature" in and of itself if you get me. But maybe=20 this will change and maybe FLR support will become more widespread. >> When it comes to virtualization, the technology has come very far,=20 >> but it is still lacking considerably when it comes to sharing GPUs=20 >> and also to some degree when it comes to sharing I/O devices=20 >> (especially when you intend to run many virtual machines on a single=20 >> system). The GPU today consists of three types of components; the=20 >> processing unit, graphics memory and the video output unit/adapter=20 >> and it is not clear as to how to share these components seamlessly=20 >> between the host and virtual machines with minimal overhead. Whereas=20 >> there are VT-x extensions that allows you to pretty seamlessly share=20 >> CPU cores between VMs and the host there are currently none for the=20 >> processing unit. It is also not clear how the hardware can assist=20 >> with sharing TV/monitor screen estate between machines with all 3D=20 >> effects such as Aqua for Win7 and the whatnot enabled for all=20 >> machines. Especially when considering the dynamics of plugging and=20 >> unplugging computer monitors to multiport/eyefinity graphics cards=20 >> and the ability to change screen resolution. Things are improving for=20 >> sure and a lot of research is likely going into this. I don't know=20 >> what's happening in the GPU frontline but I know that the next thing=20 >> with passthrough is the SR-IOV that allows PCI units to present=20 >> several virtual instances of oneself to several virtual machines.=20 >> It's a cool thing, I recommend further reading about this here: >> >> http://www.intel.com/content/www/us/en/pci-express/pci-sig-sr-iov-prim= er-sr-iov-technology-paper.html=20 >> >> http://blog.scottlowe.org/2009/12/02/what-is-sr-iov/ >> > That is fascinating. Extending virtualization to expansion hardware=20 > via SR-IOV, sure would make the kind of setup I'm attempting a lot=20 > easier. However, if I can replicate what I've seen in proof of concept=20 > videos (namely Casey DeLorme's), I think that will meet my needs for=20 > now. As it stands, I initially intend to reserve any discrete GPU(s)=20 > for Windows and rely on an integrated GPU for all other VMs using PV=20 > drivers (wherever possible). Afterward, I want to experiment with=20 > re-assigning the whatever discrete GPU(s) for GPGPU functions under a=20 > Linux VM whenever the GPU is not going to used for gaming (if at all=20 > possible). >> It is likely to take a few years before something useful will come=20 >> out of it. In the meanwhile, unless you want to use several GPUs=20 >> which might not be a bad thing as a lot of monitors these days have=20 >> several inputs, you can resort to using a remote desktop client to=20 >> integrate one machine with another. Virtualbox for example use RDP=20 >> through which you can interact with your virtual machine. In a=20 >> similar manner you can set up a VNC server on your Linux host and=20 >> establish a connection to it through your Windows VM. You will not=20 >> get full 3D functionality (such as Aqua) through the client although=20 >> there is a growing support for it through VirtualGL extensions that=20 >> are coming to VNC and perhaps the Spice protocol. But some clients=20 >> might even allow for seamless mode that lets you mix Linux and=20 >> Windows windows on the same desktop like this for example: >> >> http://i.techrepublic.com.com/blogs/seamless.png >> http://www.youtube.com/watch?v=3DeQr8iI0yZH4 >> >> >> Just keep in mind that this is still a little bit of uncharted=20 >> territory so there may be a few bumps on the way and it may not work=20 >> as smooth as you would desire. >> >> > From everything I've read, solutions that rely on any form of remote=20 > display protocols would be limited to a subset of Direct3D functions.=20 > Furthermore, these would vary from one implementation to another, thus=20 > making them far less attractive for gaming than VGA passthrough...=20 > Well, in my opinion anyway. > > VirtualBox's seamless mode is pretty nifty. But it's a Type 2=20 > Hypervisor and relies on paravirtualized drivers that also suffer from=20 > the same limitations as remote display protocols. It's great for most=20 > things, but gaming is not one of them. And I'm speaking from personal=20 > experience. Though I haven't used them myself, the same would seem to=20 > hold true of Parallel's and VMWare's 'Workstation' offerings. At=20 > least, as far as I've gathered. > > FYI, the Type 1 Hypervisors from Parallel's and VMWare* are priced=20 > waaayyy outside my budget. > I understand that you want full 3D functionality for Windows gaming but=20 maybe you'll find the subset of 3D functionality for the Linux machine=20 acceptable. I have looked into VirtualGL and with TurboVNC, you might=20 get a pretty decent desktop environment and it seems like most of the=20 features are there already. It appears that the 3D is rendered by=20 hardware/GPU before it is streamed through VNC or Spice. So it seems=20 that you would need another GPU for that. You can find more info on=20 VirtualGL here: http://www.virtualgl.org/ Also the line between a type 1 and type 2 hypervisor tend to get a bit=20 blurry. The point with type 1 is that it has access to ring-0 so that it=20 can get access directly to the hardware to be passed through to the=20 guests (I did confuse 'host' and 'guest' in my prior post). It also=20 doesn't need to ask the host OS for permission in the same way as a type=20 2 hypervisor which is likely to give performance advantages in some cases= . However, even a type 2 hypervisor, although it is run as an application=20 inside the OS can get "type 1" like privileges. By patching into the=20 kernel and/or using special "dummy drivers" for hardware to be shared=20 with VMs you can achieve pretty much the same thing, ergo it is no=20 longer clear whether the hypervisor is a type 1 or type 2. There is an article about it from the old IBM Mainframe days but I can't=20 seem to find it. > > *I only found out about VMWare's 'free' vSphere after I'd written this=20 > response. >> >> I see that your demands are somewhat multifaceted. I believe that you=20 >> also want to use diffent services such as using your machine as a=20 >> file server with the possible intention of using filesystems such as=20 >> ZFS. If you do, you should be careful with your selection of hardware=20 >> for these particular purposes. If you want to get full protection=20 >> against data corruption from ZFS, your choice of hardware gets rather=20 >> limited when it comes to choice of hard drives, host bus adapter and=20 >> network controller. The most stable implementation of ZFS is found=20 >> with Illumos based operating systems (such as OpenIndiana, SmartOS,=20 >> OmniOS, Belenix etc) or Solaris if you choose to download it from=20 >> Oracle's website. With these operating systems you are most likely to=20 >> want to use hardware that has certified drivers for it. That way you=20 >> are less likely to run into problems later on. That implies that you=20 >> will be limited to choosing Intel based network adapters and LSI=20 >> based SAS controllers. There should be _no_ hardware RAID=20 >> functionality in the SAS controller that merely should be run in IT=20 >> mode (or Initiator-Target mode). That requires the LSI controller to=20 >> be flashed with IT firmware in most cases. The objective here is to=20 >> make sure that _all_ errors that might occur with the hard drives are=20 >> reported all the way to the software level and that nothing is=20 >> concealed of obfuscated by internal error handling in the hardware.=20 >> It is therefore recommended to use SAS hard drives instead of S-ATA=20 >> (which also are fully compatible with SAS controllers). SAS hard=20 >> drives are not much more expensive than similar SATA drives and you=20 >> get a higher reliability out of them. It is also recommended to have=20 >> at least two drive redundancy simply because if one drive is dead and=20 >> you swap it, it is not uncommon that another drive dies in the=20 >> rebuild process of the RAID cluster because of the added strain the=20 >> rebuild process (or 'resilvering' as it is called in Solaris terms)=20 >> put on the drives. Of course, the system should communicate directly=20 >> to the hard drive hardware and not be obfuscated by some virtual=20 >> abstraction layer in between which means that you either run ZFS on=20 >> the metal or through PCI passthrough of the SAS (and perhaps also=20 >> network) adapters. Also, it is highly recommended that you use ECC=20 >> RAM for such applications and it doesn't hurt to dedicate a few gigs=20 >> of it to the ZFS as RAM is used for cache. The good news is that most=20 >> motherboards with good chipsets support ECC RAM even though you might=20 >> not find anything about it in the user manuals. > Again, thanks for the thorough explanation. This gives me a great deal=20 > to think about. The more I learn about ZFS, the less appealing it=20 > becomes. And by that I mean the confusion over which version of ZFS is=20 > in what OS? And just how well maintained the OSes supporting ZFS are?=20 > Now I have additional hardware considerations to keep in mind that may=20 > (or may not) make the cost of ZFS RAID-Z pool comparable to a hardware=20 > RAID5/6 solution anyway. Do you have any suggestions as to which of=20 > LSI HBAs I should be considering? I haven't found an HCL for ZFS in my=20 > searches. > > Out of curiosity =97 and if you would happen to know =97 do you think w= hat=20 > you suggest about the HBA and SAS drives for ZFS also applies to=20 > Btrfs? I'm assuming it would, but I'd appreciate some confirmation. > > It's funny how the "I" in RAID never really seems to apply...=20 > Especially since it looks more and more like using ZFS or Btrfs will=20 > require I commit myself, from the start, to one or the other and a=20 > discrete HBA. Transitioning from an integrated SATA controller(s) and=20 > mdadm seems rather impractical. If I understand what's involved in=20 > doing so correctly. It may turn out that anything other than mdadm is=20 > price prohibitive. > I don't think you will have a problem with getting ZFS to run and if=20 that's your only goal then you don't need to be very picky with your=20 choice of hardware. I find ZFS pretty easy and handy to use. I has=20 really great functionality and I don't have many bad things to say about=20 it so far. ZFS is a filesystem (along with a couple of software tools to=20 administrate it) just like EXT4 or NTFS so hardware support depends on=20 the platform it runs on. But the point with using ZFS is to get maximum protection against data=20 corruption and that's where the selection of hardware gets limited and=20 there are "best practices" set up to achieve that. I have not tested ZFS=20 on any other platform than on OpenSolaris and OpenIndiana but I do know=20 that it is well implemented on that platform and more mature there than=20 on any other (non-solaris) platform. Another advantage with the OSOL/OI=20 platform is that the CIFS functionality is implemented in the kernel=20 space and not in the userland which will give advantages performance=20 wise if you intend to share files with other windows computers. (I don't=20 deny that Samba is pretty good on Linux too. There are some benchmarks=20 on the phoronix website comparing samba with NFS and they are in favor=20 of Samba on those benchmarks...) The second best implementation is found=20 with FreeBSD and it is probably fairly mature but I haven't tested it=20 myself and some people have run into problems with it in the past. The=20 Linux version is probably merely at infancy stage and likely not yet=20 mature enough for regular use. It is probably not as "bad" as btrfs=20 though. There is quite a bit of information about it on the phoronix.com=20 website (and probably also at lwn.net): http://www.phoronix.com/scan.php?page=3Dnews_item&px=3DMTE4Nzc A search there on ZFS will give more articles. The latest official=20 version of ZFS is 28 and is probably implemented in both Linux, and=20 FreeBSD by now. Later versions have been released since Oracle killed=20 the OpenSolaris project and can be found with the commercial=20 closed-source Solaris platform that is supplied by Oracle. Things have=20 happened since Oracle pulled the plug on OSOL project and leading=20 developers behind the ZFS project such as Jeff Bonwick left Sun (after=20 the acquisition by Oracle) and joined up with the Illumos team instead.=20 So you cannot determine the stability of ZFS and ZPOOL merely by looking=20 into the version number unfortunately and I wouldn't expect the FreeBSD=20 implementation to be as stable as the Solaris implementation. It just=20 takes time for the implementation to mature and the bugs to be weeded=20 out and it just happens to have been around for=20 Solaris/OpenSolaris/Illumos for much longer than the other platforms and=20 the Solaris/Illumos version also happens to get first dibs on the=20 features. Among the Illumos people there is an ambition to drop the=20 version numbering altogether and instead talk about available features. The recommendation to use SAS hard drives is not so much about the=20 quality of the hard drives themselves as it is about the SAS protocol.=20 The SAS protocol simply handles SCSI transport commands in a better and=20 more reliable manner than do SATA. I believe any decent SAS drive would=20 do. As for HBAs I wrote a list with LSI based hardware a while ago here: https://www.illumos.org/boards/1/topics/572 the thing is that a lot of OEMs such as IBM, HP, Cisco, Fujitsu-Siemens,=20 Dell, ... supply their branded HBAs with LSI circuitry on them. What=20 hardware to choose depends on what you're looking for. If you want an=20 8-port controller I would go for Intel SASUC8I or LSI SAS3801E-R. If you=20 want SAS/SATA3 with 6.0 Gb/s then LSI's SAS 9200 series cards would be a=20 better choice. I don't know what OEMs have come up with in the SATA3=20 department since I wrote that list but the chips to look for in that=20 case are the LSI MegaRAID 2004/2008/2016e depending on how many ports=20 you want. If you want to read a further discussion about reliability of different=20 RAID setups I made a post about this in the following thread (last post): http://communities.intel.com/thread/25945 >> I admire your persistence with pursuing this undertaking and wish you=20 >> the best of luck with it! >> Robin. >> >> > Thanks. I've invested too much time in research to not at least make=20 > the attempt. Besides, if all else fails, I can fallback to a two box=20 > solution. That is, if I can get my hypothetical virtualization box to=20 > fit in my budget envelope... > > > _______________________________________________ > Xen-users mailing list > Xen-users@lists.xen.org > http://lists.xen.org/xen-users > > . > --------------030707090408060307080801 Content-Type: text/html; charset="windows-1252" Content-Transfer-Encoding: quoted-printable On 2012-09-24 05:45, ShadesOfGrey wrote:
Sorry for the late response, I've had a lot to digest.

On 09/21/2012 11:22 AM, Robin Axelsson wrote:
If you want to be able to use PCI and VGA passthrough you basically need to make sure that your hardware supports either AMD-Vi (formerly known as AMD-IOMMU) or Intel VT-d extensions. In the Intel case it limits your choice of Motherboard (it must be supported in the BIOS) and CPU. In the AMD case it limits only your choice of motherboard. A good start is to check out one of these pages:

http://wiki.xensource.com/xenwiki/VTdHowTo
http://wiki.xen.org/wiki/VTd_HowTo

A word of warning here is that parts of the documentation is somewhat dated. You can also communicate with e.g. Gigabyte, Asus or ASRock customer support and ask them if a particular motherboard supports these extensions. Most motherboards also have downloadable user manuals, if the BIOS settings in those pages shows options to enable/disable VT-d or AMD-Vi/IOMMU extensions then you will be ok with that motherboard.

The lack of current information about Xen (and KVM) online has been frustrating =97 especially finding the many proof of concept videos that demonstrated possibilities but offered no real specifics. Looking for specifics, I sought information from gaming and enthusiast sites; I figured finding confirmation of VT-d and AMD-Vi support on such sites would be more likely. However, I found that wasn't often the case. I did determine that ASRock motherboards seem to be the most likely to support VT-d, ASUS least likely (unless equipped with an Intel 'sanctioned' VT-d chipset). I had narrowed my choices to two motherboards that appear to offer VT-d support and was intending to contact the manufacturer before purchase. Both choices are a bit pricey and I've been reconsidering whether I should look to other motherboards to reduce costs.

Some motherboards support IOMMU even though it is not found in the user manual or specified on the website. Your best bet is to ask customer support. A guy posted here that he got it working on an Intel motherboard that doesn't even have options for it in the BIOS, so it seems that in some cases it is only up to the CPU. This is not the case with AMD though as I stated before. I have bought a couple of Gigabyte GA990FX-UD7 myself, they are stable and have a good layout. They have support for IOMMU but I haven't tested it thoroughly enough to fully confirm this although I don't believe there would be any problem.

It surprises me that ASRock and ASUS are so different. ASRock is, or at least used to be a subsidiary of ASUS so there shouldn't be that much difference between them.
The other thing is choice of GPU for VGA passthrough and it is preferable that the GPU supports FLR or Function Level Reset as it is called. Thing is that the hardware needs to be reset somehow as it is passed through to the host. This is best done with FLR and nVidia is known to supply firmware patches for some of their Geforce cards with this support and it is said to be supported by default with their Quadro cards. FLR is not the only way to reset a PCI device, a reset could be trigged through the ACPI power management framework by temporarily cutting power to the affected PCI slot. These reset methods are called d3d0 and bus reset. The question however, is if this works on PCI cards that use auxiliary power directly from the PSU. There is a pdf document on the VMWare website (http://www.vmware.com/f= iles/pdf/techpaper/vsp_4_vmdirectpath_host.pdf) about this:

-----------------------
Reset Method

Possible values for the reset method include flr, d3d0, link, bridge, or default.

The default setting is described as follows. If a device supports function level reset (FLR), ESX always uses FLR. If the device does not support FLR, ESX next defaults to link reset and bus reset in that order. Link reset and bus reset might prevent some devices from being assigned to different virtual machines, or from being assigned between the VMkernel and virtual machines. In the absence of FLR, it is possible to use PCI Power Management capability (D3 to D0 transitions) to trigger a reset. Most of the Intel NICs and various other HBAs support this mode.
-----------------------


There are indications from people that d3d0 also work with PCI cards that take power from auxiliary inputs. I suggest that you take a look at the following youtube clip and read the comments there:

http://www.youtube.com/watch?v=3DGtmwnx-k2qg

So it seems that it works although it may be a bit more quirky. It doesn't hurt to take that discussion (particularly about FLR support) with nVidia and/or AMD.

This is precisely the kind of information I was looking for from the threads I started on Ars Technica. It's just unfortunate that FLR and D3 D0 support aren't often found in the tech specs of must expansion hardware. However, now that I know what to ask, I'll try contacting hardware manufacturers prior to purchasing any expansion hardware. Thank you!

D3 and D0 are power states defined for devices in the ACPI specification and can be used to control the supply voltage (Vcc) to PCI and PCIe devices. You can find more information about it here for example:

http://en.wikipedia.org/wiki/A= dvanced_Configuration_and_Power_Interface

---------------

Device states

The device states D0-D3 are device-dependent:

  • D0 Fully On is the operating state.
  • D1 and D2 are intermediate power-states whose definition varies by device.
  • D3 Off has the device powered off and unresponsive to its bus.
---------------

So, either it works for a certain type of hardware or it doesn't and I wouldn't expect a vendor to state this "support" in the specifications since it isn't a "feature" in and of itself if you get me. But maybe this will change and maybe FLR support will become more widespread.

When it comes to virtualization, the technology has come very far, but it is still lacking considerably when it comes to sharing GPUs and also to some degree when it comes to sharing I/O devices (especially when you intend to run many virtual machines on a single system). The GPU today consists of three types of components; the processing unit, graphics memory and the video output unit/adapter and it is not clear as to how to share these components seamlessly between the host and virtual machines with minimal overhead. Whereas there are VT-x extensions that allows you to pretty seamlessly share CPU cores between VMs and the host there are currently none for the processing unit. It is also not clear how the hardware can assist with sharing TV/monitor screen estate between machines with all 3D effects such as Aqua for Win7 and the whatnot enabled for all machines. Especially when considering the dynamics of plugging and unplugging computer monitors to multiport/eyefinity graphics cards and the ability to change screen resolution. Things are improving for sure and a lot of research is likely going into this. I don't know what's happening in the GPU frontline but I know that the next thing with passthrough is the SR-IOV that allows PCI units to present several virtual instances of oneself to several virtual machines. It's a cool thing, I recommend further reading about this here:

http://www.intel.com/content/www/us/en/pci-express/pci-sig-sr-iov= -primer-sr-iov-technology-paper.html
http://blog.scottlowe.org/2009/12/02/what= -is-sr-iov/

That is fascinating. Extending virtualization to expansion hardware via SR-IOV, sure would make the kind of setup I'm attempting a lot easier. However, if I can replicate what I've seen in proof of concept videos (namely Casey DeLorme's), I think that will meet my needs for now. As it stands, I initially intend to reserve any discrete GPU(s) for Windows and rely on an integrated GPU for all other VMs using PV drivers (wherever possible). Afterward, I want to experiment with re-assigning the whatever discrete GPU(s) for GPGPU functions under a Linux VM whenever the GPU is not going to used for gaming (if at all possible).
It is likely to take a few years before something useful will come out of it. In the meanwhile, unless you want to use several GPUs which might not be a bad thing as a lot of monitors these days have several inputs, you can resort to using a remote desktop client to integrate one machine with another. Virtualbox for example use RDP through which you can interact with your virtual machine. In a similar manner you can set up a VNC server on your Linux host and establish a connection to it through your Windows VM. You will not get full 3D functionality (such as Aqua) through the client although there is a growing support for it through VirtualGL extensions that are coming to VNC and perhaps the Spice protocol. But some clients might even allow for seamless mode that lets you mix Linux and Windows windows on the same desktop like this for example:

http://i.techrepublic.com.com/blogs/seamless.= png
http://www.youtube.com/watch?v=3DeQr8iI0yZH4


Just keep in mind that this is still a little bit of uncharted territory so there may be a few bumps on the way and it may not work as smooth as you would desire.


From everything I've read, solutions that rely on any form of remote display protocols would be limited to a subset of Direct3D functions. Furthermore, these would vary from one implementation to another, thus making them far less attractive for gaming than VGA passthrough... Well, in my opinion anyway.

VirtualBox's seamless mode is pretty nifty. But it's a Type 2 Hypervisor and relies on paravirtualized drivers that also suffer from the same limitations as remote display protocols. It's great for most things, but gaming is not one of them. And I'm speaking from personal experience. Though I haven't used them myself, the same would seem to hold true of Parallel's and VMWare's 'Workstation' offerings. At least, as far as I've gathered.

FYI, the Type 1 Hypervisors from Parallel's and VMWare* are priced waaayyy outside my budget.

I understand that you want full 3D functionality for Windows gaming but maybe you'll find the subset of 3D functionality for the Linux machine acceptable. I have looked into VirtualGL and with TurboVNC, you might get a pretty decent desktop environment and it seems like most of the features are there already. It appears that the 3D is rendered by hardware/GPU before it is streamed through VNC or Spice. So it seems that you would need another GPU for that. You can find more info on VirtualGL here:

http://www.virtualgl.org/

Also the line between a type 1 and type 2 hypervisor tend to get a bit blurry. The point with type 1 is that it has access to ring-0 so that it can get access directly to the hardware to be passed through to the guests (I did confuse 'host' and 'guest' in my prior post). It also doesn't need to ask the host OS for permission in the same way as a type 2 hypervisor which is likely to give performance advantages in some cases.

However, even a type 2 hypervisor, although it is run as an application inside the OS can get "type 1" like privileges. By patching into the kernel and/or using special "dummy drivers" for hardware to be shared with VMs you can achieve pretty much the same thing, ergo it is no longer clear whether the hypervisor is a type 1 or type 2.

There is an article about it from the old IBM Mainframe days but I can't seem to find it.


*I only found out about VMWare's 'free' vSphere after I'd written this response.

I see that your demands are somewhat multifaceted. I believe that you also want to use diffent services such as using your machine as a file server with the possible intention of using filesystems such as ZFS. If you do, you should be careful with your selection of hardware for these particular purposes. If you want to get full protection against data corruption from ZFS, your choice of hardware gets rather limited when it comes to choice of hard drives, host bus adapter and network controller. The most stable implementation of ZFS is found with Illumos based operating systems (such as OpenIndiana, SmartOS, OmniOS, Belenix etc) or Solaris if you choose to download it from Oracle's website. With these operating systems you are most likely to want to use hardware that has certified drivers for it. That way you are less likely to run into problems later on. That implies that you will be limited to choosing Intel based network adapters and LSI based SAS controllers. There should be _no_ hardware RAID functionality in the SAS controller that merely should be run in IT mode (or Initiator-Target mode). That requires the LSI controller to be flashed with IT firmware in most cases. The objective here is to make sure that _all_ errors that might occur with the hard drives are reported all the way to the software level and that nothing is concealed of obfuscated by internal error handling in the hardware. It is therefore recommended to use SAS hard drives instead of S-ATA (which also are fully compatible with SAS controllers). SAS hard drives are not much more expensive than similar SATA drives and you get a higher reliability out of them. It is also recommended to have at least two drive redundancy simply because if one drive is dead and you swap it, it is not uncommon that another drive dies in the rebuild process of the RAID cluster because of the added strain the rebuild process (or 'resilvering' as it is called in Solaris terms) put on the drives. Of course, the system should communicate directly to the hard drive hardware and not be obfuscated by some virtual abstraction layer in between which means that you either run ZFS on the metal or through PCI passthrough of the SAS (and perhaps also network) adapters. Also, it is highly recommended that you use ECC RAM for such applications and it doesn't hurt to dedicate a few gigs of it to the ZFS as RAM is used for cache. The good news is that most motherboards with good chipsets support ECC RAM even though you might not find anything about it in the user manuals.
Again, thanks for the thorough explanation. This gives me a great deal to think about. The more I learn about ZFS, the less appealing it becomes. And by that I mean the confusion over which version of ZFS is in what OS? And just how well maintained the OSes supporting ZFS are? Now I have additional hardware considerations to keep in mind that may (or may not) make the cost of ZFS RAID-Z pool comparable to a hardware RAID5/6 solution anyway. Do you have any suggestions as to which of LSI HBAs I should be considering? I haven't found an HCL for ZFS in my searches.

Out of curiosity =97 and if you would happen to know =97 do you thi= nk what you suggest about the HBA and SAS drives for ZFS also applies to Btrfs? I'm assuming it would, but I'd appreciate some confirmation.

It's funny how the "I" in RAID never really seems to apply... Especially since it looks more and more like using ZFS or Btrfs will require I commit myself, from the start, to one or the other and a discrete HBA. Transitioning from an integrated SATA controller(s) and mdadm seems rather impractical. If I understand what's involved in doing so correctly. It may turn out that anything other than mdadm is price prohibitive.


I don't think you will have a problem with getting ZFS to run and if that's your only goal then you don't need to be very picky with your choice of hardware. I find ZFS pretty easy and handy to use. I has really great functionality and I don't have many bad things to say about it so far. ZFS is a filesystem (along with a couple of software tools to administrate it) just like EXT4 or NTFS so hardware support depends on the platform it runs on.

But the point with using ZFS is to get maximum protection against data corruption and that's where the selection of hardware gets limited and there are "best practices" set up to achieve that. I have not tested ZFS on any other platform than on OpenSolaris and OpenIndiana but I do know that it is well implemented on that platform and more mature there than on any other (non-solaris) platform. Another advantage with the OSOL/OI platform is that the CIFS functionality is implemented in the kernel space and not in the userland which will give advantages performance wise if you intend to share files with other windows computers. (I don't deny that Samba is pretty good on Linux too. There are some benchmarks on the phoronix website comparing samba with NFS and they are in favor of Samba on those benchmarks...) The second best implementation is found with FreeBSD and it is probably fairly mature but I haven't tested it myself and some people have run into problems with it in the past. The Linux version is probably merely at infancy stage and likely not yet mature enough for regular use. It is probably not as "bad" as btrfs though. There is quite a bit of information about it on the phoronix.com website (and probably also at lwn.net):

http://www.phoronix.com/scan.ph= p?page=3Dnews_item&px=3DMTE4Nzc

A search there on ZFS will give more articles. The latest official version of ZFS is 28 and is probably implemented in both Linux, and FreeBSD by now. Later versions have been released since Oracle killed the OpenSolaris project and can be found with the commercial closed-source Solaris platform that is supplied by Oracle. Things have happened since Oracle pulled the plug on OSOL project and leading developers behind the ZFS project such as Jeff Bonwick left Sun (after the acquisition by Oracle) and joined up with the Illumos team instead. So you cannot determine the stability of ZFS and ZPOOL merely by looking into the version number unfortunately and I wouldn't expect the FreeBSD implementation to be as stable as the Solaris implementation. It just takes time for the implementation to mature and the bugs to be weeded out and it just happens to have been around for Solaris/OpenSolaris/Illumos for much longer than the other platforms and the Solaris/Illumos version also happens to get first dibs on the features. Among the Illumos people there is an ambition to drop the version numbering altogether and instead talk about available features.

The recommendation to use SAS hard drives is not so much about the quality of the hard drives themselves as it is about the SAS protocol. The SAS protocol simply handles SCSI transport commands in a better and more reliable manner than do SATA. I believe any decent SAS drive would do. As for HBAs I wrote a list with LSI based hardware a while ago here:

https://www.illumos.org/boards/1/topics/572

the thing is that a lot of OEMs such as IBM, HP, Cisco, Fujitsu-Siemens, Dell, ... supply their branded HBAs with LSI circuitry on them. What hardware to choose depends on what you're looking for. If you want an 8-port controller I would go for Intel SASUC8I or LSI SAS3801E-R. If you want SAS/SATA3 with 6.0 Gb/s then LSI's SAS 9200 series cards would be a better choice. I don't know what OEMs have come up with in the SATA3 department since I wrote that list but the chips to look for in that case are the LSI MegaRAID 2004/2008/2016e depending on how many ports you want.

If you want to read a further discussion about reliability of different RAID setups I made a post about this in the following thread (last post):

http://communities.intel.com/thread/25945


I admire your persistence with pursuing this undertaking and wish you the best of luck with it!
Robin.


Thanks. I've invested too much time in research to not at least make the attempt. Besides, if all else fails, I can fallback to a two box solution. That is, if I can get my hypothetical virtualization box to fit in my budget envelope...


_______________________________________________
Xen-users mailing list
Xen-users@lists.xen.org
http://lists.xen.org/xen-users

.


--------------030707090408060307080801-- --===============3543537349546090796== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users --===============3543537349546090796==-- From xen-users-bounces@lists.xen.org Mon Sep 24 12:50:15 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Mon, 24 Sep 2012 12:50:15 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TG86D-0008WF-VP; Mon, 24 Sep 2012 12:49:21 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TG86B-0008WA-JR for xen-users@lists.xen.org; Mon, 24 Sep 2012 12:49:20 +0000 Received: from [85.158.143.35:44408] by server-3.bemta-4.messagelabs.com id D4/17-10986-EC650605; Mon, 24 Sep 2012 12:49:18 +0000 X-Env-Sender: gu99roax@student.chalmers.se X-Msg-Ref: server-4.tower-21.messagelabs.com!1348490953!7872482!1 X-Originating-IP: [216.32.181.183] X-SpamReason: No, hits=1.4 required=7.0 tests=BODY_RANDOM_LONG, HTML_20_30,HTML_MESSAGE X-StarScan-Received: X-StarScan-Version: 6.6.1.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 27746 invoked from network); 24 Sep 2012 12:49:14 -0000 Received: from ch1ehsobe003.messaging.microsoft.com (HELO ch1outboundpool.messaging.microsoft.com) (216.32.181.183) by server-4.tower-21.messagelabs.com with AES128-SHA encrypted SMTP; 24 Sep 2012 12:49:14 -0000 Received: from mail75-ch1-R.bigfish.com (10.43.68.240) by CH1EHSOBE005.bigfish.com (10.43.70.55) with Microsoft SMTP Server id 14.1.225.23; Mon, 24 Sep 2012 12:49:12 +0000 Received: from mail75-ch1 (localhost [127.0.0.1]) by mail75-ch1-R.bigfish.com (Postfix) with ESMTP id EA212180278 for ; Mon, 24 Sep 2012 12:49:12 +0000 (UTC) X-Forefront-Antispam-Report: CIP:207.46.4.203; KIP:(null); UIP:(null); IPV:NLI; H:SN2PRD0102HT013.prod.exchangelabs.com; RD:none; EFVD:NLI X-SpamScore: -16 X-BigFish: PS-16(zzbb2dI98dI9371I1503M936eIc85eh1b0bI1432I1418I2176M1447Id6f1izz1d18h1202h1d1ah1d2ah1082kzz8275ch17326ah8275bh8275dh172cdfh5eeeKc704dhz2dh2a8h668h839h8e2h8e3hd25hf0ah107ah10d2h1288h12a5h12bdh137ahbe9i1155h) Received: from mail75-ch1 (localhost.localdomain [127.0.0.1]) by mail75-ch1 (MessageSwitch) id 1348490949561117_32047; Mon, 24 Sep 2012 12:49:09 +0000 (UTC) Received: from CH1EHSMHS031.bigfish.com (snatpool2.int.messaging.microsoft.com [10.43.68.236]) by mail75-ch1.bigfish.com (Postfix) with ESMTP id 7D9B416017C for ; Mon, 24 Sep 2012 12:49:09 +0000 (UTC) Received: from SN2PRD0102HT013.prod.exchangelabs.com (207.46.4.203) by CH1EHSMHS031.bigfish.com (10.43.70.31) with Microsoft SMTP Server (TLS) id 14.1.225.23; Mon, 24 Sep 2012 12:49:07 +0000 Received: from [10.40.137.93] (217.208.204.161) by pod51000.outlook.com (10.27.50.107) with Microsoft SMTP Server (TLS) id 14.15.108.4; Mon, 24 Sep 2012 12:49:05 +0000 Message-ID: <506056BC.3010705@student.chalmers.se> Date: Mon, 24 Sep 2012 14:49:00 +0200 From: Robin Axelsson User-Agent: Mozilla/5.0 (Windows NT 5.2; WOW64; rv:9.0) Gecko/20111222 Thunderbird/9.0.1 MIME-Version: 1.0 To: References: <505B86AE.9040507@earthlink.net> <505C8630.2090002@student.chalmers.se> <505FD74E.2050405@earthlink.net> In-Reply-To: <505FD74E.2050405@earthlink.net> X-Originating-IP: [217.208.204.161] X-OriginatorOrg: student.chalmers.se Subject: Re: [Xen-users] Recommendations for Virtulization Hardware X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list Reply-To: gu99roax@student.chalmers.se List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============3543537349546090796==" Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org --===============3543537349546090796== Content-Type: multipart/alternative; boundary="------------030707090408060307080801" --------------030707090408060307080801 Content-Type: text/plain; charset="windows-1252"; format=flowed Content-Transfer-Encoding: quoted-printable On 2012-09-24 05:45, ShadesOfGrey wrote: > Sorry for the late response, I've had a lot to digest. > > On 09/21/2012 11:22 AM, Robin Axelsson wrote: >> If you want to be able to use PCI and VGA passthrough you basically=20 >> need to make sure that your hardware supports either AMD-Vi (formerly=20 >> known as AMD-IOMMU) or Intel VT-d extensions. In the Intel case it=20 >> limits your choice of Motherboard (it must be supported in the BIOS)=20 >> and CPU. In the AMD case it limits only your choice of motherboard. A=20 >> good start is to check out one of these pages: >> >> http://wiki.xensource.com/xenwiki/VTdHowTo >> http://wiki.xen.org/wiki/VTd_HowTo >> >> A word of warning here is that parts of the documentation is somewhat=20 >> dated. You can also communicate with e.g. Gigabyte, Asus or ASRock=20 >> customer support and ask them if a particular motherboard supports=20 >> these extensions. Most motherboards also have downloadable user=20 >> manuals, if the BIOS settings in those pages shows options to=20 >> enable/disable VT-d or AMD-Vi/IOMMU extensions then you will be ok=20 >> with that motherboard. >> > The lack of current information about Xen (and KVM) online has been=20 > frustrating =97 especially finding the many proof of concept videos tha= t=20 > demonstrated possibilities but offered no real specifics. Looking for=20 > specifics, I sought information from gaming and enthusiast sites; I=20 > figured finding confirmation of VT-d and AMD-Vi support on such sites=20 > would be more likely. However, I found that wasn't often the case. I=20 > did determine that ASRock motherboards seem to be the most likely to=20 > support VT-d, ASUS least likely (unless equipped with an Intel=20 > 'sanctioned' VT-d chipset). I had narrowed my choices to two=20 > motherboards that appear to offer VT-d support and was intending to=20 > contact the manufacturer before purchase. Both choices are a bit=20 > pricey and I've been reconsidering whether I should look to other=20 > motherboards to reduce costs. Some motherboards support IOMMU even though it is not found in the user=20 manual or specified on the website. Your best bet is to ask customer=20 support. A guy posted here that he got it working on an Intel=20 motherboard that doesn't even have options for it in the BIOS, so it=20 seems that in some cases it is only up to the CPU. This is not the case=20 with AMD though as I stated before. I have bought a couple of Gigabyte=20 GA990FX-UD7 myself, they are stable and have a good layout. They have=20 support for IOMMU but I haven't tested it thoroughly enough to fully=20 confirm this although I don't believe there would be any problem. It surprises me that ASRock and ASUS are so different. ASRock is, or at=20 least used to be a subsidiary of ASUS so there shouldn't be that much=20 difference between them. >> The other thing is choice of GPU for VGA passthrough and it is=20 >> preferable that the GPU supports FLR or Function Level Reset as it is=20 >> called. Thing is that the hardware needs to be reset somehow as it is=20 >> passed through to the host. This is best done with FLR and nVidia is=20 >> known to supply firmware patches for some of their Geforce cards with=20 >> this support and it is said to be supported by default with their=20 >> Quadro cards. FLR is not the only way to reset a PCI device, a reset=20 >> could be trigged through the ACPI power management framework by=20 >> temporarily cutting power to the affected PCI slot. These reset=20 >> methods are called d3d0 and bus reset. The question however, is if=20 >> this works on PCI cards that use auxiliary power directly from the=20 >> PSU. There is a pdf document on the VMWare website=20 >> (http://www.vmware.com/files/pdf/techpaper/vsp_4_vmdirectpath_host.pdf= )=20 >> about this: >> >> ----------------------- >> Reset Method >> >> Possible values for the reset method include flr, d3d0, link, bridge,=20 >> or default. >> >> The default setting is described as follows. If a device supports=20 >> function level reset (FLR), ESX always uses FLR. If the device does=20 >> not support FLR, ESX next defaults to link reset and bus reset in=20 >> that order. Link reset and bus reset might prevent some devices from=20 >> being assigned to different virtual machines, or from being assigned=20 >> between the VMkernel and virtual machines. In the absence of FLR, it=20 >> is possible to use PCI Power Management capability (D3 to D0=20 >> transitions) to trigger a reset. Most of the Intel NICs and various=20 >> other HBAs support this mode. >> ----------------------- >> >> >> There are indications from people that d3d0 also work with PCI cards=20 >> that take power from auxiliary inputs. I suggest that you take a look=20 >> at the following youtube clip and read the comments there: >> >> http://www.youtube.com/watch?v=3DGtmwnx-k2qg >> >> So it seems that it works although it may be a bit more quirky. It=20 >> doesn't hurt to take that discussion (particularly about FLR support)=20 >> with nVidia and/or AMD. >> > This is precisely the kind of information I was looking for from the=20 > threads I started on Ars Technica. It's just unfortunate that FLR and=20 > D3 D0 support aren't often found in the tech specs of must expansion=20 > hardware. However, now that I know what to ask, I'll try contacting=20 > hardware manufacturers prior to purchasing any expansion hardware.=20 > Thank you! D3 and D0 are power states defined for devices in the ACPI specification=20 and can be used to control the supply voltage (Vcc) to PCI and PCIe=20 devices. You can find more information about it here for example: http://en.wikipedia.org/wiki/Advanced_Configuration_and_Power_Interface --------------- Device states The device states /D0/-/D3/ are device-dependent: * *D0* /Fully On/ is the operating state. * *D1* and *D2* are intermediate power-states whose definition varies by device. * *D3* /Off/ has the device powered off and unresponsive to its bus. --------------- So, either it works for a certain type of hardware or it doesn't and I=20 wouldn't expect a vendor to state this "support" in the specifications=20 since it isn't a "feature" in and of itself if you get me. But maybe=20 this will change and maybe FLR support will become more widespread. >> When it comes to virtualization, the technology has come very far,=20 >> but it is still lacking considerably when it comes to sharing GPUs=20 >> and also to some degree when it comes to sharing I/O devices=20 >> (especially when you intend to run many virtual machines on a single=20 >> system). The GPU today consists of three types of components; the=20 >> processing unit, graphics memory and the video output unit/adapter=20 >> and it is not clear as to how to share these components seamlessly=20 >> between the host and virtual machines with minimal overhead. Whereas=20 >> there are VT-x extensions that allows you to pretty seamlessly share=20 >> CPU cores between VMs and the host there are currently none for the=20 >> processing unit. It is also not clear how the hardware can assist=20 >> with sharing TV/monitor screen estate between machines with all 3D=20 >> effects such as Aqua for Win7 and the whatnot enabled for all=20 >> machines. Especially when considering the dynamics of plugging and=20 >> unplugging computer monitors to multiport/eyefinity graphics cards=20 >> and the ability to change screen resolution. Things are improving for=20 >> sure and a lot of research is likely going into this. I don't know=20 >> what's happening in the GPU frontline but I know that the next thing=20 >> with passthrough is the SR-IOV that allows PCI units to present=20 >> several virtual instances of oneself to several virtual machines.=20 >> It's a cool thing, I recommend further reading about this here: >> >> http://www.intel.com/content/www/us/en/pci-express/pci-sig-sr-iov-prim= er-sr-iov-technology-paper.html=20 >> >> http://blog.scottlowe.org/2009/12/02/what-is-sr-iov/ >> > That is fascinating. Extending virtualization to expansion hardware=20 > via SR-IOV, sure would make the kind of setup I'm attempting a lot=20 > easier. However, if I can replicate what I've seen in proof of concept=20 > videos (namely Casey DeLorme's), I think that will meet my needs for=20 > now. As it stands, I initially intend to reserve any discrete GPU(s)=20 > for Windows and rely on an integrated GPU for all other VMs using PV=20 > drivers (wherever possible). Afterward, I want to experiment with=20 > re-assigning the whatever discrete GPU(s) for GPGPU functions under a=20 > Linux VM whenever the GPU is not going to used for gaming (if at all=20 > possible). >> It is likely to take a few years before something useful will come=20 >> out of it. In the meanwhile, unless you want to use several GPUs=20 >> which might not be a bad thing as a lot of monitors these days have=20 >> several inputs, you can resort to using a remote desktop client to=20 >> integrate one machine with another. Virtualbox for example use RDP=20 >> through which you can interact with your virtual machine. In a=20 >> similar manner you can set up a VNC server on your Linux host and=20 >> establish a connection to it through your Windows VM. You will not=20 >> get full 3D functionality (such as Aqua) through the client although=20 >> there is a growing support for it through VirtualGL extensions that=20 >> are coming to VNC and perhaps the Spice protocol. But some clients=20 >> might even allow for seamless mode that lets you mix Linux and=20 >> Windows windows on the same desktop like this for example: >> >> http://i.techrepublic.com.com/blogs/seamless.png >> http://www.youtube.com/watch?v=3DeQr8iI0yZH4 >> >> >> Just keep in mind that this is still a little bit of uncharted=20 >> territory so there may be a few bumps on the way and it may not work=20 >> as smooth as you would desire. >> >> > From everything I've read, solutions that rely on any form of remote=20 > display protocols would be limited to a subset of Direct3D functions.=20 > Furthermore, these would vary from one implementation to another, thus=20 > making them far less attractive for gaming than VGA passthrough...=20 > Well, in my opinion anyway. > > VirtualBox's seamless mode is pretty nifty. But it's a Type 2=20 > Hypervisor and relies on paravirtualized drivers that also suffer from=20 > the same limitations as remote display protocols. It's great for most=20 > things, but gaming is not one of them. And I'm speaking from personal=20 > experience. Though I haven't used them myself, the same would seem to=20 > hold true of Parallel's and VMWare's 'Workstation' offerings. At=20 > least, as far as I've gathered. > > FYI, the Type 1 Hypervisors from Parallel's and VMWare* are priced=20 > waaayyy outside my budget. > I understand that you want full 3D functionality for Windows gaming but=20 maybe you'll find the subset of 3D functionality for the Linux machine=20 acceptable. I have looked into VirtualGL and with TurboVNC, you might=20 get a pretty decent desktop environment and it seems like most of the=20 features are there already. It appears that the 3D is rendered by=20 hardware/GPU before it is streamed through VNC or Spice. So it seems=20 that you would need another GPU for that. You can find more info on=20 VirtualGL here: http://www.virtualgl.org/ Also the line between a type 1 and type 2 hypervisor tend to get a bit=20 blurry. The point with type 1 is that it has access to ring-0 so that it=20 can get access directly to the hardware to be passed through to the=20 guests (I did confuse 'host' and 'guest' in my prior post). It also=20 doesn't need to ask the host OS for permission in the same way as a type=20 2 hypervisor which is likely to give performance advantages in some cases= . However, even a type 2 hypervisor, although it is run as an application=20 inside the OS can get "type 1" like privileges. By patching into the=20 kernel and/or using special "dummy drivers" for hardware to be shared=20 with VMs you can achieve pretty much the same thing, ergo it is no=20 longer clear whether the hypervisor is a type 1 or type 2. There is an article about it from the old IBM Mainframe days but I can't=20 seem to find it. > > *I only found out about VMWare's 'free' vSphere after I'd written this=20 > response. >> >> I see that your demands are somewhat multifaceted. I believe that you=20 >> also want to use diffent services such as using your machine as a=20 >> file server with the possible intention of using filesystems such as=20 >> ZFS. If you do, you should be careful with your selection of hardware=20 >> for these particular purposes. If you want to get full protection=20 >> against data corruption from ZFS, your choice of hardware gets rather=20 >> limited when it comes to choice of hard drives, host bus adapter and=20 >> network controller. The most stable implementation of ZFS is found=20 >> with Illumos based operating systems (such as OpenIndiana, SmartOS,=20 >> OmniOS, Belenix etc) or Solaris if you choose to download it from=20 >> Oracle's website. With these operating systems you are most likely to=20 >> want to use hardware that has certified drivers for it. That way you=20 >> are less likely to run into problems later on. That implies that you=20 >> will be limited to choosing Intel based network adapters and LSI=20 >> based SAS controllers. There should be _no_ hardware RAID=20 >> functionality in the SAS controller that merely should be run in IT=20 >> mode (or Initiator-Target mode). That requires the LSI controller to=20 >> be flashed with IT firmware in most cases. The objective here is to=20 >> make sure that _all_ errors that might occur with the hard drives are=20 >> reported all the way to the software level and that nothing is=20 >> concealed of obfuscated by internal error handling in the hardware.=20 >> It is therefore recommended to use SAS hard drives instead of S-ATA=20 >> (which also are fully compatible with SAS controllers). SAS hard=20 >> drives are not much more expensive than similar SATA drives and you=20 >> get a higher reliability out of them. It is also recommended to have=20 >> at least two drive redundancy simply because if one drive is dead and=20 >> you swap it, it is not uncommon that another drive dies in the=20 >> rebuild process of the RAID cluster because of the added strain the=20 >> rebuild process (or 'resilvering' as it is called in Solaris terms)=20 >> put on the drives. Of course, the system should communicate directly=20 >> to the hard drive hardware and not be obfuscated by some virtual=20 >> abstraction layer in between which means that you either run ZFS on=20 >> the metal or through PCI passthrough of the SAS (and perhaps also=20 >> network) adapters. Also, it is highly recommended that you use ECC=20 >> RAM for such applications and it doesn't hurt to dedicate a few gigs=20 >> of it to the ZFS as RAM is used for cache. The good news is that most=20 >> motherboards with good chipsets support ECC RAM even though you might=20 >> not find anything about it in the user manuals. > Again, thanks for the thorough explanation. This gives me a great deal=20 > to think about. The more I learn about ZFS, the less appealing it=20 > becomes. And by that I mean the confusion over which version of ZFS is=20 > in what OS? And just how well maintained the OSes supporting ZFS are?=20 > Now I have additional hardware considerations to keep in mind that may=20 > (or may not) make the cost of ZFS RAID-Z pool comparable to a hardware=20 > RAID5/6 solution anyway. Do you have any suggestions as to which of=20 > LSI HBAs I should be considering? I haven't found an HCL for ZFS in my=20 > searches. > > Out of curiosity =97 and if you would happen to know =97 do you think w= hat=20 > you suggest about the HBA and SAS drives for ZFS also applies to=20 > Btrfs? I'm assuming it would, but I'd appreciate some confirmation. > > It's funny how the "I" in RAID never really seems to apply...=20 > Especially since it looks more and more like using ZFS or Btrfs will=20 > require I commit myself, from the start, to one or the other and a=20 > discrete HBA. Transitioning from an integrated SATA controller(s) and=20 > mdadm seems rather impractical. If I understand what's involved in=20 > doing so correctly. It may turn out that anything other than mdadm is=20 > price prohibitive. > I don't think you will have a problem with getting ZFS to run and if=20 that's your only goal then you don't need to be very picky with your=20 choice of hardware. I find ZFS pretty easy and handy to use. I has=20 really great functionality and I don't have many bad things to say about=20 it so far. ZFS is a filesystem (along with a couple of software tools to=20 administrate it) just like EXT4 or NTFS so hardware support depends on=20 the platform it runs on. But the point with using ZFS is to get maximum protection against data=20 corruption and that's where the selection of hardware gets limited and=20 there are "best practices" set up to achieve that. I have not tested ZFS=20 on any other platform than on OpenSolaris and OpenIndiana but I do know=20 that it is well implemented on that platform and more mature there than=20 on any other (non-solaris) platform. Another advantage with the OSOL/OI=20 platform is that the CIFS functionality is implemented in the kernel=20 space and not in the userland which will give advantages performance=20 wise if you intend to share files with other windows computers. (I don't=20 deny that Samba is pretty good on Linux too. There are some benchmarks=20 on the phoronix website comparing samba with NFS and they are in favor=20 of Samba on those benchmarks...) The second best implementation is found=20 with FreeBSD and it is probably fairly mature but I haven't tested it=20 myself and some people have run into problems with it in the past. The=20 Linux version is probably merely at infancy stage and likely not yet=20 mature enough for regular use. It is probably not as "bad" as btrfs=20 though. There is quite a bit of information about it on the phoronix.com=20 website (and probably also at lwn.net): http://www.phoronix.com/scan.php?page=3Dnews_item&px=3DMTE4Nzc A search there on ZFS will give more articles. The latest official=20 version of ZFS is 28 and is probably implemented in both Linux, and=20 FreeBSD by now. Later versions have been released since Oracle killed=20 the OpenSolaris project and can be found with the commercial=20 closed-source Solaris platform that is supplied by Oracle. Things have=20 happened since Oracle pulled the plug on OSOL project and leading=20 developers behind the ZFS project such as Jeff Bonwick left Sun (after=20 the acquisition by Oracle) and joined up with the Illumos team instead.=20 So you cannot determine the stability of ZFS and ZPOOL merely by looking=20 into the version number unfortunately and I wouldn't expect the FreeBSD=20 implementation to be as stable as the Solaris implementation. It just=20 takes time for the implementation to mature and the bugs to be weeded=20 out and it just happens to have been around for=20 Solaris/OpenSolaris/Illumos for much longer than the other platforms and=20 the Solaris/Illumos version also happens to get first dibs on the=20 features. Among the Illumos people there is an ambition to drop the=20 version numbering altogether and instead talk about available features. The recommendation to use SAS hard drives is not so much about the=20 quality of the hard drives themselves as it is about the SAS protocol.=20 The SAS protocol simply handles SCSI transport commands in a better and=20 more reliable manner than do SATA. I believe any decent SAS drive would=20 do. As for HBAs I wrote a list with LSI based hardware a while ago here: https://www.illumos.org/boards/1/topics/572 the thing is that a lot of OEMs such as IBM, HP, Cisco, Fujitsu-Siemens,=20 Dell, ... supply their branded HBAs with LSI circuitry on them. What=20 hardware to choose depends on what you're looking for. If you want an=20 8-port controller I would go for Intel SASUC8I or LSI SAS3801E-R. If you=20 want SAS/SATA3 with 6.0 Gb/s then LSI's SAS 9200 series cards would be a=20 better choice. I don't know what OEMs have come up with in the SATA3=20 department since I wrote that list but the chips to look for in that=20 case are the LSI MegaRAID 2004/2008/2016e depending on how many ports=20 you want. If you want to read a further discussion about reliability of different=20 RAID setups I made a post about this in the following thread (last post): http://communities.intel.com/thread/25945 >> I admire your persistence with pursuing this undertaking and wish you=20 >> the best of luck with it! >> Robin. >> >> > Thanks. I've invested too much time in research to not at least make=20 > the attempt. Besides, if all else fails, I can fallback to a two box=20 > solution. That is, if I can get my hypothetical virtualization box to=20 > fit in my budget envelope... > > > _______________________________________________ > Xen-users mailing list > Xen-users@lists.xen.org > http://lists.xen.org/xen-users > > . > --------------030707090408060307080801 Content-Type: text/html; charset="windows-1252" Content-Transfer-Encoding: quoted-printable On 2012-09-24 05:45, ShadesOfGrey wrote:
Sorry for the late response, I've had a lot to digest.

On 09/21/2012 11:22 AM, Robin Axelsson wrote:
If you want to be able to use PCI and VGA passthrough you basically need to make sure that your hardware supports either AMD-Vi (formerly known as AMD-IOMMU) or Intel VT-d extensions. In the Intel case it limits your choice of Motherboard (it must be supported in the BIOS) and CPU. In the AMD case it limits only your choice of motherboard. A good start is to check out one of these pages:

http://wiki.xensource.com/xenwiki/VTdHowTo
http://wiki.xen.org/wiki/VTd_HowTo

A word of warning here is that parts of the documentation is somewhat dated. You can also communicate with e.g. Gigabyte, Asus or ASRock customer support and ask them if a particular motherboard supports these extensions. Most motherboards also have downloadable user manuals, if the BIOS settings in those pages shows options to enable/disable VT-d or AMD-Vi/IOMMU extensions then you will be ok with that motherboard.

The lack of current information about Xen (and KVM) online has been frustrating =97 especially finding the many proof of concept videos that demonstrated possibilities but offered no real specifics. Looking for specifics, I sought information from gaming and enthusiast sites; I figured finding confirmation of VT-d and AMD-Vi support on such sites would be more likely. However, I found that wasn't often the case. I did determine that ASRock motherboards seem to be the most likely to support VT-d, ASUS least likely (unless equipped with an Intel 'sanctioned' VT-d chipset). I had narrowed my choices to two motherboards that appear to offer VT-d support and was intending to contact the manufacturer before purchase. Both choices are a bit pricey and I've been reconsidering whether I should look to other motherboards to reduce costs.

Some motherboards support IOMMU even though it is not found in the user manual or specified on the website. Your best bet is to ask customer support. A guy posted here that he got it working on an Intel motherboard that doesn't even have options for it in the BIOS, so it seems that in some cases it is only up to the CPU. This is not the case with AMD though as I stated before. I have bought a couple of Gigabyte GA990FX-UD7 myself, they are stable and have a good layout. They have support for IOMMU but I haven't tested it thoroughly enough to fully confirm this although I don't believe there would be any problem.

It surprises me that ASRock and ASUS are so different. ASRock is, or at least used to be a subsidiary of ASUS so there shouldn't be that much difference between them.
The other thing is choice of GPU for VGA passthrough and it is preferable that the GPU supports FLR or Function Level Reset as it is called. Thing is that the hardware needs to be reset somehow as it is passed through to the host. This is best done with FLR and nVidia is known to supply firmware patches for some of their Geforce cards with this support and it is said to be supported by default with their Quadro cards. FLR is not the only way to reset a PCI device, a reset could be trigged through the ACPI power management framework by temporarily cutting power to the affected PCI slot. These reset methods are called d3d0 and bus reset. The question however, is if this works on PCI cards that use auxiliary power directly from the PSU. There is a pdf document on the VMWare website (http://www.vmware.com/f= iles/pdf/techpaper/vsp_4_vmdirectpath_host.pdf) about this:

-----------------------
Reset Method

Possible values for the reset method include flr, d3d0, link, bridge, or default.

The default setting is described as follows. If a device supports function level reset (FLR), ESX always uses FLR. If the device does not support FLR, ESX next defaults to link reset and bus reset in that order. Link reset and bus reset might prevent some devices from being assigned to different virtual machines, or from being assigned between the VMkernel and virtual machines. In the absence of FLR, it is possible to use PCI Power Management capability (D3 to D0 transitions) to trigger a reset. Most of the Intel NICs and various other HBAs support this mode.
-----------------------


There are indications from people that d3d0 also work with PCI cards that take power from auxiliary inputs. I suggest that you take a look at the following youtube clip and read the comments there:

http://www.youtube.com/watch?v=3DGtmwnx-k2qg

So it seems that it works although it may be a bit more quirky. It doesn't hurt to take that discussion (particularly about FLR support) with nVidia and/or AMD.

This is precisely the kind of information I was looking for from the threads I started on Ars Technica. It's just unfortunate that FLR and D3 D0 support aren't often found in the tech specs of must expansion hardware. However, now that I know what to ask, I'll try contacting hardware manufacturers prior to purchasing any expansion hardware. Thank you!

D3 and D0 are power states defined for devices in the ACPI specification and can be used to control the supply voltage (Vcc) to PCI and PCIe devices. You can find more information about it here for example:

http://en.wikipedia.org/wiki/A= dvanced_Configuration_and_Power_Interface

---------------

Device states

The device states D0-D3 are device-dependent:

  • D0 Fully On is the operating state.
  • D1 and D2 are intermediate power-states whose definition varies by device.
  • D3 Off has the device powered off and unresponsive to its bus.
---------------

So, either it works for a certain type of hardware or it doesn't and I wouldn't expect a vendor to state this "support" in the specifications since it isn't a "feature" in and of itself if you get me. But maybe this will change and maybe FLR support will become more widespread.

When it comes to virtualization, the technology has come very far, but it is still lacking considerably when it comes to sharing GPUs and also to some degree when it comes to sharing I/O devices (especially when you intend to run many virtual machines on a single system). The GPU today consists of three types of components; the processing unit, graphics memory and the video output unit/adapter and it is not clear as to how to share these components seamlessly between the host and virtual machines with minimal overhead. Whereas there are VT-x extensions that allows you to pretty seamlessly share CPU cores between VMs and the host there are currently none for the processing unit. It is also not clear how the hardware can assist with sharing TV/monitor screen estate between machines with all 3D effects such as Aqua for Win7 and the whatnot enabled for all machines. Especially when considering the dynamics of plugging and unplugging computer monitors to multiport/eyefinity graphics cards and the ability to change screen resolution. Things are improving for sure and a lot of research is likely going into this. I don't know what's happening in the GPU frontline but I know that the next thing with passthrough is the SR-IOV that allows PCI units to present several virtual instances of oneself to several virtual machines. It's a cool thing, I recommend further reading about this here:

http://www.intel.com/content/www/us/en/pci-express/pci-sig-sr-iov= -primer-sr-iov-technology-paper.html
http://blog.scottlowe.org/2009/12/02/what= -is-sr-iov/

That is fascinating. Extending virtualization to expansion hardware via SR-IOV, sure would make the kind of setup I'm attempting a lot easier. However, if I can replicate what I've seen in proof of concept videos (namely Casey DeLorme's), I think that will meet my needs for now. As it stands, I initially intend to reserve any discrete GPU(s) for Windows and rely on an integrated GPU for all other VMs using PV drivers (wherever possible). Afterward, I want to experiment with re-assigning the whatever discrete GPU(s) for GPGPU functions under a Linux VM whenever the GPU is not going to used for gaming (if at all possible).
It is likely to take a few years before something useful will come out of it. In the meanwhile, unless you want to use several GPUs which might not be a bad thing as a lot of monitors these days have several inputs, you can resort to using a remote desktop client to integrate one machine with another. Virtualbox for example use RDP through which you can interact with your virtual machine. In a similar manner you can set up a VNC server on your Linux host and establish a connection to it through your Windows VM. You will not get full 3D functionality (such as Aqua) through the client although there is a growing support for it through VirtualGL extensions that are coming to VNC and perhaps the Spice protocol. But some clients might even allow for seamless mode that lets you mix Linux and Windows windows on the same desktop like this for example:

http://i.techrepublic.com.com/blogs/seamless.= png
http://www.youtube.com/watch?v=3DeQr8iI0yZH4


Just keep in mind that this is still a little bit of uncharted territory so there may be a few bumps on the way and it may not work as smooth as you would desire.


From everything I've read, solutions that rely on any form of remote display protocols would be limited to a subset of Direct3D functions. Furthermore, these would vary from one implementation to another, thus making them far less attractive for gaming than VGA passthrough... Well, in my opinion anyway.

VirtualBox's seamless mode is pretty nifty. But it's a Type 2 Hypervisor and relies on paravirtualized drivers that also suffer from the same limitations as remote display protocols. It's great for most things, but gaming is not one of them. And I'm speaking from personal experience. Though I haven't used them myself, the same would seem to hold true of Parallel's and VMWare's 'Workstation' offerings. At least, as far as I've gathered.

FYI, the Type 1 Hypervisors from Parallel's and VMWare* are priced waaayyy outside my budget.

I understand that you want full 3D functionality for Windows gaming but maybe you'll find the subset of 3D functionality for the Linux machine acceptable. I have looked into VirtualGL and with TurboVNC, you might get a pretty decent desktop environment and it seems like most of the features are there already. It appears that the 3D is rendered by hardware/GPU before it is streamed through VNC or Spice. So it seems that you would need another GPU for that. You can find more info on VirtualGL here:

http://www.virtualgl.org/

Also the line between a type 1 and type 2 hypervisor tend to get a bit blurry. The point with type 1 is that it has access to ring-0 so that it can get access directly to the hardware to be passed through to the guests (I did confuse 'host' and 'guest' in my prior post). It also doesn't need to ask the host OS for permission in the same way as a type 2 hypervisor which is likely to give performance advantages in some cases.

However, even a type 2 hypervisor, although it is run as an application inside the OS can get "type 1" like privileges. By patching into the kernel and/or using special "dummy drivers" for hardware to be shared with VMs you can achieve pretty much the same thing, ergo it is no longer clear whether the hypervisor is a type 1 or type 2.

There is an article about it from the old IBM Mainframe days but I can't seem to find it.


*I only found out about VMWare's 'free' vSphere after I'd written this response.

I see that your demands are somewhat multifaceted. I believe that you also want to use diffent services such as using your machine as a file server with the possible intention of using filesystems such as ZFS. If you do, you should be careful with your selection of hardware for these particular purposes. If you want to get full protection against data corruption from ZFS, your choice of hardware gets rather limited when it comes to choice of hard drives, host bus adapter and network controller. The most stable implementation of ZFS is found with Illumos based operating systems (such as OpenIndiana, SmartOS, OmniOS, Belenix etc) or Solaris if you choose to download it from Oracle's website. With these operating systems you are most likely to want to use hardware that has certified drivers for it. That way you are less likely to run into problems later on. That implies that you will be limited to choosing Intel based network adapters and LSI based SAS controllers. There should be _no_ hardware RAID functionality in the SAS controller that merely should be run in IT mode (or Initiator-Target mode). That requires the LSI controller to be flashed with IT firmware in most cases. The objective here is to make sure that _all_ errors that might occur with the hard drives are reported all the way to the software level and that nothing is concealed of obfuscated by internal error handling in the hardware. It is therefore recommended to use SAS hard drives instead of S-ATA (which also are fully compatible with SAS controllers). SAS hard drives are not much more expensive than similar SATA drives and you get a higher reliability out of them. It is also recommended to have at least two drive redundancy simply because if one drive is dead and you swap it, it is not uncommon that another drive dies in the rebuild process of the RAID cluster because of the added strain the rebuild process (or 'resilvering' as it is called in Solaris terms) put on the drives. Of course, the system should communicate directly to the hard drive hardware and not be obfuscated by some virtual abstraction layer in between which means that you either run ZFS on the metal or through PCI passthrough of the SAS (and perhaps also network) adapters. Also, it is highly recommended that you use ECC RAM for such applications and it doesn't hurt to dedicate a few gigs of it to the ZFS as RAM is used for cache. The good news is that most motherboards with good chipsets support ECC RAM even though you might not find anything about it in the user manuals.
Again, thanks for the thorough explanation. This gives me a great deal to think about. The more I learn about ZFS, the less appealing it becomes. And by that I mean the confusion over which version of ZFS is in what OS? And just how well maintained the OSes supporting ZFS are? Now I have additional hardware considerations to keep in mind that may (or may not) make the cost of ZFS RAID-Z pool comparable to a hardware RAID5/6 solution anyway. Do you have any suggestions as to which of LSI HBAs I should be considering? I haven't found an HCL for ZFS in my searches.

Out of curiosity =97 and if you would happen to know =97 do you thi= nk what you suggest about the HBA and SAS drives for ZFS also applies to Btrfs? I'm assuming it would, but I'd appreciate some confirmation.

It's funny how the "I" in RAID never really seems to apply... Especially since it looks more and more like using ZFS or Btrfs will require I commit myself, from the start, to one or the other and a discrete HBA. Transitioning from an integrated SATA controller(s) and mdadm seems rather impractical. If I understand what's involved in doing so correctly. It may turn out that anything other than mdadm is price prohibitive.


I don't think you will have a problem with getting ZFS to run and if that's your only goal then you don't need to be very picky with your choice of hardware. I find ZFS pretty easy and handy to use. I has really great functionality and I don't have many bad things to say about it so far. ZFS is a filesystem (along with a couple of software tools to administrate it) just like EXT4 or NTFS so hardware support depends on the platform it runs on.

But the point with using ZFS is to get maximum protection against data corruption and that's where the selection of hardware gets limited and there are "best practices" set up to achieve that. I have not tested ZFS on any other platform than on OpenSolaris and OpenIndiana but I do know that it is well implemented on that platform and more mature there than on any other (non-solaris) platform. Another advantage with the OSOL/OI platform is that the CIFS functionality is implemented in the kernel space and not in the userland which will give advantages performance wise if you intend to share files with other windows computers. (I don't deny that Samba is pretty good on Linux too. There are some benchmarks on the phoronix website comparing samba with NFS and they are in favor of Samba on those benchmarks...) The second best implementation is found with FreeBSD and it is probably fairly mature but I haven't tested it myself and some people have run into problems with it in the past. The Linux version is probably merely at infancy stage and likely not yet mature enough for regular use. It is probably not as "bad" as btrfs though. There is quite a bit of information about it on the phoronix.com website (and probably also at lwn.net):

http://www.phoronix.com/scan.ph= p?page=3Dnews_item&px=3DMTE4Nzc

A search there on ZFS will give more articles. The latest official version of ZFS is 28 and is probably implemented in both Linux, and FreeBSD by now. Later versions have been released since Oracle killed the OpenSolaris project and can be found with the commercial closed-source Solaris platform that is supplied by Oracle. Things have happened since Oracle pulled the plug on OSOL project and leading developers behind the ZFS project such as Jeff Bonwick left Sun (after the acquisition by Oracle) and joined up with the Illumos team instead. So you cannot determine the stability of ZFS and ZPOOL merely by looking into the version number unfortunately and I wouldn't expect the FreeBSD implementation to be as stable as the Solaris implementation. It just takes time for the implementation to mature and the bugs to be weeded out and it just happens to have been around for Solaris/OpenSolaris/Illumos for much longer than the other platforms and the Solaris/Illumos version also happens to get first dibs on the features. Among the Illumos people there is an ambition to drop the version numbering altogether and instead talk about available features.

The recommendation to use SAS hard drives is not so much about the quality of the hard drives themselves as it is about the SAS protocol. The SAS protocol simply handles SCSI transport commands in a better and more reliable manner than do SATA. I believe any decent SAS drive would do. As for HBAs I wrote a list with LSI based hardware a while ago here:

https://www.illumos.org/boards/1/topics/572

the thing is that a lot of OEMs such as IBM, HP, Cisco, Fujitsu-Siemens, Dell, ... supply their branded HBAs with LSI circuitry on them. What hardware to choose depends on what you're looking for. If you want an 8-port controller I would go for Intel SASUC8I or LSI SAS3801E-R. If you want SAS/SATA3 with 6.0 Gb/s then LSI's SAS 9200 series cards would be a better choice. I don't know what OEMs have come up with in the SATA3 department since I wrote that list but the chips to look for in that case are the LSI MegaRAID 2004/2008/2016e depending on how many ports you want.

If you want to read a further discussion about reliability of different RAID setups I made a post about this in the following thread (last post):

http://communities.intel.com/thread/25945


I admire your persistence with pursuing this undertaking and wish you the best of luck with it!
Robin.


Thanks. I've invested too much time in research to not at least make the attempt. Besides, if all else fails, I can fallback to a two box solution. That is, if I can get my hypothetical virtualization box to fit in my budget envelope...


_______________________________________________
Xen-users mailing list
Xen-users@lists.xen.org
http://lists.xen.org/xen-users

.


--------------030707090408060307080801-- --===============3543537349546090796== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users --===============3543537349546090796==-- From xen-users-bounces@lists.xen.org Mon Sep 24 13:17:22 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Mon, 24 Sep 2012 13:17:22 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TG8WP-0000hC-0h; Mon, 24 Sep 2012 13:16:25 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TG8WM-0000h4-W2 for xen-users@lists.xen.org; Mon, 24 Sep 2012 13:16:23 +0000 Received: from [85.158.143.35:22888] by server-1.bemta-4.messagelabs.com id 9A/27-05684-62D50605; Mon, 24 Sep 2012 13:16:22 +0000 X-Env-Sender: conor.winchcombe@sap.com X-Msg-Ref: server-11.tower-21.messagelabs.com!1348492565!12823832!1 X-Originating-IP: [155.56.66.96] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogMTU1LjU2LjY2Ljk2ID0+IDUwNzY4NA==\n, received_headers: No Received headers X-StarScan-Received: X-StarScan-Version: 6.6.1.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 15936 invoked from network); 24 Sep 2012 13:16:06 -0000 Received: from smtpgw01.sap-ag.de (HELO smtpgw.sap-ag.de) (155.56.66.96) by server-11.tower-21.messagelabs.com with AES128-SHA encrypted SMTP; 24 Sep 2012 13:16:06 -0000 From: "Winchcombe, Conor" To: "xen-users@lists.xen.org" Thread-Topic: [Xen-users] Xen 4.1.2 error trying to set up remus Thread-Index: Ac2aRuV8GWifiRpaQlmrK77fDwxRCg== Date: Mon, 24 Sep 2012 11:22:37 +0000 Message-ID: Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [10.21.40.41] MIME-Version: 1.0 Subject: [Xen-users] Xen 4.1.2 error trying to set up remus X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============2182683839582791133==" Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org --===============2182683839582791133== Content-Language: en-US Content-Type: multipart/alternative; boundary="_000_D9D9B0FF9377354A9EA3BA91CF4A50A90262D3DEWDFEMB17Aglobal_" --_000_D9D9B0FF9377354A9EA3BA91CF4A50A90262D3DEWDFEMB17Aglobal_ Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable When I attempt to set up remus between two machines I get an error in the r= emus log file, I can't understand why it occurs, I have the same vms runnin= g on both systems, so attempted replication shouldnt be an issue. The Log f= ile is as follows: Disk is not replicated: phy:/dev/loop0,xvda,w Disk is not replicated: phy:/dev/loop1,xvdb,w tc qdisc add dev vif1.0 ingress RTNETLINK answers: File exists tc filter add dev vif1.0 parent ffff: proto ip pref 10 u32 match u32 0 0 ac= tion mirred egress redirect dev ifb0 RTNETLINK answers: No such file or directory We have an error talking to the kernel Traceback (most recent call last): File "/usr/bin/remus", line 219, in run(cfg) File "/usr/bin/remus", line 125, in run bufs.append(BufferedNIC(vif)) File "/usr/lib64/python2.6/site-packages/xen/remus/device.py", line 326, = in __init__ self.setup() File "/usr/lib64/python2.6/site-packages/xen/remus/device.py", line 358, = in setup self.bufdev.install(self.vif) File "/usr/lib64/python2.6/site-packages/xen/remus/device.py", line 184, = in install 'dev %s' % (vif.dev, self.devname)) File "/usr/lib64/python2.6/site-packages/xen/remus/util.py", line 71, in = runcmd proc.returncode) xen.remus.util.PipeException: tc failed (errmsg: RTNETLINK answers: No such= file or directory We have an error talking to the kernel): 2, No such file or directory The remus command used to get this file is as follows: remus -i 100 sles11-sp1-xm BackupMachineIP >/var/log/xen/domU-sles11-sp1-24= -09-12.log 2>&1 & BackupMachineIP is setup as the name for the IP address of the backup devic= e, the contents of xm list and the loopback device setups on each machine a= re as follows: xm list Primary: Name ID Mem VCPUs State Tim= e(s) Domain-0 0 1036702 8 r----- 411= 617.9 sles11-sp1 512 4 = 0.0 sles11-sp1-xm 1 256 1 -b---- 7= 7.0 sles11-sp2 512 4 = 0.0 sles11-sp2-xm 2 256 1 -b---- 6= 2.0 Secondary: Name ID Mem VCPUs State Tim= e(s) Domain-0 0 1400 2 r----- 7= 3.1 sles11-sp1-xm 1 256 1 -b---- 1= 1.6 sles11-sp2-xm 2 256 1 -b---- 1= 4.0 losetup Primary: /dev/loop0: [0808]:337772 (/tmp/base/sles11sp1/sles11sp1.img) /dev/loop1: [0808]:337773 (/tmp/base/sles11sp1/swap) /dev/loop2: [0808]:337779 (/tmp/base/sles11sp2/sles11sp2.img) /dev/loop3: [0808]:337780 (/tmp/base/sles11sp2/swap) Secondary: /dev/loop0: [0805]:2109411 (/tmp/base/sles11sp1/sles11sp1.img) /dev/loop1: [0805]:2109412 (/tmp/base/sles11sp1/swap) /dev/loop2: [0805]:1840010 (/tmp/base/sles11sp2/sles11sp2.img) /dev/loop3: [0805]:1840012 (/tmp/base/sles11sp2/swap) Conor, Winchcombe SAP Research Belfast SAP (UK) Limited I The Concourse I Queen's Road I Queen's Islan= d I Belfast BT3 9DT mailto: conor.winchcombe@sap.com I www.= sap.com/research ---------------------------------------------------------------------------= ----------------------------------------------- This communication contains information which is confidential and may also = be privileged. It is for the exclusive use of the addressee. If you are not= the addressee please contact us immediately and also delete the communicat= ion from your computer. Steps have been taken to ensure this e-mail is free= from computer viruses but the recipient is responsible for ensuring that i= t is actually virus free before opening it or any attachments. Any views an= d/or opinions expressed in this e-mail are of the author only and do not re= present the views of SAP. SAP (UK) Limited, Registered in England No. 2152073. Registered Office: Clo= ckhouse Place, Bedfont Road, Feltham, Middlesex, TW14 8HD ---------------------------------------------------------------------------= ------------------------------------------------ --_000_D9D9B0FF9377354A9EA3BA91CF4A50A90262D3DEWDFEMB17Aglobal_ Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable

When I attempt to set up remus between two machines = I get an error in the remus log file, I can’t understand why it occur= s, I have the same vms running on both systems, so attempted replication sh= ouldnt be an issue. The Log file is as follows:

 

Disk is not replicated: phy:/dev/loop0,xvda,w

Disk is not replicated: phy:/dev/loop1,xvdb,w

tc qdisc add dev vif1.0 ingress

RTNETLINK answers: File exists

tc filter add dev vif1.0 parent ffff: proto ip pref = 10 u32 match u32 0 0 action

mirred egress redirect dev ifb0

RTNETLINK answers: No such file or directory

We have an error talking to the kernel

Traceback (most recent call last):

  File "/usr/bin/remus", line 219, in= <module>

     run(cfg)

  File "/usr/bin/remus", line 125, in= run

     bufs.append(BufferedNIC(vif= ))

  File "/usr/lib64/python2.6/site-packages= /xen/remus/device.py", line 326, in __init__

    self.setup()

  File "/usr/lib64/python2.6/site-packages= /xen/remus/device.py", line 358, in setup

    self.bufdev.install(self.vif)

  File "/usr/lib64/python2.6/site-packages= /xen/remus/device.py", line 184, in install

    'dev %s' % (vif.dev, self.devname= ))

  File "/usr/lib64/python2.6/site-packages= /xen/remus/util.py", line 71, in runcmd

    proc.returncode)

xen.remus.util.PipeException: tc failed (errmsg: RTN= ETLINK answers: No such file or directory

We have an error talking to the kernel): 2, No such = file or directory

 

The remus command used to get this file is as follow= s:

remus -i 100 sles11-sp1-xm BackupMachineIP >/var/= log/xen/domU-sles11-sp1-24-09-12.log 2>&1 &

 

BackupMachineIP is setup as the name for the IP addr= ess of the backup device, the contents of xm list and the loopback device s= etups on each machine are as follows:

 

xm list

 

Primary:

Name        =              &n= bsp;            = ;      ID   Mem VCPUs  &n= bsp;   State   Time(s)

Domain-0       &n= bsp;            = ;            &n= bsp;    0 1036702     8   = ;  r----- 411617.9

sles11-sp1       =             &nb= sp;            =        512     4 &nb= sp;            =    0.0

sles11-sp1-xm      &nb= sp;             = ;            1&= nbsp;  256     1     -b----&nb= sp;    77.0

sles11-sp2       =             &nb= sp;            =        512     4 &nb= sp;            =    0.0

sles11-sp2-xm      &nb= sp;            =              2&= nbsp;  256     1     -b----&nb= sp;    62.0

 

Secondary:

Name        =             &nb= sp;             = ;      ID   Mem VCPUs  &n= bsp;   State   Time(s)

Domain-0       &n= bsp;            = ;            &n= bsp;    0  1400     2  &n= bsp;  r-----     73.1

sles11-sp1-xm      &nb= sp;            =              1&= nbsp;  256     1     -b----&nb= sp;    11.6

sles11-sp2-xm      &nb= sp;            =              2&= nbsp;  256     1     -b----&nb= sp;    14.0

 

losetup

 

Primary:

/dev/loop0: [0808]:337772 (/tmp/base/sles11sp1/sles1= 1sp1.img)

/dev/loop1: [0808]:337773 (/tmp/base/sles11sp1/swap)=

/dev/loop2: [0808]:337779 (/tmp/base/sles11sp2/sles1= 1sp2.img)

/dev/loop3: [0808]:337780 (/tmp/base/sles11sp2/swap)=

 

Secondary:

/dev/loop0: [0805]:2109411 (/tmp/base/sles11sp1/sles= 11sp1.img)

/dev/loop1: [0805]:2109412 (/tmp/base/sles11sp1/swap= )

/dev/loop2: [0805]:1840010 (/tmp/base/sles11sp2/sles= 11sp2.img)

/dev/loop3: [0805]:1840012 (/tmp/base/sles11sp2/swap= )

 

 

Conor, Winchcombe

SAP Research Belfast

S= AP (UK) Limited   I   The Concourse   I =   Queen's Road   I   Queen's Island   I&= nbsp;  Belfast BT3 9DT

<= o:p> 

m= ailto: conor.winchcombe@sap.com&nb= sp; I   www.sap.com/research

<= o:p> 

-= ---------------------------------------------------------------------------= ----------------------------------------------

-= ---------------------------------------------------------------------------= -----------------------------------------------

 

--_000_D9D9B0FF9377354A9EA3BA91CF4A50A90262D3DEWDFEMB17Aglobal_-- --===============2182683839582791133== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users --===============2182683839582791133==-- From xen-users-bounces@lists.xen.org Mon Sep 24 13:17:22 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Mon, 24 Sep 2012 13:17:22 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TG8WP-0000hC-0h; Mon, 24 Sep 2012 13:16:25 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TG8WM-0000h4-W2 for xen-users@lists.xen.org; Mon, 24 Sep 2012 13:16:23 +0000 Received: from [85.158.143.35:22888] by server-1.bemta-4.messagelabs.com id 9A/27-05684-62D50605; Mon, 24 Sep 2012 13:16:22 +0000 X-Env-Sender: conor.winchcombe@sap.com X-Msg-Ref: server-11.tower-21.messagelabs.com!1348492565!12823832!1 X-Originating-IP: [155.56.66.96] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogMTU1LjU2LjY2Ljk2ID0+IDUwNzY4NA==\n, received_headers: No Received headers X-StarScan-Received: X-StarScan-Version: 6.6.1.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 15936 invoked from network); 24 Sep 2012 13:16:06 -0000 Received: from smtpgw01.sap-ag.de (HELO smtpgw.sap-ag.de) (155.56.66.96) by server-11.tower-21.messagelabs.com with AES128-SHA encrypted SMTP; 24 Sep 2012 13:16:06 -0000 From: "Winchcombe, Conor" To: "xen-users@lists.xen.org" Thread-Topic: [Xen-users] Xen 4.1.2 error trying to set up remus Thread-Index: Ac2aRuV8GWifiRpaQlmrK77fDwxRCg== Date: Mon, 24 Sep 2012 11:22:37 +0000 Message-ID: Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [10.21.40.41] MIME-Version: 1.0 Subject: [Xen-users] Xen 4.1.2 error trying to set up remus X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============2182683839582791133==" Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org --===============2182683839582791133== Content-Language: en-US Content-Type: multipart/alternative; boundary="_000_D9D9B0FF9377354A9EA3BA91CF4A50A90262D3DEWDFEMB17Aglobal_" --_000_D9D9B0FF9377354A9EA3BA91CF4A50A90262D3DEWDFEMB17Aglobal_ Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable When I attempt to set up remus between two machines I get an error in the r= emus log file, I can't understand why it occurs, I have the same vms runnin= g on both systems, so attempted replication shouldnt be an issue. The Log f= ile is as follows: Disk is not replicated: phy:/dev/loop0,xvda,w Disk is not replicated: phy:/dev/loop1,xvdb,w tc qdisc add dev vif1.0 ingress RTNETLINK answers: File exists tc filter add dev vif1.0 parent ffff: proto ip pref 10 u32 match u32 0 0 ac= tion mirred egress redirect dev ifb0 RTNETLINK answers: No such file or directory We have an error talking to the kernel Traceback (most recent call last): File "/usr/bin/remus", line 219, in run(cfg) File "/usr/bin/remus", line 125, in run bufs.append(BufferedNIC(vif)) File "/usr/lib64/python2.6/site-packages/xen/remus/device.py", line 326, = in __init__ self.setup() File "/usr/lib64/python2.6/site-packages/xen/remus/device.py", line 358, = in setup self.bufdev.install(self.vif) File "/usr/lib64/python2.6/site-packages/xen/remus/device.py", line 184, = in install 'dev %s' % (vif.dev, self.devname)) File "/usr/lib64/python2.6/site-packages/xen/remus/util.py", line 71, in = runcmd proc.returncode) xen.remus.util.PipeException: tc failed (errmsg: RTNETLINK answers: No such= file or directory We have an error talking to the kernel): 2, No such file or directory The remus command used to get this file is as follows: remus -i 100 sles11-sp1-xm BackupMachineIP >/var/log/xen/domU-sles11-sp1-24= -09-12.log 2>&1 & BackupMachineIP is setup as the name for the IP address of the backup devic= e, the contents of xm list and the loopback device setups on each machine a= re as follows: xm list Primary: Name ID Mem VCPUs State Tim= e(s) Domain-0 0 1036702 8 r----- 411= 617.9 sles11-sp1 512 4 = 0.0 sles11-sp1-xm 1 256 1 -b---- 7= 7.0 sles11-sp2 512 4 = 0.0 sles11-sp2-xm 2 256 1 -b---- 6= 2.0 Secondary: Name ID Mem VCPUs State Tim= e(s) Domain-0 0 1400 2 r----- 7= 3.1 sles11-sp1-xm 1 256 1 -b---- 1= 1.6 sles11-sp2-xm 2 256 1 -b---- 1= 4.0 losetup Primary: /dev/loop0: [0808]:337772 (/tmp/base/sles11sp1/sles11sp1.img) /dev/loop1: [0808]:337773 (/tmp/base/sles11sp1/swap) /dev/loop2: [0808]:337779 (/tmp/base/sles11sp2/sles11sp2.img) /dev/loop3: [0808]:337780 (/tmp/base/sles11sp2/swap) Secondary: /dev/loop0: [0805]:2109411 (/tmp/base/sles11sp1/sles11sp1.img) /dev/loop1: [0805]:2109412 (/tmp/base/sles11sp1/swap) /dev/loop2: [0805]:1840010 (/tmp/base/sles11sp2/sles11sp2.img) /dev/loop3: [0805]:1840012 (/tmp/base/sles11sp2/swap) Conor, Winchcombe SAP Research Belfast SAP (UK) Limited I The Concourse I Queen's Road I Queen's Islan= d I Belfast BT3 9DT mailto: conor.winchcombe@sap.com I www.= sap.com/research ---------------------------------------------------------------------------= ----------------------------------------------- This communication contains information which is confidential and may also = be privileged. It is for the exclusive use of the addressee. If you are not= the addressee please contact us immediately and also delete the communicat= ion from your computer. Steps have been taken to ensure this e-mail is free= from computer viruses but the recipient is responsible for ensuring that i= t is actually virus free before opening it or any attachments. Any views an= d/or opinions expressed in this e-mail are of the author only and do not re= present the views of SAP. SAP (UK) Limited, Registered in England No. 2152073. Registered Office: Clo= ckhouse Place, Bedfont Road, Feltham, Middlesex, TW14 8HD ---------------------------------------------------------------------------= ------------------------------------------------ --_000_D9D9B0FF9377354A9EA3BA91CF4A50A90262D3DEWDFEMB17Aglobal_ Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable

When I attempt to set up remus between two machines = I get an error in the remus log file, I can’t understand why it occur= s, I have the same vms running on both systems, so attempted replication sh= ouldnt be an issue. The Log file is as follows:

 

Disk is not replicated: phy:/dev/loop0,xvda,w

Disk is not replicated: phy:/dev/loop1,xvdb,w

tc qdisc add dev vif1.0 ingress

RTNETLINK answers: File exists

tc filter add dev vif1.0 parent ffff: proto ip pref = 10 u32 match u32 0 0 action

mirred egress redirect dev ifb0

RTNETLINK answers: No such file or directory

We have an error talking to the kernel

Traceback (most recent call last):

  File "/usr/bin/remus", line 219, in= <module>

     run(cfg)

  File "/usr/bin/remus", line 125, in= run

     bufs.append(BufferedNIC(vif= ))

  File "/usr/lib64/python2.6/site-packages= /xen/remus/device.py", line 326, in __init__

    self.setup()

  File "/usr/lib64/python2.6/site-packages= /xen/remus/device.py", line 358, in setup

    self.bufdev.install(self.vif)

  File "/usr/lib64/python2.6/site-packages= /xen/remus/device.py", line 184, in install

    'dev %s' % (vif.dev, self.devname= ))

  File "/usr/lib64/python2.6/site-packages= /xen/remus/util.py", line 71, in runcmd

    proc.returncode)

xen.remus.util.PipeException: tc failed (errmsg: RTN= ETLINK answers: No such file or directory

We have an error talking to the kernel): 2, No such = file or directory

 

The remus command used to get this file is as follow= s:

remus -i 100 sles11-sp1-xm BackupMachineIP >/var/= log/xen/domU-sles11-sp1-24-09-12.log 2>&1 &

 

BackupMachineIP is setup as the name for the IP addr= ess of the backup device, the contents of xm list and the loopback device s= etups on each machine are as follows:

 

xm list

 

Primary:

Name        =              &n= bsp;            = ;      ID   Mem VCPUs  &n= bsp;   State   Time(s)

Domain-0       &n= bsp;            = ;            &n= bsp;    0 1036702     8   = ;  r----- 411617.9

sles11-sp1       =             &nb= sp;            =        512     4 &nb= sp;            =    0.0

sles11-sp1-xm      &nb= sp;             = ;            1&= nbsp;  256     1     -b----&nb= sp;    77.0

sles11-sp2       =             &nb= sp;            =        512     4 &nb= sp;            =    0.0

sles11-sp2-xm      &nb= sp;            =              2&= nbsp;  256     1     -b----&nb= sp;    62.0

 

Secondary:

Name        =             &nb= sp;             = ;      ID   Mem VCPUs  &n= bsp;   State   Time(s)

Domain-0       &n= bsp;            = ;            &n= bsp;    0  1400     2  &n= bsp;  r-----     73.1

sles11-sp1-xm      &nb= sp;            =              1&= nbsp;  256     1     -b----&nb= sp;    11.6

sles11-sp2-xm      &nb= sp;            =              2&= nbsp;  256     1     -b----&nb= sp;    14.0

 

losetup

 

Primary:

/dev/loop0: [0808]:337772 (/tmp/base/sles11sp1/sles1= 1sp1.img)

/dev/loop1: [0808]:337773 (/tmp/base/sles11sp1/swap)=

/dev/loop2: [0808]:337779 (/tmp/base/sles11sp2/sles1= 1sp2.img)

/dev/loop3: [0808]:337780 (/tmp/base/sles11sp2/swap)=

 

Secondary:

/dev/loop0: [0805]:2109411 (/tmp/base/sles11sp1/sles= 11sp1.img)

/dev/loop1: [0805]:2109412 (/tmp/base/sles11sp1/swap= )

/dev/loop2: [0805]:1840010 (/tmp/base/sles11sp2/sles= 11sp2.img)

/dev/loop3: [0805]:1840012 (/tmp/base/sles11sp2/swap= )

 

 

Conor, Winchcombe

SAP Research Belfast

S= AP (UK) Limited   I   The Concourse   I =   Queen's Road   I   Queen's Island   I&= nbsp;  Belfast BT3 9DT

<= o:p> 

m= ailto: conor.winchcombe@sap.com&nb= sp; I   www.sap.com/research

<= o:p> 

-= ---------------------------------------------------------------------------= ----------------------------------------------

-= ---------------------------------------------------------------------------= -----------------------------------------------

 

--_000_D9D9B0FF9377354A9EA3BA91CF4A50A90262D3DEWDFEMB17Aglobal_-- --===============2182683839582791133== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users --===============2182683839582791133==-- From xen-users-bounces@lists.xen.org Mon Sep 24 16:48:14 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Mon, 24 Sep 2012 16:48:14 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TGBoE-0000eY-Ky; Mon, 24 Sep 2012 16:47:02 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TGBYi-0000FE-Ka for xen-users@lists.xen.org; Mon, 24 Sep 2012 16:31:00 +0000 Received: from [85.158.143.35:25406] by server-3.bemta-4.messagelabs.com id F8/50-10986-3CA80605; Mon, 24 Sep 2012 16:30:59 +0000 X-Env-Sender: kevin.parker092@gmail.com X-Msg-Ref: server-10.tower-21.messagelabs.com!1348504257!10278384!1 X-Originating-IP: [209.85.223.173] X-SpamReason: No, hits=0.9 required=7.0 tests=HTML_40_50,HTML_MESSAGE, ML_RADAR_SPEW_LINKS_14,RCVD_BY_IP,spamassassin: X-StarScan-Received: X-StarScan-Version: 6.6.1.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 12880 invoked from network); 24 Sep 2012 16:30:58 -0000 Received: from mail-ie0-f173.google.com (HELO mail-ie0-f173.google.com) (209.85.223.173) by server-10.tower-21.messagelabs.com with RC4-SHA encrypted SMTP; 24 Sep 2012 16:30:58 -0000 Received: by iea17 with SMTP id 17so8500272iea.32 for ; Mon, 24 Sep 2012 09:30:57 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:date:message-id:subject:from:to:content-type; bh=UzPqSbw3TDy+llHMca2V9NOuD3vaepqnFQsnMzH7Ec4=; b=vPJKqSyXQVYkb9ox/+EZYApX6bFAVf3I8a1BzfHOxr0+8lNRexenaUi/kD3MFGDDZ0 NYpL6kh4IE97AIzpECAYvvldue0hZCwVMI7hwc75dDwqC5oEGvc9grH+tiQVB3WwjgXx 2eZBaV8wU/LaDBo2cq/C/aM+oR+g2MRf0GwFZbpZ2KPELsXFXKmbNeW3G02BkD+KvrME Abgqb2MbbEtde0onFFru/1l3OmT6/g9X9RIgYx6bJOjMox08IN286bkVRmnPLx55QH0Z +zn2QueKG6BsZ5bFaM5JHobJh2cQSqteIAFuCs5LcOWKaNiSuxzyyBpmbPV0+PicP2Z/ XTxQ== MIME-Version: 1.0 Received: by 10.50.170.98 with SMTP id al2mr5777250igc.47.1348504257098; Mon, 24 Sep 2012 09:30:57 -0700 (PDT) Received: by 10.64.48.163 with HTTP; Mon, 24 Sep 2012 09:30:57 -0700 (PDT) Date: Mon, 24 Sep 2012 22:00:57 +0530 Message-ID: From: kevin parker To: xen-users@lists.xen.org X-Mailman-Approved-At: Mon, 24 Sep 2012 16:47:01 +0000 Subject: [Xen-users] Creating guest in command mode failing when used in para mode X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============7801328455555760819==" Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org --===============7801328455555760819== Content-Type: multipart/alternative; boundary=e89a8f3ba96738f3fc04ca751d4f --e89a8f3ba96738f3fc04ca751d4f Content-Type: text/plain; charset=ISO-8859-1 Hi all, I am new to running xen in command mode.I have tried creating xen using virt-manager and its working ok.But i can not make it work using command line.For that i installed virt-install and run this command (trying to install *ubuntu 12.04 64 bit*) *parvirtulization:* virt-install --name vm1 --ram 512 --vcpus=1 *-p* --description=vm --location=/var/lib/libvirt/images/12.04.iso*(64 bit ubuntu)* --disk path=/VM/secondvm,size=1 but its returning Starting install... Retrieving file version.info... | 116 B 00:00 ... ERROR *Couldn't find xen kernel for Ubuntu tree*. but in * v *mode i am able to create vm. *fullvirt* virt-install --name secondvm --ram 512 --vcpus=1 *-v* --description=second-vm --location=/var/lib/libvirt/images/12.04.iso --disk path=/VM/secondvm,size=1 Starting install... Retrieving file version.info... | 116 B 00:00 ... Retrieving file linux... | 9.5 MB 00:00 ... Retrieving file initrd.gz... | 33 MB 00:00 ... Creating storage file secondvm | 1.0 GB 00:00 Creating domain... | 0 B 00:00 2012-09-24 22:01:27.810+0000: 5067: info : libvirt version: 0.9.8 2012-09-24 22:01:27.810+0000: 5067: warning : xenHypervisorMakeCapabilities:2751 : Failed to get host power management capabilities Connected to domain secondvm Escape character is ^] *Details* dom0:ubuntu 12.04 64 bit xen version: 4.1.2 Can any one tell me how to solve this also how can i get a graphical console for installing guest vm,like choosing partition type and swap. Expecting a reply, Kevin --e89a8f3ba96738f3fc04ca751d4f Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Hi all,
=A0 =A0 =A0 =A0 =A0I am new to running xen in command mode.I ha= ve tried creating xen using virt-manager and its working ok.But i can not m= ake it work using command line.For that i installed virt-install=A0
and run this command (trying=A0to install ubuntu 12.04 64 bit) parvirtulization:

virt-install --name vm1 -= -ram 512 --vcpus=3D1 -p --description=3Dvm --location=3D/var/lib/lib= virt/images/12.04.iso(64 bit ubuntu) --disk path=3D/VM/secondvm,size= =3D1=A0

but its returning=A0

Star= ting install...
Retrieving file version.info... =A0 =A0 =A0 =A0 = =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0= =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 = =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0| =A0116 B = =A0 =A0 00:00 ...
ERROR =A0 =A0Couldn't find xen kernel for Ubuntu tree.

but in =A0v mode i am able to create vm.<= /div>


fullvirt

virt-install --name secondvm --ram 512 --vcpus=3D1=A0-v=A0--descript= ion=3Dsecond-vm --location=3D/var/lib/libvirt/images/12.04.iso --disk path= =3D/VM/secondvm,size=3D1 =A0

Starting install= ...
Retrieving file version.info... =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0= =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 = =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0= =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0| =A0116 B =A0 =A0 00:00 ...
= Retrieving file linux... =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 = =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0= =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 = =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 | 9.5 MB =A0 =A0 00:00 ...
Retrieving file initrd.gz... =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 = =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0= =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 = =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 | =A033 MB =A0 =A0 00:00 ...
Creating storage file secondvm =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 = =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0= =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 = =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 | 1.0 GB =A0 =A0 00:00
Creating domain... =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0= =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 = =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0= =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 | =A0 =A00 B =A0 =A0 0= 0:00
2012-09-24 22:01:27.810+0000: 5067: info : libvirt version: = 0.9.8
2012-09-24 22:01:27.810+0000: 5067: warning : xenHypervisorMakeCapabil= ities:2751 : Failed to get host power management capabilities
Con= nected to domain secondvm
Escape character is ^]


Details=A0
dom0:ubuntu = 12.04 64 bit
xen version: 4.1.2
Can any one tell = me how to solve this also how can i get a graphical console for installing = guest vm,like choosing partition type and swap.

Expecting a reply,

Kevin
--e89a8f3ba96738f3fc04ca751d4f-- --===============7801328455555760819== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users --===============7801328455555760819==-- From xen-users-bounces@lists.xen.org Mon Sep 24 16:48:14 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Mon, 24 Sep 2012 16:48:14 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TGBoE-0000eY-Ky; Mon, 24 Sep 2012 16:47:02 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TGBYi-0000FE-Ka for xen-users@lists.xen.org; Mon, 24 Sep 2012 16:31:00 +0000 Received: from [85.158.143.35:25406] by server-3.bemta-4.messagelabs.com id F8/50-10986-3CA80605; Mon, 24 Sep 2012 16:30:59 +0000 X-Env-Sender: kevin.parker092@gmail.com X-Msg-Ref: server-10.tower-21.messagelabs.com!1348504257!10278384!1 X-Originating-IP: [209.85.223.173] X-SpamReason: No, hits=0.9 required=7.0 tests=HTML_40_50,HTML_MESSAGE, ML_RADAR_SPEW_LINKS_14,RCVD_BY_IP,spamassassin: X-StarScan-Received: X-StarScan-Version: 6.6.1.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 12880 invoked from network); 24 Sep 2012 16:30:58 -0000 Received: from mail-ie0-f173.google.com (HELO mail-ie0-f173.google.com) (209.85.223.173) by server-10.tower-21.messagelabs.com with RC4-SHA encrypted SMTP; 24 Sep 2012 16:30:58 -0000 Received: by iea17 with SMTP id 17so8500272iea.32 for ; Mon, 24 Sep 2012 09:30:57 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:date:message-id:subject:from:to:content-type; bh=UzPqSbw3TDy+llHMca2V9NOuD3vaepqnFQsnMzH7Ec4=; b=vPJKqSyXQVYkb9ox/+EZYApX6bFAVf3I8a1BzfHOxr0+8lNRexenaUi/kD3MFGDDZ0 NYpL6kh4IE97AIzpECAYvvldue0hZCwVMI7hwc75dDwqC5oEGvc9grH+tiQVB3WwjgXx 2eZBaV8wU/LaDBo2cq/C/aM+oR+g2MRf0GwFZbpZ2KPELsXFXKmbNeW3G02BkD+KvrME Abgqb2MbbEtde0onFFru/1l3OmT6/g9X9RIgYx6bJOjMox08IN286bkVRmnPLx55QH0Z +zn2QueKG6BsZ5bFaM5JHobJh2cQSqteIAFuCs5LcOWKaNiSuxzyyBpmbPV0+PicP2Z/ XTxQ== MIME-Version: 1.0 Received: by 10.50.170.98 with SMTP id al2mr5777250igc.47.1348504257098; Mon, 24 Sep 2012 09:30:57 -0700 (PDT) Received: by 10.64.48.163 with HTTP; Mon, 24 Sep 2012 09:30:57 -0700 (PDT) Date: Mon, 24 Sep 2012 22:00:57 +0530 Message-ID: From: kevin parker To: xen-users@lists.xen.org X-Mailman-Approved-At: Mon, 24 Sep 2012 16:47:01 +0000 Subject: [Xen-users] Creating guest in command mode failing when used in para mode X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============7801328455555760819==" Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org --===============7801328455555760819== Content-Type: multipart/alternative; boundary=e89a8f3ba96738f3fc04ca751d4f --e89a8f3ba96738f3fc04ca751d4f Content-Type: text/plain; charset=ISO-8859-1 Hi all, I am new to running xen in command mode.I have tried creating xen using virt-manager and its working ok.But i can not make it work using command line.For that i installed virt-install and run this command (trying to install *ubuntu 12.04 64 bit*) *parvirtulization:* virt-install --name vm1 --ram 512 --vcpus=1 *-p* --description=vm --location=/var/lib/libvirt/images/12.04.iso*(64 bit ubuntu)* --disk path=/VM/secondvm,size=1 but its returning Starting install... Retrieving file version.info... | 116 B 00:00 ... ERROR *Couldn't find xen kernel for Ubuntu tree*. but in * v *mode i am able to create vm. *fullvirt* virt-install --name secondvm --ram 512 --vcpus=1 *-v* --description=second-vm --location=/var/lib/libvirt/images/12.04.iso --disk path=/VM/secondvm,size=1 Starting install... Retrieving file version.info... | 116 B 00:00 ... Retrieving file linux... | 9.5 MB 00:00 ... Retrieving file initrd.gz... | 33 MB 00:00 ... Creating storage file secondvm | 1.0 GB 00:00 Creating domain... | 0 B 00:00 2012-09-24 22:01:27.810+0000: 5067: info : libvirt version: 0.9.8 2012-09-24 22:01:27.810+0000: 5067: warning : xenHypervisorMakeCapabilities:2751 : Failed to get host power management capabilities Connected to domain secondvm Escape character is ^] *Details* dom0:ubuntu 12.04 64 bit xen version: 4.1.2 Can any one tell me how to solve this also how can i get a graphical console for installing guest vm,like choosing partition type and swap. Expecting a reply, Kevin --e89a8f3ba96738f3fc04ca751d4f Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Hi all,
=A0 =A0 =A0 =A0 =A0I am new to running xen in command mode.I ha= ve tried creating xen using virt-manager and its working ok.But i can not m= ake it work using command line.For that i installed virt-install=A0
and run this command (trying=A0to install ubuntu 12.04 64 bit) parvirtulization:

virt-install --name vm1 -= -ram 512 --vcpus=3D1 -p --description=3Dvm --location=3D/var/lib/lib= virt/images/12.04.iso(64 bit ubuntu) --disk path=3D/VM/secondvm,size= =3D1=A0

but its returning=A0

Star= ting install...
Retrieving file version.info... =A0 =A0 =A0 =A0 = =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0= =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 = =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0| =A0116 B = =A0 =A0 00:00 ...
ERROR =A0 =A0Couldn't find xen kernel for Ubuntu tree.

but in =A0v mode i am able to create vm.<= /div>


fullvirt

virt-install --name secondvm --ram 512 --vcpus=3D1=A0-v=A0--descript= ion=3Dsecond-vm --location=3D/var/lib/libvirt/images/12.04.iso --disk path= =3D/VM/secondvm,size=3D1 =A0

Starting install= ...
Retrieving file version.info... =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0= =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 = =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0= =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0| =A0116 B =A0 =A0 00:00 ...
= Retrieving file linux... =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 = =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0= =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 = =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 | 9.5 MB =A0 =A0 00:00 ...
Retrieving file initrd.gz... =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 = =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0= =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 = =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 | =A033 MB =A0 =A0 00:00 ...
Creating storage file secondvm =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 = =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0= =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 = =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 | 1.0 GB =A0 =A0 00:00
Creating domain... =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0= =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 = =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0= =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 | =A0 =A00 B =A0 =A0 0= 0:00
2012-09-24 22:01:27.810+0000: 5067: info : libvirt version: = 0.9.8
2012-09-24 22:01:27.810+0000: 5067: warning : xenHypervisorMakeCapabil= ities:2751 : Failed to get host power management capabilities
Con= nected to domain secondvm
Escape character is ^]


Details=A0
dom0:ubuntu = 12.04 64 bit
xen version: 4.1.2
Can any one tell = me how to solve this also how can i get a graphical console for installing = guest vm,like choosing partition type and swap.

Expecting a reply,

Kevin
--e89a8f3ba96738f3fc04ca751d4f-- --===============7801328455555760819== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users --===============7801328455555760819==-- From xen-users-bounces@lists.xen.org Mon Sep 24 19:37:42 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Mon, 24 Sep 2012 19:37:42 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TGES5-0002zq-JK; Mon, 24 Sep 2012 19:36:21 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TGES4-0002zl-GM for xen-users@lists.xen.org; Mon, 24 Sep 2012 19:36:20 +0000 Received: from [85.158.139.83:60736] by server-10.bemta-5.messagelabs.com id 65/AC-16911-336B0605; Mon, 24 Sep 2012 19:36:19 +0000 X-Env-Sender: arvind.viswanathan@gmail.com X-Msg-Ref: server-2.tower-182.messagelabs.com!1348515378!29086291!1 X-Originating-IP: [209.85.217.173] X-SpamReason: No, hits=0.6 required=7.0 tests=HTML_60_70,HTML_MESSAGE, ML_RADAR_SPEW_LINKS_14,RCVD_BY_IP,spamassassin: X-StarScan-Received: X-StarScan-Version: 6.6.1.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 22383 invoked from network); 24 Sep 2012 19:36:19 -0000 Received: from mail-lb0-f173.google.com (HELO mail-lb0-f173.google.com) (209.85.217.173) by server-2.tower-182.messagelabs.com with RC4-SHA encrypted SMTP; 24 Sep 2012 19:36:19 -0000 Received: by lbbgm13 with SMTP id gm13so8954243lbb.32 for ; Mon, 24 Sep 2012 12:36:18 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:date:message-id:subject:from:to:content-type; bh=qB6J0B1g8yUNXFryJafdq1RWlyIJFutHxnOSlgUFAtg=; b=BHutngG7BozAyMmkmh5xf2aFVx7TgwvxrIdN5GEN8VxJUoFKImT2o9TT5fPdXXTmc2 kp9JttFAiv1yPiKQA+jYKD1sjpx5tqSgTgD1m/eIr0CuYkis++iMge5gquRVVG4KKKpV TfT7kYzs7ovR543kWrtK0rBq5ZIrg324arytC0MOY/HkFbQVCmSevEfT9InsLkd9/c3J LIKeeWDdOk1Edj66u9LLQNMhwMSlpXm0YvuSGjKTBQGw/2gql+LUlbzRHnrkzc3gi+k0 y7wCTaVcJNlpRoAfEgiEcGQbtU9aALLVheIJ4HNPzVhsWOD29mcpqcN4WF+iXC0q401t rfYw== MIME-Version: 1.0 Received: by 10.112.86.200 with SMTP id r8mr4760254lbz.87.1348515378205; Mon, 24 Sep 2012 12:36:18 -0700 (PDT) Received: by 10.112.43.198 with HTTP; Mon, 24 Sep 2012 12:36:18 -0700 (PDT) Date: Mon, 24 Sep 2012 12:36:18 -0700 Message-ID: From: arvind viswanathan To: xen-users@lists.xen.org Subject: [Xen-users] Open xen support for .vhd files X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============0132990458652284510==" Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org --===============0132990458652284510== Content-Type: multipart/alternative; boundary=f46d040172fd17935204ca77b494 --f46d040172fd17935204ca77b494 Content-Type: text/plain; charset=ISO-8859-1 Hi, I have a imported VM image in .raw format. I used "qemu-img convert" to convert the .raw image to a .vhd image. I changed the config file accordingly and I tried to start the VM. I am unable to bootup and I get the message that the "booting from hard disk failed" and no bootable device found. The image is not corrupt as .raw image seems to come up fine. Any suggestions on how to make it bootable ? Does open xen even support .vhd format ? Thanks Arvind --f46d040172fd17935204ca77b494 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Hi,

I have a imported VM image = in .raw format. I used "qemu-img convert" to convert the .raw ima= ge to a .vhd image. I changed the config file accordingly and I tried to st= art the VM. I am unable to bootup and I get the message that the "boot= ing from hard disk failed" and no bootable device found. The image is = not corrupt as .raw image seems to come up fine. Any suggestions on how to = make it bootable ? Does open xen even support .vhd format ?

Thanks
Arvind
--f46d040172fd17935204ca77b494-- --===============0132990458652284510== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users --===============0132990458652284510==-- From xen-users-bounces@lists.xen.org Mon Sep 24 19:37:42 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Mon, 24 Sep 2012 19:37:42 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TGES5-0002zq-JK; Mon, 24 Sep 2012 19:36:21 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TGES4-0002zl-GM for xen-users@lists.xen.org; Mon, 24 Sep 2012 19:36:20 +0000 Received: from [85.158.139.83:60736] by server-10.bemta-5.messagelabs.com id 65/AC-16911-336B0605; Mon, 24 Sep 2012 19:36:19 +0000 X-Env-Sender: arvind.viswanathan@gmail.com X-Msg-Ref: server-2.tower-182.messagelabs.com!1348515378!29086291!1 X-Originating-IP: [209.85.217.173] X-SpamReason: No, hits=0.6 required=7.0 tests=HTML_60_70,HTML_MESSAGE, ML_RADAR_SPEW_LINKS_14,RCVD_BY_IP,spamassassin: X-StarScan-Received: X-StarScan-Version: 6.6.1.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 22383 invoked from network); 24 Sep 2012 19:36:19 -0000 Received: from mail-lb0-f173.google.com (HELO mail-lb0-f173.google.com) (209.85.217.173) by server-2.tower-182.messagelabs.com with RC4-SHA encrypted SMTP; 24 Sep 2012 19:36:19 -0000 Received: by lbbgm13 with SMTP id gm13so8954243lbb.32 for ; Mon, 24 Sep 2012 12:36:18 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:date:message-id:subject:from:to:content-type; bh=qB6J0B1g8yUNXFryJafdq1RWlyIJFutHxnOSlgUFAtg=; b=BHutngG7BozAyMmkmh5xf2aFVx7TgwvxrIdN5GEN8VxJUoFKImT2o9TT5fPdXXTmc2 kp9JttFAiv1yPiKQA+jYKD1sjpx5tqSgTgD1m/eIr0CuYkis++iMge5gquRVVG4KKKpV TfT7kYzs7ovR543kWrtK0rBq5ZIrg324arytC0MOY/HkFbQVCmSevEfT9InsLkd9/c3J LIKeeWDdOk1Edj66u9LLQNMhwMSlpXm0YvuSGjKTBQGw/2gql+LUlbzRHnrkzc3gi+k0 y7wCTaVcJNlpRoAfEgiEcGQbtU9aALLVheIJ4HNPzVhsWOD29mcpqcN4WF+iXC0q401t rfYw== MIME-Version: 1.0 Received: by 10.112.86.200 with SMTP id r8mr4760254lbz.87.1348515378205; Mon, 24 Sep 2012 12:36:18 -0700 (PDT) Received: by 10.112.43.198 with HTTP; Mon, 24 Sep 2012 12:36:18 -0700 (PDT) Date: Mon, 24 Sep 2012 12:36:18 -0700 Message-ID: From: arvind viswanathan To: xen-users@lists.xen.org Subject: [Xen-users] Open xen support for .vhd files X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============0132990458652284510==" Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org --===============0132990458652284510== Content-Type: multipart/alternative; boundary=f46d040172fd17935204ca77b494 --f46d040172fd17935204ca77b494 Content-Type: text/plain; charset=ISO-8859-1 Hi, I have a imported VM image in .raw format. I used "qemu-img convert" to convert the .raw image to a .vhd image. I changed the config file accordingly and I tried to start the VM. I am unable to bootup and I get the message that the "booting from hard disk failed" and no bootable device found. The image is not corrupt as .raw image seems to come up fine. Any suggestions on how to make it bootable ? Does open xen even support .vhd format ? Thanks Arvind --f46d040172fd17935204ca77b494 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Hi,

I have a imported VM image = in .raw format. I used "qemu-img convert" to convert the .raw ima= ge to a .vhd image. I changed the config file accordingly and I tried to st= art the VM. I am unable to bootup and I get the message that the "boot= ing from hard disk failed" and no bootable device found. The image is = not corrupt as .raw image seems to come up fine. Any suggestions on how to = make it bootable ? Does open xen even support .vhd format ?

Thanks
Arvind
--f46d040172fd17935204ca77b494-- --===============0132990458652284510== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users --===============0132990458652284510==-- From xen-users-bounces@lists.xen.org Tue Sep 25 10:58:40 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Tue, 25 Sep 2012 10:58:40 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TGSp4-0005LG-2K; Tue, 25 Sep 2012 10:57:02 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TGSp2-0005Ke-AA for xen-users@lists.xen.org; Tue, 25 Sep 2012 10:57:00 +0000 Received: from [85.158.139.83:2485] by server-6.bemta-5.messagelabs.com id 09/52-14717-AFD81605; Tue, 25 Sep 2012 10:56:58 +0000 X-Env-Sender: lars.kurth.xen@gmail.com X-Msg-Ref: server-2.tower-182.messagelabs.com!1348570618!29182936!1 X-Originating-IP: [74.125.83.45] X-SpamReason: No, hits=0.3 required=7.0 tests=RCVD_BY_IP X-StarScan-Received: X-StarScan-Version: 6.6.1.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 14736 invoked from network); 25 Sep 2012 10:56:58 -0000 Received: from mail-ee0-f45.google.com (HELO mail-ee0-f45.google.com) (74.125.83.45) by server-2.tower-182.messagelabs.com with RC4-SHA encrypted SMTP; 25 Sep 2012 10:56:58 -0000 Received: by eekb47 with SMTP id b47so1052260eek.32 for ; Tue, 25 Sep 2012 03:56:58 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=sender:message-id:date:from:reply-to:user-agent:mime-version:to :subject:content-type:content-transfer-encoding; bh=Wpz1YTr79D0LTsK1sZB7lYaA1bWrLPrWrV8yAE991CU=; b=vseRFu1uSNOtf9x7j1adCKIILF8TDj4B58JR2XbiBpL+gXwR4kkbcCOXrIMjMjkU8i 3G5E0xNAcfWV3SLIWjEYHXhujJBQ4zeyZc7bxOYqT15cQMya+EU3o2eeu45Q3pgWLPuc U8QCfcsFtk8MbMtDJpymH2dKTpmx2b9hU9dedD/6MS0CIjvNkfECmeBJV6AFRya9ZcbY ytD8XyWDcNyFoefc/xwr2FeTHTAyPi7wb8HbvHN/n89vDblS2fiOXDIRU2Qpzj5qT4ls bpHkzKFv7pw9H2C3aavkT0XCIikeDm55r2ZeKvXSCn3PoZge8cgQaBBD1Gul1hDRJ7Wf 55LQ== Received: by 10.14.173.9 with SMTP id u9mr18719241eel.8.1348570618190; Tue, 25 Sep 2012 03:56:58 -0700 (PDT) Received: from [172.16.26.11] (b0fb5b35.bb.sky.com. [176.251.91.53]) by mx.google.com with ESMTPS id x13sm11540384bkv.16.2012.09.25.03.56.57 (version=SSLv3 cipher=OTHER); Tue, 25 Sep 2012 03:56:57 -0700 (PDT) Message-ID: <50618DF5.5070400@xen.org> Date: Tue, 25 Sep 2012 11:56:53 +0100 From: Lars Kurth User-Agent: Mozilla/5.0 (Windows NT 6.1; rv:15.0) Gecko/20120907 Thunderbird/15.0.1 MIME-Version: 1.0 To: "xen-devel@lists.xen.org" , xen-users@lists.xen.org, "xen-api@lists.xen.org" , xen-arm@lists.xen.org Subject: [Xen-users] Xen Document Day - Thank You! X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list Reply-To: lars.kurth@xen.org List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset="us-ascii"; Format="flowed" Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org Hi everybody, thank you for contributing to the Xen Document Day yesterday. I ran some stats, but may have missed some activities. Wiki Changes: 1) 27039 words were changed on the Wiki for the document day 2) Contributors: Anthony, Dunlapg, GrantMcWilliams, Ijc, Lars.kurth, Lisa.Nguyen, Matthew.Spah, OliverChick, StefanoStabellini Proposals: 1) A proposal by GrantMcWilliams to contribute xe man pages to the XCP codeline in xen.org (see http://lists.xen.org/archives/html/xen-api/2012-09/msg00053.html) 2) Additional requests for XL documentation by Matthias Blankenhaus for subsequent document days. I will add this proposal the Document Day TODO list. Matthias also volunteered to take ownership, but will need help. Other changes: 1) Capability to build diagrams from source as part of the xen-unstable docs build 2) Diagrams being created and included into the wiki 3) A number of content patches to docs in the codeline (did not count lines of code) on XenStore, Scheduler, Schedop* and Xen ARM DT bindings Thank you again for helping improve Xen Documentation. Best Regards Lars _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Tue Sep 25 10:58:40 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Tue, 25 Sep 2012 10:58:40 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TGSp4-0005LG-2K; Tue, 25 Sep 2012 10:57:02 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TGSp2-0005Ke-AA for xen-users@lists.xen.org; Tue, 25 Sep 2012 10:57:00 +0000 Received: from [85.158.139.83:2485] by server-6.bemta-5.messagelabs.com id 09/52-14717-AFD81605; Tue, 25 Sep 2012 10:56:58 +0000 X-Env-Sender: lars.kurth.xen@gmail.com X-Msg-Ref: server-2.tower-182.messagelabs.com!1348570618!29182936!1 X-Originating-IP: [74.125.83.45] X-SpamReason: No, hits=0.3 required=7.0 tests=RCVD_BY_IP X-StarScan-Received: X-StarScan-Version: 6.6.1.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 14736 invoked from network); 25 Sep 2012 10:56:58 -0000 Received: from mail-ee0-f45.google.com (HELO mail-ee0-f45.google.com) (74.125.83.45) by server-2.tower-182.messagelabs.com with RC4-SHA encrypted SMTP; 25 Sep 2012 10:56:58 -0000 Received: by eekb47 with SMTP id b47so1052260eek.32 for ; Tue, 25 Sep 2012 03:56:58 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=sender:message-id:date:from:reply-to:user-agent:mime-version:to :subject:content-type:content-transfer-encoding; bh=Wpz1YTr79D0LTsK1sZB7lYaA1bWrLPrWrV8yAE991CU=; b=vseRFu1uSNOtf9x7j1adCKIILF8TDj4B58JR2XbiBpL+gXwR4kkbcCOXrIMjMjkU8i 3G5E0xNAcfWV3SLIWjEYHXhujJBQ4zeyZc7bxOYqT15cQMya+EU3o2eeu45Q3pgWLPuc U8QCfcsFtk8MbMtDJpymH2dKTpmx2b9hU9dedD/6MS0CIjvNkfECmeBJV6AFRya9ZcbY ytD8XyWDcNyFoefc/xwr2FeTHTAyPi7wb8HbvHN/n89vDblS2fiOXDIRU2Qpzj5qT4ls bpHkzKFv7pw9H2C3aavkT0XCIikeDm55r2ZeKvXSCn3PoZge8cgQaBBD1Gul1hDRJ7Wf 55LQ== Received: by 10.14.173.9 with SMTP id u9mr18719241eel.8.1348570618190; Tue, 25 Sep 2012 03:56:58 -0700 (PDT) Received: from [172.16.26.11] (b0fb5b35.bb.sky.com. [176.251.91.53]) by mx.google.com with ESMTPS id x13sm11540384bkv.16.2012.09.25.03.56.57 (version=SSLv3 cipher=OTHER); Tue, 25 Sep 2012 03:56:57 -0700 (PDT) Message-ID: <50618DF5.5070400@xen.org> Date: Tue, 25 Sep 2012 11:56:53 +0100 From: Lars Kurth User-Agent: Mozilla/5.0 (Windows NT 6.1; rv:15.0) Gecko/20120907 Thunderbird/15.0.1 MIME-Version: 1.0 To: "xen-devel@lists.xen.org" , xen-users@lists.xen.org, "xen-api@lists.xen.org" , xen-arm@lists.xen.org Subject: [Xen-users] Xen Document Day - Thank You! X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list Reply-To: lars.kurth@xen.org List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset="us-ascii"; Format="flowed" Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org Hi everybody, thank you for contributing to the Xen Document Day yesterday. I ran some stats, but may have missed some activities. Wiki Changes: 1) 27039 words were changed on the Wiki for the document day 2) Contributors: Anthony, Dunlapg, GrantMcWilliams, Ijc, Lars.kurth, Lisa.Nguyen, Matthew.Spah, OliverChick, StefanoStabellini Proposals: 1) A proposal by GrantMcWilliams to contribute xe man pages to the XCP codeline in xen.org (see http://lists.xen.org/archives/html/xen-api/2012-09/msg00053.html) 2) Additional requests for XL documentation by Matthias Blankenhaus for subsequent document days. I will add this proposal the Document Day TODO list. Matthias also volunteered to take ownership, but will need help. Other changes: 1) Capability to build diagrams from source as part of the xen-unstable docs build 2) Diagrams being created and included into the wiki 3) A number of content patches to docs in the codeline (did not count lines of code) on XenStore, Scheduler, Schedop* and Xen ARM DT bindings Thank you again for helping improve Xen Documentation. Best Regards Lars _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Tue Sep 25 12:16:03 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Tue, 25 Sep 2012 12:16:03 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TGU2P-0007AT-C2; Tue, 25 Sep 2012 12:14:53 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TGDXK-0002Ve-7S for xen-users@lists.xen.org; Mon, 24 Sep 2012 18:37:42 +0000 Received: from [85.158.143.35:17883] by server-1.bemta-4.messagelabs.com id 0F/F4-05684-578A0605; Mon, 24 Sep 2012 18:37:41 +0000 X-Env-Sender: arvind.viswanathan@gmail.com X-Msg-Ref: server-8.tower-21.messagelabs.com!1348511860!12553056!1 X-Originating-IP: [209.85.217.173] X-SpamReason: No, hits=1.2 required=7.0 tests=HTML_20_30,HTML_MESSAGE, ML_RADAR_SPEW_LINKS_14,RCVD_BY_IP,spamassassin: X-StarScan-Received: X-StarScan-Version: 6.6.1.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 30821 invoked from network); 24 Sep 2012 18:37:40 -0000 Received: from mail-lb0-f173.google.com (HELO mail-lb0-f173.google.com) (209.85.217.173) by server-8.tower-21.messagelabs.com with RC4-SHA encrypted SMTP; 24 Sep 2012 18:37:40 -0000 Received: by lbbgm13 with SMTP id gm13so8856943lbb.32 for ; Mon, 24 Sep 2012 11:37:40 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:date:message-id:subject:from:to:content-type; bh=csseRppacVdae81mNfx+4bi8pXUmqmpSmLjlZilHQBE=; b=WuxYnt2YseZuC/PcEpU1cSbFgWTPLHyRwSWek64BLCGtGdQB/u/p+ufEBZJZ0nPhjF iMtcR5SDA5A7PWt3dDn7mcMyogaXg7oSCKXuMcu2dG9qXs6FcbRiBIxWUn2tnlfn/YcM ngTznhECLtEEWlwk+xXfOeq+hcgu3z4fcEBhqHFVTATiksffVLfU1XMeubS6ko1NbB52 y+ZX0h6XPTi2MyQIhBJGiRnjHU8WcBTQ2zRIX/mj1JhlqpQv6xhiMMyxgK7ASOs6HTkI Luopa7bssD6yAh7jWg8VloHPDfBhZYPrp2S6AgwuVgw9Cq7lHXCKZgcB/0xgq4tU5lDp Cl/Q== MIME-Version: 1.0 Received: by 10.112.86.105 with SMTP id o9mr4659567lbz.58.1348511860109; Mon, 24 Sep 2012 11:37:40 -0700 (PDT) Received: by 10.112.43.198 with HTTP; Mon, 24 Sep 2012 11:37:40 -0700 (PDT) Date: Mon, 24 Sep 2012 11:37:40 -0700 Message-ID: From: arvind viswanathan To: xen-users@lists.xen.org X-Mailman-Approved-At: Tue, 25 Sep 2012 12:14:53 +0000 Subject: [Xen-users] Having trouble booting with .vhd image X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============6995716568407774512==" Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org --===============6995716568407774512== Content-Type: multipart/alternative; boundary=bcaec554d4ec65b1ea04ca76e2ed --bcaec554d4ec65b1ea04ca76e2ed Content-Type: text/plain; charset=ISO-8859-1 Hi, I have a imported VM image in .raw format. I used "qemu-img convert" to convert the .raw image to a .vhd image. I changed the config file accordingly and I tried to start the VM. I am unable to bootup and I get the message that the "booting from hard disk failed" and no bootable device found. The image is not corrupt as .raw image seems to come up fine. Any suggestions on how to make it bootable ? Thanks Arvind --bcaec554d4ec65b1ea04ca76e2ed Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Hi,

I have a imported VM image in .raw format. I used &q= uot;qemu-img convert" to convert the .raw image to a .vhd image. I cha= nged the config file accordingly and I tried to start the VM. I am unable t= o bootup and I get the message that the "booting from hard disk failed= " and no bootable device found. The image is not corrupt as .raw image= seems to come up fine. Any suggestions on how to make it bootable ?

Thanks
Arvind


--bcaec554d4ec65b1ea04ca76e2ed-- --===============6995716568407774512== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users --===============6995716568407774512==-- From xen-users-bounces@lists.xen.org Tue Sep 25 12:16:03 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Tue, 25 Sep 2012 12:16:03 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TGU2P-0007AT-C2; Tue, 25 Sep 2012 12:14:53 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TGDXK-0002Ve-7S for xen-users@lists.xen.org; Mon, 24 Sep 2012 18:37:42 +0000 Received: from [85.158.143.35:17883] by server-1.bemta-4.messagelabs.com id 0F/F4-05684-578A0605; Mon, 24 Sep 2012 18:37:41 +0000 X-Env-Sender: arvind.viswanathan@gmail.com X-Msg-Ref: server-8.tower-21.messagelabs.com!1348511860!12553056!1 X-Originating-IP: [209.85.217.173] X-SpamReason: No, hits=1.2 required=7.0 tests=HTML_20_30,HTML_MESSAGE, ML_RADAR_SPEW_LINKS_14,RCVD_BY_IP,spamassassin: X-StarScan-Received: X-StarScan-Version: 6.6.1.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 30821 invoked from network); 24 Sep 2012 18:37:40 -0000 Received: from mail-lb0-f173.google.com (HELO mail-lb0-f173.google.com) (209.85.217.173) by server-8.tower-21.messagelabs.com with RC4-SHA encrypted SMTP; 24 Sep 2012 18:37:40 -0000 Received: by lbbgm13 with SMTP id gm13so8856943lbb.32 for ; Mon, 24 Sep 2012 11:37:40 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:date:message-id:subject:from:to:content-type; bh=csseRppacVdae81mNfx+4bi8pXUmqmpSmLjlZilHQBE=; b=WuxYnt2YseZuC/PcEpU1cSbFgWTPLHyRwSWek64BLCGtGdQB/u/p+ufEBZJZ0nPhjF iMtcR5SDA5A7PWt3dDn7mcMyogaXg7oSCKXuMcu2dG9qXs6FcbRiBIxWUn2tnlfn/YcM ngTznhECLtEEWlwk+xXfOeq+hcgu3z4fcEBhqHFVTATiksffVLfU1XMeubS6ko1NbB52 y+ZX0h6XPTi2MyQIhBJGiRnjHU8WcBTQ2zRIX/mj1JhlqpQv6xhiMMyxgK7ASOs6HTkI Luopa7bssD6yAh7jWg8VloHPDfBhZYPrp2S6AgwuVgw9Cq7lHXCKZgcB/0xgq4tU5lDp Cl/Q== MIME-Version: 1.0 Received: by 10.112.86.105 with SMTP id o9mr4659567lbz.58.1348511860109; Mon, 24 Sep 2012 11:37:40 -0700 (PDT) Received: by 10.112.43.198 with HTTP; Mon, 24 Sep 2012 11:37:40 -0700 (PDT) Date: Mon, 24 Sep 2012 11:37:40 -0700 Message-ID: From: arvind viswanathan To: xen-users@lists.xen.org X-Mailman-Approved-At: Tue, 25 Sep 2012 12:14:53 +0000 Subject: [Xen-users] Having trouble booting with .vhd image X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============6995716568407774512==" Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org --===============6995716568407774512== Content-Type: multipart/alternative; boundary=bcaec554d4ec65b1ea04ca76e2ed --bcaec554d4ec65b1ea04ca76e2ed Content-Type: text/plain; charset=ISO-8859-1 Hi, I have a imported VM image in .raw format. I used "qemu-img convert" to convert the .raw image to a .vhd image. I changed the config file accordingly and I tried to start the VM. I am unable to bootup and I get the message that the "booting from hard disk failed" and no bootable device found. The image is not corrupt as .raw image seems to come up fine. Any suggestions on how to make it bootable ? Thanks Arvind --bcaec554d4ec65b1ea04ca76e2ed Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Hi,

I have a imported VM image in .raw format. I used &q= uot;qemu-img convert" to convert the .raw image to a .vhd image. I cha= nged the config file accordingly and I tried to start the VM. I am unable t= o bootup and I get the message that the "booting from hard disk failed= " and no bootable device found. The image is not corrupt as .raw image= seems to come up fine. Any suggestions on how to make it bootable ?

Thanks
Arvind


--bcaec554d4ec65b1ea04ca76e2ed-- --===============6995716568407774512== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users --===============6995716568407774512==-- From xen-users-bounces@lists.xen.org Tue Sep 25 13:43:28 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Tue, 25 Sep 2012 13:43:28 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TGVP0-0000FD-Nu; Tue, 25 Sep 2012 13:42:18 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TGVOz-0000F2-9Z for xen-users@lists.xen.org; Tue, 25 Sep 2012 13:42:17 +0000 Received: from [85.158.138.51:47278] by server-8.bemta-3.messagelabs.com id C1/19-24700-8B4B1605; Tue, 25 Sep 2012 13:42:16 +0000 X-Env-Sender: jh@excello.cz X-Msg-Ref: server-5.tower-174.messagelabs.com!1348580535!31994389!1 X-Originating-IP: [81.31.35.100] X-SpamReason: No, hits=0.0 required=7.0 tests=UNPARSEABLE_RELAY X-StarScan-Received: X-StarScan-Version: 6.6.1.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 14379 invoked from network); 25 Sep 2012 13:42:15 -0000 Received: from out2.virusfree.cz (HELO out2.virusfree.cz) (81.31.35.100) by server-5.tower-174.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 25 Sep 2012 13:42:15 -0000 Received: (qmail 25848 invoked by uid 1000); 25 Sep 2012 15:42:14 +0200 Received: from smtp.excello.cz by out2 (envelope-from , uid 201) with VF-scanner-2.08VF (www.virusfree.cz : out2.virusfree.cz Clear:RC:1(91.121.238.113):SA:0(-14.3/5.0):. Processed in 3.693445 secs); 25 Sep 2012 13:42:14 -0000 X-Spam-Status: No, hits=-14.3 required=5.0 X-Spam-Report: SA TESTS -0.0 SPF_PASS SPF: sender matches SPF record -0.6 RP_MATCHES_RCVD Envelope sender domain matches handover relay domain 1.0 SPF_HELO_FAIL SPF: HELO does not match SPF record (fail) [SPF failed: Please see http://www.openspf.net/Why?s=helo; id=smtp.excello.cz; ip=91.121.238.113; r=dq.spamfree.cz] 0.8 BAYES_50 BODY: Bayes spam probability is 40 to 60% [score: 0.5035] -2.0 MFH_PKCS7_4 FULL: S/MIME Header -0.1 DKIM_VALID_AU Message has a valid DKIM or DK signature from author's domain -0.1 DKIM_VALID Message has at least one valid DKIM or DK signature 0.1 DKIM_SIGNED Message has a DKIM or DK signature, not necessarily valid -13 CRM114_CHECK CRM114: message is GOOD with crm114-score 53.8200 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=excello.cz; h= date:message-id:from:to:subject:reply-to; q=dns/txt; s=default; t=1348580530; n=Test; bh=C5hsuDoSOgmq9Jgs+ACPh7FzhaUCGbqEblIipc vmqQ0=; b=RiIlmG/Y8sUkFKvqpVh+Dl3A87kg8Lla+RF83eJR081kWEE6b7HViS BSjihJCe+az7+uM5jcxRFZtk48Q02pV/3KzcUdJfK5ySZaPUH0uiEs7KxnLWkSDa GVUBU3DDsI DomainKey-Signature: a=rsa-sha1; c=nofws; d=excello.cz; h=message-id :date:from:mime-version:to:subject:content-type; q=dns; s= default; b=RE0cELJUGzSCP0yi5HR5NZWRIkfvBRIFXzxHDqRVrCg7Q/SDssP8v 7GUf61olR14naEBlskHx0SeYip2V3ecCEpyaWfpEV8knS7snOgJkLig9Ixfo0NX+ bduQ0UbUAN2 Received: from smtp.excello.cz (91.121.238.113) by out2.virusfree.cz with SMTP; 25 Sep 2012 15:42:09 +0200 Received: from [192.168.2.2] (unknown [212.80.95.150]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by smtp.excello.cz (Postfix) with ESMTPSA id 2F65281359B6 for ; Tue, 25 Sep 2012 15:42:09 +0200 (CEST) Message-ID: <5061B4B1.6020104@excello.cz> Date: Tue, 25 Sep 2012 15:42:09 +0200 From: Jan Hejl User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:15.0) Gecko/20120827 Thunderbird/15.0 MIME-Version: 1.0 To: xen-users@lists.xen.org Subject: [Xen-users] Auto CPU pinning for domUs X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============2640791109350789978==" Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org Toto je elektronicky podepsana zprava ve formatu MIME. --===============2640791109350789978== Content-Type: multipart/signed; protocol="application/pkcs7-signature"; micalg=sha1; boundary="------------ms090904030208020903050408" Toto je elektronicky podepsana zprava ve formatu MIME. --------------ms090904030208020903050408 Content-Type: text/plain; charset=ISO-8859-2; format=flowed Content-Transfer-Encoding: quoted-printable Hello Xen users, i'm using Xen 4.1.2 on Gentoo Hardened and i'm stucked with one thing.=20 After starting my domUs, i would like to have them pinned to specified=20 CPU cores. I'm using this config file: kernel =3D "hvmloader" builder=3D'hvm' memory =3D 2048 name =3D "VirusfreeDB" vcpus=3D4 cpus=3D"16-19" acpi=3D1 apic=3D0 vif =3D [ 'bridge=3Dxenbr0, script=3Dvif-bridge, type=3Dioemu, model=3De1= 000, mac=3D00:16:3e:63:90:aa' ] disk =3D [ 'phy:/dev/vg/VirusfreeDB,hda,w', ',hdc:cdrom,r' ] on_poweroff =3D 'destroy' on_reboot =3D 'restart' on_crash =3D 'restart' device_model =3D 'qemu-dm' boot=3D"dc" sdl=3D0 opengl=3D0 vnc=3D1 vnclisten=3D"127.0.0.1" vncpasswd=3D'' stdvga=3D0 serial=3D'pty' tsc_mode=3D0 xen_platform_pci=3D0 so I suppose that it should be pinned to CPUs 16 to 19. But in 'xl=20 vcpu-list' is 'Any CPU', thus i have to do this manually with 'xl=20 vcpu-pin' command. Is there any way to do this automaticaly? Or am I=20 doing something wrong? Let me know if you need any other information, I'm new here. Thank you Jan Hejl --------------ms090904030208020903050408 Content-Type: application/pkcs7-signature; name="smime.p7s" Content-Transfer-Encoding: base64 Content-Disposition: attachment; filename="smime.p7s" Content-Description: Elektronicky podpis S/MIME MIAGCSqGSIb3DQEHAqCAMIACAQExCzAJBgUrDgMCGgUAMIAGCSqGSIb3DQEHAQAAoIIMOzCC BUUwggQtoAMCAQICEBT4W4g+LpxVCvoVs2BeaAUwDQYJKoZIhvcNAQEFBQAwgd0xCzAJBgNV BAYTAlVTMRcwFQYDVQQKEw5WZXJpU2lnbiwgSW5jLjEfMB0GA1UECxMWVmVyaVNpZ24gVHJ1 c3QgTmV0d29yazE7MDkGA1UECxMyVGVybXMgb2YgdXNlIGF0IGh0dHBzOi8vd3d3LnZlcmlz aWduLmNvbS9ycGEgKGMpMDkxHjAcBgNVBAsTFVBlcnNvbmEgTm90IFZhbGlkYXRlZDE3MDUG A1UEAxMuVmVyaVNpZ24gQ2xhc3MgMSBJbmRpdmlkdWFsIFN1YnNjcmliZXIgQ0EgLSBHMzAe Fw0xMjA4MjEwMDAwMDBaFw0xMzA4MjEyMzU5NTlaMIIBCDEXMBUGA1UEChMOVmVyaVNpZ24s IEluYy4xHzAdBgNVBAsTFlZlcmlTaWduIFRydXN0IE5ldHdvcmsxRjBEBgNVBAsTPXd3dy52 ZXJpc2lnbi5jb20vcmVwb3NpdG9yeS9SUEEgSW5jb3JwLiBieSBSZWYuLExJQUIuTFREKGMp OTgxHjAcBgNVBAsTFVBlcnNvbmEgTm90IFZhbGlkYXRlZDEzMDEGA1UECxMqRGlnaXRhbCBJ RCBDbGFzcyAxIC0gTmV0c2NhcGUgRnVsbCBTZXJ2aWNlMREwDwYDVQQDFAhKYW4gSGVqbDEc MBoGCSqGSIb3DQEJARYNamhAZXhjZWxsby5jejCCASIwDQYJKoZIhvcNAQEBBQADggEPADCC AQoCggEBAKZYfrag8UJ0JgrVdujHsmcxbgdXnbVZuWxIuJ6rY9Y3JBUfOTRODhMkaoxQDYTq pzG/JUNNZW1nF6QIYuPMcwzhEWAfoWhnhvm03KohNVKNID3A1SghW8bV3mRtaoyFHSIfiiFF DH7+BvSsIXP8slIzBi4wXvidDw1ui0MVA6Wy0mSSHLZdGHOpO8CswWXK6YQ87nG7a28QTCi6 HycFwbdhsPm4NADD7zrqnRkLVmWdnZWpA6CHkngGuR+0LpovAlmyiKUMLK4GkMOIMz24Pawk icIGI/AqrUmYpj8IwM4F0BGI1O1rZSUK72SV11eRuriqskzpcY1FVW0VmR1XNg0CAwEAAaOB 0jCBzzAJBgNVHRMEAjAAMEQGA1UdIAQ9MDswOQYLYIZIAYb4RQEHFwEwKjAoBggrBgEFBQcC ARYcaHR0cHM6Ly93d3cudmVyaXNpZ24uY29tL3JwYTALBgNVHQ8EBAMCBaAwHQYDVR0lBBYw FAYIKwYBBQUHAwQGCCsGAQUFBwMCMFAGA1UdHwRJMEcwRaBDoEGGP2h0dHA6Ly9pbmRjMWRp Z2l0YWxpZC1nMy1jcmwudmVyaXNpZ24uY29tL0luZEMxRGlnaXRhbElELUczLmNybDANBgkq hkiG9w0BAQUFAAOCAQEAh/RUK66OYfOqJdnHSSP5U+FpIFb+Wd6Xb03Yca7Shq3G1xHdKosm WK8+MAYg1FwlpVLf3Y7lg5QbPoplGchUC5QFa1xzJc88Pxrd0kYIDdshxd2HyNWhBCLdKPPU iU10VzwFZ6mR7/nD0pWv0mxyrNd+f+BU7mM1mOQsr+GvHpWCStlPxUrQBXKKH1hcCS8NWIXU M3WXQSXWyYCEhmu0/m220BPFRjJL39nwCALgZ+LlDJHaM65hmZ4VXO75YWWjOHpuJMNJZE65 nhXX2x5my+TzazAe9z5Xxly3ZWZ2iCQP6GbGduGMGVkS2V8Y6fpFUEcqx3nucCqM7Jnf5Sfn xjCCBu4wggXWoAMCAQICEHEVZgVK5JEhTem8RPms09wwDQYJKoZIhvcNAQEFBQAwgcoxCzAJ BgNVBAYTAlVTMRcwFQYDVQQKEw5WZXJpU2lnbiwgSW5jLjEfMB0GA1UECxMWVmVyaVNpZ24g VHJ1c3QgTmV0d29yazE6MDgGA1UECxMxKGMpIDE5OTkgVmVyaVNpZ24sIEluYy4gLSBGb3Ig YXV0aG9yaXplZCB1c2Ugb25seTFFMEMGA1UEAxM8VmVyaVNpZ24gQ2xhc3MgMSBQdWJsaWMg UHJpbWFyeSBDZXJ0aWZpY2F0aW9uIEF1dGhvcml0eSAtIEczMB4XDTA5MDUwMTAwMDAwMFoX DTE5MDQzMDIzNTk1OVowgd0xCzAJBgNVBAYTAlVTMRcwFQYDVQQKEw5WZXJpU2lnbiwgSW5j LjEfMB0GA1UECxMWVmVyaVNpZ24gVHJ1c3QgTmV0d29yazE7MDkGA1UECxMyVGVybXMgb2Yg dXNlIGF0IGh0dHBzOi8vd3d3LnZlcmlzaWduLmNvbS9ycGEgKGMpMDkxHjAcBgNVBAsTFVBl cnNvbmEgTm90IFZhbGlkYXRlZDE3MDUGA1UEAxMuVmVyaVNpZ24gQ2xhc3MgMSBJbmRpdmlk dWFsIFN1YnNjcmliZXIgQ0EgLSBHMzCCASIwDQYJKoZIhvcNAQEBBQADggEPADCCAQoCggEB AO3ER98qKB18Bmu71yEyyWwTj+mxjUFONPfaC+Nq+mWIIAsRE+mb4ElOi2/VAdBfDUeRilpM dD4/xpEJu0w0no1uoYJRYvdpdliWB6+eFBgHT1q9n9IxslQZc0ZqGUIR7BJzIY313DDN5dlW CjHFNm0pFJe9LdqJRxmI2EsEPeu2PGcedAATDdCG2pNn+DMDrho8a2l49sAsjuGDP3f5mf/+ n1JawrSHCthsqUfBVCllQz5KwJYfwa33d69ssQRevsG2lC2XkC0n0rse6YNqhPbEsq4jBmUm pSdYKwcitG+mYkgad/LVUCeaKdOW+yj1uiR2YuOMWev7btVCxL5Bx/UCAwEAAaOCArkwggK1 MDQGCCsGAQUFBwEBBCgwJjAkBggrBgEFBQcwAYYYaHR0cDovL29jc3AudmVyaXNpZ24uY29t MBIGA1UdEwEB/wQIMAYBAf8CAQAwcAYDVR0gBGkwZzBlBgtghkgBhvhFAQcXATBWMCgGCCsG AQUFBwIBFhxodHRwczovL3d3dy52ZXJpc2lnbi5jb20vY3BzMCoGCCsGAQUFBwICMB4aHGh0 dHBzOi8vd3d3LnZlcmlzaWduLmNvbS9ycGEwNAYDVR0fBC0wKzApoCegJYYjaHR0cDovL2Ny bC52ZXJpc2lnbi5jb20vcGNhMS1nMy5jcmwwDgYDVR0PAQH/BAQDAgEGMG4GCCsGAQUFBwEM BGIwYKFeoFwwWjBYMFYWCWltYWdlL2dpZjAhMB8wBwYFKw4DAhoEFEtruSiWBgy70FI4myms SweLIQUYMCYWJGh0dHA6Ly9sb2dvLnZlcmlzaWduLmNvbS92c2xvZ28xLmdpZjAuBgNVHREE JzAlpCMwITEfMB0GA1UEAxMWUHJpdmF0ZUxhYmVsNC0yMDQ4LTExODAdBgNVHQ4EFgQUeUdh CEH9OASiS+e1zPVD9kkrEfgwgfEGA1UdIwSB6TCB5qGB0KSBzTCByjELMAkGA1UEBhMCVVMx FzAVBgNVBAoTDlZlcmlTaWduLCBJbmMuMR8wHQYDVQQLExZWZXJpU2lnbiBUcnVzdCBOZXR3 b3JrMTowOAYDVQQLEzEoYykgMTk5OSBWZXJpU2lnbiwgSW5jLiAtIEZvciBhdXRob3JpemVk IHVzZSBvbmx5MUUwQwYDVQQDEzxWZXJpU2lnbiBDbGFzcyAxIFB1YmxpYyBQcmltYXJ5IENl cnRpZmljYXRpb24gQXV0aG9yaXR5IC0gRzOCEQCLW3VWhFSFCwDPrzhIzrGkMA0GCSqGSIb3 DQEBBQUAA4IBAQA5Tc9BmYG1qQW1UjjpOYSJbOQ0qFrn2GwJTCQaulmkhztzIfGTgc+/aGNa Z/41hSuhw12jSsI6Gd0w1sxN7/HSgZfKVFpDvzeLeo4ZjQ9DqIzyr2CzFYqzlZw84J6zJ5ik NXIX5fwqXYfTig3C0UUq+MD0rCqTOtWuEnAI6/s74nfs6CtkNXbNutrg0csU1nFYm77VPn22 2egkxSRmTF2RH3azFz5/DcYhiS+zN7ih/1yybUneZVJC+w6I0u1KHb9L4/jMcvpIDmWOScjW +JmYO7eUPjFxBof6bFlTLtffK+1fYwCsFe0DuFUWjMZoA+ciqHMLsbyg2lJY3QoOf8GCMYIE +TCCBPUCAQEwgfIwgd0xCzAJBgNVBAYTAlVTMRcwFQYDVQQKEw5WZXJpU2lnbiwgSW5jLjEf MB0GA1UECxMWVmVyaVNpZ24gVHJ1c3QgTmV0d29yazE7MDkGA1UECxMyVGVybXMgb2YgdXNl IGF0IGh0dHBzOi8vd3d3LnZlcmlzaWduLmNvbS9ycGEgKGMpMDkxHjAcBgNVBAsTFVBlcnNv bmEgTm90IFZhbGlkYXRlZDE3MDUGA1UEAxMuVmVyaVNpZ24gQ2xhc3MgMSBJbmRpdmlkdWFs IFN1YnNjcmliZXIgQ0EgLSBHMwIQFPhbiD4unFUK+hWzYF5oBTAJBgUrDgMCGgUAoIIC2zAY BgkqhkiG9w0BCQMxCwYJKoZIhvcNAQcBMBwGCSqGSIb3DQEJBTEPFw0xMjA5MjUxMzQyMDla MCMGCSqGSIb3DQEJBDEWBBQnkOoS3efiDsq//Tl/Y1IW5hI3jDBsBgkqhkiG9w0BCQ8xXzBd MAsGCWCGSAFlAwQBKjALBglghkgBZQMEAQIwCgYIKoZIhvcNAwcwDgYIKoZIhvcNAwICAgCA MA0GCCqGSIb3DQMCAgFAMAcGBSsOAwIHMA0GCCqGSIb3DQMCAgEoMIIBAwYJKwYBBAGCNxAE MYH1MIHyMIHdMQswCQYDVQQGEwJVUzEXMBUGA1UEChMOVmVyaVNpZ24sIEluYy4xHzAdBgNV BAsTFlZlcmlTaWduIFRydXN0IE5ldHdvcmsxOzA5BgNVBAsTMlRlcm1zIG9mIHVzZSBhdCBo dHRwczovL3d3dy52ZXJpc2lnbi5jb20vcnBhIChjKTA5MR4wHAYDVQQLExVQZXJzb25hIE5v dCBWYWxpZGF0ZWQxNzA1BgNVBAMTLlZlcmlTaWduIENsYXNzIDEgSW5kaXZpZHVhbCBTdWJz Y3JpYmVyIENBIC0gRzMCEBT4W4g+LpxVCvoVs2BeaAUwggEFBgsqhkiG9w0BCRACCzGB9aCB 8jCB3TELMAkGA1UEBhMCVVMxFzAVBgNVBAoTDlZlcmlTaWduLCBJbmMuMR8wHQYDVQQLExZW ZXJpU2lnbiBUcnVzdCBOZXR3b3JrMTswOQYDVQQLEzJUZXJtcyBvZiB1c2UgYXQgaHR0cHM6 Ly93d3cudmVyaXNpZ24uY29tL3JwYSAoYykwOTEeMBwGA1UECxMVUGVyc29uYSBOb3QgVmFs aWRhdGVkMTcwNQYDVQQDEy5WZXJpU2lnbiBDbGFzcyAxIEluZGl2aWR1YWwgU3Vic2NyaWJl ciBDQSAtIEczAhAU+FuIPi6cVQr6FbNgXmgFMA0GCSqGSIb3DQEBAQUABIIBAEb4PPa6yWgk KTRV4LNSvHl3ba1mrkg8jr602R5AEoyxI7s3FS0iDbuX06Jp3nqyVMKKRFrspTIc2r5rn0ZG rtbYiHs8MTcw0KC6Vgc8KtC1RYk2JscIAShPdkZCF7kMue0s/+komyIOI9p9YdHnaqobwzse b65xfTqQITnwbo6ZeLAoS5T1IlZtaKLvuKLzOTch6Wr4Aj+Utpy0u5gry1iUSxZXp+BDnqX6 U8g5n2hqPhJ2GMrLX4bbV1PE273BwthDOuVquvYz1KKFTsODPZA1EaKPdjpIEOWlafnGU3sh Wq9UkJJ18SfynyokKCkTMhO3u9EiW+iWXfB18wuPP4EAAAAAAAA= --------------ms090904030208020903050408-- --===============2640791109350789978== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users --===============2640791109350789978==-- From xen-users-bounces@lists.xen.org Tue Sep 25 13:43:28 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Tue, 25 Sep 2012 13:43:28 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TGVP0-0000FD-Nu; Tue, 25 Sep 2012 13:42:18 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TGVOz-0000F2-9Z for xen-users@lists.xen.org; Tue, 25 Sep 2012 13:42:17 +0000 Received: from [85.158.138.51:47278] by server-8.bemta-3.messagelabs.com id C1/19-24700-8B4B1605; Tue, 25 Sep 2012 13:42:16 +0000 X-Env-Sender: jh@excello.cz X-Msg-Ref: server-5.tower-174.messagelabs.com!1348580535!31994389!1 X-Originating-IP: [81.31.35.100] X-SpamReason: No, hits=0.0 required=7.0 tests=UNPARSEABLE_RELAY X-StarScan-Received: X-StarScan-Version: 6.6.1.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 14379 invoked from network); 25 Sep 2012 13:42:15 -0000 Received: from out2.virusfree.cz (HELO out2.virusfree.cz) (81.31.35.100) by server-5.tower-174.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 25 Sep 2012 13:42:15 -0000 Received: (qmail 25848 invoked by uid 1000); 25 Sep 2012 15:42:14 +0200 Received: from smtp.excello.cz by out2 (envelope-from , uid 201) with VF-scanner-2.08VF (www.virusfree.cz : out2.virusfree.cz Clear:RC:1(91.121.238.113):SA:0(-14.3/5.0):. Processed in 3.693445 secs); 25 Sep 2012 13:42:14 -0000 X-Spam-Status: No, hits=-14.3 required=5.0 X-Spam-Report: SA TESTS -0.0 SPF_PASS SPF: sender matches SPF record -0.6 RP_MATCHES_RCVD Envelope sender domain matches handover relay domain 1.0 SPF_HELO_FAIL SPF: HELO does not match SPF record (fail) [SPF failed: Please see http://www.openspf.net/Why?s=helo; id=smtp.excello.cz; ip=91.121.238.113; r=dq.spamfree.cz] 0.8 BAYES_50 BODY: Bayes spam probability is 40 to 60% [score: 0.5035] -2.0 MFH_PKCS7_4 FULL: S/MIME Header -0.1 DKIM_VALID_AU Message has a valid DKIM or DK signature from author's domain -0.1 DKIM_VALID Message has at least one valid DKIM or DK signature 0.1 DKIM_SIGNED Message has a DKIM or DK signature, not necessarily valid -13 CRM114_CHECK CRM114: message is GOOD with crm114-score 53.8200 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=excello.cz; h= date:message-id:from:to:subject:reply-to; q=dns/txt; s=default; t=1348580530; n=Test; bh=C5hsuDoSOgmq9Jgs+ACPh7FzhaUCGbqEblIipc vmqQ0=; b=RiIlmG/Y8sUkFKvqpVh+Dl3A87kg8Lla+RF83eJR081kWEE6b7HViS BSjihJCe+az7+uM5jcxRFZtk48Q02pV/3KzcUdJfK5ySZaPUH0uiEs7KxnLWkSDa GVUBU3DDsI DomainKey-Signature: a=rsa-sha1; c=nofws; d=excello.cz; h=message-id :date:from:mime-version:to:subject:content-type; q=dns; s= default; b=RE0cELJUGzSCP0yi5HR5NZWRIkfvBRIFXzxHDqRVrCg7Q/SDssP8v 7GUf61olR14naEBlskHx0SeYip2V3ecCEpyaWfpEV8knS7snOgJkLig9Ixfo0NX+ bduQ0UbUAN2 Received: from smtp.excello.cz (91.121.238.113) by out2.virusfree.cz with SMTP; 25 Sep 2012 15:42:09 +0200 Received: from [192.168.2.2] (unknown [212.80.95.150]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by smtp.excello.cz (Postfix) with ESMTPSA id 2F65281359B6 for ; Tue, 25 Sep 2012 15:42:09 +0200 (CEST) Message-ID: <5061B4B1.6020104@excello.cz> Date: Tue, 25 Sep 2012 15:42:09 +0200 From: Jan Hejl User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:15.0) Gecko/20120827 Thunderbird/15.0 MIME-Version: 1.0 To: xen-users@lists.xen.org Subject: [Xen-users] Auto CPU pinning for domUs X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============2640791109350789978==" Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org Toto je elektronicky podepsana zprava ve formatu MIME. --===============2640791109350789978== Content-Type: multipart/signed; protocol="application/pkcs7-signature"; micalg=sha1; boundary="------------ms090904030208020903050408" Toto je elektronicky podepsana zprava ve formatu MIME. --------------ms090904030208020903050408 Content-Type: text/plain; charset=ISO-8859-2; format=flowed Content-Transfer-Encoding: quoted-printable Hello Xen users, i'm using Xen 4.1.2 on Gentoo Hardened and i'm stucked with one thing.=20 After starting my domUs, i would like to have them pinned to specified=20 CPU cores. I'm using this config file: kernel =3D "hvmloader" builder=3D'hvm' memory =3D 2048 name =3D "VirusfreeDB" vcpus=3D4 cpus=3D"16-19" acpi=3D1 apic=3D0 vif =3D [ 'bridge=3Dxenbr0, script=3Dvif-bridge, type=3Dioemu, model=3De1= 000, mac=3D00:16:3e:63:90:aa' ] disk =3D [ 'phy:/dev/vg/VirusfreeDB,hda,w', ',hdc:cdrom,r' ] on_poweroff =3D 'destroy' on_reboot =3D 'restart' on_crash =3D 'restart' device_model =3D 'qemu-dm' boot=3D"dc" sdl=3D0 opengl=3D0 vnc=3D1 vnclisten=3D"127.0.0.1" vncpasswd=3D'' stdvga=3D0 serial=3D'pty' tsc_mode=3D0 xen_platform_pci=3D0 so I suppose that it should be pinned to CPUs 16 to 19. But in 'xl=20 vcpu-list' is 'Any CPU', thus i have to do this manually with 'xl=20 vcpu-pin' command. Is there any way to do this automaticaly? Or am I=20 doing something wrong? Let me know if you need any other information, I'm new here. Thank you Jan Hejl --------------ms090904030208020903050408 Content-Type: application/pkcs7-signature; name="smime.p7s" Content-Transfer-Encoding: base64 Content-Disposition: attachment; filename="smime.p7s" Content-Description: Elektronicky podpis S/MIME MIAGCSqGSIb3DQEHAqCAMIACAQExCzAJBgUrDgMCGgUAMIAGCSqGSIb3DQEHAQAAoIIMOzCC BUUwggQtoAMCAQICEBT4W4g+LpxVCvoVs2BeaAUwDQYJKoZIhvcNAQEFBQAwgd0xCzAJBgNV BAYTAlVTMRcwFQYDVQQKEw5WZXJpU2lnbiwgSW5jLjEfMB0GA1UECxMWVmVyaVNpZ24gVHJ1 c3QgTmV0d29yazE7MDkGA1UECxMyVGVybXMgb2YgdXNlIGF0IGh0dHBzOi8vd3d3LnZlcmlz aWduLmNvbS9ycGEgKGMpMDkxHjAcBgNVBAsTFVBlcnNvbmEgTm90IFZhbGlkYXRlZDE3MDUG A1UEAxMuVmVyaVNpZ24gQ2xhc3MgMSBJbmRpdmlkdWFsIFN1YnNjcmliZXIgQ0EgLSBHMzAe Fw0xMjA4MjEwMDAwMDBaFw0xMzA4MjEyMzU5NTlaMIIBCDEXMBUGA1UEChMOVmVyaVNpZ24s IEluYy4xHzAdBgNVBAsTFlZlcmlTaWduIFRydXN0IE5ldHdvcmsxRjBEBgNVBAsTPXd3dy52 ZXJpc2lnbi5jb20vcmVwb3NpdG9yeS9SUEEgSW5jb3JwLiBieSBSZWYuLExJQUIuTFREKGMp OTgxHjAcBgNVBAsTFVBlcnNvbmEgTm90IFZhbGlkYXRlZDEzMDEGA1UECxMqRGlnaXRhbCBJ RCBDbGFzcyAxIC0gTmV0c2NhcGUgRnVsbCBTZXJ2aWNlMREwDwYDVQQDFAhKYW4gSGVqbDEc MBoGCSqGSIb3DQEJARYNamhAZXhjZWxsby5jejCCASIwDQYJKoZIhvcNAQEBBQADggEPADCC AQoCggEBAKZYfrag8UJ0JgrVdujHsmcxbgdXnbVZuWxIuJ6rY9Y3JBUfOTRODhMkaoxQDYTq pzG/JUNNZW1nF6QIYuPMcwzhEWAfoWhnhvm03KohNVKNID3A1SghW8bV3mRtaoyFHSIfiiFF DH7+BvSsIXP8slIzBi4wXvidDw1ui0MVA6Wy0mSSHLZdGHOpO8CswWXK6YQ87nG7a28QTCi6 HycFwbdhsPm4NADD7zrqnRkLVmWdnZWpA6CHkngGuR+0LpovAlmyiKUMLK4GkMOIMz24Pawk icIGI/AqrUmYpj8IwM4F0BGI1O1rZSUK72SV11eRuriqskzpcY1FVW0VmR1XNg0CAwEAAaOB 0jCBzzAJBgNVHRMEAjAAMEQGA1UdIAQ9MDswOQYLYIZIAYb4RQEHFwEwKjAoBggrBgEFBQcC ARYcaHR0cHM6Ly93d3cudmVyaXNpZ24uY29tL3JwYTALBgNVHQ8EBAMCBaAwHQYDVR0lBBYw FAYIKwYBBQUHAwQGCCsGAQUFBwMCMFAGA1UdHwRJMEcwRaBDoEGGP2h0dHA6Ly9pbmRjMWRp Z2l0YWxpZC1nMy1jcmwudmVyaXNpZ24uY29tL0luZEMxRGlnaXRhbElELUczLmNybDANBgkq hkiG9w0BAQUFAAOCAQEAh/RUK66OYfOqJdnHSSP5U+FpIFb+Wd6Xb03Yca7Shq3G1xHdKosm WK8+MAYg1FwlpVLf3Y7lg5QbPoplGchUC5QFa1xzJc88Pxrd0kYIDdshxd2HyNWhBCLdKPPU iU10VzwFZ6mR7/nD0pWv0mxyrNd+f+BU7mM1mOQsr+GvHpWCStlPxUrQBXKKH1hcCS8NWIXU M3WXQSXWyYCEhmu0/m220BPFRjJL39nwCALgZ+LlDJHaM65hmZ4VXO75YWWjOHpuJMNJZE65 nhXX2x5my+TzazAe9z5Xxly3ZWZ2iCQP6GbGduGMGVkS2V8Y6fpFUEcqx3nucCqM7Jnf5Sfn xjCCBu4wggXWoAMCAQICEHEVZgVK5JEhTem8RPms09wwDQYJKoZIhvcNAQEFBQAwgcoxCzAJ BgNVBAYTAlVTMRcwFQYDVQQKEw5WZXJpU2lnbiwgSW5jLjEfMB0GA1UECxMWVmVyaVNpZ24g VHJ1c3QgTmV0d29yazE6MDgGA1UECxMxKGMpIDE5OTkgVmVyaVNpZ24sIEluYy4gLSBGb3Ig YXV0aG9yaXplZCB1c2Ugb25seTFFMEMGA1UEAxM8VmVyaVNpZ24gQ2xhc3MgMSBQdWJsaWMg UHJpbWFyeSBDZXJ0aWZpY2F0aW9uIEF1dGhvcml0eSAtIEczMB4XDTA5MDUwMTAwMDAwMFoX DTE5MDQzMDIzNTk1OVowgd0xCzAJBgNVBAYTAlVTMRcwFQYDVQQKEw5WZXJpU2lnbiwgSW5j LjEfMB0GA1UECxMWVmVyaVNpZ24gVHJ1c3QgTmV0d29yazE7MDkGA1UECxMyVGVybXMgb2Yg dXNlIGF0IGh0dHBzOi8vd3d3LnZlcmlzaWduLmNvbS9ycGEgKGMpMDkxHjAcBgNVBAsTFVBl cnNvbmEgTm90IFZhbGlkYXRlZDE3MDUGA1UEAxMuVmVyaVNpZ24gQ2xhc3MgMSBJbmRpdmlk dWFsIFN1YnNjcmliZXIgQ0EgLSBHMzCCASIwDQYJKoZIhvcNAQEBBQADggEPADCCAQoCggEB AO3ER98qKB18Bmu71yEyyWwTj+mxjUFONPfaC+Nq+mWIIAsRE+mb4ElOi2/VAdBfDUeRilpM dD4/xpEJu0w0no1uoYJRYvdpdliWB6+eFBgHT1q9n9IxslQZc0ZqGUIR7BJzIY313DDN5dlW CjHFNm0pFJe9LdqJRxmI2EsEPeu2PGcedAATDdCG2pNn+DMDrho8a2l49sAsjuGDP3f5mf/+ n1JawrSHCthsqUfBVCllQz5KwJYfwa33d69ssQRevsG2lC2XkC0n0rse6YNqhPbEsq4jBmUm pSdYKwcitG+mYkgad/LVUCeaKdOW+yj1uiR2YuOMWev7btVCxL5Bx/UCAwEAAaOCArkwggK1 MDQGCCsGAQUFBwEBBCgwJjAkBggrBgEFBQcwAYYYaHR0cDovL29jc3AudmVyaXNpZ24uY29t MBIGA1UdEwEB/wQIMAYBAf8CAQAwcAYDVR0gBGkwZzBlBgtghkgBhvhFAQcXATBWMCgGCCsG AQUFBwIBFhxodHRwczovL3d3dy52ZXJpc2lnbi5jb20vY3BzMCoGCCsGAQUFBwICMB4aHGh0 dHBzOi8vd3d3LnZlcmlzaWduLmNvbS9ycGEwNAYDVR0fBC0wKzApoCegJYYjaHR0cDovL2Ny bC52ZXJpc2lnbi5jb20vcGNhMS1nMy5jcmwwDgYDVR0PAQH/BAQDAgEGMG4GCCsGAQUFBwEM BGIwYKFeoFwwWjBYMFYWCWltYWdlL2dpZjAhMB8wBwYFKw4DAhoEFEtruSiWBgy70FI4myms SweLIQUYMCYWJGh0dHA6Ly9sb2dvLnZlcmlzaWduLmNvbS92c2xvZ28xLmdpZjAuBgNVHREE JzAlpCMwITEfMB0GA1UEAxMWUHJpdmF0ZUxhYmVsNC0yMDQ4LTExODAdBgNVHQ4EFgQUeUdh CEH9OASiS+e1zPVD9kkrEfgwgfEGA1UdIwSB6TCB5qGB0KSBzTCByjELMAkGA1UEBhMCVVMx FzAVBgNVBAoTDlZlcmlTaWduLCBJbmMuMR8wHQYDVQQLExZWZXJpU2lnbiBUcnVzdCBOZXR3 b3JrMTowOAYDVQQLEzEoYykgMTk5OSBWZXJpU2lnbiwgSW5jLiAtIEZvciBhdXRob3JpemVk IHVzZSBvbmx5MUUwQwYDVQQDEzxWZXJpU2lnbiBDbGFzcyAxIFB1YmxpYyBQcmltYXJ5IENl cnRpZmljYXRpb24gQXV0aG9yaXR5IC0gRzOCEQCLW3VWhFSFCwDPrzhIzrGkMA0GCSqGSIb3 DQEBBQUAA4IBAQA5Tc9BmYG1qQW1UjjpOYSJbOQ0qFrn2GwJTCQaulmkhztzIfGTgc+/aGNa Z/41hSuhw12jSsI6Gd0w1sxN7/HSgZfKVFpDvzeLeo4ZjQ9DqIzyr2CzFYqzlZw84J6zJ5ik NXIX5fwqXYfTig3C0UUq+MD0rCqTOtWuEnAI6/s74nfs6CtkNXbNutrg0csU1nFYm77VPn22 2egkxSRmTF2RH3azFz5/DcYhiS+zN7ih/1yybUneZVJC+w6I0u1KHb9L4/jMcvpIDmWOScjW +JmYO7eUPjFxBof6bFlTLtffK+1fYwCsFe0DuFUWjMZoA+ciqHMLsbyg2lJY3QoOf8GCMYIE +TCCBPUCAQEwgfIwgd0xCzAJBgNVBAYTAlVTMRcwFQYDVQQKEw5WZXJpU2lnbiwgSW5jLjEf MB0GA1UECxMWVmVyaVNpZ24gVHJ1c3QgTmV0d29yazE7MDkGA1UECxMyVGVybXMgb2YgdXNl IGF0IGh0dHBzOi8vd3d3LnZlcmlzaWduLmNvbS9ycGEgKGMpMDkxHjAcBgNVBAsTFVBlcnNv bmEgTm90IFZhbGlkYXRlZDE3MDUGA1UEAxMuVmVyaVNpZ24gQ2xhc3MgMSBJbmRpdmlkdWFs IFN1YnNjcmliZXIgQ0EgLSBHMwIQFPhbiD4unFUK+hWzYF5oBTAJBgUrDgMCGgUAoIIC2zAY BgkqhkiG9w0BCQMxCwYJKoZIhvcNAQcBMBwGCSqGSIb3DQEJBTEPFw0xMjA5MjUxMzQyMDla MCMGCSqGSIb3DQEJBDEWBBQnkOoS3efiDsq//Tl/Y1IW5hI3jDBsBgkqhkiG9w0BCQ8xXzBd MAsGCWCGSAFlAwQBKjALBglghkgBZQMEAQIwCgYIKoZIhvcNAwcwDgYIKoZIhvcNAwICAgCA MA0GCCqGSIb3DQMCAgFAMAcGBSsOAwIHMA0GCCqGSIb3DQMCAgEoMIIBAwYJKwYBBAGCNxAE MYH1MIHyMIHdMQswCQYDVQQGEwJVUzEXMBUGA1UEChMOVmVyaVNpZ24sIEluYy4xHzAdBgNV BAsTFlZlcmlTaWduIFRydXN0IE5ldHdvcmsxOzA5BgNVBAsTMlRlcm1zIG9mIHVzZSBhdCBo dHRwczovL3d3dy52ZXJpc2lnbi5jb20vcnBhIChjKTA5MR4wHAYDVQQLExVQZXJzb25hIE5v dCBWYWxpZGF0ZWQxNzA1BgNVBAMTLlZlcmlTaWduIENsYXNzIDEgSW5kaXZpZHVhbCBTdWJz Y3JpYmVyIENBIC0gRzMCEBT4W4g+LpxVCvoVs2BeaAUwggEFBgsqhkiG9w0BCRACCzGB9aCB 8jCB3TELMAkGA1UEBhMCVVMxFzAVBgNVBAoTDlZlcmlTaWduLCBJbmMuMR8wHQYDVQQLExZW ZXJpU2lnbiBUcnVzdCBOZXR3b3JrMTswOQYDVQQLEzJUZXJtcyBvZiB1c2UgYXQgaHR0cHM6 Ly93d3cudmVyaXNpZ24uY29tL3JwYSAoYykwOTEeMBwGA1UECxMVUGVyc29uYSBOb3QgVmFs aWRhdGVkMTcwNQYDVQQDEy5WZXJpU2lnbiBDbGFzcyAxIEluZGl2aWR1YWwgU3Vic2NyaWJl ciBDQSAtIEczAhAU+FuIPi6cVQr6FbNgXmgFMA0GCSqGSIb3DQEBAQUABIIBAEb4PPa6yWgk KTRV4LNSvHl3ba1mrkg8jr602R5AEoyxI7s3FS0iDbuX06Jp3nqyVMKKRFrspTIc2r5rn0ZG rtbYiHs8MTcw0KC6Vgc8KtC1RYk2JscIAShPdkZCF7kMue0s/+komyIOI9p9YdHnaqobwzse b65xfTqQITnwbo6ZeLAoS5T1IlZtaKLvuKLzOTch6Wr4Aj+Utpy0u5gry1iUSxZXp+BDnqX6 U8g5n2hqPhJ2GMrLX4bbV1PE273BwthDOuVquvYz1KKFTsODPZA1EaKPdjpIEOWlafnGU3sh Wq9UkJJ18SfynyokKCkTMhO3u9EiW+iWXfB18wuPP4EAAAAAAAA= --------------ms090904030208020903050408-- --===============2640791109350789978== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users --===============2640791109350789978==-- From xen-users-bounces@lists.xen.org Tue Sep 25 13:51:37 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Tue, 25 Sep 2012 13:51:37 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TGVWq-0000wW-9t; Tue, 25 Sep 2012 13:50:24 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TGVWo-0000wK-Jh for xen-users@lists.xen.org; Tue, 25 Sep 2012 13:50:22 +0000 Received: from [85.158.138.51:47880] by server-6.bemta-3.messagelabs.com id E5/40-29694-D96B1605; Tue, 25 Sep 2012 13:50:21 +0000 X-Env-Sender: Ian.Campbell@citrix.com X-Msg-Ref: server-6.tower-174.messagelabs.com!1348581020!23878755!1 X-Originating-IP: [62.200.22.115] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogNjIuMjAwLjIyLjExNSA9PiAxMTEwNzk=\n X-StarScan-Received: X-StarScan-Version: 6.6.1.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 22978 invoked from network); 25 Sep 2012 13:50:21 -0000 Received: from smtp.eu.citrix.com (HELO SMTP.EU.CITRIX.COM) (62.200.22.115) by server-6.tower-174.messagelabs.com with RC4-SHA encrypted SMTP; 25 Sep 2012 13:50:21 -0000 X-IronPort-AV: E=Sophos;i="4.80,483,1344211200"; d="scan'208";a="14752083" Received: from lonpmailmx01.citrite.net ([10.30.203.162]) by LONPIPO01.EU.CITRIX.COM with ESMTP/TLS/RC4-MD5; 25 Sep 2012 13:49:59 +0000 Received: from [10.80.2.42] (10.80.2.42) by LONPMAILMX01.citrite.net (10.30.203.162) with Microsoft SMTP Server id 8.3.279.1; Tue, 25 Sep 2012 14:49:59 +0100 Message-ID: <1348580998.11229.20.camel@zakaz.uk.xensource.com> From: Ian Campbell To: Jan Hejl Date: Tue, 25 Sep 2012 14:49:58 +0100 In-Reply-To: <5061B4B1.6020104@excello.cz> References: <5061B4B1.6020104@excello.cz> Organization: Citrix Systems, Inc. X-Mailer: Evolution 3.4.3-1 MIME-Version: 1.0 Cc: "xen-users@lists.xen.org" Subject: Re: [Xen-users] Auto CPU pinning for domUs X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org On Tue, 2012-09-25 at 14:42 +0100, Jan Hejl wrote: > so I suppose that it should be pinned to CPUs 16 to 19. But in 'xl > vcpu-list' is 'Any CPU', thus i have to do this manually with 'xl > vcpu-pin' command. Is there any way to do this automaticaly? Or am I > doing something wrong? IIRC the cpus syntax isn't supported by xl until 4.2.0. Ian. _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Tue Sep 25 13:51:37 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Tue, 25 Sep 2012 13:51:37 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TGVWq-0000wW-9t; Tue, 25 Sep 2012 13:50:24 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TGVWo-0000wK-Jh for xen-users@lists.xen.org; Tue, 25 Sep 2012 13:50:22 +0000 Received: from [85.158.138.51:47880] by server-6.bemta-3.messagelabs.com id E5/40-29694-D96B1605; Tue, 25 Sep 2012 13:50:21 +0000 X-Env-Sender: Ian.Campbell@citrix.com X-Msg-Ref: server-6.tower-174.messagelabs.com!1348581020!23878755!1 X-Originating-IP: [62.200.22.115] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogNjIuMjAwLjIyLjExNSA9PiAxMTEwNzk=\n X-StarScan-Received: X-StarScan-Version: 6.6.1.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 22978 invoked from network); 25 Sep 2012 13:50:21 -0000 Received: from smtp.eu.citrix.com (HELO SMTP.EU.CITRIX.COM) (62.200.22.115) by server-6.tower-174.messagelabs.com with RC4-SHA encrypted SMTP; 25 Sep 2012 13:50:21 -0000 X-IronPort-AV: E=Sophos;i="4.80,483,1344211200"; d="scan'208";a="14752083" Received: from lonpmailmx01.citrite.net ([10.30.203.162]) by LONPIPO01.EU.CITRIX.COM with ESMTP/TLS/RC4-MD5; 25 Sep 2012 13:49:59 +0000 Received: from [10.80.2.42] (10.80.2.42) by LONPMAILMX01.citrite.net (10.30.203.162) with Microsoft SMTP Server id 8.3.279.1; Tue, 25 Sep 2012 14:49:59 +0100 Message-ID: <1348580998.11229.20.camel@zakaz.uk.xensource.com> From: Ian Campbell To: Jan Hejl Date: Tue, 25 Sep 2012 14:49:58 +0100 In-Reply-To: <5061B4B1.6020104@excello.cz> References: <5061B4B1.6020104@excello.cz> Organization: Citrix Systems, Inc. X-Mailer: Evolution 3.4.3-1 MIME-Version: 1.0 Cc: "xen-users@lists.xen.org" Subject: Re: [Xen-users] Auto CPU pinning for domUs X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org On Tue, 2012-09-25 at 14:42 +0100, Jan Hejl wrote: > so I suppose that it should be pinned to CPUs 16 to 19. But in 'xl > vcpu-list' is 'Any CPU', thus i have to do this manually with 'xl > vcpu-pin' command. Is there any way to do this automaticaly? Or am I > doing something wrong? IIRC the cpus syntax isn't supported by xl until 4.2.0. Ian. _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Tue Sep 25 13:55:43 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Tue, 25 Sep 2012 13:55:43 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TGVb9-0001F2-9B; Tue, 25 Sep 2012 13:54:51 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TGVb8-0001Ew-2v for xen-users@lists.xen.org; Tue, 25 Sep 2012 13:54:50 +0000 Received: from [85.158.138.51:27766] by server-4.bemta-3.messagelabs.com id 3D/38-24831-9A7B1605; Tue, 25 Sep 2012 13:54:49 +0000 X-Env-Sender: jh@excello.cz X-Msg-Ref: server-4.tower-174.messagelabs.com!1348581288!31409441!1 X-Originating-IP: [81.31.35.100] X-SpamReason: No, hits=0.0 required=7.0 tests=UNPARSEABLE_RELAY X-StarScan-Received: X-StarScan-Version: 6.6.1.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 14461 invoked from network); 25 Sep 2012 13:54:48 -0000 Received: from out2.virusfree.cz (HELO out2.virusfree.cz) (81.31.35.100) by server-4.tower-174.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 25 Sep 2012 13:54:48 -0000 Received: (qmail 29146 invoked by uid 1000); 25 Sep 2012 15:54:48 +0200 Received: from smtp.excello.cz by out2 (envelope-from , uid 201) with VF-scanner-2.08VF (www.virusfree.cz : out2.virusfree.cz Clear:RC:1(91.121.238.113):SA:0(-11.2/5.0):. Processed in 2.406922 secs); 25 Sep 2012 13:54:48 -0000 X-Spam-Status: No, hits=-11.2 required=5.0 X-Spam-Report: SA TESTS -4.9 BAYES_00 BODY: Bayes spam probability is 0 to 1% [score: 0.0001] -4.0 INREPLYTOCOM INREPLYTOCOM -1.5 INREPLYTO0 INREPLYTO0 0.8 DKIM_ADSP_ALL No valid author signature, domain signs all mail -0.0 SPF_PASS SPF: sender matches SPF record -0.6 RP_MATCHES_RCVD Envelope sender domain matches handover relay domain 1.0 SPF_HELO_FAIL SPF: HELO does not match SPF record (fail) [SPF failed: Please see http://www.openspf.net/Why?s=helo; id=smtp.excello.cz; ip=91.121.238.113; r=bq.virusfree.cz] -2.0 MFH_PKCS7_4 FULL: S/MIME Header Received: from smtp.excello.cz (91.121.238.113) by out2.virusfree.cz with SMTP; 25 Sep 2012 15:54:45 +0200 Received: from [192.168.2.2] (unknown [212.80.95.150]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by smtp.excello.cz (Postfix) with ESMTPSA id 2FEDA810EA08; Tue, 25 Sep 2012 15:54:45 +0200 (CEST) Message-ID: <5061B7A5.1020300@excello.cz> Date: Tue, 25 Sep 2012 15:54:45 +0200 From: Jan Hejl User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:15.0) Gecko/20120827 Thunderbird/15.0 MIME-Version: 1.0 To: Ian Campbell References: <5061B4B1.6020104@excello.cz> <1348580998.11229.20.camel@zakaz.uk.xensource.com> In-Reply-To: <1348580998.11229.20.camel@zakaz.uk.xensource.com> Cc: "xen-users@lists.xen.org" Subject: Re: [Xen-users] Auto CPU pinning for domUs X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============3503323030232630811==" Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org Toto je elektronicky podepsana zprava ve formatu MIME. --===============3503323030232630811== Content-Type: multipart/signed; protocol="application/pkcs7-signature"; micalg=sha1; boundary="------------ms020105060708040909010100" Toto je elektronicky podepsana zprava ve formatu MIME. --------------ms020105060708040909010100 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: quoted-printable Thank you so much Ian. I'll wait for 4.2.0 to be released on Gentoo. Have a nice day Jan Dne 25.9.2012 15:49, Ian Campbell napsal(a): > On Tue, 2012-09-25 at 14:42 +0100, Jan Hejl wrote: >> so I suppose that it should be pinned to CPUs 16 to 19. But in 'xl >> vcpu-list' is 'Any CPU', thus i have to do this manually with 'xl >> vcpu-pin' command. Is there any way to do this automaticaly? Or am I >> doing something wrong? > IIRC the cpus syntax isn't supported by xl until 4.2.0. > > Ian. > > --------------ms020105060708040909010100 Content-Type: application/pkcs7-signature; name="smime.p7s" Content-Transfer-Encoding: base64 Content-Disposition: attachment; filename="smime.p7s" Content-Description: Elektronicky podpis S/MIME MIAGCSqGSIb3DQEHAqCAMIACAQExCzAJBgUrDgMCGgUAMIAGCSqGSIb3DQEHAQAAoIIMOzCC BUUwggQtoAMCAQICEBT4W4g+LpxVCvoVs2BeaAUwDQYJKoZIhvcNAQEFBQAwgd0xCzAJBgNV BAYTAlVTMRcwFQYDVQQKEw5WZXJpU2lnbiwgSW5jLjEfMB0GA1UECxMWVmVyaVNpZ24gVHJ1 c3QgTmV0d29yazE7MDkGA1UECxMyVGVybXMgb2YgdXNlIGF0IGh0dHBzOi8vd3d3LnZlcmlz aWduLmNvbS9ycGEgKGMpMDkxHjAcBgNVBAsTFVBlcnNvbmEgTm90IFZhbGlkYXRlZDE3MDUG A1UEAxMuVmVyaVNpZ24gQ2xhc3MgMSBJbmRpdmlkdWFsIFN1YnNjcmliZXIgQ0EgLSBHMzAe Fw0xMjA4MjEwMDAwMDBaFw0xMzA4MjEyMzU5NTlaMIIBCDEXMBUGA1UEChMOVmVyaVNpZ24s IEluYy4xHzAdBgNVBAsTFlZlcmlTaWduIFRydXN0IE5ldHdvcmsxRjBEBgNVBAsTPXd3dy52 ZXJpc2lnbi5jb20vcmVwb3NpdG9yeS9SUEEgSW5jb3JwLiBieSBSZWYuLExJQUIuTFREKGMp OTgxHjAcBgNVBAsTFVBlcnNvbmEgTm90IFZhbGlkYXRlZDEzMDEGA1UECxMqRGlnaXRhbCBJ RCBDbGFzcyAxIC0gTmV0c2NhcGUgRnVsbCBTZXJ2aWNlMREwDwYDVQQDFAhKYW4gSGVqbDEc MBoGCSqGSIb3DQEJARYNamhAZXhjZWxsby5jejCCASIwDQYJKoZIhvcNAQEBBQADggEPADCC AQoCggEBAKZYfrag8UJ0JgrVdujHsmcxbgdXnbVZuWxIuJ6rY9Y3JBUfOTRODhMkaoxQDYTq pzG/JUNNZW1nF6QIYuPMcwzhEWAfoWhnhvm03KohNVKNID3A1SghW8bV3mRtaoyFHSIfiiFF DH7+BvSsIXP8slIzBi4wXvidDw1ui0MVA6Wy0mSSHLZdGHOpO8CswWXK6YQ87nG7a28QTCi6 HycFwbdhsPm4NADD7zrqnRkLVmWdnZWpA6CHkngGuR+0LpovAlmyiKUMLK4GkMOIMz24Pawk icIGI/AqrUmYpj8IwM4F0BGI1O1rZSUK72SV11eRuriqskzpcY1FVW0VmR1XNg0CAwEAAaOB 0jCBzzAJBgNVHRMEAjAAMEQGA1UdIAQ9MDswOQYLYIZIAYb4RQEHFwEwKjAoBggrBgEFBQcC ARYcaHR0cHM6Ly93d3cudmVyaXNpZ24uY29tL3JwYTALBgNVHQ8EBAMCBaAwHQYDVR0lBBYw FAYIKwYBBQUHAwQGCCsGAQUFBwMCMFAGA1UdHwRJMEcwRaBDoEGGP2h0dHA6Ly9pbmRjMWRp Z2l0YWxpZC1nMy1jcmwudmVyaXNpZ24uY29tL0luZEMxRGlnaXRhbElELUczLmNybDANBgkq hkiG9w0BAQUFAAOCAQEAh/RUK66OYfOqJdnHSSP5U+FpIFb+Wd6Xb03Yca7Shq3G1xHdKosm WK8+MAYg1FwlpVLf3Y7lg5QbPoplGchUC5QFa1xzJc88Pxrd0kYIDdshxd2HyNWhBCLdKPPU iU10VzwFZ6mR7/nD0pWv0mxyrNd+f+BU7mM1mOQsr+GvHpWCStlPxUrQBXKKH1hcCS8NWIXU M3WXQSXWyYCEhmu0/m220BPFRjJL39nwCALgZ+LlDJHaM65hmZ4VXO75YWWjOHpuJMNJZE65 nhXX2x5my+TzazAe9z5Xxly3ZWZ2iCQP6GbGduGMGVkS2V8Y6fpFUEcqx3nucCqM7Jnf5Sfn xjCCBu4wggXWoAMCAQICEHEVZgVK5JEhTem8RPms09wwDQYJKoZIhvcNAQEFBQAwgcoxCzAJ BgNVBAYTAlVTMRcwFQYDVQQKEw5WZXJpU2lnbiwgSW5jLjEfMB0GA1UECxMWVmVyaVNpZ24g VHJ1c3QgTmV0d29yazE6MDgGA1UECxMxKGMpIDE5OTkgVmVyaVNpZ24sIEluYy4gLSBGb3Ig YXV0aG9yaXplZCB1c2Ugb25seTFFMEMGA1UEAxM8VmVyaVNpZ24gQ2xhc3MgMSBQdWJsaWMg UHJpbWFyeSBDZXJ0aWZpY2F0aW9uIEF1dGhvcml0eSAtIEczMB4XDTA5MDUwMTAwMDAwMFoX DTE5MDQzMDIzNTk1OVowgd0xCzAJBgNVBAYTAlVTMRcwFQYDVQQKEw5WZXJpU2lnbiwgSW5j LjEfMB0GA1UECxMWVmVyaVNpZ24gVHJ1c3QgTmV0d29yazE7MDkGA1UECxMyVGVybXMgb2Yg dXNlIGF0IGh0dHBzOi8vd3d3LnZlcmlzaWduLmNvbS9ycGEgKGMpMDkxHjAcBgNVBAsTFVBl cnNvbmEgTm90IFZhbGlkYXRlZDE3MDUGA1UEAxMuVmVyaVNpZ24gQ2xhc3MgMSBJbmRpdmlk dWFsIFN1YnNjcmliZXIgQ0EgLSBHMzCCASIwDQYJKoZIhvcNAQEBBQADggEPADCCAQoCggEB AO3ER98qKB18Bmu71yEyyWwTj+mxjUFONPfaC+Nq+mWIIAsRE+mb4ElOi2/VAdBfDUeRilpM dD4/xpEJu0w0no1uoYJRYvdpdliWB6+eFBgHT1q9n9IxslQZc0ZqGUIR7BJzIY313DDN5dlW CjHFNm0pFJe9LdqJRxmI2EsEPeu2PGcedAATDdCG2pNn+DMDrho8a2l49sAsjuGDP3f5mf/+ n1JawrSHCthsqUfBVCllQz5KwJYfwa33d69ssQRevsG2lC2XkC0n0rse6YNqhPbEsq4jBmUm pSdYKwcitG+mYkgad/LVUCeaKdOW+yj1uiR2YuOMWev7btVCxL5Bx/UCAwEAAaOCArkwggK1 MDQGCCsGAQUFBwEBBCgwJjAkBggrBgEFBQcwAYYYaHR0cDovL29jc3AudmVyaXNpZ24uY29t MBIGA1UdEwEB/wQIMAYBAf8CAQAwcAYDVR0gBGkwZzBlBgtghkgBhvhFAQcXATBWMCgGCCsG AQUFBwIBFhxodHRwczovL3d3dy52ZXJpc2lnbi5jb20vY3BzMCoGCCsGAQUFBwICMB4aHGh0 dHBzOi8vd3d3LnZlcmlzaWduLmNvbS9ycGEwNAYDVR0fBC0wKzApoCegJYYjaHR0cDovL2Ny bC52ZXJpc2lnbi5jb20vcGNhMS1nMy5jcmwwDgYDVR0PAQH/BAQDAgEGMG4GCCsGAQUFBwEM BGIwYKFeoFwwWjBYMFYWCWltYWdlL2dpZjAhMB8wBwYFKw4DAhoEFEtruSiWBgy70FI4myms SweLIQUYMCYWJGh0dHA6Ly9sb2dvLnZlcmlzaWduLmNvbS92c2xvZ28xLmdpZjAuBgNVHREE JzAlpCMwITEfMB0GA1UEAxMWUHJpdmF0ZUxhYmVsNC0yMDQ4LTExODAdBgNVHQ4EFgQUeUdh CEH9OASiS+e1zPVD9kkrEfgwgfEGA1UdIwSB6TCB5qGB0KSBzTCByjELMAkGA1UEBhMCVVMx FzAVBgNVBAoTDlZlcmlTaWduLCBJbmMuMR8wHQYDVQQLExZWZXJpU2lnbiBUcnVzdCBOZXR3 b3JrMTowOAYDVQQLEzEoYykgMTk5OSBWZXJpU2lnbiwgSW5jLiAtIEZvciBhdXRob3JpemVk IHVzZSBvbmx5MUUwQwYDVQQDEzxWZXJpU2lnbiBDbGFzcyAxIFB1YmxpYyBQcmltYXJ5IENl cnRpZmljYXRpb24gQXV0aG9yaXR5IC0gRzOCEQCLW3VWhFSFCwDPrzhIzrGkMA0GCSqGSIb3 DQEBBQUAA4IBAQA5Tc9BmYG1qQW1UjjpOYSJbOQ0qFrn2GwJTCQaulmkhztzIfGTgc+/aGNa Z/41hSuhw12jSsI6Gd0w1sxN7/HSgZfKVFpDvzeLeo4ZjQ9DqIzyr2CzFYqzlZw84J6zJ5ik NXIX5fwqXYfTig3C0UUq+MD0rCqTOtWuEnAI6/s74nfs6CtkNXbNutrg0csU1nFYm77VPn22 2egkxSRmTF2RH3azFz5/DcYhiS+zN7ih/1yybUneZVJC+w6I0u1KHb9L4/jMcvpIDmWOScjW +JmYO7eUPjFxBof6bFlTLtffK+1fYwCsFe0DuFUWjMZoA+ciqHMLsbyg2lJY3QoOf8GCMYIE +TCCBPUCAQEwgfIwgd0xCzAJBgNVBAYTAlVTMRcwFQYDVQQKEw5WZXJpU2lnbiwgSW5jLjEf MB0GA1UECxMWVmVyaVNpZ24gVHJ1c3QgTmV0d29yazE7MDkGA1UECxMyVGVybXMgb2YgdXNl IGF0IGh0dHBzOi8vd3d3LnZlcmlzaWduLmNvbS9ycGEgKGMpMDkxHjAcBgNVBAsTFVBlcnNv bmEgTm90IFZhbGlkYXRlZDE3MDUGA1UEAxMuVmVyaVNpZ24gQ2xhc3MgMSBJbmRpdmlkdWFs IFN1YnNjcmliZXIgQ0EgLSBHMwIQFPhbiD4unFUK+hWzYF5oBTAJBgUrDgMCGgUAoIIC2zAY BgkqhkiG9w0BCQMxCwYJKoZIhvcNAQcBMBwGCSqGSIb3DQEJBTEPFw0xMjA5MjUxMzU0NDVa MCMGCSqGSIb3DQEJBDEWBBQy3XCcaGUCCpBRDnKNV1MGfzLaizBsBgkqhkiG9w0BCQ8xXzBd MAsGCWCGSAFlAwQBKjALBglghkgBZQMEAQIwCgYIKoZIhvcNAwcwDgYIKoZIhvcNAwICAgCA MA0GCCqGSIb3DQMCAgFAMAcGBSsOAwIHMA0GCCqGSIb3DQMCAgEoMIIBAwYJKwYBBAGCNxAE MYH1MIHyMIHdMQswCQYDVQQGEwJVUzEXMBUGA1UEChMOVmVyaVNpZ24sIEluYy4xHzAdBgNV BAsTFlZlcmlTaWduIFRydXN0IE5ldHdvcmsxOzA5BgNVBAsTMlRlcm1zIG9mIHVzZSBhdCBo dHRwczovL3d3dy52ZXJpc2lnbi5jb20vcnBhIChjKTA5MR4wHAYDVQQLExVQZXJzb25hIE5v dCBWYWxpZGF0ZWQxNzA1BgNVBAMTLlZlcmlTaWduIENsYXNzIDEgSW5kaXZpZHVhbCBTdWJz Y3JpYmVyIENBIC0gRzMCEBT4W4g+LpxVCvoVs2BeaAUwggEFBgsqhkiG9w0BCRACCzGB9aCB 8jCB3TELMAkGA1UEBhMCVVMxFzAVBgNVBAoTDlZlcmlTaWduLCBJbmMuMR8wHQYDVQQLExZW ZXJpU2lnbiBUcnVzdCBOZXR3b3JrMTswOQYDVQQLEzJUZXJtcyBvZiB1c2UgYXQgaHR0cHM6 Ly93d3cudmVyaXNpZ24uY29tL3JwYSAoYykwOTEeMBwGA1UECxMVUGVyc29uYSBOb3QgVmFs aWRhdGVkMTcwNQYDVQQDEy5WZXJpU2lnbiBDbGFzcyAxIEluZGl2aWR1YWwgU3Vic2NyaWJl ciBDQSAtIEczAhAU+FuIPi6cVQr6FbNgXmgFMA0GCSqGSIb3DQEBAQUABIIBAFm0PASVLQCI CsSe6aRU4VId37MRyb59FQZOPWs2WjAOnMpQ4F5bV4+Cwd20yPRT0OBBu+0ABsCfFmoQwK5c qDrFF8F/N3t2mi8FTlEeCGcMdOdm8GFAXAip+PyYIf+h95aieiz0PzYElUGN+/R5azrdzaFK FAv4MrRng/jYLF9iM8wUPNyTuM+nLJvYh7ihODe4gOOY+446O4QEUBQ0dYTeYDFkyTPiq/Hx hEFsgLfci1XZOpiS5HSB0J3Rn01vSvTebv6LR8Fp5EAqPiBiOuaL2OTzmuMaP0GWAhMizI5k z+eD78IGmMcK5z0WHsfVNcjN99vxQAG38ATLWYdbxO8AAAAAAAA= --------------ms020105060708040909010100-- --===============3503323030232630811== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users --===============3503323030232630811==-- From xen-users-bounces@lists.xen.org Tue Sep 25 13:55:43 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Tue, 25 Sep 2012 13:55:43 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TGVb9-0001F2-9B; Tue, 25 Sep 2012 13:54:51 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TGVb8-0001Ew-2v for xen-users@lists.xen.org; Tue, 25 Sep 2012 13:54:50 +0000 Received: from [85.158.138.51:27766] by server-4.bemta-3.messagelabs.com id 3D/38-24831-9A7B1605; Tue, 25 Sep 2012 13:54:49 +0000 X-Env-Sender: jh@excello.cz X-Msg-Ref: server-4.tower-174.messagelabs.com!1348581288!31409441!1 X-Originating-IP: [81.31.35.100] X-SpamReason: No, hits=0.0 required=7.0 tests=UNPARSEABLE_RELAY X-StarScan-Received: X-StarScan-Version: 6.6.1.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 14461 invoked from network); 25 Sep 2012 13:54:48 -0000 Received: from out2.virusfree.cz (HELO out2.virusfree.cz) (81.31.35.100) by server-4.tower-174.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 25 Sep 2012 13:54:48 -0000 Received: (qmail 29146 invoked by uid 1000); 25 Sep 2012 15:54:48 +0200 Received: from smtp.excello.cz by out2 (envelope-from , uid 201) with VF-scanner-2.08VF (www.virusfree.cz : out2.virusfree.cz Clear:RC:1(91.121.238.113):SA:0(-11.2/5.0):. Processed in 2.406922 secs); 25 Sep 2012 13:54:48 -0000 X-Spam-Status: No, hits=-11.2 required=5.0 X-Spam-Report: SA TESTS -4.9 BAYES_00 BODY: Bayes spam probability is 0 to 1% [score: 0.0001] -4.0 INREPLYTOCOM INREPLYTOCOM -1.5 INREPLYTO0 INREPLYTO0 0.8 DKIM_ADSP_ALL No valid author signature, domain signs all mail -0.0 SPF_PASS SPF: sender matches SPF record -0.6 RP_MATCHES_RCVD Envelope sender domain matches handover relay domain 1.0 SPF_HELO_FAIL SPF: HELO does not match SPF record (fail) [SPF failed: Please see http://www.openspf.net/Why?s=helo; id=smtp.excello.cz; ip=91.121.238.113; r=bq.virusfree.cz] -2.0 MFH_PKCS7_4 FULL: S/MIME Header Received: from smtp.excello.cz (91.121.238.113) by out2.virusfree.cz with SMTP; 25 Sep 2012 15:54:45 +0200 Received: from [192.168.2.2] (unknown [212.80.95.150]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by smtp.excello.cz (Postfix) with ESMTPSA id 2FEDA810EA08; Tue, 25 Sep 2012 15:54:45 +0200 (CEST) Message-ID: <5061B7A5.1020300@excello.cz> Date: Tue, 25 Sep 2012 15:54:45 +0200 From: Jan Hejl User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:15.0) Gecko/20120827 Thunderbird/15.0 MIME-Version: 1.0 To: Ian Campbell References: <5061B4B1.6020104@excello.cz> <1348580998.11229.20.camel@zakaz.uk.xensource.com> In-Reply-To: <1348580998.11229.20.camel@zakaz.uk.xensource.com> Cc: "xen-users@lists.xen.org" Subject: Re: [Xen-users] Auto CPU pinning for domUs X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============3503323030232630811==" Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org Toto je elektronicky podepsana zprava ve formatu MIME. --===============3503323030232630811== Content-Type: multipart/signed; protocol="application/pkcs7-signature"; micalg=sha1; boundary="------------ms020105060708040909010100" Toto je elektronicky podepsana zprava ve formatu MIME. --------------ms020105060708040909010100 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: quoted-printable Thank you so much Ian. I'll wait for 4.2.0 to be released on Gentoo. Have a nice day Jan Dne 25.9.2012 15:49, Ian Campbell napsal(a): > On Tue, 2012-09-25 at 14:42 +0100, Jan Hejl wrote: >> so I suppose that it should be pinned to CPUs 16 to 19. But in 'xl >> vcpu-list' is 'Any CPU', thus i have to do this manually with 'xl >> vcpu-pin' command. Is there any way to do this automaticaly? Or am I >> doing something wrong? > IIRC the cpus syntax isn't supported by xl until 4.2.0. > > Ian. > > --------------ms020105060708040909010100 Content-Type: application/pkcs7-signature; name="smime.p7s" Content-Transfer-Encoding: base64 Content-Disposition: attachment; filename="smime.p7s" Content-Description: Elektronicky podpis S/MIME MIAGCSqGSIb3DQEHAqCAMIACAQExCzAJBgUrDgMCGgUAMIAGCSqGSIb3DQEHAQAAoIIMOzCC BUUwggQtoAMCAQICEBT4W4g+LpxVCvoVs2BeaAUwDQYJKoZIhvcNAQEFBQAwgd0xCzAJBgNV BAYTAlVTMRcwFQYDVQQKEw5WZXJpU2lnbiwgSW5jLjEfMB0GA1UECxMWVmVyaVNpZ24gVHJ1 c3QgTmV0d29yazE7MDkGA1UECxMyVGVybXMgb2YgdXNlIGF0IGh0dHBzOi8vd3d3LnZlcmlz aWduLmNvbS9ycGEgKGMpMDkxHjAcBgNVBAsTFVBlcnNvbmEgTm90IFZhbGlkYXRlZDE3MDUG A1UEAxMuVmVyaVNpZ24gQ2xhc3MgMSBJbmRpdmlkdWFsIFN1YnNjcmliZXIgQ0EgLSBHMzAe Fw0xMjA4MjEwMDAwMDBaFw0xMzA4MjEyMzU5NTlaMIIBCDEXMBUGA1UEChMOVmVyaVNpZ24s IEluYy4xHzAdBgNVBAsTFlZlcmlTaWduIFRydXN0IE5ldHdvcmsxRjBEBgNVBAsTPXd3dy52 ZXJpc2lnbi5jb20vcmVwb3NpdG9yeS9SUEEgSW5jb3JwLiBieSBSZWYuLExJQUIuTFREKGMp OTgxHjAcBgNVBAsTFVBlcnNvbmEgTm90IFZhbGlkYXRlZDEzMDEGA1UECxMqRGlnaXRhbCBJ RCBDbGFzcyAxIC0gTmV0c2NhcGUgRnVsbCBTZXJ2aWNlMREwDwYDVQQDFAhKYW4gSGVqbDEc MBoGCSqGSIb3DQEJARYNamhAZXhjZWxsby5jejCCASIwDQYJKoZIhvcNAQEBBQADggEPADCC AQoCggEBAKZYfrag8UJ0JgrVdujHsmcxbgdXnbVZuWxIuJ6rY9Y3JBUfOTRODhMkaoxQDYTq pzG/JUNNZW1nF6QIYuPMcwzhEWAfoWhnhvm03KohNVKNID3A1SghW8bV3mRtaoyFHSIfiiFF DH7+BvSsIXP8slIzBi4wXvidDw1ui0MVA6Wy0mSSHLZdGHOpO8CswWXK6YQ87nG7a28QTCi6 HycFwbdhsPm4NADD7zrqnRkLVmWdnZWpA6CHkngGuR+0LpovAlmyiKUMLK4GkMOIMz24Pawk icIGI/AqrUmYpj8IwM4F0BGI1O1rZSUK72SV11eRuriqskzpcY1FVW0VmR1XNg0CAwEAAaOB 0jCBzzAJBgNVHRMEAjAAMEQGA1UdIAQ9MDswOQYLYIZIAYb4RQEHFwEwKjAoBggrBgEFBQcC ARYcaHR0cHM6Ly93d3cudmVyaXNpZ24uY29tL3JwYTALBgNVHQ8EBAMCBaAwHQYDVR0lBBYw FAYIKwYBBQUHAwQGCCsGAQUFBwMCMFAGA1UdHwRJMEcwRaBDoEGGP2h0dHA6Ly9pbmRjMWRp Z2l0YWxpZC1nMy1jcmwudmVyaXNpZ24uY29tL0luZEMxRGlnaXRhbElELUczLmNybDANBgkq hkiG9w0BAQUFAAOCAQEAh/RUK66OYfOqJdnHSSP5U+FpIFb+Wd6Xb03Yca7Shq3G1xHdKosm WK8+MAYg1FwlpVLf3Y7lg5QbPoplGchUC5QFa1xzJc88Pxrd0kYIDdshxd2HyNWhBCLdKPPU iU10VzwFZ6mR7/nD0pWv0mxyrNd+f+BU7mM1mOQsr+GvHpWCStlPxUrQBXKKH1hcCS8NWIXU M3WXQSXWyYCEhmu0/m220BPFRjJL39nwCALgZ+LlDJHaM65hmZ4VXO75YWWjOHpuJMNJZE65 nhXX2x5my+TzazAe9z5Xxly3ZWZ2iCQP6GbGduGMGVkS2V8Y6fpFUEcqx3nucCqM7Jnf5Sfn xjCCBu4wggXWoAMCAQICEHEVZgVK5JEhTem8RPms09wwDQYJKoZIhvcNAQEFBQAwgcoxCzAJ BgNVBAYTAlVTMRcwFQYDVQQKEw5WZXJpU2lnbiwgSW5jLjEfMB0GA1UECxMWVmVyaVNpZ24g VHJ1c3QgTmV0d29yazE6MDgGA1UECxMxKGMpIDE5OTkgVmVyaVNpZ24sIEluYy4gLSBGb3Ig YXV0aG9yaXplZCB1c2Ugb25seTFFMEMGA1UEAxM8VmVyaVNpZ24gQ2xhc3MgMSBQdWJsaWMg UHJpbWFyeSBDZXJ0aWZpY2F0aW9uIEF1dGhvcml0eSAtIEczMB4XDTA5MDUwMTAwMDAwMFoX DTE5MDQzMDIzNTk1OVowgd0xCzAJBgNVBAYTAlVTMRcwFQYDVQQKEw5WZXJpU2lnbiwgSW5j LjEfMB0GA1UECxMWVmVyaVNpZ24gVHJ1c3QgTmV0d29yazE7MDkGA1UECxMyVGVybXMgb2Yg dXNlIGF0IGh0dHBzOi8vd3d3LnZlcmlzaWduLmNvbS9ycGEgKGMpMDkxHjAcBgNVBAsTFVBl cnNvbmEgTm90IFZhbGlkYXRlZDE3MDUGA1UEAxMuVmVyaVNpZ24gQ2xhc3MgMSBJbmRpdmlk dWFsIFN1YnNjcmliZXIgQ0EgLSBHMzCCASIwDQYJKoZIhvcNAQEBBQADggEPADCCAQoCggEB AO3ER98qKB18Bmu71yEyyWwTj+mxjUFONPfaC+Nq+mWIIAsRE+mb4ElOi2/VAdBfDUeRilpM dD4/xpEJu0w0no1uoYJRYvdpdliWB6+eFBgHT1q9n9IxslQZc0ZqGUIR7BJzIY313DDN5dlW CjHFNm0pFJe9LdqJRxmI2EsEPeu2PGcedAATDdCG2pNn+DMDrho8a2l49sAsjuGDP3f5mf/+ n1JawrSHCthsqUfBVCllQz5KwJYfwa33d69ssQRevsG2lC2XkC0n0rse6YNqhPbEsq4jBmUm pSdYKwcitG+mYkgad/LVUCeaKdOW+yj1uiR2YuOMWev7btVCxL5Bx/UCAwEAAaOCArkwggK1 MDQGCCsGAQUFBwEBBCgwJjAkBggrBgEFBQcwAYYYaHR0cDovL29jc3AudmVyaXNpZ24uY29t MBIGA1UdEwEB/wQIMAYBAf8CAQAwcAYDVR0gBGkwZzBlBgtghkgBhvhFAQcXATBWMCgGCCsG AQUFBwIBFhxodHRwczovL3d3dy52ZXJpc2lnbi5jb20vY3BzMCoGCCsGAQUFBwICMB4aHGh0 dHBzOi8vd3d3LnZlcmlzaWduLmNvbS9ycGEwNAYDVR0fBC0wKzApoCegJYYjaHR0cDovL2Ny bC52ZXJpc2lnbi5jb20vcGNhMS1nMy5jcmwwDgYDVR0PAQH/BAQDAgEGMG4GCCsGAQUFBwEM BGIwYKFeoFwwWjBYMFYWCWltYWdlL2dpZjAhMB8wBwYFKw4DAhoEFEtruSiWBgy70FI4myms SweLIQUYMCYWJGh0dHA6Ly9sb2dvLnZlcmlzaWduLmNvbS92c2xvZ28xLmdpZjAuBgNVHREE JzAlpCMwITEfMB0GA1UEAxMWUHJpdmF0ZUxhYmVsNC0yMDQ4LTExODAdBgNVHQ4EFgQUeUdh CEH9OASiS+e1zPVD9kkrEfgwgfEGA1UdIwSB6TCB5qGB0KSBzTCByjELMAkGA1UEBhMCVVMx FzAVBgNVBAoTDlZlcmlTaWduLCBJbmMuMR8wHQYDVQQLExZWZXJpU2lnbiBUcnVzdCBOZXR3 b3JrMTowOAYDVQQLEzEoYykgMTk5OSBWZXJpU2lnbiwgSW5jLiAtIEZvciBhdXRob3JpemVk IHVzZSBvbmx5MUUwQwYDVQQDEzxWZXJpU2lnbiBDbGFzcyAxIFB1YmxpYyBQcmltYXJ5IENl cnRpZmljYXRpb24gQXV0aG9yaXR5IC0gRzOCEQCLW3VWhFSFCwDPrzhIzrGkMA0GCSqGSIb3 DQEBBQUAA4IBAQA5Tc9BmYG1qQW1UjjpOYSJbOQ0qFrn2GwJTCQaulmkhztzIfGTgc+/aGNa Z/41hSuhw12jSsI6Gd0w1sxN7/HSgZfKVFpDvzeLeo4ZjQ9DqIzyr2CzFYqzlZw84J6zJ5ik NXIX5fwqXYfTig3C0UUq+MD0rCqTOtWuEnAI6/s74nfs6CtkNXbNutrg0csU1nFYm77VPn22 2egkxSRmTF2RH3azFz5/DcYhiS+zN7ih/1yybUneZVJC+w6I0u1KHb9L4/jMcvpIDmWOScjW +JmYO7eUPjFxBof6bFlTLtffK+1fYwCsFe0DuFUWjMZoA+ciqHMLsbyg2lJY3QoOf8GCMYIE +TCCBPUCAQEwgfIwgd0xCzAJBgNVBAYTAlVTMRcwFQYDVQQKEw5WZXJpU2lnbiwgSW5jLjEf MB0GA1UECxMWVmVyaVNpZ24gVHJ1c3QgTmV0d29yazE7MDkGA1UECxMyVGVybXMgb2YgdXNl IGF0IGh0dHBzOi8vd3d3LnZlcmlzaWduLmNvbS9ycGEgKGMpMDkxHjAcBgNVBAsTFVBlcnNv bmEgTm90IFZhbGlkYXRlZDE3MDUGA1UEAxMuVmVyaVNpZ24gQ2xhc3MgMSBJbmRpdmlkdWFs IFN1YnNjcmliZXIgQ0EgLSBHMwIQFPhbiD4unFUK+hWzYF5oBTAJBgUrDgMCGgUAoIIC2zAY BgkqhkiG9w0BCQMxCwYJKoZIhvcNAQcBMBwGCSqGSIb3DQEJBTEPFw0xMjA5MjUxMzU0NDVa MCMGCSqGSIb3DQEJBDEWBBQy3XCcaGUCCpBRDnKNV1MGfzLaizBsBgkqhkiG9w0BCQ8xXzBd MAsGCWCGSAFlAwQBKjALBglghkgBZQMEAQIwCgYIKoZIhvcNAwcwDgYIKoZIhvcNAwICAgCA MA0GCCqGSIb3DQMCAgFAMAcGBSsOAwIHMA0GCCqGSIb3DQMCAgEoMIIBAwYJKwYBBAGCNxAE MYH1MIHyMIHdMQswCQYDVQQGEwJVUzEXMBUGA1UEChMOVmVyaVNpZ24sIEluYy4xHzAdBgNV BAsTFlZlcmlTaWduIFRydXN0IE5ldHdvcmsxOzA5BgNVBAsTMlRlcm1zIG9mIHVzZSBhdCBo dHRwczovL3d3dy52ZXJpc2lnbi5jb20vcnBhIChjKTA5MR4wHAYDVQQLExVQZXJzb25hIE5v dCBWYWxpZGF0ZWQxNzA1BgNVBAMTLlZlcmlTaWduIENsYXNzIDEgSW5kaXZpZHVhbCBTdWJz Y3JpYmVyIENBIC0gRzMCEBT4W4g+LpxVCvoVs2BeaAUwggEFBgsqhkiG9w0BCRACCzGB9aCB 8jCB3TELMAkGA1UEBhMCVVMxFzAVBgNVBAoTDlZlcmlTaWduLCBJbmMuMR8wHQYDVQQLExZW ZXJpU2lnbiBUcnVzdCBOZXR3b3JrMTswOQYDVQQLEzJUZXJtcyBvZiB1c2UgYXQgaHR0cHM6 Ly93d3cudmVyaXNpZ24uY29tL3JwYSAoYykwOTEeMBwGA1UECxMVUGVyc29uYSBOb3QgVmFs aWRhdGVkMTcwNQYDVQQDEy5WZXJpU2lnbiBDbGFzcyAxIEluZGl2aWR1YWwgU3Vic2NyaWJl ciBDQSAtIEczAhAU+FuIPi6cVQr6FbNgXmgFMA0GCSqGSIb3DQEBAQUABIIBAFm0PASVLQCI CsSe6aRU4VId37MRyb59FQZOPWs2WjAOnMpQ4F5bV4+Cwd20yPRT0OBBu+0ABsCfFmoQwK5c qDrFF8F/N3t2mi8FTlEeCGcMdOdm8GFAXAip+PyYIf+h95aieiz0PzYElUGN+/R5azrdzaFK FAv4MrRng/jYLF9iM8wUPNyTuM+nLJvYh7ihODe4gOOY+446O4QEUBQ0dYTeYDFkyTPiq/Hx hEFsgLfci1XZOpiS5HSB0J3Rn01vSvTebv6LR8Fp5EAqPiBiOuaL2OTzmuMaP0GWAhMizI5k z+eD78IGmMcK5z0WHsfVNcjN99vxQAG38ATLWYdbxO8AAAAAAAA= --------------ms020105060708040909010100-- --===============3503323030232630811== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users --===============3503323030232630811==-- From xen-users-bounces@lists.xen.org Tue Sep 25 16:22:48 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Tue, 25 Sep 2012 16:22:48 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TGXtE-00023H-RW; Tue, 25 Sep 2012 16:21:40 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TGXtD-00023C-5N for xen-users@lists.xen.org; Tue, 25 Sep 2012 16:21:39 +0000 Received: from [85.158.137.99:16202] by server-14.bemta-3.messagelabs.com id 18/36-21431-21AD1605; Tue, 25 Sep 2012 16:21:38 +0000 X-Env-Sender: christine.mayapkamga@enseeiht.fr X-Msg-Ref: server-9.tower-217.messagelabs.com!1348590097!15927792!1 X-Originating-IP: [147.127.176.11] X-SpamReason: No, hits=0.0 required=7.0 tests= X-StarScan-Received: X-StarScan-Version: 6.6.1.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 3237 invoked from network); 25 Sep 2012 16:21:37 -0000 Received: from n7smtp.enseeiht.fr (HELO n7smtp.enseeiht.fr) (147.127.176.11) by server-9.tower-217.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 25 Sep 2012 16:21:37 -0000 Received: from imap.enseeiht.fr (imap.enseeiht.fr [147.127.176.21]) by n7smtp.enseeiht.fr (8.14.3/8.14.3/Debian-5+lenny1) with ESMTP id q8PGLbIK002314 for ; Tue, 25 Sep 2012 18:21:37 +0200 Received: from [147.127.240.247] (prt-mayap.enseeiht.fr [147.127.240.247]) by imap.enseeiht.fr (8.14.3/8.14.3/Debian-5+lenny1) with ESMTP id q8PGLZ7n027169 for ; Tue, 25 Sep 2012 18:21:37 +0200 Message-ID: <5061DA10.6020500@enseeiht.fr> Date: Tue, 25 Sep 2012 18:21:36 +0200 From: Christine MAYAP User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9.1.16) Gecko/20111004 Icedove/3.0.11 MIME-Version: 1.0 To: xen-users@lists.xen.org References: <5061B4B1.6020104@excello.cz> <1348580998.11229.20.camel@zakaz.uk.xensource.com> <5061B7A5.1020300@excello.cz> In-Reply-To: <5061B7A5.1020300@excello.cz> X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-3.0 (n7smtp.enseeiht.fr [147.127.176.11]); Tue, 25 Sep 2012 18:21:37 +0200 (CEST) X-Scanned-By: MIMEDefang 2.64 on 147.127.176.11 Subject: Re: [Xen-users] Error in my 'xm dmesg ' X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset="us-ascii"; Format="flowed" Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org Hello I'm currently using Xen-4.1.2 and Linux-2.6.32.57 while looking in my dmesg output, i'm always having those errors: [VT-D]iommu.c:856: iommu_fault_status: Primary Pending Fault (XEN) [VT-D]iommu.c:831: DMAR:[DMA Read] Request device [02:00.5] fault addr 425541000, iommu reg = ffff82c3fff57000 (XEN) DMAR:[fault reason 02h] Present bit in context entry is clear (XEN) print_vtd_entries: iommu = ffff83043d6875b0 bdf = 2:0.5 gmfn = 425541 (XEN) root_entry = ffff83043d633000 (XEN) root_entry[2] = 275aa6001 (XEN) context = ffff830275aa6000 (XEN) context[5] = 0_0 (XEN) ctxt_entry[5] not present I don't need VT-D. Is there a way to solve this problems! Cheers -- MAYAP Christine IRIT/ENSEEIHT 2 rue Charles Camichel - BP 7122 31071 Toulouse cedex 7 _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Tue Sep 25 16:22:48 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Tue, 25 Sep 2012 16:22:48 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TGXtE-00023H-RW; Tue, 25 Sep 2012 16:21:40 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TGXtD-00023C-5N for xen-users@lists.xen.org; Tue, 25 Sep 2012 16:21:39 +0000 Received: from [85.158.137.99:16202] by server-14.bemta-3.messagelabs.com id 18/36-21431-21AD1605; Tue, 25 Sep 2012 16:21:38 +0000 X-Env-Sender: christine.mayapkamga@enseeiht.fr X-Msg-Ref: server-9.tower-217.messagelabs.com!1348590097!15927792!1 X-Originating-IP: [147.127.176.11] X-SpamReason: No, hits=0.0 required=7.0 tests= X-StarScan-Received: X-StarScan-Version: 6.6.1.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 3237 invoked from network); 25 Sep 2012 16:21:37 -0000 Received: from n7smtp.enseeiht.fr (HELO n7smtp.enseeiht.fr) (147.127.176.11) by server-9.tower-217.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 25 Sep 2012 16:21:37 -0000 Received: from imap.enseeiht.fr (imap.enseeiht.fr [147.127.176.21]) by n7smtp.enseeiht.fr (8.14.3/8.14.3/Debian-5+lenny1) with ESMTP id q8PGLbIK002314 for ; Tue, 25 Sep 2012 18:21:37 +0200 Received: from [147.127.240.247] (prt-mayap.enseeiht.fr [147.127.240.247]) by imap.enseeiht.fr (8.14.3/8.14.3/Debian-5+lenny1) with ESMTP id q8PGLZ7n027169 for ; Tue, 25 Sep 2012 18:21:37 +0200 Message-ID: <5061DA10.6020500@enseeiht.fr> Date: Tue, 25 Sep 2012 18:21:36 +0200 From: Christine MAYAP User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9.1.16) Gecko/20111004 Icedove/3.0.11 MIME-Version: 1.0 To: xen-users@lists.xen.org References: <5061B4B1.6020104@excello.cz> <1348580998.11229.20.camel@zakaz.uk.xensource.com> <5061B7A5.1020300@excello.cz> In-Reply-To: <5061B7A5.1020300@excello.cz> X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-3.0 (n7smtp.enseeiht.fr [147.127.176.11]); Tue, 25 Sep 2012 18:21:37 +0200 (CEST) X-Scanned-By: MIMEDefang 2.64 on 147.127.176.11 Subject: Re: [Xen-users] Error in my 'xm dmesg ' X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset="us-ascii"; Format="flowed" Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org Hello I'm currently using Xen-4.1.2 and Linux-2.6.32.57 while looking in my dmesg output, i'm always having those errors: [VT-D]iommu.c:856: iommu_fault_status: Primary Pending Fault (XEN) [VT-D]iommu.c:831: DMAR:[DMA Read] Request device [02:00.5] fault addr 425541000, iommu reg = ffff82c3fff57000 (XEN) DMAR:[fault reason 02h] Present bit in context entry is clear (XEN) print_vtd_entries: iommu = ffff83043d6875b0 bdf = 2:0.5 gmfn = 425541 (XEN) root_entry = ffff83043d633000 (XEN) root_entry[2] = 275aa6001 (XEN) context = ffff830275aa6000 (XEN) context[5] = 0_0 (XEN) ctxt_entry[5] not present I don't need VT-D. Is there a way to solve this problems! Cheers -- MAYAP Christine IRIT/ENSEEIHT 2 rue Charles Camichel - BP 7122 31071 Toulouse cedex 7 _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Tue Sep 25 17:33:19 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Tue, 25 Sep 2012 17:33:19 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TGYzT-0004GE-JU; Tue, 25 Sep 2012 17:32:11 +0000 Received: from mail27.messagelabs.com ([193.109.254.147]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TGYzS-0004G3-BB for xen-users@lists.xen.org; Tue, 25 Sep 2012 17:32:10 +0000 X-Env-Sender: clovis@agr.unicamp.br X-Msg-Ref: server-15.tower-27.messagelabs.com!1348594321!5376843!1 X-Originating-IP: [143.106.74.4] X-SpamReason: No, hits=0.0 required=7.0 tests= X-StarScan-Received: X-StarScan-Version: 6.6.1.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 2357 invoked from network); 25 Sep 2012 17:32:03 -0000 Received: from mail.feagri.unicamp.br (HELO mail.feagri.unicamp.br) (143.106.74.4) by server-15.tower-27.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 25 Sep 2012 17:32:03 -0000 Received: from localhost (localhost.localdomain [127.0.0.1]) by mail.feagri.unicamp.br (Postfix) with ESMTP id 686A781C1E7 for ; Tue, 25 Sep 2012 14:32:00 -0300 (BRT) X-Virus-Scanned: amavisd-new at feagri.unicamp.br Received: from mail.feagri.unicamp.br ([127.0.0.1]) by localhost (mail.feagri.unicamp.br [127.0.0.1]) (amavisd-new, port 10024) with SMTP id 1tqONmwanN9D for ; Tue, 25 Sep 2012 14:31:59 -0300 (BRT) Received: from bambu.feagri.unicamp.br (bambu.feagri.unicamp.br [143.106.74.221]) by mail.feagri.unicamp.br (Postfix) with ESMTPA id 2A73981C1D9 for ; Tue, 25 Sep 2012 14:31:59 -0300 (BRT) Message-ID: <5061EB68.3090703@agr.unicamp.br> Date: Tue, 25 Sep 2012 14:35:36 -0300 From: Clovis Tristao Organization: Unicamp-Feagri_Sinfo User-Agent: Mozilla/5.0 (X11; Linux i686; rv:15.0) Gecko/20120911 Thunderbird/15.0.1 MIME-Version: 1.0 To: xen-users@lists.xen.org Subject: [Xen-users] VM move/copy/export X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset="iso-8859-1"; Format="flowed" Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org Hi, I have two machines with xenserver, running in the same pool with = multiple virtual machines. When I try to move / copy / export from one machine to another = xenserver, the message: Can not move virtual disks between SR site. Can = not see required storage How do I solve this problem? I'm using version 6.0.2 Thanks a lot, for any information, Cl=F3vis -- = Clovis Tristao - UNICAMP/Faculdade de Engenharia Agricola Administrador de Redes - Secao de Informatica (SINFO) E-mail: clovis@feagri.unicamp.br http://www.feagri.unicamp.br MSN: clovis_tristao33@hotmail.com Fone: 55(19) 35211031-35211038-91173116 _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Tue Sep 25 17:33:19 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Tue, 25 Sep 2012 17:33:19 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TGYzT-0004GE-JU; Tue, 25 Sep 2012 17:32:11 +0000 Received: from mail27.messagelabs.com ([193.109.254.147]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TGYzS-0004G3-BB for xen-users@lists.xen.org; Tue, 25 Sep 2012 17:32:10 +0000 X-Env-Sender: clovis@agr.unicamp.br X-Msg-Ref: server-15.tower-27.messagelabs.com!1348594321!5376843!1 X-Originating-IP: [143.106.74.4] X-SpamReason: No, hits=0.0 required=7.0 tests= X-StarScan-Received: X-StarScan-Version: 6.6.1.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 2357 invoked from network); 25 Sep 2012 17:32:03 -0000 Received: from mail.feagri.unicamp.br (HELO mail.feagri.unicamp.br) (143.106.74.4) by server-15.tower-27.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 25 Sep 2012 17:32:03 -0000 Received: from localhost (localhost.localdomain [127.0.0.1]) by mail.feagri.unicamp.br (Postfix) with ESMTP id 686A781C1E7 for ; Tue, 25 Sep 2012 14:32:00 -0300 (BRT) X-Virus-Scanned: amavisd-new at feagri.unicamp.br Received: from mail.feagri.unicamp.br ([127.0.0.1]) by localhost (mail.feagri.unicamp.br [127.0.0.1]) (amavisd-new, port 10024) with SMTP id 1tqONmwanN9D for ; Tue, 25 Sep 2012 14:31:59 -0300 (BRT) Received: from bambu.feagri.unicamp.br (bambu.feagri.unicamp.br [143.106.74.221]) by mail.feagri.unicamp.br (Postfix) with ESMTPA id 2A73981C1D9 for ; Tue, 25 Sep 2012 14:31:59 -0300 (BRT) Message-ID: <5061EB68.3090703@agr.unicamp.br> Date: Tue, 25 Sep 2012 14:35:36 -0300 From: Clovis Tristao Organization: Unicamp-Feagri_Sinfo User-Agent: Mozilla/5.0 (X11; Linux i686; rv:15.0) Gecko/20120911 Thunderbird/15.0.1 MIME-Version: 1.0 To: xen-users@lists.xen.org Subject: [Xen-users] VM move/copy/export X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset="iso-8859-1"; Format="flowed" Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org Hi, I have two machines with xenserver, running in the same pool with = multiple virtual machines. When I try to move / copy / export from one machine to another = xenserver, the message: Can not move virtual disks between SR site. Can = not see required storage How do I solve this problem? I'm using version 6.0.2 Thanks a lot, for any information, Cl=F3vis -- = Clovis Tristao - UNICAMP/Faculdade de Engenharia Agricola Administrador de Redes - Secao de Informatica (SINFO) E-mail: clovis@feagri.unicamp.br http://www.feagri.unicamp.br MSN: clovis_tristao33@hotmail.com Fone: 55(19) 35211031-35211038-91173116 _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Tue Sep 25 17:40:28 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Tue, 25 Sep 2012 17:40:28 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TGZ6c-0004lI-Qw; Tue, 25 Sep 2012 17:39:34 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TGZ6a-0004lD-LX for xen-users@lists.xen.org; Tue, 25 Sep 2012 17:39:32 +0000 Received: from [85.158.137.99:61974] by server-10.bemta-3.messagelabs.com id D3/82-10411-35CE1605; Tue, 25 Sep 2012 17:39:31 +0000 X-Env-Sender: skippyvondrake@gmail.com X-Msg-Ref: server-5.tower-217.messagelabs.com!1348594771!14348098!1 X-Originating-IP: [209.85.212.179] X-SpamReason: No, hits=0.3 required=7.0 tests=ML_RADAR_SPEW_LINKS_14, RCVD_BY_IP,spamassassin: X-StarScan-Received: X-StarScan-Version: 6.6.1.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 26735 invoked from network); 25 Sep 2012 17:39:31 -0000 Received: from mail-wi0-f179.google.com (HELO mail-wi0-f179.google.com) (209.85.212.179) by server-5.tower-217.messagelabs.com with RC4-SHA encrypted SMTP; 25 Sep 2012 17:39:31 -0000 Received: by wibhq7 with SMTP id hq7so766111wib.14 for ; Tue, 25 Sep 2012 10:39:31 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; bh=tcYSpzL9KI1CfNM9yaOrjiEDTdqrTMo/PWUZdfQcL/A=; b=Cb8OVI5gXT3+TICg8pFppvn/NatkJXVwPfoq1NEFbXmI6f0bq3n7jCivw4CGbLBjrQ Gcsblnsf8RXgkccEs6CF1ff7poazm/cTLhaeyS7Fg/ntkRpDGF7i8ch/9Lpd03LHureh M6lb26OH3XV9MlTok0CDvM1QuW1Of2EIKvFC9wyCuO7PVG2EvtyEhiLm+5IP/g31m+X5 +socZfxs6yJHmzd5TyP5rP9eg3DReIpzChLXEYTAmvyyxKbXtBW+sCyvy4KwheJIWm6U wXSFfr4KU68fsjwHMAynM4Jt8c3xKqd8EMOMeNz1CBr+7dJKuSRglzjdREYmTSF+jVJu 7MuQ== MIME-Version: 1.0 Received: by 10.180.85.99 with SMTP id g3mr9077565wiz.5.1348594771109; Tue, 25 Sep 2012 10:39:31 -0700 (PDT) Received: by 10.194.21.197 with HTTP; Tue, 25 Sep 2012 10:39:31 -0700 (PDT) In-Reply-To: <1348475895.3452.43.camel@zakaz.uk.xensource.com> References: <1348475895.3452.43.camel@zakaz.uk.xensource.com> Date: Tue, 25 Sep 2012 13:39:31 -0400 Message-ID: From: Skippy VonDrake To: xen-users@lists.xen.org Subject: Re: [Xen-users] xl cfg disk option for lvm and cdrom X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org Thanks for the help, guys. For the record my disk config worked as: disk = [ 'phy:/dev/guestsVG/xpVol,hda,w','phy:/dev/sr0,xvdc:cdrom,r' ] "Worked" as in the domain was created but I couldn't connect to it. But I'll start a new thread for that problem. Skippy On Mon, Sep 24, 2012 at 4:38 AM, Ian Campbell wrote: > On Fri, 2012-09-21 at 19:35 +0100, Skippy VonDrake wrote: >> I configured an LogicalVolume of 15G to install an XP hvm on. >> >> But I don't know how to define the 'disk' configuration for the config >> script for "xl create". >> I also don't know the format for the cdrom disk entry. > > The xl.cfg(5) man pages references docs/misc/xl-disk-configuration.txt > which defines the syntax. You can find this in the Xen source tree or > online at http://xenbits.xen.org/docs/4.2-testing/ (or .../unstable/). > > One helpful tip for debugging this sort of thing is to do > xl -N block-attach 0 > This will print out the result of parsing disk-spec (-N == dry-run) so > you can see if it looks like what you were trying to say. > > Ian. > > _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Tue Sep 25 17:40:28 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Tue, 25 Sep 2012 17:40:28 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TGZ6c-0004lI-Qw; Tue, 25 Sep 2012 17:39:34 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TGZ6a-0004lD-LX for xen-users@lists.xen.org; Tue, 25 Sep 2012 17:39:32 +0000 Received: from [85.158.137.99:61974] by server-10.bemta-3.messagelabs.com id D3/82-10411-35CE1605; Tue, 25 Sep 2012 17:39:31 +0000 X-Env-Sender: skippyvondrake@gmail.com X-Msg-Ref: server-5.tower-217.messagelabs.com!1348594771!14348098!1 X-Originating-IP: [209.85.212.179] X-SpamReason: No, hits=0.3 required=7.0 tests=ML_RADAR_SPEW_LINKS_14, RCVD_BY_IP,spamassassin: X-StarScan-Received: X-StarScan-Version: 6.6.1.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 26735 invoked from network); 25 Sep 2012 17:39:31 -0000 Received: from mail-wi0-f179.google.com (HELO mail-wi0-f179.google.com) (209.85.212.179) by server-5.tower-217.messagelabs.com with RC4-SHA encrypted SMTP; 25 Sep 2012 17:39:31 -0000 Received: by wibhq7 with SMTP id hq7so766111wib.14 for ; Tue, 25 Sep 2012 10:39:31 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; bh=tcYSpzL9KI1CfNM9yaOrjiEDTdqrTMo/PWUZdfQcL/A=; b=Cb8OVI5gXT3+TICg8pFppvn/NatkJXVwPfoq1NEFbXmI6f0bq3n7jCivw4CGbLBjrQ Gcsblnsf8RXgkccEs6CF1ff7poazm/cTLhaeyS7Fg/ntkRpDGF7i8ch/9Lpd03LHureh M6lb26OH3XV9MlTok0CDvM1QuW1Of2EIKvFC9wyCuO7PVG2EvtyEhiLm+5IP/g31m+X5 +socZfxs6yJHmzd5TyP5rP9eg3DReIpzChLXEYTAmvyyxKbXtBW+sCyvy4KwheJIWm6U wXSFfr4KU68fsjwHMAynM4Jt8c3xKqd8EMOMeNz1CBr+7dJKuSRglzjdREYmTSF+jVJu 7MuQ== MIME-Version: 1.0 Received: by 10.180.85.99 with SMTP id g3mr9077565wiz.5.1348594771109; Tue, 25 Sep 2012 10:39:31 -0700 (PDT) Received: by 10.194.21.197 with HTTP; Tue, 25 Sep 2012 10:39:31 -0700 (PDT) In-Reply-To: <1348475895.3452.43.camel@zakaz.uk.xensource.com> References: <1348475895.3452.43.camel@zakaz.uk.xensource.com> Date: Tue, 25 Sep 2012 13:39:31 -0400 Message-ID: From: Skippy VonDrake To: xen-users@lists.xen.org Subject: Re: [Xen-users] xl cfg disk option for lvm and cdrom X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org Thanks for the help, guys. For the record my disk config worked as: disk = [ 'phy:/dev/guestsVG/xpVol,hda,w','phy:/dev/sr0,xvdc:cdrom,r' ] "Worked" as in the domain was created but I couldn't connect to it. But I'll start a new thread for that problem. Skippy On Mon, Sep 24, 2012 at 4:38 AM, Ian Campbell wrote: > On Fri, 2012-09-21 at 19:35 +0100, Skippy VonDrake wrote: >> I configured an LogicalVolume of 15G to install an XP hvm on. >> >> But I don't know how to define the 'disk' configuration for the config >> script for "xl create". >> I also don't know the format for the cdrom disk entry. > > The xl.cfg(5) man pages references docs/misc/xl-disk-configuration.txt > which defines the syntax. You can find this in the Xen source tree or > online at http://xenbits.xen.org/docs/4.2-testing/ (or .../unstable/). > > One helpful tip for debugging this sort of thing is to do > xl -N block-attach 0 > This will print out the result of parsing disk-spec (-N == dry-run) so > you can see if it looks like what you were trying to say. > > Ian. > > _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Tue Sep 25 17:47:53 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Tue, 25 Sep 2012 17:47:53 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TGZDq-00055H-45; Tue, 25 Sep 2012 17:47:02 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TGZDo-00055C-Md for xen-users@lists.xen.org; Tue, 25 Sep 2012 17:47:00 +0000 Received: from [85.158.143.99:13436] by server-1.bemta-4.messagelabs.com id AE/45-05684-31EE1605; Tue, 25 Sep 2012 17:46:59 +0000 X-Env-Sender: steven.spencer@kdsi.com X-Msg-Ref: server-5.tower-216.messagelabs.com!1348595210!31401036!1 X-Originating-IP: [69.20.200.216] X-SpamReason: No, hits=0.0 required=7.0 tests=ML_RADAR_SPEW_LINKS_8, spamassassin: , async_handler: YXN5bmNfZGVsYXk6IDcwNDM0MTQgKHRpbWVvdXQp\n X-StarScan-Received: X-StarScan-Version: 6.6.1.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 7648 invoked from network); 25 Sep 2012 17:46:51 -0000 Received: from corpmeister.kdsi.net (HELO corp2.kdsi.net) (69.20.200.216) by server-5.tower-216.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 25 Sep 2012 17:46:51 -0000 Received: (qmail 6068 invoked by uid 89); 25 Sep 2012 17:46:49 -0000 Received: from unknown (HELO ?192.168.10.15?) (sspencer@corp.kdsi.net@69.20.200.19) by corp2.kdsi.net with ESMTPA; 25 Sep 2012 17:46:49 -0000 Message-ID: <5061EE09.2010307@kdsi.com> Date: Tue, 25 Sep 2012 12:46:49 -0500 From: Steven Spencer User-Agent: Mozilla/5.0 (X11; Linux i686; rv:15.0) Gecko/20120827 Thunderbird/15.0 MIME-Version: 1.0 To: xen-users@lists.xen.org Subject: [Xen-users] libvirtd problem after update to 4.2.0-1 X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset="us-ascii"; Format="flowed" Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org All, First, I know that this list is mostly for people who build Xen from source, so if you cannot help me, I guess I'll know why. I'm just hoping that I do not have to totally rebuild this server, so if you have ideas, I'd appreciate it. I took updates on one of my Xen servers today that did not go well. The server is a CentOS 6.2 machine on which Xen was built using the procedure on HowTo Forge here: http://www.howtoforge.com/virtualization-with-xen-on-centos-6.2-x86_64-paravirtualization-and-hardware-virtualization Because CentOS 6 no-longer ships with Xen support, the libvirtd had to be rebuilt and compiled using the steps outlined in the procedure. All has gone well until this update, and everything installed except that the Xend daemon complains after the Xen package is installed: Running Transaction Installing : xen-4.2.0-1.el6.x86_64 1/1 Non-fatal POSTIN scriptlet failure in rpm package xen-4.2.0-1.el6.x86_64 Stopping xend daemon: [ OK ] Starting xend daemon: [FAILED] warning: %post(xen-4.2.0-1.el6.x86_64) scriptlet failed, exit status 1 I know from past experience that the scriptlet failure is a problem with libvirt, however a check for libvirtd's status shows it running: service libvirtd status libvirtd (pid 3131) is running.. Funny thing is that the server also shows xend running: xend (pid 322) is running... [ OK ] But none of the xm commands work: xm list Error: Unable to connect to xend: Connection refused. Is xend running? and xl info shows permission denied messages and the old 4.1.2 version version still running: release : 2.6.32.57-1.el6xen.x86_64 version : #1 SMP Tue Mar 20 10:23:34 EST 2012 machine : x86_64 libxl: error: libxl.c:3628:libxl_get_physinfo: getting physinfo: Permission denied libxl_physinfo failed. libxl: error: libxl.c:3933:libxl_get_scheduler: getting domain info list: Permission denied xen_major : 4 xen_minor : 1 xen_extra : .2 xen_caps : xen-3.0-x86_64 xen-3.0-x86_32p hvm-3.0-x86_32 hvm-3.0-x86_32p hvm-3.0-x86_64 xen_scheduler : (null) xen_pagesize : 4096 platform_params : virt_start=0xffff800000000000 xen_changeset : unavailable xen_commandline : cpufreq=xen dom0_max_vcpus=1 dom0_vcpus_pin cc_compiler : gcc version 4.4.6 20110731 (Red Hat 4.4.6-3) (GCC) cc_compile_by : mockbuild cc_compile_domain : crc.id.au cc_compile_date : Mon Feb 20 12:52:37 EST 2012 xend_config_format : 4 I'm pretty sure that if I can fix the libvirt issue, all will be well, however I'm not positive. Any ideas you have would be greatly appreciated. Thanks, -- -- Steven G. Spencer, Network Administrator KSC Corporate - The Kelly Supply Family of Companies Office 308-382-8764 Ext. 231 Mobile 308-380-7957 _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Tue Sep 25 17:47:53 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Tue, 25 Sep 2012 17:47:53 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TGZDq-00055H-45; Tue, 25 Sep 2012 17:47:02 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TGZDo-00055C-Md for xen-users@lists.xen.org; Tue, 25 Sep 2012 17:47:00 +0000 Received: from [85.158.143.99:13436] by server-1.bemta-4.messagelabs.com id AE/45-05684-31EE1605; Tue, 25 Sep 2012 17:46:59 +0000 X-Env-Sender: steven.spencer@kdsi.com X-Msg-Ref: server-5.tower-216.messagelabs.com!1348595210!31401036!1 X-Originating-IP: [69.20.200.216] X-SpamReason: No, hits=0.0 required=7.0 tests=ML_RADAR_SPEW_LINKS_8, spamassassin: , async_handler: YXN5bmNfZGVsYXk6IDcwNDM0MTQgKHRpbWVvdXQp\n X-StarScan-Received: X-StarScan-Version: 6.6.1.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 7648 invoked from network); 25 Sep 2012 17:46:51 -0000 Received: from corpmeister.kdsi.net (HELO corp2.kdsi.net) (69.20.200.216) by server-5.tower-216.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 25 Sep 2012 17:46:51 -0000 Received: (qmail 6068 invoked by uid 89); 25 Sep 2012 17:46:49 -0000 Received: from unknown (HELO ?192.168.10.15?) (sspencer@corp.kdsi.net@69.20.200.19) by corp2.kdsi.net with ESMTPA; 25 Sep 2012 17:46:49 -0000 Message-ID: <5061EE09.2010307@kdsi.com> Date: Tue, 25 Sep 2012 12:46:49 -0500 From: Steven Spencer User-Agent: Mozilla/5.0 (X11; Linux i686; rv:15.0) Gecko/20120827 Thunderbird/15.0 MIME-Version: 1.0 To: xen-users@lists.xen.org Subject: [Xen-users] libvirtd problem after update to 4.2.0-1 X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset="us-ascii"; Format="flowed" Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org All, First, I know that this list is mostly for people who build Xen from source, so if you cannot help me, I guess I'll know why. I'm just hoping that I do not have to totally rebuild this server, so if you have ideas, I'd appreciate it. I took updates on one of my Xen servers today that did not go well. The server is a CentOS 6.2 machine on which Xen was built using the procedure on HowTo Forge here: http://www.howtoforge.com/virtualization-with-xen-on-centos-6.2-x86_64-paravirtualization-and-hardware-virtualization Because CentOS 6 no-longer ships with Xen support, the libvirtd had to be rebuilt and compiled using the steps outlined in the procedure. All has gone well until this update, and everything installed except that the Xend daemon complains after the Xen package is installed: Running Transaction Installing : xen-4.2.0-1.el6.x86_64 1/1 Non-fatal POSTIN scriptlet failure in rpm package xen-4.2.0-1.el6.x86_64 Stopping xend daemon: [ OK ] Starting xend daemon: [FAILED] warning: %post(xen-4.2.0-1.el6.x86_64) scriptlet failed, exit status 1 I know from past experience that the scriptlet failure is a problem with libvirt, however a check for libvirtd's status shows it running: service libvirtd status libvirtd (pid 3131) is running.. Funny thing is that the server also shows xend running: xend (pid 322) is running... [ OK ] But none of the xm commands work: xm list Error: Unable to connect to xend: Connection refused. Is xend running? and xl info shows permission denied messages and the old 4.1.2 version version still running: release : 2.6.32.57-1.el6xen.x86_64 version : #1 SMP Tue Mar 20 10:23:34 EST 2012 machine : x86_64 libxl: error: libxl.c:3628:libxl_get_physinfo: getting physinfo: Permission denied libxl_physinfo failed. libxl: error: libxl.c:3933:libxl_get_scheduler: getting domain info list: Permission denied xen_major : 4 xen_minor : 1 xen_extra : .2 xen_caps : xen-3.0-x86_64 xen-3.0-x86_32p hvm-3.0-x86_32 hvm-3.0-x86_32p hvm-3.0-x86_64 xen_scheduler : (null) xen_pagesize : 4096 platform_params : virt_start=0xffff800000000000 xen_changeset : unavailable xen_commandline : cpufreq=xen dom0_max_vcpus=1 dom0_vcpus_pin cc_compiler : gcc version 4.4.6 20110731 (Red Hat 4.4.6-3) (GCC) cc_compile_by : mockbuild cc_compile_domain : crc.id.au cc_compile_date : Mon Feb 20 12:52:37 EST 2012 xend_config_format : 4 I'm pretty sure that if I can fix the libvirt issue, all will be well, however I'm not positive. Any ideas you have would be greatly appreciated. Thanks, -- -- Steven G. Spencer, Network Administrator KSC Corporate - The Kelly Supply Family of Companies Office 308-382-8764 Ext. 231 Mobile 308-380-7957 _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Tue Sep 25 18:54:40 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Tue, 25 Sep 2012 18:54:40 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TGaGE-0006Sf-Pp; Tue, 25 Sep 2012 18:53:34 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TGaGD-0006Sa-8M for xen-users@lists.xen.org; Tue, 25 Sep 2012 18:53:33 +0000 Received: from [85.158.139.83:35319] by server-6.bemta-5.messagelabs.com id 84/F4-14717-CADF1605; Tue, 25 Sep 2012 18:53:32 +0000 X-Env-Sender: w.d.clayton@gmail.com X-Msg-Ref: server-2.tower-182.messagelabs.com!1348599209!29257849!1 X-Originating-IP: [209.85.216.45] X-SpamReason: No, hits=1.2 required=7.0 tests=HTML_10_20,HTML_MESSAGE, ML_RADAR_SPEW_LINKS_14,RCVD_BY_IP,spamassassin: X-StarScan-Received: X-StarScan-Version: 6.6.1.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 16739 invoked from network); 25 Sep 2012 18:53:30 -0000 Received: from mail-qa0-f45.google.com (HELO mail-qa0-f45.google.com) (209.85.216.45) by server-2.tower-182.messagelabs.com with RC4-SHA encrypted SMTP; 25 Sep 2012 18:53:30 -0000 Received: by qaas11 with SMTP id s11so734619qaa.11 for ; Tue, 25 Sep 2012 11:53:29 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:from:date:message-id:subject:to:content-type; bh=UPs0kXywz0x8GPej8HeeY7Z7xK/+JsZZXEm9rRx29Fw=; b=hG3zSyMfpS5wcwAXwJwat5LJ1u+VEYGMVPNaU3j7kH5aGg9G359rwGR+pggME8H+9P u7q00OaLePXdkLTUFsluzW8ZHUD+63Q5kVOWmZQU3TuhmAwsQ2L1P9fX9w417VkTXTb2 i7MIp0j5zcDgNoAC4uEWHSDGDuN5li2xn5izSFP4Bzr2saGIZASp309M35b/cdL1khEG ZyNj0HkfLwHsVeCh6yHYbvOCfMJFD5UAzt26X7b1paBhfHxM+GNiFr1Ek1rjjBiikqvG ceFk1kOQpDPGOx1QuRMunF6eYGOmTqWlJUNwyDk7hHxsasZKQFiwdQ0sQm1K/lwHU+Ep xsvg== Received: by 10.224.147.7 with SMTP id j7mr20907326qav.86.1348599209353; Tue, 25 Sep 2012 11:53:29 -0700 (PDT) MIME-Version: 1.0 Received: by 10.49.61.137 with HTTP; Tue, 25 Sep 2012 11:53:09 -0700 (PDT) From: Will Clayton Date: Tue, 25 Sep 2012 13:53:09 -0500 Message-ID: To: xen-users@lists.xen.org Subject: [Xen-users] Xen VMs stop completely instead of restarting X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============0015239532558754854==" Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org --===============0015239532558754854== Content-Type: multipart/alternative; boundary=089e0111dca6d162b904ca8b387b --089e0111dca6d162b904ca8b387b Content-Type: text/plain; charset=ISO-8859-1 I've recently upgraded SLES to use LibXenLight and have noticed that my virtual machines no longer restart when "xl restart X" or the reboot commands are used within the VM. Instead the machine seems to get destroyed. The configs for the VMs have not changed since well before the update. Here is what one looks like: name = 'vm1' maxmem =1024 memory = 1024 vcpus = 2 builder = 'linux' on_crash = 'restart' on_reboot = 'restart' on_poweroff = 'destroy' vif = [ 'bridge=br99' ] disk = [ 'tap2:aio:raw:/vms/vm1.img,xvda,w' ] bootloader = 'pygrub' I've found documentation for libxenlight to be sparse as it is. Any ideas? --089e0111dca6d162b904ca8b387b Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable I've recently upgraded SLES to use LibXenLight and have noticed that my= virtual machines no longer restart when "xl restart X" or the re= boot commands are used within the VM. Instead the machine seems to get dest= royed.

The configs for the VMs have not changed since well before the update. = Here is what one looks like:

name =3D 'vm1'
maxmem =3D102= 4
memory =3D 1024
vcpus =3D 2
builder =3D 'linux'
on_cr= ash =3D 'restart'
on_reboot =3D 'restart'
on_poweroff =3D 'destroy'
vif= =3D=A0 [ 'bridge=3Dbr99' ]
disk =3D [ 'tap2:aio:raw:/vms/vm= 1.img,xvda,w' ]
bootloader =3D 'pygrub'

I've foun= d documentation for libxenlight to be sparse as it is. Any ideas?
--089e0111dca6d162b904ca8b387b-- --===============0015239532558754854== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users --===============0015239532558754854==-- From xen-users-bounces@lists.xen.org Tue Sep 25 18:54:40 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Tue, 25 Sep 2012 18:54:40 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TGaGE-0006Sf-Pp; Tue, 25 Sep 2012 18:53:34 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TGaGD-0006Sa-8M for xen-users@lists.xen.org; Tue, 25 Sep 2012 18:53:33 +0000 Received: from [85.158.139.83:35319] by server-6.bemta-5.messagelabs.com id 84/F4-14717-CADF1605; Tue, 25 Sep 2012 18:53:32 +0000 X-Env-Sender: w.d.clayton@gmail.com X-Msg-Ref: server-2.tower-182.messagelabs.com!1348599209!29257849!1 X-Originating-IP: [209.85.216.45] X-SpamReason: No, hits=1.2 required=7.0 tests=HTML_10_20,HTML_MESSAGE, ML_RADAR_SPEW_LINKS_14,RCVD_BY_IP,spamassassin: X-StarScan-Received: X-StarScan-Version: 6.6.1.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 16739 invoked from network); 25 Sep 2012 18:53:30 -0000 Received: from mail-qa0-f45.google.com (HELO mail-qa0-f45.google.com) (209.85.216.45) by server-2.tower-182.messagelabs.com with RC4-SHA encrypted SMTP; 25 Sep 2012 18:53:30 -0000 Received: by qaas11 with SMTP id s11so734619qaa.11 for ; Tue, 25 Sep 2012 11:53:29 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:from:date:message-id:subject:to:content-type; bh=UPs0kXywz0x8GPej8HeeY7Z7xK/+JsZZXEm9rRx29Fw=; b=hG3zSyMfpS5wcwAXwJwat5LJ1u+VEYGMVPNaU3j7kH5aGg9G359rwGR+pggME8H+9P u7q00OaLePXdkLTUFsluzW8ZHUD+63Q5kVOWmZQU3TuhmAwsQ2L1P9fX9w417VkTXTb2 i7MIp0j5zcDgNoAC4uEWHSDGDuN5li2xn5izSFP4Bzr2saGIZASp309M35b/cdL1khEG ZyNj0HkfLwHsVeCh6yHYbvOCfMJFD5UAzt26X7b1paBhfHxM+GNiFr1Ek1rjjBiikqvG ceFk1kOQpDPGOx1QuRMunF6eYGOmTqWlJUNwyDk7hHxsasZKQFiwdQ0sQm1K/lwHU+Ep xsvg== Received: by 10.224.147.7 with SMTP id j7mr20907326qav.86.1348599209353; Tue, 25 Sep 2012 11:53:29 -0700 (PDT) MIME-Version: 1.0 Received: by 10.49.61.137 with HTTP; Tue, 25 Sep 2012 11:53:09 -0700 (PDT) From: Will Clayton Date: Tue, 25 Sep 2012 13:53:09 -0500 Message-ID: To: xen-users@lists.xen.org Subject: [Xen-users] Xen VMs stop completely instead of restarting X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============0015239532558754854==" Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org --===============0015239532558754854== Content-Type: multipart/alternative; boundary=089e0111dca6d162b904ca8b387b --089e0111dca6d162b904ca8b387b Content-Type: text/plain; charset=ISO-8859-1 I've recently upgraded SLES to use LibXenLight and have noticed that my virtual machines no longer restart when "xl restart X" or the reboot commands are used within the VM. Instead the machine seems to get destroyed. The configs for the VMs have not changed since well before the update. Here is what one looks like: name = 'vm1' maxmem =1024 memory = 1024 vcpus = 2 builder = 'linux' on_crash = 'restart' on_reboot = 'restart' on_poweroff = 'destroy' vif = [ 'bridge=br99' ] disk = [ 'tap2:aio:raw:/vms/vm1.img,xvda,w' ] bootloader = 'pygrub' I've found documentation for libxenlight to be sparse as it is. Any ideas? --089e0111dca6d162b904ca8b387b Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable I've recently upgraded SLES to use LibXenLight and have noticed that my= virtual machines no longer restart when "xl restart X" or the re= boot commands are used within the VM. Instead the machine seems to get dest= royed.

The configs for the VMs have not changed since well before the update. = Here is what one looks like:

name =3D 'vm1'
maxmem =3D102= 4
memory =3D 1024
vcpus =3D 2
builder =3D 'linux'
on_cr= ash =3D 'restart'
on_reboot =3D 'restart'
on_poweroff =3D 'destroy'
vif= =3D=A0 [ 'bridge=3Dbr99' ]
disk =3D [ 'tap2:aio:raw:/vms/vm= 1.img,xvda,w' ]
bootloader =3D 'pygrub'

I've foun= d documentation for libxenlight to be sparse as it is. Any ideas?
--089e0111dca6d162b904ca8b387b-- --===============0015239532558754854== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users --===============0015239532558754854==-- From xen-users-bounces@lists.xen.org Tue Sep 25 19:13:43 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Tue, 25 Sep 2012 19:13:43 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TGaYs-000768-Bm; Tue, 25 Sep 2012 19:12:50 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TGaYr-000761-AD for xen-users@lists.xen.org; Tue, 25 Sep 2012 19:12:49 +0000 Received: from [85.158.137.99:29736] by server-5.bemta-3.messagelabs.com id 8C/6A-13133-03202605; Tue, 25 Sep 2012 19:12:48 +0000 X-Env-Sender: w.d.clayton@gmail.com X-Msg-Ref: server-11.tower-217.messagelabs.com!1348600366!17903658!1 X-Originating-IP: [209.85.216.45] X-SpamReason: No, hits=1.2 required=7.0 tests=HTML_20_30,HTML_MESSAGE, ML_RADAR_SPEW_LINKS_14,RCVD_BY_IP,spamassassin: X-StarScan-Received: X-StarScan-Version: 6.6.1.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 23002 invoked from network); 25 Sep 2012 19:12:47 -0000 Received: from mail-qa0-f45.google.com (HELO mail-qa0-f45.google.com) (209.85.216.45) by server-11.tower-217.messagelabs.com with RC4-SHA encrypted SMTP; 25 Sep 2012 19:12:47 -0000 Received: by qaas11 with SMTP id s11so759420qaa.11 for ; Tue, 25 Sep 2012 12:12:46 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :content-type; bh=x75pq8XJa2lB8hNLRIkXKui0u1mcvzsJQpn9TvqiRfg=; b=l/kUrxdxJj+IA+LBPrq4Y52je/fD6vQkNAnnAjY3pk1HtlMMeSjG2mRC5wuzLPf0zJ 6xY+YViCukFa33KSiW687Jc8dbcb5/lroG0xPeH/sCn2NmjX7cj2U/NRyL6bh90c8x4J 3Pz0wmvpgnT1ALX6S7Cy8TXtxuvQO4D+Mu35zCID4hr+4trecg28BkexR6DnXePD8Psa zf2akGQiHDkJ7jw01GhwmPEXIBiaAAuNnAjt8yd4dhu2G/ouflcVIDs7NNrBz0hlV6Hk 0Q5OfE4Jjb40bQMvcTT3cSqv0+sQicJ0r58xH5ED+R2ktG2ntSIeoiUnuzCt591yO1aO pc4g== Received: by 10.229.137.145 with SMTP id w17mr11859674qct.27.1348600366240; Tue, 25 Sep 2012 12:12:46 -0700 (PDT) MIME-Version: 1.0 Received: by 10.49.61.137 with HTTP; Tue, 25 Sep 2012 12:12:25 -0700 (PDT) In-Reply-To: References: From: Will Clayton Date: Tue, 25 Sep 2012 14:12:25 -0500 Message-ID: To: xen-users@lists.xen.org Subject: Re: [Xen-users] Xen VMs stop completely instead of restarting X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============6091538831225110842==" Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org --===============6091538831225110842== Content-Type: multipart/alternative; boundary=00235452f5acc6139c04ca8b7d9e --00235452f5acc6139c04ca8b7d9e Content-Type: text/plain; charset=ISO-8859-1 For whatever reason the interesting part of my config did not make it into my post to the list. Hopefully this will get through: on_crash = 'restart' on_reboot = 'restart' on_poweroff = 'destroy' As you can see there is not much to be said about this, unless I am completely missing something - in which case a kick in the right direction towards some documentation would be greatly appreciated. On Tue, Sep 25, 2012 at 1:53 PM, Will Clayton wrote: > I've recently upgraded SLES to use LibXenLight and have noticed that my > virtual machines no longer restart when "xl restart X" or the reboot > commands are used within the VM. Instead the machine seems to get destroyed. > > The configs for the VMs have not changed since well before the update. > Here is what one looks like: > > name = 'vm1' > maxmem =1024 > memory = 1024 > vcpus = 2 > builder = 'linux' > on_crash = 'restart' > on_reboot = 'restart' > on_poweroff = 'destroy' > vif = [ 'bridge=br99' ] > disk = [ 'tap2:aio:raw:/vms/vm1.img,xvda,w' ] > bootloader = 'pygrub' > > I've found documentation for libxenlight to be sparse as it is. Any ideas? > --00235452f5acc6139c04ca8b7d9e Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable For whatever reason the interesting part of my config did not make it into = my post to the list. Hopefully this will get through:

on_crash =3D &= #39;restart'
on_reboot =3D 'restart'
on_poweroff =3D 'destroy'
As you can see there is not much to be said about this, unless I am comple= tely missing something - in which case a kick in the right direction toward= s some documentation would be greatly appreciated.

On Tue, Sep 25, 2012 at 1:53 PM, Will Clayto= n <w.d.clayton@gmail.com> wrote:
I've recently upgraded SLES to use LibXenLight and have noticed that my= virtual machines no longer restart when "xl restart X" or the re= boot commands are used within the VM. Instead the machine seems to get dest= royed.

The configs for the VMs have not changed since well before the update. = Here is what one looks like:

name =3D 'vm1'
maxmem =3D102= 4
memory =3D 1024
vcpus =3D 2
builder =3D 'linux'
on_cr= ash =3D 'restart'
on_reboot =3D 'restart'
on_poweroff =3D 'destroy'
vif= =3D=A0 [ 'bridge=3Dbr99' ]
disk =3D [ 'tap2:aio:raw:/vms/vm= 1.img,xvda,w' ]
bootloader =3D 'pygrub'

I've foun= d documentation for libxenlight to be sparse as it is. Any ideas?

--00235452f5acc6139c04ca8b7d9e-- --===============6091538831225110842== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users --===============6091538831225110842==-- From xen-users-bounces@lists.xen.org Tue Sep 25 19:13:43 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Tue, 25 Sep 2012 19:13:43 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TGaYs-000768-Bm; Tue, 25 Sep 2012 19:12:50 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TGaYr-000761-AD for xen-users@lists.xen.org; Tue, 25 Sep 2012 19:12:49 +0000 Received: from [85.158.137.99:29736] by server-5.bemta-3.messagelabs.com id 8C/6A-13133-03202605; Tue, 25 Sep 2012 19:12:48 +0000 X-Env-Sender: w.d.clayton@gmail.com X-Msg-Ref: server-11.tower-217.messagelabs.com!1348600366!17903658!1 X-Originating-IP: [209.85.216.45] X-SpamReason: No, hits=1.2 required=7.0 tests=HTML_20_30,HTML_MESSAGE, ML_RADAR_SPEW_LINKS_14,RCVD_BY_IP,spamassassin: X-StarScan-Received: X-StarScan-Version: 6.6.1.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 23002 invoked from network); 25 Sep 2012 19:12:47 -0000 Received: from mail-qa0-f45.google.com (HELO mail-qa0-f45.google.com) (209.85.216.45) by server-11.tower-217.messagelabs.com with RC4-SHA encrypted SMTP; 25 Sep 2012 19:12:47 -0000 Received: by qaas11 with SMTP id s11so759420qaa.11 for ; Tue, 25 Sep 2012 12:12:46 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :content-type; bh=x75pq8XJa2lB8hNLRIkXKui0u1mcvzsJQpn9TvqiRfg=; b=l/kUrxdxJj+IA+LBPrq4Y52je/fD6vQkNAnnAjY3pk1HtlMMeSjG2mRC5wuzLPf0zJ 6xY+YViCukFa33KSiW687Jc8dbcb5/lroG0xPeH/sCn2NmjX7cj2U/NRyL6bh90c8x4J 3Pz0wmvpgnT1ALX6S7Cy8TXtxuvQO4D+Mu35zCID4hr+4trecg28BkexR6DnXePD8Psa zf2akGQiHDkJ7jw01GhwmPEXIBiaAAuNnAjt8yd4dhu2G/ouflcVIDs7NNrBz0hlV6Hk 0Q5OfE4Jjb40bQMvcTT3cSqv0+sQicJ0r58xH5ED+R2ktG2ntSIeoiUnuzCt591yO1aO pc4g== Received: by 10.229.137.145 with SMTP id w17mr11859674qct.27.1348600366240; Tue, 25 Sep 2012 12:12:46 -0700 (PDT) MIME-Version: 1.0 Received: by 10.49.61.137 with HTTP; Tue, 25 Sep 2012 12:12:25 -0700 (PDT) In-Reply-To: References: From: Will Clayton Date: Tue, 25 Sep 2012 14:12:25 -0500 Message-ID: To: xen-users@lists.xen.org Subject: Re: [Xen-users] Xen VMs stop completely instead of restarting X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============6091538831225110842==" Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org --===============6091538831225110842== Content-Type: multipart/alternative; boundary=00235452f5acc6139c04ca8b7d9e --00235452f5acc6139c04ca8b7d9e Content-Type: text/plain; charset=ISO-8859-1 For whatever reason the interesting part of my config did not make it into my post to the list. Hopefully this will get through: on_crash = 'restart' on_reboot = 'restart' on_poweroff = 'destroy' As you can see there is not much to be said about this, unless I am completely missing something - in which case a kick in the right direction towards some documentation would be greatly appreciated. On Tue, Sep 25, 2012 at 1:53 PM, Will Clayton wrote: > I've recently upgraded SLES to use LibXenLight and have noticed that my > virtual machines no longer restart when "xl restart X" or the reboot > commands are used within the VM. Instead the machine seems to get destroyed. > > The configs for the VMs have not changed since well before the update. > Here is what one looks like: > > name = 'vm1' > maxmem =1024 > memory = 1024 > vcpus = 2 > builder = 'linux' > on_crash = 'restart' > on_reboot = 'restart' > on_poweroff = 'destroy' > vif = [ 'bridge=br99' ] > disk = [ 'tap2:aio:raw:/vms/vm1.img,xvda,w' ] > bootloader = 'pygrub' > > I've found documentation for libxenlight to be sparse as it is. Any ideas? > --00235452f5acc6139c04ca8b7d9e Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable For whatever reason the interesting part of my config did not make it into = my post to the list. Hopefully this will get through:

on_crash =3D &= #39;restart'
on_reboot =3D 'restart'
on_poweroff =3D 'destroy'
As you can see there is not much to be said about this, unless I am comple= tely missing something - in which case a kick in the right direction toward= s some documentation would be greatly appreciated.

On Tue, Sep 25, 2012 at 1:53 PM, Will Clayto= n <w.d.clayton@gmail.com> wrote:
I've recently upgraded SLES to use LibXenLight and have noticed that my= virtual machines no longer restart when "xl restart X" or the re= boot commands are used within the VM. Instead the machine seems to get dest= royed.

The configs for the VMs have not changed since well before the update. = Here is what one looks like:

name =3D 'vm1'
maxmem =3D102= 4
memory =3D 1024
vcpus =3D 2
builder =3D 'linux'
on_cr= ash =3D 'restart'
on_reboot =3D 'restart'
on_poweroff =3D 'destroy'
vif= =3D=A0 [ 'bridge=3Dbr99' ]
disk =3D [ 'tap2:aio:raw:/vms/vm= 1.img,xvda,w' ]
bootloader =3D 'pygrub'

I've foun= d documentation for libxenlight to be sparse as it is. Any ideas?

--00235452f5acc6139c04ca8b7d9e-- --===============6091538831225110842== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users --===============6091538831225110842==-- From xen-users-bounces@lists.xen.org Tue Sep 25 20:36:44 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Tue, 25 Sep 2012 20:36:44 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TGbr0-00006i-CA; Tue, 25 Sep 2012 20:35:38 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TGbqz-00006d-3I for xen-users@lists.xen.org; Tue, 25 Sep 2012 20:35:37 +0000 Received: from [85.158.137.99:61862] by server-9.bemta-3.messagelabs.com id D5/05-15390-89512605; Tue, 25 Sep 2012 20:35:36 +0000 X-Env-Sender: skippyvondrake@gmail.com X-Msg-Ref: server-15.tower-217.messagelabs.com!1348605335!16737746!1 X-Originating-IP: [74.125.82.51] X-SpamReason: No, hits=0.3 required=7.0 tests=ML_RADAR_SPEW_LINKS_14, RCVD_BY_IP,spamassassin: X-StarScan-Received: X-StarScan-Version: 6.6.1.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 24425 invoked from network); 25 Sep 2012 20:35:35 -0000 Received: from mail-wg0-f51.google.com (HELO mail-wg0-f51.google.com) (74.125.82.51) by server-15.tower-217.messagelabs.com with RC4-SHA encrypted SMTP; 25 Sep 2012 20:35:35 -0000 Received: by wgbed3 with SMTP id ed3so4597348wgb.32 for ; Tue, 25 Sep 2012 13:35:35 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:date:message-id:subject:from:to:content-type; bh=gyAZWQDfy1ZibkXn8sFaI0zXJY9W4dZTvIxCk9Pg8Rw=; b=jbL5NKRglDTvU/k1zZ81GnRtF6cPS3n8FEvoUIiPCHQJividuV4cctoz6GESf8Jcu6 r7ncxt3ww3Mr2fXI0t120i7YWynMJZeVH/SLRGnKwYefI6j3TFhQNfBHJG4cyasDreJW GekY3pnszr3hDdMX/FgzOBSNNebgibQUh1+TUMklxblvjPztRuWcBsCbB1nD2lV2snVQ jm9JIO7ka43aZ1og1L5tATZRLXld7O+My9EstY63nt7SPQHpNmw8K3CgJ/MZ+Kvp2Djr zAn1vZPEqduZEbteYwXWCWnTWGnb23qsBGzLbYZJrjziwmGk3oZ4IukfY+1/Zi7fLwAp rZcQ== MIME-Version: 1.0 Received: by 10.216.241.137 with SMTP id g9mr8674827wer.122.1348605334930; Tue, 25 Sep 2012 13:35:34 -0700 (PDT) Received: by 10.194.21.197 with HTTP; Tue, 25 Sep 2012 13:35:34 -0700 (PDT) Date: Tue, 25 Sep 2012 16:35:34 -0400 Message-ID: From: Skippy VonDrake To: "xen-users@lists.xen.org" Subject: [Xen-users] Cannot boot to cdrom (or file) using xl create for XP hvm X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org Trying to build an XP hvm using a compiled "xenified" kernel (3.5.4) but having no success reading the cdrom or an image made from the install disk. Error in vnc display: Booting from Cd-Rom... CDROM boot failure code : 0003 Boot from CD-Rom failed: could not read the boot disk No bootable device. Powering off in 30 seconds. xl -vvv create testXpOn15g.cfg Parsing config file configXL.cfg xc: info: VIRTUAL MEMORY ARRANGEMENT: Loader: 0000000000100000->0000000000172b10 TOTAL: 0000000000000000->000000003f800000 ENTRY ADDRESS: 00000000001015a0 xc: info: PHYSICAL MEMORY ALLOCATION: 4KB PAGES: 0x0000000000000200 2MB PAGES: 0x00000000000001fb 1GB PAGES: 0x0000000000000000 Daemon running with PID 11236 xc: debug: hypercall buffer: total allocations:585 total releases:585 xc: debug: hypercall buffer: current allocations:0 maximum allocations:2 xc: debug: hypercall buffer: cache current size:2 xc: debug: hypercall buffer: cache hits:582 misses:2 toobig:1 testXpOn15g.cfg contents: builder = "hvm" name = "testXpOn15g.hvm" viridian = 1 memory = 1024 vcpus = 1 vif = [ '' ] # Disk Devices #disk = [ 'phy:/dev/guestsVG/xpVol,hda,w','phy:/dev/sr0,hdc:cdrom,r' ] #disk = [ 'phy:/dev/guestsVG/xpVol,hda,w','phy:/dev/sr0,ioemu:hdc:cdrom,r' ] #disk = [ 'phy:/dev/guestsVG/xpVol,hda,w','phy:/dev/sr0,sda:cdrom,r' ] disk = [ 'phy:/dev/guestsVG/xpVol,hda,w','/home/skippy/myXpImage/xpImage.iso,hdc:cdrom,r' ] vnc = 1 boot = "d" The qemu-dm-testXpOn15g.hvm.log: domid: 22 -videoram option does not work with cirrus vga device model. Videoram set to 4M. Using file /dev/guestsVG/xpVol in read-write mode Strip off blktap sub-type prefix to (drv 'aio') Watching /local/domain/0/device-model/22/logdirty/cmd Watching /local/domain/0/device-model/22/command Watching /local/domain/22/cpu qemu_map_cache_init nr_buckets = 10000 size 4194304 shared page at pfn feffd buffered io page at pfn feffb Guest uuid = 1ce296c3-b4ba-4f01-a181-734fe2df26da populating video RAM at ff000000 mapping video RAM from ff000000 Register xen platform. Done register platform. platform_fixed_ioport: changed ro/rw state of ROM memory area. now is rw state. xs_read(/local/domain/0/device-model/22/xen_extended_power_mgmt): read error xs_read(): vncpasswd get error. /vm/1ce296c3-b4ba-4f01-a181-734fe2df26da/vncpasswd. medium change watch on `hdc' (index: 1): aio: I/O request not ready: 0, ptr: 0, port: 0, data: 0, count: 0, size: 0 Log-dirty: no command yet. vcpu-set: watch node error. xs_read(/local/domain/22/log-throttling): read error qemu: ignoring not-understood drive `/local/domain/22/log-throttling' medium change watch on `/local/domain/22/log-throttling' - unknown device, ignored cirrus vga map change while on lfb mode mapping vram to f0000000 - f0400000 platform_fixed_ioport: changed ro/rw state of ROM memory area. now is rw state. platform_fixed_ioport: changed ro/rw state of ROM memory area. now is ro state. The xl-testXpOn15g.hvm.log: Waiting for domain testXpOn15g.hvm (domid 22) to die [pid 11237] Domain 22 is dead Action for shutdown reason code 0 is destroy Domain 22 needs to be cleaned up: destroying the domain libxl: debug: libxl_dm.c:761:libxl__destroy_device_model Device Model signaled Done. Exiting now Suggestions? I've used this XP install cd several times and know it's good. _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Tue Sep 25 20:36:44 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Tue, 25 Sep 2012 20:36:44 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TGbr0-00006i-CA; Tue, 25 Sep 2012 20:35:38 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TGbqz-00006d-3I for xen-users@lists.xen.org; Tue, 25 Sep 2012 20:35:37 +0000 Received: from [85.158.137.99:61862] by server-9.bemta-3.messagelabs.com id D5/05-15390-89512605; Tue, 25 Sep 2012 20:35:36 +0000 X-Env-Sender: skippyvondrake@gmail.com X-Msg-Ref: server-15.tower-217.messagelabs.com!1348605335!16737746!1 X-Originating-IP: [74.125.82.51] X-SpamReason: No, hits=0.3 required=7.0 tests=ML_RADAR_SPEW_LINKS_14, RCVD_BY_IP,spamassassin: X-StarScan-Received: X-StarScan-Version: 6.6.1.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 24425 invoked from network); 25 Sep 2012 20:35:35 -0000 Received: from mail-wg0-f51.google.com (HELO mail-wg0-f51.google.com) (74.125.82.51) by server-15.tower-217.messagelabs.com with RC4-SHA encrypted SMTP; 25 Sep 2012 20:35:35 -0000 Received: by wgbed3 with SMTP id ed3so4597348wgb.32 for ; Tue, 25 Sep 2012 13:35:35 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:date:message-id:subject:from:to:content-type; bh=gyAZWQDfy1ZibkXn8sFaI0zXJY9W4dZTvIxCk9Pg8Rw=; b=jbL5NKRglDTvU/k1zZ81GnRtF6cPS3n8FEvoUIiPCHQJividuV4cctoz6GESf8Jcu6 r7ncxt3ww3Mr2fXI0t120i7YWynMJZeVH/SLRGnKwYefI6j3TFhQNfBHJG4cyasDreJW GekY3pnszr3hDdMX/FgzOBSNNebgibQUh1+TUMklxblvjPztRuWcBsCbB1nD2lV2snVQ jm9JIO7ka43aZ1og1L5tATZRLXld7O+My9EstY63nt7SPQHpNmw8K3CgJ/MZ+Kvp2Djr zAn1vZPEqduZEbteYwXWCWnTWGnb23qsBGzLbYZJrjziwmGk3oZ4IukfY+1/Zi7fLwAp rZcQ== MIME-Version: 1.0 Received: by 10.216.241.137 with SMTP id g9mr8674827wer.122.1348605334930; Tue, 25 Sep 2012 13:35:34 -0700 (PDT) Received: by 10.194.21.197 with HTTP; Tue, 25 Sep 2012 13:35:34 -0700 (PDT) Date: Tue, 25 Sep 2012 16:35:34 -0400 Message-ID: From: Skippy VonDrake To: "xen-users@lists.xen.org" Subject: [Xen-users] Cannot boot to cdrom (or file) using xl create for XP hvm X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org Trying to build an XP hvm using a compiled "xenified" kernel (3.5.4) but having no success reading the cdrom or an image made from the install disk. Error in vnc display: Booting from Cd-Rom... CDROM boot failure code : 0003 Boot from CD-Rom failed: could not read the boot disk No bootable device. Powering off in 30 seconds. xl -vvv create testXpOn15g.cfg Parsing config file configXL.cfg xc: info: VIRTUAL MEMORY ARRANGEMENT: Loader: 0000000000100000->0000000000172b10 TOTAL: 0000000000000000->000000003f800000 ENTRY ADDRESS: 00000000001015a0 xc: info: PHYSICAL MEMORY ALLOCATION: 4KB PAGES: 0x0000000000000200 2MB PAGES: 0x00000000000001fb 1GB PAGES: 0x0000000000000000 Daemon running with PID 11236 xc: debug: hypercall buffer: total allocations:585 total releases:585 xc: debug: hypercall buffer: current allocations:0 maximum allocations:2 xc: debug: hypercall buffer: cache current size:2 xc: debug: hypercall buffer: cache hits:582 misses:2 toobig:1 testXpOn15g.cfg contents: builder = "hvm" name = "testXpOn15g.hvm" viridian = 1 memory = 1024 vcpus = 1 vif = [ '' ] # Disk Devices #disk = [ 'phy:/dev/guestsVG/xpVol,hda,w','phy:/dev/sr0,hdc:cdrom,r' ] #disk = [ 'phy:/dev/guestsVG/xpVol,hda,w','phy:/dev/sr0,ioemu:hdc:cdrom,r' ] #disk = [ 'phy:/dev/guestsVG/xpVol,hda,w','phy:/dev/sr0,sda:cdrom,r' ] disk = [ 'phy:/dev/guestsVG/xpVol,hda,w','/home/skippy/myXpImage/xpImage.iso,hdc:cdrom,r' ] vnc = 1 boot = "d" The qemu-dm-testXpOn15g.hvm.log: domid: 22 -videoram option does not work with cirrus vga device model. Videoram set to 4M. Using file /dev/guestsVG/xpVol in read-write mode Strip off blktap sub-type prefix to (drv 'aio') Watching /local/domain/0/device-model/22/logdirty/cmd Watching /local/domain/0/device-model/22/command Watching /local/domain/22/cpu qemu_map_cache_init nr_buckets = 10000 size 4194304 shared page at pfn feffd buffered io page at pfn feffb Guest uuid = 1ce296c3-b4ba-4f01-a181-734fe2df26da populating video RAM at ff000000 mapping video RAM from ff000000 Register xen platform. Done register platform. platform_fixed_ioport: changed ro/rw state of ROM memory area. now is rw state. xs_read(/local/domain/0/device-model/22/xen_extended_power_mgmt): read error xs_read(): vncpasswd get error. /vm/1ce296c3-b4ba-4f01-a181-734fe2df26da/vncpasswd. medium change watch on `hdc' (index: 1): aio: I/O request not ready: 0, ptr: 0, port: 0, data: 0, count: 0, size: 0 Log-dirty: no command yet. vcpu-set: watch node error. xs_read(/local/domain/22/log-throttling): read error qemu: ignoring not-understood drive `/local/domain/22/log-throttling' medium change watch on `/local/domain/22/log-throttling' - unknown device, ignored cirrus vga map change while on lfb mode mapping vram to f0000000 - f0400000 platform_fixed_ioport: changed ro/rw state of ROM memory area. now is rw state. platform_fixed_ioport: changed ro/rw state of ROM memory area. now is ro state. The xl-testXpOn15g.hvm.log: Waiting for domain testXpOn15g.hvm (domid 22) to die [pid 11237] Domain 22 is dead Action for shutdown reason code 0 is destroy Domain 22 needs to be cleaned up: destroying the domain libxl: debug: libxl_dm.c:761:libxl__destroy_device_model Device Model signaled Done. Exiting now Suggestions? I've used this XP install cd several times and know it's good. _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Tue Sep 25 21:18:06 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Tue, 25 Sep 2012 21:18:06 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TGcV0-0000lT-9S; Tue, 25 Sep 2012 21:16:58 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TGcUy-0000lJ-Eh for xen-users@lists.xen.org; Tue, 25 Sep 2012 21:16:56 +0000 Received: from [85.158.139.211:64014] by server-11.bemta-5.messagelabs.com id 97/BC-13866-74F12605; Tue, 25 Sep 2012 21:16:55 +0000 X-Env-Sender: jh@excello.cz X-Msg-Ref: server-9.tower-206.messagelabs.com!1348607814!18435693!1 X-Originating-IP: [91.121.238.116] X-SpamReason: No, hits=0.0 required=7.0 tests=UNPARSEABLE_RELAY X-StarScan-Received: X-StarScan-Version: 6.6.1.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 21010 invoked from network); 25 Sep 2012 21:16:54 -0000 Received: from out1.virusfree.cz (HELO out1.virusfree.cz) (91.121.238.116) by server-9.tower-206.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 25 Sep 2012 21:16:54 -0000 Received: (qmail 18615 invoked by uid 210); 25 Sep 2012 23:16:54 +0200 Received: from smtp.excello.cz by out1 (envelope-from , uid 201) with VF-scanner-2.08VF (www.virusfree.cz : out1.virusfree.cz Clear:RC:1(91.121.238.113):SA:0(-7.6/5.0):. Processed in 1.503405 secs); 25 Sep 2012 21:16:54 -0000 X-Spam-Status: No, hits=-7.6 required=5.0 X-Spam-Report: SA TESTS 0.1 MAILBODYHTTPLINK RAW: http:// v body 0.5 MAILBOX_SIZE RAW: Describing mailbox size -4.0 INREPLYTOCOM INREPLYTOCOM -1.5 INREPLYTO0 INREPLYTO0 -0.0 SPF_PASS SPF: sender matches SPF record -0.8 RP_MATCHES_RCVD Envelope sender domain matches handover relay domain 1.0 SPF_HELO_FAIL SPF: HELO does not match SPF record (fail) [SPF failed: Please see http://www.openspf.net/Why?s=helo; id=smtp.excello.cz; ip=91.121.238.113; r=aq.virusfree.cz] 0.8 BAYES_50 BODY: Bayes spam probability is 40 to 60% [score: 0.5839] -0.1 DKIM_VALID_AU Message has a valid DKIM or DK signature from author's domain -0.1 DKIM_VALID Message has at least one valid DKIM or DK signature 0.1 DKIM_SIGNED Message has a DKIM or DK signature, not necessarily valid -3.7 CRM114_CHECK CRM114: message is GOOD with crm114-score 14.6800 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=excello.cz; h= date:message-id:from:to:subject:reply-to; q=dns/txt; s=default; t=1348607812; n=Test; bh=ET/Fh+B3k75IB0CEkUWoyV2AS4FUgdAVMcc3Ru IaBJM=; b=UT4Eg7u12PULWLsc0Qiyu5Hz0is46/Ij4hivCjXeSIzRRI9mAyx326 mLwUq79Gu2ekY3M5hdBtuCM6VDPboPbTAUXlYbzrm4sHX3h1hhkZU3RY8EHftS/8 OCN2zbbtEW DomainKey-Signature: a=rsa-sha1; c=nofws; d=excello.cz; h=message-id :date:from:mime-version:to:subject:references:in-reply-to :content-type:content-transfer-encoding; q=dns; s=default; b=Zu1 VuO6WVagx5/IwFiHntcyjBm3S8L6zbexgzhdM4CKfkUNfDcYaToDzXOsQZd0xFfA Ypq6YhZnBwoLQdp03EXZK4Scuq2qAF4MshKHweide8GBuEHy/qCfnx+Z+NxCu Received: from smtp.excello.cz (91.121.238.113) by out1.virusfree.cz with SMTP; 25 Sep 2012 23:16:51 +0200 Received: from [192.168.1.167] (unknown [37.77.238.87]) by smtp.excello.cz (Postfix) with ESMTPA id 86E4F81C522E for ; Tue, 25 Sep 2012 23:16:51 +0200 (CEST) Message-ID: <50621F43.8060701@excello.cz> Date: Tue, 25 Sep 2012 23:16:51 +0200 From: Jan Hejl User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:13.0) Gecko/20120615 Thunderbird/13.0.1 MIME-Version: 1.0 To: xen-users@lists.xen.org References: In-Reply-To: Subject: Re: [Xen-users] Cannot boot to cdrom (or file) using xl create for XP hvm X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset="us-ascii"; Format="flowed" Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org Try add "xen_platform_pci=1" line to config file. On 25.9.2012 22:35, Skippy VonDrake wrote: > Trying to build an XP hvm using a compiled "xenified" kernel > (3.5.4) but having no success reading the cdrom or an image > made from the install disk. > > Error in vnc display: > Booting from Cd-Rom... > CDROM boot failure code : 0003 > Boot from CD-Rom failed: could not read the boot disk > No bootable device. Powering off in 30 seconds. > > xl -vvv create testXpOn15g.cfg > Parsing config file configXL.cfg > xc: info: VIRTUAL MEMORY ARRANGEMENT: > Loader: 0000000000100000->0000000000172b10 > TOTAL: 0000000000000000->000000003f800000 > ENTRY ADDRESS: 00000000001015a0 > xc: info: PHYSICAL MEMORY ALLOCATION: > 4KB PAGES: 0x0000000000000200 > 2MB PAGES: 0x00000000000001fb > 1GB PAGES: 0x0000000000000000 > Daemon running with PID 11236 > xc: debug: hypercall buffer: total allocations:585 total releases:585 > xc: debug: hypercall buffer: current allocations:0 maximum allocations:2 > xc: debug: hypercall buffer: cache current size:2 > xc: debug: hypercall buffer: cache hits:582 misses:2 toobig:1 > > testXpOn15g.cfg contents: > builder = "hvm" > name = "testXpOn15g.hvm" > viridian = 1 > memory = 1024 > vcpus = 1 > vif = [ '' ] > # Disk Devices > #disk = [ 'phy:/dev/guestsVG/xpVol,hda,w','phy:/dev/sr0,hdc:cdrom,r' ] > #disk = [ 'phy:/dev/guestsVG/xpVol,hda,w','phy:/dev/sr0,ioemu:hdc:cdrom,r' ] > #disk = [ 'phy:/dev/guestsVG/xpVol,hda,w','phy:/dev/sr0,sda:cdrom,r' ] > disk = [ 'phy:/dev/guestsVG/xpVol,hda,w','/home/skippy/myXpImage/xpImage.iso,hdc:cdrom,r' > ] > vnc = 1 > boot = "d" > > The qemu-dm-testXpOn15g.hvm.log: > domid: 22 > -videoram option does not work with cirrus vga device model. Videoram set to 4M. > Using file /dev/guestsVG/xpVol in read-write mode > Strip off blktap sub-type prefix to (drv 'aio') > Watching /local/domain/0/device-model/22/logdirty/cmd > Watching /local/domain/0/device-model/22/command > Watching /local/domain/22/cpu > qemu_map_cache_init nr_buckets = 10000 size 4194304 > shared page at pfn feffd > buffered io page at pfn feffb > Guest uuid = 1ce296c3-b4ba-4f01-a181-734fe2df26da > populating video RAM at ff000000 > mapping video RAM from ff000000 > Register xen platform. > Done register platform. > platform_fixed_ioport: changed ro/rw state of ROM memory area. now is rw state. > xs_read(/local/domain/0/device-model/22/xen_extended_power_mgmt): read error > xs_read(): vncpasswd get error. > /vm/1ce296c3-b4ba-4f01-a181-734fe2df26da/vncpasswd. > medium change watch on `hdc' (index: 1): aio: > I/O request not ready: 0, ptr: 0, port: 0, data: 0, count: 0, size: 0 > Log-dirty: no command yet. > vcpu-set: watch node error. > xs_read(/local/domain/22/log-throttling): read error > qemu: ignoring not-understood drive `/local/domain/22/log-throttling' > medium change watch on `/local/domain/22/log-throttling' - unknown > device, ignored > cirrus vga map change while on lfb mode > mapping vram to f0000000 - f0400000 > platform_fixed_ioport: changed ro/rw state of ROM memory area. now is rw state. > platform_fixed_ioport: changed ro/rw state of ROM memory area. now is ro state. > > The xl-testXpOn15g.hvm.log: > Waiting for domain testXpOn15g.hvm (domid 22) to die [pid 11237] > Domain 22 is dead > Action for shutdown reason code 0 is destroy > Domain 22 needs to be cleaned up: destroying the domain > libxl: debug: libxl_dm.c:761:libxl__destroy_device_model Device Model signaled > Done. Exiting now > > Suggestions? I've used this XP install cd several times and know > it's good. > > _______________________________________________ > Xen-users mailing list > Xen-users@lists.xen.org > http://lists.xen.org/xen-users _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Tue Sep 25 21:18:06 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Tue, 25 Sep 2012 21:18:06 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TGcV0-0000lT-9S; Tue, 25 Sep 2012 21:16:58 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TGcUy-0000lJ-Eh for xen-users@lists.xen.org; Tue, 25 Sep 2012 21:16:56 +0000 Received: from [85.158.139.211:64014] by server-11.bemta-5.messagelabs.com id 97/BC-13866-74F12605; Tue, 25 Sep 2012 21:16:55 +0000 X-Env-Sender: jh@excello.cz X-Msg-Ref: server-9.tower-206.messagelabs.com!1348607814!18435693!1 X-Originating-IP: [91.121.238.116] X-SpamReason: No, hits=0.0 required=7.0 tests=UNPARSEABLE_RELAY X-StarScan-Received: X-StarScan-Version: 6.6.1.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 21010 invoked from network); 25 Sep 2012 21:16:54 -0000 Received: from out1.virusfree.cz (HELO out1.virusfree.cz) (91.121.238.116) by server-9.tower-206.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 25 Sep 2012 21:16:54 -0000 Received: (qmail 18615 invoked by uid 210); 25 Sep 2012 23:16:54 +0200 Received: from smtp.excello.cz by out1 (envelope-from , uid 201) with VF-scanner-2.08VF (www.virusfree.cz : out1.virusfree.cz Clear:RC:1(91.121.238.113):SA:0(-7.6/5.0):. Processed in 1.503405 secs); 25 Sep 2012 21:16:54 -0000 X-Spam-Status: No, hits=-7.6 required=5.0 X-Spam-Report: SA TESTS 0.1 MAILBODYHTTPLINK RAW: http:// v body 0.5 MAILBOX_SIZE RAW: Describing mailbox size -4.0 INREPLYTOCOM INREPLYTOCOM -1.5 INREPLYTO0 INREPLYTO0 -0.0 SPF_PASS SPF: sender matches SPF record -0.8 RP_MATCHES_RCVD Envelope sender domain matches handover relay domain 1.0 SPF_HELO_FAIL SPF: HELO does not match SPF record (fail) [SPF failed: Please see http://www.openspf.net/Why?s=helo; id=smtp.excello.cz; ip=91.121.238.113; r=aq.virusfree.cz] 0.8 BAYES_50 BODY: Bayes spam probability is 40 to 60% [score: 0.5839] -0.1 DKIM_VALID_AU Message has a valid DKIM or DK signature from author's domain -0.1 DKIM_VALID Message has at least one valid DKIM or DK signature 0.1 DKIM_SIGNED Message has a DKIM or DK signature, not necessarily valid -3.7 CRM114_CHECK CRM114: message is GOOD with crm114-score 14.6800 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=excello.cz; h= date:message-id:from:to:subject:reply-to; q=dns/txt; s=default; t=1348607812; n=Test; bh=ET/Fh+B3k75IB0CEkUWoyV2AS4FUgdAVMcc3Ru IaBJM=; b=UT4Eg7u12PULWLsc0Qiyu5Hz0is46/Ij4hivCjXeSIzRRI9mAyx326 mLwUq79Gu2ekY3M5hdBtuCM6VDPboPbTAUXlYbzrm4sHX3h1hhkZU3RY8EHftS/8 OCN2zbbtEW DomainKey-Signature: a=rsa-sha1; c=nofws; d=excello.cz; h=message-id :date:from:mime-version:to:subject:references:in-reply-to :content-type:content-transfer-encoding; q=dns; s=default; b=Zu1 VuO6WVagx5/IwFiHntcyjBm3S8L6zbexgzhdM4CKfkUNfDcYaToDzXOsQZd0xFfA Ypq6YhZnBwoLQdp03EXZK4Scuq2qAF4MshKHweide8GBuEHy/qCfnx+Z+NxCu Received: from smtp.excello.cz (91.121.238.113) by out1.virusfree.cz with SMTP; 25 Sep 2012 23:16:51 +0200 Received: from [192.168.1.167] (unknown [37.77.238.87]) by smtp.excello.cz (Postfix) with ESMTPA id 86E4F81C522E for ; Tue, 25 Sep 2012 23:16:51 +0200 (CEST) Message-ID: <50621F43.8060701@excello.cz> Date: Tue, 25 Sep 2012 23:16:51 +0200 From: Jan Hejl User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:13.0) Gecko/20120615 Thunderbird/13.0.1 MIME-Version: 1.0 To: xen-users@lists.xen.org References: In-Reply-To: Subject: Re: [Xen-users] Cannot boot to cdrom (or file) using xl create for XP hvm X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset="us-ascii"; Format="flowed" Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org Try add "xen_platform_pci=1" line to config file. On 25.9.2012 22:35, Skippy VonDrake wrote: > Trying to build an XP hvm using a compiled "xenified" kernel > (3.5.4) but having no success reading the cdrom or an image > made from the install disk. > > Error in vnc display: > Booting from Cd-Rom... > CDROM boot failure code : 0003 > Boot from CD-Rom failed: could not read the boot disk > No bootable device. Powering off in 30 seconds. > > xl -vvv create testXpOn15g.cfg > Parsing config file configXL.cfg > xc: info: VIRTUAL MEMORY ARRANGEMENT: > Loader: 0000000000100000->0000000000172b10 > TOTAL: 0000000000000000->000000003f800000 > ENTRY ADDRESS: 00000000001015a0 > xc: info: PHYSICAL MEMORY ALLOCATION: > 4KB PAGES: 0x0000000000000200 > 2MB PAGES: 0x00000000000001fb > 1GB PAGES: 0x0000000000000000 > Daemon running with PID 11236 > xc: debug: hypercall buffer: total allocations:585 total releases:585 > xc: debug: hypercall buffer: current allocations:0 maximum allocations:2 > xc: debug: hypercall buffer: cache current size:2 > xc: debug: hypercall buffer: cache hits:582 misses:2 toobig:1 > > testXpOn15g.cfg contents: > builder = "hvm" > name = "testXpOn15g.hvm" > viridian = 1 > memory = 1024 > vcpus = 1 > vif = [ '' ] > # Disk Devices > #disk = [ 'phy:/dev/guestsVG/xpVol,hda,w','phy:/dev/sr0,hdc:cdrom,r' ] > #disk = [ 'phy:/dev/guestsVG/xpVol,hda,w','phy:/dev/sr0,ioemu:hdc:cdrom,r' ] > #disk = [ 'phy:/dev/guestsVG/xpVol,hda,w','phy:/dev/sr0,sda:cdrom,r' ] > disk = [ 'phy:/dev/guestsVG/xpVol,hda,w','/home/skippy/myXpImage/xpImage.iso,hdc:cdrom,r' > ] > vnc = 1 > boot = "d" > > The qemu-dm-testXpOn15g.hvm.log: > domid: 22 > -videoram option does not work with cirrus vga device model. Videoram set to 4M. > Using file /dev/guestsVG/xpVol in read-write mode > Strip off blktap sub-type prefix to (drv 'aio') > Watching /local/domain/0/device-model/22/logdirty/cmd > Watching /local/domain/0/device-model/22/command > Watching /local/domain/22/cpu > qemu_map_cache_init nr_buckets = 10000 size 4194304 > shared page at pfn feffd > buffered io page at pfn feffb > Guest uuid = 1ce296c3-b4ba-4f01-a181-734fe2df26da > populating video RAM at ff000000 > mapping video RAM from ff000000 > Register xen platform. > Done register platform. > platform_fixed_ioport: changed ro/rw state of ROM memory area. now is rw state. > xs_read(/local/domain/0/device-model/22/xen_extended_power_mgmt): read error > xs_read(): vncpasswd get error. > /vm/1ce296c3-b4ba-4f01-a181-734fe2df26da/vncpasswd. > medium change watch on `hdc' (index: 1): aio: > I/O request not ready: 0, ptr: 0, port: 0, data: 0, count: 0, size: 0 > Log-dirty: no command yet. > vcpu-set: watch node error. > xs_read(/local/domain/22/log-throttling): read error > qemu: ignoring not-understood drive `/local/domain/22/log-throttling' > medium change watch on `/local/domain/22/log-throttling' - unknown > device, ignored > cirrus vga map change while on lfb mode > mapping vram to f0000000 - f0400000 > platform_fixed_ioport: changed ro/rw state of ROM memory area. now is rw state. > platform_fixed_ioport: changed ro/rw state of ROM memory area. now is ro state. > > The xl-testXpOn15g.hvm.log: > Waiting for domain testXpOn15g.hvm (domid 22) to die [pid 11237] > Domain 22 is dead > Action for shutdown reason code 0 is destroy > Domain 22 needs to be cleaned up: destroying the domain > libxl: debug: libxl_dm.c:761:libxl__destroy_device_model Device Model signaled > Done. Exiting now > > Suggestions? I've used this XP install cd several times and know > it's good. > > _______________________________________________ > Xen-users mailing list > Xen-users@lists.xen.org > http://lists.xen.org/xen-users _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Tue Sep 25 21:42:45 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Tue, 25 Sep 2012 21:42:45 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TGcsz-0001Yv-3C; Tue, 25 Sep 2012 21:41:45 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TGcsx-0001Yf-La for xen-users@lists.xen.org; Tue, 25 Sep 2012 21:41:44 +0000 Received: from [85.158.137.99:22384] by server-15.bemta-3.messagelabs.com id BA/0C-09665-61522605; Tue, 25 Sep 2012 21:41:42 +0000 X-Env-Sender: jh@excello.cz X-Msg-Ref: server-8.tower-217.messagelabs.com!1348609301!13749742!1 X-Originating-IP: [91.121.238.116] X-SpamReason: No, hits=0.0 required=7.0 tests=UNPARSEABLE_RELAY X-StarScan-Received: X-StarScan-Version: 6.6.1.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 9507 invoked from network); 25 Sep 2012 21:41:42 -0000 Received: from out1.virusfree.cz (HELO out1.virusfree.cz) (91.121.238.116) by server-8.tower-217.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 25 Sep 2012 21:41:42 -0000 Received: (qmail 20863 invoked by uid 210); 25 Sep 2012 23:41:39 +0200 Received: from smtp.excello.cz by out1 (envelope-from , uid 201) with VF-scanner-2.08VF (www.virusfree.cz : out1.virusfree.cz Clear:RC:1(91.121.238.113):SA:0(-9.4/5.0):. Processed in 2.300937 secs); 25 Sep 2012 21:41:39 -0000 X-Spam-Status: No, hits=-9.4 required=5.0 X-Spam-Report: SA TESTS 0.1 MAILBODYHTTPLINK RAW: http:// v body 0.5 MAILBOX_SIZE RAW: Describing mailbox size -4.9 BAYES_00 BODY: Bayes spam probability is 0 to 1% [score: 0.0005] -4.0 INREPLYTOCOM INREPLYTOCOM -1.5 INREPLYTO0 INREPLYTO0 -0.0 SPF_PASS SPF: sender matches SPF record -0.6 RP_MATCHES_RCVD Envelope sender domain matches handover relay domain 1.0 SPF_HELO_FAIL SPF: HELO does not match SPF record (fail) [SPF failed: Please see http://www.openspf.net/Why?s=helo; id=smtp.excello.cz; ip=91.121.238.113; r=bq.virusfree.cz] -0.1 DKIM_VALID_AU Message has a valid DKIM or DK signature from author's domain -0.1 DKIM_VALID Message has at least one valid DKIM or DK signature 0.1 DKIM_SIGNED Message has a DKIM or DK signature, not necessarily valid DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=excello.cz; h= date:message-id:from:to:subject:reply-to; q=dns/txt; s=default; t=1348609297; n=Test; bh=sz2r8x0WXPN9OvaegFbQvOiCIHORNlHsHUWQNC LFEAM=; b=qiRmkHNKdr2n9UKD5iybTLgl+Avt2kJHV43FqbB+hY52ixCTVCS56j OvhoMM50+YuD1L3rVOZUifWUqWrrBK8CMf0yBv+sqML88vYDj3XYs1hYz+6ma7fP O2adj/dJEh DomainKey-Signature: a=rsa-sha1; c=nofws; d=excello.cz; h=message-id :date:from:mime-version:to:subject:references:in-reply-to :content-type:content-transfer-encoding; q=dns; s=default; b=a9f 0N2EchgLD+1J839IM+xBLouRYfNmnR8l3ycpx8GBcCpy6Co2NMNg8qFlPHOcnMuo 47NBnxc09wGfs/aEwSB0zVmFtj4myZYWqkUglYHb20xUFwalujqEvs8/1690i Received: from smtp.excello.cz (91.121.238.113) by out1.virusfree.cz with SMTP; 25 Sep 2012 23:41:36 +0200 Received: from [192.168.1.167] (unknown [37.77.238.87]) by smtp.excello.cz (Postfix) with ESMTPA id DAF8481C5254 for ; Tue, 25 Sep 2012 23:41:34 +0200 (CEST) Message-ID: <5062250F.9010006@excello.cz> Date: Tue, 25 Sep 2012 23:41:35 +0200 From: Jan Hejl User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:13.0) Gecko/20120615 Thunderbird/13.0.1 MIME-Version: 1.0 To: xen-users@lists.xen.org References: In-Reply-To: Subject: Re: [Xen-users] Cannot boot to cdrom (or file) using xl create for XP hvm X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset="us-ascii"; Format="flowed" Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org Changing this line: '/home/skippy/myXpImage/xpImage.iso,hdc:cdrom,r' to this: 'file:/home/skippy/myXpImage/xpImage.iso,hdc:cdrom,r' (added file: directive) did the magic. Jan On 25.9.2012 22:35, Skippy VonDrake wrote: > Trying to build an XP hvm using a compiled "xenified" kernel > (3.5.4) but having no success reading the cdrom or an image > made from the install disk. > > Error in vnc display: > Booting from Cd-Rom... > CDROM boot failure code : 0003 > Boot from CD-Rom failed: could not read the boot disk > No bootable device. Powering off in 30 seconds. > > xl -vvv create testXpOn15g.cfg > Parsing config file configXL.cfg > xc: info: VIRTUAL MEMORY ARRANGEMENT: > Loader: 0000000000100000->0000000000172b10 > TOTAL: 0000000000000000->000000003f800000 > ENTRY ADDRESS: 00000000001015a0 > xc: info: PHYSICAL MEMORY ALLOCATION: > 4KB PAGES: 0x0000000000000200 > 2MB PAGES: 0x00000000000001fb > 1GB PAGES: 0x0000000000000000 > Daemon running with PID 11236 > xc: debug: hypercall buffer: total allocations:585 total releases:585 > xc: debug: hypercall buffer: current allocations:0 maximum allocations:2 > xc: debug: hypercall buffer: cache current size:2 > xc: debug: hypercall buffer: cache hits:582 misses:2 toobig:1 > > testXpOn15g.cfg contents: > builder = "hvm" > name = "testXpOn15g.hvm" > viridian = 1 > memory = 1024 > vcpus = 1 > vif = [ '' ] > # Disk Devices > #disk = [ 'phy:/dev/guestsVG/xpVol,hda,w','phy:/dev/sr0,hdc:cdrom,r' ] > #disk = [ 'phy:/dev/guestsVG/xpVol,hda,w','phy:/dev/sr0,ioemu:hdc:cdrom,r' ] > #disk = [ 'phy:/dev/guestsVG/xpVol,hda,w','phy:/dev/sr0,sda:cdrom,r' ] > disk = [ 'phy:/dev/guestsVG/xpVol,hda,w','/home/skippy/myXpImage/xpImage.iso,hdc:cdrom,r' > ] > vnc = 1 > boot = "d" > > The qemu-dm-testXpOn15g.hvm.log: > domid: 22 > -videoram option does not work with cirrus vga device model. Videoram set to 4M. > Using file /dev/guestsVG/xpVol in read-write mode > Strip off blktap sub-type prefix to (drv 'aio') > Watching /local/domain/0/device-model/22/logdirty/cmd > Watching /local/domain/0/device-model/22/command > Watching /local/domain/22/cpu > qemu_map_cache_init nr_buckets = 10000 size 4194304 > shared page at pfn feffd > buffered io page at pfn feffb > Guest uuid = 1ce296c3-b4ba-4f01-a181-734fe2df26da > populating video RAM at ff000000 > mapping video RAM from ff000000 > Register xen platform. > Done register platform. > platform_fixed_ioport: changed ro/rw state of ROM memory area. now is rw state. > xs_read(/local/domain/0/device-model/22/xen_extended_power_mgmt): read error > xs_read(): vncpasswd get error. > /vm/1ce296c3-b4ba-4f01-a181-734fe2df26da/vncpasswd. > medium change watch on `hdc' (index: 1): aio: > I/O request not ready: 0, ptr: 0, port: 0, data: 0, count: 0, size: 0 > Log-dirty: no command yet. > vcpu-set: watch node error. > xs_read(/local/domain/22/log-throttling): read error > qemu: ignoring not-understood drive `/local/domain/22/log-throttling' > medium change watch on `/local/domain/22/log-throttling' - unknown > device, ignored > cirrus vga map change while on lfb mode > mapping vram to f0000000 - f0400000 > platform_fixed_ioport: changed ro/rw state of ROM memory area. now is rw state. > platform_fixed_ioport: changed ro/rw state of ROM memory area. now is ro state. > > The xl-testXpOn15g.hvm.log: > Waiting for domain testXpOn15g.hvm (domid 22) to die [pid 11237] > Domain 22 is dead > Action for shutdown reason code 0 is destroy > Domain 22 needs to be cleaned up: destroying the domain > libxl: debug: libxl_dm.c:761:libxl__destroy_device_model Device Model signaled > Done. Exiting now > > Suggestions? I've used this XP install cd several times and know > it's good. > > _______________________________________________ > Xen-users mailing list > Xen-users@lists.xen.org > http://lists.xen.org/xen-users _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Tue Sep 25 21:42:45 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Tue, 25 Sep 2012 21:42:45 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TGcsz-0001Yv-3C; Tue, 25 Sep 2012 21:41:45 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TGcsx-0001Yf-La for xen-users@lists.xen.org; Tue, 25 Sep 2012 21:41:44 +0000 Received: from [85.158.137.99:22384] by server-15.bemta-3.messagelabs.com id BA/0C-09665-61522605; Tue, 25 Sep 2012 21:41:42 +0000 X-Env-Sender: jh@excello.cz X-Msg-Ref: server-8.tower-217.messagelabs.com!1348609301!13749742!1 X-Originating-IP: [91.121.238.116] X-SpamReason: No, hits=0.0 required=7.0 tests=UNPARSEABLE_RELAY X-StarScan-Received: X-StarScan-Version: 6.6.1.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 9507 invoked from network); 25 Sep 2012 21:41:42 -0000 Received: from out1.virusfree.cz (HELO out1.virusfree.cz) (91.121.238.116) by server-8.tower-217.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 25 Sep 2012 21:41:42 -0000 Received: (qmail 20863 invoked by uid 210); 25 Sep 2012 23:41:39 +0200 Received: from smtp.excello.cz by out1 (envelope-from , uid 201) with VF-scanner-2.08VF (www.virusfree.cz : out1.virusfree.cz Clear:RC:1(91.121.238.113):SA:0(-9.4/5.0):. Processed in 2.300937 secs); 25 Sep 2012 21:41:39 -0000 X-Spam-Status: No, hits=-9.4 required=5.0 X-Spam-Report: SA TESTS 0.1 MAILBODYHTTPLINK RAW: http:// v body 0.5 MAILBOX_SIZE RAW: Describing mailbox size -4.9 BAYES_00 BODY: Bayes spam probability is 0 to 1% [score: 0.0005] -4.0 INREPLYTOCOM INREPLYTOCOM -1.5 INREPLYTO0 INREPLYTO0 -0.0 SPF_PASS SPF: sender matches SPF record -0.6 RP_MATCHES_RCVD Envelope sender domain matches handover relay domain 1.0 SPF_HELO_FAIL SPF: HELO does not match SPF record (fail) [SPF failed: Please see http://www.openspf.net/Why?s=helo; id=smtp.excello.cz; ip=91.121.238.113; r=bq.virusfree.cz] -0.1 DKIM_VALID_AU Message has a valid DKIM or DK signature from author's domain -0.1 DKIM_VALID Message has at least one valid DKIM or DK signature 0.1 DKIM_SIGNED Message has a DKIM or DK signature, not necessarily valid DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=excello.cz; h= date:message-id:from:to:subject:reply-to; q=dns/txt; s=default; t=1348609297; n=Test; bh=sz2r8x0WXPN9OvaegFbQvOiCIHORNlHsHUWQNC LFEAM=; b=qiRmkHNKdr2n9UKD5iybTLgl+Avt2kJHV43FqbB+hY52ixCTVCS56j OvhoMM50+YuD1L3rVOZUifWUqWrrBK8CMf0yBv+sqML88vYDj3XYs1hYz+6ma7fP O2adj/dJEh DomainKey-Signature: a=rsa-sha1; c=nofws; d=excello.cz; h=message-id :date:from:mime-version:to:subject:references:in-reply-to :content-type:content-transfer-encoding; q=dns; s=default; b=a9f 0N2EchgLD+1J839IM+xBLouRYfNmnR8l3ycpx8GBcCpy6Co2NMNg8qFlPHOcnMuo 47NBnxc09wGfs/aEwSB0zVmFtj4myZYWqkUglYHb20xUFwalujqEvs8/1690i Received: from smtp.excello.cz (91.121.238.113) by out1.virusfree.cz with SMTP; 25 Sep 2012 23:41:36 +0200 Received: from [192.168.1.167] (unknown [37.77.238.87]) by smtp.excello.cz (Postfix) with ESMTPA id DAF8481C5254 for ; Tue, 25 Sep 2012 23:41:34 +0200 (CEST) Message-ID: <5062250F.9010006@excello.cz> Date: Tue, 25 Sep 2012 23:41:35 +0200 From: Jan Hejl User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:13.0) Gecko/20120615 Thunderbird/13.0.1 MIME-Version: 1.0 To: xen-users@lists.xen.org References: In-Reply-To: Subject: Re: [Xen-users] Cannot boot to cdrom (or file) using xl create for XP hvm X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset="us-ascii"; Format="flowed" Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org Changing this line: '/home/skippy/myXpImage/xpImage.iso,hdc:cdrom,r' to this: 'file:/home/skippy/myXpImage/xpImage.iso,hdc:cdrom,r' (added file: directive) did the magic. Jan On 25.9.2012 22:35, Skippy VonDrake wrote: > Trying to build an XP hvm using a compiled "xenified" kernel > (3.5.4) but having no success reading the cdrom or an image > made from the install disk. > > Error in vnc display: > Booting from Cd-Rom... > CDROM boot failure code : 0003 > Boot from CD-Rom failed: could not read the boot disk > No bootable device. Powering off in 30 seconds. > > xl -vvv create testXpOn15g.cfg > Parsing config file configXL.cfg > xc: info: VIRTUAL MEMORY ARRANGEMENT: > Loader: 0000000000100000->0000000000172b10 > TOTAL: 0000000000000000->000000003f800000 > ENTRY ADDRESS: 00000000001015a0 > xc: info: PHYSICAL MEMORY ALLOCATION: > 4KB PAGES: 0x0000000000000200 > 2MB PAGES: 0x00000000000001fb > 1GB PAGES: 0x0000000000000000 > Daemon running with PID 11236 > xc: debug: hypercall buffer: total allocations:585 total releases:585 > xc: debug: hypercall buffer: current allocations:0 maximum allocations:2 > xc: debug: hypercall buffer: cache current size:2 > xc: debug: hypercall buffer: cache hits:582 misses:2 toobig:1 > > testXpOn15g.cfg contents: > builder = "hvm" > name = "testXpOn15g.hvm" > viridian = 1 > memory = 1024 > vcpus = 1 > vif = [ '' ] > # Disk Devices > #disk = [ 'phy:/dev/guestsVG/xpVol,hda,w','phy:/dev/sr0,hdc:cdrom,r' ] > #disk = [ 'phy:/dev/guestsVG/xpVol,hda,w','phy:/dev/sr0,ioemu:hdc:cdrom,r' ] > #disk = [ 'phy:/dev/guestsVG/xpVol,hda,w','phy:/dev/sr0,sda:cdrom,r' ] > disk = [ 'phy:/dev/guestsVG/xpVol,hda,w','/home/skippy/myXpImage/xpImage.iso,hdc:cdrom,r' > ] > vnc = 1 > boot = "d" > > The qemu-dm-testXpOn15g.hvm.log: > domid: 22 > -videoram option does not work with cirrus vga device model. Videoram set to 4M. > Using file /dev/guestsVG/xpVol in read-write mode > Strip off blktap sub-type prefix to (drv 'aio') > Watching /local/domain/0/device-model/22/logdirty/cmd > Watching /local/domain/0/device-model/22/command > Watching /local/domain/22/cpu > qemu_map_cache_init nr_buckets = 10000 size 4194304 > shared page at pfn feffd > buffered io page at pfn feffb > Guest uuid = 1ce296c3-b4ba-4f01-a181-734fe2df26da > populating video RAM at ff000000 > mapping video RAM from ff000000 > Register xen platform. > Done register platform. > platform_fixed_ioport: changed ro/rw state of ROM memory area. now is rw state. > xs_read(/local/domain/0/device-model/22/xen_extended_power_mgmt): read error > xs_read(): vncpasswd get error. > /vm/1ce296c3-b4ba-4f01-a181-734fe2df26da/vncpasswd. > medium change watch on `hdc' (index: 1): aio: > I/O request not ready: 0, ptr: 0, port: 0, data: 0, count: 0, size: 0 > Log-dirty: no command yet. > vcpu-set: watch node error. > xs_read(/local/domain/22/log-throttling): read error > qemu: ignoring not-understood drive `/local/domain/22/log-throttling' > medium change watch on `/local/domain/22/log-throttling' - unknown > device, ignored > cirrus vga map change while on lfb mode > mapping vram to f0000000 - f0400000 > platform_fixed_ioport: changed ro/rw state of ROM memory area. now is rw state. > platform_fixed_ioport: changed ro/rw state of ROM memory area. now is ro state. > > The xl-testXpOn15g.hvm.log: > Waiting for domain testXpOn15g.hvm (domid 22) to die [pid 11237] > Domain 22 is dead > Action for shutdown reason code 0 is destroy > Domain 22 needs to be cleaned up: destroying the domain > libxl: debug: libxl_dm.c:761:libxl__destroy_device_model Device Model signaled > Done. Exiting now > > Suggestions? I've used this XP install cd several times and know > it's good. > > _______________________________________________ > Xen-users mailing list > Xen-users@lists.xen.org > http://lists.xen.org/xen-users _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Tue Sep 25 21:52:02 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Tue, 25 Sep 2012 21:52:02 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TGd1z-000275-Qt; Tue, 25 Sep 2012 21:51:03 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TGd1x-00026p-BO for xen-users@lists.xen.org; Tue, 25 Sep 2012 21:51:01 +0000 Received: from [85.158.138.51:34061] by server-2.bemta-3.messagelabs.com id 33/34-04862-44722605; Tue, 25 Sep 2012 21:51:00 +0000 X-Env-Sender: cdelorme@gmail.com X-Msg-Ref: server-9.tower-174.messagelabs.com!1348609857!30269002!1 X-Originating-IP: [209.85.223.173] X-SpamReason: No, hits=0.4 required=7.0 tests=HTML_30_40,HTML_MESSAGE, ML_RADAR_SPEW_LINKS_14,RCVD_BY_IP,spamassassin: X-StarScan-Received: X-StarScan-Version: 6.6.1.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 31883 invoked from network); 25 Sep 2012 21:50:58 -0000 Received: from mail-ie0-f173.google.com (HELO mail-ie0-f173.google.com) (209.85.223.173) by server-9.tower-174.messagelabs.com with RC4-SHA encrypted SMTP; 25 Sep 2012 21:50:58 -0000 Received: by iea17 with SMTP id 17so13158137iea.32 for ; Tue, 25 Sep 2012 14:50:57 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=Fp+bVo9TM0NanTkjI8yLPI0ULwANlqkVRG4kupNpbMc=; b=tqQhvjulLmTo7rrkdsjMD0i38akpNcrMCNLC+670kzl+o1zS72oJndox1fZnISbiXE Q8b/CWvU/d6Rl9IG/jQ7Mkul9bqgckq9OaPUejEmT8Lrm3hpRtzvq8savHDX1hrNOQ/m fubRKZmQQWQ9iNxFsIiyAOS7ygDVquqsVkvmX/NHK8aQxXMLSt3HLR/y9LKaANzYjnYL ZxW6Kc72FMA+oyU2pFXW3y1SuEyRBKMEBIQTn/YAfnH+MP9Gj3lzM3x4lcvfYksmCm6q +/kd29LVdHHbYWAXjl7lUGsgNPFD4Vq2+cLCKhkF6OjsLCHQflHXVC358+kDc6kkw9Ym BG1A== MIME-Version: 1.0 Received: by 10.50.157.234 with SMTP id wp10mr9555228igb.5.1348609857106; Tue, 25 Sep 2012 14:50:57 -0700 (PDT) Received: by 10.64.102.167 with HTTP; Tue, 25 Sep 2012 14:50:57 -0700 (PDT) In-Reply-To: References: Date: Tue, 25 Sep 2012 17:50:57 -0400 Message-ID: From: Casey DeLorme To: Skippy VonDrake Cc: "xen-users@lists.xen.org" Subject: Re: [Xen-users] Cannot boot to cdrom (or file) using xl create for XP hvm X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============6510576881647627121==" Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org --===============6510576881647627121== Content-Type: multipart/alternative; boundary=e89a8f3ba6f579330804ca8db30f --e89a8f3ba6f579330804ca8db30f Content-Type: text/plain; charset=ISO-8859-1 On Tue, Sep 25, 2012 at 4:35 PM, Skippy VonDrake wrote: > Trying to build an XP hvm using a compiled "xenified" kernel > (3.5.4) but having no success reading the cdrom or an image > made from the install disk. > > Assuming Xen 4.2 given that you are using the latest kernel. First read these: [Xen Man Pages](http://wiki.xen.org/wiki/Xen_Man_Pages) [xl.cfg doc](http://xenbits.xen.org/docs/unstable/man/xl.cfg.5.html) Relative to your previous question: [xl Disk Configuration]( http://xenbits.xen.org/docs/unstable/misc/xl-disk-configuration.txt) > Error in vnc display: > Booting from Cd-Rom... > CDROM boot failure code : 0003 > Boot from CD-Rom failed: could not read the boot disk > No bootable device. Powering off in 30 seconds. > > xl -vvv create testXpOn15g.cfg > Parsing config file configXL.cfg > xc: info: VIRTUAL MEMORY ARRANGEMENT: > Loader: 0000000000100000->0000000000172b10 > TOTAL: 0000000000000000->000000003f800000 > ENTRY ADDRESS: 00000000001015a0 > xc: info: PHYSICAL MEMORY ALLOCATION: > 4KB PAGES: 0x0000000000000200 > 2MB PAGES: 0x00000000000001fb > 1GB PAGES: 0x0000000000000000 > Daemon running with PID 11236 > xc: debug: hypercall buffer: total allocations:585 total releases:585 > xc: debug: hypercall buffer: current allocations:0 maximum allocations:2 > xc: debug: hypercall buffer: cache current size:2 > xc: debug: hypercall buffer: cache hits:582 misses:2 toobig:1 > > Your able to start the HVM and connect via VNC but it cannot boot to the iso? > testXpOn15g.cfg contents: > builder = "hvm" > name = "testXpOn15g.hvm" > viridian = 1 > memory = 1024 > vcpus = 1 > vif = [ '' ] > # Disk Devices > #disk = [ 'phy:/dev/guestsVG/xpVol,hda,w','phy:/dev/sr0,hdc:cdrom,r' ] > #disk = [ 'phy:/dev/guestsVG/xpVol,hda,w','phy:/dev/sr0,ioemu:hdc:cdrom,r' > ] > #disk = [ 'phy:/dev/guestsVG/xpVol,hda,w','phy:/dev/sr0,sda:cdrom,r' ] > disk = [ > 'phy:/dev/guestsVG/xpVol,hda,w','/home/skippy/myXpImage/xpImage.iso,hdc:cdrom,r' > ] > vnc = 1 > boot = "d" > > Based on the provided configuration, I would suggest trying this revised copy: name="testXpOn15g.hvm" builder="hvm" vcpus=1 memory=1024 disk=[ '/dev/guestsVG/xpVol,,hda,w', '/dev/sr0,,hdc,r,devtype=cdrom' ] vif=[ '' ] boot='dc' videoram=8 stdvga=1 viridian = 1 vnc=1 usb=1 usbdevice="tablet" localtime=1 > The qemu-dm-testXpOn15g.hvm.log: > domid: 22 > -videoram option does not work with cirrus vga device model. Videoram set > to 4M. > Using file /dev/guestsVG/xpVol in read-write mode > Strip off blktap sub-type prefix to (drv 'aio') > Watching /local/domain/0/device-model/22/logdirty/cmd > Watching /local/domain/0/device-model/22/command > Watching /local/domain/22/cpu > qemu_map_cache_init nr_buckets = 10000 size 4194304 > shared page at pfn feffd > buffered io page at pfn feffb > Guest uuid = 1ce296c3-b4ba-4f01-a181-734fe2df26da > populating video RAM at ff000000 > mapping video RAM from ff000000 > Register xen platform. > Done register platform. > platform_fixed_ioport: changed ro/rw state of ROM memory area. now is rw > state. > xs_read(/local/domain/0/device-model/22/xen_extended_power_mgmt): read > error > xs_read(): vncpasswd get error. > /vm/1ce296c3-b4ba-4f01-a181-734fe2df26da/vncpasswd. > medium change watch on `hdc' (index: 1): aio: > I/O request not ready: 0, ptr: 0, port: 0, data: 0, count: 0, size: 0 > Log-dirty: no command yet. > vcpu-set: watch node error. > xs_read(/local/domain/22/log-throttling): read error > qemu: ignoring not-understood drive `/local/domain/22/log-throttling' > medium change watch on `/local/domain/22/log-throttling' - unknown > device, ignored > cirrus vga map change while on lfb mode > mapping vram to f0000000 - f0400000 > platform_fixed_ioport: changed ro/rw state of ROM memory area. now is rw > state. > platform_fixed_ioport: changed ro/rw state of ROM memory area. now is ro > state. > > The xl-testXpOn15g.hvm.log: > Waiting for domain testXpOn15g.hvm (domid 22) to die [pid 11237] > Domain 22 is dead > Action for shutdown reason code 0 is destroy > Domain 22 needs to be cleaned up: destroying the domain > libxl: debug: libxl_dm.c:761:libxl__destroy_device_model Device Model > signaled > Done. Exiting now > > Suggestions? I've used this XP install cd several times and know > it's good. > > Another suggestion is to try creating a disk image to work off of using: sudo dd if=/dev/sr0 of=/path/to/disk.iso Then change the line for your cdrom to read: '/path/to/disk.iso,,hdc,r,devtype=cdrom' I know you said you've used the CD before, but the only times I have specifically encountered that error message with proper configuration was when the image file I was using had been corrupted. Just to be sure, try cleaning the disk, or making an image copy using dd or another utility of your choice. > _______________________________________________ > Xen-users mailing list > Xen-users@lists.xen.org > http://lists.xen.org/xen-users > Here is my Windows 7 HVM Configuration File as an example: name='windows' builder='hvm' vcpus=4 memory=8192 disk=[ '/dev/mapper/xen-windows,,hda,w' ] vif=[ 'bridge=xenbr1,model=e1000,mac=00:16:3e:14:b1:1c' ] pci = [ '00:1d.0', '01:00.0', '01:00.1', '0b:00.0', '0c:00.0' ] boot='c' pae=1 nx=1 videoram=16 stdvga=1 #sdl=1 vnc=1 vnclisten="0.0.0.0:10" vncpasswd='' usb=1 usbdevice="tablet" localtime=1 xen_platform_pci=1 _The "xen_platform_pci" flag is for PV on HVM, it should not have anything to do with your configuration until after you install Windows and then the GPLPV drivers._ --e89a8f3ba6f579330804ca8db30f Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable
On Tue, Sep 25, 2012 at 4:35 PM, Skippy VonDrake <= ;skippyvondra= ke@gmail.com> wrote:
Trying to build an XP hvm using a compiled "xenified" kernel
(3.5.4) but having no success reading the cdrom or an image
made from the install disk.


Assuming Xen 4.2 given that you a= re using the latest kernel.

First read these:

=

Relative to your previous question:

=A0
Error in vnc display:
=A0 Booting from Cd-Rom...
=A0 CDROM boot failure code : 0003
=A0 Boot from CD-Rom failed: could not read the boot disk
=A0 No bootable device. Powering off in 30 seconds.

xl -vvv create testXpOn15g.cfg
=A0 Parsing config file configXL.cfg
=A0 xc: info: VIRTUAL MEMORY ARRANGEMENT:
=A0 =A0 Loader: =A0 =A0 =A0 =A00000000000100000->0000000000172b10
=A0 =A0 TOTAL: =A0 =A0 =A0 =A0 0000000000000000->000000003f800000
=A0 =A0 ENTRY ADDRESS: 00000000001015a0
=A0 xc: info: PHYSICAL MEMORY ALLOCATION:
=A0 =A0 4KB PAGES: 0x0000000000000200
=A0 =A0 2MB PAGES: 0x00000000000001fb
=A0 =A0 1GB PAGES: 0x0000000000000000
=A0 Daemon running with PID 11236
=A0 xc: debug: hypercall buffer: total allocations:585 total releases:585 =A0 xc: debug: hypercall buffer: current allocations:0 maximum allocations:= 2
=A0 xc: debug: hypercall buffer: cache current size:2
=A0 xc: debug: hypercall buffer: cache hits:582 misses:2 toobig:1


Your able to start the HVM and co= nnect via VNC but it cannot boot to the iso?
=A0
testXpOn15g.cfg contents:
builder =3D "hvm"
name =3D "testXpOn15g.hvm"
viridian =3D 1
memory =3D 1024
vcpus =3D 1
vif =3D [ '' ]
# Disk Devices
#disk =3D [ 'phy:/dev/guestsVG/xpVol,hda,w','phy:/dev/sr0,hdc:c= drom,r' ]
#disk =3D [ 'phy:/dev/guestsVG/xpVol,hda,w','phy:/dev/sr0,ioemu= :hdc:cdrom,r' ]
#disk =3D [ 'phy:/dev/guestsVG/xpVol,hda,w','phy:/dev/sr0,sda:c= drom,r' ]
disk =3D [ 'phy:/dev/guestsVG/xpVol,hda,w','/home/skippy/myXpIm= age/xpImage.iso,hdc:cdrom,r'
]
vnc =3D 1
boot =3D "d"



Based on the provi= ded configuration, I would suggest trying this revised copy:

=
name=3D"testXpOn15g.hvm"
builder=3D"hvm= "
vcpus=3D1
memory=3D1024

disk=3D[
=A0 =A0 =A0 =A0 '/dev/guestsVG/xpVol,,hda,w',
=A0= =A0 =A0 =A0 '/dev/sr0,,hdc,r,devtype=3Dcdrom'
]
vif=3D[
=A0 =A0 =A0 =A0 ''
]
boot=3D'dc'
videoram=3D8
stdvg= a=3D1
viridian =3D 1

vnc=3D1
<= br>
usb=3D1
usbdevice=3D"tablet"
lo= caltime=3D1
=A0
The qemu-dm-testXpOn15g.hvm.log:
domid: 22
-videoram option does not work with cirrus vga device model. Videoram set t= o 4M.
Using file /dev/guestsVG/xpVol in read-write mode
Strip off blktap sub-type prefix to =A0(drv 'aio')
Watching /local/domain/0/device-model/22/logdirty/cmd
Watching /local/domain/0/device-model/22/command
Watching /local/domain/22/cpu
qemu_map_cache_init nr_buckets =3D 10000 size 4194304
shared page at pfn feffd
buffered io page at pfn feffb
Guest uuid =3D 1ce296c3-b4ba-4f01-a181-734fe2df26da
populating video RAM at ff000000
mapping video RAM from ff000000
Register xen platform.
Done register platform.
platform_fixed_ioport: changed ro/rw state of ROM memory area. now is rw st= ate.
xs_read(/local/domain/0/device-model/22/xen_extended_power_mgmt): read erro= r
xs_read(): vncpasswd get error.
/vm/1ce296c3-b4ba-4f01-a181-734fe2df26da/vncpasswd.
medium change watch on `hdc' (index: 1): aio:
I/O request not ready: 0, ptr: 0, port: 0, data: 0, count: 0, size: 0
Log-dirty: no command yet.
vcpu-set: watch node error.
xs_read(/local/domain/22/log-throttling): read error
qemu: ignoring not-understood drive `/local/domain/22/log-throttling' medium change watch on `/local/domain/22/log-throttling' - unknown
device, ignored
cirrus vga map change while on lfb mode
mapping vram to f0000000 - f0400000
platform_fixed_ioport: changed ro/rw state of ROM memory area. now is rw st= ate.
platform_fixed_ioport: changed ro/rw state of ROM memory area. now is ro st= ate.

The xl-testXpOn15g.hvm.log:
Waiting for domain testXpOn15g.hvm (domid 22) to die [pid 11237]
Domain 22 is dead
Action for shutdown reason code 0 is destroy
Domain 22 needs to be cleaned up: destroying the domain
libxl: debug: libxl_dm.c:761:libxl__destroy_device_model Device Model signa= led
Done. Exiting now

Suggestions? I've used this XP install cd several times and know
it's good.


Another suggestion is to try crea= ting a disk image to work off of using:
=A0 sudo dd if=3D/dev/sr0= of=3D/path/to/disk.iso

Then change the line for y= our cdrom to read:
=A0 '/path/to/disk.iso,,hdc,r,devtype=3Dcdrom'

I know you said you've used the CD before, but the= only times I have specifically encountered that error message with proper = configuration was when the image file I was using had been corrupted. =A0Ju= st to be sure, try cleaning the disk, or making an image copy using dd or a= nother utility of your choice.
=A0
_______________________________________________
Xen-users mailing list
Xen-users@lists.xen.org
http://lists.x= en.org/xen-users


Here is my Windows 7 HVM Co= nfiguration File as an example:

name=3D'window= s'
builder=3D'hvm'
vcpus=3D4
memo= ry=3D8192
disk=3D[
=A0 =A0 =A0 =A0 '/dev/mapper/xen-windows,,hda,w= '
]
vif=3D[
=A0 =A0 =A0 =A0 'bridge= =3Dxenbr1,model=3De1000,mac=3D00:16:3e:14:b1:1c'
]
= pci =3D [
=A0 =A0 =A0 =A0 '00:1d.0',
=A0 =A0 =A0 =A0 '01:00.0',
=A0 =A0 =A0 =A0 '01:0= 0.1',
=A0 =A0 =A0 =A0 '0b:00.0',
=A0 =A0 = =A0 =A0 '0c:00.0'
]
boot=3D'c'
pae=3D1
nx=3D1
videoram=3D16
stdvga=3D1
#sdl=3D1
vnc=3D1
vnclisten=3D"0.0.0.0:10"=
vncpasswd=3D''
usb=3D1
usbdevice=3D&= quot;tablet"
localtime=3D1
xen_platform_pci=3D1

= _The "xen_platform_pci" flag is for PV on HVM, it should not have= anything to do with your configuration until after you install Windows and= then the GPLPV drivers._

--e89a8f3ba6f579330804ca8db30f-- --===============6510576881647627121== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users --===============6510576881647627121==-- From xen-users-bounces@lists.xen.org Tue Sep 25 21:52:02 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Tue, 25 Sep 2012 21:52:02 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TGd1z-000275-Qt; Tue, 25 Sep 2012 21:51:03 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TGd1x-00026p-BO for xen-users@lists.xen.org; Tue, 25 Sep 2012 21:51:01 +0000 Received: from [85.158.138.51:34061] by server-2.bemta-3.messagelabs.com id 33/34-04862-44722605; Tue, 25 Sep 2012 21:51:00 +0000 X-Env-Sender: cdelorme@gmail.com X-Msg-Ref: server-9.tower-174.messagelabs.com!1348609857!30269002!1 X-Originating-IP: [209.85.223.173] X-SpamReason: No, hits=0.4 required=7.0 tests=HTML_30_40,HTML_MESSAGE, ML_RADAR_SPEW_LINKS_14,RCVD_BY_IP,spamassassin: X-StarScan-Received: X-StarScan-Version: 6.6.1.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 31883 invoked from network); 25 Sep 2012 21:50:58 -0000 Received: from mail-ie0-f173.google.com (HELO mail-ie0-f173.google.com) (209.85.223.173) by server-9.tower-174.messagelabs.com with RC4-SHA encrypted SMTP; 25 Sep 2012 21:50:58 -0000 Received: by iea17 with SMTP id 17so13158137iea.32 for ; Tue, 25 Sep 2012 14:50:57 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=Fp+bVo9TM0NanTkjI8yLPI0ULwANlqkVRG4kupNpbMc=; b=tqQhvjulLmTo7rrkdsjMD0i38akpNcrMCNLC+670kzl+o1zS72oJndox1fZnISbiXE Q8b/CWvU/d6Rl9IG/jQ7Mkul9bqgckq9OaPUejEmT8Lrm3hpRtzvq8savHDX1hrNOQ/m fubRKZmQQWQ9iNxFsIiyAOS7ygDVquqsVkvmX/NHK8aQxXMLSt3HLR/y9LKaANzYjnYL ZxW6Kc72FMA+oyU2pFXW3y1SuEyRBKMEBIQTn/YAfnH+MP9Gj3lzM3x4lcvfYksmCm6q +/kd29LVdHHbYWAXjl7lUGsgNPFD4Vq2+cLCKhkF6OjsLCHQflHXVC358+kDc6kkw9Ym BG1A== MIME-Version: 1.0 Received: by 10.50.157.234 with SMTP id wp10mr9555228igb.5.1348609857106; Tue, 25 Sep 2012 14:50:57 -0700 (PDT) Received: by 10.64.102.167 with HTTP; Tue, 25 Sep 2012 14:50:57 -0700 (PDT) In-Reply-To: References: Date: Tue, 25 Sep 2012 17:50:57 -0400 Message-ID: From: Casey DeLorme To: Skippy VonDrake Cc: "xen-users@lists.xen.org" Subject: Re: [Xen-users] Cannot boot to cdrom (or file) using xl create for XP hvm X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============6510576881647627121==" Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org --===============6510576881647627121== Content-Type: multipart/alternative; boundary=e89a8f3ba6f579330804ca8db30f --e89a8f3ba6f579330804ca8db30f Content-Type: text/plain; charset=ISO-8859-1 On Tue, Sep 25, 2012 at 4:35 PM, Skippy VonDrake wrote: > Trying to build an XP hvm using a compiled "xenified" kernel > (3.5.4) but having no success reading the cdrom or an image > made from the install disk. > > Assuming Xen 4.2 given that you are using the latest kernel. First read these: [Xen Man Pages](http://wiki.xen.org/wiki/Xen_Man_Pages) [xl.cfg doc](http://xenbits.xen.org/docs/unstable/man/xl.cfg.5.html) Relative to your previous question: [xl Disk Configuration]( http://xenbits.xen.org/docs/unstable/misc/xl-disk-configuration.txt) > Error in vnc display: > Booting from Cd-Rom... > CDROM boot failure code : 0003 > Boot from CD-Rom failed: could not read the boot disk > No bootable device. Powering off in 30 seconds. > > xl -vvv create testXpOn15g.cfg > Parsing config file configXL.cfg > xc: info: VIRTUAL MEMORY ARRANGEMENT: > Loader: 0000000000100000->0000000000172b10 > TOTAL: 0000000000000000->000000003f800000 > ENTRY ADDRESS: 00000000001015a0 > xc: info: PHYSICAL MEMORY ALLOCATION: > 4KB PAGES: 0x0000000000000200 > 2MB PAGES: 0x00000000000001fb > 1GB PAGES: 0x0000000000000000 > Daemon running with PID 11236 > xc: debug: hypercall buffer: total allocations:585 total releases:585 > xc: debug: hypercall buffer: current allocations:0 maximum allocations:2 > xc: debug: hypercall buffer: cache current size:2 > xc: debug: hypercall buffer: cache hits:582 misses:2 toobig:1 > > Your able to start the HVM and connect via VNC but it cannot boot to the iso? > testXpOn15g.cfg contents: > builder = "hvm" > name = "testXpOn15g.hvm" > viridian = 1 > memory = 1024 > vcpus = 1 > vif = [ '' ] > # Disk Devices > #disk = [ 'phy:/dev/guestsVG/xpVol,hda,w','phy:/dev/sr0,hdc:cdrom,r' ] > #disk = [ 'phy:/dev/guestsVG/xpVol,hda,w','phy:/dev/sr0,ioemu:hdc:cdrom,r' > ] > #disk = [ 'phy:/dev/guestsVG/xpVol,hda,w','phy:/dev/sr0,sda:cdrom,r' ] > disk = [ > 'phy:/dev/guestsVG/xpVol,hda,w','/home/skippy/myXpImage/xpImage.iso,hdc:cdrom,r' > ] > vnc = 1 > boot = "d" > > Based on the provided configuration, I would suggest trying this revised copy: name="testXpOn15g.hvm" builder="hvm" vcpus=1 memory=1024 disk=[ '/dev/guestsVG/xpVol,,hda,w', '/dev/sr0,,hdc,r,devtype=cdrom' ] vif=[ '' ] boot='dc' videoram=8 stdvga=1 viridian = 1 vnc=1 usb=1 usbdevice="tablet" localtime=1 > The qemu-dm-testXpOn15g.hvm.log: > domid: 22 > -videoram option does not work with cirrus vga device model. Videoram set > to 4M. > Using file /dev/guestsVG/xpVol in read-write mode > Strip off blktap sub-type prefix to (drv 'aio') > Watching /local/domain/0/device-model/22/logdirty/cmd > Watching /local/domain/0/device-model/22/command > Watching /local/domain/22/cpu > qemu_map_cache_init nr_buckets = 10000 size 4194304 > shared page at pfn feffd > buffered io page at pfn feffb > Guest uuid = 1ce296c3-b4ba-4f01-a181-734fe2df26da > populating video RAM at ff000000 > mapping video RAM from ff000000 > Register xen platform. > Done register platform. > platform_fixed_ioport: changed ro/rw state of ROM memory area. now is rw > state. > xs_read(/local/domain/0/device-model/22/xen_extended_power_mgmt): read > error > xs_read(): vncpasswd get error. > /vm/1ce296c3-b4ba-4f01-a181-734fe2df26da/vncpasswd. > medium change watch on `hdc' (index: 1): aio: > I/O request not ready: 0, ptr: 0, port: 0, data: 0, count: 0, size: 0 > Log-dirty: no command yet. > vcpu-set: watch node error. > xs_read(/local/domain/22/log-throttling): read error > qemu: ignoring not-understood drive `/local/domain/22/log-throttling' > medium change watch on `/local/domain/22/log-throttling' - unknown > device, ignored > cirrus vga map change while on lfb mode > mapping vram to f0000000 - f0400000 > platform_fixed_ioport: changed ro/rw state of ROM memory area. now is rw > state. > platform_fixed_ioport: changed ro/rw state of ROM memory area. now is ro > state. > > The xl-testXpOn15g.hvm.log: > Waiting for domain testXpOn15g.hvm (domid 22) to die [pid 11237] > Domain 22 is dead > Action for shutdown reason code 0 is destroy > Domain 22 needs to be cleaned up: destroying the domain > libxl: debug: libxl_dm.c:761:libxl__destroy_device_model Device Model > signaled > Done. Exiting now > > Suggestions? I've used this XP install cd several times and know > it's good. > > Another suggestion is to try creating a disk image to work off of using: sudo dd if=/dev/sr0 of=/path/to/disk.iso Then change the line for your cdrom to read: '/path/to/disk.iso,,hdc,r,devtype=cdrom' I know you said you've used the CD before, but the only times I have specifically encountered that error message with proper configuration was when the image file I was using had been corrupted. Just to be sure, try cleaning the disk, or making an image copy using dd or another utility of your choice. > _______________________________________________ > Xen-users mailing list > Xen-users@lists.xen.org > http://lists.xen.org/xen-users > Here is my Windows 7 HVM Configuration File as an example: name='windows' builder='hvm' vcpus=4 memory=8192 disk=[ '/dev/mapper/xen-windows,,hda,w' ] vif=[ 'bridge=xenbr1,model=e1000,mac=00:16:3e:14:b1:1c' ] pci = [ '00:1d.0', '01:00.0', '01:00.1', '0b:00.0', '0c:00.0' ] boot='c' pae=1 nx=1 videoram=16 stdvga=1 #sdl=1 vnc=1 vnclisten="0.0.0.0:10" vncpasswd='' usb=1 usbdevice="tablet" localtime=1 xen_platform_pci=1 _The "xen_platform_pci" flag is for PV on HVM, it should not have anything to do with your configuration until after you install Windows and then the GPLPV drivers._ --e89a8f3ba6f579330804ca8db30f Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable
On Tue, Sep 25, 2012 at 4:35 PM, Skippy VonDrake <= ;skippyvondra= ke@gmail.com> wrote:
Trying to build an XP hvm using a compiled "xenified" kernel
(3.5.4) but having no success reading the cdrom or an image
made from the install disk.


Assuming Xen 4.2 given that you a= re using the latest kernel.

First read these:

=

Relative to your previous question:

=A0
Error in vnc display:
=A0 Booting from Cd-Rom...
=A0 CDROM boot failure code : 0003
=A0 Boot from CD-Rom failed: could not read the boot disk
=A0 No bootable device. Powering off in 30 seconds.

xl -vvv create testXpOn15g.cfg
=A0 Parsing config file configXL.cfg
=A0 xc: info: VIRTUAL MEMORY ARRANGEMENT:
=A0 =A0 Loader: =A0 =A0 =A0 =A00000000000100000->0000000000172b10
=A0 =A0 TOTAL: =A0 =A0 =A0 =A0 0000000000000000->000000003f800000
=A0 =A0 ENTRY ADDRESS: 00000000001015a0
=A0 xc: info: PHYSICAL MEMORY ALLOCATION:
=A0 =A0 4KB PAGES: 0x0000000000000200
=A0 =A0 2MB PAGES: 0x00000000000001fb
=A0 =A0 1GB PAGES: 0x0000000000000000
=A0 Daemon running with PID 11236
=A0 xc: debug: hypercall buffer: total allocations:585 total releases:585 =A0 xc: debug: hypercall buffer: current allocations:0 maximum allocations:= 2
=A0 xc: debug: hypercall buffer: cache current size:2
=A0 xc: debug: hypercall buffer: cache hits:582 misses:2 toobig:1


Your able to start the HVM and co= nnect via VNC but it cannot boot to the iso?
=A0
testXpOn15g.cfg contents:
builder =3D "hvm"
name =3D "testXpOn15g.hvm"
viridian =3D 1
memory =3D 1024
vcpus =3D 1
vif =3D [ '' ]
# Disk Devices
#disk =3D [ 'phy:/dev/guestsVG/xpVol,hda,w','phy:/dev/sr0,hdc:c= drom,r' ]
#disk =3D [ 'phy:/dev/guestsVG/xpVol,hda,w','phy:/dev/sr0,ioemu= :hdc:cdrom,r' ]
#disk =3D [ 'phy:/dev/guestsVG/xpVol,hda,w','phy:/dev/sr0,sda:c= drom,r' ]
disk =3D [ 'phy:/dev/guestsVG/xpVol,hda,w','/home/skippy/myXpIm= age/xpImage.iso,hdc:cdrom,r'
]
vnc =3D 1
boot =3D "d"



Based on the provi= ded configuration, I would suggest trying this revised copy:

=
name=3D"testXpOn15g.hvm"
builder=3D"hvm= "
vcpus=3D1
memory=3D1024

disk=3D[
=A0 =A0 =A0 =A0 '/dev/guestsVG/xpVol,,hda,w',
=A0= =A0 =A0 =A0 '/dev/sr0,,hdc,r,devtype=3Dcdrom'
]
vif=3D[
=A0 =A0 =A0 =A0 ''
]
boot=3D'dc'
videoram=3D8
stdvg= a=3D1
viridian =3D 1

vnc=3D1
<= br>
usb=3D1
usbdevice=3D"tablet"
lo= caltime=3D1
=A0
The qemu-dm-testXpOn15g.hvm.log:
domid: 22
-videoram option does not work with cirrus vga device model. Videoram set t= o 4M.
Using file /dev/guestsVG/xpVol in read-write mode
Strip off blktap sub-type prefix to =A0(drv 'aio')
Watching /local/domain/0/device-model/22/logdirty/cmd
Watching /local/domain/0/device-model/22/command
Watching /local/domain/22/cpu
qemu_map_cache_init nr_buckets =3D 10000 size 4194304
shared page at pfn feffd
buffered io page at pfn feffb
Guest uuid =3D 1ce296c3-b4ba-4f01-a181-734fe2df26da
populating video RAM at ff000000
mapping video RAM from ff000000
Register xen platform.
Done register platform.
platform_fixed_ioport: changed ro/rw state of ROM memory area. now is rw st= ate.
xs_read(/local/domain/0/device-model/22/xen_extended_power_mgmt): read erro= r
xs_read(): vncpasswd get error.
/vm/1ce296c3-b4ba-4f01-a181-734fe2df26da/vncpasswd.
medium change watch on `hdc' (index: 1): aio:
I/O request not ready: 0, ptr: 0, port: 0, data: 0, count: 0, size: 0
Log-dirty: no command yet.
vcpu-set: watch node error.
xs_read(/local/domain/22/log-throttling): read error
qemu: ignoring not-understood drive `/local/domain/22/log-throttling' medium change watch on `/local/domain/22/log-throttling' - unknown
device, ignored
cirrus vga map change while on lfb mode
mapping vram to f0000000 - f0400000
platform_fixed_ioport: changed ro/rw state of ROM memory area. now is rw st= ate.
platform_fixed_ioport: changed ro/rw state of ROM memory area. now is ro st= ate.

The xl-testXpOn15g.hvm.log:
Waiting for domain testXpOn15g.hvm (domid 22) to die [pid 11237]
Domain 22 is dead
Action for shutdown reason code 0 is destroy
Domain 22 needs to be cleaned up: destroying the domain
libxl: debug: libxl_dm.c:761:libxl__destroy_device_model Device Model signa= led
Done. Exiting now

Suggestions? I've used this XP install cd several times and know
it's good.


Another suggestion is to try crea= ting a disk image to work off of using:
=A0 sudo dd if=3D/dev/sr0= of=3D/path/to/disk.iso

Then change the line for y= our cdrom to read:
=A0 '/path/to/disk.iso,,hdc,r,devtype=3Dcdrom'

I know you said you've used the CD before, but the= only times I have specifically encountered that error message with proper = configuration was when the image file I was using had been corrupted. =A0Ju= st to be sure, try cleaning the disk, or making an image copy using dd or a= nother utility of your choice.
=A0
_______________________________________________
Xen-users mailing list
Xen-users@lists.xen.org
http://lists.x= en.org/xen-users


Here is my Windows 7 HVM Co= nfiguration File as an example:

name=3D'window= s'
builder=3D'hvm'
vcpus=3D4
memo= ry=3D8192
disk=3D[
=A0 =A0 =A0 =A0 '/dev/mapper/xen-windows,,hda,w= '
]
vif=3D[
=A0 =A0 =A0 =A0 'bridge= =3Dxenbr1,model=3De1000,mac=3D00:16:3e:14:b1:1c'
]
= pci =3D [
=A0 =A0 =A0 =A0 '00:1d.0',
=A0 =A0 =A0 =A0 '01:00.0',
=A0 =A0 =A0 =A0 '01:0= 0.1',
=A0 =A0 =A0 =A0 '0b:00.0',
=A0 =A0 = =A0 =A0 '0c:00.0'
]
boot=3D'c'
pae=3D1
nx=3D1
videoram=3D16
stdvga=3D1
#sdl=3D1
vnc=3D1
vnclisten=3D"0.0.0.0:10"=
vncpasswd=3D''
usb=3D1
usbdevice=3D&= quot;tablet"
localtime=3D1
xen_platform_pci=3D1

= _The "xen_platform_pci" flag is for PV on HVM, it should not have= anything to do with your configuration until after you install Windows and= then the GPLPV drivers._

--e89a8f3ba6f579330804ca8db30f-- --===============6510576881647627121== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users --===============6510576881647627121==-- From xen-users-bounces@lists.xen.org Tue Sep 25 21:56:44 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Tue, 25 Sep 2012 21:56:44 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TGd6d-0002W7-7x; Tue, 25 Sep 2012 21:55:51 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TGd6b-0002Vs-Kk for xen-users@lists.xen.org; Tue, 25 Sep 2012 21:55:49 +0000 Received: from [85.158.138.51:41901] by server-10.bemta-3.messagelabs.com id A1/DD-10411-46822605; Tue, 25 Sep 2012 21:55:48 +0000 X-Env-Sender: cdelorme@gmail.com X-Msg-Ref: server-16.tower-174.messagelabs.com!1348610146!31875746!1 X-Originating-IP: [209.85.223.173] X-SpamReason: No, hits=1.2 required=7.0 tests=HTML_10_20,HTML_MESSAGE, ML_RADAR_SPEW_LINKS_14,RCVD_BY_IP,spamassassin: X-StarScan-Received: X-StarScan-Version: 6.6.1.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 7104 invoked from network); 25 Sep 2012 21:55:48 -0000 Received: from mail-ie0-f173.google.com (HELO mail-ie0-f173.google.com) (209.85.223.173) by server-16.tower-174.messagelabs.com with RC4-SHA encrypted SMTP; 25 Sep 2012 21:55:48 -0000 Received: by iea17 with SMTP id 17so13170874iea.32 for ; Tue, 25 Sep 2012 14:55:46 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=65jPdM7//O1xnluxpy2vj2fzr5m6aeNnoD5sq57Yla8=; b=GKxSVgCdVypS7unHLXPyz7lRzFrgL8Uw3RNDFSdHY0Zdtwlhc1b5RFBNdT+ZAZMPUB vDVE/3o+9ByiiwKYlk9bz14AL0yO+sRILM9FTQBB3C8pPA1Rl2YyHnD3tU6f0mTzAda7 /WusE+ztaFIYG4iydJBZfU2a9SSaY3LvJSrpG0GAIfMkwyV5u6+WxhfDu/kmHq90yV0u ihp5ttQccHh+94AlczOECHDuYo8stmwO22SGZVRwyRyo0qOSICV39IUTcFIHILQ1jhls tNpwnjfSJmzlXJ4m+2nKGC3sT6wLQ+Ap5PycYERcB3JIEJCkMkotYRyTfY68WcXYMR8z IJRA== MIME-Version: 1.0 Received: by 10.50.47.227 with SMTP id g3mr9569150ign.5.1348610146330; Tue, 25 Sep 2012 14:55:46 -0700 (PDT) Received: by 10.64.102.167 with HTTP; Tue, 25 Sep 2012 14:55:46 -0700 (PDT) In-Reply-To: References: <1348475695.3452.39.camel@zakaz.uk.xensource.com> <1348477766.3452.52.camel@zakaz.uk.xensource.com> <1348479759.3452.59.camel@zakaz.uk.xensource.com> Date: Tue, 25 Sep 2012 17:55:46 -0400 Message-ID: From: Casey DeLorme To: Ian Campbell Cc: xen-users Subject: Re: [Xen-users] xl create bug on first-attempt with passthrough X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============2108332067935800080==" Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org --===============2108332067935800080== Content-Type: multipart/alternative; boundary=14dae9340cf3b6674504ca8dc472 --14dae9340cf3b6674504ca8dc472 Content-Type: text/plain; charset=ISO-8859-1 Added dom0_mem=4096MB to my grub configuration, rebooted, and all is well. I am no longer getting any errors. Ian, thank you very much for the suggestion, even though the error message claimed it was memory I would never have assumed a problem with the ballooning. I will be sure to draft up something to send to the xen-devel list. I use Dom0 for development, when I am not using the HVM for multimedia. So I have left ballooning on, so if more RAM is needed it can access it. ~Casey --14dae9340cf3b6674504ca8dc472 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable
Added dom0_mem=3D4096MB to my grub configuration, rebooted, and a= ll is well. =A0I am no longer getting any errors.

= Ian, thank you very much for the suggestion, even though the error message = claimed it was memory I would never have assumed a problem with the balloon= ing. =A0I will be sure to draft up something to send to the xen-devel list.=

I use Dom0 for development, when I am not using the HVM= for multimedia. =A0So I have left ballooning on, so if more RAM is needed = it can access it.

~Casey
--14dae9340cf3b6674504ca8dc472-- --===============2108332067935800080== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users --===============2108332067935800080==-- From xen-users-bounces@lists.xen.org Tue Sep 25 21:56:44 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Tue, 25 Sep 2012 21:56:44 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TGd6d-0002W7-7x; Tue, 25 Sep 2012 21:55:51 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TGd6b-0002Vs-Kk for xen-users@lists.xen.org; Tue, 25 Sep 2012 21:55:49 +0000 Received: from [85.158.138.51:41901] by server-10.bemta-3.messagelabs.com id A1/DD-10411-46822605; Tue, 25 Sep 2012 21:55:48 +0000 X-Env-Sender: cdelorme@gmail.com X-Msg-Ref: server-16.tower-174.messagelabs.com!1348610146!31875746!1 X-Originating-IP: [209.85.223.173] X-SpamReason: No, hits=1.2 required=7.0 tests=HTML_10_20,HTML_MESSAGE, ML_RADAR_SPEW_LINKS_14,RCVD_BY_IP,spamassassin: X-StarScan-Received: X-StarScan-Version: 6.6.1.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 7104 invoked from network); 25 Sep 2012 21:55:48 -0000 Received: from mail-ie0-f173.google.com (HELO mail-ie0-f173.google.com) (209.85.223.173) by server-16.tower-174.messagelabs.com with RC4-SHA encrypted SMTP; 25 Sep 2012 21:55:48 -0000 Received: by iea17 with SMTP id 17so13170874iea.32 for ; Tue, 25 Sep 2012 14:55:46 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=65jPdM7//O1xnluxpy2vj2fzr5m6aeNnoD5sq57Yla8=; b=GKxSVgCdVypS7unHLXPyz7lRzFrgL8Uw3RNDFSdHY0Zdtwlhc1b5RFBNdT+ZAZMPUB vDVE/3o+9ByiiwKYlk9bz14AL0yO+sRILM9FTQBB3C8pPA1Rl2YyHnD3tU6f0mTzAda7 /WusE+ztaFIYG4iydJBZfU2a9SSaY3LvJSrpG0GAIfMkwyV5u6+WxhfDu/kmHq90yV0u ihp5ttQccHh+94AlczOECHDuYo8stmwO22SGZVRwyRyo0qOSICV39IUTcFIHILQ1jhls tNpwnjfSJmzlXJ4m+2nKGC3sT6wLQ+Ap5PycYERcB3JIEJCkMkotYRyTfY68WcXYMR8z IJRA== MIME-Version: 1.0 Received: by 10.50.47.227 with SMTP id g3mr9569150ign.5.1348610146330; Tue, 25 Sep 2012 14:55:46 -0700 (PDT) Received: by 10.64.102.167 with HTTP; Tue, 25 Sep 2012 14:55:46 -0700 (PDT) In-Reply-To: References: <1348475695.3452.39.camel@zakaz.uk.xensource.com> <1348477766.3452.52.camel@zakaz.uk.xensource.com> <1348479759.3452.59.camel@zakaz.uk.xensource.com> Date: Tue, 25 Sep 2012 17:55:46 -0400 Message-ID: From: Casey DeLorme To: Ian Campbell Cc: xen-users Subject: Re: [Xen-users] xl create bug on first-attempt with passthrough X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============2108332067935800080==" Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org --===============2108332067935800080== Content-Type: multipart/alternative; boundary=14dae9340cf3b6674504ca8dc472 --14dae9340cf3b6674504ca8dc472 Content-Type: text/plain; charset=ISO-8859-1 Added dom0_mem=4096MB to my grub configuration, rebooted, and all is well. I am no longer getting any errors. Ian, thank you very much for the suggestion, even though the error message claimed it was memory I would never have assumed a problem with the ballooning. I will be sure to draft up something to send to the xen-devel list. I use Dom0 for development, when I am not using the HVM for multimedia. So I have left ballooning on, so if more RAM is needed it can access it. ~Casey --14dae9340cf3b6674504ca8dc472 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable
Added dom0_mem=3D4096MB to my grub configuration, rebooted, and a= ll is well. =A0I am no longer getting any errors.

= Ian, thank you very much for the suggestion, even though the error message = claimed it was memory I would never have assumed a problem with the balloon= ing. =A0I will be sure to draft up something to send to the xen-devel list.=

I use Dom0 for development, when I am not using the HVM= for multimedia. =A0So I have left ballooning on, so if more RAM is needed = it can access it.

~Casey
--14dae9340cf3b6674504ca8dc472-- --===============2108332067935800080== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users --===============2108332067935800080==-- From xen-users-bounces@lists.xen.org Wed Sep 26 08:50:21 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Wed, 26 Sep 2012 08:50:21 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TGnIr-0006XY-Ib; Wed, 26 Sep 2012 08:49:09 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TGnIq-0006XT-16 for xen-users@lists.xen.org; Wed, 26 Sep 2012 08:49:08 +0000 Received: from [85.158.143.99:46212] by server-2.bemta-4.messagelabs.com id 88/A4-06610-381C2605; Wed, 26 Sep 2012 08:49:07 +0000 X-Env-Sender: Ian.Campbell@citrix.com X-Msg-Ref: server-3.tower-216.messagelabs.com!1348649346!31212274!1 X-Originating-IP: [62.200.22.115] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogNjIuMjAwLjIyLjExNSA9PiAxMTE1NzQ=\n X-StarScan-Received: X-StarScan-Version: 6.6.1.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 706 invoked from network); 26 Sep 2012 08:49:06 -0000 Received: from smtp.eu.citrix.com (HELO SMTP.EU.CITRIX.COM) (62.200.22.115) by server-3.tower-216.messagelabs.com with RC4-SHA encrypted SMTP; 26 Sep 2012 08:49:06 -0000 X-IronPort-AV: E=Sophos;i="4.80,489,1344211200"; d="scan'208";a="14769740" Received: from lonpmailmx01.citrite.net ([10.30.203.162]) by LONPIPO01.EU.CITRIX.COM with ESMTP/TLS/RC4-MD5; 26 Sep 2012 08:49:06 +0000 Received: from [10.80.2.42] (10.80.2.42) by LONPMAILMX01.citrite.net (10.30.203.162) with Microsoft SMTP Server id 8.3.279.1; Wed, 26 Sep 2012 09:49:06 +0100 Message-ID: <1348649344.19176.12.camel@zakaz.uk.xensource.com> From: Ian Campbell To: Will Clayton Date: Wed, 26 Sep 2012 09:49:04 +0100 In-Reply-To: References: Organization: Citrix Systems, Inc. X-Mailer: Evolution 3.4.3-1 MIME-Version: 1.0 Cc: "xen-users@lists.xen.org" Subject: Re: [Xen-users] Xen VMs stop completely instead of restarting X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org On Tue, 2012-09-25 at 20:12 +0100, Will Clayton wrote: > As you can see there is not much to be said about this, unless I am > completely missing something - in which case a kick in the right > direction towards some documentation would be greatly appreciated. The wiki has a fair bit of documentation including links to online versions of the manpages for xl and xl.cfg. What exactly were you looking for that you were unable to find? (and where did you look so we can improve the signposting). Note that libxenlight is a library used to build toolstacks, it is not itself a toolstack. You appear to be using the "xl" toolstack, searching for info on that rather than libxkl might help your google-fu. http://wiki.xen.org/wiki/Reporting_Bugs_against_Xen has some pointers to log files which you might want to investigate too. Ian. _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Wed Sep 26 08:50:21 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Wed, 26 Sep 2012 08:50:21 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TGnIr-0006XY-Ib; Wed, 26 Sep 2012 08:49:09 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TGnIq-0006XT-16 for xen-users@lists.xen.org; Wed, 26 Sep 2012 08:49:08 +0000 Received: from [85.158.143.99:46212] by server-2.bemta-4.messagelabs.com id 88/A4-06610-381C2605; Wed, 26 Sep 2012 08:49:07 +0000 X-Env-Sender: Ian.Campbell@citrix.com X-Msg-Ref: server-3.tower-216.messagelabs.com!1348649346!31212274!1 X-Originating-IP: [62.200.22.115] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogNjIuMjAwLjIyLjExNSA9PiAxMTE1NzQ=\n X-StarScan-Received: X-StarScan-Version: 6.6.1.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 706 invoked from network); 26 Sep 2012 08:49:06 -0000 Received: from smtp.eu.citrix.com (HELO SMTP.EU.CITRIX.COM) (62.200.22.115) by server-3.tower-216.messagelabs.com with RC4-SHA encrypted SMTP; 26 Sep 2012 08:49:06 -0000 X-IronPort-AV: E=Sophos;i="4.80,489,1344211200"; d="scan'208";a="14769740" Received: from lonpmailmx01.citrite.net ([10.30.203.162]) by LONPIPO01.EU.CITRIX.COM with ESMTP/TLS/RC4-MD5; 26 Sep 2012 08:49:06 +0000 Received: from [10.80.2.42] (10.80.2.42) by LONPMAILMX01.citrite.net (10.30.203.162) with Microsoft SMTP Server id 8.3.279.1; Wed, 26 Sep 2012 09:49:06 +0100 Message-ID: <1348649344.19176.12.camel@zakaz.uk.xensource.com> From: Ian Campbell To: Will Clayton Date: Wed, 26 Sep 2012 09:49:04 +0100 In-Reply-To: References: Organization: Citrix Systems, Inc. X-Mailer: Evolution 3.4.3-1 MIME-Version: 1.0 Cc: "xen-users@lists.xen.org" Subject: Re: [Xen-users] Xen VMs stop completely instead of restarting X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org On Tue, 2012-09-25 at 20:12 +0100, Will Clayton wrote: > As you can see there is not much to be said about this, unless I am > completely missing something - in which case a kick in the right > direction towards some documentation would be greatly appreciated. The wiki has a fair bit of documentation including links to online versions of the manpages for xl and xl.cfg. What exactly were you looking for that you were unable to find? (and where did you look so we can improve the signposting). Note that libxenlight is a library used to build toolstacks, it is not itself a toolstack. You appear to be using the "xl" toolstack, searching for info on that rather than libxkl might help your google-fu. http://wiki.xen.org/wiki/Reporting_Bugs_against_Xen has some pointers to log files which you might want to investigate too. Ian. _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Wed Sep 26 15:09:07 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Wed, 26 Sep 2012 15:09:07 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TGtDR-00035r-7V; Wed, 26 Sep 2012 15:07:57 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TGtDP-00035l-N2 for xen-users@lists.xen.org; Wed, 26 Sep 2012 15:07:55 +0000 Received: from [85.158.143.35:39753] by server-3.bemta-4.messagelabs.com id 41/52-10986-B4A13605; Wed, 26 Sep 2012 15:07:55 +0000 X-Env-Sender: w.d.clayton@gmail.com X-Msg-Ref: server-16.tower-21.messagelabs.com!1348672073!13774270!1 X-Originating-IP: [209.85.216.52] X-SpamReason: No, hits=1.2 required=7.0 tests=HTML_20_30,HTML_MESSAGE, ML_RADAR_SPEW_LINKS_14,RCVD_BY_IP,spamassassin: X-StarScan-Received: X-StarScan-Version: 6.6.1.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 4691 invoked from network); 26 Sep 2012 15:07:54 -0000 Received: from mail-qa0-f52.google.com (HELO mail-qa0-f52.google.com) (209.85.216.52) by server-16.tower-21.messagelabs.com with RC4-SHA encrypted SMTP; 26 Sep 2012 15:07:54 -0000 Received: by qabg24 with SMTP id g24so1268504qab.11 for ; Wed, 26 Sep 2012 08:07:53 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type; bh=OGqSLxxfBwxjz6LMOyPla7vve4Bk0+IB5R+S3WMG4O0=; b=HE0NCMhGPF0x4TYn8JVi8zfub6GROx7bd+bJCYLBaMEIZxeC/wKZGibAFSl8N8kSeV iTFk9wc8v/ujjd0oLxccflH3xY8TfXW4YU+YvrDJXJa5xYhoxtrf3ixL5znClr+/K/+Z mnyZDP919P2hnSlS686fKHt/QfBB0/lCjfijxzZ0uyUhoM+w/WJmYvY1r21ERKacd1I3 WzB1HiOaD0AarY95PB7L2CTMHm+wrPcj7adakiM6UKypIjWCU1nRCumSa8CLPPa9/S7R s+lYTI1N7HZAU46NY2iaDy0nJ6rD6nrXtV5bYA6dj5kPmqzWjMCQAjZjR9hEf0eQGz9Y 0gzg== Received: by 10.224.207.8 with SMTP id fw8mr2575184qab.92.1348672072978; Wed, 26 Sep 2012 08:07:52 -0700 (PDT) MIME-Version: 1.0 Received: by 10.49.61.137 with HTTP; Wed, 26 Sep 2012 08:07:32 -0700 (PDT) In-Reply-To: <1348649344.19176.12.camel@zakaz.uk.xensource.com> References: <1348649344.19176.12.camel@zakaz.uk.xensource.com> From: Will Clayton Date: Wed, 26 Sep 2012 10:07:32 -0500 Message-ID: To: Ian Campbell Cc: "xen-users@lists.xen.org" Subject: Re: [Xen-users] Xen VMs stop completely instead of restarting X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============3177750727763934317==" Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org --===============3177750727763934317== Content-Type: multipart/alternative; boundary=20cf300fb263d40f7d04ca9c2fab --20cf300fb263d40f7d04ca9c2fab Content-Type: text/plain; charset=ISO-8859-1 Thanks Ian. Looks like my message got mangled again. What I was trying to paste was the on-crash, on-reboot, and on-destory lines that say restart, restart, and destroy respectively. I know there are underscores in those parameters, but I typed hyphens here in case that's causing my posts go show up without that info. Thank you for the suggestions on the documentation. If someone doesn't show up with a solution I will see about getting a full bug report going. On Wed, Sep 26, 2012 at 3:49 AM, Ian Campbell wrote: > On Tue, 2012-09-25 at 20:12 +0100, Will Clayton wrote: > > As you can see there is not much to be said about this, unless I am > > completely missing something - in which case a kick in the right > > direction towards some documentation would be greatly appreciated. > > The wiki has a fair bit of documentation including links to online > versions of the manpages for xl and xl.cfg. What exactly were you > looking for that you were unable to find? (and where did you look so we > can improve the signposting). > > Note that libxenlight is a library used to build toolstacks, it is not > itself a toolstack. You appear to be using the "xl" toolstack, searching > for info on that rather than libxkl might help your google-fu. > > http://wiki.xen.org/wiki/Reporting_Bugs_against_Xen has some pointers to > log files which you might want to investigate too. > > Ian. > > > --20cf300fb263d40f7d04ca9c2fab Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Thanks Ian.

Looks like my message got mangled again. What I was tryi= ng to paste was the on-crash, on-reboot, and on-destory lines that say rest= art, restart, and destroy respectively.

I know there are underscores= in those parameters, but I typed hyphens here in case that's causing m= y posts go show up without that info.

Thank you for the suggestions on the documentation. If someone doesn= 9;t show up with a solution I will see about getting a full bug report goin= g.

On Wed, Sep 26, 2012 at 3:49 AM, Ian C= ampbell <Ian.Campbell@citrix.com> wrote:
On Tue, 2012-09-25 at 20:1= 2 +0100, Will Clayton wrote:
> As you can see there is not much to be said about this, unless I am > completely missing something - in which case a kick in the right
> direction towards some documentation would be greatly appreciated.

The wiki has a fair bit of documentation including links to online versions of the manpages for xl and xl.cfg. What exactly were you
looking for that you were unable to find? (and where did you look so we
can improve the signposting).

Note that libxenlight is a library used to build toolstacks, it is not
itself a toolstack. You appear to be using the "xl" toolstack, se= arching
for info on that rather than libxkl might help your google-fu.

http://wiki.xen.org/wiki/Reporting_Bugs_against_Xen has some poi= nters to
log files which you might want to investigate too.

Ian.



--20cf300fb263d40f7d04ca9c2fab-- --===============3177750727763934317== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users --===============3177750727763934317==-- From xen-users-bounces@lists.xen.org Wed Sep 26 15:09:07 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Wed, 26 Sep 2012 15:09:07 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TGtDR-00035r-7V; Wed, 26 Sep 2012 15:07:57 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TGtDP-00035l-N2 for xen-users@lists.xen.org; Wed, 26 Sep 2012 15:07:55 +0000 Received: from [85.158.143.35:39753] by server-3.bemta-4.messagelabs.com id 41/52-10986-B4A13605; Wed, 26 Sep 2012 15:07:55 +0000 X-Env-Sender: w.d.clayton@gmail.com X-Msg-Ref: server-16.tower-21.messagelabs.com!1348672073!13774270!1 X-Originating-IP: [209.85.216.52] X-SpamReason: No, hits=1.2 required=7.0 tests=HTML_20_30,HTML_MESSAGE, ML_RADAR_SPEW_LINKS_14,RCVD_BY_IP,spamassassin: X-StarScan-Received: X-StarScan-Version: 6.6.1.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 4691 invoked from network); 26 Sep 2012 15:07:54 -0000 Received: from mail-qa0-f52.google.com (HELO mail-qa0-f52.google.com) (209.85.216.52) by server-16.tower-21.messagelabs.com with RC4-SHA encrypted SMTP; 26 Sep 2012 15:07:54 -0000 Received: by qabg24 with SMTP id g24so1268504qab.11 for ; Wed, 26 Sep 2012 08:07:53 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type; bh=OGqSLxxfBwxjz6LMOyPla7vve4Bk0+IB5R+S3WMG4O0=; b=HE0NCMhGPF0x4TYn8JVi8zfub6GROx7bd+bJCYLBaMEIZxeC/wKZGibAFSl8N8kSeV iTFk9wc8v/ujjd0oLxccflH3xY8TfXW4YU+YvrDJXJa5xYhoxtrf3ixL5znClr+/K/+Z mnyZDP919P2hnSlS686fKHt/QfBB0/lCjfijxzZ0uyUhoM+w/WJmYvY1r21ERKacd1I3 WzB1HiOaD0AarY95PB7L2CTMHm+wrPcj7adakiM6UKypIjWCU1nRCumSa8CLPPa9/S7R s+lYTI1N7HZAU46NY2iaDy0nJ6rD6nrXtV5bYA6dj5kPmqzWjMCQAjZjR9hEf0eQGz9Y 0gzg== Received: by 10.224.207.8 with SMTP id fw8mr2575184qab.92.1348672072978; Wed, 26 Sep 2012 08:07:52 -0700 (PDT) MIME-Version: 1.0 Received: by 10.49.61.137 with HTTP; Wed, 26 Sep 2012 08:07:32 -0700 (PDT) In-Reply-To: <1348649344.19176.12.camel@zakaz.uk.xensource.com> References: <1348649344.19176.12.camel@zakaz.uk.xensource.com> From: Will Clayton Date: Wed, 26 Sep 2012 10:07:32 -0500 Message-ID: To: Ian Campbell Cc: "xen-users@lists.xen.org" Subject: Re: [Xen-users] Xen VMs stop completely instead of restarting X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============3177750727763934317==" Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org --===============3177750727763934317== Content-Type: multipart/alternative; boundary=20cf300fb263d40f7d04ca9c2fab --20cf300fb263d40f7d04ca9c2fab Content-Type: text/plain; charset=ISO-8859-1 Thanks Ian. Looks like my message got mangled again. What I was trying to paste was the on-crash, on-reboot, and on-destory lines that say restart, restart, and destroy respectively. I know there are underscores in those parameters, but I typed hyphens here in case that's causing my posts go show up without that info. Thank you for the suggestions on the documentation. If someone doesn't show up with a solution I will see about getting a full bug report going. On Wed, Sep 26, 2012 at 3:49 AM, Ian Campbell wrote: > On Tue, 2012-09-25 at 20:12 +0100, Will Clayton wrote: > > As you can see there is not much to be said about this, unless I am > > completely missing something - in which case a kick in the right > > direction towards some documentation would be greatly appreciated. > > The wiki has a fair bit of documentation including links to online > versions of the manpages for xl and xl.cfg. What exactly were you > looking for that you were unable to find? (and where did you look so we > can improve the signposting). > > Note that libxenlight is a library used to build toolstacks, it is not > itself a toolstack. You appear to be using the "xl" toolstack, searching > for info on that rather than libxkl might help your google-fu. > > http://wiki.xen.org/wiki/Reporting_Bugs_against_Xen has some pointers to > log files which you might want to investigate too. > > Ian. > > > --20cf300fb263d40f7d04ca9c2fab Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Thanks Ian.

Looks like my message got mangled again. What I was tryi= ng to paste was the on-crash, on-reboot, and on-destory lines that say rest= art, restart, and destroy respectively.

I know there are underscores= in those parameters, but I typed hyphens here in case that's causing m= y posts go show up without that info.

Thank you for the suggestions on the documentation. If someone doesn= 9;t show up with a solution I will see about getting a full bug report goin= g.

On Wed, Sep 26, 2012 at 3:49 AM, Ian C= ampbell <Ian.Campbell@citrix.com> wrote:
On Tue, 2012-09-25 at 20:1= 2 +0100, Will Clayton wrote:
> As you can see there is not much to be said about this, unless I am > completely missing something - in which case a kick in the right
> direction towards some documentation would be greatly appreciated.

The wiki has a fair bit of documentation including links to online versions of the manpages for xl and xl.cfg. What exactly were you
looking for that you were unable to find? (and where did you look so we
can improve the signposting).

Note that libxenlight is a library used to build toolstacks, it is not
itself a toolstack. You appear to be using the "xl" toolstack, se= arching
for info on that rather than libxkl might help your google-fu.

http://wiki.xen.org/wiki/Reporting_Bugs_against_Xen has some poi= nters to
log files which you might want to investigate too.

Ian.



--20cf300fb263d40f7d04ca9c2fab-- --===============3177750727763934317== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users --===============3177750727763934317==-- From xen-users-bounces@lists.xen.org Wed Sep 26 18:22:50 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Wed, 26 Sep 2012 18:22:50 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TGwEu-0008PZ-Sc; Wed, 26 Sep 2012 18:21:40 +0000 Received: from mail27.messagelabs.com ([193.109.254.147]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TGwEt-0008P6-Ml for xen-users@lists.xen.org; Wed, 26 Sep 2012 18:21:39 +0000 X-Env-Sender: jaceksburghardt@gmail.com X-Msg-Ref: server-6.tower-27.messagelabs.com!1348683692!6939713!1 X-Originating-IP: [209.85.216.173] X-SpamReason: No, hits=0.3 required=7.0 tests=ML_RADAR_SPEW_LINKS_14, RCVD_BY_IP,spamassassin: X-StarScan-Received: X-StarScan-Version: 6.6.1.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 27754 invoked from network); 26 Sep 2012 18:21:33 -0000 Received: from mail-qc0-f173.google.com (HELO mail-qc0-f173.google.com) (209.85.216.173) by server-6.tower-27.messagelabs.com with RC4-SHA encrypted SMTP; 26 Sep 2012 18:21:33 -0000 Received: by qcab12 with SMTP id b12so868186qca.32 for ; Wed, 26 Sep 2012 11:21:32 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:date:message-id:subject:from:to:content-type; bh=RKPukZtFMu2/mi4n9HxAdEzp+9p1IlaSZOAgRx7ga/g=; b=K9uJZ4M5iyfi7hxrH7+ZZ5WUj1+Gx1BMIr73nGLq3GUE4Fv49rjblZ6LRX4EIZc4p+ uhs2kt6Qx9NMrcAKndsEkO+7LtP1yaq6iNEbngJ0/hrMxMQey4G59HurVKa4/eULl1MP 3yNkmpi1PA1U20x8JkTSoo7adRO3aSwxCMfSeYTxkuiUfrjI0MrCS33rj2BOz3L6fcrz dy7z5LUdxX3jnj/GhE1uLOO2AXQa73vE0lKFR28ZdVPegAkudPgtNmGXFrwz17hQViTG wOpSVyZN28vmpCQjNHHulHrpm+oLORGVVGmjfNccwTyJkvRES/wrLVpDwOB++gjiTp6z XPtQ== MIME-Version: 1.0 Received: by 10.224.138.143 with SMTP id a15mr3901493qau.64.1348683692233; Wed, 26 Sep 2012 11:21:32 -0700 (PDT) Received: by 10.49.118.101 with HTTP; Wed, 26 Sep 2012 11:21:32 -0700 (PDT) Date: Wed, 26 Sep 2012 12:21:32 -0600 Message-ID: From: jacek burghardt To: xen-users Subject: [Xen-users] xen-debug log no /sys/ X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org In my log file I see erro listed below. Is there scsi module that should be loaded at boot ? cat: /sys/bus/scsi/devices/host0/vendor: No such file or directory cat: /sys/bus/scsi/devices/host0/model: No such file or directory cat: /sys/bus/scsi/devices/host0/type: No such file or directory cat: /sys/bus/scsi/devices/host0/rev: No such file or directory cat: /sys/bus/scsi/devices/host0/scsi_level: No such file or directory cat: /sys/bus/scsi/devices/host1/vendor: No such file or directory cat: /sys/bus/scsi/devices/host1/model: No such file or directory cat: /sys/bus/scsi/devices/host1/type: No such file or directory cat: /sys/bus/scsi/devices/host1/rev: No such file or directory cat: /sys/bus/scsi/devices/host1/scsi_level: No such file or directory cat: /sys/bus/scsi/devices/host2/vendor: No such file or directory cat: /sys/bus/scsi/devices/host2/model: No such file or directory cat: /sys/bus/scsi/devices/host2/type: No such file or directory cat: /sys/bus/scsi/devices/host2/rev: No such file or directory cat: /sys/bus/scsi/devices/host2/scsi_level: No such file or directory cat: /sys/bus/scsi/devices/host3/vendor: No such file or directory cat: /sys/bus/scsi/devices/host3/model: No such file or directory cat: /sys/bus/scsi/devices/host3/type: No such file or directory cat: /sys/bus/scsi/devices/host3/rev: No such file or directory cat: /sys/bus/scsi/devices/host3/scsi_level: No such file or directory cat: /sys/bus/scsi/devices/target0:0:0/vendor: No such file or directory cat: /sys/bus/scsi/devices/target0:0:0/model: No such file or directory cat: /sys/bus/scsi/devices/target0:0:0/type: No such file or directory cat: /sys/bus/scsi/devices/target0:0:0/rev: No such file or directory cat: /sys/bus/scsi/devices/target0:0:0/scsi_level: No such file or directory cat: /sys/bus/scsi/devices/target1:0:0/vendor: No such file or directory cat: /sys/bus/scsi/devices/target1:0:0/model: No such file or directory cat: /sys/bus/scsi/devices/target1:0:0/type: No such file or directory cat: /sys/bus/scsi/devices/target1:0:0/rev: No such file or directory cat: /sys/bus/scsi/devices/target1:0:0/scsi_level: No such file or directory cat: /sys/bus/scsi/devices/host4/vendor: No such file or directory cat: /sys/bus/scsi/devices/host4/model: No such file or directory cat: /sys/bus/scsi/devices/host4/type: No such file or directory cat: /sys/bus/scsi/devices/host4/rev: No such file or directory cat: /sys/bus/scsi/devices/host4/scsi_level: No such file or directory cat: /sys/bus/scsi/devices/host5/vendor: No such file or directory cat: /sys/bus/scsi/devices/host5/model: No such file or directory cat: /sys/bus/scsi/devices/host5/type: No such file or directory cat: /sys/bus/scsi/devices/host5/rev: No such file or directory cat: /sys/bus/scsi/devices/host5/scsi_level: No such file or directory _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Wed Sep 26 18:22:50 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Wed, 26 Sep 2012 18:22:50 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TGwEu-0008PZ-Sc; Wed, 26 Sep 2012 18:21:40 +0000 Received: from mail27.messagelabs.com ([193.109.254.147]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TGwEt-0008P6-Ml for xen-users@lists.xen.org; Wed, 26 Sep 2012 18:21:39 +0000 X-Env-Sender: jaceksburghardt@gmail.com X-Msg-Ref: server-6.tower-27.messagelabs.com!1348683692!6939713!1 X-Originating-IP: [209.85.216.173] X-SpamReason: No, hits=0.3 required=7.0 tests=ML_RADAR_SPEW_LINKS_14, RCVD_BY_IP,spamassassin: X-StarScan-Received: X-StarScan-Version: 6.6.1.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 27754 invoked from network); 26 Sep 2012 18:21:33 -0000 Received: from mail-qc0-f173.google.com (HELO mail-qc0-f173.google.com) (209.85.216.173) by server-6.tower-27.messagelabs.com with RC4-SHA encrypted SMTP; 26 Sep 2012 18:21:33 -0000 Received: by qcab12 with SMTP id b12so868186qca.32 for ; Wed, 26 Sep 2012 11:21:32 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:date:message-id:subject:from:to:content-type; bh=RKPukZtFMu2/mi4n9HxAdEzp+9p1IlaSZOAgRx7ga/g=; b=K9uJZ4M5iyfi7hxrH7+ZZ5WUj1+Gx1BMIr73nGLq3GUE4Fv49rjblZ6LRX4EIZc4p+ uhs2kt6Qx9NMrcAKndsEkO+7LtP1yaq6iNEbngJ0/hrMxMQey4G59HurVKa4/eULl1MP 3yNkmpi1PA1U20x8JkTSoo7adRO3aSwxCMfSeYTxkuiUfrjI0MrCS33rj2BOz3L6fcrz dy7z5LUdxX3jnj/GhE1uLOO2AXQa73vE0lKFR28ZdVPegAkudPgtNmGXFrwz17hQViTG wOpSVyZN28vmpCQjNHHulHrpm+oLORGVVGmjfNccwTyJkvRES/wrLVpDwOB++gjiTp6z XPtQ== MIME-Version: 1.0 Received: by 10.224.138.143 with SMTP id a15mr3901493qau.64.1348683692233; Wed, 26 Sep 2012 11:21:32 -0700 (PDT) Received: by 10.49.118.101 with HTTP; Wed, 26 Sep 2012 11:21:32 -0700 (PDT) Date: Wed, 26 Sep 2012 12:21:32 -0600 Message-ID: From: jacek burghardt To: xen-users Subject: [Xen-users] xen-debug log no /sys/ X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org In my log file I see erro listed below. Is there scsi module that should be loaded at boot ? cat: /sys/bus/scsi/devices/host0/vendor: No such file or directory cat: /sys/bus/scsi/devices/host0/model: No such file or directory cat: /sys/bus/scsi/devices/host0/type: No such file or directory cat: /sys/bus/scsi/devices/host0/rev: No such file or directory cat: /sys/bus/scsi/devices/host0/scsi_level: No such file or directory cat: /sys/bus/scsi/devices/host1/vendor: No such file or directory cat: /sys/bus/scsi/devices/host1/model: No such file or directory cat: /sys/bus/scsi/devices/host1/type: No such file or directory cat: /sys/bus/scsi/devices/host1/rev: No such file or directory cat: /sys/bus/scsi/devices/host1/scsi_level: No such file or directory cat: /sys/bus/scsi/devices/host2/vendor: No such file or directory cat: /sys/bus/scsi/devices/host2/model: No such file or directory cat: /sys/bus/scsi/devices/host2/type: No such file or directory cat: /sys/bus/scsi/devices/host2/rev: No such file or directory cat: /sys/bus/scsi/devices/host2/scsi_level: No such file or directory cat: /sys/bus/scsi/devices/host3/vendor: No such file or directory cat: /sys/bus/scsi/devices/host3/model: No such file or directory cat: /sys/bus/scsi/devices/host3/type: No such file or directory cat: /sys/bus/scsi/devices/host3/rev: No such file or directory cat: /sys/bus/scsi/devices/host3/scsi_level: No such file or directory cat: /sys/bus/scsi/devices/target0:0:0/vendor: No such file or directory cat: /sys/bus/scsi/devices/target0:0:0/model: No such file or directory cat: /sys/bus/scsi/devices/target0:0:0/type: No such file or directory cat: /sys/bus/scsi/devices/target0:0:0/rev: No such file or directory cat: /sys/bus/scsi/devices/target0:0:0/scsi_level: No such file or directory cat: /sys/bus/scsi/devices/target1:0:0/vendor: No such file or directory cat: /sys/bus/scsi/devices/target1:0:0/model: No such file or directory cat: /sys/bus/scsi/devices/target1:0:0/type: No such file or directory cat: /sys/bus/scsi/devices/target1:0:0/rev: No such file or directory cat: /sys/bus/scsi/devices/target1:0:0/scsi_level: No such file or directory cat: /sys/bus/scsi/devices/host4/vendor: No such file or directory cat: /sys/bus/scsi/devices/host4/model: No such file or directory cat: /sys/bus/scsi/devices/host4/type: No such file or directory cat: /sys/bus/scsi/devices/host4/rev: No such file or directory cat: /sys/bus/scsi/devices/host4/scsi_level: No such file or directory cat: /sys/bus/scsi/devices/host5/vendor: No such file or directory cat: /sys/bus/scsi/devices/host5/model: No such file or directory cat: /sys/bus/scsi/devices/host5/type: No such file or directory cat: /sys/bus/scsi/devices/host5/rev: No such file or directory cat: /sys/bus/scsi/devices/host5/scsi_level: No such file or directory _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Wed Sep 26 19:22:51 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Wed, 26 Sep 2012 19:22:51 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TGxAt-0001N8-3W; Wed, 26 Sep 2012 19:21:35 +0000 Received: from mail27.messagelabs.com ([193.109.254.147]) by lists.xen.org with smtp (Exim 4.72) (envelope-from ) id 1TGxAr-0001N3-Vh for xen-users@lists.xen.org; Wed, 26 Sep 2012 19:21:34 +0000 X-Env-Sender: matej.zary@cvtisr.sk X-Msg-Ref: server-12.tower-27.messagelabs.com!1348687287!12503673!1 X-Originating-IP: [193.87.7.3] X-SpamReason: No, hits=0.0 required=7.0 tests= X-StarScan-Received: X-StarScan-Version: 6.6.1.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 16167 invoked from network); 26 Sep 2012 19:21:27 -0000 Received: from virgo.cvtisr.sk (HELO mail.cvtisr.sk) (193.87.7.3) by server-12.tower-27.messagelabs.com with SMTP; 26 Sep 2012 19:21:27 -0000 Received: from localhost (unknown [127.0.0.1]) by mail.cvtisr.sk (Postfix) with ESMTP id 29A6292D7A for ; Wed, 26 Sep 2012 22:04:52 +0200 (CEST) X-Virus-Scanned: amavisd-new at cvtisr.sk Received: from mail.cvtisr.sk ([127.0.0.1]) by localhost (mail.cvtisr.sk [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id TqRCzsG10Ups for ; Wed, 26 Sep 2012 22:04:47 +0200 (CEST) Received: from aries.space.cvtisr.sk (unknown [192.168.1.51]) by mail.cvtisr.sk (Postfix) with ESMTP id D2F3B92D79 for ; Wed, 26 Sep 2012 22:04:47 +0200 (CEST) Received: from Aries.space.cvtisr.sk ([::1]) by aries.space.cvtisr.sk ([::1]) with mapi; Wed, 26 Sep 2012 21:21:22 +0200 From: Zary Matej To: "xen-users@lists.xen.org" Date: Wed, 26 Sep 2012 21:21:20 +0200 Thread-Topic: [Xen-users] VM move/copy/export Thread-Index: Ac2bRWdg/TCktGnXSJu7m2pZPiN4gQA1qezg Message-ID: <5DB0519124BB3D4DBEEB14426D4AC7EA6A72DB7174@aries.space.cvtisr.sk> References: <5061EB68.3090703@agr.unicamp.br> In-Reply-To: <5061EB68.3090703@agr.unicamp.br> Accept-Language: en-US Content-Language: sk-SK X-MS-Has-Attach: X-MS-TNEF-Correlator: acceptlanguage: en-US MIME-Version: 1.0 Subject: Re: [Xen-users] VM move/copy/export X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="iso-8859-2" Content-Transfer-Encoding: quoted-printable Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org >________________________________________ >From: xen-users-bounces@lists.xen.org [xen-users-bounces@lists.xen.org] = >On Behalf Of Clovis Tristao [clovis@agr.unicamp.br] >Sent: 25 September 2012 19:35 >To: xen-users@lists.xen.org >Subject: [Xen-users] VM move/copy/export > >Hi, > >I have two machines with xenserver, running in the same pool with = >multiple virtual machines. >When I try to move / copy / export from one machine to another = >xenserver, the message: Can not move virtual disks between SR site. Can = >not see required storage How do I solve this problem? I'm using version = >6.0.2 > >Thanks a lot, for any information, > >Cl=F3vis Hi there, first, it seems you're running Citrix XenServer so better place to ask this= kind of question is on their official forums at http://forums.citrix.com/c= ategory.jspa?categoryID=3D101 It seems like you don't have shared storage in your pool - shared storage c= ould be iSCSI volume, NFS export, of FC volume - visible to all members of = your XenServer pool. When you are using local storage for your VMs, you can= not migrate them in current version of XenServer (it should be possible in = upcoming new versions of XenServer IIRC). You can relocate VM from local st= orage to another host using VM Export function after shutting it down and t= hen import the VM on the another host. In case of using ext local storage (= not LVM), you can copy virtual disks with scp between hosts and then attach= them to new VM on the other host (after renaming the copied file with new = UUID and SR rescan). Cheers Matej _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Wed Sep 26 19:22:51 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Wed, 26 Sep 2012 19:22:51 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TGxAt-0001N8-3W; Wed, 26 Sep 2012 19:21:35 +0000 Received: from mail27.messagelabs.com ([193.109.254.147]) by lists.xen.org with smtp (Exim 4.72) (envelope-from ) id 1TGxAr-0001N3-Vh for xen-users@lists.xen.org; Wed, 26 Sep 2012 19:21:34 +0000 X-Env-Sender: matej.zary@cvtisr.sk X-Msg-Ref: server-12.tower-27.messagelabs.com!1348687287!12503673!1 X-Originating-IP: [193.87.7.3] X-SpamReason: No, hits=0.0 required=7.0 tests= X-StarScan-Received: X-StarScan-Version: 6.6.1.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 16167 invoked from network); 26 Sep 2012 19:21:27 -0000 Received: from virgo.cvtisr.sk (HELO mail.cvtisr.sk) (193.87.7.3) by server-12.tower-27.messagelabs.com with SMTP; 26 Sep 2012 19:21:27 -0000 Received: from localhost (unknown [127.0.0.1]) by mail.cvtisr.sk (Postfix) with ESMTP id 29A6292D7A for ; Wed, 26 Sep 2012 22:04:52 +0200 (CEST) X-Virus-Scanned: amavisd-new at cvtisr.sk Received: from mail.cvtisr.sk ([127.0.0.1]) by localhost (mail.cvtisr.sk [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id TqRCzsG10Ups for ; Wed, 26 Sep 2012 22:04:47 +0200 (CEST) Received: from aries.space.cvtisr.sk (unknown [192.168.1.51]) by mail.cvtisr.sk (Postfix) with ESMTP id D2F3B92D79 for ; Wed, 26 Sep 2012 22:04:47 +0200 (CEST) Received: from Aries.space.cvtisr.sk ([::1]) by aries.space.cvtisr.sk ([::1]) with mapi; Wed, 26 Sep 2012 21:21:22 +0200 From: Zary Matej To: "xen-users@lists.xen.org" Date: Wed, 26 Sep 2012 21:21:20 +0200 Thread-Topic: [Xen-users] VM move/copy/export Thread-Index: Ac2bRWdg/TCktGnXSJu7m2pZPiN4gQA1qezg Message-ID: <5DB0519124BB3D4DBEEB14426D4AC7EA6A72DB7174@aries.space.cvtisr.sk> References: <5061EB68.3090703@agr.unicamp.br> In-Reply-To: <5061EB68.3090703@agr.unicamp.br> Accept-Language: en-US Content-Language: sk-SK X-MS-Has-Attach: X-MS-TNEF-Correlator: acceptlanguage: en-US MIME-Version: 1.0 Subject: Re: [Xen-users] VM move/copy/export X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="iso-8859-2" Content-Transfer-Encoding: quoted-printable Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org >________________________________________ >From: xen-users-bounces@lists.xen.org [xen-users-bounces@lists.xen.org] = >On Behalf Of Clovis Tristao [clovis@agr.unicamp.br] >Sent: 25 September 2012 19:35 >To: xen-users@lists.xen.org >Subject: [Xen-users] VM move/copy/export > >Hi, > >I have two machines with xenserver, running in the same pool with = >multiple virtual machines. >When I try to move / copy / export from one machine to another = >xenserver, the message: Can not move virtual disks between SR site. Can = >not see required storage How do I solve this problem? I'm using version = >6.0.2 > >Thanks a lot, for any information, > >Cl=F3vis Hi there, first, it seems you're running Citrix XenServer so better place to ask this= kind of question is on their official forums at http://forums.citrix.com/c= ategory.jspa?categoryID=3D101 It seems like you don't have shared storage in your pool - shared storage c= ould be iSCSI volume, NFS export, of FC volume - visible to all members of = your XenServer pool. When you are using local storage for your VMs, you can= not migrate them in current version of XenServer (it should be possible in = upcoming new versions of XenServer IIRC). You can relocate VM from local st= orage to another host using VM Export function after shutting it down and t= hen import the VM on the another host. In case of using ext local storage (= not LVM), you can copy virtual disks with scp between hosts and then attach= them to new VM on the other host (after renaming the copied file with new = UUID and SR rescan). Cheers Matej _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Wed Sep 26 20:23:58 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Wed, 26 Sep 2012 20:23:58 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TGy87-000285-99; Wed, 26 Sep 2012 20:22:47 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TGy85-00027x-Sm for xen-users@lists.xen.org; Wed, 26 Sep 2012 20:22:46 +0000 Received: from [85.158.143.35:26444] by server-1.bemta-4.messagelabs.com id 3A/08-05684-51463605; Wed, 26 Sep 2012 20:22:45 +0000 X-Env-Sender: clovis@agr.unicamp.br X-Msg-Ref: server-2.tower-21.messagelabs.com!1348690962!9007957!1 X-Originating-IP: [143.106.74.4] X-SpamReason: No, hits=0.0 required=7.0 tests= X-StarScan-Received: X-StarScan-Version: 6.6.1.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 7909 invoked from network); 26 Sep 2012 20:22:44 -0000 Received: from mail.feagri.unicamp.br (HELO mail.feagri.unicamp.br) (143.106.74.4) by server-2.tower-21.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 26 Sep 2012 20:22:44 -0000 Received: from localhost (localhost.localdomain [127.0.0.1]) by mail.feagri.unicamp.br (Postfix) with ESMTP id AC0C281C31A for ; Wed, 26 Sep 2012 17:22:40 -0300 (BRT) X-Virus-Scanned: amavisd-new at feagri.unicamp.br Received: from mail.feagri.unicamp.br ([127.0.0.1]) by localhost (mail.feagri.unicamp.br [127.0.0.1]) (amavisd-new, port 10024) with SMTP id s4v0lBXF2B6L for ; Wed, 26 Sep 2012 17:22:38 -0300 (BRT) Received: from bambu.feagri.unicamp.br (bambu.feagri.unicamp.br [143.106.74.221]) by mail.feagri.unicamp.br (Postfix) with ESMTPA id D705881C310 for ; Wed, 26 Sep 2012 17:22:38 -0300 (BRT) Message-ID: <506364E7.1000001@agr.unicamp.br> Date: Wed, 26 Sep 2012 17:26:15 -0300 From: Clovis Tristao Organization: Unicamp-Feagri_Sinfo User-Agent: Mozilla/5.0 (X11; Linux i686; rv:15.0) Gecko/20120911 Thunderbird/15.0.1 MIME-Version: 1.0 To: xen-users@lists.xen.org References: <5061EB68.3090703@agr.unicamp.br> <5DB0519124BB3D4DBEEB14426D4AC7EA6A72DB7174@aries.space.cvtisr.sk> In-Reply-To: <5DB0519124BB3D4DBEEB14426D4AC7EA6A72DB7174@aries.space.cvtisr.sk> Subject: Re: [Xen-users] VM move/copy/export X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset="iso-8859-1"; Format="flowed" Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org Hi, Zary, Thanks for your information. Cl=F3vis Em 26-09-2012 16:21, Zary Matej escreveu: >> ________________________________________ >> From: xen-users-bounces@lists.xen.org [xen-users-bounces@lists.xen.org] >> On Behalf Of Clovis Tristao [clovis@agr.unicamp.br] >> Sent: 25 September 2012 19:35 >> To: xen-users@lists.xen.org >> Subject: [Xen-users] VM move/copy/export >> >> Hi, >> >> I have two machines with xenserver, running in the same pool with >> multiple virtual machines. >> When I try to move / copy / export from one machine to another >> xenserver, the message: Can not move virtual disks between SR site. Can >> not see required storage How do I solve this problem? I'm using version >> 6.0.2 >> >> Thanks a lot, for any information, >> >> Cl=F3vis > Hi there, > > first, it seems you're running Citrix XenServer so better place to ask th= is kind of question is on their official forums at http://forums.citrix.com= /category.jspa?categoryID=3D101 > > It seems like you don't have shared storage in your pool - shared storage= could be iSCSI volume, NFS export, of FC volume - visible to all members o= f your XenServer pool. When you are using local storage for your VMs, you c= annot migrate them in current version of XenServer (it should be possible i= n upcoming new versions of XenServer IIRC). You can relocate VM from local = storage to another host using VM Export function after shutting it down and= then import the VM on the another host. In case of using ext local storage= (not LVM), you can copy virtual disks with scp between hosts and then atta= ch them to new VM on the other host (after renaming the copied file with ne= w UUID and SR rescan). > > Cheers > > Matej > > > > _______________________________________________ > Xen-users mailing list > Xen-users@lists.xen.org > http://lists.xen.org/xen-users > -- = Clovis Tristao - UNICAMP/Faculdade de Engenharia Agricola Administrador de Redes - Secao de Informatica (SINFO) E-mail: clovis@feagri.unicamp.br http://www.feagri.unicamp.br MSN: clovis_tristao33@hotmail.com Fone: 55(19) 35211031-35211038-91173116 _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Wed Sep 26 20:23:58 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Wed, 26 Sep 2012 20:23:58 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TGy87-000285-99; Wed, 26 Sep 2012 20:22:47 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TGy85-00027x-Sm for xen-users@lists.xen.org; Wed, 26 Sep 2012 20:22:46 +0000 Received: from [85.158.143.35:26444] by server-1.bemta-4.messagelabs.com id 3A/08-05684-51463605; Wed, 26 Sep 2012 20:22:45 +0000 X-Env-Sender: clovis@agr.unicamp.br X-Msg-Ref: server-2.tower-21.messagelabs.com!1348690962!9007957!1 X-Originating-IP: [143.106.74.4] X-SpamReason: No, hits=0.0 required=7.0 tests= X-StarScan-Received: X-StarScan-Version: 6.6.1.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 7909 invoked from network); 26 Sep 2012 20:22:44 -0000 Received: from mail.feagri.unicamp.br (HELO mail.feagri.unicamp.br) (143.106.74.4) by server-2.tower-21.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 26 Sep 2012 20:22:44 -0000 Received: from localhost (localhost.localdomain [127.0.0.1]) by mail.feagri.unicamp.br (Postfix) with ESMTP id AC0C281C31A for ; Wed, 26 Sep 2012 17:22:40 -0300 (BRT) X-Virus-Scanned: amavisd-new at feagri.unicamp.br Received: from mail.feagri.unicamp.br ([127.0.0.1]) by localhost (mail.feagri.unicamp.br [127.0.0.1]) (amavisd-new, port 10024) with SMTP id s4v0lBXF2B6L for ; Wed, 26 Sep 2012 17:22:38 -0300 (BRT) Received: from bambu.feagri.unicamp.br (bambu.feagri.unicamp.br [143.106.74.221]) by mail.feagri.unicamp.br (Postfix) with ESMTPA id D705881C310 for ; Wed, 26 Sep 2012 17:22:38 -0300 (BRT) Message-ID: <506364E7.1000001@agr.unicamp.br> Date: Wed, 26 Sep 2012 17:26:15 -0300 From: Clovis Tristao Organization: Unicamp-Feagri_Sinfo User-Agent: Mozilla/5.0 (X11; Linux i686; rv:15.0) Gecko/20120911 Thunderbird/15.0.1 MIME-Version: 1.0 To: xen-users@lists.xen.org References: <5061EB68.3090703@agr.unicamp.br> <5DB0519124BB3D4DBEEB14426D4AC7EA6A72DB7174@aries.space.cvtisr.sk> In-Reply-To: <5DB0519124BB3D4DBEEB14426D4AC7EA6A72DB7174@aries.space.cvtisr.sk> Subject: Re: [Xen-users] VM move/copy/export X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset="iso-8859-1"; Format="flowed" Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org Hi, Zary, Thanks for your information. Cl=F3vis Em 26-09-2012 16:21, Zary Matej escreveu: >> ________________________________________ >> From: xen-users-bounces@lists.xen.org [xen-users-bounces@lists.xen.org] >> On Behalf Of Clovis Tristao [clovis@agr.unicamp.br] >> Sent: 25 September 2012 19:35 >> To: xen-users@lists.xen.org >> Subject: [Xen-users] VM move/copy/export >> >> Hi, >> >> I have two machines with xenserver, running in the same pool with >> multiple virtual machines. >> When I try to move / copy / export from one machine to another >> xenserver, the message: Can not move virtual disks between SR site. Can >> not see required storage How do I solve this problem? I'm using version >> 6.0.2 >> >> Thanks a lot, for any information, >> >> Cl=F3vis > Hi there, > > first, it seems you're running Citrix XenServer so better place to ask th= is kind of question is on their official forums at http://forums.citrix.com= /category.jspa?categoryID=3D101 > > It seems like you don't have shared storage in your pool - shared storage= could be iSCSI volume, NFS export, of FC volume - visible to all members o= f your XenServer pool. When you are using local storage for your VMs, you c= annot migrate them in current version of XenServer (it should be possible i= n upcoming new versions of XenServer IIRC). You can relocate VM from local = storage to another host using VM Export function after shutting it down and= then import the VM on the another host. In case of using ext local storage= (not LVM), you can copy virtual disks with scp between hosts and then atta= ch them to new VM on the other host (after renaming the copied file with ne= w UUID and SR rescan). > > Cheers > > Matej > > > > _______________________________________________ > Xen-users mailing list > Xen-users@lists.xen.org > http://lists.xen.org/xen-users > -- = Clovis Tristao - UNICAMP/Faculdade de Engenharia Agricola Administrador de Redes - Secao de Informatica (SINFO) E-mail: clovis@feagri.unicamp.br http://www.feagri.unicamp.br MSN: clovis_tristao33@hotmail.com Fone: 55(19) 35211031-35211038-91173116 _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Wed Sep 26 22:45:14 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Wed, 26 Sep 2012 22:45:14 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TH0Kh-00047C-Qw; Wed, 26 Sep 2012 22:43:55 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TH0Kf-000477-NR for xen-users@lists.xensource.com; Wed, 26 Sep 2012 22:43:53 +0000 Received: from [85.158.139.211:9262] by server-16.bemta-5.messagelabs.com id 4D/77-05998-82583605; Wed, 26 Sep 2012 22:43:52 +0000 X-Env-Sender: pradhanparas@gmail.com X-Msg-Ref: server-13.tower-206.messagelabs.com!1348699430!16114848!1 X-Originating-IP: [209.85.219.43] X-SpamReason: No, hits=0.3 required=7.0 tests=ML_RADAR_SPEW_LINKS_14, RCVD_BY_IP,spamassassin: X-StarScan-Received: X-StarScan-Version: 6.6.1.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 10739 invoked from network); 26 Sep 2012 22:43:52 -0000 Received: from mail-oa0-f43.google.com (HELO mail-oa0-f43.google.com) (209.85.219.43) by server-13.tower-206.messagelabs.com with RC4-SHA encrypted SMTP; 26 Sep 2012 22:43:52 -0000 Received: by oagk1 with SMTP id k1so1673280oag.30 for ; Wed, 26 Sep 2012 15:43:50 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:date:message-id:subject:from:to:content-type; bh=zPu+dTx4vYygBbIGRfzY6+4Md4OUAJzX44hANKCrRo8=; b=g+IascFQr90RtKRtIUzi2GrMxNF6uRYAmGtQzVqRKJC2Og/FR2rwAdxiSiho7ZIjGw 3Z7oq0b2WDvYyPT8+QG0pXsbS2G/JrAmltWJXGUthqihuFJbKFI/JvprdULi8BdMtOXB HA1W8oevw8mHHy00NYKdP26s7+sx6aU/chANmvu+hZ9LyLPUxADKCZj4TbtoWK6GTJBQ 33Mu3wUg/BE8kzkcDFPHt6rMla4gFv5+x8cWwOFjF8e9f0ssJQGDZo6jZMjKINQ3GeUm 7dqFOph4unID9j0O980X04jp4H4Imhb/wAPo5naAJGWkc3hGmcCKkhliPGsr/I1AhBHg oE7A== MIME-Version: 1.0 Received: by 10.182.69.73 with SMTP id c9mr1665063obu.33.1348699430621; Wed, 26 Sep 2012 15:43:50 -0700 (PDT) Received: by 10.60.46.37 with HTTP; Wed, 26 Sep 2012 15:43:50 -0700 (PDT) Date: Wed, 26 Sep 2012 17:43:50 -0500 Message-ID: From: Paras pradhan To: Xen Users Subject: [Xen-users] sparse to no sparse X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org Hi. I have an old Xen para virt vm which I created using sparse file. Is there any way to convert this vm image to non-sparse without shutting down the vm?. Thanks Paras. _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Wed Sep 26 22:45:14 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Wed, 26 Sep 2012 22:45:14 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TH0Kh-00047C-Qw; Wed, 26 Sep 2012 22:43:55 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TH0Kf-000477-NR for xen-users@lists.xensource.com; Wed, 26 Sep 2012 22:43:53 +0000 Received: from [85.158.139.211:9262] by server-16.bemta-5.messagelabs.com id 4D/77-05998-82583605; Wed, 26 Sep 2012 22:43:52 +0000 X-Env-Sender: pradhanparas@gmail.com X-Msg-Ref: server-13.tower-206.messagelabs.com!1348699430!16114848!1 X-Originating-IP: [209.85.219.43] X-SpamReason: No, hits=0.3 required=7.0 tests=ML_RADAR_SPEW_LINKS_14, RCVD_BY_IP,spamassassin: X-StarScan-Received: X-StarScan-Version: 6.6.1.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 10739 invoked from network); 26 Sep 2012 22:43:52 -0000 Received: from mail-oa0-f43.google.com (HELO mail-oa0-f43.google.com) (209.85.219.43) by server-13.tower-206.messagelabs.com with RC4-SHA encrypted SMTP; 26 Sep 2012 22:43:52 -0000 Received: by oagk1 with SMTP id k1so1673280oag.30 for ; Wed, 26 Sep 2012 15:43:50 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:date:message-id:subject:from:to:content-type; bh=zPu+dTx4vYygBbIGRfzY6+4Md4OUAJzX44hANKCrRo8=; b=g+IascFQr90RtKRtIUzi2GrMxNF6uRYAmGtQzVqRKJC2Og/FR2rwAdxiSiho7ZIjGw 3Z7oq0b2WDvYyPT8+QG0pXsbS2G/JrAmltWJXGUthqihuFJbKFI/JvprdULi8BdMtOXB HA1W8oevw8mHHy00NYKdP26s7+sx6aU/chANmvu+hZ9LyLPUxADKCZj4TbtoWK6GTJBQ 33Mu3wUg/BE8kzkcDFPHt6rMla4gFv5+x8cWwOFjF8e9f0ssJQGDZo6jZMjKINQ3GeUm 7dqFOph4unID9j0O980X04jp4H4Imhb/wAPo5naAJGWkc3hGmcCKkhliPGsr/I1AhBHg oE7A== MIME-Version: 1.0 Received: by 10.182.69.73 with SMTP id c9mr1665063obu.33.1348699430621; Wed, 26 Sep 2012 15:43:50 -0700 (PDT) Received: by 10.60.46.37 with HTTP; Wed, 26 Sep 2012 15:43:50 -0700 (PDT) Date: Wed, 26 Sep 2012 17:43:50 -0500 Message-ID: From: Paras pradhan To: Xen Users Subject: [Xen-users] sparse to no sparse X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org Hi. I have an old Xen para virt vm which I created using sparse file. Is there any way to convert this vm image to non-sparse without shutting down the vm?. Thanks Paras. _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Thu Sep 27 01:33:50 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Thu, 27 Sep 2012 01:33:50 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TH2xf-0001Mq-2N; Thu, 27 Sep 2012 01:32:19 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TH2xd-0001Ml-6L for xen-users@lists.xensource.com; Thu, 27 Sep 2012 01:32:17 +0000 Received: from [85.158.137.99:5800] by server-4.bemta-3.messagelabs.com id E7/84-14155-0ACA3605; Thu, 27 Sep 2012 01:32:16 +0000 X-Env-Sender: fajar@fajar.net X-Msg-Ref: server-11.tower-217.messagelabs.com!1348709534!18078776!1 X-Originating-IP: [209.85.214.171] X-SpamReason: No, hits=0.3 required=7.0 tests=RCVD_BY_IP X-StarScan-Received: X-StarScan-Version: 6.6.1.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 8297 invoked from network); 27 Sep 2012 01:32:15 -0000 Received: from mail-ob0-f171.google.com (HELO mail-ob0-f171.google.com) (209.85.214.171) by server-11.tower-217.messagelabs.com with RC4-SHA encrypted SMTP; 27 Sep 2012 01:32:15 -0000 Received: by obc16 with SMTP id 16so1803936obc.30 for ; Wed, 26 Sep 2012 18:32:13 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:x-gm-message-state; bh=v+Vn6P0yu5Budr7K3hennlXWskt2rtAL753WegB21XU=; b=OYvjgc8NmbgmMhHD1NjCp5SknQ3BlhTWzKrsNudox26weXIA4g5x2/SLrvzsZr5cgO 4LMSnNykNO+YUuZVWYgxvfLdDn+FEpEVuB2sdt5TxQf4cmVRsMd3GB7jWc4QPc+RDFrG TaygQ349hu6dNF7XkE9QcTHOMu2pujj/yjjasC/tKFPWVNRdi2WfyqU5u52PpjBryJgu oqyzptbbLRPu4IjQygkjVCiwjF+Q4CFZsZBg6CVKqmCp3PbLqWtWmEE3brSIRCoZIwmQ DU9Fqz0aveTXLI3+mqNbNR3vsJApBs/WdIppu1NYIfdBdjMZahCNWnKg8J/iHgOVoW9v O71g== MIME-Version: 1.0 Received: by 10.182.40.34 with SMTP id u2mr1992787obk.7.1348709533804; Wed, 26 Sep 2012 18:32:13 -0700 (PDT) Received: by 10.60.150.141 with HTTP; Wed, 26 Sep 2012 18:32:13 -0700 (PDT) In-Reply-To: References: Date: Thu, 27 Sep 2012 08:32:13 +0700 Message-ID: From: "Fajar A. Nugraha" To: Paras pradhan X-Gm-Message-State: ALoCoQl5YaUakQ2S1c+34YaofFWT6rzj/QuYWMvZvxufSSNSAqcmx8blfqUubyCCB4ZKtfUEYeZ5 Cc: Xen Users Subject: Re: [Xen-users] sparse to no sparse X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org On Thu, Sep 27, 2012 at 5:43 AM, Paras pradhan wrote: > Hi. > > I have an old Xen para virt vm which I created using sparse file. Is > there any way to convert this vm image to non-sparse without shutting > down the vm?. No. -- Fajar _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Thu Sep 27 01:33:50 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Thu, 27 Sep 2012 01:33:50 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TH2xf-0001Mq-2N; Thu, 27 Sep 2012 01:32:19 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TH2xd-0001Ml-6L for xen-users@lists.xensource.com; Thu, 27 Sep 2012 01:32:17 +0000 Received: from [85.158.137.99:5800] by server-4.bemta-3.messagelabs.com id E7/84-14155-0ACA3605; Thu, 27 Sep 2012 01:32:16 +0000 X-Env-Sender: fajar@fajar.net X-Msg-Ref: server-11.tower-217.messagelabs.com!1348709534!18078776!1 X-Originating-IP: [209.85.214.171] X-SpamReason: No, hits=0.3 required=7.0 tests=RCVD_BY_IP X-StarScan-Received: X-StarScan-Version: 6.6.1.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 8297 invoked from network); 27 Sep 2012 01:32:15 -0000 Received: from mail-ob0-f171.google.com (HELO mail-ob0-f171.google.com) (209.85.214.171) by server-11.tower-217.messagelabs.com with RC4-SHA encrypted SMTP; 27 Sep 2012 01:32:15 -0000 Received: by obc16 with SMTP id 16so1803936obc.30 for ; Wed, 26 Sep 2012 18:32:13 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:x-gm-message-state; bh=v+Vn6P0yu5Budr7K3hennlXWskt2rtAL753WegB21XU=; b=OYvjgc8NmbgmMhHD1NjCp5SknQ3BlhTWzKrsNudox26weXIA4g5x2/SLrvzsZr5cgO 4LMSnNykNO+YUuZVWYgxvfLdDn+FEpEVuB2sdt5TxQf4cmVRsMd3GB7jWc4QPc+RDFrG TaygQ349hu6dNF7XkE9QcTHOMu2pujj/yjjasC/tKFPWVNRdi2WfyqU5u52PpjBryJgu oqyzptbbLRPu4IjQygkjVCiwjF+Q4CFZsZBg6CVKqmCp3PbLqWtWmEE3brSIRCoZIwmQ DU9Fqz0aveTXLI3+mqNbNR3vsJApBs/WdIppu1NYIfdBdjMZahCNWnKg8J/iHgOVoW9v O71g== MIME-Version: 1.0 Received: by 10.182.40.34 with SMTP id u2mr1992787obk.7.1348709533804; Wed, 26 Sep 2012 18:32:13 -0700 (PDT) Received: by 10.60.150.141 with HTTP; Wed, 26 Sep 2012 18:32:13 -0700 (PDT) In-Reply-To: References: Date: Thu, 27 Sep 2012 08:32:13 +0700 Message-ID: From: "Fajar A. Nugraha" To: Paras pradhan X-Gm-Message-State: ALoCoQl5YaUakQ2S1c+34YaofFWT6rzj/QuYWMvZvxufSSNSAqcmx8blfqUubyCCB4ZKtfUEYeZ5 Cc: Xen Users Subject: Re: [Xen-users] sparse to no sparse X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org On Thu, Sep 27, 2012 at 5:43 AM, Paras pradhan wrote: > Hi. > > I have an old Xen para virt vm which I created using sparse file. Is > there any way to convert this vm image to non-sparse without shutting > down the vm?. No. -- Fajar _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Thu Sep 27 01:36:10 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Thu, 27 Sep 2012 01:36:10 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TH30A-0001dL-Sw; Thu, 27 Sep 2012 01:34:54 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TH309-0001d8-42 for xen-users@lists.xen.org; Thu, 27 Sep 2012 01:34:53 +0000 Received: from [85.158.143.35:18250] by server-2.bemta-4.messagelabs.com id DA/2F-06610-C3DA3605; Thu, 27 Sep 2012 01:34:52 +0000 X-Env-Sender: shades_of_grey@earthlink.net X-Msg-Ref: server-2.tower-21.messagelabs.com!1348709688!9028574!1 X-Originating-IP: [209.86.89.63] X-SpamReason: No, hits=1.4 required=7.0 tests=BODY_RANDOM_LONG, HTML_20_30,HTML_MESSAGE,ML_RADAR_SPEW_LINKS_14,spamassassin: X-StarScan-Received: X-StarScan-Version: 6.6.1.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 31096 invoked from network); 27 Sep 2012 01:34:48 -0000 Received: from elasmtp-junco.atl.sa.earthlink.net (HELO elasmtp-junco.atl.sa.earthlink.net) (209.86.89.63) by server-2.tower-21.messagelabs.com with SMTP; 27 Sep 2012 01:34:48 -0000 DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=dk20050327; d=earthlink.net; b=hby+wuiXgje0kKGT76cxQYlX6NFrbZl6JUoaxzr/OseId39WtJrRrhzNGwvN8hKy; h=Received:Message-ID:Date:From:User-Agent:MIME-Version:To:Subject:References:In-Reply-To:Content-Type:X-ELNK-Trace:X-Originating-IP; Received: from [66.167.250.229] (helo=[192.168.1.13]) by elasmtp-junco.atl.sa.earthlink.net with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.67) (envelope-from ) id 1TH302-0005Va-Fo for xen-users@lists.xen.org; Wed, 26 Sep 2012 21:34:47 -0400 Message-ID: <5063AD2E.10800@earthlink.net> Date: Wed, 26 Sep 2012 21:34:38 -0400 From: ShadesOfGrey User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:15.0) Gecko/20120907 Thunderbird/15.0.1 MIME-Version: 1.0 To: xen-users@lists.xen.org References: <505B86AE.9040507@earthlink.net> <505C8630.2090002@student.chalmers.se> <505FD74E.2050405@earthlink.net> <506056BC.3010705@student.chalmers.se> In-Reply-To: <506056BC.3010705@student.chalmers.se> X-ELNK-Trace: 0fe7bc40aa99bc8fc963772e86942a7b94f5150ab1c16ac0485087bba56e60092323022b087e5a23eca0a53b1d256162350badd9bab72f9c350badd9bab72f9c X-Originating-IP: 66.167.250.229 Subject: Re: [Xen-users] Recommendations for Virtulization Hardware X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============8504138819812557211==" Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org This is a multi-part message in MIME format. --===============8504138819812557211== Content-Type: multipart/alternative; boundary="------------050201090706010403010301" This is a multi-part message in MIME format. --------------050201090706010403010301 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit On 09/24/2012 08:49 AM, Robin Axelsson wrote: > On 2012-09-24 05:45, ShadesOfGrey wrote: >> Sorry for the late response, I've had a lot to digest. >> The lack of current information about Xen (and KVM) online has been >> frustrating --- especially finding the many proof of concept videos >> that demonstrated possibilities but offered no real specifics. >> Looking for specifics, I sought information from gaming and >> enthusiast sites; I figured finding confirmation of VT-d and AMD-Vi >> support on such sites would be more likely. However, I found that >> wasn't often the case. I did determine that ASRock motherboards seem >> to be the most likely to support VT-d, ASUS least likely (unless >> equipped with an Intel 'sanctioned' VT-d chipset). I had narrowed my >> choices to two motherboards that appear to offer VT-d support and was >> intending to contact the manufacturer before purchase. Both choices >> are a bit pricey and I've been reconsidering whether I should look to >> other motherboards to reduce costs. > > Some motherboards support IOMMU even though it is not found in the > user manual or specified on the website. Your best bet is to ask > customer support. A guy posted here that he got it working on an Intel > motherboard that doesn't even have options for it in the BIOS, so it > seems that in some cases it is only up to the CPU. This is not the > case with AMD though as I stated before. I have bought a couple of > Gigabyte GA990FX-UD7 myself, they are stable and have a good layout. > They have support for IOMMU but I haven't tested it thoroughly enough > to fully confirm this although I don't believe there would be any > problem. > I'm aware of this. In fact, I only have anecdotal evidence that the Gigabyte G1.Sniper 3 has IOMMU (VT-d) support. I intend to query the manufacturers, seeking confirmation of IOMMU support, of every motherboard that ends up on my short list. I may include other Z77 motherboards from MSI and Gigabyte, since there is concrete evidence that the Z77 chipset does support IOMMU. I did focus, however, on those motherboards I had some inkling could support IOMMU. Now I'm trying to expand my selection process to include less expensive options. > It surprises me that ASRock and ASUS are so different. ASRock is, or > at least used to be a subsidiary of ASUS so there shouldn't be that > much difference between them. Same here. But I guess things changed after ASRock was spun-off. >> This is precisely the kind of information I was looking for from the >> threads I started on Ars Technica. It's just unfortunate that FLR and >> D3 D0 support aren't often found in the tech specs of must expansion >> hardware. However, now that I know what to ask, I'll try contacting >> hardware manufacturers prior to purchasing any expansion hardware. >> Thank you! > > D3 and D0 are power states defined for devices in the ACPI > specification and can be used to control the supply voltage (Vcc) to > PCI and PCIe devices. You can find more information about it here for > example: > > http://en.wikipedia.org/wiki/Advanced_Configuration_and_Power_Interface > > --------------- > > > Device states > > The device states /D0/-/D3/ are device-dependent: > > * *D0* /Fully On/ is the operating state. > * *D1* and *D2* are intermediate power-states whose definition > varies by device. > * *D3* /Off/ has the device powered off and unresponsive to its bus. > > --------------- > > So, either it works for a certain type of hardware or it doesn't and I > wouldn't expect a vendor to state this "support" in the specifications > since it isn't a "feature" in and of itself if you get me. But maybe > this will change and maybe FLR support will become more widespread. I did read that Wikipedia entry after your referenced excerpt. To my mind, if a manufacturer claims support for the ACPI or PCIe spec and doesn't implement certain portions of those specs(some are optional after all), said manufacturer has an obligation to make that clear to your customers and users. But then, that's just me. Anyway, this information gives me what I need to ask the right questions of tech support before purchasing. >> From everything I've read, solutions that rely on any form of remote >> display protocols would be limited to a subset of Direct3D functions. >> Furthermore, these would vary from one implementation to another, >> thus making them far less attractive for gaming than VGA >> passthrough... Well, in my opinion anyway. >> >> VirtualBox's seamless mode is pretty nifty. But it's a Type 2 >> Hypervisor and relies on paravirtualized drivers that also suffer >> from the same limitations as remote display protocols. It's great for >> most things, but gaming is not one of them. And I'm speaking from >> personal experience. Though I haven't used them myself, the same >> would seem to hold true of Parallel's and VMWare's 'Workstation' >> offerings. At least, as far as I've gathered. >> >> FYI, the Type 1 Hypervisors from Parallel's and VMWare* are priced >> waaayyy outside my budget. >> > I understand that you want full 3D functionality for Windows gaming > but maybe you'll find the subset of 3D functionality for the Linux > machine acceptable. I have looked into VirtualGL and with TurboVNC, > you might get a pretty decent desktop environment and it seems like > most of the features are there already. It appears that the 3D is > rendered by hardware/GPU before it is streamed through VNC or Spice. > So it seems that you would need another GPU for that. You can find > more info on VirtualGL here: > > http://www.virtualgl.org/ Upon further investigation, the only option that is available to remotely translate Windows 3D apps is Microsoft's own RemoteFX. In which case, Microsoft products would be the foundation of my software stack... Something I'm trying to avoid. > > Also the line between a type 1 and type 2 hypervisor tend to get a bit > blurry. The point with type 1 is that it has access to ring-0 so that > it can get access directly to the hardware to be passed through to the > guests (I did confuse 'host' and 'guest' in my prior post). It also > doesn't need to ask the host OS for permission in the same way as a > type 2 hypervisor which is likely to give performance advantages in > some cases. > > However, even a type 2 hypervisor, although it is run as an > application inside the OS can get "type 1" like privileges. By > patching into the kernel and/or using special "dummy drivers" for > hardware to be shared with VMs you can achieve pretty much the same > thing, ergo it is no longer clear whether the hypervisor is a type 1 > or type 2. > > There is an article about it from the old IBM Mainframe days but I > can't seem to find it. > You might be right, the performance of a Type 2 Hypervisor may be sufficient. Regardless, I'd still have roughly the same hardware requirements as if I were going to use a Type 1 Hypervisor. I'd still need the same CPU, RAM, GPU, and storage requirements as I've already put forth. I could omit the potentially necessary additional components for use with a Type 1 Hypervisor. Things like USB controller, NIC, or sound card. But those costs would be replaced with the cost of licensing the Type2 Hypervisor. In which case, I don't really gain or lose anything by experimenting with Type 1 Hypervisors... At any rate, I could compare and contrast the performance of Type 1 and Type 2 Hypervisors using Paralles' and VMWare's trialware. It might take a good long while, but it would be an adventure. >> >> *I only found out about VMWare's 'free' vSphere after I'd written >> this response. >> >>> Also, it is highly recommended that you use ECC RAM for such >>> applications and it doesn't hurt to dedicate a few gigs of it to the >>> ZFS as RAM is used for cache. The good news is that most >>> motherboards with good chipsets support ECC RAM even though you >>> might not find anything about it in the user manuals. >> Again, thanks for the thorough explanation. This gives me a great >> deal to think about. The more I learn about ZFS, the less appealing >> it becomes. And by that I mean the confusion over which version of >> ZFS is in what OS? And just how well maintained the OSes supporting >> ZFS are? Now I have additional hardware considerations to keep in >> mind that may (or may not) make the cost of ZFS RAID-Z pool >> comparable to a hardware RAID5/6 solution anyway. Do you have any >> suggestions as to which of LSI HBAs I should be considering? I >> haven't found an HCL for ZFS in my searches. >> >> Out of curiosity --- and if you would happen to know --- do you think >> what you suggest about the HBA and SAS drives for ZFS also applies to >> Btrfs? I'm assuming it would, but I'd appreciate some confirmation. >> >> It's funny how the "I" in RAID never really seems to apply... >> Especially since it looks more and more like using ZFS or Btrfs will >> require I commit myself, from the start, to one or the other and a >> discrete HBA. Transitioning from an integrated SATA controller(s) and >> mdadm seems rather impractical. If I understand what's involved in >> doing so correctly. It may turn out that anything other than mdadm is >> price prohibitive. >> > > I don't think you will have a problem with getting ZFS to run and if > that's your only goal then you don't need to be very picky with your > choice of hardware. I find ZFS pretty easy and handy to use. I has > really great functionality and I don't have many bad things to say > about it so far. ZFS is a filesystem (along with a couple of software > tools to administrate it) just like EXT4 or NTFS so hardware support > depends on the platform it runs on. > > But the point with using ZFS is to get maximum protection against data > corruption and that's where the selection of hardware gets limited and > there are "best practices" set up to achieve that. I have not tested > ZFS on any other platform than on OpenSolaris and OpenIndiana but I do > know that it is well implemented on that platform and more mature > there than on any other (non-solaris) platform. Another advantage with > the OSOL/OI platform is that the CIFS functionality is implemented in > the kernel space and not in the userland which will give advantages > performance wise if you intend to share files with other windows > computers. (I don't deny that Samba is pretty good on Linux too. There > are some benchmarks on the phoronix website comparing samba with NFS > and they are in favor of Samba on those benchmarks...) The second best > implementation is found with FreeBSD and it is probably fairly mature > but I haven't tested it myself and some people have run into problems > with it in the past. The Linux version is probably merely at infancy > stage and likely not yet mature enough for regular use. It is probably > not as "bad" as btrfs though. There is quite a bit of information > about it on the phoronix.com website (and probably also at lwn.net): > > http://www.phoronix.com/scan.php?page=news_item&px=MTE4Nzc > My goal wasn't just to experiment with Btrfs, mdamd, or ZFS, if that's what you meant by, "with getting ZFS to run and if that's your only goal". I actually intend to use it 'in production'. In fact, the secondary role (Linux desktop being primary) for my proposed Virtualization rig is as file server (incl. httpd). Windows gaming is a tertiary or quaternary concern for me. So, finding out that the "best practices" for implementing ZFS include hardware I hadn't anticipated, is a bit off-putting. The diversity in ZFS implementations is what I meant about being confused. I'm not as familiar with the underlying platforms that utilize ZFS (other than Linux, and not with ZFS in use). Without that familiarity, it makes it more difficult to gauge which of those platforms would suit my purposes. For example, I had read a little bit about the degraded CIFS performance on FreeBSD and Linux due to their reliance on Samba (it residing in user-space being the issue). BTW, I meant to ask how you came to the conclusion that ECC RAM is supported on desktop motherboards? It's always been my understanding that you could use ECC RAM on such hardware, but there was no added benefit. > A search there on ZFS will give more articles. The latest official > version of ZFS is 28 and is probably implemented in both Linux, and > FreeBSD by now. Later versions have been released since Oracle killed > the OpenSolaris project and can be found with the commercial > closed-source Solaris platform that is supplied by Oracle. Things have > happened since Oracle pulled the plug on OSOL project and leading > developers behind the ZFS project such as Jeff Bonwick left Sun (after > the acquisition by Oracle) and joined up with the Illumos team > instead. So you cannot determine the stability of ZFS and ZPOOL merely > by looking into the version number unfortunately and I wouldn't expect > the FreeBSD implementation to be as stable as the Solaris > implementation. It just takes time for the implementation to mature > and the bugs to be weeded out and it just happens to have been around > for Solaris/OpenSolaris/Illumos for much longer than the other > platforms and the Solaris/Illumos version also happens to get first > dibs on the features. Among the Illumos people there is an ambition to > drop the version numbering altogether and instead talk about available > features. > One of the two ZFS implementations on Linux has reached version 28, the other is at version 23 and seems to be abandoned or stagnant (last release was May 2011). I'm not quite sure what the status of ZFS on FreeBSD is. From this table on Wikipedia, ZFS is at version 28. However the table notes that there is no CIFS or iSCSI support, which I'll try to independently confirm. And, as you say, the fact that ZFS (and Solaris as a whole) has essentially been forked, with the re-consolidation of Solaris as closed-source, just adds to the confusion. It's possible any given build of Illumos' version 28 of ZFS could have features or bug fixes no present in Oracle's version 33. > The recommendation to use SAS hard drives is not so much about the > quality of the hard drives themselves as it is about the SAS protocol. > The SAS protocol simply handles SCSI transport commands in a better > and more reliable manner than do SATA. I believe any decent SAS drive > would do. As for HBAs I wrote a list with LSI based hardware a while > ago here: > > https://www.illumos.org/boards/1/topics/572 > > the thing is that a lot of OEMs such as IBM, HP, Cisco, > Fujitsu-Siemens, Dell, ... supply their branded HBAs with LSI > circuitry on them. What hardware to choose depends on what you're > looking for. If you want an 8-port controller I would go for Intel > SASUC8I or LSI SAS3801E-R. If you want SAS/SATA3 with 6.0 Gb/s then > LSI's LSI SAS3801E-R series cards would be a better choice. I don't > know what OEMs have come up with in the SATA3 department since I wrote > that list but the chips to look for in that case are the LSI MegaRAID > 2004/2008/2016e depending on how many ports you want. > > If you want to read a further discussion about reliability of > different RAID setups I made a post about this in the following thread > (last post): > > http://communities.intel.com/thread/25945 > The cost of the drives is marginally higher than the drives I had budgeted, but including the cost of an SAS HBA is problematic. I hadn't expected purchasing an HBA from the very start. I'd hoped to deffer such a purchase for a bit, but you are saying that would be ill-advised. How likely is it I would encounter problems using SATA drives in the interim? Have you seen any price/feature advantage to reseller versions of LSI OEM products? I would think the offerings from Cisco, Dell, HP, and IBM would come at a premium as opposed to purchasing LSI branded hardware. Anyway, I thought there might be specific models from particular manufacturers to meet the "best practices" for ZFS. However, from your suggestions, I gather it really doesn't matter as long as the HBA is Intel or LSI? I have seen discussions in support of file system level redundancy like that of ZFS, precisely for the reason you cited. I guess I can add your link to the pro-FS pile of reference material. I wonder, should we perhaps move the discussion of ZFS to private email? It is a bit off-topic. --------------050201090706010403010301 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Re: [Xen-users] Recommendations for Virtulization Hardware
On 09/24/2012 08:49 AM, Robin Axelsson wrote:
On 2012-09-24 05:45, ShadesOfGrey wrote:
Sorry for the late response, I've had a lot to digest.
<snip>
The lack of current information about Xen (and KVM) online has been frustrating — especially finding the many proof of concept videos that demonstrated possibilities but offered no real specifics. Looking for specifics, I sought information from gaming and enthusiast sites; I figured finding confirmation of VT-d and AMD-Vi support on such sites would be more likely. However, I found that wasn't often the case. I did determine that ASRock motherboards seem to be the most likely to support VT-d, ASUS least likely (unless equipped with an Intel 'sanctioned' VT-d chipset). I had narrowed my choices to two motherboards that appear to offer VT-d support and was intending to contact the manufacturer before purchase. Both choices are a bit pricey and I've been reconsidering whether I should look to other motherboards to reduce costs.

Some motherboards support IOMMU even though it is not found in the user manual or specified on the website. Your best bet is to ask customer support. A guy posted here that he got it working on an Intel motherboard that doesn't even have options for it in the BIOS, so it seems that in some cases it is only up to the CPU. This is not the case with AMD though as I stated before. I have bought a couple of Gigabyte GA990FX-UD7 myself, they are stable and have a good layout. They have support for IOMMU but I haven't tested it thoroughly enough to fully confirm this although I don't believe there would be any problem.

I'm aware of this.  In fact, I only have anecdotal evidence that the Gigabyte G1.Sniper 3 has IOMMU (VT-d) support.  I intend to query the manufacturers, seeking confirmation of IOMMU support, of every motherboard that ends up on my short list.  I may include other Z77 motherboards from MSI and Gigabyte, since there is concrete evidence that the Z77 chipset does support IOMMU.  I did focus, however, on those motherboards I had some inkling could support IOMMU.  Now I'm trying to expand my selection process to include less expensive options.
It surprises me that ASRock and ASUS are so different. ASRock is, or at least used to be a subsidiary of ASUS so there shouldn't be that much difference between them.
Same here.  But I guess things changed after ASRock was spun-off.

<snip>
This is precisely the kind of information I was looking for from the threads I started on Ars Technica. It's just unfortunate that FLR and D3 D0 support aren't often found in the tech specs of must expansion hardware. However, now that I know what to ask, I'll try contacting hardware manufacturers prior to purchasing any expansion hardware. Thank you!

D3 and D0 are power states defined for devices in the ACPI specification and can be used to control the supply voltage (Vcc) to PCI and PCIe devices. You can find more information about it here for example:

http://en.wikipedia.org/wiki/Advanced_Configuration_and_Power_Interface

---------------

Device states

The device states D0-D3 are device-dependent:

  • D0 Fully On is the operating state.
  • D1 and D2 are intermediate power-states whose definition varies by device.
  • D3 Off has the device powered off and unresponsive to its bus.
---------------

So, either it works for a certain type of hardware or it doesn't and I wouldn't expect a vendor to state this "support" in the specifications since it isn't a "feature" in and of itself if you get me. But maybe this will change and maybe FLR support will become more widespread.
I did read that Wikipedia entry after your referenced excerpt.  To my mind, if a manufacturer claims support for the ACPI or PCIe spec and doesn't implement certain portions of those specs(some are optional after all), said manufacturer has an obligation to make that clear to your customers and users.  But then, that's just me.  Anyway, this information gives me what I need to ask the right questions of tech support before purchasing.

<snip>
From everything I've read, solutions that rely on any form of remote display protocols would be limited to a subset of Direct3D functions. Furthermore, these would vary from one implementation to another, thus making them far less attractive for gaming than VGA passthrough... Well, in my opinion anyway.

VirtualBox's seamless mode is pretty nifty. But it's a Type 2 Hypervisor and relies on paravirtualized drivers that also suffer from the same limitations as remote display protocols. It's great for most things, but gaming is not one of them. And I'm speaking from personal experience. Though I haven't used them myself, the same would seem to hold true of Parallel's and VMWare's 'Workstation' offerings. At least, as far as I've gathered.

FYI, the Type 1 Hypervisors from Parallel's and VMWare* are priced waaayyy outside my budget.

I understand that you want full 3D functionality for Windows gaming but maybe you'll find the subset of 3D functionality for the Linux machine acceptable. I have looked into VirtualGL and with TurboVNC, you might get a pretty decent desktop environment and it seems like most of the features are there already. It appears that the 3D is rendered by hardware/GPU before it is streamed through VNC or Spice. So it seems that you would need another GPU for that. You can find more info on VirtualGL here:

http://www.virtualgl.org/
Upon further investigation, the only option that is available to remotely translate Windows 3D apps is Microsoft's own RemoteFX.  In which case, Microsoft products would be the foundation of my software stack...  Something I'm trying to avoid.

Also the line between a type 1 and type 2 hypervisor tend to get a bit blurry. The point with type 1 is that it has access to ring-0 so that it can get access directly to the hardware to be passed through to the guests (I did confuse 'host' and 'guest' in my prior post). It also doesn't need to ask the host OS for permission in the same way as a type 2 hypervisor which is likely to give performance advantages in some cases.

However, even a type 2 hypervisor, although it is run as an application inside the OS can get "type 1" like privileges. By patching into the kernel and/or using special "dummy drivers" for hardware to be shared with VMs you can achieve pretty much the same thing, ergo it is no longer clear whether the hypervisor is a type 1 or type 2.

There is an article about it from the old IBM Mainframe days but I can't seem to find it.

You might be right, the performance of a Type 2 Hypervisor may be sufficient.  Regardless, I'd still have roughly the same hardware requirements as if I were going to use a Type 1 Hypervisor.  I'd still need the same CPU, RAM, GPU, and storage requirements as I've already put forth.  I could omit the potentially necessary additional components for use with a Type 1 Hypervisor.  Things like USB controller, NIC, or sound card.  But those costs would be replaced with the cost of licensing the Type2 Hypervisor.

In which case, I don't really gain or lose anything by experimenting with Type 1 Hypervisors...  At any rate, I could compare and contrast the performance of Type 1 and Type 2 Hypervisors using Paralles' and VMWare's trialware.  It might take a good long while, but it would be an adventure.

*I only found out about VMWare's 'free' vSphere after I'd written this response.

<snip>
Also, it is highly recommended that you use ECC RAM for such applications and it doesn't hurt to dedicate a few gigs of it to the ZFS as RAM is used for cache. The good news is that most motherboards with good chipsets support ECC RAM even though you might not find anything about it in the user manuals.
Again, thanks for the thorough explanation. This gives me a great deal to think about. The more I learn about ZFS, the less appealing it becomes. And by that I mean the confusion over which version of ZFS is in what OS? And just how well maintained the OSes supporting ZFS are? Now I have additional hardware considerations to keep in mind that may (or may not) make the cost of ZFS RAID-Z pool comparable to a hardware RAID5/6 solution anyway. Do you have any suggestions as to which of LSI HBAs I should be considering? I haven't found an HCL for ZFS in my searches.

Out of curiosity — and if you would happen to know — do you think what you suggest about the HBA and SAS drives for ZFS also applies to Btrfs? I'm assuming it would, but I'd appreciate some confirmation.

It's funny how the "I" in RAID never really seems to apply... Especially since it looks more and more like using ZFS or Btrfs will require I commit myself, from the start, to one or the other and a discrete HBA. Transitioning from an integrated SATA controller(s) and mdadm seems rather impractical. If I understand what's involved in doing so correctly. It may turn out that anything other than mdadm is price prohibitive.


I don't think you will have a problem with getting ZFS to run and if that's your only goal then you don't need to be very picky with your choice of hardware. I find ZFS pretty easy and handy to use. I has really great functionality and I don't have many bad things to say about it so far. ZFS is a filesystem (along with a couple of software tools to administrate it) just like EXT4 or NTFS so hardware support depends on the platform it runs on.

But the point with using ZFS is to get maximum protection against data corruption and that's where the selection of hardware gets limited and there are "best practices" set up to achieve that. I have not tested ZFS on any other platform than on OpenSolaris and OpenIndiana but I do know that it is well implemented on that platform and more mature there than on any other (non-solaris) platform. Another advantage with the OSOL/OI platform is that the CIFS functionality is implemented in the kernel space and not in the userland which will give advantages performance wise if you intend to share files with other windows computers. (I don't deny that Samba is pretty good on Linux too. There are some benchmarks on the phoronix website comparing samba with NFS and they are in favor of Samba on those benchmarks...) The second best implementation is found with FreeBSD and it is probably fairly mature but I haven't tested it myself and some people have run into problems with it in the past. The Linux version is probably merely at infancy stage and likely not yet mature enough for regular use. It is probably not as "bad" as btrfs though. There is quite a bit of information about it on the phoronix.com website (and probably also at lwn.net):

http://www.phoronix.com/scan.php?page=news_item&px=MTE4Nzc

My goal wasn't just to experiment with Btrfs, mdamd, or ZFS, if that's what you meant by, "with getting ZFS to run and if that's your only goal".  I actually intend to use it 'in production'.  In fact, the secondary role (Linux desktop being primary) for my proposed Virtualization rig is as file server (incl. httpd).  Windows gaming is a tertiary or quaternary concern for me.  So, finding out that the "best practices" for implementing ZFS include hardware I hadn't anticipated, is a bit off-putting.

The diversity in ZFS implementations is what I meant about being confused.  I'm not as familiar with the underlying platforms that utilize ZFS (other than Linux, and not with ZFS in use).  Without that familiarity, it makes it more difficult to gauge which of those platforms would suit my purposes.  For example, I had read a little bit about the degraded CIFS performance on FreeBSD and Linux due to their reliance on Samba (it residing in user-space being the issue).

BTW, I meant to ask how you came to the conclusion that ECC RAM is supported on desktop motherboards?  It's always been my understanding that you could use ECC RAM on such hardware, but there was no added benefit.
A search there on ZFS will give more articles. The latest official version of ZFS is 28 and is probably implemented in both Linux, and FreeBSD by now. Later versions have been released since Oracle killed the OpenSolaris project and can be found with the commercial closed-source Solaris platform that is supplied by Oracle. Things have happened since Oracle pulled the plug on OSOL project and leading developers behind the ZFS project such as Jeff Bonwick left Sun (after the acquisition by Oracle) and joined up with the Illumos team instead. So you cannot determine the stability of ZFS and ZPOOL merely by looking into the version number unfortunately and I wouldn't expect the FreeBSD implementation to be as stable as the Solaris implementation. It just takes time for the implementation to mature and the bugs to be weeded out and it just happens to have been around for Solaris/OpenSolaris/Illumos for much longer than the other platforms and the Solaris/Illumos version also happens to get first dibs on the features. Among the Illumos people there is an ambition to drop the version numbering altogether and instead talk about available features.

One of the two ZFS implementations on Linux has reached version 28, the other is at version 23 and seems to be abandoned or stagnant (last release was May 2011).  I'm not quite sure what the status of ZFS on FreeBSD is.  From this table on Wikipedia, ZFS is at version 28.  However the table notes that there is no CIFS or iSCSI support, which I'll try to independently confirm.  And, as you say, the fact that ZFS (and Solaris as a whole) has essentially been forked, with the re-consolidation of Solaris as closed-source, just adds to the confusion.  It's possible any given build of Illumos' version 28 of ZFS could have features or bug fixes no present in Oracle's version 33.
The recommendation to use SAS hard drives is not so much about the quality of the hard drives themselves as it is about the SAS protocol. The SAS protocol simply handles SCSI transport commands in a better and more reliable manner than do SATA. I believe any decent SAS drive would do. As for HBAs I wrote a list with LSI based hardware a while ago here:

https://www.illumos.org/boards/1/topics/572

the thing is that a lot of OEMs such as IBM, HP, Cisco, Fujitsu-Siemens, Dell, ... supply their branded HBAs with LSI circuitry on them. What hardware to choose depends on what you're looking for. If you want an 8-port controller I would go for Intel SASUC8I or LSI SAS3801E-R. If you want SAS/SATA3 with 6.0 Gb/s then LSI's LSI SAS3801E-R series cards would be a better choice. I don't know what OEMs have come up with in the SATA3 department since I wrote that list but the chips to look for in that case are the LSI MegaRAID 2004/2008/2016e depending on how many ports you want.

If you want to read a further discussion about reliability of different RAID setups I made a post about this in the following thread (last post):

http://communities.intel.com/thread/25945

The cost of the drives is marginally higher than the drives I had budgeted, but including the cost of an SAS HBA is problematic.  I hadn't expected purchasing an HBA from the very start.  I'd hoped to deffer such a purchase for a bit, but you are saying that would be ill-advised.  How likely is it I would encounter problems using SATA drives in the interim?

Have you seen any price/feature advantage to reseller versions of LSI OEM products?  I would think the offerings from Cisco, Dell, HP, and IBM would come at a premium as opposed to purchasing LSI branded hardware.  Anyway, I thought there might be specific models from particular manufacturers to meet the "best practices" for ZFS.  However, from your suggestions, I gather it really doesn't matter as long as the HBA is Intel or LSI?

I have seen discussions in support of file system level redundancy like that of ZFS, precisely for the reason you cited.  I guess I can add your link to the pro-FS pile of reference material.


I wonder, should we perhaps move the discussion of ZFS to private email?  It is a bit off-topic.
--------------050201090706010403010301-- --===============8504138819812557211== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users --===============8504138819812557211==-- From xen-users-bounces@lists.xen.org Thu Sep 27 01:36:10 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Thu, 27 Sep 2012 01:36:10 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TH30A-0001dL-Sw; Thu, 27 Sep 2012 01:34:54 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TH309-0001d8-42 for xen-users@lists.xen.org; Thu, 27 Sep 2012 01:34:53 +0000 Received: from [85.158.143.35:18250] by server-2.bemta-4.messagelabs.com id DA/2F-06610-C3DA3605; Thu, 27 Sep 2012 01:34:52 +0000 X-Env-Sender: shades_of_grey@earthlink.net X-Msg-Ref: server-2.tower-21.messagelabs.com!1348709688!9028574!1 X-Originating-IP: [209.86.89.63] X-SpamReason: No, hits=1.4 required=7.0 tests=BODY_RANDOM_LONG, HTML_20_30,HTML_MESSAGE,ML_RADAR_SPEW_LINKS_14,spamassassin: X-StarScan-Received: X-StarScan-Version: 6.6.1.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 31096 invoked from network); 27 Sep 2012 01:34:48 -0000 Received: from elasmtp-junco.atl.sa.earthlink.net (HELO elasmtp-junco.atl.sa.earthlink.net) (209.86.89.63) by server-2.tower-21.messagelabs.com with SMTP; 27 Sep 2012 01:34:48 -0000 DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=dk20050327; d=earthlink.net; b=hby+wuiXgje0kKGT76cxQYlX6NFrbZl6JUoaxzr/OseId39WtJrRrhzNGwvN8hKy; h=Received:Message-ID:Date:From:User-Agent:MIME-Version:To:Subject:References:In-Reply-To:Content-Type:X-ELNK-Trace:X-Originating-IP; Received: from [66.167.250.229] (helo=[192.168.1.13]) by elasmtp-junco.atl.sa.earthlink.net with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.67) (envelope-from ) id 1TH302-0005Va-Fo for xen-users@lists.xen.org; Wed, 26 Sep 2012 21:34:47 -0400 Message-ID: <5063AD2E.10800@earthlink.net> Date: Wed, 26 Sep 2012 21:34:38 -0400 From: ShadesOfGrey User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:15.0) Gecko/20120907 Thunderbird/15.0.1 MIME-Version: 1.0 To: xen-users@lists.xen.org References: <505B86AE.9040507@earthlink.net> <505C8630.2090002@student.chalmers.se> <505FD74E.2050405@earthlink.net> <506056BC.3010705@student.chalmers.se> In-Reply-To: <506056BC.3010705@student.chalmers.se> X-ELNK-Trace: 0fe7bc40aa99bc8fc963772e86942a7b94f5150ab1c16ac0485087bba56e60092323022b087e5a23eca0a53b1d256162350badd9bab72f9c350badd9bab72f9c X-Originating-IP: 66.167.250.229 Subject: Re: [Xen-users] Recommendations for Virtulization Hardware X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============8504138819812557211==" Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org This is a multi-part message in MIME format. --===============8504138819812557211== Content-Type: multipart/alternative; boundary="------------050201090706010403010301" This is a multi-part message in MIME format. --------------050201090706010403010301 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit On 09/24/2012 08:49 AM, Robin Axelsson wrote: > On 2012-09-24 05:45, ShadesOfGrey wrote: >> Sorry for the late response, I've had a lot to digest. >> The lack of current information about Xen (and KVM) online has been >> frustrating --- especially finding the many proof of concept videos >> that demonstrated possibilities but offered no real specifics. >> Looking for specifics, I sought information from gaming and >> enthusiast sites; I figured finding confirmation of VT-d and AMD-Vi >> support on such sites would be more likely. However, I found that >> wasn't often the case. I did determine that ASRock motherboards seem >> to be the most likely to support VT-d, ASUS least likely (unless >> equipped with an Intel 'sanctioned' VT-d chipset). I had narrowed my >> choices to two motherboards that appear to offer VT-d support and was >> intending to contact the manufacturer before purchase. Both choices >> are a bit pricey and I've been reconsidering whether I should look to >> other motherboards to reduce costs. > > Some motherboards support IOMMU even though it is not found in the > user manual or specified on the website. Your best bet is to ask > customer support. A guy posted here that he got it working on an Intel > motherboard that doesn't even have options for it in the BIOS, so it > seems that in some cases it is only up to the CPU. This is not the > case with AMD though as I stated before. I have bought a couple of > Gigabyte GA990FX-UD7 myself, they are stable and have a good layout. > They have support for IOMMU but I haven't tested it thoroughly enough > to fully confirm this although I don't believe there would be any > problem. > I'm aware of this. In fact, I only have anecdotal evidence that the Gigabyte G1.Sniper 3 has IOMMU (VT-d) support. I intend to query the manufacturers, seeking confirmation of IOMMU support, of every motherboard that ends up on my short list. I may include other Z77 motherboards from MSI and Gigabyte, since there is concrete evidence that the Z77 chipset does support IOMMU. I did focus, however, on those motherboards I had some inkling could support IOMMU. Now I'm trying to expand my selection process to include less expensive options. > It surprises me that ASRock and ASUS are so different. ASRock is, or > at least used to be a subsidiary of ASUS so there shouldn't be that > much difference between them. Same here. But I guess things changed after ASRock was spun-off. >> This is precisely the kind of information I was looking for from the >> threads I started on Ars Technica. It's just unfortunate that FLR and >> D3 D0 support aren't often found in the tech specs of must expansion >> hardware. However, now that I know what to ask, I'll try contacting >> hardware manufacturers prior to purchasing any expansion hardware. >> Thank you! > > D3 and D0 are power states defined for devices in the ACPI > specification and can be used to control the supply voltage (Vcc) to > PCI and PCIe devices. You can find more information about it here for > example: > > http://en.wikipedia.org/wiki/Advanced_Configuration_and_Power_Interface > > --------------- > > > Device states > > The device states /D0/-/D3/ are device-dependent: > > * *D0* /Fully On/ is the operating state. > * *D1* and *D2* are intermediate power-states whose definition > varies by device. > * *D3* /Off/ has the device powered off and unresponsive to its bus. > > --------------- > > So, either it works for a certain type of hardware or it doesn't and I > wouldn't expect a vendor to state this "support" in the specifications > since it isn't a "feature" in and of itself if you get me. But maybe > this will change and maybe FLR support will become more widespread. I did read that Wikipedia entry after your referenced excerpt. To my mind, if a manufacturer claims support for the ACPI or PCIe spec and doesn't implement certain portions of those specs(some are optional after all), said manufacturer has an obligation to make that clear to your customers and users. But then, that's just me. Anyway, this information gives me what I need to ask the right questions of tech support before purchasing. >> From everything I've read, solutions that rely on any form of remote >> display protocols would be limited to a subset of Direct3D functions. >> Furthermore, these would vary from one implementation to another, >> thus making them far less attractive for gaming than VGA >> passthrough... Well, in my opinion anyway. >> >> VirtualBox's seamless mode is pretty nifty. But it's a Type 2 >> Hypervisor and relies on paravirtualized drivers that also suffer >> from the same limitations as remote display protocols. It's great for >> most things, but gaming is not one of them. And I'm speaking from >> personal experience. Though I haven't used them myself, the same >> would seem to hold true of Parallel's and VMWare's 'Workstation' >> offerings. At least, as far as I've gathered. >> >> FYI, the Type 1 Hypervisors from Parallel's and VMWare* are priced >> waaayyy outside my budget. >> > I understand that you want full 3D functionality for Windows gaming > but maybe you'll find the subset of 3D functionality for the Linux > machine acceptable. I have looked into VirtualGL and with TurboVNC, > you might get a pretty decent desktop environment and it seems like > most of the features are there already. It appears that the 3D is > rendered by hardware/GPU before it is streamed through VNC or Spice. > So it seems that you would need another GPU for that. You can find > more info on VirtualGL here: > > http://www.virtualgl.org/ Upon further investigation, the only option that is available to remotely translate Windows 3D apps is Microsoft's own RemoteFX. In which case, Microsoft products would be the foundation of my software stack... Something I'm trying to avoid. > > Also the line between a type 1 and type 2 hypervisor tend to get a bit > blurry. The point with type 1 is that it has access to ring-0 so that > it can get access directly to the hardware to be passed through to the > guests (I did confuse 'host' and 'guest' in my prior post). It also > doesn't need to ask the host OS for permission in the same way as a > type 2 hypervisor which is likely to give performance advantages in > some cases. > > However, even a type 2 hypervisor, although it is run as an > application inside the OS can get "type 1" like privileges. By > patching into the kernel and/or using special "dummy drivers" for > hardware to be shared with VMs you can achieve pretty much the same > thing, ergo it is no longer clear whether the hypervisor is a type 1 > or type 2. > > There is an article about it from the old IBM Mainframe days but I > can't seem to find it. > You might be right, the performance of a Type 2 Hypervisor may be sufficient. Regardless, I'd still have roughly the same hardware requirements as if I were going to use a Type 1 Hypervisor. I'd still need the same CPU, RAM, GPU, and storage requirements as I've already put forth. I could omit the potentially necessary additional components for use with a Type 1 Hypervisor. Things like USB controller, NIC, or sound card. But those costs would be replaced with the cost of licensing the Type2 Hypervisor. In which case, I don't really gain or lose anything by experimenting with Type 1 Hypervisors... At any rate, I could compare and contrast the performance of Type 1 and Type 2 Hypervisors using Paralles' and VMWare's trialware. It might take a good long while, but it would be an adventure. >> >> *I only found out about VMWare's 'free' vSphere after I'd written >> this response. >> >>> Also, it is highly recommended that you use ECC RAM for such >>> applications and it doesn't hurt to dedicate a few gigs of it to the >>> ZFS as RAM is used for cache. The good news is that most >>> motherboards with good chipsets support ECC RAM even though you >>> might not find anything about it in the user manuals. >> Again, thanks for the thorough explanation. This gives me a great >> deal to think about. The more I learn about ZFS, the less appealing >> it becomes. And by that I mean the confusion over which version of >> ZFS is in what OS? And just how well maintained the OSes supporting >> ZFS are? Now I have additional hardware considerations to keep in >> mind that may (or may not) make the cost of ZFS RAID-Z pool >> comparable to a hardware RAID5/6 solution anyway. Do you have any >> suggestions as to which of LSI HBAs I should be considering? I >> haven't found an HCL for ZFS in my searches. >> >> Out of curiosity --- and if you would happen to know --- do you think >> what you suggest about the HBA and SAS drives for ZFS also applies to >> Btrfs? I'm assuming it would, but I'd appreciate some confirmation. >> >> It's funny how the "I" in RAID never really seems to apply... >> Especially since it looks more and more like using ZFS or Btrfs will >> require I commit myself, from the start, to one or the other and a >> discrete HBA. Transitioning from an integrated SATA controller(s) and >> mdadm seems rather impractical. If I understand what's involved in >> doing so correctly. It may turn out that anything other than mdadm is >> price prohibitive. >> > > I don't think you will have a problem with getting ZFS to run and if > that's your only goal then you don't need to be very picky with your > choice of hardware. I find ZFS pretty easy and handy to use. I has > really great functionality and I don't have many bad things to say > about it so far. ZFS is a filesystem (along with a couple of software > tools to administrate it) just like EXT4 or NTFS so hardware support > depends on the platform it runs on. > > But the point with using ZFS is to get maximum protection against data > corruption and that's where the selection of hardware gets limited and > there are "best practices" set up to achieve that. I have not tested > ZFS on any other platform than on OpenSolaris and OpenIndiana but I do > know that it is well implemented on that platform and more mature > there than on any other (non-solaris) platform. Another advantage with > the OSOL/OI platform is that the CIFS functionality is implemented in > the kernel space and not in the userland which will give advantages > performance wise if you intend to share files with other windows > computers. (I don't deny that Samba is pretty good on Linux too. There > are some benchmarks on the phoronix website comparing samba with NFS > and they are in favor of Samba on those benchmarks...) The second best > implementation is found with FreeBSD and it is probably fairly mature > but I haven't tested it myself and some people have run into problems > with it in the past. The Linux version is probably merely at infancy > stage and likely not yet mature enough for regular use. It is probably > not as "bad" as btrfs though. There is quite a bit of information > about it on the phoronix.com website (and probably also at lwn.net): > > http://www.phoronix.com/scan.php?page=news_item&px=MTE4Nzc > My goal wasn't just to experiment with Btrfs, mdamd, or ZFS, if that's what you meant by, "with getting ZFS to run and if that's your only goal". I actually intend to use it 'in production'. In fact, the secondary role (Linux desktop being primary) for my proposed Virtualization rig is as file server (incl. httpd). Windows gaming is a tertiary or quaternary concern for me. So, finding out that the "best practices" for implementing ZFS include hardware I hadn't anticipated, is a bit off-putting. The diversity in ZFS implementations is what I meant about being confused. I'm not as familiar with the underlying platforms that utilize ZFS (other than Linux, and not with ZFS in use). Without that familiarity, it makes it more difficult to gauge which of those platforms would suit my purposes. For example, I had read a little bit about the degraded CIFS performance on FreeBSD and Linux due to their reliance on Samba (it residing in user-space being the issue). BTW, I meant to ask how you came to the conclusion that ECC RAM is supported on desktop motherboards? It's always been my understanding that you could use ECC RAM on such hardware, but there was no added benefit. > A search there on ZFS will give more articles. The latest official > version of ZFS is 28 and is probably implemented in both Linux, and > FreeBSD by now. Later versions have been released since Oracle killed > the OpenSolaris project and can be found with the commercial > closed-source Solaris platform that is supplied by Oracle. Things have > happened since Oracle pulled the plug on OSOL project and leading > developers behind the ZFS project such as Jeff Bonwick left Sun (after > the acquisition by Oracle) and joined up with the Illumos team > instead. So you cannot determine the stability of ZFS and ZPOOL merely > by looking into the version number unfortunately and I wouldn't expect > the FreeBSD implementation to be as stable as the Solaris > implementation. It just takes time for the implementation to mature > and the bugs to be weeded out and it just happens to have been around > for Solaris/OpenSolaris/Illumos for much longer than the other > platforms and the Solaris/Illumos version also happens to get first > dibs on the features. Among the Illumos people there is an ambition to > drop the version numbering altogether and instead talk about available > features. > One of the two ZFS implementations on Linux has reached version 28, the other is at version 23 and seems to be abandoned or stagnant (last release was May 2011). I'm not quite sure what the status of ZFS on FreeBSD is. From this table on Wikipedia, ZFS is at version 28. However the table notes that there is no CIFS or iSCSI support, which I'll try to independently confirm. And, as you say, the fact that ZFS (and Solaris as a whole) has essentially been forked, with the re-consolidation of Solaris as closed-source, just adds to the confusion. It's possible any given build of Illumos' version 28 of ZFS could have features or bug fixes no present in Oracle's version 33. > The recommendation to use SAS hard drives is not so much about the > quality of the hard drives themselves as it is about the SAS protocol. > The SAS protocol simply handles SCSI transport commands in a better > and more reliable manner than do SATA. I believe any decent SAS drive > would do. As for HBAs I wrote a list with LSI based hardware a while > ago here: > > https://www.illumos.org/boards/1/topics/572 > > the thing is that a lot of OEMs such as IBM, HP, Cisco, > Fujitsu-Siemens, Dell, ... supply their branded HBAs with LSI > circuitry on them. What hardware to choose depends on what you're > looking for. If you want an 8-port controller I would go for Intel > SASUC8I or LSI SAS3801E-R. If you want SAS/SATA3 with 6.0 Gb/s then > LSI's LSI SAS3801E-R series cards would be a better choice. I don't > know what OEMs have come up with in the SATA3 department since I wrote > that list but the chips to look for in that case are the LSI MegaRAID > 2004/2008/2016e depending on how many ports you want. > > If you want to read a further discussion about reliability of > different RAID setups I made a post about this in the following thread > (last post): > > http://communities.intel.com/thread/25945 > The cost of the drives is marginally higher than the drives I had budgeted, but including the cost of an SAS HBA is problematic. I hadn't expected purchasing an HBA from the very start. I'd hoped to deffer such a purchase for a bit, but you are saying that would be ill-advised. How likely is it I would encounter problems using SATA drives in the interim? Have you seen any price/feature advantage to reseller versions of LSI OEM products? I would think the offerings from Cisco, Dell, HP, and IBM would come at a premium as opposed to purchasing LSI branded hardware. Anyway, I thought there might be specific models from particular manufacturers to meet the "best practices" for ZFS. However, from your suggestions, I gather it really doesn't matter as long as the HBA is Intel or LSI? I have seen discussions in support of file system level redundancy like that of ZFS, precisely for the reason you cited. I guess I can add your link to the pro-FS pile of reference material. I wonder, should we perhaps move the discussion of ZFS to private email? It is a bit off-topic. --------------050201090706010403010301 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Re: [Xen-users] Recommendations for Virtulization Hardware
On 09/24/2012 08:49 AM, Robin Axelsson wrote:
On 2012-09-24 05:45, ShadesOfGrey wrote:
Sorry for the late response, I've had a lot to digest.
<snip>
The lack of current information about Xen (and KVM) online has been frustrating — especially finding the many proof of concept videos that demonstrated possibilities but offered no real specifics. Looking for specifics, I sought information from gaming and enthusiast sites; I figured finding confirmation of VT-d and AMD-Vi support on such sites would be more likely. However, I found that wasn't often the case. I did determine that ASRock motherboards seem to be the most likely to support VT-d, ASUS least likely (unless equipped with an Intel 'sanctioned' VT-d chipset). I had narrowed my choices to two motherboards that appear to offer VT-d support and was intending to contact the manufacturer before purchase. Both choices are a bit pricey and I've been reconsidering whether I should look to other motherboards to reduce costs.

Some motherboards support IOMMU even though it is not found in the user manual or specified on the website. Your best bet is to ask customer support. A guy posted here that he got it working on an Intel motherboard that doesn't even have options for it in the BIOS, so it seems that in some cases it is only up to the CPU. This is not the case with AMD though as I stated before. I have bought a couple of Gigabyte GA990FX-UD7 myself, they are stable and have a good layout. They have support for IOMMU but I haven't tested it thoroughly enough to fully confirm this although I don't believe there would be any problem.

I'm aware of this.  In fact, I only have anecdotal evidence that the Gigabyte G1.Sniper 3 has IOMMU (VT-d) support.  I intend to query the manufacturers, seeking confirmation of IOMMU support, of every motherboard that ends up on my short list.  I may include other Z77 motherboards from MSI and Gigabyte, since there is concrete evidence that the Z77 chipset does support IOMMU.  I did focus, however, on those motherboards I had some inkling could support IOMMU.  Now I'm trying to expand my selection process to include less expensive options.
It surprises me that ASRock and ASUS are so different. ASRock is, or at least used to be a subsidiary of ASUS so there shouldn't be that much difference between them.
Same here.  But I guess things changed after ASRock was spun-off.

<snip>
This is precisely the kind of information I was looking for from the threads I started on Ars Technica. It's just unfortunate that FLR and D3 D0 support aren't often found in the tech specs of must expansion hardware. However, now that I know what to ask, I'll try contacting hardware manufacturers prior to purchasing any expansion hardware. Thank you!

D3 and D0 are power states defined for devices in the ACPI specification and can be used to control the supply voltage (Vcc) to PCI and PCIe devices. You can find more information about it here for example:

http://en.wikipedia.org/wiki/Advanced_Configuration_and_Power_Interface

---------------

Device states

The device states D0-D3 are device-dependent:

  • D0 Fully On is the operating state.
  • D1 and D2 are intermediate power-states whose definition varies by device.
  • D3 Off has the device powered off and unresponsive to its bus.
---------------

So, either it works for a certain type of hardware or it doesn't and I wouldn't expect a vendor to state this "support" in the specifications since it isn't a "feature" in and of itself if you get me. But maybe this will change and maybe FLR support will become more widespread.
I did read that Wikipedia entry after your referenced excerpt.  To my mind, if a manufacturer claims support for the ACPI or PCIe spec and doesn't implement certain portions of those specs(some are optional after all), said manufacturer has an obligation to make that clear to your customers and users.  But then, that's just me.  Anyway, this information gives me what I need to ask the right questions of tech support before purchasing.

<snip>
From everything I've read, solutions that rely on any form of remote display protocols would be limited to a subset of Direct3D functions. Furthermore, these would vary from one implementation to another, thus making them far less attractive for gaming than VGA passthrough... Well, in my opinion anyway.

VirtualBox's seamless mode is pretty nifty. But it's a Type 2 Hypervisor and relies on paravirtualized drivers that also suffer from the same limitations as remote display protocols. It's great for most things, but gaming is not one of them. And I'm speaking from personal experience. Though I haven't used them myself, the same would seem to hold true of Parallel's and VMWare's 'Workstation' offerings. At least, as far as I've gathered.

FYI, the Type 1 Hypervisors from Parallel's and VMWare* are priced waaayyy outside my budget.

I understand that you want full 3D functionality for Windows gaming but maybe you'll find the subset of 3D functionality for the Linux machine acceptable. I have looked into VirtualGL and with TurboVNC, you might get a pretty decent desktop environment and it seems like most of the features are there already. It appears that the 3D is rendered by hardware/GPU before it is streamed through VNC or Spice. So it seems that you would need another GPU for that. You can find more info on VirtualGL here:

http://www.virtualgl.org/
Upon further investigation, the only option that is available to remotely translate Windows 3D apps is Microsoft's own RemoteFX.  In which case, Microsoft products would be the foundation of my software stack...  Something I'm trying to avoid.

Also the line between a type 1 and type 2 hypervisor tend to get a bit blurry. The point with type 1 is that it has access to ring-0 so that it can get access directly to the hardware to be passed through to the guests (I did confuse 'host' and 'guest' in my prior post). It also doesn't need to ask the host OS for permission in the same way as a type 2 hypervisor which is likely to give performance advantages in some cases.

However, even a type 2 hypervisor, although it is run as an application inside the OS can get "type 1" like privileges. By patching into the kernel and/or using special "dummy drivers" for hardware to be shared with VMs you can achieve pretty much the same thing, ergo it is no longer clear whether the hypervisor is a type 1 or type 2.

There is an article about it from the old IBM Mainframe days but I can't seem to find it.

You might be right, the performance of a Type 2 Hypervisor may be sufficient.  Regardless, I'd still have roughly the same hardware requirements as if I were going to use a Type 1 Hypervisor.  I'd still need the same CPU, RAM, GPU, and storage requirements as I've already put forth.  I could omit the potentially necessary additional components for use with a Type 1 Hypervisor.  Things like USB controller, NIC, or sound card.  But those costs would be replaced with the cost of licensing the Type2 Hypervisor.

In which case, I don't really gain or lose anything by experimenting with Type 1 Hypervisors...  At any rate, I could compare and contrast the performance of Type 1 and Type 2 Hypervisors using Paralles' and VMWare's trialware.  It might take a good long while, but it would be an adventure.

*I only found out about VMWare's 'free' vSphere after I'd written this response.

<snip>
Also, it is highly recommended that you use ECC RAM for such applications and it doesn't hurt to dedicate a few gigs of it to the ZFS as RAM is used for cache. The good news is that most motherboards with good chipsets support ECC RAM even though you might not find anything about it in the user manuals.
Again, thanks for the thorough explanation. This gives me a great deal to think about. The more I learn about ZFS, the less appealing it becomes. And by that I mean the confusion over which version of ZFS is in what OS? And just how well maintained the OSes supporting ZFS are? Now I have additional hardware considerations to keep in mind that may (or may not) make the cost of ZFS RAID-Z pool comparable to a hardware RAID5/6 solution anyway. Do you have any suggestions as to which of LSI HBAs I should be considering? I haven't found an HCL for ZFS in my searches.

Out of curiosity — and if you would happen to know — do you think what you suggest about the HBA and SAS drives for ZFS also applies to Btrfs? I'm assuming it would, but I'd appreciate some confirmation.

It's funny how the "I" in RAID never really seems to apply... Especially since it looks more and more like using ZFS or Btrfs will require I commit myself, from the start, to one or the other and a discrete HBA. Transitioning from an integrated SATA controller(s) and mdadm seems rather impractical. If I understand what's involved in doing so correctly. It may turn out that anything other than mdadm is price prohibitive.


I don't think you will have a problem with getting ZFS to run and if that's your only goal then you don't need to be very picky with your choice of hardware. I find ZFS pretty easy and handy to use. I has really great functionality and I don't have many bad things to say about it so far. ZFS is a filesystem (along with a couple of software tools to administrate it) just like EXT4 or NTFS so hardware support depends on the platform it runs on.

But the point with using ZFS is to get maximum protection against data corruption and that's where the selection of hardware gets limited and there are "best practices" set up to achieve that. I have not tested ZFS on any other platform than on OpenSolaris and OpenIndiana but I do know that it is well implemented on that platform and more mature there than on any other (non-solaris) platform. Another advantage with the OSOL/OI platform is that the CIFS functionality is implemented in the kernel space and not in the userland which will give advantages performance wise if you intend to share files with other windows computers. (I don't deny that Samba is pretty good on Linux too. There are some benchmarks on the phoronix website comparing samba with NFS and they are in favor of Samba on those benchmarks...) The second best implementation is found with FreeBSD and it is probably fairly mature but I haven't tested it myself and some people have run into problems with it in the past. The Linux version is probably merely at infancy stage and likely not yet mature enough for regular use. It is probably not as "bad" as btrfs though. There is quite a bit of information about it on the phoronix.com website (and probably also at lwn.net):

http://www.phoronix.com/scan.php?page=news_item&px=MTE4Nzc

My goal wasn't just to experiment with Btrfs, mdamd, or ZFS, if that's what you meant by, "with getting ZFS to run and if that's your only goal".  I actually intend to use it 'in production'.  In fact, the secondary role (Linux desktop being primary) for my proposed Virtualization rig is as file server (incl. httpd).  Windows gaming is a tertiary or quaternary concern for me.  So, finding out that the "best practices" for implementing ZFS include hardware I hadn't anticipated, is a bit off-putting.

The diversity in ZFS implementations is what I meant about being confused.  I'm not as familiar with the underlying platforms that utilize ZFS (other than Linux, and not with ZFS in use).  Without that familiarity, it makes it more difficult to gauge which of those platforms would suit my purposes.  For example, I had read a little bit about the degraded CIFS performance on FreeBSD and Linux due to their reliance on Samba (it residing in user-space being the issue).

BTW, I meant to ask how you came to the conclusion that ECC RAM is supported on desktop motherboards?  It's always been my understanding that you could use ECC RAM on such hardware, but there was no added benefit.
A search there on ZFS will give more articles. The latest official version of ZFS is 28 and is probably implemented in both Linux, and FreeBSD by now. Later versions have been released since Oracle killed the OpenSolaris project and can be found with the commercial closed-source Solaris platform that is supplied by Oracle. Things have happened since Oracle pulled the plug on OSOL project and leading developers behind the ZFS project such as Jeff Bonwick left Sun (after the acquisition by Oracle) and joined up with the Illumos team instead. So you cannot determine the stability of ZFS and ZPOOL merely by looking into the version number unfortunately and I wouldn't expect the FreeBSD implementation to be as stable as the Solaris implementation. It just takes time for the implementation to mature and the bugs to be weeded out and it just happens to have been around for Solaris/OpenSolaris/Illumos for much longer than the other platforms and the Solaris/Illumos version also happens to get first dibs on the features. Among the Illumos people there is an ambition to drop the version numbering altogether and instead talk about available features.

One of the two ZFS implementations on Linux has reached version 28, the other is at version 23 and seems to be abandoned or stagnant (last release was May 2011).  I'm not quite sure what the status of ZFS on FreeBSD is.  From this table on Wikipedia, ZFS is at version 28.  However the table notes that there is no CIFS or iSCSI support, which I'll try to independently confirm.  And, as you say, the fact that ZFS (and Solaris as a whole) has essentially been forked, with the re-consolidation of Solaris as closed-source, just adds to the confusion.  It's possible any given build of Illumos' version 28 of ZFS could have features or bug fixes no present in Oracle's version 33.
The recommendation to use SAS hard drives is not so much about the quality of the hard drives themselves as it is about the SAS protocol. The SAS protocol simply handles SCSI transport commands in a better and more reliable manner than do SATA. I believe any decent SAS drive would do. As for HBAs I wrote a list with LSI based hardware a while ago here:

https://www.illumos.org/boards/1/topics/572

the thing is that a lot of OEMs such as IBM, HP, Cisco, Fujitsu-Siemens, Dell, ... supply their branded HBAs with LSI circuitry on them. What hardware to choose depends on what you're looking for. If you want an 8-port controller I would go for Intel SASUC8I or LSI SAS3801E-R. If you want SAS/SATA3 with 6.0 Gb/s then LSI's LSI SAS3801E-R series cards would be a better choice. I don't know what OEMs have come up with in the SATA3 department since I wrote that list but the chips to look for in that case are the LSI MegaRAID 2004/2008/2016e depending on how many ports you want.

If you want to read a further discussion about reliability of different RAID setups I made a post about this in the following thread (last post):

http://communities.intel.com/thread/25945

The cost of the drives is marginally higher than the drives I had budgeted, but including the cost of an SAS HBA is problematic.  I hadn't expected purchasing an HBA from the very start.  I'd hoped to deffer such a purchase for a bit, but you are saying that would be ill-advised.  How likely is it I would encounter problems using SATA drives in the interim?

Have you seen any price/feature advantage to reseller versions of LSI OEM products?  I would think the offerings from Cisco, Dell, HP, and IBM would come at a premium as opposed to purchasing LSI branded hardware.  Anyway, I thought there might be specific models from particular manufacturers to meet the "best practices" for ZFS.  However, from your suggestions, I gather it really doesn't matter as long as the HBA is Intel or LSI?

I have seen discussions in support of file system level redundancy like that of ZFS, precisely for the reason you cited.  I guess I can add your link to the pro-FS pile of reference material.


I wonder, should we perhaps move the discussion of ZFS to private email?  It is a bit off-topic.
--------------050201090706010403010301-- --===============8504138819812557211== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users --===============8504138819812557211==-- From xen-users-bounces@lists.xen.org Thu Sep 27 01:58:31 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Thu, 27 Sep 2012 01:58:31 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TH3Lz-0002AW-5v; Thu, 27 Sep 2012 01:57:27 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TH3Lx-0002AR-1x for xen-users@lists.xen.org; Thu, 27 Sep 2012 01:57:25 +0000 Received: from [85.158.143.35:48222] by server-1.bemta-4.messagelabs.com id D0/81-05684-482B3605; Thu, 27 Sep 2012 01:57:24 +0000 X-Env-Sender: robert@digitalsilk.net X-Msg-Ref: server-2.tower-21.messagelabs.com!1348711042!9030020!1 X-Originating-IP: [208.157.175.245] X-SpamReason: No, hits=0.0 required=7.0 tests= X-StarScan-Received: X-StarScan-Version: 6.6.1.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 5534 invoked from network); 27 Sep 2012 01:57:23 -0000 Received: from bal-bb-static3-cisco-ws-20.dsl.airstreamcomm.net (HELO bilbo.digitalsilk.net) (208.157.175.245) by server-2.tower-21.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 27 Sep 2012 01:57:23 -0000 Received: by bilbo.digitalsilk.net (Postfix, from userid 1001) id 0C2793002D; Wed, 26 Sep 2012 20:57:20 -0500 (CDT) X-Spam-Checker-Version: SpamAssassin 3.3.2 (2011-06-06) on bilbo X-Spam-Status: No, hits=-1.0 required=3.0 tests=ALL_TRUSTED X-Spam-Level: Received: from bunsen.digitalsilk.lan (link.digitalsilk.lan [192.168.2.254]) by bilbo.digitalsilk.net (Postfix) with ESMTP id B758B3002C for ; Wed, 26 Sep 2012 20:57:19 -0500 (CDT) Message-ID: <5063B281.7020801@digitalsilk.net> Date: Wed, 26 Sep 2012 20:57:21 -0500 From: Robert Rust User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:15.0) Gecko/20120907 Thunderbird/15.0.1 MIME-Version: 1.0 To: xen-users@lists.xen.org References: <505B86AE.9040507@earthlink.net> <505C8630.2090002@student.chalmers.se> <505FD74E.2050405@earthlink.net> <506056BC.3010705@student.chalmers.se> <5063AD2E.10800@earthlink.net> In-Reply-To: <5063AD2E.10800@earthlink.net> Subject: Re: [Xen-users] Recommendations for Virtulization Hardware X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset="windows-1252"; Format="flowed" Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org On 9/26/12 8:34 PM, ShadesOfGrey wrote: > On 09/24/2012 08:49 AM, Robin Axelsson wrote: >> On 2012-09-24 05:45, ShadesOfGrey wrote: >>> Sorry for the late response, I've had a lot to digest. > >>> The lack of current information about Xen (and KVM) online has been >>> frustrating =97 especially finding the many proof of concept videos >>> that demonstrated possibilities but offered no real specifics. >>> Looking for specifics, I sought information from gaming and >>> enthusiast sites; I figured finding confirmation of VT-d and AMD-Vi >>> support on such sites would be more likely. However, I found that >>> wasn't often the case. I did determine that ASRock motherboards seem >>> to be the most likely to support VT-d, ASUS least likely (unless >>> equipped with an Intel 'sanctioned' VT-d chipset). I had narrowed my >>> choices to two motherboards that appear to offer VT-d support and was >>> intending to contact the manufacturer before purchase. Both choices >>> are a bit pricey and I've been reconsidering whether I should look to >>> other motherboards to reduce costs. >> >> Some motherboards support IOMMU even though it is not found in the >> user manual or specified on the website. Your best bet is to ask >> customer support. A guy posted here that he got it working on an Intel >> motherboard that doesn't even have options for it in the BIOS, so it >> seems that in some cases it is only up to the CPU. This is not the >> case with AMD though as I stated before. I have bought a couple of >> Gigabyte GA990FX-UD7 myself, they are stable and have a good layout. >> They have support for IOMMU but I haven't tested it thoroughly enough >> to fully confirm this although I don't believe there would be any >> problem. >> > I'm aware of this. In fact, I only have anecdotal evidence that the > Gigabyte G1.Sniper 3 has IOMMU (VT-d) support. I intend to query the > manufacturers, seeking confirmation of IOMMU support, of every > motherboard that ends up on my short list. I may include other Z77 > motherboards from MSI and Gigabyte, since there is concrete evidence > that the Z77 chipset does support IOMMU. I did focus, however, on those > motherboards I had some inkling could support IOMMU. Now I'm trying to > expand my selection process to include less expensive options. I have a Gigabyte GA-Z77-DS3H, which I can confirm does support IOMMU = ... I'm passing PCI video tuner cards to two different DomUs and a = PCI-Express 1x USB card to another DomU. I also have an Intel DH77KC that does IOMMU but the H77 chipset support = was (is?) buggy in the current mainstream kernel releases so it's still = in the box on the shelf. -Robert _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Thu Sep 27 01:58:31 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Thu, 27 Sep 2012 01:58:31 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TH3Lz-0002AW-5v; Thu, 27 Sep 2012 01:57:27 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TH3Lx-0002AR-1x for xen-users@lists.xen.org; Thu, 27 Sep 2012 01:57:25 +0000 Received: from [85.158.143.35:48222] by server-1.bemta-4.messagelabs.com id D0/81-05684-482B3605; Thu, 27 Sep 2012 01:57:24 +0000 X-Env-Sender: robert@digitalsilk.net X-Msg-Ref: server-2.tower-21.messagelabs.com!1348711042!9030020!1 X-Originating-IP: [208.157.175.245] X-SpamReason: No, hits=0.0 required=7.0 tests= X-StarScan-Received: X-StarScan-Version: 6.6.1.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 5534 invoked from network); 27 Sep 2012 01:57:23 -0000 Received: from bal-bb-static3-cisco-ws-20.dsl.airstreamcomm.net (HELO bilbo.digitalsilk.net) (208.157.175.245) by server-2.tower-21.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 27 Sep 2012 01:57:23 -0000 Received: by bilbo.digitalsilk.net (Postfix, from userid 1001) id 0C2793002D; Wed, 26 Sep 2012 20:57:20 -0500 (CDT) X-Spam-Checker-Version: SpamAssassin 3.3.2 (2011-06-06) on bilbo X-Spam-Status: No, hits=-1.0 required=3.0 tests=ALL_TRUSTED X-Spam-Level: Received: from bunsen.digitalsilk.lan (link.digitalsilk.lan [192.168.2.254]) by bilbo.digitalsilk.net (Postfix) with ESMTP id B758B3002C for ; Wed, 26 Sep 2012 20:57:19 -0500 (CDT) Message-ID: <5063B281.7020801@digitalsilk.net> Date: Wed, 26 Sep 2012 20:57:21 -0500 From: Robert Rust User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:15.0) Gecko/20120907 Thunderbird/15.0.1 MIME-Version: 1.0 To: xen-users@lists.xen.org References: <505B86AE.9040507@earthlink.net> <505C8630.2090002@student.chalmers.se> <505FD74E.2050405@earthlink.net> <506056BC.3010705@student.chalmers.se> <5063AD2E.10800@earthlink.net> In-Reply-To: <5063AD2E.10800@earthlink.net> Subject: Re: [Xen-users] Recommendations for Virtulization Hardware X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset="windows-1252"; Format="flowed" Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org On 9/26/12 8:34 PM, ShadesOfGrey wrote: > On 09/24/2012 08:49 AM, Robin Axelsson wrote: >> On 2012-09-24 05:45, ShadesOfGrey wrote: >>> Sorry for the late response, I've had a lot to digest. > >>> The lack of current information about Xen (and KVM) online has been >>> frustrating =97 especially finding the many proof of concept videos >>> that demonstrated possibilities but offered no real specifics. >>> Looking for specifics, I sought information from gaming and >>> enthusiast sites; I figured finding confirmation of VT-d and AMD-Vi >>> support on such sites would be more likely. However, I found that >>> wasn't often the case. I did determine that ASRock motherboards seem >>> to be the most likely to support VT-d, ASUS least likely (unless >>> equipped with an Intel 'sanctioned' VT-d chipset). I had narrowed my >>> choices to two motherboards that appear to offer VT-d support and was >>> intending to contact the manufacturer before purchase. Both choices >>> are a bit pricey and I've been reconsidering whether I should look to >>> other motherboards to reduce costs. >> >> Some motherboards support IOMMU even though it is not found in the >> user manual or specified on the website. Your best bet is to ask >> customer support. A guy posted here that he got it working on an Intel >> motherboard that doesn't even have options for it in the BIOS, so it >> seems that in some cases it is only up to the CPU. This is not the >> case with AMD though as I stated before. I have bought a couple of >> Gigabyte GA990FX-UD7 myself, they are stable and have a good layout. >> They have support for IOMMU but I haven't tested it thoroughly enough >> to fully confirm this although I don't believe there would be any >> problem. >> > I'm aware of this. In fact, I only have anecdotal evidence that the > Gigabyte G1.Sniper 3 has IOMMU (VT-d) support. I intend to query the > manufacturers, seeking confirmation of IOMMU support, of every > motherboard that ends up on my short list. I may include other Z77 > motherboards from MSI and Gigabyte, since there is concrete evidence > that the Z77 chipset does support IOMMU. I did focus, however, on those > motherboards I had some inkling could support IOMMU. Now I'm trying to > expand my selection process to include less expensive options. I have a Gigabyte GA-Z77-DS3H, which I can confirm does support IOMMU = ... I'm passing PCI video tuner cards to two different DomUs and a = PCI-Express 1x USB card to another DomU. I also have an Intel DH77KC that does IOMMU but the H77 chipset support = was (is?) buggy in the current mainstream kernel releases so it's still = in the box on the shelf. -Robert _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Thu Sep 27 07:03:07 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Thu, 27 Sep 2012 07:03:07 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TH86V-0005mU-Bs; Thu, 27 Sep 2012 07:01:47 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TH86T-0005lG-NM for xen-users@lists.xen.org; Thu, 27 Sep 2012 07:01:45 +0000 Received: from [85.158.139.211:24258] by server-4.bemta-5.messagelabs.com id 2C/F6-20767-8D9F3605; Thu, 27 Sep 2012 07:01:44 +0000 X-Env-Sender: lists+xen@internecto.net X-Msg-Ref: server-7.tower-206.messagelabs.com!1348729304!19671808!1 X-Originating-IP: [176.9.245.29] X-SpamReason: No, hits=0.0 required=7.0 tests= X-StarScan-Received: X-StarScan-Version: 6.6.1.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 24880 invoked from network); 27 Sep 2012 07:01:44 -0000 Received: from polaris.internecto.net (HELO mx1.internecto.net) (176.9.245.29) by server-7.tower-206.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 27 Sep 2012 07:01:44 -0000 Received: from localhost (localhost [127.0.0.1]) by mx1.internecto.net (Postfix) with ESMTP id 202CFA0161 for ; Thu, 27 Sep 2012 07:01:44 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at mail.internecto.net Received: from mx1.internecto.net ([127.0.0.1]) by localhost (mail.polaris.internecto.net [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id wAlns6snzVk8 for ; Thu, 27 Sep 2012 07:01:43 +0000 (UTC) Received: from internecto.net (5ED4FDEB.cm-7-5d.dynamic.ziggo.nl [94.212.253.235]) (using TLSv1 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (Client did not present a certificate) (Authenticated sender: lists@internecto.net) by mx1.internecto.net (Postfix) with ESMTPSA id 309E6A0058 for ; Thu, 27 Sep 2012 07:01:43 +0000 (UTC) Date: Thu, 27 Sep 2012 09:01:41 +0200 From: Mark van Dijk To: xen-users@lists.xen.org Message-ID: <20120927090141.450c69e5@internecto.net> In-Reply-To: References: Organization: Internecto SIS X-Mailer: Claws Mail 3.8.0 (GTK+ 2.24.10; i686-pc-linux-gnu) Mime-Version: 1.0 Subject: Re: [Xen-users] sparse to no sparse X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org Quoting Fajar A. Nugraha's message from 27 sep 2012: >On Thu, Sep 27, 2012 at 5:43 AM, Paras pradhan > wrote: >> Hi. >> >> I have an old Xen para virt vm which I created using sparse file. Is >> there any way to convert this vm image to non-sparse without shutting >> down the vm?. > >No. > Can't you fill it up with zeros and then delete the file? i.e. on the domu, dd if=/dev/zero of=null.tmp; rm null.tmp. -- Stay in touch, Mark van Dijk. ,------------------------------------ -------------------------------' Thu Sep 27 07:00 UTC 2012 Today is Setting Orange, the 51st day of Bureaucracy in the YOLD 3178 _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Thu Sep 27 07:03:07 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Thu, 27 Sep 2012 07:03:07 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TH86V-0005mU-Bs; Thu, 27 Sep 2012 07:01:47 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TH86T-0005lG-NM for xen-users@lists.xen.org; Thu, 27 Sep 2012 07:01:45 +0000 Received: from [85.158.139.211:24258] by server-4.bemta-5.messagelabs.com id 2C/F6-20767-8D9F3605; Thu, 27 Sep 2012 07:01:44 +0000 X-Env-Sender: lists+xen@internecto.net X-Msg-Ref: server-7.tower-206.messagelabs.com!1348729304!19671808!1 X-Originating-IP: [176.9.245.29] X-SpamReason: No, hits=0.0 required=7.0 tests= X-StarScan-Received: X-StarScan-Version: 6.6.1.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 24880 invoked from network); 27 Sep 2012 07:01:44 -0000 Received: from polaris.internecto.net (HELO mx1.internecto.net) (176.9.245.29) by server-7.tower-206.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 27 Sep 2012 07:01:44 -0000 Received: from localhost (localhost [127.0.0.1]) by mx1.internecto.net (Postfix) with ESMTP id 202CFA0161 for ; Thu, 27 Sep 2012 07:01:44 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at mail.internecto.net Received: from mx1.internecto.net ([127.0.0.1]) by localhost (mail.polaris.internecto.net [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id wAlns6snzVk8 for ; Thu, 27 Sep 2012 07:01:43 +0000 (UTC) Received: from internecto.net (5ED4FDEB.cm-7-5d.dynamic.ziggo.nl [94.212.253.235]) (using TLSv1 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (Client did not present a certificate) (Authenticated sender: lists@internecto.net) by mx1.internecto.net (Postfix) with ESMTPSA id 309E6A0058 for ; Thu, 27 Sep 2012 07:01:43 +0000 (UTC) Date: Thu, 27 Sep 2012 09:01:41 +0200 From: Mark van Dijk To: xen-users@lists.xen.org Message-ID: <20120927090141.450c69e5@internecto.net> In-Reply-To: References: Organization: Internecto SIS X-Mailer: Claws Mail 3.8.0 (GTK+ 2.24.10; i686-pc-linux-gnu) Mime-Version: 1.0 Subject: Re: [Xen-users] sparse to no sparse X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org Quoting Fajar A. Nugraha's message from 27 sep 2012: >On Thu, Sep 27, 2012 at 5:43 AM, Paras pradhan > wrote: >> Hi. >> >> I have an old Xen para virt vm which I created using sparse file. Is >> there any way to convert this vm image to non-sparse without shutting >> down the vm?. > >No. > Can't you fill it up with zeros and then delete the file? i.e. on the domu, dd if=/dev/zero of=null.tmp; rm null.tmp. -- Stay in touch, Mark van Dijk. ,------------------------------------ -------------------------------' Thu Sep 27 07:00 UTC 2012 Today is Setting Orange, the 51st day of Bureaucracy in the YOLD 3178 _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Thu Sep 27 07:45:11 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Thu, 27 Sep 2012 07:45:11 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TH8lM-0006ij-4T; Thu, 27 Sep 2012 07:44:00 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TH8lK-0006ic-MV for xen-users@lists.xen.org; Thu, 27 Sep 2012 07:43:58 +0000 Received: from [85.158.138.51:47107] by server-10.bemta-3.messagelabs.com id 88/1C-02525-DB304605; Thu, 27 Sep 2012 07:43:57 +0000 X-Env-Sender: fajar@fajar.net X-Msg-Ref: server-7.tower-174.messagelabs.com!1348731835!23268188!1 X-Originating-IP: [209.85.219.45] X-SpamReason: No, hits=0.3 required=7.0 tests=RCVD_BY_IP X-StarScan-Received: X-StarScan-Version: 6.6.1.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 4472 invoked from network); 27 Sep 2012 07:43:57 -0000 Received: from mail-oa0-f45.google.com (HELO mail-oa0-f45.google.com) (209.85.219.45) by server-7.tower-174.messagelabs.com with RC4-SHA encrypted SMTP; 27 Sep 2012 07:43:57 -0000 Received: by oagi18 with SMTP id i18so1995577oag.32 for ; Thu, 27 Sep 2012 00:43:55 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:x-gm-message-state; bh=BLFXFgw9fTSXEkNGrJoTfjOjYbu+4dBGGLExF7oR8YM=; b=THHcLZaYX6g61YzUdtKZhXyW7ZpWjpQ3WD6+vwAqcFwWC5cp5AXF23bu5xPbukWb8g AsKTqurvmp16fCiIIh7Aouy16xlW8b6Ylh8UvviMmoogMYtglvZCqLFrtfHZByPAtiWh J4YKIOniVT47qPQcp5nAwjLTo9xBgb0RFpHNqLAuFnjAn9qmjLwwn/oPac4hc8gGvwkH VyMRodYDNJSBQDA22hkyBnKNv5XqTrCJJfto04Mx4zo6GHuqIFagNhtOkp9KDe+FNxgp j/6xvsY2x2ZwoyeRBr/qg04YK36+D7l5qoIYZV1w41cpaoymlMBN/n4mlki7lAiA9IuX 2AIg== MIME-Version: 1.0 Received: by 10.182.131.98 with SMTP id ol2mr2424120obb.69.1348731835277; Thu, 27 Sep 2012 00:43:55 -0700 (PDT) Received: by 10.60.150.141 with HTTP; Thu, 27 Sep 2012 00:43:55 -0700 (PDT) In-Reply-To: <20120927090141.450c69e5@internecto.net> References: <20120927090141.450c69e5@internecto.net> Date: Thu, 27 Sep 2012 14:43:55 +0700 Message-ID: From: "Fajar A. Nugraha" To: Mark van Dijk X-Gm-Message-State: ALoCoQlrb2CdSy8f5cXrg3Dbeswv9KEh2lneRTEkluj/hpLQRkmrtgwrQ0EbnR9q2waUgEqBqPDU Cc: xen-users@lists.xen.org Subject: Re: [Xen-users] sparse to no sparse X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org On Thu, Sep 27, 2012 at 2:01 PM, Mark van Dijk wrote: > Quoting Fajar A. Nugraha's message from 27 sep 2012: >>On Thu, Sep 27, 2012 at 5:43 AM, Paras pradhan >> wrote: >>> Hi. >>> >>> I have an old Xen para virt vm which I created using sparse file. Is >>> there any way to convert this vm image to non-sparse without shutting >>> down the vm?. >> >>No. >> > Can't you fill it up with zeros and then delete the file? i.e. on the > domu, dd if=/dev/zero of=null.tmp; rm null.tmp. AFAIK some fs will bomb out before you actually fill all space. So with that method the resulting backend might still be slightly sparse. It's not recommended anyway, as there's a possibility that during that process applications on the domU can go haywire since it can't write data to disk (out of space errors). -- Fajar _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Thu Sep 27 07:45:11 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Thu, 27 Sep 2012 07:45:11 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TH8lM-0006ij-4T; Thu, 27 Sep 2012 07:44:00 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TH8lK-0006ic-MV for xen-users@lists.xen.org; Thu, 27 Sep 2012 07:43:58 +0000 Received: from [85.158.138.51:47107] by server-10.bemta-3.messagelabs.com id 88/1C-02525-DB304605; Thu, 27 Sep 2012 07:43:57 +0000 X-Env-Sender: fajar@fajar.net X-Msg-Ref: server-7.tower-174.messagelabs.com!1348731835!23268188!1 X-Originating-IP: [209.85.219.45] X-SpamReason: No, hits=0.3 required=7.0 tests=RCVD_BY_IP X-StarScan-Received: X-StarScan-Version: 6.6.1.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 4472 invoked from network); 27 Sep 2012 07:43:57 -0000 Received: from mail-oa0-f45.google.com (HELO mail-oa0-f45.google.com) (209.85.219.45) by server-7.tower-174.messagelabs.com with RC4-SHA encrypted SMTP; 27 Sep 2012 07:43:57 -0000 Received: by oagi18 with SMTP id i18so1995577oag.32 for ; Thu, 27 Sep 2012 00:43:55 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:x-gm-message-state; bh=BLFXFgw9fTSXEkNGrJoTfjOjYbu+4dBGGLExF7oR8YM=; b=THHcLZaYX6g61YzUdtKZhXyW7ZpWjpQ3WD6+vwAqcFwWC5cp5AXF23bu5xPbukWb8g AsKTqurvmp16fCiIIh7Aouy16xlW8b6Ylh8UvviMmoogMYtglvZCqLFrtfHZByPAtiWh J4YKIOniVT47qPQcp5nAwjLTo9xBgb0RFpHNqLAuFnjAn9qmjLwwn/oPac4hc8gGvwkH VyMRodYDNJSBQDA22hkyBnKNv5XqTrCJJfto04Mx4zo6GHuqIFagNhtOkp9KDe+FNxgp j/6xvsY2x2ZwoyeRBr/qg04YK36+D7l5qoIYZV1w41cpaoymlMBN/n4mlki7lAiA9IuX 2AIg== MIME-Version: 1.0 Received: by 10.182.131.98 with SMTP id ol2mr2424120obb.69.1348731835277; Thu, 27 Sep 2012 00:43:55 -0700 (PDT) Received: by 10.60.150.141 with HTTP; Thu, 27 Sep 2012 00:43:55 -0700 (PDT) In-Reply-To: <20120927090141.450c69e5@internecto.net> References: <20120927090141.450c69e5@internecto.net> Date: Thu, 27 Sep 2012 14:43:55 +0700 Message-ID: From: "Fajar A. Nugraha" To: Mark van Dijk X-Gm-Message-State: ALoCoQlrb2CdSy8f5cXrg3Dbeswv9KEh2lneRTEkluj/hpLQRkmrtgwrQ0EbnR9q2waUgEqBqPDU Cc: xen-users@lists.xen.org Subject: Re: [Xen-users] sparse to no sparse X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org On Thu, Sep 27, 2012 at 2:01 PM, Mark van Dijk wrote: > Quoting Fajar A. Nugraha's message from 27 sep 2012: >>On Thu, Sep 27, 2012 at 5:43 AM, Paras pradhan >> wrote: >>> Hi. >>> >>> I have an old Xen para virt vm which I created using sparse file. Is >>> there any way to convert this vm image to non-sparse without shutting >>> down the vm?. >> >>No. >> > Can't you fill it up with zeros and then delete the file? i.e. on the > domu, dd if=/dev/zero of=null.tmp; rm null.tmp. AFAIK some fs will bomb out before you actually fill all space. So with that method the resulting backend might still be slightly sparse. It's not recommended anyway, as there's a possibility that during that process applications on the domU can go haywire since it can't write data to disk (out of space errors). -- Fajar _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Thu Sep 27 10:32:02 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Thu, 27 Sep 2012 10:32:02 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1THBMq-0001OF-8w; Thu, 27 Sep 2012 10:30:52 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1THBMp-0001Nl-0h for xen-users@lists.xen.org; Thu, 27 Sep 2012 10:30:51 +0000 Received: from [85.158.143.99:2104] by server-1.bemta-4.messagelabs.com id D1/18-05684-9DA24605; Thu, 27 Sep 2012 10:30:49 +0000 X-Env-Sender: lars.kurth.xen@gmail.com X-Msg-Ref: server-14.tower-216.messagelabs.com!1348741847!22363696!1 X-Originating-IP: [209.85.214.45] X-SpamReason: No, hits=0.8 required=7.0 tests=BODY_RANDOM_LONG, ML_RADAR_SPEW_LINKS_23,RCVD_BY_IP,spamassassin: X-StarScan-Received: X-StarScan-Version: 6.6.1.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 31204 invoked from network); 27 Sep 2012 10:30:48 -0000 Received: from mail-bk0-f45.google.com (HELO mail-bk0-f45.google.com) (209.85.214.45) by server-14.tower-216.messagelabs.com with RC4-SHA encrypted SMTP; 27 Sep 2012 10:30:48 -0000 Received: by bkcjf3 with SMTP id jf3so1002477bkc.32 for ; Thu, 27 Sep 2012 03:30:47 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=sender:message-id:date:from:reply-to:user-agent:mime-version:to :subject:content-type:content-transfer-encoding; bh=RyWPaBVV5EKIt/pyKTe1/0Bs8HPukr02t3D1+RIvw9s=; b=KQLf4aMacCbwgbeyG+edywB1N/syJ/IhYsoebJDb7lFtFF0vBP2nP4rbfsEPFEiQ2y GWX1Hs6oeAtvt0Jkup0WMHaAu372reo7h2GHPyho2/cGc+D/2/T94xmPl8KMuVDb5U+G X+mrYy+MFA7wJSKuvEhVDLJ7UOeG9vhECQiqK8EzjppoxNUCtSpszbk5k0kH494tV/UV 5d+KePeX2EszCqjd5QvAPj594Ne0xtLTuBGlF3A6lU70qemOzU4QpunsVXZSOF3vaxDm oPXDUoXJhUQEkP6TPDEn33tXS3Tb4Ij5jC/yfo+RzUqXKURBIkEwcyODqDZ/CeHcd8pb SN+w== Received: by 10.204.155.133 with SMTP id s5mr1876405bkw.112.1348741847301; Thu, 27 Sep 2012 03:30:47 -0700 (PDT) Received: from [172.16.26.11] (b0fb5b35.bb.sky.com. [176.251.91.53]) by mx.google.com with ESMTPS id j24sm4168320bkv.0.2012.09.27.03.30.40 (version=SSLv3 cipher=OTHER); Thu, 27 Sep 2012 03:30:46 -0700 (PDT) Message-ID: <50642AC8.2070302@xen.org> Date: Thu, 27 Sep 2012 11:30:32 +0100 From: Lars Kurth User-Agent: Mozilla/5.0 (Windows NT 6.1; rv:15.0) Gecko/20120907 Thunderbird/15.0.1 MIME-Version: 1.0 To: "xen-devel@lists.xen.org" , "xen-api@lists.xen.org" , xen-users@lists.xen.org Subject: [Xen-users] Apache CloudStack Collaborotion Summit - Call for Xen Community Participation X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list Reply-To: lars.kurth@xen.org List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset="us-ascii"; Format="flowed" Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org Dear Community Members, Apache CloudStack is holding it's first Collaboration Summit, Nov 30 - Dec 2, in Las Vegas. The event takes place immediately after the AWS re: Invent conference in the same location. As a large proportion of CloudStack users use XCP, it would be really good if our community had a presence. The type of contributions which make sense are: XCP introduction and XCP+CloudStack case studies. Here is a little bit more information about the conference: "The Collaboration Conference will give CloudStack users an opportunity to learn about improvements in the upcoming Apache CloudStack 4.0 release, and best practices for deploying and managing CloudStack. Users will also be able to attend sessions on projects and tools that work well with CloudStack for configuration management, storage, monitoring, creating a Platform-as-a-Service (PaaS) on top of CloudStack, and more." 1) http://collab12.cloudstack.org/ 2) http://collab12.cloudstack.org/proposals/ (Deadline Oct 5th) 3)http://cloudstack.org/blog/183-announcing-the-cloudstack-collaboration-conference-november-30-december-2%2C-2012-in-las-vegas.html You can submit proposals directly via the cloudstack site above. However, if you need help with material (there is plenty, which can be re-used), support for travel, or maybe cannot make the CFP deadline, drop me a line and I will see what I can do. Best Regards Lars _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Thu Sep 27 10:32:02 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Thu, 27 Sep 2012 10:32:02 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1THBMq-0001OF-8w; Thu, 27 Sep 2012 10:30:52 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1THBMp-0001Nl-0h for xen-users@lists.xen.org; Thu, 27 Sep 2012 10:30:51 +0000 Received: from [85.158.143.99:2104] by server-1.bemta-4.messagelabs.com id D1/18-05684-9DA24605; Thu, 27 Sep 2012 10:30:49 +0000 X-Env-Sender: lars.kurth.xen@gmail.com X-Msg-Ref: server-14.tower-216.messagelabs.com!1348741847!22363696!1 X-Originating-IP: [209.85.214.45] X-SpamReason: No, hits=0.8 required=7.0 tests=BODY_RANDOM_LONG, ML_RADAR_SPEW_LINKS_23,RCVD_BY_IP,spamassassin: X-StarScan-Received: X-StarScan-Version: 6.6.1.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 31204 invoked from network); 27 Sep 2012 10:30:48 -0000 Received: from mail-bk0-f45.google.com (HELO mail-bk0-f45.google.com) (209.85.214.45) by server-14.tower-216.messagelabs.com with RC4-SHA encrypted SMTP; 27 Sep 2012 10:30:48 -0000 Received: by bkcjf3 with SMTP id jf3so1002477bkc.32 for ; Thu, 27 Sep 2012 03:30:47 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=sender:message-id:date:from:reply-to:user-agent:mime-version:to :subject:content-type:content-transfer-encoding; bh=RyWPaBVV5EKIt/pyKTe1/0Bs8HPukr02t3D1+RIvw9s=; b=KQLf4aMacCbwgbeyG+edywB1N/syJ/IhYsoebJDb7lFtFF0vBP2nP4rbfsEPFEiQ2y GWX1Hs6oeAtvt0Jkup0WMHaAu372reo7h2GHPyho2/cGc+D/2/T94xmPl8KMuVDb5U+G X+mrYy+MFA7wJSKuvEhVDLJ7UOeG9vhECQiqK8EzjppoxNUCtSpszbk5k0kH494tV/UV 5d+KePeX2EszCqjd5QvAPj594Ne0xtLTuBGlF3A6lU70qemOzU4QpunsVXZSOF3vaxDm oPXDUoXJhUQEkP6TPDEn33tXS3Tb4Ij5jC/yfo+RzUqXKURBIkEwcyODqDZ/CeHcd8pb SN+w== Received: by 10.204.155.133 with SMTP id s5mr1876405bkw.112.1348741847301; Thu, 27 Sep 2012 03:30:47 -0700 (PDT) Received: from [172.16.26.11] (b0fb5b35.bb.sky.com. [176.251.91.53]) by mx.google.com with ESMTPS id j24sm4168320bkv.0.2012.09.27.03.30.40 (version=SSLv3 cipher=OTHER); Thu, 27 Sep 2012 03:30:46 -0700 (PDT) Message-ID: <50642AC8.2070302@xen.org> Date: Thu, 27 Sep 2012 11:30:32 +0100 From: Lars Kurth User-Agent: Mozilla/5.0 (Windows NT 6.1; rv:15.0) Gecko/20120907 Thunderbird/15.0.1 MIME-Version: 1.0 To: "xen-devel@lists.xen.org" , "xen-api@lists.xen.org" , xen-users@lists.xen.org Subject: [Xen-users] Apache CloudStack Collaborotion Summit - Call for Xen Community Participation X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list Reply-To: lars.kurth@xen.org List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset="us-ascii"; Format="flowed" Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org Dear Community Members, Apache CloudStack is holding it's first Collaboration Summit, Nov 30 - Dec 2, in Las Vegas. The event takes place immediately after the AWS re: Invent conference in the same location. As a large proportion of CloudStack users use XCP, it would be really good if our community had a presence. The type of contributions which make sense are: XCP introduction and XCP+CloudStack case studies. Here is a little bit more information about the conference: "The Collaboration Conference will give CloudStack users an opportunity to learn about improvements in the upcoming Apache CloudStack 4.0 release, and best practices for deploying and managing CloudStack. Users will also be able to attend sessions on projects and tools that work well with CloudStack for configuration management, storage, monitoring, creating a Platform-as-a-Service (PaaS) on top of CloudStack, and more." 1) http://collab12.cloudstack.org/ 2) http://collab12.cloudstack.org/proposals/ (Deadline Oct 5th) 3)http://cloudstack.org/blog/183-announcing-the-cloudstack-collaboration-conference-november-30-december-2%2C-2012-in-las-vegas.html You can submit proposals directly via the cloudstack site above. However, if you need help with material (there is plenty, which can be re-used), support for travel, or maybe cannot make the CFP deadline, drop me a line and I will see what I can do. Best Regards Lars _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Thu Sep 27 11:04:59 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Thu, 27 Sep 2012 11:04:59 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1THBsd-00028h-Bq; Thu, 27 Sep 2012 11:03:43 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1THBsb-00028c-Jd for xen-users@lists.xen.org; Thu, 27 Sep 2012 11:03:41 +0000 Received: from [85.158.143.35:9031] by server-3.bemta-4.messagelabs.com id 89/DD-10986-C8234605; Thu, 27 Sep 2012 11:03:40 +0000 X-Env-Sender: imperiaonline4@gmail.com X-Msg-Ref: server-5.tower-21.messagelabs.com!1348743811!4360116!1 X-Originating-IP: [209.85.214.173] X-SpamReason: No, hits=0.3 required=7.0 tests=ML_RADAR_SPEW_LINKS_14, ML_RADAR_SPEW_LINKS_8,RCVD_BY_IP,spamassassin: ,async_handler: YXN5bmNfZGVsYXk6IDcwNTcwMjIgKHRpbWVvdXQp\n X-StarScan-Received: X-StarScan-Version: 6.6.1.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 27037 invoked from network); 27 Sep 2012 11:03:33 -0000 Received: from mail-ob0-f173.google.com (HELO mail-ob0-f173.google.com) (209.85.214.173) by server-5.tower-21.messagelabs.com with RC4-SHA encrypted SMTP; 27 Sep 2012 11:03:33 -0000 Received: by obbta14 with SMTP id ta14so2183710obb.32 for ; Thu, 27 Sep 2012 04:03:31 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:date:message-id:subject:from:to:content-type; bh=LxwMLLf05esgosQBBHQCzJF9KcCbABbRy6iEQ+kE1ac=; b=vuStfd09A5ilkuoY0L4IE3XPJoKCs2oHWzjc1IQPo/7sMM1Xsdwkoi76JQ41qxgpS/ Kf1Mzw9j+nb+NZITyOrdry/qd5DDk275/NZz1sT+0J5q5sVcvHPAa4/b10lh+eToeYdd sZ2lJ+Szp9YZlj5cjnWfw83LKD4tYHhb+n5JcjUn9AiEh5KoJWN34iTMUZDig5mYEaWi Qh16C3QSqo8SYzZtzlyWT8GYiHDB5OPXgoUQkpnIBGO5yXwqRSm0V7uBQ59R31WfTVd7 PrCaW+dm5RCglj1b3VEqKt0O1XiVjBho9tOphg87wsW0OiNf3A0Kawt21109PnAqCbzu G26Q== MIME-Version: 1.0 Received: by 10.60.26.41 with SMTP id i9mr2777375oeg.65.1348743811275; Thu, 27 Sep 2012 04:03:31 -0700 (PDT) Received: by 10.60.146.236 with HTTP; Thu, 27 Sep 2012 04:03:31 -0700 (PDT) Date: Thu, 27 Sep 2012 13:03:31 +0200 Message-ID: From: Dariusz Krempa To: xen-users@lists.xen.org Subject: [Xen-users] Success VGA passthrough on windows 7 x64 with Xen 4.2.1-pre X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org I'm glad i can report that today i have 100% success with VGA passthrough on windows 7 64-bit. That nasty yellow triangle with error 43 disappeared and my GTX560 has 7.8 points in aero index, also Gpu-z and Cpu-z see vga card properly and unigine heaven benchmark have no problem with it. Now i have to figure which particular option let me to do this. Most likely it was turned off msi_translate in DomU config, but i will make more test and i will share with full information today later. Cause i'm newbie with Xen and linux if there is some particular information i can share with, then please tell me and i will try to do that. http://tinypic.com/r/33djtwz/6 _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Thu Sep 27 11:04:59 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Thu, 27 Sep 2012 11:04:59 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1THBsd-00028h-Bq; Thu, 27 Sep 2012 11:03:43 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1THBsb-00028c-Jd for xen-users@lists.xen.org; Thu, 27 Sep 2012 11:03:41 +0000 Received: from [85.158.143.35:9031] by server-3.bemta-4.messagelabs.com id 89/DD-10986-C8234605; Thu, 27 Sep 2012 11:03:40 +0000 X-Env-Sender: imperiaonline4@gmail.com X-Msg-Ref: server-5.tower-21.messagelabs.com!1348743811!4360116!1 X-Originating-IP: [209.85.214.173] X-SpamReason: No, hits=0.3 required=7.0 tests=ML_RADAR_SPEW_LINKS_14, ML_RADAR_SPEW_LINKS_8,RCVD_BY_IP,spamassassin: ,async_handler: YXN5bmNfZGVsYXk6IDcwNTcwMjIgKHRpbWVvdXQp\n X-StarScan-Received: X-StarScan-Version: 6.6.1.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 27037 invoked from network); 27 Sep 2012 11:03:33 -0000 Received: from mail-ob0-f173.google.com (HELO mail-ob0-f173.google.com) (209.85.214.173) by server-5.tower-21.messagelabs.com with RC4-SHA encrypted SMTP; 27 Sep 2012 11:03:33 -0000 Received: by obbta14 with SMTP id ta14so2183710obb.32 for ; Thu, 27 Sep 2012 04:03:31 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:date:message-id:subject:from:to:content-type; bh=LxwMLLf05esgosQBBHQCzJF9KcCbABbRy6iEQ+kE1ac=; b=vuStfd09A5ilkuoY0L4IE3XPJoKCs2oHWzjc1IQPo/7sMM1Xsdwkoi76JQ41qxgpS/ Kf1Mzw9j+nb+NZITyOrdry/qd5DDk275/NZz1sT+0J5q5sVcvHPAa4/b10lh+eToeYdd sZ2lJ+Szp9YZlj5cjnWfw83LKD4tYHhb+n5JcjUn9AiEh5KoJWN34iTMUZDig5mYEaWi Qh16C3QSqo8SYzZtzlyWT8GYiHDB5OPXgoUQkpnIBGO5yXwqRSm0V7uBQ59R31WfTVd7 PrCaW+dm5RCglj1b3VEqKt0O1XiVjBho9tOphg87wsW0OiNf3A0Kawt21109PnAqCbzu G26Q== MIME-Version: 1.0 Received: by 10.60.26.41 with SMTP id i9mr2777375oeg.65.1348743811275; Thu, 27 Sep 2012 04:03:31 -0700 (PDT) Received: by 10.60.146.236 with HTTP; Thu, 27 Sep 2012 04:03:31 -0700 (PDT) Date: Thu, 27 Sep 2012 13:03:31 +0200 Message-ID: From: Dariusz Krempa To: xen-users@lists.xen.org Subject: [Xen-users] Success VGA passthrough on windows 7 x64 with Xen 4.2.1-pre X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org I'm glad i can report that today i have 100% success with VGA passthrough on windows 7 64-bit. That nasty yellow triangle with error 43 disappeared and my GTX560 has 7.8 points in aero index, also Gpu-z and Cpu-z see vga card properly and unigine heaven benchmark have no problem with it. Now i have to figure which particular option let me to do this. Most likely it was turned off msi_translate in DomU config, but i will make more test and i will share with full information today later. Cause i'm newbie with Xen and linux if there is some particular information i can share with, then please tell me and i will try to do that. http://tinypic.com/r/33djtwz/6 _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Thu Sep 27 11:30:06 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Thu, 27 Sep 2012 11:30:06 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1THCHJ-0003KB-9H; Thu, 27 Sep 2012 11:29:13 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1THCHI-0003K6-CL for xen-users@lists.xen.org; Thu, 27 Sep 2012 11:29:12 +0000 Received: from [85.158.138.51:41039] by server-4.bemta-3.messagelabs.com id D5/11-14155-78834605; Thu, 27 Sep 2012 11:29:11 +0000 X-Env-Sender: extraordinarioso@gmail.com X-Msg-Ref: server-6.tower-174.messagelabs.com!1348745349!24153457!1 X-Originating-IP: [209.85.212.45] X-SpamReason: No, hits=1.5 required=7.0 tests=HTML_00_10,HTML_MESSAGE, ML_RADAR_SPEW_LINKS_14,RCVD_BY_IP,spamassassin: X-StarScan-Received: X-StarScan-Version: 6.6.1.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 25275 invoked from network); 27 Sep 2012 11:29:10 -0000 Received: from mail-vb0-f45.google.com (HELO mail-vb0-f45.google.com) (209.85.212.45) by server-6.tower-174.messagelabs.com with RC4-SHA encrypted SMTP; 27 Sep 2012 11:29:10 -0000 Received: by vbip1 with SMTP id p1so2159806vbi.32 for ; Thu, 27 Sep 2012 04:29:09 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:date:message-id:subject:from:to:content-type; bh=YgSFiN4WzYz6g3tSJK9plrGMeBLfNPgxwA4X+seGZHc=; b=Bo0slF+DuAMML0Q5fUz0wN7HofJVQt+bmqxzUhkQeoqtczr5lk6Mf0k1NrXQ3ZwYf+ r99RFqgX3Qgqqx70PtRvuYYrMBM6RfamfI6haGroiv2jjR2L1E3mnIHBo/gdDo6GqlyU YzNrsSR1bCTzQHhYaLlWH8t/081yN2sWeuZnfBQgukd1jOwiOwWa2xlAYkQx7c4CsLwL uSuApsScs1918cUzclB7abpd253CD264LQCipq2Z5PdveIrcLKj+nR5kUkUoNHu5zDug Gi+UZcE2AxjM1TXR1XldX6VJ2hP3cNh7LhgKxa/Fy5+jJs8jZ7wRqksCO8t4GlP/V2N/ JnkA== MIME-Version: 1.0 Received: by 10.52.69.174 with SMTP id f14mr1762416vdu.17.1348745349484; Thu, 27 Sep 2012 04:29:09 -0700 (PDT) Received: by 10.220.112.11 with HTTP; Thu, 27 Sep 2012 04:29:09 -0700 (PDT) Date: Thu, 27 Sep 2012 13:29:09 +0200 Message-ID: From: extraordinarioso extraordinarioso To: xen-users@lists.xen.org Subject: [Xen-users] Dom0 archlinux kernel 3.5 with Nvidia gt240 -> Black screen X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============2738566168858722117==" Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org --===============2738566168858722117== Content-Type: multipart/alternative; boundary=20cf307f31fc72d03c04caad3ff9 --20cf307f31fc72d03c04caad3ff9 Content-Type: text/plain; charset=ISO-8859-1 Hello I have probed with ubuntu, fedora and archlinux as dom0 but always get the same error: dom0 with blank screen. I think it must be related with nvidia propietary driver that gets xorg exhausted and it turns off the screen after 10 seconds At least now i can enter in the gui without xen with the latests kernels and drivers (before was impossible) But with xen the dom0 cant start the gui, only get a blank screen and have to reboot. OS: Archlinux kernel: 3.5 Graphics: Nvidia Zotac GT240 GDDR5 Motherboard: GA-990FXA-UD3 v1.0 Bios F8 CPU: FX6200 x6 3800mhz Tried: nomodeset, pat, "amd_iommu=on iommu=on,pt" nothing works --20cf307f31fc72d03c04caad3ff9 Content-Type: text/html; charset=ISO-8859-1 Hello

I have probed with ubuntu, fedora and archlinux as dom0 but always get the same error: dom0 with blank screen. I think it must be related with nvidia propietary driver that gets xorg exhausted and it turns off the screen after 10 seconds

At least now i can enter in the gui without xen with the latests kernels and drivers (before was impossible)

But with xen the dom0 cant start the gui, only get a blank screen and have to reboot.

OS: Archlinux
kernel: 3.5
Graphics: Nvidia Zotac GT240 GDDR5
Motherboard: GA-990FXA-UD3 v1.0 Bios F8
CPU: FX6200 x6 3800mhz

Tried: nomodeset, pat, "amd_iommu=on iommu=on,pt" nothing works
--20cf307f31fc72d03c04caad3ff9-- --===============2738566168858722117== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users --===============2738566168858722117==-- From xen-users-bounces@lists.xen.org Thu Sep 27 11:30:06 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Thu, 27 Sep 2012 11:30:06 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1THCHJ-0003KB-9H; Thu, 27 Sep 2012 11:29:13 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1THCHI-0003K6-CL for xen-users@lists.xen.org; Thu, 27 Sep 2012 11:29:12 +0000 Received: from [85.158.138.51:41039] by server-4.bemta-3.messagelabs.com id D5/11-14155-78834605; Thu, 27 Sep 2012 11:29:11 +0000 X-Env-Sender: extraordinarioso@gmail.com X-Msg-Ref: server-6.tower-174.messagelabs.com!1348745349!24153457!1 X-Originating-IP: [209.85.212.45] X-SpamReason: No, hits=1.5 required=7.0 tests=HTML_00_10,HTML_MESSAGE, ML_RADAR_SPEW_LINKS_14,RCVD_BY_IP,spamassassin: X-StarScan-Received: X-StarScan-Version: 6.6.1.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 25275 invoked from network); 27 Sep 2012 11:29:10 -0000 Received: from mail-vb0-f45.google.com (HELO mail-vb0-f45.google.com) (209.85.212.45) by server-6.tower-174.messagelabs.com with RC4-SHA encrypted SMTP; 27 Sep 2012 11:29:10 -0000 Received: by vbip1 with SMTP id p1so2159806vbi.32 for ; Thu, 27 Sep 2012 04:29:09 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:date:message-id:subject:from:to:content-type; bh=YgSFiN4WzYz6g3tSJK9plrGMeBLfNPgxwA4X+seGZHc=; b=Bo0slF+DuAMML0Q5fUz0wN7HofJVQt+bmqxzUhkQeoqtczr5lk6Mf0k1NrXQ3ZwYf+ r99RFqgX3Qgqqx70PtRvuYYrMBM6RfamfI6haGroiv2jjR2L1E3mnIHBo/gdDo6GqlyU YzNrsSR1bCTzQHhYaLlWH8t/081yN2sWeuZnfBQgukd1jOwiOwWa2xlAYkQx7c4CsLwL uSuApsScs1918cUzclB7abpd253CD264LQCipq2Z5PdveIrcLKj+nR5kUkUoNHu5zDug Gi+UZcE2AxjM1TXR1XldX6VJ2hP3cNh7LhgKxa/Fy5+jJs8jZ7wRqksCO8t4GlP/V2N/ JnkA== MIME-Version: 1.0 Received: by 10.52.69.174 with SMTP id f14mr1762416vdu.17.1348745349484; Thu, 27 Sep 2012 04:29:09 -0700 (PDT) Received: by 10.220.112.11 with HTTP; Thu, 27 Sep 2012 04:29:09 -0700 (PDT) Date: Thu, 27 Sep 2012 13:29:09 +0200 Message-ID: From: extraordinarioso extraordinarioso To: xen-users@lists.xen.org Subject: [Xen-users] Dom0 archlinux kernel 3.5 with Nvidia gt240 -> Black screen X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============2738566168858722117==" Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org --===============2738566168858722117== Content-Type: multipart/alternative; boundary=20cf307f31fc72d03c04caad3ff9 --20cf307f31fc72d03c04caad3ff9 Content-Type: text/plain; charset=ISO-8859-1 Hello I have probed with ubuntu, fedora and archlinux as dom0 but always get the same error: dom0 with blank screen. I think it must be related with nvidia propietary driver that gets xorg exhausted and it turns off the screen after 10 seconds At least now i can enter in the gui without xen with the latests kernels and drivers (before was impossible) But with xen the dom0 cant start the gui, only get a blank screen and have to reboot. OS: Archlinux kernel: 3.5 Graphics: Nvidia Zotac GT240 GDDR5 Motherboard: GA-990FXA-UD3 v1.0 Bios F8 CPU: FX6200 x6 3800mhz Tried: nomodeset, pat, "amd_iommu=on iommu=on,pt" nothing works --20cf307f31fc72d03c04caad3ff9 Content-Type: text/html; charset=ISO-8859-1 Hello

I have probed with ubuntu, fedora and archlinux as dom0 but always get the same error: dom0 with blank screen. I think it must be related with nvidia propietary driver that gets xorg exhausted and it turns off the screen after 10 seconds

At least now i can enter in the gui without xen with the latests kernels and drivers (before was impossible)

But with xen the dom0 cant start the gui, only get a blank screen and have to reboot.

OS: Archlinux
kernel: 3.5
Graphics: Nvidia Zotac GT240 GDDR5
Motherboard: GA-990FXA-UD3 v1.0 Bios F8
CPU: FX6200 x6 3800mhz

Tried: nomodeset, pat, "amd_iommu=on iommu=on,pt" nothing works
--20cf307f31fc72d03c04caad3ff9-- --===============2738566168858722117== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users --===============2738566168858722117==-- From xen-users-bounces@lists.xen.org Thu Sep 27 13:06:52 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Thu, 27 Sep 2012 13:06:52 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1THDmj-0004yA-Gy; Thu, 27 Sep 2012 13:05:45 +0000 Received: from mail27.messagelabs.com ([193.109.254.147]) by lists.xen.org with smtp (Exim 4.72) (envelope-from ) id 1THDmh-0004y5-Ab for xen-users@lists.xen.org; Thu, 27 Sep 2012 13:05:43 +0000 X-Env-Sender: shades_of_grey@earthlink.net X-Msg-Ref: server-8.tower-27.messagelabs.com!1348751093!9292389!1 X-Originating-IP: [209.86.89.64] X-SpamReason: No, hits=0.0 required=7.0 tests=ML_RADAR_SPEW_LINKS_14, spamassassin: X-StarScan-Received: X-StarScan-Version: 6.6.1.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 12948 invoked from network); 27 Sep 2012 13:04:54 -0000 Received: from elasmtp-curtail.atl.sa.earthlink.net (HELO elasmtp-curtail.atl.sa.earthlink.net) (209.86.89.64) by server-8.tower-27.messagelabs.com with SMTP; 27 Sep 2012 13:04:54 -0000 DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=dk20050327; d=earthlink.net; b=IWdlD39MTX9DrNDp7G9CkLVZ2soWYBHuu+GmKa6PioG5f/o0NHUBsKkz7EhrdOtO; h=Received:Message-ID:Date:From:User-Agent:MIME-Version:To:Subject:References:In-Reply-To:Content-Type:Content-Transfer-Encoding:X-ELNK-Trace:X-Originating-IP; Received: from [66.167.250.229] (helo=[192.168.1.13]) by elasmtp-curtail.atl.sa.earthlink.net with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.67) (envelope-from ) id 1THDls-0004MU-HZ for xen-users@lists.xen.org; Thu, 27 Sep 2012 09:04:52 -0400 Message-ID: <50644EF4.2070408@earthlink.net> Date: Thu, 27 Sep 2012 09:04:52 -0400 From: ShadesOfGrey User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:15.0) Gecko/20120907 Thunderbird/15.0.1 MIME-Version: 1.0 To: xen-users@lists.xen.org References: <505B86AE.9040507@earthlink.net> <505C8630.2090002@student.chalmers.se> <505FD74E.2050405@earthlink.net> <506056BC.3010705@student.chalmers.se> <5063AD2E.10800@earthlink.net> <5063B281.7020801@digitalsilk.net> In-Reply-To: <5063B281.7020801@digitalsilk.net> X-ELNK-Trace: 0fe7bc40aa99bc8fc963772e86942a7b94f5150ab1c16ac0485087bba56e6009fa0e1d7ca0d20a88e212d3c23a193808350badd9bab72f9c350badd9bab72f9c X-Originating-IP: 66.167.250.229 Subject: Re: [Xen-users] Recommendations for Virtulization Hardware X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset="windows-1252"; Format="flowed" Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org On 09/26/2012 09:57 PM, Robert Rust wrote: > On 9/26/12 8:34 PM, ShadesOfGrey wrote: >> On 09/24/2012 08:49 AM, Robin Axelsson wrote: >>> On 2012-09-24 05:45, ShadesOfGrey wrote: >>>> Sorry for the late response, I've had a lot to digest. >> >>>> The lack of current information about Xen (and KVM) online has been >>>> frustrating =97 especially finding the many proof of concept videos >>>> that demonstrated possibilities but offered no real specifics. >>>> Looking for specifics, I sought information from gaming and >>>> enthusiast sites; I figured finding confirmation of VT-d and AMD-Vi >>>> support on such sites would be more likely. However, I found that >>>> wasn't often the case. I did determine that ASRock motherboards seem >>>> to be the most likely to support VT-d, ASUS least likely (unless >>>> equipped with an Intel 'sanctioned' VT-d chipset). I had narrowed my >>>> choices to two motherboards that appear to offer VT-d support and was >>>> intending to contact the manufacturer before purchase. Both choices >>>> are a bit pricey and I've been reconsidering whether I should look to >>>> other motherboards to reduce costs. >>> >>> Some motherboards support IOMMU even though it is not found in the >>> user manual or specified on the website. Your best bet is to ask >>> customer support. A guy posted here that he got it working on an Intel >>> motherboard that doesn't even have options for it in the BIOS, so it >>> seems that in some cases it is only up to the CPU. This is not the >>> case with AMD though as I stated before. I have bought a couple of >>> Gigabyte GA990FX-UD7 myself, they are stable and have a good layout. >>> They have support for IOMMU but I haven't tested it thoroughly enough >>> to fully confirm this although I don't believe there would be any >>> problem. >>> >> I'm aware of this. In fact, I only have anecdotal evidence that the >> Gigabyte G1.Sniper 3 has IOMMU (VT-d) support. I intend to query the >> manufacturers, seeking confirmation of IOMMU support, of every >> motherboard that ends up on my short list. I may include other Z77 >> motherboards from MSI and Gigabyte, since there is concrete evidence >> that the Z77 chipset does support IOMMU. I did focus, however, on those >> motherboards I had some inkling could support IOMMU. Now I'm trying to >> expand my selection process to include less expensive options. > > I have a Gigabyte GA-Z77-DS3H, which I can confirm does support IOMMU = > ... I'm passing PCI video tuner cards to two different DomUs and a = > PCI-Express 1x USB card to another DomU. > I also have an Intel DH77KC that does IOMMU but the H77 chipset = > support was (is?) buggy in the current mainstream kernel releases so = > it's still in the box on the shelf. > > -Robert > > _______________________________________________ > Xen-users mailing list > Xen-users@lists.xen.org > http://lists.xen.org/xen-users > The GA-Z77-DS3H doesn't fit my particular needs, but I appreciate your = confirming IOMMU support on that motherboard. If you ever get IOMMU = working on the DH77KC, please let us know. _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Thu Sep 27 13:06:52 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Thu, 27 Sep 2012 13:06:52 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1THDmj-0004yA-Gy; Thu, 27 Sep 2012 13:05:45 +0000 Received: from mail27.messagelabs.com ([193.109.254.147]) by lists.xen.org with smtp (Exim 4.72) (envelope-from ) id 1THDmh-0004y5-Ab for xen-users@lists.xen.org; Thu, 27 Sep 2012 13:05:43 +0000 X-Env-Sender: shades_of_grey@earthlink.net X-Msg-Ref: server-8.tower-27.messagelabs.com!1348751093!9292389!1 X-Originating-IP: [209.86.89.64] X-SpamReason: No, hits=0.0 required=7.0 tests=ML_RADAR_SPEW_LINKS_14, spamassassin: X-StarScan-Received: X-StarScan-Version: 6.6.1.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 12948 invoked from network); 27 Sep 2012 13:04:54 -0000 Received: from elasmtp-curtail.atl.sa.earthlink.net (HELO elasmtp-curtail.atl.sa.earthlink.net) (209.86.89.64) by server-8.tower-27.messagelabs.com with SMTP; 27 Sep 2012 13:04:54 -0000 DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=dk20050327; d=earthlink.net; b=IWdlD39MTX9DrNDp7G9CkLVZ2soWYBHuu+GmKa6PioG5f/o0NHUBsKkz7EhrdOtO; h=Received:Message-ID:Date:From:User-Agent:MIME-Version:To:Subject:References:In-Reply-To:Content-Type:Content-Transfer-Encoding:X-ELNK-Trace:X-Originating-IP; Received: from [66.167.250.229] (helo=[192.168.1.13]) by elasmtp-curtail.atl.sa.earthlink.net with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.67) (envelope-from ) id 1THDls-0004MU-HZ for xen-users@lists.xen.org; Thu, 27 Sep 2012 09:04:52 -0400 Message-ID: <50644EF4.2070408@earthlink.net> Date: Thu, 27 Sep 2012 09:04:52 -0400 From: ShadesOfGrey User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:15.0) Gecko/20120907 Thunderbird/15.0.1 MIME-Version: 1.0 To: xen-users@lists.xen.org References: <505B86AE.9040507@earthlink.net> <505C8630.2090002@student.chalmers.se> <505FD74E.2050405@earthlink.net> <506056BC.3010705@student.chalmers.se> <5063AD2E.10800@earthlink.net> <5063B281.7020801@digitalsilk.net> In-Reply-To: <5063B281.7020801@digitalsilk.net> X-ELNK-Trace: 0fe7bc40aa99bc8fc963772e86942a7b94f5150ab1c16ac0485087bba56e6009fa0e1d7ca0d20a88e212d3c23a193808350badd9bab72f9c350badd9bab72f9c X-Originating-IP: 66.167.250.229 Subject: Re: [Xen-users] Recommendations for Virtulization Hardware X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset="windows-1252"; Format="flowed" Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org On 09/26/2012 09:57 PM, Robert Rust wrote: > On 9/26/12 8:34 PM, ShadesOfGrey wrote: >> On 09/24/2012 08:49 AM, Robin Axelsson wrote: >>> On 2012-09-24 05:45, ShadesOfGrey wrote: >>>> Sorry for the late response, I've had a lot to digest. >> >>>> The lack of current information about Xen (and KVM) online has been >>>> frustrating =97 especially finding the many proof of concept videos >>>> that demonstrated possibilities but offered no real specifics. >>>> Looking for specifics, I sought information from gaming and >>>> enthusiast sites; I figured finding confirmation of VT-d and AMD-Vi >>>> support on such sites would be more likely. However, I found that >>>> wasn't often the case. I did determine that ASRock motherboards seem >>>> to be the most likely to support VT-d, ASUS least likely (unless >>>> equipped with an Intel 'sanctioned' VT-d chipset). I had narrowed my >>>> choices to two motherboards that appear to offer VT-d support and was >>>> intending to contact the manufacturer before purchase. Both choices >>>> are a bit pricey and I've been reconsidering whether I should look to >>>> other motherboards to reduce costs. >>> >>> Some motherboards support IOMMU even though it is not found in the >>> user manual or specified on the website. Your best bet is to ask >>> customer support. A guy posted here that he got it working on an Intel >>> motherboard that doesn't even have options for it in the BIOS, so it >>> seems that in some cases it is only up to the CPU. This is not the >>> case with AMD though as I stated before. I have bought a couple of >>> Gigabyte GA990FX-UD7 myself, they are stable and have a good layout. >>> They have support for IOMMU but I haven't tested it thoroughly enough >>> to fully confirm this although I don't believe there would be any >>> problem. >>> >> I'm aware of this. In fact, I only have anecdotal evidence that the >> Gigabyte G1.Sniper 3 has IOMMU (VT-d) support. I intend to query the >> manufacturers, seeking confirmation of IOMMU support, of every >> motherboard that ends up on my short list. I may include other Z77 >> motherboards from MSI and Gigabyte, since there is concrete evidence >> that the Z77 chipset does support IOMMU. I did focus, however, on those >> motherboards I had some inkling could support IOMMU. Now I'm trying to >> expand my selection process to include less expensive options. > > I have a Gigabyte GA-Z77-DS3H, which I can confirm does support IOMMU = > ... I'm passing PCI video tuner cards to two different DomUs and a = > PCI-Express 1x USB card to another DomU. > I also have an Intel DH77KC that does IOMMU but the H77 chipset = > support was (is?) buggy in the current mainstream kernel releases so = > it's still in the box on the shelf. > > -Robert > > _______________________________________________ > Xen-users mailing list > Xen-users@lists.xen.org > http://lists.xen.org/xen-users > The GA-Z77-DS3H doesn't fit my particular needs, but I appreciate your = confirming IOMMU support on that motherboard. If you ever get IOMMU = working on the DH77KC, please let us know. _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Thu Sep 27 13:16:24 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Thu, 27 Sep 2012 13:16:24 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1THDw2-0005Tt-O5; Thu, 27 Sep 2012 13:15:22 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1THDw0-0005Tj-FL for xen-users@lists.xen.org; Thu, 27 Sep 2012 13:15:20 +0000 Received: from [85.158.143.35:13384] by server-1.bemta-4.messagelabs.com id 51/15-05684-76154605; Thu, 27 Sep 2012 13:15:19 +0000 X-Env-Sender: izmmishao5@gmail.com X-Msg-Ref: server-4.tower-21.messagelabs.com!1348751715!5664856!1 X-Originating-IP: [209.85.214.45] X-SpamReason: No, hits=0.3 required=7.0 tests=ML_RADAR_SPEW_LINKS_14, ML_RADAR_SPEW_LINKS_8,RCVD_BY_IP,spamassassin: ,surbl: (ASYNC_NO) c3VyYmxfcmVjaGVja19kZWxheTogMCAoYWJhbmRvbmVkOiB0aW55cGljLmNvbS9yLzMzZGp0d 3ov\nNik=\n X-StarScan-Received: X-StarScan-Version: 6.6.1.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 5044 invoked from network); 27 Sep 2012 13:15:16 -0000 Received: from mail-bk0-f45.google.com (HELO mail-bk0-f45.google.com) (209.85.214.45) by server-4.tower-21.messagelabs.com with RC4-SHA encrypted SMTP; 27 Sep 2012 13:15:16 -0000 Received: by bkcjf3 with SMTP id jf3so1296617bkc.32 for ; Thu, 27 Sep 2012 06:15:15 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:user-agent:mime-version:to:subject:references :in-reply-to:content-type:content-transfer-encoding; bh=jvr98OM4ezGjTn9ay/eERE4fMbPXftTZ0S7Xw8w/E/M=; b=OHf/S7kt9uDLaF5ZHPnDtJh5zcm/EZNaQ667WDICL+LhZ/aaDk/crVWMUCtCGjNSR8 6zjk9bUKV0UEWRCWIrg3UXyV36RurV/Tvy4y6gmnrLDJbm6Ay4cT73ns3+/GtU0pDi4N O6I0UdyQ+zdWzGqnBjcRo6fpFmpnX4ZkY50nkaKKNuTsGBNcskVAxJSw6+adcHCGJ+kG QgqYcieE+sYsbW9l7G6FMe3u3KCMbHUirFO+XSkzg+G7N5TvejoVnAhOyWbAS9CF6ivW 2W0906vAyRzlI/3F89DTwq6OwsOBVSSq8jzrY8fCj3u8uPcOS7lCr8SmfUqryRQrU8Op 9IAw== Received: by 10.112.37.105 with SMTP id x9mr1599379lbj.69.1348751715225; Thu, 27 Sep 2012 06:15:15 -0700 (PDT) Received: from [192.168.0.110] ([217.14.197.114]) by mx.google.com with ESMTPS id pi16sm1700727lab.7.2012.09.27.06.15.13 (version=SSLv3 cipher=OTHER); Thu, 27 Sep 2012 06:15:14 -0700 (PDT) Message-ID: <50645166.2000200@gmail.com> Date: Thu, 27 Sep 2012 17:15:18 +0400 From: "Mikhail I. Izmestev" User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:14.0) Gecko/20120713 Thunderbird/14.0 MIME-Version: 1.0 To: xen-users@lists.xen.org References: In-Reply-To: Subject: Re: [Xen-users] Success VGA passthrough on windows 7 x64 with Xen 4.2.1-pre X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset="us-ascii"; Format="flowed" Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org Hi, 27.09.2012 15:03, Dariusz Krempa wrote: > I'm glad i can report that today i have 100% success with VGA > passthrough on windows 7 64-bit. That nasty yellow triangle with error > 43 disappeared and my GTX560 has 7.8 points in aero index, also Gpu-z > and Cpu-z see vga card properly and unigine heaven benchmark have no > problem with it. > Now i have to figure which particular option let me to do this. Most > likely it was turned off msi_translate in DomU config, but i will make > more test and i will share with full information today later. Cause > i'm newbie with Xen and linux if there is some particular information > i can share with, then please tell me and i will try to do that. > > http://tinypic.com/r/33djtwz/6 One day before I have tried to do this without luck. My configuration: MB: GA-Z77X-D3H with latest bios (F15) CPU: core i5-2400 two GPU GTX560 on 16x and 8x pcie ports (both works on 8x when two used). DomU: win7 x64 pro I have tried to do this with XCP 1.5b and XenServer 6.0 Free trial. There is dmesg for host: [root@xenserver-render ~]# xe host-dmesg | grep -i virtualisation (XEN) I/O virtualisation enabled (XEN) - APIC MMIO access virtualisation I just have "nasty yellow triangle with error 43" :) So I'm interested in your experience and solution. Mikhail. _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Thu Sep 27 13:16:24 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Thu, 27 Sep 2012 13:16:24 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1THDw2-0005Tt-O5; Thu, 27 Sep 2012 13:15:22 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1THDw0-0005Tj-FL for xen-users@lists.xen.org; Thu, 27 Sep 2012 13:15:20 +0000 Received: from [85.158.143.35:13384] by server-1.bemta-4.messagelabs.com id 51/15-05684-76154605; Thu, 27 Sep 2012 13:15:19 +0000 X-Env-Sender: izmmishao5@gmail.com X-Msg-Ref: server-4.tower-21.messagelabs.com!1348751715!5664856!1 X-Originating-IP: [209.85.214.45] X-SpamReason: No, hits=0.3 required=7.0 tests=ML_RADAR_SPEW_LINKS_14, ML_RADAR_SPEW_LINKS_8,RCVD_BY_IP,spamassassin: ,surbl: (ASYNC_NO) c3VyYmxfcmVjaGVja19kZWxheTogMCAoYWJhbmRvbmVkOiB0aW55cGljLmNvbS9yLzMzZGp0d 3ov\nNik=\n X-StarScan-Received: X-StarScan-Version: 6.6.1.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 5044 invoked from network); 27 Sep 2012 13:15:16 -0000 Received: from mail-bk0-f45.google.com (HELO mail-bk0-f45.google.com) (209.85.214.45) by server-4.tower-21.messagelabs.com with RC4-SHA encrypted SMTP; 27 Sep 2012 13:15:16 -0000 Received: by bkcjf3 with SMTP id jf3so1296617bkc.32 for ; Thu, 27 Sep 2012 06:15:15 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:user-agent:mime-version:to:subject:references :in-reply-to:content-type:content-transfer-encoding; bh=jvr98OM4ezGjTn9ay/eERE4fMbPXftTZ0S7Xw8w/E/M=; b=OHf/S7kt9uDLaF5ZHPnDtJh5zcm/EZNaQ667WDICL+LhZ/aaDk/crVWMUCtCGjNSR8 6zjk9bUKV0UEWRCWIrg3UXyV36RurV/Tvy4y6gmnrLDJbm6Ay4cT73ns3+/GtU0pDi4N O6I0UdyQ+zdWzGqnBjcRo6fpFmpnX4ZkY50nkaKKNuTsGBNcskVAxJSw6+adcHCGJ+kG QgqYcieE+sYsbW9l7G6FMe3u3KCMbHUirFO+XSkzg+G7N5TvejoVnAhOyWbAS9CF6ivW 2W0906vAyRzlI/3F89DTwq6OwsOBVSSq8jzrY8fCj3u8uPcOS7lCr8SmfUqryRQrU8Op 9IAw== Received: by 10.112.37.105 with SMTP id x9mr1599379lbj.69.1348751715225; Thu, 27 Sep 2012 06:15:15 -0700 (PDT) Received: from [192.168.0.110] ([217.14.197.114]) by mx.google.com with ESMTPS id pi16sm1700727lab.7.2012.09.27.06.15.13 (version=SSLv3 cipher=OTHER); Thu, 27 Sep 2012 06:15:14 -0700 (PDT) Message-ID: <50645166.2000200@gmail.com> Date: Thu, 27 Sep 2012 17:15:18 +0400 From: "Mikhail I. Izmestev" User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:14.0) Gecko/20120713 Thunderbird/14.0 MIME-Version: 1.0 To: xen-users@lists.xen.org References: In-Reply-To: Subject: Re: [Xen-users] Success VGA passthrough on windows 7 x64 with Xen 4.2.1-pre X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset="us-ascii"; Format="flowed" Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org Hi, 27.09.2012 15:03, Dariusz Krempa wrote: > I'm glad i can report that today i have 100% success with VGA > passthrough on windows 7 64-bit. That nasty yellow triangle with error > 43 disappeared and my GTX560 has 7.8 points in aero index, also Gpu-z > and Cpu-z see vga card properly and unigine heaven benchmark have no > problem with it. > Now i have to figure which particular option let me to do this. Most > likely it was turned off msi_translate in DomU config, but i will make > more test and i will share with full information today later. Cause > i'm newbie with Xen and linux if there is some particular information > i can share with, then please tell me and i will try to do that. > > http://tinypic.com/r/33djtwz/6 One day before I have tried to do this without luck. My configuration: MB: GA-Z77X-D3H with latest bios (F15) CPU: core i5-2400 two GPU GTX560 on 16x and 8x pcie ports (both works on 8x when two used). DomU: win7 x64 pro I have tried to do this with XCP 1.5b and XenServer 6.0 Free trial. There is dmesg for host: [root@xenserver-render ~]# xe host-dmesg | grep -i virtualisation (XEN) I/O virtualisation enabled (XEN) - APIC MMIO access virtualisation I just have "nasty yellow triangle with error 43" :) So I'm interested in your experience and solution. Mikhail. _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Thu Sep 27 15:55:57 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Thu, 27 Sep 2012 15:55:57 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1THGQP-0002JP-3a; Thu, 27 Sep 2012 15:54:53 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1THGQO-0002JC-B5 for xen-users@lists.xensource.com; Thu, 27 Sep 2012 15:54:52 +0000 Received: from [85.158.139.83:62399] by server-11.bemta-5.messagelabs.com id 44/CE-13866-BC674605; Thu, 27 Sep 2012 15:54:51 +0000 X-Env-Sender: mrsanna1@gmail.com X-Msg-Ref: server-12.tower-182.messagelabs.com!1348761289!32241157!1 X-Originating-IP: [209.85.212.43] X-SpamReason: No, hits=0.3 required=7.0 tests=ML_RADAR_SPEW_LINKS_14, RCVD_BY_IP,spamassassin: X-StarScan-Received: X-StarScan-Version: 6.6.1.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 1225 invoked from network); 27 Sep 2012 15:54:50 -0000 Received: from mail-vb0-f43.google.com (HELO mail-vb0-f43.google.com) (209.85.212.43) by server-12.tower-182.messagelabs.com with RC4-SHA encrypted SMTP; 27 Sep 2012 15:54:50 -0000 Received: by vbbfq11 with SMTP id fq11so2593218vbb.30 for ; Thu, 27 Sep 2012 08:54:49 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=KlG5w16g2rW49mskdLvsisNgmthetfkSy5RgMokk26A=; b=g16EFRwD7PKUsYfx2QpM7luT+KyKnRaZHnoIOcKXiRKTw9y71liglYH3/7O8CFzS7T Y96F9GlkLnN9RHw6juE55hOcCvCDVdOz/95N/X9LgK0e1hcFjwkWIdNHCtxbc6abZ4xI bsGxrcIb1iPck9n5Ej3Gtl06+eCKqUpli5YN6BmwIWPbgK8TZObQeHk4s8xjdLv+EcRt GDXprPYx9CeqEa+eOYJntMEO/5MshhzI2tvi9NHI5Y/m4hu1jtRKQTX4WD6lj3jtiob+ /7cIs80zPeU361VB5Quvdq/P/Gshopy6CcCAO07UPszrg6eTZeTRYYCCznv9bi2McBoi BY+g== MIME-Version: 1.0 Received: by 10.220.205.200 with SMTP id fr8mr2378179vcb.34.1348761288807; Thu, 27 Sep 2012 08:54:48 -0700 (PDT) Received: by 10.58.207.75 with HTTP; Thu, 27 Sep 2012 08:54:48 -0700 (PDT) In-Reply-To: References: <68c41dd8-9195-41b0-83d7-9242b8eff809@default> Date: Thu, 27 Sep 2012 17:54:48 +0200 Message-ID: From: Mauro To: Olivier Hanesse Cc: Dan Magenheimer , xen-devel@lists.xensource.com, Keir Fraser , Jeremy Fitzhardinge , Jan Beulich , Keir Fraser , Xen Users , Mark Adams Subject: Re: [Xen-users] [Xen-devel] Xen 4 TSC problems X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org On 28 February 2011 16:54, Olivier Hanesse wrote: > Yes this is what I mean. > I am glad to hear that it isn't a bad sign :) > I thought of a bad sign, because on system with "reliable TSC", this counter > is always 0. Hey men. I have exactly the same problem. I have two cluster nodes. Server are two HP Proliant DL 580 G4 with four Quad Core Intel(R) Xeon(R) CPU E7330 @ 2.40GHz. I'm running debian squeeze in dom0s end domUs. xm info: host : xen-p01 release : 2.6.32-5-xen-amd64 version : #1 SMP Sun May 6 08:57:29 UTC 2012 machine : x86_64 nr_cpus : 16 nr_nodes : 1 cores_per_socket : 4 threads_per_core : 1 cpu_mhz : 2400 hw_caps : bfebfbff:20100800:00000000:00000940:0004e3bd:00000000:00000001:00000000 virt_caps : hvm total_memory : 65532 free_memory : 40317 node_to_cpu : node0:0-15 node_to_memory : node0:40317 node_to_dma32_mem : node0:3256 max_node_id : 0 xen_major : 4 xen_minor : 0 xen_extra : .1 xen_caps : xen-3.0-x86_64 xen-3.0-x86_32p hvm-3.0-x86_32 hvm-3.0-x86_32p hvm-3.0-x86_64 xen_scheduler : credit xen_pagesize : 4096 platform_params : virt_start=0xffff800000000000 xen_changeset : unavailable xen_commandline : placeholder dom0_mem=3072M loglvl=warning guest_loglvl=warning cc_compiler : gcc version 4.4.5 (Debian 4.4.5-8) cc_compile_by : ultrotter cc_compile_domain : debian.org cc_compile_date : Sat Sep 8 19:15:46 UTC 2012 xend_config_format : 4 I'm experiencing weekly a clock jump ahead of about 50 minutes on dom0. I'm seriously in trouble because it cause every time a reboot of one of the two nodes clusters. _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Thu Sep 27 15:55:57 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Thu, 27 Sep 2012 15:55:57 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1THGQP-0002JP-3a; Thu, 27 Sep 2012 15:54:53 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1THGQO-0002JC-B5 for xen-users@lists.xensource.com; Thu, 27 Sep 2012 15:54:52 +0000 Received: from [85.158.139.83:62399] by server-11.bemta-5.messagelabs.com id 44/CE-13866-BC674605; Thu, 27 Sep 2012 15:54:51 +0000 X-Env-Sender: mrsanna1@gmail.com X-Msg-Ref: server-12.tower-182.messagelabs.com!1348761289!32241157!1 X-Originating-IP: [209.85.212.43] X-SpamReason: No, hits=0.3 required=7.0 tests=ML_RADAR_SPEW_LINKS_14, RCVD_BY_IP,spamassassin: X-StarScan-Received: X-StarScan-Version: 6.6.1.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 1225 invoked from network); 27 Sep 2012 15:54:50 -0000 Received: from mail-vb0-f43.google.com (HELO mail-vb0-f43.google.com) (209.85.212.43) by server-12.tower-182.messagelabs.com with RC4-SHA encrypted SMTP; 27 Sep 2012 15:54:50 -0000 Received: by vbbfq11 with SMTP id fq11so2593218vbb.30 for ; Thu, 27 Sep 2012 08:54:49 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=KlG5w16g2rW49mskdLvsisNgmthetfkSy5RgMokk26A=; b=g16EFRwD7PKUsYfx2QpM7luT+KyKnRaZHnoIOcKXiRKTw9y71liglYH3/7O8CFzS7T Y96F9GlkLnN9RHw6juE55hOcCvCDVdOz/95N/X9LgK0e1hcFjwkWIdNHCtxbc6abZ4xI bsGxrcIb1iPck9n5Ej3Gtl06+eCKqUpli5YN6BmwIWPbgK8TZObQeHk4s8xjdLv+EcRt GDXprPYx9CeqEa+eOYJntMEO/5MshhzI2tvi9NHI5Y/m4hu1jtRKQTX4WD6lj3jtiob+ /7cIs80zPeU361VB5Quvdq/P/Gshopy6CcCAO07UPszrg6eTZeTRYYCCznv9bi2McBoi BY+g== MIME-Version: 1.0 Received: by 10.220.205.200 with SMTP id fr8mr2378179vcb.34.1348761288807; Thu, 27 Sep 2012 08:54:48 -0700 (PDT) Received: by 10.58.207.75 with HTTP; Thu, 27 Sep 2012 08:54:48 -0700 (PDT) In-Reply-To: References: <68c41dd8-9195-41b0-83d7-9242b8eff809@default> Date: Thu, 27 Sep 2012 17:54:48 +0200 Message-ID: From: Mauro To: Olivier Hanesse Cc: Dan Magenheimer , xen-devel@lists.xensource.com, Keir Fraser , Jeremy Fitzhardinge , Jan Beulich , Keir Fraser , Xen Users , Mark Adams Subject: Re: [Xen-users] [Xen-devel] Xen 4 TSC problems X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org On 28 February 2011 16:54, Olivier Hanesse wrote: > Yes this is what I mean. > I am glad to hear that it isn't a bad sign :) > I thought of a bad sign, because on system with "reliable TSC", this counter > is always 0. Hey men. I have exactly the same problem. I have two cluster nodes. Server are two HP Proliant DL 580 G4 with four Quad Core Intel(R) Xeon(R) CPU E7330 @ 2.40GHz. I'm running debian squeeze in dom0s end domUs. xm info: host : xen-p01 release : 2.6.32-5-xen-amd64 version : #1 SMP Sun May 6 08:57:29 UTC 2012 machine : x86_64 nr_cpus : 16 nr_nodes : 1 cores_per_socket : 4 threads_per_core : 1 cpu_mhz : 2400 hw_caps : bfebfbff:20100800:00000000:00000940:0004e3bd:00000000:00000001:00000000 virt_caps : hvm total_memory : 65532 free_memory : 40317 node_to_cpu : node0:0-15 node_to_memory : node0:40317 node_to_dma32_mem : node0:3256 max_node_id : 0 xen_major : 4 xen_minor : 0 xen_extra : .1 xen_caps : xen-3.0-x86_64 xen-3.0-x86_32p hvm-3.0-x86_32 hvm-3.0-x86_32p hvm-3.0-x86_64 xen_scheduler : credit xen_pagesize : 4096 platform_params : virt_start=0xffff800000000000 xen_changeset : unavailable xen_commandline : placeholder dom0_mem=3072M loglvl=warning guest_loglvl=warning cc_compiler : gcc version 4.4.5 (Debian 4.4.5-8) cc_compile_by : ultrotter cc_compile_domain : debian.org cc_compile_date : Sat Sep 8 19:15:46 UTC 2012 xend_config_format : 4 I'm experiencing weekly a clock jump ahead of about 50 minutes on dom0. I'm seriously in trouble because it cause every time a reboot of one of the two nodes clusters. _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Thu Sep 27 16:05:53 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Thu, 27 Sep 2012 16:05:53 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1THGaD-0003Vh-S5; Thu, 27 Sep 2012 16:05:01 +0000 Received: from mail27.messagelabs.com ([193.109.254.147]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1THGaC-0003V9-Kx for xen-users@lists.xen.org; Thu, 27 Sep 2012 16:05:00 +0000 X-Env-Sender: alk@ondore.com X-Msg-Ref: server-2.tower-27.messagelabs.com!1348761893!12598946!1 X-Originating-IP: [184.172.38.138] X-SpamReason: No, hits=0.0 required=7.0 tests= X-StarScan-Received: X-StarScan-Version: 6.6.1.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 4706 invoked from network); 27 Sep 2012 16:04:54 -0000 Received: from host0a.ondore-systems.com (HELO host0a.ondore-systems.com) (184.172.38.138) by server-2.tower-27.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 27 Sep 2012 16:04:54 -0000 Received: from [201.123.193.7] (port=39534 helo=mail.ondore.i) by host0a.ondore-systems.com with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.77) (envelope-from ) id 1THGa5-0001eO-3A for xen-users@lists.xen.org; Thu, 27 Sep 2012 11:04:53 -0500 Received: from [10.13.34.156] (alk-desktop.sys.ondore.i [10.13.34.156]) by mail.ondore.i (Postfix) with ESMTPSA id 6E8FDA00B for ; Thu, 27 Sep 2012 11:04:51 -0500 (CDT) Message-ID: <50647923.8060902@ondore.com> Date: Thu, 27 Sep 2012 11:04:51 -0500 From: Alexandre Kouznetsov User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:14.0) Gecko/20120714 Thunderbird/14.0 MIME-Version: 1.0 To: xen-users@lists.xen.org References: In-Reply-To: X-AntiAbuse: This header was added to track abuse, please include it with any abuse report X-AntiAbuse: Primary Hostname - host0a.ondore-systems.com X-AntiAbuse: Original Domain - lists.xen.org X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12] X-AntiAbuse: Sender Address Domain - ondore.com Subject: Re: [Xen-users] sparse to no sparse X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset="iso-8859-1"; Format="flowed" Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org Hi. El 26/09/12 17:43, Paras pradhan escribi=F3: > I have an old Xen para virt vm which I created using sparse file. Is > there any way to convert this vm image to non-sparse without shutting > down the vm?. I do not know the goal of doing such thing, so this maybe will work for = for you, or maybe not. You can try do this form within the VM, of course without shutting it = down. Make it to fill with garbage (or zeros, or whatever) the = unallocated space of it's FS. This way, you will force the undrlaying = sparse image file to occupy it's full length. "wipe unallocated space" are your keywords. -- = Alexandre Kouznetsov _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Thu Sep 27 16:05:53 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Thu, 27 Sep 2012 16:05:53 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1THGaD-0003Vh-S5; Thu, 27 Sep 2012 16:05:01 +0000 Received: from mail27.messagelabs.com ([193.109.254.147]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1THGaC-0003V9-Kx for xen-users@lists.xen.org; Thu, 27 Sep 2012 16:05:00 +0000 X-Env-Sender: alk@ondore.com X-Msg-Ref: server-2.tower-27.messagelabs.com!1348761893!12598946!1 X-Originating-IP: [184.172.38.138] X-SpamReason: No, hits=0.0 required=7.0 tests= X-StarScan-Received: X-StarScan-Version: 6.6.1.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 4706 invoked from network); 27 Sep 2012 16:04:54 -0000 Received: from host0a.ondore-systems.com (HELO host0a.ondore-systems.com) (184.172.38.138) by server-2.tower-27.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 27 Sep 2012 16:04:54 -0000 Received: from [201.123.193.7] (port=39534 helo=mail.ondore.i) by host0a.ondore-systems.com with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.77) (envelope-from ) id 1THGa5-0001eO-3A for xen-users@lists.xen.org; Thu, 27 Sep 2012 11:04:53 -0500 Received: from [10.13.34.156] (alk-desktop.sys.ondore.i [10.13.34.156]) by mail.ondore.i (Postfix) with ESMTPSA id 6E8FDA00B for ; Thu, 27 Sep 2012 11:04:51 -0500 (CDT) Message-ID: <50647923.8060902@ondore.com> Date: Thu, 27 Sep 2012 11:04:51 -0500 From: Alexandre Kouznetsov User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:14.0) Gecko/20120714 Thunderbird/14.0 MIME-Version: 1.0 To: xen-users@lists.xen.org References: In-Reply-To: X-AntiAbuse: This header was added to track abuse, please include it with any abuse report X-AntiAbuse: Primary Hostname - host0a.ondore-systems.com X-AntiAbuse: Original Domain - lists.xen.org X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12] X-AntiAbuse: Sender Address Domain - ondore.com Subject: Re: [Xen-users] sparse to no sparse X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset="iso-8859-1"; Format="flowed" Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org Hi. El 26/09/12 17:43, Paras pradhan escribi=F3: > I have an old Xen para virt vm which I created using sparse file. Is > there any way to convert this vm image to non-sparse without shutting > down the vm?. I do not know the goal of doing such thing, so this maybe will work for = for you, or maybe not. You can try do this form within the VM, of course without shutting it = down. Make it to fill with garbage (or zeros, or whatever) the = unallocated space of it's FS. This way, you will force the undrlaying = sparse image file to occupy it's full length. "wipe unallocated space" are your keywords. -- = Alexandre Kouznetsov _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Thu Sep 27 16:14:28 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Thu, 27 Sep 2012 16:14:28 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1THGie-0004B6-AM; Thu, 27 Sep 2012 16:13:44 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1THGic-0004Al-EH for xen-users@lists.xen.org; Thu, 27 Sep 2012 16:13:42 +0000 Received: from [85.158.143.99:12123] by server-2.bemta-4.messagelabs.com id FF/C1-06610-53B74605; Thu, 27 Sep 2012 16:13:41 +0000 X-Env-Sender: singapore.mr.teo.en.ming@gmail.com X-Msg-Ref: server-4.tower-216.messagelabs.com!1348762410!26743314!1 X-Originating-IP: [209.85.160.45] X-SpamReason: No, hits=0.3 required=7.0 tests=ML_RADAR_SPEW_LINKS_14, ML_RADAR_SPEW_LINKS_8,RCVD_BY_IP,spamassassin: ,async_handler: YXN5bmNfZGVsYXk6IDcwNDQ0NjcgKHRpbWVvdXQp\n X-StarScan-Received: X-StarScan-Version: 6.6.1.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 12541 invoked from network); 27 Sep 2012 16:13:32 -0000 Received: from mail-pb0-f45.google.com (HELO mail-pb0-f45.google.com) (209.85.160.45) by server-4.tower-216.messagelabs.com with RC4-SHA encrypted SMTP; 27 Sep 2012 16:13:32 -0000 Received: by pbbrp2 with SMTP id rp2so3960385pbb.32 for ; Thu, 27 Sep 2012 09:13:30 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:disposition-notification-to:date:from:user-agent :mime-version:to:subject:references:in-reply-to:content-type :content-transfer-encoding; bh=wFpnTG8LK1kuq6nC5q57RHTuObyYITBK3j2RAsDroxs=; b=F+inHybduULz/MKGLcsWCFxdPVSr4jd17HqC1l486TYMaZXVd8fhQJWg5VTnkg0zOM sa8z1Dp1xptacoq0kIuAyLPVqwL2m291rabhRB1HVUqx05+QSIVa2ENChrAQzXHnBHin UkMGwSxyGNai0uIEAsF49YkoVj7RBkrHKkMroND0wQycQPw1wr7AN+Pxk3MsQDl7awRA 4mkAmJXW8KW/2vfldSLSSkhg733A03DJ6kIh/ms4sTXeq4qKRWCCSt0br+8n6l5biHcR xOHvV/bBv1oJgg7Rk8H7l34QC68IWbrXHWxLbu5qMyxKSe9I7Lxfec8xchC0C9aUZA82 8w8Q== Received: by 10.66.77.40 with SMTP id p8mr10461161paw.78.1348762410398; Thu, 27 Sep 2012 09:13:30 -0700 (PDT) Received: from [192.168.1.2] (cm141.gamma206.maxonline.com.sg. [202.156.206.141]) by mx.google.com with ESMTPS id w4sm3923219pav.27.2012.09.27.09.13.27 (version=SSLv3 cipher=OTHER); Thu, 27 Sep 2012 09:13:29 -0700 (PDT) Message-ID: <50647B26.9080903@gmail.com> Date: Fri, 28 Sep 2012 00:13:26 +0800 From: "Teo En Ming (Zhang Enming)" User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:10.0.2) Gecko/20120216 Thunderbird/10.0.2 MIME-Version: 1.0 To: "Mikhail I. Izmestev" , "xen-users@lists.xen.org" , "xen-devel@lists.xen.org" , "Teo En Ming (Zhang Enming)" References: <50645166.2000200@gmail.com> In-Reply-To: <50645166.2000200@gmail.com> Subject: Re: [Xen-users] Success VGA passthrough on windows 7 x64 with Xen 4.2.1-pre X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset="us-ascii"; Format="flowed" Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org On 27/09/2012 21:15, Mikhail I. Izmestev wrote: > Hi, > > 27.09.2012 15:03, Dariusz Krempa wrote: >> I'm glad i can report that today i have 100% success with VGA >> passthrough on windows 7 64-bit. That nasty yellow triangle with error >> 43 disappeared and my GTX560 has 7.8 points in aero index, also Gpu-z >> and Cpu-z see vga card properly and unigine heaven benchmark have no >> problem with it. >> Now i have to figure which particular option let me to do this. Most >> likely it was turned off msi_translate in DomU config, but i will make >> more test and i will share with full information today later. Cause >> i'm newbie with Xen and linux if there is some particular information >> i can share with, then please tell me and i will try to do that. >> >> http://tinypic.com/r/33djtwz/6 > > One day before I have tried to do this without luck. > > My configuration: > MB: GA-Z77X-D3H with latest bios (F15) > CPU: core i5-2400 > two GPU GTX560 on 16x and 8x pcie ports (both works on 8x when two used). > > DomU: win7 x64 pro > > I have tried to do this with XCP 1.5b and XenServer 6.0 Free trial. > > There is dmesg for host: > [root@xenserver-render ~]# xe host-dmesg | grep -i virtualisation > (XEN) I/O virtualisation enabled > (XEN) - APIC MMIO access virtualisation > > I just have "nasty yellow triangle with error 43" :) > > So I'm interested in your experience and solution. > > Mikhail. > > _______________________________________________ > Xen-users mailing list > Xen-users@lists.xen.org > http://lists.xen.org/xen-users > Dear Dariusz Krempa, I am also interested in knowing how you get the "nasty yellow triangle with error 43" to disappear. In addition, may I know which guide did you follow in getting VGA passthrough to work 100%? Thank you very much. -- Yours sincerely, Mr. Teo En Ming (Zhang Enming) Singapore _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Thu Sep 27 16:14:28 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Thu, 27 Sep 2012 16:14:28 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1THGie-0004B6-AM; Thu, 27 Sep 2012 16:13:44 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1THGic-0004Al-EH for xen-users@lists.xen.org; Thu, 27 Sep 2012 16:13:42 +0000 Received: from [85.158.143.99:12123] by server-2.bemta-4.messagelabs.com id FF/C1-06610-53B74605; Thu, 27 Sep 2012 16:13:41 +0000 X-Env-Sender: singapore.mr.teo.en.ming@gmail.com X-Msg-Ref: server-4.tower-216.messagelabs.com!1348762410!26743314!1 X-Originating-IP: [209.85.160.45] X-SpamReason: No, hits=0.3 required=7.0 tests=ML_RADAR_SPEW_LINKS_14, ML_RADAR_SPEW_LINKS_8,RCVD_BY_IP,spamassassin: ,async_handler: YXN5bmNfZGVsYXk6IDcwNDQ0NjcgKHRpbWVvdXQp\n X-StarScan-Received: X-StarScan-Version: 6.6.1.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 12541 invoked from network); 27 Sep 2012 16:13:32 -0000 Received: from mail-pb0-f45.google.com (HELO mail-pb0-f45.google.com) (209.85.160.45) by server-4.tower-216.messagelabs.com with RC4-SHA encrypted SMTP; 27 Sep 2012 16:13:32 -0000 Received: by pbbrp2 with SMTP id rp2so3960385pbb.32 for ; Thu, 27 Sep 2012 09:13:30 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:disposition-notification-to:date:from:user-agent :mime-version:to:subject:references:in-reply-to:content-type :content-transfer-encoding; bh=wFpnTG8LK1kuq6nC5q57RHTuObyYITBK3j2RAsDroxs=; b=F+inHybduULz/MKGLcsWCFxdPVSr4jd17HqC1l486TYMaZXVd8fhQJWg5VTnkg0zOM sa8z1Dp1xptacoq0kIuAyLPVqwL2m291rabhRB1HVUqx05+QSIVa2ENChrAQzXHnBHin UkMGwSxyGNai0uIEAsF49YkoVj7RBkrHKkMroND0wQycQPw1wr7AN+Pxk3MsQDl7awRA 4mkAmJXW8KW/2vfldSLSSkhg733A03DJ6kIh/ms4sTXeq4qKRWCCSt0br+8n6l5biHcR xOHvV/bBv1oJgg7Rk8H7l34QC68IWbrXHWxLbu5qMyxKSe9I7Lxfec8xchC0C9aUZA82 8w8Q== Received: by 10.66.77.40 with SMTP id p8mr10461161paw.78.1348762410398; Thu, 27 Sep 2012 09:13:30 -0700 (PDT) Received: from [192.168.1.2] (cm141.gamma206.maxonline.com.sg. [202.156.206.141]) by mx.google.com with ESMTPS id w4sm3923219pav.27.2012.09.27.09.13.27 (version=SSLv3 cipher=OTHER); Thu, 27 Sep 2012 09:13:29 -0700 (PDT) Message-ID: <50647B26.9080903@gmail.com> Date: Fri, 28 Sep 2012 00:13:26 +0800 From: "Teo En Ming (Zhang Enming)" User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:10.0.2) Gecko/20120216 Thunderbird/10.0.2 MIME-Version: 1.0 To: "Mikhail I. Izmestev" , "xen-users@lists.xen.org" , "xen-devel@lists.xen.org" , "Teo En Ming (Zhang Enming)" References: <50645166.2000200@gmail.com> In-Reply-To: <50645166.2000200@gmail.com> Subject: Re: [Xen-users] Success VGA passthrough on windows 7 x64 with Xen 4.2.1-pre X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset="us-ascii"; Format="flowed" Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org On 27/09/2012 21:15, Mikhail I. Izmestev wrote: > Hi, > > 27.09.2012 15:03, Dariusz Krempa wrote: >> I'm glad i can report that today i have 100% success with VGA >> passthrough on windows 7 64-bit. That nasty yellow triangle with error >> 43 disappeared and my GTX560 has 7.8 points in aero index, also Gpu-z >> and Cpu-z see vga card properly and unigine heaven benchmark have no >> problem with it. >> Now i have to figure which particular option let me to do this. Most >> likely it was turned off msi_translate in DomU config, but i will make >> more test and i will share with full information today later. Cause >> i'm newbie with Xen and linux if there is some particular information >> i can share with, then please tell me and i will try to do that. >> >> http://tinypic.com/r/33djtwz/6 > > One day before I have tried to do this without luck. > > My configuration: > MB: GA-Z77X-D3H with latest bios (F15) > CPU: core i5-2400 > two GPU GTX560 on 16x and 8x pcie ports (both works on 8x when two used). > > DomU: win7 x64 pro > > I have tried to do this with XCP 1.5b and XenServer 6.0 Free trial. > > There is dmesg for host: > [root@xenserver-render ~]# xe host-dmesg | grep -i virtualisation > (XEN) I/O virtualisation enabled > (XEN) - APIC MMIO access virtualisation > > I just have "nasty yellow triangle with error 43" :) > > So I'm interested in your experience and solution. > > Mikhail. > > _______________________________________________ > Xen-users mailing list > Xen-users@lists.xen.org > http://lists.xen.org/xen-users > Dear Dariusz Krempa, I am also interested in knowing how you get the "nasty yellow triangle with error 43" to disappear. In addition, may I know which guide did you follow in getting VGA passthrough to work 100%? Thank you very much. -- Yours sincerely, Mr. Teo En Ming (Zhang Enming) Singapore _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Thu Sep 27 16:23:44 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Thu, 27 Sep 2012 16:23:44 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1THGrc-0004kd-KR; Thu, 27 Sep 2012 16:23:00 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1THGrb-0004kS-7J for xen-users@lists.xen.org; Thu, 27 Sep 2012 16:22:59 +0000 Received: from [85.158.138.51:24017] by server-9.bemta-3.messagelabs.com id 09/B1-20338-26D74605; Thu, 27 Sep 2012 16:22:58 +0000 X-Env-Sender: singapore.mr.teo.en.ming@gmail.com X-Msg-Ref: server-10.tower-174.messagelabs.com!1348762976!24628788!1 X-Originating-IP: [209.85.220.45] X-SpamReason: No, hits=0.3 required=7.0 tests=ML_RADAR_SPEW_LINKS_14, RCVD_BY_IP,spamassassin: X-StarScan-Received: X-StarScan-Version: 6.6.1.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 16646 invoked from network); 27 Sep 2012 16:22:57 -0000 Received: from mail-pa0-f45.google.com (HELO mail-pa0-f45.google.com) (209.85.220.45) by server-10.tower-174.messagelabs.com with RC4-SHA encrypted SMTP; 27 Sep 2012 16:22:57 -0000 Received: by padfb10 with SMTP id fb10so1528480pad.32 for ; Thu, 27 Sep 2012 09:22:55 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:disposition-notification-to:date:from:user-agent :mime-version:to:subject:content-type:content-transfer-encoding; bh=vaVoSvhSfhCHFQdfIO//O2Fb6BJ7acc7qspmrJLsqng=; b=vRdivEKhZjoIL/v2qTp5FbRkG7k7XOXijuitTvs7hYM0UchijrLvjMGdSj84yo73eu A5iCakQEox+vxs/KlWARr5z6Hv8Uo9fg9q+U8HO2ksiiCEG3DUqjC8qdqpn3l4A1B/U9 4GlH7GvTyzHMXVqPWgz/RhkfrcaFPd4sgqerUHpO/igZoU8fzSYRMnbTx2G59OTyEs90 P4i1s33M2+ZSvwWCR5XtSyLwsJSxrkH3HSzwlW3GDLe9YAKXGDM9npuP/l4NQIhb2uWq Pu+yeijjPjpfO3Kt712iNdM/5gudZK3n3cqfPK2EOMa28dzRecAYV+dEI3gKNt1IepEr tIcg== Received: by 10.68.234.7 with SMTP id ua7mr13097114pbc.91.1348762975587; Thu, 27 Sep 2012 09:22:55 -0700 (PDT) Received: from [192.168.1.2] (cm141.gamma206.maxonline.com.sg. [202.156.206.141]) by mx.google.com with ESMTPS id rr6sm4047140pbc.47.2012.09.27.09.22.53 (version=SSLv3 cipher=OTHER); Thu, 27 Sep 2012 09:22:55 -0700 (PDT) Message-ID: <50647D5C.9020201@gmail.com> Date: Fri, 28 Sep 2012 00:22:52 +0800 From: "Teo En Ming (Zhang Enming)" User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:10.0.2) Gecko/20120216 Thunderbird/10.0.2 MIME-Version: 1.0 To: "xen-users@lists.xen.org" , "Teo En Ming (Zhang Enming)" Subject: [Xen-users] Where do I hg clone xen-4.2-testing? X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset="us-ascii"; Format="flowed" Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org Hi, May I know where do I go to hg clone xen-4.2-testing? Could you please give me the URL? Thank you very much. -- Yours sincerely, Mr. Teo En Ming (Zhang Enming) Singapore _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Thu Sep 27 16:23:44 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Thu, 27 Sep 2012 16:23:44 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1THGrc-0004kd-KR; Thu, 27 Sep 2012 16:23:00 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1THGrb-0004kS-7J for xen-users@lists.xen.org; Thu, 27 Sep 2012 16:22:59 +0000 Received: from [85.158.138.51:24017] by server-9.bemta-3.messagelabs.com id 09/B1-20338-26D74605; Thu, 27 Sep 2012 16:22:58 +0000 X-Env-Sender: singapore.mr.teo.en.ming@gmail.com X-Msg-Ref: server-10.tower-174.messagelabs.com!1348762976!24628788!1 X-Originating-IP: [209.85.220.45] X-SpamReason: No, hits=0.3 required=7.0 tests=ML_RADAR_SPEW_LINKS_14, RCVD_BY_IP,spamassassin: X-StarScan-Received: X-StarScan-Version: 6.6.1.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 16646 invoked from network); 27 Sep 2012 16:22:57 -0000 Received: from mail-pa0-f45.google.com (HELO mail-pa0-f45.google.com) (209.85.220.45) by server-10.tower-174.messagelabs.com with RC4-SHA encrypted SMTP; 27 Sep 2012 16:22:57 -0000 Received: by padfb10 with SMTP id fb10so1528480pad.32 for ; Thu, 27 Sep 2012 09:22:55 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:disposition-notification-to:date:from:user-agent :mime-version:to:subject:content-type:content-transfer-encoding; bh=vaVoSvhSfhCHFQdfIO//O2Fb6BJ7acc7qspmrJLsqng=; b=vRdivEKhZjoIL/v2qTp5FbRkG7k7XOXijuitTvs7hYM0UchijrLvjMGdSj84yo73eu A5iCakQEox+vxs/KlWARr5z6Hv8Uo9fg9q+U8HO2ksiiCEG3DUqjC8qdqpn3l4A1B/U9 4GlH7GvTyzHMXVqPWgz/RhkfrcaFPd4sgqerUHpO/igZoU8fzSYRMnbTx2G59OTyEs90 P4i1s33M2+ZSvwWCR5XtSyLwsJSxrkH3HSzwlW3GDLe9YAKXGDM9npuP/l4NQIhb2uWq Pu+yeijjPjpfO3Kt712iNdM/5gudZK3n3cqfPK2EOMa28dzRecAYV+dEI3gKNt1IepEr tIcg== Received: by 10.68.234.7 with SMTP id ua7mr13097114pbc.91.1348762975587; Thu, 27 Sep 2012 09:22:55 -0700 (PDT) Received: from [192.168.1.2] (cm141.gamma206.maxonline.com.sg. [202.156.206.141]) by mx.google.com with ESMTPS id rr6sm4047140pbc.47.2012.09.27.09.22.53 (version=SSLv3 cipher=OTHER); Thu, 27 Sep 2012 09:22:55 -0700 (PDT) Message-ID: <50647D5C.9020201@gmail.com> Date: Fri, 28 Sep 2012 00:22:52 +0800 From: "Teo En Ming (Zhang Enming)" User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:10.0.2) Gecko/20120216 Thunderbird/10.0.2 MIME-Version: 1.0 To: "xen-users@lists.xen.org" , "Teo En Ming (Zhang Enming)" Subject: [Xen-users] Where do I hg clone xen-4.2-testing? X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset="us-ascii"; Format="flowed" Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org Hi, May I know where do I go to hg clone xen-4.2-testing? Could you please give me the URL? Thank you very much. -- Yours sincerely, Mr. Teo En Ming (Zhang Enming) Singapore _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Thu Sep 27 16:41:16 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Thu, 27 Sep 2012 16:41:16 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1THH8g-0005Pv-Sp; Thu, 27 Sep 2012 16:40:38 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1THH8f-0005Pq-Bu for xen-users@lists.xen.org; Thu, 27 Sep 2012 16:40:37 +0000 Received: from [85.158.143.99:35306] by server-3.bemta-4.messagelabs.com id 0E/9E-10986-48184605; Thu, 27 Sep 2012 16:40:36 +0000 X-Env-Sender: singapore.mr.teo.en.ming@gmail.com X-Msg-Ref: server-15.tower-216.messagelabs.com!1348764034!32020170!1 X-Originating-IP: [209.85.220.45] X-SpamReason: No, hits=0.3 required=7.0 tests=ML_RADAR_SPEW_LINKS_14, RCVD_BY_IP,spamassassin: X-StarScan-Received: X-StarScan-Version: 6.6.1.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 431 invoked from network); 27 Sep 2012 16:40:35 -0000 Received: from mail-pa0-f45.google.com (HELO mail-pa0-f45.google.com) (209.85.220.45) by server-15.tower-216.messagelabs.com with RC4-SHA encrypted SMTP; 27 Sep 2012 16:40:35 -0000 Received: by padfb10 with SMTP id fb10so1542438pad.32 for ; Thu, 27 Sep 2012 09:40:33 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:disposition-notification-to:date:from:user-agent :mime-version:to:subject:references:in-reply-to:content-type :content-transfer-encoding; bh=zeG4j1mm/Nw16UJKJjDQEvh0JaTkwkFVngvfJZHVkg0=; b=ybZF2WFT3mzIBJBO2lHd43kmBuN0IwAQ5Atunb9k4Caz2jtGW7anQFzfXIggKgUWdL ny0YTZ+ljE6kQTWkmvAFKcpDvjyGTSv5gaQf+HzIcugcWvxzwVpzExMKa1zpBre6Fn6M UoXR8DGSVqTyGy6vLkqkoVDSU9eYdM7d3faj/6KCtl1wQ+EXQbrV/hKv2HWNulNi0bBF rVfjiL9RIvnxiqAxx946ADNn1JCL73CHWBdlVIYMYuM0eQ3qzO3hP1ZMl8xG1PdmZAZW XUzxBN/aL8M/QhwruA9huDF4FqHm/I/QhhHkFhQAOt7zZMaWFfa/lYs4Ej8mcy2mTCUy wcxA== Received: by 10.66.72.134 with SMTP id d6mr10824069pav.13.1348764033497; Thu, 27 Sep 2012 09:40:33 -0700 (PDT) Received: from [192.168.1.2] (cm141.gamma206.maxonline.com.sg. [202.156.206.141]) by mx.google.com with ESMTPS id bt7sm3964687pab.14.2012.09.27.09.40.31 (version=SSLv3 cipher=OTHER); Thu, 27 Sep 2012 09:40:32 -0700 (PDT) Message-ID: <5064817D.9040105@gmail.com> Date: Fri, 28 Sep 2012 00:40:29 +0800 From: "Teo En Ming (Zhang Enming)" User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:10.0.2) Gecko/20120216 Thunderbird/10.0.2 MIME-Version: 1.0 To: "Teo En Ming (Zhang Enming)" , "xen-users@lists.xen.org" References: <50647D5C.9020201@gmail.com> In-Reply-To: <50647D5C.9020201@gmail.com> Subject: Re: [Xen-users] Where do I hg clone xen-4.2-testing? X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset="us-ascii"; Format="flowed" Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org On 28/09/2012 00:22, Teo En Ming (Zhang Enming) wrote: > Hi, > > May I know where do I go to hg clone xen-4.2-testing? Could you please > give me the URL? > > Thank you very much. > Never mind, I have already found out the URL. http://xenbits.xen.org/hg/xen-4.2-testing.hg -- Yours sincerely, Mr. Teo En Ming (Zhang Enming) Singapore _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Thu Sep 27 16:41:16 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Thu, 27 Sep 2012 16:41:16 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1THH8g-0005Pv-Sp; Thu, 27 Sep 2012 16:40:38 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1THH8f-0005Pq-Bu for xen-users@lists.xen.org; Thu, 27 Sep 2012 16:40:37 +0000 Received: from [85.158.143.99:35306] by server-3.bemta-4.messagelabs.com id 0E/9E-10986-48184605; Thu, 27 Sep 2012 16:40:36 +0000 X-Env-Sender: singapore.mr.teo.en.ming@gmail.com X-Msg-Ref: server-15.tower-216.messagelabs.com!1348764034!32020170!1 X-Originating-IP: [209.85.220.45] X-SpamReason: No, hits=0.3 required=7.0 tests=ML_RADAR_SPEW_LINKS_14, RCVD_BY_IP,spamassassin: X-StarScan-Received: X-StarScan-Version: 6.6.1.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 431 invoked from network); 27 Sep 2012 16:40:35 -0000 Received: from mail-pa0-f45.google.com (HELO mail-pa0-f45.google.com) (209.85.220.45) by server-15.tower-216.messagelabs.com with RC4-SHA encrypted SMTP; 27 Sep 2012 16:40:35 -0000 Received: by padfb10 with SMTP id fb10so1542438pad.32 for ; Thu, 27 Sep 2012 09:40:33 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:disposition-notification-to:date:from:user-agent :mime-version:to:subject:references:in-reply-to:content-type :content-transfer-encoding; bh=zeG4j1mm/Nw16UJKJjDQEvh0JaTkwkFVngvfJZHVkg0=; b=ybZF2WFT3mzIBJBO2lHd43kmBuN0IwAQ5Atunb9k4Caz2jtGW7anQFzfXIggKgUWdL ny0YTZ+ljE6kQTWkmvAFKcpDvjyGTSv5gaQf+HzIcugcWvxzwVpzExMKa1zpBre6Fn6M UoXR8DGSVqTyGy6vLkqkoVDSU9eYdM7d3faj/6KCtl1wQ+EXQbrV/hKv2HWNulNi0bBF rVfjiL9RIvnxiqAxx946ADNn1JCL73CHWBdlVIYMYuM0eQ3qzO3hP1ZMl8xG1PdmZAZW XUzxBN/aL8M/QhwruA9huDF4FqHm/I/QhhHkFhQAOt7zZMaWFfa/lYs4Ej8mcy2mTCUy wcxA== Received: by 10.66.72.134 with SMTP id d6mr10824069pav.13.1348764033497; Thu, 27 Sep 2012 09:40:33 -0700 (PDT) Received: from [192.168.1.2] (cm141.gamma206.maxonline.com.sg. [202.156.206.141]) by mx.google.com with ESMTPS id bt7sm3964687pab.14.2012.09.27.09.40.31 (version=SSLv3 cipher=OTHER); Thu, 27 Sep 2012 09:40:32 -0700 (PDT) Message-ID: <5064817D.9040105@gmail.com> Date: Fri, 28 Sep 2012 00:40:29 +0800 From: "Teo En Ming (Zhang Enming)" User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:10.0.2) Gecko/20120216 Thunderbird/10.0.2 MIME-Version: 1.0 To: "Teo En Ming (Zhang Enming)" , "xen-users@lists.xen.org" References: <50647D5C.9020201@gmail.com> In-Reply-To: <50647D5C.9020201@gmail.com> Subject: Re: [Xen-users] Where do I hg clone xen-4.2-testing? X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset="us-ascii"; Format="flowed" Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org On 28/09/2012 00:22, Teo En Ming (Zhang Enming) wrote: > Hi, > > May I know where do I go to hg clone xen-4.2-testing? Could you please > give me the URL? > > Thank you very much. > Never mind, I have already found out the URL. http://xenbits.xen.org/hg/xen-4.2-testing.hg -- Yours sincerely, Mr. Teo En Ming (Zhang Enming) Singapore _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Thu Sep 27 16:52:52 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Thu, 27 Sep 2012 16:52:52 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1THHJs-0005o0-As; Thu, 27 Sep 2012 16:52:12 +0000 Received: from mail27.messagelabs.com ([193.109.254.147]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1THHJr-0005nk-5N; Thu, 27 Sep 2012 16:52:11 +0000 X-Env-Sender: imperiaonline4@gmail.com X-Msg-Ref: server-8.tower-27.messagelabs.com!1348764723!9321948!1 X-Originating-IP: [209.85.214.173] X-SpamReason: No, hits=0.3 required=7.0 tests=ML_RADAR_SPEW_LINKS_14, RCVD_BY_IP,spamassassin: X-StarScan-Received: X-StarScan-Version: 6.6.1.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 31901 invoked from network); 27 Sep 2012 16:52:04 -0000 Received: from mail-ob0-f173.google.com (HELO mail-ob0-f173.google.com) (209.85.214.173) by server-8.tower-27.messagelabs.com with RC4-SHA encrypted SMTP; 27 Sep 2012 16:52:04 -0000 Received: by obbta14 with SMTP id ta14so2672212obb.32 for ; Thu, 27 Sep 2012 09:52:03 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; bh=R1ba6vW1QaAyIOlAiMT/UQjOLVEfTm4gsTR43NC6gpU=; b=VbuMkWBbul5+bKtxsDTXHo3oxDnRe45Bk9S9q1jK+/+6S/gsBs+znYj5ICPqQG88kI igdgS2LJC+AlWrbn/kSdpCwhFPwPv38knqB+4/qYGQ3vUBI+jwRCddeivYuxbuv9VtJG 6q4PSkh4LyzXdbsmN+OAHGWFkR9g/dOn/e/2VxLiCTwWihLG91AXcSYYP/m5zMO+Xcy/ QSN1rOavEEt+GK+58/tx5TGElSoNixeQEOyVAMdVBigfWcetVa+VJ+7C/5UU9yThaCbq XbsjW5l/yW2Y0GORYRRJPlESxqz4Hp0etWMOsJF27VrOJq+AjP7Qzg1O0ALAqUoivHbR hK8g== MIME-Version: 1.0 Received: by 10.182.172.74 with SMTP id ba10mr3600591obc.83.1348764723170; Thu, 27 Sep 2012 09:52:03 -0700 (PDT) Received: by 10.60.146.236 with HTTP; Thu, 27 Sep 2012 09:52:03 -0700 (PDT) In-Reply-To: <50647B26.9080903@gmail.com> References: <50645166.2000200@gmail.com> <50647B26.9080903@gmail.com> Date: Thu, 27 Sep 2012 18:52:03 +0200 Message-ID: From: Dariusz Krempa To: "xen-users@lists.xen.org" , "xen-devel@lists.xen.org" Subject: Re: [Xen-users] Success VGA passthrough on windows 7 x64 with Xen 4.2.1-pre X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org > Dear Dariusz Krempa, > > I am also interested in knowing how you get the "nasty yellow triangle with > error 43" to disappear. > > In addition, may I know which guide did you follow in getting VGA > passthrough to work 100%? > > Thank you very much. > > -- > Yours sincerely, > > Mr. Teo En Ming (Zhang Enming) > Singapore > > > > _______________________________________________ > Xen-users mailing list > Xen-users@lists.xen.org > http://lists.xen.org/xen-users I started with guide from You dated 25 march 2012 to build Dom0 and Xen 4.2, but with few modifications this time. 1) I used kernel 3.6-rc7 for Dom0 --> http://kernel.org/pub/linux/kernel/v3.x/testing/linux-3.6-rc7.tar.bz2 2) I used Xen from http://xenbits.xen.org/hg/staging/xen-unstable.hg/ 3) VGA patch from David's Gis rev 25240 4) I used pciback to hide my gtx560 from Dom0, and for a while i have had second gfx - hd4850, but now i removed it and i have only gtx560, still working and finally I think I know what make that error 43 disappeared. At first I did comment those lines in DomU config: #pci_msitranslate = 1 #pci_power_mgmt = 1 #xen_platform_pci=1 #xen_extended_power_mgmt=1 When i had success with installation i start to remove comments and the one which is nasty is pci_msitranslate. This make some other problems, like not working USB ports, but ... If any other information will be needed please let me know. Hardware: asus P8H67 asus GTX560 DCII top 4GB ram System: ubuntu 12.04 Dom0 kernel 3.6-rc7 DomU windows 7 x64 nvidia drivers 275.33 - but possibly 275.50 also will work _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Thu Sep 27 16:52:52 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Thu, 27 Sep 2012 16:52:52 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1THHJs-0005o0-As; Thu, 27 Sep 2012 16:52:12 +0000 Received: from mail27.messagelabs.com ([193.109.254.147]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1THHJr-0005nk-5N; Thu, 27 Sep 2012 16:52:11 +0000 X-Env-Sender: imperiaonline4@gmail.com X-Msg-Ref: server-8.tower-27.messagelabs.com!1348764723!9321948!1 X-Originating-IP: [209.85.214.173] X-SpamReason: No, hits=0.3 required=7.0 tests=ML_RADAR_SPEW_LINKS_14, RCVD_BY_IP,spamassassin: X-StarScan-Received: X-StarScan-Version: 6.6.1.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 31901 invoked from network); 27 Sep 2012 16:52:04 -0000 Received: from mail-ob0-f173.google.com (HELO mail-ob0-f173.google.com) (209.85.214.173) by server-8.tower-27.messagelabs.com with RC4-SHA encrypted SMTP; 27 Sep 2012 16:52:04 -0000 Received: by obbta14 with SMTP id ta14so2672212obb.32 for ; Thu, 27 Sep 2012 09:52:03 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; bh=R1ba6vW1QaAyIOlAiMT/UQjOLVEfTm4gsTR43NC6gpU=; b=VbuMkWBbul5+bKtxsDTXHo3oxDnRe45Bk9S9q1jK+/+6S/gsBs+znYj5ICPqQG88kI igdgS2LJC+AlWrbn/kSdpCwhFPwPv38knqB+4/qYGQ3vUBI+jwRCddeivYuxbuv9VtJG 6q4PSkh4LyzXdbsmN+OAHGWFkR9g/dOn/e/2VxLiCTwWihLG91AXcSYYP/m5zMO+Xcy/ QSN1rOavEEt+GK+58/tx5TGElSoNixeQEOyVAMdVBigfWcetVa+VJ+7C/5UU9yThaCbq XbsjW5l/yW2Y0GORYRRJPlESxqz4Hp0etWMOsJF27VrOJq+AjP7Qzg1O0ALAqUoivHbR hK8g== MIME-Version: 1.0 Received: by 10.182.172.74 with SMTP id ba10mr3600591obc.83.1348764723170; Thu, 27 Sep 2012 09:52:03 -0700 (PDT) Received: by 10.60.146.236 with HTTP; Thu, 27 Sep 2012 09:52:03 -0700 (PDT) In-Reply-To: <50647B26.9080903@gmail.com> References: <50645166.2000200@gmail.com> <50647B26.9080903@gmail.com> Date: Thu, 27 Sep 2012 18:52:03 +0200 Message-ID: From: Dariusz Krempa To: "xen-users@lists.xen.org" , "xen-devel@lists.xen.org" Subject: Re: [Xen-users] Success VGA passthrough on windows 7 x64 with Xen 4.2.1-pre X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org > Dear Dariusz Krempa, > > I am also interested in knowing how you get the "nasty yellow triangle with > error 43" to disappear. > > In addition, may I know which guide did you follow in getting VGA > passthrough to work 100%? > > Thank you very much. > > -- > Yours sincerely, > > Mr. Teo En Ming (Zhang Enming) > Singapore > > > > _______________________________________________ > Xen-users mailing list > Xen-users@lists.xen.org > http://lists.xen.org/xen-users I started with guide from You dated 25 march 2012 to build Dom0 and Xen 4.2, but with few modifications this time. 1) I used kernel 3.6-rc7 for Dom0 --> http://kernel.org/pub/linux/kernel/v3.x/testing/linux-3.6-rc7.tar.bz2 2) I used Xen from http://xenbits.xen.org/hg/staging/xen-unstable.hg/ 3) VGA patch from David's Gis rev 25240 4) I used pciback to hide my gtx560 from Dom0, and for a while i have had second gfx - hd4850, but now i removed it and i have only gtx560, still working and finally I think I know what make that error 43 disappeared. At first I did comment those lines in DomU config: #pci_msitranslate = 1 #pci_power_mgmt = 1 #xen_platform_pci=1 #xen_extended_power_mgmt=1 When i had success with installation i start to remove comments and the one which is nasty is pci_msitranslate. This make some other problems, like not working USB ports, but ... If any other information will be needed please let me know. Hardware: asus P8H67 asus GTX560 DCII top 4GB ram System: ubuntu 12.04 Dom0 kernel 3.6-rc7 DomU windows 7 x64 nvidia drivers 275.33 - but possibly 275.50 also will work _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Thu Sep 27 17:30:12 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Thu, 27 Sep 2012 17:30:12 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1THHtt-00083b-21; Thu, 27 Sep 2012 17:29:25 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1THHtq-00083W-R7 for xen-users@lists.xen.org; Thu, 27 Sep 2012 17:29:23 +0000 Received: from [85.158.138.51:43420] by server-6.bemta-3.messagelabs.com id 5B/0A-11085-1FC84605; Thu, 27 Sep 2012 17:29:21 +0000 X-Env-Sender: singapore.mr.teo.en.ming@gmail.com X-Msg-Ref: server-8.tower-174.messagelabs.com!1348766959!32197580!1 X-Originating-IP: [209.85.160.45] X-SpamReason: No, hits=0.3 required=7.0 tests=ML_RADAR_SPEW_LINKS_14, RCVD_BY_IP,spamassassin: X-StarScan-Received: X-StarScan-Version: 6.6.1.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 29763 invoked from network); 27 Sep 2012 17:29:20 -0000 Received: from mail-pb0-f45.google.com (HELO mail-pb0-f45.google.com) (209.85.160.45) by server-8.tower-174.messagelabs.com with RC4-SHA encrypted SMTP; 27 Sep 2012 17:29:20 -0000 Received: by pbbrp2 with SMTP id rp2so4058431pbb.32 for ; Thu, 27 Sep 2012 10:29:18 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:disposition-notification-to:date:from:user-agent :mime-version:to:subject:references:in-reply-to:content-type :content-transfer-encoding; bh=GHEZnAXyFEKFQmNyCqgSZ/R5QcPXYYLTS6fDtp5AH4U=; b=L4daXIMNRFYQvjil4DWKWZSjvZAle2TQvG5PPOjjw39rwpQLX1TP9ter9sbyD2d5xX jh2iZ/eyZFe/4iQ377y6z3+ZrH5tHlKDVgx8daVtZ+XbMwjulekj/+GnQoA4jOz2EhFH D2F3UExwLkE4EIs638Fe5jqREEuDiVVbJv3trPCF9XtAp/nYACoZAarwIdHxuSe8aPQG ysAJyHdmCVCT1dAHnujSUgvrkcpLXfL7P897dn4zEs9PGoXqzniY93SBTU1tbqS9Ia4+ AGeFoQs0bcL86nSfgYiBIgefykhoewaFb3q+svuwUp2AqLCwJrK+gIAs5cto6kYH5ROR r2EQ== Received: by 10.66.74.74 with SMTP id r10mr11162943pav.57.1348766958439; Thu, 27 Sep 2012 10:29:18 -0700 (PDT) Received: from [192.168.1.2] (cm141.gamma206.maxonline.com.sg. [202.156.206.141]) by mx.google.com with ESMTPS id uz3sm4133366pbc.19.2012.09.27.10.29.15 (version=SSLv3 cipher=OTHER); Thu, 27 Sep 2012 10:29:17 -0700 (PDT) Message-ID: <50648CEA.9070107@gmail.com> Date: Fri, 28 Sep 2012 01:29:14 +0800 From: "Teo En Ming (Zhang Enming)" User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:10.0.2) Gecko/20120216 Thunderbird/10.0.2 MIME-Version: 1.0 To: Dariusz Krempa , "xen-users@lists.xen.org" , "Teo En Ming (Zhang Enming)" References: <50645166.2000200@gmail.com> <50647B26.9080903@gmail.com> In-Reply-To: Subject: Re: [Xen-users] Success VGA passthrough on windows 7 x64 with Xen 4.2.1-pre X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset="us-ascii"; Format="flowed" Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org On 28/09/2012 00:52, Dariusz Krempa wrote: >> Dear Dariusz Krempa, >> >> I am also interested in knowing how you get the "nasty yellow triangle with >> error 43" to disappear. >> >> In addition, may I know which guide did you follow in getting VGA >> passthrough to work 100%? >> >> Thank you very much. >> >> -- >> Yours sincerely, >> >> Mr. Teo En Ming (Zhang Enming) >> Singapore >> >> >> >> _______________________________________________ >> Xen-users mailing list >> Xen-users@lists.xen.org >> http://lists.xen.org/xen-users > I started with guide from You dated 25 march 2012 to build Dom0 and > Xen 4.2, but with few modifications this time. > 1) I used kernel 3.6-rc7 for Dom0 --> > http://kernel.org/pub/linux/kernel/v3.x/testing/linux-3.6-rc7.tar.bz2 > 2) I used Xen from http://xenbits.xen.org/hg/staging/xen-unstable.hg/ > 3) VGA patch from David's Gis rev 25240 > 4) I used pciback to hide my gtx560 from Dom0, and for a while i have > had second gfx - hd4850, but now i removed it and i have only gtx560, > still working > > and finally I think I know what make that error 43 disappeared. At > first I did comment those lines in DomU config: > > #pci_msitranslate = 1 > #pci_power_mgmt = 1 > #xen_platform_pci=1 > #xen_extended_power_mgmt=1 > > When i had success with installation i start to remove comments and > the one which is nasty is pci_msitranslate. This make some other > problems, like not working USB ports, but ... > > If any other information will be needed please let me know. > > Hardware: > asus P8H67 > asus GTX560 DCII top > 4GB ram > > System: > ubuntu 12.04 > Dom0 kernel 3.6-rc7 > DomU windows 7 x64 > nvidia drivers 275.33 - but possibly 275.50 also will work > > _______________________________________________ > Xen-users mailing list > Xen-users@lists.xen.org > http://lists.xen.org/xen-users > Dear Dariusz Krempa, Thank you for your prompt reply. I don't have pci_msitranslate = 1 in my Windows HVM domU config file, so I don't think "pci_msitranslate = 1" is the main cause of my "nasty yellow triangle with error 43". -- Yours sincerely, Mr. Teo En Ming (Zhang Enming) Singapore _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Thu Sep 27 17:30:12 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Thu, 27 Sep 2012 17:30:12 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1THHtt-00083b-21; Thu, 27 Sep 2012 17:29:25 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1THHtq-00083W-R7 for xen-users@lists.xen.org; Thu, 27 Sep 2012 17:29:23 +0000 Received: from [85.158.138.51:43420] by server-6.bemta-3.messagelabs.com id 5B/0A-11085-1FC84605; Thu, 27 Sep 2012 17:29:21 +0000 X-Env-Sender: singapore.mr.teo.en.ming@gmail.com X-Msg-Ref: server-8.tower-174.messagelabs.com!1348766959!32197580!1 X-Originating-IP: [209.85.160.45] X-SpamReason: No, hits=0.3 required=7.0 tests=ML_RADAR_SPEW_LINKS_14, RCVD_BY_IP,spamassassin: X-StarScan-Received: X-StarScan-Version: 6.6.1.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 29763 invoked from network); 27 Sep 2012 17:29:20 -0000 Received: from mail-pb0-f45.google.com (HELO mail-pb0-f45.google.com) (209.85.160.45) by server-8.tower-174.messagelabs.com with RC4-SHA encrypted SMTP; 27 Sep 2012 17:29:20 -0000 Received: by pbbrp2 with SMTP id rp2so4058431pbb.32 for ; Thu, 27 Sep 2012 10:29:18 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:disposition-notification-to:date:from:user-agent :mime-version:to:subject:references:in-reply-to:content-type :content-transfer-encoding; bh=GHEZnAXyFEKFQmNyCqgSZ/R5QcPXYYLTS6fDtp5AH4U=; b=L4daXIMNRFYQvjil4DWKWZSjvZAle2TQvG5PPOjjw39rwpQLX1TP9ter9sbyD2d5xX jh2iZ/eyZFe/4iQ377y6z3+ZrH5tHlKDVgx8daVtZ+XbMwjulekj/+GnQoA4jOz2EhFH D2F3UExwLkE4EIs638Fe5jqREEuDiVVbJv3trPCF9XtAp/nYACoZAarwIdHxuSe8aPQG ysAJyHdmCVCT1dAHnujSUgvrkcpLXfL7P897dn4zEs9PGoXqzniY93SBTU1tbqS9Ia4+ AGeFoQs0bcL86nSfgYiBIgefykhoewaFb3q+svuwUp2AqLCwJrK+gIAs5cto6kYH5ROR r2EQ== Received: by 10.66.74.74 with SMTP id r10mr11162943pav.57.1348766958439; Thu, 27 Sep 2012 10:29:18 -0700 (PDT) Received: from [192.168.1.2] (cm141.gamma206.maxonline.com.sg. [202.156.206.141]) by mx.google.com with ESMTPS id uz3sm4133366pbc.19.2012.09.27.10.29.15 (version=SSLv3 cipher=OTHER); Thu, 27 Sep 2012 10:29:17 -0700 (PDT) Message-ID: <50648CEA.9070107@gmail.com> Date: Fri, 28 Sep 2012 01:29:14 +0800 From: "Teo En Ming (Zhang Enming)" User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:10.0.2) Gecko/20120216 Thunderbird/10.0.2 MIME-Version: 1.0 To: Dariusz Krempa , "xen-users@lists.xen.org" , "Teo En Ming (Zhang Enming)" References: <50645166.2000200@gmail.com> <50647B26.9080903@gmail.com> In-Reply-To: Subject: Re: [Xen-users] Success VGA passthrough on windows 7 x64 with Xen 4.2.1-pre X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset="us-ascii"; Format="flowed" Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org On 28/09/2012 00:52, Dariusz Krempa wrote: >> Dear Dariusz Krempa, >> >> I am also interested in knowing how you get the "nasty yellow triangle with >> error 43" to disappear. >> >> In addition, may I know which guide did you follow in getting VGA >> passthrough to work 100%? >> >> Thank you very much. >> >> -- >> Yours sincerely, >> >> Mr. Teo En Ming (Zhang Enming) >> Singapore >> >> >> >> _______________________________________________ >> Xen-users mailing list >> Xen-users@lists.xen.org >> http://lists.xen.org/xen-users > I started with guide from You dated 25 march 2012 to build Dom0 and > Xen 4.2, but with few modifications this time. > 1) I used kernel 3.6-rc7 for Dom0 --> > http://kernel.org/pub/linux/kernel/v3.x/testing/linux-3.6-rc7.tar.bz2 > 2) I used Xen from http://xenbits.xen.org/hg/staging/xen-unstable.hg/ > 3) VGA patch from David's Gis rev 25240 > 4) I used pciback to hide my gtx560 from Dom0, and for a while i have > had second gfx - hd4850, but now i removed it and i have only gtx560, > still working > > and finally I think I know what make that error 43 disappeared. At > first I did comment those lines in DomU config: > > #pci_msitranslate = 1 > #pci_power_mgmt = 1 > #xen_platform_pci=1 > #xen_extended_power_mgmt=1 > > When i had success with installation i start to remove comments and > the one which is nasty is pci_msitranslate. This make some other > problems, like not working USB ports, but ... > > If any other information will be needed please let me know. > > Hardware: > asus P8H67 > asus GTX560 DCII top > 4GB ram > > System: > ubuntu 12.04 > Dom0 kernel 3.6-rc7 > DomU windows 7 x64 > nvidia drivers 275.33 - but possibly 275.50 also will work > > _______________________________________________ > Xen-users mailing list > Xen-users@lists.xen.org > http://lists.xen.org/xen-users > Dear Dariusz Krempa, Thank you for your prompt reply. I don't have pci_msitranslate = 1 in my Windows HVM domU config file, so I don't think "pci_msitranslate = 1" is the main cause of my "nasty yellow triangle with error 43". -- Yours sincerely, Mr. Teo En Ming (Zhang Enming) Singapore _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Thu Sep 27 17:59:21 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Thu, 27 Sep 2012 17:59:21 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1THIM0-0000Aa-PJ; Thu, 27 Sep 2012 17:58:28 +0000 Received: from mail27.messagelabs.com ([193.109.254.147]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1THIM0-0000AV-2M for xen-users@lists.xen.org; Thu, 27 Sep 2012 17:58:28 +0000 X-Env-Sender: imperiaonline4@gmail.com X-Msg-Ref: server-12.tower-27.messagelabs.com!1348768699!12638711!1 X-Originating-IP: [209.85.214.169] X-SpamReason: No, hits=0.8 required=7.0 tests=BODY_RANDOM_LONG, ML_RADAR_SPEW_LINKS_14,RCVD_BY_IP,spamassassin: X-StarScan-Received: X-StarScan-Version: 6.6.1.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 21135 invoked from network); 27 Sep 2012 17:58:21 -0000 Received: from mail-ob0-f169.google.com (HELO mail-ob0-f169.google.com) (209.85.214.169) by server-12.tower-27.messagelabs.com with RC4-SHA encrypted SMTP; 27 Sep 2012 17:58:21 -0000 Received: by obcva7 with SMTP id va7so2029940obc.28 for ; Thu, 27 Sep 2012 10:58:19 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; bh=OTIlmglQAp1/9kJBKATSZJtKAgxnDuCGJRw6IaKDE3Y=; b=M/dyEBknv7w8+AlxMDBD5hBDTRVGrYTmkiavm1SH6oYGyoNUhn64sfj5IBRw0c2RGS +lXijECI1mYm1oEbcCGurRSA7YJvKssyPIHwsQOPlb6Sb4LwS/jJImZdIq0qZBWFfcjX S0JS+9rTnYF1p9vAY+Ab7GenQVF2W4OqDc0DxhSy6iqzTjPJpeflK2QU8LqnQF27dcA8 q5CiHnhiSBfag5iNtxwvJ4Q8eij0uqjh66Avy+6hqP6jlqq1U9GYl+IstogH/nELITD2 nXIeoMKO+jWMoYLWay4XOPG60eeZ0rby/FVxI9HRqA+rxTLdPoSEfUR6GDStnxwY6wyY ddXg== MIME-Version: 1.0 Received: by 10.182.139.99 with SMTP id qx3mr3691599obb.102.1348768699491; Thu, 27 Sep 2012 10:58:19 -0700 (PDT) Received: by 10.60.146.236 with HTTP; Thu, 27 Sep 2012 10:58:19 -0700 (PDT) In-Reply-To: <50648CEA.9070107@gmail.com> References: <50645166.2000200@gmail.com> <50647B26.9080903@gmail.com> <50648CEA.9070107@gmail.com> Date: Thu, 27 Sep 2012 19:58:19 +0200 Message-ID: From: Dariusz Krempa To: "xen-users@lists.xen.org" Subject: Re: [Xen-users] Success VGA passthrough on windows 7 x64 with Xen 4.2.1-pre X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org 2012/9/27 Teo En Ming (Zhang Enming) : > On 28/09/2012 00:52, Dariusz Krempa wrote: >>> >>> Dear Dariusz Krempa, >>> >>> I am also interested in knowing how you get the "nasty yellow triangle >>> with >>> error 43" to disappear. >>> >>> In addition, may I know which guide did you follow in getting VGA >>> passthrough to work 100%? >>> >>> Thank you very much. >>> >>> -- >>> Yours sincerely, >>> >>> Mr. Teo En Ming (Zhang Enming) >>> Singapore >>> >>> >>> >>> _______________________________________________ >>> Xen-users mailing list >>> Xen-users@lists.xen.org >>> http://lists.xen.org/xen-users >> >> I started with guide from You dated 25 march 2012 to build Dom0 and >> Xen 4.2, but with few modifications this time. >> 1) I used kernel 3.6-rc7 for Dom0 --> >> http://kernel.org/pub/linux/kernel/v3.x/testing/linux-3.6-rc7.tar.bz2 >> 2) I used Xen from http://xenbits.xen.org/hg/staging/xen-unstable.hg/ >> 3) VGA patch from David's Gis rev 25240 >> 4) I used pciback to hide my gtx560 from Dom0, and for a while i have >> had second gfx - hd4850, but now i removed it and i have only gtx560, >> still working >> >> and finally I think I know what make that error 43 disappeared. At >> first I did comment those lines in DomU config: >> >> #pci_msitranslate = 1 >> #pci_power_mgmt = 1 >> #xen_platform_pci=1 >> #xen_extended_power_mgmt=1 >> >> When i had success with installation i start to remove comments and >> the one which is nasty is pci_msitranslate. This make some other >> problems, like not working USB ports, but ... >> >> If any other information will be needed please let me know. >> >> Hardware: >> asus P8H67 >> asus GTX560 DCII top >> 4GB ram >> >> System: >> ubuntu 12.04 >> Dom0 kernel 3.6-rc7 >> DomU windows 7 x64 >> nvidia drivers 275.33 - but possibly 275.50 also will work >> >> _______________________________________________ >> Xen-users mailing list >> Xen-users@lists.xen.org >> http://lists.xen.org/xen-users >> > > Dear Dariusz Krempa, > > Thank you for your prompt reply. > > I don't have pci_msitranslate = 1 in my Windows HVM domU config file, so I > don't think "pci_msitranslate = 1" is the main cause of my "nasty yellow > triangle with error 43". > > > -- > Yours sincerely, > > Mr. Teo En Ming (Zhang Enming) > Singapore > I checked DomU with and without msi and with msi i saw bluescreen and turning it off, and DomU again start normally. Like I wrote, I also have different kernel for Dom0, with 3.3-rc7 i had error 43 and today first time installed xen 4.2.1-pre( from source). Yesterday and days before that i had xen 4.2-rc2 -- 4.2-rc4. Im not 100% sure what (kernel or new xen) fixed problem and for now i will play with windows 7, maybe tommorow or day or two later i will again reinstall Dom0 to check which one solved problem. In mean time at least we know that its possible to pass vga to windows 7 DomU, and how. Im sure that You and maybe other users will try on her own system with settings I described. There was also few more things i did just before i had success, but i think it has nothing to do with it. Just mention it: - removed opencl libraries under windows system, - removed cuda libraries under windows, - reinstall nvidia drivers to version 275.33 (there was 306.xx or something, dont remember) _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Thu Sep 27 17:59:21 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Thu, 27 Sep 2012 17:59:21 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1THIM0-0000Aa-PJ; Thu, 27 Sep 2012 17:58:28 +0000 Received: from mail27.messagelabs.com ([193.109.254.147]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1THIM0-0000AV-2M for xen-users@lists.xen.org; Thu, 27 Sep 2012 17:58:28 +0000 X-Env-Sender: imperiaonline4@gmail.com X-Msg-Ref: server-12.tower-27.messagelabs.com!1348768699!12638711!1 X-Originating-IP: [209.85.214.169] X-SpamReason: No, hits=0.8 required=7.0 tests=BODY_RANDOM_LONG, ML_RADAR_SPEW_LINKS_14,RCVD_BY_IP,spamassassin: X-StarScan-Received: X-StarScan-Version: 6.6.1.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 21135 invoked from network); 27 Sep 2012 17:58:21 -0000 Received: from mail-ob0-f169.google.com (HELO mail-ob0-f169.google.com) (209.85.214.169) by server-12.tower-27.messagelabs.com with RC4-SHA encrypted SMTP; 27 Sep 2012 17:58:21 -0000 Received: by obcva7 with SMTP id va7so2029940obc.28 for ; Thu, 27 Sep 2012 10:58:19 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; bh=OTIlmglQAp1/9kJBKATSZJtKAgxnDuCGJRw6IaKDE3Y=; b=M/dyEBknv7w8+AlxMDBD5hBDTRVGrYTmkiavm1SH6oYGyoNUhn64sfj5IBRw0c2RGS +lXijECI1mYm1oEbcCGurRSA7YJvKssyPIHwsQOPlb6Sb4LwS/jJImZdIq0qZBWFfcjX S0JS+9rTnYF1p9vAY+Ab7GenQVF2W4OqDc0DxhSy6iqzTjPJpeflK2QU8LqnQF27dcA8 q5CiHnhiSBfag5iNtxwvJ4Q8eij0uqjh66Avy+6hqP6jlqq1U9GYl+IstogH/nELITD2 nXIeoMKO+jWMoYLWay4XOPG60eeZ0rby/FVxI9HRqA+rxTLdPoSEfUR6GDStnxwY6wyY ddXg== MIME-Version: 1.0 Received: by 10.182.139.99 with SMTP id qx3mr3691599obb.102.1348768699491; Thu, 27 Sep 2012 10:58:19 -0700 (PDT) Received: by 10.60.146.236 with HTTP; Thu, 27 Sep 2012 10:58:19 -0700 (PDT) In-Reply-To: <50648CEA.9070107@gmail.com> References: <50645166.2000200@gmail.com> <50647B26.9080903@gmail.com> <50648CEA.9070107@gmail.com> Date: Thu, 27 Sep 2012 19:58:19 +0200 Message-ID: From: Dariusz Krempa To: "xen-users@lists.xen.org" Subject: Re: [Xen-users] Success VGA passthrough on windows 7 x64 with Xen 4.2.1-pre X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org 2012/9/27 Teo En Ming (Zhang Enming) : > On 28/09/2012 00:52, Dariusz Krempa wrote: >>> >>> Dear Dariusz Krempa, >>> >>> I am also interested in knowing how you get the "nasty yellow triangle >>> with >>> error 43" to disappear. >>> >>> In addition, may I know which guide did you follow in getting VGA >>> passthrough to work 100%? >>> >>> Thank you very much. >>> >>> -- >>> Yours sincerely, >>> >>> Mr. Teo En Ming (Zhang Enming) >>> Singapore >>> >>> >>> >>> _______________________________________________ >>> Xen-users mailing list >>> Xen-users@lists.xen.org >>> http://lists.xen.org/xen-users >> >> I started with guide from You dated 25 march 2012 to build Dom0 and >> Xen 4.2, but with few modifications this time. >> 1) I used kernel 3.6-rc7 for Dom0 --> >> http://kernel.org/pub/linux/kernel/v3.x/testing/linux-3.6-rc7.tar.bz2 >> 2) I used Xen from http://xenbits.xen.org/hg/staging/xen-unstable.hg/ >> 3) VGA patch from David's Gis rev 25240 >> 4) I used pciback to hide my gtx560 from Dom0, and for a while i have >> had second gfx - hd4850, but now i removed it and i have only gtx560, >> still working >> >> and finally I think I know what make that error 43 disappeared. At >> first I did comment those lines in DomU config: >> >> #pci_msitranslate = 1 >> #pci_power_mgmt = 1 >> #xen_platform_pci=1 >> #xen_extended_power_mgmt=1 >> >> When i had success with installation i start to remove comments and >> the one which is nasty is pci_msitranslate. This make some other >> problems, like not working USB ports, but ... >> >> If any other information will be needed please let me know. >> >> Hardware: >> asus P8H67 >> asus GTX560 DCII top >> 4GB ram >> >> System: >> ubuntu 12.04 >> Dom0 kernel 3.6-rc7 >> DomU windows 7 x64 >> nvidia drivers 275.33 - but possibly 275.50 also will work >> >> _______________________________________________ >> Xen-users mailing list >> Xen-users@lists.xen.org >> http://lists.xen.org/xen-users >> > > Dear Dariusz Krempa, > > Thank you for your prompt reply. > > I don't have pci_msitranslate = 1 in my Windows HVM domU config file, so I > don't think "pci_msitranslate = 1" is the main cause of my "nasty yellow > triangle with error 43". > > > -- > Yours sincerely, > > Mr. Teo En Ming (Zhang Enming) > Singapore > I checked DomU with and without msi and with msi i saw bluescreen and turning it off, and DomU again start normally. Like I wrote, I also have different kernel for Dom0, with 3.3-rc7 i had error 43 and today first time installed xen 4.2.1-pre( from source). Yesterday and days before that i had xen 4.2-rc2 -- 4.2-rc4. Im not 100% sure what (kernel or new xen) fixed problem and for now i will play with windows 7, maybe tommorow or day or two later i will again reinstall Dom0 to check which one solved problem. In mean time at least we know that its possible to pass vga to windows 7 DomU, and how. Im sure that You and maybe other users will try on her own system with settings I described. There was also few more things i did just before i had success, but i think it has nothing to do with it. Just mention it: - removed opencl libraries under windows system, - removed cuda libraries under windows, - reinstall nvidia drivers to version 275.33 (there was 306.xx or something, dont remember) _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Thu Sep 27 18:00:47 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Thu, 27 Sep 2012 18:00:47 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1THINX-0000L6-Hw; Thu, 27 Sep 2012 18:00:03 +0000 Received: from mail27.messagelabs.com ([193.109.254.147]) by lists.xen.org with smtp (Exim 4.72) (envelope-from ) id 1THINV-0000GY-F8 for xen-users@lists.xen.org; Thu, 27 Sep 2012 18:00:01 +0000 X-Env-Sender: xtreme911@msn.com X-Msg-Ref: server-13.tower-27.messagelabs.com!1348768794!11521428!1 X-Originating-IP: [65.54.190.92] X-SpamReason: No, hits=0.1 required=7.0 tests=FORGED_HOTMAIL_RCVD, ML_RADAR_SPEW_LINKS_12,spamassassin: X-StarScan-Received: X-StarScan-Version: 6.6.1.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 11285 invoked from network); 27 Sep 2012 17:59:55 -0000 Received: from bay0-omc2-s17.bay0.hotmail.com (HELO bay0-omc2-s17.bay0.hotmail.com) (65.54.190.92) by server-13.tower-27.messagelabs.com with SMTP; 27 Sep 2012 17:59:55 -0000 Received: from BAY148-W11 ([65.54.190.125]) by bay0-omc2-s17.bay0.hotmail.com with Microsoft SMTPSVC(6.0.3790.4675); Thu, 27 Sep 2012 10:59:53 -0700 Message-ID: X-Originating-IP: [76.68.73.169] From: Mike Viau To: Date: Thu, 27 Sep 2012 13:59:54 -0400 Importance: Normal In-Reply-To: <50648CEA.9070107@gmail.com> References: , <50645166.2000200@gmail.com> <50647B26.9080903@gmail.com>, , <50648CEA.9070107@gmail.com> MIME-Version: 1.0 X-OriginalArrivalTime: 27 Sep 2012 17:59:53.0892 (UTC) FILETIME=[E5AF4E40:01CD9CD9] Subject: Re: [Xen-users] Success VGA passthrough on windows 7 x64 with Xen 4.2.1-pre X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org > On Fri, 28 Sep 2012 01:29:14 +0800 wrote: > > Dear Dariusz Krempa, > > Thank you for your prompt reply. > > I don't have pci_msitranslate = 1 in my Windows HVM domU config file, so > I don't think "pci_msitranslate = 1" is the main cause of my "nasty > yellow triangle with error 43". > I once recorded that the default for the pci_msitranslate option was "1". Not having this in your configuration then is like having it set. Feel free to correct me if I am wrong. I have only gotten VGA pass-through to work with a Windows domU, never in GNU/Linux for some reason. -M _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Thu Sep 27 18:00:47 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Thu, 27 Sep 2012 18:00:47 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1THINX-0000L6-Hw; Thu, 27 Sep 2012 18:00:03 +0000 Received: from mail27.messagelabs.com ([193.109.254.147]) by lists.xen.org with smtp (Exim 4.72) (envelope-from ) id 1THINV-0000GY-F8 for xen-users@lists.xen.org; Thu, 27 Sep 2012 18:00:01 +0000 X-Env-Sender: xtreme911@msn.com X-Msg-Ref: server-13.tower-27.messagelabs.com!1348768794!11521428!1 X-Originating-IP: [65.54.190.92] X-SpamReason: No, hits=0.1 required=7.0 tests=FORGED_HOTMAIL_RCVD, ML_RADAR_SPEW_LINKS_12,spamassassin: X-StarScan-Received: X-StarScan-Version: 6.6.1.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 11285 invoked from network); 27 Sep 2012 17:59:55 -0000 Received: from bay0-omc2-s17.bay0.hotmail.com (HELO bay0-omc2-s17.bay0.hotmail.com) (65.54.190.92) by server-13.tower-27.messagelabs.com with SMTP; 27 Sep 2012 17:59:55 -0000 Received: from BAY148-W11 ([65.54.190.125]) by bay0-omc2-s17.bay0.hotmail.com with Microsoft SMTPSVC(6.0.3790.4675); Thu, 27 Sep 2012 10:59:53 -0700 Message-ID: X-Originating-IP: [76.68.73.169] From: Mike Viau To: Date: Thu, 27 Sep 2012 13:59:54 -0400 Importance: Normal In-Reply-To: <50648CEA.9070107@gmail.com> References: , <50645166.2000200@gmail.com> <50647B26.9080903@gmail.com>, , <50648CEA.9070107@gmail.com> MIME-Version: 1.0 X-OriginalArrivalTime: 27 Sep 2012 17:59:53.0892 (UTC) FILETIME=[E5AF4E40:01CD9CD9] Subject: Re: [Xen-users] Success VGA passthrough on windows 7 x64 with Xen 4.2.1-pre X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org > On Fri, 28 Sep 2012 01:29:14 +0800 wrote: > > Dear Dariusz Krempa, > > Thank you for your prompt reply. > > I don't have pci_msitranslate = 1 in my Windows HVM domU config file, so > I don't think "pci_msitranslate = 1" is the main cause of my "nasty > yellow triangle with error 43". > I once recorded that the default for the pci_msitranslate option was "1". Not having this in your configuration then is like having it set. Feel free to correct me if I am wrong. I have only gotten VGA pass-through to work with a Windows domU, never in GNU/Linux for some reason. -M _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Thu Sep 27 18:36:10 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Thu, 27 Sep 2012 18:36:10 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1THIvQ-0002wU-44; Thu, 27 Sep 2012 18:35:04 +0000 Received: from mail27.messagelabs.com ([193.109.254.147]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1THIvO-0002wP-Kf for Xen-users@lists.xen.org; Thu, 27 Sep 2012 18:35:02 +0000 X-Env-Sender: imperiaonline4@gmail.com X-Msg-Ref: server-3.tower-27.messagelabs.com!1348770895!10672139!1 X-Originating-IP: [209.85.214.173] X-SpamReason: No, hits=0.3 required=7.0 tests=ML_RADAR_SPEW_LINKS_14, RCVD_BY_IP,spamassassin: X-StarScan-Received: X-StarScan-Version: 6.6.1.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 6815 invoked from network); 27 Sep 2012 18:34:56 -0000 Received: from mail-ob0-f173.google.com (HELO mail-ob0-f173.google.com) (209.85.214.173) by server-3.tower-27.messagelabs.com with RC4-SHA encrypted SMTP; 27 Sep 2012 18:34:56 -0000 Received: by obbwc18 with SMTP id wc18so47327obb.32 for ; Thu, 27 Sep 2012 11:34:54 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type:content-transfer-encoding; bh=VLBVmPF+iwilXeFT7a7O5LX9GcuSTrRZHogO08mNNQo=; b=qoG6Xwjmux9QoDJUzGO+YRvFGhfC/TBmXE0oh+e/mLcRrz4InNHWe+nOlSkzauhqK+ 2b13ED9UMtoXsPsrHHfN/85mf4T1LW9hbCgoyIbLsnSOf5vWtxFFf9yI831w03PHZEiO nXN6XRhV520B6z5sbkHwXrs4DDk0g2eJCumilx1lKZviiqu+gaHjy6+y/q3Isr9cJZYl DoPxkgsjaATjr6mYw0/X6/RP54VSI8zhRCYdCtavDxdvJ81EMeuh1SqkoMjQPo0t4csy 3H1VY3mxsU7mQc6dilj7B8sCzc7ruTxedcUy4A13yFI5T995Tnjk4HqJopt/w4mNbIsJ 9/NQ== MIME-Version: 1.0 Received: by 10.60.172.42 with SMTP id az10mr3871271oec.1.1348770894848; Thu, 27 Sep 2012 11:34:54 -0700 (PDT) Received: by 10.60.146.236 with HTTP; Thu, 27 Sep 2012 11:34:54 -0700 (PDT) In-Reply-To: References: <50645166.2000200@gmail.com> <50647B26.9080903@gmail.com> <50648CEA.9070107@gmail.com> Date: Thu, 27 Sep 2012 20:34:54 +0200 Message-ID: From: Dariusz Krempa To: "xen-users@lists.xen.org" Subject: Re: [Xen-users] Success VGA passthrough on windows 7 x64 with Xen 4.2.1-pre X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org 2012/9/27 Mike Viau : > >> On Fri, 28 Sep 2012 01:29:14 +0800 wrote: >> >> Dear Dariusz Krempa, >> >> Thank you for your prompt reply. >> >> I don't have pci_msitranslate = 1 in my Windows HVM domU config file, so >> I don't think "pci_msitranslate = 1" is the main cause of my "nasty >> yellow triangle with error 43". >> > > I once recorded that the default for the pci_msitranslate option was "1". Not having this in your configuration then is like having it set. Feel free to correct me if I am wrong. I have only gotten VGA pass-through to work with a Windows domU, never in GNU/Linux for some reason. > > > -M > > _______________________________________________ > Xen-users mailing list > Xen-users@lists.xen.org > http://lists.xen.org/xen-users from change set 25525 msitranslate is 0 by deafault http://xenbits.xensource.com/hg/staging/xen-unstable.hg/rev/84272cca638a?revcount=120 _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Thu Sep 27 18:36:10 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Thu, 27 Sep 2012 18:36:10 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1THIvQ-0002wU-44; Thu, 27 Sep 2012 18:35:04 +0000 Received: from mail27.messagelabs.com ([193.109.254.147]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1THIvO-0002wP-Kf for Xen-users@lists.xen.org; Thu, 27 Sep 2012 18:35:02 +0000 X-Env-Sender: imperiaonline4@gmail.com X-Msg-Ref: server-3.tower-27.messagelabs.com!1348770895!10672139!1 X-Originating-IP: [209.85.214.173] X-SpamReason: No, hits=0.3 required=7.0 tests=ML_RADAR_SPEW_LINKS_14, RCVD_BY_IP,spamassassin: X-StarScan-Received: X-StarScan-Version: 6.6.1.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 6815 invoked from network); 27 Sep 2012 18:34:56 -0000 Received: from mail-ob0-f173.google.com (HELO mail-ob0-f173.google.com) (209.85.214.173) by server-3.tower-27.messagelabs.com with RC4-SHA encrypted SMTP; 27 Sep 2012 18:34:56 -0000 Received: by obbwc18 with SMTP id wc18so47327obb.32 for ; Thu, 27 Sep 2012 11:34:54 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type:content-transfer-encoding; bh=VLBVmPF+iwilXeFT7a7O5LX9GcuSTrRZHogO08mNNQo=; b=qoG6Xwjmux9QoDJUzGO+YRvFGhfC/TBmXE0oh+e/mLcRrz4InNHWe+nOlSkzauhqK+ 2b13ED9UMtoXsPsrHHfN/85mf4T1LW9hbCgoyIbLsnSOf5vWtxFFf9yI831w03PHZEiO nXN6XRhV520B6z5sbkHwXrs4DDk0g2eJCumilx1lKZviiqu+gaHjy6+y/q3Isr9cJZYl DoPxkgsjaATjr6mYw0/X6/RP54VSI8zhRCYdCtavDxdvJ81EMeuh1SqkoMjQPo0t4csy 3H1VY3mxsU7mQc6dilj7B8sCzc7ruTxedcUy4A13yFI5T995Tnjk4HqJopt/w4mNbIsJ 9/NQ== MIME-Version: 1.0 Received: by 10.60.172.42 with SMTP id az10mr3871271oec.1.1348770894848; Thu, 27 Sep 2012 11:34:54 -0700 (PDT) Received: by 10.60.146.236 with HTTP; Thu, 27 Sep 2012 11:34:54 -0700 (PDT) In-Reply-To: References: <50645166.2000200@gmail.com> <50647B26.9080903@gmail.com> <50648CEA.9070107@gmail.com> Date: Thu, 27 Sep 2012 20:34:54 +0200 Message-ID: From: Dariusz Krempa To: "xen-users@lists.xen.org" Subject: Re: [Xen-users] Success VGA passthrough on windows 7 x64 with Xen 4.2.1-pre X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org 2012/9/27 Mike Viau : > >> On Fri, 28 Sep 2012 01:29:14 +0800 wrote: >> >> Dear Dariusz Krempa, >> >> Thank you for your prompt reply. >> >> I don't have pci_msitranslate = 1 in my Windows HVM domU config file, so >> I don't think "pci_msitranslate = 1" is the main cause of my "nasty >> yellow triangle with error 43". >> > > I once recorded that the default for the pci_msitranslate option was "1". Not having this in your configuration then is like having it set. Feel free to correct me if I am wrong. I have only gotten VGA pass-through to work with a Windows domU, never in GNU/Linux for some reason. > > > -M > > _______________________________________________ > Xen-users mailing list > Xen-users@lists.xen.org > http://lists.xen.org/xen-users from change set 25525 msitranslate is 0 by deafault http://xenbits.xensource.com/hg/staging/xen-unstable.hg/rev/84272cca638a?revcount=120 _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Thu Sep 27 18:42:49 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Thu, 27 Sep 2012 18:42:49 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1THJ2J-0003HD-JJ; Thu, 27 Sep 2012 18:42:11 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1THJ2I-0003Gj-4f for xen-users@lists.xen.org; Thu, 27 Sep 2012 18:42:10 +0000 Received: from [85.158.139.211:38998] by server-3.bemta-5.messagelabs.com id 93/14-16108-00E94605; Thu, 27 Sep 2012 18:42:08 +0000 X-Env-Sender: singapore.mr.teo.en.ming@gmail.com X-Msg-Ref: server-2.tower-206.messagelabs.com!1348771326!20213955!1 X-Originating-IP: [209.85.160.45] X-SpamReason: No, hits=0.3 required=7.0 tests=ML_RADAR_SPEW_LINKS_14, RCVD_BY_IP,spamassassin: X-StarScan-Received: X-StarScan-Version: 6.6.1.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 22255 invoked from network); 27 Sep 2012 18:42:08 -0000 Received: from mail-pb0-f45.google.com (HELO mail-pb0-f45.google.com) (209.85.160.45) by server-2.tower-206.messagelabs.com with RC4-SHA encrypted SMTP; 27 Sep 2012 18:42:08 -0000 Received: by pbbrp2 with SMTP id rp2so4145194pbb.32 for ; Thu, 27 Sep 2012 11:42:06 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:disposition-notification-to:date:from:user-agent :mime-version:to:subject:content-type:content-transfer-encoding; bh=9I0JTUx4ComYhqA6PgNg31tqzKqPiVTp1Z4jVK7BkRA=; b=hIhmmSQV/2WgcmNPWwt3wZaF43r4qBzSKGkLKauCyVyk0JTa7Y/oPBev1OEoOSQDTy fN2cfQ4ExCbvSxw1L6ShpFU7GVaNdhedYycUDcv+H4tS1nsAZrdCqZDFuB1ukmL5+NRN M5OxWlV/NQImaLHyhHJ4BhCb3TlFhJoGBgz7QlNuyIWHvhVAVxKS5JQhwPUo8lxCYAj7 oEVqXej0+f+/gBijk4yl5zb34kyDw/RZOYGztvn1qGeHr3lgUqlJL3pLOEKiJDm7Uqze No7NgLl1+7jxqGcigc4hVBAogywati4e87VKmczymCEsszoIdUcSJJqDwrvLObau2cT0 qUfA== Received: by 10.66.79.36 with SMTP id g4mr11539951pax.67.1348771326058; Thu, 27 Sep 2012 11:42:06 -0700 (PDT) Received: from [192.168.1.2] (cm141.gamma206.maxonline.com.sg. [202.156.206.141]) by mx.google.com with ESMTPS id nt7sm4213188pbb.33.2012.09.27.11.42.04 (version=SSLv3 cipher=OTHER); Thu, 27 Sep 2012 11:42:05 -0700 (PDT) Message-ID: <50649DFA.6020004@gmail.com> Date: Fri, 28 Sep 2012 02:42:02 +0800 From: "Teo En Ming (Zhang Enming)" User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:10.0.2) Gecko/20120216 Thunderbird/10.0.2 MIME-Version: 1.0 To: "xen-users@lists.xen.org" , "xen-devel@lists.xen.org" , "Teo En Ming (Zhang Enming)" Subject: [Xen-users] xl: symbol lookup error: xl: undefined symbol: libxl_childproc_setmode X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset="us-ascii"; Format="flowed" Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org Hi, I have just compiled xen 4.2.1-pre changeset 25862 from sources. When I tried to execute "sudo xl list" or "sudo xl info", it gave me the following error: xl: symbol lookup error: xl: undefined symbol: libxl_childproc_setmode Anybody knows how to solve this problem? Thank you very much. -- Yours sincerely, Mr. Teo En Ming (Zhang Enming) Singapore _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Thu Sep 27 18:42:49 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Thu, 27 Sep 2012 18:42:49 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1THJ2J-0003HD-JJ; Thu, 27 Sep 2012 18:42:11 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1THJ2I-0003Gj-4f for xen-users@lists.xen.org; Thu, 27 Sep 2012 18:42:10 +0000 Received: from [85.158.139.211:38998] by server-3.bemta-5.messagelabs.com id 93/14-16108-00E94605; Thu, 27 Sep 2012 18:42:08 +0000 X-Env-Sender: singapore.mr.teo.en.ming@gmail.com X-Msg-Ref: server-2.tower-206.messagelabs.com!1348771326!20213955!1 X-Originating-IP: [209.85.160.45] X-SpamReason: No, hits=0.3 required=7.0 tests=ML_RADAR_SPEW_LINKS_14, RCVD_BY_IP,spamassassin: X-StarScan-Received: X-StarScan-Version: 6.6.1.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 22255 invoked from network); 27 Sep 2012 18:42:08 -0000 Received: from mail-pb0-f45.google.com (HELO mail-pb0-f45.google.com) (209.85.160.45) by server-2.tower-206.messagelabs.com with RC4-SHA encrypted SMTP; 27 Sep 2012 18:42:08 -0000 Received: by pbbrp2 with SMTP id rp2so4145194pbb.32 for ; Thu, 27 Sep 2012 11:42:06 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:disposition-notification-to:date:from:user-agent :mime-version:to:subject:content-type:content-transfer-encoding; bh=9I0JTUx4ComYhqA6PgNg31tqzKqPiVTp1Z4jVK7BkRA=; b=hIhmmSQV/2WgcmNPWwt3wZaF43r4qBzSKGkLKauCyVyk0JTa7Y/oPBev1OEoOSQDTy fN2cfQ4ExCbvSxw1L6ShpFU7GVaNdhedYycUDcv+H4tS1nsAZrdCqZDFuB1ukmL5+NRN M5OxWlV/NQImaLHyhHJ4BhCb3TlFhJoGBgz7QlNuyIWHvhVAVxKS5JQhwPUo8lxCYAj7 oEVqXej0+f+/gBijk4yl5zb34kyDw/RZOYGztvn1qGeHr3lgUqlJL3pLOEKiJDm7Uqze No7NgLl1+7jxqGcigc4hVBAogywati4e87VKmczymCEsszoIdUcSJJqDwrvLObau2cT0 qUfA== Received: by 10.66.79.36 with SMTP id g4mr11539951pax.67.1348771326058; Thu, 27 Sep 2012 11:42:06 -0700 (PDT) Received: from [192.168.1.2] (cm141.gamma206.maxonline.com.sg. [202.156.206.141]) by mx.google.com with ESMTPS id nt7sm4213188pbb.33.2012.09.27.11.42.04 (version=SSLv3 cipher=OTHER); Thu, 27 Sep 2012 11:42:05 -0700 (PDT) Message-ID: <50649DFA.6020004@gmail.com> Date: Fri, 28 Sep 2012 02:42:02 +0800 From: "Teo En Ming (Zhang Enming)" User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:10.0.2) Gecko/20120216 Thunderbird/10.0.2 MIME-Version: 1.0 To: "xen-users@lists.xen.org" , "xen-devel@lists.xen.org" , "Teo En Ming (Zhang Enming)" Subject: [Xen-users] xl: symbol lookup error: xl: undefined symbol: libxl_childproc_setmode X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset="us-ascii"; Format="flowed" Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org Hi, I have just compiled xen 4.2.1-pre changeset 25862 from sources. When I tried to execute "sudo xl list" or "sudo xl info", it gave me the following error: xl: symbol lookup error: xl: undefined symbol: libxl_childproc_setmode Anybody knows how to solve this problem? Thank you very much. -- Yours sincerely, Mr. Teo En Ming (Zhang Enming) Singapore _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Thu Sep 27 18:55:46 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Thu, 27 Sep 2012 18:55:46 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1THJEk-0003u9-5P; Thu, 27 Sep 2012 18:55:02 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1THJEh-0003u4-Rr for xen-users@lists.xen.org; Thu, 27 Sep 2012 18:55:00 +0000 Received: from [85.158.137.99:62014] by server-7.bemta-3.messagelabs.com id 7C/2B-15765-301A4605; Thu, 27 Sep 2012 18:54:59 +0000 X-Env-Sender: singapore.mr.teo.en.ming@gmail.com X-Msg-Ref: server-16.tower-217.messagelabs.com!1348772093!19403160!1 X-Originating-IP: [209.85.220.45] X-SpamReason: No, hits=0.3 required=7.0 tests=ML_RADAR_SPEW_LINKS_14, RCVD_BY_IP,spamassassin: X-StarScan-Received: X-StarScan-Version: 6.6.1.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 13109 invoked from network); 27 Sep 2012 18:54:58 -0000 Received: from mail-pa0-f45.google.com (HELO mail-pa0-f45.google.com) (209.85.220.45) by server-16.tower-217.messagelabs.com with RC4-SHA encrypted SMTP; 27 Sep 2012 18:54:58 -0000 Received: by padfb10 with SMTP id fb10so1638117pad.32 for ; Thu, 27 Sep 2012 11:54:53 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:disposition-notification-to:date:from:user-agent :mime-version:to:subject:references:in-reply-to:content-type :content-transfer-encoding; bh=78XRWtWcyt0YrlAhKa+D5RaTUHaSeSm+2yHXOaqTr98=; b=EznDkL9VvaAOpGqbihUJP2leq9XmyTpn/GvNwR0KKpaIF/7NJmFQd0bqUEiPISHFpL vxnUldGHPVHxggGUx06DBN4snBc7+ouS83Iuutw31XBwi70Ou3r78hpyH9DvWuPQnVLR s9eUb69CqUaWX6wogQG/MS0dEU/oOvL9G8FxCNKy9CYlTpQmCMuaErDMYvbhzLmRh83V h7K2cFH8t9W6HBs7+lxm1cgJFAw3tqgK3fNb+nPopwGEmQGAYzhVuv3O2+ODWDtqVgeb oKHPkqASzY+qxP6uyIQAqnnAQxtNQu907W1iEKrjrFJ/vyqyT6jCRhPqBRNv9ROnhFBK x04w== Received: by 10.66.88.198 with SMTP id bi6mr11731874pab.23.1348772092703; Thu, 27 Sep 2012 11:54:52 -0700 (PDT) Received: from [192.168.1.2] (cm141.gamma206.maxonline.com.sg. [202.156.206.141]) by mx.google.com with ESMTPS id o1sm4116479pax.21.2012.09.27.11.54.50 (version=SSLv3 cipher=OTHER); Thu, 27 Sep 2012 11:54:51 -0700 (PDT) Message-ID: <5064A0F9.3090304@gmail.com> Date: Fri, 28 Sep 2012 02:54:49 +0800 From: "Teo En Ming (Zhang Enming)" User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:10.0.2) Gecko/20120216 Thunderbird/10.0.2 MIME-Version: 1.0 To: Dariusz Krempa , "xen-users@lists.xen.org" , "Teo En Ming (Zhang Enming)" References: <50645166.2000200@gmail.com> <50647B26.9080903@gmail.com> <50648CEA.9070107@gmail.com> In-Reply-To: Subject: Re: [Xen-users] Success VGA passthrough on windows 7 x64 with Xen 4.2.1-pre X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset="us-ascii"; Format="flowed" Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org On 28/09/2012 02:34, Dariusz Krempa wrote: > 2012/9/27 Mike Viau: >>> On Fri, 28 Sep 2012 01:29:14 +0800 wrote: >>> >>> Dear Dariusz Krempa, >>> >>> Thank you for your prompt reply. >>> >>> I don't have pci_msitranslate = 1 in my Windows HVM domU config file, so >>> I don't think "pci_msitranslate = 1" is the main cause of my "nasty >>> yellow triangle with error 43". >>> >> I once recorded that the default for the pci_msitranslate option was "1". Not having this in your configuration then is like having it set. Feel free to correct me if I am wrong. I have only gotten VGA pass-through to work with a Windows domU, never in GNU/Linux for some reason. >> >> >> -M >> >> _______________________________________________ >> Xen-users mailing list >> Xen-users@lists.xen.org >> http://lists.xen.org/xen-users > from change set 25525 msitranslate is 0 by deafault > > http://xenbits.xensource.com/hg/staging/xen-unstable.hg/rev/84272cca638a?revcount=120 > > _______________________________________________ > Xen-users mailing list > Xen-users@lists.xen.org > http://lists.xen.org/xen-users > Hi, May I know whether your GTX 560 is a Ti or a non Ti, that is, GTX 560 or GTX 560 Ti? Thank you very much. -- Yours sincerely, Mr. Teo En Ming (Zhang Enming) Singapore _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Thu Sep 27 18:55:46 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Thu, 27 Sep 2012 18:55:46 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1THJEk-0003u9-5P; Thu, 27 Sep 2012 18:55:02 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1THJEh-0003u4-Rr for xen-users@lists.xen.org; Thu, 27 Sep 2012 18:55:00 +0000 Received: from [85.158.137.99:62014] by server-7.bemta-3.messagelabs.com id 7C/2B-15765-301A4605; Thu, 27 Sep 2012 18:54:59 +0000 X-Env-Sender: singapore.mr.teo.en.ming@gmail.com X-Msg-Ref: server-16.tower-217.messagelabs.com!1348772093!19403160!1 X-Originating-IP: [209.85.220.45] X-SpamReason: No, hits=0.3 required=7.0 tests=ML_RADAR_SPEW_LINKS_14, RCVD_BY_IP,spamassassin: X-StarScan-Received: X-StarScan-Version: 6.6.1.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 13109 invoked from network); 27 Sep 2012 18:54:58 -0000 Received: from mail-pa0-f45.google.com (HELO mail-pa0-f45.google.com) (209.85.220.45) by server-16.tower-217.messagelabs.com with RC4-SHA encrypted SMTP; 27 Sep 2012 18:54:58 -0000 Received: by padfb10 with SMTP id fb10so1638117pad.32 for ; Thu, 27 Sep 2012 11:54:53 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:disposition-notification-to:date:from:user-agent :mime-version:to:subject:references:in-reply-to:content-type :content-transfer-encoding; bh=78XRWtWcyt0YrlAhKa+D5RaTUHaSeSm+2yHXOaqTr98=; b=EznDkL9VvaAOpGqbihUJP2leq9XmyTpn/GvNwR0KKpaIF/7NJmFQd0bqUEiPISHFpL vxnUldGHPVHxggGUx06DBN4snBc7+ouS83Iuutw31XBwi70Ou3r78hpyH9DvWuPQnVLR s9eUb69CqUaWX6wogQG/MS0dEU/oOvL9G8FxCNKy9CYlTpQmCMuaErDMYvbhzLmRh83V h7K2cFH8t9W6HBs7+lxm1cgJFAw3tqgK3fNb+nPopwGEmQGAYzhVuv3O2+ODWDtqVgeb oKHPkqASzY+qxP6uyIQAqnnAQxtNQu907W1iEKrjrFJ/vyqyT6jCRhPqBRNv9ROnhFBK x04w== Received: by 10.66.88.198 with SMTP id bi6mr11731874pab.23.1348772092703; Thu, 27 Sep 2012 11:54:52 -0700 (PDT) Received: from [192.168.1.2] (cm141.gamma206.maxonline.com.sg. [202.156.206.141]) by mx.google.com with ESMTPS id o1sm4116479pax.21.2012.09.27.11.54.50 (version=SSLv3 cipher=OTHER); Thu, 27 Sep 2012 11:54:51 -0700 (PDT) Message-ID: <5064A0F9.3090304@gmail.com> Date: Fri, 28 Sep 2012 02:54:49 +0800 From: "Teo En Ming (Zhang Enming)" User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:10.0.2) Gecko/20120216 Thunderbird/10.0.2 MIME-Version: 1.0 To: Dariusz Krempa , "xen-users@lists.xen.org" , "Teo En Ming (Zhang Enming)" References: <50645166.2000200@gmail.com> <50647B26.9080903@gmail.com> <50648CEA.9070107@gmail.com> In-Reply-To: Subject: Re: [Xen-users] Success VGA passthrough on windows 7 x64 with Xen 4.2.1-pre X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset="us-ascii"; Format="flowed" Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org On 28/09/2012 02:34, Dariusz Krempa wrote: > 2012/9/27 Mike Viau: >>> On Fri, 28 Sep 2012 01:29:14 +0800 wrote: >>> >>> Dear Dariusz Krempa, >>> >>> Thank you for your prompt reply. >>> >>> I don't have pci_msitranslate = 1 in my Windows HVM domU config file, so >>> I don't think "pci_msitranslate = 1" is the main cause of my "nasty >>> yellow triangle with error 43". >>> >> I once recorded that the default for the pci_msitranslate option was "1". Not having this in your configuration then is like having it set. Feel free to correct me if I am wrong. I have only gotten VGA pass-through to work with a Windows domU, never in GNU/Linux for some reason. >> >> >> -M >> >> _______________________________________________ >> Xen-users mailing list >> Xen-users@lists.xen.org >> http://lists.xen.org/xen-users > from change set 25525 msitranslate is 0 by deafault > > http://xenbits.xensource.com/hg/staging/xen-unstable.hg/rev/84272cca638a?revcount=120 > > _______________________________________________ > Xen-users mailing list > Xen-users@lists.xen.org > http://lists.xen.org/xen-users > Hi, May I know whether your GTX 560 is a Ti or a non Ti, that is, GTX 560 or GTX 560 Ti? Thank you very much. -- Yours sincerely, Mr. Teo En Ming (Zhang Enming) Singapore _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Thu Sep 27 19:14:38 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Thu, 27 Sep 2012 19:14:38 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1THJWt-0004Y5-OA; Thu, 27 Sep 2012 19:13:47 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1THJWs-0004Y0-QN for Xen-users@lists.xen.org; Thu, 27 Sep 2012 19:13:47 +0000 Received: from [85.158.139.211:39182] by server-2.bemta-5.messagelabs.com id 55/50-28944-965A4605; Thu, 27 Sep 2012 19:13:45 +0000 X-Env-Sender: imperiaonline4@gmail.com X-Msg-Ref: server-14.tower-206.messagelabs.com!1348773223!20172659!1 X-Originating-IP: [209.85.219.45] X-SpamReason: No, hits=0.3 required=7.0 tests=ML_RADAR_SPEW_LINKS_14, RCVD_BY_IP,spamassassin: X-StarScan-Received: X-StarScan-Version: 6.6.1.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 3359 invoked from network); 27 Sep 2012 19:13:45 -0000 Received: from mail-oa0-f45.google.com (HELO mail-oa0-f45.google.com) (209.85.219.45) by server-14.tower-206.messagelabs.com with RC4-SHA encrypted SMTP; 27 Sep 2012 19:13:45 -0000 Received: by oagi18 with SMTP id i18so2894222oag.32 for ; Thu, 27 Sep 2012 12:13:43 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; bh=jlleBk5B2mcUzB6N0b0VQBdXp6+0flCN8lhgAela1K8=; b=dRlL33ZTvqK9QfWbdGRGz7nKYEdAVQRNdQ5q3E6ag8Xj3YfihBgPcRNdI29VW2ob18 UVO6L5eBmg43XXvcCax4KwuJeNSq/imn0Hrcx5BXZOTudHq1Z2lQhUK/2I/wwDnzx3j/ 19G6E07peFu/ztwEGwxCfagYOmTpmreyZHgzgrq4zyehTzVzSG8lBuyPy3BNXM8JVre3 SRMrPwg6UKwzh0xzKyIijKEnMEvo83WMT0dT3Fe0GMHVkJwRo3g0JaO4e9mmZAUjGHlO 1mNJ6c5ljGIgn6v1Ed13Pet3zHub3RiXxmlxe41ywejNJt7zwyN0ESBN9M6XsFFa7GSr WBXA== MIME-Version: 1.0 Received: by 10.60.26.41 with SMTP id i9mr3911717oeg.65.1348773223435; Thu, 27 Sep 2012 12:13:43 -0700 (PDT) Received: by 10.60.146.236 with HTTP; Thu, 27 Sep 2012 12:13:43 -0700 (PDT) In-Reply-To: <5064A0F9.3090304@gmail.com> References: <50645166.2000200@gmail.com> <50647B26.9080903@gmail.com> <50648CEA.9070107@gmail.com> <5064A0F9.3090304@gmail.com> Date: Thu, 27 Sep 2012 21:13:43 +0200 Message-ID: From: Dariusz Krempa To: "xen-users@lists.xen.org" Subject: Re: [Xen-users] Success VGA passthrough on windows 7 x64 with Xen 4.2.1-pre X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org 2012/9/27 Teo En Ming (Zhang Enming) : > On 28/09/2012 02:34, Dariusz Krempa wrote: >> >> 2012/9/27 Mike Viau: >>>> >>>> On Fri, 28 Sep 2012 01:29:14 +0800 >>>> wrote: >>>> >>>> Dear Dariusz Krempa, >>>> >>>> Thank you for your prompt reply. >>>> >>>> I don't have pci_msitranslate = 1 in my Windows HVM domU config file, so >>>> I don't think "pci_msitranslate = 1" is the main cause of my "nasty >>>> yellow triangle with error 43". >>>> >>> I once recorded that the default for the pci_msitranslate option was "1". >>> Not having this in your configuration then is like having it set. Feel free >>> to correct me if I am wrong. I have only gotten VGA pass-through to work >>> with a Windows domU, never in GNU/Linux for some reason. >>> >>> >>> -M >>> >>> _______________________________________________ >>> Xen-users mailing list >>> Xen-users@lists.xen.org >>> http://lists.xen.org/xen-users >> >> from change set 25525 msitranslate is 0 by deafault >> >> >> http://xenbits.xensource.com/hg/staging/xen-unstable.hg/rev/84272cca638a?revcount=120 >> >> _______________________________________________ >> Xen-users mailing list >> Xen-users@lists.xen.org >> http://lists.xen.org/xen-users >> > Hi, > > May I know whether your GTX 560 is a Ti or a non Ti, that is, GTX 560 or GTX > 560 Ti? > > > Thank you very much. > > -- > Yours sincerely, > > Mr. Teo En Ming (Zhang Enming) > Singapore > just 560, without Ti _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Thu Sep 27 19:14:38 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Thu, 27 Sep 2012 19:14:38 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1THJWt-0004Y5-OA; Thu, 27 Sep 2012 19:13:47 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1THJWs-0004Y0-QN for Xen-users@lists.xen.org; Thu, 27 Sep 2012 19:13:47 +0000 Received: from [85.158.139.211:39182] by server-2.bemta-5.messagelabs.com id 55/50-28944-965A4605; Thu, 27 Sep 2012 19:13:45 +0000 X-Env-Sender: imperiaonline4@gmail.com X-Msg-Ref: server-14.tower-206.messagelabs.com!1348773223!20172659!1 X-Originating-IP: [209.85.219.45] X-SpamReason: No, hits=0.3 required=7.0 tests=ML_RADAR_SPEW_LINKS_14, RCVD_BY_IP,spamassassin: X-StarScan-Received: X-StarScan-Version: 6.6.1.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 3359 invoked from network); 27 Sep 2012 19:13:45 -0000 Received: from mail-oa0-f45.google.com (HELO mail-oa0-f45.google.com) (209.85.219.45) by server-14.tower-206.messagelabs.com with RC4-SHA encrypted SMTP; 27 Sep 2012 19:13:45 -0000 Received: by oagi18 with SMTP id i18so2894222oag.32 for ; Thu, 27 Sep 2012 12:13:43 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; bh=jlleBk5B2mcUzB6N0b0VQBdXp6+0flCN8lhgAela1K8=; b=dRlL33ZTvqK9QfWbdGRGz7nKYEdAVQRNdQ5q3E6ag8Xj3YfihBgPcRNdI29VW2ob18 UVO6L5eBmg43XXvcCax4KwuJeNSq/imn0Hrcx5BXZOTudHq1Z2lQhUK/2I/wwDnzx3j/ 19G6E07peFu/ztwEGwxCfagYOmTpmreyZHgzgrq4zyehTzVzSG8lBuyPy3BNXM8JVre3 SRMrPwg6UKwzh0xzKyIijKEnMEvo83WMT0dT3Fe0GMHVkJwRo3g0JaO4e9mmZAUjGHlO 1mNJ6c5ljGIgn6v1Ed13Pet3zHub3RiXxmlxe41ywejNJt7zwyN0ESBN9M6XsFFa7GSr WBXA== MIME-Version: 1.0 Received: by 10.60.26.41 with SMTP id i9mr3911717oeg.65.1348773223435; Thu, 27 Sep 2012 12:13:43 -0700 (PDT) Received: by 10.60.146.236 with HTTP; Thu, 27 Sep 2012 12:13:43 -0700 (PDT) In-Reply-To: <5064A0F9.3090304@gmail.com> References: <50645166.2000200@gmail.com> <50647B26.9080903@gmail.com> <50648CEA.9070107@gmail.com> <5064A0F9.3090304@gmail.com> Date: Thu, 27 Sep 2012 21:13:43 +0200 Message-ID: From: Dariusz Krempa To: "xen-users@lists.xen.org" Subject: Re: [Xen-users] Success VGA passthrough on windows 7 x64 with Xen 4.2.1-pre X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org 2012/9/27 Teo En Ming (Zhang Enming) : > On 28/09/2012 02:34, Dariusz Krempa wrote: >> >> 2012/9/27 Mike Viau: >>>> >>>> On Fri, 28 Sep 2012 01:29:14 +0800 >>>> wrote: >>>> >>>> Dear Dariusz Krempa, >>>> >>>> Thank you for your prompt reply. >>>> >>>> I don't have pci_msitranslate = 1 in my Windows HVM domU config file, so >>>> I don't think "pci_msitranslate = 1" is the main cause of my "nasty >>>> yellow triangle with error 43". >>>> >>> I once recorded that the default for the pci_msitranslate option was "1". >>> Not having this in your configuration then is like having it set. Feel free >>> to correct me if I am wrong. I have only gotten VGA pass-through to work >>> with a Windows domU, never in GNU/Linux for some reason. >>> >>> >>> -M >>> >>> _______________________________________________ >>> Xen-users mailing list >>> Xen-users@lists.xen.org >>> http://lists.xen.org/xen-users >> >> from change set 25525 msitranslate is 0 by deafault >> >> >> http://xenbits.xensource.com/hg/staging/xen-unstable.hg/rev/84272cca638a?revcount=120 >> >> _______________________________________________ >> Xen-users mailing list >> Xen-users@lists.xen.org >> http://lists.xen.org/xen-users >> > Hi, > > May I know whether your GTX 560 is a Ti or a non Ti, that is, GTX 560 or GTX > 560 Ti? > > > Thank you very much. > > -- > Yours sincerely, > > Mr. Teo En Ming (Zhang Enming) > Singapore > just 560, without Ti _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Thu Sep 27 19:29:12 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Thu, 27 Sep 2012 19:29:12 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1THJl5-0004sS-Oz; Thu, 27 Sep 2012 19:28:27 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1THJl4-0004sC-20 for xen-users@lists.xensource.com; Thu, 27 Sep 2012 19:28:26 +0000 Received: from [85.158.143.99:15352] by server-1.bemta-4.messagelabs.com id EA/51-05684-8D8A4605; Thu, 27 Sep 2012 19:28:24 +0000 X-Env-Sender: dan.magenheimer@oracle.com X-Msg-Ref: server-14.tower-216.messagelabs.com!1348774103!22433321!1 X-Originating-IP: [148.87.113.117] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogMTQ4Ljg3LjExMy4xMTcgPT4gNzY4ODAw\n X-StarScan-Received: X-StarScan-Version: 6.6.1.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 1801 invoked from network); 27 Sep 2012 19:28:24 -0000 Received: from rcsinet15.oracle.com (HELO rcsinet15.oracle.com) (148.87.113.117) by server-14.tower-216.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 27 Sep 2012 19:28:24 -0000 Received: from ucsinet21.oracle.com (ucsinet21.oracle.com [156.151.31.93]) by rcsinet15.oracle.com (Sentrion-MTA-4.2.2/Sentrion-MTA-4.2.2) with ESMTP id q8RJSBfj006707 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Thu, 27 Sep 2012 19:28:12 GMT Received: from acsmt356.oracle.com (acsmt356.oracle.com [141.146.40.156]) by ucsinet21.oracle.com (8.14.4+Sun/8.14.4) with ESMTP id q8RJS7a7001175 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 27 Sep 2012 19:28:08 GMT Received: from abhmt117.oracle.com (abhmt117.oracle.com [141.146.116.69]) by acsmt356.oracle.com (8.12.11.20060308/8.12.11) with ESMTP id q8RJS5jG003863; Thu, 27 Sep 2012 14:28:05 -0500 MIME-Version: 1.0 Message-ID: <65395f62-74e5-4910-b701-8df629c2ce3b@default> Date: Thu, 27 Sep 2012 12:27:53 -0700 (PDT) From: Dan Magenheimer To: Mauro , Olivier Hanesse References: <68c41dd8-9195-41b0-83d7-9242b8eff809@default> In-Reply-To: X-Priority: 3 X-Mailer: Oracle Beehive Extensions for Outlook 2.0.1.7 (607090) [OL 12.0.6661.5003 (x86)] X-Source-IP: ucsinet21.oracle.com [156.151.31.93] Cc: Jeremy Fitzhardinge , xen-devel@lists.xensource.com, Keir Fraser , Jan Beulich , Keir Fraser , Xen Users , Mark Adams Subject: Re: [Xen-users] [Xen-devel] Xen 4 TSC problems X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org > From: Mauro [mailto:mrsanna1@gmail.com] > Sent: Thursday, September 27, 2012 9:55 AM > To: Olivier Hanesse > Cc: Dan Magenheimer; Jeremy Fitzhardinge; xen-devel@lists.xensource.com; Keir Fraser; Jan Beulich; > Keir Fraser; Xen Users; Mark Adams > Subject: Re: [Xen-users] Re: [Xen-devel] Xen 4 TSC problems > > On 28 February 2011 16:54, Olivier Hanesse wrote: > > Yes this is what I mean. > > I am glad to hear that it isn't a bad sign :) > > I thought of a bad sign, because on system with "reliable TSC", this counter > > is always 0. > > Hey men. > I have exactly the same problem. > I have two cluster nodes. > Server are two HP Proliant DL 580 G4 with four Quad Core Intel(R) > Xeon(R) CPU E7330 @ 2.40GHz. > I'm running debian squeeze in dom0s end domUs. Hi Mauro -- There's been a lot of work on clocks since 4.0 (by other Xen developers, not me). I don't think this specific problem was ever reproduced by a developer so I don't think anyone knows if it has been already fixed or not, nor are there any plans to backport all the timer work to 4.0. You might try upgrading your Xen hypervisor to the just-released Xen 4.2 [1] and see if the problem goes away. If the problem still exists in 4.2, it may be easier to get some developer to pay attention to it. It may be specific hardware or processors or power management or firmware or even dom0 kernel, so the first thing to do is try later hypervisor bits. Sorry I can't be more helpful. Good luck! Dan [1] Sorry, I'm not familiar with the 4.0->4.2 upgrade process so you may want to confirm with others. > xm info: > > host : xen-p01 > release : 2.6.32-5-xen-amd64 > version : #1 SMP Sun May 6 08:57:29 UTC 2012 > machine : x86_64 > nr_cpus : 16 > nr_nodes : 1 > cores_per_socket : 4 > threads_per_core : 1 > cpu_mhz : 2400 > hw_caps : > bfebfbff:20100800:00000000:00000940:0004e3bd:00000000:00000001:00000000 > virt_caps : hvm > total_memory : 65532 > free_memory : 40317 > node_to_cpu : node0:0-15 > node_to_memory : node0:40317 > node_to_dma32_mem : node0:3256 > max_node_id : 0 > xen_major : 4 > xen_minor : 0 > xen_extra : .1 > xen_caps : xen-3.0-x86_64 xen-3.0-x86_32p hvm-3.0-x86_32 > hvm-3.0-x86_32p hvm-3.0-x86_64 > xen_scheduler : credit > xen_pagesize : 4096 > platform_params : virt_start=0xffff800000000000 > xen_changeset : unavailable > xen_commandline : placeholder dom0_mem=3072M loglvl=warning > guest_loglvl=warning > cc_compiler : gcc version 4.4.5 (Debian 4.4.5-8) > cc_compile_by : ultrotter > cc_compile_domain : debian.org > cc_compile_date : Sat Sep 8 19:15:46 UTC 2012 > xend_config_format : 4 > > I'm experiencing weekly a clock jump ahead of about 50 minutes on dom0. > I'm seriously in trouble because it cause every time a reboot of one > of the two nodes clusters. _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Thu Sep 27 19:29:12 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Thu, 27 Sep 2012 19:29:12 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1THJl5-0004sS-Oz; Thu, 27 Sep 2012 19:28:27 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1THJl4-0004sC-20 for xen-users@lists.xensource.com; Thu, 27 Sep 2012 19:28:26 +0000 Received: from [85.158.143.99:15352] by server-1.bemta-4.messagelabs.com id EA/51-05684-8D8A4605; Thu, 27 Sep 2012 19:28:24 +0000 X-Env-Sender: dan.magenheimer@oracle.com X-Msg-Ref: server-14.tower-216.messagelabs.com!1348774103!22433321!1 X-Originating-IP: [148.87.113.117] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogMTQ4Ljg3LjExMy4xMTcgPT4gNzY4ODAw\n X-StarScan-Received: X-StarScan-Version: 6.6.1.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 1801 invoked from network); 27 Sep 2012 19:28:24 -0000 Received: from rcsinet15.oracle.com (HELO rcsinet15.oracle.com) (148.87.113.117) by server-14.tower-216.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 27 Sep 2012 19:28:24 -0000 Received: from ucsinet21.oracle.com (ucsinet21.oracle.com [156.151.31.93]) by rcsinet15.oracle.com (Sentrion-MTA-4.2.2/Sentrion-MTA-4.2.2) with ESMTP id q8RJSBfj006707 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Thu, 27 Sep 2012 19:28:12 GMT Received: from acsmt356.oracle.com (acsmt356.oracle.com [141.146.40.156]) by ucsinet21.oracle.com (8.14.4+Sun/8.14.4) with ESMTP id q8RJS7a7001175 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 27 Sep 2012 19:28:08 GMT Received: from abhmt117.oracle.com (abhmt117.oracle.com [141.146.116.69]) by acsmt356.oracle.com (8.12.11.20060308/8.12.11) with ESMTP id q8RJS5jG003863; Thu, 27 Sep 2012 14:28:05 -0500 MIME-Version: 1.0 Message-ID: <65395f62-74e5-4910-b701-8df629c2ce3b@default> Date: Thu, 27 Sep 2012 12:27:53 -0700 (PDT) From: Dan Magenheimer To: Mauro , Olivier Hanesse References: <68c41dd8-9195-41b0-83d7-9242b8eff809@default> In-Reply-To: X-Priority: 3 X-Mailer: Oracle Beehive Extensions for Outlook 2.0.1.7 (607090) [OL 12.0.6661.5003 (x86)] X-Source-IP: ucsinet21.oracle.com [156.151.31.93] Cc: Jeremy Fitzhardinge , xen-devel@lists.xensource.com, Keir Fraser , Jan Beulich , Keir Fraser , Xen Users , Mark Adams Subject: Re: [Xen-users] [Xen-devel] Xen 4 TSC problems X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org > From: Mauro [mailto:mrsanna1@gmail.com] > Sent: Thursday, September 27, 2012 9:55 AM > To: Olivier Hanesse > Cc: Dan Magenheimer; Jeremy Fitzhardinge; xen-devel@lists.xensource.com; Keir Fraser; Jan Beulich; > Keir Fraser; Xen Users; Mark Adams > Subject: Re: [Xen-users] Re: [Xen-devel] Xen 4 TSC problems > > On 28 February 2011 16:54, Olivier Hanesse wrote: > > Yes this is what I mean. > > I am glad to hear that it isn't a bad sign :) > > I thought of a bad sign, because on system with "reliable TSC", this counter > > is always 0. > > Hey men. > I have exactly the same problem. > I have two cluster nodes. > Server are two HP Proliant DL 580 G4 with four Quad Core Intel(R) > Xeon(R) CPU E7330 @ 2.40GHz. > I'm running debian squeeze in dom0s end domUs. Hi Mauro -- There's been a lot of work on clocks since 4.0 (by other Xen developers, not me). I don't think this specific problem was ever reproduced by a developer so I don't think anyone knows if it has been already fixed or not, nor are there any plans to backport all the timer work to 4.0. You might try upgrading your Xen hypervisor to the just-released Xen 4.2 [1] and see if the problem goes away. If the problem still exists in 4.2, it may be easier to get some developer to pay attention to it. It may be specific hardware or processors or power management or firmware or even dom0 kernel, so the first thing to do is try later hypervisor bits. Sorry I can't be more helpful. Good luck! Dan [1] Sorry, I'm not familiar with the 4.0->4.2 upgrade process so you may want to confirm with others. > xm info: > > host : xen-p01 > release : 2.6.32-5-xen-amd64 > version : #1 SMP Sun May 6 08:57:29 UTC 2012 > machine : x86_64 > nr_cpus : 16 > nr_nodes : 1 > cores_per_socket : 4 > threads_per_core : 1 > cpu_mhz : 2400 > hw_caps : > bfebfbff:20100800:00000000:00000940:0004e3bd:00000000:00000001:00000000 > virt_caps : hvm > total_memory : 65532 > free_memory : 40317 > node_to_cpu : node0:0-15 > node_to_memory : node0:40317 > node_to_dma32_mem : node0:3256 > max_node_id : 0 > xen_major : 4 > xen_minor : 0 > xen_extra : .1 > xen_caps : xen-3.0-x86_64 xen-3.0-x86_32p hvm-3.0-x86_32 > hvm-3.0-x86_32p hvm-3.0-x86_64 > xen_scheduler : credit > xen_pagesize : 4096 > platform_params : virt_start=0xffff800000000000 > xen_changeset : unavailable > xen_commandline : placeholder dom0_mem=3072M loglvl=warning > guest_loglvl=warning > cc_compiler : gcc version 4.4.5 (Debian 4.4.5-8) > cc_compile_by : ultrotter > cc_compile_domain : debian.org > cc_compile_date : Sat Sep 8 19:15:46 UTC 2012 > xend_config_format : 4 > > I'm experiencing weekly a clock jump ahead of about 50 minutes on dom0. > I'm seriously in trouble because it cause every time a reboot of one > of the two nodes clusters. _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Thu Sep 27 20:08:35 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Thu, 27 Sep 2012 20:08:35 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1THKMu-0005lJ-Os; Thu, 27 Sep 2012 20:07:32 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1THKMt-0005lE-Dq for Xen-users@lists.xen.org; Thu, 27 Sep 2012 20:07:31 +0000 Received: from [85.158.138.51:20545] by server-7.bemta-3.messagelabs.com id 3A/57-15765-202B4605; Thu, 27 Sep 2012 20:07:30 +0000 X-Env-Sender: imperiaonline4@gmail.com X-Msg-Ref: server-11.tower-174.messagelabs.com!1348776448!32231127!1 X-Originating-IP: [209.85.214.173] X-SpamReason: No, hits=0.3 required=7.0 tests=ML_RADAR_SPEW_LINKS_14, RCVD_BY_IP,spamassassin: X-StarScan-Received: X-StarScan-Version: 6.6.1.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 17436 invoked from network); 27 Sep 2012 20:07:30 -0000 Received: from mail-ob0-f173.google.com (HELO mail-ob0-f173.google.com) (209.85.214.173) by server-11.tower-174.messagelabs.com with RC4-SHA encrypted SMTP; 27 Sep 2012 20:07:30 -0000 Received: by obbwc18 with SMTP id wc18so172167obb.32 for ; Thu, 27 Sep 2012 13:07:28 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; bh=ztiCHnSsZqdTV7/hPpBFJ1RR/oBn6jttxFV6a9AQV84=; b=HtMGh8fC07jmm6+GWS8DdRDQ9cB8R6lqkxyyqR3gW7idplKrRzXte8xU5Z1Y2ISG8b +60Inw6MhgoslIXUoUsxxZ/y3h7sME5j9Z+UB/bFA8WBKT0HXU96N199FfPCdF72n6y2 /2UigIpnthHPsxfRf4qnlfgfufLcGDVUV8Fgv5ESuzck9nsQZtz/OKfXDKgrfgupdIyY 6dvKElNfloTvq6ccJuq7EBuk6ekBNGftPaD9JysyAnMhJfVo2vQuBgxFg/M2QqYydUqF q0W4uUQWfA5FFFxQ+dEN8sroTKR0Wa1fDO/6vTPGdHJsk+/yfV5OTIWcOP7yajRljGCm 9w0w== MIME-Version: 1.0 Received: by 10.182.172.74 with SMTP id ba10mr4067644obc.83.1348776448288; Thu, 27 Sep 2012 13:07:28 -0700 (PDT) Received: by 10.60.146.236 with HTTP; Thu, 27 Sep 2012 13:07:28 -0700 (PDT) In-Reply-To: References: <50645166.2000200@gmail.com> <50647B26.9080903@gmail.com> <50648CEA.9070107@gmail.com> <5064A0F9.3090304@gmail.com> Date: Thu, 27 Sep 2012 22:07:28 +0200 Message-ID: From: Dariusz Krempa To: "xen-users@lists.xen.org" Subject: Re: [Xen-users] Success VGA passthrough on windows 7 x64 with Xen 4.2.1-pre X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org I know I shouldn't reply to myself, but I have hvm DomU with windows server 2008 r2, and i only turn on gfx_passthrough and pci=['1:00.0'], created guest and installed nvidia drivers 275.50 and full success. Just like with windows 7. I'm only having problems with windows 8 cause first available drivers are 29x.xx and they don't work. I have partial success with windows 8 and drivers 275.33 for vista/win7, cause system see my VGA but gpu-z shows that only DirectComputing is enabled, no CUDA, no PhysX, no OpenCL. _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Thu Sep 27 20:08:35 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Thu, 27 Sep 2012 20:08:35 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1THKMu-0005lJ-Os; Thu, 27 Sep 2012 20:07:32 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1THKMt-0005lE-Dq for Xen-users@lists.xen.org; Thu, 27 Sep 2012 20:07:31 +0000 Received: from [85.158.138.51:20545] by server-7.bemta-3.messagelabs.com id 3A/57-15765-202B4605; Thu, 27 Sep 2012 20:07:30 +0000 X-Env-Sender: imperiaonline4@gmail.com X-Msg-Ref: server-11.tower-174.messagelabs.com!1348776448!32231127!1 X-Originating-IP: [209.85.214.173] X-SpamReason: No, hits=0.3 required=7.0 tests=ML_RADAR_SPEW_LINKS_14, RCVD_BY_IP,spamassassin: X-StarScan-Received: X-StarScan-Version: 6.6.1.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 17436 invoked from network); 27 Sep 2012 20:07:30 -0000 Received: from mail-ob0-f173.google.com (HELO mail-ob0-f173.google.com) (209.85.214.173) by server-11.tower-174.messagelabs.com with RC4-SHA encrypted SMTP; 27 Sep 2012 20:07:30 -0000 Received: by obbwc18 with SMTP id wc18so172167obb.32 for ; Thu, 27 Sep 2012 13:07:28 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; bh=ztiCHnSsZqdTV7/hPpBFJ1RR/oBn6jttxFV6a9AQV84=; b=HtMGh8fC07jmm6+GWS8DdRDQ9cB8R6lqkxyyqR3gW7idplKrRzXte8xU5Z1Y2ISG8b +60Inw6MhgoslIXUoUsxxZ/y3h7sME5j9Z+UB/bFA8WBKT0HXU96N199FfPCdF72n6y2 /2UigIpnthHPsxfRf4qnlfgfufLcGDVUV8Fgv5ESuzck9nsQZtz/OKfXDKgrfgupdIyY 6dvKElNfloTvq6ccJuq7EBuk6ekBNGftPaD9JysyAnMhJfVo2vQuBgxFg/M2QqYydUqF q0W4uUQWfA5FFFxQ+dEN8sroTKR0Wa1fDO/6vTPGdHJsk+/yfV5OTIWcOP7yajRljGCm 9w0w== MIME-Version: 1.0 Received: by 10.182.172.74 with SMTP id ba10mr4067644obc.83.1348776448288; Thu, 27 Sep 2012 13:07:28 -0700 (PDT) Received: by 10.60.146.236 with HTTP; Thu, 27 Sep 2012 13:07:28 -0700 (PDT) In-Reply-To: References: <50645166.2000200@gmail.com> <50647B26.9080903@gmail.com> <50648CEA.9070107@gmail.com> <5064A0F9.3090304@gmail.com> Date: Thu, 27 Sep 2012 22:07:28 +0200 Message-ID: From: Dariusz Krempa To: "xen-users@lists.xen.org" Subject: Re: [Xen-users] Success VGA passthrough on windows 7 x64 with Xen 4.2.1-pre X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org I know I shouldn't reply to myself, but I have hvm DomU with windows server 2008 r2, and i only turn on gfx_passthrough and pci=['1:00.0'], created guest and installed nvidia drivers 275.50 and full success. Just like with windows 7. I'm only having problems with windows 8 cause first available drivers are 29x.xx and they don't work. I have partial success with windows 8 and drivers 275.33 for vista/win7, cause system see my VGA but gpu-z shows that only DirectComputing is enabled, no CUDA, no PhysX, no OpenCL. _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Thu Sep 27 20:59:53 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Thu, 27 Sep 2012 20:59:53 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1THLAO-0006Rd-Jr; Thu, 27 Sep 2012 20:58:40 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1THLAM-0006RY-8n for xen-users@lists.xen.org; Thu, 27 Sep 2012 20:58:38 +0000 Received: from [85.158.137.99:51589] by server-11.bemta-3.messagelabs.com id 68/CC-21460-CFDB4605; Thu, 27 Sep 2012 20:58:36 +0000 X-Env-Sender: maik.brauer@mbs-systems.net X-Msg-Ref: server-5.tower-217.messagelabs.com!1348779516!14669582!1 X-Originating-IP: [188.40.240.248] X-SpamReason: No, hits=0.5 required=7.0 tests=BODY_RANDOM_LONG X-StarScan-Received: X-StarScan-Version: 6.6.1.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 21327 invoked from network); 27 Sep 2012 20:58:36 -0000 Received: from mx1.mbs-systems.net (HELO mx1.mbs-systems.net) (188.40.240.248) by server-5.tower-217.messagelabs.com with SMTP; 27 Sep 2012 20:58:36 -0000 Received: from localhost (localhost [127.0.0.1]) by mx1.mbs-systems.net (Postfix) with ESMTP id 90D745C30B; Thu, 27 Sep 2012 22:59:52 +0200 (CEST) Received: from mx1.mbs-systems.net ([127.0.0.1]) by localhost (mta.mbs-systems.net [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id CQfxEXr64yo9; Thu, 27 Sep 2012 22:59:51 +0200 (CEST) Received: from maiks-macbookpro.fritz.box (dslb-188-109-136-209.pools.arcor-ip.net [188.109.136.209]) by mx1.mbs-systems.net (Postfix) with ESMTPSA id EE5A05C2DA; Thu, 27 Sep 2012 22:59:50 +0200 (CEST) Mime-Version: 1.0 (Apple Message framework v1283) From: Maik Brauer In-Reply-To: <1347528483.24226.75.camel@zakaz.uk.xensource.com> Date: Thu, 27 Sep 2012 22:58:30 +0200 Message-Id: References: <9F8FD2B0-450A-4A6E-A929-BA240ED1D997@mbs-systems.net> <1346746297.32462.37.camel@zakaz.uk.xensource.com> <1347266386.5305.17.camel@zakaz.uk.xensource.com> <4957C391-6070-47C1-A2AC-991ED1C1766A@mbs-systems.net> <1347289853.5305.105.camel@zakaz.uk.xensource.com> <4BCC413D-1697-4681-AF28-118D1623AF1C@mbs-systems.net> <1347445398.24226.37.camel@zakaz.uk.xensource.com> <5CB14C04-2A76-4747-8209-EB5122DF7239@mbs-systems.net> <1347515481.25803.36.camel@dagon.hellion.org.uk> <1347526716.24226.70.camel@zakaz.uk.xensource.com> <051FE94A-4663-4044-B7E1-5A518CF13A18@mbs-systems.net> <1347528483.24226.75.camel@zakaz.uk.xensource.com> To: Ian Campbell X-Mailer: Apple Mail (2.1283) Cc: "xen-users@lists.xen.org" Subject: Re: [Xen-users] Dom0 crashed when rebooting whilst DomU are running X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org On Sep 13, 2012, at 11:28 AM, Ian Campbell wrote: > On Thu, 2012-09-13 at 10:09 +0100, Maik Brauer wrote: >> On Sep 13, 2012, at 10:58 AM, Ian Campbell wrote: >> >>> On Thu, 2012-09-13 at 09:55 +0100, Maik Brauer wrote: >>>> I will try to install it on a WHEEZY machine for testing. But this will not help me, because >>>> at the end I need it working on Production machines. And I do not want to install this WHEEZY in production. >>> >>> Why not install a test system with exactly the same software as you use >>> in production? >>> >> Yes, as I said, I will install a test system with the software I want to use. But even this is working afterwards, I will >> not use this in production, because wheezy is still not stable. > > Why Wheezy? What we need here is a system which has the same software as > you use in production, which reproduces the issue and which you can play > with and experiment with as much as you like without disturbing your > customers. I tried it on several VM's and Dedicated Servers with SQUEEZE and the issue is still persistent. > > I'm not asking you to install Wheezy here, although if you think it will > help and you can reproduce the issue with that configuration then go > ahead. When using the Back-ported Kernel in SQUEEZE (vmlinuz-3.2.0-0.bpo.3-amd64) there is no issue anymore. So it seems that it is happening with the last SQUEEZE Kernel (vmlinuz-2.6.32-5-xen-amd64). This is definitely something in relation with this kernel. > > Please just be sure to be very clear about which exact environment any > specific results you report were obtained in. > > Ian. > _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Thu Sep 27 20:59:53 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Thu, 27 Sep 2012 20:59:53 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1THLAO-0006Rd-Jr; Thu, 27 Sep 2012 20:58:40 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1THLAM-0006RY-8n for xen-users@lists.xen.org; Thu, 27 Sep 2012 20:58:38 +0000 Received: from [85.158.137.99:51589] by server-11.bemta-3.messagelabs.com id 68/CC-21460-CFDB4605; Thu, 27 Sep 2012 20:58:36 +0000 X-Env-Sender: maik.brauer@mbs-systems.net X-Msg-Ref: server-5.tower-217.messagelabs.com!1348779516!14669582!1 X-Originating-IP: [188.40.240.248] X-SpamReason: No, hits=0.5 required=7.0 tests=BODY_RANDOM_LONG X-StarScan-Received: X-StarScan-Version: 6.6.1.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 21327 invoked from network); 27 Sep 2012 20:58:36 -0000 Received: from mx1.mbs-systems.net (HELO mx1.mbs-systems.net) (188.40.240.248) by server-5.tower-217.messagelabs.com with SMTP; 27 Sep 2012 20:58:36 -0000 Received: from localhost (localhost [127.0.0.1]) by mx1.mbs-systems.net (Postfix) with ESMTP id 90D745C30B; Thu, 27 Sep 2012 22:59:52 +0200 (CEST) Received: from mx1.mbs-systems.net ([127.0.0.1]) by localhost (mta.mbs-systems.net [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id CQfxEXr64yo9; Thu, 27 Sep 2012 22:59:51 +0200 (CEST) Received: from maiks-macbookpro.fritz.box (dslb-188-109-136-209.pools.arcor-ip.net [188.109.136.209]) by mx1.mbs-systems.net (Postfix) with ESMTPSA id EE5A05C2DA; Thu, 27 Sep 2012 22:59:50 +0200 (CEST) Mime-Version: 1.0 (Apple Message framework v1283) From: Maik Brauer In-Reply-To: <1347528483.24226.75.camel@zakaz.uk.xensource.com> Date: Thu, 27 Sep 2012 22:58:30 +0200 Message-Id: References: <9F8FD2B0-450A-4A6E-A929-BA240ED1D997@mbs-systems.net> <1346746297.32462.37.camel@zakaz.uk.xensource.com> <1347266386.5305.17.camel@zakaz.uk.xensource.com> <4957C391-6070-47C1-A2AC-991ED1C1766A@mbs-systems.net> <1347289853.5305.105.camel@zakaz.uk.xensource.com> <4BCC413D-1697-4681-AF28-118D1623AF1C@mbs-systems.net> <1347445398.24226.37.camel@zakaz.uk.xensource.com> <5CB14C04-2A76-4747-8209-EB5122DF7239@mbs-systems.net> <1347515481.25803.36.camel@dagon.hellion.org.uk> <1347526716.24226.70.camel@zakaz.uk.xensource.com> <051FE94A-4663-4044-B7E1-5A518CF13A18@mbs-systems.net> <1347528483.24226.75.camel@zakaz.uk.xensource.com> To: Ian Campbell X-Mailer: Apple Mail (2.1283) Cc: "xen-users@lists.xen.org" Subject: Re: [Xen-users] Dom0 crashed when rebooting whilst DomU are running X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org On Sep 13, 2012, at 11:28 AM, Ian Campbell wrote: > On Thu, 2012-09-13 at 10:09 +0100, Maik Brauer wrote: >> On Sep 13, 2012, at 10:58 AM, Ian Campbell wrote: >> >>> On Thu, 2012-09-13 at 09:55 +0100, Maik Brauer wrote: >>>> I will try to install it on a WHEEZY machine for testing. But this will not help me, because >>>> at the end I need it working on Production machines. And I do not want to install this WHEEZY in production. >>> >>> Why not install a test system with exactly the same software as you use >>> in production? >>> >> Yes, as I said, I will install a test system with the software I want to use. But even this is working afterwards, I will >> not use this in production, because wheezy is still not stable. > > Why Wheezy? What we need here is a system which has the same software as > you use in production, which reproduces the issue and which you can play > with and experiment with as much as you like without disturbing your > customers. I tried it on several VM's and Dedicated Servers with SQUEEZE and the issue is still persistent. > > I'm not asking you to install Wheezy here, although if you think it will > help and you can reproduce the issue with that configuration then go > ahead. When using the Back-ported Kernel in SQUEEZE (vmlinuz-3.2.0-0.bpo.3-amd64) there is no issue anymore. So it seems that it is happening with the last SQUEEZE Kernel (vmlinuz-2.6.32-5-xen-amd64). This is definitely something in relation with this kernel. > > Please just be sure to be very clear about which exact environment any > specific results you report were obtained in. > > Ian. > _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Thu Sep 27 21:43:13 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Thu, 27 Sep 2012 21:43:13 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1THLqT-0007Bo-8z; Thu, 27 Sep 2012 21:42:09 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1THLqS-0007Bf-4Q for xen-users@lists.xensource.com; Thu, 27 Sep 2012 21:42:08 +0000 Received: from [85.158.139.211:19125] by server-14.bemta-5.messagelabs.com id 3D/0B-05772-E28C4605; Thu, 27 Sep 2012 21:42:06 +0000 X-Env-Sender: mrsanna1@gmail.com X-Msg-Ref: server-13.tower-206.messagelabs.com!1348782125!16262943!1 X-Originating-IP: [209.85.220.171] X-SpamReason: No, hits=0.3 required=7.0 tests=ML_RADAR_SPEW_LINKS_14, RCVD_BY_IP,spamassassin: X-StarScan-Received: X-StarScan-Version: 6.6.1.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 5354 invoked from network); 27 Sep 2012 21:42:06 -0000 Received: from mail-vc0-f171.google.com (HELO mail-vc0-f171.google.com) (209.85.220.171) by server-13.tower-206.messagelabs.com with RC4-SHA encrypted SMTP; 27 Sep 2012 21:42:06 -0000 Received: by vcmm18 with SMTP id m18so3275070vcm.30 for ; Thu, 27 Sep 2012 14:42:05 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=6u/CWOMDIWFn0pMcOa4MFkHslWKhQfUNGeq/2jWGYow=; b=X5i1JQjQjSS5mZ+qRPViXSafcjDVH64K73F+C/grHojoZp8nkmb7mbJpPuI5gf3hBt OS+BupUGGK3UypUKcTIl6MARFwSNAIZmJfpx/x4GS3Wg6KqV6jB8PGqJUEGYfgfDGiQq hw6U8qupdbvFNf60oaMoI+aARyFkUi/dBmMNr0g3UGobR5oAv+7NSv6bCrHpUjTztbe4 xwU6kK0THVh6k2vkaZ6XlDzwykfwv+0cKnG7DWE8GLU+gnM9FcwnHxI3X4asunx2uIIa z6BzJ8BeT4W8ubcd68nYcCmMEN0L6ud90oNqF0t0F7909GXEuSIExPnLLFv7Oa24yDKg krSw== MIME-Version: 1.0 Received: by 10.220.116.9 with SMTP id k9mr2991072vcq.0.1348782125006; Thu, 27 Sep 2012 14:42:05 -0700 (PDT) Received: by 10.58.207.75 with HTTP; Thu, 27 Sep 2012 14:42:04 -0700 (PDT) In-Reply-To: References: <68c41dd8-9195-41b0-83d7-9242b8eff809@default> <65395f62-74e5-4910-b701-8df629c2ce3b@default> Date: Thu, 27 Sep 2012 23:42:04 +0200 Message-ID: From: Mauro To: Olivier Hanesse Cc: Dan Magenheimer , xen-devel@lists.xensource.com, Keir Fraser , Jeremy Fitzhardinge , Jan Beulich , Keir Fraser , Xen Users , Mark Adams Subject: Re: [Xen-users] [Xen-devel] Xen 4 TSC problems X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org On 27 September 2012 23:28, Olivier Hanesse wrote: > Hello, > > From my point of view, this was a kind of xen hardware "incompatibility/bug" > : I was able to reproduce this bug on more than 50 identical servers, but > not on another farm of servers with a different hardware. > Xen version, Debian Kernel was exactly the same on both farm. Yes I think so. The problem is where I use debian squeeze with xen 4.0. In another server with the same hardware but with debian lenny and xen 3.0 I have no problems. I've read that a workaround is to set clocksource=pit on the xen boot line in the grub conf, I hope this works because I can't change hardware. _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Thu Sep 27 21:43:13 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Thu, 27 Sep 2012 21:43:13 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1THLqT-0007Bo-8z; Thu, 27 Sep 2012 21:42:09 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1THLqS-0007Bf-4Q for xen-users@lists.xensource.com; Thu, 27 Sep 2012 21:42:08 +0000 Received: from [85.158.139.211:19125] by server-14.bemta-5.messagelabs.com id 3D/0B-05772-E28C4605; Thu, 27 Sep 2012 21:42:06 +0000 X-Env-Sender: mrsanna1@gmail.com X-Msg-Ref: server-13.tower-206.messagelabs.com!1348782125!16262943!1 X-Originating-IP: [209.85.220.171] X-SpamReason: No, hits=0.3 required=7.0 tests=ML_RADAR_SPEW_LINKS_14, RCVD_BY_IP,spamassassin: X-StarScan-Received: X-StarScan-Version: 6.6.1.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 5354 invoked from network); 27 Sep 2012 21:42:06 -0000 Received: from mail-vc0-f171.google.com (HELO mail-vc0-f171.google.com) (209.85.220.171) by server-13.tower-206.messagelabs.com with RC4-SHA encrypted SMTP; 27 Sep 2012 21:42:06 -0000 Received: by vcmm18 with SMTP id m18so3275070vcm.30 for ; Thu, 27 Sep 2012 14:42:05 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=6u/CWOMDIWFn0pMcOa4MFkHslWKhQfUNGeq/2jWGYow=; b=X5i1JQjQjSS5mZ+qRPViXSafcjDVH64K73F+C/grHojoZp8nkmb7mbJpPuI5gf3hBt OS+BupUGGK3UypUKcTIl6MARFwSNAIZmJfpx/x4GS3Wg6KqV6jB8PGqJUEGYfgfDGiQq hw6U8qupdbvFNf60oaMoI+aARyFkUi/dBmMNr0g3UGobR5oAv+7NSv6bCrHpUjTztbe4 xwU6kK0THVh6k2vkaZ6XlDzwykfwv+0cKnG7DWE8GLU+gnM9FcwnHxI3X4asunx2uIIa z6BzJ8BeT4W8ubcd68nYcCmMEN0L6ud90oNqF0t0F7909GXEuSIExPnLLFv7Oa24yDKg krSw== MIME-Version: 1.0 Received: by 10.220.116.9 with SMTP id k9mr2991072vcq.0.1348782125006; Thu, 27 Sep 2012 14:42:05 -0700 (PDT) Received: by 10.58.207.75 with HTTP; Thu, 27 Sep 2012 14:42:04 -0700 (PDT) In-Reply-To: References: <68c41dd8-9195-41b0-83d7-9242b8eff809@default> <65395f62-74e5-4910-b701-8df629c2ce3b@default> Date: Thu, 27 Sep 2012 23:42:04 +0200 Message-ID: From: Mauro To: Olivier Hanesse Cc: Dan Magenheimer , xen-devel@lists.xensource.com, Keir Fraser , Jeremy Fitzhardinge , Jan Beulich , Keir Fraser , Xen Users , Mark Adams Subject: Re: [Xen-users] [Xen-devel] Xen 4 TSC problems X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org On 27 September 2012 23:28, Olivier Hanesse wrote: > Hello, > > From my point of view, this was a kind of xen hardware "incompatibility/bug" > : I was able to reproduce this bug on more than 50 identical servers, but > not on another farm of servers with a different hardware. > Xen version, Debian Kernel was exactly the same on both farm. Yes I think so. The problem is where I use debian squeeze with xen 4.0. In another server with the same hardware but with debian lenny and xen 3.0 I have no problems. I've read that a workaround is to set clocksource=pit on the xen boot line in the grub conf, I hope this works because I can't change hardware. _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Thu Sep 27 22:56:56 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Thu, 27 Sep 2012 22:56:56 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1THMzd-0000Ut-Q8; Thu, 27 Sep 2012 22:55:41 +0000 Received: from mail27.messagelabs.com ([193.109.254.147]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1THLdU-0006w1-Tw; Thu, 27 Sep 2012 21:28:45 +0000 X-Env-Sender: olivier.hanesse@gmail.com X-Msg-Ref: server-6.tower-27.messagelabs.com!1348781316!7098834!1 X-Originating-IP: [209.85.214.171] X-SpamReason: No, hits=0.4 required=7.0 tests=HTML_30_40,HTML_MESSAGE, ML_RADAR_SPEW_LINKS_14,RCVD_BY_IP,spamassassin: X-StarScan-Received: X-StarScan-Version: 6.6.1.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 7762 invoked from network); 27 Sep 2012 21:28:38 -0000 Received: from mail-ob0-f171.google.com (HELO mail-ob0-f171.google.com) (209.85.214.171) by server-6.tower-27.messagelabs.com with RC4-SHA encrypted SMTP; 27 Sep 2012 21:28:38 -0000 Received: by obc16 with SMTP id 16so3280606obc.30 for ; Thu, 27 Sep 2012 14:28:36 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=QsUEQU6eWE3foUSYZ5Mnkj/D3HBa5PfMvRxRhzmQ6Ik=; b=bK+i0ldB/TojOOxfTEc2ZWXxb0rO8U3pN2sT1Bf3Zc3OnSeaWNgISX0jAXK79ypK9+ WiFfjbUnj/cxYAkVu0moqhXraZWZhJMzOsWGbxs6DiAr048uAjwtNbl3iaOc5hyead1S tWk7bNhLPau7pHSQ12rOfkAxv2iooI9Go7DBGx5LYEG61N6Ew8ik2CWzLBusEzGjp2Gu URihTDOmVXcvqrBrAy+9o9EDOMG/lpiK5ohDy95B6vG9racKoe/uXX69Vl4aYyPvXdq8 0JJsvX5nBOJTY250Ju2Ol6h8WBO7TUrdMOm9tQYVoTx2u76DlsBDaOE7UtvBR9l6udEQ IqZw== MIME-Version: 1.0 Received: by 10.60.7.36 with SMTP id g4mr4217300oea.112.1348781316158; Thu, 27 Sep 2012 14:28:36 -0700 (PDT) Received: by 10.76.33.199 with HTTP; Thu, 27 Sep 2012 14:28:36 -0700 (PDT) In-Reply-To: <65395f62-74e5-4910-b701-8df629c2ce3b@default> References: <68c41dd8-9195-41b0-83d7-9242b8eff809@default> <65395f62-74e5-4910-b701-8df629c2ce3b@default> Date: Thu, 27 Sep 2012 23:28:36 +0200 Message-ID: From: Olivier Hanesse To: Dan Magenheimer X-Mailman-Approved-At: Thu, 27 Sep 2012 22:55:41 +0000 Cc: Jeremy Fitzhardinge , xen-devel@lists.xensource.com, Keir Fraser , Jan Beulich , Keir Fraser , Mauro , Xen Users , Mark Adams Subject: Re: [Xen-users] [Xen-devel] Xen 4 TSC problems X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============6005141474881443268==" Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org --===============6005141474881443268== Content-Type: multipart/alternative; boundary=e89a8f64347c3ab36704cab59f37 --e89a8f64347c3ab36704cab59f37 Content-Type: text/plain; charset=ISO-8859-1 Hello, >From my point of view, this was a kind of xen hardware "incompatibility/bug" : I was able to reproduce this bug on more than 50 identical servers, but not on another farm of servers with a different hardware. Xen version, Debian Kernel was exactly the same on both farm. Regards Olivier 2012/9/27 Dan Magenheimer > > From: Mauro [mailto:mrsanna1@gmail.com] > > Sent: Thursday, September 27, 2012 9:55 AM > > To: Olivier Hanesse > > Cc: Dan Magenheimer; Jeremy Fitzhardinge; xen-devel@lists.xensource.com; > Keir Fraser; Jan Beulich; > > Keir Fraser; Xen Users; Mark Adams > > Subject: Re: [Xen-users] Re: [Xen-devel] Xen 4 TSC problems > > > > On 28 February 2011 16:54, Olivier Hanesse > wrote: > > > Yes this is what I mean. > > > I am glad to hear that it isn't a bad sign :) > > > I thought of a bad sign, because on system with "reliable TSC", this > counter > > > is always 0. > > > > Hey men. > > I have exactly the same problem. > > I have two cluster nodes. > > Server are two HP Proliant DL 580 G4 with four Quad Core Intel(R) > > Xeon(R) CPU E7330 @ 2.40GHz. > > I'm running debian squeeze in dom0s end domUs. > > Hi Mauro -- > > There's been a lot of work on clocks since 4.0 (by other Xen developers, > not me). I don't think this specific problem was ever reproduced > by a developer so I don't think anyone knows if it has been > already fixed or not, nor are there any plans to backport all the > timer work to 4.0. > > You might try upgrading your Xen hypervisor to the just-released > Xen 4.2 [1] and see if the problem goes away. If the problem still > exists in 4.2, it may be easier to get some developer to pay attention > to it. It may be specific hardware or processors or power > management or firmware or even dom0 kernel, so the first thing > to do is try later hypervisor bits. > > Sorry I can't be more helpful. Good luck! > > Dan > > [1] Sorry, I'm not familiar with the 4.0->4.2 upgrade process > so you may want to confirm with others. > > > xm info: > > > > host : xen-p01 > > release : 2.6.32-5-xen-amd64 > > version : #1 SMP Sun May 6 08:57:29 UTC 2012 > > machine : x86_64 > > nr_cpus : 16 > > nr_nodes : 1 > > cores_per_socket : 4 > > threads_per_core : 1 > > cpu_mhz : 2400 > > hw_caps : > > bfebfbff:20100800:00000000:00000940:0004e3bd:00000000:00000001:00000000 > > virt_caps : hvm > > total_memory : 65532 > > free_memory : 40317 > > node_to_cpu : node0:0-15 > > node_to_memory : node0:40317 > > node_to_dma32_mem : node0:3256 > > max_node_id : 0 > > xen_major : 4 > > xen_minor : 0 > > xen_extra : .1 > > xen_caps : xen-3.0-x86_64 xen-3.0-x86_32p hvm-3.0-x86_32 > > hvm-3.0-x86_32p hvm-3.0-x86_64 > > xen_scheduler : credit > > xen_pagesize : 4096 > > platform_params : virt_start=0xffff800000000000 > > xen_changeset : unavailable > > xen_commandline : placeholder dom0_mem=3072M loglvl=warning > > guest_loglvl=warning > > cc_compiler : gcc version 4.4.5 (Debian 4.4.5-8) > > cc_compile_by : ultrotter > > cc_compile_domain : debian.org > > cc_compile_date : Sat Sep 8 19:15:46 UTC 2012 > > xend_config_format : 4 > > > > I'm experiencing weekly a clock jump ahead of about 50 minutes on dom0. > > I'm seriously in trouble because it cause every time a reboot of one > > of the two nodes clusters. > --e89a8f64347c3ab36704cab59f37 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Hello,=A0

From my point of view, this was a kind of xen = hardware "incompatibility/bug" : I was able to reproduce this bug= on more than 50 identical servers, but not on another farm of servers with= a different hardware.
Xen version, Debian Kernel was exactly the same on both farm.

Regards

Olivier

2012/9/27 Dan Magenheimer <dan.magenheime= r@oracle.com>
> From: Mauro [mailto:mrsanna1@gmail.com]
> Sent: Thursday, September 27, 2012 9:55 AM
> To: Olivier Hanesse
> Cc: Dan Magenheimer; Jeremy Fitzhardinge; xen-devel@lists.xensource.com; Keir Fraser; Jan Be= ulich;
> Keir Fraser; Xen Users; Mark Adams
> Subject: Re: [Xen-users] Re: [Xen-devel] Xen 4 TSC problems
>
> On 28 February 2011 16:54, Olivier Hanesse <olivier.hanesse@gmail.com> wrote:
> > Yes this is what I mean.
> > I am glad to hear that it isn't a bad sign :)
> > I thought of a bad sign, because on system with "reliable TS= C", this counter
> > is always 0.
>
> Hey men.
> I have exactly the same problem.
> I have two cluster nodes.
> Server are two HP Proliant DL 580 G4 with four Quad Core Intel(R)
> Xeon(R) CPU E7330 =A0@ 2.40GHz.
> I'm running debian squeeze in dom0s end domUs.

Hi Mauro --

There's been a lot of work on clocks since 4.0 (by other Xen developers= ,
not me). =A0I don't think this specific problem was ever reproduced
by a developer so I don't think anyone knows if it has been
already fixed or not, nor are there any plans to backport all the
timer work to 4.0.

You might try upgrading your Xen hypervisor to the just-released
Xen 4.2 [1] and see if the problem goes away. =A0If the problem still
exists in 4.2, it may be easier to get some developer to pay attention
to it. =A0It may be specific hardware or processors or power
management or firmware or even dom0 kernel, so the first thing
to do is try later hypervisor bits.

Sorry I can't be more helpful. =A0Good luck!

Dan

[1] Sorry, I'm not familiar with the 4.0->4.2 upgrade process
so you may want to confirm with others.

> xm info:
>
> host =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 : xen-p01
> release =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0: 2.6.32-5-xen-amd64
> version =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0: #1 SMP Sun May 6 08:57:29 UTC= 2012
> machine =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0: x86_64
> nr_cpus =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0: 16
> nr_nodes =A0 =A0 =A0 =A0 =A0 =A0 =A0 : 1
> cores_per_socket =A0 =A0 =A0 : 4
> threads_per_core =A0 =A0 =A0 : 1
> cpu_mhz =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0: 2400
> hw_caps =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0:
> bfebfbff:20100800:00000000:00000940:0004e3bd:00000000:00000001:0000000= 0
> virt_caps =A0 =A0 =A0 =A0 =A0 =A0 =A0: hvm
> total_memory =A0 =A0 =A0 =A0 =A0 : 65532
> free_memory =A0 =A0 =A0 =A0 =A0 =A0: 40317
> node_to_cpu =A0 =A0 =A0 =A0 =A0 =A0: node0:0-15
> node_to_memory =A0 =A0 =A0 =A0 : node0:40317
> node_to_dma32_mem =A0 =A0 =A0: node0:3256
> max_node_id =A0 =A0 =A0 =A0 =A0 =A0: 0
> xen_major =A0 =A0 =A0 =A0 =A0 =A0 =A0: 4
> xen_minor =A0 =A0 =A0 =A0 =A0 =A0 =A0: 0
> xen_extra =A0 =A0 =A0 =A0 =A0 =A0 =A0: .1
> xen_caps =A0 =A0 =A0 =A0 =A0 =A0 =A0 : xen-3.0-x86_64 xen-3.0-x86_32p = hvm-3.0-x86_32
> hvm-3.0-x86_32p hvm-3.0-x86_64
> xen_scheduler =A0 =A0 =A0 =A0 =A0: credit
> xen_pagesize =A0 =A0 =A0 =A0 =A0 : 4096
> platform_params =A0 =A0 =A0 =A0: virt_start=3D0xffff800000000000
> xen_changeset =A0 =A0 =A0 =A0 =A0: unavailable
> xen_commandline =A0 =A0 =A0 =A0: placeholder dom0_mem=3D3072M loglvl= =3Dwarning
> guest_loglvl=3Dwarning
> cc_compiler =A0 =A0 =A0 =A0 =A0 =A0: gcc version 4.4.5 (Debian 4.4.5-8= )
> cc_compile_by =A0 =A0 =A0 =A0 =A0: ultrotter
> cc_compile_domain =A0 =A0 =A0: debian.org
> cc_compile_date =A0 =A0 =A0 =A0: Sat Sep =A08 19:15:46 UTC 2012
> xend_config_format =A0 =A0 : 4
>
> I'm experiencing weekly a clock jump ahead of about 50 minutes on = dom0.
> I'm seriously in trouble because it cause every time a reboot of o= ne
> of the two nodes clusters.

--e89a8f64347c3ab36704cab59f37-- --===============6005141474881443268== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users --===============6005141474881443268==-- From xen-users-bounces@lists.xen.org Thu Sep 27 22:56:56 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Thu, 27 Sep 2012 22:56:56 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1THMzd-0000Ut-Q8; Thu, 27 Sep 2012 22:55:41 +0000 Received: from mail27.messagelabs.com ([193.109.254.147]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1THLdU-0006w1-Tw; Thu, 27 Sep 2012 21:28:45 +0000 X-Env-Sender: olivier.hanesse@gmail.com X-Msg-Ref: server-6.tower-27.messagelabs.com!1348781316!7098834!1 X-Originating-IP: [209.85.214.171] X-SpamReason: No, hits=0.4 required=7.0 tests=HTML_30_40,HTML_MESSAGE, ML_RADAR_SPEW_LINKS_14,RCVD_BY_IP,spamassassin: X-StarScan-Received: X-StarScan-Version: 6.6.1.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 7762 invoked from network); 27 Sep 2012 21:28:38 -0000 Received: from mail-ob0-f171.google.com (HELO mail-ob0-f171.google.com) (209.85.214.171) by server-6.tower-27.messagelabs.com with RC4-SHA encrypted SMTP; 27 Sep 2012 21:28:38 -0000 Received: by obc16 with SMTP id 16so3280606obc.30 for ; Thu, 27 Sep 2012 14:28:36 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=QsUEQU6eWE3foUSYZ5Mnkj/D3HBa5PfMvRxRhzmQ6Ik=; b=bK+i0ldB/TojOOxfTEc2ZWXxb0rO8U3pN2sT1Bf3Zc3OnSeaWNgISX0jAXK79ypK9+ WiFfjbUnj/cxYAkVu0moqhXraZWZhJMzOsWGbxs6DiAr048uAjwtNbl3iaOc5hyead1S tWk7bNhLPau7pHSQ12rOfkAxv2iooI9Go7DBGx5LYEG61N6Ew8ik2CWzLBusEzGjp2Gu URihTDOmVXcvqrBrAy+9o9EDOMG/lpiK5ohDy95B6vG9racKoe/uXX69Vl4aYyPvXdq8 0JJsvX5nBOJTY250Ju2Ol6h8WBO7TUrdMOm9tQYVoTx2u76DlsBDaOE7UtvBR9l6udEQ IqZw== MIME-Version: 1.0 Received: by 10.60.7.36 with SMTP id g4mr4217300oea.112.1348781316158; Thu, 27 Sep 2012 14:28:36 -0700 (PDT) Received: by 10.76.33.199 with HTTP; Thu, 27 Sep 2012 14:28:36 -0700 (PDT) In-Reply-To: <65395f62-74e5-4910-b701-8df629c2ce3b@default> References: <68c41dd8-9195-41b0-83d7-9242b8eff809@default> <65395f62-74e5-4910-b701-8df629c2ce3b@default> Date: Thu, 27 Sep 2012 23:28:36 +0200 Message-ID: From: Olivier Hanesse To: Dan Magenheimer X-Mailman-Approved-At: Thu, 27 Sep 2012 22:55:41 +0000 Cc: Jeremy Fitzhardinge , xen-devel@lists.xensource.com, Keir Fraser , Jan Beulich , Keir Fraser , Mauro , Xen Users , Mark Adams Subject: Re: [Xen-users] [Xen-devel] Xen 4 TSC problems X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============6005141474881443268==" Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org --===============6005141474881443268== Content-Type: multipart/alternative; boundary=e89a8f64347c3ab36704cab59f37 --e89a8f64347c3ab36704cab59f37 Content-Type: text/plain; charset=ISO-8859-1 Hello, >From my point of view, this was a kind of xen hardware "incompatibility/bug" : I was able to reproduce this bug on more than 50 identical servers, but not on another farm of servers with a different hardware. Xen version, Debian Kernel was exactly the same on both farm. Regards Olivier 2012/9/27 Dan Magenheimer > > From: Mauro [mailto:mrsanna1@gmail.com] > > Sent: Thursday, September 27, 2012 9:55 AM > > To: Olivier Hanesse > > Cc: Dan Magenheimer; Jeremy Fitzhardinge; xen-devel@lists.xensource.com; > Keir Fraser; Jan Beulich; > > Keir Fraser; Xen Users; Mark Adams > > Subject: Re: [Xen-users] Re: [Xen-devel] Xen 4 TSC problems > > > > On 28 February 2011 16:54, Olivier Hanesse > wrote: > > > Yes this is what I mean. > > > I am glad to hear that it isn't a bad sign :) > > > I thought of a bad sign, because on system with "reliable TSC", this > counter > > > is always 0. > > > > Hey men. > > I have exactly the same problem. > > I have two cluster nodes. > > Server are two HP Proliant DL 580 G4 with four Quad Core Intel(R) > > Xeon(R) CPU E7330 @ 2.40GHz. > > I'm running debian squeeze in dom0s end domUs. > > Hi Mauro -- > > There's been a lot of work on clocks since 4.0 (by other Xen developers, > not me). I don't think this specific problem was ever reproduced > by a developer so I don't think anyone knows if it has been > already fixed or not, nor are there any plans to backport all the > timer work to 4.0. > > You might try upgrading your Xen hypervisor to the just-released > Xen 4.2 [1] and see if the problem goes away. If the problem still > exists in 4.2, it may be easier to get some developer to pay attention > to it. It may be specific hardware or processors or power > management or firmware or even dom0 kernel, so the first thing > to do is try later hypervisor bits. > > Sorry I can't be more helpful. Good luck! > > Dan > > [1] Sorry, I'm not familiar with the 4.0->4.2 upgrade process > so you may want to confirm with others. > > > xm info: > > > > host : xen-p01 > > release : 2.6.32-5-xen-amd64 > > version : #1 SMP Sun May 6 08:57:29 UTC 2012 > > machine : x86_64 > > nr_cpus : 16 > > nr_nodes : 1 > > cores_per_socket : 4 > > threads_per_core : 1 > > cpu_mhz : 2400 > > hw_caps : > > bfebfbff:20100800:00000000:00000940:0004e3bd:00000000:00000001:00000000 > > virt_caps : hvm > > total_memory : 65532 > > free_memory : 40317 > > node_to_cpu : node0:0-15 > > node_to_memory : node0:40317 > > node_to_dma32_mem : node0:3256 > > max_node_id : 0 > > xen_major : 4 > > xen_minor : 0 > > xen_extra : .1 > > xen_caps : xen-3.0-x86_64 xen-3.0-x86_32p hvm-3.0-x86_32 > > hvm-3.0-x86_32p hvm-3.0-x86_64 > > xen_scheduler : credit > > xen_pagesize : 4096 > > platform_params : virt_start=0xffff800000000000 > > xen_changeset : unavailable > > xen_commandline : placeholder dom0_mem=3072M loglvl=warning > > guest_loglvl=warning > > cc_compiler : gcc version 4.4.5 (Debian 4.4.5-8) > > cc_compile_by : ultrotter > > cc_compile_domain : debian.org > > cc_compile_date : Sat Sep 8 19:15:46 UTC 2012 > > xend_config_format : 4 > > > > I'm experiencing weekly a clock jump ahead of about 50 minutes on dom0. > > I'm seriously in trouble because it cause every time a reboot of one > > of the two nodes clusters. > --e89a8f64347c3ab36704cab59f37 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Hello,=A0

From my point of view, this was a kind of xen = hardware "incompatibility/bug" : I was able to reproduce this bug= on more than 50 identical servers, but not on another farm of servers with= a different hardware.
Xen version, Debian Kernel was exactly the same on both farm.

Regards

Olivier

2012/9/27 Dan Magenheimer <dan.magenheime= r@oracle.com>
> From: Mauro [mailto:mrsanna1@gmail.com]
> Sent: Thursday, September 27, 2012 9:55 AM
> To: Olivier Hanesse
> Cc: Dan Magenheimer; Jeremy Fitzhardinge; xen-devel@lists.xensource.com; Keir Fraser; Jan Be= ulich;
> Keir Fraser; Xen Users; Mark Adams
> Subject: Re: [Xen-users] Re: [Xen-devel] Xen 4 TSC problems
>
> On 28 February 2011 16:54, Olivier Hanesse <olivier.hanesse@gmail.com> wrote:
> > Yes this is what I mean.
> > I am glad to hear that it isn't a bad sign :)
> > I thought of a bad sign, because on system with "reliable TS= C", this counter
> > is always 0.
>
> Hey men.
> I have exactly the same problem.
> I have two cluster nodes.
> Server are two HP Proliant DL 580 G4 with four Quad Core Intel(R)
> Xeon(R) CPU E7330 =A0@ 2.40GHz.
> I'm running debian squeeze in dom0s end domUs.

Hi Mauro --

There's been a lot of work on clocks since 4.0 (by other Xen developers= ,
not me). =A0I don't think this specific problem was ever reproduced
by a developer so I don't think anyone knows if it has been
already fixed or not, nor are there any plans to backport all the
timer work to 4.0.

You might try upgrading your Xen hypervisor to the just-released
Xen 4.2 [1] and see if the problem goes away. =A0If the problem still
exists in 4.2, it may be easier to get some developer to pay attention
to it. =A0It may be specific hardware or processors or power
management or firmware or even dom0 kernel, so the first thing
to do is try later hypervisor bits.

Sorry I can't be more helpful. =A0Good luck!

Dan

[1] Sorry, I'm not familiar with the 4.0->4.2 upgrade process
so you may want to confirm with others.

> xm info:
>
> host =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 : xen-p01
> release =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0: 2.6.32-5-xen-amd64
> version =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0: #1 SMP Sun May 6 08:57:29 UTC= 2012
> machine =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0: x86_64
> nr_cpus =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0: 16
> nr_nodes =A0 =A0 =A0 =A0 =A0 =A0 =A0 : 1
> cores_per_socket =A0 =A0 =A0 : 4
> threads_per_core =A0 =A0 =A0 : 1
> cpu_mhz =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0: 2400
> hw_caps =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0:
> bfebfbff:20100800:00000000:00000940:0004e3bd:00000000:00000001:0000000= 0
> virt_caps =A0 =A0 =A0 =A0 =A0 =A0 =A0: hvm
> total_memory =A0 =A0 =A0 =A0 =A0 : 65532
> free_memory =A0 =A0 =A0 =A0 =A0 =A0: 40317
> node_to_cpu =A0 =A0 =A0 =A0 =A0 =A0: node0:0-15
> node_to_memory =A0 =A0 =A0 =A0 : node0:40317
> node_to_dma32_mem =A0 =A0 =A0: node0:3256
> max_node_id =A0 =A0 =A0 =A0 =A0 =A0: 0
> xen_major =A0 =A0 =A0 =A0 =A0 =A0 =A0: 4
> xen_minor =A0 =A0 =A0 =A0 =A0 =A0 =A0: 0
> xen_extra =A0 =A0 =A0 =A0 =A0 =A0 =A0: .1
> xen_caps =A0 =A0 =A0 =A0 =A0 =A0 =A0 : xen-3.0-x86_64 xen-3.0-x86_32p = hvm-3.0-x86_32
> hvm-3.0-x86_32p hvm-3.0-x86_64
> xen_scheduler =A0 =A0 =A0 =A0 =A0: credit
> xen_pagesize =A0 =A0 =A0 =A0 =A0 : 4096
> platform_params =A0 =A0 =A0 =A0: virt_start=3D0xffff800000000000
> xen_changeset =A0 =A0 =A0 =A0 =A0: unavailable
> xen_commandline =A0 =A0 =A0 =A0: placeholder dom0_mem=3D3072M loglvl= =3Dwarning
> guest_loglvl=3Dwarning
> cc_compiler =A0 =A0 =A0 =A0 =A0 =A0: gcc version 4.4.5 (Debian 4.4.5-8= )
> cc_compile_by =A0 =A0 =A0 =A0 =A0: ultrotter
> cc_compile_domain =A0 =A0 =A0: debian.org
> cc_compile_date =A0 =A0 =A0 =A0: Sat Sep =A08 19:15:46 UTC 2012
> xend_config_format =A0 =A0 : 4
>
> I'm experiencing weekly a clock jump ahead of about 50 minutes on = dom0.
> I'm seriously in trouble because it cause every time a reboot of o= ne
> of the two nodes clusters.

--e89a8f64347c3ab36704cab59f37-- --===============6005141474881443268== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users --===============6005141474881443268==-- From xen-users-bounces@lists.xen.org Fri Sep 28 00:02:44 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Fri, 28 Sep 2012 00:02:44 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1THO1P-0001aY-EC; Fri, 28 Sep 2012 00:01:35 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1THO1N-0001aT-Ae for xen-users@lists.xen.org; Fri, 28 Sep 2012 00:01:33 +0000 Received: from [85.158.139.211:48222] by server-1.bemta-5.messagelabs.com id 98/C2-09825-CD8E4605; Fri, 28 Sep 2012 00:01:32 +0000 X-Env-Sender: xtreme911@msn.com X-Msg-Ref: server-16.tower-206.messagelabs.com!1348790490!20284450!1 X-Originating-IP: [65.54.190.91] X-SpamReason: No, hits=0.1 required=7.0 tests=FORGED_HOTMAIL_RCVD, ML_RADAR_SPEW_LINKS_12,spamassassin: X-StarScan-Received: X-StarScan-Version: 6.6.1.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 21739 invoked from network); 28 Sep 2012 00:01:30 -0000 Received: from bay0-omc2-s16.bay0.hotmail.com (HELO bay0-omc2-s16.bay0.hotmail.com) (65.54.190.91) by server-16.tower-206.messagelabs.com with SMTP; 28 Sep 2012 00:01:30 -0000 Received: from BAY148-W50 ([65.54.190.123]) by bay0-omc2-s16.bay0.hotmail.com with Microsoft SMTPSVC(6.0.3790.4675); Thu, 27 Sep 2012 17:01:29 -0700 Message-ID: X-Originating-IP: [76.68.73.169] From: Mike Viau To: Date: Thu, 27 Sep 2012 20:01:29 -0400 Importance: Normal In-Reply-To: References: , <50645166.2000200@gmail.com> <50647B26.9080903@gmail.com>, , <50648CEA.9070107@gmail.com> , MIME-Version: 1.0 X-OriginalArrivalTime: 28 Sep 2012 00:01:29.0188 (UTC) FILETIME=[6916C240:01CD9D0C] Subject: Re: [Xen-users] Success VGA passthrough on windows 7 x64 with Xen 4.2.1-pre X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org >On Thu, 27 Sep 2012 20:34:54 +0200 wrote: > > >2012/9/27 Mike Viau : > > > >> On Fri, 28 Sep 2012 01:29:14 +0800 wrote: > >> > >> Dear Dariusz Krempa, > >> > >> Thank you for your prompt reply. > >> > >> I don't have pci_msitranslate = 1 in my Windows HVM domU config file, so > >> I don't think "pci_msitranslate = 1" is the main cause of my "nasty > >> yellow triangle with error 43". > >> > > > > I once recorded that the default for the pci_msitranslate option was "1". Not having this in your configuration then is like having it set. Feel free to correct me if I am wrong. I have only gotten VGA pass-through to work with a Windows domU, never in GNU/Linux for some reason. > > > > > > -M > > from change set 25525 msitranslate is 0 by deafault > > http://xenbits.xensource.com/hg/staging/xen-unstable.hg/rev/84272cca638a?revcount=120 > Thanks for this information, it was much appreciated! I will be updating my notes accordingly. -M _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Fri Sep 28 00:02:44 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Fri, 28 Sep 2012 00:02:44 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1THO1P-0001aY-EC; Fri, 28 Sep 2012 00:01:35 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1THO1N-0001aT-Ae for xen-users@lists.xen.org; Fri, 28 Sep 2012 00:01:33 +0000 Received: from [85.158.139.211:48222] by server-1.bemta-5.messagelabs.com id 98/C2-09825-CD8E4605; Fri, 28 Sep 2012 00:01:32 +0000 X-Env-Sender: xtreme911@msn.com X-Msg-Ref: server-16.tower-206.messagelabs.com!1348790490!20284450!1 X-Originating-IP: [65.54.190.91] X-SpamReason: No, hits=0.1 required=7.0 tests=FORGED_HOTMAIL_RCVD, ML_RADAR_SPEW_LINKS_12,spamassassin: X-StarScan-Received: X-StarScan-Version: 6.6.1.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 21739 invoked from network); 28 Sep 2012 00:01:30 -0000 Received: from bay0-omc2-s16.bay0.hotmail.com (HELO bay0-omc2-s16.bay0.hotmail.com) (65.54.190.91) by server-16.tower-206.messagelabs.com with SMTP; 28 Sep 2012 00:01:30 -0000 Received: from BAY148-W50 ([65.54.190.123]) by bay0-omc2-s16.bay0.hotmail.com with Microsoft SMTPSVC(6.0.3790.4675); Thu, 27 Sep 2012 17:01:29 -0700 Message-ID: X-Originating-IP: [76.68.73.169] From: Mike Viau To: Date: Thu, 27 Sep 2012 20:01:29 -0400 Importance: Normal In-Reply-To: References: , <50645166.2000200@gmail.com> <50647B26.9080903@gmail.com>, , <50648CEA.9070107@gmail.com> , MIME-Version: 1.0 X-OriginalArrivalTime: 28 Sep 2012 00:01:29.0188 (UTC) FILETIME=[6916C240:01CD9D0C] Subject: Re: [Xen-users] Success VGA passthrough on windows 7 x64 with Xen 4.2.1-pre X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org >On Thu, 27 Sep 2012 20:34:54 +0200 wrote: > > >2012/9/27 Mike Viau : > > > >> On Fri, 28 Sep 2012 01:29:14 +0800 wrote: > >> > >> Dear Dariusz Krempa, > >> > >> Thank you for your prompt reply. > >> > >> I don't have pci_msitranslate = 1 in my Windows HVM domU config file, so > >> I don't think "pci_msitranslate = 1" is the main cause of my "nasty > >> yellow triangle with error 43". > >> > > > > I once recorded that the default for the pci_msitranslate option was "1". Not having this in your configuration then is like having it set. Feel free to correct me if I am wrong. I have only gotten VGA pass-through to work with a Windows domU, never in GNU/Linux for some reason. > > > > > > -M > > from change set 25525 msitranslate is 0 by deafault > > http://xenbits.xensource.com/hg/staging/xen-unstable.hg/rev/84272cca638a?revcount=120 > Thanks for this information, it was much appreciated! I will be updating my notes accordingly. -M _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Fri Sep 28 02:17:40 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Fri, 28 Sep 2012 02:17:40 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1THQ7g-0006jc-JD; Fri, 28 Sep 2012 02:16:12 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1THQ7f-0006jX-6p for xen-users@lists.xen.org; Fri, 28 Sep 2012 02:16:11 +0000 Received: from [85.158.143.99:12977] by server-2.bemta-4.messagelabs.com id 3B/1A-06610-A6805605; Fri, 28 Sep 2012 02:16:10 +0000 X-Env-Sender: robert@digitalsilk.net X-Msg-Ref: server-5.tower-216.messagelabs.com!1348798567!31731550!1 X-Originating-IP: [208.157.175.245] X-SpamReason: No, hits=0.0 required=7.0 tests= X-StarScan-Received: X-StarScan-Version: 6.6.1.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 9220 invoked from network); 28 Sep 2012 02:16:08 -0000 Received: from bal-bb-static3-cisco-ws-20.dsl.airstreamcomm.net (HELO bilbo.digitalsilk.net) (208.157.175.245) by server-5.tower-216.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 28 Sep 2012 02:16:08 -0000 Received: by bilbo.digitalsilk.net (Postfix, from userid 1001) id B6EB93002D; Thu, 27 Sep 2012 21:16:03 -0500 (CDT) X-Spam-Checker-Version: SpamAssassin 3.3.2 (2011-06-06) on bilbo X-Spam-Status: No, hits=-1.0 required=3.0 tests=ALL_TRUSTED X-Spam-Level: Received: from bunsen.digitalsilk.lan (link.digitalsilk.lan [192.168.2.254]) by bilbo.digitalsilk.net (Postfix) with ESMTP id 8738E3002C for ; Thu, 27 Sep 2012 21:16:03 -0500 (CDT) Message-ID: <50650865.1020608@digitalsilk.net> Date: Thu, 27 Sep 2012 21:16:05 -0500 From: Robert Rust User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:15.0) Gecko/20120907 Thunderbird/15.0.1 MIME-Version: 1.0 To: xen-users@lists.xen.org References: <505FC055.4060004@digitalsilk.net> In-Reply-To: <505FC055.4060004@digitalsilk.net> Subject: Re: [Xen-users] can't pass pair of PCI cards to single domU X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset="us-ascii"; Format="flowed" Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org On 9/23/12 9:07 PM, Robert Rust wrote: > Folks - > > Any ideas on why I can't pass a pair of HVR-1600 PCI cards to a single > DomU? When I try, only a single one shows up. I can pass them to > separate DomUs (though I'm having problems getting the one in the second > DomU to capture properly, it does show up and gets recognized by the > driver for it). > Distro: Ubuntu 12.04.1 LTS > Kernel: ubuntu stock 3.2.0-31-generic #50 > xen: from ubuntu - 4.1.2-2 > > Any additional information that would be helpful? > > -Robert I did some more experimenting this evening and discovered that while I couldn't pass both cards to the domU at boot time via the .cfg file, I can hot-pass them using pci-attach. This is a bit of a pain, since I have services on the DomU expecting the cards to be there that need to be restarted after attaching the cards. I've verified they do both work after this procedure. Any thoughts on how to troubleshoot this further? Am I doing something wrong in the config? Config is as follows (pci line is commented out so I can hot-pass): kernel = '/boot/vmlinuz-3.2.0-31-generic' extra = 'iommu=soft' ramdisk = '/boot/initrd.img-3.2.0-31-generic' vcpus = '2' memory = '2048'root = '/dev/xvda2 ro' disk = [ 'phy:/dev/rivendell/pippin-disk,xvda2,w', 'phy:/dev/mythtv/pippin-swap,xvda1,w', 'phy:/dev/mythtv/mythmedia,xvda3,w', ] #pci = [ '06:00.0','06:01.0' ] name = 'pippin' dhcp = 'dhcp' vif = [ 'mac=00:16:3E:CD:FD:2E,bridge=xenbr0' ] on_poweroff = 'destroy' on_reboot = 'restart' on_crash = 'restart' -Robert _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Fri Sep 28 02:17:40 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Fri, 28 Sep 2012 02:17:40 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1THQ7g-0006jc-JD; Fri, 28 Sep 2012 02:16:12 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1THQ7f-0006jX-6p for xen-users@lists.xen.org; Fri, 28 Sep 2012 02:16:11 +0000 Received: from [85.158.143.99:12977] by server-2.bemta-4.messagelabs.com id 3B/1A-06610-A6805605; Fri, 28 Sep 2012 02:16:10 +0000 X-Env-Sender: robert@digitalsilk.net X-Msg-Ref: server-5.tower-216.messagelabs.com!1348798567!31731550!1 X-Originating-IP: [208.157.175.245] X-SpamReason: No, hits=0.0 required=7.0 tests= X-StarScan-Received: X-StarScan-Version: 6.6.1.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 9220 invoked from network); 28 Sep 2012 02:16:08 -0000 Received: from bal-bb-static3-cisco-ws-20.dsl.airstreamcomm.net (HELO bilbo.digitalsilk.net) (208.157.175.245) by server-5.tower-216.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 28 Sep 2012 02:16:08 -0000 Received: by bilbo.digitalsilk.net (Postfix, from userid 1001) id B6EB93002D; Thu, 27 Sep 2012 21:16:03 -0500 (CDT) X-Spam-Checker-Version: SpamAssassin 3.3.2 (2011-06-06) on bilbo X-Spam-Status: No, hits=-1.0 required=3.0 tests=ALL_TRUSTED X-Spam-Level: Received: from bunsen.digitalsilk.lan (link.digitalsilk.lan [192.168.2.254]) by bilbo.digitalsilk.net (Postfix) with ESMTP id 8738E3002C for ; Thu, 27 Sep 2012 21:16:03 -0500 (CDT) Message-ID: <50650865.1020608@digitalsilk.net> Date: Thu, 27 Sep 2012 21:16:05 -0500 From: Robert Rust User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:15.0) Gecko/20120907 Thunderbird/15.0.1 MIME-Version: 1.0 To: xen-users@lists.xen.org References: <505FC055.4060004@digitalsilk.net> In-Reply-To: <505FC055.4060004@digitalsilk.net> Subject: Re: [Xen-users] can't pass pair of PCI cards to single domU X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset="us-ascii"; Format="flowed" Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org On 9/23/12 9:07 PM, Robert Rust wrote: > Folks - > > Any ideas on why I can't pass a pair of HVR-1600 PCI cards to a single > DomU? When I try, only a single one shows up. I can pass them to > separate DomUs (though I'm having problems getting the one in the second > DomU to capture properly, it does show up and gets recognized by the > driver for it). > Distro: Ubuntu 12.04.1 LTS > Kernel: ubuntu stock 3.2.0-31-generic #50 > xen: from ubuntu - 4.1.2-2 > > Any additional information that would be helpful? > > -Robert I did some more experimenting this evening and discovered that while I couldn't pass both cards to the domU at boot time via the .cfg file, I can hot-pass them using pci-attach. This is a bit of a pain, since I have services on the DomU expecting the cards to be there that need to be restarted after attaching the cards. I've verified they do both work after this procedure. Any thoughts on how to troubleshoot this further? Am I doing something wrong in the config? Config is as follows (pci line is commented out so I can hot-pass): kernel = '/boot/vmlinuz-3.2.0-31-generic' extra = 'iommu=soft' ramdisk = '/boot/initrd.img-3.2.0-31-generic' vcpus = '2' memory = '2048'root = '/dev/xvda2 ro' disk = [ 'phy:/dev/rivendell/pippin-disk,xvda2,w', 'phy:/dev/mythtv/pippin-swap,xvda1,w', 'phy:/dev/mythtv/mythmedia,xvda3,w', ] #pci = [ '06:00.0','06:01.0' ] name = 'pippin' dhcp = 'dhcp' vif = [ 'mac=00:16:3E:CD:FD:2E,bridge=xenbr0' ] on_poweroff = 'destroy' on_reboot = 'restart' on_crash = 'restart' -Robert _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Fri Sep 28 14:24:56 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Fri, 28 Sep 2012 14:24:56 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1THbTd-0006MB-56; Fri, 28 Sep 2012 14:23:37 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1THbTa-0006M6-Pl for xen-users@lists.xen.org; Fri, 28 Sep 2012 14:23:35 +0000 Received: from [85.158.137.99:24442] by server-14.bemta-3.messagelabs.com id BB/51-25886-5E2B5605; Fri, 28 Sep 2012 14:23:33 +0000 X-Env-Sender: gu99roax@student.chalmers.se X-Msg-Ref: server-13.tower-217.messagelabs.com!1348842211!19546606!1 X-Originating-IP: [213.199.154.206] X-SpamReason: No, hits=1.4 required=7.0 tests=BODY_RANDOM_LONG, HTML_20_30,HTML_MESSAGE,ML_RADAR_SPEW_LINKS_8,spamassassin: X-StarScan-Received: X-StarScan-Version: 6.6.1.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 27910 invoked from network); 28 Sep 2012 14:23:31 -0000 Received: from am1ehsobe003.messaging.microsoft.com (HELO am1outboundpool.messaging.microsoft.com) (213.199.154.206) by server-13.tower-217.messagelabs.com with AES128-SHA encrypted SMTP; 28 Sep 2012 14:23:31 -0000 Received: from mail63-am1-R.bigfish.com (10.3.201.243) by AM1EHSOBE008.bigfish.com (10.3.204.28) with Microsoft SMTP Server id 14.1.225.23; Fri, 28 Sep 2012 14:23:30 +0000 Received: from mail63-am1 (localhost [127.0.0.1]) by mail63-am1-R.bigfish.com (Postfix) with ESMTP id F286A2A0125 for ; Fri, 28 Sep 2012 14:23:30 +0000 (UTC) X-Forefront-Antispam-Report: CIP:207.46.4.203; KIP:(null); UIP:(null); IPV:NLI; H:SN2PRD0102HT019.prod.exchangelabs.com; RD:none; EFVD:NLI X-SpamScore: -6 X-BigFish: PS-6(zzbb2dI98dI9371I3071M936eI146fI1b0bIc85dh1432I2176M1447I31eakd6f1izz1d18h1202h1d1ah1d2ah1082kzz8275ch1730fah17326ah8275bhf69b8h8275dh177df4h172cdfhf3c47lz2dh2a8h668h839h8e2h8e3hd25hf0ah107ah10d2h1288h12a5h12bdh137ahbe9i1155h) Received: from mail63-am1 (localhost.localdomain [127.0.0.1]) by mail63-am1 (MessageSwitch) id 1348842207752931_7407; Fri, 28 Sep 2012 14:23:27 +0000 (UTC) Received: from AM1EHSMHS001.bigfish.com (unknown [10.3.201.231]) by mail63-am1.bigfish.com (Postfix) with ESMTP id AAEB74011F for ; Fri, 28 Sep 2012 14:23:27 +0000 (UTC) Received: from SN2PRD0102HT019.prod.exchangelabs.com (207.46.4.203) by AM1EHSMHS001.bigfish.com (10.3.207.101) with Microsoft SMTP Server (TLS) id 14.1.225.23; Fri, 28 Sep 2012 14:23:26 +0000 Received: from [10.40.137.93] (217.208.204.161) by pod51000.outlook.com (10.27.90.46) with Microsoft SMTP Server (TLS) id 14.15.108.4; Fri, 28 Sep 2012 14:23:22 +0000 Message-ID: <5065B2D8.8070401@student.chalmers.se> Date: Fri, 28 Sep 2012 16:23:20 +0200 From: Robin Axelsson User-Agent: Mozilla/5.0 (Windows NT 5.2; WOW64; rv:9.0) Gecko/20111222 Thunderbird/9.0.1 MIME-Version: 1.0 To: References: <505B86AE.9040507@earthlink.net> <505C8630.2090002@student.chalmers.se> <505FD74E.2050405@earthlink.net> <506056BC.3010705@student.chalmers.se> <5063AD2E.10800@earthlink.net> In-Reply-To: <5063AD2E.10800@earthlink.net> X-Originating-IP: [217.208.204.161] X-OriginatorOrg: student.chalmers.se Subject: Re: [Xen-users] Recommendations for Virtulization Hardware X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list Reply-To: gu99roax@student.chalmers.se List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============8613724340339552063==" Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org --===============8613724340339552063== Content-Type: multipart/alternative; boundary="------------000304020608000503070706" --------------000304020608000503070706 Content-Type: text/plain; charset="ISO-8859-1"; format=flowed Content-Transfer-Encoding: 7bit On 2012-09-27 03:34, ShadesOfGrey wrote: > On 09/24/2012 08:49 AM, Robin Axelsson wrote: >> On 2012-09-24 05:45, ShadesOfGrey wrote: >>> Sorry for the late response, I've had a lot to digest. > >>> The lack of current information about Xen (and KVM) online has been >>> frustrating --- especially finding the many proof of concept videos >>> that demonstrated possibilities but offered no real specifics. >>> Looking for specifics, I sought information from gaming and >>> enthusiast sites; I figured finding confirmation of VT-d and AMD-Vi >>> support on such sites would be more likely. However, I found that >>> wasn't often the case. I did determine that ASRock motherboards seem >>> to be the most likely to support VT-d, ASUS least likely (unless >>> equipped with an Intel 'sanctioned' VT-d chipset). I had narrowed my >>> choices to two motherboards that appear to offer VT-d support and >>> was intending to contact the manufacturer before purchase. Both >>> choices are a bit pricey and I've been reconsidering whether I >>> should look to other motherboards to reduce costs. >> >> Some motherboards support IOMMU even though it is not found in the >> user manual or specified on the website. Your best bet is to ask >> customer support. A guy posted here that he got it working on an >> Intel motherboard that doesn't even have options for it in the BIOS, >> so it seems that in some cases it is only up to the CPU. This is not >> the case with AMD though as I stated before. I have bought a couple >> of Gigabyte GA990FX-UD7 myself, they are stable and have a good >> layout. They have support for IOMMU but I haven't tested it >> thoroughly enough to fully confirm this although I don't believe >> there would be any problem. >> > I'm aware of this. In fact, I only have anecdotal evidence that the > Gigabyte G1.Sniper 3 has IOMMU (VT-d) support. I intend to query the > manufacturers, seeking confirmation of IOMMU support, of every > motherboard that ends up on my short list. I may include other Z77 > motherboards from MSI and Gigabyte, since there is concrete evidence > that the Z77 chipset does support IOMMU. I did focus, however, on > those motherboards I had some inkling could support IOMMU. Now I'm > trying to expand my selection process to include less expensive options. >> It surprises me that ASRock and ASUS are so different. ASRock is, or >> at least used to be a subsidiary of ASUS so there shouldn't be that >> much difference between them. > Same here. But I guess things changed after ASRock was spun-off. > > >>> This is precisely the kind of information I was looking for from the >>> threads I started on Ars Technica. It's just unfortunate that FLR >>> and D3 D0 support aren't often found in the tech specs of must >>> expansion hardware. However, now that I know what to ask, I'll try >>> contacting hardware manufacturers prior to purchasing any expansion >>> hardware. Thank you! >> >> D3 and D0 are power states defined for devices in the ACPI >> specification and can be used to control the supply voltage (Vcc) to >> PCI and PCIe devices. You can find more information about it here for >> example: >> >> http://en.wikipedia.org/wiki/Advanced_Configuration_and_Power_Interface >> >> --------------- >> >> >> Device states >> >> The device states /D0/-/D3/ are device-dependent: >> >> * *D0* /Fully On/ is the operating state. >> * *D1* and *D2* are intermediate power-states whose definition >> varies by device. >> * *D3* /Off/ has the device powered off and unresponsive to its bus. >> >> --------------- >> >> So, either it works for a certain type of hardware or it doesn't and >> I wouldn't expect a vendor to state this "support" in the >> specifications since it isn't a "feature" in and of itself if you get >> me. But maybe this will change and maybe FLR support will become more >> widespread. > I did read that Wikipedia entry after your referenced excerpt. To my > mind, if a manufacturer claims support for the ACPI or PCIe spec and > doesn't implement certain portions of those specs(some are optional > after all), said manufacturer has an obligation to make that clear to > your customers and users. But then, that's just me. Anyway, this > information gives me what I need to ask the right questions of tech > support before purchasing. > I think most motherboards should support this. I've also had it confirmed by nVidia that they support FLR on all current Quadro cards greater than or equal to Quadro 2000, on Tesla C2050 and higher and M2050 and higher, and on new VGX and GRID cards. > >>> From everything I've read, solutions that rely on any form of remote >>> display protocols would be limited to a subset of Direct3D >>> functions. Furthermore, these would vary from one implementation to >>> another, thus making them far less attractive for gaming than VGA >>> passthrough... Well, in my opinion anyway. >>> >>> VirtualBox's seamless mode is pretty nifty. But it's a Type 2 >>> Hypervisor and relies on paravirtualized drivers that also suffer >>> from the same limitations as remote display protocols. It's great >>> for most things, but gaming is not one of them. And I'm speaking >>> from personal experience. Though I haven't used them myself, the >>> same would seem to hold true of Parallel's and VMWare's >>> 'Workstation' offerings. At least, as far as I've gathered. >>> >>> FYI, the Type 1 Hypervisors from Parallel's and VMWare* are priced >>> waaayyy outside my budget. >>> >> I understand that you want full 3D functionality for Windows gaming >> but maybe you'll find the subset of 3D functionality for the Linux >> machine acceptable. I have looked into VirtualGL and with TurboVNC, >> you might get a pretty decent desktop environment and it seems like >> most of the features are there already. It appears that the 3D is >> rendered by hardware/GPU before it is streamed through VNC or Spice. >> So it seems that you would need another GPU for that. You can find >> more info on VirtualGL here: >> >> http://www.virtualgl.org/ > Upon further investigation, the only option that is available to > remotely translate Windows 3D apps is Microsoft's own RemoteFX. In > which case, Microsoft products would be the foundation of my software > stack... Something I'm trying to avoid. I was just giving you the options I could think of OTOH that would let you share a Windows desktop with a Linux desktop, or rather share the desktop of one VM with the host machine. >> >> Also the line between a type 1 and type 2 hypervisor tend to get a >> bit blurry. The point with type 1 is that it has access to ring-0 so >> that it can get access directly to the hardware to be passed through >> to the guests (I did confuse 'host' and 'guest' in my prior post). It >> also doesn't need to ask the host OS for permission in the same way >> as a type 2 hypervisor which is likely to give performance advantages >> in some cases. >> >> However, even a type 2 hypervisor, although it is run as an >> application inside the OS can get "type 1" like privileges. By >> patching into the kernel and/or using special "dummy drivers" for >> hardware to be shared with VMs you can achieve pretty much the same >> thing, ergo it is no longer clear whether the hypervisor is a type 1 >> or type 2. >> >> There is an article about it from the old IBM Mainframe days but I >> can't seem to find it. >> > You might be right, the performance of a Type 2 Hypervisor may be > sufficient. Regardless, I'd still have roughly the same hardware > requirements as if I were going to use a Type 1 Hypervisor. I'd still > need the same CPU, RAM, GPU, and storage requirements as I've already > put forth. I could omit the potentially necessary additional > components for use with a Type 1 Hypervisor. Things like USB > controller, NIC, or sound card. But those costs would be replaced > with the cost of licensing the Type2 Hypervisor. > > In which case, I don't really gain or lose anything by experimenting > with Type 1 Hypervisors... At any rate, I could compare and contrast > the performance of Type 1 and Type 2 Hypervisors using Paralles' and > VMWare's trialware. It might take a good long while, but it would be > an adventure. >>> >>> *I only found out about VMWare's 'free' vSphere after I'd written >>> this response. >>> > >>>> Also, it is highly recommended that you use ECC RAM for such >>>> applications and it doesn't hurt to dedicate a few gigs of it to >>>> the ZFS as RAM is used for cache. The good news is that most >>>> motherboards with good chipsets support ECC RAM even though you >>>> might not find anything about it in the user manuals. >>> Again, thanks for the thorough explanation. This gives me a great >>> deal to think about. The more I learn about ZFS, the less appealing >>> it becomes. And by that I mean the confusion over which version of >>> ZFS is in what OS? And just how well maintained the OSes supporting >>> ZFS are? Now I have additional hardware considerations to keep in >>> mind that may (or may not) make the cost of ZFS RAID-Z pool >>> comparable to a hardware RAID5/6 solution anyway. Do you have any >>> suggestions as to which of LSI HBAs I should be considering? I >>> haven't found an HCL for ZFS in my searches. >>> >>> Out of curiosity --- and if you would happen to know --- do you >>> think what you suggest about the HBA and SAS drives for ZFS also >>> applies to Btrfs? I'm assuming it would, but I'd appreciate some >>> confirmation. >>> >>> It's funny how the "I" in RAID never really seems to apply... >>> Especially since it looks more and more like using ZFS or Btrfs will >>> require I commit myself, from the start, to one or the other and a >>> discrete HBA. Transitioning from an integrated SATA controller(s) >>> and mdadm seems rather impractical. If I understand what's involved >>> in doing so correctly. It may turn out that anything other than >>> mdadm is price prohibitive. >>> >> >> I don't think you will have a problem with getting ZFS to run and if >> that's your only goal then you don't need to be very picky with your >> choice of hardware. I find ZFS pretty easy and handy to use. I has >> really great functionality and I don't have many bad things to say >> about it so far. ZFS is a filesystem (along with a couple of software >> tools to administrate it) just like EXT4 or NTFS so hardware support >> depends on the platform it runs on. >> >> But the point with using ZFS is to get maximum protection against >> data corruption and that's where the selection of hardware gets >> limited and there are "best practices" set up to achieve that. I have >> not tested ZFS on any other platform than on OpenSolaris and >> OpenIndiana but I do know that it is well implemented on that >> platform and more mature there than on any other (non-solaris) >> platform. Another advantage with the OSOL/OI platform is that the >> CIFS functionality is implemented in the kernel space and not in the >> userland which will give advantages performance wise if you intend to >> share files with other windows computers. (I don't deny that Samba is >> pretty good on Linux too. There are some benchmarks on the phoronix >> website comparing samba with NFS and they are in favor of Samba on >> those benchmarks...) The second best implementation is found with >> FreeBSD and it is probably fairly mature but I haven't tested it >> myself and some people have run into problems with it in the past. >> The Linux version is probably merely at infancy stage and likely not >> yet mature enough for regular use. It is probably not as "bad" as >> btrfs though. There is quite a bit of information about it on the >> phoronix.com website (and probably also at lwn.net): >> >> http://www.phoronix.com/scan.php?page=news_item&px=MTE4Nzc >> > My goal wasn't just to experiment with Btrfs, mdamd, or ZFS, if that's > what you meant by, "with getting ZFS to run and if that's your only > goal". I actually intend to use it 'in production'. In fact, the > secondary role (Linux desktop being primary) for my proposed > Virtualization rig is as file server (incl. httpd). Windows gaming is > a tertiary or quaternary concern for me. So, finding out that the > "best practices" for implementing ZFS include hardware I hadn't > anticipated, is a bit off-putting. > > The diversity in ZFS implementations is what I meant about being > confused. I'm not as familiar with the underlying platforms that > utilize ZFS (other than Linux, and not with ZFS in use). Without that > familiarity, it makes it more difficult to gauge which of those > platforms would suit my purposes. For example, I had read a little > bit about the degraded CIFS performance on FreeBSD and Linux due to > their reliance on Samba (it residing in user-space being the issue). > > BTW, I meant to ask how you came to the conclusion that ECC RAM is > supported on desktop motherboards? It's always been my understanding > that you could use ECC RAM on such hardware, but there was no added > benefit. When I looked at the Gigabyte GA990FX motherboard there was no documentation about it anywhere, nor was it stated in the specifications. When I contacted customer support and asked about it, they sent me screen dumps of BIOS showing that it in fact does support ECC providing different ECC scrubbing options. So you can ask support if you are unsure. The benefit of ECC is that there is a parity bit that checks the integrity of the data that is present in the RAM. We have cosmic radiation and bit flips do occur, also the memory can turn out to be faulty. It has been debated whether we really "need" this on a desktop. The finer litography of the hardware is likely to make it more sensitive to such failures and bit flips than before so it makes more sense to use ECC today than in the past. If you are unlucky, you computer will crash because of that. Some files may get corrupted in the process. It may not happen very often but it does happen occasionally, hopefully, the bit flips happen in an address space that currently is not in use. If you run a server on the other hand then you are likely to run into freezes and crashes eventually (it may depend on how long uptimes were talking about). Using ECC RAM will prevent those crashes and add extra protection. In fact, Microsoft recommends ECC RAM even on desktop computers. ZFS does offer protection against data corruption but if you are unlucky, some data corruption may go by undetected when written from RAM. ZFS (or any other filesystem) will write the damaged data to disk and be unable to automatically detect the corruption. This is why using ECC RAM with ZFS is "strongly recommended" in the best practices. >> A search there on ZFS will give more articles. The latest official >> version of ZFS is 28 and is probably implemented in both Linux, and >> FreeBSD by now. Later versions have been released since Oracle killed >> the OpenSolaris project and can be found with the commercial >> closed-source Solaris platform that is supplied by Oracle. Things >> have happened since Oracle pulled the plug on OSOL project and >> leading developers behind the ZFS project such as Jeff Bonwick left >> Sun (after the acquisition by Oracle) and joined up with the Illumos >> team instead. So you cannot determine the stability of ZFS and ZPOOL >> merely by looking into the version number unfortunately and I >> wouldn't expect the FreeBSD implementation to be as stable as the >> Solaris implementation. It just takes time for the implementation to >> mature and the bugs to be weeded out and it just happens to have been >> around for Solaris/OpenSolaris/Illumos for much longer than the other >> platforms and the Solaris/Illumos version also happens to get first >> dibs on the features. Among the Illumos people there is an ambition >> to drop the version numbering altogether and instead talk about >> available features. >> > One of the two ZFS implementations on Linux has reached version 28, > the other is at version 23 and seems to be abandoned or stagnant (last > release was May 2011). I'm not quite sure what the status of ZFS on > FreeBSD is. From this table > on Wikipedia, ZFS is > at version 28. However the table notes that there is no CIFS or iSCSI > support, which I'll try to independently confirm. And, as you say, > the fact that ZFS (and Solaris as a whole) has essentially been > forked, with the re-consolidation of Solaris as closed-source, just > adds to the confusion. It's possible any given build of Illumos' > version 28 of ZFS could have features or bug fixes no present in > Oracle's version 33. I don't know much about FreeBSD but in Solaris/Illumos the CIFS is implemented in the kernel space, in platforms such as Linux and BSD it is provided by the Samba framework in the userspace. If you want iSCSI then you have full support for it in Illumos based operating systems. Also keep in mind that later version storage pools are not readable on systems with lower versions of zfs/zpool. zpool 28 is implemented in FreeBSD 9.0 and onwards. To my knowledge the ZFSonLinux project also has implemented zpool version 28. It should be noted that people also have had problems with migrating a ZFS pool from one platform to another even though the version numbers matched. >> The recommendation to use SAS hard drives is not so much about the >> quality of the hard drives themselves as it is about the SAS >> protocol. The SAS protocol simply handles SCSI transport commands in >> a better and more reliable manner than do SATA. I believe any decent >> SAS drive would do. As for HBAs I wrote a list with LSI based >> hardware a while ago here: >> >> https://www.illumos.org/boards/1/topics/572 >> >> the thing is that a lot of OEMs such as IBM, HP, Cisco, >> Fujitsu-Siemens, Dell, ... supply their branded HBAs with LSI >> circuitry on them. What hardware to choose depends on what you're >> looking for. If you want an 8-port controller I would go for Intel >> SASUC8I or LSI SAS3801E-R. If you want SAS/SATA3 with 6.0 Gb/s then >> LSI's LSI SAS3801E-R series cards would be a better choice. I don't >> know what OEMs have come up with in the SATA3 department since I >> wrote that list but the chips to look for in that case are the LSI >> MegaRAID 2004/2008/2016e depending on how many ports you want. >> >> If you want to read a further discussion about reliability of >> different RAID setups I made a post about this in the following >> thread (last post): >> >> http://communities.intel.com/thread/25945 >> > The cost of the drives is marginally higher than the drives I had > budgeted, but including the cost of an SAS HBA is problematic. I > hadn't expected purchasing an HBA from the very start. I'd hoped to > deffer such a purchase for a bit, but you are saying that would be > ill-advised. How likely is it I would encounter problems using SATA > drives in the interim? > The problem with "normal" hardware is that the error handling is internal. If a hard drive is starting to have bad sectors, the drive will handle them internally and reallocate the bad sectors. You will not notice anything and the errors will not be reported to the system. At most you will experience sluggish performance, perhaps a freeze. When things go so bad that errors are starting to become visible, then it is too late to do anything about it, the drive is already dead. In the past the drives would return "garbage", in the modern days the drive will reread the sector over and over again while trying to recalibrate the head which gives rise tio the characteristic click-of-death noise. If you use a "cheap" HBA with say ZFS, the tools for monitoring the hardware such as iostat will be pretty much useless. Things will 'look' just fine with no errors and when errors start to show, they will happen out of the blue with no prior warning. The system drive of a ZFS file server that I run just crashed like that without warning. Prior to that, all I had on the drive were some corrupt blocks of the hard drive image of a virtual machine. It was connected to the Southbridge OnChip SATA controller of the motherboard. I didn't cry about it although there were some system files that I would have liked to keep though. I replaced it with a server grade SATA drive (WD RE4). I have suffered corruption on that drive on one of the virtual hard drive images. Since I don't see much sense in using RAID on the system drive (other people may beg to differ) I enabled the "ditto blocks" feature on that drive and recovered the image file using 'ddrescue'. The drive is doing fine ever since. On the storage pool of that system I have already replaced two SATA drives on my SAS controller bacause they were going to die. What happened was that the server started to freeze but I couldn't tell what was the problem. Everything looked ok with iostat, was it a driver issue? I couldn't tell. Then eventually I started to see 'media errors' with iostat and when I replaced the drive the pool didn't freeze anymore. Then the same thing happened again and I replaced another hard drive like that. That's the reality of that, if the drives were SAS I would have been able to tell what's wrong at an earlier stage. There was a discussion about this about 6 months ago on the openindiana-discuss mailing list. > Have you seen any price/feature advantage to reseller versions of LSI > OEM products? I would think the offerings from Cisco, Dell, HP, and > IBM would come at a premium as opposed to purchasing LSI branded > hardware. Anyway, I thought there might be specific models from > particular manufacturers to meet the "best practices" for ZFS. > However, from your suggestions, I gather it really doesn't matter as > long as the HBA is Intel or LSI? > That's something you have to look for at your dealers. My experience is that the OEM versions generally are cheaper than LSI branded products. You can compare yourself here: Intel SASUC8I http://amzn.to/QjtOR9 LSI 3081E-R http://amzn.to/USps9x Both are essentially the same card but the original LSI one is more expensive than the one from Intel. > I wonder, should we perhaps move the discussion of ZFS to private > email? It is a bit off-topic. I think a better idea is to take this to the openindiana-discuss mailing list and/or the FreeNAS mailing lists/forums as other people with ZFS experience will read your posts. If you post on the openindiana-discuss I will read your post there as well. > > > _______________________________________________ > Xen-users mailing list > Xen-users@lists.xen.org > http://lists.xen.org/xen-users --------------000304020608000503070706 Content-Type: text/html; charset="ISO-8859-1" Content-Transfer-Encoding: 7bit On 2012-09-27 03:34, ShadesOfGrey wrote:
Re: [Xen-users] Recommendations for Virtulization Hardware
On 09/24/2012 08:49 AM, Robin Axelsson wrote:
On 2012-09-24 05:45, ShadesOfGrey wrote:
Sorry for the late response, I've had a lot to digest.
<snip>
The lack of current information about Xen (and KVM) online has been frustrating — especially finding the many proof of concept videos that demonstrated possibilities but offered no real specifics. Looking for specifics, I sought information from gaming and enthusiast sites; I figured finding confirmation of VT-d and AMD-Vi support on such sites would be more likely. However, I found that wasn't often the case. I did determine that ASRock motherboards seem to be the most likely to support VT-d, ASUS least likely (unless equipped with an Intel 'sanctioned' VT-d chipset). I had narrowed my choices to two motherboards that appear to offer VT-d support and was intending to contact the manufacturer before purchase. Both choices are a bit pricey and I've been reconsidering whether I should look to other motherboards to reduce costs.

Some motherboards support IOMMU even though it is not found in the user manual or specified on the website. Your best bet is to ask customer support. A guy posted here that he got it working on an Intel motherboard that doesn't even have options for it in the BIOS, so it seems that in some cases it is only up to the CPU. This is not the case with AMD though as I stated before. I have bought a couple of Gigabyte GA990FX-UD7 myself, they are stable and have a good layout. They have support for IOMMU but I haven't tested it thoroughly enough to fully confirm this although I don't believe there would be any problem.

I'm aware of this.  In fact, I only have anecdotal evidence that the Gigabyte G1.Sniper 3 has IOMMU (VT-d) support.  I intend to query the manufacturers, seeking confirmation of IOMMU support, of every motherboard that ends up on my short list.  I may include other Z77 motherboards from MSI and Gigabyte, since there is concrete evidence that the Z77 chipset does support IOMMU.  I did focus, however, on those motherboards I had some inkling could support IOMMU.  Now I'm trying to expand my selection process to include less expensive options.
It surprises me that ASRock and ASUS are so different. ASRock is, or at least used to be a subsidiary of ASUS so there shouldn't be that much difference between them.
Same here.  But I guess things changed after ASRock was spun-off.

<snip>
This is precisely the kind of information I was looking for from the threads I started on Ars Technica. It's just unfortunate that FLR and D3 D0 support aren't often found in the tech specs of must expansion hardware. However, now that I know what to ask, I'll try contacting hardware manufacturers prior to purchasing any expansion hardware. Thank you!

D3 and D0 are power states defined for devices in the ACPI specification and can be used to control the supply voltage (Vcc) to PCI and PCIe devices. You can find more information about it here for example:

http://en.wikipedia.org/wiki/Advanced_Configuration_and_Power_Interface

---------------

Device states

The device states D0-D3 are device-dependent:

  • D0 Fully On is the operating state.
  • D1 and D2 are intermediate power-states whose definition varies by device.
  • D3 Off has the device powered off and unresponsive to its bus.
---------------

So, either it works for a certain type of hardware or it doesn't and I wouldn't expect a vendor to state this "support" in the specifications since it isn't a "feature" in and of itself if you get me. But maybe this will change and maybe FLR support will become more widespread.
I did read that Wikipedia entry after your referenced excerpt.  To my mind, if a manufacturer claims support for the ACPI or PCIe spec and doesn't implement certain portions of those specs(some are optional after all), said manufacturer has an obligation to make that clear to your customers and users.  But then, that's just me.  Anyway, this information gives me what I need to ask the right questions of tech support before purchasing.

I think most motherboards should support this.

I've also had it confirmed by nVidia that they support FLR on all current Quadro cards greater than or equal to Quadro 2000, on Tesla C2050 and higher and M2050 and higher, and on new VGX and GRID cards.

<snip>
From everything I've read, solutions that rely on any form of remote display protocols would be limited to a subset of Direct3D functions. Furthermore, these would vary from one implementation to another, thus making them far less attractive for gaming than VGA passthrough... Well, in my opinion anyway.

VirtualBox's seamless mode is pretty nifty. But it's a Type 2 Hypervisor and relies on paravirtualized drivers that also suffer from the same limitations as remote display protocols. It's great for most things, but gaming is not one of them. And I'm speaking from personal experience. Though I haven't used them myself, the same would seem to hold true of Parallel's and VMWare's 'Workstation' offerings. At least, as far as I've gathered.

FYI, the Type 1 Hypervisors from Parallel's and VMWare* are priced waaayyy outside my budget.

I understand that you want full 3D functionality for Windows gaming but maybe you'll find the subset of 3D functionality for the Linux machine acceptable. I have looked into VirtualGL and with TurboVNC, you might get a pretty decent desktop environment and it seems like most of the features are there already. It appears that the 3D is rendered by hardware/GPU before it is streamed through VNC or Spice. So it seems that you would need another GPU for that. You can find more info on VirtualGL here:

http://www.virtualgl.org/
Upon further investigation, the only option that is available to remotely translate Windows 3D apps is Microsoft's own RemoteFX.  In which case, Microsoft products would be the foundation of my software stack...  Something I'm trying to avoid.
I was just giving you the options I could think of OTOH that would let you share a Windows desktop with a Linux desktop, or rather share the desktop of one VM with the host machine.


Also the line between a type 1 and type 2 hypervisor tend to get a bit blurry. The point with type 1 is that it has access to ring-0 so that it can get access directly to the hardware to be passed through to the guests (I did confuse 'host' and 'guest' in my prior post). It also doesn't need to ask the host OS for permission in the same way as a type 2 hypervisor which is likely to give performance advantages in some cases.

However, even a type 2 hypervisor, although it is run as an application inside the OS can get "type 1" like privileges. By patching into the kernel and/or using special "dummy drivers" for hardware to be shared with VMs you can achieve pretty much the same thing, ergo it is no longer clear whether the hypervisor is a type 1 or type 2.

There is an article about it from the old IBM Mainframe days but I can't seem to find it.

You might be right, the performance of a Type 2 Hypervisor may be sufficient.  Regardless, I'd still have roughly the same hardware requirements as if I were going to use a Type 1 Hypervisor.  I'd still need the same CPU, RAM, GPU, and storage requirements as I've already put forth.  I could omit the potentially necessary additional components for use with a Type 1 Hypervisor.  Things like USB controller, NIC, or sound card.  But those costs would be replaced with the cost of licensing the Type2 Hypervisor.

In which case, I don't really gain or lose anything by experimenting with Type 1 Hypervisors...  At any rate, I could compare and contrast the performance of Type 1 and Type 2 Hypervisors using Paralles' and VMWare's trialware.  It might take a good long while, but it would be an adventure.

*I only found out about VMWare's 'free' vSphere after I'd written this response.

<snip>
Also, it is highly recommended that you use ECC RAM for such applications and it doesn't hurt to dedicate a few gigs of it to the ZFS as RAM is used for cache. The good news is that most motherboards with good chipsets support ECC RAM even though you might not find anything about it in the user manuals.
Again, thanks for the thorough explanation. This gives me a great deal to think about. The more I learn about ZFS, the less appealing it becomes. And by that I mean the confusion over which version of ZFS is in what OS? And just how well maintained the OSes supporting ZFS are? Now I have additional hardware considerations to keep in mind that may (or may not) make the cost of ZFS RAID-Z pool comparable to a hardware RAID5/6 solution anyway. Do you have any suggestions as to which of LSI HBAs I should be considering? I haven't found an HCL for ZFS in my searches.

Out of curiosity — and if you would happen to know — do you think what you suggest about the HBA and SAS drives for ZFS also applies to Btrfs? I'm assuming it would, but I'd appreciate some confirmation.

It's funny how the "I" in RAID never really seems to apply... Especially since it looks more and more like using ZFS or Btrfs will require I commit myself, from the start, to one or the other and a discrete HBA. Transitioning from an integrated SATA controller(s) and mdadm seems rather impractical. If I understand what's involved in doing so correctly. It may turn out that anything other than mdadm is price prohibitive.


I don't think you will have a problem with getting ZFS to run and if that's your only goal then you don't need to be very picky with your choice of hardware. I find ZFS pretty easy and handy to use. I has really great functionality and I don't have many bad things to say about it so far. ZFS is a filesystem (along with a couple of software tools to administrate it) just like EXT4 or NTFS so hardware support depends on the platform it runs on.

But the point with using ZFS is to get maximum protection against data corruption and that's where the selection of hardware gets limited and there are "best practices" set up to achieve that. I have not tested ZFS on any other platform than on OpenSolaris and OpenIndiana but I do know that it is well implemented on that platform and more mature there than on any other (non-solaris) platform. Another advantage with the OSOL/OI platform is that the CIFS functionality is implemented in the kernel space and not in the userland which will give advantages performance wise if you intend to share files with other windows computers. (I don't deny that Samba is pretty good on Linux too. There are some benchmarks on the phoronix website comparing samba with NFS and they are in favor of Samba on those benchmarks...) The second best implementation is found with FreeBSD and it is probably fairly mature but I haven't tested it myself and some people have run into problems with it in the past. The Linux version is probably merely at infancy stage and likely not yet mature enough for regular use. It is probably not as "bad" as btrfs though. There is quite a bit of information about it on the phoronix.com website (and probably also at lwn.net):

http://www.phoronix.com/scan.php?page=news_item&px=MTE4Nzc

My goal wasn't just to experiment with Btrfs, mdamd, or ZFS, if that's what you meant by, "with getting ZFS to run and if that's your only goal".  I actually intend to use it 'in production'.  In fact, the secondary role (Linux desktop being primary) for my proposed Virtualization rig is as file server (incl. httpd).  Windows gaming is a tertiary or quaternary concern for me.  So, finding out that the "best practices" for implementing ZFS include hardware I hadn't anticipated, is a bit off-putting.

The diversity in ZFS implementations is what I meant about being confused.  I'm not as familiar with the underlying platforms that utilize ZFS (other than Linux, and not with ZFS in use).  Without that familiarity, it makes it more difficult to gauge which of those platforms would suit my purposes.  For example, I had read a little bit about the degraded CIFS performance on FreeBSD and Linux due to their reliance on Samba (it residing in user-space being the issue).

BTW, I meant to ask how you came to the conclusion that ECC RAM is supported on desktop motherboards?  It's always been my understanding that you could use ECC RAM on such hardware, but there was no added benefit.
When I looked at the Gigabyte GA990FX motherboard there was no documentation about it anywhere, nor was it stated in the specifications. When I contacted customer support and asked about it, they sent me screen dumps of BIOS showing that it in fact does support ECC providing different ECC scrubbing options. So you can ask support if you are unsure.

The benefit of ECC is that there is a parity bit that checks the integrity of the data that is present in the RAM. We have cosmic radiation and bit flips do occur, also the memory can turn out to be faulty. It has been debated whether we really "need" this on a desktop. The finer litography of the hardware is likely to make it more sensitive to such failures and bit flips than before so it makes more sense to use ECC today than in the past.  If you are unlucky, you computer will crash because of that. Some files may get corrupted in the process. It may not happen very often but it does happen occasionally, hopefully, the bit flips happen in an address space that currently is not in use. If you run a server on the other hand then you are likely to run into freezes and crashes eventually (it may depend on how long uptimes were talking about). Using ECC RAM will prevent those crashes and add extra protection. In fact, Microsoft recommends ECC RAM even on desktop computers.

ZFS does offer protection against data corruption but if you are unlucky, some data corruption may go by undetected when written from RAM. ZFS (or any other filesystem) will write the damaged data to disk and be unable to automatically detect the corruption. This is why using ECC RAM with ZFS is "strongly recommended" in the best practices.

A search there on ZFS will give more articles. The latest official version of ZFS is 28 and is probably implemented in both Linux, and FreeBSD by now. Later versions have been released since Oracle killed the OpenSolaris project and can be found with the commercial closed-source Solaris platform that is supplied by Oracle. Things have happened since Oracle pulled the plug on OSOL project and leading developers behind the ZFS project such as Jeff Bonwick left Sun (after the acquisition by Oracle) and joined up with the Illumos team instead. So you cannot determine the stability of ZFS and ZPOOL merely by looking into the version number unfortunately and I wouldn't expect the FreeBSD implementation to be as stable as the Solaris implementation. It just takes time for the implementation to mature and the bugs to be weeded out and it just happens to have been around for Solaris/OpenSolaris/Illumos for much longer than the other platforms and the Solaris/Illumos version also happens to get first dibs on the features. Among the Illumos people there is an ambition to drop the version numbering altogether and instead talk about available features.

One of the two ZFS implementations on Linux has reached version 28, the other is at version 23 and seems to be abandoned or stagnant (last release was May 2011).  I'm not quite sure what the status of ZFS on FreeBSD is.  From this table on Wikipedia, ZFS is at version 28.  However the table notes that there is no CIFS or iSCSI support, which I'll try to independently confirm.  And, as you say, the fact that ZFS (and Solaris as a whole) has essentially been forked, with the re-consolidation of Solaris as closed-source, just adds to the confusion.  It's possible any given build of Illumos' version 28 of ZFS could have features or bug fixes no present in Oracle's version 33.
I don't know much about FreeBSD but in Solaris/Illumos the CIFS is implemented in the kernel space, in platforms such as Linux and BSD it is provided by the Samba framework in the userspace. If you want iSCSI then you have full support for it in Illumos based operating systems.

Also keep in mind that later version storage pools are not readable on systems with lower versions of zfs/zpool. zpool 28 is implemented in FreeBSD 9.0 and onwards. To my knowledge the ZFSonLinux project also has implemented zpool version 28.

It should be noted that people also have had problems with migrating a ZFS pool from one platform to another even though the version numbers matched.
The recommendation to use SAS hard drives is not so much about the quality of the hard drives themselves as it is about the SAS protocol. The SAS protocol simply handles SCSI transport commands in a better and more reliable manner than do SATA. I believe any decent SAS drive would do. As for HBAs I wrote a list with LSI based hardware a while ago here:

https://www.illumos.org/boards/1/topics/572

the thing is that a lot of OEMs such as IBM, HP, Cisco, Fujitsu-Siemens, Dell, ... supply their branded HBAs with LSI circuitry on them. What hardware to choose depends on what you're looking for. If you want an 8-port controller I would go for Intel SASUC8I or LSI SAS3801E-R. If you want SAS/SATA3 with 6.0 Gb/s then LSI's LSI SAS3801E-R series cards would be a better choice. I don't know what OEMs have come up with in the SATA3 department since I wrote that list but the chips to look for in that case are the LSI MegaRAID 2004/2008/2016e depending on how many ports you want.

If you want to read a further discussion about reliability of different RAID setups I made a post about this in the following thread (last post):

http://communities.intel.com/thread/25945

The cost of the drives is marginally higher than the drives I had budgeted, but including the cost of an SAS HBA is problematic.  I hadn't expected purchasing an HBA from the very start.  I'd hoped to deffer such a purchase for a bit, but you are saying that would be ill-advised.  How likely is it I would encounter problems using SATA drives in the interim?


The problem with "normal" hardware is that the error handling is internal. If a hard drive is starting to have bad sectors, the drive will handle them internally and reallocate the bad sectors. You will not notice anything and the errors will not be reported to the system. At most you will experience sluggish performance, perhaps a freeze. When things go so bad that errors are starting to become visible, then it is too late to do anything about it, the drive is already dead. In the past the drives would return "garbage", in the modern days the drive will reread the sector over and over again while trying to recalibrate the head which gives rise tio the characteristic click-of-death noise.

If you use a "cheap" HBA with say ZFS, the tools for monitoring the hardware such as iostat will be pretty much useless. Things will 'look' just fine with no errors and when errors start to show, they will happen out of the blue with no prior warning. The system drive of a ZFS file server that I run just crashed like that without warning. Prior to that, all I had on the drive were some corrupt blocks of the hard drive image of a virtual machine. It was connected to the Southbridge OnChip SATA controller of the motherboard. I didn't cry about it although there were some system files that I would have liked to keep though. I replaced it with a server grade SATA drive (WD RE4). I have suffered corruption on that drive on one of the virtual hard drive images. Since I don't see much sense in using RAID on the system drive (other people may beg to differ) I enabled the "ditto blocks" feature on that drive and recovered the image file using 'ddrescue'. The drive is doing fine ever since.

On the storage pool of that system I have already replaced two SATA drives on my SAS controller bacause they were going to die. What happened was that the server started to freeze but I couldn't tell what was the problem. Everything looked ok with iostat, was it a driver issue? I couldn't tell. Then eventually I started to see 'media errors' with iostat and when I replaced the drive the pool didn't freeze anymore. Then the same thing happened again and I replaced another hard drive like that. That's the reality of that, if the drives were SAS I would have been able to tell what's wrong at an earlier stage. There was a discussion about this about 6 months ago on the openindiana-discuss mailing list.

Have you seen any price/feature advantage to reseller versions of LSI OEM products?  I would think the offerings from Cisco, Dell, HP, and IBM would come at a premium as opposed to purchasing LSI branded hardware.  Anyway, I thought there might be specific models from particular manufacturers to meet the "best practices" for ZFS.  However, from your suggestions, I gather it really doesn't matter as long as the HBA is Intel or LSI?


That's something you have to look for at your dealers. My experience is that the OEM versions generally are cheaper than LSI branded products. You can compare yourself here:

Intel SASUC8I
http://amzn.to/QjtOR9

LSI 3081E-R
http://amzn.to/USps9x

Both are essentially the same card but the original LSI one is more expensive than the one from Intel.


I wonder, should we perhaps move the discussion of ZFS to private email?  It is a bit off-topic.

I think a better idea is to take this to the openindiana-discuss mailing list and/or the FreeNAS mailing lists/forums as other people with ZFS experience will read your posts. If you post on the openindiana-discuss I will read your post there as well.


_______________________________________________
Xen-users mailing list
Xen-users@lists.xen.org
http://lists.xen.org/xen-users

--------------000304020608000503070706-- --===============8613724340339552063== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users --===============8613724340339552063==-- From xen-users-bounces@lists.xen.org Fri Sep 28 14:24:56 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Fri, 28 Sep 2012 14:24:56 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1THbTd-0006MB-56; Fri, 28 Sep 2012 14:23:37 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1THbTa-0006M6-Pl for xen-users@lists.xen.org; Fri, 28 Sep 2012 14:23:35 +0000 Received: from [85.158.137.99:24442] by server-14.bemta-3.messagelabs.com id BB/51-25886-5E2B5605; Fri, 28 Sep 2012 14:23:33 +0000 X-Env-Sender: gu99roax@student.chalmers.se X-Msg-Ref: server-13.tower-217.messagelabs.com!1348842211!19546606!1 X-Originating-IP: [213.199.154.206] X-SpamReason: No, hits=1.4 required=7.0 tests=BODY_RANDOM_LONG, HTML_20_30,HTML_MESSAGE,ML_RADAR_SPEW_LINKS_8,spamassassin: X-StarScan-Received: X-StarScan-Version: 6.6.1.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 27910 invoked from network); 28 Sep 2012 14:23:31 -0000 Received: from am1ehsobe003.messaging.microsoft.com (HELO am1outboundpool.messaging.microsoft.com) (213.199.154.206) by server-13.tower-217.messagelabs.com with AES128-SHA encrypted SMTP; 28 Sep 2012 14:23:31 -0000 Received: from mail63-am1-R.bigfish.com (10.3.201.243) by AM1EHSOBE008.bigfish.com (10.3.204.28) with Microsoft SMTP Server id 14.1.225.23; Fri, 28 Sep 2012 14:23:30 +0000 Received: from mail63-am1 (localhost [127.0.0.1]) by mail63-am1-R.bigfish.com (Postfix) with ESMTP id F286A2A0125 for ; Fri, 28 Sep 2012 14:23:30 +0000 (UTC) X-Forefront-Antispam-Report: CIP:207.46.4.203; KIP:(null); UIP:(null); IPV:NLI; H:SN2PRD0102HT019.prod.exchangelabs.com; RD:none; EFVD:NLI X-SpamScore: -6 X-BigFish: PS-6(zzbb2dI98dI9371I3071M936eI146fI1b0bIc85dh1432I2176M1447I31eakd6f1izz1d18h1202h1d1ah1d2ah1082kzz8275ch1730fah17326ah8275bhf69b8h8275dh177df4h172cdfhf3c47lz2dh2a8h668h839h8e2h8e3hd25hf0ah107ah10d2h1288h12a5h12bdh137ahbe9i1155h) Received: from mail63-am1 (localhost.localdomain [127.0.0.1]) by mail63-am1 (MessageSwitch) id 1348842207752931_7407; Fri, 28 Sep 2012 14:23:27 +0000 (UTC) Received: from AM1EHSMHS001.bigfish.com (unknown [10.3.201.231]) by mail63-am1.bigfish.com (Postfix) with ESMTP id AAEB74011F for ; Fri, 28 Sep 2012 14:23:27 +0000 (UTC) Received: from SN2PRD0102HT019.prod.exchangelabs.com (207.46.4.203) by AM1EHSMHS001.bigfish.com (10.3.207.101) with Microsoft SMTP Server (TLS) id 14.1.225.23; Fri, 28 Sep 2012 14:23:26 +0000 Received: from [10.40.137.93] (217.208.204.161) by pod51000.outlook.com (10.27.90.46) with Microsoft SMTP Server (TLS) id 14.15.108.4; Fri, 28 Sep 2012 14:23:22 +0000 Message-ID: <5065B2D8.8070401@student.chalmers.se> Date: Fri, 28 Sep 2012 16:23:20 +0200 From: Robin Axelsson User-Agent: Mozilla/5.0 (Windows NT 5.2; WOW64; rv:9.0) Gecko/20111222 Thunderbird/9.0.1 MIME-Version: 1.0 To: References: <505B86AE.9040507@earthlink.net> <505C8630.2090002@student.chalmers.se> <505FD74E.2050405@earthlink.net> <506056BC.3010705@student.chalmers.se> <5063AD2E.10800@earthlink.net> In-Reply-To: <5063AD2E.10800@earthlink.net> X-Originating-IP: [217.208.204.161] X-OriginatorOrg: student.chalmers.se Subject: Re: [Xen-users] Recommendations for Virtulization Hardware X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list Reply-To: gu99roax@student.chalmers.se List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============8613724340339552063==" Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org --===============8613724340339552063== Content-Type: multipart/alternative; boundary="------------000304020608000503070706" --------------000304020608000503070706 Content-Type: text/plain; charset="ISO-8859-1"; format=flowed Content-Transfer-Encoding: 7bit On 2012-09-27 03:34, ShadesOfGrey wrote: > On 09/24/2012 08:49 AM, Robin Axelsson wrote: >> On 2012-09-24 05:45, ShadesOfGrey wrote: >>> Sorry for the late response, I've had a lot to digest. > >>> The lack of current information about Xen (and KVM) online has been >>> frustrating --- especially finding the many proof of concept videos >>> that demonstrated possibilities but offered no real specifics. >>> Looking for specifics, I sought information from gaming and >>> enthusiast sites; I figured finding confirmation of VT-d and AMD-Vi >>> support on such sites would be more likely. However, I found that >>> wasn't often the case. I did determine that ASRock motherboards seem >>> to be the most likely to support VT-d, ASUS least likely (unless >>> equipped with an Intel 'sanctioned' VT-d chipset). I had narrowed my >>> choices to two motherboards that appear to offer VT-d support and >>> was intending to contact the manufacturer before purchase. Both >>> choices are a bit pricey and I've been reconsidering whether I >>> should look to other motherboards to reduce costs. >> >> Some motherboards support IOMMU even though it is not found in the >> user manual or specified on the website. Your best bet is to ask >> customer support. A guy posted here that he got it working on an >> Intel motherboard that doesn't even have options for it in the BIOS, >> so it seems that in some cases it is only up to the CPU. This is not >> the case with AMD though as I stated before. I have bought a couple >> of Gigabyte GA990FX-UD7 myself, they are stable and have a good >> layout. They have support for IOMMU but I haven't tested it >> thoroughly enough to fully confirm this although I don't believe >> there would be any problem. >> > I'm aware of this. In fact, I only have anecdotal evidence that the > Gigabyte G1.Sniper 3 has IOMMU (VT-d) support. I intend to query the > manufacturers, seeking confirmation of IOMMU support, of every > motherboard that ends up on my short list. I may include other Z77 > motherboards from MSI and Gigabyte, since there is concrete evidence > that the Z77 chipset does support IOMMU. I did focus, however, on > those motherboards I had some inkling could support IOMMU. Now I'm > trying to expand my selection process to include less expensive options. >> It surprises me that ASRock and ASUS are so different. ASRock is, or >> at least used to be a subsidiary of ASUS so there shouldn't be that >> much difference between them. > Same here. But I guess things changed after ASRock was spun-off. > > >>> This is precisely the kind of information I was looking for from the >>> threads I started on Ars Technica. It's just unfortunate that FLR >>> and D3 D0 support aren't often found in the tech specs of must >>> expansion hardware. However, now that I know what to ask, I'll try >>> contacting hardware manufacturers prior to purchasing any expansion >>> hardware. Thank you! >> >> D3 and D0 are power states defined for devices in the ACPI >> specification and can be used to control the supply voltage (Vcc) to >> PCI and PCIe devices. You can find more information about it here for >> example: >> >> http://en.wikipedia.org/wiki/Advanced_Configuration_and_Power_Interface >> >> --------------- >> >> >> Device states >> >> The device states /D0/-/D3/ are device-dependent: >> >> * *D0* /Fully On/ is the operating state. >> * *D1* and *D2* are intermediate power-states whose definition >> varies by device. >> * *D3* /Off/ has the device powered off and unresponsive to its bus. >> >> --------------- >> >> So, either it works for a certain type of hardware or it doesn't and >> I wouldn't expect a vendor to state this "support" in the >> specifications since it isn't a "feature" in and of itself if you get >> me. But maybe this will change and maybe FLR support will become more >> widespread. > I did read that Wikipedia entry after your referenced excerpt. To my > mind, if a manufacturer claims support for the ACPI or PCIe spec and > doesn't implement certain portions of those specs(some are optional > after all), said manufacturer has an obligation to make that clear to > your customers and users. But then, that's just me. Anyway, this > information gives me what I need to ask the right questions of tech > support before purchasing. > I think most motherboards should support this. I've also had it confirmed by nVidia that they support FLR on all current Quadro cards greater than or equal to Quadro 2000, on Tesla C2050 and higher and M2050 and higher, and on new VGX and GRID cards. > >>> From everything I've read, solutions that rely on any form of remote >>> display protocols would be limited to a subset of Direct3D >>> functions. Furthermore, these would vary from one implementation to >>> another, thus making them far less attractive for gaming than VGA >>> passthrough... Well, in my opinion anyway. >>> >>> VirtualBox's seamless mode is pretty nifty. But it's a Type 2 >>> Hypervisor and relies on paravirtualized drivers that also suffer >>> from the same limitations as remote display protocols. It's great >>> for most things, but gaming is not one of them. And I'm speaking >>> from personal experience. Though I haven't used them myself, the >>> same would seem to hold true of Parallel's and VMWare's >>> 'Workstation' offerings. At least, as far as I've gathered. >>> >>> FYI, the Type 1 Hypervisors from Parallel's and VMWare* are priced >>> waaayyy outside my budget. >>> >> I understand that you want full 3D functionality for Windows gaming >> but maybe you'll find the subset of 3D functionality for the Linux >> machine acceptable. I have looked into VirtualGL and with TurboVNC, >> you might get a pretty decent desktop environment and it seems like >> most of the features are there already. It appears that the 3D is >> rendered by hardware/GPU before it is streamed through VNC or Spice. >> So it seems that you would need another GPU for that. You can find >> more info on VirtualGL here: >> >> http://www.virtualgl.org/ > Upon further investigation, the only option that is available to > remotely translate Windows 3D apps is Microsoft's own RemoteFX. In > which case, Microsoft products would be the foundation of my software > stack... Something I'm trying to avoid. I was just giving you the options I could think of OTOH that would let you share a Windows desktop with a Linux desktop, or rather share the desktop of one VM with the host machine. >> >> Also the line between a type 1 and type 2 hypervisor tend to get a >> bit blurry. The point with type 1 is that it has access to ring-0 so >> that it can get access directly to the hardware to be passed through >> to the guests (I did confuse 'host' and 'guest' in my prior post). It >> also doesn't need to ask the host OS for permission in the same way >> as a type 2 hypervisor which is likely to give performance advantages >> in some cases. >> >> However, even a type 2 hypervisor, although it is run as an >> application inside the OS can get "type 1" like privileges. By >> patching into the kernel and/or using special "dummy drivers" for >> hardware to be shared with VMs you can achieve pretty much the same >> thing, ergo it is no longer clear whether the hypervisor is a type 1 >> or type 2. >> >> There is an article about it from the old IBM Mainframe days but I >> can't seem to find it. >> > You might be right, the performance of a Type 2 Hypervisor may be > sufficient. Regardless, I'd still have roughly the same hardware > requirements as if I were going to use a Type 1 Hypervisor. I'd still > need the same CPU, RAM, GPU, and storage requirements as I've already > put forth. I could omit the potentially necessary additional > components for use with a Type 1 Hypervisor. Things like USB > controller, NIC, or sound card. But those costs would be replaced > with the cost of licensing the Type2 Hypervisor. > > In which case, I don't really gain or lose anything by experimenting > with Type 1 Hypervisors... At any rate, I could compare and contrast > the performance of Type 1 and Type 2 Hypervisors using Paralles' and > VMWare's trialware. It might take a good long while, but it would be > an adventure. >>> >>> *I only found out about VMWare's 'free' vSphere after I'd written >>> this response. >>> > >>>> Also, it is highly recommended that you use ECC RAM for such >>>> applications and it doesn't hurt to dedicate a few gigs of it to >>>> the ZFS as RAM is used for cache. The good news is that most >>>> motherboards with good chipsets support ECC RAM even though you >>>> might not find anything about it in the user manuals. >>> Again, thanks for the thorough explanation. This gives me a great >>> deal to think about. The more I learn about ZFS, the less appealing >>> it becomes. And by that I mean the confusion over which version of >>> ZFS is in what OS? And just how well maintained the OSes supporting >>> ZFS are? Now I have additional hardware considerations to keep in >>> mind that may (or may not) make the cost of ZFS RAID-Z pool >>> comparable to a hardware RAID5/6 solution anyway. Do you have any >>> suggestions as to which of LSI HBAs I should be considering? I >>> haven't found an HCL for ZFS in my searches. >>> >>> Out of curiosity --- and if you would happen to know --- do you >>> think what you suggest about the HBA and SAS drives for ZFS also >>> applies to Btrfs? I'm assuming it would, but I'd appreciate some >>> confirmation. >>> >>> It's funny how the "I" in RAID never really seems to apply... >>> Especially since it looks more and more like using ZFS or Btrfs will >>> require I commit myself, from the start, to one or the other and a >>> discrete HBA. Transitioning from an integrated SATA controller(s) >>> and mdadm seems rather impractical. If I understand what's involved >>> in doing so correctly. It may turn out that anything other than >>> mdadm is price prohibitive. >>> >> >> I don't think you will have a problem with getting ZFS to run and if >> that's your only goal then you don't need to be very picky with your >> choice of hardware. I find ZFS pretty easy and handy to use. I has >> really great functionality and I don't have many bad things to say >> about it so far. ZFS is a filesystem (along with a couple of software >> tools to administrate it) just like EXT4 or NTFS so hardware support >> depends on the platform it runs on. >> >> But the point with using ZFS is to get maximum protection against >> data corruption and that's where the selection of hardware gets >> limited and there are "best practices" set up to achieve that. I have >> not tested ZFS on any other platform than on OpenSolaris and >> OpenIndiana but I do know that it is well implemented on that >> platform and more mature there than on any other (non-solaris) >> platform. Another advantage with the OSOL/OI platform is that the >> CIFS functionality is implemented in the kernel space and not in the >> userland which will give advantages performance wise if you intend to >> share files with other windows computers. (I don't deny that Samba is >> pretty good on Linux too. There are some benchmarks on the phoronix >> website comparing samba with NFS and they are in favor of Samba on >> those benchmarks...) The second best implementation is found with >> FreeBSD and it is probably fairly mature but I haven't tested it >> myself and some people have run into problems with it in the past. >> The Linux version is probably merely at infancy stage and likely not >> yet mature enough for regular use. It is probably not as "bad" as >> btrfs though. There is quite a bit of information about it on the >> phoronix.com website (and probably also at lwn.net): >> >> http://www.phoronix.com/scan.php?page=news_item&px=MTE4Nzc >> > My goal wasn't just to experiment with Btrfs, mdamd, or ZFS, if that's > what you meant by, "with getting ZFS to run and if that's your only > goal". I actually intend to use it 'in production'. In fact, the > secondary role (Linux desktop being primary) for my proposed > Virtualization rig is as file server (incl. httpd). Windows gaming is > a tertiary or quaternary concern for me. So, finding out that the > "best practices" for implementing ZFS include hardware I hadn't > anticipated, is a bit off-putting. > > The diversity in ZFS implementations is what I meant about being > confused. I'm not as familiar with the underlying platforms that > utilize ZFS (other than Linux, and not with ZFS in use). Without that > familiarity, it makes it more difficult to gauge which of those > platforms would suit my purposes. For example, I had read a little > bit about the degraded CIFS performance on FreeBSD and Linux due to > their reliance on Samba (it residing in user-space being the issue). > > BTW, I meant to ask how you came to the conclusion that ECC RAM is > supported on desktop motherboards? It's always been my understanding > that you could use ECC RAM on such hardware, but there was no added > benefit. When I looked at the Gigabyte GA990FX motherboard there was no documentation about it anywhere, nor was it stated in the specifications. When I contacted customer support and asked about it, they sent me screen dumps of BIOS showing that it in fact does support ECC providing different ECC scrubbing options. So you can ask support if you are unsure. The benefit of ECC is that there is a parity bit that checks the integrity of the data that is present in the RAM. We have cosmic radiation and bit flips do occur, also the memory can turn out to be faulty. It has been debated whether we really "need" this on a desktop. The finer litography of the hardware is likely to make it more sensitive to such failures and bit flips than before so it makes more sense to use ECC today than in the past. If you are unlucky, you computer will crash because of that. Some files may get corrupted in the process. It may not happen very often but it does happen occasionally, hopefully, the bit flips happen in an address space that currently is not in use. If you run a server on the other hand then you are likely to run into freezes and crashes eventually (it may depend on how long uptimes were talking about). Using ECC RAM will prevent those crashes and add extra protection. In fact, Microsoft recommends ECC RAM even on desktop computers. ZFS does offer protection against data corruption but if you are unlucky, some data corruption may go by undetected when written from RAM. ZFS (or any other filesystem) will write the damaged data to disk and be unable to automatically detect the corruption. This is why using ECC RAM with ZFS is "strongly recommended" in the best practices. >> A search there on ZFS will give more articles. The latest official >> version of ZFS is 28 and is probably implemented in both Linux, and >> FreeBSD by now. Later versions have been released since Oracle killed >> the OpenSolaris project and can be found with the commercial >> closed-source Solaris platform that is supplied by Oracle. Things >> have happened since Oracle pulled the plug on OSOL project and >> leading developers behind the ZFS project such as Jeff Bonwick left >> Sun (after the acquisition by Oracle) and joined up with the Illumos >> team instead. So you cannot determine the stability of ZFS and ZPOOL >> merely by looking into the version number unfortunately and I >> wouldn't expect the FreeBSD implementation to be as stable as the >> Solaris implementation. It just takes time for the implementation to >> mature and the bugs to be weeded out and it just happens to have been >> around for Solaris/OpenSolaris/Illumos for much longer than the other >> platforms and the Solaris/Illumos version also happens to get first >> dibs on the features. Among the Illumos people there is an ambition >> to drop the version numbering altogether and instead talk about >> available features. >> > One of the two ZFS implementations on Linux has reached version 28, > the other is at version 23 and seems to be abandoned or stagnant (last > release was May 2011). I'm not quite sure what the status of ZFS on > FreeBSD is. From this table > on Wikipedia, ZFS is > at version 28. However the table notes that there is no CIFS or iSCSI > support, which I'll try to independently confirm. And, as you say, > the fact that ZFS (and Solaris as a whole) has essentially been > forked, with the re-consolidation of Solaris as closed-source, just > adds to the confusion. It's possible any given build of Illumos' > version 28 of ZFS could have features or bug fixes no present in > Oracle's version 33. I don't know much about FreeBSD but in Solaris/Illumos the CIFS is implemented in the kernel space, in platforms such as Linux and BSD it is provided by the Samba framework in the userspace. If you want iSCSI then you have full support for it in Illumos based operating systems. Also keep in mind that later version storage pools are not readable on systems with lower versions of zfs/zpool. zpool 28 is implemented in FreeBSD 9.0 and onwards. To my knowledge the ZFSonLinux project also has implemented zpool version 28. It should be noted that people also have had problems with migrating a ZFS pool from one platform to another even though the version numbers matched. >> The recommendation to use SAS hard drives is not so much about the >> quality of the hard drives themselves as it is about the SAS >> protocol. The SAS protocol simply handles SCSI transport commands in >> a better and more reliable manner than do SATA. I believe any decent >> SAS drive would do. As for HBAs I wrote a list with LSI based >> hardware a while ago here: >> >> https://www.illumos.org/boards/1/topics/572 >> >> the thing is that a lot of OEMs such as IBM, HP, Cisco, >> Fujitsu-Siemens, Dell, ... supply their branded HBAs with LSI >> circuitry on them. What hardware to choose depends on what you're >> looking for. If you want an 8-port controller I would go for Intel >> SASUC8I or LSI SAS3801E-R. If you want SAS/SATA3 with 6.0 Gb/s then >> LSI's LSI SAS3801E-R series cards would be a better choice. I don't >> know what OEMs have come up with in the SATA3 department since I >> wrote that list but the chips to look for in that case are the LSI >> MegaRAID 2004/2008/2016e depending on how many ports you want. >> >> If you want to read a further discussion about reliability of >> different RAID setups I made a post about this in the following >> thread (last post): >> >> http://communities.intel.com/thread/25945 >> > The cost of the drives is marginally higher than the drives I had > budgeted, but including the cost of an SAS HBA is problematic. I > hadn't expected purchasing an HBA from the very start. I'd hoped to > deffer such a purchase for a bit, but you are saying that would be > ill-advised. How likely is it I would encounter problems using SATA > drives in the interim? > The problem with "normal" hardware is that the error handling is internal. If a hard drive is starting to have bad sectors, the drive will handle them internally and reallocate the bad sectors. You will not notice anything and the errors will not be reported to the system. At most you will experience sluggish performance, perhaps a freeze. When things go so bad that errors are starting to become visible, then it is too late to do anything about it, the drive is already dead. In the past the drives would return "garbage", in the modern days the drive will reread the sector over and over again while trying to recalibrate the head which gives rise tio the characteristic click-of-death noise. If you use a "cheap" HBA with say ZFS, the tools for monitoring the hardware such as iostat will be pretty much useless. Things will 'look' just fine with no errors and when errors start to show, they will happen out of the blue with no prior warning. The system drive of a ZFS file server that I run just crashed like that without warning. Prior to that, all I had on the drive were some corrupt blocks of the hard drive image of a virtual machine. It was connected to the Southbridge OnChip SATA controller of the motherboard. I didn't cry about it although there were some system files that I would have liked to keep though. I replaced it with a server grade SATA drive (WD RE4). I have suffered corruption on that drive on one of the virtual hard drive images. Since I don't see much sense in using RAID on the system drive (other people may beg to differ) I enabled the "ditto blocks" feature on that drive and recovered the image file using 'ddrescue'. The drive is doing fine ever since. On the storage pool of that system I have already replaced two SATA drives on my SAS controller bacause they were going to die. What happened was that the server started to freeze but I couldn't tell what was the problem. Everything looked ok with iostat, was it a driver issue? I couldn't tell. Then eventually I started to see 'media errors' with iostat and when I replaced the drive the pool didn't freeze anymore. Then the same thing happened again and I replaced another hard drive like that. That's the reality of that, if the drives were SAS I would have been able to tell what's wrong at an earlier stage. There was a discussion about this about 6 months ago on the openindiana-discuss mailing list. > Have you seen any price/feature advantage to reseller versions of LSI > OEM products? I would think the offerings from Cisco, Dell, HP, and > IBM would come at a premium as opposed to purchasing LSI branded > hardware. Anyway, I thought there might be specific models from > particular manufacturers to meet the "best practices" for ZFS. > However, from your suggestions, I gather it really doesn't matter as > long as the HBA is Intel or LSI? > That's something you have to look for at your dealers. My experience is that the OEM versions generally are cheaper than LSI branded products. You can compare yourself here: Intel SASUC8I http://amzn.to/QjtOR9 LSI 3081E-R http://amzn.to/USps9x Both are essentially the same card but the original LSI one is more expensive than the one from Intel. > I wonder, should we perhaps move the discussion of ZFS to private > email? It is a bit off-topic. I think a better idea is to take this to the openindiana-discuss mailing list and/or the FreeNAS mailing lists/forums as other people with ZFS experience will read your posts. If you post on the openindiana-discuss I will read your post there as well. > > > _______________________________________________ > Xen-users mailing list > Xen-users@lists.xen.org > http://lists.xen.org/xen-users --------------000304020608000503070706 Content-Type: text/html; charset="ISO-8859-1" Content-Transfer-Encoding: 7bit On 2012-09-27 03:34, ShadesOfGrey wrote:
Re: [Xen-users] Recommendations for Virtulization Hardware
On 09/24/2012 08:49 AM, Robin Axelsson wrote:
On 2012-09-24 05:45, ShadesOfGrey wrote:
Sorry for the late response, I've had a lot to digest.
<snip>
The lack of current information about Xen (and KVM) online has been frustrating — especially finding the many proof of concept videos that demonstrated possibilities but offered no real specifics. Looking for specifics, I sought information from gaming and enthusiast sites; I figured finding confirmation of VT-d and AMD-Vi support on such sites would be more likely. However, I found that wasn't often the case. I did determine that ASRock motherboards seem to be the most likely to support VT-d, ASUS least likely (unless equipped with an Intel 'sanctioned' VT-d chipset). I had narrowed my choices to two motherboards that appear to offer VT-d support and was intending to contact the manufacturer before purchase. Both choices are a bit pricey and I've been reconsidering whether I should look to other motherboards to reduce costs.

Some motherboards support IOMMU even though it is not found in the user manual or specified on the website. Your best bet is to ask customer support. A guy posted here that he got it working on an Intel motherboard that doesn't even have options for it in the BIOS, so it seems that in some cases it is only up to the CPU. This is not the case with AMD though as I stated before. I have bought a couple of Gigabyte GA990FX-UD7 myself, they are stable and have a good layout. They have support for IOMMU but I haven't tested it thoroughly enough to fully confirm this although I don't believe there would be any problem.

I'm aware of this.  In fact, I only have anecdotal evidence that the Gigabyte G1.Sniper 3 has IOMMU (VT-d) support.  I intend to query the manufacturers, seeking confirmation of IOMMU support, of every motherboard that ends up on my short list.  I may include other Z77 motherboards from MSI and Gigabyte, since there is concrete evidence that the Z77 chipset does support IOMMU.  I did focus, however, on those motherboards I had some inkling could support IOMMU.  Now I'm trying to expand my selection process to include less expensive options.
It surprises me that ASRock and ASUS are so different. ASRock is, or at least used to be a subsidiary of ASUS so there shouldn't be that much difference between them.
Same here.  But I guess things changed after ASRock was spun-off.

<snip>
This is precisely the kind of information I was looking for from the threads I started on Ars Technica. It's just unfortunate that FLR and D3 D0 support aren't often found in the tech specs of must expansion hardware. However, now that I know what to ask, I'll try contacting hardware manufacturers prior to purchasing any expansion hardware. Thank you!

D3 and D0 are power states defined for devices in the ACPI specification and can be used to control the supply voltage (Vcc) to PCI and PCIe devices. You can find more information about it here for example:

http://en.wikipedia.org/wiki/Advanced_Configuration_and_Power_Interface

---------------

Device states

The device states D0-D3 are device-dependent:

  • D0 Fully On is the operating state.
  • D1 and D2 are intermediate power-states whose definition varies by device.
  • D3 Off has the device powered off and unresponsive to its bus.
---------------

So, either it works for a certain type of hardware or it doesn't and I wouldn't expect a vendor to state this "support" in the specifications since it isn't a "feature" in and of itself if you get me. But maybe this will change and maybe FLR support will become more widespread.
I did read that Wikipedia entry after your referenced excerpt.  To my mind, if a manufacturer claims support for the ACPI or PCIe spec and doesn't implement certain portions of those specs(some are optional after all), said manufacturer has an obligation to make that clear to your customers and users.  But then, that's just me.  Anyway, this information gives me what I need to ask the right questions of tech support before purchasing.

I think most motherboards should support this.

I've also had it confirmed by nVidia that they support FLR on all current Quadro cards greater than or equal to Quadro 2000, on Tesla C2050 and higher and M2050 and higher, and on new VGX and GRID cards.

<snip>
From everything I've read, solutions that rely on any form of remote display protocols would be limited to a subset of Direct3D functions. Furthermore, these would vary from one implementation to another, thus making them far less attractive for gaming than VGA passthrough... Well, in my opinion anyway.

VirtualBox's seamless mode is pretty nifty. But it's a Type 2 Hypervisor and relies on paravirtualized drivers that also suffer from the same limitations as remote display protocols. It's great for most things, but gaming is not one of them. And I'm speaking from personal experience. Though I haven't used them myself, the same would seem to hold true of Parallel's and VMWare's 'Workstation' offerings. At least, as far as I've gathered.

FYI, the Type 1 Hypervisors from Parallel's and VMWare* are priced waaayyy outside my budget.

I understand that you want full 3D functionality for Windows gaming but maybe you'll find the subset of 3D functionality for the Linux machine acceptable. I have looked into VirtualGL and with TurboVNC, you might get a pretty decent desktop environment and it seems like most of the features are there already. It appears that the 3D is rendered by hardware/GPU before it is streamed through VNC or Spice. So it seems that you would need another GPU for that. You can find more info on VirtualGL here:

http://www.virtualgl.org/
Upon further investigation, the only option that is available to remotely translate Windows 3D apps is Microsoft's own RemoteFX.  In which case, Microsoft products would be the foundation of my software stack...  Something I'm trying to avoid.
I was just giving you the options I could think of OTOH that would let you share a Windows desktop with a Linux desktop, or rather share the desktop of one VM with the host machine.


Also the line between a type 1 and type 2 hypervisor tend to get a bit blurry. The point with type 1 is that it has access to ring-0 so that it can get access directly to the hardware to be passed through to the guests (I did confuse 'host' and 'guest' in my prior post). It also doesn't need to ask the host OS for permission in the same way as a type 2 hypervisor which is likely to give performance advantages in some cases.

However, even a type 2 hypervisor, although it is run as an application inside the OS can get "type 1" like privileges. By patching into the kernel and/or using special "dummy drivers" for hardware to be shared with VMs you can achieve pretty much the same thing, ergo it is no longer clear whether the hypervisor is a type 1 or type 2.

There is an article about it from the old IBM Mainframe days but I can't seem to find it.

You might be right, the performance of a Type 2 Hypervisor may be sufficient.  Regardless, I'd still have roughly the same hardware requirements as if I were going to use a Type 1 Hypervisor.  I'd still need the same CPU, RAM, GPU, and storage requirements as I've already put forth.  I could omit the potentially necessary additional components for use with a Type 1 Hypervisor.  Things like USB controller, NIC, or sound card.  But those costs would be replaced with the cost of licensing the Type2 Hypervisor.

In which case, I don't really gain or lose anything by experimenting with Type 1 Hypervisors...  At any rate, I could compare and contrast the performance of Type 1 and Type 2 Hypervisors using Paralles' and VMWare's trialware.  It might take a good long while, but it would be an adventure.

*I only found out about VMWare's 'free' vSphere after I'd written this response.

<snip>
Also, it is highly recommended that you use ECC RAM for such applications and it doesn't hurt to dedicate a few gigs of it to the ZFS as RAM is used for cache. The good news is that most motherboards with good chipsets support ECC RAM even though you might not find anything about it in the user manuals.
Again, thanks for the thorough explanation. This gives me a great deal to think about. The more I learn about ZFS, the less appealing it becomes. And by that I mean the confusion over which version of ZFS is in what OS? And just how well maintained the OSes supporting ZFS are? Now I have additional hardware considerations to keep in mind that may (or may not) make the cost of ZFS RAID-Z pool comparable to a hardware RAID5/6 solution anyway. Do you have any suggestions as to which of LSI HBAs I should be considering? I haven't found an HCL for ZFS in my searches.

Out of curiosity — and if you would happen to know — do you think what you suggest about the HBA and SAS drives for ZFS also applies to Btrfs? I'm assuming it would, but I'd appreciate some confirmation.

It's funny how the "I" in RAID never really seems to apply... Especially since it looks more and more like using ZFS or Btrfs will require I commit myself, from the start, to one or the other and a discrete HBA. Transitioning from an integrated SATA controller(s) and mdadm seems rather impractical. If I understand what's involved in doing so correctly. It may turn out that anything other than mdadm is price prohibitive.


I don't think you will have a problem with getting ZFS to run and if that's your only goal then you don't need to be very picky with your choice of hardware. I find ZFS pretty easy and handy to use. I has really great functionality and I don't have many bad things to say about it so far. ZFS is a filesystem (along with a couple of software tools to administrate it) just like EXT4 or NTFS so hardware support depends on the platform it runs on.

But the point with using ZFS is to get maximum protection against data corruption and that's where the selection of hardware gets limited and there are "best practices" set up to achieve that. I have not tested ZFS on any other platform than on OpenSolaris and OpenIndiana but I do know that it is well implemented on that platform and more mature there than on any other (non-solaris) platform. Another advantage with the OSOL/OI platform is that the CIFS functionality is implemented in the kernel space and not in the userland which will give advantages performance wise if you intend to share files with other windows computers. (I don't deny that Samba is pretty good on Linux too. There are some benchmarks on the phoronix website comparing samba with NFS and they are in favor of Samba on those benchmarks...) The second best implementation is found with FreeBSD and it is probably fairly mature but I haven't tested it myself and some people have run into problems with it in the past. The Linux version is probably merely at infancy stage and likely not yet mature enough for regular use. It is probably not as "bad" as btrfs though. There is quite a bit of information about it on the phoronix.com website (and probably also at lwn.net):

http://www.phoronix.com/scan.php?page=news_item&px=MTE4Nzc

My goal wasn't just to experiment with Btrfs, mdamd, or ZFS, if that's what you meant by, "with getting ZFS to run and if that's your only goal".  I actually intend to use it 'in production'.  In fact, the secondary role (Linux desktop being primary) for my proposed Virtualization rig is as file server (incl. httpd).  Windows gaming is a tertiary or quaternary concern for me.  So, finding out that the "best practices" for implementing ZFS include hardware I hadn't anticipated, is a bit off-putting.

The diversity in ZFS implementations is what I meant about being confused.  I'm not as familiar with the underlying platforms that utilize ZFS (other than Linux, and not with ZFS in use).  Without that familiarity, it makes it more difficult to gauge which of those platforms would suit my purposes.  For example, I had read a little bit about the degraded CIFS performance on FreeBSD and Linux due to their reliance on Samba (it residing in user-space being the issue).

BTW, I meant to ask how you came to the conclusion that ECC RAM is supported on desktop motherboards?  It's always been my understanding that you could use ECC RAM on such hardware, but there was no added benefit.
When I looked at the Gigabyte GA990FX motherboard there was no documentation about it anywhere, nor was it stated in the specifications. When I contacted customer support and asked about it, they sent me screen dumps of BIOS showing that it in fact does support ECC providing different ECC scrubbing options. So you can ask support if you are unsure.

The benefit of ECC is that there is a parity bit that checks the integrity of the data that is present in the RAM. We have cosmic radiation and bit flips do occur, also the memory can turn out to be faulty. It has been debated whether we really "need" this on a desktop. The finer litography of the hardware is likely to make it more sensitive to such failures and bit flips than before so it makes more sense to use ECC today than in the past.  If you are unlucky, you computer will crash because of that. Some files may get corrupted in the process. It may not happen very often but it does happen occasionally, hopefully, the bit flips happen in an address space that currently is not in use. If you run a server on the other hand then you are likely to run into freezes and crashes eventually (it may depend on how long uptimes were talking about). Using ECC RAM will prevent those crashes and add extra protection. In fact, Microsoft recommends ECC RAM even on desktop computers.

ZFS does offer protection against data corruption but if you are unlucky, some data corruption may go by undetected when written from RAM. ZFS (or any other filesystem) will write the damaged data to disk and be unable to automatically detect the corruption. This is why using ECC RAM with ZFS is "strongly recommended" in the best practices.

A search there on ZFS will give more articles. The latest official version of ZFS is 28 and is probably implemented in both Linux, and FreeBSD by now. Later versions have been released since Oracle killed the OpenSolaris project and can be found with the commercial closed-source Solaris platform that is supplied by Oracle. Things have happened since Oracle pulled the plug on OSOL project and leading developers behind the ZFS project such as Jeff Bonwick left Sun (after the acquisition by Oracle) and joined up with the Illumos team instead. So you cannot determine the stability of ZFS and ZPOOL merely by looking into the version number unfortunately and I wouldn't expect the FreeBSD implementation to be as stable as the Solaris implementation. It just takes time for the implementation to mature and the bugs to be weeded out and it just happens to have been around for Solaris/OpenSolaris/Illumos for much longer than the other platforms and the Solaris/Illumos version also happens to get first dibs on the features. Among the Illumos people there is an ambition to drop the version numbering altogether and instead talk about available features.

One of the two ZFS implementations on Linux has reached version 28, the other is at version 23 and seems to be abandoned or stagnant (last release was May 2011).  I'm not quite sure what the status of ZFS on FreeBSD is.  From this table on Wikipedia, ZFS is at version 28.  However the table notes that there is no CIFS or iSCSI support, which I'll try to independently confirm.  And, as you say, the fact that ZFS (and Solaris as a whole) has essentially been forked, with the re-consolidation of Solaris as closed-source, just adds to the confusion.  It's possible any given build of Illumos' version 28 of ZFS could have features or bug fixes no present in Oracle's version 33.
I don't know much about FreeBSD but in Solaris/Illumos the CIFS is implemented in the kernel space, in platforms such as Linux and BSD it is provided by the Samba framework in the userspace. If you want iSCSI then you have full support for it in Illumos based operating systems.

Also keep in mind that later version storage pools are not readable on systems with lower versions of zfs/zpool. zpool 28 is implemented in FreeBSD 9.0 and onwards. To my knowledge the ZFSonLinux project also has implemented zpool version 28.

It should be noted that people also have had problems with migrating a ZFS pool from one platform to another even though the version numbers matched.
The recommendation to use SAS hard drives is not so much about the quality of the hard drives themselves as it is about the SAS protocol. The SAS protocol simply handles SCSI transport commands in a better and more reliable manner than do SATA. I believe any decent SAS drive would do. As for HBAs I wrote a list with LSI based hardware a while ago here:

https://www.illumos.org/boards/1/topics/572

the thing is that a lot of OEMs such as IBM, HP, Cisco, Fujitsu-Siemens, Dell, ... supply their branded HBAs with LSI circuitry on them. What hardware to choose depends on what you're looking for. If you want an 8-port controller I would go for Intel SASUC8I or LSI SAS3801E-R. If you want SAS/SATA3 with 6.0 Gb/s then LSI's LSI SAS3801E-R series cards would be a better choice. I don't know what OEMs have come up with in the SATA3 department since I wrote that list but the chips to look for in that case are the LSI MegaRAID 2004/2008/2016e depending on how many ports you want.

If you want to read a further discussion about reliability of different RAID setups I made a post about this in the following thread (last post):

http://communities.intel.com/thread/25945

The cost of the drives is marginally higher than the drives I had budgeted, but including the cost of an SAS HBA is problematic.  I hadn't expected purchasing an HBA from the very start.  I'd hoped to deffer such a purchase for a bit, but you are saying that would be ill-advised.  How likely is it I would encounter problems using SATA drives in the interim?


The problem with "normal" hardware is that the error handling is internal. If a hard drive is starting to have bad sectors, the drive will handle them internally and reallocate the bad sectors. You will not notice anything and the errors will not be reported to the system. At most you will experience sluggish performance, perhaps a freeze. When things go so bad that errors are starting to become visible, then it is too late to do anything about it, the drive is already dead. In the past the drives would return "garbage", in the modern days the drive will reread the sector over and over again while trying to recalibrate the head which gives rise tio the characteristic click-of-death noise.

If you use a "cheap" HBA with say ZFS, the tools for monitoring the hardware such as iostat will be pretty much useless. Things will 'look' just fine with no errors and when errors start to show, they will happen out of the blue with no prior warning. The system drive of a ZFS file server that I run just crashed like that without warning. Prior to that, all I had on the drive were some corrupt blocks of the hard drive image of a virtual machine. It was connected to the Southbridge OnChip SATA controller of the motherboard. I didn't cry about it although there were some system files that I would have liked to keep though. I replaced it with a server grade SATA drive (WD RE4). I have suffered corruption on that drive on one of the virtual hard drive images. Since I don't see much sense in using RAID on the system drive (other people may beg to differ) I enabled the "ditto blocks" feature on that drive and recovered the image file using 'ddrescue'. The drive is doing fine ever since.

On the storage pool of that system I have already replaced two SATA drives on my SAS controller bacause they were going to die. What happened was that the server started to freeze but I couldn't tell what was the problem. Everything looked ok with iostat, was it a driver issue? I couldn't tell. Then eventually I started to see 'media errors' with iostat and when I replaced the drive the pool didn't freeze anymore. Then the same thing happened again and I replaced another hard drive like that. That's the reality of that, if the drives were SAS I would have been able to tell what's wrong at an earlier stage. There was a discussion about this about 6 months ago on the openindiana-discuss mailing list.

Have you seen any price/feature advantage to reseller versions of LSI OEM products?  I would think the offerings from Cisco, Dell, HP, and IBM would come at a premium as opposed to purchasing LSI branded hardware.  Anyway, I thought there might be specific models from particular manufacturers to meet the "best practices" for ZFS.  However, from your suggestions, I gather it really doesn't matter as long as the HBA is Intel or LSI?


That's something you have to look for at your dealers. My experience is that the OEM versions generally are cheaper than LSI branded products. You can compare yourself here:

Intel SASUC8I
http://amzn.to/QjtOR9

LSI 3081E-R
http://amzn.to/USps9x

Both are essentially the same card but the original LSI one is more expensive than the one from Intel.


I wonder, should we perhaps move the discussion of ZFS to private email?  It is a bit off-topic.

I think a better idea is to take this to the openindiana-discuss mailing list and/or the FreeNAS mailing lists/forums as other people with ZFS experience will read your posts. If you post on the openindiana-discuss I will read your post there as well.


_______________________________________________
Xen-users mailing list
Xen-users@lists.xen.org
http://lists.xen.org/xen-users

--------------000304020608000503070706-- --===============8613724340339552063== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users --===============8613724340339552063==-- From xen-users-bounces@lists.xen.org Fri Sep 28 18:10:27 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Fri, 28 Sep 2012 18:10:27 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1THf03-00033x-55; Fri, 28 Sep 2012 18:09:19 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1THf01-00033q-Ff for xen-users@lists.xen.org; Fri, 28 Sep 2012 18:09:17 +0000 Received: from [85.158.137.99:12268] by server-5.bemta-3.messagelabs.com id 14/CD-00589-CC7E5605; Fri, 28 Sep 2012 18:09:16 +0000 X-Env-Sender: ksanjabi@gmail.com X-Msg-Ref: server-9.tower-217.messagelabs.com!1348855752!16395057!1 X-Originating-IP: [209.85.220.173] X-SpamReason: No, hits=1.5 required=7.0 tests=HTML_00_10,HTML_MESSAGE, RCVD_BY_IP X-StarScan-Received: X-StarScan-Version: 6.6.1.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 29108 invoked from network); 28 Sep 2012 18:09:13 -0000 Received: from mail-vc0-f173.google.com (HELO mail-vc0-f173.google.com) (209.85.220.173) by server-9.tower-217.messagelabs.com with RC4-SHA encrypted SMTP; 28 Sep 2012 18:09:13 -0000 Received: by vcbfl15 with SMTP id fl15so4513217vcb.32 for ; Fri, 28 Sep 2012 11:09:12 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:reply-to:sender:date:x-google-sender-auth:message-id :subject:from:to:content-type; bh=GHoc5eJIcLV0RhHPgyWuLBJaOUaegwcMZuOXURM5/p4=; b=GGRTgpE0KRJNE2ZUsNiYM27yUTjrLaiCkr7ChoIZBi/VdEw3y9Xmc6f8UkrmJEW3k+ 5WafADKqOYKsKW30/B6r5nhgCJqWVo3vEyg46DQFSNnElEr9GWVGjyLJMW6me71zjkrS 63hSiBgFCvJpl41dECMZTH4ZgN1x109wqjfIrd3RlGPU/2O0o2pOHnkcbQ7GdX6LwyRD kHtmCSzbrFeUeRM5AqD97Hrl/PEmxflrgisbzr3HVeh0jEHjhYgXmLig1kYitIDOCA+e MxnI/WQlp8VZznez1b0uNgqhuWmNKFuBmfv3EP+P6efIFNHSLh7/6C0SJQl+vR7quiGC 9P6g== MIME-Version: 1.0 Received: by 10.221.11.82 with SMTP id pd18mr1039862vcb.38.1348855752135; Fri, 28 Sep 2012 11:09:12 -0700 (PDT) Received: by 10.220.70.71 with HTTP; Fri, 28 Sep 2012 11:09:12 -0700 (PDT) Date: Fri, 28 Sep 2012 11:09:12 -0700 X-Google-Sender-Auth: lKJWoRbkTMMXSp6MmvTdlF__t3E Message-ID: From: Karim Sanjabi To: xen-users@lists.xen.org Subject: [Xen-users] Xen linux and gaming box X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list Reply-To: karim@robotstampede.com List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============7488637328128456416==" Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org --===============7488637328128456416== Content-Type: multipart/alternative; boundary=bcaec54eed7af5936004cac6f334 --bcaec54eed7af5936004cac6f334 Content-Type: text/plain; charset=ISO-8859-1 My first post, so please let me know if this is the wrong place for this newbie stuff. Been reading Xen ideas, docs, post for a couple months and decided to give this a shot. Goal: Run any Ubuntu derivative off an intel i5 video card and play Windows 7 games on an Nvidia gtx 570 through vga pass through. Use a simple dvi toggle switch on the monitor (2 inputs) to go between them. Hardware: 16g ram, i5 (non K), vt-d ASRock motherboard, Intel ssd 120 gig, and lots of other slower drives. So my few questions are: 1) Is there any dis-advantage between Dom0 Mint/Ubuntu/Debian/Fedora ? Performance, stability? Was assuming to compile in the latest xen unstable for the best shot at nvidia support. 2) What is the best disk performance I can get with a windows 7 DomU? Pass a controller though or just share it with dom0 and maybe another domU. 3) Seems like the recommendation is to not have an GUI on Dom0. is there any reason for this? Ideally would like to run XFCE for Ubuntu. I don't understand the pros/cons of running XFCE on an ubuntu dom0 vs running it on a DomU 4) Is it required to pass through a usb bus with a 2nd keyboard/mouse or kvm switch? Or Can I just share the keyboard mouse? If I do need a kvm switch, will any of them work or is there an approved list (couldn't find any). Little unclear on how to switch between DomU instances (that what cntrl-] does?) 5) For allocating ram and cpu. How much do I need to leave for dom0? Guessing 2 cores for win 7, 2 cores for ubuntu, 8 gigs each may not work since I get the impression I must leave some resources for dom0. Can the dom0 and ubuntu domU be shared with say 2 cores 8 gigs? Thanks ahead of time. These answers have been very hard to find and understand. Karim --bcaec54eed7af5936004cac6f334 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable My first post, so please let me know if this is the wrong place for this ne= wbie stuff. Been reading Xen ideas, docs, post for a couple months and deci= ded to give this a shot.

Goal: Run any Ubuntu derivative off an intel i5 video card and play Windows= 7 games on an Nvidia gtx 570 through vga pass through.=A0 Use a simple dvi= toggle switch on the monitor (2 inputs) to go between them.

Hardwa= re: 16g ram, i5 (non K), vt-d ASRock motherboard, Intel ssd 120 gig, and lo= ts of other slower drives.

So my few questions are:

1) Is there any dis-advantage between D= om0 Mint/Ubuntu/Debian/Fedora ? Performance, stability? Was assuming to com= pile in the latest xen unstable for the best shot at nvidia support.

2) What is the best disk performance I can get with a windows 7 DomU? P= ass a controller though or just share it with dom0 and maybe another domU. =

3) Seems like the recommendation is to not have an GUI on Dom0.=A0 is t= here any reason for this? Ideally would like to run XFCE for Ubuntu. I don&= #39;t understand the pros/cons of running XFCE on an ubuntu dom0 vs running= it on a DomU

4) Is it required to pass through a usb bus with a 2nd keyboard/mouse o= r kvm switch? Or Can I just share the keyboard mouse?=A0 If I do need a kvm= switch, will any of them work or is there an approved list (couldn't f= ind any). Little unclear on how to switch between DomU instances (that what= cntrl-] does?)

5) For allocating ram and cpu. How much do I need to leave for dom0? Gu= essing 2 cores for win 7, 2 cores for ubuntu, 8 gigs each may not work sinc= e I get the impression I must leave some resources for dom0.=A0 Can the dom= 0 and ubuntu domU be shared with say 2 cores 8 gigs?

Thanks ahead of time. These answers have been very hard to find and und= erstand.

Karim




--bcaec54eed7af5936004cac6f334-- --===============7488637328128456416== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users --===============7488637328128456416==-- From xen-users-bounces@lists.xen.org Fri Sep 28 18:10:27 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Fri, 28 Sep 2012 18:10:27 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1THf03-00033x-55; Fri, 28 Sep 2012 18:09:19 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1THf01-00033q-Ff for xen-users@lists.xen.org; Fri, 28 Sep 2012 18:09:17 +0000 Received: from [85.158.137.99:12268] by server-5.bemta-3.messagelabs.com id 14/CD-00589-CC7E5605; Fri, 28 Sep 2012 18:09:16 +0000 X-Env-Sender: ksanjabi@gmail.com X-Msg-Ref: server-9.tower-217.messagelabs.com!1348855752!16395057!1 X-Originating-IP: [209.85.220.173] X-SpamReason: No, hits=1.5 required=7.0 tests=HTML_00_10,HTML_MESSAGE, RCVD_BY_IP X-StarScan-Received: X-StarScan-Version: 6.6.1.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 29108 invoked from network); 28 Sep 2012 18:09:13 -0000 Received: from mail-vc0-f173.google.com (HELO mail-vc0-f173.google.com) (209.85.220.173) by server-9.tower-217.messagelabs.com with RC4-SHA encrypted SMTP; 28 Sep 2012 18:09:13 -0000 Received: by vcbfl15 with SMTP id fl15so4513217vcb.32 for ; Fri, 28 Sep 2012 11:09:12 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:reply-to:sender:date:x-google-sender-auth:message-id :subject:from:to:content-type; bh=GHoc5eJIcLV0RhHPgyWuLBJaOUaegwcMZuOXURM5/p4=; b=GGRTgpE0KRJNE2ZUsNiYM27yUTjrLaiCkr7ChoIZBi/VdEw3y9Xmc6f8UkrmJEW3k+ 5WafADKqOYKsKW30/B6r5nhgCJqWVo3vEyg46DQFSNnElEr9GWVGjyLJMW6me71zjkrS 63hSiBgFCvJpl41dECMZTH4ZgN1x109wqjfIrd3RlGPU/2O0o2pOHnkcbQ7GdX6LwyRD kHtmCSzbrFeUeRM5AqD97Hrl/PEmxflrgisbzr3HVeh0jEHjhYgXmLig1kYitIDOCA+e MxnI/WQlp8VZznez1b0uNgqhuWmNKFuBmfv3EP+P6efIFNHSLh7/6C0SJQl+vR7quiGC 9P6g== MIME-Version: 1.0 Received: by 10.221.11.82 with SMTP id pd18mr1039862vcb.38.1348855752135; Fri, 28 Sep 2012 11:09:12 -0700 (PDT) Received: by 10.220.70.71 with HTTP; Fri, 28 Sep 2012 11:09:12 -0700 (PDT) Date: Fri, 28 Sep 2012 11:09:12 -0700 X-Google-Sender-Auth: lKJWoRbkTMMXSp6MmvTdlF__t3E Message-ID: From: Karim Sanjabi To: xen-users@lists.xen.org Subject: [Xen-users] Xen linux and gaming box X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list Reply-To: karim@robotstampede.com List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============7488637328128456416==" Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org --===============7488637328128456416== Content-Type: multipart/alternative; boundary=bcaec54eed7af5936004cac6f334 --bcaec54eed7af5936004cac6f334 Content-Type: text/plain; charset=ISO-8859-1 My first post, so please let me know if this is the wrong place for this newbie stuff. Been reading Xen ideas, docs, post for a couple months and decided to give this a shot. Goal: Run any Ubuntu derivative off an intel i5 video card and play Windows 7 games on an Nvidia gtx 570 through vga pass through. Use a simple dvi toggle switch on the monitor (2 inputs) to go between them. Hardware: 16g ram, i5 (non K), vt-d ASRock motherboard, Intel ssd 120 gig, and lots of other slower drives. So my few questions are: 1) Is there any dis-advantage between Dom0 Mint/Ubuntu/Debian/Fedora ? Performance, stability? Was assuming to compile in the latest xen unstable for the best shot at nvidia support. 2) What is the best disk performance I can get with a windows 7 DomU? Pass a controller though or just share it with dom0 and maybe another domU. 3) Seems like the recommendation is to not have an GUI on Dom0. is there any reason for this? Ideally would like to run XFCE for Ubuntu. I don't understand the pros/cons of running XFCE on an ubuntu dom0 vs running it on a DomU 4) Is it required to pass through a usb bus with a 2nd keyboard/mouse or kvm switch? Or Can I just share the keyboard mouse? If I do need a kvm switch, will any of them work or is there an approved list (couldn't find any). Little unclear on how to switch between DomU instances (that what cntrl-] does?) 5) For allocating ram and cpu. How much do I need to leave for dom0? Guessing 2 cores for win 7, 2 cores for ubuntu, 8 gigs each may not work since I get the impression I must leave some resources for dom0. Can the dom0 and ubuntu domU be shared with say 2 cores 8 gigs? Thanks ahead of time. These answers have been very hard to find and understand. Karim --bcaec54eed7af5936004cac6f334 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable My first post, so please let me know if this is the wrong place for this ne= wbie stuff. Been reading Xen ideas, docs, post for a couple months and deci= ded to give this a shot.

Goal: Run any Ubuntu derivative off an intel i5 video card and play Windows= 7 games on an Nvidia gtx 570 through vga pass through.=A0 Use a simple dvi= toggle switch on the monitor (2 inputs) to go between them.

Hardwa= re: 16g ram, i5 (non K), vt-d ASRock motherboard, Intel ssd 120 gig, and lo= ts of other slower drives.

So my few questions are:

1) Is there any dis-advantage between D= om0 Mint/Ubuntu/Debian/Fedora ? Performance, stability? Was assuming to com= pile in the latest xen unstable for the best shot at nvidia support.

2) What is the best disk performance I can get with a windows 7 DomU? P= ass a controller though or just share it with dom0 and maybe another domU. =

3) Seems like the recommendation is to not have an GUI on Dom0.=A0 is t= here any reason for this? Ideally would like to run XFCE for Ubuntu. I don&= #39;t understand the pros/cons of running XFCE on an ubuntu dom0 vs running= it on a DomU

4) Is it required to pass through a usb bus with a 2nd keyboard/mouse o= r kvm switch? Or Can I just share the keyboard mouse?=A0 If I do need a kvm= switch, will any of them work or is there an approved list (couldn't f= ind any). Little unclear on how to switch between DomU instances (that what= cntrl-] does?)

5) For allocating ram and cpu. How much do I need to leave for dom0? Gu= essing 2 cores for win 7, 2 cores for ubuntu, 8 gigs each may not work sinc= e I get the impression I must leave some resources for dom0.=A0 Can the dom= 0 and ubuntu domU be shared with say 2 cores 8 gigs?

Thanks ahead of time. These answers have been very hard to find and und= erstand.

Karim




--bcaec54eed7af5936004cac6f334-- --===============7488637328128456416== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users --===============7488637328128456416==-- From xen-users-bounces@lists.xen.org Fri Sep 28 18:49:27 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Fri, 28 Sep 2012 18:49:27 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1THfbr-0003Sx-Gz; Fri, 28 Sep 2012 18:48:23 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1THfbq-0003Sp-Lq for xen-users@lists.xen.org; Fri, 28 Sep 2012 18:48:23 +0000 Received: from [85.158.137.99:8902] by server-13.bemta-3.messagelabs.com id 7B/2E-11249-5F0F5605; Fri, 28 Sep 2012 18:48:21 +0000 X-Env-Sender: cdelorme@gmail.com X-Msg-Ref: server-4.tower-217.messagelabs.com!1348858099!19560636!1 X-Originating-IP: [209.85.214.173] X-SpamReason: No, hits=1.7 required=7.0 tests=BODY_RANDOM_LONG, HTML_20_30, HTML_MESSAGE, ML_RADAR_SPEW_LINKS_14, RCVD_BY_IP, spamassassin: X-StarScan-Received: X-StarScan-Version: 6.6.1.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 4486 invoked from network); 28 Sep 2012 18:48:20 -0000 Received: from mail-ob0-f173.google.com (HELO mail-ob0-f173.google.com) (209.85.214.173) by server-4.tower-217.messagelabs.com with RC4-SHA encrypted SMTP; 28 Sep 2012 18:48:20 -0000 Received: by obbwc18 with SMTP id wc18so1570740obb.32 for ; Fri, 28 Sep 2012 11:48:18 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=5fq1DLe7WddTZKH2oQfP2Zn8M8T5q8w9H2Z92h6Kqlw=; b=Nsr+dE+flwtkzaro1Cp13K+npgK6I3X8Bh5F8G63dwieuBpc5Ly2v7bjRWKqIngbGd 3zrWtBAw/zU3lTd1Xom+NoSswdkzai+KD3brr4akgiNNqhUP3SmREoIY3LZAdS5438LN jKINs3EBG07ZHoGC7UA73ovyFblW66ezxNRhBR6hpxScvU7tZ+9CcjH30ED8kaXCf+d2 j8Yv9PBdqTJoRQMtVmpSTkZfcq3T9ZDT5rK4CNlN4SS80+8vQGZnCUUHmTeZL16AgbZU ndBlpMQvaVz9nWeFvYesbs56E++s5giX9tujCjVJTVcRQCpY3VdgFEc8zEmzCfuAw/59 6v5w== MIME-Version: 1.0 Received: by 10.182.146.46 with SMTP id sz14mr6424809obb.76.1348858098101; Fri, 28 Sep 2012 11:48:18 -0700 (PDT) Received: by 10.76.19.148 with HTTP; Fri, 28 Sep 2012 11:48:17 -0700 (PDT) In-Reply-To: References: Date: Fri, 28 Sep 2012 14:48:17 -0400 Message-ID: From: Casey DeLorme To: karim@robotstampede.com Cc: xen-users@lists.xen.org Subject: Re: [Xen-users] Xen linux and gaming box X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============8610284479227214474==" Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org --===============8610284479227214474== Content-Type: multipart/alternative; boundary=f46d0444e92bca2c0f04cac77ff9 --f46d0444e92bca2c0f04cac77ff9 Content-Type: text/plain; charset=ISO-8859-1 On Fri, Sep 28, 2012 at 2:09 PM, Karim Sanjabi wrote: > My first post, so please let me know if this is the wrong place for this > newbie stuff. Been reading Xen ideas, docs, post for a couple months and > decided to give this a shot. > > Goal: Run any Ubuntu derivative off an intel i5 video card and play > Windows 7 games on an Nvidia gtx 570 through vga pass through. Use a > simple dvi toggle switch on the monitor (2 inputs) to go between them. > > Hardware: 16g ram, i5 (non K), vt-d ASRock motherboard, Intel ssd 120 gig, > and lots of other slower drives. > > So my few questions are: > > 1) Is there any dis-advantage between Dom0 Mint/Ubuntu/Debian/Fedora ? > Performance, stability? Was assuming to compile in the latest xen unstable > for the best shot at nvidia support. > > 1. Go with what you feel most comfortable with, which sounds like Ubuntu. I had successfully used Debian, tried Mint but didn't like it as much so I went back to Debian. The biggest disadvantage will be forcing yourself to configure an operating system you are not familiar with. 2) What is the best disk performance I can get with a windows 7 DomU? Pass > a controller though or just share it with dom0 and maybe another domU. > > 2. You said SSD for your host, are you planning to use LVM on the SSD or on a regular HDD? I use an OCZ Vertex 3 with LVM, and a logical volume for Windows. Windows Experience Index was 6.6, but after installing GPLPV drivers jumped to 7.7 and performs at near-native speeds. I would imagine similar results from HDD performance. 3) Seems like the recommendation is to not have an GUI on Dom0. is there > any reason for this? Ideally would like to run XFCE for Ubuntu. I don't > understand the pros/cons of running XFCE on an ubuntu dom0 vs running it on > a DomU > 3. Assuming best practices, you normally would install as little as possible on Dom0 and only use it as a control OS. However, as a home use I did just the opposite and use Gnome3 with Debian and Intel's on-die GPU. From what I read XFCE is a light-weight GUI, so that should probably work great. 4) Is it required to pass through a usb bus with a 2nd keyboard/mouse or > kvm switch? Or Can I just share the keyboard mouse? If I do need a kvm > switch, will any of them work or is there an approved list (couldn't find > any). Little unclear on how to switch between DomU instances (that what > cntrl-] does?) > 4. Supposedly you can pass individual USB devices, but they perform at USB 1.1 speeds. For best results and reliability, pass a controller. You could use VNC to pass input from Dom0 to DomU, but that'd probably be difficult. If by switching DomU instances you mean using the KVM to switch controls then that might work well with passed USB controllers. > 5) For allocating ram and cpu. How much do I need to leave for dom0? > Guessing 2 cores for win 7, 2 cores for ubuntu, 8 gigs each may not work > since I get the impression I must leave some resources for dom0. Can the > dom0 and ubuntu domU be shared with say 2 cores 8 gigs? > > 5. I will try to answer this, but someone else will probably have better or more accurate advice. Dom0 will take all the RAM by default, and assign as many vcores as available (eg. Core i7 Hyperthreading 4 cores, 8vcores, i5 will probably get 4 vcores). By default Xen uses ballooning which when you attempt to launch an HVM it will free up as much RAM as necessary from Dom0. I encountered problems with the speed at which it was able to free up RAM, and had to set a limit at boot time. I did not turn off ballooning because when Windows is not running Dom0 can ask for more RAM from Xen. I run Windows with 4 vcores, when I turn it on Dom0 still retains 8 vcores. I don't limit Dom0 vcores because as mentioned when I turn off Windows I use Dom0. The vcores are shared, and not subject to the same limitations as strict cpu assignment; I have never needed strict assignment for performance, so I would try 2 or 4 vcores and if that doesn't work maybe someone will give you a run through on strict cpu assignment. Thanks ahead of time. These answers have been very hard to find and > understand. > > Karim > > > > > > _______________________________________________ > Xen-users mailing list > Xen-users@lists.xen.org > http://lists.xen.org/xen-users > --f46d0444e92bca2c0f04cac77ff9 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable
On Fri, Sep 28, 2012 at 2:09 PM, Karim Sanjabi <<= a href=3D"mailto:karim@robotstampede.com" target=3D"_blank">karim@robotstam= pede.com> wrote:
My first post, so please let me know if this is the wrong place for this ne= wbie stuff. Been reading Xen ideas, docs, post for a couple months and deci= ded to give this a shot.

Goal: Run any Ubuntu derivative off an intel i5 video card and play Windows= 7 games on an Nvidia gtx 570 through vga pass through.=A0 Use a simple dvi= toggle switch on the monitor (2 inputs) to go between them.

Hardwa= re: 16g ram, i5 (non K), vt-d ASRock motherboard, Intel ssd 120 gig, and lo= ts of other slower drives.

So my few questions are:

1) Is there any dis-advantage between D= om0 Mint/Ubuntu/Debian/Fedora ? Performance, stability? Was assuming to com= pile in the latest xen unstable for the best shot at nvidia support.

1. Go with what you feel most comfortable with, which= sounds like Ubuntu. =A0I had successfully used Debian, tried Mint but didn= 't like it as much so I went back to Debian. =A0The biggest disadvantag= e will be forcing yourself to configure an operating system you are not fam= iliar with.

2) What is the best disk perf= ormance I can get with a windows 7 DomU? Pass a controller though or just s= hare it with dom0 and maybe another domU.

2. You said SSD for your host, are you planning to us= e LVM on the SSD or on a regular HDD? =A0I use an OCZ Vertex 3 with LVM, an= d a logical volume for Windows. =A0Windows Experience Index was 6.6, but af= ter installing GPLPV drivers jumped to 7.7 and performs at near-native spee= ds. =A0I would imagine similar results from HDD performance.=A0

3) Seems like the recommendat= ion is to not have an GUI on Dom0.=A0 is there any reason for this? Ideally= would like to run XFCE for Ubuntu. I don't understand the pros/cons of= running XFCE on an ubuntu dom0 vs running it on a DomU
3. Assuming best practices, you normally would install as= little as possible on Dom0 and only use it as a control OS. =A0However, as= a home use I did just the opposite and use Gnome3 with Debian and Intel= 9;s on-die GPU. =A0From what I read XFCE is a light-weight GUI, so that sho= uld probably work great.=A0

4) Is it required to pass thr= ough a usb bus with a 2nd keyboard/mouse or kvm switch? Or Can I just share= the keyboard mouse?=A0 If I do need a kvm switch, will any of them work or= is there an approved list (couldn't find any). Little unclear on how t= o switch between DomU instances (that what cntrl-] does?)
4. Supposedly you can pass individual USB devices, but th= ey perform at USB 1.1 speeds. =A0For best results and reliability, pass a c= ontroller. =A0You could use VNC to pass input from Dom0 to DomU, but that&#= 39;d probably be difficult. =A0If by switching DomU instances you mean usin= g the KVM to switch controls then that might work well with passed USB cont= rollers.=A0
=A0
5) For allocating ram and cpu.= How much do I need to leave for dom0? Guessing 2 cores for win 7, 2 cores = for ubuntu, 8 gigs each may not work since I get the impression I must leav= e some resources for dom0.=A0 Can the dom0 and ubuntu domU be shared with s= ay 2 cores 8 gigs?

5. I will try to answer this, but someone else will p= robably have better or more accurate advice.

Dom0 = will take all the RAM by default, and assign as many vcores as available (e= g. Core i7 Hyperthreading 4 cores, 8vcores, i5 will probably get 4 vcores).=

By default Xen uses ballooning which when you attempt t= o launch an HVM it will free up as much RAM as necessary from Dom0. =A0I en= countered problems with the speed at which it was able to free up RAM, and = had to set a limit at boot time. =A0I did not turn off ballooning because w= hen Windows is not running Dom0 can ask for more RAM from Xen.

I run Windows with 4 vcores, when I turn it on Dom0 sti= ll retains 8 vcores. =A0I don't limit Dom0 vcores because as mentioned = when I turn off Windows I use Dom0. =A0The vcores are shared, and not subje= ct to the same limitations as strict cpu assignment; I have never needed st= rict assignment for performance, so I would try 2 or 4 vcores and if that d= oesn't work maybe someone will give you a run through on strict cpu ass= ignment.

Thanks ahead of time. These a= nswers have been very hard to find and understand.

Karim





_______________________________________________
Xen-users mailing list
Xen-users@lists.xen.org
http://lists.x= en.org/xen-users

--f46d0444e92bca2c0f04cac77ff9-- --===============8610284479227214474== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users --===============8610284479227214474==-- From xen-users-bounces@lists.xen.org Fri Sep 28 18:49:27 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Fri, 28 Sep 2012 18:49:27 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1THfbr-0003Sx-Gz; Fri, 28 Sep 2012 18:48:23 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1THfbq-0003Sp-Lq for xen-users@lists.xen.org; Fri, 28 Sep 2012 18:48:23 +0000 Received: from [85.158.137.99:8902] by server-13.bemta-3.messagelabs.com id 7B/2E-11249-5F0F5605; Fri, 28 Sep 2012 18:48:21 +0000 X-Env-Sender: cdelorme@gmail.com X-Msg-Ref: server-4.tower-217.messagelabs.com!1348858099!19560636!1 X-Originating-IP: [209.85.214.173] X-SpamReason: No, hits=1.7 required=7.0 tests=BODY_RANDOM_LONG, HTML_20_30, HTML_MESSAGE, ML_RADAR_SPEW_LINKS_14, RCVD_BY_IP, spamassassin: X-StarScan-Received: X-StarScan-Version: 6.6.1.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 4486 invoked from network); 28 Sep 2012 18:48:20 -0000 Received: from mail-ob0-f173.google.com (HELO mail-ob0-f173.google.com) (209.85.214.173) by server-4.tower-217.messagelabs.com with RC4-SHA encrypted SMTP; 28 Sep 2012 18:48:20 -0000 Received: by obbwc18 with SMTP id wc18so1570740obb.32 for ; Fri, 28 Sep 2012 11:48:18 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=5fq1DLe7WddTZKH2oQfP2Zn8M8T5q8w9H2Z92h6Kqlw=; b=Nsr+dE+flwtkzaro1Cp13K+npgK6I3X8Bh5F8G63dwieuBpc5Ly2v7bjRWKqIngbGd 3zrWtBAw/zU3lTd1Xom+NoSswdkzai+KD3brr4akgiNNqhUP3SmREoIY3LZAdS5438LN jKINs3EBG07ZHoGC7UA73ovyFblW66ezxNRhBR6hpxScvU7tZ+9CcjH30ED8kaXCf+d2 j8Yv9PBdqTJoRQMtVmpSTkZfcq3T9ZDT5rK4CNlN4SS80+8vQGZnCUUHmTeZL16AgbZU ndBlpMQvaVz9nWeFvYesbs56E++s5giX9tujCjVJTVcRQCpY3VdgFEc8zEmzCfuAw/59 6v5w== MIME-Version: 1.0 Received: by 10.182.146.46 with SMTP id sz14mr6424809obb.76.1348858098101; Fri, 28 Sep 2012 11:48:18 -0700 (PDT) Received: by 10.76.19.148 with HTTP; Fri, 28 Sep 2012 11:48:17 -0700 (PDT) In-Reply-To: References: Date: Fri, 28 Sep 2012 14:48:17 -0400 Message-ID: From: Casey DeLorme To: karim@robotstampede.com Cc: xen-users@lists.xen.org Subject: Re: [Xen-users] Xen linux and gaming box X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============8610284479227214474==" Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org --===============8610284479227214474== Content-Type: multipart/alternative; boundary=f46d0444e92bca2c0f04cac77ff9 --f46d0444e92bca2c0f04cac77ff9 Content-Type: text/plain; charset=ISO-8859-1 On Fri, Sep 28, 2012 at 2:09 PM, Karim Sanjabi wrote: > My first post, so please let me know if this is the wrong place for this > newbie stuff. Been reading Xen ideas, docs, post for a couple months and > decided to give this a shot. > > Goal: Run any Ubuntu derivative off an intel i5 video card and play > Windows 7 games on an Nvidia gtx 570 through vga pass through. Use a > simple dvi toggle switch on the monitor (2 inputs) to go between them. > > Hardware: 16g ram, i5 (non K), vt-d ASRock motherboard, Intel ssd 120 gig, > and lots of other slower drives. > > So my few questions are: > > 1) Is there any dis-advantage between Dom0 Mint/Ubuntu/Debian/Fedora ? > Performance, stability? Was assuming to compile in the latest xen unstable > for the best shot at nvidia support. > > 1. Go with what you feel most comfortable with, which sounds like Ubuntu. I had successfully used Debian, tried Mint but didn't like it as much so I went back to Debian. The biggest disadvantage will be forcing yourself to configure an operating system you are not familiar with. 2) What is the best disk performance I can get with a windows 7 DomU? Pass > a controller though or just share it with dom0 and maybe another domU. > > 2. You said SSD for your host, are you planning to use LVM on the SSD or on a regular HDD? I use an OCZ Vertex 3 with LVM, and a logical volume for Windows. Windows Experience Index was 6.6, but after installing GPLPV drivers jumped to 7.7 and performs at near-native speeds. I would imagine similar results from HDD performance. 3) Seems like the recommendation is to not have an GUI on Dom0. is there > any reason for this? Ideally would like to run XFCE for Ubuntu. I don't > understand the pros/cons of running XFCE on an ubuntu dom0 vs running it on > a DomU > 3. Assuming best practices, you normally would install as little as possible on Dom0 and only use it as a control OS. However, as a home use I did just the opposite and use Gnome3 with Debian and Intel's on-die GPU. From what I read XFCE is a light-weight GUI, so that should probably work great. 4) Is it required to pass through a usb bus with a 2nd keyboard/mouse or > kvm switch? Or Can I just share the keyboard mouse? If I do need a kvm > switch, will any of them work or is there an approved list (couldn't find > any). Little unclear on how to switch between DomU instances (that what > cntrl-] does?) > 4. Supposedly you can pass individual USB devices, but they perform at USB 1.1 speeds. For best results and reliability, pass a controller. You could use VNC to pass input from Dom0 to DomU, but that'd probably be difficult. If by switching DomU instances you mean using the KVM to switch controls then that might work well with passed USB controllers. > 5) For allocating ram and cpu. How much do I need to leave for dom0? > Guessing 2 cores for win 7, 2 cores for ubuntu, 8 gigs each may not work > since I get the impression I must leave some resources for dom0. Can the > dom0 and ubuntu domU be shared with say 2 cores 8 gigs? > > 5. I will try to answer this, but someone else will probably have better or more accurate advice. Dom0 will take all the RAM by default, and assign as many vcores as available (eg. Core i7 Hyperthreading 4 cores, 8vcores, i5 will probably get 4 vcores). By default Xen uses ballooning which when you attempt to launch an HVM it will free up as much RAM as necessary from Dom0. I encountered problems with the speed at which it was able to free up RAM, and had to set a limit at boot time. I did not turn off ballooning because when Windows is not running Dom0 can ask for more RAM from Xen. I run Windows with 4 vcores, when I turn it on Dom0 still retains 8 vcores. I don't limit Dom0 vcores because as mentioned when I turn off Windows I use Dom0. The vcores are shared, and not subject to the same limitations as strict cpu assignment; I have never needed strict assignment for performance, so I would try 2 or 4 vcores and if that doesn't work maybe someone will give you a run through on strict cpu assignment. Thanks ahead of time. These answers have been very hard to find and > understand. > > Karim > > > > > > _______________________________________________ > Xen-users mailing list > Xen-users@lists.xen.org > http://lists.xen.org/xen-users > --f46d0444e92bca2c0f04cac77ff9 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable
On Fri, Sep 28, 2012 at 2:09 PM, Karim Sanjabi <<= a href=3D"mailto:karim@robotstampede.com" target=3D"_blank">karim@robotstam= pede.com> wrote:
My first post, so please let me know if this is the wrong place for this ne= wbie stuff. Been reading Xen ideas, docs, post for a couple months and deci= ded to give this a shot.

Goal: Run any Ubuntu derivative off an intel i5 video card and play Windows= 7 games on an Nvidia gtx 570 through vga pass through.=A0 Use a simple dvi= toggle switch on the monitor (2 inputs) to go between them.

Hardwa= re: 16g ram, i5 (non K), vt-d ASRock motherboard, Intel ssd 120 gig, and lo= ts of other slower drives.

So my few questions are:

1) Is there any dis-advantage between D= om0 Mint/Ubuntu/Debian/Fedora ? Performance, stability? Was assuming to com= pile in the latest xen unstable for the best shot at nvidia support.

1. Go with what you feel most comfortable with, which= sounds like Ubuntu. =A0I had successfully used Debian, tried Mint but didn= 't like it as much so I went back to Debian. =A0The biggest disadvantag= e will be forcing yourself to configure an operating system you are not fam= iliar with.

2) What is the best disk perf= ormance I can get with a windows 7 DomU? Pass a controller though or just s= hare it with dom0 and maybe another domU.

2. You said SSD for your host, are you planning to us= e LVM on the SSD or on a regular HDD? =A0I use an OCZ Vertex 3 with LVM, an= d a logical volume for Windows. =A0Windows Experience Index was 6.6, but af= ter installing GPLPV drivers jumped to 7.7 and performs at near-native spee= ds. =A0I would imagine similar results from HDD performance.=A0

3) Seems like the recommendat= ion is to not have an GUI on Dom0.=A0 is there any reason for this? Ideally= would like to run XFCE for Ubuntu. I don't understand the pros/cons of= running XFCE on an ubuntu dom0 vs running it on a DomU
3. Assuming best practices, you normally would install as= little as possible on Dom0 and only use it as a control OS. =A0However, as= a home use I did just the opposite and use Gnome3 with Debian and Intel= 9;s on-die GPU. =A0From what I read XFCE is a light-weight GUI, so that sho= uld probably work great.=A0

4) Is it required to pass thr= ough a usb bus with a 2nd keyboard/mouse or kvm switch? Or Can I just share= the keyboard mouse?=A0 If I do need a kvm switch, will any of them work or= is there an approved list (couldn't find any). Little unclear on how t= o switch between DomU instances (that what cntrl-] does?)
4. Supposedly you can pass individual USB devices, but th= ey perform at USB 1.1 speeds. =A0For best results and reliability, pass a c= ontroller. =A0You could use VNC to pass input from Dom0 to DomU, but that&#= 39;d probably be difficult. =A0If by switching DomU instances you mean usin= g the KVM to switch controls then that might work well with passed USB cont= rollers.=A0
=A0
5) For allocating ram and cpu.= How much do I need to leave for dom0? Guessing 2 cores for win 7, 2 cores = for ubuntu, 8 gigs each may not work since I get the impression I must leav= e some resources for dom0.=A0 Can the dom0 and ubuntu domU be shared with s= ay 2 cores 8 gigs?

5. I will try to answer this, but someone else will p= robably have better or more accurate advice.

Dom0 = will take all the RAM by default, and assign as many vcores as available (e= g. Core i7 Hyperthreading 4 cores, 8vcores, i5 will probably get 4 vcores).=

By default Xen uses ballooning which when you attempt t= o launch an HVM it will free up as much RAM as necessary from Dom0. =A0I en= countered problems with the speed at which it was able to free up RAM, and = had to set a limit at boot time. =A0I did not turn off ballooning because w= hen Windows is not running Dom0 can ask for more RAM from Xen.

I run Windows with 4 vcores, when I turn it on Dom0 sti= ll retains 8 vcores. =A0I don't limit Dom0 vcores because as mentioned = when I turn off Windows I use Dom0. =A0The vcores are shared, and not subje= ct to the same limitations as strict cpu assignment; I have never needed st= rict assignment for performance, so I would try 2 or 4 vcores and if that d= oesn't work maybe someone will give you a run through on strict cpu ass= ignment.

Thanks ahead of time. These a= nswers have been very hard to find and understand.

Karim





_______________________________________________
Xen-users mailing list
Xen-users@lists.xen.org
http://lists.x= en.org/xen-users

--f46d0444e92bca2c0f04cac77ff9-- --===============8610284479227214474== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users --===============8610284479227214474==-- From xen-users-bounces@lists.xen.org Sat Sep 29 01:49:09 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Sat, 29 Sep 2012 01:49:09 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1THm9Y-0001Wa-UJ; Sat, 29 Sep 2012 01:47:36 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1THm9X-0001WV-51 for xen-users@lists.xen.org; Sat, 29 Sep 2012 01:47:35 +0000 Received: from [85.158.138.51:48466] by server-12.bemta-3.messagelabs.com id FF/03-23730-63356605; Sat, 29 Sep 2012 01:47:34 +0000 X-Env-Sender: james.harper@bendigoit.com.au X-Msg-Ref: server-12.tower-174.messagelabs.com!1348883250!24481019!1 X-Originating-IP: [203.16.207.99] X-SpamReason: No, hits=0.0 required=7.0 tests= X-StarScan-Received: X-StarScan-Version: 6.6.1.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 28351 invoked from network); 29 Sep 2012 01:47:33 -0000 Received: from mail.bendigoit.com.au (HELO smtp2.bendigoit.com.au) (203.16.207.99) by server-12.tower-174.messagelabs.com with AES256-SHA encrypted SMTP; 29 Sep 2012 01:47:33 -0000 Received: from [2001:388:e000:712:a5ca:4fd3:14f:ad5d] (helo=BITCOM1.int.sbss.com.au) by smtp2.bendigoit.com.au with esmtp (Exim 4.72) (envelope-from ) id 1THm9L-0002Bl-5b; Sat, 29 Sep 2012 11:47:23 +1000 Received: from BITCOM1.int.sbss.com.au ([fe80::a5ca:4fd3:14f:ad5d]) by BITCOM1.int.sbss.com.au ([fe80::a5ca:4fd3:14f:ad5d%12]) with mapi id 14.01.0379.000; Sat, 29 Sep 2012 11:47:11 +1000 From: James Harper To: Casey DeLorme , "karim@robotstampede.com" Thread-Topic: [Xen-users] Xen linux and gaming box Thread-Index: AQHNnaSgDXOblOlTvkqBGt3hlmO8pJefcLiAgAEaZTA= Date: Sat, 29 Sep 2012 01:47:10 +0000 Message-ID: <6035A0D088A63A46850C3988ED045A4B2EAB3A10@BITCOM1.int.sbss.com.au> References: In-Reply-To: Accept-Language: en-AU, en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [172.16.3.132] x-tm-as-product-ver: SMEX-10.2.0.2087-7.000.1014-19220.000 x-tm-as-result: No--21.464200-0.000000-31 x-tm-as-user-approved-sender: Yes x-tm-as-user-blocked-sender: No MIME-Version: 1.0 X-Really-From-Bendigo-IT: magichashvalue Cc: "xen-users@lists.xen.org" Subject: Re: [Xen-users] Xen linux and gaming box X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org > 2) What is the best disk performance I can get with a windows 7 > DomU? Pass a controller though or just share it with dom0 and maybe > another domU. > > 2. You said SSD for your host, are you planning to use LVM on the SSD or on a > regular HDD? I use an OCZ Vertex 3 with LVM, and a logical volume for > Windows. Windows Experience Index was 6.6, but after installing GPLPV > drivers jumped to 7.7 and performs at near-native speeds. I would imagine > similar results from HDD performance. > GPLPV doesn't (yet?) support trim/unmap/discard (http://en.wikipedia.org/wiki/TRIM) so write performance on SSD may not be as good as it could be. I'm not sure of the exact impact in terms of overall performance though. The Wikipedia article says that modern SSD's still perform well without TRIM but their lifespan may be reduced. James _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Sat Sep 29 01:49:09 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Sat, 29 Sep 2012 01:49:09 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1THm9Y-0001Wa-UJ; Sat, 29 Sep 2012 01:47:36 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1THm9X-0001WV-51 for xen-users@lists.xen.org; Sat, 29 Sep 2012 01:47:35 +0000 Received: from [85.158.138.51:48466] by server-12.bemta-3.messagelabs.com id FF/03-23730-63356605; Sat, 29 Sep 2012 01:47:34 +0000 X-Env-Sender: james.harper@bendigoit.com.au X-Msg-Ref: server-12.tower-174.messagelabs.com!1348883250!24481019!1 X-Originating-IP: [203.16.207.99] X-SpamReason: No, hits=0.0 required=7.0 tests= X-StarScan-Received: X-StarScan-Version: 6.6.1.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 28351 invoked from network); 29 Sep 2012 01:47:33 -0000 Received: from mail.bendigoit.com.au (HELO smtp2.bendigoit.com.au) (203.16.207.99) by server-12.tower-174.messagelabs.com with AES256-SHA encrypted SMTP; 29 Sep 2012 01:47:33 -0000 Received: from [2001:388:e000:712:a5ca:4fd3:14f:ad5d] (helo=BITCOM1.int.sbss.com.au) by smtp2.bendigoit.com.au with esmtp (Exim 4.72) (envelope-from ) id 1THm9L-0002Bl-5b; Sat, 29 Sep 2012 11:47:23 +1000 Received: from BITCOM1.int.sbss.com.au ([fe80::a5ca:4fd3:14f:ad5d]) by BITCOM1.int.sbss.com.au ([fe80::a5ca:4fd3:14f:ad5d%12]) with mapi id 14.01.0379.000; Sat, 29 Sep 2012 11:47:11 +1000 From: James Harper To: Casey DeLorme , "karim@robotstampede.com" Thread-Topic: [Xen-users] Xen linux and gaming box Thread-Index: AQHNnaSgDXOblOlTvkqBGt3hlmO8pJefcLiAgAEaZTA= Date: Sat, 29 Sep 2012 01:47:10 +0000 Message-ID: <6035A0D088A63A46850C3988ED045A4B2EAB3A10@BITCOM1.int.sbss.com.au> References: In-Reply-To: Accept-Language: en-AU, en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [172.16.3.132] x-tm-as-product-ver: SMEX-10.2.0.2087-7.000.1014-19220.000 x-tm-as-result: No--21.464200-0.000000-31 x-tm-as-user-approved-sender: Yes x-tm-as-user-blocked-sender: No MIME-Version: 1.0 X-Really-From-Bendigo-IT: magichashvalue Cc: "xen-users@lists.xen.org" Subject: Re: [Xen-users] Xen linux and gaming box X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org > 2) What is the best disk performance I can get with a windows 7 > DomU? Pass a controller though or just share it with dom0 and maybe > another domU. > > 2. You said SSD for your host, are you planning to use LVM on the SSD or on a > regular HDD? I use an OCZ Vertex 3 with LVM, and a logical volume for > Windows. Windows Experience Index was 6.6, but after installing GPLPV > drivers jumped to 7.7 and performs at near-native speeds. I would imagine > similar results from HDD performance. > GPLPV doesn't (yet?) support trim/unmap/discard (http://en.wikipedia.org/wiki/TRIM) so write performance on SSD may not be as good as it could be. I'm not sure of the exact impact in terms of overall performance though. The Wikipedia article says that modern SSD's still perform well without TRIM but their lifespan may be reduced. James _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Sat Sep 29 02:45:44 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Sat, 29 Sep 2012 02:45:44 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1THn2Y-0002Gr-QZ; Sat, 29 Sep 2012 02:44:26 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1THn2X-0002Gm-CT for xen-users@lists.xen.org; Sat, 29 Sep 2012 02:44:25 +0000 Received: from [85.158.139.211:16862] by server-7.bemta-5.messagelabs.com id C2/BF-00431-88066605; Sat, 29 Sep 2012 02:44:24 +0000 X-Env-Sender: cdelorme@gmail.com X-Msg-Ref: server-13.tower-206.messagelabs.com!1348886662!16417678!1 X-Originating-IP: [209.85.219.45] X-SpamReason: No, hits=0.4 required=7.0 tests=HTML_30_40,HTML_MESSAGE, ML_RADAR_SPEW_LINKS_14,RCVD_BY_IP,spamassassin: X-StarScan-Received: X-StarScan-Version: 6.6.1.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 22502 invoked from network); 29 Sep 2012 02:44:23 -0000 Received: from mail-oa0-f45.google.com (HELO mail-oa0-f45.google.com) (209.85.219.45) by server-13.tower-206.messagelabs.com with RC4-SHA encrypted SMTP; 29 Sep 2012 02:44:23 -0000 Received: by oagi18 with SMTP id i18so4808911oag.32 for ; Fri, 28 Sep 2012 19:44:22 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=z2H2Pv8beJy3SF55sxF53JF+M7X6k9tqiNHxlAbSJOU=; b=flSv9D2pvyw9deo7IDWDBT+Ilp/ANBqC4rRezH7VMYjpBXq5S9Vl0PNVAFwwYOkLfd ULkhrX3gpOEWzSLit2GfqcaApkcBNZx6uZsWNTvzGF0s4dI3Uq0JJjCGhbLYfe4kMPMZ 6jHjLQfq/pK2o2kcZxOcpsFvcpB9Pb8Pkrq+JYCKxlfTHUP2TIVcnOyzTO679/KuXQ6i Urw+Ql2L9MVRFpmB6V6knQ01gE2Vs04dlxP0Iz+rk5BEnqbvItOzCPbqJgcMSbUodlfO gsqtbfWCIhwkZsCLAw8kztdsZ8OomyF3cNyoZmAV4Rhy7nsb24Ac5fRIuV+y28PrcNZ8 Hdmg== MIME-Version: 1.0 Received: by 10.60.172.235 with SMTP id bf11mr7028143oec.30.1348886661953; Fri, 28 Sep 2012 19:44:21 -0700 (PDT) Received: by 10.76.19.148 with HTTP; Fri, 28 Sep 2012 19:44:21 -0700 (PDT) In-Reply-To: <6035A0D088A63A46850C3988ED045A4B2EAB3A10@BITCOM1.int.sbss.com.au> References: <6035A0D088A63A46850C3988ED045A4B2EAB3A10@BITCOM1.int.sbss.com.au> Date: Fri, 28 Sep 2012 22:44:21 -0400 Message-ID: From: Casey DeLorme To: James Harper Cc: "xen-users@lists.xen.org" , "karim@robotstampede.com" Subject: Re: [Xen-users] Xen linux and gaming box X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============5475259960107087510==" Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org --===============5475259960107087510== Content-Type: multipart/alternative; boundary=bcaec54ee83853f88404cace260b --bcaec54ee83853f88404cace260b Content-Type: text/plain; charset=ISO-8859-1 Windows recognizes the drive as an SSD, since it turned off defrag automatically for just that drive. I don't know if GPLPV has anything to do with it, if it turned off defrag maybe it's Windows/NTFS taking care of TRIM? There are a lot of factors involved, remember it is running on a Logical Volume partition which is handled by LVM, so it's not all about the drivers. On Fri, Sep 28, 2012 at 9:47 PM, James Harper wrote: > > 2) What is the best disk performance I can get with a windows 7 > > DomU? Pass a controller though or just share it with dom0 and maybe > > another domU. > > > > 2. You said SSD for your host, are you planning to use LVM on the SSD or > on a > > regular HDD? I use an OCZ Vertex 3 with LVM, and a logical volume for > > Windows. Windows Experience Index was 6.6, but after installing GPLPV > > drivers jumped to 7.7 and performs at near-native speeds. I would > imagine > > similar results from HDD performance. > > > > GPLPV doesn't (yet?) support trim/unmap/discard ( > http://en.wikipedia.org/wiki/TRIM) so write performance on SSD may not be > as good as it could be. I'm not sure of the exact impact in terms of > overall performance though. The Wikipedia article says that modern SSD's > still perform well without TRIM but their lifespan may be reduced. > > James > > --bcaec54ee83853f88404cace260b Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Windows recognizes the drive as an SSD, since it turned off defrag automati= cally for just that drive. =A0I don't know if GPLPV has anything to do = with it, if it turned off defrag maybe it's Windows/NTFS taking care of= TRIM?

There are a lot of factors involved, remember it is running = on a Logical Volume partition which is handled by LVM, so it's not all = about the drivers.

On Fri= , Sep 28, 2012 at 9:47 PM, James Harper <james.harper@bendigoi= t.com.au> wrote:
> =A0 =A0 =A0 2) What i= s the best disk performance I can get with a windows 7
> DomU? Pass a controller though or just share it with dom0 and maybe > another domU.
>
> 2. You said SSD for your host, are you planning to use LVM on the SSD = or on a
> regular HDD? =A0I use an OCZ Vertex 3 with LVM, and a logical volume f= or
> Windows. =A0Windows Experience Index was 6.6, but after installing GPL= PV
> drivers jumped to 7.7 and performs at near-native speeds. =A0I would i= magine
> similar results from HDD performance.
>

GPLPV doesn't (yet?) support trim/unmap/discard (http://en.wikipedia.org/wik= i/TRIM) so write performance on SSD may not be as good as it could be. = =A0I'm not sure of the exact impact in terms of overall performance tho= ugh. The Wikipedia article says that modern SSD's still perform well wi= thout TRIM but their lifespan may be reduced.

James


--bcaec54ee83853f88404cace260b-- --===============5475259960107087510== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users --===============5475259960107087510==-- From xen-users-bounces@lists.xen.org Sat Sep 29 02:45:44 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Sat, 29 Sep 2012 02:45:44 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1THn2Y-0002Gr-QZ; Sat, 29 Sep 2012 02:44:26 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1THn2X-0002Gm-CT for xen-users@lists.xen.org; Sat, 29 Sep 2012 02:44:25 +0000 Received: from [85.158.139.211:16862] by server-7.bemta-5.messagelabs.com id C2/BF-00431-88066605; Sat, 29 Sep 2012 02:44:24 +0000 X-Env-Sender: cdelorme@gmail.com X-Msg-Ref: server-13.tower-206.messagelabs.com!1348886662!16417678!1 X-Originating-IP: [209.85.219.45] X-SpamReason: No, hits=0.4 required=7.0 tests=HTML_30_40,HTML_MESSAGE, ML_RADAR_SPEW_LINKS_14,RCVD_BY_IP,spamassassin: X-StarScan-Received: X-StarScan-Version: 6.6.1.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 22502 invoked from network); 29 Sep 2012 02:44:23 -0000 Received: from mail-oa0-f45.google.com (HELO mail-oa0-f45.google.com) (209.85.219.45) by server-13.tower-206.messagelabs.com with RC4-SHA encrypted SMTP; 29 Sep 2012 02:44:23 -0000 Received: by oagi18 with SMTP id i18so4808911oag.32 for ; Fri, 28 Sep 2012 19:44:22 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=z2H2Pv8beJy3SF55sxF53JF+M7X6k9tqiNHxlAbSJOU=; b=flSv9D2pvyw9deo7IDWDBT+Ilp/ANBqC4rRezH7VMYjpBXq5S9Vl0PNVAFwwYOkLfd ULkhrX3gpOEWzSLit2GfqcaApkcBNZx6uZsWNTvzGF0s4dI3Uq0JJjCGhbLYfe4kMPMZ 6jHjLQfq/pK2o2kcZxOcpsFvcpB9Pb8Pkrq+JYCKxlfTHUP2TIVcnOyzTO679/KuXQ6i Urw+Ql2L9MVRFpmB6V6knQ01gE2Vs04dlxP0Iz+rk5BEnqbvItOzCPbqJgcMSbUodlfO gsqtbfWCIhwkZsCLAw8kztdsZ8OomyF3cNyoZmAV4Rhy7nsb24Ac5fRIuV+y28PrcNZ8 Hdmg== MIME-Version: 1.0 Received: by 10.60.172.235 with SMTP id bf11mr7028143oec.30.1348886661953; Fri, 28 Sep 2012 19:44:21 -0700 (PDT) Received: by 10.76.19.148 with HTTP; Fri, 28 Sep 2012 19:44:21 -0700 (PDT) In-Reply-To: <6035A0D088A63A46850C3988ED045A4B2EAB3A10@BITCOM1.int.sbss.com.au> References: <6035A0D088A63A46850C3988ED045A4B2EAB3A10@BITCOM1.int.sbss.com.au> Date: Fri, 28 Sep 2012 22:44:21 -0400 Message-ID: From: Casey DeLorme To: James Harper Cc: "xen-users@lists.xen.org" , "karim@robotstampede.com" Subject: Re: [Xen-users] Xen linux and gaming box X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============5475259960107087510==" Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org --===============5475259960107087510== Content-Type: multipart/alternative; boundary=bcaec54ee83853f88404cace260b --bcaec54ee83853f88404cace260b Content-Type: text/plain; charset=ISO-8859-1 Windows recognizes the drive as an SSD, since it turned off defrag automatically for just that drive. I don't know if GPLPV has anything to do with it, if it turned off defrag maybe it's Windows/NTFS taking care of TRIM? There are a lot of factors involved, remember it is running on a Logical Volume partition which is handled by LVM, so it's not all about the drivers. On Fri, Sep 28, 2012 at 9:47 PM, James Harper wrote: > > 2) What is the best disk performance I can get with a windows 7 > > DomU? Pass a controller though or just share it with dom0 and maybe > > another domU. > > > > 2. You said SSD for your host, are you planning to use LVM on the SSD or > on a > > regular HDD? I use an OCZ Vertex 3 with LVM, and a logical volume for > > Windows. Windows Experience Index was 6.6, but after installing GPLPV > > drivers jumped to 7.7 and performs at near-native speeds. I would > imagine > > similar results from HDD performance. > > > > GPLPV doesn't (yet?) support trim/unmap/discard ( > http://en.wikipedia.org/wiki/TRIM) so write performance on SSD may not be > as good as it could be. I'm not sure of the exact impact in terms of > overall performance though. The Wikipedia article says that modern SSD's > still perform well without TRIM but their lifespan may be reduced. > > James > > --bcaec54ee83853f88404cace260b Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Windows recognizes the drive as an SSD, since it turned off defrag automati= cally for just that drive. =A0I don't know if GPLPV has anything to do = with it, if it turned off defrag maybe it's Windows/NTFS taking care of= TRIM?

There are a lot of factors involved, remember it is running = on a Logical Volume partition which is handled by LVM, so it's not all = about the drivers.

On Fri= , Sep 28, 2012 at 9:47 PM, James Harper <james.harper@bendigoi= t.com.au> wrote:
> =A0 =A0 =A0 2) What i= s the best disk performance I can get with a windows 7
> DomU? Pass a controller though or just share it with dom0 and maybe > another domU.
>
> 2. You said SSD for your host, are you planning to use LVM on the SSD = or on a
> regular HDD? =A0I use an OCZ Vertex 3 with LVM, and a logical volume f= or
> Windows. =A0Windows Experience Index was 6.6, but after installing GPL= PV
> drivers jumped to 7.7 and performs at near-native speeds. =A0I would i= magine
> similar results from HDD performance.
>

GPLPV doesn't (yet?) support trim/unmap/discard (http://en.wikipedia.org/wik= i/TRIM) so write performance on SSD may not be as good as it could be. = =A0I'm not sure of the exact impact in terms of overall performance tho= ugh. The Wikipedia article says that modern SSD's still perform well wi= thout TRIM but their lifespan may be reduced.

James


--bcaec54ee83853f88404cace260b-- --===============5475259960107087510== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users --===============5475259960107087510==-- From xen-users-bounces@lists.xen.org Sat Sep 29 04:40:29 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Sat, 29 Sep 2012 04:40:29 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1THopZ-00038K-GA; Sat, 29 Sep 2012 04:39:09 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1THopY-00038E-EG for xen-users@lists.xen.org; Sat, 29 Sep 2012 04:39:08 +0000 Received: from [85.158.143.35:31621] by server-2.bemta-4.messagelabs.com id 19/F0-06610-B6B76605; Sat, 29 Sep 2012 04:39:07 +0000 X-Env-Sender: james.harper@bendigoit.com.au X-Msg-Ref: server-11.tower-21.messagelabs.com!1348893544!13533426!1 X-Originating-IP: [203.16.207.99] X-SpamReason: No, hits=0.0 required=7.0 tests= X-StarScan-Received: X-StarScan-Version: 6.6.1.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 668 invoked from network); 29 Sep 2012 04:39:06 -0000 Received: from mail.bendigoit.com.au (HELO smtp2.bendigoit.com.au) (203.16.207.99) by server-11.tower-21.messagelabs.com with AES256-SHA encrypted SMTP; 29 Sep 2012 04:39:06 -0000 Received: from [2001:388:e000:712:a5ca:4fd3:14f:ad5d] (helo=BITCOM1.int.sbss.com.au) by smtp2.bendigoit.com.au with esmtp (Exim 4.72) (envelope-from ) id 1THopL-0002VX-Rz; Sat, 29 Sep 2012 14:38:55 +1000 Received: from BITCOM1.int.sbss.com.au ([fe80::a5ca:4fd3:14f:ad5d]) by BITCOM1.int.sbss.com.au ([fe80::a5ca:4fd3:14f:ad5d%12]) with mapi id 14.01.0379.000; Sat, 29 Sep 2012 14:38:54 +1000 From: James Harper To: Casey DeLorme Thread-Topic: [Xen-users] Xen linux and gaming box Thread-Index: AQHNnaSgDXOblOlTvkqBGt3hlmO8pJefcLiAgAEaZTD//2qegIAAxvHg Date: Sat, 29 Sep 2012 04:38:52 +0000 Message-ID: <6035A0D088A63A46850C3988ED045A4B2EAB3D0F@BITCOM1.int.sbss.com.au> References: <6035A0D088A63A46850C3988ED045A4B2EAB3A10@BITCOM1.int.sbss.com.au> In-Reply-To: Accept-Language: en-AU, en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [2001:388:e000:712:219f:fab2:912f:3b7f] x-tm-as-product-ver: SMEX-10.2.0.2087-7.000.1014-19220.001 x-tm-as-result: No--29.236700-0.000000-31 x-tm-as-user-approved-sender: Yes x-tm-as-user-blocked-sender: No MIME-Version: 1.0 X-Really-From-Bendigo-IT: magichashvalue Cc: "xen-users@lists.xen.org" , "karim@robotstampede.com" Subject: Re: [Xen-users] Xen linux and gaming box X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org > > Windows recognizes the drive as an SSD, since it turned off defrag > automatically for just that drive. I don't know if GPLPV has anything to do > with it, if it turned off defrag maybe it's Windows/NTFS taking care of TRIM? > Windows can't possibly know that the drive is an SSD unless I've told it, and GPLPV doesn't give it any such information. That's for vbd (eg regular block device) though. For a USB disk passed through, or a scsi passthrough device it could interrogate the drive directly. > There are a lot of factors involved, remember it is running on a Logical > Volume partition which is handled by LVM, so it's not all about the drivers. > As far as GPLPV is concerned, the communications channel is basically read and write. Very little meta-information is passed through. I haven't even added barrier support yet because I've only recently been using a system that provides it for LVM. James _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Sat Sep 29 04:40:29 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Sat, 29 Sep 2012 04:40:29 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1THopZ-00038K-GA; Sat, 29 Sep 2012 04:39:09 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1THopY-00038E-EG for xen-users@lists.xen.org; Sat, 29 Sep 2012 04:39:08 +0000 Received: from [85.158.143.35:31621] by server-2.bemta-4.messagelabs.com id 19/F0-06610-B6B76605; Sat, 29 Sep 2012 04:39:07 +0000 X-Env-Sender: james.harper@bendigoit.com.au X-Msg-Ref: server-11.tower-21.messagelabs.com!1348893544!13533426!1 X-Originating-IP: [203.16.207.99] X-SpamReason: No, hits=0.0 required=7.0 tests= X-StarScan-Received: X-StarScan-Version: 6.6.1.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 668 invoked from network); 29 Sep 2012 04:39:06 -0000 Received: from mail.bendigoit.com.au (HELO smtp2.bendigoit.com.au) (203.16.207.99) by server-11.tower-21.messagelabs.com with AES256-SHA encrypted SMTP; 29 Sep 2012 04:39:06 -0000 Received: from [2001:388:e000:712:a5ca:4fd3:14f:ad5d] (helo=BITCOM1.int.sbss.com.au) by smtp2.bendigoit.com.au with esmtp (Exim 4.72) (envelope-from ) id 1THopL-0002VX-Rz; Sat, 29 Sep 2012 14:38:55 +1000 Received: from BITCOM1.int.sbss.com.au ([fe80::a5ca:4fd3:14f:ad5d]) by BITCOM1.int.sbss.com.au ([fe80::a5ca:4fd3:14f:ad5d%12]) with mapi id 14.01.0379.000; Sat, 29 Sep 2012 14:38:54 +1000 From: James Harper To: Casey DeLorme Thread-Topic: [Xen-users] Xen linux and gaming box Thread-Index: AQHNnaSgDXOblOlTvkqBGt3hlmO8pJefcLiAgAEaZTD//2qegIAAxvHg Date: Sat, 29 Sep 2012 04:38:52 +0000 Message-ID: <6035A0D088A63A46850C3988ED045A4B2EAB3D0F@BITCOM1.int.sbss.com.au> References: <6035A0D088A63A46850C3988ED045A4B2EAB3A10@BITCOM1.int.sbss.com.au> In-Reply-To: Accept-Language: en-AU, en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [2001:388:e000:712:219f:fab2:912f:3b7f] x-tm-as-product-ver: SMEX-10.2.0.2087-7.000.1014-19220.001 x-tm-as-result: No--29.236700-0.000000-31 x-tm-as-user-approved-sender: Yes x-tm-as-user-blocked-sender: No MIME-Version: 1.0 X-Really-From-Bendigo-IT: magichashvalue Cc: "xen-users@lists.xen.org" , "karim@robotstampede.com" Subject: Re: [Xen-users] Xen linux and gaming box X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org > > Windows recognizes the drive as an SSD, since it turned off defrag > automatically for just that drive. I don't know if GPLPV has anything to do > with it, if it turned off defrag maybe it's Windows/NTFS taking care of TRIM? > Windows can't possibly know that the drive is an SSD unless I've told it, and GPLPV doesn't give it any such information. That's for vbd (eg regular block device) though. For a USB disk passed through, or a scsi passthrough device it could interrogate the drive directly. > There are a lot of factors involved, remember it is running on a Logical > Volume partition which is handled by LVM, so it's not all about the drivers. > As far as GPLPV is concerned, the communications channel is basically read and write. Very little meta-information is passed through. I haven't even added barrier support yet because I've only recently been using a system that provides it for LVM. James _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Sat Sep 29 06:19:05 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Sat, 29 Sep 2012 06:19:05 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1THqN3-0004XO-82; Sat, 29 Sep 2012 06:17:49 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1THqN1-0004XG-3l for xen-users@lists.xen.org; Sat, 29 Sep 2012 06:17:47 +0000 Received: from [85.158.138.51:61771] by server-11.bemta-3.messagelabs.com id 13/70-21460-A8296605; Sat, 29 Sep 2012 06:17:46 +0000 X-Env-Sender: ksanjabi@gmail.com X-Msg-Ref: server-16.tower-174.messagelabs.com!1348899464!32339573!1 X-Originating-IP: [209.85.220.173] X-SpamReason: No, hits=0.4 required=7.0 tests=HTML_30_40,HTML_MESSAGE, RCVD_BY_IP X-StarScan-Received: X-StarScan-Version: 6.6.1.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 16622 invoked from network); 29 Sep 2012 06:17:45 -0000 Received: from mail-vc0-f173.google.com (HELO mail-vc0-f173.google.com) (209.85.220.173) by server-16.tower-174.messagelabs.com with RC4-SHA encrypted SMTP; 29 Sep 2012 06:17:45 -0000 Received: by vcbfl15 with SMTP id fl15so5086466vcb.32 for ; Fri, 28 Sep 2012 23:17:44 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:reply-to:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type; bh=oedBFKDTlt09fz/6FNINyQTr29lYBGxw0AqaXG7nZq8=; b=uc/2X0jrEnFBO387wIRoPPnVRALWt0i17/oUdmpJ3oy6RU41tFcEBKbK4XJTU8F8A3 U/8Ujdvo5z0JV8pPIz7ka44V9hKrCINrL72J5RdSezW4bWU4aoveZTKJ6VKtd90SYvOG jHvTItwsFKOpXSihyd57aH8ZO0Dvf7K+mf426L50IAtubeJx7FHpyrKgYoReCYjK5Q62 idQbBBxFMduChP5npYaSi49DRZ2l7ZvUoqy9NTmsrEh/ugw/ZQ19yveIQ0kjBC9Bp0mJ 7USOw6bjDKBoz1nuGfWYpNL9JsgfWhi1ga3w/Do3DUGQFqWU8ud1YEx65CenSzpS1/UB TMUA== MIME-Version: 1.0 Received: by 10.59.0.41 with SMTP id av9mr5453095ved.32.1348899463957; Fri, 28 Sep 2012 23:17:43 -0700 (PDT) Received: by 10.220.70.71 with HTTP; Fri, 28 Sep 2012 23:17:43 -0700 (PDT) In-Reply-To: <6035A0D088A63A46850C3988ED045A4B2EAB3D0F@BITCOM1.int.sbss.com.au> References: <6035A0D088A63A46850C3988ED045A4B2EAB3A10@BITCOM1.int.sbss.com.au> <6035A0D088A63A46850C3988ED045A4B2EAB3D0F@BITCOM1.int.sbss.com.au> Date: Fri, 28 Sep 2012 23:17:43 -0700 X-Google-Sender-Auth: ebAHj1sX41QGz-Ua5xIGJi2w2O8 Message-ID: From: Karim Sanjabi To: James Harper Cc: "xen-users@lists.xen.org" Subject: Re: [Xen-users] Xen linux and gaming box X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list Reply-To: karim@robotstampede.com List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============8609470489376203386==" Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org --===============8609470489376203386== Content-Type: multipart/alternative; boundary=047d7bdc992c630b9b04cad121de --047d7bdc992c630b9b04cad121de Content-Type: text/plain; charset=ISO-8859-1 Does it makes sense (or can it be done) to pass through a sata bus with the ssd on it? Karim On Fri, Sep 28, 2012 at 9:38 PM, James Harper wrote: > > > > Windows recognizes the drive as an SSD, since it turned off defrag > > automatically for just that drive. I don't know if GPLPV has anything > to do > > with it, if it turned off defrag maybe it's Windows/NTFS taking care of > TRIM? > > > > Windows can't possibly know that the drive is an SSD unless I've told it, > and GPLPV doesn't give it any such information. That's for vbd (eg regular > block device) though. For a USB disk passed through, or a scsi passthrough > device it could interrogate the drive directly. > > > There are a lot of factors involved, remember it is running on a Logical > > Volume partition which is handled by LVM, so it's not all about the > drivers. > > > > As far as GPLPV is concerned, the communications channel is basically read > and write. Very little meta-information is passed through. I haven't even > added barrier support yet because I've only recently been using a system > that provides it for LVM. > > James > > -- Connect with: 415.378.3688. Twitter: @robotstampede. Skype: ksanjabi. FB: http://www.facebook.com/robotstampede/ --047d7bdc992c630b9b04cad121de Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Does it makes sense (or can it be done) to pass through a sata bus with the= ssd on it?

Karim


On Fri, Sep= 28, 2012 at 9:38 PM, James Harper <james.harper@bendigoit.com= .au> wrote:
>
> Windows recognizes the drive as an SSD, since it turned off defrag
> automatically for just that drive. =A0I don't know if GPLPV has an= ything to do
> with it, if it turned off defrag maybe it's Windows/NTFS taking ca= re of TRIM?
>

Windows can't possibly know that the drive is an SSD unless I'= ;ve told it, and GPLPV doesn't give it any such information. That's= for vbd (eg regular block device) though. For a USB disk passed through, o= r a scsi passthrough device it could interrogate the drive directly.

> There are a lot of factors involved, remember it is running on a Logic= al
> Volume partition which is handled by LVM, so it's not all about th= e drivers.
>

As far as GPLPV is concerned, the communications channel is basically= read and write. Very little meta-information is passed through. I haven= 9;t even added barrier support yet because I've only recently been usin= g a system that provides it for LVM.

James




--
Connect w= ith: 415.378.3688. Twitter: @robotstampede. Skype: ksanjabi.=A0 FB: http://www.fa= cebook.com/robotstampede/

--047d7bdc992c630b9b04cad121de-- --===============8609470489376203386== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users --===============8609470489376203386==-- From xen-users-bounces@lists.xen.org Sat Sep 29 06:19:05 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Sat, 29 Sep 2012 06:19:05 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1THqN3-0004XO-82; Sat, 29 Sep 2012 06:17:49 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1THqN1-0004XG-3l for xen-users@lists.xen.org; Sat, 29 Sep 2012 06:17:47 +0000 Received: from [85.158.138.51:61771] by server-11.bemta-3.messagelabs.com id 13/70-21460-A8296605; Sat, 29 Sep 2012 06:17:46 +0000 X-Env-Sender: ksanjabi@gmail.com X-Msg-Ref: server-16.tower-174.messagelabs.com!1348899464!32339573!1 X-Originating-IP: [209.85.220.173] X-SpamReason: No, hits=0.4 required=7.0 tests=HTML_30_40,HTML_MESSAGE, RCVD_BY_IP X-StarScan-Received: X-StarScan-Version: 6.6.1.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 16622 invoked from network); 29 Sep 2012 06:17:45 -0000 Received: from mail-vc0-f173.google.com (HELO mail-vc0-f173.google.com) (209.85.220.173) by server-16.tower-174.messagelabs.com with RC4-SHA encrypted SMTP; 29 Sep 2012 06:17:45 -0000 Received: by vcbfl15 with SMTP id fl15so5086466vcb.32 for ; Fri, 28 Sep 2012 23:17:44 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:reply-to:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type; bh=oedBFKDTlt09fz/6FNINyQTr29lYBGxw0AqaXG7nZq8=; b=uc/2X0jrEnFBO387wIRoPPnVRALWt0i17/oUdmpJ3oy6RU41tFcEBKbK4XJTU8F8A3 U/8Ujdvo5z0JV8pPIz7ka44V9hKrCINrL72J5RdSezW4bWU4aoveZTKJ6VKtd90SYvOG jHvTItwsFKOpXSihyd57aH8ZO0Dvf7K+mf426L50IAtubeJx7FHpyrKgYoReCYjK5Q62 idQbBBxFMduChP5npYaSi49DRZ2l7ZvUoqy9NTmsrEh/ugw/ZQ19yveIQ0kjBC9Bp0mJ 7USOw6bjDKBoz1nuGfWYpNL9JsgfWhi1ga3w/Do3DUGQFqWU8ud1YEx65CenSzpS1/UB TMUA== MIME-Version: 1.0 Received: by 10.59.0.41 with SMTP id av9mr5453095ved.32.1348899463957; Fri, 28 Sep 2012 23:17:43 -0700 (PDT) Received: by 10.220.70.71 with HTTP; Fri, 28 Sep 2012 23:17:43 -0700 (PDT) In-Reply-To: <6035A0D088A63A46850C3988ED045A4B2EAB3D0F@BITCOM1.int.sbss.com.au> References: <6035A0D088A63A46850C3988ED045A4B2EAB3A10@BITCOM1.int.sbss.com.au> <6035A0D088A63A46850C3988ED045A4B2EAB3D0F@BITCOM1.int.sbss.com.au> Date: Fri, 28 Sep 2012 23:17:43 -0700 X-Google-Sender-Auth: ebAHj1sX41QGz-Ua5xIGJi2w2O8 Message-ID: From: Karim Sanjabi To: James Harper Cc: "xen-users@lists.xen.org" Subject: Re: [Xen-users] Xen linux and gaming box X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list Reply-To: karim@robotstampede.com List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============8609470489376203386==" Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org --===============8609470489376203386== Content-Type: multipart/alternative; boundary=047d7bdc992c630b9b04cad121de --047d7bdc992c630b9b04cad121de Content-Type: text/plain; charset=ISO-8859-1 Does it makes sense (or can it be done) to pass through a sata bus with the ssd on it? Karim On Fri, Sep 28, 2012 at 9:38 PM, James Harper wrote: > > > > Windows recognizes the drive as an SSD, since it turned off defrag > > automatically for just that drive. I don't know if GPLPV has anything > to do > > with it, if it turned off defrag maybe it's Windows/NTFS taking care of > TRIM? > > > > Windows can't possibly know that the drive is an SSD unless I've told it, > and GPLPV doesn't give it any such information. That's for vbd (eg regular > block device) though. For a USB disk passed through, or a scsi passthrough > device it could interrogate the drive directly. > > > There are a lot of factors involved, remember it is running on a Logical > > Volume partition which is handled by LVM, so it's not all about the > drivers. > > > > As far as GPLPV is concerned, the communications channel is basically read > and write. Very little meta-information is passed through. I haven't even > added barrier support yet because I've only recently been using a system > that provides it for LVM. > > James > > -- Connect with: 415.378.3688. Twitter: @robotstampede. Skype: ksanjabi. FB: http://www.facebook.com/robotstampede/ --047d7bdc992c630b9b04cad121de Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Does it makes sense (or can it be done) to pass through a sata bus with the= ssd on it?

Karim


On Fri, Sep= 28, 2012 at 9:38 PM, James Harper <james.harper@bendigoit.com= .au> wrote:
>
> Windows recognizes the drive as an SSD, since it turned off defrag
> automatically for just that drive. =A0I don't know if GPLPV has an= ything to do
> with it, if it turned off defrag maybe it's Windows/NTFS taking ca= re of TRIM?
>

Windows can't possibly know that the drive is an SSD unless I'= ;ve told it, and GPLPV doesn't give it any such information. That's= for vbd (eg regular block device) though. For a USB disk passed through, o= r a scsi passthrough device it could interrogate the drive directly.

> There are a lot of factors involved, remember it is running on a Logic= al
> Volume partition which is handled by LVM, so it's not all about th= e drivers.
>

As far as GPLPV is concerned, the communications channel is basically= read and write. Very little meta-information is passed through. I haven= 9;t even added barrier support yet because I've only recently been usin= g a system that provides it for LVM.

James




--
Connect w= ith: 415.378.3688. Twitter: @robotstampede. Skype: ksanjabi.=A0 FB: http://www.fa= cebook.com/robotstampede/

--047d7bdc992c630b9b04cad121de-- --===============8609470489376203386== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users --===============8609470489376203386==-- From xen-users-bounces@lists.xen.org Sat Sep 29 06:20:59 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Sat, 29 Sep 2012 06:20:59 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1THqOv-0004db-0I; Sat, 29 Sep 2012 06:19:45 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1THqOu-0004dT-5Y for xen-users@lists.xen.org; Sat, 29 Sep 2012 06:19:44 +0000 Received: from [85.158.137.99:26953] by server-8.bemta-3.messagelabs.com id 61/DA-16337-FF296605; Sat, 29 Sep 2012 06:19:43 +0000 X-Env-Sender: james.harper@bendigoit.com.au X-Msg-Ref: server-6.tower-217.messagelabs.com!1348899579!14452379!1 X-Originating-IP: [203.16.224.4] X-SpamReason: No, hits=0.0 required=7.0 tests= X-StarScan-Received: X-StarScan-Version: 6.6.1.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 1264 invoked from network); 29 Sep 2012 06:19:42 -0000 Received: from smtp1.bendigoit.com.au (HELO smtp1.bendigoit.com.au) (203.16.224.4) by server-6.tower-217.messagelabs.com with AES256-SHA encrypted SMTP; 29 Sep 2012 06:19:42 -0000 Received: from [2001:388:e000:712:a5ca:4fd3:14f:ad5d] (helo=BITCOM1.int.sbss.com.au) by smtp1.bendigoit.com.au with esmtp (Exim 4.69) (envelope-from ) id 1THqOl-00046N-Gf; Sat, 29 Sep 2012 16:19:35 +1000 Received: from BITCOM1.int.sbss.com.au ([fe80::a5ca:4fd3:14f:ad5d]) by BITCOM1.int.sbss.com.au ([fe80::a5ca:4fd3:14f:ad5d%12]) with mapi id 14.01.0379.000; Sat, 29 Sep 2012 16:19:24 +1000 From: James Harper To: "karim@robotstampede.com" Thread-Topic: [Xen-users] Xen linux and gaming box Thread-Index: AQHNnaSgDXOblOlTvkqBGt3hlmO8pJefcLiAgAEaZTD//2qegIAAxvHg//90rICAAKfGkA== Date: Sat, 29 Sep 2012 06:19:23 +0000 Message-ID: <6035A0D088A63A46850C3988ED045A4B2EAB3F34@BITCOM1.int.sbss.com.au> References: <6035A0D088A63A46850C3988ED045A4B2EAB3A10@BITCOM1.int.sbss.com.au> <6035A0D088A63A46850C3988ED045A4B2EAB3D0F@BITCOM1.int.sbss.com.au> In-Reply-To: Accept-Language: en-AU, en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [2001:388:e000:712:219f:fab2:912f:3b7f] x-tm-as-product-ver: SMEX-10.2.0.2087-7.000.1014-19220.001 x-tm-as-result: No--22.448900-0.000000-31 x-tm-as-user-approved-sender: Yes x-tm-as-user-blocked-sender: No MIME-Version: 1.0 X-Really-From-Bendigo-IT: magichashvalue Cc: "xen-users@lists.xen.org" Subject: Re: [Xen-users] Xen linux and gaming box X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org > > Does it makes sense (or can it be done) to pass through a sata bus with the > ssd on it? > It could be done, but someone would have to write the protocol for it. SCSI passthrough already exists, and GPLPV does that, although I'm not sure if it's in the later kernels and I'm pretty sure it's not supported in the xl toolstack. I'm looking at adding trim to the GPLPV drivers if possible. James _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Sat Sep 29 06:20:59 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Sat, 29 Sep 2012 06:20:59 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1THqOv-0004db-0I; Sat, 29 Sep 2012 06:19:45 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1THqOu-0004dT-5Y for xen-users@lists.xen.org; Sat, 29 Sep 2012 06:19:44 +0000 Received: from [85.158.137.99:26953] by server-8.bemta-3.messagelabs.com id 61/DA-16337-FF296605; Sat, 29 Sep 2012 06:19:43 +0000 X-Env-Sender: james.harper@bendigoit.com.au X-Msg-Ref: server-6.tower-217.messagelabs.com!1348899579!14452379!1 X-Originating-IP: [203.16.224.4] X-SpamReason: No, hits=0.0 required=7.0 tests= X-StarScan-Received: X-StarScan-Version: 6.6.1.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 1264 invoked from network); 29 Sep 2012 06:19:42 -0000 Received: from smtp1.bendigoit.com.au (HELO smtp1.bendigoit.com.au) (203.16.224.4) by server-6.tower-217.messagelabs.com with AES256-SHA encrypted SMTP; 29 Sep 2012 06:19:42 -0000 Received: from [2001:388:e000:712:a5ca:4fd3:14f:ad5d] (helo=BITCOM1.int.sbss.com.au) by smtp1.bendigoit.com.au with esmtp (Exim 4.69) (envelope-from ) id 1THqOl-00046N-Gf; Sat, 29 Sep 2012 16:19:35 +1000 Received: from BITCOM1.int.sbss.com.au ([fe80::a5ca:4fd3:14f:ad5d]) by BITCOM1.int.sbss.com.au ([fe80::a5ca:4fd3:14f:ad5d%12]) with mapi id 14.01.0379.000; Sat, 29 Sep 2012 16:19:24 +1000 From: James Harper To: "karim@robotstampede.com" Thread-Topic: [Xen-users] Xen linux and gaming box Thread-Index: AQHNnaSgDXOblOlTvkqBGt3hlmO8pJefcLiAgAEaZTD//2qegIAAxvHg//90rICAAKfGkA== Date: Sat, 29 Sep 2012 06:19:23 +0000 Message-ID: <6035A0D088A63A46850C3988ED045A4B2EAB3F34@BITCOM1.int.sbss.com.au> References: <6035A0D088A63A46850C3988ED045A4B2EAB3A10@BITCOM1.int.sbss.com.au> <6035A0D088A63A46850C3988ED045A4B2EAB3D0F@BITCOM1.int.sbss.com.au> In-Reply-To: Accept-Language: en-AU, en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [2001:388:e000:712:219f:fab2:912f:3b7f] x-tm-as-product-ver: SMEX-10.2.0.2087-7.000.1014-19220.001 x-tm-as-result: No--22.448900-0.000000-31 x-tm-as-user-approved-sender: Yes x-tm-as-user-blocked-sender: No MIME-Version: 1.0 X-Really-From-Bendigo-IT: magichashvalue Cc: "xen-users@lists.xen.org" Subject: Re: [Xen-users] Xen linux and gaming box X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org > > Does it makes sense (or can it be done) to pass through a sata bus with the > ssd on it? > It could be done, but someone would have to write the protocol for it. SCSI passthrough already exists, and GPLPV does that, although I'm not sure if it's in the later kernels and I'm pretty sure it's not supported in the xl toolstack. I'm looking at adding trim to the GPLPV drivers if possible. James _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Sat Sep 29 09:43:06 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Sat, 29 Sep 2012 09:43:06 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1THtYP-0006N6-BE; Sat, 29 Sep 2012 09:41:45 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1THtYN-0006Ms-QW for xen-users@lists.xensource.com; Sat, 29 Sep 2012 09:41:43 +0000 Received: from [85.158.138.51:44184] by server-10.bemta-3.messagelabs.com id F7/40-02525-552C6605; Sat, 29 Sep 2012 09:41:41 +0000 X-Env-Sender: mrsanna1@gmail.com X-Msg-Ref: server-4.tower-174.messagelabs.com!1348911700!31931804!1 X-Originating-IP: [209.85.220.171] X-SpamReason: No, hits=0.3 required=7.0 tests=ML_RADAR_SPEW_LINKS_14, RCVD_BY_IP,spamassassin: X-StarScan-Received: X-StarScan-Version: 6.6.1.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 11018 invoked from network); 29 Sep 2012 09:41:41 -0000 Received: from mail-vc0-f171.google.com (HELO mail-vc0-f171.google.com) (209.85.220.171) by server-4.tower-174.messagelabs.com with RC4-SHA encrypted SMTP; 29 Sep 2012 09:41:41 -0000 Received: by vcmm18 with SMTP id m18so5282817vcm.30 for ; Sat, 29 Sep 2012 02:41:39 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=QicbjTIQNJAK0q1m/rxd4jUc7f+dM9dwJRBq0N2ZGyg=; b=AlrxER6AtkHA+HeAj/1co2DRG/VxlLcyisaVN7fsKZg4C44rkQEHNjff34rqHKW2QD XVp8OT8xRbT8cKWaW+p06R1QebGeyIn5JTlrmoX3qKK3555Z5hKjnI29iXg3bL3f8dWy HUGKXbNc/D7Qw1Km3jAy50CNXEEXTpmErzpBoTVdDO/TBJtKFq7KkFcrami9CA9wBMek wtxp3n3rosWFa47WQf/3ntF5/JDUehoG900E3vuKqfMj9fr3/uitUxsWxJ1mQN8jByrl A1j6W64MbJjeDBr8iPd1ogcJiaEULTp4C/XaP76ttP0iR3FxgIjFu+Vw+593Yz+bE5kr 8QrA== MIME-Version: 1.0 Received: by 10.58.227.106 with SMTP id rz10mr5631255vec.19.1348911699689; Sat, 29 Sep 2012 02:41:39 -0700 (PDT) Received: by 10.58.207.75 with HTTP; Sat, 29 Sep 2012 02:41:39 -0700 (PDT) In-Reply-To: References: <68c41dd8-9195-41b0-83d7-9242b8eff809@default> <65395f62-74e5-4910-b701-8df629c2ce3b@default> Date: Sat, 29 Sep 2012 11:41:39 +0200 Message-ID: From: Mauro To: Olivier Hanesse Cc: Dan Magenheimer , xen-devel@lists.xensource.com, Keir Fraser , Jeremy Fitzhardinge , Jan Beulich , Keir Fraser , Xen Users , Mark Adams Subject: Re: [Xen-users] [Xen-devel] Xen 4 TSC problems X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org On 29 September 2012 10:08, Olivier Hanesse wrote: > It didn't work for me :( > clocksource=pit made another "time jump" (don't remember how much, but it > was worst than 50min) Damn.........so there isn't a solution, it is a huge problem. What processors do you have? I have HP Proliant DL580 G5 systems with four quad core Intel(R) Xeon(R) CPU E7330 @ 2.40GHz and debian linux as s.o. _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Sat Sep 29 09:43:06 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Sat, 29 Sep 2012 09:43:06 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1THtYP-0006N6-BE; Sat, 29 Sep 2012 09:41:45 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1THtYN-0006Ms-QW for xen-users@lists.xensource.com; Sat, 29 Sep 2012 09:41:43 +0000 Received: from [85.158.138.51:44184] by server-10.bemta-3.messagelabs.com id F7/40-02525-552C6605; Sat, 29 Sep 2012 09:41:41 +0000 X-Env-Sender: mrsanna1@gmail.com X-Msg-Ref: server-4.tower-174.messagelabs.com!1348911700!31931804!1 X-Originating-IP: [209.85.220.171] X-SpamReason: No, hits=0.3 required=7.0 tests=ML_RADAR_SPEW_LINKS_14, RCVD_BY_IP,spamassassin: X-StarScan-Received: X-StarScan-Version: 6.6.1.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 11018 invoked from network); 29 Sep 2012 09:41:41 -0000 Received: from mail-vc0-f171.google.com (HELO mail-vc0-f171.google.com) (209.85.220.171) by server-4.tower-174.messagelabs.com with RC4-SHA encrypted SMTP; 29 Sep 2012 09:41:41 -0000 Received: by vcmm18 with SMTP id m18so5282817vcm.30 for ; Sat, 29 Sep 2012 02:41:39 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=QicbjTIQNJAK0q1m/rxd4jUc7f+dM9dwJRBq0N2ZGyg=; b=AlrxER6AtkHA+HeAj/1co2DRG/VxlLcyisaVN7fsKZg4C44rkQEHNjff34rqHKW2QD XVp8OT8xRbT8cKWaW+p06R1QebGeyIn5JTlrmoX3qKK3555Z5hKjnI29iXg3bL3f8dWy HUGKXbNc/D7Qw1Km3jAy50CNXEEXTpmErzpBoTVdDO/TBJtKFq7KkFcrami9CA9wBMek wtxp3n3rosWFa47WQf/3ntF5/JDUehoG900E3vuKqfMj9fr3/uitUxsWxJ1mQN8jByrl A1j6W64MbJjeDBr8iPd1ogcJiaEULTp4C/XaP76ttP0iR3FxgIjFu+Vw+593Yz+bE5kr 8QrA== MIME-Version: 1.0 Received: by 10.58.227.106 with SMTP id rz10mr5631255vec.19.1348911699689; Sat, 29 Sep 2012 02:41:39 -0700 (PDT) Received: by 10.58.207.75 with HTTP; Sat, 29 Sep 2012 02:41:39 -0700 (PDT) In-Reply-To: References: <68c41dd8-9195-41b0-83d7-9242b8eff809@default> <65395f62-74e5-4910-b701-8df629c2ce3b@default> Date: Sat, 29 Sep 2012 11:41:39 +0200 Message-ID: From: Mauro To: Olivier Hanesse Cc: Dan Magenheimer , xen-devel@lists.xensource.com, Keir Fraser , Jeremy Fitzhardinge , Jan Beulich , Keir Fraser , Xen Users , Mark Adams Subject: Re: [Xen-users] [Xen-devel] Xen 4 TSC problems X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org On 29 September 2012 10:08, Olivier Hanesse wrote: > It didn't work for me :( > clocksource=pit made another "time jump" (don't remember how much, but it > was worst than 50min) Damn.........so there isn't a solution, it is a huge problem. What processors do you have? I have HP Proliant DL580 G5 systems with four quad core Intel(R) Xeon(R) CPU E7330 @ 2.40GHz and debian linux as s.o. _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Sat Sep 29 10:33:03 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Sat, 29 Sep 2012 10:33:03 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1THuKt-0006vX-1z; Sat, 29 Sep 2012 10:31:51 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1THuKr-0006vS-Fz for xen-users@lists.xen.org; Sat, 29 Sep 2012 10:31:49 +0000 Received: from [85.158.139.83:36557] by server-6.bemta-5.messagelabs.com id 2A/4C-14717-41EC6605; Sat, 29 Sep 2012 10:31:48 +0000 X-Env-Sender: singapore.mr.teo.en.ming@gmail.com X-Msg-Ref: server-13.tower-182.messagelabs.com!1348914706!32118553!1 X-Originating-IP: [209.85.160.45] X-SpamReason: No, hits=0.3 required=7.0 tests=ML_RADAR_SPEW_LINKS_14, RCVD_BY_IP,spamassassin: X-StarScan-Received: X-StarScan-Version: 6.6.1.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 17261 invoked from network); 29 Sep 2012 10:31:48 -0000 Received: from mail-pb0-f45.google.com (HELO mail-pb0-f45.google.com) (209.85.160.45) by server-13.tower-182.messagelabs.com with RC4-SHA encrypted SMTP; 29 Sep 2012 10:31:48 -0000 Received: by pbbrp2 with SMTP id rp2so6323733pbb.32 for ; Sat, 29 Sep 2012 03:31:46 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:user-agent:mime-version:to:subject:references :in-reply-to:content-type:content-transfer-encoding; bh=rm5pGtYnzbIJ556Dv/QOgdjuxaPYhZo1qQfCanhQCFw=; b=SluiY7QzKpJdqC7WUFPZN8ry+EnPp6GSCjaDHm+m+lgS9IEw0oK91VsA8hGF/h4mtd QDLsxUWWZqrxlrwvoCE2YqDQe6Dbdh9S1QLCp6bzuYgQwdxNPXL1J6Pa1N/48vdL2B2D AUSzdPkbooSdtx7vprJc8Fv6hjxrcu4cZMXNPSOsqO3HChLxeaxzv/vY+0LlRq3kjS/p S8sX2qo+sgnHcJAFHigWdWlVuPMHYKgUtBqL/hH8dxaeuHB/bxPNvb6+YbSLNkwIRF73 kmBdxzXgDrOhhRH5tDSIYCDjzBrbtisu58/+f4zFZFRpxfJktTWPjsJPr8NrpoScZPaV 5jWw== Received: by 10.68.222.40 with SMTP id qj8mr26797186pbc.139.1348914705829; Sat, 29 Sep 2012 03:31:45 -0700 (PDT) Received: from [192.168.1.2] (cm152.gamma205.maxonline.com.sg. [202.156.205.152]) by mx.google.com with ESMTPS id c5sm7014437pay.5.2012.09.29.03.31.43 (version=SSLv3 cipher=OTHER); Sat, 29 Sep 2012 03:31:44 -0700 (PDT) Message-ID: <5066CE0D.9080402@gmail.com> Date: Sat, 29 Sep 2012 18:31:41 +0800 From: "Teo En Ming (Zhang Enming)" User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:15.0) Gecko/20120912 Thunderbird/15.0.1 MIME-Version: 1.0 To: Mike Viau , "xen-users@lists.xen.org" , "Teo En Ming (Zhang Enming)" References: , <50645166.2000200@gmail.com> <50647B26.9080903@gmail.com>, , <50648CEA.9070107@gmail.com> , In-Reply-To: Subject: Re: [Xen-users] Success VGA passthrough on windows 7 x64 with Xen 4.2.1-pre X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset="us-ascii"; Format="flowed" Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org On 28/09/2012 08:01, Mike Viau wrote: > >> On Thu, 27 Sep 2012 20:34:54 +0200 wrote: >> >>> 2012/9/27 Mike Viau : >>> >>>> On Fri, 28 Sep 2012 01:29:14 +0800 wrote: >>>> >>>> Dear Dariusz Krempa, >>>> >>>> Thank you for your prompt reply. >>>> >>>> I don't have pci_msitranslate = 1 in my Windows HVM domU config file, so >>>> I don't think "pci_msitranslate = 1" is the main cause of my "nasty >>>> yellow triangle with error 43". >>>> >>> I once recorded that the default for the pci_msitranslate option was "1". Not having this in your configuration then is like having it set. Feel free to correct me if I am wrong. I have only gotten VGA pass-through to work with a Windows domU, never in GNU/Linux for some reason. >>> >>> >>> -M >> from change set 25525 msitranslate is 0 by deafault >> >> http://xenbits.xensource.com/hg/staging/xen-unstable.hg/rev/84272cca638a?revcount=120 >> > Thanks for this information, it was much appreciated! I will be updating my notes accordingly. > > -M > > _______________________________________________ > Xen-users mailing list > Xen-users@lists.xen.org > http://lists.xen.org/xen-users > Dear Dariusz Krempa, Could you publish your xen vga passthrough configuration files, namely the windows 7 x64 HVM domU configuration file? I have tried setting pci_msitranslate to 1 and also 0 but the nasty yellow triangle with an exclamation mark and error 43 won't go away. pci_msitranslate has no effect on my system. Thank you very much. -- Yours sincerely, Mr. Teo En Ming (Zhang Enming) Singapore _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Sat Sep 29 10:33:03 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Sat, 29 Sep 2012 10:33:03 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1THuKt-0006vX-1z; Sat, 29 Sep 2012 10:31:51 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1THuKr-0006vS-Fz for xen-users@lists.xen.org; Sat, 29 Sep 2012 10:31:49 +0000 Received: from [85.158.139.83:36557] by server-6.bemta-5.messagelabs.com id 2A/4C-14717-41EC6605; Sat, 29 Sep 2012 10:31:48 +0000 X-Env-Sender: singapore.mr.teo.en.ming@gmail.com X-Msg-Ref: server-13.tower-182.messagelabs.com!1348914706!32118553!1 X-Originating-IP: [209.85.160.45] X-SpamReason: No, hits=0.3 required=7.0 tests=ML_RADAR_SPEW_LINKS_14, RCVD_BY_IP,spamassassin: X-StarScan-Received: X-StarScan-Version: 6.6.1.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 17261 invoked from network); 29 Sep 2012 10:31:48 -0000 Received: from mail-pb0-f45.google.com (HELO mail-pb0-f45.google.com) (209.85.160.45) by server-13.tower-182.messagelabs.com with RC4-SHA encrypted SMTP; 29 Sep 2012 10:31:48 -0000 Received: by pbbrp2 with SMTP id rp2so6323733pbb.32 for ; Sat, 29 Sep 2012 03:31:46 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:user-agent:mime-version:to:subject:references :in-reply-to:content-type:content-transfer-encoding; bh=rm5pGtYnzbIJ556Dv/QOgdjuxaPYhZo1qQfCanhQCFw=; b=SluiY7QzKpJdqC7WUFPZN8ry+EnPp6GSCjaDHm+m+lgS9IEw0oK91VsA8hGF/h4mtd QDLsxUWWZqrxlrwvoCE2YqDQe6Dbdh9S1QLCp6bzuYgQwdxNPXL1J6Pa1N/48vdL2B2D AUSzdPkbooSdtx7vprJc8Fv6hjxrcu4cZMXNPSOsqO3HChLxeaxzv/vY+0LlRq3kjS/p S8sX2qo+sgnHcJAFHigWdWlVuPMHYKgUtBqL/hH8dxaeuHB/bxPNvb6+YbSLNkwIRF73 kmBdxzXgDrOhhRH5tDSIYCDjzBrbtisu58/+f4zFZFRpxfJktTWPjsJPr8NrpoScZPaV 5jWw== Received: by 10.68.222.40 with SMTP id qj8mr26797186pbc.139.1348914705829; Sat, 29 Sep 2012 03:31:45 -0700 (PDT) Received: from [192.168.1.2] (cm152.gamma205.maxonline.com.sg. [202.156.205.152]) by mx.google.com with ESMTPS id c5sm7014437pay.5.2012.09.29.03.31.43 (version=SSLv3 cipher=OTHER); Sat, 29 Sep 2012 03:31:44 -0700 (PDT) Message-ID: <5066CE0D.9080402@gmail.com> Date: Sat, 29 Sep 2012 18:31:41 +0800 From: "Teo En Ming (Zhang Enming)" User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:15.0) Gecko/20120912 Thunderbird/15.0.1 MIME-Version: 1.0 To: Mike Viau , "xen-users@lists.xen.org" , "Teo En Ming (Zhang Enming)" References: , <50645166.2000200@gmail.com> <50647B26.9080903@gmail.com>, , <50648CEA.9070107@gmail.com> , In-Reply-To: Subject: Re: [Xen-users] Success VGA passthrough on windows 7 x64 with Xen 4.2.1-pre X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset="us-ascii"; Format="flowed" Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org On 28/09/2012 08:01, Mike Viau wrote: > >> On Thu, 27 Sep 2012 20:34:54 +0200 wrote: >> >>> 2012/9/27 Mike Viau : >>> >>>> On Fri, 28 Sep 2012 01:29:14 +0800 wrote: >>>> >>>> Dear Dariusz Krempa, >>>> >>>> Thank you for your prompt reply. >>>> >>>> I don't have pci_msitranslate = 1 in my Windows HVM domU config file, so >>>> I don't think "pci_msitranslate = 1" is the main cause of my "nasty >>>> yellow triangle with error 43". >>>> >>> I once recorded that the default for the pci_msitranslate option was "1". Not having this in your configuration then is like having it set. Feel free to correct me if I am wrong. I have only gotten VGA pass-through to work with a Windows domU, never in GNU/Linux for some reason. >>> >>> >>> -M >> from change set 25525 msitranslate is 0 by deafault >> >> http://xenbits.xensource.com/hg/staging/xen-unstable.hg/rev/84272cca638a?revcount=120 >> > Thanks for this information, it was much appreciated! I will be updating my notes accordingly. > > -M > > _______________________________________________ > Xen-users mailing list > Xen-users@lists.xen.org > http://lists.xen.org/xen-users > Dear Dariusz Krempa, Could you publish your xen vga passthrough configuration files, namely the windows 7 x64 HVM domU configuration file? I have tried setting pci_msitranslate to 1 and also 0 but the nasty yellow triangle with an exclamation mark and error 43 won't go away. pci_msitranslate has no effect on my system. Thank you very much. -- Yours sincerely, Mr. Teo En Ming (Zhang Enming) Singapore _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Sat Sep 29 12:21:27 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Sat, 29 Sep 2012 12:21:27 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1THw1Z-0007dz-6X; Sat, 29 Sep 2012 12:20:01 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1THw1X-0007dl-AT for xen-users@lists.xensource.com; Sat, 29 Sep 2012 12:19:59 +0000 Received: from [85.158.138.51:48755] by server-16.bemta-3.messagelabs.com id 2E/AF-09129-D67E6605; Sat, 29 Sep 2012 12:19:57 +0000 X-Env-Sender: mrsanna1@gmail.com X-Msg-Ref: server-16.tower-174.messagelabs.com!1348921195!32359377!1 X-Originating-IP: [209.85.212.43] X-SpamReason: No, hits=0.3 required=7.0 tests=ML_RADAR_SPEW_LINKS_14, RCVD_BY_IP,spamassassin: X-StarScan-Received: X-StarScan-Version: 6.6.1.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 7950 invoked from network); 29 Sep 2012 12:19:57 -0000 Received: from mail-vb0-f43.google.com (HELO mail-vb0-f43.google.com) (209.85.212.43) by server-16.tower-174.messagelabs.com with RC4-SHA encrypted SMTP; 29 Sep 2012 12:19:57 -0000 Received: by vbbfq11 with SMTP id fq11so5026147vbb.30 for ; Sat, 29 Sep 2012 05:19:55 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=YrmqiR55CdaXWRvdqqPIsgslyhll5oJC550N1f7rV+o=; b=tWDjfZH51UPe/Ys9JDbIFSiQrvnZ0Dfvipp+2UV6eeX5e+PnudWuO0L6LLkzIxxgMs DnHz98WmgTFKzp1qsy0ChpsVt8c4aJrSJW5bQzwkCPu2hBofbnxi0FN7bRyEb7P6AL2Z f9B4P25fGfYmuRZkbMoDFoLkM6nqSal8Wycc61m0YnP+7+wNVFgYtMqIb2C0/+/dJDat OvZqE7dkktO2zhEyf9YnuElu9WvCwIC7ge0AXKc9igtDcmmw101OmjL/Fv6+Xc99Lk+h WKvlE7VN/ZCKvu0DVmx1Eb3hr+v6RXLgoNPR/57LyVzx3FS5jgCQcrLnro86Qm1+spl3 BsLA== MIME-Version: 1.0 Received: by 10.220.223.3 with SMTP id ii3mr5508109vcb.74.1348921195486; Sat, 29 Sep 2012 05:19:55 -0700 (PDT) Received: by 10.58.207.75 with HTTP; Sat, 29 Sep 2012 05:19:55 -0700 (PDT) In-Reply-To: References: <68c41dd8-9195-41b0-83d7-9242b8eff809@default> <65395f62-74e5-4910-b701-8df629c2ce3b@default> Date: Sat, 29 Sep 2012 14:19:55 +0200 Message-ID: From: Mauro To: Olivier Hanesse Cc: Dan Magenheimer , xen-devel@lists.xensource.com, Keir Fraser , Jeremy Fitzhardinge , Jan Beulich , Keir Fraser , Xen Users , Mark Adams Subject: Re: [Xen-users] [Xen-devel] Xen 4 TSC problems X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org It's happened another time, system date 50 minutes ahead. There is really no solution? root@xen-p02:~# date sab 29 set 2012, 15.06.25, CEST root@xen-p02:~# hwclock --debug hwclock from util-linux-ng 2.17.2 Using /dev interface to clock. Last drift adjustment done at 1348816781 seconds after 1969 Last calibration done at 1348816781 seconds after 1969 Hardware clock is on UTC time Assuming hardware clock is kept in UTC time. Waiting for clock tick... ...got clock tick Time read from Hardware Clock: 2012/09/29 12:16:58 Hw clock time : 2012/09/29 12:16:58 = 1348921018 seconds since 1969 sab 29 set 2012 14:16:58 CEST -0.751536 seconds root@xen-p02:~# hwclock --show sab 29 set 2012 14:17:12 CEST -0.423643 seconds _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Sat Sep 29 12:21:27 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Sat, 29 Sep 2012 12:21:27 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1THw1Z-0007dz-6X; Sat, 29 Sep 2012 12:20:01 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1THw1X-0007dl-AT for xen-users@lists.xensource.com; Sat, 29 Sep 2012 12:19:59 +0000 Received: from [85.158.138.51:48755] by server-16.bemta-3.messagelabs.com id 2E/AF-09129-D67E6605; Sat, 29 Sep 2012 12:19:57 +0000 X-Env-Sender: mrsanna1@gmail.com X-Msg-Ref: server-16.tower-174.messagelabs.com!1348921195!32359377!1 X-Originating-IP: [209.85.212.43] X-SpamReason: No, hits=0.3 required=7.0 tests=ML_RADAR_SPEW_LINKS_14, RCVD_BY_IP,spamassassin: X-StarScan-Received: X-StarScan-Version: 6.6.1.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 7950 invoked from network); 29 Sep 2012 12:19:57 -0000 Received: from mail-vb0-f43.google.com (HELO mail-vb0-f43.google.com) (209.85.212.43) by server-16.tower-174.messagelabs.com with RC4-SHA encrypted SMTP; 29 Sep 2012 12:19:57 -0000 Received: by vbbfq11 with SMTP id fq11so5026147vbb.30 for ; Sat, 29 Sep 2012 05:19:55 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=YrmqiR55CdaXWRvdqqPIsgslyhll5oJC550N1f7rV+o=; b=tWDjfZH51UPe/Ys9JDbIFSiQrvnZ0Dfvipp+2UV6eeX5e+PnudWuO0L6LLkzIxxgMs DnHz98WmgTFKzp1qsy0ChpsVt8c4aJrSJW5bQzwkCPu2hBofbnxi0FN7bRyEb7P6AL2Z f9B4P25fGfYmuRZkbMoDFoLkM6nqSal8Wycc61m0YnP+7+wNVFgYtMqIb2C0/+/dJDat OvZqE7dkktO2zhEyf9YnuElu9WvCwIC7ge0AXKc9igtDcmmw101OmjL/Fv6+Xc99Lk+h WKvlE7VN/ZCKvu0DVmx1Eb3hr+v6RXLgoNPR/57LyVzx3FS5jgCQcrLnro86Qm1+spl3 BsLA== MIME-Version: 1.0 Received: by 10.220.223.3 with SMTP id ii3mr5508109vcb.74.1348921195486; Sat, 29 Sep 2012 05:19:55 -0700 (PDT) Received: by 10.58.207.75 with HTTP; Sat, 29 Sep 2012 05:19:55 -0700 (PDT) In-Reply-To: References: <68c41dd8-9195-41b0-83d7-9242b8eff809@default> <65395f62-74e5-4910-b701-8df629c2ce3b@default> Date: Sat, 29 Sep 2012 14:19:55 +0200 Message-ID: From: Mauro To: Olivier Hanesse Cc: Dan Magenheimer , xen-devel@lists.xensource.com, Keir Fraser , Jeremy Fitzhardinge , Jan Beulich , Keir Fraser , Xen Users , Mark Adams Subject: Re: [Xen-users] [Xen-devel] Xen 4 TSC problems X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org It's happened another time, system date 50 minutes ahead. There is really no solution? root@xen-p02:~# date sab 29 set 2012, 15.06.25, CEST root@xen-p02:~# hwclock --debug hwclock from util-linux-ng 2.17.2 Using /dev interface to clock. Last drift adjustment done at 1348816781 seconds after 1969 Last calibration done at 1348816781 seconds after 1969 Hardware clock is on UTC time Assuming hardware clock is kept in UTC time. Waiting for clock tick... ...got clock tick Time read from Hardware Clock: 2012/09/29 12:16:58 Hw clock time : 2012/09/29 12:16:58 = 1348921018 seconds since 1969 sab 29 set 2012 14:16:58 CEST -0.751536 seconds root@xen-p02:~# hwclock --show sab 29 set 2012 14:17:12 CEST -0.423643 seconds _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Sat Sep 29 13:37:10 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Sat, 29 Sep 2012 13:37:10 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1THxCq-000894-3X; Sat, 29 Sep 2012 13:35:44 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1THxCo-00088o-Ni for xen-users@lists.xen.org; Sat, 29 Sep 2012 13:35:42 +0000 Received: from [85.158.139.83:26977] by server-6.bemta-5.messagelabs.com id FA/6B-14717-D29F6605; Sat, 29 Sep 2012 13:35:41 +0000 X-Env-Sender: singapore.mr.teo.en.ming@gmail.com X-Msg-Ref: server-4.tower-182.messagelabs.com!1348925737!28139902!1 X-Originating-IP: [209.85.160.45] X-SpamReason: No, hits=0.3 required=7.0 tests=ML_RADAR_SPEW_LINKS_14, RCVD_BY_IP,spamassassin: X-StarScan-Received: X-StarScan-Version: 6.6.1.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 2075 invoked from network); 29 Sep 2012 13:35:39 -0000 Received: from mail-pb0-f45.google.com (HELO mail-pb0-f45.google.com) (209.85.160.45) by server-4.tower-182.messagelabs.com with RC4-SHA encrypted SMTP; 29 Sep 2012 13:35:39 -0000 Received: by pbbrp2 with SMTP id rp2so6423640pbb.32 for ; Sat, 29 Sep 2012 06:35:36 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:disposition-notification-to:date:from:user-agent :mime-version:to:subject:content-type:content-transfer-encoding; bh=roq+N0SaNSCE4iHI+O8aEU6GO7nWvPPVS6aptdRFR4c=; b=bmZeYZnP8aiSQoa510kkAxRi0iXhgcmF4OpcURuFn8sSP4texx6q9hDuLCLKL7jjOM tiyQoA5LuVfH/RbT6hg3sUHvDFbnGq4qhwTQVVpFTPu+yEJUb2swWfM/JPdy/5CZ5xdO LHuUd+WLrwxLqoJupTwfi/F5L6/ATvXoSMuyW13ILC0ocPRVRYHlaXN9UGmeJj4EHQJD g+7Sw133m3pDm248IVdVTA/uek98nC8eWs6YsD8oFA4B7iSqq0w51N7F1Ro9dPYkqUCm HTuWDj6iEJpaGzeH/jnPEj0liKN2NGgbTmsmRVrPLI3KwJXDK6U+Qfjw6eH+/OJEceXS fcdA== Received: by 10.66.88.198 with SMTP id bi6mr24575918pab.23.1348925734243; Sat, 29 Sep 2012 06:35:34 -0700 (PDT) Received: from [192.168.1.2] (cm152.gamma205.maxonline.com.sg. [202.156.205.152]) by mx.google.com with ESMTPS id qa4sm7228355pbb.70.2012.09.29.06.35.31 (version=SSLv3 cipher=OTHER); Sat, 29 Sep 2012 06:35:33 -0700 (PDT) Message-ID: <5066F922.1090305@gmail.com> Date: Sat, 29 Sep 2012 21:35:30 +0800 From: "Teo En Ming (Zhang Enming)" User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:15.0) Gecko/20120912 Thunderbird/15.0.1 MIME-Version: 1.0 To: "xen-users@lists.xen.org" , "xen-devel@lists.xen.org" , "Teo En Ming (Zhang Enming)" Subject: [Xen-users] Unable to start Windows 8 HVM guest with Xen VGA Passthrough with Xen 4.2.1-pre X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset="us-ascii"; Format="flowed" Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org Hi, I have applied Xen VGA passthrough patches from David Techer's personal website to Xen 4.2.1-pre source tree. Everything compiled and installed smoothly. But when I tried to start Windows 8 HVM domU with VGA passthrough, it gave me the following error: xc: error: unable to allocate memory to the HVM guest. (16: device or resource busy): Internal error. There are no issues with Xen 4.2-unstable changeset 25099 however. -- Yours sincerely, Mr. Teo En Ming (Zhang Enming) Singapore _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Sat Sep 29 13:37:10 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Sat, 29 Sep 2012 13:37:10 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1THxCq-000894-3X; Sat, 29 Sep 2012 13:35:44 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1THxCo-00088o-Ni for xen-users@lists.xen.org; Sat, 29 Sep 2012 13:35:42 +0000 Received: from [85.158.139.83:26977] by server-6.bemta-5.messagelabs.com id FA/6B-14717-D29F6605; Sat, 29 Sep 2012 13:35:41 +0000 X-Env-Sender: singapore.mr.teo.en.ming@gmail.com X-Msg-Ref: server-4.tower-182.messagelabs.com!1348925737!28139902!1 X-Originating-IP: [209.85.160.45] X-SpamReason: No, hits=0.3 required=7.0 tests=ML_RADAR_SPEW_LINKS_14, RCVD_BY_IP,spamassassin: X-StarScan-Received: X-StarScan-Version: 6.6.1.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 2075 invoked from network); 29 Sep 2012 13:35:39 -0000 Received: from mail-pb0-f45.google.com (HELO mail-pb0-f45.google.com) (209.85.160.45) by server-4.tower-182.messagelabs.com with RC4-SHA encrypted SMTP; 29 Sep 2012 13:35:39 -0000 Received: by pbbrp2 with SMTP id rp2so6423640pbb.32 for ; Sat, 29 Sep 2012 06:35:36 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:disposition-notification-to:date:from:user-agent :mime-version:to:subject:content-type:content-transfer-encoding; bh=roq+N0SaNSCE4iHI+O8aEU6GO7nWvPPVS6aptdRFR4c=; b=bmZeYZnP8aiSQoa510kkAxRi0iXhgcmF4OpcURuFn8sSP4texx6q9hDuLCLKL7jjOM tiyQoA5LuVfH/RbT6hg3sUHvDFbnGq4qhwTQVVpFTPu+yEJUb2swWfM/JPdy/5CZ5xdO LHuUd+WLrwxLqoJupTwfi/F5L6/ATvXoSMuyW13ILC0ocPRVRYHlaXN9UGmeJj4EHQJD g+7Sw133m3pDm248IVdVTA/uek98nC8eWs6YsD8oFA4B7iSqq0w51N7F1Ro9dPYkqUCm HTuWDj6iEJpaGzeH/jnPEj0liKN2NGgbTmsmRVrPLI3KwJXDK6U+Qfjw6eH+/OJEceXS fcdA== Received: by 10.66.88.198 with SMTP id bi6mr24575918pab.23.1348925734243; Sat, 29 Sep 2012 06:35:34 -0700 (PDT) Received: from [192.168.1.2] (cm152.gamma205.maxonline.com.sg. [202.156.205.152]) by mx.google.com with ESMTPS id qa4sm7228355pbb.70.2012.09.29.06.35.31 (version=SSLv3 cipher=OTHER); Sat, 29 Sep 2012 06:35:33 -0700 (PDT) Message-ID: <5066F922.1090305@gmail.com> Date: Sat, 29 Sep 2012 21:35:30 +0800 From: "Teo En Ming (Zhang Enming)" User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:15.0) Gecko/20120912 Thunderbird/15.0.1 MIME-Version: 1.0 To: "xen-users@lists.xen.org" , "xen-devel@lists.xen.org" , "Teo En Ming (Zhang Enming)" Subject: [Xen-users] Unable to start Windows 8 HVM guest with Xen VGA Passthrough with Xen 4.2.1-pre X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset="us-ascii"; Format="flowed" Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org Hi, I have applied Xen VGA passthrough patches from David Techer's personal website to Xen 4.2.1-pre source tree. Everything compiled and installed smoothly. But when I tried to start Windows 8 HVM domU with VGA passthrough, it gave me the following error: xc: error: unable to allocate memory to the HVM guest. (16: device or resource busy): Internal error. There are no issues with Xen 4.2-unstable changeset 25099 however. -- Yours sincerely, Mr. Teo En Ming (Zhang Enming) Singapore _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Sat Sep 29 13:37:59 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Sat, 29 Sep 2012 13:37:59 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1THxDx-0008Fp-Qk; Sat, 29 Sep 2012 13:36:53 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1THxDw-0008FT-4j for xen-users@lists.xen.org; Sat, 29 Sep 2012 13:36:52 +0000 Received: from [85.158.139.83:52955] by server-15.bemta-5.messagelabs.com id EF/13-19430-379F6605; Sat, 29 Sep 2012 13:36:51 +0000 X-Env-Sender: singapore.mr.teo.en.ming@gmail.com X-Msg-Ref: server-10.tower-182.messagelabs.com!1348925808!32948472!1 X-Originating-IP: [209.85.220.45] X-SpamReason: No, hits=0.3 required=7.0 tests=ML_RADAR_SPEW_LINKS_14, RCVD_BY_IP,spamassassin: X-StarScan-Received: X-StarScan-Version: 6.6.1.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 24605 invoked from network); 29 Sep 2012 13:36:50 -0000 Received: from mail-pa0-f45.google.com (HELO mail-pa0-f45.google.com) (209.85.220.45) by server-10.tower-182.messagelabs.com with RC4-SHA encrypted SMTP; 29 Sep 2012 13:36:50 -0000 Received: by padfb10 with SMTP id fb10so3088859pad.32 for ; Sat, 29 Sep 2012 06:36:48 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:user-agent:mime-version:to:cc:subject :references:in-reply-to:content-type:content-transfer-encoding; bh=MJ65bg5sNEV0fpmXDCws5BnmFRHUCY93U3xFHyX6Xz4=; b=vC3boORDPq0+6GsOvnnmxVXaMKFo0JYndWuZAIAesh6meKbe4L1ipvdJD+takhYf/C UyeL9tuLE1SNHODdP0F+ih8oSQKwyIpzPFVUxOLYUCsy2G8QCCkhM6aFdO0FbKuxJbxb hvMJDkaM7wPj2SSvWyBtV1Lhme8IThcCICOvVzCOldlTCyeVnkMRpyqk28deogvfxu8J vMmmmZDfrVjSWqCRqYrm1yoTDCZvoZjpFGRZwsiYOk9J+r2+xYRVg0pmKMyHWyazpnqy Z73et+BF/HEjS1Xx+PIPW+1LYEMnVgjXbS0npIX5U5K9n9TYQ5LsoelqpdpVqxOnBpxT eQLg== Received: by 10.68.136.229 with SMTP id qd5mr27820106pbb.154.1348925808182; Sat, 29 Sep 2012 06:36:48 -0700 (PDT) Received: from [192.168.1.2] (cm152.gamma205.maxonline.com.sg. [202.156.205.152]) by mx.google.com with ESMTPS id it5sm7245077pbc.10.2012.09.29.06.36.46 (version=SSLv3 cipher=OTHER); Sat, 29 Sep 2012 06:36:47 -0700 (PDT) Message-ID: <5066F96C.1070908@gmail.com> Date: Sat, 29 Sep 2012 21:36:44 +0800 From: "Teo En Ming (Zhang Enming)" User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:15.0) Gecko/20120912 Thunderbird/15.0.1 MIME-Version: 1.0 To: "Teo En Ming (Zhang Enming)" References: , <50645166.2000200@gmail.com> <50647B26.9080903@gmail.com>, , <50648CEA.9070107@gmail.com> , <5066CE0D.9080402@gmail.com> In-Reply-To: <5066CE0D.9080402@gmail.com> Cc: "xen-users@lists.xen.org" , Mike Viau Subject: Re: [Xen-users] Success VGA passthrough on windows 7 x64 with Xen 4.2.1-pre X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset="us-ascii"; Format="flowed" Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org On 29/09/2012 18:31, Teo En Ming (Zhang Enming) wrote: > On 28/09/2012 08:01, Mike Viau wrote: >> >>> On Thu, 27 Sep 2012 20:34:54 +0200 wrote: >>> >>>> 2012/9/27 Mike Viau : >>>> >>>>> On Fri, 28 Sep 2012 01:29:14 +0800 >>>>> wrote: >>>>> >>>>> Dear Dariusz Krempa, >>>>> >>>>> Thank you for your prompt reply. >>>>> >>>>> I don't have pci_msitranslate = 1 in my Windows HVM domU config >>>>> file, so >>>>> I don't think "pci_msitranslate = 1" is the main cause of my "nasty >>>>> yellow triangle with error 43". >>>>> >>>> I once recorded that the default for the pci_msitranslate option >>>> was "1". Not having this in your configuration then is like having >>>> it set. Feel free to correct me if I am wrong. I have only gotten >>>> VGA pass-through to work with a Windows domU, never in GNU/Linux >>>> for some reason. >>>> >>>> >>>> -M >>> from change set 25525 msitranslate is 0 by deafault >>> >>> http://xenbits.xensource.com/hg/staging/xen-unstable.hg/rev/84272cca638a?revcount=120 >>> >>> >> Thanks for this information, it was much appreciated! I will be >> updating my notes accordingly. >> >> -M >> >> _______________________________________________ >> Xen-users mailing list >> Xen-users@lists.xen.org >> http://lists.xen.org/xen-users >> > > Dear Dariusz Krempa, > > Could you publish your xen vga passthrough configuration files, namely > the windows 7 x64 HVM domU configuration file? > > I have tried setting pci_msitranslate to 1 and also 0 but the nasty > yellow triangle with an exclamation mark and error 43 won't go away. > pci_msitranslate has no effect on my system. > > Thank you very much. > Hi, I have applied Xen VGA passthrough patches from David Techer's personal website to Xen 4.2.1-pre source tree. Everything compiled and installed smoothly. But when I tried to start Windows 8 HVM domU with VGA passthrough, it gave me the following error: xc: error: unable to allocate memory to the HVM guest. (16: device or resource busy): Internal error. There are no issues with Xen 4.2-unstable changeset 25099 however. -- Yours sincerely, Mr. Teo En Ming (Zhang Enming) Singapore _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Sat Sep 29 13:37:59 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Sat, 29 Sep 2012 13:37:59 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1THxDx-0008Fp-Qk; Sat, 29 Sep 2012 13:36:53 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1THxDw-0008FT-4j for xen-users@lists.xen.org; Sat, 29 Sep 2012 13:36:52 +0000 Received: from [85.158.139.83:52955] by server-15.bemta-5.messagelabs.com id EF/13-19430-379F6605; Sat, 29 Sep 2012 13:36:51 +0000 X-Env-Sender: singapore.mr.teo.en.ming@gmail.com X-Msg-Ref: server-10.tower-182.messagelabs.com!1348925808!32948472!1 X-Originating-IP: [209.85.220.45] X-SpamReason: No, hits=0.3 required=7.0 tests=ML_RADAR_SPEW_LINKS_14, RCVD_BY_IP,spamassassin: X-StarScan-Received: X-StarScan-Version: 6.6.1.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 24605 invoked from network); 29 Sep 2012 13:36:50 -0000 Received: from mail-pa0-f45.google.com (HELO mail-pa0-f45.google.com) (209.85.220.45) by server-10.tower-182.messagelabs.com with RC4-SHA encrypted SMTP; 29 Sep 2012 13:36:50 -0000 Received: by padfb10 with SMTP id fb10so3088859pad.32 for ; Sat, 29 Sep 2012 06:36:48 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:user-agent:mime-version:to:cc:subject :references:in-reply-to:content-type:content-transfer-encoding; bh=MJ65bg5sNEV0fpmXDCws5BnmFRHUCY93U3xFHyX6Xz4=; b=vC3boORDPq0+6GsOvnnmxVXaMKFo0JYndWuZAIAesh6meKbe4L1ipvdJD+takhYf/C UyeL9tuLE1SNHODdP0F+ih8oSQKwyIpzPFVUxOLYUCsy2G8QCCkhM6aFdO0FbKuxJbxb hvMJDkaM7wPj2SSvWyBtV1Lhme8IThcCICOvVzCOldlTCyeVnkMRpyqk28deogvfxu8J vMmmmZDfrVjSWqCRqYrm1yoTDCZvoZjpFGRZwsiYOk9J+r2+xYRVg0pmKMyHWyazpnqy Z73et+BF/HEjS1Xx+PIPW+1LYEMnVgjXbS0npIX5U5K9n9TYQ5LsoelqpdpVqxOnBpxT eQLg== Received: by 10.68.136.229 with SMTP id qd5mr27820106pbb.154.1348925808182; Sat, 29 Sep 2012 06:36:48 -0700 (PDT) Received: from [192.168.1.2] (cm152.gamma205.maxonline.com.sg. [202.156.205.152]) by mx.google.com with ESMTPS id it5sm7245077pbc.10.2012.09.29.06.36.46 (version=SSLv3 cipher=OTHER); Sat, 29 Sep 2012 06:36:47 -0700 (PDT) Message-ID: <5066F96C.1070908@gmail.com> Date: Sat, 29 Sep 2012 21:36:44 +0800 From: "Teo En Ming (Zhang Enming)" User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:15.0) Gecko/20120912 Thunderbird/15.0.1 MIME-Version: 1.0 To: "Teo En Ming (Zhang Enming)" References: , <50645166.2000200@gmail.com> <50647B26.9080903@gmail.com>, , <50648CEA.9070107@gmail.com> , <5066CE0D.9080402@gmail.com> In-Reply-To: <5066CE0D.9080402@gmail.com> Cc: "xen-users@lists.xen.org" , Mike Viau Subject: Re: [Xen-users] Success VGA passthrough on windows 7 x64 with Xen 4.2.1-pre X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset="us-ascii"; Format="flowed" Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org On 29/09/2012 18:31, Teo En Ming (Zhang Enming) wrote: > On 28/09/2012 08:01, Mike Viau wrote: >> >>> On Thu, 27 Sep 2012 20:34:54 +0200 wrote: >>> >>>> 2012/9/27 Mike Viau : >>>> >>>>> On Fri, 28 Sep 2012 01:29:14 +0800 >>>>> wrote: >>>>> >>>>> Dear Dariusz Krempa, >>>>> >>>>> Thank you for your prompt reply. >>>>> >>>>> I don't have pci_msitranslate = 1 in my Windows HVM domU config >>>>> file, so >>>>> I don't think "pci_msitranslate = 1" is the main cause of my "nasty >>>>> yellow triangle with error 43". >>>>> >>>> I once recorded that the default for the pci_msitranslate option >>>> was "1". Not having this in your configuration then is like having >>>> it set. Feel free to correct me if I am wrong. I have only gotten >>>> VGA pass-through to work with a Windows domU, never in GNU/Linux >>>> for some reason. >>>> >>>> >>>> -M >>> from change set 25525 msitranslate is 0 by deafault >>> >>> http://xenbits.xensource.com/hg/staging/xen-unstable.hg/rev/84272cca638a?revcount=120 >>> >>> >> Thanks for this information, it was much appreciated! I will be >> updating my notes accordingly. >> >> -M >> >> _______________________________________________ >> Xen-users mailing list >> Xen-users@lists.xen.org >> http://lists.xen.org/xen-users >> > > Dear Dariusz Krempa, > > Could you publish your xen vga passthrough configuration files, namely > the windows 7 x64 HVM domU configuration file? > > I have tried setting pci_msitranslate to 1 and also 0 but the nasty > yellow triangle with an exclamation mark and error 43 won't go away. > pci_msitranslate has no effect on my system. > > Thank you very much. > Hi, I have applied Xen VGA passthrough patches from David Techer's personal website to Xen 4.2.1-pre source tree. Everything compiled and installed smoothly. But when I tried to start Windows 8 HVM domU with VGA passthrough, it gave me the following error: xc: error: unable to allocate memory to the HVM guest. (16: device or resource busy): Internal error. There are no issues with Xen 4.2-unstable changeset 25099 however. -- Yours sincerely, Mr. Teo En Ming (Zhang Enming) Singapore _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Sat Sep 29 15:11:50 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Sat, 29 Sep 2012 15:11:50 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1THygj-00012c-IF; Sat, 29 Sep 2012 15:10:41 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1THygh-00012X-Si for xen-users@lists.xen.org; Sat, 29 Sep 2012 15:10:40 +0000 Received: from [85.158.139.211:36864] by server-13.bemta-5.messagelabs.com id 15/58-16359-F6F07605; Sat, 29 Sep 2012 15:10:39 +0000 X-Env-Sender: david.escott@gmail.com X-Msg-Ref: server-4.tower-206.messagelabs.com!1348931438!20453174!1 X-Originating-IP: [74.125.82.173] X-SpamReason: No, hits=0.3 required=7.0 tests=RCVD_BY_IP X-StarScan-Received: X-StarScan-Version: 6.6.1.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 21240 invoked from network); 29 Sep 2012 15:10:38 -0000 Received: from mail-we0-f173.google.com (HELO mail-we0-f173.google.com) (74.125.82.173) by server-4.tower-206.messagelabs.com with RC4-SHA encrypted SMTP; 29 Sep 2012 15:10:38 -0000 Received: by weyt11 with SMTP id t11so2408203wey.32 for ; Sat, 29 Sep 2012 08:10:38 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:from:date:x-google-sender-auth:message-id :subject:to:content-type; bh=/2rxy7Lye4kh40Ie+TAAvQnQajkuQruRxwzaxUIzKYw=; b=XNTFn7ytYijiNZvEm0psXPwNQ14E4YYLz2wFUkauS7pOiVgYmw/iK4toQhEP06SHYL N65u0fYSaxlaQdbVYMytI3ybudnDbA7fjW2eTSw/IoTDEzf2WX5lWkFP9P9RA5K/60hX EtemWnClDLcWwn1cZ0uOFQ1gmShXUat6PvxoQ7XZVEx/2TaAiXT3qNfDrJofi2z+St3r pRSLSXT8zFh1WnMusFuG87c3Bvvzd+hjE1YR2CM+vmPZQ+tlThlKGxzKybrANcJ3hZ92 L7lTtNKjujDM0m+xgiWjqBgIuhx0GHv/J8D2DXWk+PdJ8mn5xHMbcE16fCrFYheWNTIN wo1Q== Received: by 10.180.79.69 with SMTP id h5mr4132245wix.6.1348931438485; Sat, 29 Sep 2012 08:10:38 -0700 (PDT) MIME-Version: 1.0 Received: by 10.216.211.207 with HTTP; Sat, 29 Sep 2012 08:10:18 -0700 (PDT) From: David Escott Date: Sat, 29 Sep 2012 11:10:18 -0400 X-Google-Sender-Auth: uwChSx1uWdukCvrimdzT54MU85w Message-ID: To: xen-users@lists.xen.org Subject: [Xen-users] PCI Passthrough X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org I've been playing around with doing PCI passthrough of Radeon cards and have had some success. Under Fedora 17 (stock everything) I was able to passthrough an older RADEON 2600XT to a Windows7 domU. However when I try the same with a new RADEON 7850 I get a "not enough resources" error from the Windows guest. I'm not sure what the next steps are, it seems from blog postings and howtos that people are just trying things at random, and I don't understand what the debugging process is. Any advice on what the next steps are? Should I move to an OS that will have a newer XEN or is there some configuration file I should be editing? Thanks, David _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Sat Sep 29 15:11:50 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Sat, 29 Sep 2012 15:11:50 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1THygj-00012c-IF; Sat, 29 Sep 2012 15:10:41 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1THygh-00012X-Si for xen-users@lists.xen.org; Sat, 29 Sep 2012 15:10:40 +0000 Received: from [85.158.139.211:36864] by server-13.bemta-5.messagelabs.com id 15/58-16359-F6F07605; Sat, 29 Sep 2012 15:10:39 +0000 X-Env-Sender: david.escott@gmail.com X-Msg-Ref: server-4.tower-206.messagelabs.com!1348931438!20453174!1 X-Originating-IP: [74.125.82.173] X-SpamReason: No, hits=0.3 required=7.0 tests=RCVD_BY_IP X-StarScan-Received: X-StarScan-Version: 6.6.1.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 21240 invoked from network); 29 Sep 2012 15:10:38 -0000 Received: from mail-we0-f173.google.com (HELO mail-we0-f173.google.com) (74.125.82.173) by server-4.tower-206.messagelabs.com with RC4-SHA encrypted SMTP; 29 Sep 2012 15:10:38 -0000 Received: by weyt11 with SMTP id t11so2408203wey.32 for ; Sat, 29 Sep 2012 08:10:38 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:from:date:x-google-sender-auth:message-id :subject:to:content-type; bh=/2rxy7Lye4kh40Ie+TAAvQnQajkuQruRxwzaxUIzKYw=; b=XNTFn7ytYijiNZvEm0psXPwNQ14E4YYLz2wFUkauS7pOiVgYmw/iK4toQhEP06SHYL N65u0fYSaxlaQdbVYMytI3ybudnDbA7fjW2eTSw/IoTDEzf2WX5lWkFP9P9RA5K/60hX EtemWnClDLcWwn1cZ0uOFQ1gmShXUat6PvxoQ7XZVEx/2TaAiXT3qNfDrJofi2z+St3r pRSLSXT8zFh1WnMusFuG87c3Bvvzd+hjE1YR2CM+vmPZQ+tlThlKGxzKybrANcJ3hZ92 L7lTtNKjujDM0m+xgiWjqBgIuhx0GHv/J8D2DXWk+PdJ8mn5xHMbcE16fCrFYheWNTIN wo1Q== Received: by 10.180.79.69 with SMTP id h5mr4132245wix.6.1348931438485; Sat, 29 Sep 2012 08:10:38 -0700 (PDT) MIME-Version: 1.0 Received: by 10.216.211.207 with HTTP; Sat, 29 Sep 2012 08:10:18 -0700 (PDT) From: David Escott Date: Sat, 29 Sep 2012 11:10:18 -0400 X-Google-Sender-Auth: uwChSx1uWdukCvrimdzT54MU85w Message-ID: To: xen-users@lists.xen.org Subject: [Xen-users] PCI Passthrough X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org I've been playing around with doing PCI passthrough of Radeon cards and have had some success. Under Fedora 17 (stock everything) I was able to passthrough an older RADEON 2600XT to a Windows7 domU. However when I try the same with a new RADEON 7850 I get a "not enough resources" error from the Windows guest. I'm not sure what the next steps are, it seems from blog postings and howtos that people are just trying things at random, and I don't understand what the debugging process is. Any advice on what the next steps are? Should I move to an OS that will have a newer XEN or is there some configuration file I should be editing? Thanks, David _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users From xen-users-bounces@lists.xen.org Sat Sep 29 15:14:19 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Sat, 29 Sep 2012 15:14:19 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1THyjB-0001BO-Bg; Sat, 29 Sep 2012 15:13:13 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1THyjA-0001B3-DH for xen-users@lists.xensource.com; Sat, 29 Sep 2012 15:13:12 +0000 Received: from [85.158.143.35:27723] by server-3.bemta-4.messagelabs.com id B7/E7-10986-70017605; Sat, 29 Sep 2012 15:13:11 +0000 X-Env-Sender: mrsanna1@gmail.com X-Msg-Ref: server-7.tower-21.messagelabs.com!1348931588!11744757!1 X-Originating-IP: [209.85.220.171] X-SpamReason: No, hits=0.3 required=7.0 tests=ML_RADAR_SPEW_LINKS_14, RCVD_BY_IP,spamassassin: X-StarScan-Received: X-StarScan-Version: 6.6.1.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 27180 invoked from network); 29 Sep 2012 15:13:09 -0000 Received: from mail-vc0-f171.google.com (HELO mail-vc0-f171.google.com) (209.85.220.171) by server-7.tower-21.messagelabs.com with RC4-SHA encrypted SMTP; 29 Sep 2012 15:13:09 -0000 Received: by vcmm18 with SMTP id m18so5474568vcm.30 for ; Sat, 29 Sep 2012 08:13:08 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; bh=GJiiKciB+AW37QQALJh016YNCl54lMppdyoHlLSf/tQ=; b=JUgB0qFqU0I+knq9Oe3VFqvKiTWGPRoZPQ4eRFHCBH4JvldommXTftJE8BMYFXoUbJ +BVssQv2u5R1sPKUOxuca0bCwkKzzanvQb0eKc9K3h2L8urpSp1Xw6VGdPFuSsTgErfZ GTKjuOR540yKSP17bl4hQI6n3ulg0BA8x7eLOsTRY3hRmNhJ3l2nzsHVDHb4HjPJHGwr +4bHDRNzT/Lrxp9stvVztDWcp0U8UAfhK7+a6PaNqLz03jD1Al/TI9s9bBxAjMzJl463 gr5VQId+czj+Kc05V+7/qSeapWSC3GzbxLsB9zmS1VK41+snGoOGFQ9sIpaFlBGUxnsd UtIA== MIME-Version: 1.0 Received: by 10.220.205.200 with SMTP id fr8mr5652534vcb.34.1348931588463; Sat, 29 Sep 2012 08:13:08 -0700 (PDT) Received: by 10.58.207.75 with HTTP; Sat, 29 Sep 2012 08:13:08 -0700 (PDT) In-Reply-To: References: <4D655A39.2040501@gmail.com> Date: Sat, 29 Sep 2012 17:13:08 +0200 Message-ID: From: Mauro To: Keir Fraser Cc: Dan Magenheimer , xen-devel@lists.xensource.com, Jeremy Fitzhardinge , Olivier Hanesse , Xen Users , Mark Adams Subject: Re: [Xen-users] [Xen-devel] Xen 4 TSC problems X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: base64 Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org T24gMjQgRmVicnVhcnkgMjAxMSAwODoxNiwgS2VpciBGcmFzZXIgPGtlaXIueGVuQGdtYWlsLmNv bT4gd3JvdGU6Cj4gUGxlYXNlIHNlbmQgWGVuIGJvb3Qgb3V0cHV0ICh4bSBkbWVzZykuIEdldHRp bmcgaXQgZnJvbSBYZW4gMy4yIGFzIHdlbGwKPiB3b3VsZCBiZSBpbnRlcmVzdGluZywgaWYgeW91 IHN0aWxsIGhhdmUgaXQgaW5zdGFsbGVkIG9uIGFueSBvZiB0aGVzZQo+IG1hY2hpbmVzLgoKSWYg aXQgY2FuIGJlIHVzZWZ1bCBoZXJlIGlzIHhtIGRtZXNmIG9mIHhlbiA0LjAgb24gYSBkZWJpYW4g c3F1ZWV6ZSBzeXN0ZW06CgooWEVOKSBYZW4gdmVyc2lvbiA0LjAuMSAoRGViaWFuIDQuMC4xLTUu NCkgKHVsdHJvdHRlckBkZWJpYW4ub3JnKSAoZ2NjCnZlcnNpb24gNC40LjUgKERlYmlhbiA0LjQu NS04KSApIFNhdCBTZXAgIDggMTk6MTU6NDYgVVRDIDIwMTIKKFhFTikgQm9vdGxvYWRlcjogR1JV QiAxLjk4KzIwMTAwODA0LTE0K3NxdWVlemUxCihYRU4pIENvbW1hbmQgbGluZTogcGxhY2Vob2xk ZXIgZG9tMF9tZW09MzA3Mk0gbG9nbHZsPXdhcm5pbmcKZ3Vlc3RfbG9nbHZsPXdhcm5pbmcKKFhF TikgVmlkZW8gaW5mb3JtYXRpb246CihYRU4pICBWR0EgaXMgdGV4dCBtb2RlIDgweDI1LCBmb250 IDh4MTYKKFhFTikgIFZCRS9EREMgbWV0aG9kczogVjI7IEVESUQgdHJhbnNmZXIgdGltZTogMiBz ZWNvbmRzCihYRU4pIERpc2MgaW5mb3JtYXRpb246CihYRU4pICBGb3VuZCAyIE1CUiBzaWduYXR1 cmVzCihYRU4pICBGb3VuZCAyIEVERCBpbmZvcm1hdGlvbiBzdHJ1Y3R1cmVzCihYRU4pIFhlbi1l ODIwIFJBTSBtYXA6CihYRU4pICAwMDAwMDAwMDAwMDAwMDAwIC0gMDAwMDAwMDAwMDA5ZjQwMCAo dXNhYmxlKQooWEVOKSAgMDAwMDAwMDAwMDA5ZjQwMCAtIDAwMDAwMDAwMDAwYTAwMDAgKHJlc2Vy dmVkKQooWEVOKSAgMDAwMDAwMDAwMDBmMDAwMCAtIDAwMDAwMDAwMDAxMDAwMDAgKHJlc2VydmVk KQooWEVOKSAgMDAwMDAwMDAwMDEwMDAwMCAtIDAwMDAwMDAwY2ZkNDMwMDAgKHVzYWJsZSkKKFhF TikgIDAwMDAwMDAwY2ZkNDMwMDAgLSAwMDAwMDAwMGNmZDRjMDAwIChBQ1BJIGRhdGEpCihYRU4p ICAwMDAwMDAwMGNmZDRjMDAwIC0gMDAwMDAwMDBjZmQ0ZDAwMCAodXNhYmxlKQooWEVOKSAgMDAw MDAwMDBjZmQ0ZDAwMCAtIDAwMDAwMDAwZDAwMDAwMDAgKHJlc2VydmVkKQooWEVOKSAgMDAwMDAw MDBlMDAwMDAwMCAtIDAwMDAwMDAwZjAwMDAwMDAgKHJlc2VydmVkKQooWEVOKSAgMDAwMDAwMDBm ZWMwMDAwMCAtIDAwMDAwMDAwZmVkMDAwMDAgKHJlc2VydmVkKQooWEVOKSAgMDAwMDAwMDBmZWUw MDAwMCAtIDAwMDAwMDAwZmVlMTAwMDAgKHJlc2VydmVkKQooWEVOKSAgMDAwMDAwMDBmZmMwMDAw MCAtIDAwMDAwMDAxMDAwMDAwMDAgKHJlc2VydmVkKQooWEVOKSAgMDAwMDAwMDEwMDAwMDAwMCAt IDAwMDAwMDEwMmZmZmYwMDAgKHVzYWJsZSkKKFhFTikgQUNQSTogUlNEUCAwMDBGNEYyMCwgMDAy NCAocjIgSFAgICAgKQooWEVOKSBBQ1BJOiBYU0RUIENGRDQzOTAwLCAwMDdDIChyMSBIUCAgICAg UHJvTGlhbnQgICAgICAgIDIgICDvv70gICAgIDE2MkUpCihYRU4pIEFDUEk6IEZBQ1AgQ0ZENDM5 QzAsIDAwRjQgKHIzIEhQICAgICBQcm9MaWFudCAgICAgICAgMiAgIO+/vSAgICAgMTYyRSkKKFhF TikgQUNQSTogRFNEVCBDRkQ0M0FDMCwgMzBDOSAocjEgSFAgICAgICAgICBEU0RUICAgICAgICAx IElOVEwgMjAwMzAyMjgpCihYRU4pIEFDUEk6IEZBQ1MgQ0ZENDMxMDAsIDAwNDAKKFhFTikgQUNQ STogU1BDUiBDRkQ0MzE0MCwgMDA1MCAocjEgSFAgICAgIFNQQ1JSQlNVICAgICAgICAxICAg77+9 ICAgICAxNjJFKQooWEVOKSBBQ1BJOiBNQ0ZHIENGRDQzMUMwLCAwMDNDIChyMSBIUCAgICAgUHJv TGlhbnQgICAgICAgIDEgICAgICAgICAgICAgMCkKKFhFTikgQUNQSTogSFBFVCBDRkQ0MzIwMCwg MDAzOCAocjEgSFAgICAgIFByb0xpYW50ICAgICAgICAyICAg77+9ICAgICAxNjJFKQooWEVOKSBB Q1BJOiBGRkZGIENGRDQzMjQwLCAwMDY0IChyMiBIUCAgICAgUDYxICAgICAgICAgICAgIDIgICDv v70gICAgIDE2MkUpCihYRU4pIEFDUEk6IFNQTUkgQ0ZENDMyQzAsIDAwNDAgKHI1IEhQICAgICBQ cm9MaWFudCAgICAgICAgMSAgIO+/vSAgICAgMTYyRSkKKFhFTikgQUNQSTogRVJTVCBDRkQ0MzMw MCwgMDFEMCAocjEgSFAgICAgIFByb0xpYW50ICAgICAgICAxICAg77+9ICAgICAxNjJFKQooWEVO KSBBQ1BJOiBBUElDIENGRDQzNTAwLCAwMTc2IChyMSBIUCAgICAgUHJvTGlhbnQgICAgICAgIDIg ICAgICAgICAgICAgMCkKKFhFTikgQUNQSTogRkZGRiBDRkQ0MzY4MCwgMDE3NiAocjEgSFAgICAg IFByb0xpYW50ICAgICAgICAxICAg77+9ICAgICAxNjJFKQooWEVOKSBBQ1BJOiBCRVJUIENGRDQz ODAwLCAwMDMwIChyMSBIUCAgICAgUHJvTGlhbnQgICAgICAgIDEgICDvv70gICAgIDE2MkUpCihY RU4pIEFDUEk6IEhFU1QgQ0ZENDM4NDAsIDAwQkMgKHIxIEhQICAgICBQcm9MaWFudCAgICAgICAg MSAgIO+/vSAgICAgMTYyRSkKKFhFTikgU3lzdGVtIFJBTTogNjU1MzJNQiAoNjcxMDU2NzJrQikK KFhFTikgRG9tYWluIGhlYXAgaW5pdGlhbGlzZWQKKFhFTikgUHJvY2Vzc29yICMwIDY6MTUgQVBJ QyB2ZXJzaW9uIDIwCihYRU4pIFByb2Nlc3NvciAjOCA2OjE1IEFQSUMgdmVyc2lvbiAyMAooWEVO KSBQcm9jZXNzb3IgIzE2IDY6MTUgQVBJQyB2ZXJzaW9uIDIwCihYRU4pIFByb2Nlc3NvciAjMjQg NjoxNSBBUElDIHZlcnNpb24gMjAKKFhFTikgUHJvY2Vzc29yICMxIDY6MTUgQVBJQyB2ZXJzaW9u IDIwCihYRU4pIFByb2Nlc3NvciAjOSA2OjE1IEFQSUMgdmVyc2lvbiAyMAooWEVOKSBQcm9jZXNz b3IgIzE3IDY6MTUgQVBJQyB2ZXJzaW9uIDIwCihYRU4pIFByb2Nlc3NvciAjMjUgNjoxNSBBUElD IHZlcnNpb24gMjAKKFhFTikgUHJvY2Vzc29yICMyIDY6MTUgQVBJQyB2ZXJzaW9uIDIwCihYRU4p IFByb2Nlc3NvciAjMTAgNjoxNSBBUElDIHZlcnNpb24gMjAKKFhFTikgUHJvY2Vzc29yICMxOCA2 OjE1IEFQSUMgdmVyc2lvbiAyMAooWEVOKSBQcm9jZXNzb3IgIzI2IDY6MTUgQVBJQyB2ZXJzaW9u IDIwCihYRU4pIFByb2Nlc3NvciAjMyA2OjE1IEFQSUMgdmVyc2lvbiAyMAooWEVOKSBQcm9jZXNz b3IgIzExIDY6MTUgQVBJQyB2ZXJzaW9uIDIwCihYRU4pIFByb2Nlc3NvciAjMTkgNjoxNSBBUElD IHZlcnNpb24gMjAKKFhFTikgUHJvY2Vzc29yICMyNyA2OjE1IEFQSUMgdmVyc2lvbiAyMAooWEVO KSBJT0FQSUNbMF06IGFwaWNfaWQgMSwgdmVyc2lvbiAzMiwgYWRkcmVzcyAweGZlYzAwMDAwLCBH U0kgMC0yMwooWEVOKSBJT0FQSUNbMV06IGFwaWNfaWQgMiwgdmVyc2lvbiAzMiwgYWRkcmVzcyAw eGZlYzgwMDAwLCBHU0kgMjQtNDcKKFhFTikgSU9BUElDWzJdOiBhcGljX2lkIDMsIHZlcnNpb24g MzIsIGFkZHJlc3MgMHhmZWM4MTAwMCwgR1NJIDQ4LTcxCihYRU4pIElPQVBJQ1szXTogYXBpY19p ZCA0LCB2ZXJzaW9uIDMyLCBhZGRyZXNzIDB4ZmVjODE4MDAsIEdTSSA3Mi05NQooWEVOKSBFbmFi bGluZyBBUElDIG1vZGU6ICBQaHlzLiAgVXNpbmcgNCBJL08gQVBJQ3MKKFhFTikgVXNpbmcgc2No ZWR1bGVyOiBTTVAgQ3JlZGl0IFNjaGVkdWxlciAoY3JlZGl0KQooWEVOKSBEZXRlY3RlZCAyNDAw LjE0NSBNSHogcHJvY2Vzc29yLgooWEVOKSBJbml0aW5nIG1lbW9yeSBzaGFyaW5nLgooWEVOKSBW TVg6IFN1cHBvcnRlZCBhZHZhbmNlZCBmZWF0dXJlczoKKFhFTikgIC0gQVBJQyBNTUlPIGFjY2Vz cyB2aXJ0dWFsaXNhdGlvbgooWEVOKSAgLSBBUElDIFRQUiBzaGFkb3cKKFhFTikgIC0gVmlydHVh bCBOTUkKKFhFTikgIC0gTVNSIGRpcmVjdC1hY2Nlc3MgYml0bWFwCihYRU4pIEhWTTogQVNJRHMg ZGlzYWJsZWQuCihYRU4pIEhWTTogVk1YIGVuYWJsZWQKKFhFTikgSS9PIHZpcnR1YWxpc2F0aW9u IGRpc2FibGVkCihYRU4pIFRvdGFsIG9mIDE2IHByb2Nlc3NvcnMgYWN0aXZhdGVkLgooWEVOKSBF TkFCTElORyBJTy1BUElDIElSUXMKKFhFTikgIC0+IFVzaW5nIG5ldyBBQ0sgbWV0aG9kCihYRU4p IGNoZWNraW5nIFRTQyBzeW5jaHJvbml6YXRpb24gYWNyb3NzIDE2IENQVXM6IHBhc3NlZC4KKFhF TikgUGxhdGZvcm0gdGltZXIgaXMgMTQuMzE4TUh6IEhQRVQKKFhFTikgQWxsb2NhdGVkIGNvbnNv bGUgcmluZyBvZiAzMiBLaUIuCihYRU4pIEJyb3VnaHQgdXAgMTYgQ1BVcwooWEVOKSAqKiogTE9B RElORyBET01BSU4gMCAqKioKKFhFTikgIFhlbiAga2VybmVsOiA2NC1iaXQsIGxzYiwgY29tcGF0 MzIKKFhFTikgIERvbTAga2VybmVsOiA2NC1iaXQsIFBBRSwgbHNiLCBwYWRkciAweDEwMDAwMDAg LT4gMHgxNzA4MDAwCihYRU4pIFBIWVNJQ0FMIE1FTU9SWSBBUlJBTkdFTUVOVDoKKFhFTikgIERv bTAgYWxsb2MuOiAgIDAwMDAwMDA4M2MwMDAwMDAtPjAwMDAwMDA4NDAwMDAwMDAgKDc3MDA0OCBw YWdlcwp0byBiZSBhbGxvY2F0ZWQpCihYRU4pIFZJUlRVQUwgTUVNT1JZIEFSUkFOR0VNRU5UOgoo WEVOKSAgTG9hZGVkIGtlcm5lbDogZmZmZmZmZmY4MTAwMDAwMC0+ZmZmZmZmZmY4MTcwODAwMAoo WEVOKSAgSW5pdC4gcmFtZGlzazogZmZmZmZmZmY4MTcwODAwMC0+ZmZmZmZmZmY4MWVmYjAwMAoo WEVOKSAgUGh5cy1NYWNoIG1hcDogZmZmZmZmZmY4MWVmYjAwMC0+ZmZmZmZmZmY4MjRmYjAwMAoo WEVOKSAgU3RhcnQgaW5mbzogICAgZmZmZmZmZmY4MjRmYjAwMC0+ZmZmZmZmZmY4MjRmYjRiNAoo WEVOKSAgUGFnZSB0YWJsZXM6ICAgZmZmZmZmZmY4MjRmYzAwMC0+ZmZmZmZmZmY4MjUxMzAwMAoo WEVOKSAgQm9vdCBzdGFjazogICAgZmZmZmZmZmY4MjUxMzAwMC0+ZmZmZmZmZmY4MjUxNDAwMAoo WEVOKSAgVE9UQUw6ICAgICAgICAgZmZmZmZmZmY4MDAwMDAwMC0+ZmZmZmZmZmY4MjgwMDAwMAoo WEVOKSAgRU5UUlkgQUREUkVTUzogZmZmZmZmZmY4MTUzMTIwMAooWEVOKSBEb20wIGhhcyBtYXhp bXVtIDE2IFZDUFVzCihYRU4pIFNjcnViYmluZyBGcmVlIFJBTToKLi4uLi4uLi4uLi4uLi4uLi4u Li4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4u Li4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4u Li4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4u Li4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4u Li4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4u Li4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4u Li4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4u Li4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4u Li4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4u Li4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4u Li4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi5kb25lLgooWEVOKSBYZW4gdHJhY2UgYnVmZmVy czogZGlzYWJsZWQKKFhFTikgU3RkLiBMb2dsZXZlbDogRXJyb3JzIGFuZCB3YXJuaW5ncwooWEVO KSBHdWVzdCBMb2dsZXZlbDogRXJyb3JzIGFuZCB3YXJuaW5ncwooWEVOKSBYZW4gaXMgcmVsaW5x dWlzaGluZyBWR0EgY29uc29sZS4KKFhFTikgKioqIFNlcmlhbCBpbnB1dCAtPiBET00wICh0eXBl ICdDVFJMLWEnIHRocmVlIHRpbWVzIHRvIHN3aXRjaAppbnB1dCB0byBYZW4pCihYRU4pIEZyZWVk IDE3NmtCIGluaXQgbWVtb3J5LgooWEVOKSBQbGF0Zm9ybSB0aW1lciBhcHBlYXJzIHRvIGhhdmUg dW5leHBlY3RlZGx5IHdyYXBwZWQgMTAgb3IgbW9yZSB0aW1lcy4KCgphbmQgaGVyZSBpcyB4bSBk bWVzZyBvZiB4ZW4gMy4yIG9uIGEgZGViaWFuIGxlbm55IHN5c3RlbSBydW5uaW5nIG9uCnRoZSBz YW1lIGhhcmR3YXJlLCBvbiB0aGlzIHN5c3RlbSBJIGRvbid0IGhhdmUgY2xvY2sgcHJvYmxlbXM6 CgooWEVOKSBYZW4gdmVyc2lvbiAzLjItMSAoRGViaWFuIDMuMi4xLTIpICh3YWxkaUBkZWJpYW4u b3JnKSAoZ2NjCnZlcnNpb24gNC4zLjEgKERlYmlhbiA0LjMuMS0yKSApIFNhdCBKdW4gMjggMDk6 MzI6MTggVVRDIDIwMDgKKFhFTikgQ29tbWFuZCBsaW5lOgooWEVOKSBWaWRlbyBpbmZvcm1hdGlv bjoKKFhFTikgIFZHQSBpcyB0ZXh0IG1vZGUgODB4MjUsIGZvbnQgOHgxNgooWEVOKSAgVkJFL0RE QyBtZXRob2RzOiBWMjsgRURJRCB0cmFuc2ZlciB0aW1lOiAyIHNlY29uZHMKKFhFTikgRGlzYyBp bmZvcm1hdGlvbjoKKFhFTikgIEZvdW5kIDIgTUJSIHNpZ25hdHVyZXMKKFhFTikgIEZvdW5kIDIg RUREIGluZm9ybWF0aW9uIHN0cnVjdHVyZXMKKFhFTikgWGVuLWU4MjAgUkFNIG1hcDoKKFhFTikg IDAwMDAwMDAwMDAwMDAwMDAgLSAwMDAwMDAwMDAwMDlmNDAwICh1c2FibGUpCihYRU4pICAwMDAw MDAwMDAwMDlmNDAwIC0gMDAwMDAwMDAwMDBhMDAwMCAocmVzZXJ2ZWQpCihYRU4pICAwMDAwMDAw MDAwMGYwMDAwIC0gMDAwMDAwMDAwMDEwMDAwMCAocmVzZXJ2ZWQpCihYRU4pICAwMDAwMDAwMDAw MTAwMDAwIC0gMDAwMDAwMDBjZmQ0MzAwMCAodXNhYmxlKQooWEVOKSAgMDAwMDAwMDBjZmQ0MzAw MCAtIDAwMDAwMDAwY2ZkNGMwMDAgKEFDUEkgZGF0YSkKKFhFTikgIDAwMDAwMDAwY2ZkNGMwMDAg LSAwMDAwMDAwMGNmZDRkMDAwICh1c2FibGUpCihYRU4pICAwMDAwMDAwMGNmZDRkMDAwIC0gMDAw MDAwMDBkMDAwMDAwMCAocmVzZXJ2ZWQpCihYRU4pICAwMDAwMDAwMGUwMDAwMDAwIC0gMDAwMDAw MDBmMDAwMDAwMCAocmVzZXJ2ZWQpCihYRU4pICAwMDAwMDAwMGZlYzAwMDAwIC0gMDAwMDAwMDBm ZWQwMDAwMCAocmVzZXJ2ZWQpCihYRU4pICAwMDAwMDAwMGZlZTAwMDAwIC0gMDAwMDAwMDBmZWUx MDAwMCAocmVzZXJ2ZWQpCihYRU4pICAwMDAwMDAwMGZmYzAwMDAwIC0gMDAwMDAwMDEwMDAwMDAw MCAocmVzZXJ2ZWQpCihYRU4pICAwMDAwMDAwMTAwMDAwMDAwIC0gMDAwMDAwMGYyZmZmZjAwMCAo dXNhYmxlKQooWEVOKSBTeXN0ZW0gUkFNOiA2MTQzNk1CICg2MjkxMTM2OGtCKQooWEVOKSBYZW4g aGVhcDogMTJNQiAoMTMxMjhrQikKKFhFTikgRG9tYWluIGhlYXAgaW5pdGlhbGlzZWQ6IERNQSB3 aWR0aCAzMiBiaXRzCihYRU4pIFByb2Nlc3NvciAjMCA2OjE1IEFQSUMgdmVyc2lvbiAyMAooWEVO KSBQcm9jZXNzb3IgIzggNjoxNSBBUElDIHZlcnNpb24gMjAKKFhFTikgUHJvY2Vzc29yICMxNiA2 OjE1IEFQSUMgdmVyc2lvbiAyMAooWEVOKSBQcm9jZXNzb3IgIzI0IDY6MTUgQVBJQyB2ZXJzaW9u IDIwCihYRU4pIFByb2Nlc3NvciAjMSA2OjE1IEFQSUMgdmVyc2lvbiAyMAooWEVOKSBQcm9jZXNz b3IgIzkgNjoxNSBBUElDIHZlcnNpb24gMjAKKFhFTikgUHJvY2Vzc29yICMxNyA2OjE1IEFQSUMg dmVyc2lvbiAyMAooWEVOKSBQcm9jZXNzb3IgIzI1IDY6MTUgQVBJQyB2ZXJzaW9uIDIwCihYRU4p IFByb2Nlc3NvciAjMiA2OjE1IEFQSUMgdmVyc2lvbiAyMAooWEVOKSBQcm9jZXNzb3IgIzEwIDY6 MTUgQVBJQyB2ZXJzaW9uIDIwCihYRU4pIFByb2Nlc3NvciAjMTggNjoxNSBBUElDIHZlcnNpb24g MjAKKFhFTikgUHJvY2Vzc29yICMyNiA2OjE1IEFQSUMgdmVyc2lvbiAyMAooWEVOKSBQcm9jZXNz b3IgIzMgNjoxNSBBUElDIHZlcnNpb24gMjAKKFhFTikgUHJvY2Vzc29yICMxMSA2OjE1IEFQSUMg dmVyc2lvbiAyMAooWEVOKSBQcm9jZXNzb3IgIzE5IDY6MTUgQVBJQyB2ZXJzaW9uIDIwCihYRU4p IFByb2Nlc3NvciAjMjcgNjoxNSBBUElDIHZlcnNpb24gMjAKKFhFTikgSU9BUElDWzBdOiBhcGlj X2lkIDEsIHZlcnNpb24gMzIsIGFkZHJlc3MgMHhmZWMwMDAwMCwgR1NJIDAtMjMKKFhFTikgSU9B UElDWzFdOiBhcGljX2lkIDIsIHZlcnNpb24gMzIsIGFkZHJlc3MgMHhmZWM4MDAwMCwgR1NJIDI0 LTQ3CihYRU4pIElPQVBJQ1syXTogYXBpY19pZCAzLCB2ZXJzaW9uIDMyLCBhZGRyZXNzIDB4ZmVj ODEwMDAsIEdTSSA0OC03MQooWEVOKSBJT0FQSUNbM106IGFwaWNfaWQgNCwgdmVyc2lvbiAzMiwg YWRkcmVzcyAweGZlYzgxODAwLCBHU0kgNzItOTUKKFhFTikgRW5hYmxpbmcgQVBJQyBtb2RlOiAg UGh5cy4gIFVzaW5nIDQgSS9PIEFQSUNzCihYRU4pIFVzaW5nIHNjaGVkdWxlcjogU01QIENyZWRp dCBTY2hlZHVsZXIgKGNyZWRpdCkKKFhFTikgRGV0ZWN0ZWQgMjQwMC4xMzYgTUh6IHByb2Nlc3Nv ci4KKFhFTikgSFZNOiBWTVggZW5hYmxlZAooWEVOKSBDUFUwOiBJbnRlbChSKSBYZW9uKFIpIENQ VSAgICAgICAgICAgRTczMzAgIEAgMi40MEdIeiBzdGVwcGluZyAwYgooWEVOKSBCb290aW5nIHBy b2Nlc3NvciAxLzggZWlwIDhjMDAwCihYRU4pIENQVTE6IEludGVsKFIpIFhlb24oUikgQ1BVICAg ICAgICAgICBFNzMzMCAgQCAyLjQwR0h6IHN0ZXBwaW5nIDBiCihYRU4pIEJvb3RpbmcgcHJvY2Vz c29yIDIvMTYgZWlwIDhjMDAwCihYRU4pIENQVTI6IEludGVsKFIpIFhlb24oUikgQ1BVICAgICAg ICAgICBFNzMzMCAgQCAyLjQwR0h6IHN0ZXBwaW5nIDBiCihYRU4pIEJvb3RpbmcgcHJvY2Vzc29y IDMvMjQgZWlwIDhjMDAwCihYRU4pIENQVTM6IEludGVsKFIpIFhlb24oUikgQ1BVICAgICAgICAg ICBFNzMzMCAgQCAyLjQwR0h6IHN0ZXBwaW5nIDBiCihYRU4pIEJvb3RpbmcgcHJvY2Vzc29yIDQv MSBlaXAgOGMwMDAKKFhFTikgQ1BVNDogSW50ZWwoUikgWGVvbihSKSBDUFUgICAgICAgICAgIEU3 MzMwICBAIDIuNDBHSHogc3RlcHBpbmcgMGIKKFhFTikgQm9vdGluZyBwcm9jZXNzb3IgNS85IGVp cCA4YzAwMAooWEVOKSBDUFU1OiBJbnRlbChSKSBYZW9uKFIpIENQVSAgICAgICAgICAgRTczMzAg IEAgMi40MEdIeiBzdGVwcGluZyAwYgooWEVOKSBCb290aW5nIHByb2Nlc3NvciA2LzE3IGVpcCA4 YzAwMAooWEVOKSBDUFU2OiBJbnRlbChSKSBYZW9uKFIpIENQVSAgICAgICAgICAgRTczMzAgIEAg Mi40MEdIeiBzdGVwcGluZyAwYgooWEVOKSBCb290aW5nIHByb2Nlc3NvciA3LzI1IGVpcCA4YzAw MAooWEVOKSBDUFU3OiBJbnRlbChSKSBYZW9uKFIpIENQVSAgICAgICAgICAgRTczMzAgIEAgMi40 MEdIeiBzdGVwcGluZyAwYgooWEVOKSBCb290aW5nIHByb2Nlc3NvciA4LzIgZWlwIDhjMDAwCihY RU4pIENQVTg6IEludGVsKFIpIFhlb24oUikgQ1BVICAgICAgICAgICBFNzMzMCAgQCAyLjQwR0h6 IHN0ZXBwaW5nIDBiCihYRU4pIEJvb3RpbmcgcHJvY2Vzc29yIDkvMTAgZWlwIDhjMDAwCihYRU4p IENQVTk6IEludGVsKFIpIFhlb24oUikgQ1BVICAgICAgICAgICBFNzMzMCAgQCAyLjQwR0h6IHN0 ZXBwaW5nIDBiCihYRU4pIEJvb3RpbmcgcHJvY2Vzc29yIDEwLzE4IGVpcCA4YzAwMAooWEVOKSBD UFUxMDogSW50ZWwoUikgWGVvbihSKSBDUFUgICAgICAgICAgIEU3MzMwICBAIDIuNDBHSHogc3Rl cHBpbmcgMGIKKFhFTikgQm9vdGluZyBwcm9jZXNzb3IgMTEvMjYgZWlwIDhjMDAwCihYRU4pIENQ VTExOiBJbnRlbChSKSBYZW9uKFIpIENQVSAgICAgICAgICAgRTczMzAgIEAgMi40MEdIeiBzdGVw cGluZyAwYgooWEVOKSBCb290aW5nIHByb2Nlc3NvciAxMi8zIGVpcCA4YzAwMAooWEVOKSBDUFUx MjogSW50ZWwoUikgWGVvbihSKSBDUFUgICAgICAgICAgIEU3MzMwICBAIDIuNDBHSHogc3RlcHBp bmcgMGIKKFhFTikgQm9vdGluZyBwcm9jZXNzb3IgMTMvMTEgZWlwIDhjMDAwCihYRU4pIENQVTEz OiBJbnRlbChSKSBYZW9uKFIpIENQVSAgICAgICAgICAgRTczMzAgIEAgMi40MEdIeiBzdGVwcGlu ZyAwYgooWEVOKSBCb290aW5nIHByb2Nlc3NvciAxNC8xOSBlaXAgOGMwMDAKKFhFTikgQ1BVMTQ6 IEludGVsKFIpIFhlb24oUikgQ1BVICAgICAgICAgICBFNzMzMCAgQCAyLjQwR0h6IHN0ZXBwaW5n IDBiCihYRU4pIEJvb3RpbmcgcHJvY2Vzc29yIDE1LzI3IGVpcCA4YzAwMAooWEVOKSBDUFUxNTog SW50ZWwoUikgWGVvbihSKSBDUFUgICAgICAgICAgIEU3MzMwICBAIDIuNDBHSHogc3RlcHBpbmcg MGIKKFhFTikgVG90YWwgb2YgMTYgcHJvY2Vzc29ycyBhY3RpdmF0ZWQuCihYRU4pIEVOQUJMSU5H IElPLUFQSUMgSVJRcwooWEVOKSAgLT4gVXNpbmcgbmV3IEFDSyBtZXRob2QKKFhFTikgUGxhdGZv cm0gdGltZXIgb3ZlcmZsb3dzIGluIDE0OTk4IGppZmZpZXMuCihYRU4pIFBsYXRmb3JtIHRpbWVy IGlzIDE0LjMxOE1IeiBIUEVUCihYRU4pIEJyb3VnaHQgdXAgMTYgQ1BVcwooWEVOKSBBTUQgSU9N TVU6IERpc2FibGVkCihYRU4pICoqKiBMT0FESU5HIERPTUFJTiAwICoqKgooWEVOKSAgWGVuICBr ZXJuZWw6IDY0LWJpdCwgbHNiLCBjb21wYXQzMgooWEVOKSAgRG9tMCBrZXJuZWw6IDY0LWJpdCwg bHNiLCBwYWRkciAweDIwMDAwMCAtPiAweDYzMTkxOAooWEVOKSBQSFlTSUNBTCBNRU1PUlkgQVJS QU5HRU1FTlQ6CihYRU4pICBEb20wIGFsbG9jLjogICAwMDAwMDAwOGUwMDAwMDAwLT4wMDAwMDAw OGYwMDAwMDAwICgxNTQyMjU4NQpwYWdlcyB0byBiZSBhbGxvY2F0ZWQpCihYRU4pIFZJUlRVQUwg TUVNT1JZIEFSUkFOR0VNRU5UOgooWEVOKSAgTG9hZGVkIGtlcm5lbDogZmZmZmZmZmY4MDIwMDAw MC0+ZmZmZmZmZmY4MDYzMTkxOAooWEVOKSAgSW5pdC4gcmFtZGlzazogZmZmZmZmZmY4MDYzMjAw MC0+ZmZmZmZmZmY4MGQ0MGUwMAooWEVOKSAgUGh5cy1NYWNoIG1hcDogZmZmZmZmZmY4MGQ0MTAw MC0+ZmZmZmZmZmY4ODM2YjNjOAooWEVOKSAgU3RhcnQgaW5mbzogICAgZmZmZmZmZmY4ODM2YzAw MC0+ZmZmZmZmZmY4ODM2YzRhNAooWEVOKSAgUGFnZSB0YWJsZXM6ICAgZmZmZmZmZmY4ODM2ZDAw MC0+ZmZmZmZmZmY4ODNiNDAwMAooWEVOKSAgQm9vdCBzdGFjazogICAgZmZmZmZmZmY4ODNiNDAw MC0+ZmZmZmZmZmY4ODNiNTAwMAooWEVOKSAgVE9UQUw6ICAgICAgICAgZmZmZmZmZmY4MDAwMDAw MC0+ZmZmZmZmZmY4ODgwMDAwMAooWEVOKSAgRU5UUlkgQUREUkVTUzogZmZmZmZmZmY4MDIwMDAw MAooWEVOKSBEb20wIGhhcyBtYXhpbXVtIDE2IFZDUFVzCihYRU4pIEluaXRyZCBsZW4gMHg3MGVl MDAsIHN0YXJ0IGF0IDB4ZmZmZmZmZmY4MDYzMjAwMAooWEVOKSBTY3J1YmJpbmcgRnJlZSBSQU06 IC5kb25lLgooWEVOKSBYZW4gdHJhY2UgYnVmZmVyczogZGlzYWJsZWQKKFhFTikgU3RkLiBMb2ds ZXZlbDogRXJyb3JzIGFuZCB3YXJuaW5ncwooWEVOKSBHdWVzdCBMb2dsZXZlbDogTm90aGluZyAo UmF0ZS1saW1pdGVkOiBFcnJvcnMgYW5kIHdhcm5pbmdzKQooWEVOKSBYZW4gaXMgcmVsaW5xdWlz aGluZyBWR0EgY29uc29sZS4KKFhFTikgKioqIFNlcmlhbCBpbnB1dCAtPiBET00wICh0eXBlICdD VFJMLWEnIHRocmVlIHRpbWVzIHRvIHN3aXRjaAppbnB1dCB0byBYZW4pCihYRU4pIEZyZWVkIDEw NGtCIGluaXQgbWVtb3J5LgoKX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19f X19fX19fX18KWGVuLXVzZXJzIG1haWxpbmcgbGlzdApYZW4tdXNlcnNAbGlzdHMueGVuLm9yZwpo dHRwOi8vbGlzdHMueGVuLm9yZy94ZW4tdXNlcnM= From xen-users-bounces@lists.xen.org Sat Sep 29 15:14:19 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Sat, 29 Sep 2012 15:14:19 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1THyjB-0001BO-Bg; Sat, 29 Sep 2012 15:13:13 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1THyjA-0001B3-DH for xen-users@lists.xensource.com; Sat, 29 Sep 2012 15:13:12 +0000 Received: from [85.158.143.35:27723] by server-3.bemta-4.messagelabs.com id B7/E7-10986-70017605; Sat, 29 Sep 2012 15:13:11 +0000 X-Env-Sender: mrsanna1@gmail.com X-Msg-Ref: server-7.tower-21.messagelabs.com!1348931588!11744757!1 X-Originating-IP: [209.85.220.171] X-SpamReason: No, hits=0.3 required=7.0 tests=ML_RADAR_SPEW_LINKS_14, RCVD_BY_IP,spamassassin: X-StarScan-Received: X-StarScan-Version: 6.6.1.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 27180 invoked from network); 29 Sep 2012 15:13:09 -0000 Received: from mail-vc0-f171.google.com (HELO mail-vc0-f171.google.com) (209.85.220.171) by server-7.tower-21.messagelabs.com with RC4-SHA encrypted SMTP; 29 Sep 2012 15:13:09 -0000 Received: by vcmm18 with SMTP id m18so5474568vcm.30 for ; Sat, 29 Sep 2012 08:13:08 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; bh=GJiiKciB+AW37QQALJh016YNCl54lMppdyoHlLSf/tQ=; b=JUgB0qFqU0I+knq9Oe3VFqvKiTWGPRoZPQ4eRFHCBH4JvldommXTftJE8BMYFXoUbJ +BVssQv2u5R1sPKUOxuca0bCwkKzzanvQb0eKc9K3h2L8urpSp1Xw6VGdPFuSsTgErfZ GTKjuOR540yKSP17bl4hQI6n3ulg0BA8x7eLOsTRY3hRmNhJ3l2nzsHVDHb4HjPJHGwr +4bHDRNzT/Lrxp9stvVztDWcp0U8UAfhK7+a6PaNqLz03jD1Al/TI9s9bBxAjMzJl463 gr5VQId+czj+Kc05V+7/qSeapWSC3GzbxLsB9zmS1VK41+snGoOGFQ9sIpaFlBGUxnsd UtIA== MIME-Version: 1.0 Received: by 10.220.205.200 with SMTP id fr8mr5652534vcb.34.1348931588463; Sat, 29 Sep 2012 08:13:08 -0700 (PDT) Received: by 10.58.207.75 with HTTP; Sat, 29 Sep 2012 08:13:08 -0700 (PDT) In-Reply-To: References: <4D655A39.2040501@gmail.com> Date: Sat, 29 Sep 2012 17:13:08 +0200 Message-ID: From: Mauro To: Keir Fraser Cc: Dan Magenheimer , xen-devel@lists.xensource.com, Jeremy Fitzhardinge , Olivier Hanesse , Xen Users , Mark Adams Subject: Re: [Xen-users] [Xen-devel] Xen 4 TSC problems X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: base64 Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org T24gMjQgRmVicnVhcnkgMjAxMSAwODoxNiwgS2VpciBGcmFzZXIgPGtlaXIueGVuQGdtYWlsLmNv bT4gd3JvdGU6Cj4gUGxlYXNlIHNlbmQgWGVuIGJvb3Qgb3V0cHV0ICh4bSBkbWVzZykuIEdldHRp bmcgaXQgZnJvbSBYZW4gMy4yIGFzIHdlbGwKPiB3b3VsZCBiZSBpbnRlcmVzdGluZywgaWYgeW91 IHN0aWxsIGhhdmUgaXQgaW5zdGFsbGVkIG9uIGFueSBvZiB0aGVzZQo+IG1hY2hpbmVzLgoKSWYg aXQgY2FuIGJlIHVzZWZ1bCBoZXJlIGlzIHhtIGRtZXNmIG9mIHhlbiA0LjAgb24gYSBkZWJpYW4g c3F1ZWV6ZSBzeXN0ZW06CgooWEVOKSBYZW4gdmVyc2lvbiA0LjAuMSAoRGViaWFuIDQuMC4xLTUu NCkgKHVsdHJvdHRlckBkZWJpYW4ub3JnKSAoZ2NjCnZlcnNpb24gNC40LjUgKERlYmlhbiA0LjQu NS04KSApIFNhdCBTZXAgIDggMTk6MTU6NDYgVVRDIDIwMTIKKFhFTikgQm9vdGxvYWRlcjogR1JV QiAxLjk4KzIwMTAwODA0LTE0K3NxdWVlemUxCihYRU4pIENvbW1hbmQgbGluZTogcGxhY2Vob2xk ZXIgZG9tMF9tZW09MzA3Mk0gbG9nbHZsPXdhcm5pbmcKZ3Vlc3RfbG9nbHZsPXdhcm5pbmcKKFhF TikgVmlkZW8gaW5mb3JtYXRpb246CihYRU4pICBWR0EgaXMgdGV4dCBtb2RlIDgweDI1LCBmb250 IDh4MTYKKFhFTikgIFZCRS9EREMgbWV0aG9kczogVjI7IEVESUQgdHJhbnNmZXIgdGltZTogMiBz ZWNvbmRzCihYRU4pIERpc2MgaW5mb3JtYXRpb246CihYRU4pICBGb3VuZCAyIE1CUiBzaWduYXR1 cmVzCihYRU4pICBGb3VuZCAyIEVERCBpbmZvcm1hdGlvbiBzdHJ1Y3R1cmVzCihYRU4pIFhlbi1l ODIwIFJBTSBtYXA6CihYRU4pICAwMDAwMDAwMDAwMDAwMDAwIC0gMDAwMDAwMDAwMDA5ZjQwMCAo dXNhYmxlKQooWEVOKSAgMDAwMDAwMDAwMDA5ZjQwMCAtIDAwMDAwMDAwMDAwYTAwMDAgKHJlc2Vy dmVkKQooWEVOKSAgMDAwMDAwMDAwMDBmMDAwMCAtIDAwMDAwMDAwMDAxMDAwMDAgKHJlc2VydmVk KQooWEVOKSAgMDAwMDAwMDAwMDEwMDAwMCAtIDAwMDAwMDAwY2ZkNDMwMDAgKHVzYWJsZSkKKFhF TikgIDAwMDAwMDAwY2ZkNDMwMDAgLSAwMDAwMDAwMGNmZDRjMDAwIChBQ1BJIGRhdGEpCihYRU4p ICAwMDAwMDAwMGNmZDRjMDAwIC0gMDAwMDAwMDBjZmQ0ZDAwMCAodXNhYmxlKQooWEVOKSAgMDAw MDAwMDBjZmQ0ZDAwMCAtIDAwMDAwMDAwZDAwMDAwMDAgKHJlc2VydmVkKQooWEVOKSAgMDAwMDAw MDBlMDAwMDAwMCAtIDAwMDAwMDAwZjAwMDAwMDAgKHJlc2VydmVkKQooWEVOKSAgMDAwMDAwMDBm ZWMwMDAwMCAtIDAwMDAwMDAwZmVkMDAwMDAgKHJlc2VydmVkKQooWEVOKSAgMDAwMDAwMDBmZWUw MDAwMCAtIDAwMDAwMDAwZmVlMTAwMDAgKHJlc2VydmVkKQooWEVOKSAgMDAwMDAwMDBmZmMwMDAw MCAtIDAwMDAwMDAxMDAwMDAwMDAgKHJlc2VydmVkKQooWEVOKSAgMDAwMDAwMDEwMDAwMDAwMCAt IDAwMDAwMDEwMmZmZmYwMDAgKHVzYWJsZSkKKFhFTikgQUNQSTogUlNEUCAwMDBGNEYyMCwgMDAy NCAocjIgSFAgICAgKQooWEVOKSBBQ1BJOiBYU0RUIENGRDQzOTAwLCAwMDdDIChyMSBIUCAgICAg UHJvTGlhbnQgICAgICAgIDIgICDvv70gICAgIDE2MkUpCihYRU4pIEFDUEk6IEZBQ1AgQ0ZENDM5 QzAsIDAwRjQgKHIzIEhQICAgICBQcm9MaWFudCAgICAgICAgMiAgIO+/vSAgICAgMTYyRSkKKFhF TikgQUNQSTogRFNEVCBDRkQ0M0FDMCwgMzBDOSAocjEgSFAgICAgICAgICBEU0RUICAgICAgICAx IElOVEwgMjAwMzAyMjgpCihYRU4pIEFDUEk6IEZBQ1MgQ0ZENDMxMDAsIDAwNDAKKFhFTikgQUNQ STogU1BDUiBDRkQ0MzE0MCwgMDA1MCAocjEgSFAgICAgIFNQQ1JSQlNVICAgICAgICAxICAg77+9 ICAgICAxNjJFKQooWEVOKSBBQ1BJOiBNQ0ZHIENGRDQzMUMwLCAwMDNDIChyMSBIUCAgICAgUHJv TGlhbnQgICAgICAgIDEgICAgICAgICAgICAgMCkKKFhFTikgQUNQSTogSFBFVCBDRkQ0MzIwMCwg MDAzOCAocjEgSFAgICAgIFByb0xpYW50ICAgICAgICAyICAg77+9ICAgICAxNjJFKQooWEVOKSBB Q1BJOiBGRkZGIENGRDQzMjQwLCAwMDY0IChyMiBIUCAgICAgUDYxICAgICAgICAgICAgIDIgICDv v70gICAgIDE2MkUpCihYRU4pIEFDUEk6IFNQTUkgQ0ZENDMyQzAsIDAwNDAgKHI1IEhQICAgICBQ cm9MaWFudCAgICAgICAgMSAgIO+/vSAgICAgMTYyRSkKKFhFTikgQUNQSTogRVJTVCBDRkQ0MzMw MCwgMDFEMCAocjEgSFAgICAgIFByb0xpYW50ICAgICAgICAxICAg77+9ICAgICAxNjJFKQooWEVO KSBBQ1BJOiBBUElDIENGRDQzNTAwLCAwMTc2IChyMSBIUCAgICAgUHJvTGlhbnQgICAgICAgIDIg ICAgICAgICAgICAgMCkKKFhFTikgQUNQSTogRkZGRiBDRkQ0MzY4MCwgMDE3NiAocjEgSFAgICAg IFByb0xpYW50ICAgICAgICAxICAg77+9ICAgICAxNjJFKQooWEVOKSBBQ1BJOiBCRVJUIENGRDQz ODAwLCAwMDMwIChyMSBIUCAgICAgUHJvTGlhbnQgICAgICAgIDEgICDvv70gICAgIDE2MkUpCihY RU4pIEFDUEk6IEhFU1QgQ0ZENDM4NDAsIDAwQkMgKHIxIEhQICAgICBQcm9MaWFudCAgICAgICAg MSAgIO+/vSAgICAgMTYyRSkKKFhFTikgU3lzdGVtIFJBTTogNjU1MzJNQiAoNjcxMDU2NzJrQikK KFhFTikgRG9tYWluIGhlYXAgaW5pdGlhbGlzZWQKKFhFTikgUHJvY2Vzc29yICMwIDY6MTUgQVBJ QyB2ZXJzaW9uIDIwCihYRU4pIFByb2Nlc3NvciAjOCA2OjE1IEFQSUMgdmVyc2lvbiAyMAooWEVO KSBQcm9jZXNzb3IgIzE2IDY6MTUgQVBJQyB2ZXJzaW9uIDIwCihYRU4pIFByb2Nlc3NvciAjMjQg NjoxNSBBUElDIHZlcnNpb24gMjAKKFhFTikgUHJvY2Vzc29yICMxIDY6MTUgQVBJQyB2ZXJzaW9u IDIwCihYRU4pIFByb2Nlc3NvciAjOSA2OjE1IEFQSUMgdmVyc2lvbiAyMAooWEVOKSBQcm9jZXNz b3IgIzE3IDY6MTUgQVBJQyB2ZXJzaW9uIDIwCihYRU4pIFByb2Nlc3NvciAjMjUgNjoxNSBBUElD IHZlcnNpb24gMjAKKFhFTikgUHJvY2Vzc29yICMyIDY6MTUgQVBJQyB2ZXJzaW9uIDIwCihYRU4p IFByb2Nlc3NvciAjMTAgNjoxNSBBUElDIHZlcnNpb24gMjAKKFhFTikgUHJvY2Vzc29yICMxOCA2 OjE1IEFQSUMgdmVyc2lvbiAyMAooWEVOKSBQcm9jZXNzb3IgIzI2IDY6MTUgQVBJQyB2ZXJzaW9u IDIwCihYRU4pIFByb2Nlc3NvciAjMyA2OjE1IEFQSUMgdmVyc2lvbiAyMAooWEVOKSBQcm9jZXNz b3IgIzExIDY6MTUgQVBJQyB2ZXJzaW9uIDIwCihYRU4pIFByb2Nlc3NvciAjMTkgNjoxNSBBUElD IHZlcnNpb24gMjAKKFhFTikgUHJvY2Vzc29yICMyNyA2OjE1IEFQSUMgdmVyc2lvbiAyMAooWEVO KSBJT0FQSUNbMF06IGFwaWNfaWQgMSwgdmVyc2lvbiAzMiwgYWRkcmVzcyAweGZlYzAwMDAwLCBH U0kgMC0yMwooWEVOKSBJT0FQSUNbMV06IGFwaWNfaWQgMiwgdmVyc2lvbiAzMiwgYWRkcmVzcyAw eGZlYzgwMDAwLCBHU0kgMjQtNDcKKFhFTikgSU9BUElDWzJdOiBhcGljX2lkIDMsIHZlcnNpb24g MzIsIGFkZHJlc3MgMHhmZWM4MTAwMCwgR1NJIDQ4LTcxCihYRU4pIElPQVBJQ1szXTogYXBpY19p ZCA0LCB2ZXJzaW9uIDMyLCBhZGRyZXNzIDB4ZmVjODE4MDAsIEdTSSA3Mi05NQooWEVOKSBFbmFi bGluZyBBUElDIG1vZGU6ICBQaHlzLiAgVXNpbmcgNCBJL08gQVBJQ3MKKFhFTikgVXNpbmcgc2No ZWR1bGVyOiBTTVAgQ3JlZGl0IFNjaGVkdWxlciAoY3JlZGl0KQooWEVOKSBEZXRlY3RlZCAyNDAw LjE0NSBNSHogcHJvY2Vzc29yLgooWEVOKSBJbml0aW5nIG1lbW9yeSBzaGFyaW5nLgooWEVOKSBW TVg6IFN1cHBvcnRlZCBhZHZhbmNlZCBmZWF0dXJlczoKKFhFTikgIC0gQVBJQyBNTUlPIGFjY2Vz cyB2aXJ0dWFsaXNhdGlvbgooWEVOKSAgLSBBUElDIFRQUiBzaGFkb3cKKFhFTikgIC0gVmlydHVh bCBOTUkKKFhFTikgIC0gTVNSIGRpcmVjdC1hY2Nlc3MgYml0bWFwCihYRU4pIEhWTTogQVNJRHMg ZGlzYWJsZWQuCihYRU4pIEhWTTogVk1YIGVuYWJsZWQKKFhFTikgSS9PIHZpcnR1YWxpc2F0aW9u IGRpc2FibGVkCihYRU4pIFRvdGFsIG9mIDE2IHByb2Nlc3NvcnMgYWN0aXZhdGVkLgooWEVOKSBF TkFCTElORyBJTy1BUElDIElSUXMKKFhFTikgIC0+IFVzaW5nIG5ldyBBQ0sgbWV0aG9kCihYRU4p IGNoZWNraW5nIFRTQyBzeW5jaHJvbml6YXRpb24gYWNyb3NzIDE2IENQVXM6IHBhc3NlZC4KKFhF TikgUGxhdGZvcm0gdGltZXIgaXMgMTQuMzE4TUh6IEhQRVQKKFhFTikgQWxsb2NhdGVkIGNvbnNv bGUgcmluZyBvZiAzMiBLaUIuCihYRU4pIEJyb3VnaHQgdXAgMTYgQ1BVcwooWEVOKSAqKiogTE9B RElORyBET01BSU4gMCAqKioKKFhFTikgIFhlbiAga2VybmVsOiA2NC1iaXQsIGxzYiwgY29tcGF0 MzIKKFhFTikgIERvbTAga2VybmVsOiA2NC1iaXQsIFBBRSwgbHNiLCBwYWRkciAweDEwMDAwMDAg LT4gMHgxNzA4MDAwCihYRU4pIFBIWVNJQ0FMIE1FTU9SWSBBUlJBTkdFTUVOVDoKKFhFTikgIERv bTAgYWxsb2MuOiAgIDAwMDAwMDA4M2MwMDAwMDAtPjAwMDAwMDA4NDAwMDAwMDAgKDc3MDA0OCBw YWdlcwp0byBiZSBhbGxvY2F0ZWQpCihYRU4pIFZJUlRVQUwgTUVNT1JZIEFSUkFOR0VNRU5UOgoo WEVOKSAgTG9hZGVkIGtlcm5lbDogZmZmZmZmZmY4MTAwMDAwMC0+ZmZmZmZmZmY4MTcwODAwMAoo WEVOKSAgSW5pdC4gcmFtZGlzazogZmZmZmZmZmY4MTcwODAwMC0+ZmZmZmZmZmY4MWVmYjAwMAoo WEVOKSAgUGh5cy1NYWNoIG1hcDogZmZmZmZmZmY4MWVmYjAwMC0+ZmZmZmZmZmY4MjRmYjAwMAoo WEVOKSAgU3RhcnQgaW5mbzogICAgZmZmZmZmZmY4MjRmYjAwMC0+ZmZmZmZmZmY4MjRmYjRiNAoo WEVOKSAgUGFnZSB0YWJsZXM6ICAgZmZmZmZmZmY4MjRmYzAwMC0+ZmZmZmZmZmY4MjUxMzAwMAoo WEVOKSAgQm9vdCBzdGFjazogICAgZmZmZmZmZmY4MjUxMzAwMC0+ZmZmZmZmZmY4MjUxNDAwMAoo WEVOKSAgVE9UQUw6ICAgICAgICAgZmZmZmZmZmY4MDAwMDAwMC0+ZmZmZmZmZmY4MjgwMDAwMAoo WEVOKSAgRU5UUlkgQUREUkVTUzogZmZmZmZmZmY4MTUzMTIwMAooWEVOKSBEb20wIGhhcyBtYXhp bXVtIDE2IFZDUFVzCihYRU4pIFNjcnViYmluZyBGcmVlIFJBTToKLi4uLi4uLi4uLi4uLi4uLi4u Li4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4u Li4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4u Li4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4u Li4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4u Li4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4u Li4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4u Li4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4u Li4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4u Li4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4u Li4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4u Li4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi5kb25lLgooWEVOKSBYZW4gdHJhY2UgYnVmZmVy czogZGlzYWJsZWQKKFhFTikgU3RkLiBMb2dsZXZlbDogRXJyb3JzIGFuZCB3YXJuaW5ncwooWEVO KSBHdWVzdCBMb2dsZXZlbDogRXJyb3JzIGFuZCB3YXJuaW5ncwooWEVOKSBYZW4gaXMgcmVsaW5x dWlzaGluZyBWR0EgY29uc29sZS4KKFhFTikgKioqIFNlcmlhbCBpbnB1dCAtPiBET00wICh0eXBl ICdDVFJMLWEnIHRocmVlIHRpbWVzIHRvIHN3aXRjaAppbnB1dCB0byBYZW4pCihYRU4pIEZyZWVk IDE3NmtCIGluaXQgbWVtb3J5LgooWEVOKSBQbGF0Zm9ybSB0aW1lciBhcHBlYXJzIHRvIGhhdmUg dW5leHBlY3RlZGx5IHdyYXBwZWQgMTAgb3IgbW9yZSB0aW1lcy4KCgphbmQgaGVyZSBpcyB4bSBk bWVzZyBvZiB4ZW4gMy4yIG9uIGEgZGViaWFuIGxlbm55IHN5c3RlbSBydW5uaW5nIG9uCnRoZSBz YW1lIGhhcmR3YXJlLCBvbiB0aGlzIHN5c3RlbSBJIGRvbid0IGhhdmUgY2xvY2sgcHJvYmxlbXM6 CgooWEVOKSBYZW4gdmVyc2lvbiAzLjItMSAoRGViaWFuIDMuMi4xLTIpICh3YWxkaUBkZWJpYW4u b3JnKSAoZ2NjCnZlcnNpb24gNC4zLjEgKERlYmlhbiA0LjMuMS0yKSApIFNhdCBKdW4gMjggMDk6 MzI6MTggVVRDIDIwMDgKKFhFTikgQ29tbWFuZCBsaW5lOgooWEVOKSBWaWRlbyBpbmZvcm1hdGlv bjoKKFhFTikgIFZHQSBpcyB0ZXh0IG1vZGUgODB4MjUsIGZvbnQgOHgxNgooWEVOKSAgVkJFL0RE QyBtZXRob2RzOiBWMjsgRURJRCB0cmFuc2ZlciB0aW1lOiAyIHNlY29uZHMKKFhFTikgRGlzYyBp bmZvcm1hdGlvbjoKKFhFTikgIEZvdW5kIDIgTUJSIHNpZ25hdHVyZXMKKFhFTikgIEZvdW5kIDIg RUREIGluZm9ybWF0aW9uIHN0cnVjdHVyZXMKKFhFTikgWGVuLWU4MjAgUkFNIG1hcDoKKFhFTikg IDAwMDAwMDAwMDAwMDAwMDAgLSAwMDAwMDAwMDAwMDlmNDAwICh1c2FibGUpCihYRU4pICAwMDAw MDAwMDAwMDlmNDAwIC0gMDAwMDAwMDAwMDBhMDAwMCAocmVzZXJ2ZWQpCihYRU4pICAwMDAwMDAw MDAwMGYwMDAwIC0gMDAwMDAwMDAwMDEwMDAwMCAocmVzZXJ2ZWQpCihYRU4pICAwMDAwMDAwMDAw MTAwMDAwIC0gMDAwMDAwMDBjZmQ0MzAwMCAodXNhYmxlKQooWEVOKSAgMDAwMDAwMDBjZmQ0MzAw MCAtIDAwMDAwMDAwY2ZkNGMwMDAgKEFDUEkgZGF0YSkKKFhFTikgIDAwMDAwMDAwY2ZkNGMwMDAg LSAwMDAwMDAwMGNmZDRkMDAwICh1c2FibGUpCihYRU4pICAwMDAwMDAwMGNmZDRkMDAwIC0gMDAw MDAwMDBkMDAwMDAwMCAocmVzZXJ2ZWQpCihYRU4pICAwMDAwMDAwMGUwMDAwMDAwIC0gMDAwMDAw MDBmMDAwMDAwMCAocmVzZXJ2ZWQpCihYRU4pICAwMDAwMDAwMGZlYzAwMDAwIC0gMDAwMDAwMDBm ZWQwMDAwMCAocmVzZXJ2ZWQpCihYRU4pICAwMDAwMDAwMGZlZTAwMDAwIC0gMDAwMDAwMDBmZWUx MDAwMCAocmVzZXJ2ZWQpCihYRU4pICAwMDAwMDAwMGZmYzAwMDAwIC0gMDAwMDAwMDEwMDAwMDAw MCAocmVzZXJ2ZWQpCihYRU4pICAwMDAwMDAwMTAwMDAwMDAwIC0gMDAwMDAwMGYyZmZmZjAwMCAo dXNhYmxlKQooWEVOKSBTeXN0ZW0gUkFNOiA2MTQzNk1CICg2MjkxMTM2OGtCKQooWEVOKSBYZW4g aGVhcDogMTJNQiAoMTMxMjhrQikKKFhFTikgRG9tYWluIGhlYXAgaW5pdGlhbGlzZWQ6IERNQSB3 aWR0aCAzMiBiaXRzCihYRU4pIFByb2Nlc3NvciAjMCA2OjE1IEFQSUMgdmVyc2lvbiAyMAooWEVO KSBQcm9jZXNzb3IgIzggNjoxNSBBUElDIHZlcnNpb24gMjAKKFhFTikgUHJvY2Vzc29yICMxNiA2 OjE1IEFQSUMgdmVyc2lvbiAyMAooWEVOKSBQcm9jZXNzb3IgIzI0IDY6MTUgQVBJQyB2ZXJzaW9u IDIwCihYRU4pIFByb2Nlc3NvciAjMSA2OjE1IEFQSUMgdmVyc2lvbiAyMAooWEVOKSBQcm9jZXNz b3IgIzkgNjoxNSBBUElDIHZlcnNpb24gMjAKKFhFTikgUHJvY2Vzc29yICMxNyA2OjE1IEFQSUMg dmVyc2lvbiAyMAooWEVOKSBQcm9jZXNzb3IgIzI1IDY6MTUgQVBJQyB2ZXJzaW9uIDIwCihYRU4p IFByb2Nlc3NvciAjMiA2OjE1IEFQSUMgdmVyc2lvbiAyMAooWEVOKSBQcm9jZXNzb3IgIzEwIDY6 MTUgQVBJQyB2ZXJzaW9uIDIwCihYRU4pIFByb2Nlc3NvciAjMTggNjoxNSBBUElDIHZlcnNpb24g MjAKKFhFTikgUHJvY2Vzc29yICMyNiA2OjE1IEFQSUMgdmVyc2lvbiAyMAooWEVOKSBQcm9jZXNz b3IgIzMgNjoxNSBBUElDIHZlcnNpb24gMjAKKFhFTikgUHJvY2Vzc29yICMxMSA2OjE1IEFQSUMg dmVyc2lvbiAyMAooWEVOKSBQcm9jZXNzb3IgIzE5IDY6MTUgQVBJQyB2ZXJzaW9uIDIwCihYRU4p IFByb2Nlc3NvciAjMjcgNjoxNSBBUElDIHZlcnNpb24gMjAKKFhFTikgSU9BUElDWzBdOiBhcGlj X2lkIDEsIHZlcnNpb24gMzIsIGFkZHJlc3MgMHhmZWMwMDAwMCwgR1NJIDAtMjMKKFhFTikgSU9B UElDWzFdOiBhcGljX2lkIDIsIHZlcnNpb24gMzIsIGFkZHJlc3MgMHhmZWM4MDAwMCwgR1NJIDI0 LTQ3CihYRU4pIElPQVBJQ1syXTogYXBpY19pZCAzLCB2ZXJzaW9uIDMyLCBhZGRyZXNzIDB4ZmVj ODEwMDAsIEdTSSA0OC03MQooWEVOKSBJT0FQSUNbM106IGFwaWNfaWQgNCwgdmVyc2lvbiAzMiwg YWRkcmVzcyAweGZlYzgxODAwLCBHU0kgNzItOTUKKFhFTikgRW5hYmxpbmcgQVBJQyBtb2RlOiAg UGh5cy4gIFVzaW5nIDQgSS9PIEFQSUNzCihYRU4pIFVzaW5nIHNjaGVkdWxlcjogU01QIENyZWRp dCBTY2hlZHVsZXIgKGNyZWRpdCkKKFhFTikgRGV0ZWN0ZWQgMjQwMC4xMzYgTUh6IHByb2Nlc3Nv ci4KKFhFTikgSFZNOiBWTVggZW5hYmxlZAooWEVOKSBDUFUwOiBJbnRlbChSKSBYZW9uKFIpIENQ VSAgICAgICAgICAgRTczMzAgIEAgMi40MEdIeiBzdGVwcGluZyAwYgooWEVOKSBCb290aW5nIHBy b2Nlc3NvciAxLzggZWlwIDhjMDAwCihYRU4pIENQVTE6IEludGVsKFIpIFhlb24oUikgQ1BVICAg ICAgICAgICBFNzMzMCAgQCAyLjQwR0h6IHN0ZXBwaW5nIDBiCihYRU4pIEJvb3RpbmcgcHJvY2Vz c29yIDIvMTYgZWlwIDhjMDAwCihYRU4pIENQVTI6IEludGVsKFIpIFhlb24oUikgQ1BVICAgICAg ICAgICBFNzMzMCAgQCAyLjQwR0h6IHN0ZXBwaW5nIDBiCihYRU4pIEJvb3RpbmcgcHJvY2Vzc29y IDMvMjQgZWlwIDhjMDAwCihYRU4pIENQVTM6IEludGVsKFIpIFhlb24oUikgQ1BVICAgICAgICAg ICBFNzMzMCAgQCAyLjQwR0h6IHN0ZXBwaW5nIDBiCihYRU4pIEJvb3RpbmcgcHJvY2Vzc29yIDQv MSBlaXAgOGMwMDAKKFhFTikgQ1BVNDogSW50ZWwoUikgWGVvbihSKSBDUFUgICAgICAgICAgIEU3 MzMwICBAIDIuNDBHSHogc3RlcHBpbmcgMGIKKFhFTikgQm9vdGluZyBwcm9jZXNzb3IgNS85IGVp cCA4YzAwMAooWEVOKSBDUFU1OiBJbnRlbChSKSBYZW9uKFIpIENQVSAgICAgICAgICAgRTczMzAg IEAgMi40MEdIeiBzdGVwcGluZyAwYgooWEVOKSBCb290aW5nIHByb2Nlc3NvciA2LzE3IGVpcCA4 YzAwMAooWEVOKSBDUFU2OiBJbnRlbChSKSBYZW9uKFIpIENQVSAgICAgICAgICAgRTczMzAgIEAg Mi40MEdIeiBzdGVwcGluZyAwYgooWEVOKSBCb290aW5nIHByb2Nlc3NvciA3LzI1IGVpcCA4YzAw MAooWEVOKSBDUFU3OiBJbnRlbChSKSBYZW9uKFIpIENQVSAgICAgICAgICAgRTczMzAgIEAgMi40 MEdIeiBzdGVwcGluZyAwYgooWEVOKSBCb290aW5nIHByb2Nlc3NvciA4LzIgZWlwIDhjMDAwCihY RU4pIENQVTg6IEludGVsKFIpIFhlb24oUikgQ1BVICAgICAgICAgICBFNzMzMCAgQCAyLjQwR0h6 IHN0ZXBwaW5nIDBiCihYRU4pIEJvb3RpbmcgcHJvY2Vzc29yIDkvMTAgZWlwIDhjMDAwCihYRU4p IENQVTk6IEludGVsKFIpIFhlb24oUikgQ1BVICAgICAgICAgICBFNzMzMCAgQCAyLjQwR0h6IHN0 ZXBwaW5nIDBiCihYRU4pIEJvb3RpbmcgcHJvY2Vzc29yIDEwLzE4IGVpcCA4YzAwMAooWEVOKSBD UFUxMDogSW50ZWwoUikgWGVvbihSKSBDUFUgICAgICAgICAgIEU3MzMwICBAIDIuNDBHSHogc3Rl cHBpbmcgMGIKKFhFTikgQm9vdGluZyBwcm9jZXNzb3IgMTEvMjYgZWlwIDhjMDAwCihYRU4pIENQ VTExOiBJbnRlbChSKSBYZW9uKFIpIENQVSAgICAgICAgICAgRTczMzAgIEAgMi40MEdIeiBzdGVw cGluZyAwYgooWEVOKSBCb290aW5nIHByb2Nlc3NvciAxMi8zIGVpcCA4YzAwMAooWEVOKSBDUFUx MjogSW50ZWwoUikgWGVvbihSKSBDUFUgICAgICAgICAgIEU3MzMwICBAIDIuNDBHSHogc3RlcHBp bmcgMGIKKFhFTikgQm9vdGluZyBwcm9jZXNzb3IgMTMvMTEgZWlwIDhjMDAwCihYRU4pIENQVTEz OiBJbnRlbChSKSBYZW9uKFIpIENQVSAgICAgICAgICAgRTczMzAgIEAgMi40MEdIeiBzdGVwcGlu ZyAwYgooWEVOKSBCb290aW5nIHByb2Nlc3NvciAxNC8xOSBlaXAgOGMwMDAKKFhFTikgQ1BVMTQ6 IEludGVsKFIpIFhlb24oUikgQ1BVICAgICAgICAgICBFNzMzMCAgQCAyLjQwR0h6IHN0ZXBwaW5n IDBiCihYRU4pIEJvb3RpbmcgcHJvY2Vzc29yIDE1LzI3IGVpcCA4YzAwMAooWEVOKSBDUFUxNTog SW50ZWwoUikgWGVvbihSKSBDUFUgICAgICAgICAgIEU3MzMwICBAIDIuNDBHSHogc3RlcHBpbmcg MGIKKFhFTikgVG90YWwgb2YgMTYgcHJvY2Vzc29ycyBhY3RpdmF0ZWQuCihYRU4pIEVOQUJMSU5H IElPLUFQSUMgSVJRcwooWEVOKSAgLT4gVXNpbmcgbmV3IEFDSyBtZXRob2QKKFhFTikgUGxhdGZv cm0gdGltZXIgb3ZlcmZsb3dzIGluIDE0OTk4IGppZmZpZXMuCihYRU4pIFBsYXRmb3JtIHRpbWVy IGlzIDE0LjMxOE1IeiBIUEVUCihYRU4pIEJyb3VnaHQgdXAgMTYgQ1BVcwooWEVOKSBBTUQgSU9N TVU6IERpc2FibGVkCihYRU4pICoqKiBMT0FESU5HIERPTUFJTiAwICoqKgooWEVOKSAgWGVuICBr ZXJuZWw6IDY0LWJpdCwgbHNiLCBjb21wYXQzMgooWEVOKSAgRG9tMCBrZXJuZWw6IDY0LWJpdCwg bHNiLCBwYWRkciAweDIwMDAwMCAtPiAweDYzMTkxOAooWEVOKSBQSFlTSUNBTCBNRU1PUlkgQVJS QU5HRU1FTlQ6CihYRU4pICBEb20wIGFsbG9jLjogICAwMDAwMDAwOGUwMDAwMDAwLT4wMDAwMDAw OGYwMDAwMDAwICgxNTQyMjU4NQpwYWdlcyB0byBiZSBhbGxvY2F0ZWQpCihYRU4pIFZJUlRVQUwg TUVNT1JZIEFSUkFOR0VNRU5UOgooWEVOKSAgTG9hZGVkIGtlcm5lbDogZmZmZmZmZmY4MDIwMDAw MC0+ZmZmZmZmZmY4MDYzMTkxOAooWEVOKSAgSW5pdC4gcmFtZGlzazogZmZmZmZmZmY4MDYzMjAw MC0+ZmZmZmZmZmY4MGQ0MGUwMAooWEVOKSAgUGh5cy1NYWNoIG1hcDogZmZmZmZmZmY4MGQ0MTAw MC0+ZmZmZmZmZmY4ODM2YjNjOAooWEVOKSAgU3RhcnQgaW5mbzogICAgZmZmZmZmZmY4ODM2YzAw MC0+ZmZmZmZmZmY4ODM2YzRhNAooWEVOKSAgUGFnZSB0YWJsZXM6ICAgZmZmZmZmZmY4ODM2ZDAw MC0+ZmZmZmZmZmY4ODNiNDAwMAooWEVOKSAgQm9vdCBzdGFjazogICAgZmZmZmZmZmY4ODNiNDAw MC0+ZmZmZmZmZmY4ODNiNTAwMAooWEVOKSAgVE9UQUw6ICAgICAgICAgZmZmZmZmZmY4MDAwMDAw MC0+ZmZmZmZmZmY4ODgwMDAwMAooWEVOKSAgRU5UUlkgQUREUkVTUzogZmZmZmZmZmY4MDIwMDAw MAooWEVOKSBEb20wIGhhcyBtYXhpbXVtIDE2IFZDUFVzCihYRU4pIEluaXRyZCBsZW4gMHg3MGVl MDAsIHN0YXJ0IGF0IDB4ZmZmZmZmZmY4MDYzMjAwMAooWEVOKSBTY3J1YmJpbmcgRnJlZSBSQU06 IC5kb25lLgooWEVOKSBYZW4gdHJhY2UgYnVmZmVyczogZGlzYWJsZWQKKFhFTikgU3RkLiBMb2ds ZXZlbDogRXJyb3JzIGFuZCB3YXJuaW5ncwooWEVOKSBHdWVzdCBMb2dsZXZlbDogTm90aGluZyAo UmF0ZS1saW1pdGVkOiBFcnJvcnMgYW5kIHdhcm5pbmdzKQooWEVOKSBYZW4gaXMgcmVsaW5xdWlz aGluZyBWR0EgY29uc29sZS4KKFhFTikgKioqIFNlcmlhbCBpbnB1dCAtPiBET00wICh0eXBlICdD VFJMLWEnIHRocmVlIHRpbWVzIHRvIHN3aXRjaAppbnB1dCB0byBYZW4pCihYRU4pIEZyZWVkIDEw NGtCIGluaXQgbWVtb3J5LgoKX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19f X19fX19fX18KWGVuLXVzZXJzIG1haWxpbmcgbGlzdApYZW4tdXNlcnNAbGlzdHMueGVuLm9yZwpo dHRwOi8vbGlzdHMueGVuLm9yZy94ZW4tdXNlcnM= From xen-users-bounces@lists.xen.org Sat Sep 29 15:21:31 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Sat, 29 Sep 2012 15:21:31 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1THyqS-0001cw-0R; Sat, 29 Sep 2012 15:20:44 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1THyqP-0001cn-TK for xen-users@lists.xen.org; Sat, 29 Sep 2012 15:20:42 +0000 Received: from [85.158.139.83:30696] by server-6.bemta-5.messagelabs.com id B1/9E-14717-9C117605; Sat, 29 Sep 2012 15:20:41 +0000 X-Env-Sender: cdelorme@gmail.com X-Msg-Ref: server-3.tower-182.messagelabs.com!1348932038!32662535!1 X-Originating-IP: [209.85.219.45] X-SpamReason: No, hits=0.4 required=7.0 tests=HTML_30_40,HTML_MESSAGE, ML_RADAR_SPEW_LINKS_14,RCVD_BY_IP,spamassassin: X-StarScan-Received: X-StarScan-Version: 6.6.1.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 5661 invoked from network); 29 Sep 2012 15:20:40 -0000 Received: from mail-oa0-f45.google.com (HELO mail-oa0-f45.google.com) (209.85.219.45) by server-3.tower-182.messagelabs.com with RC4-SHA encrypted SMTP; 29 Sep 2012 15:20:40 -0000 Received: by oagi18 with SMTP id i18so5197705oag.32 for ; Sat, 29 Sep 2012 08:20:38 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=ba3QFZJgKzvI8XwGe8zWwhwFOZPi+Pps4jV6HRHg/t4=; b=iFcTOplb4YA4XEdBLfNCcMckh5GOd51Wh6DtwtcSugVziwOxBYS2whpn/Uncw7FfZo kVUXu49CfoNTH5tYNfZKj62w1wjtJsKdGwK00FX7QeJdzRh5S2JW1qXbEeAJz8vJZofX iR6aujqlQ9KUxkEOwskXt/mDkHquT45024eTrXVGxEq0LOrZ6WAqbTRV+6ErfE79+ZO4 9dGan4B8YHY3EHFinNO4pCsRCJ3nCC3vb9smZdwt3SHQBJ07XxhsV1vAkOnOyQxTSyzx vhON4UegCn0IFs1yOnltTxXSUpusCubmxhMI8R2inKAXSAv6Wu1M89I1rIln+NkRUR8k uKgA== MIME-Version: 1.0 Received: by 10.60.170.142 with SMTP id am14mr8199329oec.40.1348932038563; Sat, 29 Sep 2012 08:20:38 -0700 (PDT) Received: by 10.76.19.148 with HTTP; Sat, 29 Sep 2012 08:20:38 -0700 (PDT) In-Reply-To: References: Date: Sat, 29 Sep 2012 11:20:38 -0400 Message-ID: From: Casey DeLorme To: David Escott Cc: xen-users@lists.xen.org Subject: Re: [Xen-users] PCI Passthrough X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============5079269593538303749==" Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org --===============5079269593538303749== Content-Type: multipart/alternative; boundary=bcaec54b47cafc192804cad8b62a --bcaec54b47cafc192804cad8b62a Content-Type: text/plain; charset=ISO-8859-1 Hello David, I have created a guide using Debian that can successfully reproduce VGA Passthrough with AMD Radeon cards, in particular I have used an AMD Radeon 6870. If you are more familiar with Fedora, I'm sure you can translate any Debain specific actions to Fedora equivalents. http://wiki.xen.org/wiki/Comprehensive_Xen_Debian_Wheezy_PCI_Passthrough_Tutorial I also posted a video walk-through: http://www.youtube.com/playlist?list=PLC70DC33D993CEB44&feature=view_all As for your current configuration, what version of Xen (4.0, 4.1.2, 4.2?), can you share your HVM Configuration, and are you getting any errors in your Xen log files or just inside of Windows? On Sat, Sep 29, 2012 at 11:10 AM, David Escott < david.escott@post.harvard.edu> wrote: > I've been playing around with doing PCI passthrough of Radeon cards > and have had some success. > > Under Fedora 17 (stock everything) I was able to passthrough an older > RADEON 2600XT to a Windows7 domU. > However when I try the same with a new RADEON 7850 I get a "not enough > resources" error from the Windows guest. > > I'm not sure what the next steps are, it seems from blog postings and > howtos that people are just trying things at random, and I don't > understand what the debugging process is. > > Any advice on what the next steps are? Should I move to an OS that > will have a newer XEN or is there some configuration file I should be > editing? > > Thanks, > David > > _______________________________________________ > Xen-users mailing list > Xen-users@lists.xen.org > http://lists.xen.org/xen-users > --bcaec54b47cafc192804cad8b62a Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable
Hello David,

I have created a guide usin= g Debian that can successfully reproduce VGA Passthrough with AMD Radeon ca= rds, in particular I have used an AMD Radeon 6870.

If you are more familiar with Fedora, I'm sure you can translate any De= bain specific actions to Fedora equivalents.

I also posted a video walk-through:

As for your current configuration, what version of Xen = (4.0, 4.1.2, 4.2?), can you share your HVM Configuration, and are you getti= ng any errors in your Xen log files or just inside of Windows?


On Sat, Sep 2= 9, 2012 at 11:10 AM, David Escott <david.escott@post.harvard.e= du> wrote:
I've been playing around with doing PCI = passthrough of Radeon cards
and have had some success.

Under Fedora 17 (stock everything) I was able to passthrough an older
RADEON 2600XT to a Windows7 domU.
However when I try the same with a new RADEON 7850 I get a "not enough=
resources" error from the Windows guest.

I'm not sure what the next steps are, it seems from blog postings and howtos that people are just trying things at random, and I don't
understand what the debugging process is.

Any advice on what the next steps are? Should I move to an OS that
will have a newer XEN or is there some configuration file I should be
editing?

Thanks,
David

_______________________________________________
Xen-users mailing list
Xen-users@lists.xen.org
http://lists.x= en.org/xen-users

--bcaec54b47cafc192804cad8b62a-- --===============5079269593538303749== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users --===============5079269593538303749==-- From xen-users-bounces@lists.xen.org Sat Sep 29 15:21:31 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Sat, 29 Sep 2012 15:21:31 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1THyqS-0001cw-0R; Sat, 29 Sep 2012 15:20:44 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1THyqP-0001cn-TK for xen-users@lists.xen.org; Sat, 29 Sep 2012 15:20:42 +0000 Received: from [85.158.139.83:30696] by server-6.bemta-5.messagelabs.com id B1/9E-14717-9C117605; Sat, 29 Sep 2012 15:20:41 +0000 X-Env-Sender: cdelorme@gmail.com X-Msg-Ref: server-3.tower-182.messagelabs.com!1348932038!32662535!1 X-Originating-IP: [209.85.219.45] X-SpamReason: No, hits=0.4 required=7.0 tests=HTML_30_40,HTML_MESSAGE, ML_RADAR_SPEW_LINKS_14,RCVD_BY_IP,spamassassin: X-StarScan-Received: X-StarScan-Version: 6.6.1.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 5661 invoked from network); 29 Sep 2012 15:20:40 -0000 Received: from mail-oa0-f45.google.com (HELO mail-oa0-f45.google.com) (209.85.219.45) by server-3.tower-182.messagelabs.com with RC4-SHA encrypted SMTP; 29 Sep 2012 15:20:40 -0000 Received: by oagi18 with SMTP id i18so5197705oag.32 for ; Sat, 29 Sep 2012 08:20:38 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=ba3QFZJgKzvI8XwGe8zWwhwFOZPi+Pps4jV6HRHg/t4=; b=iFcTOplb4YA4XEdBLfNCcMckh5GOd51Wh6DtwtcSugVziwOxBYS2whpn/Uncw7FfZo kVUXu49CfoNTH5tYNfZKj62w1wjtJsKdGwK00FX7QeJdzRh5S2JW1qXbEeAJz8vJZofX iR6aujqlQ9KUxkEOwskXt/mDkHquT45024eTrXVGxEq0LOrZ6WAqbTRV+6ErfE79+ZO4 9dGan4B8YHY3EHFinNO4pCsRCJ3nCC3vb9smZdwt3SHQBJ07XxhsV1vAkOnOyQxTSyzx vhON4UegCn0IFs1yOnltTxXSUpusCubmxhMI8R2inKAXSAv6Wu1M89I1rIln+NkRUR8k uKgA== MIME-Version: 1.0 Received: by 10.60.170.142 with SMTP id am14mr8199329oec.40.1348932038563; Sat, 29 Sep 2012 08:20:38 -0700 (PDT) Received: by 10.76.19.148 with HTTP; Sat, 29 Sep 2012 08:20:38 -0700 (PDT) In-Reply-To: References: Date: Sat, 29 Sep 2012 11:20:38 -0400 Message-ID: From: Casey DeLorme To: David Escott Cc: xen-users@lists.xen.org Subject: Re: [Xen-users] PCI Passthrough X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============5079269593538303749==" Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org --===============5079269593538303749== Content-Type: multipart/alternative; boundary=bcaec54b47cafc192804cad8b62a --bcaec54b47cafc192804cad8b62a Content-Type: text/plain; charset=ISO-8859-1 Hello David, I have created a guide using Debian that can successfully reproduce VGA Passthrough with AMD Radeon cards, in particular I have used an AMD Radeon 6870. If you are more familiar with Fedora, I'm sure you can translate any Debain specific actions to Fedora equivalents. http://wiki.xen.org/wiki/Comprehensive_Xen_Debian_Wheezy_PCI_Passthrough_Tutorial I also posted a video walk-through: http://www.youtube.com/playlist?list=PLC70DC33D993CEB44&feature=view_all As for your current configuration, what version of Xen (4.0, 4.1.2, 4.2?), can you share your HVM Configuration, and are you getting any errors in your Xen log files or just inside of Windows? On Sat, Sep 29, 2012 at 11:10 AM, David Escott < david.escott@post.harvard.edu> wrote: > I've been playing around with doing PCI passthrough of Radeon cards > and have had some success. > > Under Fedora 17 (stock everything) I was able to passthrough an older > RADEON 2600XT to a Windows7 domU. > However when I try the same with a new RADEON 7850 I get a "not enough > resources" error from the Windows guest. > > I'm not sure what the next steps are, it seems from blog postings and > howtos that people are just trying things at random, and I don't > understand what the debugging process is. > > Any advice on what the next steps are? Should I move to an OS that > will have a newer XEN or is there some configuration file I should be > editing? > > Thanks, > David > > _______________________________________________ > Xen-users mailing list > Xen-users@lists.xen.org > http://lists.xen.org/xen-users > --bcaec54b47cafc192804cad8b62a Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable
Hello David,

I have created a guide usin= g Debian that can successfully reproduce VGA Passthrough with AMD Radeon ca= rds, in particular I have used an AMD Radeon 6870.

If you are more familiar with Fedora, I'm sure you can translate any De= bain specific actions to Fedora equivalents.

I also posted a video walk-through:

As for your current configuration, what version of Xen = (4.0, 4.1.2, 4.2?), can you share your HVM Configuration, and are you getti= ng any errors in your Xen log files or just inside of Windows?


On Sat, Sep 2= 9, 2012 at 11:10 AM, David Escott <david.escott@post.harvard.e= du> wrote:
I've been playing around with doing PCI = passthrough of Radeon cards
and have had some success.

Under Fedora 17 (stock everything) I was able to passthrough an older
RADEON 2600XT to a Windows7 domU.
However when I try the same with a new RADEON 7850 I get a "not enough=
resources" error from the Windows guest.

I'm not sure what the next steps are, it seems from blog postings and howtos that people are just trying things at random, and I don't
understand what the debugging process is.

Any advice on what the next steps are? Should I move to an OS that
will have a newer XEN or is there some configuration file I should be
editing?

Thanks,
David

_______________________________________________
Xen-users mailing list
Xen-users@lists.xen.org
http://lists.x= en.org/xen-users

--bcaec54b47cafc192804cad8b62a-- --===============5079269593538303749== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users --===============5079269593538303749==-- From xen-users-bounces@lists.xen.org Sat Sep 29 16:10:45 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Sat, 29 Sep 2012 16:10:45 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1THzbw-0002e7-I6; Sat, 29 Sep 2012 16:09:48 +0000 Received: from mail27.messagelabs.com ([193.109.254.147]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1THzbu-0002dp-9Y; Sat, 29 Sep 2012 16:09:46 +0000 X-Env-Sender: singapore.mr.teo.en.ming@gmail.com X-Msg-Ref: server-10.tower-27.messagelabs.com!1348934977!7639841!1 X-Originating-IP: [209.85.220.45] X-SpamReason: No, hits=0.3 required=7.0 tests=ML_RADAR_SPEW_LINKS_14, RCVD_BY_IP,spamassassin: X-StarScan-Received: X-StarScan-Version: 6.6.1.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 4583 invoked from network); 29 Sep 2012 16:09:39 -0000 Received: from mail-pa0-f45.google.com (HELO mail-pa0-f45.google.com) (209.85.220.45) by server-10.tower-27.messagelabs.com with RC4-SHA encrypted SMTP; 29 Sep 2012 16:09:39 -0000 Received: by padfb10 with SMTP id fb10so3147816pad.32 for ; Sat, 29 Sep 2012 09:09:36 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:user-agent:mime-version:to:cc:subject :references:in-reply-to:content-type; bh=qRfFtARMCGhTFZFnk1WcoJ8EVH1Q2JJayUgnjKpLVLk=; b=povE/bgFNJE8NxgETMp2aKJDQ2rDcpvoQ9LHd9P+ZiZ+YDsdpJNw3GF1f8vMdxg7Ot l87K2NwIHc4RcNNeiOvkoOw593fVEKnub4ZO3ldPDgaxUwoxRAf3ONNq2FqPZKxdeHD8 T7+xBGkGeCbbEaGACIUTBmQNrY8dl8X/mKlZt65ebGE7ayuugW3Ydhc5estMO5OPslUj OTnfB/qmm0L6JUblijF69xoANYZd/DjpayK5FSKeAapYbkA+Bft7EUS9IKQIiXiRzDOa QzBLI2Quqc5d9YDRP5D/xGFQ6jCIuIlvqiT+zKe7AQiPhoYsxWwLMucg9Ah4rnxPjJqI 9QXA== Received: by 10.68.224.133 with SMTP id rc5mr28518968pbc.130.1348934976787; Sat, 29 Sep 2012 09:09:36 -0700 (PDT) Received: from [192.168.1.2] (cm152.gamma205.maxonline.com.sg. [202.156.205.152]) by mx.google.com with ESMTPS id b4sm7398767pbw.28.2012.09.29.09.09.34 (version=SSLv3 cipher=OTHER); Sat, 29 Sep 2012 09:09:35 -0700 (PDT) Message-ID: <50671D3D.1010304@gmail.com> Date: Sun, 30 Sep 2012 00:09:33 +0800 From: "Teo En Ming (Zhang Enming)" User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:15.0) Gecko/20120912 Thunderbird/15.0.1 MIME-Version: 1.0 To: "Teo En Ming (Zhang Enming)" References: <5066F922.1090305@gmail.com> In-Reply-To: <5066F922.1090305@gmail.com> Content-Type: multipart/mixed; boundary="------------070102050809000405040603" Cc: "xen-users@lists.xen.org" , "xen-devel@lists.xen.org" Subject: Re: [Xen-users] Unable to start Windows 8 HVM guest with Xen VGA Passthrough with Xen 4.2.1-pre X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org This is a multi-part message in MIME format. --------------070102050809000405040603 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit On 29/09/2012 21:35, Teo En Ming (Zhang Enming) wrote: > Hi, > > I have applied Xen VGA passthrough patches from David Techer's > personal website to Xen 4.2.1-pre source tree. Everything compiled and > installed smoothly. But when I tried to start Windows 8 HVM domU with > VGA passthrough, it gave me the following error: > > xc: error: unable to allocate memory to the HVM guest. (16: device or > resource busy): Internal error. > > There are no issues with Xen 4.2-unstable changeset 25099 however. > Attached are screenshots of the errors for Xen 4.2.1-pre and Xen configuration files. The following are links to screenshots of the errors for Xen 4.2.1-pre. http://i45.tinypic.com/2j3s7pj.jpg http://i45.tinypic.com/95myc3.jpg -- Yours sincerely, Mr. Teo En Ming (Zhang Enming) Singapore --------------070102050809000405040603 Content-Type: text/plain; charset=UTF-8; name="start-windows" Content-Transfer-Encoding: base64 Content-Disposition: attachment; filename="start-windows" IyEvYmluL3NoCnNldCAteAojCiMgU3RhcnRzIFNob3Jld2FsbCBGaXJld2FsbApzdWRvIHNl cnZpY2Ugc2hvcmV3YWxsIHJlc3RhcnQKIwojIExvYWRzIHBjaS1zdHViIGtlcm5lbCBtb2R1 bGUKc3VkbyBtb2Rwcm9iZSBwY2ktc3R1YgojCiMgUGFzc3Rocm91Z2ggRVZHQSBHZWZvcmNl IEdUWCA1NjAgMSBHQiBHRERSNQojCmVjaG8gIlBhc3N0aHJvdWdoIEVWR0EgR2Vmb3JjZSBH VFggNTYwIDEgR0IgR0REUjUiCnN1ZG8gY2htb2Qgbyt3IC9zeXMvYnVzL3BjaS9kcml2ZXJz L3BjaS1zdHViL25ld19pZApzdWRvIGNobW9kIG8rdyAvc3lzL2J1cy9wY2kvZGV2aWNlcy8w MDAwOjAxOjAwLjAvZHJpdmVyL3VuYmluZApzdWRvIGNobW9kIG8rdyAvc3lzL2J1cy9wY2kv ZHJpdmVycy9wY2ktc3R1Yi9iaW5kCmVjaG8gIjEwZGUgMTIwMSIgPiAvc3lzL2J1cy9wY2kv ZHJpdmVycy9wY2ktc3R1Yi9uZXdfaWQKZWNobyAiMDAwMDowMTowMC4wIiA+IC9zeXMvYnVz L3BjaS9kZXZpY2VzLzAwMDA6MDE6MDAuMC9kcml2ZXIvdW5iaW5kCmVjaG8gIjAwMDA6MDE6 MDAuMCIgPiAvc3lzL2J1cy9wY2kvZHJpdmVycy9wY2ktc3R1Yi9iaW5kCiMKIyBQYXNzdGhy b3VnaCBJbnRlbCBIRCBBdWRpbyBDb250cm9sbGVyCiMKZWNobyAiUGFzc3Rocm91Z2ggSW50 ZWwgSEQgQXVkaW8gQ29udHJvbGxlci4iCnN1ZG8gY2htb2Qgbyt3IC9zeXMvYnVzL3BjaS9k cml2ZXJzL3BjaS1zdHViL25ld19pZApzdWRvIGNobW9kIG8rdyAvc3lzL2J1cy9wY2kvZGV2 aWNlcy8wMDAwOjAwOjFiLjAvZHJpdmVyL3VuYmluZApzdWRvIGNobW9kIG8rdyAvc3lzL2J1 cy9wY2kvZHJpdmVycy9wY2ktc3R1Yi9iaW5kCmVjaG8gIjgwODYgM2E2ZSIgPiAvc3lzL2J1 cy9wY2kvZHJpdmVycy9wY2ktc3R1Yi9uZXdfaWQKZWNobyAiMDAwMDowMDoxYi4wIiA+IC9z eXMvYnVzL3BjaS9kZXZpY2VzLzAwMDA6MDA6MWIuMC9kcml2ZXIvdW5iaW5kCmVjaG8gIjAw MDA6MDA6MWIuMCIgPiAvc3lzL2J1cy9wY2kvZHJpdmVycy9wY2ktc3R1Yi9iaW5kCiMKIyBT bGVlcCBmb3IgMTAgc2VjcwojCnNsZWVwIDEwCiMKIyBQYXNzdGhyb3VnaCBVU0IgQ29udHJv bGxlciAjMQojCmVjaG8gIlBhc3N0aHJvdWdoIFVTQiBDb250cm9sbGVyICMxLiIKc3VkbyBj aG1vZCBvK3cgL3N5cy9idXMvcGNpL2RyaXZlcnMvcGNpLXN0dWIvbmV3X2lkCnN1ZG8gY2ht b2Qgbyt3IC9zeXMvYnVzL3BjaS9kZXZpY2VzLzAwMDA6MDA6MWEuMC9kcml2ZXIvdW5iaW5k CnN1ZG8gY2htb2Qgbyt3IC9zeXMvYnVzL3BjaS9kcml2ZXJzL3BjaS1zdHViL2JpbmQKZWNo byAiODA4NiAzYTY3IiA+IC9zeXMvYnVzL3BjaS9kcml2ZXJzL3BjaS1zdHViL25ld19pZApl Y2hvICIwMDAwOjAwOjFhLjAiID4gL3N5cy9idXMvcGNpL2RldmljZXMvMDAwMDowMDoxYS4w L2RyaXZlci91bmJpbmQKZWNobyAiMDAwMDowMDoxYS4wIiA+IC9zeXMvYnVzL3BjaS9kcml2 ZXJzL3BjaS1zdHViL2JpbmQKIwojIFBhc3N0aHJvdWdoIFVTQiBDb250cm9sbGVyICMyCiMK ZWNobyAiUGFzc3Rocm91Z2ggVVNCIENvbnRyb2xsZXIgIzIuIgpzdWRvIGNobW9kIG8rdyAv c3lzL2J1cy9wY2kvZHJpdmVycy9wY2ktc3R1Yi9uZXdfaWQKc3VkbyBjaG1vZCBvK3cgL3N5 cy9idXMvcGNpL2RldmljZXMvMDAwMDowMDoxYS4xL2RyaXZlci91bmJpbmQKc3VkbyBjaG1v ZCBvK3cgL3N5cy9idXMvcGNpL2RyaXZlcnMvcGNpLXN0dWIvYmluZAplY2hvICI4MDg2IDNh NjgiID4gL3N5cy9idXMvcGNpL2RyaXZlcnMvcGNpLXN0dWIvbmV3X2lkCmVjaG8gIjAwMDA6 MDA6MWEuMSIgPiAvc3lzL2J1cy9wY2kvZGV2aWNlcy8wMDAwOjAwOjFhLjEvZHJpdmVyL3Vu YmluZAplY2hvICIwMDAwOjAwOjFhLjEiID4gL3N5cy9idXMvcGNpL2RyaXZlcnMvcGNpLXN0 dWIvYmluZAojCiMgUGFzc3Rocm91Z2ggVVNCIENvbnRyb2xsZXIgIzMKIwplY2hvICJQYXNz dGhyb3VnaCBVU0IgQ29udHJvbGxlciAjMy4iCnN1ZG8gY2htb2Qgbyt3IC9zeXMvYnVzL3Bj aS9kcml2ZXJzL3BjaS1zdHViL25ld19pZApzdWRvIGNobW9kIG8rdyAvc3lzL2J1cy9wY2kv ZGV2aWNlcy8wMDAwOjAwOjFhLjIvZHJpdmVyL3VuYmluZApzdWRvIGNobW9kIG8rdyAvc3lz L2J1cy9wY2kvZHJpdmVycy9wY2ktc3R1Yi9iaW5kCmVjaG8gIjgwODYgM2E2OSIgPiAvc3lz L2J1cy9wY2kvZHJpdmVycy9wY2ktc3R1Yi9uZXdfaWQKZWNobyAiMDAwMDowMDoxYS4yIiA+ IC9zeXMvYnVzL3BjaS9kZXZpY2VzLzAwMDA6MDA6MWEuMi9kcml2ZXIvdW5iaW5kCmVjaG8g IjAwMDA6MDA6MWEuMiIgPiAvc3lzL2J1cy9wY2kvZHJpdmVycy9wY2ktc3R1Yi9iaW5kCiMK IyBQYXNzdGhyb3VnaCBVU0IgQ29udHJvbGxlciAjNAojCmVjaG8gIlBhc3N0aHJvdWdoIFVT QiBDb250cm9sbGVyICM0LiIKc3VkbyBjaG1vZCBvK3cgL3N5cy9idXMvcGNpL2RyaXZlcnMv cGNpLXN0dWIvbmV3X2lkCnN1ZG8gY2htb2Qgbyt3IC9zeXMvYnVzL3BjaS9kZXZpY2VzLzAw MDA6MDA6MWEuNy9kcml2ZXIvdW5iaW5kCnN1ZG8gY2htb2Qgbyt3IC9zeXMvYnVzL3BjaS9k cml2ZXJzL3BjaS1zdHViL2JpbmQKZWNobyAiODA4NiAzYTZjIiA+IC9zeXMvYnVzL3BjaS9k cml2ZXJzL3BjaS1zdHViL25ld19pZAplY2hvICIwMDAwOjAwOjFhLjciID4gL3N5cy9idXMv cGNpL2RldmljZXMvMDAwMDowMDoxYS43L2RyaXZlci91bmJpbmQKZWNobyAiMDAwMDowMDox YS43IiA+IC9zeXMvYnVzL3BjaS9kcml2ZXJzL3BjaS1zdHViL2JpbmQKIwojIFBhc3N0aHJv dWdoIFVTQiBDb250cm9sbGVyICM1CiMKZWNobyAiUGFzc3Rocm91Z2ggVVNCIENvbnRyb2xs ZXIgIzUuIgpzdWRvIGNobW9kIG8rdyAvc3lzL2J1cy9wY2kvZHJpdmVycy9wY2ktc3R1Yi9u ZXdfaWQKc3VkbyBjaG1vZCBvK3cgL3N5cy9idXMvcGNpL2RldmljZXMvMDAwMDowMDoxZC4w L2RyaXZlci91bmJpbmQKc3VkbyBjaG1vZCBvK3cgL3N5cy9idXMvcGNpL2RyaXZlcnMvcGNp LXN0dWIvYmluZAplY2hvICI4MDg2IDNhNjQiID4gL3N5cy9idXMvcGNpL2RyaXZlcnMvcGNp LXN0dWIvbmV3X2lkCmVjaG8gIjAwMDA6MDA6MWQuMCIgPiAvc3lzL2J1cy9wY2kvZGV2aWNl cy8wMDAwOjAwOjFkLjAvZHJpdmVyL3VuYmluZAplY2hvICIwMDAwOjAwOjFkLjAiID4gL3N5 cy9idXMvcGNpL2RyaXZlcnMvcGNpLXN0dWIvYmluZAojCiMgUGFzc3Rocm91Z2ggVVNCIENv bnRyb2xsZXIgIzYKIwplY2hvICJQYXNzdGhyb3VnaCBVU0IgQ29udHJvbGxlciAjNi4iCnN1 ZG8gY2htb2Qgbyt3IC9zeXMvYnVzL3BjaS9kcml2ZXJzL3BjaS1zdHViL25ld19pZApzdWRv IGNobW9kIG8rdyAvc3lzL2J1cy9wY2kvZGV2aWNlcy8wMDAwOjAwOjFkLjEvZHJpdmVyL3Vu YmluZApzdWRvIGNobW9kIG8rdyAvc3lzL2J1cy9wY2kvZHJpdmVycy9wY2ktc3R1Yi9iaW5k CmVjaG8gIjgwODYgM2E2NSIgPiAvc3lzL2J1cy9wY2kvZHJpdmVycy9wY2ktc3R1Yi9uZXdf aWQKZWNobyAiMDAwMDowMDoxZC4xIiA+IC9zeXMvYnVzL3BjaS9kZXZpY2VzLzAwMDA6MDA6 MWQuMS9kcml2ZXIvdW5iaW5kCmVjaG8gIjAwMDA6MDA6MWQuMSIgPiAvc3lzL2J1cy9wY2kv ZHJpdmVycy9wY2ktc3R1Yi9iaW5kCiMKIyBQYXNzdGhyb3VnaCBVU0IgQ29udHJvbGxlciAj NwojCmVjaG8gIlBhc3N0aHJvdWdoIFVTQiBDb250cm9sbGVyICM3LiIKc3VkbyBjaG1vZCBv K3cgL3N5cy9idXMvcGNpL2RyaXZlcnMvcGNpLXN0dWIvbmV3X2lkCnN1ZG8gY2htb2Qgbyt3 IC9zeXMvYnVzL3BjaS9kZXZpY2VzLzAwMDA6MDA6MWQuMi9kcml2ZXIvdW5iaW5kCnN1ZG8g Y2htb2Qgbyt3IC9zeXMvYnVzL3BjaS9kcml2ZXJzL3BjaS1zdHViL2JpbmQKZWNobyAiODA4 NiAzYTY2IiA+IC9zeXMvYnVzL3BjaS9kcml2ZXJzL3BjaS1zdHViL25ld19pZAplY2hvICIw MDAwOjAwOjFkLjIiID4gL3N5cy9idXMvcGNpL2RldmljZXMvMDAwMDowMDoxZC4yL2RyaXZl ci91bmJpbmQKZWNobyAiMDAwMDowMDoxZC4yIiA+IC9zeXMvYnVzL3BjaS9kcml2ZXJzL3Bj aS1zdHViL2JpbmQKIwojIFBhc3N0aHJvdWdoIFVTQiBDb250cm9sbGVyICM4CiMKZWNobyAi UGFzc3Rocm91Z2ggVVNCIENvbnRyb2xsZXIgIzguIgpzdWRvIGNobW9kIG8rdyAvc3lzL2J1 cy9wY2kvZHJpdmVycy9wY2ktc3R1Yi9uZXdfaWQKc3VkbyBjaG1vZCBvK3cgL3N5cy9idXMv cGNpL2RldmljZXMvMDAwMDowMDoxZC43L2RyaXZlci91bmJpbmQKc3VkbyBjaG1vZCBvK3cg L3N5cy9idXMvcGNpL2RyaXZlcnMvcGNpLXN0dWIvYmluZAplY2hvICI4MDg2IDNhNmEiID4g L3N5cy9idXMvcGNpL2RyaXZlcnMvcGNpLXN0dWIvbmV3X2lkCmVjaG8gIjAwMDA6MDA6MWQu NyIgPiAvc3lzL2J1cy9wY2kvZGV2aWNlcy8wMDAwOjAwOjFkLjcvZHJpdmVyL3VuYmluZApl Y2hvICIwMDAwOjAwOjFkLjciID4gL3N5cy9idXMvcGNpL2RyaXZlcnMvcGNpLXN0dWIvYmlu ZAoKIwojIFdhaXQgZm9yIDEwIHNlY29uZHMKIwpzbGVlcCAxMAojCiMgU3RhcnQgV2luZG93 cyBIVk0gZG9tVSB3aXRoIFZHQSBQYXNzdGhyb3VnaAojCiNzdWRvIHhsIGNyZWF0ZSAvZXRj L3hlbi9XaW5kb3dzWFBIb21lRWRpdGlvblNQMwpzdWRvIHhsIGNyZWF0ZSAvZXRjL3hlbi93 aW5kb3dzOAoK --------------070102050809000405040603 Content-Type: text/plain; charset=UTF-8; name="windows8" Content-Transfer-Encoding: base64 Content-Disposition: attachment; filename="windows8" IyBYTCBkb21haW4gY29uZmlndXJhdGlvbiBmaWxlIGZvciBXaW5kb3dzIDggQ29uc3VtZXIg UHJldmlldyA2NC1iaXQgRW5nbGlzaCBIVk0gZG9tVQojIFBsZWFzZSByZWZlciB0byAibWFu IHhsLmNmZyIgZm9yIGZ1cnRoZXIgZXhwbGFuYXRpb25zLgojIFNlZSBhbHNvIGRvY3MvbWlz Yy94bC1uZXR3b3JrLWNvbmZpZ3VyYXRpb24ubWFya2Rvd24gYW5kCiMgZG9jcy9taXNjL3hs LWRpc2stY29uZmlndXJhdGlvbi50eHQKIyBXcml0dGVuIGJ5IFRlbyBFbiBNaW5nIChaaGFu ZyBFbm1pbmcpCiMgRW1haWw6IHRlby5lbi5taW5nQGdtYWlsLmNvbQojIE1vYmlsZSBQaG9u ZTogKzY1LTgzNjktMjYxOAojIENvdW50cnk6IFNpbmdhcG9yZQojIERhdGU6IDE4IE1hciAy MDEyIFN1bgpuYW1lPSJXaW5kb3dzOCIKIyBQcm9kdWN0IEtleTogRE5KWEotN1hCVzgtMjM3 OFQtWDIyVFgtQktHN0oKYnVpbGRlcj0iaHZtIgp2Y3B1cz0yCm1lbW9yeT0yMDQ4Cm9uX3Bv d2Vyb2ZmPSJkZXN0cm95Igpvbl9yZWJvb3Q9InJlc3RhcnQiCm9uX2NyYXNoPSJkZXN0cm95 IgpkaXNrPVsgJ2Zvcm1hdD1yYXcsIHZkZXY9aGRhLCBhY2Nlc3M9cncsIHRhcmdldD0vZXRj L3hlbi9pbWFnZXMvd2luZG93czguaW1nJywgJ2Zvcm1hdD1yYXcsIHZkZXY9aGRjLCBhY2Nl c3M9cm8sIGRldnR5cGU9Y2Ryb20sIHRhcmdldD0vaG9tZS90ZW8tZW4tbWluZy9XaW5kb3dz OC1SZWxlYXNlUHJldmlldy02NGJpdC1FbmdsaXNoLmlzbycgXQojdmlmPVsgJ2JyaWRnZT12 aXJicjAsdHlwZT1pb2VtdSxtb2RlbD1lMTAwMCcgXQojYm9vdD1bY3xkfG5dCiNTZWxlY3Rz IHRoZSBlbXVsYXRlZCB2aXJ0dWFsIGRldmljZSB0byBib290IGZyb20uIE9wdGlvbnMgYXJl IGhhcmQgZGlzayAoYyksIGNkLXJvbSAoZCkgb3IgbmV0d29yay9QWEUgKG4pLgojTXVsdGlw bGUgb3B0aW9ucyBjYW4gYmUgZ2l2ZW4gYW5kIHdpbGwgYmUgYXR0ZW1wdGVkIGluIHRoZSBv cmRlciB0aGV5IGFyZSBnaXZlbi4gZS5nLiB0byBib290IGZyb20gY2Qtcm9tCiNidXQgZmFs bGJhY2sgdG8gdGhlIGhhcmQgZGlzayB5b3UgY2FuIGdpdmUgZGMuIFRoZSBkZWZhdWx0IGlz IGNkLgpib290PSJkYyIKYWNwaT0xCiN4ZW5fcGxhdGZvcm1fcGNpPTEKI3ZpcmlkaWFuPTEK I3N0ZHZnYT0xCnZuYz0xCnZuY2xpc3Rlbj0iMTkyLjE2OC4xLjIiCnZuY2Rpc3BsYXk9MAp2 bmN1bnVzZWQ9MQp2bmNwYXNzd2Q9IiIKc2RsPTAKdXNiPTEKdXNiZGV2aWNlPSJ0YWJsZXQi CiMgRW5hYmxlIFhlbiBWR0EgUGFzc3Rocm91Z2gKZ2Z4X3Bhc3N0aHJ1PTEKIyBWR0EgUGFz c3Rocm91Z2ggRVZHQSBHZWZvcmNlIEdUWCA1NjAgMSBHQiBHRERSNS4KcGNpID0gWyAnMDE6 MDAuMCcsJzAwOjFiLjAnLCcwMDoxYS4wJywnMDA6MWEuMScsJzAwOjFhLjInLCcwMDoxYS43 JywnMDA6MWQuMCcsJzAwOjFkLjEnLCcwMDoxZC4yJywnMDA6MWQuNycgXQojIFBDSSBQYXNz dGhyb3VnaCBJbnRlbCBIRCBBdWRpbyBDb250cm9sbGVyLgojcGNpID0gWyAnMDA6MWIuMCcg XQojIFBDSSBQYXNzdGhyb3VnaCBhbGwgdGhlIFVTQiBDb250cm9sbGVycy4KIyBwY2kgPSBb ICcwMDoxYS4wJywnMDA6MWEuMScsJzAwOjFhLjInLCcwMDoxYS43JywnMDA6MWQuMCcsJzAw OjFkLjEnLCcwMDoxZC4yJywnMDA6MWQuNycgXQoKCg== --------------070102050809000405040603 Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users --------------070102050809000405040603-- From xen-users-bounces@lists.xen.org Sat Sep 29 16:10:45 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Sat, 29 Sep 2012 16:10:45 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1THzbw-0002e7-I6; Sat, 29 Sep 2012 16:09:48 +0000 Received: from mail27.messagelabs.com ([193.109.254.147]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1THzbu-0002dp-9Y; Sat, 29 Sep 2012 16:09:46 +0000 X-Env-Sender: singapore.mr.teo.en.ming@gmail.com X-Msg-Ref: server-10.tower-27.messagelabs.com!1348934977!7639841!1 X-Originating-IP: [209.85.220.45] X-SpamReason: No, hits=0.3 required=7.0 tests=ML_RADAR_SPEW_LINKS_14, RCVD_BY_IP,spamassassin: X-StarScan-Received: X-StarScan-Version: 6.6.1.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 4583 invoked from network); 29 Sep 2012 16:09:39 -0000 Received: from mail-pa0-f45.google.com (HELO mail-pa0-f45.google.com) (209.85.220.45) by server-10.tower-27.messagelabs.com with RC4-SHA encrypted SMTP; 29 Sep 2012 16:09:39 -0000 Received: by padfb10 with SMTP id fb10so3147816pad.32 for ; Sat, 29 Sep 2012 09:09:36 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:user-agent:mime-version:to:cc:subject :references:in-reply-to:content-type; bh=qRfFtARMCGhTFZFnk1WcoJ8EVH1Q2JJayUgnjKpLVLk=; b=povE/bgFNJE8NxgETMp2aKJDQ2rDcpvoQ9LHd9P+ZiZ+YDsdpJNw3GF1f8vMdxg7Ot l87K2NwIHc4RcNNeiOvkoOw593fVEKnub4ZO3ldPDgaxUwoxRAf3ONNq2FqPZKxdeHD8 T7+xBGkGeCbbEaGACIUTBmQNrY8dl8X/mKlZt65ebGE7ayuugW3Ydhc5estMO5OPslUj OTnfB/qmm0L6JUblijF69xoANYZd/DjpayK5FSKeAapYbkA+Bft7EUS9IKQIiXiRzDOa QzBLI2Quqc5d9YDRP5D/xGFQ6jCIuIlvqiT+zKe7AQiPhoYsxWwLMucg9Ah4rnxPjJqI 9QXA== Received: by 10.68.224.133 with SMTP id rc5mr28518968pbc.130.1348934976787; Sat, 29 Sep 2012 09:09:36 -0700 (PDT) Received: from [192.168.1.2] (cm152.gamma205.maxonline.com.sg. [202.156.205.152]) by mx.google.com with ESMTPS id b4sm7398767pbw.28.2012.09.29.09.09.34 (version=SSLv3 cipher=OTHER); Sat, 29 Sep 2012 09:09:35 -0700 (PDT) Message-ID: <50671D3D.1010304@gmail.com> Date: Sun, 30 Sep 2012 00:09:33 +0800 From: "Teo En Ming (Zhang Enming)" User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:15.0) Gecko/20120912 Thunderbird/15.0.1 MIME-Version: 1.0 To: "Teo En Ming (Zhang Enming)" References: <5066F922.1090305@gmail.com> In-Reply-To: <5066F922.1090305@gmail.com> Content-Type: multipart/mixed; boundary="------------070102050809000405040603" Cc: "xen-users@lists.xen.org" , "xen-devel@lists.xen.org" Subject: Re: [Xen-users] Unable to start Windows 8 HVM guest with Xen VGA Passthrough with Xen 4.2.1-pre X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org This is a multi-part message in MIME format. --------------070102050809000405040603 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit On 29/09/2012 21:35, Teo En Ming (Zhang Enming) wrote: > Hi, > > I have applied Xen VGA passthrough patches from David Techer's > personal website to Xen 4.2.1-pre source tree. Everything compiled and > installed smoothly. But when I tried to start Windows 8 HVM domU with > VGA passthrough, it gave me the following error: > > xc: error: unable to allocate memory to the HVM guest. (16: device or > resource busy): Internal error. > > There are no issues with Xen 4.2-unstable changeset 25099 however. > Attached are screenshots of the errors for Xen 4.2.1-pre and Xen configuration files. The following are links to screenshots of the errors for Xen 4.2.1-pre. http://i45.tinypic.com/2j3s7pj.jpg http://i45.tinypic.com/95myc3.jpg -- Yours sincerely, Mr. Teo En Ming (Zhang Enming) Singapore --------------070102050809000405040603 Content-Type: text/plain; charset=UTF-8; name="start-windows" Content-Transfer-Encoding: base64 Content-Disposition: attachment; filename="start-windows" IyEvYmluL3NoCnNldCAteAojCiMgU3RhcnRzIFNob3Jld2FsbCBGaXJld2FsbApzdWRvIHNl cnZpY2Ugc2hvcmV3YWxsIHJlc3RhcnQKIwojIExvYWRzIHBjaS1zdHViIGtlcm5lbCBtb2R1 bGUKc3VkbyBtb2Rwcm9iZSBwY2ktc3R1YgojCiMgUGFzc3Rocm91Z2ggRVZHQSBHZWZvcmNl IEdUWCA1NjAgMSBHQiBHRERSNQojCmVjaG8gIlBhc3N0aHJvdWdoIEVWR0EgR2Vmb3JjZSBH VFggNTYwIDEgR0IgR0REUjUiCnN1ZG8gY2htb2Qgbyt3IC9zeXMvYnVzL3BjaS9kcml2ZXJz L3BjaS1zdHViL25ld19pZApzdWRvIGNobW9kIG8rdyAvc3lzL2J1cy9wY2kvZGV2aWNlcy8w MDAwOjAxOjAwLjAvZHJpdmVyL3VuYmluZApzdWRvIGNobW9kIG8rdyAvc3lzL2J1cy9wY2kv ZHJpdmVycy9wY2ktc3R1Yi9iaW5kCmVjaG8gIjEwZGUgMTIwMSIgPiAvc3lzL2J1cy9wY2kv ZHJpdmVycy9wY2ktc3R1Yi9uZXdfaWQKZWNobyAiMDAwMDowMTowMC4wIiA+IC9zeXMvYnVz L3BjaS9kZXZpY2VzLzAwMDA6MDE6MDAuMC9kcml2ZXIvdW5iaW5kCmVjaG8gIjAwMDA6MDE6 MDAuMCIgPiAvc3lzL2J1cy9wY2kvZHJpdmVycy9wY2ktc3R1Yi9iaW5kCiMKIyBQYXNzdGhy b3VnaCBJbnRlbCBIRCBBdWRpbyBDb250cm9sbGVyCiMKZWNobyAiUGFzc3Rocm91Z2ggSW50 ZWwgSEQgQXVkaW8gQ29udHJvbGxlci4iCnN1ZG8gY2htb2Qgbyt3IC9zeXMvYnVzL3BjaS9k cml2ZXJzL3BjaS1zdHViL25ld19pZApzdWRvIGNobW9kIG8rdyAvc3lzL2J1cy9wY2kvZGV2 aWNlcy8wMDAwOjAwOjFiLjAvZHJpdmVyL3VuYmluZApzdWRvIGNobW9kIG8rdyAvc3lzL2J1 cy9wY2kvZHJpdmVycy9wY2ktc3R1Yi9iaW5kCmVjaG8gIjgwODYgM2E2ZSIgPiAvc3lzL2J1 cy9wY2kvZHJpdmVycy9wY2ktc3R1Yi9uZXdfaWQKZWNobyAiMDAwMDowMDoxYi4wIiA+IC9z eXMvYnVzL3BjaS9kZXZpY2VzLzAwMDA6MDA6MWIuMC9kcml2ZXIvdW5iaW5kCmVjaG8gIjAw MDA6MDA6MWIuMCIgPiAvc3lzL2J1cy9wY2kvZHJpdmVycy9wY2ktc3R1Yi9iaW5kCiMKIyBT bGVlcCBmb3IgMTAgc2VjcwojCnNsZWVwIDEwCiMKIyBQYXNzdGhyb3VnaCBVU0IgQ29udHJv bGxlciAjMQojCmVjaG8gIlBhc3N0aHJvdWdoIFVTQiBDb250cm9sbGVyICMxLiIKc3VkbyBj aG1vZCBvK3cgL3N5cy9idXMvcGNpL2RyaXZlcnMvcGNpLXN0dWIvbmV3X2lkCnN1ZG8gY2ht b2Qgbyt3IC9zeXMvYnVzL3BjaS9kZXZpY2VzLzAwMDA6MDA6MWEuMC9kcml2ZXIvdW5iaW5k CnN1ZG8gY2htb2Qgbyt3IC9zeXMvYnVzL3BjaS9kcml2ZXJzL3BjaS1zdHViL2JpbmQKZWNo byAiODA4NiAzYTY3IiA+IC9zeXMvYnVzL3BjaS9kcml2ZXJzL3BjaS1zdHViL25ld19pZApl Y2hvICIwMDAwOjAwOjFhLjAiID4gL3N5cy9idXMvcGNpL2RldmljZXMvMDAwMDowMDoxYS4w L2RyaXZlci91bmJpbmQKZWNobyAiMDAwMDowMDoxYS4wIiA+IC9zeXMvYnVzL3BjaS9kcml2 ZXJzL3BjaS1zdHViL2JpbmQKIwojIFBhc3N0aHJvdWdoIFVTQiBDb250cm9sbGVyICMyCiMK ZWNobyAiUGFzc3Rocm91Z2ggVVNCIENvbnRyb2xsZXIgIzIuIgpzdWRvIGNobW9kIG8rdyAv c3lzL2J1cy9wY2kvZHJpdmVycy9wY2ktc3R1Yi9uZXdfaWQKc3VkbyBjaG1vZCBvK3cgL3N5 cy9idXMvcGNpL2RldmljZXMvMDAwMDowMDoxYS4xL2RyaXZlci91bmJpbmQKc3VkbyBjaG1v ZCBvK3cgL3N5cy9idXMvcGNpL2RyaXZlcnMvcGNpLXN0dWIvYmluZAplY2hvICI4MDg2IDNh NjgiID4gL3N5cy9idXMvcGNpL2RyaXZlcnMvcGNpLXN0dWIvbmV3X2lkCmVjaG8gIjAwMDA6 MDA6MWEuMSIgPiAvc3lzL2J1cy9wY2kvZGV2aWNlcy8wMDAwOjAwOjFhLjEvZHJpdmVyL3Vu YmluZAplY2hvICIwMDAwOjAwOjFhLjEiID4gL3N5cy9idXMvcGNpL2RyaXZlcnMvcGNpLXN0 dWIvYmluZAojCiMgUGFzc3Rocm91Z2ggVVNCIENvbnRyb2xsZXIgIzMKIwplY2hvICJQYXNz dGhyb3VnaCBVU0IgQ29udHJvbGxlciAjMy4iCnN1ZG8gY2htb2Qgbyt3IC9zeXMvYnVzL3Bj aS9kcml2ZXJzL3BjaS1zdHViL25ld19pZApzdWRvIGNobW9kIG8rdyAvc3lzL2J1cy9wY2kv ZGV2aWNlcy8wMDAwOjAwOjFhLjIvZHJpdmVyL3VuYmluZApzdWRvIGNobW9kIG8rdyAvc3lz L2J1cy9wY2kvZHJpdmVycy9wY2ktc3R1Yi9iaW5kCmVjaG8gIjgwODYgM2E2OSIgPiAvc3lz L2J1cy9wY2kvZHJpdmVycy9wY2ktc3R1Yi9uZXdfaWQKZWNobyAiMDAwMDowMDoxYS4yIiA+ IC9zeXMvYnVzL3BjaS9kZXZpY2VzLzAwMDA6MDA6MWEuMi9kcml2ZXIvdW5iaW5kCmVjaG8g IjAwMDA6MDA6MWEuMiIgPiAvc3lzL2J1cy9wY2kvZHJpdmVycy9wY2ktc3R1Yi9iaW5kCiMK IyBQYXNzdGhyb3VnaCBVU0IgQ29udHJvbGxlciAjNAojCmVjaG8gIlBhc3N0aHJvdWdoIFVT QiBDb250cm9sbGVyICM0LiIKc3VkbyBjaG1vZCBvK3cgL3N5cy9idXMvcGNpL2RyaXZlcnMv cGNpLXN0dWIvbmV3X2lkCnN1ZG8gY2htb2Qgbyt3IC9zeXMvYnVzL3BjaS9kZXZpY2VzLzAw MDA6MDA6MWEuNy9kcml2ZXIvdW5iaW5kCnN1ZG8gY2htb2Qgbyt3IC9zeXMvYnVzL3BjaS9k cml2ZXJzL3BjaS1zdHViL2JpbmQKZWNobyAiODA4NiAzYTZjIiA+IC9zeXMvYnVzL3BjaS9k cml2ZXJzL3BjaS1zdHViL25ld19pZAplY2hvICIwMDAwOjAwOjFhLjciID4gL3N5cy9idXMv cGNpL2RldmljZXMvMDAwMDowMDoxYS43L2RyaXZlci91bmJpbmQKZWNobyAiMDAwMDowMDox YS43IiA+IC9zeXMvYnVzL3BjaS9kcml2ZXJzL3BjaS1zdHViL2JpbmQKIwojIFBhc3N0aHJv dWdoIFVTQiBDb250cm9sbGVyICM1CiMKZWNobyAiUGFzc3Rocm91Z2ggVVNCIENvbnRyb2xs ZXIgIzUuIgpzdWRvIGNobW9kIG8rdyAvc3lzL2J1cy9wY2kvZHJpdmVycy9wY2ktc3R1Yi9u ZXdfaWQKc3VkbyBjaG1vZCBvK3cgL3N5cy9idXMvcGNpL2RldmljZXMvMDAwMDowMDoxZC4w L2RyaXZlci91bmJpbmQKc3VkbyBjaG1vZCBvK3cgL3N5cy9idXMvcGNpL2RyaXZlcnMvcGNp LXN0dWIvYmluZAplY2hvICI4MDg2IDNhNjQiID4gL3N5cy9idXMvcGNpL2RyaXZlcnMvcGNp LXN0dWIvbmV3X2lkCmVjaG8gIjAwMDA6MDA6MWQuMCIgPiAvc3lzL2J1cy9wY2kvZGV2aWNl cy8wMDAwOjAwOjFkLjAvZHJpdmVyL3VuYmluZAplY2hvICIwMDAwOjAwOjFkLjAiID4gL3N5 cy9idXMvcGNpL2RyaXZlcnMvcGNpLXN0dWIvYmluZAojCiMgUGFzc3Rocm91Z2ggVVNCIENv bnRyb2xsZXIgIzYKIwplY2hvICJQYXNzdGhyb3VnaCBVU0IgQ29udHJvbGxlciAjNi4iCnN1 ZG8gY2htb2Qgbyt3IC9zeXMvYnVzL3BjaS9kcml2ZXJzL3BjaS1zdHViL25ld19pZApzdWRv IGNobW9kIG8rdyAvc3lzL2J1cy9wY2kvZGV2aWNlcy8wMDAwOjAwOjFkLjEvZHJpdmVyL3Vu YmluZApzdWRvIGNobW9kIG8rdyAvc3lzL2J1cy9wY2kvZHJpdmVycy9wY2ktc3R1Yi9iaW5k CmVjaG8gIjgwODYgM2E2NSIgPiAvc3lzL2J1cy9wY2kvZHJpdmVycy9wY2ktc3R1Yi9uZXdf aWQKZWNobyAiMDAwMDowMDoxZC4xIiA+IC9zeXMvYnVzL3BjaS9kZXZpY2VzLzAwMDA6MDA6 MWQuMS9kcml2ZXIvdW5iaW5kCmVjaG8gIjAwMDA6MDA6MWQuMSIgPiAvc3lzL2J1cy9wY2kv ZHJpdmVycy9wY2ktc3R1Yi9iaW5kCiMKIyBQYXNzdGhyb3VnaCBVU0IgQ29udHJvbGxlciAj NwojCmVjaG8gIlBhc3N0aHJvdWdoIFVTQiBDb250cm9sbGVyICM3LiIKc3VkbyBjaG1vZCBv K3cgL3N5cy9idXMvcGNpL2RyaXZlcnMvcGNpLXN0dWIvbmV3X2lkCnN1ZG8gY2htb2Qgbyt3 IC9zeXMvYnVzL3BjaS9kZXZpY2VzLzAwMDA6MDA6MWQuMi9kcml2ZXIvdW5iaW5kCnN1ZG8g Y2htb2Qgbyt3IC9zeXMvYnVzL3BjaS9kcml2ZXJzL3BjaS1zdHViL2JpbmQKZWNobyAiODA4 NiAzYTY2IiA+IC9zeXMvYnVzL3BjaS9kcml2ZXJzL3BjaS1zdHViL25ld19pZAplY2hvICIw MDAwOjAwOjFkLjIiID4gL3N5cy9idXMvcGNpL2RldmljZXMvMDAwMDowMDoxZC4yL2RyaXZl ci91bmJpbmQKZWNobyAiMDAwMDowMDoxZC4yIiA+IC9zeXMvYnVzL3BjaS9kcml2ZXJzL3Bj aS1zdHViL2JpbmQKIwojIFBhc3N0aHJvdWdoIFVTQiBDb250cm9sbGVyICM4CiMKZWNobyAi UGFzc3Rocm91Z2ggVVNCIENvbnRyb2xsZXIgIzguIgpzdWRvIGNobW9kIG8rdyAvc3lzL2J1 cy9wY2kvZHJpdmVycy9wY2ktc3R1Yi9uZXdfaWQKc3VkbyBjaG1vZCBvK3cgL3N5cy9idXMv cGNpL2RldmljZXMvMDAwMDowMDoxZC43L2RyaXZlci91bmJpbmQKc3VkbyBjaG1vZCBvK3cg L3N5cy9idXMvcGNpL2RyaXZlcnMvcGNpLXN0dWIvYmluZAplY2hvICI4MDg2IDNhNmEiID4g L3N5cy9idXMvcGNpL2RyaXZlcnMvcGNpLXN0dWIvbmV3X2lkCmVjaG8gIjAwMDA6MDA6MWQu NyIgPiAvc3lzL2J1cy9wY2kvZGV2aWNlcy8wMDAwOjAwOjFkLjcvZHJpdmVyL3VuYmluZApl Y2hvICIwMDAwOjAwOjFkLjciID4gL3N5cy9idXMvcGNpL2RyaXZlcnMvcGNpLXN0dWIvYmlu ZAoKIwojIFdhaXQgZm9yIDEwIHNlY29uZHMKIwpzbGVlcCAxMAojCiMgU3RhcnQgV2luZG93 cyBIVk0gZG9tVSB3aXRoIFZHQSBQYXNzdGhyb3VnaAojCiNzdWRvIHhsIGNyZWF0ZSAvZXRj L3hlbi9XaW5kb3dzWFBIb21lRWRpdGlvblNQMwpzdWRvIHhsIGNyZWF0ZSAvZXRjL3hlbi93 aW5kb3dzOAoK --------------070102050809000405040603 Content-Type: text/plain; charset=UTF-8; name="windows8" Content-Transfer-Encoding: base64 Content-Disposition: attachment; filename="windows8" IyBYTCBkb21haW4gY29uZmlndXJhdGlvbiBmaWxlIGZvciBXaW5kb3dzIDggQ29uc3VtZXIg UHJldmlldyA2NC1iaXQgRW5nbGlzaCBIVk0gZG9tVQojIFBsZWFzZSByZWZlciB0byAibWFu IHhsLmNmZyIgZm9yIGZ1cnRoZXIgZXhwbGFuYXRpb25zLgojIFNlZSBhbHNvIGRvY3MvbWlz Yy94bC1uZXR3b3JrLWNvbmZpZ3VyYXRpb24ubWFya2Rvd24gYW5kCiMgZG9jcy9taXNjL3hs LWRpc2stY29uZmlndXJhdGlvbi50eHQKIyBXcml0dGVuIGJ5IFRlbyBFbiBNaW5nIChaaGFu ZyBFbm1pbmcpCiMgRW1haWw6IHRlby5lbi5taW5nQGdtYWlsLmNvbQojIE1vYmlsZSBQaG9u ZTogKzY1LTgzNjktMjYxOAojIENvdW50cnk6IFNpbmdhcG9yZQojIERhdGU6IDE4IE1hciAy MDEyIFN1bgpuYW1lPSJXaW5kb3dzOCIKIyBQcm9kdWN0IEtleTogRE5KWEotN1hCVzgtMjM3 OFQtWDIyVFgtQktHN0oKYnVpbGRlcj0iaHZtIgp2Y3B1cz0yCm1lbW9yeT0yMDQ4Cm9uX3Bv d2Vyb2ZmPSJkZXN0cm95Igpvbl9yZWJvb3Q9InJlc3RhcnQiCm9uX2NyYXNoPSJkZXN0cm95 IgpkaXNrPVsgJ2Zvcm1hdD1yYXcsIHZkZXY9aGRhLCBhY2Nlc3M9cncsIHRhcmdldD0vZXRj L3hlbi9pbWFnZXMvd2luZG93czguaW1nJywgJ2Zvcm1hdD1yYXcsIHZkZXY9aGRjLCBhY2Nl c3M9cm8sIGRldnR5cGU9Y2Ryb20sIHRhcmdldD0vaG9tZS90ZW8tZW4tbWluZy9XaW5kb3dz OC1SZWxlYXNlUHJldmlldy02NGJpdC1FbmdsaXNoLmlzbycgXQojdmlmPVsgJ2JyaWRnZT12 aXJicjAsdHlwZT1pb2VtdSxtb2RlbD1lMTAwMCcgXQojYm9vdD1bY3xkfG5dCiNTZWxlY3Rz IHRoZSBlbXVsYXRlZCB2aXJ0dWFsIGRldmljZSB0byBib290IGZyb20uIE9wdGlvbnMgYXJl IGhhcmQgZGlzayAoYyksIGNkLXJvbSAoZCkgb3IgbmV0d29yay9QWEUgKG4pLgojTXVsdGlw bGUgb3B0aW9ucyBjYW4gYmUgZ2l2ZW4gYW5kIHdpbGwgYmUgYXR0ZW1wdGVkIGluIHRoZSBv cmRlciB0aGV5IGFyZSBnaXZlbi4gZS5nLiB0byBib290IGZyb20gY2Qtcm9tCiNidXQgZmFs bGJhY2sgdG8gdGhlIGhhcmQgZGlzayB5b3UgY2FuIGdpdmUgZGMuIFRoZSBkZWZhdWx0IGlz IGNkLgpib290PSJkYyIKYWNwaT0xCiN4ZW5fcGxhdGZvcm1fcGNpPTEKI3ZpcmlkaWFuPTEK I3N0ZHZnYT0xCnZuYz0xCnZuY2xpc3Rlbj0iMTkyLjE2OC4xLjIiCnZuY2Rpc3BsYXk9MAp2 bmN1bnVzZWQ9MQp2bmNwYXNzd2Q9IiIKc2RsPTAKdXNiPTEKdXNiZGV2aWNlPSJ0YWJsZXQi CiMgRW5hYmxlIFhlbiBWR0EgUGFzc3Rocm91Z2gKZ2Z4X3Bhc3N0aHJ1PTEKIyBWR0EgUGFz c3Rocm91Z2ggRVZHQSBHZWZvcmNlIEdUWCA1NjAgMSBHQiBHRERSNS4KcGNpID0gWyAnMDE6 MDAuMCcsJzAwOjFiLjAnLCcwMDoxYS4wJywnMDA6MWEuMScsJzAwOjFhLjInLCcwMDoxYS43 JywnMDA6MWQuMCcsJzAwOjFkLjEnLCcwMDoxZC4yJywnMDA6MWQuNycgXQojIFBDSSBQYXNz dGhyb3VnaCBJbnRlbCBIRCBBdWRpbyBDb250cm9sbGVyLgojcGNpID0gWyAnMDA6MWIuMCcg XQojIFBDSSBQYXNzdGhyb3VnaCBhbGwgdGhlIFVTQiBDb250cm9sbGVycy4KIyBwY2kgPSBb ICcwMDoxYS4wJywnMDA6MWEuMScsJzAwOjFhLjInLCcwMDoxYS43JywnMDA6MWQuMCcsJzAw OjFkLjEnLCcwMDoxZC4yJywnMDA6MWQuNycgXQoKCg== --------------070102050809000405040603 Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users --------------070102050809000405040603-- From xen-users-bounces@lists.xen.org Sat Sep 29 16:23:23 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Sat, 29 Sep 2012 16:23:23 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1THzoF-00034K-Jj; Sat, 29 Sep 2012 16:22:31 +0000 Received: from mail27.messagelabs.com ([193.109.254.147]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1THzoE-000342-5K; Sat, 29 Sep 2012 16:22:30 +0000 X-Env-Sender: cdelorme@gmail.com X-Msg-Ref: server-15.tower-27.messagelabs.com!1348935742!5866305!1 X-Originating-IP: [209.85.214.173] X-SpamReason: No, hits=0.4 required=7.0 tests=HTML_30_40,HTML_MESSAGE, ML_RADAR_SPEW_LINKS_14,RCVD_BY_IP,spamassassin: X-StarScan-Received: X-StarScan-Version: 6.6.1.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 20374 invoked from network); 29 Sep 2012 16:22:23 -0000 Received: from mail-ob0-f173.google.com (HELO mail-ob0-f173.google.com) (209.85.214.173) by server-15.tower-27.messagelabs.com with RC4-SHA encrypted SMTP; 29 Sep 2012 16:22:23 -0000 Received: by obbwc18 with SMTP id wc18so2390814obb.32 for ; Sat, 29 Sep 2012 09:22:21 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=cuthgEU24jdUcadhi8XBWi8lXF439BTxjfsq7aabTtg=; b=b6u+ed3N81uS408n88iXUYQAKQSiaqE4p9jAt6LaTnQVy0IqKfd5hKxcujG46n4w/R QkH2A2HSt08FdaQD1dtw8ZP2nzFFLi1TE1QkmAHIpNM2dFry5xXotcllfqWRjjMWjiLA ITTVB/4ehJEBxUpQQ0CkNF9bvPtJFxfrtaXn0v9XYinSDg+0mAc+1lDxWX1auHSY++4D C0ASxGWoLM7J6Hp/d3IITNZGKXL78enbaGzNwMylI5KjUOn8CM+MqbWMm7cHKmcdXHd3 dQmMrO8lKpNS68e79jUJURznnrBdkNciiQPBc1KiVLe93bULFq9aZYfHqUqSrWl5zUoG XTcg== MIME-Version: 1.0 Received: by 10.60.170.229 with SMTP id ap5mr8193776oec.101.1348935741806; Sat, 29 Sep 2012 09:22:21 -0700 (PDT) Received: by 10.76.19.148 with HTTP; Sat, 29 Sep 2012 09:22:21 -0700 (PDT) In-Reply-To: <50671D3D.1010304@gmail.com> References: <5066F922.1090305@gmail.com> <50671D3D.1010304@gmail.com> Date: Sat, 29 Sep 2012 12:22:21 -0400 Message-ID: From: Casey DeLorme To: "Teo En Ming (Zhang Enming)" Cc: "xen-users@lists.xen.org" , "xen-devel@lists.xen.org" Subject: Re: [Xen-users] Unable to start Windows 8 HVM guest with Xen VGA Passthrough with Xen 4.2.1-pre X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============2112485417139751700==" Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org --===============2112485417139751700== Content-Type: multipart/alternative; boundary=bcaec54b4ac0b7182a04cad993db --bcaec54b4ac0b7182a04cad993db Content-Type: text/plain; charset=ISO-8859-1 Hello Teo, That output is identical to the errors I had a few days ago, which was related to available RAM. Ian helped me debug it, said xl was having a ballooning problem and couldn't free up enough RAM in time to start my HVM. His suggested solution was to assign a fixed amount of RAM to Dom0 and turn off ballooning. Prior to this I had been letting Dom0 take all the RAM, but this problem was fixed by adding dom0_mem to grub.cfg and setting a fixed value. Have you tried re-running the xl create command after the first error? There are commands to move RAM around at run-time as well that you could try. ~Casey On Sat, Sep 29, 2012 at 12:09 PM, Teo En Ming (Zhang Enming) < singapore.mr.teo.en.ming@gmail.com> wrote: > On 29/09/2012 21:35, Teo En Ming (Zhang Enming) wrote: > >> Hi, >> >> I have applied Xen VGA passthrough patches from David Techer's >> personal website to Xen 4.2.1-pre source tree. Everything compiled and >> installed smoothly. But when I tried to start Windows 8 HVM domU with >> VGA passthrough, it gave me the following error: >> >> xc: error: unable to allocate memory to the HVM guest. (16: device or >> resource busy): Internal error. >> >> There are no issues with Xen 4.2-unstable changeset 25099 however. >> >> > Attached are screenshots of the errors for Xen 4.2.1-pre and Xen > configuration files. > > The following are links to screenshots of the errors for Xen 4.2.1-pre. > > http://i45.tinypic.com/**2j3s7pj.jpg > > http://i45.tinypic.com/95myc3.**jpg > > > -- > Yours sincerely, > > Mr. Teo En Ming (Zhang Enming) > Singapore > > > > _______________________________________________ > Xen-users mailing list > Xen-users@lists.xen.org > http://lists.xen.org/xen-users > --bcaec54b4ac0b7182a04cad993db Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable
Hello Teo,

That output is identical to t= he errors I had a few days ago, which was related to available RAM.

Ian helped me debug it, said xl was having a ballooning p= roblem and couldn't free up enough RAM in time to start my HVM.

His suggested solution was to assign a fixed amount of = RAM to Dom0 and turn off ballooning.

Prior to this= I had been letting Dom0 take all the RAM, but this problem was fixed by ad= ding dom0_mem to grub.cfg and setting a fixed value.

Have you tried re-running the xl create command after t= he first error? There are commands to move RAM around at run-time as well t= hat you could try.

~Casey

On Sat, Sep 29, 2012 at 12:09 PM, Teo En Ming (Z= hang Enming) <singapore.mr.teo.en.ming@gmail.com><= /span> wrote:
On 29/09/2012 21:35, Teo E= n Ming (Zhang Enming) wrote:
Hi,

I have applied Xen VGA passthrough patches from David Techer's
personal website to Xen 4.2.1-pre source tree. Everything compiled and
installed smoothly. But when I tried to start Windows 8 HVM domU with
VGA passthrough, it gave me the following error:

xc: error: unable to allocate memory to the HVM guest. (16: device or
resource busy): Internal error.

There are no issues with Xen 4.2-unstable changeset 25099 however.


Attached are screenshots of the errors for Xen 4.2.1-pre and Xen configurat= ion files.

The following are links to screenshots of the errors for Xen 4.2.1-pre.

http://i45= .tinypic.com/2j3s7pj.jpg

http://i45.= tinypic.com/95myc3.jpg

--
Yours sincerely,

Mr. Teo En Ming (Zhang Enming)
Singapore



_______________________________________________
Xen-users mailing list
Xen-users@lists.xen.org
http://lists.x= en.org/xen-users

--bcaec54b4ac0b7182a04cad993db-- --===============2112485417139751700== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users --===============2112485417139751700==-- From xen-users-bounces@lists.xen.org Sat Sep 29 16:23:23 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Sat, 29 Sep 2012 16:23:23 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1THzoF-00034K-Jj; Sat, 29 Sep 2012 16:22:31 +0000 Received: from mail27.messagelabs.com ([193.109.254.147]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1THzoE-000342-5K; Sat, 29 Sep 2012 16:22:30 +0000 X-Env-Sender: cdelorme@gmail.com X-Msg-Ref: server-15.tower-27.messagelabs.com!1348935742!5866305!1 X-Originating-IP: [209.85.214.173] X-SpamReason: No, hits=0.4 required=7.0 tests=HTML_30_40,HTML_MESSAGE, ML_RADAR_SPEW_LINKS_14,RCVD_BY_IP,spamassassin: X-StarScan-Received: X-StarScan-Version: 6.6.1.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 20374 invoked from network); 29 Sep 2012 16:22:23 -0000 Received: from mail-ob0-f173.google.com (HELO mail-ob0-f173.google.com) (209.85.214.173) by server-15.tower-27.messagelabs.com with RC4-SHA encrypted SMTP; 29 Sep 2012 16:22:23 -0000 Received: by obbwc18 with SMTP id wc18so2390814obb.32 for ; Sat, 29 Sep 2012 09:22:21 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=cuthgEU24jdUcadhi8XBWi8lXF439BTxjfsq7aabTtg=; b=b6u+ed3N81uS408n88iXUYQAKQSiaqE4p9jAt6LaTnQVy0IqKfd5hKxcujG46n4w/R QkH2A2HSt08FdaQD1dtw8ZP2nzFFLi1TE1QkmAHIpNM2dFry5xXotcllfqWRjjMWjiLA ITTVB/4ehJEBxUpQQ0CkNF9bvPtJFxfrtaXn0v9XYinSDg+0mAc+1lDxWX1auHSY++4D C0ASxGWoLM7J6Hp/d3IITNZGKXL78enbaGzNwMylI5KjUOn8CM+MqbWMm7cHKmcdXHd3 dQmMrO8lKpNS68e79jUJURznnrBdkNciiQPBc1KiVLe93bULFq9aZYfHqUqSrWl5zUoG XTcg== MIME-Version: 1.0 Received: by 10.60.170.229 with SMTP id ap5mr8193776oec.101.1348935741806; Sat, 29 Sep 2012 09:22:21 -0700 (PDT) Received: by 10.76.19.148 with HTTP; Sat, 29 Sep 2012 09:22:21 -0700 (PDT) In-Reply-To: <50671D3D.1010304@gmail.com> References: <5066F922.1090305@gmail.com> <50671D3D.1010304@gmail.com> Date: Sat, 29 Sep 2012 12:22:21 -0400 Message-ID: From: Casey DeLorme To: "Teo En Ming (Zhang Enming)" Cc: "xen-users@lists.xen.org" , "xen-devel@lists.xen.org" Subject: Re: [Xen-users] Unable to start Windows 8 HVM guest with Xen VGA Passthrough with Xen 4.2.1-pre X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============2112485417139751700==" Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org --===============2112485417139751700== Content-Type: multipart/alternative; boundary=bcaec54b4ac0b7182a04cad993db --bcaec54b4ac0b7182a04cad993db Content-Type: text/plain; charset=ISO-8859-1 Hello Teo, That output is identical to the errors I had a few days ago, which was related to available RAM. Ian helped me debug it, said xl was having a ballooning problem and couldn't free up enough RAM in time to start my HVM. His suggested solution was to assign a fixed amount of RAM to Dom0 and turn off ballooning. Prior to this I had been letting Dom0 take all the RAM, but this problem was fixed by adding dom0_mem to grub.cfg and setting a fixed value. Have you tried re-running the xl create command after the first error? There are commands to move RAM around at run-time as well that you could try. ~Casey On Sat, Sep 29, 2012 at 12:09 PM, Teo En Ming (Zhang Enming) < singapore.mr.teo.en.ming@gmail.com> wrote: > On 29/09/2012 21:35, Teo En Ming (Zhang Enming) wrote: > >> Hi, >> >> I have applied Xen VGA passthrough patches from David Techer's >> personal website to Xen 4.2.1-pre source tree. Everything compiled and >> installed smoothly. But when I tried to start Windows 8 HVM domU with >> VGA passthrough, it gave me the following error: >> >> xc: error: unable to allocate memory to the HVM guest. (16: device or >> resource busy): Internal error. >> >> There are no issues with Xen 4.2-unstable changeset 25099 however. >> >> > Attached are screenshots of the errors for Xen 4.2.1-pre and Xen > configuration files. > > The following are links to screenshots of the errors for Xen 4.2.1-pre. > > http://i45.tinypic.com/**2j3s7pj.jpg > > http://i45.tinypic.com/95myc3.**jpg > > > -- > Yours sincerely, > > Mr. Teo En Ming (Zhang Enming) > Singapore > > > > _______________________________________________ > Xen-users mailing list > Xen-users@lists.xen.org > http://lists.xen.org/xen-users > --bcaec54b4ac0b7182a04cad993db Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable
Hello Teo,

That output is identical to t= he errors I had a few days ago, which was related to available RAM.

Ian helped me debug it, said xl was having a ballooning p= roblem and couldn't free up enough RAM in time to start my HVM.

His suggested solution was to assign a fixed amount of = RAM to Dom0 and turn off ballooning.

Prior to this= I had been letting Dom0 take all the RAM, but this problem was fixed by ad= ding dom0_mem to grub.cfg and setting a fixed value.

Have you tried re-running the xl create command after t= he first error? There are commands to move RAM around at run-time as well t= hat you could try.

~Casey

On Sat, Sep 29, 2012 at 12:09 PM, Teo En Ming (Z= hang Enming) <singapore.mr.teo.en.ming@gmail.com><= /span> wrote:
On 29/09/2012 21:35, Teo E= n Ming (Zhang Enming) wrote:
Hi,

I have applied Xen VGA passthrough patches from David Techer's
personal website to Xen 4.2.1-pre source tree. Everything compiled and
installed smoothly. But when I tried to start Windows 8 HVM domU with
VGA passthrough, it gave me the following error:

xc: error: unable to allocate memory to the HVM guest. (16: device or
resource busy): Internal error.

There are no issues with Xen 4.2-unstable changeset 25099 however.


Attached are screenshots of the errors for Xen 4.2.1-pre and Xen configurat= ion files.

The following are links to screenshots of the errors for Xen 4.2.1-pre.

http://i45= .tinypic.com/2j3s7pj.jpg

http://i45.= tinypic.com/95myc3.jpg

--
Yours sincerely,

Mr. Teo En Ming (Zhang Enming)
Singapore



_______________________________________________
Xen-users mailing list
Xen-users@lists.xen.org
http://lists.x= en.org/xen-users

--bcaec54b4ac0b7182a04cad993db-- --===============2112485417139751700== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users --===============2112485417139751700==-- From xen-users-bounces@lists.xen.org Sat Sep 29 16:50:26 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Sat, 29 Sep 2012 16:50:26 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TI0EM-0003e9-H6; Sat, 29 Sep 2012 16:49:30 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1TI0EK-0003dt-Ma for xen-users@lists.xen.org; Sat, 29 Sep 2012 16:49:28 +0000 Received: from [85.158.143.99:55155] by server-3.bemta-4.messagelabs.com id 5E/AC-10986-79627605; Sat, 29 Sep 2012 16:49:27 +0000 X-Env-Sender: singapore.mr.teo.en.ming@gmail.com X-Msg-Ref: server-11.tower-216.messagelabs.com!1348937364!24726773!1 X-Originating-IP: [209.85.210.45] X-SpamReason: No, hits=0.4 required=7.0 tests=HTML_50_60,HTML_MESSAGE, ML_RADAR_SPEW_LINKS_14,RCVD_BY_IP,spamassassin: X-StarScan-Received: X-StarScan-Version: 6.6.1.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 32060 invoked from network); 29 Sep 2012 16:49:26 -0000 Received: from mail-da0-f45.google.com (HELO mail-da0-f45.google.com) (209.85.210.45) by server-11.tower-216.messagelabs.com with RC4-SHA encrypted SMTP; 29 Sep 2012 16:49:26 -0000 Received: by dadn15 with SMTP id n15so1003766dad.32 for ; Sat, 29 Sep 2012 09:49:23 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:user-agent:mime-version:to:cc:subject :references:in-reply-to:content-type; bh=Jd8L5JGVJjdhIVTOYcyZYwrbqKwpvpe+GLYdH9SIfs8=; b=QToabueoqyq0y3r10Y+OOrasOAN0mEv8jWb5ucGz2f7AzMbKdTqBbjkhILZ4wSNE07 uQPp966QRYU0I4nRWLCL/Sbuqzaye0o7Au1qQRqGIIoqGwkQpLLR+nxgNqzduW1bdbWL Qh9UxDXawJQBxTohgwWggNhADBZngSlu8n/b+A190bBrG0rckeKrc0LbkfL6VPNYr/aH M7obehNmWu3ZTN7ds3pievnCtowevhcgs7RvY98z05OqrTxgfubvWngMUviibHbtibFr 2P/c0LQ33EAx1gYUCHaiCXcpD9s3d0WCa//LxILBgoK9gK3u2ggNRep+A4czAtrtTMfK Jybg== Received: by 10.68.237.232 with SMTP id vf8mr28822881pbc.65.1348937363750; Sat, 29 Sep 2012 09:49:23 -0700 (PDT) Received: from [192.168.1.2] (cm152.gamma205.maxonline.com.sg. [202.156.205.152]) by mx.google.com with ESMTPS id j9sm7404814pav.15.2012.09.29.09.49.21 (version=SSLv3 cipher=OTHER); Sat, 29 Sep 2012 09:49:23 -0700 (PDT) Message-ID: <50672690.9070504@gmail.com> Date: Sun, 30 Sep 2012 00:49:20 +0800 From: "Teo En Ming (Zhang Enming)" User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:15.0) Gecko/20120912 Thunderbird/15.0.1 MIME-Version: 1.0 To: Casey DeLorme References: <5066F922.1090305@gmail.com> <50671D3D.1010304@gmail.com> In-Reply-To: Cc: "xen-users@lists.xen.org" , "Teo En Ming \(Zhang Enming\)" , "xen-devel@lists.xen.org" Subject: Re: [Xen-users] Unable to start Windows 8 HVM guest with Xen VGA Passthrough with Xen 4.2.1-pre X-BeenThere: xen-users@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen user discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============8573220218278058768==" Sender: xen-users-bounces@lists.xen.org Errors-To: xen-users-bounces@lists.xen.org This is a multi-part message in MIME format. --===============8573220218278058768== Content-Type: multipart/alternative; boundary="------------070007050000080102040302" This is a multi-part message in MIME format. --------------070007050000080102040302 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Dear Casey, I had dom0_mem set to 1024 and 4096 as well, but it did not help. I am still getting the errors. I have 6 GB of memory installed. How much memory should I assign to dom0_mem? Thank you for your prompt reply. -- Yours sincerely, Mr. Teo En Ming (Zhang Enming) Singapore On 30/09/2012 00:22, Casey DeLorme wrote: > Hello Teo, > > That output is identical to the errors I had a few days ago, which was > related to available RAM. > > Ian helped me debug it, said xl was having a ballooning problem and > couldn't free up enough RAM in time to start my HVM. > > His suggested solution was to assign a fixed amount of RAM to Dom0 and > turn off ballooning. > > Prior to this I had been letting Dom0 take all the RAM, but this > problem was fixed by adding dom0_mem to grub.cfg and setting a fixed > value. > > Have you tried re-running the xl create command after the first error? > There are commands to move RAM around at run-time as well that you > could try. > > ~Casey > > On Sat, Sep 29, 2012 at 12:09 PM, Teo En Ming (Zhang Enming) > > wrote: > > On 29/09/2012 21:35, Teo En Ming (Zhang Enming) wrote: > > Hi, > > I have applied Xen VGA passthrough patches from David Techer's > personal website to Xen 4.2.1-pre source tree. Everything > compiled and > installed smoothly. But when I tried to start Windows 8 HVM > domU with > VGA passthrough, it gave me the following error: > > xc: error: unable to allocate memory to the HVM guest. (16: > device or > resource busy): Internal error. > > There are no issues with Xen 4.2-unstable changeset 25099 however. > > > Attached are screenshots of the errors for Xen 4.2.1-pre and Xen > configuration files. > > The following are links to screenshots of the errors for Xen > 4.2.1-pre. > > http://i45.tinypic.com/2j3s7pj.jpg > > http://i45.tinypic.com/95myc3.jpg > > > -- > Yours sincerely, > > Mr. Teo En Ming (Zhang Enming) > Singapore > > > > _______________________________________________ > Xen-users mailing list > Xen-users@lists.xen.org > http://lists.xen.org/xen-users > > --------------070007050000080102040302 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit
Dear Casey,

I had dom0_mem set to 1024 and 4096 as well, but it did not help. I am still getting the errors.

I have 6 GB of memory installed. How much memory should I assign to dom0_mem?

Thank you for your prompt reply.

-- 
Yours sincerely,

Mr. Teo En Ming (Zhang Enming)
Singapore

On 30/09/2012 00:22, Casey DeLorme wrote:
Hello Teo,

That output is identical to the errors I had a few days ago, which was related to available RAM.

Ian helped me debug it, said xl was having a ballooning problem and couldn't free up enough RAM in time to start my HVM.

His suggested solution was to assign a fixed amount of RAM to Dom0 and turn off ballooning.

Prior to this I had been letting Dom0 take all the RAM, but this problem was fixed by adding dom0_mem to grub.cfg and setting a fixed value.

Have you tried re-running the xl create command after the first error? There are commands to move RAM around at run-time as well that you could try.

~Casey

On Sat, Sep 29, 2012 at 12:09 PM, Teo En Ming (Zhang Enming) <singapore.mr.teo.en.ming@gmail.com> wrote:
On 29/09/2012 21:35, Teo En Ming (Zhang Enming) wrote:
Hi,

I have applied Xen VGA passthrough patches from David Techer's
personal website to Xen 4.2.1-pre source tree. Everything compiled and
installed smoothly. But when I tried to start Windows 8 HVM domU with
VGA passthrough, it gave me the following error:

xc: error: unable to allocate memory to the HVM guest. (16: device or
resource busy): Internal error.

There are no issues with Xen 4.2-unstable changeset 25099 however.


Attached are screenshots of the errors for Xen 4.2.1-pre and Xen configuration files.

The following are links to screenshots of the errors for Xen 4.2.1-pre.

http://i45.tinypic.com/2j3s7pj.jpg

http://i45.tinypic.com/95myc3.jpg


--
Yours sincerely,

Mr. Teo En Ming (Zhang Enming)
Singapore



_______________________________________________
Xen-users mailing list
Xen-users@lists.xen.org
http://lists.xen.org/xen-users




  


--------------070007050000080102040302--


--===============8573220218278058768==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
Xen-users mailing list
Xen-users@lists.xen.org
http://lists.xen.org/xen-users
--===============8573220218278058768==--


From xen-users-bounces@lists.xen.org Sat Sep 29 16:50:26 2012
Return-path: 
Envelope-to: archives@lists.xen.org
Delivery-date: Sat, 29 Sep 2012 16:50:26 +0000
Received: from localhost ([127.0.0.1] helo=lists.xen.org)
	by lists.xen.org with esmtp (Exim 4.72)
	(envelope-from )
	id 1TI0EM-0003e9-H6; Sat, 29 Sep 2012 16:49:30 +0000
Received: from mail6.bemta4.messagelabs.com ([85.158.143.247])
	by lists.xen.org with esmtp (Exim 4.72)
	(envelope-from )
	id 1TI0EK-0003dt-Ma
	for xen-users@lists.xen.org; Sat, 29 Sep 2012 16:49:28 +0000
Received: from [85.158.143.99:55155] by server-3.bemta-4.messagelabs.com id
	5E/AC-10986-79627605; Sat, 29 Sep 2012 16:49:27 +0000
X-Env-Sender: singapore.mr.teo.en.ming@gmail.com
X-Msg-Ref: server-11.tower-216.messagelabs.com!1348937364!24726773!1
X-Originating-IP: [209.85.210.45]
X-SpamReason: No, hits=0.4 required=7.0 tests=HTML_50_60,HTML_MESSAGE,
	ML_RADAR_SPEW_LINKS_14,RCVD_BY_IP,spamassassin: 
X-StarScan-Received: 
X-StarScan-Version: 6.6.1.3; banners=-,-,-
X-VirusChecked: Checked
Received: (qmail 32060 invoked from network); 29 Sep 2012 16:49:26 -0000
Received: from mail-da0-f45.google.com (HELO mail-da0-f45.google.com)
	(209.85.210.45)
	by server-11.tower-216.messagelabs.com with RC4-SHA encrypted SMTP;
	29 Sep 2012 16:49:26 -0000
Received: by dadn15 with SMTP id n15so1003766dad.32
	for ; Sat, 29 Sep 2012 09:49:23 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;
	h=message-id:date:from:user-agent:mime-version:to:cc:subject
	:references:in-reply-to:content-type;
	bh=Jd8L5JGVJjdhIVTOYcyZYwrbqKwpvpe+GLYdH9SIfs8=;
	b=QToabueoqyq0y3r10Y+OOrasOAN0mEv8jWb5ucGz2f7AzMbKdTqBbjkhILZ4wSNE07
	uQPp966QRYU0I4nRWLCL/Sbuqzaye0o7Au1qQRqGIIoqGwkQpLLR+nxgNqzduW1bdbWL
	Qh9UxDXawJQBxTohgwWggNhADBZngSlu8n/b+A190bBrG0rckeKrc0LbkfL6VPNYr/aH
	M7obehNmWu3ZTN7ds3pievnCtowevhcgs7RvY98z05OqrTxgfubvWngMUviibHbtibFr
	2P/c0LQ33EAx1gYUCHaiCXcpD9s3d0WCa//LxILBgoK9gK3u2ggNRep+A4czAtrtTMfK
	Jybg==
Received: by 10.68.237.232 with SMTP id vf8mr28822881pbc.65.1348937363750;
	Sat, 29 Sep 2012 09:49:23 -0700 (PDT)
Received: from [192.168.1.2] (cm152.gamma205.maxonline.com.sg.
	[202.156.205.152])
	by mx.google.com with ESMTPS id j9sm7404814pav.15.2012.09.29.09.49.21
	(version=SSLv3 cipher=OTHER); Sat, 29 Sep 2012 09:49:23 -0700 (PDT)
Message-ID: <50672690.9070504@gmail.com>
Date: Sun, 30 Sep 2012 00:49:20 +0800
From: "Teo En Ming (Zhang Enming)" 
User-Agent: Mozilla/5.0 (X11; Linux x86_64;
	rv:15.0) Gecko/20120912 Thunderbird/15.0.1
MIME-Version: 1.0
To: Casey DeLorme 
References: <5066F922.1090305@gmail.com> <50671D3D.1010304@gmail.com>
	
In-Reply-To: 
Cc: "xen-users@lists.xen.org" ,
	"Teo En Ming \(Zhang Enming\)" ,
	"xen-devel@lists.xen.org" 
Subject: Re: [Xen-users] Unable to start Windows 8 HVM guest with Xen VGA
 Passthrough with Xen 4.2.1-pre
X-BeenThere: xen-users@lists.xen.org
X-Mailman-Version: 2.1.13
Precedence: list
List-Id: Xen user discussion 
List-Unsubscribe: ,
	
List-Post: 
List-Help: 
List-Subscribe: ,
	
Content-Type: multipart/mixed; boundary="===============8573220218278058768=="
Sender: xen-users-bounces@lists.xen.org
Errors-To: xen-users-bounces@lists.xen.org

This is a multi-part message in MIME format.
--===============8573220218278058768==
Content-Type: multipart/alternative;
 boundary="------------070007050000080102040302"

This is a multi-part message in MIME format.
--------------070007050000080102040302
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit

Dear Casey,

I had dom0_mem set to 1024 and 4096 as well, but it did not help. I am 
still getting the errors.

I have 6 GB of memory installed. How much memory should I assign to 
dom0_mem?

Thank you for your prompt reply.

-- 
Yours sincerely,

Mr. Teo En Ming (Zhang Enming)
Singapore


On 30/09/2012 00:22, Casey DeLorme wrote:
> Hello Teo,
>
> That output is identical to the errors I had a few days ago, which was 
> related to available RAM.
>
> Ian helped me debug it, said xl was having a ballooning problem and 
> couldn't free up enough RAM in time to start my HVM.
>
> His suggested solution was to assign a fixed amount of RAM to Dom0 and 
> turn off ballooning.
>
> Prior to this I had been letting Dom0 take all the RAM, but this 
> problem was fixed by adding dom0_mem to grub.cfg and setting a fixed 
> value.
>
> Have you tried re-running the xl create command after the first error? 
> There are commands to move RAM around at run-time as well that you 
> could try.
>
> ~Casey
>
> On Sat, Sep 29, 2012 at 12:09 PM, Teo En Ming (Zhang Enming) 
>  > wrote:
>
>     On 29/09/2012 21:35, Teo En Ming (Zhang Enming) wrote:
>
>         Hi,
>
>         I have applied Xen VGA passthrough patches from David Techer's
>         personal website to Xen 4.2.1-pre source tree. Everything
>         compiled and
>         installed smoothly. But when I tried to start Windows 8 HVM
>         domU with
>         VGA passthrough, it gave me the following error:
>
>         xc: error: unable to allocate memory to the HVM guest. (16:
>         device or
>         resource busy): Internal error.
>
>         There are no issues with Xen 4.2-unstable changeset 25099 however.
>
>
>     Attached are screenshots of the errors for Xen 4.2.1-pre and Xen
>     configuration files.
>
>     The following are links to screenshots of the errors for Xen
>     4.2.1-pre.
>
>     http://i45.tinypic.com/2j3s7pj.jpg
>
>     http://i45.tinypic.com/95myc3.jpg
>
>
>     -- 
>     Yours sincerely,
>
>     Mr. Teo En Ming (Zhang Enming)
>     Singapore
>
>
>
>     _______________________________________________
>     Xen-users mailing list
>     Xen-users@lists.xen.org 
>     http://lists.xen.org/xen-users
>
>



--------------070007050000080102040302
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit


  
    
  
  
    
Dear Casey,

      

      I had dom0_mem set to 1024 and 4096 as well, but it did not help.
      I am still getting the errors.

      

      I have 6 GB of memory installed. How much memory should I assign
      to dom0_mem?

      

      Thank you for your prompt reply.

      

      
-- 
Yours sincerely,

Mr. Teo En Ming (Zhang Enming)
Singapore

      

      On 30/09/2012 00:22, Casey DeLorme wrote:

    

    

      

        
Hello Teo,

        


        

        
That output is identical to the errors I had a few days
          ago, which was related to available RAM.

        


        

        
Ian helped me debug it, said xl was having a ballooning
          problem and couldn't free up enough RAM in time to start my
          HVM.

        


        

        
His suggested solution was to assign a fixed amount of RAM
          to Dom0 and turn off ballooning.

        


        

        
Prior to this I had been letting Dom0 take all the RAM, but
          this problem was fixed by adding dom0_mem to grub.cfg and
          setting a fixed value.

        


        

        
Have you tried re-running the xl create command after the
          first error? There are commands to move RAM around at run-time
          as well that you could try.

        


        

        
~Casey

      

      


        
On Sat, Sep 29, 2012 at 12:09 PM, Teo
          En Ming (Zhang Enming) <singapore.mr.teo.en.ming@gmail.com>
          wrote:

          

            
On 29/09/2012 21:35, Teo En Ming (Zhang
              Enming) wrote:

              

                Hi,

                

                I have applied Xen VGA passthrough patches from David
                Techer's

                personal website to Xen 4.2.1-pre source tree.
                Everything compiled and

                installed smoothly. But when I tried to start Windows 8
                HVM domU with

                VGA passthrough, it gave me the following error:

                

                xc: error: unable to allocate memory to the HVM guest.
                (16: device or

                resource busy): Internal error.

                

                There are no issues with Xen 4.2-unstable changeset
                25099 however.

                

              

              

            

            Attached are screenshots of the errors for Xen 4.2.1-pre and
            Xen configuration files.

            

            The following are links to screenshots of the errors for Xen
            4.2.1-pre.

            

            http://i45.tinypic.com/2j3s7pj.jpg

            

            http://i45.tinypic.com/95myc3.jpg
            

              


                

                -- 

                Yours sincerely,

                

                Mr. Teo En Ming (Zhang Enming)

                Singapore

                

                

              

            

            

            _______________________________________________

            Xen-users mailing list

            Xen-users@lists.xen.org

            http://lists.xen.org/xen-users

          

        

        

      

    

    

    

    

  


--------------070007050000080102040302--


--===============8573220218278058768==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
Xen-users mailing list
Xen-users@lists.xen.org
http://lists.xen.org/xen-users
--===============8573220218278058768==--


From xen-users-bounces@lists.xen.org Sat Sep 29 17:02:25 2012
Return-path: 
Envelope-to: archives@lists.xen.org
Delivery-date: Sat, 29 Sep 2012 17:02:25 +0000
Received: from localhost ([127.0.0.1] helo=lists.xen.org)
	by lists.xen.org with esmtp (Exim 4.72)
	(envelope-from )
	id 1TI0Q2-00046k-11; Sat, 29 Sep 2012 17:01:34 +0000
Received: from mail6.bemta5.messagelabs.com ([195.245.231.135])
	by lists.xen.org with esmtp (Exim 4.72)
	(envelope-from ) id 1TI0Q0-00046e-C8
	for xen-users@lists.xen.org; Sat, 29 Sep 2012 17:01:32 +0000
Received: from [85.158.139.83:43422] by server-9.bemta-5.messagelabs.com id
	10/D2-14846-B6927605; Sat, 29 Sep 2012 17:01:31 +0000
X-Env-Sender: david.escott@gmail.com
X-Msg-Ref: server-8.tower-182.messagelabs.com!1348938090!18591521!1
X-Originating-IP: [74.125.82.173]
X-SpamReason: No, hits=0.3 required=7.0 tests=RCVD_BY_IP
X-StarScan-Received: 
X-StarScan-Version: 6.6.1.3; banners=-,-,-
X-VirusChecked: Checked
Received: (qmail 26890 invoked from network); 29 Sep 2012 17:01:30 -0000
Received: from mail-we0-f173.google.com (HELO mail-we0-f173.google.com)
	(74.125.82.173)
	by server-8.tower-182.messagelabs.com with RC4-SHA encrypted SMTP;
	29 Sep 2012 17:01:30 -0000
Received: by weyt11 with SMTP id t11so2450854wey.32
	for ; Sat, 29 Sep 2012 10:01:30 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;
	h=mime-version:sender:in-reply-to:references:from:date
	:x-google-sender-auth:message-id:subject:to:cc:content-type;
	bh=6NxbNtzsi0nBnClRk2CEqMSkxdx53GiGqZ+i33BU9U4=;
	b=HWeEFs71PGfPkl2u/YutItqYGOyWXrP6qS32xZwOF/6lRZ608cYdPdnUxTy1DDLQ30
	IZvob4I3IlzIa+yUs8nIUt7OFGD5OXqRkX1ymSY0FvESrkd77hEKbubt8ia2qfoQYOk3
	fBD0mr/nagq6eIrtpvjNPe4biUDa/Uuzzf2isul7utFnUqwgb6H4wak3L2op8oZZymhQ
	ZImTa+4q2BUnfGsH3KflyCmDmDNB/dEA6ZrlSWA8QBOdur6S6+mMhq/N6cgVlvRd5luD
	Chhgz9EesEwAkDbx62fLMaUi7ZQ4nygs3xU78yTfNb2jPeqbzeS9TpO46XK0n5VI7Yjf
	bKiQ==
Received: by 10.180.87.74 with SMTP id v10mr4430747wiz.21.1348938090505; Sat,
	29 Sep 2012 10:01:30 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.216.211.207 with HTTP; Sat, 29 Sep 2012 10:01:10 -0700 (PDT)
In-Reply-To: 
References: 
	
From: David Escott 
Date: Sat, 29 Sep 2012 13:01:10 -0400
X-Google-Sender-Auth: JoeoraYCE8meLTIZ1hdZ2a2nxts
Message-ID: 
To: Casey DeLorme 
Cc: xen-users@lists.xen.org
Subject: Re: [Xen-users] PCI Passthrough
X-BeenThere: xen-users@lists.xen.org
X-Mailman-Version: 2.1.13
Precedence: list
List-Id: Xen user discussion 
List-Unsubscribe: ,
	
List-Post: 
List-Help: 
List-Subscribe: ,
	
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: xen-users-bounces@lists.xen.org
Errors-To: xen-users-bounces@lists.xen.org

Went back to what was working last night and now have the 7850 working
but only when I pass both graphics adapters through to the domU.

Hardware is

MSI Z77A-G45
HD2600XT in PCI-Ex16 slot 1 (pci:0000:01:00:[0-1])
HD7850     in PCI-Ex16 slot 2 (pci:0000:02:00:[0-1])

Dom0 is Fedora 17 with kernel 3.5.4-1 and the fedora version of xen.
vga_passthrough=0 is set
stdvga=1 is set
I stub out and pass both graphics adapters to domU, and then disable
the 2600XT at which point the 7850 works, and the fake VGA Graphics
adapter reports a code 43.

If I don't pass both cards to domU then both they will report code 43.

Not sure why this is, or what is going on. Looked around in the bios
for anything related to crossfire but couldn't find anything.

----------------------------------------------------------------------------------------------------

This puts a dent in my current plan which was to use the system to
support three different computers in three different rooms. Not sure
if anyone has seen anything like this/knows what might be going on.




On Sat, Sep 29, 2012 at 11:20 AM, Casey DeLorme  wrote:
> Hello David,
>
> I have created a guide using Debian that can successfully reproduce VGA
> Passthrough with AMD Radeon cards, in particular I have used an AMD Radeon
> 6870.
>
> If you are more familiar with Fedora, I'm sure you can translate any Debain
> specific actions to Fedora equivalents.
> http://wiki.xen.org/wiki/Comprehensive_Xen_Debian_Wheezy_PCI_Passthrough_Tutorial
>
> I also posted a video walk-through:
> http://www.youtube.com/playlist?list=PLC70DC33D993CEB44&feature=view_all
>
> As for your current configuration, what version of Xen (4.0, 4.1.2, 4.2?),
> can you share your HVM Configuration, and are you getting any errors in your
> Xen log files or just inside of Windows?
>
>
> On Sat, Sep 29, 2012 at 11:10 AM, David Escott
>  wrote:
>>
>> I've been playing around with doing PCI passthrough of Radeon cards
>> and have had some success.
>>
>> Under Fedora 17 (stock everything) I was able to passthrough an older
>> RADEON 2600XT to a Windows7 domU.
>> However when I try the same with a new RADEON 7850 I get a "not enough
>> resources" error from the Windows guest.
>>
>> I'm not sure what the next steps are, it seems from blog postings and
>> howtos that people are just trying things at random, and I don't
>> understand what the debugging process is.
>>
>> Any advice on what the next steps are? Should I move to an OS that
>> will have a newer XEN or is there some configuration file I should be
>> editing?
>>
>> Thanks,
>> David
>>
>> _______________________________________________
>> Xen-users mailing list
>> Xen-users@lists.xen.org
>> http://lists.xen.org/xen-users
>
>



-- 
David Wright Escott
A comathematician turns cotheorems into phi.

_______________________________________________
Xen-users mailing list
Xen-users@lists.xen.org
http://lists.xen.org/xen-users

From xen-users-bounces@lists.xen.org Sat Sep 29 17:02:25 2012
Return-path: 
Envelope-to: archives@lists.xen.org
Delivery-date: Sat, 29 Sep 2012 17:02:25 +0000
Received: from localhost ([127.0.0.1] helo=lists.xen.org)
	by lists.xen.org with esmtp (Exim 4.72)
	(envelope-from )
	id 1TI0Q2-00046k-11; Sat, 29 Sep 2012 17:01:34 +0000
Received: from mail6.bemta5.messagelabs.com ([195.245.231.135])
	by lists.xen.org with esmtp (Exim 4.72)
	(envelope-from ) id 1TI0Q0-00046e-C8
	for xen-users@lists.xen.org; Sat, 29 Sep 2012 17:01:32 +0000
Received: from [85.158.139.83:43422] by server-9.bemta-5.messagelabs.com id
	10/D2-14846-B6927605; Sat, 29 Sep 2012 17:01:31 +0000
X-Env-Sender: david.escott@gmail.com
X-Msg-Ref: server-8.tower-182.messagelabs.com!1348938090!18591521!1
X-Originating-IP: [74.125.82.173]
X-SpamReason: No, hits=0.3 required=7.0 tests=RCVD_BY_IP
X-StarScan-Received: 
X-StarScan-Version: 6.6.1.3; banners=-,-,-
X-VirusChecked: Checked
Received: (qmail 26890 invoked from network); 29 Sep 2012 17:01:30 -0000
Received: from mail-we0-f173.google.com (HELO mail-we0-f173.google.com)
	(74.125.82.173)
	by server-8.tower-182.messagelabs.com with RC4-SHA encrypted SMTP;
	29 Sep 2012 17:01:30 -0000
Received: by weyt11 with SMTP id t11so2450854wey.32
	for ; Sat, 29 Sep 2012 10:01:30 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;
	h=mime-version:sender:in-reply-to:references:from:date
	:x-google-sender-auth:message-id:subject:to:cc:content-type;
	bh=6NxbNtzsi0nBnClRk2CEqMSkxdx53GiGqZ+i33BU9U4=;
	b=HWeEFs71PGfPkl2u/YutItqYGOyWXrP6qS32xZwOF/6lRZ608cYdPdnUxTy1DDLQ30
	IZvob4I3IlzIa+yUs8nIUt7OFGD5OXqRkX1ymSY0FvESrkd77hEKbubt8ia2qfoQYOk3
	fBD0mr/nagq6eIrtpvjNPe4biUDa/Uuzzf2isul7utFnUqwgb6H4wak3L2op8oZZymhQ
	ZImTa+4q2BUnfGsH3KflyCmDmDNB/dEA6ZrlSWA8QBOdur6S6+mMhq/N6cgVlvRd5luD
	Chhgz9EesEwAkDbx62fLMaUi7ZQ4nygs3xU78yTfNb2jPeqbzeS9TpO46XK0n5VI7Yjf
	bKiQ==
Received: by 10.180.87.74 with SMTP id v10mr4430747wiz.21.1348938090505; Sat,
	29 Sep 2012 10:01:30 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.216.211.207 with HTTP; Sat, 29 Sep 2012 10:01:10 -0700 (PDT)
In-Reply-To: 
References: 
	
From: David Escott 
Date: Sat, 29 Sep 2012 13:01:10 -0400
X-Google-Sender-Auth: JoeoraYCE8meLTIZ1hdZ2a2nxts
Message-ID: 
To: Casey DeLorme 
Cc: xen-users@lists.xen.org
Subject: Re: [Xen-users] PCI Passthrough
X-BeenThere: xen-users@lists.xen.org
X-Mailman-Version: 2.1.13
Precedence: list
List-Id: Xen user discussion 
List-Unsubscribe: ,
	
List-Post: 
List-Help: 
List-Subscribe: ,
	
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: xen-users-bounces@lists.xen.org
Errors-To: xen-users-bounces@lists.xen.org

Went back to what was working last night and now have the 7850 working
but only when I pass both graphics adapters through to the domU.

Hardware is

MSI Z77A-G45
HD2600XT in PCI-Ex16 slot 1 (pci:0000:01:00:[0-1])
HD7850     in PCI-Ex16 slot 2 (pci:0000:02:00:[0-1])

Dom0 is Fedora 17 with kernel 3.5.4-1 and the fedora version of xen.
vga_passthrough=0 is set
stdvga=1 is set
I stub out and pass both graphics adapters to domU, and then disable
the 2600XT at which point the 7850 works, and the fake VGA Graphics
adapter reports a code 43.

If I don't pass both cards to domU then both they will report code 43.

Not sure why this is, or what is going on. Looked around in the bios
for anything related to crossfire but couldn't find anything.

----------------------------------------------------------------------------------------------------

This puts a dent in my current plan which was to use the system to
support three different computers in three different rooms. Not sure
if anyone has seen anything like this/knows what might be going on.




On Sat, Sep 29, 2012 at 11:20 AM, Casey DeLorme  wrote:
> Hello David,
>
> I have created a guide using Debian that can successfully reproduce VGA
> Passthrough with AMD Radeon cards, in particular I have used an AMD Radeon
> 6870.
>
> If you are more familiar with Fedora, I'm sure you can translate any Debain
> specific actions to Fedora equivalents.
> http://wiki.xen.org/wiki/Comprehensive_Xen_Debian_Wheezy_PCI_Passthrough_Tutorial
>
> I also posted a video walk-through:
> http://www.youtube.com/playlist?list=PLC70DC33D993CEB44&feature=view_all
>
> As for your current configuration, what version of Xen (4.0, 4.1.2, 4.2?),
> can you share your HVM Configuration, and are you getting any errors in your
> Xen log files or just inside of Windows?
>
>
> On Sat, Sep 29, 2012 at 11:10 AM, David Escott
>  wrote:
>>
>> I've been playing around with doing PCI passthrough of Radeon cards
>> and have had some success.
>>
>> Under Fedora 17 (stock everything) I was able to passthrough an older
>> RADEON 2600XT to a Windows7 domU.
>> However when I try the same with a new RADEON 7850 I get a "not enough
>> resources" error from the Windows guest.
>>
>> I'm not sure what the next steps are, it seems from blog postings and
>> howtos that people are just trying things at random, and I don't
>> understand what the debugging process is.
>>
>> Any advice on what the next steps are? Should I move to an OS that
>> will have a newer XEN or is there some configuration file I should be
>> editing?
>>
>> Thanks,
>> David
>>
>> _______________________________________________
>> Xen-users mailing list
>> Xen-users@lists.xen.org
>> http://lists.xen.org/xen-users
>
>



-- 
David Wright Escott
A comathematician turns cotheorems into phi.

_______________________________________________
Xen-users mailing list
Xen-users@lists.xen.org
http://lists.xen.org/xen-users

From xen-users-bounces@lists.xen.org Sat Sep 29 17:14:33 2012
Return-path: 
Envelope-to: archives@lists.xen.org
Delivery-date: Sat, 29 Sep 2012 17:14:33 +0000
Received: from localhost ([127.0.0.1] helo=lists.xen.org)
	by lists.xen.org with esmtp (Exim 4.72)
	(envelope-from )
	id 1TI0bl-0004Su-Gj; Sat, 29 Sep 2012 17:13:41 +0000
Received: from mail6.bemta3.messagelabs.com ([195.245.230.39])
	by lists.xen.org with esmtp (Exim 4.72)
	(envelope-from ) id 1TI0bk-0004Sm-2C
	for xen-users@lists.xen.org; Sat, 29 Sep 2012 17:13:40 +0000
Received: from [85.158.137.99:48330] by server-4.bemta-3.messagelabs.com id
	86/E6-14155-34C27605; Sat, 29 Sep 2012 17:13:39 +0000
X-Env-Sender: cdelorme@gmail.com
X-Msg-Ref: server-13.tower-217.messagelabs.com!1348938816!19645702!1
X-Originating-IP: [209.85.214.173]
X-SpamReason: No, hits=1.2 required=7.0 tests=HTML_20_30,HTML_MESSAGE,
	ML_RADAR_SPEW_LINKS_14,RCVD_BY_IP,spamassassin: 
X-StarScan-Received: 
X-StarScan-Version: 6.6.1.3; banners=-,-,-
X-VirusChecked: Checked
Received: (qmail 18610 invoked from network); 29 Sep 2012 17:13:37 -0000
Received: from mail-ob0-f173.google.com (HELO mail-ob0-f173.google.com)
	(209.85.214.173)
	by server-13.tower-217.messagelabs.com with RC4-SHA encrypted SMTP;
	29 Sep 2012 17:13:37 -0000
Received: by obbwc18 with SMTP id wc18so2420073obb.32
	for ; Sat, 29 Sep 2012 10:13:36 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;
	h=mime-version:in-reply-to:references:date:message-id:subject:from:to
	:cc:content-type;
	bh=x3y0i4UgX4JHG5QXZrqbpGjHpe+/Lv049MFudqeGR6U=;
	b=fipJT3jttHuG5YNPBMP9MtUV+xpC5Mtjo7X+AcVeZZ+yWZjka4ixhTpN8Yb91Cra0f
	DSTRVUwXBoufwFD0Y3gUi60kE/cQUHca8NCs4yndajf/1IccVvdd23wHZXZGBTn1624A
	Vt50SlnwpMNWhPQOUmQ4qadbUAmiXjnjfcYca1bE7JPD0HI4p95pAEgaxf2oAbs+Vtnp
	DfORvT3NKFOoOENV/D43OKrH5a1nURc0KGi/wbeQNZzjECU8iILWD+BFRLF2z0q0Un1I
	z0CddTn3cPxUAUHKlPYbCAINdbDPcKeElaQwK2jr8V/5uP0SAGYg3nYRyK0CSiq8b5Ca
	VAig==
MIME-Version: 1.0
Received: by 10.60.170.229 with SMTP id ap5mr8262617oec.101.1348938816172;
	Sat, 29 Sep 2012 10:13:36 -0700 (PDT)
Received: by 10.76.19.148 with HTTP; Sat, 29 Sep 2012 10:13:36 -0700 (PDT)
In-Reply-To: 
References: 
	
	
Date: Sat, 29 Sep 2012 13:13:36 -0400
Message-ID: 
From: Casey DeLorme 
To: David Escott 
Cc: xen-users@lists.xen.org
Subject: Re: [Xen-users] PCI Passthrough
X-BeenThere: xen-users@lists.xen.org
X-Mailman-Version: 2.1.13
Precedence: list
List-Id: Xen user discussion 
List-Unsubscribe: ,
	
List-Post: 
List-Help: 
List-Subscribe: ,
	
Content-Type: multipart/mixed; boundary="===============6674933237536163688=="
Sender: xen-users-bounces@lists.xen.org
Errors-To: xen-users-bounces@lists.xen.org

--===============6674933237536163688==
Content-Type: multipart/alternative; boundary=bcaec54b4ac0f6322504cada4a7b

--bcaec54b4ac0f6322504cada4a7b
Content-Type: text/plain; charset=ISO-8859-1

The settings for stdvga is related to the emulated graphics only, I don't
believe it has anything to do with your passed devices.  Similarly, you can
(or should be able to) omit the vga_passthrough=0 line, as it defaults to 0.

Assuming you are passing to a Windows DomU (hence code 43), have you
checked your xen log files (/var/logs/xen), also I would try running xl
-vvv create with and without both adapters to see if that maybe yields a
clue.

Also, what version of Xen did you install, and which toolstack are you
using (xm/xl)?

On Sat, Sep 29, 2012 at 1:01 PM, David Escott  wrote:

> Went back to what was working last night and now have the 7850 working
> but only when I pass both graphics adapters through to the domU.
>
> Hardware is
>
> MSI Z77A-G45
> HD2600XT in PCI-Ex16 slot 1 (pci:0000:01:00:[0-1])
> HD7850     in PCI-Ex16 slot 2 (pci:0000:02:00:[0-1])
>
> Dom0 is Fedora 17 with kernel 3.5.4-1 and the fedora version of xen.
> vga_passthrough=0 is set
> stdvga=1 is set
> I stub out and pass both graphics adapters to domU, and then disable
> the 2600XT at which point the 7850 works, and the fake VGA Graphics
> adapter reports a code 43.
>
> If I don't pass both cards to domU then both they will report code 43.
>
> Not sure why this is, or what is going on. Looked around in the bios
> for anything related to crossfire but couldn't find anything.
>
>
> ----------------------------------------------------------------------------------------------------
>
> This puts a dent in my current plan which was to use the system to
> support three different computers in three different rooms. Not sure
> if anyone has seen anything like this/knows what might be going on.
>
>
>
>
> On Sat, Sep 29, 2012 at 11:20 AM, Casey DeLorme 
> wrote:
> > Hello David,
> >
> > I have created a guide using Debian that can successfully reproduce VGA
> > Passthrough with AMD Radeon cards, in particular I have used an AMD
> Radeon
> > 6870.
> >
> > If you are more familiar with Fedora, I'm sure you can translate any
> Debain
> > specific actions to Fedora equivalents.
> >
> http://wiki.xen.org/wiki/Comprehensive_Xen_Debian_Wheezy_PCI_Passthrough_Tutorial
> >
> > I also posted a video walk-through:
> > http://www.youtube.com/playlist?list=PLC70DC33D993CEB44&feature=view_all
> >
> > As for your current configuration, what version of Xen (4.0, 4.1.2,
> 4.2?),
> > can you share your HVM Configuration, and are you getting any errors in
> your
> > Xen log files or just inside of Windows?
> >
> >
> > On Sat, Sep 29, 2012 at 11:10 AM, David Escott
> >  wrote:
> >>
> >> I've been playing around with doing PCI passthrough of Radeon cards
> >> and have had some success.
> >>
> >> Under Fedora 17 (stock everything) I was able to passthrough an older
> >> RADEON 2600XT to a Windows7 domU.
> >> However when I try the same with a new RADEON 7850 I get a "not enough
> >> resources" error from the Windows guest.
> >>
> >> I'm not sure what the next steps are, it seems from blog postings and
> >> howtos that people are just trying things at random, and I don't
> >> understand what the debugging process is.
> >>
> >> Any advice on what the next steps are? Should I move to an OS that
> >> will have a newer XEN or is there some configuration file I should be
> >> editing?
> >>
> >> Thanks,
> >> David
> >>
> >> _______________________________________________
> >> Xen-users mailing list
> >> Xen-users@lists.xen.org
> >> http://lists.xen.org/xen-users
> >
> >
>
>
>
> --
> David Wright Escott
> A comathematician turns cotheorems into phi.
>

--bcaec54b4ac0f6322504cada4a7b
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

The settings for stdvga is related to the emulated graphics only, I don'=
;t believe it has anything to do with your passed devices. =A0Similarly, yo=
u can (or should be able to) omit the vga_passthrough=3D0 line, as it defau=
lts to 0.


Assuming you are passing to a Windows DomU (hence code 43), =
have you checked your xen log files (/var/logs/xen), also I would try runni=
ng xl -vvv create with and without both adapters to see if that maybe yield=
s a clue.



Also, what version of Xen did you install, and which to=
olstack are you using (xm/xl)?

On Sat, Sep 29, 2012 at 1:01 PM, David Escott <=
;david.e=
scott@post.harvard.edu> wrote:


Went back to what was working last night and=
 now have the 7850 working

but only when I pass both graphics adapters through to the domU.



Hardware is



MSI Z77A-G45

HD2600XT in PCI-Ex16 slot 1 (pci:0000:01:00:[0-1])

HD7850 =A0 =A0 in PCI-Ex16 slot 2 (pci:0000:02:00:[0-1])



Dom0 is Fedora 17 with kernel 3.5.4-1 and the fedora version of xen.

vga_passthrough=3D0 is set

stdvga=3D1 is set

I stub out and pass both graphics adapters to domU, and then disable

the 2600XT at which point the 7850 works, and the fake VGA Graphics

adapter reports a code 43.



If I don't pass both cards to domU then both they will report code 43.<=
br>


Not sure why this is, or what is going on. Looked around in the bios

for anything related to crossfire but couldn't find anything.



---------------------------------------------------------------------------=
-------------------------



This puts a dent in my current plan which was to use the system to

support three different computers in three different rooms. Not sure

if anyone has seen anything like this/knows what might be going on.










On Sat, Sep 29, 2012 at 11:20 AM, Casey DeLorme <cdelorme@gmail.com> wrote:

> Hello David,

>

> I have created a guide using Debian that can successfully reproduce VG=
A

> Passthrough with AMD Radeon cards, in particular I have used an AMD Ra=
deon

> 6870.

>

> If you are more familiar with Fedora, I'm sure you can translate a=
ny Debain

> specific actions to Fedora equivalents.

> http://wiki.xen.org/wiki/Comprehe=
nsive_Xen_Debian_Wheezy_PCI_Passthrough_Tutorial

>

> I also posted a video walk-through:

> http://www.youtube.com/playlist?li=
st=3DPLC70DC33D993CEB44&feature=3Dview_all

>

> As for your current configuration, what version of Xen (4.0, 4.1.2, 4.=
2?),

> can you share your HVM Configuration, and are you getting any errors i=
n your

> Xen log files or just inside of Windows?

>

>

> On Sat, Sep 29, 2012 at 11:10 AM, David Escott

> <david.escott@post=
.harvard.edu> wrote:

>>

>> I've been playing around with doing PCI passthrough of Radeon =
cards

>> and have had some success.

>>

>> Under Fedora 17 (stock everything) I was able to passthrough an ol=
der

>> RADEON 2600XT to a Windows7 domU.

>> However when I try the same with a new RADEON 7850 I get a "n=
ot enough

>> resources" error from the Windows guest.

>>

>> I'm not sure what the next steps are, it seems from blog posti=
ngs and

>> howtos that people are just trying things at random, and I don'=
;t

>> understand what the debugging process is.

>>

>> Any advice on what the next steps are? Should I move to an OS that=


>> will have a newer XEN or is there some configuration file I should=
 be

>> editing?

>>

>> Thanks,

>> David

>>

>> _______________________________________________

>> Xen-users mailing list

>> Xen-users@lists.xen.org=


>> http:=
//lists.xen.org/xen-users

>

>








--

David Wright Escott

A comathematician turns cotheorems into phi.





--bcaec54b4ac0f6322504cada4a7b--


--===============6674933237536163688==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
Xen-users mailing list
Xen-users@lists.xen.org
http://lists.xen.org/xen-users
--===============6674933237536163688==--


From xen-users-bounces@lists.xen.org Sat Sep 29 17:14:33 2012
Return-path: 
Envelope-to: archives@lists.xen.org
Delivery-date: Sat, 29 Sep 2012 17:14:33 +0000
Received: from localhost ([127.0.0.1] helo=lists.xen.org)
	by lists.xen.org with esmtp (Exim 4.72)
	(envelope-from )
	id 1TI0bl-0004Su-Gj; Sat, 29 Sep 2012 17:13:41 +0000
Received: from mail6.bemta3.messagelabs.com ([195.245.230.39])
	by lists.xen.org with esmtp (Exim 4.72)
	(envelope-from ) id 1TI0bk-0004Sm-2C
	for xen-users@lists.xen.org; Sat, 29 Sep 2012 17:13:40 +0000
Received: from [85.158.137.99:48330] by server-4.bemta-3.messagelabs.com id
	86/E6-14155-34C27605; Sat, 29 Sep 2012 17:13:39 +0000
X-Env-Sender: cdelorme@gmail.com
X-Msg-Ref: server-13.tower-217.messagelabs.com!1348938816!19645702!1
X-Originating-IP: [209.85.214.173]
X-SpamReason: No, hits=1.2 required=7.0 tests=HTML_20_30,HTML_MESSAGE,
	ML_RADAR_SPEW_LINKS_14,RCVD_BY_IP,spamassassin: 
X-StarScan-Received: 
X-StarScan-Version: 6.6.1.3; banners=-,-,-
X-VirusChecked: Checked
Received: (qmail 18610 invoked from network); 29 Sep 2012 17:13:37 -0000
Received: from mail-ob0-f173.google.com (HELO mail-ob0-f173.google.com)
	(209.85.214.173)
	by server-13.tower-217.messagelabs.com with RC4-SHA encrypted SMTP;
	29 Sep 2012 17:13:37 -0000
Received: by obbwc18 with SMTP id wc18so2420073obb.32
	for ; Sat, 29 Sep 2012 10:13:36 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;
	h=mime-version:in-reply-to:references:date:message-id:subject:from:to
	:cc:content-type;
	bh=x3y0i4UgX4JHG5QXZrqbpGjHpe+/Lv049MFudqeGR6U=;
	b=fipJT3jttHuG5YNPBMP9MtUV+xpC5Mtjo7X+AcVeZZ+yWZjka4ixhTpN8Yb91Cra0f
	DSTRVUwXBoufwFD0Y3gUi60kE/cQUHca8NCs4yndajf/1IccVvdd23wHZXZGBTn1624A
	Vt50SlnwpMNWhPQOUmQ4qadbUAmiXjnjfcYca1bE7JPD0HI4p95pAEgaxf2oAbs+Vtnp
	DfORvT3NKFOoOENV/D43OKrH5a1nURc0KGi/wbeQNZzjECU8iILWD+BFRLF2z0q0Un1I
	z0CddTn3cPxUAUHKlPYbCAINdbDPcKeElaQwK2jr8V/5uP0SAGYg3nYRyK0CSiq8b5Ca
	VAig==
MIME-Version: 1.0
Received: by 10.60.170.229 with SMTP id ap5mr8262617oec.101.1348938816172;
	Sat, 29 Sep 2012 10:13:36 -0700 (PDT)
Received: by 10.76.19.148 with HTTP; Sat, 29 Sep 2012 10:13:36 -0700 (PDT)
In-Reply-To: 
References: 
	
	
Date: Sat, 29 Sep 2012 13:13:36 -0400
Message-ID: 
From: Casey DeLorme 
To: David Escott 
Cc: xen-users@lists.xen.org
Subject: Re: [Xen-users] PCI Passthrough
X-BeenThere: xen-users@lists.xen.org
X-Mailman-Version: 2.1.13
Precedence: list
List-Id: Xen user discussion 
List-Unsubscribe: ,
	
List-Post: 
List-Help: 
List-Subscribe: ,
	
Content-Type: multipart/mixed; boundary="===============6674933237536163688=="
Sender: xen-users-bounces@lists.xen.org
Errors-To: xen-users-bounces@lists.xen.org

--===============6674933237536163688==
Content-Type: multipart/alternative; boundary=bcaec54b4ac0f6322504cada4a7b

--bcaec54b4ac0f6322504cada4a7b
Content-Type: text/plain; charset=ISO-8859-1

The settings for stdvga is related to the emulated graphics only, I don't
believe it has anything to do with your passed devices.  Similarly, you can
(or should be able to) omit the vga_passthrough=0 line, as it defaults to 0.

Assuming you are passing to a Windows DomU (hence code 43), have you
checked your xen log files (/var/logs/xen), also I would try running xl
-vvv create with and without both adapters to see if that maybe yields a
clue.

Also, what version of Xen did you install, and which toolstack are you
using (xm/xl)?

On Sat, Sep 29, 2012 at 1:01 PM, David Escott  wrote:

> Went back to what was working last night and now have the 7850 working
> but only when I pass both graphics adapters through to the domU.
>
> Hardware is
>
> MSI Z77A-G45
> HD2600XT in PCI-Ex16 slot 1 (pci:0000:01:00:[0-1])
> HD7850     in PCI-Ex16 slot 2 (pci:0000:02:00:[0-1])
>
> Dom0 is Fedora 17 with kernel 3.5.4-1 and the fedora version of xen.
> vga_passthrough=0 is set
> stdvga=1 is set
> I stub out and pass both graphics adapters to domU, and then disable
> the 2600XT at which point the 7850 works, and the fake VGA Graphics
> adapter reports a code 43.
>
> If I don't pass both cards to domU then both they will report code 43.
>
> Not sure why this is, or what is going on. Looked around in the bios
> for anything related to crossfire but couldn't find anything.
>
>
> ----------------------------------------------------------------------------------------------------
>
> This puts a dent in my current plan which was to use the system to
> support three different computers in three different rooms. Not sure
> if anyone has seen anything like this/knows what might be going on.
>
>
>
>
> On Sat, Sep 29, 2012 at 11:20 AM, Casey DeLorme 
> wrote:
> > Hello David,
> >
> > I have created a guide using Debian that can successfully reproduce VGA
> > Passthrough with AMD Radeon cards, in particular I have used an AMD
> Radeon
> > 6870.
> >
> > If you are more familiar with Fedora, I'm sure you can translate any
> Debain
> > specific actions to Fedora equivalents.
> >
> http://wiki.xen.org/wiki/Comprehensive_Xen_Debian_Wheezy_PCI_Passthrough_Tutorial
> >
> > I also posted a video walk-through:
> > http://www.youtube.com/playlist?list=PLC70DC33D993CEB44&feature=view_all
> >
> > As for your current configuration, what version of Xen (4.0, 4.1.2,
> 4.2?),
> > can you share your HVM Configuration, and are you getting any errors in
> your
> > Xen log files or just inside of Windows?
> >
> >
> > On Sat, Sep 29, 2012 at 11:10 AM, David Escott
> >  wrote:
> >>
> >> I've been playing around with doing PCI passthrough of Radeon cards
> >> and have had some success.
> >>
> >> Under Fedora 17 (stock everything) I was able to passthrough an older
> >> RADEON 2600XT to a Windows7 domU.
> >> However when I try the same with a new RADEON 7850 I get a "not enough
> >> resources" error from the Windows guest.
> >>
> >> I'm not sure what the next steps are, it seems from blog postings and
> >> howtos that people are just trying things at random, and I don't
> >> understand what the debugging process is.
> >>
> >> Any advice on what the next steps are? Should I move to an OS that
> >> will have a newer XEN or is there some configuration file I should be
> >> editing?
> >>
> >> Thanks,
> >> David
> >>
> >> _______________________________________________
> >> Xen-users mailing list
> >> Xen-users@lists.xen.org
> >> http://lists.xen.org/xen-users
> >
> >
>
>
>
> --
> David Wright Escott
> A comathematician turns cotheorems into phi.
>

--bcaec54b4ac0f6322504cada4a7b
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

The settings for stdvga is related to the emulated graphics only, I don'=
;t believe it has anything to do with your passed devices. =A0Similarly, yo=
u can (or should be able to) omit the vga_passthrough=3D0 line, as it defau=
lts to 0.


Assuming you are passing to a Windows DomU (hence code 43), =
have you checked your xen log files (/var/logs/xen), also I would try runni=
ng xl -vvv create with and without both adapters to see if that maybe yield=
s a clue.



Also, what version of Xen did you install, and which to=
olstack are you using (xm/xl)?

On Sat, Sep 29, 2012 at 1:01 PM, David Escott <=
;david.e=
scott@post.harvard.edu> wrote:


Went back to what was working last night and=
 now have the 7850 working

but only when I pass both graphics adapters through to the domU.



Hardware is



MSI Z77A-G45

HD2600XT in PCI-Ex16 slot 1 (pci:0000:01:00:[0-1])

HD7850 =A0 =A0 in PCI-Ex16 slot 2 (pci:0000:02:00:[0-1])



Dom0 is Fedora 17 with kernel 3.5.4-1 and the fedora version of xen.

vga_passthrough=3D0 is set

stdvga=3D1 is set

I stub out and pass both graphics adapters to domU, and then disable

the 2600XT at which point the 7850 works, and the fake VGA Graphics

adapter reports a code 43.



If I don't pass both cards to domU then both they will report code 43.<=
br>


Not sure why this is, or what is going on. Looked around in the bios

for anything related to crossfire but couldn't find anything.



---------------------------------------------------------------------------=
-------------------------



This puts a dent in my current plan which was to use the system to

support three different computers in three different rooms. Not sure

if anyone has seen anything like this/knows what might be going on.










On Sat, Sep 29, 2012 at 11:20 AM, Casey DeLorme <cdelorme@gmail.com> wrote:

> Hello David,

>

> I have created a guide using Debian that can successfully reproduce VG=
A

> Passthrough with AMD Radeon cards, in particular I have used an AMD Ra=
deon

> 6870.

>

> If you are more familiar with Fedora, I'm sure you can translate a=
ny Debain

> specific actions to Fedora equivalents.

> http://wiki.xen.org/wiki/Comprehe=
nsive_Xen_Debian_Wheezy_PCI_Passthrough_Tutorial

>

> I also posted a video walk-through:

> http://www.youtube.com/playlist?li=
st=3DPLC70DC33D993CEB44&feature=3Dview_all

>

> As for your current configuration, what version of Xen (4.0, 4.1.2, 4.=
2?),

> can you share your HVM Configuration, and are you getting any errors i=
n your

> Xen log files or just inside of Windows?

>

>

> On Sat, Sep 29, 2012 at 11:10 AM, David Escott

> <david.escott@post=
.harvard.edu> wrote:

>>

>> I've been playing around with doing PCI passthrough of Radeon =
cards

>> and have had some success.

>>

>> Under Fedora 17 (stock everything) I was able to passthrough an ol=
der

>> RADEON 2600XT to a Windows7 domU.

>> However when I try the same with a new RADEON 7850 I get a "n=
ot enough

>> resources" error from the Windows guest.

>>

>> I'm not sure what the next steps are, it seems from blog posti=
ngs and

>> howtos that people are just trying things at random, and I don'=
;t

>> understand what the debugging process is.

>>

>> Any advice on what the next steps are? Should I move to an OS that=


>> will have a newer XEN or is there some configuration file I should=
 be

>> editing?

>>

>> Thanks,

>> David

>>

>> _______________________________________________

>> Xen-users mailing list

>> Xen-users@lists.xen.org=


>> http:=
//lists.xen.org/xen-users

>

>








--

David Wright Escott

A comathematician turns cotheorems into phi.





--bcaec54b4ac0f6322504cada4a7b--


--===============6674933237536163688==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
Xen-users mailing list
Xen-users@lists.xen.org
http://lists.xen.org/xen-users
--===============6674933237536163688==--


From xen-users-bounces@lists.xen.org Sat Sep 29 17:26:06 2012
Return-path: 
Envelope-to: archives@lists.xen.org
Delivery-date: Sat, 29 Sep 2012 17:26:06 +0000
Received: from localhost ([127.0.0.1] helo=lists.xen.org)
	by lists.xen.org with esmtp (Exim 4.72)
	(envelope-from )
	id 1TI0n0-0004nj-C3; Sat, 29 Sep 2012 17:25:18 +0000
Received: from mail6.bemta5.messagelabs.com ([195.245.231.135])
	by lists.xen.org with esmtp (Exim 4.72)
	(envelope-from ) id 1TI0mz-0004nS-09
	for xen-users@lists.xen.org; Sat, 29 Sep 2012 17:25:17 +0000
Received: from [85.158.139.211:62098] by server-3.bemta-5.messagelabs.com id
	60/3D-16108-BFE27605; Sat, 29 Sep 2012 17:25:15 +0000
X-Env-Sender: cdelorme@gmail.com
X-Msg-Ref: server-12.tower-206.messagelabs.com!1348939513!19434243!1
X-Originating-IP: [209.85.214.173]
X-SpamReason: No, hits=1.2 required=7.0 tests=HTML_20_30,HTML_MESSAGE,
	ML_RADAR_SPEW_LINKS_14,RCVD_BY_IP,spamassassin: 
X-StarScan-Received: 
X-StarScan-Version: 6.6.1.3; banners=-,-,-
X-VirusChecked: Checked
Received: (qmail 31529 invoked from network); 29 Sep 2012 17:25:14 -0000
Received: from mail-ob0-f173.google.com (HELO mail-ob0-f173.google.com)
	(209.85.214.173)
	by server-12.tower-206.messagelabs.com with RC4-SHA encrypted SMTP;
	29 Sep 2012 17:25:14 -0000
Received: by obbwc18 with SMTP id wc18so2426769obb.32
	for ; Sat, 29 Sep 2012 10:25:12 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;
	h=mime-version:in-reply-to:references:date:message-id:subject:from:to
	:cc:content-type;
	bh=97FDdDUhzKRADBgV7n/16cU5654oQdWA1zbFOxmPFKI=;
	b=SPKRCCWrTzWtwcFSPF5+8snWVWZiJMuhZMIcoBBgE+epGk+Ti95z76Xpa8HUHCdAy6
	ijuaI4aBa9jm1EXI8OvmiqoxL0EysqLsIhoBJHhxstXy3tvqg6HaKywIuroxxpVHpxJ4
	4ddtiSbyIoLURNQMdpSCB+ZdXuBifjf5+2TVGXrm3TevVr5RaNMRkW5NPJFAlMa4/naw
	44qBxjK+J0Dee8InHdd/TjTqbY2UgnZN69P0QT/oLycarnutByBxZ1QgmiZSjoW1/UVT
	55pbyCKJu6AeDxRqn0zTL98xd2VtMamtpHb+wAyMcxacLKLZ5/lNZBEUWuVzNyISCkV2
	gmzQ==
MIME-Version: 1.0
Received: by 10.60.172.235 with SMTP id bf11mr8124760oec.30.1348939512753;
	Sat, 29 Sep 2012 10:25:12 -0700 (PDT)
Received: by 10.76.19.148 with HTTP; Sat, 29 Sep 2012 10:25:12 -0700 (PDT)
In-Reply-To: <50672690.9070504@gmail.com>
References: <5066F922.1090305@gmail.com> <50671D3D.1010304@gmail.com>
	
	<50672690.9070504@gmail.com>
Date: Sat, 29 Sep 2012 13:25:12 -0400
Message-ID: 
From: Casey DeLorme 
To: "Teo En Ming (Zhang Enming)" 
Cc: "xen-users@lists.xen.org" ,
	"xen-devel@lists.xen.org" 
Subject: Re: [Xen-users] Unable to start Windows 8 HVM guest with Xen VGA
 Passthrough with Xen 4.2.1-pre
X-BeenThere: xen-users@lists.xen.org
X-Mailman-Version: 2.1.13
Precedence: list
List-Id: Xen user discussion 
List-Unsubscribe: ,
	
List-Post: 
List-Help: 
List-Subscribe: ,
	
Content-Type: multipart/mixed; boundary="===============1141923552496618835=="
Sender: xen-users-bounces@lists.xen.org
Errors-To: xen-users-bounces@lists.xen.org

--===============1141923552496618835==
Content-Type: multipart/alternative; boundary=bcaec54ee8387b2d6b04cada7487

--bcaec54ee8387b2d6b04cada7487
Content-Type: text/plain; charset=ISO-8859-1

I am working with 32GB, so you probably don't want to model your
configuration after mine.  My problem was memory was not being freed from
Dom0 fast enough.

If you have already lowered Dom0 memory, checked it with xl info, and are
still having problems launching, then it might be something else.

My assumption is the memory assigned in the configuration is not a 1:1 map
to what is required.

---

I decided to run some tests to see how Xen used my memory.

Starting with Dom0 and ipfire running, I ran xl info, got the diff, and
then xl list and compared the two to find that xl info shows 500MB more
memory used up.

I started Windows, and again roughly 500MB unaccounted for.

---

So, based on that information I can assume Xen requires half a gigabyte to
work with in the backend for its normal responsibilities.

The wiki has a best practices which shows 512MB set for Dom0:
http://wiki.xen.org/wiki/Xen_Best_Practices


I would try setting 512MB in your grub configuration like the above, check
available RAM after your reload using `xl info`, making sure you have more
than the 2GB set in the HVM configuration.

If it still doesn't work, then it must be something different.  You could
also try lowering the memory in your DomU configuration as an alternative,
just to see if it works.

--bcaec54ee8387b2d6b04cada7487
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable


I am working with 32GB, so you probably don't want to model y=
our configuration after mine. =A0My problem was memory was not being freed =
from Dom0 fast enough.

If you have alre=
ady lowered Dom0 memory, checked it with xl info, and are still having prob=
lems launching, then it might be something else.



My assumption is the memory assigned in the configurati=
on is not a 1:1 map to what is required.

---
=


I decided to run some tests to see how Xen used my memo=
ry.



Starting with Dom0 and ipfire running, I ran xl info, g=
ot the diff, and then xl list and compared the two to find that xl info sho=
ws 500MB more memory used up.

I started Windows, a=
nd again roughly 500MB unaccounted for.



---

So, based on that informat=
ion I can assume Xen requires half a gigabyte to work with in the backend f=
or its normal responsibilities.

The wiki has a bes=
t practices which shows 512MB set for Dom0:




I=
 would try setting 512MB in your grub configuration like the above, check a=
vailable RAM after your reload using `xl info`, making sure you have more t=
han the 2GB set in the HVM configuration.



If it still doesn't work, then it must be something=
 different. =A0You could also try lowering the memory in your DomU configur=
ation as an alternative, just to see if it works.


--bcaec54ee8387b2d6b04cada7487--


--===============1141923552496618835==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
Xen-users mailing list
Xen-users@lists.xen.org
http://lists.xen.org/xen-users
--===============1141923552496618835==--


From xen-users-bounces@lists.xen.org Sat Sep 29 17:26:06 2012
Return-path: 
Envelope-to: archives@lists.xen.org
Delivery-date: Sat, 29 Sep 2012 17:26:06 +0000
Received: from localhost ([127.0.0.1] helo=lists.xen.org)
	by lists.xen.org with esmtp (Exim 4.72)
	(envelope-from )
	id 1TI0n0-0004nj-C3; Sat, 29 Sep 2012 17:25:18 +0000
Received: from mail6.bemta5.messagelabs.com ([195.245.231.135])
	by lists.xen.org with esmtp (Exim 4.72)
	(envelope-from ) id 1TI0mz-0004nS-09
	for xen-users@lists.xen.org; Sat, 29 Sep 2012 17:25:17 +0000
Received: from [85.158.139.211:62098] by server-3.bemta-5.messagelabs.com id
	60/3D-16108-BFE27605; Sat, 29 Sep 2012 17:25:15 +0000
X-Env-Sender: cdelorme@gmail.com
X-Msg-Ref: server-12.tower-206.messagelabs.com!1348939513!19434243!1
X-Originating-IP: [209.85.214.173]
X-SpamReason: No, hits=1.2 required=7.0 tests=HTML_20_30,HTML_MESSAGE,
	ML_RADAR_SPEW_LINKS_14,RCVD_BY_IP,spamassassin: 
X-StarScan-Received: 
X-StarScan-Version: 6.6.1.3; banners=-,-,-
X-VirusChecked: Checked
Received: (qmail 31529 invoked from network); 29 Sep 2012 17:25:14 -0000
Received: from mail-ob0-f173.google.com (HELO mail-ob0-f173.google.com)
	(209.85.214.173)
	by server-12.tower-206.messagelabs.com with RC4-SHA encrypted SMTP;
	29 Sep 2012 17:25:14 -0000
Received: by obbwc18 with SMTP id wc18so2426769obb.32
	for ; Sat, 29 Sep 2012 10:25:12 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;
	h=mime-version:in-reply-to:references:date:message-id:subject:from:to
	:cc:content-type;
	bh=97FDdDUhzKRADBgV7n/16cU5654oQdWA1zbFOxmPFKI=;
	b=SPKRCCWrTzWtwcFSPF5+8snWVWZiJMuhZMIcoBBgE+epGk+Ti95z76Xpa8HUHCdAy6
	ijuaI4aBa9jm1EXI8OvmiqoxL0EysqLsIhoBJHhxstXy3tvqg6HaKywIuroxxpVHpxJ4
	4ddtiSbyIoLURNQMdpSCB+ZdXuBifjf5+2TVGXrm3TevVr5RaNMRkW5NPJFAlMa4/naw
	44qBxjK+J0Dee8InHdd/TjTqbY2UgnZN69P0QT/oLycarnutByBxZ1QgmiZSjoW1/UVT
	55pbyCKJu6AeDxRqn0zTL98xd2VtMamtpHb+wAyMcxacLKLZ5/lNZBEUWuVzNyISCkV2
	gmzQ==
MIME-Version: 1.0
Received: by 10.60.172.235 with SMTP id bf11mr8124760oec.30.1348939512753;
	Sat, 29 Sep 2012 10:25:12 -0700 (PDT)
Received: by 10.76.19.148 with HTTP; Sat, 29 Sep 2012 10:25:12 -0700 (PDT)
In-Reply-To: <50672690.9070504@gmail.com>
References: <5066F922.1090305@gmail.com> <50671D3D.1010304@gmail.com>
	
	<50672690.9070504@gmail.com>
Date: Sat, 29 Sep 2012 13:25:12 -0400
Message-ID: 
From: Casey DeLorme 
To: "Teo En Ming (Zhang Enming)" 
Cc: "xen-users@lists.xen.org" ,
	"xen-devel@lists.xen.org" 
Subject: Re: [Xen-users] Unable to start Windows 8 HVM guest with Xen VGA
 Passthrough with Xen 4.2.1-pre
X-BeenThere: xen-users@lists.xen.org
X-Mailman-Version: 2.1.13
Precedence: list
List-Id: Xen user discussion 
List-Unsubscribe: ,
	
List-Post: 
List-Help: 
List-Subscribe: ,
	
Content-Type: multipart/mixed; boundary="===============1141923552496618835=="
Sender: xen-users-bounces@lists.xen.org
Errors-To: xen-users-bounces@lists.xen.org

--===============1141923552496618835==
Content-Type: multipart/alternative; boundary=bcaec54ee8387b2d6b04cada7487

--bcaec54ee8387b2d6b04cada7487
Content-Type: text/plain; charset=ISO-8859-1

I am working with 32GB, so you probably don't want to model your
configuration after mine.  My problem was memory was not being freed from
Dom0 fast enough.

If you have already lowered Dom0 memory, checked it with xl info, and are
still having problems launching, then it might be something else.

My assumption is the memory assigned in the configuration is not a 1:1 map
to what is required.

---

I decided to run some tests to see how Xen used my memory.

Starting with Dom0 and ipfire running, I ran xl info, got the diff, and
then xl list and compared the two to find that xl info shows 500MB more
memory used up.

I started Windows, and again roughly 500MB unaccounted for.

---

So, based on that information I can assume Xen requires half a gigabyte to
work with in the backend for its normal responsibilities.

The wiki has a best practices which shows 512MB set for Dom0:
http://wiki.xen.org/wiki/Xen_Best_Practices


I would try setting 512MB in your grub configuration like the above, check
available RAM after your reload using `xl info`, making sure you have more
than the 2GB set in the HVM configuration.

If it still doesn't work, then it must be something different.  You could
also try lowering the memory in your DomU configuration as an alternative,
just to see if it works.

--bcaec54ee8387b2d6b04cada7487
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable


I am working with 32GB, so you probably don't want to model y=
our configuration after mine. =A0My problem was memory was not being freed =
from Dom0 fast enough.

If you have alre=
ady lowered Dom0 memory, checked it with xl info, and are still having prob=
lems launching, then it might be something else.



My assumption is the memory assigned in the configurati=
on is not a 1:1 map to what is required.

---
=


I decided to run some tests to see how Xen used my memo=
ry.



Starting with Dom0 and ipfire running, I ran xl info, g=
ot the diff, and then xl list and compared the two to find that xl info sho=
ws 500MB more memory used up.

I started Windows, a=
nd again roughly 500MB unaccounted for.



---

So, based on that informat=
ion I can assume Xen requires half a gigabyte to work with in the backend f=
or its normal responsibilities.

The wiki has a bes=
t practices which shows 512MB set for Dom0:




I=
 would try setting 512MB in your grub configuration like the above, check a=
vailable RAM after your reload using `xl info`, making sure you have more t=
han the 2GB set in the HVM configuration.



If it still doesn't work, then it must be something=
 different. =A0You could also try lowering the memory in your DomU configur=
ation as an alternative, just to see if it works.


--bcaec54ee8387b2d6b04cada7487--


--===============1141923552496618835==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
Xen-users mailing list
Xen-users@lists.xen.org
http://lists.xen.org/xen-users
--===============1141923552496618835==--


From xen-users-bounces@lists.xen.org Sat Sep 29 17:42:35 2012
Return-path: 
Envelope-to: archives@lists.xen.org
Delivery-date: Sat, 29 Sep 2012 17:42:35 +0000
Received: from localhost ([127.0.0.1] helo=lists.xen.org)
	by lists.xen.org with esmtp (Exim 4.72)
	(envelope-from )
	id 1TI135-0005KC-9A; Sat, 29 Sep 2012 17:41:55 +0000
Received: from mail6.bemta5.messagelabs.com ([195.245.231.135])
	by lists.xen.org with esmtp (Exim 4.72)
	(envelope-from ) id 1TI133-0005K7-7J
	for Xen-users@lists.xen.org; Sat, 29 Sep 2012 17:41:53 +0000
Received: from [85.158.139.211:5444] by server-6.bemta-5.messagelabs.com id
	55/A9-14717-0E237605; Sat, 29 Sep 2012 17:41:52 +0000
X-Env-Sender: imperiaonline4@gmail.com
X-Msg-Ref: server-2.tower-206.messagelabs.com!1348940509!20426949!1
X-Originating-IP: [209.85.214.173]
X-SpamReason: No, hits=1.2 required=7.0 tests=HTML_20_30,HTML_MESSAGE,
	ML_RADAR_SPEW_LINKS_14,RCVD_BY_IP,spamassassin: 
X-StarScan-Received: 
X-StarScan-Version: 6.6.1.3; banners=-,-,-
X-VirusChecked: Checked
Received: (qmail 19424 invoked from network); 29 Sep 2012 17:41:51 -0000
Received: from mail-ob0-f173.google.com (HELO mail-ob0-f173.google.com)
	(209.85.214.173)
	by server-2.tower-206.messagelabs.com with RC4-SHA encrypted SMTP;
	29 Sep 2012 17:41:51 -0000
Received: by obbwc18 with SMTP id wc18so2435567obb.32
	for ; Sat, 29 Sep 2012 10:41:49 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;
	h=mime-version:in-reply-to:references:date:message-id:subject:from:to
	:content-type; bh=/+mF1ChWMN3u3xsysj8jdNqAREUiuJ19/F3NsM/GPJY=;
	b=HZ0JvnI9OcrbesfVmM2ozxxrO+FhZziOoIQqis4VDNVVnGXWTRbqi1aFailBtNN+xr
	zQ0u/lKSUw0q3yVcS+6zggLtjebWN/OLgSaB7Drt7FgPSzjFn0QK9mkxxM0rT5PQQxja
	cAxQhAsmRjI0HQx4dgcVpoquyk83L5NEXD0g9dnBRNDwkHQm3UbQSvsD9sZtCSi4g/t4
	S1k6lctjcYEYfGoUVL7iy0CkSmqci/SjlZy1R8DsEK2ygZvvDTUev2Tl8gtJVOn+3qnO
	uX49CwnxwNvyGD4/ebXQfxaVFZ4LXHIX5wxwHag0r/Y9hNSlE+z7zSQxCviRUBVF/htL
	AJgA==
MIME-Version: 1.0
Received: by 10.60.172.20 with SMTP id ay20mr8622805oec.71.1348940509231; Sat,
	29 Sep 2012 10:41:49 -0700 (PDT)
Received: by 10.60.146.236 with HTTP; Sat, 29 Sep 2012 10:41:49 -0700 (PDT)
In-Reply-To: 
References: 
	<50645166.2000200@gmail.com> <50647B26.9080903@gmail.com>
	
	<50648CEA.9070107@gmail.com>
	
	
	
	<5066CE0D.9080402@gmail.com> <5066F96C.1070908@gmail.com>
	
Date: Sat, 29 Sep 2012 19:41:49 +0200
Message-ID: 
From: Dariusz Krempa 
To: "xen-users@lists.xen.org" 
Content-Type: multipart/mixed; boundary=bcaec550b12ee0393404cadaaf5c
Subject: [Xen-users] Fwd: Success VGA passthrough on windows 7 x64 with Xen
	4.2.1-pre
X-BeenThere: xen-users@lists.xen.org
X-Mailman-Version: 2.1.13
Precedence: list
List-Id: Xen user discussion 
List-Unsubscribe: ,
	
List-Post: 
List-Help: 
List-Subscribe: ,
	
Sender: xen-users-bounces@lists.xen.org
Errors-To: xen-users-bounces@lists.xen.org

--bcaec550b12ee0393404cadaaf5c
Content-Type: multipart/alternative; boundary=bcaec550b12ee0392c04cadaaf5a

--bcaec550b12ee0392c04cadaaf5a
Content-Type: text/plain; charset=ISO-8859-1

*menuentry 'Ubuntu GNU/Linux, with Xen 4.2.1-pre and Linux
3.6.0-rc7-xen-4.2-testing' --class ubuntu --class gnu-linux --class gnu
--class os --class xe*
*n {*
*        insmod lvm*
*        insmod part_msdos*
*        insmod ext2*
*        set root='(ubuntu-root)'*
*        search --no-floppy --fs-uuid --set=root
8626e2ee-67d6-4f8b-a407-d0c73a445104*
*        echo    'Loading Xen 4.2.1-pre ...'*
*        multiboot       /boot/xen-4.2.1-pre.gz placeholder  *
*        echo    'Loading Linux 3.6.0-rc7-xen-4.2-testing ...'*
*        module  /boot/vmlinuz-3.6.0-rc7-xen-4.2-testing placeholder
root=/dev/mapper/ubuntu-root ro  splash quiet
xen-pciback.hide=(0:1d.0)(1:00.0)(1:00.1)*
*        echo    'Loading initial ramdisk ...'*
*        module  /boot/initrd.img-3.6.0-rc7-xen-4.2-testing*
*}*

>> Dear Dariusz Krempa,
>>
>> Could you publish your xen vga passthrough configuration files, namely
the
>> windows 7 x64 HVM domU configuration file?
>>
>> I have tried setting pci_msitranslate to 1 and also 0 but the nasty
yellow
>> triangle with an exclamation mark and error 43 won't go away.
>> pci_msitranslate has no effect on my system.
>>
>> Thank you very much.
>>

No problem, there are my configurations for DomU windows 7 and 8. And this
my grub configuration :



>
> Hi,
>
> I have applied Xen VGA passthrough patches from David Techer's personal
> website to Xen 4.2.1-pre source tree. Everything compiled and installed
> smoothly. But when I tried to start Windows 8 HVM domU with VGA
passthrough,
> it gave me the following error:
>
> xc: error: unable to allocate memory to the HVM guest. (16: device or
> resource busy): Internal error.
>
> There are no issues with Xen 4.2-unstable changeset 25099 however.
>
>
> --
> Yours sincerely,
>
> Mr. Teo En Ming (Zhang Enming)
> Singapore
>

I have this error a lot time with Xen 4.2+ but i just repeat create command
and all is fine.

--bcaec550b12ee0392c04cadaaf5a
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable


menuentry 'Ubuntu GNU/Linux, wit=
h Xen 4.2.1-pre and Linux 3.6.0-rc7-xen-4.2-testing' --class ubuntu --c=
lass gnu-linux --class gnu --class os --class xe
n {

=A0 =A0 =A0 =A0 insmod lvm


=A0 =A0 =A0 =A0 insmod part_msdos
=A0 =A0 =A0 =A0 =
insmod ext2
=A0 =A0 =A0 =A0 set root=3D'(ubuntu-root)&=
#39;
=A0 =A0 =A0 =A0 search --no-floppy --fs-uuid --set=3D=
root 8626e2ee-67d6-4f8b-a407-d0c73a445104



=A0 =A0 =A0 =A0 echo =A0 =A0'Loading Xen 4.2.1-pre ...'=

=A0 =A0 =A0 =A0 multiboot =A0 =A0 =A0 /boot/xen-4.2.1-pre.gz =
placeholder =A0
=A0 =A0 =A0 =A0 echo =A0 =A0'Loading L=
inux 3.6.0-rc7-xen-4.2-testing ...'



=A0 =A0 =A0 =A0 module =A0/boot/vmlinuz-3.6.0-rc7-xen-4.2-testing p=
laceholder root=3D/dev/mapper/ubuntu-root ro =A0splash quiet xen-pciback.hi=
de=3D(0:1d.0)(1:00.0)(1:00.1)
=A0 =A0 =A0 =A0 echo =A0 =A0=
'Loading initial ramdisk ...'



=A0 =A0 =A0 =A0 module =A0/boot/initrd.img-3.6.0-rc7-xen-4.2-testin=
g
}

>> Dea=
r Dariusz Krempa,
>>
>> Could you publish your xen vga pa=
ssthrough configuration files, namely the


>> windows 7 x64 HVM domU configuration file?
>>
>>=
 I have tried setting pci_msitranslate to 1 and also 0 but the nasty yellow=

>> triangle with an exclamation mark and error 43 won't go aw=
ay.


>> pci_msitranslate has no effect on my system.
>>
>&g=
t; Thank you very much.
>>

No problem, there are my c=
onfigurations for DomU windows 7 and 8. And this my grub configuration :




>
> Hi,
>
> I have applied Xen VGA passthrough pat=
ches from David Techer's personal
> website to Xen 4.2.1-pre sour=
ce tree. Everything compiled and installed
> smoothly. But when I tri=
ed to start Windows 8 HVM domU with VGA passthrough,


> it gave me the following error:
>
> xc: error: unable to a=
llocate memory to the HVM guest. (16: device or
> resource busy): Int=
ernal error.
>
> There are no issues with Xen 4.2-unstable chan=
geset 25099 however.


>
>
> --
> Yours sincerely,
>
> Mr. Teo En=
 Ming (Zhang Enming)
> Singapore
>

I have this err=
or a lot time with Xen 4.2+ but i just repeat create command and all is fin=
e.






--bcaec550b12ee0392c04cadaaf5a--
--bcaec550b12ee0393404cadaaf5c
Content-Type: application/octet-stream; name=windows7
Content-Disposition: attachment; filename=windows7
Content-Transfer-Encoding: base64
X-Attachment-Id: f_h7oymteb0

YnVpbGRlcj0naHZtJwptZW1vcnkgPSAyMDEyCiNzaGFkb3dfbWVtb3J5ID0gNDAwCm5hbWUgPSAi
d2luZG93cyIKdmNwdXM9JzMnCnZpZj1bICdicmlkZ2U9eGVuYnIwLCBtYWM9MDA6MTY6NGU6NDk6
NjQ6MWMnXQoKZGlzayA9IFsKCQkncGh5Oi9kZXYveGVuLWh2L3dpbmRvd3M3LHh2ZGEsdycsCgkJ
J3BoeTovZGV2L3NyMCx4dmRjOmNkcm9tLHInLAogICAgICAgICBdCgpib290PSJjIgpzZGw9MAp2
bmM9MQp2bmNsaXN0ZW49IjAuMC4wLjA6MTAiCiN2bmNjb25zb2xlPTEKdm5jcGFzc3dkPScnCmFj
cGk9MQphcGljPTEKI3N2Z2E9MQp4ZW5fZXh0ZW5kZWRfcG93ZXJfbWdtdD0xCnBhZT0xCmFyY2g9
J3g4Nl82NCcKaHBldCA9IDEKaGFwID0gMQp2aXJpZGlhbiA9IDEKbW9uaXRvcj0xCiNzZXJpYWw9
J3B0eScKa2V5bWFwPSdwbCcKI3NvdW5kaHcgPSAiYWxsIgojYXVkaW89Im9uIgojbmUyMDAwPTAK
b25fcG93ZXJvZmYgPSAnZGVzdHJveScKb25fcmVib290ICAgPSAncmVzdGFydCcKb25fY3Jhc2gg
ICAgPSAnZGVzdHJveScKeGVuX3BsYXRmb3JtX3BjaT0xIApnZnhfcGFzc3RocnU9MQpwY2kgID0g
WycwMDoxZC4wJywnMTowMC4wJywnMTowMC4xJyBdCnVzYiA9IDEKI3BjaV9tc2l0cmFuc2xhdGUg
PSAxCnBjaV9wb3dlcl9tZ210ID0gMQphY3BpX3MzID0gMQphY3BpX3M0ID0gMQp1c2JkZXZpY2U9
J3RhYmxldCcKCg==
--bcaec550b12ee0393404cadaaf5c
Content-Type: application/octet-stream; name=windows8
Content-Disposition: attachment; filename=windows8
Content-Transfer-Encoding: base64
X-Attachment-Id: f_h7oynf8u1

YnVpbGRlcj0naHZtJwptZW1vcnkgPSAyMDEyCiNzaGFkb3dfbWVtb3J5ID0gNDAwCm5hbWUgPSAi
d2luZG93cyIKdmNwdXM9JzMnCnZpZj1bICdicmlkZ2U9eGVuYnIwLCBtYWM9MDA6MTY6NGU6NDk6
NjQ6MWEnXQoKZGlzayA9IFsKCQkncGh5Oi9kZXYveGVuLWh2L3dpbmRvd3M4LHh2ZGEsdycsCQkK
CQkncGh5Oi9kZXYvc3IwLHh2ZGM6Y2Ryb20scicsCiAgICAgICAgIF0KCmJvb3Q9ImMiCnNkbD0w
CnZuYz0xCnZuY2xpc3Rlbj0iMC4wLjAuMCIKdm5jY29uc29sZT0xCnZuY3Bhc3N3ZD0nJwphY3Bp
PTEKYXBpYz0xCiNzdmdhPTEKI3hlbl9leHRlbmRlZF9wb3dlcl9tZ210PTEKcGFlPTEKYXJjaD0n
eDg2XzY0JwojaHBldCA9IDEKI2hhcCA9IDEKdmlyaWRpYW4gPSAxCm1vbml0b3I9MQojc2VyaWFs
PSdwdHknCmtleW1hcD0ncGwnCiNzb3VuZGh3ID0gImFsbCIKI2F1ZGlvPSJvbiIKI25lMjAwMD0w
Cm9uX3Bvd2Vyb2ZmID0gJ2Rlc3Ryb3knCm9uX3JlYm9vdCAgID0gJ3Jlc3RhcnQnCm9uX2NyYXNo
ICAgID0gJ2Rlc3Ryb3knCiN4ZW5fcGxhdGZvcm1fcGNpPTEgCmdmeF9wYXNzdGhydT0xCnBjaSAg
PSBbJzE6MDAuMCcsJzE6MDAuMScgXQp1c2IgPSAxCiNwY2lfbXNpdHJhbnNsYXRlID0gMQojcGNp
X3Bvd2VyX21nbXQgPSAxCmFjcGlfczMgPSAxCmFjcGlfczQgPSAxCnVzYmRldmljZT0ndGFibGV0
JwoKI2RldmljZV9tb2RlbF92ZXJzaW9uPSdxdWVtdS14ZW4nCgo=
--bcaec550b12ee0393404cadaaf5c
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
Xen-users mailing list
Xen-users@lists.xen.org
http://lists.xen.org/xen-users
--bcaec550b12ee0393404cadaaf5c--


From xen-users-bounces@lists.xen.org Sat Sep 29 17:42:35 2012
Return-path: 
Envelope-to: archives@lists.xen.org
Delivery-date: Sat, 29 Sep 2012 17:42:35 +0000
Received: from localhost ([127.0.0.1] helo=lists.xen.org)
	by lists.xen.org with esmtp (Exim 4.72)
	(envelope-from )
	id 1TI135-0005KC-9A; Sat, 29 Sep 2012 17:41:55 +0000
Received: from mail6.bemta5.messagelabs.com ([195.245.231.135])
	by lists.xen.org with esmtp (Exim 4.72)
	(envelope-from ) id 1TI133-0005K7-7J
	for Xen-users@lists.xen.org; Sat, 29 Sep 2012 17:41:53 +0000
Received: from [85.158.139.211:5444] by server-6.bemta-5.messagelabs.com id
	55/A9-14717-0E237605; Sat, 29 Sep 2012 17:41:52 +0000
X-Env-Sender: imperiaonline4@gmail.com
X-Msg-Ref: server-2.tower-206.messagelabs.com!1348940509!20426949!1
X-Originating-IP: [209.85.214.173]
X-SpamReason: No, hits=1.2 required=7.0 tests=HTML_20_30,HTML_MESSAGE,
	ML_RADAR_SPEW_LINKS_14,RCVD_BY_IP,spamassassin: 
X-StarScan-Received: 
X-StarScan-Version: 6.6.1.3; banners=-,-,-
X-VirusChecked: Checked
Received: (qmail 19424 invoked from network); 29 Sep 2012 17:41:51 -0000
Received: from mail-ob0-f173.google.com (HELO mail-ob0-f173.google.com)
	(209.85.214.173)
	by server-2.tower-206.messagelabs.com with RC4-SHA encrypted SMTP;
	29 Sep 2012 17:41:51 -0000
Received: by obbwc18 with SMTP id wc18so2435567obb.32
	for ; Sat, 29 Sep 2012 10:41:49 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;
	h=mime-version:in-reply-to:references:date:message-id:subject:from:to
	:content-type; bh=/+mF1ChWMN3u3xsysj8jdNqAREUiuJ19/F3NsM/GPJY=;
	b=HZ0JvnI9OcrbesfVmM2ozxxrO+FhZziOoIQqis4VDNVVnGXWTRbqi1aFailBtNN+xr
	zQ0u/lKSUw0q3yVcS+6zggLtjebWN/OLgSaB7Drt7FgPSzjFn0QK9mkxxM0rT5PQQxja
	cAxQhAsmRjI0HQx4dgcVpoquyk83L5NEXD0g9dnBRNDwkHQm3UbQSvsD9sZtCSi4g/t4
	S1k6lctjcYEYfGoUVL7iy0CkSmqci/SjlZy1R8DsEK2ygZvvDTUev2Tl8gtJVOn+3qnO
	uX49CwnxwNvyGD4/ebXQfxaVFZ4LXHIX5wxwHag0r/Y9hNSlE+z7zSQxCviRUBVF/htL
	AJgA==
MIME-Version: 1.0
Received: by 10.60.172.20 with SMTP id ay20mr8622805oec.71.1348940509231; Sat,
	29 Sep 2012 10:41:49 -0700 (PDT)
Received: by 10.60.146.236 with HTTP; Sat, 29 Sep 2012 10:41:49 -0700 (PDT)
In-Reply-To: 
References: 
	<50645166.2000200@gmail.com> <50647B26.9080903@gmail.com>
	
	<50648CEA.9070107@gmail.com>
	
	
	
	<5066CE0D.9080402@gmail.com> <5066F96C.1070908@gmail.com>
	
Date: Sat, 29 Sep 2012 19:41:49 +0200
Message-ID: 
From: Dariusz Krempa 
To: "xen-users@lists.xen.org" 
Content-Type: multipart/mixed; boundary=bcaec550b12ee0393404cadaaf5c
Subject: [Xen-users] Fwd: Success VGA passthrough on windows 7 x64 with Xen
	4.2.1-pre
X-BeenThere: xen-users@lists.xen.org
X-Mailman-Version: 2.1.13
Precedence: list
List-Id: Xen user discussion 
List-Unsubscribe: ,
	
List-Post: 
List-Help: 
List-Subscribe: ,
	
Sender: xen-users-bounces@lists.xen.org
Errors-To: xen-users-bounces@lists.xen.org

--bcaec550b12ee0393404cadaaf5c
Content-Type: multipart/alternative; boundary=bcaec550b12ee0392c04cadaaf5a

--bcaec550b12ee0392c04cadaaf5a
Content-Type: text/plain; charset=ISO-8859-1

*menuentry 'Ubuntu GNU/Linux, with Xen 4.2.1-pre and Linux
3.6.0-rc7-xen-4.2-testing' --class ubuntu --class gnu-linux --class gnu
--class os --class xe*
*n {*
*        insmod lvm*
*        insmod part_msdos*
*        insmod ext2*
*        set root='(ubuntu-root)'*
*        search --no-floppy --fs-uuid --set=root
8626e2ee-67d6-4f8b-a407-d0c73a445104*
*        echo    'Loading Xen 4.2.1-pre ...'*
*        multiboot       /boot/xen-4.2.1-pre.gz placeholder  *
*        echo    'Loading Linux 3.6.0-rc7-xen-4.2-testing ...'*
*        module  /boot/vmlinuz-3.6.0-rc7-xen-4.2-testing placeholder
root=/dev/mapper/ubuntu-root ro  splash quiet
xen-pciback.hide=(0:1d.0)(1:00.0)(1:00.1)*
*        echo    'Loading initial ramdisk ...'*
*        module  /boot/initrd.img-3.6.0-rc7-xen-4.2-testing*
*}*

>> Dear Dariusz Krempa,
>>
>> Could you publish your xen vga passthrough configuration files, namely
the
>> windows 7 x64 HVM domU configuration file?
>>
>> I have tried setting pci_msitranslate to 1 and also 0 but the nasty
yellow
>> triangle with an exclamation mark and error 43 won't go away.
>> pci_msitranslate has no effect on my system.
>>
>> Thank you very much.
>>

No problem, there are my configurations for DomU windows 7 and 8. And this
my grub configuration :



>
> Hi,
>
> I have applied Xen VGA passthrough patches from David Techer's personal
> website to Xen 4.2.1-pre source tree. Everything compiled and installed
> smoothly. But when I tried to start Windows 8 HVM domU with VGA
passthrough,
> it gave me the following error:
>
> xc: error: unable to allocate memory to the HVM guest. (16: device or
> resource busy): Internal error.
>
> There are no issues with Xen 4.2-unstable changeset 25099 however.
>
>
> --
> Yours sincerely,
>
> Mr. Teo En Ming (Zhang Enming)
> Singapore
>

I have this error a lot time with Xen 4.2+ but i just repeat create command
and all is fine.

--bcaec550b12ee0392c04cadaaf5a
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable


menuentry 'Ubuntu GNU/Linux, wit=
h Xen 4.2.1-pre and Linux 3.6.0-rc7-xen-4.2-testing' --class ubuntu --c=
lass gnu-linux --class gnu --class os --class xe
n {

=A0 =A0 =A0 =A0 insmod lvm


=A0 =A0 =A0 =A0 insmod part_msdos
=A0 =A0 =A0 =A0 =
insmod ext2
=A0 =A0 =A0 =A0 set root=3D'(ubuntu-root)&=
#39;
=A0 =A0 =A0 =A0 search --no-floppy --fs-uuid --set=3D=
root 8626e2ee-67d6-4f8b-a407-d0c73a445104



=A0 =A0 =A0 =A0 echo =A0 =A0'Loading Xen 4.2.1-pre ...'=

=A0 =A0 =A0 =A0 multiboot =A0 =A0 =A0 /boot/xen-4.2.1-pre.gz =
placeholder =A0
=A0 =A0 =A0 =A0 echo =A0 =A0'Loading L=
inux 3.6.0-rc7-xen-4.2-testing ...'



=A0 =A0 =A0 =A0 module =A0/boot/vmlinuz-3.6.0-rc7-xen-4.2-testing p=
laceholder root=3D/dev/mapper/ubuntu-root ro =A0splash quiet xen-pciback.hi=
de=3D(0:1d.0)(1:00.0)(1:00.1)
=A0 =A0 =A0 =A0 echo =A0 =A0=
'Loading initial ramdisk ...'



=A0 =A0 =A0 =A0 module =A0/boot/initrd.img-3.6.0-rc7-xen-4.2-testin=
g
}

>> Dea=
r Dariusz Krempa,
>>
>> Could you publish your xen vga pa=
ssthrough configuration files, namely the


>> windows 7 x64 HVM domU configuration file?
>>
>>=
 I have tried setting pci_msitranslate to 1 and also 0 but the nasty yellow=

>> triangle with an exclamation mark and error 43 won't go aw=
ay.


>> pci_msitranslate has no effect on my system.
>>
>&g=
t; Thank you very much.
>>

No problem, there are my c=
onfigurations for DomU windows 7 and 8. And this my grub configuration :




>
> Hi,
>
> I have applied Xen VGA passthrough pat=
ches from David Techer's personal
> website to Xen 4.2.1-pre sour=
ce tree. Everything compiled and installed
> smoothly. But when I tri=
ed to start Windows 8 HVM domU with VGA passthrough,


> it gave me the following error:
>
> xc: error: unable to a=
llocate memory to the HVM guest. (16: device or
> resource busy): Int=
ernal error.
>
> There are no issues with Xen 4.2-unstable chan=
geset 25099 however.


>
>
> --
> Yours sincerely,
>
> Mr. Teo En=
 Ming (Zhang Enming)
> Singapore
>

I have this err=
or a lot time with Xen 4.2+ but i just repeat create command and all is fin=
e.






--bcaec550b12ee0392c04cadaaf5a--
--bcaec550b12ee0393404cadaaf5c
Content-Type: application/octet-stream; name=windows7
Content-Disposition: attachment; filename=windows7
Content-Transfer-Encoding: base64
X-Attachment-Id: f_h7oymteb0

YnVpbGRlcj0naHZtJwptZW1vcnkgPSAyMDEyCiNzaGFkb3dfbWVtb3J5ID0gNDAwCm5hbWUgPSAi
d2luZG93cyIKdmNwdXM9JzMnCnZpZj1bICdicmlkZ2U9eGVuYnIwLCBtYWM9MDA6MTY6NGU6NDk6
NjQ6MWMnXQoKZGlzayA9IFsKCQkncGh5Oi9kZXYveGVuLWh2L3dpbmRvd3M3LHh2ZGEsdycsCgkJ
J3BoeTovZGV2L3NyMCx4dmRjOmNkcm9tLHInLAogICAgICAgICBdCgpib290PSJjIgpzZGw9MAp2
bmM9MQp2bmNsaXN0ZW49IjAuMC4wLjA6MTAiCiN2bmNjb25zb2xlPTEKdm5jcGFzc3dkPScnCmFj
cGk9MQphcGljPTEKI3N2Z2E9MQp4ZW5fZXh0ZW5kZWRfcG93ZXJfbWdtdD0xCnBhZT0xCmFyY2g9
J3g4Nl82NCcKaHBldCA9IDEKaGFwID0gMQp2aXJpZGlhbiA9IDEKbW9uaXRvcj0xCiNzZXJpYWw9
J3B0eScKa2V5bWFwPSdwbCcKI3NvdW5kaHcgPSAiYWxsIgojYXVkaW89Im9uIgojbmUyMDAwPTAK
b25fcG93ZXJvZmYgPSAnZGVzdHJveScKb25fcmVib290ICAgPSAncmVzdGFydCcKb25fY3Jhc2gg
ICAgPSAnZGVzdHJveScKeGVuX3BsYXRmb3JtX3BjaT0xIApnZnhfcGFzc3RocnU9MQpwY2kgID0g
WycwMDoxZC4wJywnMTowMC4wJywnMTowMC4xJyBdCnVzYiA9IDEKI3BjaV9tc2l0cmFuc2xhdGUg
PSAxCnBjaV9wb3dlcl9tZ210ID0gMQphY3BpX3MzID0gMQphY3BpX3M0ID0gMQp1c2JkZXZpY2U9
J3RhYmxldCcKCg==
--bcaec550b12ee0393404cadaaf5c
Content-Type: application/octet-stream; name=windows8
Content-Disposition: attachment; filename=windows8
Content-Transfer-Encoding: base64
X-Attachment-Id: f_h7oynf8u1

YnVpbGRlcj0naHZtJwptZW1vcnkgPSAyMDEyCiNzaGFkb3dfbWVtb3J5ID0gNDAwCm5hbWUgPSAi
d2luZG93cyIKdmNwdXM9JzMnCnZpZj1bICdicmlkZ2U9eGVuYnIwLCBtYWM9MDA6MTY6NGU6NDk6
NjQ6MWEnXQoKZGlzayA9IFsKCQkncGh5Oi9kZXYveGVuLWh2L3dpbmRvd3M4LHh2ZGEsdycsCQkK
CQkncGh5Oi9kZXYvc3IwLHh2ZGM6Y2Ryb20scicsCiAgICAgICAgIF0KCmJvb3Q9ImMiCnNkbD0w
CnZuYz0xCnZuY2xpc3Rlbj0iMC4wLjAuMCIKdm5jY29uc29sZT0xCnZuY3Bhc3N3ZD0nJwphY3Bp
PTEKYXBpYz0xCiNzdmdhPTEKI3hlbl9leHRlbmRlZF9wb3dlcl9tZ210PTEKcGFlPTEKYXJjaD0n
eDg2XzY0JwojaHBldCA9IDEKI2hhcCA9IDEKdmlyaWRpYW4gPSAxCm1vbml0b3I9MQojc2VyaWFs
PSdwdHknCmtleW1hcD0ncGwnCiNzb3VuZGh3ID0gImFsbCIKI2F1ZGlvPSJvbiIKI25lMjAwMD0w
Cm9uX3Bvd2Vyb2ZmID0gJ2Rlc3Ryb3knCm9uX3JlYm9vdCAgID0gJ3Jlc3RhcnQnCm9uX2NyYXNo
ICAgID0gJ2Rlc3Ryb3knCiN4ZW5fcGxhdGZvcm1fcGNpPTEgCmdmeF9wYXNzdGhydT0xCnBjaSAg
PSBbJzE6MDAuMCcsJzE6MDAuMScgXQp1c2IgPSAxCiNwY2lfbXNpdHJhbnNsYXRlID0gMQojcGNp
X3Bvd2VyX21nbXQgPSAxCmFjcGlfczMgPSAxCmFjcGlfczQgPSAxCnVzYmRldmljZT0ndGFibGV0
JwoKI2RldmljZV9tb2RlbF92ZXJzaW9uPSdxdWVtdS14ZW4nCgo=
--bcaec550b12ee0393404cadaaf5c
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
Xen-users mailing list
Xen-users@lists.xen.org
http://lists.xen.org/xen-users
--bcaec550b12ee0393404cadaaf5c--


From xen-users-bounces@lists.xen.org Sat Sep 29 20:10:19 2012
Return-path: 
Envelope-to: archives@lists.xen.org
Delivery-date: Sat, 29 Sep 2012 20:10:19 +0000
Received: from localhost ([127.0.0.1] helo=lists.xen.org)
	by lists.xen.org with esmtp (Exim 4.72)
	(envelope-from )
	id 1TI3LU-0006LY-Ps; Sat, 29 Sep 2012 20:09:04 +0000
Received: from mail6.bemta5.messagelabs.com ([195.245.231.135])
	by lists.xen.org with esmtp (Exim 4.72)
	(envelope-from ) id 1TI3LT-0006LT-8a
	for Xen-users@lists.xen.org; Sat, 29 Sep 2012 20:09:03 +0000
Received: from [85.158.139.211:46146] by server-11.bemta-5.messagelabs.com id
	06/95-13866-E5557605; Sat, 29 Sep 2012 20:09:02 +0000
X-Env-Sender: imperiaonline4@gmail.com
X-Msg-Ref: server-7.tower-206.messagelabs.com!1348949340!19991916!1
X-Originating-IP: [209.85.219.45]
X-SpamReason: No, hits=1.2 required=7.0 tests=HTML_10_20,HTML_MESSAGE,
	ML_RADAR_SPEW_LINKS_14,RCVD_BY_IP,spamassassin: 
X-StarScan-Received: 
X-StarScan-Version: 6.6.1.3; banners=-,-,-
X-VirusChecked: Checked
Received: (qmail 7090 invoked from network); 29 Sep 2012 20:09:01 -0000
Received: from mail-oa0-f45.google.com (HELO mail-oa0-f45.google.com)
	(209.85.219.45)
	by server-7.tower-206.messagelabs.com with RC4-SHA encrypted SMTP;
	29 Sep 2012 20:09:01 -0000
Received: by oagi18 with SMTP id i18so5356173oag.32
	for ; Sat, 29 Sep 2012 13:09:00 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;
	h=mime-version:date:message-id:subject:from:to:content-type;
	bh=aYX1bw2pa6K6z85HrpnL6v3FZjcNtEOJPbb61b3hpMA=;
	b=DOnJpo4UvPSOgo2jwP565awrpNXxyAD6sSE5YDC9mL4Sbsmo+tCLGiD8meC63LxERX
	4+vrDvlWYPQ8LdRnit7aYzF8Ai5xmdFiCf+5+aQreV4OWyxvTFacoMxf8sJQIStBZBJC
	CXL4SO79rJoKmnB/1GJmnvkTXl7SnMlPkE0/PCbPjUx8Ma2pJlJWqfeboVj206OHOnwv
	7cPjFC/5xpZXd75mFhtNns6Fpo+olwxSjj38X7uNosm8eOC9BTG7UnzMExFjtDXESITX
	wTcnqgkiIKKIWrkG1EcnGElOQtoNkl6KPw5YfWA6kr+gLrI9nSDY87ajV93ZkGoq1ExT
	D4JQ==
MIME-Version: 1.0
Received: by 10.60.12.167 with SMTP id z7mr8750106oeb.121.1348949340073; Sat,
	29 Sep 2012 13:09:00 -0700 (PDT)
Received: by 10.60.146.236 with HTTP; Sat, 29 Sep 2012 13:09:00 -0700 (PDT)
Date: Sat, 29 Sep 2012 22:09:00 +0200
Message-ID: 
From: Dariusz Krempa 
To: "xen-users@lists.xen.org" 
Subject: [Xen-users] Xen 4.2.1-pre DomU create error
X-BeenThere: xen-users@lists.xen.org
X-Mailman-Version: 2.1.13
Precedence: list
List-Id: Xen user discussion 
List-Unsubscribe: ,
	
List-Post: 
List-Help: 
List-Subscribe: ,
	
Content-Type: multipart/mixed; boundary="===============2651914620515418738=="
Sender: xen-users-bounces@lists.xen.org
Errors-To: xen-users-bounces@lists.xen.org

--===============2651914620515418738==
Content-Type: multipart/alternative; boundary=e89a8fb1efa43c2e4504cadcbe90

--e89a8fb1efa43c2e4504cadcbe90
Content-Type: text/plain; charset=ISO-8859-1

Parsing config from server2008.cfg
xc: info: VIRTUAL MEMORY ARRANGEMENT:
  Loader:        0000000000100000->000000000019ddf0
  TOTAL:         0000000000000000->000000001f800000
  ENTRY ADDRESS: 0000000000100000
xc: info: PHYSICAL MEMORY ALLOCATION:
  4KB PAGES: 0x0000000000000200
  2MB PAGES: 0x00000000000000fb
  1GB PAGES: 0x0000000000000000
libxl: error: libxl_device.c:858:device_backend_callback: unable to
disconnect device with path /local/domain/0/backend/vbd/4/51744
libxl: error: libxl_create.c:933:domcreate_launch_dm: unable to add disk
devices
libxl: error: libxl_dm.c:1239:libxl__destroy_device_model: could not find
device-model's pid for dom 4
libxl: error: libxl.c:1429:libxl__destroy_domid:
libxl__destroy_device_model failed for 4


This error is very common in Xen 4.2.1-pre. I need to repeat create
command, sometimes few times to start DomU. This error don't let DomU to
restart. DomU is simple destroyed.

--e89a8fb1efa43c2e4504cadcbe90
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable


Parsing config from server2008.cfg
xc: info: VIRTUAL MEMORY =
ARRANGEMENT:
=A0 Loader: =A0 =A0 =A0 =A00000000000100000->0000=
00000019ddf0
=A0 TOTAL: =A0 =A0 =A0 =A0 0000000000000000->0000=
00001f800000



=A0 ENTRY ADDRESS: 0000000000100000
xc: info: PHYSICAL MEMOR=
Y ALLOCATION:
=A0 4KB PAGES: 0x0000000000000200
=A0 2MB=
 PAGES: 0x00000000000000fb
=A0 1GB PAGES: 0x0000000000000000


libxl: error: libxl_device.c:858:device_backend_callback: unable to disconn=
ect device with path /local/domain/0/backend/vbd/4/51744
libxl: e=
rror: libxl_create.c:933:domcreate_launch_dm: unable to add disk devices


libxl: error: libxl_dm.c:1239:libxl__destroy_device_model: could not f=
ind device-model's pid for dom 4
libxl: error: libxl.c:1429:l=
ibxl__destroy_domid: libxl__destroy_device_model failed for 4




This error is very common in Xen 4.2.1-pre. I=
 need to=A0repeat=A0create command, sometimes few times to start DomU. This=
 error don't let DomU to restart. DomU is simple destroyed.


--e89a8fb1efa43c2e4504cadcbe90--


--===============2651914620515418738==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
Xen-users mailing list
Xen-users@lists.xen.org
http://lists.xen.org/xen-users
--===============2651914620515418738==--


From xen-users-bounces@lists.xen.org Sat Sep 29 20:10:19 2012
Return-path: 
Envelope-to: archives@lists.xen.org
Delivery-date: Sat, 29 Sep 2012 20:10:19 +0000
Received: from localhost ([127.0.0.1] helo=lists.xen.org)
	by lists.xen.org with esmtp (Exim 4.72)
	(envelope-from )
	id 1TI3LU-0006LY-Ps; Sat, 29 Sep 2012 20:09:04 +0000
Received: from mail6.bemta5.messagelabs.com ([195.245.231.135])
	by lists.xen.org with esmtp (Exim 4.72)
	(envelope-from ) id 1TI3LT-0006LT-8a
	for Xen-users@lists.xen.org; Sat, 29 Sep 2012 20:09:03 +0000
Received: from [85.158.139.211:46146] by server-11.bemta-5.messagelabs.com id
	06/95-13866-E5557605; Sat, 29 Sep 2012 20:09:02 +0000
X-Env-Sender: imperiaonline4@gmail.com
X-Msg-Ref: server-7.tower-206.messagelabs.com!1348949340!19991916!1
X-Originating-IP: [209.85.219.45]
X-SpamReason: No, hits=1.2 required=7.0 tests=HTML_10_20,HTML_MESSAGE,
	ML_RADAR_SPEW_LINKS_14,RCVD_BY_IP,spamassassin: 
X-StarScan-Received: 
X-StarScan-Version: 6.6.1.3; banners=-,-,-
X-VirusChecked: Checked
Received: (qmail 7090 invoked from network); 29 Sep 2012 20:09:01 -0000
Received: from mail-oa0-f45.google.com (HELO mail-oa0-f45.google.com)
	(209.85.219.45)
	by server-7.tower-206.messagelabs.com with RC4-SHA encrypted SMTP;
	29 Sep 2012 20:09:01 -0000
Received: by oagi18 with SMTP id i18so5356173oag.32
	for ; Sat, 29 Sep 2012 13:09:00 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;
	h=mime-version:date:message-id:subject:from:to:content-type;
	bh=aYX1bw2pa6K6z85HrpnL6v3FZjcNtEOJPbb61b3hpMA=;
	b=DOnJpo4UvPSOgo2jwP565awrpNXxyAD6sSE5YDC9mL4Sbsmo+tCLGiD8meC63LxERX
	4+vrDvlWYPQ8LdRnit7aYzF8Ai5xmdFiCf+5+aQreV4OWyxvTFacoMxf8sJQIStBZBJC
	CXL4SO79rJoKmnB/1GJmnvkTXl7SnMlPkE0/PCbPjUx8Ma2pJlJWqfeboVj206OHOnwv
	7cPjFC/5xpZXd75mFhtNns6Fpo+olwxSjj38X7uNosm8eOC9BTG7UnzMExFjtDXESITX
	wTcnqgkiIKKIWrkG1EcnGElOQtoNkl6KPw5YfWA6kr+gLrI9nSDY87ajV93ZkGoq1ExT
	D4JQ==
MIME-Version: 1.0
Received: by 10.60.12.167 with SMTP id z7mr8750106oeb.121.1348949340073; Sat,
	29 Sep 2012 13:09:00 -0700 (PDT)
Received: by 10.60.146.236 with HTTP; Sat, 29 Sep 2012 13:09:00 -0700 (PDT)
Date: Sat, 29 Sep 2012 22:09:00 +0200
Message-ID: 
From: Dariusz Krempa 
To: "xen-users@lists.xen.org" 
Subject: [Xen-users] Xen 4.2.1-pre DomU create error
X-BeenThere: xen-users@lists.xen.org
X-Mailman-Version: 2.1.13
Precedence: list
List-Id: Xen user discussion 
List-Unsubscribe: ,
	
List-Post: 
List-Help: 
List-Subscribe: ,
	
Content-Type: multipart/mixed; boundary="===============2651914620515418738=="
Sender: xen-users-bounces@lists.xen.org
Errors-To: xen-users-bounces@lists.xen.org

--===============2651914620515418738==
Content-Type: multipart/alternative; boundary=e89a8fb1efa43c2e4504cadcbe90

--e89a8fb1efa43c2e4504cadcbe90
Content-Type: text/plain; charset=ISO-8859-1

Parsing config from server2008.cfg
xc: info: VIRTUAL MEMORY ARRANGEMENT:
  Loader:        0000000000100000->000000000019ddf0
  TOTAL:         0000000000000000->000000001f800000
  ENTRY ADDRESS: 0000000000100000
xc: info: PHYSICAL MEMORY ALLOCATION:
  4KB PAGES: 0x0000000000000200
  2MB PAGES: 0x00000000000000fb
  1GB PAGES: 0x0000000000000000
libxl: error: libxl_device.c:858:device_backend_callback: unable to
disconnect device with path /local/domain/0/backend/vbd/4/51744
libxl: error: libxl_create.c:933:domcreate_launch_dm: unable to add disk
devices
libxl: error: libxl_dm.c:1239:libxl__destroy_device_model: could not find
device-model's pid for dom 4
libxl: error: libxl.c:1429:libxl__destroy_domid:
libxl__destroy_device_model failed for 4


This error is very common in Xen 4.2.1-pre. I need to repeat create
command, sometimes few times to start DomU. This error don't let DomU to
restart. DomU is simple destroyed.

--e89a8fb1efa43c2e4504cadcbe90
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable


Parsing config from server2008.cfg
xc: info: VIRTUAL MEMORY =
ARRANGEMENT:
=A0 Loader: =A0 =A0 =A0 =A00000000000100000->0000=
00000019ddf0
=A0 TOTAL: =A0 =A0 =A0 =A0 0000000000000000->0000=
00001f800000



=A0 ENTRY ADDRESS: 0000000000100000
xc: info: PHYSICAL MEMOR=
Y ALLOCATION:
=A0 4KB PAGES: 0x0000000000000200
=A0 2MB=
 PAGES: 0x00000000000000fb
=A0 1GB PAGES: 0x0000000000000000


libxl: error: libxl_device.c:858:device_backend_callback: unable to disconn=
ect device with path /local/domain/0/backend/vbd/4/51744
libxl: e=
rror: libxl_create.c:933:domcreate_launch_dm: unable to add disk devices


libxl: error: libxl_dm.c:1239:libxl__destroy_device_model: could not f=
ind device-model's pid for dom 4
libxl: error: libxl.c:1429:l=
ibxl__destroy_domid: libxl__destroy_device_model failed for 4




This error is very common in Xen 4.2.1-pre. I=
 need to=A0repeat=A0create command, sometimes few times to start DomU. This=
 error don't let DomU to restart. DomU is simple destroyed.


--e89a8fb1efa43c2e4504cadcbe90--


--===============2651914620515418738==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
Xen-users mailing list
Xen-users@lists.xen.org
http://lists.xen.org/xen-users
--===============2651914620515418738==--


From xen-users-bounces@lists.xen.org Sat Sep 29 22:32:49 2012
Return-path: 
Envelope-to: archives@lists.xen.org
Delivery-date: Sat, 29 Sep 2012 22:32:49 +0000
Received: from localhost ([127.0.0.1] helo=lists.xen.org)
	by lists.xen.org with esmtp (Exim 4.72)
	(envelope-from )
	id 1TI5Z9-0006zf-S2; Sat, 29 Sep 2012 22:31:19 +0000
Received: from mail6.bemta4.messagelabs.com ([85.158.143.247])
	by lists.xen.org with esmtp (Exim 4.72)
	(envelope-from ) id 1TI5Z8-0006za-UW
	for xen-users@lists.xen.org; Sat, 29 Sep 2012 22:31:19 +0000
Received: from [85.158.143.99:23936] by server-2.bemta-4.messagelabs.com id
	5A/C0-06610-6B677605; Sat, 29 Sep 2012 22:31:18 +0000
X-Env-Sender: david.escott@gmail.com
X-Msg-Ref: server-9.tower-216.messagelabs.com!1348957875!32296397!1
X-Originating-IP: [74.125.83.45]
X-SpamReason: No, hits=0.3 required=7.0 tests=RCVD_BY_IP
X-StarScan-Received: 
X-StarScan-Version: 6.6.1.3; banners=-,-,-
X-VirusChecked: Checked
Received: (qmail 31658 invoked from network); 29 Sep 2012 22:31:15 -0000
Received: from mail-ee0-f45.google.com (HELO mail-ee0-f45.google.com)
	(74.125.83.45)
	by server-9.tower-216.messagelabs.com with RC4-SHA encrypted SMTP;
	29 Sep 2012 22:31:15 -0000
Received: by eekb47 with SMTP id b47so2014099eek.32
	for ; Sat, 29 Sep 2012 15:31:15 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;
	h=mime-version:sender:in-reply-to:references:from:date
	:x-google-sender-auth:message-id:subject:to:cc:content-type;
	bh=0vzi4taQX68dLQADBandqZlzUM6U976z0T6bkba3VEE=;
	b=loUF6ZlexJRobkKBNzARMjCw+35QR3lp+VbMcMlZxBgJ8Jevt89B/60eJ5ZljCVLQ/
	3cNJXSdvIi5ZFkMK2ha9KiSLpQ5tvJr2EkhJukxhTSL/yoDY88hBUdWvOEeb0YlXvxCk
	Eup4GoL1mVDvtG4tmaEw4EHJjPITua3JhUpVV8vLoSab/6XWYxOA6uqdpj7/zAjaX0AR
	iG5mttIlZkTwelL4LxTeI2czLHRs4W24B34hrF6ziMnZxOpbVq+ihZJSj4ALrPboh5id
	kQ/t/yjVZZv104I1o9CCIRo+lbLsSPcnMds085bKtCgjPJcMb2yUu/ebhWvPV8CPFtnd
	gUOA==
Received: by 10.14.201.73 with SMTP id a49mr13590046eeo.39.1348957875432; Sat,
	29 Sep 2012 15:31:15 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.14.100.129 with HTTP; Sat, 29 Sep 2012 15:30:55 -0700 (PDT)
In-Reply-To: 
References: 
	
	
	
From: David Escott 
Date: Sat, 29 Sep 2012 18:30:55 -0400
X-Google-Sender-Auth: kUaTuOo0eTR5YeztEmwnc3Lf53E
Message-ID: 
To: Casey DeLorme 
Cc: xen-users@lists.xen.org
Subject: Re: [Xen-users] PCI Passthrough
X-BeenThere: xen-users@lists.xen.org
X-Mailman-Version: 2.1.13
Precedence: list
List-Id: Xen user discussion 
List-Unsubscribe: ,
	
List-Post: 
List-Help: 
List-Subscribe: ,
	
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: xen-users-bounces@lists.xen.org
Errors-To: xen-users-bounces@lists.xen.org

Using the xm toolstack because xl is completely broken in fedora17.


xen version 4.1.3-4.fc17


On Sat, Sep 29, 2012 at 1:13 PM, Casey DeLorme  wrote:
> The settings for stdvga is related to the emulated graphics only, I don't
> believe it has anything to do with your passed devices.  Similarly, you can
> (or should be able to) omit the vga_passthrough=0 line, as it defaults to 0.
>
> Assuming you are passing to a Windows DomU (hence code 43), have you checked
> your xen log files (/var/logs/xen), also I would try running xl -vvv create
> with and without both adapters to see if that maybe yields a clue.
>
> Also, what version of Xen did you install, and which toolstack are you using
> (xm/xl)?
>
> On Sat, Sep 29, 2012 at 1:01 PM, David Escott
>  wrote:
>>
>> Went back to what was working last night and now have the 7850 working
>> but only when I pass both graphics adapters through to the domU.
>>
>> Hardware is
>>
>> MSI Z77A-G45
>> HD2600XT in PCI-Ex16 slot 1 (pci:0000:01:00:[0-1])
>> HD7850     in PCI-Ex16 slot 2 (pci:0000:02:00:[0-1])
>>
>> Dom0 is Fedora 17 with kernel 3.5.4-1 and the fedora version of xen.
>> vga_passthrough=0 is set
>> stdvga=1 is set
>> I stub out and pass both graphics adapters to domU, and then disable
>> the 2600XT at which point the 7850 works, and the fake VGA Graphics
>> adapter reports a code 43.
>>
>> If I don't pass both cards to domU then both they will report code 43.
>>
>> Not sure why this is, or what is going on. Looked around in the bios
>> for anything related to crossfire but couldn't find anything.
>>
>>
>> ----------------------------------------------------------------------------------------------------
>>
>> This puts a dent in my current plan which was to use the system to
>> support three different computers in three different rooms. Not sure
>> if anyone has seen anything like this/knows what might be going on.
>>
>>
>>
>>
>> On Sat, Sep 29, 2012 at 11:20 AM, Casey DeLorme 
>> wrote:
>> > Hello David,
>> >
>> > I have created a guide using Debian that can successfully reproduce VGA
>> > Passthrough with AMD Radeon cards, in particular I have used an AMD
>> > Radeon
>> > 6870.
>> >
>> > If you are more familiar with Fedora, I'm sure you can translate any
>> > Debain
>> > specific actions to Fedora equivalents.
>> >
>> > http://wiki.xen.org/wiki/Comprehensive_Xen_Debian_Wheezy_PCI_Passthrough_Tutorial
>> >
>> > I also posted a video walk-through:
>> > http://www.youtube.com/playlist?list=PLC70DC33D993CEB44&feature=view_all
>> >
>> > As for your current configuration, what version of Xen (4.0, 4.1.2,
>> > 4.2?),
>> > can you share your HVM Configuration, and are you getting any errors in
>> > your
>> > Xen log files or just inside of Windows?
>> >
>> >
>> > On Sat, Sep 29, 2012 at 11:10 AM, David Escott
>> >  wrote:
>> >>
>> >> I've been playing around with doing PCI passthrough of Radeon cards
>> >> and have had some success.
>> >>
>> >> Under Fedora 17 (stock everything) I was able to passthrough an older
>> >> RADEON 2600XT to a Windows7 domU.
>> >> However when I try the same with a new RADEON 7850 I get a "not enough
>> >> resources" error from the Windows guest.
>> >>
>> >> I'm not sure what the next steps are, it seems from blog postings and
>> >> howtos that people are just trying things at random, and I don't
>> >> understand what the debugging process is.
>> >>
>> >> Any advice on what the next steps are? Should I move to an OS that
>> >> will have a newer XEN or is there some configuration file I should be
>> >> editing?
>> >>
>> >> Thanks,
>> >> David
>> >>
>> >> _______________________________________________
>> >> Xen-users mailing list
>> >> Xen-users@lists.xen.org
>> >> http://lists.xen.org/xen-users
>> >
>> >
>>
>>
>>
>> --
>> David Wright Escott
>> A comathematician turns cotheorems into phi.
>
>



-- 
David Wright Escott
A comathematician turns cotheorems into phi.

_______________________________________________
Xen-users mailing list
Xen-users@lists.xen.org
http://lists.xen.org/xen-users

From xen-users-bounces@lists.xen.org Sat Sep 29 22:32:49 2012
Return-path: 
Envelope-to: archives@lists.xen.org
Delivery-date: Sat, 29 Sep 2012 22:32:49 +0000
Received: from localhost ([127.0.0.1] helo=lists.xen.org)
	by lists.xen.org with esmtp (Exim 4.72)
	(envelope-from )
	id 1TI5Z9-0006zf-S2; Sat, 29 Sep 2012 22:31:19 +0000
Received: from mail6.bemta4.messagelabs.com ([85.158.143.247])
	by lists.xen.org with esmtp (Exim 4.72)
	(envelope-from ) id 1TI5Z8-0006za-UW
	for xen-users@lists.xen.org; Sat, 29 Sep 2012 22:31:19 +0000
Received: from [85.158.143.99:23936] by server-2.bemta-4.messagelabs.com id
	5A/C0-06610-6B677605; Sat, 29 Sep 2012 22:31:18 +0000
X-Env-Sender: david.escott@gmail.com
X-Msg-Ref: server-9.tower-216.messagelabs.com!1348957875!32296397!1
X-Originating-IP: [74.125.83.45]
X-SpamReason: No, hits=0.3 required=7.0 tests=RCVD_BY_IP
X-StarScan-Received: 
X-StarScan-Version: 6.6.1.3; banners=-,-,-
X-VirusChecked: Checked
Received: (qmail 31658 invoked from network); 29 Sep 2012 22:31:15 -0000
Received: from mail-ee0-f45.google.com (HELO mail-ee0-f45.google.com)
	(74.125.83.45)
	by server-9.tower-216.messagelabs.com with RC4-SHA encrypted SMTP;
	29 Sep 2012 22:31:15 -0000
Received: by eekb47 with SMTP id b47so2014099eek.32
	for ; Sat, 29 Sep 2012 15:31:15 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;
	h=mime-version:sender:in-reply-to:references:from:date
	:x-google-sender-auth:message-id:subject:to:cc:content-type;
	bh=0vzi4taQX68dLQADBandqZlzUM6U976z0T6bkba3VEE=;
	b=loUF6ZlexJRobkKBNzARMjCw+35QR3lp+VbMcMlZxBgJ8Jevt89B/60eJ5ZljCVLQ/
	3cNJXSdvIi5ZFkMK2ha9KiSLpQ5tvJr2EkhJukxhTSL/yoDY88hBUdWvOEeb0YlXvxCk
	Eup4GoL1mVDvtG4tmaEw4EHJjPITua3JhUpVV8vLoSab/6XWYxOA6uqdpj7/zAjaX0AR
	iG5mttIlZkTwelL4LxTeI2czLHRs4W24B34hrF6ziMnZxOpbVq+ihZJSj4ALrPboh5id
	kQ/t/yjVZZv104I1o9CCIRo+lbLsSPcnMds085bKtCgjPJcMb2yUu/ebhWvPV8CPFtnd
	gUOA==
Received: by 10.14.201.73 with SMTP id a49mr13590046eeo.39.1348957875432; Sat,
	29 Sep 2012 15:31:15 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.14.100.129 with HTTP; Sat, 29 Sep 2012 15:30:55 -0700 (PDT)
In-Reply-To: 
References: 
	
	
	
From: David Escott 
Date: Sat, 29 Sep 2012 18:30:55 -0400
X-Google-Sender-Auth: kUaTuOo0eTR5YeztEmwnc3Lf53E
Message-ID: 
To: Casey DeLorme 
Cc: xen-users@lists.xen.org
Subject: Re: [Xen-users] PCI Passthrough
X-BeenThere: xen-users@lists.xen.org
X-Mailman-Version: 2.1.13
Precedence: list
List-Id: Xen user discussion 
List-Unsubscribe: ,
	
List-Post: 
List-Help: 
List-Subscribe: ,
	
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: xen-users-bounces@lists.xen.org
Errors-To: xen-users-bounces@lists.xen.org

Using the xm toolstack because xl is completely broken in fedora17.


xen version 4.1.3-4.fc17


On Sat, Sep 29, 2012 at 1:13 PM, Casey DeLorme  wrote:
> The settings for stdvga is related to the emulated graphics only, I don't
> believe it has anything to do with your passed devices.  Similarly, you can
> (or should be able to) omit the vga_passthrough=0 line, as it defaults to 0.
>
> Assuming you are passing to a Windows DomU (hence code 43), have you checked
> your xen log files (/var/logs/xen), also I would try running xl -vvv create
> with and without both adapters to see if that maybe yields a clue.
>
> Also, what version of Xen did you install, and which toolstack are you using
> (xm/xl)?
>
> On Sat, Sep 29, 2012 at 1:01 PM, David Escott
>  wrote:
>>
>> Went back to what was working last night and now have the 7850 working
>> but only when I pass both graphics adapters through to the domU.
>>
>> Hardware is
>>
>> MSI Z77A-G45
>> HD2600XT in PCI-Ex16 slot 1 (pci:0000:01:00:[0-1])
>> HD7850     in PCI-Ex16 slot 2 (pci:0000:02:00:[0-1])
>>
>> Dom0 is Fedora 17 with kernel 3.5.4-1 and the fedora version of xen.
>> vga_passthrough=0 is set
>> stdvga=1 is set
>> I stub out and pass both graphics adapters to domU, and then disable
>> the 2600XT at which point the 7850 works, and the fake VGA Graphics
>> adapter reports a code 43.
>>
>> If I don't pass both cards to domU then both they will report code 43.
>>
>> Not sure why this is, or what is going on. Looked around in the bios
>> for anything related to crossfire but couldn't find anything.
>>
>>
>> ----------------------------------------------------------------------------------------------------
>>
>> This puts a dent in my current plan which was to use the system to
>> support three different computers in three different rooms. Not sure
>> if anyone has seen anything like this/knows what might be going on.
>>
>>
>>
>>
>> On Sat, Sep 29, 2012 at 11:20 AM, Casey DeLorme 
>> wrote:
>> > Hello David,
>> >
>> > I have created a guide using Debian that can successfully reproduce VGA
>> > Passthrough with AMD Radeon cards, in particular I have used an AMD
>> > Radeon
>> > 6870.
>> >
>> > If you are more familiar with Fedora, I'm sure you can translate any
>> > Debain
>> > specific actions to Fedora equivalents.
>> >
>> > http://wiki.xen.org/wiki/Comprehensive_Xen_Debian_Wheezy_PCI_Passthrough_Tutorial
>> >
>> > I also posted a video walk-through:
>> > http://www.youtube.com/playlist?list=PLC70DC33D993CEB44&feature=view_all
>> >
>> > As for your current configuration, what version of Xen (4.0, 4.1.2,
>> > 4.2?),
>> > can you share your HVM Configuration, and are you getting any errors in
>> > your
>> > Xen log files or just inside of Windows?
>> >
>> >
>> > On Sat, Sep 29, 2012 at 11:10 AM, David Escott
>> >  wrote:
>> >>
>> >> I've been playing around with doing PCI passthrough of Radeon cards
>> >> and have had some success.
>> >>
>> >> Under Fedora 17 (stock everything) I was able to passthrough an older
>> >> RADEON 2600XT to a Windows7 domU.
>> >> However when I try the same with a new RADEON 7850 I get a "not enough
>> >> resources" error from the Windows guest.
>> >>
>> >> I'm not sure what the next steps are, it seems from blog postings and
>> >> howtos that people are just trying things at random, and I don't
>> >> understand what the debugging process is.
>> >>
>> >> Any advice on what the next steps are? Should I move to an OS that
>> >> will have a newer XEN or is there some configuration file I should be
>> >> editing?
>> >>
>> >> Thanks,
>> >> David
>> >>
>> >> _______________________________________________
>> >> Xen-users mailing list
>> >> Xen-users@lists.xen.org
>> >> http://lists.xen.org/xen-users
>> >
>> >
>>
>>
>>
>> --
>> David Wright Escott
>> A comathematician turns cotheorems into phi.
>
>



-- 
David Wright Escott
A comathematician turns cotheorems into phi.

_______________________________________________
Xen-users mailing list
Xen-users@lists.xen.org
http://lists.xen.org/xen-users

From xen-users-bounces@lists.xen.org Sat Sep 29 22:42:06 2012
Return-path: 
Envelope-to: archives@lists.xen.org
Delivery-date: Sat, 29 Sep 2012 22:42:06 +0000
Received: from localhost ([127.0.0.1] helo=lists.xen.org)
	by lists.xen.org with esmtp (Exim 4.72)
	(envelope-from )
	id 1TI5ia-0007Ey-6c; Sat, 29 Sep 2012 22:41:04 +0000
Received: from mail27.messagelabs.com ([193.109.254.147])
	by lists.xen.org with esmtp (Exim 4.72)
	(envelope-from ) id 1TI5iX-0007Es-TW
	for xen-users@lists.xen.org; Sat, 29 Sep 2012 22:41:02 +0000
X-Env-Sender: kavefish@gmail.com
X-Msg-Ref: server-4.tower-27.messagelabs.com!1348958453!12257462!1
X-Originating-IP: [209.85.216.173]
X-SpamReason: No, hits=0.3 required=7.0 tests=ML_RADAR_SPEW_LINKS_14,
	RCVD_BY_IP,spamassassin: 
X-StarScan-Received: 
X-StarScan-Version: 6.6.1.3; banners=-,-,-
X-VirusChecked: Checked
Received: (qmail 30731 invoked from network); 29 Sep 2012 22:40:54 -0000
Received: from mail-qc0-f173.google.com (HELO mail-qc0-f173.google.com)
	(209.85.216.173)
	by server-4.tower-27.messagelabs.com with RC4-SHA encrypted SMTP;
	29 Sep 2012 22:40:54 -0000
Received: by qcab12 with SMTP id b12so4083965qca.32
	for ; Sat, 29 Sep 2012 15:40:52 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;
	h=message-id:date:from:user-agent:mime-version:to:subject:references
	:in-reply-to:x-enigmail-version:content-type
	:content-transfer-encoding;
	bh=SHTYTzZHGIMQWztFA+GEIPTRY9gE5+86JGaO8cE7qoY=;
	b=It/sUNqF1ce3Od2wGC6RrbtZC2GmSfk8abIRIpmk2yLApvOsJRJnZ2z/EITdESulD4
	cbgkpcF6rX56Ksepph7dVD3gai88Hwjua+tADkEtx9HEbwmUegAl6fCqX+zLES7JetL6
	XIhN0pDe6p4Nekrhyodv76tLHvtayKEf/9cgcFw8KRnxX5VzvoL1MUZqWjdThyEsl+IB
	hYsMLJ1da0AgH1imwlRBpmTD4GqVEo9cDZ4Ywa1pCgLmbO61YX0v0VNXAZqkQtNQNX/l
	CFht/j5Hh38azqmzFCekG6c2OBwpmyXHuL1qkBaQ9Vam0ADkxbzqOLB5X3Epq/nNn41G
	vC1w==
Received: by 10.229.137.140 with SMTP id w12mr7425539qct.8.1348958452858;
	Sat, 29 Sep 2012 15:40:52 -0700 (PDT)
Received: from spin.local (pool-96-244-79-113.bltmmd.fios.verizon.net.
	[96.244.79.113])
	by mx.google.com with ESMTPS id em3sm18241403qab.5.2012.09.29.15.40.50
	(version=SSLv3 cipher=OTHER); Sat, 29 Sep 2012 15:40:52 -0700 (PDT)
Message-ID: <506778F1.8040606@gmail.com>
Date: Sat, 29 Sep 2012 18:40:49 -0400
From: Chris 
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.6;
	rv:15.0) Gecko/20120907 Thunderbird/15.0.1
MIME-Version: 1.0
To: xen-users@lists.xen.org
References: 
	
	
	
	
In-Reply-To: 
X-Enigmail-Version: 1.4.4
Subject: Re: [Xen-users] PCI Passthrough
X-BeenThere: xen-users@lists.xen.org
X-Mailman-Version: 2.1.13
Precedence: list
List-Id: Xen user discussion 
List-Unsubscribe: ,
	
List-Post: 
List-Help: 
List-Subscribe: ,
	
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: xen-users-bounces@lists.xen.org
Errors-To: xen-users-bounces@lists.xen.org

On 9/29/12 6:30 PM, David Escott wrote:
> Using the xm toolstack because xl is completely broken in fedora17.

FYI - I'm also stuck using the old xm tool stack on Fedora 17. Actually
newer Fedora kernels also cause passthru to fail. :/

_______________________________________________
Xen-users mailing list
Xen-users@lists.xen.org
http://lists.xen.org/xen-users

From xen-users-bounces@lists.xen.org Sat Sep 29 22:42:06 2012
Return-path: 
Envelope-to: archives@lists.xen.org
Delivery-date: Sat, 29 Sep 2012 22:42:06 +0000
Received: from localhost ([127.0.0.1] helo=lists.xen.org)
	by lists.xen.org with esmtp (Exim 4.72)
	(envelope-from )
	id 1TI5ia-0007Ey-6c; Sat, 29 Sep 2012 22:41:04 +0000
Received: from mail27.messagelabs.com ([193.109.254.147])
	by lists.xen.org with esmtp (Exim 4.72)
	(envelope-from ) id 1TI5iX-0007Es-TW
	for xen-users@lists.xen.org; Sat, 29 Sep 2012 22:41:02 +0000
X-Env-Sender: kavefish@gmail.com
X-Msg-Ref: server-4.tower-27.messagelabs.com!1348958453!12257462!1
X-Originating-IP: [209.85.216.173]
X-SpamReason: No, hits=0.3 required=7.0 tests=ML_RADAR_SPEW_LINKS_14,
	RCVD_BY_IP,spamassassin: 
X-StarScan-Received: 
X-StarScan-Version: 6.6.1.3; banners=-,-,-
X-VirusChecked: Checked
Received: (qmail 30731 invoked from network); 29 Sep 2012 22:40:54 -0000
Received: from mail-qc0-f173.google.com (HELO mail-qc0-f173.google.com)
	(209.85.216.173)
	by server-4.tower-27.messagelabs.com with RC4-SHA encrypted SMTP;
	29 Sep 2012 22:40:54 -0000
Received: by qcab12 with SMTP id b12so4083965qca.32
	for ; Sat, 29 Sep 2012 15:40:52 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;
	h=message-id:date:from:user-agent:mime-version:to:subject:references
	:in-reply-to:x-enigmail-version:content-type
	:content-transfer-encoding;
	bh=SHTYTzZHGIMQWztFA+GEIPTRY9gE5+86JGaO8cE7qoY=;
	b=It/sUNqF1ce3Od2wGC6RrbtZC2GmSfk8abIRIpmk2yLApvOsJRJnZ2z/EITdESulD4
	cbgkpcF6rX56Ksepph7dVD3gai88Hwjua+tADkEtx9HEbwmUegAl6fCqX+zLES7JetL6
	XIhN0pDe6p4Nekrhyodv76tLHvtayKEf/9cgcFw8KRnxX5VzvoL1MUZqWjdThyEsl+IB
	hYsMLJ1da0AgH1imwlRBpmTD4GqVEo9cDZ4Ywa1pCgLmbO61YX0v0VNXAZqkQtNQNX/l
	CFht/j5Hh38azqmzFCekG6c2OBwpmyXHuL1qkBaQ9Vam0ADkxbzqOLB5X3Epq/nNn41G
	vC1w==
Received: by 10.229.137.140 with SMTP id w12mr7425539qct.8.1348958452858;
	Sat, 29 Sep 2012 15:40:52 -0700 (PDT)
Received: from spin.local (pool-96-244-79-113.bltmmd.fios.verizon.net.
	[96.244.79.113])
	by mx.google.com with ESMTPS id em3sm18241403qab.5.2012.09.29.15.40.50
	(version=SSLv3 cipher=OTHER); Sat, 29 Sep 2012 15:40:52 -0700 (PDT)
Message-ID: <506778F1.8040606@gmail.com>
Date: Sat, 29 Sep 2012 18:40:49 -0400
From: Chris 
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.6;
	rv:15.0) Gecko/20120907 Thunderbird/15.0.1
MIME-Version: 1.0
To: xen-users@lists.xen.org
References: 
	
	
	
	
In-Reply-To: 
X-Enigmail-Version: 1.4.4
Subject: Re: [Xen-users] PCI Passthrough
X-BeenThere: xen-users@lists.xen.org
X-Mailman-Version: 2.1.13
Precedence: list
List-Id: Xen user discussion 
List-Unsubscribe: ,
	
List-Post: 
List-Help: 
List-Subscribe: ,
	
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: xen-users-bounces@lists.xen.org
Errors-To: xen-users-bounces@lists.xen.org

On 9/29/12 6:30 PM, David Escott wrote:
> Using the xm toolstack because xl is completely broken in fedora17.

FYI - I'm also stuck using the old xm tool stack on Fedora 17. Actually
newer Fedora kernels also cause passthru to fail. :/

_______________________________________________
Xen-users mailing list
Xen-users@lists.xen.org
http://lists.xen.org/xen-users

From xen-users-bounces@lists.xen.org Sun Sep 30 06:21:29 2012
Return-path: 
Envelope-to: archives@lists.xen.org
Delivery-date: Sun, 30 Sep 2012 06:21:29 +0000
Received: from localhost ([127.0.0.1] helo=lists.xen.org)
	by lists.xen.org with esmtp (Exim 4.72)
	(envelope-from )
	id 1TICsa-0005K1-9q; Sun, 30 Sep 2012 06:19:52 +0000
Received: from mail6.bemta3.messagelabs.com ([195.245.230.39])
	by lists.xen.org with esmtp (Exim 4.72)
	(envelope-from ) id 1TICsY-0005Jw-FV
	for xen-users@lists.xen.org; Sun, 30 Sep 2012 06:19:50 +0000
Received: from [85.158.138.51:52092] by server-10.bemta-3.messagelabs.com id
	8F/5D-02525-584E7605; Sun, 30 Sep 2012 06:19:49 +0000
X-Env-Sender: Rudi@softdux.com
X-Msg-Ref: server-10.tower-174.messagelabs.com!1348985988!24887565!1
X-Originating-IP: [64.191.118.125]
X-SpamReason: No, hits=0.3 required=7.0 tests=RCVD_BY_IP
X-StarScan-Received: 
X-StarScan-Version: 6.6.1.3; banners=-,-,-
X-VirusChecked: Checked
Received: (qmail 27598 invoked from network); 30 Sep 2012 06:19:48 -0000
Received: from mercury.securehosting.co.za (HELO mercury.securehosting.co.za)
	(64.191.118.125)
	by server-10.tower-174.messagelabs.com with DHE-RSA-AES256-SHA
	encrypted SMTP; 30 Sep 2012 06:19:48 -0000
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=softdux.com;
	s=default; 
	h=Content-Type:To:Subject:Message-ID:Date:From:Reply-To:MIME-Version;
	bh=IZgV+uls3IBR4IVBW0vpyhK6YXwz1yW1RtLNf8qOhaQ=; 
	b=Gvwf8AIWeX0IdESDynXTPk7mH9bceaScDzb4iMmcCfHsvurTAXrJrup/hwz9IGNYk3DaiWvvyafIUHVKC/kgEY8IUmKgzoMDTMu3jEx176uorss+p+sEmI1LG5wSLHeg;
Received: from localhost ([127.0.0.1]:56391 helo=mercury.securehosting.co.za)
	by mercury.securehosting.co.za with esmtpa (Exim 4.77)
	(envelope-from ) id 1TID1y-000hGE-7n
	for xen-users@lists.xen.org; Sun, 30 Sep 2012 08:29:34 +0200
Received: from mail-vc0-f173.google.com ([209.85.220.173]
	helo=mail-vc0-f173.google.com)
	by mercury.securehosting.co.za with ESMTP (ASSP 1.9); 30 Sep 2012
	08:29:33 +0200
Received: by vcbfl15 with SMTP id fl15so5775903vcb.32
	for ; Sat, 29 Sep 2012 23:19:47 -0700 (PDT)
Received: by 10.52.19.243 with SMTP id i19mr5263148vde.69.1348985987158; Sat,
	29 Sep 2012 23:19:47 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.58.225.228 with HTTP; Sat, 29 Sep 2012 23:19:17 -0700 (PDT)
From: Rudi Ahlers 
Date: Sun, 30 Sep 2012 08:19:17 +0200
Message-ID: 
To: xen-users@lists.xen.org
X-AntiAbuse: This header was added to track abuse,
	please include it with any abuse report
X-AntiAbuse: Primary Hostname - mercury.securehosting.co.za
X-AntiAbuse: Original Domain - lists.xen.org
X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12]
X-AntiAbuse: Sender Address Domain - softdux.com
X-Source: 
X-Source-Args: 
X-Source-Dir: 
Subject: [Xen-users] XEN on Scientific Linux 6
X-BeenThere: xen-users@lists.xen.org
X-Mailman-Version: 2.1.13
Precedence: list
Reply-To: rudi@softdux.com
List-Id: Xen user discussion 
List-Unsubscribe: ,
	
List-Post: 
List-Help: 
List-Subscribe: ,
	
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: xen-users-bounces@lists.xen.org
Errors-To: xen-users-bounces@lists.xen.org

Hi Everyone,

I want to use XEN on Scientific Linux 6 and found the following
article which describe how to set it up:
http://wiki.xensource.com/xenwiki/RHEL6Xen4Tutorial

Is anyone using XEN on Scientific Linux 6 or even CentOS 6 for that
matter in a production environment? How's it working?
Have you run into any problems or pitfalls?

And, w.r.t to the wiki article, how would I update XEN if it's
installed like this?

-- 
Kind Regards
Rudi Ahlers
SoftDux

Website: http://www.SoftDux.com
Technical Blog: http://Blog.SoftDux.com
Cell: 082 554 7532
Fax: 086 268 8492

_______________________________________________
Xen-users mailing list
Xen-users@lists.xen.org
http://lists.xen.org/xen-users

From xen-users-bounces@lists.xen.org Sun Sep 30 06:21:29 2012
Return-path: 
Envelope-to: archives@lists.xen.org
Delivery-date: Sun, 30 Sep 2012 06:21:29 +0000
Received: from localhost ([127.0.0.1] helo=lists.xen.org)
	by lists.xen.org with esmtp (Exim 4.72)
	(envelope-from )
	id 1TICsa-0005K1-9q; Sun, 30 Sep 2012 06:19:52 +0000
Received: from mail6.bemta3.messagelabs.com ([195.245.230.39])
	by lists.xen.org with esmtp (Exim 4.72)
	(envelope-from ) id 1TICsY-0005Jw-FV
	for xen-users@lists.xen.org; Sun, 30 Sep 2012 06:19:50 +0000
Received: from [85.158.138.51:52092] by server-10.bemta-3.messagelabs.com id
	8F/5D-02525-584E7605; Sun, 30 Sep 2012 06:19:49 +0000
X-Env-Sender: Rudi@softdux.com
X-Msg-Ref: server-10.tower-174.messagelabs.com!1348985988!24887565!1
X-Originating-IP: [64.191.118.125]
X-SpamReason: No, hits=0.3 required=7.0 tests=RCVD_BY_IP
X-StarScan-Received: 
X-StarScan-Version: 6.6.1.3; banners=-,-,-
X-VirusChecked: Checked
Received: (qmail 27598 invoked from network); 30 Sep 2012 06:19:48 -0000
Received: from mercury.securehosting.co.za (HELO mercury.securehosting.co.za)
	(64.191.118.125)
	by server-10.tower-174.messagelabs.com with DHE-RSA-AES256-SHA
	encrypted SMTP; 30 Sep 2012 06:19:48 -0000
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=softdux.com;
	s=default; 
	h=Content-Type:To:Subject:Message-ID:Date:From:Reply-To:MIME-Version;
	bh=IZgV+uls3IBR4IVBW0vpyhK6YXwz1yW1RtLNf8qOhaQ=; 
	b=Gvwf8AIWeX0IdESDynXTPk7mH9bceaScDzb4iMmcCfHsvurTAXrJrup/hwz9IGNYk3DaiWvvyafIUHVKC/kgEY8IUmKgzoMDTMu3jEx176uorss+p+sEmI1LG5wSLHeg;
Received: from localhost ([127.0.0.1]:56391 helo=mercury.securehosting.co.za)
	by mercury.securehosting.co.za with esmtpa (Exim 4.77)
	(envelope-from ) id 1TID1y-000hGE-7n
	for xen-users@lists.xen.org; Sun, 30 Sep 2012 08:29:34 +0200
Received: from mail-vc0-f173.google.com ([209.85.220.173]
	helo=mail-vc0-f173.google.com)
	by mercury.securehosting.co.za with ESMTP (ASSP 1.9); 30 Sep 2012
	08:29:33 +0200
Received: by vcbfl15 with SMTP id fl15so5775903vcb.32
	for ; Sat, 29 Sep 2012 23:19:47 -0700 (PDT)
Received: by 10.52.19.243 with SMTP id i19mr5263148vde.69.1348985987158; Sat,
	29 Sep 2012 23:19:47 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.58.225.228 with HTTP; Sat, 29 Sep 2012 23:19:17 -0700 (PDT)
From: Rudi Ahlers 
Date: Sun, 30 Sep 2012 08:19:17 +0200
Message-ID: 
To: xen-users@lists.xen.org
X-AntiAbuse: This header was added to track abuse,
	please include it with any abuse report
X-AntiAbuse: Primary Hostname - mercury.securehosting.co.za
X-AntiAbuse: Original Domain - lists.xen.org
X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12]
X-AntiAbuse: Sender Address Domain - softdux.com
X-Source: 
X-Source-Args: 
X-Source-Dir: 
Subject: [Xen-users] XEN on Scientific Linux 6
X-BeenThere: xen-users@lists.xen.org
X-Mailman-Version: 2.1.13
Precedence: list
Reply-To: rudi@softdux.com
List-Id: Xen user discussion 
List-Unsubscribe: ,
	
List-Post: 
List-Help: 
List-Subscribe: ,
	
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: xen-users-bounces@lists.xen.org
Errors-To: xen-users-bounces@lists.xen.org

Hi Everyone,

I want to use XEN on Scientific Linux 6 and found the following
article which describe how to set it up:
http://wiki.xensource.com/xenwiki/RHEL6Xen4Tutorial

Is anyone using XEN on Scientific Linux 6 or even CentOS 6 for that
matter in a production environment? How's it working?
Have you run into any problems or pitfalls?

And, w.r.t to the wiki article, how would I update XEN if it's
installed like this?

-- 
Kind Regards
Rudi Ahlers
SoftDux

Website: http://www.SoftDux.com
Technical Blog: http://Blog.SoftDux.com
Cell: 082 554 7532
Fax: 086 268 8492

_______________________________________________
Xen-users mailing list
Xen-users@lists.xen.org
http://lists.xen.org/xen-users

From xen-users-bounces@lists.xen.org Sun Sep 30 12:30:16 2012
Return-path: 
Envelope-to: archives@lists.xen.org
Delivery-date: Sun, 30 Sep 2012 12:30:16 +0000
Received: from localhost ([127.0.0.1] helo=lists.xen.org)
	by lists.xen.org with esmtp (Exim 4.72)
	(envelope-from )
	id 1TIIdb-0007XY-8z; Sun, 30 Sep 2012 12:28:47 +0000
Received: from mail6.bemta5.messagelabs.com ([195.245.231.135])
	by lists.xen.org with esmtp (Exim 4.72)
	(envelope-from ) id 1TIIdZ-0007XQ-FP
	for xen-users@lists.xen.org; Sun, 30 Sep 2012 12:28:46 +0000
Received: from [85.158.139.211:31843] by server-4.bemta-5.messagelabs.com id
	7C/E9-20767-CFA38605; Sun, 30 Sep 2012 12:28:44 +0000
X-Env-Sender: damas.makweba@ternet.or.tz
X-Msg-Ref: server-4.tower-206.messagelabs.com!1349008115!20510953!1
X-Originating-IP: [209.85.220.173]
X-SpamReason: No, hits=0.4 required=7.0 tests=HTML_30_40,HTML_MESSAGE,
	ML_RADAR_SPEW_LINKS_8,RCVD_BY_IP,spamassassin: ,async_handler: 
	YXN5bmNfZGVsYXk6IDcwNDQ5MDcgKHRpbWVvdXQp\n
X-StarScan-Received: 
X-StarScan-Version: 6.6.1.3; banners=-,-,-
X-VirusChecked: Checked
Received: (qmail 2120 invoked from network); 30 Sep 2012 12:28:36 -0000
Received: from mail-vc0-f173.google.com (HELO mail-vc0-f173.google.com)
	(209.85.220.173)
	by server-4.tower-206.messagelabs.com with RC4-SHA encrypted SMTP;
	30 Sep 2012 12:28:36 -0000
Received: by vcbfl15 with SMTP id fl15so5923404vcb.32
	for ; Sun, 30 Sep 2012 05:28:34 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
	d=google.com; s=20120113;
	h=mime-version:x-originating-ip:date:message-id:subject:from:to
	:content-type:x-gm-message-state;
	bh=Z31Ib8mX2VzBiaTmW1whHByPb/KMh7X6W78P2jIEq/o=;
	b=DMJP0NgxoC+kN61/LjUXydLkvu4oTIcx7MYb0sS4j1lR9XWU2XM45i41UFsy9yjz5c
	3FPe/88vHccbdW4AjeX3OT8RZ8F5Rq/tbjL2EZUYQEAG/XL3VRJ889fQ4Xby6kmPQcng
	FR4S/PEe56j34XJjbhO/2Jme+EoW9AJELhQVuq9gU8X/kT5lnyx29Gp9/9JfvWX8ZSej
	semy7h+QPzm9e3GqADDjFsMv0DFuaP1GyovF6FJFCdeBqqP9Rtp1w9N8DImWSmFRdBfP
	f8Ja5gPltJk2s/rRIBFlbQ0TPcp6l0cNf1dhe3NVMKfcrOfpD7u8MGxpqpXZ8k2uP344
	quyw==
MIME-Version: 1.0
Received: by 10.220.149.142 with SMTP id t14mr6786285vcv.46.1349008114659;
	Sun, 30 Sep 2012 05:28:34 -0700 (PDT)
Received: by 10.220.211.12 with HTTP; Sun, 30 Sep 2012 05:28:34 -0700 (PDT)
X-Originating-IP: [41.93.32.9]
Date: Sun, 30 Sep 2012 15:28:34 +0300
Message-ID: 
From: "Damas A.Makweba" 
To: xen-users@lists.xen.org
Content-Type: multipart/mixed; boundary=f46d043c822079331f04caea6d93
X-Gm-Message-State: ALoCoQkvXU2ZfrzvxShZsX7MFEyowJ15fWfFrOf1GiZNCH/keq6z5x5zArD83UY19MkY4tPWZSGp
Subject: [Xen-users] Networking
X-BeenThere: xen-users@lists.xen.org
X-Mailman-Version: 2.1.13
Precedence: list
List-Id: Xen user discussion 
List-Unsubscribe: ,
	
List-Post: 
List-Help: 
List-Subscribe: ,
	
Sender: xen-users-bounces@lists.xen.org
Errors-To: xen-users-bounces@lists.xen.org

--f46d043c822079331f04caea6d93
Content-Type: multipart/alternative; boundary=f46d043c822079331604caea6d91

--f46d043c822079331604caea6d91
Content-Type: text/plain; charset=ISO-8859-1

Greetings all,

I need help with xen networking, I am not good to set up xen.

Please, pass through the xen.pdf file attached in which i tried to let you
know how my settings should be.

I have a server, installed and configured with Ubuntu 12.04LTS server and
Xen 4.0, it contains 6doms ie VMs, i need to set up doms with static IP
rather than dhcp, I need to connect the server direct to cisco router which
is the 7600 series switch ports, please help me.

Regards,

-- 
Damas A.M
**
Network Engineer
Tanzania Education & Research Network


*Mob: +255 (0) 714/ 754/ 784 - 46 46 78*

--f46d043c822079331604caea6d91
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

Greetings all,

I need help with xen networking, I am not good to set=
 up xen.

Please, pass through the xen.pdf file attached in which i t=
ried to let you know how my settings should be.

I have a server, ins=
talled and configured with Ubuntu 12.04LTS server and Xen 4.0, it contains =
6doms ie VMs, i need to set up doms with static IP rather than dhcp, I need=
 to connect the server direct to cisco router which is the 7600 series swit=
ch ports, please help me.


Regards,

-- 
Damas A.M
Network Engineer
<=
div>Tanzania Educatio=
n & Research Network 



Mob: +255 (0) 714/ 754/ 784 - 46 46 78



--f46d043c822079331604caea6d91--
--f46d043c822079331f04caea6d93
Content-Type: application/pdf; name="xen.pdf"
Content-Disposition: attachment; filename="xen.pdf"
Content-Transfer-Encoding: base64
X-Attachment-Id: f_h7q4gnho0

JVBERi0xLjENCiXi48/TAAAADQo1IDAgb2JqDQo8PA0KL0xlbmd0aCA2IDAgUg0KPj4NCnN0cmVh
bQ0KcQ0KMC41MDIgMC41MDIgMC41MDIgcmcNCjAuMDAwIDAuMDAwIDAuMDAwIFJHDQowLjAwMCB3
DQpbIF0gMCBkDQoxIEoNCjEgag0KNTYuNjQwIDM0MC4wODAgbQ0KMjYuMDQwIDMwNC42ODAgbA0K
MTc5LjA0MCAzMDQuNjgwIGwNCjE0OC41NjAgMzQwLjA4MCBsDQo1Ni42NDAgMzQwLjA4MCBsDQpi
Kg0KMC4wMDAgMC4wMDAgMC4wMDAgcmcNCjAuMDAwIDAuMDAwIDAuMDAwIFJHDQowLjAwMCB3DQpb
IF0gMCBkDQoxIEoNCjEgag0KNTYuNjQwIDM0MC4wODAgbQ0KMjYuMDQwIDMwNC41NjAgbA0KMTc5
LjA0MCAzMDQuNTYwIGwNCjE0OC41NjAgMzQwLjA4MCBsDQo1Ni42NDAgMzQwLjA4MCBsDQo1Ni43
NjAgMzM5Ljg0MCBsDQoxNDguNDQwIDMzOS44NDAgbA0KMTc4LjQ0MCAzMDQuOTIwIGwNCjI2Ljc2
MCAzMDQuOTIwIGwNCjU2Ljc2MCAzMzkuODQwIGwNCjU2LjY0MCAzNDAuMDgwIGwNCmYqDQowLjYy
NyAwLjYyNyAwLjY0MyByZw0KMC4wMDAgMC4wMDAgMC4wMDAgUkcNCjAuMjQwIHcNClsgXSAwIGQN
CjEgSg0KMSBqDQozMC4wMDAgMzA5LjM2MCBtDQozMC4zNjAgMzA5LjM2MCBsDQozMC43MjAgMzA5
LjM2MCBsDQozMS4wODAgMzA5LjM2MCBsDQozMS40NDAgMzA5LjM2MCBsDQozMS45MjAgMzA5LjI0
MCBsDQozMi4yODAgMzA5LjI0MCBsDQozMi42NDAgMzA5LjEyMCBsDQozMy4wMDAgMzA5LjEyMCBs
DQozMy4zNjAgMzA5LjEyMCBsDQozMy43MjAgMzA5LjEyMCBsDQozNC4wODAgMzA5LjAwMCBsDQoz
NC41NjAgMzA5LjAwMCBsDQozNC45MjAgMzA5LjAwMCBsDQozNS4yODAgMzA4Ljg4MCBsDQozNS42
NDAgMzA4Ljg4MCBsDQozNi4xMjAgMzA4Ljg4MCBsDQozNi40ODAgMzA4Ljg4MCBsDQozNi44NDAg
MzA4Ljc2MCBsDQozNy4zMjAgMzA4Ljc2MCBsDQozNy42ODAgMzA4Ljc2MCBsDQozOC4wNDAgMzA4
LjY0MCBsDQozOC41MjAgMzA4LjY0MCBsDQozOC44ODAgMzA4LjY0MCBsDQozOS4zNjAgMzA4LjY0
MCBsDQozOS43MjAgMzA4LjUyMCBsDQo0MC4yMDAgMzA4LjUyMCBsDQo0MC41NjAgMzA4LjUyMCBs
DQo0MS4wNDAgMzA4LjQwMCBsDQo0MS41MjAgMzA4LjQwMCBsDQo0MS44ODAgMzA4LjQwMCBsDQo0
Mi4zNjAgMzA4LjQwMCBsDQo0Mi43MjAgMzA4LjI4MCBsDQo0My4yMDAgMzA4LjI4MCBsDQo0My42
ODAgMzA4LjE2MCBsDQo0NC4xNjAgMzA4LjE2MCBsDQo0NC41MjAgMzA4LjE2MCBsDQo0NS4wMDAg
MzA4LjA0MCBsDQo0NS40ODAgMzA4LjA0MCBsDQo0NS45NjAgMzA4LjA0MCBsDQo0Ni40NDAgMzA4
LjA0MCBsDQo0Ni45MjAgMzA3LjkyMCBsDQo0Ny40MDAgMzA3LjkyMCBsDQo0Ny44ODAgMzA3Ljky
MCBsDQo0OC4zNjAgMzA3LjgwMCBsDQo0OC44NDAgMzA3LjgwMCBsDQo0OS4zMjAgMzA3LjgwMCBs
DQo0OS44MDAgMzA3LjgwMCBsDQo1MC4yODAgMzA3LjY4MCBsDQo1MC43NjAgMzA3LjY4MCBsDQo1
MS4zNjAgMzA3LjY4MCBsDQo1MS44NDAgMzA3LjU2MCBsDQo1Mi40NDAgMzA3LjU2MCBsDQo1Mi45
MjAgMzA3LjU2MCBsDQo1My41MjAgMzA3LjU2MCBsDQo1NC4wMDAgMzA3LjQ0MCBsDQo1NC40ODAg
MzA3LjQ0MCBsDQo1NS4wODAgMzA3LjMyMCBsDQo1NS42ODAgMzA3LjMyMCBsDQo1Ni4xNjAgMzA3
LjMyMCBsDQo1Ni43NjAgMzA3LjMyMCBsDQo1Ny4zNjAgMzA3LjMyMCBsDQo1Ny45NjAgMzA3LjIw
MCBsDQo1OC41NjAgMzA3LjIwMCBsDQo1OS4xNjAgMzA3LjA4MCBsDQo1OS43NjAgMzA3LjA4MCBs
DQo2MC4zNjAgMzA3LjA4MCBsDQo2MS4wODAgMzA3LjA4MCBsDQo2MS42ODAgMzA2Ljk2MCBsDQo2
Mi40MDAgMzA2Ljk2MCBsDQo2My4wMDAgMzA2Ljk2MCBsDQo2My43MjAgMzA2Ljg0MCBsDQo2NC40
NDAgMzA2Ljg0MCBsDQo2NS4wNDAgMzA2Ljg0MCBsDQo2NS43NjAgMzA2Ljg0MCBsDQo2Ni40ODAg
MzA2LjcyMCBsDQo2Ny4zMjAgMzA2LjcyMCBsDQo2OC4wNDAgMzA2LjcyMCBsDQo2OC44ODAgMzA2
LjYwMCBsDQo2OS42MDAgMzA2LjYwMCBsDQo3MC40NDAgMzA2LjYwMCBsDQo3MS4yODAgMzA2LjYw
MCBsDQo3Mi4xMjAgMzA2LjQ4MCBsDQo3My4wODAgMzA2LjQ4MCBsDQo3My45MjAgMzA2LjQ4MCBs
DQo3NC44ODAgMzA2LjM2MCBsDQo3NS45NjAgMzA2LjM2MCBsDQo3Ni45MjAgMzA2LjM2MCBsDQo3
OC4wMDAgMzA2LjM2MCBsDQo3OS4wODAgMzA2LjI0MCBsDQo4MC4yODAgMzA2LjI0MCBsDQo4MS40
ODAgMzA2LjEyMCBsDQo4Mi45MjAgMzA2LjEyMCBsDQo4NC4yNDAgMzA2LjEyMCBsDQo4NS44MDAg
MzA2LjEyMCBsDQo4Ny42MDAgMzA2LjAwMCBsDQo4OS41MjAgMzA2LjAwMCBsDQo5MS44MDAgMzA2
LjAwMCBsDQo5NC44MDAgMzA1Ljg4MCBsDQoxMDIuMDAwIDMwNS44ODAgbA0KMTA5LjQ0MCAzMDUu
ODgwIGwNCjExMi40NDAgMzA2LjAwMCBsDQoxMTQuODQwIDMwNi4wMDAgbA0KMTE2Ljc2MCAzMDYu
MTIwIGwNCjExOC40NDAgMzA2LjEyMCBsDQoxMjAuMTIwIDMwNi4xMjAgbA0KMTIxLjU2MCAzMDYu
MTIwIGwNCjEyMi44ODAgMzA2LjI0MCBsDQoxMjQuMjAwIDMwNi4yNDAgbA0KMTI1LjQwMCAzMDYu
MjQwIGwNCjEyNi40ODAgMzA2LjM2MCBsDQoxMjcuNTYwIDMwNi4zNjAgbA0KMTI4LjY0MCAzMDYu
MzYwIGwNCjEyOS42MDAgMzA2LjM2MCBsDQoxMzAuNTYwIDMwNi40ODAgbA0KMTMxLjUyMCAzMDYu
NDgwIGwNCjEzMi40ODAgMzA2LjYwMCBsDQoxMzMuMzIwIDMwNi42MDAgbA0KMTM0LjE2MCAzMDYu
NjAwIGwNCjEzNS4wMDAgMzA2LjYwMCBsDQoxMzUuODQwIDMwNi43MjAgbA0KMTM2LjY4MCAzMDYu
NzIwIGwNCjEzNy40MDAgMzA2LjcyMCBsDQoxMzguMjQwIDMwNi44NDAgbA0KMTM4Ljk2MCAzMDYu
ODQwIGwNCjEzOS42ODAgMzA2Ljg0MCBsDQoxNDAuNDAwIDMwNi44NDAgbA0KMTQxLjEyMCAzMDYu
OTYwIGwNCjE0MS43MjAgMzA2Ljk2MCBsDQoxNDIuNDQwIDMwNy4wODAgbA0KMTQzLjE2MCAzMDcu
MDgwIGwNCjE0My43NjAgMzA3LjA4MCBsDQoxNDQuNDgwIDMwNy4wODAgbA0KMTQ1LjA4MCAzMDcu
MjAwIGwNCjE0NS42ODAgMzA3LjIwMCBsDQoxNDYuMjgwIDMwNy4yMDAgbA0KMTQ2Ljg4MCAzMDcu
MzIwIGwNCjE0Ny40ODAgMzA3LjMyMCBsDQoxNDguMjAwIDMwNy4zMjAgbA0KMTQ4LjY4MCAzMDcu
MzIwIGwNCjE0OS4yODAgMzA3LjQ0MCBsDQoxNDkuODgwIDMwNy40NDAgbA0KMTUwLjQ4MCAzMDcu
NTYwIGwNCjE1MC45NjAgMzA3LjU2MCBsDQoxNTEuNTYwIDMwNy41NjAgbA0KMTUyLjA0MCAzMDcu
NTYwIGwNCjE1Mi42NDAgMzA3LjY4MCBsDQoxNTMuMTIwIDMwNy42ODAgbA0KMTUzLjcyMCAzMDcu
NjgwIGwNCjE1NC4yMDAgMzA3LjgwMCBsDQoxNTQuODAwIDMwNy44MDAgbA0KMTU1LjI4MCAzMDcu
ODAwIGwNCjE1NS43NjAgMzA3LjgwMCBsDQoxNTYuMjQwIDMwNy45MjAgbA0KMTU2LjcyMCAzMDcu
OTIwIGwNCjE1Ny4yMDAgMzA3LjkyMCBsDQoxNTcuODAwIDMwOC4wNDAgbA0KMTU4LjI4MCAzMDgu
MDQwIGwNCjE1OC43NjAgMzA4LjA0MCBsDQoxNTkuMjQwIDMwOC4xNjAgbA0KMTU5LjcyMCAzMDgu
MTYwIGwNCjE2MC4yMDAgMzA4LjE2MCBsDQoxNjAuNjgwIDMwOC4yODAgbA0KMTYxLjA0MCAzMDgu
MjgwIGwNCjE2MS41MjAgMzA4LjI4MCBsDQoxNjIuMDAwIDMwOC40MDAgbA0KMTYyLjQ4MCAzMDgu
NDAwIGwNCjE2Mi44NDAgMzA4LjQwMCBsDQoxNjMuMzIwIDMwOC40MDAgbA0KMTYzLjgwMCAzMDgu
NTIwIGwNCjE2NC4yODAgMzA4LjUyMCBsDQoxNjQuNjQwIDMwOC42NDAgbA0KMTY1LjEyMCAzMDgu
NjQwIGwNCjE2NS42MDAgMzA4LjY0MCBsDQoxNjUuOTYwIDMwOC42NDAgbA0KMTY2LjMyMCAzMDgu
NzYwIGwNCjE2Ni44MDAgMzA4Ljc2MCBsDQoxNjcuMjgwIDMwOC43NjAgbA0KMTY3LjY0MCAzMDgu
ODgwIGwNCjE2OC4wMDAgMzA4Ljg4MCBsDQoxNjguNDgwIDMwOC44ODAgbA0KMTY4Ljg0MCAzMDgu
ODgwIGwNCjE2OS4yMDAgMzA5LjAwMCBsDQoxNjkuNjgwIDMwOS4wMDAgbA0KMTcwLjA0MCAzMDku
MTIwIGwNCjE3MC41MjAgMzA5LjEyMCBsDQoxNzAuODgwIDMwOS4xMjAgbA0KMTcxLjI0MCAzMDku
MTIwIGwNCjE3MS43MjAgMzA5LjI0MCBsDQoxNzIuMDgwIDMwOS4yNDAgbA0KMTcyLjQ0MCAzMDku
MjQwIGwNCjE3Mi44MDAgMzA5LjM2MCBsDQoxNzMuMTYwIDMwOS4zNjAgbA0KMTczLjY0MCAzMDku
MzYwIGwNCjE3NC4wMDAgMzA5LjM2MCBsDQoxNzQuMzYwIDMwOS40ODAgbA0KMTc0LjcyMCAzMDku
NDgwIGwNCjE3NS4wODAgMzA5LjYwMCBsDQoxNzUuNDQwIDMwOS42MDAgbA0KMTc1LjIwMCAzMDku
NDgwIGwNCjE3NS42ODAgMjgwLjgwMCBsDQoxNzUuMzIwIDI4MC44MDAgbA0KMTc0Ljk2MCAyODAu
ODAwIGwNCjE3NC42MDAgMjgwLjY4MCBsDQoxNzQuMTIwIDI4MC42ODAgbA0KMTczLjg4MCAyODAu
NjgwIGwNCjE3My40MDAgMjgwLjU2MCBsDQoxNzMuMDQwIDI4MC41NjAgbA0KMTcyLjY4MCAyODAu
NTYwIGwNCjE3Mi4zMjAgMjgwLjQ0MCBsDQoxNzEuOTYwIDI4MC40NDAgbA0KMTcxLjQ4MCAyODAu
NDQwIGwNCjE3MS4xMjAgMjgwLjMyMCBsDQoxNzAuNzYwIDI4MC4zMjAgbA0KMTcwLjI4MCAyODAu
MzIwIGwNCjE2OS45MjAgMjgwLjMyMCBsDQoxNjkuNTYwIDI4MC4yMDAgbA0KMTY5LjIwMCAyODAu
MjAwIGwNCjE2OC43MjAgMjgwLjA4MCBsDQoxNjguMzYwIDI4MC4wODAgbA0KMTY3Ljg4MCAyODAu
MDgwIGwNCjE2Ny41MjAgMjgwLjA4MCBsDQoxNjcuMDQwIDI3OS45NjAgbA0KMTY2LjY4MCAyNzku
OTYwIGwNCjE2Ni4zMjAgMjc5Ljk2MCBsDQoxNjUuODQwIDI3OS44NDAgbA0KMTY1LjM2MCAyNzku
ODQwIGwNCjE2NS4wMDAgMjc5Ljg0MCBsDQoxNjQuNTIwIDI3OS44NDAgbA0KMTY0LjA0MCAyNzku
NzIwIGwNCjE2My42ODAgMjc5LjcyMCBsDQoxNjMuMjAwIDI3OS42MDAgbA0KMTYyLjcyMCAyNzku
NjAwIGwNCjE2Mi4zNjAgMjc5LjYwMCBsDQoxNjEuODgwIDI3OS42MDAgbA0KMTYxLjQwMCAyNzku
NDgwIGwNCjE2MC45MjAgMjc5LjQ4MCBsDQoxNjAuNDQwIDI3OS40ODAgbA0KMTU5Ljk2MCAyNzku
MzYwIGwNCjE1OS42MDAgMjc5LjM2MCBsDQoxNTkuMTIwIDI3OS4zNjAgbA0KMTU4LjY0MCAyNzku
MzYwIGwNCjE1OC4xNjAgMjc5LjI0MCBsDQoxNTcuNjgwIDI3OS4yNDAgbA0KMTU3LjA4MCAyNzku
MTIwIGwNCjE1Ni42MDAgMjc5LjEyMCBsDQoxNTYuMTIwIDI3OS4xMjAgbA0KMTU1LjY0MCAyNzku
MDAwIGwNCjE1NS4xNjAgMjc5LjAwMCBsDQoxNTQuNTYwIDI3OS4wMDAgbA0KMTU0LjA4MCAyNzku
MDAwIGwNCjE1My42MDAgMjc4Ljg4MCBsDQoxNTMuMDAwIDI3OC44ODAgbA0KMTUyLjUyMCAyNzgu
NzYwIGwNCjE1MS45MjAgMjc4Ljc2MCBsDQoxNTEuMzIwIDI3OC43NjAgbA0KMTUwLjg0MCAyNzgu
NzYwIGwNCjE1MC4yNDAgMjc4LjY0MCBsDQoxNDkuNjQwIDI3OC42NDAgbA0KMTQ5LjE2MCAyNzgu
NjQwIGwNCjE0OC41NjAgMjc4LjUyMCBsDQoxNDcuOTYwIDI3OC41MjAgbA0KMTQ3LjM2MCAyNzgu
NTIwIGwNCjE0Ni43NjAgMjc4LjQwMCBsDQoxNDYuMTYwIDI3OC40MDAgbA0KMTQ1LjQ0MCAyNzgu
NDAwIGwNCjE0NC44NDAgMjc4LjI4MCBsDQoxNDQuMjQwIDI3OC4yODAgbA0KMTQzLjUyMCAyNzgu
MjgwIGwNCjE0Mi45MjAgMjc4LjI4MCBsDQoxNDIuMzIwIDI3OC4xNjAgbA0KMTQxLjQ4MCAyNzgu
MTYwIGwNCjE0MC44ODAgMjc4LjA0MCBsDQoxNDAuMTYwIDI3OC4wNDAgbA0KMTM5LjQ0MCAyNzgu
MDQwIGwNCjEzOC43MjAgMjc4LjA0MCBsDQoxMzcuODgwIDI3Ny45MjAgbA0KMTM3LjE2MCAyNzcu
OTIwIGwNCjEzNi4zMjAgMjc3LjkyMCBsDQoxMzUuNjAwIDI3Ny44MDAgbA0KMTM0LjY0MCAyNzcu
ODAwIGwNCjEzMy45MjAgMjc3LjgwMCBsDQoxMzIuOTYwIDI3Ny44MDAgbA0KMTMyLjEyMCAyNzcu
NjgwIGwNCjEzMS4xNjAgMjc3LjY4MCBsDQoxMzAuMjAwIDI3Ny41NjAgbA0KMTI5LjI0MCAyNzcu
NTYwIGwNCjEyOC4xNjAgMjc3LjU2MCBsDQoxMjcuMDgwIDI3Ny41NjAgbA0KMTI1Ljg4MCAyNzcu
NDQwIGwNCjEyNC42ODAgMjc3LjQ0MCBsDQoxMjMuNDgwIDI3Ny40NDAgbA0KMTIyLjE2MCAyNzcu
MzIwIGwNCjEyMC43MjAgMjc3LjMyMCBsDQoxMTkuMTYwIDI3Ny4zMjAgbA0KMTE3LjM2MCAyNzcu
MzIwIGwNCjExNS40NDAgMjc3LjIwMCBsDQoxMTMuMDQwIDI3Ny4yMDAgbA0KMTEwLjA0MCAyNzcu
MDgwIGwNCjEwMi43MjAgMjc3LjA4MCBsDQo5NS40MDAgMjc3LjA4MCBsDQo5Mi40MDAgMjc3LjIw
MCBsDQo5MC4wMDAgMjc3LjIwMCBsDQo4OC4wODAgMjc3LjMyMCBsDQo4Ni40MDAgMjc3LjMyMCBs
DQo4NC43MjAgMjc3LjMyMCBsDQo4My4yODAgMjc3LjMyMCBsDQo4MS45NjAgMjc3LjQ0MCBsDQo4
MC43NjAgMjc3LjQ0MCBsDQo3OS41NjAgMjc3LjQ0MCBsDQo3OC4zNjAgMjc3LjU2MCBsDQo3Ny4y
ODAgMjc3LjU2MCBsDQo3Ni4zMjAgMjc3LjU2MCBsDQo3NS4zNjAgMjc3LjU2MCBsDQo3NC4yODAg
Mjc3LjY4MCBsDQo3My4zMjAgMjc3LjY4MCBsDQo3Mi40ODAgMjc3LjgwMCBsDQo3MS42NDAgMjc3
LjgwMCBsDQo3MC44MDAgMjc3LjgwMCBsDQo2OS45NjAgMjc3LjgwMCBsDQo2OS4xMjAgMjc3Ljky
MCBsDQo2OC4yODAgMjc3LjkyMCBsDQo2Ny41NjAgMjc3LjkyMCBsDQo2Ni43MjAgMjc4LjA0MCBs
DQo2Ni4wMDAgMjc4LjA0MCBsDQo2NS4yODAgMjc4LjA0MCBsDQo2NC41NjAgMjc4LjE2MCBsDQo2
My45NjAgMjc4LjE2MCBsDQo2My4yNDAgMjc4LjE2MCBsDQo2Mi41MjAgMjc4LjI4MCBsDQo2MS45
MjAgMjc4LjI4MCBsDQo2MS4yMDAgMjc4LjI4MCBsDQo2MC42MDAgMjc4LjI4MCBsDQo2MC4wMDAg
Mjc4LjQwMCBsDQo1OS40MDAgMjc4LjQwMCBsDQo1OC42ODAgMjc4LjUyMCBsDQo1OC4wODAgMjc4
LjUyMCBsDQo1Ny40ODAgMjc4LjUyMCBsDQo1Ni44ODAgMjc4LjUyMCBsDQo1Ni40MDAgMjc4LjY0
MCBsDQo1NS44MDAgMjc4LjY0MCBsDQo1NS4yMDAgMjc4LjY0MCBsDQo1NC42MDAgMjc4Ljc2MCBs
DQo1NC4xMjAgMjc4Ljc2MCBsDQo1My41MjAgMjc4Ljc2MCBsDQo1My4wNDAgMjc4Ljc2MCBsDQo1
Mi40NDAgMjc4Ljg4MCBsDQo1MS45NjAgMjc4Ljg4MCBsDQo1MS4zNjAgMjc5LjAwMCBsDQo1MC44
ODAgMjc5LjAwMCBsDQo1MC4yODAgMjc5LjAwMCBsDQo0OS44MDAgMjc5LjAwMCBsDQo0OS4zMjAg
Mjc5LjEyMCBsDQo0OC44NDAgMjc5LjEyMCBsDQo0OC4zNjAgMjc5LjEyMCBsDQo0Ny44ODAgMjc5
LjI0MCBsDQo0Ny40MDAgMjc5LjI0MCBsDQo0Ni45MjAgMjc5LjM2MCBsDQo0Ni40NDAgMjc5LjM2
MCBsDQo0NS44NDAgMjc5LjM2MCBsDQo0NS40ODAgMjc5LjM2MCBsDQo0NS4wMDAgMjc5LjQ4MCBs
DQo0NC41MjAgMjc5LjQ4MCBsDQo0NC4wNDAgMjc5LjQ4MCBsDQo0My41NjAgMjc5LjYwMCBsDQo0
My4yMDAgMjc5LjYwMCBsDQo0Mi43MjAgMjc5LjYwMCBsDQo0Mi4yNDAgMjc5LjYwMCBsDQo0MS43
NjAgMjc5LjcyMCBsDQo0MS40MDAgMjc5LjcyMCBsDQo0MC45MjAgMjc5Ljg0MCBsDQo0MC40NDAg
Mjc5Ljg0MCBsDQo0MC4wODAgMjc5Ljg0MCBsDQozOS42MDAgMjc5Ljg0MCBsDQozOS4yNDAgMjc5
Ljk2MCBsDQozOC43NjAgMjc5Ljk2MCBsDQozOC40MDAgMjc5Ljk2MCBsDQozNy45MjAgMjgwLjA4
MCBsDQozNy41NjAgMjgwLjA4MCBsDQozNy4wODAgMjgwLjA4MCBsDQozNi43MjAgMjgwLjIwMCBs
DQozNi4zNjAgMjgwLjIwMCBsDQozNS44ODAgMjgwLjIwMCBsDQozNS41MjAgMjgwLjMyMCBsDQoz
NS4xNjAgMjgwLjMyMCBsDQozNC42ODAgMjgwLjMyMCBsDQozNC4zMjAgMjgwLjMyMCBsDQozMy45
NjAgMjgwLjQ0MCBsDQozMy42MDAgMjgwLjQ0MCBsDQozMy4xMjAgMjgwLjU2MCBsDQozMi43NjAg
MjgwLjU2MCBsDQozMi40MDAgMjgwLjU2MCBsDQozMi4wNDAgMjgwLjU2MCBsDQozMS42ODAgMjgw
LjY4MCBsDQozMS4zMjAgMjgwLjY4MCBsDQozMC45NjAgMjgwLjY4MCBsDQozMC40ODAgMjgwLjgw
MCBsDQozMC4xMjAgMjgwLjgwMCBsDQoyOS43NjAgMjgwLjgwMCBsDQozMC4yNDAgMjgwLjgwMCBs
DQozMC4yNDAgMzA5LjM2MCBsDQpiKg0KMC4wMDAgMC4wMDAgMC4wMDAgcmcNCjAuMDAwIDAuMDAw
IDAuMDAwIFJHDQowLjI0MCB3DQpbIF0gMCBkDQoxIEoNCjEgag0KMjMuNjQwIDI4MC41NjAgNi42
MDAgMjkuMDQwIHJlDQpiKg0KMC4wMDAgMC4wMDAgMC4wMDAgcmcNCjAuMDAwIDAuMDAwIDAuMDAw
IFJHDQowLjI0MCB3DQpbIF0gMCBkDQoxIEoNCjEgag0KMTc1LjA4MCAyODAuNDQwIDYuNzIwIDI5
LjA0MCByZQ0KYioNCjAuMDAwIDAuMDAwIDAuMDAwIHJnDQowLjAwMCAwLjAwMCAwLjAwMCBSRw0K
MC4yNDAgdw0KWyBdIDAgZA0KMSBKDQoxIGoNCjEyMS4yMDAgMjk5LjQwMCBtDQoxMTUuOTIwIDI5
OS4wNDAgbA0KMTE1LjkyMCAzMDMuMDAwIGwNCjEyMS4yMDAgMzAzLjAwMCBsDQoxMjEuMjAwIDI5
OS40MDAgbA0KZioNCjAuNzUzIDAuNzUzIDAuNzUzIHJnDQowLjAwMCAwLjAwMCAwLjAwMCBSRw0K
MC4yNDAgdw0KWyBdIDAgZA0KMSBKDQoxIGoNCjEyMS4yMDAgMjk5LjQwMCBtDQoxMTUuNTYwIDI5
OS4wNDAgbA0KMTE2LjUyMCAzMDAuMDAwIGwNCjEyMC4zNjAgMzAwLjI0MCBsDQoxMjAuMzYwIDMw
Mi42NDAgbA0KMTIxLjIwMCAzMDMuNjAwIGwNCjEyMS4yMDAgMjk5LjQwMCBsDQpmKg0KMC41MDIg
MC41MDIgMC41MDIgcmcNCjAuMDAwIDAuMDAwIDAuMDAwIFJHDQowLjI0MCB3DQpbIF0gMCBkDQox
IEoNCjEgag0KMTE1LjY4MCAzMDMuMjQwIG0NCjEyMS4yMDAgMzAzLjYwMCBsDQoxMjAuMjQwIDMw
Mi42NDAgbA0KMTE2LjUyMCAzMDIuNDAwIGwNCjExNi41MjAgMzAwLjAwMCBsDQoxMTUuNjgwIDI5
OS4wNDAgbA0KMTE1LjY4MCAzMDMuMjQwIGwNCmYqDQowLjAwMCAwLjAwMCAwLjAwMCByZw0KMC4w
MDAgMC4wMDAgMC4wMDAgUkcNCjAuMjQwIHcNClsgXSAwIGQNCjEgSg0KMSBqDQoxMjEuMjAwIDI5
My4wNDAgbQ0KMTE1LjkyMCAyOTIuNjgwIGwNCjExNS45MjAgMjk2LjUyMCBsDQoxMjEuMjAwIDI5
Ni41MjAgbA0KMTIxLjIwMCAyOTMuMDQwIGwNCmYqDQowLjc1MyAwLjc1MyAwLjc1MyByZw0KMC4w
MDAgMC4wMDAgMC4wMDAgUkcNCjAuMjQwIHcNClsgXSAwIGQNCjEgSg0KMSBqDQoxMjEuMjAwIDI5
My4wNDAgbQ0KMTE1LjU2MCAyOTIuNjgwIGwNCjExNi41MjAgMjkzLjY0MCBsDQoxMjAuMzYwIDI5
My44ODAgbA0KMTIwLjM2MCAyOTYuMTYwIGwNCjEyMS4yMDAgMjk3LjEyMCBsDQoxMjEuMjAwIDI5
My4wNDAgbA0KZioNCjAuNTAyIDAuNTAyIDAuNTAyIHJnDQowLjAwMCAwLjAwMCAwLjAwMCBSRw0K
MC4yNDAgdw0KWyBdIDAgZA0KMSBKDQoxIGoNCjExNS42ODAgMjk2Ljg4MCBtDQoxMjEuMjAwIDI5
Ny4xMjAgbA0KMTIwLjI0MCAyOTYuMTYwIGwNCjExNi41MjAgMjk2LjA0MCBsDQoxMTYuNTIwIDI5
My42NDAgbA0KMTE1LjY4MCAyOTIuNjgwIGwNCjExNS42ODAgMjk2Ljg4MCBsDQpmKg0KMC4wMDAg
MC4wMDAgMC4wMDAgcmcNCjAuMDAwIDAuMDAwIDAuMDAwIFJHDQowLjI0MCB3DQpbIF0gMCBkDQox
IEoNCjEgag0KMTIxLjIwMCAyODYuNjgwIG0NCjExNS45MjAgMjg2LjMyMCBsDQoxMTUuOTIwIDI5
MC4xNjAgbA0KMTIxLjIwMCAyOTAuMTYwIGwNCjEyMS4yMDAgMjg2LjY4MCBsDQpmKg0KMC43NTMg
MC43NTMgMC43NTMgcmcNCjAuMDAwIDAuMDAwIDAuMDAwIFJHDQowLjI0MCB3DQpbIF0gMCBkDQox
IEoNCjEgag0KMTIxLjIwMCAyODYuNTYwIG0NCjExNS41NjAgMjg2LjMyMCBsDQoxMTYuNTIwIDI4
Ny4yODAgbA0KMTIwLjM2MCAyODcuNDAwIGwNCjEyMC4zNjAgMjg5LjgwMCBsDQoxMjEuMjAwIDI5
MC43NjAgbA0KMTIxLjIwMCAyODYuNTYwIGwNCmYqDQowLjUwMiAwLjUwMiAwLjUwMiByZw0KMC4w
MDAgMC4wMDAgMC4wMDAgUkcNCjAuMjQwIHcNClsgXSAwIGQNCjEgSg0KMSBqDQoxMTUuNjgwIDI5
MC40MDAgbQ0KMTIxLjIwMCAyOTAuNzYwIGwNCjEyMC4yNDAgMjg5LjgwMCBsDQoxMTYuNTIwIDI4
OS41NjAgbA0KMTE2LjUyMCAyODcuMjgwIGwNCjExNS42ODAgMjg2LjMyMCBsDQoxMTUuNjgwIDI5
MC40MDAgbA0KZioNCjAuMDAwIDAuMDAwIDAuMDAwIHJnDQowLjAwMCAwLjAwMCAwLjAwMCBSRw0K
MC4yNDAgdw0KWyBdIDAgZA0KMSBKDQoxIGoNCjEyMS4yMDAgMjgwLjMyMCBtDQoxMTUuOTIwIDI3
OS45NjAgbA0KMTE1LjkyMCAyODMuODAwIGwNCjEyMS4yMDAgMjgzLjgwMCBsDQoxMjEuMjAwIDI4
MC4zMjAgbA0KZioNCjAuNzUzIDAuNzUzIDAuNzUzIHJnDQowLjAwMCAwLjAwMCAwLjAwMCBSRw0K
MC4yNDAgdw0KWyBdIDAgZA0KMSBKDQoxIGoNCjEyMS4yMDAgMjgwLjIwMCBtDQoxMTUuNTYwIDI3
OS44NDAgbA0KMTE2LjUyMCAyODAuODAwIGwNCjEyMC4zNjAgMjgxLjA0MCBsDQoxMjAuMzYwIDI4
My40NDAgbA0KMTIxLjIwMCAyODQuNDAwIGwNCjEyMS4yMDAgMjgwLjIwMCBsDQpmKg0KMC41MDIg
MC41MDIgMC41MDIgcmcNCjAuMDAwIDAuMDAwIDAuMDAwIFJHDQowLjI0MCB3DQpbIF0gMCBkDQox
IEoNCjEgag0KMTE1LjY4MCAyODQuMDQwIG0NCjEyMS4yMDAgMjg0LjQwMCBsDQoxMjAuMjQwIDI4
My40NDAgbA0KMTE2LjUyMCAyODMuMjAwIGwNCjExNi41MjAgMjgwLjgwMCBsDQoxMTUuNjgwIDI3
OS44NDAgbA0KMTE1LjY4MCAyODQuMDQwIGwNCmYqDQowLjAwMCAwLjAwMCAwLjAwMCByZw0KMC4w
MDAgMC4wMDAgMC4wMDAgUkcNCjAuMjQwIHcNClsgXSAwIGQNCjEgSg0KMSBqDQoxMzAuMDgwIDI5
OS43NjAgbQ0KMTI0LjkyMCAyOTkuNDAwIGwNCjEyNC45MjAgMzAzLjI0MCBsDQoxMzAuMDgwIDMw
My4yNDAgbA0KMTMwLjA4MCAyOTkuNzYwIGwNCmYqDQowLjc1MyAwLjc1MyAwLjc1MyByZw0KMC4w
MDAgMC4wMDAgMC4wMDAgUkcNCjAuMjQwIHcNClsgXSAwIGQNCjEgSg0KMSBqDQoxMzAuMDgwIDI5
OS42NDAgbQ0KMTI0LjU2MCAyOTkuMjgwIGwNCjEyNS41MjAgMzAwLjM2MCBsDQoxMjkuMjQwIDMw
MC40ODAgbA0KMTI5LjI0MCAzMDIuODgwIGwNCjEzMC4wODAgMzAzLjg0MCBsDQoxMzAuMDgwIDI5
OS42NDAgbA0KZioNCjAuNTAyIDAuNTAyIDAuNTAyIHJnDQowLjAwMCAwLjAwMCAwLjAwMCBSRw0K
MC4yNDAgdw0KWyBdIDAgZA0KMSBKDQoxIGoNCjEyNC41NjAgMzAzLjQ4MCBtDQoxMzAuMjAwIDMw
My44NDAgbA0KMTI5LjI0MCAzMDIuODgwIGwNCjEyNS40MDAgMzAyLjY0MCBsDQoxMjUuNDAwIDMw
MC4zNjAgbA0KMTI0LjU2MCAyOTkuMjgwIGwNCjEyNC41NjAgMzAzLjQ4MCBsDQpmKg0KMC4wMDAg
MC4wMDAgMC4wMDAgcmcNCjAuMDAwIDAuMDAwIDAuMDAwIFJHDQowLjI0MCB3DQpbIF0gMCBkDQox
IEoNCjEgag0KMTMwLjA4MCAyOTMuMjgwIG0NCjEyNC45MjAgMjkzLjA0MCBsDQoxMjQuOTIwIDI5
Ni44ODAgbA0KMTMwLjA4MCAyOTYuODgwIGwNCjEzMC4wODAgMjkzLjI4MCBsDQpmKg0KMC43NTMg
MC43NTMgMC43NTMgcmcNCjAuMDAwIDAuMDAwIDAuMDAwIFJHDQowLjI0MCB3DQpbIF0gMCBkDQox
IEoNCjEgag0KMTMwLjA4MCAyOTMuMjgwIG0NCjEyNC41NjAgMjkyLjkyMCBsDQoxMjUuNTIwIDI5
My44ODAgbA0KMTI5LjI0MCAyOTQuMTIwIGwNCjEyOS4yNDAgMjk2LjUyMCBsDQoxMzAuMDgwIDI5
Ny40ODAgbA0KMTMwLjA4MCAyOTMuMjgwIGwNCmYqDQowLjUwMiAwLjUwMiAwLjUwMiByZw0KMC4w
MDAgMC4wMDAgMC4wMDAgUkcNCjAuMjQwIHcNClsgXSAwIGQNCjEgSg0KMSBqDQoxMjQuNTYwIDI5
Ny4xMjAgbQ0KMTMwLjIwMCAyOTcuNDgwIGwNCjEyOS4yNDAgMjk2LjUyMCBsDQoxMjUuNDAwIDI5
Ni4yODAgbA0KMTI1LjQwMCAyOTMuODgwIGwNCjEyNC41NjAgMjkyLjkyMCBsDQoxMjQuNTYwIDI5
Ny4xMjAgbA0KZioNCjAuMDAwIDAuMDAwIDAuMDAwIHJnDQowLjAwMCAwLjAwMCAwLjAwMCBSRw0K
MC4yNDAgdw0KWyBdIDAgZA0KMSBKDQoxIGoNCjEzMC4wODAgMjg2LjkyMCBtDQoxMjQuOTIwIDI4
Ni41NjAgbA0KMTI0LjkyMCAyOTAuNTIwIGwNCjEzMC4wODAgMjkwLjUyMCBsDQoxMzAuMDgwIDI4
Ni45MjAgbA0KZioNCjAuNzUzIDAuNzUzIDAuNzUzIHJnDQowLjAwMCAwLjAwMCAwLjAwMCBSRw0K
MC4yNDAgdw0KWyBdIDAgZA0KMSBKDQoxIGoNCjEzMC4wODAgMjg2LjkyMCBtDQoxMjQuNTYwIDI4
Ni41NjAgbA0KMTI1LjUyMCAyODcuNTIwIGwNCjEyOS4yNDAgMjg3Ljc2MCBsDQoxMjkuMjQwIDI5
MC4wNDAgbA0KMTMwLjA4MCAyOTEuMTIwIGwNCjEzMC4wODAgMjg2LjkyMCBsDQpmKg0KMC41MDIg
MC41MDIgMC41MDIgcmcNCjAuMDAwIDAuMDAwIDAuMDAwIFJHDQowLjI0MCB3DQpbIF0gMCBkDQox
IEoNCjEgag0KMTI0LjU2MCAyOTAuNzYwIG0NCjEzMC4yMDAgMjkxLjEyMCBsDQoxMjkuMjQwIDI5
MC4wNDAgbA0KMTI1LjQwMCAyODkuOTIwIGwNCjEyNS40MDAgMjg3LjUyMCBsDQoxMjQuNTYwIDI4
Ni41NjAgbA0KMTI0LjU2MCAyOTAuNzYwIGwNCmYqDQowLjAwMCAwLjAwMCAwLjAwMCByZw0KMC4w
MDAgMC4wMDAgMC4wMDAgUkcNCjAuMjQwIHcNClsgXSAwIGQNCjEgSg0KMSBqDQoxMzAuMDgwIDI4
MC41NjAgbQ0KMTI0LjkyMCAyODAuMjAwIGwNCjEyNC45MjAgMjg0LjA0MCBsDQoxMzAuMDgwIDI4
NC4wNDAgbA0KMTMwLjA4MCAyODAuNTYwIGwNCmYqDQowLjc1MyAwLjc1MyAwLjc1MyByZw0KMC4w
MDAgMC4wMDAgMC4wMDAgUkcNCjAuMjQwIHcNClsgXSAwIGQNCjEgSg0KMSBqDQoxMzAuMDgwIDI4
MC41NjAgbQ0KMTI0LjU2MCAyODAuMjAwIGwNCjEyNS41MjAgMjgxLjE2MCBsDQoxMjkuMjQwIDI4
MS4yODAgbA0KMTI5LjI0MCAyODMuNjgwIGwNCjEzMC4wODAgMjg0LjY0MCBsDQoxMzAuMDgwIDI4
MC41NjAgbA0KZioNCjAuNTAyIDAuNTAyIDAuNTAyIHJnDQowLjAwMCAwLjAwMCAwLjAwMCBSRw0K
MC4yNDAgdw0KWyBdIDAgZA0KMSBKDQoxIGoNCjEyNC41NjAgMjg0LjI4MCBtDQoxMzAuMjAwIDI4
NC42NDAgbA0KMTI5LjI0MCAyODMuNjgwIGwNCjEyNS40MDAgMjgzLjU2MCBsDQoxMjUuNDAwIDI4
MS4xNjAgbA0KMTI0LjU2MCAyODAuMjAwIGwNCjEyNC41NjAgMjg0LjI4MCBsDQpmKg0KMC4wMDAg
MC4wMDAgMC4wMDAgcmcNCjAuMDAwIDAuMDAwIDAuMDAwIFJHDQowLjI0MCB3DQpbIF0gMCBkDQox
IEoNCjEgag0KMTM4Ljg0MCAzMDAuMDAwIG0NCjEzMy41NjAgMjk5LjY0MCBsDQoxMzMuNTYwIDMw
My42MDAgbA0KMTM4Ljg0MCAzMDMuNjAwIGwNCjEzOC44NDAgMzAwLjAwMCBsDQpmKg0KMC43NTMg
MC43NTMgMC43NTMgcmcNCjAuMDAwIDAuMDAwIDAuMDAwIFJHDQowLjI0MCB3DQpbIF0gMCBkDQox
IEoNCjEgag0KMTM4Ljg0MCAzMDAuMDAwIG0NCjEzMy4yMDAgMjk5LjY0MCBsDQoxMzQuMTYwIDMw
MC42MDAgbA0KMTM4LjAwMCAzMDAuODQwIGwNCjEzOC4wMDAgMzAzLjEyMCBsDQoxMzguODQwIDMw
NC4wODAgbA0KMTM4Ljg0MCAzMDAuMDAwIGwNCmYqDQowLjUwMiAwLjUwMiAwLjUwMiByZw0KMC4w
MDAgMC4wMDAgMC4wMDAgUkcNCjAuMjQwIHcNClsgXSAwIGQNCjEgSg0KMSBqDQoxMzMuMzIwIDMw
My44NDAgbQ0KMTM4Ljg0MCAzMDQuMDgwIGwNCjEzNy44ODAgMzAzLjEyMCBsDQoxMzQuMTYwIDMw
My4wMDAgbA0KMTM0LjE2MCAzMDAuNjAwIGwNCjEzMy4zMjAgMjk5LjY0MCBsDQoxMzMuMzIwIDMw
My44NDAgbA0KZioNCjAuMDAwIDAuMDAwIDAuMDAwIHJnDQowLjAwMCAwLjAwMCAwLjAwMCBSRw0K
MC4yNDAgdw0KWyBdIDAgZA0KMSBKDQoxIGoNCjEzOC44NDAgMjkzLjY0MCBtDQoxMzMuNTYwIDI5
My4yODAgbA0KMTMzLjU2MCAyOTcuMTIwIGwNCjEzOC44NDAgMjk3LjEyMCBsDQoxMzguODQwIDI5
My42NDAgbA0KZioNCjAuNzUzIDAuNzUzIDAuNzUzIHJnDQowLjAwMCAwLjAwMCAwLjAwMCBSRw0K
MC4yNDAgdw0KWyBdIDAgZA0KMSBKDQoxIGoNCjEzOC44NDAgMjkzLjUyMCBtDQoxMzMuMjAwIDI5
My4yODAgbA0KMTM0LjE2MCAyOTQuMjQwIGwNCjEzOC4wMDAgMjk0LjM2MCBsDQoxMzguMDAwIDI5
Ni43NjAgbA0KMTM4Ljg0MCAyOTcuNzIwIGwNCjEzOC44NDAgMjkzLjUyMCBsDQpmKg0KMC41MDIg
MC41MDIgMC41MDIgcmcNCjAuMDAwIDAuMDAwIDAuMDAwIFJHDQowLjI0MCB3DQpbIF0gMCBkDQox
IEoNCjEgag0KMTMzLjMyMCAyOTcuMzYwIG0NCjEzOC44NDAgMjk3LjcyMCBsDQoxMzcuODgwIDI5
Ni43NjAgbA0KMTM0LjE2MCAyOTYuNTIwIGwNCjEzNC4xNjAgMjk0LjI0MCBsDQoxMzMuMzIwIDI5
My4yODAgbA0KMTMzLjMyMCAyOTcuMzYwIGwNCmYqDQowLjAwMCAwLjAwMCAwLjAwMCByZw0KMC4w
MDAgMC4wMDAgMC4wMDAgUkcNCjAuMjQwIHcNClsgXSAwIGQNCjEgSg0KMSBqDQoxMzguODQwIDI4
Ny4yODAgbQ0KMTMzLjU2MCAyODYuOTIwIGwNCjEzMy41NjAgMjkwLjc2MCBsDQoxMzguODQwIDI5
MC43NjAgbA0KMTM4Ljg0MCAyODcuMjgwIGwNCmYqDQowLjc1MyAwLjc1MyAwLjc1MyByZw0KMC4w
MDAgMC4wMDAgMC4wMDAgUkcNCjAuMjQwIHcNClsgXSAwIGQNCjEgSg0KMSBqDQoxMzguODQwIDI4
Ny4xNjAgbQ0KMTMzLjIwMCAyODYuODAwIGwNCjEzNC4xNjAgMjg3Ljc2MCBsDQoxMzguMDAwIDI4
OC4wMDAgbA0KMTM4LjAwMCAyOTAuNDAwIGwNCjEzOC44NDAgMjkxLjM2MCBsDQoxMzguODQwIDI4
Ny4xNjAgbA0KZioNCjAuNTAyIDAuNTAyIDAuNTAyIHJnDQowLjAwMCAwLjAwMCAwLjAwMCBSRw0K
MC4yNDAgdw0KWyBdIDAgZA0KMSBKDQoxIGoNCjEzMy4zMjAgMjkxLjAwMCBtDQoxMzguODQwIDI5
MS4zNjAgbA0KMTM3Ljg4MCAyOTAuNDAwIGwNCjEzNC4xNjAgMjkwLjE2MCBsDQoxMzQuMTYwIDI4
Ny43NjAgbA0KMTMzLjMyMCAyODYuODAwIGwNCjEzMy4zMjAgMjkxLjAwMCBsDQpmKg0KMC4wMDAg
MC4wMDAgMC4wMDAgcmcNCjAuMDAwIDAuMDAwIDAuMDAwIFJHDQowLjI0MCB3DQpbIF0gMCBkDQox
IEoNCjEgag0KMTM4Ljg0MCAyODAuODAwIG0NCjEzMy41NjAgMjgwLjU2MCBsDQoxMzMuNTYwIDI4
NC40MDAgbA0KMTM4Ljg0MCAyODQuNDAwIGwNCjEzOC44NDAgMjgwLjgwMCBsDQpmKg0KMC43NTMg
MC43NTMgMC43NTMgcmcNCjAuMDAwIDAuMDAwIDAuMDAwIFJHDQowLjI0MCB3DQpbIF0gMCBkDQox
IEoNCjEgag0KMTM4Ljg0MCAyODAuODAwIG0NCjEzMy4yMDAgMjgwLjQ0MCBsDQoxMzQuMTYwIDI4
MS40MDAgbA0KMTM4LjAwMCAyODEuNjQwIGwNCjEzOC4wMDAgMjg0LjA0MCBsDQoxMzguODQwIDI4
NS4wMDAgbA0KMTM4Ljg0MCAyODAuODAwIGwNCmYqDQowLjUwMiAwLjUwMiAwLjUwMiByZw0KMC4w
MDAgMC4wMDAgMC4wMDAgUkcNCjAuMjQwIHcNClsgXSAwIGQNCjEgSg0KMSBqDQoxMzMuMzIwIDI4
NC42NDAgbQ0KMTM4Ljg0MCAyODUuMDAwIGwNCjEzNy44ODAgMjg0LjA0MCBsDQoxMzQuMTYwIDI4
My44MDAgbA0KMTM0LjE2MCAyODEuNDAwIGwNCjEzMy4zMjAgMjgwLjQ0MCBsDQoxMzMuMzIwIDI4
NC42NDAgbA0KZioNCjAuMDAwIDAuMDAwIDAuMDAwIHJnDQowLjAwMCAwLjAwMCAwLjAwMCBSRw0K
MC4yNDAgdw0KWyBdIDAgZA0KMSBKDQoxIGoNCjE0Ny40ODAgMzAwLjYwMCBtDQoxNDIuMzIwIDMw
MC4yNDAgbA0KMTQyLjMyMCAzMDQuMDgwIGwNCjE0Ny40ODAgMzA0LjA4MCBsDQoxNDcuNDgwIDMw
MC42MDAgbA0KZioNCjAuNzUzIDAuNzUzIDAuNzUzIHJnDQowLjAwMCAwLjAwMCAwLjAwMCBSRw0K
MC4yNDAgdw0KWyBdIDAgZA0KMSBKDQoxIGoNCjE0Ny40ODAgMzAwLjYwMCBtDQoxNDEuOTYwIDMw
MC4yNDAgbA0KMTQyLjkyMCAzMDEuMjAwIGwNCjE0Ni42NDAgMzAxLjMyMCBsDQoxNDYuNjQwIDMw
My43MjAgbA0KMTQ3LjQ4MCAzMDQuNjgwIGwNCjE0Ny40ODAgMzAwLjYwMCBsDQpmKg0KMC41MDIg
MC41MDIgMC41MDIgcmcNCjAuMDAwIDAuMDAwIDAuMDAwIFJHDQowLjI0MCB3DQpbIF0gMCBkDQox
IEoNCjEgag0KMTQxLjk2MCAzMDQuMzIwIG0NCjE0Ny40ODAgMzA0LjY4MCBsDQoxNDYuNTIwIDMw
My43MjAgbA0KMTQyLjgwMCAzMDMuNjAwIGwNCjE0Mi44MDAgMzAxLjIwMCBsDQoxNDEuOTYwIDMw
MC4yNDAgbA0KMTQxLjk2MCAzMDQuMzIwIGwNCmYqDQowLjAwMCAwLjAwMCAwLjAwMCByZw0KMC4w
MDAgMC4wMDAgMC4wMDAgUkcNCjAuMjQwIHcNClsgXSAwIGQNCjEgSg0KMSBqDQoxNDcuNDgwIDI5
NC4yNDAgbQ0KMTQyLjMyMCAyOTMuODgwIGwNCjE0Mi4zMjAgMjk3LjcyMCBsDQoxNDcuNDgwIDI5
Ny43MjAgbA0KMTQ3LjQ4MCAyOTQuMjQwIGwNCmYqDQowLjc1MyAwLjc1MyAwLjc1MyByZw0KMC4w
MDAgMC4wMDAgMC4wMDAgUkcNCjAuMjQwIHcNClsgXSAwIGQNCjEgSg0KMSBqDQoxNDcuNDgwIDI5
NC4xMjAgbQ0KMTQxLjk2MCAyOTMuODgwIGwNCjE0Mi45MjAgMjk0Ljg0MCBsDQoxNDYuNjQwIDI5
NC45NjAgbA0KMTQ2LjY0MCAyOTcuMzYwIGwNCjE0Ny40ODAgMjk4LjMyMCBsDQoxNDcuNDgwIDI5
NC4xMjAgbA0KZioNCjAuNTAyIDAuNTAyIDAuNTAyIHJnDQowLjAwMCAwLjAwMCAwLjAwMCBSRw0K
MC4yNDAgdw0KWyBdIDAgZA0KMSBKDQoxIGoNCjE0MS45NjAgMjk3Ljk2MCBtDQoxNDcuNDgwIDI5
OC4zMjAgbA0KMTQ2LjUyMCAyOTcuMzYwIGwNCjE0Mi44MDAgMjk3LjEyMCBsDQoxNDIuODAwIDI5
NC44NDAgbA0KMTQxLjk2MCAyOTMuODgwIGwNCjE0MS45NjAgMjk3Ljk2MCBsDQpmKg0KMC4wMDAg
MC4wMDAgMC4wMDAgcmcNCjAuMDAwIDAuMDAwIDAuMDAwIFJHDQowLjI0MCB3DQpbIF0gMCBkDQox
IEoNCjEgag0KMTQ3LjQ4MCAyODcuNzYwIG0NCjE0Mi4zMjAgMjg3LjUyMCBsDQoxNDIuMzIwIDI5
MS4zNjAgbA0KMTQ3LjQ4MCAyOTEuMzYwIGwNCjE0Ny40ODAgMjg3Ljc2MCBsDQpmKg0KMC43NTMg
MC43NTMgMC43NTMgcmcNCjAuMDAwIDAuMDAwIDAuMDAwIFJHDQowLjI0MCB3DQpbIF0gMCBkDQox
IEoNCjEgag0KMTQ3LjQ4MCAyODcuNzYwIG0NCjE0MS45NjAgMjg3LjQwMCBsDQoxNDIuOTIwIDI4
OC4zNjAgbA0KMTQ2LjY0MCAyODguNjAwIGwNCjE0Ni42NDAgMjkxLjAwMCBsDQoxNDcuNDgwIDI5
MS45NjAgbA0KMTQ3LjQ4MCAyODcuNzYwIGwNCmYqDQowLjUwMiAwLjUwMiAwLjUwMiByZw0KMC4w
MDAgMC4wMDAgMC4wMDAgUkcNCjAuMjQwIHcNClsgXSAwIGQNCjEgSg0KMSBqDQoxNDEuOTYwIDI5
MS42MDAgbQ0KMTQ3LjQ4MCAyOTEuOTYwIGwNCjE0Ni41MjAgMjkxLjAwMCBsDQoxNDIuODAwIDI5
MC43NjAgbA0KMTQyLjgwMCAyODguMzYwIGwNCjE0MS45NjAgMjg3LjQwMCBsDQoxNDEuOTYwIDI5
MS42MDAgbA0KZioNCjAuMDAwIDAuMDAwIDAuMDAwIHJnDQowLjAwMCAwLjAwMCAwLjAwMCBSRw0K
MC4yNDAgdw0KWyBdIDAgZA0KMSBKDQoxIGoNCjE0Ny40ODAgMjgxLjQwMCBtDQoxNDIuMzIwIDI4
MS4wNDAgbA0KMTQyLjMyMCAyODUuMDAwIGwNCjE0Ny40ODAgMjg1LjAwMCBsDQoxNDcuNDgwIDI4
MS40MDAgbA0KZioNCjAuNzUzIDAuNzUzIDAuNzUzIHJnDQowLjAwMCAwLjAwMCAwLjAwMCBSRw0K
MC4yNDAgdw0KWyBdIDAgZA0KMSBKDQoxIGoNCjE0Ny40ODAgMjgxLjQwMCBtDQoxNDEuOTYwIDI4
MS4wNDAgbA0KMTQyLjkyMCAyODIuMDAwIGwNCjE0Ni42NDAgMjgyLjI0MCBsDQoxNDYuNjQwIDI4
NC41MjAgbA0KMTQ3LjQ4MCAyODUuNjAwIGwNCjE0Ny40ODAgMjgxLjQwMCBsDQpmKg0KMC41MDIg
MC41MDIgMC41MDIgcmcNCjAuMDAwIDAuMDAwIDAuMDAwIFJHDQowLjI0MCB3DQpbIF0gMCBkDQox
IEoNCjEgag0KMTQxLjk2MCAyODUuMjQwIG0NCjE0Ny40ODAgMjg1LjYwMCBsDQoxNDYuNTIwIDI4
NC41MjAgbA0KMTQyLjgwMCAyODQuNDAwIGwNCjE0Mi44MDAgMjgyLjAwMCBsDQoxNDEuOTYwIDI4
MS4wNDAgbA0KMTQxLjk2MCAyODUuMjQwIGwNCmYqDQowLjAwMCAwLjAwMCAwLjAwMCByZw0KMC4w
MDAgMC4wMDAgMC4wMDAgUkcNCjAuMjQwIHcNClsgXSAwIGQNCjEgSg0KMSBqDQoxNTYuMTIwIDMw
MS40NDAgbQ0KMTUwLjk2MCAzMDEuMDgwIGwNCjE1MC45NjAgMzA1LjA0MCBsDQoxNTYuMTIwIDMw
NS4wNDAgbA0KMTU2LjEyMCAzMDEuNDQwIGwNCmYqDQowLjc1MyAwLjc1MyAwLjc1MyByZw0KMC4w
MDAgMC4wMDAgMC4wMDAgUkcNCjAuMjQwIHcNClsgXSAwIGQNCjEgSg0KMSBqDQoxNTYuMTIwIDMw
MS40NDAgbQ0KMTUwLjYwMCAzMDEuMDgwIGwNCjE1MS41NjAgMzAyLjA0MCBsDQoxNTUuMjgwIDMw
Mi4yODAgbA0KMTU1LjI4MCAzMDQuNTYwIGwNCjE1Ni4xMjAgMzA1LjY0MCBsDQoxNTYuMTIwIDMw
MS40NDAgbA0KZioNCjAuNTAyIDAuNTAyIDAuNTAyIHJnDQowLjAwMCAwLjAwMCAwLjAwMCBSRw0K
MC4yNDAgdw0KWyBdIDAgZA0KMSBKDQoxIGoNCjE1MC42MDAgMzA1LjI4MCBtDQoxNTYuMjQwIDMw
NS42NDAgbA0KMTU1LjI4MCAzMDQuNTYwIGwNCjE1MS40NDAgMzA0LjQ0MCBsDQoxNTEuNDQwIDMw
Mi4wNDAgbA0KMTUwLjYwMCAzMDEuMDgwIGwNCjE1MC42MDAgMzA1LjI4MCBsDQpmKg0KMC4wMDAg
MC4wMDAgMC4wMDAgcmcNCjAuMDAwIDAuMDAwIDAuMDAwIFJHDQowLjI0MCB3DQpbIF0gMCBkDQox
IEoNCjEgag0KMTU2LjEyMCAyOTUuMDgwIG0NCjE1MC45NjAgMjk0LjcyMCBsDQoxNTAuOTYwIDI5
OC41NjAgbA0KMTU2LjEyMCAyOTguNTYwIGwNCjE1Ni4xMjAgMjk1LjA4MCBsDQpmKg0KMC43NTMg
MC43NTMgMC43NTMgcmcNCjAuMDAwIDAuMDAwIDAuMDAwIFJHDQowLjI0MCB3DQpbIF0gMCBkDQox
IEoNCjEgag0KMTU2LjEyMCAyOTUuMDgwIG0NCjE1MC42MDAgMjk0LjcyMCBsDQoxNTEuNTYwIDI5
NS42ODAgbA0KMTU1LjI4MCAyOTUuODAwIGwNCjE1NS4yODAgMjk4LjIwMCBsDQoxNTYuMTIwIDI5
OS4xNjAgbA0KMTU2LjEyMCAyOTUuMDgwIGwNCmYqDQowLjUwMiAwLjUwMiAwLjUwMiByZw0KMC4w
MDAgMC4wMDAgMC4wMDAgUkcNCjAuMjQwIHcNClsgXSAwIGQNCjEgSg0KMSBqDQoxNTAuNjAwIDI5
OC44MDAgbQ0KMTU2LjI0MCAyOTkuMTYwIGwNCjE1NS4yODAgMjk4LjIwMCBsDQoxNTEuNDQwIDI5
OC4wODAgbA0KMTUxLjQ0MCAyOTUuNjgwIGwNCjE1MC42MDAgMjk0LjcyMCBsDQoxNTAuNjAwIDI5
OC44MDAgbA0KZioNCjAuMDAwIDAuMDAwIDAuMDAwIHJnDQowLjAwMCAwLjAwMCAwLjAwMCBSRw0K
MC4yNDAgdw0KWyBdIDAgZA0KMSBKDQoxIGoNCjE1Ni4xMjAgMjg4LjcyMCBtDQoxNTAuOTYwIDI4
OC4zNjAgbA0KMTUwLjk2MCAyOTIuMjAwIGwNCjE1Ni4xMjAgMjkyLjIwMCBsDQoxNTYuMTIwIDI4
OC43MjAgbA0KZioNCjAuNzUzIDAuNzUzIDAuNzUzIHJnDQowLjAwMCAwLjAwMCAwLjAwMCBSRw0K
MC4yNDAgdw0KWyBdIDAgZA0KMSBKDQoxIGoNCjE1Ni4xMjAgMjg4LjYwMCBtDQoxNTAuNjAwIDI4
OC4zNjAgbA0KMTUxLjU2MCAyODkuMzIwIGwNCjE1NS4yODAgMjg5LjQ0MCBsDQoxNTUuMjgwIDI5
MS44NDAgbA0KMTU2LjEyMCAyOTIuODAwIGwNCjE1Ni4xMjAgMjg4LjYwMCBsDQpmKg0KMC41MDIg
MC41MDIgMC41MDIgcmcNCjAuMDAwIDAuMDAwIDAuMDAwIFJHDQowLjI0MCB3DQpbIF0gMCBkDQox
IEoNCjEgag0KMTUwLjYwMCAyOTIuNDQwIG0NCjE1Ni4yNDAgMjkyLjgwMCBsDQoxNTUuMjgwIDI5
MS44NDAgbA0KMTUxLjQ0MCAyOTEuNjAwIGwNCjE1MS40NDAgMjg5LjMyMCBsDQoxNTAuNjAwIDI4
OC4zNjAgbA0KMTUwLjYwMCAyOTIuNDQwIGwNCmYqDQowLjAwMCAwLjAwMCAwLjAwMCByZw0KMC4w
MDAgMC4wMDAgMC4wMDAgUkcNCjAuMjQwIHcNClsgXSAwIGQNCjEgSg0KMSBqDQoxNTYuMTIwIDI4
Mi4zNjAgbQ0KMTUwLjk2MCAyODIuMDAwIGwNCjE1MC45NjAgMjg1Ljg0MCBsDQoxNTYuMTIwIDI4
NS44NDAgbA0KMTU2LjEyMCAyODIuMzYwIGwNCmYqDQowLjc1MyAwLjc1MyAwLjc1MyByZw0KMC4w
MDAgMC4wMDAgMC4wMDAgUkcNCjAuMjQwIHcNClsgXSAwIGQNCjEgSg0KMSBqDQoxNTYuMTIwIDI4
Mi4yNDAgbQ0KMTUwLjYwMCAyODEuODgwIGwNCjE1MS41NjAgMjgyLjg0MCBsDQoxNTUuMjgwIDI4
My4wODAgbA0KMTU1LjI4MCAyODUuNDgwIGwNCjE1Ni4xMjAgMjg2LjQ0MCBsDQoxNTYuMTIwIDI4
Mi4yNDAgbA0KZioNCjAuNTAyIDAuNTAyIDAuNTAyIHJnDQowLjAwMCAwLjAwMCAwLjAwMCBSRw0K
MC4yNDAgdw0KWyBdIDAgZA0KMSBKDQoxIGoNCjE1MC42MDAgMjg2LjA4MCBtDQoxNTYuMjQwIDI4
Ni40NDAgbA0KMTU1LjI4MCAyODUuNDgwIGwNCjE1MS40NDAgMjg1LjI0MCBsDQoxNTEuNDQwIDI4
Mi44NDAgbA0KMTUwLjYwMCAyODEuODgwIGwNCjE1MC42MDAgMjg2LjA4MCBsDQpmKg0KMC4wMDAg
MC4wMDAgMC4wMDAgcmcNCjAuMDAwIDAuMDAwIDAuMDAwIFJHDQowLjI0MCB3DQpbIF0gMCBkDQox
IEoNCjEgag0KMTY0Ljg4MCAzMDIuMDQwIG0NCjE1OS42MDAgMzAxLjY4MCBsDQoxNTkuNjAwIDMw
NS42NDAgbA0KMTY0Ljg4MCAzMDUuNjQwIGwNCjE2NC44ODAgMzAyLjA0MCBsDQpmKg0KMC43NTMg
MC43NTMgMC43NTMgcmcNCjAuMDAwIDAuMDAwIDAuMDAwIFJHDQowLjI0MCB3DQpbIF0gMCBkDQox
IEoNCjEgag0KMTY0Ljg4MCAzMDIuMDQwIG0NCjE1OS4yNDAgMzAxLjY4MCBsDQoxNjAuMjAwIDMw
Mi42NDAgbA0KMTY0LjA0MCAzMDIuODgwIGwNCjE2NC4wNDAgMzA1LjE2MCBsDQoxNjQuODgwIDMw
Ni4xMjAgbA0KMTY0Ljg4MCAzMDIuMDQwIGwNCmYqDQowLjUwMiAwLjUwMiAwLjUwMiByZw0KMC4w
MDAgMC4wMDAgMC4wMDAgUkcNCjAuMjQwIHcNClsgXSAwIGQNCjEgSg0KMSBqDQoxNTkuMzYwIDMw
NS44ODAgbQ0KMTY0Ljg4MCAzMDYuMTIwIGwNCjE2My45MjAgMzA1LjE2MCBsDQoxNjAuMjAwIDMw
NS4wNDAgbA0KMTYwLjIwMCAzMDIuNjQwIGwNCjE1OS4zNjAgMzAxLjY4MCBsDQoxNTkuMzYwIDMw
NS44ODAgbA0KZioNCjAuMDAwIDAuMDAwIDAuMDAwIHJnDQowLjAwMCAwLjAwMCAwLjAwMCBSRw0K
MC4yNDAgdw0KWyBdIDAgZA0KMSBKDQoxIGoNCjE2NC44ODAgMjk1LjY4MCBtDQoxNTkuNjAwIDI5
NS4zMjAgbA0KMTU5LjYwMCAyOTkuMTYwIGwNCjE2NC44ODAgMjk5LjE2MCBsDQoxNjQuODgwIDI5
NS42ODAgbA0KZioNCjAuNzUzIDAuNzUzIDAuNzUzIHJnDQowLjAwMCAwLjAwMCAwLjAwMCBSRw0K
MC4yNDAgdw0KWyBdIDAgZA0KMSBKDQoxIGoNCjE2NC44ODAgMjk1LjU2MCBtDQoxNTkuMjQwIDI5
NS4zMjAgbA0KMTYwLjIwMCAyOTYuMjgwIGwNCjE2NC4wNDAgMjk2LjQwMCBsDQoxNjQuMDQwIDI5
OC44MDAgbA0KMTY0Ljg4MCAyOTkuNzYwIGwNCjE2NC44ODAgMjk1LjU2MCBsDQpmKg0KMC41MDIg
MC41MDIgMC41MDIgcmcNCjAuMDAwIDAuMDAwIDAuMDAwIFJHDQowLjI0MCB3DQpbIF0gMCBkDQox
IEoNCjEgag0KMTU5LjM2MCAyOTkuNDAwIG0NCjE2NC44ODAgMjk5Ljc2MCBsDQoxNjMuOTIwIDI5
OC44MDAgbA0KMTYwLjIwMCAyOTguNTYwIGwNCjE2MC4yMDAgMjk2LjI4MCBsDQoxNTkuMzYwIDI5
NS4zMjAgbA0KMTU5LjM2MCAyOTkuNDAwIGwNCmYqDQowLjAwMCAwLjAwMCAwLjAwMCByZw0KMC4w
MDAgMC4wMDAgMC4wMDAgUkcNCjAuMjQwIHcNClsgXSAwIGQNCjEgSg0KMSBqDQoxNjQuODgwIDI4
OS4zMjAgbQ0KMTU5LjYwMCAyODguOTYwIGwNCjE1OS42MDAgMjkyLjgwMCBsDQoxNjQuODgwIDI5
Mi44MDAgbA0KMTY0Ljg4MCAyODkuMzIwIGwNCmYqDQowLjc1MyAwLjc1MyAwLjc1MyByZw0KMC4w
MDAgMC4wMDAgMC4wMDAgUkcNCjAuMjQwIHcNClsgXSAwIGQNCjEgSg0KMSBqDQoxNjQuODgwIDI4
OS4yMDAgbQ0KMTU5LjI0MCAyODguODQwIGwNCjE2MC4yMDAgMjg5LjgwMCBsDQoxNjQuMDQwIDI5
MC4wNDAgbA0KMTY0LjA0MCAyOTIuNDQwIGwNCjE2NC44ODAgMjkzLjQwMCBsDQoxNjQuODgwIDI4
OS4yMDAgbA0KZioNCjAuNTAyIDAuNTAyIDAuNTAyIHJnDQowLjAwMCAwLjAwMCAwLjAwMCBSRw0K
MC4yNDAgdw0KWyBdIDAgZA0KMSBKDQoxIGoNCjE1OS4zNjAgMjkzLjA0MCBtDQoxNjQuODgwIDI5
My40MDAgbA0KMTYzLjkyMCAyOTIuNDQwIGwNCjE2MC4yMDAgMjkyLjIwMCBsDQoxNjAuMjAwIDI4
OS44MDAgbA0KMTU5LjM2MCAyODguODQwIGwNCjE1OS4zNjAgMjkzLjA0MCBsDQpmKg0KMC4wMDAg
MC4wMDAgMC4wMDAgcmcNCjAuMDAwIDAuMDAwIDAuMDAwIFJHDQowLjI0MCB3DQpbIF0gMCBkDQox
IEoNCjEgag0KMTY0Ljg4MCAyODIuODQwIG0NCjE1OS42MDAgMjgyLjYwMCBsDQoxNTkuNjAwIDI4
Ni40NDAgbA0KMTY0Ljg4MCAyODYuNDQwIGwNCjE2NC44ODAgMjgyLjg0MCBsDQpmKg0KMC43NTMg
MC43NTMgMC43NTMgcmcNCjAuMDAwIDAuMDAwIDAuMDAwIFJHDQowLjI0MCB3DQpbIF0gMCBkDQox
IEoNCjEgag0KMTY0Ljg4MCAyODIuODQwIG0NCjE1OS4yNDAgMjgyLjQ4MCBsDQoxNjAuMjAwIDI4
My40NDAgbA0KMTY0LjA0MCAyODMuNjgwIGwNCjE2NC4wNDAgMjg2LjA4MCBsDQoxNjQuODgwIDI4
Ny4wNDAgbA0KMTY0Ljg4MCAyODIuODQwIGwNCmYqDQowLjUwMiAwLjUwMiAwLjUwMiByZw0KMC4w
MDAgMC4wMDAgMC4wMDAgUkcNCjAuMjQwIHcNClsgXSAwIGQNCjEgSg0KMSBqDQoxNTkuMzYwIDI4
Ni42ODAgbQ0KMTY0Ljg4MCAyODcuMDQwIGwNCjE2My45MjAgMjg2LjA4MCBsDQoxNjAuMjAwIDI4
NS44NDAgbA0KMTYwLjIwMCAyODMuNDQwIGwNCjE1OS4zNjAgMjgyLjQ4MCBsDQoxNTkuMzYwIDI4
Ni42ODAgbA0KZioNCjAuMDAwIDAuMDAwIDAuMDAwIHJnDQowLjAwMCAwLjAwMCAwLjAwMCBSRw0K
MC4yNDAgdw0KWyBdIDAgZA0KMSBKDQoxIGoNCjE3Mi42ODAgMzAyLjg4MCBtDQoxNjcuNDAwIDMw
Mi42NDAgbA0KMTY3LjQwMCAzMDYuNDgwIGwNCjE3Mi42ODAgMzA2LjQ4MCBsDQoxNzIuNjgwIDMw
Mi44ODAgbA0KZioNCjAuNzUzIDAuNzUzIDAuNzUzIHJnDQowLjAwMCAwLjAwMCAwLjAwMCBSRw0K
MC4yNDAgdw0KWyBdIDAgZA0KMSBKDQoxIGoNCjE3Mi42ODAgMzAyLjg4MCBtDQoxNjcuMDQwIDMw
Mi41MjAgbA0KMTY4LjAwMCAzMDMuNDgwIGwNCjE3MS44NDAgMzAzLjcyMCBsDQoxNzEuODQwIDMw
Ni4xMjAgbA0KMTcyLjY4MCAzMDcuMDgwIGwNCjE3Mi42ODAgMzAyLjg4MCBsDQpmKg0KMC41MDIg
MC41MDIgMC41MDIgcmcNCjAuMDAwIDAuMDAwIDAuMDAwIFJHDQowLjI0MCB3DQpbIF0gMCBkDQox
IEoNCjEgag0KMTY3LjE2MCAzMDYuNzIwIG0NCjE3Mi42ODAgMzA3LjA4MCBsDQoxNzEuNzIwIDMw
Ni4xMjAgbA0KMTY4LjAwMCAzMDUuODgwIGwNCjE2OC4wMDAgMzAzLjQ4MCBsDQoxNjcuMTYwIDMw
Mi41MjAgbA0KMTY3LjE2MCAzMDYuNzIwIGwNCmYqDQowLjAwMCAwLjAwMCAwLjAwMCByZw0KMC4w
MDAgMC4wMDAgMC4wMDAgUkcNCjAuMjQwIHcNClsgXSAwIGQNCjEgSg0KMSBqDQoxNzIuNjgwIDI5
Ni41MjAgbQ0KMTY3LjQwMCAyOTYuMTYwIGwNCjE2Ny40MDAgMzAwLjEyMCBsDQoxNzIuNjgwIDMw
MC4xMjAgbA0KMTcyLjY4MCAyOTYuNTIwIGwNCmYqDQowLjc1MyAwLjc1MyAwLjc1MyByZw0KMC4w
MDAgMC4wMDAgMC4wMDAgUkcNCjAuMjQwIHcNClsgXSAwIGQNCjEgSg0KMSBqDQoxNzIuNjgwIDI5
Ni41MjAgbQ0KMTY3LjA0MCAyOTYuMTYwIGwNCjE2OC4wMDAgMjk3LjEyMCBsDQoxNzEuODQwIDI5
Ny4zNjAgbA0KMTcxLjg0MCAyOTkuNjQwIGwNCjE3Mi42ODAgMzAwLjYwMCBsDQoxNzIuNjgwIDI5
Ni41MjAgbA0KZioNCjAuNTAyIDAuNTAyIDAuNTAyIHJnDQowLjAwMCAwLjAwMCAwLjAwMCBSRw0K
MC4yNDAgdw0KWyBdIDAgZA0KMSBKDQoxIGoNCjE2Ny4xNjAgMzAwLjM2MCBtDQoxNzIuNjgwIDMw
MC42MDAgbA0KMTcxLjcyMCAyOTkuNjQwIGwNCjE2OC4wMDAgMjk5LjUyMCBsDQoxNjguMDAwIDI5
Ny4xMjAgbA0KMTY3LjE2MCAyOTYuMTYwIGwNCjE2Ny4xNjAgMzAwLjM2MCBsDQpmKg0KMC4wMDAg
MC4wMDAgMC4wMDAgcmcNCjAuMDAwIDAuMDAwIDAuMDAwIFJHDQowLjI0MCB3DQpbIF0gMCBkDQox
IEoNCjEgag0KMTcyLjY4MCAyOTAuMTYwIG0NCjE2Ny40MDAgMjg5LjgwMCBsDQoxNjcuNDAwIDI5
My42NDAgbA0KMTcyLjY4MCAyOTMuNjQwIGwNCjE3Mi42ODAgMjkwLjE2MCBsDQpmKg0KMC43NTMg
MC43NTMgMC43NTMgcmcNCjAuMDAwIDAuMDAwIDAuMDAwIFJHDQowLjI0MCB3DQpbIF0gMCBkDQox
IEoNCjEgag0KMTcyLjY4MCAyOTAuMDQwIG0NCjE2Ny4wNDAgMjg5LjgwMCBsDQoxNjguMDAwIDI5
MC43NjAgbA0KMTcxLjg0MCAyOTAuODgwIGwNCjE3MS44NDAgMjkzLjI4MCBsDQoxNzIuNjgwIDI5
NC4yNDAgbA0KMTcyLjY4MCAyOTAuMDQwIGwNCmYqDQowLjUwMiAwLjUwMiAwLjUwMiByZw0KMC4w
MDAgMC4wMDAgMC4wMDAgUkcNCjAuMjQwIHcNClsgXSAwIGQNCjEgSg0KMSBqDQoxNjcuMTYwIDI5
My44ODAgbQ0KMTcyLjY4MCAyOTQuMjQwIGwNCjE3MS43MjAgMjkzLjI4MCBsDQoxNjguMDAwIDI5
My4wNDAgbA0KMTY4LjAwMCAyOTAuNzYwIGwNCjE2Ny4xNjAgMjg5LjgwMCBsDQoxNjcuMTYwIDI5
My44ODAgbA0KZioNCjAuMDAwIDAuMDAwIDAuMDAwIHJnDQowLjAwMCAwLjAwMCAwLjAwMCBSRw0K
MC4yNDAgdw0KWyBdIDAgZA0KMSBKDQoxIGoNCjE3Mi42ODAgMjgzLjgwMCBtDQoxNjcuNDAwIDI4
My40NDAgbA0KMTY3LjQwMCAyODcuMjgwIGwNCjE3Mi42ODAgMjg3LjI4MCBsDQoxNzIuNjgwIDI4
My44MDAgbA0KZioNCjAuNzUzIDAuNzUzIDAuNzUzIHJnDQowLjAwMCAwLjAwMCAwLjAwMCBSRw0K
MC4yNDAgdw0KWyBdIDAgZA0KMSBKDQoxIGoNCjE3Mi42ODAgMjgzLjY4MCBtDQoxNjcuMDQwIDI4
My4zMjAgbA0KMTY4LjAwMCAyODQuMjgwIGwNCjE3MS44NDAgMjg0LjUyMCBsDQoxNzEuODQwIDI4
Ni45MjAgbA0KMTcyLjY4MCAyODcuODgwIGwNCjE3Mi42ODAgMjgzLjY4MCBsDQpmKg0KMC41MDIg
MC41MDIgMC41MDIgcmcNCjAuMDAwIDAuMDAwIDAuMDAwIFJHDQowLjI0MCB3DQpbIF0gMCBkDQox
IEoNCjEgag0KMTY3LjE2MCAyODcuNTIwIG0NCjE3Mi42ODAgMjg3Ljg4MCBsDQoxNzEuNzIwIDI4
Ni45MjAgbA0KMTY4LjAwMCAyODYuNjgwIGwNCjE2OC4wMDAgMjg0LjI4MCBsDQoxNjcuMTYwIDI4
My4zMjAgbA0KMTY3LjE2MCAyODcuNTIwIGwNCmYqDQowLjAwMCAwLjAwMCAwLjAwMCByZw0KMC4w
MDAgMC4wMDAgMC4wMDAgUkcNCjAuMjQwIHcNClsgXSAwIGQNCjEgSg0KMSBqDQo4My44ODAgMjk5
LjE2MCBtDQo4OS4wNDAgMjk4LjgwMCBsDQo4OS4wNDAgMzAyLjY0MCBsDQo4My44ODAgMzAyLjY0
MCBsDQo4My44ODAgMjk5LjE2MCBsDQpmKg0KMC43NTMgMC43NTMgMC43NTMgcmcNCjAuMDAwIDAu
MDAwIDAuMDAwIFJHDQowLjI0MCB3DQpbIF0gMCBkDQoxIEoNCjEgag0KODMuODgwIDI5OS4wNDAg
bQ0KODkuNDAwIDI5OC44MDAgbA0KODguNDQwIDI5OS43NjAgbA0KODQuNjAwIDI5OS44ODAgbA0K
ODQuNjAwIDMwMi4yODAgbA0KODMuODgwIDMwMy4yNDAgbA0KODMuODgwIDI5OS4wNDAgbA0KZioN
CjAuNTAyIDAuNTAyIDAuNTAyIHJnDQowLjAwMCAwLjAwMCAwLjAwMCBSRw0KMC4yNDAgdw0KWyBd
IDAgZA0KMSBKDQoxIGoNCjg5LjI4MCAzMDIuODgwIG0NCjgzLjc2MCAzMDMuMjQwIGwNCjg0Ljcy
MCAzMDIuMjgwIGwNCjg4LjU2MCAzMDIuMDQwIGwNCjg4LjU2MCAyOTkuNzYwIGwNCjg5LjI4MCAy
OTguODAwIGwNCjg5LjI4MCAzMDIuODgwIGwNCmYqDQowLjAwMCAwLjAwMCAwLjAwMCByZw0KMC4w
MDAgMC4wMDAgMC4wMDAgUkcNCjAuMjQwIHcNClsgXSAwIGQNCjEgSg0KMSBqDQo4My44ODAgMjky
LjgwMCBtDQo4OS4wNDAgMjkyLjQ0MCBsDQo4OS4wNDAgMjk2LjI4MCBsDQo4My44ODAgMjk2LjI4
MCBsDQo4My44ODAgMjkyLjgwMCBsDQpmKg0KMC43NTMgMC43NTMgMC43NTMgcmcNCjAuMDAwIDAu
MDAwIDAuMDAwIFJHDQowLjI0MCB3DQpbIF0gMCBkDQoxIEoNCjEgag0KODMuODgwIDI5Mi42ODAg
bQ0KODkuNDAwIDI5Mi4zMjAgbA0KODguNDQwIDI5My4yODAgbA0KODQuNjAwIDI5My41MjAgbA0K
ODQuNjAwIDI5NS45MjAgbA0KODMuODgwIDI5Ni44ODAgbA0KODMuODgwIDI5Mi42ODAgbA0KZioN
CjAuNTAyIDAuNTAyIDAuNTAyIHJnDQowLjAwMCAwLjAwMCAwLjAwMCBSRw0KMC4yNDAgdw0KWyBd
IDAgZA0KMSBKDQoxIGoNCjg5LjI4MCAyOTYuNTIwIG0NCjgzLjc2MCAyOTYuODgwIGwNCjg0Ljcy
MCAyOTUuOTIwIGwNCjg4LjU2MCAyOTUuNjgwIGwNCjg4LjU2MCAyOTMuMjgwIGwNCjg5LjI4MCAy
OTIuMzIwIGwNCjg5LjI4MCAyOTYuNTIwIGwNCmYqDQowLjAwMCAwLjAwMCAwLjAwMCByZw0KMC4w
MDAgMC4wMDAgMC4wMDAgUkcNCjAuMjQwIHcNClsgXSAwIGQNCjEgSg0KMSBqDQo4My44ODAgMjg2
LjMyMCBtDQo4OS4wNDAgMjg2LjA4MCBsDQo4OS4wNDAgMjg5LjkyMCBsDQo4My44ODAgMjg5Ljky
MCBsDQo4My44ODAgMjg2LjMyMCBsDQpmKg0KMC43NTMgMC43NTMgMC43NTMgcmcNCjAuMDAwIDAu
MDAwIDAuMDAwIFJHDQowLjI0MCB3DQpbIF0gMCBkDQoxIEoNCjEgag0KODMuODgwIDI4Ni4zMjAg
bQ0KODkuNDAwIDI4NS45NjAgbA0KODguNDQwIDI4Ni45MjAgbA0KODQuNjAwIDI4Ny4xNjAgbA0K
ODQuNjAwIDI4OS41NjAgbA0KODMuODgwIDI5MC41MjAgbA0KODMuODgwIDI4Ni4zMjAgbA0KZioN
CjAuNTAyIDAuNTAyIDAuNTAyIHJnDQowLjAwMCAwLjAwMCAwLjAwMCBSRw0KMC4yNDAgdw0KWyBd
IDAgZA0KMSBKDQoxIGoNCjg5LjI4MCAyOTAuMTYwIG0NCjgzLjc2MCAyOTAuNTIwIGwNCjg0Ljcy
MCAyODkuNTYwIGwNCjg4LjU2MCAyODkuMzIwIGwNCjg4LjU2MCAyODYuOTIwIGwNCjg5LjI4MCAy
ODUuOTYwIGwNCjg5LjI4MCAyOTAuMTYwIGwNCmYqDQowLjAwMCAwLjAwMCAwLjAwMCByZw0KMC4w
MDAgMC4wMDAgMC4wMDAgUkcNCjAuMjQwIHcNClsgXSAwIGQNCjEgSg0KMSBqDQo4My44ODAgMjc5
Ljk2MCBtDQo4OS4wNDAgMjc5LjYwMCBsDQo4OS4wNDAgMjgzLjU2MCBsDQo4My44ODAgMjgzLjU2
MCBsDQo4My44ODAgMjc5Ljk2MCBsDQpmKg0KMC43NTMgMC43NTMgMC43NTMgcmcNCjAuMDAwIDAu
MDAwIDAuMDAwIFJHDQowLjI0MCB3DQpbIF0gMCBkDQoxIEoNCjEgag0KODMuODgwIDI3OS45NjAg
bQ0KODkuNDAwIDI3OS42MDAgbA0KODguNDQwIDI4MC41NjAgbA0KODQuNjAwIDI4MC44MDAgbA0K
ODQuNjAwIDI4My4wODAgbA0KODMuODgwIDI4NC4wNDAgbA0KODMuODgwIDI3OS45NjAgbA0KZioN
CjAuNTAyIDAuNTAyIDAuNTAyIHJnDQowLjAwMCAwLjAwMCAwLjAwMCBSRw0KMC4yNDAgdw0KWyBd
IDAgZA0KMSBKDQoxIGoNCjg5LjI4MCAyODMuODAwIG0NCjgzLjc2MCAyODQuMDQwIGwNCjg0Ljcy
MCAyODMuMDgwIGwNCjg4LjU2MCAyODIuOTYwIGwNCjg4LjU2MCAyODAuNTYwIGwNCjg5LjI4MCAy
NzkuNjAwIGwNCjg5LjI4MCAyODMuODAwIGwNCmYqDQowLjAwMCAwLjAwMCAwLjAwMCByZw0KMC4w
MDAgMC4wMDAgMC4wMDAgUkcNCjAuMjQwIHcNClsgXSAwIGQNCjEgSg0KMSBqDQo3NC44ODAgMjk5
LjQwMCBtDQo4MC4wNDAgMjk5LjA0MCBsDQo4MC4wNDAgMzAzLjAwMCBsDQo3NC44ODAgMzAzLjAw
MCBsDQo3NC44ODAgMjk5LjQwMCBsDQpmKg0KMC43NTMgMC43NTMgMC43NTMgcmcNCjAuMDAwIDAu
MDAwIDAuMDAwIFJHDQowLjI0MCB3DQpbIF0gMCBkDQoxIEoNCjEgag0KNzQuODgwIDI5OS40MDAg
bQ0KODAuNDAwIDI5OS4wNDAgbA0KNzkuNDQwIDMwMC4wMDAgbA0KNzUuNzIwIDMwMC4yNDAgbA0K
NzUuNzIwIDMwMi42NDAgbA0KNzQuODgwIDMwMy42MDAgbA0KNzQuODgwIDI5OS40MDAgbA0KZioN
CjAuNTAyIDAuNTAyIDAuNTAyIHJnDQowLjAwMCAwLjAwMCAwLjAwMCBSRw0KMC4yNDAgdw0KWyBd
IDAgZA0KMSBKDQoxIGoNCjgwLjQwMCAzMDMuMjQwIG0NCjc0Ljg4MCAzMDMuNjAwIGwNCjc1Ljg0
MCAzMDIuNjQwIGwNCjc5LjU2MCAzMDIuNDAwIGwNCjc5LjU2MCAzMDAuMDAwIGwNCjgwLjQwMCAy
OTkuMDQwIGwNCjgwLjQwMCAzMDMuMjQwIGwNCmYqDQowLjAwMCAwLjAwMCAwLjAwMCByZw0KMC4w
MDAgMC4wMDAgMC4wMDAgUkcNCjAuMjQwIHcNClsgXSAwIGQNCjEgSg0KMSBqDQo3NC44ODAgMjkz
LjA0MCBtDQo4MC4wNDAgMjkyLjY4MCBsDQo4MC4wNDAgMjk2LjUyMCBsDQo3NC44ODAgMjk2LjUy
MCBsDQo3NC44ODAgMjkzLjA0MCBsDQpmKg0KMC43NTMgMC43NTMgMC43NTMgcmcNCjAuMDAwIDAu
MDAwIDAuMDAwIFJHDQowLjI0MCB3DQpbIF0gMCBkDQoxIEoNCjEgag0KNzQuODgwIDI5My4wNDAg
bQ0KODAuNDAwIDI5Mi42ODAgbA0KNzkuNDQwIDI5My42NDAgbA0KNzUuNzIwIDI5My44ODAgbA0K
NzUuNzIwIDI5Ni4xNjAgbA0KNzQuODgwIDI5Ny4xMjAgbA0KNzQuODgwIDI5My4wNDAgbA0KZioN
CjAuNTAyIDAuNTAyIDAuNTAyIHJnDQowLjAwMCAwLjAwMCAwLjAwMCBSRw0KMC4yNDAgdw0KWyBd
IDAgZA0KMSBKDQoxIGoNCjgwLjQwMCAyOTYuODgwIG0NCjc0Ljg4MCAyOTcuMTIwIGwNCjc1Ljg0
MCAyOTYuMTYwIGwNCjc5LjU2MCAyOTYuMDQwIGwNCjc5LjU2MCAyOTMuNjQwIGwNCjgwLjQwMCAy
OTIuNjgwIGwNCjgwLjQwMCAyOTYuODgwIGwNCmYqDQowLjAwMCAwLjAwMCAwLjAwMCByZw0KMC4w
MDAgMC4wMDAgMC4wMDAgUkcNCjAuMjQwIHcNClsgXSAwIGQNCjEgSg0KMSBqDQo3NC44ODAgMjg2
LjY4MCBtDQo4MC4wNDAgMjg2LjMyMCBsDQo4MC4wNDAgMjkwLjE2MCBsDQo3NC44ODAgMjkwLjE2
MCBsDQo3NC44ODAgMjg2LjY4MCBsDQpmKg0KMC43NTMgMC43NTMgMC43NTMgcmcNCjAuMDAwIDAu
MDAwIDAuMDAwIFJHDQowLjI0MCB3DQpbIF0gMCBkDQoxIEoNCjEgag0KNzQuODgwIDI4Ni41NjAg
bQ0KODAuNDAwIDI4Ni4zMjAgbA0KNzkuNDQwIDI4Ny4yODAgbA0KNzUuNzIwIDI4Ny40MDAgbA0K
NzUuNzIwIDI4OS44MDAgbA0KNzQuODgwIDI5MC43NjAgbA0KNzQuODgwIDI4Ni41NjAgbA0KZioN
CjAuNTAyIDAuNTAyIDAuNTAyIHJnDQowLjAwMCAwLjAwMCAwLjAwMCBSRw0KMC4yNDAgdw0KWyBd
IDAgZA0KMSBKDQoxIGoNCjgwLjQwMCAyOTAuNDAwIG0NCjc0Ljg4MCAyOTAuNzYwIGwNCjc1Ljg0
MCAyODkuODAwIGwNCjc5LjU2MCAyODkuNTYwIGwNCjc5LjU2MCAyODcuMjgwIGwNCjgwLjQwMCAy
ODYuMzIwIGwNCjgwLjQwMCAyOTAuNDAwIGwNCmYqDQowLjAwMCAwLjAwMCAwLjAwMCByZw0KMC4w
MDAgMC4wMDAgMC4wMDAgUkcNCjAuMjQwIHcNClsgXSAwIGQNCjEgSg0KMSBqDQo3NC44ODAgMjgw
LjMyMCBtDQo4MC4wNDAgMjc5Ljk2MCBsDQo4MC4wNDAgMjgzLjgwMCBsDQo3NC44ODAgMjgzLjgw
MCBsDQo3NC44ODAgMjgwLjMyMCBsDQpmKg0KMC43NTMgMC43NTMgMC43NTMgcmcNCjAuMDAwIDAu
MDAwIDAuMDAwIFJHDQowLjI0MCB3DQpbIF0gMCBkDQoxIEoNCjEgag0KNzQuODgwIDI4MC4yMDAg
bQ0KODAuNDAwIDI3OS44NDAgbA0KNzkuNDQwIDI4MC44MDAgbA0KNzUuNzIwIDI4MS4wNDAgbA0K
NzUuNzIwIDI4My40NDAgbA0KNzQuODgwIDI4NC40MDAgbA0KNzQuODgwIDI4MC4yMDAgbA0KZioN
CjAuNTAyIDAuNTAyIDAuNTAyIHJnDQowLjAwMCAwLjAwMCAwLjAwMCBSRw0KMC4yNDAgdw0KWyBd
IDAgZA0KMSBKDQoxIGoNCjgwLjQwMCAyODQuMDQwIG0NCjc0Ljg4MCAyODQuNDAwIGwNCjc1Ljg0
MCAyODMuNDQwIGwNCjc5LjU2MCAyODMuMjAwIGwNCjc5LjU2MCAyODAuODAwIGwNCjgwLjQwMCAy
NzkuODQwIGwNCjgwLjQwMCAyODQuMDQwIGwNCmYqDQowLjAwMCAwLjAwMCAwLjAwMCByZw0KMC4w
MDAgMC4wMDAgMC4wMDAgUkcNCjAuMjQwIHcNClsgXSAwIGQNCjEgSg0KMSBqDQo2Ni4yNDAgMjk5
Ljc2MCBtDQo3MS40MDAgMjk5LjQwMCBsDQo3MS40MDAgMzAzLjI0MCBsDQo2Ni4yNDAgMzAzLjI0
MCBsDQo2Ni4yNDAgMjk5Ljc2MCBsDQpmKg0KMC43NTMgMC43NTMgMC43NTMgcmcNCjAuMDAwIDAu
MDAwIDAuMDAwIFJHDQowLjI0MCB3DQpbIF0gMCBkDQoxIEoNCjEgag0KNjYuMjQwIDI5OS42NDAg
bQ0KNzEuNzYwIDI5OS4yODAgbA0KNzAuODAwIDMwMC4zNjAgbA0KNjYuOTYwIDMwMC40ODAgbA0K
NjYuOTYwIDMwMi44ODAgbA0KNjYuMjQwIDMwMy44NDAgbA0KNjYuMjQwIDI5OS42NDAgbA0KZioN
CjAuNTAyIDAuNTAyIDAuNTAyIHJnDQowLjAwMCAwLjAwMCAwLjAwMCBSRw0KMC4yNDAgdw0KWyBd
IDAgZA0KMSBKDQoxIGoNCjcxLjY0MCAzMDMuNDgwIG0NCjY2LjEyMCAzMDMuODQwIGwNCjY3LjA4
MCAzMDIuODgwIGwNCjcwLjkyMCAzMDIuNjQwIGwNCjcwLjkyMCAzMDAuMzYwIGwNCjcxLjY0MCAy
OTkuMjgwIGwNCjcxLjY0MCAzMDMuNDgwIGwNCmYqDQowLjAwMCAwLjAwMCAwLjAwMCByZw0KMC4w
MDAgMC4wMDAgMC4wMDAgUkcNCjAuMjQwIHcNClsgXSAwIGQNCjEgSg0KMSBqDQo2Ni4yNDAgMjkz
LjI4MCBtDQo3MS40MDAgMjkzLjA0MCBsDQo3MS40MDAgMjk2Ljg4MCBsDQo2Ni4yNDAgMjk2Ljg4
MCBsDQo2Ni4yNDAgMjkzLjI4MCBsDQpmKg0KMC43NTMgMC43NTMgMC43NTMgcmcNCjAuMDAwIDAu
MDAwIDAuMDAwIFJHDQowLjI0MCB3DQpbIF0gMCBkDQoxIEoNCjEgag0KNjYuMjQwIDI5My4yODAg
bQ0KNzEuNzYwIDI5Mi45MjAgbA0KNzAuODAwIDI5My44ODAgbA0KNjYuOTYwIDI5NC4xMjAgbA0K
NjYuOTYwIDI5Ni41MjAgbA0KNjYuMjQwIDI5Ny40ODAgbA0KNjYuMjQwIDI5My4yODAgbA0KZioN
CjAuNTAyIDAuNTAyIDAuNTAyIHJnDQowLjAwMCAwLjAwMCAwLjAwMCBSRw0KMC4yNDAgdw0KWyBd
IDAgZA0KMSBKDQoxIGoNCjcxLjY0MCAyOTcuMTIwIG0NCjY2LjEyMCAyOTcuNDgwIGwNCjY3LjA4
MCAyOTYuNTIwIGwNCjcwLjkyMCAyOTYuMjgwIGwNCjcwLjkyMCAyOTMuODgwIGwNCjcxLjY0MCAy
OTIuOTIwIGwNCjcxLjY0MCAyOTcuMTIwIGwNCmYqDQowLjAwMCAwLjAwMCAwLjAwMCByZw0KMC4w
MDAgMC4wMDAgMC4wMDAgUkcNCjAuMjQwIHcNClsgXSAwIGQNCjEgSg0KMSBqDQo2Ni4yNDAgMjg2
LjkyMCBtDQo3MS40MDAgMjg2LjU2MCBsDQo3MS40MDAgMjkwLjUyMCBsDQo2Ni4yNDAgMjkwLjUy
MCBsDQo2Ni4yNDAgMjg2LjkyMCBsDQpmKg0KMC43NTMgMC43NTMgMC43NTMgcmcNCjAuMDAwIDAu
MDAwIDAuMDAwIFJHDQowLjI0MCB3DQpbIF0gMCBkDQoxIEoNCjEgag0KNjYuMjQwIDI4Ni45MjAg
bQ0KNzEuNzYwIDI4Ni41NjAgbA0KNzAuODAwIDI4Ny41MjAgbA0KNjYuOTYwIDI4Ny43NjAgbA0K
NjYuOTYwIDI5MC4wNDAgbA0KNjYuMjQwIDI5MS4xMjAgbA0KNjYuMjQwIDI4Ni45MjAgbA0KZioN
CjAuNTAyIDAuNTAyIDAuNTAyIHJnDQowLjAwMCAwLjAwMCAwLjAwMCBSRw0KMC4yNDAgdw0KWyBd
IDAgZA0KMSBKDQoxIGoNCjcxLjY0MCAyOTAuNzYwIG0NCjY2LjEyMCAyOTEuMTIwIGwNCjY3LjA4
MCAyOTAuMDQwIGwNCjcwLjkyMCAyODkuOTIwIGwNCjcwLjkyMCAyODcuNTIwIGwNCjcxLjY0MCAy
ODYuNTYwIGwNCjcxLjY0MCAyOTAuNzYwIGwNCmYqDQowLjAwMCAwLjAwMCAwLjAwMCByZw0KMC4w
MDAgMC4wMDAgMC4wMDAgUkcNCjAuMjQwIHcNClsgXSAwIGQNCjEgSg0KMSBqDQo2Ni4yNDAgMjgw
LjU2MCBtDQo3MS40MDAgMjgwLjIwMCBsDQo3MS40MDAgMjg0LjA0MCBsDQo2Ni4yNDAgMjg0LjA0
MCBsDQo2Ni4yNDAgMjgwLjU2MCBsDQpmKg0KMC43NTMgMC43NTMgMC43NTMgcmcNCjAuMDAwIDAu
MDAwIDAuMDAwIFJHDQowLjI0MCB3DQpbIF0gMCBkDQoxIEoNCjEgag0KNjYuMjQwIDI4MC41NjAg
bQ0KNzEuNzYwIDI4MC4yMDAgbA0KNzAuODAwIDI4MS4xNjAgbA0KNjYuOTYwIDI4MS4yODAgbA0K
NjYuOTYwIDI4My42ODAgbA0KNjYuMjQwIDI4NC42NDAgbA0KNjYuMjQwIDI4MC41NjAgbA0KZioN
CjAuNTAyIDAuNTAyIDAuNTAyIHJnDQowLjAwMCAwLjAwMCAwLjAwMCBSRw0KMC4yNDAgdw0KWyBd
IDAgZA0KMSBKDQoxIGoNCjcxLjY0MCAyODQuMjgwIG0NCjY2LjEyMCAyODQuNjQwIGwNCjY3LjA4
MCAyODMuNjgwIGwNCjcwLjkyMCAyODMuNTYwIGwNCjcwLjkyMCAyODEuMTYwIGwNCjcxLjY0MCAy
ODAuMjAwIGwNCjcxLjY0MCAyODQuMjgwIGwNCmYqDQowLjAwMCAwLjAwMCAwLjAwMCByZw0KMC4w
MDAgMC4wMDAgMC4wMDAgUkcNCjAuMjQwIHcNClsgXSAwIGQNCjEgSg0KMSBqDQo1Ny40ODAgMzAw
LjM2MCBtDQo2Mi43NjAgMzAwLjAwMCBsDQo2Mi43NjAgMzAzLjg0MCBsDQo1Ny40ODAgMzAzLjg0
MCBsDQo1Ny40ODAgMzAwLjM2MCBsDQpmKg0KMC43NTMgMC43NTMgMC43NTMgcmcNCjAuMDAwIDAu
MDAwIDAuMDAwIFJHDQowLjI0MCB3DQpbIF0gMCBkDQoxIEoNCjEgag0KNTcuNDgwIDMwMC4yNDAg
bQ0KNjMuMDAwIDI5OS44ODAgbA0KNjIuMDQwIDMwMC44NDAgbA0KNTguMzIwIDMwMS4wODAgbA0K
NTguMzIwIDMwMy40ODAgbA0KNTcuNDgwIDMwNC40NDAgbA0KNTcuNDgwIDMwMC4yNDAgbA0KZioN
CjAuNTAyIDAuNTAyIDAuNTAyIHJnDQowLjAwMCAwLjAwMCAwLjAwMCBSRw0KMC4yNDAgdw0KWyBd
IDAgZA0KMSBKDQoxIGoNCjYzLjAwMCAzMDQuMDgwIG0NCjU3LjQ4MCAzMDQuNDQwIGwNCjU4LjQ0
MCAzMDMuNDgwIGwNCjYyLjE2MCAzMDMuMjQwIGwNCjYyLjE2MCAzMDAuODQwIGwNCjYzLjAwMCAy
OTkuODgwIGwNCjYzLjAwMCAzMDQuMDgwIGwNCmYqDQowLjAwMCAwLjAwMCAwLjAwMCByZw0KMC4w
MDAgMC4wMDAgMC4wMDAgUkcNCjAuMjQwIHcNClsgXSAwIGQNCjEgSg0KMSBqDQo1Ny40ODAgMjkz
Ljg4MCBtDQo2Mi43NjAgMjkzLjUyMCBsDQo2Mi43NjAgMjk3LjQ4MCBsDQo1Ny40ODAgMjk3LjQ4
MCBsDQo1Ny40ODAgMjkzLjg4MCBsDQpmKg0KMC43NTMgMC43NTMgMC43NTMgcmcNCjAuMDAwIDAu
MDAwIDAuMDAwIFJHDQowLjI0MCB3DQpbIF0gMCBkDQoxIEoNCjEgag0KNTcuNDgwIDI5My44ODAg
bQ0KNjMuMDAwIDI5My41MjAgbA0KNjIuMDQwIDI5NC40ODAgbA0KNTguMzIwIDI5NC43MjAgbA0K
NTguMzIwIDI5Ny4xMjAgbA0KNTcuNDgwIDI5OC4wODAgbA0KNTcuNDgwIDI5My44ODAgbA0KZioN
CjAuNTAyIDAuNTAyIDAuNTAyIHJnDQowLjAwMCAwLjAwMCAwLjAwMCBSRw0KMC4yNDAgdw0KWyBd
IDAgZA0KMSBKDQoxIGoNCjYzLjAwMCAyOTcuNzIwIG0NCjU3LjQ4MCAyOTguMDgwIGwNCjU4LjQ0
MCAyOTcuMTIwIGwNCjYyLjE2MCAyOTYuODgwIGwNCjYyLjE2MCAyOTQuNDgwIGwNCjYzLjAwMCAy
OTMuNTIwIGwNCjYzLjAwMCAyOTcuNzIwIGwNCmYqDQowLjAwMCAwLjAwMCAwLjAwMCByZw0KMC4w
MDAgMC4wMDAgMC4wMDAgUkcNCjAuMjQwIHcNClsgXSAwIGQNCjEgSg0KMSBqDQo1Ny40ODAgMjg3
LjUyMCBtDQo2Mi43NjAgMjg3LjE2MCBsDQo2Mi43NjAgMjkxLjEyMCBsDQo1Ny40ODAgMjkxLjEy
MCBsDQo1Ny40ODAgMjg3LjUyMCBsDQpmKg0KMC43NTMgMC43NTMgMC43NTMgcmcNCjAuMDAwIDAu
MDAwIDAuMDAwIFJHDQowLjI0MCB3DQpbIF0gMCBkDQoxIEoNCjEgag0KNTcuNDgwIDI4Ny41MjAg
bQ0KNjMuMDAwIDI4Ny4xNjAgbA0KNjIuMDQwIDI4OC4xMjAgbA0KNTguMzIwIDI4OC4zNjAgbA0K
NTguMzIwIDI5MC42NDAgbA0KNTcuNDgwIDI5MS42MDAgbA0KNTcuNDgwIDI4Ny41MjAgbA0KZioN
CjAuNTAyIDAuNTAyIDAuNTAyIHJnDQowLjAwMCAwLjAwMCAwLjAwMCBSRw0KMC4yNDAgdw0KWyBd
IDAgZA0KMSBKDQoxIGoNCjYzLjAwMCAyOTEuMzYwIG0NCjU3LjQ4MCAyOTEuNjAwIGwNCjU4LjQ0
MCAyOTAuNjQwIGwNCjYyLjE2MCAyOTAuNTIwIGwNCjYyLjE2MCAyODguMTIwIGwNCjYzLjAwMCAy
ODcuMTYwIGwNCjYzLjAwMCAyOTEuMzYwIGwNCmYqDQowLjAwMCAwLjAwMCAwLjAwMCByZw0KMC4w
MDAgMC4wMDAgMC4wMDAgUkcNCjAuMjQwIHcNClsgXSAwIGQNCjEgSg0KMSBqDQo1Ny40ODAgMjgx
LjE2MCBtDQo2Mi43NjAgMjgwLjgwMCBsDQo2Mi43NjAgMjg0LjY0MCBsDQo1Ny40ODAgMjg0LjY0
MCBsDQo1Ny40ODAgMjgxLjE2MCBsDQpmKg0KMC43NTMgMC43NTMgMC43NTMgcmcNCjAuMDAwIDAu
MDAwIDAuMDAwIFJHDQowLjI0MCB3DQpbIF0gMCBkDQoxIEoNCjEgag0KNTcuNDgwIDI4MS4wNDAg
bQ0KNjMuMDAwIDI4MC44MDAgbA0KNjIuMDQwIDI4MS43NjAgbA0KNTguMzIwIDI4MS44ODAgbA0K
NTguMzIwIDI4NC4yODAgbA0KNTcuNDgwIDI4NS4yNDAgbA0KNTcuNDgwIDI4MS4wNDAgbA0KZioN
CjAuNTAyIDAuNTAyIDAuNTAyIHJnDQowLjAwMCAwLjAwMCAwLjAwMCBSRw0KMC4yNDAgdw0KWyBd
IDAgZA0KMSBKDQoxIGoNCjYzLjAwMCAyODQuODgwIG0NCjU3LjQ4MCAyODUuMjQwIGwNCjU4LjQ0
MCAyODQuMjgwIGwNCjYyLjE2MCAyODQuMDQwIGwNCjYyLjE2MCAyODEuNzYwIGwNCjYzLjAwMCAy
ODAuODAwIGwNCjYzLjAwMCAyODQuODgwIGwNCmYqDQowLjAwMCAwLjAwMCAwLjAwMCByZw0KMC4w
MDAgMC4wMDAgMC4wMDAgUkcNCjAuMjQwIHcNClsgXSAwIGQNCjEgSg0KMSBqDQo0OC44NDAgMzAx
LjIwMCBtDQo1NC4wMDAgMzAwLjg0MCBsDQo1NC4wMDAgMzA0LjY4MCBsDQo0OC44NDAgMzA0LjY4
MCBsDQo0OC44NDAgMzAxLjIwMCBsDQpmKg0KMC43NTMgMC43NTMgMC43NTMgcmcNCjAuMDAwIDAu
MDAwIDAuMDAwIFJHDQowLjI0MCB3DQpbIF0gMCBkDQoxIEoNCjEgag0KNDguODQwIDMwMS4wODAg
bQ0KNTQuMzYwIDMwMC44NDAgbA0KNTMuNDAwIDMwMS44MDAgbA0KNDkuNjgwIDMwMS45MjAgbA0K
NDkuNjgwIDMwNC4zMjAgbA0KNDguODQwIDMwNS4yODAgbA0KNDguODQwIDMwMS4wODAgbA0KZioN
CjAuNTAyIDAuNTAyIDAuNTAyIHJnDQowLjAwMCAwLjAwMCAwLjAwMCBSRw0KMC4yNDAgdw0KWyBd
IDAgZA0KMSBKDQoxIGoNCjU0LjM2MCAzMDQuOTIwIG0NCjQ4Ljg0MCAzMDUuMjgwIGwNCjQ5Ljgw
MCAzMDQuMzIwIGwNCjUzLjUyMCAzMDQuMDgwIGwNCjUzLjUyMCAzMDEuODAwIGwNCjU0LjM2MCAz
MDAuODQwIGwNCjU0LjM2MCAzMDQuOTIwIGwNCmYqDQowLjAwMCAwLjAwMCAwLjAwMCByZw0KMC4w
MDAgMC4wMDAgMC4wMDAgUkcNCjAuMjQwIHcNClsgXSAwIGQNCjEgSg0KMSBqDQo0OC44NDAgMjk0
Ljg0MCBtDQo1NC4wMDAgMjk0LjQ4MCBsDQo1NC4wMDAgMjk4LjMyMCBsDQo0OC44NDAgMjk4LjMy
MCBsDQo0OC44NDAgMjk0Ljg0MCBsDQpmKg0KMC43NTMgMC43NTMgMC43NTMgcmcNCjAuMDAwIDAu
MDAwIDAuMDAwIFJHDQowLjI0MCB3DQpbIF0gMCBkDQoxIEoNCjEgag0KNDguODQwIDI5NC43MjAg
bQ0KNTQuMzYwIDI5NC4zNjAgbA0KNTMuNDAwIDI5NS4zMjAgbA0KNDkuNjgwIDI5NS41NjAgbA0K
NDkuNjgwIDI5Ny45NjAgbA0KNDguODQwIDI5OC45MjAgbA0KNDguODQwIDI5NC43MjAgbA0KZioN
CjAuNTAyIDAuNTAyIDAuNTAyIHJnDQowLjAwMCAwLjAwMCAwLjAwMCBSRw0KMC4yNDAgdw0KWyBd
IDAgZA0KMSBKDQoxIGoNCjU0LjM2MCAyOTguNTYwIG0NCjQ4Ljg0MCAyOTguOTIwIGwNCjQ5Ljgw
MCAyOTcuOTYwIGwNCjUzLjUyMCAyOTcuNzIwIGwNCjUzLjUyMCAyOTUuMzIwIGwNCjU0LjM2MCAy
OTQuMzYwIGwNCjU0LjM2MCAyOTguNTYwIGwNCmYqDQowLjAwMCAwLjAwMCAwLjAwMCByZw0KMC4w
MDAgMC4wMDAgMC4wMDAgUkcNCjAuMjQwIHcNClsgXSAwIGQNCjEgSg0KMSBqDQo0OC44NDAgMjg4
LjM2MCBtDQo1NC4wMDAgMjg4LjEyMCBsDQo1NC4wMDAgMjkxLjk2MCBsDQo0OC44NDAgMjkxLjk2
MCBsDQo0OC44NDAgMjg4LjM2MCBsDQpmKg0KMC43NTMgMC43NTMgMC43NTMgcmcNCjAuMDAwIDAu
MDAwIDAuMDAwIFJHDQowLjI0MCB3DQpbIF0gMCBkDQoxIEoNCjEgag0KNDguODQwIDI4OC4zNjAg
bQ0KNTQuMzYwIDI4OC4wMDAgbA0KNTMuNDAwIDI4OC45NjAgbA0KNDkuNjgwIDI4OS4yMDAgbA0K
NDkuNjgwIDI5MS42MDAgbA0KNDguODQwIDI5Mi41NjAgbA0KNDguODQwIDI4OC4zNjAgbA0KZioN
CjAuNTAyIDAuNTAyIDAuNTAyIHJnDQowLjAwMCAwLjAwMCAwLjAwMCBSRw0KMC4yNDAgdw0KWyBd
IDAgZA0KMSBKDQoxIGoNCjU0LjM2MCAyOTIuMjAwIG0NCjQ4Ljg0MCAyOTIuNTYwIGwNCjQ5Ljgw
MCAyOTEuNjAwIGwNCjUzLjUyMCAyOTEuMzYwIGwNCjUzLjUyMCAyODguOTYwIGwNCjU0LjM2MCAy
ODguMDAwIGwNCjU0LjM2MCAyOTIuMjAwIGwNCmYqDQowLjAwMCAwLjAwMCAwLjAwMCByZw0KMC4w
MDAgMC4wMDAgMC4wMDAgUkcNCjAuMjQwIHcNClsgXSAwIGQNCjEgSg0KMSBqDQo0OC44NDAgMjgy
LjAwMCBtDQo1NC4wMDAgMjgxLjY0MCBsDQo1NC4wMDAgMjg1LjYwMCBsDQo0OC44NDAgMjg1LjYw
MCBsDQo0OC44NDAgMjgyLjAwMCBsDQpmKg0KMC43NTMgMC43NTMgMC43NTMgcmcNCjAuMDAwIDAu
MDAwIDAuMDAwIFJHDQowLjI0MCB3DQpbIF0gMCBkDQoxIEoNCjEgag0KNDguODQwIDI4Mi4wMDAg
bQ0KNTQuMzYwIDI4MS42NDAgbA0KNTMuNDAwIDI4Mi42MDAgbA0KNDkuNjgwIDI4Mi44NDAgbA0K
NDkuNjgwIDI4NS4xMjAgbA0KNDguODQwIDI4Ni4wODAgbA0KNDguODQwIDI4Mi4wMDAgbA0KZioN
CjAuNTAyIDAuNTAyIDAuNTAyIHJnDQowLjAwMCAwLjAwMCAwLjAwMCBSRw0KMC4yNDAgdw0KWyBd
IDAgZA0KMSBKDQoxIGoNCjU0LjM2MCAyODUuODQwIG0NCjQ4Ljg0MCAyODYuMDgwIGwNCjQ5Ljgw
MCAyODUuMTIwIGwNCjUzLjUyMCAyODUuMDAwIGwNCjUzLjUyMCAyODIuNjAwIGwNCjU0LjM2MCAy
ODEuNjQwIGwNCjU0LjM2MCAyODUuODQwIGwNCmYqDQowLjAwMCAwLjAwMCAwLjAwMCByZw0KMC4w
MDAgMC4wMDAgMC4wMDAgUkcNCjAuMjQwIHcNClsgXSAwIGQNCjEgSg0KMSBqDQo0MC4yMDAgMzAx
LjgwMCBtDQo0NS4zNjAgMzAxLjQ0MCBsDQo0NS4zNjAgMzA1LjI4MCBsDQo0MC4yMDAgMzA1LjI4
MCBsDQo0MC4yMDAgMzAxLjgwMCBsDQpmKg0KMC43NTMgMC43NTMgMC43NTMgcmcNCjAuMDAwIDAu
MDAwIDAuMDAwIFJHDQowLjI0MCB3DQpbIF0gMCBkDQoxIEoNCjEgag0KNDAuMjAwIDMwMS42ODAg
bQ0KNDUuNzIwIDMwMS4zMjAgbA0KNDQuNzYwIDMwMi4yODAgbA0KNDEuMDQwIDMwMi41MjAgbA0K
NDEuMDQwIDMwNC45MjAgbA0KNDAuMjAwIDMwNS44ODAgbA0KNDAuMjAwIDMwMS42ODAgbA0KZioN
CjAuNTAyIDAuNTAyIDAuNTAyIHJnDQowLjAwMCAwLjAwMCAwLjAwMCBSRw0KMC4yNDAgdw0KWyBd
IDAgZA0KMSBKDQoxIGoNCjQ1LjYwMCAzMDUuNTIwIG0NCjQwLjA4MCAzMDUuODgwIGwNCjQxLjA0
MCAzMDQuOTIwIGwNCjQ0Ljg4MCAzMDQuNjgwIGwNCjQ0Ljg4MCAzMDIuMjgwIGwNCjQ1LjYwMCAz
MDEuMzIwIGwNCjQ1LjYwMCAzMDUuNTIwIGwNCmYqDQowLjAwMCAwLjAwMCAwLjAwMCByZw0KMC4w
MDAgMC4wMDAgMC4wMDAgUkcNCjAuMjQwIHcNClsgXSAwIGQNCjEgSg0KMSBqDQo0MC4yMDAgMjk1
LjMyMCBtDQo0NS4zNjAgMjk1LjA4MCBsDQo0NS4zNjAgMjk4LjkyMCBsDQo0MC4yMDAgMjk4Ljky
MCBsDQo0MC4yMDAgMjk1LjMyMCBsDQpmKg0KMC43NTMgMC43NTMgMC43NTMgcmcNCjAuMDAwIDAu
MDAwIDAuMDAwIFJHDQowLjI0MCB3DQpbIF0gMCBkDQoxIEoNCjEgag0KNDAuMjAwIDI5NS4zMjAg
bQ0KNDUuNzIwIDI5NC45NjAgbA0KNDQuNzYwIDI5NS45MjAgbA0KNDEuMDQwIDI5Ni4xNjAgbA0K
NDEuMDQwIDI5OC41NjAgbA0KNDAuMjAwIDI5OS41MjAgbA0KNDAuMjAwIDI5NS4zMjAgbA0KZioN
CjAuNTAyIDAuNTAyIDAuNTAyIHJnDQowLjAwMCAwLjAwMCAwLjAwMCBSRw0KMC4yNDAgdw0KWyBd
IDAgZA0KMSBKDQoxIGoNCjQ1LjYwMCAyOTkuMTYwIG0NCjQwLjA4MCAyOTkuNTIwIGwNCjQxLjA0
MCAyOTguNTYwIGwNCjQ0Ljg4MCAyOTguMzIwIGwNCjQ0Ljg4MCAyOTUuOTIwIGwNCjQ1LjYwMCAy
OTQuOTYwIGwNCjQ1LjYwMCAyOTkuMTYwIGwNCmYqDQowLjAwMCAwLjAwMCAwLjAwMCByZw0KMC4w
MDAgMC4wMDAgMC4wMDAgUkcNCjAuMjQwIHcNClsgXSAwIGQNCjEgSg0KMSBqDQo0MC4yMDAgMjg4
Ljk2MCBtDQo0NS4zNjAgMjg4LjYwMCBsDQo0NS4zNjAgMjkyLjU2MCBsDQo0MC4yMDAgMjkyLjU2
MCBsDQo0MC4yMDAgMjg4Ljk2MCBsDQpmKg0KMC43NTMgMC43NTMgMC43NTMgcmcNCjAuMDAwIDAu
MDAwIDAuMDAwIFJHDQowLjI0MCB3DQpbIF0gMCBkDQoxIEoNCjEgag0KNDAuMjAwIDI4OC45NjAg
bQ0KNDUuNzIwIDI4OC42MDAgbA0KNDQuNzYwIDI4OS41NjAgbA0KNDEuMDQwIDI4OS44MDAgbA0K
NDEuMDQwIDI5Mi4wODAgbA0KNDAuMjAwIDI5My4wNDAgbA0KNDAuMjAwIDI4OC45NjAgbA0KZioN
CjAuNTAyIDAuNTAyIDAuNTAyIHJnDQowLjAwMCAwLjAwMCAwLjAwMCBSRw0KMC4yNDAgdw0KWyBd
IDAgZA0KMSBKDQoxIGoNCjQ1LjYwMCAyOTIuODAwIG0NCjQwLjA4MCAyOTMuMDQwIGwNCjQxLjA0
MCAyOTIuMDgwIGwNCjQ0Ljg4MCAyOTEuOTYwIGwNCjQ0Ljg4MCAyODkuNTYwIGwNCjQ1LjYwMCAy
ODguNjAwIGwNCjQ1LjYwMCAyOTIuODAwIGwNCmYqDQowLjAwMCAwLjAwMCAwLjAwMCByZw0KMC4w
MDAgMC4wMDAgMC4wMDAgUkcNCjAuMjQwIHcNClsgXSAwIGQNCjEgSg0KMSBqDQo0MC4yMDAgMjgy
LjYwMCBtDQo0NS4zNjAgMjgyLjI0MCBsDQo0NS4zNjAgMjg2LjA4MCBsDQo0MC4yMDAgMjg2LjA4
MCBsDQo0MC4yMDAgMjgyLjYwMCBsDQpmKg0KMC43NTMgMC43NTMgMC43NTMgcmcNCjAuMDAwIDAu
MDAwIDAuMDAwIFJHDQowLjI0MCB3DQpbIF0gMCBkDQoxIEoNCjEgag0KNDAuMjAwIDI4Mi42MDAg
bQ0KNDUuNzIwIDI4Mi4yNDAgbA0KNDQuNzYwIDI4My4yMDAgbA0KNDEuMDQwIDI4My4zMjAgbA0K
NDEuMDQwIDI4NS43MjAgbA0KNDAuMjAwIDI4Ni42ODAgbA0KNDAuMjAwIDI4Mi42MDAgbA0KZioN
CjAuNTAyIDAuNTAyIDAuNTAyIHJnDQowLjAwMCAwLjAwMCAwLjAwMCBSRw0KMC4yNDAgdw0KWyBd
IDAgZA0KMSBKDQoxIGoNCjQ1LjYwMCAyODYuMzIwIG0NCjQwLjA4MCAyODYuNjgwIGwNCjQxLjA0
MCAyODUuNzIwIGwNCjQ0Ljg4MCAyODUuNjAwIGwNCjQ0Ljg4MCAyODMuMjAwIGwNCjQ1LjYwMCAy
ODIuMjQwIGwNCjQ1LjYwMCAyODYuMzIwIGwNCmYqDQowLjAwMCAwLjAwMCAwLjAwMCByZw0KMC4w
MDAgMC4wMDAgMC4wMDAgUkcNCjAuMjQwIHcNClsgXSAwIGQNCjEgSg0KMSBqDQozMi40MDAgMzAy
LjY0MCBtDQozNy41NjAgMzAyLjI4MCBsDQozNy41NjAgMzA2LjEyMCBsDQozMi40MDAgMzA2LjEy
MCBsDQozMi40MDAgMzAyLjY0MCBsDQpmKg0KMC43NTMgMC43NTMgMC43NTMgcmcNCjAuMDAwIDAu
MDAwIDAuMDAwIFJHDQowLjI0MCB3DQpbIF0gMCBkDQoxIEoNCjEgag0KMzIuNDAwIDMwMi42NDAg
bQ0KMzcuOTIwIDMwMi4yODAgbA0KMzYuOTYwIDMwMy4yNDAgbA0KMzMuMTIwIDMwMy4zNjAgbA0K
MzMuMTIwIDMwNS43NjAgbA0KMzIuNDAwIDMwNi43MjAgbA0KMzIuNDAwIDMwMi42NDAgbA0KZioN
CjAuNTAyIDAuNTAyIDAuNTAyIHJnDQowLjAwMCAwLjAwMCAwLjAwMCBSRw0KMC4yNDAgdw0KWyBd
IDAgZA0KMSBKDQoxIGoNCjM3LjgwMCAzMDYuMzYwIG0NCjMyLjI4MCAzMDYuNzIwIGwNCjMzLjI0
MCAzMDUuNzYwIGwNCjM3LjA4MCAzMDUuNjQwIGwNCjM3LjA4MCAzMDMuMjQwIGwNCjM3LjgwMCAz
MDIuMjgwIGwNCjM3LjgwMCAzMDYuMzYwIGwNCmYqDQowLjAwMCAwLjAwMCAwLjAwMCByZw0KMC4w
MDAgMC4wMDAgMC4wMDAgUkcNCjAuMjQwIHcNClsgXSAwIGQNCjEgSg0KMSBqDQozMi40MDAgMjk2
LjI4MCBtDQozNy41NjAgMjk1LjkyMCBsDQozNy41NjAgMjk5Ljc2MCBsDQozMi40MDAgMjk5Ljc2
MCBsDQozMi40MDAgMjk2LjI4MCBsDQpmKg0KMC43NTMgMC43NTMgMC43NTMgcmcNCjAuMDAwIDAu
MDAwIDAuMDAwIFJHDQowLjI0MCB3DQpbIF0gMCBkDQoxIEoNCjEgag0KMzIuNDAwIDI5Ni4xNjAg
bQ0KMzcuOTIwIDI5NS44MDAgbA0KMzYuOTYwIDI5Ni44ODAgbA0KMzMuMTIwIDI5Ny4wMDAgbA0K
MzMuMTIwIDI5OS40MDAgbA0KMzIuNDAwIDMwMC4zNjAgbA0KMzIuNDAwIDI5Ni4xNjAgbA0KZioN
CjAuNTAyIDAuNTAyIDAuNTAyIHJnDQowLjAwMCAwLjAwMCAwLjAwMCBSRw0KMC4yNDAgdw0KWyBd
IDAgZA0KMSBKDQoxIGoNCjM3LjgwMCAzMDAuMDAwIG0NCjMyLjI4MCAzMDAuMzYwIGwNCjMzLjI0
MCAyOTkuNDAwIGwNCjM3LjA4MCAyOTkuMTYwIGwNCjM3LjA4MCAyOTYuODgwIGwNCjM3LjgwMCAy
OTUuODAwIGwNCjM3LjgwMCAzMDAuMDAwIGwNCmYqDQowLjAwMCAwLjAwMCAwLjAwMCByZw0KMC4w
MDAgMC4wMDAgMC4wMDAgUkcNCjAuMjQwIHcNClsgXSAwIGQNCjEgSg0KMSBqDQozMi40MDAgMjg5
LjgwMCBtDQozNy41NjAgMjg5LjU2MCBsDQozNy41NjAgMjkzLjQwMCBsDQozMi40MDAgMjkzLjQw
MCBsDQozMi40MDAgMjg5LjgwMCBsDQpmKg0KMC43NTMgMC43NTMgMC43NTMgcmcNCjAuMDAwIDAu
MDAwIDAuMDAwIFJHDQowLjI0MCB3DQpbIF0gMCBkDQoxIEoNCjEgag0KMzIuNDAwIDI4OS44MDAg
bQ0KMzcuOTIwIDI4OS40NDAgbA0KMzYuOTYwIDI5MC40MDAgbA0KMzMuMTIwIDI5MC42NDAgbA0K
MzMuMTIwIDI5My4wNDAgbA0KMzIuNDAwIDI5NC4wMDAgbA0KMzIuNDAwIDI4OS44MDAgbA0KZioN
CjAuNTAyIDAuNTAyIDAuNTAyIHJnDQowLjAwMCAwLjAwMCAwLjAwMCBSRw0KMC4yNDAgdw0KWyBd
IDAgZA0KMSBKDQoxIGoNCjM3LjgwMCAyOTMuNjQwIG0NCjMyLjI4MCAyOTQuMDAwIGwNCjMzLjI0
MCAyOTMuMDQwIGwNCjM3LjA4MCAyOTIuODAwIGwNCjM3LjA4MCAyOTAuNDAwIGwNCjM3LjgwMCAy
ODkuNDQwIGwNCjM3LjgwMCAyOTMuNjQwIGwNCmYqDQowLjAwMCAwLjAwMCAwLjAwMCByZw0KMC4w
MDAgMC4wMDAgMC4wMDAgUkcNCjAuMjQwIHcNClsgXSAwIGQNCjEgSg0KMSBqDQozMi40MDAgMjgz
LjQ0MCBtDQozNy41NjAgMjgzLjA4MCBsDQozNy41NjAgMjg3LjA0MCBsDQozMi40MDAgMjg3LjA0
MCBsDQozMi40MDAgMjgzLjQ0MCBsDQpmKg0KMC43NTMgMC43NTMgMC43NTMgcmcNCjAuMDAwIDAu
MDAwIDAuMDAwIFJHDQowLjI0MCB3DQpbIF0gMCBkDQoxIEoNCjEgag0KMzIuNDAwIDI4My40NDAg
bQ0KMzcuOTIwIDI4My4wODAgbA0KMzYuOTYwIDI4NC4wNDAgbA0KMzMuMTIwIDI4NC4yODAgbA0K
MzMuMTIwIDI4Ni41NjAgbA0KMzIuNDAwIDI4Ny41MjAgbA0KMzIuNDAwIDI4My40NDAgbA0KZioN
CjAuNTAyIDAuNTAyIDAuNTAyIHJnDQowLjAwMCAwLjAwMCAwLjAwMCBSRw0KMC4yNDAgdw0KWyBd
IDAgZA0KMSBKDQoxIGoNCjM3LjgwMCAyODcuMjgwIG0NCjMyLjI4MCAyODcuNTIwIGwNCjMzLjI0
MCAyODYuNTYwIGwNCjM3LjA4MCAyODYuNDQwIGwNCjM3LjA4MCAyODQuMDQwIGwNCjM3LjgwMCAy
ODMuMDgwIGwNCjM3LjgwMCAyODcuMjgwIGwNCmYqDQowLjAwMCAwLjAwMCAwLjAwMCBSRw0KMC4y
NDAgdw0KWyBdIDAgZA0KMSBKDQoxIGoNCjEwNC4yODAgMzM0LjkyMCBtDQoxMDQuMjgwIDMxNC44
ODAgbA0KUw0KMC4wMDAgMC4wMDAgMC4wMDAgUkcNCjAuMjQwIHcNClsgXSAwIGQNCjEgSg0KMSBq
DQoxMDQuMjgwIDMxNC44ODAgbQ0KMTY0LjI4MCAzMTQuODgwIGwNClMNCjAuMDAwIDAuMDAwIDAu
MDAwIFJHDQowLjI0MCB3DQpbIF0gMCBkDQoxIEoNCjEgag0KMTQ5LjA0MCAzMzQuNjgwIG0NCjE2
NC4yODAgMzE0Ljg4MCBsDQpTDQowLjAwMCAwLjAwMCAwLjAwMCBSRw0KMC4yNDAgdw0KWyBdIDAg
ZA0KMSBKDQoxIGoNCjEwNC4yODAgMzM0LjkyMCBtDQoxNDkuMDQwIDMzNC42ODAgbA0KUw0KMC4w
MDAgMC4wMDAgMC4wMDAgUkcNCjAuMjQwIHcNClsgXSAwIGQNCjEgSg0KMSBqDQowLjg3OCAwLjg3
OCAwLjg3OCByZw0KMjguMjAwIDMwNC44MDAgbQ0KMjguMTk4IDMwNi44ODAgMjUuMzIxIDMwNi44
ODAgMjUuMzIwIDMwNC44MDAgYw0KMjUuMzIyIDMwMi43MjAgMjguMTk4IDMwMi43MjAgMjguMjAw
IDMwNC44MDAgYw0KZioNCjAuMDAwIDAuMDAwIDAuMDAwIFJHDQowLjEyMCB3DQpbIF0gMCBkDQox
IEoNCjEgag0KMC44NzggMC44NzggMC44NzggcmcNCjI4LjQ0MCAyODQuODgwIG0NCjI4LjQzOCAy
ODYuOTYwIDI1LjU2MSAyODYuOTYwIDI1LjU2MCAyODQuODgwIGMNCjI1LjU2MiAyODIuODAwIDI4
LjQzOCAyODIuODAwIDI4LjQ0MCAyODQuODgwIGMNCmYqDQowLjAwMCAwLjAwMCAwLjAwMCBSRw0K
MC4xMjAgdw0KWyBdIDAgZA0KMSBKDQoxIGoNCjAuODc4IDAuODc4IDAuODc4IHJnDQoxODAuMDAw
IDMwNS43NjAgbQ0KMTc5Ljk5OCAzMDcuNjgwIDE3Ny4xMjIgMzA3LjY4MCAxNzcuMTIwIDMwNS43
NjAgYw0KMTc3LjEyMSAzMDMuODQwIDE3OS45OTggMzAzLjg0MCAxODAuMDAwIDMwNS43NjAgYw0K
ZioNCjAuMDAwIDAuMDAwIDAuMDAwIFJHDQowLjEyMCB3DQpbIF0gMCBkDQoxIEoNCjEgag0KMC44
NzggMC44NzggMC44NzggcmcNCjE3OS42NDAgMjgzLjQ0MCBtDQoxNzkuNjM4IDI4NS41MjAgMTc2
Ljc2MSAyODUuNTIwIDE3Ni43NjAgMjgzLjQ0MCBjDQoxNzYuNzYyIDI4MS4zNjAgMTc5LjYzOCAy
ODEuMzYwIDE3OS42NDAgMjgzLjQ0MCBjDQpmKg0KMC41MDIgMC41MDIgMC41MDIgcmcNCjAuMDAw
IDAuMDAwIDAuMDAwIFJHDQowLjEyMCB3DQpbIF0gMCBkDQoxIEoNCjEgag0KMTAyLjAwMCAzMDQu
OTIwIG0NCjEwMC44MDAgMzAzLjQ4MCBsDQoxMDAuODAwIDI3OC4yODAgbA0KMTAyLjAwMCAyNzcu
MDgwIGwNCjEwMi4wMDAgMzA0LjY4MCBsDQpmKg0KMC44NzggMC44NzggMC44NzggcmcNCjAuMDAw
IDAuMDAwIDAuMDAwIFJHDQowLjEyMCB3DQpbIF0gMCBkDQoxIEoNCjEgag0KMTAxLjc2MCAzMDQu
ODAwIG0NCjEwMi45NjAgMzAzLjM2MCBsDQoxMDIuOTYwIDI3OC4xNjAgbA0KMTAxLjc2MCAyNzYu
OTYwIGwNCjEwMS43NjAgMzA0LjU2MCBsDQpmKg0KMC4wMDAgMC4wMDAgMC4wMDAgcmcNCjAuMDAw
IDAuMDAwIDAuMDAwIFJHDQowLjI0MCB3DQpbIF0gMCBkDQoxIEoNCjEgag0KOTIuNzYwIDI5Ny42
MDAgbQ0KOTIuODgwIDI5Ny42MDAgbA0KOTMuMDAwIDI5Ny42MDAgbA0KOTMuMTIwIDI5Ny42MDAg
bA0KOTMuMjQwIDI5Ny42MDAgbA0KOTMuMzYwIDI5Ny42MDAgbA0KOTMuNDgwIDI5Ny42MDAgbA0K
OTMuNjAwIDI5Ny40ODAgbA0KOTMuNzIwIDI5Ny40ODAgbA0KOTMuODQwIDI5Ny40ODAgbA0KOTMu
OTYwIDI5Ny40ODAgbA0KOTQuMDgwIDI5Ny40ODAgbA0KOTQuMjAwIDI5Ny40ODAgbA0KOTQuMzIw
IDI5Ny40ODAgbA0KOTQuNDQwIDI5Ny40ODAgbA0KOTQuNTYwIDI5Ny40ODAgbA0KOTQuNjgwIDI5
Ny40ODAgbA0KOTQuNjgwIDI5Ny4zNjAgbA0KOTQuODAwIDI5Ny4zNjAgbA0KOTQuOTIwIDI5Ny4z
NjAgbA0KOTUuMDQwIDI5Ny4zNjAgbA0KOTUuMTYwIDI5Ny4zNjAgbA0KOTUuMjgwIDI5Ny4zNjAg
bA0KOTUuNDAwIDI5Ny4zNjAgbA0KOTUuNTIwIDI5Ny4zNjAgbA0KOTUuNjQwIDI5Ny4zNjAgbA0K
OTUuNzYwIDI5Ny4zNjAgbA0KOTUuODgwIDI5Ny4zNjAgbA0KOTYuMDAwIDI5Ny4zNjAgbA0KOTYu
MTIwIDI5Ny4zNjAgbA0KOTYuMjQwIDI5Ny4zNjAgbA0KOTYuMzYwIDI5Ny4zNjAgbA0KOTYuNDgw
IDI5Ny4zNjAgbA0KOTYuNjAwIDI5Ny4zNjAgbA0KOTYuNzIwIDI5Ny4zNjAgbA0KOTYuODQwIDI5
Ny4zNjAgbA0KOTYuOTYwIDI5Ny4zNjAgbA0KOTcuMDgwIDI5Ny4zNjAgbA0KOTcuMjAwIDI5Ny4z
NjAgbA0KOTcuMjAwIDI5Ny4yNDAgbA0KOTcuMzIwIDI5Ny4yNDAgbA0KOTcuNDQwIDI5Ny4yNDAg
bA0KOTcuNTYwIDI5Ny4yNDAgbA0KOTcuNjgwIDI5Ny4yNDAgbA0KOTcuODAwIDI5Ny4yNDAgbA0K
OTcuOTIwIDI5Ny4yNDAgbA0KOTguMDQwIDI5Ny4yNDAgbA0KOTguMTYwIDI5Ny4yNDAgbA0KOTgu
MjgwIDI5Ny4yNDAgbA0KOTguNDAwIDI5Ny4yNDAgbA0KOTguNjQwIDI5Ny4yNDAgbA0KOTguODgw
IDI5Ny4yNDAgbA0KOTkuMDAwIDI5Ny4yNDAgbA0KOTkuMTIwIDI5Ny4yNDAgbA0KOTkuMjQwIDI5
Ny4yNDAgbA0KOTkuNDgwIDI5Ny4yNDAgbA0KOTkuNjAwIDI5Ny4yNDAgbA0KOTkuODQwIDI5Ny4x
MjAgbA0KMTAwLjA4MCAyOTcuMTIwIGwNCjEwMC4zMjAgMjk3LjEyMCBsDQoxMDAuNTYwIDI5Ny4x
MjAgbA0KMTAwLjkyMCAyOTcuMTIwIGwNCjEwMS44ODAgMjk3LjEyMCBsDQoxMDIuNzIwIDI5Ny4x
MjAgbA0KMTAzLjA4MCAyOTcuMTIwIGwNCjEwMy40NDAgMjk3LjEyMCBsDQoxMDMuNjgwIDI5Ny4x
MjAgbA0KMTAzLjkyMCAyOTcuMTIwIGwNCjEwNC4wNDAgMjk3LjI0MCBsDQoxMDQuMjgwIDI5Ny4y
NDAgbA0KMTA0LjQwMCAyOTcuMjQwIGwNCjEwNC41MjAgMjk3LjI0MCBsDQoxMDQuNzYwIDI5Ny4y
NDAgbA0KMTA0Ljg4MCAyOTcuMjQwIGwNCjEwNS4wMDAgMjk3LjI0MCBsDQoxMDUuMTIwIDI5Ny4y
NDAgbA0KMTA1LjI0MCAyOTcuMjQwIGwNCjEwNS4zNjAgMjk3LjI0MCBsDQoxMDUuNDgwIDI5Ny4y
NDAgbA0KMTA1LjYwMCAyOTcuMjQwIGwNCjEwNS43MjAgMjk3LjI0MCBsDQoxMDUuODQwIDI5Ny4y
NDAgbA0KMTA1Ljk2MCAyOTcuMjQwIGwNCjEwNi4wODAgMjk3LjI0MCBsDQoxMDYuMjAwIDI5Ny4y
NDAgbA0KMTA2LjMyMCAyOTcuMjQwIGwNCjEwNi40NDAgMjk3LjI0MCBsDQoxMDYuNTYwIDI5Ny4z
NjAgbA0KMTA2LjY4MCAyOTcuMzYwIGwNCjEwNi44MDAgMjk3LjM2MCBsDQoxMDYuOTIwIDI5Ny4z
NjAgbA0KMTA3LjA0MCAyOTcuMzYwIGwNCjEwNy4xNjAgMjk3LjM2MCBsDQoxMDcuMjgwIDI5Ny4z
NjAgbA0KMTA3LjQwMCAyOTcuMzYwIGwNCjEwNy41MjAgMjk3LjM2MCBsDQoxMDcuNjQwIDI5Ny4z
NjAgbA0KMTA3Ljc2MCAyOTcuMzYwIGwNCjEwNy44ODAgMjk3LjM2MCBsDQoxMDguMDAwIDI5Ny4z
NjAgbA0KMTA4LjEyMCAyOTcuMzYwIGwNCjEwOC4yNDAgMjk3LjM2MCBsDQoxMDguMzYwIDI5Ny4z
NjAgbA0KMTA4LjQ4MCAyOTcuMzYwIGwNCjEwOC42MDAgMjk3LjM2MCBsDQoxMDguNzIwIDI5Ny4z
NjAgbA0KMTA4Ljg0MCAyOTcuMzYwIGwNCjEwOC45NjAgMjk3LjM2MCBsDQoxMDkuMDgwIDI5Ny40
ODAgbA0KMTA5LjIwMCAyOTcuNDgwIGwNCjEwOS4zMjAgMjk3LjQ4MCBsDQoxMDkuNDQwIDI5Ny40
ODAgbA0KMTA5LjU2MCAyOTcuNDgwIGwNCjEwOS42ODAgMjk3LjQ4MCBsDQoxMDkuODAwIDI5Ny40
ODAgbA0KMTA5LjkyMCAyOTcuNDgwIGwNCjExMC4wNDAgMjk3LjQ4MCBsDQoxMTAuMTYwIDI5Ny40
ODAgbA0KMTEwLjE2MCAyOTcuNjAwIGwNCjExMC4yODAgMjk3LjYwMCBsDQoxMTAuNDAwIDI5Ny42
MDAgbA0KMTEwLjUyMCAyOTcuNjAwIGwNCjExMC42NDAgMjk3LjYwMCBsDQoxMTAuNzYwIDI5Ny42
MDAgbA0KMTEwLjg4MCAyOTcuNjAwIGwNCjExMC44ODAgMjg0Ljc2MCBsDQoxMTAuNzYwIDI4NC43
NjAgbA0KMTEwLjY0MCAyODQuNzYwIGwNCjExMC41MjAgMjg0Ljc2MCBsDQoxMTAuNDAwIDI4NC43
NjAgbA0KMTEwLjI4MCAyODQuNzYwIGwNCjExMC4xNjAgMjg0Ljc2MCBsDQoxMTAuMDQwIDI4NC43
NjAgbA0KMTA5LjkyMCAyODQuNzYwIGwNCjEwOS44MDAgMjg0Ljc2MCBsDQoxMDkuNjgwIDI4NC42
NDAgbA0KMTA5LjU2MCAyODQuNjQwIGwNCjEwOS40NDAgMjg0LjY0MCBsDQoxMDkuMzIwIDI4NC42
NDAgbA0KMTA5LjIwMCAyODQuNjQwIGwNCjEwOS4wODAgMjg0LjY0MCBsDQoxMDguOTYwIDI4NC42
NDAgbA0KMTA4Ljg0MCAyODQuNjQwIGwNCjEwOC43MjAgMjg0LjY0MCBsDQoxMDguNjAwIDI4NC42
NDAgbA0KMTA4LjQ4MCAyODQuNjQwIGwNCjEwOC4zNjAgMjg0LjY0MCBsDQoxMDguMjQwIDI4NC42
NDAgbA0KMTA4LjEyMCAyODQuNjQwIGwNCjEwOC4wMDAgMjg0LjUyMCBsDQoxMDcuODgwIDI4NC41
MjAgbA0KMTA3Ljc2MCAyODQuNTIwIGwNCjEwNy42NDAgMjg0LjUyMCBsDQoxMDcuNTIwIDI4NC41
MjAgbA0KMTA3LjQwMCAyODQuNTIwIGwNCjEwNy4yODAgMjg0LjUyMCBsDQoxMDcuMTYwIDI4NC41
MjAgbA0KMTA3LjA0MCAyODQuNTIwIGwNCjEwNi45MjAgMjg0LjUyMCBsDQoxMDYuODAwIDI4NC41
MjAgbA0KMTA2LjY4MCAyODQuNTIwIGwNCjEwNi41NjAgMjg0LjUyMCBsDQoxMDYuNDQwIDI4NC41
MjAgbA0KMTA2LjMyMCAyODQuNTIwIGwNCjEwNi4yMDAgMjg0LjUyMCBsDQoxMDYuMDgwIDI4NC41
MjAgbA0KMTA1Ljk2MCAyODQuNTIwIGwNCjEwNS44NDAgMjg0LjUyMCBsDQoxMDUuNzIwIDI4NC41
MjAgbA0KMTA1LjYwMCAyODQuNTIwIGwNCjEwNS40ODAgMjg0LjUyMCBsDQoxMDUuMzYwIDI4NC41
MjAgbA0KMTA1LjI0MCAyODQuNTIwIGwNCjEwNS4xMjAgMjg0LjUyMCBsDQoxMDUuMDAwIDI4NC41
MjAgbA0KMTA0Ljg4MCAyODQuNDAwIGwNCjEwNC43NjAgMjg0LjQwMCBsDQoxMDQuNTIwIDI4NC40
MDAgbA0KMTA0LjQwMCAyODQuNDAwIGwNCjEwNC4yODAgMjg0LjQwMCBsDQoxMDQuMDQwIDI4NC40
MDAgbA0KMTAzLjkyMCAyODQuNDAwIGwNCjEwMy42ODAgMjg0LjQwMCBsDQoxMDMuNDQwIDI4NC40
MDAgbA0KMTAzLjA4MCAyODQuNDAwIGwNCjEwMi43MjAgMjg0LjQwMCBsDQoxMDEuODgwIDI4NC40
MDAgbA0KMTAwLjkyMCAyODQuNDAwIGwNCjEwMC41NjAgMjg0LjQwMCBsDQoxMDAuMzIwIDI4NC40
MDAgbA0KMTAwLjA4MCAyODQuNDAwIGwNCjk5Ljg0MCAyODQuNDAwIGwNCjk5LjYwMCAyODQuNDAw
IGwNCjk5LjQ4MCAyODQuNDAwIGwNCjk5LjI0MCAyODQuNDAwIGwNCjk5LjEyMCAyODQuNDAwIGwN
Cjk5LjAwMCAyODQuNDAwIGwNCjk4Ljg4MCAyODQuNDAwIGwNCjk4LjY0MCAyODQuNTIwIGwNCjk4
LjQwMCAyODQuNTIwIGwNCjk4LjI4MCAyODQuNTIwIGwNCjk4LjE2MCAyODQuNTIwIGwNCjk4LjA0
MCAyODQuNTIwIGwNCjk3LjkyMCAyODQuNTIwIGwNCjk3LjgwMCAyODQuNTIwIGwNCjk3LjY4MCAy
ODQuNTIwIGwNCjk3LjU2MCAyODQuNTIwIGwNCjk3LjQ0MCAyODQuNTIwIGwNCjk3LjMyMCAyODQu
NTIwIGwNCjk3LjIwMCAyODQuNTIwIGwNCjk3LjA4MCAyODQuNTIwIGwNCjk2Ljk2MCAyODQuNTIw
IGwNCjk2Ljg0MCAyODQuNTIwIGwNCjk2LjcyMCAyODQuNTIwIGwNCjk2LjYwMCAyODQuNTIwIGwN
Cjk2LjQ4MCAyODQuNTIwIGwNCjk2LjM2MCAyODQuNTIwIGwNCjk2LjI0MCAyODQuNTIwIGwNCjk2
LjEyMCAyODQuNTIwIGwNCjk2LjAwMCAyODQuNTIwIGwNCjk1Ljg4MCAyODQuNTIwIGwNCjk1Ljc2
MCAyODQuNTIwIGwNCjk1LjY0MCAyODQuNTIwIGwNCjk1LjY0MCAyODQuNjQwIGwNCjk1LjUyMCAy
ODQuNjQwIGwNCjk1LjQwMCAyODQuNjQwIGwNCjk1LjI4MCAyODQuNjQwIGwNCjk1LjE2MCAyODQu
NjQwIGwNCjk1LjA0MCAyODQuNjQwIGwNCjk0LjkyMCAyODQuNjQwIGwNCjk0LjgwMCAyODQuNjQw
IGwNCjk0LjY4MCAyODQuNjQwIGwNCjk0LjU2MCAyODQuNjQwIGwNCjk0LjQ0MCAyODQuNjQwIGwN
Cjk0LjMyMCAyODQuNjQwIGwNCjk0LjIwMCAyODQuNjQwIGwNCjk0LjA4MCAyODQuNjQwIGwNCjkz
Ljk2MCAyODQuNjQwIGwNCjkzLjk2MCAyODQuNzYwIGwNCjkzLjg0MCAyODQuNzYwIGwNCjkzLjcy
MCAyODQuNzYwIGwNCjkzLjYwMCAyODQuNzYwIGwNCjkzLjQ4MCAyODQuNzYwIGwNCjkzLjM2MCAy
ODQuNzYwIGwNCjkzLjI0MCAyODQuNzYwIGwNCjkzLjEyMCAyODQuNzYwIGwNCjkzLjAwMCAyODQu
NzYwIGwNCjkyLjg4MCAyODQuNzYwIGwNCjkyLjc2MCAyODQuNzYwIGwNCjkyLjc2MCAyOTcuNDgw
IGwNCmIqDQowLjAwMCAwLjAwMCAwLjAwMCByZw0KMC4wMDAgMC4wMDAgMC4wMDAgUkcNCjAuMjQw
IHcNClsgXSAwIGQNCjEgSg0KMSBqDQo5My44NDAgMjkwLjE2MCAxNi41NjAgNy4wODAgcmUNCm4N
CkJUDQoxLjAwMCAwLjAwMCAwLjAwMCAxLjAwMCA5NC42ODAgMjkxLjk2MCBUbQ0KL0YyIDQuNzg3
IFRmDQowIFRyDQowLjg3OCAwLjg3OCAwLjg3OCByZw0KMC4wMDAgVGMNCjEyMi4xODUgVHoNCihE
RUxMKVRqDQpFVA0KMC4wMDAgMC4wMDAgMC4wMDAgcmcNCjAuMDAwIDAuMDAwIDAuMDAwIFJHDQow
LjI0MCB3DQpbIF0gMCBkDQoxIEoNCjEgag0KOTMuNzIwIDI4NC42NDAgMTYuODAwIDYuOTYwIHJl
DQpuDQpCVA0KMS4wMDAgMC4wMDAgMC4wMDAgMS4wMDAgOTMuNzIwIDI4OS4wODAgVG0NCi9GMyAy
LjMxMSBUZg0KMCBUcg0KMC44NzggMC44NzggMC44NzggcmcNCjAuMDAwIFRjDQoxMDYuMDY2IFR6
DQooUE9XRVJFREdFKVRqDQpFVA0KQlQNCjEuMDAwIDAuMDAwIDAuMDAwIDEuMDAwIDk3LjgwMCAy
ODUuNjAwIFRtDQovRjMgMi4zMTEgVGYNCjAgVHINCjAuODc4IDAuODc4IDAuODc4IHJnDQowLjAw
MCBUYw0KMTIyLjkzOSBUeg0KKDI0NTBSKVRqDQpFVA0KMC42MjcgMC42MjcgMC42NDMgUkcNCjAu
MjQwIHcNClsgXSAwIGQNCjEgSg0KMSBqDQozMi41MjAgMzEwLjMyMCBtDQo1Ny4yNDAgMzM5LjEy
MCBsDQpTDQowLjYyNyAwLjYyNyAwLjY0MyBSRw0KMC4yNDAgdw0KWyBdIDAgZA0KMSBKDQoxIGoN
CjE0OC40NDAgMzM4Ljc2MCBtDQoxNzMuMTYwIDMwOS45NjAgbA0KUw0KMC42MjcgMC42MjcgMC42
NDMgUkcNCjAuMjQwIHcNClsgXSAwIGQNCjEgSg0KMSBqDQoxMDEuNTIwIDMzOS4xMjAgbQ0KMTAx
LjUyMCAzMDYuNjAwIGwNClMNCjAuMDAwIDAuMDAwIDAuMDAwIHJnDQowLjYyNyAwLjYyNyAwLjY0
MyBSRw0KMC4yNDAgdw0KWyBdIDAgZA0KMSBKDQoxIGoNCjIzLjY0MCAyNzYuMTIwIDE1OC4yODAg
NjMuOTYwIHJlDQpuDQowLjg5NCAwLjc5MiAwLjY5NCByZw0KMC42MjcgMC42MjcgMC42NDMgUkcN
CjAuMjQwIHcNClsgXSAwIGQNCjEgSg0KMSBqDQozNDcuNzYwIDM1MC4wNDAgbQ0KMzA0LjIwMCAz
NTAuMDQwIGwNCjMwNC4yMDAgNDA3LjE2MCBsDQozMDQuMjAwIDQwNy4yODAgbA0KMzA0LjIwMCA0
MDcuNDAwIGwNCjMwNC4yMDAgNDA3LjUyMCBsDQozMDQuMDgwIDQwNy43NjAgbA0KMzA0LjA4MCA0
MDguMDAwIGwNCjMwNC4wODAgNDA4LjI0MCBsDQozMDMuOTYwIDQwOC42MDAgbA0KMzAzLjk2MCA0
MDguOTYwIGwNCjMwMy45NjAgNDA5LjQ0MCBsDQozMDMuODQwIDQwOS44MDAgbA0KMzAzLjg0MCA0
MTAuMjgwIGwNCjMwMy43MjAgNDEwLjY0MCBsDQozMDMuNzIwIDQxMS4xMjAgbA0KMzAzLjcyMCA0
MTEuNDgwIGwNCjMwMy42MDAgNDExLjk2MCBsDQozMDMuNjAwIDQxMi4zMjAgbA0KMzAzLjYwMCA0
MTIuNjgwIGwNCjMwMy42MDAgNDEzLjA0MCBsDQozMDMuNjAwIDQxMy40MDAgbA0KMzAzLjYwMCA0
MTMuNzYwIGwNCjMwMy42MDAgNDE0LjEyMCBsDQozMDMuNjAwIDQxNC40ODAgbA0KMzAzLjcyMCA0
MTQuOTYwIGwNCjMwMy43MjAgNDE1LjMyMCBsDQozMDMuNzIwIDQxNS44MDAgbA0KMzAzLjg0MCA0
MTYuMTYwIGwNCjMwMy44NDAgNDE2LjY0MCBsDQozMDMuOTYwIDQxNy4wMDAgbA0KMzAzLjk2MCA0
MTcuMzYwIGwNCjMwNC4wODAgNDE3LjcyMCBsDQozMDQuMDgwIDQxNy45NjAgbA0KMzA0LjA4MCA0
MTguMjAwIGwNCjMwNC4yMDAgNDE4LjMyMCBsDQozMDQuMjAwIDQxOC40NDAgbA0KMzA0LjIwMCA0
MTguNTYwIGwNCjM0Ny43NjAgNDE4LjU2MCBsDQozNDcuNzYwIDQxOC40NDAgbA0KMzQ3Ljc2MCA0
MTguMzIwIGwNCjM0Ny43NjAgNDE4LjIwMCBsDQozNDcuNzYwIDQxNy45NjAgbA0KMzQ3Ljg4MCA0
MTcuNjAwIGwNCjM0Ny44ODAgNDE3LjI0MCBsDQozNDcuODgwIDQxNi44ODAgbA0KMzQ4LjAwMCA0
MTYuNTIwIGwNCjM0OC4wMDAgNDE2LjE2MCBsDQozNDguMDAwIDQxNS42ODAgbA0KMzQ4LjAwMCA0
MTUuMzIwIGwNCjM0OC4xMjAgNDE0Ljg0MCBsDQozNDguMTIwIDQxNC40ODAgbA0KMzQ4LjEyMCA0
MTQuMDAwIGwNCjM0OC4xMjAgNDEzLjY0MCBsDQozNDguMTIwIDQxMy40MDAgbA0KMzQ4LjEyMCA0
MTMuMDQwIGwNCjM0OC4xMjAgNDEyLjY4MCBsDQozNDguMTIwIDQxMi4zMjAgbA0KMzQ4LjEyMCA0
MTEuOTYwIGwNCjM0OC4xMjAgNDExLjQ4MCBsDQozNDguMDAwIDQxMS4xMjAgbA0KMzQ4LjAwMCA0
MTAuNjQwIGwNCjM0OC4wMDAgNDEwLjE2MCBsDQozNDguMDAwIDQwOS44MDAgbA0KMzQ3Ljg4MCA0
MDkuMzIwIGwNCjM0Ny44ODAgNDA4Ljk2MCBsDQozNDcuODgwIDQwOC42MDAgbA0KMzQ3Ljc2MCA0
MDguMjQwIGwNCjM0Ny43NjAgNDA4LjAwMCBsDQozNDcuNzYwIDQwNy43NjAgbA0KMzQ3Ljc2MCA0
MDcuNTIwIGwNCjM0Ny43NjAgNDA3LjQwMCBsDQozNDcuNzYwIDM1MC4wNDAgbA0KZioNCjAuMDAw
IDAuMDAwIDAuMDAwIFJHDQowLjk2MCB3DQpbIF0gMCBkDQoxIEoNCjEgag0KMzQ3Ljc2MCAzNTAu
MDQwIG0NCjMwNC4yMDAgMzUwLjA0MCBsDQozMDQuMjAwIDQwNy4xNjAgbA0KMzA0LjIwMCA0MDcu
MjgwIGwNCjMwNC4yMDAgNDA3LjQwMCBsDQozMDQuMjAwIDQwNy41MjAgbA0KMzA0LjA4MCA0MDcu
NzYwIGwNCjMwNC4wODAgNDA4LjAwMCBsDQozMDQuMDgwIDQwOC4yNDAgbA0KMzAzLjk2MCA0MDgu
NjAwIGwNCjMwMy45NjAgNDA4Ljk2MCBsDQozMDMuOTYwIDQwOS40NDAgbA0KMzAzLjg0MCA0MDku
ODAwIGwNCjMwMy44NDAgNDEwLjI4MCBsDQozMDMuNzIwIDQxMC42NDAgbA0KMzAzLjcyMCA0MTEu
MTIwIGwNCjMwMy43MjAgNDExLjQ4MCBsDQozMDMuNjAwIDQxMS45NjAgbA0KMzAzLjYwMCA0MTIu
MzIwIGwNCjMwMy42MDAgNDEyLjY4MCBsDQozMDMuNjAwIDQxMy4wNDAgbA0KMzAzLjYwMCA0MTMu
NDAwIGwNCjMwMy42MDAgNDEzLjc2MCBsDQozMDMuNjAwIDQxNC4xMjAgbA0KMzAzLjYwMCA0MTQu
NDgwIGwNCjMwMy43MjAgNDE0Ljk2MCBsDQozMDMuNzIwIDQxNS4zMjAgbA0KMzAzLjcyMCA0MTUu
ODAwIGwNCjMwMy44NDAgNDE2LjE2MCBsDQozMDMuODQwIDQxNi42NDAgbA0KMzAzLjk2MCA0MTcu
MDAwIGwNCjMwMy45NjAgNDE3LjM2MCBsDQozMDQuMDgwIDQxNy43MjAgbA0KMzA0LjA4MCA0MTcu
OTYwIGwNCjMwNC4wODAgNDE4LjIwMCBsDQozMDQuMjAwIDQxOC4zMjAgbA0KMzA0LjIwMCA0MTgu
NDQwIGwNCjMwNC4yMDAgNDE4LjU2MCBsDQozNDcuNzYwIDQxOC41NjAgbA0KMzQ3Ljc2MCA0MTgu
NDQwIGwNCjM0Ny43NjAgNDE4LjMyMCBsDQozNDcuNzYwIDQxOC4yMDAgbA0KMzQ3Ljc2MCA0MTcu
OTYwIGwNCjM0Ny44ODAgNDE3LjYwMCBsDQozNDcuODgwIDQxNy4yNDAgbA0KMzQ3Ljg4MCA0MTYu
ODgwIGwNCjM0OC4wMDAgNDE2LjUyMCBsDQozNDguMDAwIDQxNi4xNjAgbA0KMzQ4LjAwMCA0MTUu
NjgwIGwNCjM0OC4wMDAgNDE1LjMyMCBsDQozNDguMTIwIDQxNC44NDAgbA0KMzQ4LjEyMCA0MTQu
NDgwIGwNCjM0OC4xMjAgNDE0LjAwMCBsDQozNDguMTIwIDQxMy42NDAgbA0KMzQ4LjEyMCA0MTMu
NDAwIGwNCjM0OC4xMjAgNDEzLjA0MCBsDQozNDguMTIwIDQxMi42ODAgbA0KMzQ4LjEyMCA0MTIu
MzIwIGwNCjM0OC4xMjAgNDExLjk2MCBsDQozNDguMTIwIDQxMS40ODAgbA0KMzQ4LjAwMCA0MTEu
MTIwIGwNCjM0OC4wMDAgNDEwLjY0MCBsDQozNDguMDAwIDQxMC4xNjAgbA0KMzQ4LjAwMCA0MDku
ODAwIGwNCjM0Ny44ODAgNDA5LjMyMCBsDQozNDcuODgwIDQwOC45NjAgbA0KMzQ3Ljg4MCA0MDgu
NjAwIGwNCjM0Ny43NjAgNDA4LjI0MCBsDQozNDcuNzYwIDQwOC4wMDAgbA0KMzQ3Ljc2MCA0MDcu
NzYwIGwNCjM0Ny43NjAgNDA3LjUyMCBsDQozNDcuNzYwIDQwNy40MDAgbA0KMzQ3Ljc2MCAzNTAu
MDQwIGwNClMNCjAuMDAwIDAuNDk4IDAuNDk4IHJnDQowLjAwMCAwLjAwMCAwLjAwMCBSRw0KMC45
NjAgdw0KWyBdIDAgZA0KMSBKDQoxIGoNCjM0MS4xNjAgNDI0LjY4MCBtDQozMTAuODAwIDQyNC42
ODAgbA0KMzA0LjIwMCA0MTguNTYwIGwNCjM0Ny43NjAgNDE4LjU2MCBsDQozNDEuMTYwIDQyNC42
ODAgbA0KZioNCjAuMDAwIDAuMDAwIDAuMDAwIFJHDQowLjk2MCB3DQpbIF0gMCBkDQoxIEoNCjEg
ag0KMzQxLjE2MCA0MjQuNjgwIG0NCjMxMC44MDAgNDI0LjY4MCBsDQozMDQuMjAwIDQxOC41NjAg
bA0KMzQ3Ljc2MCA0MTguNTYwIGwNCjM0MS4xNjAgNDI0LjY4MCBsDQpTDQowLjgwMCAwLjAwMCAw
LjAwMCByZw0KMC4wMDAgMC4wMDAgMC4wMDAgUkcNCjAuOTYwIHcNClsgXSAwIGQNCjEgSg0KMSBq
DQozMDYuNzIwIDQxNi40MDAgbQ0KMzA2LjQ4MCA0MTYuNDAwIGwNCjMwNi40ODAgNDE2LjI4MCBs
DQozMDYuNDgwIDQxNi4xNjAgbA0KMzA2LjM2MCA0MTYuMTYwIGwNCjMwNi4zNjAgNDE2LjI4MCBs
DQozMDYuMzYwIDQxNi41MjAgbA0KMzA2LjM2MCA0MTYuNjQwIGwNCjMwNi4zNjAgNDE2Ljc2MCBs
DQozMDYuNDgwIDQxNi43NjAgbA0KMzA2LjQ4MCA0MTYuNjQwIGwNCjMwNi43MjAgNDE2LjY0MCBs
DQozMDYuNjAwIDQxNi43NjAgbA0KMzA2LjYwMCA0MTYuODgwIGwNCjMwNi40ODAgNDE2Ljg4MCBs
DQozMDYuMjQwIDQxNi44ODAgbA0KMzA2LjI0MCA0MTYuNzYwIGwNCjMwNi4xMjAgNDE2LjUyMCBs
DQozMDYuMTIwIDQxNi40MDAgbA0KMzA2LjEyMCA0MTYuMTYwIGwNCjMwNi4yNDAgNDE2LjA0MCBs
DQozMDYuNDgwIDQxNi4wNDAgbA0KMzA2LjYwMCA0MTYuMDQwIGwNCjMwNi42MDAgNDE2LjE2MCBs
DQozMDYuNzIwIDQxNi4yODAgbA0KMzA2LjcyMCA0MTYuNDAwIGwNCmYqDQowLjgwMCAwLjAwMCAw
LjAwMCByZw0KMC4wMDAgMC4wMDAgMC4wMDAgUkcNCjAuOTYwIHcNClsgXSAwIGQNCjEgSg0KMSBq
DQozMDYuOTYwIDQxNi4wNDAgbQ0KMzA3LjA4MCA0MTYuMDQwIGwNCjMwNy4wODAgNDE2LjY0MCBs
DQozMDYuOTYwIDQxNi42NDAgbA0KMzA2Ljk2MCA0MTYuMDQwIGwNCmYqDQowLjgwMCAwLjAwMCAw
LjAwMCByZw0KMC4wMDAgMC4wMDAgMC4wMDAgUkcNCjAuOTYwIHcNClsgXSAwIGQNCjEgSg0KMSBq
DQozMDcuNjgwIDQxNi41MjAgbQ0KMzA3LjgwMCA0MTYuNTIwIGwNCjMwNy42ODAgNDE2LjY0MCBs
DQozMDcuNTYwIDQxNi42NDAgbA0KMzA3LjQ0MCA0MTYuNjQwIGwNCjMwNy40NDAgNDE2LjUyMCBs
DQozMDcuNDQwIDQxNi40MDAgbA0KMzA3LjU2MCA0MTYuMjgwIGwNCjMwNy42ODAgNDE2LjI4MCBs
DQozMDcuNjgwIDQxNi4xNjAgbA0KMzA3LjU2MCA0MTYuMTYwIGwNCjMwNy41NjAgNDE2LjI4MCBs
DQozMDcuNDQwIDQxNi4yODAgbA0KMzA3LjQ0MCA0MTYuMTYwIGwNCjMwNy40NDAgNDE2LjA0MCBs
DQozMDcuNTYwIDQxNi4wNDAgbA0KMzA3LjY4MCA0MTYuMDQwIGwNCjMwNy44MDAgNDE2LjE2MCBs
DQozMDcuODAwIDQxNi4yODAgbA0KMzA3LjY4MCA0MTYuMjgwIGwNCjMwNy42ODAgNDE2LjQwMCBs
DQozMDcuNTYwIDQxNi40MDAgbA0KMzA3LjU2MCA0MTYuNTIwIGwNCjMwNy41NjAgNDE2LjY0MCBs
DQozMDcuNjgwIDQxNi41MjAgbA0KZioNCjAuODAwIDAuMDAwIDAuMDAwIHJnDQowLjAwMCAwLjAw
MCAwLjAwMCBSRw0KMC45NjAgdw0KWyBdIDAgZA0KMSBKDQoxIGoNCjMwOC40MDAgNDE2LjI4MCBt
DQozMDguMjgwIDQxNi4yODAgbA0KMzA4LjI4MCA0MTYuMTYwIGwNCjMwOC4xNjAgNDE2LjE2MCBs
DQozMDguMTYwIDQxNi4yODAgbA0KMzA4LjE2MCA0MTYuNDAwIGwNCjMwOC4xNjAgNDE2LjUyMCBs
DQozMDguMjgwIDQxNi42NDAgbA0KMzA4LjI4MCA0MTYuNTIwIGwNCjMwOC40MDAgNDE2LjUyMCBs
DQozMDguNDAwIDQxNi42NDAgbA0KMzA4LjI4MCA0MTYuNjQwIGwNCjMwOC4wNDAgNDE2LjY0MCBs
DQozMDguMDQwIDQxNi41MjAgbA0KMzA4LjA0MCA0MTYuNDAwIGwNCjMwOC4wNDAgNDE2LjI4MCBs
DQozMDguMDQwIDQxNi4xNjAgbA0KMzA4LjA0MCA0MTYuMDQwIGwNCjMwOC4yODAgNDE2LjA0MCBs
DQozMDguNDAwIDQxNi4xNjAgbA0KMzA4LjQwMCA0MTYuMjgwIGwNCmYqDQowLjAwMCAwLjAwMCAw
LjAwMCBSRw0KMC45NjAgdw0KWyBdIDAgZA0KMSBKDQoxIGoNCjAuODAwIDAuMDAwIDAuMDAwIHJn
DQozMDguNzYwIDQxNi4yODAgbQ0KMzA4Ljc2MCA0MTYuNDAwIGwNCjMwOC43NjAgNDE2LjUyMCBs
DQozMDguODgwIDQxNi42NDAgbA0KMzA4Ljg4MCA0MTYuNTIwIGwNCjMwOC44ODAgNDE2LjQwMCBs
DQozMDguODgwIDQxNi4yODAgbA0KMzA4Ljg4MCA0MTYuMTYwIGwNCjMwOC43NjAgNDE2LjE2MCBs
DQozMDguNzYwIDQxNi4yODAgbA0KaA0KMzA4LjY0MCA0MTYuNDAwIG0NCjMwOC42NDAgNDE2LjI4
MCBsDQozMDguNjQwIDQxNi4xNjAgbA0KMzA4Ljc2MCA0MTYuMDQwIGwNCjMwOC44ODAgNDE2LjA0
MCBsDQozMDkuMDAwIDQxNi4wNDAgbA0KMzA5LjAwMCA0MTYuMTYwIGwNCjMwOS4wMDAgNDE2LjI4
MCBsDQozMDkuMDAwIDQxNi40MDAgbA0KMzA5LjAwMCA0MTYuNTIwIGwNCjMwOS4wMDAgNDE2LjY0
MCBsDQozMDguODgwIDQxNi42NDAgbA0KMzA4Ljc2MCA0MTYuNjQwIGwNCjMwOC42NDAgNDE2LjUy
MCBsDQozMDguNjQwIDQxNi40MDAgbA0KZioNCjAuODAwIDAuMDAwIDAuMDAwIHJnDQowLjAwMCAw
LjAwMCAwLjAwMCBSRw0KMC4xMjAgdw0KWyBdIDAgZA0KMSBKDQoxIGoNCjMxMC4wODAgNDE2LjY0
MCBtDQozMTAuMjAwIDQxNi42NDAgbA0KMzEwLjIwMCA0MTYuNzYwIGwNCjMxMC4wODAgNDE2Ljg4
MCBsDQozMDkuOTYwIDQxNi44ODAgbA0KMzA5Ljg0MCA0MTYuODgwIGwNCjMwOS43MjAgNDE2Ljc2
MCBsDQozMDkuNzIwIDQxNi42NDAgbA0KMzA5LjcyMCA0MTYuNTIwIGwNCjMwOS44NDAgNDE2LjUy
MCBsDQozMDkuOTYwIDQxNi40MDAgbA0KMzEwLjA4MCA0MTYuMjgwIGwNCjMxMC4wODAgNDE2LjE2
MCBsDQozMDkuOTYwIDQxNi4xNjAgbA0KMzA5Ljg0MCA0MTYuMTYwIGwNCjMwOS44NDAgNDE2LjI4
MCBsDQozMDkuODQwIDQxNi40MDAgbA0KMzA5LjcyMCA0MTYuNDAwIGwNCjMwOS43MjAgNDE2LjI4
MCBsDQozMDkuNzIwIDQxNi4xNjAgbA0KMzA5Ljg0MCA0MTYuMDQwIGwNCjMwOS45NjAgNDE2LjA0
MCBsDQozMTAuMDgwIDQxNi4wNDAgbA0KMzEwLjIwMCA0MTYuMTYwIGwNCjMxMC4yMDAgNDE2LjI4
MCBsDQozMTAuMjAwIDQxNi40MDAgbA0KMzEwLjA4MCA0MTYuNTIwIGwNCjMwOS45NjAgNDE2LjUy
MCBsDQozMDkuOTYwIDQxNi42NDAgbA0KMzA5Ljg0MCA0MTYuNjQwIGwNCjMwOS44NDAgNDE2Ljc2
MCBsDQozMDkuOTYwIDQxNi43NjAgbA0KMzEwLjA4MCA0MTYuNzYwIGwNCjMxMC4wODAgNDE2LjY0
MCBsDQpmKg0KMC44MDAgMC4wMDAgMC4wMDAgcmcNCjAuMDAwIDAuMDAwIDAuMDAwIFJHDQowLjEy
MCB3DQpbIF0gMCBkDQoxIEoNCjEgag0KMzEwLjY4MCA0MTYuNTIwIG0NCjMxMC42ODAgNDE2LjY0
MCBsDQozMTAuNTYwIDQxNi42NDAgbA0KMzEwLjY4MCA0MTYuMjgwIGwNCjMxMC42ODAgNDE2LjA0
MCBsDQozMTAuODAwIDQxNi4wNDAgbA0KMzEwLjgwMCA0MTYuMjgwIGwNCjMxMC45MjAgNDE2LjY0
MCBsDQozMTAuODAwIDQxNi42NDAgbA0KMzEwLjgwMCA0MTYuNTIwIGwNCjMxMC44MDAgNDE2LjQw
MCBsDQozMTAuNjgwIDQxNi40MDAgbA0KMzEwLjY4MCA0MTYuNTIwIGwNCmYqDQowLjgwMCAwLjAw
MCAwLjAwMCByZw0KMC4wMDAgMC4wMDAgMC4wMDAgUkcNCjAuMTIwIHcNClsgXSAwIGQNCjEgSg0K
MSBqDQozMTEuNDAwIDQxNi41MjAgbQ0KMzExLjUyMCA0MTYuNTIwIGwNCjMxMS41MjAgNDE2LjY0
MCBsDQozMTEuNDAwIDQxNi42NDAgbA0KMzExLjI4MCA0MTYuNjQwIGwNCjMxMS4xNjAgNDE2LjY0
MCBsDQozMTEuMTYwIDQxNi41MjAgbA0KMzExLjE2MCA0MTYuNDAwIGwNCjMxMS4yODAgNDE2LjQw
MCBsDQozMTEuMjgwIDQxNi4yODAgbA0KMzExLjQwMCA0MTYuMjgwIGwNCjMxMS40MDAgNDE2LjE2
MCBsDQozMTEuMjgwIDQxNi4xNjAgbA0KMzExLjI4MCA0MTYuMjgwIGwNCjMxMS4xNjAgNDE2LjI4
MCBsDQozMTEuMTYwIDQxNi4xNjAgbA0KMzExLjI4MCA0MTYuMDQwIGwNCjMxMS40MDAgNDE2LjA0
MCBsDQozMTEuNTIwIDQxNi4xNjAgbA0KMzExLjUyMCA0MTYuMjgwIGwNCjMxMS40MDAgNDE2LjQw
MCBsDQozMTEuMjgwIDQxNi41MjAgbA0KMzExLjQwMCA0MTYuNjQwIGwNCjMxMS40MDAgNDE2LjUy
MCBsDQpmKg0KMC44MDAgMC4wMDAgMC4wMDAgcmcNCjAuMDAwIDAuMDAwIDAuMDAwIFJHDQowLjEy
MCB3DQpbIF0gMCBkDQoxIEoNCjEgag0KMzExLjc2MCA0MTYuNjQwIG0NCjMxMS43NjAgNDE2LjUy
MCBsDQozMTEuODgwIDQxNi41MjAgbA0KMzExLjg4MCA0MTYuMDQwIGwNCjMxMi4wMDAgNDE2LjA0
MCBsDQozMTIuMDAwIDQxNi41MjAgbA0KMzEyLjEyMCA0MTYuNTIwIGwNCjMxMi4xMjAgNDE2LjY0
MCBsDQozMTEuNzYwIDQxNi42NDAgbA0KZioNCjAuODAwIDAuMDAwIDAuMDAwIHJnDQowLjAwMCAw
LjAwMCAwLjAwMCBSRw0KMC4xMjAgdw0KWyBdIDAgZA0KMSBKDQoxIGoNCjMxMi4zNjAgNDE2LjA0
MCBtDQozMTIuNzIwIDQxNi4wNDAgbA0KMzEyLjcyMCA0MTYuMTYwIGwNCjMxMi40ODAgNDE2LjE2
MCBsDQozMTIuNDgwIDQxNi4yODAgbA0KMzEyLjcyMCA0MTYuMjgwIGwNCjMxMi43MjAgNDE2LjQw
MCBsDQozMTIuNDgwIDQxNi40MDAgbA0KMzEyLjQ4MCA0MTYuNTIwIGwNCjMxMi43MjAgNDE2LjUy
MCBsDQozMTIuNzIwIDQxNi42NDAgbA0KMzEyLjM2MCA0MTYuNjQwIGwNCjMxMi4zNjAgNDE2LjA0
MCBsDQpmKg0KMC44MDAgMC4wMDAgMC4wMDAgcmcNCjAuMDAwIDAuMDAwIDAuMDAwIFJHDQowLjEy
MCB3DQpbIF0gMCBkDQoxIEoNCjEgag0KMzEzLjA4MCA0MTYuMDQwIG0NCjMxMy4wODAgNDE2LjI4
MCBsDQozMTMuMDgwIDQxNi40MDAgbA0KMzEzLjA4MCA0MTYuNTIwIGwNCjMxMy4wODAgNDE2LjY0
MCBsDQozMTMuMjAwIDQxNi4wNDAgbA0KMzEzLjQ0MCA0MTYuNjQwIGwNCjMxMy4zMjAgNDE2LjUy
MCBsDQozMTMuMzIwIDQxNi40MDAgbA0KMzEzLjMyMCA0MTYuMjgwIGwNCjMxMy4zMjAgNDE2LjA0
MCBsDQozMTMuNDQwIDQxNi4wNDAgbA0KMzEzLjQ0MCA0MTYuNjQwIGwNCjMxMy4zMjAgNDE2LjY0
MCBsDQozMTMuMjAwIDQxNi40MDAgbA0KMzEzLjIwMCA0MTYuMjgwIGwNCjMxMy4yMDAgNDE2LjQw
MCBsDQozMTMuMDgwIDQxNi42NDAgbA0KMzEyLjk2MCA0MTYuNjQwIGwNCjMxMi45NjAgNDE2LjA0
MCBsDQozMTMuMDgwIDQxNi4wNDAgbA0KZioNCjAuODAwIDAuMDAwIDAuMDAwIHJnDQowLjAwMCAw
LjAwMCAwLjAwMCBSRw0KMC4xMjAgdw0KWyBdIDAgZA0KMSBKDQoxIGoNCjMxNC4wNDAgNDE2LjUy
MCBtDQozMTQuMTYwIDQxNi41MjAgbA0KMzE0LjA0MCA0MTYuNjQwIGwNCjMxMy45MjAgNDE2LjY0
MCBsDQozMTMuODAwIDQxNi42NDAgbA0KMzEzLjgwMCA0MTYuNTIwIGwNCjMxMy44MDAgNDE2LjQw
MCBsDQozMTMuOTIwIDQxNi4yODAgbA0KMzE0LjA0MCA0MTYuMjgwIGwNCjMxNC4wNDAgNDE2LjE2
MCBsDQozMTMuOTIwIDQxNi4xNjAgbA0KMzEzLjkyMCA0MTYuMjgwIGwNCjMxMy44MDAgNDE2LjI4
MCBsDQozMTMuODAwIDQxNi4xNjAgbA0KMzEzLjgwMCA0MTYuMDQwIGwNCjMxMy45MjAgNDE2LjA0
MCBsDQozMTQuMDQwIDQxNi4wNDAgbA0KMzE0LjE2MCA0MTYuMTYwIGwNCjMxNC4xNjAgNDE2LjI4
MCBsDQozMTQuMDQwIDQxNi4yODAgbA0KMzE0LjA0MCA0MTYuNDAwIGwNCjMxMy45MjAgNDE2LjQw
MCBsDQozMTMuOTIwIDQxNi41MjAgbA0KMzEzLjkyMCA0MTYuNjQwIGwNCjMxNC4wNDAgNDE2LjUy
MCBsDQpmKg0KMC4wMDAgMC40OTggMC40OTggcmcNCjAuMDAwIDAuMDAwIDAuMDAwIFJHDQowLjEy
MCB3DQpbIF0gMCBkDQoxIEoNCjEgag0KMzE0LjE2MCA0MTMuNTIwIG0NCjMwNi4yNDAgNDEzLjUy
MCBsDQozMDYuMjQwIDQxNS44MDAgbA0KMzE0LjE2MCA0MTUuODAwIGwNCjMxNC4xNjAgNDEzLjUy
MCBsDQpmKg0KMS4wMDAgMS4wMDAgMS4wMDAgUkcNCjAuMjQwIHcNClsgXSAwIGQNCjEgSg0KMSBq
DQozMDguNDAwIDQxMy41MjAgbQ0KMzA4LjQwMCA0MTUuMDgwIGwNClMNCjEuMDAwIDEuMDAwIDEu
MDAwIFJHDQowLjI0MCB3DQpbIF0gMCBkDQoxIEoNCjEgag0KMzA3LjkyMCA0MTMuNTIwIG0NCjMw
Ny45MjAgNDE0Ljg0MCBsDQpTDQoxLjAwMCAxLjAwMCAxLjAwMCBSRw0KMC4yNDAgdw0KWyBdIDAg
ZA0KMSBKDQoxIGoNCjMwNy41NjAgNDEzLjUyMCBtDQozMDcuNTYwIDQxNC42MDAgbA0KUw0KMS4w
MDAgMS4wMDAgMS4wMDAgUkcNCjAuMjQwIHcNClsgXSAwIGQNCjEgSg0KMSBqDQozMDcuMjAwIDQx
My41MjAgbQ0KMzA3LjIwMCA0MTQuMDAwIGwNClMNCjEuMDAwIDEuMDAwIDEuMDAwIFJHDQowLjI0
MCB3DQpbIF0gMCBkDQoxIEoNCjEgag0KMzA2Ljg0MCA0MTMuNTIwIG0NCjMwNi44NDAgNDEzLjc2
MCBsDQpTDQoxLjAwMCAxLjAwMCAxLjAwMCBSRw0KMC4yNDAgdw0KWyBdIDAgZA0KMSBKDQoxIGoN
CjMwNi40ODAgNDEzLjUyMCBtDQozMDYuNDgwIDQxMy43NjAgbA0KUw0KMS4wMDAgMS4wMDAgMS4w
MDAgUkcNCjAuMjQwIHcNClsgXSAwIGQNCjEgSg0KMSBqDQozMDguODgwIDQxMy41MjAgbQ0KMzA4
Ljg4MCA0MTQuODQwIGwNClMNCjEuMDAwIDEuMDAwIDEuMDAwIFJHDQowLjI0MCB3DQpbIF0gMCBk
DQoxIEoNCjEgag0KMzA5LjI0MCA0MTMuNTIwIG0NCjMwOS4yNDAgNDE0LjYwMCBsDQpTDQoxLjAw
MCAxLjAwMCAxLjAwMCBSRw0KMC4yNDAgdw0KWyBdIDAgZA0KMSBKDQoxIGoNCjMwOS42MDAgNDEz
LjUyMCBtDQozMDkuNjAwIDQxNC4wMDAgbA0KUw0KMS4wMDAgMS4wMDAgMS4wMDAgUkcNCjAuMjQw
IHcNClsgXSAwIGQNCjEgSg0KMSBqDQozMDkuODQwIDQxMy41MjAgbQ0KMzA5Ljg0MCA0MTMuNzYw
IGwNClMNCjEuMDAwIDEuMDAwIDEuMDAwIFJHDQowLjI0MCB3DQpbIF0gMCBkDQoxIEoNCjEgag0K
MzEyLjAwMCA0MTMuNTIwIG0NCjMxMi4wMDAgNDE1LjA4MCBsDQpTDQoxLjAwMCAxLjAwMCAxLjAw
MCBSRw0KMC4yNDAgdw0KWyBdIDAgZA0KMSBKDQoxIGoNCjMxMS41MjAgNDEzLjUyMCBtDQozMTEu
NTIwIDQxNC44NDAgbA0KUw0KMS4wMDAgMS4wMDAgMS4wMDAgUkcNCjAuMjQwIHcNClsgXSAwIGQN
CjEgSg0KMSBqDQozMTEuMDQwIDQxMy41MjAgbQ0KMzExLjA0MCA0MTQuNjAwIGwNClMNCjEuMDAw
IDEuMDAwIDEuMDAwIFJHDQowLjI0MCB3DQpbIF0gMCBkDQoxIEoNCjEgag0KMzEwLjgwMCA0MTMu
NTIwIG0NCjMxMC44MDAgNDE0LjAwMCBsDQpTDQoxLjAwMCAxLjAwMCAxLjAwMCBSRw0KMC4yNDAg
dw0KWyBdIDAgZA0KMSBKDQoxIGoNCjMxMC40NDAgNDEzLjUyMCBtDQozMTAuNDQwIDQxMy43NjAg
bA0KUw0KMS4wMDAgMS4wMDAgMS4wMDAgUkcNCjAuMjQwIHcNClsgXSAwIGQNCjEgSg0KMSBqDQoz
MTAuMjAwIDQxMy41MjAgbQ0KMzEwLjIwMCA0MTMuNzYwIGwNClMNCjEuMDAwIDEuMDAwIDEuMDAw
IFJHDQowLjI0MCB3DQpbIF0gMCBkDQoxIEoNCjEgag0KMzEyLjM2MCA0MTMuNTIwIG0NCjMxMi4z
NjAgNDE0Ljg0MCBsDQpTDQoxLjAwMCAxLjAwMCAxLjAwMCBSRw0KMC4yNDAgdw0KWyBdIDAgZA0K
MSBKDQoxIGoNCjMxMi44NDAgNDEzLjUyMCBtDQozMTIuODQwIDQxNC42MDAgbA0KUw0KMS4wMDAg
MS4wMDAgMS4wMDAgUkcNCjAuMjQwIHcNClsgXSAwIGQNCjEgSg0KMSBqDQozMTMuMDgwIDQxMy41
MjAgbQ0KMzEzLjA4MCA0MTQuMDAwIGwNClMNCjEuMDAwIDEuMDAwIDEuMDAwIFJHDQowLjI0MCB3
DQpbIF0gMCBkDQoxIEoNCjEgag0KMzEzLjQ0MCA0MTMuNTIwIG0NCjMxMy40NDAgNDEzLjc2MCBs
DQpTDQoxLjAwMCAxLjAwMCAxLjAwMCBSRw0KMC4yNDAgdw0KWyBdIDAgZA0KMSBKDQoxIGoNCjMx
My44MDAgNDEzLjUyMCBtDQozMTMuODAwIDQxMy43NjAgbA0KUw0KMC4wMDAgMC4wMDAgMC4wMDAg
cmcNCjEuMDAwIDEuMDAwIDEuMDAwIFJHDQowLjI0MCB3DQpbIF0gMCBkDQoxIEoNCjEgag0KMzMy
LjUyMCA0MTYuNDAwIG0NCjMzMi4yODAgNDE2LjQwMCBsDQozMzIuMDQwIDQxNi4yODAgbA0KMzMx
LjkyMCA0MTYuMTYwIGwNCjMzMS44MDAgNDE2LjA0MCBsDQozMzEuNjgwIDQxNS44MDAgbA0KMzMx
LjY4MCA0MTUuNTYwIGwNCjMzMS42ODAgNDE1LjIwMCBsDQozMzEuODAwIDQxNC45NjAgbA0KMzMx
LjkyMCA0MTQuNzIwIGwNCjMzMi4xNjAgNDE0LjYwMCBsDQozMzIuMjgwIDQxNC42MDAgbA0KMzMy
LjUyMCA0MTQuNjAwIGwNCjMzMi43NjAgNDE0LjYwMCBsDQozMzIuODgwIDQxNC42MDAgbA0KMzMz
LjEyMCA0MTQuODQwIGwNCjMzMy4yNDAgNDE0Ljk2MCBsDQozMzMuMjQwIDQxNS4wODAgbA0KMzMz
LjI0MCA0MTUuMjAwIGwNCjMzMy4wMDAgNDE1LjIwMCBsDQozMzMuMDAwIDQxNS4wODAgbA0KMzMy
Ljg4MCA0MTQuOTYwIGwNCjMzMi44ODAgNDE0Ljg0MCBsDQozMzIuNjQwIDQxNC44NDAgbA0KMzMy
LjUyMCA0MTQuNzIwIGwNCjMzMi4yODAgNDE0Ljg0MCBsDQozMzIuMTYwIDQxNC44NDAgbA0KMzMy
LjA0MCA0MTQuOTYwIGwNCjMzMi4wNDAgNDE1LjA4MCBsDQozMzEuOTIwIDQxNS4zMjAgbA0KMzMx
LjkyMCA0MTUuNDQwIGwNCjMzMS45MjAgNDE1LjY4MCBsDQozMzIuMDQwIDQxNS45MjAgbA0KMzMy
LjA0MCA0MTYuMDQwIGwNCjMzMi4xNjAgNDE2LjE2MCBsDQozMzIuNDAwIDQxNi4yODAgbA0KMzMy
LjUyMCA0MTYuMjgwIGwNCjMzMi42NDAgNDE2LjI4MCBsDQozMzIuNzYwIDQxNi4xNjAgbA0KMzMy
Ljg4MCA0MTYuMTYwIGwNCjMzMi44ODAgNDE2LjA0MCBsDQozMzMuMDAwIDQxNS45MjAgbA0KMzMz
LjI0MCA0MTUuOTIwIGwNCjMzMy4yNDAgNDE2LjA0MCBsDQozMzMuMTIwIDQxNi4xNjAgbA0KMzMz
LjEyMCA0MTYuMjgwIGwNCjMzMi44ODAgNDE2LjQwMCBsDQozMzIuNzYwIDQxNi40MDAgbA0KMzMy
LjUyMCA0MTYuNDAwIGwNCmYqDQoxLjAwMCAxLjAwMCAxLjAwMCBSRw0KMC4yNDAgdw0KWyBdIDAg
ZA0KMSBKDQoxIGoNCjAuMDAwIDAuMDAwIDAuMDAwIHJnDQozMzMuODQwIDQxNC42MDAgbQ0KMzMz
LjYwMCA0MTQuNjAwIGwNCjMzMy42MDAgNDE1LjkyMCBsDQozMzMuODQwIDQxNS45MjAgbA0KMzMz
Ljg0MCA0MTQuNjAwIGwNCmgNCjMzMy44NDAgNDE2LjE2MCBtDQozMzMuNjAwIDQxNi4xNjAgbA0K
MzMzLjYwMCA0MTYuNDAwIGwNCjMzMy44NDAgNDE2LjQwMCBsDQozMzMuODQwIDQxNi4xNjAgbA0K
ZioNCjAuMDAwIDAuMDAwIDAuMDAwIHJnDQowLjAwMCAwLjAwMCAwLjAwMCBSRw0KMC4xMjAgdw0K
WyBdIDAgZA0KMSBKDQoxIGoNCjMzNC4wODAgNDE0Ljk2MCBtDQozMzQuMDgwIDQxNC44NDAgbA0K
MzM0LjA4MCA0MTQuNzIwIGwNCjMzNC4yMDAgNDE0LjcyMCBsDQozMzQuMzIwIDQxNC42MDAgbA0K
MzM0LjQ0MCA0MTQuNjAwIGwNCjMzNC41NjAgNDE0LjYwMCBsDQozMzQuODAwIDQxNC42MDAgbA0K
MzM0LjkyMCA0MTQuNjAwIGwNCjMzNS4wNDAgNDE0LjcyMCBsDQozMzUuMTYwIDQxNC44NDAgbA0K
MzM1LjE2MCA0MTQuOTYwIGwNCjMzNS4xNjAgNDE1LjA4MCBsDQozMzUuMDQwIDQxNS4yMDAgbA0K
MzM0LjkyMCA0MTUuMzIwIGwNCjMzNC44MDAgNDE1LjMyMCBsDQozMzQuNjgwIDQxNS4zMjAgbA0K
MzM0LjU2MCA0MTUuNDQwIGwNCjMzNC40NDAgNDE1LjQ0MCBsDQozMzQuMzIwIDQxNS40NDAgbA0K
MzM0LjMyMCA0MTUuNTYwIGwNCjMzNC4zMjAgNDE1LjY4MCBsDQozMzQuNDQwIDQxNS44MDAgbA0K
MzM0LjU2MCA0MTUuODAwIGwNCjMzNC42ODAgNDE1LjgwMCBsDQozMzQuODAwIDQxNS42ODAgbA0K
MzM0LjkyMCA0MTUuNjgwIGwNCjMzNC45MjAgNDE1LjU2MCBsDQozMzUuMTYwIDQxNS41NjAgbA0K
MzM1LjA0MCA0MTUuNjgwIGwNCjMzNS4wNDAgNDE1LjgwMCBsDQozMzQuOTIwIDQxNS45MjAgbA0K
MzM0LjgwMCA0MTUuOTIwIGwNCjMzNC41NjAgNDE1LjkyMCBsDQozMzQuNDQwIDQxNS45MjAgbA0K
MzM0LjMyMCA0MTUuOTIwIGwNCjMzNC4yMDAgNDE1LjgwMCBsDQozMzQuMDgwIDQxNS42ODAgbA0K
MzM0LjA4MCA0MTUuNTYwIGwNCjMzNC4wODAgNDE1LjQ0MCBsDQozMzQuMjAwIDQxNS4zMjAgbA0K
MzM0LjMyMCA0MTUuMjAwIGwNCjMzNC40NDAgNDE1LjIwMCBsDQozMzQuNjgwIDQxNS4yMDAgbA0K
MzM0LjY4MCA0MTUuMDgwIGwNCjMzNC44MDAgNDE1LjA4MCBsDQozMzQuOTIwIDQxNS4wODAgbA0K
MzM0LjkyMCA0MTQuOTYwIGwNCjMzNC45MjAgNDE0Ljg0MCBsDQozMzQuODAwIDQxNC44NDAgbA0K
MzM0LjgwMCA0MTQuNzIwIGwNCjMzNC42ODAgNDE0LjcyMCBsDQozMzQuNTYwIDQxNC43MjAgbA0K
MzM0LjQ0MCA0MTQuNzIwIGwNCjMzNC4zMjAgNDE0Ljg0MCBsDQozMzQuMzIwIDQxNC45NjAgbA0K
MzM0LjA4MCA0MTQuOTYwIGwNCmYqDQowLjAwMCAwLjAwMCAwLjAwMCByZw0KMC4wMDAgMC4wMDAg
MC4wMDAgUkcNCjAuMTIwIHcNClsgXSAwIGQNCjEgSg0KMSBqDQozMzUuODgwIDQxNS45MjAgbQ0K
MzM1Ljc2MCA0MTUuOTIwIGwNCjMzNS42NDAgNDE1LjkyMCBsDQozMzUuNTIwIDQxNS44MDAgbA0K
MzM1LjQwMCA0MTUuNTYwIGwNCjMzNS4yODAgNDE1LjQ0MCBsDQozMzUuMjgwIDQxNS4yMDAgbA0K
MzM1LjI4MCA0MTUuMDgwIGwNCjMzNS40MDAgNDE0Ljg0MCBsDQozMzUuNTIwIDQxNC43MjAgbA0K
MzM1LjUyMCA0MTQuNjAwIGwNCjMzNS43NjAgNDE0LjYwMCBsDQozMzUuODgwIDQxNC42MDAgbA0K
MzM2LjAwMCA0MTQuNjAwIGwNCjMzNi4xMjAgNDE0LjYwMCBsDQozMzYuMjQwIDQxNC43MjAgbA0K
MzM2LjM2MCA0MTQuNzIwIGwNCjMzNi40ODAgNDE0Ljk2MCBsDQozMzYuNDgwIDQxNS4wODAgbA0K
MzM2LjI0MCA0MTUuMDgwIGwNCjMzNi4yNDAgNDE0Ljk2MCBsDQozMzYuMTIwIDQxNC44NDAgbA0K
MzM2LjAwMCA0MTQuNzIwIGwNCjMzNS44ODAgNDE0LjcyMCBsDQozMzUuNzYwIDQxNC43MjAgbA0K
MzM1LjY0MCA0MTQuODQwIGwNCjMzNS42NDAgNDE0Ljk2MCBsDQozMzUuNTIwIDQxNS4wODAgbA0K
MzM1LjUyMCA0MTUuMjAwIGwNCjMzNS41MjAgNDE1LjMyMCBsDQozMzUuNTIwIDQxNS40NDAgbA0K
MzM1LjY0MCA0MTUuNTYwIGwNCjMzNS42NDAgNDE1LjY4MCBsDQozMzUuNzYwIDQxNS42ODAgbA0K
MzM1Ljg4MCA0MTUuODAwIGwNCjMzNi4wMDAgNDE1LjgwMCBsDQozMzYuMTIwIDQxNS42ODAgbA0K
MzM2LjI0MCA0MTUuNTYwIGwNCjMzNi4yNDAgNDE1LjQ0MCBsDQozMzYuNDgwIDQxNS40NDAgbA0K
MzM2LjQ4MCA0MTUuNjgwIGwNCjMzNi4zNjAgNDE1LjgwMCBsDQozMzYuMjQwIDQxNS44MDAgbA0K
MzM2LjI0MCA0MTUuOTIwIGwNCjMzNi4wMDAgNDE1LjkyMCBsDQozMzUuODgwIDQxNS45MjAgbA0K
ZioNCjAuMDAwIDAuMDAwIDAuMDAwIFJHDQowLjEyMCB3DQpbIF0gMCBkDQoxIEoNCjEgag0KMC4w
MDAgMC4wMDAgMC4wMDAgcmcNCjMzNi43MjAgNDE1LjgwMCBtDQozMzYuODQwIDQxNS45MjAgbA0K
MzM3LjA4MCA0MTUuOTIwIGwNCjMzNy4yMDAgNDE1LjkyMCBsDQozMzcuNDQwIDQxNS45MjAgbA0K
MzM3LjU2MCA0MTUuOTIwIGwNCjMzNy42ODAgNDE1LjgwMCBsDQozMzcuODAwIDQxNS42ODAgbA0K
MzM3LjgwMCA0MTUuNDQwIGwNCjMzNy44MDAgNDE1LjMyMCBsDQozMzcuODAwIDQxNS4wODAgbA0K
MzM3LjgwMCA0MTQuOTYwIGwNCjMzNy42ODAgNDE0LjcyMCBsDQozMzcuNTYwIDQxNC42MDAgbA0K
MzM3LjQ0MCA0MTQuNjAwIGwNCjMzNy4yMDAgNDE0LjYwMCBsDQozMzYuOTYwIDQxNC42MDAgbA0K
MzM2Ljg0MCA0MTQuNjAwIGwNCjMzNi43MjAgNDE0LjcyMCBsDQozMzYuNjAwIDQxNC44NDAgbA0K
MzM2LjYwMCA0MTUuMDgwIGwNCjMzNi42MDAgNDE1LjIwMCBsDQozMzYuNjAwIDQxNS40NDAgbA0K
MzM2LjcyMCA0MTUuNTYwIGwNCjMzNi43MjAgNDE1LjgwMCBsDQpoDQozMzYuOTYwIDQxNC44NDAg
bQ0KMzM3LjA4MCA0MTQuNzIwIGwNCjMzNy4yMDAgNDE0LjcyMCBsDQozMzcuMzIwIDQxNC43MjAg
bA0KMzM3LjQ0MCA0MTQuODQwIGwNCjMzNy41NjAgNDE0Ljk2MCBsDQozMzcuNTYwIDQxNS4wODAg
bA0KMzM3LjU2MCA0MTUuMjAwIGwNCjMzNy41NjAgNDE1LjMyMCBsDQozMzcuNTYwIDQxNS40NDAg
bA0KMzM3LjU2MCA0MTUuNTYwIGwNCjMzNy40NDAgNDE1LjY4MCBsDQozMzcuMzIwIDQxNS44MDAg
bA0KMzM3LjIwMCA0MTUuODAwIGwNCjMzNy4wODAgNDE1LjgwMCBsDQozMzYuOTYwIDQxNS42ODAg
bA0KMzM2Ljk2MCA0MTUuNTYwIGwNCjMzNi44NDAgNDE1LjQ0MCBsDQozMzYuODQwIDQxNS4zMjAg
bA0KMzM2Ljg0MCA0MTUuMjAwIGwNCjMzNi44NDAgNDE1LjA4MCBsDQozMzYuODQwIDQxNC45NjAg
bA0KMzM2Ljk2MCA0MTQuODQwIGwNCmYqDQowLjAwMCAwLjAwMCAwLjAwMCByZw0KMC4wMDAgMC4w
MDAgMC4wMDAgUkcNCjAuMTIwIHcNClsgXSAwIGQNCjEgSg0KMSBqDQozMzguNzYwIDQxNi4yODAg
bQ0KMzM4Ljc2MCA0MTYuMTYwIGwNCjMzOS43MjAgNDE2LjE2MCBsDQozMzkuNjAwIDQxNS45MjAg
bA0KMzM5LjQ4MCA0MTUuODAwIGwNCjMzOS4zNjAgNDE1LjU2MCBsDQozMzkuMjQwIDQxNS4zMjAg
bA0KMzM5LjEyMCA0MTQuOTYwIGwNCjMzOS4wMDAgNDE0LjYwMCBsDQozMzkuMjQwIDQxNC42MDAg
bA0KMzM5LjI0MCA0MTQuNzIwIGwNCjMzOS4zNjAgNDE0Ljg0MCBsDQozMzkuMzYwIDQxNC45NjAg
bA0KMzM5LjM2MCA0MTUuMDgwIGwNCjMzOS40ODAgNDE1LjIwMCBsDQozMzkuNDgwIDQxNS40NDAg
bA0KMzM5LjYwMCA0MTUuNTYwIGwNCjMzOS43MjAgNDE1LjY4MCBsDQozMzkuNzIwIDQxNS44MDAg
bA0KMzM5Ljg0MCA0MTYuMDQwIGwNCjMzOS45NjAgNDE2LjA0MCBsDQozMzkuOTYwIDQxNi4xNjAg
bA0KMzM5Ljk2MCA0MTYuMjgwIGwNCjMzOC43NjAgNDE2LjI4MCBsDQpmKg0KMC4wMDAgMC4wMDAg
MC4wMDAgcmcNCjAuMDAwIDAuMDAwIDAuMDAwIFJHDQowLjEyMCB3DQpbIF0gMCBkDQoxIEoNCjEg
ag0KMzQwLjIwMCA0MTUuMDgwIG0NCjM0MC4yMDAgNDE0Ljg0MCBsDQozNDAuMjAwIDQxNC43MjAg
bA0KMzQwLjMyMCA0MTQuNzIwIGwNCjM0MC40NDAgNDE0LjYwMCBsDQozNDAuNTYwIDQxNC42MDAg
bA0KMzQwLjY4MCA0MTQuNjAwIGwNCjM0MC45MjAgNDE0LjYwMCBsDQozNDEuMDQwIDQxNC42MDAg
bA0KMzQxLjE2MCA0MTQuNzIwIGwNCjM0MS4yODAgNDE0Ljg0MCBsDQozNDEuNDAwIDQxNS4wODAg
bA0KMzQxLjQwMCA0MTUuMjAwIGwNCjM0MS40MDAgNDE1LjMyMCBsDQozNDEuMjgwIDQxNS40NDAg
bA0KMzQxLjE2MCA0MTUuNTYwIGwNCjM0MS4wNDAgNDE1LjY4MCBsDQozNDAuOTIwIDQxNS42ODAg
bA0KMzQwLjgwMCA0MTUuODAwIGwNCjM0MC42ODAgNDE1LjY4MCBsDQozNDAuNTYwIDQxNS42ODAg
bA0KMzQwLjQ0MCA0MTUuNjgwIGwNCjM0MC41NjAgNDE2LjE2MCBsDQozNDEuMjgwIDQxNi4xNjAg
bA0KMzQxLjI4MCA0MTYuMjgwIGwNCjM0MC4zMjAgNDE2LjI4MCBsDQozNDAuMjAwIDQxNS4zMjAg
bA0KMzQwLjQ0MCA0MTUuMzIwIGwNCjM0MC40NDAgNDE1LjQ0MCBsDQozNDAuNTYwIDQxNS40NDAg
bA0KMzQwLjU2MCA0MTUuNTYwIGwNCjM0MC42ODAgNDE1LjU2MCBsDQozNDAuODAwIDQxNS41NjAg
bA0KMzQwLjkyMCA0MTUuNDQwIGwNCjM0MS4wNDAgNDE1LjQ0MCBsDQozNDEuMDQwIDQxNS4zMjAg
bA0KMzQxLjE2MCA0MTUuMzIwIGwNCjM0MS4xNjAgNDE1LjIwMCBsDQozNDEuMTYwIDQxNS4wODAg
bA0KMzQxLjA0MCA0MTQuOTYwIGwNCjM0MS4wNDAgNDE0Ljg0MCBsDQozNDAuOTIwIDQxNC44NDAg
bA0KMzQwLjgwMCA0MTQuNzIwIGwNCjM0MC42ODAgNDE0LjcyMCBsDQozNDAuNTYwIDQxNC43MjAg
bA0KMzQwLjU2MCA0MTQuODQwIGwNCjM0MC40NDAgNDE0Ljg0MCBsDQozNDAuNDQwIDQxNC45NjAg
bA0KMzQwLjQ0MCA0MTUuMDgwIGwNCjM0MC4yMDAgNDE1LjA4MCBsDQpmKg0KMC4wMDAgMC4wMDAg
MC4wMDAgUkcNCjAuMTIwIHcNClsgXSAwIGQNCjEgSg0KMSBqDQowLjAwMCAwLjAwMCAwLjAwMCBy
Zw0KMzQxLjY0MCA0MTUuOTIwIG0NCjM0MS43NjAgNDE2LjE2MCBsDQozNDEuODgwIDQxNi4yODAg
bA0KMzQyLjEyMCA0MTYuNDAwIGwNCjM0Mi4zNjAgNDE2LjI4MCBsDQozNDIuNjAwIDQxNi4yODAg
bA0KMzQyLjcyMCA0MTYuMDQwIGwNCjM0Mi43MjAgNDE1LjkyMCBsDQozNDIuODQwIDQxNS42ODAg
bA0KMzQyLjg0MCA0MTUuNDQwIGwNCjM0Mi44NDAgNDE1LjIwMCBsDQozNDIuNzIwIDQxNS4wODAg
bA0KMzQyLjcyMCA0MTQuODQwIGwNCjM0Mi42MDAgNDE0LjcyMCBsDQozNDIuMzYwIDQxNC42MDAg
bA0KMzQyLjEyMCA0MTQuNjAwIGwNCjM0Mi4wMDAgNDE0LjYwMCBsDQozNDEuNzYwIDQxNC43MjAg
bA0KMzQxLjY0MCA0MTQuODQwIGwNCjM0MS42NDAgNDE0Ljk2MCBsDQozNDEuNjQwIDQxNS4yMDAg
bA0KMzQxLjUyMCA0MTUuNDQwIGwNCjM0MS41MjAgNDE1LjY4MCBsDQozNDEuNjQwIDQxNS44MDAg
bA0KMzQxLjY0MCA0MTUuOTIwIGwNCmgNCjM0MS44ODAgNDE0Ljk2MCBtDQozNDEuODgwIDQxNC44
NDAgbA0KMzQyLjAwMCA0MTQuNzIwIGwNCjM0Mi4xMjAgNDE0LjcyMCBsDQozNDIuMjQwIDQxNC43
MjAgbA0KMzQyLjM2MCA0MTQuODQwIGwNCjM0Mi40ODAgNDE0Ljk2MCBsDQozNDIuNDgwIDQxNS4w
ODAgbA0KMzQyLjYwMCA0MTUuMjAwIGwNCjM0Mi42MDAgNDE1LjQ0MCBsDQozNDIuNjAwIDQxNS42
ODAgbA0KMzQyLjQ4MCA0MTUuODAwIGwNCjM0Mi40ODAgNDE1LjkyMCBsDQozNDIuMzYwIDQxNi4w
NDAgbA0KMzQyLjM2MCA0MTYuMTYwIGwNCjM0Mi4yNDAgNDE2LjE2MCBsDQozNDIuMTIwIDQxNi4x
NjAgbA0KMzQyLjAwMCA0MTYuMDQwIGwNCjM0MS44ODAgNDE2LjA0MCBsDQozNDEuODgwIDQxNS44
MDAgbA0KMzQxLjc2MCA0MTUuNjgwIGwNCjM0MS43NjAgNDE1LjQ0MCBsDQozNDEuNzYwIDQxNS4z
MjAgbA0KMzQxLjg4MCA0MTUuMDgwIGwNCjM0MS44ODAgNDE0Ljk2MCBsDQpmKg0KMC4wMDAgMC4w
MDAgMC4wMDAgUkcNCjAuMTIwIHcNClsgXSAwIGQNCjEgSg0KMSBqDQowLjAwMCAwLjAwMCAwLjAw
MCByZw0KMzQzLjA4MCA0MTUuOTIwIG0NCjM0My4yMDAgNDE2LjE2MCBsDQozNDMuMzIwIDQxNi4y
ODAgbA0KMzQzLjU2MCA0MTYuNDAwIGwNCjM0My44MDAgNDE2LjI4MCBsDQozNDMuOTIwIDQxNi4y
ODAgbA0KMzQ0LjA0MCA0MTYuMDQwIGwNCjM0NC4xNjAgNDE1LjkyMCBsDQozNDQuMTYwIDQxNS42
ODAgbA0KMzQ0LjE2MCA0MTUuNDQwIGwNCjM0NC4xNjAgNDE1LjIwMCBsDQozNDQuMTYwIDQxNS4w
ODAgbA0KMzQ0LjE2MCA0MTQuODQwIGwNCjM0My45MjAgNDE0LjcyMCBsDQozNDMuODAwIDQxNC42
MDAgbA0KMzQzLjU2MCA0MTQuNjAwIGwNCjM0My40NDAgNDE0LjYwMCBsDQozNDMuMjAwIDQxNC43
MjAgbA0KMzQzLjA4MCA0MTQuODQwIGwNCjM0My4wODAgNDE0Ljk2MCBsDQozNDIuOTYwIDQxNS4y
MDAgbA0KMzQyLjk2MCA0MTUuNDQwIGwNCjM0Mi45NjAgNDE1LjY4MCBsDQozNDIuOTYwIDQxNS44
MDAgbA0KMzQzLjA4MCA0MTUuOTIwIGwNCmgNCjM0My4zMjAgNDE0Ljk2MCBtDQozNDMuMzIwIDQx
NC44NDAgbA0KMzQzLjQ0MCA0MTQuNzIwIGwNCjM0My41NjAgNDE0LjcyMCBsDQozNDMuNjgwIDQx
NC43MjAgbA0KMzQzLjgwMCA0MTQuODQwIGwNCjM0My45MjAgNDE0Ljk2MCBsDQozNDMuOTIwIDQx
NS4wODAgbA0KMzQzLjkyMCA0MTUuMjAwIGwNCjM0My45MjAgNDE1LjQ0MCBsDQozNDMuOTIwIDQx
NS42ODAgbA0KMzQzLjkyMCA0MTUuODAwIGwNCjM0My45MjAgNDE1LjkyMCBsDQozNDMuODAwIDQx
Ni4wNDAgbA0KMzQzLjY4MCA0MTYuMTYwIGwNCjM0My41NjAgNDE2LjE2MCBsDQozNDMuNDQwIDQx
Ni4xNjAgbA0KMzQzLjQ0MCA0MTYuMDQwIGwNCjM0My4zMjAgNDE2LjA0MCBsDQozNDMuMzIwIDQx
NS44MDAgbA0KMzQzLjIwMCA0MTUuNjgwIGwNCjM0My4yMDAgNDE1LjQ0MCBsDQozNDMuMjAwIDQx
NS4zMjAgbA0KMzQzLjIwMCA0MTUuMDgwIGwNCjM0My4zMjAgNDE0Ljk2MCBsDQpmKg0KMC4wMDAg
MC4wMDAgMC4wMDAgUkcNCjAuNzIwIHcNClsgXSAwIGQNCjEgSg0KMSBqDQozNDcuNTIwIDQxMi41
NjAgbQ0KMzAzLjYwMCA0MTIuNTYwIGwNClMNCjAuMDAwIDAuMDAwIDAuMDAwIFJHDQowLjI0MCB3
DQpbIF0gMCBkDQoxIEoNCjEgag0KMzQ3Ljc2MCA0MTcuNDgwIG0NCjMwNC4yMDAgNDE3LjQ4MCBs
DQpTDQowLjAwMCAwLjAwMCAwLjAwMCBSRw0KMC40ODAgdw0KWyBdIDAgZA0KMSBKDQoxIGoNCjM0
Ny4yODAgMzg0Ljk2MCBtDQozMDMuOTYwIDM4NC45NjAgbA0KUw0KMC4wMDAgMC4wMDAgMC4wMDAg
UkcNCjAuNDgwIHcNClsgXSAwIGQNCjEgSg0KMSBqDQozNDcuMjgwIDM4NC4xMjAgbQ0KMzAzLjk2
MCAzODQuMTIwIGwNClMNCjAuMDAwIDAuMDAwIDAuMDAwIFJHDQowLjQ4MCB3DQpbIF0gMCBkDQox
IEoNCjEgag0KMzQ3LjI4MCAzODIuOTIwIG0NCjMwMy45NjAgMzgyLjkyMCBsDQpTDQowLjAwMCAw
LjAwMCAwLjAwMCBSRw0KMC40ODAgdw0KWyBdIDAgZA0KMSBKDQoxIGoNCjM0Ny4yODAgMzgxLjcy
MCBtDQozMDMuOTYwIDM4MS43MjAgbA0KUw0KMC4wMDAgMC4wMDAgMC4wMDAgUkcNCjAuNDgwIHcN
ClsgXSAwIGQNCjEgSg0KMSBqDQozNDcuMjgwIDM4MC40MDAgbQ0KMzAzLjk2MCAzODAuNDAwIGwN
ClMNCjAuMDAwIDAuMDAwIDAuMDAwIFJHDQowLjQ4MCB3DQpbIF0gMCBkDQoxIEoNCjEgag0KMzQ3
LjI4MCAzNzkuMjAwIG0NCjMwMy45NjAgMzc5LjIwMCBsDQpTDQowLjAwMCAwLjAwMCAwLjAwMCBS
Rw0KMC40ODAgdw0KWyBdIDAgZA0KMSBKDQoxIGoNCjM0Ny4yODAgMzc4LjAwMCBtDQozMDMuOTYw
IDM3OC4wMDAgbA0KUw0KMC4wMDAgMC4wMDAgMC4wMDAgUkcNCjAuNDgwIHcNClsgXSAwIGQNCjEg
Sg0KMSBqDQozNDcuMjgwIDM3Ni44MDAgbQ0KMzAzLjk2MCAzNzYuODAwIGwNClMNCjAuMDAwIDAu
MDAwIDAuMDAwIFJHDQowLjQ4MCB3DQpbIF0gMCBkDQoxIEoNCjEgag0KMzQ3LjI4MCAzNzUuNDgw
IG0NCjMwMy45NjAgMzc1LjQ4MCBsDQpTDQowLjAwMCAwLjAwMCAwLjAwMCBSRw0KMC40ODAgdw0K
WyBdIDAgZA0KMSBKDQoxIGoNCjM0Ny4yODAgMzc0LjI4MCBtDQozMDMuOTYwIDM3NC4yODAgbA0K
Uw0KMC4wMDAgMC4wMDAgMC4wMDAgUkcNCjAuNDgwIHcNClsgXSAwIGQNCjEgSg0KMSBqDQozNDcu
MjgwIDM3My4wODAgbQ0KMzAzLjk2MCAzNzMuMDgwIGwNClMNCjAuMDAwIDAuMDAwIDAuMDAwIFJH
DQowLjQ4MCB3DQpbIF0gMCBkDQoxIEoNCjEgag0KMzQ3LjI4MCAzNzEuODgwIG0NCjMwMy45NjAg
MzcxLjg4MCBsDQpTDQowLjAwMCAwLjAwMCAwLjAwMCBSRw0KMC40ODAgdw0KWyBdIDAgZA0KMSBK
DQoxIGoNCjM0Ny4yODAgMzcwLjY4MCBtDQozMDMuOTYwIDM3MC42ODAgbA0KUw0KMC4wMDAgMC4w
MDAgMC4wMDAgUkcNCjAuNDgwIHcNClsgXSAwIGQNCjEgSg0KMSBqDQozNDcuMjgwIDM2OS4zNjAg
bQ0KMzAzLjk2MCAzNjkuMzYwIGwNClMNCjAuMDAwIDAuMDAwIDAuMDAwIFJHDQowLjQ4MCB3DQpb
IF0gMCBkDQoxIEoNCjEgag0KMzQ3LjI4MCAzNjYuOTYwIG0NCjMwMy45NjAgMzY2Ljk2MCBsDQpT
DQowLjAwMCAwLjAwMCAwLjAwMCBSRw0KMC40ODAgdw0KWyBdIDAgZA0KMSBKDQoxIGoNCjM0Ny4y
ODAgMzY1Ljc2MCBtDQozMDMuOTYwIDM2NS43NjAgbA0KUw0KMC4wMDAgMC4wMDAgMC4wMDAgUkcN
CjAuNDgwIHcNClsgXSAwIGQNCjEgSg0KMSBqDQozNDcuMjgwIDM2NC40NDAgbQ0KMzAzLjk2MCAz
NjQuNDQwIGwNClMNCjAuMDAwIDAuMDAwIDAuMDAwIFJHDQowLjQ4MCB3DQpbIF0gMCBkDQoxIEoN
CjEgag0KMzQ3LjI4MCAzNjMuMjQwIG0NCjMwMy45NjAgMzYzLjI0MCBsDQpTDQowLjAwMCAwLjAw
MCAwLjAwMCBSRw0KMC40ODAgdw0KWyBdIDAgZA0KMSBKDQoxIGoNCjM0Ny4yODAgMzYyLjA0MCBt
DQozMDMuOTYwIDM2Mi4wNDAgbA0KUw0KMC4wMDAgMC4wMDAgMC4wMDAgUkcNCjAuNDgwIHcNClsg
XSAwIGQNCjEgSg0KMSBqDQozNDcuMjgwIDM2MC44NDAgbQ0KMzAzLjk2MCAzNjAuODQwIGwNClMN
CjAuMDAwIDAuMDAwIDAuMDAwIFJHDQowLjQ4MCB3DQpbIF0gMCBkDQoxIEoNCjEgag0KMzQ3LjI4
MCAzNTkuNjQwIG0NCjMwMy45NjAgMzU5LjY0MCBsDQpTDQowLjAwMCAwLjAwMCAwLjAwMCBSRw0K
MC40ODAgdw0KWyBdIDAgZA0KMSBKDQoxIGoNCjM0Ny4yODAgMzU4LjMyMCBtDQozMDMuOTYwIDM1
OC4zMjAgbA0KUw0KMC4wMDAgMC4wMDAgMC4wMDAgUkcNCjAuNDgwIHcNClsgXSAwIGQNCjEgSg0K
MSBqDQozNDcuMjgwIDM1Ny4xMjAgbQ0KMzAzLjk2MCAzNTcuMTIwIGwNClMNCjAuMDAwIDAuMDAw
IDAuMDAwIFJHDQowLjQ4MCB3DQpbIF0gMCBkDQoxIEoNCjEgag0KMzQ3LjI4MCAzNTUuOTIwIG0N
CjMwMy45NjAgMzU1LjkyMCBsDQpTDQowLjAwMCAwLjAwMCAwLjAwMCBSRw0KMC40ODAgdw0KWyBd
IDAgZA0KMSBKDQoxIGoNCjM0Ny4yODAgMzU0LjcyMCBtDQozMDMuOTYwIDM1NC43MjAgbA0KUw0K
MC4wMDAgMC4wMDAgMC4wMDAgUkcNCjAuNDgwIHcNClsgXSAwIGQNCjEgSg0KMSBqDQozNDcuMjgw
IDM1My40MDAgbQ0KMzAzLjk2MCAzNTMuNDAwIGwNClMNCjAuMDAwIDAuMDAwIDAuMDAwIFJHDQow
LjQ4MCB3DQpbIF0gMCBkDQoxIEoNCjEgag0KMzQ3LjI4MCAzNTIuMjAwIG0NCjMwMy45NjAgMzUy
LjIwMCBsDQpTDQowLjAwMCAwLjAwMCAwLjAwMCBSRw0KMC40ODAgdw0KWyBdIDAgZA0KMSBKDQox
IGoNCjM0Ny4yODAgMzUxLjEyMCBtDQozMDMuOTYwIDM1MS4xMjAgbA0KUw0KMC4wMDAgMC4wMDAg
MC4wMDAgUkcNCjAuNDgwIHcNClsgXSAwIGQNCjEgSg0KMSBqDQozNDcuMjgwIDM2OC4xNjAgbQ0K
MzAzLjk2MCAzNjguMTYwIGwNClMNCjAuMDAwIDAuMDAwIDAuMDAwIFJHDQowLjQ4MCB3DQpbIF0g
MCBkDQoxIEoNCjEgag0KMzA4LjA0MCAzODUuMDgwIG0NCjMwOC4wNDAgNDEyLjY4MCBsDQpTDQow
LjAwMCAwLjAwMCAwLjAwMCBSRw0KMC40ODAgdw0KWyBdIDAgZA0KMSBKDQoxIGoNCjMxMi43MjAg
Mzg1LjA4MCBtDQozMTIuNzIwIDQxMi42ODAgbA0KUw0KMC4wMDAgMC4wMDAgMC4wMDAgUkcNCjAu
NDgwIHcNClsgXSAwIGQNCjEgSg0KMSBqDQozMTcuMTYwIDM4NS4wODAgbQ0KMzE3LjE2MCA0MTIu
NjgwIGwNClMNCjAuMDAwIDAuMDAwIDAuMDAwIFJHDQowLjQ4MCB3DQpbIF0gMCBkDQoxIEoNCjEg
ag0KMzIxLjYwMCAzODUuMDgwIG0NCjMyMS42MDAgNDEyLjQ0MCBsDQpTDQowLjAwMCAwLjAwMCAw
LjAwMCBSRw0KMC40ODAgdw0KWyBdIDAgZA0KMSBKDQoxIGoNCjMyNi4wNDAgMzg1LjA4MCBtDQoz
MjYuMDQwIDQxMi40NDAgbA0KUw0KMC4wMDAgMC4wMDAgMC4wMDAgUkcNCjAuNDgwIHcNClsgXSAw
IGQNCjEgSg0KMSBqDQozMzAuNDgwIDM4NS4wODAgbQ0KMzMwLjQ4MCA0MTIuNDQwIGwNClMNCjAu
MDAwIDAuMDAwIDAuMDAwIFJHDQowLjQ4MCB3DQpbIF0gMCBkDQoxIEoNCjEgag0KMzM0LjkyMCAz
ODUuMDgwIG0NCjMzNC45MjAgNDEyLjQ0MCBsDQpTDQowLjAwMCAwLjAwMCAwLjAwMCBSRw0KMC40
ODAgdw0KWyBdIDAgZA0KMSBKDQoxIGoNCjMzOS40ODAgMzg1LjA4MCBtDQozMzkuNDgwIDQxMi40
NDAgbA0KUw0KMC4wMDAgMC4wMDAgMC4wMDAgUkcNCjAuNDgwIHcNClsgXSAwIGQNCjEgSg0KMSBq
DQozNDMuNjgwIDM4NS4wODAgbQ0KMzQzLjY4MCA0MTIuNDQwIGwNClMNCjAuMDAwIDAuMDAwIDAu
MDAwIFJHDQowLjM2MCB3DQpbIF0gMCBkDQoxIEoNCjEgag0KMzEwLjU2MCA0MDYuNDQwIG0NCjMw
OC4xNjAgNDA2LjQ0MCBsDQozMDguMTYwIDQxMi40NDAgbA0KMzEwLjU2MCA0MTIuNDQwIGwNCjMx
MC41NjAgNDA2LjQ0MCBsDQpTDQowLjAwMCAwLjAwMCAwLjAwMCBSRw0KMC4zNjAgdw0KWyBdIDAg
ZA0KMSBKDQoxIGoNCjMxMS4xNjAgNDEyLjQ0MCBtDQozMTAuNTYwIDQwNi40NDAgbA0KUw0KMC4w
MDAgMC4wMDAgMC4wMDAgUkcNCjAuMzYwIHcNClsgXSAwIGQNCjEgSg0KMSBqDQozMTUuMTIwIDQw
Ni40NDAgbQ0KMzEyLjcyMCA0MDYuNDQwIGwNCjMxMi43MjAgNDEyLjQ0MCBsDQozMTUuMTIwIDQx
Mi40NDAgbA0KMzE1LjEyMCA0MDYuNDQwIGwNClMNCjAuMDAwIDAuMDAwIDAuMDAwIFJHDQowLjM2
MCB3DQpbIF0gMCBkDQoxIEoNCjEgag0KMzE1LjYwMCA0MTIuNDQwIG0NCjMxNS4xMjAgNDA2LjQ0
MCBsDQpTDQowLjAwMCAwLjAwMCAwLjAwMCBSRw0KMC4zNjAgdw0KWyBdIDAgZA0KMSBKDQoxIGoN
CjMxOS41NjAgNDA2LjQ0MCBtDQozMTcuMTYwIDQwNi40NDAgbA0KMzE3LjE2MCA0MTIuNDQwIGwN
CjMxOS41NjAgNDEyLjQ0MCBsDQozMTkuNTYwIDQwNi40NDAgbA0KUw0KMC4wMDAgMC4wMDAgMC4w
MDAgUkcNCjAuMzYwIHcNClsgXSAwIGQNCjEgSg0KMSBqDQozMjAuMTYwIDQxMi40NDAgbQ0KMzE5
LjU2MCA0MDYuNDQwIGwNClMNCjAuMDAwIDAuMDAwIDAuMDAwIFJHDQowLjM2MCB3DQpbIF0gMCBk
DQoxIEoNCjEgag0KMzEyLjI0MCA0MTAuMjgwIG0NCjMxMS4yODAgNDEwLjI4MCBsDQpTDQowLjAw
MCAwLjAwMCAwLjAwMCBSRw0KMC4zNjAgdw0KWyBdIDAgZA0KMSBKDQoxIGoNCjMxNi42ODAgNDEw
LjI4MCBtDQozMTUuODQwIDQxMC4yODAgbA0KUw0KMC4wMDAgMC4wMDAgMC4wMDAgUkcNCjAuMzYw
IHcNClsgXSAwIGQNCjEgSg0KMSBqDQozMTIuMjQwIDQxMS4xMjAgbQ0KMzExLjI4MCA0MTEuMTIw
IGwNClMNCjAuMDAwIDAuMDAwIDAuMDAwIFJHDQowLjM2MCB3DQpbIF0gMCBkDQoxIEoNCjEgag0K
MzE2LjgwMCA0MTEuMTIwIG0NCjMxNS44NDAgNDExLjEyMCBsDQpTDQowLjAwMCAwLjAwMCAwLjAw
MCBSRw0KMC4zNjAgdw0KWyBdIDAgZA0KMSBKDQoxIGoNCjMyMS4yNDAgNDExLjEyMCBtDQozMjAu
MjgwIDQxMS4xMjAgbA0KUw0KMC4wMDAgMC4wMDAgMC4wMDAgcmcNCjAuMDAwIDAuMDAwIDAuMDAw
IFJHDQowLjM2MCB3DQpbIF0gMCBkDQoxIEoNCjEgag0KMzAyLjUyMCAzNDguODQwIDQ2LjkyMCA3
Ni45MjAgcmUNCm4NCjAuMDAwIDAuMDAwIDAuMDAwIFJHDQowLjcyMCB3DQpbIF0gMCBkDQoxIEoN
CjEgag0KMC4wMDAgMC4wMDAgMC4wMDAgcmcNCjMwMi40NzEgNDA2LjQ0MCBtDQoxOTIuMTQ0IDQw
Ni40MDIgMTAyLjgwOCAzNzYuNzIzIDEwMi43MjAgMzQwLjA4MCBjDQpTDQoxLjAwMCAxLjAwMCAx
LjAwMCByZw0KMC4wMDAgMC4wMDAgMC4wMDAgUkcNCjAuNzIwIHcNClsgXSAwIGQNCjEgSg0KMSBq
DQoyNi40MDAgMjYyLjgwMCAxNTIuNjQwIDE4LjAwMCByZQ0KYioNCjAuMDAwIDAuMDAwIDAuMDAw
IFJHDQowLjcyMCB3DQpbIF0gMCBkDQoxIEoNCjEgag0KMTI4LjY0MCAyODEuNTIwIG0NCjEyOC42
NDAgMjYzLjUyMCBsDQpTDQowLjAwMCAwLjAwMCAwLjAwMCBSRw0KMC43MjAgdw0KWyBdIDAgZA0K
MSBKDQoxIGoNCjQ5LjQ0MCAyODAuODAwIG0NCjQ5LjQ0MCAyNjIuODAwIGwNClMNCjAuMDAwIDAu
MDAwIDAuMDAwIFJHDQowLjcyMCB3DQpbIF0gMCBkDQoxIEoNCjEgag0KNzYuODAwIDI4MC44MDAg
bQ0KNzYuODAwIDI2Mi44MDAgbA0KUw0KMC4wMDAgMC4wMDAgMC4wMDAgUkcNCjAuNzIwIHcNClsg
XSAwIGQNCjEgSg0KMSBqDQoxNTUuMjgwIDI4MC44MDAgbQ0KMTU1LjI4MCAyNjIuODAwIGwNClMN
CjAuMDAwIDAuMDAwIDAuMDAwIFJHDQowLjcyMCB3DQpbIF0gMCBkDQoxIEoNCjEgag0KMTAyLjAw
MCAyODEuNTIwIG0NCjEwMi4wMDAgMjYzLjUyMCBsDQpTDQowLjAwMCAwLjAwMCAwLjAwMCByZw0K
MC4wMDAgMC4wMDAgMC4wMDAgUkcNCjAuNzIwIHcNClsgXSAwIGQNCjEgSg0KMSBqDQoyNy4xMjAg
MjY0Ljg0MCAxOC44NDAgMTAuOTIwIHJlDQpuDQpCVA0KMS4wMDAgMC4wMDAgMC4wMDAgMS4wMDAg
MjcuMTIwIDI2Ny4xMjAgVG0NCi9GNSA5LjkwNCBUZg0KMCBUcg0KMC4wMDAgMC4wMDAgMC4wMDAg
cmcNCjAuMDAwIFRjDQoxMDMuMzMzIFR6DQooVk0xKVRqDQpFVA0KMC4wMDAgMC4wMDAgMC4wMDAg
cmcNCjAuMDAwIDAuMDAwIDAuMDAwIFJHDQowLjcyMCB3DQpbIF0gMCBkDQoxIEoNCjEgag0KNTMu
NzYwIDI2NC44NDAgMzMuMjQwIDEwLjkyMCByZQ0Kbg0KQlQNCjEuMDAwIDAuMDAwIDAuMDAwIDEu
MDAwIDUzLjc2MCAyNjcuMTIwIFRtDQovRjUgOS45MDQgVGYNCjAgVHINCjAuMDAwIDAuMDAwIDAu
MDAwIHJnDQowLjAwMCBUYw0KMTAzLjMzMyBUeg0KKFZNMilUag0KRVQNCjAuMDAwIDAuMDAwIDAu
MDAwIHJnDQowLjAwMCAwLjAwMCAwLjAwMCBSRw0KMC43MjAgdw0KWyBdIDAgZA0KMSBKDQoxIGoN
CjgwLjQwMCAyNjQuODQwIDMzLjI0MCAxMC45MjAgcmUNCm4NCkJUDQoxLjAwMCAwLjAwMCAwLjAw
MCAxLjAwMCA4MC40MDAgMjY3LjEyMCBUbQ0KL0Y1IDkuOTA0IFRmDQowIFRyDQowLjAwMCAwLjAw
MCAwLjAwMCByZw0KMC4wMDAgVGMNCjEwMy4zMzMgVHoNCihWTTMpVGoNCkVUDQowLjAwMCAwLjAw
MCAwLjAwMCByZw0KMC4wMDAgMC4wMDAgMC4wMDAgUkcNCjAuNzIwIHcNClsgXSAwIGQNCjEgSg0K
MSBqDQoxMDQuODgwIDI2NC44NDAgMzMuMjQwIDEwLjkyMCByZQ0Kbg0KQlQNCjEuMDAwIDAuMDAw
IDAuMDAwIDEuMDAwIDEwNC44ODAgMjY3LjEyMCBUbQ0KL0Y1IDkuOTA0IFRmDQowIFRyDQowLjAw
MCAwLjAwMCAwLjAwMCByZw0KMC4wMDAgVGMNCjEwMy4zMzMgVHoNCihWTTQpVGoNCkVUDQowLjAw
MCAwLjAwMCAwLjAwMCByZw0KMC4wMDAgMC4wMDAgMC4wMDAgUkcNCjAuNzIwIHcNClsgXSAwIGQN
CjEgSg0KMSBqDQoxNTguMTYwIDI2NC44NDAgMzMuMjQwIDEwLjkyMCByZQ0Kbg0KQlQNCjEuMDAw
IDAuMDAwIDAuMDAwIDEuMDAwIDE1OC4xNjAgMjY3LjEyMCBUbQ0KL0Y1IDkuOTA0IFRmDQowIFRy
DQowLjAwMCAwLjAwMCAwLjAwMCByZw0KMC4wMDAgVGMNCjEwMy4zMzMgVHoNCihWTTYpVGoNCkVU
DQowLjAwMCAwLjAwMCAwLjAwMCByZw0KMC4wMDAgMC4wMDAgMC4wMDAgUkcNCjAuNzIwIHcNClsg
XSAwIGQNCjEgSg0KMSBqDQoxMzEuNTIwIDI2NC44NDAgMzMuMjQwIDEwLjkyMCByZQ0Kbg0KQlQN
CjEuMDAwIDAuMDAwIDAuMDAwIDEuMDAwIDEzMS41MjAgMjY3LjEyMCBUbQ0KL0Y1IDkuOTA0IFRm
DQowIFRyDQowLjAwMCAwLjAwMCAwLjAwMCByZw0KMC4wMDAgVGMNCjEwMy4zMzMgVHoNCihWTTUp
VGoNCkVUDQowLjAwMCAwLjAwMCAwLjAwMCByZw0KMC4wMDAgMC4wMDAgMC4wMDAgUkcNCjAuNzIw
IHcNClsgXSAwIGQNCjEgSg0KMSBqDQo4NC4xMjAgMzI5LjY0MCAyOC42ODAgMjEuNzIwIHJlDQpu
DQpCVA0KMS4wMDAgMC4wMDAgMC4wMDAgMS4wMDAgODQuMTIwIDM0Mi43MjAgVG0NCi9GNSA5Ljkw
NCBUZg0KMCBUcg0KMC4wMDAgMC4wMDAgMC4wMDAgcmcNCjAuMDAwIFRjDQo5NS41NTEgVHoNCihl
dGgwKVRqDQpFVA0KMC4wMDAgMC4wMDAgMC4wMDAgcmcNCjAuMDAwIDAuMDAwIDAuMDAwIFJHDQow
LjcyMCB3DQpbIF0gMCBkDQoxIEoNCjEgag0KMjc5LjEyMCAzOTUuMTYwIDM5LjAwMCAxMC45MjAg
cmUNCm4NCkJUDQoxLjAwMCAwLjAwMCAwLjAwMCAxLjAwMCAyNzkuMTIwIDM5Ny40NDAgVG0NCi9G
NSA5LjkwNCBUZg0KMCBUcg0KMC4wMDAgMC4wMDAgMC4wMDAgcmcNCjAuMDAwIFRjDQo4NS4xNDgg
VHoNCihHRSA3LzMpVGoNCkVUDQowLjAwMCAwLjAwMCAwLjAwMCByZw0KMC4wMDAgMC4wMDAgMC4w
MDAgUkcNCjAuNzIwIHcNClsgXSAwIGQNCjEgSg0KMSBqDQozMDcuMjAwIDMzNy41NjAgNTMuMTYw
IDEwLjkyMCByZQ0Kbg0KQlQNCjEuMDAwIDAuMDAwIDAuMDAwIDEuMDAwIDMwNy4yMDAgMzM5Ljg0
MCBUbQ0KL0Y1IDkuOTA0IFRmDQowIFRyDQowLjAwMCAwLjAwMCAwLjAwMCByZw0KMC4wMDAgVGMN
CjkxLjUzMCBUeg0KKENpc2NvKVRqDQpFVA0KQlQNCjEuMDAwIDAuMDAwIDAuMDAwIDEuMDAwIDMy
OC44MDAgMzM5Ljg0MCBUbQ0KL0Y1IDkuOTA0IFRmDQowIFRyDQowLjAwMCAwLjAwMCAwLjAwMCBy
Zw0KMC4wMDAgVGMNCjg0LjQ4OSBUeg0KKCA3NjA5KVRqDQpFVA0KMC4wMDAgMC4wMDAgMC4wMDAg
cmcNCjAuMDAwIDAuMDAwIDAuMDAwIFJHDQowLjcyMCB3DQpbIF0gMCBkDQoxIEoNCjEgag0KMy42
MDAgMzA0LjIwMCBtDQo2Ni4wMDAgMzY2LjYwMCBsDQo3My42ODAgMzU4LjkyMCBsDQoxMS4yODAg
Mjk2LjUyMCBsDQozLjYwMCAzMDQuMjAwIGwNCm4NCkJUDQowLjcwNyAwLjcwNyAtMC43MDcgMC43
MDcgOS43MjAgMjk4LjA4MCBUbQ0KL0Y1IDkuOTA0IFRmDQowIFRyDQowLjAwMCAwLjAwMCAwLjAw
MCByZw0KMC4wMDAgVGMNCjk2LjM5NiBUeg0KKFBvd2VyVmF1bHQpVGoNCkVUDQpCVA0KMC43MDcg
MC43MDcgLTAuNzA3IDAuNzA3IDQyLjI0MCAzMzAuNjAwIFRtDQovRjUgOS45MDQgVGYNCjAgVHIN
CjAuMDAwIDAuMDAwIDAuMDAwIHJnDQowLjAwMCBUYw0KOTEuMDU4IFR6DQooTlgzMDAwKVRqDQpF
VA0KMC4wMDAgMC4wMDAgMC4wMDAgcmcNCjAuMDAwIDAuMDAwIDAuMDAwIFJHDQowLjcyMCB3DQpb
IF0gMCBkDQoxIEoNCjEgag0KMzUuMDQwIDMuNDgwIDM1OS40MDAgMjI2LjkyMCByZQ0Kbg0KQlQN
CjEuMDAwIDAuMDAwIDAuMDAwIDEuMDAwIDM1LjA0MCAyMjEuNzYwIFRtDQovRjcgOS45MDQgVGYN
CjAgVHINCjAuMDAwIDAuMDAwIDAuMDAwIHJnDQowLjAwMCBUYw0KOTUuMDI5IFR6DQooS2V5KVRq
DQpFVA0KQlQNCjEuMDAwIDAuMDAwIDAuMDAwIDEuMDAwIDUwLjE2MCAyMjEuNzYwIFRtDQovRjUg
OS45MDQgVGYNCjAgVHINCjAuMDAwIDAuMDAwIDAuMDAwIHJnDQowLjAwMCBUYw0KNzYuOTIzIFR6
DQooOilUag0KRVQNCkJUDQoxLjAwMCAwLjAwMCAwLjAwMCAxLjAwMCAzNS4wNDAgMjAwLjE2MCBU
bQ0KL0Y1IDkuOTA0IFRmDQowIFRyDQowLjAwMCAwLjAwMCAwLjAwMCByZw0KMC4wMDAgVGMNCjk2
LjM5NiBUeg0KKFBvd2VyVmF1bHQpVGoNCkVUDQpCVA0KMS4wMDAgMC4wMDAgMC4wMDAgMS4wMDAg
ODEuMTIwIDIwMC4xNjAgVG0NCi9GNSA5LjkwNCBUZg0KMCBUcg0KMC4wMDAgMC4wMDAgMC4wMDAg
cmcNCjAuMDAwIFRjDQo5MS4wNTggVHoNCihOWDMwMDApVGoNCkVUDQpCVA0KMS4wMDAgMC4wMDAg
MC4wMDAgMS4wMDAgMTExLjM2MCAyMDAuMTYwIFRtDQovRjUgOS45MDQgVGYNCjAgVHINCjAuMDAw
IDAuMDAwIDAuMDAwIHJnDQowLjAwMCBUYw0KOTIuODEzIFR6DQooID0gRGVsbCBzZXJ2ZXIsIGlu
c3RhbGxlZCBCYXNlIE9TKVRqDQpFVA0KQlQNCjEuMDAwIDAuMDAwIDAuMDAwIDEuMDAwIDIzNS4y
MDAgMjAwLjE2MCBUbQ0KL0Y1IDkuOTA0IFRmDQowIFRyDQowLjAwMCAwLjAwMCAwLjAwMCByZw0K
MC4wMDAgVGMNCjk4LjUxMSBUeg0KKFVidW50dSlUag0KRVQNCkJUDQoxLjAwMCAwLjAwMCAwLjAw
MCAxLjAwMCAyNjQuNzIwIDIwMC4xNjAgVG0NCi9GNSA5LjkwNCBUZg0KMCBUcg0KMC4wMDAgMC4w
MDAgMC4wMDAgcmcNCjAuMDAwIFRjDQo4My4yODQgVHoNCiggMTIuMDQpVGoNCkVUDQpCVA0KMS4w
MDAgMC4wMDAgMC4wMDAgMS4wMDAgMjg4LjQ4MCAyMDAuMTYwIFRtDQovRjUgOS45MDQgVGYNCjAg
VHINCjAuMDAwIDAuMDAwIDAuMDAwIHJnDQowLjAwMCBUYw0KOTEuODQ3IFR6DQooTFRTKVRqDQpF
VA0KQlQNCjEuMDAwIDAuMDAwIDAuMDAwIDEuMDAwIDMwNC4zMjAgMjAwLjE2MCBUbQ0KL0Y1IDku
OTA0IFRmDQowIFRyDQowLjAwMCAwLjAwMCAwLjAwMCByZw0KMC4wMDAgVGMNCjkyLjQxMyBUeg0K
KCBzZXJ2ZXIgd2l0aClUag0KRVQNCkJUDQoxLjAwMCAwLjAwMCAwLjAwMCAxLjAwMCAzNTEuMTIw
IDIwMC4xNjAgVG0NCi9GNSA5LjkwNCBUZg0KMCBUcg0KMC4wMDAgMC4wMDAgMC4wMDAgcmcNCjAu
MDAwIFRjDQo4NC45MzQgVHoNCihYRU4pVGoNCkVUDQpCVA0KMS4wMDAgMC4wMDAgMC4wMDAgMS4w
MDAgMzY5LjEyMCAyMDAuMTYwIFRtDQovRjUgOS45MDQgVGYNCjAgVHINCjAuMDAwIDAuMDAwIDAu
MDAwIHJnDQowLjAwMCBUYw0KNzcuNTkwIFR6DQooIDQuMClUag0KRVQNCkJUDQoxLjAwMCAwLjAw
MCAwLjAwMCAxLjAwMCAzNS4wNDAgMTc4LjU2MCBUbQ0KL0Y1IDkuOTA0IFRmDQowIFRyDQowLjAw
MCAwLjAwMCAwLjAwMCByZw0KMC4wMDAgVGMNCjkxLjUzMCBUeg0KKENpc2NvKVRqDQpFVA0KQlQN
CjEuMDAwIDAuMDAwIDAuMDAwIDEuMDAwIDU2LjY0MCAxNzguNTYwIFRtDQovRjUgOS45MDQgVGYN
CjAgVHINCjAuMDAwIDAuMDAwIDAuMDAwIHJnDQowLjAwMCBUYw0KODIuOTkyIFR6DQooIDc2MDkg
PSlUag0KRVQNCkJUDQoxLjAwMCAwLjAwMCAwLjAwMCAxLjAwMCA4NS40NDAgMTc4LjU2MCBUbQ0K
L0Y1IDkuOTA0IFRmDQowIFRyDQowLjAwMCAwLjAwMCAwLjAwMCByZw0KMC4wMDAgVGMNCjkxLjUz
MCBUeg0KKENpc2NvKVRqDQpFVA0KQlQNCjEuMDAwIDAuMDAwIDAuMDAwIDEuMDAwIDEwNy4wNDAg
MTc4LjU2MCBUbQ0KL0Y1IDkuOTA0IFRmDQowIFRyDQowLjAwMCAwLjAwMCAwLjAwMCByZw0KMC4w
MDAgVGMNCjk2LjE4NiBUeg0KKCBSb3V0ZXIgNzYwMCBzZXJpZXMsIHN3aXRjaCBwb3J0cyB3aXRo
IDkgc2xvdHMuKVRqDQpFVA0KQlQNCjEuMDAwIDAuMDAwIDAuMDAwIDEuMDAwIDM1LjA0MCAxNTYu
OTYwIFRtDQovRjUgOS45MDQgVGYNCjAgVHINCjAuMDAwIDAuMDAwIDAuMDAwIHJnDQowLjAwMCBU
Yw0KMTAzLjMzMyBUeg0KKFZNMSlUag0KRVQNCkJUDQoxLjAwMCAwLjAwMCAwLjAwMCAxLjAwMCA1
My43NjAgMTU2Ljk2MCBUbQ0KL0Y1IDkuOTA0IFRmDQowIFRyDQowLjAwMCAwLjAwMCAwLjAwMCBy
Zw0KMC4wMDAgVGMNCjc0Ljc3OSBUeg0KKCAtKVRqDQpFVA0KQlQNCjEuMDAwIDAuMDAwIDAuMDAw
IDEuMDAwIDYwLjk2MCAxNTYuOTYwIFRtDQovRjUgOS45MDQgVGYNCjAgVHINCjAuMDAwIDAuMDAw
IDAuMDAwIHJnDQowLjAwMCBUYw0KMTAzLjMzMyBUeg0KKFZNNilUag0KRVQNCkJUDQoxLjAwMCAw
LjAwMCAwLjAwMCAxLjAwMCA3OS42ODAgMTU2Ljk2MCBUbQ0KL0Y1IDkuOTA0IFRmDQowIFRyDQow
LjAwMCAwLjAwMCAwLjAwMCByZw0KMC4wMDAgVGMNCjkzLjMxNCBUeg0KKCA9IFZpcnR1YWwgTWFj
aGluZXMsIGluc3RhbGxlZClUag0KRVQNCkJUDQoxLjAwMCAwLjAwMCAwLjAwMCAxLjAwMCAxOTMu
NDQwIDE1Ni45NjAgVG0NCi9GNSA5LjkwNCBUZg0KMCBUcg0KMC4wMDAgMC4wMDAgMC4wMDAgcmcN
CjAuMDAwIFRjDQo5OC41MTEgVHoNCihVYnVudHUpVGoNCkVUDQpCVA0KMS4wMDAgMC4wMDAgMC4w
MDAgMS4wMDAgMjIyLjk2MCAxNTYuOTYwIFRtDQovRjUgOS45MDQgVGYNCjAgVHINCjAuMDAwIDAu
MDAwIDAuMDAwIHJnDQowLjAwMCBUYw0KODMuMjg0IFR6DQooIDEyLjA0KVRqDQpFVA0KQlQNCjEu
MDAwIDAuMDAwIDAuMDAwIDEuMDAwIDI0Ni43MjAgMTU2Ljk2MCBUbQ0KL0Y1IDkuOTA0IFRmDQow
IFRyDQowLjAwMCAwLjAwMCAwLjAwMCByZw0KMC4wMDAgVGMNCjkxLjg0NyBUeg0KKExUUylUag0K
RVQNCkJUDQoxLjAwMCAwLjAwMCAwLjAwMCAxLjAwMCAyNjIuNTYwIDE1Ni45NjAgVG0NCi9GNSA5
LjkwNCBUZg0KMCBUcg0KMC4wMDAgMC4wMDAgMC4wMDAgcmcNCjAuMDAwIFRjDQo5Ny44NTcgVHoN
CiggU2VydmVyKVRqDQpFVA0KQlQNCjEuMDAwIDAuMDAwIDAuMDAwIDEuMDAwIDM1LjA0MCAxMzUu
MzYwIFRtDQovRjcgOS45MDQgVGYNCjAgVHINCjAuMDAwIDAuMDAwIDAuMDAwIHJnDQowLjAwMCBU
Yw0KOTEuMjUwIFR6DQooUmVxdWlyZWQpVGoNCkVUDQpCVA0KMS4wMDAgMC4wMDAgMC4wMDAgMS4w
MDAgNzEuMDQwIDEzNS4zNjAgVG0NCi9GNSA5LjkwNCBUZg0KMCBUcg0KMC4wMDAgMC4wMDAgMC4w
MDAgcmcNCjAuMDAwIFRjDQo3Ni45MjMgVHoNCig6KVRqDQpFVA0KQlQNCjEuMDAwIDAuMDAwIDAu
MDAwIDEuMDAwIDM1LjA0MCAxMTMuNzYwIFRtDQovRjUgOS45MDQgVGYNCjAgVHINCjAuMDAwIDAu
MDAwIDAuMDAwIHJnDQowLjAwMCBUYw0KOTMuNDg0IFR6DQooSG93IGNhbiBJIGNvbmZpZ3VyZSBt
eSlUag0KRVQNCkJUDQoxLjAwMCAwLjAwMCAwLjAwMCAxLjAwMCAxMjguNjQwIDExMy43NjAgVG0N
Ci9GNSA5LjkwNCBUZg0KMCBUcg0KMC4wMDAgMC4wMDAgMC4wMDAgcmcNCjAuMDAwIFRjDQoxMDku
MTYyIFR6DQooVk1zKVRqDQpFVA0KQlQNCjEuMDAwIDAuMDAwIDAuMDAwIDEuMDAwIDE0Ny4zNjAg
MTEzLjc2MCBUbQ0KL0Y1IDkuOTA0IFRmDQowIFRyDQowLjAwMCAwLjAwMCAwLjAwMCByZw0KMC4w
MDAgVGMNCjk1LjQ2OCBUeg0KKCB0byBtZWV0IHRoZSBmb2xsb3dpbmcgc2V0dXAgb3IgbmV0d29y
az8pVGoNCkVUDQpCVA0KMS4wMDAgMC4wMDAgMC4wMDAgMS4wMDAgMzUuMDQwIDkyLjE2MCBUbQ0K
L0Y1IDkuOTA0IFRmDQowIFRyDQowLjAwMCAwLjAwMCAwLjAwMCByZw0KMC4wMDAgVGMNCjcxLjMz
MyBUeg0KKGlcKSlUag0KRVQNCkJUDQoxLjAwMCAwLjAwMCAwLjAwMCAxLjAwMCA0Mi4yNDAgOTIu
MTYwIFRtDQovRjUgOS45MDQgVGYNCjAgVHINCjAuMDAwIDAuMDAwIDAuMDAwIHJnDQowLjAwMCBU
Yw0KMTAzLjMzMyBUeg0KKFZNMSlUag0KRVQNCkJUDQoxLjAwMCAwLjAwMCAwLjAwMCAxLjAwMCA2
MC45NjAgOTIuMTYwIFRtDQovRjUgOS45MDQgVGYNCjAgVHINCjAuMDAwIDAuMDAwIDAuMDAwIHJn
DQowLjAwMCBUYw0KNzQuNzc5IFR6DQooIC0pVGoNCkVUDQpCVA0KMS4wMDAgMC4wMDAgMC4wMDAg
MS4wMDAgNjguMTYwIDkyLjE2MCBUbQ0KL0Y1IDkuOTA0IFRmDQowIFRyDQowLjAwMCAwLjAwMCAw
LjAwMCByZw0KMC4wMDAgVGMNCjEwMy4zMzMgVHoNCihWTTYpVGoNCkVUDQpCVA0KMS4wMDAgMC4w
MDAgMC4wMDAgMS4wMDAgODYuODgwIDkyLjE2MCBUbQ0KL0Y1IDkuOTA0IFRmDQowIFRyDQowLjAw
MCAwLjAwMCAwLjAwMCByZw0KMC4wMDAgVGMNCjk0LjI2MyBUeg0KKCA9IGJlIG9uIHRoZSBuZXR3
b3JrIHdpdGggLzI5KVRqDQpFVA0KQlQNCjEuMDAwIDAuMDAwIDAuMDAwIDEuMDAwIDM1LjA0MCA3
MC41NjAgVG0NCi9GNSA5LjkwNCBUZg0KMCBUcg0KMC4wMDAgMC4wMDAgMC4wMDAgcmcNCjAuMDAw
IFRjDQo3My43MTEgVHoNCihpaVwpKVRqDQpFVA0KQlQNCjEuMDAwIDAuMDAwIDAuMDAwIDEuMDAw
IDQ0LjQwMCA3MC41NjAgVG0NCi9GNSA5LjkwNCBUZg0KMCBUcg0KMC4wMDAgMC4wMDAgMC4wMDAg
cmcNCjAuMDAwIFRjDQo5NS41NTEgVHoNCihldGgwKVRqDQpFVA0KQlQNCjEuMDAwIDAuMDAwIDAu
MDAwIDEuMDAwIDYwLjk2MCA3MC41NjAgVG0NCi9GNSA5LjkwNCBUZg0KMCBUcg0KMC4wMDAgMC4w
MDAgMC4wMDAgcmcNCjAuMDAwIFRjDQo5Mi42NDggVHoNCiggYW5kIEdFIDcvMyA9IFBvaW50IHRv
IFBvaW50IExpbmsgb3IgbmV0d29yayBvZiAvMzApVGoNCkVUDQpCVA0KMS4wMDAgMC4wMDAgMC4w
MDAgMS4wMDAgMzUuMDQwIDQ4Ljk2MCBUbQ0KL0Y1IDkuOTA0IFRmDQowIFRyDQowLjAwMCAwLjAw
MCAwLjAwMCByZw0KMC4wMDAgVGMNCjk5LjA5OCBUeg0KKENhbiB0aGlzIGJlIHBvc3NpYmxlPyBp
ZiBub3Qgc3VnZ2VzdCB0aGUgYmVzdCBzZXR1cCBmb3IpVGoNCkVUDQpCVA0KMS4wMDAgMC4wMDAg
MC4wMDAgMS4wMDAgMjQ0LjU2MCA0OC45NjAgVG0NCi9GNSA5LjkwNCBUZg0KMCBUcg0KMC4wMDAg
MC4wMDAgMC4wMDAgcmcNCjAuMDAwIFRjDQoxMDkuMTYyIFR6DQooVk1zKVRqDQpFVA0KQlQNCjEu
MDAwIDAuMDAwIDAuMDAwIDEuMDAwIDI2My4yODAgNDguOTYwIFRtDQovRjUgOS45MDQgVGYNCjAg
VHINCjAuMDAwIDAuMDAwIDAuMDAwIHJnDQowLjAwMCBUYw0KOTIuNzk0IFR6DQooICAgd2l0aCBz
dGF0aWMpVGoNCkVUDQpCVA0KMS4wMDAgMC4wMDAgMC4wMDAgMS4wMDAgMzExLjUyMCA0OC45NjAg
VG0NCi9GNSA5LjkwNCBUZg0KMCBUcg0KMC4wMDAgMC4wMDAgMC4wMDAgcmcNCjAuMDAwIFRjDQo2
NS41MjAgVHoNCihJUClUag0KRVQNCkJUDQoxLjAwMCAwLjAwMCAwLjAwMCAxLjAwMCAzMTkuNDQw
IDQ4Ljk2MCBUbQ0KL0Y1IDkuOTA0IFRmDQowIFRyDQowLjAwMCAwLjAwMCAwLjAwMCByZw0KMC4w
MDAgVGMNCjg3LjQ1MyBUeg0KKC4uKVRqDQpFVA0KQlQNCjEuMDAwIDAuMDAwIDAuMDAwIDEuMDAw
IDM1LjA0MCAyNy4zNjAgVG0NCi9GNSA5LjkwNCBUZg0KMCBUcg0KMC4wMDAgMC4wMDAgMC4wMDAg
cmcNCjAuMDAwIFRjDQo5My45MjMgVHoNCihJIHRyaWVkIGJ1dCBmYWlsZWQsIGl0IGp1c3QgZ28g
dG8pVGoNCkVUDQpCVA0KMS4wMDAgMC4wMDAgMC4wMDAgMS4wMDAgMTQ1LjkyMCAyNy4zNjAgVG0N
Ci9GNSA5LjkwNCBUZg0KMCBUcg0KMC4wMDAgMC4wMDAgMC4wMDAgcmcNCjAuMDAwIFRjDQo5OS41
NjEgVHoNCihkaGNwKVRqDQpFVA0KQlQNCjEuMDAwIDAuMDAwIDAuMDAwIDEuMDAwIDE2NS4zNjAg
MjcuMzYwIFRtDQovRjUgOS45MDQgVGYNCjAgVHINCjAuMDAwIDAuMDAwIDAuMDAwIHJnDQowLjAw
MCBUYw0KOTkuMzQ1IFR6DQooIGFuZCBJIG5lZWQgc3RhdGljLilUag0KRVQNCkJUDQoxLjAwMCAw
LjAwMCAwLjAwMCAxLjAwMCAzNS4wNDAgNS43NjAgVG0NCi9GNSA5LjkwNCBUZg0KMCBUcg0KMC4w
MDAgMC4wMDAgMC4wMDAgcmcNCjAuMDAwIFRjDQo5OS40NDAgVHoNCihQbGVhc2UgaGVscC4pVGoN
CkVUDQpRDQplbmRzdHJlYW0NCmVuZG9iag0KNiAwIG9iag0KODA4ODgNCmVuZG9iag0KNyAwIG9i
ag0KPDwNCi9UeXBlIC9Gb250DQovU3VidHlwZSAvVHlwZTENCi9OYW1lIC9GMg0KL0Jhc2VGb250
IC9BcmlhbA0KL0ZvbnREZXNjcmlwdG9yIDggMCBSDQovRW5jb2RpbmcgL1dpbkFuc2lFbmNvZGlu
Zw0KPj4NCmVuZG9iag0KOCAwIG9iag0KPDwNCi9UeXBlIC9Gb250RGVzY3JpcHRvcg0KL0FzY2Vu
dCAxMDAwDQovQ2FwSGVpZ2h0IDg5Ng0KL0Rlc2NlbnQgLTIzMg0KL0ZsYWdzIDMyDQovRm9udEJC
b3ggWzAgMCAwIDAgXQ0KL0ZvbnROYW1lIC9BcmlhbA0KL0l0YWxpY0FuZ2xlIC0xMQ0KL1N0ZW1W
IDgwDQo+Pg0KZW5kb2JqDQo5IDAgb2JqDQo8PA0KL1R5cGUgL0ZvbnQNCi9TdWJ0eXBlIC9UeXBl
MQ0KL05hbWUgL0YzDQovQmFzZUZvbnQgL0FyaWFsDQovRm9udERlc2NyaXB0b3IgMTAgMCBSDQov
RW5jb2RpbmcgL1dpbkFuc2lFbmNvZGluZw0KPj4NCmVuZG9iag0KMTAgMCBvYmoNCjw8DQovVHlw
ZSAvRm9udERlc2NyaXB0b3INCi9Bc2NlbnQgMTAwMA0KL0NhcEhlaWdodCA4OTcNCi9EZXNjZW50
IC0yMzQNCi9GbGFncyAzMg0KL0ZvbnRCQm94IFswIDAgMCAwIF0NCi9Gb250TmFtZSAvQXJpYWwN
Ci9JdGFsaWNBbmdsZSAtMTENCi9TdGVtViA4MA0KPj4NCmVuZG9iag0KMTEgMCBvYmoNCjw8DQov
VHlwZSAvRm9udA0KL1N1YnR5cGUgL1RydWVUeXBlDQovTmFtZSAvRjUNCi9CYXNlRm9udCAvVGlt
ZXNOZXdSb21hbg0KL0ZvbnREZXNjcmlwdG9yIDEyIDAgUg0KL0VuY29kaW5nIC9XaW5BbnNpRW5j
b2RpbmcNCj4+DQplbmRvYmoNCjEyIDAgb2JqDQo8PA0KL1R5cGUgL0ZvbnREZXNjcmlwdG9yDQov
QXNjZW50IDEwMDANCi9DYXBIZWlnaHQgOTAyDQovRGVzY2VudCAtMjQzDQovRmxhZ3MgMzQNCi9G
b250QkJveCBbMCAwIDAgMCBdDQovRm9udE5hbWUgL1RpbWVzTmV3Um9tYW4NCi9JdGFsaWNBbmds
ZSAtMTENCi9TdGVtViA4MA0KPj4NCmVuZG9iag0KMTMgMCBvYmoNCjw8DQovVHlwZSAvRm9udA0K
L1N1YnR5cGUgL1RydWVUeXBlDQovTmFtZSAvRjcNCi9CYXNlRm9udCAvVGltZXNOZXdSb21hbg0K
L0ZvbnREZXNjcmlwdG9yIDE0IDAgUg0KL0VuY29kaW5nIC9XaW5BbnNpRW5jb2RpbmcNCj4+DQpl
bmRvYmoNCjE0IDAgb2JqDQo8PA0KL1R5cGUgL0ZvbnREZXNjcmlwdG9yDQovQXNjZW50IDEwMDAN
Ci9DYXBIZWlnaHQgOTAyDQovRGVzY2VudCAtMjQzDQovRmxhZ3MgMzQNCi9Gb250QkJveCBbMCAw
IDAgMCBdDQovRm9udE5hbWUgL1RpbWVzTmV3Um9tYW4NCi9JdGFsaWNBbmdsZSAtMTENCi9TdGVt
ViA4MA0KPj4NCmVuZG9iag0KMyAwIG9iag0KPDwNCi9UeXBlIC9QYWdlDQovUGFyZW50IDQgMCBS
DQovTWVkaWFCb3ggWyAwIDAgMzk3IDQyOSBdDQovUmVzb3VyY2VzDQo8PA0KL1Byb2NTZXQgWy9Q
REYgL1RleHQgL0ltYWdlQiAvSW1hZ2VDIC9JbWFnZUldDQovRm9udA0KPDwNCi9GMiA3IDAgUg0K
L0YzIDkgMCBSDQovRjUgMTEgMCBSDQovRjcgMTMgMCBSDQo+Pg0KPj4NCi9Db250ZW50cyA1IDAg
Ug0KPj4NCmVuZG9iag0KNCAwIG9iag0KPDwNCi9UeXBlIC9QYWdlcw0KL0tpZHMgWyAzIDAgUiBd
DQovQ291bnQgMQ0KPj4NCmVuZG9iag0KMSAwIG9iag0KPDwNCi9UeXBlIC9DYXRhbG9nDQovUGFn
ZXMgNCAwIFINCj4+DQplbmRvYmoNCjIgMCBvYmoNCjw8DQovUHJvZHVjZXIgKEluc28gS2Fuc2Fz
IENpdHkgRXhwb3J0IFBERiBmaWx0ZXIpDQo+Pg0KZW5kb2JqDQp4cmVmDTAgMTUNMDAwMDAwMDAw
MCA2NTUzNSBmDQowMDAwMDgyNTYwIDAwMDAwIG4NCjAwMDAwODI2MTUgMDAwMDAgbg0KMDAwMDA4
MjI2OSAwMDAwMCBuDQowMDAwMDgyNDk0IDAwMDAwIG4NCjAwMDAwMDAwMjAgMDAwMDAgbg0KMDAw
MDA4MDk2NyAwMDAwMCBuDQowMDAwMDgwOTkxIDAwMDAwIG4NCjAwMDAwODExMjYgMDAwMDAgbg0K
MDAwMDA4MTI5OSAwMDAwMCBuDQowMDAwMDgxNDM1IDAwMDAwIG4NCjAwMDAwODE2MDkgMDAwMDAg
bg0KMDAwMDA4MTc1NyAwMDAwMCBuDQowMDAwMDgxOTM5IDAwMDAwIG4NCjAwMDAwODIwODcgMDAw
MDAgbg0KdHJhaWxlcg0KPDwNCi9TaXplIDE1DS9JbmZvIDIgMCBSDQovUm9vdCAxIDAgUg0KPj4N
CnN0YXJ0eHJlZg04MjY4OA0lJUVPRg0=
--f46d043c822079331f04caea6d93
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
Xen-users mailing list
Xen-users@lists.xen.org
http://lists.xen.org/xen-users
--f46d043c822079331f04caea6d93--


From xen-users-bounces@lists.xen.org Sun Sep 30 12:30:16 2012
Return-path: 
Envelope-to: archives@lists.xen.org
Delivery-date: Sun, 30 Sep 2012 12:30:16 +0000
Received: from localhost ([127.0.0.1] helo=lists.xen.org)
	by lists.xen.org with esmtp (Exim 4.72)
	(envelope-from )
	id 1TIIdb-0007XY-8z; Sun, 30 Sep 2012 12:28:47 +0000
Received: from mail6.bemta5.messagelabs.com ([195.245.231.135])
	by lists.xen.org with esmtp (Exim 4.72)
	(envelope-from ) id 1TIIdZ-0007XQ-FP
	for xen-users@lists.xen.org; Sun, 30 Sep 2012 12:28:46 +0000
Received: from [85.158.139.211:31843] by server-4.bemta-5.messagelabs.com id
	7C/E9-20767-CFA38605; Sun, 30 Sep 2012 12:28:44 +0000
X-Env-Sender: damas.makweba@ternet.or.tz
X-Msg-Ref: server-4.tower-206.messagelabs.com!1349008115!20510953!1
X-Originating-IP: [209.85.220.173]
X-SpamReason: No, hits=0.4 required=7.0 tests=HTML_30_40,HTML_MESSAGE,
	ML_RADAR_SPEW_LINKS_8,RCVD_BY_IP,spamassassin: ,async_handler: 
	YXN5bmNfZGVsYXk6IDcwNDQ5MDcgKHRpbWVvdXQp\n
X-StarScan-Received: 
X-StarScan-Version: 6.6.1.3; banners=-,-,-
X-VirusChecked: Checked
Received: (qmail 2120 invoked from network); 30 Sep 2012 12:28:36 -0000
Received: from mail-vc0-f173.google.com (HELO mail-vc0-f173.google.com)
	(209.85.220.173)
	by server-4.tower-206.messagelabs.com with RC4-SHA encrypted SMTP;
	30 Sep 2012 12:28:36 -0000
Received: by vcbfl15 with SMTP id fl15so5923404vcb.32
	for ; Sun, 30 Sep 2012 05:28:34 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
	d=google.com; s=20120113;
	h=mime-version:x-originating-ip:date:message-id:subject:from:to
	:content-type:x-gm-message-state;
	bh=Z31Ib8mX2VzBiaTmW1whHByPb/KMh7X6W78P2jIEq/o=;
	b=DMJP0NgxoC+kN61/LjUXydLkvu4oTIcx7MYb0sS4j1lR9XWU2XM45i41UFsy9yjz5c
	3FPe/88vHccbdW4AjeX3OT8RZ8F5Rq/tbjL2EZUYQEAG/XL3VRJ889fQ4Xby6kmPQcng
	FR4S/PEe56j34XJjbhO/2Jme+EoW9AJELhQVuq9gU8X/kT5lnyx29Gp9/9JfvWX8ZSej
	semy7h+QPzm9e3GqADDjFsMv0DFuaP1GyovF6FJFCdeBqqP9Rtp1w9N8DImWSmFRdBfP
	f8Ja5gPltJk2s/rRIBFlbQ0TPcp6l0cNf1dhe3NVMKfcrOfpD7u8MGxpqpXZ8k2uP344
	quyw==
MIME-Version: 1.0
Received: by 10.220.149.142 with SMTP id t14mr6786285vcv.46.1349008114659;
	Sun, 30 Sep 2012 05:28:34 -0700 (PDT)
Received: by 10.220.211.12 with HTTP; Sun, 30 Sep 2012 05:28:34 -0700 (PDT)
X-Originating-IP: [41.93.32.9]
Date: Sun, 30 Sep 2012 15:28:34 +0300
Message-ID: 
From: "Damas A.Makweba" 
To: xen-users@lists.xen.org
Content-Type: multipart/mixed; boundary=f46d043c822079331f04caea6d93
X-Gm-Message-State: ALoCoQkvXU2ZfrzvxShZsX7MFEyowJ15fWfFrOf1GiZNCH/keq6z5x5zArD83UY19MkY4tPWZSGp
Subject: [Xen-users] Networking
X-BeenThere: xen-users@lists.xen.org
X-Mailman-Version: 2.1.13
Precedence: list
List-Id: Xen user discussion 
List-Unsubscribe: ,
	
List-Post: 
List-Help: 
List-Subscribe: ,
	
Sender: xen-users-bounces@lists.xen.org
Errors-To: xen-users-bounces@lists.xen.org

--f46d043c822079331f04caea6d93
Content-Type: multipart/alternative; boundary=f46d043c822079331604caea6d91

--f46d043c822079331604caea6d91
Content-Type: text/plain; charset=ISO-8859-1

Greetings all,

I need help with xen networking, I am not good to set up xen.

Please, pass through the xen.pdf file attached in which i tried to let you
know how my settings should be.

I have a server, installed and configured with Ubuntu 12.04LTS server and
Xen 4.0, it contains 6doms ie VMs, i need to set up doms with static IP
rather than dhcp, I need to connect the server direct to cisco router which
is the 7600 series switch ports, please help me.

Regards,

-- 
Damas A.M
**
Network Engineer
Tanzania Education & Research Network


*Mob: +255 (0) 714/ 754/ 784 - 46 46 78*

--f46d043c822079331604caea6d91
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

Greetings all,

I need help with xen networking, I am not good to set=
 up xen.

Please, pass through the xen.pdf file attached in which i t=
ried to let you know how my settings should be.

I have a server, ins=
talled and configured with Ubuntu 12.04LTS server and Xen 4.0, it contains =
6doms ie VMs, i need to set up doms with static IP rather than dhcp, I need=
 to connect the server direct to cisco router which is the 7600 series swit=
ch ports, please help me.


Regards,

-- 
Damas A.M
Network Engineer
<=
div>Tanzania Educatio=
n & Research Network 



Mob: +255 (0) 714/ 754/ 784 - 46 46 78



--f46d043c822079331604caea6d91--
--f46d043c822079331f04caea6d93
Content-Type: application/pdf; name="xen.pdf"
Content-Disposition: attachment; filename="xen.pdf"
Content-Transfer-Encoding: base64
X-Attachment-Id: f_h7q4gnho0

JVBERi0xLjENCiXi48/TAAAADQo1IDAgb2JqDQo8PA0KL0xlbmd0aCA2IDAgUg0KPj4NCnN0cmVh
bQ0KcQ0KMC41MDIgMC41MDIgMC41MDIgcmcNCjAuMDAwIDAuMDAwIDAuMDAwIFJHDQowLjAwMCB3
DQpbIF0gMCBkDQoxIEoNCjEgag0KNTYuNjQwIDM0MC4wODAgbQ0KMjYuMDQwIDMwNC42ODAgbA0K
MTc5LjA0MCAzMDQuNjgwIGwNCjE0OC41NjAgMzQwLjA4MCBsDQo1Ni42NDAgMzQwLjA4MCBsDQpi
Kg0KMC4wMDAgMC4wMDAgMC4wMDAgcmcNCjAuMDAwIDAuMDAwIDAuMDAwIFJHDQowLjAwMCB3DQpb
IF0gMCBkDQoxIEoNCjEgag0KNTYuNjQwIDM0MC4wODAgbQ0KMjYuMDQwIDMwNC41NjAgbA0KMTc5
LjA0MCAzMDQuNTYwIGwNCjE0OC41NjAgMzQwLjA4MCBsDQo1Ni42NDAgMzQwLjA4MCBsDQo1Ni43
NjAgMzM5Ljg0MCBsDQoxNDguNDQwIDMzOS44NDAgbA0KMTc4LjQ0MCAzMDQuOTIwIGwNCjI2Ljc2
MCAzMDQuOTIwIGwNCjU2Ljc2MCAzMzkuODQwIGwNCjU2LjY0MCAzNDAuMDgwIGwNCmYqDQowLjYy
NyAwLjYyNyAwLjY0MyByZw0KMC4wMDAgMC4wMDAgMC4wMDAgUkcNCjAuMjQwIHcNClsgXSAwIGQN
CjEgSg0KMSBqDQozMC4wMDAgMzA5LjM2MCBtDQozMC4zNjAgMzA5LjM2MCBsDQozMC43MjAgMzA5
LjM2MCBsDQozMS4wODAgMzA5LjM2MCBsDQozMS40NDAgMzA5LjM2MCBsDQozMS45MjAgMzA5LjI0
MCBsDQozMi4yODAgMzA5LjI0MCBsDQozMi42NDAgMzA5LjEyMCBsDQozMy4wMDAgMzA5LjEyMCBs
DQozMy4zNjAgMzA5LjEyMCBsDQozMy43MjAgMzA5LjEyMCBsDQozNC4wODAgMzA5LjAwMCBsDQoz
NC41NjAgMzA5LjAwMCBsDQozNC45MjAgMzA5LjAwMCBsDQozNS4yODAgMzA4Ljg4MCBsDQozNS42
NDAgMzA4Ljg4MCBsDQozNi4xMjAgMzA4Ljg4MCBsDQozNi40ODAgMzA4Ljg4MCBsDQozNi44NDAg
MzA4Ljc2MCBsDQozNy4zMjAgMzA4Ljc2MCBsDQozNy42ODAgMzA4Ljc2MCBsDQozOC4wNDAgMzA4
LjY0MCBsDQozOC41MjAgMzA4LjY0MCBsDQozOC44ODAgMzA4LjY0MCBsDQozOS4zNjAgMzA4LjY0
MCBsDQozOS43MjAgMzA4LjUyMCBsDQo0MC4yMDAgMzA4LjUyMCBsDQo0MC41NjAgMzA4LjUyMCBs
DQo0MS4wNDAgMzA4LjQwMCBsDQo0MS41MjAgMzA4LjQwMCBsDQo0MS44ODAgMzA4LjQwMCBsDQo0
Mi4zNjAgMzA4LjQwMCBsDQo0Mi43MjAgMzA4LjI4MCBsDQo0My4yMDAgMzA4LjI4MCBsDQo0My42
ODAgMzA4LjE2MCBsDQo0NC4xNjAgMzA4LjE2MCBsDQo0NC41MjAgMzA4LjE2MCBsDQo0NS4wMDAg
MzA4LjA0MCBsDQo0NS40ODAgMzA4LjA0MCBsDQo0NS45NjAgMzA4LjA0MCBsDQo0Ni40NDAgMzA4
LjA0MCBsDQo0Ni45MjAgMzA3LjkyMCBsDQo0Ny40MDAgMzA3LjkyMCBsDQo0Ny44ODAgMzA3Ljky
MCBsDQo0OC4zNjAgMzA3LjgwMCBsDQo0OC44NDAgMzA3LjgwMCBsDQo0OS4zMjAgMzA3LjgwMCBs
DQo0OS44MDAgMzA3LjgwMCBsDQo1MC4yODAgMzA3LjY4MCBsDQo1MC43NjAgMzA3LjY4MCBsDQo1
MS4zNjAgMzA3LjY4MCBsDQo1MS44NDAgMzA3LjU2MCBsDQo1Mi40NDAgMzA3LjU2MCBsDQo1Mi45
MjAgMzA3LjU2MCBsDQo1My41MjAgMzA3LjU2MCBsDQo1NC4wMDAgMzA3LjQ0MCBsDQo1NC40ODAg
MzA3LjQ0MCBsDQo1NS4wODAgMzA3LjMyMCBsDQo1NS42ODAgMzA3LjMyMCBsDQo1Ni4xNjAgMzA3
LjMyMCBsDQo1Ni43NjAgMzA3LjMyMCBsDQo1Ny4zNjAgMzA3LjMyMCBsDQo1Ny45NjAgMzA3LjIw
MCBsDQo1OC41NjAgMzA3LjIwMCBsDQo1OS4xNjAgMzA3LjA4MCBsDQo1OS43NjAgMzA3LjA4MCBs
DQo2MC4zNjAgMzA3LjA4MCBsDQo2MS4wODAgMzA3LjA4MCBsDQo2MS42ODAgMzA2Ljk2MCBsDQo2
Mi40MDAgMzA2Ljk2MCBsDQo2My4wMDAgMzA2Ljk2MCBsDQo2My43MjAgMzA2Ljg0MCBsDQo2NC40
NDAgMzA2Ljg0MCBsDQo2NS4wNDAgMzA2Ljg0MCBsDQo2NS43NjAgMzA2Ljg0MCBsDQo2Ni40ODAg
MzA2LjcyMCBsDQo2Ny4zMjAgMzA2LjcyMCBsDQo2OC4wNDAgMzA2LjcyMCBsDQo2OC44ODAgMzA2
LjYwMCBsDQo2OS42MDAgMzA2LjYwMCBsDQo3MC40NDAgMzA2LjYwMCBsDQo3MS4yODAgMzA2LjYw
MCBsDQo3Mi4xMjAgMzA2LjQ4MCBsDQo3My4wODAgMzA2LjQ4MCBsDQo3My45MjAgMzA2LjQ4MCBs
DQo3NC44ODAgMzA2LjM2MCBsDQo3NS45NjAgMzA2LjM2MCBsDQo3Ni45MjAgMzA2LjM2MCBsDQo3
OC4wMDAgMzA2LjM2MCBsDQo3OS4wODAgMzA2LjI0MCBsDQo4MC4yODAgMzA2LjI0MCBsDQo4MS40
ODAgMzA2LjEyMCBsDQo4Mi45MjAgMzA2LjEyMCBsDQo4NC4yNDAgMzA2LjEyMCBsDQo4NS44MDAg
MzA2LjEyMCBsDQo4Ny42MDAgMzA2LjAwMCBsDQo4OS41MjAgMzA2LjAwMCBsDQo5MS44MDAgMzA2
LjAwMCBsDQo5NC44MDAgMzA1Ljg4MCBsDQoxMDIuMDAwIDMwNS44ODAgbA0KMTA5LjQ0MCAzMDUu
ODgwIGwNCjExMi40NDAgMzA2LjAwMCBsDQoxMTQuODQwIDMwNi4wMDAgbA0KMTE2Ljc2MCAzMDYu
MTIwIGwNCjExOC40NDAgMzA2LjEyMCBsDQoxMjAuMTIwIDMwNi4xMjAgbA0KMTIxLjU2MCAzMDYu
MTIwIGwNCjEyMi44ODAgMzA2LjI0MCBsDQoxMjQuMjAwIDMwNi4yNDAgbA0KMTI1LjQwMCAzMDYu
MjQwIGwNCjEyNi40ODAgMzA2LjM2MCBsDQoxMjcuNTYwIDMwNi4zNjAgbA0KMTI4LjY0MCAzMDYu
MzYwIGwNCjEyOS42MDAgMzA2LjM2MCBsDQoxMzAuNTYwIDMwNi40ODAgbA0KMTMxLjUyMCAzMDYu
NDgwIGwNCjEzMi40ODAgMzA2LjYwMCBsDQoxMzMuMzIwIDMwNi42MDAgbA0KMTM0LjE2MCAzMDYu
NjAwIGwNCjEzNS4wMDAgMzA2LjYwMCBsDQoxMzUuODQwIDMwNi43MjAgbA0KMTM2LjY4MCAzMDYu
NzIwIGwNCjEzNy40MDAgMzA2LjcyMCBsDQoxMzguMjQwIDMwNi44NDAgbA0KMTM4Ljk2MCAzMDYu
ODQwIGwNCjEzOS42ODAgMzA2Ljg0MCBsDQoxNDAuNDAwIDMwNi44NDAgbA0KMTQxLjEyMCAzMDYu
OTYwIGwNCjE0MS43MjAgMzA2Ljk2MCBsDQoxNDIuNDQwIDMwNy4wODAgbA0KMTQzLjE2MCAzMDcu
MDgwIGwNCjE0My43NjAgMzA3LjA4MCBsDQoxNDQuNDgwIDMwNy4wODAgbA0KMTQ1LjA4MCAzMDcu
MjAwIGwNCjE0NS42ODAgMzA3LjIwMCBsDQoxNDYuMjgwIDMwNy4yMDAgbA0KMTQ2Ljg4MCAzMDcu
MzIwIGwNCjE0Ny40ODAgMzA3LjMyMCBsDQoxNDguMjAwIDMwNy4zMjAgbA0KMTQ4LjY4MCAzMDcu
MzIwIGwNCjE0OS4yODAgMzA3LjQ0MCBsDQoxNDkuODgwIDMwNy40NDAgbA0KMTUwLjQ4MCAzMDcu
NTYwIGwNCjE1MC45NjAgMzA3LjU2MCBsDQoxNTEuNTYwIDMwNy41NjAgbA0KMTUyLjA0MCAzMDcu
NTYwIGwNCjE1Mi42NDAgMzA3LjY4MCBsDQoxNTMuMTIwIDMwNy42ODAgbA0KMTUzLjcyMCAzMDcu
NjgwIGwNCjE1NC4yMDAgMzA3LjgwMCBsDQoxNTQuODAwIDMwNy44MDAgbA0KMTU1LjI4MCAzMDcu
ODAwIGwNCjE1NS43NjAgMzA3LjgwMCBsDQoxNTYuMjQwIDMwNy45MjAgbA0KMTU2LjcyMCAzMDcu
OTIwIGwNCjE1Ny4yMDAgMzA3LjkyMCBsDQoxNTcuODAwIDMwOC4wNDAgbA0KMTU4LjI4MCAzMDgu
MDQwIGwNCjE1OC43NjAgMzA4LjA0MCBsDQoxNTkuMjQwIDMwOC4xNjAgbA0KMTU5LjcyMCAzMDgu
MTYwIGwNCjE2MC4yMDAgMzA4LjE2MCBsDQoxNjAuNjgwIDMwOC4yODAgbA0KMTYxLjA0MCAzMDgu
MjgwIGwNCjE2MS41MjAgMzA4LjI4MCBsDQoxNjIuMDAwIDMwOC40MDAgbA0KMTYyLjQ4MCAzMDgu
NDAwIGwNCjE2Mi44NDAgMzA4LjQwMCBsDQoxNjMuMzIwIDMwOC40MDAgbA0KMTYzLjgwMCAzMDgu
NTIwIGwNCjE2NC4yODAgMzA4LjUyMCBsDQoxNjQuNjQwIDMwOC42NDAgbA0KMTY1LjEyMCAzMDgu
NjQwIGwNCjE2NS42MDAgMzA4LjY0MCBsDQoxNjUuOTYwIDMwOC42NDAgbA0KMTY2LjMyMCAzMDgu
NzYwIGwNCjE2Ni44MDAgMzA4Ljc2MCBsDQoxNjcuMjgwIDMwOC43NjAgbA0KMTY3LjY0MCAzMDgu
ODgwIGwNCjE2OC4wMDAgMzA4Ljg4MCBsDQoxNjguNDgwIDMwOC44ODAgbA0KMTY4Ljg0MCAzMDgu
ODgwIGwNCjE2OS4yMDAgMzA5LjAwMCBsDQoxNjkuNjgwIDMwOS4wMDAgbA0KMTcwLjA0MCAzMDku
MTIwIGwNCjE3MC41MjAgMzA5LjEyMCBsDQoxNzAuODgwIDMwOS4xMjAgbA0KMTcxLjI0MCAzMDku
MTIwIGwNCjE3MS43MjAgMzA5LjI0MCBsDQoxNzIuMDgwIDMwOS4yNDAgbA0KMTcyLjQ0MCAzMDku
MjQwIGwNCjE3Mi44MDAgMzA5LjM2MCBsDQoxNzMuMTYwIDMwOS4zNjAgbA0KMTczLjY0MCAzMDku
MzYwIGwNCjE3NC4wMDAgMzA5LjM2MCBsDQoxNzQuMzYwIDMwOS40ODAgbA0KMTc0LjcyMCAzMDku
NDgwIGwNCjE3NS4wODAgMzA5LjYwMCBsDQoxNzUuNDQwIDMwOS42MDAgbA0KMTc1LjIwMCAzMDku
NDgwIGwNCjE3NS42ODAgMjgwLjgwMCBsDQoxNzUuMzIwIDI4MC44MDAgbA0KMTc0Ljk2MCAyODAu
ODAwIGwNCjE3NC42MDAgMjgwLjY4MCBsDQoxNzQuMTIwIDI4MC42ODAgbA0KMTczLjg4MCAyODAu
NjgwIGwNCjE3My40MDAgMjgwLjU2MCBsDQoxNzMuMDQwIDI4MC41NjAgbA0KMTcyLjY4MCAyODAu
NTYwIGwNCjE3Mi4zMjAgMjgwLjQ0MCBsDQoxNzEuOTYwIDI4MC40NDAgbA0KMTcxLjQ4MCAyODAu
NDQwIGwNCjE3MS4xMjAgMjgwLjMyMCBsDQoxNzAuNzYwIDI4MC4zMjAgbA0KMTcwLjI4MCAyODAu
MzIwIGwNCjE2OS45MjAgMjgwLjMyMCBsDQoxNjkuNTYwIDI4MC4yMDAgbA0KMTY5LjIwMCAyODAu
MjAwIGwNCjE2OC43MjAgMjgwLjA4MCBsDQoxNjguMzYwIDI4MC4wODAgbA0KMTY3Ljg4MCAyODAu
MDgwIGwNCjE2Ny41MjAgMjgwLjA4MCBsDQoxNjcuMDQwIDI3OS45NjAgbA0KMTY2LjY4MCAyNzku
OTYwIGwNCjE2Ni4zMjAgMjc5Ljk2MCBsDQoxNjUuODQwIDI3OS44NDAgbA0KMTY1LjM2MCAyNzku
ODQwIGwNCjE2NS4wMDAgMjc5Ljg0MCBsDQoxNjQuNTIwIDI3OS44NDAgbA0KMTY0LjA0MCAyNzku
NzIwIGwNCjE2My42ODAgMjc5LjcyMCBsDQoxNjMuMjAwIDI3OS42MDAgbA0KMTYyLjcyMCAyNzku
NjAwIGwNCjE2Mi4zNjAgMjc5LjYwMCBsDQoxNjEuODgwIDI3OS42MDAgbA0KMTYxLjQwMCAyNzku
NDgwIGwNCjE2MC45MjAgMjc5LjQ4MCBsDQoxNjAuNDQwIDI3OS40ODAgbA0KMTU5Ljk2MCAyNzku
MzYwIGwNCjE1OS42MDAgMjc5LjM2MCBsDQoxNTkuMTIwIDI3OS4zNjAgbA0KMTU4LjY0MCAyNzku
MzYwIGwNCjE1OC4xNjAgMjc5LjI0MCBsDQoxNTcuNjgwIDI3OS4yNDAgbA0KMTU3LjA4MCAyNzku
MTIwIGwNCjE1Ni42MDAgMjc5LjEyMCBsDQoxNTYuMTIwIDI3OS4xMjAgbA0KMTU1LjY0MCAyNzku
MDAwIGwNCjE1NS4xNjAgMjc5LjAwMCBsDQoxNTQuNTYwIDI3OS4wMDAgbA0KMTU0LjA4MCAyNzku
MDAwIGwNCjE1My42MDAgMjc4Ljg4MCBsDQoxNTMuMDAwIDI3OC44ODAgbA0KMTUyLjUyMCAyNzgu
NzYwIGwNCjE1MS45MjAgMjc4Ljc2MCBsDQoxNTEuMzIwIDI3OC43NjAgbA0KMTUwLjg0MCAyNzgu
NzYwIGwNCjE1MC4yNDAgMjc4LjY0MCBsDQoxNDkuNjQwIDI3OC42NDAgbA0KMTQ5LjE2MCAyNzgu
NjQwIGwNCjE0OC41NjAgMjc4LjUyMCBsDQoxNDcuOTYwIDI3OC41MjAgbA0KMTQ3LjM2MCAyNzgu
NTIwIGwNCjE0Ni43NjAgMjc4LjQwMCBsDQoxNDYuMTYwIDI3OC40MDAgbA0KMTQ1LjQ0MCAyNzgu
NDAwIGwNCjE0NC44NDAgMjc4LjI4MCBsDQoxNDQuMjQwIDI3OC4yODAgbA0KMTQzLjUyMCAyNzgu
MjgwIGwNCjE0Mi45MjAgMjc4LjI4MCBsDQoxNDIuMzIwIDI3OC4xNjAgbA0KMTQxLjQ4MCAyNzgu
MTYwIGwNCjE0MC44ODAgMjc4LjA0MCBsDQoxNDAuMTYwIDI3OC4wNDAgbA0KMTM5LjQ0MCAyNzgu
MDQwIGwNCjEzOC43MjAgMjc4LjA0MCBsDQoxMzcuODgwIDI3Ny45MjAgbA0KMTM3LjE2MCAyNzcu
OTIwIGwNCjEzNi4zMjAgMjc3LjkyMCBsDQoxMzUuNjAwIDI3Ny44MDAgbA0KMTM0LjY0MCAyNzcu
ODAwIGwNCjEzMy45MjAgMjc3LjgwMCBsDQoxMzIuOTYwIDI3Ny44MDAgbA0KMTMyLjEyMCAyNzcu
NjgwIGwNCjEzMS4xNjAgMjc3LjY4MCBsDQoxMzAuMjAwIDI3Ny41NjAgbA0KMTI5LjI0MCAyNzcu
NTYwIGwNCjEyOC4xNjAgMjc3LjU2MCBsDQoxMjcuMDgwIDI3Ny41NjAgbA0KMTI1Ljg4MCAyNzcu
NDQwIGwNCjEyNC42ODAgMjc3LjQ0MCBsDQoxMjMuNDgwIDI3Ny40NDAgbA0KMTIyLjE2MCAyNzcu
MzIwIGwNCjEyMC43MjAgMjc3LjMyMCBsDQoxMTkuMTYwIDI3Ny4zMjAgbA0KMTE3LjM2MCAyNzcu
MzIwIGwNCjExNS40NDAgMjc3LjIwMCBsDQoxMTMuMDQwIDI3Ny4yMDAgbA0KMTEwLjA0MCAyNzcu
MDgwIGwNCjEwMi43MjAgMjc3LjA4MCBsDQo5NS40MDAgMjc3LjA4MCBsDQo5Mi40MDAgMjc3LjIw
MCBsDQo5MC4wMDAgMjc3LjIwMCBsDQo4OC4wODAgMjc3LjMyMCBsDQo4Ni40MDAgMjc3LjMyMCBs
DQo4NC43MjAgMjc3LjMyMCBsDQo4My4yODAgMjc3LjMyMCBsDQo4MS45NjAgMjc3LjQ0MCBsDQo4
MC43NjAgMjc3LjQ0MCBsDQo3OS41NjAgMjc3LjQ0MCBsDQo3OC4zNjAgMjc3LjU2MCBsDQo3Ny4y
ODAgMjc3LjU2MCBsDQo3Ni4zMjAgMjc3LjU2MCBsDQo3NS4zNjAgMjc3LjU2MCBsDQo3NC4yODAg
Mjc3LjY4MCBsDQo3My4zMjAgMjc3LjY4MCBsDQo3Mi40ODAgMjc3LjgwMCBsDQo3MS42NDAgMjc3
LjgwMCBsDQo3MC44MDAgMjc3LjgwMCBsDQo2OS45NjAgMjc3LjgwMCBsDQo2OS4xMjAgMjc3Ljky
MCBsDQo2OC4yODAgMjc3LjkyMCBsDQo2Ny41NjAgMjc3LjkyMCBsDQo2Ni43MjAgMjc4LjA0MCBs
DQo2Ni4wMDAgMjc4LjA0MCBsDQo2NS4yODAgMjc4LjA0MCBsDQo2NC41NjAgMjc4LjE2MCBsDQo2
My45NjAgMjc4LjE2MCBsDQo2My4yNDAgMjc4LjE2MCBsDQo2Mi41MjAgMjc4LjI4MCBsDQo2MS45
MjAgMjc4LjI4MCBsDQo2MS4yMDAgMjc4LjI4MCBsDQo2MC42MDAgMjc4LjI4MCBsDQo2MC4wMDAg
Mjc4LjQwMCBsDQo1OS40MDAgMjc4LjQwMCBsDQo1OC42ODAgMjc4LjUyMCBsDQo1OC4wODAgMjc4
LjUyMCBsDQo1Ny40ODAgMjc4LjUyMCBsDQo1Ni44ODAgMjc4LjUyMCBsDQo1Ni40MDAgMjc4LjY0
MCBsDQo1NS44MDAgMjc4LjY0MCBsDQo1NS4yMDAgMjc4LjY0MCBsDQo1NC42MDAgMjc4Ljc2MCBs
DQo1NC4xMjAgMjc4Ljc2MCBsDQo1My41MjAgMjc4Ljc2MCBsDQo1My4wNDAgMjc4Ljc2MCBsDQo1
Mi40NDAgMjc4Ljg4MCBsDQo1MS45NjAgMjc4Ljg4MCBsDQo1MS4zNjAgMjc5LjAwMCBsDQo1MC44
ODAgMjc5LjAwMCBsDQo1MC4yODAgMjc5LjAwMCBsDQo0OS44MDAgMjc5LjAwMCBsDQo0OS4zMjAg
Mjc5LjEyMCBsDQo0OC44NDAgMjc5LjEyMCBsDQo0OC4zNjAgMjc5LjEyMCBsDQo0Ny44ODAgMjc5
LjI0MCBsDQo0Ny40MDAgMjc5LjI0MCBsDQo0Ni45MjAgMjc5LjM2MCBsDQo0Ni40NDAgMjc5LjM2
MCBsDQo0NS44NDAgMjc5LjM2MCBsDQo0NS40ODAgMjc5LjM2MCBsDQo0NS4wMDAgMjc5LjQ4MCBs
DQo0NC41MjAgMjc5LjQ4MCBsDQo0NC4wNDAgMjc5LjQ4MCBsDQo0My41NjAgMjc5LjYwMCBsDQo0
My4yMDAgMjc5LjYwMCBsDQo0Mi43MjAgMjc5LjYwMCBsDQo0Mi4yNDAgMjc5LjYwMCBsDQo0MS43
NjAgMjc5LjcyMCBsDQo0MS40MDAgMjc5LjcyMCBsDQo0MC45MjAgMjc5Ljg0MCBsDQo0MC40NDAg
Mjc5Ljg0MCBsDQo0MC4wODAgMjc5Ljg0MCBsDQozOS42MDAgMjc5Ljg0MCBsDQozOS4yNDAgMjc5
Ljk2MCBsDQozOC43NjAgMjc5Ljk2MCBsDQozOC40MDAgMjc5Ljk2MCBsDQozNy45MjAgMjgwLjA4
MCBsDQozNy41NjAgMjgwLjA4MCBsDQozNy4wODAgMjgwLjA4MCBsDQozNi43MjAgMjgwLjIwMCBs
DQozNi4zNjAgMjgwLjIwMCBsDQozNS44ODAgMjgwLjIwMCBsDQozNS41MjAgMjgwLjMyMCBsDQoz
NS4xNjAgMjgwLjMyMCBsDQozNC42ODAgMjgwLjMyMCBsDQozNC4zMjAgMjgwLjMyMCBsDQozMy45
NjAgMjgwLjQ0MCBsDQozMy42MDAgMjgwLjQ0MCBsDQozMy4xMjAgMjgwLjU2MCBsDQozMi43NjAg
MjgwLjU2MCBsDQozMi40MDAgMjgwLjU2MCBsDQozMi4wNDAgMjgwLjU2MCBsDQozMS42ODAgMjgw
LjY4MCBsDQozMS4zMjAgMjgwLjY4MCBsDQozMC45NjAgMjgwLjY4MCBsDQozMC40ODAgMjgwLjgw
MCBsDQozMC4xMjAgMjgwLjgwMCBsDQoyOS43NjAgMjgwLjgwMCBsDQozMC4yNDAgMjgwLjgwMCBs
DQozMC4yNDAgMzA5LjM2MCBsDQpiKg0KMC4wMDAgMC4wMDAgMC4wMDAgcmcNCjAuMDAwIDAuMDAw
IDAuMDAwIFJHDQowLjI0MCB3DQpbIF0gMCBkDQoxIEoNCjEgag0KMjMuNjQwIDI4MC41NjAgNi42
MDAgMjkuMDQwIHJlDQpiKg0KMC4wMDAgMC4wMDAgMC4wMDAgcmcNCjAuMDAwIDAuMDAwIDAuMDAw
IFJHDQowLjI0MCB3DQpbIF0gMCBkDQoxIEoNCjEgag0KMTc1LjA4MCAyODAuNDQwIDYuNzIwIDI5
LjA0MCByZQ0KYioNCjAuMDAwIDAuMDAwIDAuMDAwIHJnDQowLjAwMCAwLjAwMCAwLjAwMCBSRw0K
MC4yNDAgdw0KWyBdIDAgZA0KMSBKDQoxIGoNCjEyMS4yMDAgMjk5LjQwMCBtDQoxMTUuOTIwIDI5
OS4wNDAgbA0KMTE1LjkyMCAzMDMuMDAwIGwNCjEyMS4yMDAgMzAzLjAwMCBsDQoxMjEuMjAwIDI5
OS40MDAgbA0KZioNCjAuNzUzIDAuNzUzIDAuNzUzIHJnDQowLjAwMCAwLjAwMCAwLjAwMCBSRw0K
MC4yNDAgdw0KWyBdIDAgZA0KMSBKDQoxIGoNCjEyMS4yMDAgMjk5LjQwMCBtDQoxMTUuNTYwIDI5
OS4wNDAgbA0KMTE2LjUyMCAzMDAuMDAwIGwNCjEyMC4zNjAgMzAwLjI0MCBsDQoxMjAuMzYwIDMw
Mi42NDAgbA0KMTIxLjIwMCAzMDMuNjAwIGwNCjEyMS4yMDAgMjk5LjQwMCBsDQpmKg0KMC41MDIg
MC41MDIgMC41MDIgcmcNCjAuMDAwIDAuMDAwIDAuMDAwIFJHDQowLjI0MCB3DQpbIF0gMCBkDQox
IEoNCjEgag0KMTE1LjY4MCAzMDMuMjQwIG0NCjEyMS4yMDAgMzAzLjYwMCBsDQoxMjAuMjQwIDMw
Mi42NDAgbA0KMTE2LjUyMCAzMDIuNDAwIGwNCjExNi41MjAgMzAwLjAwMCBsDQoxMTUuNjgwIDI5
OS4wNDAgbA0KMTE1LjY4MCAzMDMuMjQwIGwNCmYqDQowLjAwMCAwLjAwMCAwLjAwMCByZw0KMC4w
MDAgMC4wMDAgMC4wMDAgUkcNCjAuMjQwIHcNClsgXSAwIGQNCjEgSg0KMSBqDQoxMjEuMjAwIDI5
My4wNDAgbQ0KMTE1LjkyMCAyOTIuNjgwIGwNCjExNS45MjAgMjk2LjUyMCBsDQoxMjEuMjAwIDI5
Ni41MjAgbA0KMTIxLjIwMCAyOTMuMDQwIGwNCmYqDQowLjc1MyAwLjc1MyAwLjc1MyByZw0KMC4w
MDAgMC4wMDAgMC4wMDAgUkcNCjAuMjQwIHcNClsgXSAwIGQNCjEgSg0KMSBqDQoxMjEuMjAwIDI5
My4wNDAgbQ0KMTE1LjU2MCAyOTIuNjgwIGwNCjExNi41MjAgMjkzLjY0MCBsDQoxMjAuMzYwIDI5
My44ODAgbA0KMTIwLjM2MCAyOTYuMTYwIGwNCjEyMS4yMDAgMjk3LjEyMCBsDQoxMjEuMjAwIDI5
My4wNDAgbA0KZioNCjAuNTAyIDAuNTAyIDAuNTAyIHJnDQowLjAwMCAwLjAwMCAwLjAwMCBSRw0K
MC4yNDAgdw0KWyBdIDAgZA0KMSBKDQoxIGoNCjExNS42ODAgMjk2Ljg4MCBtDQoxMjEuMjAwIDI5
Ny4xMjAgbA0KMTIwLjI0MCAyOTYuMTYwIGwNCjExNi41MjAgMjk2LjA0MCBsDQoxMTYuNTIwIDI5
My42NDAgbA0KMTE1LjY4MCAyOTIuNjgwIGwNCjExNS42ODAgMjk2Ljg4MCBsDQpmKg0KMC4wMDAg
MC4wMDAgMC4wMDAgcmcNCjAuMDAwIDAuMDAwIDAuMDAwIFJHDQowLjI0MCB3DQpbIF0gMCBkDQox
IEoNCjEgag0KMTIxLjIwMCAyODYuNjgwIG0NCjExNS45MjAgMjg2LjMyMCBsDQoxMTUuOTIwIDI5
MC4xNjAgbA0KMTIxLjIwMCAyOTAuMTYwIGwNCjEyMS4yMDAgMjg2LjY4MCBsDQpmKg0KMC43NTMg
MC43NTMgMC43NTMgcmcNCjAuMDAwIDAuMDAwIDAuMDAwIFJHDQowLjI0MCB3DQpbIF0gMCBkDQox
IEoNCjEgag0KMTIxLjIwMCAyODYuNTYwIG0NCjExNS41NjAgMjg2LjMyMCBsDQoxMTYuNTIwIDI4
Ny4yODAgbA0KMTIwLjM2MCAyODcuNDAwIGwNCjEyMC4zNjAgMjg5LjgwMCBsDQoxMjEuMjAwIDI5
MC43NjAgbA0KMTIxLjIwMCAyODYuNTYwIGwNCmYqDQowLjUwMiAwLjUwMiAwLjUwMiByZw0KMC4w
MDAgMC4wMDAgMC4wMDAgUkcNCjAuMjQwIHcNClsgXSAwIGQNCjEgSg0KMSBqDQoxMTUuNjgwIDI5
MC40MDAgbQ0KMTIxLjIwMCAyOTAuNzYwIGwNCjEyMC4yNDAgMjg5LjgwMCBsDQoxMTYuNTIwIDI4
OS41NjAgbA0KMTE2LjUyMCAyODcuMjgwIGwNCjExNS42ODAgMjg2LjMyMCBsDQoxMTUuNjgwIDI5
MC40MDAgbA0KZioNCjAuMDAwIDAuMDAwIDAuMDAwIHJnDQowLjAwMCAwLjAwMCAwLjAwMCBSRw0K
MC4yNDAgdw0KWyBdIDAgZA0KMSBKDQoxIGoNCjEyMS4yMDAgMjgwLjMyMCBtDQoxMTUuOTIwIDI3
OS45NjAgbA0KMTE1LjkyMCAyODMuODAwIGwNCjEyMS4yMDAgMjgzLjgwMCBsDQoxMjEuMjAwIDI4
MC4zMjAgbA0KZioNCjAuNzUzIDAuNzUzIDAuNzUzIHJnDQowLjAwMCAwLjAwMCAwLjAwMCBSRw0K
MC4yNDAgdw0KWyBdIDAgZA0KMSBKDQoxIGoNCjEyMS4yMDAgMjgwLjIwMCBtDQoxMTUuNTYwIDI3
OS44NDAgbA0KMTE2LjUyMCAyODAuODAwIGwNCjEyMC4zNjAgMjgxLjA0MCBsDQoxMjAuMzYwIDI4
My40NDAgbA0KMTIxLjIwMCAyODQuNDAwIGwNCjEyMS4yMDAgMjgwLjIwMCBsDQpmKg0KMC41MDIg
MC41MDIgMC41MDIgcmcNCjAuMDAwIDAuMDAwIDAuMDAwIFJHDQowLjI0MCB3DQpbIF0gMCBkDQox
IEoNCjEgag0KMTE1LjY4MCAyODQuMDQwIG0NCjEyMS4yMDAgMjg0LjQwMCBsDQoxMjAuMjQwIDI4
My40NDAgbA0KMTE2LjUyMCAyODMuMjAwIGwNCjExNi41MjAgMjgwLjgwMCBsDQoxMTUuNjgwIDI3
OS44NDAgbA0KMTE1LjY4MCAyODQuMDQwIGwNCmYqDQowLjAwMCAwLjAwMCAwLjAwMCByZw0KMC4w
MDAgMC4wMDAgMC4wMDAgUkcNCjAuMjQwIHcNClsgXSAwIGQNCjEgSg0KMSBqDQoxMzAuMDgwIDI5
OS43NjAgbQ0KMTI0LjkyMCAyOTkuNDAwIGwNCjEyNC45MjAgMzAzLjI0MCBsDQoxMzAuMDgwIDMw
My4yNDAgbA0KMTMwLjA4MCAyOTkuNzYwIGwNCmYqDQowLjc1MyAwLjc1MyAwLjc1MyByZw0KMC4w
MDAgMC4wMDAgMC4wMDAgUkcNCjAuMjQwIHcNClsgXSAwIGQNCjEgSg0KMSBqDQoxMzAuMDgwIDI5
OS42NDAgbQ0KMTI0LjU2MCAyOTkuMjgwIGwNCjEyNS41MjAgMzAwLjM2MCBsDQoxMjkuMjQwIDMw
MC40ODAgbA0KMTI5LjI0MCAzMDIuODgwIGwNCjEzMC4wODAgMzAzLjg0MCBsDQoxMzAuMDgwIDI5
OS42NDAgbA0KZioNCjAuNTAyIDAuNTAyIDAuNTAyIHJnDQowLjAwMCAwLjAwMCAwLjAwMCBSRw0K
MC4yNDAgdw0KWyBdIDAgZA0KMSBKDQoxIGoNCjEyNC41NjAgMzAzLjQ4MCBtDQoxMzAuMjAwIDMw
My44NDAgbA0KMTI5LjI0MCAzMDIuODgwIGwNCjEyNS40MDAgMzAyLjY0MCBsDQoxMjUuNDAwIDMw
MC4zNjAgbA0KMTI0LjU2MCAyOTkuMjgwIGwNCjEyNC41NjAgMzAzLjQ4MCBsDQpmKg0KMC4wMDAg
MC4wMDAgMC4wMDAgcmcNCjAuMDAwIDAuMDAwIDAuMDAwIFJHDQowLjI0MCB3DQpbIF0gMCBkDQox
IEoNCjEgag0KMTMwLjA4MCAyOTMuMjgwIG0NCjEyNC45MjAgMjkzLjA0MCBsDQoxMjQuOTIwIDI5
Ni44ODAgbA0KMTMwLjA4MCAyOTYuODgwIGwNCjEzMC4wODAgMjkzLjI4MCBsDQpmKg0KMC43NTMg
MC43NTMgMC43NTMgcmcNCjAuMDAwIDAuMDAwIDAuMDAwIFJHDQowLjI0MCB3DQpbIF0gMCBkDQox
IEoNCjEgag0KMTMwLjA4MCAyOTMuMjgwIG0NCjEyNC41NjAgMjkyLjkyMCBsDQoxMjUuNTIwIDI5
My44ODAgbA0KMTI5LjI0MCAyOTQuMTIwIGwNCjEyOS4yNDAgMjk2LjUyMCBsDQoxMzAuMDgwIDI5
Ny40ODAgbA0KMTMwLjA4MCAyOTMuMjgwIGwNCmYqDQowLjUwMiAwLjUwMiAwLjUwMiByZw0KMC4w
MDAgMC4wMDAgMC4wMDAgUkcNCjAuMjQwIHcNClsgXSAwIGQNCjEgSg0KMSBqDQoxMjQuNTYwIDI5
Ny4xMjAgbQ0KMTMwLjIwMCAyOTcuNDgwIGwNCjEyOS4yNDAgMjk2LjUyMCBsDQoxMjUuNDAwIDI5
Ni4yODAgbA0KMTI1LjQwMCAyOTMuODgwIGwNCjEyNC41NjAgMjkyLjkyMCBsDQoxMjQuNTYwIDI5
Ny4xMjAgbA0KZioNCjAuMDAwIDAuMDAwIDAuMDAwIHJnDQowLjAwMCAwLjAwMCAwLjAwMCBSRw0K
MC4yNDAgdw0KWyBdIDAgZA0KMSBKDQoxIGoNCjEzMC4wODAgMjg2LjkyMCBtDQoxMjQuOTIwIDI4
Ni41NjAgbA0KMTI0LjkyMCAyOTAuNTIwIGwNCjEzMC4wODAgMjkwLjUyMCBsDQoxMzAuMDgwIDI4
Ni45MjAgbA0KZioNCjAuNzUzIDAuNzUzIDAuNzUzIHJnDQowLjAwMCAwLjAwMCAwLjAwMCBSRw0K
MC4yNDAgdw0KWyBdIDAgZA0KMSBKDQoxIGoNCjEzMC4wODAgMjg2LjkyMCBtDQoxMjQuNTYwIDI4
Ni41NjAgbA0KMTI1LjUyMCAyODcuNTIwIGwNCjEyOS4yNDAgMjg3Ljc2MCBsDQoxMjkuMjQwIDI5
MC4wNDAgbA0KMTMwLjA4MCAyOTEuMTIwIGwNCjEzMC4wODAgMjg2LjkyMCBsDQpmKg0KMC41MDIg
MC41MDIgMC41MDIgcmcNCjAuMDAwIDAuMDAwIDAuMDAwIFJHDQowLjI0MCB3DQpbIF0gMCBkDQox
IEoNCjEgag0KMTI0LjU2MCAyOTAuNzYwIG0NCjEzMC4yMDAgMjkxLjEyMCBsDQoxMjkuMjQwIDI5
MC4wNDAgbA0KMTI1LjQwMCAyODkuOTIwIGwNCjEyNS40MDAgMjg3LjUyMCBsDQoxMjQuNTYwIDI4
Ni41NjAgbA0KMTI0LjU2MCAyOTAuNzYwIGwNCmYqDQowLjAwMCAwLjAwMCAwLjAwMCByZw0KMC4w
MDAgMC4wMDAgMC4wMDAgUkcNCjAuMjQwIHcNClsgXSAwIGQNCjEgSg0KMSBqDQoxMzAuMDgwIDI4
MC41NjAgbQ0KMTI0LjkyMCAyODAuMjAwIGwNCjEyNC45MjAgMjg0LjA0MCBsDQoxMzAuMDgwIDI4
NC4wNDAgbA0KMTMwLjA4MCAyODAuNTYwIGwNCmYqDQowLjc1MyAwLjc1MyAwLjc1MyByZw0KMC4w
MDAgMC4wMDAgMC4wMDAgUkcNCjAuMjQwIHcNClsgXSAwIGQNCjEgSg0KMSBqDQoxMzAuMDgwIDI4
MC41NjAgbQ0KMTI0LjU2MCAyODAuMjAwIGwNCjEyNS41MjAgMjgxLjE2MCBsDQoxMjkuMjQwIDI4
MS4yODAgbA0KMTI5LjI0MCAyODMuNjgwIGwNCjEzMC4wODAgMjg0LjY0MCBsDQoxMzAuMDgwIDI4
MC41NjAgbA0KZioNCjAuNTAyIDAuNTAyIDAuNTAyIHJnDQowLjAwMCAwLjAwMCAwLjAwMCBSRw0K
MC4yNDAgdw0KWyBdIDAgZA0KMSBKDQoxIGoNCjEyNC41NjAgMjg0LjI4MCBtDQoxMzAuMjAwIDI4
NC42NDAgbA0KMTI5LjI0MCAyODMuNjgwIGwNCjEyNS40MDAgMjgzLjU2MCBsDQoxMjUuNDAwIDI4
MS4xNjAgbA0KMTI0LjU2MCAyODAuMjAwIGwNCjEyNC41NjAgMjg0LjI4MCBsDQpmKg0KMC4wMDAg
MC4wMDAgMC4wMDAgcmcNCjAuMDAwIDAuMDAwIDAuMDAwIFJHDQowLjI0MCB3DQpbIF0gMCBkDQox
IEoNCjEgag0KMTM4Ljg0MCAzMDAuMDAwIG0NCjEzMy41NjAgMjk5LjY0MCBsDQoxMzMuNTYwIDMw
My42MDAgbA0KMTM4Ljg0MCAzMDMuNjAwIGwNCjEzOC44NDAgMzAwLjAwMCBsDQpmKg0KMC43NTMg
MC43NTMgMC43NTMgcmcNCjAuMDAwIDAuMDAwIDAuMDAwIFJHDQowLjI0MCB3DQpbIF0gMCBkDQox
IEoNCjEgag0KMTM4Ljg0MCAzMDAuMDAwIG0NCjEzMy4yMDAgMjk5LjY0MCBsDQoxMzQuMTYwIDMw
MC42MDAgbA0KMTM4LjAwMCAzMDAuODQwIGwNCjEzOC4wMDAgMzAzLjEyMCBsDQoxMzguODQwIDMw
NC4wODAgbA0KMTM4Ljg0MCAzMDAuMDAwIGwNCmYqDQowLjUwMiAwLjUwMiAwLjUwMiByZw0KMC4w
MDAgMC4wMDAgMC4wMDAgUkcNCjAuMjQwIHcNClsgXSAwIGQNCjEgSg0KMSBqDQoxMzMuMzIwIDMw
My44NDAgbQ0KMTM4Ljg0MCAzMDQuMDgwIGwNCjEzNy44ODAgMzAzLjEyMCBsDQoxMzQuMTYwIDMw
My4wMDAgbA0KMTM0LjE2MCAzMDAuNjAwIGwNCjEzMy4zMjAgMjk5LjY0MCBsDQoxMzMuMzIwIDMw
My44NDAgbA0KZioNCjAuMDAwIDAuMDAwIDAuMDAwIHJnDQowLjAwMCAwLjAwMCAwLjAwMCBSRw0K
MC4yNDAgdw0KWyBdIDAgZA0KMSBKDQoxIGoNCjEzOC44NDAgMjkzLjY0MCBtDQoxMzMuNTYwIDI5
My4yODAgbA0KMTMzLjU2MCAyOTcuMTIwIGwNCjEzOC44NDAgMjk3LjEyMCBsDQoxMzguODQwIDI5
My42NDAgbA0KZioNCjAuNzUzIDAuNzUzIDAuNzUzIHJnDQowLjAwMCAwLjAwMCAwLjAwMCBSRw0K
MC4yNDAgdw0KWyBdIDAgZA0KMSBKDQoxIGoNCjEzOC44NDAgMjkzLjUyMCBtDQoxMzMuMjAwIDI5
My4yODAgbA0KMTM0LjE2MCAyOTQuMjQwIGwNCjEzOC4wMDAgMjk0LjM2MCBsDQoxMzguMDAwIDI5
Ni43NjAgbA0KMTM4Ljg0MCAyOTcuNzIwIGwNCjEzOC44NDAgMjkzLjUyMCBsDQpmKg0KMC41MDIg
MC41MDIgMC41MDIgcmcNCjAuMDAwIDAuMDAwIDAuMDAwIFJHDQowLjI0MCB3DQpbIF0gMCBkDQox
IEoNCjEgag0KMTMzLjMyMCAyOTcuMzYwIG0NCjEzOC44NDAgMjk3LjcyMCBsDQoxMzcuODgwIDI5
Ni43NjAgbA0KMTM0LjE2MCAyOTYuNTIwIGwNCjEzNC4xNjAgMjk0LjI0MCBsDQoxMzMuMzIwIDI5
My4yODAgbA0KMTMzLjMyMCAyOTcuMzYwIGwNCmYqDQowLjAwMCAwLjAwMCAwLjAwMCByZw0KMC4w
MDAgMC4wMDAgMC4wMDAgUkcNCjAuMjQwIHcNClsgXSAwIGQNCjEgSg0KMSBqDQoxMzguODQwIDI4
Ny4yODAgbQ0KMTMzLjU2MCAyODYuOTIwIGwNCjEzMy41NjAgMjkwLjc2MCBsDQoxMzguODQwIDI5
MC43NjAgbA0KMTM4Ljg0MCAyODcuMjgwIGwNCmYqDQowLjc1MyAwLjc1MyAwLjc1MyByZw0KMC4w
MDAgMC4wMDAgMC4wMDAgUkcNCjAuMjQwIHcNClsgXSAwIGQNCjEgSg0KMSBqDQoxMzguODQwIDI4
Ny4xNjAgbQ0KMTMzLjIwMCAyODYuODAwIGwNCjEzNC4xNjAgMjg3Ljc2MCBsDQoxMzguMDAwIDI4
OC4wMDAgbA0KMTM4LjAwMCAyOTAuNDAwIGwNCjEzOC44NDAgMjkxLjM2MCBsDQoxMzguODQwIDI4
Ny4xNjAgbA0KZioNCjAuNTAyIDAuNTAyIDAuNTAyIHJnDQowLjAwMCAwLjAwMCAwLjAwMCBSRw0K
MC4yNDAgdw0KWyBdIDAgZA0KMSBKDQoxIGoNCjEzMy4zMjAgMjkxLjAwMCBtDQoxMzguODQwIDI5
MS4zNjAgbA0KMTM3Ljg4MCAyOTAuNDAwIGwNCjEzNC4xNjAgMjkwLjE2MCBsDQoxMzQuMTYwIDI4
Ny43NjAgbA0KMTMzLjMyMCAyODYuODAwIGwNCjEzMy4zMjAgMjkxLjAwMCBsDQpmKg0KMC4wMDAg
MC4wMDAgMC4wMDAgcmcNCjAuMDAwIDAuMDAwIDAuMDAwIFJHDQowLjI0MCB3DQpbIF0gMCBkDQox
IEoNCjEgag0KMTM4Ljg0MCAyODAuODAwIG0NCjEzMy41NjAgMjgwLjU2MCBsDQoxMzMuNTYwIDI4
NC40MDAgbA0KMTM4Ljg0MCAyODQuNDAwIGwNCjEzOC44NDAgMjgwLjgwMCBsDQpmKg0KMC43NTMg
MC43NTMgMC43NTMgcmcNCjAuMDAwIDAuMDAwIDAuMDAwIFJHDQowLjI0MCB3DQpbIF0gMCBkDQox
IEoNCjEgag0KMTM4Ljg0MCAyODAuODAwIG0NCjEzMy4yMDAgMjgwLjQ0MCBsDQoxMzQuMTYwIDI4
MS40MDAgbA0KMTM4LjAwMCAyODEuNjQwIGwNCjEzOC4wMDAgMjg0LjA0MCBsDQoxMzguODQwIDI4
NS4wMDAgbA0KMTM4Ljg0MCAyODAuODAwIGwNCmYqDQowLjUwMiAwLjUwMiAwLjUwMiByZw0KMC4w
MDAgMC4wMDAgMC4wMDAgUkcNCjAuMjQwIHcNClsgXSAwIGQNCjEgSg0KMSBqDQoxMzMuMzIwIDI4
NC42NDAgbQ0KMTM4Ljg0MCAyODUuMDAwIGwNCjEzNy44ODAgMjg0LjA0MCBsDQoxMzQuMTYwIDI4
My44MDAgbA0KMTM0LjE2MCAyODEuNDAwIGwNCjEzMy4zMjAgMjgwLjQ0MCBsDQoxMzMuMzIwIDI4
NC42NDAgbA0KZioNCjAuMDAwIDAuMDAwIDAuMDAwIHJnDQowLjAwMCAwLjAwMCAwLjAwMCBSRw0K
MC4yNDAgdw0KWyBdIDAgZA0KMSBKDQoxIGoNCjE0Ny40ODAgMzAwLjYwMCBtDQoxNDIuMzIwIDMw
MC4yNDAgbA0KMTQyLjMyMCAzMDQuMDgwIGwNCjE0Ny40ODAgMzA0LjA4MCBsDQoxNDcuNDgwIDMw
MC42MDAgbA0KZioNCjAuNzUzIDAuNzUzIDAuNzUzIHJnDQowLjAwMCAwLjAwMCAwLjAwMCBSRw0K
MC4yNDAgdw0KWyBdIDAgZA0KMSBKDQoxIGoNCjE0Ny40ODAgMzAwLjYwMCBtDQoxNDEuOTYwIDMw
MC4yNDAgbA0KMTQyLjkyMCAzMDEuMjAwIGwNCjE0Ni42NDAgMzAxLjMyMCBsDQoxNDYuNjQwIDMw
My43MjAgbA0KMTQ3LjQ4MCAzMDQuNjgwIGwNCjE0Ny40ODAgMzAwLjYwMCBsDQpmKg0KMC41MDIg
MC41MDIgMC41MDIgcmcNCjAuMDAwIDAuMDAwIDAuMDAwIFJHDQowLjI0MCB3DQpbIF0gMCBkDQox
IEoNCjEgag0KMTQxLjk2MCAzMDQuMzIwIG0NCjE0Ny40ODAgMzA0LjY4MCBsDQoxNDYuNTIwIDMw
My43MjAgbA0KMTQyLjgwMCAzMDMuNjAwIGwNCjE0Mi44MDAgMzAxLjIwMCBsDQoxNDEuOTYwIDMw
MC4yNDAgbA0KMTQxLjk2MCAzMDQuMzIwIGwNCmYqDQowLjAwMCAwLjAwMCAwLjAwMCByZw0KMC4w
MDAgMC4wMDAgMC4wMDAgUkcNCjAuMjQwIHcNClsgXSAwIGQNCjEgSg0KMSBqDQoxNDcuNDgwIDI5
NC4yNDAgbQ0KMTQyLjMyMCAyOTMuODgwIGwNCjE0Mi4zMjAgMjk3LjcyMCBsDQoxNDcuNDgwIDI5
Ny43MjAgbA0KMTQ3LjQ4MCAyOTQuMjQwIGwNCmYqDQowLjc1MyAwLjc1MyAwLjc1MyByZw0KMC4w
MDAgMC4wMDAgMC4wMDAgUkcNCjAuMjQwIHcNClsgXSAwIGQNCjEgSg0KMSBqDQoxNDcuNDgwIDI5
NC4xMjAgbQ0KMTQxLjk2MCAyOTMuODgwIGwNCjE0Mi45MjAgMjk0Ljg0MCBsDQoxNDYuNjQwIDI5
NC45NjAgbA0KMTQ2LjY0MCAyOTcuMzYwIGwNCjE0Ny40ODAgMjk4LjMyMCBsDQoxNDcuNDgwIDI5
NC4xMjAgbA0KZioNCjAuNTAyIDAuNTAyIDAuNTAyIHJnDQowLjAwMCAwLjAwMCAwLjAwMCBSRw0K
MC4yNDAgdw0KWyBdIDAgZA0KMSBKDQoxIGoNCjE0MS45NjAgMjk3Ljk2MCBtDQoxNDcuNDgwIDI5
OC4zMjAgbA0KMTQ2LjUyMCAyOTcuMzYwIGwNCjE0Mi44MDAgMjk3LjEyMCBsDQoxNDIuODAwIDI5
NC44NDAgbA0KMTQxLjk2MCAyOTMuODgwIGwNCjE0MS45NjAgMjk3Ljk2MCBsDQpmKg0KMC4wMDAg
MC4wMDAgMC4wMDAgcmcNCjAuMDAwIDAuMDAwIDAuMDAwIFJHDQowLjI0MCB3DQpbIF0gMCBkDQox
IEoNCjEgag0KMTQ3LjQ4MCAyODcuNzYwIG0NCjE0Mi4zMjAgMjg3LjUyMCBsDQoxNDIuMzIwIDI5
MS4zNjAgbA0KMTQ3LjQ4MCAyOTEuMzYwIGwNCjE0Ny40ODAgMjg3Ljc2MCBsDQpmKg0KMC43NTMg
MC43NTMgMC43NTMgcmcNCjAuMDAwIDAuMDAwIDAuMDAwIFJHDQowLjI0MCB3DQpbIF0gMCBkDQox
IEoNCjEgag0KMTQ3LjQ4MCAyODcuNzYwIG0NCjE0MS45NjAgMjg3LjQwMCBsDQoxNDIuOTIwIDI4
OC4zNjAgbA0KMTQ2LjY0MCAyODguNjAwIGwNCjE0Ni42NDAgMjkxLjAwMCBsDQoxNDcuNDgwIDI5
MS45NjAgbA0KMTQ3LjQ4MCAyODcuNzYwIGwNCmYqDQowLjUwMiAwLjUwMiAwLjUwMiByZw0KMC4w
MDAgMC4wMDAgMC4wMDAgUkcNCjAuMjQwIHcNClsgXSAwIGQNCjEgSg0KMSBqDQoxNDEuOTYwIDI5
MS42MDAgbQ0KMTQ3LjQ4MCAyOTEuOTYwIGwNCjE0Ni41MjAgMjkxLjAwMCBsDQoxNDIuODAwIDI5
MC43NjAgbA0KMTQyLjgwMCAyODguMzYwIGwNCjE0MS45NjAgMjg3LjQwMCBsDQoxNDEuOTYwIDI5
MS42MDAgbA0KZioNCjAuMDAwIDAuMDAwIDAuMDAwIHJnDQowLjAwMCAwLjAwMCAwLjAwMCBSRw0K
MC4yNDAgdw0KWyBdIDAgZA0KMSBKDQoxIGoNCjE0Ny40ODAgMjgxLjQwMCBtDQoxNDIuMzIwIDI4
MS4wNDAgbA0KMTQyLjMyMCAyODUuMDAwIGwNCjE0Ny40ODAgMjg1LjAwMCBsDQoxNDcuNDgwIDI4
MS40MDAgbA0KZioNCjAuNzUzIDAuNzUzIDAuNzUzIHJnDQowLjAwMCAwLjAwMCAwLjAwMCBSRw0K
MC4yNDAgdw0KWyBdIDAgZA0KMSBKDQoxIGoNCjE0Ny40ODAgMjgxLjQwMCBtDQoxNDEuOTYwIDI4
MS4wNDAgbA0KMTQyLjkyMCAyODIuMDAwIGwNCjE0Ni42NDAgMjgyLjI0MCBsDQoxNDYuNjQwIDI4
NC41MjAgbA0KMTQ3LjQ4MCAyODUuNjAwIGwNCjE0Ny40ODAgMjgxLjQwMCBsDQpmKg0KMC41MDIg
MC41MDIgMC41MDIgcmcNCjAuMDAwIDAuMDAwIDAuMDAwIFJHDQowLjI0MCB3DQpbIF0gMCBkDQox
IEoNCjEgag0KMTQxLjk2MCAyODUuMjQwIG0NCjE0Ny40ODAgMjg1LjYwMCBsDQoxNDYuNTIwIDI4
NC41MjAgbA0KMTQyLjgwMCAyODQuNDAwIGwNCjE0Mi44MDAgMjgyLjAwMCBsDQoxNDEuOTYwIDI4
MS4wNDAgbA0KMTQxLjk2MCAyODUuMjQwIGwNCmYqDQowLjAwMCAwLjAwMCAwLjAwMCByZw0KMC4w
MDAgMC4wMDAgMC4wMDAgUkcNCjAuMjQwIHcNClsgXSAwIGQNCjEgSg0KMSBqDQoxNTYuMTIwIDMw
MS40NDAgbQ0KMTUwLjk2MCAzMDEuMDgwIGwNCjE1MC45NjAgMzA1LjA0MCBsDQoxNTYuMTIwIDMw
NS4wNDAgbA0KMTU2LjEyMCAzMDEuNDQwIGwNCmYqDQowLjc1MyAwLjc1MyAwLjc1MyByZw0KMC4w
MDAgMC4wMDAgMC4wMDAgUkcNCjAuMjQwIHcNClsgXSAwIGQNCjEgSg0KMSBqDQoxNTYuMTIwIDMw
MS40NDAgbQ0KMTUwLjYwMCAzMDEuMDgwIGwNCjE1MS41NjAgMzAyLjA0MCBsDQoxNTUuMjgwIDMw
Mi4yODAgbA0KMTU1LjI4MCAzMDQuNTYwIGwNCjE1Ni4xMjAgMzA1LjY0MCBsDQoxNTYuMTIwIDMw
MS40NDAgbA0KZioNCjAuNTAyIDAuNTAyIDAuNTAyIHJnDQowLjAwMCAwLjAwMCAwLjAwMCBSRw0K
MC4yNDAgdw0KWyBdIDAgZA0KMSBKDQoxIGoNCjE1MC42MDAgMzA1LjI4MCBtDQoxNTYuMjQwIDMw
NS42NDAgbA0KMTU1LjI4MCAzMDQuNTYwIGwNCjE1MS40NDAgMzA0LjQ0MCBsDQoxNTEuNDQwIDMw
Mi4wNDAgbA0KMTUwLjYwMCAzMDEuMDgwIGwNCjE1MC42MDAgMzA1LjI4MCBsDQpmKg0KMC4wMDAg
MC4wMDAgMC4wMDAgcmcNCjAuMDAwIDAuMDAwIDAuMDAwIFJHDQowLjI0MCB3DQpbIF0gMCBkDQox
IEoNCjEgag0KMTU2LjEyMCAyOTUuMDgwIG0NCjE1MC45NjAgMjk0LjcyMCBsDQoxNTAuOTYwIDI5
OC41NjAgbA0KMTU2LjEyMCAyOTguNTYwIGwNCjE1Ni4xMjAgMjk1LjA4MCBsDQpmKg0KMC43NTMg
MC43NTMgMC43NTMgcmcNCjAuMDAwIDAuMDAwIDAuMDAwIFJHDQowLjI0MCB3DQpbIF0gMCBkDQox
IEoNCjEgag0KMTU2LjEyMCAyOTUuMDgwIG0NCjE1MC42MDAgMjk0LjcyMCBsDQoxNTEuNTYwIDI5
NS42ODAgbA0KMTU1LjI4MCAyOTUuODAwIGwNCjE1NS4yODAgMjk4LjIwMCBsDQoxNTYuMTIwIDI5
OS4xNjAgbA0KMTU2LjEyMCAyOTUuMDgwIGwNCmYqDQowLjUwMiAwLjUwMiAwLjUwMiByZw0KMC4w
MDAgMC4wMDAgMC4wMDAgUkcNCjAuMjQwIHcNClsgXSAwIGQNCjEgSg0KMSBqDQoxNTAuNjAwIDI5
OC44MDAgbQ0KMTU2LjI0MCAyOTkuMTYwIGwNCjE1NS4yODAgMjk4LjIwMCBsDQoxNTEuNDQwIDI5
OC4wODAgbA0KMTUxLjQ0MCAyOTUuNjgwIGwNCjE1MC42MDAgMjk0LjcyMCBsDQoxNTAuNjAwIDI5
OC44MDAgbA0KZioNCjAuMDAwIDAuMDAwIDAuMDAwIHJnDQowLjAwMCAwLjAwMCAwLjAwMCBSRw0K
MC4yNDAgdw0KWyBdIDAgZA0KMSBKDQoxIGoNCjE1Ni4xMjAgMjg4LjcyMCBtDQoxNTAuOTYwIDI4
OC4zNjAgbA0KMTUwLjk2MCAyOTIuMjAwIGwNCjE1Ni4xMjAgMjkyLjIwMCBsDQoxNTYuMTIwIDI4
OC43MjAgbA0KZioNCjAuNzUzIDAuNzUzIDAuNzUzIHJnDQowLjAwMCAwLjAwMCAwLjAwMCBSRw0K
MC4yNDAgdw0KWyBdIDAgZA0KMSBKDQoxIGoNCjE1Ni4xMjAgMjg4LjYwMCBtDQoxNTAuNjAwIDI4
OC4zNjAgbA0KMTUxLjU2MCAyODkuMzIwIGwNCjE1NS4yODAgMjg5LjQ0MCBsDQoxNTUuMjgwIDI5
MS44NDAgbA0KMTU2LjEyMCAyOTIuODAwIGwNCjE1Ni4xMjAgMjg4LjYwMCBsDQpmKg0KMC41MDIg
MC41MDIgMC41MDIgcmcNCjAuMDAwIDAuMDAwIDAuMDAwIFJHDQowLjI0MCB3DQpbIF0gMCBkDQox
IEoNCjEgag0KMTUwLjYwMCAyOTIuNDQwIG0NCjE1Ni4yNDAgMjkyLjgwMCBsDQoxNTUuMjgwIDI5
MS44NDAgbA0KMTUxLjQ0MCAyOTEuNjAwIGwNCjE1MS40NDAgMjg5LjMyMCBsDQoxNTAuNjAwIDI4
OC4zNjAgbA0KMTUwLjYwMCAyOTIuNDQwIGwNCmYqDQowLjAwMCAwLjAwMCAwLjAwMCByZw0KMC4w
MDAgMC4wMDAgMC4wMDAgUkcNCjAuMjQwIHcNClsgXSAwIGQNCjEgSg0KMSBqDQoxNTYuMTIwIDI4
Mi4zNjAgbQ0KMTUwLjk2MCAyODIuMDAwIGwNCjE1MC45NjAgMjg1Ljg0MCBsDQoxNTYuMTIwIDI4
NS44NDAgbA0KMTU2LjEyMCAyODIuMzYwIGwNCmYqDQowLjc1MyAwLjc1MyAwLjc1MyByZw0KMC4w
MDAgMC4wMDAgMC4wMDAgUkcNCjAuMjQwIHcNClsgXSAwIGQNCjEgSg0KMSBqDQoxNTYuMTIwIDI4
Mi4yNDAgbQ0KMTUwLjYwMCAyODEuODgwIGwNCjE1MS41NjAgMjgyLjg0MCBsDQoxNTUuMjgwIDI4
My4wODAgbA0KMTU1LjI4MCAyODUuNDgwIGwNCjE1Ni4xMjAgMjg2LjQ0MCBsDQoxNTYuMTIwIDI4
Mi4yNDAgbA0KZioNCjAuNTAyIDAuNTAyIDAuNTAyIHJnDQowLjAwMCAwLjAwMCAwLjAwMCBSRw0K
MC4yNDAgdw0KWyBdIDAgZA0KMSBKDQoxIGoNCjE1MC42MDAgMjg2LjA4MCBtDQoxNTYuMjQwIDI4
Ni40NDAgbA0KMTU1LjI4MCAyODUuNDgwIGwNCjE1MS40NDAgMjg1LjI0MCBsDQoxNTEuNDQwIDI4
Mi44NDAgbA0KMTUwLjYwMCAyODEuODgwIGwNCjE1MC42MDAgMjg2LjA4MCBsDQpmKg0KMC4wMDAg
MC4wMDAgMC4wMDAgcmcNCjAuMDAwIDAuMDAwIDAuMDAwIFJHDQowLjI0MCB3DQpbIF0gMCBkDQox
IEoNCjEgag0KMTY0Ljg4MCAzMDIuMDQwIG0NCjE1OS42MDAgMzAxLjY4MCBsDQoxNTkuNjAwIDMw
NS42NDAgbA0KMTY0Ljg4MCAzMDUuNjQwIGwNCjE2NC44ODAgMzAyLjA0MCBsDQpmKg0KMC43NTMg
MC43NTMgMC43NTMgcmcNCjAuMDAwIDAuMDAwIDAuMDAwIFJHDQowLjI0MCB3DQpbIF0gMCBkDQox
IEoNCjEgag0KMTY0Ljg4MCAzMDIuMDQwIG0NCjE1OS4yNDAgMzAxLjY4MCBsDQoxNjAuMjAwIDMw
Mi42NDAgbA0KMTY0LjA0MCAzMDIuODgwIGwNCjE2NC4wNDAgMzA1LjE2MCBsDQoxNjQuODgwIDMw
Ni4xMjAgbA0KMTY0Ljg4MCAzMDIuMDQwIGwNCmYqDQowLjUwMiAwLjUwMiAwLjUwMiByZw0KMC4w
MDAgMC4wMDAgMC4wMDAgUkcNCjAuMjQwIHcNClsgXSAwIGQNCjEgSg0KMSBqDQoxNTkuMzYwIDMw
NS44ODAgbQ0KMTY0Ljg4MCAzMDYuMTIwIGwNCjE2My45MjAgMzA1LjE2MCBsDQoxNjAuMjAwIDMw
NS4wNDAgbA0KMTYwLjIwMCAzMDIuNjQwIGwNCjE1OS4zNjAgMzAxLjY4MCBsDQoxNTkuMzYwIDMw
NS44ODAgbA0KZioNCjAuMDAwIDAuMDAwIDAuMDAwIHJnDQowLjAwMCAwLjAwMCAwLjAwMCBSRw0K
MC4yNDAgdw0KWyBdIDAgZA0KMSBKDQoxIGoNCjE2NC44ODAgMjk1LjY4MCBtDQoxNTkuNjAwIDI5
NS4zMjAgbA0KMTU5LjYwMCAyOTkuMTYwIGwNCjE2NC44ODAgMjk5LjE2MCBsDQoxNjQuODgwIDI5
NS42ODAgbA0KZioNCjAuNzUzIDAuNzUzIDAuNzUzIHJnDQowLjAwMCAwLjAwMCAwLjAwMCBSRw0K
MC4yNDAgdw0KWyBdIDAgZA0KMSBKDQoxIGoNCjE2NC44ODAgMjk1LjU2MCBtDQoxNTkuMjQwIDI5
NS4zMjAgbA0KMTYwLjIwMCAyOTYuMjgwIGwNCjE2NC4wNDAgMjk2LjQwMCBsDQoxNjQuMDQwIDI5
OC44MDAgbA0KMTY0Ljg4MCAyOTkuNzYwIGwNCjE2NC44ODAgMjk1LjU2MCBsDQpmKg0KMC41MDIg
MC41MDIgMC41MDIgcmcNCjAuMDAwIDAuMDAwIDAuMDAwIFJHDQowLjI0MCB3DQpbIF0gMCBkDQox
IEoNCjEgag0KMTU5LjM2MCAyOTkuNDAwIG0NCjE2NC44ODAgMjk5Ljc2MCBsDQoxNjMuOTIwIDI5
OC44MDAgbA0KMTYwLjIwMCAyOTguNTYwIGwNCjE2MC4yMDAgMjk2LjI4MCBsDQoxNTkuMzYwIDI5
NS4zMjAgbA0KMTU5LjM2MCAyOTkuNDAwIGwNCmYqDQowLjAwMCAwLjAwMCAwLjAwMCByZw0KMC4w
MDAgMC4wMDAgMC4wMDAgUkcNCjAuMjQwIHcNClsgXSAwIGQNCjEgSg0KMSBqDQoxNjQuODgwIDI4
OS4zMjAgbQ0KMTU5LjYwMCAyODguOTYwIGwNCjE1OS42MDAgMjkyLjgwMCBsDQoxNjQuODgwIDI5
Mi44MDAgbA0KMTY0Ljg4MCAyODkuMzIwIGwNCmYqDQowLjc1MyAwLjc1MyAwLjc1MyByZw0KMC4w
MDAgMC4wMDAgMC4wMDAgUkcNCjAuMjQwIHcNClsgXSAwIGQNCjEgSg0KMSBqDQoxNjQuODgwIDI4
OS4yMDAgbQ0KMTU5LjI0MCAyODguODQwIGwNCjE2MC4yMDAgMjg5LjgwMCBsDQoxNjQuMDQwIDI5
MC4wNDAgbA0KMTY0LjA0MCAyOTIuNDQwIGwNCjE2NC44ODAgMjkzLjQwMCBsDQoxNjQuODgwIDI4
OS4yMDAgbA0KZioNCjAuNTAyIDAuNTAyIDAuNTAyIHJnDQowLjAwMCAwLjAwMCAwLjAwMCBSRw0K
MC4yNDAgdw0KWyBdIDAgZA0KMSBKDQoxIGoNCjE1OS4zNjAgMjkzLjA0MCBtDQoxNjQuODgwIDI5
My40MDAgbA0KMTYzLjkyMCAyOTIuNDQwIGwNCjE2MC4yMDAgMjkyLjIwMCBsDQoxNjAuMjAwIDI4
OS44MDAgbA0KMTU5LjM2MCAyODguODQwIGwNCjE1OS4zNjAgMjkzLjA0MCBsDQpmKg0KMC4wMDAg
MC4wMDAgMC4wMDAgcmcNCjAuMDAwIDAuMDAwIDAuMDAwIFJHDQowLjI0MCB3DQpbIF0gMCBkDQox
IEoNCjEgag0KMTY0Ljg4MCAyODIuODQwIG0NCjE1OS42MDAgMjgyLjYwMCBsDQoxNTkuNjAwIDI4
Ni40NDAgbA0KMTY0Ljg4MCAyODYuNDQwIGwNCjE2NC44ODAgMjgyLjg0MCBsDQpmKg0KMC43NTMg
MC43NTMgMC43NTMgcmcNCjAuMDAwIDAuMDAwIDAuMDAwIFJHDQowLjI0MCB3DQpbIF0gMCBkDQox
IEoNCjEgag0KMTY0Ljg4MCAyODIuODQwIG0NCjE1OS4yNDAgMjgyLjQ4MCBsDQoxNjAuMjAwIDI4
My40NDAgbA0KMTY0LjA0MCAyODMuNjgwIGwNCjE2NC4wNDAgMjg2LjA4MCBsDQoxNjQuODgwIDI4
Ny4wNDAgbA0KMTY0Ljg4MCAyODIuODQwIGwNCmYqDQowLjUwMiAwLjUwMiAwLjUwMiByZw0KMC4w
MDAgMC4wMDAgMC4wMDAgUkcNCjAuMjQwIHcNClsgXSAwIGQNCjEgSg0KMSBqDQoxNTkuMzYwIDI4
Ni42ODAgbQ0KMTY0Ljg4MCAyODcuMDQwIGwNCjE2My45MjAgMjg2LjA4MCBsDQoxNjAuMjAwIDI4
NS44NDAgbA0KMTYwLjIwMCAyODMuNDQwIGwNCjE1OS4zNjAgMjgyLjQ4MCBsDQoxNTkuMzYwIDI4
Ni42ODAgbA0KZioNCjAuMDAwIDAuMDAwIDAuMDAwIHJnDQowLjAwMCAwLjAwMCAwLjAwMCBSRw0K
MC4yNDAgdw0KWyBdIDAgZA0KMSBKDQoxIGoNCjE3Mi42ODAgMzAyLjg4MCBtDQoxNjcuNDAwIDMw
Mi42NDAgbA0KMTY3LjQwMCAzMDYuNDgwIGwNCjE3Mi42ODAgMzA2LjQ4MCBsDQoxNzIuNjgwIDMw
Mi44ODAgbA0KZioNCjAuNzUzIDAuNzUzIDAuNzUzIHJnDQowLjAwMCAwLjAwMCAwLjAwMCBSRw0K
MC4yNDAgdw0KWyBdIDAgZA0KMSBKDQoxIGoNCjE3Mi42ODAgMzAyLjg4MCBtDQoxNjcuMDQwIDMw
Mi41MjAgbA0KMTY4LjAwMCAzMDMuNDgwIGwNCjE3MS44NDAgMzAzLjcyMCBsDQoxNzEuODQwIDMw
Ni4xMjAgbA0KMTcyLjY4MCAzMDcuMDgwIGwNCjE3Mi42ODAgMzAyLjg4MCBsDQpmKg0KMC41MDIg
MC41MDIgMC41MDIgcmcNCjAuMDAwIDAuMDAwIDAuMDAwIFJHDQowLjI0MCB3DQpbIF0gMCBkDQox
IEoNCjEgag0KMTY3LjE2MCAzMDYuNzIwIG0NCjE3Mi42ODAgMzA3LjA4MCBsDQoxNzEuNzIwIDMw
Ni4xMjAgbA0KMTY4LjAwMCAzMDUuODgwIGwNCjE2OC4wMDAgMzAzLjQ4MCBsDQoxNjcuMTYwIDMw
Mi41MjAgbA0KMTY3LjE2MCAzMDYuNzIwIGwNCmYqDQowLjAwMCAwLjAwMCAwLjAwMCByZw0KMC4w
MDAgMC4wMDAgMC4wMDAgUkcNCjAuMjQwIHcNClsgXSAwIGQNCjEgSg0KMSBqDQoxNzIuNjgwIDI5
Ni41MjAgbQ0KMTY3LjQwMCAyOTYuMTYwIGwNCjE2Ny40MDAgMzAwLjEyMCBsDQoxNzIuNjgwIDMw
MC4xMjAgbA0KMTcyLjY4MCAyOTYuNTIwIGwNCmYqDQowLjc1MyAwLjc1MyAwLjc1MyByZw0KMC4w
MDAgMC4wMDAgMC4wMDAgUkcNCjAuMjQwIHcNClsgXSAwIGQNCjEgSg0KMSBqDQoxNzIuNjgwIDI5
Ni41MjAgbQ0KMTY3LjA0MCAyOTYuMTYwIGwNCjE2OC4wMDAgMjk3LjEyMCBsDQoxNzEuODQwIDI5
Ny4zNjAgbA0KMTcxLjg0MCAyOTkuNjQwIGwNCjE3Mi42ODAgMzAwLjYwMCBsDQoxNzIuNjgwIDI5
Ni41MjAgbA0KZioNCjAuNTAyIDAuNTAyIDAuNTAyIHJnDQowLjAwMCAwLjAwMCAwLjAwMCBSRw0K
MC4yNDAgdw0KWyBdIDAgZA0KMSBKDQoxIGoNCjE2Ny4xNjAgMzAwLjM2MCBtDQoxNzIuNjgwIDMw
MC42MDAgbA0KMTcxLjcyMCAyOTkuNjQwIGwNCjE2OC4wMDAgMjk5LjUyMCBsDQoxNjguMDAwIDI5
Ny4xMjAgbA0KMTY3LjE2MCAyOTYuMTYwIGwNCjE2Ny4xNjAgMzAwLjM2MCBsDQpmKg0KMC4wMDAg
MC4wMDAgMC4wMDAgcmcNCjAuMDAwIDAuMDAwIDAuMDAwIFJHDQowLjI0MCB3DQpbIF0gMCBkDQox
IEoNCjEgag0KMTcyLjY4MCAyOTAuMTYwIG0NCjE2Ny40MDAgMjg5LjgwMCBsDQoxNjcuNDAwIDI5
My42NDAgbA0KMTcyLjY4MCAyOTMuNjQwIGwNCjE3Mi42ODAgMjkwLjE2MCBsDQpmKg0KMC43NTMg
MC43NTMgMC43NTMgcmcNCjAuMDAwIDAuMDAwIDAuMDAwIFJHDQowLjI0MCB3DQpbIF0gMCBkDQox
IEoNCjEgag0KMTcyLjY4MCAyOTAuMDQwIG0NCjE2Ny4wNDAgMjg5LjgwMCBsDQoxNjguMDAwIDI5
MC43NjAgbA0KMTcxLjg0MCAyOTAuODgwIGwNCjE3MS44NDAgMjkzLjI4MCBsDQoxNzIuNjgwIDI5
NC4yNDAgbA0KMTcyLjY4MCAyOTAuMDQwIGwNCmYqDQowLjUwMiAwLjUwMiAwLjUwMiByZw0KMC4w
MDAgMC4wMDAgMC4wMDAgUkcNCjAuMjQwIHcNClsgXSAwIGQNCjEgSg0KMSBqDQoxNjcuMTYwIDI5
My44ODAgbQ0KMTcyLjY4MCAyOTQuMjQwIGwNCjE3MS43MjAgMjkzLjI4MCBsDQoxNjguMDAwIDI5
My4wNDAgbA0KMTY4LjAwMCAyOTAuNzYwIGwNCjE2Ny4xNjAgMjg5LjgwMCBsDQoxNjcuMTYwIDI5
My44ODAgbA0KZioNCjAuMDAwIDAuMDAwIDAuMDAwIHJnDQowLjAwMCAwLjAwMCAwLjAwMCBSRw0K
MC4yNDAgdw0KWyBdIDAgZA0KMSBKDQoxIGoNCjE3Mi42ODAgMjgzLjgwMCBtDQoxNjcuNDAwIDI4
My40NDAgbA0KMTY3LjQwMCAyODcuMjgwIGwNCjE3Mi42ODAgMjg3LjI4MCBsDQoxNzIuNjgwIDI4
My44MDAgbA0KZioNCjAuNzUzIDAuNzUzIDAuNzUzIHJnDQowLjAwMCAwLjAwMCAwLjAwMCBSRw0K
MC4yNDAgdw0KWyBdIDAgZA0KMSBKDQoxIGoNCjE3Mi42ODAgMjgzLjY4MCBtDQoxNjcuMDQwIDI4
My4zMjAgbA0KMTY4LjAwMCAyODQuMjgwIGwNCjE3MS44NDAgMjg0LjUyMCBsDQoxNzEuODQwIDI4
Ni45MjAgbA0KMTcyLjY4MCAyODcuODgwIGwNCjE3Mi42ODAgMjgzLjY4MCBsDQpmKg0KMC41MDIg
MC41MDIgMC41MDIgcmcNCjAuMDAwIDAuMDAwIDAuMDAwIFJHDQowLjI0MCB3DQpbIF0gMCBkDQox
IEoNCjEgag0KMTY3LjE2MCAyODcuNTIwIG0NCjE3Mi42ODAgMjg3Ljg4MCBsDQoxNzEuNzIwIDI4
Ni45MjAgbA0KMTY4LjAwMCAyODYuNjgwIGwNCjE2OC4wMDAgMjg0LjI4MCBsDQoxNjcuMTYwIDI4
My4zMjAgbA0KMTY3LjE2MCAyODcuNTIwIGwNCmYqDQowLjAwMCAwLjAwMCAwLjAwMCByZw0KMC4w
MDAgMC4wMDAgMC4wMDAgUkcNCjAuMjQwIHcNClsgXSAwIGQNCjEgSg0KMSBqDQo4My44ODAgMjk5
LjE2MCBtDQo4OS4wNDAgMjk4LjgwMCBsDQo4OS4wNDAgMzAyLjY0MCBsDQo4My44ODAgMzAyLjY0
MCBsDQo4My44ODAgMjk5LjE2MCBsDQpmKg0KMC43NTMgMC43NTMgMC43NTMgcmcNCjAuMDAwIDAu
MDAwIDAuMDAwIFJHDQowLjI0MCB3DQpbIF0gMCBkDQoxIEoNCjEgag0KODMuODgwIDI5OS4wNDAg
bQ0KODkuNDAwIDI5OC44MDAgbA0KODguNDQwIDI5OS43NjAgbA0KODQuNjAwIDI5OS44ODAgbA0K
ODQuNjAwIDMwMi4yODAgbA0KODMuODgwIDMwMy4yNDAgbA0KODMuODgwIDI5OS4wNDAgbA0KZioN
CjAuNTAyIDAuNTAyIDAuNTAyIHJnDQowLjAwMCAwLjAwMCAwLjAwMCBSRw0KMC4yNDAgdw0KWyBd
IDAgZA0KMSBKDQoxIGoNCjg5LjI4MCAzMDIuODgwIG0NCjgzLjc2MCAzMDMuMjQwIGwNCjg0Ljcy
MCAzMDIuMjgwIGwNCjg4LjU2MCAzMDIuMDQwIGwNCjg4LjU2MCAyOTkuNzYwIGwNCjg5LjI4MCAy
OTguODAwIGwNCjg5LjI4MCAzMDIuODgwIGwNCmYqDQowLjAwMCAwLjAwMCAwLjAwMCByZw0KMC4w
MDAgMC4wMDAgMC4wMDAgUkcNCjAuMjQwIHcNClsgXSAwIGQNCjEgSg0KMSBqDQo4My44ODAgMjky
LjgwMCBtDQo4OS4wNDAgMjkyLjQ0MCBsDQo4OS4wNDAgMjk2LjI4MCBsDQo4My44ODAgMjk2LjI4
MCBsDQo4My44ODAgMjkyLjgwMCBsDQpmKg0KMC43NTMgMC43NTMgMC43NTMgcmcNCjAuMDAwIDAu
MDAwIDAuMDAwIFJHDQowLjI0MCB3DQpbIF0gMCBkDQoxIEoNCjEgag0KODMuODgwIDI5Mi42ODAg
bQ0KODkuNDAwIDI5Mi4zMjAgbA0KODguNDQwIDI5My4yODAgbA0KODQuNjAwIDI5My41MjAgbA0K
ODQuNjAwIDI5NS45MjAgbA0KODMuODgwIDI5Ni44ODAgbA0KODMuODgwIDI5Mi42ODAgbA0KZioN
CjAuNTAyIDAuNTAyIDAuNTAyIHJnDQowLjAwMCAwLjAwMCAwLjAwMCBSRw0KMC4yNDAgdw0KWyBd
IDAgZA0KMSBKDQoxIGoNCjg5LjI4MCAyOTYuNTIwIG0NCjgzLjc2MCAyOTYuODgwIGwNCjg0Ljcy
MCAyOTUuOTIwIGwNCjg4LjU2MCAyOTUuNjgwIGwNCjg4LjU2MCAyOTMuMjgwIGwNCjg5LjI4MCAy
OTIuMzIwIGwNCjg5LjI4MCAyOTYuNTIwIGwNCmYqDQowLjAwMCAwLjAwMCAwLjAwMCByZw0KMC4w
MDAgMC4wMDAgMC4wMDAgUkcNCjAuMjQwIHcNClsgXSAwIGQNCjEgSg0KMSBqDQo4My44ODAgMjg2
LjMyMCBtDQo4OS4wNDAgMjg2LjA4MCBsDQo4OS4wNDAgMjg5LjkyMCBsDQo4My44ODAgMjg5Ljky
MCBsDQo4My44ODAgMjg2LjMyMCBsDQpmKg0KMC43NTMgMC43NTMgMC43NTMgcmcNCjAuMDAwIDAu
MDAwIDAuMDAwIFJHDQowLjI0MCB3DQpbIF0gMCBkDQoxIEoNCjEgag0KODMuODgwIDI4Ni4zMjAg
bQ0KODkuNDAwIDI4NS45NjAgbA0KODguNDQwIDI4Ni45MjAgbA0KODQuNjAwIDI4Ny4xNjAgbA0K
ODQuNjAwIDI4OS41NjAgbA0KODMuODgwIDI5MC41MjAgbA0KODMuODgwIDI4Ni4zMjAgbA0KZioN
CjAuNTAyIDAuNTAyIDAuNTAyIHJnDQowLjAwMCAwLjAwMCAwLjAwMCBSRw0KMC4yNDAgdw0KWyBd
IDAgZA0KMSBKDQoxIGoNCjg5LjI4MCAyOTAuMTYwIG0NCjgzLjc2MCAyOTAuNTIwIGwNCjg0Ljcy
MCAyODkuNTYwIGwNCjg4LjU2MCAyODkuMzIwIGwNCjg4LjU2MCAyODYuOTIwIGwNCjg5LjI4MCAy
ODUuOTYwIGwNCjg5LjI4MCAyOTAuMTYwIGwNCmYqDQowLjAwMCAwLjAwMCAwLjAwMCByZw0KMC4w
MDAgMC4wMDAgMC4wMDAgUkcNCjAuMjQwIHcNClsgXSAwIGQNCjEgSg0KMSBqDQo4My44ODAgMjc5
Ljk2MCBtDQo4OS4wNDAgMjc5LjYwMCBsDQo4OS4wNDAgMjgzLjU2MCBsDQo4My44ODAgMjgzLjU2
MCBsDQo4My44ODAgMjc5Ljk2MCBsDQpmKg0KMC43NTMgMC43NTMgMC43NTMgcmcNCjAuMDAwIDAu
MDAwIDAuMDAwIFJHDQowLjI0MCB3DQpbIF0gMCBkDQoxIEoNCjEgag0KODMuODgwIDI3OS45NjAg
bQ0KODkuNDAwIDI3OS42MDAgbA0KODguNDQwIDI4MC41NjAgbA0KODQuNjAwIDI4MC44MDAgbA0K
ODQuNjAwIDI4My4wODAgbA0KODMuODgwIDI4NC4wNDAgbA0KODMuODgwIDI3OS45NjAgbA0KZioN
CjAuNTAyIDAuNTAyIDAuNTAyIHJnDQowLjAwMCAwLjAwMCAwLjAwMCBSRw0KMC4yNDAgdw0KWyBd
IDAgZA0KMSBKDQoxIGoNCjg5LjI4MCAyODMuODAwIG0NCjgzLjc2MCAyODQuMDQwIGwNCjg0Ljcy
MCAyODMuMDgwIGwNCjg4LjU2MCAyODIuOTYwIGwNCjg4LjU2MCAyODAuNTYwIGwNCjg5LjI4MCAy
NzkuNjAwIGwNCjg5LjI4MCAyODMuODAwIGwNCmYqDQowLjAwMCAwLjAwMCAwLjAwMCByZw0KMC4w
MDAgMC4wMDAgMC4wMDAgUkcNCjAuMjQwIHcNClsgXSAwIGQNCjEgSg0KMSBqDQo3NC44ODAgMjk5
LjQwMCBtDQo4MC4wNDAgMjk5LjA0MCBsDQo4MC4wNDAgMzAzLjAwMCBsDQo3NC44ODAgMzAzLjAw
MCBsDQo3NC44ODAgMjk5LjQwMCBsDQpmKg0KMC43NTMgMC43NTMgMC43NTMgcmcNCjAuMDAwIDAu
MDAwIDAuMDAwIFJHDQowLjI0MCB3DQpbIF0gMCBkDQoxIEoNCjEgag0KNzQuODgwIDI5OS40MDAg
bQ0KODAuNDAwIDI5OS4wNDAgbA0KNzkuNDQwIDMwMC4wMDAgbA0KNzUuNzIwIDMwMC4yNDAgbA0K
NzUuNzIwIDMwMi42NDAgbA0KNzQuODgwIDMwMy42MDAgbA0KNzQuODgwIDI5OS40MDAgbA0KZioN
CjAuNTAyIDAuNTAyIDAuNTAyIHJnDQowLjAwMCAwLjAwMCAwLjAwMCBSRw0KMC4yNDAgdw0KWyBd
IDAgZA0KMSBKDQoxIGoNCjgwLjQwMCAzMDMuMjQwIG0NCjc0Ljg4MCAzMDMuNjAwIGwNCjc1Ljg0
MCAzMDIuNjQwIGwNCjc5LjU2MCAzMDIuNDAwIGwNCjc5LjU2MCAzMDAuMDAwIGwNCjgwLjQwMCAy
OTkuMDQwIGwNCjgwLjQwMCAzMDMuMjQwIGwNCmYqDQowLjAwMCAwLjAwMCAwLjAwMCByZw0KMC4w
MDAgMC4wMDAgMC4wMDAgUkcNCjAuMjQwIHcNClsgXSAwIGQNCjEgSg0KMSBqDQo3NC44ODAgMjkz
LjA0MCBtDQo4MC4wNDAgMjkyLjY4MCBsDQo4MC4wNDAgMjk2LjUyMCBsDQo3NC44ODAgMjk2LjUy
MCBsDQo3NC44ODAgMjkzLjA0MCBsDQpmKg0KMC43NTMgMC43NTMgMC43NTMgcmcNCjAuMDAwIDAu
MDAwIDAuMDAwIFJHDQowLjI0MCB3DQpbIF0gMCBkDQoxIEoNCjEgag0KNzQuODgwIDI5My4wNDAg
bQ0KODAuNDAwIDI5Mi42ODAgbA0KNzkuNDQwIDI5My42NDAgbA0KNzUuNzIwIDI5My44ODAgbA0K
NzUuNzIwIDI5Ni4xNjAgbA0KNzQuODgwIDI5Ny4xMjAgbA0KNzQuODgwIDI5My4wNDAgbA0KZioN
CjAuNTAyIDAuNTAyIDAuNTAyIHJnDQowLjAwMCAwLjAwMCAwLjAwMCBSRw0KMC4yNDAgdw0KWyBd
IDAgZA0KMSBKDQoxIGoNCjgwLjQwMCAyOTYuODgwIG0NCjc0Ljg4MCAyOTcuMTIwIGwNCjc1Ljg0
MCAyOTYuMTYwIGwNCjc5LjU2MCAyOTYuMDQwIGwNCjc5LjU2MCAyOTMuNjQwIGwNCjgwLjQwMCAy
OTIuNjgwIGwNCjgwLjQwMCAyOTYuODgwIGwNCmYqDQowLjAwMCAwLjAwMCAwLjAwMCByZw0KMC4w
MDAgMC4wMDAgMC4wMDAgUkcNCjAuMjQwIHcNClsgXSAwIGQNCjEgSg0KMSBqDQo3NC44ODAgMjg2
LjY4MCBtDQo4MC4wNDAgMjg2LjMyMCBsDQo4MC4wNDAgMjkwLjE2MCBsDQo3NC44ODAgMjkwLjE2
MCBsDQo3NC44ODAgMjg2LjY4MCBsDQpmKg0KMC43NTMgMC43NTMgMC43NTMgcmcNCjAuMDAwIDAu
MDAwIDAuMDAwIFJHDQowLjI0MCB3DQpbIF0gMCBkDQoxIEoNCjEgag0KNzQuODgwIDI4Ni41NjAg
bQ0KODAuNDAwIDI4Ni4zMjAgbA0KNzkuNDQwIDI4Ny4yODAgbA0KNzUuNzIwIDI4Ny40MDAgbA0K
NzUuNzIwIDI4OS44MDAgbA0KNzQuODgwIDI5MC43NjAgbA0KNzQuODgwIDI4Ni41NjAgbA0KZioN
CjAuNTAyIDAuNTAyIDAuNTAyIHJnDQowLjAwMCAwLjAwMCAwLjAwMCBSRw0KMC4yNDAgdw0KWyBd
IDAgZA0KMSBKDQoxIGoNCjgwLjQwMCAyOTAuNDAwIG0NCjc0Ljg4MCAyOTAuNzYwIGwNCjc1Ljg0
MCAyODkuODAwIGwNCjc5LjU2MCAyODkuNTYwIGwNCjc5LjU2MCAyODcuMjgwIGwNCjgwLjQwMCAy
ODYuMzIwIGwNCjgwLjQwMCAyOTAuNDAwIGwNCmYqDQowLjAwMCAwLjAwMCAwLjAwMCByZw0KMC4w
MDAgMC4wMDAgMC4wMDAgUkcNCjAuMjQwIHcNClsgXSAwIGQNCjEgSg0KMSBqDQo3NC44ODAgMjgw
LjMyMCBtDQo4MC4wNDAgMjc5Ljk2MCBsDQo4MC4wNDAgMjgzLjgwMCBsDQo3NC44ODAgMjgzLjgw
MCBsDQo3NC44ODAgMjgwLjMyMCBsDQpmKg0KMC43NTMgMC43NTMgMC43NTMgcmcNCjAuMDAwIDAu
MDAwIDAuMDAwIFJHDQowLjI0MCB3DQpbIF0gMCBkDQoxIEoNCjEgag0KNzQuODgwIDI4MC4yMDAg
bQ0KODAuNDAwIDI3OS44NDAgbA0KNzkuNDQwIDI4MC44MDAgbA0KNzUuNzIwIDI4MS4wNDAgbA0K
NzUuNzIwIDI4My40NDAgbA0KNzQuODgwIDI4NC40MDAgbA0KNzQuODgwIDI4MC4yMDAgbA0KZioN
CjAuNTAyIDAuNTAyIDAuNTAyIHJnDQowLjAwMCAwLjAwMCAwLjAwMCBSRw0KMC4yNDAgdw0KWyBd
IDAgZA0KMSBKDQoxIGoNCjgwLjQwMCAyODQuMDQwIG0NCjc0Ljg4MCAyODQuNDAwIGwNCjc1Ljg0
MCAyODMuNDQwIGwNCjc5LjU2MCAyODMuMjAwIGwNCjc5LjU2MCAyODAuODAwIGwNCjgwLjQwMCAy
NzkuODQwIGwNCjgwLjQwMCAyODQuMDQwIGwNCmYqDQowLjAwMCAwLjAwMCAwLjAwMCByZw0KMC4w
MDAgMC4wMDAgMC4wMDAgUkcNCjAuMjQwIHcNClsgXSAwIGQNCjEgSg0KMSBqDQo2Ni4yNDAgMjk5
Ljc2MCBtDQo3MS40MDAgMjk5LjQwMCBsDQo3MS40MDAgMzAzLjI0MCBsDQo2Ni4yNDAgMzAzLjI0
MCBsDQo2Ni4yNDAgMjk5Ljc2MCBsDQpmKg0KMC43NTMgMC43NTMgMC43NTMgcmcNCjAuMDAwIDAu
MDAwIDAuMDAwIFJHDQowLjI0MCB3DQpbIF0gMCBkDQoxIEoNCjEgag0KNjYuMjQwIDI5OS42NDAg
bQ0KNzEuNzYwIDI5OS4yODAgbA0KNzAuODAwIDMwMC4zNjAgbA0KNjYuOTYwIDMwMC40ODAgbA0K
NjYuOTYwIDMwMi44ODAgbA0KNjYuMjQwIDMwMy44NDAgbA0KNjYuMjQwIDI5OS42NDAgbA0KZioN
CjAuNTAyIDAuNTAyIDAuNTAyIHJnDQowLjAwMCAwLjAwMCAwLjAwMCBSRw0KMC4yNDAgdw0KWyBd
IDAgZA0KMSBKDQoxIGoNCjcxLjY0MCAzMDMuNDgwIG0NCjY2LjEyMCAzMDMuODQwIGwNCjY3LjA4
MCAzMDIuODgwIGwNCjcwLjkyMCAzMDIuNjQwIGwNCjcwLjkyMCAzMDAuMzYwIGwNCjcxLjY0MCAy
OTkuMjgwIGwNCjcxLjY0MCAzMDMuNDgwIGwNCmYqDQowLjAwMCAwLjAwMCAwLjAwMCByZw0KMC4w
MDAgMC4wMDAgMC4wMDAgUkcNCjAuMjQwIHcNClsgXSAwIGQNCjEgSg0KMSBqDQo2Ni4yNDAgMjkz
LjI4MCBtDQo3MS40MDAgMjkzLjA0MCBsDQo3MS40MDAgMjk2Ljg4MCBsDQo2Ni4yNDAgMjk2Ljg4
MCBsDQo2Ni4yNDAgMjkzLjI4MCBsDQpmKg0KMC43NTMgMC43NTMgMC43NTMgcmcNCjAuMDAwIDAu
MDAwIDAuMDAwIFJHDQowLjI0MCB3DQpbIF0gMCBkDQoxIEoNCjEgag0KNjYuMjQwIDI5My4yODAg
bQ0KNzEuNzYwIDI5Mi45MjAgbA0KNzAuODAwIDI5My44ODAgbA0KNjYuOTYwIDI5NC4xMjAgbA0K
NjYuOTYwIDI5Ni41MjAgbA0KNjYuMjQwIDI5Ny40ODAgbA0KNjYuMjQwIDI5My4yODAgbA0KZioN
CjAuNTAyIDAuNTAyIDAuNTAyIHJnDQowLjAwMCAwLjAwMCAwLjAwMCBSRw0KMC4yNDAgdw0KWyBd
IDAgZA0KMSBKDQoxIGoNCjcxLjY0MCAyOTcuMTIwIG0NCjY2LjEyMCAyOTcuNDgwIGwNCjY3LjA4
MCAyOTYuNTIwIGwNCjcwLjkyMCAyOTYuMjgwIGwNCjcwLjkyMCAyOTMuODgwIGwNCjcxLjY0MCAy
OTIuOTIwIGwNCjcxLjY0MCAyOTcuMTIwIGwNCmYqDQowLjAwMCAwLjAwMCAwLjAwMCByZw0KMC4w
MDAgMC4wMDAgMC4wMDAgUkcNCjAuMjQwIHcNClsgXSAwIGQNCjEgSg0KMSBqDQo2Ni4yNDAgMjg2
LjkyMCBtDQo3MS40MDAgMjg2LjU2MCBsDQo3MS40MDAgMjkwLjUyMCBsDQo2Ni4yNDAgMjkwLjUy
MCBsDQo2Ni4yNDAgMjg2LjkyMCBsDQpmKg0KMC43NTMgMC43NTMgMC43NTMgcmcNCjAuMDAwIDAu
MDAwIDAuMDAwIFJHDQowLjI0MCB3DQpbIF0gMCBkDQoxIEoNCjEgag0KNjYuMjQwIDI4Ni45MjAg
bQ0KNzEuNzYwIDI4Ni41NjAgbA0KNzAuODAwIDI4Ny41MjAgbA0KNjYuOTYwIDI4Ny43NjAgbA0K
NjYuOTYwIDI5MC4wNDAgbA0KNjYuMjQwIDI5MS4xMjAgbA0KNjYuMjQwIDI4Ni45MjAgbA0KZioN
CjAuNTAyIDAuNTAyIDAuNTAyIHJnDQowLjAwMCAwLjAwMCAwLjAwMCBSRw0KMC4yNDAgdw0KWyBd
IDAgZA0KMSBKDQoxIGoNCjcxLjY0MCAyOTAuNzYwIG0NCjY2LjEyMCAyOTEuMTIwIGwNCjY3LjA4
MCAyOTAuMDQwIGwNCjcwLjkyMCAyODkuOTIwIGwNCjcwLjkyMCAyODcuNTIwIGwNCjcxLjY0MCAy
ODYuNTYwIGwNCjcxLjY0MCAyOTAuNzYwIGwNCmYqDQowLjAwMCAwLjAwMCAwLjAwMCByZw0KMC4w
MDAgMC4wMDAgMC4wMDAgUkcNCjAuMjQwIHcNClsgXSAwIGQNCjEgSg0KMSBqDQo2Ni4yNDAgMjgw
LjU2MCBtDQo3MS40MDAgMjgwLjIwMCBsDQo3MS40MDAgMjg0LjA0MCBsDQo2Ni4yNDAgMjg0LjA0
MCBsDQo2Ni4yNDAgMjgwLjU2MCBsDQpmKg0KMC43NTMgMC43NTMgMC43NTMgcmcNCjAuMDAwIDAu
MDAwIDAuMDAwIFJHDQowLjI0MCB3DQpbIF0gMCBkDQoxIEoNCjEgag0KNjYuMjQwIDI4MC41NjAg
bQ0KNzEuNzYwIDI4MC4yMDAgbA0KNzAuODAwIDI4MS4xNjAgbA0KNjYuOTYwIDI4MS4yODAgbA0K
NjYuOTYwIDI4My42ODAgbA0KNjYuMjQwIDI4NC42NDAgbA0KNjYuMjQwIDI4MC41NjAgbA0KZioN
CjAuNTAyIDAuNTAyIDAuNTAyIHJnDQowLjAwMCAwLjAwMCAwLjAwMCBSRw0KMC4yNDAgdw0KWyBd
IDAgZA0KMSBKDQoxIGoNCjcxLjY0MCAyODQuMjgwIG0NCjY2LjEyMCAyODQuNjQwIGwNCjY3LjA4
MCAyODMuNjgwIGwNCjcwLjkyMCAyODMuNTYwIGwNCjcwLjkyMCAyODEuMTYwIGwNCjcxLjY0MCAy
ODAuMjAwIGwNCjcxLjY0MCAyODQuMjgwIGwNCmYqDQowLjAwMCAwLjAwMCAwLjAwMCByZw0KMC4w
MDAgMC4wMDAgMC4wMDAgUkcNCjAuMjQwIHcNClsgXSAwIGQNCjEgSg0KMSBqDQo1Ny40ODAgMzAw
LjM2MCBtDQo2Mi43NjAgMzAwLjAwMCBsDQo2Mi43NjAgMzAzLjg0MCBsDQo1Ny40ODAgMzAzLjg0
MCBsDQo1Ny40ODAgMzAwLjM2MCBsDQpmKg0KMC43NTMgMC43NTMgMC43NTMgcmcNCjAuMDAwIDAu
MDAwIDAuMDAwIFJHDQowLjI0MCB3DQpbIF0gMCBkDQoxIEoNCjEgag0KNTcuNDgwIDMwMC4yNDAg
bQ0KNjMuMDAwIDI5OS44ODAgbA0KNjIuMDQwIDMwMC44NDAgbA0KNTguMzIwIDMwMS4wODAgbA0K
NTguMzIwIDMwMy40ODAgbA0KNTcuNDgwIDMwNC40NDAgbA0KNTcuNDgwIDMwMC4yNDAgbA0KZioN
CjAuNTAyIDAuNTAyIDAuNTAyIHJnDQowLjAwMCAwLjAwMCAwLjAwMCBSRw0KMC4yNDAgdw0KWyBd
IDAgZA0KMSBKDQoxIGoNCjYzLjAwMCAzMDQuMDgwIG0NCjU3LjQ4MCAzMDQuNDQwIGwNCjU4LjQ0
MCAzMDMuNDgwIGwNCjYyLjE2MCAzMDMuMjQwIGwNCjYyLjE2MCAzMDAuODQwIGwNCjYzLjAwMCAy
OTkuODgwIGwNCjYzLjAwMCAzMDQuMDgwIGwNCmYqDQowLjAwMCAwLjAwMCAwLjAwMCByZw0KMC4w
MDAgMC4wMDAgMC4wMDAgUkcNCjAuMjQwIHcNClsgXSAwIGQNCjEgSg0KMSBqDQo1Ny40ODAgMjkz
Ljg4MCBtDQo2Mi43NjAgMjkzLjUyMCBsDQo2Mi43NjAgMjk3LjQ4MCBsDQo1Ny40ODAgMjk3LjQ4
MCBsDQo1Ny40ODAgMjkzLjg4MCBsDQpmKg0KMC43NTMgMC43NTMgMC43NTMgcmcNCjAuMDAwIDAu
MDAwIDAuMDAwIFJHDQowLjI0MCB3DQpbIF0gMCBkDQoxIEoNCjEgag0KNTcuNDgwIDI5My44ODAg
bQ0KNjMuMDAwIDI5My41MjAgbA0KNjIuMDQwIDI5NC40ODAgbA0KNTguMzIwIDI5NC43MjAgbA0K
NTguMzIwIDI5Ny4xMjAgbA0KNTcuNDgwIDI5OC4wODAgbA0KNTcuNDgwIDI5My44ODAgbA0KZioN
CjAuNTAyIDAuNTAyIDAuNTAyIHJnDQowLjAwMCAwLjAwMCAwLjAwMCBSRw0KMC4yNDAgdw0KWyBd
IDAgZA0KMSBKDQoxIGoNCjYzLjAwMCAyOTcuNzIwIG0NCjU3LjQ4MCAyOTguMDgwIGwNCjU4LjQ0
MCAyOTcuMTIwIGwNCjYyLjE2MCAyOTYuODgwIGwNCjYyLjE2MCAyOTQuNDgwIGwNCjYzLjAwMCAy
OTMuNTIwIGwNCjYzLjAwMCAyOTcuNzIwIGwNCmYqDQowLjAwMCAwLjAwMCAwLjAwMCByZw0KMC4w
MDAgMC4wMDAgMC4wMDAgUkcNCjAuMjQwIHcNClsgXSAwIGQNCjEgSg0KMSBqDQo1Ny40ODAgMjg3
LjUyMCBtDQo2Mi43NjAgMjg3LjE2MCBsDQo2Mi43NjAgMjkxLjEyMCBsDQo1Ny40ODAgMjkxLjEy
MCBsDQo1Ny40ODAgMjg3LjUyMCBsDQpmKg0KMC43NTMgMC43NTMgMC43NTMgcmcNCjAuMDAwIDAu
MDAwIDAuMDAwIFJHDQowLjI0MCB3DQpbIF0gMCBkDQoxIEoNCjEgag0KNTcuNDgwIDI4Ny41MjAg
bQ0KNjMuMDAwIDI4Ny4xNjAgbA0KNjIuMDQwIDI4OC4xMjAgbA0KNTguMzIwIDI4OC4zNjAgbA0K
NTguMzIwIDI5MC42NDAgbA0KNTcuNDgwIDI5MS42MDAgbA0KNTcuNDgwIDI4Ny41MjAgbA0KZioN
CjAuNTAyIDAuNTAyIDAuNTAyIHJnDQowLjAwMCAwLjAwMCAwLjAwMCBSRw0KMC4yNDAgdw0KWyBd
IDAgZA0KMSBKDQoxIGoNCjYzLjAwMCAyOTEuMzYwIG0NCjU3LjQ4MCAyOTEuNjAwIGwNCjU4LjQ0
MCAyOTAuNjQwIGwNCjYyLjE2MCAyOTAuNTIwIGwNCjYyLjE2MCAyODguMTIwIGwNCjYzLjAwMCAy
ODcuMTYwIGwNCjYzLjAwMCAyOTEuMzYwIGwNCmYqDQowLjAwMCAwLjAwMCAwLjAwMCByZw0KMC4w
MDAgMC4wMDAgMC4wMDAgUkcNCjAuMjQwIHcNClsgXSAwIGQNCjEgSg0KMSBqDQo1Ny40ODAgMjgx
LjE2MCBtDQo2Mi43NjAgMjgwLjgwMCBsDQo2Mi43NjAgMjg0LjY0MCBsDQo1Ny40ODAgMjg0LjY0
MCBsDQo1Ny40ODAgMjgxLjE2MCBsDQpmKg0KMC43NTMgMC43NTMgMC43NTMgcmcNCjAuMDAwIDAu
MDAwIDAuMDAwIFJHDQowLjI0MCB3DQpbIF0gMCBkDQoxIEoNCjEgag0KNTcuNDgwIDI4MS4wNDAg
bQ0KNjMuMDAwIDI4MC44MDAgbA0KNjIuMDQwIDI4MS43NjAgbA0KNTguMzIwIDI4MS44ODAgbA0K
NTguMzIwIDI4NC4yODAgbA0KNTcuNDgwIDI4NS4yNDAgbA0KNTcuNDgwIDI4MS4wNDAgbA0KZioN
CjAuNTAyIDAuNTAyIDAuNTAyIHJnDQowLjAwMCAwLjAwMCAwLjAwMCBSRw0KMC4yNDAgdw0KWyBd
IDAgZA0KMSBKDQoxIGoNCjYzLjAwMCAyODQuODgwIG0NCjU3LjQ4MCAyODUuMjQwIGwNCjU4LjQ0
MCAyODQuMjgwIGwNCjYyLjE2MCAyODQuMDQwIGwNCjYyLjE2MCAyODEuNzYwIGwNCjYzLjAwMCAy
ODAuODAwIGwNCjYzLjAwMCAyODQuODgwIGwNCmYqDQowLjAwMCAwLjAwMCAwLjAwMCByZw0KMC4w
MDAgMC4wMDAgMC4wMDAgUkcNCjAuMjQwIHcNClsgXSAwIGQNCjEgSg0KMSBqDQo0OC44NDAgMzAx
LjIwMCBtDQo1NC4wMDAgMzAwLjg0MCBsDQo1NC4wMDAgMzA0LjY4MCBsDQo0OC44NDAgMzA0LjY4
MCBsDQo0OC44NDAgMzAxLjIwMCBsDQpmKg0KMC43NTMgMC43NTMgMC43NTMgcmcNCjAuMDAwIDAu
MDAwIDAuMDAwIFJHDQowLjI0MCB3DQpbIF0gMCBkDQoxIEoNCjEgag0KNDguODQwIDMwMS4wODAg
bQ0KNTQuMzYwIDMwMC44NDAgbA0KNTMuNDAwIDMwMS44MDAgbA0KNDkuNjgwIDMwMS45MjAgbA0K
NDkuNjgwIDMwNC4zMjAgbA0KNDguODQwIDMwNS4yODAgbA0KNDguODQwIDMwMS4wODAgbA0KZioN
CjAuNTAyIDAuNTAyIDAuNTAyIHJnDQowLjAwMCAwLjAwMCAwLjAwMCBSRw0KMC4yNDAgdw0KWyBd
IDAgZA0KMSBKDQoxIGoNCjU0LjM2MCAzMDQuOTIwIG0NCjQ4Ljg0MCAzMDUuMjgwIGwNCjQ5Ljgw
MCAzMDQuMzIwIGwNCjUzLjUyMCAzMDQuMDgwIGwNCjUzLjUyMCAzMDEuODAwIGwNCjU0LjM2MCAz
MDAuODQwIGwNCjU0LjM2MCAzMDQuOTIwIGwNCmYqDQowLjAwMCAwLjAwMCAwLjAwMCByZw0KMC4w
MDAgMC4wMDAgMC4wMDAgUkcNCjAuMjQwIHcNClsgXSAwIGQNCjEgSg0KMSBqDQo0OC44NDAgMjk0
Ljg0MCBtDQo1NC4wMDAgMjk0LjQ4MCBsDQo1NC4wMDAgMjk4LjMyMCBsDQo0OC44NDAgMjk4LjMy
MCBsDQo0OC44NDAgMjk0Ljg0MCBsDQpmKg0KMC43NTMgMC43NTMgMC43NTMgcmcNCjAuMDAwIDAu
MDAwIDAuMDAwIFJHDQowLjI0MCB3DQpbIF0gMCBkDQoxIEoNCjEgag0KNDguODQwIDI5NC43MjAg
bQ0KNTQuMzYwIDI5NC4zNjAgbA0KNTMuNDAwIDI5NS4zMjAgbA0KNDkuNjgwIDI5NS41NjAgbA0K
NDkuNjgwIDI5Ny45NjAgbA0KNDguODQwIDI5OC45MjAgbA0KNDguODQwIDI5NC43MjAgbA0KZioN
CjAuNTAyIDAuNTAyIDAuNTAyIHJnDQowLjAwMCAwLjAwMCAwLjAwMCBSRw0KMC4yNDAgdw0KWyBd
IDAgZA0KMSBKDQoxIGoNCjU0LjM2MCAyOTguNTYwIG0NCjQ4Ljg0MCAyOTguOTIwIGwNCjQ5Ljgw
MCAyOTcuOTYwIGwNCjUzLjUyMCAyOTcuNzIwIGwNCjUzLjUyMCAyOTUuMzIwIGwNCjU0LjM2MCAy
OTQuMzYwIGwNCjU0LjM2MCAyOTguNTYwIGwNCmYqDQowLjAwMCAwLjAwMCAwLjAwMCByZw0KMC4w
MDAgMC4wMDAgMC4wMDAgUkcNCjAuMjQwIHcNClsgXSAwIGQNCjEgSg0KMSBqDQo0OC44NDAgMjg4
LjM2MCBtDQo1NC4wMDAgMjg4LjEyMCBsDQo1NC4wMDAgMjkxLjk2MCBsDQo0OC44NDAgMjkxLjk2
MCBsDQo0OC44NDAgMjg4LjM2MCBsDQpmKg0KMC43NTMgMC43NTMgMC43NTMgcmcNCjAuMDAwIDAu
MDAwIDAuMDAwIFJHDQowLjI0MCB3DQpbIF0gMCBkDQoxIEoNCjEgag0KNDguODQwIDI4OC4zNjAg
bQ0KNTQuMzYwIDI4OC4wMDAgbA0KNTMuNDAwIDI4OC45NjAgbA0KNDkuNjgwIDI4OS4yMDAgbA0K
NDkuNjgwIDI5MS42MDAgbA0KNDguODQwIDI5Mi41NjAgbA0KNDguODQwIDI4OC4zNjAgbA0KZioN
CjAuNTAyIDAuNTAyIDAuNTAyIHJnDQowLjAwMCAwLjAwMCAwLjAwMCBSRw0KMC4yNDAgdw0KWyBd
IDAgZA0KMSBKDQoxIGoNCjU0LjM2MCAyOTIuMjAwIG0NCjQ4Ljg0MCAyOTIuNTYwIGwNCjQ5Ljgw
MCAyOTEuNjAwIGwNCjUzLjUyMCAyOTEuMzYwIGwNCjUzLjUyMCAyODguOTYwIGwNCjU0LjM2MCAy
ODguMDAwIGwNCjU0LjM2MCAyOTIuMjAwIGwNCmYqDQowLjAwMCAwLjAwMCAwLjAwMCByZw0KMC4w
MDAgMC4wMDAgMC4wMDAgUkcNCjAuMjQwIHcNClsgXSAwIGQNCjEgSg0KMSBqDQo0OC44NDAgMjgy
LjAwMCBtDQo1NC4wMDAgMjgxLjY0MCBsDQo1NC4wMDAgMjg1LjYwMCBsDQo0OC44NDAgMjg1LjYw
MCBsDQo0OC44NDAgMjgyLjAwMCBsDQpmKg0KMC43NTMgMC43NTMgMC43NTMgcmcNCjAuMDAwIDAu
MDAwIDAuMDAwIFJHDQowLjI0MCB3DQpbIF0gMCBkDQoxIEoNCjEgag0KNDguODQwIDI4Mi4wMDAg
bQ0KNTQuMzYwIDI4MS42NDAgbA0KNTMuNDAwIDI4Mi42MDAgbA0KNDkuNjgwIDI4Mi44NDAgbA0K
NDkuNjgwIDI4NS4xMjAgbA0KNDguODQwIDI4Ni4wODAgbA0KNDguODQwIDI4Mi4wMDAgbA0KZioN
CjAuNTAyIDAuNTAyIDAuNTAyIHJnDQowLjAwMCAwLjAwMCAwLjAwMCBSRw0KMC4yNDAgdw0KWyBd
IDAgZA0KMSBKDQoxIGoNCjU0LjM2MCAyODUuODQwIG0NCjQ4Ljg0MCAyODYuMDgwIGwNCjQ5Ljgw
MCAyODUuMTIwIGwNCjUzLjUyMCAyODUuMDAwIGwNCjUzLjUyMCAyODIuNjAwIGwNCjU0LjM2MCAy
ODEuNjQwIGwNCjU0LjM2MCAyODUuODQwIGwNCmYqDQowLjAwMCAwLjAwMCAwLjAwMCByZw0KMC4w
MDAgMC4wMDAgMC4wMDAgUkcNCjAuMjQwIHcNClsgXSAwIGQNCjEgSg0KMSBqDQo0MC4yMDAgMzAx
LjgwMCBtDQo0NS4zNjAgMzAxLjQ0MCBsDQo0NS4zNjAgMzA1LjI4MCBsDQo0MC4yMDAgMzA1LjI4
MCBsDQo0MC4yMDAgMzAxLjgwMCBsDQpmKg0KMC43NTMgMC43NTMgMC43NTMgcmcNCjAuMDAwIDAu
MDAwIDAuMDAwIFJHDQowLjI0MCB3DQpbIF0gMCBkDQoxIEoNCjEgag0KNDAuMjAwIDMwMS42ODAg
bQ0KNDUuNzIwIDMwMS4zMjAgbA0KNDQuNzYwIDMwMi4yODAgbA0KNDEuMDQwIDMwMi41MjAgbA0K
NDEuMDQwIDMwNC45MjAgbA0KNDAuMjAwIDMwNS44ODAgbA0KNDAuMjAwIDMwMS42ODAgbA0KZioN
CjAuNTAyIDAuNTAyIDAuNTAyIHJnDQowLjAwMCAwLjAwMCAwLjAwMCBSRw0KMC4yNDAgdw0KWyBd
IDAgZA0KMSBKDQoxIGoNCjQ1LjYwMCAzMDUuNTIwIG0NCjQwLjA4MCAzMDUuODgwIGwNCjQxLjA0
MCAzMDQuOTIwIGwNCjQ0Ljg4MCAzMDQuNjgwIGwNCjQ0Ljg4MCAzMDIuMjgwIGwNCjQ1LjYwMCAz
MDEuMzIwIGwNCjQ1LjYwMCAzMDUuNTIwIGwNCmYqDQowLjAwMCAwLjAwMCAwLjAwMCByZw0KMC4w
MDAgMC4wMDAgMC4wMDAgUkcNCjAuMjQwIHcNClsgXSAwIGQNCjEgSg0KMSBqDQo0MC4yMDAgMjk1
LjMyMCBtDQo0NS4zNjAgMjk1LjA4MCBsDQo0NS4zNjAgMjk4LjkyMCBsDQo0MC4yMDAgMjk4Ljky
MCBsDQo0MC4yMDAgMjk1LjMyMCBsDQpmKg0KMC43NTMgMC43NTMgMC43NTMgcmcNCjAuMDAwIDAu
MDAwIDAuMDAwIFJHDQowLjI0MCB3DQpbIF0gMCBkDQoxIEoNCjEgag0KNDAuMjAwIDI5NS4zMjAg
bQ0KNDUuNzIwIDI5NC45NjAgbA0KNDQuNzYwIDI5NS45MjAgbA0KNDEuMDQwIDI5Ni4xNjAgbA0K
NDEuMDQwIDI5OC41NjAgbA0KNDAuMjAwIDI5OS41MjAgbA0KNDAuMjAwIDI5NS4zMjAgbA0KZioN
CjAuNTAyIDAuNTAyIDAuNTAyIHJnDQowLjAwMCAwLjAwMCAwLjAwMCBSRw0KMC4yNDAgdw0KWyBd
IDAgZA0KMSBKDQoxIGoNCjQ1LjYwMCAyOTkuMTYwIG0NCjQwLjA4MCAyOTkuNTIwIGwNCjQxLjA0
MCAyOTguNTYwIGwNCjQ0Ljg4MCAyOTguMzIwIGwNCjQ0Ljg4MCAyOTUuOTIwIGwNCjQ1LjYwMCAy
OTQuOTYwIGwNCjQ1LjYwMCAyOTkuMTYwIGwNCmYqDQowLjAwMCAwLjAwMCAwLjAwMCByZw0KMC4w
MDAgMC4wMDAgMC4wMDAgUkcNCjAuMjQwIHcNClsgXSAwIGQNCjEgSg0KMSBqDQo0MC4yMDAgMjg4
Ljk2MCBtDQo0NS4zNjAgMjg4LjYwMCBsDQo0NS4zNjAgMjkyLjU2MCBsDQo0MC4yMDAgMjkyLjU2
MCBsDQo0MC4yMDAgMjg4Ljk2MCBsDQpmKg0KMC43NTMgMC43NTMgMC43NTMgcmcNCjAuMDAwIDAu
MDAwIDAuMDAwIFJHDQowLjI0MCB3DQpbIF0gMCBkDQoxIEoNCjEgag0KNDAuMjAwIDI4OC45NjAg
bQ0KNDUuNzIwIDI4OC42MDAgbA0KNDQuNzYwIDI4OS41NjAgbA0KNDEuMDQwIDI4OS44MDAgbA0K
NDEuMDQwIDI5Mi4wODAgbA0KNDAuMjAwIDI5My4wNDAgbA0KNDAuMjAwIDI4OC45NjAgbA0KZioN
CjAuNTAyIDAuNTAyIDAuNTAyIHJnDQowLjAwMCAwLjAwMCAwLjAwMCBSRw0KMC4yNDAgdw0KWyBd
IDAgZA0KMSBKDQoxIGoNCjQ1LjYwMCAyOTIuODAwIG0NCjQwLjA4MCAyOTMuMDQwIGwNCjQxLjA0
MCAyOTIuMDgwIGwNCjQ0Ljg4MCAyOTEuOTYwIGwNCjQ0Ljg4MCAyODkuNTYwIGwNCjQ1LjYwMCAy
ODguNjAwIGwNCjQ1LjYwMCAyOTIuODAwIGwNCmYqDQowLjAwMCAwLjAwMCAwLjAwMCByZw0KMC4w
MDAgMC4wMDAgMC4wMDAgUkcNCjAuMjQwIHcNClsgXSAwIGQNCjEgSg0KMSBqDQo0MC4yMDAgMjgy
LjYwMCBtDQo0NS4zNjAgMjgyLjI0MCBsDQo0NS4zNjAgMjg2LjA4MCBsDQo0MC4yMDAgMjg2LjA4
MCBsDQo0MC4yMDAgMjgyLjYwMCBsDQpmKg0KMC43NTMgMC43NTMgMC43NTMgcmcNCjAuMDAwIDAu
MDAwIDAuMDAwIFJHDQowLjI0MCB3DQpbIF0gMCBkDQoxIEoNCjEgag0KNDAuMjAwIDI4Mi42MDAg
bQ0KNDUuNzIwIDI4Mi4yNDAgbA0KNDQuNzYwIDI4My4yMDAgbA0KNDEuMDQwIDI4My4zMjAgbA0K
NDEuMDQwIDI4NS43MjAgbA0KNDAuMjAwIDI4Ni42ODAgbA0KNDAuMjAwIDI4Mi42MDAgbA0KZioN
CjAuNTAyIDAuNTAyIDAuNTAyIHJnDQowLjAwMCAwLjAwMCAwLjAwMCBSRw0KMC4yNDAgdw0KWyBd
IDAgZA0KMSBKDQoxIGoNCjQ1LjYwMCAyODYuMzIwIG0NCjQwLjA4MCAyODYuNjgwIGwNCjQxLjA0
MCAyODUuNzIwIGwNCjQ0Ljg4MCAyODUuNjAwIGwNCjQ0Ljg4MCAyODMuMjAwIGwNCjQ1LjYwMCAy
ODIuMjQwIGwNCjQ1LjYwMCAyODYuMzIwIGwNCmYqDQowLjAwMCAwLjAwMCAwLjAwMCByZw0KMC4w
MDAgMC4wMDAgMC4wMDAgUkcNCjAuMjQwIHcNClsgXSAwIGQNCjEgSg0KMSBqDQozMi40MDAgMzAy
LjY0MCBtDQozNy41NjAgMzAyLjI4MCBsDQozNy41NjAgMzA2LjEyMCBsDQozMi40MDAgMzA2LjEy
MCBsDQozMi40MDAgMzAyLjY0MCBsDQpmKg0KMC43NTMgMC43NTMgMC43NTMgcmcNCjAuMDAwIDAu
MDAwIDAuMDAwIFJHDQowLjI0MCB3DQpbIF0gMCBkDQoxIEoNCjEgag0KMzIuNDAwIDMwMi42NDAg
bQ0KMzcuOTIwIDMwMi4yODAgbA0KMzYuOTYwIDMwMy4yNDAgbA0KMzMuMTIwIDMwMy4zNjAgbA0K
MzMuMTIwIDMwNS43NjAgbA0KMzIuNDAwIDMwNi43MjAgbA0KMzIuNDAwIDMwMi42NDAgbA0KZioN
CjAuNTAyIDAuNTAyIDAuNTAyIHJnDQowLjAwMCAwLjAwMCAwLjAwMCBSRw0KMC4yNDAgdw0KWyBd
IDAgZA0KMSBKDQoxIGoNCjM3LjgwMCAzMDYuMzYwIG0NCjMyLjI4MCAzMDYuNzIwIGwNCjMzLjI0
MCAzMDUuNzYwIGwNCjM3LjA4MCAzMDUuNjQwIGwNCjM3LjA4MCAzMDMuMjQwIGwNCjM3LjgwMCAz
MDIuMjgwIGwNCjM3LjgwMCAzMDYuMzYwIGwNCmYqDQowLjAwMCAwLjAwMCAwLjAwMCByZw0KMC4w
MDAgMC4wMDAgMC4wMDAgUkcNCjAuMjQwIHcNClsgXSAwIGQNCjEgSg0KMSBqDQozMi40MDAgMjk2
LjI4MCBtDQozNy41NjAgMjk1LjkyMCBsDQozNy41NjAgMjk5Ljc2MCBsDQozMi40MDAgMjk5Ljc2
MCBsDQozMi40MDAgMjk2LjI4MCBsDQpmKg0KMC43NTMgMC43NTMgMC43NTMgcmcNCjAuMDAwIDAu
MDAwIDAuMDAwIFJHDQowLjI0MCB3DQpbIF0gMCBkDQoxIEoNCjEgag0KMzIuNDAwIDI5Ni4xNjAg
bQ0KMzcuOTIwIDI5NS44MDAgbA0KMzYuOTYwIDI5Ni44ODAgbA0KMzMuMTIwIDI5Ny4wMDAgbA0K
MzMuMTIwIDI5OS40MDAgbA0KMzIuNDAwIDMwMC4zNjAgbA0KMzIuNDAwIDI5Ni4xNjAgbA0KZioN
CjAuNTAyIDAuNTAyIDAuNTAyIHJnDQowLjAwMCAwLjAwMCAwLjAwMCBSRw0KMC4yNDAgdw0KWyBd
IDAgZA0KMSBKDQoxIGoNCjM3LjgwMCAzMDAuMDAwIG0NCjMyLjI4MCAzMDAuMzYwIGwNCjMzLjI0
MCAyOTkuNDAwIGwNCjM3LjA4MCAyOTkuMTYwIGwNCjM3LjA4MCAyOTYuODgwIGwNCjM3LjgwMCAy
OTUuODAwIGwNCjM3LjgwMCAzMDAuMDAwIGwNCmYqDQowLjAwMCAwLjAwMCAwLjAwMCByZw0KMC4w
MDAgMC4wMDAgMC4wMDAgUkcNCjAuMjQwIHcNClsgXSAwIGQNCjEgSg0KMSBqDQozMi40MDAgMjg5
LjgwMCBtDQozNy41NjAgMjg5LjU2MCBsDQozNy41NjAgMjkzLjQwMCBsDQozMi40MDAgMjkzLjQw
MCBsDQozMi40MDAgMjg5LjgwMCBsDQpmKg0KMC43NTMgMC43NTMgMC43NTMgcmcNCjAuMDAwIDAu
MDAwIDAuMDAwIFJHDQowLjI0MCB3DQpbIF0gMCBkDQoxIEoNCjEgag0KMzIuNDAwIDI4OS44MDAg
bQ0KMzcuOTIwIDI4OS40NDAgbA0KMzYuOTYwIDI5MC40MDAgbA0KMzMuMTIwIDI5MC42NDAgbA0K
MzMuMTIwIDI5My4wNDAgbA0KMzIuNDAwIDI5NC4wMDAgbA0KMzIuNDAwIDI4OS44MDAgbA0KZioN
CjAuNTAyIDAuNTAyIDAuNTAyIHJnDQowLjAwMCAwLjAwMCAwLjAwMCBSRw0KMC4yNDAgdw0KWyBd
IDAgZA0KMSBKDQoxIGoNCjM3LjgwMCAyOTMuNjQwIG0NCjMyLjI4MCAyOTQuMDAwIGwNCjMzLjI0
MCAyOTMuMDQwIGwNCjM3LjA4MCAyOTIuODAwIGwNCjM3LjA4MCAyOTAuNDAwIGwNCjM3LjgwMCAy
ODkuNDQwIGwNCjM3LjgwMCAyOTMuNjQwIGwNCmYqDQowLjAwMCAwLjAwMCAwLjAwMCByZw0KMC4w
MDAgMC4wMDAgMC4wMDAgUkcNCjAuMjQwIHcNClsgXSAwIGQNCjEgSg0KMSBqDQozMi40MDAgMjgz
LjQ0MCBtDQozNy41NjAgMjgzLjA4MCBsDQozNy41NjAgMjg3LjA0MCBsDQozMi40MDAgMjg3LjA0
MCBsDQozMi40MDAgMjgzLjQ0MCBsDQpmKg0KMC43NTMgMC43NTMgMC43NTMgcmcNCjAuMDAwIDAu
MDAwIDAuMDAwIFJHDQowLjI0MCB3DQpbIF0gMCBkDQoxIEoNCjEgag0KMzIuNDAwIDI4My40NDAg
bQ0KMzcuOTIwIDI4My4wODAgbA0KMzYuOTYwIDI4NC4wNDAgbA0KMzMuMTIwIDI4NC4yODAgbA0K
MzMuMTIwIDI4Ni41NjAgbA0KMzIuNDAwIDI4Ny41MjAgbA0KMzIuNDAwIDI4My40NDAgbA0KZioN
CjAuNTAyIDAuNTAyIDAuNTAyIHJnDQowLjAwMCAwLjAwMCAwLjAwMCBSRw0KMC4yNDAgdw0KWyBd
IDAgZA0KMSBKDQoxIGoNCjM3LjgwMCAyODcuMjgwIG0NCjMyLjI4MCAyODcuNTIwIGwNCjMzLjI0
MCAyODYuNTYwIGwNCjM3LjA4MCAyODYuNDQwIGwNCjM3LjA4MCAyODQuMDQwIGwNCjM3LjgwMCAy
ODMuMDgwIGwNCjM3LjgwMCAyODcuMjgwIGwNCmYqDQowLjAwMCAwLjAwMCAwLjAwMCBSRw0KMC4y
NDAgdw0KWyBdIDAgZA0KMSBKDQoxIGoNCjEwNC4yODAgMzM0LjkyMCBtDQoxMDQuMjgwIDMxNC44
ODAgbA0KUw0KMC4wMDAgMC4wMDAgMC4wMDAgUkcNCjAuMjQwIHcNClsgXSAwIGQNCjEgSg0KMSBq
DQoxMDQuMjgwIDMxNC44ODAgbQ0KMTY0LjI4MCAzMTQuODgwIGwNClMNCjAuMDAwIDAuMDAwIDAu
MDAwIFJHDQowLjI0MCB3DQpbIF0gMCBkDQoxIEoNCjEgag0KMTQ5LjA0MCAzMzQuNjgwIG0NCjE2
NC4yODAgMzE0Ljg4MCBsDQpTDQowLjAwMCAwLjAwMCAwLjAwMCBSRw0KMC4yNDAgdw0KWyBdIDAg
ZA0KMSBKDQoxIGoNCjEwNC4yODAgMzM0LjkyMCBtDQoxNDkuMDQwIDMzNC42ODAgbA0KUw0KMC4w
MDAgMC4wMDAgMC4wMDAgUkcNCjAuMjQwIHcNClsgXSAwIGQNCjEgSg0KMSBqDQowLjg3OCAwLjg3
OCAwLjg3OCByZw0KMjguMjAwIDMwNC44MDAgbQ0KMjguMTk4IDMwNi44ODAgMjUuMzIxIDMwNi44
ODAgMjUuMzIwIDMwNC44MDAgYw0KMjUuMzIyIDMwMi43MjAgMjguMTk4IDMwMi43MjAgMjguMjAw
IDMwNC44MDAgYw0KZioNCjAuMDAwIDAuMDAwIDAuMDAwIFJHDQowLjEyMCB3DQpbIF0gMCBkDQox
IEoNCjEgag0KMC44NzggMC44NzggMC44NzggcmcNCjI4LjQ0MCAyODQuODgwIG0NCjI4LjQzOCAy
ODYuOTYwIDI1LjU2MSAyODYuOTYwIDI1LjU2MCAyODQuODgwIGMNCjI1LjU2MiAyODIuODAwIDI4
LjQzOCAyODIuODAwIDI4LjQ0MCAyODQuODgwIGMNCmYqDQowLjAwMCAwLjAwMCAwLjAwMCBSRw0K
MC4xMjAgdw0KWyBdIDAgZA0KMSBKDQoxIGoNCjAuODc4IDAuODc4IDAuODc4IHJnDQoxODAuMDAw
IDMwNS43NjAgbQ0KMTc5Ljk5OCAzMDcuNjgwIDE3Ny4xMjIgMzA3LjY4MCAxNzcuMTIwIDMwNS43
NjAgYw0KMTc3LjEyMSAzMDMuODQwIDE3OS45OTggMzAzLjg0MCAxODAuMDAwIDMwNS43NjAgYw0K
ZioNCjAuMDAwIDAuMDAwIDAuMDAwIFJHDQowLjEyMCB3DQpbIF0gMCBkDQoxIEoNCjEgag0KMC44
NzggMC44NzggMC44NzggcmcNCjE3OS42NDAgMjgzLjQ0MCBtDQoxNzkuNjM4IDI4NS41MjAgMTc2
Ljc2MSAyODUuNTIwIDE3Ni43NjAgMjgzLjQ0MCBjDQoxNzYuNzYyIDI4MS4zNjAgMTc5LjYzOCAy
ODEuMzYwIDE3OS42NDAgMjgzLjQ0MCBjDQpmKg0KMC41MDIgMC41MDIgMC41MDIgcmcNCjAuMDAw
IDAuMDAwIDAuMDAwIFJHDQowLjEyMCB3DQpbIF0gMCBkDQoxIEoNCjEgag0KMTAyLjAwMCAzMDQu
OTIwIG0NCjEwMC44MDAgMzAzLjQ4MCBsDQoxMDAuODAwIDI3OC4yODAgbA0KMTAyLjAwMCAyNzcu
MDgwIGwNCjEwMi4wMDAgMzA0LjY4MCBsDQpmKg0KMC44NzggMC44NzggMC44NzggcmcNCjAuMDAw
IDAuMDAwIDAuMDAwIFJHDQowLjEyMCB3DQpbIF0gMCBkDQoxIEoNCjEgag0KMTAxLjc2MCAzMDQu
ODAwIG0NCjEwMi45NjAgMzAzLjM2MCBsDQoxMDIuOTYwIDI3OC4xNjAgbA0KMTAxLjc2MCAyNzYu
OTYwIGwNCjEwMS43NjAgMzA0LjU2MCBsDQpmKg0KMC4wMDAgMC4wMDAgMC4wMDAgcmcNCjAuMDAw
IDAuMDAwIDAuMDAwIFJHDQowLjI0MCB3DQpbIF0gMCBkDQoxIEoNCjEgag0KOTIuNzYwIDI5Ny42
MDAgbQ0KOTIuODgwIDI5Ny42MDAgbA0KOTMuMDAwIDI5Ny42MDAgbA0KOTMuMTIwIDI5Ny42MDAg
bA0KOTMuMjQwIDI5Ny42MDAgbA0KOTMuMzYwIDI5Ny42MDAgbA0KOTMuNDgwIDI5Ny42MDAgbA0K
OTMuNjAwIDI5Ny40ODAgbA0KOTMuNzIwIDI5Ny40ODAgbA0KOTMuODQwIDI5Ny40ODAgbA0KOTMu
OTYwIDI5Ny40ODAgbA0KOTQuMDgwIDI5Ny40ODAgbA0KOTQuMjAwIDI5Ny40ODAgbA0KOTQuMzIw
IDI5Ny40ODAgbA0KOTQuNDQwIDI5Ny40ODAgbA0KOTQuNTYwIDI5Ny40ODAgbA0KOTQuNjgwIDI5
Ny40ODAgbA0KOTQuNjgwIDI5Ny4zNjAgbA0KOTQuODAwIDI5Ny4zNjAgbA0KOTQuOTIwIDI5Ny4z
NjAgbA0KOTUuMDQwIDI5Ny4zNjAgbA0KOTUuMTYwIDI5Ny4zNjAgbA0KOTUuMjgwIDI5Ny4zNjAg
bA0KOTUuNDAwIDI5Ny4zNjAgbA0KOTUuNTIwIDI5Ny4zNjAgbA0KOTUuNjQwIDI5Ny4zNjAgbA0K
OTUuNzYwIDI5Ny4zNjAgbA0KOTUuODgwIDI5Ny4zNjAgbA0KOTYuMDAwIDI5Ny4zNjAgbA0KOTYu
MTIwIDI5Ny4zNjAgbA0KOTYuMjQwIDI5Ny4zNjAgbA0KOTYuMzYwIDI5Ny4zNjAgbA0KOTYuNDgw
IDI5Ny4zNjAgbA0KOTYuNjAwIDI5Ny4zNjAgbA0KOTYuNzIwIDI5Ny4zNjAgbA0KOTYuODQwIDI5
Ny4zNjAgbA0KOTYuOTYwIDI5Ny4zNjAgbA0KOTcuMDgwIDI5Ny4zNjAgbA0KOTcuMjAwIDI5Ny4z
NjAgbA0KOTcuMjAwIDI5Ny4yNDAgbA0KOTcuMzIwIDI5Ny4yNDAgbA0KOTcuNDQwIDI5Ny4yNDAg
bA0KOTcuNTYwIDI5Ny4yNDAgbA0KOTcuNjgwIDI5Ny4yNDAgbA0KOTcuODAwIDI5Ny4yNDAgbA0K
OTcuOTIwIDI5Ny4yNDAgbA0KOTguMDQwIDI5Ny4yNDAgbA0KOTguMTYwIDI5Ny4yNDAgbA0KOTgu
MjgwIDI5Ny4yNDAgbA0KOTguNDAwIDI5Ny4yNDAgbA0KOTguNjQwIDI5Ny4yNDAgbA0KOTguODgw
IDI5Ny4yNDAgbA0KOTkuMDAwIDI5Ny4yNDAgbA0KOTkuMTIwIDI5Ny4yNDAgbA0KOTkuMjQwIDI5
Ny4yNDAgbA0KOTkuNDgwIDI5Ny4yNDAgbA0KOTkuNjAwIDI5Ny4yNDAgbA0KOTkuODQwIDI5Ny4x
MjAgbA0KMTAwLjA4MCAyOTcuMTIwIGwNCjEwMC4zMjAgMjk3LjEyMCBsDQoxMDAuNTYwIDI5Ny4x
MjAgbA0KMTAwLjkyMCAyOTcuMTIwIGwNCjEwMS44ODAgMjk3LjEyMCBsDQoxMDIuNzIwIDI5Ny4x
MjAgbA0KMTAzLjA4MCAyOTcuMTIwIGwNCjEwMy40NDAgMjk3LjEyMCBsDQoxMDMuNjgwIDI5Ny4x
MjAgbA0KMTAzLjkyMCAyOTcuMTIwIGwNCjEwNC4wNDAgMjk3LjI0MCBsDQoxMDQuMjgwIDI5Ny4y
NDAgbA0KMTA0LjQwMCAyOTcuMjQwIGwNCjEwNC41MjAgMjk3LjI0MCBsDQoxMDQuNzYwIDI5Ny4y
NDAgbA0KMTA0Ljg4MCAyOTcuMjQwIGwNCjEwNS4wMDAgMjk3LjI0MCBsDQoxMDUuMTIwIDI5Ny4y
NDAgbA0KMTA1LjI0MCAyOTcuMjQwIGwNCjEwNS4zNjAgMjk3LjI0MCBsDQoxMDUuNDgwIDI5Ny4y
NDAgbA0KMTA1LjYwMCAyOTcuMjQwIGwNCjEwNS43MjAgMjk3LjI0MCBsDQoxMDUuODQwIDI5Ny4y
NDAgbA0KMTA1Ljk2MCAyOTcuMjQwIGwNCjEwNi4wODAgMjk3LjI0MCBsDQoxMDYuMjAwIDI5Ny4y
NDAgbA0KMTA2LjMyMCAyOTcuMjQwIGwNCjEwNi40NDAgMjk3LjI0MCBsDQoxMDYuNTYwIDI5Ny4z
NjAgbA0KMTA2LjY4MCAyOTcuMzYwIGwNCjEwNi44MDAgMjk3LjM2MCBsDQoxMDYuOTIwIDI5Ny4z
NjAgbA0KMTA3LjA0MCAyOTcuMzYwIGwNCjEwNy4xNjAgMjk3LjM2MCBsDQoxMDcuMjgwIDI5Ny4z
NjAgbA0KMTA3LjQwMCAyOTcuMzYwIGwNCjEwNy41MjAgMjk3LjM2MCBsDQoxMDcuNjQwIDI5Ny4z
NjAgbA0KMTA3Ljc2MCAyOTcuMzYwIGwNCjEwNy44ODAgMjk3LjM2MCBsDQoxMDguMDAwIDI5Ny4z
NjAgbA0KMTA4LjEyMCAyOTcuMzYwIGwNCjEwOC4yNDAgMjk3LjM2MCBsDQoxMDguMzYwIDI5Ny4z
NjAgbA0KMTA4LjQ4MCAyOTcuMzYwIGwNCjEwOC42MDAgMjk3LjM2MCBsDQoxMDguNzIwIDI5Ny4z
NjAgbA0KMTA4Ljg0MCAyOTcuMzYwIGwNCjEwOC45NjAgMjk3LjM2MCBsDQoxMDkuMDgwIDI5Ny40
ODAgbA0KMTA5LjIwMCAyOTcuNDgwIGwNCjEwOS4zMjAgMjk3LjQ4MCBsDQoxMDkuNDQwIDI5Ny40
ODAgbA0KMTA5LjU2MCAyOTcuNDgwIGwNCjEwOS42ODAgMjk3LjQ4MCBsDQoxMDkuODAwIDI5Ny40
ODAgbA0KMTA5LjkyMCAyOTcuNDgwIGwNCjExMC4wNDAgMjk3LjQ4MCBsDQoxMTAuMTYwIDI5Ny40
ODAgbA0KMTEwLjE2MCAyOTcuNjAwIGwNCjExMC4yODAgMjk3LjYwMCBsDQoxMTAuNDAwIDI5Ny42
MDAgbA0KMTEwLjUyMCAyOTcuNjAwIGwNCjExMC42NDAgMjk3LjYwMCBsDQoxMTAuNzYwIDI5Ny42
MDAgbA0KMTEwLjg4MCAyOTcuNjAwIGwNCjExMC44ODAgMjg0Ljc2MCBsDQoxMTAuNzYwIDI4NC43
NjAgbA0KMTEwLjY0MCAyODQuNzYwIGwNCjExMC41MjAgMjg0Ljc2MCBsDQoxMTAuNDAwIDI4NC43
NjAgbA0KMTEwLjI4MCAyODQuNzYwIGwNCjExMC4xNjAgMjg0Ljc2MCBsDQoxMTAuMDQwIDI4NC43
NjAgbA0KMTA5LjkyMCAyODQuNzYwIGwNCjEwOS44MDAgMjg0Ljc2MCBsDQoxMDkuNjgwIDI4NC42
NDAgbA0KMTA5LjU2MCAyODQuNjQwIGwNCjEwOS40NDAgMjg0LjY0MCBsDQoxMDkuMzIwIDI4NC42
NDAgbA0KMTA5LjIwMCAyODQuNjQwIGwNCjEwOS4wODAgMjg0LjY0MCBsDQoxMDguOTYwIDI4NC42
NDAgbA0KMTA4Ljg0MCAyODQuNjQwIGwNCjEwOC43MjAgMjg0LjY0MCBsDQoxMDguNjAwIDI4NC42
NDAgbA0KMTA4LjQ4MCAyODQuNjQwIGwNCjEwOC4zNjAgMjg0LjY0MCBsDQoxMDguMjQwIDI4NC42
NDAgbA0KMTA4LjEyMCAyODQuNjQwIGwNCjEwOC4wMDAgMjg0LjUyMCBsDQoxMDcuODgwIDI4NC41
MjAgbA0KMTA3Ljc2MCAyODQuNTIwIGwNCjEwNy42NDAgMjg0LjUyMCBsDQoxMDcuNTIwIDI4NC41
MjAgbA0KMTA3LjQwMCAyODQuNTIwIGwNCjEwNy4yODAgMjg0LjUyMCBsDQoxMDcuMTYwIDI4NC41
MjAgbA0KMTA3LjA0MCAyODQuNTIwIGwNCjEwNi45MjAgMjg0LjUyMCBsDQoxMDYuODAwIDI4NC41
MjAgbA0KMTA2LjY4MCAyODQuNTIwIGwNCjEwNi41NjAgMjg0LjUyMCBsDQoxMDYuNDQwIDI4NC41
MjAgbA0KMTA2LjMyMCAyODQuNTIwIGwNCjEwNi4yMDAgMjg0LjUyMCBsDQoxMDYuMDgwIDI4NC41
MjAgbA0KMTA1Ljk2MCAyODQuNTIwIGwNCjEwNS44NDAgMjg0LjUyMCBsDQoxMDUuNzIwIDI4NC41
MjAgbA0KMTA1LjYwMCAyODQuNTIwIGwNCjEwNS40ODAgMjg0LjUyMCBsDQoxMDUuMzYwIDI4NC41
MjAgbA0KMTA1LjI0MCAyODQuNTIwIGwNCjEwNS4xMjAgMjg0LjUyMCBsDQoxMDUuMDAwIDI4NC41
MjAgbA0KMTA0Ljg4MCAyODQuNDAwIGwNCjEwNC43NjAgMjg0LjQwMCBsDQoxMDQuNTIwIDI4NC40
MDAgbA0KMTA0LjQwMCAyODQuNDAwIGwNCjEwNC4yODAgMjg0LjQwMCBsDQoxMDQuMDQwIDI4NC40
MDAgbA0KMTAzLjkyMCAyODQuNDAwIGwNCjEwMy42ODAgMjg0LjQwMCBsDQoxMDMuNDQwIDI4NC40
MDAgbA0KMTAzLjA4MCAyODQuNDAwIGwNCjEwMi43MjAgMjg0LjQwMCBsDQoxMDEuODgwIDI4NC40
MDAgbA0KMTAwLjkyMCAyODQuNDAwIGwNCjEwMC41NjAgMjg0LjQwMCBsDQoxMDAuMzIwIDI4NC40
MDAgbA0KMTAwLjA4MCAyODQuNDAwIGwNCjk5Ljg0MCAyODQuNDAwIGwNCjk5LjYwMCAyODQuNDAw
IGwNCjk5LjQ4MCAyODQuNDAwIGwNCjk5LjI0MCAyODQuNDAwIGwNCjk5LjEyMCAyODQuNDAwIGwN
Cjk5LjAwMCAyODQuNDAwIGwNCjk4Ljg4MCAyODQuNDAwIGwNCjk4LjY0MCAyODQuNTIwIGwNCjk4
LjQwMCAyODQuNTIwIGwNCjk4LjI4MCAyODQuNTIwIGwNCjk4LjE2MCAyODQuNTIwIGwNCjk4LjA0
MCAyODQuNTIwIGwNCjk3LjkyMCAyODQuNTIwIGwNCjk3LjgwMCAyODQuNTIwIGwNCjk3LjY4MCAy
ODQuNTIwIGwNCjk3LjU2MCAyODQuNTIwIGwNCjk3LjQ0MCAyODQuNTIwIGwNCjk3LjMyMCAyODQu
NTIwIGwNCjk3LjIwMCAyODQuNTIwIGwNCjk3LjA4MCAyODQuNTIwIGwNCjk2Ljk2MCAyODQuNTIw
IGwNCjk2Ljg0MCAyODQuNTIwIGwNCjk2LjcyMCAyODQuNTIwIGwNCjk2LjYwMCAyODQuNTIwIGwN
Cjk2LjQ4MCAyODQuNTIwIGwNCjk2LjM2MCAyODQuNTIwIGwNCjk2LjI0MCAyODQuNTIwIGwNCjk2
LjEyMCAyODQuNTIwIGwNCjk2LjAwMCAyODQuNTIwIGwNCjk1Ljg4MCAyODQuNTIwIGwNCjk1Ljc2
MCAyODQuNTIwIGwNCjk1LjY0MCAyODQuNTIwIGwNCjk1LjY0MCAyODQuNjQwIGwNCjk1LjUyMCAy
ODQuNjQwIGwNCjk1LjQwMCAyODQuNjQwIGwNCjk1LjI4MCAyODQuNjQwIGwNCjk1LjE2MCAyODQu
NjQwIGwNCjk1LjA0MCAyODQuNjQwIGwNCjk0LjkyMCAyODQuNjQwIGwNCjk0LjgwMCAyODQuNjQw
IGwNCjk0LjY4MCAyODQuNjQwIGwNCjk0LjU2MCAyODQuNjQwIGwNCjk0LjQ0MCAyODQuNjQwIGwN
Cjk0LjMyMCAyODQuNjQwIGwNCjk0LjIwMCAyODQuNjQwIGwNCjk0LjA4MCAyODQuNjQwIGwNCjkz
Ljk2MCAyODQuNjQwIGwNCjkzLjk2MCAyODQuNzYwIGwNCjkzLjg0MCAyODQuNzYwIGwNCjkzLjcy
MCAyODQuNzYwIGwNCjkzLjYwMCAyODQuNzYwIGwNCjkzLjQ4MCAyODQuNzYwIGwNCjkzLjM2MCAy
ODQuNzYwIGwNCjkzLjI0MCAyODQuNzYwIGwNCjkzLjEyMCAyODQuNzYwIGwNCjkzLjAwMCAyODQu
NzYwIGwNCjkyLjg4MCAyODQuNzYwIGwNCjkyLjc2MCAyODQuNzYwIGwNCjkyLjc2MCAyOTcuNDgw
IGwNCmIqDQowLjAwMCAwLjAwMCAwLjAwMCByZw0KMC4wMDAgMC4wMDAgMC4wMDAgUkcNCjAuMjQw
IHcNClsgXSAwIGQNCjEgSg0KMSBqDQo5My44NDAgMjkwLjE2MCAxNi41NjAgNy4wODAgcmUNCm4N
CkJUDQoxLjAwMCAwLjAwMCAwLjAwMCAxLjAwMCA5NC42ODAgMjkxLjk2MCBUbQ0KL0YyIDQuNzg3
IFRmDQowIFRyDQowLjg3OCAwLjg3OCAwLjg3OCByZw0KMC4wMDAgVGMNCjEyMi4xODUgVHoNCihE
RUxMKVRqDQpFVA0KMC4wMDAgMC4wMDAgMC4wMDAgcmcNCjAuMDAwIDAuMDAwIDAuMDAwIFJHDQow
LjI0MCB3DQpbIF0gMCBkDQoxIEoNCjEgag0KOTMuNzIwIDI4NC42NDAgMTYuODAwIDYuOTYwIHJl
DQpuDQpCVA0KMS4wMDAgMC4wMDAgMC4wMDAgMS4wMDAgOTMuNzIwIDI4OS4wODAgVG0NCi9GMyAy
LjMxMSBUZg0KMCBUcg0KMC44NzggMC44NzggMC44NzggcmcNCjAuMDAwIFRjDQoxMDYuMDY2IFR6
DQooUE9XRVJFREdFKVRqDQpFVA0KQlQNCjEuMDAwIDAuMDAwIDAuMDAwIDEuMDAwIDk3LjgwMCAy
ODUuNjAwIFRtDQovRjMgMi4zMTEgVGYNCjAgVHINCjAuODc4IDAuODc4IDAuODc4IHJnDQowLjAw
MCBUYw0KMTIyLjkzOSBUeg0KKDI0NTBSKVRqDQpFVA0KMC42MjcgMC42MjcgMC42NDMgUkcNCjAu
MjQwIHcNClsgXSAwIGQNCjEgSg0KMSBqDQozMi41MjAgMzEwLjMyMCBtDQo1Ny4yNDAgMzM5LjEy
MCBsDQpTDQowLjYyNyAwLjYyNyAwLjY0MyBSRw0KMC4yNDAgdw0KWyBdIDAgZA0KMSBKDQoxIGoN
CjE0OC40NDAgMzM4Ljc2MCBtDQoxNzMuMTYwIDMwOS45NjAgbA0KUw0KMC42MjcgMC42MjcgMC42
NDMgUkcNCjAuMjQwIHcNClsgXSAwIGQNCjEgSg0KMSBqDQoxMDEuNTIwIDMzOS4xMjAgbQ0KMTAx
LjUyMCAzMDYuNjAwIGwNClMNCjAuMDAwIDAuMDAwIDAuMDAwIHJnDQowLjYyNyAwLjYyNyAwLjY0
MyBSRw0KMC4yNDAgdw0KWyBdIDAgZA0KMSBKDQoxIGoNCjIzLjY0MCAyNzYuMTIwIDE1OC4yODAg
NjMuOTYwIHJlDQpuDQowLjg5NCAwLjc5MiAwLjY5NCByZw0KMC42MjcgMC42MjcgMC42NDMgUkcN
CjAuMjQwIHcNClsgXSAwIGQNCjEgSg0KMSBqDQozNDcuNzYwIDM1MC4wNDAgbQ0KMzA0LjIwMCAz
NTAuMDQwIGwNCjMwNC4yMDAgNDA3LjE2MCBsDQozMDQuMjAwIDQwNy4yODAgbA0KMzA0LjIwMCA0
MDcuNDAwIGwNCjMwNC4yMDAgNDA3LjUyMCBsDQozMDQuMDgwIDQwNy43NjAgbA0KMzA0LjA4MCA0
MDguMDAwIGwNCjMwNC4wODAgNDA4LjI0MCBsDQozMDMuOTYwIDQwOC42MDAgbA0KMzAzLjk2MCA0
MDguOTYwIGwNCjMwMy45NjAgNDA5LjQ0MCBsDQozMDMuODQwIDQwOS44MDAgbA0KMzAzLjg0MCA0
MTAuMjgwIGwNCjMwMy43MjAgNDEwLjY0MCBsDQozMDMuNzIwIDQxMS4xMjAgbA0KMzAzLjcyMCA0
MTEuNDgwIGwNCjMwMy42MDAgNDExLjk2MCBsDQozMDMuNjAwIDQxMi4zMjAgbA0KMzAzLjYwMCA0
MTIuNjgwIGwNCjMwMy42MDAgNDEzLjA0MCBsDQozMDMuNjAwIDQxMy40MDAgbA0KMzAzLjYwMCA0
MTMuNzYwIGwNCjMwMy42MDAgNDE0LjEyMCBsDQozMDMuNjAwIDQxNC40ODAgbA0KMzAzLjcyMCA0
MTQuOTYwIGwNCjMwMy43MjAgNDE1LjMyMCBsDQozMDMuNzIwIDQxNS44MDAgbA0KMzAzLjg0MCA0
MTYuMTYwIGwNCjMwMy44NDAgNDE2LjY0MCBsDQozMDMuOTYwIDQxNy4wMDAgbA0KMzAzLjk2MCA0
MTcuMzYwIGwNCjMwNC4wODAgNDE3LjcyMCBsDQozMDQuMDgwIDQxNy45NjAgbA0KMzA0LjA4MCA0
MTguMjAwIGwNCjMwNC4yMDAgNDE4LjMyMCBsDQozMDQuMjAwIDQxOC40NDAgbA0KMzA0LjIwMCA0
MTguNTYwIGwNCjM0Ny43NjAgNDE4LjU2MCBsDQozNDcuNzYwIDQxOC40NDAgbA0KMzQ3Ljc2MCA0
MTguMzIwIGwNCjM0Ny43NjAgNDE4LjIwMCBsDQozNDcuNzYwIDQxNy45NjAgbA0KMzQ3Ljg4MCA0
MTcuNjAwIGwNCjM0Ny44ODAgNDE3LjI0MCBsDQozNDcuODgwIDQxNi44ODAgbA0KMzQ4LjAwMCA0
MTYuNTIwIGwNCjM0OC4wMDAgNDE2LjE2MCBsDQozNDguMDAwIDQxNS42ODAgbA0KMzQ4LjAwMCA0
MTUuMzIwIGwNCjM0OC4xMjAgNDE0Ljg0MCBsDQozNDguMTIwIDQxNC40ODAgbA0KMzQ4LjEyMCA0
MTQuMDAwIGwNCjM0OC4xMjAgNDEzLjY0MCBsDQozNDguMTIwIDQxMy40MDAgbA0KMzQ4LjEyMCA0
MTMuMDQwIGwNCjM0OC4xMjAgNDEyLjY4MCBsDQozNDguMTIwIDQxMi4zMjAgbA0KMzQ4LjEyMCA0
MTEuOTYwIGwNCjM0OC4xMjAgNDExLjQ4MCBsDQozNDguMDAwIDQxMS4xMjAgbA0KMzQ4LjAwMCA0
MTAuNjQwIGwNCjM0OC4wMDAgNDEwLjE2MCBsDQozNDguMDAwIDQwOS44MDAgbA0KMzQ3Ljg4MCA0
MDkuMzIwIGwNCjM0Ny44ODAgNDA4Ljk2MCBsDQozNDcuODgwIDQwOC42MDAgbA0KMzQ3Ljc2MCA0
MDguMjQwIGwNCjM0Ny43NjAgNDA4LjAwMCBsDQozNDcuNzYwIDQwNy43NjAgbA0KMzQ3Ljc2MCA0
MDcuNTIwIGwNCjM0Ny43NjAgNDA3LjQwMCBsDQozNDcuNzYwIDM1MC4wNDAgbA0KZioNCjAuMDAw
IDAuMDAwIDAuMDAwIFJHDQowLjk2MCB3DQpbIF0gMCBkDQoxIEoNCjEgag0KMzQ3Ljc2MCAzNTAu
MDQwIG0NCjMwNC4yMDAgMzUwLjA0MCBsDQozMDQuMjAwIDQwNy4xNjAgbA0KMzA0LjIwMCA0MDcu
MjgwIGwNCjMwNC4yMDAgNDA3LjQwMCBsDQozMDQuMjAwIDQwNy41MjAgbA0KMzA0LjA4MCA0MDcu
NzYwIGwNCjMwNC4wODAgNDA4LjAwMCBsDQozMDQuMDgwIDQwOC4yNDAgbA0KMzAzLjk2MCA0MDgu
NjAwIGwNCjMwMy45NjAgNDA4Ljk2MCBsDQozMDMuOTYwIDQwOS40NDAgbA0KMzAzLjg0MCA0MDku
ODAwIGwNCjMwMy44NDAgNDEwLjI4MCBsDQozMDMuNzIwIDQxMC42NDAgbA0KMzAzLjcyMCA0MTEu
MTIwIGwNCjMwMy43MjAgNDExLjQ4MCBsDQozMDMuNjAwIDQxMS45NjAgbA0KMzAzLjYwMCA0MTIu
MzIwIGwNCjMwMy42MDAgNDEyLjY4MCBsDQozMDMuNjAwIDQxMy4wNDAgbA0KMzAzLjYwMCA0MTMu
NDAwIGwNCjMwMy42MDAgNDEzLjc2MCBsDQozMDMuNjAwIDQxNC4xMjAgbA0KMzAzLjYwMCA0MTQu
NDgwIGwNCjMwMy43MjAgNDE0Ljk2MCBsDQozMDMuNzIwIDQxNS4zMjAgbA0KMzAzLjcyMCA0MTUu
ODAwIGwNCjMwMy44NDAgNDE2LjE2MCBsDQozMDMuODQwIDQxNi42NDAgbA0KMzAzLjk2MCA0MTcu
MDAwIGwNCjMwMy45NjAgNDE3LjM2MCBsDQozMDQuMDgwIDQxNy43MjAgbA0KMzA0LjA4MCA0MTcu
OTYwIGwNCjMwNC4wODAgNDE4LjIwMCBsDQozMDQuMjAwIDQxOC4zMjAgbA0KMzA0LjIwMCA0MTgu
NDQwIGwNCjMwNC4yMDAgNDE4LjU2MCBsDQozNDcuNzYwIDQxOC41NjAgbA0KMzQ3Ljc2MCA0MTgu
NDQwIGwNCjM0Ny43NjAgNDE4LjMyMCBsDQozNDcuNzYwIDQxOC4yMDAgbA0KMzQ3Ljc2MCA0MTcu
OTYwIGwNCjM0Ny44ODAgNDE3LjYwMCBsDQozNDcuODgwIDQxNy4yNDAgbA0KMzQ3Ljg4MCA0MTYu
ODgwIGwNCjM0OC4wMDAgNDE2LjUyMCBsDQozNDguMDAwIDQxNi4xNjAgbA0KMzQ4LjAwMCA0MTUu
NjgwIGwNCjM0OC4wMDAgNDE1LjMyMCBsDQozNDguMTIwIDQxNC44NDAgbA0KMzQ4LjEyMCA0MTQu
NDgwIGwNCjM0OC4xMjAgNDE0LjAwMCBsDQozNDguMTIwIDQxMy42NDAgbA0KMzQ4LjEyMCA0MTMu
NDAwIGwNCjM0OC4xMjAgNDEzLjA0MCBsDQozNDguMTIwIDQxMi42ODAgbA0KMzQ4LjEyMCA0MTIu
MzIwIGwNCjM0OC4xMjAgNDExLjk2MCBsDQozNDguMTIwIDQxMS40ODAgbA0KMzQ4LjAwMCA0MTEu
MTIwIGwNCjM0OC4wMDAgNDEwLjY0MCBsDQozNDguMDAwIDQxMC4xNjAgbA0KMzQ4LjAwMCA0MDku
ODAwIGwNCjM0Ny44ODAgNDA5LjMyMCBsDQozNDcuODgwIDQwOC45NjAgbA0KMzQ3Ljg4MCA0MDgu
NjAwIGwNCjM0Ny43NjAgNDA4LjI0MCBsDQozNDcuNzYwIDQwOC4wMDAgbA0KMzQ3Ljc2MCA0MDcu
NzYwIGwNCjM0Ny43NjAgNDA3LjUyMCBsDQozNDcuNzYwIDQwNy40MDAgbA0KMzQ3Ljc2MCAzNTAu
MDQwIGwNClMNCjAuMDAwIDAuNDk4IDAuNDk4IHJnDQowLjAwMCAwLjAwMCAwLjAwMCBSRw0KMC45
NjAgdw0KWyBdIDAgZA0KMSBKDQoxIGoNCjM0MS4xNjAgNDI0LjY4MCBtDQozMTAuODAwIDQyNC42
ODAgbA0KMzA0LjIwMCA0MTguNTYwIGwNCjM0Ny43NjAgNDE4LjU2MCBsDQozNDEuMTYwIDQyNC42
ODAgbA0KZioNCjAuMDAwIDAuMDAwIDAuMDAwIFJHDQowLjk2MCB3DQpbIF0gMCBkDQoxIEoNCjEg
ag0KMzQxLjE2MCA0MjQuNjgwIG0NCjMxMC44MDAgNDI0LjY4MCBsDQozMDQuMjAwIDQxOC41NjAg
bA0KMzQ3Ljc2MCA0MTguNTYwIGwNCjM0MS4xNjAgNDI0LjY4MCBsDQpTDQowLjgwMCAwLjAwMCAw
LjAwMCByZw0KMC4wMDAgMC4wMDAgMC4wMDAgUkcNCjAuOTYwIHcNClsgXSAwIGQNCjEgSg0KMSBq
DQozMDYuNzIwIDQxNi40MDAgbQ0KMzA2LjQ4MCA0MTYuNDAwIGwNCjMwNi40ODAgNDE2LjI4MCBs
DQozMDYuNDgwIDQxNi4xNjAgbA0KMzA2LjM2MCA0MTYuMTYwIGwNCjMwNi4zNjAgNDE2LjI4MCBs
DQozMDYuMzYwIDQxNi41MjAgbA0KMzA2LjM2MCA0MTYuNjQwIGwNCjMwNi4zNjAgNDE2Ljc2MCBs
DQozMDYuNDgwIDQxNi43NjAgbA0KMzA2LjQ4MCA0MTYuNjQwIGwNCjMwNi43MjAgNDE2LjY0MCBs
DQozMDYuNjAwIDQxNi43NjAgbA0KMzA2LjYwMCA0MTYuODgwIGwNCjMwNi40ODAgNDE2Ljg4MCBs
DQozMDYuMjQwIDQxNi44ODAgbA0KMzA2LjI0MCA0MTYuNzYwIGwNCjMwNi4xMjAgNDE2LjUyMCBs
DQozMDYuMTIwIDQxNi40MDAgbA0KMzA2LjEyMCA0MTYuMTYwIGwNCjMwNi4yNDAgNDE2LjA0MCBs
DQozMDYuNDgwIDQxNi4wNDAgbA0KMzA2LjYwMCA0MTYuMDQwIGwNCjMwNi42MDAgNDE2LjE2MCBs
DQozMDYuNzIwIDQxNi4yODAgbA0KMzA2LjcyMCA0MTYuNDAwIGwNCmYqDQowLjgwMCAwLjAwMCAw
LjAwMCByZw0KMC4wMDAgMC4wMDAgMC4wMDAgUkcNCjAuOTYwIHcNClsgXSAwIGQNCjEgSg0KMSBq
DQozMDYuOTYwIDQxNi4wNDAgbQ0KMzA3LjA4MCA0MTYuMDQwIGwNCjMwNy4wODAgNDE2LjY0MCBs
DQozMDYuOTYwIDQxNi42NDAgbA0KMzA2Ljk2MCA0MTYuMDQwIGwNCmYqDQowLjgwMCAwLjAwMCAw
LjAwMCByZw0KMC4wMDAgMC4wMDAgMC4wMDAgUkcNCjAuOTYwIHcNClsgXSAwIGQNCjEgSg0KMSBq
DQozMDcuNjgwIDQxNi41MjAgbQ0KMzA3LjgwMCA0MTYuNTIwIGwNCjMwNy42ODAgNDE2LjY0MCBs
DQozMDcuNTYwIDQxNi42NDAgbA0KMzA3LjQ0MCA0MTYuNjQwIGwNCjMwNy40NDAgNDE2LjUyMCBs
DQozMDcuNDQwIDQxNi40MDAgbA0KMzA3LjU2MCA0MTYuMjgwIGwNCjMwNy42ODAgNDE2LjI4MCBs
DQozMDcuNjgwIDQxNi4xNjAgbA0KMzA3LjU2MCA0MTYuMTYwIGwNCjMwNy41NjAgNDE2LjI4MCBs
DQozMDcuNDQwIDQxNi4yODAgbA0KMzA3LjQ0MCA0MTYuMTYwIGwNCjMwNy40NDAgNDE2LjA0MCBs
DQozMDcuNTYwIDQxNi4wNDAgbA0KMzA3LjY4MCA0MTYuMDQwIGwNCjMwNy44MDAgNDE2LjE2MCBs
DQozMDcuODAwIDQxNi4yODAgbA0KMzA3LjY4MCA0MTYuMjgwIGwNCjMwNy42ODAgNDE2LjQwMCBs
DQozMDcuNTYwIDQxNi40MDAgbA0KMzA3LjU2MCA0MTYuNTIwIGwNCjMwNy41NjAgNDE2LjY0MCBs
DQozMDcuNjgwIDQxNi41MjAgbA0KZioNCjAuODAwIDAuMDAwIDAuMDAwIHJnDQowLjAwMCAwLjAw
MCAwLjAwMCBSRw0KMC45NjAgdw0KWyBdIDAgZA0KMSBKDQoxIGoNCjMwOC40MDAgNDE2LjI4MCBt
DQozMDguMjgwIDQxNi4yODAgbA0KMzA4LjI4MCA0MTYuMTYwIGwNCjMwOC4xNjAgNDE2LjE2MCBs
DQozMDguMTYwIDQxNi4yODAgbA0KMzA4LjE2MCA0MTYuNDAwIGwNCjMwOC4xNjAgNDE2LjUyMCBs
DQozMDguMjgwIDQxNi42NDAgbA0KMzA4LjI4MCA0MTYuNTIwIGwNCjMwOC40MDAgNDE2LjUyMCBs
DQozMDguNDAwIDQxNi42NDAgbA0KMzA4LjI4MCA0MTYuNjQwIGwNCjMwOC4wNDAgNDE2LjY0MCBs
DQozMDguMDQwIDQxNi41MjAgbA0KMzA4LjA0MCA0MTYuNDAwIGwNCjMwOC4wNDAgNDE2LjI4MCBs
DQozMDguMDQwIDQxNi4xNjAgbA0KMzA4LjA0MCA0MTYuMDQwIGwNCjMwOC4yODAgNDE2LjA0MCBs
DQozMDguNDAwIDQxNi4xNjAgbA0KMzA4LjQwMCA0MTYuMjgwIGwNCmYqDQowLjAwMCAwLjAwMCAw
LjAwMCBSRw0KMC45NjAgdw0KWyBdIDAgZA0KMSBKDQoxIGoNCjAuODAwIDAuMDAwIDAuMDAwIHJn
DQozMDguNzYwIDQxNi4yODAgbQ0KMzA4Ljc2MCA0MTYuNDAwIGwNCjMwOC43NjAgNDE2LjUyMCBs
DQozMDguODgwIDQxNi42NDAgbA0KMzA4Ljg4MCA0MTYuNTIwIGwNCjMwOC44ODAgNDE2LjQwMCBs
DQozMDguODgwIDQxNi4yODAgbA0KMzA4Ljg4MCA0MTYuMTYwIGwNCjMwOC43NjAgNDE2LjE2MCBs
DQozMDguNzYwIDQxNi4yODAgbA0KaA0KMzA4LjY0MCA0MTYuNDAwIG0NCjMwOC42NDAgNDE2LjI4
MCBsDQozMDguNjQwIDQxNi4xNjAgbA0KMzA4Ljc2MCA0MTYuMDQwIGwNCjMwOC44ODAgNDE2LjA0
MCBsDQozMDkuMDAwIDQxNi4wNDAgbA0KMzA5LjAwMCA0MTYuMTYwIGwNCjMwOS4wMDAgNDE2LjI4
MCBsDQozMDkuMDAwIDQxNi40MDAgbA0KMzA5LjAwMCA0MTYuNTIwIGwNCjMwOS4wMDAgNDE2LjY0
MCBsDQozMDguODgwIDQxNi42NDAgbA0KMzA4Ljc2MCA0MTYuNjQwIGwNCjMwOC42NDAgNDE2LjUy
MCBsDQozMDguNjQwIDQxNi40MDAgbA0KZioNCjAuODAwIDAuMDAwIDAuMDAwIHJnDQowLjAwMCAw
LjAwMCAwLjAwMCBSRw0KMC4xMjAgdw0KWyBdIDAgZA0KMSBKDQoxIGoNCjMxMC4wODAgNDE2LjY0
MCBtDQozMTAuMjAwIDQxNi42NDAgbA0KMzEwLjIwMCA0MTYuNzYwIGwNCjMxMC4wODAgNDE2Ljg4
MCBsDQozMDkuOTYwIDQxNi44ODAgbA0KMzA5Ljg0MCA0MTYuODgwIGwNCjMwOS43MjAgNDE2Ljc2
MCBsDQozMDkuNzIwIDQxNi42NDAgbA0KMzA5LjcyMCA0MTYuNTIwIGwNCjMwOS44NDAgNDE2LjUy
MCBsDQozMDkuOTYwIDQxNi40MDAgbA0KMzEwLjA4MCA0MTYuMjgwIGwNCjMxMC4wODAgNDE2LjE2
MCBsDQozMDkuOTYwIDQxNi4xNjAgbA0KMzA5Ljg0MCA0MTYuMTYwIGwNCjMwOS44NDAgNDE2LjI4
MCBsDQozMDkuODQwIDQxNi40MDAgbA0KMzA5LjcyMCA0MTYuNDAwIGwNCjMwOS43MjAgNDE2LjI4
MCBsDQozMDkuNzIwIDQxNi4xNjAgbA0KMzA5Ljg0MCA0MTYuMDQwIGwNCjMwOS45NjAgNDE2LjA0
MCBsDQozMTAuMDgwIDQxNi4wNDAgbA0KMzEwLjIwMCA0MTYuMTYwIGwNCjMxMC4yMDAgNDE2LjI4
MCBsDQozMTAuMjAwIDQxNi40MDAgbA0KMzEwLjA4MCA0MTYuNTIwIGwNCjMwOS45NjAgNDE2LjUy
MCBsDQozMDkuOTYwIDQxNi42NDAgbA0KMzA5Ljg0MCA0MTYuNjQwIGwNCjMwOS44NDAgNDE2Ljc2
MCBsDQozMDkuOTYwIDQxNi43NjAgbA0KMzEwLjA4MCA0MTYuNzYwIGwNCjMxMC4wODAgNDE2LjY0
MCBsDQpmKg0KMC44MDAgMC4wMDAgMC4wMDAgcmcNCjAuMDAwIDAuMDAwIDAuMDAwIFJHDQowLjEy
MCB3DQpbIF0gMCBkDQoxIEoNCjEgag0KMzEwLjY4MCA0MTYuNTIwIG0NCjMxMC42ODAgNDE2LjY0
MCBsDQozMTAuNTYwIDQxNi42NDAgbA0KMzEwLjY4MCA0MTYuMjgwIGwNCjMxMC42ODAgNDE2LjA0
MCBsDQozMTAuODAwIDQxNi4wNDAgbA0KMzEwLjgwMCA0MTYuMjgwIGwNCjMxMC45MjAgNDE2LjY0
MCBsDQozMTAuODAwIDQxNi42NDAgbA0KMzEwLjgwMCA0MTYuNTIwIGwNCjMxMC44MDAgNDE2LjQw
MCBsDQozMTAuNjgwIDQxNi40MDAgbA0KMzEwLjY4MCA0MTYuNTIwIGwNCmYqDQowLjgwMCAwLjAw
MCAwLjAwMCByZw0KMC4wMDAgMC4wMDAgMC4wMDAgUkcNCjAuMTIwIHcNClsgXSAwIGQNCjEgSg0K
MSBqDQozMTEuNDAwIDQxNi41MjAgbQ0KMzExLjUyMCA0MTYuNTIwIGwNCjMxMS41MjAgNDE2LjY0
MCBsDQozMTEuNDAwIDQxNi42NDAgbA0KMzExLjI4MCA0MTYuNjQwIGwNCjMxMS4xNjAgNDE2LjY0
MCBsDQozMTEuMTYwIDQxNi41MjAgbA0KMzExLjE2MCA0MTYuNDAwIGwNCjMxMS4yODAgNDE2LjQw
MCBsDQozMTEuMjgwIDQxNi4yODAgbA0KMzExLjQwMCA0MTYuMjgwIGwNCjMxMS40MDAgNDE2LjE2
MCBsDQozMTEuMjgwIDQxNi4xNjAgbA0KMzExLjI4MCA0MTYuMjgwIGwNCjMxMS4xNjAgNDE2LjI4
MCBsDQozMTEuMTYwIDQxNi4xNjAgbA0KMzExLjI4MCA0MTYuMDQwIGwNCjMxMS40MDAgNDE2LjA0
MCBsDQozMTEuNTIwIDQxNi4xNjAgbA0KMzExLjUyMCA0MTYuMjgwIGwNCjMxMS40MDAgNDE2LjQw
MCBsDQozMTEuMjgwIDQxNi41MjAgbA0KMzExLjQwMCA0MTYuNjQwIGwNCjMxMS40MDAgNDE2LjUy
MCBsDQpmKg0KMC44MDAgMC4wMDAgMC4wMDAgcmcNCjAuMDAwIDAuMDAwIDAuMDAwIFJHDQowLjEy
MCB3DQpbIF0gMCBkDQoxIEoNCjEgag0KMzExLjc2MCA0MTYuNjQwIG0NCjMxMS43NjAgNDE2LjUy
MCBsDQozMTEuODgwIDQxNi41MjAgbA0KMzExLjg4MCA0MTYuMDQwIGwNCjMxMi4wMDAgNDE2LjA0
MCBsDQozMTIuMDAwIDQxNi41MjAgbA0KMzEyLjEyMCA0MTYuNTIwIGwNCjMxMi4xMjAgNDE2LjY0
MCBsDQozMTEuNzYwIDQxNi42NDAgbA0KZioNCjAuODAwIDAuMDAwIDAuMDAwIHJnDQowLjAwMCAw
LjAwMCAwLjAwMCBSRw0KMC4xMjAgdw0KWyBdIDAgZA0KMSBKDQoxIGoNCjMxMi4zNjAgNDE2LjA0
MCBtDQozMTIuNzIwIDQxNi4wNDAgbA0KMzEyLjcyMCA0MTYuMTYwIGwNCjMxMi40ODAgNDE2LjE2
MCBsDQozMTIuNDgwIDQxNi4yODAgbA0KMzEyLjcyMCA0MTYuMjgwIGwNCjMxMi43MjAgNDE2LjQw
MCBsDQozMTIuNDgwIDQxNi40MDAgbA0KMzEyLjQ4MCA0MTYuNTIwIGwNCjMxMi43MjAgNDE2LjUy
MCBsDQozMTIuNzIwIDQxNi42NDAgbA0KMzEyLjM2MCA0MTYuNjQwIGwNCjMxMi4zNjAgNDE2LjA0
MCBsDQpmKg0KMC44MDAgMC4wMDAgMC4wMDAgcmcNCjAuMDAwIDAuMDAwIDAuMDAwIFJHDQowLjEy
MCB3DQpbIF0gMCBkDQoxIEoNCjEgag0KMzEzLjA4MCA0MTYuMDQwIG0NCjMxMy4wODAgNDE2LjI4
MCBsDQozMTMuMDgwIDQxNi40MDAgbA0KMzEzLjA4MCA0MTYuNTIwIGwNCjMxMy4wODAgNDE2LjY0
MCBsDQozMTMuMjAwIDQxNi4wNDAgbA0KMzEzLjQ0MCA0MTYuNjQwIGwNCjMxMy4zMjAgNDE2LjUy
MCBsDQozMTMuMzIwIDQxNi40MDAgbA0KMzEzLjMyMCA0MTYuMjgwIGwNCjMxMy4zMjAgNDE2LjA0
MCBsDQozMTMuNDQwIDQxNi4wNDAgbA0KMzEzLjQ0MCA0MTYuNjQwIGwNCjMxMy4zMjAgNDE2LjY0
MCBsDQozMTMuMjAwIDQxNi40MDAgbA0KMzEzLjIwMCA0MTYuMjgwIGwNCjMxMy4yMDAgNDE2LjQw
MCBsDQozMTMuMDgwIDQxNi42NDAgbA0KMzEyLjk2MCA0MTYuNjQwIGwNCjMxMi45NjAgNDE2LjA0
MCBsDQozMTMuMDgwIDQxNi4wNDAgbA0KZioNCjAuODAwIDAuMDAwIDAuMDAwIHJnDQowLjAwMCAw
LjAwMCAwLjAwMCBSRw0KMC4xMjAgdw0KWyBdIDAgZA0KMSBKDQoxIGoNCjMxNC4wNDAgNDE2LjUy
MCBtDQozMTQuMTYwIDQxNi41MjAgbA0KMzE0LjA0MCA0MTYuNjQwIGwNCjMxMy45MjAgNDE2LjY0
MCBsDQozMTMuODAwIDQxNi42NDAgbA0KMzEzLjgwMCA0MTYuNTIwIGwNCjMxMy44MDAgNDE2LjQw
MCBsDQozMTMuOTIwIDQxNi4yODAgbA0KMzE0LjA0MCA0MTYuMjgwIGwNCjMxNC4wNDAgNDE2LjE2
MCBsDQozMTMuOTIwIDQxNi4xNjAgbA0KMzEzLjkyMCA0MTYuMjgwIGwNCjMxMy44MDAgNDE2LjI4
MCBsDQozMTMuODAwIDQxNi4xNjAgbA0KMzEzLjgwMCA0MTYuMDQwIGwNCjMxMy45MjAgNDE2LjA0
MCBsDQozMTQuMDQwIDQxNi4wNDAgbA0KMzE0LjE2MCA0MTYuMTYwIGwNCjMxNC4xNjAgNDE2LjI4
MCBsDQozMTQuMDQwIDQxNi4yODAgbA0KMzE0LjA0MCA0MTYuNDAwIGwNCjMxMy45MjAgNDE2LjQw
MCBsDQozMTMuOTIwIDQxNi41MjAgbA0KMzEzLjkyMCA0MTYuNjQwIGwNCjMxNC4wNDAgNDE2LjUy
MCBsDQpmKg0KMC4wMDAgMC40OTggMC40OTggcmcNCjAuMDAwIDAuMDAwIDAuMDAwIFJHDQowLjEy
MCB3DQpbIF0gMCBkDQoxIEoNCjEgag0KMzE0LjE2MCA0MTMuNTIwIG0NCjMwNi4yNDAgNDEzLjUy
MCBsDQozMDYuMjQwIDQxNS44MDAgbA0KMzE0LjE2MCA0MTUuODAwIGwNCjMxNC4xNjAgNDEzLjUy
MCBsDQpmKg0KMS4wMDAgMS4wMDAgMS4wMDAgUkcNCjAuMjQwIHcNClsgXSAwIGQNCjEgSg0KMSBq
DQozMDguNDAwIDQxMy41MjAgbQ0KMzA4LjQwMCA0MTUuMDgwIGwNClMNCjEuMDAwIDEuMDAwIDEu
MDAwIFJHDQowLjI0MCB3DQpbIF0gMCBkDQoxIEoNCjEgag0KMzA3LjkyMCA0MTMuNTIwIG0NCjMw
Ny45MjAgNDE0Ljg0MCBsDQpTDQoxLjAwMCAxLjAwMCAxLjAwMCBSRw0KMC4yNDAgdw0KWyBdIDAg
ZA0KMSBKDQoxIGoNCjMwNy41NjAgNDEzLjUyMCBtDQozMDcuNTYwIDQxNC42MDAgbA0KUw0KMS4w
MDAgMS4wMDAgMS4wMDAgUkcNCjAuMjQwIHcNClsgXSAwIGQNCjEgSg0KMSBqDQozMDcuMjAwIDQx
My41MjAgbQ0KMzA3LjIwMCA0MTQuMDAwIGwNClMNCjEuMDAwIDEuMDAwIDEuMDAwIFJHDQowLjI0
MCB3DQpbIF0gMCBkDQoxIEoNCjEgag0KMzA2Ljg0MCA0MTMuNTIwIG0NCjMwNi44NDAgNDEzLjc2
MCBsDQpTDQoxLjAwMCAxLjAwMCAxLjAwMCBSRw0KMC4yNDAgdw0KWyBdIDAgZA0KMSBKDQoxIGoN
CjMwNi40ODAgNDEzLjUyMCBtDQozMDYuNDgwIDQxMy43NjAgbA0KUw0KMS4wMDAgMS4wMDAgMS4w
MDAgUkcNCjAuMjQwIHcNClsgXSAwIGQNCjEgSg0KMSBqDQozMDguODgwIDQxMy41MjAgbQ0KMzA4
Ljg4MCA0MTQuODQwIGwNClMNCjEuMDAwIDEuMDAwIDEuMDAwIFJHDQowLjI0MCB3DQpbIF0gMCBk
DQoxIEoNCjEgag0KMzA5LjI0MCA0MTMuNTIwIG0NCjMwOS4yNDAgNDE0LjYwMCBsDQpTDQoxLjAw
MCAxLjAwMCAxLjAwMCBSRw0KMC4yNDAgdw0KWyBdIDAgZA0KMSBKDQoxIGoNCjMwOS42MDAgNDEz
LjUyMCBtDQozMDkuNjAwIDQxNC4wMDAgbA0KUw0KMS4wMDAgMS4wMDAgMS4wMDAgUkcNCjAuMjQw
IHcNClsgXSAwIGQNCjEgSg0KMSBqDQozMDkuODQwIDQxMy41MjAgbQ0KMzA5Ljg0MCA0MTMuNzYw
IGwNClMNCjEuMDAwIDEuMDAwIDEuMDAwIFJHDQowLjI0MCB3DQpbIF0gMCBkDQoxIEoNCjEgag0K
MzEyLjAwMCA0MTMuNTIwIG0NCjMxMi4wMDAgNDE1LjA4MCBsDQpTDQoxLjAwMCAxLjAwMCAxLjAw
MCBSRw0KMC4yNDAgdw0KWyBdIDAgZA0KMSBKDQoxIGoNCjMxMS41MjAgNDEzLjUyMCBtDQozMTEu
NTIwIDQxNC44NDAgbA0KUw0KMS4wMDAgMS4wMDAgMS4wMDAgUkcNCjAuMjQwIHcNClsgXSAwIGQN
CjEgSg0KMSBqDQozMTEuMDQwIDQxMy41MjAgbQ0KMzExLjA0MCA0MTQuNjAwIGwNClMNCjEuMDAw
IDEuMDAwIDEuMDAwIFJHDQowLjI0MCB3DQpbIF0gMCBkDQoxIEoNCjEgag0KMzEwLjgwMCA0MTMu
NTIwIG0NCjMxMC44MDAgNDE0LjAwMCBsDQpTDQoxLjAwMCAxLjAwMCAxLjAwMCBSRw0KMC4yNDAg
dw0KWyBdIDAgZA0KMSBKDQoxIGoNCjMxMC40NDAgNDEzLjUyMCBtDQozMTAuNDQwIDQxMy43NjAg
bA0KUw0KMS4wMDAgMS4wMDAgMS4wMDAgUkcNCjAuMjQwIHcNClsgXSAwIGQNCjEgSg0KMSBqDQoz
MTAuMjAwIDQxMy41MjAgbQ0KMzEwLjIwMCA0MTMuNzYwIGwNClMNCjEuMDAwIDEuMDAwIDEuMDAw
IFJHDQowLjI0MCB3DQpbIF0gMCBkDQoxIEoNCjEgag0KMzEyLjM2MCA0MTMuNTIwIG0NCjMxMi4z
NjAgNDE0Ljg0MCBsDQpTDQoxLjAwMCAxLjAwMCAxLjAwMCBSRw0KMC4yNDAgdw0KWyBdIDAgZA0K
MSBKDQoxIGoNCjMxMi44NDAgNDEzLjUyMCBtDQozMTIuODQwIDQxNC42MDAgbA0KUw0KMS4wMDAg
MS4wMDAgMS4wMDAgUkcNCjAuMjQwIHcNClsgXSAwIGQNCjEgSg0KMSBqDQozMTMuMDgwIDQxMy41
MjAgbQ0KMzEzLjA4MCA0MTQuMDAwIGwNClMNCjEuMDAwIDEuMDAwIDEuMDAwIFJHDQowLjI0MCB3
DQpbIF0gMCBkDQoxIEoNCjEgag0KMzEzLjQ0MCA0MTMuNTIwIG0NCjMxMy40NDAgNDEzLjc2MCBs
DQpTDQoxLjAwMCAxLjAwMCAxLjAwMCBSRw0KMC4yNDAgdw0KWyBdIDAgZA0KMSBKDQoxIGoNCjMx
My44MDAgNDEzLjUyMCBtDQozMTMuODAwIDQxMy43NjAgbA0KUw0KMC4wMDAgMC4wMDAgMC4wMDAg
cmcNCjEuMDAwIDEuMDAwIDEuMDAwIFJHDQowLjI0MCB3DQpbIF0gMCBkDQoxIEoNCjEgag0KMzMy
LjUyMCA0MTYuNDAwIG0NCjMzMi4yODAgNDE2LjQwMCBsDQozMzIuMDQwIDQxNi4yODAgbA0KMzMx
LjkyMCA0MTYuMTYwIGwNCjMzMS44MDAgNDE2LjA0MCBsDQozMzEuNjgwIDQxNS44MDAgbA0KMzMx
LjY4MCA0MTUuNTYwIGwNCjMzMS42ODAgNDE1LjIwMCBsDQozMzEuODAwIDQxNC45NjAgbA0KMzMx
LjkyMCA0MTQuNzIwIGwNCjMzMi4xNjAgNDE0LjYwMCBsDQozMzIuMjgwIDQxNC42MDAgbA0KMzMy
LjUyMCA0MTQuNjAwIGwNCjMzMi43NjAgNDE0LjYwMCBsDQozMzIuODgwIDQxNC42MDAgbA0KMzMz
LjEyMCA0MTQuODQwIGwNCjMzMy4yNDAgNDE0Ljk2MCBsDQozMzMuMjQwIDQxNS4wODAgbA0KMzMz
LjI0MCA0MTUuMjAwIGwNCjMzMy4wMDAgNDE1LjIwMCBsDQozMzMuMDAwIDQxNS4wODAgbA0KMzMy
Ljg4MCA0MTQuOTYwIGwNCjMzMi44ODAgNDE0Ljg0MCBsDQozMzIuNjQwIDQxNC44NDAgbA0KMzMy
LjUyMCA0MTQuNzIwIGwNCjMzMi4yODAgNDE0Ljg0MCBsDQozMzIuMTYwIDQxNC44NDAgbA0KMzMy
LjA0MCA0MTQuOTYwIGwNCjMzMi4wNDAgNDE1LjA4MCBsDQozMzEuOTIwIDQxNS4zMjAgbA0KMzMx
LjkyMCA0MTUuNDQwIGwNCjMzMS45MjAgNDE1LjY4MCBsDQozMzIuMDQwIDQxNS45MjAgbA0KMzMy
LjA0MCA0MTYuMDQwIGwNCjMzMi4xNjAgNDE2LjE2MCBsDQozMzIuNDAwIDQxNi4yODAgbA0KMzMy
LjUyMCA0MTYuMjgwIGwNCjMzMi42NDAgNDE2LjI4MCBsDQozMzIuNzYwIDQxNi4xNjAgbA0KMzMy
Ljg4MCA0MTYuMTYwIGwNCjMzMi44ODAgNDE2LjA0MCBsDQozMzMuMDAwIDQxNS45MjAgbA0KMzMz
LjI0MCA0MTUuOTIwIGwNCjMzMy4yNDAgNDE2LjA0MCBsDQozMzMuMTIwIDQxNi4xNjAgbA0KMzMz
LjEyMCA0MTYuMjgwIGwNCjMzMi44ODAgNDE2LjQwMCBsDQozMzIuNzYwIDQxNi40MDAgbA0KMzMy
LjUyMCA0MTYuNDAwIGwNCmYqDQoxLjAwMCAxLjAwMCAxLjAwMCBSRw0KMC4yNDAgdw0KWyBdIDAg
ZA0KMSBKDQoxIGoNCjAuMDAwIDAuMDAwIDAuMDAwIHJnDQozMzMuODQwIDQxNC42MDAgbQ0KMzMz
LjYwMCA0MTQuNjAwIGwNCjMzMy42MDAgNDE1LjkyMCBsDQozMzMuODQwIDQxNS45MjAgbA0KMzMz
Ljg0MCA0MTQuNjAwIGwNCmgNCjMzMy44NDAgNDE2LjE2MCBtDQozMzMuNjAwIDQxNi4xNjAgbA0K
MzMzLjYwMCA0MTYuNDAwIGwNCjMzMy44NDAgNDE2LjQwMCBsDQozMzMuODQwIDQxNi4xNjAgbA0K
ZioNCjAuMDAwIDAuMDAwIDAuMDAwIHJnDQowLjAwMCAwLjAwMCAwLjAwMCBSRw0KMC4xMjAgdw0K
WyBdIDAgZA0KMSBKDQoxIGoNCjMzNC4wODAgNDE0Ljk2MCBtDQozMzQuMDgwIDQxNC44NDAgbA0K
MzM0LjA4MCA0MTQuNzIwIGwNCjMzNC4yMDAgNDE0LjcyMCBsDQozMzQuMzIwIDQxNC42MDAgbA0K
MzM0LjQ0MCA0MTQuNjAwIGwNCjMzNC41NjAgNDE0LjYwMCBsDQozMzQuODAwIDQxNC42MDAgbA0K
MzM0LjkyMCA0MTQuNjAwIGwNCjMzNS4wNDAgNDE0LjcyMCBsDQozMzUuMTYwIDQxNC44NDAgbA0K
MzM1LjE2MCA0MTQuOTYwIGwNCjMzNS4xNjAgNDE1LjA4MCBsDQozMzUuMDQwIDQxNS4yMDAgbA0K
MzM0LjkyMCA0MTUuMzIwIGwNCjMzNC44MDAgNDE1LjMyMCBsDQozMzQuNjgwIDQxNS4zMjAgbA0K
MzM0LjU2MCA0MTUuNDQwIGwNCjMzNC40NDAgNDE1LjQ0MCBsDQozMzQuMzIwIDQxNS40NDAgbA0K
MzM0LjMyMCA0MTUuNTYwIGwNCjMzNC4zMjAgNDE1LjY4MCBsDQozMzQuNDQwIDQxNS44MDAgbA0K
MzM0LjU2MCA0MTUuODAwIGwNCjMzNC42ODAgNDE1LjgwMCBsDQozMzQuODAwIDQxNS42ODAgbA0K
MzM0LjkyMCA0MTUuNjgwIGwNCjMzNC45MjAgNDE1LjU2MCBsDQozMzUuMTYwIDQxNS41NjAgbA0K
MzM1LjA0MCA0MTUuNjgwIGwNCjMzNS4wNDAgNDE1LjgwMCBsDQozMzQuOTIwIDQxNS45MjAgbA0K
MzM0LjgwMCA0MTUuOTIwIGwNCjMzNC41NjAgNDE1LjkyMCBsDQozMzQuNDQwIDQxNS45MjAgbA0K
MzM0LjMyMCA0MTUuOTIwIGwNCjMzNC4yMDAgNDE1LjgwMCBsDQozMzQuMDgwIDQxNS42ODAgbA0K
MzM0LjA4MCA0MTUuNTYwIGwNCjMzNC4wODAgNDE1LjQ0MCBsDQozMzQuMjAwIDQxNS4zMjAgbA0K
MzM0LjMyMCA0MTUuMjAwIGwNCjMzNC40NDAgNDE1LjIwMCBsDQozMzQuNjgwIDQxNS4yMDAgbA0K
MzM0LjY4MCA0MTUuMDgwIGwNCjMzNC44MDAgNDE1LjA4MCBsDQozMzQuOTIwIDQxNS4wODAgbA0K
MzM0LjkyMCA0MTQuOTYwIGwNCjMzNC45MjAgNDE0Ljg0MCBsDQozMzQuODAwIDQxNC44NDAgbA0K
MzM0LjgwMCA0MTQuNzIwIGwNCjMzNC42ODAgNDE0LjcyMCBsDQozMzQuNTYwIDQxNC43MjAgbA0K
MzM0LjQ0MCA0MTQuNzIwIGwNCjMzNC4zMjAgNDE0Ljg0MCBsDQozMzQuMzIwIDQxNC45NjAgbA0K
MzM0LjA4MCA0MTQuOTYwIGwNCmYqDQowLjAwMCAwLjAwMCAwLjAwMCByZw0KMC4wMDAgMC4wMDAg
MC4wMDAgUkcNCjAuMTIwIHcNClsgXSAwIGQNCjEgSg0KMSBqDQozMzUuODgwIDQxNS45MjAgbQ0K
MzM1Ljc2MCA0MTUuOTIwIGwNCjMzNS42NDAgNDE1LjkyMCBsDQozMzUuNTIwIDQxNS44MDAgbA0K
MzM1LjQwMCA0MTUuNTYwIGwNCjMzNS4yODAgNDE1LjQ0MCBsDQozMzUuMjgwIDQxNS4yMDAgbA0K
MzM1LjI4MCA0MTUuMDgwIGwNCjMzNS40MDAgNDE0Ljg0MCBsDQozMzUuNTIwIDQxNC43MjAgbA0K
MzM1LjUyMCA0MTQuNjAwIGwNCjMzNS43NjAgNDE0LjYwMCBsDQozMzUuODgwIDQxNC42MDAgbA0K
MzM2LjAwMCA0MTQuNjAwIGwNCjMzNi4xMjAgNDE0LjYwMCBsDQozMzYuMjQwIDQxNC43MjAgbA0K
MzM2LjM2MCA0MTQuNzIwIGwNCjMzNi40ODAgNDE0Ljk2MCBsDQozMzYuNDgwIDQxNS4wODAgbA0K
MzM2LjI0MCA0MTUuMDgwIGwNCjMzNi4yNDAgNDE0Ljk2MCBsDQozMzYuMTIwIDQxNC44NDAgbA0K
MzM2LjAwMCA0MTQuNzIwIGwNCjMzNS44ODAgNDE0LjcyMCBsDQozMzUuNzYwIDQxNC43MjAgbA0K
MzM1LjY0MCA0MTQuODQwIGwNCjMzNS42NDAgNDE0Ljk2MCBsDQozMzUuNTIwIDQxNS4wODAgbA0K
MzM1LjUyMCA0MTUuMjAwIGwNCjMzNS41MjAgNDE1LjMyMCBsDQozMzUuNTIwIDQxNS40NDAgbA0K
MzM1LjY0MCA0MTUuNTYwIGwNCjMzNS42NDAgNDE1LjY4MCBsDQozMzUuNzYwIDQxNS42ODAgbA0K
MzM1Ljg4MCA0MTUuODAwIGwNCjMzNi4wMDAgNDE1LjgwMCBsDQozMzYuMTIwIDQxNS42ODAgbA0K
MzM2LjI0MCA0MTUuNTYwIGwNCjMzNi4yNDAgNDE1LjQ0MCBsDQozMzYuNDgwIDQxNS40NDAgbA0K
MzM2LjQ4MCA0MTUuNjgwIGwNCjMzNi4zNjAgNDE1LjgwMCBsDQozMzYuMjQwIDQxNS44MDAgbA0K
MzM2LjI0MCA0MTUuOTIwIGwNCjMzNi4wMDAgNDE1LjkyMCBsDQozMzUuODgwIDQxNS45MjAgbA0K
ZioNCjAuMDAwIDAuMDAwIDAuMDAwIFJHDQowLjEyMCB3DQpbIF0gMCBkDQoxIEoNCjEgag0KMC4w
MDAgMC4wMDAgMC4wMDAgcmcNCjMzNi43MjAgNDE1LjgwMCBtDQozMzYuODQwIDQxNS45MjAgbA0K
MzM3LjA4MCA0MTUuOTIwIGwNCjMzNy4yMDAgNDE1LjkyMCBsDQozMzcuNDQwIDQxNS45MjAgbA0K
MzM3LjU2MCA0MTUuOTIwIGwNCjMzNy42ODAgNDE1LjgwMCBsDQozMzcuODAwIDQxNS42ODAgbA0K
MzM3LjgwMCA0MTUuNDQwIGwNCjMzNy44MDAgNDE1LjMyMCBsDQozMzcuODAwIDQxNS4wODAgbA0K
MzM3LjgwMCA0MTQuOTYwIGwNCjMzNy42ODAgNDE0LjcyMCBsDQozMzcuNTYwIDQxNC42MDAgbA0K
MzM3LjQ0MCA0MTQuNjAwIGwNCjMzNy4yMDAgNDE0LjYwMCBsDQozMzYuOTYwIDQxNC42MDAgbA0K
MzM2Ljg0MCA0MTQuNjAwIGwNCjMzNi43MjAgNDE0LjcyMCBsDQozMzYuNjAwIDQxNC44NDAgbA0K
MzM2LjYwMCA0MTUuMDgwIGwNCjMzNi42MDAgNDE1LjIwMCBsDQozMzYuNjAwIDQxNS40NDAgbA0K
MzM2LjcyMCA0MTUuNTYwIGwNCjMzNi43MjAgNDE1LjgwMCBsDQpoDQozMzYuOTYwIDQxNC44NDAg
bQ0KMzM3LjA4MCA0MTQuNzIwIGwNCjMzNy4yMDAgNDE0LjcyMCBsDQozMzcuMzIwIDQxNC43MjAg
bA0KMzM3LjQ0MCA0MTQuODQwIGwNCjMzNy41NjAgNDE0Ljk2MCBsDQozMzcuNTYwIDQxNS4wODAg
bA0KMzM3LjU2MCA0MTUuMjAwIGwNCjMzNy41NjAgNDE1LjMyMCBsDQozMzcuNTYwIDQxNS40NDAg
bA0KMzM3LjU2MCA0MTUuNTYwIGwNCjMzNy40NDAgNDE1LjY4MCBsDQozMzcuMzIwIDQxNS44MDAg
bA0KMzM3LjIwMCA0MTUuODAwIGwNCjMzNy4wODAgNDE1LjgwMCBsDQozMzYuOTYwIDQxNS42ODAg
bA0KMzM2Ljk2MCA0MTUuNTYwIGwNCjMzNi44NDAgNDE1LjQ0MCBsDQozMzYuODQwIDQxNS4zMjAg
bA0KMzM2Ljg0MCA0MTUuMjAwIGwNCjMzNi44NDAgNDE1LjA4MCBsDQozMzYuODQwIDQxNC45NjAg
bA0KMzM2Ljk2MCA0MTQuODQwIGwNCmYqDQowLjAwMCAwLjAwMCAwLjAwMCByZw0KMC4wMDAgMC4w
MDAgMC4wMDAgUkcNCjAuMTIwIHcNClsgXSAwIGQNCjEgSg0KMSBqDQozMzguNzYwIDQxNi4yODAg
bQ0KMzM4Ljc2MCA0MTYuMTYwIGwNCjMzOS43MjAgNDE2LjE2MCBsDQozMzkuNjAwIDQxNS45MjAg
bA0KMzM5LjQ4MCA0MTUuODAwIGwNCjMzOS4zNjAgNDE1LjU2MCBsDQozMzkuMjQwIDQxNS4zMjAg
bA0KMzM5LjEyMCA0MTQuOTYwIGwNCjMzOS4wMDAgNDE0LjYwMCBsDQozMzkuMjQwIDQxNC42MDAg
bA0KMzM5LjI0MCA0MTQuNzIwIGwNCjMzOS4zNjAgNDE0Ljg0MCBsDQozMzkuMzYwIDQxNC45NjAg
bA0KMzM5LjM2MCA0MTUuMDgwIGwNCjMzOS40ODAgNDE1LjIwMCBsDQozMzkuNDgwIDQxNS40NDAg
bA0KMzM5LjYwMCA0MTUuNTYwIGwNCjMzOS43MjAgNDE1LjY4MCBsDQozMzkuNzIwIDQxNS44MDAg
bA0KMzM5Ljg0MCA0MTYuMDQwIGwNCjMzOS45NjAgNDE2LjA0MCBsDQozMzkuOTYwIDQxNi4xNjAg
bA0KMzM5Ljk2MCA0MTYuMjgwIGwNCjMzOC43NjAgNDE2LjI4MCBsDQpmKg0KMC4wMDAgMC4wMDAg
MC4wMDAgcmcNCjAuMDAwIDAuMDAwIDAuMDAwIFJHDQowLjEyMCB3DQpbIF0gMCBkDQoxIEoNCjEg
ag0KMzQwLjIwMCA0MTUuMDgwIG0NCjM0MC4yMDAgNDE0Ljg0MCBsDQozNDAuMjAwIDQxNC43MjAg
bA0KMzQwLjMyMCA0MTQuNzIwIGwNCjM0MC40NDAgNDE0LjYwMCBsDQozNDAuNTYwIDQxNC42MDAg
bA0KMzQwLjY4MCA0MTQuNjAwIGwNCjM0MC45MjAgNDE0LjYwMCBsDQozNDEuMDQwIDQxNC42MDAg
bA0KMzQxLjE2MCA0MTQuNzIwIGwNCjM0MS4yODAgNDE0Ljg0MCBsDQozNDEuNDAwIDQxNS4wODAg
bA0KMzQxLjQwMCA0MTUuMjAwIGwNCjM0MS40MDAgNDE1LjMyMCBsDQozNDEuMjgwIDQxNS40NDAg
bA0KMzQxLjE2MCA0MTUuNTYwIGwNCjM0MS4wNDAgNDE1LjY4MCBsDQozNDAuOTIwIDQxNS42ODAg
bA0KMzQwLjgwMCA0MTUuODAwIGwNCjM0MC42ODAgNDE1LjY4MCBsDQozNDAuNTYwIDQxNS42ODAg
bA0KMzQwLjQ0MCA0MTUuNjgwIGwNCjM0MC41NjAgNDE2LjE2MCBsDQozNDEuMjgwIDQxNi4xNjAg
bA0KMzQxLjI4MCA0MTYuMjgwIGwNCjM0MC4zMjAgNDE2LjI4MCBsDQozNDAuMjAwIDQxNS4zMjAg
bA0KMzQwLjQ0MCA0MTUuMzIwIGwNCjM0MC40NDAgNDE1LjQ0MCBsDQozNDAuNTYwIDQxNS40NDAg
bA0KMzQwLjU2MCA0MTUuNTYwIGwNCjM0MC42ODAgNDE1LjU2MCBsDQozNDAuODAwIDQxNS41NjAg
bA0KMzQwLjkyMCA0MTUuNDQwIGwNCjM0MS4wNDAgNDE1LjQ0MCBsDQozNDEuMDQwIDQxNS4zMjAg
bA0KMzQxLjE2MCA0MTUuMzIwIGwNCjM0MS4xNjAgNDE1LjIwMCBsDQozNDEuMTYwIDQxNS4wODAg
bA0KMzQxLjA0MCA0MTQuOTYwIGwNCjM0MS4wNDAgNDE0Ljg0MCBsDQozNDAuOTIwIDQxNC44NDAg
bA0KMzQwLjgwMCA0MTQuNzIwIGwNCjM0MC42ODAgNDE0LjcyMCBsDQozNDAuNTYwIDQxNC43MjAg
bA0KMzQwLjU2MCA0MTQuODQwIGwNCjM0MC40NDAgNDE0Ljg0MCBsDQozNDAuNDQwIDQxNC45NjAg
bA0KMzQwLjQ0MCA0MTUuMDgwIGwNCjM0MC4yMDAgNDE1LjA4MCBsDQpmKg0KMC4wMDAgMC4wMDAg
MC4wMDAgUkcNCjAuMTIwIHcNClsgXSAwIGQNCjEgSg0KMSBqDQowLjAwMCAwLjAwMCAwLjAwMCBy
Zw0KMzQxLjY0MCA0MTUuOTIwIG0NCjM0MS43NjAgNDE2LjE2MCBsDQozNDEuODgwIDQxNi4yODAg
bA0KMzQyLjEyMCA0MTYuNDAwIGwNCjM0Mi4zNjAgNDE2LjI4MCBsDQozNDIuNjAwIDQxNi4yODAg
bA0KMzQyLjcyMCA0MTYuMDQwIGwNCjM0Mi43MjAgNDE1LjkyMCBsDQozNDIuODQwIDQxNS42ODAg
bA0KMzQyLjg0MCA0MTUuNDQwIGwNCjM0Mi44NDAgNDE1LjIwMCBsDQozNDIuNzIwIDQxNS4wODAg
bA0KMzQyLjcyMCA0MTQuODQwIGwNCjM0Mi42MDAgNDE0LjcyMCBsDQozNDIuMzYwIDQxNC42MDAg
bA0KMzQyLjEyMCA0MTQuNjAwIGwNCjM0Mi4wMDAgNDE0LjYwMCBsDQozNDEuNzYwIDQxNC43MjAg
bA0KMzQxLjY0MCA0MTQuODQwIGwNCjM0MS42NDAgNDE0Ljk2MCBsDQozNDEuNjQwIDQxNS4yMDAg
bA0KMzQxLjUyMCA0MTUuNDQwIGwNCjM0MS41MjAgNDE1LjY4MCBsDQozNDEuNjQwIDQxNS44MDAg
bA0KMzQxLjY0MCA0MTUuOTIwIGwNCmgNCjM0MS44ODAgNDE0Ljk2MCBtDQozNDEuODgwIDQxNC44
NDAgbA0KMzQyLjAwMCA0MTQuNzIwIGwNCjM0Mi4xMjAgNDE0LjcyMCBsDQozNDIuMjQwIDQxNC43
MjAgbA0KMzQyLjM2MCA0MTQuODQwIGwNCjM0Mi40ODAgNDE0Ljk2MCBsDQozNDIuNDgwIDQxNS4w
ODAgbA0KMzQyLjYwMCA0MTUuMjAwIGwNCjM0Mi42MDAgNDE1LjQ0MCBsDQozNDIuNjAwIDQxNS42
ODAgbA0KMzQyLjQ4MCA0MTUuODAwIGwNCjM0Mi40ODAgNDE1LjkyMCBsDQozNDIuMzYwIDQxNi4w
NDAgbA0KMzQyLjM2MCA0MTYuMTYwIGwNCjM0Mi4yNDAgNDE2LjE2MCBsDQozNDIuMTIwIDQxNi4x
NjAgbA0KMzQyLjAwMCA0MTYuMDQwIGwNCjM0MS44ODAgNDE2LjA0MCBsDQozNDEuODgwIDQxNS44
MDAgbA0KMzQxLjc2MCA0MTUuNjgwIGwNCjM0MS43NjAgNDE1LjQ0MCBsDQozNDEuNzYwIDQxNS4z
MjAgbA0KMzQxLjg4MCA0MTUuMDgwIGwNCjM0MS44ODAgNDE0Ljk2MCBsDQpmKg0KMC4wMDAgMC4w
MDAgMC4wMDAgUkcNCjAuMTIwIHcNClsgXSAwIGQNCjEgSg0KMSBqDQowLjAwMCAwLjAwMCAwLjAw
MCByZw0KMzQzLjA4MCA0MTUuOTIwIG0NCjM0My4yMDAgNDE2LjE2MCBsDQozNDMuMzIwIDQxNi4y
ODAgbA0KMzQzLjU2MCA0MTYuNDAwIGwNCjM0My44MDAgNDE2LjI4MCBsDQozNDMuOTIwIDQxNi4y
ODAgbA0KMzQ0LjA0MCA0MTYuMDQwIGwNCjM0NC4xNjAgNDE1LjkyMCBsDQozNDQuMTYwIDQxNS42
ODAgbA0KMzQ0LjE2MCA0MTUuNDQwIGwNCjM0NC4xNjAgNDE1LjIwMCBsDQozNDQuMTYwIDQxNS4w
ODAgbA0KMzQ0LjE2MCA0MTQuODQwIGwNCjM0My45MjAgNDE0LjcyMCBsDQozNDMuODAwIDQxNC42
MDAgbA0KMzQzLjU2MCA0MTQuNjAwIGwNCjM0My40NDAgNDE0LjYwMCBsDQozNDMuMjAwIDQxNC43
MjAgbA0KMzQzLjA4MCA0MTQuODQwIGwNCjM0My4wODAgNDE0Ljk2MCBsDQozNDIuOTYwIDQxNS4y
MDAgbA0KMzQyLjk2MCA0MTUuNDQwIGwNCjM0Mi45NjAgNDE1LjY4MCBsDQozNDIuOTYwIDQxNS44
MDAgbA0KMzQzLjA4MCA0MTUuOTIwIGwNCmgNCjM0My4zMjAgNDE0Ljk2MCBtDQozNDMuMzIwIDQx
NC44NDAgbA0KMzQzLjQ0MCA0MTQuNzIwIGwNCjM0My41NjAgNDE0LjcyMCBsDQozNDMuNjgwIDQx
NC43MjAgbA0KMzQzLjgwMCA0MTQuODQwIGwNCjM0My45MjAgNDE0Ljk2MCBsDQozNDMuOTIwIDQx
NS4wODAgbA0KMzQzLjkyMCA0MTUuMjAwIGwNCjM0My45MjAgNDE1LjQ0MCBsDQozNDMuOTIwIDQx
NS42ODAgbA0KMzQzLjkyMCA0MTUuODAwIGwNCjM0My45MjAgNDE1LjkyMCBsDQozNDMuODAwIDQx
Ni4wNDAgbA0KMzQzLjY4MCA0MTYuMTYwIGwNCjM0My41NjAgNDE2LjE2MCBsDQozNDMuNDQwIDQx
Ni4xNjAgbA0KMzQzLjQ0MCA0MTYuMDQwIGwNCjM0My4zMjAgNDE2LjA0MCBsDQozNDMuMzIwIDQx
NS44MDAgbA0KMzQzLjIwMCA0MTUuNjgwIGwNCjM0My4yMDAgNDE1LjQ0MCBsDQozNDMuMjAwIDQx
NS4zMjAgbA0KMzQzLjIwMCA0MTUuMDgwIGwNCjM0My4zMjAgNDE0Ljk2MCBsDQpmKg0KMC4wMDAg
MC4wMDAgMC4wMDAgUkcNCjAuNzIwIHcNClsgXSAwIGQNCjEgSg0KMSBqDQozNDcuNTIwIDQxMi41
NjAgbQ0KMzAzLjYwMCA0MTIuNTYwIGwNClMNCjAuMDAwIDAuMDAwIDAuMDAwIFJHDQowLjI0MCB3
DQpbIF0gMCBkDQoxIEoNCjEgag0KMzQ3Ljc2MCA0MTcuNDgwIG0NCjMwNC4yMDAgNDE3LjQ4MCBs
DQpTDQowLjAwMCAwLjAwMCAwLjAwMCBSRw0KMC40ODAgdw0KWyBdIDAgZA0KMSBKDQoxIGoNCjM0
Ny4yODAgMzg0Ljk2MCBtDQozMDMuOTYwIDM4NC45NjAgbA0KUw0KMC4wMDAgMC4wMDAgMC4wMDAg
UkcNCjAuNDgwIHcNClsgXSAwIGQNCjEgSg0KMSBqDQozNDcuMjgwIDM4NC4xMjAgbQ0KMzAzLjk2
MCAzODQuMTIwIGwNClMNCjAuMDAwIDAuMDAwIDAuMDAwIFJHDQowLjQ4MCB3DQpbIF0gMCBkDQox
IEoNCjEgag0KMzQ3LjI4MCAzODIuOTIwIG0NCjMwMy45NjAgMzgyLjkyMCBsDQpTDQowLjAwMCAw
LjAwMCAwLjAwMCBSRw0KMC40ODAgdw0KWyBdIDAgZA0KMSBKDQoxIGoNCjM0Ny4yODAgMzgxLjcy
MCBtDQozMDMuOTYwIDM4MS43MjAgbA0KUw0KMC4wMDAgMC4wMDAgMC4wMDAgUkcNCjAuNDgwIHcN
ClsgXSAwIGQNCjEgSg0KMSBqDQozNDcuMjgwIDM4MC40MDAgbQ0KMzAzLjk2MCAzODAuNDAwIGwN
ClMNCjAuMDAwIDAuMDAwIDAuMDAwIFJHDQowLjQ4MCB3DQpbIF0gMCBkDQoxIEoNCjEgag0KMzQ3
LjI4MCAzNzkuMjAwIG0NCjMwMy45NjAgMzc5LjIwMCBsDQpTDQowLjAwMCAwLjAwMCAwLjAwMCBS
Rw0KMC40ODAgdw0KWyBdIDAgZA0KMSBKDQoxIGoNCjM0Ny4yODAgMzc4LjAwMCBtDQozMDMuOTYw
IDM3OC4wMDAgbA0KUw0KMC4wMDAgMC4wMDAgMC4wMDAgUkcNCjAuNDgwIHcNClsgXSAwIGQNCjEg
Sg0KMSBqDQozNDcuMjgwIDM3Ni44MDAgbQ0KMzAzLjk2MCAzNzYuODAwIGwNClMNCjAuMDAwIDAu
MDAwIDAuMDAwIFJHDQowLjQ4MCB3DQpbIF0gMCBkDQoxIEoNCjEgag0KMzQ3LjI4MCAzNzUuNDgw
IG0NCjMwMy45NjAgMzc1LjQ4MCBsDQpTDQowLjAwMCAwLjAwMCAwLjAwMCBSRw0KMC40ODAgdw0K
WyBdIDAgZA0KMSBKDQoxIGoNCjM0Ny4yODAgMzc0LjI4MCBtDQozMDMuOTYwIDM3NC4yODAgbA0K
Uw0KMC4wMDAgMC4wMDAgMC4wMDAgUkcNCjAuNDgwIHcNClsgXSAwIGQNCjEgSg0KMSBqDQozNDcu
MjgwIDM3My4wODAgbQ0KMzAzLjk2MCAzNzMuMDgwIGwNClMNCjAuMDAwIDAuMDAwIDAuMDAwIFJH
DQowLjQ4MCB3DQpbIF0gMCBkDQoxIEoNCjEgag0KMzQ3LjI4MCAzNzEuODgwIG0NCjMwMy45NjAg
MzcxLjg4MCBsDQpTDQowLjAwMCAwLjAwMCAwLjAwMCBSRw0KMC40ODAgdw0KWyBdIDAgZA0KMSBK
DQoxIGoNCjM0Ny4yODAgMzcwLjY4MCBtDQozMDMuOTYwIDM3MC42ODAgbA0KUw0KMC4wMDAgMC4w
MDAgMC4wMDAgUkcNCjAuNDgwIHcNClsgXSAwIGQNCjEgSg0KMSBqDQozNDcuMjgwIDM2OS4zNjAg
bQ0KMzAzLjk2MCAzNjkuMzYwIGwNClMNCjAuMDAwIDAuMDAwIDAuMDAwIFJHDQowLjQ4MCB3DQpb
IF0gMCBkDQoxIEoNCjEgag0KMzQ3LjI4MCAzNjYuOTYwIG0NCjMwMy45NjAgMzY2Ljk2MCBsDQpT
DQowLjAwMCAwLjAwMCAwLjAwMCBSRw0KMC40ODAgdw0KWyBdIDAgZA0KMSBKDQoxIGoNCjM0Ny4y
ODAgMzY1Ljc2MCBtDQozMDMuOTYwIDM2NS43NjAgbA0KUw0KMC4wMDAgMC4wMDAgMC4wMDAgUkcN
CjAuNDgwIHcNClsgXSAwIGQNCjEgSg0KMSBqDQozNDcuMjgwIDM2NC40NDAgbQ0KMzAzLjk2MCAz
NjQuNDQwIGwNClMNCjAuMDAwIDAuMDAwIDAuMDAwIFJHDQowLjQ4MCB3DQpbIF0gMCBkDQoxIEoN
CjEgag0KMzQ3LjI4MCAzNjMuMjQwIG0NCjMwMy45NjAgMzYzLjI0MCBsDQpTDQowLjAwMCAwLjAw
MCAwLjAwMCBSRw0KMC40ODAgdw0KWyBdIDAgZA0KMSBKDQoxIGoNCjM0Ny4yODAgMzYyLjA0MCBt
DQozMDMuOTYwIDM2Mi4wNDAgbA0KUw0KMC4wMDAgMC4wMDAgMC4wMDAgUkcNCjAuNDgwIHcNClsg
XSAwIGQNCjEgSg0KMSBqDQozNDcuMjgwIDM2MC44NDAgbQ0KMzAzLjk2MCAzNjAuODQwIGwNClMN
CjAuMDAwIDAuMDAwIDAuMDAwIFJHDQowLjQ4MCB3DQpbIF0gMCBkDQoxIEoNCjEgag0KMzQ3LjI4
MCAzNTkuNjQwIG0NCjMwMy45NjAgMzU5LjY0MCBsDQpTDQowLjAwMCAwLjAwMCAwLjAwMCBSRw0K
MC40ODAgdw0KWyBdIDAgZA0KMSBKDQoxIGoNCjM0Ny4yODAgMzU4LjMyMCBtDQozMDMuOTYwIDM1
OC4zMjAgbA0KUw0KMC4wMDAgMC4wMDAgMC4wMDAgUkcNCjAuNDgwIHcNClsgXSAwIGQNCjEgSg0K
MSBqDQozNDcuMjgwIDM1Ny4xMjAgbQ0KMzAzLjk2MCAzNTcuMTIwIGwNClMNCjAuMDAwIDAuMDAw
IDAuMDAwIFJHDQowLjQ4MCB3DQpbIF0gMCBkDQoxIEoNCjEgag0KMzQ3LjI4MCAzNTUuOTIwIG0N
CjMwMy45NjAgMzU1LjkyMCBsDQpTDQowLjAwMCAwLjAwMCAwLjAwMCBSRw0KMC40ODAgdw0KWyBd
IDAgZA0KMSBKDQoxIGoNCjM0Ny4yODAgMzU0LjcyMCBtDQozMDMuOTYwIDM1NC43MjAgbA0KUw0K
MC4wMDAgMC4wMDAgMC4wMDAgUkcNCjAuNDgwIHcNClsgXSAwIGQNCjEgSg0KMSBqDQozNDcuMjgw
IDM1My40MDAgbQ0KMzAzLjk2MCAzNTMuNDAwIGwNClMNCjAuMDAwIDAuMDAwIDAuMDAwIFJHDQow
LjQ4MCB3DQpbIF0gMCBkDQoxIEoNCjEgag0KMzQ3LjI4MCAzNTIuMjAwIG0NCjMwMy45NjAgMzUy
LjIwMCBsDQpTDQowLjAwMCAwLjAwMCAwLjAwMCBSRw0KMC40ODAgdw0KWyBdIDAgZA0KMSBKDQox
IGoNCjM0Ny4yODAgMzUxLjEyMCBtDQozMDMuOTYwIDM1MS4xMjAgbA0KUw0KMC4wMDAgMC4wMDAg
MC4wMDAgUkcNCjAuNDgwIHcNClsgXSAwIGQNCjEgSg0KMSBqDQozNDcuMjgwIDM2OC4xNjAgbQ0K
MzAzLjk2MCAzNjguMTYwIGwNClMNCjAuMDAwIDAuMDAwIDAuMDAwIFJHDQowLjQ4MCB3DQpbIF0g
MCBkDQoxIEoNCjEgag0KMzA4LjA0MCAzODUuMDgwIG0NCjMwOC4wNDAgNDEyLjY4MCBsDQpTDQow
LjAwMCAwLjAwMCAwLjAwMCBSRw0KMC40ODAgdw0KWyBdIDAgZA0KMSBKDQoxIGoNCjMxMi43MjAg
Mzg1LjA4MCBtDQozMTIuNzIwIDQxMi42ODAgbA0KUw0KMC4wMDAgMC4wMDAgMC4wMDAgUkcNCjAu
NDgwIHcNClsgXSAwIGQNCjEgSg0KMSBqDQozMTcuMTYwIDM4NS4wODAgbQ0KMzE3LjE2MCA0MTIu
NjgwIGwNClMNCjAuMDAwIDAuMDAwIDAuMDAwIFJHDQowLjQ4MCB3DQpbIF0gMCBkDQoxIEoNCjEg
ag0KMzIxLjYwMCAzODUuMDgwIG0NCjMyMS42MDAgNDEyLjQ0MCBsDQpTDQowLjAwMCAwLjAwMCAw
LjAwMCBSRw0KMC40ODAgdw0KWyBdIDAgZA0KMSBKDQoxIGoNCjMyNi4wNDAgMzg1LjA4MCBtDQoz
MjYuMDQwIDQxMi40NDAgbA0KUw0KMC4wMDAgMC4wMDAgMC4wMDAgUkcNCjAuNDgwIHcNClsgXSAw
IGQNCjEgSg0KMSBqDQozMzAuNDgwIDM4NS4wODAgbQ0KMzMwLjQ4MCA0MTIuNDQwIGwNClMNCjAu
MDAwIDAuMDAwIDAuMDAwIFJHDQowLjQ4MCB3DQpbIF0gMCBkDQoxIEoNCjEgag0KMzM0LjkyMCAz
ODUuMDgwIG0NCjMzNC45MjAgNDEyLjQ0MCBsDQpTDQowLjAwMCAwLjAwMCAwLjAwMCBSRw0KMC40
ODAgdw0KWyBdIDAgZA0KMSBKDQoxIGoNCjMzOS40ODAgMzg1LjA4MCBtDQozMzkuNDgwIDQxMi40
NDAgbA0KUw0KMC4wMDAgMC4wMDAgMC4wMDAgUkcNCjAuNDgwIHcNClsgXSAwIGQNCjEgSg0KMSBq
DQozNDMuNjgwIDM4NS4wODAgbQ0KMzQzLjY4MCA0MTIuNDQwIGwNClMNCjAuMDAwIDAuMDAwIDAu
MDAwIFJHDQowLjM2MCB3DQpbIF0gMCBkDQoxIEoNCjEgag0KMzEwLjU2MCA0MDYuNDQwIG0NCjMw
OC4xNjAgNDA2LjQ0MCBsDQozMDguMTYwIDQxMi40NDAgbA0KMzEwLjU2MCA0MTIuNDQwIGwNCjMx
MC41NjAgNDA2LjQ0MCBsDQpTDQowLjAwMCAwLjAwMCAwLjAwMCBSRw0KMC4zNjAgdw0KWyBdIDAg
ZA0KMSBKDQoxIGoNCjMxMS4xNjAgNDEyLjQ0MCBtDQozMTAuNTYwIDQwNi40NDAgbA0KUw0KMC4w
MDAgMC4wMDAgMC4wMDAgUkcNCjAuMzYwIHcNClsgXSAwIGQNCjEgSg0KMSBqDQozMTUuMTIwIDQw
Ni40NDAgbQ0KMzEyLjcyMCA0MDYuNDQwIGwNCjMxMi43MjAgNDEyLjQ0MCBsDQozMTUuMTIwIDQx
Mi40NDAgbA0KMzE1LjEyMCA0MDYuNDQwIGwNClMNCjAuMDAwIDAuMDAwIDAuMDAwIFJHDQowLjM2
MCB3DQpbIF0gMCBkDQoxIEoNCjEgag0KMzE1LjYwMCA0MTIuNDQwIG0NCjMxNS4xMjAgNDA2LjQ0
MCBsDQpTDQowLjAwMCAwLjAwMCAwLjAwMCBSRw0KMC4zNjAgdw0KWyBdIDAgZA0KMSBKDQoxIGoN
CjMxOS41NjAgNDA2LjQ0MCBtDQozMTcuMTYwIDQwNi40NDAgbA0KMzE3LjE2MCA0MTIuNDQwIGwN
CjMxOS41NjAgNDEyLjQ0MCBsDQozMTkuNTYwIDQwNi40NDAgbA0KUw0KMC4wMDAgMC4wMDAgMC4w
MDAgUkcNCjAuMzYwIHcNClsgXSAwIGQNCjEgSg0KMSBqDQozMjAuMTYwIDQxMi40NDAgbQ0KMzE5
LjU2MCA0MDYuNDQwIGwNClMNCjAuMDAwIDAuMDAwIDAuMDAwIFJHDQowLjM2MCB3DQpbIF0gMCBk
DQoxIEoNCjEgag0KMzEyLjI0MCA0MTAuMjgwIG0NCjMxMS4yODAgNDEwLjI4MCBsDQpTDQowLjAw
MCAwLjAwMCAwLjAwMCBSRw0KMC4zNjAgdw0KWyBdIDAgZA0KMSBKDQoxIGoNCjMxNi42ODAgNDEw
LjI4MCBtDQozMTUuODQwIDQxMC4yODAgbA0KUw0KMC4wMDAgMC4wMDAgMC4wMDAgUkcNCjAuMzYw
IHcNClsgXSAwIGQNCjEgSg0KMSBqDQozMTIuMjQwIDQxMS4xMjAgbQ0KMzExLjI4MCA0MTEuMTIw
IGwNClMNCjAuMDAwIDAuMDAwIDAuMDAwIFJHDQowLjM2MCB3DQpbIF0gMCBkDQoxIEoNCjEgag0K
MzE2LjgwMCA0MTEuMTIwIG0NCjMxNS44NDAgNDExLjEyMCBsDQpTDQowLjAwMCAwLjAwMCAwLjAw
MCBSRw0KMC4zNjAgdw0KWyBdIDAgZA0KMSBKDQoxIGoNCjMyMS4yNDAgNDExLjEyMCBtDQozMjAu
MjgwIDQxMS4xMjAgbA0KUw0KMC4wMDAgMC4wMDAgMC4wMDAgcmcNCjAuMDAwIDAuMDAwIDAuMDAw
IFJHDQowLjM2MCB3DQpbIF0gMCBkDQoxIEoNCjEgag0KMzAyLjUyMCAzNDguODQwIDQ2LjkyMCA3
Ni45MjAgcmUNCm4NCjAuMDAwIDAuMDAwIDAuMDAwIFJHDQowLjcyMCB3DQpbIF0gMCBkDQoxIEoN
CjEgag0KMC4wMDAgMC4wMDAgMC4wMDAgcmcNCjMwMi40NzEgNDA2LjQ0MCBtDQoxOTIuMTQ0IDQw
Ni40MDIgMTAyLjgwOCAzNzYuNzIzIDEwMi43MjAgMzQwLjA4MCBjDQpTDQoxLjAwMCAxLjAwMCAx
LjAwMCByZw0KMC4wMDAgMC4wMDAgMC4wMDAgUkcNCjAuNzIwIHcNClsgXSAwIGQNCjEgSg0KMSBq
DQoyNi40MDAgMjYyLjgwMCAxNTIuNjQwIDE4LjAwMCByZQ0KYioNCjAuMDAwIDAuMDAwIDAuMDAw
IFJHDQowLjcyMCB3DQpbIF0gMCBkDQoxIEoNCjEgag0KMTI4LjY0MCAyODEuNTIwIG0NCjEyOC42
NDAgMjYzLjUyMCBsDQpTDQowLjAwMCAwLjAwMCAwLjAwMCBSRw0KMC43MjAgdw0KWyBdIDAgZA0K
MSBKDQoxIGoNCjQ5LjQ0MCAyODAuODAwIG0NCjQ5LjQ0MCAyNjIuODAwIGwNClMNCjAuMDAwIDAu
MDAwIDAuMDAwIFJHDQowLjcyMCB3DQpbIF0gMCBkDQoxIEoNCjEgag0KNzYuODAwIDI4MC44MDAg
bQ0KNzYuODAwIDI2Mi44MDAgbA0KUw0KMC4wMDAgMC4wMDAgMC4wMDAgUkcNCjAuNzIwIHcNClsg
XSAwIGQNCjEgSg0KMSBqDQoxNTUuMjgwIDI4MC44MDAgbQ0KMTU1LjI4MCAyNjIuODAwIGwNClMN
CjAuMDAwIDAuMDAwIDAuMDAwIFJHDQowLjcyMCB3DQpbIF0gMCBkDQoxIEoNCjEgag0KMTAyLjAw
MCAyODEuNTIwIG0NCjEwMi4wMDAgMjYzLjUyMCBsDQpTDQowLjAwMCAwLjAwMCAwLjAwMCByZw0K
MC4wMDAgMC4wMDAgMC4wMDAgUkcNCjAuNzIwIHcNClsgXSAwIGQNCjEgSg0KMSBqDQoyNy4xMjAg
MjY0Ljg0MCAxOC44NDAgMTAuOTIwIHJlDQpuDQpCVA0KMS4wMDAgMC4wMDAgMC4wMDAgMS4wMDAg
MjcuMTIwIDI2Ny4xMjAgVG0NCi9GNSA5LjkwNCBUZg0KMCBUcg0KMC4wMDAgMC4wMDAgMC4wMDAg
cmcNCjAuMDAwIFRjDQoxMDMuMzMzIFR6DQooVk0xKVRqDQpFVA0KMC4wMDAgMC4wMDAgMC4wMDAg
cmcNCjAuMDAwIDAuMDAwIDAuMDAwIFJHDQowLjcyMCB3DQpbIF0gMCBkDQoxIEoNCjEgag0KNTMu
NzYwIDI2NC44NDAgMzMuMjQwIDEwLjkyMCByZQ0Kbg0KQlQNCjEuMDAwIDAuMDAwIDAuMDAwIDEu
MDAwIDUzLjc2MCAyNjcuMTIwIFRtDQovRjUgOS45MDQgVGYNCjAgVHINCjAuMDAwIDAuMDAwIDAu
MDAwIHJnDQowLjAwMCBUYw0KMTAzLjMzMyBUeg0KKFZNMilUag0KRVQNCjAuMDAwIDAuMDAwIDAu
MDAwIHJnDQowLjAwMCAwLjAwMCAwLjAwMCBSRw0KMC43MjAgdw0KWyBdIDAgZA0KMSBKDQoxIGoN
CjgwLjQwMCAyNjQuODQwIDMzLjI0MCAxMC45MjAgcmUNCm4NCkJUDQoxLjAwMCAwLjAwMCAwLjAw
MCAxLjAwMCA4MC40MDAgMjY3LjEyMCBUbQ0KL0Y1IDkuOTA0IFRmDQowIFRyDQowLjAwMCAwLjAw
MCAwLjAwMCByZw0KMC4wMDAgVGMNCjEwMy4zMzMgVHoNCihWTTMpVGoNCkVUDQowLjAwMCAwLjAw
MCAwLjAwMCByZw0KMC4wMDAgMC4wMDAgMC4wMDAgUkcNCjAuNzIwIHcNClsgXSAwIGQNCjEgSg0K
MSBqDQoxMDQuODgwIDI2NC44NDAgMzMuMjQwIDEwLjkyMCByZQ0Kbg0KQlQNCjEuMDAwIDAuMDAw
IDAuMDAwIDEuMDAwIDEwNC44ODAgMjY3LjEyMCBUbQ0KL0Y1IDkuOTA0IFRmDQowIFRyDQowLjAw
MCAwLjAwMCAwLjAwMCByZw0KMC4wMDAgVGMNCjEwMy4zMzMgVHoNCihWTTQpVGoNCkVUDQowLjAw
MCAwLjAwMCAwLjAwMCByZw0KMC4wMDAgMC4wMDAgMC4wMDAgUkcNCjAuNzIwIHcNClsgXSAwIGQN
CjEgSg0KMSBqDQoxNTguMTYwIDI2NC44NDAgMzMuMjQwIDEwLjkyMCByZQ0Kbg0KQlQNCjEuMDAw
IDAuMDAwIDAuMDAwIDEuMDAwIDE1OC4xNjAgMjY3LjEyMCBUbQ0KL0Y1IDkuOTA0IFRmDQowIFRy
DQowLjAwMCAwLjAwMCAwLjAwMCByZw0KMC4wMDAgVGMNCjEwMy4zMzMgVHoNCihWTTYpVGoNCkVU
DQowLjAwMCAwLjAwMCAwLjAwMCByZw0KMC4wMDAgMC4wMDAgMC4wMDAgUkcNCjAuNzIwIHcNClsg
XSAwIGQNCjEgSg0KMSBqDQoxMzEuNTIwIDI2NC44NDAgMzMuMjQwIDEwLjkyMCByZQ0Kbg0KQlQN
CjEuMDAwIDAuMDAwIDAuMDAwIDEuMDAwIDEzMS41MjAgMjY3LjEyMCBUbQ0KL0Y1IDkuOTA0IFRm
DQowIFRyDQowLjAwMCAwLjAwMCAwLjAwMCByZw0KMC4wMDAgVGMNCjEwMy4zMzMgVHoNCihWTTUp
VGoNCkVUDQowLjAwMCAwLjAwMCAwLjAwMCByZw0KMC4wMDAgMC4wMDAgMC4wMDAgUkcNCjAuNzIw
IHcNClsgXSAwIGQNCjEgSg0KMSBqDQo4NC4xMjAgMzI5LjY0MCAyOC42ODAgMjEuNzIwIHJlDQpu
DQpCVA0KMS4wMDAgMC4wMDAgMC4wMDAgMS4wMDAgODQuMTIwIDM0Mi43MjAgVG0NCi9GNSA5Ljkw
NCBUZg0KMCBUcg0KMC4wMDAgMC4wMDAgMC4wMDAgcmcNCjAuMDAwIFRjDQo5NS41NTEgVHoNCihl
dGgwKVRqDQpFVA0KMC4wMDAgMC4wMDAgMC4wMDAgcmcNCjAuMDAwIDAuMDAwIDAuMDAwIFJHDQow
LjcyMCB3DQpbIF0gMCBkDQoxIEoNCjEgag0KMjc5LjEyMCAzOTUuMTYwIDM5LjAwMCAxMC45MjAg
cmUNCm4NCkJUDQoxLjAwMCAwLjAwMCAwLjAwMCAxLjAwMCAyNzkuMTIwIDM5Ny40NDAgVG0NCi9G
NSA5LjkwNCBUZg0KMCBUcg0KMC4wMDAgMC4wMDAgMC4wMDAgcmcNCjAuMDAwIFRjDQo4NS4xNDgg
VHoNCihHRSA3LzMpVGoNCkVUDQowLjAwMCAwLjAwMCAwLjAwMCByZw0KMC4wMDAgMC4wMDAgMC4w
MDAgUkcNCjAuNzIwIHcNClsgXSAwIGQNCjEgSg0KMSBqDQozMDcuMjAwIDMzNy41NjAgNTMuMTYw
IDEwLjkyMCByZQ0Kbg0KQlQNCjEuMDAwIDAuMDAwIDAuMDAwIDEuMDAwIDMwNy4yMDAgMzM5Ljg0
MCBUbQ0KL0Y1IDkuOTA0IFRmDQowIFRyDQowLjAwMCAwLjAwMCAwLjAwMCByZw0KMC4wMDAgVGMN
CjkxLjUzMCBUeg0KKENpc2NvKVRqDQpFVA0KQlQNCjEuMDAwIDAuMDAwIDAuMDAwIDEuMDAwIDMy
OC44MDAgMzM5Ljg0MCBUbQ0KL0Y1IDkuOTA0IFRmDQowIFRyDQowLjAwMCAwLjAwMCAwLjAwMCBy
Zw0KMC4wMDAgVGMNCjg0LjQ4OSBUeg0KKCA3NjA5KVRqDQpFVA0KMC4wMDAgMC4wMDAgMC4wMDAg
cmcNCjAuMDAwIDAuMDAwIDAuMDAwIFJHDQowLjcyMCB3DQpbIF0gMCBkDQoxIEoNCjEgag0KMy42
MDAgMzA0LjIwMCBtDQo2Ni4wMDAgMzY2LjYwMCBsDQo3My42ODAgMzU4LjkyMCBsDQoxMS4yODAg
Mjk2LjUyMCBsDQozLjYwMCAzMDQuMjAwIGwNCm4NCkJUDQowLjcwNyAwLjcwNyAtMC43MDcgMC43
MDcgOS43MjAgMjk4LjA4MCBUbQ0KL0Y1IDkuOTA0IFRmDQowIFRyDQowLjAwMCAwLjAwMCAwLjAw
MCByZw0KMC4wMDAgVGMNCjk2LjM5NiBUeg0KKFBvd2VyVmF1bHQpVGoNCkVUDQpCVA0KMC43MDcg
MC43MDcgLTAuNzA3IDAuNzA3IDQyLjI0MCAzMzAuNjAwIFRtDQovRjUgOS45MDQgVGYNCjAgVHIN
CjAuMDAwIDAuMDAwIDAuMDAwIHJnDQowLjAwMCBUYw0KOTEuMDU4IFR6DQooTlgzMDAwKVRqDQpF
VA0KMC4wMDAgMC4wMDAgMC4wMDAgcmcNCjAuMDAwIDAuMDAwIDAuMDAwIFJHDQowLjcyMCB3DQpb
IF0gMCBkDQoxIEoNCjEgag0KMzUuMDQwIDMuNDgwIDM1OS40MDAgMjI2LjkyMCByZQ0Kbg0KQlQN
CjEuMDAwIDAuMDAwIDAuMDAwIDEuMDAwIDM1LjA0MCAyMjEuNzYwIFRtDQovRjcgOS45MDQgVGYN
CjAgVHINCjAuMDAwIDAuMDAwIDAuMDAwIHJnDQowLjAwMCBUYw0KOTUuMDI5IFR6DQooS2V5KVRq
DQpFVA0KQlQNCjEuMDAwIDAuMDAwIDAuMDAwIDEuMDAwIDUwLjE2MCAyMjEuNzYwIFRtDQovRjUg
OS45MDQgVGYNCjAgVHINCjAuMDAwIDAuMDAwIDAuMDAwIHJnDQowLjAwMCBUYw0KNzYuOTIzIFR6
DQooOilUag0KRVQNCkJUDQoxLjAwMCAwLjAwMCAwLjAwMCAxLjAwMCAzNS4wNDAgMjAwLjE2MCBU
bQ0KL0Y1IDkuOTA0IFRmDQowIFRyDQowLjAwMCAwLjAwMCAwLjAwMCByZw0KMC4wMDAgVGMNCjk2
LjM5NiBUeg0KKFBvd2VyVmF1bHQpVGoNCkVUDQpCVA0KMS4wMDAgMC4wMDAgMC4wMDAgMS4wMDAg
ODEuMTIwIDIwMC4xNjAgVG0NCi9GNSA5LjkwNCBUZg0KMCBUcg0KMC4wMDAgMC4wMDAgMC4wMDAg
cmcNCjAuMDAwIFRjDQo5MS4wNTggVHoNCihOWDMwMDApVGoNCkVUDQpCVA0KMS4wMDAgMC4wMDAg
MC4wMDAgMS4wMDAgMTExLjM2MCAyMDAuMTYwIFRtDQovRjUgOS45MDQgVGYNCjAgVHINCjAuMDAw
IDAuMDAwIDAuMDAwIHJnDQowLjAwMCBUYw0KOTIuODEzIFR6DQooID0gRGVsbCBzZXJ2ZXIsIGlu
c3RhbGxlZCBCYXNlIE9TKVRqDQpFVA0KQlQNCjEuMDAwIDAuMDAwIDAuMDAwIDEuMDAwIDIzNS4y
MDAgMjAwLjE2MCBUbQ0KL0Y1IDkuOTA0IFRmDQowIFRyDQowLjAwMCAwLjAwMCAwLjAwMCByZw0K
MC4wMDAgVGMNCjk4LjUxMSBUeg0KKFVidW50dSlUag0KRVQNCkJUDQoxLjAwMCAwLjAwMCAwLjAw
MCAxLjAwMCAyNjQuNzIwIDIwMC4xNjAgVG0NCi9GNSA5LjkwNCBUZg0KMCBUcg0KMC4wMDAgMC4w
MDAgMC4wMDAgcmcNCjAuMDAwIFRjDQo4My4yODQgVHoNCiggMTIuMDQpVGoNCkVUDQpCVA0KMS4w
MDAgMC4wMDAgMC4wMDAgMS4wMDAgMjg4LjQ4MCAyMDAuMTYwIFRtDQovRjUgOS45MDQgVGYNCjAg
VHINCjAuMDAwIDAuMDAwIDAuMDAwIHJnDQowLjAwMCBUYw0KOTEuODQ3IFR6DQooTFRTKVRqDQpF
VA0KQlQNCjEuMDAwIDAuMDAwIDAuMDAwIDEuMDAwIDMwNC4zMjAgMjAwLjE2MCBUbQ0KL0Y1IDku
OTA0IFRmDQowIFRyDQowLjAwMCAwLjAwMCAwLjAwMCByZw0KMC4wMDAgVGMNCjkyLjQxMyBUeg0K
KCBzZXJ2ZXIgd2l0aClUag0KRVQNCkJUDQoxLjAwMCAwLjAwMCAwLjAwMCAxLjAwMCAzNTEuMTIw
IDIwMC4xNjAgVG0NCi9GNSA5LjkwNCBUZg0KMCBUcg0KMC4wMDAgMC4wMDAgMC4wMDAgcmcNCjAu
MDAwIFRjDQo4NC45MzQgVHoNCihYRU4pVGoNCkVUDQpCVA0KMS4wMDAgMC4wMDAgMC4wMDAgMS4w
MDAgMzY5LjEyMCAyMDAuMTYwIFRtDQovRjUgOS45MDQgVGYNCjAgVHINCjAuMDAwIDAuMDAwIDAu
MDAwIHJnDQowLjAwMCBUYw0KNzcuNTkwIFR6DQooIDQuMClUag0KRVQNCkJUDQoxLjAwMCAwLjAw
MCAwLjAwMCAxLjAwMCAzNS4wNDAgMTc4LjU2MCBUbQ0KL0Y1IDkuOTA0IFRmDQowIFRyDQowLjAw
MCAwLjAwMCAwLjAwMCByZw0KMC4wMDAgVGMNCjkxLjUzMCBUeg0KKENpc2NvKVRqDQpFVA0KQlQN
CjEuMDAwIDAuMDAwIDAuMDAwIDEuMDAwIDU2LjY0MCAxNzguNTYwIFRtDQovRjUgOS45MDQgVGYN
CjAgVHINCjAuMDAwIDAuMDAwIDAuMDAwIHJnDQowLjAwMCBUYw0KODIuOTkyIFR6DQooIDc2MDkg
PSlUag0KRVQNCkJUDQoxLjAwMCAwLjAwMCAwLjAwMCAxLjAwMCA4NS40NDAgMTc4LjU2MCBUbQ0K
L0Y1IDkuOTA0IFRmDQowIFRyDQowLjAwMCAwLjAwMCAwLjAwMCByZw0KMC4wMDAgVGMNCjkxLjUz
MCBUeg0KKENpc2NvKVRqDQpFVA0KQlQNCjEuMDAwIDAuMDAwIDAuMDAwIDEuMDAwIDEwNy4wNDAg
MTc4LjU2MCBUbQ0KL0Y1IDkuOTA0IFRmDQowIFRyDQowLjAwMCAwLjAwMCAwLjAwMCByZw0KMC4w
MDAgVGMNCjk2LjE4NiBUeg0KKCBSb3V0ZXIgNzYwMCBzZXJpZXMsIHN3aXRjaCBwb3J0cyB3aXRo
IDkgc2xvdHMuKVRqDQpFVA0KQlQNCjEuMDAwIDAuMDAwIDAuMDAwIDEuMDAwIDM1LjA0MCAxNTYu
OTYwIFRtDQovRjUgOS45MDQgVGYNCjAgVHINCjAuMDAwIDAuMDAwIDAuMDAwIHJnDQowLjAwMCBU
Yw0KMTAzLjMzMyBUeg0KKFZNMSlUag0KRVQNCkJUDQoxLjAwMCAwLjAwMCAwLjAwMCAxLjAwMCA1
My43NjAgMTU2Ljk2MCBUbQ0KL0Y1IDkuOTA0IFRmDQowIFRyDQowLjAwMCAwLjAwMCAwLjAwMCBy
Zw0KMC4wMDAgVGMNCjc0Ljc3OSBUeg0KKCAtKVRqDQpFVA0KQlQNCjEuMDAwIDAuMDAwIDAuMDAw
IDEuMDAwIDYwLjk2MCAxNTYuOTYwIFRtDQovRjUgOS45MDQgVGYNCjAgVHINCjAuMDAwIDAuMDAw
IDAuMDAwIHJnDQowLjAwMCBUYw0KMTAzLjMzMyBUeg0KKFZNNilUag0KRVQNCkJUDQoxLjAwMCAw
LjAwMCAwLjAwMCAxLjAwMCA3OS42ODAgMTU2Ljk2MCBUbQ0KL0Y1IDkuOTA0IFRmDQowIFRyDQow
LjAwMCAwLjAwMCAwLjAwMCByZw0KMC4wMDAgVGMNCjkzLjMxNCBUeg0KKCA9IFZpcnR1YWwgTWFj
aGluZXMsIGluc3RhbGxlZClUag0KRVQNCkJUDQoxLjAwMCAwLjAwMCAwLjAwMCAxLjAwMCAxOTMu
NDQwIDE1Ni45NjAgVG0NCi9GNSA5LjkwNCBUZg0KMCBUcg0KMC4wMDAgMC4wMDAgMC4wMDAgcmcN
CjAuMDAwIFRjDQo5OC41MTEgVHoNCihVYnVudHUpVGoNCkVUDQpCVA0KMS4wMDAgMC4wMDAgMC4w
MDAgMS4wMDAgMjIyLjk2MCAxNTYuOTYwIFRtDQovRjUgOS45MDQgVGYNCjAgVHINCjAuMDAwIDAu
MDAwIDAuMDAwIHJnDQowLjAwMCBUYw0KODMuMjg0IFR6DQooIDEyLjA0KVRqDQpFVA0KQlQNCjEu
MDAwIDAuMDAwIDAuMDAwIDEuMDAwIDI0Ni43MjAgMTU2Ljk2MCBUbQ0KL0Y1IDkuOTA0IFRmDQow
IFRyDQowLjAwMCAwLjAwMCAwLjAwMCByZw0KMC4wMDAgVGMNCjkxLjg0NyBUeg0KKExUUylUag0K
RVQNCkJUDQoxLjAwMCAwLjAwMCAwLjAwMCAxLjAwMCAyNjIuNTYwIDE1Ni45NjAgVG0NCi9GNSA5
LjkwNCBUZg0KMCBUcg0KMC4wMDAgMC4wMDAgMC4wMDAgcmcNCjAuMDAwIFRjDQo5Ny44NTcgVHoN
CiggU2VydmVyKVRqDQpFVA0KQlQNCjEuMDAwIDAuMDAwIDAuMDAwIDEuMDAwIDM1LjA0MCAxMzUu
MzYwIFRtDQovRjcgOS45MDQgVGYNCjAgVHINCjAuMDAwIDAuMDAwIDAuMDAwIHJnDQowLjAwMCBU
Yw0KOTEuMjUwIFR6DQooUmVxdWlyZWQpVGoNCkVUDQpCVA0KMS4wMDAgMC4wMDAgMC4wMDAgMS4w
MDAgNzEuMDQwIDEzNS4zNjAgVG0NCi9GNSA5LjkwNCBUZg0KMCBUcg0KMC4wMDAgMC4wMDAgMC4w
MDAgcmcNCjAuMDAwIFRjDQo3Ni45MjMgVHoNCig6KVRqDQpFVA0KQlQNCjEuMDAwIDAuMDAwIDAu
MDAwIDEuMDAwIDM1LjA0MCAxMTMuNzYwIFRtDQovRjUgOS45MDQgVGYNCjAgVHINCjAuMDAwIDAu
MDAwIDAuMDAwIHJnDQowLjAwMCBUYw0KOTMuNDg0IFR6DQooSG93IGNhbiBJIGNvbmZpZ3VyZSBt
eSlUag0KRVQNCkJUDQoxLjAwMCAwLjAwMCAwLjAwMCAxLjAwMCAxMjguNjQwIDExMy43NjAgVG0N
Ci9GNSA5LjkwNCBUZg0KMCBUcg0KMC4wMDAgMC4wMDAgMC4wMDAgcmcNCjAuMDAwIFRjDQoxMDku
MTYyIFR6DQooVk1zKVRqDQpFVA0KQlQNCjEuMDAwIDAuMDAwIDAuMDAwIDEuMDAwIDE0Ny4zNjAg
MTEzLjc2MCBUbQ0KL0Y1IDkuOTA0IFRmDQowIFRyDQowLjAwMCAwLjAwMCAwLjAwMCByZw0KMC4w
MDAgVGMNCjk1LjQ2OCBUeg0KKCB0byBtZWV0IHRoZSBmb2xsb3dpbmcgc2V0dXAgb3IgbmV0d29y
az8pVGoNCkVUDQpCVA0KMS4wMDAgMC4wMDAgMC4wMDAgMS4wMDAgMzUuMDQwIDkyLjE2MCBUbQ0K
L0Y1IDkuOTA0IFRmDQowIFRyDQowLjAwMCAwLjAwMCAwLjAwMCByZw0KMC4wMDAgVGMNCjcxLjMz
MyBUeg0KKGlcKSlUag0KRVQNCkJUDQoxLjAwMCAwLjAwMCAwLjAwMCAxLjAwMCA0Mi4yNDAgOTIu
MTYwIFRtDQovRjUgOS45MDQgVGYNCjAgVHINCjAuMDAwIDAuMDAwIDAuMDAwIHJnDQowLjAwMCBU
Yw0KMTAzLjMzMyBUeg0KKFZNMSlUag0KRVQNCkJUDQoxLjAwMCAwLjAwMCAwLjAwMCAxLjAwMCA2
MC45NjAgOTIuMTYwIFRtDQovRjUgOS45MDQgVGYNCjAgVHINCjAuMDAwIDAuMDAwIDAuMDAwIHJn
DQowLjAwMCBUYw0KNzQuNzc5IFR6DQooIC0pVGoNCkVUDQpCVA0KMS4wMDAgMC4wMDAgMC4wMDAg
MS4wMDAgNjguMTYwIDkyLjE2MCBUbQ0KL0Y1IDkuOTA0IFRmDQowIFRyDQowLjAwMCAwLjAwMCAw
LjAwMCByZw0KMC4wMDAgVGMNCjEwMy4zMzMgVHoNCihWTTYpVGoNCkVUDQpCVA0KMS4wMDAgMC4w
MDAgMC4wMDAgMS4wMDAgODYuODgwIDkyLjE2MCBUbQ0KL0Y1IDkuOTA0IFRmDQowIFRyDQowLjAw
MCAwLjAwMCAwLjAwMCByZw0KMC4wMDAgVGMNCjk0LjI2MyBUeg0KKCA9IGJlIG9uIHRoZSBuZXR3
b3JrIHdpdGggLzI5KVRqDQpFVA0KQlQNCjEuMDAwIDAuMDAwIDAuMDAwIDEuMDAwIDM1LjA0MCA3
MC41NjAgVG0NCi9GNSA5LjkwNCBUZg0KMCBUcg0KMC4wMDAgMC4wMDAgMC4wMDAgcmcNCjAuMDAw
IFRjDQo3My43MTEgVHoNCihpaVwpKVRqDQpFVA0KQlQNCjEuMDAwIDAuMDAwIDAuMDAwIDEuMDAw
IDQ0LjQwMCA3MC41NjAgVG0NCi9GNSA5LjkwNCBUZg0KMCBUcg0KMC4wMDAgMC4wMDAgMC4wMDAg
cmcNCjAuMDAwIFRjDQo5NS41NTEgVHoNCihldGgwKVRqDQpFVA0KQlQNCjEuMDAwIDAuMDAwIDAu
MDAwIDEuMDAwIDYwLjk2MCA3MC41NjAgVG0NCi9GNSA5LjkwNCBUZg0KMCBUcg0KMC4wMDAgMC4w
MDAgMC4wMDAgcmcNCjAuMDAwIFRjDQo5Mi42NDggVHoNCiggYW5kIEdFIDcvMyA9IFBvaW50IHRv
IFBvaW50IExpbmsgb3IgbmV0d29yayBvZiAvMzApVGoNCkVUDQpCVA0KMS4wMDAgMC4wMDAgMC4w
MDAgMS4wMDAgMzUuMDQwIDQ4Ljk2MCBUbQ0KL0Y1IDkuOTA0IFRmDQowIFRyDQowLjAwMCAwLjAw
MCAwLjAwMCByZw0KMC4wMDAgVGMNCjk5LjA5OCBUeg0KKENhbiB0aGlzIGJlIHBvc3NpYmxlPyBp
ZiBub3Qgc3VnZ2VzdCB0aGUgYmVzdCBzZXR1cCBmb3IpVGoNCkVUDQpCVA0KMS4wMDAgMC4wMDAg
MC4wMDAgMS4wMDAgMjQ0LjU2MCA0OC45NjAgVG0NCi9GNSA5LjkwNCBUZg0KMCBUcg0KMC4wMDAg
MC4wMDAgMC4wMDAgcmcNCjAuMDAwIFRjDQoxMDkuMTYyIFR6DQooVk1zKVRqDQpFVA0KQlQNCjEu
MDAwIDAuMDAwIDAuMDAwIDEuMDAwIDI2My4yODAgNDguOTYwIFRtDQovRjUgOS45MDQgVGYNCjAg
VHINCjAuMDAwIDAuMDAwIDAuMDAwIHJnDQowLjAwMCBUYw0KOTIuNzk0IFR6DQooICAgd2l0aCBz
dGF0aWMpVGoNCkVUDQpCVA0KMS4wMDAgMC4wMDAgMC4wMDAgMS4wMDAgMzExLjUyMCA0OC45NjAg
VG0NCi9GNSA5LjkwNCBUZg0KMCBUcg0KMC4wMDAgMC4wMDAgMC4wMDAgcmcNCjAuMDAwIFRjDQo2
NS41MjAgVHoNCihJUClUag0KRVQNCkJUDQoxLjAwMCAwLjAwMCAwLjAwMCAxLjAwMCAzMTkuNDQw
IDQ4Ljk2MCBUbQ0KL0Y1IDkuOTA0IFRmDQowIFRyDQowLjAwMCAwLjAwMCAwLjAwMCByZw0KMC4w
MDAgVGMNCjg3LjQ1MyBUeg0KKC4uKVRqDQpFVA0KQlQNCjEuMDAwIDAuMDAwIDAuMDAwIDEuMDAw
IDM1LjA0MCAyNy4zNjAgVG0NCi9GNSA5LjkwNCBUZg0KMCBUcg0KMC4wMDAgMC4wMDAgMC4wMDAg
cmcNCjAuMDAwIFRjDQo5My45MjMgVHoNCihJIHRyaWVkIGJ1dCBmYWlsZWQsIGl0IGp1c3QgZ28g
dG8pVGoNCkVUDQpCVA0KMS4wMDAgMC4wMDAgMC4wMDAgMS4wMDAgMTQ1LjkyMCAyNy4zNjAgVG0N
Ci9GNSA5LjkwNCBUZg0KMCBUcg0KMC4wMDAgMC4wMDAgMC4wMDAgcmcNCjAuMDAwIFRjDQo5OS41
NjEgVHoNCihkaGNwKVRqDQpFVA0KQlQNCjEuMDAwIDAuMDAwIDAuMDAwIDEuMDAwIDE2NS4zNjAg
MjcuMzYwIFRtDQovRjUgOS45MDQgVGYNCjAgVHINCjAuMDAwIDAuMDAwIDAuMDAwIHJnDQowLjAw
MCBUYw0KOTkuMzQ1IFR6DQooIGFuZCBJIG5lZWQgc3RhdGljLilUag0KRVQNCkJUDQoxLjAwMCAw
LjAwMCAwLjAwMCAxLjAwMCAzNS4wNDAgNS43NjAgVG0NCi9GNSA5LjkwNCBUZg0KMCBUcg0KMC4w
MDAgMC4wMDAgMC4wMDAgcmcNCjAuMDAwIFRjDQo5OS40NDAgVHoNCihQbGVhc2UgaGVscC4pVGoN
CkVUDQpRDQplbmRzdHJlYW0NCmVuZG9iag0KNiAwIG9iag0KODA4ODgNCmVuZG9iag0KNyAwIG9i
ag0KPDwNCi9UeXBlIC9Gb250DQovU3VidHlwZSAvVHlwZTENCi9OYW1lIC9GMg0KL0Jhc2VGb250
IC9BcmlhbA0KL0ZvbnREZXNjcmlwdG9yIDggMCBSDQovRW5jb2RpbmcgL1dpbkFuc2lFbmNvZGlu
Zw0KPj4NCmVuZG9iag0KOCAwIG9iag0KPDwNCi9UeXBlIC9Gb250RGVzY3JpcHRvcg0KL0FzY2Vu
dCAxMDAwDQovQ2FwSGVpZ2h0IDg5Ng0KL0Rlc2NlbnQgLTIzMg0KL0ZsYWdzIDMyDQovRm9udEJC
b3ggWzAgMCAwIDAgXQ0KL0ZvbnROYW1lIC9BcmlhbA0KL0l0YWxpY0FuZ2xlIC0xMQ0KL1N0ZW1W
IDgwDQo+Pg0KZW5kb2JqDQo5IDAgb2JqDQo8PA0KL1R5cGUgL0ZvbnQNCi9TdWJ0eXBlIC9UeXBl
MQ0KL05hbWUgL0YzDQovQmFzZUZvbnQgL0FyaWFsDQovRm9udERlc2NyaXB0b3IgMTAgMCBSDQov
RW5jb2RpbmcgL1dpbkFuc2lFbmNvZGluZw0KPj4NCmVuZG9iag0KMTAgMCBvYmoNCjw8DQovVHlw
ZSAvRm9udERlc2NyaXB0b3INCi9Bc2NlbnQgMTAwMA0KL0NhcEhlaWdodCA4OTcNCi9EZXNjZW50
IC0yMzQNCi9GbGFncyAzMg0KL0ZvbnRCQm94IFswIDAgMCAwIF0NCi9Gb250TmFtZSAvQXJpYWwN
Ci9JdGFsaWNBbmdsZSAtMTENCi9TdGVtViA4MA0KPj4NCmVuZG9iag0KMTEgMCBvYmoNCjw8DQov
VHlwZSAvRm9udA0KL1N1YnR5cGUgL1RydWVUeXBlDQovTmFtZSAvRjUNCi9CYXNlRm9udCAvVGlt
ZXNOZXdSb21hbg0KL0ZvbnREZXNjcmlwdG9yIDEyIDAgUg0KL0VuY29kaW5nIC9XaW5BbnNpRW5j
b2RpbmcNCj4+DQplbmRvYmoNCjEyIDAgb2JqDQo8PA0KL1R5cGUgL0ZvbnREZXNjcmlwdG9yDQov
QXNjZW50IDEwMDANCi9DYXBIZWlnaHQgOTAyDQovRGVzY2VudCAtMjQzDQovRmxhZ3MgMzQNCi9G
b250QkJveCBbMCAwIDAgMCBdDQovRm9udE5hbWUgL1RpbWVzTmV3Um9tYW4NCi9JdGFsaWNBbmds
ZSAtMTENCi9TdGVtViA4MA0KPj4NCmVuZG9iag0KMTMgMCBvYmoNCjw8DQovVHlwZSAvRm9udA0K
L1N1YnR5cGUgL1RydWVUeXBlDQovTmFtZSAvRjcNCi9CYXNlRm9udCAvVGltZXNOZXdSb21hbg0K
L0ZvbnREZXNjcmlwdG9yIDE0IDAgUg0KL0VuY29kaW5nIC9XaW5BbnNpRW5jb2RpbmcNCj4+DQpl
bmRvYmoNCjE0IDAgb2JqDQo8PA0KL1R5cGUgL0ZvbnREZXNjcmlwdG9yDQovQXNjZW50IDEwMDAN
Ci9DYXBIZWlnaHQgOTAyDQovRGVzY2VudCAtMjQzDQovRmxhZ3MgMzQNCi9Gb250QkJveCBbMCAw
IDAgMCBdDQovRm9udE5hbWUgL1RpbWVzTmV3Um9tYW4NCi9JdGFsaWNBbmdsZSAtMTENCi9TdGVt
ViA4MA0KPj4NCmVuZG9iag0KMyAwIG9iag0KPDwNCi9UeXBlIC9QYWdlDQovUGFyZW50IDQgMCBS
DQovTWVkaWFCb3ggWyAwIDAgMzk3IDQyOSBdDQovUmVzb3VyY2VzDQo8PA0KL1Byb2NTZXQgWy9Q
REYgL1RleHQgL0ltYWdlQiAvSW1hZ2VDIC9JbWFnZUldDQovRm9udA0KPDwNCi9GMiA3IDAgUg0K
L0YzIDkgMCBSDQovRjUgMTEgMCBSDQovRjcgMTMgMCBSDQo+Pg0KPj4NCi9Db250ZW50cyA1IDAg
Ug0KPj4NCmVuZG9iag0KNCAwIG9iag0KPDwNCi9UeXBlIC9QYWdlcw0KL0tpZHMgWyAzIDAgUiBd
DQovQ291bnQgMQ0KPj4NCmVuZG9iag0KMSAwIG9iag0KPDwNCi9UeXBlIC9DYXRhbG9nDQovUGFn
ZXMgNCAwIFINCj4+DQplbmRvYmoNCjIgMCBvYmoNCjw8DQovUHJvZHVjZXIgKEluc28gS2Fuc2Fz
IENpdHkgRXhwb3J0IFBERiBmaWx0ZXIpDQo+Pg0KZW5kb2JqDQp4cmVmDTAgMTUNMDAwMDAwMDAw
MCA2NTUzNSBmDQowMDAwMDgyNTYwIDAwMDAwIG4NCjAwMDAwODI2MTUgMDAwMDAgbg0KMDAwMDA4
MjI2OSAwMDAwMCBuDQowMDAwMDgyNDk0IDAwMDAwIG4NCjAwMDAwMDAwMjAgMDAwMDAgbg0KMDAw
MDA4MDk2NyAwMDAwMCBuDQowMDAwMDgwOTkxIDAwMDAwIG4NCjAwMDAwODExMjYgMDAwMDAgbg0K
MDAwMDA4MTI5OSAwMDAwMCBuDQowMDAwMDgxNDM1IDAwMDAwIG4NCjAwMDAwODE2MDkgMDAwMDAg
bg0KMDAwMDA4MTc1NyAwMDAwMCBuDQowMDAwMDgxOTM5IDAwMDAwIG4NCjAwMDAwODIwODcgMDAw
MDAgbg0KdHJhaWxlcg0KPDwNCi9TaXplIDE1DS9JbmZvIDIgMCBSDQovUm9vdCAxIDAgUg0KPj4N
CnN0YXJ0eHJlZg04MjY4OA0lJUVPRg0=
--f46d043c822079331f04caea6d93
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
Xen-users mailing list
Xen-users@lists.xen.org
http://lists.xen.org/xen-users
--f46d043c822079331f04caea6d93--


From xen-users-bounces@lists.xen.org Sun Sep 30 13:36:49 2012
Return-path: 
Envelope-to: archives@lists.xen.org
Delivery-date: Sun, 30 Sep 2012 13:36:49 +0000
Received: from localhost ([127.0.0.1] helo=lists.xen.org)
	by lists.xen.org with esmtp (Exim 4.72)
	(envelope-from )
	id 1TIJgC-00086z-5r; Sun, 30 Sep 2012 13:35:32 +0000
Received: from mail27.messagelabs.com ([193.109.254.147])
	by lists.xen.org with esmtp (Exim 4.72)
	(envelope-from ) id 1TIJgA-00086u-Gq
	for xen-users@lists.xen.org; Sun, 30 Sep 2012 13:35:31 +0000
X-Env-Sender: jh@excello.cz
X-Msg-Ref: server-3.tower-27.messagelabs.com!1349012123!10935698!1
X-Originating-IP: [81.31.35.100]
X-SpamReason: No, hits=0.1 required=7.0 tests=HTML_50_60,HTML_MESSAGE,
	ML_RADAR_SPEW_LINKS_8, UNPARSEABLE_RELAY, spamassassin: ,
	surbl: (ASYNC_NO) 
	c3VyYmxfcmVjaGVja19kZWxheTogMCAoYWJhbmRvbmVkOiB0ZXJuZXQub3IudHop\n
X-StarScan-Received: 
X-StarScan-Version: 6.6.1.3; banners=-,-,-
X-VirusChecked: Checked
Received: (qmail 14315 invoked from network); 30 Sep 2012 13:35:23 -0000
Received: from out2.virusfree.cz (HELO out2.virusfree.cz) (81.31.35.100)
	by server-3.tower-27.messagelabs.com with DHE-RSA-AES256-SHA encrypted
	SMTP; 30 Sep 2012 13:35:23 -0000
Received: (qmail 25920 invoked by uid 1000); 30 Sep 2012 15:35:21 +0200
Received: from smtp.excello.cz by out2 (envelope-from ,
	uid 201) with VF-scanner-2.08VF 
	(www.virusfree.cz : out2.virusfree.cz 
	Clear:RC:1(91.121.238.113):SA:0(-5.8/5.0):. 
	Processed in 1.991668 secs); 30 Sep 2012 13:35:21 -0000
X-Spam-Status: No, hits=-5.8 required=5.0
X-Spam-Report: SA TESTS 0.1 MAILBODYHTTPLINK       RAW: http:// v body
	-4.0 INREPLYTOCOM           INREPLYTOCOM
	-1.5 INREPLYTO0             INREPLYTO0
	-0.0 SPF_PASS               SPF: sender matches SPF record
	-2.1 RP_MATCHES_RCVD Envelope sender domain matches handover relay
	domain
	1.0 SPF_HELO_FAIL          SPF: HELO does not match SPF record (fail)
	[SPF failed: Please see http://www.openspf.net/Why?s=helo;
	id=smtp.excello.cz; ip=91.121.238.113; r=aq.virusfree.cz]
	0.0 HTML_MESSAGE           BODY: HTML included in message
	0.8 BAYES_50               BODY: Bayes spam probability is 40 to 60%
	[score: 0.5500]
	-0.1 DKIM_VALID_AU Message has a valid DKIM or DK signature from
	author's domain
	-0.1 DKIM_VALID Message has at least one valid DKIM or DK signature
	0.1 DKIM_SIGNED            Message has a DKIM or DK signature,
	not necessarily valid
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=excello.cz; h=
	date:message-id:from:to:subject:reply-to; q=dns/txt; s=default;
	t=1349012119; n=Test; bh=wwZl3FNKpFRYKvPM13pEZRAHRyzB262TGIUapc
	azpjk=; b=gq8FF9WUJyhmlvUErnoU3fpReGMlAUsH/BSoeRVTWzyQoRc+nXFkyD
	sPfbZRji8IMPiZTCCze7/iCJQ7HbF2Ra5r0oa+Kskg157onQC/RtD4CviBMzLSl/
	00ymQcbLj8
DomainKey-Signature: a=rsa-sha1; c=nofws; d=excello.cz; h=message-id
	:date:from:mime-version:to:subject:references:in-reply-to
	:content-type; q=dns; s=default; b=B8zn3XOMQ2T5BXNYE5ogR3EZg4J7k
	jLjXaM6ZVt83WoU79FQA2ZYPUh5LocSnREp7qMRfAwgxD53I0I40W4isxGMVjNRj
	RWGd8r01tp4RyQCU2aXwjGKvfrJbydNqOBa
Received: from smtp.excello.cz (91.121.238.113)
	by out2.virusfree.cz with SMTP; 30 Sep 2012 15:35:19 +0200
Received: from [192.168.1.167] (unknown [37.77.238.87])
	by smtp.excello.cz (Postfix) with ESMTPA id BDA9982458D1
	for ; Sun, 30 Sep 2012 15:35:18 +0200 (CEST)
Message-ID: <50684A96.6070201@excello.cz>
Date: Sun, 30 Sep 2012 15:35:18 +0200
From: Jan Hejl 
User-Agent: Mozilla/5.0 (X11; Linux x86_64;
	rv:15.0) Gecko/20120827 Thunderbird/15.0
MIME-Version: 1.0
To: xen-users@lists.xen.org
References: 
In-Reply-To: 
Subject: Re: [Xen-users] Networking
X-BeenThere: xen-users@lists.xen.org
X-Mailman-Version: 2.1.13
Precedence: list
List-Id: Xen user discussion 
List-Unsubscribe: ,
	
List-Post: 
List-Help: 
List-Subscribe: ,
	
Content-Type: multipart/mixed; boundary="===============7479245274809481919=="
Sender: xen-users-bounces@lists.xen.org
Errors-To: xen-users-bounces@lists.xen.org

This is a multi-part message in MIME format.
--===============7479245274809481919==
Content-Type: multipart/alternative;
 boundary="------------020602090601070104020405"

This is a multi-part message in MIME format.
--------------020602090601070104020405
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit

Hello Damas,

have you tried bridge setup? It should fit perfectly to your case.

Jan

On 30.9.2012 14:28, Damas A.Makweba wrote:
> Greetings all,
>
> I need help with xen networking, I am not good to set up xen.
>
> Please, pass through the xen.pdf file attached in which i tried to let 
> you know how my settings should be.
>
> I have a server, installed and configured with Ubuntu 12.04LTS server 
> and Xen 4.0, it contains 6doms ie VMs, i need to set up doms with 
> static IP rather than dhcp, I need to connect the server direct to 
> cisco router which is the 7600 series switch ports, please help me.
>
> Regards,
>
> -- 
> Damas A.M
> Network Engineer
> Tanzania Education & Research Network
> 
>
> *Mob: +255 (0) 714/ 754/ 784 - 46 46 78*
>
>
>
> _______________________________________________
> Xen-users mailing list
> Xen-users@lists.xen.org
> http://lists.xen.org/xen-users


--------------020602090601070104020405
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit


  
    
  
  
    Hello Damas,

    

    have you tried bridge setup? It should fit perfectly to your case.

    

    Jan

    

    
On 30.9.2012 14:28, Damas A.Makweba
      wrote:

    

    
Greetings all,

      

      I need help with xen networking, I am not good to set up xen.

      

      Please, pass through the xen.pdf file attached in which i tried to
      let you know how my settings should be.

      

      I have a server, installed and configured with Ubuntu 12.04LTS
      server and Xen 4.0, it contains 6doms ie VMs, i need to set up
      doms with static IP rather than dhcp, I need to connect the server
      direct to cisco router which is the 7600 series switch ports,
      please help me.

      

      Regards,

      

      -- 

      Damas A.M

      
Network Engineer

      

      
      


      

      
Mob: +255 (0) 714/ 754/ 784 - 46 46 78

      

      

      

      

      

      
_______________________________________________
Xen-users mailing list
Xen-users@lists.xen.org
http://lists.xen.org/xen-users

    

    

  


--------------020602090601070104020405--


--===============7479245274809481919==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
Xen-users mailing list
Xen-users@lists.xen.org
http://lists.xen.org/xen-users
--===============7479245274809481919==--


From xen-users-bounces@lists.xen.org Sun Sep 30 13:36:49 2012
Return-path: 
Envelope-to: archives@lists.xen.org
Delivery-date: Sun, 30 Sep 2012 13:36:49 +0000
Received: from localhost ([127.0.0.1] helo=lists.xen.org)
	by lists.xen.org with esmtp (Exim 4.72)
	(envelope-from )
	id 1TIJgC-00086z-5r; Sun, 30 Sep 2012 13:35:32 +0000
Received: from mail27.messagelabs.com ([193.109.254.147])
	by lists.xen.org with esmtp (Exim 4.72)
	(envelope-from ) id 1TIJgA-00086u-Gq
	for xen-users@lists.xen.org; Sun, 30 Sep 2012 13:35:31 +0000
X-Env-Sender: jh@excello.cz
X-Msg-Ref: server-3.tower-27.messagelabs.com!1349012123!10935698!1
X-Originating-IP: [81.31.35.100]
X-SpamReason: No, hits=0.1 required=7.0 tests=HTML_50_60,HTML_MESSAGE,
	ML_RADAR_SPEW_LINKS_8, UNPARSEABLE_RELAY, spamassassin: ,
	surbl: (ASYNC_NO) 
	c3VyYmxfcmVjaGVja19kZWxheTogMCAoYWJhbmRvbmVkOiB0ZXJuZXQub3IudHop\n
X-StarScan-Received: 
X-StarScan-Version: 6.6.1.3; banners=-,-,-
X-VirusChecked: Checked
Received: (qmail 14315 invoked from network); 30 Sep 2012 13:35:23 -0000
Received: from out2.virusfree.cz (HELO out2.virusfree.cz) (81.31.35.100)
	by server-3.tower-27.messagelabs.com with DHE-RSA-AES256-SHA encrypted
	SMTP; 30 Sep 2012 13:35:23 -0000
Received: (qmail 25920 invoked by uid 1000); 30 Sep 2012 15:35:21 +0200
Received: from smtp.excello.cz by out2 (envelope-from ,
	uid 201) with VF-scanner-2.08VF 
	(www.virusfree.cz : out2.virusfree.cz 
	Clear:RC:1(91.121.238.113):SA:0(-5.8/5.0):. 
	Processed in 1.991668 secs); 30 Sep 2012 13:35:21 -0000
X-Spam-Status: No, hits=-5.8 required=5.0
X-Spam-Report: SA TESTS 0.1 MAILBODYHTTPLINK       RAW: http:// v body
	-4.0 INREPLYTOCOM           INREPLYTOCOM
	-1.5 INREPLYTO0             INREPLYTO0
	-0.0 SPF_PASS               SPF: sender matches SPF record
	-2.1 RP_MATCHES_RCVD Envelope sender domain matches handover relay
	domain
	1.0 SPF_HELO_FAIL          SPF: HELO does not match SPF record (fail)
	[SPF failed: Please see http://www.openspf.net/Why?s=helo;
	id=smtp.excello.cz; ip=91.121.238.113; r=aq.virusfree.cz]
	0.0 HTML_MESSAGE           BODY: HTML included in message
	0.8 BAYES_50               BODY: Bayes spam probability is 40 to 60%
	[score: 0.5500]
	-0.1 DKIM_VALID_AU Message has a valid DKIM or DK signature from
	author's domain
	-0.1 DKIM_VALID Message has at least one valid DKIM or DK signature
	0.1 DKIM_SIGNED            Message has a DKIM or DK signature,
	not necessarily valid
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=excello.cz; h=
	date:message-id:from:to:subject:reply-to; q=dns/txt; s=default;
	t=1349012119; n=Test; bh=wwZl3FNKpFRYKvPM13pEZRAHRyzB262TGIUapc
	azpjk=; b=gq8FF9WUJyhmlvUErnoU3fpReGMlAUsH/BSoeRVTWzyQoRc+nXFkyD
	sPfbZRji8IMPiZTCCze7/iCJQ7HbF2Ra5r0oa+Kskg157onQC/RtD4CviBMzLSl/
	00ymQcbLj8
DomainKey-Signature: a=rsa-sha1; c=nofws; d=excello.cz; h=message-id
	:date:from:mime-version:to:subject:references:in-reply-to
	:content-type; q=dns; s=default; b=B8zn3XOMQ2T5BXNYE5ogR3EZg4J7k
	jLjXaM6ZVt83WoU79FQA2ZYPUh5LocSnREp7qMRfAwgxD53I0I40W4isxGMVjNRj
	RWGd8r01tp4RyQCU2aXwjGKvfrJbydNqOBa
Received: from smtp.excello.cz (91.121.238.113)
	by out2.virusfree.cz with SMTP; 30 Sep 2012 15:35:19 +0200
Received: from [192.168.1.167] (unknown [37.77.238.87])
	by smtp.excello.cz (Postfix) with ESMTPA id BDA9982458D1
	for ; Sun, 30 Sep 2012 15:35:18 +0200 (CEST)
Message-ID: <50684A96.6070201@excello.cz>
Date: Sun, 30 Sep 2012 15:35:18 +0200
From: Jan Hejl 
User-Agent: Mozilla/5.0 (X11; Linux x86_64;
	rv:15.0) Gecko/20120827 Thunderbird/15.0
MIME-Version: 1.0
To: xen-users@lists.xen.org
References: 
In-Reply-To: 
Subject: Re: [Xen-users] Networking
X-BeenThere: xen-users@lists.xen.org
X-Mailman-Version: 2.1.13
Precedence: list
List-Id: Xen user discussion 
List-Unsubscribe: ,
	
List-Post: 
List-Help: 
List-Subscribe: ,
	
Content-Type: multipart/mixed; boundary="===============7479245274809481919=="
Sender: xen-users-bounces@lists.xen.org
Errors-To: xen-users-bounces@lists.xen.org

This is a multi-part message in MIME format.
--===============7479245274809481919==
Content-Type: multipart/alternative;
 boundary="------------020602090601070104020405"

This is a multi-part message in MIME format.
--------------020602090601070104020405
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit

Hello Damas,

have you tried bridge setup? It should fit perfectly to your case.

Jan

On 30.9.2012 14:28, Damas A.Makweba wrote:
> Greetings all,
>
> I need help with xen networking, I am not good to set up xen.
>
> Please, pass through the xen.pdf file attached in which i tried to let 
> you know how my settings should be.
>
> I have a server, installed and configured with Ubuntu 12.04LTS server 
> and Xen 4.0, it contains 6doms ie VMs, i need to set up doms with 
> static IP rather than dhcp, I need to connect the server direct to 
> cisco router which is the 7600 series switch ports, please help me.
>
> Regards,
>
> -- 
> Damas A.M
> Network Engineer
> Tanzania Education & Research Network
> 
>
> *Mob: +255 (0) 714/ 754/ 784 - 46 46 78*
>
>
>
> _______________________________________________
> Xen-users mailing list
> Xen-users@lists.xen.org
> http://lists.xen.org/xen-users


--------------020602090601070104020405
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit


  
    
  
  
    Hello Damas,

    

    have you tried bridge setup? It should fit perfectly to your case.

    

    Jan

    

    
On 30.9.2012 14:28, Damas A.Makweba
      wrote:

    

    
Greetings all,

      

      I need help with xen networking, I am not good to set up xen.

      

      Please, pass through the xen.pdf file attached in which i tried to
      let you know how my settings should be.

      

      I have a server, installed and configured with Ubuntu 12.04LTS
      server and Xen 4.0, it contains 6doms ie VMs, i need to set up
      doms with static IP rather than dhcp, I need to connect the server
      direct to cisco router which is the 7600 series switch ports,
      please help me.

      

      Regards,

      

      -- 

      Damas A.M

      
Network Engineer

      

      
      


      

      
Mob: +255 (0) 714/ 754/ 784 - 46 46 78

      

      

      

      

      

      
_______________________________________________
Xen-users mailing list
Xen-users@lists.xen.org
http://lists.xen.org/xen-users

    

    

  


--------------020602090601070104020405--


--===============7479245274809481919==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
Xen-users mailing list
Xen-users@lists.xen.org
http://lists.xen.org/xen-users
--===============7479245274809481919==--


From xen-users-bounces@lists.xen.org Sun Sep 30 14:49:49 2012
Return-path: 
Envelope-to: archives@lists.xen.org
Delivery-date: Sun, 30 Sep 2012 14:49:49 +0000
Received: from localhost ([127.0.0.1] helo=lists.xen.org)
	by lists.xen.org with esmtp (Exim 4.72)
	(envelope-from )
	id 1TIKos-0000Bc-2L; Sun, 30 Sep 2012 14:48:34 +0000
Received: from mail6.bemta5.messagelabs.com ([195.245.231.135])
	by lists.xen.org with esmtp (Exim 4.72)
	(envelope-from ) id 1TIKop-0000BX-UJ
	for xen-users@lists.xen.org; Sun, 30 Sep 2012 14:48:32 +0000
Received: from [85.158.139.211:48050] by server-14.bemta-5.messagelabs.com id
	20/55-05772-FBB58605; Sun, 30 Sep 2012 14:48:31 +0000
X-Env-Sender: nd@syndicat.com
X-Msg-Ref: server-11.tower-206.messagelabs.com!1349016510!20508220!1
X-Originating-IP: [62.146.89.62]
X-SpamReason: No, hits=0.0 required=7.0 tests=
X-StarScan-Received: 
X-StarScan-Version: 6.6.1.3; banners=-,-,-
X-VirusChecked: Checked
Received: (qmail 16987 invoked from network); 30 Sep 2012 14:48:30 -0000
Received: from ffm-dr1.syndicat.com (HELO ffm-dr1.syndicat.com) (62.146.89.62)
	by server-11.tower-206.messagelabs.com with DHE-RSA-AES256-SHA
	encrypted SMTP; 30 Sep 2012 14:48:30 -0000
Received: from localhost.syndicat.com ([127.0.0.1] helo=localhost)
	by ffm-dr1.syndicat.com with esmtp (Syndicat.com PostHamster 8.1.4.76)
	(envelope-from )
	id 1TIKon-0000VT-G8; Sun, 30 Sep 2012 16:48:29 +0200
X-Virus-Scanned: amavisd-new at syndicat.com
Received: from ffm-dr1.syndicat.com ([127.0.0.1])
	by localhost (ffm-dr1.syndicat.com [127.0.0.1]) (amavisd-new,
	port 10024)
	with ESMTP id SJdbrT4dGyFR; Sun, 30 Sep 2012 16:48:29 +0200 (CEST)
Received: from tmo-097-118.customers.d1-online.com ([80.187.97.118]
	helo=[31.230.158.52])
	by ffm-dr1.syndicat.com with esmtpsa (TLSv1:RC4-MD5:128)
	(Syndicat.com PostHamster 8.1.4.76) (envelope-from )
	id 1TIKom-0001vZ-Ds; Sun, 30 Sep 2012 16:48:29 +0200
User-Agent: K-9 Mail for Android
In-Reply-To: 
References: 
MIME-Version: 1.0
From: "Niels Dettenbach (Syndicat IT&Internet)" 
Date: Sun, 30 Sep 2012 16:47:26 +0200
To: "Damas A.Makweba" , xen-users@lists.xen.org,
	"Damas A.Makweba" , xen-users@lists.xen.org
Message-ID: 
Subject: Re: [Xen-users] Networking
X-BeenThere: xen-users@lists.xen.org
X-Mailman-Version: 2.1.13
Precedence: list
List-Id: Xen user discussion 
List-Unsubscribe: ,
	
List-Post: 
List-Help: 
List-Subscribe: ,
	
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: xen-users-bounces@lists.xen.org
Errors-To: xen-users-bounces@lists.xen.org

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256





"Damas A.Makweba"  schrieb:
orking, I am not good to set up xen.
>
>Please, pass through the xen.pdf file attached in which i tried to let
>you
>know how my settings should be.
Just btw: please avoid posting attachements in such lists like here and use links or bring it inline as text.


>I have a server, installed and configured with Ubuntu 12.04LTS server
>and
>Xen 4.0, it contains 6doms ie VMs, i need to set up doms with static IP
>rather than dhcp, I need to connect the server direct to cisco router
DHCP has nothing to do with dynamic/static IP setups - you are able to make static assignements with DHCP to dedicated guests too (i.e. by MAC).

>which
>is the 7600 series switch ports, please help me.

- - generate a bridge with your eth0 - i.e. xenbr0
- - activate xen bridge script (let connecting new VMs vif to the bridge) or do that by hand
- - give IPs from the same IP segment you have routed by your cisco to your host machine(s eth0)

You may check that the bridge setup is working with brctl show - your eth0 and your vif should be connected to that bridge when DomU is up. You may connect as many DomUs to your bridge as possible by your setup / hardware too.

Hth
Best regards,


Niels.

- --
Niels Dettenbach
Syndicat IT&Internet
http://www.syndicat.com
-----BEGIN PGP SIGNATURE-----
Version: APG v1.0.8

iIEEAREIAEEFAlBoW3k6HE5pZWxzIERldHRlbmJhY2ggKFN5bmRpY2F0IElUJklu
dGVybmV0KSA8bmRAc3luZGljYXQuY29tPgAKCRBU3ERlZRyiDVg+AJ0Q6XE9EGkE
qdYPh++p5LTgZCvPlwCcDUKGIpv/sbVcVxYUFQcZSr49dXc=
=Ynvn
-----END PGP SIGNATURE-----


_______________________________________________
Xen-users mailing list
Xen-users@lists.xen.org
http://lists.xen.org/xen-users

From xen-users-bounces@lists.xen.org Sun Sep 30 14:49:49 2012
Return-path: 
Envelope-to: archives@lists.xen.org
Delivery-date: Sun, 30 Sep 2012 14:49:49 +0000
Received: from localhost ([127.0.0.1] helo=lists.xen.org)
	by lists.xen.org with esmtp (Exim 4.72)
	(envelope-from )
	id 1TIKos-0000Bc-2L; Sun, 30 Sep 2012 14:48:34 +0000
Received: from mail6.bemta5.messagelabs.com ([195.245.231.135])
	by lists.xen.org with esmtp (Exim 4.72)
	(envelope-from ) id 1TIKop-0000BX-UJ
	for xen-users@lists.xen.org; Sun, 30 Sep 2012 14:48:32 +0000
Received: from [85.158.139.211:48050] by server-14.bemta-5.messagelabs.com id
	20/55-05772-FBB58605; Sun, 30 Sep 2012 14:48:31 +0000
X-Env-Sender: nd@syndicat.com
X-Msg-Ref: server-11.tower-206.messagelabs.com!1349016510!20508220!1
X-Originating-IP: [62.146.89.62]
X-SpamReason: No, hits=0.0 required=7.0 tests=
X-StarScan-Received: 
X-StarScan-Version: 6.6.1.3; banners=-,-,-
X-VirusChecked: Checked
Received: (qmail 16987 invoked from network); 30 Sep 2012 14:48:30 -0000
Received: from ffm-dr1.syndicat.com (HELO ffm-dr1.syndicat.com) (62.146.89.62)
	by server-11.tower-206.messagelabs.com with DHE-RSA-AES256-SHA
	encrypted SMTP; 30 Sep 2012 14:48:30 -0000
Received: from localhost.syndicat.com ([127.0.0.1] helo=localhost)
	by ffm-dr1.syndicat.com with esmtp (Syndicat.com PostHamster 8.1.4.76)
	(envelope-from )
	id 1TIKon-0000VT-G8; Sun, 30 Sep 2012 16:48:29 +0200
X-Virus-Scanned: amavisd-new at syndicat.com
Received: from ffm-dr1.syndicat.com ([127.0.0.1])
	by localhost (ffm-dr1.syndicat.com [127.0.0.1]) (amavisd-new,
	port 10024)
	with ESMTP id SJdbrT4dGyFR; Sun, 30 Sep 2012 16:48:29 +0200 (CEST)
Received: from tmo-097-118.customers.d1-online.com ([80.187.97.118]
	helo=[31.230.158.52])
	by ffm-dr1.syndicat.com with esmtpsa (TLSv1:RC4-MD5:128)
	(Syndicat.com PostHamster 8.1.4.76) (envelope-from )
	id 1TIKom-0001vZ-Ds; Sun, 30 Sep 2012 16:48:29 +0200
User-Agent: K-9 Mail for Android
In-Reply-To: 
References: 
MIME-Version: 1.0
From: "Niels Dettenbach (Syndicat IT&Internet)" 
Date: Sun, 30 Sep 2012 16:47:26 +0200
To: "Damas A.Makweba" , xen-users@lists.xen.org,
	"Damas A.Makweba" , xen-users@lists.xen.org
Message-ID: 
Subject: Re: [Xen-users] Networking
X-BeenThere: xen-users@lists.xen.org
X-Mailman-Version: 2.1.13
Precedence: list
List-Id: Xen user discussion 
List-Unsubscribe: ,
	
List-Post: 
List-Help: 
List-Subscribe: ,
	
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: xen-users-bounces@lists.xen.org
Errors-To: xen-users-bounces@lists.xen.org

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256





"Damas A.Makweba"  schrieb:
orking, I am not good to set up xen.
>
>Please, pass through the xen.pdf file attached in which i tried to let
>you
>know how my settings should be.
Just btw: please avoid posting attachements in such lists like here and use links or bring it inline as text.


>I have a server, installed and configured with Ubuntu 12.04LTS server
>and
>Xen 4.0, it contains 6doms ie VMs, i need to set up doms with static IP
>rather than dhcp, I need to connect the server direct to cisco router
DHCP has nothing to do with dynamic/static IP setups - you are able to make static assignements with DHCP to dedicated guests too (i.e. by MAC).

>which
>is the 7600 series switch ports, please help me.

- - generate a bridge with your eth0 - i.e. xenbr0
- - activate xen bridge script (let connecting new VMs vif to the bridge) or do that by hand
- - give IPs from the same IP segment you have routed by your cisco to your host machine(s eth0)

You may check that the bridge setup is working with brctl show - your eth0 and your vif should be connected to that bridge when DomU is up. You may connect as many DomUs to your bridge as possible by your setup / hardware too.

Hth
Best regards,


Niels.

- --
Niels Dettenbach
Syndicat IT&Internet
http://www.syndicat.com
-----BEGIN PGP SIGNATURE-----
Version: APG v1.0.8

iIEEAREIAEEFAlBoW3k6HE5pZWxzIERldHRlbmJhY2ggKFN5bmRpY2F0IElUJklu
dGVybmV0KSA8bmRAc3luZGljYXQuY29tPgAKCRBU3ERlZRyiDVg+AJ0Q6XE9EGkE
qdYPh++p5LTgZCvPlwCcDUKGIpv/sbVcVxYUFQcZSr49dXc=
=Ynvn
-----END PGP SIGNATURE-----


_______________________________________________
Xen-users mailing list
Xen-users@lists.xen.org
http://lists.xen.org/xen-users

From xen-users-bounces@lists.xen.org Sun Sep 30 15:14:30 2012
Return-path: 
Envelope-to: archives@lists.xen.org
Delivery-date: Sun, 30 Sep 2012 15:14:30 +0000
Received: from localhost ([127.0.0.1] helo=lists.xen.org)
	by lists.xen.org with esmtp (Exim 4.72)
	(envelope-from )
	id 1TILCw-0000aZ-TO; Sun, 30 Sep 2012 15:13:26 +0000
Received: from mail27.messagelabs.com ([193.109.254.147])
	by lists.xen.org with esmtp (Exim 4.72)
	(envelope-from )
	id 1TILCv-0000aK-2I; Sun, 30 Sep 2012 15:13:25 +0000
X-Env-Sender: pasik@iki.fi
X-Msg-Ref: server-5.tower-27.messagelabs.com!1349017997!6806956!1
X-Originating-IP: [192.89.123.25]
X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: 
	VHJ1c3RlZCBJUDogMTkyLjg5LjEyMy4yNSA9PiA1MjEyOTQ=\n
X-StarScan-Received: 
X-StarScan-Version: 6.6.1.3; banners=-,-,-
X-VirusChecked: Checked
Received: (qmail 1054 invoked from network); 30 Sep 2012 15:13:17 -0000
Received: from smtp.tele.fi (HELO smtp.tele.fi) (192.89.123.25)
	by server-5.tower-27.messagelabs.com with DHE-RSA-AES256-SHA encrypted
	SMTP; 30 Sep 2012 15:13:17 -0000
X-Originating-Ip: [194.89.68.22]
Received: from ydin.reaktio.net (reaktio.net [194.89.68.22])
	by smtp.tele.fi (Postfix) with ESMTP id 2304E13DB;
	Sun, 30 Sep 2012 18:13:14 +0300 (EEST)
Received: by ydin.reaktio.net (Postfix, from userid 1001)
	id 7DA7B2005D; Sun, 30 Sep 2012 18:13:14 +0300 (EEST)
Date: Sun, 30 Sep 2012 18:13:14 +0300
From: Pasi =?iso-8859-1?Q?K=E4rkk=E4inen?= 
To: Mauro 
Message-ID: <20120930151314.GU8912@reaktio.net>
References: 
	
	
	
	<65395f62-74e5-4910-b701-8df629c2ce3b@default>
	
	
	
	
	
MIME-Version: 1.0
Content-Disposition: inline
In-Reply-To: 
User-Agent: Mutt/1.5.20 (2009-06-14)
Cc: Dan Magenheimer , xen-devel@lists.xensource.com,
	Keir Fraser , Jeremy Fitzhardinge ,
	Olivier Hanesse ,
	Keir Fraser ,
	Xen Users ,
	Mark Adams 
Subject: Re: [Xen-users] [Xen-devel]  Re:  Xen 4 TSC problems
X-BeenThere: xen-users@lists.xen.org
X-Mailman-Version: 2.1.13
Precedence: list
List-Id: Xen user discussion 
List-Unsubscribe: ,
	
List-Post: 
List-Help: 
List-Subscribe: ,
	
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: xen-users-bounces@lists.xen.org
Errors-To: xen-users-bounces@lists.xen.org

On Sat, Sep 29, 2012 at 02:19:55PM +0200, Mauro wrote:
> It's happened another time, system date 50 minutes ahead.
> There is really no solution?
> 

Try with a recent Xen hypervisor version. Xen 4.1.3 or 4.2.0.
It helps a lot to know if the issue is still in the latest hypervisor versions or not.

4.0.1 is quite old already.. and besides 4.0.4 is the latest version in 4.0 branch.

-- Pasi

> root@xen-p02:~# date
> sab 29 set 2012, 15.06.25, CEST
> 
> root@xen-p02:~# hwclock --debug
> hwclock from util-linux-ng 2.17.2
> Using /dev interface to clock.
> Last drift adjustment done at 1348816781 seconds after 1969
> Last calibration done at 1348816781 seconds after 1969
> Hardware clock is on UTC time
> Assuming hardware clock is kept in UTC time.
> Waiting for clock tick...
> ...got clock tick
> Time read from Hardware Clock: 2012/09/29 12:16:58
> Hw clock time : 2012/09/29 12:16:58 = 1348921018 seconds since 1969
> sab 29 set 2012 14:16:58 CEST  -0.751536 seconds
> 
> root@xen-p02:~# hwclock --show
> sab 29 set 2012 14:17:12 CEST  -0.423643 seconds
> 
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xen.org
> http://lists.xen.org/xen-devel

_______________________________________________
Xen-users mailing list
Xen-users@lists.xen.org
http://lists.xen.org/xen-users

From xen-users-bounces@lists.xen.org Sun Sep 30 15:14:30 2012
Return-path: 
Envelope-to: archives@lists.xen.org
Delivery-date: Sun, 30 Sep 2012 15:14:30 +0000
Received: from localhost ([127.0.0.1] helo=lists.xen.org)
	by lists.xen.org with esmtp (Exim 4.72)
	(envelope-from )
	id 1TILCw-0000aZ-TO; Sun, 30 Sep 2012 15:13:26 +0000
Received: from mail27.messagelabs.com ([193.109.254.147])
	by lists.xen.org with esmtp (Exim 4.72)
	(envelope-from )
	id 1TILCv-0000aK-2I; Sun, 30 Sep 2012 15:13:25 +0000
X-Env-Sender: pasik@iki.fi
X-Msg-Ref: server-5.tower-27.messagelabs.com!1349017997!6806956!1
X-Originating-IP: [192.89.123.25]
X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: 
	VHJ1c3RlZCBJUDogMTkyLjg5LjEyMy4yNSA9PiA1MjEyOTQ=\n
X-StarScan-Received: 
X-StarScan-Version: 6.6.1.3; banners=-,-,-
X-VirusChecked: Checked
Received: (qmail 1054 invoked from network); 30 Sep 2012 15:13:17 -0000
Received: from smtp.tele.fi (HELO smtp.tele.fi) (192.89.123.25)
	by server-5.tower-27.messagelabs.com with DHE-RSA-AES256-SHA encrypted
	SMTP; 30 Sep 2012 15:13:17 -0000
X-Originating-Ip: [194.89.68.22]
Received: from ydin.reaktio.net (reaktio.net [194.89.68.22])
	by smtp.tele.fi (Postfix) with ESMTP id 2304E13DB;
	Sun, 30 Sep 2012 18:13:14 +0300 (EEST)
Received: by ydin.reaktio.net (Postfix, from userid 1001)
	id 7DA7B2005D; Sun, 30 Sep 2012 18:13:14 +0300 (EEST)
Date: Sun, 30 Sep 2012 18:13:14 +0300
From: Pasi =?iso-8859-1?Q?K=E4rkk=E4inen?= 
To: Mauro 
Message-ID: <20120930151314.GU8912@reaktio.net>
References: 
	
	
	
	<65395f62-74e5-4910-b701-8df629c2ce3b@default>
	
	
	
	
	
MIME-Version: 1.0
Content-Disposition: inline
In-Reply-To: 
User-Agent: Mutt/1.5.20 (2009-06-14)
Cc: Dan Magenheimer , xen-devel@lists.xensource.com,
	Keir Fraser , Jeremy Fitzhardinge ,
	Olivier Hanesse ,
	Keir Fraser ,
	Xen Users ,
	Mark Adams 
Subject: Re: [Xen-users] [Xen-devel]  Re:  Xen 4 TSC problems
X-BeenThere: xen-users@lists.xen.org
X-Mailman-Version: 2.1.13
Precedence: list
List-Id: Xen user discussion 
List-Unsubscribe: ,
	
List-Post: 
List-Help: 
List-Subscribe: ,
	
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: xen-users-bounces@lists.xen.org
Errors-To: xen-users-bounces@lists.xen.org

On Sat, Sep 29, 2012 at 02:19:55PM +0200, Mauro wrote:
> It's happened another time, system date 50 minutes ahead.
> There is really no solution?
> 

Try with a recent Xen hypervisor version. Xen 4.1.3 or 4.2.0.
It helps a lot to know if the issue is still in the latest hypervisor versions or not.

4.0.1 is quite old already.. and besides 4.0.4 is the latest version in 4.0 branch.

-- Pasi

> root@xen-p02:~# date
> sab 29 set 2012, 15.06.25, CEST
> 
> root@xen-p02:~# hwclock --debug
> hwclock from util-linux-ng 2.17.2
> Using /dev interface to clock.
> Last drift adjustment done at 1348816781 seconds after 1969
> Last calibration done at 1348816781 seconds after 1969
> Hardware clock is on UTC time
> Assuming hardware clock is kept in UTC time.
> Waiting for clock tick...
> ...got clock tick
> Time read from Hardware Clock: 2012/09/29 12:16:58
> Hw clock time : 2012/09/29 12:16:58 = 1348921018 seconds since 1969
> sab 29 set 2012 14:16:58 CEST  -0.751536 seconds
> 
> root@xen-p02:~# hwclock --show
> sab 29 set 2012 14:17:12 CEST  -0.423643 seconds
> 
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xen.org
> http://lists.xen.org/xen-devel

_______________________________________________
Xen-users mailing list
Xen-users@lists.xen.org
http://lists.xen.org/xen-users

From xen-users-bounces@lists.xen.org Sun Sep 30 15:51:39 2012
Return-path: 
Envelope-to: archives@lists.xen.org
Delivery-date: Sun, 30 Sep 2012 15:51:39 +0000
Received: from localhost ([127.0.0.1] helo=lists.xen.org)
	by lists.xen.org with esmtp (Exim 4.72)
	(envelope-from )
	id 1TILmo-00016U-Ag; Sun, 30 Sep 2012 15:50:30 +0000
Received: from mail6.bemta3.messagelabs.com ([195.245.230.39])
	by lists.xen.org with esmtp (Exim 4.72)
	(envelope-from ) id 1THs6T-00061B-Dn
	for xen-users@lists.xensource.com; Sat, 29 Sep 2012 08:08:49 +0000
Received: from [85.158.138.51:22366] by server-13.bemta-3.messagelabs.com id
	30/7E-11249-F8CA6605; Sat, 29 Sep 2012 08:08:47 +0000
X-Env-Sender: olivier.hanesse@gmail.com
X-Msg-Ref: server-12.tower-174.messagelabs.com!1348906125!24499739!1
X-Originating-IP: [209.85.223.171]
X-SpamReason: No, hits=0.4 required=7.0 tests=HTML_30_40,HTML_MESSAGE,
	ML_RADAR_SPEW_LINKS_14,RCVD_BY_IP,spamassassin: 
X-StarScan-Received: 
X-StarScan-Version: 6.6.1.3; banners=-,-,-
X-VirusChecked: Checked
Received: (qmail 11546 invoked from network); 29 Sep 2012 08:08:47 -0000
Received: from mail-ie0-f171.google.com (HELO mail-ie0-f171.google.com)
	(209.85.223.171)
	by server-12.tower-174.messagelabs.com with RC4-SHA encrypted SMTP;
	29 Sep 2012 08:08:47 -0000
Received: by iecs9 with SMTP id s9so11219887iec.30
	for ; Sat, 29 Sep 2012 01:08:45 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;
	h=mime-version:in-reply-to:references:date:message-id:subject:from:to
	:cc:content-type;
	bh=/bNPju4pbG3HzClnBKgdV/tm2QvImu5qgALMiQbuQPA=;
	b=jQ2+wmej4/P8PO2/XLyY3elQRjiYH8LMDCXdEV7ZLVO/Sf3G5MZ3RIVaIFZmZQZOZX
	lQG0m7GA0oJeHmwDoNInrW6t4J3rjDdwPPfiIeZ9ovv8If6ZKGxJJ2kLLsXgJ0yIVwJk
	l3MeL6Vt6TxJb6WGSAfriwV/YxBj987/R4bJvn8gr4X+SVMh4QbMWIsUNb9uMQy+xYb0
	3o3tivaQVJ9pjex1++1KViiq4LiwGWHtJe5qbDGMsIVUOfzXOGut1zIZ2C32hoN+R9Qp
	b0NU/T5XuwN6QC3WAj8GuJ9RTT0+9Kv0rl4ong0zEKeay/L1xmn/SqF9D88a7L/YuyGB
	6bRw==
MIME-Version: 1.0
Received: by 10.50.104.137 with SMTP id ge9mr870235igb.17.1348906125215; Sat,
	29 Sep 2012 01:08:45 -0700 (PDT)
Received: by 10.64.20.76 with HTTP; Sat, 29 Sep 2012 01:08:45 -0700 (PDT)
In-Reply-To: 
References: <68c41dd8-9195-41b0-83d7-9242b8eff809@default>
	
	
	
	
	
	<65395f62-74e5-4910-b701-8df629c2ce3b@default>
	
	
Date: Sat, 29 Sep 2012 10:08:45 +0200
Message-ID: 
From: Olivier Hanesse 
To: Mauro 
X-Mailman-Approved-At: Sun, 30 Sep 2012 15:50:29 +0000
Cc: Dan Magenheimer , xen-devel@lists.xensource.com,
	Keir Fraser , Jeremy Fitzhardinge ,
	Jan Beulich , Keir Fraser ,
	Xen Users ,
	Mark Adams 
Subject: Re: [Xen-users] [Xen-devel] Xen 4 TSC problems
X-BeenThere: xen-users@lists.xen.org
X-Mailman-Version: 2.1.13
Precedence: list
List-Id: Xen user discussion 
List-Unsubscribe: ,
	
List-Post: 
List-Help: 
List-Subscribe: ,
	
Content-Type: multipart/mixed; boundary="===============6031517816050720802=="
Sender: xen-users-bounces@lists.xen.org
Errors-To: xen-users-bounces@lists.xen.org

--===============6031517816050720802==
Content-Type: multipart/alternative; boundary=e89a8f23585f6dc74e04cad2ae5f

--e89a8f23585f6dc74e04cad2ae5f
Content-Type: text/plain; charset=ISO-8859-1

It didn't work for me :(
clocksource=pit made another "time jump" (don't remember how much, but it
was worst than 50min)

2012/9/27 Mauro 

> On 27 September 2012 23:28, Olivier Hanesse 
> wrote:
> > Hello,
> >
> > From my point of view, this was a kind of xen hardware
> "incompatibility/bug"
> > : I was able to reproduce this bug on more than 50 identical servers, but
> > not on another farm of servers with a different hardware.
> > Xen version, Debian Kernel was exactly the same on both farm.
>
> Yes I think so.
> The problem is where I use debian squeeze with xen 4.0.
> In another server with the same hardware but with debian lenny and xen
> 3.0 I have no problems.
> I've read that a workaround is to set clocksource=pit on the xen boot
> line in the grub conf, I hope this works because I can't change hardware.
>

--e89a8f23585f6dc74e04cad2ae5f
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

It didn't work for me :(
clocksource=3Dpit made another "time =
jump" (don't remember how much, but it was worst than 50min)
2012/9/27 Mauro <mrsanna1@gmail.com>=



On 27 September 2012 23:28=
, Olivier Hanesse <olivier.=
hanesse@gmail.com> wrote:



> Hello,

>

> From my point of view, this was a kind of xen hardware "incompati=
bility/bug"

> : I was able to reproduce this bug on more than 50 identical servers, =
but

> not on another farm of servers with a different hardware.

> Xen version, Debian Kernel was exactly the same on both farm.




Yes I think so.

The problem is where I use debian squeeze with xen 4.0.

In another server with the same hardware but with debian lenny and xen

3.0 I have no problems.

I've read that a workaround is to set clocksource=3Dpit on the xen boot=



line in the grub conf, I hope this works because I can't change h=
ardware.





--e89a8f23585f6dc74e04cad2ae5f--


--===============6031517816050720802==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
Xen-users mailing list
Xen-users@lists.xen.org
http://lists.xen.org/xen-users
--===============6031517816050720802==--


From xen-users-bounces@lists.xen.org Sun Sep 30 15:51:39 2012
Return-path: 
Envelope-to: archives@lists.xen.org
Delivery-date: Sun, 30 Sep 2012 15:51:39 +0000
Received: from localhost ([127.0.0.1] helo=lists.xen.org)
	by lists.xen.org with esmtp (Exim 4.72)
	(envelope-from )
	id 1TILmo-00016U-Ag; Sun, 30 Sep 2012 15:50:30 +0000
Received: from mail6.bemta3.messagelabs.com ([195.245.230.39])
	by lists.xen.org with esmtp (Exim 4.72)
	(envelope-from ) id 1THs6T-00061B-Dn
	for xen-users@lists.xensource.com; Sat, 29 Sep 2012 08:08:49 +0000
Received: from [85.158.138.51:22366] by server-13.bemta-3.messagelabs.com id
	30/7E-11249-F8CA6605; Sat, 29 Sep 2012 08:08:47 +0000
X-Env-Sender: olivier.hanesse@gmail.com
X-Msg-Ref: server-12.tower-174.messagelabs.com!1348906125!24499739!1
X-Originating-IP: [209.85.223.171]
X-SpamReason: No, hits=0.4 required=7.0 tests=HTML_30_40,HTML_MESSAGE,
	ML_RADAR_SPEW_LINKS_14,RCVD_BY_IP,spamassassin: 
X-StarScan-Received: 
X-StarScan-Version: 6.6.1.3; banners=-,-,-
X-VirusChecked: Checked
Received: (qmail 11546 invoked from network); 29 Sep 2012 08:08:47 -0000
Received: from mail-ie0-f171.google.com (HELO mail-ie0-f171.google.com)
	(209.85.223.171)
	by server-12.tower-174.messagelabs.com with RC4-SHA encrypted SMTP;
	29 Sep 2012 08:08:47 -0000
Received: by iecs9 with SMTP id s9so11219887iec.30
	for ; Sat, 29 Sep 2012 01:08:45 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;
	h=mime-version:in-reply-to:references:date:message-id:subject:from:to
	:cc:content-type;
	bh=/bNPju4pbG3HzClnBKgdV/tm2QvImu5qgALMiQbuQPA=;
	b=jQ2+wmej4/P8PO2/XLyY3elQRjiYH8LMDCXdEV7ZLVO/Sf3G5MZ3RIVaIFZmZQZOZX
	lQG0m7GA0oJeHmwDoNInrW6t4J3rjDdwPPfiIeZ9ovv8If6ZKGxJJ2kLLsXgJ0yIVwJk
	l3MeL6Vt6TxJb6WGSAfriwV/YxBj987/R4bJvn8gr4X+SVMh4QbMWIsUNb9uMQy+xYb0
	3o3tivaQVJ9pjex1++1KViiq4LiwGWHtJe5qbDGMsIVUOfzXOGut1zIZ2C32hoN+R9Qp
	b0NU/T5XuwN6QC3WAj8GuJ9RTT0+9Kv0rl4ong0zEKeay/L1xmn/SqF9D88a7L/YuyGB
	6bRw==
MIME-Version: 1.0
Received: by 10.50.104.137 with SMTP id ge9mr870235igb.17.1348906125215; Sat,
	29 Sep 2012 01:08:45 -0700 (PDT)
Received: by 10.64.20.76 with HTTP; Sat, 29 Sep 2012 01:08:45 -0700 (PDT)
In-Reply-To: 
References: <68c41dd8-9195-41b0-83d7-9242b8eff809@default>
	
	
	
	
	
	<65395f62-74e5-4910-b701-8df629c2ce3b@default>
	
	
Date: Sat, 29 Sep 2012 10:08:45 +0200
Message-ID: 
From: Olivier Hanesse 
To: Mauro 
X-Mailman-Approved-At: Sun, 30 Sep 2012 15:50:29 +0000
Cc: Dan Magenheimer , xen-devel@lists.xensource.com,
	Keir Fraser , Jeremy Fitzhardinge ,
	Jan Beulich , Keir Fraser ,
	Xen Users ,
	Mark Adams 
Subject: Re: [Xen-users] [Xen-devel] Xen 4 TSC problems
X-BeenThere: xen-users@lists.xen.org
X-Mailman-Version: 2.1.13
Precedence: list
List-Id: Xen user discussion 
List-Unsubscribe: ,
	
List-Post: 
List-Help: 
List-Subscribe: ,
	
Content-Type: multipart/mixed; boundary="===============6031517816050720802=="
Sender: xen-users-bounces@lists.xen.org
Errors-To: xen-users-bounces@lists.xen.org

--===============6031517816050720802==
Content-Type: multipart/alternative; boundary=e89a8f23585f6dc74e04cad2ae5f

--e89a8f23585f6dc74e04cad2ae5f
Content-Type: text/plain; charset=ISO-8859-1

It didn't work for me :(
clocksource=pit made another "time jump" (don't remember how much, but it
was worst than 50min)

2012/9/27 Mauro 

> On 27 September 2012 23:28, Olivier Hanesse 
> wrote:
> > Hello,
> >
> > From my point of view, this was a kind of xen hardware
> "incompatibility/bug"
> > : I was able to reproduce this bug on more than 50 identical servers, but
> > not on another farm of servers with a different hardware.
> > Xen version, Debian Kernel was exactly the same on both farm.
>
> Yes I think so.
> The problem is where I use debian squeeze with xen 4.0.
> In another server with the same hardware but with debian lenny and xen
> 3.0 I have no problems.
> I've read that a workaround is to set clocksource=pit on the xen boot
> line in the grub conf, I hope this works because I can't change hardware.
>

--e89a8f23585f6dc74e04cad2ae5f
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

It didn't work for me :(
clocksource=3Dpit made another "time =
jump" (don't remember how much, but it was worst than 50min)
2012/9/27 Mauro <mrsanna1@gmail.com>=



On 27 September 2012 23:28=
, Olivier Hanesse <olivier.=
hanesse@gmail.com> wrote:



> Hello,

>

> From my point of view, this was a kind of xen hardware "incompati=
bility/bug"

> : I was able to reproduce this bug on more than 50 identical servers, =
but

> not on another farm of servers with a different hardware.

> Xen version, Debian Kernel was exactly the same on both farm.




Yes I think so.

The problem is where I use debian squeeze with xen 4.0.

In another server with the same hardware but with debian lenny and xen

3.0 I have no problems.

I've read that a workaround is to set clocksource=3Dpit on the xen boot=



line in the grub conf, I hope this works because I can't change h=
ardware.





--e89a8f23585f6dc74e04cad2ae5f--


--===============6031517816050720802==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
Xen-users mailing list
Xen-users@lists.xen.org
http://lists.xen.org/xen-users
--===============6031517816050720802==--


From xen-users-bounces@lists.xen.org Sun Sep 30 19:25:14 2012
Return-path: 
Envelope-to: archives@lists.xen.org
Delivery-date: Sun, 30 Sep 2012 19:25:14 +0000
Received: from localhost ([127.0.0.1] helo=lists.xen.org)
	by lists.xen.org with esmtp (Exim 4.72)
	(envelope-from )
	id 1TIP7F-0002Ph-0p; Sun, 30 Sep 2012 19:23:49 +0000
Received: from mail6.bemta4.messagelabs.com ([85.158.143.247])
	by lists.xen.org with esmtp (Exim 4.72)
	(envelope-from ) id 1TIP7D-0002PV-L3
	for xen-users@lists.xensource.com; Sun, 30 Sep 2012 19:23:47 +0000
Received: from [85.158.143.35:28224] by server-2.bemta-4.messagelabs.com id
	04/8A-06610-24C98605; Sun, 30 Sep 2012 19:23:46 +0000
X-Env-Sender: mrsanna1@gmail.com
X-Msg-Ref: server-3.tower-21.messagelabs.com!1349033024!14347235!1
X-Originating-IP: [209.85.220.171]
X-SpamReason: No, hits=0.3 required=7.0 tests=ML_RADAR_SPEW_LINKS_14,
	RCVD_BY_IP,spamassassin: 
X-StarScan-Received: 
X-StarScan-Version: 6.6.1.3; banners=-,-,-
X-VirusChecked: Checked
Received: (qmail 3107 invoked from network); 30 Sep 2012 19:23:45 -0000
Received: from mail-vc0-f171.google.com (HELO mail-vc0-f171.google.com)
	(209.85.220.171)
	by server-3.tower-21.messagelabs.com with RC4-SHA encrypted SMTP;
	30 Sep 2012 19:23:45 -0000
Received: by vcmm18 with SMTP id m18so6266401vcm.30
	for ; Sun, 30 Sep 2012 12:23:44 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;
	h=mime-version:in-reply-to:references:date:message-id:subject:from:to
	:cc:content-type:content-transfer-encoding;
	bh=S6DOuzPTttiLRHgSDA5DcR9zBsABjWntkdBwVQc0bG0=;
	b=AbkHOyIHzdwrTIKcbyl/9ME+NjEbcn3DEvWZhz/hIbuiS+Ss0VQWMfP0qvcZU425IQ
	RQk7RrSO9cF7c4r63VnU5wgbl2UmVPH3/OddcMkf0hNugU58jyJRQg52pQ/9hZuhG+A4
	ZNkQE8Hwbb6TLupVobtUBLqY8vdVJiV4UBq4jx0jHnaWBhZ/6kpkeb8ka6OoLjAvivbH
	eK/fWpAy/7/1E5f+l01+uYuMzArvOh3leXxBJaYT4lHRPqtT4KtJuqrdWvXtC69AHm/Q
	wu+oBZqnR/IfxQP4zdXBvwEk4YWe0v5lAeWACt0oaeY/++od0QOYZC32BpXpSQ9gS0WA
	0Weg==
MIME-Version: 1.0
Received: by 10.52.69.132 with SMTP id e4mr5884953vdu.2.1349033024424; Sun, 30
	Sep 2012 12:23:44 -0700 (PDT)
Received: by 10.58.207.75 with HTTP; Sun, 30 Sep 2012 12:23:44 -0700 (PDT)
In-Reply-To: <20120930151314.GU8912@reaktio.net>
References: 
	
	
	
	<65395f62-74e5-4910-b701-8df629c2ce3b@default>
	
	
	
	
	
	<20120930151314.GU8912@reaktio.net>
Date: Sun, 30 Sep 2012 21:23:44 +0200
Message-ID: 
From: Mauro 
To: =?UTF-8?B?UGFzaSBLw6Rya2vDpGluZW4=?= 
Cc: Dan Magenheimer , xen-devel@lists.xensource.com,
	Keir Fraser , Jeremy Fitzhardinge ,
	Olivier Hanesse ,
	Keir Fraser ,
	Xen Users ,
	Mark Adams 
Subject: Re: [Xen-users] [Xen-devel]  Re: Xen 4 TSC problems
X-BeenThere: xen-users@lists.xen.org
X-Mailman-Version: 2.1.13
Precedence: list
List-Id: Xen user discussion 
List-Unsubscribe: ,
	
List-Post: 
List-Help: 
List-Subscribe: ,
	
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
Sender: xen-users-bounces@lists.xen.org
Errors-To: xen-users-bounces@lists.xen.org

T24gMzAgU2VwdGVtYmVyIDIwMTIgMTc6MTMsIFBhc2kgS8Okcmtrw6RpbmVuIDxwYXNpa0Bpa2ku
Zmk+IHdyb3RlOgo+IE9uIFNhdCwgU2VwIDI5LCAyMDEyIGF0IDAyOjE5OjU1UE0gKzAyMDAsIE1h
dXJvIHdyb3RlOgo+PiBJdCdzIGhhcHBlbmVkIGFub3RoZXIgdGltZSwgc3lzdGVtIGRhdGUgNTAg
bWludXRlcyBhaGVhZC4KPj4gVGhlcmUgaXMgcmVhbGx5IG5vIHNvbHV0aW9uPwo+Pgo+Cj4gVHJ5
IHdpdGggYSByZWNlbnQgWGVuIGh5cGVydmlzb3IgdmVyc2lvbi4gWGVuIDQuMS4zIG9yIDQuMi4w
Lgo+IEl0IGhlbHBzIGEgbG90IHRvIGtub3cgaWYgdGhlIGlzc3VlIGlzIHN0aWxsIGluIHRoZSBs
YXRlc3QgaHlwZXJ2aXNvciB2ZXJzaW9ucyBvciBub3QuCgpJJ20gdXNpbmcgZGViaWFuIHNxdWVl
emUgeGVuIGtlcm5lbCBhbmQgdGhpcyBrZXJuZWwgaGFzIHhlbiA0LjAuCgpfX19fX19fX19fX19f
X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fXwpYZW4tdXNlcnMgbWFpbGluZyBsaXN0
Clhlbi11c2Vyc0BsaXN0cy54ZW4ub3JnCmh0dHA6Ly9saXN0cy54ZW4ub3JnL3hlbi11c2Vycw==

From xen-users-bounces@lists.xen.org Sun Sep 30 19:25:14 2012
Return-path: 
Envelope-to: archives@lists.xen.org
Delivery-date: Sun, 30 Sep 2012 19:25:14 +0000
Received: from localhost ([127.0.0.1] helo=lists.xen.org)
	by lists.xen.org with esmtp (Exim 4.72)
	(envelope-from )
	id 1TIP7F-0002Ph-0p; Sun, 30 Sep 2012 19:23:49 +0000
Received: from mail6.bemta4.messagelabs.com ([85.158.143.247])
	by lists.xen.org with esmtp (Exim 4.72)
	(envelope-from ) id 1TIP7D-0002PV-L3
	for xen-users@lists.xensource.com; Sun, 30 Sep 2012 19:23:47 +0000
Received: from [85.158.143.35:28224] by server-2.bemta-4.messagelabs.com id
	04/8A-06610-24C98605; Sun, 30 Sep 2012 19:23:46 +0000
X-Env-Sender: mrsanna1@gmail.com
X-Msg-Ref: server-3.tower-21.messagelabs.com!1349033024!14347235!1
X-Originating-IP: [209.85.220.171]
X-SpamReason: No, hits=0.3 required=7.0 tests=ML_RADAR_SPEW_LINKS_14,
	RCVD_BY_IP,spamassassin: 
X-StarScan-Received: 
X-StarScan-Version: 6.6.1.3; banners=-,-,-
X-VirusChecked: Checked
Received: (qmail 3107 invoked from network); 30 Sep 2012 19:23:45 -0000
Received: from mail-vc0-f171.google.com (HELO mail-vc0-f171.google.com)
	(209.85.220.171)
	by server-3.tower-21.messagelabs.com with RC4-SHA encrypted SMTP;
	30 Sep 2012 19:23:45 -0000
Received: by vcmm18 with SMTP id m18so6266401vcm.30
	for ; Sun, 30 Sep 2012 12:23:44 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;
	h=mime-version:in-reply-to:references:date:message-id:subject:from:to
	:cc:content-type:content-transfer-encoding;
	bh=S6DOuzPTttiLRHgSDA5DcR9zBsABjWntkdBwVQc0bG0=;
	b=AbkHOyIHzdwrTIKcbyl/9ME+NjEbcn3DEvWZhz/hIbuiS+Ss0VQWMfP0qvcZU425IQ
	RQk7RrSO9cF7c4r63VnU5wgbl2UmVPH3/OddcMkf0hNugU58jyJRQg52pQ/9hZuhG+A4
	ZNkQE8Hwbb6TLupVobtUBLqY8vdVJiV4UBq4jx0jHnaWBhZ/6kpkeb8ka6OoLjAvivbH
	eK/fWpAy/7/1E5f+l01+uYuMzArvOh3leXxBJaYT4lHRPqtT4KtJuqrdWvXtC69AHm/Q
	wu+oBZqnR/IfxQP4zdXBvwEk4YWe0v5lAeWACt0oaeY/++od0QOYZC32BpXpSQ9gS0WA
	0Weg==
MIME-Version: 1.0
Received: by 10.52.69.132 with SMTP id e4mr5884953vdu.2.1349033024424; Sun, 30
	Sep 2012 12:23:44 -0700 (PDT)
Received: by 10.58.207.75 with HTTP; Sun, 30 Sep 2012 12:23:44 -0700 (PDT)
In-Reply-To: <20120930151314.GU8912@reaktio.net>
References: 
	
	
	
	<65395f62-74e5-4910-b701-8df629c2ce3b@default>
	
	
	
	
	
	<20120930151314.GU8912@reaktio.net>
Date: Sun, 30 Sep 2012 21:23:44 +0200
Message-ID: 
From: Mauro 
To: =?UTF-8?B?UGFzaSBLw6Rya2vDpGluZW4=?= 
Cc: Dan Magenheimer , xen-devel@lists.xensource.com,
	Keir Fraser , Jeremy Fitzhardinge ,
	Olivier Hanesse ,
	Keir Fraser ,
	Xen Users ,
	Mark Adams 
Subject: Re: [Xen-users] [Xen-devel]  Re: Xen 4 TSC problems
X-BeenThere: xen-users@lists.xen.org
X-Mailman-Version: 2.1.13
Precedence: list
List-Id: Xen user discussion 
List-Unsubscribe: ,
	
List-Post: 
List-Help: 
List-Subscribe: ,
	
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
Sender: xen-users-bounces@lists.xen.org
Errors-To: xen-users-bounces@lists.xen.org

T24gMzAgU2VwdGVtYmVyIDIwMTIgMTc6MTMsIFBhc2kgS8Okcmtrw6RpbmVuIDxwYXNpa0Bpa2ku
Zmk+IHdyb3RlOgo+IE9uIFNhdCwgU2VwIDI5LCAyMDEyIGF0IDAyOjE5OjU1UE0gKzAyMDAsIE1h
dXJvIHdyb3RlOgo+PiBJdCdzIGhhcHBlbmVkIGFub3RoZXIgdGltZSwgc3lzdGVtIGRhdGUgNTAg
bWludXRlcyBhaGVhZC4KPj4gVGhlcmUgaXMgcmVhbGx5IG5vIHNvbHV0aW9uPwo+Pgo+Cj4gVHJ5
IHdpdGggYSByZWNlbnQgWGVuIGh5cGVydmlzb3IgdmVyc2lvbi4gWGVuIDQuMS4zIG9yIDQuMi4w
Lgo+IEl0IGhlbHBzIGEgbG90IHRvIGtub3cgaWYgdGhlIGlzc3VlIGlzIHN0aWxsIGluIHRoZSBs
YXRlc3QgaHlwZXJ2aXNvciB2ZXJzaW9ucyBvciBub3QuCgpJJ20gdXNpbmcgZGViaWFuIHNxdWVl
emUgeGVuIGtlcm5lbCBhbmQgdGhpcyBrZXJuZWwgaGFzIHhlbiA0LjAuCgpfX19fX19fX19fX19f
X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fXwpYZW4tdXNlcnMgbWFpbGluZyBsaXN0
Clhlbi11c2Vyc0BsaXN0cy54ZW4ub3JnCmh0dHA6Ly9saXN0cy54ZW4ub3JnL3hlbi11c2Vycw==

From xen-users-bounces@lists.xen.org Sun Sep 30 20:15:09 2012
Return-path: 
Envelope-to: archives@lists.xen.org
Delivery-date: Sun, 30 Sep 2012 20:15:09 +0000
Received: from localhost ([127.0.0.1] helo=lists.xen.org)
	by lists.xen.org with esmtp (Exim 4.72)
	(envelope-from )
	id 1TIPtn-00039v-7t; Sun, 30 Sep 2012 20:13:59 +0000
Received: from mail6.bemta5.messagelabs.com ([195.245.231.135])
	by lists.xen.org with esmtp (Exim 4.72)
	(envelope-from ) id 1TIPtl-00039q-Hn
	for xen-users@lists.xen.org; Sun, 30 Sep 2012 20:13:57 +0000
Received: from [85.158.139.211:20968] by server-15.bemta-5.messagelabs.com id
	26/94-19430-408A8605; Sun, 30 Sep 2012 20:13:56 +0000
X-Env-Sender: mrsanna1@gmail.com
X-Msg-Ref: server-16.tower-206.messagelabs.com!1349036035!20548921!1
X-Originating-IP: [209.85.212.45]
X-SpamReason: No, hits=0.3 required=7.0 tests=ML_RADAR_SPEW_LINKS_14,
	RCVD_BY_IP,spamassassin: 
X-StarScan-Received: 
X-StarScan-Version: 6.6.1.3; banners=-,-,-
X-VirusChecked: Checked
Received: (qmail 32181 invoked from network); 30 Sep 2012 20:13:56 -0000
Received: from mail-vb0-f45.google.com (HELO mail-vb0-f45.google.com)
	(209.85.212.45)
	by server-16.tower-206.messagelabs.com with RC4-SHA encrypted SMTP;
	30 Sep 2012 20:13:56 -0000
Received: by vbip1 with SMTP id p1so5811737vbi.32
	for ; Sun, 30 Sep 2012 13:13:55 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;
	h=mime-version:in-reply-to:references:date:message-id:subject:from:to
	:cc:content-type;
	bh=mODFH3HnWHCeOKHjK9IzNWPYiRUlNF7v/C4ZkOFOHsg=;
	b=kEQnH8L+Y7NIbNN7rDUdtYeSqgrEf0stVb++n7sYmvZ2BsC0Tpo9wNawN+XCF7NfAX
	MtCPt8nrIungJf4ELHbJ9A70HCmxliHFbZ0RuyHdgVloG6+gdgGK6LkGCs9hd/fcTZQh
	UDulfHX6wDK+uLLIqObChC0XTqvVJ8lthk3YIWoUCx1UU2S4dFq4TBUrPo4PdCQWoAQX
	b+T5WMbGpHs0Ba5c1dIXcA4JY3DdD3d58xZ7FjzyTbc1cSCIY9BV8lCGZVM41icneGal
	WpgrqP+x6/o1grhIx4RW4wKcKLHDobZO7H2VXD8MqoaaJlvH53RlOi3LKiUpBEnTkWIy
	pUnQ==
MIME-Version: 1.0
Received: by 10.52.36.34 with SMTP id n2mr5914869vdj.105.1349036034875; Sun,
	30 Sep 2012 13:13:54 -0700 (PDT)
Received: by 10.58.207.75 with HTTP; Sun, 30 Sep 2012 13:13:54 -0700 (PDT)
In-Reply-To: <503BB696.3030603@pa.metrocast.net>
References: 
	<503BB696.3030603@pa.metrocast.net>
Date: Sun, 30 Sep 2012 22:13:54 +0200
Message-ID: 
From: Mauro 
To: sdawson@pa.metrocast.net
Cc: xen-users@lists.xen.org
Subject: Re: [Xen-users] Clock problems on Squeeze/Xen4 (clock jumps 50
 minutes ahead)
X-BeenThere: xen-users@lists.xen.org
X-Mailman-Version: 2.1.13
Precedence: list
List-Id: Xen user discussion 
List-Unsubscribe: ,
	
List-Post: 
List-Help: 
List-Subscribe: ,
	
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: xen-users-bounces@lists.xen.org
Errors-To: xen-users-bounces@lists.xen.org

On 27 August 2012 20:04, Steve Dawson  wrote:

> We had this problem too, from what we could tell it was a hardware issue on some of our servers, specifically HP DL380 G5 servers, we have G6's and G7's as well, they don't seem to be affected.
>
> The fix was to boot the G5 servers with clocksource=pit and cpuidle=0 on the xen command line. Example grub 1 entry below. Maybe the cpuidle switch is needed too.
>
> title Xen-4.1.1
>        root (hd0,0)
>        kernel /boot/xen-4.1.1.gz dom0_mem=2048M dom0_max_vcpus=1 dom0_vcpus_pin clocksource=pit cpuidle=0
>        module /boot/vmlinuz-2.6.32.41 ro root=/dev/cciss/c0d0p1 max_loop=32

Hello, I have exactly the same problem on two HP Proliant DL580 G5
servers with debian squeeze.
It's very very annoying and I am also angry for this bug.
Is it a xen bug or a hardware problem?
I've tried clocksource=pit but I've not resolved.
Have you solved adding cpuidle=0?

_______________________________________________
Xen-users mailing list
Xen-users@lists.xen.org
http://lists.xen.org/xen-users

From xen-users-bounces@lists.xen.org Sun Sep 30 20:15:09 2012
Return-path: 
Envelope-to: archives@lists.xen.org
Delivery-date: Sun, 30 Sep 2012 20:15:09 +0000
Received: from localhost ([127.0.0.1] helo=lists.xen.org)
	by lists.xen.org with esmtp (Exim 4.72)
	(envelope-from )
	id 1TIPtn-00039v-7t; Sun, 30 Sep 2012 20:13:59 +0000
Received: from mail6.bemta5.messagelabs.com ([195.245.231.135])
	by lists.xen.org with esmtp (Exim 4.72)
	(envelope-from ) id 1TIPtl-00039q-Hn
	for xen-users@lists.xen.org; Sun, 30 Sep 2012 20:13:57 +0000
Received: from [85.158.139.211:20968] by server-15.bemta-5.messagelabs.com id
	26/94-19430-408A8605; Sun, 30 Sep 2012 20:13:56 +0000
X-Env-Sender: mrsanna1@gmail.com
X-Msg-Ref: server-16.tower-206.messagelabs.com!1349036035!20548921!1
X-Originating-IP: [209.85.212.45]
X-SpamReason: No, hits=0.3 required=7.0 tests=ML_RADAR_SPEW_LINKS_14,
	RCVD_BY_IP,spamassassin: 
X-StarScan-Received: 
X-StarScan-Version: 6.6.1.3; banners=-,-,-
X-VirusChecked: Checked
Received: (qmail 32181 invoked from network); 30 Sep 2012 20:13:56 -0000
Received: from mail-vb0-f45.google.com (HELO mail-vb0-f45.google.com)
	(209.85.212.45)
	by server-16.tower-206.messagelabs.com with RC4-SHA encrypted SMTP;
	30 Sep 2012 20:13:56 -0000
Received: by vbip1 with SMTP id p1so5811737vbi.32
	for ; Sun, 30 Sep 2012 13:13:55 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;
	h=mime-version:in-reply-to:references:date:message-id:subject:from:to
	:cc:content-type;
	bh=mODFH3HnWHCeOKHjK9IzNWPYiRUlNF7v/C4ZkOFOHsg=;
	b=kEQnH8L+Y7NIbNN7rDUdtYeSqgrEf0stVb++n7sYmvZ2BsC0Tpo9wNawN+XCF7NfAX
	MtCPt8nrIungJf4ELHbJ9A70HCmxliHFbZ0RuyHdgVloG6+gdgGK6LkGCs9hd/fcTZQh
	UDulfHX6wDK+uLLIqObChC0XTqvVJ8lthk3YIWoUCx1UU2S4dFq4TBUrPo4PdCQWoAQX
	b+T5WMbGpHs0Ba5c1dIXcA4JY3DdD3d58xZ7FjzyTbc1cSCIY9BV8lCGZVM41icneGal
	WpgrqP+x6/o1grhIx4RW4wKcKLHDobZO7H2VXD8MqoaaJlvH53RlOi3LKiUpBEnTkWIy
	pUnQ==
MIME-Version: 1.0
Received: by 10.52.36.34 with SMTP id n2mr5914869vdj.105.1349036034875; Sun,
	30 Sep 2012 13:13:54 -0700 (PDT)
Received: by 10.58.207.75 with HTTP; Sun, 30 Sep 2012 13:13:54 -0700 (PDT)
In-Reply-To: <503BB696.3030603@pa.metrocast.net>
References: 
	<503BB696.3030603@pa.metrocast.net>
Date: Sun, 30 Sep 2012 22:13:54 +0200
Message-ID: 
From: Mauro 
To: sdawson@pa.metrocast.net
Cc: xen-users@lists.xen.org
Subject: Re: [Xen-users] Clock problems on Squeeze/Xen4 (clock jumps 50
 minutes ahead)
X-BeenThere: xen-users@lists.xen.org
X-Mailman-Version: 2.1.13
Precedence: list
List-Id: Xen user discussion 
List-Unsubscribe: ,
	
List-Post: 
List-Help: 
List-Subscribe: ,
	
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: xen-users-bounces@lists.xen.org
Errors-To: xen-users-bounces@lists.xen.org

On 27 August 2012 20:04, Steve Dawson  wrote:

> We had this problem too, from what we could tell it was a hardware issue on some of our servers, specifically HP DL380 G5 servers, we have G6's and G7's as well, they don't seem to be affected.
>
> The fix was to boot the G5 servers with clocksource=pit and cpuidle=0 on the xen command line. Example grub 1 entry below. Maybe the cpuidle switch is needed too.
>
> title Xen-4.1.1
>        root (hd0,0)
>        kernel /boot/xen-4.1.1.gz dom0_mem=2048M dom0_max_vcpus=1 dom0_vcpus_pin clocksource=pit cpuidle=0
>        module /boot/vmlinuz-2.6.32.41 ro root=/dev/cciss/c0d0p1 max_loop=32

Hello, I have exactly the same problem on two HP Proliant DL580 G5
servers with debian squeeze.
It's very very annoying and I am also angry for this bug.
Is it a xen bug or a hardware problem?
I've tried clocksource=pit but I've not resolved.
Have you solved adding cpuidle=0?

_______________________________________________
Xen-users mailing list
Xen-users@lists.xen.org
http://lists.xen.org/xen-users

From xen-users-bounces@lists.xen.org Sun Sep 30 20:18:32 2012
Return-path: 
Envelope-to: archives@lists.xen.org
Delivery-date: Sun, 30 Sep 2012 20:18:32 +0000
Received: from localhost ([127.0.0.1] helo=lists.xen.org)
	by lists.xen.org with esmtp (Exim 4.72)
	(envelope-from )
	id 1TIPx9-0003Jy-3R; Sun, 30 Sep 2012 20:17:27 +0000
Received: from mail27.messagelabs.com ([193.109.254.147])
	by lists.xen.org with smtp (Exim 4.72)
	(envelope-from ) id 1TIPx7-0003Jr-48
	for xen-users@lists.xen.org; Sun, 30 Sep 2012 20:17:25 +0000
X-Env-Sender: reklov@unitedklasens.de
X-Msg-Ref: server-15.tower-27.messagelabs.com!1349036235!5945024!1
X-Originating-IP: [37.17.224.13]
X-SpamReason: No, hits=0.0 required=7.0 tests=ML_RADAR_SPEW_LINKS_23,
	spamassassin: 
X-StarScan-Received: 
X-StarScan-Version: 6.6.1.3; banners=-,-,-
X-VirusChecked: Checked
Received: (qmail 14228 invoked from network); 30 Sep 2012 20:17:15 -0000
Received: from webgo24-server13.de (HELO webgo24-server13.de) (37.17.224.13)
	by server-15.tower-27.messagelabs.com with SMTP;
	30 Sep 2012 20:17:15 -0000
Received: from [192.168.42.13] (HSI-KBW-091-089-000-078.hsi2.kabelbw.de
	[91.89.0.78])
	by webgo24-server13.de (Postfix) with ESMTPSA id 0BB7B304019D;
	Sun, 30 Sep 2012 22:17:15 +0200 (CEST)
Message-ID: <5068A8CA.2030402@unitedklasens.de>
Date: Sun, 30 Sep 2012 22:17:14 +0200
From: Volker Klasen 
User-Agent: Mozilla/5.0 (X11; Linux x86_64;
	rv:10.0.7) Gecko/20120922 Icedove/10.0.7
MIME-Version: 1.0
To: karim@robotstampede.com
References: 
In-Reply-To: 
X-Enigmail-Version: 1.4.1
Cc: xen-users@lists.xen.org
Subject: Re: [Xen-users] Xen linux and gaming box
X-BeenThere: xen-users@lists.xen.org
X-Mailman-Version: 2.1.13
Precedence: list
List-Id: Xen user discussion 
List-Unsubscribe: ,
	
List-Post: 
List-Help: 
List-Subscribe: ,
	
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: xen-users-bounces@lists.xen.org
Errors-To: xen-users-bounces@lists.xen.org

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hi Karim,

> Goal: Run any Ubuntu derivative off an intel i5 video card and play
> Windows 7 games on an Nvidia gtx 570 through vga pass through.  Use
> a simple dvi toggle switch on the monitor (2 inputs) to go between
> them.

I have (almost) the same setup running, only using 2 monitors and an
AMD graphics.

As much was already said, I'll only go into one of your points:

> 4) Is it required to pass through a usb bus with a 2nd
> keyboard/mouse or kvm switch? Or Can I just share the keyboard
> mouse?  If I do need a kvm switch, will any of them work or is
> there an approved list (couldn't find any). Little unclear on how
> to switch between DomU instances (that what cntrl-] does?)

I do have USB ports passed through, however, I don't use them for
Keyboard/Mouse and currently (kernel 3.5) usb passthrough doesn't work.

To control my Windows VM I use synergy (server on linux, client on
windows). I only need one Keyboard/Mouse and everything works, I can
play as well as in native Windows. It might not be the optimal setup
when you only have one monitor, but it might be worth a shot.

Cheers,
Volker
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.12 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iEYEARECAAYFAlBoqMoACgkQgKD4KXUzSrhHigCfSC/ZtGvqamL/K/rGHpAlwINx
VLQAoIUwt6xRG/PXT5dMrStObfLqQY+R
=UoYI
-----END PGP SIGNATURE-----

_______________________________________________
Xen-users mailing list
Xen-users@lists.xen.org
http://lists.xen.org/xen-users

From xen-users-bounces@lists.xen.org Sun Sep 30 20:18:32 2012
Return-path: 
Envelope-to: archives@lists.xen.org
Delivery-date: Sun, 30 Sep 2012 20:18:32 +0000
Received: from localhost ([127.0.0.1] helo=lists.xen.org)
	by lists.xen.org with esmtp (Exim 4.72)
	(envelope-from )
	id 1TIPx9-0003Jy-3R; Sun, 30 Sep 2012 20:17:27 +0000
Received: from mail27.messagelabs.com ([193.109.254.147])
	by lists.xen.org with smtp (Exim 4.72)
	(envelope-from ) id 1TIPx7-0003Jr-48
	for xen-users@lists.xen.org; Sun, 30 Sep 2012 20:17:25 +0000
X-Env-Sender: reklov@unitedklasens.de
X-Msg-Ref: server-15.tower-27.messagelabs.com!1349036235!5945024!1
X-Originating-IP: [37.17.224.13]
X-SpamReason: No, hits=0.0 required=7.0 tests=ML_RADAR_SPEW_LINKS_23,
	spamassassin: 
X-StarScan-Received: 
X-StarScan-Version: 6.6.1.3; banners=-,-,-
X-VirusChecked: Checked
Received: (qmail 14228 invoked from network); 30 Sep 2012 20:17:15 -0000
Received: from webgo24-server13.de (HELO webgo24-server13.de) (37.17.224.13)
	by server-15.tower-27.messagelabs.com with SMTP;
	30 Sep 2012 20:17:15 -0000
Received: from [192.168.42.13] (HSI-KBW-091-089-000-078.hsi2.kabelbw.de
	[91.89.0.78])
	by webgo24-server13.de (Postfix) with ESMTPSA id 0BB7B304019D;
	Sun, 30 Sep 2012 22:17:15 +0200 (CEST)
Message-ID: <5068A8CA.2030402@unitedklasens.de>
Date: Sun, 30 Sep 2012 22:17:14 +0200
From: Volker Klasen 
User-Agent: Mozilla/5.0 (X11; Linux x86_64;
	rv:10.0.7) Gecko/20120922 Icedove/10.0.7
MIME-Version: 1.0
To: karim@robotstampede.com
References: 
In-Reply-To: 
X-Enigmail-Version: 1.4.1
Cc: xen-users@lists.xen.org
Subject: Re: [Xen-users] Xen linux and gaming box
X-BeenThere: xen-users@lists.xen.org
X-Mailman-Version: 2.1.13
Precedence: list
List-Id: Xen user discussion 
List-Unsubscribe: ,
	
List-Post: 
List-Help: 
List-Subscribe: ,
	
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: xen-users-bounces@lists.xen.org
Errors-To: xen-users-bounces@lists.xen.org

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hi Karim,

> Goal: Run any Ubuntu derivative off an intel i5 video card and play
> Windows 7 games on an Nvidia gtx 570 through vga pass through.  Use
> a simple dvi toggle switch on the monitor (2 inputs) to go between
> them.

I have (almost) the same setup running, only using 2 monitors and an
AMD graphics.

As much was already said, I'll only go into one of your points:

> 4) Is it required to pass through a usb bus with a 2nd
> keyboard/mouse or kvm switch? Or Can I just share the keyboard
> mouse?  If I do need a kvm switch, will any of them work or is
> there an approved list (couldn't find any). Little unclear on how
> to switch between DomU instances (that what cntrl-] does?)

I do have USB ports passed through, however, I don't use them for
Keyboard/Mouse and currently (kernel 3.5) usb passthrough doesn't work.

To control my Windows VM I use synergy (server on linux, client on
windows). I only need one Keyboard/Mouse and everything works, I can
play as well as in native Windows. It might not be the optimal setup
when you only have one monitor, but it might be worth a shot.

Cheers,
Volker
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.12 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iEYEARECAAYFAlBoqMoACgkQgKD4KXUzSrhHigCfSC/ZtGvqamL/K/rGHpAlwINx
VLQAoIUwt6xRG/PXT5dMrStObfLqQY+R
=UoYI
-----END PGP SIGNATURE-----

_______________________________________________
Xen-users mailing list
Xen-users@lists.xen.org
http://lists.xen.org/xen-users

From xen-users-bounces@lists.xen.org Sun Sep 30 20:20:17 2012
Return-path: 
Envelope-to: archives@lists.xen.org
Delivery-date: Sun, 30 Sep 2012 20:20:17 +0000
Received: from localhost ([127.0.0.1] helo=lists.xen.org)
	by lists.xen.org with esmtp (Exim 4.72)
	(envelope-from )
	id 1TIPz9-0003Zv-9S; Sun, 30 Sep 2012 20:19:31 +0000
Received: from mail27.messagelabs.com ([193.109.254.147])
	by lists.xen.org with esmtp (Exim 4.72)
	(envelope-from )
	id 1TIPz8-0003Z5-60; Sun, 30 Sep 2012 20:19:30 +0000
X-Env-Sender: mrsanna1@gmail.com
X-Msg-Ref: server-11.tower-27.messagelabs.com!1349036362!3621780!1
X-Originating-IP: [209.85.220.171]
X-SpamReason: No, hits=0.3 required=7.0 tests=ML_RADAR_SPEW_LINKS_14,
	RCVD_BY_IP,spamassassin: 
X-StarScan-Received: 
X-StarScan-Version: 6.6.1.3; banners=-,-,-
X-VirusChecked: Checked
Received: (qmail 12868 invoked from network); 30 Sep 2012 20:19:24 -0000
Received: from mail-vc0-f171.google.com (HELO mail-vc0-f171.google.com)
	(209.85.220.171)
	by server-11.tower-27.messagelabs.com with RC4-SHA encrypted SMTP;
	30 Sep 2012 20:19:24 -0000
Received: by vcmm18 with SMTP id m18so6296425vcm.30
	for ; Sun, 30 Sep 2012 13:19:22 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;
	h=mime-version:in-reply-to:references:date:message-id:subject:from:to
	:cc:content-type:content-transfer-encoding;
	bh=k80c23drYPmwBIfSbIkRjgxIW66HCVjzI/F9pIYGq50=;
	b=Wr+bt7z1LnUsSNJO7WkIbvGclf+xa/NiKPBg6bkUwH/S+N5dIH5BPBsIMvUE8YGPyt
	M40+T8Y3J2huKYakByP/SnuOkflaK+dNEAq1grwnCj03Cf0kHOQFpEcsMuszDZQvmap9
	eH/cQBCOKNzZ8VJzybD9GtKfuq1XpAQ8K5vX4tF+VeB8qd4SbbywRUpeUeaRMlfcUjmb
	C1UqzV/EJU4A5eL0BhlMJ8EtW+pUmuQmxuAlCN49e5LVf0Me4qHB63ECYOo1VCbNfF9R
	BGY3t8dJoqh78SK7oAgMm11aUgKFS6RdCE/ilcZX4RBWbPlkk1ICEVXilqE3mf/ZnRNR
	ut+A==
MIME-Version: 1.0
Received: by 10.52.93.238 with SMTP id cx14mr337653vdb.42.1349036362646; Sun,
	30 Sep 2012 13:19:22 -0700 (PDT)
Received: by 10.58.207.75 with HTTP; Sun, 30 Sep 2012 13:19:22 -0700 (PDT)
In-Reply-To: 
References: 
	
	
	
	<65395f62-74e5-4910-b701-8df629c2ce3b@default>
	
	
	
	
	
	<20120930151314.GU8912@reaktio.net>
	
Date: Sun, 30 Sep 2012 22:19:22 +0200
Message-ID: 
From: Mauro 
To: =?UTF-8?B?UGFzaSBLw6Rya2vDpGluZW4=?= 
Cc: Dan Magenheimer , xen-devel@lists.xensource.com,
	Keir Fraser , Jeremy Fitzhardinge ,
	Olivier Hanesse ,
	Keir Fraser ,
	Xen Users ,
	Mark Adams 
Subject: Re: [Xen-users] [Xen-devel]  Re: Xen 4 TSC problems
X-BeenThere: xen-users@lists.xen.org
X-Mailman-Version: 2.1.13
Precedence: list
List-Id: Xen user discussion 
List-Unsubscribe: ,
	
List-Post: 
List-Help: 
List-Subscribe: ,
	
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
Sender: xen-users-bounces@lists.xen.org
Errors-To: xen-users-bounces@lists.xen.org

T24gMzAgU2VwdGVtYmVyIDIwMTIgMjE6MjMsIE1hdXJvIDxtcnNhbm5hMUBnbWFpbC5jb20+IHdy
b3RlOgo+IE9uIDMwIFNlcHRlbWJlciAyMDEyIDE3OjEzLCBQYXNpIEvDpHJra8OkaW5lbiA8cGFz
aWtAaWtpLmZpPiB3cm90ZToKPj4gT24gU2F0LCBTZXAgMjksIDIwMTIgYXQgMDI6MTk6NTVQTSAr
MDIwMCwgTWF1cm8gd3JvdGU6Cj4+PiBJdCdzIGhhcHBlbmVkIGFub3RoZXIgdGltZSwgc3lzdGVt
IGRhdGUgNTAgbWludXRlcyBhaGVhZC4KPj4+IFRoZXJlIGlzIHJlYWxseSBubyBzb2x1dGlvbj8K
Pj4+Cj4+Cj4+IFRyeSB3aXRoIGEgcmVjZW50IFhlbiBoeXBlcnZpc29yIHZlcnNpb24uIFhlbiA0
LjEuMyBvciA0LjIuMC4KPj4gSXQgaGVscHMgYSBsb3QgdG8ga25vdyBpZiB0aGUgaXNzdWUgaXMg
c3RpbGwgaW4gdGhlIGxhdGVzdCBoeXBlcnZpc29yIHZlcnNpb25zIG9yIG5vdC4KClRoZXJlIGlz
IHNvbWVvbmUgdGhhdCBoYWQgdGhlIHByb2JsZW0gYW5kIHNvbHZlZCB1c2luZyBhIHJlY2VudCB4
ZW4gaHlwZXJ2aXNvcj8KCl9fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19f
X19fX19fClhlbi11c2VycyBtYWlsaW5nIGxpc3QKWGVuLXVzZXJzQGxpc3RzLnhlbi5vcmcKaHR0
cDovL2xpc3RzLnhlbi5vcmcveGVuLXVzZXJz

From xen-users-bounces@lists.xen.org Sun Sep 30 20:20:17 2012
Return-path: 
Envelope-to: archives@lists.xen.org
Delivery-date: Sun, 30 Sep 2012 20:20:17 +0000
Received: from localhost ([127.0.0.1] helo=lists.xen.org)
	by lists.xen.org with esmtp (Exim 4.72)
	(envelope-from )
	id 1TIPz9-0003Zv-9S; Sun, 30 Sep 2012 20:19:31 +0000
Received: from mail27.messagelabs.com ([193.109.254.147])
	by lists.xen.org with esmtp (Exim 4.72)
	(envelope-from )
	id 1TIPz8-0003Z5-60; Sun, 30 Sep 2012 20:19:30 +0000
X-Env-Sender: mrsanna1@gmail.com
X-Msg-Ref: server-11.tower-27.messagelabs.com!1349036362!3621780!1
X-Originating-IP: [209.85.220.171]
X-SpamReason: No, hits=0.3 required=7.0 tests=ML_RADAR_SPEW_LINKS_14,
	RCVD_BY_IP,spamassassin: 
X-StarScan-Received: 
X-StarScan-Version: 6.6.1.3; banners=-,-,-
X-VirusChecked: Checked
Received: (qmail 12868 invoked from network); 30 Sep 2012 20:19:24 -0000
Received: from mail-vc0-f171.google.com (HELO mail-vc0-f171.google.com)
	(209.85.220.171)
	by server-11.tower-27.messagelabs.com with RC4-SHA encrypted SMTP;
	30 Sep 2012 20:19:24 -0000
Received: by vcmm18 with SMTP id m18so6296425vcm.30
	for ; Sun, 30 Sep 2012 13:19:22 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;
	h=mime-version:in-reply-to:references:date:message-id:subject:from:to
	:cc:content-type:content-transfer-encoding;
	bh=k80c23drYPmwBIfSbIkRjgxIW66HCVjzI/F9pIYGq50=;
	b=Wr+bt7z1LnUsSNJO7WkIbvGclf+xa/NiKPBg6bkUwH/S+N5dIH5BPBsIMvUE8YGPyt
	M40+T8Y3J2huKYakByP/SnuOkflaK+dNEAq1grwnCj03Cf0kHOQFpEcsMuszDZQvmap9
	eH/cQBCOKNzZ8VJzybD9GtKfuq1XpAQ8K5vX4tF+VeB8qd4SbbywRUpeUeaRMlfcUjmb
	C1UqzV/EJU4A5eL0BhlMJ8EtW+pUmuQmxuAlCN49e5LVf0Me4qHB63ECYOo1VCbNfF9R
	BGY3t8dJoqh78SK7oAgMm11aUgKFS6RdCE/ilcZX4RBWbPlkk1ICEVXilqE3mf/ZnRNR
	ut+A==
MIME-Version: 1.0
Received: by 10.52.93.238 with SMTP id cx14mr337653vdb.42.1349036362646; Sun,
	30 Sep 2012 13:19:22 -0700 (PDT)
Received: by 10.58.207.75 with HTTP; Sun, 30 Sep 2012 13:19:22 -0700 (PDT)
In-Reply-To: 
References: 
	
	
	
	<65395f62-74e5-4910-b701-8df629c2ce3b@default>
	
	
	
	
	
	<20120930151314.GU8912@reaktio.net>
	
Date: Sun, 30 Sep 2012 22:19:22 +0200
Message-ID: 
From: Mauro 
To: =?UTF-8?B?UGFzaSBLw6Rya2vDpGluZW4=?= 
Cc: Dan Magenheimer , xen-devel@lists.xensource.com,
	Keir Fraser , Jeremy Fitzhardinge ,
	Olivier Hanesse ,
	Keir Fraser ,
	Xen Users ,
	Mark Adams 
Subject: Re: [Xen-users] [Xen-devel]  Re: Xen 4 TSC problems
X-BeenThere: xen-users@lists.xen.org
X-Mailman-Version: 2.1.13
Precedence: list
List-Id: Xen user discussion 
List-Unsubscribe: ,
	
List-Post: 
List-Help: 
List-Subscribe: ,
	
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
Sender: xen-users-bounces@lists.xen.org
Errors-To: xen-users-bounces@lists.xen.org

T24gMzAgU2VwdGVtYmVyIDIwMTIgMjE6MjMsIE1hdXJvIDxtcnNhbm5hMUBnbWFpbC5jb20+IHdy
b3RlOgo+IE9uIDMwIFNlcHRlbWJlciAyMDEyIDE3OjEzLCBQYXNpIEvDpHJra8OkaW5lbiA8cGFz
aWtAaWtpLmZpPiB3cm90ZToKPj4gT24gU2F0LCBTZXAgMjksIDIwMTIgYXQgMDI6MTk6NTVQTSAr
MDIwMCwgTWF1cm8gd3JvdGU6Cj4+PiBJdCdzIGhhcHBlbmVkIGFub3RoZXIgdGltZSwgc3lzdGVt
IGRhdGUgNTAgbWludXRlcyBhaGVhZC4KPj4+IFRoZXJlIGlzIHJlYWxseSBubyBzb2x1dGlvbj8K
Pj4+Cj4+Cj4+IFRyeSB3aXRoIGEgcmVjZW50IFhlbiBoeXBlcnZpc29yIHZlcnNpb24uIFhlbiA0
LjEuMyBvciA0LjIuMC4KPj4gSXQgaGVscHMgYSBsb3QgdG8ga25vdyBpZiB0aGUgaXNzdWUgaXMg
c3RpbGwgaW4gdGhlIGxhdGVzdCBoeXBlcnZpc29yIHZlcnNpb25zIG9yIG5vdC4KClRoZXJlIGlz
IHNvbWVvbmUgdGhhdCBoYWQgdGhlIHByb2JsZW0gYW5kIHNvbHZlZCB1c2luZyBhIHJlY2VudCB4
ZW4gaHlwZXJ2aXNvcj8KCl9fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19f
X19fX19fClhlbi11c2VycyBtYWlsaW5nIGxpc3QKWGVuLXVzZXJzQGxpc3RzLnhlbi5vcmcKaHR0
cDovL2xpc3RzLnhlbi5vcmcveGVuLXVzZXJz

From xen-users-bounces@lists.xen.org Sun Sep 30 20:45:11 2012
Return-path: 
Envelope-to: archives@lists.xen.org
Delivery-date: Sun, 30 Sep 2012 20:45:11 +0000
Received: from localhost ([127.0.0.1] helo=lists.xen.org)
	by lists.xen.org with esmtp (Exim 4.72)
	(envelope-from )
	id 1TIQN3-0004Id-SJ; Sun, 30 Sep 2012 20:44:13 +0000
Received: from mail6.bemta4.messagelabs.com ([85.158.143.247])
	by lists.xen.org with esmtp (Exim 4.72)
	(envelope-from ) id 1TIQN1-0004IY-Jn
	for xen-users@lists.xen.org; Sun, 30 Sep 2012 20:44:11 +0000
Received: from [85.158.143.99:9931] by server-1.bemta-4.messagelabs.com id
	EA/B8-05684-A1FA8605; Sun, 30 Sep 2012 20:44:10 +0000
X-Env-Sender: robert@digitalsilk.net
X-Msg-Ref: server-2.tower-216.messagelabs.com!1349037849!24141732!1
X-Originating-IP: [208.157.175.245]
X-SpamReason: No, hits=0.0 required=7.0 tests=
X-StarScan-Received: 
X-StarScan-Version: 6.6.1.3; banners=-,-,-
X-VirusChecked: Checked
Received: (qmail 6463 invoked from network); 30 Sep 2012 20:44:10 -0000
Received: from bal-bb-static3-cisco-ws-20.dsl.airstreamcomm.net (HELO
	bilbo.digitalsilk.net) (208.157.175.245)
	by server-2.tower-216.messagelabs.com with DHE-RSA-AES256-SHA encrypted
	SMTP; 30 Sep 2012 20:44:10 -0000
Received: by bilbo.digitalsilk.net (Postfix, from userid 1001)
	id 18D6C16639; Sun, 30 Sep 2012 15:44:03 -0500 (CDT)
X-Spam-Checker-Version: SpamAssassin 3.3.2 (2011-06-06) on bilbo
X-Spam-Status: No, hits=-1.0 required=3.0 tests=ALL_TRUSTED
X-Spam-Level: 
Received: from bunsen-wifi.digitalsilk.lan (link.digitalsilk.lan
	[192.168.2.254])
	by bilbo.digitalsilk.net (Postfix) with ESMTP id C54EC16636
	for ; Sun, 30 Sep 2012 15:44:02 -0500 (CDT)
Message-ID: <5068AF20.1040101@digitalsilk.net>
Date: Sun, 30 Sep 2012 15:44:16 -0500
From: Robert Rust 
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7;
	rv:15.0) Gecko/20120907 Thunderbird/15.0.1
MIME-Version: 1.0
To: xen-users@lists.xen.org
Subject: [Xen-users] repeated domU filesystem corruption
X-BeenThere: xen-users@lists.xen.org
X-Mailman-Version: 2.1.13
Precedence: list
List-Id: Xen user discussion 
List-Unsubscribe: ,
	
List-Post: 
List-Help: 
List-Subscribe: ,
	
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"; Format="flowed"
Sender: xen-users-bounces@lists.xen.org
Errors-To: xen-users-bounces@lists.xen.org

I'm being plagued by repeated corruption of file systems for a few of my 
DomUs.  I originally thought it was a failing hard drive, so I've 
replaced the hard drive but my problems continue.  I always end up with 
the following on the DomU console:
[177949.345654] EXT3-fs (xvda2): error in ext3_new_inode: IO failure
[177949.345669] Aborting journal on device xvda2.

I'm using LVMs to house my file systems.  Can anyone help me root out 
what the cause of this is?  Is it reasonable to blame software for this?

-Robert

_______________________________________________
Xen-users mailing list
Xen-users@lists.xen.org
http://lists.xen.org/xen-users

From xen-users-bounces@lists.xen.org Sun Sep 30 20:45:11 2012
Return-path: 
Envelope-to: archives@lists.xen.org
Delivery-date: Sun, 30 Sep 2012 20:45:11 +0000
Received: from localhost ([127.0.0.1] helo=lists.xen.org)
	by lists.xen.org with esmtp (Exim 4.72)
	(envelope-from )
	id 1TIQN3-0004Id-SJ; Sun, 30 Sep 2012 20:44:13 +0000
Received: from mail6.bemta4.messagelabs.com ([85.158.143.247])
	by lists.xen.org with esmtp (Exim 4.72)
	(envelope-from ) id 1TIQN1-0004IY-Jn
	for xen-users@lists.xen.org; Sun, 30 Sep 2012 20:44:11 +0000
Received: from [85.158.143.99:9931] by server-1.bemta-4.messagelabs.com id
	EA/B8-05684-A1FA8605; Sun, 30 Sep 2012 20:44:10 +0000
X-Env-Sender: robert@digitalsilk.net
X-Msg-Ref: server-2.tower-216.messagelabs.com!1349037849!24141732!1
X-Originating-IP: [208.157.175.245]
X-SpamReason: No, hits=0.0 required=7.0 tests=
X-StarScan-Received: 
X-StarScan-Version: 6.6.1.3; banners=-,-,-
X-VirusChecked: Checked
Received: (qmail 6463 invoked from network); 30 Sep 2012 20:44:10 -0000
Received: from bal-bb-static3-cisco-ws-20.dsl.airstreamcomm.net (HELO
	bilbo.digitalsilk.net) (208.157.175.245)
	by server-2.tower-216.messagelabs.com with DHE-RSA-AES256-SHA encrypted
	SMTP; 30 Sep 2012 20:44:10 -0000
Received: by bilbo.digitalsilk.net (Postfix, from userid 1001)
	id 18D6C16639; Sun, 30 Sep 2012 15:44:03 -0500 (CDT)
X-Spam-Checker-Version: SpamAssassin 3.3.2 (2011-06-06) on bilbo
X-Spam-Status: No, hits=-1.0 required=3.0 tests=ALL_TRUSTED
X-Spam-Level: 
Received: from bunsen-wifi.digitalsilk.lan (link.digitalsilk.lan
	[192.168.2.254])
	by bilbo.digitalsilk.net (Postfix) with ESMTP id C54EC16636
	for ; Sun, 30 Sep 2012 15:44:02 -0500 (CDT)
Message-ID: <5068AF20.1040101@digitalsilk.net>
Date: Sun, 30 Sep 2012 15:44:16 -0500
From: Robert Rust 
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7;
	rv:15.0) Gecko/20120907 Thunderbird/15.0.1
MIME-Version: 1.0
To: xen-users@lists.xen.org
Subject: [Xen-users] repeated domU filesystem corruption
X-BeenThere: xen-users@lists.xen.org
X-Mailman-Version: 2.1.13
Precedence: list
List-Id: Xen user discussion 
List-Unsubscribe: ,
	
List-Post: 
List-Help: 
List-Subscribe: ,
	
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"; Format="flowed"
Sender: xen-users-bounces@lists.xen.org
Errors-To: xen-users-bounces@lists.xen.org

I'm being plagued by repeated corruption of file systems for a few of my 
DomUs.  I originally thought it was a failing hard drive, so I've 
replaced the hard drive but my problems continue.  I always end up with 
the following on the DomU console:
[177949.345654] EXT3-fs (xvda2): error in ext3_new_inode: IO failure
[177949.345669] Aborting journal on device xvda2.

I'm using LVMs to house my file systems.  Can anyone help me root out 
what the cause of this is?  Is it reasonable to blame software for this?

-Robert

_______________________________________________
Xen-users mailing list
Xen-users@lists.xen.org
http://lists.xen.org/xen-users

From xen-users-bounces@lists.xen.org Sun Sep 30 21:15:37 2012
Return-path: 
Envelope-to: archives@lists.xen.org
Delivery-date: Sun, 30 Sep 2012 21:15:37 +0000
Received: from localhost ([127.0.0.1] helo=lists.xen.org)
	by lists.xen.org with esmtp (Exim 4.72)
	(envelope-from )
	id 1TIQqN-0004iX-QM; Sun, 30 Sep 2012 21:14:31 +0000
Received: from mail6.bemta5.messagelabs.com ([195.245.231.135])
	by lists.xen.org with esmtp (Exim 4.72)
	(envelope-from ) id 1TIQqM-0004iS-CW
	for xen-users@lists.xen.org; Sun, 30 Sep 2012 21:14:30 +0000
Received: from [85.158.139.211:44760] by server-8.bemta-5.messagelabs.com id
	E0/A4-18073-536B8605; Sun, 30 Sep 2012 21:14:29 +0000
X-Env-Sender: fajar@fajar.net
X-Msg-Ref: server-9.tower-206.messagelabs.com!1349039667!19009821!1
X-Originating-IP: [209.85.214.173]
X-SpamReason: No, hits=0.3 required=7.0 tests=RCVD_BY_IP
X-StarScan-Received: 
X-StarScan-Version: 6.6.1.3; banners=-,-,-
X-VirusChecked: Checked
Received: (qmail 9861 invoked from network); 30 Sep 2012 21:14:29 -0000
Received: from mail-ob0-f173.google.com (HELO mail-ob0-f173.google.com)
	(209.85.214.173)
	by server-9.tower-206.messagelabs.com with RC4-SHA encrypted SMTP;
	30 Sep 2012 21:14:29 -0000
Received: by obbwc18 with SMTP id wc18so3171640obb.32
	for ; Sun, 30 Sep 2012 14:14:27 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
	d=google.com; s=20120113;
	h=mime-version:in-reply-to:references:date:message-id:subject:from:to
	:cc:content-type:x-gm-message-state;
	bh=9hxohsVYi620stu0AlS6IkgLDUNrtfBaT1uDD33im4g=;
	b=SraHhc9W7GFyMmKIrKYNiCGsjgy0R+NGgfiVb1L6r1Ge5CyoVtorS6xf1ogz0xOVAZ
	SsK4vhkFfDvN6ulSsSSkcXr5n8PkMUCwq1zgdicF0lrzfJ4MrLV0+6LienBQEkXDMnAn
	fD2zFaZ85q1DZ5xd5wGZJ2+XTJwE/jDHcPly4QQ0MHWnJNlKiF/yIWPDzXXc4TnC9pws
	h19GEbumPxJNzA02JWcAvDS5cg3AwiiBNRphd++hgXXw4eh67ffE5FkSyd36vslcEftA
	gEdZTQSJDs8xWChw307yNfvH+t0HprHB0meNVj7V+eYGJBhN0jRioKZjs43BIuU6vZqU
	7W+Q==
MIME-Version: 1.0
Received: by 10.60.170.133 with SMTP id am5mr10257382oec.51.1349039667448;
	Sun, 30 Sep 2012 14:14:27 -0700 (PDT)
Received: by 10.60.150.141 with HTTP; Sun, 30 Sep 2012 14:14:27 -0700 (PDT)
In-Reply-To: <5068AF20.1040101@digitalsilk.net>
References: <5068AF20.1040101@digitalsilk.net>
Date: Mon, 1 Oct 2012 04:14:27 +0700
Message-ID: 
From: "Fajar A. Nugraha" 
To: Robert Rust 
X-Gm-Message-State: ALoCoQnwCkLrlWLRITWxpP7z5TfZtbuTSCCRel++FPR4LNh5c+jt61B0TrVJWTLwd5ZipJexff+2
Cc: xen-users@lists.xen.org
Subject: Re: [Xen-users] repeated domU filesystem corruption
X-BeenThere: xen-users@lists.xen.org
X-Mailman-Version: 2.1.13
Precedence: list
List-Id: Xen user discussion 
List-Unsubscribe: ,
	
List-Post: 
List-Help: 
List-Subscribe: ,
	
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: xen-users-bounces@lists.xen.org
Errors-To: xen-users-bounces@lists.xen.org

On Mon, Oct 1, 2012 at 3:44 AM, Robert Rust  wrote:
> I'm being plagued by repeated corruption of file systems for a few of my
> DomUs.  I originally thought it was a failing hard drive, so I've replaced
> the hard drive but my problems continue.  I always end up with the following
> on the DomU console:
> [177949.345654] EXT3-fs (xvda2): error in ext3_new_inode: IO failure
> [177949.345669] Aborting journal on device xvda2.
>
> I'm using LVMs to house my file systems.  Can anyone help me root out what
> the cause of this is?  Is it reasonable to blame software for this?

IIRC I had something like that a long time ago, and it was solved by
xen update. Can't remember exactly which version though.
Try using the latest version, either from upstream directly, or one
that your distro bundled.

... And if you're using distro-bundled version, make sure to file a
bug fix/support request to the distro/package maintainers.

-- 
Fajar

_______________________________________________
Xen-users mailing list
Xen-users@lists.xen.org
http://lists.xen.org/xen-users

From xen-users-bounces@lists.xen.org Sun Sep 30 21:15:37 2012
Return-path: 
Envelope-to: archives@lists.xen.org
Delivery-date: Sun, 30 Sep 2012 21:15:37 +0000
Received: from localhost ([127.0.0.1] helo=lists.xen.org)
	by lists.xen.org with esmtp (Exim 4.72)
	(envelope-from )
	id 1TIQqN-0004iX-QM; Sun, 30 Sep 2012 21:14:31 +0000
Received: from mail6.bemta5.messagelabs.com ([195.245.231.135])
	by lists.xen.org with esmtp (Exim 4.72)
	(envelope-from ) id 1TIQqM-0004iS-CW
	for xen-users@lists.xen.org; Sun, 30 Sep 2012 21:14:30 +0000
Received: from [85.158.139.211:44760] by server-8.bemta-5.messagelabs.com id
	E0/A4-18073-536B8605; Sun, 30 Sep 2012 21:14:29 +0000
X-Env-Sender: fajar@fajar.net
X-Msg-Ref: server-9.tower-206.messagelabs.com!1349039667!19009821!1
X-Originating-IP: [209.85.214.173]
X-SpamReason: No, hits=0.3 required=7.0 tests=RCVD_BY_IP
X-StarScan-Received: 
X-StarScan-Version: 6.6.1.3; banners=-,-,-
X-VirusChecked: Checked
Received: (qmail 9861 invoked from network); 30 Sep 2012 21:14:29 -0000
Received: from mail-ob0-f173.google.com (HELO mail-ob0-f173.google.com)
	(209.85.214.173)
	by server-9.tower-206.messagelabs.com with RC4-SHA encrypted SMTP;
	30 Sep 2012 21:14:29 -0000
Received: by obbwc18 with SMTP id wc18so3171640obb.32
	for ; Sun, 30 Sep 2012 14:14:27 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
	d=google.com; s=20120113;
	h=mime-version:in-reply-to:references:date:message-id:subject:from:to
	:cc:content-type:x-gm-message-state;
	bh=9hxohsVYi620stu0AlS6IkgLDUNrtfBaT1uDD33im4g=;
	b=SraHhc9W7GFyMmKIrKYNiCGsjgy0R+NGgfiVb1L6r1Ge5CyoVtorS6xf1ogz0xOVAZ
	SsK4vhkFfDvN6ulSsSSkcXr5n8PkMUCwq1zgdicF0lrzfJ4MrLV0+6LienBQEkXDMnAn
	fD2zFaZ85q1DZ5xd5wGZJ2+XTJwE/jDHcPly4QQ0MHWnJNlKiF/yIWPDzXXc4TnC9pws
	h19GEbumPxJNzA02JWcAvDS5cg3AwiiBNRphd++hgXXw4eh67ffE5FkSyd36vslcEftA
	gEdZTQSJDs8xWChw307yNfvH+t0HprHB0meNVj7V+eYGJBhN0jRioKZjs43BIuU6vZqU
	7W+Q==
MIME-Version: 1.0
Received: by 10.60.170.133 with SMTP id am5mr10257382oec.51.1349039667448;
	Sun, 30 Sep 2012 14:14:27 -0700 (PDT)
Received: by 10.60.150.141 with HTTP; Sun, 30 Sep 2012 14:14:27 -0700 (PDT)
In-Reply-To: <5068AF20.1040101@digitalsilk.net>
References: <5068AF20.1040101@digitalsilk.net>
Date: Mon, 1 Oct 2012 04:14:27 +0700
Message-ID: 
From: "Fajar A. Nugraha" 
To: Robert Rust 
X-Gm-Message-State: ALoCoQnwCkLrlWLRITWxpP7z5TfZtbuTSCCRel++FPR4LNh5c+jt61B0TrVJWTLwd5ZipJexff+2
Cc: xen-users@lists.xen.org
Subject: Re: [Xen-users] repeated domU filesystem corruption
X-BeenThere: xen-users@lists.xen.org
X-Mailman-Version: 2.1.13
Precedence: list
List-Id: Xen user discussion 
List-Unsubscribe: ,
	
List-Post: 
List-Help: 
List-Subscribe: ,
	
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: xen-users-bounces@lists.xen.org
Errors-To: xen-users-bounces@lists.xen.org

On Mon, Oct 1, 2012 at 3:44 AM, Robert Rust  wrote:
> I'm being plagued by repeated corruption of file systems for a few of my
> DomUs.  I originally thought it was a failing hard drive, so I've replaced
> the hard drive but my problems continue.  I always end up with the following
> on the DomU console:
> [177949.345654] EXT3-fs (xvda2): error in ext3_new_inode: IO failure
> [177949.345669] Aborting journal on device xvda2.
>
> I'm using LVMs to house my file systems.  Can anyone help me root out what
> the cause of this is?  Is it reasonable to blame software for this?

IIRC I had something like that a long time ago, and it was solved by
xen update. Can't remember exactly which version though.
Try using the latest version, either from upstream directly, or one
that your distro bundled.

... And if you're using distro-bundled version, make sure to file a
bug fix/support request to the distro/package maintainers.

-- 
Fajar

_______________________________________________
Xen-users mailing list
Xen-users@lists.xen.org
http://lists.xen.org/xen-users